[c-nsp] Cat 6000

[W. Kevin Hunt]

I have the Sup1A2G w/ PFC / MSFC2 card in another box not being utilized 
that I can just replace w/ a Sup1a(no pfc/msfc), and I do understand 
this is EOL.  I am just wanting something that can operate quietly and 
run 2 IBGP session to each of my borders, terminate a few client BGP 
sessions and one BGP session to a provider (I can cut down those routes 
and just take a default).  This way if the New Orleans portion of my 
ring goes down, the folks connected to the ring with the Cat6k will 
still have communication with the outside world.

--
W. Kevin Hunt

"There are 10 kinds of people in this world, those that understand 
binary and those that do not."

Tim Stevenson wrote:
> At 05:15 AM 4/25/2006, W. Kevin Hunt pronounced:
>> I have a 12k and an M40 at our border taking 5 full BGP feeds.  We want
>> to add another border router capable of an OC3 or DS3 feed in another
>> city for disaster prepardness purposes (We are in New Orleans and are
>> getting ready for the next hurricane season).
>> I have a Cat 6k, can I just add a MSFC2 w/ 512megs of RAM/PFC to my
>> Sup1A and a flexwan module to pick up the ds3 or oc3?
> 
> Only if there is already an MSFC (1) on it, Sup1A is NOT field 
> upgradeable from sup1a/(EARL4) or sup1a/PFC to MSFC2. Also note that 
> Sup1A is EOS.
> 
> Tim
> 
>> I have no experience w/ the MSFC2 or flexwan module so if there are any
>> gotcha's I'd like to know, but it'd sure be nice to use something in my
>> closet as opposed to buying another 12k or M5.
>>
>> -- 
>> W. Kevin Hunt
>>
>> _______________________________________________
>> 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/
> 
> 
> 
> Tim Stevenson, tstevens at cisco.com
> Routing & Switching CCIE #5561
> Technical Marketing Engineer, Catalyst 6500
> Cisco Systems, http://www.cisco.com
> IP Phone: 408-526-6759
> ********************************************************
> The contents of this message may be *Cisco Confidential*
> and are intended for the specified recipients only.
>