[c-nsp] Moving Routing from 7206VRX to 6509-E
An Nguyen
anguyen at emprisebank.com
Sun Dec 16 16:32:13 EST 2012
Would someone please tell me what the commands are to setup a Layer 3 EtherChannel (LACP preferred) for the 4 ports of the 10-GB switch modules on the chassis, and then create several sub-interfaces within this EtherChannel?
Thanks
>>>
From: Nick Hilliard <nick at foobar.org>
To:An Nguyen <anguyen at emprisebank.com>
CC:"<ed at edgeoc.net>" <ed at edgeoc.net>, Chuck Church <chuckchurch at gmail.com>, "<cisco-nsp-bounces at puck.nether.net>" <cisco-nsp-bounces at puck.nether.net>, "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
Date: 12/13/2012 8:51 AM
Subject: Re: [c-nsp] Moving Routing from 7206VRX to 6509-E
On 13 Dec 2012, at 14:12, "An Nguyen" <anguyen at emprisebank.com> wrote:
> Is it possible to configure sub-interfaces/VLAN interfaces from an EtherChannel port?
Yes but there are a bunch of qos limitations for lag interfaces. Even more so than for regular c6500 LAN card interfaces.
Nick
> Thanks
>
>>>>
>
>
> From: "Edward Salonia" <ed at edgeoc.net>
> To:"An Nguyen" <anguyen at emprisebank.com>, <cisco-nsp-bounces at puck.nether.net>, "Chuck Church" <chuckchurch at gmail.com>
> CC:<cisco-nsp at puck.nether.net>
> Date: 12/12/2012 11:41 AM
> Subject: Re: [c-nsp] Moving Routing from 7206VRX to 6509-E
> I think it's also prudent to ask what release train are you currently running? T train? SR? I know you said you were reading up on 15.1SY for the Sup2T. Code train differences can be a big enough pain on their own, changing to a different platform not withstanding.
>
>
> As for qos, check out http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-652042.html
>
> - Ed
> -----Original Message-----
> From: "An Nguyen" <anguyen at emprisebank.com>
> Sender: cisco-nsp-bounces at puck.nether.netDate: Wed, 12 Dec 2012 11:29:35
> To: Chuck Church<chuckchurch at gmail.com>
> Cc: <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] Moving Routing from 7206VRX to 6509-E
>
> Currently, we are using the 7206VRX as a core router with the following features:
> 1. QoS for ShoreTel VoIP traffic (we are not using Cisco VoIP solution)
> 2. Traffic shapping for some replication traffic between our primary data center and disaster recovery data center site.
> 3. Two routing protocols: EIGRP and OSPF.
>
> The QoS we use is very simple as outlined below.
>
> Thanks
> ***************************************
> show policy-map
> Policy Map CCP-QoS-Policy-1
> Class QOS_VOICE
> priority 7 (%)
> set dscp ef
> Class QOS_TELLER
> priority 3 (%)
> set dscp af41
> Class QOS_ATM
> priority 3 (%)
> set dscp af31
> Class QOS_VIDEO
> priority 7 (%)
> set dscp af21
> Class SHAPING_DR
> Average Rate Traffic Shaping
> cir 385000000 (bps)
> Class SHAPING_MIDTOWN
> Average Rate Traffic Shaping
> cir 5000000 (bps)
> Class SHAPING_EBC
> Average Rate Traffic Shaping
> cir 30000000 (bps)
> Class SHAPING_PARKCITY
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_WEST
> Average Rate Traffic Shaping
> cir 5000000 (bps)
> Class SHAPING_WESTLINK
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_WESTWAY
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_BRITTANY
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_SOUTH
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_NEWMARKET
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_VALLEYCENTER
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_B47SOUTH
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_ANDOVER
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_CLEARWATER
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_GODDARD
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_HAYSVILLE
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_MULVANE
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_ELDORADO
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_IOLA
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_MORAN
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_EUREKA
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_TORONTO
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_POTWIN
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_HILLSBORO
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_COUNCILGROVE
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_WAKARUSA
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_ROSEHILL
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_HUMBOLDT
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_CHANUTE
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_AUGUSTA
> Average Rate Traffic Shaping
> cir 5000000 (bps)
> Class SHAPING_HAYS
> Average Rate Traffic Shaping
> cir 3000000 (bps)
> Class SHAPING_SOUTHEAST
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_WEBB21
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_DERBY
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_EAST
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class SHAPING_RIDGE21
> Average Rate Traffic Shaping
> cir 1500000 (bps)
> Class class-default
> bandwidth remaining 80 (%)
>
> Policy Map CCP-QoS-Policy-2
> Class class-default
> Average Rate Traffic Shaping
> cir 400000000 (bps)
> queue-limit 512 packets
> service-policy CCP-QoS-Policy-1
> ****************
> show class-map
> Class Map match-any SHAPING_WEST (id 71)
> Match access-group name SHAPING_WEST
>
> Class Map match-any SHAPING_WESTLINK (id 78)
> Match access-group name SHAPING_WESTLINK
>
> Class Map match-any SHAPING_B47SOUTH (id 68)
> Match access-group name SHAPING_B47SOUTH
>
> Class Map match-any SHAPING_DR (id 74)
> Match access-group name SHAPING_DR
>
> Class Map match-any SHAPING_WEBB21 (id 60)
> Match access-group name SHAPING_WEBB21
>
> Class Map match-any SHAPING_COUNCILGROVE (id 54)
> Match access-group name SHAPING_COUNCILGROVE
>
> Class Map match-any SHAPING_POTWIN (id 55)
> Match access-group name SHAPING_POTWIN
>
> Class Map match-any SHAPING_ELDORADO (id 77)
> Match access-group name SHAPING_ELDORADO
>
> Class Map match-all QOS_REALTIME_VIDEO (id 9)
> Match access-group name QOS_COXVIDEO
>
> Class Map match-all QOS_REALTIME_VOICE (id 10)
> Match access-group name QOS_COXVOICE
>
> Class Map match-any QOS_TELLER (id 42)
> Match dscp af41 (34)
> Match access-group name QOS_TELLER
>
> Class Map match-any SHAPING_HUMBOLDT (id 48)
> Match access-group name SHAPING_HUMBOLDT
>
> Class Map match-any SHAPING_VALLEYCENTER (id 46)
> Match access-group name SHAPING_VALLEYCENTER
>
> Class Map match-any SHAPING_EAST (id 58)
> Match access-group name SHAPING_EAST
>
> Class Map match-any SHAPING_HAYS (id 62)
> Match access-group name SHAPING_HAYS
>
> Class Map match-any SHAPING_EUREKA (id 72)
> Match access-group name SHAPING_EUREKA
>
> Class Map match-any SHAPING_CLEARWATER (id 1)
> Match access-group name SHAPING_CLEARWATER
>
> Class Map match-all QOS_REALTIME_ATM (id 12)
> Match access-group name QOS_COXATM
>
> Class Map match-any SHAPING_PARKCITY (id 65)
> Match access-group name SHAPING_PARKCITY
>
> Class Map match-any SHAPING_BRITTANY (id 67)
> Match access-group name SHAPING_BRITTANY
>
> Class Map match-any SHAPING_WAKARUSA (id 45)
> Match access-group name SHAPING_WAKARUSA
>
> Class Map match-any SHAPING_IOLA (id 52)
> Match access-group name SHAPING_IOLA
>
> Class Map match-any SHAPING_ROSEHILL (id 76)
> Match access-group name SHAPING_ROSEHILL
>
> Class Map match-any class-default (id 0)
> Match any
>
> Class Map match-any SHAPING_SOUTH (id 47)
> Match access-group name SHAPING_SOUTH
>
> Class Map match-any QOS_VIDEO (id 38)
> Match dscp af21 (18)
> Match access-group name QOS_VIDEO
>
> Class Map match-any SHAPING_SOUTHEAST (id 49)
> Match access-group name SHAPING_SOUTHEAST
>
> Class Map match-all QOS_REALTIME_TELLER (id 19)
> Match access-group name QOS_COXTELLER
>
> Class Map match-any QOS_VOICE (id 44)
> Match dscp ef (46)
> Match access-group name QOS_VOICE
>
> Class Map match-any SHAPING_TORONTO (id 73)
> Match access-group name SHAPING_TORONTO
>
> Class Map match-any 50_WEBB (id 37)
> Match access-group name WEBB_50
>
> Class Map match-any QOS_ATM (id 41)
> Match dscp af31 (26)
> Match access-group name QOS_ATM
>
> Class Map match-any SHAPING_GODDARD (id 53)
> Match access-group name SHAPING_GODDARD
>
> Class Map match-any SHAPING_MORAN (id 56)
> Match access-group name SHAPING_MORAN
>
> Class Map match-any SHAPING_RIDGE21 (id 64)
> Match access-group name SHAPING_RIDGE21
>
> Class Map match-any SHAPING_HAYSVILLE (id 79)
> Match access-group name SHAPING_HAYSVILLE
>
> Class Map match-any SHAPING_NEWMARKET (id 61)
> Match access-group name SHAPING_NEWMARKET
>
> Class Map match-any SHAPING_WESTWAY (id 59)
> Match access-group name SHAPING_WESTWAY
>
> Class Map match-any SHAPING_ANDOVER (id 75)
> Match access-group name SHAPING_ANDOVER
>
> Class Map match-any SHAPING_EBC (id 66)
> Match access-group name SHAPING_EBC
>
> Class Map match-any SHAPING_AUGUSTA (id 51)
> Match access-group name SHAPING_AUGUSTA
>
> Class Map match-any SHAPING_CHANUTE (id 69)
> Match access-group name SHAPING_CHANUTE
>
> Class Map match-any SHAPING_HILLSBORO (id 50)
> Match access-group name SHAPING_HILLSBORO
>
> Class Map match-any SHAPING_MIDTOWN (id 57)
> Match access-group name SHAPING_MIDTOWN
>
> Class Map match-any SHAPING_DERBY (id 63)
> Match access-group name SHAPING_DERBY
>
> Class Map match-any SHAPING_MULVANE (id 70)
> Match access-group name SHAPING_MULVANE
>
>>>>
>
>
> From: "Chuck Church" <chuckchurch at gmail.com>
> To:"'An Nguyen'" <anguyen at emprisebank.com>
> CC:<cisco-nsp at puck.nether.net>
> Date: 12/12/2012 11:04 AM
> Subject: RE: [c-nsp] Moving Routing from 7206VRX to 6509-E
> 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.
>
>
> 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.
>
>
> 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.
> _______________________________________________
> 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/
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.
More information about the cisco-nsp
mailing list