|
|
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 extensioned functionality:
 |
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 <CellCommandItalic>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.
These terms relate to Virtual Switching Interface and MPLS (Multiprotocol Label Switching):
ATM Edge LSR
ATM-LSR
BCC
BPX
BPX-LSR
BXM
Class of Service (CoS) Buffer
Class of Service (CoS) Buffer Descriptor Template
CLI
CommBus
CosB
Feeder
LC-ATM Interface
LCN
Logical Interface
LSR
PNNI
Port
Routing Node
Service Class (aka Service Type)
 |
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
Service Class Template (SCT):
VC
VCI
VC Descriptor Template
VP, VPC, VPI
VPCI
Virtual Trunks
VSI
VSI 2
VSI Controller
VSI Master
VSI Slave
Table 16-1 shows the command name and starting page for the description of each VSI-related command.
| Mnemonic | Description | Page |
|---|---|---|
addctrlr | Attach a controller to a node; for controllers that require Annex G capabilities in the controller interface. Add a PNNI VSI controller to a BPX node through an AAL5 interface shelf. | |
addshelf | Add a trunk between the hub node and interface shelf, VSI-MPLS (Multiprotocol Label Switching) controller, or and SES PNNI. | |
cnfqbin | Configure QBin parameters. | |
cnfrsrc | Configure resources, for example, for Automatic Routing Management PVCs and MPLS (Multiprotocol Label Switching) Controller (LSC). | |
cnfvsiif | Configure VSI Interface or a different template to an interface. | |
cnfvsipart | Configure VSI partition characteristics for VSI. | |
delctrlr | Delete a controller, such as a PNNI ESP (Extended Services Processor) 4.0 controller, from a BPX node. | |
delshelf | Delete a trunk between a hub node and access shelf. | |
dspchuse | Display a summary of channel distribution in a given slot. | |
dspctrlrs | Display the VSI controllers, such as an PNNI controller, on a BPX node. | |
dspqbin | Display QBin card. | |
dspqbint | Display QBin template. | |
dsprsrc | Display LSC (Label Switching Controller) resources. | |
dspsct | Display Service Class Template assigned to an interface. | |
dspvsiif | Display VSI Interface. | |
dspvsipartcnf | Display information about VSI ILMI functionality. | |
dspvsipartinfo | Display VSI resource status for the partition. |
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:
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.
Add VSI capabilities to a AAL5 feeder interface
addctrlr < slot.port> <controller id> <partition id> <control_vpi> <start_vci>
| Parameter | Description | ||
|---|---|---|---|
<slot.port> | Slot and Port numbers corresponding to the feeder trunk. | ||
<controller-id> | Controller ID corresponding to the PNNI controller, values 1 - 32. | ||
<partition-id> | Partition ID of the VSI partition controlled by the PNNI controller. | ||
<control_vpi> | Starting VPI of the VSI control channels used for communication between the VSI master residing on the SES and VSI slaves residing on the BXM cards. There can be a total of 12 such channels one for each slave residing on each BXM card. For a trunk interface with NNI header type: For a trunk interface with UNI header type Default value: 0
| ||
<start_vci> | Starting VCI of the VSI control channels. This VCI value is assigned to the first VSI control channel (between the VSI master and the VSI slave residing on the BXM card in slot 1). The last VSI control channel corresponding to communication with the VSI slave on slot 14 will use the VCI value of (<start_vci>+14-1). The valid values are: 33 - 65521. Default value: 40
|
addshelf, delctrlr, dspctrlrs
| Privilege | Jobs | Log | Node | Lock |
1 | No | Yes | BPX | Yes |
addctrlr 10.4 3 2 0 40
Add controller to port 4 on slot 10, partition ID of 2, and controller ID of 3.
night TN StrataCom BPX 8600 9.2.00 Apr. 11 1998 14:31 GMT
BPX Controllers Information
Trunk Name Type Part Id Ctrl ID Ctrl IP State
10.3 PNNI VSI 1 1 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled
Warning partition already in use do you want to add redundant controller
Last Command: addctrlr 10.4 3 2 0 40
Next Command:
Adds a controller, such a PNNI controller, to a BPX interface shelf.
night TN StrataCom BPX 8600 9.2.00 Apr. 11 1998 14:31 GMT
BPX Controllers Information
Trunk Name Type Part Id Ctrl ID Ctrl IP State
10.3 PNNI VSI 1 1 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled
Warning partition already in use do you want to add redundant controller
Last Command: addctrlr 10.3 3 1 0 40
Next Command:
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:
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.
In this release, the new parameters "Control VPI" and "Control VCI start" have been added.
In this release, addshelf will prevent adding a feeder to a trunk if a VSI ILMI session is active on a VSI partition on the trunk interface.
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.
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.
Add an interface shelf (feeder) or a controller to a routing node or hub.
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. |
addctrlr, delshelf, dspnode, dsptrks
| Privilege | Jobs | Log | Node | Lock |
1-4 | Yes | Yes | BPX switch with IGX interface shelf BPX switch with the MGX 8220 shelf BPX with the MGX 8850 shelf BPX switch for MPLS (Multiprotocol Label Switching) controller (LSC) | Yes |
Interface shelf: addshelf 11.1 a 21 200
MPLS (Multiprotocol Label Switching) controller: addshelf 4.1 vsi 1 1
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.
An interface shelf can be one of the following:
| Parameter | Description |
|---|---|
slot.port (trunk) | slot.port Specifies the slot and port number of the trunk. |
shelf-type | I or A or X On a BPX node, shelf type specifies the type of interface shelf when you execute addshelf. The choices are I for /AF or IGX/AF, A for the MGX 8220 and PNNI SES, V for VSI, or X for the MGX 8800. On an IGX hub, only the IGX/AF is possible, so shelf type does not appear. |
vpi vci | Specifies the VPI and VCI (Annex G VPI and VCI used). For the MGX 8220 only, the valid range for VPI is 5-14 and for VCI is 16-271. For an IGX/AF interface shelf, the valid range for both VPI and VCI is 1-255. On an IGX 8400 node, when using an MGX 8800 interface shelf, the following VPI/VCI limits apply:
|
control_vpi | Choose the value for <control_VPI> such that: if <control_VPI> = 0, <control_VCI_start> can be set to a value > 40. If any VSI partition exists on the interface, then control_VPI < start_VPI or control_VPI > end_VPI for all partitions on that interface. An error message appears if the control VPI falls into the VPI range belonging to a VSI partition. No AutoRoute connection exists on (VPI.start_VCI to VPI.start_VCI+14). If any AutoRoute connection exists on these VPI/VCI values, you are not allowed to use these VPI/VCI values. This VPI is reserved for control VCs. Default = 0 |
control_vci_start | Default = 40 |
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).
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:
nmsbpx23 TN SuperUser BPX 8620 9.2 Apr. 4 1998 13:28 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
1.3 AXIS240 AXIS OK
11.2 A242 AXIS OK
This Command: addshelf 11.1
Enter Interface Shelf Type: I (IGX/AF), A (AXIS), P (APS), V (VSI), X (AAL5)
Next Command:
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.)
pswbpx3 TN SuperUser BPX 8600 9.1 June 6 1998 13:28 PST
BPX Interface Shelf Information
Trunk Name Type Part Id Ctrl Id Alarm
4.8 SIMFDR0 AAL5 - - OK
This Command: addshelf 4.8 x
Enter Interface Shelf Type: I (IGX/AF), A (AXIS), P (APS), V (VSI), X (AAL5)
Next Command:
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. |
| Parameter | Description |
|---|---|
slot.port | Specifies the BXM slot and port number of the trunk. You can configure the port for either trunk (network) or port (service) mode. |
device-type | VSI, which is "virtual switch interface, specifies a virtual interface to an MPLS controller (TSR) such as a Cisco 6400, 7200 or 7500 series router. |
control ID | Control IDs must be in the range of 1 to 32, and you must set these identically on the LSC and in the addshelf command. A control ID of "1" is the default used by the MPLS (Multiprotocol Label Switching) controller (LSC). |
control VPI | Starting VPI of the VSI control channels used for communication between the VSI master residing on the SES and VSI slaves residing on the BXM cards. There can be a total of 12 such channels one for each slave residing on each BXM card. For a trunk interface with NNI header type: Valid values for this parameter are: 0-4095 For a trunk interface with UNI header type Valid values for this parameter are: 0-255. Default value: 0 |
start VCI | Starting VCI of the VSI control channels. This vci value is assigned to the first VSI control channel (between the VSI master and the VSI slave residing on the BXM card in slot 1). The last VSI control channel corresponding to communication with the VSI slave on slot 14 will use the vci value of (<start_vci>+14-1). The valid values are: 33 - 65521. Default value: 40 |
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
nmsbpx23 TN SuperUser BPX 15 9.1 Apr. 4 1998 13:28 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
5.1 j6c AXIS MIN
5.3 j5c /AF MIN
4.1 VSI VSI OK
This Command: addshelf 4.1 v 1 1
Next Command:
Add a VSI controller link to a BPX node by entering the addshelf command at the desired BXM port as follows:
addshelf 13.2
sw237 TN StrataCom BPX 8620 9.2.L3 May 10 1999 14:48 PST
TRK Type Current Line Alarm Status Other End
4.1 [T3 Clear - OK VSI(VSI)
10.1 OC-3 Clear - OK VSI(VSI)
10.5 OC-3 Clear - OK VSI(VSI)
13.1.1 OC-3 Clear - OK -
13.2 OC-3 Clear - OK -
This Command: addshelf 13.2
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:
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.
Add Y-cable redundancy.
addyred <primary slot> <secondary slot>
delyred, dspyred, prtyred
| Privilege | Jobs | Log | Node | Lock |
1-4 | No | Yes | IGX, BPX | Yes |
addyred 25 26
Add Y-cable redundancy to the SDP/SDI card sets in slots 25 and 26.
beta TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 14:27 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
2 Pri 3 BXM LM-BXM
3 Sec 2 BXM LM-BXM
Last Command: addcdred 2 3
Next Command:
| Parameter | Description |
|---|---|
primary slot | Specifies the slot number of the primary card set. |
secondary slot | Specifies the slot number of the secondary card set. |
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 Rel 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 label 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.
Configure Qbin
cnfqbin <slot number>.<port number>.<vtrk>
dspqbin
| Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | No | BPX | No |
cnfqbin 13.1
Create a Qbin configuration on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS.
sw57 TN SuperUser BPX 8600 9.2 Mar. 10 1997 10:41 GMT
Port/Trunk: 13.1 [ACTIVE ]
Qbin Id :
Enable Qbin (Y/N) :
Minimum Bandwidth :
Qbin Discard threshold:
Low CLP threshold: [80] %
High CLP threshold: [80] %
EFCI threshold: [30]%
Last Command: cnfqbin 13.1
cnfqbin 4.1 10
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:
For all other parameters, accept the (default).
The previous parameters can also be set for Qbin 10 as follows:
Sample Display:
n4 TN SuperUser BPX 15 9.2 Apr. 4 1998 16:41 PST
Qbin Database 4.1 on BXM qbin 10
Qbin State: Enabled
Minimum Bandwidth: 0
Qbin Discard threshold: 65536
Low CLP/EPD threshold: 95%
High CLP/EPD threshold: 100%
EFCI threshold: 40%
This Command: cnfqbin 4.1 10
'E' to Enable, 'D' to Disable [E]:
Next Command:
n4 TN SuperUser BPX 8620 9.2 Apr. 4 1998 16:41 PST
Qbin Database 4.1 on BXM qbin 10
Qbin State: Enabled
Minimum Bandwidth: 0
Qbin Discard threshold: 65536
Low CLP/EPD threshold: 95%
High CLP/EPD threshold: 100%
EFCI threshold: 40%
Last Command: cnfqbin 4.1 10 e 0 65536 95 100 40
Next Command:
| Parameter | Description |
|---|---|
slot.port | Specifies the BXM card slot and port number. |
Qbin ID | Specifies the ID number of the Qbin available for use by the LSC (MPLS Controller) for VSI. The range is 0 to 255.; 0 is the default. Always use 10 in 9.1. |
Enable Qbin | Answer yes or no to enable your Qbin configuration. |
Minimum Bandwidth | Specifies the minimum bandwidth in cells per second available for the Qbin. The range is 0 to 352207; 0 is the default. |
Qbin Discard Threshold | Specifies the threshold in percentage for Qbin discard. The range is 0 to 100. |
CLP Low Threshold | Specifies the threshold in percentage for CLP low. The range is 0 to 100; 80% is the default. |
CLP High Threshold | Specifies the threshold in percentage for CLP high. The range is 0 to 100; 80% is the default. |
EFCI threshold | Specifies the threshold in percentage for EFCI. The range is 0 to 100; 30% is the default. |
Template | Specifies that the interface service class template should be used to configure the Qbin parameters. Thus the cnfqbin command will use the card's Qbin values from the Qbin template. If you do not chose the template option, you can enter your own desired values for the Qbin parameters. |
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.
.
| Qbin | Max Qbin Threshold (usec) | CLP High | CLP Low/EPD | EFCI | Discard Selection |
|---|---|---|---|---|---|
| LABEL Template 1 | |||||
10 (Null, Default, Signalling, Tag0,4) | 300,000 | 100% | 95% | 100% | EPD |
11 (Tag1,5) | 300,000 | 100% | 95% | 100% | EPD |
12 (Tag2,6) | 300,000 | 100% | 95% | 100% | EPD |
13 (Tag3,7) | 300,000 | 100% | 95% | 100% | EPD |
14 (Tag Abr) | 300,000 | 100% | 95% | 6% | EPD |
15 (Tag unused) | 300,000 | 100% | 95% | 100% | EPD |
| PNNI Templates 2 (with policing) and 3 | |||||
10 (Null, Default, CBR) | 4200 | 80% | 60% | 100% | CLP |
11 (VbrRt) | 53000 | 80% | 60% | 100% | EPD |
12 (VbrNrt) | 53000 | 80% | 60% | 100% | EPD |
13 (Ubr) | 105000 | 80% | 60% | 100% | EPD |
14 (Abr) | 105000 | 80% | 60% | 20% | EPD |
15 (Unused) | 105000 | 80% | 60% | 100% | EPD |
| Full Support for ATMF and reduced support for Tag CoS without Tag-Abr Templates 4 (with policing) and 5 | |||||
10 (Tag 0,4,1,5, Default, UBR, Tag-Abr*) | 300,000 | 100% | 95% | 100% | EPD |
11 (VbrRt) | 53000 | 80% | 60% | 100% | EPD |
12 (VbrNrt) | 53000 | 80% | 60% | 100% | EPD |
13 (Tag 2,6,3,7) | 300,000 | 100% | 95% | 100% | EPD |
14 (Abr) | 105000 | 80% | 60% | 20% | EPD |
15 (Cbr) | 4200 | 80% | 60% | 100% | CLP |
| Full Support for Tag ABR and ATMF without Tag CoS Templates 6 (with policing) and 7 | |||||
10 (Tag 0,4,1,5,2,6,3,7 Default, UBR) | 300,000 | 100% | 95% | 100% | EPD |
11 (VbrRt) | 53000 | 80% | 60% | 100% | EPD |
12 (VbrNrt) | 53000 | 80% | 60% | 100% | EPD |
13 (Tag-Abr) | 300,000 | 100% | 95% | 6% | EPD |
14 (Abr) | 105000 | 80% | 60% | 20% | EPD |
15 (Cbr) | 4200 | 80% | 60% | 100% | CLP |
| Full Support for Tag CoS and reduced support for ATMF Templates 8 (with policing) and 9 | |||||
10 (Cbr, Vbr-rt) | 4200 | 80% | 60% | 100% | CLP |
11 (Vbr-nrt, Abr) | 53000 | 80% | 60% | 20% | EPD |
12 (Ubr, Tag 0,4) | 300,000 | 100% | 95% | 100% | EPD |
13 (Tag 1, 5, Tag-Abr) | 300,000 | 100% | 95% | 6% | EPD |
14 (Tag 2,6) | 300,000 | 100% | 95% | 100% | EPD |
15 (Tag 3, 7) | 300,000 | 100% | 95% | 100% | EPD |
| Template Object Name | Template Units | Template Range/Values |
|---|---|---|
Qbin Number | enumeration | 0 -15 (10-15 valid for VSI) |
Max Qbin Threshold | u sec | 1-2000000 |
Qbin CLP High Threshold | % of max Qbin threshold | 0 - 100 |
Qbin CLP Low Threshold | % of max Qbin threshold | 0 - 100 |
EFCI Threshold | % of max Qbin threshold | 0 - 100 |
Discard Selection | enumeration
| 1 - CLP Hystersis 2 - Frame Discard |
Weighted Fair Queueing | enable/disable | 0: Disable 1: Enable |
Use the cnfrsrc command to partition resources for Automatic Routing Management PVCs, VSI-MPLS (Multiprotocol Label Switching), or VSI-PNNI (Private Network to Network Interface).
You can configure a port, trunk, or virtual trunk to support VSI. 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:
Configurable resources (using cnfrsrc) are:
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.
The PVC VIP ranges are added to facilitate migration of PVCs to PNNI SPVCs. PVC VIP ranges are allowed to overlap with the VSI VPI range if the VSI partition is for PNNI. Overlapping of PVC VPI range with MPLS VPI range is not supported. When overlapping VIP range, users will be asked if the VSI partition is for MPLS. If it is, the command will fail.
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.
If none of the PVC VPI range is defined, when enabling a partition, if [start_VSI_VPI, end_VSI_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.
If PVC VIP ranges are defined such that they covers all PVCs including VSI control VCs, users are allowed to enable a VSI partition with VPI range overlapping with the PVC VPI ranges. Thus, if VPI 10 is used for VSI control VC on an interface, then you can include VPI 10 in a VSI partition if it is also included in the PVC VPI range for that interface. A warning message of VPI overlapping will 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).
| ifci parameters | Min | Max |
|---|---|---|
lcns | min_lcnsi | max_lcnsi |
bw | min_bwi | max_bwi |
vpi | min_vpi | max_vpi |
The controller is supplied with a logical LCN connection number, that is slot, port, and so on. Information is converted to a logical connection number (lcn).
Some ranges of values available for a partition are listed in Table 16-10:
| Partition | Range |
|---|---|
trunks | 1-4095 VPI range |
ports | 0-4095 (NNI), 0-255 (UNI) |
virtual trunk | Only one VPI available per virtual trunk since a virtual trunk is currently delineated by a specific VP |
virtual trunk | Each virtual trunk can either be Automatic Routing Management or VSI, not both |
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.
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.
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 label switching connections. The traditional PVC connections are configured directly on the BPX platform, and label switching connections are set up by the TSC using the VSI. The following resources are partitioned on each interface:
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), or PNNI SPVCs/SVCs.
See Table 16-11 for a listing of cnfrsrc parameters, ranges and values, and descriptions. These parameters appear on the cnfrsrc screen.
| Object Name | Range/Values | Default | Description |
|---|---|---|---|
VSI Start LCN | 0... 64K-1 | NA | Start LCN for the whole VSI partition. Each VSI sub-partition (specific partition-id) will be given lcns from this partition. subject to the min/max ranges for that partition-id specified in object 3. The Start LCN once set will not be permitted to change if there are any active/configured VSI partitions. |
VSI End LCN | 0...64 K-1 | NA | End LCN for the whole VSI partition. If End LCN cannot be satisfied due to existing VSI connections or other constraints in this range then firmware will reject this request with a get response (same message tag) with this Object indicating the possible new End LCN that firmware can accommodate. |
VSI partition | 1...3 | 0 | identifies the partition |
Partition state | 0 = Disable Partition 1 = Enable Partition | NA | For Partition state = 1, Objects (8, 9, A, B, C, D, E, F) are mandatory |
Min LCNs | 0...card | NA | Min lcns (conns) guaranteed for this partition |
Max LCNs | 0...Card limit | NA | Maximum LCNs permitted on this partition |
Start VPI | 0 ... 4095 | NA | Partition Start VPI |
End VPI | 0 ... 4095 | NA | Partition End VPI |
Min Bw | 0...port bandwidth | NA | Minimum Partition bandwidth |
Max Bw | 0...port bandwidth | NA | Maximum Partition bandwidth |
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.
Configure resources
cnfrsrc <slot.port.vtrk>
or
cnfrsrc <slot>.<port>.<vtrk> <maxpvclcns><maxpvcbw><configurepvcvpirange> <pvcstartvpi><pvcendvpi><pvcstartvpi><pvcendvpi><pvcstartvpi><pvcendvpi><pvcstartvpi><pvcendvpi><configurevsipart><partition> <e/d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw>
dsprsrc
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | No |
cnfrsrc 9.1 256 96000 N N
Configure resource for port 9.1.
sw215 TN Cisco BPX 8620 9.3.f9 May 31 2000 15:29 GMT
Port : 9.1
Full Port Bandwidth: 96000
Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 96000
(CAC Reserve: 0)
PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1
PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1
Partition : 1 2 3
Partition State : Disabled Disabled Disabled
VSI LCNS (min/max): 0 /0 0 /0 0 /0
VSI VPI (start/end): 0 /0 0 /0 0 /0
VSI BW (min/max): 0 /0 0 /0 0 /0
VSI ILMI Config: CLR CLR CLR
Last Command: cnfrsrc 9.1 256 96000 N N
Next Command:
cnfrsrc 12.1 800 348207 y 1 E 100 3000 10 300 2000 96000
sonofsam TN Cisco BPX 8620 9.3.0k June 20 2000 08:51 GMT
Trunk : 12.1
Full Port Bandwidth: 353208
Maximum PVC LCNS: 800 Maximum PVC Bandwidth: 252207
(Statistical Reserve: 5000)
PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1
PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1
Partition : 1 2 3
Partition State : Enabled Disabled Disabled
VSI LCNS (min/max): 100 /3000 0 /0 0 /0
VSI VPI (start/end): 10 /300 0 /0 0 /0
VSI BW (min/max): 2000 /96000 0 /0 0 /0
VSI ILMI Config: SET CLR CLR
Last Command: cnfrsrc 12.1 800 348207 y 1 E 100 3000 10 300 2000 96000
Partition resource on trunk 12.1 on the BPX to support VSI service such as MPLS or PNNI.
|
Note By default the LSC will use either a starting VSI VPI of 1 or 2 for label 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 label switching VPI interface configuration command can be used on the TSC to override the defaults |
|
Note The VSI range for label 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 label 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.
cnfrsrc 9.6.1 256 3096
Configure virtual port 6.1 on the BXM card in slot 9 with a maximum of 256 PVC LCNS and a bandwidth of 3096.
sw215 TN Cisco BPX 8620 9.3.f9 May 31 2000 15:28 GMT
Port : 9.6.1
Full Port Bandwidth: 3096
Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 3096
(CAC Reserve: 0)
PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1
PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1
Partition : 1 2 3
Partition State : Disabled Disabled Disabled
VSI LCNS (min/max): 0 /0 0 /0 0 /0
VSI VPI (start/end): 0 /0 0 /0 0 /0
VSI BW (min/max): 0 /0 0 /0 0 /0
VSI ILMI Config: CLR CLR CLR
Last Command: cnfrsrc 9.6.1 256 3096
| Parameter | Description | ||
|---|---|---|---|
slot.port.vtrk | Specifies the BXM card slot and port number and virtual trunk. | ||
Maximum PVC LCNs | The maximum number of LCNs allocated for Automatic Routing Management PVCs for this port. The range depends upon the card type (1-11771 for the BNI T/E3 and 1-15867 for the BNI OC) 256 is the default. The default is 256 only if 256 are available. If other ports and trunks on the card have been configured to use LCNs such that there are only 100 remaining, then the default value for the newly added port would be 100. In this instance trunk upping would be blocked indicating that there are not enough LCNs to support the trunk. For trunks, there are additional LCNs allocated for Automatic Routing Management that are not configurable. You can use the dspcd <slot> command to display the maximum number of LCNs you can configure using the cnfrsrc command for the given port. For trunks, configurable LCNs represent the LCNs remaining after the BCC has subtracted the networking LCNs needed. A trunk has 270 networking LCNs, or channels. You can use the dspcd command to display VSI channels also. For a port card, a larger number is shown, as compared with a trunk card. This is because a trunk uses 270 networking LCNs, as compared with a port card, which uses no networking LCNs. You can use dspcd to display VSI channels also. Setting this field to "0" would disable Automatic Routing Management PVCs on the specified port.
Logical Interface (slot.port [.vtrk] for trunks and slot.port for lines). The bandwidth is logical interface based. The default value for this object is the line rate of this interface. | ||
Maximum PVC Bandwidth | Specifies the maximum bandwidth of the port allocated for Automatic Routing Management use depends upon the card type (1-11771 for the BNI T/E3 and 1-15867 for the BNI OC); 256 is the default. The default is 256 only if 256 is available. If other ports and trunks on the card have been configured to use LCNs such that there are only 100 remaining, then the default value for the newly added port would be 100. In this instance trunk upping would be blocked indicating that there are not enough LCNs to support the trunk. You can configure the Maximum PVC Bandwidth value for ports, but not for trunks.
| ||
Configure PVC VCI Range | You will be prompted when configuring a port or feeder trunk only. Answer Yes or No to begin configuring the PVC VPI range. Enter Y if you are migrating PVCs on this interface to PNNI SPVCs, otherwise answer N. If you enter Y, you will be prompted for the four PVC VPI ranges. | ||
Start of PVC VPI range x | User can define 4 VPI ranges. ALl the existing PVCs have to be using a VPI in one of the defined PVC VIP ranges. | ||
End of PVC VPI range x | Together with Start of PVC VPI range, it defines a VPI range for PVCs. | ||
Configure Partition | Answer yes or no to begin configuring resources for the partition. To configure Automatic Routing Management PVCs, enter n for No. You will not be prompted to enter VSI options to configure VSI partition resources. | ||
Partition ID | Specifies the ID number of the partition. In previous releases, use 1. In release 9.1, use 1 for the partition ID. (The default is 0. The range of values for Partition ID is 1-3 In this release, you may use 2. | ||
Enable Partition | Answer yes or no to enable your configured partition. | ||
Minimum VSI LCNs | The minimum number of LCNs guaranteed for this partition. Range is from 0 to card limit: 0 is the default. The VSI controller guarantees at least this many connection endpoints in the partition, provided there are sufficient free LCNs in the common pool to satisfy the request at the time the partition is added. When a new partition is added or the value is increased, it may be that existing connections have depleted the common pool so that there are not enough free LCNs to satisfy the request. The BXM gives priority to the request when LCNs are freed. The net effect is that the partition may not receive all the guaranteed LCNs (min LCNs) until other LCNs are returned to the common pool. You can increase this value dynamically when there are enough unallocated LCNs in the port group to satisfy the increase. You may not decrease the value dynamically. All partitions in the same port group must be deleted first and reconfigured in order to reduce this value. To avoid this deficit condition, which could occur with maximum LCN usage by a partition or partitions, it is recommended that all partitions be configured ahead of time before adding connections. Also, it is recommended that all partitions be configured before adding a VSI controller using the addshelf command. | ||
Maximum VSI LCNs | The total number of LCNs the partition is allowed for setting up connections. The min LCNs is included in this calculation. If max LCNs equals min LCNs, then the max LCNs are guaranteed for this partition. Otherwise, (max - min) LCNs are allocated from the common pool on a FIFO basis. If the common pool is exhausted, new connection setup requests will be rejected for the partition, even though the maximum LCNs has not been reached. You may increase this value dynamically when there are enough unallocated LCNs in the port group to satisfy the increase. You may not decrease the value dynamically. All partitions in the same port group must be deleted first and reconfigured in order to reduce this value. Different types of BXM cards support different maximum values. If you enter a value greater than the allowed maximum, a message is displayed with the allowable maximum value. Note that you must specify a value greater than 0 for the Maximum VSI LCNs, Maximum PVC Channels, and Maximum PVC Bandwidth parameters. Otherwise, you will not be able to add any connections on a BXM card. | ||
Start VSI VPI | By default the LSC (for example, the 6400, 7200 or 7500 series router) will use either a starting VSI VPI of 1 or 2 for MPLS, whichever is available. If both are available, a starting VSI VPI of 1 is used. The VPI range should be 2-15 on a BPX 8620 VSI. The VSI range for MPLS on the BPX 8620 is configured as a VSI partition, usually VSI partition number 1. VSI VPI 1 is reserved for Automatic Routing Management PVCs. (This restriction applies only to trunks, not to ports. For a port, you can use any VPI value.) For a port UNI, the VPI range is 1 to 255. For a port NNI, the range is 1 to 4095. For trunks that do not have Automatic Routing Management configured, the VPI ranges are the same as for ports. The VSI partition for MPLS should start at VPI 2. If VPI 2 is not to be used, you can use the MPLS VPI interface configuration on the LSC to override the defaults. For trunks with Automatic Routing Management configured, the range is 2 to 4095. Always set to 2 for trunks. For ports in port mode it should be set to "1". By default the TSC (for example, 6400, 7200 or 7500 series router) will use either a starting VSI VPI of 1 or 2 for label switching, whichever is available. They default to 1. | ||
End VSI VPI | Two VPIs are sufficient for Release 9.1, although it may be advisable to reserve a larger range of VPIs for later expansion, for example, VPIs 2-15. The range is the <Start VSI VPI > value to 4095. | ||
Minimum VSI Bandwidth | The minimum port bandwidth that can be used by this partition in cells per second. The range is 0 to <Maximum Line Rate>. For example, the OC-3 line rate is 352207; 0 is the default. | ||
Maximum VSI Bandwidth | The maximum port bandwidth that can be used by this partition. This value is used for VSI Qbin bandwidth scaling. The range is 0 to <Maximum Line Rate>. For example, the OC-3 line rate is 352207; 0 is the default. |
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.
A default service template is assigned to a logical interface (VI) when you up the interface by using upport/uptrk.
For example:
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:
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:
Configure a service class template and assign it to an interface
cnfvsiif <slot.port.vtrk> <tmplt_id>
cnfrsrc, dsprsrc, cnfqbin, dspqbin
| Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | Yes | BPX | Yes |
cnfvsiif 11.1 2
sw53 TN StrataCom BPX 8600 9.2.a5 Date/Time Not Set
Port: 11.1
Service Class Template ID: 2
Last Command: cnfvsiif 11.1 2
Next Command:
Use the cnfvsipart command to enable or disable VSI ILMI support.
Configure VSI paritition characteristics
cnfvsipart <slot.port.[vtrk]> <part_id> <enable_option>
| Parameter | Description |
|---|---|
slot.port.[vtrk] | Slot, port (and virtual port if applicable) of the interface. |
part_id | Partition ID corresponding to the VSI partition. |
enable_option | This parameter indicates whether to enable or disable VSI ILMI functionality. Valid values:
|
cnfrsrc, dspvsipartcnf, cnfport, cnftrk
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | Yes | BPX | Yes |
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. |
Delete VSI capabilities from a AAL5 feeder interface
delctrlr <slot.port> <controller id>
| Parameter | Description |
|---|---|
slot.port | Slot and port numbers corresponding to the feeder trunk. |
controller id | Controller ID number corresponding to the PNNI controller you are deleting. ID numbers should correspond to an active PNNI controller. Valid controller values are 1 - 32 |
addctrlr, dspctrlrs, dspnode
| Privilege | Jobs | Log | Node | Lock |
1 | Yes | Yes | BPX | Yes |
delctrlr 10.3
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."
night TN StrataCom BPX 8600 9.2.00 Apr. 11 1998 14:31 GMT
BPX Controllers Information
Trunk Name Type Part Id Ctrl Id Ctrl IP State
10.3 PAR VSI 1 2 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled
Last Command: delctrlr 10.3
night TN StrataCom BPX 8600 9.2. Apr. 11 1998 14:31 GMT
BPX Controllers Information
Trunk Name Type Part Id Ctrl Id Ctrl IP State
10.3 PAR VSI 1 2 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled
Last Command: delctrlr 10.3
delctrlr <slot.port><controller_id>
Deletes controller from port 3 on slot 10, with controller name E, and controller ID of 1.
night TN StrataCom BPX 8600 9.2.00 Apr. 11 1998 14:31 GMT
BPX Controllers Information
Trunk Name Type Part Id Ctrl Id Ctrl IP State
10.3 PAR VSI 1 1 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled
Last Command: delctrlr 10.3
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.
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.
Delete an interface shelf
delshelf <trunk> | <shelf-name>
addshelf, dspnode
| Privilege | Jobs | Log | Node | Lock |
1 | Yes | Yes | IGX, BPX | Yes |
delshelf 4.1
Delete shelf trunk A241 from a BPX node.
nmsbpx23 TN SuperUser BPX 8600 9.2 Aug. 16 1998 13:26 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
1.3 AXIS240 AXIS OK
11.2 A242 AXIS OK
Last Command: delshelf A241
Shelf has been deleted
Next Command:
| Parameter | Description |
|---|---|
trunk or shelf name | Specifies the slot and port number of the trunk or the name of the interface shelf. |
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.
Delete Y-cable redundancy
delyred <primary slot>
addyred, dspyred, prtyred
| Privilege | Jobs | Log | Node | Lock |
1-4 | No | Yes | IGX, BPX | Yes |
delyred 16
Disable Y-cable redundancy at slot 16.
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.
Display channel distribution
dspchuse <slot >
dspvsiif, dspvsipartinfo
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | No |
Parameter | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
dspchuse 13
Display channel management summary for slot 13.
sw53 TN StrataCom BPX 8600 9.2.10 Jan. 10 1999 14:31 GMT Channel Management Summary for Slot 13 max used avail netw pvc cnfg vsi mgmt vsi cnf card 13: 16320 8675 7645 1358 2304 13 5000 port grp 1: 8160 5849 2311 813 1024 12 4000 port grp 2: 8160 2825 5335 545 1280 0 1000 pvc cnfg pvc used nw used vsi mgmt vsi min vsi max port 1: 256 0 271 0 part 1: 1000 4000 part 2: 2000 4000 port 2: 256 0 271 0 port 3: 256 0 271 12 This Command: dspchuse 13 Continue?
dspchuse 3
Display channel management summary for slot 3.
Use the dspctrlrs command to display all VSI controllers, such as a SES PNNI controller on a BPX or IGX node. This command lists:
|
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.
Displays all VSI controllers, for example, all PNNI controllers such as PNNI, on a BPX or IGX node.
dspctrlrs <slot.port><controller name string><partition_id><controller_id>
addctrlr, addshelf, cnfctrlr, delctrlr, dspnode
| Privilege | Jobs | Log | Node | Lock |
1 | No | Yes | IGX, BPX | Yes |
dspctrlrs
Display VSI controllers on BPX node sw174.
sw174 TRM StrataCom BPX 8620 9.2.xS Sep 20 1998 14:31 GMT
BPX 8620 VSI controller information
Ctrl Id Part Id Trunk Ctrlr Type Intfc Type Name
1 1 2.1 VSI AAL5 SIMFDR0
Last Command: dspctrlrs
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 label switching connections. Check the queue buffer 10 configurations for port 4.1 as follows:
Display Qbin
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. |
cnfqbin
| Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | No | BPX | No |
dspqbin 13.1
Display the current Qbin configuration on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS.
sw53 TN StrataCom BPX 8600 9.2.a5 Date/Time Not Set
Qbin Database 11.1 on BXM qbin 10 (Configured by ATMF1 Template)
(EPD Disabled on this qbin)
Qbin State: Enabled
Qbin Discard threshold: 8
Low CLP threshold: 90%
High CLP threshold: 95%
EFCI threshold: 50%
Last Command: dspqbin 11.1 10
Next Command:
dspqbin 4.1 10
Display the current Qbin configuration on slot 4, port 1, Qbin 10.
sw237 TN StrataCom BPX 8620 9.2.L3 May 10 1999 14:42 PST
Qbin Database 4.1 on BXM qbin 10 (Configured by MPLS1 Template)
(EPD Enabled on this qbin)
Qbin State: Enabled
Discard Threshold: 28800 cells
EPD Threshold: 95%
High CLP Threshold: 100%
EFCI Threshold: 100%
Last Command: dspqbin 4.1 10
dspqbin 2.1.1 10
Display Qbin 10 on slot 2, port 1, virtual trunk 1.
Qbin Database 2.1.1 on BXM qbin 10 Qbin Discard threshold: 9800 Low CLP/EPD threshold: 60% High CLP threshold: 80% EFCI threshold: 80%
dspqbin 13.1.1 10
Display Qbin 10 configuration for virtual trunk 1, on port 1 of card slot 13.
sw237 TN StrataCom BPX 8620 9.2.L3 May 10 1999 14:42 PST
Qbin Database 13.1.1 on BXM qbin 10 (Configured by ATMF1 Template)
(EPD Disabled on this qbin)
Qbin State: Enabled
Discard Threshold: 12 cells
Low CLP Threshold: 60%
High CLP Threshold: 80%
EFCI Threshold: 100%
Last Command: dspqbin 13.1.1 10
| Parameter | Description |
|---|---|
slot.port | Specifies the BXM card slot and port number. |
Qbin ID | Specifies the ID number of the Qbin available for use by the LSC (MPLS Controller) for VSI. The range is 0 to 255; 0 is the default. Always use 10 in Release 9.1; use Qbin 13 in Release 9.2. |
Table 16-18 below 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.
| Object (Parameter) Name | Range/Values | Default | Description |
|---|---|---|---|
Service Template ID | 0 - 7 | R | Service Class Template number for this parameter set. |
Qbin Number | 0 - 15 | R | Identifies the target Qbin to modify. |
Direction | 0: Ingress 1: Egress | R | Indicates whether the Qbin configuration applies to the ingress or egress of the card. |
Priority | 0 - 15 | R | Parameter defines the relative priority of the Qbin in relationship to the other Qbins in the VI. Zero is the highest priority and 15 is the lowest priority. |
Discard Selection | 1 - CLP Hysteresis 2 - Frame Discard | R | Indicates whether Qbin should perform the CLP Hysteresis or the Frame Discard option. The Qbin can only be configured to do one or the other. |
Max Threshold | 0 - ? cells | R | Determines the amount of cell memory to dedicated to this Qbin. |
CLP High Threshold | 0 - 100% | R | Parameter determines at which level in the Qbin CLP-tagged cells get discarded. Discard continues until the Qbin depth drops below the Qbin CLP Low Threshold. |
CLP Low Threshold | 0 - 100% | R | Parameter determines at which level in the Qbin CLP-tagged cells get admitted. |
EFCI Threshold | 0 - 100% | R | Parameter determines at which level in the Qbin EFCI bits get tagged in the departing cell(s). |
EPD 0 Threshold | 0 - 100% | R | Qbin Frame Discard threshold for CLP 0 traffic. |
WFQ enable | 0: Disable 1: Enable | R | Indicates whether weighted fair queueing/ traffic shaping is enabled for this Qbin. |
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:
Additional service template commands you can use are:
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.
Display Qbin template
dspqbint <template #><qbin #>
Display a service class template number, which identifies one of the templates between 1-3, and the Qbin number.
dspsct, dspqbin, cnfrsrc, dsprsrc, cnfvsiif, dspvsiif
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | No |
dspqbint <template #> <qbin>
Displays the Qbin template number 1 for a specified Qbin (10).
sw53 TN StrataCom BPX 8600 9.2.a5 Date/Time Not Set
Qbin Template: 1 Qbin: 10
CLP High 95 (% of Max Depth)
CLP Low 90 (% of Max Depth)
EFCI Threshold 50 (% of Max Depth)
EPD Enabled
Vc Shaping Enabled
Max Depth 2000 (micro secs)
Last Command: dspqbint 1 10
Next Command:
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.
Display resources
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. |
cnfrsrc, cnfqbin, dspqbin
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | No |
dsprsrc 3.2.1
Display partition resources on the OC-3 trunk on card slot 3, port 2, and virtual trunk 1 on the BPX node.
sw57 TN SuperUser BPX 8620 9.2 Mar. 10 1998 10:41 GMT Port/Trunk : 3.2.1 Template: 3 Maximum PVC LCNS: 256 Maximum PVC Bandwidth:1411679 Min Lcn(1) : 0 Min Lcn(2) : 0 Partition 1 Partition State : Enabled Minimum VSI LCNS: 0 Maximum VSI LCNS: 1 Used VSI LCNs: 25 Start VSI VP: 1 End VSI VPI : 1 Minimum VSI Bandwidth : 0 Maximum VSI Bandwidth : 0
dsprsrc 13.1
Display partition resources on the OC-3 trunk on port 1 of slot 13 on the BPX to support MPLS.
sw57 TN SuperUser BPX 8620 9.2 Mar. 10 1997 10:41 GMT
Port/Trunk: 13.1 [ACTIVE ]
Interface: OC-3-2
Available Channels: 16000
Maximum PVC Channels : 256 (default)
Maximum PVC Bandwidth : 352207 cps
Partition ID : 0
VSI Signalling VCI : 32 (default)
Minimum VSI LCNs : 0
Maximum VSI LCNs : 0
Start VSI VPI : 0
End VSI VPI : 0
Minimum VSI Bandwidth : 0 cps
Maximum VSI Bandwidth : 0 cps
Last Command: dsprsrc 13.1
dsprsrc 4.1 1
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.
sw237 TN StrataCom BPX 8620 9.2.L3 May 10 1999 14:27 PST
Port/Trunk :4.1
Maximum PVC LCNS: 256 Maximum PVC Bandwidth:95000
Partition 1
Partition State : Disable
Last Command:dsprsrc 4.1 1
dsprsrc 4.1 1
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.)
sw237 TN StrataCom BPX 8620 9.2.L3 May 10 1999 14:35 PST
Port/Trunk :4.1
Maximum PVC LCNS: 256 Maximum PVC Bandwidth:92000
Partition 1
Partition State : Enabled
Minimum VSI LCNS: 20
Maximum VSI LCNS: 30
Start VSI VPI: 4
End VSI VPI : 6
Minimum VSI Bandwidth : 2000 Maximum VSI Bandwidth : 3000
Last Command:dsprsrc 4.1 1
dsprsrc 4.1 1
Display partition resources on VSI trunk 4.1.
n4 TN SuperUser BPX 8620 9.2 Apr. 4 1998 16:47 PST
Port/Trunk : 4.1
Maximum PVC LCNS: 256 Maximum PVC Bandwidth:26000
Min Lcn(1) : 0 Min Lcn(2) : 0
Partition 1
Partition State : Enabled
Minimum VSI LCNS: 512
Maximum VSI LCNS: 7048
Start VSI VPI: 2
End VSI VPI : 15
Minimum VSI Bandwidth : 26000 Maximum VSI Bandwidth : 100000
Last Command: dsprsrc 4.1 1
Next Command:
dsprsrc 3.7.10
Display partition resources on VSI trunk 3.7, and partition ID 10. (If the partition is enabled, more parameters related to how resources are partitioned are displayed.)
| Parameter | Description |
|---|---|
slot.port | Specifies the BXM card slot and port number. |
Partition ID | Specifies the ID number of the partition available for use by the LSC (MPLS Controller) for VSI. The range is 0 to 255; 0 is the default. Always use 1 in Release 9.1. |
The dspsct command displays a list of nine supported Service Class Templates (SCT).
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.
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
QoS guarantees
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.
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:
A list of supported service templates and associated Qbins, and service types is shown in Table 16-20.
| Template Type | Service Type ID | Service Type | Parameters | Associated Qbin |
|---|---|---|---|---|
VSI Special Types | 0x0001 0x0002 | Default Signaling |
| 13 10 |
ATMF Types ATMF1 and ATMF2 templates (for PNNI controllers) | 0x0100 0x0101 0x0102 0x0103 0x0104 0x0105 0x0106 0x0107 0x0108 0x0109 0x010A 0x010B | cbr.1 vbr.rt1 vbr2.rt vbr3.rt vbr1.nrt vbr.2nrt vbr.3nrt ubr.1 ubr.2 abr cbr.2 cbr.3 | ATM Forum (ATMF) Types
See dspsct command for sample parameters for various service types, such as VbrRt1, Cbr1, and so on.
| 10 11 11 11 12 12 12 13 13 14 10 10 |
MPLS Types (for MPLS controllers) | 0x0001 0x0200 0x0201 0x0202 0x0203 0x0204 0x0205 0x0206 0x0207 0x0210 | Default Signaling label cos0 label cos1 label cos2 label cos3 label cos4 label cos5 label cos6 label cos7 label ABR |
| 13 10 10 11 12 13 10 11 12 13 14 |
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.
Qbin # Description CoS Buffer (Qbin) to use for this CoS
Range/Values: 10 - 15 (for Release 9.2)
Units: enumeration UPC Enable Description: Enable/Disable Policing function. The first 2 values are consistent with the definition for the older cards. Option #2 and #3 are new and provide the ability to turn on policing on just GCRA #1 (PCR policing) or #2 (SCR policing). Range/Values: 0 -3
0: Disable both GCRAs
1: Enable both GCRAs
2: Enable GCRA #1 only (PCR policing)
3: Enable GCRA #2 only (SCR policing) Units: enumeration UPC CLP Selection Description: Selects processing of policing Buckets based on the CLP bit. Range/Values: 0 -2
0 - Bk 1: CLP (0+1), Bk 2: CLP (0)
1 - Bk 1: CLP (0+1), Bk 2: CLP (0+1)
2 - Bk 1: CLP (0+1), Bk 2: Disabled Units: enumeration Policing Action (GCRA #1) Description: Indicates how cells that fail the second bucket (SCR bucket) of the policer should be handled, if policing is enabled. Range/Values: 0 - Discard
1 - Set CLP bit
2 - Set CLP of untagged cells, disc. tag'd cells Units: enumeration Policing Action (GCRA #2) Description: Indicates how cells that fail the second bucket (SCR bucket) of the policer should be handled, if policing is enabled. Range/Values: 0 - Discard
1 - Set CLP bit
2 - Set CLP of untagged cells, disc. tag'd cells Units: enumeration PCR Description: Peak Cell Rate; used as default value if not supplied in VSI connection request. Range/Values: 0 - 100 Units: cells/sec MCR Description: Minimum Cell Rate; used as default value if not supplied in VSI connection request. Range/Values: 0 - 100 Units: cells/sec SCR Description: Sustained Cell Rate; used as default value if not supplied in VSI connection request. Range/Values: 0 - 100 Units: cells/sec ICR Description: Initial Cell Rate . Used only for ABR VCs to set initial ACR value after idle traffic period. Range/Values: 0 - 100 Units: cells/sec MBS Description: Maximum Burst Size - used to set bucket depth in policer function. Range/Values: 1 - 5M Units: cell count CoS Min BW Description: Bandwidth reserved for this Class of Service; used to initialize the CoS Buffer (Qbin) Minimum Service Rate (HW param. = ICG), and for CAC purposes (subject to CAC treatment type). Range/Values: 0% - 100% Units: % of Partition Min BW. CoS Max BW Description: Maximum value allowed for the sum of VC Min. BW's for this CoS; used by CAC (subject to CAC treatment type). Range/Values: 0% - 100% Units: % of Partition Max BW Scaling Class Description: Scaling table used for modifying per-VC thresholds under VI or Global cell-memory congestion. Range/Values: choices are 0 - 3, 0: CBR
1: VBR
2: ABR
3: UBR Units: enumeration CAC Treatment Description: Connection Admission Control algorithm used by this CoS Range/Values: 0 - 256 0: No CAC performed; all connections admitted. 1: LCN_CAC; check for LCN availability only; no BW consideration. 2: MINBW_CAC; LCN + simple min. BW test (sum_of_VC_min_BW <= CoS_max_BW) 3: CAC_2 w/ overbooking allowed 4: ECR_CAC; LCN + ECR calculation (from table) & BW test (sum_of VC_ECR <= Cos_max_BW). 5: CAC_4 w/ overbooking allowed 6: MEASURED_CAC; LCN + ECR calculation (from dynamic measurement) & BW test (sum_of VC_ECR <= Cos_max_BW). Units: enumeration VC Max Description: Maximum VC-cell-count threshold; all cells are discarded on a VC when this threshold has been exceeded. Range/Values: 0 - VI_max_cell_count Units: cell count VC CLPhi Description: VC cell count above which CLP=1 cells are discarded Range/Values: 0 - 100 Units: % of VC Max threshold VC CLPlo Description: VC cell count below which CLP=1 cells are no longer discarded (discards having begun when CLPhi was exceeded). Range/Values: 0 - 100 Units: % of VC Max threshold VC EPD Description: VC cell count above which AAL-5 frames are discarded Range/Values: 0 - 100 Units: % of VC Max threshold VC EFCI Description: VC cell count above which congestion notification is activated Range/Values: 0 - 100 Units: % of VC Max threshold VC Discard Selection Description: Choice of frame-based discard (EPD) or CLP-hysteresis Range/Values: 0 - 1
0: CLP Hysteresis
1: EPD Units: enumeration VSVD/FCES Description: For ABR VC's, enable/disable Virtual Source/Virtual Destination (VSVD) and/or Flow Control on External Segments (FCES) functionality Range/Values: 0 -2
0: None
1: VSVD
2: VSVD w/ FCES Units: enumeration ADTF ABR only parameter Description: ACR decrease time factor; idle time before ACR -> ICR Range/Values: 10 - 1023 Units: milliseconds RDF ABR only parameter Description: Rate Decrease Factor
ACR = ACR - (ACR * RDF) Range/Values: 2 - 512, in powers of 2 Units: Inverse decrease factor RIF ABR only parameter Description: Rate Increase Factor
ACR = ACR + (PCR * RDF) Range/Values: 2 - 512, in powers of 2 Units: Inverse decrease factor NRM ABR only parameter Description: Number of data cells between FRM cells Range/Values: 2 - 512, in powers of 2 Units: cells TRM ABR only parameter Description: Range/Values: Units: CDF ABR only parameter Description: Range/Values: Units: TBE ABR only parameter Description: Range/Values: Units: FRTT ABR only parameter Description: Range/Values: Units:
Display service class template (SCT)
dspsct [template #][service_type]
dspqbint, cnfvsiif, dspvsiif
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | No |
dspsct
Displays all the templates in the node.
sw53 TN StrataCom BPX 8620 9.2.a5 May 11 1999 14:24 PST
Service Class Templates
Template Name
1 MPLS1
2 ATMF1
3 ATMF2
Last Command: dspsct
Next Command:
dspsct 2
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).
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 17:48 PST
Service Class Map for ATMF1 Template
Service Class Qbin Service Class Qbin Service Class Qbin
Default 13 Cbr2 10
VbrRt1 11 Cbr3 10
VbrRt2 11
VbrRt3 11
VbrNRt1 12
VbrNRt2 12
VbrNRt3 12
Ubr1 13
Ubr2 13
Abr 14
Cbr1 10
Last Command: dspsct 2
Next Command:
dspsct 3
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).
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 17:45 PST
Service Class Map for ATMF2 Template
Service Class Qbin Service Class Qbin Service Class Qbin
Default 13 Cbr2 10
VbrRt1 11 Cbr3 10
VbrRt2 11
VbrRt3 11
VbrNRt1 12
VbrNRt2 12
VbrNRt3 12
Ubr1 13
Ubr2 13
Abr 14
Cbr1 10
Last Command: dspsct 3
Next Command:
dspsct 2 vbrrt1
Display service class template (SCT) for template number 2 called vbrrt1.
sw53 TN BPX 8620 9.2.a3 Apr. 13 1999 17:30 PST
Service Template:ATMF1 (2) Service Type: VbrRt1 (101)
Service Category VbrRt (101)
Qbin 11
UPC Enable GCRA_1_2
UPC CLP Selection CLP01_CLP01
Policing Action 1 DISCARD
Policing Action 2 DISCARD
Sustained Cell Rate 100 (% of PCR)
Maximum Burst Size 1024 (cells)
Scaling Class Scaled 3rd
CAC Treatment CAC4
VC Max Threshold 1280 (cells)
VC Dscd Selection Hystersis
VC CLP High 80 (% of Vc MAX
Threshold)
Last Command:dspsct 2 vbrrt1
sw236 TRM StrataCom BPX 8620 9.2.a8 May 11 1999 14:35 PST
Service Template:ATMF1 (2) Service Type: VbrRt1 (101)
VC CLP Low 35 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000
Last Command:dspsct 2 vbrrt1
dspsct 2 Abr
Display all the parameters of the service class template ID 2, specified by Abr.
sw53 TN StrataCom BPX 8600 9.2.a5 Date/Time Not Set
Service Template: ATMF1 (2) Class: Abr (104)
Service Class Type 109
Qbin 14
UPC Enable 2
UPC CLP Selection 2
Policing Action 1 2
Peak Cell Rate 100 (%age of PCR)
Minimum Cell Rate 50 (% of PCR)
Initial Cell Rate 50 (% of PCR)
Scaling Class 0
CAC Treatment 2
VC Max Threshold 0 (cells)
VC CLP High 75 (% of Vc MAX Threshold)
VC CLP Low 30 (% of Vc MAX Threshold)
This Command: dspsct 2 abr
Continue?
dspsct 1 Default
Displays the parameters for service class template 1 (the MPLS1 service class template), for the Default service type.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 17:53 PST
Service Template: MPLS1 (1) Service Type: Default (1)
Service Category Default (1)
Qbin 13
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000
Last Command: dspsct 1 Default
Next Command:
dspsct 1 Signaling
Displays the parameters for service class template 1 (the MPLS1 service class template), for the Signaling service type.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 17:57 PST
Service Template: MPLS1 (1) Service Type: Signaling (2)
Service Category Signaling (2)
Qbin 10
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 0 (cells)
VC Dscd Selection Hystersis
VC CLP High 75 (% of Vc MAX Threshold)
VC CLP Low 30 (% of Vc MAX Threshold)
Last Command: dspsct 1 signaling
Next Command:
CD MAJOR ALARM
dspsct 1 Signaling
Displays the parameters for service class template 1 (the MPLS1 service class template), for the Signaling service type.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 17:59 PST
Service Template: MPLS1 (1) Service Type: Tag0 (200)
Service Category Tag0 (200)
Qbin 10
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)
Last Command: dspsct 1 Tag0
Next Command:
dspsct 1 Tag0
Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 17:59 PST
Service Template: MPLS1 (1) Service Type: Tag0 (200)
Service Category Tag0 (200)
Qbin 10
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)
Last Command: dspsct 1 Tag0
Next Command:
dspsct 1 Tag1
Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 18:02 PST
Service Template: MPLS1 (1) Service Type: Tag1 (201)
Service Category Tag1 (201)
Qbin 11
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)
Last Command: dspsct 1 Tag1
Next Command:
dspsct 1 Tag2
Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 18:02 PST
Service Template: MPLS1 (1) Service Type: Tag1 (201)
Service Category Tag1 (201)
Qbin 11
UPC Enable NONE
Scaling Class Scaled 1st
CAC Treatment LCN
VC Max Threshold 61440 (cells)
VC Dscd Selection EPD
VC CLP High 100 (% of Vc MAX Threshold)
VC EPD 40 (% of Vc MAX Threshold)
Last Command: dspsct 1 Tag2
Next Command:
dspsct 1 VbrRt1
Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 18:09 PST
Service Template: ATMF1 (2) Service Type: VbrRt1 (101)
Service Category VbrRt (101)
Qbin 11
UPC Enable GCRA_1_2
UPC CLP Selection CLP01_CLP01
Policing Action 1 DISCARD
Policing Action 2 DISCARD
Sustained Cell Rate 100 (% of PCR)
Maximum Burst Size 1024 (cells)
Scaling Class Scaled 3rd
CAC Treatment CAC4
VC Max Threshold 1280 (cells)
VC Dscd Selection Hystersis
VC CLP High 80 (% of Vc MAX Threshold)
This Command: dspsct 2 VbrRt1
Continue?
dspsct 1 VbrRt1
Displays the service classes in the service template 3, which is a service class template for use with a PNNI controller.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 18:11 PST
Service Template: ATMF1 (2) Service Type: Cbr1 (100)
Service Category Cbr (100)
Qbin 10
UPC Enable GCRA_1
UPC CLP Selection CLP01
Policing Action 1 DISCARD
Scaling Class Scaled 4th
CAC Treatment CAC4
VC Max Threshold 160 (cells)
VC Dscd Selection Hystersis
VC CLP High 80 (% of Vc MAX Threshold)
VC CLP Low 35 (% of Vc MAX Threshold)
Cell Delay Variation Tolerance 250000
Last Command: dspsct 2 Cbr1
Next Command:
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.
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:
Display a service class template assigned to an interface.
dspvsiif <slot.port.vtrk> <tmplt_id>
cnfrsrc, dsprsrc, cnfqbin, dspqbin
| Privilege | Jobs | Log | Node | Lock |
1-6 | Yes | Yes | IGX, BPX | Yes |
dspvsiif 13.1.1
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.
sw237 TN StrataCom BPX 8620 9.2.L3 May 10 1999 14:39 PST
Virtual Trunk :13.1.1
Service Class Template ID:2
Last Command:dspvsiif 13.1.1
dspvsiif 11.1 2
Display a service class template assigned to an interface.
sw53 TN StrataCom BPX 8600 9.2.30 Date/Time Not Set
Port: 11.1
Service Class Template ID: 2
VSI Partitions
channels bw vpi
Part E/D min max min max start end ilmi
1 E 1000 4000 10000 40000 240 249 Off
2 E 2000 4000 20000 40000 250 255 On
Last Command: dspvsiif 11.1 2
Next Command:
Use this command to display VSI partition characteristics. It displays information about only VSI ILMI functionality. This command displays:
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.
Display VSI partition characteristics
dspvsipartcnf <slot.port.[vtrk]> [partition_id]
| Parameter | Description |
|---|---|
slot.port.[vtrk] | Slot, port (and virtual port if applicable) of the interface. |
partition_id | Partition ID corresponding to the VSI partition. This parameter is optional and if not specified, this command will display information about all VSI partitions. |
cnfrsrc, cnfvsipart, cnfport, cnftrk
| Privilege | Jobs | Log | Node | Lock |
1-2 | Yes | No | BPX | Yes |
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.
Display VSI statistics per partition
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.
cnfrsrc, dsprsrc, cnfvsiif, dspvsiif
| Privilege | Jobs | Log | Node | Lock | Multiple Users |
1-6 | No | No | BPX | Yes | Yes |
| Parameter | Description |
|---|---|
Min BW | Configured minimum bandwidth for this partition (for reference only). |
Max BW | Configured maximum bandwidth for this partition (for reference only). |
Used BW | Bandwidth currently used by connections on this partition. |
Available BW | Bandwidth currently available to connections on this partition. This is determined based on the minimum and maximum bandwidth configured for the partition and the bandwidth currently available in the common pool. |
Min Lcns | Configured minimum LCNs for this partition (for reference only). |
Max Lcns | Configured maximum LCNs for this partition (for reference only). |
Used Lcns | Number of LCNs currently used by connections in this partition. |
Available Lcns | Number of LCNs available to this partition. This is determined based on the minimum and maximum LCNs configured for the partition and the LCNs currently available in the common pool. |
dspvsipartinfo 3.1 1 10
Display VSI statistics for slot 3, port 1 for interface configured on partition ID 1, at an interval of every 10 seconds.
sw237 TN StrataCom BPX 8620 9.2.1G June 9 1999 17:32 PST
VSI Resources Status for trunk 3.1 Partition 1
Min Lcns : 0 Min BW (cps) : 0
Max Lcns : 20 Max BW (cps) : 0
Used Lcns : Used BW (cps) :
Available Lcns : Available BW(cps):
Next Command: dspvsipartinfo 3.1 1
dspvsipartinfo 11.1 2 10
Display VSI statistics for port 1 for interface configured on partition ID 2, at an interval of every 10 seconds.
sw53 TN StrataCom BPX 8600 9.2.10 Jan. 10 1999 14:31 GMT
VSI Resource Status for port 11.1 Partition 2
Min Lcns 1000 Min BW (cps) 20000
Max Lcns 4000 Max BW (cps) 40000
Used Lcns 500 Used BW (cps) 20000
Available Lcns: : 1000 Available BW(cps) 10000
This Command: dspvsipartinfo 11.1 2 10
Hit DEL key to quit:
dspvsipartinfo 4.1 1
Display VSI statistics for slot 4, port 1 for interface configured on partition ID 1.
sw237 TN StrataCom BPX 8620 9.2.L3 May 10 1999 14:58 PST
VSI Resources Status for trunk 4.1 Partition 1 Snapshot
Min Lcns :20 Min BW (cps) :2000
Max Lcns :30 Max BW (cps) :3000
Used Lcns : Used BW (cps) :
Available Lcns : Available BW(cps):
Last Command:dspvsipartinfo 4.1 1
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.
Display VSI logical connections
dspvsich <slot>
Display the VSI channels (or LCNs) on the specified slot.
cnfqbin
| Privilege | Jobs | Log | Node | Lock |
Service Level | No | No | BPX | No |
dspqbin 13.1
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).
dspvsich 4
Display VSI management channels (or LCNs) on slot 4.
sw237 TN StrataCom BPX 8620 9.2.a3 June 16 1999 05:10 PST
VSI lcns for Slot 4
lcn type dest_slot dest_lcn vpi vci
272 slave-end msvc 13 546 - -
16365 control-port msvc local - 1 23
16364 control-port msvc 3 16365 1 22
16374 control-port msvc 13 8173 1 32
16349 interslave 3 16350 - -
16359 interslave 13 8158 - -
Last Command: dspvsich 4
| Parameter | Description |
|---|---|
slot.port | Specifies the BXM card slot and port number. |
Qbin ID | Specifies the ID number of the Qbin available for use by the LSC (MPLS Controller) for VSI. The range is 0 to 255; 0 is the default. Always use 10 in 9.1. |
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:
Remaining columns (Channel Configuration) describe the channel configurations when appropriate.
Display Y-cable redundancy
dspyred [slot]
addyred, delyred, prtyred
| Privilege | Jobs | Log | Node | Lock |
1-4 | No | No | IGX, BPX | No |
dspyred
Display Y-redundancy for all cards.
beta TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 14:28 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
25 Pri 26 SDP RS232 DCE DCE DCE DCE
26 Sec 25 SDP RS232 DCE DCE DCE DCE
Last Command: dspyred
Next Command:
Posted: Fri Sep 29 13:43:51 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.