Node Operations and Maintenance · 2007-06-19 · CLI commands. TransNav Man-agement System TL1 Guide This document describes the syntax of the TL1 lan-guage in the TransNav environment

Turin Networks Inc.

Operations Documentation

Release OPS3.1.xPublication Date: April 2007Document Number: 800-0011-OPS31 Rev. A

Node Operations and Maintenance Guide

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 StandardsEN55022 EN55024 CISPR-22

Safety StandardsEN60950 CSA 22.2 No. 60950, ASINZS 3260IEC 60950 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 UseUse, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212 (Commercial Computer Software-Restricted Rights) and DFAR 227.7202 (Rights in Technical Data and Computer Software), as applicable.

Release OPS3.1.x Turin Networks Page i

NODE OPERATIONS AND MAINTENANCE GUIDE

ContentsAbout this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Section 1 Fault ManagementChapter 1Managing Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Chapter 2Alarms, Events, and Recommended Actions . . . . . . . . . . . . . . . . . . . . . . . . 1-19Chapter 3TransNav GUI Service Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-105

Section 2 Performance MonitoringChapter 1Managing Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Chapter 2SONET Performance Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Chapter 3SDH Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Chapter 4Ethernet Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55

Section 3 Equipment LED StatusChapter 1LEDs and Module Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Section 4 DiagnosticsChapter 1Diagnostics Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Chapter 2Traverse Transmit and Receive Signal Levels . . . . . . . . . . . . . . . . . . . . . . . 4-3Chapter 3TraverseEdge 100 Transmit and Receive Signal Levels . . . . . . . . . . . . . . . 4-7Chapter 4Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Chapter 5Other Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Section 5 Test AccessChapter 1Traverse Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Chapter 2Traverse Test Access Guidelines for the Spirent BRTU Interface . . . . . . . . 5-23

Section 6 Routine MaintenanceChapter 1

Node Operations and Maintenance Guide

Page ii Turin Networks Release OPS3.1.x

Routine Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Chapter 2Node Database Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23

Section 7 Software UpgradesChapter 1Release TR2.1.x Traverse Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . 7-1Chapter 2Release 3.0.x TE-100 System Software Upgrade . . . . . . . . . . . . . . . . . . . . . 7-49

Section 8 Hardware UpgradesChapter 1Replacing Existing Traverse Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Chapter 2Upgrade to a Traverse Front Inlet Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

Section 9 AppendicesAppendix AModule Placement Planning and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Appendix BTraverse SNMP v1/v2c Agent and MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Release OPS3.1.x Turin Networks Page iii

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

Traverse System Product Documentation

Page iv Turin Networks Release OPS3.1.x

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

This document provides a detailed overview of the Traverse system. It also includes engineering and planning information.

Anyone who wants to understand the Traverse system and its applications.

Traverse Installation and Configuration

This document provides required equipment, tools, and step-by-step procedures for:■ Hardware installation■ Power cabling■ Network cabling■ Node power up■ Node start-up

Installers, field, and network engineers

Traverse Provisioning

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.

Network engineers, provisioning, and net-work operations center (NOC) personnel

TraverseEdge System Product Documentation

Release OPS3.1.x Turin Networks Page v

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 This section provides a detailed overview of the TraverseEdge system.

Anyone who wants to understand the Traver-seEdge system and its applications

Description and Specifications

This section includes engineering and planning infor-mation.

Field and network engi-neers

Installation and Configuration

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

Installers, field, and network engineers

Provisioning the Network

This section provides step-by-step procedures for provisioning a TraverseEdge network using the Tran-sNav management system. Also see the TransNav Management System Product Documentation.


Configuring Equip-ment

This section provides step-by-step procedures for configuring module and interface parameters of a TraverseEdge using the TransNav management sys-tem. Also see the TransNav Management System Product Documentation.


Creating TDM Ser-vices

This section provides step-by-step procedures for provisioning a TraverseEdge network using the Tran-sNav management system. Also see the TransNav Management System Product Documentation.


Creating Ethernet Services

This section provides step-by-step procedures for provisioning a TraverseEdge network using the Tran-sNav management system. See the TransNav Man-agement System Product Documentation.


Appendices This section provides installation and provisioning checklists, compliance information, and acronym descriptions.

Installers and anyone who wants reference information.

TransNav Management System Product Documentation

Page vi Turin Networks Release OPS3.1.x

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


TransNav Man-agement System Product Overview

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.

Anyone who wants to understand the Tran-sNav management sys-tem

TransNav Man-agement System Server Guide

This document describes the management server com-ponent of the management system and provides proce-dures and troubleshooting information for the server.

Field and network engi-neers, provisioning, and network opera-tions center (NOC) personnelTransNav Man-

agement System GUI Guide

This document describes the graphical user interface including installation instructions and logon proce-dures.

This document describes every menu, window, and screen a user sees in the graphical user interface.

TransNav Man-agement System CLI Guide

This document includes a quick reference to the com-mand line interface (CLI). Also included are compre-hensive lists of both the node-level and domain-level CLI commands.

TransNav Man-agement System TL1 Guide

This document describes the syntax of the TL1 lan-guage 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.


Release OPS3.1.x Turin Networks Page vii


The document below provides operations and maintenance information for Turin’s TransNav managed products.

Information Mapping

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 Help

If you need assistance while working with Traverse products, contact the Turin Networks Technical Assistance Center (TAC):■ Inside the U.S., toll-free: 1-866-TURINET (1-866-887-4638)■ Outside the U.S.: 916-348-2105■ Online: www.turinnetworks.com/html/support_assistance.htm

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. E-mail support (24-hour response) is also available through: [email protected].

Table 4 Operations Documentation


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

http://www.turinnetworks.com/html/support_assistance.htm

Calling for Repairs

Page viii Turin Networks Release OPS3.1.x

Calling for Repairs

If repair is necessary, call the Turin Repair Facility at 1-866-TURINET (866-887-4638) 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 916-348-2105 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 FacilityAttn: RMA # ________1415 North McDowell Blvd.Petaluma, CA 94954 USA


SECTION 1 FAULT MANAGEMENTSECTION 1SYSTEM MONITORING

SECTION 1

Contents

Chapter 1Managing Alarms and Events

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Provisioning events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Performance events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Security events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Normal operational events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Fault events (alarms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Events Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Network Alarm Summary Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Service Affecting Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Alarm Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Customizing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Alarm Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Sort by Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Creating a New Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Assigning an Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Assigning a Port Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Assigning a Subport Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Assigning a Service Path Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Suppressing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Suppress Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Service CTP Path Alarm Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Viewing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Alarm Tallies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Detail View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Map View Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16New Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Set Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Sort by Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17StickyMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Node Operations and Maintenance Guide, Section 1 Fault Management


Chapter 2Alarms, Events, and Recommended Actions

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Alarms/Events, A through C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Alarms/Events, D through K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56Alarms/Events, L through S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57Alarms/Events, TA200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91Alarms/Events, TB through TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-92Alarms/Events U through Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-99

Chapter 3TransNav GUI Service Error Codes

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-105Service Activation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-106TransNav GUI Service Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-107

List of FiguresFigure 1-1 Map View, Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Figure 1-2 Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Figure 1-3 Network Alarm Summary Window. . . . . . . . . . . . . . . . . . . . . . . . . 1-5Figure 1-4 Alarm Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Figure 1-5 Alarm Profiles Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Figure 1-6 Alarm Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Figure 1-7 Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Figure 1-8 Path Display for Services Screen . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Figure 1-9 Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Figure 1-10 Path Display for Services Screen . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Figure 1-11 Alarm Filter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Figure 1-12 Hardware Fault Detection Descriptions . . . . . . . . . . . . . . . . . . . . . 1-55Figure 1-13 TransNav GUI Service Request Error Window . . . . . . . . . . . . . . . 1-105Figure 1-14 Service Request Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-106Figure 1-15 Services Menu—Show Last Error Option . . . . . . . . . . . . . . . . . . . 1-106

List of TablesTable 1-1 Creating a New Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Table 1-2 Assigning a Port Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Table 1-3 Assigning a Subport Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Table 1-4 Assigning a Service Path Alarm Profile . . . . . . . . . . . . . . . . . . . . . 1-10Table 1-5 Suppress Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Table 1-6 Suppress Service CTP Path Alarms . . . . . . . . . . . . . . . . . . . . . . . 1-13Table 1-7 Viewing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Table 1-8 Alarms, Events and Recommended Actions, A through C . . . . . . 1-20Table 1-9 Alarms, Events and Recommended Actions, D through K . . . . . . 1-37


Release OPS3.1.x Turin Networks Page ix

Table 1-10 Alarms, Events and Recommended Actions, L through S . . . . . . 1-57Table 1-11 Alarms, Events and Recommended Actions, TA200 . . . . . . . . . . 1-91Table 1-12 Alarms, Events and Recommended Actions, TB through TZ . . . . 1-92Table 1-13 Alarms, Events and Recommended Actions, U through Z . . . . . . 1-99Table 1-14 Service Request—Show Last Error . . . . . . . . . . . . . . . . . . . . . . . 1-106Table 1-15 Service Error Codes and Recommended Actions. . . . . . . . . . . . . 1-107


Page x Turin Networks Release OPS3.1.x

Release OPS3.1.x Turin Networks Page 1-1

SECTION 1FAULT MANAGEMENT

Chapter 1Managing 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.

Node Operations and Maintenance Guide, Section 1: Fault ManagementEvent Types

Page 1-2 Turin Networks Release OPS3.1.x

Event Types 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).

Event Logs 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 2-21.

Chapter 1 Managing Alarms and EventsEvents 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

Node Operations and Maintenance Guide, Section 1: Fault ManagementAlarms 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

Figure 1-2 Alarms Tab

StickyMode

Detail View

Set Filters

New WindowCommand

Command

Command

PrintCommand

SaveCommand

View SelectorSort by Column

Map View

Alarm Caption

Node Object

Alarms

Display

List

Alarm Tab

Chapter 1 Managing Alarms and EventsAlarm 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).

Figure 1-3 Network Alarm Summary Window

Service Affecting Status

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.

Alarm Severity Levels

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.

Alarm Summary

Node Operations and Maintenance Guide, Section 1: Fault ManagementAlarm 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

This system conforms to the alarm reporting hierarchy set forth in the Telcordia General Requirements GR-253, ETSI 300-417-3-1, and ITU recommendation G.783.

Customizing Alarms

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

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.

Figure 1-4 Alarm Profile Dialog Box

Chapter 1 Managing Alarms and EventsCreating 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.

Figure 1-5 Alarm Profiles Dialog Box

2

Node Operations and Maintenance Guide, Section 1: Fault ManagementCreating a New Alarm Profile


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.

Figure 1-6 Alarm Profile Dialog Box

Table 1-1 Creating a New Alarm Profile (continued)

Step Procedure

3

Chapter 1 Managing Alarms and EventsAssigning a Port Alarm Profile


Assigning an 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

Assigning a Port Alarm Profile

The following procedure describes how to assign a port alarm profile template to a port.

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.

Table 1-1 Creating a New Alarm Profile (continued)

Step Procedure

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.

Node Operations and Maintenance Guide, Section 1: Fault ManagementAssigning 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.

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-3 Assigning a Subport Alarm Profile

Step Procedure

1 In Shelf View, select a DS3 Transmux module port.


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.

Table 1-4 Assigning a Service Path Alarm Profile

Step Procedure

1 From any view, click the Service tab.

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.

2

1

Chapter 1 Managing Alarms and EventsAssigning a Service Path Alarm Profile


3 Click the CTP tab to display the CTP dialog box.

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).

Table 1-4 Assigning a Service Path Alarm Profile (continued)

Step Procedure

3

2

4a

4b

5

6

Node Operations and Maintenance Guide, Section 1: Fault ManagementSuppressing Alarms


Suppressing 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

Suppress Port Alarms

The following procedure describes how to suppress port (line and path) alarms. Alarm suppression occurs also for all objects contained within the port.

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.

Table 1-4 Assigning a Service Path Alarm Profile (continued)

Step Procedure

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.

Chapter 1 Managing Alarms and EventsService CTP Path Alarm Suppression


Service CTP Path Alarm Suppression

The following procedure describes how to suppress service CTP (connection termination point) path alarms.

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.

Table 1-5 Suppress Port Alarms (continued)

Step Procedure

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.



3

2

Node Operations and Maintenance Guide, Section 1: Fault ManagementService CTP Path Alarm Suppression


3 Select a service. Right-click and select Show Tx/Rx Path to display the 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.

Table 1-6 Suppress Service CTP Path Alarms (continued)

Step Procedure

4

3

5a

5b

6 7

Chapter 1 Managing Alarms and EventsViewing 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 14.

5 Detail View

From the alarm list, select an alarm.

Node Operations and Maintenance Guide, Section 1: Fault ManagementViewing Alarms


6 Click Detail View to display the Alert Detail (View Main) dialog box and view highlighted alarm details.

Go to Step 14.

7 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 14.

8 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 14.

9 Print

Click Print to print the contents of the Alarms tab alarms list.

Go to Step 14.

10 Save

Click Save to save alarm information to a text file.

Go to Step 14.

Table 1-7 Viewing Alarms (continued)

Step Procedure

Chapter 1 Managing Alarms and EventsViewing Alarms


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.

Figure 1-11 Alarm Filter Dialog Box

Go to Step 14.

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.


Step Procedure

Node Operations and Maintenance Guide, Section 1: Fault ManagementViewing Alarms


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.


Step Procedure



Chapter 2Alarms, 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.

Node O

perations and Maintenance G

uide, Section1: Fault M

anagement

Alarm

s/Events, A through C

Page 1-20Turin N

etworks

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

Service Affecting Default

Default SeverityRecommended Action

SA (Unprotected)

NSA (Protected)

ACO: Alarm Cut Off shelf The audible alarm is cut off (silenced) because the operator pressed the ACO/LED control button.

– Info Info (Informational; no action required.)

ACO_CLEAR: Clear Alarm Cut Off

shelf Alarm cutoff is now clear. – Info Info (Informational; no action required.)

ADMINTASK1: Administrative task

server An administrative task was executed.


AIRCOND: Air Conditioning System Fail

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_ptpds3_ptp(ds_ptp)e3_ptp1

ta200te50

The input signal on a DS1, DS3, or EC-1 interface contains an AIS.

SA ical Critical Check the equipment (module/port) upstream.

Clear upstream alarms.

shelf The locally received BITS signal contains an AIS. This indicates a remote BITS failure.

SA Critical Minor Check the BITS upstream.


sonet_ptp The locally received OC-N signal contains an AIS. This indicates a remote OC-N level failure.

SA Critical Minor Check the equipment (module/port) upstream.


Chapter2

Alarms, Events, and R

ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-21

AIS-P: Alarm indication signal – Path

ds3_ptp(ds_ptp)e3_ptpta200te50

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.

SA Critical Critical Check the equipment (module/port) upstream.


Verify your payload connections.

sonet_ptpsonet_sts

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.

SA Critical Minor Check the equipment upstream.



AIS-S1: Alarm indication signal – Service

ds3_ptp(ds_ptp)e3_ptpsdh_ptpsonet_ptpsonet_service

An upstream failure occurred at the Service layer.

– Warning Info Check the equipment upstream.


AIS-V1: Alarm indication signal – VT

ds1_ptpds3_ptp(ds_ptp)e3_ptpshelfsonet_ptpsonet_vtsonet_sts

An upstream failure occurred at the VT path layer.



Verify your VT payload connections.

ta200te50

An upstream failure occurred at the VT path layer.

SA Critical Critical Check the equipment upstream.


Verify your VT payload connections.

sdh_ptp See TU-AIS. n/a n/a n/a See TU-AIS.

Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)




SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-22Turin N

etworks

Release OPS3.1.x

AIS-VC: Alarm indication signal - VC

e1_ptpsdh_ptp

An upstream failure occurred at the VC path layer.



Verify your VC payload connections.

ALS: Automatic laser shutdown ethernet_ptpsdh_ptpsonet_ptp

Transmitter of the optical interface has been turned off automatically after detection of LOS on the receiver.

– Critical Minor Transmitter has been shutdown per G.664. Check remote port transmitter state and fiber and resolve LOS condition.

ALS-TX-OFF: Transmitter automatically disabled

ethernet_ptpsdh_ptpsonet_ptp

Event logged against the optical interface upon ALS alarm condition.


APS-AIS-P1: Automatic protection ( multiplex section protection - MSP) Administrative Unit switching Alarm Indication Signal – Path

shelf A protection switch has occurred due to an AIS-P alarm.

– Info Info See AIS-P.

APS-LOP-P1: Automatic protection switching (multiplex section protection - MSP) Loss of Pointer – Path

shelf A protection switch has occurred due to an LOP-P alarm.

– Info Info See LOP-P.

APS-SDBER-P1: Automatic protection switching (multiplex section protection - MSP) Signal Degrade Bit Error Rate – Path

shelf A protection switch has occurred because of an SDBER-P alarm.

– Info Info See SDBER-P.

APS-SFBER-P1: Automatic protection switching (multiplex section protection - MSP) Signal Fail Bit Error Rate – Path

shelf A protection switch has occurred because of an SFBER-P alarm.

– Info Info See SFBER-P.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-23

APS-UNEQ-P1: Automatic protection switching (multiplex section protection - MSP) Unequipped – (High Order) Path

shelf A protection switch has occurred because of an UNEQ STS path alarm.

– Info Info See UNEQ-P.

APSAISCLEAR1: Automatic protection switching (multiplex section protection - MSP) Alarm Indication Signal Clear

shelf A protection switch which occurred because of an AIS alarm has been cleared.

– Info Info If frequent protection switching occurs, check the revertive WTR period setting.

APSB: Automatic protection switch (multiplex section protection - MSP) byte failure

sonet_ptpsdh_ptp

On a 2F BLSR, the APS K1/K2 bytes are in an invalid state.

– 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.APSBF: Automatic protection

switch byte failure

APSCFGMIS: Automatic protection switch (multiplex section protection - MSP) configuration mismatch

sonet_ptpsdh_ptp

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.

– Minor Minor ■ Check that the fiber is connected properly to the remote node.

■ Check that a remote 1+1 linear PG exists.

APSCM: Automatic protection switch (multiplex section protection - MSP) channel mismatch

sonet_ptpsdh_ptp

On a 2F BLSR, the local Traverse node is not receiving the K1/K2 values it is expecting.

– 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.

APSIMP: Improper automatic protection switching (multiplex section protection - MSP) code

sonet_ptpsdh_ptp

On a 2F BLSR, the automatic protection switching codes are improper. Indicates 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.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-24Turin N

etworks

Release OPS3.1.x

APSINC: Inconsistent automatic protection switching (multiplex section protection - MSP) code

sonet_ptpsdh_ptp

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.

– 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.

APSLOPCLEAR1: Automatic protection switching (multiplex section protection - MSP) Loss of Pointer Clear

shelf A protection switch which occurred because of an LOP-P alarm has been cleared.


APSLOS1: Automatic protection switching (multiplex section protection - MSP) Loss of Signal

shelf A protection switch has occurred because of an LOS alarm.

– Info Info See LOS.

APSLOSCLEAR1: Automatic protection switching (multiplex section protection - MSP) Loss of Signal Clear

shelf A protection switch which occurred because of an LOS alarm has been cleared.


APSMM1: Automatic protection switch (multiplex section protection - MSP) mode mismatch

sonet_ptpsdh_ptp

There is a mismatch of the protection switching schemes at the two ends of the span.

– Minor Minor Check protection modes at both ends. Verify that both ends are set for bidirectional or unidirectional.

APSPATHCLEAR1: Automatic protection switching (multiplex section protection - MSP) Path Clear

shelf A protection switch which occurred because of a path alarm has been cleared.






SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-25

APSPDI1: Automatic protection switching (multiplex section protection - MSP) Path Defect Indication

shelf A protection switch has occurred because of a PDI alarm.

– Info Info See PDI.

APSPDICLEAR1: Automatic protection switching (multiplex section protection - MSP) Path Defect Indication Clear

shelf A protection switch which occurred because of a PDI alarm has been cleared.


APSREL: Automatic protection switching (multiplex section protection - MSP) release

shelf The alarm condition that caused an automatic protection switch has been cleared. This occurs when a protection group has been configured as non-revertive.


APSSDCLEAR1: Automatic protection switching (multiplex section protection - MSP) Signal Degrade Clear

shelf A protection switch which occurred because of an SDBER-P alarm has been cleared.


APSSFCLEAR1: Automatic protection switching (multiplex section protection - MSP) Signal Fail Clear

shelf A protection switch which occurred because of an SFBER-P alarm has been cleared.


APSUNEQCLEAR1: Automatic protection switching (multiplex section protection - MSP) Unequipped Clear

shelf A protection switch which occurred because of an UNEQ STS path alarm has been cleared.






SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-26Turin N

etworks

Release OPS3.1.x

APSWTR: Transition to Wait to Restore mode (multiplex section protection - MSP)

shelf 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.


AU-AIS: Administrative Unit Alarm Indication Signal

ds3_ptpsdh_hpsdh_ptp

The STM signal demultiplexed from the STM-N contains an AIS. This AIS can result from an upstream failure along the STM path.




AU-LOP: Administrative Unit Loss of Pointer


Valid AU pointer bytes are missing from the SDH overhead.

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.

AUTHFAIL1: OSPF authentication key or type mismatch

shelf An OSPF packet has been received whose authentication key or type conflicts with this node’s authentication key or type.

– Minor Minor Retry authentication with new key or type.

AUTOPRV1: Auto provisioning error

sonet_ptpsdh_ptp

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.

– Minor Minor Clear the signal failure.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-27

AUTO-TX-ON: Transmitter automatically enabled


Event against the optical interface when the transmitter has been turned on automatically.


BADPKTRX1: Received an OSPF packet that cannot be parsed

shelf OSPF packet cannot be parsed. – Minor Minor Check configuration and PM.

BATDSCHRG2: Battery is discharging

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.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-28Turin N

etworks

Release OPS3.1.x

BERSD-L: Bit ErrorRate signal degrade – Line

ds3_ptp(ds_ptp)e3_ptp1

The BER on the incoming EC-1 line has exceeded the signal degrade threshold.

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.

shelfte50

The BER on the incoming BITS has exceeded the signal degrade threshold.

– Warning Warning Check cable connectors.

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.

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).





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-29

BERSD-P: Bit Error Rate signal degrade – Path


The STS signal demultiplexed and dropped from the EC-1 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.


sonet_ptpsonet_sts

The STS signal demultiplexed and dropped from the OC-N/STM-N has exceeded its signal degrade threshold.




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.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-30Turin N

etworks

Release OPS3.1.x

BERSD-V: BitError Rate signal degrade – VT Path


The VT signal demultiplexed and dropped from the DS1 has exceeded its signal degrade threshold.




sonet_ptpsonet_stssonet_vtshelf

The VT signal demultiplexed and dropped from the OC-N has exceeded its signal degrade threshold.




sdh_ptp See LP-BERSD. n/a n/a n/a See LP-BERSD.

BERSD-VC: Bit Error Rate signal degrade – VC Path

e1_ptpsdh_ptp

The VC signal demultiplexed and dropped from the STM-N has exceeded its signal degrade threshold.








SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-31

BERSF-L: Bit Error Rate signal fail – Line


The BER on the incoming EC-1 line has exceeded the signal fail threshold.

SA Warning Warning Check cable connectors and module ports.

shelfte50

The BER on the incoming BITS has exceeded the signal fail threshold.

– Warning Warning Check cable connectors.

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.


SA Warning Warning Verify the local receive optical levels, as well as the upstream transmit levels.










SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-32Turin N

etworks

Release OPS3.1.x

BERSF-P: Bit Error Rate signal fail – Path


The STS signal demultiplexed and dropped from the EC-1 has exceeded its signal fail threshold.





sonet_ptpsonet_sts

The STS signal demultiplexed and dropped from the OC-N has exceeded its signal fail threshold.









SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-33

BERSF-V: Bit Error Rate signal fail – VT/VC Path


The VT/VC signal demultiplexed and dropped from the module has exceeded its signal fail threshold.




sonet_ptpsonet_vtsonet_sts

The VT signal demultiplexed and dropped from the OC-N has exceeded its signal fail threshold.


Perform loopback tests to isolate theproblem.


shelf The VT signal demultiplexed and dropped from the OC-N has exceeded its signal fail threshold.




sdh_ptp See LP-BERSF. n/a n/a n/a See LP-BERSF.

BERSF-VC: Bit Error Rate signal fail – VC Path

e1_ptpsdh_ptp

The VC signal demultiplexed and dropped from the STM-N has exceeded its signal fail threshold.




BITSA-FRC: Forced switch - Derived DS1 System BITS 1

shelf A forced switch is in process. – Warning Warning Clear the Forced switch command.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-34Turin N

etworks

Release OPS3.1.x

BITSA-LOCK: Lockout - Derived DS1 System BITS 1

shelf A lockout is in process on this timing reference.

– Warning Warning Clear the Lockout switch command.

BITSA-MAN: Manual switch - Derived DS1 System BITS 1

shelf A manual switch is in process. – Warning Warning Clear the Manual switch command.

BITSB-FRC: Forced switch - Derived DS1 System BITS 2

shelf A forced switch is in process. – Warning Warning Clear the Forced switch command.

BITSB-LOCK: Lockout - Derived DS1 System BITS 2

shelf A lockout is in process on this timing reference.

– Warning Warning Clear the Lockout switch command.

BITSB-MAN: Manual switch - Derived DS1 System BITS 2

shelf A manual switch is in process. – Warning Warning Clear the Manual switch command.

BITSGEN1: BITS event shelf Unused. – Info Info Unused.

BITSRBOC1: BITS RBOC detect shelf Unused. – Info Info Unused.

BLSR_NOT_SYNC: BLSR ring is out of sync

server 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.

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.

BLSR_SYNC_UNKNOWN: BLSR unknown error

server BLSR/MS-SPRing synchronization status is unknown.

– 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.

BOARDFAIL: Board failure alarm ta200 The OMX3 or PM13 board may not be seated correctly in the chassis or has failed.

SA Critical Critical Check that the module is inserted correctly into the chassis. Otherwise, run diagnostics to test the state of the module.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, A

through C

Release O

PS3.1.xTurin N

etworks

Page 1-35

BPSIG: The backplane cannot communicate with other modules

shelf ■ Module defect.■ Backplane slot defect.

SA Critical Minor Replace the module. If the same alarm persists, try another slot in the shelf.

CFGERR1: OSPF configuration parameter mismatch)

shelf A packet was received whose configuration parameters conflict with the node’s configuration parameters.

– Minor Minor Check the configuration.

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.

– 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 ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpethernet_ptpsonet_ptpsdh_ptp

A loopback has been cleared. – Warning Warning (Informational; no action required.)

COM: Communication failure server The management server cannot synchronize with the node.

– Warning Warning Check that the node name was entered exactly as configured with the node-level CLI (the node name is case-sensitive).

ta200te50

The management server cannot synchronize with the node.

SA Warning Warning Check that the node name was entered exactly as configured with the node-level CLI (the node name is case-sensitive).





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-36Turin N

etworks

Release OPS3.1.x

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.

SA Critical Critical Check connectivity and configuration.

1 Not supported in this release.

2 Environmental alarm inputs are customized by each operator.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-37

Alarms/Events, D through K

Table 1-9 Alarms, Events and Recommended Actions, D through K




SA (Unprotected)

NSA (Protected)

DBCRPT: Database corruption servershelf

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).

DBFAIL: Database failed servershelf

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.

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).

DBMIS: Database version mismatch

servershelf

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.

SA Critical Minor ■ Verify that the software version is correct.

■ Contact Turin’s Customer Service (TAC).

DBRED: Redundant Database failed

servershelf

A redundant database failure has occurred as a result of a standby GCM reboot, a connection failure, or abnormal shutdown of database software.

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).

Node O



anagement

Alarm

s/Events, D through K

Page 1-38Turin N

etworks

Release OPS3.1.x

DBSIGN: Database signature mismatch

ds3_ptpe1_ptpe3_ptpethernet_ptpsdh_ptpsonet_ptpservershelfta200te50

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.

DCCFAIL: Data Communications Channel fail

ds3_ptp(ds_ptp)

Not supported on EC-1. SA Major Major Not supported; no action required.


sonet_ptpsonet_stssdh_hpsdh_lpsdh_ptp

■ 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.

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.

Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)




SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-39

DOWN1: Out of service ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpethernet_ptpservershelfsonet_ptpsdh_ptpsonet_serviceta200te50

Unused. – Minor Minor Unused.

DQL1: Degraded quality level ds3_ptpds_ptpe3_ptpshelfsonet_ptpsdh_ptp

The incoming signal has a degraded quality level.

– Minor Minor Check and clean connections.

DS1AIS: Alarm indication signal - DS1

ds1_ptpta200te50

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.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-40Turin N

etworks

Release OPS3.1.x

DS1RAI: Remote alarm indication

ds1_ptpte50

■ 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.

DS3AIS: Alarm indication signal - DS3

ds3_ptpds_ptpta200te50

The DS3 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment.

DS3RAI: Remote alarm indication

ds3_ptpds_ptpta200te50

■ 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.

– 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.

DSR: Data set ready on MPS IM te50 The data set ready signal is not yet received on the MPS IM alarm monitoring system.

SA Critical Critical Check the node, connectivity, and the configuration.

DTR:Data terminal ready on MPS IM

te50 The data terminal ready signal is not yet received on the MPS IM alarm monitoring system.

SA Critical Critical Check the DTE and modem connectivity and the configuration.

E1AIS: Alarm indication signal - E1

e1_ptpta200te50

The E1 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment.

E1LOMCAS: Alarm indication signal - E1

e1_ptp Loss of Multiframe CAS. – Critical Critical Check the interface.

E1LOMCRC: Alarm indication signal - E1

e1_ptp Loss of Multiframe CRC. – Critical Critical Check the interface.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-41

E1RAI: Remote alarm indication

e1_ptp ■ The far-end node has detected a defect signal on an incoming E1.

■ The local node is sending a bad E1 signal towards the E-X.

– Warning Warning Verify that the connections between the E-X and the E1 module are secure.

Verify that the E1 signal entering the far end of the SDH network is error-free.

te50 SA Critical Critical

E3 AIS: Alarm indication signal - E3

e3_ptp The E3 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment.

E3 RAI: Remote alarm indication

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.

– 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.

EFMFAIL: EFM failure shelf EFM (ingress or egress) failure; parity or other error.

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.

– Minor Minor Monitor for further internal queue engine failures.

EQCOMM1: Communication link failed

shelf The link is down. SA Critical Critical Check the link connections.

EQFRCSW1: Forced protection switch – Equipment

shelf A forced protection switch command has been executed on a 1:1 equipment protection group.

– Warning Warning If the reason for executing the forced switch command no longer exists, clear the switch command.

EQINV: Equipment invalid shelf An invalid piece of equipment has been used.

– Critical Critical Plug in a valid piece of equipment.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-42Turin N

etworks

Release OPS3.1.x

EQLOCK1: Protection lockout – Equipment

shelf A lockout protection switch command has been executed on a 1:1 equipment protection group.

– Warning Warning If the reason for executing the lockout switch command no longer exists, clear the switch command.

EQMANSW1: Manual protection switch – Equipment

shelf A manual protection switch command has been executed on a 1:1 equipment protection group.

– Warning Warning If the reason for executing the manual switch command no longer exists, clear the switch command.

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.

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.

EQPT: Equipment malfunction / failure.

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 A hardware failure has occurred on the reporting module.

SA Critical Minor Reseat the module. If this fails to clear the alarm, replace the module if necessary.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-43

EQRMV: Equipment removed shelf A module is not properly seated or it has been removed.

SA Critical Minor Plug in the correct module or delete the module using the TransNav system if that slot is not being used.

ERFI-V: Enhanced (two bit) Remote failure indication – VT Path

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.

– Warning Warning Determine the defects found at the far-end node.


Clear path alarms such as LOP-V, AIS-V, PLM-V, TIM-V, and UNEQ-V from the far-end node.

EXER_SWITCH: Exercise switch on remote node

shelf Checking status of remote node via exercise command (using K1/K2 bytes) for 1+1 bidirectional protection group.

– 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

shelf 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.

– Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table.

EXTA-REF2-ALM: Secondary reference in alarm

shelf 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.






SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-44Turin N

etworks

Release OPS3.1.x

EXTA-REF3-ALM: Third reference in alarm

shelf 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.


EXTA-REF4-ALM: Fourth reference in alarm

shelf 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.


EXTB-REF1-ALM: Primary reference in alarm.

shelf 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.


EXTB-REF2-ALM: Secondary reference in alarm

shelf 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.


EXTB-REF3-ALM: Third reference in alarm

shelf 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.


EXTB-REF4-ALM: Fourth reference in alarm

shelf 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.






SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-45

FANCOMM: Fan tray communication failure

shelf Communication failure with the fan tray.

– Minor Minor Reseat the fan tray.

FANCOND: Fan tray condition shelf EEPROM failure or thermistor failure.

– Warning Warning Replace the fan tray.

FANFLTR: Fan filter shelf Temperature has exceeded 49 ºC.

– 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.

FEP1: Far-end protection failure sonet_ptpsdh_ptp

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.

FILE_UPLOAD: Single file transfer

shelf File upload is in process. – Info Info (Informational only; no action required.)

FIRDETR: Fire detector failure shelf Fire detection equipment has failed.

– Minor Minor Check fire detection equipment and power source.

Check and follow your method of procedures.

FIRE2: Fire shelf Fire detected. – Minor Minor Check and follow your method of procedures.

FLOOD2: Flood shelf Flood detected. – Minor Minor Check and follow your method of procedures.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-46Turin N

etworks

Release OPS3.1.x

FLOW-DEGRADED: VPG Degraded Flow

ethernet_ptp 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).

SA Major Major The system clears flow-related alarms once it unlearns the flow.

FLOW-LEARNED: Learned VLAN Flow

ethernet_ptp The system has learned a VLAN flow.


FLOW-UNLEARNED: Unlearned VLAN Flow

ethernet_ptp The system has unlearned a single VLAN flow either automatically or through an operator request.


FLOWS-UNLEARNED: Unlearned All VLAN Flows

ethernet_ptp The system has unlearned all the VLAN flows through an operator request.


FLOW-UNPROTECTED: VPG Unprotected Flow

ethernet_ptp 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.

– Minor Minor The system clears flow-related alarms once it unlearns the flow.

FOPR: Failure of protocol - receive

eossdh_eos

LCAS has detected unexpected behavior by the remote LCAS peer.

SA Critical Critical Check remote peer for proper configuration.

