Would modifying an LACP sharing port cause an outage?

[Keith9]

I have a 5 stack 5520 switch with 4 links to two X690's at the core.  Its currently configured like so:

enable sharing 1:57 grouping 1:57,2:57,4:57,5:57 algorithm address-based L3_L4 lacp

We are working on a switch consolidation project to reclaim switch 5 for another site that only has a single 24 port 5520 and is almost out of ports.  In doing so I want to move the 10 gig link in sharing port group 1:57 from 5:57 to 3:57.  Can I just run this command:
enable sharing 1:57 grouping 1:57,2:57,3:57,4:57 algorithm address-based L3_L4 lacp

without causing an outage?  Then I would move my sfp+ and cable from 5:57 to 3:57 after thats complete.

[Keith9 · Accepted solution]

Ok I was able to do it with no outage.  This is what I did...

configure sharing 1:57 add ports 3:57

This added to the sharing group, so its a 5 port lag.

I then physically moved the cable.  Checked logs all is good.

Then I removed 5:57 with this:

configure sharing 1:57 delete ports 5:57

Then sh sharing proves the new group is moved.

sh sharing
Load Sharing Monitor
Config Current Agg Min Ld Share Ld Share Agg Link Link Up
Master Master Control Active Algorithm Flags Group Mbr State Transitions
================================================================================
1:57 1:57 LACP 1 L3_L4 A 1:57 Y A 1
L3_L4 2:57 Y A 1
L3_L4 3:57 Y A 1
L3_L4 4:57 Y A 2
================================================================================

Finally altered port descriptions to our specs and were good so far.

The next challenge will be to see if we can remove switch 5 from the stack without causing any downtime.  Right now switch 4 goes to switch 5 and then switch 5 has a cable that loops back up to switch 1.  I see a KB on this, I just have to read it very carefully.

sh stacking
Stack Topology is a Ring
Active Topology is a Ring
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*f0:64:26:81:a4:00 1 Active Master CA-
f0:64:26:81:f4:00 2 Active Backup CA-
f0:64:26:82:20:00 3 Active Standby CA-
f0:64:26:84:98:00 4 Active Standby CA-
40:88:2f:ea:a0:00 5 Active Standby CA-
* - Indicates this node
Flags: (C) Candidate for this active topology, (A) Active Node
(O) node may be in Other active topology

[FredrikB-NN2]

Stacking in EXOS can be a bit ... iffy. Make sure you monitor the free memory as memory leaks related to stacking has been a problem in lots of EXOS releases and the primary cause for crashes. Oddities like the one you describe are not too common, but happen.

Your LAG/LACP approach seems fine. In the past you could also configure LAGs to push the packet out on a local port in the stack if one was available, but I cannot seem to find that now.

configure sharing master_port distribution-mode local-slot

If a frame comes in on port 1:1 and is destined for your LAG on ports x:57, it would always go out on 1:57 as that port is in the same slot. Only if there is no "local" LAG port po put the packet on will it be hashed among the other ports in the LAG, causing traffic on the stacking ports. Without this "local-slot", you will very often have your traffic go via the stacking ports, causing latency and, if you have a lot of traffic, congestion on the stacking ports.

Perhaps this has been deprecated?

[Bill_Handler]

Keith,

I don’t think that will work since 1:57 is already set as a sharing group.  Depending on your firmware you may be able to use the command:

configure sharing 1:57 add port 3:57

However, I’m not sure if you can delete port 5:57 with a similar command….

thanks,

Bill

[Keith9 · Accepted solution]

Ok I was able to do it with no outage.  This is what I did...

configure sharing 1:57 add ports 3:57

This added to the sharing group, so its a 5 port lag.

I then physically moved the cable.  Checked logs all is good.

Then I removed 5:57 with this:

configure sharing 1:57 delete ports 5:57

Then sh sharing proves the new group is moved.

