Provisioning Multilink PPP Services

Provisioning Multilink PPP Services on MPSM-T3E3-155 and MPSM-16-T1E1

Multilink PPP (MLPPP) combines multiple T1/E1 lines or paths into single logical interface, called an MLPPP bundle. Multilink bundles can bridge the gap between DS1 and DS3 bandwidths in small increments, and increase resiliency because the failure of a single link does not necessarily bring down the bundle. Each link is a T1/E1 line or path, which you can fractionalize down to N * DS0.

MLPPP bundles can also utilize PPP Multiplexing (PPPMUX). PPPMUX improves bandwidth utilization by combining small-sized packets into larger frames for transmitting over a the T1/E1 link. This is especially important in the IP-RAN solution because of the small packet sizes encountered.

This chapter describes how to provision Multilink PPP (MLPPP) services on the MPSM-16-T1E1 and MPSM-T3E3-155 cards in the following sections:

• MLPPP Command Summary

• MLPPP Quickstart Provisioning

• MLPPP Provisioning Procedures

• MLPPP PVC Connections

Note Before you perform the procedures in this section, you must set up the MPSM-16-T1E1 cards and lines from the PXM controller as described in Chapter 2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication." Make sure that you select the appropriate card SCT for the controller that you are using.

MLPPP Command Summary

Table 5-1 lists and describes the MLPPP commands.

Table 5-1 MLPPP Commands and Descriptions
Command	Description
addmpbundle	Adds the MLPPP bundle
addppplink	Adds the PPP link to an MLPPP bundle
addpppmux	Enables a PPP multiplexer (MUX) on an MLPPP bundle
clrmpbundlecnt	Clears all the counts associated with an MLPPP bundle
clrppplnkcnt	Clears the PPP link count
clrpppmuxcnt	Clears PPP MUX count
cnfmpbundle	Modifies the configuration of the MLPPP bundle
cnfmpbundleparams	Configures the parameters associated with an MLPPP bundle
cnfppplink	Configures the PPP Link in an MLPPP bundle
cnfpppmux	Configures a PPP MUX on an MLPPP bundle
delmpbundle	Deletes the MLPPP bundle
delppplnk	Deletes a specific link belonging to a specific bundle
delpppmux	Deletes a PPP MUX from an MLPPP bundle
dnmpbundle	Puts the MLPPP bundle in administratively DOWN state
dnppplink	Puts the PPP link in administratively DOWN state
dspmpbundle	Displays the configuration of an MLPPP bundle
dspmpbundlecnt	Displays the counts associated with an MLPPP bundles
dspmpbundleload	Displays the operational load for an MLPPP bundle
dspmpbundleparams	Displays the parameters associated with an MLPPP bundle
dspmpbundles	Displays all of the MLPPP bundles provisioned on the card
dspppplink	Displays the configuration of an PPP link
dspppplinks	Displays all of the PPP links provisioned on the bundle
dspppplnkcnt	Displays the PPP link count
dsppppmux	Displays PPP MUX information associated with a bundle
dsppppmuxcnt	Displays PPP MUX count information
dsptotals	Display the line, path, group, bundle, link, port and connection totals for the current card.
dspwinpathload	Displays the operational loads for WinPath packet processing engines.
dspwpbundles¹	Displays the assignment of MLPPP bundles to WinPath packet processing engines.
upmpbundle	Puts the MLPPP bundle in administratively UP state
upppplink	Puts the PPP link in administratively DOWN state

¹MPSM-T3E3-155 only

MLPPP Quickstart Provisioning

This section provides quick reference for those who have previously configured MLPPP bundles and connections. MLPPP provisioning consists of two tasks:

• MLPPP Bundle Configuration Quickstart

• PVC Configuration Quickstart

MLPPP Bundle Configuration Quickstart

To provision an MLPPP bundle, perform the following steps:


	Command	Comments
Step 1	addmpbundle Related commands: dspmpbundle cnfmpbundle delmpbundle	Create an MLPPP bundle. See Adding an MLPPP Bundle. The MPSM automatically creates a switch-side link to the backplane for the new bundle.
Step 2	cnfmpbundleparams Related command: dspmpbundleparams	Configure MLPPP bundle parameters. See Adding Links to an MLPPP Bundle.
Step 3	addppplink Related commands: dspppplink cnfppplink delppplink	Add MLPPP links to the bundle. See Adding Links to an MLPPP Bundle. Note Before you can add links to a bundle, the links must be up.
Step 4	addpppmux Related commands: dsppppmux cnfpppmux delpppmux	Activate PPP MUX on the bundle. See Adding PPPMUX to an MLPPP Bundle.