FOPT: Failure of protocol - transmit

eossdh_eos

LCAS has detected unexpected behavior by the remote LCAS peer.

SA Critical Critical Check remote peer for proper configuration.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-47

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.

SA Warning Warning Verify that the reason for performing the forced switch no longer exists.

Clear the switch command.

FORCED: Forced protection switching

shelf A forced protection switch has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group.

– Warning Warning Verify that the reason for performing the forced switch no longer exists.


FORCED_ON_PROT: Forced protection switch on protecting unit

shelf A forced protection switch has been performed on a protection group.



FORCED_ON_SECT1: Forced protection switch on optimized 1+1 APS working section 1

shelf 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.







SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-48Turin N

etworks

Release OPS3.1.x

FORCED_ON_SECT2: Forced protection switch on optimized 1+1 APS working section 2

shelf A forced switch has been performed on the optimized 1+1 APS bi-directional working section 2.




FORCED_ON_WORK: Forced protection switch on working unit

shelf A forced protection switch has been performed on the working unit.



FORCED-EAST: Forced switch applied on east facility

shelf A forced protection switch has been performed on the east facility.



FORCED-WEST: Forced switch applied on wast facility

shelf A forced protection switch has been performed on the west facility.



FUSE: Fuse failure shelf A fuse has failed. – Minor Minor Check and follow your method of procedures.

GENFAIL2: 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.

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.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-49

GIDERR: LCAS group ID mismatch

shelf 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.



■ Check the cable and interface.

GIDM: Group ID mismatch eossdh_eos

Group ID mismatch. SA Critical Critical The expected group ID does not match the received group ID.

H4-LOM: H4 Loss of multiframe

ds3_ptpsdh_hpsdh_lpsdh_ptpsonet_ptpsonet_sts

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.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-50Turin N

etworks

Release OPS3.1.x

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.

– Minor Minor Check and follow your method of procedures.

HP-BERSD: Bit error rate signal degrade - High order Path


The STM signal demultiplexed and dropped from the STM-N has exceeded its signal degrade threshold.

– 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.



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 (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-51

HP-BERSF: Bit error rate signal degrade - High order Path


The STM signal demultiplexed and dropped from the STM-N has exceeded its signal fail threshold.

– 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 theproblem.



HP-LOM: High order path Loss of multiframe

sdh_eossdh_eos_ctp

An error is detected in the paths multiframe indicator.

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.

HP-MND: High order path Member not deskewable

sdh_eossdh_eos_ctp

Differential Delay exceeded on EOS member and the member was removed from the group.

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.

HP-SQM: High order path Sequence ID mismatch

sdh_eossdh_eos_ctp

The member sequence number is in error.


If non-LCAS, check that the order of members in the remote EOS matches the local order

HP-PLM: Payload label mismatch received - High order Path


■ Invalid C2 byte (signal label byte) in the SDH path overhead.

■ The payload does not match what the signal label is reporting.

SA Critical Minor Connect correct payload.

Verify that the payload is the same as the provisioned payload/service.





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-52Turin N

etworks

Release OPS3.1.x

HP-RDI: Remote Defect Indication - High order Path


Valid STM-N framing is not detected or AU-AIS (or MS-AIS) is received from the source.

– Warning Warning Check STM-N framing source.See AU-AIS.

See MS-AIS.

HP-RFI: Remote Failure Indication - High order Path

sdh_hpsdh_ptp

■ The signal demultiplexed from the STM-N contains a remote failure indication.




Clear path alarms from the far-end node.

HP-RFICON: Remote failure indication, connectivity defect - High order Path


Far end path has an HP-UNEQ or HP-TIM alarm.

– 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.

HP-RFIPAY: Remote failure indication, payload defect - High order Path


Far end path has a HP-PLM alarm.


Check for far end alarms, especially HP-PLM.

Refer to the recommended actions for HP-PLM.

HP-RFISVR: Remote failure indication, server defect - High order Path


Far end path has an AU-AIS or AU-LOP alarm.

– 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.

HP-TIM: Trace identifier mismatch - High order Path


The expected path trace string (J1 byte in the SDH path overhead) 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.





SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-53

HP-UNEQ: Unequipped - High order Path


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 ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptp

Service is not provisioned over the interface.

SA Warning Warning Check the interface.

Check the far-end node.

INCOMPATSW: Incompatible software

servershelf

Software is incompatible between modules that are attempting communication with each other.

– 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.

INTRUDER: Intrusion shelf – Minor Minor





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-54Turin N

etworks

Release OPS3.1.x

INDICATION: Indication Alarm on MPS IM

te50 SA Critical Critical

KBYTE: Default K byte sonet_ptpsdh_ptp

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.

– Minor Minor Check protection mode for far-end node.







SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, D

through K

Release O

PS3.1.xTurin N

etworks

Page 1-55

Figure 1-12 Hardware Fault Detection Descriptions

Node O



anagement

Page 1-56Turin N

etworks

Release OPS3.1.x

Chapter2


ecomm

ended ActionsA

larms/Events, L through S

Release O

PS3.1.xTurin N

etworks

Page 1-57

Alarms/Events, L through S

Table 1-10 Alarms, Events and Recommended Actions, L through S




SA (Unprotected)

NSA(Protected)

LBC: TXlaser bias current threshold violation

ethernet_ptpsdh_ptpsonet_ptpshelf

TXlaser bias current threshold violation.

– Warning Warning Check laser bias.

LBCNRML1: Laser bias current normalized threshold crossing alert.

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)

– Info Info Check for LCAS (GIDERR, SSF) or member path alarms and proceed as directed.

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)


LEAK2: Leak shelf Leak detected. – Minor Minor Check and follow your method of procedures.

LFD: Loss of Frame Delineation eossdh_eos

GFP has lost sync. SA Critical Critical Check the paths associated with the EOS members for alarms.

Node O



anagement

Alarm

s/Events, L through S

Page 1-58Turin N

etworks

Release OPS3.1.x

LINKFAIL: Link failure ethernet_ptp ■ Transmitter/receiver failure.

■ Fiber connection lost.■ A module along the path

has been removed.

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 5-53.

LINK_FRCD_DIS: Duplex mode mismatch

ethernet_ptp There is a Duplex mode port parameter mismatch between the near- and far-end Ethernet ports.

SA Critical Critical Check the Duplex mode of the Ethernet interfaces.

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.

LNKBCPTY3: Link broadcast message parity error

shelf Unused. – Minor Minor Unused.

LNKBLKCNT3: Link block count error


Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)




SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-59

LNKBLKPTY3: Link block parity error


LNKCRC3: Link CRC error shelf Unused. – Minor Minor Unused.

LNKCSUM3: Link checksum error


LNKDOWN3: Link down shelf Unused. – Info Info Unused.

LNKERR3: Unrecognized link error


LNKOVFL3: Link overflow shelf Unused. Minor Minor Unused.

LNKPAPTY3: Link path alarm parity error


LNKRXCORR3: Link receive corruption


LNKRXDROP3: Link receive drop


LNKRXLEN3: Link receive length error


LNKRXSTAT3: Link receive stat count error


LNKTXCORR3: Link transmit corruption


LNKTXDROP3: Link transmit drop


LNKUP1: Link up shelf The link is now up. – Info Info (Informational; no action required.)





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-60Turin N

etworks

Release OPS3.1.x

LO-LBC: TX laser bias current exceeds low alarm threshold

sonet_ptp SFP optic alarm. Set when TX Bias current is below low alarm level as a result of a possible component failure.

– Warning Warning Contact Turin’s Customer Service (TAC).

LO-OPR: Optical power received exceeds low alarm threshold

sonet_ptp SFP optic alarm. as a result of a possible input level problem at the patch panel OR the need to clean the fibers.

– Warning Warning ■ Check receive input level at patch panel.

■ Clean fibers if necessary.

LO-OPT: Optical power transmitted exceeds low alarm threshold

sonet_ptp SFP optic alarm. Set when TX Bias current is below low alarm level as a result of a possible component failure.


LO-TEMP: Internal temp exceeds low alarm threshold

sonet_ptp SFP optic alarm. Set when internal temperature is below low alarm level as a result of a possible component failure.


LO-VCC: Internal voltage exceeds low alarm threshold

sonet_ptp SFP optic alarm. Set when internal supply voltage is below low alarm level as a result of a possible component failure.


LOA: Loss of Assignment eossdh_eos

Differential Delay exceeded on active EOS member.

SA Critical Critical Check the EOS member status to determine which paths have exceeded the delay and reroute them.

LOCKOUT4: Lockout automatic protection switching

shelf A lockout protection switch command has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group.

– Warning Warning If protection required, investigate and remedy lockout provisioning. Otherwise, no action required.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-61

LOCKOUT-LPS: Lockout of Protection Ring

shelf A lockout protection ring command has been performed on a BLSR protection ring.

– Warning Warning Clear “Lockout Protection Ring” from the BLSR protection group.

LOCK_WORK1: Lockout automatic protection switching

shelf A lockout protection switch command has been performed on a working module in a 1:N Transmux equipment protection group.


















SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-62Turin N

etworks

Release OPS3.1.x












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.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-63














SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-64Turin N

etworks

Release OPS3.1.x

LOF: Loss of frame ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpta200te50

Framing problem on the incoming signal.

SA Critical Critical Inspect all facilities related to the STS link.

Check remote sites for module removal/failure alarms.

Check the cable and interface.

ethernet_ptp Generic Framing Procedure (GFP) framing problem on the incoming bit stream.

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.

shelf Framing problem on the incoming BITS.

– Minor Minor Inspect all facilities related to the BITS.

Check remote sites for BITS alarms.

Check the cable connection.

sonet_ptpsdh_ptp

Framing problem on the incoming OC-N signal.

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.


Check the upstream node for OC-N module failure/removal.

Verify good optical connections to the local and far-end OC-N modules.

LOG: Loss of Group eossdh_eos

Loss of Group. SA Critical Critical Check the paths associated with the EOS members for alarms.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-65

LOGINFAIL: Login failed servershelf

Login attempt has failed. – Info Info ■ Try again.■ Check the login log; contact your

system administrator – persistent login failures could indicate possible hacking.

LOGINSUCC: Login successful servershelf

Login has succeeded. – Info Info (Informational; no action required.)

LOGINTERM: Login terminated

servershelf

Login has terminated. – Info Info (Informational; no action required.)

LOL: Loss of link te50 SA Critical Critical

LOM1: Loss of Multiframe, Rx path

ethernet_ptpsdh_ptp

shelf

Unused. SA Critical Minor Unused.

te50 SA Warning Warning

LOM-P: Loss of Multiframe synchronization - STS

eoseos_ctp



LOM-V: Loss of Multiframe synchronization - VT

eoseos_ctp







SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-66Turin N

etworks

Release OPS3.1.x

LOP-P: Loss of Pointer – Path ds3_ptp(ds_ptp)e3_ptpsonet_ptpsonet_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 that the expected bandwidth and received bandwidth are the same.


ethernet_ptp1 Valid pointer bytes are missing. SA Critical Minor Check the cabling and physical connections on the reporting module.

ta200te50

Valid pointer bytes are missing. SA Critical Critical Check the cabling and physical connections on the reporting module.

LOP-V1: Loss of Pointer – VT ds1_ptpds3_ptp(ds_ptp)e3_ptpshelfsonet_ptpsonet_vtsonet_sts

Valid pointer bytes are missing from the VT overhead.





ta200te50

Valid pointer bytes are missing from the VT overhead.

SA Critical Critical Check the cabling and physical connections on the reporting module.




sdh_ptp See TU-LOP. n/a n/a n/a See TU-LOP.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-67

LOP-VC1: Loss of Pointer – VC e1_ptpsdh_ptp

Valid pointer bytes are missing from the VC overhead.





LOS: Loss of signal ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpta200te50

■ 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 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_ptpsdh_ptp

■ 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.

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.





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-68Turin N

etworks

Release OPS3.1.x

LP-BERSD: Bit error rate signal degrade - Low order Path

sdh_hpsdh-lpsdh_ptp

The STM signal demultiplexed and dropped from the STM-N has exceeded its signal degrade threshold.

– 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.




LP-BERSF: Bit error rate signal degrade - Low order Path

sdh_hpsdh-lpsdh_ptp

The STM signal demultiplexed and dropped from the STM-N has exceeded its signal fail threshold.

– 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.




LPBKEQPT: Equipment loopback active

ds1_ptpds3_ptpe1_ptpethernet_ptpsdh_ptpsonet_ptp

Equipment is in active loopback state.

– Warning Warning Validate this state.

Clear loopback, as required.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-69

LPBKFACILITY: Facility loopback active

ds1_ptpds3_ptpe1_ptpe3_ptpethernet_ptpsdh_ptpshelfsonet_ptp

Facility is in active loopback state.

– Warning Warning Validate this state.


LPBKINBAND: Inband loopback active

ds3_ptp An inband loopback is active. – Warning Warning Validate this state.


LPBKTERM: Terminal loopback active

ds1_ptpds_ptpe1_ptpe3_ptpethernet_ptpsdh_ptpshelfsonet_ptp

A terminal loopback is active. – Warning Warning Validate this state.


LP-LOM: Low order path Loss of multiframe synchronization

sdh_eossdh_eos_ctp



If not using LCAS, check that EOS member order matches that of the remote EOS.

LP-MND: Low order path Member not de-skewable

sdh_eossdh_eos_ctp



Check the EOS member status to determine which paths have exceeded the delay and reroute them.





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-70Turin N

etworks

Release OPS3.1.x

LP-PLM: Payload label mismatch received - Low order Path

sdh_hpsdh-lpsdh_ptp

■ Invalid byte in the Low Order path overhead.




LP-RDI: Remote Defect Indication - Low order Path

sdh_hpsdh-lpsdh_ptp

Valid STM-N framing is not detected or AU-AIS is received from the source.

– Warning Warning Check STM-N framing source.See AU-AIS.

LP-RFI: Remote Failure Indication - Low order Path

sdh_hpsdh-lpsdh_ptp

■ The signal demultiplexed from the STM-N contains a remote failure indication.




Clear path alarms from the far-end node.

LP-RFICON: Remote failure indication, connectivity defect - Low order Path

sdh_hpsdh-lpsdh_ptp

Far end path has an LP-UNEQ or LP-TIM alarm.


Check for far end alarms, especially LP-UNEQ and LP-TIM.

Refer to the recommended actions for LP-UNEQ and LP-TIM.

LP-RFIPAY: Remote failure indication, payload defect - Low order Path

sdh_hpsdh-lpsdh_ptp

Far end path has a LP-PLM alarm.


Check for far end alarms, especially LP-PLM.

Refer to the recommended actions for LP-PLM.

LP-RFISVR: Remote failure indication, server defect - Low order Path

sdh_hpsdh-lpsdh_ptp

Far end path has an AU-AIS or AU-LOP alarm.

– 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 (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-71

LP-SQM: Low order path Sequence ID mismatch

sdh_eossdh_eos_ctp


SA Critical Critical If non-LCAS, check that the order of members in the remote EOS matches the local order.

LP-TIM: Trace identifier mismatch - Low order Path

ssdh_hpsdh-lpsdh_ptp

The expected path trace string does not match the received path trace string.



LP-UNEQ: Unequipped - Low order Path

sdh_hpsdh-lpsdh_ptp


SA Critical Minor Check your connection.

Connect your proper payload.

Check the service source.

LSDBOVFL1: Exceeded maximum number of LSAs


LSM1: 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.

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.





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-72Turin N

etworks

Release OPS3.1.x

MANUAL: Manual protection switching

shelf A manual protection switch has been executed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group.


MAN_ON_PROT: Manual protection switching

shelf A manual protection switch has been executed on the protecting port of a protection group.


MAN_ON_WORK: Manual protection switching

shelf A manual protection switch has been executed on a working port of a protection group.


MAN-TX-OFF: Transmitter manually disabled


Operator disabled the optical laser.


MAN-TX-ON: Transmitter manually enabled


Operator enabled the optical laser.


MAXAGE1: Maximum age shelf Unused. – Minor Minor Unused.

MISC: Misc (default) shelf – Minor Minor

MND-P: Member not de-skewable - STS

eoseos_ctp


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.

MND-V: Member not de-skewable - VT

eoseos_ctp


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 (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-73

MPU_BATTERY_A: Battery A alarm

ta200 SA Critical Critical

MPU_BATTERY_B: Battery B alarm


MS-AIS: Alarm Indication Signal - Multiplex Section

sdh_ptp An upstream failure occurred at the multiplex section layer.



Verify your multiplex section payload connections.

MS-BERSD: BER signal degrade - Multiplex Section

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.


– Critical Minor Verify the local receive optical levels, as well as the upstream transmit levels.






If the problem persists, contact Turin’s Customer Service (TAC).





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-74Turin N

etworks

Release OPS3.1.x

MS-BERSF: BER signal fail - Multiplex Section

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.


– Critical Minor Verify the local receive optical levels, as well as the upstream transmit levels.






MS-RDI: Remote Defect Indicator - Multiplex Section

sdh_ptp Valid STM-N framing is not detected or MS-AIS is received from the source.

– Warning Warning Check STM-N framing source.See MS-AIS.

MSSP_NOT_SYNC: MS-SP Ring synchronization failure

server 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.

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.

MSSP_SYNC_UNKNOWN: Unknown error

server MSSP ring synchronization status is unknown.

– Warning Warning Issue sync command to resynchronize the ring.

MULT_PRIMARY_SERVER server There are multiple primary servers discovered. Only one primary server is allowed.

SA Major Warning Restore the environment to one primary server.

NEIGHSC1 shelf Unused. – Minor Minor Unused.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-75

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.

NEWLSA1 shelf Unused. – Minor Minor Unused.

NO_OUTPUT: Output Signal Activity Failure


NO_PRIMARY_SERVER: No primary TransNav server

server The primary server was not found.

SA Major Warning Check connectivity.

If no primary server in the network, set up a primary server in the network environment.

NODEEQMIS: Node equipment mismatch

server Server-Agent equipment mismatch.

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.

NODEIDMIS: Node ID mismatch

sonet_ptpsdh_ptp

The node ID selected is already in use.

– Minor Minor Check all node IDs. Verify that they are each unique.





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-76Turin N

etworks

Release OPS3.1.x

NODESYNC: Node synchronization

server ■ Discovery of and synchronization with a new node.

■ GCM protection switch.

– Warning Warning ■ Wait for node synchronization to complete.

■ Check network server connections.

NO-REMOTE-LCAS: No remote LCAS

eossdh_eosshelf

The remote peer does not have LCAS capability or the capability is undetermined.

– Warning Warning Enable LCAS on the remote nodes EOS.

Check remote peer configuration, capability, and connectivity.

NPM: No provisioned members eossdh_eoslag

No members have been provisioned.

SA Critical Critical Add CTP members to the EOS port.

Add ports to the LAG.

OPENDR: Door open shelf A door is open in the environment.

– Minor Minor Validate that the door should be open.

Close the door, as necessary.

OPR: Optical power received threshold violation


Received optical power does not meet guaranteed value.

– Warning Warning Check interface.

OPT: Optical power transmitted threshold violation


Current is outside guaranteed bounds.

– Warning Warning Measure power level using optical power meter.

ORPNORM1: Optical receive power normalized threshold crossing alert

shelf Unused. – Warning Warning Unused.

OTPNORM1: Optical transmit power normalized threshold crossing alert

shelf Unused. – Warning Warning Unused.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-77

OVERTEMP: Fan tray temperature has exceeded a maximum value

shelf Fan tray temperature has exceeded 56 ºC.

– Minor Minor Check that the temperature of the room is not abnormally high.

Replace the fan tray air filter.

OVERVOLTAGE_A1: Exceeded a maximum voltage value - Enhanced GCM_A

shelf GCM_A has triggered due to an over voltage condition.

The Enhanced GCM triggers the over-voltage alarm at -60.5 VDC. It clears this alarm at -58.5 VDC.

– Minor Minor Check power system, breaker, fuse, and related cabling for power input A.

OVERVOLTAGE_B1: Exceeded a maximum voltage value - Enhanced GCM_B

shelf GCM_B has triggered due to an over voltage condition.

The Enhanced GCM triggers the over-voltage alarm at -60.5 VDC. It clears this alarm at -58.5 VDC.

– Minor Minor Check power system, breaker, fuse, and related cabling for power input B.

PCASQLCH1: PCA channel squelched

sonet_ptpsdh_ptp

Extra traffic carried on protection channel(s) has been squelched due to a protection switch.

– Minor Minor Clear the protection switch.

Check equipment ring topology configuration.

PDI-n (P, n<2)1: Payload defect indicator

ds3_ptp(ds_ptp)e3_ptpsdh_hpsdh-lpsdh_ptpsonet_sts

Payload defect indication. SA Minor Minor Check cable connectors and module ports.

sonet_ptpsdh_ptp

Payload defect indication. – Minor Minor Clean the fiber connections.





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-78Turin N

etworks

Release OPS3.1.x

PDI-n (1<n<5)1:Payload defect indicator

ds3_ptp(ds_ptp)e3_ptp

Payload defect indication. SA Major Minor For DS3/EC1 modules, check cable connectors and module ports.

sonet_ptpsdh_ptp

Payload defect indication. SA Major Minor For OC-N modules, clean the fiber connections.

PDI-n (n>4)1:Payload defect indicator


Payload defect indication. SA Critical Minor For DS3/EC1 modules, check cable connectors and module ports.

sonet_ptpsdh_ptp

Payload defect indication. SA Critical Minor For OC-N modules, clean the fiber connections.

PKTRETX1: An OSPF packet has been retransmitted


PLC: Partial loss of capacity lag At least one port in the LAG is down.

SA Critical Critical At least one port in the LAG is down.

Check for proper cabling and that local and remote port configurations match.

PLCPLOF1: PLCP (Physical Layer Convergence Procedure) loss of frame



PLCPRFI1: PLCP (Physical Layer Convergence Procedure) Remote Failure Indication


Unused. – Warning Info Unused.

PLCR: Partial loss of capacity - receive

eossdh_eos

Capacity loss on path. SA Critical Critical Check the paths associated with the EOS members for alarms.

PLCT: Partial loss of capacity - transmit

eossdh_eos

Capacity loss on path. SA Critical Critical Check the paths associated with the EOS members for alarms.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-79

PLINESQL1: Persistent line squelching

sonet_ptpsdh_ptp

STS (high order) path on the reporting OC-N/STM-N line has been squelched to avoid a misconnection.


PLM:Payload label mismatch received

ds3_ptp(ds_ptp)e3_ptpsonet_ptpsonet_sts

■ Invalid C2 byte (signal label byte) in the SONET path overhead.




PLM-P: Path label mismatch ta200te50

Payload label mismatch on the path.

– Warning Warning Verify that the payload is the same as the provisioned payload/service.

PLM-V: Payload label mismatch received

ds1_ptpds3_ptp(ds_ptp)e3_ptpshelfsonet_ptpsonet_vtsonet_sts

■ Invalid byte in the path overhead.




te50 ■ Invalid byte in the path overhead.


– Warning Warning Connect correct payload.


PLM-VC: Payload label mismatch received - VC

e1_ptpsdh_ptp

■ Invalid byte in the path overhead.








SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-80Turin N

etworks

Release OPS3.1.x

PMCFG: PM configuration error

ds3_ptp(ds_ptp)e1_ptpe3_ptpethernet_ptpsonet_ptpsdh_ptp

PM configuration is incorrect. – Warning Warning Check configuration.

PMDATALOST: Performance data lost

servershelf

PM data loss. – Info Info (Informational; no action required.)

POWER: Commercial power failure

shelf The commercial power source has failed.


PS: Automatic protection switch shelf An automatic protection switch has occurred.

– Info Info Check the equipment.

PUMPFAIL2: Pump failure shelf Pump has failed. – Minor Minor Check and follow your method of procedures.

PWFAIL-A: Power problem—power input A failed

shelf GMT A fuse, cabling, circuit breaker, or power system unit has failed.


PWFAIL-B: Power problem —power input B failed

shelf GMT B fuse, cabling, circuit breaker, or power system unit has failed.


PWR-48: 48VDC power supply failure

shelf Commercial fuse, cabling, circuit breaker, or power system unit has failed.


QEFAIL: Queue Engine fail shelf Internal forwarding queue engine error.

SA Critical Critical Contact Turin’s Customer Service (TAC).

RECTFAIL2: Rectifier failure shelf Rectifier has failed. – Minor Minor Check and follow your method of procedures.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-81

RECTHIGH2: Rectifier high voltage

shelf Rectifier has high voltage. – Minor Minor Check and follow your method of procedures.

RECTLOW2: Rectifier low voltage

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.

– Critical Critical Check the cable and configuration at the remote port.

REMOTE-LINKFAIL: Remote loss of client signal

ethernet_ptp Link Integrity enabled and indicating that the remote Ethernet port is down.

SA Critical Critical Check the cable and configuration at the remote port.

RESOURCE_MISMATCH: STSRM/VTRM Resource Mismatch

shelf 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.

SA Critical Minor Contact Turin’s Customer Service (TAC).





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-82Turin N

etworks

Release OPS3.1.x

RFI-L: Remote failure indication – Line

ds3_ptp(ds_ptp)ta200te50

■ The locally received EC-1 signal contains an RFI.

■ The local EC-1 module is sending a bad signal to the remote node.

– Warning Warning Check module/port.

Check cable and connections.

Check for and resolve LOS, LOF, and AIS alarms in the far-end 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.

– 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.


Check the fiber connection on adjacent equipment.

RFI-P: Remote failure indication – Path


ta200te50

■ The signal demultiplexed from the EC-1 contains an RFI.




Clear path alarms such as LOP-P, AIS-P, PLM-P, TIM-P, and UNEQ-P from the far-end node.

sonet_ptpsonet_sts

■ The STS-1 signal demultiplexed from the OC-N contains an RFI-P.


SA Warning Warning Determine the defects found at the far-end node.


Clear path alarms such as LOP-P, AIS-P, and UNEQ-P from the far-end node.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-83

RFI-V: Remote failure indication

ds1_ptpds3_ptp(ds_ptp)sonet_ptpsonet_vtsonet_stsshelfta200te50

■ 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.



Clear path alarms such as LOP-P, AIS-P, PLM-P, TIM-P, and UNEQ-P from the far-end node.

e3_ptp1

sdh_ptp■ 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.



Clear path alarms such as LOP-V, AU-AIS, LP-PLM, LP-TIM, and LP-UNEQ from the far-end node.

RFI-VC: Remote failure indication

e1_ptpsdh_ptp

■ 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.



Clear path alarms such as LOP-V, AU-AIS, LP-PLM, LP-TIM, and LP-UNEQ from the far-end node.





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-84Turin N

etworks

Release OPS3.1.x

RFICON: Remote failure indication – Connectivity defect

ds3_ptp(ds_ptp)sonet_ptpsonet_sts

Far end path has an UNEQ-P or TIM-P alarm.

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.

e3_ptpsdh_ptp

Far end path has an UNEQ-P or TIM-P alarm.


Check for far end alarms, especially UNEQ-P and TIM-P.

Refer to the recommended actions for UNEQ-P and TIM-P.

RFICON-V: Remote failure indication – Connectivity defect

ds1_ptpds3_ptp(ds_ptp)shelfsonet_ptpsonet_vtsonet_sts

Far-end VT path has an UNEQ-V or TIM-P alarm.


Check for far end alarms, especially UNEQ-V and TIM-V.

Refer to the recommended actions for UNEQ and TIM.

e3_ptpsdh_ptp

Far end VC path has an LP-UNEQ or LP-TIM alarm.




RFICON-VC: Remote failure indication – Connectivity defect

e1_ptpsdh_ptp

Far-end VC path has an LP-UNEQ or LP-TIM alarm.








SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-85

RFIPAY: Remote failure indication – Payload defect

ds3_ptp(ds_ptp)sonet_ptpsonet_sts

Far end path has a PLM-P alarm.


Check for far end alarms, especially PLM-P.

Refer to the recommended actions for PLM.

e3_ptpsdh_ptp

Far end path has a HP-PLM alarm.


Check for far end alarms, especially HP-PLM.

Refer to the recommended actions for HP-PLM.

RFIPAY-V: Remote failure indication – Payload defect


Far end path has a PLM-V alarm.


Check for far end alarms, especially PLM-V.

Refer to the recommended actions for PLM.

e3_ptpsdh_ptp





RFIPAY-VC: Remote failure indication – Payload defect

e1_ptpsdh_ptp









SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-86Turin N

etworks

Release OPS3.1.x

RFISVR: Remote failure indication – Server defect

ds1_ptpds3_ptp(ds_ptp)sonet_ptpsonet_sts

Far end path has an AIS-P or LOP-P alarm.


Check for far end alarms, especially AIS-P and LOP-P.

Refer to the recommended actions for AIS-P and LOP-P.

e3_ptpsdh_ptp

Far end path has an AIS-P or LOP-P alarm.


Check for far end alarms, especially AIS-P and LOP-P.

Refer to the recommended actions for AIS-P and LOP-P.

RFISVR-V: Remote failure indication – Server defect


Far end path has an AIS-V or LOP-V alarm.


Check for far end alarms, especially AIS-V and LOP-V.

Refer to the recommended actions for AIS-V and LOP-V.

e3_ptpsdh_ptp

Far end path has an TU-AIS or TU-LOP alarm.


Check for far end alarms, especially TU-AIS and TU-LOP.

Refer to the recommended actions for TU-AIS and TU-LOP.

RFISVR-VC: Remote failure indication – Server defect

e1_ptpsdh_ptp

Far end path has an TU-AIS or TU-LOP alarm.


Check for far end alarms, especially TU-AIS and TU-LOP.

Refer to the recommended actions for TU-AIS and TU-LOP.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-87

RLSD: Receive Line Signal Detect on MPS IM

te50 Line signal not detected. SA Critical Critical Check connectivity and configuration at the remote end.

RS-TIM: Trace identifier mismatch

sdh_ptp The expected path trace string does not match the received path trace string.



RTS: Request to send on MPS IM

te50 Request to send not present. SA Critical Critical Check connectivity and configuration.

SENSORFAIL: Thermal sensor failure

shelf The thermal sensor on a line or control module has failed.

– 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.

SERVER_LOGINFAIL: Server login to node failed

server Node login authentication failed.

– Critical Critical ■ Try again.■ Contact your system administrator –

persistent login failures could indicate possible hacking.

SERVER_ROLE servershelf

Event identifies the server role as primary or secondary.


SETOPER: Set operation performed

servershelf

A set operation has been performed.


SFO1: Sync frequency offset ds3_ptp(ds_ptp)sonet_ptp

EC-1 or SONET facility timing. – Minor Minor Check timing signal quality.

e3_ptpsdh_ptp

SONET facility timing. – Minor Minor Check timing signal quality.





SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-88Turin N

etworks

Release OPS3.1.x

SFPMIS: SFP mismatch ethernet_ptpsdh_ptpsonet_ptpshelf

There is a mismatch on the SFP interface.

– Critical Minor Check interface.

SFPRMV: SFP removed ethernet_ptpsdh_ptpsonet_ptpshelf

The SFP has been removed. – Critical Minor Check interface.

SHELFMIS: Shelf type mismatch

server 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.

SMOKE2: Smoke detected shelf Smoke detected. – Minor Minor Check and follow your method of procedures.

SQLCHTBL1: Squelch table mismatch

sonet_ptpsdh_ptp

■ 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.

SQM1: Sequence number change

ethernet_ptpshelf


SQM-P: Sequence ID mismatch- STS

eoseos_ctp


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 (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-89

SQM-V: Sequence ID mismatch- VT

eoseos_ctp


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.

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.



■ Check the cables and interfaces.

SVC_STATUS1: Service status report

servershelf

Unused. – Info Info Unused.

SWCRPT: Software corruption servershelf

Software did not load or loaded with errors.

SA Critical Minor Contact Turin’s Customer Service (TAC).

SWERR: Software error all objects The software has detected an unexpected error.

– Info Info Contact Turin’s Customer Service (TAC).

SWITCH1: Pointer switch ethernet_ptp Unused. SA Critical Minor Unused.

SWITCH_TO_PROT: Traffic switch to Protection

shelf 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.


SWITCH_TO_SECT1: Traffic switch on optimized 1+1 APS working section 1

shelf Traffic has switched on the optimized 1+1 APS bi-directional working section 1.







SA (Unprotected)

NSA(Protected)

Node O



anagement

Alarm


Page 1-90Turin N

etworks

Release OPS3.1.x

SWITCH_TO_SECT2: Traffic switch on optimized 1+1 APS working section 2

shelf Traffic has switched on the optimized 1+1 APS bi-directional working section 2.


– Warning Warning ■ Verify that the switch was expected.■ Check the switch-from section for

degraded performance or other relevant alarm conditions.

SWITCH_TO_WORK: Traffic switch to Working

shelf 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.

– Warning Warning ■ Verify that the switch was expected.■ Check the switch-from section for

degraded performance or other relevant alarm conditions.

SWMIS: Software version mismatch

all objects The reporting module is not running with the same software version as the active GCM.

– Minor Minor Reinstall correct software.

SW_UPG: Software upgrade shelf Software upgrade event is in process.


SW_UPG_PROG shelf Software upgrade is in progress. – Info Info (Informational; no action required.)

SYSREF: System reference lock failed

shelf Lock on system reference is lost. – Critical Critical Check system reference.

SYSREF_EVENT: System lost reference lock

shelf System lost reference lock. – Info Info Check for SYSREF alarm.

SYNCFAIL2: Synchronization reference failure

sonet_ptpsdh_ptp

OC-N facility timing. SA Minor Minor Check timing signal quality.

1 Not supported in this release.2 Environmental alarm inputs are customized by each operator. 3 Legacy event for Release 1.1 and below.4 If switch mode is set to Lockout, a failure on the working module may affect service.





SA (Unprotected)

NSA(Protected)

Chapter2


ecomm

ended ActionsA

larms/Events, TA

200

Release O

PS3.1.xTurin N

etworks

Page 1-91

Alarms/Events, TA200

Table 1-11 Alarms, Events and Recommended Actions, TA200




SA (Unprotected)

(Protected)

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.

– Warning Warning Check the remote end for out of frame errors and confirm the correct configuration.

TA200_CLOCK: Clock alarm ta200 The primary timing source is no longer present or has failed.

SA Critical Critical Check the configuration or timing source equipment for hard failure.

TA200_PM13E_G747FESmry: PM13e T3 747 Out of frame

ta200 PM13e T3 is out of frame. – Warning Warning Check the configuration.

TA200_PM13E_G747OOFSmry: PM13e T3 747 Out of frame: PM13e T3 747 FE (Remote Far-End) Failure

ta200 PM13e T3 is out of frame at the remote end.

SA Critical Critical Check the remote end configuration.

Node O



anagement

Alarm

s/Events, TB through TZ

Page 1-92Turin N

etworks

Release OPS3.1.x

Alarms/Events, TB through TZ

Table 1-12 Alarms, Events and Recommended Actions, TB through TZ




SA (Unprotected)

NSA (Protected)

TCA: Threshold crossing alert ds1_ptpds3_ptp(ds_ptp)e3_ptpethernet_ptpsonet_ptpsdh_ptp

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.”

– Info Info Check PM for the integrity of the communications channel.

TEMP: Internal temperature threshold violation


Temperature is too great. – Warning Warning Card overtemp. Check fans and filter.

TEMPCRIT: Temperature critical

shelf A module’s temperature has exceeded 65ºC.

– Minor Minor Check the fan tray for proper functioning. Replace, as necessary.

TEMPWARN: Temperature warning

shelf A module’s temperature has exceeded 59 ºC.

– Minor Minor Check the fan speed change. The alarm should clear once the fan speed changes.

TIM: Trace identifier mismatch ds3_ptp(ds_ptp)e3_ptpsonet_ptpsdh_ptp

The expected path trace string (J1 byte in the path overhead) does not match the received path trace string.



TIM-P: Trace identifier mismatch - Path

e3_ptpsonet_ptpsonet_stste50

The expected path trace string does not match the received path trace string.



Chapter2


ecomm

ended ActionsA

larms/Events, TB through TZ

Release O

PS3.1.xTurin N

etworks

Page 1-93

TIM-S: Trace identifier mismatch - Section

e3_ptpsonet_ptpte50

The expected section trace (J0 byte) string does not match the received section trace string.

SA Critical Minor ■ Check configuration of section source or cross-connect.

■ Match the section trace string at each end.

TIM-V: Trail trace mismatch - VT

ds1_ptpds3_ptp(ds_ptp)e3_ptpshelfsdh_ptpsonet_ptpsonet_vtsonet_stste50

The expected VT trail trace (J2 byte) string does not match the received VT trail trace string.

SA Critical Minor ■ Check configuration of VT trail trace source or cross-connect.

■ Match the VT trail trace string at each end.

TIU-V: Trail trace unstable -VT ds1_ptpds3_ptp(ds_ptp)e3_ptpsdh_ptpsonet_ptpsonet_vtsonet_sts

The expected VT trail trace string match at received VT trail trace string is unstable.

SA Critical Minor ■ Check configuration of VT trail trace source or cross-connect.

■ Match the VT trail trace string at each end.

TIMEDOUT: Session terminated

servershelf

The user session has been idle for two hours.

– Info Info Start a new user session.

TIMEOUTWARN: Session terminate warning

servershelf

The user session has been idle for 1 hour and 55 minutes; the session will terminate in 5 minutes.

– Info Info Perform a user action to stop session termination.

TIU-V: Trail trace mismatch - VT

shelf VT trail trace mismatch. SA Critical Minor Check trace configuration at each end.

Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued)




SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-94Turin N

etworks

Release OPS3.1.x

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

eossdh_eos

Total capacity lost. SA Critical Critical Check the ingress transport link for alarms. Check the paths associated with the EOS members for alarms.

TLCT: Total loss of capacity - transmit

eossdh_eos

Total capacity lost. SA Critical Critical Check the ingress transport link for alarms. Check the paths associated with the EOS members for alarms.

TOOMANYEVENTS1: Too many events in the server

server Server event log too large. – Critical Critical Clear event log.

TOPOMIS2: Topology mismatch

sonet_ptpsdh_ptp

Topology is mismatched. – Minor Minor Check topologies.

TOXIC3: 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

shelf Controller A EXT A reference is out of local oscillator qualification frequency range.

SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin’s Customer Service (TAC).

TSS-EXTA-OOB-B: Controller B EXT A - Out of Band

shelf Controller B EXT A reference is out of local oscillator qualification frequency range.


TSS-EXTB-OOB-A: Controller A EXT B - Out of Band

shelf Controller A EXT B reference is out of local oscillator qualification frequency range.


TSS-EXTB-OOB-B: Controller B EXT B - Out of Band.

shelf Controller B EXT B reference is out of local oscillator qualification frequency range.






SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-95

TSS-FRC: Forced protection switching on timing

shelf A forced protection switch command has been performed on the BITS or line timing source.

– Warning Warning If the reason for executing the forced switch no longer exists, clear the switch command.

TSS-FREERUN-GCMA: GCM is in freerun mode

shelf No timing references found. Defer to freerun mode.

– Warning Warning Check timing references.

TSS-FREERUN-GCMB: GCM is in freerun mode

shelf No timing references found. Defer to freerun mode.

– Warning Warning Check timing references.

TSS-HOLDOVER-GCMA: GCMA in holdover state awaiting a reference

shelf There are no available external references so the GCMA is referencing the local oscillator.


TSS-HOLDOVER-GCMB: GCMB in holdover state awaiting a reference

shelf There are no available external references so the GCMB is referencing the local oscillator.


TSS-LINE1-OOB-GCMA: GCMA Line Ref 1 - Out of Band

shelf GCMA Line Reference 1 is out of local oscillator qualification frequency range.


TSS-LINE1-OOB-GCMB: GCMB Line Ref 1 - Out of Band

shelf GCMB Line Reference 1 is out of local oscillator qualification frequency range.

SA Critical Minor If this alarm persists for more than 5 minutes, contact Turin’s Customer Service (TAC)











SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-96Turin N

etworks

Release OPS3.1.x













TSS-LOCK: Lockout protection switching on timing

shelf A lockout protection switch command has been performed on the BITS or line timing source.

– Warning Warning If the reason for executing the lockout command no longer exists, clear the switch command.

TSS-MAN: Manual protection switching on timing

shelf A manual protection switch command has been performed on the BITS or line timing source.

– Warning Warning If the reason for executing the manual switch no longer exists, clear the switch command.

TSS-REF1-ALM: Primary reference for timing subsystem is alarmed

shelf An LOS, LOF, or AIS-L alarm exists on the BITS or line timing primary reference.


TSS-REF2-ALM: Secondary reference for timing subsystem is alarmed

shelf An LOS, LOF, or AIS-L alarm exists on the BITS or line timing secondary reference.


TSS-REF3-ALM: Third reference for timing subsystem is alarmed

shelf An LOS, LOF, or AIS-L alarm exists on the BITS or line timing third reference.






SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-97

TSS-REF4-ALM: Fourth reference for timing subsystem is alarmed

shelf An LOS, LOF, or AIS-L alarm exists on the BITS or line timing fourth reference.


TSS-REFL-GCMA: All synchronization references are failed or unusable

shelf All BITS or line timing sources are alarmed.

– Major Major Restore primary and secondary timing references.

TSS-REFL-GCMB: All synchronization references are failed or unusable

shelf All BITS or line timing sources are alarmed.

– Major Major Restore primary and secondary timing references.

TSS-REFS2: Reference switched - timing subsystem

shelf Reference has been switched. – Info Info (Informational; no action required.)

TSS-SSM: SSM (synchronization status message) update - timing subsystem)

shelf There has been a change in SSM for BITS or line timing sources.


TSSALM2: Timing reference alarm

shelf Timing reference alarm. – Info Info Check timing reference.

TSSGEN2: Timing subsystem event

shelf Timing subsystem event. – Info Info (Informational; no action required.)

TSSREF: Timing system reference lock failed

shelf Lock on timing system reference is lost.

– Critical Critical Check timing system reference.

TSSREF_EVENT: Timing system lost reference lock

shelf Timing system lost reference lock.

– Info Info Check for TSSREF alarm.

TSSSETS2: SETS status shelf Timing subsystem event. – Info Info (Informational; no action required.)





SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-98Turin N

etworks

Release OPS3.1.x

TU-AIS: Alarm indication signal – Tributary Unit)

