Table of Contents

Cisco IGX 8400 Series Cards

This chapter provides a description of the cards available for use in the IGX node. Some of the cards described in this manual may no longer be available for purchase, so please check with your account representative for card availability.

Most cards use the standard installation and initial configuration procedures described in "Installing the IGX" This chapter details exceptions and recommendations specific to each card.

Note   The following cards are not supported in switch software Release 9.3 or later: FTM and back cards, BTM and back cards, ALM/A and back cards, and ALM/B and back cards. For information on these cards, refer to IGX documentation from earlier switch software releases.

For information about the BPX, see Chapter 1, "The BPX Switch: Functional Overview ," in the Cisco BPX 8600 Series Installation and Configuration manual.

Functional Overview

The Cisco IGX 8400 Series WAN switch uses combinations of front cards and back cards (or modules) to provide the user with greater configurational adaptability and flexibility. These modules can be classified into functional types as follows:

Processor cards are necessary for node function. Without a processor card, the switch has no software and cannot continue with power-on.

Alarm cards are optional, and are recommended because they provide alarm summary information as an aid in troubleshooting node and network problems.

Service cards provide a wide variety of information-handling services, including the following:

Nodal Processor Module

The IGX nodal processor module (NPM) group consists of a front card (called NPM) and a system clock module (SCM) back card.

The NPM performs the following major functions:

The NPM has a 68040 microprocessor-based system controller running switch software for the IGX chassis and communicates with other IGX cards over the control bus. In conjunction with the system bus, the NPM is responsible for system timing, network control, and status reporting.

Figure 2-1 illustrates the relation of the NPM to other parts of the system (including attached peripherals).

NPM Front Card

The NPM front card monitors its own activity. When a failure is detected, the fail LED is lit. In nodes with redundant NPMs, the active NPM is indicated by an active LED, while the standby NPM will not have a lit active LED (see Figure 2-2 ). To display information on any NPM from the switch software command-line interface (CLI), use the switch software dspcd command.

Table 2-1 describes NPM front card memory and memory expansion capability for all three NPM front card versions.The switch software image is stored in the dynamic RAM (DRAM), with non-volatile Flash electrically-erasable programmable ROM (EEPROM) supporting switch software image download over the attached network. Battery-backup RAM (BRAM) stores system configuration data.

NPM Failovers and Card Redundancy

In a nonredundant system, the NPM front card resides in either slot 1 or slot 2 (see the "Disabling NPM Redundancy" section for information on disabling NPM redundancy). In a redundant system with two NPM front cards, the front cards reside in slot 1 and slot 2. A utility bus in the backplane connects redundant NPMs.

Redundant NPMs have automatic failover, with the redundant card becoming active as soon as a failure occurs on the primary NPM. The failed NPM will report an alarm condition through the fail LED on the failed card's faceplate.

In automatic failover, configuration and operational information changes are shared by both cards as they occur.

Disabling NPM Redundancy

NPMs are shipped with NPM redundancy enabled.However, if you have only one NPM installed in your chassis, your node will continue to report a minor alarm until you disable NPM redundancy on that node. To disable NPM redundancy, use the following procedure.

Step 2   At the switch software CLI, disable NPM redundancy with the switch software cnfnodeparm 16 n command.

Step 3   Log out of the IGX node.

System Clock Module Back Card

The system clock module (SCM) back card provides the main clock generation function for the IGX. The SCM phase-locks internal IGX timing to the selected clock source for network synchronization. The SCM also measures cabinet temperature and provides external interfaces for network management access to the node.

Each SCM has the following external interfaces (see Figure 2-3):

For a description of the SCM LEDs, see Table 2-2.

The power supply monitor connector allows you to connect an external power supply monitor. Pins 2 and 3 indicate the status of the power supplies. These pins are TTL binary logic signals, with a value of zero indicating a power supply failure and a value of one indicating normal power supply operation. To use the power supply monitor connector, you need a device that responds with a fail condition when a zero TTL logic level is present on pin 2 or pin 3.

Caution   Do not use the RJ-45 connector on the SCM back card to connect your PC or terminal to the IGX. Power from the power supply monitor connector will cause damage to your PC or terminal.

Failovers and Card Redundancy

The SCM has integrated, independently-operating internal clock circuitry and phase-lock loops, with one clock circuit operating system bus A and the other clock circuit off system bus B. If the system bus A fails, the SCM fails over to the system bus B clock circuitry and the fail LED will turn on. Node operations will not be affected by SCM back card fail over.

Lower-priority SCM circuits, such as external clock input, control and auxiliary connectors, and power supply, cabinet temperate, and fan monitoring circuits are not duplicated. Failure of lower-priority circuits does not cause a system failure, but the SCM reports an alarm.

Each operating IGX node must have an SCM. Removal of the SCM disrupts system operation. The SCM resides in back card slot 1 (for information on installing back cards, see the Installing the IGX  chapter in the Cisco IGX 8400 Series Installation Guide ).

Tip One SCM is sufficient to support redundant NPM front cards.

External Clock Sources

The external clock connector is a 15-pin input designed to allow network synchronization signals from an EIA/TIA-422 external clock source. The external clock signal must be 1.544 MHz or 2.048 MHz.

The external clock source can be configured as a primary, secondary, or tertiary clock source.

Trunk or line inputs can also serve as a source for timing for the node. If no clock source is detected, the node will use the internal IGX clock (on the SCM) as the clock source for the node.

An external clock source can be connected to the SCM card using the external clock adapter cable. The external clock device can be either 1.544 MHz or 2.048 MHz EIA/TIA-422 square wave signals. Selection is made through software.

For information on configuring external clock sources for an IGX node, see the "Making External Clock Connections" section in the Cisco IGX 8400 Series Installation Guide.

NPM Installation

The active and redundant NPMs must be installed in slots 1 and 2. The NPM front card and SCM back card use a standard IGX card installation (see the "Inserting the Cards" section in the Cisco IGX 8400 Series Installation Guide).

NPM Management

Primary management tasks include maintaining and upgrading the switch software and firmware images for the IGX node, monitoring alarm states, and collecting statistics. In addition, Cisco recommends exercising redundant NPMs occasionally using the switch software command, switchcc.

Switch Software Management

Switch software management tasks can be conducted through a network management station running a network management program, such as Cisco WAN Manager, or through using the switch software command-line interface (CLI).

Replacing or Upgrading the Switch Software

Before upgrading the switch software on a node, confirm the compatibility of the switch software and the firmware image(s) found on the cards installed in the node. Some switch software upgrades may require an additional firmware upgrade on some or all of the cards installed in the node.

For information on switch software and firmware compatibility, see the Compatibility Matrix at http://www.cisco.com/public/sw-center/sw-wan.shtml.

