AUTOBOOT Catalyst 4506

[ironrlo]

I`m working with a Catalyst 4506, actual boot system flash "bootflash:cat4500-entservicesk9-mz.122-31.SG1.bin", also it has 2 modules:
Module 1 (WS-X4516-10GE Hw: 2.1)
Module 2 (WS-X4548-GB-RJ45 Hw: 2.1)

A Boot occurs when I try to used the command "copy running-config startup-config".

In the beginng the boot system flash was "bootflash:cat4000-i9k91s-mz.122-25.ewa4.bin"

Supervisor Module (WS-X4516-10GE) would produce the boot..??

Help Please...

 

[vipergg]

Are you saying when you do a copy run start it reloads the box ?

 

[ironrlo]

that's right!!!... When I do a copy running-config startup-config it reloads the Catalyst 4506... Do you have an Idea to solve this fail??

Thanks

 

[vipergg]

Anything show in the logs ? If not then maybe you have a bad supervisor or a major bug in the IOS version you are running. I would get ahold of cisco and have it rma'd . I would say its a supervisor problem , looked and did not see anything major like that in the bug tracker for that version you are running. Other than make sure the supervisor is seated correctly and tightened down likely a hardware issue.

 

[vipergg]

If it worked fine on the old IOS then try a different version , the recommended current version for that card is
12.2(31)SGA8 .

 

[ironrlo]

Here is a copy of the procedure on the Catalyst 4506

CK4506_38T#copy running-config startup-config
Destination filename [startup-config]?
Build
VECTOR 0

Buffered messages: (last 8192 bytes only)

00:00:10: %C4K_IOSMODPORTMAN-4-POWERSUPPLYBAD: Power supply 2 has failed or been turned off
00:00:10: %C4K_IOSMODPORTMAN-4-POWERSUPPLYFANBAD: Fan of power supply 2 has failed
00:00:10: %C4K_IOSMODPORTMAN-4-INLINEPOWERSUPPLYBAD: Inline power from power supply 2 has failed or been turned off
00:00:24: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
*Nov 28 12:14:22: %SYS-6-CLOCKUPDATE: System clock has been updated from 18:14:22 UTC Fri Nov 28 2008 to 12:14:22 CDT Fri Nov 28 2008, configured from console by console.
*Nov 28 12:14:22: %SYS-6-CLOCKUPDATE: System clock has been updated from 12:14:22 CDT Fri Nov 28 2008 to 12:14:22 CDT Fri Nov 28 2008, configured from console by console.
*Nov 28 12:14:22: %C4K_IOSMODPORTMAN-6-MODULEONLINE: Module 1 (WS-X4516-10GE S/N: JAB094000S2 Hw: 2.1) is online
*Nov 28 12:14:22: %C4K_IOSMODPORTMAN-6-MODULEONLINE: Module 2 (WS-X4548-GB-RJ45 S/N: JAE0940MKVU Hw: 2.1) is online
*Nov 28 12:14:23.683: VTP mode mismatches between startup-config: transparent, vlan database: server.
*Nov 28 12:14:23: %SW_VLAN-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory
*Nov 28 12:14:23: %SYS-5-CONFIG_I: Configured from memory by console
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/5, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/6, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/7, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/8, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/9, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/10, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/11, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/12, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/13, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/14, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/15, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/16, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/18, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/20, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/22, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/24, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/25, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/26, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/27, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/28, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/29, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/30, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/31, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/32, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/33, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/34, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/35, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/36, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/37, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/38, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/39, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/40, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/41, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/42, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/43, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/44, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/45, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/46, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/47, changed state to administratively down
*Nov 28 12:14:23: %LINK-5-CHANGED: Interface GigabitEthernet2/48, changed state to administratively down
*Nov 28 12:14:23: %SYS-5-RESTART: System restarted --
Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500-ENTSERVICESK9-M), Version 12.2(31)SG1, RELEASE SOFTWARE (fc4)
Technical Support:

http://www.cisco.com/techsupport

Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Mon 27-Nov-06 19:43 by kehsiao
*Nov 28 12:14:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/3, changed state to down

 

[burtsbees]

You have a bad power supply!

00:00:10: %C4K_IOSMODPORTMAN-4-POWERSUPPLYBAD: Power supply 2 has failed or been turned off
00:00:10: %C4K_IOSMODPORTMAN-4-POWERSUPPLYFANBAD: Fan of power supply 2 has failed

Unless, of course, it's unplugged...

Burt

 

[VinceWhirlwind]

This one's interesting:
*Nov 28 12:14:23.683: VTP mode mismatches between startup-config: transparent, vlan database: server.
*Nov 28 12:14:23: %SW_VLAN-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory

I'm getting some 4506s soon, so I'll be keen to figure out how to make that happen.

I guess if it's rebooted before successfully saving the running-config it makes sense.

 

[ironrlo]

Thanks for your comments, One of the Power supply is not working... I'm going to check the Vlan 4...

 

[burtsbees]

Vince---it's probably an old config still in there that just never got taken out. This won't make it reboot every time a copy run start is issued.
The copy run start taxes the cpu for a short period of time, which requires more power. You may have a system board or another psu---I would say a power issue, or a buggy IOS...VERY buggy!

I am a hardware tech, so I have seen somewhat similar issues. Replace the power supply (PSU) and see what that does.

Burt

 

[vipergg]

Make sure the power is on for the plug that feeds it , also check to make sure that cable is shoved all the way , on those power supplies they can be very hard to push in with those clamps there and you may think its pushed all the way in but its not. Seeing thats it bitching about the vlan config its possible that the vlan.dat file is corrupted and that is causing a problem . I would try deleting it and recreating all your vlans and see what happens. Make sure its in transparent mode if you are not using client/server setup.

 

[PeterHurst]

Obviously the power is an issue but should in no way cause a reboot on saving config. It's the VECTOR 0 that concerns me - I'm guessing the startup has VTP set as server and the running as client hence the VTP error.. my guess is that theres NVRAM corruption - not sure if that cna be fixed from boot mode - point of interest - if you tftp off the running and then try and copy tftp to startup does that work?

 

[ironrlo]

Thanks for your comments. time after time, I was looking for help in every place, after long time A CCNP gave me a copy of a Field Notice: "FN-62479" refer to WS-X4516-10GE and WS-X4013+10GE Supervisors May Reset Due to Multibit
ECC Error

WS-X4516-10GE with Hardware Revision 2.0 to 2.3 AND Supervisor serial numbers lower than JAx1030xxxx, are affected by a SDRAM degradation, it produce a Reset.

I`m working with a Catalyst 4506, Module 1 (WS-X4516-10GE Hw: 2.1) and the serial Number is Lower than JAx1030xxxx

Thanks for your comments ! ! !