Cisco ATM and Frame Relay Services (MPSM-T3E3-155) Configuration Guide and Command Reference for MGX Switches, Release 5

Provisioning Frame Relay Services

This chapter describes how to provision Frame Relay services on the MSPM-T3E3-155 card, and provides procedures for adding Frame Relay ports and connections to the physical lines and paths. The types of links and connections are described in Table 4-1.

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

Soft permanent virtual circuits (SPVCs) are permanent connections that can be rerouted in the event of a link failure. An MSPM-T3E3-155 SPVC establishes a connection between two ports. Such ports can be on the same card, on different cards in the same switch, or on different cards in different switches.

The following services are supported on Frame Relay connections:

•High priority

•VBR-RT

•VBR-NRT

•ABR-STD

•UBR

The following types of channels are supported on the MPSM-T3E3-155 when it is in Frame Relay mode:

•NIW

•NIW-Replace

•SIW-T

•SIW-X

•Frame Forwarding

To do the procedures in this section you must start a CLI session on the appropriate MPSM-T3E3-155 card by logging in with the appropriate username and password. For detailed information about user names, passwords, and logging into the CLI, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

Note To do the procedures in this section, you must log in as a user with GROUP1 privileges or higher.

A new CLI command, or a simple change to an existing CLI command argument, is used to differentiate the line and connection types from each other.

To eliminate redundancy and help experienced users complete configuration tasks quickly and efficiently, this chapter provides configuration quickstart procedures.

The first time you configure a connection type, use the applicable quickstart procedure to get an overview of the tasks to be performed. Then, for more detailed instructions, consult the appropriate section(s) elsewhere in the document that are called out in the quickstart procedure. As you gain experience in configuring MSPM-T3E3-155 card connections, referring to a quickstart procedure may suffice for performing a particular configuration task.

Tip You can get information about most CLI commands by entering the command without arguments. Ordinarily, experienced users can configure MSPM-T3E3-155 card connections using just the quickstart procedures and the online help facilities.

Note For a detailed description of the commands used in this chapter, refer to Chapter 6, "MPSM-T3E3-155 Command Reference."

Note Before you attempt to configure Frame Relay connections, complete the general switch configuration tasks described in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5. Some of the procedures described in this chapter will not work if the MGX 8850 or Cisco MGX 8830 switch has not been configured properly.

Quickstart Provisioning Procedures

This section contains abbreviated procedures for provisioning the communications capabilities of MSPM-T3E3-155 cards installed in Cisco MGX 8850/8830 Release 5 switches. These procedures provide a high level overview and summary for users who may already be experienced in configuring Cisco MGX 8850/8830 switches:

•"MPSM-T3E3-155-to-MPSM-T3E3-155 Frame Relay SPVC Configuration Quickstart"

•"MPSM (Frame Relay)-to-MPSM (ATM) SPVC Configuration Quickstart"

•"MPSM-to-Non-MPSM SPVC Configuration Quickstart"

Caution Before you can configure any Frame Relay connections, you must first complete the general switch configuration procedures described in Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

Before you can configure an MSPM-T3E3-155 port, you must set up lines and/or paths as described in Chapter 2, "Preparing MPSM-T3E3-155 Cards and Lines for Communication."

Note The equipment at both ends of a Frame Relay line must be configured with compatible settings in order for the link to be logically completed.

MPSM-T3E3-155-to-MPSM-T3E3-155 Frame Relay SPVC Configuration Quickstart

A soft permanent virtual circuit (SPVC), a variant of a permanent virtual circuit (PVC), can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol.

Both PVCs and SPVCs are full-time connections. A PVC uses a predefined circuit path that fails if the path is interrupted for any reason. In contrast to a PVC, if a link along an SPVC path fails, or if that link cannot provide the required bandwidth, the PNNI protocol reroutes that link to maintain the connection and supply the necessary bandwidth for the connection.

Note The procedures in this section apply to the MPSM-T3E3-155 in Frame Relay mode only. To establish a connection between and MPSM-T3E3-155 in Frame Relay mode and an MPSM-T3E3-155 in ATM mode, refer to the "MPSM (Frame Relay)-to-MPSM (ATM) SPVC Configuration Quickstart".

You can configure an SPVC between two MSPM-T3E3-155 card Frame Relay ports in any of the following instances:

•Any two Frame Relay ports on a single MSPM-T3E3-155 card in a Cisco MGX 8850 (PXM1E/PXM45) or Cisco 8830 switch.

•Any two Frame Relay ports on different MSPM-T3E3-155 cards in the same Cisco MGX 8850 (PXM1E/PXM45) or Cisco 8830 switch.

•Any two Frame Relay ports on different MSPM-T3E3-155 cards in different Cisco MGX 8850/8830 switches

To configure an SPVC between two MSPM-T3E3-155 card ports, perform the following steps:

MPSM (Frame Relay)-to-MPSM (ATM) SPVC Configuration Quickstart

To configure an SPVC between a local MSPM-T3E3-155 Frame Relay port and a remote ATM port on another MPSM-T3E3-155 in the same switch or in another switch, perform the following steps:

MPSM-to-Non-MPSM SPVC Configuration Quickstart

To configure an SPVC between a local MSPM-T3E3-155 port and a remote port on another card in the same switch or in another switch, perform the following steps:

•For additional details about configuring SPVCs on AXSM cards, see the Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.

•For additional details about configuring SPVCs on PXM1E cards, see the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

•For additional details about configuring SPVCs on PXM1 cards, see the Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3.

•For additional details about configuring SPVCs on BXM cards, see the BPX 8600 Series Installation and Configuration documentation.

•For additional details about configuring SPVCs on RPM cards, see the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 or the Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1.

MSPM-T3E3-155 Frame Relay Configuration Procedures

This section describes the following MSPM-T3E3-155 Frame Relay concepts and general procedures:

•Adding Frame Relay Ports

•Partitioning Port Resources Between Controllers

•Selecting the Port Signaling Protocol

•Provisioning and Managing SPVCs

The descriptions and procedures in this section use Frame Relay service context commands. See Chapter 6, "MPSM-T3E3-155 Command Reference" for detailed descriptions of the MPSM-T3E3-155 Frame Relay service commands and parameters.

See Table 1-1 in "Introduction" for a list of the MPSM-T3E3-155 model numbers, back cards, and the number of possible connections.

Some of the procedures in this section use PXM commands and PNNI commands. Refer to the Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5 for descriptions of the PXM and PNNI commands and parameters.

For more information on port signaling, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

Adding Frame Relay Ports

On an MPSM-T3E3-155 card, a logical port is also called a virtual interface and is represented by the ifNum variable. The MPSM-T3E3-155 cards can have the following types of Frame Relay interfaces:

•Frame Relay —This is a port that sends and receives standard Frame Relay frames as defined by ITU-T Q.922. Multiple virtual circuits (VCs) can terminate on a single Frame Relay port and are differentiated by their data-link connection identifiers (DLCIs).

•FrameForwarding—This is a port that sends and receives frame-based traffic that is similar to Frame Relay frames such as HDLC, SDLC, and X.25 over Frame Relay interfaces. You can transport any protocol across an ATM network, as long as it supports the HDLC, SDLC, or X.25 format. Application examples include routers interconnected via PPP, mainframes or hosts connected by X.25/HDLC, SNA/SDLC links, and video CODECs that use a frame-based protocol. Frame Forwarding is often used for the aggregation of point-to-point (PPP) traffic into an ATM network, then exiting the ATM network via an ATM interface over multiple VCs into routers supporting PPP over ATM. Frame Forwarding features include:

–No translation or mapping is attempted between the frame header bits and ATM layer EFCI and CLP bits. Because the port is unable to read the address and control information in the frame, all traffic must be forwarded to a single destination frame forwarding port.

–Only one frame forwarding VC is allowed per port.

–If a connection is set up, all frames are routed to and from that connection, otherwise the frame is discarded.

–A single set of Frame Relay traffic access parameters (for example, CIR) is configured for the logical port in frame forwarding mode. All arriving frames are treated as if they arrived without a set DE bit. If the frame is determined to exceed committed rate (exceeding CIR), the CLP of all cells associated with that frame is set to indicate low priority. If the frame exceeds the total rate allowed for committed and uncommitted traffic, the frame is discarded.

–Support for PPP encapsulation over AAL5 and frame is based on RFC 1483 and RFC 1490.

Note The range for the number of logical broadband Frame Relay ports (ifNum) on the MPSM-T3E3-155 card is 1-1003. The range for the number of logical narrowband Frame Relay ports (ifNum) on the MPSM-T3E3-155 card is 4-1003.

The "Setting Up Lines" section in Chapter 2, "Preparing MPSM-T3E3-155 Cards and Lines for Communication," describes how to bring up physical lines by specifying the correct line port number. The "Channelizing SONET, SDH, and DS3 (T3) Lines into Paths" in Chapter 2, "Preparing MPSM-T3E3-155 Cards and Lines for Communication," describes how to bring up paths on SONET lines. Line ports correspond to the line connectors on the back cards of a Cisco MGX 8850/8830 switch.

Bringing up a line establishes physical layer connectivity between two network devices. When you add a Frame Relay port to a line, you enable Frame Relay communications by means of that line.

To add a Frame Relay port to a line, perform the following steps:

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

Step 2 Enter the cc command to change to the active MPSM-T3E3-155 card on which you want to add a port.

Step 3 Get the line or path number on which you will add the port.

If you are adding a port to a line, enter the dsplns command to determine the line number on which you intend to add the Frame Relay port, as shown in the following example.