PVC Configuration Quickstart


	Command	Comments
Step 1	switch connection Note: This is an RPM-XF command.	Add a slave PVC connection, for example on the RPM-XF. See Creating a Slave Connection at the RPM-XF.
Step 2	addcon Related commands: dspcons cnfcon delcon	Add a master PVC connection on MPSM-16-T1E1 or MPSM-T3E3-155. See Creating an Master Connection at the MPSM.

MLPPP Provisioning Procedures

This section describes MLPPP restrictions and contains procedures for provisioning MLPPP on an MPSM-16-T1E1 and MPSM-T3E3-155 cards. For information about MLPPP features, see the MPSM-16-T1E1 Card Features, page 1-7 or MPSM-T3E3-155 Card Features, page 1-4.

MLPPP Configuration Guidelines

When configuring MLPPP in your network, keep the following in mind:

•When configuring bundles:

–The MPSM-16-T1E1 supports a maximum of 16 MLPPP bundles with up to 4 PPP links per bundle.

–The MPSM-T3E3-155 supports a maximum of 84 MLPPP bundles with up to 6 links per bundle.

•When configuring links:

–For the MPSM-16-T1E1, links are physical T1/E1 lines.

–For the MPSM-T3E3-155, links are T1/E1 paths. You cannot add lines to the bundle.

–PPP links must belong to MLPPP bundles; standalone PPP links are not supported.

–All PPP links in a MLPPP bundle must have the same bandwidth to fully use each link. If you add links of unequal bandwidth, the bundle bandwidth might be under utilized.

–The MPSM-16-T1E1 requires that all links in an bundle be in the same range, either 1-8 or 9-16.

–Only one fractional T1/E1 link per line or path is allowed.

•When configuring fractional T1/E1:

–For E1 lines, timeslot 0 cannot be used for PPP links.

–For E1 lines with MF and CRCMF formats, timeslot 0 and 16 cannot be used for PPP links.

–DS0 ranges for fractional T1/E1 are contiguous

Adding an MLPPP Bundle

You create MLPPP bundles using the addmpbundle command. A new bundle is administratively up, but its operational state depends on the state of its member PPP links.

In the IP Radio Access Network (IP-RAN) solution or Evolution Data Optimized (EV-DO) solution, you subsequently provision a PVC link between MPSM and the RPM-XF for each bundle. This PVC connects the MLPPP bundle to a virtual interface on the RPM-XF, which routes the data through an IP network.

To create a bundle, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 Enter the addmpbundle command as follows to add an MLPPP bundle.

M8850_SF.25.MPSM16T1E1PPP[FR].a > addmpbundle <bundleNumber> [-mrru <value>] 
[-endDisc <value>]

Table 5-2 describes the parameters for the addmpbundle command.

Table 5-2 addmpbundle Command Parameters
bundleNumber	A number that identifies the new bundle. •MPSM-16-T1E1 range: 1-16 •MPSM-T3E3-155 range: 1-84
-mrru	Specifies the Max Received Reconstructed Unit (MRRU), in the range 64 - 1524. The default is 1524. After the user adds a link to an MLPPP bundle, the MRRU is sent to the remote end, which notifies the remote end that this link is capable of receiving MLPPP packets.
-endDisc	Describes the bundle endpoint. The value is null terminated string that contains printable ASCII characters, which include A-Z, a-z, and 0-9. Maximum length: 20 characters. The default value is a description of the format Node-Name.SlotNumber.BundleNumber.

The following example shows how to create bundle 2.

M8850_SF.27.MPSM16T1E1PPP[FR].a > addmpbundle 2

Step 4 Verify that the MLPPP bundle is created by entering the dspmpbundles command.

The following example displays the new bundle on an MPSM-16-T1E1 card:

M8850_LA.29.MPSM16T1E1PPP[FR].a > dspmpbundles

MLPPP   Admin  Oper    Active  Available       Alarm      MUX      AutoBW

Bundle  State  State   Links   Bandwidth       Cause     Status     Mode

-------------------------------------------------------------------------------

  2       Up   Down      0            0       No Link   Disable    Enable

The following example shows the new bundle on an MPSM-T3E3-155 card:

M8850_LA.13.MPSM155PPP[FR].a > dspmpbundles

MLPPP   Admin  Oper    Active  Available       Alarm      MUX      AutoBW   WP

