Cisco WAN Manager User's Guide, 12.0 - Configuring Service Class Templates [Cisco WAN Manager]

Table Of Contents

Configuring Service Class Templates

SCT Overview

SCT File Types

Comparing SCT and Connection Manager Graphical User Interface Templates

Understanding SCT Templates

Understanding Connection Manager Graphical User Interface Templates

Loading SCT Files

Managing with the Service Class Template Manager

Launching the Service Class Template Manager

Navigating with Service Class Template Manager

Service Class Template Manager Main Window

Service Class Template Manager Menu Bar

Service Class Template Manager Toolbar

Displaying a SCT File

Declaring SCT Sync-Up

Creating a SCT File

Modifying a SCT File

Renaming the SCT File

Removing and Deleting the SCT File

Confirming Version and Data Discrepancy

Downloading the SCT File to a Node

Verifying the Download of the SCT Through the Switch

Associating a SCT File to a Card or Port

Notifying the SCT Application for the SCT Activity on the Node

Configuring Service Class Templates

This chapter describes the CWM Service Class Template (SCT) Java based application. In Release 12 of CWM, the SCT application maps standard connection protocol parameters for AXSM, AXSM/B, AXSM-E, AXSM-XG, FRSM-12 and PXM1-E cards using a set of data structures that associate virtual switch interface (VSI) service types to sets of preconfigured virtual channel (VC), and class of service buffer (CoSB) parameters.

Contents of this chapter include:

•SCT Overview

•Comparing SCT and Connection Manager Graphical User Interface Templates

•Managing with the Service Class Template Manager

SCT Overview

The Service Class Template application, which is a CWM process, creates SCT files that are loaded to nodes, and associated with interfaces on cards within the nodes. SCT allows users and network operators to configure AXSM, AXSM/B, AXSM-E, AXSM-XG, FRSM-12 and PXM1-E cards. Specifically, users or network operators can use the SCT application to create, modify, delete, download, and associate SCT files to cards and ports. Creating a new SCT involves configuring ATM parameters for specific classes of service to suit the special needs of your customers. For example, if you have customers with special policing or shaping requirements, you can create an SCT to meet those specifications. Differing SCTs can also be assigned depending on the role of a particular port, for example, a line, trunk, or virtual trunk.

You can define a card SCT and port SCT. When you add a soft permanent virtual circuit (SPVC), the card SCT determines the default ingress characteristics of the connection. The port SCT determines the default egress characteristics of the connection. Ingress refers to the interface between the card and internal switch plane(s); whereas, egress refers to the interface across where traffic enters and leaves the switch.

For each card, you can assign a card SCT that defines the connection characteristics between the card and the switch bus. All cards share the same SCT or they can each have a different SCT. When you add a port, you assign a port SCT that defines the connection characteristics between the port and the customer premises equipment (CPE). All ports can share the same SCT or they can each have a different SCT.

The card and port SCT files reside on the PXM45 hard drive. An SCT must be on the hard drive before you can assign it to a card or port. You can have up to 255 SCT files on your switch.

During data transmission, statistics collect at different points. Figure 6-1 shows data traveling through two cards, which are connected across the bus.

Figure 6-1 Data Flow Through Two Cards Connected Across a Bus

The ingress direction describes traffic that travels toward the bus. The egress direction describes traffic that travels from the bus.

The numbers in Figure 6-1 correspond to the points at which statistics are collected. Points 1-7 show data on the incoming path with policing. Points 8-13 show data on the return path without policing.

•1—Data enters the UNI/NNI port card (ingress).

•2—Data is queued (ingress).

•3—Data is scheduled for admission onto the bus (ingress).

•4—Data is queued for going onto the bus (ingress).

•5—Data is queued for being taken off the bus (egress).

•6—Data is processed on the trunk card (egress).

•7—Data is queued for going out the trunk (egress).

•8—Data enters the card from the trunk (ingress).

•9—Data is scheduled for admission onto the bus (ingress).

•10—Data is queued for going onto the bus (ingress).

•11—Data is queued for being taken off the bus (egress).

•12—Data is processed on the port card (egress).

•13—Data is queued for going out the port (egress).

Note The data flow process can vary depending on the card type.

The SCT provides default characteristics for a connection that includes bandwidth, policing, and queuing parameters. You can change from the connection defaults when you add the connection, or after the connection is added. Changing a connection does not affect the SCT or any connections that were defined by the SCT.

The SCT provides the following two classes of data that are contained in a subtemplate:

•VC Descriptor—Specifies that the VC Descriptor Template is a component of a SCT that contains platform specific VC configuration, and is indexed primarily by service type. A service type is a concept for grouping connections that share a common set of traffic characteristics and quality of service (QoS) requirements. The VC Descriptor Template defines SCT parameters that are applied to all VCs and that match a specified Service Type. As defined in the SCT MIB for the AXSM card, a VC Descriptor for AXSM consists of 36 elements, including the SCT ID, which the VC Descriptor is a part, the Service Type, and the CoSB (Class of Service Buffer) number, which indicates the CoSB used for the connections.

