Showing results for 
Search instead for 
Did you mean: 

Auto reboot issue on 4500 series switch


We are facing cold start issue on 4500 series switch. The switch is restarting automatically almost weekly twice or thrice.

As per show tech. output , there is "cold start log".Please find the attached  logs for your reference.

Please help urgently to resolve issue & which may cause the issue?

After time change , auto restart happening & am not found any log for power failure also.




Since the 4500 series are Catalyst switches, they are supported by TAC not SBSC. You may move this topic to the proper forum but for an issue like that, I would just call TAC and open an incident.



This post has been moved to the correct area.

Cindy Toy
Cisco Small Business Community Manager
for Cisco Small Business Products
twitter: CiscoSBsupport

Regards, Cindy If my response answered your question, please mark the response as answered. Thank you!


Pls help ASAP.

Awaiting for reply..



Hall of Fame Community Legend

Post the following output:

1.  dir

2.  sh version


please refer the below log.

------------------ show version ------------------

Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500e-IPBASEK9-M), Version 12.2(53)SG, RELEASE SOFTWARE (fc3)

Technical Support:

Copyright (c) 1986-2009 by Cisco Systems, Inc.

Compiled Thu 16-Jul-09 21:52 by prod_rel_team

Image text-base: 0x10000000, data-base: 0x1258A1FC

ROM: 12.2(44r)SG5

Darkside Revision 4, Jawa Revision 9, Tatooine Revision 140, Forerunner Revision 1.21

BOB_3RDFLR_SW_1 uptime is 3 minutes

System returned to ROM by reload

System image file is "bootflash:cat4500e-ipbasek9-mz.122-53.SG.bin"

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

If you require further assistance please contact us by sending email to

cisco WS-C4506-E (MPC8548) processor (revision 8) with 524288K bytes of memory.

Processor board ID FOX1405G661

MPC8548 CPU at 1GHz, Supervisor 6L-E

Last reset from Reload

5 Virtual Ethernet interfaces

96 FastEthernet interfaces

100 Gigabit Ethernet interfaces

2 Ten Gigabit Ethernet interfaces

511K bytes of non-volatile configuration memory.

Configuration register is 0x2101

------------------ dir nvram: ------------------

Directory of nvram:/

  512  -rw-        9123                      startup-config

  513  ----           5                      private-config

  514  -rw-        9123                      underlying-config

    1  ----         174                      persistent-data

    2  ----           0                      rf_cold_starts

    3  -rw-           0                      ifIndex-table.gz

524284 bytes total (512032 bytes free)

Cisco Employee

Hi Shanmugam,

I have reviewed the outputs and the decodes in the crashdump show that this

crash was due to a parity error.

Possible causes of these parity errors are random static discharge or other

external factors.

We have two types of these errors:

Soft parity errors

These errors occur when an energy level within the chip (for example, a one

or a zero) changes, most often due to radiation. When referenced by the CPU,

such errors cause the system to crash. In case of a soft parity error, there

is no need to swap the board or any of the components.

Hard parity errors

These errors occur when there is a chip or board failure that corrupts data.

In this case, you need to re-seat or replace the affected component, which

usually involves a memory chip swap or a board swap.

Moving forward with this case we need to monitor the device 2 days and if

the device is stable, this can be considered a soft parity (one-time

incident). If the device crashes again then this would be a HW failure and

we need to proceed with RMA.




*Plz rate this info is helpfull.

Content for Community-Ad