|
|
To install the IGX, complete the following tasks:
6. Performing basic node configuration tasks (see the "IGX Configuration Summary" section)
For more information on node configuration, see the Cisco IGX 8400 Series Provisioning Guide .
For more information on switch software commands, see the Cisco WAN Switching Command Reference .
 |
Warning Hazardous network voltages are present in WAN ports regardless of whether power to the router is OFF or ON. To avoid electric shock, use caution when working near WAN ports. When detaching cables, detach the end away from the router first. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this product. |
The locations of the system cards in the IGX node depend on the hardware configuration. Primary and redundant nodal processor modules (NPMs) must reside in front slot 1 and 2. The system clock module (SCM) must reside in back slot 1. Except for these reserved slots, cards can reside in any slot on the appropriate side of the node (but Cisco recommends that the optional alarm relay module (ARM)/alarm relay interface (ARI) card set reside in the slot on the far right).
The SCM card determines whether the IGX node is an IGX 8410 (which has 8 slots), an IGX 8420 (which has 16 slots), or an IGX 8430 (which has 32 slots). Before installing cards in the node or replacing the SCM, verify that the jumpers are set properly. (See Table 3-1.) The two jumpers, W5 and W6, are located near the P2 connector and the strengthening bar on the SCM card. (See Figure 3-1.) Record your setting, so that you don't have to remove the SCM card later to verify the setting.
 |
Caution Incorrect jumper settings can cause the loss of data and services. |
 |
