One last thing and this is stated in the warning message above.
If it does, user traffic may be blackholed.Īfter adding the command you will see a new line when you do the “ show switch” command: TPA-SWA#sh switch WARNING: stack-mac does not appear elsewhere in this network WARNING: The Network Administrators must make sure that the old WARNING: master switchover, the current stack-mac will continue
#Mac pdf stacks problem mac#
WARNING: Stack MAC persistency timer value of 0 means that, after a You will get the warning below when you enter the command: This will keep the Mac Address of the previous Master until you enter the “ no stack-mac persistent timer”. The fix for this is to use “ stack-mac persistent timer 0” command. This will bring down your LACP Etherchannels. If the stack Master goes down, the LACP System ID can change resulting in the Etherchannel flapping and STP reconverging. So basically when you use LACP, the System ID uses the stack MAC Address from the stack master. Usually it would stay down until the Master switch is reloaded. So if you have any servers teamed with LACP interfaces, they will go down. This LACP System ID will change causing the Etherchannel to flap. This will be a problem if the Master switch goes offline. Te1/1/1 32768,1c6a.7ad3.0c80 0x136 27s SAĪctivity: Timeout: Aggregation: Synchronization:Ĭollecting: Distributing: Defaulted: Expired: Now if you look at the LACP details, you will see the Master switches Mac Address being used on both uplinks for the System ID: TPA-SWA#sh lacp internal detailįlags: S - Device is requesting Slow LACPDUsĪ - Device is in Active mode P - Device is in Passive mode
Switch# Role Mac Address Priority Version State Switch/Stack Mac Address : 1c6a.7ad3.0c80 If you look below, you will see the “ Switch/Stack Mac Address” is the Master’s.
When a switch stack forms a port-channel, the active stack member’s MAC Address is used for the LACP ID.
0 kommentar(er)
