Table Of Contents
AXSM Command Reference
This chapter provides descriptions of the commands that are available on the AXSM CLI. The commands are in alphabetical order. The descriptions include the following information about the commands:
•
The name of the command as it is entered in the CLI.
•
•
•
•
•
•
–
–
–
•
addapsln
Add APS Line—AXSM, AXSM-E, AXSM-XG
Designates a pair of lines (workingIndex, protectIndex) as APS lines. To configure the APS parameters, use the cnfapsln command after creating the lines using the addapsln command.
Note
APS Overview
Automatic Protection Switching (APS) is a standards-based redundancy scheme which enhances network reliability by protecting against line failure. APS is defined in Bellcore and ITU standards for North American SONET and international Synchronous Digital Hierarchy (SDH) optical network links. The relevant standards are Bellcore GR-253 and ITU-T G.783.
APS enables a pair of SONET lines to be configured for line redundancy. The APS pair consists of a working line (workingIndex) and a protection line (protectIndex), where one line is active and the other is a backup. Whether or not the backup line passes traffic while in standby mode depends on the APS architecture mode (archmode).
Coordination of line switching is controlled by an in-band signaling protocol. If the fiber optic carrier for the active line is severed or damaged, the in-band signaling protocol must detect the fault within 10 milliseconds. After the in-band signaling protocol has detected the fault, it must switch the user traffic to the standby line within 50 milliseconds.
When the revertive option is enabled (see cnfapsln), the in-band signaling protocol will attempt to switch the user traffic back to the working line from the protection line after the working line becomes functional again. However, it must wait for the configured time period (wait to restore) to elapse.
Direction
APS can be configured in two directions (see direction parameter in cnfapsln), bidirectional and unidirectional. Bidirectional means that both the receiving and transmitting paths are switched. Unidirectional means that only the affected path, receiving or transmitting, is switched.
Same-card APS
In same-card APS, the working bay and protection bay must be the same, and the working line and protection line must be adjacent.
Architecture mode 1:1 is supported only on same-card APS.
Cross-card APS
In cross-card APS, the working slot and the protection slot must be adjacent. The working bay and line number, and the protection bay and line number must be the same. Card redundancy must be configured on the two cards before cross-card APS can be added (see the addred command).
Architecture modes 1+1, Annex 1+1, and Straight 1+1 Nok1k2 are supported on same-card as well as cross-card APS.
AXSM-E, AXSM-XG
On AXSM-E and AXSM-XG, the primary line numbers must be 1.1 and 1.3 for the upper card and 2.1 and 2.3 for lower card.
APS Architecture Modes
AXSM/A supports the following APS architecture modes (archmode):
•
•
Note
AXSM/B, AXSM-E, and AXSM-XG supports the following APS architecture modes (archmode):
•
•
•
Note
Note
AXSM/A and AXSM/B APS Issues
AXSM PXM45-based software has two different operating modes:
•
•
Note
AXSM PXM1-based cards and below have only the AXSM-A mode. AXSM PXM45-based cards have both AXSM-A and AXSM-B modes.
When you upgrade from a PXM1-based switch to a PXM45-based switch, the AXSM will still be in AXSM-A mode. To change to AXSM-B mode, use the PXM command, enableaxsmbaps from the PXM CLI. Refer to Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 4.
AXSM-A mode monitors only one line at a time. AXSM-B monitors two lines at the same time. AXSM/B cards can run in either the AXSM-A or AXSM-B mode.
When using two AXSM/A cards for an APS redundant pair, if one of the AXSM/A cards does not function in the intercard state, the AXSM-A mode will not function. AXSM/A transmits RDI on both the working and protection lines.
When using two AXSM/B cards for an APS redundant pair, if one of the AXSM/B cards does not function in the intercard state, APS is unaffected.
For APS to function properly on AXSM/B, AXSM-E, and AXSM-XG, at least one front card and its back card must be functioning properly. However, signal failure will be reported from all lines on the other back card if the other back card is not present.
Syntax (AXSM)
addapsln <workingIndex> <protectIndex> <archmode>
Syntax Description (AXSM)
Syntax (AXSM-E, AXSM-XG)
addapsln <wSlot.wBay.wLine> <pSlot.pBay.pLine> <mode>
Syntax Description (AXSM-E, AXSM-XG)
Related Commands
cnfapsln, delapsln, dspapsln, dspapslns, switchapsln, dspapsbkplane, clrbecnt, dspbecnt
Attributes
Example
Add 1+1 APS redundancy to two lines on the same AXSM card:
MGX8850.9.AXSM.a > addapsln 9.2.1 9.2.2 1addchanloop
Add Channel Loopback—AXSM, AXSM-E, AXSM-32-T1E1-E, AXSM-XG
The channel loopback tests the integrity of the connection (channel) at the local UNI or across the network. The system returns an error message if the connection is broken or incorrect data arrives at the end of the loopback. The maximum number of connection loopbacks that can exist on an AXSM is 256.
The addchanloop command applies to a network that is not carrying live traffic because the test is very intrusive. The test requires a testing device to generate a cell stream. The parameters for such a stream are the number of cells transmitted through the loop, the cell transfer rate, and so on. (To test connection integrity in a non-destructive way while the connection carries user data, use tstdelay on the ingress or tstconseg on the egress. These commands generate one OAM cell for each command execution.)
A connection can have only one loopback at a time. Therefore, you cannot add a loopback for both directions at the same time. The loopback remains until you delete it by executing delchanloop. To see the presence of connection loopbacks on a per-port basis, use dspchanloop.
The addchanloop command lets you specify the direction of cell flow within the loop (see Figure 3-1).
•
•
The maximum number of loopbacks that can exist on an AXSM is 256.
Figure 3-1 Connection (Channel) Loopbacks on the Ingress and Egress
Syntax
addchanloop <ifNumber> <vpi> <vci> <loopback mode>
Syntax Description
Related Commands
delchanloop, dspchanloop
Attributes
Example
Add a loopback on the connection with VPI/VCI of 1 50 on logical port 4. No message is returned unless an error occurs in command execution (such as an attempt to add a channel loopback to a connection that already has a loopback).
MGX8850.1.AXSM.a > addchanloop 4 1 50Check for the presence of the loopback by displaying all channel loopbacks on port 4.
MGX8850.1.AXSM.a > dspchanloop 4Port Type lVPI lVCI rVPI rVCI4 igrLpbk 1 50 0 35addcon
Add Connection—AXSM, AXSM-E, AXSM-32-T1E1-E, AXSM-XG
Adds a logical connection as an SPVC on a service module. The switch assigns a 20-octet NSAP address to the slave endpoint, which is sent back to the master and uniquely identifies the endpoint on the network. An AXSM front card can support a maximum of 64K SPVCs. This command does not apply to SVCs or SVPs.
AXSM supports a maximum of 64K SPVCs.
AXSME supports a maximum of 60K SPVCs-4K are reserved.The connection is either a dual-ended connection or a single-ended connection. For a dual ended connection, you first add the endpoint at the slave-end switch. Upon successful addition of the slave endpoint, the slave-end node generates a 20 octet NSAP address for that endpoint that is used at the master endpoint. The slave endpoint identifier uniquely identifies the endpoint in the network, and you must use this identifier when adding the master endpoint of a dual-ended connection. For a single-ended connection, you add the connection only at the master end.
Before Adding a Connection
Before you can add an SPVC, the following tasks must have been completed:
1.
2.
3.
4.
Adding a Connection
Adding a connection requires you first to provision a slave endpoint. Subsequently, you again execute addcon to provision a master endpoint. The master endpoint of the connection initiates the routing of the call and can be viewed as the "calling" party. The slave endpoint is the called endpoint. The following characteristics pertain to this master-slave arrangement:
•
•
To modify the bandwidth parameters or configure usage parameter control (UPC), use cnfcon for all service types. In addition, ABR connections require more configurable parameters for implementing closed loop control. Use the cnfabr command to configure the ABR parameters.
Traffic Parameters
Traffic parameters such as PCR, SCR, MBS are entered at both the master and slave endpoints for both the forward and reverse directions. Be sure that the value entered as "local" on one end is equal to the value entered as "remote" on the other end. For example, the lpcr on the slave endpoint should be same as the rpcr on the master endpoint and vice versa when you provision the connection at the other end. If you modify traffic parameters after creating a dual-ended SPVC, you must modify them using the same set of parameters at both the master endpoint and the slave endpoint. For a single-ended connection, modify parameters at the master endpoint only.
Traffic parameters such as CDV, CTD are entered at both the master and slave endpoints for both the forward and reverse directions. However, the parameters entered at the slave end are ignored during call setup. Therefore, you can specify the lcdv, rcdv, lctd and rctd options at the master end only.
Default Traffic Parameters in the Service Class Templates
The Service Class Templates (SCTs) provide the default traffic parameters for the logical ports. The default traffic parameters are set to a fraction of the bandwidth available on the logical port. The SCT ID (sctID) and interface type (ifType) parameters that are specified using the addport command determine which default traffic parameters are used.
Note
Note
Table 3-1 Default Traffic Parameters for AXSM
VSI-SIG
N/P
N/P
N/P
N/P
N/P
N/U
N/P
CBR.1
50
N/A
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
VBR-RT.1
50
50
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
VBR-RT.2
50
50
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
VBR-RT.3
50
50
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
VBR-nRT.1
50
50
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
VBR-nRT.2
50
50
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
VBR-nRT.3
50
50
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
UBR.1
50
N/A
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
UBR.2
50
N/A
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
ABR
50
N/A
50
50
dspmbsdft
N/U
dspcdvtdft
CBR.21
50
N/A
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
CBR.32
50
N/A
N/A
N/A
dspmbsdft
N/U
dspcdvtdft
1 CBR.2 will no longer be available in the near future. Use CBR.1 instead.
2 CBR.3 will no longer be available in the near future. Use CBR.1 instead.
Routing Parameters
Routing parameter such as maximum route cost (-mc maxcost) or the routing priority (-rtngprio routingPriority) must be entered only at the master endpoint.
You can assign a priority at the master end of an SPVC or SPVP. The PNNI controller routes higher priority connections before lower priority connections. The user-configurable range for a connection is, in descending order of priority, 1-15. The default is 8. See cnfpri-routing for a detailed description of the Priority Routing feature. Also, the cnfpri-routing command lets you configure groups of bandwidth so that the order of routing also reflects the bandwidth requirements of the connection.
A connection created with older software that does not support Priority Routing receives the default priority of 8 after an upgrade. You can modify this priority by using the cnfcon command.
Frame Discard
The current release supports two types of frame discard for VCCs carrying AAL5 cells. These frame discard mechanisms are policing-based and congestion-based. Policing-based frame discard depends on the -frame option in the addcon or cnfcon command. (Congestion-based policing for all cell streams is governed by settings in the current port SCT.) This -frame parameter is specified only at the master end.
When policing-based frame discard is enabled, the policer discards all cells of an AAL5 frame that follow a non-compliant cell. Specific actions for PCR and SCR non-compliance are detailed in the section, "Policer Settings and Consequences."
When congestion based frame discard is enabled in the current port-level SCT, if the arriving cells exceed an EPD threshold, the whole frame is discarded.
Note
Table 3-3 shows the action applied to a connection according to the frame discard setting. The following information clarifies the table contents:
•
–
–
•
–
A value of 1 implies that the EPD0/1 thresholds would take effect during congestion and that discards would occur on an AAL5 frame-basis.
Restrictions
Frame discard applies to connections that use ATM AAL5 adaptation (ITU-T I.363.5). Although enabling frame discard on an AAL5 cell stream is not mandatory, it helps improve the useful throughput on a VC by discarding complete frames during times of congestion on the switch. Without frame discard enabled on an AA5 cell stream, corrupted AAL5 frames (containing dropped cells) can reach upper layers and trigger numerous re-sends. Conversely, enabling frame discard on other (non-AAL5) types of cell streams can bring uncertain results. In a worst case, total discard of end-to-end traffic of a non-AAL5 stream can occur in either direction.
The service module hardware does not support frame-based discard on VPCs. Only VCCs support frame-based discard.
Note
Policer Settings and Consequences
This section describes two types of conformance tests that occur when you enable frame discard through this frame discard parameter. The tests are PCR and SCR conformance tests.
The PCR conformance test is performed using GCRA1 in exactly the same manner as normal cell policing. For this test, the Action should be set to discard. If the PCR conformance test is deemed to be non-compliant, the action will be to discard of the cells in the current frame. In other words, a "partial packet action" can be taken when cells in the current frame fail this conformance test. The PCR conformance test implements a partial packet discard (PPD). The policer does a complete frame discard if the first cell of the packet was discarded as a result of PCR failure
The SCR conformance test is performed using GCRA2, although it differs slightly from the normal cell policing.The SCR conformance test is performed only at the start of a frame. If the first cell of a frame is a conforming CLP=0 cell, then all remaining cells will be as if they are conforming to the SCR conformance test. The SCR conformance test can be programmed to tag non-conforming CLP=0 cells. If the first cell of a frame is a non-conforming CLP=0, then that cell and all other cells in that frame (including the EOM) will be tagged. In other words, the tagged action taken by this conformance test is determined at frame boundaries only. If the SCR conformance test is programmed to discard, the policer can discard at any point in the frame and is not restricted by frame boundaries.
Local-Only Parameters
The parameters CDVT, stats enable, (specified using -cdvt, -stat) are significant only at the endpoint where you enter them. Therefore, they can be different at each end of the connection. Note that the cc parameter must be enabled at both ends or disabled at both ends.
Interoperability With Other Switches
Cisco MGX 8850 PXM1E-based and PXM45-based switches support interoperability with nodes manufactured by other vendors or Cisco ATM WAN switches other than the MGX and BPX families of switches. The other Cisco devices include the LS 1010 switch, DSLAMs such as the Cisco 6160 and Cisco 6250 products, and feeder nodes.
The mechanism that supports this interoperability is the single-ended provisioning of a connection. With single-ended provisioning, you specify both endpoints at the master endpoint only, and the slave endpoint is called a non persistent slave endpoint.
In single-ended provisioning, the slave endpoint is not actually provisioned on the far-end service module. The slave endpoint exists only on the PNNI controller on the local node. The slave endpoint is cleared when the connection is derouted by either the dncon command or the clrspvcnonpers command (the delcon command does not apply to nonpersistent endpoints).
Specifying a Single-ended Connection
A single-ended connection can be added only through the addcon command. CWM currently does not support addition of single-ended connections but only shows these connections.
The single-ended connection is specified at the master endpoint only. The specific addcon parameters that create a single-ended connection are as follows:
•
•
•
When you add a dual-ended connection, command entry for the slave endpoint automatically returns the connection identifier for the slave endpoint. For single-ended connections, you must already have the connection identifier for the non-persistent, slave endpoint. How you get the slave endpoint ID depends on the vendor of the switch, as follows:
•
•
•
To delete a single-ended connection, use the delcon command at the master endpoint. To de-route a single-ended connection, use the clrspvcnonpers command at the slave endpoint.
Overriding a Slave-end SVC or SVP
A routed SVC may have a VPI and VCI at the slave-end port that is needed by an incoming, single-ended connection. Because an existing SVC can take the next available VPI/VCI on the port, you can enable an override of the VPI/VCI. To override an SVC or SVP use the cnfsvcoverride command.
Limits
The following limitations apply to single-ended connections.
•
•
–
–
•
Characteristics Multicast Operation
Point-to-multipoint (P2MP) connections are added at the master endpoint only. You do not specify an NSAP in this case. After the connection has been added, you can add multiple parties by using the addparty command on the PXM on the source node. In the addparty command, you can provide an NSAP for the remote endpoint (the party). The nature of P2MP connections significantly affects the connection services that are available to these connections. This section describes these effects.
•
•
•
•
•
•
•
–
–
–
–
–
•
–
–
–
–
OAM and Failure Management
OAM functionality is not supported for P2MP connections (OAM needs two way communication of OAM cells). Further, the following functionality is not supported on P2MP connections:
•
•
•
At the P2MP root, the following functionality is supported:
•
•
•
Syntax (AXSM)
addcon <ifNum> <vpi> <vci> <service type> <mastership>
[-casttype <value>] [-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>]
[-lscr <local SCR>] [-rscr <remote SCR>] [-lmbs <local MBS>] [-rmbs <remote MBS>]
[-cdvt <local CDVT>] [-lcdv <local maxCDV>] [-rcdv <remote maxCDV>] [-lctd <local maxCTD>] [-rctd <remote maxCTD>] [-cc <OAM CC Cnfg>] [-stat <Stats Cnfg>] [-frame <frame discard>]
[-mc <maximum cost>] [-lputil <local util>] [-rputil <remote util>] [-slavepersflag <slavepers>] [-rtngprio <routingPriority>] [-prefrte <preferredRouteId>] [-directrte <directRoute>]
Note
Syntax Description
For the applicable parameters, the "local" end is the point at which you are provisioning the connection.
ifNum
The logical interface (or port) number. This ifNum corresponds to the ifNum added through the addport command. The ranges are:
•
•
•
When you add an endpoint on an NNI, make sure that PNNI signaling is disabled on the PXM45 (cnfpnportsig <portid> -nniver none).
vpi
Virtual path identifier value in the range 0-255 (UNI) or 0-4095 (NNI or VNNI). For VNNI, specify one VPI per port.
vci
Virtual connection identifier (VCI):
•
•
service type
Value in the range 1-12 to specify the service type:
•
•
•
•
•
•
•
•
•
•
•
•
Note
mastership
Value to specify the endpoint as master or slave:
•
•
-casttype
The broadcast type is either point-to-point or point-to-multipoint, as follows:
•
•
Default: point-to-point (0)
-slave
The slave-end connection identifier is an item you enter at the master end. For a dual-ended connection, you get the slave-end connection ID at the slave-end node when you add that endpoint. This keyword is mandatory when you are adding a master endpoint (mastership=1).
-lpcr
Local peak cell rate (PCR). Specifies the PCR from a local endpoint to a remote endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-rpcr
Remote peak cell rate (PCR). Specifies the PCR from a remote endpoint to a local endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-lscr
Local sustained cell rate (SCR). Specifies the SCR from a local endpoint to a remote endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-rscr
Remote sustained cell rate (SCR). Specifies the SCR from a remote endpoint to a local endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-lmbs
Local maximum burst size (MBS). Specifies the MBS from a local endpoint to a remote endpoint (1-5000000 cells). MBS is the maximum number of cells that can burst at the PCR and still be compliant.
-rmbs
Remote maximum burst size (MBS). Specifies the MBS from a remote endpoint to a local endpoint (1-5000000 cells). MBS is the maximum number of cells that can burst at the PCR and still be compliant.
-cdvt
Local cell delay variation tolerance (CDVT). Specifies the CDVT from a local endpoint to a remote endpoint (1-5000000 microseconds). Cell Delay Variation Tolerance controls the time scale over which the PCR is policed.
Note that no remote CDVT is necessary.
-lcdv
The local cell delay variation (CDV) parameter specifies the peak to peak cell delay variation from the local endpoint to the remote endpoint. The range is 1-16777215 microseconds.
-rcdv
The remote cell delay variation (CDV) parameter specifies the peak to peak cell delay variation from the remote endpoint to the local endpoint. The range is 1-16777215 microseconds.
Default: -1
-lctd
Local cell transfer delay (CTD). This parameter specifies the CTD from a local endpoint to a remote endpoint. The range is 0-65535 microseconds.
-rctd
Remote cell transfer delay (CTD). This parameter specifies the CTD from the remote endpoint to the local endpoint. The range is 0-65535 microseconds.
Default: -1
-cc
Operations, administration, and maintenance continuity check (OAM CC):
•
•
Continuity checking involves a round trip of an OAM cell simply to confirm that both directions of the connection are intact.
To provision continuity checking, enable this function at both ends of the connection, otherwise a connection alarm results. When you add a connection and include this parameter, the connection goes into alarm until both ends of the connection are added.
Note that a non-zero AIS delay timer affects CC functionality (if enabled) during the intentional re-routing of a connection following the optrte or cnfrteopt command. (See the cnfaisdelaytimer description for details of this AIS-delay feature.) If the delay timer is configured and the connection is groomed, the switch turns of CC until the connection is re-routed.
Default: 0
-stat
Statistics collection: enter 1 to enable or 0 to disable. The default is 0.
The Cisco WAN Manager tool collects statistics for a connection if you enable it here. Statistics collection is disabled for all connections by default. Statistics collection has an impact (which may not be significant) on the real-time response, especially for SVCs (which can be affected even though you do not add SVCs). Therefore, you should enable statistics collection for only the subset of connections that really warrants such a feature.
-frame
This optional parameter lets you enable or disable frame discard for the connection. Note that you can use it at only the master endpoint of a connection.
•
•
Default: 0 (disabled)
-mc
Maximum cost (maxcost): a value that creates a priority for the connection route. The switch can select a route if the cost does not exceed maxcost. The range for maxcost is 0-4294967295. If you do not specify maxcost, the connection has the highest routing priority by default. Therefore, the maxcost parameter lets you lower the routing priority of a connection. Note the following effects of values in the maxcost range:
•
•
•
Although maxcost applies to an individual connection, routing costs substantially depend on a cost-per-link that you specify at every PNNI logical port in the network. The applicable PNNI command is cnfpnni-intf.
The cost of a route is as follows:
routing cost = sum of all costs-per-link
where:
•
•
The cost-per-link applies to all connections of a particular service type on a port. For example, the cost-per-link is the same for all VBR.1 connections that PNNI controls on a port, and this cost can differ from all UBR.1 connections on the same port. Alternatively, you can use cnfpnni-intf to make the cost-per-link the same for all service types.
To illustrate by examining a four-link route:
1.
2.
3.
The route is usable because the cost of 50240 is less than the maxcost of 100000.
Default: 4294967295 The default makes maxcost meaningless for the connection, so PNNI does not use it as a routing metric.
Note
-lputil
Local Percentage Utilization: Range 1-100. The default is 100.
-rputil
Remote Percentage Utilization: Range 1-100. The default is100.
-slavepersflag
The slave endpoint persistency flag is necessary for setting up a single-ended connection. For details, see the section, "Interoperability With Other Switches."
•
•
Default: persistent
-rtngprio
You can modify the priority of this connection. The range is 1-15. Default: 8
-prefrte
This option associates a preferred route to the connection. Use this optional parameter at the master endpoint only. Be sure the route exists before you associate it with the connection because the system does not check it. Use the dspprefs command as needed. See the addpref description for details on preferred routes.
To disassociate a connection from a route, assign a value of 0 for the -prefrte parameter through the cnfcon command.
Note
dspcons [-rteid <pref rte id> ]
Note
Range: 0-65535
Default: 0
-directrte
This parameter specifies that the connection can take only the preferred route associated through the -prefrte parameter. Use this optional parameter at the master endpoint only. To remove this requirement from the connection, use the cnfcon command and specify a 0 for this parameter. The possible values are as follows:
•
•
Default: no (0)
Error Messages
The system can display error messages for the following reasons:
•
•
•
•
One of the following error messages appears if one of the preceding causes is true:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Related Commands
cnfcon, cnfabr, delcon, dspcon, dspcons, dncon, upcon
Attributes
Example
Add the slave end of a VCC on logical port 1 with VPI = 10, VCI = 40, CBR service type. Note that the system returns the slave end connection identifier in the hexadecimal NSAP format with the VPI.VCI at the end. When you add the master endpoint of the connection, type -slave followed by this connection identifier. You can do a copy and paste rather than typing the whole string.
MGX8850.AXSM.a >addcon 1 10 40 1 sslave endpoint added successfullyslave endpoint id: 00000E1000001C008051B730FFFFFF010B180100.10.40In the following two examples, the connection works with default values of PCR, SCT, MCR taken from the SCT. Defaults applied for the connection can be viewed by using the dspcon command.
MGX8850.1.11.AXSME.a > addcon 1 10 40 1 sslave endpoint added successfullyslave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40MGX8850.1.11.AXSME.a > addcon 1 10 50 1 m -slave 00000E1000001C008051B730FFFFFF010B180100.10.40master endpoint added successfullymaster endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.50In the following two examples, the connection works with default values of SCR, MCR derived from the PCR value specified using lpcr and rpcr keywords. Defaults applied for the connection can be viewed by using the dspchan command.
MGX8850.1.11.AXSME.a > addcon 1 10 40 1 sslave endpoint added successfullyslave endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.40MGX8850.1.11.AXSME.a > addcon 1 10 50 1 m -slave 00000E1000001C008051B730FFFFFF010B180100.10.40 -lpcr 1000 -rpcr 1000master endpoint added successfullymaster endpoint id : 00000E1000001C008051B730FFFFFF010B180100.10.50addfdr
Add Feeder—AXSM, AXSM-E
Adds a feeder node connection to the specified port (ifNum). The interface numbers of active ports are displayed in the dspports command report. LMI is up by default when you use addfdr.
Note
When adding a feeder node, the following conditions apply:
•
•
•
•
For more detailed information on configuring a feeder, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4 .
Syntax
addfdr <ifNum>
Syntax Description
Related Commands
delfdr, dspfdr, dspfdrs
Attributes
Example
MGX8850.1.AXSM.a > addfdr 1addimagrp
Add IMA Group—AXSM-32-T1E1-E
Creates and configures a new IMA Group.
Syntax
addimagrp <group> <version> <minLinks> <txImaId> <txFrameLen>
<txclkMode> <diffDelayMax>Syntax Description
