|
|
A stand-alone application is defined as one in which the MGX 8220 shelf is connected to some device (router or ATM switch) other than a BPX 8620.
The interface between MGX 8220 shelf and the connected device must be ATM UNI/NNI over either T3, E3, nxT1, nxE1, or OC-3c as shown in Figure 6-1.
This chapter provides guidance in those areas of configuration that are peculiar to the stand-alone configurations.
This chapter makes reference to the MGX 8220 command-line interface (CLI) commands. Details of these commands are found in the Cisco MGX 8220 Command Reference.
A stand-alone MGX 8220 shelf cannot be configured from CWM and must be configured using the MGX 8220 CLI. This may be achieved either through an in-band connection over the ATM link, or through one of the out-of-band options (maintenance, control, or Ethernet ports on the ASC).
To create an in-band access to the MGX 8220 shelf
1. Use an out-of-band method to configure the MGX 8220 IP address to 37. Enter the cnfifip command.
2. Configure the IP address on the connected router or ATM switch
3. The MGX 8220 shelf uses a VPI of 3 and VCI of 8 for in-band access. The connected router or ATM switch must be able to support these values. Configure the router or switch for these VPI/VCI values.
4. From the ATM network, telnet into the MGX 8220 address. The login prompt should appear.
The MGX 8220 options for out-of-band access are
See Chapter 3, "Managing the Cisco MGX 8220 Shelf."
In stand-alone applications, the Annex-G ATM LMI must be disabled in order to suppress ATM LMI related connection alarms. This is achieved by looping back Annex-G LMI messages within the MGX 8220 shelf. Enter the addlmiloop command.
The loopback can be confirmed with the dsplmiloop command and the response of "AtmLmiLoopBack: Loop."
In stand-alone applications, the BNM card interface format must be configured to UNI before connections can be provisioned. You need to enter the cnfbnmif command to specify the "interface format" parameter as 2 (for UNI).
The BNM interface format is preserved in the BRAM (battery-backed RAM) of the ASC card(s) and need not be reconfigured. The clrallcnf command will not modify the BNM interface format.
Display the current BNM interface format by entering the following command:
The current BNM interface format (in this case, STI) is displayed.
Use the following syntax to configure the BNM interface:
<interfaceFormat> = 2-3, 2: UNI, 3: NNI
Configure the BNM interface to UNI format,
If the BNM-T3 card is being used, the ATM line must be configured with PLCP.
The interface format can be confirmed with the dspbnmif command and the response of "bnmLineInterfaceFormat: bnmUni."
In stand-alone applications, trap managers are configured through the CLI entering either the cnftrapmgr command or the addtrapmgr command.
Trap managers registered (added) entering the cnftrapmgr command will age. That is to say the trap manager will be disabled automatically after 30 minutes and must be reregistered if it is to continue to exist. The function of reregistering is normally accomplished by the Cisco WAN Manager (CWM), but since CWM cannot be used for stand-alone applications, there is no method for reregistering trap managers.
In stand-alone applications, therefore, the addtrapmgr command should be entered to register a trap manager. Using this command the trap manager does not age and exists until de registered by the deltrapmgr command. Once a trap manager is registered by the addtrapmgr command it can be modified by the cnftrapmgr command and the trap manager will still not age.
Current trap managers can be displayed using either the dsptrapmgrs or dsptrapmgr commands. The dsptrapmgrs command displays all current trap managers but does not include time-out information. The dsptrapmgr command displays the status for a single specified trap manager including the time-out status.
Refer to the Cisco MGX 8220 Command Reference for details of these commands.
When creating connections on the MGX 8220 shelf the user does not explicitly assign VPI and VCI values. Instead, the MGX 8220 shelf takes user-entered values such as DLCI, LCN, and so forth, and uses mapping algorithms to calculate VPI/VCI values. In stand-alone applications, the user needs to know how this mapping works since these VPI and VCI values must be configured into the connected router or ATM switch.
For FRASM and AUSM VC connections, the user associates a logical channel number (LCN) with the connection DLCI for a service module in a particular slot. The card's slot number is used as the value for the VPI and the LCN is used as the value for the VCI.
The VPI, therefore, is a number in the range of 5 to 14 (the range of permissible slots for service modules in the MGX 8220).
The VCI range is determined by the service module type and is 16 to 271 for 4-port FRAM and AUSM modules and 16 to 1015 for 8-port modules.
For AUSM VP connections, the situation is more complicated. The CPE port VPI value will most likely be different from the network VPI. Depending upon the BNM interface format (UNI or NNI), the range of VPI values is evenly divided among the 10 service module slots. During the process of adding a VP connection, the user is asked to assign a VP ID where the VPID is an index corresponding to the VPI within the assigned range.
The ranges of VPID for the various service modules are shown in Table 6-1.
There are two methods that can be used to identify the network VPI associated with an AUSM VP connection.
The first method is to enter the dspadrxlat command. This command lists all the VC and VP connections currently existing on the shelf in slot number/channel number order showing the connection type and the VPI value for each connection.
myshelf.1.4.ASC. a > dspadrxlat
could result in the following response
The second method is to calculate the VPI from the slot number and the VPID value.
VPI = (slot number - 5) * 20 + (VPID - 1) + 16
VPI = (slot number - 5) * 340 + (VPID - 1) + 16
To provision a FRSM channel in a stand-alone application:
1. Enter the cc command to change the active CLI card to the slot number corresponding to the channel to be provisioned. For example,
myshelf.1.3.ASC. a > cc 5
2. Enter the addln command to add a physical line (line number corresponds to the physical line module port number for the channel being provisioned). Then enter the dsplns command to verify the line has been added. For example,
myshelf.1.5.FRSM. a > addln
myself.1.5.FRSM. a > dsplns
3. Enter the addport command to add a Frame Relay port to the enabled line. Then enter the dspports command to verify the port has been added. For example,
myshelf.1.5.FRSM. a > addport
myself.1.5.FRSM. a > dspports
4. Enter the addchan command to add a Frame Relay endpoint. Then enter the dspchans command to verify the channel has been added. For example,
myshelf.1.5.FRSM.a>addchan
myself.1.5.FRSM.a>dspchans
To provision a AUSM channel in a stand-alone application
1. Enter the cc command to change the active CLI card to the slot number corresponding to the channel to be provisioned. For example,
myshelf.1.3.ASC. a > cc 5
2. Enter the addln command to add a physical line (line number corresponds to the physical line module port number for the channel being provisioned). Then enter the dsplns command to verify the line has been added. For example,
myshelf.1.5.AUSM. a > addln (add line parameters)
myself.1.5.AUSM. a > dsplns
3. Enter the addport command to add a ATM port to the enabled line. Then enter the dspports command to verify that the port has been added. For example,
myshelf.1.5.AUSM. a > addport
myself.1.5.AUSM. a > dspports
4. Enter the addchan to add a ATM endpoint. Then enter the dspchans command to verify the channel is added. It is in this command that the VPID is specified. For example,
myshelf.1.5.AUSM.a>addchan
myself.1.5.AUSM.a>dspchans
Posted: Thu Nov 20 21:46:52 PST 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
