Cisco Nexus 1000V - Debugging Policy Configuration Errors

17-4
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 17 Quality of Service
Debugging Policy Configuration Errors
2 class op_DEFAULT
Example 17-3 module vem module-number execute vemcmd show qos policy Command
~ # module vem 3 execute vemcmd show qos policy
policyid classid policerid set_type value
-------- -------- -------- -------- --------
0 1 -1 dscp 5
2 0 dscp 0
Example 17-4 module vem module-number execute vemcmd show qos pinst Command
~ # module vem 3 execute vemcmd show qos pinst
id type
-------- --------
17 Ingress
class bytes matched pkts matched
-------- -------------------- --------------------
1 0 0
2 85529 572
0
policer stats: conforming (85529, 572)
policer stats: exceeding (0, 0)
policer stats: violating (0, 0)
Debugging Policy Configuration Errors
You can debug a policy configuration failure caused by processing on the VSM.
Step 1 Enter the debug aclmgr all command if the policy references an ACL.
Step 2 Enter the debug ipqos all command.
Step 3 Enter the policy map and class commands to collect logs for all operations.
Step 4 Save the Telnet SSH session buffer to a file.
If you are debugging a policy on a port profile, it might be easier to first install it directly on an interface.
You can debug a policy configuration failure on the VEM.
Step 1 Enter the module vem module-number execute vemdpalog clear command.
Step 2 Enter the module vem module-number execute vemdpalog sfqosagent all command.
Step 3 Enter module vem module-number execute vemdpalog start command.
Step 4 Enter the policy-map command which will execute the command once again with the DPA debug traces
output to vemdpalog.
Step 5 Enter module vem module-number execute vemdpalog stop command.