[c-nsp] Upgrading Catalyst 6500 from 720-3B to 720-3BXL

[Fernando García Fernández]

Hello John and Gert

I assume that I must reboot. But what I wanted is to have a procedure that minimizes the downtime and allows me to go back if anything goes wrong.

If I don’t activate redundancy, could I copy the configuration from the active RSP to the new one so when I reboot with it (shuting down, removing old RSP) It can go up with the new one?

And yes, I now I will have to tune it up to avoid the 500k routes limit.

The final configuration will be just the
720-3BXL 
and a 
WS-X6748-GE-TX

(we are going to have another 6509 chassis for redundancy)

Regards

> El 28/4/2015, a las 18:12, Jon Lewis <jlewis at lewis.org> escribió:
> 
> On Tue, 28 Apr 2015, [utf-8] Fernando García Fernández wrote:
> 
>> Hello all
>> 
>> Iÿÿve tried to google the solution to one doubt I have, but couldnÿÿt find it.
>> 
>> Iÿÿm going to upgrade a Catalyst 6509 from a 720-3B to a new 720-3BXL so we can use it for BGP routing with full Internet route table.
>> 
>> The procedure Iÿÿm designing is:
>> 
>> - create a CF for the 720-3BXL with the same IOS of the 720-3B
>> 
>> - Insert the 720-3BXL y the second slot of the 6500
>> 
>> - activate redundancy:
>> conf t
>> redundancy
>> mode sso
>> end
>> show redundancy
>> 
>> - switch processing to 720-3BXL
>> 
>> redundancy force-switchover
>> 
>> - disable redundancy
>> 
>> conf t
>> redundancy
>> mode none
>> end
>> 
>> - remove 720-3B
>> 
>> Iÿÿm almost sure that a 720-3B and a 720-3BXL can coexist in a chassis. Is correct?
>> 
>> Also is the procedure correct?
> 
> Even if this worked, you'd still end up having to reboot.
> 
> In order to put full routes on the 3BXL, you're going to have to manually tune the v4/v6 mls cef maximum-routes split (which requires a reboot to take affect).
> 
> According to http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/107258-C6K-PFC-DFC-CFC.html
> your plan is not going to work.
> 
> Q. Can the Supervisors with different PFC versions form redundancy?
> 
> A. You cannot use one type of PFC3 (PFC3BXL, PFC3B, or PFC3A) on one supervisor engine and a different type on the other supervisor engine for redundancy. You must use identical policy feature cards for redundancy.
> 
> ----------------------------------------------------------------------
> Jon Lewis, MCP :)           |  I route
>                             |  therefore you are
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________