sonet transmission products s/dms transportnode …npatrick/nortel-sdms-docs/n3rltcyl.pdf ·...

NT7E65DJ 323-1111-104

SONET Transmission Products

S/DMS TransportNodeOC-3/OC-12 NE—TBM

Alarms and Surveillance Description

Standard Rel 14 February 2001

What’s inside ...

Alarm reporting and surveillanceLog report descriptionSurveillance interface

Copyright

1992–2001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks and S/DMS TransportNode are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment Corporation. UNIX is a trademark of X/Open Company Ltd.

Printed in Canada

iii

Contents What’s inside ...About this document v

Alarm reporting and surveillance 1-1Alarm severity, service code, and protection and activity status 1-1

Critical 1-1Major 1-1Minor 1-2Warning 1-2Service code 1-2Protection and activity status 1-2

Time filtering 1-2Local alarm indications 1-2

Bay alarms 1-3Shelf alarms 1-3Circuit pack alarms 1-4Cooling unit alarms 1-5

Remote alarms 1-5Alarm reporting 1-7Alarm hierarchy 1-8

Facility alarm hierarchy 1-8Equipment alarm hierarchy 1-10Common equipment and environmental alarm hierarchy 1-11

Control architecture 1-11

Log report description 2-1Numbering scheme 2-1NE logs 2-2OPC logs 2-4

Surveillance interface 3-1Operations controller 3-1

OPC network communication 3-1OPC network surveillance 3-1

Maintenance interface controller circuit pack 3-2User interface CRT 3-4X.11 terminal 3-4Serial telemetry (TBOS) 3-6

TBOS displays 3-7

Alarms and Surveillance Description 323-1111-104 Rel 14 Standard Feb 2001

iv

Contents

TBOS protocol 3-10TBOS scan request 3-11TBOS command request 3-12

Remote telemetry 3-14Network summary display (Remote network telemetry) 3-14Network element monitor display 3-15Network application 3-15Remote parallel telemetry 3-16Impact of communications losses between OPC and network elements 3-17

Alarms not displayed on the monitor displays 3-54Parallel telemetry 3-55

External customer inputs (telemetry inputs) 3-56External customer outputs (telemetry outputs) 3-56

S/DMS TransportNode OC-3/OC-12 NE—TBM Vol 1 323-1111-104 Rel 14 Standard Feb 2001

v

About this documentThis document provides details on the alarms and surveillance network available with the OC-3 and OC-12 network element. Topics covered include alarm features and definitions, and the interfaces that provide these features.

AudienceThis document is for the following members of the operating company:

• planners

• provisioners

• network administrators

• transmission standards engineers

• maintenance personnel

References in this documentThis document refers to the following documents:

• System Administration, 323-1111-100

• Circuit Pack Descriptions, 323-1111-102

• TL1 Interface Description, 323-1111-190

• Installation Procedures, 323-1111-201

• System Admnistration Procedures, 323-1111-302

• Network Surveillance Procedures, 323-1111-510

• Alarm and Trouble Clearing Procedures, 323-1111-543

• Log Report Manual, 323-1111-840


vi

About this document


1-1

Alarm reporting and surveillance 1-The OC-3 and OC-12 network elements offer an integrated alarm reporting system structured to efficiently locate and identify the source of a problem. There is a correlation of all alarm indications to present only one alarm point for each event whenever possible. Single-ended maintenance is provided, which means that a user can issue commands from one network element to be executed at another network element within the system.

Note: Shelf alarm monitoring is not available during processor circuit pack reset or software download.

For information on alarms and how to clear an alarm, see Alarm and Trouble Clearing Procedures, 323-1111-543. For information on how to display alarms for the network elements within an operations controller (OPC) span of control, and a summary of the OPC network surveillance tools, see Network Surveillance Procedures, 323-1111-510.

Alarm severity, service code, and protection and activity statusThe alarms are classified into four severity levels: Critical (C), Major (M), minor (m), and warning (w). These classifications indicate the level of office alarm raised. Each alarm point has a default severity level.

Critical and major alarms are represented by red lamps at the shelf and bay levels, while minor alarms are represented by yellow lamps. There are no lamps for warnings, but the warning indication appears on the user interface screens.

Critical Critical alarms are the most severe alarms. Unprotected optical-line failures and unprotected service-carrying circuit pack failures are examples of critical alarms.

Major Major alarms correspond to failures that are not as severe as critical alarms. Low-speed (DS3 rate or lower) tributary failures or configuration alarms such as a missing interface circuit pack are examples of major alarms.


1-2

Alarm reporting and surveillance

Minor Protected circuit pack failures, common-equipment circuit pack failures, and exceeding performance-monitoring thresholds are examples of minor alarms.

Warning A warning indicates a condition that needs investigation but is not as severe as a minor alarm. A switch-complete indication or the detection of a maintenance signal (for example, an alarm indication signal [AIS]) are examples of warnings.

Service code Alarms of all severity levels are also assigned a service code that indicates if the alarm is service affecting (SA) or not service affecting (NSA). For example, an unprotected optical unit failure is reported as SA, while a protected optical unit failure is reported as NSA.

Protection and activity statusThe alarm severity and service code often differ according to whether the equipment or facility is protectable. If a fault appears on an equipment or facility that is either carrying traffic or providing timing, and the traffic or timing is not switched automatically to the protection equipment or facility, then the failed equipment or facility is unprotectable. In this case, the fault exists on the active equipment or facility.

If the traffic or timing is switched to the protection equipment or facility, then the equipment or facility is protectable. In this case, the fault exists on the inactive equipment or facility.

The protection equipment or facility is not available under the following conditions: during protection lockout; if not installed; if providing protection to another equipment or facility; if out of service; or if failed.

Time filteringThe OC-3 and OC-12 network elements support time filtering of alarms, as specified in Bellcore TR-TSY-00253. Time filtering means that an alarm condition must be present for a predetermined amount of time before the alarm report is generated. A predetermined amount of time has elapsed after the alarm clears. For further information, see Alarm and Trouble Clearing Procedures, 323-1111-543.

Local alarm indications The OC-3 and OC-12 network elements provide local alarm indications to simplify locating the source of a problem. There are bay, shelf, and unit level alarms available at a network element. All of these local alarm indications are controlled either by hardware, that is by the circuit pack itself, or by software through the shelf processor.



1-3

Bay alarms The bay alarms are indicated with colored lamps on the breaker interface panel (BIP); see Figure 1-1. The critical and major alarms are indicated with individual red lamps and the minor alarm by a yellow lamp. These lamps are labelled and indicate the presence of an alarm within that bay.

These alarms are also available as office alarms. There are three Form-C relay contacts for audible alarms and three Form-C relay contacts for visual alarms. An illuminated pushbutton switch enables the alarm cutoff (ACO) for the audible alarms only. The visual alarms cannot be cut off.

Figure 1-1Bay alarms on the breaker interface panel (BIP)

FW-0142.1

Shelf alarms The shelf alarms are indicated with colored lamps on the local craft access panel (LCAP) directly above each TBM shelf. The LCAP has individual lamps for critical, major, and minor alarms, as well as a pushbutton ACO switch; see Figure 1-2.

Battery A Battery BA 1 A 2 A 3 A 4 B 1 B 2 B 3 B 4

ACO/LTPowerCriticalMajorMinor

I

O

TripI

O

I

O

I

O

I

O

I

O

I

O

I

O

Bay alarms


1-4


Figure 1-2Shelf alarms on the local craft access panel (LCAP)

FW-0143 (OC)

Circuit pack alarms Most circuit packs include one or more light-emitting diodes (LED), which are labeled on the faceplates as an aid to indicating the source of the problem. Generally speaking, the LED colors are defined as follows (see Alarm and Trouble Clearing Procedures, 323-1111-543, for a definition of the meaning of the LEDs for each circuit pack).RedA red LED indicates a probable circuit pack failure, a high temperature condition on the shelf, or an exerciser failure.

GreenA green LED indicates that the circuit pack is in service, and that it should not be removed.

YellowOn a traffic-carrying circuit pack, yellow indicates a loss of signal. On other circuit packs, it indicates that an active lockout or loopback is being performed, that the exerciser is running, or that the circuit pack or shelf is being initialized.

The circuit-pack LEDs are illustrated in Circuit Pack Descriptions, 323-1111-102.

Critical Major MinorACO/LT ESDGround

Cover Flap(Open Position)

Critical Major MinorACO/LT ESDGround

Call IncomingIndicator



1-5

Cooling unit alarmsOn the cooling unit, there are three visual alarm indicators. On the face of each of the three fan modules there is a red fail indicator (see Figure 1-3). The fail indicator on a fan module lights up if the fan in the cooling unit fails.

Figure 1-3Visual indicators on the cooling unit

FW-1925

Remote alarms The alarm information can be accessed remotely from anywhere within the same system, using different interfaces that have connectorized ports on the shelf side interconnect left circuit pack.

Ports are provided for the following: a VT100 user interface; TBOS (Serial E2A) applications; parallel telemetry applications (input latches and output relays); and TL1. Figure 1-4 shows the surveillance interfaces.

In addition to the ports available on each shelf, each OPC is equipped with an Ethernet port. The Ethernet port can be used to connect a graphical terminal (NCD X-Terminal) to the OPC.