sdh_hpsdh-lpsdh_ptp

An upstream failure occurred at the tributary unit path layer.



Verify your tributary unit payload connections.

TU-LOP: Loss of Pointer – Tributary Unit

sdh_hpsdh-lpsdh_ptp

Valid pointer bytes are missing from the tributary unit overhead.

SA Critical Minor Check the cabling and physical connections on the reporting card.




TX-OFF-LI:Transmitter off due to link indication

ethernet_ptp The module is in standby mode. – Info Info Information only.

TX-ON-LI:Transmitter on due to link indication

ethernet_ptp The module is in active mode. – Info Info Information only.

1 Legacy event for Release 1.1 and below.







SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA

larms/Events U through Z

Release O

PS3.1.xTurin N

etworks

Page 1-99

Alarms/Events U through Z

Table 1-13 Alarms, Events and Recommended Actions, U through Z




SA (Unprotected)

NSA (Protected)

UNDERVOLTAGE_A1: Below the minimum voltage value - Enhanced GCM_A

shelf GCM_A has triggered due to an under voltage condition.

The Enhanced GCM triggers the under-voltage alarm at -40.5 VDC. It clears this alarm at -42.5 VDC.


UNDERVOLTAGE_B1: Below the minimum voltage value - Enhanced GCM_B

shelf GCM_B has triggered due to an under voltage condition.

The Enhanced GCM triggers the under-voltage alarm at -40.5 VDC. It clears this alarm at -42.5 VDC.


UNEQ: Rx Path unequipped code received

ethernet_ptp No payload is received on an activated service.

SA Critical Minor Check your interface connection.

Connect your proper payload and service source.UNEQ-P Unequipped code

signal label receivedds3_ptp(ds_ptp)e3_ptpsonet_ptpsonet_stste50

SA Critical Minor

Node O



anagement

Alarm

s/Events U through Z

Page 1-100Turin N

etworks

Release OPS3.1.x

UNEQ-V: Unequipped code signal label received - VT path

ds1_ptpds3_ptp(ds_ptp)shelfsonet_ptpsonet_vtsonet_stste50



Connect your proper payload and service source.

e3_ptpsdh_ptp

See UNEQ-VC. SA Critical Minor See UNEQ-VC.

UNEQ-VC: Unequipped code signal label received - VC path

e1_ptpsdh_ptp



Connect your proper payload and service source.

UP1: In service all objects Unused. – Minor Minor Unused.

VCC: Internal voltage threshold violation


Supply voltage doe not meet guarantee.

– Warning Warning Call Turin’s Customer Support.

VENTFAIL2: Ventilation system failure

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.

– Minor Minor Verify that the module warm reboot request is expected.

WLMIS: Configured wavelength mismatch with hardware

sdh_ptpsonet_ptp

Incorrect provisioning. SA Major Minor Check interface and configuration.

Table 1-13 Alarms, Events and Recommended Actions, U through Z (continued)




SA (Unprotected)

NSA (Protected)

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-101

X86_ABORT shelf Receiving X.86 encapsulation abort condition.

SA Critical Minor Check interface and configuration.

X86_CRC shelf Receiving X.86 encapsulation CRC errors.

SA Critical Minor Check interface and configuration.

XPT-FAIL-RX: Receiver connection failure

ethernet_ptp Link Integrity detected transport failure in the receive direction.

SA Critical Critical Check EOS members for path alarms.

XPT-FAIL-TX: Transmitter connection failure

ethernet_ptp Link Integrity detected transport failure in the transmit direction.


XPTRX: Receive transport failure

lag Link Integrity detected transport failure in the receive direction.


XPTTX: Transmit transport failure

lag Link Integrity detected transport failure in the transmit direction.


1 Not supported in this release.2 Environmental alarm inputs are customized by each operator.

Table 1-13 Alarms, Events and Recommended Actions, U through Z (continued)




SA (Unprotected)

NSA (Protected)

Node O



anagement

Alarm


Page 1-102Turin N

etworks

Release OPS3.1.x

Chapter2


ecomm

ended ActionsA


Release O

PS3.1.xTurin N

etworks

Page 1-103

Node O



anagement

Alarm


Page 1-104Turin N

etworks

Release OPS3.1.x



Chapter 3TransNav 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 1-106■ TransNav GUI Service Error Codes, page 1-107

Figure 1-13 TransNav GUI Service Request Error Window

Node Operations and Maintenance Guide, Section 1: Fault ManagementService 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.

Figure 1-14 Service Request Failure

2 From the Services menu, select Show Last Error.

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 1-107 for further troubleshooting details.

4 The Service Request—Show Last Error procedure is complete.

Service ActivationFailure

Indication

Service Error Code

InformationEntryRequest

Chapter3

TransNav G

UI Service Error C

odesTransN

av GUI Service Error Codes

Release O

PS3.1.xTurin N

etworks

Page 1-107

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.

1007 RSVP (resource reservation protocol) error - MIB SET operation failed

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.)

■ 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.

1008 RSVP (resource reservation protocol) error - MIB GET operation failed


■ Try to deactivate/reactive the new service.■ If deactivation/reactivation does not resolve the problem,


1009 RSVP (resource reservation protocol) error - MIB TEST operation failed


■ Try to deactivate/reactive the new service.■ If deactivation/reactivation does not resolve the problem,


1016 RSVP (resource reservation protocol) error - No path for reservation

Remote node or link failure. Retry service request.

Node O



anagement

TransNav GU

I Service Error Codes

Page 1-108Turin N

etworks

Release OPS3.1.x

1025 RSVP (resource reservation protocol) error - Service preempted

Service of a higher priority has used the requested resources.

Check/set service priority. If possible, set high priority for all services to eliminate preemption.

1034 RSVP (resource reservation protocol) error - Resources not available

Service resources completely used. Most typically, this applies to STS resources.

Use IP address and node name returned in the error message and trace the resource deficiency.

Select another resource and retry the service request.

1035 RSVP (resource reservation protocol) error - System resources not available

Internal system resources completely used. The error is most commonly seen when using the Bulk Activation tool.

■ 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.

1036 RSVP (resource reservation protocol) error - System error, resources not available

Internal system resources completely used. The error is most commonly seen when using the Bulk Activation tool.

■ 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.

1205 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.

1207 Invalid slot in request Unrecognized module was plugged into the slot. (e.g., a module was plugged into a previously configured yet unequipped slot.)

Check the slot configuration.

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 interface specified in the original request. Make a new request with a valid interface.

Table 1-15 Service Error Codes and Recommended Actions (continued)

Service Error Code


Chapter3

TransNav G

UI Service Error C

odesTransN


Release O

PS3.1.xTurin N

etworks

Page 1-109

1209 Invalid Protection interface Unsupported interface identified in the request. For example, an Ethernet I/F in 1+1 protection group request.

Check the interface specified in the original request. Make a new request with a valid interface.

1210 Resources not available ■ Port is locked■ STS is completely used

■ Unlock the port■ Select a different STS with sufficient bandwidth

1215 Error while processing a service request

Module not responding. 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.

1218 Interface already exists The interface is already in use. Make another interface selection and retry the service request.

1219 Slot already exists The slot is already in use. Make another slot selection and retry the service request.

1220 PG (protection group) already exists The protection group is already in use. Make another protection group selection and retry the service request.

1221 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.

1222 Slot exists in a PG (protection group)

The slot is already in use in a protection group. Make another slot selection and retry the service request.

1227 PG (protection group) already used by a service

The protection group is already in use. Make another protection group selection and retry the service request.

1228 Interface already used by a service The interface is already in use in a service. Make another interface selection and retry the service request.

1229 Slot already used by a service The slot is already in use in a service. Make another slot selection and retry the service request.

1230 Error in processing UPSR (unidirectional path switched ring) request

Trying to use an unavailable UPSR protection group. Create the UPSR protection group and retry the service request.


Service Error Code


Node O



anagement

TransNav GU


Page 1-110Turin N

etworks

Release OPS3.1.x

1231 Invalid Direction for service Incorrect Direction type selected for the service. Make a valid Direction selection and retry the service request.

1233 Invalid Encoding Type Incorrect Encoding Type selected for the service. Make a valid Encoding Type selection and retry the service request.

1234 Invalid Protection Group Incorrect Protection Group selected for the service. Make a valid Protection Group selection and retry the service request.

1235 Invalid Ring Type Incorrect Ring Type selected for the service. Make a valid Ring Type selection and retry the service request.

1236 Switch command successful The Switch function completed successfully. No action required.

1237 Switch command denial - equal or higher priority request outstanding

A failed attempt to request a lower priority protection switch while a higher priority protection switch was in progress.

Check the protection group priority.

1238 Invalid Starting STS (synchronous transmission signal) specified

Incorrect STS selected. Make a valid STS selection and retry the service request.

1239 Invalid Bandwidth specified Bandwidth request does not match the option. Check bandwidth, make another selection, and retry the service request.

1241 Interface in PG (protection group) of different type

Selected different interface types. Retry the service request with appropriate interface types.

1242 Invalid service request or invalid re-use of STS

■ Attempted an invalid service request (e.g., mixed uni- and bi-direction request)

■ Invalid slot, port, or STS identified in request

■ Check service■ Check the slot, port, and STS made in the request

1244 Error encountered on PG (protection group) operation on line cards

Failure occurred while creating the protection group. If the problem persists, contactthe Turin Technical Assistance Center.

1246 Requested resource is Admin locked The resource is locked and must be unlocked. Unlock the resource.


Service Error Code


Chapter3

TransNav G

UI Service Error C

odesTransN


Release O

PS3.1.xTurin N

etworks

Page 1-111

1247 No UPSR PG (protection group) created for the requested UPSR service

No UPSR PG was created so cannot be applied. Create UPSR PG and retry the service request.

1254 Invalid span or tributary card given in the transparent service

The span or tributary card cannot be identified. Check your selections.

1258 DCC Tunnel interface is in a transparent ring

The port you’ve selected is in a transparent ring. Make another port selection and retry the service request.

1259 DCC Tunnel STS is in use The STS specified is already in use. Make another selection and retry the service request.

1263 E2E (End to End) service request; forward direction STS already in use

STS is unavailable to complete E2E service request. Check STS. Make another STS selection and retry the service request.

1264 E2E (End to End) service request; forward direction STS already in use

STS is unavailable to complete E2E service request. STS already in use.

Check STS. Make another STS selection and retry the service request.

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



1267 Interface check failed Attempting to set up a service with incorrect constraint settings.

Make correct constraint selections and retry the service request.

1268 Interface type invalid Attempting to set up a service with an incorrect interface type.

Make another interface selection and retry the service request.

1269 Link encoding type invalid Incorrect encoding type selected. Make another encoding type selection and retry the service request.

1270 Link direction invalid Incorrect direction selected. Make another direction selection and retry the service request.


Service Error Code


Node O



anagement

TransNav GU


Page 1-112Turin N

etworks

Release OPS3.1.x

1271 Invalid interface During an end-to-end service, typically strict, a remote module was incorrectly specified or was inadvertently removed.

Check the slot/port of each module interface. If it is correct, then investigate the possibility of a remote module extraction.

1272 Pending IN label unavailable During an end-to-end service, the STS pending resource identifier is not found.

Check the slot/port. If the problem persists, contact the Turin Technical Assistance Center.

1273 Pending OUT label unavailable During an end-to-end service, the STS pending resource identifier is not found.


1274 Used IN label unavailable During an end-to-end service, the STS used resource identifier is not found.


1275 Used OUT label unavailable During an end-to-end service, the STS used resource identifier is not found.


1277 Label word invalid Invalid directional resource request ■ Check uni- and bi-directional settings.■ If the problem persists, contact the Turin Technical

Assistance Center.

1278 Invalid label Invalid user request for STS # = 0 Make another STS # selection and retry the service request.

1280 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.

If the problem persists, contact the Turin Technical Assistance Center.

1284 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.

Check STS number availability across the entire BLSR path.

Make another STS number selection as necessary and retry the service.


Service Error Code


Chapter3

TransNav G

UI Service Error C

odesTransN


Release O

PS3.1.xTurin N

etworks

Page 1-113

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.

1286 Invalid BLSR constraints. System error during the E2E BLSR service request. If the problem persists, contact the Turin Technical Assistance Center.

1289 Switch exercise failed 1+1 linear bidirectional protection group exercise request failed.

Check remote node for (K1/K2 APS) byte failure.

1290 Path protection error Trying to use an unavailable 1+1 Path protection group.

Create the 1+1 Path protection group and retry the service request.

1291 Control channels don’t match for interfaces in the 1+1 PG (protection group)

Control channel down Retry the service request.

1292 DCC bytes for interfaces in a 1+1 PG (protection group) do not match

The DCC configuration termination bytes must match.

Retry the service request with matching DCC configuration termination bytes.

1293 Error modifying path parameter(s) Invalid parameter modification selection. Make appropriate parameter selections.

2820 GCM FM error - destination termination point resource allocation failed

Resource allocation failure during the Ethernet service request. There is not enough bandwidth available on the SONET endpoint to accommodate the new Ethernet service.

■ 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.

3016 Destination termination point admin state is locked

The destination Ethernet port administrative state is set to locked.

Unlock the destination Ethernet port and retry the service request.

3017 Source termination point admin state is locked

The source Ethernet port administrative state is set to locked.

Unlock the source Ethernet port and retry the service request.


Service Error Code


Node O



anagement

TransNav GU


Page 1-114Turin N

etworks

Release OPS3.1.x

3021 LC FM error - flow action failed Too many VLANs have been configured on the Ethernet module. Ethernet modules support up to 243 VLANs.

■ 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.

3204 Previous command issued by MP is still being processed

A second service request was issued before a previous request process had time to complete.

Retry the service request.

3212 Ethernet card requested in service is physically absent

The Ethernet module specified in the service request is not physically present.

Plug in an appropriate Ethernet module and retry the service request.

3220 Invalid Ethernet slot requested in service

Invalid slot identified in request. For example, slot 21 is requested in a 20 slot chassis.

Make another (valid) slot selection and retry the service request.

3221 Invalid Ethernet port requested in service

Invalid port identified in request. For example, port 25 is requested in a 24 port module.

Make another port selection and retry the service request.

3224 Ethernet port requested in service is used by active service with another tagging type

The Ethernet port identified in the service request is being used for another service type. Service types must be compatible.

Deactivate the conflicting service using the Ethernet port and retry the new service request.

3225 Optical facility requested in service is in use

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.

Deactivate the conflicting service using the SONET endpoint and retry the new service request.

3227 Optical facility requested in service is in use for a dedicated p2p (point to point) service

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.


3228 Optical facility requested in service is in use for a Transparent LAN Service

The SONET endpoint is already in use with a Transparent LAN service and is incompatible with the service in the activation request.



Service Error Code


Chapter3

TransNav G

UI Service Error C

odesTransN


Release O

PS3.1.xTurin N

etworks

Page 1-115

3229 VLAN ID requested in service is already being used in the Ethernet module (card)

One or more VLAN IDs specified in the service request are already in use for another service on the Ethernet module.

Deactivate the conflicting service using the VLAN ID and retry the new service request.

3236 Ethernet module (card) requested in service is not yet ready to accept new services

The Ethernet module in the service request has not completed initialization, therefore, is not ready to accept service.

Once the Ethernet board completes initialization, retry the service request.

3240 Ethernet module (card) type is not supported by EA in this release

The Ethernet module type in the service request is not supported in this release.

■ 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.

3242 Termination point specified in service is being used by non-IAS applications

The SONET endpoint is already in use with non-IAS services and is incompatible with the service in the IAS service request.


3243 Termination point specified in IAS service has an invalid participation type

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).


3244 Ethernet port specified in IAS service has subscribers going to a different optical facility

The source Ethernet port identified in the service request is being used by another IAS service with a different destination termination point.

Use the same destination termination point as the previously activated IAS service and retry the service request.


Service Error Code


Node O



anagement

TransNav GU


Page 1-116Turin N

etworks

Release OPS3.1.x

3247 No free traffic contracts are available on the Ethernet module (card) specified in service

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.

Deactivate some service using a traffic contract to free up resources and retry the new service request.

3256 EA is not ready to receive MP requests

■ 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.

Retry the service request as this is a transient condition.

3271 Maximum number of TDM endpoints bound to Ethernet module (card)

SONET endpoint resource allocation failure during service request. All SONET endpoints are already in use.

Each Ethernet module supports (typically) 24 SONET endpoints.


3272 Maximum number of TLS TDM endpoints bound to Ethernet module (card)

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.

Deactivate all services using one of the other TLS SONET endpoints and retry the new service request.

3273 Maximum number of TLS instances on Ethernet module (card)

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.

Deactivate all of the active services using another TLS instance and retry the service request.


Service Error Code


Chapter3

TransNav G

UI Service Error C

odesTransN


Release O

PS3.1.xTurin N

etworks

Page 1-117

3274 VLAN ID is in use by non-TLS service on same Ethernet module (card)

The VLAN ID specified in the service request is already in use by another non-TLS service on the Ethernet module.

■ Deactivate the conflicting service using the VLAN ID and retry the new service request.

■ Make another VLAN ID selection and retry the service request.

3275 VLAN ID is in use by TLS service on another Ethernet module (card)

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.

■ Deactivate the conflicting service using the VLAN ID and retry the new service request.

■ Make another VLAN ID selection and retry the service request.

3276 Optical facility requested in service is in use for a Shared-p2p (point to point) service

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.


3277 Optical facility requested in service is in use for an IAS service

The SONET endpoint is already in use with an internet access service (IAS) and is incompatible with the service in the activation request.


3600 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.

3601 STS resources between the cards are all used up

■ VT Switch module is required but not present in the system.

■ All the resources are already in use.

■ Install a VT Switch module in the system.■ Make a different resource selection with appropriate

bandwidth and retry the service request.

3609 Internal error; cannot create STS cross-connect

A system error occurred during the STS cross-connect process.


3612 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.

3613 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.


Service Error Code


Node O



anagement

TransNav GU


Page 1-118Turin N

etworks

Release OPS3.1.x

3620 Internal error; Error replicating generic cross-connect to standby

A system error occurred during the GCM replication process.


3622 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.

3817 All tunnels on Ethernet module (card) already allocated

Ethernet module cannot support any new SONET endpoints at this time.

Each Ethernet module supports (typically) 24 SONET endpoints.

Deactivate one or more services using another SONET endpoint on this Ethernet module and retry the new service request.

3818 Minimum Best Effort bandwidth requirements unavailable

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.

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.

3820 Ethernet module (card) must be created before adding services

The Ethernet module (card) in the service request does not exist. The module has not been provisioned.

Provision the Ethernet module and retry the service request.

3824 Backplane bandwidth from Ethernet module (card) not available

Resource allocation request failure. SONET termination point resources required are unavailable so the service request cannot complete.

Deactivate one or more services using SONET termination points on the same Ethernet module to free up resources and retry the new service request.

3828 VC Bundle misconfigured The VC Bundle (being used as a SONET termination point) is configured incorrectly. The SONET termination point is unusable.

Check the VC Bundle configuration, correct misconfiguration, and retry the service request.


Service Error Code



SECTION 2 PERFORMANCE MONITORINGSECTION 2SYSTEM MONITORING

SECTION 2

Contents

Chapter 1Managing Performance

Creating or Modifying a PM Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Assigning a PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Assigning a Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Assigning an EOS Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Assigning a Subport PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Assigning a Service PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Assigning a TransAccess 100 Mux PM Template. . . . . . . . . . . . . . . . . . . . . . 2-8Viewing PM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

PM Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Viewing Port or Subport PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Viewing Service Path PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Viewing Signal Path Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Generating a PM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Chapter 2SONET Performance Parameters

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17DS1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18DS3 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21EC-1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Small Form-Factor Pluggable Optical Port PM . . . . . . . . . . . . . . . . . . . . . . . . 2-26SONET Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27SONET STS Path Layer PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31SONET VT Path Layer PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Chapter 3SDH Performance Parameters

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35E1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36E3 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39SDH High and Low Order Path PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41SDH Port PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45SDH VC-11 and VC-12 Path PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

Chapter 4Ethernet Performance Parameters

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55EOS Port PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55Ethernet Equipment PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

Node Operations and Maintenance Guide, Section 2 Performance Monitoring


Ethernet Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59Ethernet Service Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62

List of FiguresFigure 2-1 Performance Templates Dialog Box . . . . . . . . . . . . . . . . . . . . . . . 2-2Figure 2-2 DS1 PM Configuration Template Dialog Box . . . . . . . . . . . . . . . . 2-4Figure 2-3 Synchronize Template Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 2-4Figure 2-4 Service PM Template Parameters. . . . . . . . . . . . . . . . . . . . . . . . . 2-7Figure 2-5 TransAccess 100 Mux Config Tab . . . . . . . . . . . . . . . . . . . . . . . . 2-8Figure 2-6 Object Selection for PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Figure 2-7 Port Performance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Figure 2-8 Path Display for Services Screen . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Figure 2-9 Service Performance (PM) Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Figure 2-10 Path Display for Service Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Figure 2-11 Path Overhead Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Figure 2-12 Event Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Figure 2-13 Reports Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

List of TablesTable 2-1 Creating or Modifying a PM Template . . . . . . . . . . . . . . . . . . . . . . 2-2Table 2-2 Assigning a Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Table 2-3 Assigning an EOS Port PM Template . . . . . . . . . . . . . . . . . . . . . . 2-5Table 2-4 Assigning a Subport PM Template . . . . . . . . . . . . . . . . . . . . . . . . 2-6Table 2-5 Assigning a Service PM Template. . . . . . . . . . . . . . . . . . . . . . . . . 2-6Table 2-6 Assigning a TransAccess 100 Mux PM Template . . . . . . . . . . . . . 2-8Table 2-7 Viewing Port or Subport PM Data . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Table 2-8 Viewing Service PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Table 2-9 Viewing Signal Path Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Table 2-10 PM Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Table 2-11 DS1 Port PM Parameters—Near End . . . . . . . . . . . . . . . . . . . . . . 2-18Table 2-12 DS1 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . 2-19Table 2-13 DS3 Port PM Parameters—Near End . . . . . . . . . . . . . . . . . . . . . . 2-21Table 2-14 DS3 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . 2-23Table 2-15 EC1 Port PM Parameters—Near-End . . . . . . . . . . . . . . . . . . . . . . 2-24Table 2-16 EC1 Port PM Parameters—Far-End . . . . . . . . . . . . . . . . . . . . . . . 2-25Table 2-17 SFP Optical Port PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Table 2-18 SONET Port PM—Near End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Table 2-19 SONET Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . 2-29Table 2-20 SONET STS Path PM Parameters—Near End. . . . . . . . . . . . . . . 2-31Table 2-21 SONET STS Path PM Parameters—Far End . . . . . . . . . . . . . . . . 2-32Table 2-22 SONET VT Path PM Parameters—Near End. . . . . . . . . . . . . . . . 2-33Table 2-23 SONET VT Path PM Parameters—Far End . . . . . . . . . . . . . . . . . 2-34Table 2-24 E1 Port PM Parameters—Near End . . . . . . . . . . . . . . . . . . . . . . . 2-36


Release OPS3.1.x Turin Networks Page ix

Table 2-25 E1 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . . 2-38Table 2-26 E3 Port PM Parameters–Near End . . . . . . . . . . . . . . . . . . . . . . . . 2-39Table 2-27 E3 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . . 2-40Table 2-28 Number of Errored Blocks that Constitute an SES . . . . . . . . . . . . 2-41Table 2-29 SDH High Order VC Path and

Low Order VC3 PM Parameters—Near End. . . . . . . . . . . . . . . . . 2-42Table 2-30 SDH High Order VC Path and

Low Order VC3 PM Parameters—Far End . . . . . . . . . . . . . . . . . . 2-44Table 2-31 SDH Port PM—Near End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45Table 2-32 SDH Port PM—Far End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48Table 2-33 Number of Errored Blocks that Constitute an SES . . . . . . . . . . . . 2-50Table 2-34 SDH VC-11 and VC-12 Path PM Parameters—Near End . . . . . . 2-50Table 2-35 SDH VC-11 and VC-12 Path PM Parameters—Far End . . . . . . . 2-52Table 2-36 EOS Port PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56Table 2-37 Ethernet Equipment PM Parameters . . . . . . . . . . . . . . . . . . . . . . 2-57Table 2-38 Ethernet Port PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59Table 2-39 Ethernet Service Port PM Parameters . . . . . . . . . . . . . . . . . . . . . 2-62


Page x Turin Networks Release OPS3.1.x


SECTION 2PERFORMANCE MONITORING

Chapter 1Managing Performance

Introduction 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 a PM Template

Creating or modifying performance monitoring templates gives the user configuration flexibility for threshold default settings and report generation parameter collection.

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.

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.

Node Operations and Maintenance Guide, Section 2: Performance MonitoringCreating 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

Chapter 1 Managing PerformanceCreating or Modifying a PM Template


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.

Table 2-1 Creating or Modifying a PM Template (continued)

Step Procedure

Node Operations and Maintenance Guide, Section 2: Performance MonitoringCreating or Modifying a PM Template


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.

Table 2-1 Creating or Modifying a PM Template (continued)

Step Procedure

Chapter 1 Managing PerformanceAssigning an EOS Port PM Template


Assigning a 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

Assigning a Port PM Template

The following procedure describes how to assign a port PM template to a port.

Assigning an EOS Port PM Template

The following procedure describes how to assign an EOS port PM template to an EOS port.

Table 2-2 Assigning a Port PM Template

Step Procedure

1 In Shelf View, click a module port.


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.

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.

Node Operations and Maintenance Guide, Section 2: Performance MonitoringAssigning 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.

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-4 Assigning a Subport PM Template

Step Procedure

1 In Shelf View, select a DS3 Transmux module port.


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.

Table 2-5 Assigning a Service PM Template

Step Procedure


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.

Chapter 1 Managing PerformanceAssigning a Service PM Template


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.

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.

Table 2-5 Assigning a Service PM Template (continued)

Step Procedure

3

4

Node Operations and Maintenance Guide, Section 2: Performance MonitoringAssigning 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.

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 2-11.

Table 2-6 Assigning a TransAccess 100 Mux PM Template

Step Procedure

1 In Shelf View, select a TransAccess 100 Mux icon.

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.

2

3

4

1

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.

Chapter 1 Managing PerformanceViewing 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.

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.

1b

1a

Node Operations and Maintenance Guide, Section 2: Performance MonitoringViewing Port or Subport PM Data


3 Click Refresh to re-display updated PM values.

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.

Table 2-7 Viewing Port or Subport PM Data (continued)

Step Procedure

2a 2b 3 4 5 6

Chapter 1 Managing PerformanceViewing 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.


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.

4a

3

2

4b

5

