|
|
This chapter describes the BXM card sets which include the BXM T3/E3, BXM-155, and BXM-622. card sets. The BXM cards may be configured for either trunk or service (port UNI) mode. In trunk mode they provide BPX network interfaces, and in service (port UNI) mode they provide service access to CPE.
The chapter includes the following:
A BXM card set, using Application Specific Integrated Circuit (ASIC) technology, provides high speed ATM connectivity, flexibility, and scalability. The card set is comprised of a front card that provides the processing, management, and switching of ATM traffic and of a back card that provides the physical interface for the card set. An example of a BPX network provisioned with BXM-622 cards is shown in Figure 6-1.
The BXM card group includes the BXM-T3/E3, BXM-155, and BXM-622. These cards may be configured to support either trunk (network) or port (service access) interfaces. The BXM T3/E3 is available in 8 or 12 port versions with T3/E3 interfaces. The BXM-155 is available in 4 or 8 port versions with OC3/STM-1 interfaces. The BXM-622 is available in 1 or 2 port versions with OC-12/STM-4 interfaces. The BXM card sets are compliant with ATM UNI 3.1 and Traffic Management 4.0 including ABR VS/VD and provide the capacity to meet the needs of emerging bandwidth driven applications.
For additional information on ATM Connections, refer to Chapter 7, ATM Connections, of this document or to the System Overview document.
The BXM cards are designed to support all the following service classes: Constant Bit Rate (CBR), Variable Bit Rate (VBR), Available Bit Rate (ABR with VS/VD, ABR without VS/VD, and ABR using Foresight), and Unspecified Bit Rate (UBR). ABR with VS/VD supports explicit rate marking and Congestion Indication (CI) control.
All software and administration firmware for the BXM card is downloadable from the BCC and is operated by the BXM on-board sub-system processor.
A BXM card set consists of a front and back card. The BXM T3/E3 is available with a universal BPX-T3/E3 backcard in 8 or 12 port versions. The BXM-OC3 is available with 4 or 8 port multi-mode fiber (MMF), single mode fiber (SMF), or single mode fiber long reach (SMFLR) back cards. The BXM-OC12 is available with 1 or 2 port SMF or SMFLR back cards,
Any of the 12 general purpose slots can be used for the BXM cards. The same backcards are used whether the BXM ports are configured as trunks or lines. Table 6-1 and Table 6-2 list the available front and back card options for the BXM-T3/E3, BXM-155, and BXM-622.
| Front Card Model Number | No. of Ports | Cell Buffer (ingress/egress) | Connections per card | Back Cards |
|---|---|---|---|---|
T3/E3 (45 Mbps/34Mbps) | ||||
BXM-T3-8 | 8 | 100k/100k | 16k/32k | BPX-T3/E3-BC |
BXM-E3-8 | 8 | 100k/100k | 16k/32k | BPX-T3/E3-BC |
BXM-T3-12 | 12 | 100k/230k | 16k/32k | BPX-T3/E3-BC |
BXM-E3-12 | 12 | 100k/230k | 16k/32k | BPX-T3/E3-BC |
OC3/STM-1 (155.52 Mbps) | ||||
BXM-155-8 | 8 | 230k/230k | 16k | MMF-155-8 SMF-155-8 SMFLR-155-8 |
BXM-155-4 | 4 | 100k/230k | 16K | MMF-155-4 SMF-155-4 SMFLR-155-4 |
OC12/STM-4 (622.08 Mbps) | ||||
BXM-622-2 | 2 | 230k/230k | 16K | SMF-622-2 SMFLR-622-2 SMFXLR-622-2 |
BXM-622 | 1 | 130k/230k | 16K/32K | SMF-622 SMFLR-622 SMFXLR-622 |
*The BXM cards can be configured for either, but not both, trunk or service access (UNI) on a card by card basis. Once a card is so configured, all ports are either trunk or service interfaces until the card is reconfigured.
**The BPX-T3/E3-BC universal backcard supports 8 or 12 ports.
| Back Card Model Number | No. of Ports | Description | Optical Range (less than or equal to) |
|---|---|---|---|
T3/E3 (45 Mbps/34Mbps) | |||
BPX-T3/E3-BC | 8/12 | Universal T3/E3 backcard for 8 or 12 port card configurations | n/a |
OC3/STM-1 (155.520 Mbps) | |||
MMF-155-8 | 8 | Multi-Mode Fiber | 2km |
MMF-155-4 | 4 | Multi-Mode Fiber | 2km |
SMF-155-8 | 8 | Single-Mode Fiber | 20km |
SMF-155-4 | 4 | Single-Mode Fiber | 20km |
SMFLR-155-8 | 8 | Single-Mode Fiber Long Reach | 40km |
SMFLR-155-4 | 4 | Single-Mode Fiber Long Reach | 40km |
OC12/STM-4 (622.08 Mbps) | |||
SMF-622-2 | 2 | Single-Mode Fiber | 20km |
SMF-622 | 1 | Single-Mode Fiber | 20km |
SMFLR-622-2 | 2 | Single-Mode Fiber Long Range | 40km |
SMFLR-622 | 1 | Single-Mode Fiber Long Range | 40km |
The following lists some of the major capabilities of the BXM cards:
The BXM cards support the full range of ATM service types per ATM Forum TM 4.0.
CBR Service:
VBR Service:
ABR Service:
UBR Service:
Virtual Interfaces
The BXM front panel has a three-section, multi-colored "card" LED to indicate the card status. A two-port BXM-622, an 8-port BXM-155 front card, and a 12-port BXM-T3/E3 are shown in figures Figure 6-2, Figure 6-3, and Figure 6-4, respectively. The card status LED is color-coded as indicated in Table 6-3. A three-section multi-colored "port" LED indicates the status of the ports. Types of failures are indicated by various combinations of the card status indicators as indicated in Table 6-4.
| Status | LED color | Status Description |
|---|---|---|
port | off | Trunk/line is inactive and not carrying data. |
| green | Trunk/line is actively carrying data. |
| yellow | Trunk/line is in remote alarm. |
| red | Trunk/line is in local alarm. |
card | green (act) | Card is on-line and one or more trunks/lines on the card have been upped. If off, card may be operational but is not carrying traffic. |
| yellow (stby) | Card is off-line and in standby mode (for redundant card pairs). May not have any upped trunks/lines. If blinking, indicates card firmware or configuration data is being updated. |
| red (fail) | Card failure; card has failed self-test and/or is in a reset mode. See Table 6-4 for more information. |
| act | stby | fail | Failure Description |
|---|---|---|---|
on | off | on | Non-fatal error detected; card is still active. |
off | on | on | Non-fatal error detected; card is in standby mode. |
off | blinking | on | Fatal error detected; card is in a reboot mode. |
on | on | on | Card failed boot load and operation is halted. |
The BXM backcards connect to the BXM front cards through the StrataBus midplane.
The BXM-622 is available in one or two port versions in either a single-mode fiber intermediate range (SMF) or a single-mode fiber long range (SMFLR) backcard. Connector information is listed in Table 6-5 and a 2-port SMF card is shown in Figure 6-5.
| No. | Connector | Function |
|---|---|---|
1 or 2 | PORT | Two FC connectors per port, one each for the transmit and receive signal |
The BXM-155 is available in four or eight port versions in a choice of multi-mode fiber (MMF), single-mode fiber intermediate range (SMF), or single-mode fiber long range (SMFLR) backcards. Connector information is listed in Table 6-6 and an 8-port SMF card is shown in Figure 6-6.
| No. | Connector | Function |
|---|---|---|
4 or 8 | PORT | One SC connector per port, accommodates both the transmit and receive signals. |
The BXM-T3/E3 is available in 8 or twelve port versions. Connector information is listed in Table 6-7 and a 12-port T3/E3 card is shown in Figure 6-7.
| No. | Connector | Function |
|---|---|---|
8 or 12 | PORT | Two SMB connectors per port, one each for the transmit and receive signals. |
The SMF-622 series backcards may be Y-cabled for redundancy using the Y-Cable splitter shown in Figure 6-8. The cards must be configured for Y-Cable redundancy using the addyred command.
This functional description provides an overview of BXM operation.
The following provides an overview of the operation of the BXM card when the ports are configured in port (access) mode for connection to customer equipment (CPE).
The ingress flow of ATM cells into the BXM when the card is configured for port (access) operation is shown in Figure 6-9.
ATM cells from the CPE are processed at the physical interface level by the SUNI (OC3/OC12) or Mux/Demux (T3/E3), policed per individual VC by the RCMP and routed to applicable ingress queues. In addition, for ABR cells, additional functions are performed by the SABRE ABR connection controller, including: VS/VD, Foresight, and virtual connection queueing. The cells are served out via the BPX Backplane to the BPX crosspoint switch in an order of priority based on their connection type.
The egress flow of ATM cells out of the BXM when the card is configured for port (access) operation is shown in Figure 6-10.
ATM cells are routed to the BXM-622 via the BPX Backplane/Stratabus from the BPX crosspoint switch, applied to the DRSIU, then to an egress queue per class of service, and then served out to the SUNI (OC3/OC12) or Mux/Demux (T3/E3) which processes the ATM cells into frames, processing the cells from the ATM layer to the physical and on out to the CPE connected to the port(s) on the BXM backcard. In addition, for ABR cells, additional functions are performed by the SABRE ABR connection controller, including: VS/VD, Foresight, and virtual connection queueing.
This following provides an overview of the operation of the BXM when the card is configured in the trunk mode for connection to another node or network.
The ingress flow of ATM cells into the BXM when the card is configured for trunk operation is shown in Figure 6-11.
ATM cells from a node or network are processed at the physical interface level by the SUNI (OC3/OC12) or Demux/Mux (T3/E3), routed to applicable ingress slot queues, and served out to the BPX crosspoint switch via the BPX Backplane.
The egress flow of ATM cells out of the BXM when the card is configured for trunk operation is shown in Figure 6-12.
ATM cells are routed to the BXM from the BPX crosspoint switch, applied to the DRSIU, then to an egress queue per class of service, and then served out to the SUNI (OC3/OC12) or Demux/Mux (T3/E3). The SUNI or Demux/Mux, as applicable, processes the ATM cells into frames, processing the cells from the ATM layer to the physical and on out to the backcard trunk interface connecting to another node or network.
The following provides a summary of the principal functions performed by the major functional circuits of the BXM.
The DRSIU provides a total egress capacity from the BPX switch fabric of 1.6 Gbps.
The SUNI ASIC implements the BXM physical processing for OC3 and OC12 interfaces. The SUNI provides SONET/SDH header processing, framing, ATM layer mapping and processing functions for OC12/STM-4 (622.08 Mbps) or OC3/STM1 (155.52 Mbps)
For ingress traffic, the BXM physical interface receives incoming SONET/SDH frames, extracts ATM cell payloads, and processes section, line, and path overhead. For egress traffic ATM cells are processed into SONET/SDH frames.
Alarms and statistics are collected at each level: section, line and path.
The Demux/Mux and associated circuits implement the BXM physical layer processing for T3/E3 interfaces, providing header processing, framing, ATM layer mapping, and processing functions for T3 at a 44.736 Mbps rate, or E3 at a 34.368 rate.
Usage Parameter Control (UPC) is provided by the RCMP. Each arriving ATM cell header is processed and identified on a per VC basis. The policing function utilizes a leaky bucket algorithm.
In addition to UPC and traffic policing, the RCMP provides route monitoring and also terminates OAM flows to provide performance monitoring on an end-to-end per VC/VP basis.
Traffic policing and UPC functionality is in accordance with the GCRA as specified by ATM Forum's UNI 3.1 using dual leaky buckets.
In addition, two selective cell discard thresholds are supported for all queues for discard of CLP=1 cells should congestion occur.
The Scheduling and ABR Engine (SABRE) includes both VS/VD and Foresight dynamic traffic transfer rate control and other functions:
The overall function of the queue engines is to manage the bandwidth of trunks or ports (UNI) via management of the ingress and egress queues.
In addition to the ABR VS queues, the ingress queues include 15 slot servers, one for each of 14 possible BPX destination slots, plus 1 for multicast operation. Each of the 15 slot servers contains 16 Qbins, supporting 16 classes of service per slot server.
In addition to the ABR VS queues, the egress queues include 32 Virtual Interfaces (VIs). Each of the 32 VIs supports 16 Qbins.
This serial interface and multicast buffer ASIC provides the following:
The ACP performs the following localized functions:
All basic configuration data on the card is copied to the battery backup memory (BRAM) on the card so that in the event of a power outage, the card will retain its main configuration.
Compliant to Bellcore GR-253-CORE
Alarms:
Performance Monitoring:
Statistics:
OAM
Compliant to Bellcore GR-253-CORE
Alarms:
Performance Monitoring:
Statistics:
Process Monitoring for ATM Header Cell Processing
Miscellaneous ATM Layer Statistics
| Back card | Source 1310 nm | Tx Power (dBm) Min Max | Rx Power (dBm) Min Max | Connection Type | Range (km) | ||
|---|---|---|---|---|---|---|---|
SMF (IR) | Laser | -15 | -8 | -28 | -8 | FC | 20 |
SMF (LR) | Laser | -3 | +2 | -28 | -8 | FC | 40 |
SMF (XLR) | Laser |
|
|
|
|
|
|
| Back card | Source | Tx Power (dBm) Min Max | Rx Power (dBm) Min Max | Connection Type | Range (km) | ||
|---|---|---|---|---|---|---|---|
MMF | LED | -22 | -15 | -343 | -10 | SC | 2 |
SMF (IR) | Laser 1310 nm | -15 | -8 | -34 | -10 | FC | 20 |
SMF (LR) | Laser 1310 nm | -5 | 0 | -34 | -10 | FC | 40 |
SONET is defined across three elements, section, line, and path as shown in Figure 6-13 and described in Table 6-10. An advantage of this tiered approach is that management control can be exercised at each level, for example at the section level independent of the line or path level
| Unit | Description |
|---|---|
Section | A section is the fiber optic cable between two active elements such as simple repeaters. The active element terminating these sections is called Section Terminating Equipment (STE). |
Line | A line is a physical element that contains multiple sections and repeaters and is terminated by line terminating equipment (LTE) at each end. |
Path | A path includes sections and lines and terminates at the customer premises equipment (CPE) |
Table 6-11 provides a cross-reference between OC-n optical carrier levels and the equivalent STS-n and SDH-n levels. It also includes the associated line rates.
| OC-n Optical Carrier | STS-n Synchronized Transport Signal | Line Rates (Mbps) | SDH-n Synchronized Digital Hierarchy | STM-n
Synchronous Transport Module |
|---|---|---|---|---|
OC-1 | STS-1 | 51.84 |
|
|
OC-3 | STS-3 | 155.52 | SDH-1 | STM-1 |
OC-12 | STS-12 | 622.08 | SDH-4 | STM-4 |
OC-48 | STS-48 | 2488.32 | SDH-16 | STM-12 |
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.
New or modified commands include but are not limited to:
Connections are typically provisioned and configured using StrataView Plus. Howver, the connections can also be added using the BPX command line interface (CLI). This may be appropriate during initial local node setup and when a Strata View Plus workstation is not available.
There are two connection addressing modes supported. The user may enter a unique VPI/VCI address in which case the BPX functions as a virtual circuit switch. Or the user may enter only a VPI address in which case all circuits are switched to the same destination port and the BPX functions as a virtual path switch in this case. The full ATM address range for VPI and VCI is supported.
Connections are routed between CPE connected to BXM ports. Before adding connections, the BXM is configured for port mode.
A line is upped with the upln command and configured with the cnfln command. Then the associated port is configured with the cnfport command and upped with the upport command. Following this, the ATM connections are added via the addcon command.
The slot number is the BXM card slot on the BPX. The port number is one of two ports on the BXM, the VPI is the virtual path identifier, and the VCI is the virtual circuit identifier.
The VPI and VCI fields have significance only to the local BPX, and are translated by tables in the BPX to route the connection. Connections are automatically routed by the AutoRoute feature once the connection endpoints are specified.
Connections can be either Virtual Path Connections (VPC) or Virtual Circuit Connections (VCC). Virtual Path Connections are identified by an * in the VCI field. Virtual Circuit Connections specify both the VPI and VCI fields.
Refer to Chapter 7 of this document and to the System Overview document for further information on ATM connections.
The following parameters are entered for the BXM addcon command. Depending upon the connection type, the user is prompted with appropriate parameters as shown below.
Syntax:
addcon local_addr node remote_addr traffic_type ...extended parameters
| Field | Value | Description |
|---|---|---|
|
|
|
local/remote_addr | slot.port.vpi.vci | 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 |
The following pages have a number of 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 follows:
pubsbpx1 TN StrataCom BPX 15 8.5 Jan. 23 1997 18:52 GMT
TRK Type Current Line Alarm Status Other End
1.1 T3 Clear - OK pubsaxi1(AXIS)
1.3 T3 Clear - OK pubsipx1/8
4.1 OC3 Clear - OK -
Last Command: uptrk 4.1
Next Command:
An example of the cnftrk command for trunk 4.1 of a BXM card follows:
pubsbpx1 TN StrataCom BPX 15 8.5 Jan. 23 1997 18:50 GMT
TRK 4.1 Config OC3 [353207cps] BXM slot: 4
Transmit Rate: 353208 Restrict CC traffic: No
Subrate interface: -- Link type: Terrestrial
Subrate data rate: -- Line framing: STS-3C
Line DS-0 map: -- coding: --
Pass sync: Yes CRC: --
Loop clock: No recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: --
Max Channels/Port: 256 HCS Masking: Yes
Connection Channels: 256 Payload Scramble: Yes
Valid Traffic Classes: Frame Scramble: Yes
V,TS,NTS,FR,FST,CBR,VBR,ABR Virtual Trunk Type: --
SVC Channels: -- Virtual Trunk VPI: --
SVC Bandwidth: -- cps Deroute delay time: 0
This Command: cnftrk 4.1
Transmit Rate [T2=14490, E3=80000, T3=96000, OC3 = 353208, OC12=1412830](353208)
An example of the addtrk command follows:
pubsbpx1 TN StrataCom BPX 15 8.5 Jan. 23 1997 18:54 GMT
TRK Type Current Line Alarm Status Other End
1.1 T3 Clear - OK pubsaxi1(AXIS)
1.3 T3 Clear - OK pubsipx1/8
4.1 OC3 Clear - OK -
Last Command: dsptrks
Next Command: addtrk 4.1
An example of the upln command for UNI port access on a BXM card follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:18 GMT
Line Type Current Line Alarm Status
3.1 OC3 Clear - OK
3.2 OC3 Clear - OK
3.3 OC3 Clear - OK
5.1 T3 Clear - OK
5.2 T3 Clear - OK
Last Command: upln 3.3
Next Command:
An example of the cnfln command follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:24 GMT
LN 3.3 Config OC3 [353208cps] BXM slot: 3
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
This Command: cnfln 3.3
Loop clock (N):
An example of the cnfport command for port 3 of a BXM card in slot 3 follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:25 GMT
Port: 3.3 [INACTIVE]
Interface: LM-BXM
Type: UNI %Util Use: Disabled
Speed: 353208 (cps)
Shift: SHIFT ON HCF (Normal Operation)
VBR Queue Depth: 5000
Protocol: NONE
SVC Channels: 0
SVC VPI Min: 0
SVC VPI Max: 0
SVC Bandwidth: 0 (c/s)
This Command: cnfport 3.3
NNI Cell Header Format? [N]:
An example of the cnfportq command follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:27 GMT
Port: 3.3 [INACTIVE]
Interface: LM-BXM
Type: UNI
Speed: 353208 (cps)
SVC Queue Pool Size: 0
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 ABR Queue Depth: 20000
VBR Queue CLP High Threshold: 80% ABR Queue CLP High Threshold: 80%
VBR Queue CLP Low Threshold: 60% ABR Queue CLP Low Threshold: 60%
VBR Queue EFCI Threshold: 80% ABR Queue EFCI Threshold: 80%
This Command: cnfportq 3.3
SVC Queue Pool Size [0]:
An example of the upport command follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:28 GMT
Port: 3.3 [ACTIVE ]
Interface: LM-BXM
Type: UNI %Util Use: Disabled
Speed: 353208 (cps)
Shift: SHIFT ON HCF (Normal Operation)
VBR Queue Depth: 5000
Protocol: NONE
SVC Channels: 0
SVC VPI Min: 0
SVC VPI Max: 0
SVC Bandwidth: 0 (c/s)
Last Command: upport 3.3
Next Command:
An example of the cnfcls command for class 1 follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:31 GMT
ATM Connection Classes
Class: 1 Type: ABR
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC FST VSVD
96000/96000 100/100 96000/96000 10000/10000 n n n
Description: "Default ABR 96000"
This Command: cnfcls 1
Enter class type (VBR, CBR, UBR, ABR, ATFR):
An example of the cnfcls command for class 2 follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:33 GMT
ATM Connection Classes
Class: 2 Type: 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 VBR 1000 "
This Command: cnfcls 2
Enter class type (VBR, CBR, UBR, ABR, ATFR):
An example of the addcon command for a VBR connection 3.1.105.55 that originates at port 1 of a BXM card in slot 3 follows:
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:39 GMT
From Remote Remote Route
3.1.105.55 NodeName Channel State Type Avoid COS O
3.1.105.55 pubsbpx1 3.2.205.65 Ok vbr
3.2.201.61 pubsbpx1 3.1.101.51 Ok abr
3.2.201.62 pubsbpx1 3.1.101.52 Ok abr
3.2.203.63 pubsbpx1 3.1.103.53 Ok abr
3.2.204.64 pubsbpx1 3.1.104.54 Ok abr
3.2.205.65 pubsbpx1 3.1.105.55 Ok vbr
5.1.30.120 pubsbpx1 5.2.60.240 Ok abr
5.1.31.121 pubsbpx1 5.2.61.241 Ok abr
5.1.32.122 pubsbpx1 5.2.62.242 Ok abr
5.1.33.123 pubsbpx1 5.2.63.242 Ok abr
5.2.60.240 pubsbpx1 5.1.30.120 Ok abr
5.2.61.241 pubsbpx1 5.1.31.121 Ok abr
5.2.62.242 pubsbpx1 5.1.32.122 Ok abr
Last Command: addcon 3.1.105.55 pubsbpx1 3.2.205.65 v * * * * * * *
Next Command:
An example of the cnfcon command for a VBR connection 3.1.105.55 follows.
pubsbpx1 TN YourID:1 BPX 15 8.5 Jan. 23 1997 02:41 GMT
Conn: 3.1.105.55 pubsbpx1 3.2.205.65 vbr
Description:
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 3.1.105.55
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 YourID BPX 15 8.5 Jan. 21 1997 01:10 GMT
From Remote Remote Route
3.1.104.54 NodeName Channel State Type Avoid COS O
3.1.104.54 pubsbpx1 3.2.204.64 Ok abr
3.2.201.61 pubsbpx1 3.1.101.51 Ok abr
3.2.201.62 pubsbpx1 3.1.101.52 Ok abr
3.2.203.63 pubsbpx1 3.1.103.53 Ok abr
3.2.204.64 pubsbpx1 3.1.104.54 Ok abr
5.1.30.120 pubsbpx1 5.2.60.240 Ok abr
5.1.31.121 pubsbpx1 5.2.61.241 Ok abr
5.1.32.122 pubsbpx1 5.2.62.242 Ok abr
5.1.33.123 pubsbpx1 5.2.63.242 Ok abr
5.2.60.240 pubsbpx1 5.1.30.120 Ok abr
5.2.61.241 pubsbpx1 5.1.31.121 Ok abr
5.2.62.242 pubsbpx1 5.1.32.122 Ok abr
5.2.63.242 pubsbpx1 5.1.33.123 Ok abr
This Command: addcon 3.1.104.54 pubsbpx1 3.2.204.64 abr 100/100 95/95 50/50 * e
d e d d 70/70 * 3 * 80/80 60/60 30/30 65/65 * 100 16 16 32 10 *
Add these connections (y/n)? y
An example of the cnfcon command for an ABR connection follows:
pubsbpx1 TN YourID BPX 15 8.5 Jan. 21 1997 01:10 GMT
Conn: 3.1.104.54 pubsbpx1 3.2.204.64 abr
Description:
PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC FST VSVD
100/100 95/95 50/50 250000/250000 y n y
FCES SCR MBS Policing VC Qdepth CLP Hi CLP Lo EFCI
n 70/70 1000/1000 3 16000/16000 80/80 60/60 30/30
ICR ADTF Trm RIF RDF Nrm FRTT TBE
65/65 1000 100 16 16 32 10 1048320
This Command: cnfcon 3.1.104.54
PCR(0+1) [100/100]:
An example of the cnfabrparm command follows:
pubsbpx1 TN YourID BPX 15 8.5 Feb. 8 1997 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 follows:
pubsbpx1 TN YourID BPX 15 8.5 Feb. 8 1997 00:22 GMT
Line Type Current Line Alarm Status
3.1 OC3 Clear - OK
3.2 OC3 Clear - OK
3.3 OC3 Clear - OK
3.4 OC3 Clear - OK
5.1 T3 Clear - OK
5.2 T3 Clear - OK
Last Command: dsplns
Next Command:
During the configuration of BPX Service Node interfaces, you must make sure that the BPX IP address, SNMP parameters, and Network IP address are set consistent with your local area network (Ethernet LAN). Use the following BPX commands to set these parameters:
The use of these commands is covered in the Cisco StrataCom Command Reference or the Cisco StrataCom Super User Command Reference. Super User commands must only be used by authorized personnel, and must be used carefully.
AXIS installation and configuration are covered in the Cisco StrataCom AXIS Reference. During the configuration of BPX Service Node interfaces, you must make sure that the AXIS IP address is set up consistent with your local area network (Ethernet LAN). Use the following AXIS command to set the proper IP addresses:
cnfifip "-ip <ip address> -if <interface type> -msk <subnet mask address> -bc <broadcast address>"
The use of this command is covered in the Cisco StrataCom AXIS Command Reference
Resources on BPX Service Node UNI ports and NNI trunks have to divided between SVCs and PVCs. This is known as resource partitioning and is done through the Command Line Interface for the BPX and the AXIS.
This section provides procedures for:
A BPX ATM Service Interface (ASI) card which will support ATM SVCs will have to be added and upped like a standard PVC port. Before adding connections, an ASI line is upped with the upln command and configured with the cnfport command and upped with the upport command. Complete details on using the BPX command line interface and applicable commands are described in the Cisco StrataCom BPX Reference and Command Reference manuals. In addition, the Cisco StrataCom System Overview provides conceptual information about ATM connections. These procedures will concentrate on those commands that are specific to SVC resource partitioning.
Before partitioning SVC resources, you must have determined which ASI will support ATM SVCs. The ASI will have to have its resources partitioned to support SVCs. The following resources must be partitioned for each ASI UNI port:
To partition the ASI UNI port, follow these steps:
Step 2 Using the upln and upport commands, up the line and port which are 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, as illustrated in Figure 6-14:
Step 5 Configure the desired SVC Channels, SVC VPI Min, SVC VPI Max, and SVC Bandwidth as desired.
Step 6 Next configure the SVC Port Queue depth with the cnfportq <port num> command. shown in Figure 6-15.
Step 7 Configure the SVC Queue Pool Size with this menu. Other parameters are for PVCs.
Step 8 Repeat SVC resource partitioning for every ASI port that you want to support SVCs in the BPX Service Node.
A BXM card used as a UNI port can be configured to support ATM SVCs. The BXM will have to be added and upped like a standard PVC port. The BXM port will have to upped as a line (upln) to function as a UNI port.
For additional information on using the BPX command line interface and applicable commands, refer to the Cisco StrataCom Command Reference manual. In addition, the Cisco StrataCom System Overview provides conceptual information about ATM connections and services. These procedures will concentrate on those commands that are specific to SVC resource partitioning.
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. The following resources must be partitioned:
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 Figure 6-16:
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 Figure 6-17.
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 Service Node.
The BPX has two types of trunk cards which may have their resources partitioned to support SVCs.
When the BNI is used as a trunk in a BPX Service Node network, it will have to have its resources partitioned to support SVCs. The BNI is described in the Cisco StrataCom BPX Reference. Complete details on using the BPX command line interface and applicable commands are described in the Cisco StrataCom BPX Reference and Command Reference manuals. In addition, the Cisco StrataCom System Overview provides conceptual information about ATM connections and services. These procedures will concentrate on those commands that are specific to SVC resource partitioning.
The following BNI trunk resources must be partitioned for SVCs:
To partition the BNI trunk resources, follow these steps:
Step 2 Up the trunk with uptrk <trunk_num> command.
Step 3 Enter the cnftrk <trk num> command as shown in Figure 6-18:
Step 4 Configure the SVC Channels and SVC Bandwidth as desired.
Step 5 Next configure the SVC Queue depth with cnftrkparms <trunk_num> command shown in Figure 6-19:
Step 6 Configure the SVC Queue Pool Size as desired.
Step 7 Partition the SVC resources for all the other BNIs in your BPX Service Node. This includes the BNI that is used to connect an AXIS shelf to a BPX when they are to be used for SVC connections.
When the BXM is used as a trunk in a BPX Service Node network, it needs to have its resources partitioned to support SVCs. The BXM card will have to upped as a trunk (uptrk).
For additional information on using the BPX command line interface and applicable commands refer to the Cisco StrataCom Command Reference manual. In addition, the Cisco StrataCom System Overview provides conceptual information about ATM connections and services. These procedures concentrate on those commands that are specific to SVC resource partitioning.
The following BXM trunk resources must be partitioned for SVCs:
To partition the BXM trunk resources for SVCs, follow these steps:
Step 2 Make sure the BXM has been upped as a trunk with uptrk <trunk_num> command.
Step 3 Enter the cnftrk <trk num> command, shown in Figure 6-20:
Step 4 Configure the SVC Channels and SVC Bandwidth as desired.
Step 5 Next configure the SVC Queue depth with cnftrkparms <trunk_num> command shown in Figure 6-21:
Step 6 Configure the SVC Queue Pool Size as desired.
Step 7 Partition the SVC resources for all the other BXMs in the BPX Service Node.
Posted: Wed Jan 17 21:30:21 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.