Skip to main content
Open

Support for Cisco VDC

Related products:Discovery
  • September 8, 2021
  • 6 replies
  • 51 views

Usually, when discovering devices you use the mgmt IP which is fine for most devices. Cisco Nexus support VDC and when you discover via the mgmt IP, you only get the admin context but not the important stuff from the productive contexts.
Adding the command show running-config vdc-all will provide the missing information.
Of course, this information will also require analysis and interpretation, adding IPs, routing etc.

6 replies

Forum|alt.badge.img+4
  • Author
  • Brainy
  • 82 replies
  • September 8, 2021

Forum|alt.badge.img+1
  • Community Manager
  • 85 replies
  • September 9, 2021

@Carsten.Schmidt  I think we should support to discover the Non-default VDC via their independent management IP or via the default VDC.  Could you submit a ticket via portal so that we can have a check? Please include the IP or hostname of the device if possible.

 

Thanks,

Gerry 


Forum|alt.badge.img+4
  • Author
  • Brainy
  • 82 replies
  • September 10, 2021

@Gerry.zhang discovery via mgmt IP of the other contexts works but this creates a new device. Depending on the environment you have, if you work with many virtual contexts this will have a very negative effect on your node license situation. I do not even want to think about how NB will present the routing, L2 and L3 connectivity when a physical device is separated into many devices/nodes when they are only virtual parts of a physical device.


Forum|alt.badge.img+1
  • Community Manager
  • 85 replies
  • September 10, 2021

Understand, i can help you to file a feature request to it if you would like to show it as a single device.


Forum|alt.badge.img+4
  • Author
  • Brainy
  • 82 replies
  • September 10, 2021

Case 00134396


Forum|alt.badge.img+1
  • Community Manager
  • 85 replies
  • September 10, 2021

Thanks, we will continue to follow up with you on the case.