Node Operations and Maintenance Guide, Section 2: Performance MonitoringViewing Service Path PM Data


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.

Figure 2-9 Service Performance (PM) Tab


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.

Table 2-8 Viewing Service PM Data (continued)

Step Procedure

6a

6b 7 8 9 10

Chapter 1 Managing PerformanceViewing 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.

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).

4a

3

2

4b

5

Node Operations and Maintenance Guide, Section 2: Performance MonitoringViewing Signal Path Trace Data


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


8 Click Done to return to the previous screen.

9 The Viewing Service PM Data procedure is complete.

Table 2-9 Viewing Signal Path Trace Data (continued)

Step Procedure

Chapter 1 Managing PerformanceReport 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

Node Operations and Maintenance Guide, Section 2: Performance MonitoringGenerating 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.

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.

3,4

2

3

5



Chapter 2SONET 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


Node Operations and Maintenance Guide, Section 2: Performance MonitoringDS1 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)

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.

1–16383

Default: 13340

1–1048575

Default: 133400

NE ES_L (Errored Seconds)

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.

1–900

Default: 65

1–65535

Default: 648

NE SES_L (Severely Errored Seconds)

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.

1–63

Default: 10

1–4095

Default: 100

NE LOSS_L (Loss of Signal Seconds

Count of one or more 1-second intervals containing LOS defects.

1–63

Default: 10

1–4095

Default: 100

Path—Near End

NE CV_P (Code Violations)

Count of frame synchronization bit errors in the SF format or a count of CRC-6 errors in the ESF format.

1–16383

Default: 13296

1–1048575

Default: 132960

NE ES_P (Errored Seconds)

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)

1–900

Default: 65

1–65535

Default: 648

NE SES_P (Severely Errored Seconds)

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)

1–63

Default: 10

1–4095

Default: 100

NE AISS_P (Alarm Indication Signal Seconds)

Count of 1-second intervals containing one or more AIS defects

1–63

Default: 10

1–4095

Default: 100

Chapter 2 SONET Performance ParametersDS1 Port PM


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.

1–63

Default: 2

1–4095

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.

1–63

Default: 10

1–4095

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.

1–72

Default: 4

1–4094

Default: 40

Table 2-12 DS1 Port PM Parameters—Far End


Daily Threshold

Line—Far End

FE ES_L (Errored Seconds)


Path—Far End

FE CV_P (Code Violations)


FE ES_P (Errored Seconds–Path)


1–900

Default: 65

1–65535

Default: 648

Table 2-11 DS1 Port PM Parameters—Near End (continued)


Daily Threshold



FE SES_P (Severely Errored Seconds–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)

1–63

Default: 10

1–4095

Default: 100

FE SEFS_P (Severely Errored Framing Seconds–Path)


FE CSS_P (Controlled Slip Seconds–Path)


FE UAS_P (Unavailable Seconds–Path)


1–63

Default: 10

1–4095

Default: 100

FE FC_P (Failure Count–Path)

Count of far-end path failure (RAI) events. 1–63

Default: 10

1–4095

Table 2-12 DS1 Port PM Parameters—Far End (continued)


Daily Threshold



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


Daily Threshold

Line—Near End

CV-L (Code Violations)

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.

1–16383

Default: 382

1–1048575

Default: 3865

ES-L (Errored Seconds)


1–900

Default: 25

1–65535

Default: 250

SES-L (Severely Errored Seconds)

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.

1–63

Default: 4

1–4095

Default: 40

Path PBit—Near End

CV-P (Code Violations)

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.

1–16383

Default: 382

1–1048575

Default: 3820

ES-P (Errored Seconds

Count of seconds containing one or more P-bit parity errors, one or more SEF defects, or one or more LOS defects.

1–900

Default: 25

1–65535

Default: 250

SES-P (Severely Errored Seconds)

Count of seconds containing more than 44 P-bit parity violations, one or more SEF defects, or one or more LOS defects.

1–63

Default: 4

1–4095

Default: 40

UAS-P (Unavailable Seconds)

Count of 1-second intervals during which the DS3 path is unavailable.

1–63

Default: 10

1–4095

Default: 10



FC-P (Failure Counts)

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.

1–63

Default: 4

1–4095

Default: 40

Path CBit—Near End

CVC-P (Code Violations)

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.

1–16383

Default: 382

1–1048575

Default: 3820

ESC-P (Errored Seconds)

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.

1–900

Default: 25

1–65535

Default: 250

SESC-P (Severely Errored Seconds)

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.

1–63

Default: 4

1–4095

Default: 40

UASC-P (Unavailable Seconds–C-bit parity application)


1–63

Default: 10

1–4095

Default: 10

Table 2-13 DS3 Port PM Parameters—Near End (continued)


Daily Threshold



Table 2-14 DS3 Port PM Parameters—Far End


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 1.

1–16383

Default: 382

1–1048575

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.

1–900

Default: 25

1–65535

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.

1–63

Default: 4

1–4095

Default: 40

FE UASC-P (Unavailable Seconds


1–63

Default: 10

1–4095

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.

1–63

Default: 4

1–4095

Default: 40

Node Operations and Maintenance Guide, Section 2: Performance MonitoringEC-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


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.

1–16383

Default: 387

1–1048575

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.

1–900

Default: 25

1–65535

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.

1–63

Default: 4

1–4095

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.

1–63

Default: 4

1–4095

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.

1–63

Default: 4

1–4095

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.

1–16383

Default: 382

1–1048575

Default: 3820

Chapter 2 SONET Performance ParametersEC-1 Port PM


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

1–900

Default: 25

1–65535

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.

1–900

Default: 4

1–65535

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.

1–900

Default: 2

1–65535

Default: 8

Table 2-15 EC1 Port PM Parameters—Near-End (continued)


Daily Threshold

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.

1–16383

Default: 387

1–1048575

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.

1–900

Default: 25

1–65535

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.

1–63

Default: 4

1–4095

Default: 40

Node Operations and Maintenance Guide, Section 2: Performance MonitoringSmall Form-Factor Pluggable Optical Port PM


Small Form-Factor Pluggable Optical Port PM

The Traverse system provides the following performance (diagnostic) monitoring

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.

1–63

Default: 4

1–4095

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.

1–63

Default: 4

1–4095

Default: 40

Table 2-16 EC1 Port PM Parameters—Far-End (continued)


Table 2-17 SFP Optical Port PM Parameters

Parameter Definition

Measured Temperature A measure of the internal transceiver temperature yielding a value within the total range of -128 to +128 celsius.

Measured Supply Voltage A measure of the internal transceiver supply voltage yielding a value within the total range of 0 to +6.55 volts.

Measured TX Bias Current A measure of the TX bias current yielding a value within the total range of 0 to 131 mA.

Measured TX Output Power 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 6.5535 mW.

Measured TX Input Power A measure of the TX input power yielding a value within the total range of 0 to 6.5535 mW (~ -40 to +8.2 dBm). Absolute accuracy is dependent upon the exact optical wavelength.

Chapter 2 SONET Performance ParametersSONET 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


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.

1–16383

Default: 382

1–1048575

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.

1–900

Default: 25

1–65535

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 OC12■ 2459 for OC48■ 8854 for OC192

1–900

Default: 4

1–65535

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.

1–900

Default: 2

1–65535

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.

1–16383

Default: 1146

1–1048575

Default: 11460

Node Operations and Maintenance Guide, Section 2: Performance MonitoringSONET Port PM


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.

1–900

Default: 25

1–65535

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 OC12■ 2459 for OC48■ 8854 for OC192

1–900

Default: 4

1–65535

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.

1–900

Default: 4

1–65535

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.

1–72

Default: 4

1–4094

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.

1–63

Default: 2

1–255

Default: 10

Table 2-18 SONET Port PM—Near End (continued)


Chapter 2 SONET Performance ParametersSONET Port PM


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).

1–900

Default: 4

1–65535

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.

1–63

Default: 2

1–255

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).

1–900

Default: 4

1–65535

Default: 40

Table 2-18 SONET Port PM—Near End (continued)


Table 2-19 SONET Port PM Parameters—Far End


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.

1–16383

Default: 1146

1–1048575

Default: 11460

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.

1–900

Default: 25

1–65535

Default: 250

Node Operations and Maintenance Guide, Section 2: Performance MonitoringSONET Port PM


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 OC12■ 2459 for OC48■ 8854 for OC-192

1–900

Default: 4

1–65535

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.

1–900

Default: 4

1–65535

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.

1–72

Default: 4

1–4094

Default: 40

Table 2-19 SONET Port PM Parameters—Far End (continued)


Daily Threshold

Chapter 2 SONET Performance ParametersSONET 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


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.

1–16383

Default: 1146

1–1048575

Default: 11460

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.

1–900

Default: 25

1–65535

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.

1–900

Default: 4

1–65535

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.

1–900

Default: 4

1–65535

Default: 40

Node Operations and Maintenance Guide, Section 2: Performance MonitoringSONET STS Path Layer PM


Table 2-21 SONET STS Path PM Parameters—Far End


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.

1–16383

Default: 1146

1–1048575

Default: 11460

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.

1–900

Default: 25

1–65535

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.

1–900

Default: 4

1–65535

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.

1–900

Default: 4

1–65535

Default: 40

Chapter 2 SONET Performance ParametersSONET 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


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.

1–16383

Default: 156

1–1048575

Default: 14976

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 6.2.1.8.2), an LOP–V defect or, if the VT PTE monitoring the path supports ERDI–V for that path, an UNEQ–V defect was present.

1–900

Default: 65

1–65535

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 6.2.1.8.2), an LOP–V defect or, if the VT PTE monitoring the path supports ERDI–V for that path, an UNEQ–V defect was present.

1–900

Default: 10

1–65535

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.

1–900

Default: 10

1–65535

Default: 100

Node Operations and Maintenance Guide, Section 2: Performance MonitoringSONET VT Path Layer PM


Table 2-23 SONET VT Path PM Parameters—Far End


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.

1–16383

Default: 156

1–1048575

Default: 14796

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 6.2.1.3.3) an ERDI–V Server or Connectivity defect was present.

1–900

Default: 65

1–65535

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.

1–900

Default: 10

1–65535

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.

1–900

Default: 10

1–65535

Default: 100



Chapter 3SDH 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


Node Operations and Maintenance Guide, Section 2: Performance MonitoringE1 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


Daily Threshold

Line–Near End

NE FC_L (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.

1–72

Default: 4

1–4094

Default: 40


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.

1–16383

Default: 13340

1–1048575

Default: 133400



1–900

Default: 65

1–65535

Default: 648


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.

1–63

Default: 10

1–4095

Default: 100

NE LOSS_L (Loss of Signal Seconds

Count of one or more 1-second intervals containing LOS defects.

1–63

Default: 10

1–4095

Default: 100

NE FAS_L (Frame Alignment Signal)

Count of one or more 1-second intervals containing FAS defects.

1–63Default: 2

1–4095Default: 17

Path—Near End

NE EB_P (Errored Blocks)

Count of the number of blocks containing one or more bit errors.

1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

Chapter 3 SDH Performance ParametersE1 Port PM




1–900

Default: 65

1–65535

Default: 648


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).

1–63

Default: 10

1–4095

Default: 100

NE AISS_P (Alarm Indication Signal Seconds)

Count of 1-second intervals containing one or more AIS defects

1–63

Default: 10

1–4095

Default: 100



1–63

Default: 10

1–4095

Default: 100

NE BBE_P (Background Block Error)

An errored block not occurring as part of an SES. 1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

NE ESR_P (Errored Seconds Ratio)

The ratio of ES to total seconds in available time during a fixed measurement interval.

1–65535

Default: 4

1–65535

Default: 10

NE SESR_P (Severely Errored Seconds Ratio)

The ratio of SES to total seconds in available time during a fixed measurement interval.

1–65535

Default: 4

1–65535

Default: 10

NE BBER_P (Background Block Error Ratio)

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.

1–65535

Default: 4

1–65535

Default: 10

Table 2-24 E1 Port PM Parameters—Near End (continued)


Daily Threshold



Table 2-25 E1 Port PM Parameters—Far End


Daily Threshold

Line—Far End

FE ES_L (Errored Seconds)


1–900

Default: 65

1–65535

Default: 648

Path—Far End

FE ES_P (Errored Seconds)


1–900

Default: 65

1–65535

Default: 648

FE SES_P (Severely Errored Seconds)

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).

1–63

Default: 10

1–4095

Default: 100

FE UAS_P (Unavailable Seconds)


1–63

Default: 10

1–4095

Default: 100

FE EB_P (Errored Blocks)

Count of the number of blocks containing one or more bit errors.

1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

FE FC_P (Failure Count)

Count of far-end path failure (RAI) events. 1–63

Default: 10

1–4095

FE BBE_P (Background Block Error)

An errored block not occurring as part of an SES.

1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

Chapter 3 SDH Performance ParametersE3 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


Line—Near End


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.

Default: 13340 Default: 133400





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.


Path

NE EB_P (Errored Blocks)

Count of the number of blocks containing one or more bit errors. Default:13296 Default: 132960

NE BBE_P (Background Block Error)

An errored block not occurring as part of an SES. Default:13296 Default: 132960



1–900

Default: 25

1–65535

Default: 250



1–63

Default: 4

1–4095

Default: 40



1–63

Default: 10

1–4095

Default: 10

NE ESR_P (Errored Seconds Ratio)

The ratio of ES to total seconds in available time during a fixed measurement interval. Default: 4 Default: 10



NE SESR_P (Severely Errored Seconds Ratio)

The ratio of SES to total seconds in available time during a fixed measurement interval. Default: 4 Default: 10

NE BBER_P (Background Block Error Ratio)

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.


NE FC_P (Failure Counts)

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.

1–63

Default: 4

1–4095

Default: 40

Table 2-26 E3 Port PM Parameters–Near End (continued)


Table 2-27 E3 Port PM Parameters—Far End


Path—Far End

FE EB_P (Errored Blocks)

Count of the number of blocks containing one or more bit errors. Default:13296 Default: 132960

FE ES_P (Errored Seconds)


1–900

Default: 25

1–65535

Default: 250

FE SES_P (Severely Errored Seconds)


1–63

Default: 4

1–4095

Default: 40

Chapter 3 SDH Performance ParametersSDH High and Low Order Path PM


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.

FE UAS_P (Unavailable Seconds


1–63

Default: 10

1–4095

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.


Table 2-27 E3 Port PM Parameters—Far End (continued)


Table 2-28 Number of Errored Blocks that Constitute an SES

VC type Bits/Block Blocks/Second Threshold of EBs for SES

VC-3 6120 8000 2400

VC-4 18,792 8000 2400

VC-4-4c 75,168 8000 2400

VC-4-16c 300,672 8000 2400

Node Operations and Maintenance Guide, Section 2: Performance MonitoringSDH 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 andLow Order VC3 PM Parameters—Near End


EB-HPEB-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,000

1–691,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.

1–900

Default: 25

1–86,400

Default: 250

SES-HPSES-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.

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.

1–900

Default: 4

1–86,400

Default: 40

UAS-HP UAS-LP

(Unavailable Seconds)


1–900

Default: 4

1–86,400

Default: 40

BBE-HPBBE-LP

(Background Block Error)

Count of errored blocks not occurring as part of Severely Errored Seconds.

1–7,200,000

Default: 20,000

1–691,200,000

Default: 200,000

Chapter 3 SDH Performance ParametersSDH High and Low Order Path PM


FC-HP FC-LP

(Failure Counts)


1–900

Default: 2

1–225

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: 60

1–16,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: 60

1–16,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: 60

1–16,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: 60

1–16,777,215

Default: 6000

Table 2-29 SDH High Order VC Path andLow Order VC3 PM Parameters—Near End (continued)


Node Operations and Maintenance Guide, Section 2: Performance MonitoringSDH High and Low Order Path PM


Table 2-30 SDH High Order VC Path andLow Order VC3 PM Parameters—Far End


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.

1–7200000

Default: 20,000

1–691200000

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.

1–900

Default: 20

1–65535

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.

1–900

Default: 3

1–65535

Default: 10

FE UAS-HPFE 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.

1–900

Default: 3

1–65535

Default: 10

FE BBE-HPFE BBE-LP


Count of errored blocks at the far end not occurring as part of Severely Errored Seconds.

1–7200000

Default: 36,000

1–691200000

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.

1–900

Default: 2

1–225

Default: 10

Chapter 3 SDH Performance ParametersSDH 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


Regenerator Section—Near End

EB-RS (Errored Block)

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.

1–7200000

Default: 10,000

1–691200000

Default: 100,000

Recommended defaults for rates other than STM-1:

STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000

ES-RS (Errored Seconds)

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.

1–900

Default: 25

1–65535

Default: 250

SES-RS (Severely Errored Seconds)

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 STM4■ 2459 for STM16■ 8854 for STM64

1–900

Default: 4

1–86,400

Default: 40

BBE-RS (Background Block Error)

Count of error block not occurring as part of Severely Errored Seconds.

1–7200000

Default: 10,000

1–691200000

Default: 100,000


STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000

Node Operations and Maintenance Guide, Section 2: Performance MonitoringSDH Port PM


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.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

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.

1–900

Default: 25

1–86,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 STM4■ 2459 for STM16■ 8854 for STM64

1–900

Default: 4

1–86,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.

1–900

Default: 4

1–65535

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.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

Default: 288,000

Table 2-31 SDH Port PM—Near End (continued)




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.

1–72

Default: 4

1–4094

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.

1–63

Default: 2

1–255

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).

1–900

Default: 300

1–86,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.

1–63

Default: 2

1–255

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).

1–900

Default: 300

1–86,400

Default: 600

Table 2-31 SDH Port PM—Near End (continued)


Node Operations and Maintenance Guide, Section 2: Performance MonitoringSDH Port PM


Table 2-32 SDH Port PM—Far End


Multiplex Section—Far End

FE 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.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

Default: 288,000


STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000

FE 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.

1–900

Default: 25

1–86,400

Default: 250

FE SES-MS (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 STM1■ 615 for STM4■ 2459 for STM16■ 8854 for STM64

1–900

Default: 4

1–86,400

Default: 40

FE 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.

1–900

Default: 4

1–65535

Default: 40



FE BBE-MS (Error Blocks)

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.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

Default: 288,000


STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000

FE FC-MS (Failure Counts)

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.

1–72

Default: 4

1–4094

Default: 40

Table 2-32 SDH Port PM—Far End (continued)


Node Operations and Maintenance Guide, Section 2: Performance MonitoringSDH 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.

The following table lists the supported performance monitoring parameters for SDH paths.

Table 2-33 Number of Errored Blocks that Constitute an SES

VC type Bits/Block Blocks/Second Threshold of EBs for SES

VC-11 832 2000 600

VC-12 1120 2000 600

Table 2-34 SDH VC-11 and VC-12 Path PM Parameters—Near End


BBE-LP (Background Block Error)

Count of errored blocks not occurring as part of Severely Errored Seconds.

1–1.8 x 106

Default: 5,000

1–1.8x108

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.

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).

1–1.8 x 106

Default: 5,000

1–1.8x108

Default: 50,000

ES-LP (Errored Seconds)

Count of 1-second period with at least one errored block or one defect.

1–900

Default: 25

1–65,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.

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.

1–900

Default: 4

1–65,535

Default: 40

Chapter 3 SDH Performance ParametersSDH VC-11 and VC-12 Path PM


UAS-LP (Unavailable Seconds)


1–900

Default: 4

1–65,535

Default: 40

FC-LP (Failure Counts)


1–72

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: 30

1–2,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: 30

1–2,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: 30

1–2,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: 30

1–2,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.

1–900

Default: 9

1–65,535

Default: 90

Table 2-34 SDH VC-11 and VC-12 Path PM Parameters—Near End (continued)




PJCS-GEN-LP (Pointer Justifications Seconds Generated)

Count of seconds containing one or more PPJC-GEN or NPJC-GEN.

1–900

Default: 9

1–65,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: 10

1–2,097,151

Default: 100

Table 2-34 SDH VC-11 and VC-12 Path PM Parameters—Near End (continued)


Table 2-35 SDH VC-11 and VC-12 Path PM Parameters—Far End


FE BBE-LP


Count of errored blocks at the far end not occurring as part of Severely Errored Seconds.

1–1.8 x 106

Default: 5,000

1–1.8x108

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.

1–1.8 x 106

Default: 5,000

1–1.8x108

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.

1–900

Default: 25

1–65,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.

1–900

Default: 4

1–65,535

Default: 40

Chapter 3 SDH Performance ParametersSDH VC-11 and VC-12 Path PM


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.

1–900

Default: 4

1–65,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.

1–72

Default: 2

1–4,095

Default: 10

Table 2-35 SDH VC-11 and VC-12 Path PM Parameters—Far End (continued)






Chapter 4Ethernet Performance Parameters

Introduction 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


EOS Port PM 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.

Node Operations and Maintenance Guide, Section 2: Performance MonitoringEOS 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)

Definition

TX UNICAST(TE-100 Ethernet only)

The number of unicast frames transmitted with no errors.

TX MULTICAST(TE-100 Ethernet only)

The number of multicast frames that are not broadcast, transmitted with no errors.

TX BROADCAST(TE-100 Ethernet only)

The number of broadcast frames transmitted with no errors.

TX FRAMES1 The number of frames transmitted (unicast, multicast, and broadcast) with no errors.

TX BYTES2,3 The number of bytes transmitted in good frames.

TX DISCARDS(Traverse NGE only)

The number of outbound frames received by this port which were discarded.

RX UNICAST(TE-100 Ethernet only)

The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors.

RX MULTICAST(TE-100 Ethernet only)

The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors.

RX BROADCAST(TE-100 Ethernet only)

The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors.

RX FRAMES1 The number of frames received (unicast, multicast, and broadcast) with no errors.

RX BYTES23 The number of bytes received in good frames.

RX DISCARDS(Traverse NGE only)

The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol.

GFP FCS DISCARDS4

(Traverse NGE only)The number of GFP frames discarded due to frame checksum (FCS) errors.

GFP CHEC DISCARDS The number of GFP frames discarded due to uncorrectable core header (cHEC) checksum errors.

GFP PHEC DISCARDS(Traverse NGE only)

The number of GFP frames discarded due to due to uncorrectable “payload header” (extension or type header) checksum (eHEC, tHEC) errors.

GFP FCS OR PHEC DISCARDS(TE-100 Ethernet only)

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.

Chapter 4 Ethernet Performance ParametersEthernet Equipment PM


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.

RX MTU DISCARDS(TE-100 Ethernet only)

The number of frames discarded by this interface due to an excessive size.

GFP HEC CORRECTIONS 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.

Table 2-36 EOS Port PM Parameters (continued)


Definition

Table 2-37 Ethernet Equipment PM Parameters


Definition Counter type

LAN SPI3 RX FIFO OVERRUNS

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.

Event

LAN SPI3 TX CRC ERRORS Count of SPI-3 CRC error events in the Gardenia to LAN direction.


Event

LAN SPI3 TX PROTOCOL ERRORS

Count of protocol error events in the Gardenia to LAN direction. Protocol events include SPI-3 CRC errors, protocol violations or parity errors.


Event

Node Operations and Maintenance Guide, Section 2: Performance MonitoringEthernet Equipment PM


LAN TX OVERSIZE CNT 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.

Frame

GARDENIA FLT DISCARDS 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.

Errored seconds

GARDENIA BUFFER ABORTS

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.

Errored seconds

GARDENIA SPI3 RX PROTOCOL ERRORS

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.

Errored seconds

WAN RX FIFO OVERRUNS 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.


Event

WAN ENCAP UNDERRUNS Underrun events on SPI-3 bus in Gardenia to WAN direction.


Event

WAN TX ABORTS Frames discarded due to unspecified errors in Gardenia to WAN direction.

Frame

Table 2-37 Ethernet Equipment PM Parameters (continued)


Definition Counter type

Chapter 4 Ethernet Performance ParametersEthernet 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


Definition

TX UNICAST1 The number of unicast frames transmitted with no errors.

TX MULTICAST1 The number of multicast frames that are not broadcast, transmitted with no errors.

TX BROADCAST The number of broadcast frames transmitted with no errors.

TX FRAMES1 The number of frames transmitted (unicast, multicast, and broadcast) with no errors.

TX PKT 64(Traverse Legacy Ethernet only)

The number of transmitted 64-byte frames, including bad frames.

TX PKT 65-127(Traverse Legacy Ethernet only)

The number of transmitted frames, 65 to 127 bytes in length, including bad frames.









TX PKT > 1518(Traverse Legacy Ethernet only)

The number of transmitted frames, greater than or equal to 1519 bytes in length, including bad frames.

RX UNICAST1 The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors.

Node Operations and Maintenance Guide, Section 2: Performance MonitoringEthernet Port PM


RX MULTICAST1 The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors.

RX BROADCAST The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors.

RX FRAMES1 The number of frames received (unicast, multicast, and broadcast) with no errors.

RX > MAX FRAME SIZE The number of received frames that exceed the maximum valid packet length for the port.

RX < 64 The number of frames received, less than 64 bytes in length, received with no errors.

RX PKT 64(Not applicable to Traverse NGE)

The number of received 64-byte frames, including bad frames.

RX PKT 65-127(Not applicable to Traverse NGE)

The number of received frames, 65 to 127 bytes in length, including bad frames.









RX PKT > 1518(Not applicable to Traverse NGE)

The number of received frames, greater than or equal to 1519 bytes in length, including bad frames.

RX NO DELIMITER(Traverse Legacy Ethernet only)

The number of frames received without start of frame delimiter detection but with carrier assertion.

RX DISCARDS2,3,4 The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol.

TX DISCARDS(Traverse NGE only)

The number of outbound frames discarded by this port due to aborted frames and underruns.

RX DELAY DISCARDS(TE-100 Ethernet only)

Number of frames discarded by this interface due to excessive transit delay through the bridge.

RX MTU DISCARDS(Not applicable to TE-100 Ethernet)

Number of frames discarded by this interface due to an excessive size.

Table 2-38 Ethernet Port PM Parameters (continued)


Definition

Chapter 4 Ethernet Performance ParametersEthernet Port PM


RX ALIGNMENT ERR(Traverse Legacy Ethernet only)

Number of frames received which are not an integral number of octets and do not pass the FCS check.

RX FCS ERR5 Number of frames received which are an integral number of octets and do not pass the FCS check.

RX PAUSE The number of received pause control frames.

TX PAUSE The number of transmitted pause control frames.

TX BYTES6 The number of bytes transmitted in good frames.

TX BYTES BAD(Traverse Legacy Ethernet only)

The number of bytes transmitted in bad frames.

RX BYTES2 The number of bytes received in good frames.

RX BYTES BAD(Traverse Legacy Ethernet only)

The number of bytes received in bad frames.

TX SINGLE COLL(10/100BaseTX only)

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.

