Table of Contents

Overview: BXM Cards
BXM Capabilities

ATM Layer
Service Types

Minimum SCR and PCR
Virtual Interfaces
Virtual Ports

Enhanced BXM
BXM Front Card Indicators
BXM Backcard Connectors
Y-Cabling of SMF-622 Series Backcards
Automatic Protection Switching Redundancy
BXM Functional Description

Operation in Port (UNI) Mode
Operation in Trunk Mode
Detailed Description of Port (UNI) and Trunk Modes

DRSIU
SONET/SDH UNI (SUNI)
DeMux/Mux
RCMP
SABRE
Ingress and Egress Queue Engines
SIMBA
ACP Subsystem Processor

Fault Management and Statistics

Port (UNI) Mode
Trunk Mode

Technical Specifications

Physical Layer
General Information

BXM Card Sets: T3/E3, 155, and 622

This chapter describes the physical BXM card sets, their major circuit functionality, and technical specifications:

• Overview: BXM Cards

• BXM Capabilities

• Enhanced BXM

• BXM Front Card Indicators

• BXM Backcard Connectors

• Automatic Protection Switching Redundancy

• BXM Functional Description

• Fault Management and Statistics

• Technical Specifications

The BXM set includes these cards:

• BXM T3/E3

• BXM-155

• BXM-622

The BXM cards may be upgraded to Enhanced BXM. Enhanced BXM cards improve upon the current BXM cards by delivering even more cost-effective ATM switching and traffic management. The Enhanced BXM cards support up to 12 ATM interfaces per card at speeds from T3/E3 to OC-12/STM-4.

The BXM cards may be configured for either:

• Trunk mode
  In Trunk mode, BXM cards provide BPX network interfaces.

• Service mode.
  In service (port UNI) mode, BXM cards provide service access to customer premise equipment.

The BXM cards support label switching. For information on Label Switching, refer to The MPLS Controller Software Configuration Guide.

Partitions for the BXM can be allocated between either:

• SVCs and PVCs, or

• Label switching virtual circuits (LVCs) and PVCs.

The BXM card supports dynamic resource partitioning to support the conversion of PVCs to soft permanent virtual circuits (SPVCs). This feature is described in Cisco SES PNNI Controller Software Configuration Guide.

Overview: BXM Cards

A BXM card set, using Application Specific Integrated Circuit (ASIC) technology, provides high speed ATM connectivity, flexibility, and scalability. The card set is comprised of a front card that provides the processing, management, and switching of ATM traffic and a back card that provides the physical interface for the card set.

An example of a BPX switch network provisioned with BXM-622 cards is shown in Figure 5-1.

The BXM card group includes:

• BXM-T3/E3
  Available in 8 or 12 port versions with T3/E3 interfaces.

• BXM-155
  Available in 4 or 8 port versions with OC-3/STM-1 interfaces.

• BXM-622
  Available in 1 or 2 port versions with OC-12/STM-4 interfaces.

For additional information on ATM Connections, refer to Chapter 21, Configuring ATM Connections.

The enhanced BXM-E card (version DX or EX) supports a higher connection density (32K) than either the legacy BXM or regular BXM-E cards. Both DX and EX versions have the same connection density, providing you with the ability to upgrade networks with the high connection density BXM-Es on trunk side, port side, or a combination of trunks and ports. You can smoothly upgrade BXM cards to BXM-E capabilities; see "Upgrade BXM to BXM-E Cards" in "Upgrade Information"

Any of the 12 general purpose slots can be used for the BXM cards. The same backcards are used whether the BXM ports are configured as trunks or lines. Table 5-1 and Table 5-2 list the available front and back card options for the BXM-T3/E3, BXM-155, and BXM-622.

BXM Capabilities

Here are some of the major features of the BXM cards:

• Virtual Path (VP) as well as Virtual Circuit (VC) connections.

• Support both PVC and SVC connections.

• Connections supported per card:

  • 16,000 to 32,000 connections per card depending on configuration.

• BXM, T3/E3 ATM with 8 or 12 ports, either T3 at a 44.736 Mbps rate, or E3 at a 34.368 rate.

• BXM, OC-3/STM-1 ATM: four or eight ports, with each port operating at a 155.52 Mbps rate, 353,208 cells per second (full OC-3 rate).

• BXM, OC-12/STM-4 ATM: one or two ports, with each port operating at a 622.08 Mbps rate, 1,412,830 cells per second (full OC-12 rate).