Bundle  State  State   Links   Bandwidth       Cause     Status     Mode    Id

-------------------------------------------------------------------------------

  2       Up   Down      0            0       No Link   Disable    Enable    1

Adding Links to an MLPPP Bundle

After you create an MLPPP bundle, you can increase the aggregate bandwidth by adding PPP links to the bundle using the addppplink command.

MLPPP links come up as follows:

•The link increases the aggregate bandwidth of the bundle only after the link successfully negotiates the MRRU option with the peer (MWR). Links that fail this negotiation remain in alarm.

•For a bundle with one just PPP link, the data PDU sent or received does not include the MLPPP header. This helps conserve bandwidth on single-link bundles, without affecting solutions such as EV-DO (Evolution Data Optimized).

To add links to an MLPPP bundle, perform the following steps:

Step 1 Establish a configuration session using a username with GROUP1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 Bring up (activate) the lines or paths that you want to add to the bundle. See Chapter 2, "Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication." Remember to select the appropriate service class template (SCT) for the controller or controllers that you are using.

Step 4 Enter the dspmpbundles command to view the available MLPPP bundles.

Step 5 Enter the addppplink command as follows to add a PPP link to an MLPPP bundle:

mpsm_node1.2.MPSM16T1E1[FR].a > addppplink <link> <bay.line> <bundleNumber> [-mru <value>] 
[-lcpTimeout <msec>] [-startDS0 <value>] [-numDS0 <value>] [-ds0speed <mode>]  
[-pfcTx <mode>] [-acfcTx <mode>] [-loopCheck <mode>]

Table 5-3 describes the parameters for the addppplink command.

Table 5-3 addppplink Command Parameters
Parameter	Description
link	A number for the PPP link. •MPSM-16-T1E1 range: 1-16 •MPSM-T3E3-155 range: 1-84
bay.line	The line or path number of the link. •MPSM-16-T1E1 (DS1/E1 line): –bay.line, where bay = 1, line = 1-16. Note All links on a bundle must be in the same range of lines, either 1-8 or 9-16 •MPSM-T3E3-155 (DS1/E1 path): –DS3 line: bay.line:ds1 –DS3 payload: bay.line.sts :ds1 –VT payload : bay.line.sts:vtg.vt –VT structured payload: bay.line.sts:tug3.vtg.vt where: bay=1, line=1-3, sts=0-3, ds1=1-28, tug3=1-3, vtg=1-7, vt=1-4 (VT15) or 1-3 (VT2) Note Enter the dsplns or dsppaths -all command to display all available lines or paths on the card.
bundleNumber	The MLPPP bundle number to which you are adding a PPP link. •MPSM-16-T1E1 range: 1-16 •MPSM-T3E3-155 range: 1-84 Note Enter the dspmpbundles command to display all MLPPP bundles on the card.
-mru	Maximum Receive Unit, in the range 64-1524. Default:1500
-lcpTimeout	Note The length of time to wait for an echo reply before bringing down LCP. The value is specified in msec, but is rounded down to the nearest 100 msec. Range: 1000-4294967 Default: 10000 msec
-startDS0	Specifies a starting DS0 for a fractional T1/E1 link, in the following ranges: •T1 line or path: 1 - 24 •E1 line or path: –E1 and CRC types: 2 - 32 (timeslot 0 reserved) –MF or CRCMF types: 2 - 16, 18 - 32 (timeslots 0 and 16 reserved) Note This parameter is required for a fractional T1/E1 link.
-numDS0	Specifies the number of DS0s for a fractional T1/E1 link, in the following ranges: •T1 line or path: 1- 24 •E1 line or path: –E1 and CRC types: 1- 31 (timeslot 0 reserved) –MF or CRCMF types: 1 - 30 (timeslots 0 and 16 reserved) Default: Maximum number of DS0s Note A fractional T1/E1 link has a contiguous set of DS0s.
-ds0speed	Specifies the speed of DS0 channels. •1 = 56K, •2 = 64K (default)
-pfcTx	Controls the compression of PF in PPP packets transmitted from this end. •1 = enable, PFC is performed if the far end is capable of receiving compressed PF. •2 = disable, PFC is not performed, even if the far end is capable of receiving compressed PF. Default: 2
-acfcTX	Controls the compression of address/control fields in PPP packets transmitted from this end. •1 = enable, ACFC is performed if the far end is capable of receiving compressed address/control fields. •2 = disable, ACFC is not performed, even if far end is capable of receiving compressed address/control fields. Default: 2
-loopCheck	Enables or disables loopback check. If loopback check is enabled, when the magic number in the incoming echo reply is the same as of this PPP link, then this PPP link assumes that the far end is in loopback and brings down the LCP session. •1 = enabled (default) •2 = disabled

