ADTRAN 4200659L2 User Manual

Size:
1.66 Mb
Download

Chapter 8 Power Loss Recovery

The MX2800 STS-1provides backup measures of protection for both power supply and power source failures. The following sections describe the possible modes of operation:

Non-Redundant Power Mode, which offers no backup protection, is described on page 8-2.

Power Supply Recovery Mode, which offers backup protection in the event of power supply card failure, is described on page 8-3.

Power Supply and Source Recovery Mode, which offers a backup system for both card and source failure, is described on page 8-4.

Battery Backup Mode, which offers battery backup in the event of a power outage, is described onpage 8-5.

61200659L1-1

MX2800 STS-1User Manual

8-1

Chapter 8. Power Loss Recovery

NON-REDUNDANTPOWER MODE

In Non-RedundantPower Mode, the MX2800STS-1houses only one power supply card and only one power source is available. There is no power failure protection. If a power supply card fails, then the unit is inoperable until the card is repaired or replaced. SeeFigure 8-1 for an illustration.

MX2800 STS-1

Figure 8-1.Non-RedundantPower Mode

Power supplies are hot-swappable.

8-2

MX2800 STS-1User Manual

61200659L1-1

Chapter 8. Power Loss Recovery

POWER SUPPLY RECOVERY MODE

In Power Supply Recovery Mode, two power supply cards are installed and connected to a single power source (see Figure 8-2).In this mode, the MX2800STS-1can continue to operate during a power supply failure, without interrupting service. The power supplies are load sharing, so either power supply can provide power for the entire unit.

When the unit is configured with dual internal AC power supplies, this is the only power protection mode available.

MX2800 STS-1

Figure 8-2.Power Supply Failure Recovery Mode

61200659L1-1

MX2800 STS-1User Manual

8-3

Chapter 8. Power Loss Recovery

POWER SUPPLY AND SOURCE RECOVERY MODE

In this mode, two power supply cards are installed and are connected to two individual power sources. The MX2800 STS-1handles any combination of power source or power supply failure.

Much like the backup design for the controller cards, the MX2800 STS-1is able to internallyre-routethe power source if a power supply card and theopposite power source fail. For example, in the illustration given inFigure 8-3,failedPOWER SOURCE A is connected to functionalCARD A and functionalPOWER SOURCE B is connected to failedCARD B. In this case, the MX2800STS-1automatically connectsPOWER SOURCE B toCARD A.

This configuration is only available with DC power supplies.

STS-1

Figure 8-3.Power Supply and Source Failure Recovery Mode

8-4

MX2800 STS-1User Manual

61200659L1-1

Chapter 8. Power Loss Recovery

BATTERY BACKUP MODE

With the installation of the ADTRAN Power Supply/Battery Charger (PS/BC) and backup battery pack, the MX2800 STS-1is able to continue operation without service interruption during a power outage. This PS/BC (P/N 4175043L2) provides-48VDC to the MX2800STS-1.It receives 115 VAC through a standard plug and wall socket.

The PS/BC maintains the battery at peak charge (-48V) at all times. If AC power is lost, the unit automatically transfers power to the battery without interrupting service. When AC power returns, the unit switches back to AC power and recharges the battery. For installation instructions, refer to the guide provided with the PS/BC. SeeFigure 8-4 for an illustration of this setup.

.

MX2800 STS-1

NET

Magnified View

PWR FAIL

-

RET

PWR FAIL

-

RET

AC/DC Power Supply

Battery Charging Unit

P/N 1175043L2

AC Power Input

Green

Black

Red

White

-48VDC

Backup Battery Pack

P/N 1175044L1

Battery Charger

Power Cable

Figure 8-4.Battery Backup System

The MX2800 STS-1can operate on afully-chargedbattery for four hours without recharging.

61200659L1-1

MX2800 STS-1User Manual

8-5

Chapter 8. Power Loss Recovery

8-6

MX2800 STS-1User Manual

61200659L1-1

Chapter 9 Transaction Language 1 (TL1)

INTRODUCTION

Transaction Language 1 (TL1) is a BELLCORE standard used in the input and output messages that pass between Operations Systems (OS) and Network Elements (NE) in telecommunication networks. It was developed to standardize equipment surveillance and memory administration, and to test with a common format.

This release of TL1 primarily supports the interactive and autonomous retrieval of system events as part of a valid TL1 session.

OVERVIEW

TL1 is an ASCII-basedlanguage that supports both commandresponse and autonomous (NE) message generation. Commonly, TL1 is used over a X.25 packet network but is completely independent of any physical layer protocols. For the

