Circuit Emulation over IP Network Modules

CISCO/라우터 & 라우팅 시스템 2007/05/04 12:10
CIRCUIT EMULATION OVER IP NETWORK MODULES

Figure 1. Four-Port T1/E1 Circuit Emulation Network Module (NM-CEM-4TE1)

Figure 2. Four-Port Serial Circuit Emulation Network Module (NM-CEM-4SER)

The Circuit Emulation over IP (CEoIP) network modules (product numbers NM-CEM-4TE1 and NM-CEM-4SER) for the Cisco® 2600XM, 2691, 2811, 2821, 2851, 3660, 3700 and 3800 routers provide a new CEoIP service offering. These network modules provide bit-transparent data transport that is completely protocol-independent.
For the first time, this allows network administrators to take advantage of their existing IP network to provide leased-line emulation services, or to carry data streams or protocols that do not meet the format requirements of other multiservice platform interfaces.

APPLICATIONS

These two new network modules are the first Cisco router interfaces designed to meet the emerging standards for CEoIP.
All previous Cisco router interfaces require that data be presented in the form of:

• Native IP frames

• Frame Relay frames

• High-Level Data Link Control (HDLC) frames

• ATM cells

• Channelized pulse-code-modulation (PCM) voice

• Asynchronous ("start/stop") data

These new network modules do not assume that data has any predefined format or structure. They simply regard the data as an arbitrary bit stream. All data bits are simply transported to a defined destination encapsulated in IP packets.
This transparency, for the first time, allows an IP network to carry the variety of data applications and protocols that do not meet the requirements of other router interfaces. Such applications, shown in Figure 3, might include:

• Pre-encrypted data for government, defense, or other high-security applications

• Proprietary synchronous or asynchronous data protocols used in transportation, utilities, and other industries

• Leased-line emulation service offerings in metropolitan (metro) ethernet or wide-area network service provider environments

Figure 3. CEoIP Application Examples

FEATURES AT A GLANCE

• Emerging standards-based CEoIP based on Vainshtein draft with enhancements

• Configurable using Cisco IOS® software

• Four T1/E1 ports per T1/E1 network module

• Four synchronous serial ports per serial network module

• Interworking between the T1/E1 and serial network modules

• Bit-transparent data transport

• Protocol-independent data transport

• IP transport using Real-Time Transport Protocol (RTP) and UserDatagram Protocol (UDP) protocol stack

• IP quality of Service (QoS) using differentiated services code point (DSCP) or type of service (ToS) and IP Precedence

• Configurable payload size

• Optional payload compression

• Optional data protection

• Adaptive clock synthesis

• Configurable egress de-jitter buffers up to 500 milliseconds

• Configurable idle pattern

• Online insertion and removal (OIR) supported on Cisco 3660 and Cisco 3745 platforms

• Overall network module status LEDs

• Per-port status LEDs

Additional Features of the NM-CEM-4TE1

• Unframed (unstructured) T1/E1 transport

• N x 64 kbps and N x 56 kbps framed T1 transport

• N x 64 kbps framed E1 transport

• Grooming of up to 24 (T1) or 31 (E1) separate data streams, each able to terminate on a separate network destination

• Optional channel associated signaling (CAS) transport

• Configurable clock source for each port

• T1/E1 line diagnostic loopbacks (local line, local payload, and network payload)

Additional Features of the NM-CEM-4SER

• Serial data rates from 200 bps to 2048 kbps

• Optional serial control lead transport

• Optional extended serial control lead support

• Configurable serial control lead sampling

• Serial control lead programming

• Optional data strobe configuration

• Configurable clock mode for each port

• Configurable clock source for each port

• Serial port loopbacks (local and network)

• Asynchronous data support with over-sampling

• Support of RFC 1406 MIB for T1/E1 performance monitoring

FEATURE DETAILS

Protocol-Independent Data Transport

These network modules provide completely bit-transparent, bidirectional, point-to-point data transport. Every bit presented to an ingress port is transported unchanged to the corresponding egress port by encapsulating the data bits into an IP packet for transport across an IP network. The data ports do not care about the structure or content of the data stream. Consequently, these network modules are ideally suited to transport data streams that are not suited to be carried using other platform interfaces. Such data streams might include:

• Leased-line emulation services

• Encrypted data

• Data protocols that cannot easily be migrated to native IP, ATM, Frame Relay, HDLC, etc.

Data Integrity

Because these network modules do not consider the content of any circuit emulation data stream, it is important to engineer the transport network in such a way as to minimize the risk of losing any data packets. To that end, these network modules support a variety of QoS mechanisms, including IP DSCP, IP ToS, and IP Precedence.
To ensure that a data stream is delivered, without gaps, to the destination customer premises equipment (CPE), data packets are held in a de-jitter buffer at the destination port to eliminate any delay variation (that is, jitter) experienced by successive packets traveling through the network. The
de-jitter buffer is user-configurable up to 500 milliseconds (± 250 milliseconds).
For a measure of added safety, the network modules support a data protection feature based on RFC 2198. This feature guarantees that no data is lost in the event of any nonconsecutive packet(s) being dropped (or excessively delayed) in the IP network.

Flexibility in Delay vs. Overhead

Each packet created by these network modules carries a 44-byte header that includes:

• A 20-byte IP header

• An 8-byte UDP header

• A 12-byte RTP header

• A 4-byte circuit emulation header

However, these network modules support a wide variety of payload sizes from 1 byte (for very low-speed data streams) to 1312 bytes. This provides the user the ability to control the overall efficiency as well as the end-to-end delay of the system by controlling the packetizing delay. Naturally, large packets introduce more packetizing delay but generate fewer packets per second with correspondingly lower packet overhead.

