|
|
This chapter describes how to bring up communications on the physical ports of the CESM cards using the command-line interface (CLI).
 |
Note CESM cards, lines, and ports can also be configured using the CiscoView application. Refer to the CiscoView documentation for the directions. |
|
Note The easiest way to add connections is by using the Cisco WAN Manager application. For full details on how to set up a connection through the Cisco WAN Manager GUI, refer to the Cisco WAN Manager User's Guide. |
This chapter explains how to provision the link and connection types described in Table 2-1.
| AUSM Link and Connection Type | Description |
|---|---|
Lines | Lines establish physical layer connectivity between a CESM port and the same port type (T1, for example) on another device. |
Ports | Ports establish communications over a line to customer premises equipment (CPE). |
CESM-to-CESM SPVCs | Soft permanent virtual circuits (SPVCs) are permanent connections that can be rerouted in the event of a link failure. A CESM-to-CESM SPVC establishes a connection between two CESM ports. Such ports can be on the same card, on different cards in the same switch, or on different cards in different switches. |
CESM-to-Non-CESM SPVCs | A CESM-to-non-CESM SPVC establishes a connection between a CESM port and a port on a non-CESM card such as a PXM1E, FRSM, RPM, or AXSM card. Such ports can be on different cards in the same switch or on different cards in different switches. |
To eliminate redundancy and help experienced users complete configuration tasks quickly and efficiently, this chapter provides configuration quickstart procedures.
The first time you configure a connection type, use the applicable quickstart procedure to get an overview of the tasks to be performed. Then, for more detailed instructions, consult the appropriate section(s) elsewhere in the document that are called out in the quickstart procedure. As you gain experience in configuring CESM card connections, referring to a quickstart procedure may suffice for performing a particular configuration task.
 |
