|
|
This chapter describes how to configure ATM lines and trunks for communication with other ATM devices. Lines connect the switch to ATM end devices such as Customer Premise Equipment (CPE) and ATM routers. ATM trunks connect the switch to other ATM switches in the core ATM network.
Customer data and voice communications enter through a line, travel over the core network trunks, and depart on another line. This communications path takes place using Soft Permanent Virtual Circuit connections (SPVCs) or Switched Virtual Circuit (SVC) connections. These connections are routed over the ATM core network using the PNNI protocol.
This chapter describes how to configure ATM lines and trunks to support SPVCs, SVCs, and PNNI. Because many of the configuration procedures are required for both lines and trunks, two quickstart configuration sections are provided, one for lines and one for trunks. The balance of the chapter provides procedures for completing the tasks listed in the quickstart sections.
 |
Note For all commands in this chapter, refer to the MGX 8850 Routing Switch Command Reference for detailed information. |
|
Note Before you start configuring ATM connections, you should complete the general switch configuration as described in "Configuring General Switch Features." Some of the procedures described in this chapter will not work if the switch has not been set up properly. |
The quickstart procedure in this section provides a summary of the tasks required to configure ATM trunks on the MGX 8850. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
|
Note The trunk configuration is not complete until the following procedure has been completed on the switches at both ends of the trunk. |
Command | Purpose | |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The quickstart procedure in this section provides a summary of the tasks required to configure ATM lines on the MGX 8850. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections.
|
Note The line configuration is not complete until the equipment at the other end of the line has been configured with compatible configuration settings. |
Command | Purpose | |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The first step in configuring ATM lines and trunks is to define the physical lines and trunks that are connected to the switch. At this configuration level, line and trunk configuration is identical, so lines and trunks are both called lines in the CLI commands.
The following section describe how to do the following:
The switch does not attempt to use a line or trunk until it is defined. Installing an AXSM card can add 1 to 16 lines to your switch, but the switch has no way of knowing which lines are connected to other ATM devices. Bringing up a line tells the switch that you intend to use a line for communications with other ATM devices. You must bring up a line before you can configure the line.
To bring up a line on the switch, use the following procedure.
Step 2 Select the card on which you want to bring up a line with the cc command:
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 3 Enter the upln command after the switch prompt:
mgx8850a.10.AXSM.a > upln <bay.line>
Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Replace line with the number that corresponds to the back card port to which the line is connected. Table 3-1 lists the valid bay numbers and line numbers for each AXSM card. Figure 3-1 illustrates the bay and line numbers used on the MGX 8850.
| Front Card | Valid Line Numbers | Valid Bay Numbers |
|---|---|---|
AXSM-16-155 | 1-8 | 1, 2 |
AXSM-8-155 | 1-4 | 1, 2 |
AXSM-4-622 | 1-4 | 1, 2 |
AXSM-2-622 | 1-2 | 1, 2 |
AXSM-1-2488 | 1 | 1 |
AXSM-16-T3E3 | 1-8 | 1, 2 |
Step 4 Enter the following command:
mgx8850a.10.AXSM.a > dsplns
The line state column shows whether each line is up or down as shown in the following example:
pop2one.10.AXSM.a > dsplns
Medium Medium
Sonet Line Line Line Frame Line Line Alarm
Line State Type Lpbk Scramble Coding Type State
----- ----- ------------ ------ -------- ------ ------- ------
1.1 Up sonetSts12c NoLoop Enable Other Other Critical
1.2 Down sonetSts12c NoLoop Enable Other Other Clear
2.1 Up sonetSts12c NoLoop Enable Other ShortSMF Clear
2.2 Up sonetSts12c NoLoop Enable Other ShortSMF Critical
The line state is reported as down until the line is brought up at the remote end. When a line is reported as up, the physical devices at each end of the line have established physical layer communications. ATM connectivity is established later when interfaces or ports are configured on the line.
All lines are brought up with the same default configuration. After you bring up a line, you can change the default configuration. At the physical communications level, you can configure the following:
The following procedure describes how to configure SONET, DS3, and E3 lines.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 If you do not know the line number you want to configure, enter the dsplns command to display a list of the lines:
mgx8850a.10.AXSM.a > dsplns
Remember that you cannot configure a line until you have brought it up as described in the previous section, "Bringing Up Lines."
Step 3 To configure a SONET line, enter the following commands:
mgx8850a.10.AXSM.a > cnfln -sonet <bay.line> -slt <LineType> -sfs <FrameScramble> -clk <clockSource>
Table 3-2 lists the parameter descriptions for configuring SONET, DS3 and E3 lines. Be sure to use only the parameters listed above for SONET lines.
| Parameter | Line Types Supported | Description |
|---|---|---|
AIScBitsCheck | T3 | The -cb option defines C-bit checking. Set AIScBitsCheck to 1 to enable C-bit checking. Set it to 2 to ignore the C-bit. |
bay | T3 | Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. |
clockSource | T3 | The -clk option selects the source timing for transmitting messages over the line. Replace clockSource with 1 to use the clock signal received over this line from a remote node, or specify 2 to use the local timing defined for the local switch. For information on defining the clock source for the local switch, see "Configuring General Switch Features," "Managing Network Clock Sources." |
FrameScramble | SONET | The -sfs option enables or disables SONET frame scrambling. This setting must match the setting on the remote end of the line. Replace the FrameScramble variable with 1 to disable frame scrambling or 2 to enable frame scrambling. |
line | T3 | Replace line with the number that corresponds to the back card port to which the line is connected. Table 3-1 lists the valid line numbers for each AXSM card. |
LineLength | T3 | The -len option specifies the length of a T3 line from the local node to a remote node in meters. Enter a value between 0 and 64000 meters. |
LineType | SONET | The -slt and -lt options specify the line type. For SONET lines, replace the LineType variable with 1 for SONET or 2 for SDH. For DS3 lines, replace the LineType variable with 1 for ds3cbitadm or 2 for ds3cbitplcp. |
OOFCriteria | T3 | |
RcvFEACValidation | T3 | Replace RcvFEACValidation with 1 to select 4 out of 5 and 2 to select 8 out of 10. |
Step 4 To configure a DS3 line, enter the following command:
mgx8850a.10.AXSM.a > cnfln -ds3 <bay.line> -lt <LineType> -len <LineLength> -oof <OOFCriteria> -cb <AIScBitsCheck> -rfeac <RcvFEACValidation> -clk <clockSource">
Table 3-2 lists the parameter descriptions for configuring SONET, DS3 and E3 lines. Be sure to use only the parameters listed above for DS3 lines.
Step 5 To configure an E3 line, enter the following command:
mgx8850a.10.AXSM.a > cnfln -ds3 <bay.line> -len <LineLength> -clk <clockSource">
Table 3-2 lists the parameter descriptions for configuring SONET, DS3 and E3 lines. Be sure to use only the parameters listed above for E3 lines.
After you configure a line, you can verify the configuration by following the procedure in the next section.
To display the configuration of a line, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 If you don't know the line number you want to view, display a list of the lines by entering the following command:
mgx8850a.10.AXSM.a > dsplns
Step 3 To display the configuration of a single line, enter the following command:
mgx8850a.10.AXSM.a > dspln -type <bay.line>
The following table describes the command parameters.
type | The parameter specifies the type of line that is connected to the switch. Enter -sonet or -ds3. The -ds3 option works for DS3 and E3 lines. |
bay | Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. |
line | Replace line with the number that corresponds to the back card port to which the line is connected. Table 3-1 lists the valid line numbers for each AXSM card. |
The line configuration appears as follows:
pop2one.10.AXSM.a > dspln -sonet 2.1 Line Number : 2.1 Admin Status : Up Alarm Status : Clear Loopback : NoLoop APS enabled : Disable Frame Scrambling : Enable Number of ports : 1 Xmt Clock source : localTiming Number of partitions: 1 Line Type : sonetSts12c Number of SPVC : 0 Medium Type(SONET/SDH) : SONET Number of SVC : 4 Medium Time Elapsed : 248198 Medium Valid Intervals : 96 Medium Line Type : ShortSMF
A Service Class Template (SCT) is a collection of ATM configuration parameter settings that are stored in a single file and can be applied to multiple lines or ports. Instead of retyping configuration data for identical lines or trunks, you can specify an existing SCT to apply those settings to additional lines and trunks. SCT files include the following types of configuration data:
There are two types of SCTs: card SCTs and port SCTs. Card SCTs define parameters that apply to all ingress communications for all lines on a single AXSM card. Port SCTs define parameters that apply to egress communications on a single line or port. You can apply the same SCT to multiple cards or ports. To enable ATM communications, you must assign a card SCT to every card and a port SCT to every port you use.
The SCT files are stored in the C:\SCT\AXSM directory. Cisco provides default SCT files you can use. To create additional SCT files or change the configuration of existing SCT files, you need to use Cisco WAN Manager (CWM). You cannot create or modify SCT files using the CLI.
|
Note After you create a SCT file with CWM, you must FTP that file to the switch before you can use it. For guidelines on transferring files to the switch, see "Copying Firmware Files to the Switch" in "Downloading and Installing Firmware Updates." Be sure to copy SCT files to the C:\SCT\AXSM directory on the switch. |
The following sections describe how to select SCTs for a card and how to display card SCT settings. Port SCTs are selected when you add ports to lines or trunks, and this procedure is discussed later in this chapter.
A card SCT defines ATM parameters that apply to ingress communications for all lines on a card. You can use the same SCT for multiple cards. To select an SCT for a card, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 Enter the following command:
pop20two.9.AXSM.a > cnfcdsct <sctID>
Replace sctID with the number of the SCT that you want to assign to the card. Valid SCT numbers are from 0 to 255, however, a valid SCT file must exist for the number you enter.
A port SCT defines ATM parameters that apply to egress communications on a single port. You can use the same port SCT for multiple ports. To select an SCT for a port, use the addport as described later in "Adding ATM Ports."
To view the card SCT settings, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 Enter the following command:
pop20two.9.AXSM.a > dspcdsct <bw|gen|cosb|vcThr|cosThr>
Select one of the options to display one of the five SCT configuration reports. Table 3-3 describes the reports for each of these options. The following section lists sample reports for each of these options.
|
Note The option names are case sensitive. The switch does not recognize the vcthr option. You must enter vcThr. |
| Option | Description |
bw | Displays bandwidth and policing parameters. |
gen | Displays general SCT parameters. |
cosb | Displays COSB parameters. |
vcThr | Displays virtual circuit threshold parameters. |
cosThr | Displays COSB threshold parameters. |
The following sections display the reports for each of the dspcdsct command options.
The following report appears when you enter the dspcdsct bw command:
pop20two.1.AXSM.a > dspcdsct bw +-----------------------------------------------------------------------------+ Service Class Template [6] : Bw and Policing Parameters +-----------------------------------------------------------------------------+ | SERV-TYPE | PCR | SCR | MCR | MBS | CDVT | ICR | +-----------------------------------------------------------------------------+ | CBR.1 | 00001000 | 00000000 | 00000000 | 00000001 | 00250000 | 00000000 | | VBR-RT.1 | 00001000 | 01000000 | 00000000 | 00000050 | 00250000 | 00000000 | | VBR-RT.2 | 00001000 | 01000000 | 00000000 | 00000050 | 00250000 | 00000000 | | VBR-RT.3 | 00001000 | 01000000 | 00000000 | 00000050 | 00250000 | 00000000 | | VBR-nRT.1 | 00001000 | 01000000 | 00000000 | 00000050 | 00250000 | 00000000 | | VBR-nRT.2 | 00001000 | 01000000 | 00000000 | 00000050 | 00250000 | 00000000 | | VBR-nRT.3 | 00001000 | 01000000 | 00000000 | 00000050 | 00250000 | 00000000 | | UBR.1 | 00000010 | 00000000 | 00000000 | 00000001 | 00250000 | 00000000 | | UBR.2 | 00000010 | 00000000 | 00000000 | 00000001 | 00250000 | 00000000 | | ABR | 00000010 | 00000000 | 01000000 | 00000001 | 00250000 | 00000000 | | CBR.2 | 00001000 | 00000000 | 00000000 | 00000001 | 00250000 | 00000000 | | CBR.3 | 00001000 | 00000000 | 00000000 | 00000001 | 00250000 | 00000000 | +-----------------------------------------------------------------------------+
The following report appears when you enter the dspcdsct gen command:
pop20two.1.AXSM.a > dspcdsct gen +------------------------------------------------------------------------------ Service Class Template [6] : General Parameters +------------------------------------------------------------------------------ | SERV-TYPE | COSB_NUM | CAC_TYPE | UPC_ENB | CLP-SELEC | GCRA-1 | GC +------------------------------------------------------------------------------ | CBR.1 | 00000003 | B-CAC |GCRA1-ENB | 000000003 | DISCARD | | VBR-RT.1 | 00000004 | B-CAC |GCRA 1 & 2| 000000002 | DISCARD | | VBR-RT.2 | 00000004 | B-CAC |GCRA 1 & 2| 000000001 | DISCARD | | VBR-RT.3 | 00000004 | B-CAC |GCRA 1 & 2| 000000001 | DISCARD | | VBR-nRT.1 | 00000005 | B-CAC |GCRA 1 & 2| 000000002 | DISCARD | | VBR-nRT.2 | 00000005 | B-CAC |GCRA 1 & 2| 000000001 | DISCARD | | VBR-nRT.3 | 00000005 | B-CAC |GCRA 1 & 2| 000000001 | DISCARD | | UBR.1 | 00000006 | LCN_CAC |GCRA1-ENB | 000000003 | DISCARD | | UBR.2 | 00000006 | LCN_CAC |GCRA1-ENB | 000000003 | DSCD/SET-CLP | | ABR | 00000001 | B-CAC |GCRA1-ENB | 000000003 | DISCARD | | CBR.2 | 00000003 | B-CAC |GCRA 1 & 2| 000000001 | DISCARD | | CBR.3 | 00000003 | B-CAC |GCRA 1 & 2| 000000001 | DISCARD | +------------------------------------------------------------------------------
The following report appears when you enter the dspcdsct cosb command:
pop20two.1.AXSM.a > dspcdsct cosb +--------------------------------------------------------------------------+ |Service Class Template [06] : COSB Parameters | +--------------------------------------------------------------------------+ | COSB | MIN-RATE | MAX-RATE | MIN-PRIORITY | EXCESS-PRIORITY | ERS ENABLE | +--------------------------------------------------------------------------+ | 0001 | 00000000 | 00000100 | 000 | 002 | ENABLE | | 0002 | 00000000 | 00000100 | 000 | 002 | ENABLE | | 0003 | 00000000 | 00000100 | 000 | 000 | DISABLE | | 0004 | 00000000 | 00000100 | 000 | 001 | DISABLE | | 0005 | 00000000 | 00000100 | 000 | 001 | DISABLE | | 0006 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0007 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0008 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0009 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0010 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0011 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0012 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0013 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0014 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0015 | 00000000 | 00000100 | 000 | 002 | DISABLE | | 0016 | 00000000 | 00000100 | 000 | 002 | DISABLE | +--------------------------------------------------------------------------+
The following report appears when you enter the dspcdsct vcThr command:
pop20two.1.AXSM.a > dspcdsct vcThr +------------------------------------------------------------------------------+ Service Class Template [6] : VC Threshold Parameters +------------------------------------------------------------------------------+ | SERV-TYPE | VC THRESH | PACKET | MAX_CELL | EFCI | CLP_HI | EPD0 | C| | | TBL IDX | MODE | THRESH | | | | | +------------------------------------------------------------------------------+ | CBR.1 | 225 | DSB | 0000002500 | 1000000 | 0800000 | 0600000 | 0| | VBR-RT.1 | 226 | DSB | 0000005000 | 1000000 | 0800000 | 0600000 | 0| | VBR-RT.2 | 227 | DSB | 0000005000 | 1000000 | 0800000 | 0600000 | 0| | VBR-RT.3 | 228 | DSB | 0000005000 | 1000000 | 0800000 | 0600000 | 0| | VBR-nRT.1 | 229 | DSB | 0000025000 | 1000000 | 0800000 | 0600000 | 0| | VBR-nRT.2 | 230 | DSB | 0000025000 | 1000000 | 0800000 | 0600000 | 0| | VBR-nRT.3 | 231 | DSB | 0000025000 | 1000000 | 0800000 | 0600000 | 0| | UBR.1 | 232 | DSB | 0000050000 | 1000000 | 0800000 | 0600000 | 0| | UBR.2 | 233 | DSB | 0000050000 | 1000000 | 0800000 | 0600000 | 0| | ABR | 234 | DSB | 0000050000 | 0200000 | 0800000 | 0600000 | 0| | CBR.2 | 235 | DSB | 0000002500 | 1000000 | 0800000 | 0600000 | 0| | CBR.3 | 236 | DSB | 0000002500 | 1000000 | 0800000 | 0600000 | 0| +------------------------------------------------------------------------------+
The following report appears when you enter the dspcdsct cosThr command:
pop20two.1.AXSM.a > dspcdsct cosThr +------------------------------------------------------------------------------+ Service Class Template [00006] : COSB Threshold Parameters +------------------------------------------------------------------------------+ | COSB |COSB THRESH| MAX_CELL | EFCI | CLP_HI | EPD0 | CLP_LO | RED| | | TBL IDX | THRESH | | | | EPD1 | | +------------------------------------------------------------------------------+ | 0001 | 0000114 | 1000000 | 0200000 | 0800000 | 0600000 | 0800000 | 10000| | 0002 | 0000115 | 1000000 | 0200000 | 0800000 | 0600000 | 0800000 | 10000| | 0003 | 0000116 | 5000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0004 | 0000117 | 10000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0005 | 0000118 | 50000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0006 | 0000119 | 100000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0007 | 0000120 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0008 | 0000121 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0009 | 0000122 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0010 | 0000123 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0011 | 0000124 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0012 | 0000125 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0013 | 0000126 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0014 | 0000127 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| | 0015 | 0000128 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| Type <CR> to continue, Q<CR> to stop: | 0016 | 0000129 | 1000000 | 1000000 | 0800000 | 0600000 | 0800000 | 10000| +------------------------------------------------------------------------------+
Earlier in this chapter, you brought up lines and trunks by specifying the correct line port number. The line ports correspond to line connectors on the switch back cards. Bringing up a line establishes minimal connectivity between two nodes. When you add an ATM port to a line, you enable ATM communications over the line.
Each line can support UNI or NNI ports. UNI ports are used for lines that connect to PBXs, ATM routers, and other ATM devices that connect to the core ATM network through the MGX 8850 Release 2 switch. NNI ports are used for trunks that connect to other core ATM network devices, such as the MGX 8850 Release 2 switch.
You must configure one ATM port for each line or trunk to enable ATM communications over that link. You define the port type (UNI or NNI) when you add the ATM port to the line or trunk.
To add an ATM port to a line, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 If you don't know the line number you want to configure, display a list of the lines by entering the following command:
mgx8850a.10.AXSM.a > dsplns
 |
