Table of Contents

VSI Terms and Acronyms
Summary of Commands
addctrlr
addshelf

Adding a VSI Controller
Feature Mismatching to Verify VSI Support

addyred
cnfqbin

Qbin Dependencies

cnfrsrc

Resource Partitioning
Partition Information Sent to Cisco WAN Manager
Partitioning
cnfrsrc Parameters, Possible Values, and Descriptions
Feature Mismatching to Verify VSI Support

cnfvsiif

Assigning a Service Template to an Interface
cnfvsiif Example

cnfvsipart
delctrlr
delshelf

Deleting a Controller

delyred
dspchuse
dspctrlrs
dspqbin

Class of Service Buffer Descriptor Template Configuration

dspqbint
dsprsrc
dspsct

Extended Services Types Support
Connection Admission Control (CAC)
Supported Service Types
Details of Connection (VC) Parameters Used in Service Class Templates

dspvsiif
dspvsipartcnf
dspvsipartinfo
dspvsich
dspyred

VSI Commands

Virtual Switch Interface (VSI) is a common control interface for MSSBU switches such as the BPX 8650 and the MGX 8850. Virtual Switch Interfaces (VSIs) allow a node to be controlled by multiple controllers, such as MPLS (Multiprotocol Label Switching, formerly called Tag Switching) and PNNI.

When a virtual switch interface (VSI) is activated on a port, trunk, or virtual trunk so that it can be used by a master controller, such as a SES PNNI or an MPLS controller, the resources of the virtual interface associated with the port, trunk or virtual trunk are made available to the VSI. These control planes can be external or internal to the switch. The Virtual Switch Interface provides a mechanism for networking applications to control the switch and use a partition of the switch resources.

VSI was implemented first on the BPX 8650 in Release 9.1, which uses VSI to perform Multiprotocol Label Switching. Release 9.1 allowed support for VSI on BXM cards and for partitioning BXM resources between Automatic Routing Management (formerly called AutoRoute) and a VSI-MPLS controller. Previous to this release, you could configure partition resources to be shared between Automatic Routing Management PVCs and one VSI control plane, but not both. You now can configure partition resources between Automatic Routing Management PVCs and two VSI controllers (LSC or PNNI).

The second implementation of VSI on the BPX provides the following extended functionality:

• class of service templates
  
  
• virtual trunks support for VSI
  
  
• support for VSI master redundancy
  
  
• multiple VSI partitions
  
  
• SV+ support for VSI
  
  

Caution   You can use the VSI features (such as to configure a VSI-MPLS controller or a PNNI controller). However, you can still configure and use Automatic Routing Management PVCs. Use the cnfrsrc command to configure Automatic Routing Management PVCs.

For more overview information and specific information on how to configure a BPX 8650 switch, refer to the Cisco BPX Series Installation and Configuration. For information about configuring a 6400, 7200 or 7500 router for MPLS operation, refer to the MPLS Configuration Guide.

VSI Terms and Acronyms

These terms relate to Virtual Switching Interface and MPLS (Multiprotocol Label Switching):

ATM Edge LSR

A label switching router that is connected to the ATM-LSR cloud through LC-ATM interfaces. The ATM edge LSR adds labels to unlabeled packets and strips labels from labeled packets.

ATM-LSR

An ATM-LSR is a MPLS (Multiprotocol Label Switching) router in which packets are forwarded by switching cells rather than frames, and all packet interfaces are MPLS (Label) Controller-ATM interfaces.

A label switching router with a number of LC-ATM interfaces. The router forwards the cells from these interfaces using labels carried in the VPI and/or VCI field.

BCC

The switch control card in the BPX is the Broadband Control Card, which has a 68040 processor.

BPX

A high-end ATM switch called the Cisco Broadband Packet Exchange (BPX). The BPX is a carrier-quality switch, with trunk and CPU hot-standby redundancy.

BPX-LSR

An ATM label switch router consisting of a label switch controller (series 6400, 7200 or 7500 router) and a label controlled switch (BPX switch).

BXM

The Broadband Switch Module (BXM) cards are ATM port cards for the BPX switch that use the Monarch chipset. Various different port configurations are supported by the BXM card: 8¥DS3, 12¥DS3, 4¥OC-3, 8¥OC-3, 1¥OC-12 or 2¥OC-12. The Monarch architecture supports up to 64K bidirectional cross-connect legs per BXM card, although only 16K or 32K options are supported in the first release. The BXM has very flexible input and output queueing facilities, a Segmentation Assembly and Reassembly (SAR) capability, and a MIPS 4650 control processor.

Class of Service (CoS) Buffer

