nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Active is local
Standby is 10.10.100.3, priority 100 (expires in 7.827
sec)
Priority 200 (configured)
Weighting 100 (default 100), thresholds: lower 1, upper
100
Load balancing: round-robin
Group members:
001B.54C2.7641 (10.10.100.2) local
001B.54C2.78C1 (10.10.100.3)
There are 2 forwarders (1 active)
Forwarder 1
State is Active
2 state change(s), last state change 00:19:30
MAC address is 0007.B400.6401 (default)
Owner ID is 001B.54C2.7641
Preemption enabled, min delay 30 sec
Active is local, weighting 100
Forwarder 2
State is Listen
3 state change(s), last state change 00:00:54
MAC address is 0007.B400.6402 (learnt)
Owner ID is 001B.54C2.78C1
Redirection enabled, 597.827 sec remaining (maximum
600 sec)
Time to live: 14397.827 sec (maximum 14400 sec)
Preemption enabled, min delay 30 sec
Active is 10.10.100.3 (primary), weighting 100
(expires in 7.827 sec)
Configuring MD5 authentication is a multistep process. You must first define a keychain that
contains attributes like the password to be used to authenticate the connection and lifetime of
the key chain for both sending and receiving, as demonstrated in Example 3-125.
Example 3-125. Configuring a Keychain
Click here to view code image
Congo(config)# key chain nexus
Congo(config-keychain)# key 1
Congo(config-keychain-key)# key-string nexus
The next step is to enable authentication under the GLBP process, as demonstrated in
Example 3-126, and reference the keychain created in Example 3-125.