Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

OUTPUT PROBLEM IN 6509-SUP1

Hi!

Another problem on my 6509sup1-2GE.LOOK WHAT HAPPEN TO THE 6509.

HAVE A LOOK:

Router#remote login switch

Cannot remote to switch

......................................

Router#show boot

BOOT variable = slot0:c6sup11-dsv-mz.121-20.E2,1

CONFIG_FILE variable does not exist

00:02:17: %ONLINE-SP-6-INITFAIL: Module 1: Failed to synchronize Port asic

00:02:17: %ONLINE-SP-6-INITFAIL: Module 1: Failed to synchronize Port asic

00:03:00: %ONLINE-SP-6-TIMER: Module 7, Proc. 0. Failed to bring online because

of timer event

00:03:00: %C6KPWR-SP-4-DISABLED: power to module in slot 7 set off (Reset)

00:03:02: %ONLINE-SP-6-TIMER: Module 2, Proc. 0. Failed to bring online because

of timer event

00:03:02: %C6KPWR-SP-4-DISABLED: power to module in slot 2 set off (Reset)

00:03:02: %ONLINE-SP-6-TIMER: Module 3, Proc. 0. Failed to bring online because

of timer event

00:03:02: %C6KPWR-SP-4-DISABLED: power to module in slot 3 set off (Reset)

00:03:03: %ONLINE-SP-6-TIMER: Module 4, Proc. 0. Failed to bring online because

of timer event

00:03:03: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Reset)

00:03:03: %ONLINE-SP-6-TIMER: Module 5, Proc. 0. Failed to bring online because

of timer event

00:03:03: %C6KPWR-SP-4-DISABLED: power to module in slot 5 set off (Reset)

00:03:04: %ONLINE-SP-6-TIMER: Module 6, Proc. 0. Failed to bring online because

of timer event

00:03:04: %C6KPWR-SP-4-DISABLED: power to module in slot 6 set off (Reset)

t4 : 60315970, t5 : 0000001C, t6 : 6F6E202C, t7 : 00000006addressddressby is no

shutdownutdownigu

!t

interface Fast

s0 : 00000000, s1 : 00000000, s2 : 621E20E8, s3 : 621E20E8ress t

shutdownon

shutd

!n

interface FastEthernet7/8abit

s4 : 622E8C8C, s5 : 00000040, s6 : 60031408, s7 : 602B7E24nh-sp#?

!h

interface FastEthernet7/9ce GigabitEthernet5

t8 : 00000000, t9 : 00000000, k0 : 00000000, k1 : 00000000nterface FastEthernet7/10terface GigabitEthernet5/7

no ip

gp : 618C1DA0, sp : 622ACF88, s8 : 00008847, ra : 6030F538Ethernet7/11

interface GigabitEtherne

no ip addressinter

EPC : 603113BC, ErrorEPC : BFC016DC, SREG : 3400E103cc

!s

interface GigabitEth

no ip address-List entryint

MDLO : 00000000, MDHI : 00000000, BadVaddr : BFBBB7BEnterface Gigabi

no ip addresses

00

shutdownI

Cause 00000024 (Code 0x9): Breakpoint exceptionr

interface Gi

no ip address3tflash:c6msfc

sh

Writing crashinfo to bootflash:crashinfo_20060622-092152a

!w

interfac

no ip addresset6

shutdo

!i

interface FastEthernet7/37 Star

00:01:02: %C6KPWR-SP-4-PSOK: power supply 1 turned on.yt

Config

!a

interface FastEthernet7/38

of timer event

00:03:02: %C6KPWR-SP-4-DISABLED: power to module in slot 2 set off (Reset)

00:03:02: %ONLINE-SP-6-TIMER: Module 3, Proc. 0. Failed to bring online because

of timer event

00:03:02: %C6KPWR-SP-4-DISABLED: power to module in slot 3 set off (Reset)

00:03:03: %ONLINE-SP-6-TIMER: Module 4, Proc. 0. Failed to bring online because

of timer event

00:5

00:03:45: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure

console debugging output.

00:03:45: %OIR-SP-6-CONSOLE: Changing console ownership to switch processor

*** System received a Software forced crash ***

signal= 0x17, code= 0x24, context= 0x61a3c9b4

PC = 0x60128ca8, Cause = 0x1820, Status Reg = 0x34018002

System Bootstrap, Version 5.3(1)

Copyright (c) 1994-1999 by cisco Systems, Inc.

c6k_sup1 processor with 65536 Kbytes of main memory

rommon 1 >

WHAT CAUSE THIS PROBLEM,HOW CAN I SOLVED THIS MATTER

1 REPLY
Silver

Re: OUTPUT PROBLEM IN 6509-SUP1

The new module could be missing the maintenance partition. Complete these steps to fix the problem:

1. Issue the power enable module command to verify if adequate power is available in the system to turn the power on for a module that was previously powered down. If there is not enough power available, the module status changes from power-down to power-deny.

2. Issue the show module command to check the status of the module.

Refer to Power Management for Catalyst 6000 Series Switches in cisco.com website

482
Views
0
Helpful
1
Replies
CreatePlease login to create content