A buffer or queue that serves connections with similar QoS requirements. Also called "QBin" (though a QBin is a platform-specific instance, such as a BXM card, of the more general Class of Service Buffer (CoSB).

Class of Service (CoS) Buffer Descriptor Template

A component of a Service Class Template that contains Class of Service Buffer configurations indexed by CoSB number.

A QBin is a platform-specific (BXM in this case) instance of the more general Class of Service Buffer (or CosB).

CLI

There are two separate Command-Line Interfaces on the BPX-LSR: One on the BPX itself and one on the MPLS (Multiprotocol Label Switching) Controller. The Control Point integrate these into a single command line interface.

CommBus

The CommBus is the BPX's internal messaging protocol.

CosB

See Class of Service (CoS) Buffer.

Feeder

A feeder is a small switch that acts as an extension shelf, typically with lower-bandwidth interfaces, for a larger switch. The larger switch is referred to as the Routing node with the feeder(s) it supports. Collectively, the feeder(s) and routing node form a type of supernode.

LC-ATM Interface

A Label Controlled ATM interface is an MPLS (Multiprotocol Label Switching) interface where labels are carried in the VPI/VCI bits of ATM cells, and where VC (virtual circuit) connections are established under the control of MPLS (Multiprotocol Label Switching) control software.

LCN

Each interface card in a BPX has a certain number of Logical Connection Numbers. A Logical Connection Number is used for each cross connect leg through the card in question. "LCN" is often roughly synonymous with "cross-connect leg." In VSI terminology, an LCN is an example of an Other End Reference.

Logical Interface

Each physical interface and every virtual trunk endpoint on a platform is represented to the VSI controllers as a different logical interface with partitions, and other VSI configuration. Logical Interface numbers are 32-bit with a format which is, in general, known only to the platform.

LSR

Label Switching router, which is an MPLS (Multiprotocol Label Switching) router.

PNNI

Private Network-to-Network Interface controller software that runs on the SES hardware platform. The term PNNI controller and SES may be used interchangeably.

Port

The VSI makes no distinction between trunk ports and endpoint ports. "Port" is synonymous with "Interface."

Routing Node

In tiered networks terminology, a routing node is a larger switch to which one or more feeders is attached. Collectively, the feeder(s) and routing node form a type of supernode.

Service Class (aka Service Type)

A concept for grouping connections that share a common set of traffic characteristics and QoS requirements. The terms service class and service type are sometimes used interchangeably.

---

Note   In this release, there are some major service categories, such as VbrRt, VbrNRt, CBR, Abr, and Ubr, and under these major service categories are service types such as VbrRt1, VbrRt2, VbrRt3, and VbrNRt1, VbrNrt2, and so on.

---

Service Class Database

The collection of data items that support the service class template concept, and implemented on a per-VI basis on the BXM. These items include a B2_Body2copy of the specific Service Class Template selected for a VI, as well as additional data as required.

Service Class Template (SCT):

A set of data structures that map VSI service types to sets of pre-configured VC and QBin parameters. Consists of two sub-components—a VC Descriptor Template and a Class of Service Buffer descriptor template.

VC

ATM and Frame Relay traffic is carried in Virtual Channels that are set up between adjacent ATM or Frame Relay switches before data transmission occurs. An ATM link between switches may support up to 2²⁸ different VCs, although a small number of VCs is reserved for special purposes.

VCI

Each VC within a specific Virtual Path on a link has a unique Virtual Channel Identifier, which is a 16-bit number.

VC Descriptor Template

A component of a Service Class Template which contains platform-specific VC configurations that are indexed primarily by service type. Together with a Class of Service Buffer (CoSB) descriptor template, it defines a Service Class Template (SCT).

VP, VPC, VPI

A Virtual Path is a bundle of 2¹⁶ Virtual Connections with the same Virtual Path Identifier, that is, the first 12 bits of the VPCI. Most ATM switches can switch VPs using only a single cross-connect (instead of up to 2¹⁶ ). An end-to-end sequence of VPs cross-connected at the intermediate swi5tches is a Virtual Path Connection.

VPCI

Each VC on a link has a unique Virtual Path and Channel Identifier, which is a 28-bit number. The VPCI consists of a 12-bit VPI concatenated with a 16-bit VCI.

Virtual Trunks

A Virtual Trunks is a Virtual Path Connection which appears to VSI masters as ordinary trunk (except that the trunk supports 64K VCs at most). In a VSI platform, a virtual trunk endpoint has its own logical interface.

VSI

Virtual Switch Interface is a proposed common control interface to all Cisco MSSBU switches. It embodies both connection management and switch configuration discovery capabilities.

VSI 2

Virtual Switch Interface, Protocol Version 2: this is revision 2 of a proposed common control interface to all MSSBU switches. It embodies both connection management and switch configuration discovery capabilities.

VSI Controller

A controller, such as a PNNI SVC Controller, Portable AutoRoute or Label Switch Controller, which controls a switch using the VSI.

VSI Master

A VSI master process implementing the master side of the VSI protocol in a VSI controller. Sometimes the whole VSI controller might be referred to as a "VSI Master", but this is not strictly correct.
1) A device that controls a VSI switch, for example, a VSI Label Switch Controller.
2) A process implementing the master side of the VSI protocol.

VSI Slave

1) A switch (in the "Single Slave model") or a port card (in the "Multiple Slave Model") that implements the VSI.
2) A process implementing the slave side of the VSI protocol.

Summary of Commands

Table 16-1 shows the command name and starting page for the description of each VSI-related command.

addctrlr

Adds VSI capabilities to a trunk interface to which a feeder of type AAL5 is attached. The addctrlr command is used only to connect a Private Network to Network Interface (PNNI) controller. PNNI controller software resides on the SES hardware.

The addctrlr command is the second step in the adding of a PNNI controller to a BPX node.

The first step is to run the command addshelf with shelf type set to P to add a AAL5 feeder. This ensures that Annex G protocol runs between the BPX and the SES.

Then run the addctrlr command to set up the VSI control channels from the PNNI SES controller to the VSI slave processes running on the BXM cards to ensure full VSI functionality for the PNNI controller. You execute the addctrlr command on an existing AAL5 interface shelf.

Also note that you can add a PNNI controller to a trunk interface only if the interface already has an active VSI partition corresponding to the partition that is controlled by the PNNI controller. Suppose a PNNI controller controlling the partition 1 were added to a trunk interface 12.1. Then it would be necessary that a VSI partition corresponding to partition 1 be active on the interface 12.1. Otherwise the addctrlr command would fail.

When you add VSI controller capabilities onto an AAL5 interface shelf (or feeder), the switch software prompts you for the specifics of the VSI controller:

• controller ID of the PNNI controller
  
  
• partition ID of the VSI partitions controlled by the PNNI controller
  
  
• VPI used for the VSI control channels set up by the PNNI controller
  
  
• start VCI value for the VSI control channels set up by the PNNI controller
  
  

There could be 12 BXM cards on the BPX node and the PNNI controller would control VSI partitions on those BXM cards that support VSI capability. Hence a separate VSI control channel must be set up from the PNNI control to each BXM card that supports VSI. Suppose you specify a VPI value of 0 and start VCI value of 40 for the VSI control channels. Then the control channel corresponding to any BXM card on slot 1 would use VPI, VCI values <0, 40>. The VSI control channels to other slots would use the VPI, VCI values of <0, 40+slot-1>, where "slot" corresponds to the slot number of the BXM card.

Caution   For feeder trunk interfaces, the addctrlr command will fail if the AutoRoute connections terminating on the feeder interface use the same VPI VCI as those specified for the VSI control channels. You must delete the connections before proceeding if connections with VPI and VCI in the range exist in the range you specified.

The addition of a controller to a node will fail if there are not enough channels available to set up the control VCs in one or more of the BXM slaves.

Full Name

Add VSI capabilities to a AAL5 feeder interface

Syntax

addctrlr < slot.port> <controller id> <partition id> <control_vpi> <start_vci>

Related Commands

addshelf, delctrlr, dspctrlrs

Attributes

Example 1

addctrlr 10.4 3 2 0 40

Description

Add controller to port 4 on slot 10, partition ID of 2, and controller ID of 3.

System Response

Description

Adds a controller, such a PNNI controller, to a BPX interface shelf.

addshelf

