4507 supervisor going down after working few hours

Unanswered Question
Nov 13th, 2007
User Badges:


my comp is having 4507 switch it has 2 supervisor Sup V-10GE 10GE (X2), 1000BaseX (SFP). one of the sup which is in slot 1 is getting power off after working arouund 30 minutes no status power led nothing. checked the value of the Environment Variable with 'show platform environment variable' command and i found the PeerResetReason environment variable in the result with a time stamp, the output showed the following result,

PeerResetReason='12 Timer Expired 22:15:2 UTC Sun Oct 28 2007'

Also when the system is running on the secondary Supervisor Engine, i can't work in the configuration mode of the Switch. When i try to enter any Global Config mode command it gives the following error.

Config mode locked out until standby initializes

configuration mode locked out by 'PARSER Client'. Please try later

Output of the show redundancy command is;


IDAS-CORE#sh redundancy

Redundant System Information :


Available system uptime = 22 hours, 5 minutes

Switchovers system experienced = 1

Standby failures = 1

Last switchover reason = active unit failed

Hardware Mode = Duplex

Configured Redundancy Mode = Stateful Switchover

Operating Redundancy Mode = Stateful Switchover

Maintenance Mode = Disabled

Communications = Down Reason: Failure

Current Processor Information :


Active Location = slot 2

Current Software state = ACTIVE

Uptime in current state = 22 hours, 4 minutes

Image Version = Cisco IOS Software, Catalyst 4500 L3 Switch Sof

tware (cat4500-IPBASEK9-M), Version 12.2(31)SG, RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

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

Compiled Tue 14-Mar-06 15:38 by ssearch

Configuration register = 0x2101

Peer (slot: 1) information is not available because it is in 'DISABLED' state


i dont know whtat the problem is i am sending attachment please help me out form this i will be thnak full to u

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
lgijssel Tue, 11/13/2007 - 02:22
User Badges:
  • Red, 2250 points or more

The module looks failed indeed.

You can try to eject and re-seat it to see if it comes back up.

Otherwise this looks like a typical DOA (Dead On Arrival). Contact your support representative for a replacement.




This Discussion