17-6
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 17 Quality of Service
Debugging Policing Configuration Errors
Debugging Policing Configuration Errors
You can debug a policy verification 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
debug aclcomp all
command.
Step 4
Enter the
service-policy
command to execute the command once again with debug traces output to the
console.
Step 5
Save the Telnet SSH session buffer to a file.
If you are debugging a policy on a port profile, it may be easier to first install it directly on an interface.
To debug a policy verification failure on the VEM, follow these steps:
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
service-policy
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.
Step 6
Enter the
module vem
module-number
execute vemdpalog show all
command to see the logs on
console.
The output will look similar to the following:
calling add policy 81610ac len 220 classmaps 3- --> Session actions
…
Adding classmap 1 (108) with op 1 and 2 filters
…
Adding classmap 2 (116) with op 2 and 2 filters
…
Adding classmap 3 (56) with op 0 and 0 filters
…
init pinst ltl 11 policy id 0 if_index 1a020200 --> Service-policy being applied
installing pinst type 0 17 for policy 0
dpa_sf_qos_verify returned 0
…
Session commit complete and successful --> Session ending