The VC Descriptor parameters are necessary to establish a SPVC connection, and includes entries such as UPC actions, various bandwidth related items, per connection thresholds, and so forth.

•CoSB Descriptor—Specifies the CoSB is a buffer or queue that serves connections with similar QoS requirements. A CoSB Descriptor Template contains CoSB configurations, with eighteen attributes for AXSM cards indexed by CoSB number.

When you use CiscoView or the switch command line interface (CLI) to activate an interface on the card, you can define the SCT that is assigned to the interface. When a connection is added, the service type applied to the connection determines the VC parameters that the CoSB used for the connection. For example, the connection setup request is for a CBR.1 connection. The VC Descriptor subtemplate defines the VC parameters that includes the policing action, VC queue depth, congestion discard mechanism, and threshold. The VC Descriptor also defines the CoSB used for that class of service type. For example, CBR.1 uses CoSB 1.

If the SCT is not defined when the card or port is activated, the system applies the default SCTs. Similarly, if you activate a port using an unavailable SCT, the defaults are applied.

SCT File Types

This section describes the types of SCT files.

The following types of SCT files by ID are:

•SCT ID of 0—Specifies the default SCTs that are not configurable on the switch side.

•SCT ID from 1 to 99—Specifies the standard, Cisco distributed SCT. You can modify the parameters.

•SCT ID from 100 to 255—Specifies the custom SCTs that are created using CWM. You can create, modify, and delete custom-made SCTs.

Note All of the features and capabilities are possible only on nodes running the switch software version 3.x or higher. Release 12 of CWM SCT management for 2.x based switches will remain the same as Release 10.5 of CWM.

A number of preconfigured default files, which contain SCT files with SCT ID equal to zero, are available. Default templates are not cumulative.

The following Cisco distributed SCT ID default file types are

•SCT2 and SCT3 are used for PNNI.

•SCT2 and SCT4 are used for policing.

•SCT3 and SCT5 are used for no policing.

•SCT4 and SCT5 are used for PNNI and MPLS.

For a detailed list of SCT default file types, refer to the Cisco MGX 8850 (PXM1E/PXM45),
Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4.

Comparing SCT and Connection Manager Graphical User Interface Templates

This section compares SCT templates with Connection Manager Graphical User Interface (CMGUI) templates.

CMGUI templates save parameters that are specific to connections, for example, traffic shaping parameters. SCT templates save parameters that are applicable to all connections on a given card and port.

Both of the CMGUI and SCT templates are stored in the CWM database and are not switch information. However, once the templates are stored in the database, the template can be retrieved from the CWM database to apply the stored values.

Understanding SCT Templates

SCT templates are card (ingress) and port (egress) based, and all five cards that support SCT, for example, AXSM, AXSM-E, AXSM-XG, FRSM12, and PXM1E, have two built in default templates:

•one default SCT file for card

•one default SCT file for port

Both of these default templates have the SCT ID of 0 (zero).

An SCT template that is saved from the CWM Service Class Template application is stored on the switch only after it has been downloaded to a node using the SCT GUI. Until then, the SCT template information will remain as CWM database information only. This applies to the CWM workstation on which the template was saved, and is user data which will be deleted from the CWM database upon a coldstart -F.

Note The SCT templates saved from the SCT GUI have SCT IDs greater than 100; whereas, the Cisco-provided SCTs have IDs from 1 to 99.

Note None of the narrowband service modules support SCT templates.

Understanding Connection Manager Graphical User Interface Templates

CMGUI templates are stored only on the CWM database, which provides you with the flexibility to load the parameters for new connections with the values that have already been stored in the CMGUI templates. CMGUI templates are applicable for all types of connections from the CWM Connection Manager application, and there is no limitation on the types of connections for which CMGUI templates can be save. All of the connection types and service types, which can be provisioned from the CWM Connection Manager application, can have CMGUI templates associated with them. The only restriction for CMGUI templates is that the local and remote card types need to match the connection types from where the connection template was saved. Also, CMGUI templates are user data; therefore, they are deleted from the database upon a coldstart -F.

Note Coldstart without the -F option, or a coldstart with the -U option will not erase Connection Templates, SCT Templates or Connection Descriptor from the database. Only a coldstart -F deletes the above data from the database.

Loading SCT Files

The CWM tool provides the sctLoad command to load the SCT files onto CWM.

Note•The sctLoad command is not used for Release 3.x based switches or higher.

•The sctLoad command is used only for Release 2.x based switches.

•The sctLoad command does not support PXM1E and FRSM12 SCT files.

To load SCT information to the CWM database, complete the following procedure:

Step 1 Open a terminal window.

Step 2 When you establish a CLI session, you must:

a. Enter the applicable username at the prompt.

b. Enter the applicable password at the prompt.

Step 3 Enter the ftp command to copy the Cisco-provided SCT files from the switch to the CWM workstation to the ~svplus/sct-file/1 directory.

Step 4 Enter the sctLoad command to retrieve SCT information to CWM.