sh sharing
Load Sharing Monitor
Config Current Agg Min Ld Share Ld Share Agg Link Link Up
Master Master Control Active Algorithm Flags Group Mbr State Transitions
================================================================================
1:57 1:57 LACP 1 L3_L4 A 1:57 Y A 1
L3_L4 2:57 Y A 1
L3_L4 3:57 Y A 1
L3_L4 4:57 Y A 2
================================================================================

Finally altered port descriptions to our specs and were good so far.

The next challenge will be to see if we can remove switch 5 from the stack without causing any downtime.  Right now switch 4 goes to switch 5 and then switch 5 has a cable that loops back up to switch 1.  I see a KB on this, I just have to read it very carefully.

sh stacking
Stack Topology is a Ring
Active Topology is a Ring
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*f0:64:26:81:a4:00 1 Active Master CA-
f0:64:26:81:f4:00 2 Active Backup CA-
f0:64:26:82:20:00 3 Active Standby CA-
f0:64:26:84:98:00 4 Active Standby CA-
40:88:2f:ea:a0:00 5 Active Standby CA-
* - Indicates this node
Flags: (C) Candidate for this active topology, (A) Active Node
(O) node may be in Other active topology

[Keith9 · Accepted solution]

I removed slot 5 from the stack following these instructions:

https://extreme-networks.my.site.com/ExtrArticleDetail?an=000081255

Overall it worked but I'm glad I waited till most everyone was out of the office.  Slot 5 removed fine and I recabled it, and at first slots 1-4 seemed ok, but after I did unconfigure slot 5, something happened to slot 2 where its state went unknown and ports 2:1-48 and 2:57 were down.  So I did a reboot slot 2 and when it came up everything seems ok again.  Weird that removing slot 5 caused slot 2 to crash.