Payload Compression and cRTP to Increase Efficiency

In networks where bandwidth optimization is of premium importance, these network modules support both payload and header compression, independently of each other. Both compression algorithms are optional.
The payload compression is implemented on the network modules using the Lempel-Zif-Stac (LZS) algorithm. Naturally, the overall compression efficiency is a function of the data in the transmitted data stream.
The header compression is implemented on the host platform using compressed RTP (cRTP) to compress the 44-byte header to 6 or 8bytes.

Clocking Flexibility

In order to achieve bit-transparent circuit emulation without bit errors, it is imperative that both endpoints of the circuit use the same bit clock frequency.

Figure 4. Synchronization with a Common Clock

One way to accomplish this is to externally synchronize both end devices with a common clock source, as shown in Figure 4.
An alternative is to use an "adaptive clock" at the slave end of the circuit, as shown if Figure 5.

Figure 5. Synchronization With Adaptive Clock

The "adaptive clock" is a locally synthesized clock frequency that is tuned to match the master clock (applied to either the source CPE or the source router). These network modules provide the option to generate an adaptive clock based on the average amount of data in the egress de-jitter buffer of the data stream.

FEATURES OF THE NM-CEM-4TE1

The same hardware supports either four T1 ports or four E1 ports.

Unframed vs. Framed Mode

Each T1/E1 port can be independently configured to operate either in unframed or framed mode.
In unframed mode, a T1 or E1 port encapsulates the entire T1 stream (1544000 bits/second) or E1 stream (2048000 bits/second) for transport across the IP network.
In framed mode, a T1/E1 port supports both unchannelized and channelized operation. In unchannelized operation, a T1 or E1 port encapsulates the entire T1 payload (1536000 bits/second) or E1 payload (1984000 bits/second) for transport across the IP network. In channelized operation, a T1 or E1 port may be configured with up to N separate data streams (N = 24 for a T1 port and N = 31 for an E1 port). Each data stream may include any combination of time slots, either contiguous or not. Of course, each time slot may be included in only one data stream.

T1/E1 Clock Sources Supported

On a T1/E1 port, each device must provide the clock used to send data bits to the other device. Depending on the clock configuration of the attached CPE, the T1/E1 port supports any of three clock modes.
If internal clock is specified, the internal oscillator of the router or the network module is used to derive the clock used to send data to the attached CPE.
If line clock is specified, the port phase-locks to the clock provided by the CPE and uses that clock to send data to the attached CPE.
If adaptive clock is specified, the network module provides a clock that is locally synthesized, based on the level of data bits in the egress de-jitter buffer of one of the data streams terminating on the port, to match the clock used at the source data port.

Channel Associated Signaling

If the network module is used to transport N x 64 kbps data streams that carry voice with CAS, the signaling transport feature may be enabled to ensure proper signaling bit extraction, transport, and insertion across the IP network.

FEATURES OF THE NM-CEM-4SER

This network module provides four independent synchronous serial interfaces. Each serial port is equipped with a "smart serial" connector widely used on previous serial interfaces from Cisco Systems®.

Port Types Supported

Depending on the cable plugged into the "smart serial" connector, the port may be:

• V.35

• X.21

• EIA-530

• EIA-530A

• EIA/TIA-449

• EIA/TIA-232

Similarly, depending on the cable plugged into the "smart serial" connector, the port may be either a data communications equipment (DCE) or a data terminal equipment (DTE).
Table 1 and Table 2 below give the Cisco part numbers for each type of available cable.

Serial Data Rates Supported

Each serial data port may be configured to support any of the following data rates, specified in bits per second.

200

3600

12800

32000

76800

168000

384000

1024000

200

3600

12800

32000

76800

168000

384000

1024000

800

6400

16000

48000

96000

224000

512000

1344000

1200

7200

16800

56000

112000

230400

672000

1536000

1800

8000

19200

57600

115200

25600

768000

1544000

2400

9600

24000

64000

128000

288000

772000

2048000

3200

12000

28800

72000

144000

336000

896000

  

Serial Clock Modes Supported

Each serial port may be configured in one of two clock modes to specify whether the DCE or the DTE provides each of the required transmit and receive data clocks.
In normal clock mode, the DCE provides both the receive clock and the transmit clock to the DTE.
In split clock mode, the DCE provides the receive clock to the DTE and the DTE provides the transmit clock to the DCE.

Serial Clock Sources Supported

In any mode where a serial data port provides a clock (or both clocks) to the attached CPE, the source of that clock may be specified.
If internal clock is specified, the internal oscillator of the router or the network module is used to derive the clock(s) provided to the CPE.
If looped clock is specified, the transmit or receive clock provided by the CPE is used as the receive or transmit clock provided to the CPE. Of course, this is supported only in split clock mode.
If adaptive clock is specified, the network module provides a clock that is locally synthesized, based on the level of data bits in the egress de-jitter buffer, to match the clock used at the source data port.

Control Signal Support

The network module provides the option to monitor, transport, and deliver changes in the serial port control signals across the network.
Depending on the cable plugged into the "smart serial" connector, the port may support either the "basic" set of serial control signals or the "extended" set of serial control signals.
The "basic" set of control signals supported follows:

• Data Terminal Ready (DTR)

• Data Set Ready (DSR)

• Request to Send (RTS)

• Clear to Send (CTS)

• Data Carrier Detect (DCD)

• Local Loop (LL)

The "extended" set of control signals supported follows:

• Remote Loop (RL)

• Test Mode (TM)

