MGX 8850 Installation and Configuration, Release 1.1.0 - Card and Service Configuration
[Cisco MGX 8800 Series Switches] - Cisco
MGX 8850 Installation and Configuration, Release 1.1.0
Book Contents
Book Contents
Available Languages
Download Options
Book Title
MGX 8850 Installation and Configuration, Release 1.1.0
Chapter Title
Card and Service Configuration
View with Adobe Reader on a variety of devices
Chapter: Card and Service Configuration
Chapter Contents
Card and Service Configuration
This chapter describes how to configure the MGX 8850 cards and the services they support. Although the presumption for this chapter is that a plan exists for your network, it reviews some of the information that supports network planning. Generic instructions for inserting and removing cards appear in &
The services and applicable modules described in this chapter are:
oPhysical and logical configuration of a broadband interface on the Processor Switching Module (PXM) and, for a stand-alone switch, connection addition
oATM service on the MGX-AUSM/B
oFrame Relay service on the following service modules:
MGX-FRSM-2CT3
MGX-FRSM-2T3E3
MGX-FRSM-HS2
MGX-FRSM-HS1/B
AX-FRSM-8T1 and AX-FRSM-8E1
oCircuit emulation service on the MGX-CESM-8T1 and MGX-CESM-8E1
oRedundancy and bulk distribution on the Service Resource Module-3T3 (MGX-SRM-3T3/B)
Note&&&For information on the Route Processor Module (RPM), see the Cisco Route Processor Module Installation and Configuration Guide.
This section contains a general description of the sequence of tasks for configuring the cards and their services. It also contains details on how to configure resource partitions and add local connections and three-segment connections. Detailed descriptions of these tasks for individual cards appear in subsequent sections.
A resource partition at the card level consists of a number of logical connections (LCNs). At the port level, a resource partition consists of a percentage of bandwidth, a DLCI or VPI/VCI range, and the number of logical connection numbers (LCNs) available to a network control application. On the PXM, the connections are global logical connections (GLCNs). By default, all resources on a a card or logical port are available to any controller on a first-come, first-served basis. If necessary, you can modify the resource partitioning at the card level or logical port level. Port-level resource modification follows card-level modification, so the available port-level resources depend on whether and how much you change the card-level resource partitioing. You do not have to change the resource partitioning for the card before changing resource partitioning for a port.
The current network control application is Portable AutoRoute (PAR). Planning considerations should include the possibility of modifying the partitioning of resources for the interface. For example, the MGX 8850 switch has the capacity to support a Cisco Multi-Protocol Label Switching (MPLS) controller or a Private Network to Network Interface (PNNI) controller.
In a new switch, the common approach is to configure the same aspect for all cards at once—adding logical ports to all applicable cards, for example. In contrast, the likely sequence for installing a single card is to begin with its card-level features and continue until you have configured every connection. The common tasks for a new switch are:
1 Optionally configure the service modules (except the RPM) for redundancy. This card-level operation requires redundant cards and possibly an MGX-SRM-3T3/B.
2 Optionally configure resource partitioning for the whole card if the default partitioning does not fulfill the purpose of the card.
3 Activate physical lines.
4 Configure the line if default parameters are not appropriate.
5 Create the logical ports then modify them as needed.
6 Optionally configure resource partitions for a logical port if the default partitioning does not support the intended operation of the port.
7 Add connections then modify them as needed.
This section describes the rules for adding local connections, three-segment connections, and management connections. The MGX 8850 switch can support:
oLocal-only, digital access and cross-connect (DAX) connections
oThree-segment connections across an ATM or Frame Relay network
oIP management connections (stand-alone switches only)
A management connection is an inband IP connection that lets a workstation control a local or remote MGX 8850 switch through a service module rather than the Ethernet port on a PXM-UI. Although the rules include references to CLI syntax, they also apply to the Cisco WAN Manager application.
A DAX con is a connection whose endpoints for the entire connection exist on the same switch. The following apply to the MGX 8850 switch:
1 On a feeder, a DAX con can exist between different service modules or the same service module.
2 A stand-alone node supports DAX cons with one or both endpoints on the PXM in addition to DAX cons between service modules.
3 Either endpoint can be the master.
4 The first endpoint to add is the slave. The generic syntax is:
addcon &local parameters&
where local parameters are the port, DLCI or VPI and VCI, and mastership status. Slave is the default case, so you actually do not explicitly have to specify it. When you press Return, the system returns a connection identifier. The identifier includes the port and DLCI or VPI and VCI.
Use the identifier to specify the slave endpoint when you subsequently add the connection at the master end. The slave endpoint is specified as the remote parameters in item .
5 To complete the DAX con, add the master endpoint. The generic syntax is
addcon &local parameters& &remote parameters&
where local parameters are the port, DLCI or VPI and VCI, and mastership status (master in this case). The remote parameters are the items in the connection identifier that the system returned when you added the slave endpoint.
6 If the endpoint is a PXM port in a stand-alone node, specify the slot as 0. The addcon command is the only command in which you specify the slot number for the PXM as 0.
A three-segment connection consists of a local segment on each MGX 8850 switch at the edges of the network cloud and a middle segment across the network cloud. The MGX 8850 requirements are:
1 For MGX 8850 feeders, the backbone must consist of BPX 8600-series switches.
2 For MGX 8850 stand-alone switches, the backbone switches can be either BPX 8600-series switches or switches from another manufacturer.
3 On a feeder, the local segment exists between a service module and the PXM.
4 On a stand-alone node, the local segment can be between a service module and a port on the PXM or just two ports on the PXM.
5 For the local segment, add the connection at only the master endpoint. The generic syntax is:
addcon &local parameters& &remote parameters&
where local parameters are the port, DLCI or VPI and VCI, and mastership status (master in this case). The remote parameters are the current nodename, slot, port, and VPI and VCI of the slave end. For the PXM endpoints, specify the slot number as 0. The addcon command is the only command in which you specify the slot number for the PXM as 0.
This section describes the requirements for adding an inband ATM PVC for managing an MGX 8850 stand-alone node. A management connection lets a workstation connected through a router control either the local MGX 8850 node or a remote MGX 8850 node that has no workstation. The typical configuration has the connecting router feed an AUSM/B, FRSM, RPM, or PXM UNI port.
A management connection can be either a DAX con or a three-segment connection. The maximum number of management connections is eight. The DAX con exists between a service module or PXM UNI and port 34 of the local PXM. PXM port 34 is a reserved port for management connections on a stand-alone node. The network in
shows FRSMs in a feeder application.
A three-segment management connection has a:
1 Local segment between a near-end service module or PXM UNI and a PXM port in the range 1-32.
2 Middle segment across the network cloud.
3 Local segment between a remote PXM port in the range 1-32 and port 34 of that same PXM.
The path from &A& to &B& in
consists of three segments. A segment exists between the FRSM and the PXM on each MGX 8850 switch. The middle segment exists between the BXMs at the edges of the ATM cloud and may traverse BPX 8600 via nodes in the cloud. The VPI and VCI at each BPX8600-series switch connected to an MGX 8850 feeder must match the VPI and VCI on the slave endpoint of the connected PXM. The VPIs and VCIs at the endpoints of the middle segment do not have to match. If you use the CLI rather than the Cisco WAN Manager application, add each segment through the CLI at each switch.
Figure&6-1 Frame Relay Connection Through an MGX 8850-BPX 8600-Series Network
This section first describes how to activate and configure the card-level parameters, lines, and ports on the PXM uplink card then describes how to add connections to the PXM in a stand-alone node. The descriptions tell you how to:
oOptionally modify the resource partitioning at the card level.
oActivate a line on the uplink card. On a stand-alone node, you can activate more than one line if the uplink card has multiple lines. One physical line must be the trunk to a network routing node.
oIf the switch has a pair of SRMs for bulk distribution and you use the CLI rather than the CiscoView application, activate the SRM lines from the PXM.
oOptionally modify the resource partitioning at the port level.
oCreate logical ports.
oOn a stand-alone node, specify the cell header type. UNI cell headers typically apply where a workstation connects to a UNI port on the uplink card rather than a port on the PXM-UI card. Such an implementation is not common.
oOn a stand-alone node, add standard connections and optional management connections.
oOn a stand-alone node, configure Automatic Protection Switching (APS).
oFor a feeder, execute steps on the connected BPX 8600-series switch to make the feeder an available resource in the network.
Note&&&For a description of the bit error rate test (BERT) functions, see the section titled &.&
This section describes how to configure card-level features, activate a physical line, and configure logical elements such as a port. If necessary, refer to the section titled && for background information on these types of tasks.
Step&1 Optionally, you can modify the resource partitioning for the whole card by executing cnfcdrscprtn. You can view resource partitioning through dspcdrscprtn.
cnfcdrscprtn &number_PAR_conns& &number_PNNI_conns& &number_TAG_conns&
onumber_PAR_conns is the number of connections in the range 0-32767 for PAR.
onumber_PNNI_conns is the number in the range 0-32767 available to PNNI.
onumber_TAG_conns is the number of connections in the range 0-32767 for MPLS.
For example, you could reserve 10,000 connections for each controller on the PXM with:
cnfcdrscprtn
Step&2 Activate a line by executing addln:
addln -ds3 &slot.line& | -e3 &slot.line& | -sonet &slot.line&
o-ds3 indicates a T3 line parameter follows.
o-e3 indicates an E3 line parameter follows.
o-sonet indicates an OC-3 or OC-12 line parameter follows.
oslot is 7 or 8 for the PXM. If the switch has a single of redundant pair of SRMs, execute addln for slots 15, 16, 31, and 32.
oline has the range 1-4 but depends on the number of lines on the back card.
For a feeder, you can activate only one line. For a stand-alone, you can activate more than one line if the back card has multiple lines. One line must serve as the trunk to the ATM network. With an OC-3, T3, or E3 card, remaining lines can serve as UNI ports to CPE.
Step&3 If necessary, modify the characteristics of a line by using cnfln.
Step&4 Configure logical ports for the physical line by executing addport. Execute addport once for each logical port. Related commands are cnfport, dspports, and delport.
addport &port_num& &line_num& &pct_bw& &min_vpi& &max_vpi&
oport_num is the number for the logical port. The range is 1-32 for user-ports or 34 for inband ATM PVCs that serve as management connections.
oline_num is the line number in the range 1-4 but depends on the type of uplink card.
opct_bw is the percentage of bandwidth. The range is 0-100. This parameter applies to both ingress and egress.
omin_vpi is the minimum VPI value. On a feeder, the range is 0-4095. On a stand-alone node, the range is 0-255.
omax_vpi is the maximum VPI value. On a feeder, the range is 0-4095. On a stand-alone node, the range is 0-255.
Using an example of 100% of the bandwidth on one logical port 1:
addport 1 1 100 1 200
where the first &1& is the the second &1& is the line number on the PXM back card to which you are assigning this &100& is the percentage of bandwidth this port ha and the VPI range is 1-200.
Step&5 If necessary, use cnfportrscprtn to modify port-level resources for a controller:
cnfportrscprtn &port_no& &controller& &ingress_%BW& &egress_%BW&
o&min_VPI& &max_VPI& &min_VCI& &max_VCI& &max_GLCNs&
oport_no is the logical port number in the range 1-32 for user-connections or 34 for inband ATM PVCs for network management.
ocontroller is a string identifying the network controller—&PAR,& &PNNI,& or &TAG.&
oingress_%BW is the percentage of ingress bandwidth in the range 0-100.
oegress_%BW is the percentage of egress bandwidth in the range 0-100.
omin_vpi is the minimum VPI in the range 0-4095.
omax_vpi is the maximum VPI in the range 0-4095.
omin_vci is the minimum VCI in the range 0-65535.
omax_vci is the maximum VCI in the range 0-65535.
omax_chans is the maximum GLCNS in the range 0-32767.
Step&6 On a stand-alone node, specify the cell header type as needed by executing cnfatmln.
cnfatmln &line_num& &type&
oline_num is the line number in the range 1-4.
otype is either 2 for UNI or 3 for NNI (the default).
UNI cell headers typically apply where a workstation connects through a line to a PXM UNI port (rather than a SLIP-based port on the PXM-UI card). Such an implementation is not common, so cnfatmln usually is not necessary.
Automatic Protection Switching (APS) provides redundancy for an OC-3 or OC-12 line on the PXM if a failure occurs someplace other than the PXM front card. The failure can originate on the daughter card, uplink card, or any part of the physical line. With APS, the active PXM remains active and passes the cells from the failed line-path through the redundant line. The advantage of APS is that a line switchover requires significantly less time than a full PXM switchover. (A failure of the PXM front card in a redundant system causes the entire PXM card set to switch over.) As defined in GR-253, a variety of APS modalities are possible (see the command summaries that follow).
The current requirements for APS service on an MGX 8850 switch are:
oRedundant PXMs (currently, the PXM does not support an APS configuration where the working and protection lines on the same uplink card).
oA &B& version of an OC-3 or OC-12 back card (SMLR-1-622/B, and so on).
oThe connected network switch or CPE must also support APS.
Initial APS specification consists of the working and protection slot and line and the mode for APS. After the initial APS specification, you can configure additional APS parameters, give commands for switching lines, and display the APS configuration. The CiscoView application and CLI provide access to the APS feature. For detailed descriptions of the CLI commands, see the Cisco MGX 8850 Wide Area Edge Switch Command Reference. Note that APS is available for only the &B& versions of the SONET cards—SMLR-1-622/B, and so on. The applicable CLI commands are:
oaddapsln to specify the lines and mode for APS
ocnfapsln to modify the following details of APS operation:
oerror thresholds
owait period before the PXM restores the working line after errors clear
ounidirectional or bidirectional switchover, which specifies whether one or both directions of a line are switched when the criteria for a hard or soft failure are met for one direction
orevertive recovery, where the working line automatically returns to operation after errors clear and any wait period has elapsed
oenable use of K1 and K2 bytes in the line-level frame for equipment at both ends to exchange APS-related information
odelapsln to delete the APS configuration
odspapsln to display the configuration for an APS-configured line
oswitchapsln to issue commands for line switching that:
oclear previous user requests
olock out (block) line switching
omanually switch to the protection line if the following are true: no errors exist, the working line is active, and your request has an equal or higher priority than the last switch request.
oforce a line switch regardless of existing errors the following are true: the working line is active and your request has an equal or higher priority than the last switch request.
oswitch all traffic to either the working lines or protection lines so you can remove a card (applies to only the currently supported configuration of 1+1 mode on two uplink cards)
To specify APS, use the following syntax:
addapsln &workline& &workingslot& &protectionline& &protectionslot& &archmode&
where workline and workingslot identify the line and slot of the APS working line, and protectionline and protectionslot identify the protection line and slot. According to GR-253, the archmode identifies the type of APS operation. The mode definition includes:
1 1+1 on one back card
2 1+1 on two back cards
Currently, the only supported mode is 1+1 with two uplink cards (mode=2). With 1+1 APS, both the working line and the protection line carry duplicate data even though no error threshold has been exceeded or line break has occurred. This mode requires that two standard cables (rather than a Y-cable) connect at two ports on the equipment at the opposite end. With the two-card implementation, workline must be the same as protectionline.
This section describes the CLI commands for provisioning connections on a PXM in a stand-alone node. Connection addition abides by the rules for a standard connection or a management connection in the form of either a three-segment connection or a DAX con. See && earlier in this chapter. In addition this section describes the commands for modifying certain features for a connection and policing connections by way of usage parameter control.
The CLI commands correspond to functions in the Cisco WAN Manager application. The preferred CLI command is addcon. (If the application requires NSAP addressing, use addchan to add the connection and cnfchan if you need to modify it. Refer to the command reference for the syntax.) In addition, On the PXM CLI:
Step&1 Execute the addcon command according to the following syntax:
addcon &port_num& &conn_type& &local_VPI& &local_VCI& &service& [CAC] [mastership] [remoteConnId]
oport_no is the logical port in the range 1-32 for a user connection or 34 for management connection.
oconn_type is a number identifying the connection type—1 for VPC or 2 for VCC.
olocal_VPI is the local VPI in the range 0-4095.
olocal_VCI is the local VCI in the range 0-65535.
oservice is a number in the range 1-4 to specify the type of service: 1=CBR, 2=VBR, 3=ABR, and 4=UBR.
oCAC optionally lets you turn off the addition of the loading affect of a connection to the aggregated load on a port.
omastership specifies whether the endpoint you are adding is the master or slave. 1=master. 2=slave (default). The syntax shows this parameter as optional because you need to enter it at only the master end. Slave is the default, so you do not explicitly need to specify it when entering a DAX con.
oremoteConnId identifies the connection at the slave end. The format for remoteConnId is Remote_nodename.slot_num.remote_VPI.remoteVCI. Note that the slot number of the active PXM is always 0 when you add a connection because the PXM slot number is a fixed, logical value.
Step&2 If necessary, modify a connection by using cnfcon:
cnfcon &conn_ID& &route_priority& &max_cost& &restrict_trunk_type& [CAC]
oconn_ID identifies the connection. The format is logical_port.VPI.VCI.
oroute_priority is the priority of the connection for re-routing. The range is 1-15 and is meaningful only in relation to the priority of other connections.
omax_cost is a number establishing the maximum cost of the connection route. The range is 1-255 and is meaningful only in relation to the cost of other connections for which you specify a maximum cost.
orestrict_trunk_type is a number that specifies the type of trunk this connection can traverse. The numbers are 1 for no restriction, 2 for terrestrial trunk only, and 3 for satellite trunk only.
oCAC optionally lets you turn on or off the addition of the loading affect of a connection to the aggregated load on a port.
Step&3 As needed, specify usage parameter control according to the connection type. Use either cnfupccbr, cnfupcvbr, cnfupcabr, or cnfupcubr. The following text lists the parameters for each. Note that the parameters for cnfupcvbr and cnfupcabr are the same. Also, the polType (policing type) parameter has numerous variations in accordance with ATM Forum v4.0. For a list of the policing variations, see
after the syntax descriptions.
cnfupccbr &conn_ID& &polType& &pcr[0+1]& &cdvt[0+1]& &IngPcUtil& &EgSrvRate& &EgPcUtil&
oconn_ID identifies the connection. The format is port.vpi.vci.
opolType is the policing type. The choices are 4 or 5. See
for a description of these types.
opcr is the peak call rate in the range 50-1412832 cps.
ocdvt is the cell delay variation tolerance in the range 1-5000000 microseconds.
oIngPcUtil is the percentage of utilization on the ingress. The range is 1-100.
oEgSrvRate is the egress service rate. The range is 50-1412832 cps.
oEgPcUtil is the percentage of utilization on the egress. The range is 1-100.
cnfupcvbr or cnfupcabr &conn_ID& &polType& &pcr[0+1] & cdvt[0+1]& &scr& &mbs& &IngPcUtil& &EgSrvRate& &EgPcUtil&
oconn_ID identifies the connection. The format is port.vpi.vci.
opolType is the policing type in the range 1- 5. See
for a list of these types.
opcr is the peak call rate in the range 50-1412832 cps.
ocdvt is the cell delay variation tolerance in the range 1-5000000 microseconds.
oscr is the sustained cell rate. The range is 50-1412832 cps.
ombs is the maximum burst size. The range is 1-5000000 cells.
oIngPcUtil is the percentage of utilization on the ingress. The range is 1-100.
oEgSrvRate is the egress service rate. The range is 50-1412832 cps.
oEgPcUtil is the percentage of utilization on the egress. The range is 1-100.
cnfupcubr &conn_ID& &polType& &pcr[0+1] & cdvt[0+1]& &IngPcUtil&
oconn_ID identifies the connection. The format is port.vpi.vci.
opolType is the policing type. The range is 3- 5. See
for a list of these types.
opcr is the peak call rate in the range 50-1412832 cps.
ocdvt is the cell delay variation tolerance in the range 1-5000000 microseconds.
oIngPcUtil is the percentage of utilization on the ingress. The range is 1-100.
Table&6-1 Policing Definitions According to Policing and Connection Type
(PCR Policing only)
When policing = 5 (off)
when CLP setting = no
when CLP setting = yes
Policing is off
(when Policing = 4)
Policing is off
The eight-port ATM Universal Service Module (MGX-AUSM/B-8T1 and MGX-AUSM/B-E1) is a multipurpose card set with eight T1 or E1 lines that support:
oATM UNI with high port-density for the CPE—with AUSMs in all 24 service module slots, an MGX 8850 switch can support up to 192 individual T1 or E1 lines. An individual card set can support 1000 data connections and 16 management connections.
oInverse multiplexing for ATM (IMA) that complies with ATM Forum v3.0 and v3.1—the 8-port AUSM can provide N x T1 or N x E1 logical ports up to maximum rates of 12 Mbps for T1 or 16 Mbps for E1.
oClasses of service—CBR, VBR, ABR, and UBR with per-VC queuing on ingress and multiple class-of-service queues on egress.
oStatistics collection.
oVirtual path connections (VPCs).
oNetwork synchronization derived from one of its lines.
oBit error rate test (BERT) functionality with loopback pattern generation and verification on individual lines or logical port. For a description of the BERT functions, see the section titled &.&
o1:N redundancy for through the optional MGX-SRM-3T3/B card.
oAutomatic card-restore.
oSNMP and TFTP to support card and connection management.
oResource partitions for individual network control applications.
You can activate and configure the card, the lines, and the ports on the AUSM-series cards through the CiscoView application or the CLI. To perform connection-related tasks, use the Cisco WAN Manager application or the CLI. Refer to the documentation for these applications for task descriptions. Use the commands described in this section to:
oOptionally modify resource partitioning at the card-level
oActivate and configure a line
oCreate and configure a logical port
oOptionally modify resource partitioning at the port-level
oConfigure usage parameters
oConfigure queue depths
oConfigure the ForeSight feature
oConfigure a line as a clock source
On the CLI of the AUSM/B:
Step&1 If necessary, modify the resource partitioning for the whole card by executing the cnfcdrscprtn command. You can view resource partitioning through dspcdrscprtn.
cnfcdrscprtn &number_PAR_conns | number_PNNI_conns | number_TAG_conns&
onumber_PAR_conns is the number of connections in the range 0-1000 for PAR.
onumber_PNNI_conns is the number of connections in the range 0-1000 for PNNI.
onumber_TAG_conns is the number of connections in the range 0-1000 for MPLS.
For example, you could reserve 300 connections for each controller on the AUSM with:
cnfcdrscprtn 300 300 300
Step&2 Activate a physical line by using addln for each of the eight lines as needed:
addln &line_number&
Step&3 Optionally, use the cnfln command to specify line coding, line length, and clock source:
cnfln &line_num& &line_code& &line_len& &clk_src& [E1-signaling]
Step&4 Execute upport to activate the logical operation of the line:
upport &port_number&, where port_number is in the range 1-8.
Step&5 If necessary, execute cnfportq to modify the egress queues:
cnfportq &port_num& &q_num& &q_algo& &q_depth& &clp_high& &clp_low& &efci_thres&
is the logical port number in the range 1-8.
is the queue number in the range 1-16. 0 is the default for addchan.
1=CBR2=VBR3=ABR4=UBR
is a number to specify the queue algorithm:
0=disable queue1=high priority—always serve2=best available3=minimum guaranteed bandwidth4=minimum guaranteed bandwidth with maximum rate shaping5=CBR with smoothing
is the maximum queue depth in the range 1-16000 cells.
is the high cell loss priority in the range 1-16000 cells.
is the low cell loss priority in the range 1-16000 cells.
efci_thres
is the EFCI threshold in the range 1-16000 cells.
Step&6 If necessary, configure resources at the port level by executing cnfportrscprtn. Use dspportrscprtn to see the current resource partitioning.
cnfportrscprtn &port_num& &controller& &ingress_%BW& &egress_%BW& &number_of_cons& &VPImin/VPImax& [VCImin/VCImax]
oport_num is the port number in the range 1-8.
ocontroller is a number representing the controller: 1=PAR, 2=PNNI, and 3=MPLS.
oingress_%BW is the percentage of ingress bandwidth in the range 0-100.
oegress_%BW is the percentage of egress bandwidth in the range 0-100.
onumber_of_cons is the maximum number of connections on the port.
oVPImin/VPImax is the minimum and maximum VPI numbers.
oVCImin/VCImax is the optional specification for VCI range.
The command sequence for configuring the IMA feature:
Step&1 addln on all constituent links.
Step&2 cnfln if necessary.
Step&3 addimagrp (or addaimgrp) to create the IMA group by using the following syntax:
addimagrp &group_num& &port_type& &list_of_links& &minNumLink&
is a number for IMA group. The range is 1-8.
is the port type: 1=UNI, 2=NN1.
list_of_links
is the list of links to be included in the group. Separate each link number by a period.
minNumLink
is the minimum number of links in the range 1-8 to form a group.
For example: the following creates IMA group 1 with lines 3, 4, and 5. The minimum is 3.
addimagrp 1 3.4.5 3
IMA-related commands are dspimagrp, dspimagrpcnt, dspimagrps, dspimainfo, and dspimalncnt. Refer to the Cisco MGX 8850 Wide Area Edge Switch Command Reference for descriptions.
You can add and modify connections through the Cisco WAN Manager or the CLI. Refer to applicable documentation if you use the WAN Manager application. This section describes how to add an ATM connection through the CLI according to the rules for adding a standard connection or a management connection in the form of either a DAX con or a three-segment connection. See && earlier in this chapter.
On the CLI of the AUSM/B:
Step&1 Execute the addcon command.
When you add a connection with addcon, the system automatically assigns the next available channel number, so addcon does not require it. However, some related commands require a channel number—cnfchanfst, cnfchanq, and cnfupcabr, for example. To see the channel number after you add a connection, use dspcons.
The addcon syntax is:
addcon &port_number& &vpi& &vci& &ConType& &SrvType& [Controller_Type] [mastership] [remoteConnID]
port number
port number is in the range 1-8.
vpi has a value in the range 0-255.
vci can be in the range 0-65535 for a VCC or * for a VPC.
is the connection type: 0=VCC, and non-0 is the local ID of a VPC in the range 1-1000.
Service Type
is the service type: 1=CBR, 2=VBR, 3=ABR, and 4=UBR.
mastership
is the mastership status of the endpoint. 1=master, and 2=slave. The default is slave, so you actually do not need to type a 2.
Controller_Type
is the optional controller specification. 1=PAR (the default}. 2=SPVC (PNNI).
is entered at only the master end and consists of the node name, slot number, port number, vci, and vpi of the slave end.
Step&2 To configure usage parameter control (UPC) for the connection (channel), use cnfupccbr, cnfupcvbr, cnfupcabr, or cnfupcubr. Use dspcons to obtain the channel number.
cnfupccbr &port.vpi.vci& &enable/disable& &pcr[0+1]& &cdvt[0+1]& &IngPcUtil& &EgSrvRate& &EgPcUtil&
port.vpi.vci
identifies the connection.
enable/disable
is the UPC enable: 1=disable, 2=enable.
is the peak cell rate. Without IMA, the range is as follows:
T1, 10-3622 cells per secondE1, 10-4528 cells per secondclear E1, 10-4830 cells per second
For IMA, multiply the line rate by the number of links.
is the cell delay variation tolerance for cells with CLP=0 and CLP=1. The range is 1-250000 micro seconds.
is the percent utilization on the ingress. The range is 1-127. The default is 0.
is the egress service rate. Without IMA, the range is as follows:
T1, 10-3622 cells per secondE1, 10-4528 cells per secondclear E1, 10-4830 cells per second
For IMA, multiply the line rate by the number of links.
is the percent utilization on the egress. The range is 1-127. The default is 0.
cnfupcvbr has the same syntax and parameters as cnfupcabr
cnfupcvbr or cnfupcabr &port.vpi.vci& &enable& &pcr[0+1]& &cdvt[0+1]& &scr& &scr_police& &mbs& &IngPcUtil& &EgSrvRate& &EgPcUtil& &clp_tag&
port.vpi.vci
identifies the connection.
is the enabled/disable for UPC: 1=Disable, 2=Enable.
is the peak cell rate. Without IMA, the range is as follows:
T1, 10-3622 cells per secondE1, 10-4528 cells per secondclear E1, 10-4830 cells per second
For IMA, multiply the line rate by the number of links.
cdvt[0+1] is the cell delay variation tolerance for cells with CLP=[0+1]. The range is 1-250000 micro seconds.
is the peak cell rate. Without IMA, the range is as follows:
T1, 10-3622 cells per secondE1, 10-4528 cells per secondclear E1, 10-4830 cells per second
For IMA, multiply the line rate by the number of links.
scr_police
specifies the type of scr policing: 1= CLP[0] cells, 2=CLP[0+1] cells, and 3=no SCR policing.
is the maximum burst size: the range is 1-5000 cells.
is the percent utilization on the egress. The range is 1-127. The default is 0.
is the egress service rate. Without IMA, the range is as follows:
T1, 10-3622E1, 10-4528clear E1, 10-4830
For IMA, multiply the line rate by the number of links.
is the percent utilization on the ingress. The range is 1-127. The default is 0.
is the enable for CLP tagging: 1=disable, 2=enable.
cnfupcubr &port.vpi.vci& &enable& &pcr[0+1]& &cdvt[0+1]& &IngPc& &util& &clp_tag&
port.vpi.vci
identifies the connection.
is the enabled/disable for UPC: 1=Disable, 2=Enable.
is the peak cell rate. Without IMA, the range is:
T1, 10-3622E1, 10-4528clear E1, 10-4830
For IMA, multiply the line rate by the number of links.
cdvt[0+1] is the cell delay variation tolerance for cells with CLP=[0+1]. The range is 1-250000 micro seconds.
is the peak cell rate. Without IMA, the range is:
T1, 10-3622E1, 10-4528clear E1, 10-4830
For IMA, multiply the line rate by the number of links.
scr_police
specifies the type of scr policing: 1= CLP[0] Cells, 2=CLP[0+1] cells, and 3=no SCR policing.
is the maximum burst size: the range is 1-5000 cells.
is the percent utilization on the ingress. The range is 1-127. The default is 0.
is the enable for CLP tagging: 1=disable, 2=enable.
Step&3 If the system has the ForeSight feature, use cnfchanfst to configure it.
cnfchanfst &port.vpi.vci& &enable& &fgcra_enable& &ibs& &pcr& &mcr& &icr&
port.vpi.vci
identifies the connection.
is the enabled/disable for the ForeSight feature: 1=disable, 2=enable.
fgcra_enable
is the enabled/disable for the frame-based generic cell rate algorithm: 1=disable, 2=enable.
is the initial burst size in the range 0-5000 cells.
is the peak cell rate. Without IMA, the range is:
T1, 10-3622E1, 10-4528clear E1, 10-4830
For IMA, multiply the line rate by the number of links.
is the minimum cell rate. Without IMA, the range is:
T1, 0-3622E1, 0-4528clear E1, 0-4830
For IMA, multiply the line rate by the number of links.
is the initial cell rate. Without IMA, the range is as follows:
T1, 0-3622E1, 0-4528clear E1, 0-4830
For IMA, multiply the line rate by the number of links.
Step&4 If necessary, change the queue depths by using cnfchanq.
cnfchanq &port.vpi.vci& &discard_option& &vc_q_depth& &clp_thresh_high& &clp_thresh_low | epd_threshold& &efci_thresh&
port.vpi.vci
identifies the connection.
discard_option
is either 1 for CLP hysteresis or 2 for frame-based.
vc_q_depth
is the ingress queue depth in the range 1-16000 cells.
clp_thresh_high
is the CLP high threshold in the range 1-16000 cells.
clp_thresh_low
epd_threshold
is the CLP low threshold in the range 1-16000 cells for CLP hysteresis-based discard.
is the EPD threshold in the range 1-16000 cells frame-based discard.
efci_thresh
is the EFCI threshold in the range 1-16000 cells.
For the middle segment, be sure to use the connection type as the local segments on the MGX 8850 node (CBR, VBR, ABR, or UBR). The parameters directly map from those specified at the connection endpoint.
This section describes the features available on each of the Frame Service Modules (FRSMs). For descriptions of how to set up these cards and add connections, see the subsequent section titled &.& This section consists of:
oBrief descriptions of each model of the FRSM
oLists of features shared by all FRSMs
oLists of features for individual models of the FRSM
oBrief descriptions of the services
The primary function of the FRSM is to convert between the Frame Relay-formatted data and ATM/AAL5 cell-formatted data. For an individual connection, you can configure network interworking (NIW), service interworking (SIW), ATM to Frame Relay UNI (FUNI), or frame forwarding. An FRSM converts the header format and translates the address for:
oFrame Relay port number and DLCI
oATM-Frame UNI (FUNI) port number and frame address or frame forwarding port
oATM virtual connection identifier (VPI/VCI)
The models of the FRSM include eight-port T1 and E1 cards and very high-speed modules. Higher speed modules support unchannelized E3 and HSSI as well as channelized and unchannelized T3.
The Very High Speed Frame Service Modules (FRSM-VHS) support Frame Relay services on T3, E3, and HSSI interfaces. Up to 24 FRSM-VHS cards in any combination can operate in the switch. They should occupy upper slots whenever possible. The FRSM-VHS group on an MGX 8850 node consists of the:
oMGX-FRSM-2CT3, which provides channelized Frame Relay service for up to 1000 user connections over two T3 lines on the BNC-2T3 back card (or line module).
oMGX-FRSM-2T3E3, which provides unchannelized (clear-channel) Frame Relay service for up to 1000 user connections over two T3 lines (44.736 Mbps each) or two E3 lines (34.368 Mbps each) on a BNC-2T3 or BNC-2E3 back card. The MGX-FRSM-2T3E3 can also support subrate T3 or E3 for tiered DS3 on each physical port.
oMGX-FRSM-HS2, which provides unchannelized Frame Relay service for up to 1000 user-connections over two HSSI lines on the SCSI2-2HSSI back card. The maximum rate for the card is 70 Mbps. Each port can operate either as DTE or DCE with incremental rates of NxT1 or NxE1 up to 52 Mbps.
The AX-FRSM-8T1 and AX-FRSM-8E1 provide unchannelized Frame Relay service for up to 1000 user-connections on 8 T1 or E1 lines. The AX-FRSM-8T1c and AX-FRSM-8E1c provide channelized Frame Relay service for up to 1000 connections.
The MGX-FRSM-HS1/B provides unchannelized Frame Relay service across four V.35 lines. The maximum throughput for the card is 16 Mbps. The maximum rate on a line is 8 Mbps. Without the cost of a T3 or E3 card, the MGX-FRSM-HS1/B provides greater that T1 or E1 speeds on a port as well as a choice of 50 line rates in the range 48 Kbps-8 Mbps.
This section first lists the features common to all FRSM models then lists the features of each model. All FRSMs support:
oFrame Relay-to-ATM Network Interworking (NIW) as defined in FRF.5.
oFrame Relay-to-ATM Service Interworking (SIW) with or without translation as in FRF.8.
oFrame forwarding.
oATM Frame-UNI.
oMaximum frame sizes of 4510 bytes for Frame Relay and 4096 bytes for ATM-FUNI.
oPer-virtual-circuit (VC) queuing in the ingress direction (towards the Cellbus). Traffic arriving at the network on a connection has a dynamically assigned buffer at the entrance to the switch. Buffer size depends on the amount of traffic and the service-level agreement (SLA).
oAdvanced buffer management. When a frame arrives, the depth of the queue for the LCN is compared against the peak queue depth scaled down by a specified factor. The scale-down factor depends on the amount of congestion in the free buffer pool. As the free buffer pool begins to empty, the scale-down factor is increased, preventing an excessive number of buffers from being held up by any single LCN.
oMultiple, priority-level queuing to support class of service on the egress. The FRSM services egress queues according to a weighted priority. The priority depends on the percentage of logical port bandwidth needed by all connections of a particular type on a port. The FRSM supports a:
oHigh-priority queue
oReal-time Variable Bit Rate (rt-VBR) queue
oCommon queue for non-real-time Variable Bit Rate (nrt-VBR) and ABR connections
oUBR queue
oInitial burst per channel. After a period of silence, the FRSM sends a configurable number of bytes at a peak service rate.
oThe ForeSight option. This Cisco mechanism for managing congestion and optimizing bandwidth continuously monitors the utilization of ATM trunks. It proactively adjusts the bandwidth for connections to avoid queuing delays and cell discards.
oConsolidated Link Layer Management (CLLM), an out-of-band mechanism to transport congestion related information to the far end.
oDual leaky bucket policing. Within the basic parameters such as committed burst, excess burst, and CIR, incoming frames go into two buckets: those to be checked for compliance with the committed burst rate and those to be checked for compliance with the excess burst rate. Frames that overflow the first bucket go into the second bucket. The buckets &leak& by a certain amount to allow for policing without disruption or delay of service.
oStandards-based management tools. Each FRSM supports SNMP, TFTP for configuration and statistics collection, and a command line interface. The Cisco WAN Manager application provides full graphical user interface support for connection management. The CiscoView application provides equipment management.
oMGX 8800-series network management functions, including image download, configuration upload, statistics, telnet, UI, SNMP, trap, and MIBs.
oOAM features: OAM F5 AIS, RDI, end-to-end or segment loopback as well as LMI and Enhanced LMI (ANNEX A, ANNEX D, Strata LMI).
oHot swappable redundancy (see sections for individual FRSM card types).
oCLLM (router ForeSight and NNI ForeSight operation).
oResource partitioning at the card level or port level.
oBit error rate test (BERT) functions for all card types except the HSSI card types. For a description of BERT on the MGX-FRSM-2T3E3, see the forthcoming section . Running a BERT session on an MGX-FRSM-2CT3 or an eight-port FRSM requires a set of MGX-SRM-3T3s in the system. For a description of BERT on these cards, see the section titled &.&
The specific features are:
oUp to 1000 user-connections
oTwo T3 lines
oUp to 256 logical ports
oLogical port speed from DS0 56 Kbps through DS1 1.536 Mbps
oSupport for five Class of Service (CoS) queues (high priority, rt-VBR, nrt-VBR, ABR, UBR)
o1:1 redundancy through Y-cable redundancy (no Service Resource Module required)
The specific features are:
oUp to 1000 user-connections
oTwo T3 or E3 lines coinciding with two logical ports
oADC Kentrox and Digital Link methods for supporting fractional T3 or E3 ports
oMaximum possible number of DLCIs per port by using the Q.922 two-octet header format
oSupport for five Class of Service (CoS) queues (high priority, rt-VBR, nrt-VBR, ABR, UBR)
o1:1 redundancy through Y-cable redundancy (no Service Resource Module required)
oFractional T3 speeds available through either the Digital Link or ADC Kentrox method
The specific features are:
oUp to 1000 user-connections
oMaximum 2 logical ports
oTwo HSSI lines with configurable line speeds in multiples of 56 Kbps or 64 Kbps
oSelectable DTE or DCE mode for each port
oIn DCE mode, per port clock speeds of NxT1 and NxE1 up to 52 Mbps
oVarious DTE/DCE loopback operations
oMaximum possible number of DLCIs per port by using the Q.922 two-octet header format.
o1:1 redundancy through a Y-cable
The specific features are:
oUp to 512 data connections
oIn addition to data connections, support for:
oLMI according to ITU-T Q.333 Annex A and ANSI T1.617 Annex D
oOAM messaging
oTotal card throughput of 16 Mbps
oMaximum of 8 Mbps per line
oChoice of DTE or DCE mode for each line
oA maximum frame size of 4510 bytes
oOne-to-one mapping between a logical port and a physical line
oSupport for metallic (internal) loopback (ITU-T type 1)
oSupport for ANSI/EIA/TIA-613-1993 and ANSI/EIA/TIA-612-1993
The specific features are:
oUp to 1000 user-connections.
oFractional FRSMs support a single 56-Kbps or multiple 64-Kbps user-ports (FR-UNI, FR-NNI, FUNI, and frame forwarding) per T1 or E1 line. Channelized FRSMs (AX-FRSM-8T1c and AX-FRSM-8E1c) support multiple 56 Kbps or N x 64 Kbps user-ports per line up to the physical line bandwidth limit.
oBulk distribution for T1 only through the MGX-SRM-3T3. See the && section in this chapter.
oRedundancy support: the MGX-SRM-3T3 can provide 1:N redundancy for T1 or E1 operation. If the FRSM uses an SMB-8E1 back card, 1:1 redundancy is also available through Y-cabling.
The following sections describe NIW, SIW, FUNI, and frame forwarding. Topics include translation and congestion management.
FR-ATM network interworking (NIW) supports a permanent virtual connection (PVC) between two Frame Relay users over a Cisco network or a multi-vendor network. The traffic crosses the network as ATM cells. To specify NIW for a connection, add the connection with a channel type of &network interworking.& For an illustration of a BPX 8620 network with NIW connections, see .
Figure&6-2 BPX 8620 Network with NIW Connections
In addition to frame-to-cell and DLCI-to-VPI/VCI conversion, the NIW feature maps cell loss priority (CLP) and congestion information from Frame Relay-to-ATM formats. Subsequent sections contain the details. You can modify the CLP and congestion indicators for individual connections.
You can modify the CLP and congestion indicators for individual connections. On the CLI., use the cnfchanmap command. In the Frame Relay-to-ATM direction, you can configure each Frame Relay-ATM NIW connection for one of the following CLP-to-DE mapping schemes:
oDE bit in the Frame Relay frame is mapped to the CLP bit of every ATM cell generated by the segmentation process.
oCLP is always 0.
oCLP is always 1.
In the ATM-to-Frame Relay direction, you can configure each Frame Relay/ATM NIW connection for one of the following CLP-to-DE mapping schemes:
oIf at least one ATM cell from a frame has CLP=1, the DE field of the Frame Relay frame is set.
oNo mapping from CLP to DE.
Congestion on the Frame Relay/ATM network interworking connection is flagged by the EFCI bit. The EFCI setting depends on the direction of the traffic. In the Frame Relay-to-ATM direction, EFCI is always set to 0. In the ATM-to-Frame Relay direction, the FECN bit of the Frame Relay frame is set if the EFCI field in the last received ATM cell of a segmented frame is set.
The management of ATM layer and FR PVC status management can operate independently. The PVC status from the ATM layer is used when determining the status of the FR PVC. However, no direct actions of mapping LMI A bit to OAM AIS is performed.
By specifying a service interworking (SIW) channel type when you add a Frame Relay PVC to an FRSM, all data is subject to SIW translation and mapping in both the Frame Relay-to-ATM and ATM-to-Frame Relay directions. A BPX 8620 network with SIW connections appears in .
Figure&6-3 BPX 8600-Series Network with SIW Connections
In , an MGX 8850 node on the right has three Frame Relay SIW connections terminating on an FRSM. Three far-end terminations for these connections appear in other parts of :
oATM FUNI (framed UNI) port on an FRSM
oATM UNI port on an RPM
oATM UNI port on a BPX 8600-series BXM card
In addition to frame-to-cell and DLCI-to-VPI/VCI conversion, SIW maps cell loss priority and congestion data between the Frame Relay and ATM formats and is FRF.8-compliant. It provides full support for routed and bridged PDUs, transparent and translation modes, and VP translation.
In addition to frame-to-cell and DLCI-to-VPI/VCI conversion, the SIW feature maps cell loss priority (CLP) and congestion information from Frame Relay-to-ATM formats.
You can modify the CLP and congestion indicators for individual connections. On the CLI., use the cnfchanmap command. In the Frame Relay-to-ATM direction, you can specify one of the following discard eligibility (DE)-to-cell loss priority (CLP) schemes for an individual SIW connection:
oDE bit in the Frame Relay frame is mapped to the CLP bit of every ATM cell generated by frame segmentation.
oCLP is always 0.
oCLP is always 1.
In the ATM-to-Frame Relay direction, you can specify a CLP-to-DE mapping scheme for an individual connection:
oIf one or more ATM cells belonging to a frame has CLP=1, the DE field of the Frame Relay frame is set.
oDE is always 0.
oDE is always 1.
This section describes congestion indictors. You can modify the CLP and congestion indicators for individual connections. On the CLI, use the cnfchanmap command. In the Frame Relay-to-ATM direction, you can configure a Frame Relay-to-ATM SIW connection for one of the following Forward Explicit Congestion Notification (FECN)-to-Explicit Forward Congestion Indicator (EFCI) schemes:
oFECN bit in the Frame Relay frame is mapped to the EFCI bit of every ATM cell generated by the segmentation process of the frame.
oEFCI is always 0.
oEFCI is always 1.
In the ATM-to-Frame Relay direction, service interworking connections use the following EFCI to FECN/BECN mapping schemes:
oIf the EFCI bit in the last ATM cell of a segmented frame received is set to 1, the FECN of the Frame Relay frame is set to 1.
oBECN is always set to 0.
The FRSM provides command and response mapping in both directions:
oIn the Frame Relay-to-ATM direction, the FRSM maps the C/R bit of the received Frame Relay frame to the CPCS-UU least significant bit of the AAL5 CPCS PDU.
oIn the ATM-to-Frame Relay direction, the FRSM maps the least significant bit of the CPCS-UU to the C/R bit of the Frame Relay frame.
Each service interworking (SIW) connection can exist in either translation or transparent mode. In translation mode, the FRSM translates protocols between the FR NLPID encapsulation (RFC 1490) and the ATM LCC encapsulation (RFC 1483). In transparent mode, the FRSM does not translate. Translation mode support includes address resolution by transforming address resolution protocol (ARP, RFC 826) and inverse ARP (inARP, RFC 1293) between the Frame Relay and ATM formats.
You can configure an individual port for frame forwarding. Frame forwarding is the same as standard Frame Relay except that the FRSM:
oDoes not interpret the two-byte Q.922 header.
oMaps all received frames to a specific connection if it exists, otherwise it discards the frames.
oDoes not map between DE and CLP or between FECN and EFI.
oDoes not support statistics for &Illegal header count& or &Invalid DLCI.&
oDoes generate statistics for &Discarded frame count due to no connection.&
All FRSMs support the ATM Frame User-to-Network Interface (FUNI). When a frame arrives from the FUNI interface, the FRSM removes the 2-byte FUNI header and segments the frame into ATM cells by using AAL5. In the reverse direction, the FRSM assembles ATM cells from the network into a frame by using AAL5, adds a FUNI header to the frame, and sends it to the FUNI port.
The FRSM maps the loss priority indication for both directions:
oIn the FUNI to ATM direction, the FRSM maps the CLP bit in the FUNI header to the CLP bit of every ATM cell that it generates for the FUNI frame.
oIn the ATM-to-FUNI direction, the FRSM always sets the CLP bit in the FUNI header to 0.
The FRSM maps congestion indication in both directions:
oIn the FUNI-to-ATM direction, it sets EFCI to 0 for every ATM cell it generates by segmentation.
oIn the ATM-to-FUNI direction, it sets the CN bit in the FUNI header to 1 if the EFCI field in the last ATM cell of a received, segmented frame is 1. The two reserve bits (the same positions as C/R and BECN in Frame Relay header) are always 0.
This section first describes how to configure the FRSM card, lines, and ports, then describes how to add connections. The descriptions are for the CLI execution of the tasks. You can also configure the FRSM card, lines, and ports by using the CiscoView application. Refer to the CiscoView documentation for the directions. Also, the easiest way to add connections is by using the Cisco WAN Manager application. For full details of how to set up a connection through the WAN Manager GUI, refer to the Cisco WAN Manager Operations manual.
This section describes how to configure card-level parameters—including Y-cable redundancy where applicable, physical lines, and logical ports on the FRSM-series cards.
Step&1 If necessary, modify the resource partitioning for the whole card by executing the cnfcdrscprtn command. You can view resource partitioning through dspcdrscprtn.
cnfcdrscprtn &number_PAR_conns | number_PNNI_conns | number_TAG_conns&
number_PAR_conns is the number of connections in the range 0-1000 available to the PAR controller.
number_PNNI_conns is the number of connections in the range 0-1000 available to a PNNI controller.
number_TAG_conns is the number of connections in the range 0-1000 available to the Tag controller.
For example, you could reserve 300 connections for each controller on the FRSM with:
cnfcdrscprtn 300 300 300
Step&2 If the physical line is not yet active, use the addln command to activate it. The only argument addln takes is the line number.
Step&3 If necessary, modify a line on the MGX-FRSM-2CT3, MGX-FRSM-HS2/B, MGX-FRSM-HD1/B, AX-FRSM-8T1 or AX-FRSM-8E1 by using cnfln.
To change line parameters on an MGX-FRSM-2CT3, MGX-FRSM-2T3E3, or MGX-FRSM-2E3, use cnfds3ln. Note that both cnfln and cnfds3ln apply to the MGX-FRSM-2CT3 but affect different aspects of it.
For the syntax of the line modification commands on all cards except the MGX-FRSM-HS1/B, refer to the Cisco MGX 8850 Wide Area Edge Switch Command Reference.
The syntax for the MGX-FRSM-HS1/B
cnfln &line_num& &line_type& &line_rate&
oline_num has the range 1-4,
oline_num is a number that specifies the mode and must accord with the 12IN1 cable connected to the port: 1=DTE. 2=DCE. 3=DTE_ST (V.35 only)
ois a number in the range 1-50 that corresponds to a specific rate for the line. The range for line rates is 48 Kbps-52 Mbps. In , the number for line_rate corresponds to a number of bits per second.
Table&6-2 Supported Lines rates on the MGX-FRSM-HS1/B
18=1024000
19=1536000
20=1544000
21=1792000
22=1920000
23=1984000
24=2048000
25=3097000
26=3157000
27=4096000
28=4645000
29=4736000
30=6195000
31=6315000
32=7744000
33=7899000
34=8192000
35=9289000
36=9472000
49=2498600
The possible errors for cnfln are:
oOne or more parameters are invalid.
oLine does not exist (has not been added).
oLoopback or BERT is on.
oAn active port already exists on this line.
Step&4 If the logical port does not exist or is not the appropriate type (Frame Relay, FUNI, or frame forwarding), execute addport to create the appropriate type of port. If the logical port already exists and needs no modification (cnfport), you can add connections by performing the tasks in &.& The parameters for addport depend on the type of FRSM:
For MGX-FRSM-2T3, MGX-FRSM-2E3, or MGX-FRSM-HS2/B:
addport &port_num& &line_num& &port_type&
oport_num is the logical port number in the range 1-2. The mapping between a logical port and a line is one-to-one for these cards. Note that the maximum committed information rate (CIR) on each line for these cards is 0- bps for MGX-FRSM-2T3, 0- bps for MGX-FRSM-2E3, and 0- bps for MGX-FRSM-HS2. Specify CIR with addcon (or addchan if necessary).
oline_num is the physical line number in the range 1-2.
oport_type is a number representing the mode of operation for the logical port: 1 for Frame R 2 for FUNI mode-1a; or 3 for frame forwarding.
For an MGX-FRSM-2CT3:
addport &port_num& &line_num& &ds0_speed& &begin_slot& &num_slot& &port_type&
oport_num is the logical port number in the range 1-256. When you subsequently add a connection through the preferred command addcon or the addchan command (which requires NSAP format), you must indicate a logical port by using this singular port_num regardless of the number of DS0s. (You can add 1-24 DS0s to a single port_num through the other addport parameters.)
oline_num is the DS1 number in the range 1-56 to which you assign the DS0 when both lines are active. If you activate only one line, the range is 1-28. You can assign up to 24 contiguous DS0s to one DS1. Each physical line supports up to 28 DS1s. The number of DS0s cannot span more than DS1.
ods0_speed is a number representing the DS0 speed: 1 for 56 Kbps or 2 for 64 Kbps.
obegin_slot is the beginning DS0 timeslot in 1 base. For example, on port number 50, you could make begin_slot=9 then specify num_slot to be in the range 1-16.
onum_slot is the number of DS0s in the associated DS1. Note that the number of DS0s cannot be such that the logical port spans more than DS1.
oport_type is a number representing the mode of operation for the logical port: 1 for Frame R 2 for FUNI mode-1a; and 3 for frame forwarding.
For MGX-FRSM-HS1/B
addport &port_num& &port_type&
oport_num is the port number in the range 1-4.
oport_type is a number representing the type of frame interface technology for the logical port: 1 for Frame R 2 for FUNI mode-1a; or 3 for frame forwarding.
For AX-FRSM-8T1 and AX-FRSM-8E1:
addport &port_num& &line_num& &ds0_speed& &begin_slot& &num_slot& &port_type&
oport_num is the logical port number in the range of either 1-192 for T1 or 1-248 for E1. When you subsequently add a connection through the preferred command addcon or the addchan command (which requires NSAP format), you must indicate a logical port by using this singular port_num regardless of the number of DS0s. (You can add 1-24 DS0s to a single line through the other addport parameters.)
oline_num is the physical line number in the range 1-8.
ods0_speed is a number representing the DS0 speed: 1 for 56 Kbps or 2 for 64 Kbps.
obegin_slot is the beginning DS0 timeslot in 1 base. For example, on port number 50, you could make begin_slot=9 then specify num_slot to be in the range 1-16.begin_slot is the beginning timeslot in 1 base.
onum_slot is the consecutive DS0s that each connection on port_num has.
oport_type is a number representing the mode of operation for the logical port: 1 for Frame R 2 for FUNI mode-1a; and 3 for frame forwarding.
Step&5 Modify as needed the signaling on a port by executing cnfport.
cnfport &port_num& &lmi_sig& &asyn& &elmi& &T391& &T392& &N391& &N392& &N393&
oport_num is the logical port number with a range that depends on the type of FRSM:
–For the MGX-FRSM-2CT3, 1-56
–For a channelized AX-FRSM-8T1, 1-192
–For a channelized AX-FRSM-8E1, 1-248
–For the unchannelized cards, the range equals the number of lines.
olmi_sig specifies the LMI signaling. 1=Other, 2=None, 3=StrataLMI, 4=AnnexAUNI, 5=AnnexDUNI, 6=AnnexANNI, 7=AnnexDNNI LMI signalling, N=none, S=StrataLMI, and au=AnnexAUNI.
oasyn enables asynchronous updates: (y)es or (n)o
oelmi enables Enhanced LMI: (N or n) disable (Y or y) enable
oT391 sets the T391 timer. The range is 5-30 seconds. It sets the interval in seconds for NNI status polling. The default is 10.
oT392 sets the T392 timer. The range is 5-30 seconds. It sets the interval in seconds for UNI status polling. The default is 15.
oN391 sets the N391 counter-the number of UNI/NNI polling cycles. The range is 1-255. The default is 6.
oN392 sets the N392 counter-the threshold for UNI/NNI errors. The range is 1-10. The default is 3.
oN393 sets the N393 counter-the UNI/NNI threshold for monitored events. The range is 1-10 and must be greater than the value of N392. The default is 4.
Step&6 Configure resources for the port as needed by executing cnfportrscprtn. To see the partitioning, use dspportrscprtn. The description has a high and low-bandwidth version:
cnfportrscprtn &port_num& &controller& &percent BW& &low DLCI& &high DLCI& &max LCN&
For FRSM-VHS cards:
oport_num is the port number in the range 1-2 for MGX-FRSM-2T3E3 and MGX-FRSM-HS2 or 1-256 for MGX-FRSM-2CT3.
ocontroller is a number representing the controller: 1=PAR, 2=PNNI, and 3=Tag.
opercent BW is the percentage of the bandwidth in the range 0-100 and applies to both egress and ingress.
olow DLCI is in the range 0-1023.
ohigh DLCI is in the range 0-1023.
omax LCN is the maximum number of logical connections available to the controller on this port. The ranges are 1-4000 for MGX-FRSM-2CT3 and 1-2000 for MGX-FRSM-2T3E3 and MGX-FRSM-HS2.
For AX-FRSM-8T1 or AX-FRSM-8E1:
oport_num is the logical port number in the range 1-192 for T1 or 1-248 for E1.
ocontroller-name is PAR, PNNI, or TAG.
opercent BW is the percentage of the bandwidth in the range 0-100 and applies to both egress and ingress.
olow DLCI is in the range 0-1023.
ohigh DLCI is in the range 0-1023.
omax LCN is the maximum number of logical connections available to the controller on this port. The range is 1-1000.
Note&&&The following step applies to Y-cable redundancy for the MGX-FRSM-2T3E3. For 1:N redundancy on the eight-port FRSMs, refer to &.&
Step&7 Optionally configure Y-cable redundancy if you have connected the lines of adjacent MGX-FRSM-2T3 or MGX-FRSM-2E3 cards through a Y-cable. The applicable commands are addred, dspred, and delred. These commands run on the PXM rather than the service module, so you must change to the PXM CLI to execute them:
addred &redPrimarySlotNum& &redSecondarySlotNum& &redType&
oredPrimarySlotNum is the slot number of the primary card. The possible numbers are 1-6, 9-14, 17-22, and 25-30.
oredSecondarySlotNum is the slot number of the primary card. The possible numbers are 1-6, 9-14, 17-22, and 25-30.
oredType is the type of redundancy. Enter a 1 for 1:1 Y-cable redundancy.
This section describes how to add a Frame Relay connection according to the rules for adding a standard connection or a management connection in the form of either a DAX con or a three-segment connection. See && earlier in this chapter.
Step&1 Add a connection by using addcon. If the application requires the NSAP form for the endpoint, use addchan as described in the command reference.
The system automatically assigns the next available channel number, so the addcon command does not require it. However, some related commands require a channel number. To see the channel number after you add a connection, use dspcons.
On the FRSM-VHS cards (2CT3, 2T3E3, or HS2):
addcon &port& &DLCI& &cir& &chan_type& &egress_service_type& [CAC] &controller_type& &mastership& [connID] &controllerID&
oport is the logical port number on the MGX-FRSM-2CT3 in the range 1-256. On the MGX-FRSM-2T3E3 and MGX-FRSM-HS2, the range is 1-2. (See addport step if necessary.)
oDLCI is the DLCI number in the range 0-/2T3/2E3/HS2).
ocir is the committed information rate in one of the following ranges: for 2CT3, 0-1536000 for 2T3, 0-E3, 0- and for HS2, 0- bps.
ochan_type specifies the type of connection: 1=NIW, 2=SIW- 3=SIW 4=FUNI, and 5=frame forwarding.
oegress_service_type is a number that specifies the type of queue on the egress:1= 2=real-time VBR, 3=nonreal-time VBR; 4=ABR; and 5=UBR.
oCAC optionally enables connecti 1=enable. 2=disable (default). With CAC enabled, the system adds the resource consumption represented by adding the connection to the total resources consumed on a logical port.
ocontroller_type is the controller type for signaling connections: 1 (the default) specifies a PVC and applies to PAR. 2 specifies a SPVC and applies to PNNI.
omastership indicates if this end of the connection is master or slave: 1=master, 2=slave.
oconnID is the connection identifier at the remote end. It appears in the syntax as an optional parameter because it is mandatory only when you add the connection at the master end. See && at the beginning of this chapter. connID can have one the following formats according to the slave endpoint:
Nodename.SlotNo.PortNo.DLCI
Nodename.SlotNo.PortNo.ControllerId.DLCI
Nodename.SlotNo.PortNo.VPI.VCI for ATM endpoint
ocontrollerID is a number indicating the type of network control application: 1=PAR, 2=PNNI, 3=MPLS
For AX-FRSM-8T1 and AX-FRSM-8E1:
addcon &port& &DLCI& &cir& &chan_type& [CAC] &controller_type& &mastership& &connID& &controllerID&
oport is the logical port number in the range 1-192 for T1 or 1-248 for E1. (See addport step if necessary.)
oDLCI is the DLCI number in the range 0-1023.
ocir is the committed information rate in one of the following ranges:for T1, 0-1536000 bps for T1; for E1, 0-2048000 bps.
ochan_type specifies the type of connection: 1=NIW, 2=SIW- 3=SIW 4=FUNI, and 5=frame forwarding.
oCAC optionally enables connection admission control: 1=enable. 2=disable (default).
ocontroller_type is the controller type for signaling: 1=PVC (PAR), the default, 2=SPVC (PNNI).
omastership indicates if this end of the connection is master or slave: 1=master, 2=slave.
oconnID is the connection identifier at the remote end and can have one the following formats according to the type of card at the slave endpoint:
NodeName.SlotNo.PortNo.DLCI
NodeName.SlotNo.PortNo.ControllerId.DLCI
NodeName.SlotNo.PortNo.VPI.VCI for ATM endpoint
If the remote end is a PXM, the port number can be in the range 1-32 for user connections or 34 for inband management connections (stand-alone node only).
ocontrollerID is a number indicating the type of network control application: 1=PAR, 2=PNNI, 3=TAG.
For MGX-FRSM-HS1/B:
addcon &port_number& &DLCI& &CIR& &chan_type& &CAC& &Controller_type& &mastership& &connID&
oport_number is the logical port in the range 1-4.
oDLCI is the DLCI in the range 0-1023.
oCIR specifies the committed information rate. The range is 0- bps (although the V.35 version supports a maximum of 8 Mbps sustained).
ochan_type is a number that identifies the channel type: 1=NIW. 2=transparent SIW. 3=SIW with translation. 4=FUNI. 5=frame forwarding.
oCAC enables connection admission control.
oController_type identifies the network control application. 1=PAR. 3=PNNI.
ospecifies the mastership status of this end of the connection. 1=,aster. 2=slave.
omastership indicates the mastership status for this end of the connection. 1=master. 2=slave.
oconnID is the &remote& connection identifier from the slave end if you need to enter it at the master end. See
for an explanation. The possible formats are:
–NodeName.SlotNo.PortNo.DlCI
–NodeName.SlotNo.PortNo.ControllerId.DlCI for Frame Relay end point
–NodeName.SlotNo.PortNo.VPI.VCI for ATM end point.
Where ControllerId can be 1(PAR),2(PNNI),3(TAG)
Step&2 Modify a connection as needed by executing cnfcon. See the command line Help or the command reference for the parameters for individual