what is the meaning of exclamation mark (!) in stacking?

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
! Slot-1 H.O-x460-Stack.1 #
Photo of Marlon

Marlon

  • 1,570 Points 1k badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Prashanth KG

Prashanth KG, Employee

  • 5,300 Points 5k badge 2x thumb
Hi Marlon,

This could be an indication that the sys-recovery is triggered in the stack.
Could you share the following commands and the logs from the switch.

show configuration devmgr
show log

Looking forward to the outputs.
Photo of Marlon

Marlon

  • 1,570 Points 1k badge 2x thumb
Hi Prashanth,

Thanks. i will share to you the outputs this coming Monday (Philippines time)
Photo of Marlon

Marlon

  • 1,570 Points 1k badge 2x thumb
Hi Prashanth,

please see the output below:


 Slot-1 H.O-x460-Stack.1 # sho con "devmgr"
#
# Module devmgr configuration.
#
configure snmp sysName "H.O-x460-Stack"
configure snmp sysLocation "HO-2ndFloor-IT"
configure timezone name Taiwan 480
configure slot 1 module X460-24t
configure sys-recovery-level slot 1 reset
configure slot 2 module X460-24t
configure sys-recovery-level slot 2 reset

! Slot-1 H.O-x460-Stack.2 #
! Slot-1 H.O-x460-Stack.2 # sho log
12/13/2015 20:25:46.22 <Noti:DM.Notice> Slot-1: Previous message repeated 155 additional times in the last 9951 second(s)
12/13/2015 23:12:41.94 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/13/2015 23:12:47.63 <Info:AAA.authPass> Slot-1: Login passed for user warning through telnet (172.18.2.105)
12/13/2015 23:12:50.02 <Info:AAA.logout> Slot-1: User warning logout from telnet (172.18.2.105)
12/13/2015 23:13:46.55 <Noti:DM.Notice> Slot-1: Previous message repeated 42 additional times in the last 2649 second(s)
12/13/2015 23:59:00.56 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 00:00:02.90 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)
12/14/2015 00:00:05.14 <Noti:DM.Notice> Slot-1: Previous message repeated 29 additional times in the last 1809 second(s)
12/14/2015 00:31:19.08 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 00:31:32.27 <Info:AAA.authPass> Slot-1: Login passed for user warning through telnet (172.18.2.105)
12/14/2015 00:32:04.70 <Info:AAA.authPass> Slot-1: Login passed for user warning through telnet (172.18.2.105)
12/14/2015 00:32:23.71 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 00:32:27.21 <Info:AAA.logout> Slot-1: User warning logout from telnet (172.18.2.105)
12/14/2015 00:32:28.20 <Info:AAA.logout> Slot-1: User warning logout from telnet (172.18.2.105)
12/14/2015 00:33:28.30 <Noti:DM.Notice> Slot-1: Previous message repeated 25 additional times in the last 1551 second(s)
12/14/2015 01:00:23.73 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 01:00:27.70 <Info:AAA.authPass> Slot-1: Login passed for user warning through ssh (172.18.1.184)
12/14/2015 01:00:27.70 <Info:AAA.LogSsh> Slot-1: Msg from Master : Did password authentication for user warning (172.18.1.184)
12/14/2015 01:00:31.45 <Info:AAA.logout> Slot-1: User warning logout from ssh (172.18.1.184)
12/14/2015 01:00:32.20 <Info:AAA.authPass> Slot-1: Login passed for user warning through ssh (172.18.1.184)
12/14/2015 01:00:32.21 <Info:AAA.LogSsh> Slot-1: Msg from Master : Did password authentication for user warning (172.18.1.184)
12/14/2015 01:01:28.31 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 01:02:01.83 <Info:AAA.logout> Slot-1: User warning logout from ssh (172.18.1.184)
12/14/2015 01:02:32.94 <Noti:DM.Notice> Slot-1: Previous message repeated 287 additional times in the last 18481 second(s)
12/14/2015 06:11:38.34 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 06:12:17.67 <Info:AAA.authPass> Slot-1: Login passed for user warning through telnet (172.18.2.105)
12/14/2015 06:12:20.24 <Info:AAA.logout> Slot-1: User warning logout from telnet (172.18.2.105)
12/14/2015 06:12:42.94 <Noti:DM.Notice> Slot-1: Previous message repeated 205 additional times in the last 13246 second(s)
12/14/2015 09:54:33.21 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 09:55:12.82 <Info:AAA.authPass> Slot-1: Login passed for user warning through ssh (172.21.200.219)
12/14/2015 09:55:12.82 <Info:AAA.LogSsh> Slot-1: Msg from Master : Did password authentication for user warning (172.21.200.219)
12/14/2015 09:55:37.93 <Noti:DM.Notice> Slot-1: Previous message repeated 18 additional times in the last 1115 second(s)
12/14/2015 10:15:17.39 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 10:15:58.27 <Info:AAA.logout> Slot-1: User warning logout from ssh (172.21.200.219)
12/14/2015 10:16:22.03 <Noti:DM.Notice> Slot-1: Previous message repeated 209 additional times in the last 13569 second(s)
12/14/2015 14:03:36.64 <Noti:DM.Notice> Slot-1: Setting hwclock time to system time, and broadcasting time
12/14/2015 14:03:48.00 <Info:AAA.authPass> Slot-1: Login passed for user warning through telnet (172.18.2.105)
Photo of Ryan Mathews

