|
|
This chapter provides instructions for configuring the the Broadband Switch Module (BXM) card sets. It also describes resource partitioning for the BPX switch, including procedures for UNI port resource partitioning for the BXM. You will also find procedures for NNI or trunk resource partitioning for the BXM and BNI.
The chapter includes:
The BXM supports label switching. Partitions for the BXM can be allocated either between:
For information on Label Switching, refer to the Cisco MPLS Software Configuration Guide.
For details about the BXM card set, see Chapter 5, BXM Card Sets: T3/E3, 155, and 622.
The BXM cards supports dynamic resource partitioning to support the conversion of PVCs to soft permanent virtual circuits (SPVCs).
You will typically configure and provision connections by using Cisco WAN Manager. However,you can also add the connections by using the BPX switch command line interface (CLI). This may be appropriate during initial local node setup and when a Cisco WAN Manager workstation is not available. Afterwards, it is faster and easier to use the graphical interface.
Two connection addressing modes are supported:
The full ATM address range for VPI and VCI is supported.
To route connections between customer premise equipment and BXM ports:
a. The initial command to up a trunk (uptrk) or to up a line (upln) on the BXM card configures all the ports of the card to be either trunks or lines (UNI port access).
b. Afer using the uptrk command at each port, issue the addtrk command to activate a trunk for network access.
Step 2 Up the line by using the upln command
Step 3 Configure the line by using the cnfln command
Step 4 Configure the associated port by using the cnfport command
Step 5 Up the port by using the upport command
Step 6 Add the ATM connections by using the addcon command.
Parameters:
Connections can be either:
The VPI and VCI fields have significance only to the local BPX switch, and are translated by tables in the BPX switch to route the connection. Connections are automatically routed by the AutoRoute feature once the connection endpoints are specified.
Enter the following parameters for the BXM addcon command. Depending upon the connection type, you are prompted with appropriate parameters:
Syntax:
addcon local_addr node remote_addr traffic_type ...extended parameters
| Field | Value | Description |
|---|---|---|
local/remote_addr | slot.port.vpi.vci | card slot, port, and desired VCC or VPI connection identifier |
node |
| slave end of connection |
traffic_type |
| type of traffic, chosen from CBR, VBR, ABR, and UBR |
extended parameters |
| parameters associated with each connection type |
 |
