[nsp] Holy crap!

Christopher J. Wolff chris at bblabs.com
Fri Jul 18 12:16:28 EDT 2003


Stacy,

IIRC, there was a BGP setting that holds the session in limbo (bgp
dampening?) Having to failover and wait for the sessions to reload will
definitely make the phone ring.  It's probably because the failover
MSFC2 does not have a current route table?

Christopher J. Wolff, VP CIO
Broadband Laboratories, Inc.
http://www.bblabs.com 

-----Original Message-----
From: Stacy J. Brandenburg [mailto:sbranden at redhat.com] 
Sent: Friday, July 18, 2003 8:00 AM
To: Iva Cabric
Cc: Christopher J. Wolff; cisco-nsp at puck.nether.net
Subject: Re: [nsp] Holy crap!

I have also seen this with the MSFC2s in failover.  I run single router 
mode and when a failover is forced, it takes a quite a few seconds for 
the FlexWANs to reinitialize.  This can be seen through the logging from

the switch as well.

I recently updated to 12.1(13)E9.  When I upgraded, the config for two 
OC3's was lost, but my DS3 configs remained.  I have a one of each on 
each of two blades.  That was very odd I thought.  Anyone see that one 
before?

Looking at the config showed the interfaces, but they were shutdown and 
all IP/settings were lost.  Again the DS3's were just fine.

BTW when you failover and the FlewWANs reinitialize, it does kill BGP 
and all sessions need to restart as well from what I have seen.  Kind of

a pisser for wanting stateful failovers....





Iva Cabric wrote:
> On Fri, Jul 18, 2003 at 12:06:42AM -0700, Christopher J. Wolff wrote:
> 
>>Hello again :)
>>
>>I hope I'm not seeing things but something very odd just happened.
>>
>>I installed (C6MSFC2-PSV-M), Version 12.1(19)E1.  When I reloaded the
>>router there were no Flexwan/DS3/DS1 interfaces.  So I'm getting ready
>>to back-rev to a version I know works, when all of a sudden my pager
>>goes off and says all of the Serial lines are back up.  I look at the
>>running config and the serial interfaces are back in there.  
>>
>>Is it possible that flexwan initialization is delayed several minutes
>>after a reload?
> 
> 
> It surely is delayed, but for how long it probably depends on switch
> configuration (number of modules...) and IOS configuration.
> 
> I am testing new Sup720, and when I boot 6500 (only Sup720 and FlexWAN
are
> inside) with empty startup configuration, FlexWAN becomes active after
90
> seconds:
> 
> 00:01:26: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimum
Diagnostics...
> 00:01:26: %DIAG-SP-6-DIAG_OK: Module 1: Passed Online Diagnostics
> 00:01:27: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are
now online
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-- 
========================================================
= Stacy J. Brandenburg                    Red Hat Inc. =
= Sr. Network Engineer           http://www.redhat.com =
= 919-754-3700 x44313              sbranden at redhat.com =
========================================================



More information about the cisco-nsp mailing list