Table of Contents

Processor Card Types

Nodal Processor Module

NPM Processor and Memory Capacity
NPM Redundancy
NPM Faceplate and LEDs

System Clock Module

SCM Features and Functions
Using the Power Supply Monitor Connector

Optional Alarm Interface Cards

Alarm Relay Module

User Commands
Alarm Relay Interface Description

Maintenance and Troubleshooting

Card Self-Test
Card Replacement

Common Alarms, Controls, and Indicators

Processor Cards

This chapter describes the hardware and functionality of IGX processor cards. The description of each card includes:

• Function
  
  
• System interconnect
  
  
• Faceplate indicators
  
  

Other publications that relate to IGX operation are:

• The Cisco IGX 8400 Series Installation and Configuration publication describes installation, troubleshooting, user commands, repair and replacement, and the rack-mount Cisco IGX 8420-to-IGX 8430 conversion.
  
  
• The Cisco WAN Switching Command Reference publication and the Cisco WAN Switching SuperUser Command Reference publication describe standard user commands and superuser commands.
  
  
• The Cisco WAN Manager Installation publication and the Cisco WAN Manager Operations publication both contain information on network management.
  
  

Processor Card Types

Table 3-1 lists the processor cards that can operate in a Cisco IGX switch.

The processor card group consists of the nodal processor module (NPM) and the system clock module (SCM). In conjunction with the system bus, the processor group is responsible for system timing, network control, and status reporting.

Nodal Processor Module

The nodal processor module (NPM) is a 68040 microprocessor-based system controller that runs the software for controlling the IGX switch. The NPM communicates with the other system cards over the control bus. Figure 3-1 illustrates the relation of the NPM to other parts of the system. The NPM performs the following major functions:

• Runs the software for controlling, configuring, diagnosing, and monitoring the IGX switch
  
  
• Sends configuration and control commands over the control bus to other cards in the switch
  
  
• Receives statistics, status, and alarm messages from the other cards in the switch
  
  
• Generates all system bus control signals for directing the interpretation of address buses and controlling data transfers
  
  
• Communicates with other nodes in the network
  
  

The NPM communicates with all other nodes through a trunk that uses a reserved queue on the trunk. The NPM communication link with other nodes carries information about new connections, topology changes, and rerouting.

One version of the NPM-32 and two versions of the NPM-64 exist. The total of three NPMs are the NPM-32, the NPM-64, and the NPM-64B. The NPM-32 and the NPM-64B use +5 VDC flash memory. The next section, "NPM Processor and Memory Capacity ," describes NPM memory.

NPM Processor and Memory Capacity

The DRAM memory in an NPM holds the switch software for performing the regular functions of the NPM. The NPMs also have memory features that let you download new software releases over the network and maintain the system software and its configuration if the power fails. Non-volatile Flash EEPROM supports software downloading over the network. Battery-backup RAM (BRAM) stores system configuration data. Table 3-3 shows the memory capacity of each NPM.

NPM Redundancy

An IGX has one NPM in a non-redundant system or two NPMs in a redundant system. In a non-redundant system, an NPM resides in either front slot 1 or front slot 2. For a redundant system, NPMs reside in slots 1 and 2. The NPM plugs into the system bus backplane. A utility bus in the backplane connects the NPMs in a redundant system.

NPM Faceplate and LEDs

The faceplate of the NPM has a green Active LED and a red Fail LED. (See Figure 3-2 .) The NPM monitors its own activity and, if a failure is detected, the Fail LED is lit. If the node has redundant NPMs, the on-line NPM is indicated by the lit Active LED, while the standby NPM has no lit indicators. In addition to the status LEDs on the NPM faceplate, information on any NPM can be displayed at a terminal by executing the dspcd command.

System Clock Module

The system clock module (SCM) card provides the main clock generation function for the IGX. It generates the system clock and trunk synchronizing clocks. The SCM phase-locks the internal IGX timing to the selected clock source for network synchronization. Each IGX node must have an SCM. The SCM plugs into back card slot 1.

SCM Features and Functions

The NPM and SCM card sets are the backbone of the IGX: without an NPM and SCM, the node is inoperative. The NPM controls and monitors the SCM control buses. A single SCM can support redundant NPMs.

In addition, the SCM provides:

• Two low-speed communications paths for a control terminal, a printer, or one or two modems
  
  
• One LAN communication path for connecting the Network Management System to the IGX
  
  

The SCM circuits include the following:

• Internal clock generator for the node
  
  
• Clock detection, alarm status, and control from the NPM
  
  
• Phase lock loops
  
  
• External clock input
  
  
• Clock, power supply, temperature, and fan monitoring
  
  
• Bus expansion
  
  
• Reset circuitry
  
  
• Ports for a control terminal, printer or modem, and LAN AUI
  
  
• Two EIA/TIA-232 serial port interfaces
  
  

The two serial EIA/TIA-232 ports provide connection to control terminals and modems for remote access to the node. In conjunction with the SCM, the NPM also supports a high-speed Ethernet LAN port for faster system statistics transfer between the node and a Cisco WAN Manager NMS workstation. This port conforms to the requirements of IEEE standard 802.3 for Ethernet.

The SCM has duplicates of the internal clock circuitry and its associated phase lock loops and NPM-related control circuitry. One clock circuit operates off the System A Bus, and the other operates off the System B Bus. Both circuits operate independently and are monitored separately to provide complete backup if a circuit fails (which would cause the Fail LED to turn on). However, because both the System A bus and System B bus clock circuits exist on a single card, removing the SCM disrupts system operation. The lower priority SCM circuits are not duplicated. The lower priority circuits are the external clock input, control and auxiliary ports, and monitoring circuits for power supplies, cabinet temperature, and fans. A failure in a lower priority circuit does not cause a system failure, but the SCM reports the problem.