After the SCT files upload, click the SCT tab of the Navigator panel from the SCT main window
(see Figure 6-2) to display the retrieved SCT files.

Managing with the Service Class Template Manager

This section describes how to create custom SCTs and configure standard and custom SCTs.

You must use the SCT manager to create and modify a SCT file. You cannot use a text editor or any other tool to change the parameters in the SCT. The SCT manager provides card and port template files that you can use to create new SCTs.

The following configuration tasks are used:

•Launching the Service Class Template Manager

•Navigating with Service Class Template Manager

•Displaying a SCT File

•Declaring SCT Sync-Up

•Creating a SCT File

•Modifying a SCT File

•Removing and Deleting the SCT File

•Confirming Version and Data Discrepancy

•Downloading the SCT File to a Node

•Associating a SCT File to a Card or Port

•Notifying the SCT Application for the SCT Activity on the Node

Launching the Service Class Template Manager

To launch the Service Class Template Manager (see Figure 6-2), choose Apps > Service Class Template Manager or click the Service Class Template Manager icon from the toolbar.

Figure 6-2 Service Class Template Main Window

1

Menu bar

2

Toolbar

3

Navigator panel

4

Path label

5

VC subtemplate

6

CoSB subtemplate

7

Button panel

8

Status bar

To determine the logical sequence for loading and associating SCT files from the SCT main window (see Figure 6-2), you must:

1. Click Save As to create and save a new SCT file.

2. Click Save to modify and save the SCT under the existing name and the modifications.

3. Click Download to download the SCT file to the specified node.

4. Click Associate to associate the SCT with the card or port.

Navigating with Service Class Template Manager

The following sections describe the navigation of the Service Class Template Manager:

•Service Class Template Manager Main Window

•Service Class Template Manager Menu Bar

•Service Class Template Manager Toolbar

Service Class Template Manager Main Window

After launching the Service Class Template Manager, you will see the SCT File in the left panel of the window (see Figure 6-2). The Service Class Template Manager main window includes eight options
(see Table 6-1).

Table 6-1 Service Class Template Manager Main Window Options

Options

Task

Menu bar

For a definition, see Table 6-2.

Toolbar

For a definition, see Table 6-3.

Navigator panel

Displays a tree view that allows data to be visually displayed in a hierarchical file format.

If you have authorized permission, a SCT file is modified even if the SCT file has been downloaded and associated to a card and port. You have the following two options when modifying a SCT file:

•Click Save Local Only to perform a modification of a SCT file locally.

•Click Save to perform a modification of a SCT file.

If the local modification is selected, the SCT file is modified and saved in the CWM database only.

The following tabs are displayed:

Tab

Task

SCT

Displays the nodes by the SCT file. Nodes are displayed by expanding the SCT file node. Each SCT file can have more than one node since each SCT file is downloaded to more than one network node. In addition, the SCT file can also be associated by more than one card node and more than one port node.

If the SCT file node is not a leaf node, it is expanded to display network nodes, card nodes, and port nodes. The expansion cycle is repeated for each subnode that is not a leaf node for the following operations:

•If the SCT file node is a leaf node and cannot be expanded, the SCT file is created, but is not downloaded to any network node.

•If the network node is a leaf node and cannot be expanded, the SCT file is downloaded to a node, and is not associated with any card or port of that network node.

•If the card node is a leaf node and cannot be expanded, the SCT file is downloaded to the node and is associated with the card node. However, it is not associated with any ports of that card node.

The SCT tab is the default tab.

Navigator panel

Node

Views SCT files by the network node hierarchy. When network nodes are expanded, subnodes are displayed. A network node includes the SCT file node, card node, and port node. If a subnode is a leaf node, it does not have a reference and cannot be expanded.

If the card node is not a leaf node, it is expanded to view the associated SCT file and ports. If the port node is not a leaf node, it is also expanded to view the associated SCT file node.

Path label

Specifies the location of the selected SCT card or port file.

VC subtemplate

Displays a group of VC parameters and CoSB parameters in table format.

CoSB subtemplate

Displays CoSB parameters by CoSB number only. The data reflects the row selection of the table on the VC.

Status bar

Displays the status information of the request. For example, if the modified request cannot be completed because of a lock, the status bar displays the relevant error message.

Button panel

Provides the following button options:

Button

Task

Save

Modifies and saves a selected SCT file.

Save As

Creates and saves a new SCT file.

Delete

Deletes a selected SCT file from a specific switch or from the CWM managed network. The SCT manager allows only the deletion of a nonassociated SCT file. If the SCT file is downloaded to the switch or node, it is removed or deleted only by using the delsct command.

Reset

Cancels changes and resets data for a selected SCT file.

Download

Downloads a selected SCT file to a selected switch.

Associate

Associates a selected SCT file if it is downloaded into a node.

Service Class Template Manager Menu Bar

The menu bar provides available menu options for the Service Class Template Manager application.

The options and functions are listed in Table 6-2.

Table 6-2 Service Class Template Manager Menu Bar

Menu-Bar Options

Task

File

New SCT GUI