MX2800 STS-1,TL1 is implemented as a Telnet session running over either Ethernet or PPP.

Currently, up to eight simultaneous TL1 Telnet connections can be active. To manually bring up a TL1 Telnet connection, a Telnet client is used to request a connection on (TCP) port 3116. A successful connection will require that the MX2800 STS-1be properly configured to operate via the LAN or modem. For example, in the LAN case, the MX2800STS-1must have the LAN

61200659L1-1

MX2800 STS-1User Manual

9-1

Chapter 9. Transaction Language 1 (TL1)

management port enabled, a valid IP and gateway address, and a valid subnet mask.

Once the Telnet connection is established, it is necessary to initiate a TL1 session. Establishing a TL1 session involves successful user authentication. Until a TL1 session is established, all commands other than those used to initiate or terminate a session will be denied (autonomous messaging is also disabled). Authentication involves the successful entry of a username/password pair. A table of usernames and associated passwords and privileges is kept for TL1 authentication. This table is maintained by an administrator through theVT-100menus or through a TL1 session. For information on using theAct-Usercommand to initiate a TL1 session, see the sectionTL1 Commands on page 9-5.

TL1 MESSAGES

As stated earlier, TL1 messages are either part of a commandresponse exchange or are generated autonomously.

The general format for a TL1 command is as follows:

<VERB>[-<MOD1>[-<MOD2>]]:[<TID>]:[<AID>]:[<CTAG>]:[GB](:<PARAMx>(,<PARAMx>)*)*;

Refer to TL1 Commands on page 9-5 for a list of TL1 commands supported by the MX2800STS-1.

TL1 Responses

There are three types of TL1 responses:

Acknowledgment messages

Output Response messages

Autonomous messages

Acknowledgment Messages

Acknowledgment messages are brief output messages generated in response to received TL1 commands. The MX2800 STS-1

9-2

MX2800 STS-1User Manual

61200659L1-1

Chapter 9. Transaction Language 1 (TL1)

currently supports two types of acknowledgment messages: In Progress (IP) and All Right (OK).

In Progress

The IP acknowledgment message is usually generated as an interim response message to indicate that a message has been received and that the command is being executed. IP messages have the following general format:

IP <CTAG><CR><LF>

<

All Right

The OK acknowledgment message indicates that a command has been received and that the required action was initiated and completed. This message has the following general format:

OK <CTAG><CR><LF>

<

Output Response Messages

Output Response messages are generated in response to received commands and have the following general format:

<CR><LF><LF>

<SID> <YR>-<MO>-<DAY><HR>:<MIN>:<SEC><CR><LF>

M<CTAG> <COMPLETION CODE><CR><LF>

(<UNQUOTED LINE>|<QUOTED LINE>|<COMMENT><CR><LF>)*

(;|>)

For the MX2800 STS-1,theCOMPLETION CODE field will contain one of the following values:

COMPLD - Successful execution of the received command

DENY - Denial of the received command

When the received command is denied, the line in the message following the COMPLETION CODE line will contain a4-lettererror code. See the sectionTL1 Error Codes on page 9-13 for a description of possible MX2800STS-1error codes.

61200659L1-1

MX2800 STS-1User Manual

9-3

Chapter 9. Transaction Language 1 (TL1)

The MX2800 STS-1specifically uses “quoted line(s)” in the response message of successfully executedRTRV-ALM commands. The quoted line format is as follows:

<AID>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,<LOCN>…

The NTFCNCDE field will contain one of the following values:

MN - Minor

MJ - Major

CR - Critical

Refer to the condition types listed in Table 9-2 on page 9-10 (MX2800 STS-1 Alarm Events) for possible MX2800STS-1

CONDTYPE codes.

Autonomous Messages

The Autonomous message is sent from the NE to the OS and is not associated with any explicit input message. The MX2800 STS-1uses this message to exclusively report alarmed andnon-alarmedevents. An autonomous message has the following general format:

<CR><LF><LF>

<SID> <YR>-<MO>-<DAY><HR>:<MIN>:<SEC><CR><LF> <ALARM CODE> <ATAG> <VERB>[ <MOD1>[ <MOD2>]]<CR><LF> (<UNQUOTED LINE>|<QUOTED LINE>|<COMMENT><CR><LF>)+ (;|>)

Possible values for the ALARM CODE field include:

*C - Critical Alarm

** - Major Alarm

* - Minor Alarm

A - Non-alarm

NULL - (blank)

9-4

MX2800 STS-1User Manual

61200659L1-1