Alarms and Surveillance Description

Transcription

1 NT7E65DJ SONET Transmission Products S/DMS TransportNode OC-3/OC-12 NE TBM Alarms and Surveillance Description Standard Rel 14 February 2001 What s inside... Alarm reporting and surveillance Log report description Surveillance interface

2 Copyright 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

3 iii Contents What s inside... About this document v Alarm reporting and surveillance 1-1 Alarm severity, service code, and protection and activity status 1-1 Critical 1-1 Major 1-1 Minor 1-2 Warning 1-2 Service code 1-2 Protection and activity status 1-2 Time filtering 1-2 Local alarm indications 1-2 Bay alarms 1-3 Shelf alarms 1-3 Circuit pack alarms 1-4 Cooling unit alarms 1-5 Remote alarms 1-5 Alarm reporting 1-7 Alarm hierarchy 1-8 Facility alarm hierarchy 1-8 Equipment alarm hierarchy 1-10 Common equipment and environmental alarm hierarchy 1-11 Control architecture 1-11 Log report description 2-1 Numbering scheme 2-1 NE logs 2-2 OPC logs 2-4 Surveillance interface 3-1 Operations controller 3-1 OPC network communication 3-1 OPC network surveillance 3-1 Maintenance interface controller circuit pack 3-2 User interface CRT 3-4 X.11 terminal 3-4 Serial telemetry (TBOS) 3-6 TBOS displays 3-7 Alarms and Surveillance Description Rel 14 Standard Feb 2001

4 iv Contents TBOS protocol 3-10 TBOS scan request 3-11 TBOS command request 3-12 Remote telemetry 3-14 Network summary display (Remote network telemetry) 3-14 Network element monitor display 3-15 Network application 3-15 Remote parallel telemetry 3-16 Impact of communications losses between OPC and network elements 3-17 Alarms not displayed on the monitor displays 3-54 Parallel telemetry 3-55 External customer inputs (telemetry inputs) 3-56 External customer outputs (telemetry outputs) 3-56 S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

5 About this document v This 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. Audience This document is for the following members of the operating company: planners provisioners network administrators transmission standards engineers maintenance personnel References in this document This document refers to the following documents: System Administration, Circuit Pack Descriptions, TL1 Interface Description, Installation Procedures, System Admnistration Procedures, Network Surveillance Procedures, Alarm and Trouble Clearing Procedures, Log Report Manual, Alarms and Surveillance Description Rel 14 Standard Feb 2001

6 vi About this document S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

7 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, 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, Alarm severity, service code, and protection and activity status The 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

8 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 status The 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 filtering The OC-3 and OC-12 network elements support time filtering of alarms, as specified in Bellcore TR-TSY 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, 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. S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

9 Alarm reporting and surveillance 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-1 Bay alarms on the breaker interface panel (BIP) FW Trip Battery A Battery B A 1 A 2 A 3 A 4 B 1 B 2 B 3 B 4 I I I I I I I I O O O O O O O O ACO/LT Power Critical Major Minor Bay alarms 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

10 1-4 Alarm reporting and surveillance Figure 1-2 Shelf alarms on the local craft access panel (LCAP) FW-0143 (OC) ACO/LT Critical Major Minor ESD Ground Cover Flap (Open Position) Call Incoming Indicator ACO/LT Critical Major Minor ESD Ground 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, , for a definition of the meaning of the LEDs for each circuit pack). Red A red LED indicates a probable circuit pack failure, a high temperature condition on the shelf, or an exerciser failure. Green A green LED indicates that the circuit pack is in service, and that it should not be removed. Yellow On 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, S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

11 Alarm reporting and surveillance 1-5 Cooling unit alarms On 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-3 Visual indicators on the cooling unit FW-1925 Fail indicators CU Interface CU Pwr A(±), B(±) (see Note) Note: A second set of cooling unit power connectors (CU Pwr A and B) for the through-flow cooling unit (NT4K18BA) is located on the right side of the shelf. 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, , for details concerning TL1. Alarms and Surveillance Description Rel 14 Standard Feb 2001