• Selective Cell Discard.

• Up to 228,300 cell ingress (receive) buffers depending on card configuration.

• Up to 228,300 cell egress (transmit) buffers depending on card configuration.

• CBR, VBR, ABR, and UBR service classes.

• For MFJ firmware and above, channel statistics level 0 is no longer supported for BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-12, BXM-T3-8, BXM-E3-8, and BXM-E3-12 models. However, it is still supported for all the other models (BXM-155-8DX, BXM-155-8D, BXM-155-4DX, BXM-155-4D, BXM-622-2DX, BXM-622-2D, BXM-622-DX, BXM-T3-12EX, BXM-T3-12E, BXM-T3-8E, BXM-E3-12EX, BXM-E3-12E, and BXM-E3-8E).

• ATM cell structure and format per ATM Forum UNI v3.1.

• Loopback support.

• 1:1 card redundancy using Y-cable configuration.

• A BXM card may be configured for either network or port (access) operation.

ATM Layer

• UNI port option conforming to ATM Forum UNI v3.1 specification.

• ATM cell structure and format supported per ATM UNI v3.1 and ITU I.361.

• Header Error Correction (HEC) field calculation and processing supported per ITU I.432.

• Usage Parameter Control using single and dual leaky bucket algorithm, as applicable, to control admission to the network per ATM Forum 4.0 Traffic Management.

• Provides up to 16 CoS's with the following configurable parameters:

  • Minimum service rate

  • Maximum queue depth

  • Frame discard enable

  • Cell Loss Priority (CLP) High and Low thresholds

  • Service priority level

  • Explicit Forward Congestion Indication (EFCI) threshold

• Per VC Queuing

• Support for UBR CoS with Early Packet Discard

• Failure alarm monitoring per T1.64b

• ATM layer OAM functionality

• Congestion control mechanisms

  • ABR with Virtual Source Virtual Destination (VSVD)

  • ABR with Explicit Rate (ER) stamping/EFCI tagging

  • ABR with ForeSight

• Self-test and diagnostic facility.

Service Types

The BXM cards support the full range of ATM service types per ATM Forum TM 4.0.

CBR Service:

• Usage Parameter Control (UPC) and Admission Control

• UPC: Ingress rate monitoring and discarding per I.371 for:

  • Peak Cell Rate (PCR)

  • Cell Transfer Delay Variation (CTDV)

VBR Service:

• Usage Parameter Control (UPC) and Admission Control

• UPC: Ingress rate monitoring and cell tagging per ITU-T I.371 for:

  • Sustained Cell Rate (SCR)

  • Peak Cell Rate (PCR)

  • Burst Tolerance (BT)

• CLP tagging, enabled or disabled on a per VC basis at the Ingress side

ABR Service:

• Based on Virtual Source Virtual Destination (VSVD) per ATM Forum TM4.0

• VSVD

  • VSVDs provide Resource Management (RM) cell generation and termination to support congestion control loops

  • A virtual connection queue (VCQ) is assigned to a VC in the ingress direction

  • VCQ configurable parameters

  • CLP Hi and Lo thresholds

  Maximum queue depth
  

  Reserved queue depth
  

  Congestion threshold
  

• ABR congestion control

Based on Explicit rate stamping/EFCI cell tagging and ingress rate monitoring per ITU-T I.371

• ABR with Virtual Source Virtual Destination (VSVD)

• ABR with Explicit Rate (ER) stamping/EFCI tagging

• ABR with ForeSight

UBR Service:

• Based on UPC and admission control including EPD

• Based on Explicit Rate Marking/EFCI cell tagging and ingress rate monitoring per ITU-T I.371

Minimum SCR and PCR

The minimum Sustainable Cell Rate (SCR) and Peak Cell Rate (PCR) of a connection supported by the BXM and UXM cards, including enhanced modes, was 50 cells per second (cps) or 19.2 Kbps. These values were set to maintain a policing accuracy with 1% when policing is performed on a BXM or UXM card. Because of this limitation, it was impossible to offer and differentiate connection services on a UXM or BXM at speeds less than 19.2 Kbps (50 cps).

In Release 9.3.0, the switch software supports connections with policing enabled and with SCR and PCR values as low as 12 cps on the BPX switch, with certain card limitations.

Use the dspcd command to determine if this feature is supported on a given slot.

Use the addcon command to set the minimum SCR and PCR values.

