[c-nsp] Moving Routing from 7206VRX to 6509-E

[Chuck Church]

If you could summarize what features you're using on the 7200, or even a
small sampling of the more important/interesting commands, the list could
probably summarize how difficult it would be to migrate from one to the
other.  Keep in the mind they're totally different devices.  The 7200 uses a
CPU for everything, and is very flexible.  The 6500 needs everything to
happen in ASICs, and there are a lot of caveats (though the 2T is better).
Migrating your QOS will most likely be the most painful.  I wouldn't sweat
the DFC issue too much, the 2T is worlds faster in any mode than a 7200, as
long as the caveats are followed.

Chuck


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of An Nguyen
Sent: Wednesday, December 12, 2012 10:51 AM
To: Phil Mayers
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Moving Routing from 7206VRX to 6509-E

No, I am not familiar with this at all since this is the first time we have
purchased the system. I am starting to go through the 15.1SY release for the
Sup 2T, but haven't complete it yet.
However, I don't think that will give me enough information for what I need
to get a complete picture of the features offered in this chassis.
 
Any information is greatly appreciated.
 
Thanks

>>> 


From: Phil Mayers <p.mayers at imperial.ac.uk> To:An Nguyen
<anguyen at emprisebank.com> CC:<cisco-nsp at puck.nether.net>
Date: 12/12/2012 9:37 AM
Subject: Re: [c-nsp] Moving Routing from 7206VRX to 6509-E On 12/12/12
15:19, An Nguyen wrote:
> Thanks.
> So by default, if DFC is installed, ingress and egress on the same 
> fabric-enabled module, everything is good. If egress is on a different 
> fabric-enabled module, it is still not going through supervisor engine?
> Does it only goes through supervisor engine if egress or ingress is on 
> a non frabric enabled module?

Not quite. You need to distinguish between presence of fabric and presence
of DFC.

I don't have time to write a detailed response, but basically you have:

non-fabric (forwarding lookups on PFC & data - both via bus) fabric-with-CFC
(forwarding lookups on PFC via bus, data via fabric) fabric-with-DFC
(forwarding lookups on DFC, data via fabric)

If you want the "max" performance option, you need fabric-with-DFC in every
slot.

Every packet "goes through the supervisor" because the sup has both the
fabric and the PFC, and every packet goes through one of them.

TBH I can't remember if sup2t even supports non-fabric linecards any more.

As others have said - it sounds like you're not very familiar with this
platform. Be prepared to do some reading - it's got a lot of
platform-specific behaviours.

If you need to provide Emprise Bank with sensitive information such as
account numbers, social security numbers, pin numbers, user names, or
passwords, please use our secure email site at
https://securemail.emprisebank.com. This site will encrypt and send the
information securely. 

For your protection, do not submit sensitive information about yourself via
non-secure email. Information sent without the use of the secure email site
is not encrypted, and we cannot guarantee your privacy. 

This communication is intended only for the person or entity to which it is
addressed. If you are not the intended recipient, you may not make use of
the enclosed information in any way. Please notify Emprise Bank of the error
immediately and delete the email from your computer.