cisco MDS 9222i switch reloads

[lfgallegon]

Hi, I restarted my Cisco MDS 9222i and after that my device is keeping restarting every 2 minutes. Please your comment about a possible solution:

-----------------------

cisco MDS 9222i ("4x1GE IPS, 18x1/2/4Gbps FC/Sup2")

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 1.0.19
  loader:    version N/A
  kickstart: version 5.2(8a)
  system:    version 5.2(8a)
  BIOS compile time:       02/01/10
  kickstart image file is: bootflash:/m9200-s2ek9-kickstart-mz.5.2.8a.bin
  kickstart compile time:  12/25/2020 12:00:00 [05/13/2013 03:27:31]
  system image file is:    bootflash:/m9200-s2ek9-mz.5.2.8a.bin
  system compile time:     5/3/2013 10:00:00 [05/13/2013 04:34:47]


Hardware
  cisco MDS 9222i ("4x1GE IPS, 18x1/2/4Gbps FC/Sup2")
  Motorola, e500v2  with 1036300 kB of memory.
  Processor Board ID JAF1446AQBN

  Device name: MDS-BCOL-PERU
  bootflash:    1023120 kB
Kernel uptime is 0 day(s), 0 hour(s), 1 minute(s), 52 second(s)

Last reset at 111249 usecs after  Tue May 29 18:32:13 2018

  Reason: Reset Requested due to Fatal Module Error
  System version: 5.2(8a)
  Service: Xbar manager

-----------------------

show log#

%DAEMON-3-SYSTEM_MSG: ^Iaddress: <127.1.1.1> 7f010101  - in.tftpd[2399]
%KERN-2-SYSTEM_MSG: Starting kernel... - kernel
%KERN-1-SYSTEM_MSG:  Entered kgdb_console_init:1975 - kernel
%KERN-3-SYSTEM_MSG: CMOS: Module initialized - kernel
%KERN-3-SYSTEM_MSG: Initializing fc2 proto  - kernel
%KERN-2-SYSTEM_MSG: Checksum failed for sprom signature: 0xabab, blk signature: 0xababcomputed cksum: 0x14bc, block cksum: 0x14b8 - kernel
%MODULE-5-ACTIVE_SUP_OK: Supervisor 1 is active (serial: JAF1446AQBN)
%PLATFORM-5-MOD_STATUS: Module 1 current-status is MOD_STATUS_ONLINE/OK
%USER-3-SYSTEM_MSG: Launching root group entities  - proc_mgr
%USER-3-SYSTEM_MSG: Launching remaining group entities  - proc_mgr
May 29 18:31:23 %KERN-3-SYSTEM_MSG: **** TOTAL PORTS = 34 ***** - kernel
%PORT-5-IF_UP: Interface mgmt0 is up
%IMAGE_DNLD-SLOT1-5-ADDON_IMG_DNLD_STARTED:  Addon module image download process started. Addon Image download started...
%IMAGE_DNLD-SLOT1-5-ADDON_IMG_DNLD_COMPLETE:  Addon module image download process completed. Addon Image download completed, installing image please wait..
%IMAGE_DNLD-SLOT1-5-ADDON_IMG_DNLD_STARTED:  Addon module image download process started. Addon Image download started...
%IMAGE_DNLD-SLOT1-5-ADDON_IMG_DNLD_COMPLETE:  Addon module image download process completed. Addon Image download completed, installing image please wait..
%IMAGE_DNLD-SLOT1-5-ADDON_IMG_DNLD_SUCCESSFUL:  Addon module image download and install process successful. Addon image installed.
%IPS-5-FCIP_IF_CR_DEL: Interface FCIP21 created
%PORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: %$VSAN 1%$ Interface fcip21 is down (Tunnel port src interface unbound)
                     
%KERN-3-SYSTEM_MSG: Sending reconfig cmd 0 to get spi egress 1 - kernel
%KERN-3-SYSTEM_MSG: Sending reconfig cmd 0 to get spi egress 2 - kernel
%KERN-3-SYSTEM_MSG: Sending reconfig cmd 0 to get spi egress 3 - kernel
%PROC_MGR-2-MESG: Entity : (dnld_image) has exited successfully

After this last log the switch reboots.

---------------

Thanks for your help

[Kirk J]

Greetings.

Hopefully you have a current contract, and can open a TAC case.

The fatal module error could be an actual hardware problem, or image  issue, etc.

For a TAC case they will normally ask for show tech-support details, show logging onboard, show logging onboard error-stats, etc, to look for details if that is an issue with linecard Module, X-bar, supervisor, etc.

IF, you don't have any hardware coverage, and the switch continues to be stuck in reboot loop forever, then you may want to consider attempting a bootflash recovery.

If your real issue is hardware failure, then this obviously won't help.

https://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/troubleshooting/guide/ts_sw.html#wp781831  covers the general steps for rebuilding bootflash and reloading the kickstart and system images.

Hopefully you can get a copy of your current running config (or already have one), so you can re-apply that if the bootflash rebuild is successful.

Thanks,

Kirk...