TX MULTIPLE COLL(10/100BaseTX 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.

TX DEFERRED FRAMES(10/100BaseTX 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.

TX LATE COLL(10/100BaseTX 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.

TX EXCESSIVE COLL(10/100BaseTX 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.

Table 2-38 Ethernet Port PM Parameters (continued)


Definition

Node Operations and Maintenance Guide, Section 2: Performance MonitoringEthernet Service Port PM


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.

5 TE-100 Ethernet includes align errors as well.

6 Traverse NGE includes PAUSE frames.

Table 2-39 Ethernet Service Port PM Parameters


Definition

TX BYTES The number of bytes contained in packets queued for transmitted to this port for this service, including internal overhead per packet.

TX PACKETS The number of packets queued for transmission to this port for this service.

TX RED DISCARDS 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).

RX BYTES2 The number of bytes received on this port for this service, including internal overhead per packet.

RX PACKETS The number of packets received on this port for this service.

RX LOCAL DISCARDS The number of packets received on this port for this service, but discarded because the destination address has been learned on the ingress port.

RX HARDWARE PACKET DISCARDS

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.


SECTION 3 EQUIPMENT LED STATUSSECTION 3SYSTEM MONITORING

SECTION 3

Contents

Chapter 1LEDs and Module Status

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1PDAP LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Front Inlet Fan Tray Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Fan Tray Holder LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Traverse Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Power and Standby LED Indicators—All Modules . . . . . . . . . . . . . . . . . . . . . 3-7General Control Module (GCM) LED Indicators . . . . . . . . . . . . . . . . . . . . . . . 3-8Electrical Module Port LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Optical Module Port LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10GbE and Fast Ethernet Module Port LED Indicators. . . . . . . . . . . . . . . . . . . . 3-10

List of FiguresFigure 3-1 PDAP-2S LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Figure 3-2 PDAP-4S LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Figure 3-3 Front Inlet Fan Module with LEDs. . . . . . . . . . . . . . . . . . . . . . . . . 3-4Figure 3-4 Fan Tray Holder with LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Figure 3-5 Module LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

List of TablesTable 3-1 PDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Table 3-2 Front Inlet Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Table 3-3 Fan Tray Holder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Table 3-4 Power and Active/Standby—All Modules . . . . . . . . . . . . . . . . . . . 3-7Table 3-5 Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Table 3-6 Timing Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Table 3-7 Ethernet Link (OSS and Craft 10/100BaseT) . . . . . . . . . . . . . . . . 3-9Table 3-8 Electrical Module/Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Table 3-9 Optical Module/Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Table 3-10 GbE and Fast Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Node Operations and Maintenance Guide, Section 3 Equipment LED Status



SECTION 3EQUIPMENT LED STATUS

Chapter 1LEDs 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

Node Operations and Maintenance Guide, Section 3: Equipment LED StatusPDAP 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.

Figure 3-1 PDAP-2S LEDs

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/ANo critical alarms for the entire rack

GMT Fuse BlockPower

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

InputPower N/A

Power from Battery “A” or “B” input.

N/ANo power

Major Summary

Alarm

At least one major alarm in the rack. N/A N/A

No major alarms for the entire rack

InputPower

“A”

InputPower

“B”

Critical Minor

Major

GMT Fuse BlockPower

GMT Fuse BlockPower

InputPower

“A”

InputPower

“B”

Critical MinorMajor

TPA Fuses “A” TPA Fuses “B”

GMT Fuse

Chapter 1 LEDs and Module StatusPDAP LEDs


Minor Summary

AlarmN/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

Table 3-1 PDAP (continued)

LED RED GREEN AMBER OFF

Node Operations and Maintenance Guide, Section 3: Equipment LED StatusFront 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.

Figure 3-3 Front Inlet Fan Module with LEDs

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.

Power(green)

Fan Failure(red)

Traverse 1600 FIFT Traverse 600 FIFT

Power(green)

Fan Failure(red)

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.

Chapter 1 LEDs and Module StatusFan 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.

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.

Power(green)

Fan Failure(red)

Node Operations and Maintenance Guide, Section 3: Equipment LED StatusTraverse 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:

Figure 3-5 Module LEDs

DS3/E3 OC-N/STM-N Ethernet

DS1, DS3/E3,E1, OC-N/STM-N

and ETH PortIndicators

ETHERNET LINKOSS and Craft

Alarms:CRITICAL/MAJOR

MINOR

Timing:LOCKED/

UNLOCKEDFREE RUN/HOLDOVER

RS-232 Interface(DB-9)

EGCM

ACO ON

10/100BaseTEthernet Interface

(RJ-45)

DS1 VTSwitch

ACO

PWR(Power)

ACTV/STNBY

(Active/Standby)Optical

Port

E1

Chapter 1 LEDs and Module StatusPower 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

LEDRED 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.

Node Operations and Maintenance Guide, Section 3: Equipment LED StatusGeneral 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

LEDRED AMBER

OFFSolid Solid

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/AThe audible alarm is cut off (silenced).

The audible alarm is not cut off (not silenced).

Table 3-6 Timing Subsystem

LEDRED GREEN AMBER

OFFSolid Flashing Solid Flashing Solid

Locked/ Unlocked

Selected timing input reference is lost.

Lost-phase mode. LED flashes at 500ms on/off rate.

Locked to a timing input reference1 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 mode2 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 reference1.

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.

Chapter 1 LEDs and Module StatusElectrical Module Port LED Indicators


:

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-7 Ethernet Link (OSS and Craft 10/100BaseT)

LEDRED 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.

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.

Node Operations and Maintenance Guide, Section 3: Equipment LED StatusOptical 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.

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

Table 3-10 GbE and Fast Ethernet Port

LEDRED 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


SECTION 4 DIAGNOSTICSSECTION 4

Contents

Chapter 1Diagnostics Overview

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Symptoms and Recommended Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Chapter 2Traverse Transmit and Receive Signal Levels

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Traverse Optical Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Fast Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4GbE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4OC-3/STM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4OC-12/STM-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4OC-48/STM-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4OC-192/STM-64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Chapter 3TraverseEdge 100 Transmit and Receive Signal Levels

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7TE-100 Optical Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Chapter 4Loopback Tests

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9DS1 and DS3 Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

DS1 and DS3 Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . 4-10DS1 and DS3 Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

EC-3 and STM-1E Loopback Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11EC-3and STM-1E Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . 4-11EC-3 and STM-1E Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

E1 and E3 Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12E1 and E3 Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12E1 and E3 Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Ethernet Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Ethernet Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Ethernet Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

SONET/SDH Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15SONET/SDH Facility Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15SONET/SDH Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Performing Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Node Operations and Maintenance Guide, Section 4 Diagnostics


Chapter 5Other Diagnostics

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Power On Self Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Alarm Cut-Off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21LED Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

List of FiguresFigure 4-1 DS-x Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Figure 4-2 DS-x Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Figure 4-3 EC-3/STM-1E Facility Payload Loopback . . . . . . . . . . . . . . . . . . . 4-11Figure 4-4 EC-3/STM-1E Terminal Loopback. . . . . . . . . . . . . . . . . . . . . . . . . 4-11Figure 4-5 E-x Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Figure 4-6 E-x Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Figure 4-7 Ethernet Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . 4-13Figure 4-8 Ethernet Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Figure 4-9 SONET/SDH Facility Payload Loopback. . . . . . . . . . . . . . . . . . . . 4-15Figure 4-10 SONET/SDH Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Figure 4-11 Setting Up a Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Figure 4-12 Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

List of TablesTable 4-1 Symptoms and Recommended Actions . . . . . . . . . . . . . . . . . . . . 4-2Table 4-2 Optical Interface Specification Summary Table. . . . . . . . . . . . . . . 4-4Table 4-3 SONET, STM, and GbE Optics . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Table 4-4 Performing Loopback Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16


SECTION 4DIAGNOSTICS

Chapter 1Diagnostics 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

Node O


uide, Section4: D

iagnosticsSym

ptoms and R

ecomm

ended Actions

Page 4-2Turin N

etworks

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 Symptom Description Scope Probable Cause Recommended Action

Environmental Alarms

Environmental Alarm input or output is incorrect.

Node ■ Incorrect alarm cable connections

■ Environmental Alarm Module (EAM) failure

■ 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

OC-192 Module 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 OC-192 module was installed in a node with pre-Release 1.3 software.

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



Chapter 2Traverse 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.

Node O


uide, Section4: D

iagnosticsTraverse O

ptical Interface Specifications

Page 4-4Turin N

etworks

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 Wave-length Range

RX Wave-length Range

Transmitter Output Power1

Receiver Signal1,2

Guaran-teed Link Budget1,3

Maximum Reach4

(nm) (nm) (nm) (dBm) (dBm) (dB) (mi) (km)

Fast Ethernet 100BaseFX (GbE/Fast Ethernet combo) 1310 1261 to 1360 1260 to 1600 -16 to -14 -29 to -14 13 20.2 32.5

GbE GbE SX 850 830 to 860 770 to 860 -10.5 to -4 -16 to -3 5.5 0.34 0.55

GbE LX 1310 1270 to 1360 1270 to 1355 -10 to -3 -18 to -3 8 6.21 10

GbE CWDM 1470 to 1610(8 channels at 20 nm intervals)

1260 to 1620 -1 to 4 -18 to -0 17 24.85 40

OC-3/STM-1 OC-3 IR1/STM-1 SH1 1310 1261 to 1360 1260 to 1600 -16 to -8 -28 to -7 12 9.32 15

OC-3 LR2/STM-1 LH2 1550 1480 to 1580 1260 to 1600 -6 to 0 -32 to -10 11 49.71 80

OC-12/STM-4 OC-12 IR1/STM-4 SH15 1310 1274 to 1356 1260 to 1600 -16 to -8 -27 to -7 11 9.32 15


OC-48/STM-16 OC-48 SR1/STM-16 SH15 1310 1266 to 1360 1260 to 1600 -11 to -3 -17 to -3 6 1.24 2

OC-48 IR1/STM-16 SH15 1310 1260 to 1360 1260 to 1600 -6 to 0 -17 to 0 11 9.32 15



OC-48 LR2/STM-16 LH CWDM 1470 to 1610(8 channels at 20 nm intervals)

1260 to 1620 -1 to 5 -25 to -8 24 49.71 80

OC-48 ELR/STM-16 LH ITU DWDM 1529.55 to 1562.23 (42 channels) 1260 to 1600 -1 to 4 -26 to -8 25 62.14 100

OC-48 VR2/STM-16 VLH 1550 1530 to 1560 1260 to 1600 4 to 10 -25 to -8 29 62.14 100

Chapter2

Traverse Transmit and R

eceive Signal LevelsTraverse O


Release O

PS3.1.xTurin N

etworks

Page 4-5

OC-192/STM-64 OC-192 SR1/STM-64 SH1 1310 1290 to 1330 1290 to 1600 -5 to -1 -13 to -1 8 7.46 12

OC-192 IR2/STM-64 SH2 1550 1530 to 1565 1290 to 1600 -2 to 2 -11 to -1 9 24.85 40

OC-192 LR2/STM-64 LH2 1550 1530 to 1565 1290 to 1600 2 to 7 -20 to -4 22 49.71 80

OC-192 LR/STM-64 LH ITU DWDM 1529.55 to 1562.23 (42 channels) 1290 to 1600 2 to 7 -20 to -4 22 49.71 80

OC-192 ELR/STM-64 LH ITU DWDM 1529.55 to 1562.23 (42 channels) 1290 to 1600 2 to 7 -23 to -4 25 55.92 90

1 These values account for the connector loss from connection to the optical interface and the worst case optical path penalty.

2 223 -1 PRBS, BER=10-10

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.

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.

Table 4-2 Optical Interface Specification Summary Table (continued)

Optical Interface Module Optic Type

Typical Nominal TX Wavelength

TX Wave-length Range

RX Wave-length Range

Transmitter Output Power1

Receiver Signal1,2

Guaran-teed Link Budget1,3

Maximum Reach4

(nm) (nm) (nm) (dBm) (dBm) (dB) (mi) (km)

Node O


uide, Section4: D

iagnosticsTraverse O


Page 4-6Turin N

etworks

Release OPS3.1.x



Chapter 3TraverseEdge 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.

Node O


uide, Section4: D

iagnosticsTE-100 O


Page 4-8Turin N

etworks

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.

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.

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.

Table 4-3 SONET, STM, and GbE Optics

Application Approx Distance

(km)

Tx Power Range(dBm)

Rx Power Range(dBm)

Dispersion Penalty

(db)

Attenuation Range

Extinction Ratio (dB)

Tx Wavelength

Range(nm)

RxWavelength

Range(nm)

Dispersion Tolerance (ps/nm)

Temperature Range (degC)SONET STM

OC-3 IR-1 STM-1 S-1.1 15 -15 to -8 -29 to -7 0 0 to 14 8.2 1261 to 1360 1260 to 1600 0 -40 to 85

OC-3 LR-2 STM-1 L-1.2 80 -5 to 0 -33 to -10 1 10 to 28 10 1480 to 1580 1260 to 1600 0 0 to 70

OC-12 IR-1 STM-4 S-4.1 15 -15 to -8 -28 to -7 0 0 to 13 8.2 1274 to 1356 1260 to 1600 0 -40 to 85

OC-12 LR-2 STM-4 L-4.2 80 -3 to 2 -27 to -8 1 10 to 24 10 1480 to 1580 1260 to 1600 0 -5 to 70

OC-48 SR-1 STM-16 I-16 2 -10 to -3 -18 to -3 0 0 to 8 8.2 1266 to 1360 1260 to 1600 0 0 to 70

OC-48 IR-1 STM-16 S.16.1 15 -5 to 0 -18 to 0 0 0 to 13 8.2 1260 to 1360 1260 to 1600 0 0 to 70

OC-48 LR-1 STM-16 L-16.1 40 -2 to 3 -27 to -8 1 11 to 25 8.2 1280 to 1335 1260 to 1600 0 0 to 70

OC-48 LR-2 STM-16 L-16.2 80 -2 to 3 -26 to -8 2 11 to 24 8.2 1500 to 1580 1260 to 1600 1600 0 to 70

OC-48 LR-2 STM-16 L-16.2 80 0 to 5 -26 to -8 2 13 to 26 8.2 1470 to 1610 1260 to 1600 1760 -5 to 70

OC-48 ELR STM-16 100 0 to 4 -27 to -8 2 12 to 27 8.2 1529.55 to 1562.23

1260 to 1600 1750 0 to 70

1000Base SX 1000Base SX 0 -9.5 to -4 -17 to -3 0 0 to 7.5 9 830 to 860 770 to 860 0 0 to 70

1000Base LX 1000Base LX 10 -9 to -3 -19 to -3 0 0 to 10 9 1270 to 1360 1270 to 1355 0 0 to 70

1000Base ZX 1000Base ZX 80 0 to 4 -22 to 0 1 4 to 22 9 1430 to 1580 1260 to 1620 1600 -5 to 70



Chapter 4Loopback 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

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.

WARNING! Loopback tests interrupt traffic flow; do not perform them on nodes providing service.

Node Operations and Maintenance Guide, Section 4: DiagnosticsDS1 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.

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.

Figure 4-2 DS-x Terminal Loopback

DS-x module Trunk module

LIU LIUAIS

DS-x facility underloopback test

TestSet

Servicebetween ports


LIU LIU


TestSet

Service set upbetween ports

Chapter 4 Loopback TestsEC-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.

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.

Figure 4-4 EC-3/STM-1E Terminal Loopback


LIU LIUAIS


TestSet


EC-3/STM-1E


LIU LIU


TestSet


EC-3/STM-1E

Node Operations and Maintenance Guide, Section 4: DiagnosticsE1 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.

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.

Figure 4-6 E-x Terminal Loopback

E-x module Trunk module

LIU LIUAIS

E-x facility underloopback test

TestSet


E-x module Trunk module

LIU LIU

E-x facility underloopback test

TestSet


Chapter 4 Loopback TestsEthernet 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.

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).

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.

Node Operations and Maintenance Guide, Section 4: DiagnosticsEthernet 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

Chapter 4 Loopback TestsSONET/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.

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 4-10. Terminal loopback is used to verify the integrity of the electronics associated with the framer or the transmitted signal.

Figure 4-10 SONET/SDH Terminal Loopback

OC-N module OC-N module

LIU LIUAIS

SONET facilityunder loopback test

STS-NSTS-N

TestSet


OC-N/STM-Nmodule

OC-N/STM-Nmodule

LIU LIU

SONET/SDH facilityunder loopback test

TestSet


Node Operations and Maintenance Guide, Section 4: DiagnosticsPerforming Loopback Tests


Performing Loopback Tests

Before performing loopback testing, the port’s administrative state must first be changed to Unlocked.

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.

Important: Loopback tests interrupt data flow; do not perform them on a port providing service.

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.


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.

Chapter 4 Loopback TestsEquipment States


Equipment States

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): 223-1 PRBS– Fixed-24Bit: Repeating 24-bit pattern

(101110111011101110111011)

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.

Table 4-4 Performing Loopback Tests (continued)

Step Procedure

Node Operations and Maintenance Guide, Section 4: DiagnosticsEquipment States


Icons in the bottom left-hand corner of the Config tab indicate the state of the module or port.

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.

Operational state

Equipped state

Administrative state

Chapter 4 Loopback TestsEquipment States


Node Operations and Maintenance Guide, Section 4: DiagnosticsEquipment States




Chapter 5Other Diagnostics

Introduction 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

Power On Self Test

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.

Alarm Cut-Off 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.

LED Lamp Test 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.

Node Operations and Maintenance Guide, Section 4: DiagnosticsLED Lamp Test



SECTION 5 TEST ACCESSSECTION 5

Contents

Chapter 1Traverse Test Access

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Local Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Remote Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Mode Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Access Identifier (AID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Monitor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Split Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Feature Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Test Access Mode Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Monitor Test Access Example (MONE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Per Side Split Test Access Example (SPLTE) . . . . . . . . . . . . . . . . . . . . . . . . 5-14Series Split Test Access Example (SPLTA) . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Chapter 2Traverse Test Access Guidelines for the Spirent BRTU Interface

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Traverse Platform and Spirent BRTU Interoperability . . . . . . . . . . . . . . . . . . . 5-24Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface . . . . 5-25

List of FiguresFigure 5-1 Local Traverse DCS3/1 Test Access . . . . . . . . . . . . . . . . . . . . . . 5-2Figure 5-2 Remote Traverse DCS3/1 Test Access . . . . . . . . . . . . . . . . . . . . 5-3Figure 5-3 TransNav GUI AID Format Example. . . . . . . . . . . . . . . . . . . . . . . 5-5Figure 5-4 Monitor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Figure 5-5 Split Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Figure 5-6 Monitor Test Access Configuration—MONE. . . . . . . . . . . . . . . . . 5-10Figure 5-7 Example VT TAP (Single FAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Figure 5-8 MONE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Figure 5-9 Service with MONE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . 5-13Figure 5-10 Per Side Split Test Access Configuration—SPLTE . . . . . . . . . . . 5-14Figure 5-11 Example VT TAP (Single FAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15Figure 5-12 SPLTE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Figure 5-13 Service with SPLTE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . 5-17Figure 5-14 Series Split Test Access Configuration—SPLTA . . . . . . . . . . . . . 5-18Figure 5-15 Example DS1 TAP (Single FAD). . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Node Operations and Maintenance Guide, Section 5 Test Access


Figure 5-16 SPLTA TAC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Figure 5-17 Service with SPLTA TAC Example . . . . . . . . . . . . . . . . . . . . . . . . 5-21Figure 5-18 Turin TransNav GUI and Spirent BRTU REACT OSS Example . . 5-24

List of TablesTable 5-1 Test Access Mode vs. Service Compatibility Matrix . . . . . . . . . . . 5-4Table 5-2 Monitor Test Access Configuration—MONE . . . . . . . . . . . . . . . . . 5-11Table 5-3 Per Side Split Test Access Configuration—SPLTE. . . . . . . . . . . . 5-15Table 5-4 Series Split Test Access Configuration—SPLTA . . . . . . . . . . . . . 5-19


SECTION 5TEST ACCESS

Chapter 1Traverse 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 5-23.

For parameter descriptions, see the TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 5—“Test Access,” page 8-43.

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 5-9

1 (SDH network only) Test access is planned for a future release.

Node Operations and Maintenance Guide, Section 5: Test AccessLocal 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.

Figure 5-1 Local Traverse DCS3/1 Test Access

TestSystem

Controller(TSC)

Test Access Point (TAP)(e.g., DS1 port)

ManagementSystem

(GUI, CLI, or TL1)

DCS3/1

RemoteTestUnit

(RTU)

Patch Panel

Node-level Control Link(CLI or TL1)Termination Point (TP)

of the Circuit Under Test

TransNav

Chapter 1 Traverse Test AccessRemote 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.

Figure 5-2 Remote Traverse DCS3/1 Test Access

SONETNetwork

Remote Test Unit(RTU)

Remote AccessMultiplexer

Physical TAPs (e.g., DS1)

Logical TAPs(e.g., VT1.5 on OC-N port)

DCS3/1

STS-1or VTPath

Node Operations and Maintenance Guide, Section 5: Test AccessMode 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

ModeService

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

Chapter 1 Traverse Test AccessAccess 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 2000. 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.

Node Operations and Maintenance Guide, Section 5: Test AccessMonitor 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 point2

■ MONEF - Monitor bidirectional data flow from both the ingress and egress termination points

Figure 5-4 Monitor Configurations

2 If MONF is configured with a DFAD instead of the standard FAD, then it uses the second FAD.

FAD

E F

MONF Test Access

FAD

E F

MONE Test Access

FAD

E F

MONEF Test Access

FAD

Chapter 1 Traverse Test AccessSplit 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 service3

■ 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 point4

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.

A

B

SPLTB Test Access

FAD

A

B

SPLTA Test Access

FAD

E

F

SPLTF Test Access

FAD

E

F

SPLTE Test Access

FAD

FAD

E

F

SPLTEF Test Access

FAD

Node Operations and Maintenance Guide, Section 5: Test AccessFeature 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.

Chapter 1 Traverse Test AccessMonitor Test Access Example (MONE)


Configuration Management

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.

Test Access Mode Examples

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

Monitor Test Access Example (MONE)

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

Node Operations and Maintenance Guide, Section 5: Test AccessMonitor Test Access Example (MONE)


is active. These states remain intact through the MONE test access mode configuration and use.

Figure 5-6 Monitor Test Access Configuration—MONE

Service to be Tested

Monitor Test Access(Non-Intrusive)

TAP (e.g., DS1)

DCS D1S1

TAP1

DCS D1S1



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)

Node Operations and Maintenance Guide, Section 5: Test AccessMonitor Test Access Example (MONE)


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.

Figure 5-8 MONE TAC Example

Table 5-2 Monitor Test Access Configuration—MONE (continued)

Step Procedure

TAP1MONE Mode Service ID Connected State

Switch Mode command



4 The original service remains intact (enabled) as seen when you select the Service tab.

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.

Table 5-2 Monitor Test Access Configuration—MONE (continued)

Step Procedure

Service ID Enabled Operational State

Node Operations and Maintenance Guide, Section 5: Test AccessPer 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.

Figure 5-10 Per Side Split Test Access Configuration—SPLTE


Per Side Split Test Access(Intrusive)

TAP (e.g., DS1)

DCS D1S1

TAP1

DCS D1S1

Chapter 1 Traverse Test AccessPer 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)

Node Operations and Maintenance Guide, Section 5: Test AccessPer Side Split Test Access Example (SPLTE)


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.


Figure 5-12 SPLTE TAC Example

Table 5-3 Per Side Split Test Access Configuration—SPLTE (continued)

Step Procedure

TAP2SPLTE Mode Service ID Connected State

Switch Mode command

Chapter 1 Traverse Test AccessPer Side Split Test Access Example (SPLTE)


4 The system disables the original service as seen when you select the Service tab.

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.

Table 5-3 Per Side Split Test Access Configuration—SPLTE (continued)

Step Procedure


Node Operations and Maintenance Guide, Section 5: Test AccessSeries 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.

Figure 5-14 Series Split Test Access Configuration—SPLTA


Series Split Test Access(Intrusive)

TAP (e.g., DS1)

DCS D1S1

TAP1

DCS D1S1

Chapter 1 Traverse Test AccessSeries 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)



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.


Figure 5-16 SPLTA TAC Example

Table 5-4 Series Split Test Access Configuration—SPLTA (continued)

Step Procedure

TAP3SPLTE Mode Service ID Connected State

Switch Mode command

Chapter 1 Traverse Test AccessSeries Split Test Access Example (SPLTA)


4 The system disables the original service as seen when you select the Service tab.

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.

Table 5-4 Series Split Test Access Configuration—SPLTA (continued)

Step Procedure





SECTION 5TEST ACCESS

Chapter 2Traverse 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.

Node Operations and Maintenance Guide, Section 5: Test AccessTraverse 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.

Figure 5-18 Turin TransNav GUI and Spirent BRTU REACT OSS Example

Spirent REACT OSSTurin TransNav GUI

Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU InterfaceGuidelines 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.

Node Operations and Maintenance Guide, Section 5: Test AccessGuidelines to Set Up the Traverse Test Access Spirent BRTU Interface



SECTION 6 ROUTINE MAINTENANCESECTION 6SYSTEM MONITORING

SECTION 6

Contents

Chapter 1Routine Maintenance

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Fan Air Filter Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Fan Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000) . . . . . 6-1Fan Module with Integral Fan Tray (Traverse 600) . . . . . . . . . . . . . . . . . 6-1Fan Assembly (TE-100). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Fan Tray Module (Legacy Traverse) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Air Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Air Filter Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Air Filter Replacement (Traverse 1600 and Traverse 2000) . . . . . . . . . . . . . . 6-2Fan Tray Air Filter Replacement (Traverse 600). . . . . . . . . . . . . . . . . . . . . . . 6-4Air Filter Replacement (TE-100) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Air Filter Replacement (Legacy Traverse). . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7PDAP Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10PDAP-15A GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10PDAP-2S Circuit Breaker Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11PDAP-2S GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12PDAP-2S LED Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14PDAP-4S TPA Fuse Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16PDAP-4S GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18PDAP-4S LED Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Environmental Alarm Module Replacement (Traverse only). . . . . . . . . . . . . . 6-20Non-Field Replaceable Fuses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

Chapter 2Node Database Backup and Restore

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back-ing Up the Node Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23Guidelines for Node Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23Node Database Restore Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24Backup and Restore Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24

exec node database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24exec node database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25

Troubleshooting Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Node Operations and Maintenance Guide, Section 6 Routine Maintenance


List of FiguresFigure 6-1 Front Inlet Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Figure 6-2 Traverse 600 Fan Assembly Air Filter . . . . . . . . . . . . . . . . . . . . . . 6-4Figure 6-3 Fan Cage and Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Figure 6-4 Removing the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Figure 6-5 Attaching the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Figure 6-6 Air Filter with Springs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Figure 6-7 Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Figure 6-8 Air Filter with Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Figure 6-9 Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10Figure 6-10 PDAP-15A Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Figure 6-11 PDAP-2S Circuit Breakers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Figure 6-12 PDAP-2S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Figure 6-13 PDAP-2S Assembly - Remove Front Cover . . . . . . . . . . . . . . . . . 6-14Figure 6-14 PDAP-2S Assembly - LED Module . . . . . . . . . . . . . . . . . . . . . . . . 6-15Figure 6-15 PDAP-2S LED Module Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15Figure 6-16 PDAP-4S TPA Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Figure 6-17 PDAP-4S TPA Fuse and Holder . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Figure 6-18 PDAP-4S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Figure 6-19 PDAP-4S Assembly - LED Faceplate . . . . . . . . . . . . . . . . . . . . . . 6-19Figure 6-20 EAM Location - Traverse 1600 Main Backplane . . . . . . . . . . . . . . 6-20Figure 6-21 EAM Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

List of TablesTable 6-1 Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000) . . . . . 6-3Table 6-2 Insert a Fan Assembly Air Filter (Traverse 600) . . . . . . . . . . . . . . 6-4Table 6-3 Replace the Fan Air Filter (TE-100). . . . . . . . . . . . . . . . . . . . . . . . 6-5Table 6-4 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) . . 6-7Table 6-5 Fan Tray Air Filter (with handle) Installation . . . . . . . . . . . . . . . . . 6-9Table 6-6 Replacing PDAP-15A GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . 6-11Table 6-7 Replacing PDAP-2S Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . 6-12Table 6-8 Replacing PDAP-2S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Table 6-9 Replacing PDAP-2S LED Module . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Table 6-10 Replacing PDAP-4S TPA Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Table 6-11 Replacing PDAP-4S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Table 6-12 Replacing PDAP-4S LED Module . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Table 6-13 Replacing EAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20Table 6-14 CLI Command Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24


SECTION 6ROUTINE MAINTENANCE

Chapter 1Routine Maintenance

Introduction 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

Fan Air Filter Maintenance

The fan maintenance topics are as follows:■ Fan Assemblies, page 6-1■ Air Filters, page 6-2■ Air Filter Replacement, page 6-2

Fan Assemblies

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

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceAir 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.

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).

Air Filter Replacement

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

Air Filter Replacement (Traverse 1600 and Traverse 2000)

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.

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.

Important: Fan tray air filters should be checked once every six months and replaced as necessary.

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.

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 www.turinnetworks.com. User registration is required. To register for the Turin Infocenter, contact your sales account team.

Chapter 1 Routine MaintenanceAir 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

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.

Pull Tab (top view)

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceFan 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


Figure 6-2 Traverse 600 Fan Assembly Air Filter

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.


Pull Tab (top view)

Chapter 1 Routine MaintenanceAir 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.

Figure 6-3 Fan Cage and Assembly

3 Lift the old air filter from the fan assembly.

Figure 6-4 Removing the Air Filter

4 Make sure the new air filter is clean and free of dust particles.

Captive Fastener

Fan Cage

Pull up on the air filter

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceAir Filter Replacement (TE-100)


5 Slide the air filter into place, lining up the small tabs with the small holes on the fan assembly.

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.

Table 6-3 Replace the Fan Air Filter (TE-100) (continued)

Step Procedure

Tabs Lined up with Holes

Chapter 1 Routine MaintenanceAir 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.

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.

Springs

Pull Tabs

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceAir Filter Replacement (Legacy Traverse)


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.

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.



Step Procedure

Captive Fasteners

Chapter 1 Routine MaintenanceAir 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.

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.

Handle

Node Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP Maintenance


PDAP Maintenance

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

PDAP-15A GMT Fuse Replacement

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.



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.

Table 6-5 Fan Tray Air Filter (with handle) Installation (continued)

Step Procedure

Captive Fasteners

WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits.

Chapter 1 Routine MaintenancePDAP-2S Circuit Breaker Replacement


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.

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

Figure 6-10 PDAP-15A Front View

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.

2 Replace the failed GMT fuse with a new one of equal current rating.

3 The Replacing PDAP-2S GMT Fuses procedure is complete.

GMT Fuses

Alarm LEDs

1 Optional PDAP-2S circuit breakers are available up to a 50 amp maximum.


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.

Node Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-2S GMT Fuse Replacement


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.


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.

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.

Circuit Breakers, Pair BCircuit Breakers, Pair A

Toggle Switches



Chapter 1 Routine MaintenancePDAP-2S GMT Fuse Replacement


Table 6-8 Replacing PDAP-2S GMT Fuses

Step Procedure


Figure 6-12 PDAP-2S GMT Fuses



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.

GMT Fuse Block GMT Fuse Block(Pair A) (Pair B)

Node Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-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

Chapter 1 Routine MaintenancePDAP-2S LED Module Replacement


3 Locate the nonfunctional module with a white pull tab at the center of the PDAP-2S.

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.

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.

Table 6-9 Replacing PDAP-2S LED Module (continued)

Step Procedure

LED module

White Pull Tab

Right Guide

Left Guide

Node Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-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.

2 Optional PDAP-4S TPA fuses are available up to a 50 amp maximum.



Chapter 1 Routine MaintenancePDAP-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.

Figure 6-16 PDAP-4S TPA Fuses

2 Remove the TPA fuse holder by pulling it straight out.1

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.

TPA Fuse Holders

Pair A Pair B

TPA Fuse LEDsTPA Fuse LEDs

TPA Fuse Holder

TPA Fuse

Node Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-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.




Table 6-11 Replacing PDAP-4S GMT Fuses

Step Procedure


Figure 6-18 PDAP-4S GMT Fuses

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.



GMT Fuse Block GMT Fuse Block(Pair A) (Pair B)

Chapter 1 Routine MaintenancePDAP-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.

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.

Captive Fasteners

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceEnvironmental 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.

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.

Connector

Plastic Standoff

EAM

with Tab

Pivotal

Chapter 1 Routine MaintenanceNon-Field Replaceable Fuses


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.

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.

Figure 6-21 EAM Alignment

4 The Replacing EAM procedure is complete.

Table 6-13 Replacing EAM (continued)

Step Procedure

Long edge

Pins facing Main Backplane Proper Alignment Guide

Plastic Standoff Guide

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceNon-Field Replaceable Fuses



SECTION 6ROUTINE MAINTENANCE

Chapter 2Node Database Backup and Restore

Introduction 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

Backing Up the Node Database

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.

Guidelines for Node Database Backups

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 127.0.0.1 (localhost). This default is for the active

GCM module.

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceNode 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

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.

Backup and Restore Commands

Command descriptions use the following conventions:

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.

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 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 Italics indicate arguments for which you supply values.

Boldface Underlined

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.

Chapter 2 Node Database Backup and RestoreBackup 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

Node Operations and Maintenance Guide, Section 6: Routine MaintenanceTroubleshooting 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.


SECTION 7 SOFTWARE UPGRADESSECTION 7

Contents

Chapter 1Release TR2.1.x Traverse Software Upgrade

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Release TR2.1.x Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Node Software Upgrade Flowchart (Top Level) . . . . . . . . . . . . . . . . . . . . . . . 7-2Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Traverse Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

TransNav Management System GUI Commands and Conventions . . . . . . . . 7-4Compatibility and Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4General Software Compatibility Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Traverse System SW Upgrade Compatibility Notes . . . . . . . . . . . . . . . . . . . . 7-5

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Software Upgrade for TR2.1 Maintenance Releases . . . . . . . . . . . . . . . 7-6Software Upgrade from Release 2.0.x.x to TR2.1. . . . . . . . . . . . . . . . . . 7-6Software Upgrade from 1.5E to TR2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Software Upgrade from 1.5 to TR2.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Guidelines for Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Pre-Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-10Download Node Software to the TransNav Server— PC System. . . . . . . . . . 7-10Download Node Software to the TransNav Server— Solaris System. . . . . . . 7-11Module Software Download Set-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Module Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18BLSR/MS-SP Ring on GCM with Optics Software Activation . . . . . . . . . . . . . 7-21Control Module Software Upgrade Activation . . . . . . . . . . . . . . . . . . . . . . . . . 7-25Software Upgrade Activate (all other protected modules). . . . . . . . . . . . . . . . 7-30Software Upgrade Activate (all unprotected modules) . . . . . . . . . . . . . . . . . . 7-33Spare Control Module Software Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35Spare Module Software Activation (All Other Types) . . . . . . . . . . . . . . . . . . . 7-36Post-Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36Verify Protection Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37Perform a Forced Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38Perform a Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Clear Protection Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41Software Revert Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44

Node Operations and Maintenance Guide, Section 7 Software Upgrades


Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44Revert TransNav Management System Software . . . . . . . . . . . . . . . . . . 7-45

Post-Remote Node— Upgrade the Spare Control Module Software. . . . . . . . 7-45User- selectable FPGA Upgrade Capability . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47

Chapter 2Release 3.0.x TE-100 System Software Upgrade

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49Release 3.0.x Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50Required Equipment and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50TE-100 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50

TransNav Management System GUI Commands and Conventions . . . . . . . . 7-51Compatibility and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51General Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51TE-100 Platform SW Upgrade Compatibility Notes . . . . . . . . . . . . . . . . . . . . . 7-53Guidelines for Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-54Download Node Software to the TransNav Server— PC System . . . . . . . . . . 7-55Download Node Software to the TransNav Server— Solaris System . . . . . . . 7-56Module Software Download Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58Module Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61Control Module Software Upgrade Activation . . . . . . . . . . . . . . . . . . . . . . . . . 7-62Spare Control Module Software Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65Software Revert Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66

Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66Revert TransNav Management System Software . . . . . . . . . . . . . . . . . . 7-67

List of FiguresFigure 7-1 Node Software Upgrade Process Flowchart . . . . . . . . . . . . . . . . . 7-2Figure 7-2 Example—PC System Explorer Window File Listing . . . . . . . . . . 7-10Figure 7-3 Explorer “Extract to” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Figure 7-4 Example—File Extraction Comments . . . . . . . . . . . . . . . . . . . . . . 7-12Figure 7-5 SW Upgrade Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Figure 7-6 Download Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14Figure 7-7 SW Upgrade Download Times . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15Figure 7-8 SW Upgrade—Clear Download Time . . . . . . . . . . . . . . . . . . . . . . 7-16Figure 7-9 Dnld Status and Standby SW Version Fields . . . . . . . . . . . . . . . . 7-17Figure 7-10 Card Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Figure 7-11 Card Configuration GCM Protection Status. . . . . . . . . . . . . . . . . . 7-21Figure 7-12 SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22Figure 7-13 Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-23Figure 7-14 Card Configuration Protection Status . . . . . . . . . . . . . . . . . . . . . . 7-26Figure 7-15 SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26



Figure 7-16 Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-27Figure 7-17 SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30Figure 7-18 Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-31Figure 7-19 SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33Figure 7-20 Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-34Figure 7-21 Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37Figure 7-22 Equipment Protection Group Configuration Dialog Box . . . . . . . . 7-38Figure 7-23 Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38Figure 7-24 Protection Group—Forced Switch. . . . . . . . . . . . . . . . . . . . . . . . . 7-39Figure 7-25 Confirm Force Switch Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . 7-39Figure 7-26 Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Figure 7-27 Protection Group—Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . 7-40Figure 7-28 Confirm Manual Switch Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . 7-40Figure 7-29 Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41Figure 7-30 Protection Group—Clear Protection Switch . . . . . . . . . . . . . . . . . 7-42Figure 7-31 Confirm Release Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42Figure 7-32 Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43Figure 7-33 User-selectable FPGA Upgrade Parameter . . . . . . . . . . . . . . . . . 7-47Figure 7-34 Example—PC System Explorer Window File Listing . . . . . . . . . . 7-55Figure 7-35 Explorer “Extract to” Command. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55Figure 7-36 Example—File Extraction Comments. . . . . . . . . . . . . . . . . . . . . . 7-57Figure 7-37 SW Upgrade Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58Figure 7-38 Download Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59Figure 7-39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59Figure 7-40 SW Upgrade—Clear Download Time. . . . . . . . . . . . . . . . . . . . . . 7-60Figure 7-41 Dnld Status and Standby SW Version Fields . . . . . . . . . . . . . . . . 7-60Figure 7-42 Card Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61Figure 7-43 Card Configuration Protection Status . . . . . . . . . . . . . . . . . . . . . . 7-63Figure 7-44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63Figure 7-45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63

List of TablesTable 7-1 Node Software Upgrade Requirements . . . . . . . . . . . . . . . . . . . . 7-3Table 7-2 TransNav GUI Command Descriptions. . . . . . . . . . . . . . . . . . . . . 7-4Table 7-3 Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Table 7-4 Pre-Software Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . 7-9Table 7-5 Download Node Software to the TransNav Server—PC System . 7-10Table 7-6 Download Node Software to the TransNav Server—

Solaris System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Table 7-7 Module Software Download Set-up. . . . . . . . . . . . . . . . . . . . . . . . 7-13Table 7-8 Module Software Version Number Verification . . . . . . . . . . . . . . . 7-18Table 7-9 Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Table 7-10 Activate Software—BLSR/MS-SP Ring GCM with Optic

Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21Table 7-11 Activate Software—Control Module . . . . . . . . . . . . . . . . . . . . . . . 7-25



Table 7-12 Activate Software —All Other Protected Modules . . . . . . . . . . . . . 7-30Table 7-13 Activate Software —All Unprotected Modules . . . . . . . . . . . . . . . . 7-33Table 7-14 Activate Software—Spare Control Modules . . . . . . . . . . . . . . . . . 7-35Table 7-15 Activate Software—Spare Modules (All Other Types) . . . . . . . . . 7-36Table 7-16 Post-Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . 7-36Table 7-17 Verify Protection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37Table 7-18 Perform a Forced Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38Table 7-19 Perform a Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Table 7-20 Clear Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41Table 7-21 Deactivate Legacy Ethernet Services . . . . . . . . . . . . . . . . . . . . . . 7-43Table 7-22 Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44Table 7-23 Revert TransNav Management System Software . . . . . . . . . . . . . 7-45Table 7-24 Post-Remote Node Upgrade —Upgrade the Spare Control

Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45Table 7-25 Node Software Upgrade Requirements. . . . . . . . . . . . . . . . . . . . . 7-50Table 7-26 TransNav GUI Command Descriptions . . . . . . . . . . . . . . . . . . . . . 7-51Table 7-27 Turin Product and Software Release Compatibility . . . . . . . . . . . . 7-53Table 7-28 Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Table 7-29 Download Node Software to the TransNav Server—PC System . 7-55Table 7-30 Download Node Software to the TransNav Server—‘ Solaris System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56Table 7-31 Module Software Download Set-up . . . . . . . . . . . . . . . . . . . . . . . . 7-58Table 7-32 Module Software Version Number Verification . . . . . . . . . . . . . . . 7-61Table 7-33 Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62Table 7-34 Activate Software— Control Module . . . . . . . . . . . . . . . . . . . . . . . 7-62Table 7-35 Activate Software—Spare Control Modules . . . . . . . . . . . . . . . . . 7-65Table 7-37 Revert TransNav Management System Software . . . . . . . . . . . . . 7-67Table 7-36 Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67


SECTION 7SOFTWARE UPGRADES

Chapter 1Release TR2.1.x Traverse Software Upgrade

Introduction 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 Upgrade Overview

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

Node Operations and Maintenance Guide, Section 7: Software UpgradesNode 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

Chapter 1 Release TR2.1.x Traverse Software UpgradeRequired Equipment and Tools


Before You Begin

Review this information before you begin.

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 www.turinnetworks.com

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

Table 7-1 Node Software Upgrade Requirements

Requirement Reference