If these values are less than the minimum values supported on a given card, the command line interface will not allow you to set them until you have disabled policing. (A prompt will let you know about this limitation.)

Please refer to Table 5-1 for a list of cards that are supported by this feature and their performance specifications.

Policing must be disabled to support 6 cps and above for all BXM/UXM interface types.

Virtual Interfaces

• VPI/VCI used to identify virtual connection

• Support for up to 32 virtual interfaces per card, each with 16 CoS queues

• Virtual Interface parameters

  • Physical port (trunk or access)

  • Peak Service Rate (PSR)

  • Minimum Service Rate (MSR)

  • Maximum resource allocation

Virtual Ports

Virtual ports support hierarchical egress traffic shaping at more than one level on a single UNI port, combining virtual path traffic shaping and associated virtual connections. This feature allows one or more Virtual Ports per Physical Port interface.

A maximum of 31 virtual ports are available per BXM card. Each port supports all autoroute traffic types currently supported by physical ports. Up to 255 virtual ports are supported per BPX node (with BCC-4-128) and 144 ports (with BCC-3-64).

Enhanced BXM

The Enhanced BXM cards improve the current BXM cards by delivering even more cost-effective ATM switching and traffic management. The Enhanced BXM cards come in EX and DX versions, both including these key feature enhancements:

• Support a greater cell storage capacity and a greater number of connections

  • The cell memory has been increased on the Enhanced BXM cards to support even greater cell buffering to maximize bandwidth efficiency and cell/frame throughput in wide area networks.

  • Enhanced BXM cards support up to 12 ATM interfaces per card at speeds from T3/E3 to OC-12/STM-4.

  • The ACP processor memory is quadrupled
    ACP Processor memory is 64 Mbyte and the flash memory is doubled to 4 Mbyte on all Enhanced BXM cards to allow more headroom for feature addition and enhancement in the future.

With a more powerful processor and more VC configuration memory in ATM cell switching subsystem, the EX and DX versions of Enhanced BXM cards meet the ever increasing demand for greater number of connections per interface. For each PVC terminating on the card, Enhanced BXM supports a full range of stats for usage-based billing at cell and frame levels, cell policing, EFCI marking, ABR RM cells, and OAM cells. Supporting a greater number of connections per interface translates to supporting a greater user density more cost effectively.

This table provides detailed information about the number of connections and cell buffer size supported on different types of Enhanced BXM card:

• Support an improved traffic shaping granularity for each virtual interface (VI) to allow any desired shaping rate.

On regular BXM cards, the VI traffic shaping rate is limited to OC-12/n, where n is an integer. On the Enhanced BXM cards, the VI traffic shaping rate can be any desired shaping rate with a precision of 9-bit mantissa and 4-bit exponent.

• Provide ABR support for connections with non-AAL5 traffic

On the current BXM cards, the ABR support is limited to connections with AAL5 traffic. These connections allow early packet discard to be applied to avoid queue congestion and thus maintain RM cell flow. The Enhanced BXM cards extend the ABR support to connections with non-AAL5 traffic also. The Enhanced BXM cards minimize the problem of RM cell discard when RM cells are injected into a congested VC by reserving room for 8 RM cells even when the VC begins to drop data cells. The RM cell reserve can be globally configured for VSVD and non-VSVD connections.

• Support unidirectional ForeSight connections