• Ring Indicator (RI)

Note: The set of control signals supported on each port, and the standards-based name for each signal, depends on the interface type. Each control signal listed may not be supported on every interface type. Also, the control signal names shown are simply the most commonly used names, familiar to most users.

Table 1. Smart Serial Cables with Basic Control Leads

 

DCE

DTE

V.35
· CAB-SS-V35FC
· CAB-SS-V35MT
· CAB-SS-V35MC
· CAB-SS-V35FC
X.21

CAB-SS-X21FC

CAB-SS-X21MT

EIA-530

Not available

CAB-SS-530MT

EIA-530A

Not available

CAB-SS-530AMT

EIA/TIA-449

CAB-SS-449FC

CAB-SS-449MT

EIA/TIA-232

CAB-SS-232FC

CAB-SS-232MT

Table 2. Smart Serial Cables with Extended Control Leads

DCE

DTE

V.35
· CAB-SS-V35FC-EXT
· CAB-SS-V35MT-EXT
· CAB-SS-V35MC-EXT
· CAB-SS-V35FC-EXT
EIA-530

CAB-SS-530FC-EXT

CAB-SS-530MT-EXT

EIA-530A

CAB-SS-530AFC-EXT

CAB-SS-530AMT-EXT

EIA/TIA-449

CAB-SS-449FC-EXT

CAB-SS-449MT-EXT

EIA/TIA-232

CAB-SS-232FC-EXT

CAB-SS-232MT-EXT

Bandwidth Preservation

The network module has the intelligence to detect the failure of the attached CPE and to stop building and sending packets across the IP network when that occurs.
This feature works by detecting that an input clock is missing (assuming the CPE is supposed to provide such a clock) or, optionally, by monitoring the state of any specified serial control signal (known as a "data strobe"). If the clock or the specified control signal becomes inactive, no packets are built until the clock and control signal return to their normal states.
When data packets are not received at the destination port (because of a missing ingress clock, de-activation of the data strobe, or drops in the IP network), the "vacant" data bit times are replaced with a user-configurable idle pattern.

PLATFORM SUPPORT, SOFTWARE, AND MEMORY REQUIREMENTS

Memory Requirements

Memory requirements depend on the selected platform, software feature set, and other installed modules and features. For information about memory planning, refer to the software release notes or the Cisco IOS Software Upgrade Planner, or ask your local Cisco representative.

Platforms Supported

Table 3 shows which platforms support these network modules, and the minimum Ciso IOS Software release for eac p

Table 3. Supported Platforms and Minimum Software Requirements

Platform

Cisco IOS Software Release Required

Cisco 2610XM-2651XM

12.3(7)T and later

Cisco 2691

12.3(7)T and later

Cisco 2811, 2821, 2851

12.3(8)T and later

Cisco 3660

12.3(7)T and later

Cisco 3725 , 3745

12.3(7)T and later

Cisco 3825, 3845

12.3(11)T and later

Cisco IOS Software Feature Set Requirements

These network modules are supported in the following Cisco IOS Software feature sets for the platforms and releases listed in Table 3.

• SP Services and above (Cisco 2600XM, 2691, 2811, 2821, 2851, 3700 and 3800)

–SP Services

–Advanced IP Services

–Enterprise Services

–Advanced Enterprise Services

• IP Plus and above (Cisco 3660 only)

The network modules also are supported in a selection of special purpose feature sets. For more details of the feature sets supporting these network modules, refer to the Feature Navigator at http://www.cisco.com/go/fn or contact your local Cisco representative.

Maximum Number of Circuit Emulation Network Modules per Platform

Table 4 shows the maximum number of network modules, including circuit emulation network modules, that are supported in each platform. Maximum Number of Network Modules Supported

Table 4. Maximum Number of Network Modules Supported

Network Module

Cisco 2600XM

Cisco 2691

Cisco 2811, 2821, 2851

Cisco 3660

Cisco 3725

Cisco 3745

Cisco 3825

Cisco 3845

Total Number of Network Modules Supported

1

1

1

6

2

4

2

4

HARDWARE SPECIFICATIONS

Table 5 shows the environmental specifications for these network modules.

Table 5. Environmental Specifications

Specification

Description

Dimensions (H x W x D)
· 1.55 x 7.1 x. 7.2 inches
· 39 x 180 x 183 millimeters
Operating Temperature
· 32° to 104°F
· 0° to 40°C
Non-operating Temperature
· -40° to 185°F
· -40° to 85°C
Relative Humidity

5 to 95 percent non-condensing

Table 6 shows the hardware specifications for the T1/E1 network module.

Table 6. Hardware Specifications for the NM-CEM-4TE1

Ports

4 Ports (all T1 or all E1 according to software selection)

Nominal Bit Rate per Port
· T1: 1544000 bits/second
· E1: 2048000 bits/second
Line Coding
· T1: binary 8-zero substitution (B8ZS)
· E1: high-density bipolar with three zeroes (HDB3)
Line Framing
· T1: superframe (SF), extended superframe (ESF), or unframed
· E1: G.704 with 4-bit cyclic redundancy check (CRC4), G.704 without CRC4, or unframed
Table 7 shows the hardware specifications for the serial network module.

Table 7. Hardware Specifications for the NM-CEM-4SER

Feature

Description

Ports

4 synchronous serial ports

Port Interface Type

Depends on cable attached; refer to Table 1 and Table 2 for cable options.

· ITU-T V.35
· ITU-T X.21
· EIA-530
· EIA-530A
· EIA/TIA-449
· EIA/TIA-232
Port Interface Polarity

