|
|
A frame relay connection can be setup either from StrataView Plus or via the MGX 8220 command line interface.
Setting up a frame relay connection is normally performed from StrataView Plus using the Connection Manager graphical user interface. An example of the StrataView Plus screen used for making an MGX 8220 frame relay connection is shown in . For full details of how to set up a connection, refer to the Cisco StrataView Plus Operations Guide.
The CLI provides the capability to set up a variety of frame relay connections.
The following paragraphs describe how to establish an end-to-end frame relay connection assuming network interworking and MGX 8220 FRSM end points.
Figure 5-2 shows two BPX nodes in a BPX network in which each of these two nodes is connected to an MGX 8220 shelf via an BNI card. User frame relay equipment, located at "A", is attached to one of the MGX 8220 shelves via a port on the shelf's FRSM card. User frame relay equipment, located at "B", is attached to the other MGX 8220 shelf. This chapter describes how a frame relay connection can be established to permit bidirectional communication between the frame relay equipment at "A" and "B".
To make the connection, the path from "A" to "B" is made up of three segments as shown in Figure 5-2. When using CLI, each segment must be established and configured separately.
Two segments span the BPX backbone from the FRSM to the BNM on the MGX 8220 shelves. These segments are part ATM and part frame relay with the conversion being made in the MGX 8220 shelves.
There is also an ATM trunk segment that spans the BPX backbone network from one of the
BPX nodes to the other BPX node, this segment terminates on a BNI feeder trunk in each node. This segment may include intermediary BPX nodes (not shown in the diagram).
The links between the segments must be configured properly so that the three segments make up one complete end to end connection from "A" to "B". This process consists primarily of ensuring that the VPI between the MGX 8220 shelf and the collocated BPX switch contains the MGX 8220 slot number of the FRSM and the VCI contains the logical channel numbers assigned to the virtual circuit.
To establish an end to end frame relay connection, perform the following step:
This step must be performed on the MGX 8220 shelf at BOTH ends of the connection ("A" and "B").
On the MGX 8220 shelf perform the following steps:
Step 2 Enable the T1 line to be used for the frame relay connection by performing an addln command using the physical FRSM connector number (1 to 4) connected to the T1 line.
Step 3 Configure the T1 line to the frame relay equipment using the cnfln command. Specify parameters as appropriate.
Step 4 Enable the port to the frame relay equipment by performing an addport command using the parameters as follows:
Step 5 Enable the frame relay channel by performing an addchan command.
Select network interworking or service interworking in the chan_type parameter.
1 is for network interworking.
For channel number, enter a value between 16 and 271. THIS WILL BE THE SAME NUMBER SPECIFIED IN THE VCI FIELD TO/FROM THE BPX switch.
For port number, enter the port number previously enabled.
For DLCI, enter a DLCI number to be used in communicating with the frame relay equipment.
At this point the MGX 8220 segment is up with default parameters.
The following steps should be performed to establish the required BPX to BPX segments.
1. Perform an addcon command at one of the BPX nodes (not both) with the following parameters.
2. Specify the other addcon parameters of bandwidth, and so on.
| Parameter | Description |
|---|---|
MCR | Minimum Cell Rate |
PCR | Peak Cell Rate |
% Util | Percentage |
Minimum Cell Rate (MCR) is only used with ForeSight (ATFST).
MCR and Peak Cell Rated (PCR) should be specified according to the following formulae.
MCR = CIR *3/800 cells per second
PCR = AR * 3/800 cells per second but less than or equal to 6000
AR = Frame relay port speed in bps.
For example: | AR equals 64K, PCR = 237, or |
The above MCR and PCR formulae assume the DC version of the MGX 8220 shelf frame size of 100 octets, however, even smaller frame sizes can result in worse case scenarios. For example:
For a frame size of 64 octets the PCR formula becomes | PCR = AR * 2/512 cells per sec |
For a frame size of 43 octets the PCR formula becomes | PCR = AR * 2/344 cells per sec |
% Util should normally be set to the same value as that used for the frame relay segments of the connection.
FRSM service interworking connections are made in the same manner as the network interworking connections except that chan_type in the MGX 8220 addchan command is specified as service interworking (transparent or translation) and the connection end that is remote from the MGX 8220 shelf is an ATM UNI.
These services are setup the same as frame relay except the for port_type in the addchan command which is set as 2 for FUNI or 3 for frame forwarding.
AUSM connections can be setup either through StrataView Plus or via the CLI.
Setting up an AUSM connection is normally performed from StrataView Plus using the Connection Manager graphical user interface. An example of the StrataView Plus screen used for making an MGX 8220 ATM to ATM connection is shown in Figure 5-3. For full details of how to set up a connection, refer to the Cisco StrataView Plus Operations Guide.
Use the following sequence of commands to establish an ATM UNI/NNI connection using the AUSM card. The connection is between a T1 or E1 ATM UNI on the AUSM card and an
ATM service interface elsewhere in the IPX/BPX network.
1. Login to AUSM
2. Issue addln command, specifying the line/port number (between 1 and 4), 1 being the top line/port
3. If required, use cnfln command specifying line code, line length, and clock source
4. Issue upport command specifying the port to be upped
5. Use cnfportq to setup egress queues. Other than defaults you need to specify:
port number (1-4)
queue number (1-16)
queue priority
0 = disable queue
1 = high priority, always serve
2 = best available
3 = Min. guaranteed bandwidth
4 = Min. guaranteed bandwidth with max. rate shaping
5 = CBR with smoothing
service sequence number (1-16)
max. queue depth (1-8000)
CLP low threshold (1-8000)
CLP high threshold (1-8000)
EFCI threshold (1-8000)
6. Use addcon command to add the connection, specifying:
logical connection (LCN 16-271)
connection type (1 = vpc, 2 = vcc)
port number (1-4)
vpi (0-255)
vci (0-65535)
service type (1 = cbr, 2 = vbr, 3 = abr)
queue number (1-16)
7. For configuring UPC, use one of
cnfupc cbr
cnfupc vbr
cnfupc abr
8. Use cnfchanfst to configure ForeSight
9. If queue depths need to be changed, use cnfchanq command
The AUSM 8T1/E1 has a similar command sequence for adding ATM connections for ATM ports.
For IMA ports:
1. addln—on all constituent links
2. cnfln—if required
3. addimagrp—to add the IMA port then follow the command sequence for the ATM ports
The AUSM 8Ti/E1 LCN range is 16 -1015.
For the BPX segment, set up the connection in the same manner as that for FRSM. The connection type should be specified as ABR, CBR, or VBR to match the connection type used at the connection endpoint (for example, AUSM). The parameter values map directly from those specified at the connection endpoint.
Use the following procedure to setup a CESM connection.
Via the Command Line Interface
Setting up a CESM connection is performed through the CLI. The procedure is to first add the line using the add line command (addln) and then add and configure a channel using the add channel (addchan) command. In the addchan command the channel number, the cell delay variation, the cell loss integration period, and buffer size are all specified. The command sequence is:
1. addln <line #>
2. addchan "chan_num CDV CellLossIntegPeriod bufsize"
chan_num -- value ranging from 16 to 19
16 - line 1, 17 - line 2, 18 - line 3, 19 - line 4
CDV -- Cell delay variation:Range 1000-65535 micro seconds
CellLossIntegPeriod -- Cell loss integration period:
Range 1000-65535 milli seconds
bufsize -- egress bufsize: Min value: 0.6(CDV-T1), 0.7(CDV-E1).
Max value: 65535, 0 to auto-compute
Example:
addln 1
addchan 16 10000 2500 0
Posted: Mon Jan 15 22:00:44 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.