Alcatel-Lucent omnistack 6300 Guía Del Usuario

Descargar
Página de 21
♦  IP precedence rule on output/egress service policy 
Console(config)# access-list ip mask-precedence out 
Console(config-ip-mask-acl)# mask any any precedence 
Console(config-ip-mask-acl)# exit 
♦  IP dscp  rule  on input/ingress service policy 
Console(config)# access-list ip mask-precedence in 
Console(config-ip-mask-acl)# mask any any dscp 
Console(config-ip-mask-acl)# exit 
♦  IP dscp  rule  on output/egress service policy 
Console(config)# access-list ip mask-precedence out 
Console(config-ip-mask-acl)# mask any any dscp 
Console(config-ip-mask-acl)# exit 
♦  vlan rule on input/ingress service policy 
Console(config)# access-list mac mask-precedence in 
Console(config-mac-mask-acl)# mask any any vid 
Console(config-mac-mask-acl)# exit 
♦  vlan rule on output/egress service policy 
Console(config)# access-list mac mask-precedence out 
Console(config-mac-mask-acl)# mask any any vid 
Console(config-mac-mask-acl)# exit 
 
Limitations 
♦  Only 1 input Policy can be configured per interface 
♦  Only 1 output Policy can be configured per interface 
♦  A Policy can have up to 8 actions on FastEthernet interfaces 
♦  A Policy can have up to 128 actions on GigabitEthernet interfaces 
♦  A Class is always “match-any”, a packet matches a Class if it matches one of the rules defined in the Class 
♦  Always create a “vlan mask” when using a “vlan” rule in a Class-Map 
♦  Always create a “ip precedence mask” when using an “ip precedence” rule in a Class-Map 
♦  Always create a “ip dscp mask” when using an “ip dscp” rule in a Class-Map 
♦  A policy has to have at least one “set” action. A policy with only one rate limiting action is not allowed 
♦  “output” service policy do not support rate limiting. If a rate limiting policy is attached to an interface as 
“output”, the rate limiting action will be ignored. 
 
Issues 
“Set ip dscp” action does not work, DSCP value is always set to 0. 
Also, the Internal priority is always the same. 
Interoperability with OmniSwitch 6624/6648 7700/7800 8800 
This feature is the equivalent of the “policy condition”, “policy action”, “policy rule” feature on OmniSwitch 
6624/6648 7700/7800 8800. 
Also, this feature allows the user to create some “mapping” policies. 
For instance, you can create a “Class-Map” ToS 5 with action “set ToS 7” in order to map ToS 5 to ToS 7. 
OmniSwitch 6300 does not need a “qos apply” (that flushes the mac and arp tables) after creating a new policy. 
Policies are enforced to a dedicated filtering hardware that does not interact with “source learning”. 
Polices always work at “wire speed”, there is no software processing at all. 
 
 
Examples  
With the following setup, we will explain several configurations. 
        
IXIA1 
 1/1 OmniSwitch 6300 1/3 
 1/3 OmniSwitch 7700 1/1 
 IXIA3 
IXIA2 
 1/2 
 
 
 
 
   
 
        1/2 
 IXIA4 
 
All ports are 100Mbps Full and tagged for vlan 2  
2 flows are running at 95Mbps each. 
- Flow1: IXIA1->IXIA3 000000:000003/2.0.0.3 -> 000000:000003/2.0.0.1  
  with 802.1p 0 and ToS byte 0xC8 (ip precedence or tos 3 and dscp 26) 
- Flow2: IXIA2->IXIA4 000000:000004/2.0.0.4 -> 000000:000003/2.0.0.2  
  with 802.1p 3 and ToS byte 0x30 (ip precedence or tos 1 and dscp 12)