DCE or DTE, depending on cable attached; refer to Table 1 and Table 2 for cable options.

Nominal Bit Rate per Port (bits/second)

Software-configurable to any of the following:

200

400

800

1200

1800

2400

3200

3600

4800

6400

7200

8000

9600

12000

12800

14400

16000

16800

19200

24000

28800

32000

38400

56000

57600

64000

72000

76800

84000

96000

112000

115200

128000

144000

168000

192000

224000

230400

256000

288000

336000

384000

448000

512000

672000

768000

772000

896000

1024000

1152000

1344000

1536000

1544000

2048000

Clock Modes per Port
· Normal: DCE provides Receive Clock and Transmit Clock
· Split: DCE provides Receive Clock and DTE provides Transmit Clock
Clock Sources per Port
· Internal (uses platform time-division multiplexing (TDM) bus phase-lock loop (PLL) clock or on-board oscillator)
· Looped (uses clock provided by CPE)
· Adaptive (uses synthesized clock based on arriving data rate)
Control signals supported per port with standard 12-in-1 "Smart Serial" cables as described in Table 1

The subset of the following control signals that are defined on each interface type are supported (note that some interface types may use different names for these control signals):

DTR

DS

RTS

CTS

DCD

LL

Control signals supported per port with extended 12-in-1 "Smart Serial" cables as described in Table 2

The subset of the following control signals that are defined on each interface type are supported (note that some interface types may use different names for these control signals):

RL

TM

RI

Control Signal Sampling Rate

0 to 20 samples per second

REGULATORY COMPLIANCE, SAFETY, EMISSIONS, EMC, AND IMMUNITY

Table 8 shows a partial listing of regulatory compliance and safety data.

Table 8. Regulatory Compliance and Safety (Partial Listing1)

Telecommunication Interface Industry Standards

NM-CEM-4TE1 Configured in T1 Mode
· TIA-968-A (U.S. requirement, formerly known as FCC Part 68)
· G.703
· G.704
· G.824 (except not compliant with clock wander requirements in adaptive clock mode)
· CS-03 (Canada)
· T1.403
· GR-499
NM-CEM-4TE1 Configured in E1 Mode
· G.703
· G.704
· G.706
· G.823 (except not compliant with clock wander requirements in adaptive clockmode)
· TBR 4, 12, and 13 (Europe)
· ACA S016 (Australia)
NM-CEM-4SER

TBR 1 and 2 (Europe)

Safety
· US (UL 60950)
· Canada (CSA-C22.2 No. 60950)
· UK (EN 60950)
· Germany (EN 60950)
· France (EN 6095)
· Australia and New Zealand (TS001, AS/NZS 60950)
· Other countries (IEC 60950)
NEBS
· GR-63
· GR-78
· NM-CEM-4TE1 is designed for compliance with GR-1089-Core Type 1/3
· NM-CEM-4SER is designed for compliance with GR-1089-Core Type 2/4
EMC Emissions and Immunity
· EN300386: 2001
· EN50082-1: 1997
· EN55022: 1998
· CISPR22: 1997
· EN61000-3-2:2000
· EN61000-3-3: 1995
· EN55024: 1998
· EN55082-1: 1992
· AS/NZS3548: 1995 (including Amendments I and II)
· VCCI:V-3/2000.04
· CNS13438: 199
· CISPR24: 1997
· ITU-T K.22: 1995
· CFR 47 Part 15: 2002
· CFR 47 Part 15 Subpart B
· EN61000-4-6: 1996 (including Amendment 1)
· EN61000-4-3: 1996 (including Amendments 1 and 2)
· EN61000-4-2: 1995 (including Amendments 1 and 2)
· EN61000-4-4: 1995
· EN61000-4-5: 1995
· EN61000-4-11: 1994 (including Amendment 1)
· EN61000-4-5: 1995
· EN300386-2: 1997
· CISPR22: 1997
· EN55022: 1998
1 For more information, visit the Cisco Compliance home page (listed later in this document under Country Support) or contact your local Cisco representative for further details.

POWER AND ENVIRONMENTAL REQUIREMENTS

These network modules, when installed in Cisco routers, do not change the power or environmental requirements and standards of the router platform itself. Refer to the platform-specific data sheets for more information.

Country Support

Contact your local Cisco representative for country-specific approval information.
2007/05/04 12:10 2007/05/04 12:10
트랙백 0개, 댓글 0개가 달렸습니다.

트랙백 주소 :: http://thinkit.or.kr/network/trackback/349

댓글을 달아 주세요

Alarm Monitoring & Remote Control Module for Cisco 2600/3600

CISCO/라우터 & 라우팅 시스템 2007/05/04 12:09
ALARM INTERFACE CONTROLLER NETWORK MODULE FOR THE CISCO 2600 AND 3600 SERIES

The Cisco NM-AIC-64 Network Module expands the capabilities of Service Provider and Enterprise networks by providing remote alarm monitoring and control of non-IP devices. By installing this network module into the Cisco Multi-service Access Routers or Integrated Services Routers, network managers have the capability of monitoring and controlling remote, unstaffed sites to provide increased security, reliability, and control of the network. For example, if a flood occurs at a service-provider remote site, the Alarm Interface Controller (AIC) issues an alarm. The network manager can then invoke a command to turn on a sump pump instead of wasting valuable time waiting for somebody to arrive at the facility. In the event of an unauthorized entry into a secure area, the AIC can initiate a visual and audible alarm. Further, if wired to a camera, the AIC can activate it for remote surveillance.

Figure 1. Cisco NM-AIC-64

