No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Qos on Portswitch interface of NE40

Publication Date:  2012-07-27 Views:  58 Downloads:  0
Issue Description
Topology: UA5000-------NE20------NE40-------SBC 
    UA5000 and SBC are in the same VPN instance ,there is some voice traffic between UA5000 and SBC . UA 5000 will mark the voice traffic with 8021.p value as 6 , then send to NE20. NE20 remark these voice packets as EF depend on the 802.1p value . So we can ensure that the voice traffic out of NE20 is EF stream. 
     While for the traffic from SBC back to UA5000, it's a little difference. Because the interface connected to SBC on NE40 is L2 interface , it can not be applied with L3 traffic-policy . 
Alarm Information
     When we defined a ACL based on IP address of SBC , and make a traffic classfier / behaviour  ,then bind this policy to the L2 interface . 
system don't allow to bind the traffic policy for this interface. 
Handling Process
1. Define a mac- group which contains the SBC's  mac-address (including the master &backup SBC interface address and the virtual mac-address)
#
 mac-group 1 mac 0000-5e00-0101    *******(virtual address)                                               
 mac-group 1 mac 00e0-fc90-5de1                                                 
 mac-group 1 mac 00e0-fc8a-f2be    
2.Define a traffic classfier 
#
traffic classifier L2-rem-voice-mac l2                                          
 if-match mac-group 1     
3. Define a traffic behaviour 
#
traffic behavior L2-rem-voice-mac                                               
 remark dscp ef    
4.Bind the traffic classfier and behaviour
#                                                                               
traffic policy L2-rem-voice-mac                                                 
 classifier L2-rem-voice-mac behavior L2-rem-voice-mac precedence 0    
5.Apply the traffic policy on the L2 interface of NE40
#
interface GigabitEthernet3/1/1                                                  
 description HOST-SBC-2---GE1/0/0                                               
 undo shutdown                                                                  
 traffic-policy L2-rem-voice-mac inbound vlan 33                                
 portswitch                                                                     
 port default vlan 33      
Root Cause
    L2 interface can't seperate the L3 traffic ,also can't be applied with L3 traffic policy . It only can be applied with L2 traffic policy which based on MAC etc. parameters.
Suggestions
Normally ,it's better to user L3 interface for Qos .Because L3 Traffic policy is easy to control . 
According to the current topology ,we can do L2 traffic policy on NE40.

END