Guest

Design Zone for TelePresence

Medianet Campus Cisco Catalyst 6500 Supervisor 2T Qos Design At-a-Glance

  • Viewing Options

  • PDF (273.2 KB)
  • Feedback
Medianet Campus Cisco Catalyst 6500 Supervisor 2T QoS Design

Table Of Contents

Medianet Campus Cisco Catalyst 6500 Supervisor 2T
QoS Design

Role in Medianet Campus Network

QoS Design Steps

Step 1: Configure Ingress Queuing

Step 2: Configure Egress Queuing

EtherChannel QoS

Cisco Validated Design (CVD)


Medianet Campus Cisco Catalyst 6500 Supervisor 2T
QoS Design


Role in Medianet Campus Network

The Cisco Catalyst 6500 series switches with Supervisor 2Ts are well-suited to the role of distribution- or core-layer switches in medianet campus networks. As such, these switches typically connect directly to other switches or routers, as shown in Figure 1.

Figure 1 Cisco Catalyst 6500 Supervisor 2T Switches in a Medianet Campus Network

QoS Design Steps

There are two main steps to configure QoS on Cisco Catalyst 6500 series switches with Supervisor 2T:

1. Configure Ingress Queuing

2. Configure Egress Queuing

Step 1: Configure Ingress Queuing

The medianet 8Q4T ingress queuing model for the Cisco Catalyst 6500 with Supervisor 2T is shown in Figure 2.

Figure 2 Catalyst 6500 Sup2T (8Q4T) Ingress Queuing Model

Step 2: Configure Egress Queuing

The medianet 1P7Q4T egress queuing model for the Cisco Catalyst 6500 with Supervisor 2T is shown in Figure 3.

Figure 3 Catalyst 6500 Sup2T (1P7Q4T) Egress Queuing Model

EtherChannel QoS

Ingress QoS policies on the Cisco Catalyst 6500 are configured on the logical Port-Channel interface (typically these are simply to enable DSCP trust, which is enabled by default on the Sup2T) , while egress QoS policies are configured on the physical port-member interfaces.

Cisco Validated Design (CVD)

The Cisco Validated Design for Cisco Catalyst 6500 series switches with Supervisor 2T in the role of a distribution- or core-layer switch in a medianet campus network is presented on the reverse.

Note: Highlighted commands are interface specific; otherwise these are global.