The following example adds PPP link 5, line 1.5, to bundle 5 on an MPSM-16-T1E1 card.

M8850_SF.27.MPSM16T1E1PPP[FR].a > addppplink 5 1.5 5

Step 6 Add additional links to the bundle, as necessary.

Step 7 Verify the bundle bandwidth using the dspmpbundle <bundleNumber> command, specifying the desired bundle number.

The following example displays information about bundle 5:

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspmpbundle 5

   Bundle Number            : 5

   Admin State              : Up

   Oper  State              : Up

   Alarm Cause              : No Alarm

   MRRU                     : 1100

   SeqNumFormat             : 24 bit

   Fragmentation            : Disable

   EndpointDiscrimClass     : Locally Assigned

   EndpointDiscriminator    : TestNode.6.1

   LinksConfigured          : 1

   LinksActive              : 1

   RemoteMRRU               : 1100

   RemoteEndpDiscrimClass   : Locally Assigned

   RemoteEndpDiscriminator  : TestNode.6.1

   Configured Bandwidth     : 1344000

   Available Bandwidth      : 1344000

Adding PPPMUX to an MLPPP Bundle

The PPPMUX feature packs small-sized packets into a larger frame before transmission on a PPP link. This helps conserve bandwidth on the T1/E1 lines because it reduces the number of frames and the overhead of extra frame headers. Before PPPMUX becomes active, it must be enabled on both endpoints of the MLPPP bundle.

To add PPPMUX to a bundle, perform the following steps:

Step 1 Establish a configuration session using a username with GROUP1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 Enter the dspmpbundles command to view the available MLPPP bundles.

Step 4 Enter the addpppmux command as follows to add PPPMUX on an MLPPP bundle.

mpsm_node1.2.MPSM16T1E1[FR].a > addpppmux <bundleNumber> [-pid <value>]  
[-muxTimer <value>] [-frameLength <value>] [-subFrameLength <value>]  
[-subFrameCount <value>]

Table 5-4 describes the parameters for the addpppmux command.

Table 5-4 addpppmux Command Parameters
Parameter	Description
bundleNumber	Specifies the bundle number to configure for PPPMUX. •MPSM-16-T1E1 range: 1-16 •MPSM-T3E3-155 range: 1-84 Note Enter the dspmpbundles command to display all MLPPP bundles on the card.
-pid	Specifies the Default Protocol ID, in the range 0 - 65535 Default: 33 (cUDP).
-muxTimer	Specifies the maximum length of time to wait after the multiplexer operation starts before multiplexing begins. Values: 0 (disabled) or 64-4000000 microseconds Default: 600 microseconds
-frameLength	Specifies the maximum length of a multiplexer frame, in the range 1 - 512. Default: 256
-subFrameLength	Specifies the maximum length of a sub-frame, in the range 1 - 512. Default: 64
-subFrameCount	Specifies the maximum number of sub-frames in a multiplex frame, in the range 2 - 15. Default: 15

The following example shows how to add a PPP multiplexer to bundle 5 with a PID of 33, a subframe length of 64, a MUX timer of 600, a subframe count of 15, and a maximum receivable MUXed frame length of 64.

U4.5.MPSM16T1E1PPP[FR].a > addpppmux 5 33 64 600 15 64

MLPPP PVC Connections

In the PPP mode, the MPSM-16-T1E1 and MPSM-T3E3-155 support PVC connections only, and the MPSM must be the master endpoint. For the IP-RAN solution, the RPM-XF is always the slave endpoint.

This section explains how to create the two endpoints, using the IP-RAN solution as an example:

• Creating a Slave Connection at the RPM-XF

• Creating an Master Connection at the MPSM

These procedures presume you have already configured an MLPPP bundle with at least one PPP link. For more information, see Adding an MLPPP Bundle and Adding Links to an MLPPP Bundle.

Creating a Slave Connection at the RPM-XF

Create a slave endpoint for an ATM PVC with the following characteristics:

•PPPoATM encapsulation

•Real-time or non-real-time variable bit rate service

•Bandwidth (PCR and SCR) that match the bundle bandwidth.

•Frame forwarding channel type

The configuration procedure varies by card, so refer to the appropriate configuration guide for details about cards other than the RPM-XF.

