Smarts IP: Nexus switch has 3 sub-VDC's but following a discovery only one VDC is discovered; sub VDC's are not discovered for Nexus devices.
Article ID: 331735
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
The nexus switch has 3 sub-VDC's but following a discovery only one VDC is discovered :
On the switch we see:
The following steps were followed to configure and discover the VDCs:
1) Enable the flag EnableVirtualDataContextDiscovery in tpmgr-param.conf file controls VDC discovery.
Default Value=TRUE
2) Provide the read-only or Administrator VDC credentials under the CLI Access Group in
Polling and Threshold -> Device Access.
3) Discover all the VDC devices using their IP addresses.
4) Discovery will create Switch(Main Switch)->ComposedOf->Switch(Child Switch) relationship.
5) Relationships are created based on the Child Switch Mac address and Sub-VDC Mac address available in Main VDC Device.
6) Device is certified using CONT = Cisco-Nexus-VDC-CLI
The nexus switch has 3 sub-VDC's but following a discovery only one VDC is discovered :
On the switch we see:
switch667North-admin# sh vdc
Switchwide mode is f2e f3
vdc_id vdc_name state mac type lc
------ -------- ----- ---------- --------- ----------------------------------------------------
1 switch667North-admin active 00:2a:6a:b6:f3:91 Admin None
2 switch667South active 00:2a:6a:b6:f3:92 Ethernet f2e f3
3 switch667East active 00:2a:6a:b6:f3:93 Ethernet f2e f3
4 switch667West active 00:2a:6a:b6:f3:94 Ethernet f2e f3
vdc_id vdc_name state mac type lc
------ -------- ----- ---------- --------- ----------------------------------------------------
1 switch667North-admin active 00:2a:6a:b6:f3:91 Admin None
2 switch667South active 00:2a:6a:b6:f3:92 Ethernet f2e f3
3 switch667East active 00:2a:6a:b6:f3:93 Ethernet f2e f3
4 switch667West active 00:2a:6a:b6:f3:94 Ethernet f2e f3
The following steps were followed to configure and discover the VDCs:
1) Enable the flag EnableVirtualDataContextDiscovery in tpmgr-param.conf file controls VDC discovery.
Default Value=TRUE
2) Provide the read-only or Administrator VDC credentials under the CLI Access Group in
Polling and Threshold -> Device Access.
3) Discover all the VDC devices using their IP addresses.
4) Discovery will create Switch(Main Switch)->ComposedOf->Switch(Child Switch) relationship.
5) Relationships are created based on the Child Switch Mac address and Sub-VDC Mac address available in Main VDC Device.
6) Device is certified using CONT = Cisco-Nexus-VDC-CLI
Environment
VMware Smart Assurance - SMARTS
Cause
From the logs, we can see the following:
The MAC "00-2A-6A-B6-F3-91" was not found and its not part of any system, hence ignore. And more over this MAC is supposed to belong to the Admin VDC switch. So lets skip this.
The MAC "00-2A-6A-B6-F3-92" was found to be associated to the Switch : switch667North-admin-switch667South
The MAC "00-2A-6A-B6-F3-93" was not found to be associated to any Switch.
The MAC "00-2A-6A-B6-F3-94" was not found to be associated to any Switch.
From the above findings, only the MAC "00-2A-6A-B6-F3-92" appears to be associated to the switch "switch667North-admin-switch667South" and hence this switch will be part of the Admin switch.
The rest of the switch that is supposed to host the MAC (i.e 00-2A-6A-B6-F3-93 and 00-2A-6A-B6-F3-94) is not part of the topology and hence they were not part of the composedOf relationship with the admin VDC switch.
The MAC "00-2A-6A-B6-F3-91" was not found and its not part of any system, hence ignore. And more over this MAC is supposed to belong to the Admin VDC switch. So lets skip this.
The MAC "00-2A-6A-B6-F3-92" was found to be associated to the Switch : switch667North-admin-switch667South
The MAC "00-2A-6A-B6-F3-93" was not found to be associated to any Switch.
The MAC "00-2A-6A-B6-F3-94" was not found to be associated to any Switch.
From the above findings, only the MAC "00-2A-6A-B6-F3-92" appears to be associated to the switch "switch667North-admin-switch667South" and hence this switch will be part of the Admin switch.
The rest of the switch that is supposed to host the MAC (i.e 00-2A-6A-B6-F3-93 and 00-2A-6A-B6-F3-94) is not part of the topology and hence they were not part of the composedOf relationship with the admin VDC switch.
Resolution
The sub VDCs needs to be part of the topology.
If they are part of the topology, then check the switch configuration to see why Sub VDC MAC is not associated with the respective switch as it is with the the sub vdc switch "switch667South".
i.e. the MAC address ending in 92 , is configured correctly (its associated with a switch)
Therefore, check the configuration of the remaining MAC address and make sure they are associated with a switch
Once this is completed and a rediscovery done, you should something similar to the following:
If they are part of the topology, then check the switch configuration to see why Sub VDC MAC is not associated with the respective switch as it is with the the sub vdc switch "switch667South".
i.e. the MAC address ending in 92 , is configured correctly (its associated with a switch)
Therefore, check the configuration of the remaining MAC address and make sure they are associated with a switch
Once this is completed and a rediscovery done, you should something similar to the following:
Feedback
Yes
No
Powered by