Tips Remember that you cannot configure a line until you have brought it up as described in the section, "Bringing Up Lines." |
Step 3 To display a list of the ports configured on the AXSM card, enter the following command:
mgx8850a.10.AXSM.a > dspports
This command displays all ports on the AXSM card in the ifNum (interface number) column. The interfaces listed include UNI and NNI ports. Pay attention to the port numbers already in use. When you add a port, you must specify a port number that is unique on the AXSM card. For example, if port number 2 is assigned to line 2.1 (bay 2, line 1), you cannot use port 2 on any other line on that AXSM card.
Step 4 To add an ATM port to a line, enter the following command:
mgx8850a.10.AXSM.a > addport <ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> <ifType> [vpi]
Table 3-4 lists the parameter descriptions for adding ports. Figure 3-2 shows the relationship between logical interface numbers and physical lines.
| Parameter | Description |
|---|---|
ifNum | |
bay | Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Remember that the bay number is always 1 for an AXSM-2-2488. |
line | Replace line with the number that corresponds to the back card port to which the line is connected. Table 3-1 lists the valid line numbers for each AXSM card. |
guaranteedRate | Enter the minimum rate for the port in cells per second (cps). |
maxRate | Enter the maximum rate for the port in cps (this must be the same as guaranteedRate when the port type is UNI or NNI). The rate ranges are as follows: OC48: 50 to 5651328 OC12: 50 to 1412832 OC3: 50 to 353208 T3: 50 to 96000 (PLCP) or 104268 (ADM) E3: 50 to 80000 |
sctID | Enter the egress SCT number (0-255). Entering 0 selects the default SCT. |
ifType | Enter a number that indicates the interface type. Enter 1 for UNI, 2 for NNI, and 3 for VNNI. Note that option 3 (VNNI) is provided for future use. |
vpi | This parameter is provided for future use. |
The following command defines a line port as a UNI T3 line:
mgx8850a.10.AXSM.a > addport 1 1.1 96000 96000 1 1
The following command defines a line port as an OC48 NNI trunk:
mgx8850a.10.AXSM.a > addport 2 2.1 5651328 5651328 2 2
Step 5 To display a list that shows the port you have added, enter the dspports command.
Step 6 To display specific configuration information for a port, use the procedure described in the next section, "Viewing the Port Configuration."
|
Tips To change the port configuration, enter the cnfport command, or enter the delport command to delete a port configuration. You can also activate and deactivate ports using the upport and dnport commands. For more information on these commands, refer to the Cisco MGX 8850 Routing Switch Command Reference. |
To view the configuration of an ATM line or trunk port, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 To display a list of the ports already configured on the AXSM card, enter the following command:
mgx8850a.10.AXSM.a > dspports
This command displays all configured ports on the AXSM card. Port numbers are listed in the ifNum (interface number) column. The interfaces listed include UNI and NNI ports. Note the number of the port for which you want to view the configuration.
Step 3 To display the port configuration, enter the following command:
mgx8850a.10.AXSM.a > dspport <ifNum>
Replace ifNum with the number assigned to the port during configuration. The following example shows the report for this command:
pop20two.9.AXSM.a > dspport 2 Interface Number : 2 Line Number : 2.1 Admin State : Up Operational State : Down Guaranteed bandwidth(cells/sec): 100000 Number of partitions: 1 Maximum bandwidth(cells/sec) : 100000 Number of SPVC : 0 ifType : NNI Number of SVC : 0 SCT Id : 6 VPI number(VNNI only) : 0
After you add a line or trunk port, you need to configure additional ATM parameters to define how that port is used. These parameters include the following:
The MGX 8850 allows you to define multiple configurations for a port. For example, you can create one configuration for VPIs 100 to 200 and another for VPIs 300 to 400. Each of these configurations is called a resource partition, and these resource partitions are identified by numbers. To extend the example in this paragraph, you could create partition 1 that uses VPIs 100 to 200 and gets 25% of the maximum bandwidth, and then you could create partition 2, which uses VPIs 300 to 400 and gets 75% of the maximum bandwidth. Whenever you bring up a line and add a port, you must create at least one resource partition to define ATM communications on that port.
The following sections describe how to add, display, change, and delete resource partitions.
To create a resource partition for a port, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
|
Note You must add the PNNI controller and add a port before you create a resource partition for a port. For instructions on adding the controller, see "Configuring the PNNI Controller," in "Configuring General Switch Features." For instructions on adding ports, see "Adding ATM Ports for Lines and Trunks," which appears earlier in this chapter. |
Step 2 If you don't know the port number to which you want to assign the resource partition, display a list of the ports by entering the following command:
mgx8850a.10.AXSM.a > dspports
This command displays all ports on the AXSM card in the ifNum (interface number) column.
Step 3 To create a resource partition, enter the following command:
mgx8850a.10.AXSM.a > addpart <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> <ingmaxbw> <minVpi> <maxVpi> <minVci> <maxVci> <minConns> <maxConns>
Table 3-5 describes the parameters for this command.
| Parameter | Description |
|---|---|
ifNum | Interface number or port number. This number identifies the port this resource partition configures. Enter the interface number that was assigned to the port when it was configured (see "Adding ATM Ports for Lines and Trunks"). |
ctrlrId | Controller identification number. Enter the number assigned to the controller when it was created (see "Configuring the PNNI Controller," in "Configuring General Switch Features"). |
egrminbw | Egress minimum bandwidth. Enter the minimum percentage of the outgoing port bandwidth that you want assigned to this partition. One percent is equal to 0.00001 units. For example, an egrminbw of 1000000 = 100%. |
egrmaxbw | Egress maximum bandwidth. Enter the maximum percentage of the outgoing port bandwidth that you want assigned to this partition. One percent is equal to 0.00001 units. For example, an egrminbw of 250000 = 25%. |
ingminbw | Ingress minimum bandwidth. Enter the minimum percentage of the incoming port bandwidth that you want assigned to this partition. One percent is equal to 0.00001 units. For example, an egrminbw of 500000 = 50%. |
ingmaxbw | Ingress maximum bandwidth. Enter the maximum percentage of the incoming port bandwidth that you want assigned to this partition. One percent is equal to 0.00001 units. For example, an egrminbw of 750000 = 75%. |
minVpi | Minimum VPI number for this partition. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095. |
maxVpi | Maximum VPI number for this partition. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095. The value for maxVpi cannot be less than for minVpi. |
minVci | Minimum VCI number for this partition. For OC-48 AXSM cards, enter a number in the range from 32 to 131072. For all other cards, enter a number in the range from 32 to 65535. |
maxVci | Maximum VCI number for this partition. For OC-48 AXSM cards, enter a number in the range from 32 to 131072. For all other cards, enter a number in the range from 32 to 65535. |
minConns | Minimum number of simultaneous connections allowed on this partition. For OC-48 AXSM cards, enter a number in the range from 32 to 131072. For all other cards, enter a number in the range from 32 to 65535. |
maxConns | Maximum number of simultaneous connections allowed on this partition. For OC-48 AXSM cards, enter a number in the range from 32 to 131072. For all other cards, enter a number in the range from 32 to 65535. |
Step 4 To display a list showing the partition you have created, enter the following command:
mgx8850a.10.AXSM.a > dspparts
The following sections describe how to display the configuration for a specific partition and how to change its configuration or delete it.
To display a list of resource partitions or a resource partition configuration, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 To display a list showing the resource partitions on this card, enter the following command:
mgx8850a.10.AXSM.a > dspparts
The switch displays a report similar to the following:
pop20two.9.AXSM.a > dspparts
if part Ctlr egr egr ingr ingr min max min max min max
Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn
(.0001%)(.0001%)(.0001%)(.0001%)
-----------------------------------------------------------------------------
2 2 2 1000000 1000000 1000000 1000000 0 4000 32 4000 0 4000
3 2 2 1000000 1000000 1000000 1000000 0 255 32 2000 0 2000
Step 3 To display the configuration of a resource partition, note the partition number and enter the following command:
mgx8850a.10.AXSM.a > dsppart <ifNum> <partId>
Table 3-5 describes the parameters for this command. The following example shows the report provided by the dsppart command.
pop20two.9.AXSM.a > dsppart 2 2 Interface Number : 2 Partition Id : 2 Number of SPVC: 0 Controller Id : 2 Number of SVC : 4 egr Guaranteed bw(.0001percent): 1000000 egr Maximum bw(.0001percent) : 1000000 ing Guaranteed bw(.0001percent): 1000000 ing Maximum bw(.0001percent) : 1000000 min vpi : 0 max vpi : 4000 min vci : 32 max vci : 4000 guaranteed connections : 0 maximum connections : 4000
To change the configuration of a resource partition, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 To display a list showing the partitions for this card, enter the dspparts command.
Step 3 To create a resource partition, enter the following command:
mgx8850a.10.AXSM.a > cnfpart -if <ifNum> -id <partId> -emin <egrminbw> -emax <egrmaxbw> -imin <ingminbw> -imax <ingmaxbw> -vpmin <minVpi> -vpmax <maxVpi> -vc min <minVci> -vc max <maxVci> -mincon <minConns> -maxcon <maxConns>
Table 3-5 describes the parameters for this command.
Step 4 To display the changed partition configuration, use the dsppart command as described in the previous section.
To delete a resource partition, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the AXSM card is installed. Valid slot numbers are from 1 to 6 and 9 to 14. Verify your card selection by viewing the switch prompt, which should list the slot number and the AXSM card type.
Step 2 To display a list showing the partitions for this card, enter the dspparts command.
Step 3 To delete a resource partition, enter the following command:
mgx8850a.10.AXSM.a > delpart <ifNum> <partId>
Table 3-5 describes the parameters for this command.
Step 4 To verify that the partition has been deleted, enter the dspparts command to display a list of partitions for the card.
Each port on the MGX 8850 can be configured with a static ATM address, or it can be configured to dynamically generate an ATM address using an ATM address prefix that you supply. Your choice of ATM addressing for each UNI port must match the capabilities of the remote equipment. For example, if the remote CPE cannot accept a dynamically generated ATM address, you must define a static ATM address for the port. The following sections describe how to define static and dynamic addressing for UNI ports.
Use the following procedure to create a static address for a UNI port.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 To locate the port to which you want to add an address, enter the dsppnports command.
Step 3 Use the following command to turn off automatic address registration on the port that will use the static address:
popeye2.7.PXM.a > cnfaddrreg <portid> no
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
| Parameter | Description |
|---|---|
slot | Enter the slot number for the card that hosts the port you are configuring. |
bay | Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay. Remember that the bay number is always 1 for an AXSM-2-2488. |
line | Replace line with the number that corresponds to the back card port to which the line is connected. Table 3-1 lists the valid line numbers for each AXSM card. |
ifNum | An ATM port is also called an interface. Enter a number from 1 to 60 to identify this interface. The interface number must be unique on the card to which it is assigned. An ATM port is defined by its slot, bay, line, and interface numbers. You do not have to enter a slot number during port configuration because you identify the slot number when you select the card. |
Step 4 Specify an ATM address for the port using the following command:
popeye2.7.PXM.a > addaddr <portid> atm-address length [-type {int | ext}] [-proto {local | static}] [-plan {e164 | nsap}] [-scope scope] [-redistribute {yes | no}]
Table 3-7 describes the parameters for this command.
| Parameter | Description |
|---|---|
portid | Port identifier in the format slot[:bay].line[:port]. These parameters are described in Table 3-6. |
atm-address | Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits. |
length | Enter the length, in bits, of the address you specified with the atm-address parameter. Each nibble is equal to 4 bits. The acceptable range for the parameter is from 0 to 160 bits. |
-type | Type of reachability. Enter either int for internal or ext for external. Default = int. |
-proto | Routing mechanism by which connectivity from the advertising node to the reachable address is to be learned. Enter either local or static. Default = local. |
-plan | Enter the address plan, which is either e164 (E.164) or nsap (NSAP). For an NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD. Default = nsap. |
scope | PNNI scope of advertisement (as in level of PNNI hierarchy) of the reachability from the advertising node to the address. Range: 0 through 104. |
-redistribute | Specifies whether or not the ATM should be distributed. Enter yes to enable distribution and enter no to disable. Default = no. |
The following example assigns an ATM address to port 9:1.2:2:
popeye2.7.PXM.a > addaddr 9:1.2:2
47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 160 length:160 type:internal proto:local > scope:0 plan:nsap_icd redistribute:false
Step 5 To verify that the new address has been assigned, enter the following command:
popeye2.7.PXM.a > dspaddr <portid>
Replace portid with the port address using the format slot[:bay].line[:port]. These parameters are described in Table 3-6.
The following example shows the report from the dspaddr command.
popeye2.7.PXM.a > dspaddr 9:1.2:2 47.2222.2222.2222.2222.2222.2222.2222.2222.2222.22 length:160 type:internal proto:local scope:0 plan:nsap_icd redistribute:false
If you create a static ATM address and later want to remove that address, you can do so by using the following procedure.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 To locate the port for which you want to delete an address, enter the dsppnports command.
Step 3 Use the following command to delete the static address:
popeye2.7.PXM.a > deladdr <portid> <atm-address> <length> [-plan {e164|nsap}]
The command parameters are described in Table 3-7.
Step 4 To verify that the static address has been deleted, enter the following command:
popeye2.7.PXM.a > dspaddr <portid>
Replace portid with the port address using the format slot[:bay].line[:port]. These parameters are described in Table 3-6.
For dynamic addressing to work on a port, the remote device must support it. ILMI versions 3.x and 4.0 support dynamic address registration.When a port is configured for dynamic addressing, the ILMI protocol within the switch provides a 13-byte ATM address prefix to the remote node. The remote node then completes the ATM address and responds to the switch. When both the remote node and the switch agree on a dynamic address, that address is assigned to the port.
Use the following procedure to enable dynamic addressing for a UNI port and to assign an ATM address prefix to the port.
|
Note The PXM45 supports up to 255 prefixes per service module. |
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 Use the following command to down the port so that it can be configured:
popeye2.7.PXM.a > dnpnport <portid>
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
Step 3 Use the following command to turn on automatic address registration on the port that will use dynamic addressing:
popeye2.7.PXM.a > cnfaddrreg <portid> yes
|
Note Dynamic addressing is enabled by default. This command is required only when dynamic addressing has been disabled. |
Step 4 Use the following command to define an ATM prefix for a port:
popeye2.7.PXM.a > addprfx <portid> atm-prefix
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
Replace atm-prefix with the 13-byte ATM address prefix that you want the dynamically assigned address to use. Specify the address prefix using 26 hexadecimal digits. Each hexadecimal digit represents 1 nibble (1 byte = 2 nibbles).
Step 5 Use the following command to bring up the configured port:
popeye2.7.PXM.a > uppnport <portid>
Step 6 To verify the proper ATM prefix configuration for a port, enter the following command:
popeye2.7.PXM.a > dspprfx <portid>
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
|
Tips To delete an ATM address prefix, use the delprfx command as described in the Cisco MGX 8850 Routing Switch Command Reference. |
The following sections describe how to add and configure PNNI ports, as well as how to configure a PNNI port range.
To prepare a port for PNNI routing, use the following procedure.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 Add a port to PNNI by entering the following command:
pop20two.7.PXM.a > addpnport <portid>
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
Step 3 To display a list of PNNI ports, which should include the port you added, enter the dsppnports command.
To configure PNNI port signaling for a specific port, use the following procedure.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 Use the following command to bring down the PNNI port you want to configure:
popeye2.7.PXM.a > dnpnport <portid>
A PNNI port is automatically brought up when you add it. You must down the port before you can change the port configuration. Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
Step 3 To confirm the port is down, enter the dsppnports command. The following example shows the report that appears.
popeye2.7.PXM.a > dsppnports
Summary of total connections(p2p=point to point,p2mp=point to multipoint)
Type #Svcc: #Svpc: #SpvcActive: #SpvcCfg: #SpvpActive: #SpvpCfg: T:
p2p: 0 0 0 0 0 0
p2mp: 0 0 0 0 0 0
Total
Per-port status summary
PortId IF status Admin status ILMI state Total Activeconns
9:1.1:1 down down Disable 0
Step 4 To configure the PNNI port signaling, enter the following command:
pop20two.7.PXM.a > cnfpnportsig <portid> [-univer {uni30|uni31|uni40|none}] [-nniver {iisp30|iisp31|pnni10}] [-unitype {public|private}] [-addrplan {both|aesa|e164}] [-side {user|network}] [-vpi <vpi>] [-sigvci <signalling-vci>] [-rccvci <routing-vci>]
The only required parameter for this command is the portid parameter, but the command serves no purpose if you don't enter at least one option with it. If you include some options with the command and omit others, the omitted option remain set to the last configured value. Table 3-8 lists and describes the options and parameters for this command.
| Parameter | Description |
|---|---|
portid | Port identifier in the format slot[:bay].line[:port]. These parameters are described in Table 3-6. |
-univer | When configuring PNNI signaling for a UNI port, you can use this option to specify which version of UNI signaling you want the port to use. You can select UNI version 3.0 (uni30), UNI version 3.1 (uni31), or UNI version 4.0 (uni40). If this port will use NNI signaling, set the value to none. The default value is uni31. |
-nniver | When configuring PNNI signaling for an NNI port, you can use this option to specify which signaling protocol you want the port to use. You can select IISP version 3.0 (iisp30), IISP version 3.1 (iisp31), or PNNI version 1.0 (pnni10). The default value is pnni10. |
-unitype | When configuring PNNI signaling for a UNI port, you can use this option to specify the UNI type. You can define the port as a private UNI port (private) or as a public UNI port (public). The default value is private. |
-addrplan | When configuring PNNI signaling for a UNI port, this parameter specifies the ATM address plan used on this port. You can select AESA (aesa), E.164 (e164), or both (both). The default value is aesa. |
-side | Defines the role of the signaling service used on the port. This parameter applies to IISP ports when static addressing is used (address registration is disabled). If this is a UNI connection or an NNI connection within the network, select network. For connections to other networks, you might need to select user (this is negotiated with the administrators of the other network). The default value is network. |
-vpi | Defines the vpi for signaling services on this port. Enter a value in the range from 0 to 4095. The default value is 0. |
-sigvci | Defines the VCI for signaling services on this port. The default value is 5, which is the well-known, reserved VCI for signaling services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range from 32 to 65535 (otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0). |
-rccvci | Defines the VCI for the PNNI routing control channel (RCC) on this port. The default value is 18, which is the well-known, reserved VCI for this services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range of 32 to 65535 (otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0). |
|
Note The selection of UNI or NNI is made when the port is added with the addport command. You cannot use the -univer and -nniver options to change the port type. |
The following example illustrates how to configure an NNI port to use PNNI Version 1.0 signaling.
popeye2.7.PXM.a > cnfpnportsig 9:1.1:1 -nniver pnni10
Step 5 Use the following command to bring up the PNNI port you just configured:
popeye2.7.PXM.a > uppnport <portid>
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
Step 6 To verify the status of the PNNI port, enter the dsppnports command.
Step 7 To display the configuration of the PNNI port, enter the following command:
popeye2.7.PXM.a > dsppnport <portid>
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters. The following example shows the report for this command.
popeye2.7.PXM.a > dsppnport 9:1.1:1 > Port: 9:1.1:1 Logical Id: 17373185 > IF status: up Admin Status: up Auto-config: enable Addrs-reg: enable IF-side: network IF-type: nni UniType: private version: pnni10 Input filter: 0 Output filter: 0 minSvccVpi: 0 maxSvccVpi: 1000 minSvccVci: 32 maxSvccVci: 1000 minSvpcVpi: 1 maxSvpcVpi: 1000
When you add a partition to a port, you define the minimum and maximum VPIs and VCIs for that port. These VPIs and VCIs become available for all services unless you make additional configuration changes. When you configure a PNNI port range, you can define the minimum and maximum values for the following:
To configure a PNNI port range for a specific port, use the following procedure.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 To display a list of PNNI ports, enter the dsppnports command.
Step 3 Use the following command to bring down the PNNI port you want to configure:
popeye2.7.PXM.a > dnpnport <portid>
A PNNI port is automatically brought up when you add it. You must down the port before you can change the port range. Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
Step 4 To configure the port range, enter the following command:
popeye2.7.PXM.a > cnfpnportrange <portid> [-minsvccvpi <min-svcc-vpi>] [-maxsvccvpi <max-svcc-vpi>]] [-minsvccvci <min-svcc-vci>] [-maxsvccvci <max-svcc-vci>]] [-minsvpcvpi <min-svpc-vpi>] [-maxsvpcvpi <max-svpc-vpi>]]
The only required parameter for this command is the portid parameter, but the command serves no purpose if you don't enter at least one option with it. If you include some options with the command and omit others, the omitted option remains set to the last configured value. Table 3-9 lists and describes the options and parameters for this command.
| Parameter | Description |
|---|---|
portid | Port identifier in the format slot[:bay].line[:port]. Table 3-6 describes these parameters. |
min-svcc-vpi | Minimum VPI value for SVCC. Range: 0 to 4095 |
max-svcc-vpi | Maximum VPI value for SVCC Range: 0 to 4095 |
min-svcc-vci | Minimum VCI value for SVCC Range: 32 to 65535 |
max-svcc-vci | Maximum VCI value for SVCC. Range: 32 to 65535 |
min-svpc-vpi | Minimum VPI value for SVPC. Range: 1 to 4095 |
max-svpc-vpi | Maximum VPI value for SVPC. Range: 1 to 4095 |
Step 5 Use the following command to bring up the PNNI port you just configured:
popeye2.7.PXM.a > uppnport <portid>
Replace portid using the format slot[:bay].line[:ifNum]. Table 3-6 describes these parameters.
Step 6 To display the PNNI port range for a port, enter the following command:
popeye2.7.PXM.a > dsppnportrange <portid>
After you enter this command, the switch displays a report similar to the following example.
pop20two.7.PXM.a > dsppnportrange 1:2.1:2 minSvccVpi: 0 maxSvccVpi: 4095 minSvccVci: 32 maxSvccVci: 65535 minSvpcVpi: 1 maxSvpcVpi: 4095
This release of the MGX 8850 supports PNNI routing of switched virtual circuits (SVCs). SVCs are the solution for on-demand connections. They are set up as needed and torn down when no longer needed. To achieve this dynamic behavior, SVCs use signaling. End systems request connectivity to other end systems and, provided that certain criteria are met, the connection is set up at the time of the request. When idle, an SVC is torn down to save network bandwidth, and it can reestablished later when needed.
MGX 8850 switches use the PNNI protocol to develop a logical map of the network. This logical map allows switches to work together to determine how to set up SVCs through the network. PNNI enables automatic SVC configuration, which greatly reduces the time required to set up new networks.
The following sections describe the requirements for setting up SVCs and how to display active SVCs.
Because the switch automatically sets up SVCs for you, you do not have to configure SVC routes. However, the switch must be configured correctly before it can set up SVCs. All the procedures for setting up the switch have been discussed earlier in this chapter. The following list summarizes the key steps required in configuring the switch to support SVCs:
|
Note The addresses you assign to each port must conform to the addressing scheme for PNNI in your network. For more information on selecting addresses for PNNI routing, see "Address Selection, Call Routing, and WAN Switching Using the PNNI Protocol." |
To display active SVCs, use the following procedure.
mgx8850a.7.PXM.a > cc <slotnumber>
Step 2 Enter the following command:
popeye2.7.PXM.a > dsppncons
The following is an example report for the dsppncons command.
popeye2.7.PXM.a > dsppncons
Port VPI VCI CallRef X-Port VPI VCI CallRef Type OAM-Type
9:1.1:1 0 32 1 9:1.2:2 0 36 5 PTP No
Calling-Addr:47.666666666666666666666666.666666666666.00
Called-Addr: 47.111111111111111111111111.111111111111.64
9:1.2:2 0 36 5 9:1.1:1 0 32 1 PTP No
Calling-Addr:47.666666666666666666666666.666666666666.00
Called-Addr: 47.111111111111111111111111.111111111111.64
A Soft Permanent Virtual Circuit (SPVC) is a Permanent Virtual Circuit (PVC) that can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. As with PVCs, SPVCs are full-time connections. A PVC, however, uses a predefined circuit path and will fail if the path is interrupted. Using the PNNI protocol, SPVCs can be rerouted to avoid failed communication links or to use links that offer better bandwidth.
The SPVC node prefix is the ATM prefix that PNNI uses for identifying the node within the PNNI network. There is just one SPVC node prefix per node, and you must configure the SPVC node prefix at each node that participates in the PNNI network. To configure the SPVC node prefix, use the following procedure.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 Use the following command to find out if the SVPC node prefix has already been defined:
pop20two.7.PXM.a > dspspvcprfx
If the SPVC node prefix has already been defined, a report appears that is similar to the following:
pop20two.7.PXM.a > dspspvcprfx SPVC Node Prefix: 47.00918100000000001a531c2a
Step 3 To create or change the SPVC node prefix, enter the following command:
pop20two.7.PXM.a > cnfspvcprfx <prefix>
Replace prefix with the 13-byte prefix you want to use.
|
Note The SPVC node prefix for each node must be unique within the network. |
Step 4 Verify the correct entry of the prefix by entering the dspspvcprfx command.
SPVCs are created between two nodes and must be configured on each node. The master node is responsible for routing and rerouting. The slave node is responsible for responding to requests from the master during connection setup and rerouting.
The master and slave relationships exist for each SPVC and apply only to that connection. For example, you can have define one SPVC with a master on Node A and a slave on Node B, and then create another with the Master on Node B and the slave on Node A. It is good design practice to distribute the master side of SPVCs among the network nodes so that the SPVC route processing task is distributed.
The following sections describe how to configure slave and master SPVC connections.
To configure the slave side of an SPVC, use the following procedure.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 Verify that the node hosting the master side of the SPVC is connected to the network and reachable by entering the following command:
pop2one.7.PXM.a > dsppnni-reachable-addr local
You will need to know the remote node's SPVC node prefix to recognize it in the report that appears. The following is an example report:
pop2one.7.PXM.a > dsppnni-reachable-addr local scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.0000.1a53.1c2f.0000.010a.1802/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.0000.1a53.1c2f.0000.010a.1803/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.0000.1a53.1c2a.0000.1a53.1c2f/152
If the remote node does not appear in the list, enter the dsppnni-link command locally and on the remote node to verify that both nodes have PNNI links. Also, verify that the SPVC node address has been set on both the local and remote nodes.
Step 3 Use the following command to select the AXSM card that hosts the slave side of the SPVC:
mgx8850a.7.PXM.a > cc <slotnumber>
Step 4 Define the slave side of the SPVC by entering the following command:
mgx8850a.10.AXSM.a > addslave <portId> <vpi> <vci> <serviceType>
[-lpcr <cellrate>] [-rpcr <cellrate>] [-lscr <cellrate>] [-rscr <cellrate>]
[-lmbs <cells>] [-rmbs <cells>] [-lcdvt <time>] [-rcdvt <time>]
[-lcdv <time>] [-rcdv <time>] [-lctd <time>] [-rctd <time>]
[-cc <1|0>] [-stat <1|0>] [-frame <1|0>] [-mxc <1|0>]
Table 3-10 lists and defines the parameters and options for this command. If you omit an option, the SPVC uses the default value.
|
Note The options you set with the addslave command must match the options set with the addmaster command, and they must be valid and appropriate for the lines at each end. The default values for each option are defined as percentages of the line bandwidth and will be correct for identical line types. However, the default values will not work for different line types. For example, the default values for a T3 line will not match the default values for OC3 line. |
| Parameter | Description |
|---|---|
portid | Enter the port ID for the line to which this SPVC will connect. Enter the port identifier in the format slot[:bay].line[:port]. Table 3-6 describes these parameters. |
vpi | Enter the VPI for the slave side of the SPVC. UNI Range: 1 to 255 |
vci | Enter the VCI for the slave side of the SPVC. Range: 32 to 65535 |
serviceType | Replace with the number that corresponds to the requested service type for this SPVC (this value must be identical on master and slave sides): cbr1 = 1 |
slave_nsap.vpi.vci | This parameter is used only with the addmaster command and identifies the slave side of the SPVC. The value entered here should match the NSAP displayed after the addslave command is run. The slave_nsap portion of the address corresponds to the remote ATM address and the vpi and vci parameters correspond to the VPI and VCI settings for the slave. The periods between slave_nsap and vpi and between vpi and vci are required. |
-lpcr> | These options specify the local (-lpcr) and remote (-rpcr) Peak Cell Rate (PCR) for the SPVC. Range: 3 to 5651328 cells/sec |
-lscr | These options specify the local (-lscr) and remote (-rscr) Sustained Cell Rate (SCR) for the SPVC. Range: 3 to 5651328 cells/sec |
-lmbs | These options specify the local (-lmbs) and remote (-rmbs) Maximum Burst Size (MBS) for the SPVC. Range: 0 to 2147483647 cells/sec |
-lcdvt | These options specify the local (-lcdvt) and remote (-rcdvt) Cell Delay Variation Tolerance (CDVT) for the SPVC. Range: 0 to 2147483647 microseconds |
-lcdv | These options specify the local (-lcdv) and remote (-rcdv) Cell Delay Variation (CDV) for the SPVC. Range: 0 to 2147483647 microseconds |
-lctd | These options specify the local (-lctd) and remote (-rctd) Cell Transfer Delay (CTD) for the SPVC. Range: 0 to 2147483647 microseconds |
-cc | This option enables or disables the flow of Operation, Administration, and Maintenance (OAM) traffic on the SVPC. Enter 1 to enable OAM traffic flow, or enter 0 to disable traffic flow. |
-stat | This option enables or disables statistics collection for the SPVC. Enter 1 to enable OAM statistics collection, or enter 0 to disable it. |
-frame | This option enables or disables frame discard. Enter 1 to enable frame discard, or enter 0 to disable it. |
-mxc | This option enables or disables cost based routing. Enter 1 to enable this feature, or enter 0 to disable it. |
Step 5 Note the NSAP address the switch displays when the addslave command is complete. You will need this to configure the master side of the SPVC.
Step 6 Verify the slave-side SPVC addition by entering the following command:
pop2one.10.AXSM.a > dspchans
The switch displays a report similar to the following:
pop2one.10.AXSM.a > dspchans
record Identifier Type SrvcType M/S Upld Alarm
------ ---------- ---- -------- --- ---- -----
0 03.0001.00032 VCC vbr1nrt M 0000720d multiple
1 03.0001.00033 VCC vbr1nrt S 00007803 multiple
To configure the master side of an SPVC, use the following procedure.
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM card is installed. Valid slot numbers are 7 and 8.
Step 2 Verify that the node hosting the slave side of the SPVC is connected to the network and reachable by entering the following command:
pop2one.7.PXM.a > dsppnni-reachable-addr local
You will need to know the remote node's SPVC node prefix to recognize it in the report that appears. The following is an example report:
pop2one.7.PXM.a > dsppnni-reachable-addr local scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.0000.1a53.1c2f.0000.010a.1802/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.0000.1a53.1c2f.0000.010a.1803/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.0000.1a53.1c2a.0000.1a53.1c2f/152
If the remote node does not appear in the list, use the dsppnni-link command locally and on the remote node to verify that both nodes have PNNI links. Also, verify that the SPVC node address has been set on both the local and remote nodes.
Step 3 Use the following command to select the AXSM card that hosts the master side of the SPVC:
mgx8850a.7.PXM.a > cc <slotnumber>
Step 4 Define the master side of the SPVC by entering the following command:
mgx8850a.10.AXSM.a > addmaster <portId> <vpi> <vci> <serviceType> <slave_nsap.vpi.vci> [-lpcr <local-pcr>] [-rpcr <remote-pcr>]
Table 3-10 lists and defines the parameters and options for this command. If you omit an option, the SPVC uses the default value.
Step 5 Verify the master-side SPVC addition by entering the following command:
pop2one.10.AXSM.a > dspchans
The switch displays a report similar to the following:
pop2one.10.AXSM.a > dspchans
record Identifier Type SrvcType M/S Upld Alarm
------ ---------- ---- -------- --- ---- -----
0 03.0001.00032 VCC vbr1nrt M 0000720d multiple
1 03.0001.00033 VCC vbr1nrt S 00007803 multiple
Step 6 To display the configuration for a single channel, enter the following command:
pop20two.9.AXSM.a > dspcon ifNum vpi vci
Replace the ifNum parameter with the interface or port number. The vpi and vci parameters are described in Table 3-10. The following example shows a dspcon command report.
pop2one.10.AXSM.a > dspcon 3 1 32 -------------------------------------------------------------------------- Local : NSAP Address port vpi vci (M) 4700918100000000001A531C2F0000010A180300 1.10.03 1 32 Remote : NSAP Address port vpi vci (S) 4700918100000000001A531C2A00000101180300 1.01.03 1 32 -------------------------------------------------------------------------- Conn. Type : VCC Admn Status : ADMN-UP Service Type : vbr1nrt Rtng Status : 2 Controller : 2 -------------------------------------------------------------------------- Local PCR : 90 Remote PCR : 90 Local SCR : 90 Remote SCR : 90 Local CDV : -1 Remote CDV : -1 Local CTD : -1 Remote CTD : -1 Local MBS : 50 Remote MBS : 50 Local CDVT : -1 Remote CDVT : -1 Max. cost : -1 Frame discard: N -------------------------------------------------------------------------- OAM CC Config : DISABLED Statistics : DISABLED -------------------------------------------------------------------------- Loopback Type : No Lpbk | Dir: N/A | Status: No Lpbk | RTD: 0 us -------------------------------------------------------------------------- Type <CR> to continue, Q<CR> to stop: -------------------------------------------------------------------------- Port side Tx : normal Swth side Tx : AIS Port side Rx : normal Swth side Rx : AIS -------------------------------------------------------------------------- I-AIS/RDI E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch NO YES NO NO YES NO --------------------------------------------------------------------------
Step 7 Use the following command to change back to the active PXM45 card:
mgx8850a.10.AXSM.a > cc <slotnumber>
Replace slotnumber with the number of the slot in which the active PXM45 card is installed. Valid slot numbers are 7 and 8.
Step 8 Enter the following command to see the SPVCs:
pop20two.7.PXM.a > dspspvcs
If the SPVC was created successfully, it will appear in the report for this command. The following is an example report.
Local Port Vpi.Vci Remote Port Vpi.Vci State Owner ----------------------------+-----------------------------+-------+------ 1:2.2:3 1 32 Routed 0 0 FAIL SLAVE Local Addr: 47.00918100000000001a531c2a.000001011803.00 Remote Addr: 00.000000000000000000000000.000000000000.00 1:2.2:3 1 33 Routed 1 33 FAIL MASTER Local Addr: 47.00918100000000001a531c2a.000001011803.00 Remote Addr: 47.00918100000000001a531c2f.0000010a1803.00
Posted: Mon Aug 7 08:38:15 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.