These interfaces are described in more detail in “Surveillance interface” on page 3-1. See TL1 Interface Description, 323-1111-190, for details concerning TL1.

Fail indicators

CU PwrA(±), B(±)(see Note)

CUInterface

Note: A second set of cooling unit power connectors (CU Pwr A and B) for thethrough-flow cooling unit (NT4K18BA) is located on the right side of the shelf.


1-6


Figure 1-4Surveillance interfaces

FW-1945(TBM)

OperationsController

OAMBus

Serial Telemetry ports(Alarm Processing Remote)

TBOS(E2A)

RelayOutputs

ExternalCustomer

Inputs

••• ••• ••• •••1 1 11

ParallelTelemetry Out

ParallelTelemetry In

Printer

Modem to Remote Terminal

CNetLAN

EthernetTBM Shelf

Processorcard

MaintenanceInterface

card

18

X.11 TerminalGraphical

User Interface

User InterfacePort 2 (RS-232)

on LCAP

VT100-typeTerminal

orX.25 TL-1interface

orPrinter

User Interface(Local terminalVT100-type)

Side Interconnect Left (SIL)card connectors

Side InterconnectLeft (SIL)

card connectors

OPCPort 1


User Interface(Local Terminal

VT100-type)

OR

OR

X.25 TL-1interface


card connectors (Note)

OPCPort 2

Note: OPC Port 2 is not available if the NT7E24AA or NT7E24BA OPC circuit packs are used.OPC Port 2 is available in a TBM shelf provided the OPC is equipped in slot 5.



1-7

Alarm reportingAlarm points are divided into three classes: facility alarms, equipment alarms, and environmental alarms (see Table 1-1).

Facility alarms monitor the signals being carried, while equipment alarms monitor the circuit packs processing the signals. Environmental alarms are raised in the event of a fan failure or a high-temperature alarm, 48-V battery supply, as well as external customer inputs (for example, an open door or a fire alarm) or remote alarms.

The alarm reporting feature supports the correlation of multiple alarms that indicate the same failure. All alarm indications are also screened through a hierarchy to eliminate related alarm indications. In general, only one alarm report is generated.

Alarm hierarchy Alarms are screened through a hierarchy to eliminate related alarm indications. In all hierarchies, if a higher-level alarm point is raised, the lower-level alarm points are masked. For the facility alarm class, Figure 1-5 gives the complete hierarchy of those alarms. Examples follow for each alarm class.

Table 1-1Alarm classes and types

Facility alarms Equipment alarms Environment alarms

COMM CE (common equipment) (shelf) CE (common equipment) (shelf)

DS1 DS1 Input

DS3 DS3 REMT (remote)

ESI ESI (external synchronization interface)

OC3/OC12 (OC-3/OC-12)

Lpbk (loopback)

REMT (remote) MIC (maintenance interface controller) circuit pack

STS-1 OC3/OC12

OC12

OPC

Proc (processor)

REMT (remote)

STS1 (STS-1 electrical interface)


1-8


Facility alarm hierarchy In general, the facility alarm identifies the nature of the failure (for example, loss of frame, LOF), and the facility affected (for example, DS1).

DS1 or DS3 facility example A loss of frame (LOF) is detected and the alarm point is raised. A failure in an external piece of equipment results in DS1 or DS3 AIS being sent into the shelf. However, the Rx AIS alarm is not reported due to the higher-level LOF alarm.

OC-3 or OC-12 facility example An AIS is detected on the OC-3 or OC-12 facility and the alarm point is raised. A loss of signal (LOS) is then detected. The line AIS alarm is cleared and the LOS alarm is asserted. When the LOS condition is cleared, the OC-3 or OC-12 line is monitored to determine if lower-level alarms are present (for example, loss of frame, or signal degrade).



1-9

Figure 1-5Facility alarm hierarchy

FW-2040 (TBM R11 Ph1)

STS1 Rx Unequipped

Optical Source

Rx LOS

LOF

Signal Fail

Line RFI

STS1 Rx LOP

STS1 Rx AIS (path)

OC-3 or OC-12 Facility

DS3 Source

Loopback

Rx BPV

Rx LOF

Rx AIS (path)

Rx Yellow

VT Rx AIS

VT Rx Unequipped

VT Rx LOP

DS1 Source

Rx LOS

Rx BPVRx AIS (path)

DS1 Facility

Rx AIS (line)

VT Path RFI

STS1 SLM

Tx LOF

Rx LOF

Rx Yellow

Tx AIS (path)

Path Facility

Loopback

Signal Degrade

Rx LOS

Rx LOS

Rx LOF Rx BPV

Rx Line AIS

Rx RFI

Loopback

STS1 Facility

STS1 Source

Rx LOP

Rx Path AIS

STS1 Rx PTF

STS1 Path RFI

Path Facility orDS3 Facility

DS3 Facility

Freq OOR


1-10


Equipment alarm hierarchy In general, the equipment alarm identifies the nature of the failure (for example, circuit pack mismatch) and the equipment affected (for example, optical interface circuit pack). The hierarchy of the three common alarms to all circuit packs (except the processor circuit pack) is indicated in Figure 1-6, with examples following.

All facility alarms are masked by equipment alarms except for the Protection path fail and Switcher circuit pack missing (for DS3 only) alarm points. The Protection path fail alarm point is reported by a working circuit pack, to inform the craftsperson of a problem with the protection.

Figure 1-6Equipment alarm hierarchy

FW-2118

DS1 or DS3 equipment example A failed DS1 VT mapper circuit pack is inserted by mistake into a slot provisioned for a DS3 STS mapper. A Circuit pack mismatch alarm is raised; the Circuit pack failure alarm is not raised because it is lower in the hierarchy.

OC-3 or OC-12 equipment example If the optical laser and photo detector fail on an OC-3 or OC-12 optical interface circuit pack, two alarms are raised: an optical-laser failure alarm and an OC-3 or OC-12 optical interface component failure alarm. Both alarms are raised because they are on the same level in the hierarchy.

Circuit packmissing

Circuit packmismatch

Circuit packfail



1-11

Common equipment and environmental alarm hierarchy The OPC, MIC and ESI, falling under the common equipment category, also have three alarms and the hierarchy is indicated in Figure 1-6. The processor circuit pack is also considered common equipment but does not have these three alarms. The environmental alarms are all on the same level of hierarchy and therefore do not mask each other. Examples of these alarms follow.

Common equipment alarm example A serial telemetry port failure is detected by the MIC and this alarm is raised. There is then a failure on the MIC. The MIC Circuit pack fail alarm is generated and the Serial telemetry port fail alarm disappears because it is masked by the MIC failure alarm.

Environmental alarm example An external alarm input (telemetry latch) is activated, but the alarm is not reported because the MIC is missing. The telemetry latch alarm is raised as soon as the MIC is inserted in the shelf.

Control architecture All network elements within the same system are linked through the standard SONET section, line, and path overhead (see Figure 1-7). The processor circuit pack collects all the alarm information from the circuit packs, then processes this information to convert it into the proper SONET overhead and to make it available to the surveillance interfaces. The processor also accepts the overhead information from other network elements and makes it available to the local surveillance interfaces.


1-12


Figure 1-7Overhead layers

FW-0022 (OC)

LineTerminatingEquipment

LineTerminatingEquipment

PathTerminatingEquipment

PathTerminatingEquipment

Regenerator

SONETTerminal

Section

Line

Path(end-to-end)

TxRx

(FW-0022)

(example:multiplexer)


2-1

Log report description 2-Log reports are sources of information about changes of state or other significant events in a TBM network element (NE) or an operations controller (OPC). Typically, the logs are intended to convey information about the event. However, in some cases, the log indicates a problem or provides additional information to alarm reports that also result from a particular problem.

Logs are generated by either the network element or by the OPC. As well as collecting and archiving all logs generated by itself (or the backup OPC), the OPC collects and archives all logs generated by the network elements within its span of control. Each network element stores a certain number of its own logs in the appropriate one of a series of log buffers (one buffer for each type of NE log).

For a complete listing and description of TBM NE and OPC logs, see Log Report Manual, 323-1111-840.

Numbering schemeAll logs are followed by a number that ranges from 300 to 999. The number indicates the general nature of the event being logged as shown in the following chart. FAC and EQP logs in the 300 series require follow-up action. All other logs are for information only.

300 to 399 Trouble indicates a problem

400 to 499 Usage indicates the use of a resource or service

500 to 599 State change indicates a significant change in status

600 to 699 Completion indicates that a process has been completed

700 to 799 Progress indicates that a process is underway

900 to 999 Software error indicates that a software error has been detected


2-2 Log report description

NE logs The NE event logs are divided into user logs and system logs. The log reports provide indications on a particular event, such as the location, the time, and the type of problem, as well as supplementary information to help in fault locating and troubleshooting. See the procedures on monitoring NE logs in System Administration Procedures, 323-1111-302.

The user log categories are as follows:

• Communication (COMLOG or COML): events related to communication between NE-to-NE and NE-to-OPC.

• Communication Addressing (COADDR or COAD): events related to Data Comm Address provisioning

• Download (DLD): events related to downloading firmware to the network element

• Equipment (EQP): events related to circuit packs, circuit pack groups, common equipment, shelf, and frame hardware.