Note   If a firmware image upgrade is necessary for a card installed in the node, you may need to upgrade the card's firmware before upgrading the switch software image to avoid operational problems in your network. Check the firmware release notes for specific information on upgrade procedures.

Optional Peripherals

At least one node in a network should have a Cisco WAN Manager terminal, a control terminal, or a dial-in modem connected to it. Any control terminal connected in the network can configure, manage, monitor, and diagnose the entire network. In addition, at least one node in a network can have a connected printer for error and event reports.

The control terminal and printer connect to two EIA/TIA-232 serial ports. These ports are the control terminal and auxiliary port on the SCM faceplate. These serial ports support all standard asynchronous data rates from 1200 to 19,200 bps. The default rate is 9600 bps. Data rates and the type of equipment connected to the ports are software-configurable.

Alarm Relay Module

The IGX alarm interface module consists of an alarm relay module (ARM) front card and an alarm relay interface (ARI) back card.

The module performs the following major functions:

---

Note    Alarm reporting through the alarm interface module is separate from alarm output to the node's control port which provides alarm data to a control terminal such as a CWM network management station.

---

One set of alarm relays signals a major or minor alarm on the node, with one pair of contacts on each relay being used for audible alarms. The other set of relay contacts is used for visual alarms (see Table 2-5).

.

Tip To turn off audible alarms, use the faceplate alarm cutoff (ACO) switch. When the ACO switch is activated, a faceplate ACO indicator is lit as a reminder to the user. 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.

Alarm Relay Module Front Card

The ARM front card requires the ARI back card for proper functioning. Alarm relays are controlled by switch software through control bus commands. Because the ARM does not handle user data, there is no ARM connection to the cell bus.

The ARM faceplate contains the alarm, active, and fail LEDs, and the ACO and history clear push buttons (see Figure 2-4 and Table 2-6).

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.

Alarm Relay Interface Back Card

The alarm relay interface (ARI) back card contains the alarm relays and their associated relay drivers. Alarm outputs are dry contact closures from form C relays. The user must supply the voltage source to be switched by the IGX. Any source or load can be switched if 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. For information on connector pinouts, see the "External Alarm Cabling" section in the Cisco IGX 8400 Series Installation Guide.

Refer to Figure 2-5 for an illustration of the ARI faceplate.

ARM Configuration and Management

Enable alarm display functionality on the ARM with the switch software addalmslot command. The ARM requires standard management and preventive maintenance tasks.

Making Alarm Relay Output Connections

To set up an ARM after installation, use the following procedure:

Step 2   Enter the switch software addalmslot slot command to activate alarm reporting from the card.

Step 3   Check the active LED on the front card faceplate.

Step 4   Test alarm output operation by creating an alarm on the node.

Tip Create an alarm by disconnecting a trunk cable from the connector on the back card.

Caution   To avoid disruption of necessary network traffic, do not generate a major alarm during periods of high network traffic.

Step 5   Check that the major LED lights up on the front card faceplate of the ARM.

Step 6   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 7   Remove the alarm from the node by restoring the connection you disabled in Step 4.

Step 8   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 DB-37 connector on the ARI card. The connector pin assignments with the alarm signal names are listed in Table 2-7.

ARM 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 behavior. 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 switch software dspcd command. If a card failure is reported, the report remains until cleared. To clear a card failure, use the switch software 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.

Service Modules

Service modules allow configuring of data, voice, ATM, Frame Relay (FR), and IP services over the IGX node. In an operational network, multiple service cards may be installed in the same physical chassis, with many different possible configurations of service types, interface connector types, and transmission formats. These service modules can be used in any of the three chassis models. However, careful planning of slot space and cabling is important for easy and efficient maintenance and troubleshooting tasks.

Standard Service Module LEDs

IGX service front cards and back cards have several standard indicator LEDs on their faceplates. While some cards may have additional LEDs, all cards have both a green active LED and a red fail LED located at the bottom of the faceplate.

Standard Service Module Installation

Caution   In order to contain electromagnetic interference (EMI) and radio frequency interference (RFI), and to ensure desired airflow for adequate chassis cooling, install a blank faceplate in any back card slots where no back card exists.

Except where noted, IGX service modules use a standard installation procedure (see "Installing the IGX" in the Cisco IGX 8400 Series Installation Guide).

Card Redundancy

Except where noted, you can configure the service module for 1:1 redundancy by installing a second, identical card group in another slot. Use a Y-cable to connect the two redundant back cards, then use the switch software addyred command to add Y-redundancy to the card's configuration. See Figure 2-6 for an illustration.

The hardware kits for this feature usually contain a second, duplicate card set, a set of Y-cables to interconnect the two card sets, and any other pieces that apply to the card types. Y-cable redundancy is not possible using back cards with different interfaces, such as an FRI T1 and FRI V.35.

Standard Service Module Configuration

For specific information on advanced card configuration tasks, refer to the information for your specific front card and back card combination, or to "Installing the IGX" in the Cisco IGX 8400 Series Installation Guide.

Standard Service Module Troubleshooting

The following paragraphs describe standard service module maintenance and troubleshooting features. Except where noted, preventive maintenance is not necessary.

Card Mismatch

When you connect an unsupported back card to the service module front card, the output from the switch software dspcds command informs you that you have a card mismatch.

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 switch software dspcd command at the control terminal. If a card failure is reported, the report remains until cleared. To clear a card failure, use the switch software resetcd command.

There are two types of resets: hardware and failure. The failure reset 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.

Network Trunk Module

Table 2-9 shows supported front and back cards for the network trunk module (NTM).

The NTM enables FastPacket transmission on a trunk established between two IGX nodes. NTM features include the following:

NTM Front Card

Note   There are two variants of the NTM front card: one uses an ACM1 adapter to connect two legacy card designs and the other is a single card version built for the IGX chassis. While functionally identical, their firmware cannot be interchanged. The single-card NTM requires firmware revision F or later.

An NTM front card can occupy any available front service card slot (slots 3 to 32). The module's back card depends on the desired trunk interface type. See the following usage information:

For a description of the NTM front card faceplate, see Figure 2-7.

NTM T1 Interface Back Card

The NTM T1 interface back card (BC-T1) terminates a single 1.544 Mbps T1 trunk on the network trunk module in the IGX, and provides the following features:

The BC-T1 uses a DB-15 interface connector (see Figure 2-8) and has loss of signal and loss of FastPacket alignment indicators on the back card faceplate (see Table 2-10).

NTM E1 Interface Back Card

The NTM E1 interface card (BC-E1) terminates an E1 trunk line on the NTM front card, and provides the following features:

Figure 2-9 and Table 2-11 provide descriptions of the BC-E1 status LEDs and connectors on the BC-E1 faceplate.

NTM Y1 Interface Back Card

The NTM Y1 interface back card (BC-Y1) terminates a Y1 line on the NTM front card, and provides the following features:

Figure 2-10 and Table 2-12 provide descriptions of the BC-Y1 status LEDs and connectors on the faceplate.

NTM Subrate Interface Back Card

The subrate interface back card (BC-SR) terminates subrate trunks on the NTM. The BC-SR provides the following features:

Because a subrate trunk facility interface operates in DCE mode with the subrate channel functioning like a synchronous data channel, the BC-SR back card always operates in DTE mode. Subrate trunks cannot pass clock signals, so you must make provisions for separate clock signalling sources for each IGX node connected to the network solely through subrate trunks (see the "Connecting an NTM E1 or Subrate Trunk" section in the Cisco IGX 8400 Series Installation Guide).

Universal Switching Module

Table 2-15 shows the front and back cards supported for the universal switching module (UXM and UXM-E).

Note   Information for the enhanced universal switching module (UXM-E) also applies to the UXM. For differences between the two cards, refer to the release notes for your card.

The enhanced universal switching module (UXM-E) provides ATM trunk and line service for the IGX. In trunk mode, the UXM-E supports network trunks and in port mode, the UXM-E supports either an ATM user-to-network interface (UNI) or a network-to-network interface (NNI). The back cards support multiple physical connector types, with ports operating at OC3/STM1, T3, E3, T1, or E1 rates.

The UXM-E can transport ATM cells to and from the IGX cellbus at a maximum rate of 310 Mbps in each direction. This maximum rate applies regardless of back card type.

Switch software limits the number of logical trunks and lines that can be configured on an IGX node as shown below:

These limits are independent of the number of UXM or UXM-E cards in the IGX switch chassis, because switch software monitors the number of configured lines and trunks, not the number of cards that are physically present.

When you reach these limits, switch software prevents activation of additional trunks or lines on the node, and you see an error message.

The UXM and UXM-E also support the following features for both trunk and port modes:

---

Note    The UXM and UXM-E cannot support more than 4000 gateway connections. All remaining connections can be user or networking connections. For example, if you configure 2500 gateway connections onto a UXM-E, you still have 5500 possible user or networking connections.

---

For information on initial configuration of a UXM-E, see the "UXM-E Configuration" section.

UXM-E Trunk Mode Features

In trunk mode, the UXM-E supports up to 8000 connections. The UXM-E in trunk mode cannot support more than 4000 gateway connections. All remaining connections can be either user or networking connections. For example, if you configure 2500 gateway connections, you still have 5500 connections available to be used for networking connections.

Between the network and customer premise equipment (CPE), the UXM-E communicates only ATM cells. However, on the cellbus, the UXM-E communicates either ATM cells or FastPackets, depending on the destination card type.

Traffic Management Features

Table 2-16 provides a summary of the traffic management features available on the UXM-E.

UXM-E Front Card

The UXM-E front card faceplate has five LEDs (see Figure 2-12). These LEDs indicate card status through different combinations of the fail, active, and standby LEDs. Use Table 2-17 during UXM-E troubleshooting (for more information on UXM-E troubleshooting, see the "UXM-E Troubleshooting" section).

UXM-E Back Cards

The UXM-E has many different back cards, providing support for various physical line and connector configurations. See Table 2-18 for more information.

For images of sample UXM-E back cards, see Figure 2-13, Figure 2-14, Figure 2-15, and Figure 2-16.

For technical information on the various physical line types, see the "UXM-E Physical and Electrical Specifications" section in the Cisco IGX 8400 Series Installation Guide.

Most UXM-E back cards have a tricolor LED for each line that indicates the status of the line. This tricolor LED is located above the physical connector for the line. See Table 2-19 for a description of the tricolor LED.

Note   The T1 and E1 back cards do not have the standard service module active and fail LEDs to indicate card status. If a T1 or E1 back card failure is detected, all of the tricolor LEDs on the back card turn red.

The appearance of UXM-E back card faceplates will vary based on the back card's physical line type, physical connector type, and number of physical connectors. See Figure 2-13, Figure 2-14, Figure 2-15, and Figure 2-16 for sample UXM-E back cards.

Figure 2-13 shows a BC-UAI-4-155-SMF back card faceplate. The following back cards have similar faceplates:

Figure 2-14 shows a BC-UAI-6-T3 back card faceplate. The following back cards have similar faceplates:

Figure 2-15 shows a BC-UAI-8-T1-DB-15 back card faceplate. The following back cards have similar faceplates:

Figure 2-16 shows a BC-UAI-8-E1 BNC back card faceplate. Each BNC connector carries traffic in only one direction. The BC-UAI-4-E1 has a similar faceplate.

UXM-E Installation

Tip Switch software limits the number of logical trunks and lines that can be configured on an IGX switch. To optimize your chassis space, do not install more than 64 lines or 32 trunks (these totals include all lines or trunks available on all trunk or line modules in the chassis). Modules used for hot standby do not count toward these totals.

The UXM-E uses a standard IGX card installation (see "Installing the IGX" in the Cisco IGX 8400 Series Installation Guide).

UXM-E Redundancy

Like other IGX service modules, the UXM-E can be configured for Y-cable redundancy. Both cards, the primary and the redundant, must be installed before you configure them for Y-cable redundancy.

The UXM-E features hot standby, in which the redundant card receives card configuration information as soon as you finish specifying redundancy. The standby card also updates its configuration as the active card configuration changes.

For more information on setting up Y-cable redundancy, see the "Card Redundancy" section.

UXM-E Configuration

When you insert a new UXM-E into the backplane, or apply power to the IGX node, the UXM-E firmware reports the card type and the number of physical lines on the back card to the node's switch software.

Note   On activation, the UXM-E reports the number and type of physical ports available on the attached back card. This back card configuration information is retained by switch software even if the back card is later removed.

To activate a trunk, use the switch software uptrk command (see Chapter 4, "Cisco IGX 8400 Series Trunks").

To activate a line, use the switch software upln command (see Chapter 5, "Cisco IGX 8400 Series Lines").

UXM-E Management

Most UXM-E management tasks are general trunk or line management tasks. See Chapter 4, "Cisco IGX 8400 Series Trunks," or Chapter 5, "Cisco IGX 8400 Series Lines" for more information on managing and troubleshooting trunks or lines.

UXM-E as a Clock Source

A UXM-E line or trunk can serve as the clock source for the IGX node. To configure the clock source, use the switch software cnfclk command. To display available clock sources, use the switch software dspclksrcs command. To show the current clock source, use the switch software dspcurclk command.