The Cisco NM-AIC-64 is a network module that greatly expands the network monitoring and control capabilities of the Cisco Multi-service Access Routers or Integrated Services Routers. The AIC functions as an integrated entity, residing within the Cisco 26xx and 36xx routers to provide network alarm monitoring and remote control of network elements through contact closure. The AIC reduces service-provider and enterprise operating expenses by providing a flexible, low-cost integrated solution for migrating existing monitoring equipment onto a highly scalable IP-based solution from Cisco. The AIC facilitates a seamless solution, because it can be housed and configured in a Cisco IOS® Router, greatly simplifying network layout and management, and thereby reducing the high cost of operations, administration, maintenance, and provisioning (OAM&P). The AIC is supported starting with Cisco IOS 12.2 (2) XG & 12.2(8)T
Each AIC can monitor 64 network elements, and remotely control 16 network elements. More than one AIC can be installed per router. For example, a Cisco 366x with its six network-module slots can accommodate up to six AICs, giving the Cisco 366x the ability to monitor up to 384 network elements and remotely control 96 network elements, all in one highly compact chassis
The AIC Network Module supports 64 discrete alarm inputs, of which 8 of the last 64 alarm points are software configurable to accept either analog or discrete inputs. The AIC further supports 16 control relays to facilitate the remote control of network elements. Each of the 64 discrete alarm inputs can be activated via ground or negative battery input. The negative battery range is -36V to -72V. The analog alarm input can be configured to monitor either DC voltage or current. It can measure voltage from -60V to 60V or current from 0 to 20 mA. The control relays can be utilized to remotely control simple network devices. These alarm inputs are configured in Cisco IOS Software. Some reportable events include:

• Network element alarm states

• Building security/intrusion detection (opening and closing of doors and windows)

• Building environmental factors (temperature and humidity)

• Commercial power (A/C) and central-office (CO) (D/C) power readings

• Fire and smoke detection

• Equipment alarm

• Temperature threshold violation

• Voltage fluctuation

The AIC converts relay contact alarm signals to Transaction Language One (TL-1) and Simple Network Management Protocol (SNMP) message formats, providing TL-1 over Transmission Control Protocol/Internet Protocol (TCP/IP) and SNMP protocols. When an event occurs, such as a door alarm or an open gate, the AIC maps the simple discrete and analog alarms to preprogrammed intelligent messages and transports the messages to destinations in the IP network, typically to a Network Operations Center (NOC). Generated either in TL-1 or in SNMP, these messages are used by an Operations Support System (OSS). All the contact closure-related alarms are routed and reported through the existing OSS and the associated OSS networks. The AIC sends the TL-1 or SNMP messages to the OSS autonomously or in response to TL-1 or SNMP commands from the OSS. The option to utilize TL-1 or SNMP is defined by the user, and it is software configurable on the AIC.

Figure 2. Alarm Interface Controller Network Module

CONNECTING THE CISCO NM-AIC-64 NETWORK MODULE TO THE NETWORK

The alarm and remote-control features of the AIC are accessed via four female small computer serial interface (SCSI) II (Micro DB-50) interfaces (see Figure 2). A SCSI II (Micro DB-50) cable with male connectors is required to interface the female SCSI II interfaces on a AIC Network Module to a SCSI II-to-Telco-50 pin patch panel. Two different patch panels are available based on customer requirements (see Table 1). It is highly recommended that a patch panel be used in conjunction with the AIC. Figures 2 and 3 give examples of the two types of patch panels. SCSI cables and the recommended patch panels are not supplied with the network module; they are orderable separately as necessary. The recommended patch panels and cables are available either from Cisco Systems or Components Express (www.networkcable.com). (See Table 1 for part numbers).

Table 1. Accessory Patch Panels and cables for the AIC

Part Number

Description

AIC-DBL-PNL

Patch panel for terminating up to two AIC or 128 alarm points

AIC-SGL-PNL

Patch panel with power monitoring terminals, for terminating one AIC with eight lugs and fuses for power monitoring

CAB-AIC-008

Set of four eight-foot-long male-to-male SCSI II interface cables

Figure 3. AIC-DBL-PNL: Interfaces up to two (2) Alarm Interface Controllers.

Isometric Front View
Top View
Isometric Back View
Front View
Back View

Figure 4. AIC-SGL-PNL: Panel with Voltage Monitoring.

Isometric Front View
Top View
Isometric Back View
Front View
Back View

AIC NETWORK MODULE LIGHT EMITTING DIODES

The AIC follows the convention of other network modules for light emitting diode (LED) operation. There are two LEDs-enable (EN) and status (STAT). Table 2 lists the network-module state indicated by the LEDs, and Figure 5 shows the placement of the LEDs.

Figure 5. AIC Network-Module LEDs

Table 2. AIC LED Description

STAT LED

EN LED
Green
Orange
Description

Off

Off

Off

Power off to router

On

Off

Off

Software initializing

On

On

Off

Normal operation

On

Off

On

Fault encountered

INTERFACING THE AIC

When the AIC is incorporated into a DCN-Operations Support Network router, all the AIC contact-closure alarms are routed and reported through the same network and systems as the DCN router. This setup facilitates continued use of the existing OSS and its associated networks. A Cisco router with an AIC sends TL-1 or SNMP messages to the OSS autonomously or in response to TL-1 or SNMP commands from the OSS, as shown in Figure 6.

Figure 6. TL-1 and SNMP Message Flow in an Operations Support Network Application

SERIAL COMMUNICATION CHANNELS

The AIC has an embedded operating system that interfaces with the Cisco IOS Software in the router. Communication between the AIC operating system and Cisco IOS Software is accomplished through two serial communications channels, as illustrated in Figure 7:

• Serial data channel

• Asynchronous craft port

Serial Data Channel

The serial data channel supports all TCP/IP traffic to and from the AIC, including communication over IP with NOCs and data centers. The channel consists of one physical interface that provides support for the following applications:

• Telnet-Used to communicate directly with the AIC OS and command-line interface (CLI)

• TL-1-Used to transport TL-1 messages between the NOC and the AIC

• Trivial File Transfer Protocol (TFTP)-Used to download firmware to the AIC

• SNMP-Used to transport SNMP traps between the Network Operations Center and the AIC

The Cisco IOS Software assigns an IP address to the AIC for use by the serial data channel. To route traffic, the serial data channel uses IP over synchronous High-Level Data Link Control (HDLC). All IP packets coming to the Cisco router with a destination IP address that matches the AIC IP address are forwarded to the serial data channel using IP over HDLC.

Asynchronous Craft Port

The asynchronous craft port supports Telnet to the AIC port number. This Telnet method, called local CLI, is useful for debugging when remote Telnet to the AIC IP address (remote CLI) is not applicable. The asynchronous craft port also supports an AIC boot sequence, similar to the ROM monitor in Cisco IOS Software, which allows the user to recover from a corrupted software image or configuration.

Figure 7. TOS Boundary into the AIC

SUPPORTED STANDARDS, MIBS, AND RFCS

Standards

The new standard that the AIC adds to the Cisco portfolio of protocols supported is Transaction Language One (TL-1).

MIBs

The AIC introduces a new Management Information Base (MIB) called CISCO-AIC-MIB. To support the AIC, an AIC object type and AIC ID have been added to the following MIBs:

• OLD-CISCO-CHASSIS-MIB

• CISCO-ENTITY-VENDORTYPE-OID-MIB

To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB Web site on Cisco.com at: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

Configuring Alarms

Alarms are configured using either TL-1 or AIC CLI. Information about TL-1 commands can be found in the Telcordia Technology (formerly Bellcore) document Network Maintenance: Network Element and Transport Surveillance Messages, GR-833-CORE, Issue 5, November 1996. For a reference of security-related commands (ACT-USER and CANC-USER), refer to Telcordia Technology's Operations Applications Messages-Network Element and Network System Security Admin Messages, TR-NWT-000835, Issue 2, January 1993.

AIC CLI Syntax

The AIC is designed to provide different privilege levels for separation of tasks among various personnel in a central office. Described in Table 3, these modes are designed to mimic the modes available at the Cisco CLI:

Table 3. AIC CLI Privilege Levels

Features

Description

User Mode
(Prompt: name >)

The interface begins in user mode. This mode is not password protected, by default, although it may be configured to be. In user mode, commands that show information are available. Also available is the command for entering privileged mode.