• Event (EVNT): events related to internal routing of event reports. The event reports can be alarms, logs, and attribute changes.

• Facility (FAC): events related to facility provisioning (create, delete, state change, and parameter editing).

• Fault (FLT): events related to equipment faults that cause circuit pack failure.

• Database (FWDB): events related to FiberWorld NE database operations. These operations include database backup, database restore, and journal entry.

• Host Messaging Unit (HMU): events reported by the HMU processor on the processor circuit pack (Proc). These events include errors detected by HMU software, HMU restart, HMU sanity time out, and HMU software errors. In the case of software errors (HMU901), contact your next level of support or your Nortel Networks support group.

• Network element (NE): events related to the creation, deletion, or modification of a NE.

• Remote (REMT): events related to the connection status between the OC-3/OC-12 system and the remote node.

• Security (SECU): events related to network element security.

• Software events (SOFT): events related to a change in the normal operation of the software

• Software errors (SWERR and TRAP): events related to internal software operation. Report any SWERR or TRAP log raised to Nortel Networks support group.


Log report description 2-3

• Transport control subsystem firmware (TCSF): events related to firmware errors on the OC-12 Virtual Tributary Bandwidth Management Optical Interface circuit pack (NT7E05)

The system logs contain information related to internal software audits and file or message transfers between software applications. System log categories and log severity categories are as follows.

The following is an example of an EQP log report.

NE event logger The event logger is a feature that records all significant events in the NE. The logs are captured in buffers on the Proc, and can be viewed through the network element user interface. The logs can also be routed to a printer, if required.

ACTSYS

ASNILOG

BMS

CLIN

DECR

FREQ

FPRT

INFO

INIT

ISYSLOG

ISYSLOG1

MTS

SAVLOG

SOS

STOR

SWERR

SYSLOG

SYSLOG1

TPS

TRAP

log number

date

log typetime

reportnumber

event typeINFO: informationFAIL: alarm or failure

event

EQP501 FEB13 14: 15: 29 5103 INFO EQP State Change

Object Class: Circuit Pack GroupPresent State: ISPrevious State: OOS

NE: 12 Ring5 LOCATION: 1 TORONTO EQP: 1 OC12 RingADM SHELF POS: 1 SHELF: 1 CPG: OC12 G1S SLOT: 11 PEC: NT7E02KC

description location



The event logger buffer stores event messages according to the category and shelf. The number of event messages that can be stored in the allocated buffer before the buffer entries are overwritten varies with the size of the individual event logs. The following table shows estimates of the number of log entries (for each category) that can be stored in each log buffer before overwriting occurs.

OPC logs All OPC logs are considered user logs. Their categories are as follows:

• Communication (COM): communication events between the NEs and the OPC.

• General (GEN): general OPC system-level events.

• Network administration and surveillance (NAD): events associated with the administration and surveillance of the system.

Log category

Minimum quantityof entries

Maximum quantityof entries

COAD 35 35

COML 42 73

DLD 86 86

EQP 13 124

EVNT 26 42

FAC 33 99

FLT 21 21

FWDB 16 64

HMU 21 21

NE 10 46

REMT 6 6

SOFT 18 18

SWERR 20 20

TCSF 18 24

TRAP — —

Note: These numbers are estimates only; they can vary by ±2 entries.


Log report description 2-5

• Software and data administration (SDA): events dealing with the installation and distribution of software loads to NEs, and the backup and restoration of the network element data.

• Security (SEC): events related to OPC security.

• Standby (STBY): events concerning the status of the primary and backup OPCs.

OPC event browser The event browser is a feature used to browse the history of logs, alarms, and alerts for the OPC, and to display or print the detailed information about individual events.


3-1

Surveillance interface 3-This chapter describes the different alarm and surveillance interfaces available with the OC-12 and OC-3 network elements (NEs). For more information, see System Description, 323-1111-100. For details on the Transaction Language 1 (TL1) interface, see TL1 Interface Description, 323-1111-190.

Operations controller The operations controller (OPC) is the core element of the OC-12 and OC-3 network elements: the operations, administration, maintenance, provisioning (OAM&P), and the overall system control.

OPC network communication The OPC maintains intranetwork element communication to the processor (Proc) circuit pack and maintenance interface controller (MIC) circuit pack through the shelf backplane buses.

Internetwork element communication is maintained through the SONET data communication channel (DCC) embedded in the SONET overhead, and through the associated control network (CNet) interfaces provided on the shelf side interconnect left connector.

OPC network surveillance The network surveillance functions in the OPC module to make it easier to locate a failure in the network.

The OPC module processes and correlates alarms from all sites within its span of control. In addition, the module is able to indicate the originating alarm source all the way down to the replaceable module. The OPC suppresses all other secondary alarms while still logging them, therefore making them available for query.

Another surveillance feature is storing performance monitoring data for each network element in nonvolatile memory on the OPC hard disk. The OPC module also archives OPC alarm/log messages collected for the network elements.


3-2 Surveillance interface

Maintenance interface controller circuit packThe maintenance interface controller (MIC) circuit pack (NT4K53) is one of the essential elements of the OC-12 and OC-3 network element operations, administration, maintenance (OAM), and control systems. It provides ports for the user interface, the TBOS (serial E2A) interface, and external customer inputs and outputs.

Complementary to the OPCs, the MIC circuit pack provides peripheral nonvolatile storage for OAM and provisioning data. The MIC circuit pack activates the protection switching relays for the DS1, DS3, and STS-1 circuit packs. The MIC circuit pack also controls circuit-pack and shelf-alarm indications, as well as the bay alarm lamps, the office relays and the alarm cutoff function. Table 3-1 provides the communication rates supported by the MIC circuit pack.

This section gives details on the different surveillance interfaces that are provided by the MIC circuit pack (see Figure 3-1).

Table 3-1Communication rates supported by the MIC circuit pack

Communication rate (baud) Typical applications

300 Printer

1200 Modem to Remote terminal/printer

2400 TBOS (serial E2A) modem

4800 --

9600 User interface


Surveillance interface 3-3

Figure 3-1Surveillance interfaces supported by the maintenance interface controller (MIC)circuit pack

FW-1945 (TBM)

OperationsController

OAMBus

Serial Telemetry ports(Alarm Processing Remote)

TBOS(E2A)

RelayOutputs

ExternalCustomer

Inputs••• ••• ••• •••1 1 11

ParallelTelemetry Out

ParallelTelemetry In

Printer

Modem to Remote Terminal

CNetLAN

EthernetTBM Shelf

Processorcard

MaintenanceInterface

card

18

X.11 TerminalGraphical

User Interface


on LCAP

VT100-typeTerminal

orX.25 TL-1interface

orPrinter

User Interface(Local terminalVT100-type)

Side Interconnect Left (SIL)card connectors


card connectors

OPCPort 1


User Interface(Local Terminal

VT100-type)

OR

OR

X.25 TL-1interface


card connectors (Note)

OPCPort 2

Note: OPC Port 2 is not available if the NT7E24AA or NT7E24BA OPC circuit packs are used.OPC Port 2 is available in a TBM shelf provided the OPC is equipped in slot 5.



User interface CRT The user interface provides detailed network information and operational control, and allows technicians to perform provisioning, troubleshooting, and maintenance operations. Extensive alarm information is available at different levels, from individual circuit packs to network elements. This information facilitates fault location and troubleshooting.

Intersite communication makes the user interface one of the most powerful surveillance tools available for any network. Figure 3-2 gives a typical example of how the user interface can monitor a system locally, or remotely, through a modem.

The OC-12 and OC-3 network elements offer a simple and efficient way to monitor and control a transmission network by using an inexpensive VT100 compatible terminal. The maintenance interface controller (MIC) circuit pack provides two dedicated RS-232 ports, a data communications equipment (DCE) port on the local craft access panel (user interface port 2) for local terminal applications, and a data terminal equipment (DTE) port on the side interconnect left (SIL) circuit pack (user interface port 1) for remote applications.

Direct access to the OPC is also possible through the associated user OPC port 1 interface provided on the SIL. In general, the user can access the OPC by way of the RS-232 ports provided through the MIC circuit pack.

X.11 terminal The OPC module supports one input/output interface on its front panel. This interface, a standard Ethernet 802.3 LAN, is offered to provide an interface for X.11 terminals and other such Ethernet devices. The X.11 type terminals allow the simultaneous viewing of multiple network elements and multiple OPC tools by using the windowing capabilities of the X.11 terminal.

The same functionality as the OPC VT100 user interface is provided with the X.11 terminal. In addition, OPC-to-OPC login is supported, allowing users to view multiple subnetworks from a single X.11 terminal.



Figure 3-2User interface applications

FW-1950

RemoteUser Interface

(VT100 Compatible)RS-232

Modem

Terminal

DS1/DS3

Terminal

RS-232

DS1/DS3

RS-232

LocalUser Interface

(VT100 Compatible)

Remote Surveillance Center

GraphicalUser Interface(X.11 Terminal)

Printer

Modem

RS-232

LTE LTE

Ethernet



Serial telemetry (TBOS) The serial telemetry feature (telemetry bit-oriented serial [TBOS] feature) provides a simple and reliable means of transmitting alarm surveillance and control data between monitoring and monitored equipment. In this case, the feature provides remote monitoring and control capabilities of the SONET network elements from remote monitoring centers, or possibly operations support system (OSS) agents.