For more information about clocking on IGX nodes, see "Cisco IGX 8400 Series Nodes"

Y-Redundancy and VC Merge on the UXM-E

Note   Because VC merge is not supported on the UXM, y-redundancy cannot be set up using a UXM-E and a UXM without generating a feature mismatch error. If y-redundancy is set up between a UXM-E and a UXM, the VC merge feature cannot be enabled.

Before setting up y-redundancy on two UXM-E cards, make sure that VC merge feature support is enabled on both cards. Both cards must run the appropriate firmware to support the VC merge feature.

For more information on enabling VC merge on the IGX, see the "VC Merge on the IGX" section in "IP ServiceFunctional Overview."

Note   VC merge on the IGX is not supported in releases preceding Switch Software Release 9.3.40.

UXM-E Troubleshooting

Switch software classifies UXM-E trunk statistics as physical or logical. See the following list of rules used to distinguish physical trunk statistics from logical ones:

Trunk Statistics on the UXM-E

The following switch software commands apply to statistics for physical lines within an IMA trunk:

Statistics Commands for Troubleshooting

You can configure bucket statistics through Cisco WAN Manager (CWM) for logical lines, ports, and channels (connections). Statistics configuration in CWM requires the TFTP mechanism. You can also enter commands on the CLI. Refer to the Cisco WAN Switching Command Reference for descriptions of the following commands:

Integrated and Statistical Line Alarms

Integrated alarms for the UXM-E consist of LOS, LOF, AIS, YEL, LOC, LOP, Path AIS, Path YEL, Path Trace, and Section alarms. The display for the dsplns command lists an alarm if the related event occurs. You can configure the event duration that qualifies and clears an alarm with cnflnparm.

You can configure the class, rate, and duration for setting and clearing of statistical alarms with the cnflnalm command. Refer to the description of cnflnalm in the Cisco WAN Switching Command Reference publication for a list of all possible line alarm types. The display for the dsplnerrs command shows data for existing alarms. To clear the statistical alarms on a line, use the clrlnalm command.

Loopback and Test Commands

The UXM-E supports local and remote loopbacks. You can establish a local loopback on either a connection or a port. Remote loopbacks are available for connections only. No line loopbacks are available for the UXM-E.

Card Mismatch

Note   Card mismatch is not reported when the front card is in standby. If the card becomes active and there is a mismatch condition, the UXM-E will report a card mismatch.

The UXM-E uses a standard card mismatch notification for unsupported back cards.

If the front card was previously active, the UXM-E provides mismatch notification for supported back cards featuring a different line type than the previously-installed back card, or if the back card has a smaller number of the correct line types than what the UXM-E previously reported to switch software. Attaching a back card with more ports of the correct line types does not trigger a card mismatch. If the front card has not yet been activated, the UXM-E does not provide mismatch information for supported back cards because a supported back card mismatch has not occurred.

For card mismatch examples, see Table 2-21.

Universal Voice Module

Table 2-22 shows the front and back cards supported by the universal voice module (UVM).

The universal voice module consists of a UVM front card and a universal voice interface (UVI) back card with physical connectors for T1, E1, or Y1 lines. The module supports channelized T1, E1, or Y1 lines carrying voice, data, or voice+data traffic. For information on the connections supported by the UVM, see Table 2-23.

UVM features include the following:

For more information on voice technology specifications, see the "UXM-E Physical and Electrical Specifications" section in the Cisco IGX 8400 Series Installation Guide.

Tip To configure more than 16 channels for LDCELP or CSACELP with G.729, you must configure the UVM to pass remaining time slots to a second UVM for processing through configuration of line pass-through. During line pass-through, one UVM port connects to user equipment and the other port connects to another UVM. For more information on line pass-through, see Chapter 7, "Cisco IGX 8400 Series Voice Service"

Voice frequency compression ratios can be determined through selection of a kbps rate for the voice channel. For example, a 64 kbps voice channel does not compress voice traffic. A 32 kbps voice channel compresses voice traffic at 2:1. See Table 2-24, "Cisco IGX 8400 Series Voice Service" (Chapter 7), and the Cisco WAN Switching Command Reference for more information.

Idle Code Suppression on the UVM

Idle code suppression (ICS) allows bandwidth savings on an nx64 super-rate data connection used to carry video traffic conforming to the H.221 video codec frame protocol. The video channel is considered idle at any time when identical data occurs in relevant time slots for 256 consecutive T1, E1, or J1 frames. Depending on the data channel size, the number of consecutive identical bytes necessary to trigger idle code suppression can range from 256 to 2048 consecutive identical bytes.

To enable ICS on a data channel, use the switch software cnfdch command.

Tip In order to configure ICS on a data channel, the data channel must be used in an nx64 super-rate data connection that terminates on either a UVM or a CVM.

Fax Relay on the UVM

The fax relay feature compresses the DS0 bit stream of a G3 fax connection to 9.6 kbps for transport through the IGX network. Fax relay on the UVM is supported for LDCELP and G.729 connections.

Note   Fax relay on the UVM is not supported for connections using the G.729A standard (or PCM or ADPCM).

After being enabled, fax relay overrides the automatic fax upgrade feature. However, a data modem will still upgrade to PCM or ADPCM. This automatic upgrade feature suspends compression when a modem or fax tone appears on a voice connection.

To configure a fax relay channel, use the switch software cnfchfax command.

UVM Front Card

A UVM front card can occupy any available front service card slot (slots 3 to 32). The module's back card depends on the desired line interface type. See the following usage information:

See Figure 2-17 for a description of the UVM front card faceplate.

Universal Voice Interface Back Card

The UVM has three different UVI back cards, providing support for various physical line types. See Table 2-25 for more information.

Each physical connector on a UVI back card has a tri-color LED beneath it on the back card faceplate. The tricolor LED indicates the status of the port associated with that physical connector. See Table 2-26 for a description of the tricolor LEDs. See Figure 2-18 for a sample UVI back card.

Note   The BC-UVI-2E1EC has an additional multiframe alignment LED associated with each physical connector. See Table 2-27 and Figure 2-19 for details.

UVM Configuration

To specify voice connections on the UVM, use either Cisco WAN Manager or the switch software CLI. For information on accessing the switch software CLI, see the "IGX Configuration Summary" section in the Cisco IGX 8400 Series Installation Guide . For more detailed information on switch software commands used to provision voice service, see "Cisco IGX 8400 Series Voice Service"

UVM Troubleshooting

The UVM card set monitors and reports statistics on the following input line conditions:

Channelized Voice Module

Table 2-28 shows the front and back cards supported for the channelized voice module (CVM).

The CVM provides voice, data, and voice+data service for the IGX. Three different front cards and multiple back cards allow for users to select the configuration that best fits their networking environment.