M8850_NY.13.MPSM155[FR].a> dsplns 

Sonet         Line     Line      Line    Frame   Line    Line    Valid   Alarm   APS     Channe-

  Line          State    Type      Lpbk   Scramble Coding  Type    Intvls  State   Enabled lized

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

   1.1             Up   sonetSts3c NoLoop   Enable    NRZ ShortSMF     96    Clear Disable   Yes

   1.2           Down   sonetSts3c NoLoop   Enable    NRZ    Other      0    Clear Disable    No

This command displays a list of the lines and line numbers configured for the MSPM-T3E3-155 card.

Tip You cannot configure a line until you have brought it up, as described in the "Setting Up Lines" section in Chapter 2, "Preparing MPSM-T3E3-155 Cards and Lines for Communication."

If you are adding a port to a path, enter the dsppaths -all command to determine the path number on which you intend to add the Frame Relay port.

M8850_NY.13.MPSM155[FR].a > dsppaths -all

  Path     Path    Admin       Path       Path     Alarm    Oper  

           Type    Status      Payload    Width    Status   State 

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

   1.1.1      sts       Up        hdlcFr       1  Critical   Down

   1.1.2      sts       Up           atm       1  Critical   Down

   1.1.3      sts       Up        hdlcFr       1  Critical   Down

    Shelf Database table empty.SonetVTsTable

    Shelf Database table empty.Ds3PathsTable

    Shelf Database table empty.Ds1PathsTable

Note You cannot add a port directly on a SONET line. Before you can configure a SONET connection, you must enter the uppath command to activate a path on the specified line.

Step 4 Verify that the line/path and port number you want to use is not configured.

To display a list of the configured ports on the MSPM-T3E3-155 card, enter the dspports command as follows:

M8850_NY.13.MPSM155[FR].a> dspports 

The dspports command shows all configured ports in the ifNum (interface number) column. Note the port numbers that already in use. When you add a port, you must specify a unique port number on the MSPM-T3E3-155 card. For example, if port number 2 is assigned to line 1.1 (bay 1, line 1), you cannot use port 2 on any other line on that MSPM-T3E3-155 card.

Note The MSPM-T3E3-155 cards support one port per line.

Note On MPSM-T3E3-155 cards, the bay is always 1.

Step 5 Enter the addport command as follows to add a Frame Relay port to an active line or path.

M8850_NY.13.MPSM155[FR].a> addport <ifNum> <path> <portType> <sctId> [-dlciLen <dlciLen>] 
[-flags <portFlagsBetweenFrames>] [-rat <PortEqueueServiceRatio>] [-csum <checksum>] 
[-oversub <overSubscribeEnable>] [-lmiSig <lmiSigType>] [-asynUpdt <updateType>] [-elmi <elmiState>] 
[-segLmi <segLmiStatus>] [-t391 <t391Value>] [-t392 <t392Value>] [-n391 <n391Value>] [-n392 <n392Value>] 
[-n393 <n393Value>] [-ds0speed <ds0speed> -ds0beg <ds0beg> -ds0num <ds0num>]  
[-fragEnable <fragEnable>] [-fragSize <fragSize>] [-hdlcinv <hdlcinv>]

Table 4-2 lists and describes the keywords and arguments for adding a logical port to a physical line by means of the addport command.

In the following example, the user defines a Frame Relay port that uses SCT 4 and the default values for all arguments:

M8850_NY.13.MPSM155[FR].a> addport 1 1.1 1 4

Step 6 Enter the dspports command as follows to verify that the port you added in Step 5 appears in the ifNum (interface number) column.

M8850_NY.13.MPSM155[FR].a> dspports

ifNum   Line/Path     Admin        Oper           ifType         SCT id          FRF 12

                      State        State                       Conf./InUse    Fragmentation

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

    2         1.1.1    Down             Down      Frame Relay    0/  0 =Def     Disabled

   50     1.1.3:1.1      Up               Up      Frame Relay    0/  0 =Def     Disabled

If you want to view the configuration information for a particular port, note the number of that port and proceed to Step 7.

Step 7 Enter the dspport command to display the configuration information for a specific port.

mpsm_node.5.MPSM155[FR].a > dspport <ifNum>

Replace the <ifNum> argument with the number assigned to the port during port configuration. In the following example, the user displays the configuration information for logical port number 2:

M8850_NY.13.MPSM155[FR].a> dspport 2

  Interface Number                 : 2

  Line Number                      : 1.1.1

  DS0 Speed                        : unused

  DS0 Configuration Bit Map        : N/A

  Admin State                      : Down   

  Operational State                : Down          

  Port State                       : Inactive

  Port Signaling State             : No Signaling Failure

  Interface Type                   : Frame Relay

  SCT Id                           : 0/0 =Def

  Frame Header Length              : Two Bytes

  Flags Between Frames             : 1

  Equeue Service Ratio             : 1

  Port Speed                       : 44209 kbps

  Checksum type                    : crc16

  Over-subscription                : Disabled

  Over-subscribed                  : False

  Signaling Protocol Type          : No Signaling

  Enhanced LMI                     : Disabled

  FRF 1.2 Support                  : Disabled

  Asynchronous Updates             : Disabled

  T391 Link Integrity Timer        : 10 secs

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

  T392 Polling Verification Timer  : 15 secs

  N391 Full Status Polling Counter : 6

  N392 Error Threshold             : 3

  N393 Monitored Event Count       : 4

  FRF.12 Fragmentation             : Disabled

  FRF.12 Fragment Size             : 64 Bytes

  Port HDLC Frame Inversion        : Disabled

  Number of Partitions             : 1

  Number of SPVC                   : 0

Tip To change the port configuration, enter the cnfport command. To delete the port configuration, enter the delport command. You can also activate or deactivate a port using the upport and dnport commands. For more information about these commands, refer to Chapter 6, "MPSM-T3E3-155 Command Reference."

Partitioning Port Resources Between Controllers

After you add a Frame Relay port, you can define how the port resources are to be used by the PNNI controller. Although the Cisco MGX 8850/8830 software allows you to distribute port resources to multiple controllers, the PNNI controller is the only controller supported on Frame Relay ports in Release 5 of the MPSM-T3E3-155. Therefore, you can assign all resources to the PNNI controller. These resources include the following:

•Range of DLCI values

•Maximum percent of bandwidth in the ingress and egress directions

•Maximum number of connections

•Minimum and Maximum DLCI values

Note You can and should use the partition definition to control how available connections are distributed within the Cisco MGX 8850/8830 switch. Each switch, card, and port supports a maximum number of connections. Although it is possible to enable the maximum number of connections on all ports, if two or three ports are very busy, all the available connections could be consumed on these ports, thus disabling communications on all other ports.

A partition is automatically added when you add a port. You can change the resource partition configuration with the cnfpart command.

Note You can use the addpart command to create additional resource partitions for a port. The partition ID you use when you create the resource partition can be any number in the range from 1 to 255. Once you assign a partition ID to any resource partition on the MSPM-T3E3-155 card, you must use the same partition ID for all other resource partitions on that card. Consider using 2 for the partition ID so that it matches the controller ID. If you do likewise on the other cards in your switch, there will be less confusion in managing partitions on different types of cards.

To configure a port resource partition, use the following procedure:

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

Step 2 Enter the dspports command as shown in the following example to display a list of all the logical ports on the MSPM-T3E3-155. Determine the port number to which you want to assign the resource partition.

Note All port numbers appear in the ifNum (interface number) column.

mgx8850a.10.MSPM-155[FR].a > dspports 

ifNum   Line/Path     Admin        Oper           ifType         SCT id          FRF 12

                      State        State                       Conf./InUse    
Fragmentation

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

    1         1.1.1      Up   LowerLayerDown     Frame Forward    0/  0 =Def     Disabled

    2         1.1.3      Up   LowerLayerDown     Frame Forward    0/  0 =Def     Disabled

Step 3 Enter the cnfpart command as follows to create a resource partition.

M8850_NY.13.MPSM155[FR].a> cnfpart <ifNum> <ctrlrNum> [-lcn <lcn>] [-dlcilow <dlcilow>]         
[-dlcihigh <dlcihigh>] [-ibw <ibw>] [-ebw <ebw>]

Table 4-3 lists and describes the arguments for the cnfpart command.

Step 4 Enter the dspparts command to display the resource partitions that you have configured on the current card. In the following example, the dspparts command indicates that two partitions have been configured.

M8850_NY.13.MPSM155[FR].a> dspparts

if      Ctlr   Ctlr  available   min      max     ingr     egr

Num     Num     ID      LCNs     DLCI     DLCI    PctBw   PctBw

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

   2    pnni      2     4000        0     1023     100     100

  50    pnni      2     2000        0     1023     100     100

Step 5 Enter the dsppart <ifNum> <ctrlrNum> command to display the configuration of a particular partition. Replace <ifNum> with the interface number, and replace <ctrlrNum> with the controller number, as shown in the following example:

M8850_NY.13.MPSM155[FR].a> dsppart 1 2 

The following example shows the output from a dsppart command:

M8850_NY.13.MPSM155[FR].a> dsppart 2 2

  Interface Number               : 2

  Partition Id                   : pnni        Number of SPVC: 0

  Controller Id                  : 2      

  Available LCNs                 : 4000   

  Min DLCI                       : 0

  Max DLCI                       : 1023

  Ingress Percentage Bandwidth   : 100    

  Egress Percentage Bandwidth    : 100    