Ryan Mathews, Alum

  • 8,988 Points 5k badge 2x thumb
Prashanth gave you a nice next action.

Here's an explanation of the exclamation mark from a GTAC Knowledge query:
https://gtacknowledge.extremenetworks.com/articles/Q_A/What-does-it-mean-when-an-exclamation-point-a...
Photo of Marlon

Marlon

  • 1,570 Points 1k badge 2x thumb
Thanks for the info Ryan.
Photo of Prashanth KG

Prashanth KG, Employee

  • 5,300 Points 5k badge 2x thumb
Hi Marlon,

Thank you for sharing the configuration and the log messages. 
I see that the switch sys-recovery option is set to reset and not shutdown. 

Please check if there is any issue with the temperature in the switch/environment LED is on in the switch. 
We can verify the same from the output of show switch.

This output is little strange as the ! indicates a node to in the shutdown state. Please collect the following outputs: 

show slot
show log messages nvram. 

Also, please share if the traffic flow across the slot 1 is fine. 
Look for any failure state of the slots in the outputs above. If nothing interesting shows up, I would suggest opening up a GTAC case. 

Looking forward to the outputs! 
Photo of Marlon

Marlon

  • 1,570 Points 1k badge 2x thumb
Hi Prashanth,

Thanks. if we execute "clear sys-recovery-level" command this will required a reboot?

below are the outputs:

! Slot-1 H.O-x460-Stack.1 # show log messages nvra
! Slot-1 H.O-x460-Stack.4 #                   835265 bytes saved on Tue Dec 15 10:24:44 2015primary.cfg       Created by ExtremeXOS version 15.3.4.6Config Booted:    primary.cfg                                          Config Selected:  primary.cfg                                          Secondary ver:    15.2.2.7                     15.2.2.7                                  patch1-13                    patch1-13Primary ver:      15.3.4.6                     15.3.4.6                Press <SPACE> to continue or <Q> to quit:Image Booted:     primary                      primary                 Image Selected:   primary                      primary                 Current State:    MASTER                       BACKUP (In Sync)                          ------------------------     ------------------------Slot:             Slot-1 *                     Slot-2                  System UpTime:    246 days 7 hours 13 minutes 58 seconds Next Reboot:      None scheduledBoot Count:       14Boot Time:        Mon Apr 13 03:14:43 2015Timezone:         [Auto DST Disabled] GMT Offset: 480 minutes, name is Taiwan.Current Time:     Tue Dec 15 10:28:41 2015System Watchdog:  EnabledRecovery Mode:    AllSysHealth check:  Enabled (Normal)System Type:      X460-24t (Stack)System MAC:       02:04:96:52:57:FASysContact:       support@extremenetworks.com, +1 888 257 3000SysLocation:      HO-2ndFloor-ITSysName:          H.O-x460-Stack! Slot-1 H.O-x460-Stack.3 # show switch ! Slot-1 H.O-x460-Stack.3 # show switSlot-8                                             Empty          0    Slot-7                                             Empty          0    Slot-6                                             Empty          0    Slot-5                                             Empty          0    Slot-4                                             Empty          0    Slot-3                                             Empty          0    Slot-2   X460-24t             X460-24t             Operational   34    Slot-1   X460-24t             X460-24t             Operational   34    --------------------------------------------------------------------Slots    Type                 Configured           State       Ports! Slot-1 H.O-x460-Stack.2 # sho slotA total of 111 log messages were displayed.11/13/2015 18:04:47.41 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12017B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:47.41 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120182 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120108 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120158 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120108 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12016E / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120158 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120187 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12016E / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120157 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120187 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120159 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120157 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12016F / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120159 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120181 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12016F / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120156 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.Press <SPACE> to continue or <Q> to quit:11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120181 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120180 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120156 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12014A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120180 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120149 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:48.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12014A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12014B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120149 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12013C / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12014B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120163 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12013C / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12017C / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120163 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.41 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12018B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12017C / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.44 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120185 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:49.40 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12018B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.44 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120199 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.42 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120185 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.44 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120160 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.42 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120199 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.Press <SPACE> to continue or <Q> to quit:11/13/2015 18:04:50.44 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12019A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.42 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120160 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.44 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120138 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.42 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12019A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.44 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120146 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.42 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120138 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.44 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120147 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.42 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120146 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:04:50.42 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120147 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/13/2015 18:06:37.19 <Warn:BFD.RxPktInv> Slot-1: Received BFD an invalid packet on VLAN MPLS Error:Invalid ttl value for single Hop session11/14/2015 00:00:03.24 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/15/2015 00:00:03.55 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/16/2015 00:00:03.30 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/17/2015 00:00:03.36 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/18/2015 00:00:03.06 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/19/2015 00:00:03.21 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/20/2015 00:00:03.51 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12018A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC1201B9 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12018A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC1201A0 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC1201B9 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC1202A3 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.Press <SPACE> to continue or <Q> to quit:11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC1201A0 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120109 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC1202A3 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12017B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120109 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:54.45 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12017B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.48 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120182 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.48 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12024A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.47 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120182 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.48 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12024D / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.47 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12024A / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.48 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120249 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.47 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12024D / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.48 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120248 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.47 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120249 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.48 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC120264 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.47 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120248 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.48 <Warn:Kern.IPv4FIB.Warning> Slot-1: dest 0xAC12024B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.47 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC120264 / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/20/2015 16:39:55.47 <Warn:Kern.IPv4FIB.Warning> Slot-2: dest 0xAC12024B / 32  nexthop 0xAC1202F6: Unable to add route to unit 0, rc Entry exists.  Shadow problem.11/21/2015 00:00:03.05 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/22/2015 00:00:03.26 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/23/2015 00:00:03.82 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)Press <SPACE> to continue or <Q> to quit:11/24/2015 00:00:02.91 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/25/2015 00:00:03.31 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/26/2015 00:00:03.13 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/27/2015 00:00:03.53 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/28/2015 00:00:02.94 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/29/2015 00:00:03.52 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)11/30/2015 00:00:03.48 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/01/2015 00:00:03.25 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/02/2015 00:00:03.72 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/03/2015 00:00:03.85 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/04/2015 00:00:03.92 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/05/2015 00:00:06.79 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/06/2015 00:00:03.49 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/07/2015 00:00:03.41 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/07/2015 13:48:36.41 <Warn:AAA.authFail> Slot-1: Login failed for user failsafe through telnet (172.21.200.246)12/08/2015 00:00:03.82 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/09/2015 00:00:03.44 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/10/2015 00:00:03.95 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/11/2015 00:00:03.36 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/11/2015 10:19:13.23 <Warn:IPMC.Warning> Slot-1: Warning: received IGMPv3 query on vlan WIFI configured for IGMPv2 from 172.25.14.1112/12/2015 00:00:03.64 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/13/2015 00:00:02.89 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/14/2015 00:00:02.90 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)12/15/2015 00:00:03.40 <Warn:AAA.authFail> Slot-1: Login failed for user admin through telnet (172.18.1.151)! Slot-1 H.O-x460-Stack.1 # show log messages nvram
Photo of Prashanth KG

Prashanth KG, Employee

  • 5,300 Points 5k badge 2x thumb
Hi Marlon,

yes, we need to reboot the slot after clearing the sys-recovery-level.

Snippet from the user guide:

Clear the shutdown state with the command:
clear sys-recovery-level
On a SummitStack, use the command:
clear sys-recovery-level slot slot
The switch prompts you to confirm this action. The following is a sample confirmation message:
Are you sure you want to clear sys-recovery-level? (y/n)
2 Enter y to confirm this action and clear the shutdown state. Enter n or press [Enter] to cancel this
action.
After you clear the shutdown state, use the reboot command to bring the switch and ports back
online. After rebooting, the switch is operational.

Hope this helps!
Photo of Marlon

Marlon

  • 1,570 Points 1k badge 2x thumb
Hi Prashanth,

Thanks you so much.