The CVM supports the following features:

For more information on voice technology specifications, see the "Voice Circuit Support" section.

Note   The CVM does not support LDCELP or CSACELP compression and cannot terminate a connection from a UVM if the connection uses LDCELP or CSACELP.

Voice frequency compression ratios can be determined through selection of a kbps rate for the voice channel. For example, a 64 kbps voice channel does not compress voice traffic. A 32 kbps voice channel compresses voice traffic at 2:1. See Table 2-30, "Cisco IGX 8400 Series Voice Service" (Chapter 7), and the Cisco WAN Switching Command Reference for more information.

Tip Voice compression ratios approximately double when you enable internal VAD on that channel.

Idle Code Suppression on the CVM

Idle code suppression (ICS) allows bandwidth savings on an nx64 super-rate data connection used to carry video traffic conforming to the H.221 video codec frame protocol. The video channel is considered idle at any time when identical data occurs in relevant time slots for 256 consecutive T1, E1, or J1 frames. Depending on the data channel size, the number of consecutive identical bytes necessary to trigger idle code suppression can range from 256 to 2048 consecutive identical byes.

To enable ICS on a data channel, use the switch software cnfdch command.

Tip In order to configure ICS on a data channel, the data channel must be used in an nx64 super-rate data connection that terminates on either a UVM or a CVM.

CVM Front Cards

The CVM has three different front card options: standard CVM, CVM T1 EC, and CVM E1 EC.

The standard CVM supports the features listed in the "Channelized Voice Module" section. The CVM T1 EC features on-board echo cancelling circuitry for T1 lines. The CVM E1 EC features on-board echo cancelling circuitry for E1 lines.

CVM Back Cards

The CVM has three different back cards. Please refer to the "CVM Front Cards" section for compatibility requirements.

T1 Interface Back Card (BC-T1)

The BC-T1 back card provides a T1 line interface for a CVM front card. The BC-T1 back card has the following features:

See Figure 2-20 for a description of the BC-T1 back card faceplate.

E1 Interface Back Card (BC-E1)

The BC-E1 back card provides one E1 line interface for a CVM. The BC-E1 has the following features:

See Figure 2-21 for a description of the BC-E1 back card faceplate. The BC-E1 back card has an additional multiframe alignment LED. See Table 2-31 for details.

J1 Interface Back Card (BC-J1)

The BC-J1 back card provides a Japanese J1 circuit line interface for a CVM. The BC-J1 has the following features:

See Figure 2-22 for a description of the BC-J1 back card faceplate. The BC-J1 back card has an additional multiframe alignment LED. See Table 2-32 for details.

Universal Frame Module

Table 2-33 shows the front and back cards supported for the universal frame module (UFM).

The UFM provides Frame Relay (FR) service across a connection between two IGX nodes. The module supports ELMI and Frame Relay-to-ATM service interworking, and can support FR traffic through T1, E1, V.35, X.21, or HSSI interfaces.

There are three front cards in the UFM card set. See the "UFM-C Front Cards" section for more information about the two UFM-C front card models, and see the "UFM-U Front Card" section for information on the UFM-U front card. See Table 2-33 for information on front and back card compatibility.

UFM Network Integration

The following cards can terminate connections from a UFM:

---

Note    For connections with an endpoint on a Cisco MGX 8200 series platform, refer to either MGX  8220 or MGX 8250  documentation, as appropriate.

---

UFM Features

The UFM supports the following features:

---

Note    Logical ports must use contiguous time slots. See the "Making Frame Relay Connections" section in the Cisco IGX 8400 Series Installation Guide for more information.

---

UFM-C Front Cards

The UFM-C front cards can occupy any available front service card slot (slots 3 to 32). The module's back card depends on the desired interface type; please see the following usage information:

The UFM-C front cards support either four (the UFM-4C) or eight (the UFM-8C) T1 or E1 lines per back card. See Figure 2-23 for a description of a UFM-C front card faceplate. The UFM-C front cards use standard service card LEDs; see the "Standard Service Module LEDs" section for more information on these LEDs. For information on back cards compatible with the UFM-C, see Table 2-33.

Note   Actual data throughput on the card depends on hardware and on frame size. As the frame size decreases, throughput will decrease. For example, a frame size of 100 B results in a sustainable throughput of 16.384 Mbps. With 60 B frames, a throughput of 16.384 Mbps can result in data loss.

Tip UFM-8C front cards are simply labeled "UFM-C" while UFM-4C front cards are labeled "UFM-4C."

UFM-U Front Card

A UFM-U front card can occupy any available front service card slot (slots 3 to 32). The module's back card depends on the desired port type; see the following usage information:

In addition to features supported by the UFM-C (see the "UFM-C Front Cards" section), the UFM-U front card has the following features:

The aggregate port speed configurable across all ports is 24.576 Mbps. This speed is the maximum line speed and the over-subscription ceiling.

The UFM-U front card allows you to specify active ports and to set the maximum speed allowed on each active port. See the "UFM-U Configuration" section for more information. Figure 2-24 shows the UFM-U front card faceplate.

UFM-U Configuration

Because of hardware constraints, the UFM-U does not permit random combinations of speeds across active ports. Configuring active ports on the UFM-U requires that you use certain specified combinations (called modes) of maximum rates on these active ports.

Note   Specifying the maximum speed for active ports requires careful planning, so read the following information before attempting to configure your UFM-U active ports. To specify active ports and the maximum speed allowed on each active port, see the "Initial Configuration of the UFM-U" section.

Active ports on the UFM-U are grouped into port groups, which are indicated by alphabetic names. For example, Group A consists of ports 1 through 4 on the V.35 and X.21 back cards, and ports 1 and 2 on the HSSI back card. Group B consists of ports 5 through 8 on the V.35 and X.21 back cards, and ports 3 and 4 on the HSSI back card. Group C consists of ports 9 through 12 on the V.35 and X.21 back cards; the HSSI back card does not have a Group C.

Initial Configuration of the UFM-U

TimeSaver Specify your desired mode before you add connections to the card to avoid having to delete some or all of your connections and down your active ports before changing the mode. For information on changing the mode, see the "Configuring UFM-U Modes" section.

To configure your UFM-U on initial power-on of the module, use the following procedure:

---

Note    The UFM-U is initially set to mode 1 at card power-on.

---

Step 2   Select the appropriate mode for the card, based on desired maximum throughputs for each port group.

Step 3   Configure port speeds with the switch software cnfport command. For each port to be activated, set the port speeds at or below the maximum throughput shown in Table 2-34 and Table 2-35.

Step 4   Activate the appropriate ports for each port group with the switch software upport command.

Step 5   Add connections to the UFM-U with the switch software addcon command.

