Cisco Cisco Dynamic Fabric Automation for OpenStack Troubleshooting Guide

Cisco Dynamic Fabric Automation Production Troubleshooting Guide 
 

 

to support routing tenant traffic within or between VN segments. Any L2 traffic with proper dot1Q tagging can drive 
profile instantiation.  

We can track the auto-profile instantiation steps in sequence. Be aware that NX-OS event-history outputs are in re-
verse chronological order. The host-learning event must be put into a “Profile Wait” state while the initial network and 
partition profiles query and auto-configuration process completes. 

1.  Interesting dot1q tagged Layer-2 frame is received by HMM process 

2.  Check global profile-map for ether-tag match will fail as using dynamic-profile 
3.  No local profile found in local database for given dot1q tag and mobility domain 

4.  Query ADBM database for profile matching mobility domain and dot1q tag 

5.  Leaf receives profile parameters from ADBM and installs in local profile database 

6.  Profile instantiation occurs on the local leaf 

 

This sequence of events can be viewed in detail with the following event-history command.  

Process auto-config logs of HMM 

2015 Nov 11 19:13:25.823754 hmm [4660]: [4662]: Updating with keys: seg-id 0,bd 100 and Profile de-

faultNetworkUniversalEfProfile(instance_1) state 2 parameterized 1 recovery 0 

2015 Nov 11 19:13:25.823738 hmm [4660]: [4662]: Get instance - Could not find profile  with instance 0 

2015 Nov 11 19:13:25.823730 hmm [4660]: [4662]: [100] Host entry has the include-vrf name sein-

feld:vandelay 

2015 Nov 11 19:13:25.823726 hmm [4660]: [4662]: [100] ADBM Mark to-do query flags [01001010] : parti-

tion 

2015 Nov 11 19:13:25.823695 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $mtuValue= 

2015 Nov 11 19:13:25.823687 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $prefixLength=64 

2015 Nov 11 19:13:25.823678 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $gatewayIpv6Address=2000:aaaa::1 

2015 Nov 11 19:13:25.823671 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $vrfDhcp= 

2015 Nov 11 19:13:25.823663 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $dhcpServerAddr= 

2015 Nov 11 19:13:25.823655 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $netMaskLength=24 

2015 Nov 11 19:13:25.823647 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $gatewayIpAddress=20.10.100.1 

2015 Nov 11 19:13:25.823638 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $vrfName=seinfeld:vandelay 

2015 Nov 11 19:13:25.823580 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $netMaskLength=24 

2015 Nov 11 19:13:25.823544 hmm [4660]: [4662]: [100] ADBM Receive [ADD] Entry: PARENT, DB: NETWORK, 

Profile Parameter: $gatewayIpAddress=20.10.100.1