Compose and have ready for the Upgrade Team a comprehensive network upgrade plan.

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 (805-0108-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.

If you are upgrading from an earlier Traverse or TransNav software release, contact the Turin TAC.

Have the required equipment and tools ready.

Required Equipment and Tools, page 7-3

Node Operations and Maintenance Guide, Section 7: Software UpgradesTransNav 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.

Compatibility and Guidelines

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

General Software Compatibility Notes

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: 1.2.3.4):■ 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.

Table 7-2 TransNav GUI Command Descriptions

Command Description

Boldface Boldface indicates dialog box, field, menu, and list names

Italics Italics indicates information you supply

Chapter 1 Release TR2.1.x Traverse Software UpgradeTraverse 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 7-101.

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.

Node Operations and Maintenance Guide, Section 7: Software UpgradesTraverse 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 R2.0.2.4, R2.0.2.6, R2.0.3.4, R2.0.4.2, R2.0.5, and TR2.0.6.1 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-R2.0.3.4, pre-R2.0.4.2, pre-R2.0.5, or pre-TR2.0.6.1) to Release TR2.1.

Important: See the Upgrade and Installation Notes topic in the Turin Release Notes TR2.1.x (805-0008-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 (805-0008-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.

Chapter 1 Release TR2.1.x Traverse Software UpgradeNode Software Upgrade Process


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.■ 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 (805-0108-TR21) defines any potential exceptions. This document is on the Turin Infocenter website at www.turinnetworks.com. User registration is required. To register for the Turin Infocenter, contact your sales account team.

Node Software Upgrade Process

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?

Before You Begin, page 7-3

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.

Pre-Software Upgrade Procedure, page 7-9

Node Operations and Maintenance Guide, Section 7: Software UpgradesNode Software Upgrade Process


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.

TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Upgrade Server Software, page 2-33

5 Download the new node software to the TransNav server.

Download Node Software to the TransNav Server, page 7-10

6 Download the software to the modules.

Module Software Download Set-up, page 7-13

7 Activate the new software. Software Activation Process, page 7-18

8 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 7-36

9 The Node Software Upgrade Process is complete.

Table 7-3 Node Software Upgrade Process (continued)


Chapter 1 Release TR2.1.x Traverse Software UpgradePre-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 7-43.– 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 7-36.

– 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. 17152.)

– 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.

Node Operations and Maintenance Guide, Section 7: Software UpgradesDownload Node Software to the TransNav Server


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 www.turinnetworks.com. 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

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

Chapter 1 Release TR2.1.x Traverse Software UpgradeDownload Node Software to the TransNav Server— Solaris System


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.

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.


Step Procedure

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

Node Operations and Maintenance Guide, Section 7: Software UpgradesDownload Node Software to the TransNav Server— Solaris System


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-4 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 6 of the Node Software Upgrade Process, page 7-7.


Step Procedure

Chapter 1 Release TR2.1.x Traverse Software UpgradeModule 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 7-18.

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

Node Operations and Maintenance Guide, Section 7: Software UpgradesModule Software Download Set-up


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 10–20 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,

Figure 7-6 Download Time Settings

Table 7-7 Module Software Download Set-up (continued)

Step Procedure

7



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 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.


Step Procedure

8



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.

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.


Step Procedure

12



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.

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


Step Procedure

15b15a

Node Operations and Maintenance Guide, Section 7: Software UpgradesModule 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.

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.

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.

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: 1.2.3.4):■ 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.

2

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.

Chapter 1 Release TR2.1.x Traverse Software UpgradeSoftware Activation Process


WARNING! For TR2.1 upgrades from 2.0.2.x through to and including 2.0.2.4, Turin recommends reversing the order of GCM activation (i.e., activate the active GCM first, then the standby GCM). (Issues No. 17376)

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


1 Did you complete the Pre-Software Upgrade Procedure?

Pre-Software Upgrade Procedure, page 7-9

2 Did you complete the upgrade of TransNav EMS server and client software and download the node software to the TransNav server?

Section 2—Management Server Procedures, Chapter 1—“Server Administration Procedures,” Upgrade Server Software, page 2-13

3 Did you download the node software to the TransNav server?


Node Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Activation Process


4 Is the module software download complete?


5 Do you have your network nodes in a BLSR/MS-SP Ring network with Traverse Enhanced GCMs with Optics?

Important: For any Release 2.0.2.x through to and including 2.0.2.4, 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 2.0.2.x through to and including 2.0.2.4, Turin recommends reversing the order of GCM activation (i.e., activate the active GCM first, then standby GCM).

Control Module Software Upgrade Activation, page 7-25

7 Activate software for all modules set up in a protection group.

Software Upgrade Activate (all other protected modules), page 7-30

8 Activate software for all unprotected modules.

Software Upgrade Activate (all unprotected modules), page 7-33

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.

Spare Module Software Activation (All Other Types), page 7-36

10 The Software Activation Process is complete. Continue to Step 8 of the Node Software Upgrade Process, page 7-7.

Table 7-9 Software Activation Process (continued)


Chapter 1 Release TR2.1.x Traverse Software UpgradeBLSR/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.

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.

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.

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.

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 7-38.

Check the BLSR/MS-SP Ring state and verify that Force is issued on the near- and far-end.

3

Node Operations and Maintenance Guide, Section 7: Software UpgradesBLSR/MS-SP Ring on GCM with Optics Software Activation


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.

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 (805-0108-TR21).

8 Select to ignore the FPGA upgrade available on this module. See User- selectable 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.


Step Procedure

6

Chapter 1 Release TR2.1.x Traverse Software UpgradeBLSR/MS-SP Ring on GCM with Optics Software Activation


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 7-41.

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 7-38.

Check the BLSR/MS-SP Ring state and verify that Force is issued on the near- and far-end.


Step Procedure

10 11

Node Operations and Maintenance Guide, Section 7: Software UpgradesBLSR/MS-SP Ring on GCM with Optics Software Activation


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






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.


Step Procedure

Chapter 1 Release TR2.1.x Traverse Software UpgradeControl Module Software Upgrade Activation


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.

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.

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 7-41.

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 7-20.


Step Procedure

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.

Table 7-11 Activate Software—Control Module

Step Procedure


2 In Shelf View, select a control module and click the Config tab.

Node Operations and Maintenance Guide, Section 7: Software UpgradesControl Module Software Upgrade Activation


3 Verify the Protection Status of the Active/Standby control module using the Card Configuration dialog box.

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.


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



Table 7-11 Activate Software—Control Module (continued)

Step Procedure

3

4



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 (805-0108-TR21).



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.


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).


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.


Step Procedure

9 10



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.






Step Procedure






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.



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 7-20.


Step Procedure

Node Operations and Maintenance Guide, Section 7: Software UpgradesSoftware 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

Chapter 1 Release TR2.1.x Traverse Software UpgradeSoftware Upgrade Activate (all other protected modules)


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.




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.


9 Verify that the new software version is displayed in SW Activation dialog box, Current SW Ver field.


Table 7-12 Activate Software —All Other Protected Modules (continued)

Step Procedure

8 9

Node Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Upgrade Activate (all other protected modules)


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 7-18.

Table 7-12 Activate Software —All Other Protected Modules (continued)

Step Procedure

Chapter 1 Release TR2.1.x Traverse Software UpgradeSoftware 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.


3 Select the activation type Act Type and set to SA for the module.



regardless of its active or standby status.




6 Click Update.

2

Node Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Upgrade Activate (all unprotected modules)


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.


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

Table 7-13 Activate Software —All Unprotected Modules (continued)

Step Procedure

7 8

Chapter 1 Release TR2.1.x Traverse Software UpgradeSpare 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.

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.

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.

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

Node Operations and Maintenance Guide, Section 7: Software UpgradesSpare 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.

Post-Software Upgrade Procedure

Complete the following post-software upgrade procedure.

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 7-20.

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.

Chapter 1 Release TR2.1.x Traverse Software UpgradeVerify Protection Status


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:

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.

Table 7-16 Post-Software Upgrade Procedure (continued)

Step Procedure

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.

Figure 7-21 Protection Groups Dialog Box

3 Select the protection group.

4 Click Edit to display the Protection Group Configuration dialog box.

2

Node Operations and Maintenance Guide, Section 7: Software UpgradesPerform a Forced Switch


Perform a Forced Switch

Use the following step-by-step instructions to perform a user-initiated forced protection switch.

5 The status displays in the Protection field - either Active or Standby.

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 7-30.

Table 7-17 Verify Protection Status (continued)

Step Procedure

5

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

Chapter 1 Release TR2.1.x Traverse Software UpgradePerform a Forced Switch


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.

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.

Table 7-18 Perform a Forced Switch (continued)

Step Procedure

4

Node Operations and Maintenance Guide, Section 7: Software UpgradesPerform 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





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.

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

1

4

Chapter 1 Release TR2.1.x Traverse Software UpgradeClear Protection Switch


Clear Protection Switch

Use the following step-by-step instructions to clear (release) a user-initiated protection switch.

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.

Table 7-19 Perform a Manual Switch (continued)

Step Procedure

Table 7-20 Clear Protection Switch

Step Procedure

1 From Map View, double-click on a node to display the Shelf View.




4 Click Edit to display the Protection Group Creation dialog box.

2

Node Operations and Maintenance Guide, Section 7: Software UpgradesClear Protection Switch


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.

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.

Table 7-20 Clear Protection Switch (continued)

Step Procedure

5

Chapter 1 Release TR2.1.x Traverse Software UpgradeClear 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.


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.

1

Node Operations and Maintenance Guide, Section 7: Software UpgradesSoftware 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):beginexec upgrade switch-to-stdby-load slot <slot#>Are you sure you want to execute this command?YES.endexec node restartAre 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.

Chapter 1 Release TR2.1.x Traverse Software UpgradePost-Remote Node— Upgrade the Spare Control Module Software


Revert TransNav Management System Software

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.

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-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.

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.

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.


Node Operations and Maintenance Guide, Section 7: Software UpgradesPost-Remote Node— Upgrade the Spare Control Module Software


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 7-13.

5 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 7-25. You must change the value in the ActType field to SPARE.

Note: After the upgrade, the EQRMV and EQCOMM alarms clear.


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.

Table 7-24 Post-Remote Node Upgrade —Upgrade the Spare Control Module

Step Procedure

Chapter 1 Release TR2.1.x Traverse Software UpgradeUser- selectable FPGA Upgrade Capability


User- selectable 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

Node Operations and Maintenance Guide, Section 7: Software UpgradesUser- selectable FPGA Upgrade Capability



SECTION 7SOFTWARE UPGRADES

Chapter 2Release 3.0.x TE-100 System Software Upgrade

Introduction 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.x Upgrade Overview

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 nodes1

■ 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.

Node Operations and Maintenance Guide, Section 7: Software UpgradesBefore You Begin


Before You Begin

Review this information before you begin.


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 (www.turinnetworks.com)

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)

Table 7-25 Node Software Upgrade Requirements

Requirement Reference

Compose and have ready for the Upgrade Team a comprehensive network upgrade plan.

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.

■ Refer to Release Notes 3.0.x (805-0108-30).■ Read through this entire chapter.■ Contact your company’s Operations Manager.

The software upgrade feature for this release supports TransNav Release 1.5, 1.5E, and 2.0 to 3.0 upgrades.

If you are upgrading from an earlier TransNav software release, contact the Turin Technical Assistance Center.

Have the required equipment and tools ready.


Chapter 2 Release 3.0.x TE-100 System Software UpgradeGeneral 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.

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








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,

Table 7-26 TransNav GUI Command Descriptions

Command Description

Boldface Boldface indicates dialog box, field, menu, and list names

Italics Italics indicates information you supply

Node Operations and Maintenance Guide, Section 7: Software UpgradesGeneral Software Compatibility


use the procedures in this section to upgrade or rollback the software version on the replacement module.

Chapter 2 Release 3.0.x TE-100 System Software UpgradeGuidelines 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.

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 (805-0108-30) define any

potential exceptions.

Table 7-27 Turin Product and Software Release Compatibility

TE-100 Release 3.0 Traverse Release 2.0

TE-100 3.0.x TE-100 2.0.x

Traverse 2.0.x Traverse 2.0.x

TE-50 4.3.x TE-50 4.3.x

TransNav 3.0.x manages:■ Traverse 2.0.x, 1.5E.x, 1.5x■ TE-100 3.0.x■ TransAccess 200 Mux 9.0

TransNav 2.0.x manages:■ Traverse 2.0.x, 1.5E.x, 1.5x, 1.4E.x, 1.4.x■ TE-100 2.0.x■ TransAccess 200 Mux 8.1 alarms

TransAccess 200 Mux 9.0 TransAccess 200 Mux 8.1

Node Operations and Maintenance Guide, Section 7: Software UpgradesNode Software Upgrade Process


Node Software Upgrade Process

Complete the software upgrade procedures in the following order:

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 www.turinnetworks.com. 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

Table 7-28 Node Software Upgrade Process


1 Have you read through, and do you understand, all of the Before You Begin items?

Before You Begin, page 7-50

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.

TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Upgrade Server Software, page 2-33

4 Download the new node software to the TransNav server.


5 Download the software to the modules.


6 Activate the new software. Software Activation Process, page 7-61

7 The Node Software Upgrade Process is complete.

Chapter 2 Release 3.0.x TE-100 System Software UpgradeDownload 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.


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

Node Operations and Maintenance Guide, Section 7: Software UpgradesDownload Node Software to the TransNav Server— Solaris System


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.

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.


Step Procedure


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

Chapter 2 Release 3.0.x TE-100 System Software UpgradeDownload Node Software to the TransNav Server— Solaris System


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.


Step Procedure



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 7-58.

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

Chapter 2 Release 3.0.x TE-100 System Software UpgradeModule Software Download Set-up


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 10–20 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.

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 7-39

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.


Step Procedure

7



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.

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.

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.


Step Procedure

12

15b15a

Chapter 2 Release 3.0.x TE-100 System Software UpgradeSoftware Activation Process


Module Software Version Verification


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.


Step Procedure






2

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.



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.

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.

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


1 Did you complete the upgrade of TransNav EMS server and client software and download the node software to the TransNav server?

Section 2—Management Server Procedures, Chapter 1—“Server Administration Procedures,” Upgrade Server Software, page 2-13

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

Control Module Software Upgrade Activation, page 7-62

5 The Software Activation Process is complete. Continue to Step 7 of the Node Software Upgrade Process, page 7-54.

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.

Table 7-34 Activate Software— Control Module

Step Procedure


2 In Shelf View, select a control module and click the Config tab.

Chapter 2 Release 3.0.x TE-100 System Software UpgradeControl Module Software Upgrade Activation


3 Verify the Protection Status of the Active/Standby control module using the Card Configuration dialog box.

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 7-44

5 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 7-45

9 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.

Table 7-34 Activate Software— Control Module (continued)

Step Procedure

3



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.


Step Procedure

Chapter 2 Release 3.0.x TE-100 System Software UpgradeSpare Control Module Software Activation


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.

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.

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 7-61.


Step Procedure

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.

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.


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.



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

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).


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 7-64.

Table 7-35 Activate Software—Spare Control Modules (continued)

Step Procedure

Important: This procedure is service affecting.

Important: Turin recommends that if you expect to revert an entire node, call TAC for assistance.

Chapter 2 Release 3.0.x TE-100 System Software UpgradeSoftware Revert Procedure


Revert TransNav Management System Software

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):beginexec upgrade switch-to-stdby-load slot <slot#>Are you sure you want to execute this command?YES.endexec node restartAre 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.

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.




SECTION 8 HARDWARE UPGRADESSECTION 8

Contents

Chapter 1Replacing Existing Traverse Hardware

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Fan Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Software Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Electrostatic Discharge Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Traverse Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Replacement Module—Type and Software Version . . . . . . . . . . . . . . . . . . . . 8-5Preparing a Module for Removal and Replacement . . . . . . . . . . . . . . . . . . . . 8-7Remove a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Module Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10GCM Module Replacement as Standby— LED Indicators . . . . . . . . . . . . . . . 8-15Clean Fiber Optic MPX Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16Insert a Replacement Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20Replace the Front Inlet Fan Tray Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24Front Inlet Fan Tray Air Filter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25Replace the Traverse 600 Fan Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26Fan Assembly Air Filter Installation (Traverse 600) . . . . . . . . . . . . . . . . . . . . 8-28Replace the Fan Tray Module (legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29Fan Tray Air Filter Installation (legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32

Chapter 2Upgrade to a Traverse Front Inlet Fan Tray

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Precautions and Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38FIFT Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Check the New Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39

List of FiguresFigure 8-1 Card Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Figure 8-2 Equipment Mismatch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Figure 8-3 Module Tabs in the Unlocked Position . . . . . . . . . . . . . . . . . . . . . 8-9Figure 8-4 Fiber Optic Backplane Housing A and B. . . . . . . . . . . . . . . . . . . . 8-17

Node Operations and Maintenance Guide, Section 8 Hardware Upgrades


Figure 8-5 Traverse 600 Fiber Optic Backplane Housing A and B . . . . . . . . . 8-18Figure 8-6 Optical Module MPX Connector . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18Figure 8-7 Module Locking Tabs in the Unlocked Position . . . . . . . . . . . . . . . 8-21Figure 8-8 Traverse 1600 or Traverse 2000 Shelf with Guides . . . . . . . . . . . 8-22Figure 8-9 Traverse 600 Shelf with Guides . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22Figure 8-10 Module Tabs in the Locked Position . . . . . . . . . . . . . . . . . . . . . . . 8-23Figure 8-11 Front Inlet Fan Module Captive Fasteners . . . . . . . . . . . . . . . . . . 8-24Figure 8-12 Front Inlet Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25Figure 8-13 Fan Assembly Front Cover - Traverse 600 . . . . . . . . . . . . . . . . . . 8-26Figure 8-14 Traverse 600 Fan Assembly Installation . . . . . . . . . . . . . . . . . . . . 8-27Figure 8-15 Traverse 600 Fan Assembly Air Filter . . . . . . . . . . . . . . . . . . . . . . 8-28Figure 8-16 Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29Figure 8-17 Traverse 1600 Fan Tray Module Installation . . . . . . . . . . . . . . . . . 8-30Figure 8-18 Traverse 2000 Fan Tray Module Installation . . . . . . . . . . . . . . . . . 8-30Figure 8-19 Air Filter with Springs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Figure 8-20 Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33Figure 8-21 Air Filter with Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Figure 8-22 Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Figure 8-23 Existing Fan Tray Holder Back Panel . . . . . . . . . . . . . . . . . . . . . . 8-39

List of TablesTable 8-1 Module Software Version Number Verification . . . . . . . . . . . . . . . 8-4Table 8-2 Preparing a Module for Removal and Replacement . . . . . . . . . . . 8-7Table 8-3 Remove a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Table 8-4 Module Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Table 8-5 Redundancy Rules for GCM Types. . . . . . . . . . . . . . . . . . . . . . . . 8-14Table 8-6 Power and Active/Standby—All Modules . . . . . . . . . . . . . . . . . . . 8-15Table 8-7 Clean Cable and Module MPX Connectors. . . . . . . . . . . . . . . . . . 8-17Table 8-8 Insert a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21Table 8-9 Insert a Front Inlet Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24Table 8-10 Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000) . . . . . 8-25Table 8-11 Insert a Fan Module with Integral Fan Tray. . . . . . . . . . . . . . . . . . 8-26Table 8-12 Insert a Fan Assembly Air Filter (Traverse 600) . . . . . . . . . . . . . . 8-28Table 8-13 Insert a Fan Tray Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29Table 8-14 Fan Tray Air Filter (with springs) Installation (Traverse, legacy) . . 8-32Table 8-15 Fan Tray Air Filter (with handle) Installation . . . . . . . . . . . . . . . . . 8-34Table 8-16 Front Inlet Fan Tray Holder Upgrade Instructions . . . . . . . . . . . . . 8-38Table 8-17 New Fan Module Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39






SECTION 8HARDWARE UPGRADES

Chapter 1Replacing 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 2-19.

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesSoftware 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








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.

Chapter 1 Replacing Existing Traverse HardwareSoftware Compatibility


Node Operations and Maintenance Guide, Section 8: Hardware UpgradesSoftware Version Verification


Software Version Verification



Step Procedure






2

Chapter 1 Replacing Existing Traverse HardwareReplacement Module—Type and Software Version


Electrostatic Discharge Protection

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.

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesReplacement 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

Chapter 1 Replacing Existing Traverse HardwarePreparing 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.

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesPreparing a Module for Removal and Replacement


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 8-20

8 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.

Table 8-2 Preparing a Module for Removal and Replacement (continued)

Step Procedure

Chapter 1 Replacing Existing Traverse HardwareRemove 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.

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.

Locking Tabs inOpen Position

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesModule 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 TypeTraverse

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)


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■ E1

1–12 1–16 1–4 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 2000. This application has no DS3/E3 ECM requirement. One module protects all remaining adjacent modules.

Chapter 1 Replacing Existing Traverse HardwareModule Placement


■ EC-3/STM-1E 1–12 1–16 1–4 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 2-12.

Table 8-4 Module Placement Guidelines (continued)

Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s




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


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.

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.

■ OC-3/STM-1■ OC-12/STM-4■ OC-48/STM-16■ OC-48/STM-16 with VTX (legacy)

1–14 1–18 1-4 None


Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


Chapter 1 Replacing Existing Traverse HardwareModule Placement


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.

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 1–14 1–18 1-4 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.


Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


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.



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 | Universal1

1 GCM Enhanced or Universal environmental alarm function should not be used in this combination.

GCM Enhanced | Universal1 GCM

GCM Enhanced | Universal GCM Enhanced | Universal

GCM with OC-N/STM-N GCM with OC-N/STM-N

Chapter 1 Replacing Existing Traverse HardwareGCM 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

LEDRED 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.

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesClean 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.

Chapter 1 Replacing Existing Traverse HardwareClean 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.

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.

Housing A

Housing B

White StripeReference Markers

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesClean Fiber Optic MPX Connectors


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.

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).

Figure 8-6 Optical Module MPX Connector

Table 8-7 Clean Cable and Module MPX Connectors (continued)

Step Procedure

Housing A

Housing B

White StripeReference Markers

Dust Cap on MPX Connector

Chapter 1 Replacing Existing Traverse HardwareClean Fiber Optic MPX Connectors


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.

Table 8-7 Clean Cable and Module MPX Connectors (continued)

Step Procedure

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesInsert 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.

Chapter 1 Replacing Existing Traverse HardwareInsert a Replacement Module


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.

Figure 8-7 Module Locking Tabs in the Unlocked Position

Guide Pins

Locking Tabs in Open Position

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesInsert a Replacement Module


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.

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.

Figure 8-9 Traverse 600 Shelf with Guides

Table 8-8 Insert a Module (continued)

Step Procedure

Card Cage Guides for Module Alignment

Card Cage Guides for Module Alignment

Chapter 1 Replacing Existing Traverse HardwareInsert a Replacement Module


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.

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.

Table 8-8 Insert a Module (continued)

Step Procedure

Locking Tabs inClosed Position

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesReplace 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.

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).

Captive Fasteners

Chapter 1 Replacing Existing Traverse HardwareFront 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.

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.

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.

Table 8-10 Insert a Front Inlet Fan Air Filter (Traverse 1600 and 2000)

Step Procedure


Figure 8-12 Front Inlet Air Filter

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.


Pull Tab (top view)

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesReplace 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.


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.

Figure 8-13 Fan Assembly Front Cover - Traverse 600

2 Open the right-front fan assembly cover.

Captive Fasteners

Chapter 1 Replacing Existing Traverse HardwareReplace the Traverse 600 Fan Assembly


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.

Figure 8-14 Traverse 600 Fan Assembly Installation

4 Continue to the next procedure, Insert a Fan Assembly Air Filter (Traverse 600).

Table 8-11 Insert a Fan Module with Integral Fan Tray (continued)

Step Procedure

Traverse 600 Shelf

Fan Assembly

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesFan 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


Figure 8-15 Traverse 600 Fan Assembly Air Filter

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.


Pull Tab (top view)

Chapter 1 Replacing Existing Traverse HardwareReplace 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.


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.


2 Lower the fan tray holder front cover.

Captive Fasteners

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesReplace the Fan Tray Module (legacy)


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.

Figure 8-17 Traverse 1600 Fan Tray Module Installation

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.

Table 8-13 Insert a Fan Tray Module (continued)

Step Procedure

Fan Tray Module Connector

Fan Tray Holder Guides

Fan Tray Module Connector

Fan Tray Holder Guides

Chapter 1 Replacing Existing Traverse HardwareReplace the Fan Tray Module (legacy)


Node Operations and Maintenance Guide, Section 8: Hardware UpgradesFan 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


Step Procedure

1 Rotate the air filter pull-tabs out.

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.

Springs

Pull Tabs

Chapter 1 Replacing Existing Traverse HardwareFan Tray Air Filter Installation (legacy)




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.



Step Procedure

Captive Fasteners



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.

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.

Handle

Chapter 1 Replacing Existing Traverse HardwareFan Tray Air Filter Installation (legacy)




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.

Table 8-15 Fan Tray Air Filter (with handle) Installation (continued)

Step Procedure

Captive Fasteners




SECTION 8HARDWARE UPGRADES

Chapter 2Upgrade to a Traverse Front Inlet Fan Tray

Introduction 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

Precautions and Assumptions

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.

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesRequired Equipment and Tools



The following equipment and tools are required for this upgrade:■ Front inlet fan tray holder■ Front inlet fan module■ Air filter1

■ 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:

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.

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 7-8.

8 The Front Inlet Fan Tray Holder Upgrade Instructions are complete.

Chapter 2 Upgrade to a Traverse Front Inlet Fan TrayCheck 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).

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.

Front

Power Cable Cover

Node Operations and Maintenance Guide, Section 8: Hardware UpgradesCheck the New Fan Module



SECTION 9 APPENDICESSECTION 9

Contents

Appendix AModule Placement Planning and Guidelines

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Module Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Traverse 1600 Module Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7Traverse 2000 Module Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12Traverse 600 Module Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17

Appendix BTraverse SNMP v1/v2c Agent and MIBs

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21Supported Traverse SNMP MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21Configure the Traverse SNMP Agent Parameters from TransNav . . . . . . . . . 9-22Location of SNMP MIB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23

List of FiguresFigure 9-1 Admin Menu—SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . 9-22Figure 9-2 Node SNMP Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . 9-22

List of TablesTable 9-1 Module Placement Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Table 9-2 Redundancy Rules for GCM Types . . . . . . . . . . . . . . . . . . . . . . . 9-6Table 9-3 Traverse 1600 Module Placement Guidelines . . . . . . . . . . . . . . . 9-7Table 9-4 Traverse 2000 Module Placement Guidelines . . . . . . . . . . . . . . . 9-12Table 9-5 Traverse 600 Module Placement Guidelines . . . . . . . . . . . . . . . . 9-17

Node Operations and Maintenance Guide, Section 9 Appendices



SECTION 9APPENDICES

Appendix AModule 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

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

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).


Node Operations and Maintenance Guide, Section 9: AppendicesModule 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 TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


■ 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)



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■ E1


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 2000. This application has no DS3/E3 ECM requirement. One module protects all remaining adjacent modules.

Appendix A Module Placement Planning and GuidelinesModule Placement Guidelines


■ EC-3/STM-1E 1–12 1–16 1–4 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 2-12.


Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s




Ethernet (Next Generation)—

NGE and NGE Plus:■ GbE [LX, SX] plus 10/100BaseTX

Combo [CEP]■ GbE TX plus GbE [LX or SX] plus


NGE only:■ GbE CWDM plus 10/100BaseTX

Combo■ GbE SX plus GbE CWDM plus

10/100BaseTX Combo


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.

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.

■ OC-3/STM-1■ OC-12/STM-4■ OC-48/STM-16■ OC-48/STM-16 with VTX (legacy)

1–14 1–18 1-4 None


Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


Appendix A Module Placement Planning and GuidelinesModule Placement Guidelines


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.

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 1–14 1–18 1-4 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.


Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


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.




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 | Universal1

1 GCM Enhanced or Universal environmental alarm function should not be used in this combination.

GCM Enhanced | Universal1 GCM

GCM Enhanced | Universal GCM Enhanced | Universal

GCM with OC-N/STM-N GCM with OC-N/STM-N

Appendix AM

odule Placement Planning and G

uidelinesTraverse 1600 M

odule Placement

Release O

PS3.1.xTurin N

etworks

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 TypeTraverse 1600 Slot Numbers

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

GCM S/A S/A

GCM

Enhanced GCM1

GCM OC-12/STM-41

GCM OC-48/STM-161

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

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

Node O


uide, Section9: Appendices

Traverse 1600 Module Placem

ent

Page 9-8Turin N

etworks

Release OPS3.1.x


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 O W O W O W O W O W O W

Table 9-3 Traverse 1600 Module Placement Guidelines (continued)


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Appendix AM



odule Placement

Release O

PS3.1.xTurin N

etworks

Page 9-9

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


■ 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 W/P W/P W/P W/P W/P W/P W/P W/P W/P W

ETHERNET unprotected with a 2-slot 10/100BaseT ECM







W W W W W W W W W W W W



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Node O




ent

Page 9-10Turin N

etworks

Release OPS3.1.x

ETHERNET unprotected with a 2-slot Ethernet (Protection) ECM







O W/O W/O W/O W/O W/O W/O W/O W/O W/O W/O W

TDM 1:2 equipment protection with the corresponding ECM

■ DS1 ■ DS3/E3/EC-1 CC ■ DS3/EC-1 Transmux■ E1

W W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W

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 W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P


■ DS3/E3/EC-1 CC ■ DS3/EC-1 Transmux■ E1

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

TDM unprotected with the corresponding ECM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Appendix AM



odule Placement

Release O

PS3.1.xTurin N

etworks

Page 9-11

■ DS1, ■ E1

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



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 VTX2 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

VT/TU 5G Switch W W W W W W W W W W W W W W

GCM with optics plus VTX2 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.



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Node O




ent

Page 9-12Turin N

etworks

Release OPS3.1.x




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.



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

GCM S/A S/A

GCM

Enhanced GCM1

GCM OC-12/STM-41

GCM OC-48/STM-161



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 O W/O

P/W/O

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/O/W/P

P/W/O/W

W/P/W/O

O/W/P/W

W/P

P/W

W


Appendix AM



odule Placement

Release O

PS3.1.xTurin N

etworks

Page 9-13

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/O/W

W/P/O

O/W/P

P/O/W

W/P

W


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

O P/O W/P

O/W


EC-3/STM-1E O O W O O W O O W O O W O O W


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.)







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

W/P

W




1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Node O




ent

Page 9-14Turin N

etworks

Release OPS3.1.x







W W W W W W W W W W W W W W W W








O W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W

TDM 1:2 equipment protection with corresponding ECM


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

W/P

W



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Appendix AM



odule Placement

Release O

PS3.1.xTurin N

etworks

Page 9-15



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

W/P

W/P


■ DS3/E3/EC-1 CC ■ DS3/EC-1 Transmux■ E1

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

W/P/O

W/P/O

W/P/O

W/P/O


■ DS1 ■ E1

W W W W W W W W W W W W W W W W



O W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W


■ 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/O

W/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 with 1:1 Equipment Protection

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

W/P

W/P

W/P

W/P

GCM with optics plus VTX2 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

W/P

W/P

W/P

W/P

VT/VC Switching unprotected



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Node O




ent

Page 9-16Turin N

etworks

Release OPS3.1.x

VT/TU 5G Switch without Equipment Protection

W W W W W W W W W W W W W W W W W W

GCM with optics plus VTX2 W W W W W W W W W W W W W W W W W W


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.



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

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.

Appendix AM



odule Placement

Release O

PS3.1.xTurin N

etworks

Page 9-17




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.



1 2 3 4 5 6

GCM S/A S/A

GCM

Enhanced GCM1

GCM OC-12/STM-41

GCM OC-48/STM-161



W W W W

OC-192/STM-64 (Note: Not available on the Traverse 600.)


EC-3/STM-1E O W P W/


EC-3/STM-1E O P/O W/P W


Node O




ent

Page 9-18Turin N

etworks

Release OPS3.1.x

EC-3/STM-1E O P W O


EC-3/STM-1E O O W/O W


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

P W/P W/P W



[CEP]


W W W W




1 2 3 4 5 6

Appendix AM



odule Placement

Release O

PS3.1.xTurin N

etworks

Page 9-19


[CEP]


O W/O W/O W

TDM 1:2 equipment protection with the corresponding ECM


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


■ DS1 ■ E1

W W W W



O W/O W/O W



1 2 3 4 5 6

Node O




ent

Page 9-20Turin N

etworks

Release OPS3.1.x

TDM unprotected with a 3-slot DS3/E3 ECM (Note: the module placement restriction is due to the electrical connector module.)


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 VTX2 W/P W/P W/P W/P

VT/VC Switching without Equipment Protection

VT/TU 5G Switch W W W W

OC-48/STM-16 with VTX W W W W


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.



1 2 3 4 5 6

SECTION 9APPENDICES

Appendix BTraverse SNMP v1/v2c Agent and MIBs

Introduction 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,

Supported Traverse SNMP MIBs

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.


Node Operations and Maintenance Guide, Section 9: AppendicesConfigure 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 ID1: Displays the user-defined node name entered during node commissioning.

Node IP1: Displays the node IP address entered during node commissioning.

1 Set through the CLI during node commissioning.


Appendix B Traverse SNMP v1/v2c Agent and MIBsLocation 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.


Node Operations and Maintenance Guide, Section 9: AppendicesLocation of SNMP MIB File


Release OPS3.1.x Turin Networks Index-1

INDEX

Numerics1:1 equipment protection

module placement, 9-11:2 equipment protection

module placement, 9-11:N equipment protection

module placement, 9-110/100BaseTX

precaution statementmodule placement, 8-20, 9-1

10/100BaseTX portperformance monitoring, 2-59

AAccess Identifier (AID)

test access, 5-2, 5-5ACO

alarm cutoff, 1-20ACO_CLEAR

clear alarm cutoff, 1-20Activate software

protected modules, 7-30unprotected 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-64Activation type, 7-31Active Hop, 1-11, 1-14, 2-11, 2-13Administrative state

card or port, 4-18ADMINTASK

Administrative task, 1-20AID, see Access Identifier (AID)Air filters

cooling function, 6-2replacement, 6-7

AIRCONDair contitioning system failed, 1-20

AIRDRYRair dryer fail, 1-20

AIS-LDS port alarm, 1-20

AIS-PDS port alarm, 1-21

AIS-SAlarm indication signal Service, 1-21

AIS-VDS port alarm, 1-21