Calculating Maximum Throughput on the UFM-U

When configuring your active ports and selecting your mode, remember the following two rules:

When calculating your maximum throughput, you must add the maximum bit rate for each port in the port group to find the maximum group throughput before calculating the maximum throughput for the card.

Table 2-34 shows the maximum bit rate per port on the V.35 or the X.21 back card for each available mode. Table 2-35 shows the maximum bit rate per port on the HSSI back card for each available mode.

Note   In Table 2-34 and Table 2-35, the following abbreviations are used to reflect switch software command syntax: 3 = 3 Mbps = 3072 kbps 8 = 8 Mbps = 8192 kbps 10 = 10 Mbps = 10240 kbps

Configuring UFM-U Modes

Before changing the mode on a UFM-U, you must first determine whether the mode change will cause any changes in the maximum port speeds of any active ports. If the maximum port speed on an active port will change because of a mode change, you must first delete all connections in that port's port group and down all active ports in that port group before changing the mode.

For example, if you have connections on ports 1, 3, and 9 through 12 in mode 1 and you want to change to mode 4, you must first delete all connections on ports 1 and 3, then down ports 1 and 3 before changing to mode 4.

If you have connections on ports 1, 3, 5, 7, 9, and 11 in mode 2 and you want to change to mode 9, you must first delete connections on ports 1 and 3, then down ports 1 and 3 before changing to mode 9. After changing to mode, you must reestablish all of your connections on port 1 only.

Note   If you do not have connections on a port in the port group but the port has been upped, you must still down all ports in the port group before changing the mode.

See the "Changing the Mode on a UFM-U" section for information on how to change modes on the UFM-U.

Changing the Mode on a UFM-U

To change modes on a previously-configured UFM-U, use the following procedure:

Step 2   Deactivate all active ports in port groups where the maximum ports speeds will change with the switch software dnport command.

Step 3   Using the switch software cnfport command, configure new port speeds for all appropriate ports in any port group where maximum port speed changes will occur due to the mode change.

Step 4   Change the mode on the UFM-U with the switch software cnfmode command.

Step 5   Activate all necessary ports for the new mode with the switch software upport command.

Step 6   Add necessary connections to the UFM-U with the switch software addcon command.

UFI-8T1-DB-15 Back Card

Note   The UFI-8T1-DB-15 back card is compatible with the UFM-4C and UFM-8C front cards. It is not compatible with the UFM-U front card.

The UFM back card shown in Figure 2-25 has eight bidirectional, DB-15 connectors. For each line, one tricolor LED displays the status of the line using that connector (see Table 2-36). If the LED is off, the line is inactive.

UFI-8E1 Back Cards

Note   The UFI-8E1-DB-15 and UFI-8E1-BNC back cards are compatible with the UFM-4C and UFM-8C front cards. They are not compatible with the UFM-U front card.

There are two different E1 back cards available for the UFM—the UFI-8E1-DB-15 and the UFI-8E1-BNC. The UFI-8E1-DB-15 has eight bidirectional DB-15 connectors, and the UFI-8E1-BNC has 16 BNC connectors (two per port, with one transmit connector and one receive connector). See Figure 2-26 for a description of these two back card faceplates. For each line, one tricolor LED displays the status of the line using that connector (see Table 2-36). If the LED is off, the line is inactive.

UFI-12V.35 Back Card

Note   The UFI-12.V35 back card is compatible with the UFM-U front card. It is not compatible with either the UFM-4C or the UFM-8C front cards.

The UFI-12V.35 back card in Figure 2-27 for the UFM-U front card has six connectors, with each connector carrying two V.35 ports. Each port in the connector has an associated LED for indicating port state. See Table 2-38 for more information on these LEDs.

To use the UFI-12V.35 back card in DTE mode, use the V.35-DTE cable to connect the back card to DCE interfaces. For more information on the cables used with the UFI back cards, see the "UFM Cabling" section in the Cisco IGX 8400 Series Installation Guide.

Tip Each port on the UFI-12V.35 can be configured to support either normal clocking or loop timing. For more information on port configuration, see the "UFM-U Configuration" section.

Note   The following port speeds are supported on the UFI-12V.35 back card: 56, 64, 112, 128, 168, 192, 224, 256, 320, 336, 384, 448, 512, 640, 672, 768, 896, 960, 1024, 1280, 1344, 1536, 1920, 2048, 3072, 4096, 5120, 6144, 7168, 8192, 9216, and 10240 kbps.

UFI-12X.21 Back Card

Note   The UFI-12X.21 back card is compatible with the UFM-U front card. It is not compatible with either the UFM-4C or the UFM-8C front cards.

The UFI-12X.21 back card in Figure 2-28 for the UFM-U front card has six connectors, with each connector carrying two X.21 ports. Each port in the connector has an associated LED for indicating port state. See Table 2-39 for more information on these LEDs.

Tip To use the UFI-12X.21 back card in DTE mode, use the X.21-DTE cable to connect the back card to DCE interfaces. For more information on the cables used with the UFI back cards, see the "UFM Cabling" section in the Cisco IGX 8400 Series Installation Guide.

Note   The following port speeds are supported on the UFI-12X.21 back card: 56, 64, 112, 128, 168, 192, 224, 256, 320, 336, 384, 448, 512, 640, 672, 768, 896, 960, 1024, 1280, 1344, 1536, 1920, 2048, 3072, 4096, 5120, 6144, 7168, 8192, 9216, and 10240 kbps.

UFI-4HSSI Back Card

Note   The UFI-4HSSI back card is compatible with the UFM-U front card. It is not compatible with either the UFM-4C or the UFM-8C front cards.

The UFI-4HSSI back card in Figure 2-29 for the UFM-U front card has four connectors. Each connector has a tri-color status LED (see Table 2-40). Each connector corresponds to one port. For information on configuring these ports, see the "UFM-U Configuration" section.

TimeSaver Interfaces on the UFI-4HSSI back card are already in DCE mode (default) so you can directly connect any DTE interface to the back card using a straight pin-to-pin HSSI standard cable.

Tip The UFI-4HSSI back card can be configured in DTE mode by using the HSSI-DTE cable to connect back cards in DTE mode to DCE interfaces. For more information on the cables used with the UFI back cards, see the "UFM Cabling" section in the Cisco IGX 8400 Series Installation Guide.

Frame Relay Module

Table 2-41 shows the front and back cards supported for the Frame Relay module (FRM).

Note   The Frame Relay module (FRM) is no longer available for sale through Cisco Systems, Inc. However, the card set is supported in Switch Software Release 9.3.30 or later to allow legacy users to migrate their networks into the current switch software release. If you have questions regarding the availability of the FRM, contact your Cisco account representative (see "Obtaining Technical Assistance" section on page xiv for information on contacting Cisco if you do not have an account representative).