Creates a new SCT GUI.

Save

Saves and modifies a selected SCT file locally or at the switch.

Save As

Creates and saves a new SCT file.

Delete

Deletes a selected SCT file.

Download

Loads a selected SCT file.

Associate

Associates a selected SCT file.

Close

Closes the current SCT main window.

Exit

Exits the SCT application.

View

Show SCT

Shows a selected SCT file.

Show Node

Shows a selected SCT node.

Help

Displays the version of Service Class Template Manager.

Service Class Template Manager Toolbar

The toolbar contains buttons that are used frequently (see Table 6-3). Move the pointer over a button to display the feature.

Table 6-3 Service Class Template Manager Toolbar Buttons

Toolbar Options

Task

Save

Saves and modifies a selected SCT file locally or at the switch.

Save As

Creates and saves a new SCT file.

Delete

Deletes a selected SCT file.

Reset

Cancels changes and resets data for a selected SCT file.

Download

Loads a selected SCT file.

Associate

Associates a selected SCT.

Displaying a SCT File

The SCT main window (see Figure 6-3) has a SCT View and Node View that are chosen through tabs. By expanding the SCT File from the SCT View on initial start-up, all the SCT files in CWM are displayed. All supported cards have separate card SCT 0 files and separate port SCT 0 files. The Node View contains the hierarchical network tree familiar from other CWM applications.

The following examples are shown for a card SCT and port SCT:

•AXSM : CARD : AXSM_SCT.CARD.0.V1[0]

•AXSM : PORT : AXSM_SCT.PORT.0.V1[0]
The port SCT manages all the traffic that is entering into and leaving from the port. The card SCT is 
manages all the traffic entering into and leaving the backplane of the Cisco MGX 8850  
(PXM1E and PXM45).
Figure 6-3 Expanded View of SCT Cards and Ports

The right panels contain the VC descriptor and CoSB subtemplates. Upon start-up, the fields are initially blank. Once an SCT is selected, the fields fill in. The VC descriptor panel provides a series of tabs that access different subsets of the VC-related parameters. Each tab represents a group of VC parameters that categorically belong to that group. One tab displays all VC parameters and the other tab displays all CoSB parameters.

You can edit both VC parameters and CoSB parameters, if you are given security permissions to configure SCT files.

Note You can also view SCT activity from the switch CLI.

Table 6-4 lists the tab options for the VC subtemplate and CoSB subtemplate.

Table 6-4 VC and CoSB Subtemplate Tab Options

Tab Option

Task

Policy

Displays policy information related to management priorities for network traffic.

Conn Parm

Displays connection parameter information related to connection types, services, and categories.

VC Threshold

Displays information related to the virtual channel threshold.

Scaling

Displays information related to service scaling.

ABR

Displays information related to the ABR service type.

WFQ

Displays information related to WFQ.

All VC

Displays information related to all VC.

FR Conn Parm

Displays information related to FR Conn Parm.

All CoSB

Presents all CoSB information within the VC subtemplate.

Table 6-5 lists the parameters that are displayed for the VC subtemplate and CoSB subtemplate.

Table 6-5 Service Class Template Parameters

Name

VC

CoSB

Description

Service Type

X

—

Specifies the service type for the applicable parameters, for example, CBR, VBR, and ABR.

Service Category

X

—

Specifies the service category where the service type belongs. All service types that belong to the same service category are mapped to the same CoSB.

The values range from 0 to 65535.

Access: read only

CoSB No

X

X

Specifies the CoSB number that is associated with the service type.

The values range from 1 to 16.

Access: read-write

CAC Treatment

X

—

Specifies the following CAC algorithms:

•lcnCac

•eCac-Model A

•eCac-Model B

•eCac-Model C

•eCac-Model D

•eCac-Model E

•eCac-Model F

•mbBwCac

The default value is 2.

The value ranges from 1 to 256.

Access: read-write

UPC Enable

X

—

Enables or disables UPC¹ policing on the virtual circuit. When a connection is added, a VPI.VCI address is assigned, and UPC parameters are configured for the connection. For each cell in an ATM stream, the VPI.VCI addresses are verified and each cell is checked for compliance with UPC parameters.

The following values include:

•enableAll

•enableGcra1

•enable Gcra2

•enable Gcra1WithPktPolicing

•enable Gcra2WithPktPolicing

•disableAll

Access: read-write

UPC CLP

X

—

Enables or disables GCRA² policing functions on the connection for UPC CLP³ Selection.

The following GCRA functions are

•GCRA1-ENB: Enables GCRA1 only

•GCRA 1&2: Enables both GCRA1 & GCRA2

GCRA-1

X

—

Handles the cells that fail the first PCR⁴ bucket of the policer. If the UPC_ENABLE object is set to disable the policing, the object is not used.

The following options are

•1- discard

•2- set Clp bit

•3- set Clp DiscTagged

Discard tagged cells.

GCRA-2

X

—

Handles the cells that fail the second PCR bucket of the policer. If the UPC_ENABLE object is set to disable the policing, the object is not used.

The following options are