Communications between the remote monitoring center and the monitored SONET network element is carried over a four-wire cable, as shown in Figure 3-3. The protocol being transmitted over the four-wire cable is the TBOS protocol. This protocol specifies that communications are to be asynchronous, serial, half duplex and at a rate of 2400 baud. Words are transmitted in ASCII format with one start bit, eight data bits, one odd-parity bit, and two stop bits. The serial word format composition is as follows.

SONET network elements support the TBOS protocol and the alarm processing remote (APR) application, which implies that the physical cable is connected to an E2A alarm processing remote located at the remote monitoring centre. The cable terminates at the RS422 connector located on the side interconnect left circuit pack on the TBM shelf.

The remote monitoring center initiates separate requests for command execution and scan requests for indication information retrieval. The SONET network element must reply to all error-free requests for command execution, or scan requests for indication information within 200 ms. Any requests containing detectable errors are ignored and no reply is returned. (Any requests containing undetectable errors are treated as error-free commands and replies are sent regardless.)

Each of the two physical interface ports can accommodate up to eight mapping positions. The user can assign one of the predefined 64-bit TBOS displays to any of the eight mapping positions for each port. The displays are selected using the network element user interface, from a set of predefined displays, as

0 1 1

0 1 2 3 4 5 6 7 8 9 10 11

StartBit

Character Odd StopBitsParity



described in Table 3-4 to Table 3-17 on page 3-17 through page 3-52. Setting parameters of the network element user interface ports is described in System Administration Procedures, 323-1111-302.

Figure 3-3RS-422 port

FW-0047

TBOS displays There are three types of displays: monitor, control, and remote.

• Monitor displays keep track of status and alarm information of a single network element and map a single bit within a display to an alarm point or status point.

• Control displays map a single bit within a display to an executable command. A remote display can be either a network level (one OPC span of control) summary display or an individual network element summary display.

• Remote displays are described in the“Remote telemetry” section on page 3-14.

TBOS(serial E2A)

Alarmprocessing

remote

120 Ω RS-422receiver

RS-422driver

TransportNode network elementmaintenance interface

TBOS port drivers (one port shown)

Transmit +

Transmit -

Receive +

Receive -



The 64-point assignments of the monitor and control displays are provided in Table 3-4 through Table 3-16 on pages page 3-17 through page 3-48. The Network Summary display (Remote display 1) is described in Table 3-17 on page 3-52.

Each TBOS port has eight mapping positions. The displays assigned to these mapping positions can be any combination of monitor, control, and remote displays. The assignment of the local monitor and control displays to a TBOS port is done through the network element user interface. (Setting serial telemetry ports and displays with the network element user interface is described in System Administration Procedures, 323-1111-302.) The assignment of the Remote displays is done with the OPC user interface. (Mapping remote TBOS ports is described in System Administration Procedures, 323-1111-302).

The monitor, control, and remote displays are predefined and are not user-modifiable. That is, a particular bit within a given display always reflects the status of the same alarm or executes the same command.

Note: Not all TBM alarms are displayed on the monitor displays. For a list of these alarms, see “Alarms not displayed on the monitor displays” on page 3-54.

All monitoring points are considered as having the property of alarm with memory. That is, all monitoring points are raised whenever the associated alarm of status is raised; however, the monitoring points are cleared when the monitoring points are scanned after the alarm condition is cleared. This will ensure that the monitoring system will not miss any transient alarms that may exist for a shorter duration than the polling period.

Alarm with memory is available for a given display according to each port. That is, a given display must only be assigned to one mapping position on the same port. If the same display is assigned to more than one mapping position for the same port, an alarm with memory is not guaranteed.

All TBOS ports have default displays assigned based on shelf function. For the TBM terminal shelf, see Table 3-2. For the TBM regenerator shelf, see Table 3-3. Any default mappings can be altered. (Setting serial telemetry ports and displays is described in System Administration Procedures, 323-1111-302).



Table 3-2 Serial telemetry mapping position for the terminal and ADM shelves (port 1)

Mapping position Display TBOS display default

1 Monitor 1 TBM network element

2 Monitor 2 Telemetry overview

3 Monitor 3 Equipment indications

4 Monitor 4 DS1 facility indications, and OC-3/OC-12/STS-12 secondary transport activity

5 Monitor 5 OC-3/OC-12/STS-12/DS1 protection indications, and OC-3/OC-12/STS-12 transport activity

6 Monitor 6 OC-3/OC-12/STS-12/DS3/STS-1 facility protection indications, and OC-3/OC-12/STS-12 transport activity

7 Monitor 7 Parallel telemetry indications

(see Note) Monitor 8 OC-3 optical tributary facility indications

(see Note) Monitor 9 OC-3 optical tributary protection

(see Note) Monitor 10 Maintenance display

8 Control 1 DS1 protection switching, processor restart, exerciser routine, and database backup commands

(see Note) Control 2 OC-3/OC-12/STS-12 and DS3/STS-1 protection switching commands

Note: Not assigned to a mapping position by default



TBOS protocol The TBOS protocol is a simple reliable protocol used for receiving small amounts of alarm surveillance information and transmitting control messages at low data rates. All TBOS command execution and alarm surveillance requests are initiated by the remote monitoring center.

Any request in error can be ignored by the monitored system. Errors include parity or format errors. The monitoring system is expected to reinitiate any request for which an appropriate reply has not been received more than 200 ms after the command was initiated. If a transaction fails three times, the monitoring system declares the serial link as failed and halts serial telemetry over that link.

The first two bits of data within any request are the request OP code. This code determines how the rest of the data within the message is decoded.

Table 3-3Serial telemetry mapping position for the regenerator shelf (port 1)

Mapping position Display TBOS display default

1 Monitor 1 TBM network element

2 Monitor 2 Telemetry overview

3 Monitor 3 Equipment indications

4 Monitor 7 Parallel telemetry indications

5 Monitor 8 OC-3 optical tributary facility indications (see Note)

6 Unassigned

7 Control 1 Shelf control

8 Control 2 Output control

Note: This display is currently not in use on TBM regenerators.

OP code Description

00 TBOS Scan Request

01 TBOS Command Request (message 1)





TBOS scan request A TBOS scan request is initiated by the remote monitoring system and requires the monitored system to send the character within the display identified in the scan request. The data within the reply reflects indication information: whether a specific indication is currently raised, or a specific indication is presently active.

The monitored system is expected to reply with the status character within 200 ms. The monitoring system is expected to then resend an identical request to the monitored system and the monitored system is expected to reply within 200 ms with the same status character. (The monitored system simply buffers the last character sent and resends this data when the identical request is received.) Even though the indication information might have changed between the first and second requests (indication might have been raised or lowered), the reply for the second request must be identical. If the monitoring system does not resend an identical request, the internal buffer is simply flushed and normal processing resumes.

Because the state of each point within a TBOS display is Boolean, the points within the monitoring display can only be used to indicate the following:

• whether a given indication is currently raised

• whether a particular object is in a certain state

The following diagrams show the scan request and reply formats

Scan request

The proper reply consists of the character of the display implied by the mapping position number and the character index supplied in the command.

0 0 0 MSB LSB MSB LSB 1 1

0 1 2 3 4 5 6 7 8 9 10 11

Start Character Odd StopBit

RequestOPcode No.

MappingPosition No.

<00> 000 = Pos 1001 = Pos 2010 = Pos 3011 = Pos 4100 = Pos 5101 = Pos 6110 = Pos 7111 = Pos 8

000 = Char 1001 = Char 2010 = Char 3011 = Char 4100 = Char 5101 = Char 6110 = Char 7111 = Char 8



All error-free requests must be replied to appropriately within 200 ms. Bits within the character portion of all replies are time-order reversed. (The character bits, B1, B2, B3, B4, B5, B6, B7, and B8 are backwards; see the following diagram.)

Scan response

TBOS command request A TBOS command request is initiated by the remote monitoring system and requires the monitor system to execute the specified command identified in the command request. The entire command sequence requires three words to be transmitted and replied to. The reply echoes the command request (with the character bits being time-order reversed). Command request message 1, 2, and 3 formats are shown in the following diagrams.

Command request (message 1)

0 B8 B7 B6 B5 B4 B3 B2 B1 Parity 1 1

0 0 1 MSB LSB 0 • • 1 1

0 1 2 3 4 5 6 7 8 9 10 11

Start Character Odd StopBit Parity Bits

0 1 2 3 4 5 6 7 8 9 10 11

Start Request Odd StopBit

RequestOPcode Type

MappingPosition No.

<01> 000 = Pos 1001 = Pos 2010 = Pos 3011 = Pos 4100 = Pos 5101 = Pos 6110 = Pos 7111 = Pos 8

11 = Not used10 = unlatch/release01 = latch/operate00 = momentary





The monitored system (S/DMS TransportNode network element) must reply to each message in the command sequence within 200 ms. The next message in the command sequence should be received in about 10 ms: the next message can be sent by the monitoring system (customer-owned TBOS monitoring system) in as much as 80 ms.