Note Do not connect both W5 and W6 jumpers. The setting is not supported. |
|
Caution Turn off the IGX node before removing or inserting the SCM card. Damage to the node can occur if you insert the SCM card while the node is on. |
Installing an IGX 8420 switch requires the following tools and equipment:
Many card sets support Y-cable redundancy. This feature requires an extra set of cards and a Y-cable. A set of commands exists to specify, delete, and display Y-cable redundancy. For instructions on setting up Y-cable redundancy, refer to the setup section for the specific card set.
|
Note Frame Relay module (FRM) and network trunk module (NTM) front cards exist in one and two-piece versions. The two-piece card uses an ACM1. Refer to the Cisco IGX 8400 Series Provisioning Guide for details. |
A Cisco IGX node can support a configuration of up to 32 trunks.
|
Caution Connector pins must align with receptacles. Before card insertion, make sure that pins are straight and that card connectors and the backplane align. Insert the card gently. It might be necessary to push the edge of the card slightly to one side for alignment. (This might require removing cards.) |
The locations for the NPMs and SCMs in a Cisco IGX:
|
Caution When handling the cards, wear a wrist strap to prevent damage to the cards from electrostatic discharge. The IGX 8410 cabinet has wrist strap attached at both the front and the back. |
Step 2 Using the 5/32-in. Allen wrench, open the Cisco IGX 8400 series switch door.
Step 3 Be sure that you are inserting the module into the correct slot.
Step 4 Grasp the card front panel with one hand and place your other hand under the card to balance the weight of the card as you push it vertically into the slot. See Figure 3-6.
Step 5 Push down on the ejector levers to properly seat the card.
|
Caution Always use the ejector levers when disengaging or seating the modules. Failure to do so can cause erroneous system error messages, and indicate card failure. However, do not use the ejector levers to lift or support the weight of the cards. |
Step 6 Using the number 1 Phillips screwdriver, tighten the panel fasteners at the top and bottom of the card front panel.
The remaining sections of this chapter describe how to set up physical lines, ports, trunks, and signal connections. The Cisco WAN Switching Command Reference and Cisco WAN Switching SuperUser Command Reference provide important details on the commands appearing in this chapter.
The following trunk rates are supported:
The following service module (or circuit line) connections are supported:
The sections that follow contain basic information on how to set up the two types of trunks on the
IGX node. The two trunk types are FastPacket and ATM. The supported line types are OC3/STM1, T3, E3, T1, Y1, and E1. The card sets described in this section are the network trunk module (NTM). The enhanced universal switching module (UXM-E) is a dual-purpose, ATM cell-based card and has its own section that includes information for trunk-mode configuration and port-mode configuration.
To set up a UXM-E attach cables and enter commands at the command-line interface (CLI). For detailed information regarding the UXM-E, refer to the Cisco IGX 8400 Series Provisioning Guide .
You can specify the mode of the UXM-E through Cisco WAN Manager or the switch software CLI. The UXM-E card set goes into the mode determined when you activate the first port. If you activate a logical port to be a trunk by using the uptrk command, for example, the UXM-E goes into trunk mode. If you use the upln command to activate a line as a User-Network Interface (UNI) port to customer premises equipment (CPE) or an Network-to-Network Interface (NNI) to another network, the UXM-E goes into port mode.
For a summary of commands used to bring up an IGX node, refer to the "IGX Configuration Summary" section.
If you are not familiar with precautions for card insertion, see the "Preparing the Cards" section.
To attach the cables to a back card:
Step 2 If the unit has the optional cable manager, you can use it to help route the cables. See Figure 3-7.
Step 3 Connect the cables to the connectors on the back card. See Figure 3-7.
Use the following command sequence for bringing up the trunk. You must bring up the trunk before you add connections.
For more information on switch software commands, see the Cisco WAN Switching Command Reference .
Step 2 Configure the cellbus bandwidth allocation for the card if you do not plan to rely on automatic increases from switch software. Use the superuser command cnfbusbw on the CLI to see and increase the current allocation.
|
Note Cisco recommends that you not allow oversubscription. Refer to the Cisco IGX 8400 Series Provisioning Guide for the description of cellbus bandwidth allocation and the Cisco WAN Switching SuperUser Command Reference for a description of the cnfbusbw command. Any user can view the current cellbus bandwidth allocation by using the dspbusbw command. |
Step 3 Activate the trunk by using the uptrk command. Run this command on the nodes at both ends of the trunk. On the CLI, use the vt command to reach the far-end node to run commands. The only trunk cards you can connect to a UXM-E trunk are another UXM-E trunk card or a BXM in trunk mode. The syntax of the single-port trunk specification is slot.port.
To specify an inverse multiplexing over ATM (IMA) trunk through the CLI, enter the uptrk slot.first_line-last_line command. The line numbers must be contiguous.
Step 4 At each end, configure trunk parameters as required by using the cnftrk command. Each type of trunk comes up with a default configuration, but you can alter the configuration with the cnftrk command. Refer to the description of the cnftrk command in the Cisco WAN Switching Command Reference for the parameters that apply to each interface.
Step 5 Use the addtrk command to add the trunk. Adding the trunk makes it a usable resource, so you can subsequently add connections through Cisco WAN Manager or the CLI using the addcon command. Add the trunk at only one node. If, after you add the trunk, you later determine that changes to the trunk parameters are necessary, you can change certain parameters with the cnftrk command without taking the trunk out of service.
Step 6 Optionally, configure a UXM-E trunk as a clock source by entering the cnfclksrc command.
Step 7 Configure the cellbus bandwidth allocation with the cnfbusbw command if you plan to activate many ports or carry a large number of connections on the UXM-E trunk. Use the dspbusbw or cnfbusbw command to check cellbus usage and changes in bandwidth requirements for the UXM-E. For information on cellbus bandwidth needs, see the Cisco IGX 8400 Series Provisioning Guide .
Step 8 To configure physical and logical trunk statistics, use the cnfphyslnstats and cnftrkstats commands, respectively. See the Cisco IGX 8400 Series Provisioning Guide for UXM-E trunk statistics.
An IMA lets you group physical T1 or E1 lines to form a logical trunk. A logical trunk consisting of more than one T1 or E1 line supports connections with data rates that are much higher than the T1 or E1 rate. System software lets you specify IMA so that one or more physical lines within the logical trunk can serve as backup if a line fails. IMA characteristics are as follows:
To specify the range of ports for an IMA trunk, you can use either Cisco WAN Manager or the command-line interface (CLI). To define an IMA trunk on the CLI, use the uptrk command:
uptrk slot.start_port-end_port
For example, you could enter uptrk 8.1-4. Subsequently, you would refer to this logical trunk by using only the slot number and first port number—8.1 in this example—when you use other commands, such as addtrk, deltrk, cnftrk, and so on. Commands for viewing IMA information also include dspportstats, dspphyslns, dsptrkcnf, dspfdr, dspnode, and dspphyslnstathist.
To add the UXM-E feeder trunk, you can use either Cisco WAN Manager or the CLI. To define an IMA trunk on the CLI:
Step 2 Use the cnftrk command to configure the activated UXM-E feeder trunk:
Step 3 Use the addshelf command to add the feeder trunk to an IGX routing node:
addshelf slot.primary link shelf type
To add links to an IMA group, you can use either Cisco WAN Manager or the CLI. To add a link to an IMA on the CLI:
Step 2 Increase the IMA group members on both trunk and feeder nodes by manually entering the number of group members. Enter:
Step 3 Increase the receive rate using the DS0 calculation on both trunk and feeder nodes.
Step 4 Increase the number of retained links on both trunk and feeder nodes.
To remove links from an IMA group, you can use either Cisco WAN Manager or the CLI. To remove a link from an IMA group on the CLI:
Step 2 Reduce the number of retained links on the IMA feeder node.
Step 3 Reduce the receive rate using the DS0 calculation on the IMA feeder node.
Step 4 Repeat Step 2 and Step 3 on the IMA trunk.
Step 5 Reduce the number of IMA group members on both trunk and feeder nodes by manually entering the number of group members:
This feature allows the extension of the IMA protocol to UXM-E line interfaces, which substantially reduces equipment and interface costs for customers requiring IMA line interfaces and trunks and high bandwidth demand for ATM. It reduces costs by bundling multiple physical T1/E1 lines into a logical line enlarging traffic bandwidth. This makes it unnecessary to upgrade access lines to higher-speed services such as T3/E3.
|
Note Both ends of the UXM-E IMA lines require you to install UXM-E Firmware Model B (Release 9.2 and later releases). If the UXM IMA line is connected to another device, that device must support ATM Forum Compliant IMA Protocol, Version 1.0. To verify the UXM firmware version, use the dspcd command. |
To specify the range of ports for an IMA line, you can use either Cisco WAN Manager or the command-line interface (CLI). To define an IMA line on the CLI, use the upln command:
For example, you could enter upln 8.1-4. Subsequently, you would refer to this physical line by using only the slot number and first group member—8.1 in this example—when you use commands, such as upln, dnln, cnfln, and so on. Following the activation of an IMA line group, the logical port will be created with the primary line port as the port number.
Commands for viewing IMA line information also include dsplncnf, dsplns, dspports, dspport, dspphyslnstathist and dspphyslnstatcnf.
|
Note The UXM-E IMA ports on an IGX, will interoperate with an IMA compliant router or a device that supports the ATM Forum Compliant IMA Protocol, Version 1.0. |
If you are not familiar with card insertion, see the "IGX Configuration Summary" section.
Step 2 If the unit has the optional cable manager, you can use it to help route the cables.
Step 3 Connect the cables to the connectors on the back card.
To activate a port-mode UXM-E:
Step 2 Activate each line by using the upln command. Run this command on the nodes at both ends of the line. Use the vt command to reach the far-end node to run commands. When you activate the first line with the upln command, the UXM-E goes into port mode.
Step 3 At the near-end and far-end nodes, use the cnfln command to configure line parameters as required. Each line comes up with a default configuration, but you can change the configuration with the cnfln command.
Step 4 Optionally, you can specify Y-cable redundancy with the addyred command.
Step 5 Use the upport command at the near-end and far-end nodes to activate (up) the logical port. Use vt to reach the far-end node. Activating the port makes it a usable resource, so you can subsequently add connections through Cisco WAN Manager or the CLI (using the addcon command).
Step 6 Use the cnfport command at the near-end and far-end nodes to configure each logical port. Applicable parameters are the choice of UNI or NNI cell header, an enable for Local Management Interface (LMI) or Interim Local Management Interface (ILMI) protocol or no protocol, and an enable for the %util parameter.
Step 7 If you do not want the defaults for the queue depths and high and low discard eligibility thresholds, use the cnfportq command to configure parameters for the CBR, VBR, and ABR queues.
Step 8 Optionally, you can use the cnfabrparm command to configure additional parameters for ABR traffic. The cnfabrparm command parameters are CI control and egress explicit rate stamping.
Step 9 Optionally, you can configure a UXM-E port as a clock source. Use the cnfclksrc command.
Step 10 Configure the cellbus bandwidth allocation with the cnfbusbw command if you plan to activate a large number of ports on the UXM-E. Use the dspbusbw or cnfbusbw command to check cellbus usage and changes in bandwidth requirements for the UXM-E. For an explanation of cellbus bandwidth allocation, see the Cisco IGX 8400 Series Provisioning Guide .
|
Note Cisco recommends that you not allow oversubscription. Refer to the Cisco IGX 8400 Series Provisioning Guide for the description of cellbus bandwidth allocation and the Cisco WAN Switching SuperUser Command Reference for a description of cnfbusbw. Any user can view the current cellbus bandwidth allocation by using the dspbusbw command. |
Step 11 To check the status of the lines, use the dsplns command.
Step 12 To configure the duration, sample count and size, and peak values for historical port statistics, use the cnfportstats command. Use the dspportstats command to display the summary statistics for cell count, CLP cell count, OAM cell count, RM cell count, OAM cell count, unknown VPI/VCI cell count, and optional LMI/ILMI status. Other applicable commands are dsplnerrs, dspportstatcnf, and dspportstathist.
The T1 trunk connections use the NTM front card and the BC-T1 back card. Japanese Y1 connections use the NTM front card and the BC-Y1 back card. The procedure for making Y1 connections is the same as for T1 connections described below.
Make the T1 connections as follows:
Step 2 Use the cable management feature to help route the cables.
Step 3 Connect the trunks to the connectors on the BC-T1s that are part of NTM/BC-T1 card sets. The T1 lines are attached to DB-15, subminiature, 15-pin connectors on the BC-T1 cards.
The back slot line numbers correspond to the back slot number in which the BC-T1 card resides. Record the back slot number of each line. These numbers are necessary for configuring the system after you complete hardware installation.
|
Note If the number of trunks is odd, connect as many as possible in pairs, and connect the remaining lines in ascending order. |
The E1 trunk connections use the NTM front card and the BC-E1 back card. Subrate E1 connections use the NTM front card and the BC-SR back card. The E1 trunk interface card BC-E1 contains the E1 trunk connector (G.703 Input/Output) that is located at the top of the back card. The BC-E1 faceplate has four 75-ohm BNC connectors.
|
Note The BC-E1 faceplate provides two connector arrangements for attaching E1 lines. Use either the two BNC (RX and TX) connectors or the 15-pin DB connector. |
Make the E1 connections as follows:
|
Note Some versions of the BC-E1 use a metal BNC connector instead of a plastic BNC. For terminating 75- or 120-ohm balanced E1 lines at the metal BNC connectors, remove the BNC mounting nuts. This removes the ground that normally appears on one side of the connector shell. |
Step 2 Use the cable management feature to help route the cables.
Step 3 Connect the cables to connectors on the BC-E1s that are part of an NTM/BC-E1 card sets.
Record the slot numbers of the NTM/BC-E1 card set. You need these numbers when you configure the system.
The universal router module (URM) is a dual-processor card, featuring both a modified Cisco IGX 8400 series UXM-E processor and a modified Cisco 3660 modular-access router processor. Each processor uses a different operating system. See documentation for both Cisco IOS software and switch software while working with the URM.
For more information on the URM, see the Cisco IGX 8400 Series Provisioning Guide.
The following procedure describes the installation of an encryption advanced interface module (AIM) module on the URM front card. This encryption AIM module is required for implementation of a virtual private network (VPN) using the IGX.
 |