12 1-6 Alarm reporting and surveillance Figure 1-4 Surveillance interfaces FW-1945(TBM) TBM Shelf Ethernet X.11 Terminal Graphical User Interface User Interface (Local terminal VT100-type) User Interface Port 2 (RS-232) on LCAP CNet LAN Operations Controller Processor card Maintenance Interface card OAM Bus OPC Port 1 Side Interconnect Left (SIL) card connectors VT100-type Terminal or X.25 TL-1 interface or Printer Side Interconnect Left (SIL) card connectors OPC Port 2 X.25 TL-1 interface Side Interconnect Left (SIL) card connectors (Note) Serial Telemetry ports (Alarm Processing Remote) Relay Outputs External Customer Inputs TBOS (E2A) Parallel Telemetry Out Parallel Telemetry In User Interface Port 1 (RS-232) OR Printer OR User Interface (Local Terminal VT100-type) Modem to Remote Terminal 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. S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

13 Alarm reporting and surveillance 1-7 Alarm reporting Alarm 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. Table 1-1 Alarm 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 OC3/OC12 (OC-3/OC-12) REMT (remote) STS-1 ESI (external synchronization interface) Lpbk (loopback) MIC (maintenance interface controller) circuit pack OC3/OC12 OC12 OPC Proc (processor) REMT (remote) STS1 (STS-1 electrical interface) 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

14 1-8 Alarm reporting and surveillance 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). S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

15 Alarm reporting and surveillance 1-9 Figure 1-5 Facility alarm hierarchy FW-2040 (TBM R11 Ph1) OC-3 or OC-12 Facility STS1 Facility Optical Source Rx LOS LOF Loopback STS1 Source Rx LOS Rx LOF Rx BPV Rx AIS (line) Signal Fail Signal Degrade Rx Line AIS Line RFI Rx RFI Rx LOP Rx Path AIS STS1 Rx LOP STS1 Rx AIS (path) Path Facility Path Facility or DS3 Facility DS3 Source Loopback Rx LOS Freq OOR DS3 Facility STS1 Rx Unequipped STS1 SLM STS1 Rx PTF Rx AIS (path) Rx LOF Rx Yellow Rx BPV STS1 Path RFI Tx LOF Tx AIS (path) VT Rx LOP VT Rx AIS VT Rx Unequipped DS1 Source Loopback Rx LOS DS1 Facility VT Path RFI Rx AIS (path) Rx LOF Rx Yellow Rx BPV Alarms and Surveillance Description Rel 14 Standard Feb 2001

16 1-10 Alarm reporting and surveillance 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-6 Equipment alarm hierarchy FW-2118 Circuit pack missing Circuit pack mismatch Circuit pack fail 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. S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

17 Alarm reporting and surveillance 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

18 1-12 Alarm reporting and surveillance Figure 1-7 Overhead layers FW-0022 (OC) Path Terminating Equipment Line Terminating Equipment Regenerator Line Terminating Equipment Path Terminating Equipment (example: multiplexer) SONET Terminal Tx Rx Section Line Path (end-to-end) (FW-0022) S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

19 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, Numbering scheme All 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 Alarms and Surveillance Description Rel 14 Standard Feb 2001

20 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, 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. S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

21 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. ACTSYS ASNILOG BMS CLIN DECR FREQ FPRT INFO INIT ISYSLOG ISYSLOG1 MTS SAVLOG SOS STOR SWERR SYSLOG SYSLOG1 TPS TRAP The following is an example of an EQP log report. log number date report number event type INFO: information FAIL: alarm or failure log type time event EQP501 FEB13 14: 15: INFO EQP State Change description location Object Class: Circuit Pack Group Present State: IS Previous State: OOS NE: 12 Ring5 LOCATION: 1 TORONTO EQP: 1 OC12 RingADM SHELF POS: 1 SHELF: 1 CPG: OC12 G1S SLOT: 11 PEC: NT7E02KC 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

22 2-4 Log report description 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. Log category Minimum quantity of entries Maximum quantity of entries COAD COML DLD EQP EVNT FAC FLT FWDB HMU NE REMT 6 6 SOFT SWERR TCSF TRAP Note: These numbers are estimates only; they can vary by ±2 entries. 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. S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

23 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

24 2-6 Log report description S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

25 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, For details on the Transaction Language 1 (TL1) interface, see TL1 Interface Description, 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

26 3-2 Surveillance interface Maintenance interface controller circuit pack The 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-1 Communication 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 User interface S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

