Network Router User Manual
Table Of Contents
- Rules for Adding a DAX Connection
- Rules for Adding Three-Segment Connections
- Rules for Adding Management Connections
- BPX 8600-to-BPX 8600 Segment
- Very High Speed Frame Service Modules
- Eight-Port Channelized and Unchannelized Frame Service Module
- Four-Port Unchannelized Frame Service Module for V.35
- MGX-FRSM-2CT3 Features
- MGX-FRSM-2T3E3 Features
- MGX-FRSM-HS2/B Features
- MGX-FRSM-HS1/B Features
- Eight-Port FRSM Features
- Congestion Indication for NIW Connections
- PVC Status Management
- Cell Loss Priority
- Congestion Indication
- Command and Response Mapping
- Translation and Transparent Modes
- Loss Priority Indication
- Congestion Indication
- Cell Delay Treatment
- Error and Alarm Response
- Configuring the Card, Lines, and Ports
- Adding and Modifying Connections
- Configuring the Card, Lines, and Ports
- Configuring Bulk Distribution and Redundancy
- Adding and Modifying Connections
- Configuring Redundancy Through the Redundancy Bus
- Configuring Redundancy Through the Distribution Bus
- Pattern Test Options
- Loopback Test Options
Card and Service Configuration 6-3
Rules for Adding Connections
Rules for Adding a DAX Connection
A DAX con is a connection whose endpoints for the entire connection exist on the same switch. The
following apply to the MGX 8850 switch:
1 On a feeder, a DAX con can exist between different service modules or the same service module.
2 A stand-alone node supports DAX cons with one or both endpoints on the PXM in addition to
DAX cons between service modules.
3 Either endpoint can be the master.
4 The first endpoint to add is the slave. The generic syntax is:
addcon <local parameters>
where local parameters are the port, DLCI or VPI and VCI, and mastership status. Slave is the
default case, so you actually do not explicitly have to specify it. When you press Return, the
system returns a connection identifier. The identifier includes the port and DLCI or VPI and VCI.
Use the identifier to specify the slave endpoint when you subsequently add the connection at the
master end. The slave endpoint is specified as the remote parameters in item 5.
5 To complete the DAX con, add the master endpoint. The generic syntax is
addcon <local parameters> <remote parameters>
where local parameters are the port, DLCI or VPI and VCI, and mastership status (master in this
case). The remote parameters are the items in the connection identifier that the system returned
when you added the slave endpoint.
6 If the endpoint is a PXM port in a stand-alone node, specify the slot as 0. The addcon command
is the only command in which you specify the slot number for the PXM as 0.
Rules for Adding Three-Segment Connections
A three-segment connection consists of a local segment on each MGX 8850 switch at the edges of
the network cloud and a middle segment across the network cloud. The MGX 8850 requirements are:
1 For MGX 8850 feeders, the backbone must consist of BPX 8600-series switches.
2 For MGX 8850 stand-alone switches, the backbone switches can be either BPX 8600-series
switches or switches from another manufacturer.
3 On a feeder, the local segment exists between a service module and the PXM.
4 On a stand-alone node, the local segment can be between a service module and a port on the PXM
or just two ports on the PXM.
5 For the local segment, add the connection at only the master endpoint. The generic syntax is:
addcon <local parameters> <remote parameters>
where local parameters are the port, DLCI or VPI and VCI, and mastership status (master in this
case). The remote parameters are the current nodename, slot, port, and VPI and VCI of the slave
end. For the PXM endpoints, specify the slot number as 0. The addcon command is the only
command in which you specify the slot number for the PXM as 0.