Adds an ATM link between a hub node and an interface shelf such as an MGX 8220, an MGX 8850, or IGX shelf in a tiered network; or an ATM link between a BXM card on a BPX node and an MPLS (Multiprotocol Label Switching) controller such as a series 6400, 7200 or 7500 router; or an ATM link between a BXM card on a BPX node and an SES PNNI Controller. (An MPLS Controller or an SES PNNI Controller is considered an interface shelf from the BPX switch's perspective.) The routing hub can be either a BPX or an IGX.

The interface shelf can be one of the following:

• An MGX 8220 shelf connected to a BPX node
  
  
• An IGX shelf connected to an IGX routing node which serves as a hub for the IGX/AF
  
  
• An SES PNNI Controller connected to a BPX node
  
  
• An MGX 8850 shelf connected to a BPX node
  
  
• An MPLS (Multiprotocol Label Switching) Controller connected to a BPX node
  
  
• An SES (Service Expansion Shelf) connected to an IGX node
  
  

The signaling protocol that applies to the trunk on an interface shelf is Annex G. For example, in this release, the IGX 8400 interface shelf with a BTM E1 interface communicates with the routing hub through the Annex G LMI using STI cell format. However, the MGX 8850 interface shelf, or feeder, communicates over a UXM/UXM-E interface with the routing hub over Annex G LMI using AAL5 format.

Note   Because tiered network capability is a paid option, personnel in the Cisco Technical Assistance Center (TAC) must telnet to the unit and configure it as an interface shelf before you can execute addshelf.

Each IGX/AF, MGX 8220, or MGX 8850 shelf has one trunk that connects to the BPX or IGX node serving as an access hub. A BPX routing hub can support up to 16 T3 trunks to the interface shelves, which can be IGX/AF, MGX 8220, or MGX 8850 interface shelves. An IGX hub can support up to four trunks to the interface shelves, which can be IGX/AF shelves only.

An IGX 8400 interface shelf can connect to an IGX 8400 routing hub over a BTM E1 interface using STI cell format. In Release 9.1, an IGX 8400 interface shelf can connect to an MGX 8800 over a UXM/UXM-E interface using ATM cell format.

Before it can carry traffic, you must "up" trunk on an interface shelf (using uptrk) on both the interface shelf and the hub node and "add" it to the network (using addshelf). Also, a trunk must be free of major alarms before you can add it with the addshelf command.

Adding a VSI Controller

The maximum number of controllers that can be attached to a given node is limited by the maximum number of feeders (16) that can be attached to a BPX hub. Therefore the total number of feeders and controllers cannot exceed 16.

You add a VSI controller, such as an MPLS (Multiprotocol Label Switching) Controller, to a switch with the addshelf command using the vsi option. The vsi option of the addshelf command is used to identify VSI controllers and tell them apart from interface shelves (feeders). The VSI controllers are allocated a partition of the switch resources. VSI controllers manage their partition through the VSI interface. The controllers run the VSI master. The VSI master entity interacts with the VSI slave running on the BXMs through the VSI interface, to set up VSI connections using the resources in the partition assigned to the controller. Two controllers that are intended to be used in a redundant configuration must specify the same partition when added to the node through the addshelf command.

When a controller is added to the node switch software will set up the infrastructure so that the controllers can communicate with the slaves in the node. The VSI entities decide how and when to use these communication channels.

In addition, the controllers require a communication channel between them. This channel could be in-band or out-of-band. When a controller is added to the switch, switch software will send controller information to the slaves. This information will be advertised to all the controllers in the partition. The controllers may decide to use this information to set up an intermaster channel. Alternatively the controllers may use an out-of-band channel to communicate.

The maximum number of controllers that can be attached to a given node is limited by the maximum number of interface shelves (feeders) that can be attached to a BPX hub. This number in Release 9.2 is 16. Therefore the total number of feeders and controllers cannot exceed 16.

To add a controller to the node, use the addshelf command. A redundant controller is added in the normal way, except that it specifies a partition that may be already in use by another controller. In this release the addshelf command allows for up to two controllers to manage the same partition.

One of the parameters that must be specified with the addshelf command when a VSI controller is added to the switch is the controller id. This is a number between 1 and 32 that uniquely identifies the controller. Two different controllers must always have different controller IDs.

The management of resources on the VSI slaves requires that each slave in the node has a communication control VC to each of the controllers attached to the node. When a controller is added to the BCC via the addshelf command, the BCC sets up the set of master-slave connections between the new controller port and each of the active slaves in the switch. The master slave connections are specified via the <Control VPI> and <Control Start VCI> parameters. The default for these parameters is 0/0.

Feature Mismatching to Verify VSI Support

The cnfrsrc and addshelf commands, in addition to other configuration commands, will perform mismatch verification on the BXM and UXM cards. For example, the cnfrsrc and addshelf commands will verify whether the cards both have VSI 2.0 support configured.

The Feature Mismatching capability will not mismatch cards unless the actual feature has been enabled on the card. This allows for a graceful card migration from an older release.

Full Name

Add an interface shelf (feeder) or a controller to a routing node or hub.

Syntax

Interface shelf:

addshelf <slot.port> <shelf-type> <vpi> <vci>

MPLS (Multiprotocol Label Switching) controller:

addshelf <trunk slot.port> v <ctrlr id> <part id> <control vpi> <control vci start> <redundant ctrlr warning>

Note   If you manage a tiered network through the command line interface, you can manage only Frame Relay interworking connections (ATFR) across the network. Three-segment connections for carrying serial data or voice between IGX/AFs is allowed, but you must manage them through WAN Manager.

Related Commands

addctrlr, delshelf, dspnode, dsptrks

Attributes

Example 1

Interface shelf: addshelf 11.1 a 21 200

MPLS (Multiprotocol Label Switching) controller: addshelf 4.1 vsi 1 1

Description

Interface shelf:

Add trunk 11.1 as an MGX 8220 interface shelf. After you add the shelf, the screen displays a confirmation message and the name of the shelf.

MPLS (Multiprotocol Label Switching) controller:

Add trunk 4.1 as a VSI-MPLS (Multiprotocol Label Switching) Controller interface shelf. After you add the LSC, the screen displays a confirmation message and the name of the shelf.

Description for Interface Shelves

An interface shelf can be one of the following:

• An MGX 8220 connected to a BPX node.
  
  
• An MGX 8850 connected to a BPX node.
  
  
• An IGX node connected to a BPX node, which serves as a hub for the IGX/AF.
  
  
• An IGX node connected to an IGX routing node, which serves as a hub for the IGX/AF.
  
  

The (VPI.VCI) of the 15 control VCs is:
(control_VPI.control_VCI_start) to (control_VPI.control_VCI_start+14).

The control VC used for slot n (1<= n<=15) is:
(control_VPI.control_VCI_start + n -1).

Example for Interface Shelves

Add an MGX 8220 at trunk 11.1 After you add the shelf, the screen displays a confirmation message and the name of the shelf. Add the MGX 8220 (may be referred to on screen as AXIS) as follows:

addshelf 11.1 a

The sample display shows a partially executed command prompting you for the interface shelf type:

System Response

Example for Adding an MGX 8850 AAL5 (ATM Adaptive Layer/5) Interface Shelf

Add an MGX 8850 at trunk 4.8. After you add the MGX 8800 shelf, the screen displays a confirmation message and the name of the shelf. Add the MGX 8850 (may be referred to on screen as AAL5) as follows:

addshelf 4.8 x

The sample display shows that an MGX 8850 was added on trunk 4.8 as an AAL5 (ATM Adaptive Layer/5 type of interface shelf. (Adding an MGX 8850 interface shelf is similar to adding an MPLS Controller interface shelf.)

System Response

Description for MPLS

For MPLS, before it can carry traffic, you need to up the link to a MPLS controller (by using uptrk) at the BPX node. You can then add the link to the network (by using addshelf). Also, the link must be free of major alarms before you can add it with the addshelf command.

Note   Once you up a port on the BXM in either trunk or port mode by using either the uptrk or upport commands, respectively, you can only up the ports in the same mode.

Example for MPLS

Add a MPLS controller link to a BPX node by entering the addshelf command at the desired BXM port as follows:

addshelf 4.1 vsi 1 1

System Response

Example for VSI Controller

Add a VSI controller link to a BPX node by entering the addshelf command at the desired BXM port as follows:

addshelf 13.2

System Response

addyred

Enables card redundancy for IGX and BPX cards. Use the addyred command to specify the slots of the primary and secondary (standby) cards that form the redundant pair.

You must use the addyred command to configure a VSI slave redundant card. When a standby slave card is first started (either by having been inserted into the slot, or if the user issues the addyred command from the CLI console), the active slave VSI forward all VSI messages it had received from the Master VSI controller card to the standby slave VSI controller card.

Redundant card sets must have the following characteristics:

• The primary and secondary card sets must be identical.
  
  
• When configuring APS 1+1, primary and secondary card sets must be in adjacent slots. (Note that this restriction only applies to the BPX chassis for APS 1+1 redundancy.)
  
  
• Secondary card sets must not currently be active.
  
  
• Neither the primary nor secondary card set may already be part of a redundant set.
  
  
• Redundancy applies to the entire card and not specific trunks or lines.
  
  

In both the single and multiport card sets, if the secondary card set becomes active, the primary card set serves as its backup (assuming the primary card set is complete and not failed). You cannot use the addyred command if the primary and secondary slots are empty. If cards reside in the primary and secondary slots, the system checks for card compatibility. Two types of incompatibility can occur: back card and jumper or cable inconsistencies. (On SDI, FRI, and FTI cards, jumpers determine whether a port is configured as DCE or DTE. On LDI cards, either a DCE or DTE adapter cable connects to the LDI port. For descriptions of the jumper positions and cabling, see the Cisco IGX 8400 Series Installation and Configuration manual.)

Note that the addyred command prevents invalid configurations when you try to configure the SONET APS feature. When SONET Automatic Protection Switching (APS) is configured, you will not be able to use the addyred or delyred commands on a card configured for APS 1:1 architecture. That is, you will not be able to execute the addyred command, then configure the APS 1:1 architecture. Similarly, you will not be able to configure APS 1:1, then execute the addyred command. You will be blocked from executing these commands at the command line interface.

If incompatibilities exist, the message "Y-Cable Conflict" appears on the screen. Specific conflicts are listed in reverse video in the dspyred display. See the dspyred description for more information.

To ensure that only cards with the Idle Code Suppression feature enabled on them are allowed to be a Y-redundancy pair, addyred blocks cards that have different idle code suppression capability.

Full Name

Add Y-cable redundancy.

Syntax

addyred <primary slot> <secondary slot>

Related Commands

delyred, dspyred, prtyred

Attributes

Example 1

addyred 25 26

Description

Add Y-cable redundancy to the SDP/SDI card sets in slots 25 and 26.

System Response

cnfqbin

Use the cnfqbin command to configure the Qbin (Class of Service Buffers parameters on a selected BXM port or trunk. The cnfqbin command prompts you to configure the Qbin from the template assigned to a logical interface.

This command now lets you accept the interface template as the values, as an option. For example, you can type in Yes when prompted whether the interface service class template (SCT) should be used, and the command will use the card Qbin values from the Qbin templates. You will not be allowed to enter values for any Qbin parameter in this case. You can, however, enter desired values if the template option has not been chosen.

When a VSI interface is activated, the default template gets assigned to an interface. The corresponding Qbin template gets copied into the card Qbin data structure for that interface. When you want to change this, by giving new values using the cnfqbin command, the Qbin is now user configured as opposed to template configured. This information is displayed on the dspqbin screen. It indicates whether the values in the Qbin are from the template assigned to the interface OR the values have been changed to user-defined values. The cnfqbin command will prompt you whether template should be used for Qbin parameters. In this release, the dspqbin command now displays all the fields of a Qbin template.

The cnfqbin command was introduced in Release 9.1 to configure any Qbin on the BXM cards. In this release, it has been extended to support virtual trunks. When the virtual trunk is dedicated to the controller, you can only configure Qbin 10-15.

VC connections are grouped into large buffers called Qbins. (Per-VC queues can be specified on a connection-by-connection basis also). In this release, all VSI connections use Qbin 10 on each interface.

You configure Multiprotocol Label Switching (formerly Tag Switching) for VSIs on a BXM card is configured using the cnfrsrc and cnfqbin commands. Qbin 10 is assigned to tag switching.

Use the cnfqbin command is used to adjust the threshold for the traffic arriving in Qbin 10 of a given VSI interface as away of fine tuning traffic delay.

If you use the cnfqbin command to set an existing Qbin to disabled, the egress of the connection traffic to the network is disabled. Re-enabling the Qbin restores the egress traffic.

Note   Cell Delay Variation (CDV) is based on the Qbin depths and the transmission speed of the virtual switch interface. The default Qbin depths are specified in the service class templates (SCTs). You can configure the Qbin depths by using the cnfqbin command. Cell Tolerance Delay (CTD), which is the fixed delay, is based on a fixed value, and is not configurable.

The cnfqbin command prompts you whether "template" should be used for Qbin parameters.

Full Name

Configure Qbin

Syntax

cnfqbin <slot number>.<port number>.<vtrk>

Related Commands

dspqbin

Attributes

Example 1

cnfqbin 13.1

Description

Create a Qbin configuration on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS.

System Response

Example 2

cnfqbin 4.1 10

Description

Configure the Qbin 10 for port 4.1; also configure ports 4.2 and 4.3, and enter port 4.2 and 4.3 where applicable.

If the Qbin is not configured, configure the queues on the ports using the cnfqbin command:

cnfqbin 4.1 10

enable/disable: e

For all other parameters, accept the (default).

The previous parameters can also be set for Qbin 10 as follows:

cnfqbin 4.1 10 e 0 65536 95 100 40

System Response

System Response

Qbin Dependencies

The available Qbin parameters are shown in Table 16-7. Notice that the Qbins available for VSI are restricted to Qbins 10-15 for that interface. All 32 possible virtual interfaces are provided with 16 For Qbin default settings, see Table 16-7. Qbins. Refer to Table 16-8 for a listing of cnfqbin parameters with possible values and ranges.

.

cnfrsrc

Use the cnfrsrc command to partition resources for Automatic Routing Management PVCs or VSI-MPLS (Multiprotocol Label Switching).

This command was introduced in Release 9.1 to support physical trunks. It has been extended to support virtual trunks. After VSI has been enabled, the virtual trunk becomes a "dedicated" VSI virtual trunk. Note that if the trunk has already been added or if the VPI value has not been configured, you will not be able to configure the VPI value. (Switch software will block you from doing so.)

You can configure a virtual trunk to be dedicated to VSI or to Automatic Routing Management. You cannot configure a virtual trunk for both VSI and Automatic Routing Management.

The switch software:

• Allows start VPI = 0 for a VSI partition on a port interface, provided there is only one VSI partition on the port interface.
  
  
• Prevents a second VSI partition from being enabled on a port interface if the first VSI partition uses a start VPI = 0.
  
  
• Prevents a VSI partition from being disabled on a trunk interface if a PNNI controller is attached to the trunk interface controlling partition being disabled.
  
  

Configurable resources (using cnfrsrc) are:

• Template number (new field in Release 9.2)
  
  
• Maximum PVC LCNs
  
  
• Maximum PVC Bandwidth
  
  
• Configure Partition (Y/N)
  
  
• Partition ID
  
  
• Enable Partition (Enable/Disable)
  
  
• Minimum VSI LCNs
  
  
• Maximum VSI LCNs
  
  
• Start VSI VPI
  
  
• End VSI VPI - Warning message will tell you that the end vsi vpi is equal to the start vsi vpi for virtual trunks
  
  
• Minimum VSI Bandwidth
  
  
• Maximum VSI Bandwidth
  
  

Resource Partitioning

The VSIs need to partition the resources between competing controllers: Automatic Routing Management, MPLS (Multiprotocol Label Switching), and PNNI for example. You can have different types of controllers splitting up a partition's assets. For example, Automatic Routing Management, and MPLS, or Automatic Routing Management and PNNI (SVCs), but not PNNI and MPLS.

This release supports one or two partitions only. In this release, two controllers of a single type are supported. The user interface will block the activation of partitions with ID higher than 1 if the card does not support multiple partitions.

When enabling a partition, If [start_VPI, end_VPI] of the partition contains any "reserved" VPI, an error message is displayed and you are prompted for different values for start_VPI, end_VPI. Thus, if VPI 10 is used for control VCs on an interface, then you cannot include VPI 10 in any VSI partition by using the cnfrsrc command. An error message would be displayed.

The resources that you need to configure for a partition are shown in Table 16-9 for a partition designated ifci, which stands for interface controller 1, in this example. The three parameters that need to be distributed are: 1) number of logical connections (lcns); 2) bandwidth (bw); and 3) virtual path identifiers (vpi).

