I have a nexus 7000 with two Supervisor engines. One is Active and the other one is Hot-Standby. I have connected the management ports from each supervisor engines to Catalyst 3750 Switch.
The management connections MGMT0 (copper connections) coming from Active supervisor engine to 3750 Switch is showing up and connected.
SwitchA#sh int gigabitEthernet 1/0/7 GigabitEthernet1/0/7 is up, line protocol is up (connected)
However the management connections MGMT 0(copper connections) coming from Standby supervisor engine to 3750 Switch is showing down.
SwitchB#sh int GigabitEthernet 1/0/40 GigabitEthernet1/0/40 is down, line protocol is down (notconnect)
Is this the way it should behave ? I am trying to failover the supervisor engines as i am upgrading the code in Nexus 7k. Once i failover, will the copper connections coming from standby sup will be up and connected ? Else i will lose my management connectivity to the Nexus 7000. Please let me know if you have experienced something like this.
That is the correct behavior. As long as the primary sup is up, you will see the mgmt0 for the primary Sup up. The second you fail over to the stand-by sup, the mgmt0 for that sup will come up and the old primary will go down. So, it is only one mgmt0 is up at a time.
Make sure both mgmt0 interfaces are in the same vlan and also port fast is turned on so the mgmt ports comes up as soon as possible.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...