The first and second messages in the command request sequence uniquely define which mapping position and which command is executed. The third message in the command request sequence is the same for all command requests and is identified by OPcode 11 followed by bit string 001100.

Two bits within the first message indicate the request type.

0 1 0 MSB LSB 1 1

0 1 1 0 0 1 1 0 0 1 1

0 1 2 3 4 5 6 7 8 9 10 11

Start Odd StopBit

RequestOPcode <10>

Parity BitsRemote Command Number

000000 = Command No. 1000001 = Command No. 2000010 = Command No. 3

• • •• • •

111111 = Command No. 64

Command Response (Message 2) - Echo of Request

0 1 2 3 4 5 6 7 8 9 10 11

Odd StopRequestOPcode <11>

Parity BitsExecute Code <001100>Start

Bit

Command Response (Message 3) - Echo of Request



The request type applies to commands that cause something to toggle. For example, a lockout on a DS3 circuit pack can be operated or released. Rather than describing these commands as two separate events, a combined command (described as a DS3 circuit pack lockout for a particular circuit pack) is defined, and the request type is used to indicate the desired operation.

Momentary is used for commands that do not have a specific operate or release function. Functions which use momentary are those that should run until completion, for example, performing a database backup to the OPC.

Remote telemetry This feature provides the necessary management of TBOS displays and the TBOS port for centralized surveillance using serial telemetry. Centralized serial telemetry minimizes the number of wires needed between the monitoring equipment and the network elements.

The Remote Telemetry tool on the OPC allows the user to assign displays to any provisioned TBOS port in the OPC span of control. Currently, there are two types of TBOS displays supported by the feature: the Network Summary display and the Network Element Monitor display. When either of these displays is received by a surveillance network element, the display appears as “Remote” on that network element. “Remote” control displays are not presently supported by this feature.

Network summary display (Remote network telemetry)This display allows for delivery of network-wide (within an OPC span of control) telemetry indications. The Network Summary display is described in Table 3-17 on page 3-52.

Five network telemetry indications are provided. These indications reflect the presence or absence of any Critical, Major, minor, and warning alarms in the network and the communication status between the OPC and the network elements. This telemetry information is consolidated into a single Serial Telemetry (TBOS) display called the Network Summary display.

The first four points within the TBOS display indicate if an alarm of a certain severity is present in the network. These points reflect the presence or absence of any Critical, Major, minor, and warning alarms in the network.

Request Type Description

00 Momentary

01 Latch/Operate

10 Unlatch/Release

11 Unused



The fifth indication reflects the current status of the OPC/network element communication and critical OPC resources required for Remote Telemetry. If any communication or resource is unavailable for any reason, the “Counts Inaccurate” indication is set to 1 (or ON).

This display appears as a “Remote Display 1” at the receiving network element. For more information, see the chapter on mapping remote TBOS ports in System Administration Procedures, 323-1111-302.

Network element monitor display The network element monitor display is a copy of local monitor display 2. This monitor display is a summary display of the network element status and is described in Table 3-5. For more information, see the chapter on mapping remote TBOS ports in System Administration Procedures, 323-1111-302.

The feature allows the routing of the monitor display 2 owned by one network element (referred to as the source network element) to any other network element (referred to as the destination network element). The source and destination network elements must be located within the same OPC span of control.

At the destination network element, the received monitor display appears as “Remote Display N”, where N ranges from 3 to 32. The exact identification number is indicated by the user interface.

Network application A typical network application would be to extend the monitor display 2 of each network element in the OPC span of control, as well as the Network Summary display to a designated surveillance network element. E2A TBOS monitoring equipment can then be used to monitor the network using serial telemetry (see Figure 3-4).

Using the remote telemetry tool, a particular display can be routed only once to an individual network element. Also, each particular display can be assigned to a maximum of two network elements within the OPC span of control.



Figure 3-4Example of a centralized serial telemetry surveillance center

FW-2004

Remote parallel telemetry Direct support of network parallel telemetry is not part of the Remote Telemetry feature. However, through functions supplied by this feature and provisioning from the network element user interface, limited remote parallel telemetry is available.

By routing the monitor display 2 with the Remote Telemetry tool, parallel inputs and outputs of the source network element can be monitored by the receiving network element. Also, by using the network element user interface, any alarm points of the received Remote display can be assigned to drive a parallel telemetry output point. For example, a direct link can be established between an external input point of one network element and an external output point at the surveillance network element receiving the remote monitor display 2.

Since this feature assigns remote displays on TBOS mapping positions, the surveillance network element must have at least one TBOS port provisioned even if surveillance only occurs through parallel telemetry. In that case, the TBOS port does not require a serial link connected to it. For more information, see the chapter on mapping remote TBOS ports in System Administration Procedures, 323-1111-302.

S/DMSTransportNode

OPC

NE #1

S/DMSTransportNode

NE #2

S/DMSTransportNode

NE #7

Monitor 1

Monitor 3

Monitor 2 of NE #2

Monitor 2 of NE #4

Monitor 2 of NE #8

Monitor 2 of NE #12

Monitor 2 of NE #11

Network summary display

8 displaysmaximum

Telcomonitoringequipment

RS-422 link

TBOS port

Localdisplays

Remotedisplays



Impact of communications losses between OPC and network elements If communications are lost between the OPC and a particular network element, the following conditions result:

• no remote provisioning of displays related to this network element can be performed until communications are reestablished

• the display monitor 2 or any information related to this network element is not updated anywhere until communications are reestablished

• the remote displays, mapped to an active TBOS of this network element, are not updated until communications are reestablished

• the Network Summary display does not correctly display the alarms and status of this network element and those downstream. The downstream network elements receive a questionable Network Summary display. However, the “Counts Inaccurate” indication point in the Network Summary display is set to 1 (or ON) to reflect this communication problem. The only reliable remote displays are those in which the source and destination network elements are in the upstream system.

The “Counts Inaccurate” alarm point in the Network Summary display is not set to one at the network element that lost the association with the OPC. A separate indication point (OPC-Network Element Association Down) is available to reflect the communication status with the OPC. If this indication is set to 1 (or ON), the OPC is unable to “deliver” any display to this network element. The current content of the remote displays present in this network element can then be considered questionable. This local Serial Telemetry display point is available in display Monitor 1, byte 8, bit 5.

During a network split, all the provisioning done with this feature at the backup OPC is not retained after communication is reestablished and the primary OPC takes over. When the primary OPC becomes active, any new remote display assignments performed with the backup OPC appear as “unknown.” All “unknown” assignments must be deleted and reprovisioned, if required.

Table 3-4 Monitor display 1—TBM network element

Point Byte Bit Description

1 1 1 Critical alarm in the Fac category

2 1 2 Major alarm in the Fac category

3 1 3 Minor alarm in the Fac category

4 1 4 Warning alarm in the Fac category

5 1 5 Critical alarm in the Eqp category

6 1 6 Major alarm in the Eqp category



7 1 7 Minor alarm in the Eqp category

8 1 8 Warning alarm in the Eqp category

9 2 1 Critical alarm in the Env category

10 2 2 Major alarm in the Env category

11 2 3 Minor alarm in the Env category

12 2 4 Warning alarm in the Env category

13 2 5

14 2 6

15 2 7

16 2 8

17 3 1

18 3 2

19 3 3

20 3 4 Any OC-12 alert

21 3 5 Any OC-3 alert

22 3 6

23 3 7

24 3 8 Any STS1 alert

25 4 1 Any DS3 alert

26 4 2 Any DS1 alert

27 4 3

28 4 4

29 4 5

30 4 6

31 4 7

32 4 8

33 5 1

34 5 2

Table 3-4 (continued)Monitor display 1—TBM network element




35 5 3

36 5 4

37 5 5

38 5 6

39 5 7

40 5 8

41 6 1 OC-3/OC-12 protection fail

42 6 2 OC-3/OC-12 protection active

43 6 3 OC-3/OC-12 active lockout

44 6 4

45 6 5

46 6 6

47 6 7 DS3/DS1/STS1 protection fail

48 6 8 DS3/DS1/STS1 protection active

49 7 1 DS3/DS1/STS1 active lockout

50 7 2

51 7 3

52 7 4

53 7 5

54 7 6

55 7 7

56 7 8

57 8 1

58 8 2

59 8 3

60 8 4

61 8 5 Local NE-OPC association down

62 8 6 Alarm of any severity is raised





63 8 7 Alarm of severity Critical, Major, or minor is raised

64 8 8 Reserved

Note: When STS-12 electrical interface circuit packs are used instead of OC-12 optical interfaces, alarms and other indications appear as type OC-12, and are reported as such by TBOS.

Table 3-5 Monitor display 2—telemetry overview


1 1 1 Any OC-3/OC-12 equipment fail

2 1 2 Any OC-3/OC-12 LOS/LOF

3 1 3 Any OC-3/OC-12 line AIS detected (not for regen)

4 1 4 Any OC-3/OC-12 protection switch completed (not for regen)

5 1 5 Any OC-3/OC-12 protection switch fail (not for regen)

6 1 6 Any OC-3/OC-12 protection lockout (not for regen)

7 1 7 Any OC-3/OC-12 PM threshold 1 crossed

8 1 8 Any OC-3/OC-12 PM threshold 2 crossed

9 2 1 Any OC-3/OC-12 protection path fail (not for regen)

