OmniSwitch OS6860/OS6900/OS10K Troubleshooting Guide Part No.032996-00 Rev.A
AOS Release 7.X and 8.X January 2015
Alcatel-Lucent Page 64 of 148
Slice 0 - Reserved for untrusted port entries/low priority (overridable) system slice
Slice 1 - Reserved for IP protocol cpu priority entries
Slices 14 & 15 - Reserved for high priority (non overridable) system slices
Features which require TCAM reservation:
QoS Policies - can dynamically use all free slices based on policy configuration
SIP snooping - will use between 1-4 slices based on a static tunable when enabled
FIP snooping - reserves a single slice when enabled
OpenFlow - Will reserve all free slices (2-13) when enabled (no other applications can be in use if it is
enabled)
AntiSpoofing - reserves a single slice when enabled
Vlan Stacking / SPB SAPs - can dynamically use all free slices based on configuration
*,G: - reserves a single slice when enabled
DHCP Snooping - reserves a single slice on ASICs where DHCP snooping ports are enabled
Deep Packet Inspection - reserves a single slice when enabled
No cache
For 'Switch' group policies it's recommended to use the 'no-cache' keyword in the action for the rule (it really
should be part of the rule, but for historical reasons it's in the action). That will cause the policy to not be
programmed into the hardware TCAM and only be matched in software. It is recommended to use AOS
7.3.1.643.R01 or later - given test traffic in the lab, show health shows no change in CPU utilization.
It's may be tricky to get right though, especially in the case there are rules with a lower precedence "deny all"
and higher precedence "accept" policies. All policies that come after the first no-cache policy will need to be
carefully checked to see if they also need to be no-cache, since if there's any overlap then they'll match first if
they're in hardware.
Maximum bandwidth per port
There are two ways of limiting ingress banwidth:
qos port <chassis/slot/port> maximum ingress-bandwidth <bw> maximum depth <depth>
or
interfaces <chassis/slot/port> ingress-bandwidth mbps <bw> burst <burst>
interfaces <chassis/slot/port> ingress-bandwidth enable
Minimum and maximum bandwidth per queue
The following configuration from AOS 6:
qos port slot/port qn {minbw | maxbw} kbps
Can be replaced by:
-> show configuration snapshot vfc
! Virtual Flow Control:
qos qsp dcb "port11001" import qsp dcb "dcp-1"
qos qsp dcb "port11001" tc 1 min-bw 0 max-bw 20
qos qsp dcb "port11001" tc 2 max-bw 20
qos qsi port 1/1/1 qsp dcb "port11001"
QoS/ACL Design and Configuration
Introduction
QoS software on OmniSwitch 6900 provides a way to manipulate flows coming through the switch based on
user configured policies such as ACLs, traffic prioritization, bandwidth shaping or traffic marking and
mapping. ACLs are a specific type of QoS policy used for Layer 2, Layer 3/4, and multicast filtering. The
below is intended to provide the QoS/ACL necessary information on the OmniSwitch 6900 series to
successfully configure and design a QoS/ACL policy in your networks.
To Next Page
Loading...