mpsm_node.5.MPSM155[FR].a > 

Selecting the Port Signaling Protocol

The default signaling protocol for new Frame Relay ports is none.

To change the signaling protocol from the default setting, perform the following steps:

Step 1 Establish a configuration session with the active PXM using a user name with GROUP1 privileges or higher.

Step 2 Enter the dsppnports command as follows to display a list of PNNI ports available for configuration.

M8850_NY.7.PXM45.a > dsppnports

Summary of total connections

(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)

Type   #Svcc:   #Svpc:   #SpvcD:  #SpvpD:  #SpvcR:  #SpvpR:  #Ctrl #Total:

p2p:   0        0        30       0        0        0        0        30     

p2mp:  0        0        0        0        0        0        0        0      

    Total(User cons) =      30/50000,   Total(Ctrl cons) = 0      

            Total=30      

Summary of total SPVC endpoints

(P=Persistent, NP=Non-Persistent)

Type   #SpvcR-P  #SpvcR-NP #SpvpR-P  #SpvpR-NP #SpvcD   #SpvpD   Total

p2p:   0         0         0         0         60        0         60     

p2mp:  0         0         0         0         0         0         0      

                         Total=60     

Summary of total active SVC/SPVC intermediate endpoints

Type   #Svcc    #Svpc     #SpvcR   #SpvpR   Total

p2p:   0         0         0         0         0      

p2mp:  0         0         0         0         0      

                         Total=0      

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

DSPPNPORTS          EndPoint Grand Total =     60/100000 

Per-port status summary

PortId      LogicalId    IF status      Admin status  ILMI state        #Conns

7.35         17251107    up             up            NotApplicable     0       

7.36         17251108    up             up            NotApplicable     0       

7.37         17251109    up             up            NotApplicable     0       

7.38         17251110    up             up            NotApplicable     0       

11:1.1:1     17504257    provisioning   up            NotApplicable     5       

11:1.2:2     17504258    provisioning   up            NotApplicable     5       

11:1.3:3     17504259    provisioning   up            NotApplicable     5       

11:1.4:4     17504260    provisioning   up            NotApplicable     5       

11:1.5:5     17504261    provisioning   up            NotApplicable     5       

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

PortId      LogicalId    IF status      Admin status  ILMI state        #Conns

11:1.6:6     17504262    provisioning   up            NotApplicable     5       

11:2.1:7     17504263    provisioning   up            NotApplicable     5       

11:2.2:8     17504264    provisioning   up            NotApplicable     5       

11:2.3:9     17504265    provisioning   up            NotApplicable     5       

11:2.4:10    17504266    provisioning   up            NotApplicable     5       

11:2.5:11    17504267    provisioning   up            NotApplicable     5       

11:2.6:12    17504268    provisioning   up            NotApplicable     5       

M8850_NY.7.PXM45.a > 

Step 3 Enter the dnpnport <portid> command to bring down the port you want to configure. Replace the <portid> argument in the dnpnport command using the format slot[:bay].line[:ifNum]. The port identification arguments are listed and described in Table 4-4.

Note A port is automatically brought up when you add it. Therefore, you must bring down the port before you can change the signaling protocol for that port.

In the following example, the user brings down port 13.5:

M8850_NY.7.PXM.a > dnpnport 13.5

Step 4 Enter the dsppnports command as shown in the following example to confirm that the specified port is down.

M8850_NY.7.PXM45.a > dsppnports

Summary of total connections

(p2p=point to point,p2mp=point to multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc)

Type   #Svcc:   #Svpc:   #SpvcD:  #SpvpD:  #SpvcR:  #SpvpR:  #Total:

p2p:   0        0        17       0        0        0        17     

p2mp:  0        0        0        0        0        0        0      

                         Total=     17/50000 

Summary of total SPVC endpoints

(P=Persistent, NP=Non-Persistent)

Type   #SpvcR-P  #SpvcR-NP #SpvpR-P  #SpvpR-NP #SpvcD   #SpvpD   Total

p2p:   1         0         0         0         34        0         35     

p2mp:  0         0         0         0         0         0         0      

                         Total=35     

Summary of total active SVC/SPVC intermediate endpoints

Type   #Svcc    #Svpc     #SpvcR   #SpvpR   Total

p2p:   0         0         0         0         0      

p2mp:  0         0         0         0         0      

                         Total=0      

          EndPoint Grand Total =     35/100000 

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

DSPPNPORTSPer-port status summary

PortId      LogicalId    IF status      Admin status  ILMI state        #Conns

7.35         17251107    up             up            NotApplicable     0       

7.36         17251108    up             up            NotApplicable     0       

7.37         17251109    up             up            NotApplicable     0       

7.38         17251110    up             up            NotApplicable     0       

4:1.1:1      17045505    down           up            NotApplicable     11      