•1- discard

•2- set Clp bit

•3- set Clp DiscTagged

Discard tagged cells.

PCR

X

—

Specifies the maximum PCR for a connection using this service type. The value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

The range and units are 0 to 1000000.

SCR

X

—

Specifies the SCR⁵ for a connection using this service type. The value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

The range and units are from 0 to 1000000.

MCR

X

—

Specifies the MCR⁶ for a connection using this service type. The value is a percentage of the maximum cell rate for the logical interface. 1000000 is equal to 100%.

The range and units are from 0 to 1000000.

ICR

X

—

Specifies the ICR⁷ for a transmission on a connection that has been idle for a configured period of time. The value is a percentage of the PCR for the logical interface. 1000000 is equal to 100%.

Note ABR service type connections are used only.

The range and units are from 0 to 1000000.

MBS

X

—

Specifies the maximum number of cells that can arrive at a rate equal to the PCR. The MBS⁸ is used for policing.

The range and units are from 1 to 5000000.

MFS

X

—

Specifies the AAL5 MFS⁹ in cells.

CDVT

X

—

Specifies the CDVT¹⁰ for the first leaky bucket.

Packet Discard Mode

X

—

Enables or disables the packet discard mode on the connection.

The following range and units are:

•1 = enabled

•2 = disabled

Maximum Threshold

X

—

Specifies the VcMax Threshold for CLP (0+1) cells in microseconds.

The range and units are from 0 to 5000000 microseconds.

CLP-HIGH

X

X

Specifies that the CLP¹¹ high threshold (% of VC QMax) is the highest threshold for the bit in the header of an ATM cell that identifies the cell as eligible for discard within the network under predefined congestion conditions. Most often set by the ingress policing function.

CLP-LOW/EPD1

X

X

Specifies the CLP Low Threshold (% of VC QMax)/ EPD¹². If AAL5 FBTC is yes for the BXM card, this is the EPD threshold setting. EPD is the lowest threshold for the bit in the header of an ATM cell that identifies the cell as eligible for discard within the network under predefined congestion conditions.

EPD0

X

X

Specifies the maximum threshold for CLP (0+1) cells. The value is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%.

The range and values are from 0 to 1000000.

EFCI

X

X

Specifies the VC EFCI¹³ discard threshold. The value is a percentage of MAX_CELL THRESH. 1000000 is equal to 100%.

The range and values are from 0 to 1000000.

COS Scaling

X

—

Provides a means of COS¹⁴ scaling through a set of extended parameters, which are generally platform specific, based on a set of standard ATM parameters passed to the VSI slave during connection set up.

Interface Scaling

X

—

Scales and exchanges information between connections.

CI Control

X

—

Specifies that the CI¹⁵ field is an RM¹⁶ cell that is used to cause the source to decrease the ACR. When an RM cell is sent, the source sets CI=1. When EFCI is received on a previous data cell, CI=1.

Cut-Off RM Cells

X

—

Allows for variations in the RM cell.

VSVD

X

—

Specifies that a VSVD¹⁷ is an ABR connection that is divided into two or more separate controlled ABR segments. Each ABR control segment, except the first, is sourced by a virtual source. Sources and destinations are linked through bidirectional connections, and each connection termination point is both a source and a destination, a source for data that is transmitting, and a destination for data that is receiving.

The following options are

•enable with FCES

•enable without FCES

•disable

ADTF

X

—

Specifies the ADTF¹⁸ time between RM cells before the allowable cell rate returns to the ICR.

RDF

X

—

Specifies the RDF¹⁹ for an ABR service parameter that controls the decrease in the cell transmission rate.

RIF

X

—

Specifies the RIF²⁰ for a percentage increase in the ACR²¹ for an ABR connection if the BRM cells do not have the N1 or C1 bits set.

NRM

X

—

Specifies the maximum number of data cells that are sent before sending an RM cell on an ABR connection. NRM²² is the number of data cells sent between RM cells.

TRM

X

—

Specifies the TRM²³ for the maximum amount of time between RM cells for an ABR connection.

CDF

X

—

Specifies that the CDF²⁴ controls the decrease in ACR, an ABR service parameter. The CDF is associated with CRM²⁵, which is a measure of the difference between the effective bandwidth allocation and the allocation for sustainable rate in cps.

TBE

X

—

Specifies that TBE²⁶ is the number of cells that a source can transmit before receiving feedback from the network through a returned RM cell.

FRTT

X

—

Specifies that FRTT²⁷ is an estimate of the round trip time or the amount of time it takes, in ms, for an RM cell to be transmitted from the source to the destination and back.

WFQ

X

X

Specifies that the WFQ²⁸ is an approximation of the GPS²⁹ scheduling. WFQ is generally used to give performance guarantees to connections carrying best-effort packet traffic, which each connection is guaranteed bandwidth in proportion to its weight and in a fair manner. You can either enable or disable the WFQ parameter.

Minimum Rate

—

X

Specifies that the field is not editable and is set to the default value.

Maximum Rate

—

X

Specifies that the field is not editable and is set to the default value.

