Migrating edge routing from Cisco 2901 to Extreme X690's

[Keith9]

We are looking to migrate our branch routing from a Cisco 2901 to our core switches which are two cores containing Extreme X690's with the core licence.

To do so I was wondering how I could replicate a bandwidth throttling feature that we use today between our HQ and branch 2901 routers.

On the 2901 we have service-policy output applied to interfaces and then we have these policy maps that do shape average. There is also something like this:
class-map match-any WEBTraffic
match access-group name http
match access-group name https
class-map match-all VR
match access-group name VRPorts

ip access-list extended VRPorts
permit tcp any any eq 44046
permit tcp any any eq 31031

ip access-list extended http
permit tcp any any eq www
ip access-list extended https
permit tcp any any eq 443


I know some telco providers drop packets if they exceed the subscribed rate. We do not have that issue on a Comcast metro-e connection, but I do not want to (by trial and error) experience that migrating some Windstream metro-e connections.

Besides that, above shows that we can identify and slightly limit web browsing traffic if we want, by looking for port 80 and 443 traffic. Plus we limit VMWare vSphere replication traffic which goes over ports 44046 and 31031 as shown above in access-list VRPorts.

We currently limit that to 60mbps out of a 100mbps wan connection to our DR site.

[Keith9]

Ok we are already using some of the queues for voice and signaling traffic. Thats a shame you are maxed out at 7 queues if your doing stacking.

Example of the first few uplink ports on one of my X690
Port QP1 QP2 QP3 QP4 QP5 QP6 QP7 QP8
Pkt Pkt Pkt Pkt Pkt Pkt Pkt Pkt
Xmts Xmts Xmts Xmts Xmts Xmts Xmts Xmts
========================================================================================================
1:1 6313325376 10100 37732695 0 482924457 0 0 248136656
1:2 1037726751 0 10902750 0 417439093 0 0 143071988
1:3 14741035996 0 417386 0 722564 0 0 162212439
1:4 14211 0 502 0 12465 0 0 595
1:5 3411132878 2051 1053663 0 471431 0 0 88042469
1:6 2846295857 2053 67194717 0 6223666 1 0 84809948
1:7 876417270 2053 1367866 0 601542 0 0 84750745
1:8 41703903291 2053 1056034 0 112630 0 0 84744981


It looks like I only have QP4, QP6 and QP7 to work with. But then I look at my config and see this
create qosprofile "QP3"
create qosprofile "QP5"
configure qosprofile QP3 maxbuffer 100 weight 1
configure qosprofile QP5 maxbuffer 100 weight 1
configure qosprofile QP3 minbw 0 maxbw 100 ports 1:1
configure qosprofile QP5 minbw 0 maxbw 100 ports 1:1
enable diffserv examination port 2:1
disable dot1p examination port 2:1
(last 4 lines above are on every port).

configure diffserv examination code-point 24 qosprofile QP3
configure diffserv examination code-point 26 qosprofile QP3
configure diffserv examination code-point 46 qosprofile QP5


So with all of that it looks like QP3 and QP5 are my voice and signaling, QP1 is a default queue I guess, and QP8 must be the ISC traffic inter-stack and between my two stacks maybe, like the mlag or maybe network protocol stuff like OSPF?

Not sure what little bit of traffic incremented the counters in QP2.

[Erik_Auerswald]

Hi Keith,

just for the rate limiting the WAN connection you can use the configure ports [port_list | port_group]rate-limit egress [no-limit | cir-rate [Kbps | Mbps | Gbps] {max-burst-size burst-size [Kb | Mb]}] command.

To classify traffic and preferring some traffic over the other, you first need to create and configure QoS Profiles (EXOS allows up to 8 of those, 7 if stacking is used), and then use ACLs (or existing CoS or DSCP markings) to assign traffic to the QoS profiles.

Please take a look at the QoS chapter of the EXOS User Guide for detailed information.

If you disregard the flow control commands, the GTAC Knowledge article How to configure Priority Flow Control (https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-Priority-Flow-Control/) gives an example QoS configuration including rate limiting you may be able to use as a reference.

Thanks,
Erik