Cisco Cisco Prime Network Services Controller Adaptor for DFA Troubleshooting Guide
Cisco Dynamic Fabric Automation Production Troubleshooting Guide
11
2.3.1 Do a manual pull of the profile/instance and verify it can get applied
Below is a working case of a manual (i.e. not triggered by traffic or VDP, but by the user through CLI) pull that instanti-
ates vlan 112 on port-channel interface 104 (an interface part of mobility domain PineForest):
ates vlan 112 on port-channel interface 104 (an interface part of mobility domain PineForest):
acorn1%PineForest:Tree1# fabric database auto-pull dot1q 112 interface port-channel 104
acorn1%PineForest:Tree1# show fabric database host statistics
ADBM Requests 2
ADBM Responses 2
Profile Apply Received 1
Profile vPC Queued 0
Profile Local Apply Queued 0
Profile Local UnApply Queued 0
Profile Apply Sent 1
Profile Apply Responses 5
Profile Apply Success 1
Profile Commands 4
Profile High Queue adds 1
Outstanding vlan requests 0
Outstanding adbm requests 0
Outstanding Profile Applies 0
Outstanding vPC Profile Applies 0
acorn1%PineForest:Tree1# show fabric database host dot1q 112
instance_index 0
Got Local originated vlan type trigger at 16:48:52
Number of associated interfaces: 1
Sent to Database Manager at 16:48:53
Received Parameters from Database Manager at 16:48:53
Sent to vPC peer at 16:48:54
Completed executing all commands on vPC peer at 16:48:54
Displaying Data Snooping Ports
Interface Encap Flags State