From: Elias Chari (elias.chari@gmail.com)
Date: Thu Aug 03 2006 - 15:00:21 ART
Hi Sami,
Hmm... it should work. Have you got fair queuing enabled in the default
class where you have random detect?
Normally in the default class you need to enable fair queuing or assign a
bandwidth to allow RED.
It could be a bug. Try with another router which runs on a different code.
Rgds
Elias
On 8/3/06, Sami <sy1977@gmail.com> wrote:
>
> Thanks Elias.
>
> If there is only one DLCI and there is no requirement of FRTS, can we map
> service policy directly on FR physical inteface. will it work or not?
>
> I tried to apply service policy with random-detect and router..crashed..
>
>
>
> R2(config-pmap-c)#^Z
> R2#s
> *Aug 3 15:54:34.457: %SYS-5-CONFIG_I: Configured from console by console
> R2#sho
> R2#show poli
> R2#show policy-map
> R2#show policy-map
> Policy Map ALL-TRAFFIC
> Class class-default
> Bandwidth 60 (%)
> exponential weight 9
> explicit congestion notification
> class min-threshold max-threshold mark-probablity
> ----------------------------------------------------------
>
> 0 - - 1/10
> 1 - - 1/10
> 2 - - 1/10
> 3 - - 1/10
> 4 - - 1/10
> 5 - - 1/10
> 6 - - 1/10
> 7 - - 1/10
> rsvp - - 1/10
>
> R2#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> R2(config)#int
> R2(config)#interface s0/0/0
> R2(config-if)#se
> R2(config-if)#serv
> R2(config-if)#service-policy ou
> R2(config-if)#service-policy output ALL-TRAFFIC
> R2(config-if)#^Z
> R2#sho
> *Aug 3 15:55:29.325: %SYS-5-CONFIG_I: Configured from console by console
> R2#sho
> R2#show pol
> R2#show policy-map
> R2#show policy-map int
> R2#show policy-map interface s0/0/0
>
>
> 15:55:37 UTC Thu Aug 3 2006: TLB (load or instruction fetch) exception,
> CPU signal 10, PC = 0x41E69F1C
>
>
>
> --------------------------------------------------------------------
> Possible software fault. Upon reccurence, please collect
> crashinfo, "show tech" and contact Cisco Technical Support.
> --------------------------------------------------------------------
>
>
> -Traceback= 0x41E69F1C 0x414A34CC 0x414A38C0 0x402D4ECC 0x402D7038
> 0x402D79E0 0x41E5FAE0 0x41E5F624 0x41E62D58 0x41E62DA8 0x41E62DFC 0x41298BD0
> 0x412B7604 0x42339794 0x42339778
> $0 : 00000000, AT : 45490000, v0 : 00000004, v1 : FFFFFFFF
> a0 : 00000070, a1 : FFFFFFFF, a2 : 00000004, a3 : 4668E6B8
> t0 : 45FB305C, t1 : 45A57BF8, t2 : 00000000, t3 : 00000000
> t4 : 00000000, t5 : 00000000, t6 : 00000000, t7 : 45FB1BE4
> s0 : 73202020, s1 : 4668E710, s2 : 442976C8, s3 : 44297A68
> s4 : 45FB163C, s5 : 00000040, s6 : 00000001, s7 : 46923CA8
> t8 : 00000000, t9 : 45FB240C, k0 : 45B42FCC, k1 : 423495EC
> gp : 4549C54C, sp : 4668E6E0, s8 : 00000200, ra : 41E69F1C
> EPC : 41E69F1C, ErrorEPC : BFC0900C, SREG : 3400FF03
> MDLO : 00000000, MDHI : 00000007, BadVaddr : 7320202C
> Cause 00000008 (Code 0x2): TLB (load or instruction fetch) exception
>
> Writing crashinfo to flash:crashinfo_20060803-155537
>
> 15:55:37 UTC Thu Aug 3 2006: TLB (load or instruction fetch) exception,
> CPU signal 10, PC = 0x41E69F1C
>
>
>
> --------------------------------------------------------------------
> Possible software fault. Upon reccurence, please collect
> crashinfo, "show tech" and contact Cisco Technical Support.
> --------------------------------------------------------------------
>
>
> -Traceback= 0x41E69F1C 0x414A34CC 0x414A38C0 0x402D4ECC 0x402D7038
> 0x402D79E0 0x41E5FAE0 0x41E5F624 0x41E62D58 0x41E62DA8 0x41E62DFC 0x41298BD0
> 0x412B7604 0x42339794 0x42339778
> $0 : 00000000, AT : 45490000, v0 : 00000004, v1 : FFFFFFFF
> a0 : 00000070, a1 : FFFFFFFF, a2 : 00000004, a3 : 4668E6B8
> t0 : 45FB305C, t1 : 45A57BF8, t2 : 00000000, t3 : 00000000
> t4 : 00000000, t5 : 00000000, t6 : 00000000, t7 : 45FB1BE4
> s0 : 73202020, s1 : 4668E710, s2 : 442976C8, s3 : 44297A68
> s4 : 45FB163C, s5 : 00000040, s6 : 00000001, s7 : 46923CA8
> t8 : 00000000, t9 : 45FB240C, k0 : 45B42FCC, k1 : 423495EC
> gp : 4549C54C, sp : 4668E6E0, s8 : 00000200, ra : 41E69F1C
> EPC : 41E69F1C, ErrorEPC : BFC0900C, SREG : 3400FF03
> MDLO : 00000000, MDHI : 00000007, BadVaddr : 7320202C
> Cause 00000008 (Code 0x2): TLB (load or instruction fetch) exception
>
> -Traceback= 0x41E69F1C 0x414A34CC 0x414A38C0 0x402D4ECC 0x402D7038
> 0x402D79E0 0x41E5FAE0 0x41E5F624 0x41E62D58 0x41E62DA8 0x41E62DFC 0x41298BD0
> 0x412B7604 0x42339794 0x42339778
>
>
> === Flushing messages (15:55:37 UTC Thu Aug 3 2006) ===
>
> Queued messages::
> m e
> *** System received a Bus Error exception ***
> signal= 0xa, code= 0x8, context= 0x456d3444
> PC = 0x4008ff84, Cause = 0x2020, Status Reg = 0x34008002
>
>
> System Bootstrap, Version 12.4(1r) [hqluong 1r], RELEASE SOFTWARE (fc1)
> Copyright (c) 2005 by cisco Systems, Inc.
>
> Initializing memory for ECC
> Initializing memory for ECC
> .
> c2811 processor with 262144 Kbytes of main memory
> Main memory is configured to 64 bit mode with ECC enabled
>
>
>
> On 8/3/06, Elias Chari <elias.chari@gmail.com > wrote:
> >
> > It won't until traffic shaping is enabled.
> >
> > On 8/3/06, Sami < sy1977@gmail.com> wrote:
> >
> > > Group,
> >
> > Show policy-map interface command doesn't show anything if a service
> > policy
> > using MQC is applied using FR class-map to a FR interface. Which command
> >
> > show the service policy applied to FR interface ?
> >
> > Thanks
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:55 ART