Specifications

10-6
Cisco IGX 8400 Series Provisioning Guide, Release 9.3.3 and Later Releases
OL-1166-04
Chapter 10 Cisco IGX 8400 Series IP Service
IP Service—Functional Overview
Service Class Templates
Note Service class templates (SCTs) are primarily used with virtual circuits (VCs) and must be used when
configuring the IGX to work with a VSI master in a label switch controller (LSC).
SCTs provide a way to map a set of standard connection protocol parameters to different hardware
platforms. For example, SCTs for the BPX and the IGX are different, but the BPX and IGX can still
deliver equivalent CoS for full QoS.
On the IGX, the NPM stores a set of SCTs. When a UXM or UXM-E is initially configured, the
appropriate SCTs are downloaded to the card. Later, if you configure a new interface on the card, the
appropriate SCTs for that new interface will also be downloaded to the card.
Each SCT contains the following information:
• Parameters necessary to establish a connection, including entries such as UPC actions, various
bandwidth-related items, and per-VC thresholds (for VCs)
• Parameters necessary to configure associated CoS buffers (Qbins) to provide QoS support
Each SCT has an associated Qbin mapping table, which manages bandwidth by temporarily storing cells
and serving them to the interface based on bandwidth availability and CoS priority.
Note The default SCT, Template 1, is automatically assigned to a virtual interface (VI) when you configure
the interface.
The following nine SCTs are available for assignment to a VSI:
• VSI special type (Template 1, default)
• MPLS1
• ATMF_tagcos_1
• ATMF_tagcos_2
• ATM F_tagAB R_1
• ATM F_tagAB R_2
• ATMF_tagcos_tagABR_1
• ATMF_tagcos_tagABR_2
For more information on how SCTs work, see Figure 10-4. For information on supported SCT
characteristics, see Table 10-2.
Caution SCTs can be reassigned on an operational interface, triggering a resynchronization process between the
UXM or UXM-E and the controllers. However, for a Cisco MPLS VSI controller, reassignment of an
SCT on an operational interface will cause all connections on the card to be resynchronized with the
controller, and can impact service.