TimeSaver To avoid having to redo tasks, install the encryption AIM on the URM front card before installing the URM in the IGX chassis. |
 |
Tip Use the anti-static bag used to ship the URM as a ground cloth to prevent ESD. |
Step 2 With the flat-blade screwdriver, remove the three metal screws nearest the AIM connector while holding down the URM front card.
Step 3 Place the encryption AIM in the plastic stand-off that comes with the encryption AIM.
Step 4 Align the legs on the plastic stand-off with the screw holes on the URM front card and insert the encryption AIM into the AIM connector on the URM front card (see Figure 3-8).
|
Note Be sure to firmly seat the encryption AIM in the connector. Also, make sure that the metal stand-offs align with the screw holes on the URM front card. |
Step 5 Insert the three metal screws into the holes in the encryption AIM. Tighten each screw with the flat-blade screwdriver.
Step 6 Confirm that the encryption AIM is correctly installed, then continue with the "Configuring Internet Encryption" section.
|
Note There are no commands specific to configuring the encryption hardware. Both software-based and hardware-based encryption are configured in the same way. The system automatically detects the presence of an encryption module at bootup and uses it to encrypt data; if no encryption hardware is detected, software is used to encrypt data. |
Whenever you install a new interface, or if you want to change the configuration of an existing interface, you must configure the interface. If you replace a module that was already configured, the router recognizes it and brings up the interface in the existing configuration.
Before you configure an interface, have the following information available:
|
TimeSaver Obtain this information from your system administrator or network plan before you begin router configuration. |
This section describes basic encryption configuration including:
For more information about configuring IPSec, see the "IP Security and Encryption" sections in Cisco IOS software documentation (see the "Cisco IOS Software Documentation" section).
|
Note Depending on your own requirements and the protocols you plan to route, you might also need to enter other configuration commands. |
To configure the Internet Key Exchange Security Protocol, complete this procedure:
To configure IPSec network security, complete this procedure:
For complete information about global configuration commands, and about configuring LAN and WAN interfaces on your router, refer to the Cisco IOS configuration guides and command references.
After configuring the new interface, you can use the following commands to verify that the new interface is operating correctly:
This section contains sample configuration files for two peer routers set up to exchange encrypted data through a secure IPSec tunnel over a channelized T1 interface channel group, serial 1/0:0.
This section describes how to install the voice cards. See the "IGX Configuration Summary" section for a summary of the commands that apply to circuit lines and voice connections. The two voice card sets are the channelized voice module (CVM) and the universal voice module (UVM). These cards can also carry channelized data. The serial data card sets are the high-speed data module (HDM) and the low-speed data module (LDM). This section also describes the considerations for using the Time-Division Multiplexing (TDM) Transport feature on the CVM.
Voice or data connections on a T1 line use the CVM front card and the BC-T1 back card. Japanese J1 connections use the CVM front card and the BC-J1 back card. The procedure for making J1 connections is the same as for T1 connections. Make the T1 connections as follows:
Step 2 Use the cable management feature to help route the cables.
Step 3 Connect the trunks to the connectors on the BC-T1s that mate with the CVM (not NTM). The T1 lines are attached to DB-15, subminiature, 15-pin connectors on the BC-T1 cards.
The back slot line numbers correspond to the back slot number in which the BC-T1 card resides. Record the back slot number of each line. These numbers are necessary for configuring the system after you complete hardware installation.
|
Note If the number of lines is odd, connect as many as possible in pairs, and connect the remaining lines in ascending order. |
Channelized voice or data connections on an E1 line use the CVM front card and the BC-E1 back card. Subrate E1 connections use the CVM front card and the BC-SR back card. The E1 trunk interface card BC-E1 contains the E1 connector (G.703 Input/Output) that resides at the top of the back card. The BC-E1 faceplate has four, 75-ohm BNCs.
|
Note The BC-E1 faceplate provides two connector arrangements for attaching E1 lines. Use either the two BNC (RX and TX) connectors or the 15-pin DB connector. |
Make the E1 connections as follows:
|
Note Some versions of the BC-E1 use a metal BNC connector instead of a plastic BNC. For terminating 75- or 120-ohm balanced E1 lines to the metal BNC connectors on these back cards, remove and discard the BNC mounting nuts. With the mounting nuts removed, the ground that normally appears on one side of the connector shell is also removed. This step is not required for DB-15 connectors or for back cards that use the plastic BNC connectors. |
Step 2 Attach the cabling to connectors on the BC-E1s that mate with the CVM (not an NTM).
Step 3 Use the cable management feature to help route the cables.
The back slot line numbers correspond to the back slot number in which the BC-E1 card resides. Record the back slot number of each line. These number are necessary for configuring the system after installation is complete.
The next section describes a specialized version of data transmission service called TDM Transport. It applies to older WANs not manufactured by Cisco.
This section describes how to plan for use of the Time-Division Multiplexing Transport (TDM Transport) feature. Note that TDM Transport requires Model C firmware on all connected CVMs or CDPs that use this feature. Refer to the Cisco WAN Switching Command Reference for a description of the command parameters in related commands.
Before adding a bundled connection under TDM Transport, consider the following:
Voice or data connections on a T1 line use the UVM front card and the BC-UVI-2T1EC back card. The procedure for connecting the T1 lines is as follows:
Step 2 If the intended compression for voice channels is LDCELP and the number of channels on a T1 line exceeds 16, install cabling for pass-through. Note that the UVM does not pass-through t-type or td-type connections. For the steps that follow, refer to Figure 3-9 for an illustration of the possible UVM cabling arrangements. Note that, in Example B, the number of channels has not exceeded the UVM capacity, so pass-through is unnecessary.
For a description of the pass-through feature, refer to the Cisco IGX 8400 Series Provisioning Guide .
Record the back slot number and port number of each line. These numbers are necessary for configuring the system after you complete hardware installation.
Voice or data connections on an E1 line use the UVM front card and the BC-UVI-2E1EC back card. The procedure for connecting the E1 lines is as follows:
Step 2 If you use the 120-ohm, DB-15 connectors, you must remove the nuts on the BNC connectors for the port, although the BNC has no attached cable.
Step 3 If you use the 75-ohm BNC connectors in a balanced mode, you must remove the nuts from the BNC connector.
Step 4 Install optional Y-cables as needed.
Step 5 If the intended compression for voice channels is LDCELP and the number of channels on a E1 line exceeds 16, install cabling for pass-through. For the steps that follow, refer to Figure 3-10 for an illustration of the possible UVM cabling arrangements. Note that, in Example B, the number of channels has not exceeded the UVM capacity, so pass-through is unnecessary.
For a description of the pass-through feature, refer to the Cisco IGX 8400 Series Provisioning Guide .
The back slot line numbers correspond to the slot number in which the BC-UVI-2E1EC card resides. Record the back slot number and port number of each line. These numbers are necessary for configuring the system after you complete hardware installation.
Voice or data connections on a J1 line use the UVM front card and the BC-UVI-2J1EC back card. The procedure for connecting the J1 lines is as follows:
Step 2 Attach each cable according to the cabling requirement (pass-through, external, and so on).
If the intended compression for voice channels is LDCELP and the number of channels on a J1 line exceeds 16, install cabling for pass-through. For the steps that follow, refer to Figure 3-11 for an illustration of the possible UVM cabling arrangements. Note that, in Example B, the number of channels has not exceeded the UVM capacity, so pass-through is unnecessary.
For a description of the pass-through feature, refer to the Cisco IGX 8400 Series Provisioning Guide .
The back slot line numbers correspond to the slot number in which the BC-UVI-2J1EC card resides. Record the back slot number and port number of each line. These numbers are necessary for configuring the system after you complete hardware installation.
The low-speed data module (LDM) and high-speed data module (HDM) card sets provide serial data service. Each of these front cards uses a variety of back cards.
The LDM front card uses the 4- or 8-port version of the low-speed data interface (LDI) back card for EIA/TIA-232C/D (V.24) connections. The connection ports are labeled Port 1 through Port 4 or Port 1 through Port 8. See Figure 3-12 for illustrations of these back cards. For instructions on configuring a port on the LDI back card for data terminal equipment (DTE) or data circuit-terminating equipment (DCE) mode, refer to the "Configuring the Mode of an LDI Port" section.
The HDM front card works with four types of serial data interface (SDI) back cards. Available SDIs are V.35, EIA/TIA-449/422, EIA/TIA-232D, and EIA/TIA-232C (V.24). (X.21 uses EIA/TIA-449 plus an adapter cable.) Each type of SDI has four connection ports, which are labeled Port 1 through Port 4. A sample SDI card appears in Figure 3-12 .
When you connect an HDM or LDM port, use the shortest reasonable cable length for each port.
Small jumper boards on the back card determine whether the mode of the port is DTE or DCE. The factory-set modes of the SDI ports alternate DCE with DTE. The steps that follow describe how to change the mode of the port. For the two modes, the rows on the back card jumper connector that are occupied by the jumper card are:
|
Note A jumper board ships with an impedance of either 100 ohms or 200 ohms. For higher port speeds, the impedance is important if you have specified Y-cable redundancy. With Y-cable redundancy on a higher-speed connection, use the 200-ohm jumper board. With no Y-cable redundancy or when the port speed is relatively low, the 100-ohm jumper board is adequate. |
To change the mode on a port to DTE, position the jumper board for that port as follows:
|
Caution To prevent damage to the SDI cards, wear a wrist strap and clip the strap to the enclosure. |
Step 2 Move the jumper board one row of pins away from the SDI faceplate. (See Figure 3-13 .) For DTE mode, the jumper board should occupy rows 2, 3, 5, and 6.
If a port is in DTE mode and needs to be changed to DCE, plug the jumper board into the connector receptacle pin rows closest to the SDI faceplate. (See Figure 3-13 .) These rows are 1, 2, 4, and 5.
Optional redundancy for HDM and LDM cards can be provided with a second front and back card set and a Y-cable connection on each port to the customer data equipment.
|
Note A jumper board ships with an impedance of either 100 ohms or 200 ohms. For higher port speeds, the impedance is important if you have specified Y-cable redundancy. With Y-cable redundancy on a higher-speed connection, use the 200-ohm jumper board. With no Y-cable redundancy or when the port speed is relatively low, the 100-ohm jumper board is adequate. |
Each port on an LDI card uses an adapter cable. For a list of LDI adapter cables, refer to the "Data Cabling" section. Each cable does the following:
Figure 3-14 shows an example in which the adapter cable makes the port a DCE port. Circuits on the card test certain pins on the cable then configure the port as DTE or DCE.
This section outlines how to establish Frame Relay service by setting up a universal frame module (UFM) or a Frame Relay module (FRM). The information includes details for T1, E1, HSSI, V.35, and X.25 interfaces. Detailed descriptions of the Frame Relay commands appear in the Cisco WAN Switching Command Reference. Specific cabling requirements for the UFI back cards on the UFM-U appear in the UFM-U description in the Cisco IGX 8400 Series Provisioning Guide.
For any Frame Relay card set that has a maximum frame length of 4510 bytes, the type of signaling protocol you can (optionally) specify with the cnffrport command results in a limit on the number of connections per physical or logical port. The maximum number of connections per port for each protocol is:
Neither the addcon nor the cnffrport command prevents you from adding more than the maximum number of connections on a port. (You might, for example, use the cnffrport command to specify an LMI when too many connections for that particular LMI already exist.) If the number of connections is exceeded for a particular LMI, the LMI does not work on the port, the full status messages that result are discarded, and LMI timeouts occur on the port. A port failure results and subsequently leads to a-bit failures in other segments of the connection path.
Channelized and unchannelized versions of the UFM card sets exist. The channelized front cards, UFM-4C and UFM-8C, operate with T1 and E1 interfaces, and the unchannelized front card, UFM-U, operates with V.35, X.21, and HSSI interfaces.
The back cards have the following terminations:
If the installation includes Y-cable redundancy, first read the "Y-Cable Redundancy on the UFMs" section.
Redundancy for a Frame Relay port is possible with a second card set and the appropriate Y-cable. The card redundancy kit for UFM contains a second UFM/UFI card set and Y-cables to interconnect the ports on the two back cards. The "Setting Up Frame Relay Ports and Connections (UFM)" section includes the step for configuring Y-cable redundancy.
Refer to the cabling description in the UFM-U section of the Cisco IGX 8400 Series Provisioning Guide for descriptions and part numbers of all cables for unchannelized UFMs.
Figure 3-15 shows the Y-cable arrangement for standard cables that support one or two ports. The diagram for single-port cables applies to all back cards. The dual-port cables connect to only a V.35 or X.21 UFI. The Y-cable connects to the back card, and the standard cable runs between the access device or CPE and the base of the Y.
Y-cable redundancy is not allowed between different line types, such as a UFI-8T1-DB-15 and a UFI-8E1-DB-15. The dspyred command display shows any conflict in reverse video. (See the descriptions of the upln (or upcln) and upfrport commands in the Cisco WAN Switching Command Reference.)
The commands that relate to Y-cable redundancy are addyred, delyred, dspyred, and ptyred. After you have installed the cards in adjacent slots and connected the cables, use the addyred command to direct the node to recognize the card redundancy. See the Cisco WAN Switching Command Reference for descriptions of the commands.
For important details on standard cables and Y-cables for the UFI back cards, refer to the cabling description in the UFM-U section of the Cisco IGX 8400 Series Provisioning Guide .
Take the following steps after you have inserted the cards according to the information on installing cards in the "Preparing the Cards" section. Connect the cables as follows:
Step 2 Bring each cable through the opening at the top or bottom of the cabinet (if applicable) and along the back of the unit. If necessary, use the cable manager to help route the cables.
Step 3 Add optional Y-cables as necessary.
Step 4 Secure the cables to the connectors on the back cards that mate with the correct front card. If the front card is a UFM-4C, use only the first four lines. If you install Y-cable redundancy on a UFI-4HSSI card, only Port 1 is configurable for redundancy.
Step 5 Record the slot number of each line for configuration purposes after you install the hardware.
This section outlines the steps for setting up and deleting Frame Relay ports, adding connections, and bundling connections. If a port has multiple permanent virtual circuits (PVCs), you can optionally bundle the connections. Bundling facilitates network meshing. You can specify connection bundling during parameter specification in the add connection (addcon) command: if you press Return without specifying a data-link connection identifier (DLCI) during port specification, the system prompts for bundling information. See the "Frame Relay Connections" chapter in the Cisco WAN Switching Command Reference for details.
Use either a Cisco WAN Manager workstation or an IGX control terminal to do the following tasks. For detailed command descriptions, see the Cisco WAN Switching Command Reference.
Step 2 If the card is a UFM-C, activate each line with the up line (upln) command. The range of lines for a UFM-4C is 1 to 4. The range of lines for a UFM-8C is 1 to 8.
A UFM-U does not require activation with the upln command.
Step 3 If the card is a UFM-C, assign logical Frame Relay ports to individual physical lines by using the addfrport command. A UFM-U does not require the addfrport command. Optionally, use the configure line command (cnfln) command for a UFM-C either before or after the addfrport command. Note that if you use the cnfln command to assign a DS0 to carry signaling, you cannot subsequently assign that DS0 for user-data with the addfrport command.
Step 4 If the card is a UFM-U, use the cnfmode command to configure the mode of the card if you do not use the default of mode 1. You must understand the ramifications of this step before you use cnfmode. If you do not understand the modes of the UFM-U, refer to the UFM-U description in the Cisco IGX 8400 Series Provisioning Guide.
Step 5 For optional Y-cable redundancy, configure the two cards by using the addyred command. For Y-cable redundancy on a HSSI card, you must use port 1 of the cards for the primary and redundant ports. For important information about Y-cable redundancy on a UFM-U, see the description in the UFM-U portion of the Cisco IGX 8400 Series Provisioning Guide .
Step 6 Activate the ports using the upfrport command.
Step 7 Configure the port for DCE or DTE mode, speed, clocking, LMI type, and so on, by using the cnffrport command. Alternatively, you can keep the default parameters. If you plan to bundle connections, use the cnffrport command to set the Port ID to the DLCI planned for the near-end connections before you add the bundled connections. The PortID is optional for nonbundled connections. Note that the cnfport command functions the same for Frame Relay as the cnffrport command.
Step 8 Add connections by using the addcon command. Adding connections requires the slot number, logical port number, and DLCI for each end of the connection. Frame Relay is a purchased option. If you attempt to add connections but the system display states that Frame Relay is not available, see the "Obtaining Technical Assistance" section.
If you do not know the Frame Relay class intended for entry with the addcon command, determine which Frame Relay class number to use. Use the dspfrcls command to see the parameters that each class specifies. To modify parameters in a class, use the cnffrcls command.
Step 9 Optionally—for an individual connection—you can configure bandwidth parameters or enable ForeSight (if purchased) by using the cnffrcon command.
Optionally, you can set the channel priority by using the cnfchpri command. Normally, the system-default priority is adequate.
To specify logical ports on a T1 or E1 interface, use the addfrport command. The addfrport command assigns a logical port number to a physical line and a range of 1 or more DS0s or time slots. Use the logical port number to activate a port (using the upfrport command), add connections (using the addcon command), or display statistics (using the dspportstats command). For example, after you add logical port 14.60 2.1-24 with the addfrport command, you activate (up) this logical port by entering the upfrport 14.60 command. The maximum number of logical port numbers on a UFM-C is 250. Use the dspfrport command to display logical ports.
Delete a logical port by executing the delfrport command. Executing the delfrport command dissolves any groups of DS0s or time slots and unassigns all DS0s or time slots on the logical port.
|
Note Before you delete a Frame Relay port, you must delete any connections on the port using the delcon command. |
After deleting a logical port with the delfrport command, you can deactivate the physical port with the dnport command.
Four types of interfaces are available for the FRM. The back cards have the following terminations:
Cabling requirements for the Frame Relay interfaces are in the "FRI V.35 Port Pin Assignments" section.
Take the following steps after you have inserted the cards according to the general information on installing cards in the "Preparing the Cards" section. To connect a cable:
Step 2 If needed, use the cable manager to help route the cables.
Step 3 Secure the cables to the connectors on the cards that mate with the correct front card.
Step 4 Record the slot number of each line. These numbers are necessary for configuring the system.
The position of a small jumper board at each port determines whether it is a DCE or a DTE.
|
Caution To prevent damage to the FRI cards, ground yourself before handling IGX cards by clipping a grounding strap to your wrist, and clipping the wrist strap lead to the enclosure. |
A small jumper card near each connector on the back card selects the port's mode. The factory-set modes alternate between DCE and DTE. The steps that follow describe how to change the mode of a port. The relation between back card row numbers and the port mode is as follows:
|
Note Jumper cards for selecting the mode of a V.35 or X.21 interface have an impedance of either 100 ohms or 200 ohms. At higher speeds on ports with Y-cable redundancy, the impedance is important. With Y-cable redundancy on a higher-speed connection, use the 200-ohm jumper card. Without Y-cable redundancy or when the port speed is low, the 100-ohm jumper card is adequate. |
|
Note Carefully choose the mode for each port. If you change a port mode after other ports on the card are carrying traffic, it disrupts service on the other ports. |
To change the mode of an interface, reposition the jumper board for the port as follows:
Step 2 To change to DTE, move the jumper board one row of pins away from the FRI faceplate. (See Figure 3-16.) For DTE mode, the jumper board should occupy rows 2, 3, 5, and 6.
To change to DCE, plug the jumper board into the connector receptacle pin rows closest to the FRI faceplate. (See Figure 3-16.) The rows for DCE mode are 1, 2, 4, and 5.
Step 3 Insert the FRI card and gently slide it in all the way to the rear of the slot.
Step 4 Insert and tighten the mounting screws.
Optional redundancy on a Frame Relay port is possible with a second FRM/FRI card set and a Y-cable connection on each applicable port. The "Setting Up Frame Relay on an FRM" section includes the step for configuring Y-cable redundancy. The card redundancy kit contains a second FRM/FRI card set, Y-cables to interconnect the ports on the two back card, and four 200-ohm DCE or DTE jumper cards if the back cards are either FRI-V.35s or FRI-X.21s. (The DCE or DTE port applies to only V.35 or X.21 interfaces.) Make sure that the firmware revision of the FRM in the kit matches the firmware in the installed FRM. Model D firmware supports V.35 and X.21 interfaces. Model E firmware supports T1 and E1 interfaces.
When you install a redundant card set with either a V.35 or X.21 interface, you must change the daughter cards on the existing FRI that specify DCE or DTE mode at each port. Install the higher impedance (200 ohms) version cards that are in the Y-cable kit.
Y-cable redundancy is not allowed between inconsistent back card types, such as an FRI T1 and an FRI V.35. The dspyred command display shows any conflict in reverse video. (Refer also to the descriptions of the upcln and upfrport commands in the Cisco WAN Switching Command Reference.)
After the hardware is installed, use the addyred command to reconfigure the node to recognize the card redundancy. Refer to the Cisco WAN Switching Command Reference for more information on the commands addyred, delyred, dspyred, and ptyred.
This section outlines the steps for setting up and deleting Frame Relay ports, adding and configuring connections, and bundling connections. As the steps show, some commands apply to channelized connections (T1, E1, or J1) but not to unchannelized connections (V.35 or X.21). Use either the IGX control terminal or a Cisco WAN Manager workstation to run the commands. For parameters and other details on the commands, refer to the Cisco WAN Switching Command Reference.
If a port has multiple PVCs, you can optionally bundle the connections. Bundling facilitates network meshing. You can specify connection bundling during parameter specification in the add connection (addcon) command: if you press Return without specifying a DLCI during port specification, the system prompts for bundling information.
Step 2 Use the dspcds command to verify that all nodes have the correct FRI back card and FRM front card. (Use the vt command to gain access to other nodes.) The dspcds output shows the slot number of each card and any mismatch between firmware on the front card and firmware on the back card. Note the slot number of each FRM or UFM for subsequent commands.
Step 3 For V.35 and X.21 interfaces, check the mode (DCE or DTE) of each relevant port by using the dspfrport command. (For T1 and E1 lines, the mode is not applicable.) On an FRI-X.25 or FRI-V.35 back card, a jumper board near each connector determines the mode of the port. See the "Port Mode Selection for V.35 and X.21" section.
|
Note Jumper cards for selecting the mode of a V.35 or X.21 interface have an impedance of either 100 ohms or 200 ohms. At higher speeds on ports with Y-cable redundancy, the impedance is important. With Y-cable redundancy on a higher-speed connection, use the 200-ohm jumper card. Without Y-cable redundancy or when the port speed is low, the 100-ohm jumper card is adequate. |
Step 4 For optional Y-cable redundancy, configure the two slots for redundancy by using the addyred command.
For V.35 and X.21 interfaces, skip the next three steps.
Step 5 For T1, E1, and J1 interfaces, bring up the line using the upln command.
Step 6 For T1, E1, and J1 interfaces, configure the line using the cnfln command.
Step 7 For T1, E1, and J1 interfaces, add the logical Frame Relay port using the addport command.
Step 8 For all interface types, activate the port using the upport command.
Step 9 Configure the port for speed, clocking, LMI type, and so on, by using the cnffrport command. Alternatively, you can keep the default parameters.
If you intend to bundle connections, use the cnffrport command to set the Port ID to the DLCI planned at the near-end connections. Setting the PortID is optional for nonbundled connections.
Step 10 Determine which Frame Relay class number to use when you add connections to a port. To see the parameters that a class specifies, use the dspfrcls command. To modify parameters in a class, use the cnffrcls command.
Step 11 Add connections to the port by using the addcon command. Enter the slot number and specify a DLCI for each end of the connection.
Step 12 For an individual connection, you can configure bandwidth parameters or enable ForeSight (if purchased) by using the cnffrcon command.
Step 13 Optionally, you can set the channel priority by using the configure channel priority cnfchpri command. Normally, the system-default priority is adequate.
To specify logical ports on a T1 or E1 interface, use the addfrport command. The addfrport command assigns a logical port number to a group of one or more DS0s or time slots. The slot number and the lowest number in the user-specified DS0 or time slot group form the logical port number. Use the logical port number to activate a port (using the upfrport command), add connections (using the addcon command), or display statistics (using the dspportstats command). For example, after you add logical port 14.1-6 (6 DS0s or time slots) with the addfrport command, you activate (or up) this logical port by entering upfrport 14.1. Use the dspfrport command to display logical ports.
Running the delfrport command dissolves any groups of DS0s or time slots and unassigns all DS0s and time slots on the logical port. To delete a logical port:
Step 2 Delete the logical port with the delfrport command.
Step 3 Deactivate the logical port with the dnfrport command.
Step 4 Deactivate the physical line with the dnln command.
To install an alarm relay module (ARM) card set:
Step 2 Install the ARM in the front slot and use the card extractors to help secure card.
Step 3 Install the ARI in the corresponding back slot. Use the extractor handles to help secure the card, then tighten the captive screws by hand.
Step 4 Note that the FAIL LED on the ARM is not on. The ACTIVE LED also is not on.
Step 5 Attach a 22- or 24-gauge cable with the appropriate number of pairs to a male DB-37 connector at one end. Typically, a 12-pair cable is adequate. Connect this cable to the DB-37 connector on the ARI and tighten the captive screws.
See the "Initial Startup of the IGX" section when the system is ready for power.
The steps that follow show how to set up an ARM card set after the physical installation is complete. This is done from the IGX control terminal or the Cisco WAN Manager workstation. For details on each command used, refer to the Cisco WAN Switching Command Reference.
Step 2 From a control terminal or a Cisco WAN Manager NMS workstation, log in to the node and enter the addalmslot command followed by the slot number where the ARM is located. This activates the alarm reporting from the card.
Step 3 Observe that the ACTIVE LED on the ARM card is on.
Step 4 Testing the operation of the alarm outputs requires you to create an alarm and note the resulting alarm output. This test is easy on a node that is not connected to the network but is difficult on a node in a fully operational network. The best time to create a major alarm in an operational network is during a low traffic period. If you create an alarm, go to Step 5. Otherwise, end the procedure here.
Step 5 Create an alarm by disconnecting a trunk cable from the connector on a back card.
Step 6 Observe that a MAJOR LED comes on on the front of the ARM.
Step 7 Using a voltage/ohm meter (VOM), make sure continuity exists between pins 16 and 17 and between pins 35 and 36 at the DB-37 connector on the ARI card.
Step 8 Reconnect the cable that was disconnected in Step 5.
Step 9 With the VOM, check that the reading between pins 16 and 17 and pins 35 and 36 are open and the MAJOR LED is not on.
Alarm output connections are made at the DB37 connector on the ARI card. The connector pin assignments with the alarm signal names are listed in Table 3-2. (See the "External Alarm Cabling" section.)
Table 3-3 shows the unassigned connector pins.
The DB-15 connector labeled Ext Clocks on the faceplate of the SCM connects two external sources for a high-stability clock (primary and redundant). One of the trunk or circuit line inputs can also serve as a source of timing for the node. If you do not select a clock source, the node uses the internal IGX clock as the clock source.
Two separate clock inputs exist, and can be used simultaneously on the IGX. They are labelled External-1 and External-2. Both clock inputs require an EIA/TIA 422 balanced square wave signal at either 1.544 or 2.048 MB per second.
|
Note Standard DS1 or E1 BITS clock sources using AMI bipolar pulse stream signals are not compatible with IGX external clock inputs. |
For a list of connector pin assignments, see the "External Clock Input Cabling" section.
A network must have at least one control terminal (or a Cisco WAN Manager workstation if you want to collect statistics) attached, along with a network printer for printing out the status of the system. The SCM has three ports for attaching peripherals to an IGX node. These ports are Control Terminal, LAN AUI, and AUX port.
For the Cisco TAC to perform remote troubleshooting, a modem must connect to the network. This is a requirement for all Cisco service plans. The following sections provide procedures for attaching peripherals to the IGX node. Be sure to read the manufacturers' literature to ensure that the equipment is ready before attempting to connect it to the IGX node.
To use network management, at least one node in a Cisco WAN switching network running
Release 7.2 or higher software must have a Cisco WAN Manager workstation connected. The workstation connects to the AUI Ethernet LAN port on the SCM.
The Cisco WAN Manager workstation can be used to configure and maintain all nodes in a network. For instructions on using the Cisco WAN Manager workstation, see the Cisco StrataView Plus Operations Guide.
If only a single NMS station is connected and the network is relatively small, you can use a serial EIA/TIA232 port—the Control Terminal port.
The "Network Management Terminal" section lists the control terminals supported by the IGX 8410 node and the configuration settings. "General IGX 8410 Switch Specifications," has the pin assign-ments for the IGX 8410 control terminal port.
Attach the control terminal to the SCM. (See Figure 3-17.)
Step 2 Locate the control terminal connector on the SCM and attach the control terminal EIA/TIA-232/V.24 cable to it.
Step 3 Tighten the EIA/TIA-232 connector screws to firmly attach the cable to the Control Terminal connector.
Step 4 Plug the control terminal power cord into the appropriate wall receptacle.
Step 5 Set the port function for VT100 (#5) using the cnftermfunc command.
Step 6 Make sure that the Auxiliary port and the terminal are set to the same baud rate and check the other communication parameters using the cnfterm command.
|
Note When you power up a node, it enters boot mode. Its control terminal communicates at a default rate of 9600 bps. If the rate for the node's control port previously was 19,200 bps, the first messages appears garbled because the control port (in boot mode) is temporarily running at 9,600 bps. When the transition to online occurs, the speeds match, so the display becomes readable. |
If the network is large or extensive network statistics are needed, an Ethernet port (LAN port) should be used. Larger networks produce a greater flow of statistics data between the node and the Cisco WAN Manager workstation, so a higher-speed Ethernet port is suitable. Figure 3-18 illustrates this connection. Accessing a node over an Internet connection requires the operator to use the cnflan command to enter the IP address, IP subnet mask, Transmission Control Protocol (TCP) service port, and gateway IP address.
|
Note Configure the LAN parameters before connecting the node to a LAN. |
|
Note Refer to the Cisco WAN Switching Command Reference for additional information. |
Step 2 Normally, the system administrator updates the network information server (NIS) database, as applicable (if a NIS is used), and adds the IP addresses for the workstation and node to the NIS database.
|
Note If an NIS is in use (in a corporate network, for example), consult with the system administrator. |
Step 3 Configure the LAN port on the IGX node using a dumb terminal or an EIA/TIA-232 connection via the workstation (using the vt command, as applicable) to enter the appropriate cnflan parameters.
The cnflan command configures the node's communication parameters so that the node can communicate with a Cisco WAN Manager terminal over an Ethernet LAN using the TCP/IP protocol. The parameters contain address information about the Ethernet TCP/IP network that is used to connect the Cisco WAN Manager workstation to an IGX node. The values used must conform to those of the network and should be supplied by the Ethernet network administrator.
The cnflan command has the following parameters:
A cnflan command screen looks like this:
The active IP address for the workstation has been entered as the IP address selected previously for the node, 192.187.207.21. The IP Subnet mask is entered as 255.255.255.0 for a Class C LAN network. The TCP service port is entered as 5120. Because the workstation and node are on different networks in this example, a gateway address of 192.187.207.1 has been entered. If the workstation and node are both on the same network, no gateway address is needed. The "Maximum LAN Transmit Unit" and "Ethernet Address" parameters are not configurable by the cnflan command. The Ethernet Address is a hardware address (burned into the NPM card) that is unique to each NPM card.
Step 4 Connect the Cisco WAN Manager workstation and the IGX node to a LAN network. Examples are shown in Figure 3-19 and Figure 3-20. The LAN port on the IGX node provides a DB-15 connector that can be connected to a Y-cable, which in turn is connected to an AUI, as shown in Figure 3-20.
Step 5 To make sure that a LAN connection on the IGX LAN port is good, use a sample host name of "sanfran" entered in the config.sv file, and enter the following at the Cisco WAN Manager workstation:
After the workstation and IGX node interface have been set up, Cisco WAN Manager can be started. After Cisco WAN Manager has started and the communication sockets are active, the dsplan command screen looks like this:
|
Note "Sockets" is the BSD UNIX name for connections between processes and typically applies to network communication. |
Step 6 Switch on the control terminal (or Cisco WAN Manager workstation). Adjust the terminal's configuration, if necessary, to match the default settings of the control terminal port in the IGX node. See Cisco WAN Manager Operations for settings and operating instructions for the workstations.
When a network management station has more than one serial port, ports can connect to different networks. When the number of workstation serial ports is less than the number of networks to be managed, a terminal server is necessary to obtain a communications link to the separate networks. This subject is covered in the Cisco WAN Manager Installation publication.
At least one node in the network should have a printer connected. The printer connects to the AUX port on the SCM.
The printer is used to print information about network operation. It can be configured to print maintenance information on a regular basis, and it can print specific diagnostic information when necessary. Instructions on using the printer for this purpose are in the Cisco WAN Switching Command Reference.
Attach the printer to the IGX node as follows:
Step 2 At the back of the cabinet, run the printer EIA/TIA-232/V.24 cable through the opening at the bottom and up to the SCM card in back slot 1.
Step 3 Locate the AUX port connector on the SCM and attach the printer EIA/TIA-232/V.24 cable to it. See Figure 3-21 .
Step 4 Tighten the EIA/TIA-232/V.24 connector screws to firmly attach the cable connector to the AUX port connector.
Step 5 Plug the printer power cord into the appropriate wall receptacle.
Two modems can be connected to the IGX node to provide access for remote troubleshooting and for remote alarm logging. (See Figure 3-22.) Each connection between the SCM and a modem requires a special cable and setup procedure.
The modem that provides access for remote troubleshooting from the Cisco TAC office (TAC-to-IGX modem) connects to the Control Terminal port on the SCM. Typically, the modem connects to the telephone wall jack with a direct-dial line. For information on contacting TAC, see the "Obtaining Technical Assistance" section.
The modem that is used to provide remote alarm logging (IGX-to-TAC modem) is connected to the AUX port on the SCM. This modem connects to a wall jack using a standard telephone line.
The power supply monitor (PSM) is a connector with outputs that signal an AC power supply alarm. Cisco provides no equipment that connects to the PSM connector, so user-supplied equipment is necessary. Refer to the Cisco IGX 8400 Series Provisioning Guide for a description of the PSM outputs.
The Power Supply Monitor (PSM) is an RJ-45 connector with the following pinout:
Each AC power supply provides an open collector output that goes low if an AC power failure occurs. The inactive state of the status signals is high on the SCM. The signals go into an ALS244 driver, the outputs of which are connected directly to the RJ-45 connector as well as circuitry that communicates the status to the control card. To use the PSM connector, you need a device that responds with a fail condition when a "0" TTL logic level is present on pin 2 or pin 3.
This section describes checkout procedures to follow after the hardware is in place and ready to receive power. The "IGX Configuration Summary" section summarizes the steps and lists the commands for bringing up the system.
Before using the IGX node, be sure that the following procedures are complete:
Step 2 Check the record for the correct switch status for switch W6 on the SCM. See the recommendation in the "Preparing the Cards" section. If the switch position was not previously verified, check it now. W6 sits above component U7P on the SCM. To indicate to the controller card that the system is an IGX 8430 node, remove the jumper. To indicate that the system is an IGX 8420 node, leave the jumper on the card. For an IGX 8410, Cisco personnel set the switch positions to indicate the node type.
Step 3 The full complement of cards for the node are mounted in the correct slots, correctly seated, and secured with screws.
Step 4 The T1 cables are attached to the correct BC-T1, BC-UVI-2T1EC, or UFI-8T1 card.
Step 5 The E1 cables are attached to the correct BC-E1, BC-UVI-2E1EC, or UFI-8E1 card.
Step 6 The Fractional E1 or T1 connections are attached to the BC-E1 or BC-T1 card connector if the IGX node is providing Fractional E1 or T1 service.
Step 7 The Subrate connections connect to the BC-SR card if the IGX node is providing Subrate E1 or T1 service.
Step 8 E3 cables connect to the correct BC-UAI-1E3 card.
Step 9 T3 cables connect to the correct BC-UAI-1T3 card.
Step 10 The data connections are attached to the appropriate SDI/LDI cards.
Step 11 A control terminal connects to the Control Terminal port on the SCM in back slot 1, or a Cisco WAN Manager workstation connects to the AUI port, and the power cord is plugged into the appropriate AC receptacle.
|
Caution If the FAN 2 connector on the PE-BC is unused, be sure not to plug the control terminal cable into FAN2. |
Step 12 If specified, a printer connects to the AUX port on the SCM in back slot 1, and the power cord is plugged into the appropriate AC receptacle.
Step 13 If specified, one or more modems connect to the Control Terminal port or AUX port, as applicable, on the SCM in back slot 1, and any modem power cords plug into the appropriate AC receptacle.
Step 14 At the back of the unit, turn the circuit breakers to the ON position. In a system using a DC source, attach the cable guard (AC should already have the cable guard in place). After initial power up, DC systems can be switched off and on either at the PEM or at the building site's resident circuit breaker. Use the building's DC circuit breaker only if all cables are clearly marked, if the building's dedicated circuit breaker has an actual switch and not just a fuse, and if controlling power at the building's circuit breaker actually provides an advantage over removing the cable guard.
Step 15 Observe that, after you turn on the IGX node, the cards run diagnostic self-test:
Step 16 If an alarm exists for a T1 or an E1 line that is physically connected to the IGX node, try reconnecting the line to make sure that there is a good physical connection. If the alarm condition continues, a valid T1 or E1 problem might exist.
The IGX software contains a group of diagnostic tests that run on the system's hardware at powerup. The startup diagnostic either passes or fails the NPMs. The test result is displayed on the control terminal screen as pass or fail. The pass screen looks like this:
The fail screen looks like this:
If an NPM fails the power-up diagnostic, the boot process does not finish. If this failure occurs:
Step 2 Install the NPM in the same slot again.
Step 3 Wait for the power-up diagnostic to run.
Step 4 If the NPM fails the power-up diagnostics again, replace it with a known-good NPM. For card replacement procedures, refer to "Troubleshooting the IGX.".
IGX software includes internal diagnostic routines that periodically test a card's performance. The diagnostics automatically run in background and do not disrupt normal traffic. If a failure occurs during the test, the red FAIL LED comes on. You can also view status on a terminal with the dspcd command.
The report of a card failure remains until cleared. On the CLI, clear a card failure by using the resetcd command. Two types of resets exist. The reset-failure clears the event log of failures detected by the test. It does not disrupt operation. A reset-hardware resets the card's firmware: it reboots the firmware (momentarily disabling the card) and, if a redundant card exists, switches over to the standby card.
Check the status lights on the system unit cards. Table 3-4 shows the lights for normal status where n+1 redun-dancy exists for NTM and CVM cards.
Table 3-4 System Unit Card Status Lights
| Card | Active Status | Standby Status1 | Alarms |
|---|---|---|---|
| 1Standby status is indicated by no lights on. |
The means for verifying the correct power supply voltages are the DC Okay and AC Okay LEDs on each power supply. If either of these LEDs is off, a problem exists in relation to that supply. Power supplies are not field-adjustable. If a power supply voltage is out of tolerance, replace the supply with one known to be within tolerance.
|
Note In an IGX node, no test points are available in either the AC power supplies or any circuit board for checking voltages. |
This section outlines the steps and names the commands for configuring a network. This section is not an exhaustive presentation. For detailed descriptions of the commands, refer to Cisco WAN Switching Command Reference or Cisco WAN Switching SuperUser Command Reference.
You can configure the IGX node through commands you enter at the control terminal or, if you have access, at a Cisco WAN Manager network management system (NMS). Note that certain features are paid options, which TAC personnel must enable before you add the corresponding connections. Examples of paid options are Frame Relay and ABR with ForeSight.
For IGX configuration, the control terminal has system access either through a local control port (over an EIA/TIA-232 or Ethernet TCP/IP link) or from a control terminal screen on a Cisco WAN Manager NMS. Remote control terminal access is possible using a virtual terminal (vt) command if the node has been configured with a name (using the cnfname command) and at least one trunk has been established to the network.
The basic tasks to configure an IGX node are as follows:
Two approaches are available for establishing a Frame Relay-to-ATM interworking connection in a tiered network. The simplest approach is to use the Connection Manager in Cisco WAN Manager. When you specify a connection to a Frame Relay service module (FRSM) on a Cisco MGX 8220 edge concentrator, Cisco WAN Manager directs the node to establish the correct end-to-end connection type. This connection type is either atfr (ATM-to-Frame Relay interworking) or atfst (ATM-to-Frame Relay interworking with ForeSight). The other approach is to use the command line interface on the IGX node or other routing node to run addcon and related commands (such as cnfcon) to establish the connection between routing nodes. A network interworking connection requires that you specify each individual segment of the connection. (Establishing the connection between the FRSM on the Cisco MGX 8220 and the BPX node requires you to run the addchan command on the Cisco MGX 8220.)
An interface shelf is a nonrouting, concentrator shelf that communicates ATM cells to and from a BPX or IGX routing hub in a tiered network. (An interface shelf is also known as a feeder shelf.) An interface shelf is an IGX node configured to be an interface shelf. The MGX 8220 edge concentrator is also an interface shelf. IGX/AF is the designation of an IGX interface shelf.
For an IGX node to serve as an interface shelf, personnel in the TAC must first configure the node for that purpose because tiered network capability is a purchased option.
You can add an interface shelf from Cisco WAN Manager or the command line interface (CLI). The steps for adding a new interface shelf to a network are:
Step 2 Configure the trunk for STI cell headers and BPX Addressing Mode (BAM).
Step 3 Add the IGX/AF to the hub (after the TAC has enabled this feature) by using the addshelf command. You add the shelf from the routing hub.
Figure 3-23 illustrates the sequence of using the addshelf command either locally or remotely to add one or more interface shelves. To delete an interface shelf, use the delshelf command after you delete connections and the active interfaces. To view status of an interface shelf, run the dspnode command at the routing hub. (The dspnw command shows an alarm on a node but does not specify an interface shelf.)
Adding a connection in a tiered network requires that you add local segments and a network segment. The following steps illustrate the setup for each segment for an interworking connection:
addcon slot.port.DLCI local_nodename slot.vpi1.vci1
where the first slot has a Frame Relay card, and the second slot has a BTM. (In an IGX interface shelf, the only card that supports the trunk to the hub is the BTM.)
Step 2 The network segment:
addcon slot.port.vpi1.vci1 remote_nodename slot.port.vpi2.vci2
where the card in slot is a BNI
Step 3 For segment 2:
addcon slot.vpi2.vci2 local_nodename slot.port.DLCI
where the second slot is a Frame Relay card.
|
Note The vpi and vci must match only at the segment on the local interface shelf. Apart from this requirement, the vpi.vci on segment 1 can also be the same as the vci.vpi on segment 2. |
To convert a routing node to an interface shelf, first remove the routing node from the network by deleting all connections then deleting and downing all lines and trunks. See information in the WAN Switching System Overview , or in the interface shelf section in the Understanding and Enablin g Software Functions on IGX 8400 Switches tech note.
For information on troubleshooting the Cisco IGX 8400 series, see "Checking AC Power Supplies."
For software configuration and service provisioning information, see the Cisco IGX 8400 Series Provisioning Guide, Chapter 1, "Introduction to the Cisco IGX 8400 Series."
For more information on switch software commands, refer to the Cisco WAN Switching Command Reference, Chapter 1, "Command Line Fundamentals ."
Posted: Thu May 15 08:26:42 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