27 Surveillance interface 3-3 Figure 3-1 Surveillance interfaces supported by the maintenance interface controller (MIC) circuit pack FW-1945 (TBM) TBM Shelf Ethernet X.11 Terminal Graphical User Interface User Interface (Local terminal VT100-type) User Interface Port 2 (RS-232) on LCAP CNet LAN Operations Controller Processor card Maintenance Interface card OAM Bus OPC Port 1 Side Interconnect Left (SIL) card connectors VT100-type Terminal or X.25 TL-1 interface or Printer Side Interconnect Left (SIL) card connectors OPC Port 2 X.25 TL-1 interface Side Interconnect Left (SIL) card connectors (Note) Serial Telemetry ports (Alarm Processing Remote) Relay Outputs External Customer Inputs TBOS (E2A) Parallel Telemetry Out Parallel Telemetry In User Interface Port 1 (RS-232) OR Printer OR User Interface (Local Terminal VT100-type) Modem to Remote Terminal 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001

28 3-4 Surveillance interface 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 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. S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

29 Surveillance interface 3-5 Figure 3-2 User interface applications FW-1950 Remote Surveillance Center RS-232 Remote User Interface (VT100 Compatible) Modem Terminal RS-232 Modem Terminal LTE Ethernet LTE DS1/DS3 DS1/DS3 RS-232 RS-232 Local User Interface (VT100 Compatible) Graphical User Interface (X.11 Terminal) Printer Alarms and Surveillance Description Rel 14 Standard Feb 2001

30 3-6 Surveillance interface 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 Start Bit Character Odd Stop Parity Bits 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 S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

31 Surveillance interface 3-7 described in Table 3-4 to Table 3-17 on page 3-17 through page Setting parameters of the network element user interface ports is described in System Administration Procedures, Figure 3-3 RS-422 port FW-0047 TransportNode network element maintenance interface TBOS port drivers (one port shown) Transmit + TBOS (serial E2A) Transmit Ω RS-422 receiver Alarm processing remote Receive + Receive - RS-422 driver 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 Alarms and Surveillance Description Rel 14 Standard Feb 2001

32 3-8 Surveillance interface 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 The Network Summary display (Remote display 1) is described in Table 3-17 on page 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, ) The assignment of the Remote displays is done with the OPC user interface. (Mapping remote TBOS ports is described in System Administration Procedures, ). 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 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, ). S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

33 Surveillance interface 3-9 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 Alarms and Surveillance Description Rel 14 Standard Feb 2001

34 3-10 Surveillance interface Table 3-3 Serial 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. 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. OP code Description 00 TBOS Scan Request 01 TBOS Command Request (message 1) 10 TBOS Command Request (message 2) 11 TBOS Command Request (message 3) S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

35 Surveillance interface 3-11 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 MSB LSB MSB LSB Start Request Mapping Character Odd Stop Bit OPcode Position No. No. <00> 000 = Pos = Char = Pos = Char = Pos = Char = Pos = Char = Pos = Char = Pos = Char = Pos = Char = Pos = Char 8 The proper reply consists of the character of the display implied by the mapping position number and the character index supplied in the command. Alarms and Surveillance Description Rel 14 Standard Feb 2001

36 3-12 Surveillance interface 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 0 B8 B7 B6 B5 B4 B3 B2 B1 Parity Start Character Odd Stop Bit Parity Bits 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) MSB LSB Start Request Mapping Request Odd Stop Bit OPcode Position No. Type <01> 000 = Pos = Pos 2 00 = momentary 010 = Pos 3 01 = latch/operate 011 = Pos 4 10 = unlatch/release 100 = Pos 5 11 = Not used 101 = Pos = Pos = Pos 8 S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

37 Surveillance interface 3-13 Command request (message 2) MSB LSB Start Request Remote Command Number Odd Stop Bit OPcode Parity Bits <10> = Command No = Command No = Command No = Command No. 64 Command Response (Message 2) - Echo of Request Command request (message 3) Start Bit Request OPcode <11> Execute Code <001100> Odd Parity Stop Bits Command Response (Message 3) - Echo of Request 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 Two bits within the first message indicate the request type. Alarms and Surveillance Description Rel 14 Standard Feb 2001

38 3-14 Surveillance interface Request Type Description 00 Momentary 01 Latch/Operate 10 Unlatch/Release 11 Unused 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 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. S/DMS TransportNode OC-3/OC-12 NE TBM Vol Rel 14 Standard Feb 2001

39 Surveillance interface 3-15 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, 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, 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. Alarms and Surveillance Description Rel 14 Standard Feb 2001