Tip You can get information about most CLI commands by entering the command without parameters. Ordinarily, experienced users can configure CESM card connections using just the quickstart procedures and the online help facilities. |
|
Note For a detailed description of the commands used in this chapter, see "CESM Command Reference." |
When a CESM card is first installed, it must be initialized before you can start configuration. The CESM cards support card redundancy, and they support line redundancy and bulk distribution through SRM cards. Before you begin provisioning connections, you need to initialize the cards you plan to provision, and then you should configure the card and line redundancy options. Otherwise, you may have to change your configuration later to support these options.
For instructions on initializing cards and configuring card and line redundancy, refer to the Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3.
The following sections contain abbreviated procedures for provisioning the communications capabilities of CESM cards installed in MGX 8850 (PXM1E) and 8830 Release 3 switches. These procedures provide a high level overview and serve as a procedural reminder for users already experienced in configuring MGX switches.
To prepare CESM lines for communications with customer premises equipment (CPE), perform the following steps:
| Command | Purpose | |
|---|---|---|
Step 1 | username <password> | Start a configuration session. Note To perform the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher. |
Step 2 | addln <line> Related commands: | Bring up a line. This step establishes physical layer connectivity between an MGX switch and a CPE device. See the "Bringing Up Lines" section that appears later in this chapter. |
Step 3 | cnfln <options> Related commands: | This step allows you to change a line configuration when the default or existing configuration needs changing. For example, the line configuration must be changed if you want to create ports that support unstructured E1 communications. See the "Configuring Lines" section that appears later in this chapter. |
Circuit emulation ports connect an MGX 8850 switch to CPE circuit emulation devices (which, in most cases, are routers).
|
Note The equipment at both ends of a circuit emulation line must be configured with compatible settings in order for the link to be logically completed. |
To configure a circuit emulation port on a CESM card, perform the following steps:
| Command | Purpose | |
|---|---|---|
Step 1 | username <password> | Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher. |
Step 2 | addln <line> | Prepare a CESM line for communications. See "Line Configuration Quickstart," which appears earlier in this chapter. |
Step 3 | addport <options> Related commands: dspports | Add a circuit emulation port. This step establishes circuit emulation communications between two devices. See the "Adding Circuit Emulation Ports" section that appears later in this chapter. |
A soft permanent virtual circuit (SPVC), a variant of a permanent virtual circuit (PVC), can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol.
Both PVCs and SPVCs are full-time connections. However, a PVC uses a predefined circuit path that fails altogether if that path is interrupted for any reason. Conversely, if a link along an SPVC path fails or that link cannot provide the required bandwidth to support the connection, the PNNI protocol reroutes that link to maintain the connection and to supply the necessary bandwidth.
To configure an SPVC between two CESM card ports (on the same card in a switch, on different cards in the same switch, or on cards in different switches), perform the following steps:
| Command | Purpose | |
|---|---|---|
Step 1 | username <password> | Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher. |
Step 2 | Refer to the software configuration guides for the switches between the two CESM cards to be connected. See the Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3 and the Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3. | Configure the trunks that link the switch(es) that host(s) the CESM card ports. Verify PNNI connectivity between the nodes that host the SPVC endpoints. |
Step 3 | See the "Circuit Emulation Port Configuration Quickstart" section that appears earlier in this chapter. | Configure the Circuit Emulation port at each end of the SPVC you are creating. |
Step 4 | addcon <options> Related commands: | Configure the slave side of the SPVC (if you are configuring a double-ended SPVC). See the "Configuring SPVCs on CESM Cards" section that appears later in this chapter. |
Step 5 | addcon <options> Related commands: | Configure the master side of the SPVC. Note In this release, the CESM cards cannot host the master side of a single-ended SPVC. See the "Configuring SPVCs on CESM Cards" section that appears later in this chapter. |
When creating an SPVC between a CESM card and a non-CESM card (such as an PXM1E, AUSM, RPM, or AXSM card), you must define both ends of the connection, just as you would for a CESM-to-CESM connection. The difference is that you will have to refer to the documentation for the non-CESM product for information on configuring the connection endpoint.
To configure an SPVC between a CESM card and a non-CESM card, perform the following steps:
| Command | Purpose | |
|---|---|---|
Step 1 | username <password> | Start a configuration session. Note To perform all the steps in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher. |
Step 2 | Refer to the software configuration guides for the switches between the two cards to be connected. See the Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3 and the Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3. | Configure the trunks that link the switch(es) that host(s) the connection endpoints. Verify PNNI connectivity between the nodes that host the SPVC endpoints. |
Step 3 | See the "Circuit Emulation Port Configuration Quickstart" section that appears earlier in this chapter. | Configure the Circuit Emulation port at the CESM card end of the SPVC you are creating. |
Step 4 | addcon <options> Related commands: | Configure the slave side of the SPVC (if you are configuring a double-ended SPVC). If the slave side of the connection is on the CESM card, see the "Configuring SPVCs on CESM Cards" section that appears later in this chapter. If the slave side of the connection is on a non-CESM card, refer to the documentation for that card. |
Step 5 | addcon <options> Related commands: | Configure the master side of the SPVC. Note In this release, the CESM cards cannot host the master side of a single-ended SPVC. If the master side of the connection is on the CESM card, see the "Configuring SPVCs on CESM Cards" section that appears later in this chapter. If the master side of the connection is on a non-CESM card, refer to the documentation for that card. |
This section describes the following procedures for configuring CESM card communications:
Installing a CESM card can add up to 8 physical lines to your switch. You must bring up a line before you can configure it or provision circuit emulation services on the line.
Before a line is brought up, or after it is brought down, the switch does not monitor the line. Prior to bringing up a line, the CESM port status light for the line is unlit, and all line alarms are cleared.
When you bring up a line on a CESM card, the switch starts monitoring the line. The CESM card port status light turns green when physical layer connectivity is established with a remote device. If a physical layer communications problem occurs, the port status light turns red, and an alarm is reported.
|
Tip To minimize the number of alarms reported and to reduce the frequency of failed port status lamps (which display red), keep lines down until they are actually needed for communication. |
To bring up a CESM line on an MGX switch, perform the following steps:
Step 1 Establish a configuration session using a user name with GROUP 1 privileges or higher.
Step 2 Select the CESM card on which you want to bring up a line by issuing the cc command, as shown below:
PXM1E_SJ.1.7.PXM.a > cc <slotnumber>
Replace the <slotnumber> parameter with the number of the slot in which the CESM card is installed.
Step 3 To activate a line on the CESM card, enter the addln command as shown below:
PXM1E_SJ.1.6.CESM.a > addln <line>
Replace the <line> parameter with the number corresponding to the back card port to which the line is connected. Table 2-2 lists the valid line numbers for the CESM cards.
| Front Card | Valid Line Numbers |
|---|---|
CESM-8T1/B | 1 to 8 |
CESM-8E1 | 1 to 8 |
The following example brings up a line with the default parameters.
PXM1E_SJ.1.4.CESM.a > addln 5
PXM1E_SJ.1.4.CESM.a >
Step 4 To display the current configuration for all lines on a CESM card, enter the dsplns command:
PXM1E_SJ.1.6.CESM.a > dsplns
Line Conn Type Status/Coding Length XmtClock Alarm Stats
Type Source Alarm
---- ----- ------------ ------ -------- ------------- -------- ----- -----
6.1 RJ-48 dsx1ESF Ena/dsx1B8ZS 0-131 ft LocalTim Yes No
6.2 RJ-48 dsx1ESF Ena/dsx1B8ZS 0-131 ft LocalTim Yes No
6.3 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
6.4 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
6.5 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
6.6 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
6.7 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
6.8 RJ-48 dsx1ESF Dis/dsx1B8ZS 0-131 ft LocalTim
LineNumOfValidEntries: 8
PXM1E_SJ.1.6.CESM.a >
When a line has been successfully brought up, the status column reports the line status as Ena, which is an abbreviation for enabled.
The alarm state indicates whether the line is communicating with a remote switch. When the alarm state is blank or is reported as No, it indicates that the physical devices at each end of the line have established physical layer communications. Higher-layer connectivity is established later when ports are configured on the CESM card lines.
All line types are brought up with a default configuration, which may or may not be compatible with the CPE device to which you are connecting. When configuring a CESM card line, you must ensure that the devices at both ends of the connection are using the same configuration parameters on the shared line.
To configure lines on a CESM card, perform the following steps:
Step 1 Establish a configuration session using a user name with GROUP 1 privileges or higher.
Step 2 If you do not know the line number you want to configure on the CESM card, enter the dsplns command to display the current configuration of all lines on the card:
PXM1E_SJ.1.6.CESM.a > dsplns
Remember that you cannot configure a line until you have brought it up, as described earlier in the "Bringing Up Lines" section.
Step 3 To display the configuration information for the particular line that you want to configure, enter a dspln command in the format shown below:
PXM1E_SJ.1.6.CESM.a > dspln 1
LineNum: 1
LineConnectorType: RJ-48
LineEnable: Enabled
LineType: dsx1ESF
LineCoding: dsx1B8ZS
LineLength: 0-131 ft
LineXmtClockSource: LocalTiming
LineLoopbackCommand: NoLoop
LineSendCode: NoCode
LineUsedTimeslotsBitMap: 0x1
LineLoopbackCodeDetection: codeDetectDisabled
LineNumOfValidEntries: 8
PXM1E_SJ.1.6.CESM.a >
This sample dspln command shows the configuration parameters of a T1 line for a CESM card that is installed in slot 1.
Step 4 To configure a line on a CESM card, enter a cnfln command in the format shown below:
PXM1E_SJ.1.6.CESM.a > cnfln <line_num> <line_code> <line_len>
<clk_src> [E1-signalling]
Table 2-3 lists and describes the parameters that you use in configuring T1 and E1 lines on a CESM card.
| Parameter | Description |
|---|---|
line_num | Enter the number of the line you want to configure. Use the dsplns command to display the available lines. |
line_code | Select the line coding:
|
line_len | Enter the length of the line:
|
clk_src | DSX1 clock source.
|
E1-signalling | This option selects E1 signalling methods. Enter the keyword for the signalling combination listed below:
Note To support unstructured E1 communications (addport command), you must set the E1 signalling to CLEAR. |
The following example configures an E1 line for clear channel signaling.
PXM1E_SJ.1.3.CESM.a > cnfln 3 3 9 2 CLEAR
PXM1E_SJ.1.3.CESM.a >
Step 5 To verify the line configuration changes made above, enter a dspln command for the appropriate line.
The "Bringing Up Lines" section that appears earlier in this chapter describes how to bring up physical lines by specifying the correct line port number. Line ports correspond to the line connectors on the back cards of an MGX 8850 switch.
Bringing up a line establishes physical layer connectivity between two network devices. When you add a circuit emulation port to a line, you enable circuit emulation communications by means of that line.
To add a circuit emulation port to a line, perform the following steps:
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 Determine the line number on which you intend to add the circuit emulation port. To do so, enter the dsplns command.
Step 3 Verify that the port number you want to use is not already in use. To display a list of the configured ports on the CESM card, enter the following command:
PXM1E_SJ.1.4.CESM.a > dspports
Port Ena/Speed Type
------ --- ------ --------
4.1.1 Add/1536k structur
4.2.2 Add/1536k structur
4.3.3 Add/1536k structur
4.4.4 Add/1536k structur
Number of ports: 4
PortDs0UsedLine1: 0x00ffffff
PortDs0UsedLine2: 0x00ffffff
PortDs0UsedLine3: 0x00ffffff
PortDs0UsedLine4: 0x00ffffff
PortDs0UsedLine5: 0x00000000
PortDs0UsedLine6: 0x00000000
PortDs0UsedLine7: 0x00000000
PortDs0UsedLine8: 0x00000000
PortNumNextAvailable: 5
PXM1E_SJ.1.4.CESM.a >
This example shows that ports 1 through 4 have been configured on the current card and the next available port number is 5.
Step 4 To add a circuit emulation port to the card, enter the following command:
PXM1E_SJ.1.3.CESM.a > addport <port_num> <line_num> <begin_slot>
<num_slot> <port_type>
Table 2-4 lists and describes the addport command parameters.
| Parameter or Option | Description |
|---|---|
port_num | Port number for the Frame Relay service. The port number range varies with the card type:
|
line_num | Line number to which the port definition applies. To display the lines that have been added, enter the dsplns command. You cannot add a port to a line unless the Status/Coding column shows that the line is enabled (Ena). |
begin_slot | This parameter selects the starting time slot for port communications over the T1 or E1 frame. Valid slot numbers are:
Note When using an unstructured port with T1 or E1 lines, the time slot range is ignored and all channels are assigned to the port. Once an unstructured port is added to a line, you cannot assign additional ports to that line. |
num_slot | This parameter determines the number of consecutive time slots for this port within the T1 or E1 frame. Valid slot numbers are:
Note When using an unstructured port with T1 or E1 lines, the time slot range is ignored and all channels are assigned to the port. Once an unstructured port is added to a line, you cannot assign additional ports to that line. |
port_type | Circuit emulation port type:
|
The following addport command example creates an unstructured port, where all time slots are used by the port (the port range must be entered, but it is ignored).
PXM1E_SJ.1.3.CESM.a > addport 3 3 1 1 2
The next addport command example assigns half of the available T1 time slots on line 4 to port 4.
PXM1E_SJ.1.4.CESM.a > addport 4 4 1 12 1
Step 5 To display the configuration information for a specific port, enter the following command:
PPXM1E_SJ.1.4.CESM.a > dspport <port>
Replace the <port> parameter with the number assigned to the port during configuration.
The following example shows the output of a dspport command for port number 4:
PXM1E_SJ.1.4.CESM.a > dspport 4
SlotNum: 4
PortLineNum: 4
PortNum: 4
PortRowStatus: Add
PortNumOfSlots: 12
PortDs0ConfigBitMap(1stDS0): 0xfff(1)
PortSpeed: 768kbps
PortType: structured
PortState: Active
|
Tip To delete the port configuration, enter the delport command. For more information about these commands, refer to "CESM Command Reference". |
CESM SPVCs are created between one circuit emulation port and another circuit emulation port. Each SPVC has two endpoints. The master endpoint is responsible for routing and rerouting functions. The slave endpoint is responsible for responding to requests from the master during connection setup and rerouting. Both endpoints are configured on the switch or switches to which the circuit emulation CPE connects. Such endpoints can be on the same switch or on different switches.
The master/slave relationship exists for each SPVC and applies only to that SPVC connection. For example, you can have one SPVC with a master on Node A and a slave on Node B, and then create another SPVC with the master on Node B and the slave on Node A. It is good practice to distribute the master side of SPVCs among network nodes so that route processing functions can be distributed.
You can create two types of SPVCs on a CESM cards:
Single-ended SPVCs are defined at the master endpoint and do not require configuration of a slave endpoint. The primary benefit of single-ended SPVCs is that they are easier to configure. After configuration, the master endpoint configures and brings up the slave endpoint. In order for this feature to work correctly, the destination endpoint must support single-ended SPVCs.
|
Note In this software release, the CESM cards support only the slave side of single-ended SPVCs. This means that you can configure master endpoints for single-ended SPVCs on other devices that support this feature, but you cannot create a single-ended SPVC by defining a master endpoint on a CESM card. If both SPVC endpoints must terminate on CESM cards, you must create a double-ended SPVC. |
Double-ended SPVCs require separate configuration of the master and slave endpoints. The slave endpoint must be configured first because this step generates a slave address that must be entered during master endpoint configuration.
The following sections describe how to configure slave and master SPVC connections.
If you wish to configure a double-ended SPVC connection, you must first configure the slave endpoint for the connection. If you are configuring a single-ended SPVC, you need not configure a slave endpoint.
To configure the slave side of a double-ended SPVC, perform the following steps:
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Step 2 Define the slave side of the SPVC by entering the following addcon command:
PXM1E_SJ.1.4.CESM.a > addcon <port_number> [-master <MasterShip>]
[-rmc <RemoteConnId>] [-pf <PartialFill>] [-condat <ConditionalData>]
[-condsig <ConditionalSigCode>] [-cdv <CDVT>] [-cas <SignallingType>]
[-clip <CellLossIntegPeriod>] [-maxbuf <MaximumBufferSize>] [-clkmode <ClockMode>]
[-contp <ControllerType>] [-rtngprio <RoutingPriority>] [-maxcost <MaxCost>]
[-type <restrictedType>]
|
Note If the addcon command fails and displays the "Failed to update disk" message, it could be that the PNNI controller has not been added on the PXM1E card. For information on adding the PNNI controller, refer to the Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3. |
Table 2-5 lists and describes the parameters for the addcon command. The local and remote terms used in this table refer to settings for the local port you are configuring and the remote port at the other end of the connection. If you omit an option, a default value for that option is used for SPVC configuration.
 |
