Network Visualization with Cisco Nexus 9K Switches | Nutanix Community
Skip to main content
Question

Network Visualization with Cisco Nexus 9K Switches

SteveNutter
Forum|alt.badge.img
Hello ... can anyone provide feedback on getting Network Visualization working with Cisco Nexus 9K Switches. The Nexus Series is on the Supported Switch list, but I've had a ticket open with Support for weeks and we can't get it working.
https://portal.nutanix.com/#/page/docs/details?targetId=Web-Console-Guide-Prism-v510:wc-network-visualizer-supported-switches-r.html

LLDP is enabled globally on the 9K, and I can populate the 9K switch info into Prism just fine. The issue is I can't get any port data. Nutanix Support is saying the issue is by default the "port-id-subtype" is set "locally-assigned", and it needs to be changed to "interface-name". The 9Ks are in ACI-Mode, not NX-OS, and no one seems to know how or where the change is made. Has anyone gotten this setup to work? Here are some pics from my environment. Thanks!

4 replies

S
  • StuartB
  • Voyager
  • 2 replies
  • December 17, 2019

Hi, did you ever get this sorted?  We’re having the same issue, displays perfectly on our DR site (with 5K’s), no port details on the 9K’s on our primary site.

Alona
Nutanix Employee
Forum|alt.badge.img+5
  • AlonaNutanix Employee
  • Nutanix Employee
  • 432 replies
  • December 23, 2019

@StuartB 

To the best of my knowledge, this was fixed in AOS 5.5. Could you please confirm the version of the affected site?

S
  • StuartB
  • Voyager
  • 2 replies
  • January 2, 2020

Hi @Alona - We are running AOS 5.11.2.  I believe this worked okay when we first switched to the 9K’s (on 5.10), but hasn’t worked since we upgraded to 5.11.

I have now got it displaying correctly by switching to SNMPv2 - problem exists if we try and use SNMPv3.

C
Forum|alt.badge.img+2
  • Charu
  • Trailblazer
  • 18 replies
  • October 6, 2020

@SteveNutter Can you please visit https://portal.nutanix.com/page/documents/kbs/details?targetId=kA032000000TVfiCAG and search for Workaround for Issue #1.

Reply


Terms & Conditions