10 2 2 Any DS3/STS1 protection path fail (not for regen)

11 2 3 Any DS1 protection path fail (not for regen)

12 2 4 Any OC-3/OC-12 signal degraded

13 2 5 Any OC-3/OC-12 FERF

14 2 6 Any common equipment failure or environment alarm (Fan fail, Breaker trip, High temperature)

15 2 7 Any OC-3/OC-12 indication

16 2 8 Any DS1 or DS3/STS-1 indication (not for regen)

17 3 1 DS3/STS1 equipment fail (not for regen)

18 3 2 DS3/STS1 LOS, LOF, BPV, or BER (not for regen)

19 3 3 DS3/STS1 incoming AIS detected (not for regen)

20 3 4 DS3/STS1 protection switch completed (not for regen)





21 3 5 DS3/STS1 protection switch fail (not for regen)

22 3 6 DS3/STS1 protection lockout (not for regen)

23 3 7 DS3/STS1 PM threshold 1 crossed (not for regen)

24 3 8 DS3/STS1 PM threshold 2 crossed (not for regen)

25 4 1 DS1 equipment fail (not for regen)

26 4 2 DS1 LOS, LOF, BPV, or BER (not for regen)

27 4 3 DS1 line AIS detected (not for regen)

28 4 4 DS1 protection switch completed (not for regen)

29 4 5 DS1 protection switch fail (not for regen)

30 4 6 DS1 protection lockout (not for regen)

31 4 7 DS1 PM threshold 1 crossed (not for regen)

32 4 8 DS1 PM threshold 2 crossed (not for regen)

33 5 1 External Input #1











44 6 4 Any Express Remote Alarm(including First Alert Alarms)

45 6 5

46 6 6 Inter-ring protection switch complete

47 6 7 Tx loss of Inter-ring secondary feed

Table 3-5 (continued)Monitor display 2—telemetry overview




48 6 8 Inter-ring both feeds fail

49 7 1 Any equipment fail

50 7 2 Any LOS, LOF, BPV, or BER

51 7 3 Any AIS detected (not for regen) (see Note 2)

52 7 4 Any protection switch completed (not for regen)

53 7 5 Any protection switch fail (not for regen)

54 7 6 Any protection lockout (not for regen)

55 7 7 Any PM threshold 1 crossed

56 7 8 Any PM threshold 2 crossed

57 8 1 Any alarm of critical severity is raised

58 8 2 Any alarm of major severity is raised

59 8 3 Any alarm of minor severity is raised

60 8 4 Any alarm of warning severity is raised

61 8 5 Any fan failure detected

62 8 6 Any shelf over temperature alarm

63 8 7 Any breaker trip detected (battery fail)

64 8 8 Reserved

Note 1: When STS-12 electrical interface circuit packs are used instead of OC-12 optical interfaces, alarms and other indications appear as type OC-12, and are reported as such by TBOS.

Note 2: TBOS point (51) indicates any of the following STS1 conditions: Rx Path AIS, Rx Line AIS, and Rx RFI.

Legend

PM = Performance monitoringFERF = Far end receive failRFI = Remote Failure Indication

Table 3-5 (continued)Monitor display 2—telemetry overview




Table 3-6 Monitor display 3—equipment indications


1 1 1 DS1 equipment fail alarm, CP G1 (not for regen)












13 2 5 DS1 equipment fail alarm, CP P (not for regen)

14 2 6 (see Note 2)

15 2 7 OC-3/OC-12 equipment fail alarm (see Table 3-7 for CP)

16 2 8 OC-3/OC-12 equipment fail alarm (see Table 3-7 for CP)



17 3 1 OC-3/OC-12 equipment fail alarm (seeTable 3-7 for CP)






23 3 7 OC-3 /OC-12 equipment fail alarm (seeTable 3-7 for CP)

24 3 8 OC-3 /OC-12 equipment fail alarm (seeTable 3-7 for CP)

25 4 1 DS3/STS1 equipment fail alarm, CP G1 (not for regen)




29 4 5 DS3 equipment fail alarm, CP P (not for regen)

30 4 6 Common equipment fail alarm, slot #1















Table 3-6 (continued)Monitor display 3—equipment indications










51 7 3 48V Battery A CE Supply fail

52 7 4 48V Battery B CE Supply fail

53 7 5 Power I/O breaker tripped

54 7 6

55 7 7 STS1 equipment fail alarm, CP P (not for regen)

56 7 8 Any ESI reference alarm

57 8 1 Fan #1 fail

58 8 2 Fan #2 fail

59 8 3 Fan #3 fail

60 8 4 High temperature at common equipment shelf

61 8 5 High temperature at fan units

62 8 6 Oscillation protection activated

63 8 7 Communication failed (LAPD/CNet/Ethernet LOS)





64 8 8 Reserved


Note 2: Point 14 is raised when any of the following alarms occur: Eqp CE Autoprovisioning mismatchEqp CE Database not restored. Type Q APPROVE at NEEqp CE Software trapEqp DS3 P Protection hardware incompatibleEqp DS3 VT connection provisioning mismatchEqp Lpbk LpbkG1 Protection switching byte failEqp Lpbk LpbkG1S Protection switching byte failEqp Lpbk LpbkG1 Maps invalid or missingEqp Lpbk LpbkG1S Maps invalid or missingEqp Lpbk Ring protection suspended or unavailableEqp OC12 Protection switching byte failEqp OC12 Channel match failEqp OC12 Transmission rate mismatchEqp OC12 Switch mode mismatchEqp OC12 Protection scheme mismatchEqp OC12 Invalid neighbour detectedEqp OC12 VT connection provisioning mismatchEqp OC12 Firmware trapEqp Shelf Exerciser failEqp Shelf Ring reconfiguration in progressEqp STS1 VT connection provisioning mismatch

When this TBOS point is triggered, not enough information can be conveyed through TBOS to adequately diagnose the problem. Check actual alarm through the user interfaces to further isolate the alarm. See Alarm and Trouble Clearing Procedures, 323-1111-543.

Legend

CP = circuit pack





Table 3-7Monitor display 3—Circuit pack identification for points 15 to 24

Monitordisplay point

Terminal NE or VTM ring ADM NE

ADM NE NWK ring ADM NE Regenerator NE

CP Application CP Application CP Application CP Application

15 G1 OC-3/OC-12/STS-12 interfaces

G1 OC-3/OC-12/STS-12 interfaces

G1 OC-12/STS-12 interface

G1E OC-12 interface

16 G2 G2 LpbkG1 OC-12/STS-12 loopback

17 G1S OC-3 tributaries

G1S G1S OC-12 interface

G1W OC-12 interface

18 G2S G2S LpbkG1S OC-12 loopback

19 G3 G3 OC-3 tributaries

G3 OC-3 tributaries

20 G4 G4 G4

21 G5 G5 G5

22 G6 G6 G6

23 G7 G7 G7

24 G8 G8 G8

Table 3-8 Monitor display 4—DS1 facility indications, and OC-3/OC-12/STS-12 secondary transport activity


1 1 1 DS1 metallic facility fail, CP G1 (LOS, LOF, BPV, BER)














13 2 5 OC-3/OC-12 Tx active, CP G1S

14 2 6 OC-3/OC-12 Rx active, CP G1S

15 2 7 OC-3/OC-12 Tx active, CP G2S

16 2 8 OC-3/OC-12 Rx active, CP G2S

17 3 1 DS1 line AIS detected, CP G1












29 4 5

30 4 6

31 4 7

32 4 8

33 5 1 DS1 PM threshold 1 crossed, CP G1





Table 3-8 (continued)Monitor display 4—DS1 facility indications, and OC-3/OC-12/STS-12 secondary transport activity











45 6 5

46 6 6

47 6 7

48 6 8













61 8 5

62 8 6

63 8 7 STS1 protection lockout, CP P





64 8 8 Reserved


Legend

BER = bit error rate

BPV = bipolar violation

CP = circuit pack

LOF = loss of frame

LOS = loss of signal

PM = performance monitoring

Table 3-9 Monitor display 5—OC-3/ OC-12/STS-12/DS1 protection indications,and OC-3/OC-12/STS-12 transport activity


1 1 1 DS1 protection switch fail, CP G1












13 2 5 OC-3/OC-12 protection switch fail, CP G1

14 2 6 OC-3/OC-12 protection switch fail, CP G2





15 2 7 OC-3/OC-12 protection switch fail, CP G1S

16 2 8 OC-3/OC-12 protection switch fail, CP G2S

17 3 1 DS1 protection switch complete, CP G1












29 4 5 OC-3/OC-12 protection switch complete, CP G1

30 4 6 OC-3/OC-12 protection switch complete, CP G2

31 4 7 OC-3/OC-12 protection switch complete, CP G1S

32 4 8 OC-3/OC-12 protection switch complete, CP G2S

33 5 1 DS1 protection path fail, CP G1









Table 3-9 (continued)Monitor display 5—OC-3/ OC-12/STS-12/DS1 protection indications,and OC-3/OC-12/STS-12 transport activity







45 6 5 OC-3/OC-12 protection path fail, CP G1

46 6 6 OC-3/OC-12 protection path fail, CP G2

47 6 7 OC-3/OC-12 protection path fail, CP G1S

