Cisco Cisco Dynamic Fabric Automation for OpenStack トラブルシューティングガイド
Cisco Dynamic Fabric Automation Production Troubleshooting Guide
38
Station: 0002.3d40.6403
Machine State: [02] VDP_BDG_INIT
Entry State: -
Reason: Could not apply profile
Recycle in: 327 sec
In certain failure scenarios, a de-associate indication may be returned directly to the Nexus 1000V switch. In those
situations, the VSI can be removed directly from the switch and it might not be possible to identify the reason with
show commands during the association attempt window.
situations, the VSI can be removed directly from the switch and it might not be possible to identify the reason with
show commands during the association attempt window.
Upon a new VM association, The EVB process notifies the HMM process that a new host is present, and also notifies
the host interface and the associated segment ID.
the host interface and the associated segment ID.
acorn3# show fabric forwarding internal event-history auto-config | i “VDP request”
2015 Nov 1 10:24:36.820927 hmm [4263]: [4268]: 31015:00000000000000007927005056B972C6 Got VDP request
(trigger: 1 id:31015 mtype: 3) on Ethernet1/26
mtype:3 indicates an association request while mtype:4 indicates a de-association request.
The following counters can be checked to see if the HMM process received VDP associations or de-
associations.
acorn3# show fabric database host statistics
..
VDP Association Requests 11
VDP DeAssociation Requests 9
…
If the profile for the segment has already been instantiated, HMM will immediately return a success notification to the
EVB process to proceed to a successful association.
EVB process to proceed to a successful association.
In case of a new segment, HMM will add a host entry to its database, keyed by the VNI/segment ID for the network in
case of segment-based VDP:
case of segment-based VDP:
acorn3# show fabric database host
Active Host Entries
flags: L - Locally inserted, V - vPC+ inserted, R - Recovered, X - xlated Vlan
VNI VLAN STATE FLAGS PROFILE(INSTANCE)
31015 1604 Profile Active L defaultNetworkUniversalEfProfile(instance_vni_31015_13)
The hmm process will then request an available VLAN from the pool of POAP defined dynamic VLANs (system fabric
dynamic-vlans).
dynamic-vlans).
The leaf switch will then query the LDAP server to retrieve the attributes and attribute values associated with the profile
that is to be applied. In case of a segment-based VDP trigger, the search key for an LDAP entry in the network data-
base will be made of the segment ID advertised by the VDP station. If necessary, the switch will proceed with retriev-
ing the tenant profile, the profile contents and will synchronize the profiles and fabric database host entry to the vPC
peer.
that is to be applied. In case of a segment-based VDP trigger, the search key for an LDAP entry in the network data-
base will be made of the segment ID advertised by the VDP station. If necessary, the switch will proceed with retriev-
ing the tenant profile, the profile contents and will synchronize the profiles and fabric database host entry to the vPC
peer.