GPN QoS Implementation Dave Hartzell, Raytheon, Greatplains Network, And the USGS.

Need for QoS GPN (at the time) had two GSRs, one in KS and MN. There was also a DS-3 backbone link between the two GSRs, with universities accessing the via 7500s, ATM DS-3s and OC-3s to the ‘nearest’ GSR.

Access to GPN Some access links to the GPN (partial DS- 3s) were filling up. The universities were using H.323 to deliver class sessions, and the access circuits were experiencing congestion.

QoS on the GSRs Goal: Implement Premium Service and Scavenger Service Used MDRR with RED and Priority Queuing Used CAR to more accurately track the occurrences of DSCP 8 and 46.

Monitoring GSRs To monitor the GSRs, the Cisco CAR MIB was used. There isn’t an easy way to track MDRR queuing on the GSRs, at least with the Engine 0 OC-12 POS interface.

GSRs, SNMP Tools, and RRDTool

GSR Performance Right now, since we’re not pushing the OC- 12 to the limit, we haven’t seen any problems with CPU utilization on the Engine 0 cards.

QoS on Access Circuits Next, similar QoS functions needed to be put on the Access routers and the Campus border routers. There was a need to support H.323 video within some of the state networks.

QoS on 7500s IOS 12.1E was selected to support QoS over ATM PVCs. Other versions of IOS didn’t seem to work as advertised. Cisco’s Modular Command Line QoS was used, in conjunction with QoS Device Manager 2.0

QoS on 7500s Also, SNMP Tools and RRDTool were selected for monitoring…

Testing… Testing was performed with IPerf and different DSCPs (ToS bytes) to verify actually queuing and shaping. For the most part, everything (on the 7500s) worked well.

Testing of QoS on ATM PVCs

Analysis For the most part, we tend to see more lower priority (Scavenger Service) traffic. When H.323 video runs for distance education, we do see IP Prec 5. There have been no complains regarding the quality of the video thus far.

Thanks.