Operations Documentation. Node Operations and Maintenance Guide

Transcription

1 Turin Networks Inc. Operations Documentation Node Operations and Maintenance Guide Release OPS3.1.x Publication Date: April 2007 Document Number: OPS31 Rev. A

2 FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the installation instructions may cause harmful interference to radio communications. Canadian Compliance This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respects toutes les exigences du Règlement sur le matériel brouilleur du Canada. Japanese Compliance This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case, the user may be required to take corrective actions. International Declaration of Conformity We, Turin Networks, Inc. declare under our sole responsibility that the Traverse platform (models: Traverse 2000, Traverse 1600, and Traverse 600) to which this declaration relates, is in conformity with the following standards: EMC Standards EN55022 EN55024 CISPR-22 Safety Standards EN60950 CSA 22.2 No , ASINZS 3260 IEC Third Edition. Compliant with all CB scheme member country deviations. Following the provisions of the EMC Directive 89/336/EEC of the Council of the European Union. Copyright 2007 Turin Networks, Inc. All rights reserved. This document contains proprietary and confidential information of Turin Networks, Inc., and may not be used, reproduced, or distributed except as authorized by Turin Networks. No part of this publication may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation or adaptation) without written permission from Turin Networks, Inc. Turin Networks reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of Turin Networks to provide notification of such revision or change. Turin Networks may make improvements or changes in the product(s) described in this manual at any time. Turin Networks Trademarks Turin Networks, the Turin Networks logo, Traverse, TraverseEdge, TransAccess, TransNav, and Creating The Broadband Edge are trademarks of Turin Networks, Inc. or its affiliates in the United States and other countries. All other trademarks, service marks, product names, or brand names mentioned in this document are the property of their respective owners. Government Use Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR (Commercial Computer Software-Restricted Rights) and DFAR (Rights in Technical Data and Computer Software), as applicable.

3 NODE OPERATIONS AND MAINTENANCE GUIDE Contents About this Document iii Section 1 Fault Management Chapter 1 Managing Alarms and Events Chapter 2 Alarms, Events, and Recommended Actions Chapter 3 TransNav GUI Service Error Codes Section 2 Performance Monitoring Chapter 1 Managing Performance Chapter 2 SONET Performance Parameters Chapter 3 SDH Performance Parameters Chapter 4 Ethernet Performance Parameters Section 3 Equipment LED Status Chapter 1 LEDs and Module Status Section 4 Diagnostics Chapter 1 Diagnostics Overview Chapter 2 Traverse Transmit and Receive Signal Levels Chapter 3 TraverseEdge 100 Transmit and Receive Signal Levels Chapter 4 Loopback Tests Chapter 5 Other Diagnostics Section 5 Test Access Chapter 1 Traverse Test Access Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface Section 6 Routine Maintenance Chapter 1 Release OPS3.1.x Turin Networks Page i

4 Node Operations and Maintenance Guide Routine Maintenance Chapter 2 Node Database Backup and Restore Section 7 Software Upgrades Chapter 1 Release TR2.1.x Traverse Software Upgrade Chapter 2 Release 3.0.x TE-100 System Software Upgrade Section 8 Hardware Upgrades Chapter 1 Replacing Existing Traverse Hardware Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray Section 9 Appendices Appendix A Module Placement Planning and Guidelines Appendix B Traverse SNMP v1/v2c Agent and MIBs Index Index-1 Page ii Turin Networks Release OPS3.1.x

5 Node Operations and Maintenance [OPS3.1.x] Document Description About this Document Introduction This description contains the following documentation topics: Traverse System Product Documentation, page iv TraverseEdge System Product Documentation, page v TransNav Management System Product Documentation, page vi Operations Documentation, page vii Information Mapping, page vii If You Need Help, page vii Calling for Repairs, page viii Release OPS3.1.x Turin Networks Page iii

6 Traverse System Product Documentation Traverse System Product Documentation The Traverse system product documentation set includes the documents described in the table below. Table 1 Traverse System Product Documentation Document Description Target Audience Traverse Product Overview Traverse Installation and Configuration Traverse Provisioning This document provides a detailed overview of the Traverse system. It also includes engineering and planning information. This document provides required equipment, tools, and step-by-step procedures for: Hardware installation Power cabling Network cabling Node power up Node start-up This document provides step-by-step procedures for provisioning a network of Traverse nodes using the TransNav management system. See the TransNav Management System Product Documentation. Anyone who wants to understand the Traverse system and its applications. Installers, field, and network engineers Network engineers, provisioning, and network operations center (NOC) personnel Page iv Turin Networks Release OPS3.1.x

7 TraverseEdge System Product Documentation TraverseEdge System Product Documentation The TraverseEdge 100 User Guide includes the sections described in the table below. Table 2 TraverseEdge 100 System Product Documentation Section Description Target Audience Product Overview Description and Specifications Installation and Configuration Provisioning the Network Configuring Equipment Creating TDM Services Creating Ethernet Services Appendices This section provides a detailed overview of the TraverseEdge system. This section includes engineering and planning information. This document identifies required equipment and tools and provides step-by-step procedures for: Hardware installation Power cabling Network cabling Node power up Node start-up This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for configuring module and interface parameters of a TraverseEdge using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. See the TransNav Management System Product Documentation. This section provides installation and provisioning checklists, compliance information, and acronym descriptions. Anyone who wants to understand the TraverseEdge system and its applications Field and network engineers Installers, field, and network engineers Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Installers and anyone who wants reference information. Release OPS3.1.x Turin Networks Page v

8 TransNav Management System Product Documentation TransNav Management System Product Documentation The TransNav management system product documentation set includes the documents described in the table below. Table 3 TransNav Management System Product Documentation Document Description Target Audience TransNav Management System Product Overview TransNav Management System Server Guide TransNav Management System GUI Guide This document provides a detailed overview of the TransNav management system. This document includes hardware and software requirements for the management system. It also includes network management planning information. This document describes the management server component of the management system and provides procedures and troubleshooting information for the server. This document describes the graphical user interface including installation instructions and logon procedures. Anyone who wants to understand the TransNav management system Field and network engineers, provisioning, and network operations center (NOC) personnel TransNav Management System CLI Guide TransNav Management System TL1 Guide This document describes every menu, window, and screen a user sees in the graphical user interface. This document includes a quick reference to the command line interface (CLI). Also included are comprehensive lists of both the node-level and domain-level CLI commands. This document describes the syntax of the TL1 language in the TransNav environment. This document also defines all input commands and expected responses for retrieval commands as well as autonomous messages that the system outputs due to internal system events. Page vi Turin Networks Release OPS3.1.x

9 Operations Documentation Operations Documentation The document below provides operations and maintenance information for Turin s TransNav managed products. Table 4 Operations Documentation Document Description Target Audience Node Operations and Maintenance This document identifies required equipment and tools. It also provides step-by-step procedures for: Alarms and recommended actions Performance monitoring Equipment LED and status Diagnostics Test access (SONET network only) Routine maintenance Node software upgrades Node hardware upgrades Field and network engineers Information Mapping If You Need Help Traverse, TransNav, and TraverseEdge 100 system documentation uses the Information Mapping format which presents information in small units or blocks. The beginning of an information block is identified by a subject label in the left margin; the end is identified by a horizontal line. Subject labels allow the reader to scan the document and find a specific subject. Its objective is to make information easy for the reader to access, use, and remember. Each procedure lists the equipment and tools and provides step-by-step instructions required to perform each task. Graphics are integrated into the procedures whenever possible. If you need assistance while working with Traverse products, contact the Turin Networks Technical Assistance Center (TAC): Inside the U.S., toll-free: TURINET ( ) Outside the U.S.: Online: TAC is available 6:00AM to 6:00PM Pacific Time, Monday through Friday (business hours). When the TAC is closed, emergency service only is available on a callback basis. support (24-hour response) is also available through: [email protected]. Release OPS3.1.x Turin Networks Page vii

10 Calling for Repairs Calling for Repairs If repair is necessary, call the Turin Repair Facility at TURINET ( ) for a Return Material Authorization (RMA) number before sending the unit. The RMA number must be prominently displayed on all equipment cartons. The Repair Facility is open from 6:00AM to 6:00PM Pacific Time, Monday through Friday. When calling from outside the United States, use the appropriate international access code, and then call to contact the Repair Facility. When shipping equipment for repair, follow these steps: 1. Pack the unit securely. 2. Enclose a note describing the exact problem. 3. Enclose a copy of the invoice that verifies the warranty status. 4. Ship the unit PREPAID to the following address: Turin Networks, Inc. Turin Repair Facility Attn: RMA # 1415 North McDowell Blvd. Petaluma, CA USA Page viii Turin Networks Release OPS3.1.x

11 SECTION 1SYSTEM MONITORING SECTION 1 FAULT MANAGEMENT SECTION 1 Contents Chapter 1 Managing Alarms and Events Introduction Events Alarms Event Types Provisioning events Performance events Security events Normal operational events Fault events (alarms) Event Logs Events Tab Alarms Tab Network Alarm Summary Window Service Affecting Status Alarm Severity Levels Alarm Hierarchy Customizing Alarms Alarm Profiles Sort by Column Creating a New Alarm Profile Assigning an Alarm Profile Assigning a Port Alarm Profile Assigning a Subport Alarm Profile Assigning a Service Path Alarm Profile Suppressing Alarms Suppress Port Alarms Service CTP Path Alarm Suppression Viewing Alarms Alarm Tallies Detail View Map View Display New Window Print Save Set Filters Sort by Column StickyMode Release OPS3.1.x Turin Networks Page vii

12 Node Operations and Maintenance Guide, Section 1 Fault Management Chapter 2 Alarms, Events, and Recommended Actions Introduction Alarms/Events, A through C Alarms/Events, D through K Alarms/Events, L through S Alarms/Events, TA Alarms/Events, TB through TZ Alarms/Events U through Z Chapter 3 TransNav GUI Service Error Codes Introduction Service Activation Failure TransNav GUI Service Error Codes List of Figures Figure 1-1 Map View, Events Tab Figure 1-2 Alarms Tab Figure 1-3 Network Alarm Summary Window Figure 1-4 Alarm Profile Dialog Box Figure 1-5 Alarm Profiles Dialog Box Figure 1-6 Alarm Profile Dialog Box Figure 1-7 Service Tab Figure 1-8 Path Display for Services Screen Figure 1-9 Service Tab Figure 1-10 Path Display for Services Screen Figure 1-11 Alarm Filter Dialog Box Figure 1-12 Hardware Fault Detection Descriptions Figure 1-13 TransNav GUI Service Request Error Window Figure 1-14 Service Request Failure Figure 1-15 Services Menu Show Last Error Option List of Tables Table 1-1 Creating a New Alarm Profile Table 1-2 Assigning a Port Alarm Profile Table 1-3 Assigning a Subport Alarm Profile Table 1-4 Assigning a Service Path Alarm Profile Table 1-5 Suppress Port Alarms Table 1-6 Suppress Service CTP Path Alarms Table 1-7 Viewing Alarms Table 1-8 Alarms, Events and Recommended Actions, A through C Table 1-9 Alarms, Events and Recommended Actions, D through K Page viii Turin Networks Release OPS3.1.x

13 Node Operations and Maintenance Guide, Section 1 Fault Management Table 1-10 Alarms, Events and Recommended Actions, L through S Table 1-11 Alarms, Events and Recommended Actions, TA Table 1-12 Alarms, Events and Recommended Actions, TB through TZ Table 1-13 Alarms, Events and Recommended Actions, U through Z Table 1-14 Service Request Show Last Error Table 1-15 Service Error Codes and Recommended Actions Release OPS3.1.x Turin Networks Page ix

14 Node Operations and Maintenance Guide, Section 1 Fault Management Page x Turin Networks Release OPS3.1.x

15 SECTION 1FAULT MANAGEMENT Chapter 1 Managing Alarms and Events Introduction During normal operation of the Turin product family, various conditions may arise that require attention by network operations. Events and alarms alert you to system operational changes. Events Events (other than alarm fault events) are state-less alerts indicating configuration changes, operator actions, performance changes, and other standard operations. Alarms Alarms are fault events indicating abnormal single-state or multi-state conditions requiring system operator attention. A single-state condition example is a hardware device failure. The hardware device is either in the failed condition or not. Each alarm is characterized by alarm severity, service affecting status, and whether the alarm is active or clear. If a condition persists, the alarm is active. If the fault condition is resolved, either automatically or by operator action, the alarm is clear. This chapter provides information on: Event Types, page 1-2 Event Logs, page 1-2 Events Tab, page 1-3 Alarms Tab, page 1-4 Network Alarm Summary Window, page 1-5 Customizing Alarms, page 1-6 Suppressing Alarms, page 1-12 Viewing Alarms, page 1-15 For management system reference, see the TransNav Management System GUI Guide, Section 8 Maintenance and Testing, Chapter 2 Alarms. Contact the Turin Technical Assistance Center if you need assistance while working with this product. Release OPS3.1.x Turin Networks Page 1-1

16 Node Operations and Maintenance Guide, Section 1: Fault Management Event Types Event Types Event Logs Events alert the operator to changes to the system. Each of these changes are logged and can be any one of the following event types: Provisioning events. The node has made a change to its configuration in response to a request from a management entity. Performance events. The value of a Performance Management (PM) parameter has crossed a provisioned threshold. This threshold crossing alert (TCA) may indicate service deterioration and require operator attention. Security events. A user has logged in or out of the node, an attempted login has failed, or a user has made some change to the user account database. Normal operational events. Normal and expected occurrences, such as initialization completed or control plane connection established with other nodes. They are logged for information only. Fault events (alarms). Fault conditions that may affect service and require operator attention. Fault events generate and clear alarms. The system raises an alarm when it first detects a fault condition. While the fault condition persists, the alarm is active. When the system detects that a fault condition no longer exists, it clears the alarm. The clearing may be automatic or a result of an operator action (e.g., replacing a bad module). All events (including alarm fault events) are logged on either the Traverse General Control Module (GCM) or TraverseEdge 100 System module. The events logged are not persistent reboots clear the logs. For user-accessible, longer-term secure storage, an Event Log is stored on the TransNav server. This log provides easy access to information about recent events. Included in the TransNav server Event Log is the following information: Type of event (configuration, fault, performance, and security) Timestamp Component or subsystem detecting the event Descriptive text about the event The Event Log maintains a configurable number of events for a specified length of time. The oldest events are deleted after the limit has been reached; the default is 30 days. This length of time is also configurable. Turin recommends performing regular backups of the log files. One way to accomplish this is to use the Report Scheduler and set up a regularly generated report on events. For details, see the TransNav Management System GUI Guide, Section 2 Administrative Tasks, Chapter 4 Administrative Tasks, Generating Reports, page Page 1-2 Turin Networks Release OPS3.1.x

17 Chapter 1 Managing Alarms and Events Events Tab Events Tab The TransNav GUI Events tab displays a list of events for the user to quickly view and analyze state-less alerts. Figure 1-1 Map View, Events Tab Release OPS3.1.x Turin Networks Page 1-3

18 Node Operations and Maintenance Guide, Section 1: Fault Management Alarms Tab Alarms Tab The TransNav GUI Alarms tab displays a list of alarms for the user to quickly view, analyze, and resolve fault conditions. If a node is in an alarm state, it will be displayed on the Map View node object in the color of the highest level alarm severity with a caption indicating the number and type of alarm. For example, in Figure 1-2, the node TE100SIGTWO has four critical (4C) alarms, so it is colored red with the caption 4C. For alarms tab definitions, refer to: Customizing Alarms, page 1-6 Alarm Severity Levels, page 1-5 Alarm Hierarchy, page 1-6 Map View Display Alarm Caption Node Object Alarms List Alarm Tab StickyMode View Selector Set Filters Command Print Command Sort by Column Detail View New Window Save Command Command Command Figure 1-2 Alarms Tab Page 1-4 Turin Networks Release OPS3.1.x

19 Chapter 1 Managing Alarms and Events Alarm Severity Levels Network Alarm Summary Window The TransNav network alarm summary window shows counts of outstanding Critical (C), Major (M), Minor (m) alarms, and Warnings (W). Alarm Summary Figure 1-3 Network Alarm Summary Window Service Affecting Status Alarm Severity Levels Two levels of service affecting status are used in the alarm definitions: Service Affecting (SA): Indicates that a service affecting condition has occurred and an immediate corrective action is required. Non-Service Affecting (NSA): Indicates that a non-service affecting condition has occurred. Service affecting alarms apply when protection is not available. This same alarm is considered non-service affecting if the equipment or facility is protected and configured using automatic protection switching APS (multiplex section protection MSP) mode. Alarms listed as non-service affecting do not affect service regardless of equipment or facility protection scheme. Some alarms are always service affecting, some are always non-service affecting, and some can be either, depending on the circumstances. Alarms on unprotected equipment or facilities are, by default, always critical. However, this same alarm is not considered critical if the equipment or facility is protected and configured using APS (MSP). Alarms listed as minor or warning are not considered service affecting regardless of the protection scheme. The following severity levels, from the most severe to the least severe, are defined and used in the alarm and event definitions: Critical (red): A severe, service affecting condition has occurred. Immediate corrective action is imperative, regardless of the time of the day or day of the week. Major (orange): A hardware or software condition has occurred that indicates a serious disruption of service or the malfunctioning or failure of important circuits. This requires the immediate attention and response of a technician to restore or maintain system capability. The urgency is less than in critical situations because of a lesser immediate or impending effect on service or system performance. Minor (yellow): Trouble has occurred that does not have a serious affect on service to customers, or trouble in circuits has occurred that is not essential to node operation. Corrective action should be taken in order to prevent a more serious fault. Release OPS3.1.x Turin Networks Page 1-5

20 Node Operations and Maintenance Guide, Section 1: Fault Management Alarm Hierarchy Warning (cyan): A potential or impending service affecting event may occur; no significant effects have been felt. Action should be taken to further diagnose, if necessary, and correct the problem in order to prevent it from becoming a more serious fault. In general, severity levels of Critical, Major, Minor, and Warning are reported to the Alarms and Events tabs in the GUI. A severity level of Info is reported to the Events tab only. Alarm Hierarchy Customizing Alarms Alarm Profiles This system conforms to the alarm reporting hierarchy set forth in the Telcordia General Requirements GR-253, ETSI , and ITU recommendation G.783. The TransNav GUI provides functions for creating new, modifying default, and assigning alarm profiles in order to customize alarm parameter settings (e.g., severity level) based on your network requirements. Refer to the following topics: Alarm Profiles, page 1-6 Creating a New Alarm Profile, page 1-7 Assigning a Port Alarm Profile, page 1-9 Alarm profiles allow the user to customize alarms based on severity, service affecting status, and whether to enable or disable (suppress) alarm generation. Note: Create EC-3/STM-1E alarm profiles with the SONET/SDH templates, like that for the OC-3/STM-1ports. Sort by Column Figure 1-4 Alarm Profile Dialog Box Click a column heading to sort the alarms by that category. The Name and Probable Cause columns can be sorted in alphabetical or reverse alphabetical order. The Severity NSA and Severity SA columns can be sorted in ascending or descending severity. The ServiceAffecting and Enabled columns can be sorted by select/clear. Click the column heading again to switch from one sorting category to the other. Page 1-6 Turin Networks Release OPS3.1.x

21 Chapter 1 Managing Alarms and Events Creating a New Alarm Profile Creating a New Alarm Profile The following procedure describes how to create an Alarm Profile template. Table 1-1 Creating a New Alarm Profile Step Procedure 1 In Map View, from the Admin menu, click Alarm Profiles. 2 Figure 1-5 Alarm Profiles Dialog Box Release OPS3.1.x Turin Networks Page 1-7

22 Node Operations and Maintenance Guide, Section 1: Fault Management Creating a New Alarm Profile Table 1-1 Creating a New Alarm Profile (continued) Step Procedure 2 From the Type drop-down list, select the type of alarm profile you want to create: ds1_ptp: SONET DS1 port ds3_ptp: SONET DS3/EC1 ports (previously called ds_ptp) e1_ptp: SDH E1 port e3_ptp: SDH E3 port eos: SONET EOS port eos_ctp: SONET EOS connection termination point. ethernet_ptp: Ethernet port lag: (Ethernet) Link aggregated group sdh_eos: SDH EOS port sdh_eos_ctp: SDH EOS connection termination point sdh_hp: SDH high order path (VC4 or VC3) sdh_lp: SDH VC3 low order path sdh_ptp: SDH port server: TransNav server platform shelf: Traverse or TraverseEdge node (Planned for future release.) sonet_ptp: SONET port sonet_sts: SONET STS path sonet_vt: SONET VT path t100: TransAccess 100 Mux ta200: TransAccess 100 Mux 3 Click Add to view the alarm profile, then enter a Name for the alarm profile. The example shown below is an ethernet_ptp alarm profile with default values. 3 Figure 1-6 Alarm Profile Dialog Box Page 1-8 Turin Networks Release OPS3.1.x

23 Chapter 1 Managing Alarms and Events Assigning a Port Alarm Profile Table 1-1 Creating a New Alarm Profile (continued) Step Procedure 4 To modify the alarm entry settings, make a selection from the drop-down list or check the box in the row of the following columns: Severity NSA: Alarm severity when it is non-service affecting. Severity SA: Alarm severity when it is service affecting; this severity only applies if ServiceAffecting is selected. ServiceAffecting: Select to make the alarm service affecting. Clear the checkbox to make the alarm non-service affecting. Enabled: Select to enable the alarm. Clear to disable the alarm. Click OK. A user prompt appears. 5 Click Yes to synchronize the alarm profile to make it available to other nodes. Click No if you do not want to synchronize the new template. 6 Click Done in the Alarm Profiles dialog box. 7 The Creating a New Alarm Profile procedure is complete. Assigning an Alarm Profile Assigning a Port Alarm Profile Choose one of the following topics by object type (e.g., port) to assign an alarm profile: Assigning a Port Alarm Profile, page 1-9 Assigning a Subport Alarm Profile, page 1-10 Assigning a Service Path Alarm Profile, page 1-10 The following procedure describes how to assign a port alarm profile template to a port. Table 1-2 Assigning a Port Alarm Profile Step Procedure 1 In Shelf View, select a module port (or a TransAccess 100 Mux). 2 Click the Config tab. 3 From the Alarm Profiles list, select a port (ptp) alarm profile template. 4 Click Apply. 5 The Assigning a Port Alarm Profile procedure is complete. Release OPS3.1.x Turin Networks Page 1-9

24 Node Operations and Maintenance Guide, Section 1: Fault Management Assigning a Subport Alarm Profile Assigning a Subport Alarm Profile The following procedure describes how to assign a port alarm profile template to a DS3 Transmux subport. Table 1-3 Assigning a Subport Alarm Profile Step Procedure 1 In Shelf View, select a DS3 Transmux module port. 2 Click the Config tab. 3 From the Subport row, Alarm Profile column list, select a port (ptp) alarm profile template matching the embedded signal subport type (e.g., ds1_ptp). 4 Click Apply. 5 The Assigning a Subport Alarm Profile procedure is complete. Assigning a Service Path Alarm Profile The following procedure describes how to assign a path alarm profile template to a service connection termination point (CTP) within an end-to-end transport path. Table 1-4 Assigning a Service Path Alarm Profile Step Procedure 1 From any view, click the Service tab. 1 2 Figure 1-7 Service Tab 2 Select a service. Right-click and select the Show Tx/Rx Path option to display the Path Display for Services screen. Page 1-10 Turin Networks Release OPS3.1.x

25 Chapter 1 Managing Alarms and Events Assigning a Service Path Alarm Profile Table 1-4 Assigning a Service Path Alarm Profile (continued) Step Procedure 3 Click the CTP tab to display the CTP dialog box. 2 4a 3 4b 5 6 Figure 1-8 Path Display for Services Screen 4 From the Path Display for Service screen, Tx or Rx table row, select an Active Hop (4a). Your selection is placed in the EndPoint field of the CTP screen (4b). Release OPS3.1.x Turin Networks Page 1-11

26 Node Operations and Maintenance Guide, Section 1: Fault Management Suppressing Alarms Table 1-4 Assigning a Service Path Alarm Profile (continued) Step Procedure 5 From the Alarm Profile list, select one of the following profile values: useparent: The alarm profile of the containing object (Parent) based on the following (superset and subset) definitions: Port: Contains line and path alarms and is the superset. High-order path: Contains high- and low-order path alarms and is a subset of port profiles. Low-order path: Contains only low-order path alarms and is a finer subset of high-order path profiles. STS path. Contains STS and VT path alarms and is a subset of port profiles. VT path: Contains only VT path alarms and is a finer subset of STS path profiles. default: The default alarm profile matching the CTP object type. <user-defined>: Depending on the CTP object type, a user-defined alarm profile of one of the following path alarm profile types: sdh_hp sdh_lp sonet_sts sonet_vt 6 Click Apply. 7 The Assigning a Service Path Alarm Profile procedure is complete. Suppressing Alarms Suppress Port Alarms The TransNav GUI provides an alarm suppression function through the administrative state of an object. When the administrative state of a containing object is set to suppress alarms, then any object contained within obeys the parent object without consideration of its own current administrative state. Refer to the following topics: Suppress Port Alarms, page 1-12 Service CTP Path Alarm Suppression, page 1-13 The following procedure describes how to suppress port (line and path) alarms. Alarm suppression occurs also for all objects contained within the port. Table 1-5 Suppress Port Alarms Step Procedure 1 In Shelf View, select the module port. 2 Click the Config tab to display the Card Configuration dialog box. Page 1-12 Turin Networks Release OPS3.1.x

27 Chapter 1 Managing Alarms and Events Service CTP Path Alarm Suppression Table 1-5 Suppress Port Alarms (continued) Step Procedure 3 Click the Lock icon at the bottom left portion of the screen to change the administrative state to locked and click Apply. 4 The Suppress Port Alarms procedure is complete. Service CTP Path Alarm Suppression The following procedure describes how to suppress service CTP (connection termination point) path alarms. Table 1-6 Suppress Service CTP Path Alarms Step Procedure 1 Is a parent object of the CTP already suppressing alarms? Yes: Stop. CTP alarms are already being suppressed in accordance with the parent object. No: Go to the next step. 2 From any view, click the Service tab. 2 3 Figure 1-9 Service Tab Release OPS3.1.x Turin Networks Page 1-13

28 Node Operations and Maintenance Guide, Section 1: Fault Management Service CTP Path Alarm Suppression Table 1-6 Suppress Service CTP Path Alarms (continued) Step Procedure 3 Select a service. Right-click and select Show Tx/Rx Path to display the Path Display for Services screen. 3 5a 4 5b 6 7 Figure 1-10 Path Display for Services Screen 4 Click the CTP tab to display the CTP screen. 5 From the Path Display for Service screen, Tx or Rx table row, select an Active Hop (5b). Your selection inserts into the EndPoint field in the CTP screen (5b). 6 Click the Lock icon at the bottom left portion of the screen to change the administrative state to locked. 7 Click Apply. 8 The Suppress Service CTP Path Alarms procedure is complete. Page 1-14 Turin Networks Release OPS3.1.x

29 Chapter 1 Managing Alarms and Events Viewing Alarms Viewing Alarms The TransNav GUI displays alarm information for the user to view, analyze, and resolve fault conditions quickly. The alarms shown can be for different levels of object granularity: all nodes, one node, a module, a port, or a service connection termination point (CTP) within an end-to-end transport path. The following procedure describes how to view alarms per callout item in Figure 1-2. Table 1-7 Viewing Alarms Step Procedure 1 Which alarms to view? All nodes. In Map View, click the Alarms tab to view the alarm list and functions. Go to Step 3. Node. In Map View, double-click a node. Module. In Shelf View, select a module. Port. In Shelf View, select a port. Service CTP. Click the Services tab. Right-click on a service and select Show Tx/Rx Path. Select an Active Hop. 2 Click the Alarms tab to view the alarm list and functions. 3 Choose one (or more) of the following viewing functions: Alarm Tallies, go to the next step Detail View, go to Step 5 Map View Display, go to Step 7 New Window, go to Step 8 Print, go to Step 9 Save, go to Step 10 Set Filters, go to Step 11 Sort by Column, go to Step 12 StickyMode, go to Step 13 4 Alarm Tallies Draw your attention to the lower-left corner of the alarm tab to see the alarm tallies as follows: Raised Alarms: The number of alarms raised by the system. Displayed Alarms: The number of alarms in the display list. Go to Step Detail View From the alarm list, select an alarm. Release OPS3.1.x Turin Networks Page 1-15

30 Node Operations and Maintenance Guide, Section 1: Fault Management Viewing Alarms Table 1-7 Viewing Alarms (continued) Step Procedure 6 Click Detail View to display the Alert Detail (View Main) dialog box and view highlighted alarm details. Go to Step Map View Display Draw your attention to the upper half of the GUI screen to see the Map View alarm screen. If a node is in an alarm state, it will be displayed on the Map View node object in the color of the highest level alarm severity with a caption indicating the number and type of alarm. For example, in Figure 1-2, the node TE100SIGTWO has four critical (4C) alarms, so it is colored red with the caption 4C. For definitions of the severity levels, see Alarm Severity Levels, page 1-5. Go to Step New Window From the Alarms tab, click New Window to open a new alarm window. Note: Multiple alarm windows can be opened, each with independently configurable filters. Go to Step Print Click Print to print the contents of the Alarms tab alarms list. Go to Step Save Click Save to save alarm information to a text file. Go to Step 14. Page 1-16 Turin Networks Release OPS3.1.x

31 Chapter 1 Managing Alarms and Events Viewing Alarms Table 1-7 Viewing Alarms (continued) Step Procedure 11 Set Filters From the Alarms tab, click Set Filters to set the alarm filters. Note: Alarms can be filtered by Source, Probable Cause, Time, Severity, and Acknowledged By categories. Go to Step 14. Figure 1-11 Alarm Filter Dialog Box 12 Sort by Column Click a column heading to sort the alarms by that category. The Name, Probable Cause, and AckBy (acknowledged by) columns can be sorted in alphabetical or reverse alphabetical order. The Severity NSA and Severity SA columns can be sorted in ascending or descending severity. The ServiceAffecting and Enabled columns can be sorted by select/clear. Click the column heading again to switch from one sorting category to the other. Go to Step 14. Release OPS3.1.x Turin Networks Page 1-17

32 Node Operations and Maintenance Guide, Section 1: Fault Management Viewing Alarms Table 1-7 Viewing Alarms (continued) Step Procedure 13 StickyMode Selecting this checkbox freezes the current alarm screen. Alarms remain in the order displayed at the time the check box was selected, regardless of a change in severity level. For example, if alarms are currently sorted by decreasing severity level, critical alarms display first, followed by major, minor, and so on. New alarms are not reported, but deleted alarms are removed (when a node is deleted, all of its alarms are deleted). If the StickyMode check box is clear, when a critical alarm is cleared, it is moved to the bottom of the list. If the StickyMode check box is selected, that alarm remains at the top of the list, while its severity would change from Critical to Clear. Turin recommends that you open a new window before you select StickyMode so that new alarms continue to be reported. 14 Do you want to perform another alarm display function? Yes. Go to Step 3. No. The Viewing Alarms procedure is complete. Page 1-18 Turin Networks Release OPS3.1.x

33 SECTION 1FAULT MANAGEMENT Chapter 2 Alarms, Events, and Recommended Actions Introduction During normal operation of the Turin product family, various conditions may arise that require attention by network operations. Events and alarms alert you to Traverse system operational changes. This chapter includes the following alarms, events, and recommended actions. Alarms/Events, A through C, page 1-20 Alarms/Events, D through K, page 1-37 Alarms/Events, L through S, page 1-57 Alarms/Events, TA200, page 1-91 Alarms/Events, TB through TZ, page 1-92 Alarms/Events U through Z, page 1-99 Each alarm or event contains the following information: The alarm or event as viewed on the Alarms or Events tab in the TransNav GUI. The Alarm Profile which contains the alarm or event. This is provided in case you want to change the service affecting status, severity or enabled status of the alarm. Alarm or event definition/probable cause. Alarm or event Service Affecting or Non-Service Affecting status by default on the Alarm Profile. Alarm or event default severity when it is Service Affecting (unprotected), and its severity when it is Non-Service Affecting (protected). Recommended action when the alarm or event is received. Note: The Traverse backplane provides hardware support for sixteen environmental alarm inputs and eight environmental alarm outputs. The environmental telemetry inputs and outputs are supported by the optional Environmental Alarm Module (EAM) located on the main backplane. These alarms are defined using the TransNav management system. Refer to the Traverse Installation and Commissioning Guide or the TraverseEdge 100 User Guide for details on environmental alarm connections. Note: For Loss of Signal alarms, see the information in Section 4 Diagnostics, Chapter 2 Traverse Transmit and Receive Signal Levels, page 4-3 or Chapter 3 TraverseEdge 100 Transmit and Receive Signal Levels, page 4-7. Contact the Turin Technical Assistance Center (TAC) if you need assistance. Release OPS3.1.x Turin Networks Page 1-19

34 Page 1-20 Turin Networks Release OPS3.1.x Alarms/Events, A through C Table 1-8 Alarms, Events and Recommended Actions, A through C Alarm: Definition Alarm Profiles Probable Cause ACO: Alarm Cut Off shelf The audible alarm is cut off (silenced) because the operator pressed the ACO/LED control button. ACO_CLEAR: Clear Alarm Cut Off ADMINTASK 1 : Administrative task AIRCOND: Air Conditioning System Fail Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info (Informational; no action required.) shelf Alarm cutoff is now clear. Info Info (Informational; no action required.) server An administrative task was executed. Info Info (Informational; no action required.) shelf Air conditioning system failed. Minor Minor Check and repair the air conditioning equipment, as necesary. AIRDRYR: Air Dryer Fail shelf Air dryer failed. Minor Minor Check and repair the air dryer equipment, as necesary. AIS-L: Alarm indication signal Line ds1_ptp ds3_ptp (ds_ptp) e3_ptp 1 ta200 te50 shelf sonet_ptp The input signal on a DS1, DS3, or EC-1 interface contains an AIS. The locally received BITS signal contains an AIS. This indicates a remote BITS failure. The locally received OC-N signal contains an AIS. This indicates a remote OC-N level failure. SA ical Critical Check the equipment (module/port) upstream. Clear upstream alarms. SA Critical Minor Check the BITS upstream. Clear upstream alarms. SA Critical Minor Check the equipment (module/port) upstream. Clear upstream alarms. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

35 Release OPS3.1.x Turin Networks Page 1-21 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition AIS-P: Alarm indication signal Path AIS-S 1 : Alarm indication signal Service AIS-V 1 : Alarm indication signal VT Alarm Profiles ds3_ptp (ds_ptp) e3_ptp ta200 te50 sonet_ptp sonet_sts ds3_ptp (ds_ptp) e3_ptp sdh_ptp sonet_ptp sonet_service ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sonet_ptp sonet_vt sonet_sts ta200 te50 Probable Cause The STS signal demultiplexed from the DS3 or EC-1 contains an AIS. This AIS can result from an upstream failure along the STS path. The STS signal demultiplexed from the OC-N/STM-N contains an AIS. This AIS can result from an upstream failure along the STS path. An upstream failure occurred at the Service layer. An upstream failure occurred at the VT path layer. An upstream failure occurred at the VT path layer. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Critical Check the equipment (module/port) upstream. Clear upstream alarms. Verify your payload connections. SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your payload connections. Warning Info Check the equipment upstream. Clear upstream alarms. SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your VT payload connections. SA Critical Critical Check the equipment upstream. Clear upstream alarms. Verify your VT payload connections. sdh_ptp See TU-AIS. n/a n/a n/a See TU-AIS. Recommended Action Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

36 Page 1-22 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition AIS-VC: Alarm indication signal - VC ALS: Automatic laser shutdown ALS-TX-OFF: Transmitter automatically disabled APS-AIS-P 1 : Automatic protection ( multiplex section protection - MSP) Administrative Unit switching Alarm Indication Signal Path APS-LOP-P 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Pointer Path APS-SDBER-P 1 : Automatic protection switching (multiplex section protection - MSP) Signal Degrade Bit Error Rate Path APS-SFBER-P 1 : Automatic protection switching (multiplex section protection - MSP) Signal Fail Bit Error Rate Path Alarm Profiles e1_ptp sdh_ptp ethernet_ptp sdh_ptp sonet_ptp ethernet_ptp sdh_ptp sonet_ptp shelf shelf shelf shelf Probable Cause An upstream failure occurred at the VC path layer. Transmitter of the optical interface has been turned off automatically after detection of LOS on the receiver. Event logged against the optical interface upon ALS alarm condition. A protection switch has occurred due to an AIS-P alarm. A protection switch has occurred due to an LOP-P alarm. A protection switch has occurred because of an SDBER-P alarm. A protection switch has occurred because of an SFBER-P alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your VC payload connections. Critical Minor Transmitter has been shutdown per G.664. Check remote port transmitter state and fiber and resolve LOS condition. Info Info (Informational; no action required.) Info Info See AIS-P. Info Info See LOP-P. Info Info See SDBER-P. Info Info See SFBER-P. Recommended Action Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

37 Release OPS3.1.x Turin Networks Page 1-23 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APS-UNEQ-P 1 : Automatic protection switching (multiplex section protection - MSP) Unequipped (High Order) Path APSAISCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Alarm Indication Signal Clear APSB: Automatic protection switch (multiplex section protection - MSP) byte failure APSBF: Automatic protection switch byte failure APSCFGMIS: Automatic protection switch (multiplex section protection - MSP) configuration mismatch APSCM: Automatic protection switch (multiplex section protection - MSP) channel mismatch APSIMP: Improper automatic protection switching (multiplex section protection - MSP) code Alarm Profiles shelf shelf sonet_ptp sdh_ptp sonet_ptp sdh_ptp sonet_ptp sdh_ptp sonet_ptp sdh_ptp Probable Cause A protection switch has occurred because of an UNEQ STS path alarm. A protection switch which occurred because of an AIS alarm has been cleared. On a 2F BLSR, the APS K1/K2 bytes are in an invalid state. 1+1 linear APS reports this alarm if bidirectional mode is set and K2 bits 6-8 are any of these values: 0,1,2,3. On a 2F BLSR, the local Traverse node is not receiving the K1/K2 values it is expecting. On a 2F BLSR, the automatic protection switching codes are improper. Indicates invalid K bytes. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info See UNEQ-P. Recommended Action Info Info If frequent protection switching occurs, check the revertive WTR period setting. Minor Minor Check for OC-N module failures. Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes. Minor Minor Check that the fiber is connected properly to the remote node. Check that a remote 1+1 linear PG exists. Minor Minor Check for OC-N module failures. Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes. Minor Minor Reseat the modules at the near end and upstream nodes. Examine the incoming SONET overhead with an optical test set to confirm invalid K bytes. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

38 Page 1-24 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APSINC: Inconsistent automatic protection switching (multiplex section protection - MSP) code APSLOPCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Pointer Clear APSLOS 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Signal APSLOSCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Signal Clear APSMM 1 : Automatic protection switch (multiplex section protection - MSP) mode mismatch APSPATHCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Path Clear Alarm Profiles sonet_ptp sdh_ptp shelf shelf shelf sonet_ptp sdh_ptp shelf Probable Cause On a 2F BLSR, the automatic protection switching codes are inconsistent. Three consecutive frames do not contain identical APS bytes, giving the receiving equipment conflicting commands about switching. A protection switch which occurred because of an LOP-P alarm has been cleared. A protection switch has occurred because of an LOS alarm. A protection switch which occurred because of an LOS alarm has been cleared. There is a mismatch of the protection switching schemes at the two ends of the span. A protection switch which occurred because of a path alarm has been cleared. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Minor Minor Check for other alarms, especially BERSD-L and BERSF-L. Clear these alarms. Verify the local receive optical levels, as well as the upstream transmit optical levels. Clean the optical connectors. Reseat the modules at the near end and upstream nodes. Check the protection mode for the far-end node. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info See LOS. Recommended Action Info Info If frequent protection switching occurs, check the revertive WTR period setting. Minor Minor Check protection modes at both ends. Verify that both ends are set for bidirectional or unidirectional. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

39 Release OPS3.1.x Turin Networks Page 1-25 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APSPDI 1 : Automatic protection switching (multiplex section protection - MSP) Path Defect Indication APSPDICLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Path Defect Indication Clear APSREL: Automatic protection switching (multiplex section protection - MSP) release APSSDCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Signal Degrade Clear APSSFCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Signal Fail Clear APSUNEQCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Unequipped Clear Alarm Profiles shelf shelf shelf shelf shelf shelf Probable Cause A protection switch has occurred because of a PDI alarm. A protection switch which occurred because of a PDI alarm has been cleared. The alarm condition that caused an automatic protection switch has been cleared. This occurs when a protection group has been configured as non-revertive. A protection switch which occurred because of an SDBER-P alarm has been cleared. A protection switch which occurred because of an SFBER-P alarm has been cleared. A protection switch which occurred because of an UNEQ STS path alarm has been cleared. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info See PDI. Recommended Action Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info (Informational; no action required.) Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

40 Page 1-26 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APSWTR: Transition to Wait to Restore mode (multiplex section protection - MSP) AU-AIS: Administrative Unit Alarm Indication Signal AU-LOP: Administrative Unit Loss of Pointer AUTHFAIL 1 : OSPF authentication key or type mismatch AUTOPRV 1 : Auto provisioning error Alarm Profiles shelf ds3_ptp sdh_hp sdh_ptp ds3_ptp sdh_hp sdh_ptp shelf sonet_ptp sdh_ptp Probable Cause Traffic is in the process of switching back to working channels. This occurs when a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group has been configured as revertive. The STM signal demultiplexed from the STM-N contains an AIS. This AIS can result from an upstream failure along the STM path. Valid AU pointer bytes are missing from the SDH overhead. An OSPF packet has been received whose authentication key or type conflicts with this node s authentication key or type. A signal failure has occurred on the ring and the user has added new cross-connect data. When the system attempts to auto provision the squelch tables, they cannot be updated, triggering the alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info If frequent protection switching occurs, check the revertive WTR period setting. SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your payload connections. SA Critical Minor Check the cabling and physical connections on the reporting card. Verify cross-connects. Check network timing synchronization. Verify that the expected bandwidth and received bandwidth are the same. If the alarm persists, replace the module. Minor Minor Retry authentication with new key or type. Minor Minor Clear the signal failure. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

41 Release OPS3.1.x Turin Networks Page 1-27 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition AUTO-TX-ON: Transmitter automatically enabled BADPKTRX 1 : Received an OSPF packet that cannot be parsed BATDSCHRG 2 : Battery is discharging Alarm Profiles ethernet_ptp sdh_ptp sonet_ptp Probable Cause Event against the optical interface when the transmitter has been turned on automatically. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info (Informational; no action required.) shelf OSPF packet cannot be parsed. Minor Minor Check configuration and PM. shelf Battery is discharging. Minor Minor Check and follow your method of procedures. BATTERY: Battery has failed shelf Battery has failed. Minor Minor Check and follow your method of procedures. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

42 Page 1-28 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BERSD-L: Bit ErrorRate signal degrade Line ds3_ptp (ds_ptp) e3_ptp 1 shelf te50 Alarm Profiles Probable Cause The BER on the incoming EC-1 line has exceeded the signal degrade threshold. The BER on the incoming BITS has exceeded the signal degrade threshold. sonet_ptp The BER on the incoming OC-N line has exceeded the signal degrade threshold. A connector in the OC-N optical link could be dirty. An OC-N module hardware problem could exist. Fiber could be bent or damaged. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Check cable connectors and module ports. If an EC-1 module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and cable connection. Warning Warning Check cable connectors. SA Warning Warning Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an OC-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and fiber connection. Check fiber for bends or damage. If the problem persists, contact Turin s Customer Service (TAC). Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

43 Release OPS3.1.x Turin Networks Page 1-29 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BERSD-P: Bit Error Rate signal degrade Path Alarm Profiles ds3_ptp (ds_ptp) e3_ptp 1 sonet_ptp sonet_sts Probable Cause The STS signal demultiplexed and dropped from the EC-1 has exceeded its signal degrade threshold. The STS signal demultiplexed and dropped from the OC-N/STM-N has exceeded its signal degrade threshold. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an EC-1 module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an OC-N/STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

44 Page 1-30 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BERSD-V: BitError Rate signal degrade VT Path BERSD-VC: Bit Error Rate signal degrade VC Path Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e3_ptp 1 sonet_ptp sonet_sts sonet_vt shelf The VT signal demultiplexed and dropped from the DS1 has exceeded its signal degrade threshold. The VT signal demultiplexed and dropped from the OC-N has exceeded its signal degrade threshold. SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. sdh_ptp See LP-BERSD. n/a n/a n/a See LP-BERSD. e1_ptp sdh_ptp Probable Cause The VC signal demultiplexed and dropped from the STM-N has exceeded its signal degrade threshold. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

45 Release OPS3.1.x Turin Networks Page 1-31 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BERSF-L: Bit Error Rate signal fail Line ds3_ptp (ds_ptp) e3_ptp 1 shelf te50 Alarm Profiles Probable Cause The BER on the incoming EC-1 line has exceeded the signal fail threshold. The BER on the incoming BITS has exceeded the signal fail threshold. sonet_ptp The BER on the incoming OC-N line has exceeded the signal fail threshold. A connector in the OC-N optical link could be dirty. An OC-N module hardware problem could exist. Fiber could be bent or damaged. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Check cable connectors and module ports. Warning Warning Check cable connectors. SA Warning Warning Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an OC-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and fiber connection. Check fiber for bends or damage. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

46 Page 1-32 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BERSF-P: Bit Error Rate signal fail Path Alarm Profiles ds3_ptp (ds_ptp) e3_ptp 1 sonet_ptp sonet_sts Probable Cause The STS signal demultiplexed and dropped from the EC-1 has exceeded its signal fail threshold. The STS signal demultiplexed and dropped from the OC-N has exceeded its signal fail threshold. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an EC-1 module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an OC-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

47 Release OPS3.1.x Turin Networks Page 1-33 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BERSF-V: Bit Error Rate signal fail VT/VC Path BERSF-VC: Bit Error Rate signal fail VC Path BITSA-FRC: Forced switch - Derived DS1 System BITS 1 Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e3_ptp 1 sonet_ptp sonet_vt sonet_sts shelf The VT/VC signal demultiplexed and dropped from the module has exceeded its signal fail threshold. The VT signal demultiplexed and dropped from the OC-N has exceeded its signal fail threshold. The VT signal demultiplexed and dropped from the OC-N has exceeded its signal fail threshold. SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. sdh_ptp See LP-BERSF. n/a n/a n/a See LP-BERSF. e1_ptp sdh_ptp Probable Cause The VC signal demultiplexed and dropped from the STM-N has exceeded its signal fail threshold. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. shelf A forced switch is in process. Warning Warning Clear the Forced switch command. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

48 Page 1-34 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BITSA-LOCK: Lockout - Derived DS1 System BITS 1 BITSA-MAN: Manual switch - Derived DS1 System BITS 1 BITSB-FRC: Forced switch - Derived DS1 System BITS 2 BITSB-LOCK: Lockout - Derived DS1 System BITS 2 BITSB-MAN: Manual switch - Derived DS1 System BITS 2 shelf A lockout is in process on this timing reference. Warning Warning Clear the Lockout switch command. shelf A manual switch is in process. Warning Warning Clear the Manual switch command. shelf A forced switch is in process. Warning Warning Clear the Forced switch command. shelf A lockout is in process on this timing reference. Warning Warning Clear the Lockout switch command. shelf A manual switch is in process. Warning Warning Clear the Manual switch command. BITSGEN 1 : BITS event shelf Unused. Info Info Unused. BITSRBOC 1 : BITS RBOC detect shelf Unused. Info Info Unused. BLSR_NOT_SYNC: BLSR ring is out of sync BLSR_SYNC_UNKNOWN: BLSR unknown error server server BOARDFAIL: Board failure alarm ta200 Alarm Profiles Probable Cause One of the nodes in the BLSR/MS-SPRing is out of sync with the other nodes in the ring possibly due to invalid K bytes. BLSR/MS-SPRing synchronization status is unknown. The OMX3 or PM13 board may not be seated correctly in the chassis or has failed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical Check for OC-N/STM-N module failures. Examine the incoming SONET/SDH overhead with an optical test set to confirm inconsistent or invalid K bytes. Issue an init command to re-initialize the ring. Warning Warning Check for OC-N/STM-N module failures. Examine the incoming SONET/SDH overhead with an optical test set to confirm inconsistent or invalid K bytes. Issue a sync command to re-synchronize the ring. SA Critical Critical Check that the module is inserted correctly into the chassis. Otherwise, run diagnostics to test the state of the module. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

49 Release OPS3.1.x Turin Networks Page 1-35 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BPSIG: The backplane cannot communicate with other modules CFGERR 1 : OSPF configuration parameter mismatch) shelf Module defect. Backplane slot defect. shelf A packet was received whose configuration parameters conflict with the node s configuration parameters. CLEAR: Clear switch request shelf A Clear switch command has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. CLFAIL: Cooling fan failure shelf The cooling fan or the power source may have a defect. SA Critical Minor Replace the module. If the same alarm persists, try another slot in the shelf. Minor Minor Check the configuration. Info Info (Informational; no action required.) Minor Minor Check the state of the cooling fan or the power. CLFAN: Fan failed shelf The cooling fan is defective. Minor Minor Check the state of the cooling fan or the power source. Replace the fan unit, as necesary. CLRLOOP: Clear loopback Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp ethernet_ptp sonet_ptp sdh_ptp COM: Communication failure server The management server cannot synchronize with the node. ta200 te50 Probable Cause A loopback has been cleared. Warning Warning (Informational; no action required.) The management server cannot synchronize with the node. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Check that the node name was entered exactly as configured with the node-level CLI (the node name is case-sensitive). SA Warning Warning Check that the node name was entered exactly as configured with the node-level CLI (the node name is case-sensitive). Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

50 Page 1-36 Turin Networks Release OPS3.1.x Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition CONTROL: Control alarm on MPS IM te50 The control signal is not present. SA Critical Critical Check connectivity and the multi-protocol serial (MPS) interface module (IM) alarm monitor configuration. CTS: Clear to send on MPS IM te50 A clear to send (CTS) signal is not yet received on the MPS IM alarm monitoring system. 1 Not supported in this release. Alarm Profiles 2 Environmental alarm inputs are customized by each operator. Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical Check connectivity and configuration. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

51 Release OPS3.1.x Turin Networks Page 1-37 Alarms/Events, D through K Table 1-9 Alarms, Events and Recommended Actions, D through K Alarm: Definition DBCRPT: Database corruption DBFAIL: Database failed DBMIS: Database version mismatch DBRED: Redundant Database failed Alarm Profiles server shelf server shelf server shelf server shelf Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action The active database fails to start. Minor Minor This alarm will not be visible due to action taken by the software to recover from this condition. If the alarm generates, contact Turin s Customer Service (TAC). A failure has occurred on the active database upon GCM initialization or some other temporary loss of connectivity. The database is inaccessible as a result of connection failures or abnormal shutdown of database software. The database engine software version is incompatible with the node software as a result of improper upgrade of software. This condition will not occur during normal upgrade. Some database operations will fail, but the node is still usable. A redundant database failure has occurred as a result of a standby GCM reboot, a connection failure, or abnormal shutdown of database software. SA Critical Minor If this condition does not resolve itself in a few minutes, corrective action must be taken. Reboot the active GCM. If no resolution, contact Turin s Customer Service Technical Assistance Center (TAC). SA Critical Minor Verify that the software version is correct. Contact Turin s Customer Service (TAC). SA Minor Minor If the standby GCM is rebooting, the condition will clear when the active GCM goes hot. Otherwise, reboot the standby GCM and allow time for the GCMs to go hot. If no resolution, contact Turin s Customer Service (TAC). Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

52 Page 1-38 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DBSIGN: Database signature mismatch DCCFAIL: Data Communications Channel fail Alarm Profiles ds3_ptp e1_ptp e3_ptp ethernet_ptp sdh_ptp sonet_ptp server shelf ta200 te50 ds3_ptp (ds_ptp) ds3_ptp (ds_ptp) e3_ptp 1 sonet_ptp sonet_sts sdh_hp sdh_lp sdh_ptp The database content does not match the node commissioning parameter values. The database is unusable. The commissioning parameters may have not been provisioned. A GCM may have been moved from one node to another node. This alarm is only visible via the node-level CLI when TransNav server will not connect to the node due to improper commissioning. SA Major Minor If the TransNav server connects, and this alarm is present, verify commissioning parameters, then reboot the node. If the TransNav server does not connect to the node, use the Craft port on the active GCM to commission the node via CLI, verify commissioning parameters, then reboot the node. Not supported on EC-1. SA Major Major Not supported; no action required. Probable Cause The DCC on the incoming OC-N has failed. The OC-N port is not connected or the fiber is cut along the path. The remote link is not active. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Major Minor Check the OC-N interface. Check for a fiber cut and OC-N LOS alarms. Verify the remote OC-N interface has Control Data enabled and is active. Filter local alarms as necessary until remote link comes active. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

53 Release OPS3.1.x Turin Networks Page 1-39 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DOWN 1 : Out of service DQL 1 : Degraded quality level DS1AIS: Alarm indication signal - DS1 Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp ethernet_ptp server shelf sonet_ptp sdh_ptp sonet_service ta200 te50 ds3_ptp ds_ptp e3_ptp shelf sonet_ptp sdh_ptp ds1_ptp ta200 te50 Probable Cause Unused. Minor Minor Unused. The incoming signal has a degraded quality level. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check and clean connections. The DS1 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. DS1LOF: Loss of frame - DS1 ds1_ptp The DS1 input contains a LOF. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. DS1LOS: Loss of signal - DS1 ds1_ptp The DS1 input contains an LOS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

54 Page 1-40 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DS1RAI: Remote alarm indication DS3AIS: Alarm indication signal - DS3 DS3RAI: Remote alarm indication ds1_ptp te50 ds3_ptp ds_ptp ta200 te50 ds3_ptp ds_ptp ta200 te50 The far-end node has detected a defect signal on an incoming DS1. The local node is sending a bad DS1 signal towards the DS-X. Warning Warning Verify that the connections between the DS-X and the DS1 module are secure. Verify that the DS1 signal entering the far end of the SONET network is error-free. The DS3 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. The far-end node has detected a defect signal on an incoming DS3. The local node is sending a bad DS3 signal towards the DS-X. DSR: Data set ready on MPS IM te50 The data set ready signal is not yet received on the MPS IM alarm monitoring system. DTR:Data terminal ready on MPS IM E1AIS: Alarm indication signal - E1 E1LOMCAS: Alarm indication signal - E1 E1LOMCRC: Alarm indication signal - E1 Alarm Profiles te50 e1_ptp ta200 te50 Probable Cause The data terminal ready signal is not yet received on the MPS IM alarm monitoring system. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Warning Warning Verify that the connections between the DS-X and the DS3 module are secure. Verify that the DS3 signal entering the far end of the SONET network is error-free. SA Critical Critical Check the node, connectivity, and the configuration. SA Critical Critical Check the DTE and modem connectivity and the configuration. The E1 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. e1_ptp Loss of Multiframe CAS. Critical Critical Check the interface. e1_ptp Loss of Multiframe CRC. Critical Critical Check the interface. Recommended Action Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

55 Release OPS3.1.x Turin Networks Page 1-41 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition E1RAI: Remote alarm indication E3 AIS: Alarm indication signal - E3 E3 RAI: Remote alarm indication e1_ptp The far-end node has Warning Warning Verify that the connections between the detected a defect signal on E-X and the E1 module are secure. te50 an incoming E1. SA Critical Critical Verify that the E1 signal entering the far The local node is sending a end of the SDH network is error-free. bad E1 signal towards the E-X. e3_ptp The E3 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. e3_ptp The far-end node has detected a defect signal on an incoming E3. The local node is sending a bad E3 signal towards the E-X. EFMFAIL: EFM failure shelf EFM (ingress or egress) failure; parity or other error. Warning Warning Verify that the connections between the E-X and the E3 module are secure. Verify that the E3 signal entering the far end of the SDH network is error-free. SA Critical Critical Reboot card and consult Turin s Customer Service (TAC), if alarm persists. ENGINE: Engine failure shelf Internal queue engine failure. Minor Minor Reboot card and consult Turin s Customer Service (TAC), if alarm persists. ENGOPRG: Engine operating shelf Internal queue engine is operating again. EQCOMM 1 : Communication link failed EQFRCSW 1 : Forced protection switch Equipment Alarm Profiles Minor Minor Monitor for further internal queue engine failures. shelf The link is down. SA Critical Critical Check the link connections. shelf Probable Cause A forced protection switch command has been executed on a 1:1 equipment protection group. EQINV: Equipment invalid shelf An invalid piece of equipment has been used. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning If the reason for executing the forced switch command no longer exists, clear the switch command. Critical Critical Plug in a valid piece of equipment. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

56 Page 1-42 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition EQLOCK 1 : Protection lockout Equipment EQMANSW 1 : Manual protection switch Equipment shelf shelf A lockout protection switch command has been executed on a 1:1 equipment protection group. A manual protection switch command has been executed on a 1:1 equipment protection group. EQMIS: Equipment mismatch shelf Type of equipment plugged in does not match the provisioned type or the module is not allowed in the slot. Note: GCM, Enhanced GCM, and GCM with integrated optics are considered different module types. EQPT: Equipment malfunction / failure. Alarm Profiles Warning Warning If the reason for executing the lockout switch command no longer exists, clear the switch command. Warning Warning If the reason for executing the manual switch command no longer exists, clear the switch command. SA Critical Minor Determine if the TransNav server or the node contains the correct module configuration. Please refer to Appendix A Module Placement Planning and Guidelines for module placement details. If the TransNav server contains the correct module configuration, replace the module with the correct module type. The alarm should be cleared. If the node contains the correct module configuration, lock, restart, and delete the module. During auto discovery, the correct configuration information will be forwarded to the TransNav server and the alarm should be cleared. server A hardware failure has occurred. SA Critical Critical Check and reseat equipment. If this fails to clear the alarm, replace the equipment if necessary. shelf Probable Cause A hardware failure has occurred on the reporting module. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Reseat the module. If this fails to clear the alarm, replace the module if necessary. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

57 Release OPS3.1.x Turin Networks Page 1-43 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition EQRMV: Equipment removed shelf A module is not properly seated or it has been removed. ERFI-V: Enhanced (two bit) Remote failure indication VT Path EXER_SWITCH: Exercise switch on remote node ds1_ptp The VT signal demultiplexed from the DS1 contains ERFI-V (RFISVR-V, RFICON-V, and RFIPAY-V.) The far-end node has detected path defects coming from the local site. shelf Checking status of remote node via exercise command (using K1/K2 bytes) for 1+1 bidirectional protection group. SA Critical Minor Plug in the correct module or delete the module using the TransNav system if that slot is not being used. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms such as LOP-V, AIS-V, PLM-V, TIM-V, and UNEQ-V from the far-end node. Info Info (Informational only; no action required.) EXPLGS: Explosive gas shelf Explosive gas detected. Minor Minor Check and follow your method of procedures. EXTA-REF1-ALM: Primary reference in alarm EXTA-REF2-ALM: Secondary reference in alarm Alarm Profiles shelf shelf Probable Cause Primary reference for Derived DS1 System SASE 1 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Secondary reference for Derived DS1 System SASE 1 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

58 Page 1-44 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition EXTA-REF3-ALM: Third reference in alarm EXTA-REF4-ALM: Fourth reference in alarm EXTB-REF1-ALM: Primary reference in alarm. EXTB-REF2-ALM: Secondary reference in alarm EXTB-REF3-ALM: Third reference in alarm EXTB-REF4-ALM: Fourth reference in alarm Alarm Profiles shelf shelf shelf shelf shelf shelf Probable Cause Third reference for Derived DS1 System SASE 1 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Fourth reference for Derived DS1 System SASE 1 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Primary reference for Derived DS1 System SASE 2 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Secondary reference for Derived DS1 System SASE 2 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Third reference for Derived DS1 System SASE 2 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Fourth reference for Derived DS1 System SASE 2 is alarmed due to source signal failure or unavailability due to an LOS, LOF or AIS-L alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

59 Release OPS3.1.x Turin Networks Page 1-45 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FANCOMM: Fan tray communication failure shelf Communication failure with the fan tray. FANCOND: Fan tray condition shelf EEPROM failure or thermistor failure. FANFLTR: Fan filter shelf Temperature has exceeded 49 ºC. Minor Minor Reseat the fan tray. Warning Warning Replace the fan tray. Minor Minor Check that the temperature of the room is not abnormally high. Replace the fan tray air filter. FANRMV: Fan tray removed shelf Fan tray has been removed. Minor Minor Install the fan tray. FEP 1 : Far-end protection failure FILE_UPLOAD: Single file transfer Alarm Profiles sonet_ptp sdh_ptp Probable Cause An APS switching channel signal failure has occurred on the protect module coming into the node. Minor Minor Check the equipment on the other end of the fiber. shelf File upload is in process. Info Info (Informational only; no action required.) FIRDETR: Fire detector failure shelf Fire detection equipment has failed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check fire detection equipment and power source. Check and follow your method of procedures. FIRE 2 : Fire shelf Fire detected. Minor Minor Check and follow your method of procedures. FLOOD 2 : Flood shelf Flood detected. Minor Minor Check and follow your method of procedures. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

60 Page 1-46 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FLOW-DEGRADED: VPG Degraded Flow FLOW-LEARNED: Learned VLAN Flow FLOW-UNLEARNED: Unlearned VLAN Flow FLOWS-UNLEARNED: Unlearned All VLAN Flows FLOW-UNPROTECTED: VPG Unprotected Flow FOPR: Failure of protocol - receive FOPT: Failure of protocol - transmit Alarm Profiles ethernet_ptp ethernet_ptp ethernet_ptp ethernet_ptp ethernet_ptp eos sdh_eos eos sdh_eos Probable Cause The system is currently forwarding a Poor, Lost, or Null copy of a learned flow. Note: Flow alarms are received on the working port of the Virtual Protection Group (VPG). The system has learned a VLAN flow. The system has unlearned a single VLAN flow either automatically or through an operator request. The system has unlearned all the VLAN flows through an operator request. The system is currently forwarding a Good copy of a learned flow when the status of the flow on the other port in the VPG is anything other than Good. Note: Flow alarms are received on the working port of the VPG. LCAS has detected unexpected behavior by the remote LCAS peer. LCAS has detected unexpected behavior by the remote LCAS peer. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Major Major The system clears flow-related alarms once it unlearns the flow. Info Info (Informational only; no action required.) Info Info (Informational only; no action required.) Info Info (Informational only; no action required.) Minor Minor The system clears flow-related alarms once it unlearns the flow. SA Critical Critical Check remote peer for proper configuration. SA Critical Critical Check remote peer for proper configuration. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

61 Release OPS3.1.x Turin Networks Page 1-47 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FORCE_ONLINE ta200 The selected module is forced online. A 50 ms hit occurs on the T1 traffic during the switch. Redundancy is disabled while a force protection switch is active. Any failures to the on-line module are not protected. Therefore, the status LED will be turned yellow to indicate a maintenance condition is active. FORCED: Forced protection switching FORCED_ON_PROT: Forced protection switch on protecting unit FORCED_ON_SECT1: Forced protection switch on optimized 1+1 APS working section 1 Alarm Profiles shelf shelf shelf Probable Cause A forced protection switch has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. A forced protection switch has been performed on a protection group. A forced switch has been performed on the optimized 1+1 APS bi-directional working section 1. Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

62 Page 1-48 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FORCED_ON_SECT2: Forced protection switch on optimized 1+1 APS working section 2 FORCED_ON_WORK: Forced protection switch on working unit FORCED-EAST: Forced switch applied on east facility FORCED-WEST: Forced switch applied on wast facility Alarm Profiles shelf shelf shelf shelf Probable Cause A forced switch has been performed on the optimized 1+1 APS bi-directional working section 2. Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge. A forced protection switch has been performed on the working unit. A forced protection switch has been performed on the east facility. A forced protection switch has been performed on the west facility. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. FUSE: Fuse failure shelf A fuse has failed. Minor Minor Check and follow your method of procedures. GENFAIL 2 : Generator failure shelf Generator has failed. Minor Minor Check and follow your method of procedures. GFPLOF: Loss of frame shelf Generic Framing Procedure (GFP) framing problem on the incoming bit stream. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Inspect all VC bundle facilities. Check remote sites for module removal/failure alarms or disabled Ethernet transmitter. Check the cable and interface. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

63 Release OPS3.1.x Turin Networks Page 1-49 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition GIDERR: LCAS group ID mismatch GIDM: Group ID mismatch H4-LOM: H4 Loss of multiframe Alarm Profiles shelf eos sdh_eos ds3_ptp sdh_hp sdh_lp sdh_ptp sonet_ptp sonet_sts Probable Cause A link capacity adjustment scheme (LCAS) group ID member of the VC bundle shows one of the following conditions are present on the path: LOP. LOM. AIS. LOS. The VC bundle continues to operate. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Inspect all VC bundle facilities. Check remote sites for module removal/failure alarms or disabled Ethernet transmitter. Check the cable and interface. Group ID mismatch. SA Critical Critical The expected group ID does not match the received group ID. H4 Loss of multiframe. SA Critical Minor Incoming STS should contain VTs. HIAIR: High airflow shelf High airflow detected. Minor Minor Check and follow your method of procedures. HIHUM: High humidity shelf Humidity is too high. Minor Minor Check and follow your method of procedures. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

64 Page 1-50 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition HITEMP: High temperature shelf Temperature is too high. Minor Minor Check that the temperature in the room is not abnormally high. Ensure that nothing prevents the fan tray from passing air through the Traverse shelf. Ensure that blank faceplates are inserted in empty slots in the Traverse shelf. Blank faceplates help airflow. Check the condition of the air filter to see if it needs replacement. If the filter is clean, take the fan tray assembly out of the Traverse shelf. Reinsert the fan tray, making sure the back of the fan tray connects to the rear of the Traverse shelf. If the fan does not run or the alarm persists, replace the fan tray. HIWTR: High Water shelf The water level has exceeded the threshold. HP-BERSD: Bit error rate signal degrade - High order Path Alarm Profiles ds3_ptp sdh_hp sdh_ptp Probable Cause The STM signal demultiplexed and dropped from the STM-N has exceeded its signal degrade threshold. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check and follow your method of procedures. Warning Warning Examine the network for other high order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

65 Release OPS3.1.x Turin Networks Page 1-51 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition HP-BERSF: Bit error rate signal degrade - High order Path HP-LOM: High order path Loss of multiframe HP-MND: High order path Member not deskewable HP-SQM: High order path Sequence ID mismatch HP-PLM: Payload label mismatch received - High order Path Alarm Profiles ds3_ptp sdh_hp sdh_ptp sdh_eos sdh_eos_ctp sdh_eos sdh_eos_ctp sdh_eos sdh_eos_ctp ds3_ptp sdh_hp sdh_ptp The STM signal demultiplexed and dropped from the STM-N has exceeded its signal fail threshold. An error is detected in the paths multiframe indicator. Differential Delay exceeded on EOS member and the member was removed from the group. The member sequence number is in error. Probable Cause Invalid C2 byte (signal label byte) in the SDH path overhead. The payload does not match what the signal label is reporting. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Examine the network for other high order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. SA Critical Critical This is an eos_ctp member alarm. If not using LCAS, check that EOS member order matches that of the remote EOS. SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them. SA Critical Critical This is an eos_ctp member alarm. If non-lcas, check that the order of members in the remote EOS matches the local order SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

66 Page 1-52 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition HP-RDI: Remote Defect Indication - High order Path HP-RFI: Remote Failure Indication - High order Path HP-RFICON: Remote failure indication, connectivity defect - High order Path HP-RFIPAY: Remote failure indication, payload defect - High order Path HP-RFISVR: Remote failure indication, server defect - High order Path HP-TIM: Trace identifier mismatch - High order Path Alarm Profiles ds3_ptp sdh_hp sdh_ptp sdh_hp sdh_ptp ds3_ptp sdh_hp sdh_ptp ds3_ptp sdh_hp sdh_ptp ds3_ptp sdh_hp sdh_ptp ds3_ptp sdh_hp sdh_ptp Valid STM-N framing is not detected or AU-AIS (or MS-AIS) is received from the source. Probable Cause The signal demultiplexed from the STM-N contains a remote failure indication. The far-end node has detected path defects coming from the local site. Far end path has an HP-UNEQ or HP-TIM alarm. Far end path has a HP-PLM alarm. Far end path has an AU-AIS or AU-LOP alarm. The expected path trace string (J1 byte in the SDH path overhead) does not match the received path trace string. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Check STM-N framing source. See AU-AIS. See MS-AIS. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms from the far-end node. Warning Warning Verify your payload connections. Check for far end alarms, especially HP-UNEQ and HP-TIM. Refer to the recommended actions for HP-UNEQ and HP-TIM. Warning Warning Verify your payload connections. Check for far end alarms, especially HP-PLM. Refer to the recommended actions for HP-PLM. Warning Info Verify your payload connections. Check for far end alarms, especially AU-AIS and AU-LOP. Refer to the recommended actions for AU-AIS and AU-LOP. SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

67 Release OPS3.1.x Turin Networks Page 1-53 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition HP-UNEQ: Unequipped - High order Path ds3_ptp sdh_hp sdh_ptp No payload is received on an activated service. SA Critical Minor Check your connection. Connect your proper payload. Check the service source. HWFAULT: Hardware fault shelf A hardware fault has occurred. SA Critical Critical See Figure 1-12 Hardware Fault Detection Descriptions, page 1-55 for further details. Take appropriate action, as necessary. IDLE: Idle signal detection INCOMPATSW: Incompatible software Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp server shelf Probable Cause Service is not provisioned over the interface. Software is incompatible between modules that are attempting communication with each other. Service Affecting Default Default Severity SA (Unprotected) INTRUDER: Intrusion shelf Minor Minor NSA (Protected) Recommended Action SA Warning Warning Check the interface. Check the far-end node. Critical Critical Check the current software versions and compatibility IDs of the modules. One module s current software version must be at least the compatibility ID (the lowest software version the other module can work with) of the other module. Perform software upgrade as necessary for software compatibility. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

68 Page 1-54 Turin Networks Release OPS3.1.x Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition INDICATION: Indication Alarm on MPS IM KBYTE: Default K byte 1 Not supported in this release. Alarm Profiles te50 SA Critical Critical sonet_ptp sdh_ptp 2 Environmental alarm inputs are customized by each operator. Probable Cause Far end protection mode mismatch. K1/K2 bytes not sent. For example, a BLSR may have one node configured as a UPSR, and a node in a UPSR would not send the two valid K1/K2 bytes expected by a BLSR system. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check protection mode for far-end node. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

69 Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K Figure 1-12 Hardware Fault Detection Descriptions Release OPS3.1.x Turin Networks Page 1-55

70 Node Operations and Maintenance Guide, Section 1: Fault Management Page 1-56 Turin Networks Release OPS3.1.x

71 Release OPS3.1.x Turin Networks Page 1-57 Alarms/Events, L through S Table 1-10 Alarms, Events and Recommended Actions, L through S Alarm: Definition LBC: TXlaser bias current threshold violation LBCNRML 1 : Laser bias current normalized threshold crossing alert. Alarm Profiles ethernet_ptp sdh_ptp sonet_ptp shelf Probable Cause TXlaser bias current threshold violation. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Warning Warning Check laser bias. Recommended Action shelf Power level out of range. Warning Warning Measure power level using optical power meter; replace module if below threshold. LCAS-REM: LCAS remove vc bundle Ethernet over SONET (EOS) event to indicate a failed member was removed from operation in an LCAS-enabled VC bundle. (Location: Near-end, Direction: received) LCAS-RES: LCAS restore vc bundle EOS event to indicate member was restored to operation in an LCAS-enabled VC bundle. (Location: Near-end, Direction: received) Info Info Check for LCAS (GIDERR, SSF) or member path alarms and proceed as directed. Info Info (Informational; no action required.) LEAK 2 : Leak shelf Leak detected. Minor Minor Check and follow your method of procedures. LFD: Loss of Frame Delineation eos sdh_eos GFP has lost sync. SA Critical Critical Check the paths associated with the EOS members for alarms. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

72 Page 1-58 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LINKFAIL: Link failure ethernet_ptp Transmitter/receiver failure. Fiber connection lost. A module along the path has been removed. LINK_FRCD_DIS: Duplex mode mismatch LNKBCPTY 3 : Link broadcast message parity error LNKBLKCNT 3 : Link block count error Alarm Profiles ethernet_ptp Probable Cause There is a Duplex mode port parameter mismatch between the near- and far-end Ethernet ports. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Critical Check connectors, cables, and modules. Check Ethernet port configuration, Integrity Status parameter for details. See TransNav Management System GUI Guide, Section 5 Equipment, Chapter 4 Ethernet Equipment, Ethernet Equipment, page SA Critical Critical Check the Duplex mode of the Ethernet interfaces. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. Recommended Action Alarm clearing criteria: First, at the Turin Ethernet interface: Lock the offending Ethernet interface. Then, at the link partner interface: Lock the offending Ethernet interface. Turn off auto-negotiation. Set the Duplex parameter to forced half-duplex mode. Then, at the Turin Ethernet interface: Unlock the offending Ethernet interface. Finally, at the link partner interface: Unlock the offending Ethernet interface. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

73 Release OPS3.1.x Turin Networks Page 1-59 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LNKBLKPTY 3 : Link block parity error shelf Unused. Minor Minor Unused. LNKCRC 3 : Link CRC error shelf Unused. Minor Minor Unused. LNKCSUM 3 : Link checksum error shelf Unused. Minor Minor Unused. LNKDOWN 3 : Link down shelf Unused. Info Info Unused. LNKERR 3 : Unrecognized link error shelf Unused. Minor Minor Unused. LNKOVFL 3 : Link overflow shelf Unused. Minor Minor Unused. LNKPAPTY 3 : Link path alarm parity error LNKRXCORR 3 : Link receive corruption LNKRXDROP 3 : Link receive drop LNKRXLEN 3 : Link receive length error LNKRXSTAT 3 : Link receive stat count error LNKTXCORR 3 : Link transmit corruption LNKTXDROP 3 : Link transmit drop Alarm Profiles Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. Recommended Action LNKUP 1 : Link up shelf The link is now up. Info Info (Informational; no action required.) Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

74 Page 1-60 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LO-LBC: TX laser bias current exceeds low alarm threshold LO-OPR: Optical power received exceeds low alarm threshold LO-OPT: Optical power transmitted exceeds low alarm threshold LO-TEMP: Internal temp exceeds low alarm threshold LO-VCC: Internal voltage exceeds low alarm threshold LOA: Loss of Assignment LOCKOUT 4 : Lockout automatic protection switching Alarm Profiles sonet_ptp sonet_ptp sonet_ptp sonet_ptp sonet_ptp eos sdh_eos shelf Probable Cause SFP optic alarm. Set when TX Bias current is below low alarm level as a result of a possible component failure. SFP optic alarm. as a result of a possible input level problem at the patch panel OR the need to clean the fibers. SFP optic alarm. Set when TX Bias current is below low alarm level as a result of a possible component failure. SFP optic alarm. Set when internal temperature is below low alarm level as a result of a possible component failure. SFP optic alarm. Set when internal supply voltage is below low alarm level as a result of a possible component failure. Differential Delay exceeded on active EOS member. A lockout protection switch command has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Contact Turin s Customer Service (TAC). Warning Warning Check receive input level at patch panel. Clean fibers if necessary. Warning Warning Contact Turin s Customer Service (TAC). Warning Warning Contact Turin s Customer Service (TAC). Warning Warning Contact Turin s Customer Service (TAC). SA Critical Critical Check the EOS member status to determine which paths have exceeded the delay and reroute them. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

75 Release OPS3.1.x Turin Networks Page 1-61 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOCKOUT-LPS: Lockout of Protection Ring LOCK_WORK1: Lockout automatic protection switching LOCK_WORK10: Lockout automatic protection switching LOCK_WORK11: Lockout automatic protection switching LOCK_WORK12: Lockout automatic protection switching LOCK_WORK13: Lockout automatic protection switching Alarm Profiles shelf shelf shelf shelf shelf shelf Probable Cause A lockout protection ring command has been performed on a BLSR protection ring. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Clear Lockout Protection Ring from the BLSR protection group. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

76 Page 1-62 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOCK_WORK14: Lockout automatic protection switching LOCK_WORK2: Lockout automatic protection switching LOCK_WORK3: Lockout automatic protection switching LOCK_WORK4: Lockout automatic protection switching LOCK_WORK5: Lockout automatic protection switching LOCK_WORK6: Lockout automatic protection switching Alarm Profiles shelf shelf shelf shelf shelf shelf Probable Cause A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

77 Release OPS3.1.x Turin Networks Page 1-63 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOCK_WORK7: Lockout automatic protection switching LOCK_WORK8: Lockout automatic protection switching LOCK_WORK9: Lockout automatic protection switching Alarm Profiles shelf shelf shelf Probable Cause A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

78 Page 1-64 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOF: Loss of frame LOG: Loss of Group Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp ta200 te50 ethernet_ptp shelf sonet_ptp sdh_ptp eos sdh_eos Probable Cause Framing problem on the incoming signal. Generic Framing Procedure (GFP) framing problem on the incoming bit stream. Framing problem on the incoming BITS. Framing problem on the incoming OC-N signal. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical Inspect all facilities related to the STS link. Check remote sites for module removal/failure alarms. Check the cable and interface. SA Major Major Inspect all facilities related to the STS Bundle. Check remote sites for module removal/failure alarms or disabled Ethernet transmitter. Check the cable and interface. Minor Minor Inspect all facilities related to the BITS. Check remote sites for BITS alarms. Check the cable connection. SA Critical Minor Inspect all facilities related to the OC-N link. Verify the local receive optical levels, as well as the upstream transmit optical levels. Clean the optical connectors. Check the upstream node for OC-N module failure/removal. Verify good optical connections to the local and far-end OC-N modules. Loss of Group. SA Critical Critical Check the paths associated with the EOS members for alarms. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

79 Release OPS3.1.x Turin Networks Page 1-65 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOGINFAIL: Login failed LOGINSUCC: Login successful LOGINTERM: Login terminated server shelf server shelf server shelf Login attempt has failed. Info Info Try again. Check the login log; contact your system administrator persistent login failures could indicate possible hacking. Login has succeeded. Info Info (Informational; no action required.) Login has terminated. Info Info (Informational; no action required.) LOL: Loss of link te50 SA Critical Critical LOM 1 : Loss of Multiframe, Rx path LOM-P: Loss of Multiframe synchronization - STS LOM-V: Loss of Multiframe synchronization - VT Alarm Profiles ethernet_ptp sdh_ptp shelf Unused. SA Critical Minor Unused. te50 SA Warning Warning eos eos_ctp eos eos_ctp Probable Cause An error is detected in the paths multiframe indicator. An error is detected in the paths multiframe indicator. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical This is an eos_ctp member alarm. If not using LCAS, check that EOS member order matches that of the remote EOS. SA Critical Critical This is an eos_ctp member alarm. If not using LCAS, check that EOS member order matches that of the remote EOS. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

80 Page 1-66 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOP-P: Loss of Pointer Path LOP-V 1 : Loss of Pointer VT Alarm Profiles ds3_ptp (ds_ptp) e3_ptp sonet_ptp sonet_sts Valid H1/H2 pointer bytes are missing from the STS path overhead. SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. Verify that the expected bandwidth and received bandwidth are the same. If the alarm persists, replace the module. ethernet_ptp 1 Valid pointer bytes are missing. SA Critical Minor Check the cabling and physical connections on the reporting module. ta200 te50 ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sonet_ptp sonet_vt sonet_sts ta200 te50 Probable Cause Valid pointer bytes are missing. SA Critical Critical Check the cabling and physical connections on the reporting module. Valid pointer bytes are missing from the VT overhead. Valid pointer bytes are missing from the VT overhead. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. SA Critical Critical Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. sdh_ptp See TU-LOP. n/a n/a n/a See TU-LOP. Recommended Action Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

81 Release OPS3.1.x Turin Networks Page 1-67 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOP-VC 1 : Loss of Pointer VC LOS: Loss of signal Alarm Profiles e1_ptp sdh_ptp ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp ta200 te50 Valid pointer bytes are missing from the VC overhead. Loss of signal on a port interface input. The cabling may not be correctly connected to the module, or no signal exists on the line. Upstream equipment failure or cable cut may cause this alarm. SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. SA Critical Critical Check the cable and interface. Verify that the port is in service. Use a test set to confirm that a valid signal exists on the line. shelf Loss of signal on BITS 1 or 2. Minor Minor Check the cable and interface. sonet_ptp sdh_ptp Probable Cause OC-N loss of signal. Fiber may not be correctly connected to the module, or no signal exists on the line. Upstream equipment failure or fiber cut may cause this alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check the upstream node for OC-N module failure/removal. Check the fiber connection. Verify the receive optical levels. Verify good optical connections to the local and far-end OC-N modules. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

82 Page 1-68 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LP-BERSD: Bit error rate signal degrade - Low order Path LP-BERSF: Bit error rate signal degrade - Low order Path LPBKEQPT: Equipment loopback active Alarm Profiles sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp ds1_ptp ds3_ptp e1_ptp ethernet_ptp sdh_ptp sonet_ptp Probable Cause The STM signal demultiplexed and dropped from the STM-N has exceeded its signal degrade threshold. The STM signal demultiplexed and dropped from the STM-N has exceeded its signal fail threshold. Equipment is in active loopback state. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Examine the network for other low order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Warning Warning Examine the network for other low order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Warning Warning Validate this state. Clear loopback, as required. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

83 Release OPS3.1.x Turin Networks Page 1-69 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LPBKFACILITY: Facility loopback active LPBKINBAND: Inband loopback active LPBKTERM: Terminal loopback active LP-LOM: Low order path Loss of multiframe synchronization LP-MND: Low order path Member not de-skewable Alarm Profiles ds1_ptp ds3_ptp e1_ptp e3_ptp ethernet_ptp sdh_ptp shelf sonet_ptp Facility is in active loopback state. Warning Warning Validate this state. Clear loopback, as required. ds3_ptp An inband loopback is active. Warning Warning Validate this state. Clear loopback, as required. ds1_ptp ds_ptp e1_ptp e3_ptp ethernet_ptp sdh_ptp shelf sonet_ptp sdh_eos sdh_eos_ctp sdh_eos sdh_eos_ctp Probable Cause A terminal loopback is active. Warning Warning Validate this state. Clear loopback, as required. An error is detected in the paths multiframe indicator. Differential Delay exceeded on EOS member and the member was removed from the group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical This is an eos_ctp member alarm. If not using LCAS, check that EOS member order matches that of the remote EOS. SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

84 Page 1-70 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LP-PLM: Payload label mismatch received - Low order Path LP-RDI: Remote Defect Indication - Low order Path LP-RFI: Remote Failure Indication - Low order Path LP-RFICON: Remote failure indication, connectivity defect - Low order Path LP-RFIPAY: Remote failure indication, payload defect - Low order Path LP-RFISVR: Remote failure indication, server defect - Low order Path Alarm Profiles sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp Invalid byte in the Low Order path overhead. The payload does not match what the signal label is reporting. Valid STM-N framing is not detected or AU-AIS is received from the source. Probable Cause The signal demultiplexed from the STM-N contains a remote failure indication. The far-end node has detected path defects coming from the local site. Far end path has an LP-UNEQ or LP-TIM alarm. Far end path has a LP-PLM alarm. Far end path has an AU-AIS or AU-LOP alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Warning Warning Check STM-N framing source. See AU-AIS. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms from the far-end node. Warning Warning Verify your payload connections. Check for far end alarms, especially LP-UNEQ and LP-TIM. Refer to the recommended actions for LP-UNEQ and LP-TIM. Warning Warning Verify your payload connections. Check for far end alarms, especially LP-PLM. Refer to the recommended actions for LP-PLM. Warning Info Verify your payload connections. Check for far end alarms, especially AU-AIS and AU-LOP. Refer to the recommended actions for AU-AIS and AU-LOP. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

85 Release OPS3.1.x Turin Networks Page 1-71 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LP-SQM: Low order path Sequence ID mismatch LP-TIM: Trace identifier mismatch - Low order Path LP-UNEQ: Unequipped - Low order Path LSDBOVFL 1 : Exceeded maximum number of LSAs Alarm Profiles sdh_eos sdh_eos_ctp ssdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp Probable Cause The member sequence number is in error. The expected path trace string does not match the received path trace string. No payload is received on an activated service. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Critical If non-lcas, check that the order of members in the remote EOS matches the local order. SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. SA Critical Minor Check your connection. Connect your proper payload. Check the service source. shelf Unused. Minor Minor Unused. LSM 1 : Loss of sync message shelf Unused. Minor Minor Unused. LWBATVG: Battery is low shelf The battery is low. Minor Minor Recharge the battery. LWFUEL: Low fuel shelf The fuel level is low. Minor Minor Refuel. Recommended Action LWHUM: Low humidity shelf The humidity is low. Minor Minor Check your method of procedures. LWPRES: Low cable press shelf Cable pressure is low. Minor Minor Check your method of procedures. LWTEMP: Low temperature shelf The temperature is too low. Minor Minor Check the environment for temperature drop. Check your method of procedures. LWWTR: Low water shelf The water level is too low. Minor Minor Check your method of procedures. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

86 Page 1-72 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition MANUAL: Manual protection switching MAN_ON_PROT: Manual protection switching MAN_ON_WORK: Manual protection switching MAN-TX-OFF: Transmitter manually disabled MAN-TX-ON: Transmitter manually enabled shelf shelf shelf ethernet_ptp sdh_ptp sonet_ptp ethernet_ptp sdh_ptp sonet_ptp A manual protection switch has been executed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. A manual protection switch has been executed on the protecting port of a protection group. A manual protection switch has been executed on a working port of a protection group. Operator disabled the optical laser. Operator enabled the optical laser. Info Info (Informational; no action required.) Info Info (Informational; no action required.) Info Info (Informational; no action required.) Info Info (Informational; no action required.) Info Info (Informational; no action required.) MAXAGE 1 : Maximum age shelf Unused. Minor Minor Unused. MISC: Misc (default) shelf Minor Minor MND-P: Member not de-skewable - STS MND-V: Member not de-skewable - VT Alarm Profiles eos eos_ctp eos eos_ctp Probable Cause Differential Delay exceeded on EOS member and the member was removed from the group. Differential Delay exceeded on EOS member and the member was removed from the group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them. SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

87 Release OPS3.1.x Turin Networks Page 1-73 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition MPU_BATTERY_A: Battery A alarm MPU_BATTERY_B: Battery B alarm MS-AIS: Alarm Indication Signal - Multiplex Section MS-BERSD: BER signal degrade - Multiplex Section Alarm Profiles ta200 SA Critical Critical ta200 SA Critical Critical sdh_ptp Probable Cause An upstream failure occurred at the multiplex section layer. sdh_ptp The BER on the incoming STM-N line has exceeded the signal degrade threshold. A connector in the STM-N optical link could be dirty. An STM-N module hardware problem could exist. Fiber could be bent or damaged. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your multiplex section payload connections. Critical Minor Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and fiber connection. Check fiber for bends or damage. If the problem persists, contact Turin s Customer Service (TAC). Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

88 Page 1-74 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition MS-BERSF: BER signal fail - Multiplex Section MS-RDI: Remote Defect Indicator - Multiplex Section MSSP_NOT_SYNC: MS-SP Ring synchronization failure MSSP_SYNC_UNKNOWN: Unknown error Alarm Profiles sdh_ptp The BER on the incoming STM-N line has exceeded the signal fail threshold. A connector in the STM-N optical link could be dirty. An STM-N module hardware problem could exist. Fiber could be bent or damaged. sdh_ptp server server Probable Cause Valid STM-N framing is not detected or MS-AIS is received from the source. One of the nodes in the MS-SP Ring is out of sync with the other nodes in the ring possibly due to invalid K bytes. MSSP ring synchronization status is unknown. MULT_PRIMARY_SERVER server There are multiple primary servers discovered. Only one primary server is allowed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Critical Minor Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and fiber connection. Check fiber for bends or damage. Warning Warning Check STM-N framing source. See MS-AIS. SA Critical Critical Check for OC-N module failures. Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes. Warning Warning Issue sync command to resynchronize the ring. SA Major Warning Restore the environment to one primary server. NEIGHSC 1 shelf Unused. Minor Minor Unused. Recommended Action Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

89 Release OPS3.1.x Turin Networks Page 1-75 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition NETSYNC: Network object synchronization failure server Master network objects (e.g., alarm profiles) are out of synchronization with propagated node objects. Warning Warning Resynchronize using the TransNav GUI. NEWLSA 1 shelf Unused. Minor Minor Unused. NO_OUTPUT: Output Signal Activity Failure NO_PRIMARY_SERVER: No primary TransNav server NODEEQMIS: Node equipment mismatch NODEIDMIS: Node ID mismatch Alarm Profiles ta200 SA Critical Critical server server sonet_ptp sdh_ptp Probable Cause The primary server was not found. Server-Agent equipment mismatch. The node ID selected is already in use. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Major Warning Check connectivity. If no primary server in the network, set up a primary server in the network environment. SA Critical Critical Determine if the TransNav server or the node contains the correct module configuration. If the TransNav server contains the correct module configuration, use the node-level CLI to lock, restart, and delete the module. The alarm should be deleted. If the node contains the correct module configuration, delete the node. During autodiscovery, the correct information will be forwarded to the TransNav server and the alarm should be deleted. Minor Minor Check all node IDs. Verify that they are each unique. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

90 Page 1-76 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition NODESYNC: Node synchronization NO-REMOTE-LCAS: No remote LCAS NPM: No provisioned members server Discovery of and synchronization with a new node. GCM protection switch. eos sdh_eos shelf eos sdh_eos lag The remote peer does not have LCAS capability or the capability is undetermined. No members have been provisioned. OPENDR: Door open shelf A door is open in the environment. OPR: Optical power received threshold violation OPT: Optical power transmitted threshold violation ORPNORM 1 : Optical receive power normalized threshold crossing alert OTPNORM 1 : Optical transmit power normalized threshold crossing alert Alarm Profiles ethernet_ptp sdh_ptp sonet_ptp shelf ethernet_ptp sdh_ptp sonet_ptp shelf Probable Cause Received optical power does not meet guaranteed value. Current is outside guaranteed bounds. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Warning Warning Wait for node synchronization to complete. Check network server connections. Warning Warning Enable LCAS on the remote nodes EOS. Check remote peer configuration, capability, and connectivity. SA Critical Critical Add CTP members to the EOS port. Add ports to the LAG. Minor Minor Validate that the door should be open. Close the door, as necessary. Warning Warning Check interface. Warning Warning Measure power level using optical power meter. shelf Unused. Warning Warning Unused. shelf Unused. Warning Warning Unused. Recommended Action Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

91 Release OPS3.1.x Turin Networks Page 1-77 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition OVERTEMP: Fan tray temperature has exceeded a maximum value OVERVOLTAGE_A 1 : Exceeded a maximum voltage value - Enhanced GCM_A OVERVOLTAGE_B 1 : Exceeded a maximum voltage value - Enhanced GCM_B PCASQLCH 1 : PCA channel squelched PDI-n (P, n<2) 1 : Payload defect indicator Alarm Profiles shelf shelf shelf sonet_ptp sdh_ptp ds3_ptp (ds_ptp) e3_ptp sdh_hp sdh-lp sdh_ptp sonet_sts sonet_ptp sdh_ptp Probable Cause Fan tray temperature has exceeded 56 ºC. GCM_A has triggered due to an over voltage condition. The Enhanced GCM triggers the over-voltage alarm at VDC. It clears this alarm at VDC. GCM_B has triggered due to an over voltage condition. The Enhanced GCM triggers the over-voltage alarm at VDC. It clears this alarm at VDC. Extra traffic carried on protection channel(s) has been squelched due to a protection switch. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check that the temperature of the room is not abnormally high. Replace the fan tray air filter. Minor Minor Check power system, breaker, fuse, and related cabling for power input A. Minor Minor Check power system, breaker, fuse, and related cabling for power input B. Minor Minor Clear the protection switch. Check equipment ring topology configuration. Payload defect indication. SA Minor Minor Check cable connectors and module ports. Payload defect indication. Minor Minor Clean the fiber connections. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

92 Page 1-78 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition PDI-n (1<n<5) 1 :Payload defect indicator PDI-n (n>4) 1 :Payload defect indicator PKTRETX 1 : An OSPF packet has been retransmitted ds3_ptp (ds_ptp) e3_ptp sonet_ptp sdh_ptp ds3_ptp (ds_ptp) e3_ptp sonet_ptp sdh_ptp Payload defect indication. SA Major Minor For DS3/EC1 modules, check cable connectors and module ports. Payload defect indication. SA Major Minor For OC-N modules, clean the fiber connections. Payload defect indication. SA Critical Minor For DS3/EC1 modules, check cable connectors and module ports. Payload defect indication. SA Critical Minor For OC-N modules, clean the fiber connections. shelf Unused. Minor Minor Unused. PLC: Partial loss of capacity lag At least one port in the LAG is down. PLCPLOF 1 : PLCP (Physical Layer Convergence Procedure) loss of frame PLCPRFI 1 : PLCP (Physical Layer Convergence Procedure) Remote Failure Indication PLCR: Partial loss of capacity - receive PLCT: Partial loss of capacity - transmit Alarm Profiles ds3_ptp (ds_ptp) e3_ptp ds3_ptp (ds_ptp) e3_ptp eos sdh_eos eos sdh_eos Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Critical At least one port in the LAG is down. Check for proper cabling and that local and remote port configurations match. Unused. SA Critical Minor Unused. Unused. Warning Info Unused. Recommended Action Capacity loss on path. SA Critical Critical Check the paths associated with the EOS members for alarms. Capacity loss on path. SA Critical Critical Check the paths associated with the EOS members for alarms. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

93 Release OPS3.1.x Turin Networks Page 1-79 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition PLINESQL 1 : Persistent line squelching PLM:Payload label mismatch received PLM-P: Path label mismatch PLM-V: Payload label mismatch received PLM-VC: Payload label mismatch received - VC Alarm Profiles sonet_ptp sdh_ptp ds3_ptp (ds_ptp) e3_ptp sonet_ptp sonet_sts ta200 te50 ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sonet_ptp sonet_vt sonet_sts STS (high order) path on the reporting OC-N/STM-N line has been squelched to avoid a misconnection. Invalid C2 byte (signal label byte) in the SONET path overhead. The payload does not match what the signal label is reporting. Payload label mismatch on the path. Invalid byte in the path overhead. The payload does not match what the signal label is reporting. te50 Invalid byte in the path overhead. The payload does not match what the signal label is reporting. e1_ptp sdh_ptp Probable Cause Invalid byte in the path overhead. The payload does not match what the signal label is reporting. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Contact Turin s Customer Service (TAC). SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Warning Warning Verify that the payload is the same as the provisioned payload/service. SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Warning Warning Connect correct payload. Verify that the payload is the same as the provisioned payload/service. SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

94 Page 1-80 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition PMCFG: PM configuration error PMDATALOST: Performance data lost POWER: Commercial power failure ds3_ptp (ds_ptp) e1_ptp e3_ptp ethernet_ptp sonet_ptp sdh_ptp server shelf shelf PM configuration is incorrect. Warning Warning Check configuration. PM data loss. Info Info (Informational; no action required.) The commercial power source has failed. PS: Automatic protection switch shelf An automatic protection switch has occurred. Minor Minor Check and follow your method of procedures. Info Info Check the equipment. PUMPFAIL 2 : Pump failure shelf Pump has failed. Minor Minor Check and follow your method of procedures. PWFAIL-A: Power problem power input A failed PWFAIL-B: Power problem power input B failed PWR-48: 48VDC power supply failure Alarm Profiles shelf shelf shelf Probable Cause GMT A fuse, cabling, circuit breaker, or power system unit has failed. GMT B fuse, cabling, circuit breaker, or power system unit has failed. Commercial fuse, cabling, circuit breaker, or power system unit has failed. QEFAIL: Queue Engine fail shelf Internal forwarding queue engine error. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check power system, breaker, fuse, and related cabling for power input A. Minor Minor Check power system, breaker, fuse, and related cabling for power input B. Minor Minor Check and follow your method of procedures. SA Critical Critical Contact Turin s Customer Service (TAC). RECTFAIL 2 : Rectifier failure shelf Rectifier has failed. Minor Minor Check and follow your method of procedures. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

95 Release OPS3.1.x Turin Networks Page 1-81 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RECTHIGH 2 : Rectifier high voltage RECTLOW 2 : Rectifier low voltage shelf Rectifier has high voltage. Minor Minor Check and follow your method of procedures. shelf Rectifier has low voltage. Minor Minor Check and follow your method of procedures. RMLF: Remote link failure lag A failure has occurred at the remote end of the link. REMOTE-LINKFAIL: Remote loss of client signal RESOURCE_MISMATCH: STSRM/VTRM Resource Mismatch Alarm Profiles ethernet_ptp shelf Probable Cause Link Integrity enabled and indicating that the remote Ethernet port is down. An uncommon alarm. The resource mismatch may occur as a result of a non-active GCM controller condition. The management system configuration does not match that of the line card. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Critical Critical Check the cable and configuration at the remote port. SA Critical Critical Check the cable and configuration at the remote port. SA Critical Minor Contact Turin s Customer Service (TAC). Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

96 Page 1-82 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RFI-L: Remote failure indication Line RFI-P: Remote failure indication Path Alarm Profiles ds3_ptp (ds_ptp) ta200 te50 The locally received EC-1 signal contains an RFI. The local EC-1 module is sending a bad signal to the remote node. sonet_ptp The locally received OC-N signal contains an RFI. The local OC-N module is sending a bad OC-N signal to the remote node. The far-end OC-N module has failed. ds3_ptp (ds_ptp) e3_ptp 1 ta200 te50 sonet_ptp sonet_sts Probable Cause The signal demultiplexed from the EC-1 contains an RFI. The far-end node has detected path defects coming from the local site. The STS-1 signal demultiplexed from the OC-N contains an RFI-P. The far-end node has detected path defects coming from the local site. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Check module/port. Check cable and connections. Check for and resolve LOS, LOF, and AIS alarms in the far-end node. Warning Warning Check module/port. Check for and resolve LOS, LOF, and AIS-L alarms in the far-end node. Verify the output of the local OC-N module for level degradation/dirty optical connectors. Clean the optical connectors. Check the fiber connection on adjacent equipment. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms such as LOP-P, AIS-P, PLM-P, TIM-P, and UNEQ-P from the far-end node. SA Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms such as LOP-P, AIS-P, and UNEQ-P from the far-end node. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

97 Release OPS3.1.x Turin Networks Page 1-83 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RFI-V: Remote failure indication RFI-VC: Remote failure indication Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) sonet_ptp sonet_vt sonet_sts shelf ta200 te50 e3_ptp 1 sdh_ptp e1_ptp sdh_ptp Probable Cause The VT signal demultiplexed from the DS1 contains an RFI-V. The far-end node has detected VT path defects coming from the local site. The low order signal demultiplexed from the STM contains an RFI-V. The far-end node has detected low order path defects coming from the local site. The low order signal demultiplexed from the STM contains an RFI-VC. The far-end node has detected low order path defects coming from the local site. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms such as LOP-P, AIS-P, PLM-P, TIM-P, and UNEQ-P from the far-end node. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms such as LOP-V, AU-AIS, LP-PLM, LP-TIM, and LP-UNEQ from the far-end node. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms such as LOP-V, AU-AIS, LP-PLM, LP-TIM, and LP-UNEQ from the far-end node. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

98 Page 1-84 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RFICON: Remote failure indication Connectivity defect RFICON-V: Remote failure indication Connectivity defect RFICON-VC: Remote failure indication Connectivity defect Alarm Profiles ds3_ptp (ds_ptp) sonet_ptp sonet_sts e3_ptp sdh_ptp ds1_ptp ds3_ptp (ds_ptp) shelf sonet_ptp sonet_vt sonet_sts e3_ptp sdh_ptp e1_ptp sdh_ptp Probable Cause Far end path has an UNEQ-P or TIM-P alarm. Far end path has an UNEQ-P or TIM-P alarm. Far-end VT path has an UNEQ-V or TIM-P alarm. Far end VC path has an LP-UNEQ or LP-TIM alarm. Far-end VC path has an LP-UNEQ or LP-TIM alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Info Verify your payload connections. Check for far end alarms, especially UNEQ-P and TIM-P. Refer to the recommended actions for UNEQ and TIM. SA Warning Info Verify your payload connections. Check for far end alarms, especially UNEQ-P and TIM-P. Refer to the recommended actions for UNEQ-P and TIM-P. SA Warning Info Verify your payload connections. Check for far end alarms, especially UNEQ-V and TIM-V. Refer to the recommended actions for UNEQ and TIM. SA Warning Info Verify your payload connections. Check for far end alarms, especially LP-UNEQ and LP-TIM. Refer to the recommended actions for LP-UNEQ and LP-TIM. SA Warning Info Verify your payload connections. Check for far end alarms, especially LP-UNEQ and LP-TIM. Refer to the recommended actions for LP-UNEQ and LP-TIM. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

99 Release OPS3.1.x Turin Networks Page 1-85 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RFIPAY: Remote failure indication Payload defect RFIPAY-V: Remote failure indication Payload defect RFIPAY-VC: Remote failure indication Payload defect Alarm Profiles ds3_ptp (ds_ptp) sonet_ptp sonet_sts e3_ptp sdh_ptp ds1_ptp ds3_ptp (ds_ptp) shelf sonet_ptp sonet_vt sonet_sts e3_ptp sdh_ptp e1_ptp sdh_ptp Probable Cause Far end path has a PLM-P alarm. Far end path has a HP-PLM alarm. Far end path has a PLM-V alarm. Far end path has a LP-PLM alarm. Far end path has a LP-PLM alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Info Verify your payload connections. Check for far end alarms, especially PLM-P. Refer to the recommended actions for PLM. SA Warning Info Verify your payload connections. Check for far end alarms, especially HP-PLM. Refer to the recommended actions for HP-PLM. SA Warning Info Verify your payload connections. Check for far end alarms, especially PLM-V. Refer to the recommended actions for PLM. SA Warning Info Verify your payload connections. Check for far end alarms, especially LP-PLM. Refer to the recommended actions for LP-PLM. SA Warning Info Verify your payload connections. Check for far end alarms, especially LP-PLM. Refer to the recommended actions for LP-PLM. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

100 Page 1-86 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RFISVR: Remote failure indication Server defect RFISVR-V: Remote failure indication Server defect RFISVR-VC: Remote failure indication Server defect Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) sonet_ptp sonet_sts e3_ptp sdh_ptp ds1_ptp ds3_ptp (ds_ptp) shelf sonet_ptp sonet_vt sonet_sts e3_ptp sdh_ptp e1_ptp sdh_ptp Probable Cause Far end path has an AIS-P or LOP-P alarm. Far end path has an AIS-P or LOP-P alarm. Far end path has an AIS-V or LOP-V alarm. Far end path has an TU-AIS or TU-LOP alarm. Far end path has an TU-AIS or TU-LOP alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Info Verify your payload connections. Check for far end alarms, especially AIS-P and LOP-P. Refer to the recommended actions for AIS-P and LOP-P. SA Warning Info Verify your payload connections. Check for far end alarms, especially AIS-P and LOP-P. Refer to the recommended actions for AIS-P and LOP-P. SA Warning Info Verify your payload connections. Check for far end alarms, especially AIS-V and LOP-V. Refer to the recommended actions for AIS-V and LOP-V. SA Warning Info Verify your payload connections. Check for far end alarms, especially TU-AIS and TU-LOP. Refer to the recommended actions for TU-AIS and TU-LOP. SA Warning Info Verify your payload connections. Check for far end alarms, especially TU-AIS and TU-LOP. Refer to the recommended actions for TU-AIS and TU-LOP. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

101 Release OPS3.1.x Turin Networks Page 1-87 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RLSD: Receive Line Signal Detect on MPS IM RS-TIM: Trace identifier mismatch RTS: Request to send on MPS IM SENSORFAIL: Thermal sensor failure SERVER_LOGINFAIL: Server login to node failed SERVER_ROLE SETOPER: Set operation performed SFO 1 : Sync frequency offset Alarm Profiles te50 Line signal not detected. SA Critical Critical Check connectivity and configuration at the remote end. sdh_ptp The expected path trace string does not match the received path trace string. SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. te50 Request to send not present. SA Critical Critical Check connectivity and configuration. shelf server server shelf server shelf ds3_ptp (ds_ptp) sonet_ptp e3_ptp sdh_ptp Probable Cause The thermal sensor on a line or control module has failed. Node login authentication failed. Event identifies the server role as primary or secondary. A set operation has been performed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Major Major Check that the temperature of the room or equipment is not abnormally high. Contact TAC for assistance if the temperature is normal and this failure persists. Critical Critical Try again. Recommended Action Contact your system administrator persistent login failures could indicate possible hacking. Info Info (Informational; no action required.) Info Info (Informational; no action required.) EC-1 or SONET facility timing. Minor Minor Check timing signal quality. SONET facility timing. Minor Minor Check timing signal quality. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

102 Page 1-88 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition SFPMIS: SFP mismatch SFPRMV: SFP removed SHELFMIS: Shelf type mismatch ethernet_ptp sdh_ptp sonet_ptp shelf ethernet_ptp sdh_ptp sonet_ptp shelf server There is a mismatch on the SFP interface. Critical Minor Check interface. The SFP has been removed. Critical Minor Check interface. The PreProvision shelf type does not match the actual shelf type. Warning Warning Delete the node. During autodiscovery, the correct node type should be discovered. SMOKE 2 : Smoke detected shelf Smoke detected. Minor Minor Check and follow your method of procedures. SQLCHTBL 1 : Squelch table mismatch SQM 1 : Sequence number change SQM-P: Sequence ID mismatch- STS Alarm Profiles sonet_ptp sdh_ptp ethernet_ptp shelf eos eos_ctp Probable Cause Alarm is raised as a circuit is being added to or deleted from a BLSR. May also be caused by incomplete provisioning of the STS channels. Minor Minor If a circuit is being added, the alarm will clear after the circuit has been completely built into the ring by adding all the necessary cross-connections. Be sure that the STS channels have been properly provisioned. Check equipment ring topology configuration. Unused. SA Critical Minor Unused. The member sequence number is in error. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical This is an eos_ctp member alarm. If non-lcas, check that the order of members in the remote EOS matches the local order. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

103 Release OPS3.1.x Turin Networks Page 1-89 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition SQM-V: Sequence ID mismatch- VT eos eos_ctp The member sequence number is in error. SSF: Server Signal Fail shelf All LCAS VC bundle members have failed. Also see path alarms for each VC bundle member (facility). The VC bundle operational state is set to Disabled until at least one member returns. SVC_STATUS 1 : Service status report SWCRPT: Software corruption server shelf server shelf SA Critical Critical This is an eos_ctp member alarm. If non-lcas, check that the order of members in the remote EOS matches the local order. SA Critical Minor Inspect all VC bundle facilities. Check remote sites for module removal/failure alarms or disabled Ethernet transmitter. Check the cables and interfaces. Unused. Info Info Unused. Software did not load or loaded with errors. SWERR: Software error all objects The software has detected an unexpected error. SA Critical Minor Contact Turin s Customer Service (TAC). Info Info Contact Turin s Customer Service (TAC). SWITCH 1 : Pointer switch ethernet_ptp Unused. SA Critical Minor Unused. SWITCH_TO_PROT: Traffic switch to Protection SWITCH_TO_SECT1: Traffic switch on optimized 1+1 APS working section 1 Alarm Profiles shelf shelf Probable Cause Traffic has switched to the standby module, port, or channel for a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. Traffic has switched on the optimized 1+1 APS bi-directional working section 1. Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info (Informational; no action required.) Info Info (Informational; no action required.) Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

104 Page 1-90 Turin Networks Release OPS3.1.x Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition SWITCH_TO_SECT2: Traffic switch on optimized 1+1 APS working section 2 SWITCH_TO_WORK: Traffic switch to Working SWMIS: Software version mismatch shelf shelf all objects Traffic has switched on the optimized 1+1 APS bi-directional working section 2. Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge. Traffic has switched to the working module, port, or channel for a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. The reporting module is not running with the same software version as the active GCM. SW_UPG: Software upgrade shelf Software upgrade event is in process. Warning Warning Verify that the switch was expected. Check the switch-from section for degraded performance or other relevant alarm conditions. Warning Warning Verify that the switch was expected. Check the switch-from section for degraded performance or other relevant alarm conditions. Minor Minor Reinstall correct software. Info Info (Informational; no action required.) SW_UPG_PROG shelf Software upgrade is in progress. Info Info (Informational; no action required.) SYSREF: System reference lock failed SYSREF_EVENT: System lost reference lock SYNCFAIL 2 : Synchronization reference failure 1 Not supported in this release. shelf Lock on system reference is lost. Critical Critical Check system reference. shelf System lost reference lock. Info Info Check for SYSREF alarm. sonet_ptp sdh_ptp 2 Environmental alarm inputs are customized by each operator. 3 Legacy event for Release 1.1 and below. Alarm Profiles Probable Cause 4 If switch mode is set to Lockout, a failure on the working module may affect service. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action OC-N facility timing. SA Minor Minor Check timing signal quality. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

105 Release OPS3.1.x Turin Networks Page 1-91 Alarms/Events, TA200 Table 1-11 Alarms, Events and Recommended Actions, TA200 Alarm: Definition Alarm Profiles Probable Cause Service Affecting Default Default Severity SA (Unprotected) (Protected) Recommended Action T2OOF: T2 Line - Out of frame ta200 T2 is out of frame. SA Critical Critical Check the configuration. T2XBIT: T2 Remote (Far-End) Failure ta200 On T2OOF alarm detection, the remote PM13 sends T2XBIT out the T3 interface. TA200_CLOCK: Clock alarm ta200 The primary timing source is no longer present or has failed. TA200_PM13E_G747FESmry: PM13e T3 747 Out of frame TA200_PM13E_G747OOFSmry: PM13e T3 747 Out of frame: PM13e T3 747 FE (Remote Far-End) Failure Warning Warning Check the remote end for out of frame errors and confirm the correct configuration. SA Critical Critical Check the configuration or timing source equipment for hard failure. ta200 PM13e T3 is out of frame. Warning Warning Check the configuration. ta200 PM13e T3 is out of frame at the remote end. SA Critical Critical Check the remote end configuration. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TA200

106 Page 1-92 Turin Networks Release OPS3.1.x Alarms/Events, TB through TZ Table 1-12 Alarms, Events and Recommended Actions, TB through TZ Alarm: Definition TCA: Threshold crossing alert TEMP: Internal temperature threshold violation TEMPCRIT: Temperature critical TEMPWARN: Temperature warning TIM: Trace identifier mismatch TIM-P: Trace identifier mismatch - Path Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e3_ptp ethernet_ptp sonet_ptp sdh_ptp ethernet_ptp sdh_ptp sonet_ptp shelf shelf shelf ds3_ptp (ds_ptp) e3_ptp sonet_ptp sdh_ptp e3_ptp sonet_ptp sonet_sts te50 Probable Cause A threshold crossing alert can be generated for each port PM parameter. The PM parameter is displayed in the Description column of the Events tab. For a listing of PM parameters, see Section 2 Performance Monitoring, Chapter 1 Managing Performance. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info Check PM for the integrity of the communications channel. Temperature is too great. Warning Warning Card overtemp. Check fans and filter. A module s temperature has exceeded 65ºC. A module s temperature has exceeded 59 ºC. The expected path trace string (J1 byte in the path overhead) does not match the received path trace string. The expected path trace string does not match the received path trace string. Minor Minor Check the fan tray for proper functioning. Replace, as necessary. Minor Minor Check the fan speed change. The alarm should clear once the fan speed changes. SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TB through TZ

107 Release OPS3.1.x Turin Networks Page 1-93 Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued) Alarm: Definition TIM-S: Trace identifier mismatch - Section TIM-V: Trail trace mismatch - VT TIU-V: Trail trace unstable -VT TIMEDOUT: Session terminated TIMEOUTWARN: Session terminate warning TIU-V: Trail trace mismatch - VT Alarm Profiles e3_ptp sonet_ptp te50 ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sdh_ptp sonet_ptp sonet_vt sonet_sts te50 ds1_ptp ds3_ptp (ds_ptp) e3_ptp sdh_ptp sonet_ptp sonet_vt sonet_sts server shelf server shelf Probable Cause The expected section trace (J0 byte) string does not match the received section trace string. The expected VT trail trace (J2 byte) string does not match the received VT trail trace string. The expected VT trail trace string match at received VT trail trace string is unstable. The user session has been idle for two hours. The user session has been idle for 1 hour and 55 minutes; the session will terminate in 5 minutes. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check configuration of section source or cross-connect. Match the section trace string at each end. SA Critical Minor Check configuration of VT trail trace source or cross-connect. Match the VT trail trace string at each end. SA Critical Minor Check configuration of VT trail trace source or cross-connect. Match the VT trail trace string at each end. Info Info Start a new user session. Info Info Perform a user action to stop session termination. shelf VT trail trace mismatch. SA Critical Minor Check trace configuration at each end. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TB through TZ

108 Page 1-94 Turin Networks Release OPS3.1.x Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued) Alarm: Definition TLC: Total loss of capacity lag All ports in the LAG are down. SA Critical Critical Check for proper cabling and that local and remote port configurations match. TLCR: Total loss of capacity - receive TLCT: Total loss of capacity - transmit TOOMANYEVENTS 1 : Too many events in the server TOPOMIS 2 : Topology mismatch eos sdh_eos eos sdh_eos Total capacity lost. SA Critical Critical Check the ingress transport link for alarms. Check the paths associated with the EOS members for alarms. Total capacity lost. SA Critical Critical Check the ingress transport link for alarms. Check the paths associated with the EOS members for alarms. server Server event log too large. Critical Critical Clear event log. sonet_ptp sdh_ptp Topology is mismatched. Minor Minor Check topologies. TOXIC 3 : Toxic gas detected shelf Toxic gas detected. Minor Minor Check and follow your method of procedures TSS-EXTA-OOB-A: Controller A EXT A - Out of Band TSS-EXTA-OOB-B: Controller B EXT A - Out of Band TSS-EXTB-OOB-A: Controller A EXT B - Out of Band TSS-EXTB-OOB-B: Controller B EXT B - Out of Band. Alarm Profiles shelf shelf shelf shelf Probable Cause Controller A EXT A reference is out of local oscillator qualification frequency range. Controller B EXT A reference is out of local oscillator qualification frequency range. Controller A EXT B reference is out of local oscillator qualification frequency range. Controller B EXT B reference is out of local oscillator qualification frequency range. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TB through TZ

109 Release OPS3.1.x Turin Networks Page 1-95 Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued) Alarm: Definition TSS-FRC: Forced protection switching on timing TSS-FREERUN-GCMA: GCM is in freerun mode TSS-FREERUN-GCMB: GCM is in freerun mode TSS-HOLDOVER-GCMA: GCMA in holdover state awaiting a reference TSS-HOLDOVER-GCMB: GCMB in holdover state awaiting a reference TSS-LINE1-OOB-GCMA: GCMA Line Ref 1 - Out of Band TSS-LINE1-OOB-GCMB: GCMB Line Ref 1 - Out of Band TSS-LINE2-OOB-GCMA: GCMA Line Ref 2 - Out of Band TSS-LINE2-OOB-GCMB: GCMB Line Ref 2 - Out of Band Alarm Profiles shelf shelf shelf shelf shelf shelf shelf shelf shelf Probable Cause A forced protection switch command has been performed on the BITS or line timing source. No timing references found. Defer to freerun mode. No timing references found. Defer to freerun mode. There are no available external references so the GCMA is referencing the local oscillator. There are no available external references so the GCMB is referencing the local oscillator. GCMA Line Reference 1 is out of local oscillator qualification frequency range. GCMB Line Reference 1 is out of local oscillator qualification frequency range. GCMA Line Reference 2 is out of local oscillator qualification frequency range. GCMB Line Reference 2 is out of local oscillator qualification frequency range. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning If the reason for executing the forced switch no longer exists, clear the switch command. Warning Warning Check timing references. Warning Warning Check timing references. SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC) SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TB through TZ

110 Page 1-96 Turin Networks Release OPS3.1.x Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued) Alarm: Definition TSS-LINE3-OOB-GCMA: GCMA Line Ref 3 - Out of Band TSS-LINE3-OOB-GCMB: GCMB Line Ref 3 - Out of Band TSS-LINE4-OOB-GCMA: GCMA Line Ref 4 - Out of Band TSS-LINE4-OOB-GCMB: GCMB Line Ref 4 - Out of Band TSS-LOCK: Lockout protection switching on timing TSS-MAN: Manual protection switching on timing TSS-REF1-ALM: Primary reference for timing subsystem is alarmed TSS-REF2-ALM: Secondary reference for timing subsystem is alarmed TSS-REF3-ALM: Third reference for timing subsystem is alarmed Alarm Profiles shelf shelf shelf shelf shelf shelf shelf shelf shelf Probable Cause GCMA Line Reference 3 is out of local oscillator qualification frequency range. GCMB Line Reference 3 is out of local oscillator qualification frequency range. GCMA Line Reference 4 is out of local oscillator qualification frequency range. GCMB Line Reference 4 is out of local oscillator qualification frequency range. A lockout protection switch command has been performed on the BITS or line timing source. A manual protection switch command has been performed on the BITS or line timing source. An LOS, LOF, or AIS-L alarm exists on the BITS or line timing primary reference. An LOS, LOF, or AIS-L alarm exists on the BITS or line timing secondary reference. An LOS, LOF, or AIS-L alarm exists on the BITS or line timing third reference. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin s Customer Service (TAC). Warning Warning If the reason for executing the lockout command no longer exists, clear the switch command. Warning Warning If the reason for executing the manual switch no longer exists, clear the switch command. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TB through TZ

111 Release OPS3.1.x Turin Networks Page 1-97 Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued) Alarm: Definition TSS-REF4-ALM: Fourth reference for timing subsystem is alarmed TSS-REFL-GCMA: All synchronization references are failed or unusable TSS-REFL-GCMB: All synchronization references are failed or unusable TSS-REFS 2 : Reference switched - timing subsystem TSS-SSM: SSM (synchronization status message) update - timing subsystem) TSSALM 2 : Timing reference alarm TSSGEN 2 : Timing subsystem event TSSREF: Timing system reference lock failed TSSREF_EVENT: Timing system lost reference lock Alarm Profiles shelf shelf shelf An LOS, LOF, or AIS-L alarm exists on the BITS or line timing fourth reference. All BITS or line timing sources are alarmed. All BITS or line timing sources are alarmed. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Major Major Restore primary and secondary timing references. Major Major Restore primary and secondary timing references. shelf Reference has been switched. Info Info (Informational; no action required.) shelf There has been a change in SSM for BITS or line timing sources. Info Info (Informational; no action required.) shelf Timing reference alarm. Info Info Check timing reference. shelf Timing subsystem event. Info Info (Informational; no action required.) shelf shelf Probable Cause Lock on timing system reference is lost. Timing system lost reference lock. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Critical Critical Check timing system reference. Info Info Check for TSSREF alarm. TSSSETS 2 : SETS status shelf Timing subsystem event. Info Info (Informational; no action required.) Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TB through TZ

112 Page 1-98 Turin Networks Release OPS3.1.x Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued) Alarm: Definition TU-AIS: Alarm indication signal Tributary Unit) TU-LOP: Loss of Pointer Tributary Unit TX-OFF-LI:Transmitter off due to link indication TX-ON-LI:Transmitter on due to link indication sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp 1 Legacy event for Release 1.1 and below. 2 Not supported in this release. Alarm Profiles 3 Environmental alarm inputs are customized by each operator. Probable Cause An upstream failure occurred at the tributary unit path layer. Valid pointer bytes are missing from the tributary unit overhead. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your tributary unit payload connections. SA Critical Minor Check the cabling and physical connections on the reporting card. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. ethernet_ptp The module is in standby mode. Info Info Information only. ethernet_ptp The module is in active mode. Info Info Information only. Recommended Action Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TB through TZ

113 Release OPS3.1.x Turin Networks Page 1-99 Alarms/Events U through Z Table 1-13 Alarms, Events and Recommended Actions, U through Z Alarm: Definition UNDERVOLTAGE_A 1 : Below the minimum voltage value - Enhanced GCM_A UNDERVOLTAGE_B 1 : Below the minimum voltage value - Enhanced GCM_B UNEQ: Rx Path unequipped code received UNEQ-P Unequipped code signal label received Alarm Profiles shelf shelf ethernet_ptp ds3_ptp (ds_ptp) e3_ptp sonet_ptp sonet_sts te50 Probable Cause GCM_A has triggered due to an under voltage condition. The Enhanced GCM triggers the under-voltage alarm at VDC. It clears this alarm at VDC. GCM_B has triggered due to an under voltage condition. The Enhanced GCM triggers the under-voltage alarm at VDC. It clears this alarm at VDC. No payload is received on an activated service. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check power system, breaker, fuse, and related cabling for power input A. Minor Minor Check power system, breaker, fuse, and related cabling for power input B. SA Critical Minor Check your interface connection. Connect your proper payload and service SA Critical Minor source. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events U through Z

114 Page Turin Networks Release OPS3.1.x Table 1-13 Alarms, Events and Recommended Actions, U through Z (continued) Alarm: Definition UNEQ-V: Unequipped code signal label received - VT path UNEQ-VC: Unequipped code signal label received - VC path ds1_ptp ds3_ptp (ds_ptp) shelf sonet_ptp sonet_vt sonet_sts te50 e3_ptp sdh_ptp e1_ptp sdh_ptp No payload is received on an activated service. SA Critical Minor Check your interface connection. Connect your proper payload and service source. See UNEQ-VC. SA Critical Minor See UNEQ-VC. No payload is received on an activated service. SA Critical Minor Check your interface connection. Connect your proper payload and service source. UP 1 : In service all objects Unused. Minor Minor Unused. VCC: Internal voltage threshold violation VENTFAIL 2 : Ventilation system failure ethernet_ptp sdh_ptp sonet_ptp shelf Supply voltage doe not meet guarantee. Warning Warning Call Turin s Customer Support. shelf Ventilation system has failed. Minor Minor Check and follow your method of procedures. WARMREBOOT shelf Module warm reboot request in process. Until complete (within 60 seconds), module does not respond to provisioning requests or protection switch triggers. WLMIS: Configured wavelength mismatch with hardware Alarm Profiles sdh_ptp sonet_ptp Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Verify that the module warm reboot request is expected. Incorrect provisioning. SA Major Minor Check interface and configuration. Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events U through Z

115 Release OPS3.1.x Turin Networks Page Table 1-13 Alarms, Events and Recommended Actions, U through Z (continued) Alarm: Definition X86_ABORT shelf Receiving X.86 encapsulation abort condition. X86_CRC shelf Receiving X.86 encapsulation CRC errors. XPT-FAIL-RX: Receiver connection failure XPT-FAIL-TX: Transmitter connection failure XPTRX: Receive transport failure XPTTX: Transmit transport failure 1 Not supported in this release. Alarm Profiles ethernet_ptp ethernet_ptp 2 Environmental alarm inputs are customized by each operator. lag lag Probable Cause Link Integrity detected transport failure in the receive direction. Link Integrity detected transport failure in the transmit direction. Link Integrity detected transport failure in the receive direction. Link Integrity detected transport failure in the transmit direction. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check interface and configuration. SA Critical Minor Check interface and configuration. SA Critical Critical Check EOS members for path alarms. SA Critical Critical Check EOS members for path alarms. SA Critical Critical Check EOS members for path alarms. SA Critical Critical Check EOS members for path alarms. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events U through Z

116 Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events U through Z Page Turin Networks Release OPS3.1.x

117 Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events U through Z Release OPS3.1.x Turin Networks Page 1-103

118 Node Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events U through Z Page Turin Networks Release OPS3.1.x

119 SECTION 1FAULT MANAGEMENT Chapter 3 TransNav GUI Service Error Codes Introduction This document provides TransNav GUI service error code information to assist you in troubleshooting TransNav system service request failure indications. See the figure below. This chapter includes the following topics: Service Activation Failure, page TransNav GUI Service Error Codes, page Figure 1-13 TransNav GUI Service Request Error Window Release OPS3.1.x Turin Networks Page 1-105

120 Node Operations and Maintenance Guide, Section 1: Fault Management Service Activation Failure Service Activation Failure If a service request activation fails, use the following Service Request Show Last Error procedure to help trace and resolve the problem. Table 1-14 Service Request Show Last Error Step Procedure 1 Select the service request entry. Service Request Entry Service Error Code Information Figure 1-14 Service Request Failure 2 From the Services menu, select Show Last Error. Activation Failure Indication Figure 1-15 Services Menu Show Last Error Option 3 Observe the service error code information and refer to Table 1-15 Service Error Codes and Recommended Actions, page for further troubleshooting details. 4 The Service Request Show Last Error procedure is complete. Page Turin Networks Release OPS3.1.x

121 Release OPS3.1.x Turin Networks Page TransNav GUI Service Error Codes TransNav GUI service error codes are listed in the following table in ascending, numerical order. Each error code table entry contains the following information: The service error code as visible in the service request error window. Service error code string definition as visible in the service request error window. Probable cause(s) for service request failure. Recommended action(s) to take upon receiving the service error code indication. Table 1-15 Service Error Codes and Recommended Actions Service Error Code Service Error Code String Definition Probable Cause Recommended Action 1 Internal error A system error occurred. If the problem persists, contact the Turin Technical Assistance Center RSVP (resource reservation protocol) error - MIB SET operation failed 1008 RSVP (resource reservation protocol) error - MIB GET operation failed 1009 RSVP (resource reservation protocol) error - MIB TEST operation failed 1016 RSVP (resource reservation protocol) error - No path for reservation Residual resources from a previous service were not cleared due to a switchover. (e.g., a service deletion request in process when a switchover occurred.) Residual resources from a previous service were not cleared due to a switchover. (e.g., a service deletion request in process when a switchover occurred.) Residual resources from a previous service were not cleared due to a switchover. (e.g., a service deletion request in process when a switchover occurred.) Remote node or link failure. Try to deactivate/reactivate the new service. If deactivation/reactivation does not resolve the problem, then perform a GCM switchover. As a last resort, restart the node. Try to deactivate/reactive the new service. If deactivation/reactivation does not resolve the problem, then perform a GCM switchover. As a last resort, restart the node. Try to deactivate/reactive the new service. If deactivation/reactivation does not resolve the problem, then perform a GCM switchover. As a last resort, restart the node. Retry service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

122 Page Turin Networks Release OPS3.1.x Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 1025 RSVP (resource reservation protocol) error - Service preempted 1034 RSVP (resource reservation protocol) error - Resources not available 1035 RSVP (resource reservation protocol) error - System resources not available 1036 RSVP (resource reservation protocol) error - System error, resources not available Probable Cause Service of a higher priority has used the requested resources. Service resources completely used. Most typically, this applies to STS resources. Internal system resources completely used. The error is most commonly seen when using the Bulk Activation tool. Internal system resources completely used. The error is most commonly seen when using the Bulk Activation tool. Check/set service priority. If possible, set high priority for all services to eliminate preemption. Use IP address and node name returned in the error message and trace the resource deficiency. Select another resource and retry the service request. Switchover to access potentially free resources, and then retry the service request. If you were using the Bulk Activation tool, make note of the first service request error identified, and one-by-one, retry service activation. Switchover to access potentially free resources, and then retry the service request. If you were using the Bulk Activation tool, make note of the first service request error identified, and one-by-one, retry service activation Unsupported interface in request Unsupported interface identified in the request. Check the interface specified in the original request. Make a new request with a valid interface Invalid slot in request Unrecognized module was plugged into the slot. (e.g., a module was plugged into a previously configured yet unequipped slot.) 1208 Invalid interface in request Invalid interface selected in Ethernet, DCC Channel, or Service request. The physical port or card cannot be found. For example, an attempt was made to create a DCC Channel on an invalid port. Check the slot configuration. Recommended Action Check the interface specified in the original request. Make a new request with a valid interface. Node Operations and Maintenance Guide, Section 1: Fault Management TransNav GUI Service Error Codes

123 Release OPS3.1.x Turin Networks Page Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 1209 Invalid Protection interface Unsupported interface identified in the request. For example, an Ethernet I/F in 1+1 protection group request Resources not available Port is locked STS is completely used 1215 Error while processing a service request Module not responding. Check the interface specified in the original request. Make a new request with a valid interface. Unlock the port Select a different STS with sufficient bandwidth Reseat the module. If the problem persists, contact the Turin Technical Assistance Center 1217 Cannot find the service The service or cross-connect identifier has been lost. If the problem persists, contact the Turin Technical Assistance Center Interface already exists The interface is already in use. Make another interface selection and retry the service request Slot already exists The slot is already in use. Make another slot selection and retry the service request PG (protection group) already exists The protection group is already in use. Make another protection group selection and retry the service request Interface exists in a protection group The interface is already in use in a protection group. Make another interface selection and retry the service request Slot exists in a PG (protection group) 1227 PG (protection group) already used by a service The slot is already in use in a protection group. The protection group is already in use. Make another slot selection and retry the service request. Make another protection group selection and retry the service request Interface already used by a service The interface is already in use in a service. Make another interface selection and retry the service request Slot already used by a service The slot is already in use in a service. Make another slot selection and retry the service request Error in processing UPSR (unidirectional path switched ring) request Probable Cause Trying to use an unavailable UPSR protection group. Recommended Action Create the UPSR protection group and retry the service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

124 Page Turin Networks Release OPS3.1.x Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 1231 Invalid Direction for service Incorrect Direction type selected for the service. Make a valid Direction selection and retry the service request Invalid Encoding Type Incorrect Encoding Type selected for the service. Make a valid Encoding Type selection and retry the service request Invalid Protection Group Incorrect Protection Group selected for the service. Make a valid Protection Group selection and retry the service request Invalid Ring Type Incorrect Ring Type selected for the service. Make a valid Ring Type selection and retry the service request Switch command successful The Switch function completed successfully. No action required Switch command denial - equal or higher priority request outstanding 1238 Invalid Starting STS (synchronous transmission signal) specified A failed attempt to request a lower priority protection switch while a higher priority protection switch was in progress. Incorrect STS selected. Check the protection group priority. Make a valid STS selection and retry the service request Invalid Bandwidth specified Bandwidth request does not match the option. Check bandwidth, make another selection, and retry the service request Interface in PG (protection group) of different type 1242 Invalid service request or invalid re-use of STS 1244 Error encountered on PG (protection group) operation on line cards Probable Cause Selected different interface types. Attempted an invalid service request (e.g., mixed uni- and bi-direction request) Invalid slot, port, or STS identified in request Failure occurred while creating the protection group Requested resource is Admin locked The resource is locked and must be unlocked. Unlock the resource. Recommended Action Retry the service request with appropriate interface types. Check service Check the slot, port, and STS made in the request If the problem persists, contactthe Turin Technical Assistance Center. Node Operations and Maintenance Guide, Section 1: Fault Management TransNav GUI Service Error Codes

125 Release OPS3.1.x Turin Networks Page Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 1247 No UPSR PG (protection group) created for the requested UPSR service 1254 Invalid span or tributary card given in the transparent service 1258 DCC Tunnel interface is in a transparent ring No UPSR PG was created so cannot be applied. The span or tributary card cannot be identified. The port you ve selected is in a transparent ring. Create UPSR PG and retry the service request. Check your selections. Make another port selection and retry the service request DCC Tunnel STS is in use The STS specified is already in use. Make another selection and retry the service request E2E (End to End) service request; forward direction STS already in use 1264 E2E (End to End) service request; forward direction STS already in use 1265 E2E (End to End) service request; reverse direction STS already in use 1266 E2E (End to End) service request; reverse direction STS already in use Probable Cause STS is unavailable to complete E2E service request. STS is unavailable to complete E2E service request. STS already in use. STS is unavailable to complete E2E service request. STS already in use. STS is unavailable to complete E2E service request. STS already in use Interface check failed Attempting to set up a service with incorrect constraint settings Interface type invalid Attempting to set up a service with an incorrect interface type. Recommended Action Check STS. Make another STS selection and retry the service request. Check STS. Make another STS selection and retry the service request. Check STS. Make another STS selection and retry the service request. Check STS. Make another STS selection and retry the service request. Make correct constraint selections and retry the service request. Make another interface selection and retry the service request Link encoding type invalid Incorrect encoding type selected. Make another encoding type selection and retry the service request Link direction invalid Incorrect direction selected. Make another direction selection and retry the service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

126 Page Turin Networks Release OPS3.1.x Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition Probable Cause 1271 Invalid interface During an end-to-end service, typically strict, a remote module was incorrectly specified or was inadvertently removed Pending IN label unavailable During an end-to-end service, the STS pending resource identifier is not found Pending OUT label unavailable During an end-to-end service, the STS pending resource identifier is not found Used IN label unavailable During an end-to-end service, the STS used resource identifier is not found Used OUT label unavailable During an end-to-end service, the STS used resource identifier is not found. Check the slot/port of each module interface. If it is correct, then investigate the possibility of a remote module extraction. Check the slot/port. If the problem persists, contact the Turin Technical Assistance Center. Check the slot/port. If the problem persists, contact the Turin Technical Assistance Center. Check the slot/port. If the problem persists, contact the Turin Technical Assistance Center. Check the slot/port. If the problem persists, contact the Turin Technical Assistance Center Label word invalid Invalid directional resource request Check uni- and bi-directional settings. If the problem persists, contact the Turin Technical Assistance Center Invalid label Invalid user request for STS # = 0 Make another STS # selection and retry the service request Invalid pointer Cannot find system pointer If the problem persists, contact the Turin Technical Assistance Center 1281 Next label unavailable Cannot find an available resource because all system resources are in use Invalid BLSR link check The STS number requested must be equivalent across the E2E BLSR path. One of the STS labels along the path is already in use OR a module has been inadvertently pulled during the E2E service request selection process. Recommended Action If the problem persists, contact the Turin Technical Assistance Center. Check STS number availability across the entire BLSR path. Make another STS number selection as necessary and retry the service. Node Operations and Maintenance Guide, Section 1: Fault Management TransNav GUI Service Error Codes

127 Release OPS3.1.x Turin Networks Page Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 1285 BLSR label unavailable The STS number in the E2E BLSR service request is in use. Reactivate BLSR service request. If previously attempting service request using Bulk Activation, retry on a one-by-one basis for better traceability Invalid BLSR constraints. System error during the E2E BLSR service request. If the problem persists, contact the Turin Technical Assistance Center Switch exercise failed 1+1 linear bidirectional protection group exercise request failed Path protection error Trying to use an unavailable 1+1 Path protection group Control channels don t match for interfaces in the 1+1 PG (protection group) 1292 DCC bytes for interfaces in a 1+1 PG (protection group) do not match Control channel down The DCC configuration termination bytes must match. Check remote node for (K1/K2 APS) byte failure. Create the 1+1 Path protection group and retry the service request. Retry the service request. Retry the service request with matching DCC configuration termination bytes Error modifying path parameter(s) Invalid parameter modification selection. Make appropriate parameter selections GCM FM error - destination termination point resource allocation failed 3016 Destination termination point admin state is locked 3017 Source termination point admin state is locked Probable Cause Resource allocation failure during the Ethernet service request. There is not enough bandwidth available on the SONET endpoint to accommodate the new Ethernet service. The destination Ethernet port administrative state is set to locked. The source Ethernet port administrative state is set to locked. Recommended Action Deactivate any unnecessary Ethernet services to free bandwidth at the SONET endpoint for the new service. Create a new SONET endpoint with the required bandwidth and use it in the new Ethernet service request. Unlock the destination Ethernet port and retry the service request. Unlock the source Ethernet port and retry the service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

128 Page Turin Networks Release OPS3.1.x Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 3021 LC FM error - flow action failed Too many VLANs have been configured on the Ethernet module. Ethernet modules support up to 243 VLANs Previous command issued by MP is still being processed 3212 Ethernet card requested in service is physically absent 3220 Invalid Ethernet slot requested in service 3221 Invalid Ethernet port requested in service 3224 Ethernet port requested in service is used by active service with another tagging type 3225 Optical facility requested in service is in use 3227 Optical facility requested in service is in use for a dedicated p2p (point to point) service 3228 Optical facility requested in service is in use for a Transparent LAN Service Probable Cause A second service request was issued before a previous request process had time to complete. The Ethernet module specified in the service request is not physically present. Invalid slot identified in request. For example, slot 21 is requested in a 20 slot chassis. Invalid port identified in request. For example, port 25 is requested in a 24 port module. The Ethernet port identified in the service request is being used for another service type. Service types must be compatible. The SONET endpoint is already in use by another service using a different Ethernet module. A SONET endpoint can only be used with one Ethernet module at a time. The SONET endpoint is already in use with a dedicated point to point (p2p) service and is incompatible with the service in the activation request. The SONET endpoint is already in use with a Transparent LAN service and is incompatible with the service in the activation request. Deactivate any unnecessary Ethernet services to free up VLANs for the new service. Use a different Ethernet module on the same node and retry the service request. Retry the service request. Recommended Action Plug in an appropriate Ethernet module and retry the service request. Make another (valid) slot selection and retry the service request. Make another port selection and retry the service request. Deactivate the conflicting service using the Ethernet port and retry the new service request. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Node Operations and Maintenance Guide, Section 1: Fault Management TransNav GUI Service Error Codes

129 Release OPS3.1.x Turin Networks Page Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 3229 VLAN ID requested in service is already being used in the Ethernet module (card) 3236 Ethernet module (card) requested in service is not yet ready to accept new services 3240 Ethernet module (card) type is not supported by EA in this release 3242 Termination point specified in service is being used by non-ias applications 3243 Termination point specified in IAS service has an invalid participation type 3244 Ethernet port specified in IAS service has subscribers going to a different optical facility Probable Cause One or more VLAN IDs specified in the service request are already in use for another service on the Ethernet module. The Ethernet module in the service request has not completed initialization, therefore, is not ready to accept service. The Ethernet module type in the service request is not supported in this release. The SONET endpoint is already in use with non-ias services and is incompatible with the service in the IAS service request. The SONET endpoint is already in use with another IAS service with a different participation type. All services using a SONET endpoint must have the same participation type (SUBSCRIBER or PROVIDER). The source Ethernet port identified in the service request is being used by another IAS service with a different destination termination point. Recommended Action Deactivate the conflicting service using the VLAN ID and retry the new service request. Once the Ethernet board completes initialization, retry the service request. To use the Ethernet module in question, perform a system software release upgrade. See Section 7 Software Upgrades, Chapter 1 Release TR2.1.x Traverse Software Upgrade, page 7-1 for details. Choose another Ethernet module for the service request. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Use the same destination termination point as the previously activated IAS service and retry the service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

130 Page Turin Networks Release OPS3.1.x Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 3247 No free traffic contracts are available on the Ethernet module (card) specified in service 3256 EA is not ready to receive MP requests 3271 Maximum number of TDM endpoints bound to Ethernet module (card) 3272 Maximum number of TLS TDM endpoints bound to Ethernet module (card) 3273 Maximum number of TLS instances on Ethernet module (card) Traffic contract resource allocation failure during service request. All traffic contracts are in use. Each Ethernet module supports (typically) 124 traffic contracts. Traffic contracts are required and most commonly used for Ethernet services with a guaranteed data rate. They are also needed for each SONET termination point using best effort services. Probable Cause Ethernet management command occurs while the GCM is still initializing and unable to handle the request. A large number of Ethernet requests occur in a very short period of time. SONET endpoint resource allocation failure during service request. All SONET endpoints are already in use. Each Ethernet module supports (typically) 24 SONET endpoints. The limit for Transparent LAN Service (TLS) SONET endpoints has been reached. There can only be a maximum of two TLS SONET endpoints on an Ethernet module. The limit for Transparent LAN Service (TLS) service instantiation has been reached. There can only be a maximum of four TLS service instances on an Ethernet module. Each TLS instance is identified by its VLAN ID. Recommended Action Deactivate some service using a traffic contract to free up resources and retry the new service request. Retry the service request as this is a transient condition. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Deactivate all services using one of the other TLS SONET endpoints and retry the new service request. Deactivate all of the active services using another TLS instance and retry the service request. Node Operations and Maintenance Guide, Section 1: Fault Management TransNav GUI Service Error Codes

131 Release OPS3.1.x Turin Networks Page Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 3274 VLAN ID is in use by non-tls service on same Ethernet module (card) 3275 VLAN ID is in use by TLS service on another Ethernet module (card) 3276 Optical facility requested in service is in use for a Shared-p2p (point to point) service 3277 Optical facility requested in service is in use for an IAS service The VLAN ID specified in the service request is already in use by another non-tls service on the Ethernet module. One or more VLAN IDs specified in the service request are already in use for another TLS service on a different Ethernet module in the same node. A VLAN ID can only be used for TLS on one Ethernet module at a time in a node. The SONET endpoint is already in use with a Shared point to point (p2p) service and is incompatible with the service in the activation request. The SONET endpoint is already in use with an internet access service (IAS) and is incompatible with the service in the activation request. Deactivate the conflicting service using the VLAN ID and retry the new service request. Make another VLAN ID selection and retry the service request. Deactivate the conflicting service using the VLAN ID and retry the new service request. Make another VLAN ID selection and retry the service request. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Deactivate the conflicting service using the SONET endpoint and retry the new service request VT resource request is in use The VT resource requested is already in use. Check VT. Make another VT selection and retry the service request STS resources between the cards are all used up 3609 Internal error; cannot create STS cross-connect Probable Cause VT Switch module is required but not present in the system. All the resources are already in use. A system error occurred during the STS cross-connect process. Recommended Action Install a VT Switch module in the system. Make a different resource selection with appropriate bandwidth and retry the service request. If the problem persists, contact the Turin Technical Assistance Center Incoming VT already in use The VT service endpoint requested is already in use. Check VT. Make another VT selection and retry the service request Outgoing VT already in use The VT service endpoint requested is already in use. Check VT. Make another VT selection and retry the service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

132 Page Turin Networks Release OPS3.1.x Table 1-15 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 3620 Internal error; Error replicating generic cross-connect to standby A system error occurred during the GCM replication process. If the problem persists, contact the Turin Technical Assistance Center STS resource is already being used The STS resource requested is already in use. Make another STS selection (with appropriate bandwidth) and retry the service request All tunnels on Ethernet module (card) already allocated 3818 Minimum Best Effort bandwidth requirements unavailable 3820 Ethernet module (card) must be created before adding services 3824 Backplane bandwidth from Ethernet module (card) not available Probable Cause Ethernet module cannot support any new SONET endpoints at this time. Each Ethernet module supports (typically) 24 SONET endpoints. Resource allocation request failure. SONET termination point resources required for Best Effort class of service are unavailable so the service request cannot complete. Premium class of service services are using the required bandwidth. The Ethernet module (card) in the service request does not exist. The module has not been provisioned. Resource allocation request failure. SONET termination point resources required are unavailable so the service request cannot complete VC Bundle misconfigured The VC Bundle (being used as a SONET termination point) is configured incorrectly. The SONET termination point is unusable. Recommended Action Deactivate one or more services using another SONET endpoint on this Ethernet module and retry the new service request. Deactivate one or more services using SONET termination points with the Premium class of service to free up resources and retry the new service request. Provision the Ethernet module and retry the service request. Deactivate one or more services using SONET termination points on the same Ethernet module to free up resources and retry the new service request. Check the VC Bundle configuration, correct misconfiguration, and retry the service request. Node Operations and Maintenance Guide, Section 1: Fault Management TransNav GUI Service Error Codes

133 SECTION 2SYSTEM MONITORING SECTION 2 PERFORMANCE MONITORING SECTION 2 Contents Chapter 1 Managing Performance Creating or Modifying a PM Template Assigning a PM Template Assigning a Port PM Template Assigning an EOS Port PM Template Assigning a Subport PM Template Assigning a Service PM Template Assigning a TransAccess 100 Mux PM Template Viewing PM Data PM Timing Viewing Port or Subport PM Data Viewing Service Path PM Data Viewing Signal Path Trace Data Report Generation Generating a PM Report Chapter 2 SONET Performance Parameters Introduction DS1 Port PM DS3 Port PM EC-1 Port PM Small Form-Factor Pluggable Optical Port PM SONET Port PM SONET STS Path Layer PM SONET VT Path Layer PM Chapter 3 SDH Performance Parameters Introduction E1 Port PM E3 Port PM SDH High and Low Order Path PM SDH Port PM SDH VC-11 and VC-12 Path PM Chapter 4 Ethernet Performance Parameters Introduction EOS Port PM Ethernet Equipment PM Release OPS3.1.x Turin Networks Page vii

134 Node Operations and Maintenance Guide, Section 2 Performance Monitoring Ethernet Port PM Ethernet Service Port PM List of Figures Figure 2-1 Performance Templates Dialog Box Figure 2-2 DS1 PM Configuration Template Dialog Box Figure 2-3 Synchronize Template Dialog Box Figure 2-4 Service PM Template Parameters Figure 2-5 TransAccess 100 Mux Config Tab Figure 2-6 Object Selection for PM Figure 2-7 Port Performance Tab Figure 2-8 Path Display for Services Screen Figure 2-9 Service Performance (PM) Tab Figure 2-10 Path Display for Service Screen Figure 2-11 Path Overhead Dialog Box Figure 2-12 Event Report Sample Figure 2-13 Reports Screen List of Tables Table 2-1 Creating or Modifying a PM Template Table 2-2 Assigning a Port PM Template Table 2-3 Assigning an EOS Port PM Template Table 2-4 Assigning a Subport PM Template Table 2-5 Assigning a Service PM Template Table 2-6 Assigning a TransAccess 100 Mux PM Template Table 2-7 Viewing Port or Subport PM Data Table 2-8 Viewing Service PM Data Table 2-9 Viewing Signal Path Trace Data Table 2-10 PM Report Generation Table 2-11 DS1 Port PM Parameters Near End Table 2-12 DS1 Port PM Parameters Far End Table 2-13 DS3 Port PM Parameters Near End Table 2-14 DS3 Port PM Parameters Far End Table 2-15 EC1 Port PM Parameters Near-End Table 2-16 EC1 Port PM Parameters Far-End Table 2-17 SFP Optical Port PM Parameters Table 2-18 SONET Port PM Near End Table 2-19 SONET Port PM Parameters Far End Table 2-20 SONET STS Path PM Parameters Near End Table 2-21 SONET STS Path PM Parameters Far End Table 2-22 SONET VT Path PM Parameters Near End Table 2-23 SONET VT Path PM Parameters Far End Table 2-24 E1 Port PM Parameters Near End Page viii Turin Networks Release OPS3.1.x

135 Node Operations and Maintenance Guide, Section 2 Performance Monitoring Table 2-25 E1 Port PM Parameters Far End Table 2-26 E3 Port PM Parameters Near End Table 2-27 E3 Port PM Parameters Far End Table 2-28 Number of Errored Blocks that Constitute an SES Table 2-29 SDH High Order VC Path and Low Order VC3 PM Parameters Near End Table 2-30 SDH High Order VC Path and Low Order VC3 PM Parameters Far End Table 2-31 SDH Port PM Near End Table 2-32 SDH Port PM Far End Table 2-33 Number of Errored Blocks that Constitute an SES Table 2-34 SDH VC-11 and VC-12 Path PM Parameters Near End Table 2-35 SDH VC-11 and VC-12 Path PM Parameters Far End Table 2-36 EOS Port PM Parameters Table 2-37 Ethernet Equipment PM Parameters Table 2-38 Ethernet Port PM Parameters Table 2-39 Ethernet Service Port PM Parameters Release OPS3.1.x Turin Networks Page ix

136 Node Operations and Maintenance Guide, Section 2 Performance Monitoring Page x Turin Networks Release OPS3.1.x

137 SECTION 2PERFORMANCE MONITORING Chapter 1 Managing Performance Introduction Creating or Modifying a PM Template The TransNav management system provides performance monitoring (PM) functions to monitor electrical and optical signals. PM parameters are used to gather, store, and report on performance data. The results can be used to evaluate and analyze the effect and severity level of periodic conditions, and to facilitate early detection of problems. This chapter provides procedures for: Creating or Modifying a PM Template, page 2-1 Assigning a PM Template, page 2-5 Viewing PM Data, page 2-8 PM Timing, page 2-8 Report Generation, page 2-15 Generating a PM Report, page 2-16 For further information on performance monitoring and the management system, see the TransNav Management System GUI Guide. Creating or modifying performance monitoring templates gives the user configuration flexibility for threshold default settings and report generation parameter collection. Important: Default threshold values in the sonet_ptp_pm and sdh_ptp_pm template are based on performance monitoring for OC-3 and STM-1 rates, respectively. Turin recommends customizing these templates for rates other than OC-3 and STM-1. Note: Create EC-3/STM-1E alarm profiles with the SONET/SDH templates, like that for the OC-3/STM-1ports. The following procedure describes how to create or modify a PM template. Release OPS3.1.x Turin Networks Page 2-1

138 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Creating or Modifying a PM Template Table 2-1 Creating or Modifying a PM Template Step Procedure 1 In Map View, select Admin, then Performance Templates. The Performance Templates dialog box displays. Figure 2-1 Performance Templates Dialog Box Page 2-2 Turin Networks Release OPS3.1.x

139 Chapter 1 Managing Performance Creating or Modifying a PM Template Table 2-1 Creating or Modifying a PM Template (continued) Step Procedure 2 From the Type drop-down list, select the template type. Each ptp template is used for port or subport; each path template is used for service performance monitoring. ds1_ptp_pm: DS1 port performance monitoring ds3_ptp_pm: DS3 port performance monitoring e1_ptp_pm: E1 port performance monitoring e3_ptp_pm: E3 port performance monitoring ec1_ptp_pm: EC1 port performance monitoring eos_pm: Ethernet over SONET/SDH port performance monitoring ethernet_eq_pm: Ethernet equipment performance monitoring ethernet_ptp_pm: Ethernet port performance monitoring ethernet_svcport_pm: Ethernet service port performance monitoring per service flow sdh_hp_path_pm: SDH high order path (VC4 or VC3) performance monitoring sdh_lp_path_pm: SDH VC3 low order path performance monitoring sdh_ptp_pm: SDH port performance monitoring sdh_vc11_path_pm: VC11 low order path performance monitoring sdh_vc12_path_pm: VC12 low order path performance monitoring sonet_path_pm: SONET path performance monitoring sonet_ptp_pm: SONET port performance monitoring t100_ptp_pm: Legacy equipment. See Release 2.0 Node Operations and Maintenance Guide vt_path_pm: SONET virtual tributary (VT) path performance monitoring 3 Creating a template? Yes. Go to the next step. No. Go to Step 5. 4 Click Add, then enter a Name for the template. Go to Step 6. 5 Double-click the template row to open the template dialog box. Release OPS3.1.x Turin Networks Page 2-3

140 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Creating or Modifying a PM Template Table 2-1 Creating or Modifying a PM Template (continued) Step Procedure 6 Set thresholds for each parameter you want the system to generate threshold crossing alerts (TCA) using one of the following methods: Manually set threshold defaults. (If the threshold value is crossed prior to setting the level for the current 15-minute or 24-hour period, the system could erroneously generate Ethernet PM TCA alerts.) Click Default Thresholds to set all standard default settings if there are no non-default threshold requirements. Click Disable Thresholds and zero out all settings. The system will not generate TCAs. 7 Select the check box in the corresponding Collect column to enable Report data collection (as desired). For all service port PM parameters, the default is Disabled. 8 Click OK. The example shown below is a DS1 port performance monitoring template with standard default values and Collect (for the Report function) set. Figure 2-2 DS1 PM Configuration Template Dialog Box 9 Click Yes to synchronize the template to make it available to other nodes. Click No if you do not want to synchronize the new template. Figure 2-3 Synchronize Template Dialog Box 10 Click Done in the Performance Templates dialog box. 11 The Creating or Modifying a PM Template procedure is complete. Page 2-4 Turin Networks Release OPS3.1.x

141 Chapter 1 Managing Performance Assigning an EOS Port PM Template Assigning a PM Template Assigning a Port PM Template Choose one of the following topics by object type (e.g., port) to assign a PM template: Assigning a Port PM Template, page 2-5 Assigning an EOS Port PM Template, page 2-5 Assigning a Subport PM Template, page 2-6 Assigning a Service PM Template, page 2-6 Assigning a TransAccess 100 Mux PM Template, page 2-8 The following procedure describes how to assign a port PM template to a port. Table 2-2 Assigning a Port PM Template Step Procedure 1 In Shelf View, click a module port. 2 Click the Config tab. 3 From the PM Template list, select a port PM (ptp) template. 4 Click Apply. 5 The Assigning a Port PM Template procedure is complete. Assigning an EOS Port PM Template The following procedure describes how to assign an EOS port PM template to an EOS port. Table 2-3 Assigning an EOS Port PM Template Step Procedure 1 In Shelf View, click the Ethernet tab. 2 Click an EOS port from the EOS port list, then click Edit. 3 Click Advanced. 4 From the PM Template list, select an eos_pm template. 5 Click Apply. 6 The Assigning an EOS Port PM Template procedure is complete. Release OPS3.1.x Turin Networks Page 2-5

142 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Assigning a Subport PM Template Assigning a Subport PM Template The following procedure describes how to assign a port PM template to a DS3 Transmux subport. Table 2-4 Assigning a Subport PM Template Step Procedure 1 In Shelf View, select a DS3 Transmux module port. 2 Click the Config tab. 3 From the Subport row, PM Template column list, select a port (ptp) PM template matching the embedded signal subport type (e.g., ds1_ptp). 4 Click Apply. 5 The Assigning a Subport PM Template procedure is complete. Assigning a Service PM Template The following procedure describes how to assign a path PM template to a service. The service PM template is selected during service creation or editing. Table 2-5 Assigning a Service PM Template Step Procedure 1 From any view, click the Service tab. 2 Creating or editing a service? Creating: Click Add to access the Create Service tab. Editing: Double-click a service row to access the Edit Service tab. 3 Click Advanced to access the Advanced Parameters dialog box. Page 2-6 Turin Networks Release OPS3.1.x

143 Chapter 1 Managing Performance Assigning a Service PM Template Table 2-5 Assigning a Service PM Template (continued) Step Procedure 4 The Advanced Parameters dialog box appears. From the Source PM Template and Destination PM Template or Service Port PM list, select a PM template. 4 3 Figure 2-4 Service PM Template Parameters 5 Click Done and continue creating or editing the service. 6 The Assigning a Service PM Template procedure is complete. Release OPS3.1.x Turin Networks Page 2-7

144 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Assigning a TransAccess 100 Mux PM Template Assigning a TransAccess 100 Mux PM Template The following procedure describes how to assign a PM template to a TransAccess 100 Mux. Table 2-6 Assigning a TransAccess 100 Mux PM Template Step Procedure 1 In Shelf View, select a TransAccess 100 Mux icon Click the Config tab. Figure 2-5 TransAccess 100 Mux Config Tab 3 From the PM Template list, select a PM template. 4 Click Apply. 5 The Assigning a TransAccess 100 Mux PM Template procedure is complete. 4 Viewing PM Data Choose one of the following topics by object type (e.g., port) to view PM data: Viewing Port or Subport PM Data, page 2-9. Viewing Service Path PM Data, page PM Timing. Performance monitor on-screen Samples (bin) column timestamps use the Traverse node time. The on-screen PM Refresh Time uses the TransNav GUI time. The Traverse node time and TransNav GUI time could be different if they are in different time zones. Page 2-8 Turin Networks Release OPS3.1.x

145 Chapter 1 Managing Performance Viewing Port or Subport PM Data Viewing Port or Subport PM Data The following procedure describes how to view port or subport PM data. Table 2-7 Viewing Port or Subport PM Data Step Procedure 1 In Shelf View, click the Performance tab and select a port (1a), a subport (1b), or a TransAccess 100 Mux. 1a 1b Figure 2-6 Object Selection for PM 2 On the Interval (2a) list (see the graphic in the next step), you can select 15-minute or 24-hour intervals. You can view up to thirty-two 15-minute or two 24-hour Samples (2b) current and previous. Release OPS3.1.x Turin Networks Page 2-9

146 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Viewing Port or Subport PM Data Table 2-7 Viewing Port or Subport PM Data (continued) Step Procedure 3 Click Refresh to re-display updated PM values. 2a 2b Figure 2-7 Port Performance Tab 4 If you click Reset, the counters reset to zero. 5 Click Print to print the current screen. 6 Click Save to save the PM data to a file. 7 The Viewing Port or Subport PM Data procedure is complete. Page 2-10 Turin Networks Release OPS3.1.x

147 Chapter 1 Managing Performance Viewing Service Path PM Data Viewing Service Path PM Data The following procedure describes how to view service path PM data. Table 2-8 Viewing Service PM Data Step Procedure 1 In Shelf View, click the Service tab. 2 Select a service. Right-click and select Show Tx/Rx Path to display the Path Display for Service screen. 2 4a 3 4b 5 Figure 2-8 Path Display for Services Screen 3 Click the PM (Performance) tab to display the PM screen. 4 From the Path Display for Service screen, for either a Tx or Rx table row, select an Active or Standby Hop (4a). Your selection appears in the Hop Id field on the PM tab (4b). 5 Click the Refresh button on the PM tab to display the performance monitoring data. Release OPS3.1.x Turin Networks Page 2-11

148 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Viewing Service Path PM Data Table 2-8 Viewing Service PM Data (continued) Step Procedure 6 On the Interval list (6a) you can select 15-minute or 24-hour intervals. You can view up to thirty-two 15-minute or two 24-hour Samples (6b) current and previous. 6b a Figure 2-9 Service Performance (PM) Tab 7 Click Refresh to re-display updated PM values. 8 If you click Reset, the counters reset to zero. 9 Click Print to print the current screen. 10 Click Save to save the PM data to a file. 11 The Viewing Service PM Data procedure is complete. Page 2-12 Turin Networks Release OPS3.1.x

149 Chapter 1 Managing Performance Viewing Signal Path Trace Data Viewing Signal Path Trace Data The following procedure describes how to view transmission and received signal path trace information. Table 2-9 Viewing Signal Path Trace Data Step Procedure 1 In Shelf View, click the Service tab. 2 Select a service. Right-click and select Show Tx/Rx Path to display the Path Display for Service screen. 2 4a 3 4b 5 Figure 2-10 Path Display for Service Screen 3 Click the CTP tab to display the CTP screen. 4 From the Path Display for Service screen, for either a Tx or Rx table row, select an Active Hop (4a). Your selection appears in the EndPoint field on the CTP tab (4b). Release OPS3.1.x Turin Networks Page 2-13

150 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Viewing Signal Path Trace Data Table 2-9 Viewing Signal Path Trace Data (continued) Step Procedure 5 In the Alarm Profile field, one of the following profile values displays: useparent: The alarm profile of the containing object (Parent) based on the following superset and subset definitions: Port: Contains line and path alarms and is the superset. High-order path: Contains high- and low-order path alarms and is a subset of port profiles. Low-order path: Contains only low-order path alarms and is a finer subset of high-order path profiles. STS path. Contains STS and VT path alarms and is a subset of port profiles. VT path: Contains only VT path alarms and is a finer subset of STS path profiles. default: The default alarm profile matching the CTP object type. <user-defined>: Depending on the CTP object type, this value indicates a user-defined alarm profile of one of the following path alarm profile types: sdh_hp sdh_lp sonet_sts sonet_vt 6 Click Received/Transmitted Path Overhead. The Received/Transmitted Path Overhead dialog box displays. (The name of the button and the resulting dialog box corresponds to whether you selected a Tx or Rx active hop.) Figure 2-11 Path Overhead Dialog Box 7 Click Refresh to re-display updated PM values. 8 Click Done to return to the previous screen. 9 The Viewing Service PM Data procedure is complete. Page 2-14 Turin Networks Release OPS3.1.x

151 Chapter 1 Managing Performance Report Generation Report Generation Through the TransNav management system, you have the ability to generate different reports. You can customize the reports for your own uses, as well as specify generation dates and generation periods. Generate the following reports for all nodes in a domain or for a specific node: Performance monitoring Historical alarm Node inventory Historical event Resource availability Domain service Service availability The following figure shows a sample event report. Figure 2-12 Event Report Sample Release OPS3.1.x Turin Networks Page 2-15

152 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Generating a PM Report Generating a PM Report The following procedure describes how to generate a PM report. Important: Performance monitoring data collection for the Report function occurs when the corresponding PM template Collect check boxes are set. See Creating or Modifying a PM Template, page 1-2. Table 2-10 PM Report Generation Step Procedure 1 From the Admin menu, select Reports ,4 5 Figure 2-13 Reports Screen 2 Select a PM report from the Report Schedulers list. 3 Click Generate Now. Entries appear in the Report List section. 4 Select a Report List entry. 5 Click View Report. 6 The PM Report Generation procedure is complete. Page 2-16 Turin Networks Release OPS3.1.x

153 SECTION 2PERFORMANCE MONITORING Chapter 2 SONET Performance Parameters Introduction This chapter provides performance parameter information for: DS1 Port PM, page 2-18 DS3 Port PM, page 2-21 EC-1 Port PM, page 2-24 Small Form-Factor Pluggable Optical Port PM, page 2-26 SONET Port PM, page 2-27 SONET STS Path Layer PM, page 2-31 SONET VT Path Layer PM, page 2-33 For further information on performance monitoring and the management system, see the TransNav Management System GUI Guide. Release OPS3.1.x Turin Networks Page 2-17

154 Node Operations and Maintenance Guide, Section 2: Performance Monitoring DS1 Port PM DS1 Port PM The Traverse system provides near- and far-end DS1 port PM parameters. Table 2-11 DS1 Port PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold Line Near End NE CV_L (Code Violations) NE ES_L (Errored Seconds) NE SES_L (Severely Errored Seconds) NE LOSS_L (Loss of Signal Seconds Path Near End NE CV_P (Code Violations) NE ES_P (Errored Seconds) NE SES_P (Severely Errored Seconds) NE AISS_P (Alarm Indication Signal Seconds) Count of both bipolar violations (BPV) and excessive zeros (EXZ) occurring over the accumulation period. An EXZ increments the CV Line count by one regardless of the length of the zero string. Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded. Count of 1-second intervals during which BPVs plus EXZs exceed 1544, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded. Count of one or more 1-second intervals containing LOS defects. Count of frame synchronization bit errors in the SF format or a count of CRC-6 errors in the ESF format. Count of 1-second intervals containing any of the following: CRC-6 errors (ESF) CS events (ESF, SF) SEF defects (ESF, SF) LOS defects (ESF, SF) FE errors (SF) Count of 1-second intervals containing: 320 or more CRC-6 errors (ESF) 8 or more FE events (SF) one or more SEF or LOS defects (ESF, SF) Count of 1-second intervals containing one or more AIS defects Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: 100 Page 2-18 Turin Networks Release OPS3.1.x

155 Chapter 2 SONET Performance Parameters DS1 Port PM Table 2-11 DS1 Port PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold NE SAS_P (Severely Errored Frames/Alarm Indication Signal Seconds) Count of 1-second intervals containing one or more of either SEF defects or LOS/AIS defects Default: Default: 17 NE CSS_P (Controlled Slip Seconds Currently not supported NE UAS_P (Unavailable Seconds) Count of 1-second intervals for which the DS1 path is unavailable Default: Default: 100 NE FC_P (Failure Counts) Count of the number of near-end failure events on the path. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 Table 2-12 DS1 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Line Far End FE ES_L (Errored Seconds) Currently not supported Path Far End FE CV_P (Code Violations) Currently not supported FE ES_P (Errored Seconds Path) Count of 1-second intervals containing any of the following: CRC-6 errors (ESF) CS events (ESF, SF) SEF defects (ESF, SF) LOS defects (ESF, SF) FE errors (SF) Default: Default: 648 Release OPS3.1.x Turin Networks Page 2-19

156 Node Operations and Maintenance Guide, Section 2: Performance Monitoring DS1 Port PM Table 2-12 DS1 Port PM Parameters Far End (continued) Parameter Definition 15-min Threshold Daily Threshold FE SES_P (Severely Errored Seconds Path) FE SEFS_P (Severely Errored Framing Seconds Path) FE CSS_P (Controlled Slip Seconds Path) FE UAS_P (Unavailable Seconds Path) FE FC_P (Failure Count Path) Count of 1-second intervals containing: 320 or more CRC-6 errors (ESF) 8 or more FE events (SF) 1 or more SEF or LOS defects (ESF, SF) Currently not supported Currently not supported Count of 1-second intervals for which the DS1 path is unavailable Default: Default: 10 Count of far-end path failure (RAI) events Default: Default: Default: Page 2-20 Turin Networks Release OPS3.1.x

157 Chapter 2 SONET Performance Parameters DS3 Port PM DS3 Port PM The Traverse system provides near- and far-end DS3 (clear channel or transmux) port PM parameters. Table 2-13 DS3 Port PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold Line Near End CV-L (Code Violations) ES-L (Errored Seconds) SES-L (Severely Errored Seconds) Path PBit Near End CV-P (Code Violations) ES-P (Errored Seconds SES-P (Severely Errored Seconds) UAS-P (Unavailable Seconds) Count of both bipolar violations (BPV) and excessive zeros (EXZ) occurring over the accumulation period. An EXZ increments the CV Line count by one regardless of the length of the zero string. BPVs that are part of the zero substitution code are excluded. Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded. Count of seconds during which BPVs plus EXZs exceed 44, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded. Count of P-bit parity check CVs. The receipt of non-identical P-bits corresponding to the same DS3 M-Frame also constitutes a parity check CV. Count of seconds containing one or more P-bit parity errors, one or more SEF defects, or one or more LOS defects. Count of seconds containing more than 44 P-bit parity violations, one or more SEF defects, or one or more LOS defects. Count of 1-second intervals during which the DS3 path is unavailable Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: 10 Release OPS3.1.x Turin Networks Page 2-21

158 Node Operations and Maintenance Guide, Section 2: Performance Monitoring DS3 Port PM Table 2-13 DS3 Port PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold FC-P (Failure Counts) Path CBit Near End CVC-P (Code Violations) ESC-P (Errored Seconds) SESC-P (Severely Errored Seconds) UASC-P (Unavailable Seconds C-bit parity application) Count of the number of near-end path failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins. Both CP-bit parity CVs (CVCP-P) and CVP-P counts are defined and may be supported since they can convey different information. The first is the count of CP-bit parity errors occurring in the accumulation period. The CVP-P parameter count is the same as described above. Two versions of the ES parameter may be accumulated and stored. The ESCP-P parameter is a count of seconds containing one or more CP-bit parity errors, one or more SEF defects, or one or more LOS defects. The ESP-P parameter count is the same as described above. Two versions of the SES parameter may be accumulated and stored. The SESCP-P parameter is a count of seconds containing more than 44 CP-bit parity errors, one or more SEF defects, or one or more LOS defects. The SESP-P parameter is the same as described above. Count of 1-second intervals during which the DS3 path is unavailable Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: 10 Page 2-22 Turin Networks Release OPS3.1.x

159 Chapter 2 SONET Performance Parameters DS3 Port PM Table 2-14 DS3 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Path CBit Far End FE CVC-P (Code Violations) Counted when the three FEBE bits in an M-frame are not all set to Default: Default: 3820 FE ESC-P (Errored Seconds) Count of 1-second intervals containing one or more M-frames with the three FEBE bits not all set to one, or one or more far-end SEF/LOS defects Default: Default: 250 FE SESC-P (Severely Errored Seconds) Count of 1-second intervals containing one or more than 44 M-frames with the three FEBE bits not all set to one, or one or more far-end SEF/LOS defects Default: Default: 40 FE UASC-P (Unavailable Seconds Count of 1-second intervals during which the DS3 path is unavailable Default: Default: 10 FE FCC-P (Failure Counts) Count of the number of far-end path failure events. A failure event begins when the RFI-P failure is declared, and ends when the RFI-P failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 Release OPS3.1.x Turin Networks Page 2-23

160 Node Operations and Maintenance Guide, Section 2: Performance Monitoring EC-1 Port PM EC-1 Port PM The Traverse system provides near- and far-end EC-1 port PM parameters. Table 2-15 EC1 Port PM Parameters Near-End Parameter Definition 15-min Threshold Daily Threshold LINE CV (Coding Violations Line) Count of BIP errors detected at the line layer (i.e., using the B2 bytes in the incoming SONET signal). Up to 8xN BIP errors can be detected per STS-N frame, with each error incrementing the CV-L current second register Default: Default: 3865 ES (Errored Seconds Line) Count of the seconds during which (at any point during the second) at least one Line layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present Default: Default: 250 SES (Severely Errored Seconds Line) Count of the seconds during which 52 or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present Default: Default: 40 UAS (Unavailable Seconds Line) Count of the seconds during which the Line was considered unavailable. A Line becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ls, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ls Default: Default: 40 FC (Failure Counts Line) Count of the number of near-end Line failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 SECTION CV (Code Violations Section) Count of BIP-8 errors that are detected at the section layer of the incoming signal. Count of BIP errors detected at the section layer (i.e., using the B1 bytes in the incoming SONET signal). Up to 8 section BIP errors can be detected per STS-N frame, with each error incrementing the CV-S register Default: Default: 3820 Page 2-24 Turin Networks Release OPS3.1.x

161 Chapter 2 SONET Performance Parameters EC-1 Port PM Table 2-15 EC1 Port PM Parameters Near-End (continued) Parameter Definition 15-min Threshold Daily Threshold ES (Errored Seconds Section) Count of 1-second intervals during which (at any point during the second) at least one section layer BIP error was detected or an SEF or LOS defect was present Default: Default: 250 SES (Severely Errored Seconds Section) Count of the seconds during which 154 or more section layer BIP errors were detected or an SEF or LOS defect was present Default: Default: 40 SEFS (Severely Errored Framing Seconds Section) Count of 1-second intervals during which (at any point during the second) an SEF defect was present. An SEF defect is detected when an incoming signal has a minimum of four consecutive errored framing patterns Default: Default: 8 Table 2-16 EC1 Port PM Parameters Far-End Parameter Definition 15-min Threshold Daily Threshold LINE CVFE (Coding Violations Line, Far-End) Count of the number of BIP errors detected by the far-end LTE and reported back to the near-end LTE using the REI-L indication in the Line overhead. For SONET signals at rates below OC-48, up to 8xN BIP errors per STS-N frame can be indicated using the REI-L. For OC-48 signals, up to 255 BIP errors per STS-N frame can be indicated. The CV-LFE current second register increments for each BIP error indicated by the incoming REI-L Default: Default: 3865 ESFE (Errored Seconds Line, Far-End) Count of the seconds during which (at any point during the second) at least one Line BIP error was reported by the far-end LTE (using the REI-L indication) or an RDI-L defect was present Default: Default: 250 SESFE (Severely Errored Seconds Line, Far-End) Count of the seconds during which K or more Line BIP errors were reported by the far-end LTE or an RDI-L defect was present. The number of reported far-end BIP errors causing a second to be considered an SES-LFE Default: Default: 40 Release OPS3.1.x Turin Networks Page 2-25

162 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Small Form-Factor Pluggable Optical Port PM Table 2-16 EC1 Port PM Parameters Far-End (continued) Parameter Definition 15-min Threshold Daily Threshold UASFE (Unavailable Seconds Line, Far-End) Count of the seconds during which the Line is considered unavailable at the far end. A Line is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-LFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-LFEs Default: Default: 40 FCFE (Failure Counts Line, Far-End) Count of the number of far-end Line failure events. A failure event begins when the RFI-L failure is declared, and ends when the RFI-L failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 Small Form-Factor Pluggable Optical Port PM The Traverse system provides the following performance (diagnostic) monitoring Table 2-17 SFP Optical Port PM Parameters Parameter Measured Temperature Measured Supply Voltage Measured TX Bias Current Measured TX Output Power Measured TX Input Power Definition A measure of the internal transceiver temperature yielding a value within the total range of -128 to +128 celsius. A measure of the internal transceiver supply voltage yielding a value within the total range of 0 to volts. A measure of the TX bias current yielding a value within the total range of 0 to 131 ma. A measure of the TX output power based on the measurement of laser monitor photodiode current and yielding a value within the total range of 0 to mw. A measure of the TX input power yielding a value within the total range of 0 to mw (~ -40 to +8.2 dbm). Absolute accuracy is dependent upon the exact optical wavelength. Page 2-26 Turin Networks Release OPS3.1.x

163 Chapter 2 SONET Performance Parameters SONET Port PM SONET Port PM The Traverse system provides the following near- and far-end SONET port performance monitoring parameters. Important: Default threshold values in the sonet_ptp_pm template are based on performance monitoring for OC-3 rates. Turin recommends customizing this template for rates other than OC-3. Table 2-18 SONET Port PM Near End Parameter Definition 15-min Threshold Daily Threshold Section Near End CV-S (Coding Violation) Count of BIP (Bit Interleaved Parity) errors detected at the Section layer (i.e., using the B1 byte in the incoming SONET signal). Up to 8 section BIP errors can be detected per STS-N frame, with each error incrementing the CV-S register Default: Default: 3820 ES-S (Errored Seconds) Count of 1-second intervals during which (at any point during the second) at least one Section layer BIP error was detected or an SEF or LOS defect was present Default: Default: 250 SES-S (Severely Errored Seconds) Count of the seconds during which K or more Section layer BIP errors were detected or an SEF or LOS defect was present. K has the following values: 154 for OC3 615 for OC for OC for OC Default: Default: 40 SEFS-S (Severely Errored Framing Seconds) Count of 1-second intervals during which (at any point during the second) an SEF defect was present. An SEF defect is detected when an incoming signal has a minimum of four consecutive errored framing patterns Default: Default: 8 Line Near end CV-L (Coding Violation) Count of BIP errors detected at the Line layer (i.e., using the B2 bytes in the incoming SONET signal). Up to 8xN BIP errors can be detected per STS-N frame, with each error incrementing the CV-L current second register Default: Default: Release OPS3.1.x Turin Networks Page 2-27

164 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SONET Port PM Table 2-18 SONET Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold ES-L (Errored Seconds) Count of the seconds during which (at any point during the second) at least one Line layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present Default: Default: 250 SES-L (Severely Errored Seconds) Count of the seconds during which K or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: 154 for OC3 615 for OC for OC for OC Default: Default: 40 UAS-L (Unavailable Seconds) Count of the seconds during which the Line was considered unavailable. A Line becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ls, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ls Default: Default: 40 FC-L (Failure Counts) Count of the number of near-end Line failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 PSCW-L (Protection Switch Counts Working) Count of the number of times that an OC-N line service (i.e., BLSR, 1+1 ASP) switches from the working to the protecting line. This count also includes the number of times the service (revertive) switches back from the protecting to the working line Default: Default: 10 Page 2-28 Turin Networks Release OPS3.1.x

165 Chapter 2 SONET Performance Parameters SONET Port PM Table 2-18 SONET Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold PSDW-L (Protection Switch Duration Working) Count of the seconds that the working line was being used to carry an OC-N line service (i.e., BLSR, 1+1 ASP) Default: Default: 40 PSCP-L (Protection Switch Counts Protecting) Count of the number of times that an OC-N line service (i.e., BLSR, 1+1 ASP) switches from the protecting to any working line. This count also includes the number of times service (revertive) switches back from the protecting to the working line Default: Default: 10 PSDP-L (Protection Switching Duration Protecting) Count of the seconds that the protecting line was being used to carry OC-N line service (i.e., BLSR, 1+1 ASP) Default: Default: 40 Table 2-19 SONET Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Line Far End FE CV-L (Coding Violations) Count of the number of BIP errors detected by the far-end LTE and reported back to the near-end LTE using the REI-L indication in the Line overhead. For SONET signals at rates below OC48, up to 8xN BIP errors per STS-N frame can be indicated using the REI-L. For OC48 signals, up to 255 BIP errors per STS-N frame can be indicated. The CV-LFE current second register increments for each BIP error indicated by the incoming REI-L Default: Default: FE ES-L (Errored Seconds Far End) Count of the seconds during which (at any point during the second) at least one Line BIP error was reported by the far-end LTE (using the REI-L indication) or an RDI-L defect was present Default: Default: 250 Release OPS3.1.x Turin Networks Page 2-29

166 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SONET Port PM Table 2-19 SONET Port PM Parameters Far End (continued) Parameter Definition 15-min Threshold Daily Threshold FE SES-L (Severely Errored Seconds Far End) Count of the seconds during which K or more Line BIP errors were reported by the far-end LTE or an RDI-L defect was present. The number of reported far-end BIP errors causing a second to be considered an SES-LFE. K has the following values: 154 for OC3 615 for OC for OC for OC Default: Default: 40 FE UAS-L (Unavailable Seconds) Count of the seconds during which the Line is considered unavailable at the far end. A Line is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-LFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-LFEs Default: Default: 40 FC (Failure Counts) Count of the number of far-end Line failure events. A failure event begins when the RFI-L failure is declared, and ends when the RFI-L failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 Page 2-30 Turin Networks Release OPS3.1.x

167 Chapter 2 SONET Performance Parameters SONET STS Path Layer PM SONET STS Path Layer PM The Traverse system provides the following performance monitoring parameters for SONET STS path layer services. Table 2-20 SONET STS Path PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold CV-P (Coding Violations) Count of BIP errors detected at the STS Path layer (i.e., using the B3 byte in the incoming STS path overhead). Up to 8 BIP errors can be detected per frame, with each error incrementing the CV-P current second register Default: Default: ES-P (Errored Seconds) Count of the seconds during which (at any point during the second) at least one path BIP error was detected, or an LOS (or a lower-layer, traffic-related, near-end defect), an LOP-P or, if the STS PTE monitoring the path supports ERDI-P for that path, an UNEQ-P or TIM-P (Trace Identifier Mismatch) defect was present Default: Default: 250 SES-P (Severely Errored Seconds) Count of the seconds during which 2400 or more path BIP errors were detected, or an LOS (or a lower-layer, traffic-related, near-end defect), an LOP-P or, if the STS PTE monitoring the path supports ERDI-P for that path, an UNEQ-P or TIM-P defect was present. The number of BIP errors causes a second to be considered an SES-P Default: Default: 40 UAS-P (Unavailable Seconds) Count of the seconds during which the path was considered unavailable. A path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ps, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps Default: Default: 40 Release OPS3.1.x Turin Networks Page 2-31

168 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SONET STS Path Layer PM Table 2-21 SONET STS Path PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold FE CV-P (Coding Violations) Count of the number of BIP errors detected by the far-end STS PTE and reported back to the near-end STS PTE using the REI-P indication in the STS Path overhead. Up to 8 BIP errors per frame can be indicated. The CV-PFE current second register increments for each BIP error indicated by the incoming REI-P Default: Default: FE ES-P (Errored Seconds) Count of the seconds during which (at any point during the second) at least one STS Path BIP error was reported by the far-end STS PTE (using the REI-P indication), a one-bit RDI-P was present, or (if ERDI-P is supported) an ERDI-P Server or Connectivity defect was present Default: Default: 250 FE SES-P (Severely Errored Seconds) Count of the seconds during which 2400 or more STS Path BIP errors were reported by the far-end STS PTE, a one-bit RDI-P was present, or (if ERDI-P is supported) an ERDI-P Server or connectivity defect was present. The number of reported far-end BIP errors causing a second to be considered an SES-PFE Default: Default: 40 FE UAS-P (Unavailable Seconds) Count of the seconds during which the STS Path is considered unavailable at the far end. A path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-PFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-PFEs Default: Default: 40 Page 2-32 Turin Networks Release OPS3.1.x

169 Chapter 2 SONET Performance Parameters SONET VT Path Layer PM SONET VT Path Layer PM The Traverse system provides the following performance monitoring parameters for SONET VT path layer services. Table 2-22 SONET VT Path PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold CV-V (Coding Violations) Count of BIP errors detected at the VT Path layer (i.e., using bits 1 and 2 of the V5 byte in the incoming VT Path overhead). Up to 2 BIP errors can be detected per VT superframe, with each error incrementing the CV V current second register Default: Default: ES-V (Errored Seconds) Count of the seconds during which (at any point during the second) at least one VT Path BIP error was detected, or an LOS defect (or a lower-layer, traffic-related, near-end defect, see Section ), an LOP V defect or, if the VT PTE monitoring the path supports ERDI V for that path, an UNEQ V defect was present Default: Default: 648 SES-V (Severely Errored Seconds) Count of the seconds during which 600 or more VT Path BIP errors were detected, or an LOS defect (or a lower-layer, traffic-related, near-end defect, see Section ), an LOP V defect or, if the VT PTE monitoring the path supports ERDI V for that path, an UNEQ V defect was present Default: Default: 100 UAS-V (Unavailable Seconds) Count of the seconds during which the VT Path was considered unavailable. A VT Path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES Vs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES Vs Default: Default: 100 Release OPS3.1.x Turin Networks Page 2-33

170 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SONET VT Path Layer PM Table 2-23 SONET VT Path PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold FE CV-V (Coding Violations) Count of the number of BIP errors detected by the far-end VT PTE and reported back to the near-end VT PTE using the REI V indication in the VT Path overhead. Note that only 1 BIP error can be indicated per VT superframe using the REI V bit (out of the two BIP errors that can be detected). The CV VFE current second register increments for each BIP error indicated by the incoming REI V Default: Default: FE ES-V (Errored Seconds) Count of the seconds during which (at any point during the second) at least one VT Path BIP error was reported by the far-end VT PTE (using the REI V indication), a one-bit RDI V defect was present, or (if ERDI V is supported, see Section ) an ERDI V Server or Connectivity defect was present Default: Default: 648 FE SES-V (Severely Errored Seconds) Count of the seconds during which 600 or more VT Path BIP errors were reported by the far-end VT PTE, a one-bit RDI V defect was present, or (if ERDI V is supported) an ERDI V Server or Connectivity defect was present. The number of reported far-end BIP errors causing a second to be considered an SES VFE Default: Default: 100 FE UAS-V (Unavailable Seconds) Count of the seconds during which the VT Path is considered unavailable at the far end. A VT Path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES VFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES VFEs Default: Default: 100 Page 2-34 Turin Networks Release OPS3.1.x

171 SECTION 2PERFORMANCE MONITORING Chapter 3 SDH Performance Parameters Introduction This chapter provides performance parameter information for: E1 Port PM, page 2-36 E3 Port PM, page 2-39 SDH High and Low Order Path PM, page 2-41 SDH Port PM, page 2-45 SDH VC-11 and VC-12 Path PM, page 2-50 For further information on performance monitoring and the management system, see the TransNav Management System GUI Guide. Release OPS3.1.x Turin Networks Page 2-35

172 Node Operations and Maintenance Guide, Section 2: Performance Monitoring E1 Port PM E1 Port PM The Traverse system provides the following near- and far-end E1 port performance monitoring parameters. Table 2-24 E1 Port PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold Line Near End NE FC_L (Failure Counts) NE CV_L (Code Violations) NE ES_L (Errored Seconds) NE SES_L (Severely Errored Seconds) NE LOSS_L (Loss of Signal Seconds NE FAS_L (Frame Alignment Signal) Path Near End NE EB_P (Errored Blocks) Count of the number of near-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins. Count of both BPVs (Bipolar Violations) and EXZs (Excessive Zeros) occurring over the accumulation period. An EXZ increments the CV Line count by one regardless of the length of the zero string. Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded. Count of 1-second intervals during which BPVs plus EXZs exceed 2048, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded. Count of one or more 1-second intervals containing LOS defects. Count of one or more 1-second intervals containing FAS defects. Count of the number of blocks containing one or more bit errors Default: Default: Default: Default: Default: Default: x 10 6 Default: Default: Default: Default: Default: Default: Default: x 10 8 Default: 13,296 Page 2-36 Turin Networks Release OPS3.1.x

173 Chapter 3 SDH Performance Parameters E1 Port PM Table 2-24 E1 Port PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold NE ES_P (Errored Seconds) NE SES_P (Severely Errored Seconds) NE AISS_P (Alarm Indication Signal Seconds) NE UAS_P (Unavailable Seconds) NE BBE_P (Background Block Error) NE ESR_P (Errored Seconds Ratio) NE SESR_P (Severely Errored Seconds Ratio) NE BBER_P (Background Block Error Ratio) Count of 1-second intervals containing any of the following: CRC-6 errors (ESF) CS events (ESF, SF) SEF defects (ESF, SF) LOS defects (ESF, SF) FE errors (SF) Count of 1-second intervals containing: 320 or more CRC-6 errors (ESF). 8 or more FE events (SF). one or more SEF or LOS defects (ESF, SF). Count of 1-second intervals containing one or more AIS defects Count of 1-second intervals for which the DS1 path is unavailable Default: Default: Default: Default: 10 An errored block not occurring as part of an SES. 1 8 x 10 6 The ratio of ES to total seconds in available time during a fixed measurement interval. The ratio of SES to total seconds in available time during a fixed measurement interval. The ratio of Background Block Errors (BBE) to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs. Default: Default: Default: Default: Default: Default: Default: Default: x 10 8 Default: 13, Default: Default: Default: 10 Release OPS3.1.x Turin Networks Page 2-37

174 Node Operations and Maintenance Guide, Section 2: Performance Monitoring E1 Port PM Table 2-25 E1 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Line Far End FE ES_L (Errored Seconds) Path Far End FE ES_P (Errored Seconds) FE SES_P (Severely Errored Seconds) FE UAS_P (Unavailable Seconds) FE EB_P (Errored Blocks) FE FC_P (Failure Count) FE BBE_P (Background Block Error) Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded. Count of 1-second intervals containing any of the following: CRC-6 errors (ESF) CS events (ESF, SF) SEF defects (ESF, SF) LOS defects (ESF, SF) FE errors (SF) Count of 1-second intervals containing: 320 or more CRC-6 errors (ESF). 8 or more FE events (SF). one or more SEF or LOS defects (ESF, SF). Count of 1-second intervals for which the DS1 path is unavailable. Count of the number of blocks containing one or more bit errors Default: Default: Default: Default: x 10 6 Default: 1329 Count of far-end path failure (RAI) events Default: 10 An errored block not occurring as part of an SES. 1 8 x 10 6 Default: Default: Default: Default: Default: x 10 8 Default: 13, x 10 8 Default: 13,296 Page 2-38 Turin Networks Release OPS3.1.x

175 Chapter 3 SDH Performance Parameters E3 Port PM E3 Port PM The Traverse system provides the following near- and far-end E3 port performance monitoring parameters. Table 2-26 E3 Port PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold Line Near End NE CV_L (Code Violations) NE ES_L (Errored Seconds) NE SES_L (Severely Errored Seconds) Path NE EB_P (Errored Blocks) NE BBE_P (Background Block Error) NE ES_P (Errored Seconds) NE SES_P (Severely Errored Seconds) NE UAS_P (Unavailable Seconds) NE ESR_P (Errored Seconds Ratio) Count of both BPVs (Bipolar Violations) and EXZs (Excessive Zeros) occurring over the accumulation period. An EXZ shall increment the CV Line count by one regardless of the length of the zero string. BPVs that are part of the zero substitution code are excluded. Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded. Count of seconds during which BPVs plus EXZs exceed 44, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded. Count of the number of blocks containing one or more bit errors. An errored block not occurring as part of an SES. Count of seconds containing one or more P-bit parity errors, one or more SEF defects, or one or more LOS defects. Count of seconds containing more than 44 P-bit parity violations, one or more SEF defects, or one or more LOS defects. Count of 1-second intervals during which the DS3 path is unavailable. The ratio of ES to total seconds in available time during a fixed measurement interval. Default: Default: Default: 65 Default: 648 Default: 10 Default: 100 Default:13296 Default: Default:13296 Default: Default: 25 Default: Default: 4 Default: Default: 10 Default: 10 Default: 4 Default: 10 Release OPS3.1.x Turin Networks Page 2-39

176 Node Operations and Maintenance Guide, Section 2: Performance Monitoring E3 Port PM Table 2-26 E3 Port PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold NE SESR_P (Severely Errored Seconds Ratio) NE BBER_P (Background Block Error Ratio) NE FC_P (Failure Counts) The ratio of SES to total seconds in available time during a fixed measurement interval. The ratio of Background Block Errors (BBE) to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs. Count of the number of near-end path failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins. Default: 4 Default: 10 Default: 4 Default: Default: 4 Default: 40 Table 2-27 E3 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Path Far End FE EB_P (Errored Blocks) FE ES_P (Errored Seconds) FE SES_P (Severely Errored Seconds) Count of the number of blocks containing one or more bit errors. Count of seconds containing one or more P-bit parity errors, one or more SEF defects, or one or more LOS defects. Count of seconds containing more than 44 P-bit parity violations, one or more SEF defects, or one or more LOS defects. Default:13296 Default: Default: 25 Default: Default: 4 Default: 40 Page 2-40 Turin Networks Release OPS3.1.x

177 Chapter 3 SDH Performance Parameters SDH High and Low Order Path PM Table 2-27 E3 Port PM Parameters Far End (continued) Parameter Definition 15-min Threshold Daily Threshold FE UAS_P (Unavailable Seconds Count of 1-second intervals during which the DS3 path is unavailable Default: Default: 10 FE FC_P (Failure Counts) Count of the number of far-end path failure events. A failure event begins when the RFI-P failure is declared, and ends when the RFI-P failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins. Default: 4 Default: 40 SDH High and Low Order Path PM The Traverse system provides the following SDH high order (VC-4 or VC-3) and low order (VC-3) path performance monitoring parameters. The following table lists the block size and the threshold for errored blocks for each path layer. Table 2-28 Number of Errored Blocks that Constitute an SES VC type Bits/Block Blocks/Second Threshold of EBs for SES VC VC-4 18, VC-4-4c 75, VC-4-16c 300, Release OPS3.1.x Turin Networks Page 2-41

178 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SDH High and Low Order Path PM The following table lists the supported performance monitoring parameters for SDH paths. Table 2-29 SDH High Order VC Path and Low Order VC3 PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold EB-HP EB-LP (Errored Block) A block is a set of consecutive bits associated with the path. An errored block contains one or more bits with an error. See Table 2-28 Number of Errored Blocks that Constitute an SES, page 2-41 to determine how many bits are in one block for each container type (VC-N). 1 7,200,000 Default: 20, ,200,000 Default: 200,000 ES-HP ES-LP (Errored Seconds) Count of 1-second period with at least one errored block or one defect Default: ,400 Default: 250 SES-HP SES-LP (Severely Errored Seconds) Count of a 1-second period which contains 30% or more errored blocks or at least one defect. See Table 2-28 Number of Errored Blocks that Constitute an SES, page 2-41 to determine how many errored blocks constitute an SES on the path Default: ,400 Default: 40 When a near-end SES occurs as a result of a near-end defect, the far-end performance is not evaluated during that second. However, if a near-end SES occurs as a result of 30% or more EBs, performance monitoring at the far end continues. UAS-HP UAS-LP (Unavailable Seconds) Count of the seconds during which the path was considered unavailable. A path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ps, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps Default: ,400 Default: 40 BBE-HP BBE-LP (Background Block Error) Count of errored blocks not occurring as part of Severely Errored Seconds. 1 7,200,000 Default: 20, ,200,000 Default: 200,000 Page 2-42 Turin Networks Release OPS3.1.x

179 Chapter 3 SDH Performance Parameters SDH High and Low Order Path PM Table 2-29 SDH High Order VC Path and Low Order VC3 PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold FC-HP FC-LP (Failure Counts) Count of the number of near-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 10 PPJC-DET-HP PPJC-DET-LP (Positive Pointer Justifications Detected) Count of the positive pointer justifications detected on the path. 1 1,048,575 Default: ,777,215 Default: 6000 NPJC-DET-HP NPJC-DET-LP (Negative Pointer Justifications Detected) Count of the negative pointer justifications detected on the path. 1 1,048,575 Default: ,777,215 Default: 6000 PPJC-GEN-HP PPJC-GEN-LP (Positive Pointer Justifications Generated) Count of the positive pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference. 1 1,048,575 Default: ,777,215 Default: 6000 NPJC-GEN-HP NPJC-GEN-LP (Negative Pointer Justifications Generated) Count of the negative pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference. 1 1,048,575 Default: ,777,215 Default: 6000 Release OPS3.1.x Turin Networks Page 2-43

180 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SDH High and Low Order Path PM Table 2-30 SDH High Order VC Path and Low Order VC3 PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold FE EB-HP FE EB-LP (Errored Blocks) Count of the number of BIP errors detected by the far-end node and reported back to the near-end node using the overhead bytes. Up to 8 BIP errors per frame can be indicated Default: 20, Default: 30,000 FE ES-HP FE ES-LP (Errored Seconds) Count of the seconds during which (at any point during the second) at least one defect is detected at the far end Default: Default: 200 FE SES-HP FE SES-LP (Severely Errored Seconds) Count of seconds which contains 30% or more errored blocks or at least one defect at the far end Default: Default: 10 FE UAS-HP FE UAS-LP (Unavailable Seconds) Count of the seconds during which the path is considered unavailable at the far end. A path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-PFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-PFEs Default: Default: 10 FE BBE-HP FE BBE-LP (Background Block Error) Count of errored blocks at the far end not occurring as part of Severely Errored Seconds Default: 36, Default: 48,000 FE FC-HP FE FC-LP (Failure Counts) Count of the number of far-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 10 Page 2-44 Turin Networks Release OPS3.1.x

181 Chapter 3 SDH Performance Parameters SDH Port PM SDH Port PM The Traverse system provides the following near- and far-end SDH port performance monitoring parameters. Important: Default threshold values in the sdh_ptp_pm template are based on performance monitoring for STM-1 rates. Turin recommends customizing this template for rates other than STM-1. Table 2-31 SDH Port PM Near End Parameter Definition 15-min Threshold Daily Threshold Regenerator Section Near End EB-RS (Errored Block) ES-RS (Errored Seconds) SES-RS (Severely Errored Seconds) BBE-RS (Background Block Error) Count of BIP (Bit Interleaved Parity) errors detected at the regenerator section layer (i.e., using the B1 byte in the incoming SDH signal). Up to 8 section BIP errors can be detected per STM-N frame, with each error incrementing the EB-RS register. Count of 1-second intervals during which (at any point during the second) at least one regenerator section layer BIP error was detected or at least one defect was present. Count of the seconds during which K or more regenerator section layer BIP errors were detected or at least one defect was present. K has the following values: 154 for STM1 615 for STM for STM for STM64 Count of error block not occurring as part of Severely Errored Seconds Default: 10, Default: 100,000 Recommended defaults for rates other than STM-1: STM-0: 9,600 STM-4: 115,200 STM-16: 460,800 STM-64:1,843, Default: Default: Default: 10,000 STM-0: 96,000 STM-4: 288,000 STM-16: 1,152,000 STM-64: 18,432, Default: ,400 Default: Default: 100,000 Recommended defaults for rates other than STM-1: STM-0: 9,600 STM-4: 115,200 STM-16: 460,800 STM-64:1,843,200 STM-0: 96,000 STM-4: 288,000 STM-16: 1,152,000 STM-64: 18,432,000 Release OPS3.1.x Turin Networks Page 2-45

182 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SDH Port PM Table 2-31 SDH Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold Multiplex Section Near End EB-MS (Errored Blocks) Count of BIP errors detected at the multiplex section layer. Up to 8 section BIP errors can be detected per STM frame, with each error incrementing the EB-MS register x Defaults: 28, x Default: 288,000 ES-MS (Errored Seconds) Count of the seconds during which (at any point during the second) at least one multiplex section layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present Default: ,400 Default: 250 SES-MS (Severely Errored Seconds) Count of the seconds during which K or more multiplex section layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: 154 for STM1 615 for STM for STM for STM Default: ,400 Default: 40 UAS-MS (Unavailable Seconds) Count of the seconds during which the multiplex section was considered unavailable. A multiplex section becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-MSs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-MSs Default: Default: 40 BBE-MS (Error Blocks) Count of BIP errors detected at the multiplex section layer (i.e., using the B1 byte in the incoming SDH signal). Up to 8 section BIP errors can be detected per STM-N frame, with each error incrementing the EB-MS register x Defaults: 28, x Default: 288,000 Page 2-46 Turin Networks Release OPS3.1.x

183 Chapter 3 SDH Performance Parameters SDH Port PM Table 2-31 SDH Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold FC-MS (Failure Counts) Count of the number of near-end multiplex section failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 PSCW-MS (Protection Switch Count Working) Count of the number of times that an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) switches from the working to the protecting facility. This count also includes the number of times the service (revertive) switches back from the protecting to the working facility Default: Default: 10 PSDW-MS (Protection Switch Duration Working) Count of the seconds that the working facility was being used to carry an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) Default: ,400 Default: 600 PSCP-MS (Protection Switch Count Protecting) Count of the number of times that an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) switches from the protecting to any working facility. This count also includes the number of times the service (revertive) switches back from the protecting to the working facility Default: Default: 10 PSDP-MS (Protection Switch Duration Protecting) Count of the seconds that the protecting facility was being used to carry an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) Default: ,400 Default: 600 Release OPS3.1.x Turin Networks Page 2-47

184 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SDH Port PM Table 2-32 SDH Port PM Far End Parameter Definition 15-min Threshold Daily Threshold Multiplex Section Far End FE EB-MS (Errored Blocks FE ES-MS (Errored Seconds FE SES-MS (Severely Errored Seconds) FE UAS-MS (Unavailable Seconds) Count of BIP errors detected at the multiplex section layer. Up to 8 section BIP errors can be detected per STM frame, with each error incrementing the EB-MS register. Count of the seconds during which (at any point during the second) at least one multiplex section layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. Count of the seconds during which K or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: 154 for STM1 615 for STM for STM for STM64 Count of the seconds during which the multiplex section was considered unavailable. A multiplex section becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-MSs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-MSs x Defaults: 28, x Default: 288,000 Recommended defaults for rates other than STM-1: STM-0: 9,600 STM-4: 115,200 STM-16: 460,800 STM-64:1,843, Default: Default: Default: 4 STM-0: 96,000 STM-4: 288,000 STM-16: 1,152,000 STM-64: 18,432, ,400 Default: ,400 Default: Default: 40 Page 2-48 Turin Networks Release OPS3.1.x

185 Chapter 3 SDH Performance Parameters SDH Port PM Table 2-32 SDH Port PM Far End (continued) Parameter Definition 15-min Threshold Daily Threshold FE BBE-MS (Error Blocks) FE FC-MS (Failure Counts) Count of BIP errors detected at the multiplex section layer (i.e., using the B2 byte in the incoming SDH signal). Up to 8 section BIP errors can be detected per STM-N frame, with each error incrementing the EB-MS register. Count of the number of far end multiplex section failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins x Defaults: 28, x Default: 288,000 Recommended defaults for rates other than STM-1: STM-0: 9,600 STM-4: 115,200 STM-16: 460,800 STM-64:1,843, Default: 4 STM-0: 96,000 STM-4: 288,000 STM-16: 1,152,000 STM-64: 18,432, Default: 40 Release OPS3.1.x Turin Networks Page 2-49

186 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SDH VC-11 and VC-12 Path PM SDH VC-11 and VC-12 Path PM The Traverse system provides the following SDH VC-11 and VC-12 path performance monitoring parameters. The following table lists the block size and the threshold for errored blocks for each low order path layer. Table 2-33 Number of Errored Blocks that Constitute an SES VC type Bits/Block Blocks/Second Threshold of EBs for SES VC VC The following table lists the supported performance monitoring parameters for SDH paths. Table 2-34 SDH VC-11 and VC-12 Path PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold BBE-LP (Background Block Error) Count of errored blocks not occurring as part of Severely Errored Seconds x 10 6 Default: 5, x10 8 Default: 50,000 EB-LP (Errored Blocks) A block is a set of consecutive bits associated with the path. An errored block contains one or more bits with an error x 10 6 Default: 5, x10 8 Default: 50,000 See Table 2-33 Number of Errored Blocks that Constitute an SES, page 2-50 to determine how many bits are in one block for each container type (VC-N). ES-LP (Errored Seconds) Count of 1-second period with at least one errored block or one defect Default: ,535 Default: 250 SES-LP (Severely Errored Seconds) Count of a 1-second period which contains 30% or more errored blocks or at least one defect. See Table 2-33 Number of Errored Blocks that Constitute an SES, page 2-50 to determine how many errored blocks constitute an SES on the path Default: ,535 Default: 40 When a near-end SES occurs as a result of a near-end defect, the far-end performance is not evaluated during that second. However, if a near-end SES occurs as a result of 30% or more EBs, performance monitoring at the far end continues. Page 2-50 Turin Networks Release OPS3.1.x

187 Chapter 3 SDH Performance Parameters SDH VC-11 and VC-12 Path PM Table 2-34 SDH VC-11 and VC-12 Path PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold UAS-LP (Unavailable Seconds) Count of the seconds during which the path was considered unavailable. A path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ps, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps Default: ,535 Default: 40 FC-LP (Failure Counts) Count of the number of near-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: 2 1 4,095 Default: 10 PPJC-DET-LP (Positive Pointer Justifications Detected) Count of the positive pointer justifications detected on the path. 1 32,767 Default: ,097,151 Default: 300 NPJC-DET-LP (Negative Pointer Justifications Detected) Count of the negative pointer justifications detected on the path. 1 32,767 Default: ,097,151 Default: 300 PPJC-GEN-LP (Positive Pointer Justifications Generated) Count of the positive pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference. 1 32,767 Default: ,097,151 Default: 300 NPJC-GEN-LP (Negative Pointer Justifications Generated) Count of the negative pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference. 1 32,767 Default: ,097,151 Default: 300 PJCS-DET-LP (Pointer Justifications Seconds Detected) Count of seconds containing one or more PPJC-DET-LP or NPJC-DET-HP Default: ,535 Default: 90 Release OPS3.1.x Turin Networks Page 2-51

188 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SDH VC-11 and VC-12 Path PM Table 2-34 SDH VC-11 and VC-12 Path PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold PJCS-GEN-LP (Pointer Justifications Seconds Generated) Count of seconds containing one or more PPJC-GEN or NPJC-GEN Default: ,535 Default: 90 PJCD-LP (Pointer Justifications Difference) Absolute value of the difference between the net number of detected pointer justification counts and the net number of generated pointer justification counts. 1 32,767 Default: ,097,151 Default: 100 Table 2-35 SDH VC-11 and VC-12 Path PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold FE BBE-LP (Background Block Error) Count of errored blocks at the far end not occurring as part of Severely Errored Seconds x 10 6 Default: 5, x10 8 Default: 50,000 FE EB-LP (Errored Blocks) Count of the number of BIP errors detected by the far-end node and reported back to the near-end node using the overhead bytes. Up to 8 BIP errors per frame can be indicated x 10 6 Default: 5, x10 8 Default: 50,000 FE ES-LP (Errored Seconds) Count of the seconds during which (at any point during the second) at least one defect is detected at the far end Default: ,535 Default: 250 FE SES-LP (Severely Errored Seconds) Count of seconds which contains 30% or more errored blocks or at least one defect at the far end Default: ,535 Default: 40 Page 2-52 Turin Networks Release OPS3.1.x

189 Chapter 3 SDH Performance Parameters SDH VC-11 and VC-12 Path PM Table 2-35 SDH VC-11 and VC-12 Path PM Parameters Far End (continued) Parameter Definition 15-min Threshold Daily Threshold FE UAS-LP (Unavailable Seconds) Count of the seconds during which the path is considered unavailable at the far end. A path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-PFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-PFEs Default: ,535 Default: 40 FE FC-LP (Failure Counts) Count of the number of far-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: 2 1 4,095 Default: 10 Release OPS3.1.x Turin Networks Page 2-53

190 Node Operations and Maintenance Guide, Section 2: Performance Monitoring SDH VC-11 and VC-12 Path PM Page 2-54 Turin Networks Release OPS3.1.x

191 SECTION 2PERFORMANCE MONITORING Chapter 4 Ethernet Performance Parameters Introduction EOS Port PM This chapter provides performance parameter information for: EOS Port PM, page 2-55 Ethernet Equipment PM, page 2-57 Ethernet Port PM, page 2-59 Ethernet Service Port PM, page 2-62 For further information on performance monitoring and the management system, see the TransNav Management System GUI Guide. The system provides the following performance monitoring parameters and counters for EOS ports. Important: The table below contains common, as well as, exclusive PM (where noted) for: Traverse NGE (both NGE and NGE Plus) and TE-100 Ethernet. Note: The EOS Port PM byte counts include the 8-byte GFP header, allowing users to view the precise loads being handled by the EOS port. EOS Port PM and EOS Service PM byte counts may differ for the following reasons: If multiple services are using the same EOS port, the EOS Port PM is the cumulative total across all such services. EOS Service PM byte counts do not include the 8-byte GBP header. VLAN tags may be added or stripped as packets traverse the Ethernet card. This results in different packet sizes when counted at the service interface than when counted at the EOS port interface. Release OPS3.1.x Turin Networks Page 2-55

192 Node Operations and Maintenance Guide, Section 2: Performance Monitoring EOS Port PM In Shelf View, click the Ethernet tab, click the EOS subtab, click an EOS port from the EOS port list, then click the Performance tab. Table 2-36 EOS Port PM Parameters Parameter (Exclusive Parameter Note) TX UNICAST (TE-100 Ethernet only) TX MULTICAST (TE-100 Ethernet only) TX BROADCAST (TE-100 Ethernet only) TX FRAMES 1 TX BYTES 2,3 TX DISCARDS (Traverse NGE only) RX UNICAST (TE-100 Ethernet only) RX MULTICAST (TE-100 Ethernet only) RX BROADCAST (TE-100 Ethernet only) RX FRAMES 1 RX BYTES 23 RX DISCARDS (Traverse NGE only) GFP FCS DISCARDS 4 (Traverse NGE only) GFP CHEC DISCARDS GFP PHEC DISCARDS (Traverse NGE only) GFP FCS OR PHEC DISCARDS (TE-100 Ethernet only) Definition The number of unicast frames transmitted with no errors. The number of multicast frames that are not broadcast, transmitted with no errors. The number of broadcast frames transmitted with no errors. The number of frames transmitted (unicast, multicast, and broadcast) with no errors. The number of bytes transmitted in good frames. The number of outbound frames received by this port which were discarded. The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors. The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors. The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors. The number of frames received (unicast, multicast, and broadcast) with no errors. The number of bytes received in good frames. The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol. The number of GFP frames discarded due to frame checksum (FCS) errors. The number of GFP frames discarded due to uncorrectable core header (chec) checksum errors. The number of GFP frames discarded due to due to uncorrectable payload header (extension or type header) checksum (ehec, thec) errors. The number of GFP frames discarded due to frame checksum (FCS) errors, plus GFP frames discarded due to uncorrectable payload header (extension or type header) checksum (ehec, thec) errors. Page 2-56 Turin Networks Release OPS3.1.x

193 Chapter 4 Ethernet Performance Parameters Ethernet Equipment PM Table 2-36 EOS Port PM Parameters (continued) Parameter (Exclusive Parameter Note) RX MTU DISCARDS (TE-100 Ethernet only) GFP HEC CORRECTIONS Definition The number of frames discarded by this interface due to an excessive size. GFP frames received with single-bit HEC errors (chec, ehec or thec) that have been corrected. 1 Not supported by Traverse Legacy Ethernet. Traverse NGE and TE-100 Ethernet exclude CMF frames. 2 Traverse NGE has a complete GFP Frame, excluding CMF frames. 3 TE-100 Ethernet has Ethernet Frame only. 4 Traverse NGE payload FCS, includes CMF frames. Ethernet Equipment PM The system provides the following performance monitoring and counters for NGE equipment (both NGE and NGE Plus) events that occur during normal operation. For example, discarded frames or excessive traffic on a service. Table 2-37 Ethernet Equipment PM Parameters Parameter (Exclusive Parameter Note) Definition Counter type LAN SPI3 RX FIFO OVERRUNS LAN SPI3 TX CRC ERRORS LAN SPI3 TX PROTOCOL ERRORS Count of overrun events on FIFO for SPI-3 bus in LAN to Gardenia direction. NGE increments this counter when it discards an ingress frame from an Ethernet port due to inability of the internal switch to handle aggregate traffic arriving from Ethernet and EOS ports. The most likely cause of the congestion is an excess of aggregate traffic arriving at NGE from the Ethernet ports. There could be several events for a single discarded frame, or one event for several discarded frames. Count of SPI-3 CRC error events in the Gardenia to LAN direction. There could be several events for a single discarded frame, or one event for several discarded frames. Count of protocol error events in the Gardenia to LAN direction. Protocol events include SPI-3 CRC errors, protocol violations or parity errors. There could be several events for a single discarded frame, or one event for several discarded frames. Event Event Event Release OPS3.1.x Turin Networks Page 2-57

194 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Ethernet Equipment PM Table 2-37 Ethernet Equipment PM Parameters (continued) Parameter (Exclusive Parameter Note) LAN TX OVERSIZE CNT GARDENIA FLT DISCARDS GARDENIA BUFFER ABORTS GARDENIA SPI3 RX PROTOCOL ERRORS WAN RX FIFO OVERRUNS WAN ENCAP UNDERRUNS WAN TX ABORTS Definition Frames discarded before transmission on the physical port because they exceeded the size limit of NGE s PHY. These frames are well over the NGE module s maximum Jumbo Frame Size. Count of seconds during which Gardenia discarded frames due to overflow of internal multicast queue. This is a normal condition that can arise when there is more multicast traffic than the system can handle. Count of seconds during which Gardenia discarded frames due to inability to access RLDRAM buffer memory. This could occur if ingress traffic contains a high volume of 81-byte frames. Count of seconds during which Gardenia detected a SPI-3 RX interface protocol error in either the LAN to Gardenia or WAN to Gardenia direction. Count of overrun events on FIFO for SPI-3 bus in WAN to Gardenia direction. NGE increments this counter when it discards an ingress frame from an EOS (WAN-side) port due to inability of the internal switch to handle aggregate traffic arriving from Ethernet and EOS ports. The most likely cause of the congestion is an excess of aggregate traffic arriving at the NGE module from the Ethernet ports. There could be several events for a single discarded frame, or one event for several discarded frames. Underrun events on SPI-3 bus in Gardenia to WAN direction. There could be several events for a single discarded frame, or one event for several discarded frames. Frames discarded due to unspecified errors in Gardenia to WAN direction. Counter type Frame Errored seconds Errored seconds Errored seconds Event Event Frame Page 2-58 Turin Networks Release OPS3.1.x

195 Chapter 4 Ethernet Performance Parameters Ethernet Port PM Ethernet Port PM The system provides the following performance monitoring parameters and counters for Gigabit Ethernet (GbE) and Fast Ethernet (10/100BaseTX) ports. Important: The table below contains common, as well as exclusive, PM (where noted) for: Traverse NGE (both NGE and NGE Plus), TE-100 Ethernet, and Traverse Legacy Ethernet. Note: Ethernet Port PM and Ethernet Service PM byte counts may differ for the following reasons: Ethernet Service PM byte counts do not include the 8-byte GBP header. VLAN tags may be added or stripped as packets traverse the Ethernet card. This results in different packet sizes when counted at the service interface than when counted at the Ethernet port interface. In Shelf View, click an Ethernet port, then click the Performance tab to view these parameters in the order given. Table 2-38 Ethernet Port PM Parameters Parameter (Exclusive Parameter Note) TX UNICAST 1 TX MULTICAST 1 TX BROADCAST TX FRAMES 1 TX PKT 64 (Traverse Legacy Ethernet only) TX PKT (Traverse Legacy Ethernet only) TX PKT (Traverse Legacy Ethernet only) TX PKT (Traverse Legacy Ethernet only) TX PKT (Traverse Legacy Ethernet only) TX PKT (Traverse Legacy Ethernet only) TX PKT > 1518 (Traverse Legacy Ethernet only) RX UNICAST 1 Definition The number of unicast frames transmitted with no errors. The number of multicast frames that are not broadcast, transmitted with no errors. The number of broadcast frames transmitted with no errors. The number of frames transmitted (unicast, multicast, and broadcast) with no errors. The number of transmitted 64-byte frames, including bad frames. The number of transmitted frames, 65 to 127 bytes in length, including bad frames. The number of transmitted frames, 128 to 255 bytes in length, including bad frames. The number of transmitted frames, 256 to 511 bytes in length, including bad frames. The number of transmitted frames, 512 to 1023 bytes in length, including bad frames. The number of transmitted frames, 1024 to 1518 bytes in length, including bad frames. The number of transmitted frames, greater than or equal to 1519 bytes in length, including bad frames. The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors. Release OPS3.1.x Turin Networks Page 2-59

196 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Ethernet Port PM Table 2-38 Ethernet Port PM Parameters (continued) RX MULTICAST 1 RX BROADCAST RX FRAMES 1 RX > MAX FRAME SIZE RX < 64 Parameter (Exclusive Parameter Note) RX PKT 64 (Not applicable to Traverse NGE) RX PKT (Not applicable to Traverse NGE) RX PKT (Not applicable to Traverse NGE) RX PKT (Not applicable to Traverse NGE) RX PKT (Not applicable to Traverse NGE) RX PKT (Not applicable to Traverse NGE) RX PKT > 1518 (Not applicable to Traverse NGE) RX NO DELIMITER (Traverse Legacy Ethernet only) RX DISCARDS 2,3,4 TX DISCARDS (Traverse NGE only) RX DELAY DISCARDS (TE-100 Ethernet only) RX MTU DISCARDS (Not applicable to TE-100 Ethernet) Definition The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors. The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors. The number of frames received (unicast, multicast, and broadcast) with no errors. The number of received frames that exceed the maximum valid packet length for the port. The number of frames received, less than 64 bytes in length, received with no errors. The number of received 64-byte frames, including bad frames. The number of received frames, 65 to 127 bytes in length, including bad frames. The number of received frames, 128 to 255 bytes in length, including bad frames. The number of received frames, 256 to 511 bytes in length, including bad frames. The number of received frames, 512 to 1023 bytes in length, including bad frames. The number of received frames, 1024 to 1518 bytes in length, including bad frames. The number of received frames, greater than or equal to 1519 bytes in length, including bad frames. The number of frames received without start of frame delimiter detection but with carrier assertion. The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol. The number of outbound frames discarded by this port due to aborted frames and underruns. Number of frames discarded by this interface due to excessive transit delay through the bridge. Number of frames discarded by this interface due to an excessive size. Page 2-60 Turin Networks Release OPS3.1.x

197 Chapter 4 Ethernet Performance Parameters Ethernet Port PM Table 2-38 Ethernet Port PM Parameters (continued) RX ALIGNMENT ERR (Traverse Legacy Ethernet only) RX FCS ERR 5 RX PAUSE TX PAUSE TX BYTES 6 TX BYTES BAD (Traverse Legacy Ethernet only) RX BYTES 2 Parameter (Exclusive Parameter Note) RX BYTES BAD (Traverse Legacy Ethernet only) TX SINGLE COLL (10/100BaseTX only) TX MULTIPLE COLL (10/100BaseTX only) TX DEFERRED FRAMES (10/100BaseTX only) TX LATE COLL (10/100BaseTX only) TX EXCESSIVE COLL (10/100BaseTX only) Definition Number of frames received which are not an integral number of octets and do not pass the FCS check. Number of frames received which are an integral number of octets and do not pass the FCS check. The number of received pause control frames. The number of transmitted pause control frames. The number of bytes transmitted in good frames. The number of bytes transmitted in bad frames. The number of bytes received in good frames. The number of bytes received in bad frames. The number of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. Also counted as a successful transmission. Half-duplex operation only. The number of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. Also counted as a successful transmission. Half-duplex operation only. The number of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. Does not include frames involved in collisions. Half-duplex operation only. The number of times that a collision is detected on a particular interface later than one slottime into the transmission of a packet. Half-duplex operation only. The number of frames for which transmission on a particular interface fails due to excessive collisions. Half-duplex operation only. 1 Traverse NGE does not include PAUSE frames. 2 Traverse NGE includes packets that are < 64 or > MTU with CRC errors. 3 Traverse NGE discards due to coding error or rate limiting. 4 TE-100 Ethernet includes packets < 64 wcrc errors, packets dropped due to lack of resources or rate limiting. Release OPS3.1.x Turin Networks Page 2-61

198 Node Operations and Maintenance Guide, Section 2: Performance Monitoring Ethernet Service Port PM 5 TE-100 Ethernet includes align errors as well. 6 Traverse NGE includes PAUSE frames. Ethernet Service Port PM The system provides the following performance monitoring parameters and counters for Traverse NGE (both NGE and NGE Plus) ports. In Shelf View, click an Ethernet port, then click the Performance tab to view these parameters in the order given. Table 2-39 Ethernet Service Port PM Parameters TX BYTES Parameter (Exclusive Parameter Note) TX PACKETS TX RED DISCARDS RX BYTES 2 RX PACKETS RX LOCAL DISCARDS RX HARDWARE PACKET DISCARDS Definition The number of bytes contained in packets queued for transmitted to this port for this service, including internal overhead per packet. The number of packets queued for transmission to this port for this service. The number of packets that were not queued for transmission to this port for this service because they were discarded due to Random Early Discard (RED). The number of bytes received on this port for this service, including internal overhead per packet. The number of packets received on this port for this service. The number of packets received on this port for this service, but discarded because the destination address has been learned on the ingress port. The number of packets dropped due to Spanning Tree port blocking. The number of packets received on this port for this service, but discarded due to an unclassifiable hardware error. Page 2-62 Turin Networks Release OPS3.1.x

199 SECTION 3SYSTEM MONITORING SECTION 3 EQUIPMENT LED STATUS SECTION 3 Contents Chapter 1 LEDs and Module Status Introduction PDAP LEDs Front Inlet Fan Tray Module LEDs Fan Tray Holder LEDs Traverse Module LEDs Power and Standby LED Indicators All Modules General Control Module (GCM) LED Indicators Electrical Module Port LED Indicators Optical Module Port LED Indicators GbE and Fast Ethernet Module Port LED Indicators List of Figures Figure 3-1 PDAP-2S LEDs Figure 3-2 PDAP-4S LEDs Figure 3-3 Front Inlet Fan Module with LEDs Figure 3-4 Fan Tray Holder with LEDs Figure 3-5 Module LEDs List of Tables Table 3-1 PDAP Table 3-2 Front Inlet Fan Module Table 3-3 Fan Tray Holder Table 3-4 Power and Active/Standby All Modules Table 3-5 Alarm Table 3-6 Timing Subsystem Table 3-7 Ethernet Link (OSS and Craft 10/100BaseT) Table 3-8 Electrical Module/Port Status Table 3-9 Optical Module/Port Status Table 3-10 GbE and Fast Ethernet Port Release OPS3.1.x Turin Networks Page i

200 Node Operations and Maintenance Guide, Section 3 Equipment LED Status Page ii Turin Networks Release OPS3.1.x

201 SECTION 3EQUIPMENT LED STATUS Chapter 1 LEDs and Module Status Introduction There are light emitting diodes (LEDs) on several pieces of Turin product family equipment to provide visual status. This chapter provides information on each of the LEDs and what they indicate: PDAP LEDs, page 3-2 Front Inlet Fan Tray Module LEDs, page 3-4 Fan Tray Holder LEDs, page 3-5 Traverse Module LEDs, page 3-6 Power and Standby LED Indicators All Modules, page 3-7 General Control Module (GCM) LED Indicators, page 3-8 Electrical Module Port LED Indicators, page 3-9 Optical Module Port LED Indicators, page 3-10 GbE and Fast Ethernet Module Port LED Indicators, page 3-10 Release OPS3.1.x Turin Networks Page 3-1

202 Node Operations and Maintenance Guide, Section 3: Equipment LED Status PDAP LEDs PDAP LEDs The locations of the Power Distribution and Alarm Panel (PDAP-2S, or PDAP-4S) LEDs are shown in the following drawings. Refer to Table 3-1 for information on how to interpret the PDAP LED indicators. GMT Fuse Block Power GMT Fuse Block Power Input Critical Minor Input Power A Major Power B Figure 3-1 PDAP-2S LEDs TPA Fuses A TPA Fuses B Input Power A GMT Fuse Input Power B Critical Major Minor Figure 3-2 PDAP-4S LEDs The LEDs in the following table apply to LEDs on the PDAP-2S and PDAP-4S. Table 3-1 PDAP LED RED GREEN AMBER OFF Critical Summary Alarm At least one critical alarm in the rack. N/A N/A No critical alarms for the entire rack GMT Fuse Block Power At least one fuse failure in GMT Fuse Block A or B. All fuses are good in GMT Fuse Block A or B. N/A No power Input Power N/A Power from Battery A or B input. N/A No power Major Summary Alarm At least one major alarm in the rack. N/A N/A No major alarms for the entire rack Page 3-2 Turin Networks Release OPS3.1.x

203 Chapter 1 LEDs and Module Status PDAP LEDs Table 3-1 PDAP (continued) LED RED GREEN AMBER OFF Minor Summary Alarm N/A N/A At least one minor alarm exists in the rack. No minor alarms for the entire rack TPA Fuse Power (PDAP-4S only) The TPA fuse has failed. N/A N/A TPA fuse is good Release OPS3.1.x Turin Networks Page 3-3

204 Node Operations and Maintenance Guide, Section 3: Equipment LED Status Front Inlet Fan Tray Module LEDs Front Inlet Fan Tray Module LEDs The location of the front inlet fan tray module LEDs are shown in the following drawing. Refer to Table 3-2 for information on how to interpret LED indicators. Important: This topic refers to the LEDs on the fan module of the redesigned front inlet fan tray with integrated air ramp unit. Refer to Fan Tray Holder LEDs, page 3-5 if you are viewing an original fan tray unit with a separate air ramp unit. Traverse 1600 FIFT Traverse 600 FIFT Fan Failure (red) Power (green) Fan Failure (red) Figure 3-3 Front Inlet Fan Module with LEDs Power (green) Table 3-2 Front Inlet Fan Module LED RED GREEN OFF Power N/A Power on. No power. Fan Failure At least one fan module, fan tray EEPROM or thermistor has failed. Check and replace the fan tray and/or module. Lost communication with GCM. Reseat the fan tray. Over temperature condition on the GCM. Check that the room temperature is not abnormally high or replace the front inlet fan tray air filter. N/A All fans are working. Communication with GCM is good. All temperature indications are good. Page 3-4 Turin Networks Release OPS3.1.x

205 Chapter 1 LEDs and Module Status Fan Tray Holder LEDs Fan Tray Holder LEDs This topic applies to the original fan tray unit with separate air ramp unit (pre-release 1.4). Refer to Front Inlet Fan Tray Module LEDs, page 3-4 if you are viewing the fan module of the redesigned front inlet fan tray with integrated air ramp unit. The locations of the fan tray holder LEDs are shown in the following drawing. Refer to Table 3-2 for information on how to interpret LED indicators. Fan Failure (red) Power (green) Figure 3-4 Fan Tray Holder with LEDs Table 3-3 Fan Tray Holder LED RED GREEN OFF Power N/A Power on. No power. Fan Failure At least one fan module, fan tray EEPROM or thermistor has failed. Check and replace the fan tray. Lost communication with GCM. Reseat the fan tray. Over temperature condition on the GCM. Check that the room temperature is not abnormally high or replace the fan tray air filter. N/A All fans are working. Communication with GCM is good. All temperature indications are good. Release OPS3.1.x Turin Networks Page 3-5

206 Node Operations and Maintenance Guide, Section 3: Equipment LED Status Traverse Module LEDs Traverse Module LEDs The locations of common and specific module LEDs is shown in the following graphic. Refer to the tables that follow in the rest of the chapter for LED information: PWR (Power) ACTV/ STNBY (Active/Standby) DS1, DS3/E3, E1, OC-N/STM-N and ETH Port Indicators Alarms: CRITICAL/MAJOR MINOR ACO ON ACO Optical Port Timing: LOCKED/ UNLOCKED FREE RUN/ HOLDOVER ETHERNET LINK OSS and Craft 10/100BaseT Ethernet Interface (RJ-45) RS-232 Interface (DB-9) DS1 DS3/E3 E1 OC-N/ STM-N VT Switch Ethernet EGCM Figure 3-5 Module LEDs Page 3-6 Turin Networks Release OPS3.1.x

207 Chapter 1 LEDs and Module Status Power and Standby LED Indicators All Modules Power and Standby LED Indicators All Modules The LEDs in the following tables apply to all modules. Table 3-4 Power and Active/Standby All Modules LED RED Amber GREEN OFF Flashing Solid Flashing Solid Flashing Solid Power Initialization and diagnosis is underway but not complete Hardware failure detected; replace the module N/A N/A N/A Initialization is complete and the module is operational. No power Active/ Standby N/A N/A The module is unlocked and in Standby mode. 1 Synchronization with the Active module is not complete. The module is unlocked. The module type does not match the provisioned module type or the module is placed in an invalid slot. 2 The module is unlocked and in Standby mode. Synchronization with the Active module is complete. The Active module is unlocked and operational. The module is locked or initialization is not complete. 1 Does not apply to GbE or OC-N modules. 2 For the Traverse platform, refer to Appendix A Module Placement Planning and Guidelines, page 12-1 for valid module placement guidelines. Release OPS3.1.x Turin Networks Page 3-7

208 Node Operations and Maintenance Guide, Section 3: Equipment LED Status General Control Module (GCM) LED Indicators General Control Module (GCM) LED Indicators The LEDs in the following tables apply to GCM modules only. If you have placed GCMs with integrated (OC-12/STM-4 or OC-48/STM-16) optics, also refer to Table 3-9 Optical Module/Port Status. Table 3-5 Alarm LED RED Solid AMBER Solid OFF Critical/ Major One or more critical or major alarms are active. Indicates a service-affecting event(s) and requires immediate action. N/A No critical or major alarms Minor N/A One or more minor alarms are active. Indicates a non-service-affecting event(s). Take action to prevent a more serious problem. No minor alarms Alarm Cutoff (ACO) N/A The audible alarm is cut off (silenced). The audible alarm is not cut off (not silenced). Table 3-6 Timing Subsystem LED RED GREEN AMBER Solid Flashing Solid Flashing Solid OFF Locked/ Unlocked Selected timing input reference is lost. Lost-phase mode. LED flashes at 500ms on/off rate. Locked to a timing input reference 1 N/A N/A Initialization is not complete or the GCM is in free-run mode. Free-run/ Hold-over N/A Tracking a timing reference signal, but not completely out of free-run mode. LED flashes at 500ms on/off rate. Free-run mode 2 Transitioning out of hold-over mode, but not Locked. LED flashes at 500ms on/off rate. Hold-over mode. 3 Initialization is not complete or the GCM is locked to a timing input reference 1. 1 Timing input references are: T1, Composite Clock, or OC-N line timing reference. 2 A valid timing input reference is not available and the GCM is unable to acquire an estimate for hold-over, or the GCM is configured for free-run mode. 3 The external timing reference is degraded or lost and no other input references are available for system synchronization. The GCM was locked to its selected timing input reference and established a valid frequency estimate before going into hold-over mode. Page 3-8 Turin Networks Release OPS3.1.x

209 Chapter 1 LEDs and Module Status Electrical Module Port LED Indicators : Table 3-7 Ethernet Link (OSS and Craft 10/100BaseT) LED RED GREEN OFF Flashing Solid Flashing Solid Ethernet Port Running diagnostics or in loopback mode. Port is unlocked, but there is no link integrity/ signal. Transmitting or receiving frames. Operational, the link is active. Port is locked. Electrical Module Port LED Indicators The LEDs in the following table apply to electrical (DS1, DS3, E1, E3, and VT/TU Switch) modules only. Table 3-8 Electrical Module/Port Status RED GREEN OFF LED Flashing Solid Flashing Solid Ports Running diagnostics or in loopback mode. Unlocked and a port failure is detected (LOS, LOF/OOF, AIS, RFI) N/A Unlocked and receiving a valid signal. Module initialization is not complete, the module is in Standby mode, or the port is locked. Release OPS3.1.x Turin Networks Page 3-9

210 Node Operations and Maintenance Guide, Section 3: Equipment LED Status Optical Module Port LED Indicators Optical Module Port LED Indicators The LEDs in the following table apply to optical modules (OC-N/STM-N) and to the optical ports (OC-12/STM-4 or OC-48/STM-16) on the GCM with integrated optics modules. Table 3-9 Optical Module/Port Status RED GREEN OFF LED Flashing Solid Flashing Solid Ports Running diagnostics or in loopback mode Unlocked and a port failure is detected (LOS, LOF/OOF, AIS, RFI) Unlocked and receiving a valid signal; in Standby mode for a 1+1 facility protection group Unlocked and receiving a valid signal Module initialization is not complete or the port is locked GbE and Fast Ethernet Module Port LED Indicators The LEDs in the following table apply to the optical GbE and FE (100Base FX and 10/100BaseTX) modules. Table 3-10 GbE and Fast Ethernet Port LED RED GREEN OFF Flashing Solid Flashing Solid Ethernet Port Running diagnostics or in loopback mode Unlocked no link integrity/ signal detected Unlocked and transmitting or receiving frames Unlocked and operational. The Ethernet link is active. Module initialization is not complete or the port is locked Page 3-10 Turin Networks Release OPS3.1.x

211 SECTION 4 DIAGNOSTICS SECTION 4 Contents Chapter 1 Diagnostics Overview Introduction Symptoms and Recommended Actions Chapter 2 Traverse Transmit and Receive Signal Levels Introduction Traverse Optical Interface Specifications Fast Ethernet GbE OC-3/STM OC-12/STM OC-48/STM OC-192/STM Chapter 3 TraverseEdge 100 Transmit and Receive Signal Levels Introduction TE-100 Optical Interface Specifications Chapter 4 Loopback Tests Introduction DS1 and DS3 Loopback Tests DS1 and DS3 Facility Payload Loopback DS1 and DS3 Terminal Loopback EC-3 and STM-1E Loopback Tests EC-3and STM-1E Facility Payload Loopback EC-3 and STM-1E Terminal Loopback E1 and E3 Loopback Tests E1 and E3 Facility Payload Loopback E1 and E3 Terminal Loopback Ethernet Loopback Test Ethernet Facility Loopback Ethernet Terminal Loopback SONET/SDH Loopback Tests SONET/SDH Facility Loopback SONET/SDH Terminal Loopback Performing Loopback Tests Equipment States Release OPS3.1.x Turin Networks Page i

212 Node Operations and Maintenance Guide, Section 4 Diagnostics Chapter 5 Other Diagnostics Introduction Power On Self Test Alarm Cut-Off LED Lamp Test List of Figures Figure 4-1 DS-x Facility Payload Loopback Figure 4-2 DS-x Terminal Loopback Figure 4-3 EC-3/STM-1E Facility Payload Loopback Figure 4-4 EC-3/STM-1E Terminal Loopback Figure 4-5 E-x Facility Payload Loopback Figure 4-6 E-x Terminal Loopback Figure 4-7 Ethernet Facility Payload Loopback Figure 4-8 Ethernet Terminal Loopback Figure 4-9 SONET/SDH Facility Payload Loopback Figure 4-10 SONET/SDH Terminal Loopback Figure 4-11 Setting Up a Loopback Test Figure 4-12 Equipment States List of Tables Table 4-1 Symptoms and Recommended Actions Table 4-2 Optical Interface Specification Summary Table Table 4-3 SONET, STM, and GbE Optics Table 4-4 Performing Loopback Tests Page ii Turin Networks Release OPS3.1.x

213 SECTION 4DIAGNOSTICS Chapter 1 Diagnostics Overview Introduction The diagnostics section provides various diagnostic tips and tools to assist you isolate and find resolution to abnormal conditions observed while monitoring the Traverse system. This chapter includes the following topics: Symptoms and Recommended Actions, page 4-2 Chapter 2 Traverse Transmit and Receive Signal Levels, page 4-3 Chapter 3 TraverseEdge 100 Transmit and Receive Signal Levels, page 4-7 Chapter 4 Loopback Tests, page 4-9 Chapter 5 Other Diagnostics, page 4-21 Release OPS3.1.x Turin Networks Page 4-1

214 Page 4-2 Turin Networks Release OPS3.1.x Symptoms and Recommended Actions During normal operation of the Traverse system, various symptoms (non-alarm/event conditions) may arise that require attention by network operations. Table 4-1 Symptoms and Recommended Actions below provides a description of observable symptoms, their probable causes, and any recommended actions to take to resolve the problem. Symptoms are listed in the following table in ascending, alphabetical order. Each symptom entry contains the following information: Suspected system area Symptom description Suspected domain (network) or node (module or port) scope Probable cause Recommended action based upon symptom observation Table 4-1 Symptoms and Recommended Actions System Area Environmental Alarms OC-192 Module Symptom Description Scope Probable Cause Recommended Action Environmental Alarm input or output is incorrect. Upon installation into the shelf slot, the (R1.3 and above) enhanced OC-192 module does not initialize or come operational. The module LEDs continue flashing. Node Incorrect alarm cable connections Environmental Alarm Module (EAM) failure Node OC-192 module was installed in a node with pre-release 1.3 software. Incorrect alarm cable connections. See Traverse Installation and Commissioning Guide, Section 1 Fault Management, Chapter 2 Alarms, Events, and Recommended Actions, page 1-19 Replace EAM. See Section 6 Routine Maintenance, Chapter 1 Routine Maintenance, Environmental Alarm Module Replacement (Traverse only), page 6-20 Check the current software version. Perform software upgrade as necessary for software compatibility. See Section 7 Software Upgrades, Chapter 1 Release TR2.1.x Traverse Software Upgrade, page 7-1 Node Operations and Maintenance Guide, Section 4: Diagnostics Symptoms and Recommended Actions

215 SECTION 4DIAGNOSTICS Chapter 2 Traverse Transmit and Receive Signal Levels Introduction This chapter provides optical parameter specifications to assist you in handling a Loss of Signal (LOS) condition on a Traverse optical module. Release OPS3.1.x Turin Networks Page 4-3

216 Page 4-4 Turin Networks Release OPS3.1.x Traverse Optical Interface Specifications The table below provides a summary of all optical interface specifications. WARNING! The optical receiver of the OC-N/STM-N Long Reach modules can be damaged permanently if overloaded. Do not connect the optical transmitter directly to the optical receiver, unless with proper attenuation. A minimum of 10 db attenuation is required for long reach optics. Table 4-2 Optical Interface Specification Summary Table Optical Interface Module Optic Type Typical Nominal TX Wavelength TX Wavelength Range RX Wavelength Range Transmitter Output Power 1 Receiver Signal 1,2 Guaranteed Link Budget 1,3 Maximum Reach 4 (nm) (nm) (nm) (dbm) (dbm) (db) (mi) (km) Fast Ethernet 100BaseFX (GbE/Fast Ethernet combo) to to to to GbE GbE SX to to to to GbE LX to to to to GbE CWDM 1470 to 1610 (8 channels at 20 nm intervals) 1260 to to 4-18 to OC-3/STM-1 OC-3 IR1/STM-1 SH to to to to OC-3 LR2/STM-1 LH to to to 0-32 to OC-12/STM-4 OC-12 IR1/STM-4 SH to to to to OC-12 LR2/STM-4 LH to to to 2-26 to OC-48/STM-16 OC-48 SR1/STM-16 SH to to to to OC-48 IR1/STM-16 SH to to to 0-17 to OC-48 LR1/STM-16 LH to to to 3-26 to OC-48 LR2/STM-16 LH to to to 3-25 to OC-48 LR2/STM-16 LH CWDM 1470 to 1610 (8 channels at 20 nm intervals) 1260 to to 5-25 to OC-48 ELR/STM-16 LH ITU DWDM to (42 channels) 1260 to to 4-26 to OC-48 VR2/STM-16 VLH to to to to Node Operations and Maintenance Guide, Section 4: Diagnostics Traverse Optical Interface Specifications

217 Release OPS3.1.x Turin Networks Page 4-5 Table 4-2 Optical Interface Specification Summary Table (continued) Optical Interface OC-192/STM-64 OC-192 SR1/STM-64 SH to to to to OC-192 IR2/STM-64 SH to to to 2-11 to OC-192 LR2/STM-64 LH to to to 7-20 to OC-192 LR/STM-64 LH ITU DWDM to (42 channels) 1290 to to 7-20 to OC-192 ELR/STM-64 LH ITU DWDM to (42 channels) 1290 to to 7-23 to These values account for the connector loss from connection to the optical interface and the worst case optical path penalty PRBS, BER=10-10 Module Optic Type 3 Measured from fiber patch panel to fiber patch panel. Includes 1.0 db penalty for loss from fiber line card to patch panel. 4 Assumes a fiber loss only of 0.25 db/km. Typical Nominal TX Wavelength TX Wavelength Range RX Wavelength Range Transmitter Output Power 1 Receiver Signal 1,2 Guaranteed Link Budget 1,3 Maximum Reach 4 (nm) (nm) (nm) (dbm) (dbm) (db) (mi) (km) 5 GCM with integrated optics are also available. See Traverse Product Overview Guide, Section 3 Module Descriptions, Chapter 1 General Control Modules, page 3-1 for more information. Chapter 2 Traverse Transmit and Receive Signal Levels Traverse Optical Interface Specifications

218 Node Operations and Maintenance Guide, Section 4: Diagnostics Traverse Optical Interface Specifications Page 4-6 Turin Networks Release OPS3.1.x

219 SECTION 4DIAGNOSTICS Chapter 3 TraverseEdge 100 Transmit and Receive Signal Levels Introduction This chapter provides optical parameter specifications to assist you in handling a Loss of Signal (LOS) condition on a TraverseEdge 100 optical port. Release OPS3.1.x Turin Networks Page 4-7

220 Page 4-8 Turin Networks Release OPS3.1.x TE-100 Optical Interface Specifications The table below provides a summary of all optical interface specifications. This table represents data for Turin-approved SFPs. Additional SFPs may now be available; contact your local Turin Sales representative. Table 4-3 SONET, STM, and GbE Optics SONET Application STM WARNING! The optical receiver of the OC-N long-reach optics can be damaged permanently if overloaded. Do not connect the optical transmitter directly to the optical receiver without proper attenuation. A minimum of 10 db attenuation is required for long reach optics. Important: Only use SFPs approved by Turin or equipment damage may occur, thus voiding any TE-100 warranty. Approx Distance (km) Tx Power Range (dbm) Rx Power Range (dbm) Dispersion Penalty (db) Attenuation Range Extinction Ratio (db) Tx Wavelength Range (nm) Rx Wavelength Range (nm) Dispersion Tolerance (ps/nm) Temperature Range (degc) OC-3 IR-1 STM-1 S to to to to to to 85 OC-3 LR-2 STM-1 L to 0-33 to to to to to 70 OC-12 IR-1 STM-4 S to to to to to to 85 OC-12 LR-2 STM-4 L to 2-27 to to to to to 70 OC-48 SR-1 STM-16 I to to to to to to 70 OC-48 IR-1 STM-16 S to 0-18 to to to to to 70 OC-48 LR-1 STM-16 L to 3-27 to to to to to 70 OC-48 LR-2 STM-16 L to 3-26 to to to to to 70 OC-48 LR-2 STM-16 L to 5-26 to to to to to 70 OC-48 ELR STM to 4-27 to to to to to Base SX 1000Base SX to to to to to to Base LX 1000Base LX 10-9 to to to to to to Base ZX 1000Base ZX 80 0 to 4-22 to to to to to 70 Notes on the table: All TE-100 optical ports use SFP optical modules. The RX power (min) and Attenuation (max) values assume the worst case optical path penalty (dispersion). Not all vendors specify RX wavelength range. It is likely that the module will operate over a larger range than specified. Node Operations and Maintenance Guide, Section 4: Diagnostics TE-100 Optical Interface Specifications

221 SECTION 4DIAGNOSTICS Chapter 4 Loopback Tests Introduction The TransNav Management System provides diagnostic loopback testing for troubleshooting ports and spans. The system supports the following loopback tests: Facility To troubleshoot the line interface unit of a module, the backplane, or the cabling Terminal To troubleshoot a circuit path and loop back to the module WARNING! Loopback tests interrupt traffic flow; do not perform them on nodes providing service. Important: Facility and terminal loopbacks cannot be performed on ports, part of a BLSR/MS-SP Ring, or on a 1+1 APS/1+1 MSP protection group. This chapter contains the following module-specific loopback tests: DS1 and DS3 Loopback Tests, page 4-10 EC-3 and STM-1E Loopback Tests, page 4-11 E1 and E3 Loopback Tests, page 4-12 Ethernet Loopback Test, page 4-13 SONET/SDH Loopback Tests, page 4-15 See Performing Loopback Tests, page 4-16 for a step-by-step procedure on how to perform loopback tests. See Equipment States, page 4-17 for a discussion of the Traverse operational and administrative states. Release OPS3.1.x Turin Networks Page 4-9

222 Node Operations and Maintenance Guide, Section 4: Diagnostics DS1 and DS3 Loopback Tests DS1 and DS3 Loopback Tests DS1 and DS3 Facility Payload Loopback Each node supports a facility payload loopback for each incoming received DS-x signal. The facility must first be taken out of service prior to initiating the loopback test. The facility payload loopback connects the incoming received DS-x signal immediately to the associated return transmitter, as shown in Figure 4-1. During this loopback, AIS is inserted and sent to the far end. Service between ports DS-x module Trunk module Test Set LIU AIS LIU DS-x facility under loopback test Figure 4-1 DS-x Facility Payload Loopback DS1 and DS3 Terminal Loopback The node supports terminal loopback for each DS-x signal. The facility must first be taken out of service prior to initiating the loopback test. For DS1 and DS3 terminal loopback, the signal is looped back toward the SONET/SDH system just before being transmitted toward the DS-x line, as shown in Figure 4-2. This loopback is used to verify the receiver associated with the interface and the integrity of the transmitted DS-x signal. Service set up between ports DS-x module Trunk module LIU LIU Test Set DS-x facility under loopback test Figure 4-2 DS-x Terminal Loopback Page 4-10 Turin Networks Release OPS3.1.x

223 Chapter 4 Loopback Tests EC-3 and STM-1E Loopback Tests EC-3 and STM-1E Loopback Tests EC-3and STM-1E Facility Payload Loopback Each node supports a facility payload loopback for each incoming received signal. The facility must first be taken out of service prior to initiating the loopback test. The facility payload loopback connects the incoming received signal immediately to the associated return transmitter, as shown in Figure 4-1. During this loopback, AIS is inserted and sent to the far end. Service between ports EC-3/STM-1E DS-x module Trunk module Test Set LIU AIS LIU DS-x facility under loopback test Figure 4-3 EC-3/STM-1E Facility Payload Loopback EC-3 and STM-1E Terminal Loopback The node supports terminal loopback for each signal. The facility must first be taken out of service prior to initiating the loopback test. For terminal loopback, the signal is looped back toward the SONET/SDH system just before being transmitted toward the line, as shown in Figure 4-2. This loopback is used to verify the receiver associated with the interface and the integrity of the transmitted signal. Service set up between ports EC-3/STM-1E DS-x module Trunk module LIU LIU Test Set DS-x facility under loopback test Figure 4-4 EC-3/STM-1E Terminal Loopback Release OPS3.1.x Turin Networks Page 4-11

224 Node Operations and Maintenance Guide, Section 4: Diagnostics E1 and E3 Loopback Tests E1 and E3 Loopback Tests E1 and E3 Facility Payload Loopback The node supports a facility payload loopback for each incoming received E-x signal. The facility must first be taken out of service prior to initiating the loopback test. The facility payload loopback connects the incoming received E-x signal immediately to the associated return transmitter, as shown in Figure 4-1. During this loopback, AIS is inserted and sent to the far end. Service between ports E-x module Trunk module Test Set LIU AIS LIU E-x facility under loopback test Figure 4-5 E-x Facility Payload Loopback E1 and E3 Terminal Loopback The node supports terminal loopback for each E-x signal. The facility must first be taken out of service prior to initiating the loopback test. For E1 and E3 terminal loopback, the signal is looped back toward the SONET/SDH system just before being transmitted toward the E-x line, as shown in Figure 4-2. This loopback is used to verify the receiver associated with the interface and the integrity of the transmitted E-x signal. Service set up between ports E-x module Trunk module LIU LIU Test Set E-x facility under loopback test Figure 4-6 E-x Terminal Loopback Page 4-12 Turin Networks Release OPS3.1.x

225 Chapter 4 Loopback Tests Ethernet Loopback Test Ethernet Loopback Test Ethernet Facility Loopback The node supports a facility payload loopback for next-generation Ethernet interfaces. All packets that the Ethernet module receives from a CPE port are transmitted back on the same CPE port. Service providers can use this to check the local cabling from CPE device to the node. Facility loopback does not affect traffic flow on any other Ethernet port. If an Ethernet port is in an activated Ethernet service, the system prohibits facility loopback. If facility loopback is active, the system prohibits the activation of any Ethernet service. Important: When facility loopback is on for the next-generation Ethernet port, and when no other Ethernet ports on this module are sending or receiving frames, then the system transmits back to the loopback port all frames that it receives from that port, with the likely exception of PAUSE frames and errored frames. The facility payload loopback connects the incoming received signal immediately to the associated return transmitter, as shown in Figure 4-7. The facility loopback is in effect across module reboot. Figure 4-7 Ethernet Facility Payload Loopback Ethernet Terminal Loopback The node supports terminal loopback for next-generation Ethernet interfaces. Ethernet terminal loopback uses the forwarding relationship established by an Ethernet service to loop back packets to their sources, instead of transmitting them out the looped-back facility. This function requires the facility be in use by one or more activated Ethernet services that use point-to-point forwarding. (i.e., Line services). Release OPS3.1.x Turin Networks Page 4-13

226 Node Operations and Maintenance Guide, Section 4: Diagnostics Ethernet Loopback Test For Ethernet terminal loopback, the signal is looped back toward the SONET/SDH system just before being transmitted toward the Ethernet interface. Figure 4-8 Ethernet Terminal Loopback Page 4-14 Turin Networks Release OPS3.1.x

227 Chapter 4 Loopback Tests SONET/SDH Loopback Tests SONET/SDH Loopback Tests SONET/SDH Facility Loopback The node supports a facility payload loopback for each OC-N/STM-N facility (including the OC-12/STM-4 and OC-48/STM-16 facility on the Traverse GCM). The facility must first be taken out of service prior to initiating the loopback test. The facility payload loopback connects the incoming received SONET/SDH signal immediately to the associated return transmitter following the optical-to-electrical conversion (before scrambling), as shown in Figure 4-9. During this loopback, AIS is inserted and sent to the far end. Service between ports STS-N OC-N module OC-N module STS-N Test Set LIU AIS LIU SONET facility under loopback test Figure 4-9 SONET/SDH Facility Payload Loopback SONET/SDH Terminal Loopback The node supports terminal loopback for each OC-N/STM-N facility (including the OC-12/STM-4 and OC-48/STM-16 facility on the Traverse GCM). The facility must first be taken out of service prior to initiating the loopback test. For SONET/SDH terminal loopback, the signal is looped back toward the SONET/SDH system by connecting the outgoing signal immediately before the electrical-to-optical conversion (after scrambling), as shown in Figure Terminal loopback is used to verify the integrity of the electronics associated with the framer or the transmitted signal. Service set up between ports OC-N/STM-N module OC-N/STM-N module LIU LIU Test Set SONET/SDH facility under loopback test Figure 4-10 SONET/SDH Terminal Loopback Release OPS3.1.x Turin Networks Page 4-15

228 Node Operations and Maintenance Guide, Section 4: Diagnostics Performing Loopback Tests Performing Loopback Tests Before performing loopback testing, the port s administrative state must first be changed to Unlocked. Important: Loopback tests interrupt data flow; do not perform them on a port providing service. Use the vendor s procedures for setting up your test equipment. Then follow the procedure below to perform loopback tests on a port. For instructions on performing loopback tests on a TransAccess 100 Mux, see TransNav Management System GUI Guide, Section 8 Maintenance and Testing. Note: The loopback state or port lock/unlock state is be restored after a node database restore operation is performed. Instead, the system uses the current state of the port to override what was stored in the node database. Table 4-4 Performing Loopback Tests Step Procedure 1 In the GUI, display the Shelf View of the node on which you will perform loopback tests. If you are currently in Map View, double-click the node to switch to the Shelf View. 2 Select a port on the appropriate module. 3 Click the Config tab. 4 To unlock a port that is currently locked, click the Locked icon in the lower left corner to display the Unlocked icon, then click Apply. 5 An OC-N/STM-N port? Yes. Disable the Config tab Control Data parameter. No. Go to the next step. 6 Click Apply. 7 Click the Diagnostic tab. Page 4-16 Turin Networks Release OPS3.1.x

229 Chapter 4 Loopback Tests Equipment States Table 4-4 Performing Loopback Tests (continued) Step Procedure 8 From the Loopback drop-down list, select one of the following types of loopback tests to run: Facility: Troubleshoot the line interface unit (LIU) of a module, the backplane, and the cable. Terminal: Troubleshoot a circuit path and loop back from the module. Note 1: Facility loopback tests are not available for Legacy Ethernet modules. Note 2: For the Legacy Ethernet modules only, after a card reboot, previously active terminal loopbacks are not reactivated. Figure 4-11 Setting Up a Loopback Test 9 For DS3/EC-1 ports only, select the Test Signal Type: (Planned for future release.) Clear (default) PRBS (Pseudo random bit sequence): PRBS Fixed-24Bit: Repeating 24-bit pattern ( ) 10 Click Apply to run the loopback test. If the loopback test fails, there is a problem with the signal path. Corrective action should be taken. 11 After receiving feedback on the test equipment about the success or failure of the loopback test, clear the loopback test. Select Clear on the Loopback status drop-down list, then click Apply. 12 The Performing Loopback Tests procedure is complete. Equipment States Release OPS3.1.x Turin Networks Page 4-17

230 Node Operations and Maintenance Guide, Section 4: Diagnostics Equipment States Icons in the bottom left-hand corner of the Config tab indicate the state of the module or port. Equipped state Operational state Administrative state Figure 4-12 Equipment States Equipped State: Displays one of the following: Equipped: The equipped state of the module or port is Equipped. The equipment is present in the system. Non-Equipped: The equipped state of the module or port is Non-Equipped. The equipment is not present in the system. Operational State: Displays one of the following: Enabled: The administrative state of the module or port is Unlocked. Disabled: The administrative state of the module or port is Locked. Administrative State: Click the icon until one of the following is displayed: Lock (default for ports): Do not allow the module or port to operate. Changes the operational state to Disabled. Initiates protection switching, if applicable. Unlock (default for modules): Allow the module or port to operate. Page 4-18 Turin Networks Release OPS3.1.x

231 Chapter 4 Loopback Tests Equipment States Release OPS3.1.x Turin Networks Page 4-19

232 Node Operations and Maintenance Guide, Section 4: Diagnostics Equipment States Page 4-20 Turin Networks Release OPS3.1.x

233 SECTION 4DIAGNOSTICS Chapter 5 Other Diagnostics Introduction Power On Self Test Alarm Cut-Off LED Lamp Test This chapter provides other general diagnostics: Power On Self Test, page 4-21 Alarm Cut-Off, page 4-21 LED Lamp Test, page 4-21 The Traverse and TE-100 system runs the Power On Self Test (POST) diagnostic test sequence on the Traverse general control module (GCM) and TE-100 System module at system startup, respectively. The POST determines whether all system components are working properly and takes approximately one minute to run, during which time the power LED displays solid red. The POST runs on both the working and protection modules Any and all POST failures cause a fail-over The POST invokes LED activity for test progress, and pass and fail notification For a complete description of the LEDs in the system, see Chapter 1 LEDs and Module Status, page 3-1. The Alarm Cut-Off (ACO) button on the front of the Traverse GCM and TE-100 System module causes the audible sound for major and critical alarms to silence or re-active. Press the ACO button on the active module to silence the audible alarm and have the ACO LED turn and remain amber. If a subsequent major or critical alarm is raised, then the audible sound and matching LED turn on. Upon resolution of the condition or the operator presses (toggles) the button again, the LED turns off, and the ACO button relay is reset for normal operation. The ACO button also serves as a diagnostic LED lamp test button. Press and hold the ACO button for greater than 10 seconds to activate or cancel the test. Upon activation, all: Traverse shelf module LEDs light sequentially from left to right, through all their individual valid colors, and eventually go solid green. Upon cancellation, all LEDs return to normal behavior. TE-100 shelf module LEDs light in unison through all their individual valid colors (green, red, and amber). Upon cancellation, all LEDs return to normal behavior. Release OPS3.1.x Turin Networks Page 4-21

234 Node Operations and Maintenance Guide, Section 4: Diagnostics LED Lamp Test Page 4-22 Turin Networks Release OPS3.1.x

235 SECTION 5 TEST ACCESS SECTION 5 Contents Chapter 1 Traverse Test Access Introduction Local Test Access Remote Test Access Mode Configurations Access Identifier (AID) Monitor Configurations Split Configurations Feature Set Options Configuration Management Test Access Mode Examples Monitor Test Access Example (MONE) Per Side Split Test Access Example (SPLTE) Series Split Test Access Example (SPLTA) Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface Introduction Traverse Platform and Spirent BRTU Interoperability Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface List of Figures Figure 5-1 Local Traverse DCS3/1 Test Access Figure 5-2 Remote Traverse DCS3/1 Test Access Figure 5-3 TransNav GUI AID Format Example Figure 5-4 Monitor Configurations Figure 5-5 Split Configurations Figure 5-6 Monitor Test Access Configuration MONE Figure 5-7 Example VT TAP (Single FAD) Figure 5-8 MONE TAC Example Figure 5-9 Service with MONE TAC Example Figure 5-10 Per Side Split Test Access Configuration SPLTE Figure 5-11 Example VT TAP (Single FAD) Figure 5-12 SPLTE TAC Example Figure 5-13 Service with SPLTE TAC Example Figure 5-14 Series Split Test Access Configuration SPLTA Figure 5-15 Example DS1 TAP (Single FAD) Release OPS3.1.x Turin Networks Page i

236 Node Operations and Maintenance Guide, Section 5 Test Access Figure 5-16 SPLTA TAC Example Figure 5-17 Service with SPLTA TAC Example Figure 5-18 Turin TransNav GUI and Spirent BRTU REACT OSS Example List of Tables Table 5-1 Test Access Mode vs. Service Compatibility Matrix Table 5-2 Monitor Test Access Configuration MONE Table 5-3 Per Side Split Test Access Configuration SPLTE Table 5-4 Series Split Test Access Configuration SPLTA Page ii Turin Networks Release OPS3.1.x

237 SECTION 5TEST ACCESS Chapter 1 Traverse Test Access Introduction (SONET network only) Traverse Test Access on digital cross-connect (DCS3/1) systems and Add-drop Multiplexer (ADM) systems provides for non-intrusive monitoring and intrusive split testing of DS3/STS-1 and DS1/VT1.5 digital signals. 1 Traverse test access is compliant with the following Telcordia standards: GR-834-CORE, Network Maintenance: Access and Testing, GR-1402-CORE, Network Maintenance: Access Testing - DS3 HCDS TSC/RTU and DTAU Functional Requirement, and GR-818 Network Maintenance: Access and Testing - Generic Test Architecture. Interoperability with the Spirent Communication s network tester, Broadband Remote Test Unit (BRTU) with REACT remote test Operations Support System (OSS), provides the Traverse platform with integrated test access functionality, enabling carriers to test and monitor any DS1/VT1.5 or DS3/STS-1 service provisioned on the Traverse switch fabric. See Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface, page For parameter descriptions, see the TransNav Management System GUI Guide, Section 8 Maintenance and Testing, Chapter 5 Test Access, page This chapter includes the following test access information. Local Test Access, page 5-2 Remote Test Access, page 5-3 Mode Configurations, page 5-4 Access Identifier (AID), page 5-5 Feature Set Options, page 5-8 Configuration Management, page 5-9 Test Access Mode Examples, page (SDH network only) Test access is planned for a future release. Release OPS3.1.x Turin Networks Page 5-1

238 Node Operations and Maintenance Guide, Section 5: Test Access Local Test Access Local Test Access The digital signal for monitoring or testing drops at a logical, pre-configured test access point (TAP) as shown in the figure below. The user pre-configures the TAP for use in establishing a test access cross-connect (TAC) to a unidirectional service, a bidirectional service, or an unmapped termination point (TP). The TAP is given a unique identifier and is configured as either a single facility access digroup (FAD) or a dual FAD (DFAD) using one or two service endpoint access identifiers (AIDs), respectively. A DFAD is just two FADs together in one TAP. DFADs are only used in test access mode configurations that require two FADs. Refer to Mode Configurations, page 5-4 for a description of all the test access mode configurations. For service endpoint information, refer to Access Identifier (AID), page 5-5. The physical connection for a TAP is a standard cable connection between a DS3 or DS1 port and the remote test unit (RTU), typically via a patch panel. The user establishes TACs through the node-level control link or TransNav management system interface. With the test access cross-connects in service, the user can monitor or perform tests using the test system controller (TSC) user interface to the RTU. The Traverse system automatically disconnects all in-service TACs and restores all the original services upon reboot or communication loss with the RTU. TransNav Management System (GUI, CLI, or TL1) Test System Controller (TSC) DCS3/1 Termination Point (TP) of the Circuit Under Test Node-level Control Link (CLI or TL1) Test Access Point (TAP) (e.g., DS1 port) Patch Panel Remote Test Unit (RTU) Figure 5-1 Local Traverse DCS3/1 Test Access Page 5-2 Turin Networks Release OPS3.1.x

239 Chapter 1 Traverse Test Access Remote Test Access Remote Test Access Remote test access provides for the configuration of and access to TAPs at a remote location or network element as shown in the figure below. The remote TAP definition is a logical VT1.5 termination on an OC-N port. The DS1s for test access may be physically located at a remote site and/or in an access network element. The remote test access network configuration is shown in the figure below. At the top of the figure is the Traverse DCS3/1. A static STS-1 or VT1.5 path is created across the service provider network from the remote multiplexer to the Traverse DCS3/1. A remote test unit (RTU) is connected with physical TAPs to a remote access multiplexer. When references are made to the logical VT1.5 level TAPs on the Traverse DCS3/1, the resulting test access configurations are effectively cross-connected to DS1 ports on the remote multiplexer for testing. DCS3/1 Logical TAPs (e.g., VT1.5 on OC-N port) STS-1 or VT Path SONET Network Remote Access Multiplexer Physical TAPs (e.g., DS1) Remote Test Unit (RTU) Figure 5-2 Remote Traverse DCS3/1 Test Access Release OPS3.1.x Turin Networks Page 5-3

240 Node Operations and Maintenance Guide, Section 5: Test Access Mode Configurations Mode Configurations There are multiple monitor and split test access mode configurations available for use with bidirectional, unidirectional, and unmapped DS3/STS-1 and DS1/VT1.5 services. The Traverse system supports the following test access mode configurations: Monitor Configurations, page 5-6 Split Configurations, page 5-7 Each test access mode supports a set of service types. The following table shows the test access mode versus service compatibility matrix where A = Allowed, NA = Not Allowed. Table 5-1 Test Access Mode vs. Service Compatibility Matrix Mode Service Bidirectional Unidirectional Unmapped MONE A A A MONEF A NA NA MONF A NA NA SPLTA A A NA SPLTB A NA NA SPLTE A A A SPLTEF A NA NA SPLTF A NA NA Page 5-4 Turin Networks Release OPS3.1.x

241 Chapter 1 Traverse Test Access Access Identifier (AID) Access Identifier (AID) The access identifier (AID) is a simple or compound string to uniquely identify a Traverse service (ingress or egress) endpoint. Although the endpoint is the same, the actual AID format differs between the TransNav management system or node-level access interfaces (GUI and TL1) quite simply because there are underlying interface structural differences. TransNav GUI AID Format For example, the AID format for a DS1 port facility is the following compound string group s(1-m)(ds1), p(1-28)(ds1). The s stands for slot. The M is 4 for the Traverse 600, 12 for the Traverse 1600, or 16 for the Traverse 2000, offering all possible module (card) slot choices. The p stands for port. The port number choices are from 1 to 28. DS1 identifies the module and port type, respectively. See Figure 5-3 TransNav GUI AID Format Example below. For service endpoint mapping definitions, refer to TransNav Management System GUI Guide, Section 9 Appendices, Appendix A Service Endpoints : Figure 5-3 TransNav GUI AID Format Example TL1 AID Format For example, the AID format for a DS1 port facility is FAC-(1-M)-(1-28). FAC stands for facility. The M is 4 offering 1 to 4 possible module (card) slot choices on the Traverse 600, 12 offering 1 to 12 possible module slot choices on the Traverse 1600, or 16 offering 1 to 16 possible module slot choices for the Traverse The port number choices are from 1 to 28. For a list of TL1-specific Traverse system AID formats, refer to TransNav Management System TL1 Guide, Appendix C AIDs. Release OPS3.1.x Turin Networks Page 5-5

242 Node Operations and Maintenance Guide, Section 5: Test Access Monitor Configurations Monitor Configurations Each monitor configuration is non-intrusive. The original service remains intact so there is no disruption to customer traffic while monitoring the data flow. Test access provides three monitor mode configurations: MONE - Monitor unidirectional data flow from ingress to egress termination point MONF - Monitor unidirectional data flow from egress to ingress termination point 2 MONEF - Monitor bidirectional data flow from both the ingress and egress termination points MONE Test Access MONF Test Access E F E F FAD MONEF Test Access FAD E F FAD FAD Figure 5-4 Monitor Configurations 2 If MONF is configured with a DFAD instead of the standard FAD, then it uses the second FAD. Page 5-6 Turin Networks Release OPS3.1.x

243 Chapter 1 Traverse Test Access Split Configurations Split Configurations Each split configuration is intrusive. These configurations disable the original service so there is disruption to customer traffic. There are two kinds of split configurations: series and per side. Test access provides five split mode configurations: SPLTE - Per side split on the ingress termination point to test the ingress service SPLTF - Per side split on the egress termination point to test the egress service 3 SPLTEF - Per side split on both the ingress and egress termination points to test services simultaneously SPLTA - Series split on the ingress termination point to test data flow from the ingress toward the egress termination point SPLTB - Series split on the egress termination point to test data flow from the egress toward the ingress termination point 4 SPLTA Test Access SPLTB Test Access A A B B FAD FAD SPLTE Test Access SPLTF Test Access E F E F FAD SPLTEF Test Access FAD E F FAD FAD Figure 5-5 Split Configurations 3 If SPLTF is configured with a DFAD instead of the common FAD, then it uses the second FAD. 4 If SPLTB is configured with a DFAD instead of the standard FAD, then it uses the second FAD. Release OPS3.1.x Turin Networks Page 5-7

244 Node Operations and Maintenance Guide, Section 5: Test Access Feature Set Options Feature Set Options The Traverse system provides the following full feature set module and user access interface options to support DCS3/1 test access applications. Choose those items that fit your network and test configuration requirements: Modules: DS1 The DS1 module terminates up to 28 DS1s and provides mapping of DS1 to VT1.5 to enable grooming of VT1.5 at the VT Switch module. E1 The E1 module terminates up to 21 E1s and provides mapping of E1 to VC to enable grooming of VC at the VCX component STM module. DS3/E3/EC-1 The DS3/E3/EC-1 module is a single-slot 12 or 24-port transport module that provides twelve or twenty-four DS3 Clear Channel and twelve Transmux transport interfaces. The DS3/E3/EC-1 module provides support for SONET STS-1 or SDH TU-3/TUG-3/AU-3 mapping of DS3/E3/EC-1 client signals. DS3/EC-1 Transmux The DS3/EC-1 Transmux module is a single-slot 12-port module that provides DS3 transmultiplexing (transmux) functions for channelized DS3 access to the Traverse platform. In addition to transmux functionality, any port can be independently configured for DS3 clear channel or EC-1 through the user interface. OC-N/STM-N The OC-N/STM-N modules integrate the capabilities of a high-performance SONET/SDH Add-Drop Multiplexer (ADM) and a non-blocking cross connect in a single module. The OC-N/STM-N module ports can be used as a trunk interface or for the aggregation and grooming of SONET/SDH services. Virtual Tributary/Tributary Unit (VT/TU) Switch The VT/TU 5G Switch module integrates wideband switching and grooming functions into the Traverse platform. This module has a termination capacity of 5 Gbps for up to 32 STS-3c/AU-4 equivalents or 96 STS-1/AU-3 equivalents. Virtual Tributary Cross-connect (VTX) The OC-48/STM-16 and GCM modules with an integrated virtual tributary/container (VT/VC) cross-connect component (VTX/VCX) known simply as VTX. The VTX component has a termination capacity of 2.5 Gbps for up to 16 STS-3c/AU-4 equivalents or 48 STS-1/AU-3 equivalents. User Access Interfaces: Node-level Control Link Direct test access configuration management via standards-compliant node-level TL1 (Transaction Language 1) or CLI (Command Line Interface) control link interface from the TSC or RTU to the Traverse general control module. The physical connection of the control link is between the Traverse DCS3/1 system general control module (GCM) and the remote test system utilizing the Ethernet interface. The CLI interface also supports the RS-232 interface. TransNav Management System Direct test access configuration management via the TransNav graphical user interface (GUI), CLI, or TL1 interface. Refer to the TransNav Management System Product Overview Guide. Page 5-8 Turin Networks Release OPS3.1.x

245 Chapter 1 Traverse Test Access Monitor Test Access Example (MONE) Configuration Management Test Access Mode Examples Monitor Test Access Example (MONE) The user can manage the test access feature through the GUI, CLI, or TL1 interface. Each interface is unique and offers the ability to create, change mode, view, disconnect, and report on test access configurations. GUI The procedures in this chapter use this interface. For further information, refer to the TransNav Management System GUI Guide. CLI CLI scripts may be written to automate test access. These scripts run in the TSC or the RTU itself. For further information, refer to the TransNav Management System CLI Guide. TL1 TL1 scripts may be written to automate test access. These scripts run in the TSC or the RTU itself. This interface is interoperable with the Spirent network tester, BRTU with REACT remote test OSS. For further information, refer to the TransNav Management System TL1 Guide. The test access mode examples identified below use the TransNav management system as the user interface for configuration management. See one of the following test access mode examples: Monitor Test Access Example (MONE), page 5-9 Series Split Test Access Example (SPLTA), page 5-18 Per Side Split Test Access Example (SPLTE), page 5-14 The MONE (Monitor-E) monitor test access configuration is non-intrusive. There is no disruption to customer traffic. A MONE monitor test access configuration is shown in the figure below. At the top of the figure, a service is provisioned and activated between the source (S1) and destination (D1). The original service operational state is enabled and the service state Release OPS3.1.x Turin Networks Page 5-9

246 Node Operations and Maintenance Guide, Section 5: Test Access Monitor Test Access Example (MONE) is active. These states remain intact through the MONE test access mode configuration and use. Service to be Tested S1 DCS D1 TAP (e.g., DS1) Monitor Test Access (Non-Intrusive) S1 DCS D1 TAP1 Figure 5-6 Monitor Test Access Configuration MONE Page 5-10 Turin Networks Release OPS3.1.x

247 Chapter 1 Traverse Test Access Monitor Test Access Example (MONE) Use the following procedure to create the MONE monitor test access configuration. This configuration allows the test equipment at test access port (TAP1) to monitor the data flow in the direction from the source (S1) to destination (D1). Table 5-2 Monitor Test Access Configuration MONE Step Procedure 1 Physically connect the cable for the TAP from the remote test unit (RTU) into the patch panel connected to the Traverse DSC3/1. 2 Using the TransNav GUI, from the Test Access tab, TAP sub-tab, create a logical TAP (single FAD) of the same type as the service source termination point (S1). Figure 5-7 Example VT TAP (Single FAD) Release OPS3.1.x Turin Networks Page 5-11

248 Node Operations and Maintenance Guide, Section 5: Test Access Monitor Test Access Example (MONE) Table 5-2 Monitor Test Access Configuration MONE (continued) Step Procedure 3 From the Test Access tab, TAC sub-tab, create a Monitor-E (MONE) TAC from the source (S1) to a logical TAP. Note: Use the Switch Mode button to switch from one mode configuration to another. For valid mode changes, see Table 5-1 Test Access Mode vs. Service Compatibility Matrix. MONE Mode TAP1 Service ID Connected State Switch Mode command Figure 5-8 MONE TAC Example Page 5-12 Turin Networks Release OPS3.1.x

249 Chapter 1 Traverse Test Access Monitor Test Access Example (MONE) Table 5-2 Monitor Test Access Configuration MONE (continued) Step Procedure 4 The original service remains intact (enabled) as seen when you select the Service tab. Service ID Enabled Operational State Figure 5-9 Service with MONE TAC Example 5 With the TAC enabled to the RTU, you can now monitor the ingress (S1) to egress (D1) data flow at the source service under test. 6 To disconnect the TAC from the original (and still active) service, simply remove the TAC. 7 The Monitor Test Access Configuration MONE procedure is complete. Release OPS3.1.x Turin Networks Page 5-13

250 Node Operations and Maintenance Guide, Section 5: Test Access Per Side Split Test Access Example (SPLTE) Per Side Split Test Access Example (SPLTE) The SPLTE per side split test access configuration is intrusive. A SPLTE per side split test access configuration is shown in the figure below. At the top of the figure, a service is provisioned and activated between the source (S1) and destination (D1). The original service operational state is enabled and the service state is active. The service under the test operational state is disabled. Service to be Tested S1 DCS D1 TAP (e.g., DS1) Per Side Split Test Access (Intrusive) S1 DCS D1 TAP1 Figure 5-10 Per Side Split Test Access Configuration SPLTE Page 5-14 Turin Networks Release OPS3.1.x

251 Chapter 1 Traverse Test Access Per Side Split Test Access Example (SPLTE) Use the following procedure to create the per side split test access configuration. Table 5-3 Per Side Split Test Access Configuration SPLTE Step Procedure 1 Physically connect the cables for TAP from the remote test unit (RTU) into the patch panel connected to the Traverse DSC3/1. 2 Using the TransNav GUI, from the Test Access, TAP tab, create a logical test access point (TAP) (single FAD) of the same type as the source termination point (S1). Figure 5-11 Example VT TAP (Single FAD) Release OPS3.1.x Turin Networks Page 5-15

252 Node Operations and Maintenance Guide, Section 5: Test Access Per Side Split Test Access Example (SPLTE) Table 5-3 Per Side Split Test Access Configuration SPLTE (continued) Step Procedure 3 From the Test Access tab, TAC sub-tab, create a per side split (SPLTE) test access cross-connect (TAC) from the source (S1) to a logical TAP. Note: Use the Switch Mode button to switch from one mode configuration to another. For valid mode changes, see Table 5-1 Test Access Mode vs. Service Compatibility Matrix. SPLTE Mode TAP2 Service ID Connected State Switch Mode command Figure 5-12 SPLTE TAC Example Page 5-16 Turin Networks Release OPS3.1.x

253 Chapter 1 Traverse Test Access Per Side Split Test Access Example (SPLTE) Table 5-3 Per Side Split Test Access Configuration SPLTE (continued) Step Procedure 4 The system disables the original service as seen when you select the Service tab. Service ID Enabled Operational State Figure 5-13 Service with SPLTE TAC Example 5 With the TAC enabled to the RTU, you can now run various tests on the source service under test. Note: An alarm indication signal (AIS) is automatically transmitted in the direction of D1 to indicate service disruption due to the test configuration. 6 To remove the TAC from the original (and still active) service, simply remove the TAC. Note: The system restores the original service state. 7 The Per Side Split Test Access Configuration SPLTE procedure is complete. Release OPS3.1.x Turin Networks Page 5-17

254 Node Operations and Maintenance Guide, Section 5: Test Access Series Split Test Access Example (SPLTA) Series Split Test Access Example (SPLTA) The SPLTA series split test access configuration is intrusive. A SPLTA series split test access configuration is shown in the figure below. At the top of the figure, a service is provisioned and activated between the source (S1) and destination (D1). The original service operational state is enabled and the service state is active. The service under the test operational state is disabled. Service to be Tested S1 DCS D1 TAP (e.g., DS1) Series Split Test Access (Intrusive) S1 DCS D1 TAP1 Figure 5-14 Series Split Test Access Configuration SPLTA Page 5-18 Turin Networks Release OPS3.1.x

255 Chapter 1 Traverse Test Access Series Split Test Access Example (SPLTA) Use the following procedure to create the series split test access configuration. Table 5-4 Series Split Test Access Configuration SPLTA Step Procedure 1 Physically connect the cables for TAP (test access point) from the remote test unit (RTU) into the patch panel connected to the Traverse DSC3/1. 2 Using the TransNav GUI, from the Test Access tab, TAP sub-tab, create a logical TAP (single FAD) of the same type as the source termination point (S1). Figure 5-15 Example DS1 TAP (Single FAD) Release OPS3.1.x Turin Networks Page 5-19

256 Node Operations and Maintenance Guide, Section 5: Test Access Series Split Test Access Example (SPLTA) Table 5-4 Series Split Test Access Configuration SPLTA (continued) Step Procedure 3 From the Test Access tab, TAP sub-tab, create a series split (SPLTA) test access cross-connect (TAC) from the source (S1) to a logical TAP. Note: Use the Switch Mode button to switch from one mode configuration to another. For valid mode changes, see Table 5-1 Test Access Mode vs. Service Compatibility Matrix. SPLTE Mode TAP3 Service ID Connected State Switch Mode command Figure 5-16 SPLTA TAC Example Page 5-20 Turin Networks Release OPS3.1.x

257 Chapter 1 Traverse Test Access Series Split Test Access Example (SPLTA) Table 5-4 Series Split Test Access Configuration SPLTA (continued) Step Procedure 4 The system disables the original service as seen when you select the Service tab. Service ID Enabled Operational State Figure 5-17 Service with SPLTA TAC Example 5 With the TAC enabled to the RTU, you can now run various tests on the source service under test. 6 To remove the TAC from the original (and still active) service, simply remove the TAC. Note: The system restores the original service state. 7 The Series Split Test Access Configuration SPLTA procedure is complete. Release OPS3.1.x Turin Networks Page 5-21

258 Node Operations and Maintenance Guide, Section 5: Test Access Series Split Test Access Example (SPLTA) Page 5-22 Turin Networks Release OPS3.1.x

259 SECTION 5TEST ACCESS Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface Introduction This appendix includes the following topics. Traverse Platform and Spirent BRTU Interoperability, page 5-24 Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface, page 5-25 For general Traverse test access information, refer to Section 5 Test Access, Chapter 1 Traverse Test Access, page 5-1. Release OPS3.1.x Turin Networks Page 5-23

260 Node Operations and Maintenance Guide, Section 5: Test Access Traverse Platform and Spirent BRTU Interoperability Traverse Platform and Spirent BRTU Interoperability The Traverse platform interoperates with the Spirent Communication s Broadband Remote Test Unit (BRTU) network tester to provide integrated test access functionality. The Traverse system, TransNav management system graphical user interface (GUI), and Spirent BRTU with REACT remote test Operations Support System (OSS) enables carriers to test and monitor any DS1/VT1.5 or DS3/STS-1 service provisioned on the Traverse switch fabric. Turin TransNav GUI Spirent REACT OSS Figure 5-18 Turin TransNav GUI and Spirent BRTU REACT OSS Example Page 5-24 Turin Networks Release OPS3.1.x

261 Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface Use the following guidelines to set up Traverse test access interoperability with the Spirent BRTU. Read through all of these guidelines before you begin the system setup. The Username and Password TransNav management system parameters must be in all caps format. For parameter descriptions, refer to the TransNav Management System GUI Guide, Section 2 Administrative Tasks, Chapter 1 Managing Server Security, Security Management, page 2-1. Configure the TransNav user as both a Domain User and a Node User. The Traverse system and Spirent BRTU must be on the same subnet when communicating via the backplane data communications network (DCN) Ethernet IP connection. Configure the Spirent BRTU with the Traverse backplane DCN Ethernet IP address (BP DCN IP) and use port 9988 (system) or 9989 (user) to communicate from the Spirent BRTU to the Traverse digital cross-connect system (DCS). Configure the Traverse DCS equipment type as O for other in the current version of the Spirent BRTU REACT OSS. All tests are driven from the test system controller (TSC) user interface to the Spirent Communication s remote test unit (RTU) REACT OSS. For a configuration example, see Section 5 Test Access, Chapter 1 Traverse Test Access, Local Test Access, page 5-2. If the Spirent BRTU is to also act as the TSC, then configure it to TSC mode. The TL1 target identifier (TID) is the Traverse network element node identifier, know as the Node Name in the TransNav GUI or node-id in the command line interface (CLI). For a TID format description, refer to TransNav Management System TL1 Guide. Each access identifier (AID) is equal to a Traverse service (ingress or egress) endpoint. For a list of all possible Traverse system AID formats in TL1, refer to TransNav Management System TL1 Guide, Appendix C AIDs. For service endpoint mapping definitions, refer to TransNav Management System GUI Guide, Section 9 Appendices, Appendix A Service Endpoints. Note that the AID formats may differ between the Traverse GUI, TL1, or CLI and that of the Spirent BRTU. For a list of Spirent BRTU AID formats, refer to your Spirent test access documentation. Configure the test access point (TAP) and test access cross-connect (TAC) via the TransNav management system or over the node-level TL1 control link. For a configuration example, see Section 5 Test Access, Chapter 1 Traverse Test Access, Monitor Test Access Example (MONE), page 5-9. For parameter descriptions, refer to TransNav Management System GUI Guide, Section 8 Maintenance and Testing, Chapter 5 Test Access, page 8-43 or the TransNav Management System TL1 Guide, Section 3.7 Test Access Commands. The Spirent BRTU uses the term DS3 test access digroup (TAD) which is a Traverse system DS1 subport within a DS3 Transmux port. Release OPS3.1.x Turin Networks Page 5-25

262 Node Operations and Maintenance Guide, Section 5: Test Access Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface Page 5-26 Turin Networks Release OPS3.1.x

263 SECTION 6SYSTEM MONITORING SECTION 6 ROUTINE MAINTENANCE SECTION 6 Contents Chapter 1 Routine Maintenance Introduction Fan Air Filter Maintenance Fan Assemblies Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000) Fan Module with Integral Fan Tray (Traverse 600) Fan Assembly (TE-100) Fan Tray Module (Legacy Traverse) Air Filters Air Filter Replacement Air Filter Replacement (Traverse 1600 and Traverse 2000) Fan Tray Air Filter Replacement (Traverse 600) Air Filter Replacement (TE-100) Air Filter Replacement (Legacy Traverse) PDAP Maintenance PDAP-15A GMT Fuse Replacement PDAP-2S Circuit Breaker Replacement PDAP-2S GMT Fuse Replacement PDAP-2S LED Module Replacement PDAP-4S TPA Fuse Replacement PDAP-4S GMT Fuse Replacement PDAP-4S LED Module Replacement Environmental Alarm Module Replacement (Traverse only) Non-Field Replaceable Fuses Chapter 2 Node Database Backup and Restore Backing Up the Node Database Guidelines for Node Database Backups Node Database Restore Guidelines Backup and Restore Commands exec node database backup exec node database restore Troubleshooting Backup and Restore Release OPS3.1.x Turin Networks Page vii

264 Node Operations and Maintenance Guide, Section 6 Routine Maintenance List of Figures Figure 6-1 Front Inlet Air Filter Figure 6-2 Traverse 600 Fan Assembly Air Filter Figure 6-3 Fan Cage and Assembly Figure 6-4 Removing the Air Filter Figure 6-5 Attaching the Air Filter Figure 6-6 Air Filter with Springs Figure 6-7 Fan Tray Holder Front Cover Figure 6-8 Air Filter with Handle Figure 6-9 Fan Tray Holder Front Cover Figure 6-10 PDAP-15A Front View Figure 6-11 PDAP-2S Circuit Breakers Figure 6-12 PDAP-2S GMT Fuses Figure 6-13 PDAP-2S Assembly - Remove Front Cover Figure 6-14 PDAP-2S Assembly - LED Module Figure 6-15 PDAP-2S LED Module Guides Figure 6-16 PDAP-4S TPA Fuses Figure 6-17 PDAP-4S TPA Fuse and Holder Figure 6-18 PDAP-4S GMT Fuses Figure 6-19 PDAP-4S Assembly - LED Faceplate Figure 6-20 EAM Location - Traverse 1600 Main Backplane Figure 6-21 EAM Alignment List of Tables Table 6-1 Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000) Table 6-2 Insert a Fan Assembly Air Filter (Traverse 600) Table 6-3 Replace the Fan Air Filter (TE-100) Table 6-4 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) Table 6-5 Fan Tray Air Filter (with handle) Installation Table 6-6 Replacing PDAP-15A GMT Fuses Table 6-7 Replacing PDAP-2S Circuit Breakers Table 6-8 Replacing PDAP-2S GMT Fuses Table 6-9 Replacing PDAP-2S LED Module Table 6-10 Replacing PDAP-4S TPA Fuses Table 6-11 Replacing PDAP-4S GMT Fuses Table 6-12 Replacing PDAP-4S LED Module Table 6-13 Replacing EAM Table 6-14 CLI Command Conventions Page viii Turin Networks Release OPS3.1.x

265 SECTION 6ROUTINE MAINTENANCE Chapter 1 Routine Maintenance Introduction Fan Air Filter Maintenance Fan Assemblies This chapter provides routine maintenance tasks for node-specific system equipment: Fan Air Filter Maintenance, page 6-1 PDAP Maintenance, page 6-10 Environmental Alarm Module Replacement (Traverse only), page 6-20 The fan maintenance topics are as follows: Fan Assemblies, page 6-1 Air Filters, page 6-2 Air Filter Replacement, page 6-2 Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000) The Traverse 1600 and Traverse 2000 fan assembly (fan tray with integrated air ramp and fan module) cools the control modules and service modules in the shelf. The Traverse 1600 fan assembly has 5 fans. The Traverse 2000 fan assembly has 6 fans. The fans draw in cooling air from the front and push the air upward through the perforated shelf. The integrated air ramp on the shelf above directs the heated air through to the rear of the shelf. The fan module can force up to 200 cubic feet per minute of cooling air. Fan Module with Integral Fan Tray (Traverse 600) The Traverse 600 fan assembly (fan module with integral fan tray) cools the control modules and service modules in the shelf. The Traverse 600 fan assembly has 6 fans. The fans draw in cooling air and push the air through the perforated shelf. The fan module can force up to 200 cubic feet per minute of cooling air. Fan Assembly (TE-100) The TE-100 shelf has a pre-installed, field-replaceable fan assembly. The fan assembly consists of three fans and a replaceable, cleanable air filter. Fan Tray Module (Legacy Traverse) This topic applies to the original (pre-release 1.4) Traverse 1600 and Traverse 2000 fan assembly. The Traverse fan assembly (fan tray holder with fan module and separate Release OPS3.1.x Turin Networks Page 6-1

266 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Air Filters air ramp) cools the GCM and service interface modules. The Traverse 1600 and Traverse 2000 fan assemblies have ten (6 large and 4 small) and eight (large) fans, respectively. The fans draw in cooling air from the front and push the air upward through the perforated shelf. The separate air ramp above the shelf directs the heated air through to the rear of the shelf. Air Filters The air filters on the Traverse and TE-100 systems play a very important role in the cooling function of the modules. Important: Fan tray air filters should be checked once every six months and replaced as necessary. There are environmental factors that could decrease the amount of time required between air filter replacements. These environmental factors must be checked regularly. Any unusual environmental circumstance at the site that causes an increase in temperature and/or particulate matter in the air might affect performance (for example, new equipment installation). Important: The speeds of the cooling fans should be monitored regularly in order to accurately determine air filter replacement intervals. An increase in overall fan speed may indicate a clogged filter. Air Filter Replacement Air Filter Replacement (Traverse 1600 and Traverse 2000) The fan air filter replacement topics are as follows: Air Filter Replacement (Traverse 1600 and Traverse 2000), page 6-2 Fan Tray Air Filter Replacement (Traverse 600), page 6-4 Air Filter Replacement (TE-100), page 6-5 Air Filter Replacement (Legacy Traverse), page 6-7 When the front inlet fan tray air filter (for either Traverse 1600 or Traverse 2000) has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter. Important: The instructions below support the redesigned front inlet fan tray with integrated air ramp unit. Refer to Air Filter Replacement (Legacy Traverse), page 6-7 in the Traverse Release 2.0 documentation if you are installing an original fan tray air filter. The Release 2.0 documentation is on the Turin Infocenter at User registration is required. To register for the Turin Infocenter, contact your sales account team. Required Equipment: New front inlet fan tray air filter. The front inlet fan tray air filters are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. Page 6-2 Turin Networks Release OPS3.1.x

267 Chapter 1 Routine Maintenance Air Filter Replacement (Traverse 1600 and Traverse 2000) The following procedure provides step-by-step instructions on how to insert the front inlet fan tray air filter. Table 6-1 Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000) Step Procedure 1 Grasp the air filter flexible pull tab. Figure 6-1 Front Inlet Air Filter Pull Tab (top view) 2 Insert the air filter in the gap between the top of the front inlet fan module and the top of the front inlet fan tray holder. Slide the air filter along the fan tray holder guides until the filter is flush with the front of the fan tray holder. 3 The Fan Tray Air Filter (with springs) Installation (Traverse, legacy) procedure is complete. Release OPS3.1.x Turin Networks Page 6-3

268 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Fan Tray Air Filter Replacement (Traverse 600) Fan Tray Air Filter Replacement (Traverse 600) When the Traverse 600 fan air filter has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter. Required Equipment: New air filter The Traverse 600 fan air filters are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. The following procedure provides step-by-step instructions on how to insert the air filter. Table 6-2 Insert a Fan Assembly Air Filter (Traverse 600) Step Procedure 1 Grasp the air filter flexible pull tab. Figure 6-2 Traverse 600 Fan Assembly Air Filter Pull Tab (top view) 2 Insert the air filter in the gap between the fan assembly and the left of the fan cage. Slide the air filter along the guides until the filter is flush. 3 The Fan Tray Air Filter (with springs) Installation (Traverse, legacy) procedure is complete. Page 6-4 Turin Networks Release OPS3.1.x

269 Chapter 1 Routine Maintenance Air Filter Replacement (TE-100) Air Filter Replacement (TE-100) When the TE-100 fan air filter has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter. Required Equipment: New air filter The fan assembly is in a vertical slot on the left front of the shelf. It draws ambient air through the perforation on the left wall and forces the air over the system and interface modules in the horizontal slots. The fan assembly must be removed before the air filter can be replaced because the metal air filter attaches to the side of the fan assembly. The following procedure provides step-by-step instructions on how to replace the TE-100 air filter. Table 6-3 Replace the Fan Air Filter (TE-100) Step Procedure 1 Loosen the captive fastener that holds the fan assembly in place. 2 Slide the fan assembly out of the fan cage. Fan Cage Captive Fastener Figure 6-3 Fan Cage and Assembly 3 Lift the old air filter from the fan assembly. Pull up on the air filter Figure 6-4 Removing the Air Filter 4 Make sure the new air filter is clean and free of dust particles. Release OPS3.1.x Turin Networks Page 6-5

270 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Air Filter Replacement (TE-100) Table 6-3 Replace the Fan Air Filter (TE-100) (continued) Step Procedure 5 Slide the air filter into place, lining up the small tabs with the small holes on the fan assembly. Tabs Lined up with Holes Figure 6-5 Attaching the Air Filter 6 Slide the fan assembly back into the fan cage. Important: Do not force the fan assembly into position. If it does not plug in easily, slide it back out and check for any obstructions that might prevent it from sliding into position. 7 Tighten the captive fastener to secure the fan assembly in place. 8 The Replace the Fan Air Filter (TE-100) procedure is complete. Page 6-6 Turin Networks Release OPS3.1.x

271 Chapter 1 Routine Maintenance Air Filter Replacement (Legacy Traverse) Air Filter Replacement (Legacy Traverse) This topic applies to air filters for the original fan tray unit without an integrated air ramp (pre-release 1.4). Refer to Air Filter Replacement (Traverse 1600 and Traverse 2000), page 6-2 if you are replacing a front inlet fan tray air filter into the redesigned front inlet fan tray holder with integrated air ramp unit. Refer to Fan Tray Air Filter Replacement (Traverse 600), page 6-4 if you are replacing a Traverse 600 fan air filter. When the fan tray air filter has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use one of the following procedures to replace the filter with either springs or a handle. Required Equipment: New fan tray air filter There are two different designs of fan tray air filters as listed below. Both designs are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. Table 6-4 Fan Tray Air Filter (with springs) Installation (Traverse, legacy), page 6-7 Table 6-5 Fan Tray Air Filter (with handle) Installation, page 6-9 Table 6-4 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) Step Procedure 1 Rotate the air filter pull-tabs out. Springs Pull Tabs Figure 6-6 Air Filter with Springs 2 Hold the air filter with the metal window-pane side down and the springs to the back. 3 Insert the air filter in the gap between the fan tray module and the top of the fan tray holder. Slide the air filter along the fan tray holder guides until the springs on the back edge are fully compressed. Release OPS3.1.x Turin Networks Page 6-7

272 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Air Filter Replacement (Legacy Traverse) Table 6-4 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) Step Procedure 4 With the springs fully compressed, lift the front edge of the air filter up and over the retaining flanges and release it. 5 Rotate the pull-tabs so they are parallel to the front edge of the air filter. 6 Lift the fan tray holder front cover into its closed position. Tighten the captive fasteners to secure it. Captive Fasteners Figure 6-7 Fan Tray Holder Front Cover Note: The front cover closes very easily when the fan tray module and air filter are in position. If the cover does not close easily, check the fan tray module to make sure it is recessed from the front of the fan tray holder. 7 The Fan Tray Air Filter (with springs) Installation (Traverse, legacy) procedure is complete. Page 6-8 Turin Networks Release OPS3.1.x

273 Chapter 1 Routine Maintenance Air Filter Replacement (Legacy Traverse) The following procedure provides step-by-step instructions on how to install the fan tray filter with a handle on the front edge. Table 6-5 Fan Tray Air Filter (with handle) Installation Step Procedure 1 Hold the air filter with the metal window-pane side down with the handle facing to the front. Handle Figure 6-8 Air Filter with Handle 2 Insert the air filter in the gap between the fan tray module and the top of the fan tray holder. 3 Slide the air filter along the fan tray holder guides. Lift up on the filter handle as you are pushing the filter towards the back of the fan tray holder. There is an audible click when the air filter is in position. The handle drops down over the front of the fan tray module. Release OPS3.1.x Turin Networks Page 6-9

274 Node Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP Maintenance Table 6-5 Fan Tray Air Filter (with handle) Installation (continued) Step Procedure 4 Lift the fan tray holder front cover into its closed position. Tighten the captive fasteners to secure it. Captive Fasteners Figure 6-9 Fan Tray Holder Front Cover Note: The front cover closes very easily when the fan tray module and air filter are correctly in position. If the cover does not close easily, check the fan tray module to make sure it is recessed from the front of the fan tray holder. 5 The Fan Tray Air Filter (with handle) Installation procedure is complete. PDAP Maintenance PDAP-15A GMT Fuse Replacement The Power Distribution and Alarm Panel (PDAP) maintenance topics are as follows: PDAP-15A GMT Fuse Replacement, page 6-10 PDAP-2S Circuit Breaker Replacement, page 6-11 PDAP-2S GMT Fuse Replacement, page 6-12 PDAP-2S LED Module Replacement, page 6-14 PDAP-4S TPA Fuse Replacement, page 6-16 PDAP-4S GMT Fuse Replacement, page 6-18 PDAP-4S LED Module Replacement, page 6-19 The PDAP-15A provides GMT fuses (from 0.25 amps to 15 amps per fuse) for up to ten pieces of auxiliary equipment. The PDAP s field replaceable fuses are accessible without having to remove the front panel. Use the following procedure to replace a failed GMT fuse. WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits. Page 6-10 Turin Networks Release OPS3.1.x

275 Chapter 1 Routine Maintenance PDAP-2S Circuit Breaker Replacement Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-15A). Plug the ESD wrist strap into an ESD jack or other confirmed source of earth ground. Table 6-6 Replacing PDAP-15A GMT Fuses Step Procedure 1 Remove the GMT fuse by pulling it straight out. 1 GMT Fuses Alarm LEDs Figure 6-10 PDAP-15A Front View 2 Replace the failed GMT fuse with a new one of equal current rating. 3 The Replacing PDAP-2S GMT Fuses procedure is complete. 1 The GMT fuses protrude from the PDAP-15A front panel to allow access for fuse removal and insertion without having to remove the front panel. PDAP-2S Circuit Breaker Replacement The Power Distribution and Alarm Panel (PDAP-2S) contains field replaceable 40 ampere (amp) circuit breakers. 1 Each pair of A and B circuit breakers (e.g., A1, B1) provides redundant circuit protection per shelf. Power will not be lost to the shelf if a circuit breaker fails. Use the following procedure to replace a failed circuit breaker. WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-2S). Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. 1 Optional PDAP-2S circuit breakers are available up to a 50 amp maximum. Release OPS3.1.x Turin Networks Page 6-11

276 Node Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-2S GMT Fuse Replacement Table 6-7 Replacing PDAP-2S Circuit Breakers Step Procedure 1 If the toggle switch on the failed circuit breaker is in the On position, switch it off. Toggle Switches Circuit Breakers, Pair A Circuit Breakers, Pair B Figure 6-11 PDAP-2S Circuit Breakers 2 Remove the circuit breaker by pulling it straight out. 3 Replace the failed circuit breaker with a new one of equal current rating. 4 Switch the new circuit breaker on. 5 The Replacing PDAP-2S Circuit Breakers procedure is complete. PDAP-2S GMT Fuse Replacement The PDAP-2S contains two fuse blocks (A and B) of ten field replaceable GMT fuses. Each block has a 100 amp maximum load. Each pair of A and B GMT fuses (e.g., A1, B1) provides redundant power (from 0.25 to 10 amps per fuse) to one of up to ten pieces of auxiliary equipment. Use the following procedure to replace a failed GMT fuse. WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-2S). Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Page 6-12 Turin Networks Release OPS3.1.x

277 Chapter 1 Routine Maintenance PDAP-2S GMT Fuse Replacement Table 6-8 Replacing PDAP-2S GMT Fuses Step Procedure 1 Remove the GMT fuse by pulling it straight out. 1 GMT Fuse Block GMT Fuse Block (Pair A) (Pair B) Figure 6-12 PDAP-2S GMT Fuses 2 Replace the failed GMT fuse with a new one of equal current rating. 3 The Replacing PDAP-2S GMT Fuses procedure is complete. 1 The GMT fuses protrude from the PDAP-2S front panel to allow access for fuse removal and insertion without having to remove the front panel. Release OPS3.1.x Turin Networks Page 6-13

278 Node Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-2S LED Module Replacement PDAP-2S LED Module Replacement The Power Distribution and Alarm Panel (PDAP-2S) system alarm LEDs (Critical, Major, Minor), power input A and B LEDs, and GMT A and B fuse block failure LEDs are on one field replaceable module. Use the following procedure to replace the PDAP-2S LED module. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the PDAP-2S. Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Table 6-9 Replacing PDAP-2S LED Module Step Procedure 1 Loosen the two captive fasteners on the PDAP-2S front cover to release it. Figure 6-13 PDAP-2S Assembly - Remove Front Cover 2 Remove the front cover. Captive Fasteners Page 6-14 Turin Networks Release OPS3.1.x

279 Chapter 1 Routine Maintenance PDAP-2S LED Module Replacement Table 6-9 Replacing PDAP-2S LED Module (continued) Step Procedure 3 Locate the nonfunctional module with a white pull tab at the center of the PDAP-2S. White Pull Tab LED module Figure 6-14 PDAP-2S Assembly - LED Module 4 Remove the module by pulling it straight out using the white pull tab. 5 Insert the new PDAP-2S LED module using the left and right guides for proper alignment. Important: The module should insert easily into the PDAP-2S. Do not force it into position. If the module does not insert easily, slide it back out and verify you are placing it in the correct position and inserting it into the correct left and right guides. Right Guide Left Guide Figure 6-15 PDAP-2S LED Module Guides 6 Replace the front cover. 7 Tighten the two captive fasteners on the PDAP-2S front cover to secure it. 8 The Replacing PDAP-2S LED Module procedure is complete. Release OPS3.1.x Turin Networks Page 6-15

280 Node Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-4S TPA Fuse Replacement PDAP-4S TPA Fuse Replacement The Power Distribution and Alarm Panel (PDAP-4S) contains field replaceable 40 amp TPA fuses. 2 Each pair of A and B TPA fuses (e.g., A1, B1) provides redundant protection per shelf. Power will not be lost to the shelf if a TPA fuse fails. Use the following procedure to replace a failed TPA fuse. WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-4S). Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. 2 Optional PDAP-4S TPA fuses are available up to a 50 amp maximum. Page 6-16 Turin Networks Release OPS3.1.x

281 Chapter 1 Routine Maintenance PDAP-4S TPA Fuse Replacement Table 6-10 Replacing PDAP-4S TPA Fuses Step Procedure 1 If a TPA fuse LED is RED, replace the fuse embedded in the TPA holder. TPA Fuse Holders Pair A Pair B TPA Fuse LEDs TPA Fuse LEDs Figure 6-16 PDAP-4S TPA Fuses 2 Remove the TPA fuse holder by pulling it straight out. 1 TPA Fuse TPA Fuse Holder Figure 6-17 PDAP-4S TPA Fuse and Holder 3 Replace the failed TPA fuse with a new one of equal current rating (Turin recommends using 40 AMP fuses). 4 Insert the TPA fuse holder by pushing it straight in. 5 The Replacing PDAP-4S TPA Fuses procedure is complete. 1 The TPA fuses protrude from the PDAP-4S front panel to allow access for fuse removal and insertion without having to remove the front panel. Release OPS3.1.x Turin Networks Page 6-17

282 Node Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-4S GMT Fuse Replacement PDAP-4S GMT Fuse Replacement The PDAP-4S contains two fuse blocks (A and B) of five field replaceable GMT fuses. Each block has a 65 amp maximum load. Each pair of A and B GMT fuses (e.g., A1, B1) provides redundant power (from 0.25 to 15 amps per fuse) to one of up to five pieces of auxiliary equipment. Use the following procedure to replace a failed GMT fuse. WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-4S). Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Table 6-11 Replacing PDAP-4S GMT Fuses Step Procedure 1 Remove the GMT fuse by pulling it straight out. 1 GMT Fuse Block GMT Fuse Block (Pair A) (Pair B) Figure 6-18 PDAP-4S GMT Fuses 2 Replace the failed GMT fuse with a new one of equal current rating. 3 The Replacing PDAP-4S GMT Fuses procedure is complete. 1 The GMT fuses protrude from the PDAP-4S front panel to allow access for fuse removal and insertion without having to remove the front panel. Page 6-18 Turin Networks Release OPS3.1.x

283 Chapter 1 Routine Maintenance PDAP-4S LED Module Replacement PDAP-4S LED Module Replacement The Power Distribution and Alarm Panel (PDAP-4S) system alarm LEDs (Critical, Major, Minor), power input A and B LEDs, and TPA/GMT fuse block failure LED (for both A and B) are on one field replaceable module. Use the following procedure to replace the PDAP-4S LED module. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the PDAP-4S. Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Table 6-12 Replacing PDAP-4S LED Module Step Procedure 1 Loosen the two PDAP-4S LED faceplate captive fasteners to release it. Captive Fasteners Figure 6-19 PDAP-4S Assembly - LED Faceplate 2 Remove the faceplate with attached module by pulling it straight out. 3 Insert the new PDAP-4S LED module using the left and right guides for proper alignment. Important: The module should insert easily into the PDAP-4S. Do not force it into position. If the module does not insert easily, slide it back out and verify you are placing it in the correct position and inserting it into the correct left and right guides. 4 Tighten the two captive fasteners on the faceplate to secure it. 5 The Replacing PDAP-4S LED Module procedure is complete. Release OPS3.1.x Turin Networks Page 6-19

284 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Environmental Alarm Module Replacement (Traverse only) Environmental Alarm Module Replacement (Traverse only) The Environmental Alarm Module (EAM) located on the Traverse main back plane supports the environmental telemetry inputs and outputs. The EAM is an optional, field replaceable module required to support environmental alarm input/output functionality. Environmental signals are accessed through wire-wrap posts located on the main backplane, allowing the EAM to be replaced without disconnecting alarm wiring. Use the following procedure to replace the EAM on the Traverse backplane. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working with the EAM and the main backplane. Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Table 6-13 Replacing EAM Step Procedure 1 Locate and remove the nonfunctional module by simultaneously holding the module along the long edges toward the top of the module and pressing the plastic standoff tab to pull out the module. Important: The module should remove fairly easily from the main backplane connector once the plastic standoff tab is depressed. Do not force it out of position. If the module does not remove easily, check the pressure on the plastic standoff tab to be sure it is fully depressed. You may need to pivot the plastic standoff (by hand) to align the tab into a more convenient, accessible position. Connector EAM Pivotal Plastic Standoff with Tab Figure 6-20 EAM Location - Traverse 1600 Main Backplane 2 Prepare to insert the new EAM by holding the module upright along the long edges with the pins facing toward the main backplane. Page 6-20 Turin Networks Release OPS3.1.x

285 Chapter 1 Routine Maintenance Non-Field Replaceable Fuses Table 6-13 Replacing EAM (continued) Step Procedure 3 Insert the module into the main backplane EAM connector using the plastic standoff and proper alignment guides. The plastic standoff tab clicks into place when the module is properly seated. Important: The module should insert easily into the main backplane connector. Do not force it into position. If the module does not insert easily, pull it back out and verify you are placing it in the correct position and inserting it along the plastic standoff and proper alignment guides. Long edge Pins facing Main Backplane Proper Alignment Guide Plastic Standoff Guide Figure 6-21 EAM Alignment 4 The Replacing EAM procedure is complete. Non-Field Replaceable Fuses The following components in the Traverse system contain non-field replaceable fuses: Control module Service interface module Fan tray If a Traverse module requires (non-field replaceable) fuse replacement, refer to Traverse Maintenance and Testing Guide, About this Document, Calling for Repairs. If the fan tray requires fuse replacement, it will need to be replaced with a new fan tray unit. Release OPS3.1.x Turin Networks Page 6-21

286 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Non-Field Replaceable Fuses Page 6-22 Turin Networks Release OPS3.1.x

287 SECTION 6ROUTINE MAINTENANCE Chapter 2 Node Database Backup and Restore Introduction Backing Up the Node Database Guidelines for Node Database Backups This chapter provides information on backing up and restoring the node database using CLI commands. The following topics are included: Backing Up the Node Database, page 6-23 Guidelines for Node Database Backups, page 6-23 Node Database Restore Guidelines, page 6-24 Backup and Restore Commands, page 6-24 Troubleshooting Backup and Restore, page 6-26 Node databases can be backed up in one of the two methods: to an FTP server or to the GCM card. Node-level CLI commands are used for the backup and restore procedures. Turin recommends backing up the node database to a remote FTP server due to size constraints, especially if optical cards currently exist on the shelf. During the backup, provisioning is allowed. Be aware, however, that provisioned services may not be captured during the backup and may be lost when the database is restored. Backups may occur with live traffic on the node. The backup procedure produces two files: a.dat file and a.meta file. The Traverse uses these files to restore the database. If the node has minimal services, the backup will take a minute or two. However, if numerous services exist on the node, the backup may take several minutes. Have the FTP server information ready before beginning the backup procedure. The FTP (host) server IP address, the username and password are required to logon to the FTP server. If FTP server information is provided, a path must be provided in the path parameter to tell the Traverse where to backup the database. The default is the path of the FTP server directory accessed when logging into the FTP server. The backup tool does not create directories specified in the path parameter. If FTP server information is not provided: The system uses a default of (localhost). This default is for the active GCM module. Release OPS3.1.x Turin Networks Page 6-23

288 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Node Database Restore Guidelines If an FTP host IP address is not provided, the username, password, and path parameters are not required. The default for the path parameter is nodedb.*. The filename is optional. If a file name is not entered, the system uses the default nodedb.xxx. If services are provisioned during the backup, some services may not be captured during the backup and will, therefore, be lost when the database is restored. Turin recommends backing up the node database during a maintenance period, especially if optical cards exist on the shelf. Node Database Restore Guidelines Backup and Restore Commands The restoration process will take longer than the backup procedure; both shelf controllers (GCMs) must be rebooted to allow the new database changes to become effective. A message appears and must be confirmed before the restoration can proceed any further. The current database will be replaced with the backed up information. If more than one backup version exists on the FTP server, make sure the data from the correct file is restored. Command descriptions use the following conventions: Table 6-14 CLI Command Conventions Command Description Vertical bars ( ) separate alternative, mutually exclusive elements. You must enter one of the options as part of the command. [ ] Square brackets ([ ]) indicate optional elements. { } Braces ({ }) indicate a required choice of a command element. Boldface Italics Boldface Underlined Boldface indicates literal commands and keywords that are entered exactly as shown. Note: You can abbreviate literal commands. See the TransNav Management System GUI Guide, Section 1 Overview and Quick Reference, Chapter 1 CLI Overview, page 1-1. Italics indicate arguments for which you supply values. Boldface Underlined or underlined in parentheses (value) is a default value if you do not provide your own. Default values are set when an object (such as a service or interface) is created using the create command. Use the following CLI commands to backup and restore the node database. exec node database backup. Use the exec node database backup command to back up the Traverse node database. Page 6-24 Turin Networks Release OPS3.1.x

289 Chapter 2 Node Database Backup and Restore Backup and Restore Commands Syntax exec node database backup [host ip address user-name UserName password password [path blank][filename nodedb.xxx]] Syntax Description ip address - IP address of the FTP server where the database will be backed up user-name - username to use when accessing the FTP server password - password to use when accessing the FTP server path - enter the path on the FTP site where the database will be backed up filename - enter the file name to call the database file l exec node database restore. Use the exec node database restore command to restore the Traverse node database. Syntax exec node database restore [host ip address user-name UserName password password [path blank][filename nodedb.xxx]] Syntax Description ip address - IP address of the FTP server where the database is backed up user-name - username to use when accessing the FTP server password - password to use when accessing the FTP server path - enter the path on the FTP site from where the database will be restored filename - enter the file name of the database file Release OPS3.1.x Turin Networks Page 6-25

290 Node Operations and Maintenance Guide, Section 6: Routine Maintenance Troubleshooting Backup and Restore Troubleshooting Backup and Restore If problems occur when restoring the backup, it may be due to one of the following reasons (in the following table): Backups will fail if: An incorrect FTP server IP address is entered. Verify the FTP server IP address is correct. The directories are not provided or are incorrect in the path parameter of the CLI command. Verify the name of the directory is provided and is correct. A filename already exists with the same name as the backup file. Change the name of the file being backed up. Restorations will fail if: The node database backup file is corrupt. The Node IP address in the node database backup file is different than the system s commissioned values. The Node ID in the node database backup file is different than the system s commissioned values. Note: Do not restore a database file backed up from a different node. Newly provisioned services do not appear: If the service was provisioned while the backup was in progress, the data may not have been captured. Re-provision the service. Page 6-26 Turin Networks Release OPS3.1.x

291 SECTION 7 SOFTWARE UPGRADES SECTION 7 Contents Chapter 1 Release TR2.1.x Traverse Software Upgrade Introduction Release TR2.1.x Upgrade Overview Node Software Upgrade Flowchart (Top Level) Before You Begin Required Equipment and Tools General Traverse Shelf TransNav Management System GUI Commands and Conventions Compatibility and Guidelines General Software Compatibility Notes Traverse System SW Upgrade Compatibility Notes General Software Upgrade for TR2.1 Maintenance Releases Software Upgrade from Release 2.0.x.x to TR Software Upgrade from 1.5E to TR Software Upgrade from 1.5 to TR Guidelines for Software Upgrade Node Software Upgrade Process Pre-Software Upgrade Procedure Download Node Software to the TransNav Server Download Node Software to the TransNav Server PC System Download Node Software to the TransNav Server Solaris System Module Software Download Set-up Module Software Version Verification Software Activation Process BLSR/MS-SP Ring on GCM with Optics Software Activation Control Module Software Upgrade Activation Software Upgrade Activate (all other protected modules) Software Upgrade Activate (all unprotected modules) Spare Control Module Software Activation Spare Module Software Activation (All Other Types) Post-Software Upgrade Procedure Verify Protection Status Perform a Forced Switch Perform a Manual Switch Clear Protection Switch Software Revert Procedure Release OPS3.1.x Turin Networks Page i

292 Node Operations and Maintenance Guide, Section 7 Software Upgrades Revert Node Software Revert TransNav Management System Software Post-Remote Node Upgrade the Spare Control Module Software User- selectable FPGA Upgrade Capability Chapter 2 Release 3.0.x TE-100 System Software Upgrade Introduction Release 3.0.x Upgrade Overview Before You Begin Required Equipment and Tools General TE-100 Shelf TransNav Management System GUI Commands and Conventions Compatibility and Guidelines General Software Compatibility TE-100 Platform SW Upgrade Compatibility Notes Guidelines for Software Upgrade Node Software Upgrade Process Download Node Software to the TransNav Server Download Node Software to the TransNav Server PC System Download Node Software to the TransNav Server Solaris System Module Software Download Set-up Module Software Version Verification Software Activation Process Control Module Software Upgrade Activation Spare Control Module Software Activation Software Revert Procedure Revert Node Software Revert TransNav Management System Software List of Figures Figure 7-1 Node Software Upgrade Process Flowchart Figure 7-2 Example PC System Explorer Window File Listing Figure 7-3 Explorer Extract to Command Figure 7-4 Example File Extraction Comments Figure 7-5 SW Upgrade Dialog Box Figure 7-6 Download Time Settings Figure 7-7 SW Upgrade Download Times Figure 7-8 SW Upgrade Clear Download Time Figure 7-9 Dnld Status and Standby SW Version Fields Figure 7-10 Card Configuration Dialog Box Figure 7-11 Card Configuration GCM Protection Status Figure 7-12 SW Activation Activate Time Figure 7-13 Act Status and Current SW Ver Fields Figure 7-14 Card Configuration Protection Status Figure 7-15 SW Activation Activate Time Page ii Turin Networks Release OPS3.1.x

293 Node Operations and Maintenance Guide, Section 7 Software Upgrades Figure 7-16 Act Status and Current SW Ver Fields Figure 7-17 SW Activation Activate Time Figure 7-18 Act Status and Current SW Ver Fields Figure 7-19 SW Activation Activate Time Figure 7-20 Act Status and Current SW Ver Fields Figure 7-21 Protection Groups Dialog Box Figure 7-22 Equipment Protection Group Configuration Dialog Box Figure 7-23 Protection Groups Dialog Box Figure 7-24 Protection Group Forced Switch Figure 7-25 Confirm Force Switch Dialog Box Figure 7-26 Protection Groups Dialog Box Figure 7-27 Protection Group Manual Switch Figure 7-28 Confirm Manual Switch Dialog Box Figure 7-29 Protection Groups Dialog Box Figure 7-30 Protection Group Clear Protection Switch Figure 7-31 Confirm Release Dialog Box Figure 7-32 Service Tab Figure 7-33 User-selectable FPGA Upgrade Parameter Figure 7-34 Example PC System Explorer Window File Listing Figure 7-35 Explorer Extract to Command Figure 7-36 Example File Extraction Comments Figure 7-37 SW Upgrade Dialog Box Figure 7-38 Download Time Settings Figure Figure 7-40 SW Upgrade Clear Download Time Figure 7-41 Dnld Status and Standby SW Version Fields Figure 7-42 Card Configuration Dialog Box Figure 7-43 Card Configuration Protection Status Figure Figure List of Tables Table 7-1 Node Software Upgrade Requirements Table 7-2 TransNav GUI Command Descriptions Table 7-3 Node Software Upgrade Process Table 7-4 Pre-Software Upgrade Procedure Table 7-5 Download Node Software to the TransNav Server PC System Table 7-6 Download Node Software to the TransNav Server Solaris System Table 7-7 Module Software Download Set-up Table 7-8 Module Software Version Number Verification Table 7-9 Software Activation Process Table 7-10 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Table 7-11 Activate Software Control Module Release OPS3.1.x Turin Networks Page iii

294 Node Operations and Maintenance Guide, Section 7 Software Upgrades Table 7-12 Activate Software All Other Protected Modules Table 7-13 Activate Software All Unprotected Modules Table 7-14 Activate Software Spare Control Modules Table 7-15 Activate Software Spare Modules (All Other Types) Table 7-16 Post-Software Upgrade Procedure Table 7-17 Verify Protection Status Table 7-18 Perform a Forced Switch Table 7-19 Perform a Manual Switch Table 7-20 Clear Protection Switch Table 7-21 Deactivate Legacy Ethernet Services Table 7-22 Revert Node Software Table 7-23 Revert TransNav Management System Software Table 7-24 Post-Remote Node Upgrade Upgrade the Spare Control Module Table 7-25 Node Software Upgrade Requirements Table 7-26 TransNav GUI Command Descriptions Table 7-27 Turin Product and Software Release Compatibility Table 7-28 Node Software Upgrade Process Table 7-29 Download Node Software to the TransNav Server PC System Table 7-30 Download Node Software to the TransNav Server Solaris System Table 7-31 Module Software Download Set-up Table 7-32 Module Software Version Number Verification Table 7-33 Software Activation Process Table 7-34 Activate Software Control Module Table 7-35 Activate Software Spare Control Modules Table 7-37 Revert TransNav Management System Software Table 7-36 Revert Node Software Page iv Turin Networks Release OPS3.1.x

295 SECTION 7SOFTWARE UPGRADES Chapter 1 Release TR2.1.x Traverse Software Upgrade Introduction Release TR2.1.x Upgrade Overview Complete the TR2.1.x software upgrade of all modules in a Traverse node using the release TR2.1.x TransNav management system graphical user interface (GUI). This chapter provides the following information including step-by-step procedures on how to initiate and complete software upgrades using the TransNav GUI. Release TR2.1.x Upgrade Overview, page 7-1 Node Software Upgrade Flowchart (Top Level), page 7-2 Before You Begin, page 7-3 Required Equipment and Tools, page 7-3 TransNav Management System GUI Commands and Conventions Compatibility and Guidelines, page 7-4 Node Software Upgrade Process, page 7-7 Software Revert Procedure, page 7-44 Post-Remote Node Upgrade the Spare Control Module Software, page 7-45 User- selectable FPGA Upgrade Capability, page 7-47 Release TR2.1.x provides a unified release for the Traverse and TransNav products supporting SONET and SDH networks and services. This software release supports: Traverse in-service software upgrade to TR2.1.x from the following previous releases: 1.5.x, 1.5E.x, and 2.0.x Note: If your systems are on an earlier release (pre-1.5.x), then contact the Turin Technical Assistance Center (TAC). Point releases (as necessary) for the TR2.1.x Traverse nodes Remote upgrade capability User-selectable FPGA (Field Programmable Gate Array) upgrade capability Simultaenous TransNav Management System software management of Release 1.5.x, 1.5E.x, 2.0.x and TR2.1.x Traverse and 3.0.x TE-100 nodes to accommodate longer-term upgrade paths Release OPS3.1.x Turin Networks Page 7-1

296 Node Operations and Maintenance Guide, Section 7: Software Upgrades Node Software Upgrade Flowchart (Top Level) Node Software Upgrade Flowchart (Top Level) The diagram below shows a top-level flow for the node software upgrade process. Figure 7-1 Node Software Upgrade Process Flowchart Page 7-2 Turin Networks Release OPS3.1.x

297 Chapter 1 Release TR2.1.x Traverse Software Upgrade Required Equipment and Tools Before You Begin Review this information before you begin. Table 7-1 Node Software Upgrade Requirements Requirement Compose and have ready for the Upgrade Team a comprehensive network upgrade plan. Reference Your company s Operations Manager is responsible for this task. Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company s comprehensive upgrade plan. See Release Notes TR2.1.x ( TR21). Read through this entire chapter. Contact your company s Operations Manager. The software upgrade feature for this release supports Traverse and TransNav 1.5.x, 1.5E.x, or 2.0.x to TR2.1.x upgrades. Have the required equipment and tools ready. If you are upgrading from an earlier Traverse or TransNav software release, contact the Turin TAC. Required Equipment and Tools, page 7-3 Required Equipment and Tools The following equipment and tools are required for a Traverse system software upgrade to a node or multiple nodes in a domain: The following equipment and tools are required for a Traverse system software upgrade to a node or multiple nodes in a domain: TransNav management system server connected to a gateway Traverse node Software CD or the online Infocenter website at Note: If you do not have access to the Turin Infocenter, contact your local sales representative. The following equipment and tools are required to place modules in a Traverse shelf. General Electrostatic Discharge (ESD) wrist strap 1-slot wide blank faceplates for any empty slots to ensure EMI protection and proper cooling Traverse Shelf MPX cleaning materials to clean fiber optic cable and module MPX connectors: Isopropyl alcohol of at least 91% purity Lint free wipes Lint free cleaning swabs with urethane foam heads Release OPS3.1.x Turin Networks Page 7-3

298 Node Operations and Maintenance Guide, Section 7: Software Upgrades TransNav Management System GUI Commands and Conventions Pressurized optical duster (canned air) 1 or 2 control modules, as well as any spares System interface modules (SIMs) Note: The number and combination of SIMs is based on your network requirements and physical cabling at the Traverse main and fiber optic backplanes. TransNav Management System GUI Commands and Conventions This document provides node software upgrade procedures using the TransNav GUI. Refer to the TransNav Management System Product Overview Guide to become familiar with the TransNav system. The following conventions are used in the procedure tables. Table 7-2 TransNav GUI Command Descriptions Command Boldface Italics Description Boldface indicates dialog box, field, menu, and list names Italics indicates information you supply Compatibility and Guidelines General Software Compatibility Notes Read the compatibility topics that are relevant to your specific upgrade. General Software Compatibility Notes, page 7-4 Traverse System SW Upgrade Compatibility Notes, page 7-5 Guidelines for Software Upgrade, page 7-7 Control Modules. Each control module is partitioned and capable of holding two versions of software. The new software is downloaded onto the module s backup partition during a software upgrade. The new software is activated by the user after the software has been successfully downloaded. Software upgrade activation reboots each module and activates the back-up partition with the newly downloaded software. Provisioning data stored on the node control module is migrated to the backup partition prior to reboot. Management Software. The TransNav software simultaneously manages various node releases to accommodate longer-term upgrade paths. For a detailed product compatibility matrix, see the Product Compatibility Matrix table in the Release Notes corresponding to your upgrade release. Replacement modules. Software version numbers are broken down as follows (SW Version: ): 1st position indicates the major software release number 2nd position indicates the minor software release number 3rd position indicates the release build number 4th position indicates the software batch to build number An INCOMPATSW:Incompatible software alarm is generated when: a replacement module with a (major.x.x.x) software version lower than the compatibility ID of the Active control module the lowest software version the Active control module can work with is placed in the node. Page 7-4 Turin Networks Release OPS3.1.x

299 Chapter 1 Release TR2.1.x Traverse Software Upgrade Traverse System SW Upgrade Compatibility Notes the Active control module (major.x.x.x) software version is lower than the compatibility ID of the replacement module. the Active control module with a (major.x.x.x) software version higher than the TransNav management system can support. In these cases, use the procedures in this section to upgrade or rollback the software version on the replacement module. A SWMIS: Software version mismatch alarm is generated when a replacement module with either an earlier or later (major.minor.build.x) version of software than the software running on the control module is placed in the node. In this case, use the procedures in this section to upgrade or rollback the software version on the replacement module. Traverse System SW Upgrade Compatibility Notes Review this information to understand the important compatibility items for Traverse and TransNav software releases. General Release TN3.1.x TransNav management system software: simultaneously manages Release 1.5.x, 1.5E.x, 2.0.x and TR2.1.x Traverse nodes. manages the in-service software upgrade from Release 1.5.x, 1.5E.x, and 2.0.x to TR2.1.x, as well as, any TR2.1.x maintenance releases. manages a network of mixed nodes running Release 1.5.x, 1.5E.x, 2.0.x and TR2.1.x for functions including: Service management (provisioning, activation, deactivation, deletion, etc.) Alarms and performance monitoring (on-demand and periodic) Node and module addition and deletion Loopback External commands on protection groups The remote upgrade capability manages the arrival of older version modules and allows for remote download and activation of such modules to the TR2.1.x release. For TR2.1, line-derived timing modules (e.g., OC-3/STM-1) support only one timing reference. In pre-tr2.1 releases, line-derived timing modules would support multiple timing references. When a service provider replaces an old card with a new card, they should plan for and make the line-derived timing reference provisioning changes accordingly (i.e., move the timing references to different modules). Upon in-service replacement, the Traverse system raises and alarm and uses the timing reference of the lowest-numbered port on the module that was previously provisioned with multiple timing references, and ignores the timing provisioning for the higher-numbered ports. Legacy Ethernet and next-generation Ethernet (NGE) can interwork as per Traverse Provisioning Guide, Section 7 Configuring Ethernet, Chapter 9 Interworking Ethernet Services with Legacy Ethernet Services, page Important: If a replacement (or spare) module with Release 1.5 is inserted into a Traverse node with a software version higher than Release 1.5, the software disables the warm restart capability on all modules. Release OPS3.1.x Turin Networks Page 7-5

300 Node Operations and Maintenance Guide, Section 7: Software Upgrades Traverse System SW Upgrade Compatibility Notes Software Upgrade for TR2.1 Maintenance Releases Hitless software upgrade and warm restart are available, unless otherwise noted in the specific maintenance software Release Notes document. In-service, hitless software upgrade support is available for Release TR2.1.x and future maintenance releases. Software Upgrade from Release 2.0.x.x to TR2.1 Support for in-service software upgrade from Release 2.0.x.x to TR2.1.x for all network topologies: UPSR, BLSR, linear 1+1 chain, mesh, or combinations of these topologies. Due to FPGA updates (and other restrictions): Hitless software upgrade with warm restart is unavailable for NGE and NGE Plus (as well as, Legacy Ethernet) modules from Release TR2.0.7 to TR2.1.x. In the R , R , R , R , R2.0.5, and TR point and patch releases (and by inheritance, also in the TR2.1 point release), various modules do not support hitless software upgrade using warm restart when upgrading from Release R1.5E or R2.0.[0-6].x (i.e., pre-r , pre-r , pre-r2.0.5, or pre-tr ) to Release TR2.1. Important: See the Upgrade and Installation Notes topic in the Turin Release Notes TR2.1.x ( TR21) document for specific details. Software Upgrade from 1.5E to TR2.1 Hitless software upgrade and warm restart are available. In-service, hitless software upgrade support is available from 1.5E.x to TR2.1.x for all network topologies, including gateway configuration, SNCP and MS-SP Ring, linear MSP (including 1+1 path over dual MSP), mesh, or combinations of these topologies. Due to FPGA updates, various modules do not support hitless software upgrade using warm restart when upgrading from Release R1.5E to Release TR2.1. Important: See the Upgrade and Installation Notes topic in the Turin Release Notes TR2.1.x ( TR21) document for specific details. Software Upgrade from 1.5 to TR2.1 Hitless software upgrade and warm restart are unavailable. In-service software upgrade from 1.5.x to TR2.1.x for all network topologies: UPSR, BLSR, linear 1+1 chain, mesh, or combinations of these topologies. Page 7-6 Turin Networks Release OPS3.1.x

301 Chapter 1 Release TR2.1.x Traverse Software Upgrade Node Software Upgrade Process Guidelines for Software Upgrade Node Software Upgrade Process Review the following guidelines for software upgrade: Conduct upgrades in a specific maintenance window when you expect no user-initiated service state changes. For larger network upgrades, the entire upgrade process may span several nights. Start the upgrade from the services egress node of the network (if possible). Do not perform any new service creation, deletion, activation or deactivation (e.g., for Ethernet or End-to-End services) until you complete the upgrade on the TransNav server and all network nodes. When upgrading from a Release 1.5.x node, do not use SW Activation>WarmRbt. This feature is for upgrades from Release 1.5E.x forward only. Verify that all communication links between nodes are operational and have no loss of signal (LOS) or data communications channel (DCC) alarms. Do not change any fiber/link or other network (node, slot, port) objects during the upgrade. Due to the use of ftp libraries, bulk software downloads may fail so schedule software download to the control modules (i.e., Traverse GCM) at least 5 minutes apart. Perform an upgrade on spare modules, unless you are using the remote upgrade capability and plan to upgrade spares at a later time (see Post-Remote Node Upgrade the Spare Control Module Software, page 7-45 for details). Software upgrade is to be errorless. Release Notes TR2.1 ( TR21) defines any potential exceptions. This document is on the Turin Infocenter website at User registration is required. To register for the Turin Infocenter, contact your sales account team. Traverse and TransNav support in-service software upgrade from Release 1.5.x, 1.5E.x and 2.0.x to TR2.1.x. Depending on your requirements and current software load, you can choose either a hitless (warm restart) or a service-affecting (cold reboot) upgrade. Complete the software upgrade procedures in the following order: Table 7-3 Node Software Upgrade Process Step Procedure Reference 1 Have you read through, and do you understand, all the Before You Begin items? 2 Do you have the required equipment and tools ready? 3 Are you upgrading from Release 1.5 or 1.5E to TR2.1, and do you plan in this upgrade process to also upgrade Legacy Ethernet services to the next-generation Ethernet service model? Note: The Legacy Ethernet to Ethernet model upgrade requires pre and post steps be run to accommodate the new service model. Before You Begin, page 7-3 Required Equipment and Tools, page 7-3 Pre-Software Upgrade Procedure, page 7-9 Release OPS3.1.x Turin Networks Page 7-7

302 Node Operations and Maintenance Guide, Section 7: Software Upgrades Node Software Upgrade Process Table 7-3 Node Software Upgrade Process (continued) Step Procedure Reference 4 Upgrade the TransNav Management System server software (includes first exporting the current database off the TransNav server). Note: Do not uninstall the previous version. Mark the directory as old and remove the Icon from the desktop. Note: NETSYNC alarms occur when you start the GUI, after the server software upgrade, and before upgrading the node software. The master network objects (e.g., alarm profiles) are out of synchronization with propagated node objects. 5 Download the new node software to the TransNav server. 6 Download the software to the modules. TransNav Management System Server Guide, Section 2 Management Server Procedures, Chapter 3 Server Administration Procedures, Upgrade Server Software, page 2-33 Download Node Software to the TransNav Server, page 7-10 Module Software Download Set-up, page Activate the new software. Software Activation Process, page Are you upgrading from Release 1.5 or 1.5E to TR2.1, and do you plan in this upgrade process to also upgrade Legacy Ethernet services to the next-generation Ethernet service model? Post-Software Upgrade Procedure, page The Node Software Upgrade Process is complete. Page 7-8 Turin Networks Release OPS3.1.x

303 Chapter 1 Release TR2.1.x Traverse Software Upgrade Pre-Software Upgrade Procedure Pre-Software Upgrade Procedure Complete the following procedure before you begin the software upgrade. Table 7-4 Pre-Software Upgrade Procedure Step Procedure 1 Are you upgrading a Traverse node from Release 1.5 or 1.5E to TR2.1 and are you planning in this upgrade process to perform an upgrade of Legacy Ethernet to TR2.1 next-generation Ethernet? Note: A new next-generation Ethernet services provisioning model exists in Release 2.0. Yes. Clear Protection Switch, page Delete the corresponding Legacy Ethernet services. Note: Service recreation occurs after the software upgrade is complete. See Table 7-16 Post-Software Upgrade Procedure, page Go to the next step. No. Go to the next step. 2 Are you upgrading Traverse node from Release 1.5.x or 1.5E.x to TR2.1 and does your network have service connections where the first service using an STS on a port is a hop-by-hop service, and a subsequent STS is used by an e2e service? Important: Run the following command from the Server CLI only. (i.e., Do not use Node CLI.) Yes. (See Turin Release Notes TR2.1.x, Issue No ) Prior to software upgrade, resolve any line-level connectivity alarms (e.g., DCC FAIL, COM, NODESYNC), then refresh the end-to-end service connections by applying the following CLI command: _service exec e2e-oper command Refresh-All-E2E 3 The Pre-Software Upgrade Procedure procedure is complete. Continue to Step 4 of the Node Software Upgrade Process, page 7-7. Release OPS3.1.x Turin Networks Page 7-9

304 Node Operations and Maintenance Guide, Section 7: Software Upgrades Download Node Software to the TransNav Server Download Node Software to the TransNav Server Download Node Software to the TransNav Server PC System You must first download the node software for the upgrade from the CD or the Infocenter onto a TransNav server before proceeding with the upgrade procedures. Choose one of the following download procedures, depending on the TransNav EMS platform (i.e., PC or Solaris) for your network. The Infocenter can be accessed at User registration is required. Note: If you do not have access to the Infocenter, contact your local sales representative. Download Node Software to the TransNav Server PC System, page 7-10 Download Node Software to the TransNav Server Solaris System, page 7-11 Use this procedure to download node software to the TransNav server on a PC system. Table 7-5 Download Node Software to the TransNav Server PC System Step Procedure 1 Insert the software CD into the CD drive on the PC or navigate to the directory where the software files were previously downloaded from the Infocenter. 2 In an Explorer window, navigate to the CD drive containing the upgrade software CD or temporary download directory. Figure 7-2 Example PC System Explorer Window File Listing 3 Right-click on the flash.n.n.n.n.zip file (where n.n.n.n is the latest software release number) and select the Extract to command. Figure 7-3 Explorer Extract to Command Page 7-10 Turin Networks Release OPS3.1.x

305 Chapter 1 Release TR2.1.x Traverse Software Upgrade Download Node Software to the TransNav Server Solaris System Table 7-5 Download Node Software to the TransNav Server PC System Step Procedure 4 From the Extract dialog box, select a user-defined folder path directory (e.g., /upgrade/files), then click Extract to download the flash files into the /<user-defined>/flash directory. Important: Verify the Use folder names check box is selected to keep the./flash relative path structure in the zip file intact upon download. 5 After the file extraction is complete, the WinZip dialog box for the zip file archive remains open. Select File, then Exit to exit the dialog box. 6 The Download Node Software to the TransNav Server PC System procedure is complete. Continue to Step 6 of the Node Software Upgrade Process, page 7-7. Download Node Software to the TransNav Server Solaris System Use this procedure to download node software to the TransNav server on a Solaris (UNIX) system. Table 7-6 Download Node Software to the TransNav Server Solaris System Step Procedure 1 Open a terminal window and create a user-defined directory according to local site practices. For example: $ mkdir -p /files/node 2 Change to the directory you created in Step 1. For example: $ cd /files/node Release OPS3.1.x Turin Networks Page 7-11

306 Node Operations and Maintenance Guide, Section 7: Software Upgrades Download Node Software to the TransNav Server Solaris System Table 7-6 Download Node Software to the TransNav Server Solaris System Step Procedure 3 Type the following command to unzip the node flash software into the current directory. For example: $ unzip /cdrom/*.zip Important: This particular example assumes /cdrom is the mountpoint for the CD. Change the syntax accordingly to your local setup. The spaces, the pipe character ( ), and the dash (-) must be typed exactly as shown. Important: The user who unzips the *.zip file will have the permissions on the directory files necessary to later download to the node modules. To change permissions, contact your local UNIX administrator. 4 Eject the CD from the drive. For example: $ eject Figure 7-4 Example File Extraction Comments 5 The Download Node Software to the TransNav Server Solaris System procedure is complete. Continue to Step 6 of the Node Software Upgrade Process, page 7-7. Page 7-12 Turin Networks Release OPS3.1.x

307 Chapter 1 Release TR2.1.x Traverse Software Upgrade Module Software Download Set-up Module Software Download Set-up Software upgrades are done at the node level. The following procedure provides step-by-step instructions on how to begin a software upgrade by setting software download times for each module using the SW Upgrade dialog box. Table 7-7 Module Software Download Set-up Step Procedure 1 Verify the module software versions. Refer to Module Software Version Verification, page In Shelf View, select SW Upgrade from the Admin menu to display the SW Upgrade dialog box. Figure 7-5 SW Upgrade Dialog Box 3 Server IP Address: Enter the TransNav server IP address where the new node software version was downloaded from the software upgrade CD or the Infocenter. (For example: aaa.bbb.ccc.ddd) 4 Base Path: Enter the directory path on the TransNav server to the node software files. (For example: /files/node/flash) 5 Username: Enter the user name with File Transfer Protocol (ftp) permission access to the TransNav server where the new node software version resides. (For example: ftpusername) 6 Password: Enter the user password with ftp permission access to the TransNav server where the new node software version resides. (For example: ftppassword) 7 Click the Update button and verify that there were no errors in the ftp session. Note: This action should fill in the data for each module in the Relative Path columns. Important: The Relative Path and Upgrade Type (default to INIT) values must be set by the system before the download starts. Release OPS3.1.x Turin Networks Page 7-13

308 Node Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Table 7-7 Module Software Download Set-up (continued) Step Procedure 8 Set each Download Time based on these requirements for each module. Approximate software download times are as follows: Control module download time is approximately minutes Download time for all other modules is approximately 2 5 minutes Note: Turin recommends you set sequential download times based on the module requirements. Note: It takes a fully loaded Traverse-specific node approximately one hour to download the new software onto all modules. The time required to download software is dependent on the IP bandwidth available to the Traverse node. Download times can increase by a factor of 2 or more if there are multiple nodes using the same DCC channel for downloading software files. The software download process is completely non-service-affecting for protected modules and services. It does not require you to stand by during the download. Note: Turin recommends you download the control modules individually, three line modules at a time, and one node at a time, 7 Figure 7-6 Download Time Settings Page 7-14 Turin Networks Release OPS3.1.x

309 Chapter 1 Release TR2.1.x Traverse Software Upgrade Module Software Download Set-up Table 7-7 Module Software Download Set-up (continued) Step Procedure 9 From the Download Time drop-down box, select Set time to manually adjust the time. Select part of the time string (e.g., month, day, hour).use either the up and down arrows, or manually re-enter the time, to reset the value. 8 Figure 7-7 SW Upgrade Download Times 10 Verify that the Relative Path is set for each module. Relative Path: A literal sub-directory path (in relation to the Base Path directory) where the software resides for each module. It is based on the type of module in the slot and is case sensitive. For example: ds3. 11 Verify that the Upgrade Type is set to the default (INIT) for each module. Upgrade Type (default=init): The upgrade type for each module can be set to one of the following values: INIT (default): Completely erases the backup partition before copying the complete set of software upgrade files. MERGE: This setting is made available for special cases only when working with TAC. 12 Repeat Steps 7 through 10 for each module in the node. Release OPS3.1.x Turin Networks Page 7-15

310 Node Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Table 7-7 Module Software Download Set-up (continued) Step Procedure 13 You can Clear Download Time for any module by right-clicking the module in the SW Upgrade dialog box and clicking the Update button. If necessary, you can Abort Download to any module by right-clicking the module in the SW Upgrade dialog box. Note: Turin recommends that you not leave the module in the upgrade abort state. Clearing the download time and clicking the update button also clears the download state. 12 Figure 7-8 SW Upgrade Clear Download Time 14 Verify that the download date and times are correct. 15 The software upgrade begins based on the dates and times entered in the Download Time field. You do not have to stand by during the software download; it does not affect protected service or system performance. You can view the status of the software upgrade in the Download Status field of the SW Upgrade dialog box. The following status displays: NONE: The software download has not begun. INPROGRESS: The software download has begun, but is not complete. OK: The software download has successfully completed. ABORTED: The software download has stopped. FAILED: The software download has failed. Retry the software download. Contact the Turin s TAC, if software download fails a second time. Page 7-16 Turin Networks Release OPS3.1.x

311 Chapter 1 Release TR2.1.x Traverse Software Upgrade Module Software Download Set-up Table 7-7 Module Software Download Set-up (continued) Step Procedure 16 Continue only when the Download Status is OK and the newly downloaded software version displays in Standby SW Version field for all modules (select each module row and check the Standby SW Version field). This indicates the software download has successfully completed. 15a 15b Figure 7-9 Dnld Status and Standby SW Version Fields 17 The Module Software Download Set-up procedure is complete. Depending on the procedure where you started, return to either: Step 7 of the Node Software Upgrade Process, page 7-7 Step 3 of the Spare Module Software Activation (All Other Types), page 7-36 Release OPS3.1.x Turin Networks Page 7-17

312 Node Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Version Verification Module Software Version Verification You can determine the software version number of a module (card) using the TransNav GUI. The software version and serial number are displayed on the Config tab in Shelf View. Follow these steps to verify the software version. Table 7-8 Module Software Version Number Verification Step Procedure 1 In Shelf View, click a module to select it. 2 Click the Config tab to view current software version information. 2 Figure 7-10 Card Configuration Dialog Box 3 The software version is displayed in the Current SW Version field in the Card Configuration dialog box. Software version numbers are broken down as follows (Current SW Version: ): 1st position indicates the major software release number 2nd position indicates the minor software release number 3rd position indicates the release build number 4th position indicates the software patch to build number 4 The Module Software Version Number Verification procedure is complete. Software Activation Process The new software is not active until the software is activated and system reboots each module. The reboot loads and executes the new software, and in the case of the control module, upgrades the database. Important: Read all important notes below before beginning the activation process. Important: Software activation should start at the node farthest from the server that is connected to the headend node, then work inward. Page 7-18 Turin Networks Release OPS3.1.x

313 Chapter 1 Release TR2.1.x Traverse Software Upgrade Software Activation Process WARNING! For TR2.1 upgrades from x through to and including , Turin recommends reversing the order of GCM activation (i.e., activate the active GCM first, then the standby GCM). (Issues No ) Important: The software upgrade activate process is considered service-affecting unless all services are protected. Therefore, Turin recommends that activation be scheduled/completed one module at a time. This requires you to observe the reboot process and set the activate time for each module after the previous module reboot is complete. Check the Alarms dialog box to verify that the equipment alarm, caused by the reboot, has cleared before setting the activate time for the next module. Important: Any unprotected traffic residing on an Enhanced GCM (EGCM) with Optics module will experience an outage until the EGCM is restored from activation. Important: Warm reboot is not available for Legacy Ethernet modules. Important: During software activation, the modules automatically reboot. Do not execute any external commands on the modules during software activation. Important: If you are upgrading a BLSR/MS-SP Ring network without GCMs with Optics, make sure to perform a lockout on the span before activating the line module. Once the line modules for the span on both nodes have been activated, release the force switch. Perform this on each span in the BLSR/MS-SP Ring network. Table 7-9 Software Activation Process Step Procedure Reference 1 Did you complete the Pre-Software Upgrade Procedure? 2 Did you complete the upgrade of TransNav EMS server and client software and download the node software to the TransNav server? 3 Did you download the node software to the TransNav server? Pre-Software Upgrade Procedure, page 7-9 Section 2 Management Server Procedures, Chapter 1 Server Administration Procedures, Upgrade Server Software, page 2-13 Download Node Software to the TransNav Server, page 7-10 Release OPS3.1.x Turin Networks Page 7-19

314 Node Operations and Maintenance Guide, Section 7: Software Upgrades Software Activation Process Table 7-9 Software Activation Process (continued) Step Procedure Reference 4 Is the module software download complete? Module Software Download Set-up, page Do you have your network nodes in a BLSR/MS-SP Ring network with Traverse Enhanced GCMs with Optics? Important: For any Release x through to and including , Turin recommends reversing the order of GCM activation (i.e., activate the active GCM first, then the standby GCM). Activate software for all modules set up in a BLSR/MS-SP Ring protection group. See BLSR/MS-SP Ring on GCM with Optics Software Activation, page 7-21 Continue to Step 7 of this process to software upgrade activate all other protected modules. 6 Activate software for: Standby GCM Spare (standby) GCM(s), unless you are using the remote upgrade feature and want to upgrade your spare modules at a later time (see page 7-45) Active GCM Important: For any Release x through to and including , Turin recommends reversing the order of GCM activation (i.e., activate the active GCM first, then standby GCM). 7 Activate software for all modules set up in a protection group. 8 Activate software for all unprotected modules. 9 Activate software for all other types of spare modules, unless you are using the remote upgrade capability and want to upgrade your spare modules at a later time. Control Module Software Upgrade Activation, page 7-25 Software Upgrade Activate (all other protected modules), page 7-30 Software Upgrade Activate (all unprotected modules), page 7-33 Spare Module Software Activation (All Other Types), page The Software Activation Process is complete. Continue to Step 8 of the Node Software Upgrade Process, page 7-7. Page 7-20 Turin Networks Release OPS3.1.x

315 Chapter 1 Release TR2.1.x Traverse Software Upgrade BLSR/MS-SP Ring on GCM with Optics Software Activation BLSR/MS-SP Ring on GCM with Optics Software Activation The new software is not active until the software is activated and system reboots each module. The reboot loads and executes the new software, and in the case of the control module, upgrades the database. Important: The following procedure applies to Traverse nodes only. Important: Do not start the Activate Software BLSR/MS-SP Ring GCM with Optic Modules procedure until the downloaded software version displays indicating that the software download has successfully completed. The software version displays in the SW Activation dialog box, Standby SW Ver field for all modules. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Activation dialog box. Follow these step-by-step instructions to set up software upgrade activation for GCMs with Optics in a BLSR/MS-SP Ring. Table 7-10 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 1 Verify the network is alarm free or validate and record any alarms present prior to activation. 2 In Shelf View, select a GCM with Optics module and click the Config tab. 3 Verify Active/Standby GCM with Optics Protection Status using the Card Configuration dialog box. 3 Figure 7-11 Card Configuration GCM Protection Status 4 Execute a BLSR/MS-SP Ring Forced Switch on the standby GCM with Optics module following the procedure in Table 7-18 Perform a Forced Switch, page Check the BLSR/MS-SP Ring state and verify that Force is issued on the near- and far-end. Release OPS3.1.x Turin Networks Page 7-21

316 Node Operations and Maintenance Guide, Section 7: Software Upgrades BLSR/MS-SP Ring on GCM with Optics Software Activation Table 7-10 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 5 Click the standby GCM with Optics Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. 6 Figure 7-12 SW Activation Activate Time 6 Select the activation type Act Type (default=nsa). Service Affecting (SA) is required for standby GCM with Optics module activation. Valid values are: NSA (non-service-affecting): Default. Will not activate an active node GCM. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Only use this option in the instance where the standby and active control modules have already been upgraded and activated. 7 Select to warm reboot (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TR2.1 table in the Release Notes TR2.1 ( TR21). 8 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-47 for details about this paramter. Note: Although the user-selectable FPGA upgrade capability is available to avoid FPGA updates that are deemed to be non-critical to your network, Turin does still recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network. 9 Click Update. Page 7-22 Turin Networks Release OPS3.1.x

317 Chapter 1 Release TR2.1.x Traverse Software Upgrade BLSR/MS-SP Ring on GCM with Optics Software Activation Table 7-10 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 10 View the status of the software activation in the Act Status field of the SW Upgrade dialog box. The following status displays: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry software activation. Contact the Turin (TAC), if software activation fails a second time. Important: The activation status will show INPROGRESS, and then NONE until the module has completed the upgrade, then it will show OK. This is normal behavior. 11 Verify that the new software version activation is complete and it displays in the SW Activation dialog box, Current SW Ver field Figure 7-13 Act Status and Current SW Ver Fields 12 With the standby GCM with Optics selected in Shelf View, select the Alarms tab and check the Alarms dialog box to verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. 13 A SWMIS: Software version mismatch alarm is generated since the standby GCM with Optics software version is now mismatched with the active GCM with Optics. This is normal behavior. 14 If you have spare GCM with Optic modules to software upgrade at this time (i.e., you are not using the remote upgrade capability), remove the standby GCM with Optics module from the shelf and install the spare GCM with Optics. Complete the Spare Control Module Software Activation, page 7-35 procedure. 15 Clear the near-end Forced Switch using the procedure in Table 7-20 Clear Protection Switch, page Verify that the BLSR/MS-SP Ring has returned to normal operation. If not, intialize the BLSR/MS-SP Ring. 16 Execute a BLSR/MS-SP Ring Forced Switch on the active GCM with Optics module following the procedure in Table 7-18 Perform a Forced Switch, page Check the BLSR/MS-SP Ring state and verify that Force is issued on the near- and far-end. Release OPS3.1.x Turin Networks Page 7-23

318 Node Operations and Maintenance Guide, Section 7: Software Upgrades BLSR/MS-SP Ring on GCM with Optics Software Activation Table 7-10 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 17 Click the active GCM with Optics module Activate Time field in the SW Activation dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. Note: You can clear the Activation Time for any module by right-clicking the module in the SW Activation dialog box and selecting Clear Activation Time from the shortcut menu. 18 Select the activation type Act Type (default=nsa). Service Affecting (SA) is required for standby GCM with Optics module activation. Valid values are: NSA (non-service-affecting): Default. Will not reboot (activate) an active node GCM. SA (service-affecting): Will activate and reboot the node GCM regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Only use this option in the instance where the standby and active control modules have already been upgraded and activated. 19 Select to warm reboot (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TR2.1 table in the Release Notes TR2.1 ( TR21). 20 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-47 for details about this paramter. Note: Although the user-selectable FPGA upgrade capability is available to avoid FPGA updates that are deemed to be non-critical to your network, Turin does still recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network. 21 Click Update. 22 Verify that the new software version activation is complete and it is displayed in the SW Activation dialog box, Current SW Ver field. Note: Activating the active GCM causes the new software to upgrade and a switchover to the protection module. 23 With the now standby (previously active) GCM with Optics module selected in Shelf View, select the Alarms tab and check the Alarms dialog box to verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. Page 7-24 Turin Networks Release OPS3.1.x

319 Chapter 1 Release TR2.1.x Traverse Software Upgrade Control Module Software Upgrade Activation Table 7-10 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 24 The SWMIS: Software version mismatch alarm generated on the previously standby GCM with Optics clears as both GCM with Optics software versions now match. However, this alarm is now generated for all other modules in the system as their software versions are now mismatched with the active GCM with Optics. This is normal behavior. 25 Clear the near-end Forced Switch using the procedure in Table 7-20 Clear Protection Switch, page Verify that the BLSR/MS-SP Ring has returned to normal operation. 26 The Activate Software BLSR/MS-SP Ring GCM with Optic Modules procedure is complete. Return back to Step 5 of the Software Activation Process, page Control Module Software Upgrade Activation The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software on the control module at each node. Important: Do not start the Activate Software Control Module procedure until the downloaded software version displays, indicating that the software download has completed successfully. The software version displays in the SW Activation dialog box, Standby SW Ver field for all modules. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Activation dialog box. Follow these step-by-step instructions to set up software upgrade activation for node GCMs. Table 7-11 Activate Software Control Module Step Procedure 1 Verify the network is alarm free or validate and record any alarms present prior to activation. 2 In Shelf View, select a control module and click the Config tab. Release OPS3.1.x Turin Networks Page 7-25

320 Node Operations and Maintenance Guide, Section 7: Software Upgrades Control Module Software Upgrade Activation Table 7-11 Activate Software Control Module (continued) Step Procedure 3 Verify the Protection Status of the Active/Standby control module using the Card Configuration dialog box. 3 Figure 7-14 Card Configuration Protection Status 4 Click the standby control module Activate Time field in the SW Activation dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. 4 Figure 7-15 SW Activation Activate Time 5 Select the activation type Act Type (default=nsa). Change to SA for standby control module activation. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control module. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Only use this option in the instance where the standby and active control modules have already been upgraded and activated. Page 7-26 Turin Networks Release OPS3.1.x

321 Chapter 1 Release TR2.1.x Traverse Software Upgrade Control Module Software Upgrade Activation Table 7-11 Activate Software Control Module (continued) Step Procedure 6 If the module does not require a cold restart, then select to warm restart (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TR2.1 table in the Release Notes TR2.1 ( TR21). 7 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-47 for details about this paramter. Note: Although the user-selectable FPGA upgrade capability is available to avoid FPGA updates that are deemed to be non-critical to your network, Turin does still recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network. 8 Click Update. 9 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following status displays: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Turin (TAC) if the software activation fails a second time. Important: The activation status will show INPROGRESS, and then NONE until the module has completed the upgrade, then it will show OK. This is normal behavior. 10 Verify that the new software version activation is complete and it displays in the SW Activation dialog box, Current SW Ver field. Important: If there are any unexpected discrepancies here, STOP and contact the Turin (TAC) Figure 7-16 Act Status and Current SW Ver Fields 11 With the standby control module selected in Shelf View, select the Alarms tab and check the Alarms dialog box to verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. Release OPS3.1.x Turin Networks Page 7-27

322 Node Operations and Maintenance Guide, Section 7: Software Upgrades Control Module Software Upgrade Activation Table 7-11 Activate Software Control Module (continued) Step Procedure 12 A SWMIS: Software version mismatch alarm is generated since the standby control module software version is now mismatched with the active control module. This is normal behavior. 13 If you have spare control modules to software upgrade at this time (i.e., you are not using the Remote Upgrade feature), remove the standby control module from the shelf and install the spare (standby) control module. Complete the Spare Control Module Software Activation, page 7-35 procedure. 14 If the control modules contain integrated VTX/VCX modules in a protection group (e.g., GCM with VTX/VCX), then perform a Manual switch on the active module (module with the old software) to change its state to standby. Refer to the Perform a Manual Switch procedure on page 7-40 for details. Note: The manual protection switch on certain modules is necessary due to FPGA changes. 15cm. aman After the manual switch is complete, repeat Steps 3 through 12, for the now standby module (module with the old software) of the protection group. 16 Release (clear) the protection switch after activation is complete on the standby module to return it to its original active status. Refer to the Clear Protection Switch procedure on page 7-41 for details. 17 Click the active control module Activate Time field in the SW Activation dialog box to display the current date and time. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. Note: Clear the Activation Time for any module by right-clicking the module in the SW Activation dialog box and selecting Clear Activation Time from the shortcut menu. 18 Act Type (default=nsa). Select SA (service-affecting) activation type for the active control module. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control module. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Only use this option in the instance where the standby and active control modules have already been upgraded and activated. Page 7-28 Turin Networks Release OPS3.1.x

323 Chapter 1 Release TR2.1.x Traverse Software Upgrade Control Module Software Upgrade Activation Table 7-11 Activate Software Control Module (continued) Step Procedure 19 Select to warm reboot (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TR2.1 table in the Release Notes TR2.1 ( TR21). 20 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-47 for details about this paramter. Note: Although the user-selectable FPGA upgrade capability is available to avoid FPGA updates that are deemed to be non-critical to your network, Turin does still recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network. 21 Click Update. 22 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following status types display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Turin (TAC) if the software activation fails a second time. Important: The activation status will show INPROGRESS, and then NONE until the module has completed the upgrade, then it will show OK. This is normal behavior. 23 Verify that the new software version activation is complete and it is displayed in the SW Activation dialog box, Current SW Ver field. Note: Activating the active control module causes the new software to upgrade and a switchover to the protection module. 24 With the now standby (previously active) control module selected in Shelf View, select the Alarms tab and check the Alarms dialog box to verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. 25 The SWMIS: Software version mismatch alarm generated on the previously standby control module clears as both control module software versions now match. However, this alarm is now generated for all other modules in the system as their software versions are now mismatched with the active control module. This is normal behavior. 26 The Activate Software Control Module procedure is complete. Continue to Step 7 of the Software Activation Process, page Release OPS3.1.x Turin Networks Page 7-29

324 Node Operations and Maintenance Guide, Section 7: Software Upgrades Software Upgrade Activate (all other protected modules) Software Upgrade Activate (all other protected modules) Follow these step-by-step instructions to set up software upgrade activation for all other protected modules. Important: Upgrade the entire protection group first before continuing to the next protection group. Table 7-12 Activate Software All Other Protected Modules Step Procedure 1 Proceed with software upgrade activation for other protected modules after the software activation has successfully completed on both the control modules (Act Status=OK) and any service-affecting alarms on the node are cleared. Software upgrade activation on other protected modules must be performed in the following order for all modules set up in a protection group: Set the Activate Time so the standby module activates first. If a cold reboot activation was used, after the activation (activate software and reboot) has successfully completed, perform a manual switch on the active module to change its state to standby. Set the Activate Time for the active module. Release the protection switch. 2 Verify and record the standby/active status for modules/ports set up in a protection group. Refer to the Verify Protection Status procedure on page 7-37 for more details. 3 Click the standby module Activate Time field to display the current date and time. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. 3 Figure 7-17 SW Activation Activate Time Page 7-30 Turin Networks Release OPS3.1.x

325 Chapter 1 Release TR2.1.x Traverse Software Upgrade Software Upgrade Activate (all other protected modules) Table 7-12 Activate Software All Other Protected Modules (continued) Step Procedure 4 Select the activation type Act Type to SA for the module. Valid types are: NSA (non-service-affecting): Default. Will not activate a module if it has any active services. SA (service-affecting): Activates the software and reboots the module regardless of any services. 5 If the module does not require a cold restart, then select to warm restart (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TR2.1 table in the Release Notes TR2.1 ( TR21). 6 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-47 for details about this paramter. Note: Although the user-selectable FPGA upgrade capability is available to avoid FPGA updates that are deemed to be non-critical to your network, Turin does still recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network. 7 Click Update. 8 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following statuses display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Turin (TAC) if the software activation fails a second time. 9 Verify that the new software version is displayed in SW Activation dialog box, Current SW Ver field. 8 9 Figure 7-18 Act Status and Current SW Ver Fields Release OPS3.1.x Turin Networks Page 7-31

326 Node Operations and Maintenance Guide, Section 7: Software Upgrades Software Upgrade Activate (all other protected modules) Table 7-12 Activate Software All Other Protected Modules (continued) Step Procedure 10 With the standby module selected in Shelf View, check the Alarms dialog box to verify the following alarms have cleared: EQFAIL (equipment failure): caused by the reboot. SWMIS (software mismatch): caused by a software version mismatch with the active control module. 11 If the modules contain integrated VTX/VCX modules in a protection group, then perform a Manual Switch on the active module (module with the old software) to change its state to standby. Refer to the Perform a Manual Switch procedure on page 7-40 for details. Note: The manual protection switch on certain modules is necessary due to FPGA changes. 12 After the manual switch is complete, repeat Steps 3 through 10, for the now standby module (module with the old software) of the protection group. 13 Release (clear) the protection switch after activation is complete on the standby module to return it to its original active status. Refer to the Clear Protection Switch procedure on page 7-41 for details. 14 Repeat Steps 2 through 13 for the next protection group. 15 The Activate Software All Other Protected Modules procedure is complete. Continue to Step 8 of the Software Activation Process, page Page 7-32 Turin Networks Release OPS3.1.x

327 Chapter 1 Release TR2.1.x Traverse Software Upgrade Software Upgrade Activate (all unprotected modules) Software Upgrade Activate (all unprotected modules) Use the following step-by-step instructions to set up software upgrade activation for all unprotected modules: Table 7-13 Activate Software All Unprotected Modules Step Procedure 1 Proceed with software upgrade activation on all unprotected modules after the software activation has successfully completed (Act Status=OK) on both the control modules, on all other protected modules, then clear any service-affecting alarms on the node. 2 Click the unprotected module Activate Time field to display the current date and time. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. 2 Figure 7-19 SW Activation Activate Time 3 Select the activation type Act Type and set to SA for the module. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control module. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. 4 If the module does not require a cold restart, then select to warm restart (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TR2.1 table in the Release Notes TR2.1 ( TR21). 5 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-47 for details about this paramter. Note: Although the user-selectable FPGA upgrade capability is available to avoid FPGA updates that are deemed to be non-critical to your network, Turin does still recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network. 6 Click Update. Release OPS3.1.x Turin Networks Page 7-33

328 Node Operations and Maintenance Guide, Section 7: Software Upgrades Software Upgrade Activate (all unprotected modules) Table 7-13 Activate Software All Unprotected Modules (continued) Step Procedure 7 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following status types display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Turin (TAC) if software activation fails a second time. 8 Verify that the new software version displays in SW Activation dialog box, Current SW Ver field. 7 8 Figure 7-20 Act Status and Current SW Ver Fields 9 With the unprotected module selected in Shelf View, check the Alarms dialog box to verify the following alarms have cleared: EQFAIL (equipment failure): Caused by the reboot. SWMIS (software mismatch): Caused by a software version mismatch with the active control module. 10 Repeat Steps 2 through 9 for all unprotected modules. 11 Verify that the network is alarm free, or validate and record any alarms present prior to the upgrade. 12 Verify the restoration of all the services. 13 The Activate Software All Unprotected Modules procedure is complete. Depending on the procedure from which you came, continue to either: Step 9 of the Software Activation Process, page 7-20 Step 4 of the Spare Module Software Activation (All Other Types), page 7-36 Page 7-34 Turin Networks Release OPS3.1.x

329 Chapter 1 Release TR2.1.x Traverse Software Upgrade Spare Control Module Software Activation Spare Control Module Software Activation The new software is not active until the system activates the software and reboots the spare (standby) control module. The reboot loads and executes the new software. Important: This procedure assumes you have completed upgrading the standby control module and have not yet activated the active control module. Important: A spare control module can only be upgraded in a shelf that has the same type of control module. For example, if the standby Traverse GCM is a GCM with OC-48 module, you can only upgrade GCM with OC-48 modules in this procedure. Also, if the standby TE-100 System module is an OC-48 module, you can only upgrade with another OC-48 system module. The activation is scheduled for each module at the node based on the date and time entered in the Activate Time field of the SW Activation dialog box. Follow these step-by-step instructions to set up software upgrade activation for spare control modules. Table 7-14 Activate Software Spare Control Modules Step Procedure 1 Remove the upgraded standby control module by restarting the module through the TransNav management system, then removing the module from the shelf. 2 Insert the spare (standby) control module. 3 Once the spare control module is online and the EQRMV/EQCOMM alarms are clear, download the new software version to the module using the Table 7-7 Module Software Download Set-up, page 7-13 procedure. 4 Once the new software downloads to the spare control module, activate the software using the steps described for the standby control module in the Table 7-11 Activate Software Control Module, page 7-25 procedure. 5 Repeat Steps 1 through 4 for each spare control module. 6 Once the upgrade and activation is complete for all the spare control modules you can either: Leave the last spare in place to act as the new standby module. Place the original standby control module back into the standby slot and continue the procedure to activate software on the active control module. 7 The Activate Software Spare Control Modules procedure is complete. Depending on the procedure from which you came, continue to either: Step 15 of the procedure BLSR/MS-SP Ring on GCM with Optics Software Activation, page 7-23 Step 13 of the procedure Control Module Software Upgrade Activation, page 7-28 Release OPS3.1.x Turin Networks Page 7-35

330 Node Operations and Maintenance Guide, Section 7: Software Upgrades Spare Module Software Activation (All Other Types) Spare Module Software Activation (All Other Types) The new software is not active until the system activates the software and reboots the spare modules (that are not control modules). The reboot loads and executes the new software. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Activation dialog box. Use the following step-by-step instructions to set up the software upgrade activation for the spare modules. Table 7-15 Activate Software Spare Modules (All Other Types) Step Procedure 1 Insert the spare module in an unused slot in the shelf that has an empty slot to both the left and the right of the spare module. 2 Once the spare module is online and the EQRMV/EQCOMM alarms are clear, download the new software version to the module using the Module Software Download Set-up, page 7-13 procedure. 3 Once the new software downloads to the spare module, activate the software using the steps described in the Software Upgrade Activate (all other protected modules), page 7-30 procedure. 4 Repeat Steps 1 through 3 for each spare module. 5 The Activate Software Spare Modules (All Other Types) procedure is complete. Continue to Step 10 of the Software Activation Process, page Post-Software Upgrade Procedure Complete the following post-software upgrade procedure. Table 7-16 Post-Software Upgrade Procedure Step Procedure 1 Are you upgrading from Release 1.5 or 1.5E.x to Release TR2.1? Do you plan in this upgrade process to also upgrade Legacy Ethernet services to the next-generation Ethernet service model? If so, did you delete Legacy Ethernet services in the Pre-Software Upgrade Procedure? Yes. Recreate these services using the new next-generation Ethernet software model. Refer to Traverse Provisioning Guide. Refer to Traverse Provisioning Guide, Section 7 Configuring Ethernet, Chapter 1 Configuring Ethernet Overview, page 7-1. Go to the next step. No. Stop. Go to Step 3. Page 7-36 Turin Networks Release OPS3.1.x

331 Chapter 1 Release TR2.1.x Traverse Software Upgrade Verify Protection Status Table 7-16 Post-Software Upgrade Procedure (continued) Step Procedure 2 Verify activation of the newly created (next-generation) Ethernet services. 3 The Post-Software Upgrade Procedure procedure is complete. Continue to Step 9 of the Node Software Upgrade Process, page 1-8. Verify Protection Status Follow these step-by-step instructions to verify the protection status (Standby or Active) of a module/port in a protection group: Table 7-17 Verify Protection Status Step Procedure 1 From Map View, double-click on a node to display the Shelf View. 2 Click the Protection tab to display the Protection Groups dialog box. 2 3 Select the protection group. Figure 7-21 Protection Groups Dialog Box 4 Click Edit to display the Protection Group Configuration dialog box. Release OPS3.1.x Turin Networks Page 7-37

332 Node Operations and Maintenance Guide, Section 7: Software Upgrades Perform a Forced Switch Table 7-17 Verify Protection Status (continued) Step Procedure 5 The status displays in the Protection field - either Active or Standby. 5 Figure 7-22 Equipment Protection Group Configuration Dialog Box 6 The Verify Protection Status procedure is complete. Continue to Step 3 of the Software Upgrade Activate (all other protected modules), page Perform a Forced Switch Use the following step-by-step instructions to perform a user-initiated forced protection switch. Table 7-18 Perform a Forced Switch Step Procedure 1 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 1 2 Select the protection group. Figure 7-23 Protection Groups Dialog Box 3 Click Edit to display the Protection Group Configuration dialog box. Page 7-38 Turin Networks Release OPS3.1.x

333 Chapter 1 Release TR2.1.x Traverse Software Upgrade Perform a Forced Switch Table 7-18 Perform a Forced Switch (continued) Step Procedure 4 Right-click the module or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Forced from the shortcut menu. 4 Figure 7-24 Protection Group Forced Switch 5 The Confirm Force Switch dialog box displays. Click Yes to confirm. Figure 7-25 Confirm Force Switch Dialog Box 6 Check the Alarms dialog box to verify the EQFAIL: equipment failure alarm (caused by the forced protection switch) has cleared. 7 The active module or port is switched to standby. 8 The Perform a Forced Switch procedure is complete. If you were in the procedure BLSR/MS-SP Ring on GCM with Optics Software Activation to activate the: standby module, then return to Step 4. active module, then return to Step 16. Release OPS3.1.x Turin Networks Page 7-39

334 Node Operations and Maintenance Guide, Section 7: Software Upgrades Perform a Manual Switch Perform a Manual Switch For modules in a protection group, requiring a cold restart activation due to FPGA changes, a manual protection switch is necessary. Follow these step-by-step instructions to perform a manual protection switch to switch the active module (with the old software) from the active to the standby state. Note: This procedure is required for cold restart activation only. Table 7-19 Perform a Manual Switch Step Procedure 1 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 1 2 Select the protection group. Figure 7-26 Protection Groups Dialog Box 3 Click Edit to display the Protection Group Configuration dialog box. 4 Right-click the module or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Manual from the shortcut menu. 4 Figure 7-27 Protection Group Manual Switch 5 The Confirm Manual Switch dialog box displays. Click Yes to confirm. Figure 7-28 Confirm Manual Switch Dialog Box Page 7-40 Turin Networks Release OPS3.1.x

335 Chapter 1 Release TR2.1.x Traverse Software Upgrade Clear Protection Switch Table 7-19 Perform a Manual Switch (continued) Step Procedure 6 Check the Alarms dialog box to verify the EQFAIL: equipment failure alarm (caused by the forced protection switch) has cleared. 7 The active module or port is switched to standby. 8 The Perform a Manual Switch procedure is complete. If you were in the procedure: Control Module Software Upgrade Activation, then return to Step 15. Software Upgrade Activate (all other protected modules), then return to Step 12. Clear Protection Switch Use the following step-by-step instructions to clear (release) a user-initiated protection switch. Table 7-20 Clear Protection Switch Step Procedure 1 From Map View, double-click on a node to display the Shelf View. 2 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 2 3 Select the protection group. Figure 7-29 Protection Groups Dialog Box 4 Click Edit to display the Protection Group Creation dialog box. Release OPS3.1.x Turin Networks Page 7-41

336 Node Operations and Maintenance Guide, Section 7: Software Upgrades Clear Protection Switch Table 7-20 Clear Protection Switch (continued) Step Procedure 5 Right-click the Standby module/port in the Protection Group Creation dialog box to display a shortcut menu. Select Clear from the shortcut menu. 5 Figure 7-30 Protection Group Clear Protection Switch 6 The Confirm Release dialog box displays. Click Yes to confirm the force switch release. Figure 7-31 Confirm Release Dialog Box 7 Check the Alarms dialog box to verify that the EQFAIL: equipment failure alarm (caused by the protection switch release) has cleared. 8 The standby module or port is switched back to its original active status. 9 The Clear Protection Switch procedure is complete. If you were in the procedure: BLSR/MS-SP Ring on GCM with Optics Software Activation to activate the: standby module, then return to Step 15. active module, then return to Step 25. Software Upgrade Activate (all other protected modules), then return to Step 14. Page 7-42 Turin Networks Release OPS3.1.x

337 Chapter 1 Release TR2.1.x Traverse Software Upgrade Clear Protection Switch Deactivate Legacy Ethernet Services Follow these step-by-step instructions to deactivate services on a Legacy Ethernet module. Table 7-21 Deactivate Legacy Ethernet Services Step Procedure 1 From Map View, click the Service tab to display the services screen. 1 Figure 7-32 Service Tab 2 Click one or more of the table rows to select all related service(s) on the Legacy Ethernet module. To select more than one table row, hold down the Ctrl key when selecting the table rows. 3 Click Deactivate for the selected Ethernet services to stop carrying traffic. 4 The Deactivate Legacy Ethernet Services procedure is complete. Release OPS3.1.x Turin Networks Page 7-43

338 Node Operations and Maintenance Guide, Section 7: Software Upgrades Software Revert Procedure Software Revert Procedure Use the following procedures to revert to a previous software version used on the node and TransNav management system. Revert Node Software, page 7-44 Revert TransNav Management System Software, page 7-45 Revert Node Software Important: This procedure is service affecting. Important: Turin recommends that if you expect to revert an entire node, call TAC for assistance. Table 7-22 Revert Node Software Step Procedure 1 Connect to the node using the Node CLI. 2 Perform the software revert command on every module (card) that has been upgraded to the desired software load. Execute this command in the following module order: Line modules, one at a time Standby control module (e.g., GCM) Active control module CLI command sequence: For modules 1 to n (in the order described above): begin exec upgrade switch-to-stdby-load slot <slot#> Are you sure you want to execute this command? YES. end exec node restart Are you sure you want to execute this command? YES. 3 Verify the node software level has been revised to the desired version and that the system is running the desired software load. 4 The Revert Node Software procedure is complete. Page 7-44 Turin Networks Release OPS3.1.x

339 Chapter 1 Release TR2.1.x Traverse Software Upgrade Post-Remote Node Upgrade the Spare Control Module Software Revert TransNav Management System Software Table 7-23 Revert TransNav Management System Software Step Procedure 1 Stop the upgraded TransNav server. 2 Start the previous version of software on the TransNav server. 3 Open the previous software version of the Client GUI. Verify the nodes and services are correct, i.e., nodesync/com are cleared. 4 The Revert TransNav Management System Software procedure is complete. Post-Remote Node Upgrade the Spare Control Module Software If you initially used the remote upgrade capability to upgrade the software version on your network nodes, the software on your spare modules likely needs to still be upgraded. The following procedure gives step-by-step instructions to perform this function. The new software is not active until the system reboots the spare (standby) control module (i.e., Traverse GCM or TE-100 System module). The reboot activates the backup partition with the newly downloaded software on the spare control module. Important: A spare control module can only be upgraded in a shelf that has the same type of control module. For example, if the standby Traverse GCM is a GCM with OC-48 module, you can only upgrade GCM with OC-48 modules in this procedure. Similarly, if the standby TE-100 System module is an OC-48 module, you can only upgrade with another OC-48 system module. The activation is set based on the date and time entered in the Activate Time field of the SW Activation dialog box. Use these step-by-step instructions to set up software upgrade activation for spare control modules in the case where the other modules on the node have already been upgraded. Table 7-24 Post-Remote Node Upgrade Upgrade the Spare Control Module Step Procedure 1 Remove the previously upgraded standby control module by first restarting the module through the TransNav management system using a cold reboot, then removing the module from the shelf. 2 Insert the spare (standby) control module. Release OPS3.1.x Turin Networks Page 7-45

340 Node Operations and Maintenance Guide, Section 7: Software Upgrades Post-Remote Node Upgrade the Spare Control Module Software Table 7-24 Post-Remote Node Upgrade Upgrade the Spare Control Module Step Procedure 3 Important: Once the spare control module is online, the following alarms generate: EQRMV and EQCOMM. From this point, you have up to 30 minutes to complete the download and activation process. The versions and other data will be invalid until the upgrade is complete. 4 Download the desired software version to the spare control module using the procedure in Table 7-7 Module Software Download Set-up, page When the desired software is loaded onto the spare control module, activate the software using the steps described for the standby control module in the procedure described in Table 7-11 Activate Software Control Module, page You must change the value in the ActType field to SPARE. Note: After the upgrade, the EQRMV and EQCOMM alarms clear. 6 Repeat Steps 1 through 4 for each spare control module. 7 Once the upgrade and activation is complete for all the spare control modules you can either: Leave the last spare in place to act as the new standby module. Place the original standby control module back into the standby slot and continue the procedure to activate software on the active control module. 8 The Post-Remote Node Upgrade Upgrade the Spare Control Module procedure is complete. Page 7-46 Turin Networks Release OPS3.1.x

341 Chapter 1 Release TR2.1.x Traverse Software Upgrade User- selectable FPGA Upgrade Capability Userselectable FPGA Upgrade Capability In some cases, upgrading from one release to another requires a new FPGA image for a module or set of modules. Accepting this new FPGA image can resolve an issue that is unique to a certain deployment. The user-selectable FPGA upgrade capability (force warm reboot) gives you the choice to not ignore the FPGA module software change because it is non-critical in nature to your deployment. This capability allows the upgrade to proceed in a hitless fashion, without loading the new FPGA image. From the SW Activation dialog box, if you select to ignore the new FPGA image, and the existing FPGA image remains compatible with the new FPGA image, the system performs a force warm upgrade for the module. Figure 7-33 User-selectable FPGA Upgrade Parameter Release OPS3.1.x Turin Networks Page 7-47

342 Node Operations and Maintenance Guide, Section 7: Software Upgrades User- selectable FPGA Upgrade Capability Page 7-48 Turin Networks Release OPS3.1.x

343 SECTION 7SOFTWARE UPGRADES Chapter 2 Release 3.0.x TE-100 System Software Upgrade Introduction Release 3.0.x Upgrade Overview Complete the Release 3.0.x software upgrade of all TraverseEdge 100 (TE-100) modules using the Release 3.0.x TransNav management system graphical user interface (GUI). This chapter provides the following information including step-by-step procedures on how to initiate and complete software upgrades using the TransNav GUI. Release 3.0.x Upgrade Overview, page 7-49 Before You Begin, page 7-50 Required Equipment and Tools, page 7-50 TransNav Management System GUI Commands and Conventions, page 7-51 Compatibility and Guidelines, page 7-51 Node Software Upgrade Process, page 7-54 Software Revert Procedure, page 7-66 Release 3.0 provides a unified release for the TE-100 product supporting SONET or SDH networks and services. This software release supports: TE-100 software upgrade from Release 2.0.x to Release 3.0.x not an in-service upgrade In-service software upgrade 3.0.x point releases (as necessary) for TE-100 nodes 1 TE-100 warm reboot and hitless upgrade features are unavailable TransNav in-service software upgrade from Release 1.5.x, 1.5E.x, and 2.0.x to Release 3.0.x Simultaneous Release 3.0.x TransNav management system node software management to accommodate longer-term upgrade paths: Release 1.5.x, 1.5E.x, and 2.0.x Traverse nodes Release 3.0.x TE-100 nodes 1 TE-100 warm reboot and hitless upgrade features are planned for a future release. Release OPS3.1.x Turin Networks Page 7-49

344 Node Operations and Maintenance Guide, Section 7: Software Upgrades Before You Begin Before You Begin Review this information before you begin. Table 7-25 Node Software Upgrade Requirements Requirement Compose and have ready for the Upgrade Team a comprehensive network upgrade plan. Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company s comprehensive upgrade plan. The software upgrade feature for this release supports TransNav Release 1.5, 1.5E, and 2.0 to 3.0 upgrades. Have the required equipment and tools ready. Reference Your company s Operations Manager is responsible for this task. Refer to Release Notes 3.0.x ( ). Read through this entire chapter. Contact your company s Operations Manager. If you are upgrading from an earlier TransNav software release, contact the Turin Technical Assistance Center. Required Equipment and Tools, page 7-50 Required Equipment and Tools The following equipment and tools are required for a TE-100 system software upgrade to a node or multiple nodes in a domain: TransNav management system server connected to a TE-100 node or gateway Traverse node. Software CD or the Infocenter website ( Note: If you do not have access to the Infocenter website, contact your local sales representative. the Infocenter websitethe following equipment and tools are required to place modules in a TE-100 shelf. General Electrostatic Discharge (ESD) wrist strap. 1-slot wide blank faceplates are required in any empty slots to ensure EMI protection and proper cooling. TE-100 Shelf 1 or 2 System modules (and any spares) Page 7-50 Turin Networks Release OPS3.1.x

345 Chapter 2 Release 3.0.x TE-100 System Software Upgrade General Software Compatibility TransNav Management System GUI Commands and Conventions This document provides node software upgrade procedures using the TransNav GUI. Refer to the TransNav Management System Product Overview Guide to become familiar with the TransNav system. The following conventions are used in the procedure tables. Table 7-26 TransNav GUI Command Descriptions Command Boldface Italics Description Boldface indicates dialog box, field, menu, and list names Italics indicates information you supply Compatibility and Guidelines Read the compatibility topics that are relevant to your specific upgrade. General Software Compatibility, page 7-51 TE-100 Platform SW Upgrade Compatibility Notes, page 7-53 Guidelines for Software Upgrade, page 7-53 General Software Compatibility Control Modules. Each control module is partitioned and capable of holding two versions of software. The new software is downloaded onto the module s backup partition during a software upgrade. The new software is activated by the user after the software has been successfully downloaded. Software upgrade activation reboots each module and activates the back-up partition with the newly downloaded software. Provisioning data stored on the node control module is migrated to the backup partition prior to reboot. Management Software. The TransNav software simultaneously manages various node releases to accommodate longer-term upgrade paths. For a detailed product compatibility matrix, see the Product Compatibility Matrix table in the Release Notes corresponding to your upgrade release. Replacement modules. Software version numbers are broken down as follows (SW Version: ): 1st position indicates the major software release number 2nd position indicates the minor software release number 3rd position indicates the release build number 4th position indicates the software batch to build number An INCOMPATSW:Incompatible software alarm is generated when: a replacement module with a (major.x.x.x) software version lower than the compatibility ID of the Active control module the lowest software version the Active control module can work with is placed in the node. the Active control module (major.x.x.x) software version is lower than the compatibility ID of the replacement module. the Active control module with a (major.x.x.x) software version higher than the TransNav management system can support. In these cases, use the procedures in this section to upgrade or rollback the software version on the replacement module. A SWMIS: Software version mismatch alarm is generated when a replacement module with either an earlier or later (major.minor.build.x) version of software than the software running on the control module is placed in the node. In this case, Release OPS3.1.x Turin Networks Page 7-51

346 Node Operations and Maintenance Guide, Section 7: Software Upgrades General Software Compatibility use the procedures in this section to upgrade or rollback the software version on the replacement module. Page 7-52 Turin Networks Release OPS3.1.x

347 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Guidelines for Software Upgrade TE-100 Platform SW Upgrade Compatibility Notes Review this information to understand the important compatibility items for the TE-100 and TransNav 3.0.x software release. TE-100 software upgrade from Release 2.0.x to Release 3.0.x. This is not an in-service upgrade. TransNav in-service software upgrade from Release 1.5.x, 1.5E.x, and 2.0.x to Release 3.0.x. In-service 3.0.x point release software upgrades (as necessary) for TE-100 nodes. TransNav manages the in-service software upgrade for Release 3.0.x maintenance releases. TE-100 hitless upgrade and warm reboot features are unavailable in this release. This table shows compatible product and software release groups. Table 7-27 Turin Product and Software Release Compatibility TE-100 Release 3.0 Traverse Release 2.0 TE x Traverse 2.0.x TE x TransNav 3.0.x manages: Traverse 2.0.x, 1.5E.x, 1.5x TE x TransAccess 200 Mux 9.0 TE x Traverse 2.0.x TE x TransNav 2.0.x manages: Traverse 2.0.x, 1.5E.x, 1.5x, 1.4E.x, 1.4.x TE x TransAccess 200 Mux 8.1 alarms TransAccess 200 Mux 9.0 TransAccess 200 Mux 8.1 Guidelines for Software Upgrade Review the following guidelines for software upgrade: Conduct upgrades in a specific maintenance window when you expect no user-initiated service state changes. Start the upgrade from the services egress node of the network (if possible). Do not perform any new service creation, deletion, activation or deactivation (e.g., for Ethernet) until you complete the upgrade on the TransNav server and all network nodes. Do not change any fiber/link or other network (node, slot, port) objects during the upgrade. Due to the use of ftp libraries, bulk software downloads may fail so schedule software download to the TE-100 System modules at least 5 minutes apart. Perform an upgrade on spare modules. Software upgrade is to be errorless. Release Notes 3.0.x ( ) define any potential exceptions. Release OPS3.1.x Turin Networks Page 7-53

348 Node Operations and Maintenance Guide, Section 7: Software Upgrades Node Software Upgrade Process Node Software Upgrade Process Complete the software upgrade procedures in the following order: Table 7-28 Node Software Upgrade Process Step Procedure Reference 1 Have you read through, and do you understand, all of the Before You Begin items? 2 Do you have the required equipment and tools ready? 3 Upgrade the TransNav management system server software (includes first exporting the current database off the TransNav server). Note: Do not uninstall the previous software version. Mark the directory as old and remove the Icon from the desktop. 4 Download the new node software to the TransNav server. 5 Download the software to the modules. Before You Begin, page 7-50 Required Equipment and Tools, page 7-50 TransNav Management System Server Guide, Section 2 Management Server Procedures, Chapter 3 Server Administration Procedures, Upgrade Server Software, page 2-33 Download Node Software to the TransNav Server, page 7-54 Module Software Download Set-up, page Activate the new software. Software Activation Process, page The Node Software Upgrade Process is complete. Download Node Software to the TransNav Server You must first download the node software for the upgrade from the CD or the Infocenter onto a TransNav server before proceeding with the upgrade procedures. Choose one of the following download procedures, depending on the TransNav EMS platform (i.e., PC or Solaris) for your network. The Infocenter can be accessed at User registration is required. Note: If you do not have access to the Infocenter, contact your local sales representative. Download Node Software to the TransNav Server PC System, page 7-55 Download Node Software to the TransNav Server Solaris System, page 7-56 Page 7-54 Turin Networks Release OPS3.1.x

349 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Download Node Software to the TransNav Server PC System Download Node Software to the TransNav Server PC System Use this procedure to download node software to the TransNav server on a PC system. Table 7-29 Download Node Software to the TransNav Server PC System Step Procedure 1 Insert the software CD into the CD drive on the PC or navigate to the directory where the software files were previously downloaded from the Infocenter. 2 In an Explorer window, navigate to the CD drive containing the upgrade software CD or temporary download directory. Figure 7-34 Example PC System Explorer Window File Listing 3 Right-click on the flash.n.n.n.n.zip file (where n.n.n.n is the latest software release number) and select the Extract to command. Figure 7-35 Explorer Extract to Command Release OPS3.1.x Turin Networks Page 7-55

350 Node Operations and Maintenance Guide, Section 7: Software Upgrades Download Node Software to the TransNav Server Solaris System Table 7-29 Download Node Software to the TransNav Server PC System Step Procedure 4 From the Extract dialog box, select a user-defined folder path directory (e.g., /upgrade/files), then click Extract to download the flash files into the /<user-defined>/flash directory. Important: Verify the Use folder names check box is selected to keep the./flash relative path structure in the zip file intact upon download. 5 After the file extraction is complete, the WinZip dialog box for the zip file archive remains open. Select File, then Exit to exit the dialog box. 6 The Download Node Software to the TransNav Server PC System procedure is complete. Continue to Step 5 of the Node Software Upgrade Process, page 7-7. Download Node Software to the TransNav Server Solaris System Use this procedure to download node software to the TransNav server on a Solaris (UNIX) system. Table 7-30 Download Node Software to the TransNav Server Solaris System Step Procedure 1 Open a terminal window and create a user-defined directory according to local site practices. For example: $ mkdir -p /files/node 2 Change to the directory you created in Step 1. For example: $ cd /files/node Page 7-56 Turin Networks Release OPS3.1.x

351 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Download Node Software to the TransNav Server Solaris System Table 7-30 Download Node Software to the TransNav Server Solaris System Step Procedure 3 Type the following command to unzip the node flash software into the current directory. For example: $ unzip /cdrom/*.zip Important: This particular example assumes /cdrom is the mountpoint for the CD. Change the syntax accordingly to your local setup. The spaces, the pipe character ( ), and the dash (-) must be typed exactly as shown. Important: The user who unzips the *.zip file will have the permissions on the directory files necessary to later download to the node modules. To change permissions, contact your local UNIX administrator. Figure 7-36 Example File Extraction Comments 4 Eject the CD from the drive. For example: $ eject 5 The Download Node Software to the TransNav Server Solaris System procedure is complete. Continue to Step 5 of the Node Software Upgrade Process, page 7-7. Release OPS3.1.x Turin Networks Page 7-57

352 Node Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Module Software Download Set-up Software upgrades are done at the node level. The following procedure provides step-by-step instructions on how to begin a software upgrade by setting software download times for each module using the SW Upgrade dialog box. Table 7-31 Module Software Download Set-up Step Procedure 1 Verify the module software versions. Refer to Module Software Download Set-up, page In Shelf View, select SW Upgrade from the Admin menu to display the SW Upgrade dialog box. Figure 7-37 SW Upgrade Dialog Box 3 Server IP Address: Enter the TransNav server IP address where the new node software version was downloaded from the software upgrade CD or the Infocenter. (For example: aaa.bbb.ccc.ddd) 4 Base Path: Enter the directory path on the TransNav server to the node software files. (For example: /files/node/flash) 5 Username: Enter the user name with File Transfer Protocol (ftp) permission access to the TransNav server where the new node software version resides. (For example: ftpusername) 6 Password: Enter the user password with ftp permission access to the TransNav server where the new node software version resides. (For example: ftppassword) 7 Click the Update button and verify that there were no errors in the ftp session. Note: This action should fill in the data for each module in the Relative Path columns. Important: The Relative Path and Upgrade Type (default to INIT) values must be set by the system before the download starts. Page 7-58 Turin Networks Release OPS3.1.x

353 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Module Software Download Set-up Table 7-31 Module Software Download Set-up (continued) Step Procedure 8 Set each Download Time based on these requirements for each module. Approximate software download times are as follows: Control module download time is approximately minutes Download time for all other modules is approximately 2 5 minutes Note: Turin recommends you set sequential download times based on the module requirements. 7 Figure 7-38 Download Time Settings 9 From the Download Time drop-down box, select Set time to manually adjust the time. Select part of the time string (e.g., month, day, hour).use either the up and down arrows, or manually re-enter the time, to reset the value. Figure Verify that the Relative Path is set for each module. Relative Path: A literal sub-directory path (in relation to the Base Path directory) where the software resides for each module. It is based on the type of module in the slot and is case sensitive. For example: ds3. 11 Verify that the Upgrade Type is set to the default (INIT) for each module. Upgrade Type (default=init): The upgrade type for each module can be set to one of the following values: INIT (default): Completely erases the backup partition before copying the complete set of software upgrade files. MERGE: This setting is made available for special cases only when working with TAC. 12 Repeat Steps 7 through 10 for each module in the node. Release OPS3.1.x Turin Networks Page 7-59

354 Node Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Table 7-31 Module Software Download Set-up (continued) Step Procedure 13 You can Clear Download Time for any module by right-clicking the module in the SW Upgrade dialog box and clicking the Update button. If necessary, you can Abort Download to any module by right-clicking the module in the SW Upgrade dialog box. Turin recommends that you not leave the module in the upgrade abort state. Clearing the download time and clicking the update button also clears the download state. 12 Figure 7-40 SW Upgrade Clear Download Time 14 Verify that the download date and times are correct. 15 The software upgrade begins based on the dates and times entered in the Download Time field. You do not have to stand by during the software download; it does not affect protected service or system performance. You can view the status of the software upgrade in the Download Status field of the SW Upgrade dialog box. The following status displays: NONE: The software download has not begun. INPROGRESS: The software download has begun, but is not complete. OK: The software download has successfully completed. ABORTED: The software download has stopped. FAILED: The software download has failed. Retry the software download. Contact the Turin s TAC, if software download fails a second time. 16 Continue only when the Download Status is OK and the newly downloaded software version displays in Standby SW Version field for all modules (select each module row and check the Standby SW Version field). This indicates the software download has successfully completed. 15a 15b Figure 7-41 Dnld Status and Standby SW Version Fields 17 The Module Software Download Set-up procedure is complete. Return to Step 6 of the Node Software Upgrade Process, page 7-7. Page 7-60 Turin Networks Release OPS3.1.x

355 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Software Activation Process Module Software Version Verification You can determine the software version number of a module (card) using the TransNav GUI. The software version and serial number are displayed on the Config tab in Shelf View. Follow these steps to verify the software version. Table 7-32 Module Software Version Number Verification Step Procedure 1 In Shelf View, click a module to select it. 2 Click the Config tab to view current software version information. 2 Figure 7-42 Card Configuration Dialog Box 3 The software version is displayed in the Current SW Version field in the Card Configuration dialog box. Software version numbers are broken down as follows (Current SW Version: ): 1st position indicates the major software release number 2nd position indicates the minor software release number 3rd position indicates the release build number 4th position indicates the software patch to build number 4 The Module Software Version Number Verification procedure is complete. Software Activation Process The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software. Important: Read all important notes below before beginning the activation process. Important: Software activation should start at the node farthest from the server that is connected to the headend node, then work inward. Release OPS3.1.x Turin Networks Page 7-61

356 Node Operations and Maintenance Guide, Section 7: Software Upgrades Control Module Software Upgrade Activation Important: During software activation, the modules automatically reboot. Do not execute any external commands on the modules during software activation. Table 7-33 Software Activation Process Step Procedure Reference 1 Did you complete the upgrade of TransNav EMS server and client software and download the node software to the TransNav server? 2 Did you download the node software to the TransNav server? 3 Is the module software download complete? 4 Activate software for: Standby control module Spare (standby) control module(s) Active control module Section 2 Management Server Procedures, Chapter 1 Server Administration Procedures, Upgrade Server Software, page 2-13 Download Node Software to the TransNav Server, page 7-54 Module Software Download Set-up, page 7-58 Control Module Software Upgrade Activation, page The Software Activation Process is complete. Continue to Step 7 of the Node Software Upgrade Process, page Control Module Software Upgrade Activation The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software on the control module. Important: Do not start the Activate Software Control Module procedure until the downloaded software version displays in the SW Upgrade dialog box, Standby SW Ver field for all modules, indicating the software download has successfully completed. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for control modules. Table 7-34 Activate Software Control Module Step Procedure 1 Verify the network is alarm free or validate and record any alarms present prior to activation. 2 In Shelf View, select a control module and click the Config tab. Page 7-62 Turin Networks Release OPS3.1.x

357 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Control Module Software Upgrade Activation Table 7-34 Activate Software Control Module (continued) Step Procedure 3 Verify the Protection Status of the Active/Standby control module using the Card Configuration dialog box. 3 Figure 7-43 Card Configuration Protection Status 4 Click the standby control module Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. Figure Change the activation type Act Type (default=nsa) to SA for standby control module activation. Valid values are: NSA (non-service-affecting). Default. Indicates the activation type will not reboot (activate) an active control module. SA (service-affecting): Indicates the activation type will reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Indicates the activation type will reboot the spare (standby) control module. 6 Click Update. 7 Important: View the status of the software activation in the Act Status field of the SW Upgrade dialog box. The following status types display: NON: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Turin Technical Assistance Center if the software activation fails a second time. 8 Verify that the new software version activation is complete and it is displayed in the SW Upgrade dialog box, Current SW Ver field. Important: If there are any unexpected discrepancies here, STOP. Contact the Turin Technical Assistance Center. Figure With the standby control module selected in Shelf View, select the Alarms tab and check the Alarms dialog box to verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. Release OPS3.1.x Turin Networks Page 7-63

358 Node Operations and Maintenance Guide, Section 7: Software Upgrades Control Module Software Upgrade Activation Table 7-34 Activate Software Control Module (continued) Step Procedure 10 A SWMIS: Software version mismatch alarm is generated since the standby control module software version is now mismatched with the active control module. This is normal behavior. 11 If you have spare control modules to software upgrade at this time (i.e., you are not using the remote upgrade capability), remove the standby control module from the shelf and install the spare (standby) control module. Complete the Spare Control Module Software Activation, page 7-65 procedure. 12 Click the active control module Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time; or select the date, time, hour, or minute fields and then re-enter. Note: You can clear the Activation Time for any module by right-clicking the module in the SW Upgrade dialog box and selecting Clear Activation Time from the shortcut menu. 13 Change the activation type Act Type (default=nsa) to SA for standby control module activation. Valid values are: NSA (non-service-affecting). Default. Indicates the activation type will not reboot (activate) an active control module. SA (service-affecting): Indicates the activation type will reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Indicates the activation type will reboot the spare (standby) control module. 14 Click Update. 15 Important: View the status of the software activation in the Act Status field of the SW Upgrade dialog box. The following status types display: NON: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Turin Technical Assistance Center if the software activation fails a second time. 16 Verify that the new software version activation is complete and it is displayed in the SW Upgrade dialog box, Current SW Ver field. Note: Activating the active control module causes the new software to upgrade and a switchover to the protection module. Page 7-64 Turin Networks Release OPS3.1.x

359 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Spare Control Module Software Activation Table 7-34 Activate Software Control Module (continued) Step Procedure 17 With the now standby (previously active) control module selected in Shelf View, select the Alarms tab and check the Alarms dialog box to verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. 18 The SWMIS: Software version mismatch alarm generated on the previously standby control module clears as both control module software versions now match. However, this alarm is now generated for all other modules in the system as their software versions are now mismatched with the active control module. This is normal behavior. 19 The Activate Software Control Module procedure is complete. Continue to Step 5 of the Software Activation Process, page Spare Control Module Software Activation The new software is not active until the system reboots the spare (standby) control module. The reboot activates the backup partition with the newly downloaded software on the spare control module. Important: This procedure assumes you have completed upgrading the standby control module and have not yet activated the active control module. Important: A spare control module can only be upgraded in a shelf that has the same type of control module. For example, if the standby TE-100 System module is an OC-48 module, you can only upgrade with another OC-48 system module. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for spare control modules. Table 7-35 Activate Software Spare Control Modules Step Procedure 1 Remove the upgraded standby control module by restarting the module through the TransNav management system, then removing the module from the shelf. 2 Insert the spare (standby) control module. 3 Once the spare control module is online and the EQRMV and EQCOMM alarms are clear, download the new software version to the module using the Table 7-31 Module Software Download Set-up, page 7-58 procedure. Release OPS3.1.x Turin Networks Page 7-65

360 Node Operations and Maintenance Guide, Section 7: Software Upgrades Software Revert Procedure Table 7-35 Activate Software Spare Control Modules (continued) Step Procedure 4 Once the new software downloads to the spare control module, activate the software using the steps described for the standby control module in the Table 7-34 Activate Software Control Module, page 7-62 procedure (using ActType=SPARE). 5 Repeat Steps 1 through 4 for each spare control module. 6 Once upgrade and activation is complete for all the spare control modules, place the original standby control module back into the standby slot and continue the procedure to activate software on the active control module. 7 The Activate Software Spare Control Modules procedure is complete. Continue to Step 12 of the procedure Control Module Software Upgrade Activation, page Software Revert Procedure Use the following procedures to revert to a previous software version used on the node and TransNav management system. Revert Node Software, page 7-66 Revert TransNav Management System Software, page 7-67 Revert Node Software Important: This procedure is service affecting. Important: Turin recommends that if you expect to revert an entire node, call TAC for assistance. Page 7-66 Turin Networks Release OPS3.1.x

361 Chapter 2 Release 3.0.x TE-100 System Software Upgrade Software Revert Procedure Table 7-36 Revert Node Software Step Procedure 1 Connect to the node using the Node CLI. 2 Perform the software revert command on every module (card) that has been upgraded to the desired software load. Execute this command in the following module order: Line modules, one at a time Standby control module (e.g., GCM) Active control module CLI command sequence: For modules 1 to n (in the order described above): begin exec upgrade switch-to-stdby-load slot <slot#> Are you sure you want to execute this command? YES. end exec node restart Are you sure you want to execute this command? YES. 3 Verify the node software level has been revised to the desired version and that the system is running the desired software load. 4 The Revert Node Software procedure is complete. Revert TransNav Management System Software Table 7-37 Revert TransNav Management System Software Step Procedure 1 Stop the upgraded TransNav server. 2 Start the previous version of software on the TransNav server. 3 Open the previous software version of the Client GUI. Verify the nodes and services are correct, i.e., nodesync/com are cleared. 4 The Revert TransNav Management System Software procedure is complete. Release OPS3.1.x Turin Networks Page 7-67

362 Node Operations and Maintenance Guide, Section 7: Software Upgrades Software Revert Procedure Page 7-68 Turin Networks Release OPS3.1.x

363 SECTION 8 HARDWARE UPGRADES SECTION 8 Contents Chapter 1 Replacing Existing Traverse Hardware Introduction Modules Fan Equipment Software Compatibility Software Version Verification Electrostatic Discharge Protection Required Equipment and Tools General Traverse Shelf Replacement Module Type and Software Version Preparing a Module for Removal and Replacement Remove a Module Module Placement GCM Module Replacement as Standby LED Indicators Clean Fiber Optic MPX Connectors Insert a Replacement Module Replace the Front Inlet Fan Tray Module Front Inlet Fan Tray Air Filter Installation Replace the Traverse 600 Fan Assembly Fan Assembly Air Filter Installation (Traverse 600) Replace the Fan Tray Module (legacy) Fan Tray Air Filter Installation (legacy) Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray Introduction Precautions and Assumptions Required Equipment and Tools FIFT Upgrade Instructions Check the New Fan Module List of Figures Figure 8-1 Card Configuration Dialog Box Figure 8-2 Equipment Mismatch Alarm Figure 8-3 Module Tabs in the Unlocked Position Figure 8-4 Fiber Optic Backplane Housing A and B Release OPS3.1.x Turin Networks Page i

364 Node Operations and Maintenance Guide, Section 8 Hardware Upgrades Figure 8-5 Traverse 600 Fiber Optic Backplane Housing A and B Figure 8-6 Optical Module MPX Connector Figure 8-7 Module Locking Tabs in the Unlocked Position Figure 8-8 Traverse 1600 or Traverse 2000 Shelf with Guides Figure 8-9 Traverse 600 Shelf with Guides Figure 8-10 Module Tabs in the Locked Position Figure 8-11 Front Inlet Fan Module Captive Fasteners Figure 8-12 Front Inlet Air Filter Figure 8-13 Fan Assembly Front Cover - Traverse Figure 8-14 Traverse 600 Fan Assembly Installation Figure 8-15 Traverse 600 Fan Assembly Air Filter Figure 8-16 Fan Tray Holder Front Cover Figure 8-17 Traverse 1600 Fan Tray Module Installation Figure 8-18 Traverse 2000 Fan Tray Module Installation Figure 8-19 Air Filter with Springs Figure 8-20 Fan Tray Holder Front Cover Figure 8-21 Air Filter with Handle Figure 8-22 Fan Tray Holder Front Cover Figure 8-23 Existing Fan Tray Holder Back Panel List of Tables Table 8-1 Module Software Version Number Verification Table 8-2 Preparing a Module for Removal and Replacement Table 8-3 Remove a Module Table 8-4 Module Placement Guidelines Table 8-5 Redundancy Rules for GCM Types Table 8-6 Power and Active/Standby All Modules Table 8-7 Clean Cable and Module MPX Connectors Table 8-8 Insert a Module Table 8-9 Insert a Front Inlet Fan Module Table 8-10 Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000) Table 8-11 Insert a Fan Module with Integral Fan Tray Table 8-12 Insert a Fan Assembly Air Filter (Traverse 600) Table 8-13 Insert a Fan Tray Module Table 8-14 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) Table 8-15 Fan Tray Air Filter (with handle) Installation Table 8-16 Front Inlet Fan Tray Holder Upgrade Instructions Table 8-17 New Fan Module Check Page ii Turin Networks Release OPS3.1.x

365 Node Operations and Maintenance Guide, Section 8 Hardware Upgrades Release OPS3.1.x Turin Networks Page iii

366 Node Operations and Maintenance Guide, Section 8 Hardware Upgrades Page iv Turin Networks Release OPS3.1.x

367 SECTION 8HARDWARE UPGRADES Chapter 1 Replacing Existing Traverse Hardware Introduction During the course of normal operation, various conditions may arise that require network operations personnel to replace existing system equipment. This section describes Traverse module and fan equipment replacement. Modules All modules in the Traverse system, including the General Control Modules (GCMs), are hot-swappable and can be removed and replaced while the system is in operation. During replacement procedures, service is interrupted to all connections on the removed modules. For related information about adding and removing modules using the TransNav GUI, see the TransNav Management System GUI Guide, Section 3 Network, Chapter 1 Creating and Deleting Equipment Using Preprovisioning. The module replacement topics in this chapter are as follows: Software Compatibility, page 8-2 Software Version Verification, page 8-4 Electrostatic Discharge Protection, page 8-5 Required Equipment and Tools, page 8-5 Replacement Module Type and Software Version, page 8-5 Preparing a Module for Removal and Replacement, page 8-7 Remove a Module, page 8-9 Module Placement, page 8-10 GCM Module Replacement as Standby LED Indicators, page 8-15 Clean Fiber Optic MPX Connectors, page 8-16 Insert a Replacement Module, page 8-20 Fan Equipment The fan module and fan air filter can be removed and replaced while the system is in operation. For general fan assembly information, see the Traverse Product Overview Guide, Section 2 Platform Descriptions, Chapter 4 Fan Assemblies, page Release OPS3.1.x Turin Networks Page 8-1

368 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Software Compatibility The fan equipment replacement topics are as follows: Section 8 Hardware Upgrades, Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray, page 8-37 Replace the Front Inlet Fan Tray Module, page 8-24 Front Inlet Fan Tray Air Filter Installation, page 8-25 Replace the Traverse 600 Fan Assembly, page 8-26 Fan Assembly Air Filter Installation (Traverse 600), page 8-28 Replace the Fan Tray Module (legacy), page 8-29 Fan Tray Air Filter Installation (legacy), page 8-32 Software Compatibility Control Modules. Each control module is partitioned and capable of holding two versions of software. The new software is downloaded onto the module s backup partition during a software upgrade. The new software is activated by the user after the software has been successfully downloaded. Software upgrade activation reboots each module and activates the back-up partition with the newly downloaded software. Provisioning data stored on the node control module is migrated to the backup partition prior to reboot. Management Software. The TransNav software simultaneously manages various node releases to accommodate longer-term upgrade paths. For a detailed product compatibility matrix, see the Product Compatibility Matrix table in the Release Notes corresponding to your upgrade release. Replacement modules. Software version numbers are broken down as follows (SW Version: ): 1st position indicates the major software release number 2nd position indicates the minor software release number 3rd position indicates the release build number 4th position indicates the software batch to build number An INCOMPATSW:Incompatible software alarm is generated when: a replacement module with a (major.x.x.x) software version lower than the compatibility ID of the Active control module the lowest software version the Active control module can work with is placed in the node. the Active control module (major.x.x.x) software version is lower than the compatibility ID of the replacement module. the Active control module with a (major.x.x.x) software version higher than the TransNav management system can support. In these cases, use the procedures in this section to upgrade or rollback the software version on the replacement module. A SWMIS: Software version mismatch alarm is generated when a replacement module with either an earlier or later (major.minor.build.x) version of software than the software running on the control module is placed in the node. In this case, use the procedures in this section to upgrade or rollback the software version on the replacement module. Refer to Section 7 Software Upgrades, Chapter 1 Release TR2.1.x Traverse Software Upgrade for software upgrade procedures. Page 8-2 Turin Networks Release OPS3.1.x

369 Chapter 1 Replacing Existing Traverse Hardware Software Compatibility Release OPS3.1.x Turin Networks Page 8-3

370 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Software Version Verification Software Version Verification You can determine the software version number of a module (card) using the TransNav GUI. The software version and serial number are displayed on the Config tab in Shelf View. Follow these steps to verify the software version. Table 8-1 Module Software Version Number Verification Step Procedure 1 In Shelf View, click a module to select it. 2 Click the Config tab to view current software version information. 2 Figure 8-1 Card Configuration Dialog Box 3 The software version is displayed in the Current SW Version field in the Card Configuration dialog box. Software version numbers are broken down as follows (Current SW Version: ): 1st position indicates the major software release number 2nd position indicates the minor software release number 3rd position indicates the release build number 4th position indicates the software patch to build number 4 The Module Software Version Number Verification procedure is complete. Page 8-4 Turin Networks Release OPS3.1.x

371 Chapter 1 Replacing Existing Traverse Hardware Replacement Module Type and Software Version Electrostatic Discharge Protection Required Equipment and Tools A properly grounded Electrostatic Discharge (ESD) wrist strap must be worn during the following installation and maintenance activities to avoid damage to any Traverse integrated circuits: While handling any Traverse module When connecting copper or optical cables to the PDAP, Traverse main backplane, fiber optic backplane, and fan tray module The following equipment and tools are required to place modules in a Traverse shelf. General Electrostatic Discharge (ESD) wrist strap 1-slot wide blank faceplates for any empty slots to ensure EMI protection and proper cooling Traverse Shelf MPX cleaning materials to clean fiber optic cable and module MPX connectors: Isopropyl alcohol of at least 91% purity Lint free wipes Lint free cleaning swabs with urethane foam heads Pressurized optical duster (canned air) 1 or 2 control modules, as well as any spares System interface modules (SIMs) Note: The number and combination of SIMs is based on your network requirements and physical cabling at the Traverse main and fiber optic backplanes. Replacement Module Type and Software Version Module of Same Type and Software Version. When you replace a module with another of the same type and software version, the TransNav management system configures the replacement module in the same way the removed module was configured. Module of Same Type with a Earlier or Later Software Version. Replacement modules that have an earlier version of software earlier than the other modules in the Traverse node will require a software upgrade. Replacement modules that have a later version of software later than the other modules in the Traverse node will require a software downgrade. Refer to Section 7 Software Upgrades, Chapter 1 Release TR2.1.x Traverse Software Upgrade for procedures on how to convert software versions on a replacement module. Release OPS3.1.x Turin Networks Page 8-5

372 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Replacement Module Type and Software Version Module of Different Type. If you replace a module with a different type of module, an Equipment Mismatch alarm is generated indicating a failure condition. In the following Map View, the Alarm tab provides an example of an Equipment Mismatch alarm in the TransNav GUI: Figure 8-2 Equipment Mismatch Alarm Page 8-6 Turin Networks Release OPS3.1.x

373 Chapter 1 Replacing Existing Traverse Hardware Preparing a Module for Removal and Replacement Preparing a Module for Removal and Replacement The following procedures provide step-by-step instructions on how to prepare a module for removal and replacement using the TransNav GUI. Important: GCM, Enhanced GCM (EGCM), Universal GCM (UGCM), and GCMs with integrated optics are considered different modules and must be physically removed and deleted via TransNav prior to replacement with a different GCM module type to avoid an EQMIS: Equipment Mismatch alarm. Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older GCM modules with the newer GCM modules in a redundant configuration. The following replacement rules apply: Replace: GCM with a UGCM EGCM (without optics) with a UGCM EGCM (with OC-12/STM-4) with a UGCM with 1-port OC-12/STM-4 EGCM (with OC-48/STM-16) with a UGCM with OC-48/STM-16 Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older DS3, E3, EC-1, and DS3 Transmux modules with the newer DS3, E3, EC-1, and DS3 Transmux modules with no greater than 50 ms traffic interruption for each module in any 1:N (where N=1,2) protection group. Table 8-2 Preparing a Module for Removal and Replacement Step Procedure 1 In the TransNav GUI, go to Shelf View. 2 Click the module to be removed. 3 Click the Config tab to display the Card Configuration dialog box. 4 Click the Lock icon at the bottom left portion of the screen to change the Administrative state to locked and click Apply. Note: Turin recommends a forced switchover if you are replacing the working module of a protection group. 5 Physically remove the module from the Traverse shelf. Refer to the procedure Remove a Module, page 8-9 for details. You must physically remove the old module from the shelf before deleting it using the TransNav GUI. The TransNav system will continue to discover the module if it is not physically removed from the shelf. Release OPS3.1.x Turin Networks Page 8-7

374 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Preparing a Module for Removal and Replacement Table 8-2 Preparing a Module for Removal and Replacement (continued) Step Procedure 6 In the TransNav GUI, right-click the module and select Delete Card to delete the card or Replace with Card to replace with a different type of module. 7 Place the new module in the Traverse shelf. Refer to the following sequence of topics for important details: Module Placement, page 8-10 GCM Module Replacement as Standby LED Indicators, page 8-15 (Standby GCM module replacement only.) Clean Fiber Optic MPX Connectors, page 8-16 Insert a Replacement Module, page Click the Lock icon at the bottom left portion of the screen to change the Administrative state to unlock and click Apply. 9 The Preparing a Module for Removal and Replacement procedure is complete. Page 8-8 Turin Networks Release OPS3.1.x

375 Chapter 1 Replacing Existing Traverse Hardware Remove a Module Remove a Module Follow these step-by-step instructions to remove a module. Important: A properly grounded ESD wrist strap must be worn at all times while handling Traverse modules to prevent damage to the circuitry. Important: Handle modules by the edges and face plate only. Do not touch any module connectors or components. Table 8-3 Remove a Module Step Procedure 1 Flip the locking tabs up to unlock the module. Locking Tabs in Open Position Figure 8-3 Module Tabs in the Unlocked Position 2 Hold the module with the tabs parallel to the top and bottom of the module and pull it straight out of the slot. 3 The Remove a Module procedure is complete. Release OPS3.1.x Turin Networks Page 8-9

376 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Module Placement Module Placement The following restrictions apply for module placement in a Traverse shelf. Refer to Appendix A Module Placement Planning and Guidelines, page 9-1 for additional information. Table 8-4 Module Placement Guidelines Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) GCM GCM Enhanced GCM with OC-12/STM-4 GCM with OC-48/STM-16 GCM with VTX GCM with OC-12/STM-4 plus VTX GCM with OC-48/STM-16 plus VTX GCMA and GCMB (slots 15 and 16) GCMA and GCMB (slots 19 and 20) GCMA and GCMB (slots 5 and 6) Redundant GCMs are recommended for equipment protection. However, if only one GCM is used, it can be placed in either slot GCMA or GCMB. Redundant GCMs can be different types. See Table 8-5 Redundancy Rules for GCM Types for a list of control modules. DS1 DS3/E3/EC-1 CC (12-port) DS3/E3/EC-1 CC (24-port) DS3/EC-1 Transmux E Important: Do not place an electrical module (of another type) to the left of any 10/100BaseTX-inclusive module. In a 1:1 equipment protection scheme with a 2-slot electrical connector module (ECM), either the left- or right-adjacent module from the protection module is the working module. In a 1:2 equipment protection scheme, the center module protects the left- and right-adjacent working modules. In an unprotected scheme, place modules in any valid slot; the 2-slot DS3/E3 ECM provides access to only the right-most module, so place an optic module in the left-most slot. The 3-slot DS3/E3 and 3-slot E1 ECM provides access to only the center and right-most modules, so place an optic module in the left-most slot. (SONET network only) The DS3 Transmux module supports 1:N equipment protection for high-density optical transmux applications, where N=1 to 12 in a Traverse This application has no DS3/E3 ECM requirement. One module protects all remaining adjacent modules. Page 8-10 Turin Networks Release OPS3.1.x

377 Chapter 1 Replacing Existing Traverse Hardware Module Placement Table 8-4 Module Placement Guidelines (continued) Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) EC-3/STM-1E Important: Do not place an electrical module (of another type) to the left of any 10/100BaseTX-inclusive module. With 4-slot EC-3/STM-1E ECMs, for 1:2 protection, place like modules in any three adjacent slots (i.e., n+1, n+2, and n+3). Note: Slot n=1 is not available for electrical protection; use an optical module in this slot instead. The protection group can start in any odd or even slot. The module in the center slot (n+2) is the protecting module for the working modules in the two adjacent slots (n+1 and n+3). With 3-slot EC-3/STM-1E ECMs, for 1:1 protection, place like modules in any two adjacent slots (n+1 and n+2). Note: Slot n=1 is not available for electrical protection; use an optical module in this slot instead. The protection group can start in any odd or even slot. Either module (n+1 or n+2) can be the protecting or working module in the protection group. Note: There is a one-slot offset from the ECM connection to the module itself. See Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications, Chapter 2 ECM Interface Specifications, ECM Placement at the Traverse Main Backplane, page Release OPS3.1.x Turin Networks Page 8-11

378 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Module Placement Table 8-4 Module Placement Guidelines (continued) Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) Ethernet (Next Generation) NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo Important: Do not place an electrical module (of another type) to the left of any 10/100BaseTX-inclusive module. In a 1:1 equipment protection scheme with a 2-slot Ethernet Protection ECM, either the left- or right-adjacent module from the protection module is the working module. In an unprotected scheme, place modules in any valid slot. The 2-slot Ethernet Protection ECM provides access to only the right-most module, so place an optic module in the left-most slot. OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 OC-48/STM-16 with VTX (legacy) None Use the following options when placing any 10/100BaseTX-inclusive modules in a Traverse shelf with DS1, DS3/E3/EC-1 CC, DS3/EC-1 Transmux, or E1 modules: Place 10/100BaseTX-inclusive modules directly to the left of DS1, DS3/E3/EC-1 CC, DS3/EC-1 Transmux, or E1 modules. An OC-N/STM-N module or 1-slot wide blank faceplate is not required if the 10/100BaseTX-inclusive modules are placed to the left of electrical interface modules. or Place an OC-N/STM-N module or a 1-slot wide blank faceplate between the 10/100BaseTX and an electrical interface module if the 10/100BaseTX-inclusive module is placed to the right of the electrical interface module. Page 8-12 Turin Networks Release OPS3.1.x

379 Chapter 1 Replacing Existing Traverse Hardware Module Placement Table 8-4 Module Placement Guidelines (continued) Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) OC-192/STM-64 1/2, 3/4, 5/6, 7/8, 9/10, 11/12, and 13/14 1/2, 3/4, 5/6, 7/8, 9/10, 11/12, 13/14, 15/16, and 17/18 n/a The OC-192/STM-64 modules require two slots for placement. The left side of the OC-192/STM-64 module is placed in an odd numbered slot. VT/TU 5G Switch The VT/TU 5G Switch module supports 1:N equipment protection where: N=1 to 9 in a Traverse 2000 (SONET network only) N=1 (SDH network only) This module has no ECM requirement. One module protects all adjacent modules. Important: Place an OC-N/STM-N or 1-slot blank faceplate between any 10/100BaseTX-inclusive module and an electrical module (of another type), if the 10/100BaseTX-inclusive module is placed to the right of an electrical interface module. A blank faceplate or OC-N/STM-N module is not required if the 10/100BaseTX-inclusive module is placed to the left of an electrical module. Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots. Turin recommends the following module placement scheme: Place DS1, DS3, E3, EC-1 CC, DS3/EC-1 Transmux, EC-3/STM-1E, or E1, and 10/100BaseTX (see Important note above for 10/100BaseTX placement) modules in the left-most slots beginning with slots 1 and 2. Work towards the center of the shelf as required (up to Traverse 1600 slot 12 or Traverse 2000 slot 16). Place VT/TU 5G Switch modules next to the GCM modules. Place additional modules toward the center of the shelf as required. Place OC-N/STM-N and GbE modules (optical modules) beginning in the right-most available slot (starting at Traverse 1600 slot 14 or Traverse 2000 slot 18). Place additional modules towards the center of the shelf as required. Release OPS3.1.x Turin Networks Page 8-13

380 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Module Placement The following table shows the redundancy rules for all GCM types: Table 8-5 Redundancy Rules for GCM Types Active GCM Standby GCM GCM GCM GCM GCM Enhanced Universal 1 GCM Enhanced Universal 1 GCM Enhanced Universal GCM with OC-N/STM-N GCM GCM Enhanced Universal GCM with OC-N/STM-N 1 GCM Enhanced or Universal environmental alarm function should not be used in this combination. Page 8-14 Turin Networks Release OPS3.1.x

381 Chapter 1 Replacing Existing Traverse Hardware GCM Module Replacement as Standby LED Indicators GCM Module Replacement as Standby LED Indicators When a new GCM module is placed as the standby module, the Power and Active/Standby LED indications are as shown in the following table. The LEDs in the following tables apply to all modules. Table 8-6 Power and Active/Standby All Modules LED RED Amber GREEN OFF Flashing Solid Flashing Solid Flashing Solid Power Initialization and diagnosis is underway but not complete Hardware failure detected; replace the module N/A N/A N/A Initialization is complete and the module is operational. No power Active/ Standby N/A N/A The module is unlocked and in Standby mode. 1 Synchronization with the Active module is not complete. The module is unlocked. The module type does not match the provisioned module type or the module is placed in an invalid slot. 2 The module is unlocked and in Standby mode. Synchronization with the Active module is complete. The Active module is unlocked and operational. The module is locked or initialization is not complete. 1 Does not apply to GbE or OC-N modules. 2 For the Traverse platform, refer to Appendix A Module Placement Planning and Guidelines, page 12-1 for valid module placement guidelines. Release OPS3.1.x Turin Networks Page 8-15

382 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Clean Fiber Optic MPX Connectors Clean Fiber Optic MPX Connectors It is critical that optical MPX connectors are clean to ensure proper operation. Turin recommends that you visually inspect the MPX connectors on both the fiber optic cables and optical modules using fiber optic magnification equipment. Turin also recommends that you clean the fiber optic cable and module MPX connectors using the following procedure. WARNING! The Traverse system is a class 1 product that contains a class IIIb laser and is intended for operation in a closed environment with fiber attached. Do not look into the optical connector of the transmitter with power applied. Laser output is invisible and eye damage can result. Do not defeat safety features that prevent looking into the optical connector. WARNING! The optical connector system used on the Traverse fiber optic backplane is designed with a mechanical shutter mechanism that blocks physical and visual access to the optical connector. Do not defeat this safety feature designed to prevent eye damage. WARNING! Follow all warning labels when working with optical fibers. Always wear eye protection when working with optical fibers. Never look directly into the end of a terminated or unterminated fiber or connector, as it may cause eye damage. Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when handling and placing modules in the Traverse shelf. Follow all warnings and instructions included in module packaging to prevent electrostatic damage. Important: Handle modules by the edges and faceplate only. Do not touch any module connectors or components. Important: Do not touch the end of the MPX connectors. Page 8-16 Turin Networks Release OPS3.1.x

383 Chapter 1 Replacing Existing Traverse Hardware Clean Fiber Optic MPX Connectors Table 8-7 Clean Cable and Module MPX Connectors Step Procedure 1 Was the fiber optic cable pre-cabled? If yes, continue to Step 2. If no, continue to Step 3. 2 Remove the fiber optic cable MPX connector(s) from the fiber optic backplane. 3 Clean the fiber optic cable MPX connector with 91% IPA alcohol, a lint-free wipe, and a pressurized optical duster (canned air). 4 Align the white reference marker on the MPX connector with the white stripe on the left side of the fiber optic backplane housing. Note: For a Traverse 600 shelf type, see Figure 8-5 in Step 5. White Stripe Reference Markers Housing A Housing B Figure 8-4 Fiber Optic Backplane Housing A and B For specifications, refer to Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications, Chapter 1 Fiber Optic Interface Cabling Specifications, General MPX Connector to Optical Fiber Port Assignment, page 2-5. Release OPS3.1.x Turin Networks Page 8-17

384 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Clean Fiber Optic MPX Connectors Table 8-7 Clean Cable and Module MPX Connectors (continued) Step Procedure 5 Align the white reference marker on the MPX connector with the white stripe on the left side of the Traverse 600 fiber optic backplane housing. White Stripe Reference Markers Housing A Housing B Figure 8-5 Traverse 600 Fiber Optic Backplane Housing A and B 6 Gently push the MPX connector back into the correct fiber optic backplane housing. 7 Repeat Steps 2 through 6 for each MPX connector. 8 Remove the dust cap from the optical module MPX connector(s). Dust Cap on MPX Connector Figure 8-6 Optical Module MPX Connector Page 8-18 Turin Networks Release OPS3.1.x

385 Chapter 1 Replacing Existing Traverse Hardware Clean Fiber Optic MPX Connectors Table 8-7 Clean Cable and Module MPX Connectors (continued) Step Procedure 9 Clean the optical module MPX connector with 91% IPA alcohol, a lint-free wipe, and a pressurized optical duster (canned air). 10 Continue to the next procedure, Insert a Module. Release OPS3.1.x Turin Networks Page 8-19

386 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Insert a Replacement Module Insert a Replacement Module Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when handling Traverse modules (cards). Plug the ESD wrist strap into the ESD jack provided on the Traverse front inlet fan module, standalone air ramp, or other confirmed source of earth ground. Refer to ESD Jack Locations, page 6-6. Important: Do not install Traverse modules until all installation and cabling procedures are complete. Important: Handle modules by the edges and faceplate only. Do not touch any module connectors or components. Important: Observe all electrostatic sensitive device warnings and precautions when handling Traverse modules. Important: Insert the module into the Traverse shelf using the guides at the top and bottom of the card cage for proper alignment. Make sure the module is vertical, from top to bottom, and that the module stays in the guides from the front to the back of the shelf. Important: Do not place an electrical module (of another type) in the slot directly to the left of any of the following modules: 10/100BaseTX-inclusive (24-port 10/100BaseTX, 2-port GbE LX plus 16-port 10/100BaseTX Combo, or the 2-port GbE SX plus 16-port 10/100BaseTX Combo) module. Important: Modules should insert easily into the Traverse shelf. Do not force the module into position. If the module does not insert easily, slide it back out, verify you are placing it in the correct position and inserting the module into the correct guides top and bottom. Important: Insert the module in the Traverse 600 shelf using the guides for proper alignment. If the Traverse 600 shelf is installed horizontally make sure the module is horizontal, from left to right, and that the module stays in the guides. Page 8-20 Turin Networks Release OPS3.1.x

387 Chapter 1 Replacing Existing Traverse Hardware Insert a Replacement Module Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots. Follow these steps to insert a module. Table 8-8 Insert a Module Step Procedure 1 Is this an optical module with MPX connectors? If yes, complete the Clean MPX Connectors procedure before proceeding. If no, continue to Step 2. 2 Flip the module locking tabs up. Hold the module with the tabs parallel to the top and bottom of the module. Guide Pins Locking Tabs in Open Position Figure 8-7 Module Locking Tabs in the Unlocked Position Release OPS3.1.x Turin Networks Page 8-21

388 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Insert a Replacement Module Table 8-8 Insert a Module (continued) Step Procedure 3 Important: Each slot in the Traverse shelf has guides to properly align the module into position for contact with the main and mesh backplanes. Use these guides to ensure the module is properly aligned. This is easier to do if you are eye level with the shelf. The module should insert easily into the Traverse shelf. Do not force the module into position. Insert the module in the Traverse 1600 or Traverse 2000 shelf using the guides at the top and bottom of the card cage for proper alignment. Make sure the module is vertical, from top to bottom, and that the module stays in the guides from the front to the back of the shelf. Card Cage Guides for Module Alignment Figure 8-8 Traverse 1600 or Traverse 2000 Shelf with Guides Insert the module in the Traverse 600 shelf using the guides for proper alignment. If the Traverse 600 shelf is installed horizontally, as in the following figure, make sure the module is horizontal, from left to right, and that the module stays in the guides from the front to the back of the shelf. Card Cage Guides for Module Alignment Figure 8-9 Traverse 600 Shelf with Guides Page 8-22 Turin Networks Release OPS3.1.x

389 Chapter 1 Replacing Existing Traverse Hardware Insert a Replacement Module Table 8-8 Insert a Module (continued) Step Procedure 4 Push the center of the module faceplate until the locking tabs begin to close and the locking tabs start to roll around the lip of the Traverse shelf. The optical module makes an audible click indicating it is making contact with the fiber optic backplane connectors. 5 Push the locking tabs down. The tabs must close around each end of the module to lock the module in place. Locking Tabs in Closed Position Figure 8-10 Module Tabs in the Locked Position 6 Press the tabs into their locked position to secure the module. The module is locked into position when the top and bottom tabs are pressed down completely and the locking tabs are secured in the lip of the Traverse shelf. 7 The Insert a Module procedure is complete. Release OPS3.1.x Turin Networks Page 8-23

390 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Replace the Front Inlet Fan Tray Module Replace the Front Inlet Fan Tray Module The front inlet fan tray holder is bundled and shipped with the Traverse 1600 and Traverse 2000 systems. The fan tray module, including the fans, is shipped separately. Proceed with the following steps to install the fan tray module into the fan tray holder. Important: The instructions below support the redesigned front inlet fan tray with integrated air ramp unit. Refer to Replace the Fan Tray Module (legacy), page 8-29 if you are installing an original fan tray module. Important: Wear a properly grounded Electrostatic Discharge (ESD) wrist strap when installing the fan tray module as it contains static-sensitive components. Table 8-9 Insert a Front Inlet Fan Module Step Procedure 1 Lift the front inlet fan module to be level with the front inlet fan tray holder. Slide the fan module into the front of the fan tray holder and push it straight in until the two connectors engage. 2 The front inlet fan module is in the correct position when it is flush with the front of the fan tray holder. Important: Do not force the fan module into position. If it does not plug in easily, slide it back out. Check for any obstructions or a damaged connector that might prevent it from sliding into position and verify it is in the correct guides before attempting to insert it again. 3 Tighten the captive fasteners to secure it. Captive Fasteners Figure 8-11 Front Inlet Fan Module Captive Fasteners 4 Continue to the next procedure, Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000). Page 8-24 Turin Networks Release OPS3.1.x

391 Chapter 1 Replacing Existing Traverse Hardware Front Inlet Fan Tray Air Filter Installation Front Inlet Fan Tray Air Filter Installation The front inlet fan module requires a foam air filter that is placed at the top of the front inlet fan tray holder after the fan module is installed. Important: The instructions below support the redesigned front inlet fan tray with integrated air ramp unit. Refer to Fan Tray Air Filter Installation (legacy), page 8-32 if you are installing an original fan tray air filter. The front inlet fan tray air filters are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. The following procedure provides step-by-step instructions on how to insert the front inlet fan tray air filter. Table 8-10 Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000) Step Procedure 1 Grasp the air filter flexible pull tab. Figure 8-12 Front Inlet Air Filter Pull Tab (top view) 2 Insert the air filter in the gap between the top of the front inlet fan module and the top of the front inlet fan tray holder. Slide the air filter along the fan tray holder guides until the filter is flush with the front of the fan tray holder. 3 The Fan Tray Air Filter (with springs) Installation (Traverse, legacy) procedure is complete. Release OPS3.1.x Turin Networks Page 8-25

392 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Replace the Traverse 600 Fan Assembly Replace the Traverse 600 Fan Assembly The Traverse 600 fan module with integral fan tray is bundled and shipped with the Traverse 600 system. Proceed with the following steps to install the fan assembly. Important: Wear a properly grounded Electrostatic Discharge (ESD) wrist strap when installing the fan tray module as it contains static-sensitive components. Table 8-11 Insert a Fan Module with Integral Fan Tray Step Procedure 1 Loosen the two captive screws on the right-front cover of the Traverse 600 fan assembly to release it. Captive Fasteners Figure 8-13 Fan Assembly Front Cover - Traverse Open the right-front fan assembly cover. Page 8-26 Turin Networks Release OPS3.1.x

393 Chapter 1 Replacing Existing Traverse Hardware Replace the Traverse 600 Fan Assembly Table 8-11 Insert a Fan Module with Integral Fan Tray (continued) Step Procedure 3 Hold the fan assembly vertically with the fan module facing left and lift it level with the fan cage. Slide the fan assembly into the fan cage along the guides and push it straight in until it connects to the back of the shelf. Important: Do not force the fan tray module into position. If it does not plug in easily, slide it back out. Check for any obstructions or a damaged connector that might prevent it from sliding into position and verify it is lined up in the correct guides. Traverse 600 Shelf Fan Assembly Figure 8-14 Traverse 600 Fan Assembly Installation 4 Continue to the next procedure, Insert a Fan Assembly Air Filter (Traverse 600). Release OPS3.1.x Turin Networks Page 8-27

394 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Fan Assembly Air Filter Installation (Traverse 600) Fan Assembly Air Filter Installation (Traverse 600) The Traverse 600 fan assembly (fan module with integral fan tray) requires a foam air filter that is placed to the left of the fan assembly after the fan module is installed. The Traverse 600 fan air filters are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. The following procedure provides step-by-step instructions on how to insert the air filter. Table 8-12 Insert a Fan Assembly Air Filter (Traverse 600) Step Procedure 1 Grasp the air filter flexible pull tab. Figure 8-15 Traverse 600 Fan Assembly Air Filter Pull Tab (top view) 2 Insert the air filter in the gap between the fan assembly and the left of the fan cage. Slide the air filter along the guides until the filter is flush. 3 The Fan Tray Air Filter (with springs) Installation (Traverse, legacy) procedure is complete. Page 8-28 Turin Networks Release OPS3.1.x

395 Chapter 1 Replacing Existing Traverse Hardware Replace the Fan Tray Module (legacy) Replace the Fan Tray Module (legacy) This topic applies to the original fan tray unit without an integrated air ramp (legacy, pre-release 1.4). Refer to Replace the Front Inlet Fan Tray Module, page 8-24 if you are installing the front inlet fan module into the redesigned front inlet fan tray holder with integrated air ramp unit for either the Traverse 1600 and Traverse 2000 shelf. Refer to Replace the Traverse 600 Fan Assembly, page 8-26 if you are installing the fan assembly for the Traverse 600 shelf. The (legacy) fan tray holder is bundled and shipped with the Traverse 1600 and Traverse 2000 system. The fan tray module, including the fans, is shipped separately. Proceed with the following steps to install the fan tray module into the fan tray holder. Important: Wear a properly grounded Electrostatic Discharge (ESD) wrist strap when installing the fan tray module as it contains static-sensitive components. Table 8-13 Insert a Fan Tray Module Step Procedure 1 Loosen the captive fasteners on the fan tray holder front cover to release it. Figure 8-16 Fan Tray Holder Front Cover 2 Lower the fan tray holder front cover. Captive Fasteners Release OPS3.1.x Turin Networks Page 8-29

396 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Replace the Fan Tray Module (legacy) Table 8-13 Insert a Fan Tray Module (continued) Step Procedure 3 Lift the fan tray module until it is level with the fan tray holder. Slide the fan tray module into the fan tray holder along the guides. Push it straight in until it connects to the fan tray holder. Fan Tray Module Connector Fan Tray Holder Guides Figure 8-17 Traverse 1600 Fan Tray Module Installation Fan Tray Module Connector Fan Tray Holder Guides Figure 8-18 Traverse 2000 Fan Tray Module Installation 4 The fan tray module is in the correct position when it is slightly recessed from the front of the fan tray holder. Important: Do not force the fan tray module into position. If it does not plug in easily, slide it back out. Check for any obstructions or a damaged connector that might prevent it from sliding into position, and verify it is in the correct guides. 5 Continue to the next procedure, Fan Tray Air Filter (with springs) Installation (Traverse, legacy) or Fan Tray Air Filter (with handle) Installation. Page 8-30 Turin Networks Release OPS3.1.x

397 Chapter 1 Replacing Existing Traverse Hardware Replace the Fan Tray Module (legacy) Release OPS3.1.x Turin Networks Page 8-31

398 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Fan Tray Air Filter Installation (legacy) Fan Tray Air Filter Installation (legacy) This topic applies to the air filters for the original fan tray unit without an integrated air ramp (pre-release 1.4). Refer to Front Inlet Fan Tray Air Filter Installation, page 8-25 if you are installing the front inlet fan tray air filter into the redesigned front inlet fan tray holder with integrated air ramp unit. There are two different designs of fan tray air filters as listed below. Both designs are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. Table 8-14 Fan Tray Air Filter (with springs) Installation (Traverse, legacy), page 8-32 Table 8-15 Fan Tray Air Filter (with handle) Installation, page 8-34 Table 8-14 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) Step Procedure 1 Rotate the air filter pull-tabs out. Springs Pull Tabs Figure 8-19 Air Filter with Springs 2 Hold the air filter with the metal window-pane side down and the springs to the back. 3 Insert the air filter in the gap between the fan tray module and the top of the fan tray holder. Slide the air filter along the fan tray holder guides until the springs on the back edge are fully compressed. 4 With the springs fully compressed, lift the front edge of the air filter up and over the retaining flanges and release it. 5 Rotate the pull-tabs so they are parallel to the front edge of the air filter. Page 8-32 Turin Networks Release OPS3.1.x

399 Chapter 1 Replacing Existing Traverse Hardware Fan Tray Air Filter Installation (legacy) Table 8-14 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) Step Procedure 6 Lift the fan tray holder front cover into its closed position. Tighten the captive fasteners to secure it. Captive Fasteners Figure 8-20 Fan Tray Holder Front Cover Note: The front cover closes very easily when the fan tray module and air filter are in position. If the cover does not close easily, check the fan tray module to make sure it is recessed from the front of the fan tray holder. 7 The Fan Tray Air Filter (with springs) Installation (Traverse, legacy) procedure is complete. Release OPS3.1.x Turin Networks Page 8-33

400 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Fan Tray Air Filter Installation (legacy) The following procedure provides step-by-step instructions on how to install the fan tray filter with a handle on the front edge. Table 8-15 Fan Tray Air Filter (with handle) Installation Step Procedure 1 Hold the air filter with the metal window-pane side down with the handle facing to the front. Handle Figure 8-21 Air Filter with Handle 2 Insert the air filter in the gap between the fan tray module and the top of the fan tray holder. 3 Slide the air filter along the fan tray holder guides. Lift up on the filter handle as you are pushing the filter towards the back of the fan tray holder. There is an audible click when the air filter is in position. The handle drops down over the front of the fan tray module. Page 8-34 Turin Networks Release OPS3.1.x

401 Chapter 1 Replacing Existing Traverse Hardware Fan Tray Air Filter Installation (legacy) Table 8-15 Fan Tray Air Filter (with handle) Installation (continued) Step Procedure 4 Lift the fan tray holder front cover into its closed position. Tighten the captive fasteners to secure it. Captive Fasteners Figure 8-22 Fan Tray Holder Front Cover Note: The front cover closes very easily when the fan tray module and air filter are correctly in position. If the cover does not close easily, check the fan tray module to make sure it is recessed from the front of the fan tray holder. 5 The Fan Tray Air Filter (with handle) Installation procedure is complete. Release OPS3.1.x Turin Networks Page 8-35

402 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Fan Tray Air Filter Installation (legacy) Page 8-36 Turin Networks Release OPS3.1.x

403 SECTION 8HARDWARE UPGRADES Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray Introduction Precautions and Assumptions This chapter provides upgrade instructions for replacing separate Traverse fan tray and air ramp assemblies with a single front inlet fan tray (FIFT) assembly: Precautions and Assumptions, page 8-37 Required Equipment and Tools, page 8-38 FIFT Upgrade Instructions, page 8-38 The following precautions and assumptions apply: WARNING! Plan this upgrade to avoid disruptions and keep the time to a minimum. This replacement operation should take no more than 4 to 5 minutes. A fully loaded Traverse shelf can sustain a non-service affecting temperature increase for approximately 6 minutes before it begins generating critical alarms. Depending on the number of modules in the shelf and the room temperature, Turin recommends the use of a regular room fan blowing on the node during this operation. If you do use a standalone room fan, carefully remove any blank faceplates in the shelf and position the fan to blow directly onto the front of the shelf. Important: A fan tray holder, with fay tray module and fan filter, must be installed directly below the Traverse 1600 or Traverse 2000 shelf so there is no gap between the shelf and fan tray holder to ensure proper air flow. Important: These upgrade instructions apply to nodes on software Release 1.4 or higher. Important: The existing separate fan tray holder and air ramp use 4 inches of height. This is the required minimum replacement space to allow easy insertion of the new FIFT. Release OPS3.1.x Turin Networks Page 8-37

404 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Required Equipment and Tools Required Equipment and Tools The following equipment and tools are required for this upgrade: Front inlet fan tray holder Front inlet fan module Air filter 1 Large straight slot screwdriver or 5/16-inch hex socket Two technicians (to decrease the replacement time, have one in front and one in back of the rack) Stepladder (optional) Electrostatic Discharge (ESD) wrist strap FIFT Upgrade Instructions Follow these FIFT upgrade instructions: Table 8-16 Front Inlet Fan Tray Holder Upgrade Instructions Step Instructions 1 Check the New Fan Module, page 8-39 to ensure proper power up. 2 Is there an air ramp below the existing fan tray? Yes. Remove it. No. Go to the next step. 3 Pull the air filter from the fan tray holder. 4 Remove the existing fan tray module. 5 Remove the power cable from the rear of the fan tray holder. 6 Remove the fan tray holder. 7 Install the new FIFT (including the fan module and air filter). Refer to Traverse Installation and Commissioning Guide, Section 7 Hardware Installation Procedures, Chapter 2 Traverse System Hardware Installation, Front Inlet Fan Tray Holder Installation, page The Front Inlet Fan Tray Holder Upgrade Instructions are complete. 1 Front inlet fan tray air filters are available in 63% arrestance at 300 FPM feet per minute (91.4 meters per minute) and 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. Page 8-38 Turin Networks Release OPS3.1.x

405 Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray Check the New Fan Module Check the New Fan Module Check the new FIFT fan module as follows: Table 8-17 New Fan Module Check Step Procedure 1 From the rear of the existing fan tray module, loosen the two thumbscrews on the power cable cover (located on the left-hand side). Power Cable Cover Front Figure 8-23 Existing Fan Tray Holder Back Panel 2 Unplug the power cable from the existing fan tray module. 3 Plug the power cable into the new FIFT fan module to verify power up. 4 Unplug the power cable from the new FIFT fan tray module. 5 Plug the power cable back into the existing fan module. 6 Did the new FIFT fan module power up? Yes. Go to Step 9. No. Go to Step 7. 7 Tighten the thumbscrews on the existing power cable cover and stop the upgrade procedure. 8 RMA the tested fan module. 9 The New Fan Module Check procedure is complete. Release OPS3.1.x Turin Networks Page 8-39

406 Node Operations and Maintenance Guide, Section 8: Hardware Upgrades Check the New Fan Module Page 8-40 Turin Networks Release OPS3.1.x

407 SECTION 9 APPENDICES SECTION 9 Contents Appendix A Module Placement Planning and Guidelines Introduction Module Placement Guidelines Traverse 1600 Module Placement Traverse 2000 Module Placement Traverse 600 Module Placement Appendix B Traverse SNMP v1/v2c Agent and MIBs Introduction Supported Traverse SNMP MIBs Configure the Traverse SNMP Agent Parameters from TransNav Location of SNMP MIB File List of Figures Figure 9-1 Admin Menu SNMP Configuration Figure 9-2 Node SNMP Configuration Screen List of Tables Table 9-1 Module Placement Guidelines Table 9-2 Redundancy Rules for GCM Types Table 9-3 Traverse 1600 Module Placement Guidelines Table 9-4 Traverse 2000 Module Placement Guidelines Table 9-5 Traverse 600 Module Placement Guidelines Release OPS3.1.x Turin Networks Page i

408 Node Operations and Maintenance Guide, Section 9 Appendices Page ii Turin Networks Release OPS3.1.x

409 SECTION 9APPENDICES Appendix A Module Placement Planning and Guidelines Introduction It is important to plan for module placement during installation, cabling, and start-up activities for the Traverse system. The following tables provide module placement guidelines for the Traverse shelf, including: Valid slot placement for GCM, optical, electrical, and VT/VC switching modules Equipment protection (1:N, where N=1, 2), working, and protection module placement Unprotected module placement Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older modules with newer modules with minimal traffic interruption for each module in any 1:N protection group. Important: Do not place an electrical module (of another type) in the slot directly to the left of any 10/100BaseTX-inclusive module (i.e., 10/100BaseTX, GbE [LX, SX, or CWDM] plus 10/100BaseTX Combo, GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo, and GbE SX plus GbE CWDM plus 10/100BaseTX Combo). Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots. This appendix contains information on the following topics: Module Placement Guidelines, page 9-2 Traverse 1600 Module Placement, page 9-7 Traverse 2000 Module Placement, page 9-12 Traverse 600 Module Placement, page 9-17 Release OPS3.1.x Turin Networks Page 9-1

410 Node Operations and Maintenance Guide, Section 9: Appendices Module Placement Guidelines Module Placement Guidelines The following table provides guidelines for placement of modules in a Traverse shelf: Table 9-1 Module Placement Guidelines Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) GCM GCM Enhanced GCM with OC-12/STM-4 GCM with OC-48/STM-16 GCM with VTX GCM with OC-12/STM-4 plus VTX GCM with OC-48/STM-16 plus VTX GCMA and GCMB (slots 15 and 16) GCMA and GCMB (slots 19 and 20) GCMA and GCMB (slots 5 and 6) Redundant GCMs are recommended for equipment protection. However, if only one GCM is used, it can be placed in either slot GCMA or GCMB. Redundant GCMs can be different types. See Table 9-2 Redundancy Rules for GCM Types for a list of control modules. DS1 DS3/E3/EC-1 CC (12-port) DS3/E3/EC-1 CC (24-port) DS3/EC-1 Transmux E Important: Do not place an electrical module (of another type) to the left of any 10/100BaseTX-inclusive module. In a 1:1 equipment protection scheme with a 2-slot electrical connector module (ECM), either the left- or right-adjacent module from the protection module is the working module. In a 1:2 equipment protection scheme, the center module protects the left- and right-adjacent working modules. In an unprotected scheme, place modules in any valid slot; the 2-slot DS3/E3 ECM provides access to only the right-most module, so place an optic module in the left-most slot. The 3-slot DS3/E3 and 3-slot E1 ECM provides access to only the center and right-most modules, so place an optic module in the left-most slot. (SONET network only) The DS3 Transmux module supports 1:N equipment protection for high-density optical transmux applications, where N=1 to 12 in a Traverse This application has no DS3/E3 ECM requirement. One module protects all remaining adjacent modules. Page 9-2 Turin Networks Release OPS3.1.x

411 Appendix A Module Placement Planning and Guidelines Module Placement Guidelines Table 9-1 Module Placement Guidelines (continued) Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) EC-3/STM-1E Important: Do not place an electrical module (of another type) to the left of any 10/100BaseTX-inclusive module. With 4-slot EC-3/STM-1E ECMs, for 1:2 protection, place like modules in any three adjacent slots (i.e., n+1, n+2, and n+3). Note: Slot n=1 is not available for electrical protection; use an optical module in this slot instead. The protection group can start in any odd or even slot. The module in the center slot (n+2) is the protecting module for the working modules in the two adjacent slots (n+1 and n+3). With 3-slot EC-3/STM-1E ECMs, for 1:1 protection, place like modules in any two adjacent slots (n+1 and n+2). Note: Slot n=1 is not available for electrical protection; use an optical module in this slot instead. The protection group can start in any odd or even slot. Either module (n+1 or n+2) can be the protecting or working module in the protection group. Note: There is a one-slot offset from the ECM connection to the module itself. See Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications, Chapter 2 ECM Interface Specifications, ECM Placement at the Traverse Main Backplane, page Release OPS3.1.x Turin Networks Page 9-3

412 Node Operations and Maintenance Guide, Section 9: Appendices Module Placement Guidelines Table 9-1 Module Placement Guidelines (continued) Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) Ethernet (Next Generation) NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo Important: Do not place an electrical module (of another type) to the left of any 10/100BaseTX-inclusive module. In a 1:1 equipment protection scheme with a 2-slot Ethernet Protection ECM, either the left- or right-adjacent module from the protection module is the working module. In an unprotected scheme, place modules in any valid slot. The 2-slot Ethernet Protection ECM provides access to only the right-most module, so place an optic module in the left-most slot. OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 OC-48/STM-16 with VTX (legacy) None Use the following options when placing any 10/100BaseTX-inclusive modules in a Traverse shelf with DS1, DS3/E3/EC-1 CC, DS3/EC-1 Transmux, or E1 modules: Place 10/100BaseTX-inclusive modules directly to the left of DS1, DS3/E3/EC-1 CC, DS3/EC-1 Transmux, or E1 modules. An OC-N/STM-N module or 1-slot wide blank faceplate is not required if the 10/100BaseTX-inclusive modules are placed to the left of electrical interface modules. or Place an OC-N/STM-N module or a 1-slot wide blank faceplate between the 10/100BaseTX and an electrical interface module if the 10/100BaseTX-inclusive module is placed to the right of the electrical interface module. Page 9-4 Turin Networks Release OPS3.1.x

413 Appendix A Module Placement Planning and Guidelines Module Placement Guidelines Table 9-1 Module Placement Guidelines (continued) Module Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) OC-192/STM-64 1/2, 3/4, 5/6, 7/8, 9/10, 11/12, and 13/14 1/2, 3/4, 5/6, 7/8, 9/10, 11/12, 13/14, 15/16, and 17/18 n/a The OC-192/STM-64 modules require two slots for placement. The left side of the OC-192/STM-64 module is placed in an odd numbered slot. VT/TU 5G Switch The VT/TU 5G Switch module supports 1:N equipment protection where: N=1 to 9 in a Traverse 2000 (SONET network only) N=1 (SDH network only) This module has no ECM requirement. One module protects all adjacent modules. Important: Place an OC-N/STM-N or 1-slot blank faceplate between any 10/100BaseTX-inclusive module and an electrical module (of another type), if the 10/100BaseTX-inclusive module is placed to the right of an electrical interface module. A blank faceplate or OC-N/STM-N module is not required if the 10/100BaseTX-inclusive module is placed to the left of an electrical module. Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots. Turin recommends the following module placement scheme: Place DS1, DS3, E3, EC-1 CC, DS3/EC-1 Transmux, EC-3/STM-1E, or E1, and 10/100BaseTX (see Important note above for 10/100BaseTX placement) modules in the left-most slots beginning with slots 1 and 2. Work towards the center of the shelf as required (up to Traverse 1600 slot 12 or Traverse 2000 slot 16). Place VT/TU 5G Switch modules next to the GCM modules. Place additional modules toward the center of the shelf as required. Place OC-N/STM-N and GbE modules (optical modules) beginning in the right-most available slot (starting at Traverse 1600 slot 14 or Traverse 2000 slot 18). Place additional modules towards the center of the shelf as required. Release OPS3.1.x Turin Networks Page 9-5

414 Node Operations and Maintenance Guide, Section 9: Appendices Module Placement Guidelines The following table shows the redundancy rules for all GCM types: Table 9-2 Redundancy Rules for GCM Types Active GCM Standby GCM GCM GCM GCM GCM Enhanced Universal 1 GCM Enhanced Universal 1 GCM Enhanced Universal GCM with OC-N/STM-N GCM GCM Enhanced Universal GCM with OC-N/STM-N 1 GCM Enhanced or Universal environmental alarm function should not be used in this combination. Page 9-6 Turin Networks Release OPS3.1.x

415 Release OPS3.1.x Turin Networks Page 9-7 Traverse 1600 Module Placement The following table provides module placement guidelines for the Traverse 1600 shelf. Legend: Gray Fill=valid slot for module, No Fill=invalid module slot, Standby or Active (S/A), Protecting (P), Working (W), Open (O). Important: For standard electrical connector module (ECM) placement, the 2-slot ECMs plug into slot n of an n and n+1 slot combination. The 3-slot ECMs plug into slot n+1 of an n, n+1, and n+2 slot combination. For example, in a Traverse 1600 slot 11 and 12 combination, the 2-slot ECM plugs into the slot 11 backplane connectors. Some ECMs require specific placement, see the Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications, Chapter 2 ECM Interface Specifications, page 2-9 for ECM slot placement details. Table 9-3 Traverse 1600 Module Placement Guidelines Module Type Traverse 1600 Slot Numbers GCM S/A S/A GCM Enhanced GCM 1 GCM OC-12/STM-4 1 GCM OC-48/STM-16 1 OPTICAL (Note: Optical modules are protected at the port level, there are no slot or module placement restrictions for optical working/protection.) OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 W W W W W W W W W W W W W W OC-192/STM-64 Slots 1/2 Slots 3/4 Slots 5/6 Slots 7/8 Slots 9/10 Slots 11/12 Slots 13/14 EC-3/STM-1E 1:2 equipment protection with a 4-slot ECM EC-3/STM-1E O W/O P/W/O W/P/ W/O EC-3/STM-1E 1:1 equipment protection with a 3-slot ECM O/W/P /W W/O/ W/P P/W/O /W W/P/ W/O O/W/P /W W/P P/W W EC-3/STM-1E O P/O W/P/O O/W/P P/O/W W/P/O O/W/P P/O/W W/P/O O/W/P P/W W Appendix A Module Placement Planning and Guidelines Traverse 1600 Module Placement

416 Page 9-8 Turin Networks Release OPS3.1.x Table 9-3 Traverse 1600 Module Placement Guidelines (continued) Traverse 1600 Slot Numbers Module Type EC-3/STM-1E 1:1 equipment protection with a 4-slot ECM EC-3/STM-1E O P/O W/P O/W O P/O W/P O/W O P/O W/P O/W EC-3/STM-1E unprotected with a 3-slot ECM EC-3/STM-1E O O W O O W O O W O O W EC-3/STM-1E unprotected with a 4-slot ECM EC-3/STM-1E O W O W O W O W O W O W Node Operations and Maintenance Guide, Section 9: Appendices Traverse 1600 Module Placement

417 Release OPS3.1.x Turin Networks Page 9-9 Table 9-3 Traverse 1600 Module Placement Guidelines (continued) Module Type ETHERNET (next generation) 1:1 equipment protection with a 2-slot Ethernet Protection ECM (Note: The Ethernet Combo modules have optical ports and electrical ports. The module placement restriction is due to the electrical ports.) NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo ETHERNET unprotected with a 2-slot 10/100BaseT ECM NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo Traverse 1600 Slot Numbers P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W W W W W W W W W W W W W Appendix A Module Placement Planning and Guidelines Traverse 1600 Module Placement

418 Page 9-10 Turin Networks Release OPS3.1.x Table 9-3 Traverse 1600 Module Placement Guidelines (continued) Module Type ETHERNET unprotected with a 2-slot Ethernet (Protection) ECM NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo TDM 1:2 equipment protection with the corresponding ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 2-slot ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 3-slot ECM DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM unprotected with the corresponding ECM Traverse 1600 Slot Numbers O W/O W/O W/O W/O W/O W/O W/O W/O W/O W/O W W W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O Node Operations and Maintenance Guide, Section 9: Appendices Traverse 1600 Module Placement

419 Table 9-3 Traverse 1600 Module Placement Guidelines (continued) Release OPS3.1.x Turin Networks Page 9-11 DS1, E1 Module Type W W W W W W W W W W W W TDM unprotected with a 2-slot DS3/E3 ECM (Note: The module placement restriction is due to the electrical connector module.) DS3/E3/EC-1 CC DS3/EC-1 Transmux O W/O W/O W/O W/O W/O W/O W/O W/O W/O W/O W TDM unprotected with a 3-slot DS3/E3 ECM (Note: The module placement restriction is due to the electrical connector module.) DS3/E3/EC-1 CC DS3/EC-1 Transmux O W/O W/O W/O W/O W/O W/O W/O W/O W/O W W VT/VC Switching 1:N equipment protection (Note: No ECM requirement with VT/VC switching modules.) VT/TU 5G Switch W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P GCM with optics plus VTX 2 W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P VT/VC Switching unprotected Traverse 1600 Slot Numbers VT/TU 5G Switch W W W W W W W W W W W W W W GCM with optics plus VTX 2 W W W W W W W W W W W W W W 1 Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with a Enhanced GCM for GCM redundancy. 2 While the VTX can be in a 1:1 or unprotected group, the related OC-N/STM-N facilities can be unprotected or in a 1+1 APS, UPSR, or BLSR protection group. Important: Place an OC-N or one-slot wide blank faceplate between any 10/100BaseTX-inclusive module and an electrical module (of another type), if the 10/100BaseTX-inclusive module is placed to the right of an electrical interface module. A blank faceplate or OC-N module is not required if the 10/100BaseTX-inclusive module is placed to the left of an electrical module. Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling. Appendix A Module Placement Planning and Guidelines Traverse 1600 Module Placement

420 Page 9-12 Turin Networks Release OPS3.1.x Traverse 2000 Module Placement The following table provides module placement guidelines for the Traverse 2000 shelf. Legend: Gray Fill=valid slot for module, No Fill=invalid module slot, Standby or Active (S/A), Protecting (P), Working (W), Open (O). Important: For standard electrical connector module (ECM) placement, 2-slot ECMs plug into slot n of an n and n+1 slot combination. The 3-slot ECMs plug into slot n+1 of an n, n+1, and n+2 slot combination. For example, in a Traverse 2000 slot 15 and 16 combination, the 2-slot ECM plugs into the slot 15 backplane connectors. Some ECMs require specific placement, see Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications for ECM slot placement details. Table 9-4 Traverse 2000 Module Placement Guidelines Module Type Traverse 2000 Slot Numbers GCM S/A S/A GCM Enhanced GCM 1 GCM OC-12/STM-4 1 GCM OC-48/STM-16 1 OPTICAL (Note: Optical modules are protected at the port level, there are no slot or module placement restrictions for optical working/protection.) OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 W W W W W W W W W W W W W W W W W W OC-192/STM-64 Slots 1/2 Slots 3/4 Slots 5/6 Slots 7/8 Slots 9/10 Slots 11/12 Slots 13/14 Slots 15/16 Slots 17/18 EC-3/STM-1E 1:2 equipment protection with a 4-slot ECM EC-3/STM-1E O W/ O P/ W/ O W/ P/ W/ O EC-3/STM-1E 1:1 equipment protection with a 3-slot ECM O/ W/ P/ W W/ O/ W/ P P/ W/ O/ W W/ P/ W/ O O/ W/ P/ W W/ O/ W/ P P/ W/ O/ W W/ P/ W/ O O/ W/ P/ W W/ P P/ W W Node Operations and Maintenance Guide, Section 9: Appendices Traverse 2000 Module Placement

421 Release OPS3.1.x Turin Networks Page 9-13 Table 9-4 Traverse 2000 Module Placement Guidelines (continued) Module Type EC-3/STM-1E O P/O W/ P/O O/ W/ P EC-3/STM-1E 1:1 equipment protection with a 4-slot ECM EC-3/STM-1E O P/O W/ P EC-3/STM-1E unprotected with a 3-slot ECM O/ W P/O /W W/ P/O O/ W/ P O P/O W/ P P/O /W O/ W W/ P/O O/ W/ P P/O /W O P/O W/ P W/ P/O O/ W O/ W/ P P/O /W W/ P O P/O W/ P EC-3/STM-1E O O W O O W O O W O O W O O W EC-3/STM-1E unprotected with a 4-slot ECM EC-3/STM-1E O W O W O W O W O W O W O W O W ETHERNET 1:1 equipment protection and 2-slot Ethernet Protection ECM (Note: The Ethernet Combo modules have optical ports and electrical ports. The module placement restriction is due to the electrical ports.) NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo P W/ P ETHERNET unprotected with a 2-slot 10/100BaseT ECM W/ P W/ P W/ P W/ P W/ P W/ P Traverse 2000 Slot Numbers W/ P W/ P W/ P W/ P W/ P W/ P W/ P W O/ W W Appendix A Module Placement Planning and Guidelines Traverse 2000 Module Placement

422 Page 9-14 Turin Networks Release OPS3.1.x Table 9-4 Traverse 2000 Module Placement Guidelines (continued) Module Type NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo ETHERNET unprotected with a 2-slot Ethernet (Protection) ECM NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo W W W W W W W W W W W W W W W W O W/ O TDM 1:2 equipment protection with corresponding ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 W W/ P W/ O W/ P W/ O W/ P W/ O W/ P W/ O W/ P W/ O W/ P W/ O W/ P Traverse 2000 Slot Numbers W/ O W/ P W/ O W/ P W/ O W/ P W/ O W/ P W/ O W/ P W/ O W/ P W/ O W/ P W W Node Operations and Maintenance Guide, Section 9: Appendices Traverse 2000 Module Placement

423 Release OPS3.1.x Turin Networks Page 9-15 Table 9-4 Traverse 2000 Module Placement Guidelines (continued) TDM 1:1 equipment protection with a 2-slot ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 W/ P W/ P TDM 1:1 equipment protection with a 3-slot ECM DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 W/ P/O W/ P/O TDM unprotected with the corresponding ECM DS1 E1 Module Type W/ P W/ P/O W/ P W/ P/O W/ P W/ P/O W/ P W/ P/O W/ P W/ P/O W/ P W/ P/O W W W W W W W W W W W W W W W W TDM unprotected with a 2-slot DS3/E3 ECM (Note: The module placement restriction is due to the electrical connector module.) DS3/E3/EC-1 CC DS3/EC-1 Transmux O W/ O W/ O W/ O TDM unprotected with a 3-slot DS3/E3 ECM (Note: The module placement restriction is due to the electrical connector module.) DS3/E3/EC-1 CC DS3/EC-1 Transmux O W/ O W/ O VT/VC Switching with 1:N equipment protection (Note: No ECM requirement with VT/VC switching modules.) VT/TU 5G Switch with 1:1 Equipment Protection W/ P GCM with optics plus VTX 2 W/ P VT/VC Switching unprotected W/ P W/ P W/ P W/ P W/ O W/ P W/ P W/ O W/ O W/ P W/ P W/ O W/ O W/ P W/ P W/ O W/ O W/ P W/ P W/ O W/ O W/ P W/ P Traverse 2000 Slot Numbers W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P W/ P/O W/ O W W/ P W/ P W/ P W/ P/O W W W/ P W/ P W/ P W/ P W/ P W/ P Appendix A Module Placement Planning and Guidelines Traverse 2000 Module Placement

424 Page 9-16 Turin Networks Release OPS3.1.x Table 9-4 Traverse 2000 Module Placement Guidelines (continued) Module Type VT/TU 5G Switch without Equipment Protection Traverse 2000 Slot Numbers W W W W W W W W W W W W W W W W W W GCM with optics plus VTX 2 W W W W W W W W W W W W W W W W W W 1 Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with a Enhanced GCM for GCM redundancy. 2 While the VTX can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1 APS, UPSR, or BLSR protection group. Important: Place an OC-N or wide blank faceplate between any 10/100BaseTX-inclusive module and an electrical module (of another type) if the 10/100BaseTX-inclusive module is placed to the right of an electrical interface module. A blank faceplate or OC-N module is not required if the 10/100BaseTX-inclusive module is placed to the left of an electrical module. Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling. Node Operations and Maintenance Guide, Section 9: Appendices Traverse 2000 Module Placement

425 Release OPS3.1.x Turin Networks Page 9-17 Traverse 600 Module Placement The following table provides module placement guidelines for the Traverse 600 shelf. Legend: Gray Fill=valid slot for module, No Fill=invalid module slot, Standby or Active (S/A), Protecting (P), Working (W), Open (O). Important: For standard electrical connector module (ECM) placement, 2-slot ECMs plug into slot n of an n and n+1 slot combination. The 3-slot ECMs plug into slot n+1 of an n, n+1, and n+2 slot combination. For example, in a Traverse 600 slot 3 and 4 combination, the 2-slot ECM plugs into the slot 3 backplane connectors. Some ECMs require specific placement, see Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications for ECM slot placement details. Table 9-5 Traverse 600 Module Placement Guidelines Module Type Traverse 600 Slot Numbers GCM S/A S/A GCM Enhanced GCM 1 GCM OC-12/STM-4 1 GCM OC-48/STM-16 1 OPTICAL (Note: Optical modules are protected at the port level, there are no slot or module placement restrictions for optical working/protection.) OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 W W W W OC-192/STM-64 (Note: Not available on the Traverse 600.) EC-3/STM-1E 1:2 equipment protection with a 4-slot ECM EC-3/STM-1E O W P W/ EC-3/STM-1E 1:1 equipment protection with a 3-slot ECM EC-3/STM-1E O P/O W/P W EC-3/STM-1E 1:1 equipment protection with a 4-slot ECM Appendix A Module Placement Planning and Guidelines Traverse 600 Module Placement

426 Page 9-18 Turin Networks Release OPS3.1.x Table 9-5 Traverse 600 Module Placement Guidelines (continued) Module Type EC-3/STM-1E O P W O EC-3/STM-1E unprotected with a 3-slot ECM EC-3/STM-1E O O W/O W EC-3/STM-1E unprotected with a 4-slot ECM EC-3/STM-1E O W O W ETHERNET 1:1 equipment protection with a 2-slot Ethernet Protection ECM NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo ETHERNET unprotected with a 2-slot 10/100BaseT ECM NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo ETHERNET unprotected with a 2-slot Ethernet (Protection) ECM Traverse 600 Slot Numbers P W/P W/P W W W W W Node Operations and Maintenance Guide, Section 9: Appendices Traverse 600 Module Placement

427 Release OPS3.1.x Turin Networks Page 9-19 Table 9-5 Traverse 600 Module Placement Guidelines (continued) NGE and NGE Plus: GbE [LX, SX] plus 10/100BaseTX Combo [CEP] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP] NGE only: GbE CWDM plus 10/100BaseTX Combo GbE SX plus GbE CWDM plus 10/100BaseTX Combo TDM 1:2 equipment protection with the corresponding ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 2-slot ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 3-slot ECM DS3/E3/EC-1 CC DS3/EC-1 Transmux TDM unprotected with the corresponding ECM DS1 E1 O W/O W/O W W W/P W/P W W/P W/P W/P W/P W/P/O W/P/O W/P/O W/P/O W W W W TDM unprotected with a 2-slot DS3/E3 ECM (Note: The module placement restriction is due to the electrical connector module.) DS3/E3/EC-1 CC DS3/EC-1 Transmux Module Type Traverse 600 Slot Numbers O W/O W/O W Appendix A Module Placement Planning and Guidelines Traverse 600 Module Placement

428 Page 9-20 Turin Networks Release OPS3.1.x Table 9-5 Traverse 600 Module Placement Guidelines (continued) TDM unprotected with a 3-slot DS3/E3 ECM (Note: the module placement restriction is due to the electrical connector module.) DS3/E3/EC-1 CC DS3/EC-1 Transmux Module Type O W/O W W VT/VC Switching with 1:N Equipment Protection (Note: No ECM requirement with VT/VC switching modules.) VT/TU 5G Switch W/P W/P W/P W/P OC-48/STM-16 with VTX 2 W/P W/P W/P W/P VT/VC Switching without Equipment Protection Traverse 600 Slot Numbers VT/TU 5G Switch W W W W OC-48/STM-16 with VTX W W W W 1 Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with a Enhanced GCM for GCM redundancy. 2 While the VTX Switch can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1 APS, UPSR, or BLSR protection group. Important: Place an OC-N/STM-N or wide blank faceplate between any 10/100BaseTX-inclusive module and an electrical module (of another type) if the 10/100BaseTX-inclusive module is placed to the right of an electrical interface module. A blank faceplate or OC-N/STM-N module is not required if the 10/100BaseTX-inclusive module is placed to the left of an electrical module. Important: Place wide blank faceplates in empty slots to ensure EMI protection and proper cooling. Node Operations and Maintenance Guide, Section 9: Appendices Traverse 600 Module Placement

429 SECTION 9APPENDICES Appendix B Traverse SNMP v1/v2c Agent and MIBs Introduction Supported Traverse SNMP MIBs Turin supports an SNMP agent directly on the Traverse system and provides limited standard MIB support for Ethernet module ports. Note: There is no relationship between the TransNav server and Traverse system SNMP agents. The configuration of the Traverse system SNMP agent (community strings, trap destinations) is not coordinated in any way. Important: The Traverse SNMP agent access is available on a physical node; Preprovisioned support for the SNMP agent is unavailable. This chapter includes information about the subnetwork management protocol (SNMP) on a Traverse network element: Supported Traverse SNMP MIBs, page 9-21 Configure the Traverse SNMP Agent Parameters from TransNav, page 9-22 Location of SNMP MIB File, page 9-23 For specific configuration information, The Traverse SNMP northbound interface implements the SNMP v1 and SNMP v2c protocols and maintains a Turin-proprietary MIB. SNMP v2c uses the same security model as v1, and adds two main features: the ability to GET large amounts of management data in a single request (GETBULK operation), and support for 64-bit counters. The Traverse SNMP agent supports these MIBs: Note: The list below does not reflect the set of MIBs supported by the TransNav SNMP agent. The Traverse MIB set supports the direct management of Traverse nodes by third-party applications, such as HP OpenView. RFC 1213: System group of MIB-II RFC 2737: Physical Entity table of Entity MIB, Version 2 RFC 2863: The Interfaces Group MIB used for physical Ethernet interfaces only, the Interfaces and Extension Interfaces tables Turin enterprise (proprietary) SNMP MIB: EMS Alert table Set of traps All counters are copies of Traverse PM 24-hour counters and is consistent with the way the TransNav MIBs support counters. Release OPS3.1.x Turin Networks Page 9-21

430 Node Operations and Maintenance Guide, Section 9: Appendices Configure the Traverse SNMP Agent Parameters from TransNav Configure the Traverse SNMP Agent Parameters from TransNav Turin supports an SNMP agent directly on the Traverse system. The Traverse SNMP agent access is available on a physical node only; Preprovisioned support for the SNMP agent is unavailable. The Traverse SNMP agent port 161 sends and receives management data to the SNMP management stations. Note: There is no relationship between the TransNav management server and Traverse system SNMP agents. The configuration of the Traverse system SNMP agent (community strings and trap destinations) is not coordinated in any way. From Map View, select a node. From the Admin menu, click SNMP Configuration. Figure 9-1 Admin Menu SNMP Configuration The Node SNMP Configuration screen displays: Figure 9-2 Node SNMP Configuration Screen The Node SNMP Configuration screen allows you to view and change the following Traverse node SNMP configuration information: Node ID 1 : Displays the user-defined node name entered during node commissioning. Node IP 1 : Displays the node IP address entered during node commissioning. 1 Set through the CLI during node commissioning. Page 9-22 Turin Networks Release OPS3.1.x

431 Appendix B Traverse SNMP v1/v2c Agent and MIBs Location of SNMP MIB File Read Community: An alpha-numeric character string that provides an SNMP management station with read-only access to the Traverse SNMP agent. Public is the default string. Note: For each of the alpha-numeric character string parameters, there is a corresponding Confirm parameter to check for matching string entry. Write Community: An alpha-numeric character string that provides an SNMP management station with read and write access to the Traverse SNMP agent. Public is the default string. Trap Destination [1 through 4]: Enter the unique IP address assigned by a network administrator of the SNMP management station to receive management data. There are up to four possible trap destinations. Trap Destination [1 through 4] Community: An alpha-numeric character string (corresponding to the Read or Write Community string) that provides the Trap Destination Community with specific access rights to the Traverse SNMP agent. Public is the default string. Trap Destination [1 through 4] Port Number: The SNMP management station port that receives management data from the Traverse SNMP agent. The default is 162. The command buttons are: Apply: Click Apply to save changes and return to the main screen. Done: Click Done to cancel any changes and return to the main screen. Location of SNMP MIB File The Turin enterprise (proprietary) SNMP MIB (filename=ems.mib) file is located in the same directory where you installed the server application. Release OPS3.1.x Turin Networks Page 9-23

432 Node Operations and Maintenance Guide, Section 9: Appendices Location of SNMP MIB File Page 9-24 Turin Networks Release OPS3.1.x

433 INDEX Numerics 1:1 equipment protection module placement, 9-1 1:2 equipment protection module placement, 9-1 1:N equipment protection module placement, /100BaseTX precaution statement module placement, 8-20, /100BaseTX port performance monitoring, 2-59 A Access Identifier (AID) test access, 5-2, 5-5 ACO alarm cutoff, 1-20 ACO_CLEAR clear alarm cutoff, 1-20 Activate software protected modules, 7-30 unprotected modules, 7-33 Activate time, 7-21, 7-22, 7-24, 7-30, 7-36, 7-45, 7-62, 7-63, 7-64, 7-65 Activation status, 7-23, 7-31, 7-63, 7-64 Activation type, 7-31 Active Hop, 1-11, 1-14, 2-11, 2-13 Administrative state card or port, 4-18 ADMINTASK Administrative task, 1-20 AID, see Access Identifier (AID) Air filters cooling function, 6-2 replacement, 6-7 AIRCOND air contitioning system failed, 1-20 AIRDRYR air dryer fail, 1-20 AIS-L DS port alarm, 1-20 AIS-P DS port alarm, 1-21 AIS-S Alarm indication signal Service, 1-21 AIS-V DS port alarm, 1-21 AIS-VC sdh port alarm, 1-22 Alarm and event default severity levels, 1-1, 1-19 Alarm indication signal seconds DS1 port, 2-18 E1 port, 2-37 Alarm management customization, 1-6 Alarm profile creation, 1-7 DS1 port, 1-8 DS3 port, 1-8 DS3 EC3 port, 1-8 E1 port, 1-8 E3 port, 1-8 eos ctp, 1-8 eos port, 1-8 GbE port, 1-8 lag, 1-8 Mux, 1-8 probable cause, 1-6 sdh eos ctp, 1-8 sdh eos port, 1-8 sdh high order path, 1-8 sdh low order path, 1-8 SDH port, 1-8 server, 1-8 shelf, 1-8 SONET port, 1-8 sonet sts, 1-8 sonet vt, 1-8 synchronize, 1-9 Alarm reporting hierarchy, 1-6 Alarms ACO, 1-20 ACO (shelf), 1-20 ACO_CLEAR, 1-20 ACO_CLEAR (shelf), 1-20 ADMINTASK, 1-20 AIRCOND, 1-20 AIRCOND (shelf), 1-20 AIRDRYR, 1-20 AIRDRYR (shelf), 1-20 AIS-L (DS port), 1-20 AIS-L (port, shelf), 1-20 AIS-P (DS port), 1-21 AIS-P (port), 1-21 AIS-V (DS port), 1-21 Release OPS3.1.x Turin Networks Index-1

434 Index AIS-VC (port), 1-22 AIS-VC (sdh port), 1-22 ALS, 1-22 ALS (port), 1-22 ALS-TX-OFF, 1-22 ALS-TX-OFF (port), 1-22 APSAISCLEAR, 1-23 APS-AIS-P, 1-22 APSB (port), 1-23 APSBF (port), 1-23 APSCFGMIS (port), 1-23 APSCM (MSP) (port), 1-23 APSDICLEAR, 1-25 APSIMP (MSP) (port), 1-23 APSINC (MSP) (port), 1-24 APSLOP, 1-24 APSLOPCLEAR, 1-24 APS-LOP-P, 1-22 APSLOSCLEAR, 1-24 APSMM (port), 1-24 APSPATHCLEAR, 1-24 APSPDI, 1-25 APSREL (MSP) (shelf), 1-25 APSREL (shelf), 1-25 APS-SDBER-P, 1-22 APSSDCLEAR, 1-25 APS-SFBER-P APS-SFBER-P, 1-22 APSUNEQCLEAR, 1-25 APS-UNEQ-P, 1-23 APSWTR (MSP) (shelf), 1-26 APSWTR (shelf), 1-26 AU-AIS (optical port), 1-26 AU-AIS (port), 1-26 AU-LOP (port), 1-26 AU-LOP (SDH port), 1-26 AUTHFAIL, 1-26 automatic protection switching (APS), 1-5 AUTOPRV, 1-26 AUTO-TX-ON, 1-27 AUTO-TX-ON (port), 1-27 BADPKTRX, 1-27 BATDSCHRG (shelf), 1-27 BATTERY (shelf), 1-27 BERSD-L (EC-1 port), 1-28 BERSD-L (port, shelf), 1-28 BERSD-P (EC-1 port), 1-29 BERSD-P (port), 1-29 BERSD-V (DS1 port), 1-30 BERSD-V (port), 1-30 BERSD-VC (port), 1-30 BERSD-VC (sdh port), 1-30 BERSF-L (EC-1 port), 1-31 BERSF-L (port, shelf), 1-31 BERSF-P (EC-1 port), 1-32 BERSF-P (port), 1-32 BERSF-V (DS1 port), 1-33 BERSF-V (port, shelf), 1-33 BERSF-VC (port), 1-33 BERSF-VC (sdh port), 1-33 BITSA-FRC, 1-33 BITSA-FRC (shelf), 1-33 BITSA-LOCK, 1-34 BITSA-LOCK (shelf), 1-34 BITSA-MAN, 1-34 BITSA-MAN (shelf), 1-34 BITSB-FRC, 1-34 BITSB-FRC (shelf), 1-34 BITSB-LOCK, 1-34 BITSB-LOCK (shelf), 1-34 BITSB-MAN, 1-34 BITSB-MAN (shelf), 1-34 BITSGEN, 1-34 BITSRBOC, 1-34 BLSR_NOT_SYNC (server), 1-34 BLSR_SYNC_UNKNOWN, 1-34 BLSR_SYNC_UNKNOWN (server), 1-34 BOARDFAIL, 1-34 BOARDFAIL (ta200), 1-34 BPSIG, 1-35 BPSIG (shelf), 1-35 categories of, 1-2 CFGERR, 1-35 CLEAR (shelf), 1-35 CLFAIL, 1-35 CLFAIL (shelf), 1-35 CLFAN, 1-35 CLFAN (shelf), 1-35 CLRLOOP (all ports), 1-35 CLRLOOP (shelf), 1-35 COM (server), 1-35 COM (ta200), 1-35 COM (te50), 1-35 CONTROL, 1-36 CONTROL (te50), 1-36 CTS, 1-36 CTS (te50), 1-36 DBCRPT (server), 1-37 DBCRPT (shelf), 1-37 DBFAIL (server), 1-37 DBFAIL (shelf), 1-37 DBMIS (server, shelf), 1-37 DBRED (server, shelf), 1-37 DBSIGN (port, server, shelf), 1-38 DCCFAIL (EC-1 port), 1-38 DCCFAIL (port), 1-38 Index-2 Turin Networks Release OPS3.1.x

435 Index default severities, 4-2 default severity levels, 1-19 DS1 AIS (DS1 port), 1-39 DS1 LOF (DS1 port), 1-39 DS1 LOS (DS1 port), 1-39 DS1 RAI (DS1 port), 1-40 DS1AIS (port), 1-39 DS1LOF (port), 1-39 DS1LOS (port), 1-39 DS1RAI (port), 1-40 DS3 AIS (DS port), 1-40 DS3 RAI (DS3 port), 1-40 DS3AIS (port), 1-40 DS3RAI (port), 1-40 DSR (te50), 1-40 DTR (te50), 1-40 E1 AIS (E1 port), 1-40 E1 LOM CAS (E1 port), 1-40 E1 LOM CRC (E1 port), 1-40 E1 RAI (E1 port), 1-41 E1AIS (port), 1-40 E1LOMCAS (port), 1-40 E1LOMCRC (port), 1-40 E1RAI (port), 1-41 E3 AIS (E3 port), 1-41 E3 AIS (port), 1-41 E3 RAI (E3 port), 1-41 E3 RAI (port), 1-41 EFMFAIL (shelf), 1-41 ENGINE (shelf), 1-41 ENGOPRG (shelf), 1-41 EQCOMM (shelf), 1-41 EQFAIL (server), 1-42 EQINV (shelf), 1-41 EQLOCK (shelf), 1-42 EQMIS (shelf), 1-42 EQPT (server, shelf), 1-42 EQRMV (shelf), 1-43 ERFI-V (DS1 port), 1-43 ERFI-V (port), 1-43 EXER_SWITCH (shelf), 1-43 EXPLGS (shelf), 1-43 EXT2-REF1-ALM, 1-44 EXTA-REF1-ALM, 1-43 EXTA-REF1-ALM (shelf), 1-43 EXTA-REF2-ALM, 1-43 EXTA-REF2-ALM (shelf), 1-43 EXTA-REF3-ALM, 1-44 EXTA-REF3-ALM (shelf), 1-44 EXTA-REF4-ALM, 1-44 EXTA-REF4-ALM (shelf), 1-44 EXTB-REF1-ALM (shelf), 1-44 EXTB-REF2-ALM, 1-44 EXTB-REF2-ALM (shelf), 1-44 EXTB-REF3-ALM, 1-44 EXTB-REF3-ALM (shelf), 1-44 EXTB-REF4-ALM, 1-44 EXTB-REF4-ALM (shelf), 1-44 FANCOMM (shelf), 1-45 FANCOND (shelf), 1-45 FANFLTR (shelf), 1-45 FANRMV (shelf), 1-45 FEP, 1-45 FILE_UPLOAD (shelf), 1-45 filtering, 1-17 FIRDETR (shelf), 1-45 FIRE (shelf), 1-45 FLOOD (shelf), 1-45 FLOW-DEGRADED (port), 1-46 FLOW-LEARNED (port), 1-46 FLOWS-UNLEARNED (port), 1-46 FLOW-UNPROTECTED (port), 1-46 FOPR (eos), 1-46 FOPR (port), 1-46 FOPT (eos), 1-46 FOPT (port), 1-46 FORCE_ONLINE (ta200), 1-47 FORCED (shelf), 1-47 FORCED_ON_EAST (shelf), 1-48 FORCED_ON_PROT (shelf), 1-47 FORCED_ON_SECT1 (shelf), 1-47 FORCED_ON_SECT2 (shelf), 1-48 FORCED_ON_WEST (shelf), 1-48 FORCED_ON_WORK (shelf), 1-48 FUSE (shelf), 1-48 GENFAIL (shelf), 1-48 GFPLOF, 1-48 GFPLOF (shelf), 1-48 GIDERR (shelf), 1-49 GIDM (eos), 1-49 GIDM (port), 1-49 H4-LOM, 1-49 H4-LOM (port), 1-49 HIAIR (shelf), 1-49 HIGHHMD (shelf), 1-49 HIHUM (shelf), 1-49 HITEMP (shelf), 1-50 HIWTR (shelf), 1-50 HP-BERSD (optical port), 1-50 HP-BERSD (port), 1-50 HP-BERSF (optical port), 1-51 HP-BERSF (port), 1-51 HP-LOM, 1-51 HP-LOM (port), 1-51 HP-MND, 1-51 HP-MND (port), 1-51 Release OPS3.1.x Turin Networks Index-3

436 Index HP-PLM (optical port), 1-51 HP-PLM (port), 1-51 HP-RDI (optical port), 1-52 HP-RDI (port), 1-52 HP-RFI (optical port), 1-52 HP-RFI (port), 1-52 HP-RFICON (port), 1-52 HP-RFIPAY (port), 1-52 HP-RFISVR (port), 1-52 HP-SQM, 1-51 HP-SQM (port), 1-51 HP-TIM (optical port), 1-52 HP-TIM (port), 1-52 HP-UNEQ (optical port), 1-53 HP-UNEQ (port), 1-53 HWFAULT (shelf), 1-53 IDLE (DS port), 1-53 IDLE (port), 1-53 INCOMPATSW (server), 1-53 INCOMPATSW (server, shelf), 1-53 INCOMPATSW (shelf), 1-53 INDICATION (te50), 1-54 INTRUDER (shelf), 1-53 KBYTE (optical port), 1-54 KBYTE (port), 1-54 LBC, 1-57 LBC (port, shelf), 1-57 LCAS-REM (vc bundle), 1-57 LCAS-RES (vc bundle), 1-57 LEAK (shelf), 1-57 LFD (eos), 1-57 LFD (port), 1-57 LINK_FRCD_DIS (Ethernet port), 1-58 LINK_FRCD_DIS (port), 1-58 LINKFAIL (Ethernet port), 1-58 LINKFAIL (port), 1-58 LO_LBC (SFP optical port), 1-60 LO_OPR (SFP optical port), 1-60 LO_OPT (SFP optical port), 1-60 LO_TEMP (SFP optical port), 1-60 LO_VCC (SFP optical port), 1-60 LOA (eos), 1-60 LOA (port), 1-60 LOCK_WORK1 (shelf), 1-61, 1-62, 1-63 LOCK_WORK10 (shelf), 1-61 LOCK_WORK11 (shelf), 1-61 LOCK_WORK12 (shelf), 1-61 LOCK_WORK13 (shelf), 1-61 LOCK_WORK14 (shelf), 1-62 LOCK_WORK2 (shelf), 1-62 LOCK_WORK3 (shelf), 1-62 LOCK_WORK4 (shelf), 1-62 LOCK_WORK5 (shelf), 1-62 LOCK_WORK6 (shelf), 1-62 LOCK_WORK7 (shelf), 1-63 LOCK_WORK8 (shelf), 1-63 LOCK_WORK9 (shelf), 1-63 LOCKOUT (shelf), 1-60 LOCKOUT-LPS (shelf), 1-61 LOF (DS port), 1-64 LOF (port, shelf), 1-64 LOG (eos), 1-64 LOG (port), 1-64 LOGINFAIL, 1-65 LOGINFAIL (server, shelf), 1-65 LOGINSUCC, 1-65 LOGINSUCC (server, shelf), 1-65 LOGINTERM, 1-65 LOGINTERM (server, shelf), 1-65 LOL (te50), 1-65 LO-LBC (port), 1-60 LOM-P (eos), 1-65 LOM-P (port), 1-65 LOM-V (eos), 1-65 LOM-V (port), 1-65 LO-OPR (port), 1-60 LO-OPT (port), 1-60 LOP-P (DS port), 1-66 LOP-P (port), 1-66 LOS (DS port), 1-67 LOS (port, shelf), 1-67 LO-TEMP (port), 1-60 LO-VCC (port), 1-60 LP-BERSD (optical port), 1-68 LP-BERSF (optical port), 1-68 LP-LOM (eos), 1-69 LP-MND (eos), 1-69 LP-PLM (optical port), 1-70 LP-RDI (optical port), 1-70 LP-RFI (optical port), 1-70 LP-RFICON (optical port), 1-70 LP-RFIPAY (optical port), 1-70 LP-RFISVR (optical port), 1-70 LP-SQM (eos), 1-71 LP-TIM (optical port), 1-71 LP-UNEQ (optical port), 1-71 MAN_ON_PROT (shelf), 1-72 MAN_ON_WORK, 1-72 MAN-TX-OFF, 1-72 MAN-TX-ON, 1-72 MANUAL (shelf), 1-72 MND-P (eos), 1-72 MND-V (eos), 1-72 MS-AIS (optical port), 1-73 MS-BERSD (optical port), 1-73 MS-BERSF (optical port), 1-74 Index-4 Turin Networks Release OPS3.1.x

437 Index MS-RDI (optical port), 1-74 MSSP_NOT_SYNC, 1-74 multiplex section protection (MSP), 1-5 NETSYNC (server), 1-75 NODEEQMIS (server), 1-75 NODEMIS (optical port), 1-75 NODESYNC (server), 1-76 NO-REMOTE-LCAS, 1-76 NPM (eos), 1-76 OPR, 1-76 OPT, 1-76 OVERTEMP (shelf), 1-77 OVERVOLTAGE_A (shelf), 1-77 OVERVOLTAGE_B (shelf), 1-77 PCASQLCH (optical port), 1-77 PDI-n, 1-78 PDI-n (n, 1-77 PDI-n (n>4), 1-78 PLC (lag), 1-78 PLCR (eos), 1-78 PLCT (eos), 1-78 PLINESQL (optical port), 1-79 PLM (DS port), 1-79 PLM-V (DS port), 1-79 PLM-V (optical port), 1-79 PLM-V (shelf), 1-79 PLM-VC (optical port), 1-79 PMCFG (all ports), 1-80 PMDATALOST, 1-80 PUMPFAIL (shelf), 1-80 PWFAIL-A (shelf), 1-80 PWFAIL-B (shelf), 1-80 QEFAIL (shelf), 1-80 recommended actions, 1-19 RECTFAIL (shelf), 1-80 RECTHIGH (shelf), 1-81 RECTLOW (shelf), 1-81 REMOTE-LINKFAIL, 1-81 reporting, 1-2 RESOURCE_MISMATCH (shelf), 1-81 RFICON (DS port), 1-84 RFICON (port), 1-84 RFICON-V (DS port), 1-84 RFICON-V (port), 1-84 RFICON-VC (port), 1-84 RFI-L (EC-1 port), 1-82 RFI-L (port), 1-82 RFI-P (EC-1 port), 1-82 RFI-P (port), 1-82 RFIPAY (DS port), 1-85 RFIPAY (port), 1-85 RFIPAY-V (DS port), 1-85 RFIPAY-V (port), 1-85 RFIPAY-VC (optical port), 1-85 RFISVR (DS port), 1-86 RFISVR (port), 1-86 RFISVR-V (DS port), 1-86 RFISVR-V (port), 1-86 RFISVR-VC (port), 1-86 RFI-V (DS1 port), 1-83 RFI-V (port), 1-83 RFI-VC (optical port), 1-83 RS-TIM, 1-87 SERVER_LOGINFAIL, 1-87 SETOPER, 1-87 severity levels default, 1-1 SFO (optical port), 1-87 SFO (port alarm), 1-87 SFPMIS, 1-88 SFPRMV, 1-88 SHELFMIS (server), 1-88 SMOKE (shelf), 1-88 SQLCHTBL (optical port), 1-88 SQM, 1-88 SQM-P (eos), 1-88 SQM-V (eos), 1-89 SSF, 1-89 StickyMode, 1-18 SVC_ERROR, 1-89 SW_UPG (shelf), 1-90 SWCRPT, 1-89 SWERR (all ports), 1-89 SWITCH (Ethernet port), 1-89 SWITCH (shelf), 1-90 SWITCH_TO_PROT (shelf), 1-89 SWITCH_TO_SECT1 (shelf), 1-89 SWITCH_TO_SECT2 (shelf), 1-90 SWMIS (all ports), 1-90 SYNCFAIL (optical port), 1-90 SYSREF, 1-90 TA200_COM, 1-91 TCA (port), 1-92 TEMP, 1-92 TEMPCRIT (shelf), 1-92 TEMPWARN (shelf), 1-92 TIM (port), 1-92 TIMEDOUT (shelf), 1-93 TIMEOUTWARN (shelf), 1-93 TIM-P (port), 1-92 TIM-S (port), 1-93 TIM-V (port), 1-93 TIU-V (port), 1-93 TIU-V (shelf), 1-93 TLC (lag), 1-94 TLCR (eos), 1-94 TLCT (eos), 1-94 TOOMANYEVENTS (server), 1-94 Release OPS3.1.x Turin Networks Index-5

438 Index TOPOMIS (optical port), 1-94 TOXIC (shelf), 1-94 TSSALM (shelf), 1-97 TSS-EXTA-OOB-A, 1-94 TSS-EXTA-OOB-B, 1-94 TSS-EXTB-OOB-A, 1-94 TSS-EXTB-OOB-B, 1-94 TSS-FRC (shelf), 1-95 TSS-FREERUN-GCMA (shelf), 1-95 TSS-FREERUN-GCMB (shelf), 1-95 TSSGEN (shelf), 1-97 TSS-HOLDOVER-GCMA, 1-95 TSS-HOLDOVER-GCMB, 1-95 TSS-LINE1-OOB-GCMA, 1-95, 1-96 TSS-LINE1-OOB-GCMB, 1-95 TSS-LINE2-OOB-GCMA, 1-95 TSS-LINE2-OOB-GCMB, 1-95 TSS-LINE3-OOB-GCMA, 1-96 TSS-LINE3-OOB-GCMB, 1-96 TSS-LINE4-OOB-GCMB, 1-96 TSS-LOCK (shelf), 1-96 TSS-MAN (shelf), 1-96 TSSREF, 1-97 TSS-REF1-ALM (shelf), 1-96 TSS-REF2-ALM (shelf), 1-96 TSS-REF3-ALM (shelf), 1-96 TSS-REF4-ALM (shelf), 1-97 TSS-REFL-GCMA (shelf), 1-97 TSS-REFL-GCMB (shelf), 1-97 TSS-REFS (shelf), 1-97 TSSSETS (shelf), 1-97 TSS-SSM (shelf), 1-97 TU-AIS (optical port), 1-21, 1-98 TU-LOP (optical port), 1-98 types of, 1-2 UNDERVOLTAGE_A (shelf), 1-99 UNDERVOLTAGE_B (shelf), 1-99 UNEQ, 1-99 UNEQ-P (port), 1-99 UNEQ-V (port, shelf), UNEQ-VC (optical port), UP (all ports), VCC, VENTFAIL (shelf), viewing, 1-6 WARMREBOOT, X86_ABORT, X86_CRC, XPT-FAIL-RX, XPT-FAIL-TX, XPTRX (lag), XPTTX (lag), AlarmsAIS-S, 1-21 ALS alarm, 1-22 ALS-TX-OFF alarm, 1-22 APS-AIS, 1-22 APSAISCLEAR, 1-23 APSDICLEAR, 1-25 APSLOPCLEAR, 1-24 APS-LOP-P, 1-22 APSLOS, 1-24 APSLOSCLEAR, 1-24 APSPATHCLEAR, 1-24 APSPDI, 1-25 APSREL shelf alarm, 1-25 APS-SDBER-P, 1-22 APSSDCLEAR, 1-25 APSUNEQCLEAR, 1-25 APS-UNEQ-P, 1-23 APSWTR shelf alarm, 1-26 AU-AIS optical port alarm, 1-26 AU-LOP SDH port alarm, 1-26 AUTHFAIL, 1-26 AUTOPRV, 1-26 AUTO-TX-ON alarm, 1-27 B Background block error ratio E1 port, 2-37 E3 port, 2-40 Background block errors E1 port, 2-37 E1 port, far end, 2-38 E3 port, 2-39 LO VC3 path, 2-42 LO VC3 path, far end, 2-44 SDH port MS, 2-46 SDH port MS, far end, 2-49 SDH port RS, 2-45 VC11 path, 2-50 VC11 path, far end, 2-52 VC12 path, 2-50 VC12 path, far end, 2-52 VC3 path, 2-42 VC3 path, far end, 2-44 VC4 path, 2-42 VC4 path, far end, 2-44 Backward compatibility software, 7-4, 7-51, 8-2 Index-6 Turin Networks Release OPS3.1.x

439 Index BADPKTRX, 1-27 Base path, 7-13, 7-58 BATDSCHRG shelf alarm, 1-27 BATTERY shelf alarm, 1-27 BERSD-L EC-1 port alarm, 1-28 BERSD-P EC-1 port alarm, 1-29 BERSD-V DS1 port alarm, 1-30 BERSD-VC sdh port alarm, 1-30 BERSF-L EC-1 port alarm, 1-31 BERSF-P EC-1 port alarm, 1-32 BERSF-V DS1 port alarm, 1-33 BERSF-VC sdh port alarm, 1-33 BITSA-FRC, 1-33 BITSA-LOCK, 1-34 BITSA-MAN, 1-34 BITSB-FRC, 1-34 BITSB-LOCK, 1-34 BITSB-MAN, 1-34 BITSGEN, 1-34 BITSRBOC, 1-34 BLSR_NOT_SYNC server alarm, 1-34 BLSR_SYNC_UNKNOWN, 1-34 BOARDFAIL, 1-34 BPSIG, 1-35 Bulk service activation unavailable resources, C Captive fasteners PDAP-2S, 6-14 PDAP-4S, 6-19 Circuit breaker PDAP-2S replacing, 6-11 Circuit breaker, PDAP-2S toggle switch, 6-12 Cleaning MPX connectors, 8-16 CLEAR shelf alarm, 1-35 Clear activation time, 7-24, 7-64 download time, 7-16, 7-60 CLFAIL, 1-35 CLFAN, 1-35 CLI node commands exec node database backup, 6-24 CLRLOOP all ports alarm, 1-35 Coding violations DS1 port, 2-18, 2-19 DS3 port, 2-21 (CBit), 2-22 (CBit), far end, 2-23 (PBit), 2-21 E1 port, 2-36 E3 port, 2-39 Line EC1 port, 2-24 Line, far-end EC1 port, 2-25 Section EC1 port, 2-24 SONET line, 2-27 SONET line, far end, 2-29 SONET path, 2-31 SONET path, far end, 2-32 SONET section, 2-27 SONET VT path, 2-33 SONET VT path, far end, 2-34 COM server alarm, 1-35 Compatibility alarms, 7-4, 7-51, 8-2 product compatibility matrix, 7-4, 7-51, 8-2 replacement modules, 7-4, 7-51, 8-2 software, 7-4, 7-51, 8-2 software version, 7-4, 7-51, 8-2 Connectors, cleaning, 8-16 CONTROL, 1-36 Controlled slip seconds DS1 port, 2-19 DS1 port, far end, 2-20 Creating alarm profiles, 1-7 PM templates, 2-2 Critical alarm, see LEDs CTS, 1-36 Current SW version, 7-23, 7-24, 7-31, 7-63, 7-64 CVFE coding violations, far end line, 2-25 D DBCRPT server alarm, 1-37 DBFAIL Release OPS3.1.x Turin Networks Index-7

440 Index shelf alarm, 1-37 DCCFAIL EC-1 port alarm, 1-38 Deactivate Ethernet Services, 7-43 Default alarm and event severity levels, 1-1, 1-19 Default severities, alarms, 4-2 Default values, 6-24 DFAD dual facility access digroup, test access, 5-2 Diagnostics environmental alarm conditions, incorrect, 4-1 loopback tests, 4-9 transmit and receive signal levels, 4-3, 4-7 Disabled operational state card or port, 4-18 Download archive from Infocenter, 7-3, 7-10, 7-50, 7-54 time by module, 7-14, 7-59 DS1 facility loopback, 4-10, 4-11 port alarm profile, 1-8 terminal loopback tests, 4-10 DS1 AIS DS1 port alarm, 1-39 DS1 LOF DS1 port alarm, 1-39 DS1 LOS DS1 port alarm, 1-39 DS1 port alarm profile, 1-8 facility loopback tests, 4-10 performance monitoring, 2-18 FE CCS_P, 2-20 FE ES_L, 2-19 FE ES_P, 2-19 FE FC_P, 2-20 FE SEF_P, 2-20 FE SES_P, 2-20 FE UAS_P, 2-20 NE AISS_P, 2-18 NE CSS_P, 2-19 NE CV_L, 2-18 NE CV_P, 2-18, 2-19 NE ES_L, 2-18 NE ES_P, 2-18 NE FC_L, 2-19 NE LOSS_L, 2-18 NE SAS_P, 2-19 NE SES_L, 2-18 NE SES_P, 2-18 NE UAS_P, 2-19 DS1 RAI DS1 port alarm, 1-40 DS3 facility loopback, 4-10, 4-11 terminal loopback tests, 4-10 DS3 AIS DS port alarm, 1-40 DS3 CC facility loopback tests, 4-10, 4-11 DS3 port alarm profile, 1-8 performance monitoring, 2-21, 2-36 FE CVC-P (CBit), 2-23 FE ESC-P (CBit), 2-23 FE FC-P (PBit), 2-23 FE SESC-P (CBit), 2-23 FE UASC-P (CBit), 2-23 NE CVC-P (CBit), 2-22 NE CV-L, 2-21 NE CV-P (PBit), 2-21 NE ESC-P (CBit), 2-22 NE ES-L, 2-21 NE ES-P (PBit), 2-21 NE FC-P (PBit), 2-22 NE SESC-P (CBit), 2-22 NE SES-L, 2-21 NE SES-P (PBit), 2-21 NE UASC-P (CBit), 2-22 NE UAS-P (PBit), 2-21 DS3 RAI DS3 port alarm, 1-40 DS3 TMUX facility loopback tests, 4-10 DS3/E3/EC-1 12-port, 8-10, port, 8-10, 9-2 module placement, 8-10, 9-2 DS3/EC-1 Transmux, 8-10, 9-2 DS3/EC-1 port facility loopback tests, 4-10 DS3 EC3 port alarm profile, 1-8 DSC CC terminal loopback tests, 4-10 DSC TMUX terminal loopback tests, 4-10 Dual facility access digroup DFAD test access point, 5-2 E E1 AIS E1 port alarm, 1-40 E1 LOM CAS E1 port alarm, 1-40 Index-8 Turin Networks Release OPS3.1.x

441 Index E1 LOM CRC E1 port alarm, 1-40 E1 port alarm profile, 1-8 facility loopback, 4-12 facility loopback tests, 4-10, 4-12 performance monitoring, 2-36 FE BBE_P, 2-38 FE ES_L, 2-38 FE ES_P, 2-38 FE FC_P, 2-38 FE SES_P, 2-38 FE UAS_P, 2-38 NE AISS_P, 2-37 NE BBE_P, 2-37 NE BBER_P, 2-37 NE CV_L, 2-36 NE EB_P, 2-36, 2-38 NE ES_L, 2-36 NE ES_P, 2-37 NE ESR_P, 2-37 NE FAS_L, 2-36 NE FC_L, 2-36 NE LOSS_L, 2-36 NE SES_L, 2-36 NE SES_P, 2-37 NE SESR_P, 2-37 NE UAS_P, 2-37 terminal loopback, 4-12 E1 RAI E1 port alarm, 1-41 E3 AIS E3 port alarm, 1-41 E3 port alarm profile, 1-8 facility loopback, 4-12 facility loopback tests, 4-10, 4-12 performance monitoring, 2-39 FE EB_P, 2-40, 2-41 FE ES_P, 2-40 FE SES_P, 2-40 FE UAS_P, 2-41 NE BBE_P, 2-39 NE BBER_P, 2-40 NE CV_L, 2-39 NE EB_P, 2-39 NE ES_L, 2-39 NE ES_P, 2-39 NE ESR_P, 2-39 NE FC_P, 2-40 NE SES_L, 2-39 NE SES_P, 2-39 NE SESR_P, 2-40 NE UAS_P, 2-39 terminal loopback, 4-12 E3 RAI E3 port alarm, 1-41 EAM, see Environmental Alarm Module EC1 port facility loopback tests, 4-10 performance monitoring, 2-24 terminal loopback tests, 4-10 EC-3 terminal loopback tests, 4-11 EC-3 STM-1E 1 1 protection with ECM, 9-7, 9-8, 9-12, 9-13, protection with 4-slot ECM, 9-7, 9-12, 9-17 unprotected with 3-slot ECM, 9-8, 9-13, 9-18 unprotected with 4-slot ECM, 9-8, 9-13, 9-18 EFMFAIL shelf alarm, 1-41 Electrical and optical signals, monitoring, 2-1 Electrostatic discharge protection (ESD), 8-5 EMS service error codes, 1-105, software compatibility, 8-2 EMSI mux, 2-8 Enabled operational state card or port, 4-18 Environmental Alarm Module (EAM) guides, 6-21 plastic standoff replacing, 6-20 Environmental alarms observing incorrect conditions, 4-1 symptom, incorrect input/output, 4-2 EOS performance monitoring GFP FCS DISCARDS, 2-56 RX BROADCAST, 2-56 RX BYTES, 2-56, 2-57 RX FRAMES, 2-56 RX MTU DISCARDS, 2-57 RX MULTICAST, 2-56 RX UNICAST, 2-56 TX BROADCAST, 2-56 TX BYTES, 2-56 TX DISCARDS, 2-56 TX FRAMES, 2-56 TX UNICAST, 2-56 EOS ctp Release OPS3.1.x Turin Networks Index-9

442 Index alarm profile, 1-8 EOS port alarm profile, 1-8 EQCOMM shelf alarm, 1-41 EQFAIL server alarm, 1-42 EQINV shelf alarm, 1-41 EQLOCK shelf alarm, 1-42 EQMIS shelf alarm, 1-42 EQRMV shelf alarm, 1-43 Equipped state card or port, 4-18 ERFI-V DS1 port alarm, 1-43 Error codes EMS, 1-105, Errored blocks E1 port, 2-36, 2-38 E3 port, 2-39 E3 port, far end, 2-40 LO VC3 path, 2-42 LO VC3 path, far end, 2-44 SDH port MS, 2-46 SDH port MS, far end, 2-48 SDH port RS, 2-45 VC11 path, 2-50 VC11 path, far end, 2-52 VC12 path, 2-50 VC12 path, far end, 2-52 VC3 path, 2-42 VC3 path, far end, 2-44 VC4 path, 2-42 VC4 path, far end, 2-44 Errored seconds DS1 port, 2-18 DS1 port, far end, 2-19 DS3 port, 2-21 DS3 port (CBit), 2-22 DS3 port (CBit), far end, 2-23 DS3 port (PBit), 2-21 E1 port, 2-36, 2-37 E1 port, far end, 2-38 E3 port, 2-39 E3 port, far end, 2-40 Line, EC1 port, 2-24 Line, far end EC1 port, 2-25 LO VC3 path, 2-42 LO VC3 path, far end, 2-44 Ratio E1 port, 2-37 E3 port, 2-39 SDH port MS, 2-46 SDH port MS, far end, 2-48 SDH port RS, 2-45 Section EC1 port, 2-25 SONET line, 2-28 SONET line, far end, 2-29 SONET path, 2-31 SONET path, far end, 2-32 SONET section, 2-27 SONET VT path, 2-33 SONET VT path, far end, 2-34 VC11 path, 2-50 VC11 path, far end, 2-52 VC12 path, 2-50 VC12 path, far end, 2-52 VC3 path, 2-42 VC3 path, far end, 2-44 VC4 path, 2-42 VC4 path, far end, 2-44 ESFE errored seconds far end, line, 2-25 Ethernet module placement, 9-7, 9-8, 9-9, 9-12, 9-13, 9-17, BaseTX-inclusive, 9-1 performance monitoring RX, 2-60 RX ALIGNMENT ERR, 2-61 RX BROADCAST, 2-60 RX BYTES, 2-61, 2-62 RX BYTES BAD, 2-61 RX DELAY DISCARDS, 2-60 RX DISCARDS, 2-60 RX FCS ERR, 2-61 RX FRAMES, 2-60 RX MTU DISCARDS, 2-60 RX MULTICAST, 2-60 RX NO DELIMITER, 2-60 RX PAUSE, 2-61 RX PKT > 1518, 2-60 RX PKT , 2-60 RX PKT , 2-60 RX PKT , 2-60 RX PKT , 2-60 RX PKT 64, 2-60 RX PKT , 2-60 RX UNICAST, 2-59 Index-10 Turin Networks Release OPS3.1.x

443 Index TX BROADCAST, 2-59 TX BYTES, 2-61, 2-62 TX BYTES BAD, 2-61 TX DEFERRED FRAMES (10/100 only), 2-61 TX DISCARDS, 2-60 TX EXCESSIVE COLL (10/00 only), 2-61 TX FRAMES, 2-59 TX LATE COLL (T10/00 only), 2-61 TX MULTICAST, 2-56, 2-59 TX MULTIPLE COLL (10/100 only), 2-61 TX PAUSE, 2-61 TX PKT > 1518, 2-59 TX PKT , 2-59 TX PKT , 2-59 TX PKT , 2-59 TX PKT , 2-59 TX PKT 64, 2-59 TX PKT , 2-59 TX SINGLE COLL (10/100 only), 2-61 TX UNICAST, 2-59 performance parameters, 2-55 protection with Ethernet (protection) ECM, 9-9 unprotected with 10/100BaseT ECM, 9-9, 9-13, 9-18 unprotected with Ethernet (protection) ECM, 9-10, 9-14, 9-18 Ethernet port link integrity status, 1-58 terminal loopbacks, 4-13 Event categories of, 1-2 default severity levels, 1-19 LCAS remove, 1-57 LCAS restore, 1-57 logs, 1-2 recommended actions, 1-19 reporting, 1-2 severity levels default, 1-1 SYSREF, 1-90 TSSREF, 1-97 types of, 1-2 Events logs, 1-2 EXER_SWITCH shelf alarm, 1-43 EXT2-REF1-ALM reference timing alarm, 1-44 EXTA-REF1-ALM reference timing alarm, 1-43 EXTA-REF2-ALM reference timing alarm, 1-43 EXTA-REF3-ALM reference timing alarm, 1-44 EXTA-REF4-ALM reference timing alarm, 1-44 EXTB-REF2-ALM reference timing alarm, 1-44 EXTB-REF3-ALM reference timing alarm, 1-44 EXTB-REF4-ALM reference timing alarm, 1-44 F Facility access digroup FAD test access point, 5-2 Facility payload loopback DS1, 4-10, 4-11 DS3, 4-10, 4-11 E1, 4-12 E3, 4-12 FAD facility access digroup, test access, 5-2 Failure count Line, far end EC1 port, 2-26 Failure counts DS1 port, 2-19 DS1 port, far end, 2-20 DS3 port (PBit), 2-22 DS3 port (PBit), far end, 2-23 E1 port, far end, 2-38 E1port, 2-36 E3 port, 2-40 E3 port, far end, 2-41 Line EC1 port, 2-24 LO VC3 path, 2-43 LO VC3 path, far end, 2-44 SDH port MS, 2-47 SDH port MS, far end, 2-49 SONET line, 2-28 SONET line, far end, 2-30 VC11 path, 2-51 VC11 path, far end, 2-53 VC12 path, 2-51 VC12 path, far end, 2-53 VC3 path, 2-43 VC3 path, far end, 2-44 VC4 path, 2-43 VC4 path, far end, 2-44 Fan fan tray and module, 6-1 maintenance air filter, 6-2 front inlet fan tray module, 6-1 Release OPS3.1.x Turin Networks Index-11

444 Index speeds, 6-2 tray air filters, 6-2 tray holder LEDs, 3-4, 3-5 tray module replacing, 8-24, 8-26, 8-29 upgrade to FIFT, 8-37 Fan tray air filters replacing, 6-7 FANCOMM shelf alarm, 1-45 FANCOND shelf alarm, 1-45 FANFLTR shelf alarm, 1-45 FANRMV shelf alarm, 1-45 Fast Ethernet LEDs, 3-10 Fault management customization, 1-6 viewing alarms, 1-15 FC failure count, line, 2-24 FCFE failure count, line, 2-26 FEP far-end protection failure alarm, 1-45 Fiber optic cabling, 8-17, 8-18 Filtering alarms, 1-17 Filters air, 6-2 FIRE shelf alarm, 1-45 FLOOD shelf alarm, 1-45 FOPR eos alarm, 1-46 FOPT eos alarm, 1-46 Force switch, 7-28, 7-32 FORCED shelf alarm, 1-47 FORCED_ON_PROT shelf alarm, 1-47 FORCED_ON_SECT1 shelf alarm, 1-47 FORCED_ON_SECT2 shelf alarm, 1-48 FORCED_ON_WORK shelf alarm, 1-48 Frame alignment signal E1 port, 2-36 Fuse PDAP-2S replacing, 6-10, 6-12 PDAP-4S replacing, 6-18 G GbE LX-VC LEDs, 3-10 GbE port alarm profile, 1-8 performance monitoring, 2-59 GCM alarm LEDs, 3-8 module placement, 9-7 status active standby, 7-21, 7-63 protection, 7-21, 7-63 GCM (General control module) with VTX/VCX, 8-10, 9-2 General Control Module Power On Self Test (POST), 4-21 Generating PM reports, 2-15 GENFAIL shelf alarm, 1-48 GFP FCS DISCARDS EOS port, 2-56 GFPLOF VC bundle alarm, 1-48 GIDM eos alarm, 1-49 GMT fuse replacing, PDAP-2S, 6-12 replacing, PDAP-4S, 6-18 GMT fuse block PDAP-2S, 6-12 PDAP-4S, 6-18 Guides EAM, 6-21 PDAP-2S LED module, 6-15 PDAP-4S LED module, 6-19 H H4-LOM alarm, 1-49 Hierarchy alarms, 1-6 HIGHHMD shelf alarm, 1-49 HP_BERSD optical port alarm, 1-50 Index-12 Turin Networks Release OPS3.1.x

445 Index HP_BERSF optical port alarm, 1-51 HP_PLM optical port alarm, 1-51 HP_RDI optical port alarm, 1-52 HP_RFI optical port alarm, 1-52 HP_TIM optical port alarm, 1-52 HP_UNEQ optical port alarm, 1-53 HP-LOM alarm, 1-51 HP-MND alarm, 1-51 HP-SQOM alarm, 1-51 I ical, 1-20 IDLE DS port alarm, 1-53 INCOMPATSW server alarm, 1-53 shelf alarm, 1-53 Initiate upgrade, 7-15, 7-59 Inserting modules, 8-5 Integrity status Ethernet, 1-58 Intervals performance monitoring, 2-9, 2-12 IP address node-ip, 9-22 K KBYTE optical port alarm, 1-54 L LAG alarm profile, 1-8 LBC alarm, 1-57 LCAS remove EOS event, 1-57 LCAS restore EOS event, 1-57 LEAK shelf alarm, 1-57 LEDs electrical module port, 3-9 fan tray holder, 3-4, 3-5 Fast Ethernet, 3-10 GbE LX-VC, 3-10 GCM alarm, 3-8 GCM power and standby, 8-15 general control module (GCM), 3-8 module, 3-6 module status, 3-1 optical modules, 3-10 PDAP, 3-2 PDAP-2S, 3-2 power and standby, 3-7 LFD eos alarm, 1-57 Light emitting diodes, see LEDs Line CVFE (coding violations, far end), 2-25 FC (failure count), 2-24 FC (failure counts, far end), 2-26 SESFE (severely errored seconds, far end), 2-25 UASFE (unavailable seconds, far end), 2-26 Link integrity, see Integrity status LINK_FRCD_DIS Ethernet port alarm, 1-58 LINKFAIL Ethernet port alarm, 1-58 integrity status LO VC3 path performance monitoring BBE-LP, 2-42 EB-LP, 2-42 ES-LP, 2-42 FC-LP, 2-43 FE BBE-LP, 2-44 FE EB-LP, 2-44 FE ES-LP, 2-44 FE FC-LP, 2-44 FE SES-LP, 2-44 FE UAS-LP, 2-44 NPJC-DET-LP, 2-43 NPJC-GEN-LP, 2-43 PPJC-DET-LP, 2-43 PPJC-GEN-LP, 2-43 SES-LP, 2-42 UAS-LP, 2-42 LO_LBC SFP optical port alarm, 1-60 LO_OPR SFP optical port alarm, 1-60 LO_OPT SFP optical port alarm, 1-60 LO_TEMP SFP optical port alarm, 1-60 Release OPS3.1.x Turin Networks Index-13

446 Index LO_VCC SFP optical port alarm, 1-60 LOA eos alarm, 1-60 LOCK_WORK1 shelf alarm, 1-61, 1-62, 1-63 Locked administrative state card or port, 4-18 LOCKOUT shelf alarm, 1-60 LOF DS port alarm, 1-64 LOG eos alarm, 1-64 Login management system, 7-51 LOGINFAIL server alarm, 1-65 shelf alarm, 1-65 LOGINSUCC server alarm, 1-65 shelf alarm, 1-65 LOGINTERM server alarm, 1-65 shelf alarm, 1-65 LOM-P eos alarm, 1-65 LOM-V eos alarm, 1-65 Loopback tests, 4-9 description, 4-9 DS1 facility, 4-10 DS1 terminal, 4-10 DS3 CC facility, 4-10, 4-11 DS3 CC terminal, 4-10 DS3 terminal, 4-10 DS3 TMUX facility, 4-10 DS3 TMUX terminal, 4-10 DS3/EC-1 facility, 4-10 E1 facility, 4-10, 4-12 E1 terminal, 4-12 E3 facility, 4-10, 4-12 E3 terminal, 4-12 EC1 facility, 4-10 EC1 terminal, 4-10 EC-3 terminal, 4-11 Ethernet terminal, 4-13 SDH facility, 4-15 SDH terminal, 4-15 SONET facility, 4-15 SONET terminal, 4-15 STM-1E terminal, 4-11 LOP-P DS port alarm, 1-66 LOS DS port alarm, 1-67 Loss of signal seconds DS1 port, 2-18 E1 port, 2-36 LP_BERSD optical port alarm, 1-68 LP_BERSF optical port alarm, 1-68 LP_PLM optical port alarm, 1-70 LP_RDI optical port alarm, 1-70 LP_RFI optical port alarm, 1-70 LP_TIM optical port alarm, 1-71 LP_UNEQ optical port alarm, 1-71 LP-LMD eos alarm, 1-69 LP-LOM eos alarm, 1-69 LP-RFICON optical port alarm, 1-70 LP-RFIPAY optical port alarm, 1-70 LP-RFISVR optical port alarm, 1-70 LP-SQM eos alarm, 1-71 M Maintenance alarm board PDAP-4S, 6-19 fan tray air filter, 6-2 fan tray air filter replacement, 6-7 fuse PDAP-2S, 6-10, 6-12 PDAP-4S, 6-18 PDAP-2S replace circuit breaker, 6-11 PDAP-2S alarm board, 6-14 PDAP-4S TPA fuse, 6-16 replacing EAM, 6-20 routine, shelf, 6-1 Major alarm, see LEDs MAN_ON_PROT shelf alarm, 1-72 MAN_ON_WORK shelf alarm, 1-72 Management System Index-14 Turin Networks Release OPS3.1.x

447 Index event logs, 1-2 verify software version, 7-18, 7-61, 8-4 MAN-TX-OFF alarm, 1-72 MAN-TX-ON alarm, 1-72 MANUAL shelf alarm, 1-72 Measured supply voltage SFP optic port, 2-26 temperature SFP optic port, 2-26 TX bias current SFP optic port, 2-26 TX input power SFP optic port, 2-26 TX output power SFP optic port, 2-26 Minor alarm, see LEDs MND-P eos alarm, 1-72 MND-V eos alarm, 1-72 Module placement guidelines, 8-10, 9-2 Module download times, 7-14, 7-59 Module software version compatibility, 7-4, 7-51, 8-2 Modules inserting, 8-5 power and standby LEDs, 3-7 prepare for removal and replacement, 8-7 replacing, 8-1, 8-37 Monitoring, performance, 2-1 MPX connector cleaning material, 7-3, 8-5 MPX connectors cleaning, 8-16 inspection, 8-16 MS-AIS optical port alarm, 1-73 MS-BERSD optical port alarm, 1-73 MS-BERSF optical port alarm, 1-74 MS-RDI optical port alarm, 1-74 MSSP_NOT_SYNC MS-SP Ring out of sync alarm, 1-74 Multiplex section performance monitoring BBE-MS, 2-46 EB-MS, 2-46 ES-MS, 2-46 FC-MS, 2-47 FE BBE-MS, 2-49 FE EB-MS, 2-48 FE ES-MS, 2-48 FE FC-MS, 2-49 FE UAS-MS, 2-48 PSCP-MS, 2-47 PSCW-MS, 2-47 PSDP-MS, 2-47 PSDW-MS, 2-47 SES-MS, 2-46 UAS-MS, 2-46 Mux alarm profile, 1-8 EMSI, 2-8 N Negative pointer justifications detected LO VC3 path, 2-43 VC11 path, 2-51 VC12 path, 2-51 VC3 path, 2-43 VC4 path, 2-43 Negative pointer justifications generated LO VC3 path, 2-43 VC11 path, 2-51 VC12 path, 2-51 VC3 path, 2-43 VC4 path, 2-43 NETSYNC server alarm, 1-75 Node ID, 9-22 IP, 9-22 IP address, 9-22 parameters node ID (node name), 9-22 node IP, 9-22 NODEEQMIS server alarm, 1-75 NODEMIS optical port, 1-75 optical port alarm, 1-75 NODESYNC server alarm, 1-76 Non-equipped state card or port, 4-18 NO-REMOTE-LCAS remote peer LCAS status alarm, 1-76 NPM eos alarm, 1-76 Release OPS3.1.x Turin Networks Index-15

448 Index O OFGERR, 1-35 Operational state card or port, 4-18 OPR alarm, 1-76 OPT alarm, 1-76 Optic modules, 8-12, 9-4 Optical power specifications, 4-4 Optics module placement, 9-7 OVERTEMP shelf alarm, 1-77 OVERVOLTAGE_A shelf alarm, 1-77 OVERVOLTAGE_B shelf alarm, 1-77 P Password, 7-13, 7-58 PCASQLCH optical port alarm, 1-77 PDAP-15A replace GMT fuse, 6-10 PDAP-2S also see Power Distribution and Alarm Panel captive fasteners, 6-14 circuit breaker, 6-12 GMT fuse block, 6-12 LED module, 6-15 LEDs, 3-2 replace circuit breaker, 6-11 replacing alarm board, 6-14 PDAP-4S also see Power Distribution and Alarm Panel captive fasteners, 6-19 GMT fuse block, 6-18 LED module guides, 6-19 LEDs, 3-2 replacing alarm board, 6-19 TPA fuse, 6-16 TPA fuse, 6-17 Performance monitoring, /100BaseTX port, 2-59 DS1 port, 2-18 DS3 port, 2-21, 2-36 E1 port, 2-36 E3 port, 2-39 EC1 port, 2-24 GbE port, 2-59 generating reports, 2-15 intervals, 2-9, 2-12 printing PM data, 2-10, 2-12 refreshing PM values, 2-10, 2-12 reports, generating, 2-15 resetting PM counters, 2-10, 2-12 samples, 2-9, 2-12 saving PM data, 2-10, 2-12 SDH path, 2-41, 2-50 SDH port, 2-45 services (SONET STS), 2-31 services (SONET VT), 2-33 SONET port, 2-27 templates, 2-2 viewing port PM data, 2-9 viewing service PM data, 2-11, 2-13 Performance parameters Ethernet, 2-55 SDH, 2-35 SONET, 2-17 Periodic conditions, monitoring, 2-1 Plastic standoff, see Environmental Alarm Module PLC lag alarm, 1-78 PLCR eos alarm, 1-78 PLCT eos alarm, 1-78 PLINESQL optical port alarm, 1-79 PLM DS port alarm, 1-79 PLM-V DS port alarm, 1-79 optical port alarm, 1-79 shelf alarm, 1-79 PLM-VC optical port alarm, 1-79 PM also see Performance monitoring template synchronize, 2-4 timing refresh time, 2-8 samples, 2-8 PMCFG all ports alarm, 1-80 PMDATALOST shelf alarm, 1-80 Pointer justifications difference VC11 path, 2-52 VC12 path, 2-52 Index-16 Turin Networks Release OPS3.1.x

449 Index Pointer justifications seconds detected VC11 path, 2-51 VC12 path, 2-51 Pointer justifications seconds generated VC11 path, 2-52 VC12 path, 2-52 Port number TransAccess 200 Mux, 9-23 Positive pointer justifications detected LO VC3 path, 2-43 VC11 path, 2-51 VC12 path, 2-51 VC3 path, 2-43 VC4 path, 2-43 Positive pointer justifications generated LO VC3 path, 2-43 VC11 path, 2-51 VC12 path, 2-51 VC3 path, 2-43 VC4 path, 2-43 Power and standby LEDs, 3-7 Power Distribution and Alarm Panel alarm board replacing, 6-14 LEDs, 3-2 replacing circuit board, 6-19 circuit breaker, 6-11 TPA fuse, 6-16 Power On Self Test (POST) for GCM, 4-21 Printing PM data, 2-10, 2-12 Probable Cause, 1-17 Problems, see Symptoms Procedures air filter replacement, 6-7 cleaning MPX connectors, 8-16 Fan Assembly (6-slot) Air Filter Installation, 8-28 fan tray air filter installation, 8-25, 8-32 fan tray module installation, 8-24, 8-26, 8-29 inserting modules, 8-5 software upgrade activate GCM, 7-45 upgrade to FIFT (fan), 8-37 Procedures (GUI) activate software protected modules, 7-30 unprotected modules, 7-33 assign port alarm profile, 1-9 assigning a port PM template, 2-5 assigning a service path alarm profile, 1-10 assigning a service PM template, 2-6 assigning a subport alarm profile, 1-10 assigning a subport PM template, 2-6 assigning a T100 PM template, 2-8 clear protection switch, 7-41 creating a PM template, 2-2 new alarm profile, 1-7 perform a forced switch, 7-38 perform a manual switch, 7-40 PM report generation, 2-16 software upgrade activate GCM, 7-21, 7-25, 7-35, 7-36, 7-62, 7-65 software version number verification, 7-18, 7-61, 8-4 suppressing port alarms, 1-12 suppressing service CTP path alarms, 1-13 viewing alarms, 1-15 viewing port or subport PM data, 2-9 viewing service PM data, 2-11 Protected modules, 7-30 Protection electrical modules, 8-10, 8-11, 9-2, 9-3 Ethernet, 8-12, 9-4 Protection groups, 7-30 Protection switch forced, 7-28, 7-32 release, 7-28, 7-32 Protection switch count protecting SDH port MS, 2-47 SONET line, 2-29 working SDH port MS, 2-47 SONET line, 2-28 Protection switch duration protecting SDH port MS, 2-47 SONET line, 2-29 working SDH port MS, 2-47 SONET line, 2-29 PUMPFAIL shelf alarm, 1-80 PWFAIL-A shelf alarm, 1-80 PWFAIL-B shelf alarm, 1-80 Q QEFAIL shelf alarm, 1-80 R Read community TransAccess 200 Mux, 9-23 Recommended Actions Release OPS3.1.x Turin Networks Index-17

450 Index alarms and events, 1-19 non-alarmed symptoms, 4-2 RECTFAIL shelf alarm, 1-80 RECTHIGH shelf alarm, 1-81 RECTLOW shelf alarm, 1-81 Refreshing PM values, 2-10, 2-12 Regenerator section performance monitoring BBE-RS, 2-45 EB-RS, 2-45 ES-RS, 2-45 SES-RS, 2-45 Release path, 7-15, 7-59 Release protection switch, 7-28, 7-32 Remote test access test access, 5-3 Remote test unit test access, 5-2 REMOTE-LINKFAIL alarm, 1-81 Replacement modules, 7-4, 7-51, 8-2 Replacing alarm board PDAP-2S, 6-14 PDAP-4S, 6-19 circuit breaker PDAP-2S, 6-11 EAM circuit board, 6-20 fan tray module, 8-24, 8-26, 8-29 fuse PDAP-2S, 6-10, 6-12 PDAP-4S, 6-18 GCM power and standby LEDs, 8-15 modules, 8-1, 8-5, 8-37 required equipment, 7-3, 7-50, 8-5, 8-38 Reporting alarms and events, 1-2 Reports, PM, 2-15 Resetting PM counters, 2-10, 2-12 RESOURCE_MISMATCH shelf alarm, 1-81 RFICON DS port alarm, 1-84 RFICON-V DS port alarm, 1-84 RFI-L EC-1 port alarm, 1-82 RFI-P EC-1 port alarm, 1-82 RFIPAY DS port alarm, 1-85 RFIPAY-V DS port alarm, 1-85 RFIPAY-VC optical port alarm, 1-85 RFISVR DS port alarm, 1-86 RFISVR-V DS port alarm, 1-86 RFI-V DS1 port alarm, 1-83 RFI-VC optical port alarm, 1-83 RS-TIM trace identifier mismatch alarm, 1-87 RTU remote test unit, 5-2 RX Ethernet port, 2-60 RX ALIGNMENT ERR Ethernet port, 2-61 RX BROADCAST EOS port, 2-56 Ethernet port, 2-60 RX BYTES EOS port, 2-56, 2-57 Ethernet port, 2-61, 2-62 RX BYTES BAD Ethernet port, 2-61 RX DELAY DISCARDS Ethernet port, 2-60 RX DISCARDS Ethernet port, 2-60 RX FCS ERR Ethernet port, 2-61 RX FRAMES EOS port, 2-56 Ethernet port, 2-60 RX MTU DISCARDS EOS port, 2-57 Ethernet port, 2-60 RX MULTICAST EOS port, 2-56 Ethernet port, 2-60 RX NO DELIMITER Ethernet port, 2-60 RX PAUSE Ethernet port, 2-61 RX PKT > 1518 Ethernet port, 2-60 RX PKT Ethernet port, 2-60 RX PKT Index-18 Turin Networks Release OPS3.1.x

451 Index Ethernet port, 2-60 RX PKT Ethernet port, 2-60 RX PKT Ethernet port, 2-60 RX PKT 64 Ethernet port, 2-60 RX PKT Ethernet port, 2-60 RX UNICAST EOS port, 2-56 Ethernet port, 2-59 S Samples in performance monitoring, 2-9, 2-12 Saving PM data, 2-10, 2-12 SDH HO path alarm profile, 1-8 LO path alarm profile, 1-8 path performance monitoring, 2-41, 2-50 performance parameters, 2-35 port alarm profile, 1-8 SDH port facility loopback tests, 4-15 performance monitoring, 2-45 BBE-MS, 2-46 BBE-RS, 2-45 EB-MS, 2-46 EB-RS, 2-45 ES-MS, 2-46 ES-RS, 2-45 FC-MS, 2-47 FE BBE-MS, 2-49 FE EB-MS, 2-48 FE ES-MS, 2-48 FE FC-MS, 2-49 FE UAS-MS, 2-48 PSCP-MS, 2-47 PSCW-MS, 2-47 PSDP-MS, 2-47 PSDW-MS, 2-47 SES-MS, 2-46 SES-RS, 2-45 UAS-MS, 2-46 terminal loopback tests, 4-15 Self test, GCM, see General Control Module, Power On Self Test Server alarm profile, 1-8 Server IP address, 7-13, 7-58 SERVER_LOGINFAIL server alarm, 1-87 Service (SONET STS) performance monitoring, 2-31 (SONET VT) performance monitoring, 2-33 Service (SONET VT) performance monitoring, 2-33 Service error codes EMS, system resources unavailable (1035), SESFE severely errored seconds, far end line, 2-25 SETOPER shelf alarm, 1-87 Severely errored frames alarm indication signal seconds DS1 port, 2-19 Severely errored framing seconds DS1 port, far end, 2-20 Section EC1 port, 2-25 SONET section, 2-27 Severely errored seconds DS1 port, 2-18 DS1 port, far end, 2-20 DS3 port, 2-21 DS3 port (CBit), 2-22 DS3 port (CBit), far end, 2-23 DS3 port (PBit), 2-21 E1 port, 2-36, 2-37 E1 port, far end, 2-38 E3 port, 2-39 E3 port, far end, 2-40 Line EC1 port, 2-24 Line, far end EC1 port, 2-25 LO VC3 path, 2-42 LO VC3 path, far end, 2-44 Ratio E1 port, 2-37 E3 port, 2-40 SDH port MS, 2-46 SDH port MS, far end, 2-48 SDH port RS, 2-45 Section EC1 port, 2-25 SONET line, 2-28 SONET line, far end, 2-30 SONET path, 2-31 SONET path, far end, 2-32 SONET section, 2-27 Release OPS3.1.x Turin Networks Index-19

452 Index SONET VT path, 2-33 SONET VT path, far end, 2-34 VC11 path, 2-50 VC11 path, far end, 2-52 VC12 path, 2-50 VC12 path, far end, 2-52 VC3 path, 2-42 VC3 path, far end, 2-44 VC4 path, 2-42 VC4 path, far end, 2-44 Severity NSA, 1-6, 1-17 SA, 1-6, 1-17 Severity levels alarms and events default, 1-1 defined, 1-5 Severity levels for alarms and events default, 1-19 SFO DS port alarm, 1-87 optical port alarm, 1-87 SFP optic port performance monitoring measured supply voltage, 2-26 measured temperature, 2-26 measured TX bias current, 2-26 measured TX input power, 2-26 measured TX output power, 2-26 SFPMIS alarm, 1-88 SFPRMV alarm, 1-88 Shelf alarm profile, 1-8 SHELFMIS server alarm, 1-88 SMOKE shelf alarm, 1-88 SNMP ems.mib, 9-23 MIB, 9-23 SNMP, node configuration, 9-22 node agent port 161, 9-22 Software activation, 7-30 compatibility, 7-4, 7-51, 8-2 download abort, 7-16, 7-60 status, 7-16, 7-17, 7-60 download times, 7-14, 7-59 upgrade, 7-1, 7-49 activate GCM, 7-21, 7-25, 7-35, 7-36, 7-62, 7-65 activate time, 7-30 upgrade order, 7-30 version number verify, 7-18, 7-61, 8-4 Software upgrade activate GCM, 7-45 activate time, 7-22, 7-24, 7-63, 7-64 Software version current, 7-18, 7-61, 8-4 standby, 7-17, 7-60 SONET performance parameters, 2-17 port alarm profile, 1-8 STS alarm profile, 1-8 VT alarm profile, 1-8 SONET line performance monitoring CV-L, 2-27 ES-L, 2-28 FC-L, 2-28 FE CV-L, 2-29 FE ES-L, 2-29 FE FC-L, 2-30 FE SES-L, 2-30 FE UAS-L, 2-30 PSCP-L, 2-29 PSCW-L, 2-28 PSDP-L, 2-29 PSDW-L, 2-29 SES-L, 2-28 UAS-L, 2-28 SONET path performance monitoring CV-P, 2-31 ES-P, 2-31 FE CV-P, 2-32 FE ES-P, 2-32 FE SES-P, 2-32 FE UAS-P, 2-32 SES-P, 2-31 UAS-P, 2-31 SONET port facility loopback tests, 4-15 performance monitoring, 2-27 terminal loopback tests, 4-15 SONET section performance monitoring CV-S, 2-27 ES-S, 2-27 SEFS-S, 2-27 SES-S, 2-27 Index-20 Turin Networks Release OPS3.1.x

453 Index SONET VT path performance monitoring CV-V, 2-33 ES-V, 2-33 FE CV-V, 2-34 FE ES-V, 2-34 FE SES-V, 2-34 FE UAS-V, 2-34 SES-V, 2-33 UAS-V, 2-33 Speed cooling fan, 6-2 SQLCHTBL optical port alarm, 1-88 SQM ethernet port alarm, 1-88 SQM-P eos alarm, 1-88 SQM-V eos alarm, 1-89 SSF server signal fail alarm, 1-89 Standby hop, 2-11 module, 7-42 Status activation, 7-23, 7-63, 7-64 activation time, 7-31 GCM protection, 7-21, 7-63 StickyMode alarms display, 1-18 STM-1E terminal loopback tests, 4-11 SVC_ERROR shelf alarm, 1-89 SW_UPG shelf alarm, 1-90 SWCRPT shelf alarm, 1-89 SWERR all ports alarm, 1-89 SWITCH Ethernet port alarm, 1-89 shelf alarm, 1-90 SWITCH_TO_PROT shelf alarm, 1-89 SWITCH_TO_SECT1 shelf alarm, 1-89 SWITCH_TO_SECT2 shelf alarm, 1-90 SWMIS, 7-23, 7-25, 7-29, 7-64, 7-65 all ports alarm, 1-90 Symptoms incorrect environmental alarms, 4-2 recommended actions, 4-2 SYNCFAIL optical port alarm, 1-90 SYSREF system reference alarm, 1-90 system reference event, 1-90 System resources unavailable, System software upgrade status ABORTED, 7-16, 7-60 FAILED, 7-16, 7-60 INPROGRESS, 7-16, 7-60 NONE, 7-16, 7-60 OK, 7-16, 7-60 T TA200_COM alarm, 1-91 TAC, 5-2 TAP (FAD or DFAD), 5-2 TCA port alarm, 1-92 TEMP alarm, 1-92 TEMPCRIT shelf alarm, 1-92 Templates performance monitoring, 2-2 TEMPWARN shelf alarm, 1-92 Termination point TP, test access, 5-2 Test Access ADM, 5-1 AID, 5-2, 5-5 cross-connect, 5-2 DCS3/1, 5-1 digital signals, 5-1 DS1 module, 5-8 DS3 module, 5-8 DS3 transmux module, 5-8 dual facility access digroup (DFAD), 5-2 E1 module, 5-8 facility access digroup (FAD), 5-2 intrusive, 5-1 management system, 5-8 monitor, 5-9 non-intrusive, 5-1 per side split, 5-14 point, 5-2 remote test access, 5-3 remote test unit (RTU), 5-2 series split, 5-18 termination point (TP), 5-2 test system controller (TSC), 5-2, 5-25 Release OPS3.1.x Turin Networks Index-21

454 Index VCX component, 5-8 VT/TU 5G switch, 5-8 Test system controller TSC, 5-2, 5-25 Thresholds setting for PM parameters, 2-4 TIM port alarm, 1-92 TIMEDOUT shelf alarm, 1-93 TIMEOUTWARN shelf alarm, 1-93 TIM-P port alarm, 1-92 TIM-S port alarm, 1-93 TIM-V port alarm, 1-93 TIU-V port alarm, 1-93 shelf alarm, 1-93 TLC lag alarm, 1-94 TLCR eos alarm, 1-94 TLCT eos alarm, 1-94 Toggle switch PDAP-2S circuit breaker, 6-12 TOOMANYEVENTS server alarm, 1-94 TOPOMIS optical port alarm, 1-94 TOXIC shelf alarm, 1-94 TP termination point, test access, 5-2 TPA fuse PDAP-4S, 6-17 TransAccess 200 Mux port number, 9-23 read community, 9-23 write community, 9-23 Transmit and receive signal levels, 4-3, 4-7 Transmux DS3/EC-1, 8-10, 9-2 Troubleshooting error codes, loopback tests, 4-9 transmit and receive signal levels, 4-3, 4-7 TSSALM shelf alarm, 1-97 TSS-EXTA-OOB-A controller A EXT A out of band alarm, 1-94 TSS-EXTA-OOB-B controller B EXT A out of band alarm, 1-94 TSS-EXTB-OOB-A Controller A EXT B out of band alarm, 1-94 TSS-EXTB-OOB-B Controller B EXT B out of band alarm, 1-94 TSS-FRC shelf alarm, 1-95 TSS-FREERUN-GCMA shelf alarm, 1-95 TSS-FREERUN-GCMB shelf alarm, 1-95 TSSGE shelf alarm, 1-97 TSS--HOLDOVER-GCMA GCM A is in holdover state., 1-95 TSS--HOLDOVER-GCMB GCM B is in holdover state., 1-95 TSS-LINE1-OOB-GCMA GCM A line reference 1 out of band alarm, 1-95, 1-96 TSS-LINE1-OOB-GCMB GCM A line reference 1 out of band alarm, 1-95 TSS-LINE2-OOB-GCMA GCM A line reference 2 out of band alarm, 1-95 TSS-LINE2-OOB-GCMB GCM B line reference 2 out of band alarm, 1-95 TSS-LINE3-OOB-GCMA GCM A line reference 3 out of band alarm, 1-96 TSS-LINE3-OOB-GCMB GCM B line reference 3 out of band alarm, 1-96 TSS-LINE4-OOB-GCMB GCM B line reference 4 out of band alarm, 1-96 TSS-LOCK shelf alarm, 1-96 TSS-MAN shelf alarm, 1-96 TSSREF timing reference alarm, 1-97 timing reference event, 1-97 TSS-REF1-ALM shelf alarm, 1-96 TSS-REF2-ALM shelf alarm, 1-96 TSS-REF3-ALM shelf alarm, 1-96 TSS-REF4-ALM shelf alarm, 1-97 TSS-REFL-GCMA shelf alarm, 1-97 TSS-REFL-GCMB shelf alarm, 1-97 Index-22 Turin Networks Release OPS3.1.x

455 Index TSS-REFS shelf alarm, 1-97 TSSSETS shelf alarm, 1-97 TSS-SSM shelf alarm, 1-97 TU-AIS optical port alarm, 1-21, 1-98 TU-LOP optical port alarm, 1-98 TX BROADCAST EOS port, 2-56 Ethernet port, 2-59 TX BYTES EOS port, 2-56 Ethernet port, 2-61, 2-62 TX BYTES BAD Ethernet port, 2-61 TX DEFERRED FRAMES Ethernet port (T10/00 only), 2-61 TX DISCARDS EOS port, 2-56 Ethernet port, 2-60 TX EXCESSIVE COLL Ethernet port (10/100 only), 2-61 TX FRAMES EOS port, 2-56 Ethernet port, 2-59 TX LATE COLL Ethernet port (10/100 only), 2-61 TX MULTICAST Ethernet port, 2-56, 2-59 TX MULTIPLE COLL Ethernet port (10/-100 only), 2-61 TX PAUSE Ethernet port, 2-61 TX PKT > 1518 Ethernet port, 2-59 TX PKT Ethernet port, 2-59 TX PKT Ethernet port, 2-59 TX PKT Ethernet port, 2-59 TX PKT Ethernet port, 2-59 TX PKT 64 Ethernet port, 2-59 TX PKT Ethernet port, 2-59 TX SINGLE COLL Ethernet port (10/00 only), 2-61 TX UNICAST U EOS port, 2-56 Ethernet port, 2-59 UASFE unavailable seconds far end, line, 2-26 Unavailable seconds DS1 port, 2-19 DS1 port, far end, 2-20 DS3 port (CBit), 2-22 DS3 port (CBit), far end, 2-23 DS3 port (PBit), 2-21 E1 port, 2-37 E1 port, far end, 2-38 E3 port, 2-39 E3 port, far end, 2-41 Line EC1 port, 2-24 Line, far-end EC1 port, 2-26 LO VC3 path, 2-42 LO VC3 path, far end, 2-44 SDH port MS, 2-46 SDH port MS, far end, 2-48 SONET line, 2-28 SONET line, far end, 2-30 SONET path, 2-31 SONET path, far end, 2-32 SONET VT path, 2-33 SONET VT path, far end, 2-34 VC11 path, 2-51 VC11 path, far end, 2-53 VC12 path, 2-51 VC12 path, far end, 2-53 VC3 path, 2-42 VC3 path, far end, 2-44 VC4 path, 2-42 VC4 path, far end, 2-44 UNDERVOLTAGE_A shelf alarm, 1-99 UNDERVOLTAGE_B shelf alarm, 1-99 UNEQ alarm, 1-99 UNEQ-P port alarm, 1-99 UNEQ-V port, shelf alarm, UNEQ-VC optical port alarm, Unlocked administrative state card or port, 4-18 Release OPS3.1.x Turin Networks Index-23

456 Index UP all ports alarm, Upgrade type, 7-15, 7-59 init, 7-15, 7-59 Upgrading software, 7-1, 7-49 Username, 7-13, 7-58 V VC11 path performance monitoring BBE-LP, 2-50 EB-LP, 2-50 ES-LP, 2-50 FC-LP, 2-51 FE BBE-LP, 2-52 FE EB-LP, 2-52 FE ES-LP, 2-52 FE FC-LP, 2-53 FE SES-LP, 2-52 FE UAS-LP, 2-53 NPJC-DET-LP, 2-51 NPJC-GEN-LP, 2-51 PJCD-LP, 2-52 PJCS-DET-LP, 2-51 PJCS-GEN-LP, 2-52 PPJC-DET-LP, 2-51 PPJC-GEN-LP, 2-51 SES-LP, 2-50 UAS-LP, 2-51 VC12 path performance monitoring BBE-LP, 2-50 EB-LP, 2-50 ES-LP, 2-50 FC-LP, 2-51 FE BBE-LP, 2-52 FE EB-LP, 2-52 FE ES-LP, 2-52 FE FC-LP, 2-53 FE SES-LP, 2-52 FE UAS-LP, 2-53 NPJC-DET-LP, 2-51 NPJC-GEN-LP, 2-51 PJCD-LP, 2-52 PJCS-DET-LP, 2-51 PJCS-GEN-LP, 2-52 PPJC-DET-LP, 2-51 PPJC-GEN-LP, 2-51 SES-LP, 2-50 UAS-LP, 2-51 VC3 path performance monitoring BBE-HP, 2-42 EB-HP, 2-42 ES-HP, 2-42 FC-HP, 2-43 FE BBE-HP, 2-44 FE EB-HP, 2-44 FE ES-HP, 2-44 FE FC-HP, 2-44 FE SES-HP, 2-44 FE UAS-HP, 2-44 NPJC-DET-HP, 2-43 NPJC-GEN-HP, 2-43 PPJC-DET-HP, 2-43 PPJC-GEN-HP, 2-43 SES-HP, 2-42 UAS-HP, 2-42 VC4 path performance monitoring BBE-HP, 2-42 EB-HP, 2-42 ES-HP, 2-42 FC-HP, 2-43 FE BBE-HP, 2-44 FE EB-HP, 2-44 FE ES-HP, 2-44 FE FC-HP, 2-44 FE SES-HP, 2-44 FE UAS-HP, 2-44 NPJC-DET-HP, 2-43 NPJC-GEN-HP, 2-43 PPJC-DET-HP, 2-43 PPJC-GEN-HP, 2-43 SES-HP, 2-42 UAS-HP, 2-42 VCC alarm, VENTFAIL shelf alarm, Verifying software version, 7-18, 7-61, 8-4 Viewing alarms, 1-6 Viewing alarms, 1-15 all nodes, 1-15 module, 1-15 one node, 1-15 port, 1-15 service CTP, 1-15 Viewing PM data port, 2-9 service, 2-11, 2-13 VT/TU Switch module placement, 8-13, 9-5 W Warm reboot hitless software upgrade, 7-7 Index-24 Turin Networks Release OPS3.1.x

457 Index WARMREBOOT warm reboot alarm, Warning alarm, see LEDs Write community TransAccess 200 Mux, 9-23 X X86_ABORT ethernet encapsulation alarm, X86_CRC ethernet encapsulation alarm, XPT-FAIL-RX alarm, XPT-FAIL-TX alarm, XPTRX lag alarm, XPTTX lag alarm, Release OPS3.1.x Turin Networks Index-25

458 Index Index-26 Turin Networks Release OPS3.1.x

459

460 Visit our website at: Release OPS3.1.x Operations Documentation OPS31