Minimum Ptry

—

X

Specifies that the priority for the CoSB is serviced to guarantee minimum and maximum bandwidth requirements.

The following bandwidth requirements include:

•Highest priority = 0

•Lowest priority = 15

The range and units are from 0 to 15

Excess Priority

—

X

Specifies that the priority for the CoSB is given access to excess bandwidth.

The following bandwidth requirements include:

•Highest priority = 0

•Lowest priority = 15

The range and units are from 0 to 15.

Maximum Threshold

—

X

Specifies the VC maximum threshold for CLP (0+1) cells in microseconds.

The range and units are from 0 to 5000000 microseconds.

RED

—

X

Specifies that RED³⁰ drops packets from queues on a random basis to avoid buffer overflow. RED is accomplished by dropping packets on a random basis, which is determined statistically. When the mean queue depth exceeds a threshold over a period of time, RED effectively advises the packet source router to decrease its packet rate.

Dscd Alm Th

—

X

Specifies the discard alarm threshold.

RED Pro Factor

—

X

Specifies the mantissa value of probability for maximum discard when RED is activated. Determined as 1/2^<value> for the RED probability factor.

RED Selection

—

X

Specifies that RED drops packets from queues on a random basis to avoid buffer overflow. RED is accomplished by dropping packets on a random basis, which is determined statistically. When the mean queue depth exceeds a threshold over a period of time, RED effectively advises the packet source router to decrease its packet rate.

ERS

—

X

Indicates whether ERS³¹ is enabled or disabled.

The following range and units are

•1 = enabled

•2 = disabled

Best Effort

—

X

Specifies a Quality of Service Class where no specific traffic parameters and no absolute guarantees are provided. Best Effort includes UBR and ABR Service Types.

Dscrd Alarm

—

X

Indicates whether Discard Alarm has been enabled or disabled.

The following range and units are

•1 = enabled

•2 = disabled

CLR

—

X

Specifies that the CLR³² is a negotiated QoS³³ parameter in the ATM network. The parameter indicates a ratio of lost cells to total transmitted cells.

¹UPC = usage parameter control

²GCRA = generic cell rate algorithm

³UPC CLP = usage parameter control-cell loss priority

⁴PCR = peak cell rate

⁵SCR = sustained cell rate

⁶MCR = minimum cell rate

⁷ICR = initial cell rate

⁸MBS = maximum burst size

⁹MFS = maximum frame size

¹⁰CDVT = cell delay variation tolerance

¹¹CLP = cell loss priority

¹²EPD = early packet discard

¹³EFCI = Explicit Forward Congestion Indication

¹⁴CoS = Class of Service

¹⁵CI = congestion indicator

¹⁶RM = resource management

¹⁷VSVD = virtual source/virtual destination

¹⁸ADTF = allowed cell rate decrease time factor

¹⁹RDF = rate decrease factor

²⁰RIF = rate increase factor

²¹ACR = allowed cell rate

²²NRM = number RM

²³TRM = time RM

²⁴CDF = cut-off decrease factor

²⁵CRM = cell rate margin

²⁶TBE = transient buffer exposure

²⁷FRTT = fixed round-trip time

²⁸WFQ = weighted fair queuing

²⁹GPS = generalized processor sharing

³⁰RED = random early discard selection

³¹ERS = Explicit Rate Stamping

³²CLR = cell loss ratio

³³QoS = quality of service

Declaring SCT Sync-Up

When CWM is either started by using cold start or warm start, the SCT daemon discovers all the SCTs present on all the switches running switch software version 3.x or higher, and imports them into the database. The SCT discovery is possible due to the introduction of the SCT management MIB at the switch running version 3.x or higher. During a CWM cold start, all SCT files that exist on the switches in the network can send information about the SCT files, which include the SCT filename, version, and content to all CWM workstations in the domain.

When the SCT daemon is discovering SCTs in the network, SCT operations are blocked. When the daemon is done discovering, it declares a SCT sync-up, which maintains the SCT integrity to the network.

The SCT application notifies you of a sync-up in progress (see Figure 6-4).

At CWM cold start, all SCT files that exist on the switches in the network will send information about the SCT files, including SCT filename, version, and content, to all CWM workstations in the domain.

Caution Performing a coldstart -F deletes connection templates, SCT templates, and connection descriptors from the database.

Table 6-6 lists the scenarios that are used for sync up.

Table 6-6 Sync-up Scenarios

Scenario

Equation

I (perfect)

Done = Start = Total

II (sync up timeout)

Done < Start = Total

III (discovery timeout)

Done = Start < Total

IV

Done < Start < Total

After launching the Service Class Template application, the Sync-Up Progress window (see Figure 6-4) can appear to notify you that the SCT file sync-up is in progress.

Figure 6-4 Sync-Up Progress Window

Creating a SCT File

You must use CWM to create custom Service Class Templates.

Creating a new SCT involves configuring ATM parameters for specific classes of service to suit the special needs of your customers. For example, if you have customers with special policing or nonpolicing requirements, you can create an SCT to meet those specifications.

