cbwfq on atm subinterface

Trying to apply service-policy (cbwfq) command to an atm sub-int. Note there is also a BVI interface configured for this adsl link, but, the BVI int doesn't support service-policy (cbwfq). Perhaps that is somehow the problem. But, please read on...

Restrictions from this doc

formatting link
Configuring CBWFQ on a physical interface is only possible if the interface is in the default queueing mode. Serial interfaces at E1 (2.048 Mbps) and below use WFQ by default?other interfaces use FIFO by default. Enabling CBWFQ on a physical interface overrides the default interface queueing method. Enabling CBWFQ on an ATM PVC does not override the default queueing method.

If you configure a class in a policy map to use WRED for packet drop instead of tail drop, you must ensure that WRED is not configured on the interface to which you intend to attach that service policy.

Traffic shaping and policing are not currently supported with CBWFQ.

CBWFQ is supported on variable bit rate (VBR) and available bit rate (ABR) ATM connections. It is not supported on unspecified bit rate (UBR) connections.

...........

Interestingly, the max configurable bw is 384kbps, the same as the priority value on the voice class. Just a coincidence? I'd rather set it to something higher, say 1536, but, I'll take it for test purposes at the moment...

router(config-if-atm-vc)#vbr-nrt ? Peak Cell Rate(PCR) in Kbps

however even after applying the command

router(config-if-atm-vc)#vbr-nrt 384 384 router(config-if-atm-vc)#service-policy output voice router(config-if-atm-vc)#end router#sh policy-map int

router#sh policy-map Policy Map voice Class voice Strict Priority Bandwidth 384 (kbps) Burst 9600 (Bytes) Class class-default Flow based Fair Queueing Bandwidth 0 (kbps) Max Threshold 64 (packets)

...sh run

interface ATM0.1 point-to-point no snmp trap link-status bridge-group 1 pvc 0/35 encapsulation aal5snap ! !

....it takes the service-policy command but nothing shows up under the atm sub-int nor "show policy-map int". Is it applied?

Here's the output of sh int. Note there is no queueing listed under atm0.1 and it's fifo elsewhere.

ATM0 is up, line protocol is up Hardware is DSLSAR (with Alcatel ADSL Module) MTU 4470 bytes, sub MTU 4470, BW 384 Kbit, DLY 1330 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ATM, loopback not set Encapsulation(s): AAL5 AAL2, PVC mode 23 maximum active VCs, 256 VCs per VP, 1 current VCCs VC Auto Creation Disabled. VC idle disconnect time: 300 seconds Last input 00:58:32, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: Per VC Queueing 5 minute input rate 3000 bits/sec, 4 packets/sec 5 minute output rate 3000 bits/sec, 4 packets/sec 9466 packets input, 1432144 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 42469 packets output, 2217792 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out ATM0.1 is up, line protocol is up Hardware is DSLSAR (with Alcatel ADSL Module) MTU 4470 bytes, BW 384 Kbit, DLY 1330 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ATM 68931 packets input, 13483251 bytes 298787 packets output, 16730828 bytes 0 OAM cells input, 0 OAM cells output AAL5 CRC errors : 0 AAL5 SAR Timeouts : 0 AAL5 Oversized SDUs : 0 Last clearing of "show interface" counters never BVI1 is up, line protocol is up Hardware is BVI, address is 0000.0c96.6958 (bia 000c.857f.9a93) Internet address is x MTU 4470 bytes, BW 800 Kbit, DLY 5000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/0 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 2000 bits/sec, 4 packets/sec 5875 packets input, 1261279 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 7363 packets output, 636468 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out FastEthernet0 is up, line protocol is up Hardware is PQUICC_FEC, address is 000c.857f.9a93 (bia 000c.857f.9a93) Internet address is 192.168.2.1/24 MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s, 100BaseTX/FX ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:11, output 00:00:04, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 11175 packets input, 1276337 bytes Received 6460 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog 0 input packets with dribble condition detected 13055 packets output, 1971283 bytes, 0 underruns 53 output errors, 0 collisions, 2 interface resets 0 babbles, 0 late collision, 0 deferred 53 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out NVI0 is up, line protocol is up Hardware is NVI Interface is unnumbered. Using address of NVI0 (0.0.0.0) MTU 1514 bytes, BW 10000000 Kbit, DLY 0 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation UNKNOWN, loopback not set Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out

..................

more service-policy command ref here.

formatting link

Reply to
linguafr
Loading thread data ...

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.