Note You can configure the range of VPIs and VCIs reserved for PVC traffic and SVC traffic by using the cnfport command. While adding connections, the system checks the entered VPI/VPC against the range reserved for SVC traffic. If there is a conflict, the addcon command fails with the message "VPI/VCI on selected port is reserved at local/remote end". |
This section provides a preliminary summary of configuration, provisioning, and monitoring commands associated with the BXM cards. These commands apply to initial card configuration, line and trunk configuration and provisioning, and connection configuration and provisioning.
Connection Provisioning
Diagnostics
Test
Statistics
This section contains command examples, including configuring BXM lines and trunks and adding connections terminating on BXM cards.
An example of the uptrk command for trunk 1 on a BXM in slot 4 of a BPX switch:
pubsbpx1 TN silves BPX 8620 9.3 Aug. 2 2000 13:42 PDT
TRK Type Current Line Alarm Status Other End
1.1 T3 Clear - OK -
2.1 OC-3 Clear - OK VSI(VSI)
4.1 OC-3 Clear - OK -
Last Command: uptrk 4.1
256 PVCs allocated. Use 'cnfrsrc' to configure PVCs
Next Command:
|
Note The initial command to up a trunk (uptrk) or to up a line (upln) on the BXM card configures all the ports of the card to be either trunks or lines (UNI port access). After using the uptrk command at each port, use the addtrk command to activate a trunk for network access. |
An example of the cnftrk command for trunk 4.1 of a BXM card:
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 13:40 PDT
TRK 4.1 Config OC-3 [353207cps] BXM slot: 2
Transmit Rate: 353208 Line framing: STS-3C
Protocol By The Card: No coding: --
VC Shaping: No CRC: --
Hdr Type NNI: Yes recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: --
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR, T-VBR clock: No
SVC Vpi Min: 0 HCS Masking: Yes
SVC Channels: 0 Payload Scramble: Yes
SVC Bandwidth: 0 cps Frame Scramble: Yes
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
This Command: cnftrk 4.1
Transmit Rate [ 1-353208 ]:
An example of the addtrk command:
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 13:45 PDT
TRK Type Current Line Alarm Status Other End
1.1 T3 Clear - OK -
2.1 OC-3 Clear - OK VSI(VSI)
2.4 OC-3 Clear - OK -
Last Command: dsptrks
Next Command:
An example of the upln command for UNI port access on a BXM card:
pubsbpx1 TN StrataCom BPX 8620 9.3 March 2 2000 13:54 PDT
Line Type Current Line Alarm Status
2.2 OC-3 Clear - OK
2.3 OC-3 Clear - OK
Last Command: upln 2.2
256 PVCs allocated. Use 'cnfrsrc' to configure PVCs
Next Command:
|
Note The initial command to up a trunk (uptrk) or to up a line (upln) on the BXM card configures all the ports of the card to be either trunks or lines (UNI port access). After using the upln command at each port, use the upport command to activate a port for UNI access. |
An example of the cnfln command:
pubsbpx1 TN StrataCom BPX 8620 9.3 Aug. 2 2000 13:55 PDT
LN 2.2 Config OC-3 [353208cps] BXM slot: 2
Loop clock: No Idle code: 7F hex
Line framing: --
coding: --
CRC: --
recv impedance: --
E1 signalling: --
encoding: -- cable type: --
T1 signalling: -- length: --
HCS Masking: Yes
Payload Scramble: Yes
56KBS Bit Pos: -- Frame Scramble: Yes
pct fast modem: -- Cell Framing: STS-3C
VC Shaping: No
This Command: cnfln 2.2
Loop clock (N):
An example of the cnfport command for port 3 of a BXM card in slot 3:
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 13:56 PDT
Port: 2.2 [INACTIVE]
Interface: LM-BXM CAC Override: Enabled
Type: UNI %Util Use: Disabled
Shift: SHIFT ON HCF (Normal Operation)
SIG Queue Depth: 640 Port Load: 0 %
Protocol: NONE Protocol by Card: No
This Command: cnfport 2.2
NNI Cell Header Format? [N]:
An example of the cnfportq command:
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 13:57 PDT
Port: 2.2 [INACTIVE]
Interface: LM-BXM
Type: UNI
Speed: 353208 (cps)
SVC Queue Pool Size: 0
CBR Queue Depth: 600 rt-VBR Queue Depth: 5000
CBR Queue CLP High Threshold: 80% rt-VBR Queue CLP High Threshold: 80%
CBR Queue CLP Low Threshold: 60% rt-VBR Queue CLP Low/EPD Threshold: 60%
CBR Queue EFCI Threshold: 60% rt-VBR Queue EFCI Threshold: 60%
nrt-VBR Queue Depth: 5000 UBR/ABR Queue Depth: 20000
nrt-VBR Queue CLP High Threshold: 80% UBR/ABR Queue CLP High Threshold: 80%
nrt-VBR Queue CLP Low Threshold: 60% UBR/ABR Queue CLP Low/EPD Threshold:60%
nrt-VBR Queue EFCI Threshold: 60% UBR/ABR Queue EFCI Threshold: 20%
This Command: cnfportq 2.2
SVC Queue Pool Size [0]:
An example of the upport command:
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 13:58 PDT
Port: 2.2 [ACTIVE ]
Interface: LM-BXM CAC Override: Enabled
Type: UNI %Util Use: Disabled
Shift: SHIFT ON HCF (Normal Operation)
SIG Queue Depth: 640 Port Load: 0 %
Protocol: NONE Protocol by Card: No
Last Command: upport 2.2
Next Command:
An example of the cnfatmcls command for class 2:
pubsbpx1 TN StrataCom BPX 8620 9.3 March 2 2000 13:59 PDT
ATM Connection Classes
Class: 2 Type: nrt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
1000/1000 100/100 10000/10000 n 1000/1000
MBS Policing
1000/1000 3
Description: "Default nrt-VBR 1000 "
This Command: cnfatmcls 2
Enter class type (rt-VBR, nrt-VBR, CBR, UBR, ABRSTD, ABRFST, ATFR, ATFST, ATFT,
ATFTFST, ATFX, ATFXFST):
An example of the cnfcls command for class 3:
pubsbpx1 TN StrataCom BPX 8620 9.3 March 2 2000 14:02 PDT
ATM Connection Classes
Class: 3 Type: rt-VBR
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
4000/4000 100/100 10000/10000 n 4000/4000
MBS Policing
1000/1000 3
Description: "Default rt-VBR 4000 "
This Command: cnfatmcls 3
Enter class type (rt-VBR, nrt-VBR, CBR, UBR, ABRSTD, ABRFST, ATFR, ATFST, ATFT,
ATFTFST, ATFX, ATFXFST):
An example of the addcon command for a VBR connection 3.1.105.55 that originates at port 2 of a BXM card in slot 2:
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 14:05 PDT
Local Remote Remote Route
Channel NodeName Channel State Type Avoid COS O
2.2.16.16 pubsbpx1 2.3.66.66 Ok rt-vbr
2.3.66.66 pubsbpx1 2.2.16.16 Ok rt-vbr
Last Command: addcon 2.2.16.16 pubsbpx1 2.3.66.66 rt-VBR * * * * * * *
Next Command:
An example of the cnfcon command for a rt-VBR connection 2.2.16.16.
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 14:06 PDT
Conn: 2.2.16.16 pubsbpx1 2.3.66.66 rt-vbr Status:OK
PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR
50/50 100/100 250000/250000 n 50/50
MBS Policing
1000/1000 3
This Command: cnfcon 2.2.16.16
PCR(0+1) [50/50]:
An example of the addcon command for an ABR connection follows. In this case, the choice to accept the default parameters was not accepted, and individual parameters were configured for a connection using ABR standard VSVD flow control.
pubsbpx1 TN StrataCom BPX 8620 9.3 March 2 2000 14:12 PDT
From Remote Remote Route
2.2.17.17 NodeName Channel State Type Avoid COS O
2.3.66.66 pubsbpx1 2.2.16.16 Ok rt-vbr
This Command: addcon 2.2.17.17 pubsbpx1 2.3.67.67 abrstd 100/100 95/95 * * e e e
d 70/70 * 3 * * * 65/65 * * * * * * * *
Add these connections (y/n)? y
An example of the cnfcon command for an ABR connection:
pubsbpx1 TN silves BPX 8620 9.3 March 2 2000 14:14 PDT
Conn: 2.2.17.17 pubsbpx1 2.3.67.67 abrstd Status:OK
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC VSVD FCES
100/100 95/95 50/50 250000/250000 y y y
SCR MBS Policing VC Qdepth CLP Hi CLP Lo/EDP EFCI
70/70 1000/1000 3 16000/16000 80/80 35/35 65/65
ICR ADTF Trm RIF RDF Nrm FRTT TBE
50/50 1000 100 128 16 32 0 1048320
This Command: cnfcon 2.2.17.17
PCR(0+1) [100/100]:
An example of the cnfabrparm command:
pubsbpx1 TN YourID:1 BPX 15 9.3 March 8 2000 00:21 GMT
ABR Configuration for BXM in slot 3
Egress CI Control : N
ER Stamping : N
Weighted Queueing : N
Last Command: cnfabrparm 3
Next Command:
An example of the dsplns command:
pubsbpx1 TN YourID BPX 15 9.3 Jun. 8 2000 00:22 GMT
Line Type Current Line Alarm Status
3.1 OC-3 Clear - OK
3.2 OC-3 Clear - OK
3.3 OC-3 Clear - OK
3.4 OC-3 Clear - OK
5.1 T3 Clear - OK
5.2 T3 Clear - OK
Last Command: dsplns
Next Command:
During the configuration of BPX switch interfaces, you must make sure that the BPX switch IP address, SNMP parameters, and Network IP address are set consistent with your local area network (Ethernet LAN). Use the following BPX switch commands to set these parameters:
The use of these commands is explained in the Cisco WAN Switching Command Reference or the Cisco WAN Switch Superuser Command Reference. Super User commands should be used only by authorized personnel, and must be used carefully.
This section provides procedures for:
Resources on BPX switch UNI ports and NNI trunks can be divided between:
This is known as resource partitioning and is done through the Command Line Interface for the BPX switch and the MGX 8220.
These resources for BXM and BNI cards can be partitioned appropriately between SVCs or PVCs.
You can have both a PNNI controller and a Cisco 6400 controller, each in its own partition controlling the same VSI slave.
The BXM supports Multiprotocol Label Switching (MPLS). You can allocate partitions for the BXM either between:
For information on MPLS Switching, refer to Cisco MPLS Software Configuration Guide.
A BXM card used as a UNI port can be configured to support ATM SVCs. You will need to:
|
Note The initial command to up a trunk (uptrk) or to up a line (upln) on the BXM configures all the physical ports on a BXM card to be either trunks or ports. They can not be intermixed. |
Before partitioning SVC resources, you must determine which BXM UNI ports will support ATM SVCs. The BXM must have its resources partitioned to support SVCs.
These resources must be partitioned:
For additional information on using the BPX switch command line interface and applicable commands, refer to the Cisco WAN Switching Command Reference. These procedures will concentrate on those commands that are specific to SVC resource partitioning.
To partition the BXM port, follow these steps:
Step 2 Using the upln and upport commands, up the line and port which is going to be connected to ATM CPE.
Step 3 Make sure the port is configured as UNI.
Step 4 Enter the cnfport <port num> command, shown in the following example:
Example: BXM cnfport Command
ins-bpx6 TN SuperUser BPX 15 9.3 Sep. 24 2000 07:37 GMT
Port: 13.1 [ACTIVE ]
Interface: LM-BXM
Type: UNI %Util Use: Disabled
Speed: 353208 (cps)
Shift: SHIFT ON HCF (Normal Operation)
SIG Queue Depth: 640
Protocol: NONE
SVC Channels: 1000
SVC VPI Min: 0
SVC VPI Max: 10
SVC Bandwidth: 300000 (cps)
This Command: cnfport 13.1
NNI Cell Header Format? [N]:
Step 5 Configure the SVC Channels, SVC VPI Min, SVC VPI Max, and SVC Bandwidth as desired.
Step 6 Next you need to configure the SVC Port Queue depth with the cnfportq <portnum> command shown in the following example.
ins-bpx6 TN SuperUser BPX 15 9.3 Sep. 24 2000 07:39 GMT
Port: 13.1 [ACTIVE ]
Interface: LM-BXM
Type: UNI
Speed: 353208 (cps)
SVC Queue Pool Size: 5000
CBR Queue Depth: 600
CBR Queue CLP High Threshold: 80%
CBR Queue CLP Low Threshold: 60%
CBR Queue EFCI Threshold: 80%
VBR Queue Depth: 5000 UBR/ABR Queue Depth: 20000
VBR Queue CLP High Threshold: 80% UBR/ABR Queue CLP High Threshold: 80%
VBR Queue CLP Low Threshold: 60% UBR/ABR Queue CLP Low Threshold: 60%
VBR Queue EFCI Threshold: 80% UBR/ABR Queue EFCI Threshold: 30%
This Command: cnfportq 13.1
SVC Queue Pool Size [5000]:
Step 7 Configure the SVC Queue Pool Size parameter to a value greater than 0 (zero); the default is 0 and needs to be changed for SVCs to operate.
Step 8 Partition the SVC resources for every BXM which is to support ATM SVCs in the BPX switch.
Posted: Mon Jul 10 20:58:18 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.