[c-nsp] second supervisor engine on 7609
Brad Swanson
lakepepin at hotmail.com
Tue May 10 08:35:16 EDT 2005
I second the ROMMON issue, been there done that... Everything worked fine
after getting the RP to boot properly. Did not have to put the card into a
second chassis though, just fiddled with it on the live box with no
problems.
Should the standby be 0x2 or 0x2102?
>From: Ian Cox <icox at cisco.com>
>To: Vects <alexc at actcom.co.il>, cisco-nsp at puck.nether.net
>Subject: Re: [c-nsp] second supervisor engine on 7609
>Date: Tue, 10 May 2005 04:08:12 -0700
>
>Does the 2nd Supervisor go any further than the output provided
>below. The output below just shows the SP side booting of the 2nd
>supervisor. The RP side also has to boot up, does it stop at a rommon
>prompt? if it does change the configuration register to 0x2 and type
>reset to get the RP to boot on the backup. -> You may want to get the
>second supervisor booting correctly in another chassis, and when it
>is ok, put it in this chassis.
>
>
>Ian
>
>
>At 01:14 PM 5/10/2005 +0300, Vects wrote:
> >Hi,
> >I'm encountered a problem with activation of second supervisor engine on
> >our 7609, it looks like secondary supervisor engine is booting well
> >after hot insertion to chassis but it's not recognized by system, I've
> >got 'Supervisor-Other' by 'sh module' command, see below.
> >Could somebody help me with it?
> >I don't want to reboot router, it will disconnects many users of ours.
> >
> >Thanks, Alexc
> >
> >sh module output:
> >Mod Ports Card Type Model
>Serial No.
> >--- ----- -------------------------------------- ------------------
> >-----------
> > 1 2 Catalyst 6000 supervisor 2
> > (Active) WS-X6K-S2U-MSFC2 SAD054600JF
> > 2 0 Supervisor-Other Unknown
>Unknown
> > 3 0 2 port adapter
> > FlexWAN WS-X6182-2PA SAD044207FV
> > 4 8 8 port 1000mb
> > ethernet WS-X6408-GBIC SAD04130F1Y
> >
> >Mod MAC addresses Hw Fw Sw
>Status
> >--- ---------------------------------- ------ ------------
> >------------ -------
> > 1 0001.6415.8aa6 to 0001.6415.8aa7 3.2 6.1(4) 12.1(20)E2
>Ok
> > 2 0000.0000.0000 to
> > 0000.0000.0000 0.0 Unknown Unknown Unknown
> > 3 0003.32b9.151a to 0003.32b9.1559 1.3 12.1(20)E2 12.1(20)E2
>Ok
> > 4 00d0.d337.cf48 to 00d0.d337.cf4f 2.4 5.1(1)CSX 8.2(0.58)TFW
>Ok
> >
> >Mod
> >Sub-Module Model Serial Hw
>Status
> >--- --------------------------- --------------- ---------------
> >------- -------
> > 1 Policy Feature Card 2 WS-F6K-PFC2 SAD054506NB 2.0
>Ok
> > 1 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAD054504DY 1.2
>Ok
> > 2 Policy Feature Card 2 WS-F6K-PFC2 SAL082292PH 3.4
>Other
> >
> >Mod Online Diag Status
> >--- -------------------
> > 1 Pass
> > 2 Unknown
> > 3 Not Applicable
> > 4 Pass
> >
> >sh version output:
> >Cisco Internetwork Operating System Software
> >IOS (tm) c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(20)E2, EARLY
> >DEPLOYMENT RELEASE SOFTWARE (fc1)
> >TAC Support: http://www.cisco.com/tac
> >Copyright (c) 1986-2004 by cisco Systems, Inc.
> >Compiled Fri 30-Jan-04 22:36 by pwade
> >Image text-base: 0x40008F90, data-base: 0x41850000
> >
> >ROM: System Bootstrap, Version 12.1(4r)E, RELEASE SOFTWARE (fc1)
> >BOOTLDR: c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(20)E2, EARLY
> >DEPLOYMENT RELEASE SOFTWARE (fc1)
> >
> >rtr76 uptime is 8 weeks, 1 day, 8 hours, 16 minutes
> >Time since rtr76 switched to active is 8 weeks, 1 day, 8 hours, 17
> >minutes
> >System returned to ROM by power-on (SP by power-on)
> >System restarted at 01:47:07 UTC Mon Mar 14 2005
> >System image file is "slot0:c6sup22-psv-mz.121-20.E2.bin"
> >
> >cisco OSR-7609 (R7000) processor (revision 3.1) with 458752K/65536K
> >bytes of memory.
> >Processor board ID TBA05450364
> >R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3
> >Cache
> >Last reset from power-on
> >X.25 software, Version 3.0.0.
> >Bridging software.
> >1 FlexWAN controller (2 ATM).
> >62 Virtual Ethernet/IEEE 802.3 interface(s)
> >10 Gigabit Ethernet/IEEE 802.3 interface(s)
> >2 ATM network interface(s)
> >381K bytes of non-volatile configuration memory.
> >
> >16384K bytes of Flash internal SIMM (Sector size 512K).
> >Configuration register is 0x102
> >
> >
> >output on console of second supervisor engine:
> >Autoboot executing command: "boot
> >slot0:"
> >
> >
> >Self decompressing the image : ###..### [OK]
> >
> >
> > Restricted Rights Legend
> >
> >
> >Use, duplication, or disclosure by the Government
> >is
> >subject to restrictions as set forth in
> >subparagraph
> >(c) of the Commercial Computer Software -
> >Restricted
> >Rights clause at FAR sec. 52.227-19 and
> >subparagraph
> >(c) (1) (ii) of the Rights in Technical Data and
> >Computer
> >Software clause at DFARS sec.
> >252.227-7013.
> >
> >
> > cisco Systems,
> > Inc.
> > 170 West Tasman
> > Drive
> > San Jose, California 95134-1706
> >
> >
> >
> >Cisco Internetwork Operating System
> >Software
> >IOS (tm) c6sup2_sp Software (c6sup2_sp-SPV-M), Version 13.1(20)E2,
> >EARLY DEPLOYM
> >ENT RELEASE SOFTWARE
> >(fc1)
> >TAC Support:
> >http://www.cisco.com/tac
> >Copyright (c) 1986-2004 by cisco Systems,
> >Inc.
> >Compiled Fri 30-Jan-04 23:13 by
> >pwade
> >Image text-base: 0x40020F90, data-base:
> >0x4097A000
> >
> >
> >
> >
> >00:00:02: %PFREDUN-6-STANDBY: Initializing as STANDBY
> >processor
> >00:00:03: %C6K_PLATFORM-5-MISMATCH: 'sup-bootflash' device
> >programming algorithm
> >mismatch detected on SP (module: 2), formatting is
> >recommended.
> >00:00:08: %OIR-SP-STDBY-6-CONSOLE: Changing console ownership to
> >route processor
> >
> >
> >_______________________________________________
> >cisco-nsp mailing list cisco-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
>_______________________________________________
>cisco-nsp mailing list cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list