The Ext Clock connector on the faceplate of the SCM provides an interface for an external source for a high-stability clock. This clock is configurable as the primary, secondary, or tertiary clock. The input is 1.544 MHz for T1 systems and 2.048 MHz for E1 systems. In addition, one of the trunk or circuit line inputs can also serve as a source of timing for the node. If no clock source is selected, the clock source is the internal IGX clock.

Figure 3-3 and Table 3-4 describe the SCM faceplate connectors and LEDs. When you correlate the descriptions in the table with the callouts in the figure, read from the top to the bottom.

In addition to the clock functions, the SCM provides a pair of low-speed, serial communications ports. The control terminal port is a bidirectional port for connecting the IGX to a local network control terminal or to a modem for remote terminal connection. The auxiliary port connects to a maintenance log printer, an additional dumb terminal, an alarm message collector, external device window, or an auto-dial modem for automatic reporting of local IGX alarm conditions. You can program the modem to dial into the Technical Assistance Center (TAC) for assistance when a network alarm occurs. You can reach the TAC through Cisco Customer Engineering at 800-553-2447 or 1-408-526-4000.

Table 3-5 lists the pin assignments for the LAN connector.

Using the Power Supply Monitor Connector

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.

Optional Alarm Interface Cards

The alarm relay card set is optional. The set consists of an alarm relay module (ARM) front card and an alarm relay interface (ARI) back card. This card set provides alarm summary outputs by using relay contact closures.

The alarm summary feature provided by the Alarm Relay cards provides both a faceplate visual indication of an IGX node alarm as well as a set of relay outputs (dry-contact) for indicating node and network alarm indications. A visual alarm history indication is also provided. This alarm reporting is separate and is in addition to the alarm output at the node's control port, which provides a data output to a control terminal, such as the Cisco WAN Manager Network Management Station. Table 3-6 summarizes the alarm conditions and the resulting indications.

One set of alarm relays is used to signal a major alarm or minor alarm on the node. One pair of contacts on each relay is used for audible alarms. These contacts are in series with a faceplate alarm cut-off (ACO) switch. The other set of relay contacts are used for visual alarms and are not affected by the ACO switch. When the ACO switch is activated, a faceplate ACO indicator lights up as a reminder to the operator. If the ACO switch is activated to disable the node's audible alarm output and a second alarm occurs, the audible alarm is re-activated. Two faceplate LEDs provide local indication of network alarms.

The alarm reporting feature requires a card set that includes an ARM front card and an ARI back card. This card set can reside in any slot except the reserved slots. However, Cisco recommends that the front card go in the slot on the far right. Because a failure of either of these cards does not affect service, card redundancy is not necessary.

Alarm Relay Module

The alarm relays are controlled by system software through Control Bus commands. The ARM interface with the Control Bus allows the card to receive alarm signals from the NPM and to send status signals back to the NPM. The firmware on the ARM decodes the alarms. The ARM does not connect to the Cellbus because it does not packetize user data.

The ARM faceplate contains the alarm LEDs, ACO, and History Clear push buttons, and the active and fail LEDs indicating the status of the ARM card (see Figure 3-4 and Table 3-7). The ARM card is used in conjunction with an ARI card. The ARI card connects to the ARM at the P2 connector. Relay drive signals originate in the ARM to operate relays on the ARI.

The ARM periodically runs a background self-test to determine the state of the card. If the card fails this self-test, the faceplate Fail LED turns on, and the Active LED turns off.

User Commands

Three commands apply to the ARM card set:

• addalmslot
  
  
• delalmslot
  
  
• dspcd
  
  

Alarm Relay Interface Description

The alarm relay interface (ARI) card contains the alarm relays and their associated relay drivers. Alarm outputs are dry contact closures or opening contacts from Form C relays. The user must supply the voltage source to be switched by the IGX. Any source or load can be switched as long as it meets the following requirements.

A female DB-37 connector resides on the faceplate for connection to the customer's office alarm or alarm-reporting system. Refer to Figure 3-5 for an illustration of the ARI faceplate.

Maintenance and Troubleshooting

The following paragraphs describe the maintenance and troubleshooting features associated with the ARM card set. Preventive maintenance is not necessary.

Card Self-Test

Diagnostic routines periodically run to test the card's performance. These diagnostics run in the background and do not disrupt normal traffic. If a failure is detected during the self-test, the faceplate red Fail LED turns on. In addition, you can check the status of the card by using the dspcd command at the control terminal. If a card failure is reported, the report remains until cleared. To clear a card failure, use the resetcd command.

There are two types of resets: hardware and failure. The reset failure clears the event log of any failure detected by the card self-test and does not disrupt card operation. The hardware reset reboots the firmware and resets the card, which momentarily disables the card.

Card Replacement

ARM card set replacement is the same as other card replacement. For these procedures, refer to the repair and replacement description in the Cisco IGX 8400 Series Installation publication.

Common Alarms, Controls, and Indicators

Front cards and back cards have faceplates with indicator LEDs. Most cards have both a green Active LED and a red Fail LED at the bottom of the faceplate. For definitions of the port status LEDs on a back card, refer to the section that describes the back card.

Posted: Sat Aug 31 17:56:49 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.