Flow-Based DWFQ Example - DWFQ on a Fast Ethernet interface
- DWFQ system should not contain more than 200 packets
- No queue should accept new packets when the DWFQ system is congested and the queue is longer than 30 packets
- interface FastEthernet 1/1/0
- ip address 80.0.2.70 255.255.255.0
- fair-queue
- fair-queue aggregate-limit 200
- fair-queue individual-limit 30
- !
show interface - Router#show interfaces FastEthernet1/1/0
- FastEthernet1/1/0 is up, line protocol is up
- Hardware is cyBus FastEthernet Interface, address is 0007.f618.4448
- Description: pkt input i/f for WRL tests (to pagent)
- Internet address is 80.0.2.70/24
- MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
- Encapsulation ARPA, loopback not set, keepalive not set, 100BaseTX/FX
- ARP type: ARPA, ARP Timeout 04:00:00
- Last input never, output 01:11:01, output hang never
- Last clearing of "show interface" counters 01:12:31
- Queueing strategy: VIP-based fair queuing
- Output queue 0/40, 0 drops; input queue 0/75, 0 drops
- 30 second input rate 0 bits/sec, 0 packets/sec
- 30 second output rate 0 bits/sec, 0 packets/sec
- … rest deleted ...
show interface fair-queue - Router#show interface fastethernet 1/1/0 fair
- FastEthernet 1/1/0 queue size 0
- pkts output 0, wfq drops 0, nobuffer drops 0
- WFQ: aggregate queue limit 200 individual queue limit 30
- max available buffers 0
Benefits and Drawbacks of Flow-Based DWFQ - Benefits
- Drawbacks
- Does not support the configuration of classification
- Does not use IP Precedence as weight
- Only supported on Cisco 7x00 series routers with VIP2-40 or newer
Chia sẻ với bạn bè của bạn: |
