Loading...
Loading...
MDS fabric discovered in DCNM - NPV switches connected to MDS using NP port channels. DCNM shows some but not all NPV switches in the switch list. DCNM " SAN/Fabrics/ISL/Statistics " view some but not all NPV switches in the list. NPV devices concerned are the following: N9K-C93180YC-FX running firmware n9000-15.3(2b) DCNM hardware matrix confirms devices supported: https://www.cisco.com/c/en/us/td/docs/dcn/dcnm/1154/release-notes/cisco-dcnm-release-notes-1154/supported_hardware.html ( External Link )
Compared working and non-working devices OUI Working NPV device: 20:0a: ac:4a:67 :bc:97:da Non-working OUI: 20:0a: cc:d3:42 :f6:af:9a 20:0a :bc:8d:1f :46:b4:7a Verified DCNM server.properties file in DCNM webGUI Section on the new OUI: # Add new OUIs for discovering switch, end device with format: # 0xhhhhhh vendor_name devicetypes h(host)|d(disk)|t(tape)|g(gateway)|m(cisco mds/nexus/ucs switch)|s(3rd party switch)) # for example: newOUIs=0x00E069 JNI h|d; 0x000ded Cisco m;\ # 0x006069 Brocade s; newOUIs=0xac4a67 Cisco m fmserver.log from the DCNM server confirms the issue: INFO [fms.disc] <ip address> fcns entry cannot be identified as NPV device because of the unknown wwn:20:0a:cc:d3:42:f6:af:9a; please add the new OUI to server.properties->newOUIs as permanent one.
Added new entries in the DCNM server.properties file viaDCNM webGUI to include the missing devices OUI as follows: newOUIs=0xac4a67 Cisco m;0xccd342 Cisco m; 0xccd342 Cisco m
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.