From time to time we receive calls into TAC about the mgmt0 interface showing as “Administratively down” from NX-OS. Since the beginning of time, this has been expected behavior due to the platform design architecture on 1st, 2nd, and 3rd Gen FI’s.
The FI switch architecture uses 2 network stacks. We use the Linux stack for eth0, a.k.a management port or mgmt0, and we use the NX-OS stack for, you guessed it, the NX-OS context. Upon FI boot, NX-OS sets the IP address for mgmt0, but it’s not used or connected to the physical interface. Because only one stack can manage the physical port, this management is done by the Linux stack. This is why we have the appearance of this “admin down” behavior.
From NX-OS, we can see that mgmt0 is “Administratively down”, and again, this is the expected behavior we’re talking about.
When we want to verify that our management port or mgmt0 is up and operational, we can check it one of two ways. We can check it from the local-mgmt context with the below command, and here we’re interested in “eth0” specifically.
Weasley-B(local-mgmt)# show mgmt-ip-debug | grep -i -A 7 "eth0" | head
A 10.X.X.X 10.X.X.X 255.255.255.0 :: :: 64 Operable
While we’re discussing the design architecture, I’ll briefly explain how CDP operates with this. Because of how these 2 stacks are implemented, we’re able to see neighbor switch information from the FI’s NX-OS context, but the FI will not share out it’s information to the neighboring management switch.
From UCS NX-OS perspective, we see what's displayed below, and notice how we’re able to see the Mgmt-SW. When running a “show cdp neighbors” from Mgmt-SW, we will not see UCS FI information, which is expected.
Weasley-B(nxos)# show cdp neighbors
Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
S - Switch, H - Host, I - IGMP, r - Repeater,
V - VoIP-Phone, D - Remotely-Managed-Device,
s - Supports-STP-Dispute
Device-ID Local Intrfce Hldtme Capability Platform Port ID
Hello,I just picked up two C200 M1 machines second hand, and have run into an issue. I tested both before I purchased them, and they both POST'd fine so I purchased them. When I got them home I powered up one of them up. It was doing fine but seemed to st...
I have a customer that is looking to replace their 6296UP FIs with the new 6332-16UP model along with the 2304 IOMs.I found this guide - Migrating to UCS 6300 Series Fabric Interconnects and the UCS 2304 IOM The guide isn't quite as detail...