But, this command just mean that the switch with priority of 1 will be not elected as master if other switch with higher priority exist in the stack. This could cause problems if, for example, we reboot the Master. The switch with priority of one was elected as master. And because this switch is an "SMI" version, we lost the "EMI" functionnality.
So my question is, is it possible to force it to never become the Master? We prefer to lost for a short time (the reboot time) the connection, than to lost the "EMI" functionnality.
But wouldn't the EMI switch cause a stack re-election if the power was cycled? In this case you would only have the SMI as master during the reboot of the EMI switch. You say that you would rather lose connectivity all together rather than lose EMI functionality. I don't understand why though? In either case you have lost your layer 3 functions right?
The system-level features supported on the stack master are supported on the entire switch stack. If the switch stack must have switches running both standard multilayer image (SMI) and enhanced multilayer image (EMI) software, we recommend that a switch running the EMI software be the stack master. EMI features are unavailable if the stack master is running the SMI software.
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 ...