48 6 8 OC-3/OC-12 protection path fail, CP G2S

49 7 1 DS1 protection lockout, CP G1












61 8 5 DS1 protection lockout, CP P

62 8 6 OC-3/OC-12 Tx active, CP G1 (CP G1E for regenerator)

63 8 7 OC-3/OC-12 Rx active, CP G1 (CP G1E for regenerator)

64 8 8 Reserved


Legend

CP = circuit pack

Table 3-9 (continued)Monitor display 5—OC-3/ OC-12/STS-12/DS1 protection indications,and OC-3/OC-12/STS-12 transport activity




Table 3-10 Monitor display 6—OC-3/OC-12/STS-12/DS3/STS-1 facility protection indications, and OC-3/OC-12/STS-12 transport activity


1 1 1 DS3/STS1 metallic facility fail, CP G1




5 1 5 OC-3/OC-12 LOS, LOF, CP G1 (CP G1E for regenerator)

6 1 6 OC-3/OC-12 LOS, LOF, CP G2 (CP G1W for regenerator)

7 1 7 OC-3/OC-12 LOS, LOF, CP G1S

8 1 8 OC-3/OC-12 LOS, LOF, CP G2S

9 2 1 DS3/STS1 line AIS detected, CP G1 (see Note 2)




13 2 5 OC-3/OC-12 line AIS detected, CP G1

14 2 6 OC-3/OC-12 line AIS detected, CP G2

15 2 7 OC-3/OC-12 line AIS detected, CP G1S

16 2 8 OC-3/OC-12 line AIS detected, CP G2S

17 3 1 DS3/STS1 PM threshold 1 crossed, CP G1




21 3 5 OC-3/OC-12 PM threshold 1 crossed, CP G1


23 3 7 OC-3/OC-12 PM threshold 1 crossed, CP G1S












33 5 1 OC-3/OC-12 FERF, CP G1

34 5 2 OC-3/OC-12 FERF, CP G2

35 5 3 OC-3/OC-12 FERF, CP G1S

36 5 4 OC-3/OC-12 FERF, CP G2S

37 5 5 OC-3/OC-12 signal degrade on CP G1

38 5 6 OC-3/OC-12 signal degrade on CP G2

39 5 7 OC-3/OC-12 signal degrade on CP G1S

40 5 8 OC-3/OC-12 signal degrade on CP G2S

41 6 1 DS3/STS1 protection switch failure, CP G1




45 6 5 DS3/STS1 protection path failure, CP G1




49 7 1 DS3/STS1 protection switch complete, CP G1




53 7 5 OC-3/OC-12 protection lockout, CP G1

54 7 6 OC-3/OC-12 protection lockout, CP G2

Table 3-10 (continued)Monitor display 6—OC-3/OC-12/STS-12/DS3/STS-1 facility protection indications, and OC-3/OC-12/STS-12 transport activity




55 7 7 OC-3/OC-12 protection lockout, CP G1S

56 7 8 OC-3/OC-12 protection lockout, CP G2S

57 8 1 DS3/STS1 protection lockout, CP G1




61 8 5 DS3 protection lockout, CP P

62 8 6 OC-3/OC-12 Tx active, CP G2 (CP G1W for regenerator)

63 8 7 OC-3/OC-12 Rx active, CP G2 (CP G1W for regenerator)

64 8 8 Reserved


Note 2: The STS1 AIS TBOS points (9 to 12) indicate any of the following conditions: Rx Path AIS, Rx Line AIS, and Rx FERF/RFI.

Legend

CP = circuit pack

FERF = far end receive fail

LOF = loss of frame

LOS = loss of signal

PM = performance monitoring

Table 3-10 (continued)Monitor display 6—OC-3/OC-12/STS-12/DS3/STS-1 facility protection indications, and OC-3/OC-12/STS-12 transport activity




Table 3-11 Monitor display 7—parallel telemetry indications


1 1 1 External output (relay) #1


















19 3 3

20 3 4

21 3 5

22 3 6

23 3 7

24 3 8

25 4 1 External input (latch) #1













36 5 4

37 5 5

38 5 6

39 5 7

40 5 8

41 6 1 Inter-ring lockout request

42 6 2 Inter-ring forced switch request

43 6 3 Inter-ring manual switch request

44 6 4

45 6 5

46 6 6

47 6 7

48 6 8

49 7 1

50 7 2

51 7 3

52 7 4

53 7 5

54 7 6

55 7 7

56 7 8

Table 3-11 (continued)Monitor display 7—parallel telemetry indications




57 8 1

58 8 2

59 8 3

60 8 4

61 8 5

62 8 6

63 8 7

64 8 8 Reserved

Table 3-12 Monitor display 8—OC-3 optical tributary facility indications


1 1 1 OC-3 optics fail, CP G3






7 1 7

8 1 8

9 2 1 OC-3 line AIS detected, CP G3






15 2 7

16 2 8

17 3 1 OC-3 FERF, CP G3

Table 3-11 (continued)Monitor display 7—parallel telemetry indications




18 3 2 OC-3 FERF, CP G4

19 3 3 OC-3 FERF, CP G5

20 3 4 OC-3 FERF, CP G6

21 3 5 OC-3 FERF, CP G7

22 3 6 OC-3 FERF, CP G8

23 3 7

24 3 8

25 4 1 OC-3 optical signal degraded, CP G3






31 4 7

32 4 8

33 5 1 OC-3 PM threshold 1 crossed, CP G3






39 5 7

40 5 8






Table 3-12 (continued)Monitor display 8—OC-3 optical tributary facility indications





47 6 7

48 6 8

49 7 1

50 7 2

51 7 3

52 7 4

53 7 5

54 7 6

55 7 7

56 7 8

57 8 1

58 8 2

59 8 3

60 8 4

61 8 5

62 8 6

63 8 7

64 8 8 Reserved

Note: Monitor display 8 does not apply to regenerators.

Table 3-12 (continued)Monitor display 8—OC-3 optical tributary facility indications




Table 3-13 Monitor display 9—OC-3 optical tributary protection


1 1 1 OC-3 switch fail, CP G3






7 1 7

8 1 8

9 2 1 OC-3 switch complete, CP G3






15 2 7

16 2 8

17 3 1 OC-3 protection path fail, CP G3






23 3 7

24 3 8

25 4 1 OC-3 lockout, CP G3








31 4 7

32 4 8

33 5 1 OC-3 Tx active, CP G3

34 5 2 OC-3 Rx active, CP G3











45 6 5

46 6 6

47 6 7

48 6 8

49 7 1

50 7 2

51 7 3

52 7 4

53 7 5

54 7 6

55 7 7

56 7 8

Table 3-13 (continued)Monitor display 9—OC-3 optical tributary protection




57 8 1

58 8 2

59 8 3

60 8 4

61 8 5

62 8 6

63 8 7

64 8 8 Reserved

Note: Monitor display 9 does not apply to regenerators.

Table 3-14 Monitor display 10—maintenance display


1 1 1 0

2 1 2 1

3 1 3 0

4 1 4 1

5 1 5 0

6 1 6 1

7 1 7 0

8 1 8 1

9 2 1 1

10 2 2 0

11 2 3 1

12 2 4 0

13 2 5 1

14 2 6 0

15 2 7 1

16 2 8 0

Table 3-13 (continued)Monitor display 9—OC-3 optical tributary protection




17 3 1 0

18 3 2 1

19 3 3 0

20 3 4 1

21 3 5 0

22 3 6 1

23 3 7 0

24 3 8 1

25 4 1 1

26 4 2 0

27 4 3 1

28 4 4 0

29 4 5 1

30 4 6 0

31 4 7 1

32 4 8 0

33 5 1 0

34 5 2 1

35 5 3 0

36 5 4 1

37 5 5 0

38 5 6 1

39 5 7 0

40 5 8 1

41 6 1 1

42 6 2 0

43 6 3 1

44 6 4 0

Table 3-14 (continued)Monitor display 10—maintenance display




45 6 5 1

46 6 6 0

47 6 7 1

48 6 8 0

49 7 1 0

50 7 2 1

51 7 3 0

52 7 4 1

53 7 5 0

54 7 6 1

55 7 7 0

56 7 8 1

57 8 1 1

58 8 2 0

59 8 3 1

60 8 4 0

61 8 5 1

62 8 6 0

63 8 7 1

64 8 8 0

Note: The maintenance display is a known checkerboard pattern of 1’s and 0’s used for serial integrity.

Table 3-14 (continued)Monitor display 10—maintenance display




Table 3-15 Control display 1—DS1 protection switching, processor restart, exerciser routine, and database backup command


1 1 1 DS1 lockout (operate/release), CP G1












13 2 5 DS1 lockout (operate/release), CP P

14 2 6

15 2 7

16 2 8

17 3 1 DS1 forced switch (operate/release), CP G1














29 4 5

30 4 6

31 4 7

32 4 8

33 5 1 DS1 manual switch (operate/release), CP G1












45 6 5

46 6 6

47 6 7

48 6 8

49 7 1

50 7 2

51 7 3

52 7 4

53 7 5

54 7 6

Table 3-15 (continued)Control display 1—DS1 protection switching, processor restart, exerciser routine, and database backup command




55 7 7

56 7 8