Privileged Mode
(Prompt: name #)

In privileged mode, configuration may be viewed and all user-mode commands are available. Also available are the commands for reentering user mode and entering configuration modes.

Upon entrance to privileged mode, if one or more users are already using privileged mode (or any configuration mode), the entering user is warned that those other users may be configuring the AIC.

Global Configuration Mode
(Prompt: name (config)#)

Global configuration mode allows configuration of global options and allows the user to enter the subconfiguration modes. The commands available here are not available in other modes. The prompt in this mode is the AIC name followed by config#.

Subconfiguration Modes
(Prompt: name (config-xxx)#)

The subconfiguration modes are used for configuring specific parts of the AIC. Commands available in this mode are not available in other modes. Four subconfiguration modes are available: alarm, control, TL-1, and SNMP. The prompts in these modes are the AIC name followed by (config-alarm)#, (config-control)#, (config-tl1)#, and (config-snmp)#.

ORDERABILITY, AVAILABILITY, COMPATIBILITY, MINIMUM SOFTWARE, AND MEMORY REQUIREMENTS

Table 4. Product Specifications/Regulatory Approvals Part Number NM-AIC-64(=

Features

Description

Network Module Density
· 64 discrete alarm points
· Up to 8 of the last 64 alarm points can be configured to accept analog or discrete inputs.
· 16 relay control points

Cisco IOS Release

Cisco IOS 12.2 (2) XG and higher

Voltage Range Discrete Points

-36V to -72V

Analog Input Modes

Current sense or voltage sense

Voltage Sense Range-Analog Input

-60V to 60V

Current Sense Range

0 to 20 mA

Number of Network Modules Supported
· Cisco 366x-Six network modules or 384 contact points, and 96 relay controls
· Cisco 3640-Three network modules or 192 contact points, and 48 relay controls
· Cisco 3631-Two network modules or 128 contact points, and 32 relay controls
· Cisco 26xx-One network module or 64 contact points, and 16 relay controls

Alarm Message Formats/Protocols Supported

Configurable-TL-1 (two sessions) or SNMP (four sessions) Alarm messages can be sent autonomous or upon being polled.

Connector Types

Four SCSI II Micro DB-50 female connectors

Recommended Patch Panels and Cables (See Table 1)

AIC-DBL-PNL, AIC-SGL-PNL, CAB-AIC-008

MIB Support

CISCO-AIC-MIB

Online Insertion and Removal (OIR) Support

Yes, on Cisco 366x 3745, and 3845 only

Standards and Compliance Support

Dimensions (H x W x D) 1.55 x 7.10 x 7.2 in.

Weight

1.1 lb maximum

Environmental Conditions
· Operating temperature: +32° to +104° F (0° to +40° C)
· Nonoperating temperature: 13° to +158° F (25° to +70° C)

Power Requirements

10.7 watts

Maximum Relative Humidity

5 to 95 percent

Mean Time Between Failures (MTBF)

113,772 hours at 25° C ambient conditions

Emissions
· CISPR22:1997 [EN55022:1998] Class A 0.15-30MHz [dBuV/dBuA] Conducted Emissions
· CISPR22:1997 [EN55022:1998] Class A 30MHz-1GHz [dBuV/m] Radiated Emissions

Immunity
· EN61000-4-2: 1995 Level 3 6kV Contact,8kV Air ESD
· EN61000-4-3: 1997 Level 3 10V/m Radiated RF Susceptibility
· EN61000-4-4: 1995 Level 4 2kV Burst/Transients
· EN61000-4-4: 1995 Level 4 4kV Burst/Transients
· EN61000-4-5: 1995 - 0.5kV/0.5kV Surges
· EN61000-4-6: 1996 Level 3 10V Conducted RF Susceptibility
· AS/NZS 3548: 1995 incorporating Amendments 1 and 2
· VCCIV-3/ 97.04
· 47 CFR 15 Subpart B: 1998

Additional Conformance

The NM-AIC-64 carries the CE mark for meeting the respective requirements. Additionally, meets AS/NZS 3548: 1995 for Australia.

Glossary AIC

Alarm Interface Controller

CAP

Competitive access provider

CLEC

Competitive local exchange carrier-In the United States, The Telecommunications Act of 1996 allowed CLECs/CAPs) to compete with the regional Bell operating companies (RBOCs) for local traffic. CLECs are frequently aggressive competitors who are trying to grow their networks quickly in order to gain market share. CLECs frequently partner with Tier 2/3 Internet service providers (ISPs). The CLEC provides the access portion of the network and delivers bulk traffic to the ISP. CLECs tend to focus on business customers.

DCN

Data Communications Network

IP

Internet protocol-IP is the Open System Interconnection (OSI) Layer 3 (the network layer protocol), which contains addressing information and some control information that allows packets to be routed. IP is a connectionless-orientated protocol that offers network services. IP provides features for addressing, type-of-service specification, fragmentation and reassembly, and security. IP was originally developed by the Department of Defense (DoD) to support interworking of dissimilar computers across a network. This protocol works with TCP and is usually identified as TCP/IP. (See TCP/IP and OSI model; IP is documented in RFC 791.)

Cisco IOS Software

Cisco Internet Operating System Software-This software provides common functionality, scalability, and security for all products under the CiscoFusion architecture. Cisco IOS Software allows centralized integrated and automated installation and management of internetworks, while ensuring support for a wide variety of protocols, media, services, and platforms. See CiscoFusion.

NM

Network module

NOC

Network Operating Center

OSS

Operation Support Systems

SNMP

Simple Network Management Protocol-This TCP/IP protocol was built to serve as a communications channel for internetwork management operating at the application layer of the IP stack. TL-1 is a widely used management protocol for telecommunications developed by Telcordia Technologies' GRE833-CORE specification.

TCP

Transmission Control Protocol-TCP is the common name for the suite of protocols developed by the U.S. DoD in the 1970s to support the internetwork of dissimilar computers across the network and the construction of worldwide internetworks. TCP is a transport protocol that offers a connection-oriented transport service in the Internet suite of protocols. TCP provides transport level connections between hosts. It is designed to provide a reliable connection and handles error detection, lost packets, and packets that arrive out of sequence. It is also called TCP/IP because it uses IP. The entire collection of IP protocols is also frequently referred to as TCP/IP. Telnet uses TCP for its connections. TCP is a Layer 4 protocol that operates under IP to provide the sequencing, reliable transport, and the end-to-end connection of packets. Often, TCP and IP are used in the same context, TCP/IP. Some TCP-based protocols include:

· TELNET X-WINDOWS
· File Transfer Protocol Hypertext Transfer Protocol (FTP HTTP)
· Simple Mail Transfer Protocol (SMTP)

TCP is the reliable end-to-end protocol used on the Internet. It is a virtual circuit protocol in that when a connection is established between two endpoints, data flows only between those two endpoints until the connection is closed. TCP is defined in RFC-793. TCP and IP are the two best-known protocols in the suite. See also TCP/IP and IP.

TCP/IP

The two best-known internet protocols, often erroneously thought of as one protocol-The Transmission Control Protocol (TCP), which corresponds to Layer 4 (the transport layer) of the Open System Interconnection (OSI) reference model, provides reliable transmission of data. The Internet Protocol (IP) corresponds to Layer 3 (the network layer) of the OSI reference model and provides connectionless datagram service. TCP/IP were the internetworking protocols developed by the U.S. Department of Defense's Advanced Research Project Agency (ARPA) in the 1970s to support the construction of worldwide internetworks. TCP/IP has been widely adopted and supported by computer and software manufacturers as a standard computer networking protocol. It is a transport and interworking protocol that is an accepted networking standard. Commonly used over X.25 and Ethernet cabling, TCP/IP is viewed as one of the few protocols available that is able to offer a true migration path toward OSI. It was originally developed by the U.S. Department of Defense and is able to operate in most environments. TCP/IP operates as Layers 3 and 4 of the OSI model (network and transport, respectively). TCP/IP ensures that packets of data are delivered to their destination in the sequence in which they were transmitted. TCP/IP is also the delivery mechanism for associated services, including Simple Network Management Protocol (SNMP), Simple Mail Transfer Protocol (SMTP), File Transfer Protocol (FTP), and Telnet. TCP/IP protocols are the WAN protocols of choice. They include protocols that address media access, packet transport, session communication, file transfer, electronic mail, and terminal emulation. The main protocols in the suite include the following:

· TELNET X-WINDOWS
· File Transfer Protocol Hypertext Transfer Protocol (FTP HTTP)
· Simple Mail Transfer Protocol (SMTP)

TCP is the reliable end-to-end protocol used on the Internet. It is a virtual circuit protocol in that when a connection is established between two endpoints, data flows only between those two endpoints until the connection is closed. TCP is defined in RFC-793. TCP and IP are the two best-known protocols in the suite. See also TCP/IP and IP.

WIC

Wide-area network (WAN) interface card-The WIC can be placed in the network-module slot.

RELATED DOCUMENTS

For additional information, see the following documents:
2007/05/04 12:09 2007/05/04 12:09
트랙백 0개, 댓글 0개가 달렸습니다.

트랙백 주소 :: http://thinkit.or.kr/network/trackback/348

댓글을 달아 주세요

600-Watt Redundant AC Power System

CISCO/라우터 & 라우팅 시스템 2007/05/04 12:08

600-Watt Redundant AC Power System

While software and hardware redundancy have long been a requirement for the core networks of large companies, increasingly both their smaller offices and offices of small and medium-sized businesses have the same needs. The 600-Watt redundant AC Power System meets this need for hardware redundancy as an option for a range of Cisco routers, switches, hubs and access servers.

The 600-watt Redundant AC Power System (RPS), the PWR600-AC-RPS, is a separate chassis that provides redundant power for any combination of up to four of the following products:

  • Cisco 1516M hub (HP 10Base-T Hub-16M)
  • FastHub 400 Series 10/100 hubs
  • Catalyst 1900 Series Ethernet switches
  • Catalyst 2820 Series Ethernet switches
  • Catalyst 2900 Series XL switches
  • Catalyst 3500 Series XL switches
  • Cisco 2500 Series routers
  • Cisco 2500 Series access servers
  • Cisco 2600 Series routers
  • Cisco 2600XM Series routers
  • Cisco 3620/3640 Series routers
  • Cisco 3725 Series routers
  • Cisco MC3810 Multiservice access concentrator
  • Cisco 4000 Series routers

PWR 600-AC-RPS 600-Watt Redundant AC Power System

This power system is ideal for powering these stackable LAN and WAN products. It supports both local and remote monitoring of system status. Front-mounted LEDs allow a quick check of local status for AC input power, DC output power, cooling fans and system temperature. When one of the external devices being powered is a Cisco 2600, 3600, or 3700 Series, the 2600, 3600, or 3700 Series access server/router can receive and store status signals from the system. In turn, the status stored on router is available for remote monitoring via Simple Network Management Protocol (SNMP) products such as CiscoWorks.

Features

  • Support of up to four of any combination of 150-watt external devices (hubs, switches, routers, and access servers)
  • Hot insertion of external devices
  • Dual AC inputs and power cords
  • Two fully redundant AC input power modules
  • Four DC output power modules
  • Four one-to-one DC power cables (PWR600-AC-RPS-CAB)
  • LEDs on front panel for AC input, DC output, fan, and temperature status
  • Redundant cooling fans
  • Remote monitoring using SNMP via a Cisco 3700, 3600, or 2600 Series
  • 19-inch rack-mount kit included (24-inch optional)

Benefits

  • Increased network uptime
    • with dual AC input modules power supply mean time between failure (MTBF) is significantly improved
    • demonstrated MTBF in excess of 500,000 hours
  • Advanced warning of possible failure
    • Front Panel LEDs for AC input power, DC output power, and cooling status
    • SNMP manageable via a Cisco 3700, 3600 or 2600 Series router
  • Flexibility and cost-effectiveness
    • a single RPS supports up to four external devices
    • match the level of redundancy required to the specific application requirements

Software Requirements

The RPS itself requires no software. When the RPS powers a Cisco 3600 Series router, the Cisco 3600 series must be loaded with Cisco IOS® Release 11.2(7)P (available July 1997) or later.

Specifications

  • Dimensions (H x W x D): 3.44 x 17.5 x 16 in.
  • Weight: 27.25 lbs
  • Nominal input voltage: 100 to 240 VAC autoranging
  • Current: 10A maximum
  • Frequency: 50 to 60 Hz
  • Absolute maximum input: 1000W
  • Output voltage/current: +5@24 ADC, +12@5 ADC, -12@3 ADC
  • Output power: 150W per module (maximum)
  • Operating temperature: 32 to 104° F (0 to 40° C)
  • Operating humidity: 10 to 85%, noncondensing
  • Operating altitude: 0 to 10,000 feet
  • Nonoperating temperature: -4 to 149° F (-20 to 65° C)
  • Nonoperating humidity: 5 to 95% noncondensing
  • Nonoperating altitude: 0 to 30,000 feet
  • Normal operating noise level: 48 dBA
  • Regulatory compliance: FCC Class B
  • Status LEDs (bicolor: Off, Amber, Green): AC input power, DC output power, fan, and temperature
  • Demonstrated MTBF in excess of 500,000 hours

2007/05/04 12:08 2007/05/04 12:08
트랙백 1개, 댓글 0개가 달렸습니다.

트랙백 주소 :: http://thinkit.or.kr/network/trackback/347

  1. Subject: Think IT :: 600-Watt Redundant AC Power System

    Tracked from pligg.com 2016/11/27 08:48  삭제

    ajax cart,ajax cms,ajaxfied cart,ajaxfied cms,fast cart,php cart,free cart,free php cart

댓글을 달아 주세요

1 ... 8 9 10 11 12 13 14 15 16 ... 128