Debugging Policy Verification Failures - Cisco Nexus 1000V Troubleshooting Manual

Chapter 17 Quality of Service
Enter the module vem module-number execute vemdpalog show all command to display the logs on
the console.
The policy gets added first
add plcy node - calling add policy 8eb5c20 sf_qos_policy_len(policy) 4 classmaps 0, Policy
name <p_name>
This will be followed by addition of class-map filter nodes. Please note that the same is
done via multiple sessions. Hence there could be a replace policy , before the addition of
filter nodes.
A noticeable thing in the log is the class-map counter could be updated.
replace plcy node - calling replace policy 8eb47d8 sf_qos_policy_len(policy) 92 classmaps
1, Policy <p_name>
...
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
...
Every session should end with the log
Debug qosagent: Session commit complete and successful

Debugging Policy Verification Failures

You can debug a policy verification failure on VEM.
Enter the module vem module-number execute vemdpalog clear command.
Step 1
Enter the module vem module-number execute vemdpalog sfqosagent all command.
Step 2
Enter the module vem module-number execute vemdpalog start command.
Step 3
Enter the service-policy command to execute the command once again with the DPA debug traces output
Step 4
to vemdpalog.
Enter the module vem module-number execute vemdpalog stop command.
Step 5
Enter the module vem module-number execute vemdpalog show all command to display the logs on
Step 6
console.
The VEM-side output logs contain the following:
add pinst - add_pinst policy_id 0
add pinst - add_pinst gpolicy_id 72352041
verify - installing pinst type 0 49 for policy 0
verify - returned 0
commit - adding pinst ltl 49 use 2 to policy 0
Session commit complete and successful
OL-31593-01
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
Debugging Policy Verification Failures
17-5