Document ID: 10712
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Site Preparation
Installation Procedures
Pre-Installation Phase Checklist
Physical Installation Phase Checklist
Configuration Phase Checklist
Acceptance Phase Checklist
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document is a quick reference guide to installing Cisco StrataCom IGX products. However, the standard installation reference manual should serve as the primary reference when installing this product. Refer to the following:
-
IGX 16/32 Stanalone and Rackmounted Installation (SWSW Version 9.3)
-
IGX 8 Standalone and Rackmounted Installation (SWSW Version 9.3)
The physical installation for the IGX is relatively easy. A single installer can unpack the node. Cisco System recommends that another person assist with moving the equipment off of the pallet and positioning. The STRATM cabinet has casters, but it is 82 inches tall and may tip over while moving it. Additional time on site is required to complete rack mount installations.
Prerequisites
Requirements
The installer should be trained in basic electricity and have some understanding of basic telecommunications. A standard set of technician tools and a laptop DOS PC to run the StrataView Lite application may be required. Assuming the installation is controlled and supervised by the OSS, the installer should also be familiar with the basic operation of the IGX equipment including:
-
Power requirements for the various models (110VAC, 220VAC, or -48VDC).
-
Proper power termination procedures (mainly for DC systems).
-
Proper circuit card removal and replacement procedures.
Components Used
IGX nodes can be ordered as stand-alone, rack mount or factory installed in an enclosure (STRATM cabinet). A single installer can unpack the node; however, it is recommended that another person assist with moving equipment off of the pallet and positioning. The STRATM cabinet has casters, but it is 82 inches tall and may tip over. Initial configuration must be performed via the node's async control port. HDM card has hardware jumpers that may need to be configured for the your application. A modem should be installed for remote access. Cables between the trunk card(s) in the node and the customer CSU(s) or patch panel(s) must be connected. Once this is complete, a command is issued via the control port to add the new node into the network. At this time, the new node can be reached from any other node in the network and by the network management system (NMS) application, StrataView Plus (SV+).
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Site Preparation
The IGX has the following site preparation requirements:
-
Space—Each IGX requires floor space of 22 inches (55.9cm) wide and 80 inches (203.2cm) deep to assure sufficient clearance around the cabinet and allow access to the front and back of the unit.
-
Power—An AC or DC power source must be available within 6 feet (2m) of the rear of the IGX. A fully-loaded AC-powered node may require up to 2100 VA. A DC version requires up to 1680 VA at -48 VDC.
-
Cooling—The site must be capable of maintaining an ambient temperature of 40C maximum while the system is operating (recommended range is 20C to 30C). A fully-loaded IGX may dissipate up to 7200 BTUs. It is extremely important that the IGX is positioned to assure an unrestricted air flow through the enclosure.
-
Dimensions:
-
Stratum Cabinet—23.09" W x 80.11" H x 36"D
-
Shipping Weight:
-
600 pounds (270 kilograms) for a fully loaded IGX 32
-
400 pounds (180 kilograms) for a fully loaded IGX 16
-
270 pounds (122.7 kilograms) for a fully loaded IGX 8
-
-
Installation Procedures
Follow the steps below for installation instructions.
Pre-Installation Phase Checklist
-
Ensure that the site survey document is obtained from the Program Manager or the customer and that it has been reviewed (if NIS service has been purchased, the Program Manager will supply the documents).
-
Call the installation site contact one week in advance to confirm appointment.
-
Complete the checklist to confirm the following:
-
Power is installed.
-
The customer-supplied cables and equipment are installed.
-
The trunk circuit(s) is installed.
-
Cisco equipment is on site.
-
The dial-up phone line is installed.
-
-
Prepare installation procedure (install script) for installer (location, contacts, description, special tools required, hardware configuration information, connectivity diagrams, and so on).
Physical Installation Phase Checklist
-
Call the customer's network control center within 10 minutes of arrival to confirm presence.
-
Position the cabinet containing the IGX in the designated position. If rack mounting, refer to the Installation Manual for the proper procedure.
-
Verify with voltmeter that correct power is provided for IGX model being installed.
-
Ensure IGX card placement is as specified in supporting documentation. Position jumpers on applicable back cards to set ports for (DCE/DTE) as specified.
-
Ensure all circuit cards are seated and all locking screws tight.
-
Run cables between trunk cards and demarcation point (CSU, patch panel, and so on). If any trunk card is redundant, ensure Y cable is installed between redundant card pair.
-
Label each trunk cable with node name and slot number at both ends of the cable.
-
Properly secure and route all cables.
-
Attach dial-in modem and cable to IGX control port.
-
Apply power to IGX. Secure the power cord clamp for AC systems.
-
Notify Cisco GPS that node is ready for configuration and provide modem's phone number.
Configuration Phase Checklist
-
Using VT100 emulator, establish dial up connection to node. The default configuration for the IGX control port is 9600 8 1 N.
-
Important! Verify that the node is running specified system software release. Download software as required using dspcd x (where x = slot position of each network processor card (NPM).
-
Verify each card is running specified firmware release using the dspcds command. If required, download firmware.
-
Configure the node name using cnfname xxxxxxxx (where x is the node name).
-
Configure the node number using the rnmnd xxx command (where x is the node number).
-
Enable the software features purchased using the cnfswfunc command (second password needed to enable).
Note: Ensure that the features enabled on the new node are the exact same as those enabled on the network. You can potentially lose network features as a result of misconfiguration on a new node added to the network.
-
Configure the node's LAN address using the cnflan x.x.x.x y.y.y.y command (x = node's LAN IP address, y = subnet mask).
-
Configure the node's Network IP address (IP relay address) using the cnfnwip x.x.x.x y.y.y.y command (x = node's IP relay address, y = subnet mask).
-
Configure the node's system-wide parameters using the cnfsysparm command (as specified by the customer or Project Manager).
-
Modify additional IPX/IGX configuration parameters as specified by the customer or Project Manager.
-
Up and configure packet trunk parameters as specified by the customer or Project Manager:
-
uptrk x (where x = NTC slot number)
-
cnftrk x (where x = NTC slot number)
-
-
Contact the customer's network control center and have them up and configure the packet lines on the adjacent nodes. Ask the network operator to not perform an add packet line command for these nodes.
-
Ensure the trunk line is operational. If not, determine the cause of the problem by having the installer perform a loopback on the CSU, patch panel, and so on. Do the dsptrks command (the output should show "Clear-OK" status).
-
Add the node into the network. Allow network updates to finish before adding additional trunks. Enter the addtrk x command (where x is the NTM slot number) and the dsprevs command (wait until all nodes indicate their software revision).
Acceptance Phase Checklist
-
Switch NPM cards to test functionality using the switchcc command.
-
Log in and ensure off-line NPM returns to standby mode.
-
Perform a bus switchover to ensure functionality using the cnfbus command.
-
Ensure no power supply or other faults exist, using the dspalms command.
-
Installer gets customer representative to acknowledge completed installation.
-
Close out job and report status to Cisco Project Manger or customer contact.
The following table summarizes the minimum configuration information needed before the node can be added into the network:
|
Item |
Command |
Notes |
|---|---|---|
|
Node Name |
cnfname |
Eight characters maximum. |
|
Node Number |
rnmnd |
Range is from 1 to 160 (>63 optional). |
|
LAN IP Address |
cnflan |
May not be required. |
|
IP Relay Address |
cnfnwip |
Used for Telnet and stats TFTP. |
|
Software Options |
cnfswfunc |
Software features to enable. Note: Features are purchased items (reference the sales order). Some have network-wide significance, others have only local significance. |
|
Software version |
dspcd x |
x = processor slot number. Note: All StrataCom switches must be running the same release of software. If the node to be installed does not have the required version, it must be downloaded. |
|
Firmware version |
dspcds |
May require certain release. |
|
Slot/trunk number |
cnftrk x |
x = slot number. Need to configure trunk parameters based on type of trunk (DS1, subrate, DS3, or OC3). |
|
System Parameters |
cnfsysparm |
Some parameters have network-wide significance. Need to match the existing nodes. |
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for WAN Switching |
| Network Infrastructure: WAN Routing and Switching |
Related Information
- Cisco WAN Switching Solutions – Cisco Documentation
- Guide to New Names and Colors for WAN Switching Products
- Downloads – WAN Switching Software
- Technical Support – Cisco Systems
| Updated: Apr 17, 2009 | Document ID: 10712 |
