OPERATIONAL DEFECT DATABASE
...
...
Nexus 93180YC-FX may show discrepancies in the vsan database configuration in the outputs of commands *show running-config* and *show startup-config* after a VXLAN overlay profile is configured on the switch. It's observed that the configuration where fiber channel interfaces are added to the vsan database, goes missing. The configuration command that triggers the discrepancy is *configure profile* . The actual vsan membership of the ports stays unaffected. You may see such discrepancies in the running and startup config, adding an example here: Before the profile is configure: *nexus9k# show run | i vsan* *vsan database* *vsan xxx interface fc1/37* *vsan xxx interface fc1/38* Configuring the overlay profile: *nexus9k# configure profile* After the policy is applied : *nexus9k# show run | i vsan* *vsan database* *vsan xxx interface fc1/37* The actual vsan membership of the interfaces remains unchanged : *nexus9k# sh vsan membership* *vsan 1 interfaces:* *vsan xxx interfaces:* *fc1/37 fc1/38*
This behaviour has been observed on Nexus 93180YC-FX running NX-OS 9.3(10) and is in NPV mode. NPV config command : *feature npv* It's observed that the FC ports affected by the discrepancy are unified fiber channel interfaces.
None at the moment
*Resolution summary* To be determined once resolved.
Cisco 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.
