OS6450 stacking (two os6450-24) and one os6450 would auto poweroff

[oysterliu]

master :
THU MAY 25 17:18:09 2023 STACK-MANAGER info == SM == Stack Port B Status Changed: DOWN
THU MAY 25 17:18:09 2023 STACK-MANAGER info == SM == Stack Port A Status Changed: DOWN
THU MAY 25 17:18:10 2023 STACK-MANAGER info == SM == NI 2 down notification sent to LAG
THU MAY 25 17:18:10 2023 LINKAGG info Port Leave . port: 2025 agg: 1
THU MAY 25 17:18:11 2023 STP info Topology changed on VLAN/STP id 1
THU MAY 25 17:18:11 2023 STP info Topology changed on VLAN/STP id 4001
THU MAY 25 17:18:12 2023 HSM-CHASSIS info T8: Ni(2) extraction detected
THU MAY 25 17:18:12 2023 HSM-CHASSIS info == HSM == csHsmUtilNiCtxBrdSend() nsm CS_HSM_NSM_ST_OP, poweroff 0 Ni2
THU MAY 25 17:18:12 2023 HSM-CHASSIS info === HSM === Power Supply 3 has been REMOVED
THU MAY 25 17:18:12 2023 VLAN info CS_NI_DOWN/CS_NI_NOTPRESENT msg Rx for slot 2
THU MAY 25 17:18:12 2023 VLAN info Del connection for slot 2
THU MAY 25 17:18:12 2023 VLAN info VMC: Sent Pause for slot 2
THU MAY 25 17:18:12 2023 VLAN info Start Timer on ni_down 2 @ 1685006292
THU MAY 25 17:18:12 2023 INTERFACE info Close NI 2 ESM, socket 40 OK
THU MAY 25 17:18:12 2023 INTERFACE info Close NI 2 NiSUp, socket 19 OK
THU MAY 25 17:18:12 2023 GM info NI_DOWN 2
THU MAY 25 17:18:12 2023 GM info Del connection for slot 2
THU MAY 25 17:18:12 2023 GM info GMC: Sent Pause for slot 2
THU MAY 25 17:18:12 2023 GM info Start Timer on ni_down 2 @ 1685006292
THU MAY 25 17:18:12 2023 LINKAGG info EVT board down received slot 2 slice 0 recover 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 8: c failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 4f: 3 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 6: 4 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: a: 1 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: b: 1 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 31: 5 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 7: a failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 20: 29 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 9: b failed!! event 2 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 28: 2 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: c: 1 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 12: 2 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 17: 6 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 5b: 2 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: d: 2 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 16: 0 failed!! event 2 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 96: 3 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 29: 5 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 95: 5 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: a3: 2 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: a4: 0 failed!! event 3 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 4d: 1 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alarm sendPmMsg: sendTo 41 : 0: 4d: 1 failed!! event 4 len 0
THU MAY 25 17:18:12 2023 PORT-MGR alert pmSend: aborting send... 0
THU MAY 25 17:18:12 2023 ETHERNET-OAM info Timer started Slot: 2, SocketID: 506
THU MAY 25 17:18:17 2023 GM info Timer closed skt on ni 1 @ 1685006297
THU MAY 25 17:18:17 2023 VLAN info Timer closed skt on ni 1 @ 1685006297
THU MAY 25 17:18:17 2023 VLAN info Timer closed skt for GVRP NI on ni 1 @ 1685006297
THU MAY 25 17:18:17 2023 ETHERNET-OAM info Timer expired Slot: 2, SocketID: 506
THU MAY 25 17:18:21 2023 STP info Topology changed on VLAN/STP id 1
THU MAY 25 17:18:21 2023 STP info Topology changed on VLAN/STP id 4001
THU MAY 25 17:28:12 2023 CSM-CHASSIS info == CSM == Stack topology changes have been updated to persistant file
THU MAY 25 17:28:12 2023 CCM-CHASSIS info === CCM === NI 2 has gone down/removed from host 'vxTarget'

I had changed a os6450 to test it , but it happend again. I also change the stacking module and stacking cable, but this event happened again.

and I change the power input to UPS , this event also exits. (my AOS=OS6450-24 6.7.2.19.R04).
Have anyone encountered this event?

[silvio]

both switches are working standalone without problems?
If yes than check AOS and uboot/miniboot. show hardware-info, show microcode.
And use the newest release. Than stack again.
BR Silvio