57 8 1 Run shelf exerciser (operate/momentary only)

58 8 2 Shelf processor restart (operate/momentary only)

59 8 3 Backup database to OPC (operate/momentary only)

60 8 4

61 8 5

62 8 6

63 8 7

64 8 8

Note: Only points 58 and 59 apply to regenerators.

Table 3-16 Control display 2—OC-3/OC-12/STS-12 and DS3/STS-1 protectionswitching commands


1 1 1 OC-3/OC-12 lockout (operate/release), CP G1 (see Note 3)

2 1 2 OC-3/OC-12 lockout (operate/release), CP G2 (see Note 3)

3 1 3 OC-3/OC-12 lockout (operate/release), CP G1S(see Note 3)

4 1 4

5 1 5 OC-3 lockout (operate/release), CP G3

6 1 6


8 1 8


10 2 2

11 2 3 DS3/STS1 lockout (operate/release), CP G1


Table 3-15 (continued)Control display 1—DS1 protection switching, processor restart, exerciser routine, and database backup command






15 2 7 DS3 lockout (operate/release), CP P

16 2 8 STS1 lockout (operate/release), CP P

17 3 1 OC-3/OC-12 forced switch (operate/release), CP G1

18 3 2 OC-3/OC-12 forced switch (operate/release), CP G2

19 3 3 OC-3/OC-12 forced switch (operate/release), CP G1S

20 3 4 OC-3/OC-12 forced switch (operate/release), CP G2S

21 3 5 OC-3 forced switch (operate/release), CP G3






27 4 3 DS3/STS1 forced switch (operate/release), CP G1




31 4 7 OC-3/OC-12 lockout working (operate/release), CP G1 (see Note 4)

32 4 8 OC-3/OC-12 lockout working (operate/release), CP G1S (see Note 4)

33 5 1 OC-3/OC-12 manual switch (operate/release), CP G1

34 5 2 OC-3/OC-12 manual switch (operate/release), CP G2

35 5 3 OC-3/OC-12 manual switch (operate/release), CP G1S

36 5 4 OC-3/OC-12 manual switch (operate/release), CP G2S

37 5 5 OC-3 manual switch (operate/release), CP G3


Table 3-16 (continued)Control display 2—OC-3/OC-12/STS-12 and DS3/STS-1 protectionswitching commands








43 6 3 DS3/STS1 manual switch (operate/release), CP G1




47 6 7 Manual operation (operate/release), parallel output relay 1 (see Note 5)























Note 2: Before manual operation of parallel outputs can be performed, the “Deldisp” command must be issued on the NE user interface to change output operation from automatic to manual. See the procedure on deleting a display from a TBOS port in System Administration Procedures, 323-1111-302, or the “Deldisp” command for parallel outputs.

Note 3: In ring configurations these points provide lockout of protection.

Note 4: These points apply to ring configurations only.

Note 5: Only points 47 to 64 apply for regenerators.

Legend

CP = circuit pack





Table 3-17 Network summary display—remote display 1


1 1 1 Network critical

2 1 2 Network major

3 1 3 Network minor

4 1 4 Network warning

5 1 5 Counts inaccurate

6 1 6

7 1 7

8 1 8

9 2 1

10 2 2

11 2 3

12 2 4

13 2 5

14 2 6

15 2 7

16 2 8

17 3 1

18 3 2

19 3 3

20 3 4

21 3 5

22 3 6

23 3 7

24 3 8

25 4 1

26 4 2

27 4 3

28 4 4



29 4 5

30 4 6

31 4 7

32 4 8

33 5 1

34 5 2

35 5 3

36 5 4

37 5 5

38 5 6

39 5 7

40 5 8

41 6 1

42 6 2

43 6 3

44 6 4

45 6 5

46 6 6

47 6 7

48 6 8

49 7 1

50 7 2

51 7 3

52 7 4

53 7 5

54 7 6

55 7 7

56 7 8

Table 3-17 (continued)Network summary display—remote display 1




Alarms not displayed on the monitor displaysThe following alarms do not trigger TBOS alarm points:

• Automatic firmware download in progress (STS-1, OC-12)

• Critical test alarm

• Entry to SONET clock freerun

• Equipment forced switch request (ESI)

• Equipment lockout request (ESI)

• Equipment manual switch request (ESI)

• Equipment protection switch complete (ESI)

• Failure to lock (ESI)

• Fan 4 fail

• Firmware corrupt

• Firmware/software incompatible (OC-12)

• Forced switch request (DS1, DS3, STS-1, OC-12)

• Lockout protection operation fail

• Loopback (DS1, DS3, STS-1)

• LpbkG1 Automatic firmware download in progress

• LpbkG1S Automatic firmware download in progress

• Major test alarm

57 8 1

58 8 2

59 8 3

60 8 4

61 8 5

62 8 6

63 8 7

64 8 8


Table 3-17 (continued)Network summary display—remote display 1




• Manual area address dropped from area

• Manual switch request (DS1, DS3, STS-1, OC-12)

• Minor test alarm

• Multiple fan fail

• Node count limit is exceeded

• OPC alarm(s) active

• Performance monitor clock fail

• PM threshold capping active

• Protection equipment unavailable (DS1, DS3, STS-1)

• Protection switch complete (remote request) (OC-12)

• PUSEB override

• RTU DTAU test in progress

• Rx Inter-ring secondary feed fail

• Rx yellow (DS1)

• STS1 signal label mismatch

• Timing generation entry to acquire (ESI)

• Timing generation entry to fast (ESI)

• Timing generation entry to freerun (ESI)

• Timing generation entry to holdover (ESI)

• Tx AIS (DS3)

• Tx loss of frame (DS3)

• User port 3 intrusion attempt

• User port 4 intrusion attempt

• Warning test alarm

• VT Path signal label mismatch

• VT Rx AIS

• VT Rx loss of pointer

• VT Rx RFI

• VT Rx unequipped

Parallel telemetry An S/DMS TransportNode network allows external alarms to be carried to the local network element using external customer inputs. A set of output relays is also provided to activate office alarms, environment-control equipment, or power generators. The inputs and outputs share a 44-pin connector on the side interconnect left (SIL) circuit pack. Do not connect the parallel telemetry



connector to the same connector on any other TransportNode equipment. These parallel telemetry inputs and outputs are intended to be connected to isolated contacts. See Installation Procedures, 323-1111-201, to connect the parallel telemetry.

External customer inputs (telemetry inputs) A set of eleven external inputs is provided with return connection. The inputs are activated by applying a connection to the input return, from an isolated relay contact or switch. These inputs correspond to external alarms only (for example, power failure, fire alarm, flood alarm). They are not system alarms (for example, signal degrade, protection failure, circuit pack failure). Each of these external customer inputs can be assigned a 40-character string of text to identify the specific alarms. The alarm class and severity are preset to a default but can be changed (see Network Surveillance Procedures, 323-1111-510). The following defaults apply.

External customer outputs (telemetry outputs)A 44-pin connector on the SIL circuit pack provides the connection for the 18 Form-A relays (normally open). Any of the alarm points available for the TBOS (serial E2A) interface can be assigned to a particular relay, including the external customer inputs. These external outputs are typically used to activate bells or lamps, or to start generators, heaters, or air conditioners. Table 3-18 shows the default assignments for external outputs.

Figure 3-5 provides examples of applications for external customer inputs and external outputs.

Input point

Alarm text Severity Service code

Default status

1

2

3

4-11

AC power fail

Low battery

Reserved for future use

Telemetry Input N

Minor

Major

Minor

Minor

NSA

NSA

NSA

NSA

Enabled

Enabled

Enabled

Enabled



Table 3-18External outputs default assignment

Output Status Description Monitor display

Byte Bit

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Enabled

Network Element Identifier (any critical, major, or minor alarm)

Critical alarm

Major alarm

Minor alarm

nil

nil

nil

Any OC-n Indication

Any DS-n indication

OC-n/DS-n Signal Fail

OC-n Signal Degrade

OC-n/DS-n Equipment Fail

OC-n/DS-n Protection Switch Complete

Any common Eqp or Env alarm

External Input #1 (AC Power Fail)

External Input #2 (Low Battery)

nil

nil

1

2

2

2

-

-

-

2

2

2

2

2

2

2

2

2

-

-

8

8

8

8

-

-

-

2

2

7

2

7

7

2

5

5

-

-

7

1

2

3

-

-

-

7

8

2

4

1

4

6

1

2

-

-



Figure 3-5Parallel telemetry applications

FW-00438

Relay outputs

(Executable commandsfor external control)

Lights andflashers

Bells

Generators,heaters and

air conditioners

TransportNodenetworkelement

External customer inputs

(Monitor external alarmand status points)

Lowtemperature

Hightemperature

Flood

Opendoor

Fire

Powerfailure

TransportNodenetworkelement


SONET Transmission Products

S/DMS TransportNodeOC-3/OC-12 NE—TBMAlarms and Surveillance Description

Copyright „1992–2001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks and S/DMS TransportNode are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment Corporation. UNIX is a trademark of X/Open Company Ltd.

323-1111-104Rel 14 Standard February 2001Printed in Canada

sonet transmission products s/dms transportnode …npatrick/nortel-sdms-docs/n3rltcyl.pdf ·...

Documents