AIS-VCsdh port alarm, 1-22

Alarm and eventdefault severity levels, 1-1, 1-19

Alarm indication signal secondsDS1 port, 2-18E1 port, 2-37

Alarm managementcustomization, 1-6

Alarm profilecreation, 1-7DS1 port, 1-8DS3 port, 1-8DS3�EC3 port, 1-8E1 port, 1-8E3 port, 1-8eos ctp, 1-8eos port, 1-8GbE port, 1-8lag, 1-8Mux, 1-8probable cause, 1-6sdh eos ctp, 1-8sdh eos port, 1-8sdh high order path, 1-8sdh low order path, 1-8SDH port, 1-8server, 1-8shelf, 1-8SONET port, 1-8sonet sts, 1-8sonet vt, 1-8synchronize, 1-9

Alarm reporting hierarchy, 1-6Alarms

ACO, 1-20ACO (shelf), 1-20ACO_CLEAR, 1-20ACO_CLEAR (shelf), 1-20ADMINTASK, 1-20AIRCOND, 1-20AIRCOND (shelf), 1-20AIRDRYR, 1-20AIRDRYR (shelf), 1-20AIS-L (DS port), 1-20AIS-L (port, shelf), 1-20AIS-P (DS port), 1-21AIS-P (port), 1-21AIS-V (DS port), 1-21

Index

Index-2 Turin Networks Release OPS3.1.x

AIS-VC (port), 1-22AIS-VC (sdh port), 1-22ALS, 1-22ALS (port), 1-22ALS-TX-OFF, 1-22ALS-TX-OFF (port), 1-22APSAISCLEAR, 1-23APS-AIS-P, 1-22APSB (port), 1-23APSBF (port), 1-23APSCFGMIS (port), 1-23APSCM (MSP) (port), 1-23APSDICLEAR, 1-25APSIMP (MSP) (port), 1-23APSINC (MSP) (port), 1-24APSLOP, 1-24APSLOPCLEAR, 1-24APS-LOP-P, 1-22APSLOSCLEAR, 1-24APSMM (port), 1-24APSPATHCLEAR, 1-24APSPDI, 1-25APSREL (MSP) (shelf), 1-25APSREL (shelf), 1-25APS-SDBER-P, 1-22APSSDCLEAR, 1-25APS-SFBER-P

APS-SFBER-P, 1-22APSUNEQCLEAR, 1-25APS-UNEQ-P, 1-23APSWTR (MSP) (shelf), 1-26APSWTR (shelf), 1-26AU-AIS (optical port), 1-26AU-AIS (port), 1-26AU-LOP (port), 1-26AU-LOP (SDH port), 1-26AUTHFAIL, 1-26automatic protection switching (APS), 1-5AUTOPRV, 1-26AUTO-TX-ON, 1-27AUTO-TX-ON (port), 1-27BADPKTRX, 1-27BATDSCHRG (shelf), 1-27BATTERY (shelf), 1-27BERSD-L (EC-1 port), 1-28BERSD-L (port, shelf), 1-28BERSD-P (EC-1 port), 1-29BERSD-P (port), 1-29BERSD-V (DS1 port), 1-30BERSD-V (port), 1-30BERSD-VC (port), 1-30BERSD-VC (sdh port), 1-30BERSF-L (EC-1 port), 1-31

BERSF-L (port, shelf), 1-31BERSF-P (EC-1 port), 1-32BERSF-P (port), 1-32BERSF-V (DS1 port), 1-33BERSF-V (port, shelf), 1-33BERSF-VC (port), 1-33BERSF-VC (sdh port), 1-33BITSA-FRC, 1-33BITSA-FRC (shelf), 1-33BITSA-LOCK, 1-34BITSA-LOCK (shelf), 1-34BITSA-MAN, 1-34BITSA-MAN (shelf), 1-34BITSB-FRC, 1-34BITSB-FRC (shelf), 1-34BITSB-LOCK, 1-34BITSB-LOCK (shelf), 1-34BITSB-MAN, 1-34BITSB-MAN (shelf), 1-34BITSGEN, 1-34BITSRBOC, 1-34BLSR_NOT_SYNC (server), 1-34BLSR_SYNC_UNKNOWN, 1-34BLSR_SYNC_UNKNOWN (server), 1-34BOARDFAIL, 1-34BOARDFAIL (ta200), 1-34BPSIG, 1-35BPSIG (shelf), 1-35categories of, 1-2CFGERR, 1-35CLEAR (shelf), 1-35CLFAIL, 1-35CLFAIL (shelf), 1-35CLFAN, 1-35CLFAN (shelf), 1-35CLRLOOP (all ports), 1-35CLRLOOP (shelf), 1-35COM (server), 1-35COM (ta200), 1-35COM (te50), 1-35CONTROL, 1-36CONTROL (te50), 1-36CTS, 1-36CTS (te50), 1-36DBCRPT (server), 1-37DBCRPT (shelf), 1-37DBFAIL (server), 1-37DBFAIL (shelf), 1-37DBMIS (server, shelf), 1-37DBRED (server, shelf), 1-37DBSIGN (port, server, shelf), 1-38DCCFAIL (EC-1 port), 1-38DCCFAIL (port), 1-38

Index


default severities, 4-2default severity levels, 1-19DS1 AIS (DS1 port), 1-39DS1 LOF (DS1 port), 1-39DS1 LOS (DS1 port), 1-39DS1 RAI (DS1 port), 1-40DS1AIS (port), 1-39DS1LOF (port), 1-39DS1LOS (port), 1-39DS1RAI (port), 1-40DS3 AIS (DS port), 1-40DS3 RAI (DS3 port), 1-40DS3AIS (port), 1-40DS3RAI (port), 1-40DSR (te50), 1-40DTR (te50), 1-40E1 AIS (E1 port), 1-40E1 LOM CAS (E1 port), 1-40E1 LOM CRC (E1 port), 1-40E1 RAI (E1 port), 1-41E1AIS (port), 1-40E1LOMCAS (port), 1-40E1LOMCRC (port), 1-40E1RAI (port), 1-41E3 AIS (E3 port), 1-41E3 AIS (port), 1-41E3 RAI (E3 port), 1-41E3 RAI (port), 1-41EFMFAIL (shelf), 1-41ENGINE (shelf), 1-41ENGOPRG (shelf), 1-41EQCOMM (shelf), 1-41EQFAIL (server), 1-42EQINV (shelf), 1-41EQLOCK (shelf), 1-42EQMIS (shelf), 1-42EQPT (server, shelf), 1-42EQRMV (shelf), 1-43ERFI-V (DS1 port), 1-43ERFI-V (port), 1-43EXER_SWITCH (shelf), 1-43EXPLGS (shelf), 1-43EXT2-REF1-ALM, 1-44EXTA-REF1-ALM, 1-43EXTA-REF1-ALM (shelf), 1-43EXTA-REF2-ALM, 1-43EXTA-REF2-ALM (shelf), 1-43EXTA-REF3-ALM, 1-44EXTA-REF3-ALM (shelf), 1-44EXTA-REF4-ALM, 1-44EXTA-REF4-ALM (shelf), 1-44EXTB-REF1-ALM (shelf), 1-44EXTB-REF2-ALM, 1-44

EXTB-REF2-ALM (shelf), 1-44EXTB-REF3-ALM, 1-44EXTB-REF3-ALM (shelf), 1-44EXTB-REF4-ALM, 1-44EXTB-REF4-ALM (shelf), 1-44FANCOMM (shelf), 1-45FANCOND (shelf), 1-45FANFLTR (shelf), 1-45FANRMV (shelf), 1-45FEP, 1-45FILE_UPLOAD (shelf), 1-45filtering, 1-17FIRDETR (shelf), 1-45FIRE (shelf), 1-45FLOOD (shelf), 1-45FLOW-DEGRADED (port), 1-46FLOW-LEARNED (port), 1-46FLOWS-UNLEARNED (port), 1-46FLOW-UNPROTECTED (port), 1-46FOPR (eos), 1-46FOPR (port), 1-46FOPT (eos), 1-46FOPT (port), 1-46FORCE_ONLINE (ta200), 1-47FORCED (shelf), 1-47FORCED_ON_EAST (shelf), 1-48FORCED_ON_PROT (shelf), 1-47FORCED_ON_SECT1 (shelf), 1-47FORCED_ON_SECT2 (shelf), 1-48FORCED_ON_WEST (shelf), 1-48FORCED_ON_WORK (shelf), 1-48FUSE (shelf), 1-48GENFAIL (shelf), 1-48GFPLOF, 1-48GFPLOF (shelf), 1-48GIDERR (shelf), 1-49GIDM (eos), 1-49GIDM (port), 1-49H4-LOM, 1-49H4-LOM (port), 1-49HIAIR (shelf), 1-49HIGHHMD (shelf), 1-49HIHUM (shelf), 1-49HITEMP (shelf), 1-50HIWTR (shelf), 1-50HP-BERSD (optical port), 1-50HP-BERSD (port), 1-50HP-BERSF (optical port), 1-51HP-BERSF (port), 1-51HP-LOM, 1-51HP-LOM (port), 1-51HP-MND, 1-51HP-MND (port), 1-51

Index


HP-PLM (optical port), 1-51HP-PLM (port), 1-51HP-RDI (optical port), 1-52HP-RDI (port), 1-52HP-RFI (optical port), 1-52HP-RFI (port), 1-52HP-RFICON (port), 1-52HP-RFIPAY (port), 1-52HP-RFISVR (port), 1-52HP-SQM, 1-51HP-SQM (port), 1-51HP-TIM (optical port), 1-52HP-TIM (port), 1-52HP-UNEQ (optical port), 1-53HP-UNEQ (port), 1-53HWFAULT (shelf), 1-53IDLE (DS port), 1-53IDLE (port), 1-53INCOMPATSW (server), 1-53INCOMPATSW (server, shelf), 1-53INCOMPATSW (shelf), 1-53INDICATION (te50), 1-54INTRUDER (shelf), 1-53KBYTE (optical port), 1-54KBYTE (port), 1-54LBC, 1-57LBC (port, shelf), 1-57LCAS-REM (vc bundle), 1-57LCAS-RES (vc bundle), 1-57LEAK (shelf), 1-57LFD (eos), 1-57LFD (port), 1-57LINK_FRCD_DIS (Ethernet port), 1-58LINK_FRCD_DIS (port), 1-58LINKFAIL (Ethernet port), 1-58LINKFAIL (port), 1-58LO_LBC (SFP optical port), 1-60LO_OPR (SFP optical port), 1-60LO_OPT (SFP optical port), 1-60LO_TEMP (SFP optical port), 1-60LO_VCC (SFP optical port), 1-60LOA (eos), 1-60LOA (port), 1-60LOCK_WORK1 (shelf), 1-61, 1-62, 1-63LOCK_WORK10 (shelf), 1-61LOCK_WORK11 (shelf), 1-61LOCK_WORK12 (shelf), 1-61LOCK_WORK13 (shelf), 1-61LOCK_WORK14 (shelf), 1-62LOCK_WORK2 (shelf), 1-62LOCK_WORK3 (shelf), 1-62LOCK_WORK4 (shelf), 1-62LOCK_WORK5 (shelf), 1-62

LOCK_WORK6 (shelf), 1-62LOCK_WORK7 (shelf), 1-63LOCK_WORK8 (shelf), 1-63LOCK_WORK9 (shelf), 1-63LOCKOUT (shelf), 1-60LOCKOUT-LPS (shelf), 1-61LOF (DS port), 1-64LOF (port, shelf), 1-64LOG (eos), 1-64LOG (port), 1-64LOGINFAIL, 1-65LOGINFAIL (server, shelf), 1-65LOGINSUCC, 1-65LOGINSUCC (server, shelf), 1-65LOGINTERM, 1-65LOGINTERM (server, shelf), 1-65LOL (te50), 1-65LO-LBC (port), 1-60LOM-P (eos), 1-65LOM-P (port), 1-65LOM-V (eos), 1-65LOM-V (port), 1-65LO-OPR (port), 1-60LO-OPT (port), 1-60LOP-P (DS port), 1-66LOP-P (port), 1-66LOS (DS port), 1-67LOS (port, shelf), 1-67LO-TEMP (port), 1-60LO-VCC (port), 1-60LP-BERSD (optical port), 1-68LP-BERSF (optical port), 1-68LP-LOM (eos), 1-69LP-MND (eos), 1-69LP-PLM (optical port), 1-70LP-RDI (optical port), 1-70LP-RFI (optical port), 1-70LP-RFICON (optical port), 1-70LP-RFIPAY (optical port), 1-70LP-RFISVR (optical port), 1-70LP-SQM (eos), 1-71LP-TIM (optical port), 1-71LP-UNEQ (optical port), 1-71MAN_ON_PROT (shelf), 1-72MAN_ON_WORK, 1-72MAN-TX-OFF, 1-72MAN-TX-ON, 1-72MANUAL (shelf), 1-72MND-P (eos), 1-72MND-V (eos), 1-72MS-AIS (optical port), 1-73MS-BERSD (optical port), 1-73MS-BERSF (optical port), 1-74

Index