The FRM provides FR support for the IGX chassis, and supports the following features:

Firmware Compatibility

Firmware on the FRM front card must match the interface type found on the back card. See Table 2-42 for compatibility information. Use the switch software command, dspcd, to view the type of back card supported by your current FRM firmware.

Note   FRM front cards exist in two forms. One uses an ACM1 adapter. The other is a single-card or "native" version. Functionally, they are identical. For the single-card version, you must use FRM firmware version V or later.

Frame Relay Interface V.35 and X.21 Back Cards

Both the Frame Relay interface V.35 (FRI-V.35) and X.21 (FRI-X.21) back cards provide the FRM with interfaces to user equipment. The FRI-V.35 provides four V.35 interfaces, and the FRI-X.21 provides four X.21 interfaces. Port operating rates and composite data rates for the two interface types are the same, and most configuration tasks require the same procedures.

For a description of the FRI-V.35 back card faceplate, see Figure 2-30. For a description of the FRI-X.21 back card faceplate, see Figure 2-31.

Y-Cable Redundancy

The Y-cable redundancy kits for the FRI-X.21 and FRI-V.35 contain four extra daughter cards for specifying individual ports as either DCE or DTE. The extra daughter cards are 200-ohm versions for the FRI already installed. The higher impedance cards are necessary to maintain proper termination impedance when the two interfaces are in parallel (by way of the Y-cable).

Port Modes

You can configure the port (DCE or DTE) on an FRI back card using the position of a jumper card on the back card. See the "Preparing the Cards" section in the Cisco IGX 8400 Series Installation Guide for more information.

For more information on the FRI-V.35 back card, see the "FRI-V.35 Back Cards" section. For more information on the FRI-X.21 back card, see the "FRI-X.21 Back Card" section.

FRI-V.35 Back Cards

Both models of the FRI-V.35 have the following functions and features:

For a description of the back card faceplate, see Figure 2-30.

FRI-X.21 Back Card

The FRI-X.21 back card has the following features:

For a description of the back card faceplate, see Figure 2-31.

Configuring an FRM with FRI-V.35 Back Card

Most configuration tasks for the FRM follow standard IGX module configuration procedures. However, the FRM with FRI-V.35 back card differs in the effect that module firmware models and number of operating ports has on maximum throughputs for each port, and in the way the FRI-V.35 back card handles data clocking. For information on calculating maximum throughput for your specific usage situation, see the "Calculating Maximum Throughput for Different FRM Firmware Combinations" section. For more information on data clocking on the FRI-V.35 back card, see the "Data Clocking on the FRI-V.35 Back Card" section.

Calculating Maximum Throughput for Different FRM Firmware Combinations

The maximum throughput for the FRM using the FRI-V.35 back card depends on the number of activated ports (see Table 2-43).

Data Clocking on the FRI-V.35 Back Card

The FRI-V.35 back card supports both normal and looped clocking modes. However, the direction for clock and data flow will differ, depending on whether the FRI-V.35 back card is configured as DCE or DTE. Use the following rules to determine how clocking is conducted in different clocking modes:

See Figure 2-32 for a visual description of these two clocking modes.

Note   In looped clocking, the clock is looped by the FRI-V.35 back card, not the connected user device.

Port Testing on the FRI-V.35 Back Card (for Ports Configured DTE Only)

For ports configured for DTE, local and remote loopback port tests are also available. In test mode, the card transmits a loopback data pattern to initiate the loopback. Attached modems or NTUs might or might not recognize the loopback initiation pattern. If the modem or NTU does not recognize the loopback initiation pattern, the modem or NTU will not perform the requested loopback. The FRI waits a programmable time period (default=10 seconds) before sending the test pattern. After the test is completed, pattern transmission terminates and the circuit returns to normal operation.

Some external equipment supports loopback testing but does not recognize the test pattern (Test Mode) in the data stream. In these cases, the FRM/FRI toggles the V.35 local loopback (LLB) and the remote loopback (RLB) leads then runs the test pattern. The FRM/FRI still waits the user-specified time (default=10 seconds) before running the data test pattern.

To display test results, use the switch software tstport command.

Configuring an FRM with FRI-X.21 Back Card

FRI configuration supports one to four ports. The configuration depends on the maximum speed requirement (the card itself has a maximum composite speed).

Note   The following port speeds are supported on the FRM with FRI-X.21 back card: 56, 64, 112, 128, 168, 192, 224, 256, 320, 336, 384, 448, 512, 640, 672, 768, 896, 960, 1024, 1280, 1344, 1536, 1920, and 2048 kbps.

Data Clocking on the FRI-X.21 Back Card

Unlike the FRI-V.35, the FRI-X.21 only supports normal clock mode. Depending on the configuration of the FRI, the direction of the clock and data lines may be reversed according to the following rules (see Figure 2-33):

Port Testing on the FRI-X.21 Back Card

To test FRI-X.21 back card ports and any associated external modems, CSUs, or NTUs, set up data loopback points in the circuit path using one of the following loopbacks:

To set up a loopback test, use the switch software tstport command. You can only test one port in loopback mode at a time.

Tip Any modem being used to test FRI-X.21 back card ports must be compatible with Cisco loopback protocols. For more information on these protocols and on supported modems, see Appendix A, "System Specifications", in the Cisco IGX 8400 Series Installation Guide or refer to the Cisco WAN Switching Command Reference for protocol requirements for the switch software commands addextlp, addloclp, and addrmtlp.

The internal loopback point is established inside the FRI-X.21 back card, as shown in Figure 2-34. The FRM front card generates a test pattern, sends the test pattern out on the transmit circuitry, and detects the returned pattern on the receive circuitry.

Tip To avoid disruptions in service, conduct loopback tests during periods of low network traffic. The test takes several seconds and will momentarily interrupt traffic on the port.

Frame Relay Interface T1 and E1 Back Cards

The FR interface T1 and E1 back cards (the FRI-T1 and FRI-E1) are one-line back cards with either a T1 or E1 interface, for use with the channelized FRM front card (Models E or J). For a description of the back card faceplates, see Figure 2-35. For a definition of the faceplate LEDs, see Table 2-44.

High-Speed Data Module

Table 2-45 shows the front and back cards supported for the high-speed data module (HDM).

The HDM consists of an HDM front card and a synchronous data interface (SDI) back card. There are three different models of the SDI back card, depending on the desired interface type (see Table 2-45 and Table 2-47). Depending on the chassis type, the IGX can support up to 29 HDMs for up to 232 full-duplex data connections.

The HDM supports the following features:

HDM Front Card

