Changes between Version 1 and Version 2 of VLANQoS

Show
Ignore:
Timestamp:
03/29/10 16:51:02 (9 years ago)
Author:
yxin (IP: 152.54.8.156)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VLANQoS

    v1 v2  
    77The Catalyst 6500/6000 Policy Feature Card (PFC) and PFC2 only support ingress policing. The PFC3 supports both ingress and egress policing. Traffic shaping is only supported on certain WAN modules for the Catalyst 6500/7600 series, such as the Optical Services Modules (OSMs) and FlexWAN modules. Refer to the Cisco 7600 Series Router Module Configuration Notes for more information 
    88 
    9 Prerequisites 
    10  
    11 Requirements 
    12  
    13 There are no specific requirements for this document. 
    14  
    15 Components Used 
    16  
    17 This document is not restricted to specific software and hardware versions. 
    18  
    19 Conventions 
    20  
    21 Refer to the Cisco Technical Tips Conventions for more information on document conventions. 
    22  
    239QoS Policing Parameters 
    2410 
     
    156142Consider the same example as that provided in the section Configure and Monitor Policing in CatOS Software, but now with Cisco IOS Software. For this example, you have a traffic generator attached to port 2/8. It sends 17 Mbps of UDP traffic with destination port 111: 
    157143 
     144{{{ 
    158145Catalyst 6500/6000 
    159146 
     
    191178 
    192179!--- This applies the QoS policy to an interface. 
    193  
     180}}} 
    194181There are two types of aggregate policers in Cisco IOS Software: named and per-interface. The named aggregate policer polices the traffic combined from all interfaces to which it is applied. This is the type used in the above example. The per-interface policer polices traffic separately on each inbound interface to which it is applied. A per-interface policer is defined within the policy map configuration. Consider this example, which has a per-interface aggregate policer: 
    195182 
     183{{{ 
    196184Catalyst 6500/6000 
    197185 
     
    224212 
    225213!--- This applies the QoS policy to an interface. 
    226  
     214}}} 
    227215Microflow policers are defined within the policy map configuration, as are per-interface aggregate policers. In the example below, every flow from host 192.168.2.2 that comes into VLAN 2 is policed to 100 kbps. All traffic from 192.168.2.2 is policed to 500 kbps aggregate. VLAN 2 includes interfaces fa4/11 and fa4/12: 
    228216 
     217{{{ 
    229218Catalyst 6500/6000 
    230219 
     
    268257 
    269258!--- This applies the QoS policy to VLAN 2. 
     259}}} 
    270260 
    271261The example below shows a configuration for egress policing for the Supervisor Engine 720. It establishes the policing of all outbound traffic on interface Gigabit Ethernet 8/6 to 100 kbps: 
    272262 
     263{{{ 
    273264Catalyst 6500/6000 
    274265 
     
    297288 
    298289!--- This attaches the policy to an interface. 
     290}}} 
    299291 
    300292The example below shows a configuration for per-user policing for the Supervisor Engine 720. Traffic that comes in from users behind port 1/1 toward the Internet is policed to 1 Mbps per user. Traffic that comes from the Internet toward the users is policed to 5 Mbps per user: 
    301293 
     294{{{ 
    302295Catalyst 6500/6000 
    303296 
     
    343336 
    344337!--- 1/2 is the uplink to the Internet. 
    345  
    346338service-policy input pol_in 
     339}}} 
    347340To monitor policing, you can use these commands: 
    348  
     341{{{ 
    349342bratan# show mls qos  
    350343QoS is enabled globally 
     
    375368Gi2/8 1   In  udp_qos   0    1*   No    0        127755           2134670 
    376369Note: Allowed packets have increased by 304 and excess packets have increased by 5068. This means that the policer has dropped 5068 packets and allowed 304 to pass through. Given the input rate of 17 Mbps, the policer should pass 1/17 of the traffic. If you compare the dropped and forwarded packets, you see that this has been the case: 304 / (304 + 5068) = 0.057, or roughly 1/17. Some minor variation is possible due to hardware policing granularity. 
     370}}} 
    377371 
    378372For microflow policing statistics, use the show mls ip detail command: 
    379373 
     374{{{ 
    380375Orion# show mls ip detail 
    381376IP Destination IP Source        Protocol L4 Ports     Vlan Xtag L3-protocol  
     
    399394YES   1937     NO       NO 
    400395Note: The Police Count field shows the number of policed packets per flow. 
     396}}}