On the current BXM cards, the ForeSight ABR (Cisco's pre-standard ABR implementation) support is limited to bi-directional connections only. The current BXM cards also support ATM Forum standard ABR for both bi-directional and unidirectional connections. The Enhanced BXM cards will extend the ForeSight ABR support to include unidirectional connections also.

• Support interworking of the port ABR segment controlled with ATM Forum ABR algorithm and the network ABR segment controlled with ForeSight ABR algorithm.

The Enhanced BXM cards will provide coupling between the port ABR segment with ATM Forum ABR algorithm and the network ABR segment with ForeSight ABR algorithm.

The Enhanced BXM cards include features that can be enabled by future firmware and switch software:

• Separate frame discard CLP0 and frame discard CLP1 thresholds for each Class-of-Service (CoS) queue

The Enhanced BXM cards support separate frame discard CLP0 and frame discard CLP1 thresholds for each CoS queue. This feature enables preferential treatment for conforming traffic within CIR (frames with CLP=1 start-of-frame cell) compared to non-conforming traffic (frames with CLP=0 start-of-frame cell) when applying early packet discard (EPD).

• Merging of multiple frame-based VCs onto a single frame-based VC with future software upgrade

The Enhanced BXM card hardware will support VC merge to facilitate label switching with simple software upgrade. With VC merge, the Enhanced BXM cards allow the BPX to aggregate multiple incoming frame based VCs with the same destination address into a single outgoing frame-based VC. Cells from different VCIs going to the same destination are transmitted to the same outgoing VC using multipoint-to-point connections.

Where VC merge occurs, several incoming labels indicated by VCIs are mapped to one single outgoing label. This sharing of labels reduces the total number of virtual circuits required for label switching. Without VC merge, each source-destination prefix pair consumes one label VC on each interface along the path. VC merge reduces the label space shortage by sharing labels for different flows with the same destination.

BXM Front Card Indicators

The BXM front panel has a three-section, multicolored "card" LED to indicate the card status. The card status LED is color-coded as indicated in Table 5-5. A three-section multi-colored "port" LED indicates the status of the ports.

A two-port BXM-622 is shown in Figure 5-2. An 8-port BXM-155 front card is shown in Figure 5-3. A 12-port BXM-T3/E3 is shown in Figure 5-4.

Types of failures are indicated by various combinations of the card status indicators as described in Table 5-6.

BXM Backcard Connectors

The BXM backcards connect to the BXM front cards through the StrataBus midplane.

The BXM-622 is available in one or two port versions in either a single-mode fiber intermediate range (SMF) or a single-mode fiber long range (SMFLR) backcard. Connector information is listed in Table 5-7. A 2-port SMF card is shown in Figure 5-5.

The BXM-155 is available in four or eight port versions in a choice of multimode fiber (MMF), single-mode fiber intermediate range (SMF), or single-mode fiber long range (SMFLR) backcards. Connector information is listed in Table 5-8 and an 8-port SMF card is shown in Figure 5-6.

The BXM-STM1-4 is available in a four-port version that provides an electrical interface where the longer line lengths provided by the BXM optical backcards are not required. Connector information is listed in Table 5-9 and the backcard is shown in Figure 5-7.

The BXM-T3/E3 is available in eight or twelve port versions. Connector information is listed in Table 5-10 and a 12-port T3/E3 card is shown in Figure 5-8.

The two backcards are connected together by a BPX Redundant Backplane which mates with the BPX Midplane. The connectors are the same as those for the standard backcards. An APS backcard is shown in (Figure 5-10, and the BPX Redundant Backplane is shown in (Figure 5-11).

Y-Cabling of SMF-622 Series Backcards

You can Y-cable the SMF-622 series backcards for redundancy by using the Y-Cable splitter shown in Figure 5-9. To configure the cards for Y-Cable redundancy, use the addyred command.

Automatic Protection Switching Redundancy

Automatic Protection Switching (APS) provides a standards-based line-redundancy for BXM OC-3 and OC-12 cards. The BXM OC-3 and BXM OC-12 cards support the SONET APS 1+1 and APS 1:1 standards for line redundancy. Line redundancy is provided by switching from the working line to the protection line.

The APS protocols supported by the BXM are listed in Table 5-11:

A backcard is shown in (Figure 5-10). The APS Redundant Frame Assembly is shown in (Figure 5-11). Two redundant backcards are connected together by the APS Redundant Frame Assembly. The APS Redundant Frame Assembly with associated APS redundant backcards is inserted as a unit in two appropriate backcard slots.

Refer to Chapter 26, Configuring SONET Automatic Protection System, for additional information.

BXM Functional Description

This functional description provides an overview of BXM operation.

Operation in Port (UNI) Mode

This section is an overview of operation when the BXM card's ports are configured in port (access) mode for connection to customer equipment.

The ingress flow of ATM cells from CPE into a BXM port when the card is configured for port (access) operation is shown in Figure 5-12.

ATM cells from the customer premise equipment are:

• Processed at the physical interface level by the SUNI (OC-3/OC-12) or Mux/Demux (T3/E3),

• Served out via the BPX Backplane to the BPX crosspoint switch in an order of priority based on their connection type

• Policed per individual VC by the RCMP and

• Routed to applicable ingress queues

For ABR cells, additional functions are performed by the SABRE ABR connection controller, including: VSVD, Foresight, and virtual connection queueing.

The egress flow of ATM cells out of the BXM when the card is configured for port (access) operation is shown in Figure 5-13.

ATM cells are:

1. Routed to the BXM-622 via the BPX Backplane/Stratabus from the BPX crosspoint switch,

2. Applied to the DRSIU,

3. To an egress queue per class of service, and

4. Served out to the SUNI (OC-3/OC-12) or Mux/Demux (T3/E3)

5. Which processes the ATM cells into frames,

6. Processes the cells from the ATM layer to the physical, and

7. On out to customer premise equipment connected to the ports on the BXM backcard.

For ABR cells, additional functions are performed by the SABRE ABR connection controller, including: VSVD, Foresight, and virtual connection queueing.

Operation in Trunk Mode

This section is an overview of the operation of the BXM when the card is configured in the trunk mode for connection to another node or network.

The ingress flow of ATM cells into the BXM when the card is configured for trunk operation is shown in Figure 5-14.

On ingress, ATM cells from a node or network are:

1. Processed at the physical interface level by the SUNI (OC-3/OC-12) or Demux/Mux (T3/E3)

2. Routed to applicable ingress slot queues

3. Served out to the BPX crosspoint switch via the BPX Backplane.

The egress flow of ATM cells out of the BXM when the card is configured for trunk operation is shown in Figure 5-15.

In egress, ATM cells are:

1. Routed to the BXM from the BPX crosspoint switch,

2. Applied to the DRSIU,

3. To an egress queue per class of service, and

4. Served out to the SUNI (OC-3/OC-12) or Demux/Mux (T3/E3).

5. The SUNI or Demux/Mux, as applicable, processes the ATM cells into frames,

6. Processing the cells from the ATM layer to the physical and

7. On out to the backcard trunk interface connecting to another node or network.

Detailed Description of Port (UNI) and Trunk Modes

This section is a summary of the principal functions performed by the major functional circuits of the BXM.

DRSIU

The DRSIU provides a total egress capacity from the BPX switch fabric of 1.6 Gbps.

SONET/SDH UNI (SUNI)

The SUNI ASIC implements the BXM physical processing for OC-3 and OC-12 interfaces. The SUNI provides SONET/SDH header processing, framing, ATM layer mapping and processing functions for OC-12/STM-4 (622.08 Mbps) or OC-3/STM1 (155.52 Mbps).

For ingress traffic, the BXM physical interface:

1. Receives incoming SONET/SDH frames,

2. Extracts ATM cell payloads, and

3. Processes section, line, and path overhead.

For egress traffic ATM cells are processed into SONET/SDH frames.

Alarms and statistics are collected at each level: section, line, and path.

DeMux/Mux

The Demux/Mux and associated circuits implement the BXM physical layer processing for T3/E3 interfaces, processing functions for T3 at a 44.736 Mbps rate or E3 at a 34.368 rate. It provides:

• header processing

• framing

• ATM layer mapping

RCMP

Usage Parameter Control (UPC) is provided by the RCMP. Each arriving ATM cell header is processed and identified on a per VC basis. The policing function utilizes a leaky bucket algorithm.

In addition to UPC and traffic policing, the RCMP provides route monitoring and also terminates OAM flows to provide performance monitoring on an end-to-end per VC/VP basis.

Traffic policing and UPC functionality is in accordance with the GCRA as specified by ATM Forum's UNI 3.1 using dual leaky buckets.

• Leaky Bucket 1 utilizes:

  • Peak Cell Rate (PCR)

  • Cell Delay Variation Tolerance: CDVT

• Leaky Bucket 2 utilizes:

  • Sustainable Cell Rate (SCR)

  • Maximum Burst Size (MBS)

In addition, two selective cell discard thresholds are supported for all queues for discard of CLP=1 cells should congestion occur.

SABRE

The Scheduling and ABR Engine (SABRE) includes both VSVD and Foresight dynamic traffic transfer rate control and other functions:

• ATM Forum Traffic Management 4.0 compliant ABR Virtual Source/Virtual Destination (VSVD).

• Terminates ABR flows for VSVD and Foresight control loops.

• Performs explicit rate (ER) and EFCI tagging if enabled.

• Supports Foresight congestion control and manages the designated service classes on a per VC basis with OAM processing.

• Supports OAM flows for internal loopback diagnostic self-tests and performance monitoring.

• Provides service queue decisions to the Ingress and Egress Queue Engines for per VC queues for ABR VCs.

Ingress and Egress Queue Engines

The overall function of the queue engines is to manage the bandwidth of trunks or ports (UNI) via management of the ingress and egress queues.

In addition to the ABR VS queues, the ingress queues include 15 slot servers, one for each of 14 possible BPX destination slots, plus 1 for multicast operation. Each of the 15 slot servers contains 16 Qbins, supporting 16 classes of service per slot server.

In addition to the ABR VS queues, the egress queues include 32 Virtual Interfaces (VIs). Each of the 32 VIs supports 16 qbins.

SIMBA

This serial interface and multicast buffer ASIC provides:

• ATM cell header translation.

• Directs ATM cells to the Egress Queue Engine with a 2 x OC-12c throughput capacity.

• Implements the multicast function in the egress direction, providing up to 4000 multicast connections.

• Translates standard OAM flows and Foresight cells.

• Optimizes backplane bandwidth by means of a polling mechanism.

ACP Subsystem Processor

The ACP performs these localized functions:

• Initializes BXM at power up

• Manages local connection databases

• Collects card, port, and connection statistics

• Manages OAM operation

• Controls alarm indicators (active, standby, fail)

All basic configuration data on the card is copied to the battery backup memory (BRAM) on the card so that in the event of a power outage, the card will retain its main configuration.

Fault Management and Statistics

Port (UNI) Mode

Compliant to Bellcore GR-253-CORE

Alarms:

• Loss Of Signal (LOS)

• Loss Of Pointer (LOP)

• Loss Of Frame (LOF)

• Loss Of Cell delineation (LOC)

• Alarm Indication Signal (AIS)

• Remote Defect Indication (RDI)

• Alarm Integration Up/down Count

Performance Monitoring:

• Performance monitoring provided for Line, Section, and Path

• Bit Interleaved Parity (BIP) error detection

• Far End Block Error (FEBE) count

• Unavailable Seconds (UAS)

• Errored Seconds (ES)

• Severely Errored Seconds (SES)

• Header Error Checksum (HCS) monitoring

Statistics:

• ATM statistics collected on a per VC basis

  • Two modes of statistics collection:

  Basic: collection of 4 statistics per VC per direction
  

  Enhanced: collection of 12 statistics per VC per direction
  

OAM

• Loopback support

• Generation and detection of AIS and RDI OAM cells

• Termination and processing of OAM cells

Trunk Mode

Compliant to Bellcore GR-253-CORE

Alarms:

• Loss Of Signal (LOS)

• Loss Of Pointer (LOP)

• Loss Of Frame (LOF)

• Loss Of Cell delineation (LOC)

• Alarm Indication Signal (AIS)

• Remote Defect Indication (RDI)

• Alarm Integration Up/down Count

Performance Monitoring:

• Performance monitoring provided for Line, Section and Path

• Bit Interleaved Parity (BIP) error detection

• Far End Block Error (FEBE) count

• Unavailable Seconds (UAS)

• Errored Seconds (ES)

• Severely Errored Seconds (SES)

• Header Error Checksum (HCS) monitoring

Statistics:

Process Monitoring for ATM Header Cell Processing

• Cells discarded due to Header Errors (LCN mismatch)

Miscellaneous ATM Layer Statistics

• Number of cell arrivals from port

• Number of cell arrivals with CLP = 1

• Number of cells transmitted to port

• Number of cells transmitted with CLP = 1

Technical Specifications

Physical Layer

• Trunk or port (access) interface mode.

• Compliant to SONET standards.

  • *Bellcore GR-253-CORE, TR-TSY-000020

  • *ANSI T1.105, T1E1.2/93-020RA

• Compliant to SDH standards.

  • *ITU-T G.707, G.708 and G.709

  • *ITU-T G.957, G.958

• 1:1 BXM redundancy supported using `Y' redundancy.

• Fiber optic interface characteristics are listed in Table 5-12 and Table 5-13.

General Information

• Card dimensions: 19"(H) x 1.1"(W) x 27"(D)

• Weight: 6 lb (2.7kg)

• Power -48 V DC at 85 W

• EMI/ESD: FCC Part 15, Bellcore GR1089-CORE

• IEC 801-2, EN55022

• Safety: EN 60950, UL 1950

• Bellcore NEBS: Level 3 compliant

• Optical Safety:

  • Intermediate Reach IEC 825-1 (Class 1)

  • Long Reach IEC 825-1 (Class 36)

Posted: Fri Jul 27 15:40:17 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.