Some ranges of values available for a partition are listed in Table 16-10:

When you add a trunk, the entire bandwidth is allocated to Automatic Routing Management (formerly known as AutoRouting). To change the allocation to provide resources for a VSI, use the cnfrsrc command on the BPX switch. A view of the resource partitioning available is shown in Figure 16-1.

Partition Information Sent to Cisco WAN Manager

When the partition information is configured for the first time or any parameters are changed, Cisco WAN Manager will be updated through a robust message.

• vsi_min_channels:
  This field represents the minimum guaranteed channels available for a given port.
  
  
• vsi_max_channels:
  This field represents the maximum number of channels available, but not guaranteed, for a port.
  
  
• vsi_vpi_start:
  This field represents the starting VPI that can be used by VSI.
  
  
• vsi_vpi_end:
  This field represents the end of the VPI range that can be used by VSI.
  
  
• vsi_min_bw:
  This field represents the minimum guaranteed bandwidth available for a port.
  
  
• vsi_max_bw:
  This field represents the maximum bandwidth available, but not guaranteed, for a port.
  
  

Partitioning

On each interface (port or trunk) on the BXM cards used for label switching, two sets of resources must be divided up between traditional PVC connections and tag switching connections. The traditional PVC connections are configured directly on the BPX platform, and tag switching connections are set up by the TSC using the VSI. The following resources are partitioned on each interface:

• Bandwidth
  
  
• Connections
  
  

As with all ATM switches, the BPX switch supports up to a specified number of connections. On the BPX switch, the number of connections supported depends on the number of port/trunk cards installed. On each interface, space for connections is divided up between traditional BPX switch permanent virtual circuit (PVC) connections, and Label Switching VCs (LVCs).

cnfrsrc Parameters, Possible Values, and Descriptions

See Table 16-11 for a listing of cnfrsrc parameters, ranges and values, and descriptions. These parameters appear on the cnfrsrc screen.

Feature Mismatching to Verify VSI Support

In this release, the cnfrsrc and addshelf commands, in addition to other configuration commands, performs mismatch verification on the BXM and UXM cards. For example, the cnfrsrc and addshelf commands will verify whether the cards both have VSI 2.0 support configured.

The Feature Mismatching capability will not mismatch cards unless the actual feature has been enabled on the card. This allows for a graceful card migration from an older release.

Full Name

Configure resources

Syntax

cnfrsrc <slot.port.vtrk>

or

cnfrsrc <slot>.<port>.<vtrk> <maxpvclcns> <maxpvcbw> <partition> <e/d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw>

Related Commands

dsprsrc

Attributes

Example 1

cnfrsrc 4.1 256 26000 1 e 512 16384 2 15 26000 100000

Description

Configure the VSI partition for port 4.1.

System Response

Example 2

cnfrsrc 13.1

Description

Partition resources on the OC-3 trunk on port 1 of slot 13 on the BPX to support a service such as VSI-MPLS (or PNNI SVCs).

System Response

Example 3

cnfrsrc 4.1

Description

Port 4.1 is the slave interface to the label switch controller. Configure the VSI partitions for port 4.1 as follows:

cnfrsrc 4.1

PVC LCNs: [256] {accept default value}

max PVC bandwidth: 26000

partition: 1

enabled: e

VSI min LCNs: 512