4:1.2:1      17045505    provisioning   up            NotApplicable     0       

4:1.2:2      17045506    up             up            NotApplicable     11      

Step 5 Enter the cnfpnportsig command as follows to define the signaling protocol for the specified port.

M8850_NY.7.PXM45.a > cnfpnportsig <portid> -univer none

Table 4-4 describes the elements of the <portid> argument.

Tip With some CLI commands, you can refer to a port using only the interface number. Other commands require that you enter a complete port identification number, which includes the slot, bay, line, and interface numbers. When entering commands at the PXM card prompt, you always need to specify the complete port identification number. When entering commands at the MSPM-T3E3-155 card prompt, you need enter only the interface number, because the interface number on the MSPM-T3E3-155 card is unique.

In the following example, the user configures an NNI port to use the PNNI Version 1.0 signaling protocol.

M8850_NY.7.PXM45.a > cnfpnportsig 4:1.1:1 -univer none

Step 6 Enter the uppnport command as follows to bring up the port you just configured.

M8850_NY.7.PXM45.a > uppnport <portid>

Replace the <portid> argument using the format slot:bay.line:ifNum.

Table 4-4 describes the elements of the <portid> argument.

Step 7 Enter the dsppnports command to verify that the port you brought up in Step 6 is in the "up" state in the Admin_st column.

Step 8 Enter the dsppnport <portid> command as follows to display the configuration of a specific PNNI port. Replace the <portid> argument using the format slot:bay.line:ifNum.

Note Table 4-4 describes the elements of the <portid> argument.

M8850_NY.7.PXM45.a > dsppnport 4:1.2:2

Port:               4:1.2:2           Logical ID:       17045506          

IF status:          up                Admin Status:     up                

UCSM:               disable           SVC Routing Pri:  8                 

Auto-config:        disable           Addrs-reg:        disable           

IF-side:            network           IF-type:          uni               

UniType:            private           Version:          none              

PassAlongCapab:     n/a               

Input filter:       0                 Output filter:    0                 

minSvccVpi:         0                 maxSvccVpi:       0                 

minSvccVci:         100               maxSvccVci:       32867             

minSvpcVpi:         1                 maxSvpcVpi:       0                 

       (P=Configured Persistent Pep, NP=Non-Persistent Pep, Act=Active)

       #Spvc-P:  #Spvc-NP:  #SpvcAct:  #Spvp-P:  #Spvp-NP:  #SpvpAct:  

p2p :  11        0          11         0         0          0          

p2mp:  0         0          0          0         0          0          

       #Svcc:     #Svpc:        Total:     

p2p :  0          0             11         

p2mp:  0          0             0          

                                Total:     11

Provisioning and Managing SPVCs

SPVCs are created between two Frame Relay ports, and each SPVC has two endpoints. The master endpoint of the SPVC is responsible for routing and rerouting functions. The slave endpoint of the SPVC is responsible for responding to requests from the master endpoint during connection setup and rerouting. Both endpoints are configured on the switch or switches to which the Frame Relay CPE connects. Such endpoints can be in the same switch or in different switches.

The master/slave relationship exists for each SPVC and applies only to that SPVC. For example, you can have one SPVC with a master on Node A and a slave on Node B, and then create another SPVC with the master on Node B and the slave on Node A. It is good practice to distribute the master side of SPVCs among network nodes to distribute route processing functions.

Before you can add an SPVC, the following tasks must have been completed:

1. The switch must have a network controller (see the addcontroller command in the Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5.

2. A physical line must be active. Use the upln command or the CiscoView application to bring up a line.

3. A path must be active. Use the uppath command or the CiscoView application to bring up a path.

4. At least one logical port must exist on the active path. Use the addport command or the CiscoView application to create the port. If necessary, modify the port through cnfport.

5. At least one resource partition must exist on the logical port. A resource partition is automatically added when you add a port. Use cnfpart command to modify the configuration for the existing resource partition, or delete the existing partition and enter the addpart command to create a new resource partition on the port. The resource partition should be associated with the controller added in Step 1.

You can create two types of SPVCs:

•Single-ended SPVCs

•Double-ended SPVCs

Single-ended SPVCs are defined at the master endpoint and do not require configuration of a slave endpoint. The primary benefit of single-ended SPVCs is that they are easier to configure. After configuration, the master endpoint configures and brings up the slave endpoint. In order for this feature to work correctly, the destination endpoint must support single-ended SPVCs.

Note In this software release for the Cisco MGX 8850/8830, the MSPM-T3E3-155 card supports only the origination of single-ended SPVCs. This means that you can configure master endpoints for single-ended SPVCs that terminate on another card.

Double-ended SPVCs require separate configuration of the master and slave endpoints. The slave endpoint must be configured first because this step generates a slave address that must be entered during master endpoint configuration.

The following sections describe how to configure slave and master SPVC connections.

Configuring the Slave Side of SPVCs

If you wish to configure a double-ended SPVC, you must first configure the slave endpoint for the connection. If you are configuring a single-ended SPVC, you need not configure a slave endpoint.

To configure the slave side of a double-ended SPVC, perform the following steps:

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

Step 2 Enter the cc <slotnumber> command as follows to change to the MSPM-T3E3-155 card that hosts the slave side of the SPVC connection.

mgx8850a.7.PXM45.a > cc <slotnumber>

Replace <slotnumber> with the number of the slot in which the MSPM-T3E3-155 card is installed.

Step 3 Enter the addcon command as follows to define the slave side of the SPVC:

mgx8850a.10.MSPM-155[FR] .a > addcon <ifNum> <dlci> <chanType> <serviceType> <mastership> 
<cir> [-slave <value> ] [-slavespersflag <slavepers> ]

[-eir <zeroCirEir>] [-bc <Burst Commit>] [-be <Burst Excess>] [-detag <DE Tagging Enable>] 
[-igde <Ignore Incoming DE>] [-fecnmap <FECN map>] [-demap <DE to CLP map>] 
[-clpmap <CLP to DE map>] [-eqsel <Egress Q Select>] [-ingut <Ingress Perc Util>] 
[-egut <Egress Perc Util>] [-egrat <Egress Service Rate>] [-rtngprio <Routing Priority>] 
[-upc <UPC Cnfg>] [-lpcr <cellrate>] [-rpcr <cellrate>] [-lscr <cellrate>] 
[-rscr <cellrate>] [-lmcr <cellrate>] [-rmcr <cellrate>] [-prefrte <routeId>]  
[-directrte {yes|no}

Table 4-5 lists and describes the keywords and arguments for the addcon command. The local and remote terms used in this table refer to settings for the local port you are configuring and the remote port at the other end of the connection. If you omit an optional argument, a default value for that argument is used for SPVC configuration.

Caution Once you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections have been deleted. The procedure for changing the SPVC prefix is described in the document entitled Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

Tip If you omit one or more of the configuration arguments when entering the addcon command, the SPVC connection uses the default values listed in Table 4-5, as appropriate. To override the default value for a given argument, enter the argument with a desired value.

Note Enter the cnfchanstdabr command to configure additional ABR arguments. For more information about the cnfchanstdabr command, refer to Chapter 6, "MPSM-T3E3-155 Command Reference."

In the following example, the addcon command defines a port as the slave side of an SPVC connection. Note the slave endpoint ID shown at the end of the display.

mgx8850a.10.MSPM-155[FR] .a > addcon 1 100 1 1 2 36000

slave endpoint added successfully

slave endpoint id : 4700918100000000036B5E309C00000104180100.0.655

Step 4 Write down the NSAP address displayed when the addcon command output is completed. You will need the NSAP address to configure the master side of the SPVC connection.

Tip When you set up the master side of the SPVC, you will need to enter the slave ATM address reported by the addcon command. If you maintain the current session or use the CLI copy command to copy the ATM address now, you can use the CLI paste command to complete the addcon command on the switch that hosts the master side of the SPVC.

Step 5 Enter the dspcons command as follows to verify the addition of the slave side of the SPVC connection. The dspcons command displays all information for the SPVCs.

mpsm_node.5.MPSM155[FR].a > dspcons

record  Identifier     SrvcType    M/S     Upld    Admn         Alarm

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

    0   02 0001000  High Priority   S    0000000b   UP        Multiple        

    1   50 0001000  High Priority   S    0000000c   UP   Condn(A bit from n/w)

Configuring the Master Side of SPVCs

To configure the master side of an SPVC, perform the following steps:

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

Tip During this procedure, you will have to enter the ATM address for the slave end of the connection. If you establish this session from the same workstation you used to create the slave connection, you can use the CLI Copy and Paste commands to avoid data entry errors.

Step 2 Enter the cc <slotnumber> command as follows to change to the MSPM-T3E3-155 card that hosts the master side of the SPVC connection.

mgx8850a.7.PXM45.a > cc <slotnumber>

Replace <slotnumber> with the number of the slot in which the MSPM-T3E3-155 card is installed.

Step 3 Enter the addcon command as follows to define the master side of the SPVC connection.

mgx8850a.10.MSPM-155[FR] .a > addcon <ifNum> <dlci> <chanType> <serviceType> <mastership> 
<cir> [-slave <value> ] [-slavespersflag <slavepers> ]

[-eir <zeroCirEir>] [-bc <Burst Commit>] [-be <Burst Excess>] [-detag <DE Tagging Enable>] 
[-igde <Ignore Incoming DE>] [-fecnmap <FECN map>] [-demap <DE to CLP map>] 
[-clpmap <CLP to DE map>] [-eqsel <Egress Q Select>] [-ingut <Ingress Perc Util>]

[-egut <Egress Perc Util>] [-egrat <Egress Service Rate>] [-rtngprio <Routing Priority>] 
[-upc <UPC Cnfg>] [-lpcr <cellrate>] [-rpcr <cellrate>] [-lscr <cellrate>] [-rscr 
<cellrate>] [-lmcr <cellrate>] [-rmcr <cellrate>]

Table 4-5 lists and describes the keywords and arguments for the addcon command.

Tip If you omit one or more of the optional arguments when entering the addcon command, the connection uses the default values listed in Table 4-5. To override the default value for a given argument, enter the argument with the desired value.

In the following example, the user defines a port as the master side of a double-ended SPVC. Note the master endpoint ID shown in the last line of command output.

M8850_NY.13.MPSM155[FR].a> addcon 2 555 1 1 1 36000 -slave 
4700918100000000036B5E309C00000104180100.0.655

master endpoint added successfully

master endpoint id : 4700918100000000036B5E309C00000104180200.0.655

Step 4 Enter the dspcons command as follows to verify the master-side of the new SPVC connection.

M8850_NY.13.MPSM155[FR].a> dspcons

record  Identifier     SrvcType    M/S     Upld    Admn         Alarm

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

    0   02 0001000  High Priority   S    0000000b   UP        Multiple        

    1   50 0001000  High Priority   S    0000000c   UP   Condn(A bit from n/w)

The dspcons command displays all the connections for the MSPM-T3E3-155 card.

Step 5 Enter the dspcon command as follows to display the configuration information for a specific SPVC.

M8850_NY.13.MPSM155[FR].a> dspcon <ifNum> <dlci>

Replace the <ifNum> argument with the interface or port number of the MSPM-T3E3-155 card. The <dlci> argument (see Table 4-5) establishes the DLCI for the SPVC endpoint.

The following is sample output from the dspcon command.

M8850_NY.13.MPSM155[FR].a> dspcon 50 100

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

Local   :                NSAP  Address                     vpi       vci   

(S)       47009181000000000164436C3D000001051FFF00           98       100  

Remote  :                NSAP  Address                     vpi       vci   

(M)       0000000000000000000000000000000000000000            0         0  

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

Port Number       : 50                    DLCI             : 100       

Conn. Type        : frNIW                 Chan Service Type: High Priority

Conn Service Type : cbr1                  Egress Queue Type: highPriority

Admn Status       : UP                    Oper Status      : FAILED    

Slave Persist     : N/A                   Max Cost         : N/A       

CIR (bps)         : 1000                  BC (bytes)       : 5100      

BE (bytes)        : 5100                  FECN Config      : setEFCIzero

ChanDEtoCLPmap    : mapCLP                ChanCLPtoDEmap   : mapDE     

IngrPercentUtil   : 100                   EgrPercentUtil   : 100

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

DE Tagging        : DISABLED              IgnoreIncomingDE : DISABLED

Pref Rte Id       : 0                     Directed Route   : NO 

Upload            : 0000001a              Routing Priority : 0 

OAM CC Config     : DISABLED              Statistics       : DISABLED

Local Loopback    : ENABLED               UPC              : ENABLED 

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

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

Local PCR (cps)   : 10                    Remote PCR (cps) : 10        

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

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

                  :                       Remote MBS (cps) : N/A       

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

Xmt Abit State    : OFF                   Rcv Abit State   : OFF      

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

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

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

   NO           NO          NO       NO       YES        NO  

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

M8850_NY.13.MPSM155[FR].a>

Step 6 Enter the cc command to change to the active PXM card.

M8850_NY.13.MPSM155[FR].a> cc 7

(session redirected)

pop20two.7.PXM45.a > 

Step 7 Enter the dspcons command as follows to display all connections for the PXM card. the connection you added appears in the Local Port column.

M8850_NY.7.PXM.a > dspcons

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

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

13.5         100 100    Routed       100 100     FAIL      MASTER 8   Persistent

Local  Addr: 47.00918100000000036b5e31b3.0000010d1805.00

Remote Addr: 47.00918100000000001a538943.0000010c1805.00

Preferred Route ID:-    Cast Type: P2P

13.65535    2048 100    Routed         0 0       FAIL      SLAVE  -   Persistent

Local  Addr: 47.00918100000000036b5e31b3.0000010d1fff.00

Remote Addr: 00.000000000000000000000000.000000000000.00

Preferred Route ID:-   Cast Type: P2P

6:1.8:18     100 100    Routed       100 100     OK        MASTER 8   Persistent

Local  Addr: 47.00918100000000036b5e31b3.000001061812.00

Remote Addr: 47.00918100000000036b5e2bb2.00000106180d.00

Preferred Route ID:-    Cast Type: P2P