Displaying egress–queue StatisticsTo display the number of transmitted and dropped packets and their rate on the egress queues of an interface, use the following command:• Display the number of packets and number of bytes on the egress-queue profile.EXEC Privilege modeshow qos statistics egress-queueExample of show qos statistics egress-queue CommandDell#show qos statistics egress-queue tengigabitethernet 1/4/1/2Interface Te 1/4/1/2Unicast/Multicast Egress Queue StatisticsQueue# Q# Type TxPkts TxPkts/s TxBytes TxBytes/s DroppedPkts DroppedPkts/s DroppedBytes DroppedBytes/s---------------------------------------------------------------------------------------------------------------------------0 UCAST 0 0 0 0 0 0 0 01 UCAST 0 0 0 0 0 0 0 02 UCAST 0 0 0 0 0 0 0 03 UCAST 1708252734 2340972 874625399808 1198000301 1357413570 0 694995747840 04 UCAST 0 0 0 0 0 0 0 05 UCAST 0 0 0 0 0 0 0 06 UCAST 0 0 0 0 0 0 0 07 UCAST 0 0 0 0 0 0 0 08 UCAST 0 0 0 0 0 0 0 09 UCAST 1132 1 143063 217 0 0 0 010 MCAST 0 0 0 0 0 0 0 011 MCAST 0 0 0 0 0 0 0 012 MCAST 0 0 0 0 0 0 0 013 MCAST 0 0 0 0 0 0 0 014 MCAST 0 0 0 0 0 0 0 015 MCAST 0 0 0 0 0 0 0 016 MCAST 0 0 0 0 0 0 0 017 MCAST 0 0 0 0 0 0 0 018 MCAST 0 0 0 0 0 0 0 019 MCAST 0 0 0 0 0 0 0 0Dell#Pre-Calculating Available QoS CAM SpaceBefore Dell Networking OS version 7.3.1, there was no way to measure the number of CAM entries a policy-map would consume (thenumber of CAM entries that a rule uses is not predictable; from 1 to 16 entries might be used per rule depending upon its complexity).Therefore, it was possible to apply to an interface a policy-map that requires more entries than are available. In this case, the system writesas many entries as possible, and then generates an CAM-full error message (shown in the following example). The partial policy-mapconfiguration might cause unintentional system behavior.%EX2YD:12 %DIFFSERV-2-DSA_QOS_CAM_INSTALL_FAILED: Not enough space in L3Cam(PolicyQos) for class 2 (TeGi 12/20) entries on portpipe 1The test cam-usage command allows you to verify that there are enough available CAM entries before applying a policy-map to aninterface so that you avoid exceeding the QoS CAM space and partial configurations. This command measures the size of the specifiedpolicy-map and compares it to the available CAM space in a partition for a specified port-pipe.Test the policy-map size against the CAM space for a specific port-pipe or all port-pipes using these commands:• test cam-usage service-policy input policy-map {stack-unit } number port-set number• test cam-usage service-policy input policy-map {stack-unit } allThe output of this command, shown in the following example, displays:• The estimated number of CAM entries the policy-map will consume.• Whether or not the policy-map can be applied.• The number of interfaces in a port-pipe to which the policy-map can be applied.Specifically:• Available CAM — the available number of CAM entries in the specified CAM partition for the specified line card or stack-unit port-pipe.716 Quality of Service (QoS)