The HDM front card faceplate shown in Figure 2-36 has both LEDs and control buttons to assist with loopback control and signal monitoring tasks. See Table 2-46 for more information about the HDM front card faceplate LEDs and the "HDM Control Buttons" section for more information on HDM front card faceplate control buttons.

HDM Control Buttons

The HDM front card faceplate has two control buttons used to assist monitoring tasks (see Figure 2-36). The scroll control button allows you to select one of the four data ports on the SDI back card for monitoring. Information displayed by the front card faceplate LEDs applies to the selected back card data port only.

For example, if you use the scroll control button to select data port 1 (which has a local loopback present), the port 1 and LL LEDs will come on. If you use the scroll control button to select data port 4 (which has a transmit data signal), the port 4 and TXD LEDs will come on.

The loopback control button allows you to select one of three different loopback states (no loopback, local loopback, or remote loopback) for the selected port. For example, if port 1 is lit and you use the loopback control button to specify local loopback, the port under test LED and the LL LED will become lit to indicate that data port 1 now has a local loopback present.

SDI Back Card

The SDI back card provides data connections for the HDM front card. Each SDI back card model has four connectors with the connector type depending on the interface supported by the back card (see Table 2-47). Each connector provides the physical interface for one data ports. These data ports correspond to the Port LEDs of the same number on the HDM front card faceplate (see Figure 2-36). Each port is separately configurable.

SDI Clocking

You can use three different clocking modes on the SDI back card for clocking transmit data and receive data. Since the SDI back card can operate as either a DCE or a DTE, six different clocking combinations are possible (see Figure 2-37 and Figure 2-38 ).

Low-Speed Data Module

Table 2-48 shows the front and back cards supported for the low-speed data module (LDM).

The LDM consists of an LDM front card and a low-speed data interface (LDI) back card. There are two LDI variants, depending on the desired number of ports (see Table 2-50).

LDM Front Card

The LDM card is a low-speed data module for use on EIA/TIA-232 ports with data rates up to 56 bps (4-port back card) or 19.2 kbps (8-port back card), where the higher speeds of an HDM are unnecessary. The low-speed data module (LDM) front card supports up to eight synchronous data ports. Each port can be independently configured for DTE or DCE mode, baud rate, and other parameters.

The LDM front card has the following features:

The LDM front card can reside in any empty front slot and requires an LDI back card.

The faceplate of the LDM front card has LEDs and buttons for loopback control and signal monitoring. Figure 2-39 shows and Table 2-49 lists these LEDs and buttons. The buttons are for loopback testing and scrolling through the data ports to obtain a snapshot of selected port conditions (indicated by port, port under test, loopback, and communication line status lights).

Redundancy for LDM data card types is available through a second front and back card set and a Y-cable connection on each port to the customer data equipment. For more information on Y-cable redundancy, see the "Card Redundancy" section.

The 4- and 8-port LDM supports only a subset of the full EIA/TIA-232C/D control leads. The LDM supports only nonisochronous DCE normal and DTE looped clocking modes, transmission of 3 EIA lead states (non-interleaved), and baud rates of up to 19.2 kbps on the 8-port version and 56 kbps on the 4-port version. Split clock mode is not supported.

Low-Speed Data Interface Back Card

The low-speed data interface (LDI) back card is a low-speed data interface back card that operates in conjunction with an LDM front card. The LDI back card provides the physical and electrical connection interface between the user low-speed data circuit and the LDM data PAD. There are two LDI models—one 4-port and one 8-port (see Table 2-50).

The LDI back card has the following features:

The LDI back card can operate either as a DCE or DTE. Selection is made by using a Cisco DTE or DCE adapter cable between the port connector and the cable from the user device. This cable is terminated with a standard DB-25 on the customer end. Each port is configured separately.

Three EIA control leads are brought out to the rear connectors (see Table 2-51).

You can use remote loopback (RL) to enable a far-end modem loopback. Local loopback (LL) is not provided as an output on the LDI back card.

The LDI back card supports two clocking modes: normal and looped (see Figure 2-40). The normal mode is used when the LDI port is configured as a DCE. Looped clock is only used when the LDI port is configured as a DTE. The user device must take the external transmit clock and loop it back to the RxC for clocking in the receive data. In both cases, the LDI is the source of clock timing.

Universal Router Module

Table 2-52 shows the front and back cards supported for the universal router module (URM).

The URM delivers high-density voice interfaces, Fast Ethernet connectivity and ATM switching through a combination of Cisco IOS software and switch software functionality.

Note   Refer to the Compatibility Matrix  for Cisco IOS software, switch software, and firmware compatibility requirements.

The URM consists of a logically-partitioned front card connected to a universal router interface (URI) back card. The front card contains an embedded UXM-E running an Administration firmware image, and an embedded router (based on the Cisco 3660 router) running a Cisco IOS image. The embedded UXM-E and the embedded router connect through a logical internal ATM interface, with capability equivalent to an OC3 ATM port.

Note   Switch software treats this interface as an OC3 ATM port, and this interface is the only port on the embedded UXM-E that is visible to switch software.

Unlike the Cisco 3660 router, which has one slot for the motherboard and six slots for network modules, the embedded router has three virtual slots with built-in interfaces (see Table 2-53 and Figure 2-41).

Because the URM front card contains both an embedded UXM-E and an embedded Cisco router, the front card runs two separate software images with two different download procedures. For the embedded UXM-E, the administration firmware image is downloaded and saved to the embedded UXM-E Flash memory through switch software commands (see Cisco WAN Switching Command Reference ).

The embedded router runs Cisco IOS software. You can download and save the Cisco IOS image using standard Cisco IOS procedures as outlined in any documentation supporting the Cisco IOS image being used on the node.

The embedded UXM-E hardware is based on the UXM-E card for the Cisco IGX series and features 16 MB asynchronous DRAM, 8 MB Flash memory, and 8 KB BRAM. The embedded router hardware is based on the Cisco 3660 modular-access router and features 8 MB boot Flash SIMM, 32 MB Cisco IOS Flash SIMM, and 128 KB NVRAM.

URM Front Card

To locate different LEDs on the URM front card faceplate, see Figure 2-42. Refer to Table 2-55 for a description of the LED function.

Embedded UXM-E Features

Embedded Router Features

URI-2FE2V Back Cards

The BC-URI-2FE2VT1 and BC-URI-2FE2VE1 back cards provide T1 or E1 digital voice interfaces for the URM. BC-URI-2FE2V features include:

See Figure 2-43 to locate LEDs and interfaces on the URM back card. See Table 2-56 for a description of the physical ports on the back card, Table 2-57 for a description of the LEDs on the URI back card, and Table 2-58 for a description of the LEDs located on the installed VWIC.