VSI max LCNs: 7048 {varies with BXM type

VSI start VPI: 2

VSI end VPI: 15

VSI min b/w: 26000

VSI max b/w: 100000

or with one entry as follows:

cnfrsrc 4.1 256 26000 1 e 512 7048 2 15 26000 100000

System Response

Note   It is possible to have PVCs terminating on the Tag Switch Controller itself. This example reserves approximately 10 Mbps (26000 cells/sec) for PVCs, and allows up to 256 PVCs on the switch port connected to the LSC.

Note   The VSI max and min logical connections (LCNs) will determine the maximum number of tag virtual connections (TVCs) that can be supported on the interface. The number of TVCs required on the interface depends on the routing topology of the tag switch.

Note   By default the LSC will use either a starting VSI VPI of 1 or 2 for tag switching, whichever is available. If both are available, a starting VSI VPI of 1 is used. The VPI range should be 2-3 on a BPX VSI connected to a 6400, 7200 or 7500 AIP. If VPI 2 is not to be used, the tag switching VPI interface configuration command can be used on the TSC to override the defaults

Note   The VSI range for tag switching on the BPX switch is configured as a VSI partition, usually VSI partition number 1. VSI VPI 1 is reserved for Automatic Routing Management, so the VSI partition for tag switching should start at VPI 2. Two VPIs are sufficient for the current release, although it may be advisable to reserve a larger range of VPIs for later expansion, for example, VPIs 2-15.

Table 16-12 lists the cnfrsrc parameters, focusing more on configuring resources for VSI partitions (an MPLS controller, for example). For more information on configuring resources for Automatic Routing Management PVCs, refer to the cnfrsrc command.

cnfvsiif

Use the cnfvsiif command to assign a Service Class Templates (SCT) to an interface.

Use the dspvsiif command to display a service class template assigned to an interface (VI), as well as display a summary of the resources allocated to the VSI partition on a given interface.

Assigning a Service Template to an Interface

A default service template is assigned to a logical interface (VI) when you up the interface by using upport/uptrk.

For example:

• uptrk 1.1
  
  
• uptrk 1.1.1 (virtual trunk)
  
  
• upport 1.1
  
  

This default template has the identifier of 1. You can change the service template from service template 1 to another service template using the cnfvsiif command. The dspvsiif command allows you to display the template associated with the interface. For example:

• cnfvsiif 1.1 2
  
  
• cnfvsiif 1.1.1 2
  
  
• dspvsiif 1.1
  
  
• dspvsiif 1.1.1
  
  

cnfvsiif Example

You use the cnfvsiif command to assign a selected service template to an interface (VI) by specifying the template number. It has the following syntax:

cnfvsiif <slot.port.vtrk> <tmplt_id>

Full Name

Configure a service class template and assign it to an interface

Syntax

cnfvsiif <slot.port.vtrk> <tmplt_id>

Related Commands

cnfrsrc, dsprsrc, cnfqbin, dspqbin

Attributes

Example 1

cnfvsiif 11.1 2

System Response

cnfvsipart

Use the cnfvsipart command to enable or disable VSI ILMI support.

Full Name

Configure VSI partition characteristics

Syntax

cnfvsipart <slot.port.[vtrk]> <part_id> <enable_option>

Related Commands

cnfrsrc, dspvsipartcnf, cnfport, cnftrk

Attributes

delctrlr

Deletes VSI capabilities on a trunk interface to which a feeder of type AAL5 is attached. Use this command to delete a controller, such as a PNNI SES controller, from a BPX node. It deletes the VSI control channels used to communicate between the VSI master on the PNNI controller and the VSI slaves on the BXM cards.

You run this command as the first step in deleting a PNNI controller from a BPX node. The second step is to run the command delshelf to delete the AAL5 feeder.

(Do not use delctrlr to delete a VSI Label Switching controller from a BPX node; you must use delshelf to delete a VSI Label Switching controller from a BPX node.)

In this release, PNNI runs on the Service Expansion Shelf (SES) hardware.

To add VSI controller capabilities onto the newly created AAL5 interface, you use the addctrlr command. You are prompted to enter the controller ID and partition ID. This creates an interface through which a PNNI controller can use the VSI protocol to control the node resources that were previously specified by using the cnfrsrc command.

You remove a PNNI controller from a BPX node by using the delctrlr command. For example, this might be a VSI controller such as an PNNI controller configured with VSI capabilities as an AAL5 interface shelf to a BPX. When you delete one of the controllers by using the delctrlr command, the master-slave connections associated with this controller are deleted. The control VCs associated with other controllers managing the same partition will not be affected.

Note   To add a VSI Label Switch Controller, you use addshelf and delshelf commands, as in releases previous to Release 9.2.

Full Name

Delete VSI capabilities from a AAL5 feeder interface

Syntax

delctrlr <slot.port> <controller id>

Related Commands

addctrlr, dspctrlrs, dspnode

Attributes

Example 1

delctrlr 10.3

Description

Delete VSI controller with interface shelf (feeder) type of AAL5 connected on trunk 10.3 from the list of controllers connected to BPX node named "night."

System Response

System Response

Example 2

delctrlr <slot.port><controller_id>

Description

Deletes controller from port 3 on slot 10, with controller name E, and controller ID of 1.

System Response

delshelf

Deletes an interface shelf from a tiered network. The identifier for an interface shelf is either the trunk number or the name of the shelf. Normally, you do not execute delshelf only at the hub node, but on the IGX/AF itself. The command delshelf has the single function of letting you turn off LMI if the trunk is not allowing communication. In contrast to the deltrk command, you can execute delshelf at any time if no connections terminate at the trunk.

Deleting a Controller

You remove a controller from the node by using the delshelf command. When one of the controllers is deleted using the delshelf command, the master-slave connections associated with this controller will be deleted. The control VCs associated with other controllers managing the same partition will not be affected.

The deletion of the controller will trigger a new VSI configuration CommBus (internal BPX protocol) message. This message will include the list of the controllers attached to the node. The controller deleted will be removed from the list. This message will be sent to all active slaves in the shelf. In cluster configurations, deleting a controller will be communicated to the remote slaves by the slave directly attached through the inter-slave protocol.

While there is at least one controller attached to the node controlling a given partition, the resources in use on this partition should not be affected by a controller being deleted. Only when a given partition is disabled, the slaves will release all the VSI resources used on that partition.

Full Name

Delete an interface shelf

Syntax

delshelf <trunk> | <shelf-name>

Related Commands

addshelf, dspnode

Attributes

Example 1

delshelf 4.1

Description

Delete shelf trunk A241 from a BPX node.

System Response

delyred

This command disables Y-redundancy for the card set in the specified primary slot number. If the secondary card slot is being used as the active slot at the time you use the delyred command, the system attempts to switch back to the primary slot. The substitution takes place only if the primary slot has a complete set of cards and the cards are in a Standby or a Standby-F state (not if they are Failed). See the dspcds description for information on card states. See the addyred and dspyred commands for more information on Y-cable redundancy.

When you issue the delyred command, it always completes. If the primary card is incomplete, control will still be given to the primary card.

Full Name

Delete Y-cable redundancy

Syntax

delyred <primary slot>

Related Commands

addyred, dspyred, prtyred

Attributes

Example

delyred 16

Description

Disable Y-cable redundancy at slot 16.

dspchuse

The dspchuse command displays the a summary of the channel distribution in a given slot. It shows the distribution of channels between AutoRoute pvcs, networking channels, VSI management channels, and channels allocated to the VSI slave.

This command applies only to BXM cards. Previously a debug command; dspchuse is available to multiple users at all privilege levels in this release.

Full Name

Display channel distribution

Syntax

dspchuse <slot >

Related Commands

dspvsiif, dspvsipartinfo

Attributes

Parameters

Example 1

dspchuse 13

Description

Display channel management summary for slot 13.

System Response

dspctrlrs

Use the dspctrlrs command to display all VSI controllers, such as a SES PNNI controller on a BPX or IGX node. This command lists:

• the controller ID
  
  
• the partition the controller use
  
  
• the trunk/interface to which a controller is attached
  
  
• the controller type (always a VSI controller)
  
  
• the interface type (AAL5, VSI Label Switching)
  
  
• MGX 8220 (formerly called AXIS) interface shelf
  
  
• the name of the controller/entity on which the controller exists (that is, node name, equipment name).
  
  

---

Note   You use addshelf and delshelf to add and delete a VSI controller such as a Label Switching Controller to a BPX node

---

You can also the dspnode command to display the VSI controllers on a BPX node.

Full Name

Displays all VSI controllers, for example, all PNNI controllers such as PNNI, on a BPX or IGX node.

Syntax

dspctrlrs <slot.port><controller name string><partition_id><controller_id>

Related Commands

addctrlr, addshelf, cnfctrlr, delctrlr, dspnode

Attributes

Example 1

dspctrlrs

Description

Display VSI controllers on BPX node sw174.

System Response

dspqbin

The dspqbin command displays the Qbin resources on a selected trunk, port, or virtual trunk. It displays the Qbin parameters currently configured for an interface, and shows whether the Qbin resources have been configured by the user OR by a template. The dspqbin command displays whether the Qbin has been configured by a user or by the template assigned to the interface. It also displays whether the Qbin has EPD enabled/disabled.

For this release, Class of Service buffer 10 is used for tag switching connections. Check the queue buffer 10 configurations for port 4.1 as follows:

dspqbin 4.1 10

Full Name

Display Qbin

Syntax

dspqbin <slot number>.<port number> [qbin-id]

Note   To display a specific Qbin configuration on the selected port, enter qbin-id as an optional parameter to the dspqbin command. For Release 9.1, use only Qbin 10 for VSI connections.

Related Commands

cnfqbin

Attributes

Example 1

dspqbin 13.1

Description

Display the current Qbin configuration on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS.

System Response

Example 2

dspqbin 4.1 10

Description

Display the current Qbin configuration on slot 4, port 1, Qbin 10.

System Response

Example 3

dspqbin 2.1.1 10

Description

Display Qbin 10 on slot 2, port 1, virtual trunk 1.

System Response

Example 4

dspqbin 13.1.1 10

Description

Display Qbin 10 configuration for virtual trunk 1, on port 1 of card slot 13.

System Response

Class of Service Buffer Descriptor Template Configuration

Table 16-18 lists parameters included in the Class of Service (CoS) Buffer (Qbin) portion of the Service Class Templates. (Note that a Qbin is a platform-specific instance (for example, BXM) of the more general Class of Service Buffer. A firmware command sends a command (message) to switch software to initialize the CoS Buffer Descriptors in the Service Class Templates. This command may contain multiple instances of Qbin number, each indicating a new Qbin configuration.

dspqbint

Display the Qbin (class of service buffer) templates. You can enter optional parameters to display the service classes in a specified Qbin template.

Use the dspqbint command to display the service class template number assigned to an interface (VI). The dspsctmplt command has three levels of operation:

• dspqbint With no arguments lists all the service templates resident in the node.
  
  
• dspqbint <tmplt_id> Lists all the service classes in the template
  
  
• dspqbint <tmplt_id> Lists all the parameters of that service class
  
  

Additional service template commands you can use are:

• cnfqbin Configures the Qbin. You can answer yes when prompted and the cnfqbin command will use the card's Qbin values from the Qbin templates.
  
  
• dspqbin Displays Qbin parameters currently configured for the virtual interface.
  
  
• dspcd Display the card configuration.
  
  

See the sections that precede the VSI commands at the front of this chapter for more high-level information on VSI and more detailed information on service class templates in Release 9.2 and how you use them to configure connections with specified service classes.

Full Name

Display Qbin template

Syntax

dspqbint <template #><qbin #>

Description

Display a service class template number, which identifies one of the templates between 1-3, and the Qbin number.

Related Commands

dspsct, dspqbin, cnfrsrc, dsprsrc, cnfvsiif, dspvsiif

Attributes

Example 1

dspqbint <template #> <qbin>

Description

Displays the Qbin template number 1 for a specified Qbin (10).

System Response

dsprsrc

The dsprsrc command displays the partition of all the resources on the specified trunk or port. It also displays virtual trunks for a specified trunk or port. Resources not applicable to virtual trunks are not displayed.

Full Name

Display resources

Syntax

dsprsrc <slot number>.<port number>.<vtrk> [partition_id]

Note   To display a specific partition, you can enter the optional partition_id parameter for the dsprsrc command. In this release, the valid partitions are 1 and 2.

Related Commands

cnfrsrc, cnfqbin, dspqbin

Attributes

Example 1

dsprsrc 3.2.1

Description

Display partition resources on the OC-3 trunk on card slot 3, port 2, and virtual trunk 1 on the BPX node.

System Response

Example 2

dsprsrc 13.1

Description

Display partition resources on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS.

System Response

Example 3

dsprsrc 4.1 1

Description

Display partition resources on VSI trunk 4.1 (slot.port), specifying partition ID of 1. Note that if the partition is disabled, you only see the Max PVC LCNs Max. PVC Bandwidth available, and Partition ID number parameters.

System Response

Example 4

dsprsrc 4.1 1

Description

Display partition resources on VSI trunk 4.1, and partition ID 1. (If the partition is enabled, more parameters related to how resources are partitioned are displayed.)

System Response

Example 5

dsprsrc 4.1 1

Description

Display partition resources on VSI trunk 4.1.

System Response

dspsct

The dspsct command displays a list of nine supported Service Class Templates (SCT).

Extended Services Types Support

The service-type parameter for a connection is specified in the connection bandwidth information parameter group. The service-type and service-category parameters determine the service class to be used from the service template.

Connection Admission Control (CAC)

For this release, when a connection request is received by the VSI Slave, it is first subjected to a Connection Admission Control process before being forwarded to the firmware layer responsible for actually programming the connection. The granting of the connection is based on the following criteria:

LCNs available in the VSI partition

• Qbin
  
  
• Service Class
  
  

QoS guarantees

• max CLR
  
  
• max CTD
  
  
• max CDV
  
  

When the VSI slave accepts (that is, after CAC) a connection setup command from the VSI master in the Label Switch Controller, it receives information about the connection including service type, bandwidth parameters, and QoS parameters. This information is used to determine an index into the VI's selected Service Template's VC Descriptor table thereby establishing access to the associated extended parameter set stored in the table.

Supported Service Types

The service type identifier is a 32-bit number. The service type identifier appears on the dspsct screen when you specify a service class template number and service type; for example:

dspsct <2> <vbrrt1>

A list of supported service templates and associated Qbins, and service types is shown in Table 16-20.

Details of Connection (VC) Parameters Used in Service Class Templates

Listed below is some detailed information on connection (VC) parameters used in service class templates. Some of these parameters may appear on the dspsct display.

Full Name

Display service class template (SCT)

Syntax

dspsct [template #][service_type]

Related Commands

dspqbint, cnfvsiif, dspvsiif

Attributes

Example 1

dspsct

Description

Displays all the templates in the node.

System Response

Example 2

dspsct 2

Description

Display service class template 2, which displays service classes (also referred to as service categories or service sub-categories) for the ATMF1 template, along with designated Qbins (class of service buffers).

System Response

Example 3

dspsct 3

Description

Display service class template 3, which displays service classes (also referred to as service categories or service sub-categories) for the ATMF1 template, along with designated Qbins (class of service buffers).

System Response

Example 4

dspsct 2 vbrrt1

Description

Display service class template (SCT) for template number 2 called vbrrt1.

System Response

Example 5

dspsct 2 Abr

Description

Display all the parameters of the service class template ID 2, specified by Abr.

System Response

Example 6

dspsct 1 Default

Description

Displays the parameters for service class template 1 (the MPLS1 service class template), for the Default service type.

System Response

Example 7

dspsct 1 Signaling

Description

Displays the parameters for service class template 1 (the MPLS1 service class template), for the Signaling service type.

System Response

Example 8

dspsct 1 Signaling

Description

Displays the parameters for service class template 1 (the MPLS1 service class template), for the Signaling service type.

System Response

Example 9

dspsct 1 Tag0

Description

Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.

System Response

Example 10

dspsct 1 Tag1

Description

Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.

System Response

Example 11

dspsct 1 Tag2

Description

Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.

System Response

Example 12

dspsct 1 VbrRt1

Description

Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.

System Response

Example 13

dspsct 1 VbrRt1

Description

Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.

System Response

dspvsiif

You can use the dspvsiif command to display a service class template assigned to an interface (VI). You can also display a summary of the resources allocated to the VSI partition on a given interface. Multiple users are allowed to use the dspvsiif at one time.

Example

After using cnfvsiif command to assign a selected service class template to an interface, you can use the dspvsiif command to display the type of service template assigned to an interface (VI). It has the following syntax:

dspvsiif <slot.port.vtrk>

Full Name

Display a service class template assigned to an interface.

Syntax

dspvsiif <slot.port.vtrk> <tmplt_id>

Related Commands

cnfrsrc, dsprsrc, cnfqbin, dspqbin

Attributes

Example 1

dspvsiif 13.1.1

Description

Display the service class template ID assigned to an interface configured on slot 13, port 1, virtual trunk of 1. In this case, service class template 2 has been assigned to this interface.

System Response

Example 2

dspvsiif 11.1 2

Description

Display a service class template assigned to an interface.

System Response

dspvsipartcnf

Use this command to display VSI partition characteristics. It displays information about only VSI ILMI functionality. This command displays:

• whether VSI ILMI is enabled for a given partition
  
  
• the LCN used for the sessions (only for trunk interfaces)
  
  
• the type of IP address downloaded to the BXM card for topology discovery purposes
  
  

If no partition is specified, this command displays the above information about all the VSI partitions and also the Sys_Id downloaded to the BXM card for ILMI functionality.

Full Name

Display VSI partition characteristics

Syntax

dspvsipartcnf <slot.port.[vtrk]> [partition_id]

Related Commands

cnfrsrc, cnfvsipart, cnfport, cnftrk

Attributes

dspvsipartinfo

Use the dspvsipartinfo command to display VSI statistics for a particular active partition on an interface. You can use the dspvsipartinfo command on only one partition at a time, to get VSI statistics on an interface (can be a port or virtual trunk). You can optionally specify an interval in seconds, which will display VSI statistics for the specified active partition every x seconds. The command shows you some of the same parameters that display on the cnfrsrc screen, such as Min LCNs and Max LCNs, Used LCNs and Available LCNs, and Min BW, Max BW, and Used BW.

The command dspvsipartinfo also displays a line that provides slave redundancy status. It tells you whether the standby card is in synch with the active card. You must have cards in Y-redundancy configuration for this line to display.

Multiple users may use the dspvsipartinfo command at the same time.

Job mode is not allowed.

Full Name

Display VSI statistics per partition

Syntax

dspvsipartinfo <interface>.<partition>[<interval>]

<interface>             the slot.port.[vtrk] of the interface being monitored.

<partition>             partition id for which information is to be displayed.

<interval>               the refresh interval for displaying data. Range:1-60 seconds. Default: 1 second.

Related Commands

cnfrsrc, dsprsrc, cnfvsiif, dspvsiif

Attributes

Example 1

dspvsipartinfo 3.1 1 10

Description

Display VSI statistics for slot 3, port 1 for interface configured on partition ID 1, at an interval of every 10 seconds.

System Response

Example 2

dspvsipartinfo 11.1 2 10

Description

Display VSI statistics for port 1 for interface configured on partition ID 2, at an interval of every 10 seconds.

Example 3

dspvsipartinfo 4.1 1

Description

Display VSI statistics for slot 4, port 1 for interface configured on partition ID 1.

System Response

dspvsich

The dspvsich command is a debug command that displays VSI logical connections. These VSI logical connections are also sometimes referred to as management LCNs (1-6, 9-15). The dspvsich command displays the LCN number, type of channel (for example, interslave, master-slave, or intershelf); the destination slot, and destination LCN.

(Note that you must have debug level privileges to use this command, that is, either Service or StrataCom level privileges. Check with the TAC for assistance in accessing these commands.)

In this release, this command displays the control_VPI and control_VCI_start of the particular controller.

Full Name

Display VSI logical connections

Syntax

dspvsich <slot>

Description

Display the VSI channels (or LCNs) on the specified slot.

Related Commands

cnfqbin

Attributes

Example 1

dspqbin 13.1

Description

Display the current Qbin configuration on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS (Multiprotocol Label Switching).

Example 2

dspvsich 4

Description

Display VSI management channels (or LCNs) on slot 4.

System Response

dspyred

Displays information for Y-cable pairings. A single slot can be specified, or all pairings are displayed when no slot is specified. Slot numbers appearing in high intensity indicate active card status. Front card, back card, and channel configuration conflicts appear in reverse video. A conflict occurs when the port interfaces are different for corresponding ports in a redundant slot pair. The output display contains the following information:

• First column (Slot) designates the slot of the displayed card.
  
  
• Second column (Slot Type) designates its status, Pri (primary) or Sec (secondary).
  
  
• Third column (Other Slot) designates the slot number of the associated Y-redundant card.
  
  
• Fourth column (Front Card) designates the type of card in the front slot.
  
  
• Fifth column (Back Card) designates the type of card in the back slot.
  
  

Remaining columns (Channel Configuration) describe the channel configurations when appropriate.

Full Name

Display Y-cable redundancy

Syntax

dspyred [slot]

Related Commands

addyred, delyred, prtyred

Attributes

Example 1

dspyred

Description

Display Y-redundancy for all cards.

System Response

Posted: Mon Aug 19 21:35:06 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.