To create a slave connection endpoint at the RPM-XF, perform the following steps:

Step 1 Connect to the RPM-XF in privileged exec mode.

Step 2 Configure a switch port, virtual template, and PVC slave connection. For more information about these procedures, see the "Configuring IP-RAN" section in the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide.

Step 3 Display the connection information using the show switch connections vcc <VPI> <VCI>, using the VPI and VCI you used when creating the PVC.

Router#show switch connection vcc 0 102

----------------------------------------------------------

Alarm state           : conditioned

Local Sub-Interface   : 2

Local VPI             : 0

Local VCI             : 102

Remote NSAP address   : default

Local NSAP address    : 47.009181000000000164444B61.000001011802.00

Remote VPI            : 0

Remote VCI            : 0

Routing Priority      : N/A

Max Cost              : N/A

Preferred Route Id    : N/A

Directed Route        : N/A

Percent Util          : 100

Remote PCR            : 14491

Remote SCR            : 14491

Remote MBS            : 1024

Local PCR             : 14491

Local SCR             : 14491

Remote Percent Util   : 100

Connection Master     : Remote

Slave type            : N/A

Synch Status          : inSynch

Auto Synch            : OFF

Admin Status          : UP

Conn-Id               : 1

Update Count          : 141767194

Step 4 Record the Local NSAP address (removing the decimal points), Local PCR, and Local SCR values. You need these later to configure the MPSM master connection.

Creating an Master Connection at the MPSM

To create a master connection endpoint at an MPSM-16-T1E1 or MPSM-T3E3-155 card, perform the following steps:

Step 1 Establish a configuration session using a username with Group1 privileges or higher.

Step 2 Start a management session with the MPSM card using the cc command.

Step 3 Add a frame-forwarding master connection between the MPSM card and the other endpoint using the addcon command. Only one frame-forwarding PVC can be configured per MLPPP bundle.

mpsm_node1.2.MPSM16T1E1[FR].a > addcon <ifNum> <dlci> <chanType> <serviceType> 
<mastership> <cir> 
      [-slave <value>] [-slavepersflag <slavepers>]

      [-eir <zeroCirEir>] [-bc <Burst Commit>] [-be <Burst Excess>]

      [-detag <DE Tagging Enable>] [-igde <Ignore Incoming DE>]

      [-fecnmap <FECN map>] [-demap <DE to CLP map>]

      [-clpmap <CLP to DE map>] [-eqsel <Egress Q Select>]

      [-ingut <Ingress Perc Util>] [-egut <Egress Perc Util>]

      [-egrat <Egress Service Rate>]

      [-rtngprio <Routing Priority>] [-upc <UPC Cnfg>]

      [-lpcr <local -> remote PCR>] [-rpcr <remote -> local PCR>]

      [-lscr <local -> remote SCR>] [-rscr <remote -> local SCR>]

      [-lmcr <local -> remote MCR>] [-rmcr <remote -> local MCR>]

      [-prefrte <routeId>] [-directrte {yes|no}]

      [-rmbs <remote MBS>] [-cc <OAM CC Cnfg>]

Table 5-5 describes the parameters of the addcon command used for MLPPP connections. The unlisted addcon parameters apply to other protocols, have fixed values, or are automatically set; you do not need to set them.

Table 5-5 addcon Command Parameters for the IP-RAN Solution
Parameter	Description
ifnum	Specifies the interface number (bundle number) of the bundle to connect. •MPSM-16-T1E1 range: 1-16 •MPSM-T3E3-155 range: 1-84 Note Enter the dspports command to display the bundle number for all active MLPPP bundles.
dlci	Specifies the data-link connection identifier. Use 1000 for RPM-XF connections.
chanType	Specifies the channel type. The following channel type is valid: •5 = frForward: Frame Forwarding
serviceType	Specifies the service type for the connection. Enter a number to indicate one of the following service types: •2 = rtVBR: real-time variable bit rate (use vbr3rt at ATM endpoints) •3 = nrtVBR: non-real-time variable bit rate (use vbr3nrt at ATM endpoints)
mastership	Controls whether this end of a connection is a master or slave endpoint. Only master endpoints are allowed. •1 = master •2 = slave (not supported)
cir	Specifies the CIR for the connection. •MPSM-T3E3-155 –T1 range: 0-9216000 bps (6 T1s) –E1 range: 0-11984000 bps (6 E1s) •MPSM-16-T1E1 –T1 range: 0-6144000 bps (4 T1s) –E1 range:0-7936000 bps (4 E1s)
-slave	Identifies the slave-end connection in the format nsap_address.vpi.vci. To find the NSAP address for the IP-RAN solution, use the RPM-XF show switch connection vcc <vpi> <vci> command. Remove all of the decimal points from the NSAP address and then append the vpi and vci of the RPM-XF connection endpoint, separated by decimal points.
-lpcr	Specifies the Local PCR, in the range 10 - 104268 cells per second. Set this to the rpcr value of the slave connection.
-lscr	Specifies the Local SCR, in the range 10 - 104268 cells per second. Set this to the rscr value of the slave connection.