Some service providers offer different levels of service, for example, gold, silver, or bronze, at different prices. Each level of service offers a different class of service and is supported by a different SCT.

Caution Only network engineers who are extremely knowledgeable about ATM and its parameters should create and use their own SCTs.

To create a new SCT file, complete the following procedure:

Step 1 Select an existing SCT file from the navigator panel.

Step 2 Click Save As to create and save a new SCT file.

Figure 6-5 displays the Save As Dialog.

Figure 6-5 SCT: Save As Dialog

Step 3 Enter the applicable name for the SCT file in the Enter a Sct Name field.

A new SCT file with a new ID and minor version 0 is created only on the CWM workstation.

Note A new SCT file begins with ID 100 an increment by 1 regardless if it is a card or port file.

The SCT Manager locates the next available SCT ID that has not been used.

Step 4 Click OK. The new SCT (see Figure 6-6) appears in the navigator panel.

Figure 6-6 New SCT

Modifying a SCT File

You must use CWM to modify the table or field entries of Service Class Templates. The SCT tables contain all the parameters; whereas, the field entries display only the most frequently access parameters.

You can modify both the data and description of the SCT that has already been downloaded and associated with various nodes in the network. Recent minor versions of the SCT are created and downloaded to the nodes that contained the original SCT.

You can also modify SCT files that have been downloaded and are currently being used. SCTs can also be removed from a particular node if the SCTs are not being associated to cards or ports.

Minor versions allow you to make minor changes to SCT parameters without creating a new SCT ID; therefore, you do not need to reconfigure the port or card with a new SCT ID. However, ports and cards must be reset for the new values to take affect. When you modify or save a SCT, minor versions are created. The numbers for the minor version are automatically incremented.

To modify a SCT file, complete the following procedure:

Step 1 Select the SCT that you want to modify.

Step 2 To modify the SCT parameter by using the SCT table, you can:

a. Double-click the applicable field.

b. Enter the new number if applicable.

c. Choose a value or parameter from the drop-down arrow.

Figure 6-7 shows the SCT Manager with the CAC Treatment field for RT VBR.1 selected and the drop-down arrow.

Figure 6-7 SCT Manager with CAC Treatment Field Selected

Step 3 To modify the SCT entry fields that include rate and priority, threshold, and miscellaneous columns, you can:

a. Enter the new number into the applicable fields.

b. Choose either enable or disable from the drop-down arrow in the Miscellaneous column.

Figure 6-8 shows the SCT Manager with ABR.1 selected. ABR.1 - CosB #1 appears over the Entry Fields section. 100 in the Maximum Rate field of the Rate and Priority column is selected.

Figure 6-8 SCT Manager with ABR.1 Selected

Step 4 Click Save to save the SCT under the existing name and the modifications.

Figure 6-9 displays the Save Dialog window.

Figure 6-9 SCT Save

Table 6-7 lists the modify options.

Table 6-7 Service Class Template Manager Modify Options

Option

Description

Save Local Only

Saves a local copy of the SCT file with the changes in CWM only. A filename with a trailing "T" is defined as a temporary entry in the SCT tree. You can temporarily save the modified SCT.

A temporary version of an SCT can be saved for the modified SCT and does not affect the minor version sequence.

You cannot download a particular minor version of the SCT. Only the latest minor version is downloaded. Also, you cannot selectively delete minor versions of an SCT; the SCT is deleted as a whole.

Save

If you select to modify and save a nonlocal copy of the SCT file at the switch, a new minor version of the SCT file is created and downloaded to the switch. The SCT file overrides the SCT file in the switch. For changes in the new minor version of the same SCT file to take affect, you must reboot the card or use the dnport command followed by the cnfport command on all effected ports.

Cancel

Cancels the selection.

Renaming the SCT File

The SCT manager allows you to rename the SCT filename with 1 to 32 characters. The new SCT name also shows up on the switch CLI.

To rename the SCT file, complete the following procedure:

Step 1 Select the SCT file that you want to rename.

Step 2 Choose View > Change SCT Name to rename the SCT.

Figure 6-10 displays the Change SCT Name dialog.

Figure 6-10 Change SCT Name Dialog

The name change is propragated to all the nodes that contain the SCT. When the SCT is being updated in the network, a lock icon is displayed next to the SCT. Upon completion, the lock disappears.

If the operation is not successful, the state of the SCT is marked as partial.

Removing and Deleting the SCT File

The SCT manager deletes only a nonassociated SCT file.

To remove and delete the SCT file from a switch, CWM, and the network, complete the following procedure:

Step 1 Select the applicable SCT file.

Note You must select the top-level SCT file entry, for example, the file entry that does not display the minor version.

Step 2 Click Delete or choose File > Delete.

Figure 6-11 displays the Remove and Delete dialog.

Figure 6-11 SCT: Remove and Delete Window

Step 3 If you are removing the SCT file from a switch, you must:

a. Select the applicable node.

b. Uncheck the Delete SCT File checkbox.

Step 4 If you are deleting the SCT from CWM and the network, you must:

a. Check the Delete SCT File checkbox.

An alert window appears.

b. Click OK.

Step 5 Click Delete to remove the SCT file.

If you chose to remove the SCT file from a switch, the SCT file is removed only from the selected switch. The SCT file remains in CWM and other switches.

Note You can also remove the SCT file that is not being used from the switch.

If you chose to delete the SCT file from CWM and the network, the SCT file is deleted.

Confirming Version and Data Discrepancy

Before performing any operations on a SCT file that has data or version discrepancies, you must resolve or confirm version and data discrepancies.

If a SCT has the same SCT ID, SCT type, front card type, and major version number, but has a different minor version number or contains different data on two or more nodes, a version or data inconsistency is caused respectively.

On a particular node, the SCT key identifies a particular SCT for only one minor version. The SCT key uniquely describes the SCT and provides the SCT ID, SCT port or card type, front card type such as AXSM, AXSME, PXM1E, or FRSM12, and the major version that is currently one.

Any SCT file discrepancies must be resolved to preserve the integrity and consistency of the SCT files.

Ideally, there is only one minor version and one set of SCT data for the SCT on a network.

For information about the SCT ID types, see the "SCT File Types" section.

Note Version and data discrepancy confirmation is performed only on a primary CWM workstation.

To confirm version discrepancy, complete the following procedure:

Step 1 Select the existing SCT file that is tagged with a red icon. The version discrepancy indicates different minor versions on different nodes.

Figure 6-12 displays a Confirm Dialog.

Figure 6-12 Confirm Dialog: Version Inconsistency for SCT Window

Step 2 Click Yes to select the highest minor version number.

The highest minor version is downloaded to all switches with lower minor versions.

Version inconsistency is resolved.

SCTs with the same minor versions but different data can cause a data inconsistency. For example, two switches can have the same SCT filename and version number, but different SCT file content.

To confirm data discrepancy, complete the following procedure:

Step 1 Select the existing SCT file that is tagged with a blue icon.

Figure 6-13 displays the Mediation Dialog window.

Figure 6-13 Mediation Dialog Window

Step 2 Click View to view the information for the selected card or port. You decide the SCT file that you want confirmation.

Step 3 Click Confirm to confirm the card or port information.

The selected file is downloaded to all switches that contain the SCT file.

Data inconsistency is resolved.

Downloading the SCT File to a Node

To download the SCT file to a node, complete the following procedure:

Step 1 Select the applicable SCT file that you want downloaded to a switch.

Step 2 Click Download or choose File > Download.

Figure 6-14 displays the Download SCT to Switch Dialog window.

Figure 6-14 Download SCT to Switch Dialog

Step 3 Select the applicable node destination to download the SCT file.

Step 4 Click OK to download the SCT file to the specified node.

Figure 6-15 shows the downloaded SCT in the left panel of the SCT main window.

For verification on the switch, see the "Verifying the Download of the SCT Through the Switch" section.

Figure 6-15 Downloaded SCT

Verifying the Download of the SCT Through the Switch

You can verify a successful download to the switch through the CLI.

To verify that the SCT is loaded on the switch, complete the following procedure:

Step 1 Open a terminal window.

Step 2 When you establish a CLI session, you must:

a. Enter the applicable username at the prompt.

b. Enter the applicable password at the prompt.

Step 3 Enter the dspscts command to list all the available SCTs on the hard drive.

For more information about the dspscts command, refer to the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 4.

Step 4 From the list, verify that the new SCT is applied and registered to the appropriate card.

Associating a SCT File to a Card or Port

Once the SCT is present on the switch, you can proceed to associate the SCT with the card or port. A card SCT defines the queue parameters for the destination slot based cell queues towards the backplane. A port SCT manages all traffic coming to and leaving from the port.

For card association, all ports on the card must be down first. For port association, use the dnport command to bring down the port that is in the administrative state "Up". For more information, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4.

Note You can also use the cnfcdsct command as an alternative to CWM.

A downloaded SCT file is identified by a leaf node on the SCT tree. From the Node View, if an SCT file is leaf node of a node, the SCT is downloaded into that node.

To associate a SCT file to a card or port, complete the following procedure:

Step 1 Select an existing SCT file that was downloaded to the switch.

Step 2 Click Associate or choose File > Associate.

Figure 6-16 displays the Associate Dialog window.

Figure 6-16 Associate Dialog Window

Step 3 Select the card or port that you want to associate. The example shows a card association (see Figure 6-16).

Step 4 Click OK to associate the file.

Notifying the SCT Application for the SCT Activity on the Node

If a SCT is added, modified, or deleted from a node, a respective trap is sent to CWM monitoring that node. CWM is always synchronized with the SCTs for the node.

To notify the SCT application for the SCT activity on the node, complete the following procedure:

Step 1 Select the applicable node that is already modified.

Figure 6-17 displays that the Refresh button is enabled.

Figure 6-17 SCT: Refresh Enabled Window

Step 2 Click Refresh to enable the SCT activity and to refresh the SCT Manager.