UNSOLVED

malarba

updated

3 years ago

M

malarba

11 Posts

0

91

January 23rd, 2024 11:32

Card Removed Stack MXL, help please.

Stack-MXL#show system brief

Stack MAC                  : f8:b1:56:95:0f:3a
Reload-Type                         : normal-reload [Next boot : normal-reload]

--  Stack Info  --
Unit  UnitType     Status         ReqTyp          CurTyp          Version     Ports
------------------------------------------------------------------------------------
  0   Member       not present    MXL-10/40GbE
  1   Standby      online         MXL-10/40GbE    MXL-10/40GbE    9.11(0.0)   56
  2   Management   online         MXL-10/40GbE    MXL-10/40GbE    9.11(0.0)   56
  3   Member       online         MXL-10/40GbE    MXL-10/40GbE    9.11(0.0)   56

Jan 18 10:18:46: %STKUNIT2-M:CP %CHMGR-2-STACKUNIT_DOWN: stack-unit 0 down - card removed
Jan 18 10:18:25: %STKUNIT2-M:CP %CHMGR-5-CARD_RETRY_RESET: stack-unit 0 power-cycled to attempt bring-up
Jan 18 10:18:17: %STKUNIT1-S:CP %IFMGR-1-DEL_PORT: Removed port: Te 0/1-32,41-48,53-56, Fo 0/49, 
Jan 18 10:18:17: %STKUNIT2-M:CP %LACP-5-PORT-UNGROUPED: PortChannel-128-Ungrouped: Interface Fo 0/49 exited port-channel 128.
Jan 18 10:18:17: %STKUNIT2-M:CP %IFMGR-1-DEL_PORT: Removed port: Te 0/1-32,41-48,53-56, Fo 0/49, 
Jan 18 10:18:17: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Fo 0/49
Jan 18 10:18:17: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/26
Jan 18 10:18:17: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/25
Jan 18 10:18:17: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/18
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/17
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/16
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/15
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/14
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/10
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/9
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/8
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/7
Jan 18 10:18:16: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/6
Jan 18 10:18:15: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/5
Jan 18 10:18:15: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/2
Jan 18 10:18:15: %STKUNIT2-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 0/1
Jan 18 10:18:15: %STKUNIT2-M:CP %CHMGR-2-STACKUNIT_DOWN: Major alarm: stack-unit 0 down - IPC timeout
Jan 18 10:18:15: %STKUNIT2-M:CP %IPC-2-STATUS: target stack-unit 0 not responding
Jan 18 10:16:54: %STKUNIT2-M:CP %SYSADM-5-TASK_CPU_THRESHOLD: 1min cpu utilization of stack-unit 0 has exceeded the threshold. Top three processes are ifagt_1 (0.50%), tExcTask (0.25%), frrpaRecv (0.00%) 
Jan 18 10:16:54: %STKUNIT2-M:CP %SYSADM-5-CPU_THRESHOLD: Overall cpu usage of stack-unit 0 is above threshold. Cpu1minUsage (94%)

The strange thing is that the Enclosure 1000e enclosure chassis does not show alarms. The interface LEDs are ok.