MS-RDI (optical port), 1-74MSSP_NOT_SYNC, 1-74multiplex section protection (MSP), 1-5NETSYNC (server), 1-75NODEEQMIS (server), 1-75NODEMIS (optical port), 1-75NODESYNC (server), 1-76NO-REMOTE-LCAS, 1-76NPM (eos), 1-76OPR, 1-76OPT, 1-76OVERTEMP (shelf), 1-77OVERVOLTAGE_A (shelf), 1-77OVERVOLTAGE_B (shelf), 1-77PCASQLCH (optical port), 1-77PDI-n, 1-78PDI-n (n, 1-77PDI-n (n>4), 1-78PLC (lag), 1-78PLCR (eos), 1-78PLCT (eos), 1-78PLINESQL (optical port), 1-79PLM (DS port), 1-79PLM-V (DS port), 1-79PLM-V (optical port), 1-79PLM-V (shelf), 1-79PLM-VC (optical port), 1-79PMCFG (all ports), 1-80PMDATALOST, 1-80PUMPFAIL (shelf), 1-80PWFAIL-A (shelf), 1-80PWFAIL-B (shelf), 1-80QEFAIL (shelf), 1-80recommended actions, 1-19RECTFAIL (shelf), 1-80RECTHIGH (shelf), 1-81RECTLOW (shelf), 1-81REMOTE-LINKFAIL, 1-81reporting, 1-2RESOURCE_MISMATCH (shelf), 1-81RFICON (DS port), 1-84RFICON (port), 1-84RFICON-V (DS port), 1-84RFICON-V (port), 1-84RFICON-VC (port), 1-84RFI-L (EC-1 port), 1-82RFI-L (port), 1-82RFI-P (EC-1 port), 1-82RFI-P (port), 1-82RFIPAY (DS port), 1-85RFIPAY (port), 1-85RFIPAY-V (DS port), 1-85RFIPAY-V (port), 1-85RFIPAY-VC (optical port), 1-85

RFISVR (DS port), 1-86RFISVR (port), 1-86RFISVR-V (DS port), 1-86RFISVR-V (port), 1-86RFISVR-VC (port), 1-86RFI-V (DS1 port), 1-83RFI-V (port), 1-83RFI-VC (optical port), 1-83RS-TIM, 1-87SERVER_LOGINFAIL, 1-87SETOPER, 1-87severity levels

default, 1-1SFO (optical port), 1-87SFO (port alarm), 1-87SFPMIS, 1-88SFPRMV, 1-88SHELFMIS (server), 1-88SMOKE (shelf), 1-88SQLCHTBL (optical port), 1-88SQM, 1-88SQM-P (eos), 1-88SQM-V (eos), 1-89SSF, 1-89StickyMode, 1-18SVC_ERROR, 1-89SW_UPG (shelf), 1-90SWCRPT, 1-89SWERR (all ports), 1-89SWITCH (Ethernet port), 1-89SWITCH (shelf), 1-90SWITCH_TO_PROT (shelf), 1-89SWITCH_TO_SECT1 (shelf), 1-89SWITCH_TO_SECT2 (shelf), 1-90SWMIS (all ports), 1-90SYNCFAIL (optical port), 1-90SYSREF, 1-90TA200_COM, 1-91TCA (port), 1-92TEMP, 1-92TEMPCRIT (shelf), 1-92TEMPWARN (shelf), 1-92TIM (port), 1-92TIMEDOUT (shelf), 1-93TIMEOUTWARN (shelf), 1-93TIM-P (port), 1-92TIM-S (port), 1-93TIM-V (port), 1-93TIU-V (port), 1-93TIU-V (shelf), 1-93TLC (lag), 1-94TLCR (eos), 1-94TLCT (eos), 1-94TOOMANYEVENTS (server), 1-94

Index


TOPOMIS (optical port), 1-94TOXIC (shelf), 1-94TSSALM (shelf), 1-97TSS-EXTA-OOB-A, 1-94TSS-EXTA-OOB-B, 1-94TSS-EXTB-OOB-A, 1-94TSS-EXTB-OOB-B, 1-94TSS-FRC (shelf), 1-95TSS-FREERUN-GCMA (shelf), 1-95TSS-FREERUN-GCMB (shelf), 1-95TSSGEN (shelf), 1-97TSS-HOLDOVER-GCMA, 1-95TSS-HOLDOVER-GCMB, 1-95TSS-LINE1-OOB-GCMA, 1-95, 1-96TSS-LINE1-OOB-GCMB, 1-95TSS-LINE2-OOB-GCMA, 1-95TSS-LINE2-OOB-GCMB, 1-95TSS-LINE3-OOB-GCMA, 1-96TSS-LINE3-OOB-GCMB, 1-96TSS-LINE4-OOB-GCMB, 1-96TSS-LOCK (shelf), 1-96TSS-MAN (shelf), 1-96TSSREF, 1-97TSS-REF1-ALM (shelf), 1-96TSS-REF2-ALM (shelf), 1-96TSS-REF3-ALM (shelf), 1-96TSS-REF4-ALM (shelf), 1-97TSS-REFL-GCMA (shelf), 1-97TSS-REFL-GCMB (shelf), 1-97TSS-REFS (shelf), 1-97TSSSETS (shelf), 1-97TSS-SSM (shelf), 1-97TU-AIS (optical port), 1-21, 1-98TU-LOP (optical port), 1-98types of, 1-2UNDERVOLTAGE_A (shelf), 1-99UNDERVOLTAGE_B (shelf), 1-99UNEQ, 1-99UNEQ-P (port), 1-99UNEQ-V (port, shelf), 1-100UNEQ-VC (optical port), 1-100UP (all ports), 1-100VCC, 1-100VENTFAIL (shelf), 1-100viewing, 1-6WARMREBOOT, 1-100X86_ABORT, 1-101X86_CRC, 1-101XPT-FAIL-RX, 1-101XPT-FAIL-TX, 1-101XPTRX (lag), 1-101XPTTX (lag), 1-101

AlarmsAIS-S, 1-21

ALSalarm, 1-22

ALS-TX-OFFalarm, 1-22

APS-AIS, 1-22APSAISCLEAR, 1-23APSDICLEAR, 1-25APSLOPCLEAR, 1-24APS-LOP-P, 1-22APSLOS, 1-24APSLOSCLEAR, 1-24APSPATHCLEAR, 1-24APSPDI, 1-25APSREL

shelf alarm, 1-25APS-SDBER-P, 1-22APSSDCLEAR, 1-25APSUNEQCLEAR, 1-25APS-UNEQ-P, 1-23APSWTR

shelf alarm, 1-26AU-AIS

optical port alarm, 1-26AU-LOP

SDH port alarm, 1-26AUTHFAIL, 1-26AUTOPRV, 1-26AUTO-TX-ON

alarm, 1-27

BBackground block error ratio

E1 port, 2-37E3 port, 2-40

Background block errorsE1 port, 2-37E1 port, far end, 2-38E3 port, 2-39LO VC3 path, 2-42LO VC3 path, far end, 2-44SDH port–MS, 2-46SDH port–MS, far end, 2-49SDH port–RS, 2-45VC11 path, 2-50VC11 path, far end, 2-52VC12 path, 2-50VC12 path, far end, 2-52VC3 path, 2-42VC3 path, far end, 2-44VC4 path, 2-42VC4 path, far end, 2-44

Backward compatibilitysoftware, 7-4, 7-51, 8-2

Index


BADPKTRX, 1-27Base path, 7-13, 7-58BATDSCHRG

shelf alarm, 1-27BATTERY

shelf alarm, 1-27BERSD-L

EC-1 port alarm, 1-28BERSD-P

EC-1 port alarm, 1-29BERSD-V

DS1 port alarm, 1-30BERSD-VC

sdh port alarm, 1-30BERSF-L

EC-1 port alarm, 1-31BERSF-P

EC-1 port alarm, 1-32BERSF-V

DS1 port alarm, 1-33BERSF-VC

sdh port alarm, 1-33BITSA-FRC, 1-33BITSA-LOCK, 1-34BITSA-MAN, 1-34BITSB-FRC, 1-34BITSB-LOCK, 1-34BITSB-MAN, 1-34BITSGEN, 1-34BITSRBOC, 1-34BLSR_NOT_SYNC

server alarm, 1-34BLSR_SYNC_UNKNOWN, 1-34BOARDFAIL, 1-34BPSIG, 1-35Bulk service activation

unavailable resources, 1-108

CCaptive fasteners

PDAP-2S, 6-14PDAP-4S, 6-19

Circuit breakerPDAP-2S

replacing, 6-11Circuit breaker, PDAP-2S

toggle switch, 6-12Cleaning MPX connectors, 8-16CLEAR

shelf alarm, 1-35Clear

activation time, 7-24, 7-64download time, 7-16, 7-60

CLFAIL, 1-35CLFAN, 1-35CLI node commands

exec node database backup, 6-24CLRLOOP

all ports alarm, 1-35Coding violations

DS1 port, 2-18, 2-19DS3 port, 2-21

(CBit), 2-22(CBit), far end, 2-23(PBit), 2-21

E1 port, 2-36E3 port, 2-39Line

EC1 port, 2-24Line, far-end

EC1 port, 2-25Section

EC1 port, 2-24SONET line, 2-27SONET line, far end, 2-29SONET path, 2-31SONET path, far end, 2-32SONET section, 2-27SONET VT path, 2-33SONET VT path, far end, 2-34

COMserver alarm, 1-35

Compatibilityalarms, 7-4, 7-51, 8-2product compatibility matrix, 7-4, 7-51, 8-2replacement modules, 7-4, 7-51, 8-2software, 7-4, 7-51, 8-2software version, 7-4, 7-51, 8-2

Connectors, cleaning, 8-16CONTROL, 1-36Controlled slip seconds

DS1 port, 2-19DS1 port, far end, 2-20

Creatingalarm profiles, 1-7PM templates, 2-2

Critical alarm, see LEDsCTS, 1-36Current SW version, 7-23, 7-24, 7-31, 7-63, 7-64CVFE

coding violations, far end–line, 2-25

DDBCRPT

server alarm, 1-37DBFAIL

Index


shelf alarm, 1-37DCCFAIL

EC-1 port alarm, 1-38Deactivate Ethernet Services, 7-43Default alarm and event severity levels, 1-1, 1-19Default severities, alarms, 4-2Default values, 6-24DFAD

dual facility access digroup, test access, 5-2Diagnostics

environmental alarm conditions, incorrect, 4-1loopback tests, 4-9transmit and receive signal levels, 4-3, 4-7

Disabled operational statecard or port, 4-18

Downloadarchive

from Infocenter, 7-3, 7-10, 7-50, 7-54time by module, 7-14, 7-59

DS1facility loopback, 4-10, 4-11port alarm profile, 1-8terminal loopback tests, 4-10

DS1 AISDS1 port alarm, 1-39

DS1 LOFDS1 port alarm, 1-39

DS1 LOSDS1 port alarm, 1-39

DS1 portalarm profile, 1-8facility loopback tests, 4-10performance monitoring, 2-18

FE CCS_P, 2-20FE ES_L, 2-19FE ES_P, 2-19FE FC_P, 2-20FE SEF_P, 2-20FE SES_P, 2-20FE UAS_P, 2-20NE AISS_P, 2-18NE CSS_P, 2-19NE CV_L, 2-18NE CV_P, 2-18, 2-19NE ES_L, 2-18NE ES_P, 2-18NE FC_L, 2-19NE LOSS_L, 2-18NE SAS_P, 2-19NE SES_L, 2-18NE SES_P, 2-18NE UAS_P, 2-19

DS1 RAI

DS1 port alarm, 1-40DS3

facility loopback, 4-10, 4-11terminal loopback tests, 4-10

DS3 AISDS port alarm, 1-40

DS3 CCfacility loopback tests, 4-10, 4-11

DS3 portalarm profile, 1-8performance monitoring, 2-21, 2-36

FE CVC-P (CBit), 2-23FE ESC-P (CBit), 2-23FE FC-P (PBit), 2-23FE SESC-P (CBit), 2-23FE UASC-P (CBit), 2-23NE CVC-P (CBit), 2-22NE CV-L, 2-21NE CV-P (PBit), 2-21NE ESC-P (CBit), 2-22NE ES-L, 2-21NE ES-P (PBit), 2-21NE FC-P (PBit), 2-22NE SESC-P (CBit), 2-22NE SES-L, 2-21NE SES-P (PBit), 2-21NE UASC-P (CBit), 2-22NE UAS-P (PBit), 2-21

DS3 RAIDS3 port alarm, 1-40

DS3 TMUXfacility loopback tests, 4-10

DS3/E3/EC-112-port, 8-10, 9-224-port, 8-10, 9-2module placement, 8-10, 9-2

DS3/EC-1Transmux, 8-10, 9-2

DS3/EC-1 portfacility loopback tests, 4-10

DS3�EC3 portalarm profile, 1-8

DSC CCterminal loopback tests, 4-10

DSC TMUX terminal loopback tests, 4-10Dual facility access digroup

DFAD test access point, 5-2

EE1 AIS

E1 port alarm, 1-40E1 LOM CAS

E1 port alarm, 1-40

Index


E1 LOM CRCE1 port alarm, 1-40

E1 portalarm profile, 1-8facility loopback, 4-12facility loopback tests, 4-10, 4-12performance monitoring, 2-36

FE BBE_P, 2-38FE ES_L, 2-38FE ES_P, 2-38FE FC_P, 2-38FE SES_P, 2-38FE UAS_P, 2-38NE AISS_P, 2-37NE BBE_P, 2-37NE BBER_P, 2-37NE CV_L, 2-36NE EB_P, 2-36, 2-38NE ES_L, 2-36NE ES_P, 2-37NE ESR_P, 2-37NE FAS_L, 2-36NE FC_L, 2-36NE LOSS_L, 2-36NE SES_L, 2-36NE SES_P, 2-37NE SESR_P, 2-37NE UAS_P, 2-37

terminal loopback, 4-12E1 RAI

E1 port alarm, 1-41E3 AIS

E3 port alarm, 1-41E3 port

alarm profile, 1-8facility loopback, 4-12facility loopback tests, 4-10, 4-12performance monitoring, 2-39

FE EB_P, 2-40, 2-41FE ES_P, 2-40FE SES_P, 2-40FE UAS_P, 2-41NE BBE_P, 2-39NE BBER_P, 2-40NE CV_L, 2-39NE EB_P, 2-39NE ES_L, 2-39NE ES_P, 2-39NE ESR_P, 2-39NE FC_P, 2-40NE SES_L, 2-39NE SES_P, 2-39

NE SESR_P, 2-40NE UAS_P, 2-39

terminal loopback, 4-12E3 RAI

E3 port alarm, 1-41EAM, see Environmental Alarm ModuleEC1 port

facility loopback tests, 4-10performance monitoring, 2-24terminal loopback tests, 4-10

EC-3terminal loopback tests, 4-11

EC-3�STM-1E1

1 protection with ECM, 9-7, 9-8, 9-12, 9-13, 9-17

2 protection with 4-slot ECM, 9-7, 9-12, 9-17unprotected with 3-slot ECM, 9-8, 9-13, 9-18unprotected with 4-slot ECM, 9-8, 9-13, 9-18

EFMFAILshelf alarm, 1-41

Electrical and optical signals, monitoring, 2-1Electrostatic discharge protection (ESD), 8-5EMS

service error codes, 1-105, 1-107software compatibility, 8-2

EMSImux, 2-8

Enabled operational statecard or port, 4-18

Environmental Alarm Module (EAM)guides, 6-21plastic standoffreplacing, 6-20

Environmental alarmsobserving incorrect conditions, 4-1symptom, incorrect input/output, 4-2

EOSperformance monitoring

GFP FCS DISCARDS, 2-56RX BROADCAST, 2-56RX BYTES, 2-56, 2-57RX FRAMES, 2-56RX MTU DISCARDS, 2-57RX MULTICAST, 2-56RX UNICAST, 2-56TX BROADCAST, 2-56TX BYTES, 2-56TX DISCARDS, 2-56TX FRAMES, 2-56TX UNICAST, 2-56

EOS ctp

Index


alarm profile, 1-8EOS port

alarm profile, 1-8EQCOMM

shelf alarm, 1-41EQFAIL

server alarm, 1-42EQINV

shelf alarm, 1-41EQLOCK

shelf alarm, 1-42EQMIS

shelf alarm, 1-42EQRMV

shelf alarm, 1-43Equipped state

card or port, 4-18ERFI-V

DS1 port alarm, 1-43Error codes

EMS, 1-105, 1-107Errored blocks

E1 port, 2-36, 2-38E3 port, 2-39E3 port, far end, 2-40LO VC3 path, 2-42LO VC3 path, far end, 2-44SDH port–MS, 2-46SDH port–MS, far end, 2-48SDH port–RS, 2-45VC11 path, 2-50VC11 path, far end, 2-52VC12 path, 2-50VC12 path, far end, 2-52VC3 path, 2-42VC3 path, far end, 2-44VC4 path, 2-42VC4 path, far end, 2-44

Errored secondsDS1 port, 2-18DS1 port, far end, 2-19DS3 port, 2-21DS3 port (CBit), 2-22DS3 port (CBit), far end, 2-23DS3 port (PBit), 2-21E1 port, 2-36, 2-37E1 port, far end, 2-38E3 port, 2-39E3 port, far end, 2-40Line, EC1 port, 2-24Line, far end

EC1 port, 2-25LO VC3 path, 2-42

LO VC3 path, far end, 2-44Ratio

E1 port, 2-37E3 port, 2-39

SDH port–MS, 2-46SDH port–MS, far end, 2-48SDH port–RS, 2-45Section

EC1 port, 2-25SONET line, 2-28SONET line, far end, 2-29SONET path, 2-31SONET path, far end, 2-32SONET section, 2-27SONET VT path, 2-33SONET VT path, far end, 2-34VC11 path, 2-50VC11 path, far end, 2-52VC12 path, 2-50VC12 path, far end, 2-52VC3 path, 2-42VC3 path, far end, 2-44VC4 path, 2-42VC4 path, far end, 2-44

ESFEerrored seconds

far end, line, 2-25Ethernet

module placement, 9-7, 9-8, 9-9, 9-12, 9-13, 9-17, 9-18

10�100BaseTX-inclusive, 9-1performance monitoring

RX, 2-60RX ALIGNMENT ERR, 2-61RX BROADCAST, 2-60RX BYTES, 2-61, 2-62RX BYTES BAD, 2-61RX DELAY DISCARDS, 2-60RX DISCARDS, 2-60RX FCS ERR, 2-61RX FRAMES, 2-60RX MTU DISCARDS, 2-60RX MULTICAST, 2-60RX NO DELIMITER, 2-60RX PAUSE, 2-61RX PKT > 1518, 2-60RX PKT 1024-1518, 2-60RX PKT 128-255, 2-60RX PKT 256-511, 2-60RX PKT 512-1023, 2-60RX PKT 64, 2-60RX PKT 65-127, 2-60RX UNICAST, 2-59

Index


TX BROADCAST, 2-59TX BYTES, 2-61, 2-62TX BYTES BAD, 2-61TX DEFERRED FRAMES (10/100 only), 2-61TX DISCARDS, 2-60TX EXCESSIVE COLL (10/00 only), 2-61TX FRAMES, 2-59TX LATE COLL (T10/00 only), 2-61TX MULTICAST, 2-56, 2-59TX MULTIPLE COLL (10/100 only), 2-61TX PAUSE, 2-61TX PKT > 1518, 2-59TX PKT 1024-1518, 2-59TX PKT 128-255, 2-59TX PKT 256-511, 2-59TX PKT 512-1023, 2-59TX PKT 64, 2-59TX PKT 65-127, 2-59TX SINGLE COLL (10/100 only), 2-61TX UNICAST, 2-59

performance parameters, 2-55protection with Ethernet (protection) ECM, 9-9unprotected with 10/100BaseT ECM, 9-9, 9-13, 9-

18unprotected with Ethernet (protection) ECM, 9-10,

9-14, 9-18Ethernet port

link integrity status, 1-58terminal loopbacks, 4-13

Eventcategories of, 1-2default severity levels, 1-19LCAS remove, 1-57LCAS restore, 1-57logs, 1-2recommended actions, 1-19reporting, 1-2severity levels

default, 1-1SYSREF, 1-90TSSREF, 1-97types of, 1-2

Eventslogs, 1-2

EXER_SWITCHshelf alarm, 1-43

EXT2-REF1-ALMreference timing alarm, 1-44

EXTA-REF1-ALMreference timing alarm, 1-43

EXTA-REF2-ALMreference timing alarm, 1-43

EXTA-REF3-ALM

reference timing alarm, 1-44EXTA-REF4-ALM

reference timing alarm, 1-44EXTB-REF2-ALM



reference timing alarm, 1-44

FFacility access digroup

FAD test access point, 5-2Facility payload loopback

DS1, 4-10, 4-11DS3, 4-10, 4-11E1, 4-12E3, 4-12

FADfacility access digroup, test access, 5-2

Failure countLine, far end

EC1 port, 2-26Failure counts

DS1 port, 2-19DS1 port, far end, 2-20DS3 port (PBit), 2-22DS3 port (PBit), far end, 2-23E1 port, far end, 2-38E1port, 2-36E3 port, 2-40E3 port, far end, 2-41Line

EC1 port, 2-24LO VC3 path, 2-43LO VC3 path, far end, 2-44SDH port–MS, 2-47SDH port–MS, far end, 2-49SONET line, 2-28SONET line, far end, 2-30VC11 path, 2-51VC11 path, far end, 2-53VC12 path, 2-51VC12 path, far end, 2-53VC3 path, 2-43VC3 path, far end, 2-44VC4 path, 2-43VC4 path, far end, 2-44

Fanfan tray and module, 6-1maintenance

air filter, 6-2front inlet fan tray module, 6-1

Index


speeds, 6-2tray air filters, 6-2tray holder LEDs, 3-4, 3-5tray module

replacing, 8-24, 8-26, 8-29upgrade to FIFT, 8-37

Fan tray air filtersreplacing, 6-7

FANCOMMshelf alarm, 1-45

FANCONDshelf alarm, 1-45

FANFLTRshelf alarm, 1-45

FANRMVshelf alarm, 1-45

Fast EthernetLEDs, 3-10

Fault managementcustomization, 1-6viewing alarms, 1-15

FCfailure count, line, 2-24

FCFEfailure count, line, 2-26

FEPfar-end protection failure alarm, 1-45

Fiber opticcabling, 8-17, 8-18

Filtering alarms, 1-17Filters

air, 6-2FIRE

shelf alarm, 1-45FLOOD

shelf alarm, 1-45FOPR

eos alarm, 1-46FOPT

eos alarm, 1-46Force switch, 7-28, 7-32FORCED

shelf alarm, 1-47FORCED_ON_PROT

shelf alarm, 1-47FORCED_ON_SECT1

shelf alarm, 1-47FORCED_ON_SECT2

shelf alarm, 1-48FORCED_ON_WORK

shelf alarm, 1-48Frame alignment signal

E1 port, 2-36

FusePDAP-2S

replacing, 6-10, 6-12PDAP-4S

replacing, 6-18

GGbE LX-VC

LEDs, 3-10GbE port

alarm profile, 1-8performance monitoring, 2-59

GCMalarm LEDs, 3-8module placement, 9-7status

active�standby, 7-21, 7-63protection, 7-21, 7-63

GCM (General control module)with VTX/VCX, 8-10, 9-2

General Control ModulePower On Self Test (POST), 4-21

Generating PM reports, 2-15GENFAIL

shelf alarm, 1-48GFP FCS DISCARDS

EOS port, 2-56GFPLOF

VC bundle alarm, 1-48GIDM

eos alarm, 1-49GMT

fusereplacing, PDAP-2S, 6-12replacing, PDAP-4S, 6-18

GMT fuse blockPDAP-2S, 6-12PDAP-4S, 6-18

GuidesEAM, 6-21PDAP-2S LED module, 6-15PDAP-4S LED module, 6-19

HH4-LOM

alarm, 1-49Hierarchy

alarms, 1-6HIGHHMD

shelf alarm, 1-49HP_BERSD

optical port alarm, 1-50

Index


HP_BERSFoptical port alarm, 1-51

HP_PLMoptical port alarm, 1-51

HP_RDIoptical port alarm, 1-52

HP_RFIoptical port alarm, 1-52

HP_TIMoptical port alarm, 1-52

HP_UNEQoptical port alarm, 1-53

HP-LOMalarm, 1-51

HP-MNDalarm, 1-51

HP-SQOMalarm, 1-51

Iical, 1-20IDLE

DS port alarm, 1-53INCOMPATSW

server alarm, 1-53shelf alarm, 1-53

Initiate upgrade, 7-15, 7-59Inserting modules, 8-5Integrity status

Ethernet, 1-58Intervals

performance monitoring, 2-9, 2-12IP address

node-ip, 9-22

KKBYTE

optical port alarm, 1-54

LLAG

alarm profile, 1-8LBC

alarm, 1-57LCAS remove

EOS event, 1-57LCAS restore

EOS event, 1-57LEAK

shelf alarm, 1-57LEDs

electrical module port, 3-9

fan tray holder, 3-4, 3-5Fast Ethernet, 3-10GbE LX-VC, 3-10GCM alarm, 3-8GCM power and standby, 8-15general control module (GCM), 3-8module, 3-6module status, 3-1optical modules, 3-10PDAP, 3-2PDAP-2S, 3-2power and standby, 3-7

LFDeos alarm, 1-57

Light emitting diodes, see LEDsLine

CVFE (coding violations, far end), 2-25FC (failure count), 2-24FC (failure counts, far end), 2-26SESFE (severely errored seconds, far end), 2-25UASFE (unavailable seconds, far end), 2-26

Link integrity, see Integrity statusLINK_FRCD_DIS

Ethernet port alarm, 1-58LINKFAIL

Ethernet port alarm, 1-58integrity status

LO VC3 pathperformance monitoring

BBE-LP, 2-42EB-LP, 2-42ES-LP, 2-42FC-LP, 2-43FE BBE-LP, 2-44FE EB-LP, 2-44FE ES-LP, 2-44FE FC-LP, 2-44FE SES-LP, 2-44FE UAS-LP, 2-44NPJC-DET-LP, 2-43NPJC-GEN-LP, 2-43PPJC-DET-LP, 2-43PPJC-GEN-LP, 2-43SES-LP, 2-42UAS-LP, 2-42

LO_LBCSFP optical port alarm, 1-60

LO_OPRSFP optical port alarm, 1-60

LO_OPTSFP optical port alarm, 1-60

LO_TEMPSFP optical port alarm, 1-60

Index


LO_VCCSFP optical port alarm, 1-60

LOAeos alarm, 1-60

LOCK_WORK1shelf alarm, 1-61, 1-62, 1-63

Locked administrative statecard or port, 4-18

LOCKOUTshelf alarm, 1-60

LOFDS port alarm, 1-64

LOGeos alarm, 1-64

Loginmanagement system, 7-51

LOGINFAILserver alarm, 1-65shelf alarm, 1-65

LOGINSUCCserver alarm, 1-65shelf alarm, 1-65

LOGINTERMserver alarm, 1-65shelf alarm, 1-65

LOM-Peos alarm, 1-65

LOM-Veos alarm, 1-65

Loopback tests, 4-9description, 4-9DS1 facility, 4-10DS1 terminal, 4-10DS3 CC facility, 4-10, 4-11DS3 CC terminal, 4-10DS3 terminal, 4-10DS3 TMUX facility, 4-10DS3 TMUX terminal, 4-10DS3/EC-1 facility, 4-10E1 facility, 4-10, 4-12E1 terminal, 4-12E3 facility, 4-10, 4-12E3 terminal, 4-12EC1 facility, 4-10EC1 terminal, 4-10EC-3 terminal, 4-11Ethernet terminal, 4-13SDH facility, 4-15SDH terminal, 4-15SONET facility, 4-15SONET terminal, 4-15STM-1E terminal, 4-11

LOP-PDS port alarm, 1-66

LOSDS port alarm, 1-67

Loss of signal secondsDS1 port, 2-18E1 port, 2-36

LP_BERSDoptical port alarm, 1-68

LP_BERSFoptical port alarm, 1-68

LP_PLMoptical port alarm, 1-70

LP_RDIoptical port alarm, 1-70

LP_RFIoptical port alarm, 1-70

LP_TIMoptical port alarm, 1-71

LP_UNEQoptical port alarm, 1-71

LP-LMDeos alarm, 1-69

LP-LOMeos alarm, 1-69

LP-RFICONoptical port alarm, 1-70

LP-RFIPAYoptical port alarm, 1-70

LP-RFISVRoptical port alarm, 1-70

LP-SQMeos alarm, 1-71

MMaintenance

alarm boardPDAP-4S, 6-19

fan tray air filter, 6-2fan tray air filter replacement, 6-7fuse

PDAP-2S, 6-10, 6-12PDAP-4S, 6-18

PDAP-2Sreplace circuit breaker, 6-11

PDAP-2S alarm board, 6-14PDAP-4S TPA fuse, 6-16replacing EAM, 6-20routine, shelf, 6-1

Major alarm, see LEDsMAN_ON_PROT

shelf alarm, 1-72MAN_ON_WORK

shelf alarm, 1-72Management System

Index


event logs, 1-2verify software version, 7-18, 7-61, 8-4

MAN-TX-OFFalarm, 1-72

MAN-TX-ONalarm, 1-72

MANUALshelf alarm, 1-72

Measuredsupply voltage

SFP optic port, 2-26temperature

SFP optic port, 2-26TX bias current

SFP optic port, 2-26TX input power

SFP optic port, 2-26TX output power

SFP optic port, 2-26Minor alarm, see LEDsMND-P

eos alarm, 1-72MND-V

eos alarm, 1-72Module

placementguidelines, 8-10, 9-2

Module download times, 7-14, 7-59Module software version compatibility, 7-4, 7-51, 8-2Modules

inserting, 8-5power and standby LEDs, 3-7prepare for removal and replacement, 8-7replacing, 8-1, 8-37

Monitoring, performance, 2-1MPX connector

cleaning material, 7-3, 8-5MPX connectors

cleaning, 8-16inspection, 8-16

MS-AISoptical port alarm, 1-73

MS-BERSDoptical port alarm, 1-73

MS-BERSFoptical port alarm, 1-74

MS-RDIoptical port alarm, 1-74

MSSP_NOT_SYNCMS-SP Ring out of sync alarm, 1-74

Multiplex sectionperformance monitoring

BBE-MS, 2-46

EB-MS, 2-46ES-MS, 2-46FC-MS, 2-47FE BBE-MS, 2-49FE EB-MS, 2-48FE ES-MS, 2-48FE FC-MS, 2-49FE UAS-MS, 2-48PSCP-MS, 2-47PSCW-MS, 2-47PSDP-MS, 2-47PSDW-MS, 2-47SES-MS, 2-46UAS-MS, 2-46

Muxalarm profile, 1-8EMSI, 2-8

NNegative pointer justifications detected

LO VC3 path, 2-43VC11 path, 2-51VC12 path, 2-51VC3 path, 2-43VC4 path, 2-43

Negative pointer justifications generatedLO VC3 path, 2-43VC11 path, 2-51VC12 path, 2-51VC3 path, 2-43VC4 path, 2-43

NETSYNCserver alarm, 1-75

NodeID, 9-22IP, 9-22IP address, 9-22parameters

node ID (node name), 9-22node IP, 9-22

NODEEQMISserver alarm, 1-75

NODEMISoptical port, 1-75optical port alarm, 1-75

NODESYNCserver alarm, 1-76

Non-equipped statecard or port, 4-18

NO-REMOTE-LCASremote peer LCAS status alarm, 1-76

NPMeos alarm, 1-76

Index


OOFGERR, 1-35Operational state

card or port, 4-18OPR

alarm, 1-76OPT

alarm, 1-76Optic

modules, 8-12, 9-4Optical power specifications, 4-4Optics

module placement, 9-7OVERTEMP

shelf alarm, 1-77OVERVOLTAGE_A

shelf alarm, 1-77OVERVOLTAGE_B

shelf alarm, 1-77

PPassword, 7-13, 7-58PCASQLCH

optical port alarm, 1-77PDAP-15A

replace GMT fuse, 6-10PDAP-2S

also see Power Distribution and Alarm Panelcaptive fasteners, 6-14circuit breaker, 6-12GMT fuse block, 6-12LED

module, 6-15LEDs, 3-2replace circuit breaker, 6-11replacing

alarm board, 6-14PDAP-4S

also see Power Distribution and Alarm Panelcaptive fasteners, 6-19GMT fuse block, 6-18LED module guides, 6-19LEDs, 3-2replacing

alarm board, 6-19TPA fuse, 6-16

TPA fuse, 6-17Performance monitoring, 2-1

10/100BaseTX port, 2-59DS1 port, 2-18DS3 port, 2-21, 2-36E1 port, 2-36E3 port, 2-39

EC1 port, 2-24GbE port, 2-59generating reports, 2-15intervals, 2-9, 2-12printing PM data, 2-10, 2-12refreshing PM values, 2-10, 2-12reports, generating, 2-15resetting PM counters, 2-10, 2-12samples, 2-9, 2-12saving PM data, 2-10, 2-12SDH path, 2-41, 2-50SDH port, 2-45services (SONET STS), 2-31services (SONET VT), 2-33SONET port, 2-27templates, 2-2viewing port PM data, 2-9viewing service PM data, 2-11, 2-13

Performance parametersEthernet, 2-55SDH, 2-35SONET, 2-17

Periodic conditions, monitoring, 2-1Plastic standoff, see Environmental Alarm ModulePLC

lag alarm, 1-78PLCR

eos alarm, 1-78PLCT

eos alarm, 1-78PLINESQL

optical port alarm, 1-79PLM

DS port alarm, 1-79PLM-V

DS port alarm, 1-79optical port alarm, 1-79shelf alarm, 1-79

PLM-VCoptical port alarm, 1-79

PMalso see Performance monitoringtemplate

synchronize, 2-4timing

refresh time, 2-8samples, 2-8

PMCFGall ports alarm, 1-80

PMDATALOSTshelf alarm, 1-80

Pointer justifications differenceVC11 path, 2-52VC12 path, 2-52

Index


Pointer justifications seconds detectedVC11 path, 2-51VC12 path, 2-51

Pointer justifications seconds generatedVC11 path, 2-52VC12 path, 2-52

Portnumber

TransAccess 200 Mux, 9-23Positive pointer justifications detected

LO VC3 path, 2-43VC11 path, 2-51VC12 path, 2-51VC3 path, 2-43VC4 path, 2-43

Positive pointer justifications generatedLO VC3 path, 2-43VC11 path, 2-51VC12 path, 2-51VC3 path, 2-43VC4 path, 2-43

Power and standby LEDs, 3-7Power Distribution and Alarm Panel

alarm boardreplacing, 6-14

LEDs, 3-2replacing

circuit board, 6-19circuit breaker, 6-11TPA fuse, 6-16

Power On Self Test (POST) for GCM, 4-21Printing PM data, 2-10, 2-12Probable Cause, 1-17Problems, see SymptomsProcedures

air filter replacement, 6-7cleaning MPX connectors, 8-16Fan Assembly (6-slot) Air Filter Installation, 8-28fan tray air filter installation, 8-25, 8-32fan tray module installation, 8-24, 8-26, 8-29inserting modules, 8-5software upgrade activate GCM, 7-45upgrade to FIFT (fan), 8-37

Procedures (GUI)activate software

protected modules, 7-30unprotected modules, 7-33

assign port alarm profile, 1-9assigning a port PM template, 2-5assigning a service path alarm profile, 1-10assigning a service PM template, 2-6assigning a subport alarm profile, 1-10assigning a subport PM template, 2-6assigning a T100 PM template, 2-8

clear protection switch, 7-41creating a PM template, 2-2new alarm profile, 1-7perform a forced switch, 7-38perform a manual switch, 7-40PM report generation, 2-16software 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-12suppressing service CTP path alarms, 1-13viewing alarms, 1-15viewing port or subport PM data, 2-9viewing service PM data, 2-11

Protected modules, 7-30Protection

electrical modules, 8-10, 8-11, 9-2, 9-3Ethernet, 8-12, 9-4

Protection groups, 7-30Protection switch

forced, 7-28, 7-32release, 7-28, 7-32

Protection switch countprotecting

SDH port–MS, 2-47SONET line, 2-29

workingSDH port–MS, 2-47SONET line, 2-28

Protection switch durationprotecting

SDH port–MS, 2-47SONET line, 2-29

workingSDH port–MS, 2-47SONET line, 2-29

PUMPFAILshelf alarm, 1-80

PWFAIL-Ashelf alarm, 1-80

PWFAIL-Bshelf alarm, 1-80

QQEFAIL

shelf alarm, 1-80

RRead community

TransAccess 200 Mux, 9-23Recommended Actions

Index


alarms and events, 1-19non-alarmed symptoms, 4-2

RECTFAILshelf alarm, 1-80

RECTHIGHshelf alarm, 1-81

RECTLOWshelf alarm, 1-81

Refreshing PM values, 2-10, 2-12Regenerator section

performance monitoringBBE-RS, 2-45EB-RS, 2-45ES-RS, 2-45SES-RS, 2-45

Release path, 7-15, 7-59Release protection switch, 7-28, 7-32Remote test access

test access, 5-3Remote test unit

test access, 5-2REMOTE-LINKFAIL

alarm, 1-81Replacement modules, 7-4, 7-51, 8-2Replacing

alarm boardPDAP-2S, 6-14PDAP-4S, 6-19

circuit breakerPDAP-2S, 6-11

EAM circuit board, 6-20fan tray module, 8-24, 8-26, 8-29fuse

PDAP-2S, 6-10, 6-12PDAP-4S, 6-18

GCMpower and standby LEDs, 8-15

modules, 8-1, 8-5, 8-37required equipment, 7-3, 7-50, 8-5, 8-38

Reporting alarms and events, 1-2Reports, PM, 2-15Resetting PM counters, 2-10, 2-12RESOURCE_MISMATCH

shelf alarm, 1-81RFICON

DS port alarm, 1-84RFICON-V

DS port alarm, 1-84RFI-L

EC-1 port alarm, 1-82RFI-P

EC-1 port alarm, 1-82RFIPAY

DS port alarm, 1-85RFIPAY-V

DS port alarm, 1-85RFIPAY-VC

optical port alarm, 1-85RFISVR

DS port alarm, 1-86RFISVR-V

DS port alarm, 1-86RFI-V

DS1 port alarm, 1-83RFI-VC

optical port alarm, 1-83RS-TIM

trace identifier mismatch alarm, 1-87RTU

remote test unit, 5-2RX

Ethernet port, 2-60RX ALIGNMENT ERR

Ethernet port, 2-61RX BROADCAST

EOS port, 2-56Ethernet port, 2-60

RX BYTESEOS port, 2-56, 2-57Ethernet port, 2-61, 2-62

RX BYTES BADEthernet port, 2-61

RX DELAY DISCARDSEthernet port, 2-60

RX DISCARDSEthernet port, 2-60

RX FCS ERREthernet port, 2-61

RX FRAMESEOS port, 2-56Ethernet port, 2-60

RX MTU DISCARDSEOS port, 2-57Ethernet port, 2-60

RX MULTICASTEOS port, 2-56Ethernet port, 2-60

RX NO DELIMITEREthernet port, 2-60

RX PAUSEEthernet port, 2-61

RX PKT > 1518Ethernet port, 2-60

RX PKT 1024-1518Ethernet port, 2-60

RX PKT 128-255

Index


Ethernet port, 2-60RX PKT 256-511


Ethernet port, 2-60RX PKT 64


Ethernet port, 2-60RX UNICAST


SSamples in performance monitoring, 2-9, 2-12Saving PM data, 2-10, 2-12SDH

HO pathalarm profile, 1-8

LO pathalarm profile, 1-8

pathperformance monitoring, 2-41, 2-50

performance parameters, 2-35port

alarm profile, 1-8SDH port

facility loopback tests, 4-15performance monitoring, 2-45

BBE-MS, 2-46BBE-RS, 2-45EB-MS, 2-46EB-RS, 2-45ES-MS, 2-46ES-RS, 2-45FC-MS, 2-47FE BBE-MS, 2-49FE EB-MS, 2-48FE ES-MS, 2-48FE FC-MS, 2-49FE UAS-MS, 2-48PSCP-MS, 2-47PSCW-MS, 2-47PSDP-MS, 2-47PSDW-MS, 2-47SES-MS, 2-46SES-RS, 2-45UAS-MS, 2-46

terminal loopback tests, 4-15Self test, GCM, see General Control Module, Power On

Self TestServer alarm profile, 1-8Server IP address, 7-13, 7-58

SERVER_LOGINFAILserver alarm, 1-87

Service(SONET STS)

performance monitoring, 2-31(SONET VT)

performance monitoring, 2-33Service (SONET VT) performance monitoring, 2-33Service error codes

EMS, 1-107system resources unavailable (1035), 1-108

SESFEseverely errored seconds, far end–line, 2-25

SETOPERshelf alarm, 1-87

Severely errored framesalarm indication signal seconds

DS1 port, 2-19Severely errored framing seconds

DS1 port, far end, 2-20Section

EC1 port, 2-25SONET section, 2-27

Severely errored secondsDS1 port, 2-18DS1 port, far end, 2-20DS3 port, 2-21DS3 port (CBit), 2-22DS3 port (CBit), far end, 2-23DS3 port (PBit), 2-21E1 port, 2-36, 2-37E1 port, far end, 2-38E3 port, 2-39E3 port, far end, 2-40Line

EC1 port, 2-24Line, far end

EC1 port, 2-25LO VC3 path, 2-42LO VC3 path, far end, 2-44Ratio

E1 port, 2-37E3 port, 2-40

SDH port–MS, 2-46SDH port–MS, far end, 2-48SDH port–RS, 2-45Section

EC1 port, 2-25SONET line, 2-28SONET line, far end, 2-30SONET path, 2-31SONET path, far end, 2-32SONET section, 2-27

Index


SONET VT path, 2-33SONET VT path, far end, 2-34VC11 path, 2-50VC11 path, far end, 2-52VC12 path, 2-50VC12 path, far end, 2-52VC3 path, 2-42VC3 path, far end, 2-44VC4 path, 2-42VC4 path, far end, 2-44

SeverityNSA, 1-6, 1-17SA, 1-6, 1-17

Severity levelsalarms and events

default, 1-1defined, 1-5

Severity levels for alarms and eventsdefault, 1-19

SFODS port alarm, 1-87optical port alarm, 1-87

SFP optic portperformance monitoring

measured supply voltage, 2-26measured temperature, 2-26measured TX bias current, 2-26measured TX input power, 2-26measured TX output power, 2-26

SFPMISalarm, 1-88

SFPRMValarm, 1-88

Shelf alarm profile, 1-8SHELFMIS

server alarm, 1-88SMOKE

shelf alarm, 1-88SNMP

ems.mib, 9-23MIB, 9-23

SNMP, nodeconfiguration, 9-22node agent port 161, 9-22

Softwareactivation, 7-30compatibility, 7-4, 7-51, 8-2download

abort, 7-16, 7-60status, 7-16, 7-17, 7-60

download times, 7-14, 7-59upgrade, 7-1, 7-49

activate GCM, 7-21, 7-25, 7-35, 7-36, 7-62, 7-65

activate time, 7-30upgrade order, 7-30version number

verify, 7-18, 7-61, 8-4Software upgrade

activate GCM, 7-45activate time, 7-22, 7-24, 7-63, 7-64

Software versioncurrent, 7-18, 7-61, 8-4standby, 7-17, 7-60

SONETperformance parameters, 2-17port

alarm profile, 1-8STS

alarm profile, 1-8VT

alarm profile, 1-8SONET line

performance monitoringCV-L, 2-27ES-L, 2-28FC-L, 2-28FE CV-L, 2-29FE ES-L, 2-29FE FC-L, 2-30FE SES-L, 2-30FE UAS-L, 2-30PSCP-L, 2-29PSCW-L, 2-28PSDP-L, 2-29PSDW-L, 2-29SES-L, 2-28UAS-L, 2-28

SONET pathperformance monitoring

CV-P, 2-31ES-P, 2-31FE CV-P, 2-32FE ES-P, 2-32FE SES-P, 2-32FE UAS-P, 2-32SES-P, 2-31UAS-P, 2-31

SONET portfacility loopback tests, 4-15performance monitoring, 2-27terminal loopback tests, 4-15

SONET sectionperformance monitoring

CV-S, 2-27ES-S, 2-27SEFS-S, 2-27SES-S, 2-27

Index


SONET VT pathperformance monitoring

CV-V, 2-33ES-V, 2-33FE CV-V, 2-34FE ES-V, 2-34FE SES-V, 2-34FE UAS-V, 2-34SES-V, 2-33UAS-V, 2-33

Speedcooling fan, 6-2

SQLCHTBLoptical port alarm, 1-88

SQMethernet port alarm, 1-88

SQM-Peos alarm, 1-88

SQM-Veos alarm, 1-89

SSFserver signal fail alarm, 1-89

Standbyhop, 2-11module, 7-42

Statusactivation, 7-23, 7-63, 7-64activation time, 7-31GCM protection, 7-21, 7-63

StickyModealarms display, 1-18

STM-1Eterminal loopback tests, 4-11

SVC_ERRORshelf alarm, 1-89

SW_UPGshelf alarm, 1-90

SWCRPTshelf alarm, 1-89

SWERRall ports alarm, 1-89

SWITCHEthernet port alarm, 1-89shelf alarm, 1-90

SWITCH_TO_PROTshelf alarm, 1-89

SWITCH_TO_SECT1shelf alarm, 1-89

SWITCH_TO_SECT2shelf alarm, 1-90

SWMIS, 7-23, 7-25, 7-29, 7-64, 7-65all ports alarm, 1-90

Symptomsincorrect environmental alarms, 4-2recommended actions, 4-2

SYNCFAILoptical port alarm, 1-90

SYSREFsystem reference alarm, 1-90system reference event, 1-90

System resourcesunavailable, 1-108

System software upgrade statusABORTED, 7-16, 7-60FAILED, 7-16, 7-60INPROGRESS, 7-16, 7-60NONE, 7-16, 7-60OK, 7-16, 7-60

TTA200_COM

alarm, 1-91TAC, 5-2TAP (FAD or DFAD), 5-2TCA

port alarm, 1-92TEMP

alarm, 1-92TEMPCRIT

shelf alarm, 1-92Templates

performance monitoring, 2-2TEMPWARN

shelf alarm, 1-92Termination point

TP, test access, 5-2Test Access

ADM, 5-1AID, 5-2, 5-5cross-connect, 5-2DCS3/1, 5-1digital signals, 5-1DS1 module, 5-8DS3 module, 5-8DS3 transmux module, 5-8dual facility access digroup (DFAD), 5-2E1 module, 5-8facility access digroup (FAD), 5-2intrusive, 5-1management system, 5-8monitor, 5-9non-intrusive, 5-1per side split, 5-14point, 5-2remote test access, 5-3remote test unit (RTU), 5-2series split, 5-18termination point (TP), 5-2test system controller (TSC), 5-2, 5-25

Index


VCX component, 5-8VT/TU 5G switch, 5-8

Test system controllerTSC, 5-2, 5-25

Thresholdssetting for PM parameters, 2-4

TIMport alarm, 1-92

TIMEDOUTshelf alarm, 1-93

TIMEOUTWARNshelf alarm, 1-93

TIM-Pport alarm, 1-92

TIM-Sport alarm, 1-93

TIM-Vport alarm, 1-93

TIU-Vport alarm, 1-93shelf alarm, 1-93

TLClag alarm, 1-94

TLCReos alarm, 1-94

TLCTeos alarm, 1-94

Toggle switchPDAP-2S circuit breaker, 6-12

TOOMANYEVENTSserver alarm, 1-94

TOPOMISoptical port alarm, 1-94

TOXICshelf alarm, 1-94

TPtermination point, test access, 5-2

TPA fusePDAP-4S, 6-17

TransAccess 200 Muxport number, 9-23read community, 9-23write community, 9-23

Transmit and receive signal levels, 4-3, 4-7Transmux

DS3/EC-1, 8-10, 9-2Troubleshooting

error codes, 1-105loopback tests, 4-9transmit and receive signal levels, 4-3, 4-7

TSSALMshelf alarm, 1-97

TSS-EXTA-OOB-A

controller A EXT A out of band alarm, 1-94TSS-EXTA-OOB-B

controller B EXT A out of band alarm, 1-94TSS-EXTB-OOB-A

Controller A EXT B out of band alarm, 1-94TSS-EXTB-OOB-B

Controller B EXT B out of band alarm, 1-94TSS-FRC

shelf alarm, 1-95TSS-FREERUN-GCMA

shelf alarm, 1-95TSS-FREERUN-GCMB

shelf alarm, 1-95TSSGE

shelf alarm, 1-97TSS--HOLDOVER-GCMA

GCM A is in holdover state., 1-95TSS--HOLDOVER-GCMB

GCM B is in holdover state., 1-95TSS-LINE1-OOB-GCMA

GCM A line reference 1 out of band alarm, 1-95, 1-96

TSS-LINE1-OOB-GCMBGCM A line reference 1 out of band alarm, 1-95

TSS-LINE2-OOB-GCMAGCM A line reference 2 out of band alarm, 1-95

TSS-LINE2-OOB-GCMBGCM B line reference 2 out of band alarm, 1-95

TSS-LINE3-OOB-GCMAGCM A line reference 3 out of band alarm, 1-96



TSS-LOCKshelf alarm, 1-96

TSS-MANshelf alarm, 1-96

TSSREFtiming reference alarm, 1-97timing reference event, 1-97

TSS-REF1-ALMshelf alarm, 1-96




TSS-REFL-GCMAshelf alarm, 1-97

TSS-REFL-GCMBshelf alarm, 1-97

Index


TSS-REFSshelf alarm, 1-97

TSSSETSshelf alarm, 1-97

TSS-SSMshelf alarm, 1-97

TU-AISoptical port alarm, 1-21, 1-98

TU-LOPoptical port alarm, 1-98

TX BROADCASTEOS port, 2-56Ethernet port, 2-59

TX BYTESEOS port, 2-56Ethernet port, 2-61, 2-62

TX BYTES BADEthernet port, 2-61

TX DEFERRED FRAMESEthernet port (T10/00 only), 2-61

TX DISCARDSEOS port, 2-56Ethernet port, 2-60

TX EXCESSIVE COLLEthernet port (10/100 only), 2-61

TX FRAMESEOS port, 2-56Ethernet port, 2-59

TX LATE COLLEthernet port (10/100 only), 2-61

TX MULTICASTEthernet port, 2-56, 2-59

TX MULTIPLE COLLEthernet port (10/-100 only), 2-61

TX PAUSEEthernet port, 2-61

TX PKT > 1518Ethernet port, 2-59

TX PKT 1024-1518Ethernet port, 2-59




TX PKT 64Ethernet port, 2-59


TX SINGLE COLLEthernet port (10/00 only), 2-61

TX UNICAST


UUASFE

unavailable secondsfar end, line, 2-26

Unavailable secondsDS1 port, 2-19DS1 port, far end, 2-20DS3 port (CBit), 2-22DS3 port (CBit), far end, 2-23DS3 port (PBit), 2-21E1 port, 2-37E1 port, far end, 2-38E3 port, 2-39E3 port, far end, 2-41Line

EC1 port, 2-24Line, far-end

EC1 port, 2-26LO VC3 path, 2-42LO VC3 path, far end, 2-44SDH port–MS, 2-46SDH port–MS, far end, 2-48SONET line, 2-28SONET line, far end, 2-30SONET path, 2-31SONET path, far end, 2-32SONET VT path, 2-33SONET VT path, far end, 2-34VC11 path, 2-51VC11 path, far end, 2-53VC12 path, 2-51VC12 path, far end, 2-53VC3 path, 2-42VC3 path, far end, 2-44VC4 path, 2-42VC4 path, far end, 2-44

UNDERVOLTAGE_Ashelf alarm, 1-99

UNDERVOLTAGE_Bshelf alarm, 1-99

UNEQalarm, 1-99

UNEQ-Pport alarm, 1-99

UNEQ-Vport, shelf alarm, 1-100

UNEQ-VCoptical port alarm, 1-100

Unlocked administrative statecard or port, 4-18

Index


UPall ports alarm, 1-100

Upgrade type, 7-15, 7-59init, 7-15, 7-59

Upgrading software, 7-1, 7-49Username, 7-13, 7-58

VVC11 path

performance monitoringBBE-LP, 2-50EB-LP, 2-50ES-LP, 2-50FC-LP, 2-51FE BBE-LP, 2-52FE EB-LP, 2-52FE ES-LP, 2-52FE FC-LP, 2-53FE SES-LP, 2-52FE UAS-LP, 2-53NPJC-DET-LP, 2-51NPJC-GEN-LP, 2-51PJCD-LP, 2-52PJCS-DET-LP, 2-51PJCS-GEN-LP, 2-52PPJC-DET-LP, 2-51PPJC-GEN-LP, 2-51SES-LP, 2-50UAS-LP, 2-51

VC12 pathperformance monitoring

BBE-LP, 2-50EB-LP, 2-50ES-LP, 2-50FC-LP, 2-51FE BBE-LP, 2-52FE EB-LP, 2-52FE ES-LP, 2-52FE FC-LP, 2-53FE SES-LP, 2-52FE UAS-LP, 2-53NPJC-DET-LP, 2-51NPJC-GEN-LP, 2-51PJCD-LP, 2-52PJCS-DET-LP, 2-51PJCS-GEN-LP, 2-52PPJC-DET-LP, 2-51PPJC-GEN-LP, 2-51SES-LP, 2-50UAS-LP, 2-51


BBE-HP, 2-42EB-HP, 2-42

ES-HP, 2-42FC-HP, 2-43FE BBE-HP, 2-44FE EB-HP, 2-44FE ES-HP, 2-44FE FC-HP, 2-44FE SES-HP, 2-44FE UAS-HP, 2-44NPJC-DET-HP, 2-43NPJC-GEN-HP, 2-43PPJC-DET-HP, 2-43PPJC-GEN-HP, 2-43SES-HP, 2-42UAS-HP, 2-42


BBE-HP, 2-42EB-HP, 2-42ES-HP, 2-42FC-HP, 2-43FE BBE-HP, 2-44FE EB-HP, 2-44FE ES-HP, 2-44FE FC-HP, 2-44FE SES-HP, 2-44FE UAS-HP, 2-44NPJC-DET-HP, 2-43NPJC-GEN-HP, 2-43PPJC-DET-HP, 2-43PPJC-GEN-HP, 2-43SES-HP, 2-42UAS-HP, 2-42

VCCalarm, 1-100

VENTFAILshelf alarm, 1-100

Verifying software version, 7-18, 7-61, 8-4Viewing

alarms, 1-6Viewing alarms, 1-15

all nodes, 1-15module, 1-15one node, 1-15port, 1-15service CTP, 1-15

Viewing PM dataport, 2-9service, 2-11, 2-13

VT/TU Switchmodule placement, 8-13, 9-5

WWarm reboot

hitless software upgrade, 7-7

Index


WARMREBOOTwarm reboot alarm, 1-100

Warning alarm, see LEDsWrite community

TransAccess 200 Mux, 9-23

XX86_ABORT

ethernet encapsulation alarm, 1-101X86_CRC

ethernet encapsulation alarm, 1-101XPT-FAIL-RX

alarm, 1-101XPT-FAIL-TX

alarm, 1-101XPTRX

lag alarm, 1-101XPTTX

lag alarm, 1-101

Index


Visit our website at:www.turinnetworks.com

Release OPS3.1.xOperations Documentation800-0011-OPS31

www.turinnetworks.com

Documents

Node Operations and Maintenance · 2007-06-19 · CLI commands. TransNav Man-agement System TL1 Guide This document describes the syntax of the TL1 lan-guage in the TransNav environment