In the following example, an RPM-XF slave connection was previously added. The following command adds a master connection to bundle 5 on the MPSM-16-T1E1.

M8850_SF.27.MPSM16T1E1PPP[FR].a > addcon 5 1000 5 3 1 6144000 -slave 
47009181000000000164444B6100000101180200.0.102 -lpcr 14491 -lscr 14491

master endpoint added successfully

master endpoint id : 47009181000000000164444B610000011B1FFF00.24.1000

Note The -slave argument has three parts: NSAP.VPI.VCI. Make sure the NSAP address does not contain decimal points.

Step 4 To verify connections, enter the dspcon command. The following example displays the connection of bundle 5 with DLCI 1000.

D4.11.MPSM16T1E1PPP[FR].a > dspcon 5 1000

--------------------------------------------------------------------------

Local   :                NSAP  Address                     vpi       vci

(M)       4700918100000000107B65F4250000010B1FFF00            8      1000

Remote  :                NSAP  Address                     vpi       vci

(S)       4700918100000000107B65F42500000109180200            4      2005

--------------------------------------------------------------------------

Port Number       : 5                     DLCI             : 1000

Conn. Type        : frForward             Chan Service Type: nrtVBR

Conn Service Type : vbr3nrt               Egress Queue Type: lowPriority

Admn Status       : UP                    Oper Status      : OK

Slave Persist     : YES                   Max Cost         : -1

CIR (bps)         : 10000                 BC (bytes)       : 10300

BE (bytes)        : 10300                 FECN Config      : setEFCIzero

ChanDEtoCLPmap    : setCLPzero            ChanCLPtoDEmap   : ignoreCLP

IngrPercentUtil   : 100                   EgrPercentUtil   : 100

EgrSrvRate (bps)  : 10000                 ZeroCirEir (bps) : N/A

DE Tagging        : DISABLED              IgnoreIncomingDE : DISABLED

Pref Rte Id       : 0                     Directed Route   : NO

Upload            : 000001a3              Routing Priority : 8

OAM CC Config     : DISABLED              Statistics       : ENABLED

Local Loopback    : DISABLED              UPC              : ENABLED

--------------------------------------------------------------------------

Type <CR> to continue, Q<CR> to stop:

Local PCR (cps)   : 25833                 Remote PCR (cps) : 25833

Local SCR (cps)   : 25833                 Remote SCR (cps) : 25833

Local MCR (cps)   : N/A                   Remote MCR (cps) : N/A

                  :                       Remote MBS (cps) : 1024

--------------------------------------------------------------------------

Xmt Abit State    : A equal 1             Rcv Abit State   : OFF

Xmt ATM State     : Not Sending           Rcv ATM  State   : Not Recving

--------------------------------------------------------------------------

E-AIS/RDI   CONDITIONED   CCFAIL   IfFail   Mismatch  LMI-ABIT

   NO           NO          NO       NO        NO        NO

--------------------------------------------------------------------------

Step 5 From the PXM card, you can use the dspcons command to view additional information about the master and slave side of the connection.

M8850_SF.8.PXM.a > dspcons

Local Port   Vpi.Vci    Remote Port  Vpi.Vci     State     Owner  Pri Persistency

----------------------+------------------------+---------+-------+---+-----------

27.65535       8 1000   1:1.2:2        0 101     OK        MASTER 8   Persistent

Local  Addr: 47.009181000000000164444b61.0000011b1fff.00

Remote Addr: 47.009181000000000164444b61.000001011802.00

Preferred Route ID:-    Cast Type: P2P

1:1.2:2        0 101    27.65535       8 1000    OK        SLAVE  -   Persistent

Local  Addr: 47.009181000000000164444b61.000001011802.00

Remote Addr: 47.009181000000000164444b61.0000011b1fff.00

Preferred Route ID:-   Cast Type: P2P

Table Of Contents