new core 6509e , plz check my plan

[rnbhatija]

we recently got a new core 6509e with 5 WS-X6148A-GE-45AF modules

at the moment we have WS-C3560E running as code, connect to 3 (3560) switchs. (hub and spoke)

we have one PBX UC560 with about 35 users. (connected to one of the 3560 switch (spoke))

plan is to use 6509 and ditch all other switch. have it connect to storage with 8 port WS-X6708-10GE  (also on the core)

currently core is not doing intervlan routing. (handing everything to a firewall ) 

so no vlan interfaces are defined. (no ip route)

manager has advised that we dont really need qos as its small network etc. (however i do see qos configured on current core and access)

my plan

i take it i can run same command (as below) on 6509e and it will take , (as its auto qos)

define vlan interfaces

ip routing 

(set vtp transparent). turn off stp? as only core (and maybe 1-2 other spoke switch) 

anything else im missing?

----------------------------------------------------------------------------------------------

current core and access switch (config for qos)

vlan internal allocation policy ascending
!
!
class-map match-all AUTOQOS_VOIP_DATA_CLASS
match ip dscp ef
class-map match-all AUTOQOS_DEFAULT_CLASS
match access-group name AUTOQOS-ACL-DEFAULT
class-map match-all AUTOQOS_VOIP_SIGNAL_CLASS
match ip dscp cs3
!
policy-map AUTOQOS-SRND4-CISCOPHONE-POLICY
class AUTOQOS_VOIP_DATA_CLASS
set dscp ef
police 128000 8000 exceed-action policed-dscp-transmit
class AUTOQOS_VOIP_SIGNAL_CLASS
set dscp cs3
police 32000 8000 exceed-action policed-dscp-transmit
class AUTOQOS_DEFAULT_CLASS
set dscp default
police 10000000 8000 exceed-action policed-dscp-transmit

[Jon Marshall]

QOS on 6500 is supervisor and module dependant.

If you don't need it don't bother with it because otherwise you are in for a lot of reading.

Do not turn off STP, why would you want to, it protects against misconfiguration etc. and does not use up much bandwidth.

If you are migrating the L3 interfaces to the 6500 then you need to reconfigure the link to the firewall and you also need to take care of exchanging routes between the 6500 and the firewall ie. the 6500 needs a default route but the firewall will need to know about all the subnets on the 6500.

And ip routing is enabled by default on the 6500.

Jon

[Reza Sharifi]

Hi Jon,

If you don't need it don't bother with it because otherwise you are in for a lot of reading

That is so true :)

a lot of reading and complications, as almost every Cisco platform/OS does QOS differently.

Thanks,

Reza

[Jon Marshall]

Hi Reza

QOS on switches is one of my least favourite things to be honest.

Too long to learn and too easy to forget :)

Jon

[rnbhatija]

i guess in my mind having core/switch without qos for voice, is bad design/ isn't qos needed when dealing with voice?

also, can you please elaborate on 

thanks much for input.

If you are migrating the L3 interfaces to the 6500 then you need to reconfigure the link to the firewall

[Jon Marshall]

Whether or not you need QOS depends on how the network performs.

I am not saying don't do it I am simply saying that QOS on the 6500 is complicated and takes a certain amount of time to fully understand.

But if you want to deploy it then read the relevant configuration guide and module specs to work out how to do it.

In terms of the link to the firewall you currently have the L3 interfaces for the vlans on the firewall but you want to migrate these to the 6500 so you need to remove them off the firewall.

You should then use a dedicated link to the firewall from the 6500.

You can either use a new vlan/IP subnet for the connection using an SVI on the 6500 or you can use a L3 routed port.

Depends on whether it is one firewall or a pair of firewalls ?

Jon