Cisco RPM-XF Specifications download pdf (Page 146)

100

101

3-64

Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches

Release 5.2, Part Number OL-6484-01 Rev. C0, September 2005

Chapter 3 Provisioning ATM Services

General AXSM Configuration Procedures

Step 8 Repeat Steps 6 and 7 to add more parties, one at a time, to the root you created in Step 3.

To display all configured parties for a specific connection, enter the dsppartiespercon <portid> <vpi>

<vci> command. Replace <portid> with the Port identifier whose parties you want to view, in the format.

Replace <vpi> with the appropriate VPI of the connection, and <vci> with the appropriate VCI of the

connection.

MGX8850.8.PXM.a > dsppartiespercon 5.3 100 100

Port Vpi Vci Owner State Persistency

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

5.3 100 100 OK MASTER Persistent

Local Addr: 47.009181000000001029300121.000000050300.00

Remote Party 100 101 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 101

Remote Party 100 102 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 102

Port Vpi Vci Owner State Persistency

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

5.3 100 100 OK MASTER Persistent

Local Addr: 47.009181000000001029300121.000000050300.00

Remote Party 100 103 OK PARTY Persistent

Remote Addr: 47.00918100000000c043002de1.000000050300.00

Endpoint Reference: 103

Remote Party 100 104 OK PARTY Persistent

Obtaining the NSAP for a Party

To obtain the NSAP for a party, you need to add a slave endpoint at the port on which the desired party

will reside, and then delete it. Use the following procedure to obtain the NSAP for a party/slave endpoint.

Step 1 Establish a configuration session with the switch that will host the party, using a user name with

GROUP1 privileges or higher.

Step 2 Enter the cc command to change to the AXSM card that will host the root of the P2MP connection.

Step 3 At the AXSM prompt, enter the addcon command to establish a slave end-point for the master endpoint

(or root) that you configured the previous section, as if you are configuring a regular P2P connection.

addcon

ifNum

vpi

vci

serviceType

mastership

[-casttype <value>] [-slave <value>]

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

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

[-lmbs <local -> remote MBS>] [-rmbs <remote -> local MBS>]

[-lcdv <local -> remote maxCDV>] [-rcdv <remote -> local maxCDV>]

[-lctd <local -> remote maxCTD>] [-rctd <remote -> local maxCTD>]

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

[-cdvt <local CDVT>] [-cc <OAM CC Cnfg>] [-stat <Stats Cnfg>] [-frame <frame discard>]

[-mc <Max Cost>] [-lputil <local -> remote PUtil>] [-rputil <remote -> local PUtil>]

[-slavepersflag <slavepers>] [-rtngprio <routingPriority>] [-prefrte <preferredRouteId>]

[-intvsvd <internal vsvd config>] [-extvsvd <external vsvd config>]

[-directrte <directRoute>]

In the following example, the user adds the slave end of a VCC on logical port 1 with VPI=10, VCI=40,

CBR service type.

M8950_DC.5.AXSM.a > addcon 1 10 40 1 s

1 ... 145 146 147 ... 688

Comments to this Manuals

No comments

Cisco RPM-XF Specifications Page 146

Comments to this Manuals

Related products and manuals for Networking Cisco RPM-XF