11/15/2023 17:38:20.34 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 4:38 link down
11/15/2023 17:32:52.12 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
11/15/2023 17:30:16.12 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:48 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:30:08.39 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:48 link down
11/15/2023 17:29:37.99 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:48 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:29:13.44 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:45 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:29:11.29 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:37 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:29:11.06 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:45 link down
11/15/2023 17:29:10.97 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:36 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:29:08.87 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:37 link down
11/15/2023 17:29:08.47 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:36 link down
11/15/2023 17:29:04.19 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:9 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:29:03.19 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:5 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:29:01.84 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:9 link down
11/15/2023 17:29:00.78 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:5 link down
11/15/2023 17:28:58.53 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:45 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:28:56.58 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:37 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:28:56.18 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:36 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:28:49.70 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:9 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:28:49.31 <Noti:DM.Notice> Slot-1: Backup is in SYNC
11/15/2023 17:28:48.49 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:5 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:28:28.53 <Info:cli.logRemoteCmd> Slot-1: 10.7.3.12 (ssh) user.admin: save
11/15/2023 17:28:09.89 <Warn:log.NVRAMFull> Slot-2: NVRAM is full, old messages are overwritten.
11/15/2023 17:28:09.89 <Warn:STP.DomainEnable> Slot-2: STP domain s0 enabled
11/15/2023 17:28:04.04 <Info:AAA.LogSsh> Slot-1: Msg from Backup : 1675 of 1675 bytes written to SSH System Config
11/15/2023 17:28:03.96 <Info:AAA.LogSsh> Slot-1: Msg from Standby Slot 4: 1675 of 1675 bytes written to SSH System Config
11/15/2023 17:28:03.95 <Info:AAA.LogSsh> Slot-1: Msg from Standby Slot 3: 1675 of 1675 bytes written to SSH System Config
11/15/2023 17:28:02.48 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:7 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:28:00.64 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:7 link down
11/15/2023 17:28:00.57 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:7 link UP at speed (down) and half-duplex
11/15/2023 17:27:46.49 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:41 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:46.42 <Info:HAL.Sys.Info> Slot-1: Input voltage to Internal PSU-2 in slot 2 is on. Output enabled.
11/15/2023 17:27:46.42 <Info:HAL.Sys.Info> Slot-1: Internal PSU-2 in slot 2 is present.
11/15/2023 17:27:46.42 <Info:HAL.Sys.Info> Slot-1: Input voltage to Internal PSU-1 in slot 2 is on. Output enabled.
11/15/2023 17:27:46.42 <Info:HAL.Sys.Info> Slot-1: Internal PSU-1 in slot 2 is present.
11/15/2023 17:27:46.14 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:12 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:46.09 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:1 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:45.99 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:18 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:45.93 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:6 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:45.89 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:2 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:43.29 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:41 link down
11/15/2023 17:27:43.01 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:2 link down
11/15/2023 17:27:42.99 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:1 link down
11/15/2023 17:27:42.92 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:18 link down
11/15/2023 17:27:42.91 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:12 link down
11/15/2023 17:27:42.89 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:6 link down
11/15/2023 17:27:42.07 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:41 link UP at speed 10 Mbps and full-duplex
11/15/2023 17:27:41.89 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:2 link UP at speed 10 Mbps and full-duplex
11/15/2023 17:27:41.80 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:18 link UP at speed 10 Mbps and full-duplex
11/15/2023 17:27:41.77 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:1 link UP at speed 10 Mbps and full-duplex
11/15/2023 17:27:41.68 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:12 link UP at speed 10 Mbps and full-duplex
11/15/2023 17:27:41.65 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:6 link UP at speed 10 Mbps and full-duplex
11/15/2023 17:27:41.58 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:46 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:41.50 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:30 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:41.33 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:21 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:41.31 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:16 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:41.28 <Info:LACP.AddPortToAggr> Slot-1: Add port 2:57 to aggregator
11/15/2023 17:27:41.20 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:57 link UP at speed 10 Gbps and full-duplex
11/15/2023 17:27:41.14 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:10 link UP at speed 1 Gbps and full-duplex
11/15/2023 17:27:40.54 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:47 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.50 <Info:vlan.dbg.info> Slot-1: Media Q+CR4_.5m is inserted into Port 2:53
11/15/2023 17:27:40.50 <Info:vlan.dbg.info> Slot-1: Media Q+CR4_.5m is inserted into Port 2:49
11/15/2023 17:27:40.49 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:44 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.45 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:43 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.42 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:42 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.40 <Info:vlan.dbg.info> Slot-1: Media SF+_SR is inserted into Port 2:57
11/15/2023 17:27:40.38 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:32 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.25 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:20 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.22 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:14 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.19 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:4 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.11 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:8 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:40.03 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 2:3 link UP at speed 100 Mbps and full-duplex
11/15/2023 17:27:37.30 <Info:HAL.Card.Info> Slot-1: Module in Slot-2 is operational
11/15/2023 17:27:36.35 <Warn:cm.configNotInSync> Slot-1: Backup node has different configuration files than primary node. Auto configuration file synchronization will be performed.
11/15/2023 17:27:34.26 <Info:HAL.IPv4ACL.Info> Slot-1: Done synching ACLs to Slot-2
11/15/2023 17:27:33.55 <Info:HAL.IPv4ACL.Info> Slot-1: Synching ACLs to Slot-2
11/15/2023 17:27:33.55 <Info:HAL.IPv4ACL.Info> Slot-1: Done synching ACLs to Slot-2
11/15/2023 17:27:33.08 <Info:HAL.IPv4ACL.Info> Slot-1: Synching ACLs to Slot-2
11/15/2023 17:27:27.34 <Noti:DM.Notice> Slot-1: Slot-2 being Powered ON
11/15/2023 17:27:03.34 <Info:HAL.Card.Info> Slot-1: Module in Slot-2 is inserted
11/15/2023 17:27:02.38 <Info:HAL.Port.Info> Slot-1: Stacking port 2:2 link up at 40Gbps.
11/15/2023 17:27:02.38 <Info:HAL.Port.Info> Slot-1: Stacking port 2:1 link up at 40Gbps.
11/15/2023 17:26:58.84 <Info:HAL.Port.Info> Slot-1: Stacking port 3:1 link up at 40Gbps.
11/15/2023 17:26:58.84 <Info:HAL.Port.Info> Slot-1: Stacking port 1:2 link up at 40Gbps.
11/15/2023 17:25:00.84 <Info:HAL.Port.Info> Slot-1: Stacking port 3:1 link down.
11/15/2023 17:25:00.84 <Info:HAL.Port.Info> Slot-1: Stacking port 2:2 link down.
11/15/2023 17:25:00.84 <Info:HAL.Port.Info> Slot-1: Stacking port 2:1 link down.
11/15/2023 17:25:00.67 <Info:HAL.Port.Info> Slot-1: Stacking port 1:2 link down.
11/15/2023 17:24:58.34 <Info:HAL.Card.Info> Slot-1: Slot-2 down, resetting all TCP connections to it
11/15/2023 17:24:58.34 <Info:HAL.Card.Info> Slot-1: Module in Slot-2 is removed
11/15/2023 17:24:56.60 <Info:cli.logRemoteCmd> Slot-1: 10.7.3.12 (ssh) user.admin: reboot slot 2
11/15/2023 17:24:52.37 <Info:HAL.Card.Info> Slot-1: Module in Slot-2 is inserted
11/15/2023 17:24:50.84 <Info:HAL.Port.Info> Slot-1: Stacking port 2:2 link up at 40Gbps.
11/15/2023 17:24:50.84 <Info:HAL.Port.Info> Slot-1: Stacking port 2:1 link up at 40Gbps.
11/15/2023 17:24:47.84 <Info:HAL.Port.Info> Slot-1: Stacking port 3:1 link up at 40Gbps.
11/15/2023 17:24:47.84 <Info:HAL.Port.Info> Slot-1: Stacking port 1:2 link up at 40Gbps.
11/15/2023 17:23:05.92 <Noti:DM.Notice> Slot-1: Transitioning slot 2 to UNKNOWN rather than FAIL
11/15/2023 17:22:54.50 <Noti:DM.Notice> Slot-1: Previous message repeated 23 additional times in the last 11 second(s)
11/15/2023 17:22:54.42 <Noti:DM.Notice> Slot-1: Transitioning slot 2 to UNKNOWN rather than MASTER
11/15/2023 17:22:42.92 <Noti:DM.Notice> Slot-1: Previous message repeated 47 additional times in the last 12 second(s)
11/15/2023 17:22:42.79 <Info:cli.logLocalCmd> Slot-1: clearflow expy: enable snmp access v1v2c-internal
11/15/2023 17:22:42.42 <Noti:DM.Notice> Slot-1: Transitioning slot 2 to UNKNOWN rather than MASTER
11/15/2023 17:22:35.92 <Noti:DM.Notice> Slot-1: Previous message repeated 26 additional times in the last 7 second(s)
11/15/2023 17:22:35.85 <Info:cli.logRemoteCmd> Slot-1: 10.7.3.12 (ssh) user.admin: save
11/15/2023 17:22:35.42 <Noti:DM.Notice> Slot-1: Transitioning slot 2 to UNKNOWN rather than MASTER
11/15/2023 17:22:32.42 <Noti:DM.Notice> Slot-1: Previous message repeated 6 additional times in the last 2 second(s)
11/15/2023 17:22:32.32 <Noti:DM.Notice> Slot-1: Transitioning slot 2 to UNKNOWN rather than BACKUP
11/15/2023 17:22:28.82 <Noti:DM.Notice> Slot-1: Previous message repeated 7 additional times in the last 3 second(s)
11/15/2023 17:22:28.78 <Info:LACP.RemPortFromAggr> Slot-1: Remove port 2:57 from aggregator
11/15/2023 17:22:28.78 <Info:vlan.dbg.info> Slot-1: Port 2:57 is Down, remove from aggregator 1:57
11/15/2023 17:22:28.78 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:57 link down
11/15/2023 17:22:28.69 <Warn:DM.Warning> Slot-4: BACKUP NODE (Slot-2) DOWN
11/15/2023 17:22:28.69 <Warn:DM.Warning> Slot-3: BACKUP NODE (Slot-2) DOWN
11/15/2023 17:22:28.68 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:48 link down
11/15/2023 17:22:28.67 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:47 link down
11/15/2023 17:22:28.63 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:46 link down
11/15/2023 17:22:28.63 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:45 link down
11/15/2023 17:22:28.61 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:44 link down
11/15/2023 17:22:28.58 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:43 link down
11/15/2023 17:22:28.57 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:42 link down
11/15/2023 17:22:28.53 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:41 link down
11/15/2023 17:22:28.48 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:37 link down
11/15/2023 17:22:28.48 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:36 link down
11/15/2023 17:22:28.43 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:32 link down
11/15/2023 17:22:28.43 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:30 link down
11/15/2023 17:22:28.41 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:21 link down
11/15/2023 17:22:28.40 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:20 link down
11/15/2023 17:22:28.32 <Noti:DM.Notice> Slot-1: Transitioning slot 2 to UNKNOWN rather than BACKUP
11/15/2023 17:22:28.31 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:18 link down
11/15/2023 17:22:28.31 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:16 link down
11/15/2023 17:22:28.30 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:14 link down
11/15/2023 17:22:28.30 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:12 link down
11/15/2023 17:22:28.19 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:10 link down
11/15/2023 17:22:28.19 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:9 link down
11/15/2023 17:22:28.19 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:8 link down
11/15/2023 17:22:28.18 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:7 link down
11/15/2023 17:22:28.15 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:6 link down
11/15/2023 17:22:28.13 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:5 link down
11/15/2023 17:22:28.12 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:4 link down
11/15/2023 17:22:28.06 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:3 link down
11/15/2023 17:22:28.05 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:2 link down
11/15/2023 17:22:28.01 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 2:1 link down
11/15/2023 17:22:28.01 <Warn:DM.Warning> Slot-1: BACKUP NODE (Slot-2) DOWN
11/15/2023 17:22:27.97 <Erro:HAL.Card.Error> Slot-1: halGetHwPortMapping: Unable to get slot tree node for slot 5
11/15/2023 17:22:27.67 <Erro:HAL.Card.Error> Slot-1: Previous message repeated 205 additional times in the last 1 second(s)
11/15/2023 17:22:27.67 <Info:HAL.Sys.Info> Slot-1: Internal PSU-2 in slot 2 is disconnected.
11/15/2023 17:22:27.67 <Info:HAL.Sys.Info> Slot-1: Internal PSU-1 in slot 2 is disconnected.
11/15/2023 17:22:27.63 <Info:HAL.Card.Info> Slot-1: Module in Slot-2 is removed
11/15/2023 17:22:27.48 <Warn:DM.Warning> Slot-1: BACKUP is NOT in SYNC
11/15/2023 17:22:27.47 <Info:HAL.Port.Info> Slot-1: Stacking port 3:1 link down.
11/15/2023 17:22:27.47 <Info:HAL.Port.Info> Slot-1: Stacking port 2:2 link down.
11/15/2023 17:22:27.47 <Info:HAL.Port.Info> Slot-1: Stacking port 2:1 link down.
11/15/2023 17:22:27.41 <Info:HAL.Card.Info> Slot-1: Slot-2 down, resetting all TCP connections to it
11/15/2023 17:22:27.41 <Info:HAL.Card.Info> Slot-1: Module in Slot-2 is removed
11/15/2023 17:22:27.41 <Info:HAL.Port.Info> Slot-1: Stacking port 1:2 link down.
11/15/2023 17:22:21.03 <Erro:HAL.Card.Error> Slot-2: halGetHwPortMapping: Unable to get slot tree node for slot 5
11/15/2023 17:22:21.03 <Erro:HAL.Card.Error> Slot-2: Previous message repeated 16 additional times in the last 1 second(s)
11/15/2023 17:22:20.85 <Noti:log.AlertMbufTrgtPrcntFull> Slot-1: The memory-buffer log target is 90% full with 900 of a possible 1000 messages currently logged.
11/15/2023 17:22:20.53 <Noti:ACL.Policy.unBind> Slot-1: Policy:unBind:acl1:vlan:*:port:5:40:
11/15/2023 17:22:20.40 <Noti:ACL.Policy.unBind> Slot-1: Policy:unBind:acl1:vlan:*:port:5:5:
11/15/2023 17:22:20.40 <Erro:HAL.Card.Error> Slot-1: halGetHwPortMapping: Unable to get slot tree node for slot 5
11/15/2023 17:22:20.39 <Erro:HAL.Card.Error> Slot-1: Previous message repeated 68 additional times in the last 1 second(s)
11/15/2023 17:22:14.03 <Info:cli.logRemoteCmd> Slot-1: 10.7.3.12 (ssh) user.admin: unconfigure slot 5
11/15/2023 17:14:49.42 <Info:cli.logRemoteCmd> Slot-1: 10.7.3.12 (ssh) user.admin: save
11/15/2023 17:14:09.38 <Info:vlan.dbg.info> Slot-1: Media Q+CR4_3m is inserted into Port 4:53
11/15/2023 17:14:08.84 <Info:HAL.Port.Info> Slot-1: Stacking port 4:2 link up at 40Gbps.
11/15/2023 17:14:07.94 <Info:HAL.Port.Info> Slot-1: Stacking port 1:1 link up at 40Gbps.
11/15/2023 17:14:01.28 <Info:vlan.dbg.info> Slot-1: Media Q+CR4_.5m is removed from Port 4:53
11/15/2023 17:13:43.98 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 4:35 link down
11/15/2023 17:13:38.35 <Info:HAL.Sys.Info> Slot-1: Internal PSU-2 in slot 5 is disconnected.
11/15/2023 17:13:38.35 <Info:HAL.Sys.Info> Slot-1: Internal PSU-1 in slot 5 is disconnected.
11/15/2023 17:13:29.73 <Warn:HAL.Card.Warning> Slot-2: Slot-5 is not present to do card exec cmd POWER_OFF
11/15/2023 17:13:29.69 <Warn:DM.Warning> Slot-2: Slot-5 FAILED (1) Conduit receive error encountered
11/15/2023 17:13:29.69 <Warn:HAL.Card.Warning> Slot-2: pibConduitMasterRcvOneSlot(): failed, rc=-6, errno=107, slot=5
11/15/2023 17:13:28.84 <Info:HAL.Port.Info> Slot-1: Stacking port 5:2 link down.
11/15/2023 17:13:28.84 <Info:HAL.Port.Info> Slot-1: Stacking port 5:1 link down.
11/15/2023 17:13:28.84 <Info:HAL.Port.Info> Slot-1: Stacking port 4:2 link down.
11/15/2023 17:13:28.84 <Info:HAL.Port.Info> Slot-1: Stacking port 1:1 link down.
11/15/2023 17:13:27.90 <Noti:DM.Notice> Slot-1: Transitioning slot 5 to UNKNOWN rather than STANDBY
11/15/2023 17:13:26.90 <Noti:DM.Notice> Slot-1: Previous message repeated 2 additional times in the last 1 second(s)
11/15/2023 17:13:26.38 <Info:HAL.Card.Info> Slot-1: Slot-5 down, resetting all TCP connections to it
11/15/2023 17:13:26.38 <Info:HAL.Card.Info> Slot-1: Module in Slot-5 is removed

Stack Topology is a Ring
Active Topology is a Ring
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*f0:64:26:81:a4:00 1 Active Master CA-
f0:64:26:81:f4:00 2 Active Backup CA-
f0:64:26:82:20:00 3 Active Standby CA-
f0:64:26:84:98:00 4 Active Standby CA-
* - Indicates this node
Flags: (C) Candidate for this active topology, (A) Active Node
(O) node may be in Other active topology

sh slot
Slots Type Configured State Ports
---------- ------------------------------- ------------------------------- ----------- -----
Slot-1 5520-48W 5520-48W Operational 60
Slot-2 5520-48W 5520-48W Operational 60
Slot-3 5520-48W 5520-48W Operational 60
Slot-4 5520-48W 5520-48W Operational 60
Slot-5 Empty 0
Slot-6 Empty 0
Slot-7 Empty 0
Slot-8 Empty 0