Caution Once you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections have been deleted. The procedure for changing the SPVC prefix is described in the Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3. |
| Parameter | Description | ||
|---|---|---|---|
port_number | Enter the port number for the port to which you will add the connection. To display a list of configured ports, enter the dspports command. | ||
-master | Mastership role of connection. Select from the following options:
| ||
-rmc | Remote connection ID. This option is used when defining the master end of a connection. Enter the slave connection ID as it appears after the addcon command is issued. The format is: RemoteNsapAddress.VPI.VCI.
| ||
-pf | Partial fill for ATM cells. This option determines how many bytes must be assembled before an ATM cell is sent across the network. Partially filled cells take less time to assemble and reduce transmission delay. However, partially filled cells consume more ATM network bandwidth. You can select the number of bytes for ATM cells as follows:
| ||
-condat | Conditional data is sent on the line when there is an underflow and also when there is a loss of signal (LOS). For a voice connection, the larger the ConditionalData value, the louder the hiss heard during LOS. The conditional data range is different for Unstructured Data Transfer (UDT) and Structured Data Transfer (SDT):
| ||
-condsig | Conditional signaling is sent on the line when there is an underflow and also toward the network when forming dummy cells. Conditional signaling is a string of bits that you specify with a decimal number in the range 0-15, where, for example, 15=1111, and 0=0000. These bits represent the ABCD signalling to the line or network when an underflow occurs. | ||
-cdv | Cell Delay Variation Time (CDVT) is the tolerable variation for the arrival time of cells. Enter the CDVT in increments of 125 microseconds:
| ||
-cas | Channel associated signaling (CAS) value.
Note The channels on a particular line can be either all MF (SF MF or ESF SF) or all non-mf (SF or ESF). The first connection type added on a particular line (mf/non-mf) decides the sync. mode. The second connection must have the same cesCas type, and so on. | ||
-clip | Cell loss integration period (CLIP) is the amount of time a connection can be in an error condition before an alarm is declared. Range: 1000 to 65535 milliseconds. | ||
-maxbuf | Maximum egress buffer size in bytes. Buffers are used to mitigate variations in the cell delay. The size can be automatically computed, or you can enter a specific size in bytes. The ranges are as follows:
N = Number of 64 Kbps time slots (SDT) = 32 (T1/E1 UDT) | ||
-clkmode | Clock mode.
| ||
-contp | Controller type. Select one of the following:
| ||
-rtngprio | Routing priority for this connection. Range is 1 to 15. Default setting is 8. | ||
-maxcost | Maximum end-to-end cost for the connection. Range is 1 to 2,147,483,647. Default setting is 2147483647. | ||
-type | Trunk restriction option. To restrict the connection routing to terrestrial trunks, enter -type 2. To restrict the connection routing to satellite trunks, enter -type 3. To enable connection routing without trunk restrictions, enter -type 1. Default setting routes connections with no restrictions. |
|
Tip If you omit one or more of the configuration options when entering the addcon command, the SPVC connection uses the default values listed in Table 2-5, as appropriate. To override the default value for a given option, enter the option with a desired value. |
The following addcon command defines a port as the slave side of an SPVC connection. Note the slave Local Connection ID shown at the end of the display.
PXM1E_SJ.1.4.CESM.a > addcon 1
Local Connection ID is : 4700918100000000001a53337700000107230100.4.35
PXM1E_SJ.1.4.CESM.a >
Step 3 Write down the NSAP address displayed when the addcon command output is completed. You will need the NSAP address to configure the master side of the SPVC connection.
|
Tip When you set up the master side of the SPVC, you will need to enter the slave ATM address reported by the addcon command. If you maintain the current session or use the session Copy command to copy the ATM address now, you can use the session Paste command to complete the addcon command on the switch that hosts the master side of the SPVC. |
Step 4 Verify the addition of the slave side of the SPVC connection by entering the following command, which causes all information for the SPVCs to be displayed:
PXM1E_SJ.1.4.CESM.a > dspcons
LCN Port.VPI.VCI Type M/S Clock PCR CDVT BufSz CLIP Admin Alarm
---- ------------ ---- --- ----- ------ ----- ----- ----- ----- -----
0035 001.04.035 stru S Synch 4096 01000 00384 02500 Up CTRLR-ABIT
0037 003.04.037 stru S Synch 4096 01000 00384 02500 Up CTRLR-ABIT
Number of channels: 2
ChanNumNextAvailable: 38
PXM1E_SJ.1.4.CESM.a >
Step 5 If you add the master side of the SPVC at a later date, you can display the slave connection ID with the dspcon command as shown in the following example. The connection number is specified by entering the port number. The complete slave ID must be entered at the master endpoint in the format ChanLocalNSAP.ChanLocalVpi.ChanLocalVci. These values correspond to dspcon parameters shown in this example:
PXM1E_SJ.1.4.CESM.a > dspcon 1
-------------------------------------------
ChanNum: 35 RowStatus: Add
AdmnState: Up ChanState: Alarm
---------- ---------- ---------- ----------
PORT-ALARM CTRLR-ABIT E-AIS/RDI CELL-LOSS
---------- ---------- ---------- ----------
NO NO NO YES
-------------------------------------------
ChanNum: 35
ChanRowStatus: Add
ConnAdminStatus: Up
ChanLineNum: 1
ChanMapVpi: 4
ChanMapVci: 35
ChanCBRService: struct
ChanClockMode: Synchronous
ChanCAS: Basic
ChanPartialFill: 47
ChanMaxBufSize: 384 bytes
ChanCDVT: 1000 micro seconds
C L I P: 2500 milliseconds
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 ms
ChanPortNum 1
ChanConnType SPVC
ISDetType DetectionDisabled
CondData 255
CondSignalling 15
ExtISTrig DisableIdleSupression
ISIntgnPeriod 3 seconds
ISSignallingCode 0
OnHookCode 1
ChanLocalVpi: 4
ChanLocalVci: 35
ChanLocalNSAP: 4700918100000000001a53337700000107230100
ChanRemoteVpi: 0
ChanRemoteVci: 0
ChanRemoteNSAP: NULL NSAP
ChanMastership: Slave
ChanVpcFlag: Vcc
ChanConnServiceType: CBR1
ChanRoutingPriority: 8
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction
ChanConnPCR: 4096
ChanConnMCR: 4096
ChanConnPercentUtil: 100
Channel Reroute: False
ChanNumNextAvailable: 36
PXM1E_SJ.1.4.CESM.a >
To configure the master side of an SPVC, perform the following steps:
Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
|
Tip During this procedure, you will have to enter the ATM address for the slave end of the connection. If you establish this session from the same workstation you used to create the slave connection, you can do a copy and paste sequence to avoid data entry errors. |
Step 2 To define the master side of the SPVC connection, enter the following command:
PXM1E_SJ.1.4.CESM.a > addcon <port_number> [-master <MasterShip>]
[-rmc <RemoteConnId>] [-pf <PartialFill>] [-condat <ConditionalData>]
[-condsig <ConditionalSigCode>] [-cdv <CDVT>] [-cas <SignallingType>]
[-clip <CellLossIntegPeriod>] [-maxbuf <MaximumBufferSize>] [-clkmode <ClockMode>]
[-contp <ControllerType>] [-rtngprio <RoutingPriority>] [-maxcost <MaxCost>]
[-type <restrictedType>]
|
Note If the addcon command fails and displays the "Failed to update disk" message, it could be that the PNNI controller has not been added on the PXM1E card. For information on adding the PNNI controller, refer to the Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3. |
Table 2-5 lists and describes the parameters for the addcon command.
|
Tip If you omit one or more of the options when entering the addcon command, the connection uses the default values listed in Table 2-5. To override the default value for a given option, enter the option with the desired value. |
The following addcon command defines a port as the master side of a double-ended SPVC.
PXM1E_SJ.1.4.CESM.a > addcon 2 -master 1 -rmc
4700918100000000001a53337700000107230100.4.35
PXM1E_SJ.1.4.CESM.a >
Step 3 To view the master-side of the new SPVC connection in the connection list, enter the dspcons command:
PXM1E_SJ.1.4.CESM.a > dspcons
LCN Port.VPI.VCI Type M/S Clock PCR CDVT BufSz CLIP Admin Alarm
---- ------------ ---- --- ----- ------ ----- ----- ----- ----- -----
0035 001.04.035 stru S Synch 4096 01000 00384 02500 Up OK
0036 002.04.036 stru M Synch 4096 01000 00384 02500 Up OK
0037 003.04.037 stru S Synch 4096 01000 00384 02500 Up CTRLR-ABIT
Number of channels: 3
ChanNumNextAvailable: 38
This command displays all the connections for the CESM card.
Step 4 To display the configuration information for a specific SPVC endpoint, enter the following command:
PPXM1E_SJ.1.4.CESM.a > dspcon port
Replace the port parameter with the port number for the connection you want to display. The port number is listed in the dspcons command display.
The following is sample output from the dspcon command for the connection created in the previous example. Notice that once the master connection is added, the dspcon report shows the NSAP IDs for both ends of the connection.
PXM1E_SJ.1.4.CESM.a > dspcon 2
-------------------------------------------
ChanNum: 36 RowStatus: Add
AdmnState: Up ChanState: Ok
---------- ---------- ---------- ----------
PORT-ALARM CTRLR-ABIT E-AIS/RDI CELL-LOSS
---------- ---------- ---------- ----------
NO NO NO NO
-------------------------------------------
ChanNum: 36
ChanRowStatus: Add
ConnAdminStatus: Up
ChanLineNum: 2
ChanMapVpi: 4
ChanMapVci: 36
ChanCBRService: struct
ChanClockMode: Synchronous
ChanCAS: Basic
ChanPartialFill: 47
ChanMaxBufSize: 384 bytes
ChanCDVT: 1000 micro seconds
C L I P: 2500 milliseconds
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 ms
ChanPortNum 2
ChanConnType SPVC
ISDetType DetectionDisabled
CondData 255
CondSignalling 15
ExtISTrig DisableIdleSupression
ISIntgnPeriod 3 seconds
ISSignallingCode 0
OnHookCode 1
ChanLocalVpi: 4
ChanLocalVci: 36
ChanLocalNSAP: 4700918100000000001a53337700000107230200
ChanRemoteVpi: 4
ChanRemoteVci: 35
ChanRemoteNSAP: 4700918100000000001a53337700000107230100
ChanMastership: Master
ChanVpcFlag: Vcc
ChanConnServiceType: CBR1
ChanRoutingPriority: 8
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction
ChanConnPCR: 4096
ChanConnMCR: 4096
ChanConnPercentUtil: 100
Channel Reroute: False
ChanNumNextAvailable: 38
Posted: Fri Oct 18 11:16:30 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.