Turin Networks Inc.
Operations Documentation
Node Operations and
Maintenance Guide
Release OPS4.0.x
Publication Date: January 2008
Document Number: 800-0011-OPS40 Rev. A
FCC Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to
Part 15 of the FCC Rules. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the installation instructions may cause harmful interference to radio
communications.
Canadian Compliance
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment
Regulations. Cet appareil numérique de la classe A respects toutes les exigences du Règlement sur le
matériel brouilleur du Canada.
Japanese Compliance
This is a Class A product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio
disturbance may occur, in which case, the user may be required to take corrective actions.
International Declaration of Conformity
We, Turin Networks, Inc. declare under our sole responsibility that the Traverse platform (models: Traverse
2000, Traverse 1600, and Traverse 600) to which this declaration relates, is in conformity with the following
standards:
EMC Standards
EN55022
EN55024
CISPR-22
Safety Standards
EN60950
CSA 22.2 No. 60950, ASINZS 3260
IEC 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 © 2008 Turin Networks, Inc.
All rights reserved. This document contains proprietary and confidential information of Turin Networks,
Inc., and may not be used, reproduced, or distributed except as authorized by Turin Networks. No part of this
publication may be reproduced in any form or by any means or used to make any derivative work (such as
translation, transformation or adaptation) without written permission from Turin Networks, Inc.
Turin Networks reserves the right to revise this publication and to make changes in content from time to time
without obligation on the part of Turin Networks to provide notification of such revision or change. Turin
Networks may make improvements or changes in the product(s) described in this manual at any time.
Turin Networks Trademarks
Turin Networks, the Turin Networks logo, Traverse, TraverseEdge, TransAccess, TransNav, and Creating
The Broadband Edge are trademarks of Turin Networks, Inc. or its affiliates in the United States and other
countries. All other trademarks, service marks, product names, or brand names mentioned in this document
are the property of their respective owners.
Government Use
Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212
(Commercial Computer Software-Restricted Rights) and DFAR 227.7202 (Rights in Technical Data and
Computer Software), as applicable.
N ODE O PERATIONS
AND
M AINTENANCE G UIDE
Contents
About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Section 1 Fault Management
Chapter 1
Managing Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Chapter 2
Alarms, Events, and Recommended Actions . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Chapter 3
TransNav GUI Service Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-107
Section 2 Performance Monitoring
Chapter 1
Managing Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
SONET Performance Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
SDH Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4
Ethernet Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
2-19
2-39
2-61
Section 3 Equipment LED Status
Chapter 1
LEDs and Module Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Section 4 Diagnostics
Chapter 1
Diagnostics Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
Traverse Transmit and Receive Signal Levels . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
TraverseEdge 100 Transmit and Receive Signal Levels . . . . . . . . . . . . . . .
Chapter 4
Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5
Other Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1
4-3
4-7
4-11
4-21
Section 5 Test Access
Chapter 1
Traverse Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Chapter 2
Traverse Test Access Guidelines for the Spirent BRTU Interface . . . . . . . . 5-21
Section 6 Routine Maintenance
Chapter 1
Release OPS4.0.x
Turin Networks
Page i
DRAFT
Node Operations and Maintenance Guide
Routine Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Chapter 2
Node Database Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Section 7 Software Upgrades
Chapter 1
Release TR3.0.x Traverse Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . 7-1
Chapter 2
Release 3.0.x TE-100 System Software Upgrade . . . . . . . . . . . . . . . . . . . . . 7-49
Section 8 Hardware Upgrades
Chapter 1
Replacing Existing Traverse Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Chapter 2
Upgrade to a Traverse Front Inlet Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
Section 9 Appendices
Appendix A
Module Placement Planning and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Appendix B
Traverse SNMP v1/v2c Agent and MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Page ii
DRAFT
Turin Networks
Release OPS4.0.x
Node Operations and Maintenance [OPS4.0.x]
Document Description
About this Document
Introduction
This description contains the following documentation topics:
• Traverse System Product Documentation, page iii
• TraverseEdge System Product Documentation, page iv
• TransNav Management System Product Documentation, page v
• Operations Documentation, page vi
• Information Mapping, page vi
• If You Need Help, page vi
• Calling for Repairs, page vi
Refer to “” to review the new and changed features for this release.
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
Release OPS4.0.x
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
network operations
center (NOC)
personnel
Turin Networks
Page iii
TraverseEdge System Product Documentation
TraverseEdge
System
Product
Documentation
The TraverseEdge™ 100 User Guide includes the sections described in the table below.
Table 2 TraverseEdge 100 System Product Documentation
Section
Page iv
Description
Target Audience
Product Overview
This section provides a detailed overview of the
TraverseEdge system.
Anyone who wants to
understand the
TraverseEdge system
and its applications
Description and
Specifications
This section includes engineering and planning
information.
Field and network
engineers
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
TransNav management system. Also see the
TransNav Management System Product
Documentation.
Network engineers,
provisioning, and
network operations
center (NOC)
personnel
Configuring
Equipment
This section provides step-by-step procedures for
configuring module and interface parameters of a
TraverseEdge using the TransNav management
system. Also see the TransNav Management
System Product Documentation.
Network engineers,
provisioning, and
network operations
center (NOC)
personnel
Creating TDM
Services
This section provides step-by-step procedures for
provisioning a TraverseEdge network using the
TransNav management system. Also see the
TransNav Management System Product
Documentation.
Network engineers,
provisioning, and
network operations
center (NOC)
personnel
Creating Ethernet
Services
This section provides step-by-step procedures for
provisioning a TraverseEdge network using the
TransNav management system. See the TransNav
Management System Product Documentation.
Network engineers,
provisioning, and
network operations
center (NOC)
personnel
Appendices
This section provides installation and provisioning
checklists, compliance information, and acronym
descriptions.
Installers and anyone
who wants reference
information.
Turin Networks
Release OPS4.0.x
TransNav Management System Product Documentation
TransNav
Management
System
Product
Documentation
The TransNav™ management system product documentation set includes the
documents described in the table below.
Table 3 TransNav Management System Product Documentation
Document
Description
TransNav
Management
System Product
Overview
This document provides a detailed overview of the
TransNav management system.
TransNav
Management
System Server
Guide
This document describes the management server
component of the management system and provides
procedures and troubleshooting information for the
server.
TransNav
Management
System GUI
Guide
This document describes the graphical user interface
including installation instructions and logon
procedures.
This document includes hardware and software
requirements for the management system. It also
includes network management planning information.
Target Audience
Anyone who wants to
understand the
TransNav management
system
Field and network
engineers,
provisioning, and
network operations
center (NOC)
personnel
This document describes every menu, window, and
screen a user sees in the graphical user interface.
Release OPS4.0.x
TransNav
Management
System CLI
Guide
This document includes a quick reference to the
command line interface (CLI). Also included are
comprehensive lists of both the node-level and
domain-level CLI commands.
TransNav
Management
System TL1
Guide
This document describes the syntax of the TL1
language in the TransNav environment.
This document also defines all input commands and
expected responses for retrieval commands as well as
autonomous messages that the system outputs due to
internal system events.
Turin Networks
Page v
Operations Documentation
Operations
Documentation
The document below provides operations and maintenance information for Turin’s
TransNav managed products.
Table 4 Operations Documentation
Document
Node Operations
and Maintenance
Information
Mapping
Description
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
Target Audience
Field and network
engineers
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_overview.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].
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.
Page vi
Turin Networks
Release OPS4.0.x
Calling for Repairs
When shipping equipment for repair, follow these steps:
1. Pack the unit securely.
2. Enclose a note describing the exact problem.
3. Enclose a copy of the invoice that verifies the warranty status.
4. Ship the unit PREPAID to the following address:
Turin Networks, Inc.
Turin Repair Facility
Attn: RMA # ________
1415 North McDowell Blvd.
Petaluma, CA 94954 USA
Release OPS4.0.x
Turin Networks
Page vii
Calling for Repairs
Page viii
Turin Networks
Release OPS4.0.x
S ECTION 1
F AULT M ANAGEMENT
S ECTION 1SYSTEM M ONITORING
S ECTION 1
Contents
Chapter 1
Managing Alarms and Events
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Provisioning events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Performance events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Security events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Normal operational events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Fault events (alarms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Events Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Network Alarm Summary Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Service Affecting Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Alarm Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Traverse Card LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Customizing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Alarm Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Sort by Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Creating a New Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Assigning an Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Assigning a Port Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Assigning a Subport Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Assigning a Service Path Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Suppressing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Suppress Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Service CTP Path Alarm Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Viewing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Alarm Tallies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Detail View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Map View Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
New Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Set Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Sort by Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
StickyMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Release OPS4.0.x
Turin Networks
Page vii
Node Operations and Maintenance Guide, Section 1 Fault Management
Chapter 2
Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Alarms/Events, L through S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Alarms/Events, TA200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-93
Alarms/Events, TB through TZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-95
Alarms/Events U through Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-102
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-105
Chapter 3
TransNav GUI Service Error Codes
Service Activation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
TransNav GUI Service Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-109
List of Figures
Figure 1-1
Figure 1-2
Figure 1-3
Figure 1-4
Figure 1-5
Figure 1-6
Figure 1-7
Figure 1-8
Figure 1-9
Figure 1-10
Figure 1-11
Figure 1-12
Figure 1-13
Figure 1-14
Figure 1-15
Figure 1-16
Map View, Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Network Alarm Summary Window . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Physical Card LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Alarm Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Alarm Profiles Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Alarm Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Path Display for Services Screen . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Path Display for Services Screen . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Alarm Filter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Hardware Fault Detection Descriptions . . . . . . . . . . . . . . . . . . . . . 1-58
TransNav GUI Service Request Error Window . . . . . . . . . . . . . . . 1-107
Service Request Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
Services Menu—Show Last Error Option . . . . . . . . . . . . . . . . . . . 1-108
Table 1-1
Table 1-2
Table 1-3
Table 1-4
Table 1-5
Table 1-6
Table 1-7
Table 1-8
Table 1-9
Table 1-10
Table 1-11
Creating a New Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Assigning a Port Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Assigning a Subport Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Assigning a Service Path Alarm Profile . . . . . . . . . . . . . . . . . . . . . 1-12
Suppress Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Suppress Service CTP Path Alarms . . . . . . . . . . . . . . . . . . . . . . . 1-15
Viewing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Alarms, Events and Recommended Actions, A through C . . . . . . 1-23
Alarms, Events and Recommended Actions, D through K . . . . . . 1-40
Alarms, Events and Recommended Actions, L through S. . . . . . . 1-59
Alarms, Events and Recommended Actions, TA200. . . . . . . . . . . 1-93
List of Tables
Page viii
Turin Networks
Release OPS4.0.x
Node Operations and Maintenance Guide, Section 1 Fault Management
Table 1-12
Table 1-13
Table 1-14
Table 1-15
Release OPS4.0.x
Alarms, Events and Recommended Actions, TB through TZ . . . . 1-95
Alarms, Events and Recommended Actions, U through Z . . . . . . 1-102
Service Request—Show Last Error . . . . . . . . . . . . . . . . . . . . . . . 1-108
Service Error Codes and Recommended Actions. . . . . . . . . . . . . 1-109
Turin Networks
Page ix
Node Operations and Maintenance Guide, Section 1 Fault Management
Page x
Turin Networks
Release OPS4.0.x
S ECTION 1FAULT M ANAGEMENT
Chapter 1
Managing Alarms and Events
Introduction
During normal operation of the Turin product family, various conditions may arise that
require attention by network operations. Events and alarms alert you to system
operational changes. A user’s ability to view and respond to these alarms correlates to
their access role(s) and security levels. For more information, see the TransNav
Management System GUI Guide, Section 2—Administrative Tasks,
Chapter 1—“Managing Server Security” and Chapter 2—“Managing Node Security,”
page 2-11.
Network alarms display at the network Map View level or Network level on the
navigation tree. Alarms for node groups display the number of alarms for each group,
including the node groups and nodes contained in that group.
Events
Events (other than alarm fault events) are state-less alerts indicating configuration
changes, operator actions, performance changes, and other standard operations. If a
card (module) does not appear to generate events, contact the System Administrator.
The card may be reserved for administrative use.
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-7
• Suppressing Alarms, page 1-14
• Viewing Alarms, page 1-17
For management system references, see the TransNav Management System GUI
Guide, Section 8—Maintenance and Testing, Chapter 2—“Alarms.”
Contact the Turin Technical Assistance Center if you need assistance while working
with this product.
Release OPS4.0.x
Turin Networks
Page 1-1
Node Operations and Maintenance Guide, Section 1: Fault Management
Event Types
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 card).
Event Logs
All events (including alarm fault events) are logged on either the Traverse General
Control Card (GCM) or TraverseEdge 100 System card. 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-25.
Page 1-2
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Events Tab
Events Tab
The TransNav GUI Events tab displays a list of events for users to quickly view and
analyze state-less alerts.
Figure 1-1 Map View, Events Tab
Release OPS4.0.x
Turin Networks
Page 1-3
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms Tab
Alarms Tab
The TransNav GUI Alarms tab displays a list of alarms for users to quickly view,
analyze, and resolve fault conditions.
If a node or group is in an alarm state, it displays on the Map View object in the color of
the highest level alarm severity with a caption indicating the number and type of alarm.
(Groups display the color of the most severe alarm present in the nodes or groups
within that group.) For example, in Figure 1-2 the node TE100SIGTWO has four
critical (4C) alarms, so it is colored red with the caption 4C. The “+” indicates other
alarms exist at a lower severity.
For alarms tab definitions, refer to:
• Alarm Severity Levels, page 1-5
• Alarm Hierarchy, page 1-6
• Customizing Alarms, page 1-7
Map View
Display
Alarm Caption
Node Object
Alarms
List
StickyMode
View Selector
Detail View
Command
Alarms Tab
Sort by Column
Print
Command
Set Filters New Window
Save
Command
Command
Command
Figure 1-2 Alarms Tab
Page 1-4
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Alarm Severity Levels
Network Alarm
Summary
Window
The TransNav network alarm summary window shows counts of outstanding Critical
(C), Major (M), Minor (m) alarms, and Warnings (W).
Alarm Summary
Figure 1-3 Network Alarm Summary Window
Network alarms display at the network Map View level or network level on the
navigation tree. Groups display the number of alarms for each group, including the
groups and nodes contained in that group. To view node group alarms, click the group
in the navigation tree or go to the Group Map of the group.
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. 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. An alarm on unprotected
equipment or facilities may be critical, whereas, this same alarm is not considered
critical if the equipment or facility is protected. 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:
•
•
Release OPS4.0.x
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.
Turin Networks
Page 1-5
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarm Hierarchy
•
•
Minor (yellow): Trouble has occurred that does not have a serious effect 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.
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
Page 1-6
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Customizing Alarms
Traverse Card
LEDs
The locations of common and specific card LEDs is shown in the following graphic.
PWR
(Power)
Alarms:
CRITICAL/MAJOR
MINOR
ACO ON
ACTV/
STNBY
(Active/Standby)
ACO
Optical
Port
Timing:
LOCKED/
UNLOCKED
FREE RUN/
HOLDOVER
DS1, DS3/E3,
E1, OC-N/STM-N
and ETH Port
Indicators
ETHERNET LINK
OSS and Craft
10/100BaseT
Ethernet Interface
(RJ-45)
RS-232 Interface
(DB-9)
DS1
DS3/E3
E1
OC-N/
STM-N
VT
Switch
Ethernet
EGCM
OPS 00015
Figure 1-4 Physical Card LEDs
Customizing
Alarms
Release OPS4.0.x
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-8
• Creating a New Alarm Profile, page 1-9
• Assigning a Port Alarm Profile, page 1-11
Turin Networks
Page 1-7
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarm Profiles
Alarm Profiles
Alarm profiles allow users 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-1 ports.
Figure 1-5 Alarm Profile Dialog Box
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.
Page 1-8
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Creating a New Alarm Profile
Creating a New
Alarm Profile
The following procedure describes how to create an Alarm Profile template.
Table 1-1 Creating a New Alarm Profile
Step
1
Procedure
In Map View, from the Admin menu, click Alarm Profiles.
Figure 1-6 Alarm Profiles Dialog Box
Release OPS4.0.x
Turin Networks
Page 1-9
Node Operations and Maintenance Guide, Section 1: Fault Management
Creating a New Alarm Profile
Table 1-1 Creating a New Alarm Profile (continued)
Step
Procedure
2
From the Type drop-down list, select the type of alarm profile you want to
create:
• ds1_ptp: SONET DS1 port
• ds3_ptp: SONET DS3/EC1 ports (previously called ds_ptp)
• e1_ptp: SDH E1 port
• e3_ptp: SDH E3 port
• eos: SONET EOS port
• eos_ctp: SONET EOS connection termination point.
• ethernet_ptp: Ethernet port
• lag: (Ethernet) Link aggregated group
• sdh_eos: SDH EOS port
• sdh_eos_ctp: SDH EOS connection termination point
• sdh_hp: SDH high order path (VC4 or VC3)
• sdh_lp: SDH VC3 low order path
• sdh_ptp: SDH port
• server: TransNav server platform
• shelf: Traverse or TraverseEdge node
• 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-7 Alarm Profile Dialog Box
Page 1-10
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Assigning a Port Alarm Profile
Table 1-1 Creating a New Alarm Profile (continued)
Step
Procedure
4
To modify the alarm entry settings, make a selection from the drop-down
list or check the box in the row of the following columns:
• Severity NSA: Alarm severity when it is non-service affecting.
• Severity SA: Alarm severity when it is service affecting; this severity
only applies if ServiceAffecting is selected.
• ServiceAffecting: Select to make the alarm service affecting. Clear
the checkbox to make the alarm non-service affecting.
• Enabled: Select to enable the alarm. Clear to disable the alarm.
Click OK. A user prompt appears.
5
Click Yes to synchronize the alarm profile to make it available to other
nodes. Click No if you do not want to synchronize the new template.
6
Click Done in the Alarm Profiles dialog box.
7
The Creating a New Alarm Profile procedure is complete.
Assigning an
Alarm Profile
Choose one of the following topics by object type (e.g., port) to assign an alarm profile:
• Assigning a Port Alarm Profile, page 1-11
• Assigning a Subport Alarm Profile, page 1-12
• Assigning a Service Path Alarm Profile, page 1-12
Assigning a
Port Alarm
Profile
The following procedure describes how to assign a port alarm profile template to a port.
Table 1-2 Assigning a Port Alarm Profile
Step
Release OPS4.0.x
Procedure
1
In Shelf View, select a card port (or a TransAccess 100 Mux).
2
Click the Config tab.
3
From the Alarm Profile drop-down list, select a port (ptp) alarm profile
template.
4
Click Apply.
5
The Assigning a Port Alarm Profile procedure is complete.
Turin Networks
Page 1-11
Node Operations and Maintenance Guide, Section 1: Fault Management
Assigning a Subport Alarm Profile
Assigning a
Subport Alarm
Profile
The following procedure describes how to assign a port alarm profile template to a DS3
Transmux subport.
Table 1-3 Assigning a Subport Alarm Profile
Step
Assigning a
Service Path
Alarm Profile
Procedure
1
In Shelf View, select a DS3 Transmux card port.
2
Click the Config tab.
3
From the Subport row, Alarm Profile column list, select a port (ptp)
alarm profile template matching the embedded signal subport type (e.g.,
ds1_ptp).
4
Click Apply.
5
The Assigning a Subport Alarm Profile procedure is complete.
The following procedure describes how to assign a path alarm profile template to a
service connection termination point (CTP) within an end-to-end transport path.
Table 1-4 Assigning a Service Path Alarm Profile
Step
1
Procedure
From any view, click the Service tab.
Figure 1-8 Service Tab
2
Page 1-12
Select a service. Right-click and select Show TxRx Path to display the
Path Display for Services screen.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Assigning a Service Path Alarm Profile
Table 1-4 Assigning a Service Path Alarm Profile (continued)
Step
3
Procedure
Click the CTP tab to display the CTP dialog box.
3
Figure 1-9 Path Display for Services Screen
4
Release OPS4.0.x
From the Path Display for Service screen, Tx or Rx table row, select an
Active Hop. Your selection displays in the EndPoint field of the CTP
screen.
Turin Networks
Page 1-13
Node Operations and Maintenance Guide, Section 1: Fault Management
Suppressing Alarms
Table 1-4 Assigning a Service Path Alarm Profile (continued)
Suppressing
Alarms
Step
Procedure
5
From the Alarm Profile list, select one of the following profile values:
• useParent: The alarm profile of the containing object (Parent) based
on the following (superset and subset) definitions:
– Port: Contains line and path alarms and is the superset.
– High-order path: Contains high- and low-order path alarms and is
a subset of port profiles.
– Low-order path: Contains only low-order path alarms and is a
finer subset of high-order path profiles.
– STS path. Contains STS and VT path alarms and is a subset of
port profiles.
– VT path: Contains only VT path alarms and is a finer subset of
STS path profiles.
• default: The default alarm profile matching the CTP object type.
• <user-defined>: Depending on the CTP object type, a user-defined
alarm profile of one of the following path alarm profile types:
– sdh_hp
– sdh_lp
– sonet_sts
– sonet_vt
6
Click Apply.
7
The Assigning a Service Path Alarm Profile procedure is complete.
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-14
• Service CTP Path Alarm Suppression, page 1-15
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.
Table 1-5 Suppress Port Alarms
Step
Page 1-14
Procedure
1
In Shelf View, select the card port.
2
Click the Config tab to display the Card Configuration dialog box.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Service CTP Path Alarm Suppression
Table 1-5 Suppress Port Alarms (continued)
Step
Service CTP
Path Alarm
Suppression
Procedure
3
Click the Lock icon
at the bottom left portion of the screen to change
and click Apply.
the administrative state to locked
4
The Suppress Port Alarms procedure is complete.
The following procedure describes how to suppress service CTP (connection
termination point) path alarms.
Table 1-6 Suppress Service CTP Path Alarms
Step
Procedure
1
Is a parent object of the CTP already suppressing alarms?
• Yes: Stop. CTP alarms are already being suppressed in accordance
with the parent object.
• No: Go to the next step.
2
From any view, click the Service tab.
2
3
Figure 1-10 Service Tab
Release OPS4.0.x
Turin Networks
Page 1-15
Node Operations and Maintenance Guide, Section 1: Fault Management
Service CTP Path Alarm Suppression
Table 1-6 Suppress Service CTP Path Alarms (continued)
Step
3
Procedure
Select a service. Right-click and select Show TxRx Path to display the
Path Display for Services screen.
3
5a
4
5b
6
7
Figure 1-11 Path Display for Services Screen
Page 1-16
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 (6) to
.
change the administrative state to locked
7
Click Apply (7).
8
The Suppress Service CTP Path Alarms procedure is complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Viewing Alarms
Viewing
Alarms
The TransNav GUI displays alarm information for users to view, analyze, and resolve
fault conditions quickly. The alarms shown can be for different levels of object
granularity: by node group (includes all the nodes and groups within that group) all
nodes, one node, a card, a port, or a service connection termination point (CTP) within
an end-to-end transport path.
Note: If a map for a group is displayed, only the alarms for nodes within that group
display in the alarm summary list.
The following procedure describes how to view alarms described 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, select a node.
• Card. In Shelf View, select a card.
• Port. In Shelf View, select a port.
• Service CTP.
– Click the Services tab.
– Right-click on a service and select Show TxRx 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
Look in the lower-left corner of the Alarms 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.
Release OPS4.0.x
Turin Networks
Page 1-17
Node Operations and Maintenance Guide, Section 1: Fault Management
Viewing Alarms
Table 1-7 Viewing Alarms (continued)
Step
Procedure
6
Click Detail View to display the Alert Detail (View Main) dialog box and
view highlighted alarm details.
Go to Step 14.
7
Map View Display
The Map View displays in the upper half of the GUI screen.
If a node is in an alarm state, it displays 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. The “+” indicates other alarms exist at a lower severity.
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.
Page 1-18
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Alarms and Events
Viewing Alarms
Table 1-7 Viewing Alarms (continued)
Step
11
Procedure
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-12 Alarm Filter Dialog Box
Go to Step 14.
12
Sort by Column
Click a column heading to sort the alarms by that category. The AlarmID,
Source, ProbCause (probable cause), Time, and AckBy (acknowledged
by) columns can be sorted in alphanumeric or reverse alphanumeric order.
The Severity column can be sorted in ascending or descending severity.
The SA (ServiceAffecting) column can be sorted by select/clear. Click the
column heading again to switch from one sorting category to the other.
Go to Step 14.
Release OPS4.0.x
Turin Networks
Page 1-19
Node Operations and Maintenance Guide, Section 1: Fault Management
Viewing Alarms
Table 1-7 Viewing Alarms (continued)
Step
13
Procedure
StickyMode
Selecting this check box 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 moves
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 changes from Critical
to Clear.
Turin recommends that you open a new window before you select
StickyMode so new alarms continue to be reported.
14
Page 1-20
Do you want to perform another alarm display function?
• Yes. Go to Step 3.
• No. The Viewing Alarms procedure is complete.
Turin Networks
Release OPS4.0.x
S ECTION 1FAULT M ANAGEMENT
Chapter 2
Alarms, Events, and Recommended Actions
Introduction
During normal operation of the Turin product family, various conditions may arise that
require attention by network operations. Events and alarms alert you to Traverse
system operational changes.
This chapter includes the following alarms, events, and recommended actions.
• conditioningAlarms/Events, D through K, page 1-23
• Alarms/Events, L through S, page 1-59
• Alarms/Events, TA200, page 1-93
• Alarms/Events, TB through TZ, page 1-95
• Alarms/Events U through Z, page 1-102
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.
To view alarms associated with a node group, select the node group in the navigation
tree or click on the Group Map for the node group. Only the alarms associated with that
node group, including the nodes and node groups included in that node group
hierarchy, display in the alarm summary in the TransNav GUI.
If a card (module) does not appear to generate alarms, contact your system
Administrator. The card may be reserved for administrative use.
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.
Release OPS4.0.x
Turin Networks
Page 1-21
Node Operations and Maintenance Guide, Section 1: Fault Management
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 Customer Service Technical Assistance Center (TAC). if you need
assistance.
Page 1-22
Turin Networks
Release OPS4.0.x
Release OPS4.0.x
conditioningAla
Table 1-8 Alarms, Events and Recommended Actions, A through C
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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.
–
Info
Info
Informational; no action required.
AIRCOND:Air Conditioning
System Fail
shelf
Air conditioning system failed.
–
Minor
Minor
Check and repair the air conditioning
equipment, as necessary.
AIRDRYR:Air Dryer Fail
shelf
Air dryer failed.
–
Minor
Minor
Check and repair the air dryer equipment, as
necessary.
AIS-L: Alarm indication signal –
Line
ds1_ptp
ds3_ptp
(ds_ptp)
e3_ptp1
ta200
te50
The input signal on a DS1, DS3, or
EC-1 interface contains an AIS.
SA
Critical
Critical
shelf
The locally received BITS signal
contains an AIS. This indicates a
remote BITS failure.
SA
The locally received OC-N signal
contains an AIS. This indicates a
remote OC-N level failure.
SA
sonet_ptp
Check the equipment (card/port) upstream.
Clear upstream alarms.
Critical
Minor
Check the BITS upstream.
Clear upstream alarms.
Critical
Minor
Check the equipment (card/port) upstream.
Clear upstream alarms.
Page 1-23
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
ACO: Alarm Cut Off
Alarm: Definition
AIS-P: Alarm indication signal –
Path
Alarm
Profiles
Probable Cause
Service
Affecting
Default
ds3_ptp
(ds_ptp)
e3_ptp
ta200
te50
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
sonet_ptp
sonet_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
SA
NSA
(Unprotected)
(Protected)
Critical
Critical
Recommended Action
Check the equipment (card/port) upstream.
Clear upstream alarms.
Verify your payload connections.
Critical
Minor
Check the equipment upstream.
Clear upstream alarms.
Verify your payload connections.
Turin Networks
AIS-S1: Alarm indication signal – ds3_ptp
Service
(ds_ptp)
e3_ptp
sdh_ptp
sonet_ptp
sonet_service
An upstream failure occurred at
the Service layer.
–
AIS-V1: Alarm indication signal – ds1_ptp
VT
ds3_ptp
(ds_ptp)
e3_ptp
shelf
sonet_ptp
sonet_vt
sonet_sts
An upstream failure occurred at
the VT path layer.
SA
Release OPS4.0.x
ta200
te50
Default Severity
Warning
Info
Check the equipment upstream.
Clear upstream alarms.
Critical
Minor
Check the equipment upstream.
Clear upstream alarms.
Verify your VT payload connections.
An upstream failure occurred at
the VT path layer.
SA
Critical
Critical
Check the equipment upstream.
Clear upstream alarms.
Verify your VT payload connections.
sdh_ptp
See TU-AIS.
n/a
n/a
n/a
See TU-AIS.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-24
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
Alarm
Profiles
AIS-VC: Alarm indication signal - e1_ptp
VC
sdh_ptp
Probable Cause
An upstream failure occurred at
the VC path layer.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Minor
Recommended Action
Check the equipment upstream.
Clear upstream alarms.
Verify your VC payload connections.
Page 1-25
ethernet_ptp
sdh_ptp
sonet_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_ptp
sdh_ptp
sonet_ptp
Event logged against the optical
interface upon ALS alarm
condition.
–
Info
Info
Informational; no action required.
APS-AIS-P1: Automatic
shelf
protection (multiplex section
protection - MSP) Administrative
Unit switching Alarm Indication
Signal – Path
A protection switch has occurred
due to an AIS-P alarm.
–
Info
Info
See AIS-P.
APS-LOP-P1: Automatic
shelf
protection switching (multiplex
section protection - MSP) Loss of
Pointer – Path
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.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
ALS: Automatic laser shutdown
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
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_ptp
sdh_ptp
On a 2F BLSR, the APS K1/K2
bytes are in an invalid state.
–
Minor
Minor
Check for OC-N card failures.
APSCFGMIS: Automatic
protection switch (multiplex
section protection - MSP)
configuration mismatch
sonet_ptp
sdh_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
APSCM: Automatic protection
switch (multiplex section
protection - MSP) channel
mismatch
sonet_ptp
sdh_ptp
On a 2F BLSR, the local Traverse
node is not receiving the K1/K2
values it is expecting.
–
Minor
Minor
APSIMP: Improper automatic
protection switching (multiplex
section protection - MSP) code
sonet_ptp
sdh_ptp
On a 2F BLSR, the automatic
protection switching codes are
improper. Indicates invalid K
bytes.
–
Examine the incoming SONET overhead
with an optical test set to confirm
inconsistent or invalid K bytes.
APSBF: Automatic protection
switch byte failure
• Check that the fiber is connected properly
to the remote node.
• Check that a remote 1+1 linear PG exists.
Check for OC-N card failures.
Examine the incoming SONET overhead
with an optical test set to confirm
inconsistent or invalid K bytes.
Minor
Minor
Reseat the cards at the near end and
upstream nodes.
Examine the incoming SONET overhead
with an optical test set to confirm invalid K
bytes.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-26
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
APSINC: Inconsistent automatic
protection switching (multiplex
section protection - MSP) code
Alarm
Profiles
sonet_ptp
sdh_ptp
Probable Cause
On a 2F BLSR, the automatic
protection switching codes are
inconsistent. Three consecutive
frames do not contain identical
APS bytes, giving the receiving
equipment conflicting commands
about switching.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Minor
Minor
Recommended Action
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 cards at the near end and
upstream nodes.
Page 1-27
APSLOPCLEAR1: Automatic
shelf
protection switching (multiplex
section protection - MSP) Loss of
Pointer Clear
A protection switch which
occurred because of an LOP-P
alarm has been cleared.
–
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
APSLOS1: Automatic protection
switching (multiplex section
protection - MSP) Loss of Signal
A protection switch has occurred
because of an LOS alarm.
–
Info
Info
See LOS.
shelf
APSLOSCLEAR1: Automatic
protection switching (multiplex
section protection - MSP) Loss of
Signal Clear
A protection switch which
occurred because of an LOS alarm
has been cleared.
–
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
APSMM1: Automatic protection sonet_ptp
switch (multiplex section
sdh_ptp
protection - MSP) mode mismatch
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
A protection switch which
occurred because of a path alarm
has been cleared.
–
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
shelf
shelf
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
Check the protection mode for the far-end
node.
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
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.
–
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
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.
–
Info
Info
Informational; no action required.
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.
–
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
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.
–
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
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.
–
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-28
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
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_ptp
sdh_hp
sdh_ptp
The STM signal demultiplexed
from the STM-N contains an AIS.
This AIS can result from an
upstream failure along the STM
path.
SA
ds3_ptp
sdh_hp
sdh_ptp
Valid AU pointer bytes are missing
from the SDH overhead.
SA
AU-LOP: Administrative Unit
Loss of Pointer
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Info
Info
If frequent protection switching occurs,
check the revertive WTR period setting.
Critical
Minor
Check the equipment upstream.
Clear upstream alarms.
Verify your payload connections.
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 card.
1
Page 1-29
AUTHFAIL : 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_ptp
sdh_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.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
APSWTR: Transition to Wait to
Restore mode (multiplex section
protection - MSP)
Default Severity
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Event against the optical interface
when the transmitter has been
turned on automatically.
–
Info
Info
Informational; no action required.
BADPKTRX1: Received an OSPF shelf
packet that cannot be parsed
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.
AUTO-TX-ON: Transmitter
automatically enabled
ethernet_ptp
sdh_ptp
sonet_ptp
Turin Networks
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-30
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
BERSD-L: Bit ErrorRate signal
degrade – Line
Alarm
Profiles
ds3_ptp
(ds_ptp)
e3_ptp1
Probable Cause
The BER on the incoming EC-1
line has exceeded the signal
degrade threshold.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Check cable connectors and card ports.
If an EC-1 card 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.
The BER on the incoming BITS
has exceeded the signal degrade
threshold.
sonet_ptp
n
n
n
n
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 card hardware
problem could exist.
Fiber could be bent or
damaged.
–
Warning
Warning
Check cable connectors.
SA
Warning
Warning
Verify the local receive optical levels, as
well as the upstream transmit levels.
Verify good optical connections.
Clean optical cable connectors and card
ports.
If an OC-N card 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 Technical Assistance
Center (TAC).
Page 1-31
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
shelf
te50
Alarm: Definition
BERSD-P: Bit Error Rate signal
degrade – Path
Alarm
Profiles
ds3_ptp
(ds_ptp)
e3_ptp1
Probable Cause
The STS signal demultiplexed and
dropped from the EC-1 has
exceeded its signal degrade
threshold.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
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 card ports.
If an EC-1 card 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.
Turin Networks
sonet_ptp
sonet_sts
The STS signal demultiplexed and
dropped from the OC-N/STM-N
has exceeded its signal degrade
threshold.
SA
Warning
Warning
Examine the network for other path bit error
rate problems and retrieve PM data to find a
possible common source of the bit errors.
Perform loopback tests to isolate the
problem.
Check cable connectors and card ports.
If an OC-N/STM-N card is a possible source
of the bit errors, perform a manual protection
switch to the protection unit. If the BER
alarm clears, replace the defective “working”
unit.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-32
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
BERSD-V: BitError Rate signal
degrade – VT Path
Alarm
Profiles
ds1_ptp
ds3_ptp
(ds_ptp)
e3_ptp1
Probable Cause
The VT signal demultiplexed and
dropped from the DS1 has
exceeded its signal degrade
threshold.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
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 card ports.
The VT signal demultiplexed and
dropped from the OC-N has
exceeded its signal degrade
threshold.
SA
Warning
Warning
Examine the network for other path bit error
rate problems and retrieve PM data to find a
possible common source of the bit errors.
Perform loopback tests to isolate the
problem.
Check cable connectors and card ports.
sdh_ptp
BERSD-VC: Bit Error Rate signal e1_ptp
degrade – VC Path
sdh_ptp
See LP-BERSD.
n/a
n/a
n/a
See LP-BERSD.
The VC signal demultiplexed and
dropped from the STM-N has
exceeded its signal degrade
threshold.
SA
Warning
Warning
Examine the network for other path bit error
rate problems and retrieve PM data to find a
possible common source of the bit errors.
Perform loopback tests to isolate the
problem.
Check cable connectors and card ports.
Page 1-33
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
sonet_ptp
sonet_sts
sonet_vt
shelf
Alarm: Definition
BERSF-L: Bit Error Rate signal
fail – Line
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
ds3_ptp
(ds_ptp)
e3_ptp1
The BER on the incoming EC-1
line has exceeded the signal fail
threshold.
SA
Warning
Warning
Check cable connectors and card ports.
shelf
te50
The BER on the incoming BITS
has exceeded the signal fail
threshold.
–
Warning
Warning
Check cable connectors.
sonet_ptp
n
SA
Warning
Warning
Verify the local receive optical levels, as
well as the upstream transmit levels.
n
Turin Networks
n
n
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 card hardware
problem could exist.
Fiber could be bent or
damaged.
Verify good optical connections.
Clean optical cable connectors and card
ports.
If an OC-N card 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.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-34
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
BERSF-P: Bit Error Rate signal
fail – Path
Alarm
Profiles
ds3_ptp
(ds_ptp)
e3_ptp1
Probable Cause
The STS signal demultiplexed and
dropped from the EC-1 has
exceeded its signal fail threshold.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
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 card ports.
sonet_ptp
sonet_sts
The STS signal demultiplexed and
dropped from the OC-N has
exceeded its signal fail threshold.
SA
Warning
Warning
Examine the network for other path bit error
rate problems and retrieve PM data to find a
possible common source of the bit errors.
Perform loopback tests to isolate the
problem.
Check cable connectors and card ports.
If an OC-N card 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.
Page 1-35
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
If an EC-1 card 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.
Alarm: Definition
BERSF-V: Bit Error Rate signal
fail – VT/VC Path
Alarm
Profiles
ds1_ptp
ds3_ptp
(ds_ptp)
e3_ptp1
Probable Cause
The VT/VC signal demultiplexed
and dropped from the card has
exceeded its signal fail threshold.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
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 card ports.
sonet_ptp
sonet_vt
sonet_sts
The VT signal demultiplexed and
dropped from the OC-N has
exceeded its signal fail threshold.
SA
Warning
Warning
Examine the network for other path bit error
rate problems and retrieve PM data to find a
possible common source of the bit errors.
Turin Networks
Perform loopback tests to isolate the
problem.
Check cable connectors and card ports.
shelf
The VT signal demultiplexed and
dropped from the OC-N has
exceeded its signal fail threshold.
SA
Warning
Warning
Examine the network for other path bit error
rate problems and retrieve PM data to find a
possible common source of the bit errors.
Perform loopback tests to isolate the
problem.
Check cable connectors and card ports.
sdh_ptp
BERSF-VC: Bit Error Rate signal e1_ptp
fail – VC Path
sdh_ptp
See LP-BERSF.
n/a
n/a
n/a
See LP-BERSF.
The VC signal demultiplexed and
dropped from the STM-N has
exceeded its signal fail threshold.
SA
Warning
Warning
Examine the network for other path bit error
rate problems and retrieve PM data to find a
possible common source of the bit errors.
Release OPS4.0.x
Perform loopback tests to isolate the
problem.
Check cable connectors and card ports.
BITSA-FRC: Forced switch Derived DS1 System BITS 1
shelf
A forced switch is in process.
–
Warning
Warning
Clear the Forced switch command.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-36
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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 shelf
DS1 System BITS 2
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 server
out of sync
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.
Critical
Critical
Check for OC-N/STM-N card failures.
Examine the incoming SONET/SDH
overhead with an optical test set to confirm
inconsistent or invalid K bytes.
SA
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 card 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.
Page 1-37
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 card is inserted correctly into
the chassis. Otherwise, run diagnostics to
test the state of the card.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
BITSA-LOCK: Lockout - Derived shelf
DS1 System BITS 1
Alarm: Definition
Alarm
Profiles
Probable Cause
BPSIG: The backplane cannot
communicate with other cards
shelf
• Card defect.
• Backplane slot defect.
CFGERR1: OSPF configuration
parameter mismatch)
shelf
CLEAR: Clear switch request
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
SA
Critical
Minor
Replace the card. If the same alarm persists,
try another slot in the shelf.
A packet was received whose
configuration parameters conflict
with the node’s configuration
parameters.
–
Minor
Minor
Check the configuration.
shelf
A Clear switch command has been
performed on a 1:1 equipment,
1+1 facility, or BLSR/MS-SP Ring
protection group.
–
Info
Info
Informational; no action required.
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
necessary.
CLRLOOP: Clear loopback
ds1_ptp
ds3_ptp
(ds_ptp)
e1_ptp
e3_ptp
ethernet_ptp
sonet_ptp
sdh_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).
ta200
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).
te50
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-38
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Release OPS4.0.x
Table 1-8 Alarms, Events and Recommended Actions, A through C (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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 card (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.
Not supported in this release.
2
Environmental alarm inputs are customized by each operator.
rms/Events, D
through K
Page 1-39
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
1
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
DBCRPT: Database corruption
server
shelf
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 Technical
Assistance Center (TAC).
DBFAIL: Database failed
server
shelf
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
server
shelf
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.
SA
Critical
Minor
• Verify that the software version is
correct.
• Contact Turin’s Customer Service
Technical Assistance Center (TAC).
SA
Minor
Minor
• If the standby GCM is rebooting, the
condition will clear when the active
GCM goes hot.
• Otherwise, reboot the standby GCM
and allow time for the GCMs to go hot.
• If no resolution, contact Turin’s
Customer Service Technical Assistance
Center (TAC).
Some database operations will
fail, but the node is still usable.
DBRED: Redundant Database
failed
server
shelf
Release OPS4.0.x
A redundant database failure has
occurred as a result of a standby
GCM reboot, a connection
failure, or abnormal shutdown
of database software.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-40
Table 1-9 Alarms, Events and Recommended Actions, D through K
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
DBSIGN: Database signature
mismatch
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
SA
Major
Minor
• If the TransNav server connects, and
this alarm is present, verify
commissioning parameters, then reboot
the node.
• If the TransNav server does not
connect to the node, use the Craft port
on the active GCM to commission the
node via CLI, verify commissioning
parameters, then reboot the node.
Not supported on EC-1.
SA
Major
Major
Not supported; no action required.
•
SA
Major
Minor
•
•
ds3_ptp
e1_ptp
e3_ptp
ethernet_ptp
sdh_ptp
sonet_ptp
server
shelf
ta200
te50
The database content does not
match the node commissioning
parameter values. The database
is unusable.
ds3_ptp
(ds_ptp)
ds3_ptp
(ds_ptp)
e3_ptp1
sonet_ptp
sonet_sts
sdh_hp
sdh_lp
sdh_ptp
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 the
TransNav server will not
connect to the node due to
improper commissioning.
•
•
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.
•
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.
Page 1-41
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
DCCFAIL: Data
Communications Channel fail
Alarm
Profiles
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
DOWN1: Out of service
ds1_ptp
ds3_ptp
(ds_ptp)
e1_ptp
e3_ptp
ethernet_ptp
server
shelf
sonet_ptp
sdh_ptp
sonet_service
ta200
te50
Unused.
–
Minor
Minor
Unused.
DQL1: Degraded quality level
ds3_ptp
ds_ptp
e3_ptp
shelf
sonet_ptp
sdh_ptp
The incoming signal has a
degraded quality level.
–
Minor
Minor
Check and clean connections.
DS1AIS: Alarm indication
signal - DS1
ds1_ptp
ta200
te50
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.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-42
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
DS1RAI: Remote alarm
indication
Alarm
Profiles
ds1_ptp
te50
Probable Cause
n
n
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.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
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.
Page 1-43
ds3_ptp
ds_ptp
ta200
te50
The DS3 input contains an AIS.
DS3RAI: Remote alarm
indication
ds3_ptp
ds_ptp
ta200
te50
n
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_ptp
ta200
te50
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.
n
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.
SA
Critical
Critical
Inspect and clear alarms from the
upstream asynchronous equipment.
–
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.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
DS3AIS: Alarm indication
signal - DS3
Alarm: Definition
E1RAI: Remote alarm
indication
Alarm
Profiles
e1_ptp
Probable Cause
n
te50
n
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.
E3 AIS: Alarm indication signal
- E3
e3_ptp
The E3 input contains an AIS.
E3 RAI: Remote alarm
indication
e3_ptp
n
Turin Networks
n
The far-end node has
detected a defect signal on
an incoming E3.
The local node is sending a
bad E3 signal towards the
E-X.
EFMFAIL: EFM failure
shelf
EFM (ingress or egress) failure;
parity or other error.
ENGINE: Engine failure
shelf
ENGOPRG: Engine operating
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
–
Warning
Warning
Verify that the connections between the
E-X and the E1 module are secure.
SA
Critical
Critical
SA
Critical
Critical
Inspect and clear alarms from the
upstream asynchronous equipment.
–
Warning
Warning
Verify that the connections between the
E-X and the E3 module are secure.
Verify that the E1 signal entering the far
end of the SDH network is error-free.
Verify that the E3 signal entering the far
end of the SDH network is error-free.
Release OPS4.0.x
SA
Critical
Critical
Reboot card and consult Turin’s Customer
Service Technical Assistance Center
(TAC), if alarm persists.
Internal queue engine failure.
–
Minor
Minor
Reboot card and consult Turin’s Customer
Service Technical Assistance Center
(TAC), if alarm persists.
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.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-44
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
shelf
An invalid piece of equipment
has been used.
–
Critical
Critical
Plug in a valid piece of equipment.
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.
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.
Note: GCM, Enhanced
GCM, and GCM with integrated
optics are considered different
module types.
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.
Page 1-45
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.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
EQINV: Equipment invalid
Alarm: Definition
Alarm
Profiles
Probable Cause
EQRMV: Equipment removed
shelf
A module is not properly seated
or it has been removed.
ERFI-V: Enhanced (two bit)
Remote failure indication – VT
Path
ds1_ptp
n
n
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
SA
Critical
Minor
Plug in the correct module or delete the
module using the TransNav system if that
slot is not being used.
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.
Verify your payload connections.
Clear path alarms such as LOP-V, AIS-V,
PLM-V, TIM-V, and UNEQ-V from the
far-end node.
Turin Networks
Release OPS4.0.x
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 a
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 a
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.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-46
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Page 1-47
shelf
Third reference for Derived DS1
System SASE 1 is alarmed due
to source signal failure or
unavailability due to a 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-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 a
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.
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 a
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.
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 a
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.
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 a 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.
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.
–
Warning
Warning
Clear the LOS, LOF, or AIS-L alarm.
Refer to the recommended actions for
those alarms in this table.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
EXTA-REF3-ALM: Third
reference in alarm
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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.
FEP : Far-end protection failure
sonet_ptp
sdh_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.
1
Turin Networks
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.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-48
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
FLOW-DEGRADED: VPG
Degraded Flow
Alarm
Profiles
ethernet_ptp
Probable Cause
The system is currently
forwarding a Poor, Lost, or Null
copy of a learned flow.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Major
Major
The system clears flow-related alarms
once it unlearns the flow.
Note: Flow alarms are
received on the working port of
the Virtual Protection Group
(VPG).
ethernet_ptp
The system has learned a VLAN
flow.
–
Info
Info
Informational only; no action required.
FLOW-UNLEARNED:
Unlearned VLAN Flow
ethernet_ptp
The system has unlearned a
single VLAN flow either
automatically or through an
operator request.
–
Info
Info
Informational only; no action required.
FLOWS-UNLEARNED:
Unlearned All VLAN Flows
ethernet_ptp
The system has unlearned all the
VLAN flows through an
operator request.
–
Info
Info
Informational only; no action required.
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.
–
Minor
Minor
The system clears flow-related alarms
once it unlearns the flow.
SA
Critical
Critical
Check remote peer for proper
configuration.
Note: Flow alarms are
received on the working port of
the VPG.
Page 1-49
FOPR: Failure of protocol receive
eos
sdh_eos
LCAS has detected unexpected
behavior by the remote LCAS
peer.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
FLOW-LEARNED: Learned
VLAN Flow
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
FOPT: Failure of protocol transmit
eos
sdh_eos
LCAS has detected unexpected
behavior by the remote LCAS
peer.
SA
Critical
Critical
Check remote peer for proper
configuration.
FORCE_ONLINE
ta200
The selected module is forced
online. A 50 ms ‘hit’ occurs on
the T1 traffic during the switch.
SA
Warning
Warning
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
Turin Networks
Redundancy is disabled while a
force protection switch is active.
Any failures to the on-line
module are not protected.
Therefore, the status LED will
be turned yellow to indicate a
maintenance condition is active.
FORCED: Forced protection
switching
shelf
FORCED_ON_PROT: Forced
protection switch on protecting
unit
shelf
FORCED_ON_SECT1: Forced
protection switch on optimized
1+1 APS working section 1
shelf
A forced protection switch has
been performed on a 1:1
equipment, 1+1 facility, or
BLSR/MS-SP Ring protection
group.
–
A forced protection switch has
been performed on a protection
group.
–
A forced switch has been
performed on the optimized 1+1
APS bi-directional working
section 1.
–
Release OPS4.0.x
Note: Section 1 and 2 are
equal working sections, each
with a permanent traffic bridge.
Warning
Warning
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
Warning
Warning
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
Warning
Warning
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-50
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
FORCED_ON_SECT2: Forced
protection switch on optimized
1+1 APS working section 2
Alarm
Profiles
shelf
Probable Cause
A forced switch has been
performed on the optimized 1+1
APS bi-directional working
section 2.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
Note: Section 1 and 2 are
equal working sections, each
with a permanent traffic bridge.
shelf
FORCED-EAST: Forced switch
applied on east facility
shelf
FORCED-WEST: Forced switch
applied on wast facility
shelf
A forced protection switch has
been performed on the working
unit.
–
A forced protection switch has
been performed on the east
facility.
–
A forced protection switch has
been performed on the west
facility.
–
Warning
Warning
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
Warning
Warning
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
Warning
Warning
Verify that the reason for performing the
forced switch no longer exists.
Clear the switch command.
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.
Page 1-51
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
FORCED_ON_WORK: Forced
protection switch on working
unit
Alarm: Definition
GIDERR: LCAS group ID
mismatch
Alarm
Profiles
shelf
Probable Cause
A link capacity adjustment
scheme (LCAS) group ID
member of the VC bundle shows
one of the following conditions
are present on the path:
• LOP
• LOM
• AIS
• LOS
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
SA
Critical
Minor
• Inspect all VC bundle facilities.
• Check remote sites for module
removal/failure alarms or disabled
Ethernet transmitter.
• Check the cable and interface.
The VC bundle continues to
operate.
Turin Networks
GIDM: Group ID mismatch
eos
sdh_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_ptp
sdh_hp
sdh_lp
sdh_ptp
sonet_ptp
sonet_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.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-52
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
HITEMP: High temperature
Alarm
Profiles
shelf
Probable Cause
Temperature is too high.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Minor
Minor
Recommended Action
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.
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
ds3_ptp
sdh_hp
sdh_ptp
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.
Perform loopback tests to isolate the
problem.
Check cable connectors and module ports.
Page 1-53
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.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
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.
Alarm: Definition
HP-BERSF: Bit error rate signal
degrade - High order Path
Alarm
Profiles
ds3_ptp
sdh_hp
sdh_ptp
Probable Cause
The STM signal demultiplexed
and dropped from the STM-N
has exceeded its signal fail
threshold.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Examine the network for other high order
path bit error rate problems and retrieve
PM data to find a possible common source
of the bit errors.
Perform loopback tests to isolate the
problem.
Check cable connectors and module ports.
Turin Networks
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.
Release OPS4.0.x
HP-LOM: High order path Loss
of multiframe
sdh_eos
sdh_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_eos
sdh_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.
HP-SQM: High order path
Sequence ID mismatch
sdh_eos
sdh_eos_ctp
The member sequence number
is in error.
SA
HP-PLM: Payload label
mismatch received - High order
Path
ds3_ptp
sdh_hp
sdh_ptp
n
n
Invalid C2 byte (signal label
byte) in the SDH path
overhead.
The payload does not match
what the signal label is
reporting.
Check the EOS member status to
determine which paths have exceeded the
delay and reroute them.
Critical
Critical
This is an eos_ctp member alarm.
If non-LCAS, check that the order of
members in the remote EOS matches the
local order
SA
Critical
Minor
Connect correct payload.
Verify that the payload is the same as the
provisioned payload/service.
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-54
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
HP-RDI: Remote Defect
Indication - High order Path
HP-RFI: Remote Failure
Indication - High order Path
Alarm
Profiles
Probable Cause
ds3_ptp
sdh_hp
sdh_ptp
Valid STM-N framing is not
detected or AU-AIS (or
MS-AIS) is received from the
source.
sdh_hp
sdh_ptp
n
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Check STM-N framing source.
See AU-AIS.
See MS-AIS.
–
Far end path has an HP-UNEQ
or HP-TIM alarm.
–
Warning
Warning
Determine the defects found at the far-end
node.
Verify your payload connections.
Clear path alarms from the far-end node.
Warning
Warning
Verify your payload connections.
Check for far end alarms, especially
HP-UNEQ and HP-TIM.
Refer to the recommended actions for
HP-UNEQ and HP-TIM.
HP-RFIPAY: Remote failure
indication, payload defect High order Path
ds3_ptp
sdh_hp
sdh_ptp
Far end path has a HP-PLM
alarm.
–
Warning
Warning
Verify your payload connections.
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
ds3_ptp
sdh_hp
sdh_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.
Page 1-55
HP-TIM: Trace identifier
mismatch - High order Path
ds3_ptp
sdh_hp
sdh_ptp
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.
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
ds3_ptp
sdh_hp
sdh_ptp
–
The signal demultiplexed
from the STM-N contains a
remote failure indication.
The far-end node has
detected path defects
coming from the local site.
n
HP-RFICON: Remote failure
indication, connectivity defect High order Path
Service
Affecting
Default
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
SA
NSA
(Unprotected)
(Protected)
No payload is received on an
activated service.
HWFAULT: Hardware fault
shelf
A hardware fault has occurred.
SA
Critical
Critical
See Figure 1-13 Hardware Fault
Detection Descriptions, page 1-58 for
further details. Take appropriate action, as
necessary.
IDLE: Idle signal detection
ds1_ptp
ds3_ptp
(ds_ptp)
e1_ptp
e3_ptp
Service is not provisioned over
the interface.
SA
Warning
Warning
Check the interface.
server
shelf
Software is incompatible
between modules that are
attempting communication with
each other.
–
Turin Networks
INCOMPATSW: Incompatible
software
Critical
Minor
Recommended Action
ds3_ptp
sdh_hp
sdh_ptp
HP-UNEQ: Unequipped - High
order Path
SA
Default Severity
Check your connection.
Connect your proper payload.
Check the service source.
Check the far-end node.
Critical
Critical
Check the current software versions and
compatibility IDs of the modules.
One module’s current software version
must be at least the compatibility ID (the
lowest software version the other module
can work with) of the other module.
Perform software upgrade as necessary for
software compatibility.
INTRUDER: Intrusion
shelf
–
Minor
Minor
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-56
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Release OPS4.0.x
Release OPS4.0.x
Table 1-9 Alarms, Events and Recommended Actions, D through K (continued)
Alarm: Definition
Alarm
Profiles
INDICATION: Indication
Alarm on MPS IM
te50
KBYTE: Default K byte
sonet_ptp
sdh_ptp
Probable Cause
Far end protection mode
mismatch. K1/K2 bytes not sent.
For example, a BLSR may have
one node configured as a UPSR,
and a node in a UPSR would not
send the two valid K1/K2 bytes
expected by a BLSR system.
Not supported in this release.
2
Environmental alarm inputs are customized by each operator.
Default Severity
SA
NSA
(Unprotected)
(Protected)
SA
Critical
Critical
–
Minor
Minor
Recommended Action
Check protection mode for far-end node.
Page 1-57
Chapter 2 Alarms, Events, and Recommended Actions
conditioningAlarms/Events, D through K
Turin Networks
1
Service
Affecting
Default
Turin Networks
Node Operations and Maintenance Guide, Section 1: Fault Management
conditioningAlarms/Events, D through K
Page 1-58
Figure 1-13 Hardware Fault Detection Descriptions
Release OPS4.0.x
Release OPS4.0.x
Alarms/Events,
L through S
Table 1-10 Alarms, Events and Recommended Actions, L through S
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
ethernet_ptp
sdh_ptp
sonet_ptp
shelf
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)
–
Info
Info
Informational; no action required.
LEAK2: Leak
shelf
Leak detected.
–
Minor
Minor
Check and follow your method of
procedures.
LFD: Loss of Frame Delineation
eos
sdh_eos
GFP has lost sync.
SA
Critical
Critical
Check the paths associated with the EOS
members for alarms.
Page 1-59
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
LBC: TXlaser bias current
threshold violation
Alarm: Definition
LINKFAIL: Link failure
Alarm
Profiles
ethernet_ptp
Probable Cause
•
Transmitter/receiver
failure.
Fiber connection lost.
A module along the path
has been removed.
SA
There is a Duplex mode port
parameter mismatch between
the near- and far-end Ethernet
ports.
SA
•
•
LINK_FRCD_DIS: Duplex
mode mismatch
ethernet_ptp
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Critical
Recommended Action
Check connectors, cables, and modules.
Check Ethernet port configuration,
Integrity Status parameter for details. See
the TransNav Management System GUI
Guide, Section 5—Equipment,
Chapter 4—“Ethernet Equipment,”
Ethernet Equipment, page 5-47.
Critical
Critical
Check the Duplex mode of the Ethernet
interfaces.
Turin Networks
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.
•
Release OPS4.0.x
LNKBCPTY3: Link broadcast
message parity error
shelf
Unused.
–
Minor
Minor
Unused.
LNKBLKCNT3: Link block
count error
shelf
Unused.
–
Minor
Minor
Unused.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-60
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
LNKBLKPTY3: Link block
parity error
shelf
Unused.
–
Minor
Minor
Unused.
LNKCRC3: Link CRC error
Unused.
–
Minor
Minor
Unused.
LNKCSUM : Link checksum
error
shelf
Unused.
–
Minor
Minor
Unused.
LNKDOWN3: Link down
shelf
Unused.
–
Info
Info
Unused.
LNKERR : Unrecognized link
error
shelf
Unused.
–
Minor
Minor
Unused.
LNKOVFL3: Link overflow
shelf
Unused.
Minor
Minor
Unused.
LNKPAPTY : Link path alarm
parity error
shelf
Unused.
–
Minor
Minor
Unused.
LNKRXCORR3: Link receive
corruption
shelf
Unused.
–
Minor
Minor
Unused.
LNKRXDROP3: Link receive
drop
shelf
Unused.
–
Minor
Minor
Unused.
LNKRXLEN3: Link receive
length error
shelf
Unused.
–
Minor
Minor
Unused.
LNKRXSTAT3: Link receive
stat count error
shelf
Unused.
–
Minor
Minor
Unused.
LNKTXCORR3: Link transmit
corruption
shelf
Unused.
–
Minor
Minor
Unused.
LNKTXDROP3: Link transmit
drop
shelf
Unused.
–
Minor
Minor
Unused.
LNKUP1: Link up
shelf
The link is now up.
–
Info
Info
Informational; no action required.
3
Turin Networks
3
Page 1-61
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
shelf
3
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.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
Technical Assistance Center (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.
–
Warning
Warning
Contact Turin’s Customer Service
Technical Assistance Center (TAC).
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.
–
Warning
Warning
Contact Turin’s Customer Service
Technical Assistance Center (TAC).
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.
–
Warning
Warning
Contact Turin’s Customer Service
Technical Assistance Center (TAC).
LOA: Loss of Assignment
eos
sdh_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.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-62
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK10: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK11: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK12: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK13: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
Page 1-63
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
LOCKOUT-LPS: Lockout of
Protection Ring
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
LOCK_WORK14: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK2: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK3: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK4: 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.
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK5: 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.
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK6: 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.
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
–
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-64
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
shelf
A lockout protection switch
command has been performed
on a working module in a 1:N
Transmux equipment protection
group.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK8: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
LOCK_WORK9: 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.
–
Warning
Warning
If protection required, investigate and
remedy lockout provisioning. Otherwise,
no action required.
Page 1-65
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
LOCK_WORK7: Lockout
automatic protection switching
Alarm: Definition
LOF: Loss of frame
Alarm
Profiles
Probable Cause
ds1_ptp
ds3_ptp
(ds_ptp)
e1_ptp
e3_ptp
ta200
te50
Framing problem on the
incoming signal.
ethernet_ptp
Generic Framing Procedure
(GFP) framing problem on the
incoming bit stream.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Critical
Recommended Action
Inspect all facilities related to the STS
link.
Check remote sites for module
removal/failure alarms.
Check the cable and interface.
SA
Major
Major
Inspect all facilities related to the STS
Bundle.
Turin Networks
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_ptp
sdh_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.
Clean the optical connectors.
Check the upstream node for OC-N
module failure/removal.
Release OPS4.0.x
Verify good optical connections to the
local and far-end OC-N modules.
LOG: Loss of Group
eos
sdh_eos
Loss of Group.
SA
Critical
Critical
Check the paths associated with the EOS
members for alarms.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-66
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
server
shelf
Login attempt has failed.
–
Info
Info
• Try again.
• Check the login log; contact your
system administrator – persistent login
failures could indicate possible
hacking.
LOGINSUCC: Login successful
server
shelf
Login has succeeded.
–
Info
Info
Informational; no action required.
LOGINTERM: Login
terminated
server
shelf
Login has terminated.
–
Info
Info
Informational; no action required.
LOL: Loss of link
te50
SA
Critical
Critical
LOM1: Loss of Multiframe, Rx
path
ethernet_ptp
sdh_ptp
shelf
SA
Critical
Minor
SA
Warning
Warning
Unused.
te50
Unused.
LOM-P: Loss of Multiframe
synchronization - STS
eos
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 the EOS member
order matches that of the remote EOS.
LOM-V: Loss of Multiframe
synchronization - VT
eos
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 the EOS member
order matches that of the remote EOS.
Note: This alarm does not apply for
10GE cards.
Page 1-67
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
LOGINFAIL: Login failed
Alarm: Definition
LOP-P: Loss of Pointer – Path
Alarm
Profiles
ds3_ptp
(ds_ptp)
e3_ptp
sonet_ptp
sonet_sts
Probable Cause
Service
Affecting
Default
SA
Valid H1/H2 pointer bytes are
missing from the STS path
overhead.
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Minor
Recommended Action
Check the cabling and physical
connections on the reporting module.
Verify cross-connects.
Check network timing synchronization.
Verify that the expected bandwidth and
received bandwidth are the same.
If the alarm persists, replace the module.
Turin Networks
LOP-V1: Loss of Pointer – VT
ethernet_ptp1
Valid pointer bytes are missing.
SA
Critical
Minor
Check the cabling and physical
connections on the reporting module.
ta200
te50
Valid pointer bytes are missing.
SA
Critical
Critical
Check the cabling and physical
connections on the reporting module.
ds1_ptp
ds3_ptp
(ds_ptp)
e3_ptp
shelf
sonet_ptp
sonet_vt
sonet_sts
Valid pointer bytes are missing
from the VT overhead.
SA
Critical
Minor
Check the cabling and physical
connections on the reporting module.
ta200
te50
Valid pointer bytes are missing
from the VT overhead.
Verify cross-connects.
Check network timing synchronization.
If the alarm persists, replace the module.
SA
Critical
Critical
Check the cabling and physical
connections on the reporting module.
Verify cross-connects.
Check network timing synchronization.
Release OPS4.0.x
If the alarm persists, replace the module.
sdh_ptp
See TU-LOP.
n/a
n/a
n/a
See TU-LOP.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-68
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
LOP-VC1: Loss of Pointer – VC
Alarm
Profiles
e1_ptp
sdh_ptp
Probable Cause
Valid pointer bytes are missing
from the VC overhead.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Minor
Recommended Action
Check the cabling and physical
connections on the reporting module.
Verify cross-connects.
Check network timing synchronization.
If the alarm persists, replace the module.
LOS: Loss of signal
n
shelf
Loss of signal on BITS 1 or 2.
sonet_ptp
sdh_ptp
n
n
n
n
n
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
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.
–
Minor
Minor
Check the cable and interface.
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.
Page 1-69
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
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.
ds1_ptp
ds3_ptp
(ds_ptp)
e1_ptp
e3_ptp
ta200
te50
Alarm: Definition
LP-BERSD: Bit error rate signal
degrade - Low order Path
Alarm
Profiles
sdh_hp
sdh-lp
sdh_ptp
Probable Cause
The STM signal demultiplexed
and dropped from the STM-N
has exceeded its signal degrade
threshold.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Examine the network for other low order
path bit error rate problems and retrieve
PM data to find a possible common source
of the bit errors.
Perform loopback tests to isolate the
problem.
Check cable connectors and module ports.
Turin Networks
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.
LP-BERSF: Bit error rate signal
degrade - Low order Path
sdh_hp
sdh-lp
sdh_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.
Perform loopback tests to isolate the
problem.
Check cable connectors and module ports.
If an STM-N module is a possible source
of the bit errors, perform a manual
protection switch to the protection unit. If
the BER alarm clears, replace the
defective “working” unit.
Release OPS4.0.x
LPBKEQPT: Equipment
loopback active
ds1_ptp
ds3_ptp
e1_ptp
ethernet_ptp
sdh_ptp
sonet_ptp
Equipment is in active loopback
state.
–
Warning
Warning
Validate this state.
Clear loopback, as required.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-70
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
ds1_ptp
ds3_ptp
e1_ptp
e3_ptp
ethernet_ptp
sdh_ptp
shelf
sonet_ptp
Facility is in active loopback
state.
–
LPBKINBAND: Inband
loopback active
ds3_ptp
An inband loopback is active.
–
LPBKTERM: Terminal
loopback active
ds1_ptp
ds_ptp
e1_ptp
e3_ptp
ethernet_ptp
sdh_ptp
shelf
sonet_ptp
A terminal loopback is active.
LP-LOM: Low order path Loss
of multiframe synchronization
sdh_eos
sdh_eos_ctp
An error is detected in the paths
multiframe indicator.
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Validate this state.
Clear loopback, as required.
Warning
Warning
Validate this state.
Clear loopback, as required.
–
Warning
Warning
Validate this state.
Clear loopback, as required.
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.
Note: This alarm does not apply for
10GE cards.
LP-MND: Low order path
Member not de-skewable
sdh_eos
sdh_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.
Page 1-71
Check the EOS member status to
determine which paths have exceeded the
delay and reroute them.
Note: This alarm does not apply for
10GE cards.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
LPBKFACILITY: Facility
loopback active
Default Severity
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
LP-PLM: Payload label
mismatch received - Low order
Path
sdh_hp
sdh-lp
sdh_ptp
n
LP-RDI: Remote Defect
Indication - Low order Path
sdh_hp
sdh-lp
sdh_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_hp
sdh-lp
sdh_ptp
n
The signal demultiplexed
from the STM-N contains a
remote failure indication.
The far-end node has
detected path defects
coming from the local site.
–
Warning
Warning
Determine the defects found at the far-end
node.
n
n
LP-RFICON: Remote failure
indication, connectivity defect Low order Path
sdh_hp
sdh-lp
sdh_ptp
Invalid byte in the Low
Order path overhead.
The payload does not match
what the signal label is
reporting.
Far end path has an LP-UNEQ
or LP-TIM alarm.
SA
Critical
Minor
Connect correct payload.
Verify that the payload is the same as the
provisioned payload/service.
Verify your payload connections.
Clear path alarms from the far-end node.
–
Warning
Warning
Verify your payload connections.
Check for far end alarms, especially
LP-UNEQ and LP-TIM.
Refer to the recommended actions for
LP-UNEQ and LP-TIM.
LP-RFIPAY: Remote failure
indication, payload defect - Low
order Path
sdh_hp
sdh-lp
sdh_ptp
Far end path has a LP-PLM
alarm.
–
Warning
Warning
Verify your payload connections.
Check for far end alarms, especially
LP-PLM.
Refer to the recommended actions for
LP-PLM.
Release OPS4.0.x
LP-RFISVR: Remote failure
indication, server defect - Low
order Path
sdh_hp
sdh-lp
sdh_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.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-72
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
LP-SQM: Low order path
Sequence ID mismatch
Alarm
Profiles
sdh_eos
sdh_eos_ctp
Probable Cause
The member sequence number
is in error.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Critical
Recommended Action
If non-LCAS, check that the order of
members in the remote EOS matches the
local order.
Note: This alarm does not apply for
10GE cards.
LP-TIM: Trace identifier
mismatch - Low order Path
The expected path trace string
does not match the received path
trace string.
SA
sdh_hp
sdh-lp
sdh_ptp
No payload is received on an
activated service.
SA
LSDBOVFL : Exceeded
maximum number of LSAs
shelf
Unused.
–
Minor
Minor
Unused.
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.
LP-UNEQ: Unequipped - Low
order Path
1
Critical
Minor
Check configuration of path source or
cross-connect.
Match the path trace string on both ends of
the path.
Critical
Minor
Check your connection.
Connect your proper payload.
Check the service source.
Check your method of procedures.
Page 1-73
LWWTR: Low water
shelf
The water level is too low.
–
Minor
Minor
Check your method of procedures.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
ssdh_hp
sdh-lp
sdh_ptp
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.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.
–
Info
Info
Informational; no action required.
MAN_ON_PROT: Manual
protection switching
shelf
A manual protection switch has
been executed on the protecting
port of a protection group.
–
Info
Info
Informational; no action required.
MAN_ON_WORK: Manual
protection switching
shelf
A manual protection switch has
been executed on a working port
of a protection group.
–
Info
Info
Informational; no action required.
MAN-TX-OFF: Transmitter
manually disabled
ethernet_ptp
sdh_ptp
sonet_ptp
Operator disabled the optical
laser.
–
Info
Info
Informational; no action required.
MAN-TX-ON: Transmitter
manually enabled
ethernet_ptp
sdh_ptp
sonet_ptp
Operator enabled the optical
laser.
–
Info
Info
Informational; no action required.
MAXAGE1: Maximum age
shelf
Unused.
–
Minor
Minor
Unused.
MISC: Misc (default)
shelf
–
Minor
Minor
MND-P: Member not
de-skewable - STS
eos
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.
MND-V: Member not
de-skewable - VT
eos
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.
Note: This alarm does not apply to
10GE cards.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-74
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
MPU_BATTERY_A: Battery A
alarm
ta200
SA
Critical
Critical
MPU_BATTERY_B: Battery B
alarm
ta200
SA
Critical
Critical
MS-AIS: Alarm Indication
Signal - Multiplex Section
sdh_ptp
SA
Critical
Minor
An upstream failure occurred at
the multiplex section layer.
Recommended Action
Check the equipment upstream.
Clear upstream alarms.
Verify your multiplex section payload
connections.
sdh_ptp
n
n
n
n
The BER on the incoming
STM-N line has exceeded
the signal degrade threshold.
A connector in the STM-N
optical link could be dirty.
An STM-N module
hardware problem could
exist.
Fiber could be bent or
damaged.
–
Critical
Minor
Verify the local receive optical levels, as
well as the upstream transmit levels.
Verify good optical connections.
Clean optical cable connectors and module
ports.
If an STM-N module is a possible source
of the bit errors, perform a manual
protection switch to the protection unit. If
the BER alarm clears, replace the
defective “working” unit.
Check the remote (source) Transmit and
fiber connection.
Check fiber for bends or damage.
If the problem persists, contact Turin’s
Customer Service Technical Assistance
Center (TAC).
Page 1-75
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
MS-BERSD: BER signal
degrade - Multiplex Section
Alarm: Definition
MS-BERSF: BER signal fail Multiplex Section
Alarm
Profiles
sdh_ptp
Probable Cause
n
n
n
n
The BER on the incoming
STM-N line has exceeded
the signal fail threshold.
A connector in the STM-N
optical link could be dirty.
An STM-N module
hardware problem could
exist.
Fiber could be bent or
damaged.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Minor
Recommended Action
Verify the local receive optical levels, as
well as the upstream transmit levels.
Verify good optical connections.
Clean optical cable connectors and module
ports.
If an STM-N module is a possible source
of the bit errors, perform a manual
protection switch to the protection unit. If
the BER alarm clears, replace the
defective “working” unit.
Turin Networks
Check the remote (source) Transmit and
fiber connection.
Check fiber for bends or damage.
Release OPS4.0.x
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.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-76
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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
ta200
SA
Critical
Critical
NO_PRIMARY_SERVER: No
primary TransNav server
server
The primary server was not
found.
SA
Major
Warning
NODEEQMIS: Node equipment
mismatch
server
Server-Agent equipment
mismatch.
SA
Check connectivity.
If no primary server in the network, set up
a primary server in the network
environment.
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_ptp
sdh_ptp
The node ID selected is already
in use.
–
Minor
Minor
Check all node IDs. Verify that they are
each unique.
Page 1-77
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
NETSYNC: Network object
synchronization failure
Alarm: Definition
NODESYNC: Node
synchronization
Alarm
Profiles
server
Probable Cause
n
n
Discovery of and
synchronization with a new
node.
GCM protection switch.
Service
Affecting
Default
SA
NSA
(Unprotected)
(Protected)
Recommended Action
–
Warning
Warning
• Wait for node synchronization to
complete.
• Check network server connections.
–
Warning
Warning
Enable LCAS on the remote nodes EOS.
Turin Networks
NO-REMOTE-LCAS: No
remote LCAS
eos
sdh_eos
shelf
The remote peer does not have
LCAS capability or the
capability is undetermined.
NPM: No provisioned members
eos
sdh_eos
lag
No members have been
provisioned.
shelf
A door is open in the
environment.
–
OPENDR: Door open
Default Severity
Check remote peer configuration,
capability, and connectivity.
SA
Critical
Critical
Add CTP members to the EOS port.
Add ports to the LAG.
Minor
Minor
Validate that the door should be open.
Close the door, as necessary.
Release OPS4.0.x
OPR: Optical power received
threshold violation
ethernet_ptp
sdh_ptp
sonet_ptp
shelf
Received optical power does not
meet guaranteed value.
–
Warning
Warning
Check interface.
OPT: Optical power transmitted
threshold violation
ethernet_ptp
sdh_ptp
sonet_ptp
shelf
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.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-78
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
OVERTEMP: Fan tray
temperature has exceeded a
maximum value
1
Alarm
Profiles
shelf
Probable Cause
Fan tray temperature has
exceeded 56ºC.
Service
Affecting
Default
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Minor
Minor
Recommended Action
Check that the temperature of the room is
not abnormally high.
Replace the fan tray air filter.
Page 1-79
shelf
OVERVOLTAGE_B1:
Exceeded a maximum voltage
value - Enhanced GCM_B
shelf
PCASQLCH1: PCA channel
squelched
sonet_ptp
sdh_ptp
Extra traffic carried on
protection channel(s) has been
squelched due to a protection
switch.
PDI-n (P, n<2)1: Payload defect
indicator
ds3_ptp
(ds_ptp)
e3_ptp
sdh_hp
sdh-lp
sdh_ptp
sonet_sts
Payload defect indication.
SA
Minor
Minor
Check cable connectors and module ports.
sonet_ptp
sdh_ptp
Payload defect indication.
–
Minor
Minor
Clean the fiber connections.
GCM_A has triggered due to an
over voltage condition.
–
Minor
Minor
Check power system, breaker, fuse, and
related cabling for power input A.
–
Minor
Minor
Check power system, breaker, fuse, and
related cabling for power input B.
–
Minor
Minor
Clear the protection switch.
The Enhanced GCM triggers the
over-voltage alarm at -60.5
VDC. It clears this alarm at
-58.5 VDC.
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.
Check equipment ring topology
configuration.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
OVERVOLTAGE_A :
Exceeded a maximum voltage
value - Enhanced GCM_A
Alarm: Definition
PDI-n (1<n<5)1:Payload defect
indicator
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
ds3_ptp
(ds_ptp)
e3_ptp
Payload defect indication.
SA
Major
Minor
For DS3/EC1 modules, check cable
connectors and module ports.
sonet_ptp
sdh_ptp
Payload defect indication.
SA
Major
Minor
For OC-N modules, clean the fiber
connections.
ds3_ptp
(ds_ptp)
e3_ptp
Payload defect indication.
SA
Critical
Minor
For DS3/EC1 modules, check cable
connectors and module ports.
sonet_ptp
sdh_ptp
Payload defect indication.
SA
Critical
Minor
For OC-N modules, clean the fiber
connections.
PKTRETX1: An OSPF packet
has been retransmitted
shelf
Unused.
–
Minor
Minor
Unused.
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.
PDI-n (n>4)1:Payload defect
indicator
Turin Networks
Check for proper cabling and that local
and remote port configurations match.
Release OPS4.0.x
PLCPLOF1: PLCP (Physical
Layer Convergence Procedure)
loss of frame
ds3_ptp
(ds_ptp)
e3_ptp
Unused.
SA
Critical
Minor
Unused.
PLCPRFI1: PLCP (Physical
Layer Convergence Procedure)
Remote Failure Indication
ds3_ptp
(ds_ptp)
e3_ptp
Unused.
–
Warning
Info
Unused.
PLCR: Partial loss of capacity receive
eos
sdh_eos
Capacity loss on path.
SA
Critical
Critical
Check the paths associated with the EOS
members for alarms.
PLCT: Partial loss of capacity transmit
eos
sdh_eos
Capacity loss on path.
SA
Critical
Critical
Check the paths associated with the EOS
members for alarms.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-80
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
sonet_ptp
sdh_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_ptp
sonet_ptp
sonet_sts
n
PLM-P: Path label mismatch
ta200
te50
Payload label mismatch on the
path.
PLM-V: Payload label mismatch
received
ds1_ptp
ds3_ptp
(ds_ptp)
e3_ptp
shelf
sonet_ptp
sonet_vt
sonet_sts
n
te50
n
n
n
n
PLM-VC: Payload label
mismatch received - VC
e1_ptp
sdh_ptp
n
n
Invalid C2 byte (signal label
byte) in the SONET path
overhead.
The payload does not match
what the signal label is
reporting.
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
–
Warning
Warning
Contact Turin’s Customer Service
Technical Assistance Center (TAC)..
SA
Critical
Minor
Connect correct payload.
Verify that the payload is the same as the
provisioned payload/service.
Page 1-81
–
Warning
Warning
Verify that the payload is the same as the
provisioned payload/service.
Invalid byte in the path
overhead.
The payload does not match
what the signal label is
reporting.
SA
Critical
Minor
Connect correct payload.
Invalid byte in the path
overhead.
The payload does not match
what the signal label is
reporting.
–
Invalid byte in the path
overhead.
The payload does not match
what the signal label is
reporting.
SA
Verify that the payload is the same as the
provisioned payload/service.
Warning
Warning
Connect correct payload.
Verify that the payload is the same as the
provisioned payload/service.
Critical
Minor
Connect correct payload.
Verify that the payload is the same as the
provisioned payload/service.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
PLINESQL1: Persistent line
squelching
Service
Affecting
Default
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
PMCFG: PM configuration
error
ds3_ptp
(ds_ptp)
e1_ptp
e3_ptp
ethernet_ptp
sonet_ptp
sdh_ptp
PM configuration is incorrect.
–
Warning
Warning
Check configuration.
PMDATALOST: Performance
data lost
server
shelf
PM data loss.
–
Info
Info
Informational; no action required.
POWER: Commercial power
failure
shelf
The commercial power source
has failed.
–
Minor
Minor
Check and follow your method of
procedures.
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.
–
Minor
Minor
Check power system, breaker, fuse, and
related cabling for power input A.
PWFAIL-B: Power
problem —power input B failed
shelf
GMT B fuse, cabling, circuit
breaker, or power system unit
has failed.
–
Minor
Minor
Check power system, breaker, fuse, and
related cabling for power input B.
PWR-48: 48VDC power supply
failure
shelf
Commercial fuse, cabling,
circuit breaker, or power system
unit has failed.
–
Minor
Minor
Check and follow your method of
procedures.
QEFAIL: Queue Engine fail
shelf
Internal forwarding queue
engine error.
SA
Critical
Critical
Contact Turin’s Customer Service
Technical Assistance Center (TAC).
RECTFAIL2: Rectifier failure
shelf
Rectifier has failed.
–
Minor
Minor
Check and follow your method of
procedures.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-82
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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
Technical Assistance Center (TAC).
Page 1-83
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
RECTHIGH2: Rectifier high
voltage
Alarm: Definition
RFI-L: Remote failure
indication – Line
Alarm
Profiles
Probable Cause
ds3_ptp
(ds_ptp)
ta200
te50
n
sonet_ptp
n
n
n
n
Service
Affecting
Default
Turin Networks
The locally received EC-1
signal contains an RFI.
The local EC-1 module is
sending a bad signal to the
remote node.
–
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.
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Check module/port.
Check cable and connections.
Check for and resolve LOS, LOF, and AIS
alarms in the far-end node.
Warning
Warning
Check module/port.
Check for and resolve LOS, LOF, and
AIS-L alarms in the far-end node.
Verify the output of the local OC-N
module for level degradation/dirty optical
connectors.
Clean the optical connectors.
Check the fiber connection on adjacent
equipment.
RFI-P: Remote failure
indication – Path
ds3_ptp
(ds_ptp)
e3_ptp1
ta200
te50
n
sonet_ptp
sonet_sts
n
n
n
Release OPS4.0.x
The signal demultiplexed
from the EC-1 contains an
RFI.
The far-end node has
detected path defects
coming from the local site.
–
The STS-1 signal
demultiplexed from the
OC-N contains an RFI-P.
The far-end node has
detected path defects
coming from the local site.
SA
Warning
Warning
Determine the defects found at the far-end
node.
Verify your payload connections.
Clear path alarms such as LOP-P, AIS-P,
PLM-P, TIM-P, and UNEQ-P from the
far-end node.
Warning
Warning
Determine the defects found at the far-end
node.
Verify your payload connections.
Clear path alarms such as LOP-P, AIS-P,
and UNEQ-P from the far-end node.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-84
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
RFI-V: Remote failure
indication
Alarm
Profiles
ds1_ptp
ds3_ptp
(ds_ptp)
sonet_ptp
sonet_vt
sonet_sts
shelf
ta200
te50
n
n
n
n
RFI-VC: Remote failure
indication
e1_ptp
sdh_ptp
n
n
The VT signal
demultiplexed from the DS1
contains an RFI-V.
The far-end node has
detected VT path defects
coming from the local site.
–
The low order signal
demultiplexed from the
STM contains an RFI-V.
The far-end node has
detected low order path
defects coming from the
local site.
–
The low order signal
demultiplexed from the
STM contains an RFI-VC.
The far-end node has
detected low order path
defects coming from the
local site.
–
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Warning
Recommended Action
Determine the defects found at the far-end
node.
Verify your payload connections.
Clear path alarms such as LOP-P, AIS-P,
PLM-P, TIM-P, and UNEQ-P from the
far-end node.
Warning
Warning
Determine the defects found at the far-end
node.
Verify your payload connections.
Clear path alarms such as LOP-V,
AU-AIS, LP-PLM, LP-TIM, and
LP-UNEQ from the far-end node.
Warning
Warning
Determine the defects found at the far-end
node.
Verify your payload connections.
Clear path alarms such as LOP-V,
AU-AIS, LP-PLM, LP-TIM, and
LP-UNEQ from the far-end node.
Page 1-85
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
e3_ptp1
sdh_ptp
Probable Cause
Service
Affecting
Default
Alarm: Definition
RFICON: Remote failure
indication – Connectivity defect
Alarm
Profiles
Probable Cause
ds3_ptp
(ds_ptp)
sonet_ptp
sonet_sts
Far end path has an UNEQ-P or
TIM-P alarm.
e3_ptp
sdh_ptp
Far end path has an UNEQ-P or
TIM-P alarm.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Info
Recommended Action
Verify your payload connections.
Check for far end alarms, especially
UNEQ-P and TIM-P.
Refer to the recommended actions for
UNEQ and TIM.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
UNEQ-P and TIM-P.
Refer to the recommended actions for
UNEQ-P and TIM-P.
Turin Networks
RFICON-V: Remote failure
indication – Connectivity defect
ds1_ptp
ds3_ptp
(ds_ptp)
shelf
sonet_ptp
sonet_vt
sonet_sts
Far-end VT path has an
UNEQ-V or TIM-P alarm.
e3_ptp
sdh_ptp
Far end VC path has an
LP-UNEQ or LP-TIM alarm.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
UNEQ-V and TIM-V.
Refer to the recommended actions for
UNEQ and TIM.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
LP-UNEQ and LP-TIM.
Refer to the recommended actions for
LP-UNEQ and LP-TIM.
Release OPS4.0.x
RFICON-VC: Remote failure
indication – Connectivity defect
e1_ptp
sdh_ptp
Far-end VC path has an
LP-UNEQ or LP-TIM alarm.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
LP-UNEQ and LP-TIM.
Refer to the recommended actions for
LP-UNEQ and LP-TIM.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-86
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
RFIPAY: Remote failure
indication – Payload defect
Alarm
Profiles
Probable Cause
ds3_ptp
(ds_ptp)
sonet_ptp
sonet_sts
Far end path has a PLM-P
alarm.
e3_ptp
sdh_ptp
Far end path has a HP-PLM
alarm.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Info
Recommended Action
Verify your payload connections.
Check for far end alarms, especially
PLM-P.
Refer to the recommended actions for
PLM.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
HP-PLM.
RFIPAY-V: Remote failure
indication – Payload defect
ds1_ptp
ds3_ptp
(ds_ptp)
shelf
sonet_ptp
sonet_vt
sonet_sts
Far end path has a PLM-V
alarm.
e3_ptp
sdh_ptp
Far end path has a LP-PLM
alarm.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
PLM-V.
Refer to the recommended actions for
PLM.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
LP-PLM.
Refer to the recommended actions for
LP-PLM.
RFIPAY-VC: Remote failure
indication – Payload defect
e1_ptp
sdh_ptp
Far end path has a LP-PLM
alarm.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
LP-PLM.
Page 1-87
Refer to the recommended actions for
LP-PLM.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
Refer to the recommended actions for
HP-PLM.
Alarm: Definition
RFISVR: Remote failure
indication – Server defect
Alarm
Profiles
Probable Cause
ds1_ptp
ds3_ptp
(ds_ptp)
sonet_ptp
sonet_sts
Far end path has an AIS-P or
LOP-P alarm.
e3_ptp
sdh_ptp
Far end path has an AIS-P or
LOP-P alarm.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Warning
Info
Recommended Action
Verify your payload connections.
Check for far end alarms, especially AIS-P
and LOP-P.
Refer to the recommended actions for
AIS-P and LOP-P.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially AIS-P
and LOP-P.
Refer to the recommended actions for
AIS-P and LOP-P.
Turin Networks
RFISVR-V: Remote failure
indication – Server defect
ds1_ptp
ds3_ptp
(ds_ptp)
shelf
sonet_ptp
sonet_vt
sonet_sts
Far end path has an AIS-V or
LOP-V alarm.
e3_ptp
sdh_ptp
Far end path has an TU-AIS or
TU-LOP alarm.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
AIS-V and LOP-V.
Refer to the recommended actions for
AIS-V and LOP-V.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
TU-AIS and TU-LOP.
Refer to the recommended actions for
TU-AIS and TU-LOP.
Release OPS4.0.x
RFISVR-VC: Remote failure
indication – Server defect
e1_ptp
sdh_ptp
Far end path has a TU-AIS or
TU-LOP alarm.
SA
Warning
Info
Verify your payload connections.
Check for far end alarms, especially
TU-AIS and TU-LOP.
Refer to the recommended actions for
TU-AIS and TU-LOP.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-88
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
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.
SA
Critical
Minor
Check configuration of path source or
cross-connect.
SA
Critical
Critical
Check connectivity and configuration.
–
Major
Major
Check that the temperature of the room or
equipment is not abnormally high.
RTS: Request to send on MPS
IM
te50
Request to send not present.
SENSORFAIL: Thermal sensor
failure
shelf
The thermal sensor on a line or
control module has failed.
Match the path trace string on both ends of
the path.
Contact Turin’s Customer Service
Technical Assistance Center (TAC) for
assistance if the temperature is normal and
this failure persists.
Page 1-89
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
server
shelf
Event identifies the server role
as primary or secondary.
–
Info
Info
Informational; no action required.
SETOPER: Set operation
performed
server
shelf
A set operation has been
performed.
–
Info
Info
Informational; no action required.
SFO1: Sync frequency offset
ds3_ptp
(ds_ptp)
sonet_ptp
EC-1 or SONET facility timing.
–
Minor
Minor
Check timing signal quality.
e3_ptp
sdh_ptp
SONET facility timing.
–
Minor
Minor
Check timing signal quality.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
RLSD: Receive Line Signal
Detect on MPS IM
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
SFPMIS: SFP mismatch
ethernet_ptp
sdh_ptp
sonet_ptp
shelf
There is a mismatch on the SFP
interface.
–
Critical
Minor
Check interface.
SFPRMV: SFP removed
ethernet_ptp
sdh_ptp
sonet_ptp
shelf
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_ptp
sdh_ptp
n
–
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.
n
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.
Be sure that the STS channels have been
properly provisioned. Check equipment
ring topology configuration.
Release OPS4.0.x
SQM1: Sequence number
change
ethernet_ptp
shelf
Unused.
SA
Critical
Minor
Unused.
SQM-P: Sequence ID
mismatch- STS
eos
eos_ctp
The member sequence number
is in error.
SA
Critical
Critical
This is an eos_ctp member alarm. If
non-LCAS, check that the order of
members in the remote EOS matches the
local order.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-90
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
SQM-V: Sequence ID
mismatch- VT
Alarm
Profiles
eos
eos_ctp
Probable Cause
The member sequence number
is in error.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Critical
Recommended Action
This is an eos_ctp member alarm. If
non-LCAS, check that the order of
members in the remote EOS matches the
local order.
Note: This alarm does not apply to
10GE cards.
shelf
All LCAS VC bundle members
have failed. Also see path
alarms for each VC bundle
member (facility). The VC
bundle operational state is set to
Disabled until at least one
member returns.
SVC_STATUS1: Service status
report
server
shelf
Unused.
SWCRPT: Software corruption
server
shelf
Software did not load or loaded
with errors.
SWERR: Software error
all objects
The software has detected an
unexpected error.
SWITCH1: Pointer switch
ethernet_ptp
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.
SA
–
SA
–
SA
–
Critical
Minor
• Inspect all VC bundle facilities.
• Check remote sites for module
removal/failure alarms or disabled
Ethernet transmitter.
• Check the cables and interfaces.
Info
Info
Unused.
Critical
Minor
Contact Turin’s Customer Service
Technical Assistance Center (TAC).
Info
Info
Contact Turin’s Customer Service
Technical Assistance Center (TAC).
Critical
Minor
Unused.
Info
Info
Informational; no action required.
Page 1-91
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, L through S
Turin Networks
SSF: Server Signal Fail
Alarm: Definition
SWITCH_TO_SECT1: Traffic
switch on optimized 1+1 APS
working section 1
Alarm
Profiles
shelf
Probable Cause
Traffic has switched on the
optimized 1+1 APS
bi-directional working section 1.
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
–
Info
Info
Informational; no action required.
–
Warning
Warning
• Verify that the switch was expected.
• Check the switch-from section for
degraded performance or other relevant
alarm conditions.
Note: Section 1 and 2 are
equal working sections, each
with a permanent traffic bridge.
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.
Turin Networks
Note: Section 1 and 2 are
equal working sections, each
with a permanent traffic bridge.
Release OPS4.0.x
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.
–
Info
Info
Informational; no action required.
SW_UPG_PROG
shelf
Software upgrade is in progress.
–
Info
Info
Informational; no action required.
SYSREF: System reference lock
failed
shelf
Lock on system reference is lost.
–
Critical
Critical
Check system reference.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, L through S
Page 1-92
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Release OPS4.0.x
Table 1-10 Alarms, Events and Recommended Actions, L through S (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
SYSREF_EVENT: System lost
reference lock
shelf
System lost reference lock.
SYNCFAIL2: Synchronization
reference failure
sonet_ptp
sdh_ptp
OC-N facility timing.
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
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Info
Info
Check for SYSREF alarm.
Minor
Minor
Check timing signal quality.
Alarms/Events,
TA200
Table 1-11 Alarms, Events and Recommended Actions, TA200
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
(Unprotected)
Recommended Action
(Protected)
Page 1-93
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.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, TA200
Turin Networks
1
Service
Affecting
Default
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
(Unprotected)
Recommended Action
(Protected)
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.
Turin Networks
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, TA200
Page 1-94
Table 1-11 Alarms, Events and Recommended Actions, TA200 (continued)
Release OPS4.0.x
Release OPS4.0.x
Alarms/Events,
TB through TZ
Table 1-12 Alarms, Events and Recommended Actions, TB through TZ
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Page 1-95
ds1_ptp
ds3_ptp
(ds_ptp)
e3_ptp
ethernet_ptp
sonet_ptp
sdh_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
list 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
ethernet_ptp
sdh_ptp
sonet_ptp
shelf
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_ptp
sonet_ptp
sdh_ptp
The expected path trace string
(J1 byte in the path overhead)
does not match the received path
trace string.
SA
Critical
Minor
Check configuration of path source or
cross-connect.
e3_ptp
sonet_ptp
sonet_sts
te50
The expected path trace string
does not match the received path
trace string.
SA
TIM-P: Trace identifier
mismatch - Path
Match the path trace string on both ends of
the path.
Critical
Minor
Check configuration of path source or
cross-connect.
Match the path trace string on both ends of
the path.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, TB through TZ
Turin Networks
TCA: Threshold crossing alert
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
TIM-S: Trace identifier
mismatch - Section
e3_ptp
sonet_ptp
te50
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_ptp
ds3_ptp
(ds_ptp)
e3_ptp
shelf
sdh_ptp
sonet_ptp
sonet_vt
sonet_sts
te50
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_ptp
ds3_ptp
(ds_ptp)
e3_ptp
sdh_ptp
sonet_ptp
sonet_vt
sonet_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
server
shelf
The user session has been idle
for two hours.
–
Info
Info
Start a new user session.
TIMEOUTWARN: Session
terminate warning
server
shelf
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.
Critical
Minor
Check trace configuration at each end.
SA
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, TB through TZ
Page 1-96
Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued)
Release OPS4.0.x
Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Page 1-97
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
eos
sdh_eos
Total capacity lost.
SA
Critical
Critical
Check the ingress transport link for
alarms. Check the paths associated with
the EOS members for alarms.
TLCT: Total loss of capacity transmit
eos
sdh_eos
Total capacity lost.
SA
Critical
Critical
Check the ingress transport link for
alarms. Check the paths associated with
the EOS members for alarms.
TOOMANYEVENTS1: Too
many events in the server
server
Server event log too large.
–
Critical
Critical
Clear event log.
TOPOMIS2: Topology
mismatch
sonet_ptp
sdh_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
Technical Assistance Center (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.
SA
Critical
Minor
If this alarm persists for more than 5
minutes, contact Turin’s Customer Service
Technical Assistance Center (TAC).
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.
SA
Critical
Minor
If this alarm persists for more than 5
minutes, contact Turin’s Customer Service
Technical Assistance Center (TAC).
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
Critical
Minor
If this alarm persists for more than 5
minutes, contact Turin’s Customer Service
Technical Assistance Center (TAC).
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, TB through TZ
Turin Networks
TLC: Total loss of capacity
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
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.
SA
Critical
Minor
If this alarm persists for more than 5
minutes, contact Turin’s Customer Service
Technical Assistance Center (TAC).
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.
SA
Critical
Minor
If this alarm persists for more than 5
minutes, contact Turin’s Customer Service
Technical Assistance Center (TAC).
TSS-LINE1-OOB-GCMA:
GCMA Line Ref 1 - Out of
Band
shelf
GCMA 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
Technical Assistance Center (TAC).
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
Technical Assistance Center (TAC).
TSS-LINE2-OOB-GCMA:
GCMA Line Ref 2 - Out of
Band
shelf
GCMA Line Reference 2 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
Technical Assistance Center (TAC).
TSS-LINE2-OOB-GCMB:
GCMB Line Ref 2 - Out of Band
shelf
GCMB Line Reference 2 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
Technical Assistance Center (TAC).
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, TB through TZ
Page 1-98
Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued)
Release OPS4.0.x
Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Page 1-99
shelf
GCMA Line Reference 3 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
Technical Assistance Center (TAC).
TSS-LINE3-OOB-GCMB:
GCMB Line Ref 3 - Out of Band
shelf
GCMB Line Reference 3 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
Technical Assistance Center (TAC).
TSS-LINE4-OOB-GCMA:
GCMA Line Ref 4 - Out of
Band
shelf
GCMA Line Reference 4 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
Technical Assistance Center (TAC).
TSS-LINE4-OOB-GCMB:
GCMB Line Ref 4 - Out of Band
shelf
GCMB Line Reference 4 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
Technical Assistance Center (TAC).
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.
–
Warning
Warning
Clear the LOS, LOF, or AIS-L alarm.
Refer to the recommended actions for
those alarms in this table.
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.
–
Warning
Warning
Clear the LOS, LOF, or AIS-L alarm.
Refer to the recommended actions for
those alarms in this table.
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.
–
Warning
Warning
Clear the LOS, LOF, or AIS-L alarm.
Refer to the recommended actions for
those alarms in this table.
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, TB through TZ
Turin Networks
TSS-LINE3-OOB-GCMA:
GCMA Line Ref 3 - Out of
Band
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
Release OPS4.0.x
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.
–
Warning
Warning
Clear the LOS, LOF, or AIS-L alarm.
Refer to the recommended actions for
those alarms in this table.
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.
–
Info
Info
Informational; no action required.
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.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events, TB through TZ
Page 1-100
Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued)
Release OPS4.0.x
Table 1-12 Alarms, Events and Recommended Actions, TB through TZ (continued)
Alarm: Definition
TU-AIS: Alarm indication
signal – Tributary Unit)
TU-LOP: Loss of Pointer –
Tributary Unit
Alarm
Profiles
Probable Cause
sdh_hp
sdh-lp
sdh_ptp
An upstream failure occurred at
the tributary unit path layer.
sdh_hp
sdh-lp
sdh_ptp
Valid pointer bytes are missing
from the tributary unit overhead.
Service
Affecting
Default
SA
Default Severity
SA
NSA
(Unprotected)
(Protected)
Critical
Minor
Recommended Action
Check the equipment upstream.
Clear upstream alarms.
Verify your tributary unit payload
connections.
SA
Critical
Minor
Check the cabling and physical
connections on the reporting card.
Verify cross-connects.
Check network timing synchronization.
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.
2
Not supported in this release.
3
Environmental alarm inputs are customized by each operator.
Page 1-101
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events, TB through TZ
Turin Networks
If the alarm persists, replace the module.
Table 1-13 Alarms, Events and Recommended Actions, U through Z
Alarm: Definition
Alarm
Profiles
Turin Networks
UNDERVOLTAGE_A1: Below
the minimum voltage value Enhanced GCM_A
shelf
UNDERVOLTAGE_B1: Below
the minimum voltage value Enhanced GCM_B
shelf
UNEQ: Rx Path unequipped
code received
ethernet_ptp
UNEQ-P Unequipped code
signal label received
ds3_ptp
(ds_ptp)
e3_ptp
sonet_ptp
sonet_sts
te50
Probable Cause
GCM_A has triggered due to an
under voltage condition.
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
–
Minor
Minor
Check power system, breaker, fuse, and
related cabling for power input A.
–
Minor
Minor
Check power system, breaker, fuse, and
related cabling for power input B.
SA
Critical
Minor
Check your interface connection.
SA
Critical
Minor
Connect your proper payload and service
source.
The Enhanced GCM triggers the
under-voltage alarm at -40.5
VDC. It clears this alarm at
-42.5 VDC.
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.
No payload is received on an
activated service.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events U through Z
Page 1-102
Alarms/Events
U through Z
Release OPS4.0.x
Release OPS4.0.x
Table 1-13 Alarms, Events and Recommended Actions, U through Z (continued)
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
ds1_ptp
ds3_ptp
(ds_ptp)
shelf
sonet_ptp
sonet_vt
sonet_sts
te50
No payload is received on an
activated service.
SA
e3_ptp
sdh_ptp
See UNEQ-VC.
SA
Critical
Minor
See UNEQ-VC.
UNEQ-VC: Unequipped code
signal label received - VC path
e1_ptp
sdh_ptp
No payload is received on an
activated service.
SA
Critical
Minor
Check your interface connection.
UP1: In service
all objects
Unused.
–
Minor
Minor
Unused.
VCC: Internal voltage threshold
violation
ethernet_ptp
sdh_ptp
sonet_ptp
shelf
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_ptp
sonet_ptp
Incorrect provisioning.
SA
Major
Minor
Check interface and configuration.
UNEQ-V: Unequipped code
signal label received - VT path
Critical
Minor
Recommended Action
Check your interface connection.
Connect your proper payload and service
source.
Page 1-103
Chapter 2 Alarms, Events, and Recommended Actions
Alarms/Events U through Z
Turin Networks
Connect your proper payload and service
source.
Alarm: Definition
Alarm
Profiles
Probable Cause
Service
Affecting
Default
Default Severity
SA
NSA
(Unprotected)
(Protected)
Recommended Action
Turin Networks
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.
SA
Critical
Critical
Check EOS members for path alarms.
XPTRX: Receive transport
failure
lag
Link Integrity detected transport
failure in the receive direction.
SA
Critical
Critical
Check EOS members for path alarms.
XPTTX: Transmit transport
failure
lag
Link Integrity detected transport
failure in the transmit direction.
SA
Critical
Critical
Check EOS members for path alarms.
1
Not supported in this release.
2
Environmental alarm inputs are customized by each operator.
Node Operations and Maintenance Guide, Section 1: Fault Management
Alarms/Events U through Z
Page 1-104
Table 1-13 Alarms, Events and Recommended Actions, U through Z (continued)
Release OPS4.0.x
Release OPS4.0.x
Page 1-105
Chapter 2 Alarms, Events, and Recommended Actions
Turin Networks
Turin Networks
Node Operations and Maintenance Guide, Section 1: Fault Management
Page 1-106
Release OPS4.0.x
S ECTION 1FAULT M ANAGEMENT
Chapter 3
TransNav GUI Service Error Codes
Introduction
This document provides TransNav GUI service error code information to assist you in
troubleshooting TransNav system service request failure indications. See the figure
below.
This chapter includes the following topics:
• Service Activation Failure, page 1-108
• TransNav GUI Service Error Codes, page 1-109
Figure 1-14 TransNav GUI Service Request Error Window
Release OPS4.0.x
Turin Networks
Page 1-107
Node Operations and Maintenance Guide, Section 1: Fault Management
Service Activation Failure
Service
Activation
Failure
If a service request activation fails, use the following Service Request—Show Last
Error procedure to help trace and resolve the problem.
Table 1-14 Service Request—Show Last Error
Step
1
Procedure
Select the service request entry.
Service
Error
Code
Information
Service
Request
Entry
Activation
Failure
Indication
Figure 1-15 Service Request Failure
2
From the Services menu, select Show Last Error.
Figure 1-16 Services Menu—Show Last Error Option
Page 1-108
3
Observe the service error code information and refer to Table 1-15
Service Error Codes and Recommended Actions, page 1-109 for further
troubleshooting details.
4
The Service Request—Show Last Error procedure is complete.
Turin Networks
Release OPS4.0.x
Release OPS4.0.x
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
Turin Networks
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
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/reactive the new service.
• If deactivation/reactivation does not resolve the problem,
then perform a GCM switchover.
• As a last resort, restart the node.
1009
RSVP (resource reservation
protocol) error - MIB TEST
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/reactive the new service.
• If deactivation/reactivation does not resolve the problem,
then perform a GCM switchover.
• As a last resort, restart the node.
1016
RSVP (resource reservation
protocol) error - No path for
reservation
Remote node or link failure.
Retry service request.
TransNav GUI Service Error Codes
TransNav GUI Service Error Codes
Internal error
Chapter 3
Page 1-109
1
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
Turin Networks
Release OPS4.0.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.
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 card was plugged into the slot. (e.g., a
card 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.
Select another resource and retry the service request.
Node Operations and Maintenance Guide, Section 1: Fault Management
TransNav GUI Service Error Codes
Page 1-110
Table 1-15 Service Error Codes and Recommended Actions (continued)
Release OPS4.0.x
Table 1-15 Service Error Codes and Recommended Actions (continued)
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
Turin Networks
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
Card not responding.
Reseat the card. 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.
TransNav GUI Service Error Codes
TransNav GUI Service Error Codes
Invalid Protection interface
Chapter 3
Page 1-111
1209
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
Turin Networks
Release OPS4.0.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, contact the Turin Technical Assistance
Center.
1246
Requested resource is Admin locked
The resource is locked and must be unlocked.
Unlock the resource.
Node Operations and Maintenance Guide, Section 1: Fault Management
TransNav GUI Service Error Codes
Page 1-112
Table 1-15 Service Error Codes and Recommended Actions (continued)
Release OPS4.0.x
Table 1-15 Service Error Codes and Recommended Actions (continued)
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
Turin Networks
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
STS is unavailable to complete E2E service request.
STS already in use.
Check STS. Make another STS selection and retry the service
request.
1266
E2E (End to End) service request;
reverse 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.
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.
TransNav GUI Service Error Codes
TransNav GUI Service Error Codes
No UPSR PG (protection group)
created for the requested UPSR
service
Chapter 3
Page 1-113
1247
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
Turin Networks
1271
Invalid interface
During an end-to-end service, typically strict, a
remote card was incorrectly specified or was
inadvertently removed.
Check the slot/port of each card interface. If it is correct, then
investigate the possibility of a remote card 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.
Check the slot/port. If the problem persists, contact the Turin
Technical Assistance Center.
1274
Used IN label unavailable
During an end-to-end service, the STS used resource
identifier is not found.
Check the slot/port. If the problem persists, contact the Turin
Technical Assistance Center.
1275
Used OUT label unavailable
During an end-to-end service, the STS used resource
identifier is not found.
Check the slot/port. If the problem persists, contact the Turin
Technical Assistance Center.
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.
Check STS number availability across the entire BLSR path.
Release OPS4.0.x
One of the STS labels along the path is already in
use OR a card has been inadvertently pulled during
the E2E service request selection process.
Make another STS number selection as necessary and retry the
service.
Node Operations and Maintenance Guide, Section 1: Fault Management
TransNav GUI Service Error Codes
Page 1-114
Table 1-15 Service Error Codes and Recommended Actions (continued)
Release OPS4.0.x
Table 1-15 Service Error Codes and Recommended Actions (continued)
Service
Error
Code
1285
Service Error Code
String Definition
BLSR label unavailable
Probable Cause
Recommended Action
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.
Turin Networks
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.
TransNav GUI Service Error Codes
TransNav GUI Service Error Codes
Invalid BLSR constraints.
Chapter 3
Page 1-115
1286
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
Turin Networks
Release OPS4.0.x
3021
LC FM error - flow action failed
Too many VLANs have been configured on the
Ethernet card. Ethernet cards support up to 243
VLANs.
• Deactivate any unnecessary Ethernet services to free up
VLANs for the new service.
• Use a different Ethernet card 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 card specified in the service request is
not physically present.
Plug in an appropriate Ethernet card 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 card.
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 card. A SONET
endpoint can only be used with one Ethernet card 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.
Deactivate the conflicting service using the SONET endpoint
and retry the new service 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.
Deactivate the conflicting service using the SONET endpoint
and retry the new service request.
Node Operations and Maintenance Guide, Section 1: Fault Management
TransNav GUI Service Error Codes
Page 1-116
Table 1-15 Service Error Codes and Recommended Actions (continued)
Release OPS4.0.x
Table 1-15 Service Error Codes and Recommended Actions (continued)
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
Turin Networks
One or more VLAN IDs specified in the service
request are already in use for another service on the
Ethernet card.
Deactivate the conflicting service using the VLAN ID and retry
the new service request.
3236
Ethernet card requested in service is
not yet ready to accept new services
The Ethernet card 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 card type is not supported
by EA in this release
The Ethernet card type in the service request is not
supported in this release.
• To use the Ethernet card in question, perform a system
software release upgrade. See Section 7—Software
Upgrades, Chapter 1—“Release TR3.0.x Traverse Software
Upgrade,” page 7-1 for details.
• Choose another Ethernet card 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.
Deactivate the conflicting service using the SONET endpoint
and retry the new 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.
Deactivate the conflicting service using the SONET endpoint
and retry the new service request.
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.
3244
All services using a SONET endpoint must have the
same participation type (SUBSCRIBER or
PROVIDER).
Use the same destination termination point as the previously
activated IAS service and retry the service request.
Page 1-117
TransNav GUI Service Error Codes
TransNav GUI Service Error Codes
VLAN ID requested in service is
already being used in the Ethernet
card
Chapter 3
3229
Service
Error
Code
3247
Service Error Code
String Definition
No free traffic contracts are
available on the Ethernet card
specified in service
Probable Cause
Traffic contract resource allocation failure during
service request. All traffic contracts are in use.
Recommended Action
Deactivate some service using a traffic contract to free up
resources and retry the new service request.
Each Ethernet card 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.
Turin Networks
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 card
SONET endpoint resource allocation failure during
service request. All SONET endpoints are already in
use.
Deactivate the conflicting service using the SONET endpoint
and retry the new service request.
Each Ethernet card supports (typically) 24 SONET
endpoints.
Release OPS4.0.x
3272
Maximum number of TLS TDM
endpoints bound to Ethernet 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 card.
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 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 card. Each TLS instance is identified by
its VLAN ID.
Deactivate all of the active services using another TLS instance
and retry the service request.
Node Operations and Maintenance Guide, Section 1: Fault Management
TransNav GUI Service Error Codes
Page 1-118
Table 1-15 Service Error Codes and Recommended Actions (continued)
Release OPS4.0.x
Table 1-15 Service Error Codes and Recommended Actions (continued)
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
3274
VLAN ID is in use by non-TLS
service on same Ethernet card
The VLAN ID specified in the service request is
already in use by another non-TLS service on the
Ethernet card.
• 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 card
One or more VLAN IDs specified in the service
request are already in use for another TLS service on
a different Ethernet card in the same 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.
A VLAN ID can only be used for TLS on one
Ethernet card at a time in a node.
Turin Networks
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.
Deactivate the conflicting service using the SONET endpoint
and retry the new service 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.
Deactivate the conflicting service using the SONET endpoint
and retry the new service 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 card is required but not present in the
system.
• All the resources are already in use.
• Install a VT Switch card 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.
If the problem persists, contact the Turin Technical Assistance
Center.
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.
TransNav GUI Service Error Codes
TransNav GUI Service Error Codes
Optical facility requested in service
is in use for a Shared-p2p (point to
point) service
Chapter 3
Page 1-119
3276
Service
Error
Code
Service Error Code
String Definition
Probable Cause
Recommended Action
3620
Internal error; Error replicating
generic cross-connect to standby
A system error occurred during the GCM replication
process.
If the problem persists, contact the Turin Technical Assistance
Center.
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 card (card)
already allocated
Ethernet card cannot support any new SONET
endpoints at this time.
Deactivate one or more services using another SONET endpoint
on this Ethernet card and retry the new service request.
Each Ethernet card supports (typically) 24 SONET
endpoints.
Turin Networks
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.
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.
Premium class of service services are using the
required bandwidth.
Release OPS4.0.x
3820
Ethernet card (card) must be created
before adding services
The Ethernet card (card) in the service request does
not exist. The card has not been provisioned.
Provision the Ethernet card and retry the service request.
3824
Backplane bandwidth from Ethernet
card (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 card 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.
Node Operations and Maintenance Guide, Section 1: Fault Management
TransNav GUI Service Error Codes
Page 1-120
Table 1-15 Service Error Codes and Recommended Actions (continued)
S ECTION 2
P ERFORMANCE M ONITORING
S ECTION 2SYSTEM M ONITORING
S ECTION 2
Contents
Chapter 1
Managing Performance
Creating or Modifying a Monitoring Template . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Assigning a PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Assigning a Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Assigning an EOS Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Assigning a Subport PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Assigning a Service PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Assigning a TransAccess 100 Mux PM Template. . . . . . . . . . . . . . . . . . . . . . 2-8
Viewing PM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
PM Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Viewing Port or Subport PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Viewing Service Path PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Viewing Signal Path Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Viewing Capacity Monitoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Generating a PM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Chapter 2
SONET Performance Parameters
DS1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
DS3 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
EC-1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Small Form-Factor Pluggable Optical Port PM . . . . . . . . . . . . . . . . . . . . . . . . 2-28
SONET Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
SONET STS Path Layer PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
SONET VT Path Layer PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
SONET Capacity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Chapter 3
SDH Performance Parameters
E1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
E3 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
SDH High and Low Order Path PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
SDH Port PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
SDH VC-11 and VC-12 Path PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
SDH Capacity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
Chapter 4
Ethernet Performance Parameters
EOS Port PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61
Ethernet 10GbE Equipment PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
Release OPS4.0.x
Turin Networks
Page vii
Node Operations and Maintenance Guide, Section 2 Performance Monitoring
Ethernet Equipment PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
Ethernet Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Ethernet Service Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Small Form-Factor Pluggable Optical Port PM . . . . . . . . . . . . . . . . . . . . . . . . 2-71
List of Figures
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 2-8
Figure 2-9
Figure 2-10
Figure 2-11
Figure 2-12
Figure 2-13
Figure 2-14
Performance Templates Dialog Box . . . . . . . . . . . . . . . . . . . . . . . 2-2
DS1 PM Configuration Template Dialog Box . . . . . . . . . . . . . . . . 2-4
Synchronize Template Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Service PM Template Parameters. . . . . . . . . . . . . . . . . . . . . . . . . 2-7
TransAccess 100 Mux Config Tab . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Object Selection for PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Port Performance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Path Display for Services Screen . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Service Performance (PM) Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Path Display for Service Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Path Overhead Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Viewing VT/TU Capacity Monitoring Data . . . . . . . . . . . . . . . . . . . 2-15
Event Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Reports Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 2-7
Table 2-8
Table 2-9
Table 2-10
Table 2-11
Table 2-12
Table 2-13
Table 2-14
Table 2-15
Table 2-16
Table 2-17
Table 2-18
Table 2-19
Table 2-20
Table 2-21
Creating or Modifying a PM Template . . . . . . . . . . . . . . . . . . . . . . 2-2
Assigning a Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Assigning an EOS Port PM Template . . . . . . . . . . . . . . . . . . . . . . 2-5
Assigning a Subport PM Template . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Assigning a Service PM Template. . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Assigning a TransAccess 100 Mux PM Template . . . . . . . . . . . . . 2-8
Viewing Port or Subport PM Data . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Viewing Service PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Viewing Signal Path Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Viewing VT/TU Capacity Monitoring Data . . . . . . . . . . . . . . . . . . . 2-15
PM Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
DS1 Port PM Parameters—Near End . . . . . . . . . . . . . . . . . . . . . . 2-20
DS1 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . 2-21
DS3 Port PM Parameters—Near End . . . . . . . . . . . . . . . . . . . . . . 2-23
DS3 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . 2-25
EC1 Port PM Parameters—Near-End . . . . . . . . . . . . . . . . . . . . . . 2-26
EC1 Port PM Parameters—Far-End . . . . . . . . . . . . . . . . . . . . . . . 2-27
SFP (and XFP) Optical Port PM Parameters . . . . . . . . . . . . . . . . 2-28
SONET Port PM—Near End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
SONET Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . 2-31
SONET STS Path PM Parameters—Near End. . . . . . . . . . . . . . . 2-33
List of Tables
Page viii
Turin Networks
Release OPS4.0.x
Node Operations and Maintenance Guide, Section 2 Performance Monitoring
Table 2-22
Table 2-23
Table 2-24
Table 2-25
Table 2-26
Table 2-27
Table 2-28
Table 2-29
Table 2-30
Table 2-31
Table 2-32
Table 2-33
Table 2-34
Table 2-35
Table 2-36
Table 2-37
Table 2-38
Table 2-39
Table 2-40
Table 2-41
Table 2-42
Table 2-43
Table 2-44
Release OPS4.0.x
SONET STS Path PM Parameters—Far End . . . . . . . . . . . . . . . . 2-34
SONET VT Path PM Parameters—Near End . . . . . . . . . . . . . . . 2-35
SONET VT Path PM Parameters—Far End. . . . . . . . . . . . . . . . . 2-36
SONET Capacity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
E1 Port PM Parameters—Near End . . . . . . . . . . . . . . . . . . . . . . . 2-40
E1 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . . 2-42
E3 Port PM Parameters–Near End . . . . . . . . . . . . . . . . . . . . . . . . 2-43
E3 Port PM Parameters—Far End . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Number of Errored Blocks that Constitute an SES . . . . . . . . . . . . 2-46
SDH High Order VC Path and
Low Order VC3 PM Parameters—Near End. . . . . . . . . . . . . . . . . 2-46
SDH High Order VC Path and
Low Order VC3 PM Parameters—Far End . . . . . . . . . . . . . . . . . . 2-48
SDH Port PM—Near End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
SDH Port PM—Far End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
Number of Errored Blocks that Constitute an SES . . . . . . . . . . . . 2-55
SDH VC-11 and VC-12 Path PM Parameters—Near End . . . . . . 2-55
SDH VC-11 and VC-12 Path PM Parameters—Far End . . . . . . . 2-57
SDH Capacity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
EOS Port PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Ethernet 10GbE Equipment PM Parameters . . . . . . . . . . . . . . . . 2-63
Ethernet Equipment PM Parameters . . . . . . . . . . . . . . . . . . . . . . 2-64
Ethernet Port PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Ethernet Service Port PM Parameters . . . . . . . . . . . . . . . . . . . . . 2-70
SFP (and XFP) Optical Port PM Parameters . . . . . . . . . . . . . . . . 2-71
Turin Networks
Page ix
Node Operations and Maintenance Guide, Section 2 Performance Monitoring
Page x
Turin Networks
Release OPS4.0.x
S ECTION 2PERFORMANCE M ONITORING
Chapter 1
Managing Performance
Introduction
The TransNav management system provides performance monitoring (PM) functions
to monitor electrical and optical signals. It also provides capacity monitoring functions
to gather switch capacity data for VT and TU cards (cards). 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. The capacity monitoring parameters allow operators to monitor
resource usage using a ‘snapshot’ of the state of switching resources on VT/TU cards
for future planning purposes.
This chapter provides procedures for:
• Creating or Modifying a Monitoring Template, page 2-1
• Assigning a PM Template, page 2-5
• Viewing PM Data, page 2-8
– PM Timing, page 2-8
• Viewing Capacity Monitoring Data, page 2-15
• Report Generation, page 2-16
• Generating a PM Report, page 2-17
Modules (cards) which do not collect PM information may be reserved for
administrative use; contact your system Administrator.
For further information on performance monitoring, capacity monitoring, and the
management system, see the TransNav Management System GUI Guide.
Creating or
Modifying a
Monitoring
Template
Creating or modifying performance monitoring or capacity monitoring templates gives
the user configuration flexibility for threshold default settings and report generation
parameter collection.
Important: Default threshold values in the sonet_ptp_pm and
sdh_ptp_pm template are based on performance monitoring for OC-3 and
STM-1 rates, respectively. Turin recommends customizing these templates
for rates other than OC-3 and STM-1.
Note: Create EC-3/STM-1E alarm profiles with the SONET/SDH templates, like
those for the OC-3/STM-1 ports.
The following procedure describes how to create or modify a monitoring template.
Release OPS4.0.x
Turin Networks
Page 2-1
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Creating or Modifying a Monitoring Template
Table 2-1 Creating or Modifying a PM Template
Step
1
Procedure
In Map View, select Admin, then Performance Templates. The
Performance Templates dialog box displays.
Figure 2-1 Performance Templates Dialog Box
Page 2-2
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Creating or Modifying a Monitoring Template
Table 2-1 Creating or Modifying a PM Template (continued)
Step
Procedure
2
From the Type drop-down list, select the template type. Each ptp template
is used for port or subport; each path template is used for service
performance monitoring; each capacity template is used for switch
capacity 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_10ge_eq_pm: High capacity ethernet equipment
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
sdh_vc_capacity_pm: SDH VT/TU switch capacity monitoring
sonet_path_pm: SONET path performance monitoring
•
•
sonet_ptp_pm: SONET port performance monitoring
sonet_vt_capacity_pm: SONET VT/TU switch capacity monitoring
•
t100_ptp_pm: Legacy equipment. See the Release 2.0 Node
Operations and Maintenance Guide
vt_path_pm: SONET virtual tributary (VT) path performance
monitoring
•
Release OPS4.0.x
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.
Turin Networks
Page 2-3
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Creating or Modifying a Monitoring Template
Table 2-1 Creating or Modifying a PM Template (continued)
Step
Procedure
6
Set thresholds for each performance monitoring 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
For the capacity monitoring parameters, manually set the Capacity
Available % parameter threshold to have the system generate threshold
crossing alerts (TCA) if the amount of VT/TU switching capacity
available is exceeded. A TCA will be generated once per interval.
8
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.
Note: For capacity monitoring, only VT/TU switching information is
captured for reports. STS paths are not included when determining
available capacity.
9
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
10
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
Page 2-4
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Assigning an EOS Port PM Template
Table 2-1 Creating or Modifying a PM Template (continued)
Step
Procedure
11
Click Done in the Performance Templates dialog box.
12
The Creating or Modifying a PM Template procedure is complete.
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.
Table 2-2 Assigning a Port PM Template
Step
Assigning an
EOS Port PM
Template
Procedure
1
In Shelf View, click a card port.
2
Click the Config tab.
3
From the PM Template list, select a port PM (ptp) template.
4
Click Apply.
5
The Assigning a Port PM Template procedure is complete.
The following procedure describes how to assign an EOS port PM template to an EOS
port.
Table 2-3 Assigning an EOS Port PM Template
Step
Release OPS4.0.x
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.
Turin Networks
Page 2-5
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Assigning a Subport PM Template
Assigning a
Subport PM
Template
The following procedure describes how to assign a port PM template to a DS3
Transmux subport.
Table 2-4 Assigning a Subport PM Template
Step
Assigning a
Service PM
Template
Procedure
1
In Shelf View, select a DS3 Transmux card port.
2
Click the Config tab.
3
From the Subport row, PM Template column list, select a port (ptp) PM
template matching the embedded signal subport type (e.g., ds1_ptp).
4
Click Apply.
5
The Assigning a Subport PM Template procedure is complete.
The following procedure describes how to assign a path PM template to a service. The
service PM template is selected during service creation or editing.
Table 2-5 Assigning a Service PM Template
Step
Page 2-6
Procedure
1
From any view, click the Service tab.
2
Creating or editing a service?
• Creating: Click Add to access the Create Service tab.
• Editing: Double-click a service row to access the Edit Service tab.
3
Click Advanced to access the Advanced Parameters dialog box.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Assigning a Service PM Template
Table 2-5 Assigning a Service PM Template (continued)
Step
4
Procedure
The Advanced Parameters dialog box appears.
From the Source PM Template and Destination PM Template or
Service Port PM list, select a PM template.
4
3
Figure 2-4 Service PM Template Parameters
Release OPS4.0.x
5
Click Done and continue creating or editing the service.
6
The Assigning a Service PM Template procedure is complete.
Turin Networks
Page 2-7
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Assigning a TransAccess 100 Mux PM Template
Assigning a
TransAccess
100 Mux PM
Template
The following procedure describes how to assign a PM template to a TransAccess 100
Mux.
Table 2-6 Assigning a TransAccess 100 Mux PM Template
Step
1
Procedure
In Shelf View, select a TransAccess 100 Mux icon.
1
2
3
4
Figure 2-5 TransAccess 100 Mux Config Tab
Viewing PM
Data
2
Click the 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.
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
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.
PM Timing.
Page 2-8
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Viewing Port or Subport PM Data
Viewing Port or
Subport PM
Data
The following procedure describes how to view port or subport PM data.
Table 2-7 Viewing Port or Subport PM Data
Step
1
Procedure
In Shelf View, click the Performance tab and select a port (1a), or a
subport (1b), or a TransAccess 100 Mux.
1a
1b
Figure 2-6 Object Selection for PM
2
Release OPS4.0.x
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.
Turin Networks
Page 2-9
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Viewing Port or Subport PM Data
Table 2-7 Viewing Port or Subport PM Data (continued)
Step
3
Procedure
Click Refresh to re-display updated PM values.
2a
2b
3
4
5
6
Figure 2-7 Port Performance Tab
Page 2-10
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Viewing Service Path PM Data
Viewing
Service Path
PM Data
The following procedure describes how to view service path PM data.
Table 2-8 Viewing Service PM Data
Step
Procedure
1
In Shelf View, click the Service tab.
2
Select a service. Right-click and select Show Tx/Rx Path to display the
Path Display for Service screen.
2
4a
3
4b
5
Figure 2-8 Path Display for Services Screen
Release OPS4.0.x
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.
Turin Networks
Page 2-11
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Viewing Service Path PM Data
Table 2-8 Viewing Service PM Data (continued)
Step
6
Procedure
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.
7
6b
8
9
10
6a
Figure 2-9 Service Performance (PM) Tab
Page 2-12
7
Click Refresh to re-display updated PM values.
8
If you click Reset, the counters reset to zero.
9
Click Print to print the current screen.
10
Click Save to save the PM data to a file.
11
The Viewing Service PM Data procedure is complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Viewing Signal Path Trace Data
Viewing Signal
Path Trace
Data
The following procedure describes how to view transmission and received signal path
trace information.
Table 2-9 Viewing Signal Path Trace Data
Step
Procedure
1
In Shelf View, click the Service tab.
2
Select a service. Right-click and select Show Tx/Rx Path to display the
Path Display for Service screen.
2
4a
3
4b
5
Figure 2-10 Path Display for Service Screen
Release OPS4.0.x
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).
Turin Networks
Page 2-13
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Viewing Signal Path Trace Data
Table 2-9 Viewing Signal Path Trace Data (continued)
Step
Procedure
5
In the Alarm Profile field, one of the following profile values displays:
• useParent: The alarm profile of the containing object (Parent) based
on the following superset and subset definitions:
– Port: Contains line and path alarms and is the superset.
– High-order path: Contains high- and low-order path alarms and is
a subset of port profiles.
– Low-order path: Contains only low-order path alarms and is a
finer subset of high-order path profiles.
– STS path. Contains STS and VT path alarms and is a subset of
port profiles.
– VT path: Contains only VT path alarms and is a finer subset of
STS path profiles.
• default: The default alarm profile matching the CTP object type.
• <user-defined>: Depending on the CTP object type, this value
indicates a user-defined alarm profile of one of the following path
alarm profile types:
– sdh_hp
– sdh_lp
– sonet_sts
– sonet_vt
6
Click Received/Transmitted Path Overhead. The
Received/Transmitted Path Overhead dialog box displays. (The name of
the button and the resulting dialog box corresponds to whether you
selected a Tx or Rx active hop.)
Figure 2-11 Path Overhead Dialog Box
Page 2-14
7
Click Refresh to display updated PM values.
8
Click Done to return to the previous screen.
9
The Viewing Service PM Data procedure is complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Viewing Capacity Monitoring Data
Viewing
Capacity
Monitoring
Data
The following procedure describes how to view VT or TU capacity monitoring data.
The capacity monitoring data shows the numbers of paths used or available at the
instant the information is captured. Unlike the performance monitoring data, the
capacity monitoring data is not accumulated for each period. If the VT card where the
capacity is being monitored is in a 1:n protection group, only the capacity of the
working card will be collected.
Table 2-10 Viewing VT/TU Capacity Monitoring Data
Step
Procedure
1
In Shelf View, click the Performance tab and select a VT or VT-TU
module.
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.
3
Click Refresh to re-display updated capacity monitoring values.
2a
2b
3
4
5
6
Figure 2-12 Viewing VT/TU Capacity Monitoring Data
Release OPS4.0.x
4
If you click Reset, the counters reset to zero.
5
Click Print to print the current screen.
6
Click Save to save the capacity monitoring data to a file.
7
The Viewing VT/TU Capacity Monitoring Data procedure is complete.
Turin Networks
Page 2-15
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Report Generation
Report
Generation
Through the TransNav management system, you have the ability to generate different
reports. You can customize the reports for your own uses, as well as specify generation
dates and generation periods.
Generate the following reports for all nodes in a domain or for a specific node:
• Performance monitoring
• Historical alarm
• Node inventory
• Historical event
• Resource availability
• Domain service
• Service availability
The following figure shows a sample event report.
Figure 2-13 Event Report Sample
Page 2-16
Turin Networks
Release OPS4.0.x
Chapter 1 Managing Performance
Generating a PM Report
Generating a
PM Report
The following procedure describes how to generate a PM report.
Important: Performance monitoring data collection for the Report
function occurs when the corresponding PM template Collect check boxes
are set. See Creating or Modifying a PM Template, page 1-2.
Table 2-11 PM Report Generation
Step
1
Procedure
From the Admin menu, select Reports.
2
3
3,4
5
Figure 2-14 Reports Screen
Release OPS4.0.x
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.
Turin Networks
Page 2-17
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Generating a PM Report
Page 2-18
Turin Networks
Release OPS4.0.x
S ECTION 2PERFORMANCE M ONITORING
Chapter 2
SONET Performance Parameters
Introduction
This chapter provides performance parameter information for:
• DS1 Port PM, page 2-20
• DS3 Port PM, page 2-23
• EC-1 Port PM, page 2-26
• Small Form-Factor Pluggable Optical Port PM, page 2-28
• SONET Port PM, page 2-29
• SONET STS Path Layer PM, page 2-33
• SONET VT Path Layer PM, page 2-35
• SONET Capacity Monitoring, page 2-37
Modules (cards) which do not collect PM information may be reserved for
administrative use; contact your system Administrator.
For further information on performance monitoring and the management system, see
the TransNav Management System GUI Guide.
Release OPS4.0.x
Turin Networks
Page 2-19
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
DS1 Port PM
DS1 Port PM
The Traverse system provides near- and far-end DS1 port PM parameters.
Table 2-12 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
1–1048575
Default:
13340
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
1–65535
Default: 65
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
1–4095
Default: 10
Default: 100
NE LOSS_L
(Loss of Signal
Seconds
Count of one or more 1-second intervals containing
LOS defects.
1–63
1–4095
Default: 10
Default: 100
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
1–1048575
Default:
13296
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
1–65535
Default: 65
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
1–4095
Default: 10
Default: 100
NE AISS_P
(Alarm
Indication
Signal
Seconds)
Count of 1-second intervals containing one or more
AIS defects
1–63
1–4095
Default: 10
Default: 100
Path—Near End
Page 2-20
Turin Networks
Release OPS4.0.x
Chapter 2
SONET Performance Parameters
DS1 Port PM
Table 2-12 DS1 Port PM Parameters—Near End (continued)
Parameter
15-min
Threshold
Definition
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.
NE CSS_P
(Controlled
Slip Seconds
(Planned for future release.)
NE UAS_P
(Unavailable
Seconds)
NE FC_P
(Failure
Counts)
Daily
Threshold
1–63
1–4095
Default: 2
Default: 17
Count of 1-second intervals for which the DS1 path is
unavailable.
1–63
1–4095
Default: 10
Default: 100
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
1–4094
Default: 4
Default: 40
Table 2-13 DS1 Port PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily
Threshold
Line—Far End
FE ES_L (Errored
Seconds)
(Planned for future release.)
Path—Far End
FE CV_P (Code
Violations)
(Planned for future release.)
FE ES_P (Errored
Seconds–Path)
Count of 1-second intervals containing any of
the following:
• CRC-6 errors (ESF)
• CS events (ESF, SF)
• SEF defects (ESF, SF)
• LOS defects (ESF, SF)
• FE errors (SF)
Release OPS4.0.x
Turin Networks
1–900
1–65535
Default: 65
Default: 648
Page 2-21
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
DS1 Port PM
Table 2-13 DS1 Port PM Parameters—Far End (continued)
Parameter
Definition
Daily
Threshold
1–63
1–4095
Default: 10
Default: 100
Count of 1-second intervals for which the
DS1 path is unavailable.
1–63
1–4095
Default: 10
Default: 100
Count of far-end path failure (RAI) events.
1–63
1–4095
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)
FE SEFS_P
(Severely Errored
Framing
Seconds–Path)
(Planned for future release.)
FE CSS_P
(Controlled Slip
Seconds–Path)
(Planned for future release.)
FE UAS_P
(Unavailable
Seconds–Path)
FE FC_P (Failure
Count–Path)
Page 2-22
15-min
Threshold
Default: 10
Turin Networks
Release OPS4.0.x
Chapter 2
DS3 Port PM
SONET Performance Parameters
DS3 Port PM
The Traverse system provides near- and far-end DS3 (clear channel or transmux) port
PM parameters.
Table 2-14 DS3 Port PM Parameters—Near End
Parameter
Definition
15-min
Threshold
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
1–1048575
Default: 382
Default: 3865
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
1–65535
Default: 25
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
1–4095
Default: 4
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
1–1048575
Default: 382
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
1–65535
Default: 25
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
1–4095
Default: 4
Default: 40
UAS-P
(Unavailable
Seconds)
Count of 1-second intervals during which the
DS3 path is unavailable.
1–63
1–4095
Default: 10
Default: 10
Release OPS4.0.x
Turin Networks
Page 2-23
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
DS3 Port PM
Table 2-14 DS3 Port PM Parameters—Near End (continued)
Parameter
FC-P (Failure
Counts)
Definition
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.
15-min
Threshold
Daily
Threshold
1–63
1–4095
Default: 4
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
1–1048575
Default: 382
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
1–65535
Default: 25
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
1–4095
Default: 4
Default: 40
UASC-P
(Unavailable
Seconds–C-bit
parity application)
Count of 1-second intervals during which the
DS3 path is unavailable.
1–63
1–4095
Default: 10
Default: 10
Page 2-24
Turin Networks
Release OPS4.0.x
Chapter 2
SONET Performance Parameters
DS3 Port PM
Table 2-15 DS3 Port PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily
Threshold
Path CBit—Far End
FE CVC-P (Code
Violations)
Counted when the three FEBE bits in an
M-frame are not all set to 1.
1–16383
1–1048575
Default: 382
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
1–65535
Default: 25
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
1–4095
Default: 4
Default: 40
FE UASC-P
(Unavailable
Seconds
Count of 1-second intervals during which the
DS3 path is unavailable.
1–63
1–4095
Default: 10
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
1–4095
Default: 4
Default: 40
Release OPS4.0.x
Turin Networks
Page 2-25
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
EC-1 Port PM
EC-1 Port PM
The Traverse system provides near- and far-end EC-1 port PM parameters.
Table 2-16 EC1 Port PM Parameters—Near-End
Parameter
Definition
15-min
Threshold
Daily
Threshold
LINE
CV (Coding
Violations
–Line)
Count of BIP errors detected at the line layer (i.e.,
using the B2 bytes in the incoming SONET signal).
Up to 8xN BIP errors can be detected per STS-N
frame, with each error incrementing the CV-L
current second register.
1–16383
1–1048575
Default: 387
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
1–65535
Default: 25
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
1–4095
Default: 4
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
1–4095
Default: 4
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
1–4095
Default: 4
Default: 40
Count of BIP-8 errors that are detected at the
section layer of the incoming signal.
1–16383
1–1048575
Default: 382
Default: 3820
SECTION
CV (Code
Violations–
Section)
Page 2-26
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.
Turin Networks
Release OPS4.0.x
Chapter 2
SONET Performance Parameters
EC-1 Port PM
Table 2-16 EC1 Port PM Parameters—Near-End (continued)
Parameter
15-min
Threshold
Definition
Daily
Threshold
ES (Errored
Seconds– Section)
Count of 1-second intervals during which (at any
point during the second) at least one section layer
BIP error was detected or an SEF or LOS defect
was present
1–900
1–65535
Default: 25
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
1–65535
Default: 4
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
1–65535
Default: 2
Default: 8
Table 2-17 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
1–1048575
Default: 387
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
1–65535
Default:
25
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
1–4095
Default: 4
Default: 40
Release OPS4.0.x
Turin Networks
Page 2-27
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Small Form-Factor Pluggable Optical Port PM
Table 2-17 EC1 Port PM Parameters—Far-End (continued)
Parameter
15-min
Threshold
Definition
Daily Threshold
UASFE
(Unavailable
Seconds–
Line, Far-End)
Count of the seconds during which the Line is
considered unavailable at the far end. A Line
is considered unavailable at the far end at the
onset of 10 consecutive seconds that qualify
as SES-LFEs, and continues to be considered
unavailable until the onset of 10 consecutive
seconds that do not qualify as SES-LFEs.
1–63
1–4095
Default: 4
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
1–4095
Default: 4
Default: 40
Small
Form-Factor
Pluggable
Optical Port
PM
The Traverse system provides the following performance (diagnostic) monitoring
parameters for the small form-factor pluggable (SFP) and 10 Gigabit small form-factor
pluggable (XFP) optical ports.
Table 2-18 SFP (and XFP) 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.
Page 2-28
Turin Networks
Release OPS4.0.x
Chapter 2
SONET Port
PM
SONET Performance Parameters
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-19 SONET Port PM—Near End
Parameter
Definition
15-min
Threshold
Daily Threshold
Section—Near End
CV-S (Coding
Violation)
Count of BIP (Bit Interleaved Parity)
errors detected at the Section layer (i.e.,
using the B1 byte in the incoming SONET
signal). Up to 8 section BIP errors can be
detected per STS-N frame, with each error
incrementing the CV-S register.
1–16383
1–1048575
Default: 382
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
1–65535
Default: 25
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
1–65535
Default: 4
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
1–65535
Default: 2
Default: 8
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
1–1048575
Default: 1146
Default: 11460
Line—Near end
CV-L (Coding
Violation)
Release OPS4.0.x
Turin Networks
Page 2-29
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SONET Port PM
Table 2-19 SONET Port PM—Near End (continued)
Parameter
Definition
15-min
Threshold
Daily Threshold
ES-L (Errored
Seconds)
Count of the seconds during which (at any
point during the second) at least one Line
layer BIP error was detected or an LOS
defect (or a lower-layer, traffic-related,
near-end defect) was present.
1–900
1–65535
Default: 25
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
1–65535
Default: 4
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
1–65535
Default: 4
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
1–4094
Default: 4
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
1–255
Default: 2
Default: 10
Page 2-30
Turin Networks
Release OPS4.0.x
Chapter 2
SONET Performance Parameters
SONET Port PM
Table 2-19 SONET Port PM—Near End (continued)
Parameter
15-min
Threshold
Definition
Daily Threshold
PSDW-L
(Protection
Switch Duration
Working)
Count of the seconds that the working line
was being used to carry an OC-N line
service (i.e., BLSR, 1+1 ASP).
1–900
1–65535
Default: 4
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
1–255
Default: 2
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
1–65535
Default: 4
Default: 40
Table 2-20 SONET Port PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily
Threshold
Line—Far End
FE CV-L (Coding
Violations)
Count of the number of BIP errors detected
by the far-end LTE and reported back to the
near-end LTE using the REI-L indication in
the Line overhead. For SONET signals at
rates below OC48, up to 8xN BIP errors per
STS-N frame can be indicated using the
REI-L. For OC48 signals, up to 255 BIP
errors per STS-N frame can be indicated.
The CV-LFE current second register
increments for each BIP error indicated by
the incoming REI-L.
1–16383
1–1048575
Default: 1146
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
1–65535
Default: 25
Default: 250
Release OPS4.0.x
Turin Networks
Page 2-31
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SONET Port PM
Table 2-20 SONET Port PM Parameters—Far End (continued)
15-min
Threshold
Daily
Threshold
Parameter
Definition
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
1–65535
Default: 4
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
1–65535
Default: 4
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
1–4094
Default: 4
Default: 40
Page 2-32
Turin Networks
Release OPS4.0.x
Chapter 2
SONET STS
Path Layer PM
SONET Performance Parameters
SONET STS Path Layer PM
The Traverse system provides the following performance monitoring parameters for
SONET STS path layer services.
Table 2-21 SONET STS Path PM Parameters—Near End
Parameter
Definition
15-min
Threshold
Daily Threshold
CV-P (Coding
Violations)
Count of BIP errors detected at the STS Path
layer (i.e., using the B3 byte in the incoming
STS path overhead). Up to 8 BIP errors can
be detected per frame, with each error
incrementing the CV-P current second
register.
1–16383
1–1048575
Default: 1146
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
1–65535
Default: 25
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
1–65535
Default: 4
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
1–65535
Default: 4
Default: 40
Release OPS4.0.x
Turin Networks
Page 2-33
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SONET STS Path Layer PM
Table 2-22 SONET STS Path PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily Threshold
FE CV-P
(Coding
Violations)
Count of the number of BIP errors detected
by the far-end STS PTE and reported back to
the near-end STS PTE using the REI-P
indication in the STS Path overhead. Up to 8
BIP errors per frame can be indicated. The
CV-PFE current second register increments
for each BIP error indicated by the incoming
REI-P.
1–16383
1–1048575
Default: 1146
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
1–65535
Default: 25
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
1–65535
Default: 4
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
1–65535
Default: 4
Default: 40
Page 2-34
Turin Networks
Release OPS4.0.x
Chapter 2
SONET VT
Path Layer PM
SONET Performance Parameters
SONET VT Path Layer PM
The Traverse system provides the following performance monitoring parameters for
SONET VT path layer services.
Table 2-23 SONET VT Path PM Parameters—Near End
15-min
Threshold
Daily
Threshold
Parameter
Definition
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
1–1048575
Default: 156
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
1–65535
Default: 65
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
1–65535
Default: 10
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
1–65535
Default: 10
Default: 100
Release OPS4.0.x
Turin Networks
Page 2-35
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SONET VT Path Layer PM
Table 2-24 SONET VT Path PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily
Threshold
FE CV-V
(Coding
Violations)
Count of the number of BIP errors detected by the
far-end VT PTE and reported back to the near-end
VT PTE using the REI–V indication in the VT
Path overhead. Note that only 1 BIP error can be
indicated per VT superframe using the REI–V bit
(out of the two BIP errors that can be detected).
The CV–VFE current second register increments
for each BIP error indicated by the incoming
REI–V.
1–16383
1–1048575
Default: 156
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
1–65535
Default: 65
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
1–65535
Default: 10
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
1–65535
Default: 10
Default: 100
Page 2-36
Turin Networks
Release OPS4.0.x
Chapter 2
SONET
Capacity
Monitoring
SONET Performance Parameters
SONET Capacity Monitoring
The Traverse system provides the following SONET capacity monitoring parameters.
Important: Capacity monitoring values in the sonet_vt_capacity_pm
template indicate the available capacity of STS and VT1.5 paths on the
VT/TU module (card). The information is a snapshot of the instant the
information is captured.
Table 2-25 SONET Capacity Monitoring
Parameter
Definition
15-min
Threshold
Daily Threshold
STS Used
The number of STS paths that are
currently used on the VT/TU card.
0–96
0–96
STS Available
The number of additional STS paths that
could be created on the VT/TU card.
0–96
0–96
VT Used
The number of VT1.5 paths that are
currently used on the VT/TU card.
0–2688
0–2688
VT Available
The number of additional VT1.5 paths that
could be created on the VT/TU card.
0–2688
0–2688
Capacity
Available
The percentage of VT/TU switching
capacity available on the VT/TU card.
This number grows and declines as
VT/TU services are activated and
deactivated respectively. The capacity is
calculated using the lowest path
granularity (VT1.5). The STS paths are
not included when determining available
capacity. The Traverse system generates a
TCA when this threshold is crossed.
0–100
0–100
Default: 0
Default: 0
Release OPS4.0.x
Turin Networks
Page 2-37
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SONET Capacity Monitoring
Page 2-38
Turin Networks
Release OPS4.0.x
S ECTION 2PERFORMANCE M ONITORING
Chapter 3
SDH Performance Parameters
Introduction
This chapter provides performance parameter information for:
• E1 Port PM, page 2-40
• E3 Port PM, page 2-43
• SDH High and Low Order Path PM, page 2-46
• SDH Port PM, page 2-50
• SDH VC-11 and VC-12 Path PM, page 2-55
• SDH Capacity Monitoring, page 2-59
Modules (cards) which do not collect PM information may be reserved for
administrative use; contact your system Administrator.
For further information on performance monitoring and the management system, see
the TransNav Management System GUI Guide.
Release OPS4.0.x
Turin Networks
Page 2-39
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
E1 Port PM
E1 Port PM
The Traverse system provides the following near- and far-end E1 port performance
monitoring parameters.
Table 2-26 E1 Port PM Parameters—Near End
Parameter
Definition
15-min
Threshold
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
1–4094
Default: 4
Default: 40
NE CV_L
(Code
Violations)
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
1–1048575
Default:
13340
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
1–65535
Default: 65
Default: 648
NE SES_L
(Severely
Errored
Seconds)
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
1–4095
Default: 10
Default: 100
NE LOSS_L
(Loss of Signal
Seconds
Count of one or more 1-second intervals containing
LOS defects.
1–63
1–4095
Default: 10
Default: 100
NE FAS_L
(Frame
Alignment
Signal)
Count of one or more 1-second intervals containing
FAS defects.
1–63
Default: 2
1–4095
Default: 17
Count of the number of blocks containing one or more
bit errors.
1–8 x 106
1–8 x 108
Default: 1329
Default: 13,296
Path—Near End
NE EB_P
(Errored
Blocks)
Page 2-40
Turin Networks
Release OPS4.0.x
Chapter 3
SDH Performance Parameters
E1 Port PM
Table 2-26 E1 Port PM Parameters—Near End (continued)
Parameter
Definition
15-min
Threshold
Daily
Threshold
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
1–65535
Default: 65
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
1–4095
Default: 10
Default: 100
NE AISS_P
(Alarm
Indication
Signal
Seconds)
Count of 1-second intervals containing one or more
AIS defects
1–63
1–4095
Default: 10
Default: 100
NE UAS_P
(Unavailable
Seconds)
Count of 1-second intervals for which the DS1 path is
unavailable.
1–63
1–4095
Default: 10
Default: 100
NE BBE_P
(Background
Block Error)
An errored block not occurring as part of an SES.
1–8 x 106
1–8 x 108
Default: 1329
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
1–65535
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.
1–65535
1–65535
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.
1–65535
1–65535
Default: 4
Default: 10
Release OPS4.0.x
Turin Networks
Page 2-41
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
E1 Port PM
Table 2-27 E1 Port PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily
Threshold
Line—Far End
FE 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
1–65535
Default: 65
Default: 648
FE 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
1–65535
Default: 65
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
1–4095
Default: 10
Default: 100
FE UAS_P
(Unavailable
Seconds)
Count of 1-second intervals for which the
DS1 path is unavailable.
1–63
1–4095
Default: 10
Default: 100
FE EB_P (Errored
Blocks)
Count of the number of blocks containing one
or more bit errors.
1–8 x 106
1–8 x 108
Default: 1329
Default:
13,296
FE FC_P (Failure
Count)
Count of far-end path failure (RAI) events.
1–63
1–4095
FE BBE_P
(Background
Block Error)
An errored block not occurring as part of an
SES.
Path—Far End
Page 2-42
Default: 10
Turin Networks
1–8 x 106
1–8 x 108
Default: 1329
Default:
13,296
Release OPS4.0.x
Chapter 3
E3 Port PM
SDH Performance Parameters
E3 Port PM
The Traverse system provides the following near- and far-end E3 port performance
monitoring parameters.
Table 2-28 E3 Port PM Parameters–Near End
Parameter
Definition
15-min
Threshold
Daily Threshold
Line—Near End
NE CV_L (Code
Violations)
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.
NE ES_L (Errored
Seconds)
Default: 13340
Default: 133400
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.
Default: 65
Default: 648
NE 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.
Default: 10
Default: 100
NE LOSS_L
(Loss of Signal
Seconds
Count of one or more 1-second intervals
containing LOS defects.
1–63
1–4095
Default: 10
Default: 100
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
1–1048575
Default: 382
Default: 3820
NE EB_P (Errored
Blocks)
Count of the number of blocks containing one
or more bit errors.
Default:13296
Default: 132960
Default:13296
Default: 132960
1–900
1–65535
Default: 25
Default: 250
Path
(Planned for future release.)
NE BBE_P
(Background
Block Error)
An errored block not occurring as part of an
SES.
NE 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.
Release OPS4.0.x
(Planned for future release.)
Turin Networks
Page 2-43
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
E3 Port PM
Table 2-28 E3 Port PM Parameters–Near End (continued)
Parameter
Definition
15-min
Threshold
Daily Threshold
NE 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
1–4095
Default: 4
Default: 40
NE UAS_P
(Unavailable
Seconds)
Count of 1-second intervals during which the
DS3 path is unavailable.
1–63
1–4095
Default: 10
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.
Default: 4
Default: 10
1–63
1–4095
Default: 4
Default: 40
(Planned for future release.)
(Planned for future release.)
(Planned for future release.)
NE FC_P (Failure
Counts)
Page 2-44
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.
Turin Networks
Release OPS4.0.x
Chapter 3
SDH Performance Parameters
E3 Port PM
Table 2-29 E3 Port PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily Threshold
Path—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.
FE EB_P (Errored
Blocks)
Count of the number of blocks containing one
or more bit errors.
1–16383
1–1048575
Default: 1146
Default: 11460
Default:13296
Default: 132960
(Planned for future release.)
FE 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
1–65535
Default: 25
Default: 250
FE 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
1–4095
Default: 4
Default: 40
FE UAS_P
(Unavailable
Seconds
Count of 1-second intervals during which the
DS3 path is unavailable.
1–63
1–4095
Default: 10
Default: 10
FE FC_P (Failure
Counts)
Count of the number of far-end path failure
events. A failure event begins when the RFI-P
failure is declared, and ends when the RFI-P
failure is cleared. A failure event that begins
in one period and ends in another period is
counted only in the period in which it begins.
Default: 4
Default: 40
Release OPS4.0.x
Turin Networks
Page 2-45
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH 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.
Table 2-30 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
The following table lists the supported performance monitoring parameters for SDH
paths.
Table 2-31 SDH High Order VC Path and
Low Order VC3 PM Parameters—Near End
Parameter
EB-HP
EB-LP
(Errored Block)
Definition
A block is a set of consecutive bits associated
with the path. An errored block contains one
or more bits with an error.
15-min
Threshold
Daily Threshold
1–7,200,000
1–691,200,000
Default: 20,000
Default: 200,000
1–900
1–86,400
Default: 25
Default: 250
See Table 2-30 Number of Errored Blocks
that Constitute an SES, page 2-46 to
determine how many bits are in one block for
each container type (VC-N).
ES-HP
ES-LP
Count of 1-second period with at least one
errored block or one defect.
(Errored Seconds)
Page 2-46
Turin Networks
Release OPS4.0.x
Chapter 3 SDH Performance Parameters
SDH High and Low Order Path PM
Table 2-31 SDH High Order VC Path and
Low Order VC3 PM Parameters—Near End (continued)
Parameter
SES-HP
SES-LP
Definition
Daily Threshold
1–900
1–86,400
Default: 4
Default: 40
1–900
1–86,400
Default: 4
Default: 40
(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.
BBE-HP
BBE-LP
Count of errored blocks not occurring as part
of Severely Errored Seconds.
1–7,200,000
1–691,200,000
Default: 20,000
Default: 200,000
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–900
1–225
Default: 2
Default: 10
Count of the positive pointer justifications
detected on the path.
1–1,048,575
1–16,777,215
Default: 60
Default: 6000
(Severely Errored
Seconds)
Count of a 1-second period which contains
30% or more errored blocks or at least one
defect. See Table 2-30 Number of Errored
Blocks that Constitute an SES, page 2-46 to
determine how many errored blocks
constitute an SES on the path.
15-min
Threshold
When a near-end SES occurs as a result of a
near-end defect, the far-end performance is
not evaluated during that second.
However, if a near-end SES occurs as a result
of 30% or more EBs, performance
monitoring at the far end continues.
UAS-HP
UAS-LP
(Background
Block Error)
FC-HP
FC-LP
(Failure Counts)
PPJC-DET-HP
PPJC-DET-LP
(Positive Pointer
Justifications
Detected)
Release OPS4.0.x
Turin Networks
Page 2-47
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH High and Low Order Path PM
Table 2-31 SDH High Order VC Path and
Low Order VC3 PM Parameters—Near End (continued)
Parameter
NPJC-DET-HP
NPJC-DET-LP
Definition
15-min
Threshold
Daily Threshold
Count of the negative pointer justifications
detected on the path.
1–1,048,575
1–16,777,215
Default: 60
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
1–16,777,215
Default: 60
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
1–16,777,215
Default: 60
Default: 6000
15-min
Threshold
Daily Threshold
(Negative Pointer
Justifications
Detected)
Table 2-32 SDH High Order VC Path and
Low Order VC3 PM Parameters—Far End
Parameter
FE EB-HP
FE EB-LP
(Errored Blocks)
FE ES-HP
FE ES-LP
(Errored
Seconds)
FE SES-HP
FE SES-LP
(Severely Errored
Seconds)
Page 2-48
Definition
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
1–691200000
Default:
20,000
Default: 30,000
Count of the seconds during which (at any
point during the second) at least one defect is
detected at the far end.
1–900
1–65535
Default: 20
Default: 200
Count of seconds which contains 30% or
more errored blocks or at least one defect at
the far end.
1–900
1–65535
Default: 3
Default: 10
Turin Networks
Release OPS4.0.x
Chapter 3 SDH Performance Parameters
SDH High and Low Order Path PM
Table 2-32 SDH High Order VC Path and
Low Order VC3 PM Parameters—Far End (continued)
Parameter
FE UAS-HP
FE UAS-LP
(Unavailable
Seconds)
FE BBE-HP
FE BBE-LP
(Background
Block Error)
FE FC-HP
FE FC-LP
(Failure Counts)
Release OPS4.0.x
Definition
15-min
Threshold
Daily Threshold
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
1–65535
Default: 3
Default: 10
Count of errored blocks at the far end not
occurring as part of Severely Errored
Seconds.
1–7200000
1–691200000
Default:
36,000
Default: 48,000
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
1–225
Default: 2
Default: 10
Turin Networks
Page 2-49
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH Port PM
SDH Port PM
The Traverse system provides the following near- and far-end SDH port performance
monitoring parameters.
Important: Default threshold values in the sdh_ptp_pm template are
based on performance monitoring for STM-1 rates. Turin recommends
customizing this template for rates other than STM-1.
Table 2-33 SDH Port PM—Near End
Parameter
Definition
15-min Threshold
Daily Threshold
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
1–691200000
Default: 10,000
Default: 100,000
Recommended defaults for rates other than
STM-1:
STM-0: 9,600
STM-4: 115,200
STM-16: 460,800
STM-64:1,843,200
STM-0: 96,000
STM-4: 288,000
STM-16: 1,152,000
STM-64: 18,432,000
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
1–65535
Default: 25
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
1–86,400
Default: 4
Default: 40
BBE-RS
(Background
Block Error)
Count of error block not occurring as part
of Severely Errored Seconds.
1–7200000
1–691200000
Default: 10,000
Default: 100,000
Recommended defaults for rates other than
STM-1:
STM-0: 9,600
STM-4: 115,200
STM-16: 460,800
STM-64:1,843,200
Page 2-50
Turin Networks
STM-0: 96,000
STM-4: 288,000
STM-16: 1,152,000
STM-64: 18,432,000
Release OPS4.0.x
Chapter 3
SDH Performance Parameters
SDH Port PM
Table 2-33 SDH Port PM—Near End (continued)
Parameter
Definition
15-min Threshold
Daily Threshold
Multiplex Section—Near End
1–1.10592 x 1010
1–1.03168 x 1012
Defaults: 28,800
Default: 288,000
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
1–86,400
Default: 25
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
1–86,400
Default: 4
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
1–65535
Default: 4
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
1–1.03168 x 1012
Defaults: 28,800
Default: 288,000
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.
ES-MS (Errored
Seconds)
Release OPS4.0.x
Turin Networks
Page 2-51
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH Port PM
Table 2-33 SDH Port PM—Near End (continued)
Parameter
Definition
15-min Threshold
Daily Threshold
FC-MS (Failure
Counts)
Count of the number of near-end multiplex
section failure events. A failure event
begins when the LOS failure (or a
lower-layer, traffic-related, near-end
failure) is declared, and ends when the
failure is cleared. A failure event that
begins in one period and ends in another
period is counted only in the period in
which it begins.
1–72
1–4094
Default: 4
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
1–255
Default: 2
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
1–86,400
Default: 300
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
1–255
Default: 2
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
1–86,400
Default: 300
Default: 600
Page 2-52
Turin Networks
Release OPS4.0.x
Chapter 3
SDH Performance Parameters
SDH Port PM
Table 2-34 SDH Port PM—Far End
Parameter
Definition
15-min Threshold
Daily Threshold
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
1–1.03168 x 1012
Defaults: 28,800
Default: 288,000
Recommended defaults for rates other than
STM-1:
STM-0: 9,600
STM-4: 115,200
STM-16: 460,800
STM-64:1,843,200
STM-0: 96,000
STM-4: 288,000
STM-16: 1,152,000
STM-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
1–86,400
Default: 25
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
1–86,400
Default: 4
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
1–65535
Default: 4
Default: 40
Release OPS4.0.x
Turin Networks
Page 2-53
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH Port PM
Table 2-34 SDH Port PM—Far End (continued)
Parameter
FE BBE-MS
(Error Blocks)
FE FC-MS
(Failure Counts)
Page 2-54
Definition
Count of BIP errors detected at the
multiplex section layer (i.e., using the B2
byte in the incoming SDH signal). Up to 8
section BIP errors can be detected per
STM-N frame, with each error
incrementing the EB-MS register.
Count of the number of far end multiplex
section failure events. A failure event
begins when the LOS failure (or a
lower-layer, traffic-related, near-end
failure) is declared, and ends when the
failure is cleared. A failure event that
begins in one period and ends in another
period is counted only in the period in
which it begins.
Turin Networks
15-min Threshold
Daily Threshold
1–1.10592 x 1010
1–1.03168 x 1012
Defaults: 28,800
Default: 288,000
Recommended defaults for rates other than
STM-1:
STM-0: 9,600
STM-4: 115,200
STM-16: 460,800
STM-64:1,843,200
STM-0: 96,000
STM-4: 288,000
STM-16: 1,152,000
STM-64: 18,432,000
1–72
1–4094
Default: 4
Default: 40
Release OPS4.0.x
Chapter 3 SDH Performance Parameters
SDH VC-11 and VC-12 Path PM
SDH VC-11 and
VC-12 Path PM
The Traverse system provides the following SDH VC-11 and VC-12 path performance
monitoring parameters.
The following table lists the block size and the threshold for errored blocks for each
low order path layer.
Table 2-35 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
The following table lists the supported performance monitoring parameters for SDH
paths.
Table 2-36 SDH VC-11 and VC-12 Path PM Parameters—Near End
Parameter
Definition
BBE-LP
(Background
Block Error)
Count of errored blocks not occurring as part
of Severely Errored Seconds.
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.
15-min
Threshold
Daily Threshold
1–1.8 x 106
1–1.8x108
Default: 5,000
Default: 50,000
1–1.8 x 106
1–1.8x108
Default: 5,000
Default: 50,000
See Table 2-35 Number of Errored Blocks
that Constitute an SES, page 2-55 to
determine how many bits are in one block for
each container type (VC-N).
ES-LP (Errored
Seconds)
Count of 1-second period with at least one
errored block or one defect.
1–900
1–65,535
Default: 25
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-35 Number of Errored
Blocks that Constitute an SES, page 2-55 to
determine how many errored blocks
constitute an SES on the path.
1–900
1–65,535
Default: 4
Default: 40
When a near-end SES occurs as a result of a
near-end defect, the far-end performance is
not evaluated during that second.
However, if a near-end SES occurs as a result
of 30% or more EBs, performance
monitoring at the far end continues.
Release OPS4.0.x
Turin Networks
Page 2-55
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH VC-11 and VC-12 Path PM
Table 2-36 SDH VC-11 and VC-12 Path PM Parameters—Near End (continued)
Parameter
Definition
15-min
Threshold
Daily Threshold
UAS-LP
(Unavailable
Seconds)
Count of the seconds during which the path
was considered unavailable. A path becomes
unavailable at the onset of 10 consecutive
seconds that qualify as SES-Ps, and continues
to be unavailable until the onset of 10
consecutive seconds that do not qualify as
SES-Ps.
1–900
1–65,535
Default: 4
Default: 40
FC-LP (Failure
Counts)
Count of the number of near-end failure
events on the line. A failure event begins
when the LOS failure (or a lower-layer,
traffic-related, near-end failure) is declared,
and ends when the failure is cleared. A failure
event that begins in one period and ends in
another period is counted only in the period
in which it begins.
1–72
1–4,095
Default: 2
Default: 10
PPJC-DET-LP
Count of the positive pointer justifications
detected on the path.
1–32,767
1–2,097,151
Default: 30
Default: 300
NPJC-DET-LP
(Negative Pointer
Justifications
Detected)
Count of the negative pointer justifications
detected on the path.
1–32,767
1–2,097,151
Default: 30
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
1–2,097,151
Default: 30
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
1–2,097,151
Default: 30
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
1–65,535
Default: 9
Default: 90
(Positive Pointer
Justifications
Detected)
Page 2-56
Turin Networks
Release OPS4.0.x
Chapter 3 SDH Performance Parameters
SDH VC-11 and VC-12 Path PM
Table 2-36 SDH VC-11 and VC-12 Path PM Parameters—Near End (continued)
Parameter
Definition
15-min
Threshold
Daily Threshold
PJCS-GEN-LP
(Pointer
Justifications
Seconds
Generated)
Count of seconds containing one or more
PPJC-GEN or NPJC-GEN.
1–900
1–65,535
Default: 9
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
1–2,097,151
Default: 10
Default: 100
Table 2-37 SDH VC-11 and VC-12 Path PM Parameters—Far End
Parameter
Definition
15-min
Threshold
Daily Threshold
1–1.8 x 106
1–1.8x108
Default: 5,000
Default: 50,000
1–1.8 x 106
1–1.8x108
Default: 5,000
Default: 50,000
1–900
1–65,535
(Errored
Seconds)
Count of the seconds during which (at any
point during the second) at least one defect is
detected at the far end.
Default: 25
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
1–65,535
Default: 4
Default: 40
FE BBE-LP
(Background
Block Error)
FE EB-LP
(Errored Blocks)
FE ES-LP
Release OPS4.0.x
Count of errored blocks at the far end not
occurring as part of Severely Errored
Seconds.
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.
Turin Networks
Page 2-57
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH VC-11 and VC-12 Path PM
Table 2-37 SDH VC-11 and VC-12 Path PM Parameters—Far End (continued)
Parameter
Definition
15-min
Threshold
Daily Threshold
FE UAS-LP
(Unavailable
Seconds)
Count of the seconds during which the path is
considered unavailable at the far end. A path
is considered unavailable at the far end at the
onset of 10 consecutive seconds that qualify
as SES-PFEs, and continues to be considered
unavailable until the onset of 10 consecutive
seconds that do not qualify as SES-PFEs.
1–900
1–65,535
Default: 4
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
1–4,095
Default: 2
Default: 10
Page 2-58
Turin Networks
Release OPS4.0.x
Chapter 3
SDH Capacity
Monitoring
SDH Performance Parameters
SDH Capacity Monitoring
The Traverse system provides the following SDH capacity monitoring parameters.
Important: Capacity monitoring values in the sdh_vt_capacity_pm
template indicate the available capacity on the VT/TU module (card). The
information is a snapshot of the instant the information is captured.
Table 2-38 SDH Capacity Monitoring
Parameter
Definition
15-min
Threshold
Daily Threshold
VC-4 Used
The number of VC-4 paths currently used
on the VT/TU card.
0–32
0–32
VC-4 Available
The number of additional VC-4 paths that
could be created on the VT/TU card.
0–32
0–32
VC-3 Used
The number of VC-3 paths currently used
on the VT/TU card.
0–96
0–96
VC-3 Available
The number of additional VC-3 paths that
could be created on the VT/TU card.
0–96
0–96
TU-3 Used
The number of TU-3 containers currently
used on the VT/TU card. This reflects only
the TR-3 containers within VC-4
grooming endpoints currently existing on
the VT/TU card.
0–96
0–96
TU-3 Available
The number of additional TU-3 containers
that could be created on the VT/TU card.
This reflects the sum of:
0–96
0–96
• the TU-3 containers available within empty or
partially filled VC-4 grooming endpoints
currently existing on the VT/TU card and
• the TU-3 containers that would be available if all
available VC-4 paths were to be used only for
TU-3 services.
VC-12 Used
The number of VC-12 paths currently
used on the VT/TU card.
0–2016
0-2016
VC-12 Available
The number of additional VC-12 paths
that could be created on the VT/TU card.
This reflects the sum of:
0–2016
0-2016
• the VC-12 paths available within empty or
partially filled VC-4 / VC-3 grooming endpoints
currently existing on the VT/TU card and
• the VC-12 paths that would be available if all
available VC-4 or VC-3 paths were to be used
only for VC-12 services.
Release OPS4.0.x
Turin Networks
Page 2-59
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
SDH Capacity Monitoring
Table 2-38 SDH Capacity Monitoring (continued)
Parameter
Definition
15-min
Threshold
Daily Threshold
VC-11 Used
The number of VC-11 paths currently used
on the VT/TU card.
0–2688
0–2688
VC-11 Available
The number of additional VC-11 paths
that could be created on the VT/TU card.
This reflects the sum of:
0–2688
0–2688
0–100
0–100
Default: 0
Default: 0
• the VC-11 paths available within empty or
partially filled VC-4 / VC-3 grooming endpoints
currently existing on the VT/TU card and
• the VC-11 paths that would be available if all
available VC-4 or VC-3 paths were to be used
only for VC-11 services.
Capacity
Available
Page 2-60
The percentage of VT/TU switching
capacity available on the VT/TU card.
This number grows and declines as
VT/TU services are activated and
deactivated. The capacity is calculated
using the lowest path granularity (VC-11).
No other paths are included when
determining available capacity. The
Traverse system generates a TCA when
this threshold is crossed.
Turin Networks
Release OPS4.0.x
S ECTION 2PERFORMANCE M ONITORING
Chapter 4
Ethernet Performance Parameters
Introduction
This chapter provides performance parameter information for:
• EOS Port PM, page 2-61
• Ethernet 10GbE Equipment PM, page 2-63
• Ethernet Equipment PM, page 2-64
• Ethernet Port PM, page 2-67
• Ethernet Service Port PM, page 2-70
• Small Form-Factor Pluggable Optical Port PM, page 2-71
Modules (cards) which do not collect PM information may be reserved for
administrative use; contact your system Administrator.
For further information on performance monitoring and the management system, see
the TransNav Management System GUI Guide.
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), 10GbE, GbE-10, and TE-100
Ethernet.
Note: The EOS Port PM byte counts include the 8-byte GFP header, allowing users to
view the precise loads being handled by the EOS port.
EOS Port PM and EOS Service PM byte counts may differ for the following reasons:
• If multiple services are using the same EOS port, the EOS Port PM is the
cumulative total across all such services.
• EOS Service PM byte counts do not include the 8-byte GBP header.
• VLAN tags may be added or stripped as packets traverse the Ethernet card. This
results in different packet sizes when counted at the service interface than when
counted at the EOS port interface.
Release OPS4.0.x
Turin Networks
Page 2-61
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
EOS Port PM
In Shelf View, click the Ethernet tab, click the EOS subtab, click an EOS port from the
EOS port list, then click the Performance tab.
Table 2-39 EOS Port PM Parameters
Parameter
Definition
(Exclusive Parameter Note)
TX UNICAST
The number of unicast frames transmitted with no errors.
(TE-100 Ethernet only)
(TE-100 Ethernet only)
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 MULTICAST
(TE-100 Ethernet only)
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
The number of outbound frames received by this port which
were discarded.
(Traverse NGE only)
RX UNICAST
(TE-100 Ethernet only)
RX MULTICAST
(TE-100 Ethernet only)
RX BROADCAST
(TE-100 Ethernet only)
The number of unicast frames received, with length between 64
bytes and the maximum size, with no errors.
The number of multicast frames received, with length between
64 bytes and the maximum size, with no errors.
The number of broadcast frames received, with length between
64 bytes and the maximum size, with no errors.
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
The number of inbound frames discarded by this port due to
errors, and thus, unable to forward to a higher-layer protocol.
(Traverse NGE only)
RX FCS ERR
(Traverse 10GbE or GbE-10 only)
RX MAC CTL DISCARDS
(Traverse 10GbE or GbE-10 only)
GFP FCS DISCARDS4
(Traverse NGE only)
The number of received frames that were discarded due to
incorrect Ethernet CRC.
The number of received “MAC control” frames that were
discarded due to invalid addresses.
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
The number of GFP frames discarded due to due to
uncorrectable “payload header” (extension or type header)
checksum (eHEC, tHEC) errors.
(Traverse NGE only)
Page 2-62
Turin Networks
Release OPS4.0.x
Chapter 4
Ethernet Performance Parameters
Ethernet 10GbE Equipment PM
Table 2-39 EOS Port PM Parameters (continued)
Parameter
Definition
(Exclusive Parameter Note)
GFP FCS OR PHEC DISCARDS
(TE-100 Ethernet only)
RX MTU DISCARDS
(TE-100 Ethernet only)
GFP HEC CORRECTIONS
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.
The number of frames discarded by this interface due to an
excessive size.
GFP frames received with single-bit HEC errors (cHEC, eHEC
or tHEC) that have been corrected.
1
Not supported by Traverse Legacy Ethernet. Traverse NGE and TE-100 Ethernet exclude CMF frames.
2
Traverse NGE has a complete GFP Frame, excluding CMF frames.
3
TE-100 Ethernet has Ethernet Frame only.
4
Traverse NGE payload FCS, includes CMF frames.
Ethernet
10GbE
Equipment PM
The system provides the following performance monitoring and counters for 10GbE or
GbE-10 equipment events that occur during normal operation. For example, discarded
frames or excessive traffic on a service.
Table 2-40 Ethernet 10GbE Equipment PM Parameters
Parameter
Definition
(Exclusive Parameter Note)
Counter
type
G3CpDiscards
Frames discarded inside the analysis block. Includes
frames discarded because they could not be assigned
to any activated service, as well as possible internal
errors.
Frame
G3Spi4Rx Overrun
SPI-4 RX overruns. This counter could increment
under heavy load of 64-byte frames. Each event may
correspond to one or more discarded frames.
Event
G3SwcBuf RAMOverrun
Frames discarded because no buffer was available to
hold it (all available buffers are in use by queued
frames). Can occur if RED thresholds are set
excessively high for very congested egress ports
Frame
G3SwcPck HdrOverrun
Frames discarded due to lack of packet header
resources. This counter could increment if the offered
load exceeds the card’s limit of 25 million frames per
second.
Frame
Release OPS4.0.x
Turin Networks
Page 2-63
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Ethernet Equipment PM
Table 2-40 Ethernet 10GbE Equipment PM Parameters (continued)
Parameter
Counter
type
Definition
(Exclusive Parameter Note)
G3SwcFCB Overrun
Frames discarded due to lack of frame control blocks
resources. This counter could increment under heavy
load.
Frame
G3SwcDP ResetAbort
Frames that were either discarded or corrupted during
a data path reset. This counter could increment when
an equipment switchover (either manual or automatic)
takes place. Corrupted frames may have been
transmitted.
Frame
W3TxFifo IngFCDisc
Frames discarded due to FIFO overflow. This counter
could increment under heavy load of 64-byte frames.
Frame
W3TxAborts
Frames discarded because of GFP errors (payload FCS
error, excessive size) that did not appear until well into
the frame processing. Payload FCS errors are also
counted as “GFP FCS DISCARDS” in EOS port PM
for the affected port.
Frame
Ethernet
Equipment PM
The system provides the following performance monitoring and counters for NGE
equipment (both NGE and NGE Plus) events that occur during normal operation. For
example, discarded frames or excessive traffic on a service.
Table 2-41 Ethernet Equipment PM Parameters
Parameter
(Exclusive Parameter Note)
LAN SPI3 RX FIFO
OVERRUNS
Counter
type
Definition
Count of overrun events on FIFO for SPI-3 bus in
LAN to Gardenia direction.
Event
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.
LAN SPI3 TX CRC ERRORS
Count of SPI-3 CRC error events in the Gardenia to
LAN direction.
Event
There could be several events for a single discarded
frame, or one event for several discarded frames.
Page 2-64
Turin Networks
Release OPS4.0.x
Chapter 4
Ethernet Performance Parameters
Ethernet Equipment PM
Table 2-41 Ethernet Equipment PM Parameters (continued)
Parameter
Definition
(Exclusive Parameter Note)
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.
Counter
type
Event
There could be several events for a single discarded
frame, or one event for several discarded frames.
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 card’s
maximum Jumbo Frame Size.
Frame
GARDENIA FLT DISCARDS
Count of seconds during which Gardenia discarded
frames due to overflow of internal multicast queue.
Errored
seconds
This is a normal condition that can arise when there is
more multicast traffic than the system can handle.
GARDENIA BUFFER
ABORTS
Count of seconds during which Gardenia discarded
frames due to inability to access RLDRAM buffer
memory.
Errored
seconds
This could occur if ingress traffic contains a high
volume of 81-byte frames.
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.
Event
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 card from the
Ethernet ports.
There could be several events for a single discarded
frame, or one event for several discarded frames.
WAN ENCAP UNDERRUNS
Underrun events on SPI-3 bus in Gardenia to WAN
direction.
Event
There could be several events for a single discarded
frame, or one event for several discarded frames.
WAN TX ABORTS
Release OPS4.0.x
Frames discarded due to unspecified errors in
Gardenia to WAN direction.
Turin Networks
Frame
Page 2-65
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Ethernet Equipment PM
Table 2-41 Ethernet Equipment PM Parameters (continued)
Parameter
(Exclusive Parameter Note)
Counter
type
Definition
G3CpDiscards
Frames discarded inside the analysis block. Includes
frames discarded because they could not be assigned
to any activated service, as well as possible internal
errors.
Frame
G3Spi4Rx Overrun
SPI-4 RX overruns. This counter could increment
under heavy load of 64-byte frames. Each event may
correspond to one or more discarded frames.
Event
G3SwcBuf RAMOverrun
Frames discarded because no buffer was available to
hold it (all available buffers are in use by queued
frames). Can occur if RED thresholds are set
excessively high for very congested egress ports
Frame
G3SwcPck HdrOverrun
Frames discarded due to lack of packet header
resources. This counter could increment if the offered
load exceeds the card’s limit of 25 million frames per
second.
Frame
G3SwcFCB Overrun
Frames discarded due to lack of frame control blocks
resources. This counter could increment under heavy
load.
Frame
G3SwcDP ResetAbort
Frames that were either discarded or corrupted during
a data path reset. This counter could increment when
an equipment switchover (either manual or automatic)
takes place. Corrupted frames may have been
transmitted.
Frame
W3TxFifo IngFCDisc
Frames discarded due to FIFO overflow. This counter
could increment under heavy load of 64-byte frames.
Frame
W3TxAborts
Frames discarded because of GFP errors (payload FCS
error, excessive size) that did not appear until well into
the frame processing. Payload FCS errors are also
counted as “GFP FCS DISCARDS” in EOS port PM
for the affected port.
Frame
Page 2-66
Turin Networks
Release OPS4.0.x
Chapter 4
Ethernet Port
PM
Ethernet Performance Parameters
Ethernet Port PM
The system provides the following performance monitoring parameters and counters
for Fast Ethernet (10/100BaseTX), Gigabit Ethernet (GbE), 10GbE, and GbE-10 ports.
The Traverse 10GbE ports can process 10 times as many bytes or frames in any
15-minute or 24-hour period as can GbE ports.
Important: The table below contains common, as well as exclusive, PM (where
noted) for: Traverse NGE (both NGE and NGE Plus) 10GbE, GbE-10, 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-42 Ethernet Port PM Parameters
Parameter
Definition
(Exclusive Parameter Note)
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
The number of transmitted 64-byte frames, including bad
frames.
(Traverse Legacy Ethernet only)
TX PKT 65-127
(Traverse Legacy Ethernet only)
TX PKT 128-255
(Traverse Legacy Ethernet only)
TX PKT 256-511
(Traverse Legacy Ethernet only)
TX PKT 512-1023
(Traverse Legacy Ethernet only)
TX PKT 1024-1518
(Traverse Legacy Ethernet only)
TX PKT > 1518
(Traverse Legacy Ethernet only)
Release OPS4.0.x
The number of transmitted frames, 65 to 127 bytes in length,
including bad frames.
The number of transmitted frames, 128 to 255 bytes in length,
including bad frames.
The number of transmitted frames, 256 to 511 bytes in length,
including bad frames.
The number of transmitted frames, 512 to 1023 bytes in length,
including bad frames.
The number of transmitted frames, 1024 to 1518 bytes in
length, including bad frames.
The number of transmitted frames, greater than or equal to
1519 bytes in length, including bad frames.
Turin Networks
Page 2-67
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Ethernet Port PM
Table 2-42 Ethernet Port PM Parameters (continued)
Parameter
Definition
(Exclusive Parameter Note)
RX UNICAST1
The number of unicast frames received, with length between
64 bytes and the maximum size, with no errors.
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
The number of received 64-byte frames, including bad frames.
(Not applicable to Traverse NGE, 10GbE or
GbE-10)
RX PKT 65-127
(Not applicable to Traverse NGE, 10GbE or
GbE-10)
RX PKT 128-255
(Not applicable to Traverse NGE, 10GbE or
GbE-10)
RX PKT 256-511
(Not applicable to Traverse NGE, 10GbE or
GbE-10)
RX PKT 512-1023
(Not applicable to Traverse NGE, 10GbE or
GbE-10)
RX PKT 1024-1518
(Not applicable to Traverse NGE, 10GbE or
GbE-10)
RX PKT > 1518
(Not applicable to Traverse NGE, 10GbE or
GbE-10)
RX NO DELIMITER
(Traverse Legacy Ethernet only)
Page 2-68
The number of received frames, 65 to 127 bytes in length,
including bad frames.
The number of received frames, 128 to 255 bytes in length,
including bad frames.
The number of received frames, 256 to 511 bytes in length,
including bad frames.
The number of received frames, 512 to 1023 bytes in length,
including bad frames.
The number of received frames, 1024 to 1518 bytes in length,
including bad frames.
The number of received frames, greater than or equal to 1519
bytes in length, including bad frames.
The number of frames received without start of frame
delimiter detection but with carrier assertion.
Turin Networks
Release OPS4.0.x
Chapter 4
Ethernet Performance Parameters
Ethernet Port PM
Table 2-42 Ethernet Port PM Parameters (continued)
Parameter
Definition
(Exclusive Parameter Note)
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
The number of outbound frames discarded by this port due to
aborted frames and underruns.
(Traverse NGE, 10GbE or GbE-10 only)
RX DELAY DISCARDS
(TE-100 Ethernet only)
RX MTU DISCARDS
(Not applicable to TE-100 Ethernet)
RX ALIGNMENT ERR
(Traverse Legacy Ethernet only)
Number of frames discarded by this interface due to excessive
transit delay through the bridge.
Number of frames discarded by this interface due to an
excessive size.
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
The number of bytes transmitted in bad frames.
(Traverse Legacy Ethernet only)
RX BYTES2
The number of bytes received in good frames.
RX BYTES BAD
The number of bytes received in bad frames.
(Traverse Legacy Ethernet only)
TX SINGLE COLL
(10/100BaseTX only)
TX MULTIPLE COLL
(10/100BaseTX only)
TX DEFERRED FRAMES
(10/100BaseTX only)
Release OPS4.0.x
The number of successfully transmitted frames on a particular
interface for which transmission is inhibited by exactly one
collision. Also counted as a successful transmission.
Half-duplex operation only.
The number of successfully transmitted frames on a particular
interface for which transmission is inhibited by more than one
collision. Also counted as a successful transmission.
Half-duplex operation only.
The number of frames for which the first transmission attempt
on a particular interface is delayed because the medium is
busy. Does not include frames involved in collisions.
Half-duplex operation only.
Turin Networks
Page 2-69
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Ethernet Service Port PM
Table 2-42 Ethernet Port PM Parameters (continued)
Parameter
Definition
(Exclusive Parameter Note)
TX LATE COLL
(10/100BaseTX only)
TX EXCESSIVE 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.
The number of frames for which transmission on a particular
interface fails due to excessive collisions. Half-duplex
operation only.
1
Traverse NGE, 10GbE or GbE-10 do not include PAUSE frames.
2
Traverse NGE, 10GbE or GbE-10 include packets that are < 64 or > MTU with CRC errors.
3
Traverse NGE, 10GbE or GbE-10 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.
5
TE-100 Ethernet includes align errors as well.
6
Traverse NGE, 10GbE or GbE-10 include PAUSE frames.
Ethernet
Service Port
PM
The system provides the following performance monitoring parameters and counters
for Traverse NGE (both NGE and NGE Plus), 10GbE or GbE-10 ports.
In a Traverse node Shelf View, click an Ethernet port, then click the Performance tab
to view these parameters in the order given.
Table 2-43 Ethernet Service Port PM Parameters
Parameter
Definition
(Exclusive Parameter Note)
TX BYTES
(NGE and NGE Plus only)
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.
Page 2-70
Turin Networks
Release OPS4.0.x
Chapter 4 Ethernet Performance Parameters
Small Form-Factor Pluggable Optical Port PM
Table 2-43 Ethernet Service Port PM Parameters (continued)
Parameter
Definition
(Exclusive Parameter Note)
RX LOCAL DISCARDS
(Not applicable to Traverse 10GbE or
GbE-10)
RX HARDWARE PACKET
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.
On NGE cards, indicates 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.
On 10GbE and GbE-10 ports, indicates the number of local
discards, Spanning Tree discards, and packets discarded due to
an unclassifiable hardware error.
Small
Form-Factor
Pluggable
Optical Port
PM
The Traverse system provides the following performance (diagnostic) monitoring
parameters for the small form-factor pluggable (SFP) and 10 Gigabit small form-factor
pluggable (XFP) optical ports.
Table 2-44 SFP (and XFP) 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.
Release OPS4.0.x
Turin Networks
Page 2-71
Node Operations and Maintenance Guide, Section 2: Performance Monitoring
Small Form-Factor Pluggable Optical Port PM
Page 2-72
Turin Networks
Release OPS4.0.x
S ECTION 3
E QUIPMENT LED S TATUS
S ECTION 3SYSTEM M ONITORING
S ECTION 3
Contents
Chapter 1
LEDs and Module Status
PDAP LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Front Inlet Fan Tray Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Fan Tray Holder LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Traverse Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Power and Standby LED Indicators—All Modules . . . . . . . . . . . . . . . . . . . . . 3-8
General Control Module (GCM) LED Indicators . . . . . . . . . . . . . . . . . . . . . . . 3-9
Electrical Module Port LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Optical Module Port LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Ethernet Module Port LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Ethernet Termination Connector LED Indicators. . . . . . . . . . . . . . . . . . . . . . . 3-12
List of Figures
Figure 3-1
Figure 3-2
Figure 3-3
Figure 3-4
Figure 3-5
PDAP-2S LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
PDAP-4S LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Front Inlet Fan Card with LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Fan Tray Holder with LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Physical Card LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Table 3-1
Table 3-2
Table 3-3
Table 3-4
Table 3-5
Table 3-6
Table 3-7
Table 3-8
Table 3-9
Table 3-10
Table 3-11
PDAP LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Front Inlet Fan Card LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Fan Tray Holder LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Power and Active/Standby—All Cards . . . . . . . . . . . . . . . . . . . . . 3-8
GCM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Timing Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Ethernet Link (OSS and Craft 10/100BaseT) . . . . . . . . . . . . . . . . 3-10
Electrical Card/Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Optical Card/Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
GbE and Fast Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
GbE and Fast Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
List of Tables
Release OPS4.0.x
Turin Networks
Page i
Node Operations and Maintenance Guide, Section 3 Equipment LED Status
Page ii
Turin Networks
Release OPS4.0.x
S ECTION 3EQUIPMENT LED STATUS
Chapter 1
LEDs and Module Status
Introduction
There are light emitting diodes (LEDs) on several pieces of Turin product family
equipment to provide visual status.
This chapter provides information on each of the LEDs and what they indicate:
• PDAP LEDs, page 3-2
• Front Inlet Fan Tray Module LEDs, page 3-4
• Fan Tray Holder LEDs, page 3-5
• Traverse Module LEDs, page 3-7
• Power and Standby LED Indicators—All Modules, page 3-8
• General Control Module (GCM) LED Indicators, page 3-9
• Electrical Module Port LED Indicators, page 3-10
• Optical Module Port LED Indicators, page 3-11
• Ethernet Module Port LED Indicators, page 3-11
•
Release OPS4.0.x
Turin Networks
Page 3-1
Node Operations and Maintenance Guide, Section 3: Equipment LED Status
PDAP LEDs
PDAP LEDs
The locations of the Power Distribution and Alarm Panel (PDAP-2S, or PDAP-4S)
LEDs are shown in the following drawings. Refer to Table 3-1 PDAP LEDs for
information on how to interpret the PDAP LED indicators.
GMT Fuse
Block
Power
Input
Power
“A”
GMT Fuse
Block
Power
Critical
Minor
Major
Input
Power
“B”
Figure 3-1 PDAP-2S LEDs
TPA Fuses “B”
TPA Fuses “A”
Input
Power
“A”
GMT
Fuse
Input
Power
“B”
Critical
Minor
Major
OPS 00024
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 LEDs
LED
Critical
Summary
Alarm
At least one
critical alarm in
the rack.
GMT Fuse
Block
Power
At least one fuse
failure in GMT
Fuse Block “A” or
“B.”
Input
Power
N/A
Major
Summary
Alarm
Page 3-2
RED
GREEN
AMBER
OFF
N/A
N/A
No critical alarms
for the entire rack
All fuses are good
in GMT Fuse
Block “A” or “B.”
Power from
Battery “A” or
“B” input.
At least one major
alarm in the rack.
N/A
Turin Networks
No power
N/A
No power
N/A
N/A
No major alarms
for the entire rack
Release OPS4.0.x
Chapter 1 LEDs and Module Status
PDAP LEDs
Table 3-1 PDAP LEDs (continued)
Release OPS4.0.x
LED
RED
GREEN
AMBER
OFF
Minor
Summary
Alarm
N/A
N/A
At least one minor
alarm exists in the
rack.
No minor alarms
for the entire rack
TPA Fuse
Power
(PDAP-4S
only)
The TPA fuse has
failed.
TPA fuse is good
Turin Networks
N/A
N/A
Page 3-3
Node Operations and Maintenance Guide, Section 3: Equipment LED Status
Front Inlet Fan Tray Module LEDs
Front Inlet Fan
Tray Module
LEDs
The location of the front inlet fan tray module LEDs are shown in the following
drawing. Refer to Table 3-2 Front Inlet Fan Card LEDs for information on how to
interpret LED indicators.
Important: This topic refers to the LEDs on the fan module of the
redesigned front inlet fan tray with integrated air ramp unit. Refer to Fan
Tray Holder LEDs, page 3-5 if you are viewing an original fan tray unit
with a separate air ramp unit.
Traverse 1600 FIFT
Traverse 600 FIFT
Fan Failure
(red)
Power
(green)
Fan Failure
(red)
OPS 00025
Power
(green)
Figure 3-3 Front Inlet Fan Card with LEDs
Table 3-2 Front Inlet Fan Card LEDs
LED
RED
GREEN
Power
N/A
Power on.
•
•
Fan
Failure
Page 3-4
•
At least one fan card,
fan tray EEPROM or
thermistor has failed.
Check and replace
the fan tray and/or
card.
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.
Turin Networks
OFF
No power.
•
•
•
All fans are working.
Communication with
GCM is good.
All temperature
indications are good.
N/A
Release OPS4.0.x
Chapter 1 LEDs and Module Status
Fan Tray Holder LEDs
Fan Tray
Holder LEDs
This topic applies to the original fan tray unit with separate air ramp unit (pre-Release
1.4). Refer to Front Inlet Fan Tray Module LEDs, page 3-4 if you are viewing the fan
module of the redesigned front inlet fan tray with integrated air ramp unit.
The locations of the fan tray holder LEDs are shown in the following drawing. Refer to
Table 3-2 Front Inlet Fan Card LEDs for information on how to interpret LED
indicators.
Fan Failure (red) Power (green)
OPS 0026
Fan Failure
(red)
Power
(green)
OPS 00026
Figure 3-4 Fan Tray Holder with LEDs
Table 3-3 Fan Tray Holder LEDs
LED
RED
GREEN
Power
N/A
Power on.
•
•
Fan
Failure
•
Release OPS4.0.x
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.
Turin Networks
OFF
No power.
•
•
•
All fans are working.
Communication with
GCM is good.
All temperature
indications are good.
N/A
Page 3-5
Node Operations and Maintenance Guide, Section 3: Equipment LED Status
Fan Tray Holder LEDs
Page 3-6
Turin Networks
Release OPS4.0.x
Chapter 1 LEDs and Module Status
Traverse Module LEDs
Traverse
Module LEDs
The locations of common and specific card LEDs is shown in the following graphic.
PWR
(Power)
Alarms:
CRITICAL/MAJOR
MINOR
ACO ON
ACTV/
STNBY
(Active/Standby)
ACO
Optical
Port
Timing:
LOCKED/
UNLOCKED
FREE RUN/
HOLDOVER
DS1, DS3/E3,
E1, OC-N/STM-N
and ETH Port
Indicators
ETHERNET LINK
OSS and Craft
10/100BaseT
Ethernet Interface
(RJ-45)
RS-232 Interface
(DB-9)
DS1
DS3/E3
E1
OC-N/
STM-N
VT
Switch
Ethernet
EGCM
OPS 00015
Figure 3-5 Physical Card LEDs
Release OPS4.0.x
Turin Networks
Page 3-7
Node Operations and Maintenance Guide, Section 3: Equipment LED Status
Power and Standby LED Indicators—All Modules
Power and
Standby LED
Indicators—All
Modules
The LEDs in the following tables apply to all cards.
Table 3-4 Power and Active/Standby—All Cards
RED
Amber
GREEN
OFF
LED
Power
Active/
Standby
Flashing
Solid
Initialization
and diagnosis
is underway
but not
complete
Hardware
failure
detected;
replace the
card
N/A
N/A
Flashing
Solid
Flashing
N/A
N/A
N/A
The card is
unlocked and in
Standby mode.1
Synchronization
with the Active
card is not
complete.
The card is
unlocked. The
card type does not
match the
provisioned card
type or the card is
placed in an
invalid slot.2
The card is
unlocked and in
Standby mode.
Synchronization
with the Active
card is complete.
Solid
Initialization is
complete and
the card is
operational.
The Active
card is
unlocked and
operational.
No power
The card is
locked or
initialization
is not
complete.
1
Does not apply to GbE or OC-N cards.
2
For the Traverse platform, refer to Appendix A—“Card Placement Planning and Guidelines,” page 12-1 for valid card placement
guidelines.
Page 3-8
Turin Networks
Release OPS4.0.x
Chapter 1 LEDs and Module Status
General Control Module (GCM) LED Indicators
General
Control Module
(GCM) LED
Indicators
The LEDs in the following tables apply to GCM cards 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 Card/Port Status.
Table 3-5 GCM Alarms
RED
AMBER
Solid
Solid
LED
Critical/
Major
OFF
One or more critical or major
alarms are active. Indicates a
service-affecting event(s) and
requires immediate action.
Minor
N/A
Alarm
Cutoff
(ACO)
N/A
No critical or major alarms
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
The audible alarm is cut off
(silenced).
The audible alarm is not cut off
(not silenced).
Table 3-6 Timing Subsystem
RED
GREEN
AMBER
LED
OFF
Solid
Locked/
Unlocked
Selected
timing input
reference is
lost.
Free-run/
Hold-over
N/A
Flashing
Solid
Lost-phase
mode. LED
flashes at 500ms
on/off rate.
Locked to a
timing input
reference1
Tracking a
timing reference
signal, but not
completely out
of free-run
mode. LED
flashes at 500ms
on/off rate.
Free-run mode2
Flashing
Solid
N/A
N/A
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 in
free-run mode.
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.
Release OPS4.0.x
Turin Networks
Page 3-9
Node Operations and Maintenance Guide, Section 3: Equipment LED Status
Electrical Module Port LED Indicators
:
Table 3-7 Ethernet Link (OSS and Craft 10/100BaseT)
RED
GREEN
OFF
LED
Ethernet
Port
Electrical
Module Port
LED Indicators
Flashing
Solid
Flashing
Running
diagnostics or
in loopback
mode.
Port is
unlocked, but
there is no link
integrity/
signal.
Transmitting
or receiving
frames.
Solid
Operational,
the link is
active.
Port is locked.
The LEDs in the following table apply to electrical (DS1, DS3, E1, E3, and VT/TU
Switch) cards only.
Table 3-8 Electrical Card/Port Status
RED
LED
Ports
Page 3-10
Flashing
Running
diagnostics or in
loopback mode.
GREEN
Solid
Unlocked and a
port failure is
detected (LOS,
LOF/OOF, AIS,
RFI)
Flashing
N/A
Turin Networks
OFF
Solid
Unlocked and
receiving a valid
signal.
Card initialization
is not complete,
the card is in
Standby mode, or
the port is locked.
Release OPS4.0.x
Chapter 1 LEDs and Module Status
Ethernet Module Port LED Indicators
Optical Module
Port LED
Indicators
The LEDs in the following table apply to optical cards (OC-N/STM-N) and to the optical ports (OC-12/STM-4 or OC-48/STM-16) on the GCM with integrated optics cards.
Table 3-9 Optical Card/Port Status
RED
LED
Ports
Flashing
Running
diagnostics or in
loopback mode
Ethernet
Module Port
LED Indicators
GREEN
Solid
Flashing
Solid
Unlocked and
receiving a valid
signal; in Standby
mode for a 1+1
facility protection
group
Unlocked and a
port failure is
detected (LOS,
LOF/OOF, AIS,
RFI)
OFF
Unlocked and
receiving a valid
signal
Card initialization
is not complete or
the port is locked
The LEDs in the following table apply to the optical 10GbE, GbE-10, GbE and FE
(100Base FX and 10/100BaseTX) combination cards.
Table 3-10 GbE and Fast Ethernet Port
RED
GREEN
OFF
LED
Ethernet
Port
Release OPS4.0.x
Flashing
Solid
Flashing
Solid
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.
Turin Networks
Card
initialization
is not
complete or
the port is
locked
Page 3-11
Node Operations and Maintenance Guide, Section 3: Equipment LED Status
Ethernet Termination Connector LED Indicators
Ethernet
Termination
Connector LED
Indicators
The LEDs in the following table apply to the optical 10GbE, GbE-10, GbE and FE
(100Base FX and 10/100BaseTX) combination cards.
Table 3-11 GbE and Fast Ethernet Port
RED
GREEN
OFF
LED
Ethernet
Port
Page 3-12
Flashing
Solid
Flashing
Solid
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.
Turin Networks
Card
initialization
is not
complete or
the port is
locked
Release OPS4.0.x
S ECTION 4
D IAGNOSTICS
S ECTION 4
Contents
Chapter 1
Diagnostics Overview
Symptoms and Recommended Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Chapter 2
Traverse Transmit and Receive Signal Levels
Traverse Optical Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Fast Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
GbE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
10GbE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
OC-3/STM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
OC-12/STM-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
OC-48/STM-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
OC-192/STM-64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Chapter 3
TraverseEdge 100 Transmit and Receive Signal Levels
TE-100 Optical Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Chapter 4
Loopback Tests
DS1 and DS3 Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
DS1 and DS3 Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . 4-12
DS1 and DS3 Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
EC-3 and STM-1E Loopback Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
EC-3and STM-1E Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . 4-13
EC-3 and STM-1E Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
E1 and E3 Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
E1 and E3 Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
E1 and E3 Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Ethernet Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Ethernet Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Ethernet Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
SONET/SDH Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
SONET/SDH Facility Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
SONET/SDH Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Performing Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Chapter 5
Other Diagnostics
Release OPS4.0.x
Turin Networks
Page i
Node Operations and Maintenance Guide, Section 4 Diagnostics
Power On Self Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Alarm Cut-Off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
LED Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
List of Figures
Figure 4-1
Figure 4-2
Figure 4-3
Figure 4-4
Figure 4-5
Figure 4-6
Figure 4-7
Figure 4-8
Figure 4-9
Figure 4-10
Figure 4-11
Figure 4-12
DS-x Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
DS-x Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
EC-3/STM-1E Facility Payload Loopback . . . . . . . . . . . . . . . . . . . 4-13
EC-3/STM-1E Terminal Loopback. . . . . . . . . . . . . . . . . . . . . . . . . 4-13
E-x Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
E-x Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Ethernet Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . 4-15
Ethernet Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
SONET/SDH Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . 4-17
SONET/SDH Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Setting Up a Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Table 4-1
Table 4-2
Table 4-3
Table 4-4
Symptoms and Recommended Actions . . . . . . . . . . . . . . . . . . . . 4-2
Optical Interface Specification Summary Table. . . . . . . . . . . . . . . 4-4
SONET, STM, and GbE Optics . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Performing Loopback Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
List of Tables
Page ii
Turin Networks
Release OPS4.0.x
S ECTION 4DIAGNOSTICS
Chapter 1
Diagnostics Overview
Introduction
The diagnostics section provides various diagnostic tips and tools to assist you isolate,
and find resolution to, abnormal conditions observed while monitoring the Traverse
system.
This chapter includes the following topics:
• Symptoms and Recommended Actions, page 4-2
• Chapter 2—“Traverse Transmit and Receive Signal Levels,” page 4-3
• Chapter 3—“TraverseEdge 100 Transmit and Receive Signal Levels,” page 4-7
• Chapter 4—“Loopback Tests,” page 4-11
• Chapter 5—“Other Diagnostics,” page 4-21
Release OPS4.0.x
Turin Networks
Page 4-1
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
Turin Networks
System
Area
Environmental
Alarms
Symptom Description
Environmental Alarm input or
output is incorrect.
Scope
Node
•
•
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
Probable Cause
Recommended Action
Incorrect alarm cable
connections
Environmental Alarm
Module (EAM) failure
• Incorrect alarm cable connections. See the Traverse Installation
and Commissioning Guide, Section 1—Fault Management,
Chapter 2—“Alarms, Events, and Recommended Actions,”
page 1-21
• Replace EAM. See Section 6—Routine Maintenance,
Chapter 1—“Routine Maintenance,” Environmental Alarm
Module Replacement (Traverse only), page 6-21
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 TR3.0.x
Traverse Software Upgrade,” page 7-1
Node Operations and Maintenance Guide, Section 4: Diagnostics
Symptoms and Recommended Actions
Page 4-2
Symptoms and
Recommended
Actions
Release OPS4.0.x
S ECTION 4DIAGNOSTICS
Chapter 2
Traverse Transmit and Receive Signal Levels
Introduction
Release OPS4.0.x
This chapter provides optical parameter specifications to assist you in handling a
Loss of Signal (LOS) condition on a Traverse optical module.
Turin Networks
Page 4-3
The table below provides a summary of all optical interface specifications.
WARNING! The optical receiver of the OC-N/STM-N Long Reach cards 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
Card Optic Type
Guaranteed Link
Typical
Nominal TX
Wavelength
TX Wavelength
Range
RX Wavelength
Range
Transmitter
Output
Power1
(nm)
(nm)
(nm)
(dBm)
(dBm)
(dB)
(mi)
(km)
Receiver
Signal1,2
Budget
1
Distance
Objective3,
4
Turin Networks
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 ZX
1550
1530 to 1580
1260 to 1620
-1 to -5
-22 to -3
21
49.71
80
1260 to 1620
-1 to 4
-18 to -0
17
24.85
40
GbE CWDM
10GbE
OC-3/STM-1
OC-12/STM-4
1470 to 1610
(8 channels at 20 nm intervals)
10GbE LR
1310
1260 to 1355
1260 to 1600
-7.2 to 0.5
-11.6 to 0.5
4.4
6.21
10
10GbE ER
1550
1530 to 1565
1270 to 1600
-2 to 2
-13 to -1
11
24.85
40
10GbE ZR
1550
1530 to 1565
1270 to 1600
-1 to 4
-23 to -7
22
49.71
80
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
26
49.71
80
1310
1274 to 1356
1260 to 1600
-16 to -8
-27 to -7
11
9.32
15
1550
1480 to 1580
1260 to 1600
-4 to 2
-26 to -8
22
49.71
80
OC-12 IR1/STM-4 SH15
OC-12 LR2/STM-4 LH2
5
Node Operations and Maintenance Guide, Section 4: Diagnostics
Traverse Optical Interface Specifications
Page 4-4
Traverse
Optical
Interface
Specifications
Release OPS4.0.x
Release OPS4.0.x
Table 4-2 Optical Interface Specification Summary Table (continued)
Optical
Interface
Card Optic Type
OC-48/STM-16
OC-48 SR1/STM-16 SH1
OC-48 IR1/STM-16 SH1
5
5
5
OC-48 LR1/STM-16 LH1
5
OC-48 LR2/STM-16 LH2
OC-48 LR2/STM-16 LH CWDM
OC-192/STM-64
6
TX Wavelength
Range
RX Wavelength
Range
Transmitter
Output
Power1
(nm)
(nm)
(nm)
(dBm)
(dBm)
(dB)
(mi)
(km)
1310
1266 to 1360
1260 to 1600
-11 to -3
-17 to -3
6
1.24
2
1310
1260 to 1360
1260 to 1600
-6 to 0
-17 to 0
11
9.32
15
1310
1280 to 1335
1260 to 1600
-3 to 3
-26 to -8
23
24.85
40
1550
1500 to 1580
1260 to 1600
-3 to 3
-25 to -8
22
49.71
80
1470 to 1610
(8 channels at 20 nm intervals)
1260 to 1620
-1 to 5
-25 to -8
24
49.71
80
1529.55 to 1562.23 (42 channels)
1260 to 1600
-1 to 4
-26 to -8
25
62.14
100
Receiver
Signal
1,2
Budget1
Distance
Objective3,
4
OC-48 VR2/STM-16 VLH
1550
1530 to 1560
1260 to 1600
4 to 10
-25 to -8
29
62.14
100
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
-15 to -1
13
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
Page 4-5
1
These values account for the connector loss from connection to the optical interface and the worst case optical path penalty.
2
Pseudo Random Bit Sequence, Bit Error Rate is 2 23 -1 PRBS, BER=10 -12
3
Per IEEE 802.3-2005 for Ethernet and assumes a fiber loss of 0.4 dB/km for 1330 m, pr 0.25 dB/km for 1550 nm (including splices, connnectors, etc.). Per GR-253-CORE, Issue 3,
for SONET/SDH and assumes a fiber loss of 0.55 dB/km for 1310 nm or 0.275 dB/km for 1550 nm (including splices, connnectors, etc.).
4
Turin recommends customers to take actual fiber readings, as these values are based on standards qualification.
5
GCM with integrated optics are also available. See the Traverse Product Overview Guide, Section 3—Card (Module) Descriptions, Chapter 1—“General Control Module (GCM)
Cards,” page 3-1 for more information.
6
The OC-192/STM-64 LR2 and LR/LH DWDM card link budget (22 dB) is with forward error correction (FEC) off. Add an additional 3 dB with FEC on.
Chapter 2 Traverse Transmit and Receive Signal Levels
Traverse Optical Interface Specifications
Turin Networks
OC-48 ELR/STM-16 LH ITU DWDM
Guaranteed Link
Typical
Nominal TX
Wavelength
Turin Networks
Node Operations and Maintenance Guide, Section 4: Diagnostics
Traverse Optical Interface Specifications
Page 4-6
Release OPS4.0.x
S ECTION 4DIAGNOSTICS
Chapter 3
TraverseEdge 100 Transmit and Receive Signal
Levels
Introduction
Release OPS4.0.x
This chapter provides optical parameter specifications to assist you in handling a
Loss of Signal (LOS) condition on a TraverseEdge 100 optical port.
Turin Networks
Page 4-7
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.
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
SONET
STM
Turin Networks
Approx
Distance
(km)
Tx Power
Range
(dBm)
Rx Power
Range
(dBm)
Dispersion
Penalty
(db)
Attenuation
Range
Extinction
Ratio (dB)
Tx
Wavelength
Range
(nm)
Rx
Wavelength
Range
(nm)
Dispersion
Tolerance
(ps/nm)
Temperature
Range
(degC)
-15 to -8
-29 to -7
0
0 to 14
8.2
1261 to 1360
1260 to 1600
0
-40 to 85
OC-3
IR-1
STM-1
S-1.1
15
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
OC-48
ELR
STM-16
80
0 to 5
-26 to -8
2
13 to 26
8.2
1470 to 1610
1260 to 1600
1760
-5 to 70
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
Release OPS4.0.x
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
Notes on the table:
• All TE-100 optical ports use SFP optical cards.
• 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 card will operate over a larger range than specified.
Node Operations and Maintenance Guide, Section 4: Diagnostics
TE-100 Optical Interface Specifications
Page 4-8
TE-100 Optical
Interface
Specifications
Chapter 3
Release OPS4.0.x
TraverseEdge 100 Transmit and Receive Signal Levels
TE-100 Optical Interface Specifications
Turin Networks
Page 4-9
Node Operations and Maintenance Guide, Section 4: Diagnostics
TE-100 Optical Interface Specifications
Page 4-10
Turin Networks
Release OPS4.0.x
S ECTION 4DIAGNOSTICS
Chapter 4
Loopback Tests
Introduction
The TransNav Management System provides diagnostic loopback testing for
troubleshooting ports and spans. The system supports the following loopback tests:
• Facility—To troubleshoot the line interface unit of a card, the backplane, or the
cabling
• Terminal—To troubleshoot a circuit path and loop back to the card
WARNING! Loopback tests interrupt traffic flow; do not perform
them on nodes providing service.
Important: Facility and terminal loopbacks cannot be performed on ports, part of a
BLSR/MS-SP Ring, or on a 1+1 APS/MSP protection group.
This chapter contains the following module-specific loopback tests:
• DS1 and DS3 Loopback Tests, page 4-12
• EC-3 and STM-1E Loopback Tests, page 4-13
• E1 and E3 Loopback Tests, page 4-14
• Ethernet Loopback Test, page 4-15
• SONET/SDH Loopback Tests, page 4-17
See Performing Loopback Tests, page 4-18 for a step-by-step procedure on how to
perform loopback tests.
See Equipment States, page 4-20 for a discussion of the Traverse operational and
administrative states.
Release OPS4.0.x
Turin Networks
Page 4-11
Node Operations and Maintenance Guide, Section 4: Diagnostics
DS1 and DS3 Loopback Tests
DS1 and DS3
Loopback
Tests
DS1 and DS3 Facility Payload Loopback
Each node supports a facility payload loopback for each incoming received DS-x
signal. The facility must first be taken out of service prior to initiating the loopback
test.
The facility payload loopback connects the incoming received DS-x signal
immediately to the associated return transmitter, as shown in Figure 4-1. During this
loopback, AIS is inserted and sent to the far end.
Service
between ports
Trunk module
DS-x module
LIU
Test
Set
LIU
AIS
DS-x facility under
loopback test
OPS 00027
Figure 4-1 DS-x Facility Payload Loopback
DS1 and DS3 Terminal Loopback
The node supports terminal loopback for each DS-x signal. The facility must first be
taken out of service prior to initiating the loopback test.
For DS1 and DS3 terminal loopback, the signal is looped back toward the
SONET/SDH system just before being transmitted toward the DS-x line, as shown in
Figure 4-2. This loopback is used to verify the receiver associated with the interface
and the integrity of the transmitted DS-x signal.
Service set up
between ports
DS-x module
Trunk module
LIU
LIU
Test
Set
DS-x facility under
loopback test
OPS 00028
Figure 4-2 DS-x Terminal Loopback
Page 4-12
Turin Networks
Release OPS4.0.x
Chapter 4 Loopback Tests
EC-3 and STM-1E Loopback Tests
EC-3 and
STM-1E
Loopback
Tests
EC-3and STM-1E Facility Payload Loopback
Each node supports a facility payload loopback for each incoming received signal. The
facility must first be taken out of service prior to initiating the loopback test.
The facility payload loopback connects the incoming received signal immediately to
the associated return transmitter, as shown in Figure 4-1. During this loopback, AIS is
inserted and sent to the far end.
Service
between ports
Trunk module
DS-x module
LIU
Test
Set
LIU
AIS
DS-x facility under
loopback test
OPS 00027
Figure 4-3 EC-3/STM-1E Facility Payload Loopback
EC-3 and STM-1E Terminal Loopback
The node supports terminal loopback for each signal. The facility must first be taken
out of service prior to initiating the loopback test.
For terminal loopback, the signal is looped back toward the SONET/SDH system just
before being transmitted toward the line, as shown in Figure 4-2. This loopback is used
to verify the receiver associated with the interface and the integrity of the transmitted
signal.
Service set up
between ports
EC-3/STM-1E
DS-x module
Trunk module
LIU
LIU
Test
Set
DS-x facility under
loopback test
OPS 00028
Figure 4-4 EC-3/STM-1E Terminal Loopback
Release OPS4.0.x
Turin Networks
Page 4-13
Node Operations and Maintenance Guide, Section 4: Diagnostics
E1 and E3 Loopback Tests
E1 and E3
Loopback
Tests
E1 and E3 Facility Payload Loopback
The node supports a facility payload loopback for each incoming received E-x signal.
The facility must first be taken out of service prior to initiating the loopback test.
The facility payload loopback connects the incoming received E-x signal immediately
to the associated return transmitter, as shown in Figure 4-1. During this loopback, AIS
is inserted and sent to the far end.
Service
between ports
Trunk
module
E-x module
LIU
Test
Set
LIU
AIS
E-x facility under
loopback test
OPS 00029
Figure 4-5 E-x Facility Payload Loopback
E1 and E3 Terminal Loopback
The node supports terminal loopback for each E-x signal. The facility must first be
taken out of service prior to initiating the loopback test.
For E1 and E3 terminal loopback, the signal is looped back toward the SONET/SDH
system just before being transmitted toward the E-x line, as shown in Figure 4-2. This
loopback is used to verify the receiver associated with the interface and the integrity of
the transmitted E-x signal.
Service set up
between ports
E-x module
Trunk module
LIU
LIU
Test
Set
E-x facility under
loopback test
OPS 00030
Figure 4-6 E-x Terminal Loopback
Page 4-14
Turin Networks
Release OPS4.0.x
Chapter 4 Loopback Tests
Ethernet Loopback Test
Ethernet
Loopback Test
Ethernet Facility Loopback
The node supports a facility payload loopback for next-generation Ethernet interfaces.
All packets that the Ethernet module receives from a CPE port are transmitted back on
the same CPE port. Service providers can use this to check the local cabling from CPE
device to the node.
Facility loopback does not affect traffic flow on any other Ethernet port. If an Ethernet
port is in an activated Ethernet service, the system prohibits facility loopback. If facility
loopback is active, the system prohibits the activation of any Ethernet service.
Important: When facility loopback is on for the next-generation Ethernet
port, and when no other Ethernet ports on this module are sending or
receiving frames, then the system transmits back to the loopback port all
frames that it receives from that port, with the likely exception of PAUSE
frames and errored frames.
The facility payload loopback connects the incoming received signal immediately to
the associated return transmitter, as shown in Figure 4-7. The facility loopback is in
effect across module reboot.
Figure 4-7 Ethernet Facility Payload Loopback
Ethernet Terminal Loopback
The node supports terminal loopback for next-generation Ethernet interfaces. Ethernet
terminal loopback uses the forwarding relationship established by an Ethernet service
to loop back packets to their sources, instead of transmitting them out the looped-back
facility. This function requires the facility be in use by one or more activated Ethernet
services that use point-to-point forwarding. (i.e., Line services).
Release OPS4.0.x
Turin Networks
Page 4-15
Node Operations and Maintenance Guide, Section 4: Diagnostics
Ethernet Loopback Test
For Ethernet terminal loopback, the signal is looped back toward the SONET/SDH
system just before being transmitted toward the Ethernet interface.
Figure 4-8 Ethernet Terminal Loopback
Page 4-16
Turin Networks
Release OPS4.0.x
Chapter 4 Loopback Tests
SONET/SDH Loopback Tests
SONET/SDH
Loopback
Tests
SONET/SDH Facility Loopback
The node supports a facility payload loopback for each OC-N/STM-N facility
(including the OC-12/STM-4 and OC-48/STM-16 facility on the Traverse GCM). The
facility must first be taken out of service prior to initiating the loopback test.
The facility payload loopback connects the incoming received SONET/SDH signal
immediately to the associated return transmitter following the optical-to-electrical
conversion (before scrambling), as shown in Figure 4-9. During this loopback, AIS is
inserted and sent to the far end.
Service
between ports
STS-N
OC-N module
OC-N module
STS-N
Test
Set
LIU
LIU
AIS
SONET facility
under loopback test
OPS 00033
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.
Service set up
between ports
OC-N/STM-N
module
OC-N/STM-N
module
LIU
LIU
Test
Set
SONET/SDH facility
under loopback test
OPS 00034
Figure 4-10 SONET/SDH Terminal Loopback
Release OPS4.0.x
Turin Networks
Page 4-17
Node Operations and Maintenance Guide, Section 4: Diagnostics
Performing Loopback Tests
Performing
Loopback
Tests
Before performing loopback testing, the port’s administrative state must first be
changed to Unlocked.
Important: Loopback tests interrupt data flow; do not perform them on a
port providing service.
Use the vendor’s procedures for setting up your test equipment, then follow the
procedure below to perform loopback tests on a port. For instructions on performing
loopback tests on a TransAccess 100 Mux, see the TransNav Management System GUI
Guide, Section 8—Maintenance and Testing.
Note: The loopback state or port lock/unlock state is be restored after a node database
restore operation is performed. Instead, the system uses the current state of the port to
override what was stored in the node database.
Table 4-4 Performing Loopback Tests
Page 4-18
Step
Procedure
1
In the GUI, display the Shelf View of the node on which you will perform
loopback tests. If you are currently in Map View, double-click the node to
switch to the Shelf View.
2
Select a port on the appropriate module.
3
Click the Config tab.
4
To unlock a port that is currently locked, click the Locked icon
in the
lower left corner to display the Unlocked icon
, then click Apply.
5
Is this 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.
Turin Networks
Release OPS4.0.x
Chapter 4 Loopback Tests
Performing Loopback Tests
Table 4-4 Performing Loopback Tests (continued)
Step
8
Procedure
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
Release OPS4.0.x
The Performing Loopback Tests procedure is complete.
Turin Networks
Page 4-19
Node Operations and Maintenance Guide, Section 4: Diagnostics
Equipment States
Equipment
States
Icons in the bottom left-hand corner of the Config tab indicate the state of the card or
port.
Equipped Operational
state
state
Administrative
state
Figure 4-12 Equipment States
Equipped State: Displays one of the following:
• Equipped: The equipped state of the card or port is Equipped. The equipment is
present in the system.
• Non-Equipped: The equipped state of the card 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 card or port is Unlocked.
• Disabled: The administrative state of the card or port is Locked.
Administrative State: Click the icon until one of the following displays:
•
Lock (default for ports): Do not allow the card or port to operate. Changes the
operational state to Disabled. Initiates protection switching, if applicable.
•
Unlock (default for cards): Allow the card or port to operate.
Page 4-20
Turin Networks
Release OPS4.0.x
S ECTION 4DIAGNOSTICS
Chapter 5
Other 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.
Release OPS4.0.x
Turin Networks
Page 4-21
Node Operations and Maintenance Guide, Section 4: Diagnostics
LED Lamp Test
Page 4-22
Turin Networks
Release OPS4.0.x
S ECTION 5
TEST A CCESS
S ECTION 5
Contents
Chapter 1
Traverse Test Access
Local Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Remote Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Mode Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Access Identifier (AID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Monitor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Split Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Feature Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Test Access Mode Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Monitor Test Access Example (MONE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Per Side Split Test Access Example (SPLTE) . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Series Split Test Access Example (SPLTA) . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Chapter 2
Traverse Test Access Guidelines for the Spirent BRTU Interface
Traverse Platform and Spirent BRTU Interoperability . . . . . . . . . . . . . . . . . . . 5-22
Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface . . . . 5-23
List of Figures
Figure 5-1
Figure 5-2
Figure 5-3
Figure 5-4
Figure 5-5
Figure 5-6
Figure 5-7
Figure 5-8
Figure 5-9
Figure 5-10
Figure 5-11
Figure 5-12
Figure 5-13
Figure 5-14
Figure 5-15
Figure 5-16
Figure 5-17
Release OPS4.0.x
Local Traverse DCS3/1 Test Access . . . . . . . . . . . . . . . . . . . . . . 5-2
Remote Traverse DCS3/1 Test Access . . . . . . . . . . . . . . . . . . . . 5-3
TransNav GUI AID Format Example. . . . . . . . . . . . . . . . . . . . . . . 5-5
Monitor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Split Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Monitor Test Access Configuration—MONE. . . . . . . . . . . . . . . . . 5-9
Example VT TAP (Single FAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
MONE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Service with MONE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Per Side Split Test Access Configuration—SPLTE . . . . . . . . . . . 5-13
Example VT TAP (Single FAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
SPLTE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Service with SPLTE TAC Example . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Series Split Test Access Configuration—SPLTA . . . . . . . . . . . . . 5-17
Example DS1 TAP (Single FAD). . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
SPLTA TAC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Service with SPLTA TAC Example . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Turin Networks
Page i
Node Operations and Maintenance Guide, Section 5 Test Access
Figure 5-18
Turin TransNav GUI and Spirent BRTU REACT OSS Example . . 5-22
Table 5-1
Table 5-2
Table 5-3
Table 5-4
Test Access Mode vs. Service Compatibility Matrix . . . . . . . . . . . 5-4
Monitor Test Access Configuration—MONE . . . . . . . . . . . . . . . . . 5-10
Per Side Split Test Access Configuration—SPLTE. . . . . . . . . . . . 5-14
Series Split Test Access Configuration—SPLTA . . . . . . . . . . . . . 5-18
List of Tables
Page ii
Turin Networks
Release OPS4.0.x
S ECTION 5TEST A CCESS
Chapter 1
Traverse Test Access
Introduction
(SONET network only) Traverse Test Access on digital cross-connect (DCS3/1)
systems and Add-drop Multiplexer (ADM) systems provides for non-intrusive
monitoring and intrusive split testing of DS3/STS-1 and DS1/VT1.5 digital signals.1
Traverse test access is compliant with the following Telcordia standards:
GR-834-CORE, Network Maintenance: Access and Testing, GR-1402-CORE, Network
Maintenance: Access Testing - DS3 HCDS TSC/RTU and DTAU Functional
Requirement, and GR-818 Network Maintenance: Access and Testing - Generic Test
Architecture.
Interoperability with the Spirent® Communication’s network tester, Broadband
Remote Test Unit (BRTU) with REACT® remote test Operations Support System
(OSS), provides the Traverse platform with integrated test access functionality,
enabling carriers to test and monitor any DS1/VT1.5 or DS3/STS-1 service provisioned
on the Traverse switch fabric. See Chapter 2—“Traverse Test Access Guidelines for the
Spirent BRTU Interface,” page 5-21.
For parameter descriptions, see the TransNav Management System GUI Guide,
Section 8—Maintenance and Testing, Chapter 5—“Test Access,” page 8-39.
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
Release OPS4.0.x
(SDH network only) Test access is planned for a future release.
Turin Networks
Page 5-1
Node Operations and Maintenance Guide, Section 5: Test Access
Local Test Access
Local Test
Access
The digital signal for monitoring or testing drops at a logical, pre-configured test access
point (TAP) as shown in the figure below. The user pre-configures the TAP for use in
establishing a test access cross-connect (TAC) to a unidirectional service, a
bidirectional service, or an unmapped termination point (TP). The TAP is given a
unique identifier and is configured as either a single facility access digroup (FAD) or a
dual FAD (DFAD) using one or two service endpoint access identifiers (AIDs),
respectively. A DFAD is just two FADs together in one TAP. DFADs are only used in
test access mode configurations that require two FADs. Refer to Mode
Configurations, page 5-4 for a description of all the test access mode configurations.
For service endpoint information, refer to Access Identifier (AID), page 5-5.
The physical connection for a TAP is a standard cable connection between a DS3 or
DS1 port and the remote test unit (RTU), typically via a patch panel. The user
establishes TACs through the node-level control link or TransNav management system
interface. With the test access cross-connects in service, the user can monitor or
perform tests using the test system controller (TSC) user interface to the RTU.
The Traverse system automatically disconnects all in-service TACs and restores all the
original services upon reboot or communication loss with the RTU.
TransNav
Management
System
(GUI, CLI, or TL1)
Test
System
Controller
(TSC)
DCS3/1
Node-level Control Link
(CLI or TL1)
Termination Point (TP)
of the Circuit Under Test
Patch Panel
Test Access Point (TAP)
(e.g., DS1 port)
Remote
Test
Unit
(RTU)
OPS 00039
Figure 5-1 Local Traverse DCS3/1 Test Access
Page 5-2
Turin Networks
Release OPS4.0.x
Chapter 1
Remote Test
Access
Traverse Test Access
Remote Test Access
Remote test access provides for the configuration of and access to TAPs at a remote
location or network element as shown in the figure below. The remote TAP definition is
a logical VT1.5 termination on an OC-N port. The DS1s for test access may be
physically located at a remote site and/or in an access network element.
The remote test access network configuration is shown in the figure below. At the top
of the figure is the Traverse DCS3/1. A static STS-1 or VT1.5 path is created across the
service provider network from the remote multiplexer to the Traverse DCS3/1. A
remote test unit (RTU) is connected with physical TAPs to a remote access multiplexer.
When references are made to the logical VT1.5 level TAPs on the Traverse DCS3/1,
the resulting test access configurations are effectively cross-connected to DS1 ports on
the remote multiplexer for testing.
DCS3/1
Logical TAPs
(e.g., VT1.5 on OC-N port)
STS-1
or VT
Path
SONET
Network
Remote Access
Multiplexer
Physical TAPs (e.g., DS1)
Remote Test Unit
(RTU)
OPS 00040
Figure 5-2 Remote Traverse DCS3/1 Test Access
Release OPS4.0.x
Turin Networks
Page 5-3
Node Operations and Maintenance Guide, Section 5: Test Access
Mode Configurations
Mode
Configurations
There are multiple monitor and split test access mode configurations available for use
with bidirectional, unidirectional, and unmapped DS3/STS-1 and DS1/VT1.5 services.
The Traverse system supports the following test access mode configurations:
• Monitor Configurations, page 5-6
• Split Configurations, page 5-7
Each test access mode supports a set of service types. The following table shows the
test access mode versus service compatibility matrix where A = Allowed, NA = Not
Allowed.
Table 5-1 Test Access Mode vs. Service Compatibility Matrix
Service
Mode
Page 5-4
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
Turin Networks
Release OPS4.0.x
Chapter 1
Access
Identifier (AID)
Traverse Test Access
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 the TransNav Management
System GUI Guide, Section 9—Appendices, Appendix A—“Service Endpoints.”
Figure 5-3 TransNav GUI AID Format Example
•
Release OPS4.0.x
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 the TransNav
Management System TL1 Guide, Appendix C—AIDs.
Turin Networks
Page 5-5
Node Operations and Maintenance Guide, Section 5: Test Access
Monitor Configurations
Monitor
Configurations
Each monitor configuration is non-intrusive. The original service remains intact so
there is no disruption to customer traffic while monitoring the data flow.
Test access provides three monitor mode configurations:
• MONE - Monitor unidirectional data flow from ingress to egress termination point
• MONF - Monitor unidirectional data flow from egress to ingress termination point2
• MONEF - Monitor bidirectional data flow from both the ingress and egress
termination points
MONE Test Access
E
MONF Test Access
F
E
FAD
F
FAD
MONEF Test Access
E
F
FAD
FAD
OPS 00042
Figure 5-4 Monitor Configurations
2
Page 5-6
If MONF is configured with a DFAD instead of the standard FAD, it uses the second FAD.
Turin Networks
Release OPS4.0.x
Chapter 1
Split
Configurations
Traverse Test Access
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
SPLTA Test Access
SPLTB Test Access
A
A
B
B
FAD
FAD
SPLTE Test Access
SPLTF Test Access
E
E
F
F
FAD
FAD
SPLTEF Test Access
E
F
FAD
FAD
OPS 00043
Figure 5-5 Split Configurations
Release OPS4.0.x
3
If SPLTF is configured with a DFAD instead of the common FAD, it uses the second FAD.
4
If SPLTB is configured with a DFAD instead of the standard FAD, it uses the second FAD.
Turin Networks
Page 5-7
Node Operations and Maintenance Guide, Section 5: Test Access
Feature Set Options
Feature Set
Options
Page 5-8
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Traverse Test Access
Monitor 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.
Monitor Test
Access
Example
(MONE)
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-17
• Per Side Split Test Access Example (SPLTE), page 5-13
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
is active. These states remain intact through the MONE test access mode configuration
and use.
Service to be Tested
DCS
S1
D1
TAP (e.g., DS1)
Monitor Test Access
(Non-Intrusive)
S1
DCS
D1
TAP1
OPS 00011
Figure 5-6 Monitor Test Access Configuration—MONE
Release OPS4.0.x
Turin Networks
Page 5-9
Node Operations and Maintenance Guide, Section 5: Test Access
Monitor Test Access Example (MONE)
Use the following procedure to create the MONE monitor test access configuration.
This configuration allows the test equipment at test access port (TAP1) to monitor the
data flow in the direction from the source (S1) to destination (D1).
Table 5-2 Monitor Test Access Configuration—MONE
Step
Procedure
1
Physically connect the cable for the TAP from the remote test unit (RTU)
into the patch panel connected to the Traverse DSC3/1.
2
Using the TransNav GUI, from the Test Access tab, TAP sub-tab, create a
logical TAP (single FAD) of the same type as the service source
termination point (S1).
Figure 5-7 Example VT TAP (Single FAD)
Page 5-10
Turin Networks
Release OPS4.0.x
Chapter 1 Traverse Test Access
Monitor Test Access Example (MONE)
Table 5-2 Monitor Test Access Configuration—MONE (continued)
Step
Procedure
3
From the Test Access tab, TAC sub-tab, create a Monitor-E (MONE) TAC
from the source (S1) to a logical TAP.
Note: Use the Switch Mode button to switch from one mode
configuration to another. For valid mode changes, see Table 5-1 Test
Access Mode vs. Service Compatibility Matrix.
MONE Mode
TAP1
Service ID
Connected State
Switch Mode
command
Figure 5-8 MONE TAC Example
Release OPS4.0.x
Turin Networks
Page 5-11
Node Operations and Maintenance Guide, Section 5: Test Access
Monitor Test Access Example (MONE)
Table 5-2 Monitor Test Access Configuration—MONE (continued)
Step
4
Procedure
The original service remains intact (enabled) as seen when you select the
Service tab.
Enabled Operational State
Service ID
Figure 5-9 Service with MONE TAC Example
Page 5-12
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Traverse Test Access
Per Side Split Test Access Example (SPLTE)
Per Side Split
Test Access
Example
(SPLTE)
The SPLTE per side split test access configuration is intrusive.
A SPLTE per side split test access configuration is shown in the figure below. At the
top of the figure, a service is provisioned and activated between the source (S1) and
destination (D1). The original service operational state is enabled and the service state
is active. The service under the test operational state is disabled.
Service to be Tested
DCS
S1
D1
TAP (e.g., DS1)
Per Side Split Test Access
(Intrusive)
S1
DCS
TAP1
D1
OPS 00047
Figure 5-10 Per Side Split Test Access Configuration—SPLTE
Release OPS4.0.x
Turin Networks
Page 5-13
Node Operations and Maintenance Guide, Section 5: Test Access
Per Side Split Test Access Example (SPLTE)
Use the following procedure to create the per side split test access configuration.
Table 5-3 Per Side Split Test Access Configuration—SPLTE
Step
Procedure
1
Physically connect the cables for TAP from the remote test unit (RTU) into
the patch panel connected to the Traverse DSC3/1.
2
Using the TransNav GUI, from the Test Access, TAP tab, create a logical
test access point (TAP) (single FAD) of the same type as the source
termination point (S1).
Figure 5-11 Example VT TAP (Single FAD)
Page 5-14
Turin Networks
Release OPS4.0.x
Chapter 1 Traverse Test Access
Per Side Split Test Access Example (SPLTE)
Table 5-3 Per Side Split Test Access Configuration—SPLTE (continued)
Step
3
Procedure
From the Test Access tab, TAC sub-tab, create a per side split (SPLTE)
test access cross-connect (TAC) from the source (S1) to a logical TAP.
Note: Use the Switch Mode button to switch from one mode
configuration to another. For valid mode changes, see Table 5-1 Test
Access Mode vs. Service Compatibility Matrix.
SPLTE Mode
TAP2
Service ID
Connected State
Switch Mode
command
Figure 5-12 SPLTE TAC Example
Release OPS4.0.x
Turin Networks
Page 5-15
Node Operations and Maintenance Guide, Section 5: Test Access
Per Side Split Test Access Example (SPLTE)
Table 5-3 Per Side Split Test Access Configuration—SPLTE (continued)
Step
4
Procedure
The system disables the original service as seen when you select the
Service tab.
Enabled Operational State
Service ID
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
Page 5-16
The Per Side Split Test Access Configuration—SPLTE procedure is
complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Traverse Test Access
Series Split Test Access Example (SPLTA)
Series Split
Test Access
Example
(SPLTA)
The SPLTA series split test access configuration is intrusive.
A SPLTA series split test access configuration is shown in the figure below. At the top
of the figure, a service is provisioned and activated between the source (S1) and
destination (D1). The original service operational state is enabled and the service state
is active. The service under the test operational state is disabled.
Service to be Tested
DCS
S1
D1
TAP (e.g., DS1)
Series Split Test Access
(Intrusive)
S1
DCS
D1
TAP1
OPS 00051
Figure 5-14 Series Split Test Access Configuration—SPLTA
Release OPS4.0.x
Turin Networks
Page 5-17
Node Operations and Maintenance Guide, Section 5: Test Access
Series Split Test Access Example (SPLTA)
Use the following procedure to create the series split test access configuration.
Table 5-4 Series Split Test Access Configuration—SPLTA
Step
Procedure
1
Physically connect the cables for TAP (test access point) from the remote
test unit (RTU) into the patch panel connected to the Traverse DSC3/1.
2
Using the TransNav GUI, from the Test Access tab, TAP sub-tab, create a
logical TAP (single FAD) of the same type as the source termination point
(S1).
Figure 5-15 Example DS1 TAP (Single FAD)
Page 5-18
Turin Networks
Release OPS4.0.x
Chapter 1 Traverse Test Access
Series Split Test Access Example (SPLTA)
Table 5-4 Series Split Test Access Configuration—SPLTA (continued)
Step
Procedure
3
From the Test Access tab, TAP sub-tab, create a series split (SPLTA) test
access cross-connect (TAC) from the source (S1) to a logical TAP.
Note: Use the Switch Mode button to switch from one mode
configuration to another. For valid mode changes, see Table 5-1 Test
Access Mode vs. Service Compatibility Matrix.
SPLTE Mode
TAP3
Service ID
Connected State
Switch Mode
command
Figure 5-16 SPLTA TAC Example
Release OPS4.0.x
Turin Networks
Page 5-19
Node Operations and Maintenance Guide, Section 5: Test Access
Series Split Test Access Example (SPLTA)
Table 5-4 Series Split Test Access Configuration—SPLTA (continued)
Step
4
Procedure
The system disables the original service as seen when you select the
Service tab.
Enabled Operational State
Service ID
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
Page 5-20
The Series Split Test Access Configuration—SPLTA procedure is
complete.
Turin Networks
Release OPS4.0.x
S ECTION 5TEST A CCESS
Chapter 2
Traverse Test Access Guidelines for the
Spirent BRTU Interface
Introduction
This appendix includes the following topics.
• Traverse Platform and Spirent BRTU Interoperability, page 5-22
• Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface,
page 5-23
For general Traverse test access information, refer to Section 5—Test Access,
Chapter 1—“Traverse Test Access,” page 5-1.
Release OPS4.0.x
Turin Networks
Page 5-21
Node Operations and Maintenance Guide, Section 5: Test Access
Traverse Platform and Spirent BRTU Interoperability
Traverse
Platform and
Spirent BRTU
Interoperability
The Traverse platform interoperates with the Spirent® Communication’s Broadband
Remote Test Unit (BRTU) network tester to provide integrated test access functionality.
The Traverse system, TransNav management system graphical user interface (GUI),
and Spirent BRTU with REACT® remote test Operations Support System (OSS)
enables carriers to test and monitor any DS1/VT1.5 or DS3/STS-1 service provisioned
on the Traverse switch fabric.
Turin TransNav GUI
Spirent REACT OSS
Figure 5-18 Turin TransNav GUI and Spirent BRTU REACT OSS Example
Page 5-22
Turin Networks
Release OPS4.0.x
Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface
Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface
Guidelines to
Set Up the
Traverse Test
Access Spirent
BRTU Interface
Release OPS4.0.x
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 the 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 the
TransNav Management System TL1 Guide, Appendix C—AIDs. For service
endpoint mapping definitions, refer to the 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 the TransNav Management System GUI Guide,
Section 8—Maintenance and Testing, Chapter 5—“Test Access,” page 8-39 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.
Turin Networks
Page 5-23
Node Operations and Maintenance Guide, Section 5: Test Access
Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface
Page 5-24
Turin Networks
Release OPS4.0.x
S ECTION 6
R OUTINE M AINTENANCE
S ECTION 6SYSTEM M ONITORING
S ECTION 6
Contents
Chapter 1
Routine Maintenance
Fan Air Filter Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Fan Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000) . . . . . 6-1
Fan Module with Integral Fan Tray (Traverse 600) . . . . . . . . . . . . . . . . . 6-1
Fan Assembly (TE-100). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Fan Tray Module (Legacy Traverse) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Air Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Air Filter Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Air Filter Replacement (Traverse 1600 and Traverse 2000) . . . . . . . . . . . . . . 6-2
Fan Tray Air Filter Replacement (Traverse 600). . . . . . . . . . . . . . . . . . . . . . . 6-4
Air Filter Replacement (TE-100) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Air Filter Replacement (Legacy Traverse). . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Install a Fan Tray Air Filter with Handle (Legacy) . . . . . . . . . . . . . . . . . . . . . . 6-9
PDAP Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
PDAP-15A GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
PDAP-2S Circuit Breaker Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
PDAP-2S GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
PDAP-2S LED Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
PDAP-4S TPA Fuse Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
PDAP-4S GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
PDAP-4S LED Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Environmental Alarm Module Replacement (Traverse only). . . . . . . . . . . . . . 6-21
Non-Field Replaceable Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Chapter 2
Node Database Backup and Restore
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Node Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Guidelines for Node Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Node Database Restore Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Backup and Restore Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
exec node database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
exec node database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Troubleshooting Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Release OPS4.0.x
Turin Networks
Page vii
Node Operations and Maintenance Guide, Section 6 Routine Maintenance
List of Figures
Figure 6-1
Figure 6-2
Figure 6-3
Figure 6-4
Figure 6-5
Figure 6-6
Figure 6-7
Figure 6-8
Figure 6-9
Figure 6-10
Figure 6-11
Figure 6-12
Figure 6-13
Figure 6-14
Figure 6-15
Figure 6-16
Figure 6-17
Figure 6-18
Figure 6-19
Figure 6-20
Front Inlet Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Traverse 600 Fan Assembly Air Filter . . . . . . . . . . . . . . . . . . . . . . 6-4
Fan Cage and Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Removing the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Attaching the Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Air Filter with Springs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Air Filter with Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
PDAP-15A Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
PDAP-2S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
PDAP-2S Assembly - Remove Front Cover . . . . . . . . . . . . . . . . . 6-14
PDAP-2S Assembly - LED Module . . . . . . . . . . . . . . . . . . . . . . . . 6-15
PDAP-2S LED Module Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
PDAP-4S TPA Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
PDAP-4S TPA Fuse and Holder . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
PDAP-4S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
PDAP-4S Assembly - LED Faceplate . . . . . . . . . . . . . . . . . . . . . . 6-20
EAM Location - Traverse 1600 Main Backplane . . . . . . . . . . . . . . 6-21
EAM Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Table 6-1
Table 6-2
Table 6-3
Table 6-4
Table 6-5
Table 6-6
Table 6-7
Table 6-8
Table 6-9
Table 6-10
Table 6-11
Table 6-12
Table 6-13
Table 5-14
Insert a Traverse 1600 and Traverse 2000 Fan Air Filter . . . . . . . 6-3
Insert a Traverse 600 Fan Air Filter. . . . . . . . . . . . . . . . . . . . . . . . 6-4
Replace the Fan Air Filter (TE-100). . . . . . . . . . . . . . . . . . . . . . . . 6-5
Install a Fan Tray Air Filter with Springs (Legacy). . . . . . . . . . . . . 6-7
Install a Fan Tray Air Filter with Handle (Legacy) . . . . . . . . . . . . . 6-9
Replacing PDAP-15A GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Replacing PDAP-2S Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . 6-12
Replacing PDAP-2S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Replacing PDAP-2S LED Module . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Replacing PDAP-4S TPA Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Replacing PDAP-4S GMT Fuses . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Replacing PDAP-4S LED Module . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Replacing EAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
CLI Command Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
List of Tables
Page viii
Turin Networks
Release OPS4.0.x
S ECTION 6ROUTINE MAINTENANCE
Chapter 1
Routine 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-21
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 five fans. The Traverse 2000 fan assembly has six 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 six fans.
The fans draw in cooling air and push the air through the perforated shelf. The fan
module can force up to 200 cubic feet per minute of cooling air.
Fan Assembly (TE-100)
The TE-100 shelf has a pre-installed, field-replaceable fan assembly. The fan assembly
consists of three fans and a replaceable, cleanable air filter.
Fan Tray Module (Legacy Traverse)
This topic applies to the original (pre-Release 1.4) Traverse 1600 and Traverse 2000
fan assembly. The Traverse fan assembly (fan tray holder with fan module and separate
Release OPS4.0.x
Turin Networks
Page 6-1
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
Air Filters
air ramp) cools the GCM and service interface modules. The Traverse 1600 and
Traverse 2000 fan assemblies have ten (6 large and 4 small) and eight (large) fans,
respectively. The fans draw in cooling air from the front and push the air upward
through the perforated shelf. The separate air ramp above the shelf directs the heated air
through to the rear of the shelf.
Air Filters
The air filters on the Traverse and TE-100 systems play a very important role in the
cooling function of the modules.
Important: Fan tray air filters should be checked once every six months
and replaced as necessary.
There are environmental factors that could decrease the amount of time required
between air filter replacements. These environmental factors must be checked
regularly. Any unusual environmental circumstance at the site that causes an increase in
temperature and/or particulate matter in the air might affect performance (for example,
new equipment installation).
Important: The speeds of the cooling fans should be monitored regularly
in order to accurately determine air filter replacement intervals. An
increase in overall fan speed may indicate a clogged filter.
Air Filter
Replacement
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.
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.
Required Equipment: New front inlet fan tray air filter.
The front inlet fan tray air filters are available in 63% or 80% arrestance at 300 FPM—
feet per minute (91.4 meters per minute) depending on your installation requirements.
Page 6-2
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
Air Filter Replacement (Traverse 1600 and Traverse 2000)
The following procedure provides step-by-step instructions on how to insert the front
inlet fan tray air filter.
Table 6-1 Insert a Traverse 1600 and Traverse 2000 Fan Air Filter
Step
1
Procedure
Grasp the air filter flexible pull tab.
OPS 00056
Pull Tab (top view)
Figure 6-1 Front Inlet Air Filter
Release OPS4.0.x
2
Insert the air filter in the gap between the top of the front inlet fan card 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 Install a Fan Tray Air Filter with Springs (Legacy) procedure is
complete.
Turin Networks
Page 6-3
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
Fan Tray Air Filter Replacement (Traverse 600)
Fan Tray Air
Filter
Replacement
(Traverse 600)
When the Traverse 600 fan air filter has been in place for at least six months, or other
environmental factors have contributed to requiring an air filter replacement, use the
following procedure to replace the air filter.
Required Equipment: New air filter
The Traverse 600 fan air filters are available in 63% or 80% arrestance at 300 FPM—
feet per minute (91.4 meters per minute) depending on your installation requirements.
The following procedure provides step-by-step instructions on how to insert the air
filter.
Table 6-2 Insert a Traverse 600 Fan Air Filter
Step
1
Procedure
Grasp the air filter flexible pull tab.
Pull Tab (top view)
OPS 00057
Figure 6-2 Traverse 600 Fan Assembly Air Filter
Page 6-4
2
Insert the air filter in the gap between the fan assembly and the left of the
fan cage. Slide the air filter along the guides until the filter is flush.
3
The Install a Fan Tray Air Filter with Springs (Legacy) procedure is
complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
Air Filter Replacement (TE-100)
Air Filter
Replacement
(TE-100)
When the TE-100 fan air filter has been in place for at least six months, or other
environmental factors have contributed to requiring an air filter replacement, use the
following procedure to replace the air filter.
Required Equipment: New air filter
The fan assembly is in a vertical slot on the left front of the shelf. It draws ambient air
through the perforation on the left wall and forces the air over the system and interface
modules in the horizontal slots.
The fan assembly must be removed before the air filter can be replaced because the
metal air filter attaches to the side of the fan assembly.
The following procedure provides step-by-step instructions on how to replace the
TE-100 air filter.
Table 6-3 Replace the Fan Air Filter (TE-100)
Step
Procedure
1
Loosen the captive fastener that holds the fan assembly in place.
2
Slide the fan assembly out of the fan cage.
Fan Cage
Captive
Fastener
Figure 6-3 Fan Cage and Assembly
3
Lift the old air filter from the fan assembly.
Pull up on the air filter
Figure 6-4 Removing the Air Filter
4
Release OPS4.0.x
Make sure the new air filter is clean and free of dust particles.
Turin Networks
Page 6-5
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
Air Filter Replacement (TE-100)
Table 6-3 Replace the Fan Air Filter (TE-100) (continued)
Step
Procedure
5
Slide the air filter into place, lining up the small tabs with the small holes
on the fan assembly.
Tabs Lined up with Holes
Figure 6-5 Attaching the Air Filter
6
Slide the fan assembly back into the fan cage.
Important: Do not force the fan assembly into position. If it does not
plug in easily, slide it back out and check for any obstructions that might
prevent it from sliding into position.
Page 6-6
7
Tighten the captive fastener to secure the fan assembly in place.
8
The Replace the Fan Air Filter (TE-100) procedure is complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
Air Filter Replacement (Legacy Traverse)
Air Filter
Replacement
(Legacy
Traverse)
This topic applies to air filters for the original fan tray unit without an integrated air
ramp (pre-Release 1.4). Refer to Air Filter Replacement (Traverse 1600 and
Traverse 2000), page 6-2 if you are replacing a front inlet fan tray air filter into the
redesigned front inlet fan tray holder with integrated air ramp unit. Refer to Fan Tray
Air Filter Replacement (Traverse 600), page 6-4 if you are replacing a Traverse 600
fan air filter.
When the fan tray air filter has been in place for at least six months, or other
environmental factors have contributed to requiring an air filter replacement, use one of
the following procedures to replace the filter with either springs or a handle.
Required Equipment: New fan tray air filter
Table 6-4 Install a Fan Tray Air Filter with Springs (Legacy)
Step
1
Procedure
Rotate the air filter pull-tabs out.
Springs
OPS 00058
Pull Tabs
Figure 6-6 Air Filter with Springs
Release OPS4.0.x
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 card 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.
Turin Networks
Page 6-7
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
Air Filter Replacement (Legacy Traverse)
Table 6-4 Install a Fan Tray Air Filter with Springs (Legacy) (continued)
Step
6
Procedure
Lift the fan tray holder front cover into its closed position. Tighten the
captive fasteners to secure it.
OPS 00059
Captive Fasteners
Figure 6-7 Fan Tray Holder Front Cover
Note: The front cover closes very easily when the fan tray card and air
filter are in position. If the cover does not close easily, check the fan tray
card to make sure it is recessed from the front of the fan tray holder.
7
Page 6-8
The Install a Fan Tray Air Filter with Springs (Legacy) procedure is
complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
Install a Fan Tray Air Filter with Handle (Legacy)
Install a Fan
Tray Air Filter
with Handle
(Legacy)
The following procedure provides step-by-step instructions on how to install the fan
tray filter with a handle on the front edge.
Table 6-5 Install a Fan Tray Air Filter with Handle (Legacy)
Step
Procedure
1
Hold the air filter with the metal window-pane side down with the handle
facing to the front.
OPS 00060
Handle
Figure 6-8 Air Filter with Handle
Release OPS4.0.x
2
Insert the air filter in the gap between the fan tray card 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 card.
Turin Networks
Page 6-9
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
PDAP Maintenance
Table 6-5 Install a Fan Tray Air Filter with Handle (Legacy) (continued)
Step
4
Procedure
Lift the fan tray holder front cover into its closed position. Tighten the
captive fasteners to secure it.
OPS 00059
Captive Fasteners
Figure 6-9 Fan Tray Holder Front Cover
Note: The front cover closes very easily when the fan tray card and air
filter are correctly in position. If the cover does not close easily, check the
fan tray card to make sure it is recessed from the front of the fan tray
holder.
5
The Install a Fan Tray Air Filter with Handle (Legacy) procedure is
complete.
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-17
• PDAP-4S GMT Fuse Replacement, page 6-19
• PDAP-4S LED Module Replacement, page 6-20
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.
WARNING! Use extreme caution when working with battery and
battery return supply cables. Remove all metal jewelry when working
with power circuits.
Page 6-10
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
PDAP-2S Circuit Breaker Replacement
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working on the Power Distribution and Alarm
Panel (PDAP-15A). Plug the ESD wrist strap into an ESD jack or other
confirmed source of earth ground.
Table 6-6 Replacing PDAP-15A GMT Fuses
Step
1
Procedure
Remove the GMT fuse by pulling it straight out.1
GMT Fuses
Alarm LEDs
Figure 6-10 PDAP-15A Front View
1
PDAP-2S
Circuit Breaker
Replacement
2
Replace the failed GMT fuse with a new one of equal current rating.
3
The Replacing PDAP-2S GMT Fuses procedure is complete.
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.
The Power Distribution and Alarm Panel (PDAP-2S) contains field replaceable
40 ampere (amp) circuit breakers.1 Each pair of A and B circuit breakers (e.g., A1, B1)
provides redundant circuit protection per shelf. Power will not be lost to the shelf if a
circuit breaker fails.
Use the following procedure to replace a failed circuit breaker.
WARNING! Use extreme caution when working with battery and
battery return supply cables. Remove all metal jewelry when working
with power circuits.
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working on the Power Distribution and Alarm
Panel (PDAP-2S). Plug the ESD wrist strap into the ESD jack provided on
the air ramp or other confirmed source of earth ground.
1
Release OPS4.0.x
Optional PDAP-2S circuit breakers are available up to a 50 amp maximum.
Turin Networks
Page 6-11
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
PDAP-2S GMT Fuse Replacement
Table 6-7 Replacing PDAP-2S Circuit Breakers
Step
PDAP-2S GMT
Fuse
Replacement
Procedure
1
If the toggle switch on the failed circuit breaker is in the On position,
switch it off.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.
The PDAP-2S contains two fuse blocks (A and B) of ten field replaceable GMT fuses.
Each block has a 100 amp maximum load. Each pair of A and B GMT fuses (e.g., A1,
B1) provides redundant power (from 0.25 to 10 amps per fuse) to one of up to ten
pieces of auxiliary equipment.
Use the following procedure to replace a failed GMT fuse.
WARNING! Use extreme caution when working with battery and
battery return supply cables. Remove all metal jewelry when working
with power circuits.
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working on the Power Distribution and Alarm
Panel (PDAP-2S). Plug the ESD wrist strap into the ESD jack provided on
the air ramp or other confirmed source of earth ground.
Page 6-12
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
PDAP-2S GMT Fuse Replacement
Table 6-8 Replacing PDAP-2S GMT Fuses
Step
1
Procedure
Remove the GMT fuse by pulling it straight out.1
Figure 6-11 PDAP-2S GMT Fuses
1
Release OPS4.0.x
2
Replace the failed GMT fuse with a new one of equal current rating.
3
The Replacing PDAP-2S GMT Fuses procedure is complete.
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.
Turin Networks
Page 6-13
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
PDAP-2S LED Module Replacement
PDAP-2S LED
Module
Replacement
The Power Distribution and Alarm Panel (PDAP-2S) system alarm LEDs (Critical,
Major, Minor), power input A and B LEDs, and GMT A and B fuse block failure LEDs
are on one field replaceable module.
Use the following procedure to replace the PDAP-2S LED module.
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working on the PDAP-2S. Plug the ESD wrist strap
into the ESD jack provided on the air ramp or other confirmed source of
earth ground.
Table 6-9 Replacing PDAP-2S LED Module
Step
Procedure
1
Loosen the two captive fasteners on the PDAP-2S front cover to release it.
Captive Fasteners
Figure 6-12 PDAP-2S Assembly - Remove Front Cover
2
Page 6-14
Remove the front cover.
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
PDAP-2S LED Module Replacement
Table 6-9 Replacing PDAP-2S LED Module (continued)
Step
Procedure
3
Locate the nonfunctional module with a white pull tab at the center of the
PDAP-2S.
Figure 6-13 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-14 PDAP-2S LED Module Guides
6
Release OPS4.0.x
Replace the front cover.
Turin Networks
Page 6-15
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
PDAP-2S LED Module Replacement
Table 6-9 Replacing PDAP-2S LED Module (continued)
Page 6-16
Step
Procedure
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
PDAP-4S TPA Fuse Replacement
PDAP-4S TPA
Fuse
Replacement
The Power Distribution and Alarm Panel (PDAP-4S) contains field replaceable 40 amp
TPA fuses.2 Each pair of A and B TPA fuses (e.g., A1, B1) provides redundant
protection per shelf. Power will not be lost to the shelf if a TPA fuse fails.
Use the following procedure to replace a failed TPA fuse.
WARNING! Use extreme caution when working with battery and
battery return supply cables. Remove all metal jewelry when working
with power circuits.
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working on the Power Distribution and Alarm
Panel (PDAP-4S). Plug the ESD wrist strap into the ESD jack provided on
the air ramp or other confirmed source of earth ground.
2
Release OPS4.0.x
Optional PDAP-4S TPA fuses are available up to a 50 amp maximum.
Turin Networks
Page 6-17
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
PDAP-4S TPA Fuse Replacement
Table 6-10 Replacing PDAP-4S TPA Fuses
Step
Procedure
1
If a TPA fuse LED is RED, replace the fuse embedded in the TPA holder.
Figure 6-15 PDAP-4S TPA Fuses
2
Remove the TPA fuse holder by pulling it straight out.1
Figure 6-16 PDAP-4S TPA Fuse and Holder
1
Page 6-18
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.
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
PDAP-4S GMT Fuse Replacement
PDAP-4S GMT
Fuse
Replacement
The PDAP-4S contains two fuse blocks (A and B) of five field replaceable GMT fuses.
Each block has a 65 amp maximum load. Each pair of A and B GMT fuses (e.g., A1,
B1) provides redundant power (from 0.25 to 15 amps per fuse) to one of up to five
pieces of auxiliary equipment.
Use the following procedure to replace a failed GMT fuse.
WARNING! Use extreme caution when working with battery and
battery return supply cables. Remove all metal jewelry when working
with power circuits.
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working on the Power Distribution and Alarm
Panel (PDAP-4S). Plug the ESD wrist strap into the ESD jack provided on
the air ramp or other confirmed source of earth ground.
Table 6-11 Replacing PDAP-4S GMT Fuses
Step
1
Procedure
Remove the GMT fuse by pulling it straight out.1
Figure 6-17 PDAP-4S GMT Fuses
1
Release OPS4.0.x
2
Replace the failed GMT fuse with a new one of equal current rating.
3
The Replacing PDAP-4S GMT Fuses procedure is complete.
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.
Turin Networks
Page 6-19
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
PDAP-4S LED Module Replacement
PDAP-4S LED
Module
Replacement
The Power Distribution and Alarm Panel (PDAP-4S) system alarm LEDs (Critical,
Major, Minor), power input A and B LEDs, and TPA/GMT fuse block failure LED (for
both A and B) are on one field replaceable module.
Use the following procedure to replace the PDAP-4S LED module.
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working on the PDAP-4S. Plug the ESD wrist strap
into the ESD jack provided on the air ramp or other confirmed source of
earth ground.
Table 6-12 Replacing PDAP-4S LED Module
Step
1
Procedure
Loosen the two PDAP-4S LED faceplate captive fasteners to release it.
Figure 6-18 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.
Page 6-20
4
Tighten the two captive fasteners on the faceplate to secure it.
5
The Replacing PDAP-4S LED Module procedure is complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Routine Maintenance
Environmental Alarm Module Replacement (Traverse only)
Environmental
Alarm Module
Replacement
(Traverse only)
The Environmental Alarm Module (EAM) located on the Traverse main back plane
supports the environmental telemetry inputs and outputs. The EAM is an optional, field
replaceable module required to support environmental alarm input/output functionality.
Environmental signals are accessed through wire-wrap posts located on the main
backplane, allowing the EAM to be replaced without disconnecting alarm wiring.
Use the following procedure to replace the EAM on the Traverse backplane.
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when working with the EAM and the main backplane.
Plug the ESD wrist strap into the ESD jack provided on the air ramp or
other confirmed source of earth ground.
Table 6-13 Replacing EAM
Step
Procedure
1
Locate and remove the nonfunctional module by simultaneously holding
the module along the long edges toward the top of the module and pressing
the plastic standoff tab to pull out the module.
Important: The module should remove fairly easily from the main
backplane connector once the plastic standoff tab is depressed. Do not
force it out of position. If the module does not remove easily, check the
pressure on the plastic standoff tab to be sure it is fully depressed. You may
need to pivot the plastic standoff (by hand) to align the tab into a more
convenient, accessible position.
Figure 6-19 EAM Location - Traverse 1600 Main Backplane
2
Release OPS4.0.x
Prepare to insert the new EAM by holding the module upright along the
long edges with the pins facing toward the main backplane.
Turin Networks
Page 6-21
Node Operations and Maintenance Guide, Section 6: Routine Maintenance
Non-Field Replaceable Fuses
Table 6-13 Replacing EAM (continued)
Step
3
Procedure
Insert the module into the main backplane EAM connector using the
plastic standoff and proper alignment guides. The plastic standoff tab
clicks into place when the module is properly seated.
Important: The module should insert easily into the main backplane
connector. Do not force it into position. If the module does not insert
easily, pull it back out and verify you are placing it in the correct position
and inserting it along the plastic standoff and proper alignment guides.
Long edge
Proper Alignment
Guide
Pins facing
Main Backplane
Plastic Standoff Guide
Figure 6-20 EAM Alignment
4
Non-Field
Replaceable
Fuses
The Replacing EAM procedure is complete.
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 the
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.
Page 6-22
Turin Networks
Release OPS4.0.x
S ECTION 5ROUTINE MAINTENANCE
Chapter 2
Node 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 5-23
• Guidelines for Node Database Backups, page 5-23
• Node Database Restore Guidelines, page 5-24
• Backup and Restore Commands, page 5-24
• Troubleshooting Backup and Restore, page 5-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
Release OPS4.0.x
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.
Turin Networks
Page 5-23
Node Operations and Maintenance Guide, Section 5: Routine Maintenance
Node Database Restore Guidelines
–
•
•
If an FTP host IP address is not provided, the username, password, and path
parameters are not required. The default for the path parameter is nodeDB.*.
The filename is optional. If a file name is not entered, the system uses the default
nodeDB.xxx.
If services are provisioned during the backup, some services may not be captured
during the backup and will, therefore, be lost when the database is restored.
Turin recommends backing up the node database during a maintenance period,
especially if optical cards exist on the shelf.
Node Database
Restore
Guidelines
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:
Table 5-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 2—Overview and
Quick Reference, Chapter 1—“CLI Overview,” page 2-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.
Use the following CLI commands to backup and restore the node database.
exec node database backup. Use the exec node database backup
command to back up the Traverse node database.
Page 5-24
Turin Networks
Release OPS4.0.x
Chapter 2
Node Database Backup and Restore
Backup and Restore Commands
Syntax
exec node database backup [host ip address user-name
UserName password password [path blank][filename
nodeDB.xxx]]
Syntax Description
ip address
- IP address of the FTP server where
the database will be backed up
user-name
- username to use when accessing the
FTP server
password
- password to use when accessing the
FTP server
path
- enter the path on the FTP site
where the database will be backed up
filename
- enter the file name to call the
database file
l
exec node database restore. Use the exec node database restore
command to restore the Traverse node database.
Syntax
exec node database restore [host ip address user-name
UserName password password [path blank][filename
nodeDB.xxx]]
Syntax Description
Release OPS4.0.x
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
Turin Networks
Page 5-25
Node Operations and Maintenance Guide, Section 5: Routine Maintenance
Troubleshooting Backup and Restore
Troubleshooting
Backup and
Restore
If problems occur when restoring the backup, it may be due to one of the following
reasons (in the following table):
Backups will fail if:
• An incorrect FTP server IP address is entered. Verify the FTP server IP address is
correct.
• The directories are not provided or are incorrect in the path parameter of the CLI
command. Verify the name of the directory is provided and is correct.
• A filename already exists with the same name as the backup file. Change the name
of the file being backed up.
Restorations will fail if:
• The node database backup file is corrupt.
• The Node IP address in the node database backup file is different than the system’s
commissioned values.
• The Node ID in the node database backup file is different than the system’s
commissioned values.
Note: Do not restore a database file backed up from a different node.
Newly provisioned services do not appear:
• If the service was provisioned while the backup was in progress, the data may not
have been captured. Re-provision the service.
Page 5-26
Turin Networks
Release OPS4.0.x
S ECTION 7
S OFTWARE U PGRADES
S ECTION 7
Contents
Chapter 1
Release TR3.0.x Traverse Software Upgrade
Release TR3.0.x Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Node Software Upgrade Flowchart (Top Level) . . . . . . . . . . . . . . . . . . . . . . . 7-2
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Traverse Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
TransNav Management System GUI Commands and Conventions . . . . . . . . 7-4
Compatibility and Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
General Software Compatibility Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Traverse System SW Upgrade Compatibility Notes . . . . . . . . . . . . . . . . . . . . 7-5
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Software Upgrade for TR3.0.x Maintenance Releases . . . . . . . . . . . . . . 7-6
Software Upgrade from Release 2.0.x.x or TR2.1.x to TR3.0.x . . . . . . . 7-6
Software Upgrade from 1.5E to TR2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Software Upgrade from 1.5 to TR2.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Guidelines for Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Pre-Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-10
Download Node Software to the TransNav Server— PC System. . . . . . . . . . 7-10
Download Node Software to the TransNav Server— Solaris System. . . . . . . 7-12
Module Software Download Set-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Card Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
BLSR/MS-SP Ring on GCM with Optics Software Activation . . . . . . . . . . . . . 7-22
Control Module Software Upgrade Activation . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Software Upgrade Activate (all other protected modules). . . . . . . . . . . . . . . . 7-31
Software Upgrade Activate (all unprotected modules) . . . . . . . . . . . . . . . . . . 7-34
Spare Control Module Software Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Spare Module Software Activation (All Other Types) . . . . . . . . . . . . . . . . . . . 7-37
Post-Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Verify Protection Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Perform a Forced Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Perform a Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Clear Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Software Revert Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Release OPS4.0.x
Turin Networks
Page i
Node Operations and Maintenance Guide, Section 7 Software Upgrades
Revert TransNav Management System Software . . . . . . . . . . . . . . . . . . 7-46
Post-Remote Node— Upgrade the Spare Control Module Software. . . . . . . . 7-46
User- selectable FPGA Upgrade Capability . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Chapter 2
Release 3.0.x TE-100 System Software Upgrade
Release 3.0.x Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
Required Equipment and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
TE-100 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
TransNav Management System GUI Commands and Conventions . . . . . . . . 7-51
Compatibility and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
General Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
TE-100 Platform SW Upgrade Compatibility Notes . . . . . . . . . . . . . . . . . . . . . 7-52
Guidelines for Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-53
Download Node Software to the TransNav Server— PC System . . . . . . . . . . 7-54
Download Node Software to the TransNav Server— Solaris System . . . . . . . 7-56
Module Software Download Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
Card Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
Control Module Software Upgrade Activation . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Spare Control Module Software Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
Software Revert Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
Revert TransNav Management System Software . . . . . . . . . . . . . . . . . . 7-71
List of Figures
Figure 7-1
Figure 7-2
Figure 7-3
Figure 7-4
Figure 7-5
Figure 7-6
Figure 7-7
Figure 7-8
Figure 7-9
Figure 7-10
Figure 7-11
Figure 7-12
Figure 7-13
Figure 7-14
Figure 7-15
Figure 7-16
Figure 7-17
Page ii
Node Software Upgrade Process Flowchart . . . . . . . . . . . . . . . . . 7-2
Example—PC System Explorer Window File Listing . . . . . . . . . . 7-10
Explorer “Extract to” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Extract Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Example—File Extraction Comments . . . . . . . . . . . . . . . . . . . . . . 7-12
SW Upgrade Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Download Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
SW Upgrade Download Times . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
SW Upgrade—Clear Download Time . . . . . . . . . . . . . . . . . . . . . . 7-17
Dnld Status and Standby SW Version Fields . . . . . . . . . . . . . . . . 7-18
Card Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Card Configuration GCM Protection Status. . . . . . . . . . . . . . . . . . 7-22
SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-24
Card Configuration Protection Status . . . . . . . . . . . . . . . . . . . . . . 7-27
SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-28
Turin Networks
Release OPS4.0.x
Node Operations and Maintenance Guide,
Section 7 Software Upgrades
Figure 7-18
Figure 7-19
Figure 7-20
Figure 7-21
Figure 7-22
Figure 7-23
Figure 7-24
Figure 7-25
Figure 7-26
Figure 7-27
Figure 7-28
Figure 7-29
Figure 7-30
Figure 7-31
Figure 7-32
Figure 7-33
Figure 7-34
Figure 7-35
Figure 7-36
Figure 7-37
Figure 7-38
Figure 7-39
Figure 7-40
Figure 7-41
Figure 7-42
Figure 7-43
Figure 7-44
Figure 7-45
Figure 7-46
Figure 7-47
SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-32
SW Activation—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-35
Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Equipment Protection Group Configuration Dialog Box . . . . . . . . 7-38
Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Protection Group—Forced Switch. . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Confirm Force Switch Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Protection Group—Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Confirm Manual Switch Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . 7-42
Protection Groups Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Protection Group—Clear Protection Switch . . . . . . . . . . . . . . . . . 7-43
Confirm Release Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
User-selectable FPGA Upgrade Parameter . . . . . . . . . . . . . . . . . 7-48
Example—PC System Explorer Window File Listing . . . . . . . . . . 7-54
Explorer “Extract to” Command. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
Extract Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
Example—File Extraction Comments. . . . . . . . . . . . . . . . . . . . . . 7-56
SW Upgrade Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
Download Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59
SW Upgrade Download Times . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
SW Upgrade—Clear Download Time. . . . . . . . . . . . . . . . . . . . . . 7-61
Dnld Status and Standby SW Version Fields . . . . . . . . . . . . . . . . 7-62
Card Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
Card Configuration Protection Status . . . . . . . . . . . . . . . . . . . . . . 7-65
SW Upgrade—Activate Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Act Status and Current SW Ver Fields . . . . . . . . . . . . . . . . . . . . . 7-67
Table 7-1
Table 7-2
Table 7-3
Table 7-4
Table 7-5
Table 7-6
Table 7-7
Table 7-8
Table 7-9
Table 7-10
Table 7-11
Table 7-12
Node Software Upgrade Requirements . . . . . . . . . . . . . . . . . . . . 7-3
TransNav GUI Command Descriptions. . . . . . . . . . . . . . . . . . . . . 7-4
Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Pre-Software Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Download Node Software to the TransNav Server—PC System . 7-10
Download Node Software to the TransNav Server—Solaris System7-12
Card Software Download Set-up. . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Card Software Version Number Verification . . . . . . . . . . . . . . . . . 7-19
Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Activate Software—BLSR/MS-SP Ring GCM with Optic Modules 7-22
Activate Software—Control Module . . . . . . . . . . . . . . . . . . . . . . . 7-26
Activate Software —All Other Protected Modules. . . . . . . . . . . . . 7-31
List of Tables
Release OPS4.0.x
Turin Networks
Page iii
Node Operations and Maintenance Guide, Section 7 Software Upgrades
Table 7-13
Table 7-14
Table 7-15
Table 7-16
Table 7-17
Table 7-18
Table 7-19
Table 7-20
Table 7-21
Table 7-22
Table 7-23
Table 7-24
Table 7-25
Table 7-26
Table 7-27
Table 7-28
Table 7-29
Table 7-30
Table 7-31
Table 7-32
Table 7-33
Table 7-34
Table 7-35
Table 7-36
Table 7-37
Page iv
Activate Software —All Unprotected Modules . . . . . . . . . . . . . . . . 7-34
Activate Software—Spare Control Modules . . . . . . . . . . . . . . . . . 7-36
Activate Software—Spare Modules (All Other Types) . . . . . . . . . 7-37
Post-Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Verify Protection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Perform a Forced Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Perform a Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Clear Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Deactivate Legacy Ethernet Services . . . . . . . . . . . . . . . . . . . . . . 7-44
Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Revert TransNav Management System Software . . . . . . . . . . . . . 7-46
Post-Remote Node Upgrade —Upgrade the Spare Control Module7-47
Node Software Upgrade Requirements. . . . . . . . . . . . . . . . . . . . . 7-50
TransNav GUI Command Descriptions . . . . . . . . . . . . . . . . . . . . . 7-51
Turin Product and Software Release Compatibility . . . . . . . . . . . . 7-52
Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Download Node Software to the TransNav Server—PC System . 7-54
Download Node Software to the TransNav Server—Solaris System7-56
Card Software Download Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
Card Software Version Number Verification . . . . . . . . . . . . . . . . . 7-63
Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Activate Software— Control Module . . . . . . . . . . . . . . . . . . . . . . . 7-65
Activate Software—Spare Control Modules . . . . . . . . . . . . . . . . . 7-69
Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
Revert TransNav Management System Software . . . . . . . . . . . . . 7-71
Turin Networks
Release OPS4.0.x
S ECTION 7SOFTWARE UPGRADES
Chapter 1
Release TR3.0.x Traverse Software Upgrade
Introduction
Complete the TR3.0.x software upgrade of all modules in a Traverse node using the
release TR3.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 TR3.0.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-45
• Post-Remote Node— Upgrade the Spare Control Module Software, page 7-46
• User- selectable FPGA Upgrade Capability, page 7-48
Release
TR3.0.x
Upgrade
Overview
Release TR3.0.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 TR3.0.x from the following previous
releases: 2.0.x and TR2.1.
Note: If your systems are on an earlier release (pre-1.5.x), contact the Turin Technical
Assistance Center (TAC).
• Point releases (as necessary) for the TR3.0.x Traverse nodes
• Remote upgrade capability
• User-selectable FPGA (Field Programmable Gate Array) upgrade capability
• Simultaneous TransNav Management System (TN4.0.x) software management of
Release 2.0.x and TR2.1.x Traverse and 3.0.x TE-100 nodes to accommodate
longer-term upgrade paths
Release OPS4.0.x
Turin Networks
Page 7-1
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Node Software Upgrade Flowchart (Top Level)
Node Software
Upgrade
Flowchart (Top
Level)
The diagram below shows a top-level flow for the node software upgrade process.
Node Software Upgrade to Release TR2.1.x
Top-Level Flowchart
{IMPORTANT! For details, refer to the specific software upgrade procedures in the manual}
Begin
Read release
nodes, upgrade
compatibility
notes, guidelines,
and all upgrade
procedures
Operations Manager
Operations
Manager
creates a
comprehensive
upgrade plan
Read and understand the
release notes, upgrade
compatibility notes,
guidelines, upgrade
procedures, and your
company's comprehensive
upgrade plan
Upgrade Team
Point release
upgrade?
YES
NO
1.5[E].x, R2.0 to
TR2.1 major
release
upgrade?
YES
Follow the
Node
Upgrade
Process
Go to
Page 2
NO
pre-1.5[E].x
release upgrade?
YES
Contact
Technical
Assistance
Center (TAC)
End
OPS 00071
Figure 7-1 Node Software Upgrade Process Flowchart
Page 7-2
Turin Networks
Release OPS4.0.x
Chapter 1
Before You
Begin
Release TR3.0.x Traverse Software Upgrade
Required Equipment and Tools
Review this information before you begin.
Table 7-1 Node Software Upgrade Requirements
Requirement
Required
Equipment and
Tools
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 TR3.0.x (805-0108-TR30)
• Read through this entire chapter
• Contact your company’s Operations Manager
The software upgrade feature for
this release supports Traverse and
TransNav 2.0.x or TR2.1.x to
TR3.0.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
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 cards 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
•
Release OPS4.0.x
MPX cleaning materials to clean fiber optic cable and card MPX connectors:
– Isopropyl alcohol of at least 91% purity
– Lint free wipes
– Lint free cleaning swabs with urethane foam heads
Turin Networks
Page 7-3
Node Operations and Maintenance Guide, Section 7: Software Upgrades
TransNav Management System GUI Commands and Conventions
•
•
– Pressurized optical duster (canned air)
1 or 2 control cards, as well as any spares
System interface module (SIM) cards
Note: The number and combination of SIMs is based on your network
requirements and physical cabling at the Traverse main and fiber optic backplanes.
TransNav
Management
System GUI
Commands
and
Conventions
This document provides node software upgrade procedures using the TransNav GUI.
Refer to the TransNav Management System Product Overview Guide to become
familiar with the TransNav system.
The following conventions are used in the procedure tables.
Table 7-2 TransNav GUI Command Descriptions
Command
Description
Boldface
Boldface indicates dialog box, field, menu, and list names
Italics
Italics indicates information you supply
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 Cards. Each control card is partitioned and capable of holding two versions
of software. The new software is downloaded onto the card’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 card and activates
the back-up partition with the newly downloaded software. Provisioning data stored on
the node control card 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 cards. 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 card with a (major.x.x.x) software version lower than the
compatibility ID of the Active control card—the lowest software version the
Active control card can work with—is placed in the node.
• the Active control card (major.x.x.x) software version is lower than the
compatibility ID of the replacement card.
Page 7-4
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Traverse System SW Upgrade Compatibility Notes
•
the Active control card 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 card.
A SWMIS: Software version mismatch alarm is generated when a replacement
card with either an earlier or later (major.minor.build.x) version of software than the
software running on the control card is placed in the node. In this case, use the
procedures in this section to upgrade or rollback the software version on the
replacement card.
Traverse
System SW
Upgrade
Compatibility
Notes
Review this information to understand the important compatibility items for Traverse
and TransNav software releases.
General
•
•
•
•
Release TN4.0.x TransNav management system software:
– simultaneously manages Release 2.0.x , TR2.1.x and TR3.0.x Traverse nodes.
– manages the in-service software upgrade from Release 2.0 and TR2.1.x to
TR3.0.x, as well as, any TR3.0.x maintenance releases.
– manages a network of mixed nodes running Release 2.0.x, TR2.1.x, and
TR3.0.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 TR3.0.x release.
For TR2.1 and subsequent releases, 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 the
Traverse Provisioning Guide, Section 7—Configuring Ethernet,
Chapter 9—“Interworking Ethernet Services with Legacy Ethernet Services,”
page 7-109.
Important: If a replacement (or spare) module with Release 1.5 is inserted into a
Traverse node with a software version higher than Release 1.5, the software disables
the warm restart capability on all modules.
Release OPS4.0.x
Turin Networks
Page 7-5
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Traverse System SW Upgrade Compatibility Notes
Software Upgrade for TR3.0.x 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 TR3.0.x and
future maintenance releases.
Software Upgrade from Release 2.0.x.x or TR2.1.x to TR3.0.x
•
•
Support for in-service software upgrade from Release 2.0.x.x or TR2.1.x to
TR3.0.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 TR3.0.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 TR3.0.x.
Important: See the Upgrade and Installation Notes topic in the Turin Release
Notes TR3.0.x (805-0008-TR30) 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
•
•
Page 7-6
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.
Turin Networks
Release OPS4.0.x
Chapter 1
Release TR3.0.x Traverse Software Upgrade
Node 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-46 for details).
– In either case, always upgrade (download and activate) both the standby and
active GCM cards before upgrading any spare GCM cards.
• Software upgrade is to be errorless. Release Notes TR3.0.x (805-0108-TR30)
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 2.0.x,
TR2.1.x to TR3.0.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
Release OPS4.0.x
Step
Procedure
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?
Required Equipment and Tools, page 7-3
Turin Networks
Reference
Page 7-7
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Node Software Upgrade Process
Table 7-3 Node Software Upgrade Process (continued)
Step
Procedure
3
Are you upgrading from Release 1.5
or 1.5E to TR2.1 first, and do you
plan in this upgrade process to also
upgrade Legacy Ethernet services to
the next-generation Ethernet service
model?
Reference
Pre-Software Upgrade Procedure, page 7-9
Note: The Legacy Ethernet to
Ethernet model upgrade requires pre
and post steps be run to
accommodate the new service
model.
4
Upgrade the TransNav Management
System server software (includes
first exporting the current database
off the TransNav server).
TransNav Management System Server Guide,
Section 2—Management Server Procedures,
Chapter 3—“Server Administration Procedures,”
Upgrade Server Software, page 2-38
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.
Page 7-8
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 cards.
Module Software Download Set-up, page 7-13
7
Activate the new software.
Software Activation Process, page 7-19
8
Are you upgrading from Release 1.5
or 1.5E to TR2.1 first, 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-37
9
The Node Software Upgrade Process is complete.
Turin Networks
Release OPS4.0.x
Chapter 1
Pre-Software
Upgrade
Procedure
Release TR3.0.x Traverse Software Upgrade
Pre-Software Upgrade Procedure
Complete the following procedure before you begin the software upgrade.
Table 7-4 Pre-Software Upgrade Procedure
Step
1
Procedure
Are you upgrading a Traverse node from Release 1.5 or 1.5E to TR2.1
first, 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-44.
– Delete the corresponding Legacy Ethernet services.
•
2
Note: Service recreation occurs after the software upgrade is
complete. See Table 7-16 Post-Software Upgrade Procedure,
page 7-37.
– Go to the next step.
No. Go to the next step.
Are you upgrading Traverse node from Release 1.5.x or 1.5E.x to TR2.1
first, 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 end-to-end (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
Release OPS4.0.x
The Pre-Software Upgrade Procedure procedure is complete. Continue to
Step 4 of the Node Software Upgrade Process, page 7-7.
Turin Networks
Page 7-9
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Download 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-12
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
Page 7-10
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Download Node Software to the TransNav Server— PC System
Table 7-5 Download Node Software to the TransNav Server—PC System
Step
4
Procedure
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.
Figure 7-4 Extract Dialog Box
Release OPS4.0.x
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 6Step 5 of the Node Software
Upgrade Process, page 7-7.
Turin Networks
Page 7-11
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Download 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.
Table 7-6 Download Node Software to the TransNav Server—Solaris System
Step
1
Procedure
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
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 cards. To
change permissions, contact your local UNIX administrator.
Figure 7-5 Example—File Extraction Comments
4
Eject the CD from the drive.
For example:
$ eject
5
Page 7-12
The Download Node Software to the TransNav Server—Solaris System
procedure is complete. Continue to Step 6Step 5 of the Node Software
Upgrade Process, page 7-7.
Turin Networks
Release OPS4.0.x
Chapter 1
Module
Software
Download
Set-up
Release TR3.0.x Traverse Software Upgrade
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 card using the SW Upgrade dialog box.
Table 7-7 Card Software Download Set-up
Step
Procedure
1
Verify the card software versions. Refer to Card Software Version
Verification, page 7-19.
2
In Shelf View, select SW Upgrade from the Admin menu to display the
SW Upgrade dialog box.
Figure 7-6 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)
Release OPS4.0.x
Turin Networks
Page 7-13
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Module Software Download Set-up
Table 7-7 Card Software Download Set-up (continued)
Step
6
Procedure
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 Update and verify that there were no errors in the ftp session.
Note: This action should fill in the data for each card in the Relative
Path columns.
Important: The Relative Path and Upgrade Type (default is INIT)
values must be set by the system before the download starts.
Page 7-14
Turin Networks
Release OPS4.0.x
Chapter 1
Release TR3.0.x Traverse Software Upgrade
Module Software Download Set-up
Table 7-7 Card Software Download Set-up (continued)
Step
8
Procedure
Set each Download Time based on these requirements for each card.
Approximate software download times are as follows:
• Control card download time is approximately 10 to 20 minutes
• Download time for all other cards is approximately 2 to 5 minutes
Note: Turin recommends you set sequential download times based on the
card requirements.
Note: Due to the use of ftp libraries, bulk software downloads may fail so
schedule software downloads at least 5 minutes apart.
Note: It takes a fully loaded Traverse-specific node approximately one
hour to download the new software onto all cards. 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 cards and services. It does not require
you to stand by during the download.
Note: Turin recommends you download the control cards individually,
three line cards at a time and one node at a time,
7
7
Figure 7-7 Download Time Settings
Release OPS4.0.x
Turin Networks
Page 7-15
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Module Software Download Set-up
Table 7-7 Card Software Download Set-up (continued)
Step
Procedure
9
From the Download Time drop-down box, select Set time to manually
adjust the time. Select part of the time string (e.g., month, day, hour). Use
the up and down arrows or manually re-enter the time to reset the value.
8
Figure 7-8 SW Upgrade Download Times
10
Verify the Relative Path is set for each card.
Relative Path: A literal sub-directory path (in relation to the Base Path
directory) where the software resides for each card. It is based on the type
of card in the slot and is case sensitive. For example: ds3.
11
Verify the Upgrade Type is set to the default (INIT) for each card.
Upgrade Type (default=INIT): The upgrade type for each card 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 available for special cases only when working
with TAC.
12
Page 7-16
Repeat Steps 7 through 11 for each card in the node.
Turin Networks
Release OPS4.0.x
Chapter 1
Release TR3.0.x Traverse Software Upgrade
Module Software Download Set-up
Table 7-7 Card Software Download Set-up (continued)
Step
Procedure
13
You can Clear Download Time for any card by right-clicking the card in
the SW Upgrade dialog box and clicking the Update button. If necessary,
you can Abort Download to any card by right-clicking the card in the SW
Upgrade dialog box.
Note: Turin recommends that you do not leave the card in the upgrade
abort state. Clear the download time and click the Update button to clear
the abort state.
12
12
Figure 7-9 SW Upgrade—Clear Download Time
14
Verify 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 Turin’s TAC if the software download fails a
second time.
Release OPS4.0.x
Turin Networks
Page 7-17
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Module Software Download Set-up
Table 7-7 Card Software Download Set-up (continued)
Step
Procedure
16
Continue only when the Download Status is OK and the newly
downloaded software version displays in Standby SW Version field for
all cards (select each card row and check the Standby SW Version field).
This indicates the software download has successfully completed.
15a
15b
15a
15b
Figure 7-10 Dnld Status and Standby SW Version Fields
17
The Card 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-37
Return to Step 6 of the Node Software Upgrade Process, page 7-7.
Page 7-18
Turin Networks
Release OPS4.0.x
Chapter 1
Card Software
Version
Verification
Release TR3.0.x Traverse Software Upgrade
Software Activation Process
You can determine the software version number of a card (card) using the TransNav
GUI. The software version and serial number are displayed on the Config tab in Shelf
View. Follow these steps to verify the software version.
Table 7-8 Card Software Version Number Verification
Step
Procedure
1
In Shelf View, click a card to select it.
2
Click the Config tab to view current software version information.
2
Figure 7-11 Card Configuration Dialog Box
Software
Activation
Process
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 Card Software Version Number Verification procedure is complete.
The new software is not active until the software is activated and system reboots each
module. The reboot loads and executes the new software, and in the case of the control
module, upgrades the database.
Important: Read all important notes below before beginning the
activation process.
Important: Software activation should start at the node farthest from the
server that is connected to the head-end node, then work inward.
Release OPS4.0.x
Turin Networks
Page 7-19
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Software 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).
(Issue 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 step on
each span in the BLSR/MS-SP Ring network.
Table 7-9 Software Activation Process
Page 7-20
Step
Procedure
Reference
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?
Download Node Software to the TransNav Server,
page 7-10
4
Is the module software download
complete?
Module Software Download Set-up, page 7-13
Turin Networks
Release OPS4.0.x
Chapter 1
Release TR3.0.x Traverse Software Upgrade
Software Activation Process
Table 7-9 Software Activation Process (continued)
Step
Procedure
5
Do you have your network nodes in
a BLSR/MS-SP Ring network with
Traverse Enhanced GCMs with
Optics?
Important: For any upgrade to
TR2.1.x from 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).
6
Activate software for:
• Standby GCM
• Active 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-46)
Reference
• 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-22
• Continue to Step 7 of this process to software
upgrade activate all other protected modules.
Control Module Software Upgrade Activation,
page 7-26
Important: For any upgrade to
TR2.1.x from 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).
7
Activate software for all modules
set up in a protection group.
Software Upgrade Activate (all other protected
modules), page 7-31
8
Activate software for all
unprotected modules.
Software Upgrade Activate (all unprotected
modules), page 7-34
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-37
10
Release OPS4.0.x
The Software Activation Process is complete. Continue to Step 8 of the Node Software
Upgrade Process, page 7-7.
Turin Networks
Page 7-21
Node Operations and Maintenance Guide, Section 7: Software Upgrades
BLSR/MS-SP Ring on GCM with Optics Software Activation
BLSR/MS-SP
Ring on GCM
with Optics
Software
Activation
The new software is not active until the software is activated and system reboots each
module. The reboot loads and executes the new software, and in the case of the control
module, upgrades the database.
Important: The following procedure applies to Traverse nodes only.
Important: Do not start the Activate Software—BLSR/MS-SP Ring
GCM with Optic Modules procedure until the downloaded software
version displays indicating that the software download has successfully
completed. The software version displays in the SW Activation dialog
box, Standby SW Ver field for all modules.
The activation is scheduled for each module based on the date and time entered in the
Activate Time field of the SW Activation dialog box. Follow these step-by-step
instructions to set up software upgrade activation for GCMs with Optics in a
BLSR/MS-SP Ring.
Table 7-10 Activate Software—BLSR/MS-SP Ring GCM with Optic Modules
Step
Procedure
1
Verify the network is alarm free or validate and record any alarms present
prior to activation.
2
In Shelf View, select a GCM with Optics module and click the Config
tab.
3
Verify Active/Standby GCM with Optics Protection Status using the
Card Configuration dialog box.
3
Figure 7-12 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-39.
Check the BLSR/MS-SP Ring state and verify that Force is issued on the
near- and far-end.
Page 7-22
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
BLSR/MS-SP Ring on GCM with Optics Software Activation
Table 7-10 Activate Software—BLSR/MS-SP Ring GCM with Optic Modules
Step
5
Procedure
Click the standby GCM with Optics Activate Time field in the SW
Upgrade dialog box; the current date and time displays. Use the Activate
Time up and down arrows to reset the date and time or select the date,
time, hour, or minute fields and then re-enter.
6
Figure 7-13 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
TR3.0.x table in the Release Notes TR3.0.0 (805-0108-TR30).
8
Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-48 for details about this
parameter.
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 recommends that (by default) you accept all FPGA upgrades so as
not to create an upgrade deviation in your network.
9
Release OPS4.0.x
Click Update.
Turin Networks
Page 7-23
Node Operations and Maintenance Guide, Section 7: Software Upgrades
BLSR/MS-SP Ring on GCM with Optics Software Activation
Table 7-10 Activate Software—BLSR/MS-SP Ring GCM with Optic Modules
Step
Procedure
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.
10
11
Figure 7-14 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. 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
Clear the near-end Forced Switch using the procedure in Table 7-20 Clear
Protection Switch, page 7-42.
Verify that the BLSR/MS-SP Ring has returned to normal operation. If not,
initialize the BLSR/MS-SP Ring.
15
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-39.
Check the BLSR/MS-SP Ring state and verify that Force is issued on the
near- and far-end.
Page 7-24
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
BLSR/MS-SP Ring on GCM with Optics Software Activation
Table 7-10 Activate Software—BLSR/MS-SP Ring GCM with Optic Modules
Step
Procedure
16
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.
17
Select the activation type—Act Type (default=NSA). Service Affecting
(SA) is required for standby GCM with Optics module activation.
Valid values are:
• NSA (non-service-affecting): Default. Will not reboot (activate) an
active node GCM.
• SA (service-affecting): Will activate and reboot the node GCM
regardless of its active or standby status.
• SPARE (non-service-affecting): Will activate and reboot the spare
(standby) control module. Only use this option in the instance where
the standby and active control modules have already been upgraded
and activated.
18
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
TR3.0.x table in the Release Notes TR3.0.x (805-0108-TR30).
19
Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-48 for details about this
parameter.
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 recommends that (by default) you accept all FPGA upgrades so as
not to create an upgrade deviation in your network.
20
Click Update.
21
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.
22
Release OPS4.0.x
With the now standby (previously active) GCM with Optics module
selected in Shelf View, select the Alarms tab and check the Alarms dialog
box. Verify that the EQFAIL: equipment failure alarm caused by the
reboot has cleared.
Turin Networks
Page 7-25
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Control Module Software Upgrade Activation
Table 7-10 Activate Software—BLSR/MS-SP Ring GCM with Optic Modules
Step
Procedure
23
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.
24
Clear the near-end Forced Switch using the procedure in Table 7-20 Clear
Protection Switch, page 7-42.
Verify that the BLSR/MS-SP Ring has returned to normal operation.
Control Module
Software
Upgrade
Activation
25
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-36 procedure.
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-21.
The new software is not active until the system reboots each module. The reboot
activates the backup partition with the newly downloaded software on the control
module at each node.
Important: Do not start the Activate Software—Control Module
procedure until the downloaded software version displays. This indicates
the software download has completed successfully. The software version
displays in the SW Activation dialog box, Standby SW Ver field for all
modules.
The activation is scheduled for each module based on the date and time entered in the
Activate Time field of the SW Activation dialog box. Follow these step-by-step
instructions to set up software upgrade activation for node GCMs.
Table 7-11 Activate Software—Control Module
Page 7-26
Step
Procedure
1
Verify the network is alarm free or validate and record any alarms present
prior to activation.
2
In Shelf View, select a control module and click the Config tab.
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Control Module Software Upgrade Activation
Table 7-11 Activate Software—Control Module (continued)
Step
Procedure
3
Verify the Protection Status of the Active/Standby control module using
the Card Configuration dialog box.
3
Figure 7-15 Card Configuration Protection Status
4
Click the standby control module Activate Time field in the SW
Activation dialog box; the current date and time displays. Use the
Activate Time up and down arrows to reset the date and time or select the
date, time, hour, or minute fields and then re-enter.
4
Figure 7-16 SW Activation—Activate Time
5
Select the activation type Act Type (default=NSA). Change to SA for
standby control module activation.
Valid values are:
• NSA (non-service-affecting): Default. Will not activate an active
control module.
• SA (service-affecting): Will activate and reboot the control module
regardless of its active or standby status.
• SPARE (non-service-affecting): Will activate and reboot the spare
(standby) control module. Use this option only when the standby and
active control modules have already been upgraded and activated.
Release OPS4.0.x
Turin Networks
Page 7-27
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Control Module Software Upgrade Activation
Table 7-11 Activate Software—Control Module (continued)
Step
Procedure
6
If the module does not require a cold restart, then select to warm restart
(Warm Rbt) this module. To learn more about those modules that allow a
warm reboot upgrade, see the Cold Reboot Matrix for Modules on
Upgrade from Previous Releases to Release TR3.0.x table in the Release
Notes TR3.0.x (805-0108-TR30).
7
Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-48 for details about this
parameter.
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 recommends that (by default) you accept all FPGA upgrades so as
not to create an upgrade deviation in your network.
8
Click Update.
9
View the status of the software activation in the Act Status field of the SW
Activation dialog box. The following status displays:
• NONE: Software activation has not begun.
• INPROGRESS: Software activation has begun, but is not complete.
• OK: Software activation has successfully completed.
• FAILED: Software activation has failed. Retry the software activation.
Contact the Turin TAC if the software activation fails a second time.
Important: The activation status will show INPROGRESS and then
NONE until the module has completed the upgrade; then it will show OK.
This is normal behavior.
10
Verify that the new software version activation is complete and it displays
in the SW Activation dialog box, Current SW Ver field.
Important: If there are any unexpected discrepancies here, STOP and
contact the Turin TAC.
9
10
Figure 7-17 Act Status and Current SW Ver Fields
11
Page 7-28
With the standby control module selected in Shelf View, select the Alarms
tab and check the Alarms dialog box. Verify that the EQFAIL:
equipment failure alarm caused by the reboot has cleared.
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Control Module Software Upgrade Activation
Table 7-11 Activate Software—Control Module (continued)
Step
Procedure
12
A SWMIS: Software version mismatch alarm is generated since the
standby control module software version is now mismatched with the
active control module. This is normal behavior.
13
If the control modules contain integrated VTX/VCX modules in a
protection group (e.g., GCM with VTX/VCX), you must perform a
Manual switch on the active module (module with the old software) to
change its state to standby. Refer to the procedure, Perform a Manual
Switch, on page 7-41 for details.
Note: The manual protection switch on certain modules is necessary due
to FPGA changes.
14
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.
15
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-42 for details.
16
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.
17
Act Type (default=NSA). Select SA (service-affecting) activation type for
the active control module.
Valid values are:
• NSA (non-service-affecting): Default. Will not activate an active
control module.
• SA (service-affecting): Will activate and reboot the control module
regardless of its active or standby status.
• SPARE (non-service-affecting): Will activate and reboot the spare
(standby) control module. Use this option only when the standby and
active control modules have already been upgraded and activated.
18
Release OPS4.0.x
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
TR3.0.x table in the Release Notes TR3.0.x (805-0108-TR30).
Turin Networks
Page 7-29
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Control Module Software Upgrade Activation
Table 7-11 Activate Software—Control Module (continued)
Step
19
Procedure
Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-48 for details about this
parameter.
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 recommends that (by default) you accept all FPGA upgrades so as
not to create an upgrade deviation in your network.
20
Click Update.
21
View the status of the software activation in the Act Status field of the SW
Activation dialog box. The following status types display:
• NONE: Software activation has not begun.
• INPROGRESS: Software activation has begun, but is not complete.
• OK: Software activation has successfully completed.
• FAILED: Software activation has failed. Retry the software activation.
Contact the Turin TAC if the software activation fails a second time.
Important: The activation status will show INPROGRESS and then
NONE until the module has completed the upgrade; then it will show OK.
This is normal behavior.
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 control module causes the new software to
upgrade and a switchover to the protection module.
Page 7-30
23
With the now standby (previously active) control module selected in Shelf
View, select the Alarms tab. Check the Alarms dialog box to verify the
EQFAIL: equipment failure alarm caused by the reboot has cleared.
24
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.
25
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-36 procedure.
26
The Activate Software—Control Module procedure is complete. Continue
to Step 7 of the Software Activation Process, page 7-21.
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Software Upgrade Activate (all other protected modules)
Software
Upgrade
Activate (all
other protected
modules)
Follow these step-by-step instructions to set up software upgrade activation for all
other protected modules.
Important: Upgrade the entire protection group first before continuing to
the next protection group.
Table 7-12 Activate Software —All Other Protected Modules
Step
Procedure
1
Proceed with software upgrade activation for other protected modules after
the software activation has successfully completed on both the control
modules (Act Status=OK) and any service-affecting alarms on the node
are cleared.
Software upgrade activation on other protected modules must be
performed in the following order for all modules set up in a protection
group:
• Set the Activate Time so the standby module activates first.
• If a cold reboot activation was used, after the activation (activate
software and reboot) has successfully completed, perform a manual
switch on the active module to change its state to standby.
• Set the Activate Time for the active module.
• Release the protection switch.
2
Verify and record the standby/active status for modules/ports set up in a
protection group. Refer to the Verify Protection Status procedure on
page 7-38 for more details.
3
Click the standby module Activate Time field to display the current date
and time. Use the Activate Time up and down arrows to reset the date and
time or select the date, time, hour, or minute fields and then re-enter.
3
Figure 7-18 SW Activation—Activate Time
4
Set 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.
Release OPS4.0.x
Turin Networks
Page 7-31
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Software Upgrade Activate (all other protected modules)
Table 7-12 Activate Software —All Other Protected Modules (continued)
Step
Procedure
5
If the module does not require a cold restart, then select to warm restart
(Warm Rbt) this module. To learn more about those modules that allow a
warm reboot upgrade, see the Cold Reboot Matrix for Modules on
Upgrade from Previous Releases to Release TR3.0.x table in the Release
Notes TR3.0.x (805-0108-TR30).
6
Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-48 for details about this
parameter.
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 recommends that (by default) you accept all FPGA upgrades so as
not to create an upgrade deviation in your network.
7
Click Update.
8
View the status of the software activation in the Act Status field of the SW
Activation dialog box. The following statuses display:
• NONE: Software activation has not begun.
• INPROGRESS: Software activation has begun, but is not complete.
• OK: Software activation has successfully completed.
• FAILED: Software activation has failed. Retry the software activation.
Contact the Turin TAC if the software activation fails a second time.
9
Verify that the new software version is displayed in SW Activation dialog
box, Current SW Ver field.
8
9
Figure 7-19 Act Status and Current SW Ver Fields
10
Page 7-32
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Software Upgrade Activate (all other protected modules)
Table 7-12 Activate Software —All Other Protected Modules (continued)
Step
Procedure
11
If the modules contain integrated VTX/VCX modules in a protection
group, 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-41 for details.
Note: The manual protection switch on certain modules is necessary due
to FPGA changes.
Release OPS4.0.x
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-42 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-19.
Turin Networks
Page 7-33
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Software Upgrade Activate (all unprotected modules)
Software
Upgrade
Activate (all
unprotected
modules)
Use the following step-by-step instructions to set up software upgrade activation for all
unprotected modules:
Table 7-13 Activate Software —All Unprotected Modules
Step
Procedure
1
Proceed with software upgrade activation on all unprotected modules after
the software activation has successfully completed (Act Status=OK) on
both the control modules and then on all other protected modules before
clearing any service-affecting alarms on the node.
2
Click the unprotected module Activate Time field to display the current
date and time. Use the Activate Time up and down arrows to reset the date
and time or select the date, time, hour, or minute fields and then re-enter.
2
Figure 7-20 SW Activation—Activate Time
3
Select the activation type Act Type and set to SA for the module.
Valid values are:
• NSA (non-service-affecting): Default. Will not activate an active
control module.
• SA (service-affecting): Will activate and reboot the control module
regardless of its active or standby status.
4
If the module does not require a cold restart, select to warm restart (Warm
Rbt) this module. To learn more about the modules that allow a warm
reboot upgrade, see the Cold Reboot Matrix for Modules on Upgrade from
Previous Releases to Release TR3.0.x table in the Release Notes TR3.0.x
(805-0108-TR30).
5
Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-48 for details about this
parameter.
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 recommends that (by default) you accept all FPGA upgrades so as
not to create an upgrade deviation in your network.
Page 7-34
6
Click Update.
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.
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Software Upgrade Activate (all unprotected modules)
Table 7-13 Activate Software —All Unprotected Modules (continued)
Step
8
Procedure
Verify the new software version displays in SW Activation dialog box,
Current SW Ver field.
7
8
Figure 7-21 Act Status and Current SW Ver Fields
9
With the unprotected module selected in Shelf View, check the Alarms
dialog box to verify the following alarms have cleared:
• EQFAIL (equipment failure): Caused by the reboot.
• SWMIS (software mismatch): Caused by a software version mismatch
with the active control module.
10
Repeat Steps 2 through 9 for all unprotected modules.
11
Verify 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-21
• Step 4 of the Spare Module Software Activation (All Other Types),
page 7-37
Release OPS4.0.x
Turin Networks
Page 7-35
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Spare Control Module Software Activation
Spare Control
Module
Software
Activation
The new software is not active until the system activates the software and reboots the
spare (standby) control module. The reboot loads and executes the new software.
Important: This procedure assumes you have completed upgrading
(downloading and activating the new software for) the standby and active
control modules.
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. If the standby TE-100 System module is
an OC-48 module, you can only upgrade with another OC-48 system
module.
The activation is scheduled for each module at the node based on the date and time
entered in the Activate Time field of the SW Activation dialog box. Follow these
step-by-step instructions to set up software upgrade activation for spare control
modules.
Table 7-14 Activate Software—Spare Control Modules
Step
Procedure
1
Remove the upgraded standby control module by restarting the module
through the TransNav management system, then removing the module
from the shelf.
2
Insert the spare (standby) control module.
3
Once the spare control module is online and the EQRMV/EQCOMM alarms
are clear, download the new software version to the module using the
Table 7-7 Card 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-26 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.
• Replace 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 24 of the procedure BLSR/MS-SP Ring on GCM with Optics
Software Activation, page 7-24
• Step 26 of the procedure Control Module Software Upgrade
Activation, page 7-30
Page 7-36
Turin Networks
Release OPS4.0.x
Chapter 1
Spare Module
Software
Activation (All
Other Types)
Release TR3.0.x Traverse Software Upgrade
Post-Software Upgrade Procedure
The new software is not active until the system activates the software and reboots the
spare modules that are not control modules. The reboot loads and executes the new
software.
The activation is scheduled for each module based on the date and time entered in the
Activate Time field of the SW Activation dialog box. Use the following step-by-step
instructions to set up the software upgrade activation for the spare modules.
Table 7-15 Activate Software—Spare Modules (All Other Types)
Post-Software
Upgrade
Procedure
Release OPS4.0.x
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-31 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-21.
Complete the following post-software upgrade procedure.
Table 7-16 Post-Software Upgrade Procedure
Step
Procedure
1
Are you upgrading from Release 1.5 or 1.5E.x to Release TR2.1 first? 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,
Section 7—Configuring Ethernet, Chapter 1—“Configuring
Ethernet Overview,” page 7-1.
– Go to the next step.
• No. Stop. Go to Step 3.
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.
Turin Networks
Page 7-37
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Verify 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:
Table 7-17 Verify Protection Status
Step
Procedure
1
From Map View, double-click on a node to display the Shelf View.
2
Click the Protection tab to display the Protection Groups dialog box.
2
Figure 7-22 Protection Groups Dialog Box
3
Select the protection group.
4
Click Edit to display the Protection Group Configuration dialog box.
5
The status displays in the Protection field - either Active or Standby.
5
Figure 7-23 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-31.
Page 7-38
Turin Networks
Release OPS4.0.x
Chapter 1
Perform a
Forced Switch
Release TR3.0.x Traverse Software Upgrade
Perform a Forced Switch
Use the following step-by-step instructions to perform a user-initiated forced protection
switch.
Table 7-18 Perform a Forced Switch
Step
Procedure
1
In Shelf View, click the Protection tab to display the Protection Groups
dialog box.
1
Figure 7-24 Protection Groups Dialog Box
2
Select the protection group.
3
Click Edit to display the Protection Group Configuration dialog box.
4
Right-click the module or port with an Active Protection status in the
Protection Group Configuration dialog box to display a shortcut menu.
Select Forced from the shortcut menu.
4
Figure 7-25 Protection Group—Forced Switch
5
The Confirm Force Switch dialog box displays. Click Yes to confirm.
Figure 7-26 Confirm Force Switch Dialog Box
Release OPS4.0.x
Turin Networks
Page 7-39
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Perform a Forced Switch
Table 7-18 Perform a Forced Switch (continued)
Step
Procedure
6
Check the Alarms dialog box to verify the EQFAIL: equipment
failure alarm caused by the forced protection switch has cleared.
7
The active module or port is switched to standby.
8
The Perform a 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 15.
Page 7-40
Turin Networks
Release OPS4.0.x
Chapter 1
Perform a
Manual Switch
Release TR3.0.x Traverse Software Upgrade
Perform a Manual Switch
For modules in a protection group requiring a cold restart activation due to FPGA
changes, a manual protection switch is necessary. Follow these step-by-step
instructions to perform a manual protection switch to switch the active module (with
the old software) from the active to the standby state.
Note: This procedure is required for cold restart activation only.
Table 7-19 Perform a Manual Switch
Step
Procedure
1
In Shelf View, click the Protection tab to display the Protection Groups
dialog box.
1
Figure 7-27 Protection Groups Dialog Box
2
Select the protection group.
3
Click Edit to display the Protection Group Configuration dialog box.
4
Right-click the module or port with an Active Protection status in the
Protection Group Configuration dialog box to display a shortcut menu.
Select Manual from the shortcut menu.
4
Figure 7-28 Protection Group—Manual Switch
Release OPS4.0.x
Turin Networks
Page 7-41
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Clear Protection Switch
Table 7-19 Perform a Manual Switch (continued)
Step
5
Procedure
The Confirm Manual Switch dialog box displays. Click Yes to confirm.
Figure 7-29 Confirm Manual 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 Manual Switch procedure is complete.
If you were in the procedure:
• Control Module Software Upgrade Activation, then return to
Step 14.
• Software Upgrade Activate (all other protected modules), then
return to Step 12.
Clear
Protection
Switch
Use the following step-by-step instructions to clear (release) a user-initiated protection
switch.
Table 7-20 Clear Protection Switch
Step
Procedure
1
From Map View, double-click on a node to display the Shelf View.
2
In Shelf View, click the Protection tab to display the Protection Groups
dialog box.
2
Figure 7-30 Protection Groups Dialog Box
Page 7-42
Turin Networks
Release OPS4.0.x
Chapter 1
Release TR3.0.x Traverse Software Upgrade
Clear Protection Switch
Table 7-20 Clear Protection Switch (continued)
Step
Procedure
3
Select the protection group.
4
Click Edit to display the Protection Group Creation dialog box.
5
Right-click the Standby module/port in the Protection Group Creation
dialog box to display a shortcut menu. Select Clear from the shortcut
menu.
5
Figure 7-31 Protection Group—Clear Protection Switch
6
The Confirm Release dialog box displays. Click Yes to confirm the force
switch release.
Figure 7-32 Confirm Release Dialog Box
7
Check the Alarms dialog box to verify 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 14.
– active module, then return to Step 24.
• Software Upgrade Activate (all other protected modules), then
return to Step 14.
Release OPS4.0.x
Turin Networks
Page 7-43
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Deactivate Legacy Ethernet Services
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
1
Procedure
From Map View, click the Service tab to display the services screen.
1
Figure 7-33 Service Tab
Page 7-44
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.
Turin Networks
Release OPS4.0.x
Chapter 1
Software
Revert
Procedure
Release TR3.0.x Traverse Software Upgrade
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-45
• Revert TransNav Management System Software, page 7-46
Revert Node Software
Important: This procedure is service affecting.
Important: If you expect to revert an entire node, Turin recommends
that you 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 card that has been
upgraded to the desired software load. Execute this command in the
following card order:
• Line cards, one at a time
• Standby control card (e.g., GCM)
• Active control card
CLI command sequence:
For cards 1 to n (in the order described above):
begin
exec upgrade switch-to-stdby-load slot <slot#>
Are you sure you want to execute this command?
YES.
end
exec node restart
Are you sure you want to execute this command?
YES.
Release OPS4.0.x
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.
Turin Networks
Page 7-45
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Post-Remote Node— Upgrade the Spare Control Module Software
Revert TransNav Management System Software
Table 7-23 Revert TransNav Management System Software
Step
Post-Remote
Node—
Upgrade the
Spare Control
Module
Software
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.
If you initially used the remote upgrade capability to upgrade the software version on
your network nodes, the software on your spare modules likely needs to still be
upgraded. The following procedure gives step-by-step instructions to perform this
function.
The new software is not active until the system reboots the spare (standby) control
module (i.e., Traverse GCM or TE-100 System module). The reboot activates the
backup partition with the newly downloaded software on the spare control module..
Important: This procedure assumes you have completed upgrading
(downloading and activating the new software for) the standby and active
control modules.
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. If the standby TE-100 System module is
an OC-48 module, you can only upgrade with another OC-48 system
module.
The activation is set based on the date and time entered in the Activate Time field of
the SW Activation dialog box. Use these step-by-step instructions to set up software
Page 7-46
Turin Networks
Release OPS4.0.x
Chapter 1 Release TR3.0.x Traverse Software Upgrade
Post-Remote Node— Upgrade the Spare Control Module Software
upgrade activation for spare control modules in the case where the other modules on
the node have already been upgraded.
Table 7-24 Post-Remote Node Upgrade —Upgrade the Spare Control Module
Step
Procedure
1
Remove the previously upgraded standby control module by first
restarting the module through the TransNav management system using a
cold reboot, then removing the module from the shelf.
2
Insert the spare (standby) control module.
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.
3
Download the desired software version to the spare control module using
the procedure in Table 7-7 Card Software Download Set-up, page 7-13.
4
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-26. You must change the value in the
ActType field to SPARE.
Note: After the upgrade, the EQRMV and EQCOMM alarms clear.
Release OPS4.0.x
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 Post-Remote Node Upgrade —Upgrade the Spare Control Module
procedure is complete.
Turin Networks
Page 7-47
Node Operations and Maintenance Guide, Section 7: Software Upgrades
User- selectable FPGA Upgrade Capability
Userselectable
FPGA Upgrade
Capability
In some cases, upgrading from one release to another requires a new FPGA image for a
module or set of modules. Accepting this new FPGA image can resolve an issue that is
unique to a certain deployment. The user-selectable FPGA upgrade capability (force
warm reboot) gives you the choice to 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.
Important: If a decision has been made to use Ignore FPGA, Turin
recommends upgrading to the new FPGA image as soon as possible
during a network maintenance window.
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.
Important: The Ignore FPGA function is only available from Traverse software
releases TR2.1.2.x and forward.
Figure 7-34 User-selectable FPGA Upgrade Parameter
Page 7-48
Turin Networks
Release OPS4.0.x
S ECTION 7SOFTWARE UPGRADES
Chapter 2
Release 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-53
• Software Revert Procedure, page 7-70
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
Release OPS4.0.x
TE-100 warm reboot and hitless upgrade features are planned for a future release.
Turin Networks
Page 7-49
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Before You Begin
Before You
Begin
Review this information before you begin.
Table 7-25 Node Software Upgrade Requirements
Requirement
Required
Equipment and
Tools
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 (TAC).
Have the required equipment and
tools ready.
Required Equipment and Tools, page 7-50
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 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
•
Page 7-50
1 or 2 System modules (and any spares)
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
General Software Compatibility
TransNav
Management
System GUI
Commands
and
Conventions
This document provides node software upgrade procedures using the TransNav GUI.
Refer to the TransNav Management System Product Overview Guide to become
familiar with the TransNav system.
The following conventions are used in the procedure tables.
Table 7-26 TransNav GUI Command Descriptions
Command
Description
Boldface
Boldface indicates dialog box, field, menu, and list names
Italics
Italics indicates information you supply
Compatibility
and Guidelines
Read the compatibility topics that are relevant to your specific upgrade.
• General Software Compatibility, page 7-51
• TE-100 Platform SW Upgrade Compatibility Notes, page 7-52
• Guidelines for Software Upgrade, page 7-52
General
Software
Compatibility
Control Cards. Each control card is partitioned and capable of holding two versions
of software. The new software is downloaded onto the card’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 card and activates
the back-up partition with the newly downloaded software. Provisioning data stored on
the node control card 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 cards. 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 card with a (major.x.x.x) software version lower than the
compatibility ID of the Active control card—the lowest software version the
Active control card can work with—is placed in the node.
• the Active control card (major.x.x.x) software version is lower than the
compatibility ID of the replacement card.
• the Active control card 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 card.
Release OPS4.0.x
Turin Networks
Page 7-51
Node Operations and Maintenance Guide, Section 7: Software Upgrades
TE-100 Platform SW Upgrade Compatibility Notes
A SWMIS: Software version mismatch alarm is generated when a replacement
card with either an earlier or later (major.minor.build.x) version of software than the
software running on the control card is placed in the node. In this case, use the
procedures in this section to upgrade or rollback the software version on the
replacement card.
TE-100
Platform SW
Upgrade
Compatibility
Notes
Review this information to understand the important compatibility items for the
TE-100 and TransNav 3.0.x software release.
• TE-100 software upgrade from Release 2.0.x to Release 3.0.x. This is not an
in-service upgrade.
• TransNav in-service software upgrade from Release 1.5.x, 1.5E.x, and 2.0.x to
Release 3.0.x.
• In-service 3.0.x point release software upgrades (as necessary) for TE-100 nodes.
• TransNav manages the in-service software upgrade for Release 3.0.x maintenance
releases.
• TE-100 hitless upgrade and warm reboot features are unavailable in this release.
This table shows compatible product and software release groups.
Table 7-27 Turin Product and Software Release Compatibility
TE-100 Release 3.0
Guidelines for
Software
Upgrade
Page 7-52
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
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.
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Download Node Software to the TransNav Server
•
•
•
Node Software
Upgrade
Process
Due to the use of ftp libraries, bulk software downloads may fail so schedule
software downloads 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 (part number
805-0108-30) define any potential exceptions.
Complete the software upgrade procedures in the following order:
Table 7-28 Node Software Upgrade Process
Step
Procedure
Reference
1
Have you read through, and do you
understand, all of the Before You
Begin items?
Before You Begin, page 7-50
2
Do you have the required equipment
and tools ready?
Required Equipment and Tools, page 7-50
3
Upgrade the TransNav management
system server software (includes
first exporting the current database
off the TransNav server).
TransNav Management System Server Guide,
Section 2—Management Server Procedures,
Chapter 3—“Server Administration Procedures,”
Upgrade Server Software, page 2-38
Note: Do not uninstall the previous
software version. Mark the directory
as old and remove the icon from the
desktop.
Download
Node Software
to the
TransNav
Server
4
Download the new node software to
the TransNav server.
Download Node Software to the TransNav Server,
page 7-53
5
Download the software to the
modules.
Module Software Download Set-up, page 7-57
6
Activate the new software.
Software Activation Process, page 7-63
7
The Node Software Upgrade Process is complete.
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-54
• Download Node Software to the TransNav Server— Solaris System, page 7-56
Release OPS4.0.x
Turin Networks
Page 7-53
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Download Node Software to the TransNav Server— PC System
Download
Node Software
to the
TransNav
Server— PC
System
Use this procedure to download node software to the TransNav server on a PC system.
Table 7-29 Download Node Software to the TransNav Server—PC System
Step
Procedure
1
Insert the software CD into the CD drive on the PC or navigate to the
directory where the software files were previously downloaded from the
Infocenter.
2
In an Explorer window, navigate to the CD drive containing the upgrade
software CD or temporary download directory.
Figure 7-35 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-36 Explorer “Extract to” Command
Page 7-54
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Download Node Software to the TransNav Server— PC System
Table 7-29 Download Node Software to the TransNav Server—PC System
Step
4
Procedure
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.
Figure 7-37 Extract Dialog Box
Release OPS4.0.x
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 6Step 5 of the Node Software
Upgrade Process, page 7-7.
Turin Networks
Page 7-55
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Download 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.
Table 7-30 Download Node Software to the TransNav Server—Solaris System
Step
1
Procedure
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
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 cards. To
change permissions, contact your local UNIX administrator.
Figure 7-38 Example—File Extraction Comments
4
Eject the CD from the drive.
For example:
$ eject
5
Page 7-56
The Download Node Software to the TransNav Server—Solaris System
procedure is complete. Continue to Step 6Step 5 of the Node Software
Upgrade Process, page 7-7.
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Module Software Download Set-up
Module
Software
Download
Set-up
Software upgrades are done at the node level. The following procedure provides
step-by-step instructions on how to begin a software upgrade by setting software
download times for each card using the SW Upgrade dialog box.
Table 7-31 Card Software Download Set-up
Step
Procedure
1
Verify the card software versions. Refer to Module Software Download
Set-up, page 7-57.
2
In Shelf View, select SW Upgrade from the Admin menu to display the
SW Upgrade dialog box.
Figure 7-39 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)
Release OPS4.0.x
Turin Networks
Page 7-57
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Module Software Download Set-up
Table 7-31 Card Software Download Set-up (continued)
Step
6
Procedure
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 Update and verify that there were no errors in the ftp session.
Note: This action should fill in the data for each card in the Relative
Path columns.
Important: The Relative Path and Upgrade Type (default is INIT)
values must be set by the system before the download starts.
Page 7-58
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Module Software Download Set-up
Table 7-31 Card Software Download Set-up (continued)
Step
8
Procedure
Set each Download Time based on these requirements for each card.
Approximate software download times are as follows:
• Control card download time is approximately 10 to 20 minutes
• Download time for all other cards is approximately 2 to 5 minutes
Note: Turin recommends you set sequential download times based on the
card requirements.
Note: Due to the use of ftp libraries, bulk software downloads may fail so
schedule software downloads at least 5 minutes apart.
Note: It takes a fully loaded Traverse-specific node approximately one
hour to download the new software onto all cards. 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 cards and services. It does not require
you to stand by during the download.
Note: Turin recommends you download the control cards individually,
three line cards at a time and one node at a time,
7
7
Figure 7-40 Download Time Settings
Release OPS4.0.x
Turin Networks
Page 7-59
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Module Software Download Set-up
Table 7-31 Card Software Download Set-up (continued)
Step
Procedure
9
From the Download Time drop-down box, select Set time to manually
adjust the time. Select part of the time string (e.g., month, day, hour). Use
the up and down arrows or manually re-enter the time to reset the value.
8
Figure 7-41 SW Upgrade Download Times
10
Verify the Relative Path is set for each card.
Relative Path: A literal sub-directory path (in relation to the Base Path
directory) where the software resides for each card. It is based on the type
of card in the slot and is case sensitive. For example: ds3.
11
Verify the Upgrade Type is set to the default (INIT) for each card.
Upgrade Type (default=INIT): The upgrade type for each card 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 available for special cases only when working
with TAC.
12
Page 7-60
Repeat Steps 7 through 11 for each card in the node.
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Module Software Download Set-up
Table 7-31 Card Software Download Set-up (continued)
Step
Procedure
13
You can Clear Download Time for any card by right-clicking the card in
the SW Upgrade dialog box and clicking the Update button. If necessary,
you can Abort Download to any card by right-clicking the card in the SW
Upgrade dialog box.
Note: Turin recommends that you do not leave the card in the upgrade
abort state. Clear the download time and click the Update button to clear
the abort state.
12
12
Figure 7-42 SW Upgrade—Clear Download Time
14
Verify 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 Turin’s TAC if the software download fails a
second time.
Release OPS4.0.x
Turin Networks
Page 7-61
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Module Software Download Set-up
Table 7-31 Card Software Download Set-up (continued)
Step
Procedure
16
Continue only when the Download Status is OK and the newly
downloaded software version displays in Standby SW Version field for
all cards (select each card row and check the Standby SW Version field).
This indicates the software download has successfully completed.
15a
15b
15a
15b
Figure 7-43 Dnld Status and Standby SW Version Fields
17
The Card 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-37
Return to Step 6 of the Node Software Upgrade Process, page 7-7.
Page 7-62
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Software Activation Process
Card Software
Version
Verification
You can determine the software version number of a card (card) using the TransNav
GUI. The software version and serial number are displayed on the Config tab in Shelf
View. Follow these steps to verify the software version.
Table 7-32 Card Software Version Number Verification
Step
Procedure
1
In Shelf View, click a card to select it.
2
Click the Config tab to view current software version information.
2
Figure 7-44 Card Configuration Dialog Box
Software
Activation
Process
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 Card Software Version Number Verification procedure is complete.
The new software is not active until the system reboots each module. The reboot
activates the backup partition with the newly downloaded software.
Important: Read all important notes below before beginning the
activation process.
Important: Software activation should start at the node farthest from the
server that is connected to the head end node, then work inward.
Release OPS4.0.x
Turin Networks
Page 7-63
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Control Module Software Upgrade Activation
Important: During software activation, the modules automatically
reboot. Do not execute any external commands on the modules during
software activation.
Table 7-33 Software Activation Process
Step
Control Module
Software
Upgrade
Activation
Page 7-64
Procedure
Reference
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?
Download Node Software to the TransNav Server,
page 7-53
3
Is the module software download
complete?
Module Software Download Set-up, page 7-57
4
Activate software for:
• Standby control module
• Spare (standby) control
module(s), unless you are using
the remote upgrade capability
and want to upgrade your spare
modules at a later time (see
Chapter 1—“Release TR3.0.x
Traverse Software Upgrade,”
Post-Remote Node— Upgrade
the Spare Control Module
Software, page 7-46).
• Active control module
Control Module Software Upgrade Activation,
page 7-64
5
The Software Activation Process is complete. Continue to Step 7 of the Node Software
Upgrade Process, page 7-53.
The new software is not active until the system reboots each module. The reboot
activates the backup partition with the newly downloaded software on the control
module.
Important: Do not start the Activate Software— Control Module
procedure until the downloaded software version displays in the SW
Upgrade dialog box, Standby SW Ver field for all modules, indicating the
software download has successfully completed.
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Control Module Software Upgrade Activation
The activation is scheduled for each module based on the date and time entered in the
Activate Time field of the SW Upgrade dialog box. Follow these step-by-step
instructions to set up software upgrade activation for control modules.
Table 7-34 Activate Software— Control Module
Step
Procedure
1
Verify the network is alarm free or validate and record any alarms present
prior to activation.
2
In Shelf View, select a control module and click the Config tab.
3
Verify the Protection Status of the Active/Standby control module using
the Card Configuration dialog box.
3
3
Figure 7-45 Card Configuration Protection Status
Release OPS4.0.x
Turin Networks
Page 7-65
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Control Module Software Upgrade Activation
Table 7-34 Activate Software— Control Module (continued)
Step
Procedure
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.
4
Figure 7-46 SW Upgrade—Activate Time
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.
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 TAC if the software activation fails a second time.
Page 7-66
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Control Module Software Upgrade Activation
Table 7-34 Activate Software— Control Module (continued)
Step
Procedure
7
Verify 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 TAC.
7
8
6
7
Figure 7-47 Act Status and Current SW Ver Fields
Release OPS4.0.x
8
With the standby control module selected in Shelf View, select the Alarms
tab and check the Alarms dialog box. Verify that the EQFAIL:
equipment failure alarm caused by the reboot has cleared.
9
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.
10
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-69 procedure.
Turin Networks
Page 7-67
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Control Module Software Upgrade Activation
Table 7-34 Activate Software— Control Module (continued)
Step
Procedure
11
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.
12
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.
13
Click Update.
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 TAC if the software activation fails a second time.
14
Verify the new software version activation is complete and it is displayed
in the SW Upgrade dialog box, Current SW Ver field.
Note: Activating the active control module causes the new software to
upgrade and a switchover to the protection module.
Page 7-68
15
With the now standby (previously active) control module selected in Shelf
View, select the Alarms tab and check the Alarms dialog box. Verify the
EQFAIL: equipment failure alarm caused by the reboot has cleared.
16
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.
17
The Activate Software— Control Module procedure is complete.
Continue to Step 5 of the Software Activation Process, page 7-63.
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Spare 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.
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. Likewise, if the standby TE-100 System
module is an OC-48 module, you can only upgrade with another OC-48
system module.
The activation is scheduled for each module based on the date and time entered in the
Activate Time field of the SW Upgrade dialog box. Follow these step-by-step
instructions to set up software upgrade activation for spare control modules.
Table 7-35 Activate Software—Spare Control Modules
Step
Release OPS4.0.x
Procedure
1
Remove the upgraded standby control module by restarting the module
through the TransNav management system, then removing the module
from the shelf.
2
Insert the spare (standby) control module.
3
Once the spare control module is online and the EQRMV and EQCOMM
alarms are clear, download the new software version to the module using
the Table 7-31 Card Software Download Set-up, page 7-57 procedure.
4
Once the new software downloads to the spare control module, activate the
software using the steps described for the standby control module in the
Table 7-34 Activate Software— Control Module, page 7-65 procedure
(using ActType=SPARE).
5
Repeat Steps 1 through 4 for each spare control module.
6
Once upgrade and activation is complete for all the spare control modules,
place the original standby control module back into the standby slot and
continue the procedure to activate software on the active control module.
7
The Activate Software—Spare Control Modules procedure is complete.
Continue to Step 11 of the procedure Control Module Software Upgrade
Activation, page 7-68.
Turin Networks
Page 7-69
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Software Revert Procedure
Software
Revert
Procedure
Use the following procedures to revert to a previous software version used on the node
and TransNav management system.
• Revert Node Software, page 7-70
• Revert TransNav Management System Software, page 7-71
Revert Node Software
Important: This procedure is service affecting.
Important: If you expect to revert an entire node, Turin recommends
that you call TAC for assistance.
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 card that has been
upgraded to the desired software load. Execute this command in the
following card order:
• Line cards, one at a time
• Standby control card (e.g., GCM)
• Active control card
CLI command sequence:
For cards 1 to n (in the order described above):
begin
exec upgrade switch-to-stdby-load slot <slot#>
Are you sure you want to execute this command?
YES.
end
exec node restart
Are you sure you want to execute this command?
YES.
Page 7-70
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.
Turin Networks
Release OPS4.0.x
Chapter 2 Release 3.0.x TE-100 System Software Upgrade
Software Revert Procedure
Revert TransNav Management System Software
Table 7-37 Revert TransNav Management System Software
Step
Release OPS4.0.x
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.
Turin Networks
Page 7-71
Node Operations and Maintenance Guide, Section 7: Software Upgrades
Software Revert Procedure
Page 7-72
Turin Networks
Release OPS4.0.x
S ECTION 8
H ARDWARE U PGRADES
S ECTION 8
Contents
Chapter 1
Replacing Existing Traverse Hardware
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Fan Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Software Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Electrostatic Discharge Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Traverse Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Replacement Module—Type and Software Version . . . . . . . . . . . . . . . . . . . . 8-4
Preparing a Module for Removal and Replacement . . . . . . . . . . . . . . . . . . . . 8-6
Remove a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Module Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
GCM Module Replacement as Standby— LED Indicators . . . . . . . . . . . . . . . 8-13
Clean Fiber Optic MPX Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Insert a Replacement Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Replace the Front Inlet Fan Tray Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Front Inlet Fan Tray Air Filter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Replace the Traverse 600 Fan Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
Fan Assembly Air Filter Installation (Traverse 600) . . . . . . . . . . . . . . . . . . . . 8-26
Replace the Fan Tray Module (legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Fan Tray Air Filter Installation (legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Install a Fan Tray Air Filter with Handle (Legacy) . . . . . . . . . . . . . . . . . . . . . . 8-30
Chapter 2
Upgrade to a Traverse Front Inlet Fan Tray
Precautions and Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
FIFT Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
Check the New Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
List of Figures
Figure 8-1
Figure 8-2
Figure 8-3
Figure 8-4
Release OPS4.0.x
Card Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Equipment Mismatch Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Card Tabs in the Unlocked Position . . . . . . . . . . . . . . . . . . . . . . . 8-8
Fiber Optic Backplane Housing A and B. . . . . . . . . . . . . . . . . . . . 8-15
Turin Networks
Page i
Node Operations and Maintenance Guide, Section 8 Hardware Upgrades
Figure 8-5
Figure 8-6
Figure 8-7
Figure 8-8
Figure 8-9
Figure 8-10
Figure 8-11
Figure 8-12
Figure 8-13
Figure 8-14
Figure 8-15
Figure 8-16
Figure 8-17
Figure 8-18
Figure 8-19
Figure 8-20
Figure 8-21
Figure 8-22
Figure 8-23
Traverse 600 Fiber Optic Backplane Housing A and B . . . . . . . . . 8-16
Optical Card MPX Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Card Locking Tabs in the Unlocked Position. . . . . . . . . . . . . . . . . 8-19
Traverse 1600 or Traverse 2000 Shelf with Guides . . . . . . . . . . . 8-20
Traverse 600 Shelf with Guides . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Card Tabs in the Locked Position . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Front Inlet Fan Card Captive Fasteners . . . . . . . . . . . . . . . . . . . . 8-22
Front Inlet Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Fan Assembly Front Cover - Traverse 600 . . . . . . . . . . . . . . . . . . 8-24
Traverse 600 Fan Assembly Installation . . . . . . . . . . . . . . . . . . . . 8-25
Traverse 600 Fan Assembly Air Filter . . . . . . . . . . . . . . . . . . . . . . 8-26
Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Traverse 1600 Fan Tray Card Installation . . . . . . . . . . . . . . . . . . . 8-28
Traverse 2000 Fan Tray Card Installation . . . . . . . . . . . . . . . . . . . 8-28
Air Filter with Springs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
Air Filter with Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
Fan Tray Holder Front Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Existing Fan Tray Holder Back Panel . . . . . . . . . . . . . . . . . . . . . . 8-35
Table 8-1
Table 8-2
Table 8-3
Table 8-4
Table 8-5
Table 8-6
Table 8-7
Table 8-8
Table 8-9
Table 8-10
Table 8-11
Table 8-12
Table 8-13
Table 8-14
Table 8-15
Table 8-16
Table 8-17
Card Software Version Number Verification . . . . . . . . . . . . . . . . . 8-3
Preparing a Module for Removal and Replacement . . . . . . . . . . . 8-6
Remove a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Card Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Redundancy Rules for GCM Types . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Power and Active/Standby—All Cards . . . . . . . . . . . . . . . . . . . . . 8-13
Clean Cable and Card MPX Connectors . . . . . . . . . . . . . . . . . . . . 8-15
Insert a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Insert a Traverse 1600 and Traverse 2000 Fan Assembly . . . . . . 8-22
Insert a Traverse 1600 and Traverse 2000 Fan Air Filter . . . . . . . 8-23
Insert a Traverse 600 Fan Assembly. . . . . . . . . . . . . . . . . . . . . . . 8-24
Insert a Traverse 600 Fan Air Filter. . . . . . . . . . . . . . . . . . . . . . . . 8-26
Insert a Fan Tray Card (Legacy) . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Install a Fan Tray Air Filter with Springs (Legacy). . . . . . . . . . . . . 8-29
Install a Fan Tray Air Filter with Handle (Legacy) . . . . . . . . . . . . . 8-30
Front Inlet Fan Tray Holder Upgrade Instructions . . . . . . . . . . . . . 8-34
New Fan Module Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
List of Tables
Page ii
Turin Networks
Release OPS4.0.x
Node Operations and Maintenance Guide, Section 8 Hardware Upgrades
Release OPS4.0.x
Turin Networks
Page iii
Node Operations and Maintenance Guide, Section 8 Hardware Upgrades
Page iv
Turin Networks
Release OPS4.0.x
S ECTION 8HARDWARE U PGRADES
Chapter 1
Replacing Existing Traverse Hardware
Introduction
During the course of normal operation, various conditions may arise that require
network operations personnel to replace existing system equipment. This section
describes Traverse module and fan equipment replacement.
Modules
All modules in the Traverse system, including the General Control Modules (GCMs),
are “hot-swappable” and can be removed and replaced while the system is in operation.
During replacement procedures, service is interrupted to all connections on the
removed modules. For related information about adding and removing modules using
the TransNav GUI, see the TransNav Management System GUI Guide,
Section 3—Network, Chapter 1—“Creating and Deleting Equipment Using
Preprovisioning.”
The module replacement topics in this chapter are as follows:
• Software Compatibility, page 8-2
• Software Version Verification, page 8-3
• Electrostatic Discharge Protection, page 8-4
• Required Equipment and Tools, page 8-4
• Replacement Module—Type and Software Version, page 8-4
• Preparing a Module for Removal and Replacement, page 8-6
• Remove a Module, page 8-8
• Module Placement, page 8-9
• GCM Module Replacement as Standby— LED Indicators, page 8-13
• Clean Fiber Optic MPX Connectors, page 8-14
• Insert a Replacement Module, page 8-18
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.
Release OPS4.0.x
Turin Networks
Page 8-1
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Software Compatibility
The fan equipment replacement topics are as follows:
• Section 8—Hardware Upgrades, Chapter 2—“Upgrade to a Traverse Front Inlet
Fan Tray,” page 8-33
• Replace the Front Inlet Fan Tray Module, page 8-22
• Front Inlet Fan Tray Air Filter Installation, page 8-23
• Replace the Traverse 600 Fan Assembly, page 8-24
• Fan Assembly Air Filter Installation (Traverse 600), page 8-26
• Replace the Fan Tray Module (legacy), page 8-27
• Fan Tray Air Filter Installation (legacy), page 8-29
Software
Compatibility
Control Cards. Each control card is partitioned and capable of holding two versions
of software. The new software is downloaded onto the card’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 card and activates
the back-up partition with the newly downloaded software. Provisioning data stored on
the node control card 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 cards. 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 card with a (major.x.x.x) software version lower than the
compatibility ID of the Active control card—the lowest software version the
Active control card can work with—is placed in the node.
• the Active control card (major.x.x.x) software version is lower than the
compatibility ID of the replacement card.
• the Active control card 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 card.
A SWMIS: Software version mismatch alarm is generated when a replacement
card with either an earlier or later (major.minor.build.x) version of software than the
software running on the control card is placed in the node. In this case, use the
procedures in this section to upgrade or rollback the software version on the
replacement card.
Refer to Section 7—Software Upgrades, Chapter 1—“Release TR3.0.x Traverse
Software Upgrade” for software upgrade procedures.
Page 8-2
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Software Version Verification
Software
Version
Verification
You can determine the software version number of a card (card) using the TransNav
GUI. The software version and serial number are displayed on the Config tab in Shelf
View. Follow these steps to verify the software version.
Table 8-1 Card Software Version Number Verification
Step
Procedure
1
In Shelf View, click a card to select it.
2
Click the Config tab to view current software version information.
2
Figure 8-1 Card Configuration Dialog Box
Release OPS4.0.x
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 Card Software Version Number Verification procedure is complete.
Turin Networks
Page 8-3
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Electrostatic Discharge Protection
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
Required
Equipment and
Tools
The following equipment and tools are required to place cards 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 card 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 cards, as well as any spares
System interface module (SIM) cards
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 TR3.0.x Traverse Software Upgrade” for procedures on how to
convert software versions on a replacement module.
Page 8-4
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Replacement Module—Type and Software Version
Module of Different Type. If you replace a module with a different type of module,
an Equipment Mismatch alarm is generated indicating a failure condition. In the
following Map View, the Alarm tab provides an example of an Equipment
Mismatch alarm in the TransNav GUI:
Figure 8-2 Equipment Mismatch Alarm
Release OPS4.0.x
Turin Networks
Page 8-5
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Preparing a Module for Removal and Replacement
Preparing a
Module for
Removal and
Replacement
The following procedures provide step-by-step instructions on how to prepare a
module for removal and replacement using the TransNav GUI.
Important: GCM, Enhanced GCM (EGCM), Universal GCM (UGCM),
and GCMs with integrated optics are considered different modules and
must be physically removed and deleted via TransNav prior to replacement
with a different GCM module type to avoid an EQMIS: Equipment
Mismatch alarm.
Important: The Traverse system allows the network operator an
in-service upgrade capability (protection switching) to replace older GCM
modules with the newer GCM modules in a redundant configuration. The
following replacement rules apply:
Replace:
• GCM with a UGCM
• EGCM (without optics) with a UGCM
• EGCM (with OC-12/STM-4) with a UGCM with 1-port
OC-12/STM-4
• EGCM (with OC-48/STM-16) with a UGCM with OC-48/STM-16
Important: The Traverse system allows the network operator an
in-service upgrade capability (protection switching) to replace older DS3,
E3, EC-1, and DS3 Transmux modules with the newer DS3, E3, EC-1, and
DS3 Transmux modules with no greater than 50 ms traffic interruption for
each module in any 1:N (where N=1,2) protection group.
Table 8-2 Preparing a Module for Removal and Replacement
Step
Procedure
1
In the TransNav GUI, go to Shelf View.
2
Click the module to be removed.
3
Click the Config tab to display the Card Configuration dialog box.
4
Click the Lock icon
at the bottom left portion of the screen to change
and click Apply.
the Administrative state to locked
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-8 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.
Page 8-6
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Preparing a Module for Removal and Replacement
Table 8-2 Preparing a Module for Removal and Replacement (continued)
Step
Release OPS4.0.x
Procedure
6
In the TransNav GUI, right-click the module and select Delete Card to
delete the card or Replace with Card to replace with a different type of
module.
7
Place the new module in the Traverse shelf. Refer to the following
sequence of topics for important details:
• Module Placement, page 8-9
• GCM Module Replacement as Standby— LED Indicators,
page 8-13 (Standby GCM module replacement only.)
• Clean Fiber Optic MPX Connectors, page 8-14
• Insert a Replacement Module, page 8-18
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.
Turin Networks
Page 8-7
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Remove a Module
Remove a
Module
Follow these step-by-step instructions to remove a module.
Important: A properly grounded ESD wrist strap must be worn at all
times while handling Traverse modules to prevent damage to the circuitry.
Important: Handle modules by the edges and face plate only. Do not
touch any module connectors or components.
Table 8-3 Remove a Card
Step
1
Procedure
Flip the locking tabs up to unlock the card.
Locking Tabs in
Open Position
OPS 00083
Figure 8-3 Card Tabs in the Unlocked Position
Page 8-8
2
Hold the card with the tabs parallel to the top and bottom of the card and
pull it straight out of the slot.
3
The Remove a Card procedure is complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Module Placement
Module
Placement
The following restrictions apply for module placement in a Traverse shelf.
Refer to Appendix A—“Module Placement Planning and Guidelines,” page 9-1 for
additional information.
X
Table 8-4 Card Placement Guidelines
Card Type
Traverse
1600
Slot #s
Traverse
2000
Slot #s
Traverse
600
Slot #s
GCMA
and
GCMB
(slots 15
and 16)
GCMA
and
GCMB
(slots 19
and 20)
GCMA
and
GCMB
(slots 5
and 6)
Comments
(Front-shelf Perspective)
GCM
•
•
•
•
•
•
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/VCX
• GCM with OC-48/STM-16 plus
VTX/VCX
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 cards.
Electrical
•
•
•
•
•
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 card (of
another type) to the left of any
10/100BaseTX-inclusive card.
In a 1:1 equipment protection scheme with a
2-slot electrical connector card (ECM), either
the left- or right-adjacent card from the
protection card is the working card.
In a 1:2 equipment protection scheme, the
center card protects the left- and right-adjacent
working cards.
In an unprotected scheme, place cards in any
valid slot; the 2-slot DS3/E3 ECM provides
access to only the right-most card, so place an
optic card in the left-most slot. The 3-slot
DS3/E3 and 3-slot E1 ECM provides access to
only the center and right-most cards, so place
an optic card in the left-most slot.
(SONET network only) The DS3 Transmux
card 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 card protects all remaining adjacent cards.
Release OPS4.0.x
Turin Networks
Page 8-9
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Module Placement
Table 8-4 Card Placement Guidelines (continued)
Card Type
Traverse
1600
Slot #s
Traverse
2000
Slot #s
Traverse
600
Slot #s
1–12
1–16
1–4
Comments
(Front-shelf Perspective)
Ethernet (Next Generation)
NGE and NGE Plus:
• GbE [LX, SX] plus 10/100BaseTX
Combo [CEP]
• GbE TX plus GbE [LX or SX] plus
10/100BaseTX Combo [CEP]
Important: Do not place an electrical card (of
another type) to the left of any
10/100BaseTX-inclusive card.
In a 1:1 equipment protection scheme with a
2-slot Ethernet Protection ECM, either the
left- or right-adjacent card from the protection
card is the working card.
NGE only:
• GbE CWDM plus 10/100BaseTX
Combo
• GbE SX plus GbE CWDM plus
10/100BaseTX Combo
In an unprotected scheme, place cards in any
valid slot. The 2-slot Ethernet Protection ECM
provides access to only the right-most card, so
place an optic card in the left-most slot.
Use the following options when placing any
10/100BaseTX-inclusive cards in a Traverse
shelf with DS1, DS3/E3/EC-1 CC, DS3/EC-1
Transmux, or E1 cards:
• Place 10/100BaseTX-inclusive cards
directly to the left of DS1, DS3/E3/EC-1
CC, DS3/EC-1 Transmux, or E1 cards. An
OC-N/STM-N card or 1-slot wide blank
faceplate is not required if the
10/100BaseTX-inclusive cards are placed
to the left of electrical interface cards.
or
• Place an OC-N/STM-N card or a 1-slot
wide blank faceplate between the
10/100BaseTX and an electrical interface
card if the 10/100BaseTX-inclusive card is
placed to the right of the electrical interface
card.
Ethernet (Dual Slot GbE)
• 10GBASE-LR
1–14
1–18
• 10-port 1GbE card, no optics
1–12
1–16
1–14
1–18
n/a
None
Requires an SFP connector card. See Traverse
Installation and Commissioning Guide,
Section 2—Network Interface Specifications,
Chapter 1—“Fiber Optic Interface Cabling
Specifications,” GbE-10 SCM, Fiber
Assignments, and SFPs, page 2-4.
SONET/SDH
•
•
•
•
OC-3/STM-1
OC-12/STM-4
OC-48/STM-16
OC-48/STM-16 with VTX/VCX
(legacy)
Page 8-10
1-4
Turin Networks
None
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Module Placement
Table 8-4 Card Placement Guidelines (continued)
Card Type
• OC-192/STM-64
Traverse
1600
Slot #s
Traverse
2000
Slot #s
Traverse
600
Slot #s
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 cards require two slots
for placement. The left side of the
OC-192/STM-64 card is placed in an odd
numbered slot.
1–14
1–18
1-4
The VT/TU 5G Switch card supports 1:N
equipment protection where:
• N=1 to 9 in a Traverse 2000
(SONET network only)
• N=1 (SDH network only)
Comments
(Front-shelf Perspective)
VT/TU Switching
VT/TU 5G Switch
This card has no ECM requirement. One card
protects all adjacent cards.
Important: Place an OC-N/STM-N or 1-slot blank faceplate between any
10/100BaseTX-inclusive card and an electrical card (of another type), if the
10/100BaseTX-inclusive card is placed to the right of an electrical interface
card. A blank faceplate or OC-N/STM-N card is not required if the
10/100BaseTX-inclusive card is placed to the left of an electrical card.
Important: To ensure EMI protection and proper cooling, place one-slot
wide blank faceplates in any empty Traverse slots.
Turin recommends the following card 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) cards 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 cards next to the GCM cards. Place additional cards
toward the center of the shelf as required.
• Place OC-N/STM-N and GbE cards (optical cards) beginning in the right-most
available slot (starting at Traverse 1600 slot 14 or Traverse 2000 slot 18). Place
additional cards towards the center of the shelf as required.
Release OPS4.0.x
Turin Networks
Page 8-11
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Module Placement
The following table shows the redundancy rules for all GCM types:
Table 8-5 Redundancy Rules for GCM Types
Active GCM
1
Page 8-12
Standby GCM
GCM
GCM
GCM
GCM Enhanced | Universal1
GCM Enhanced | Universal1
GCM
GCM Enhanced | Universal
GCM Enhanced | Universal
GCM with OC-N/STM-N
GCM with OC-N/STM-N
GCM Enhanced or Universal environmental alarm function should not be used in this combination.
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
GCM Module Replacement as Standby— LED Indicators
GCM Module
Replacement
as Standby—
LED Indicators
When a new GCM module is placed as the standby module, the Power and
Active/Standby LED indications are as shown in the following table.
The LEDs in the following tables apply to all cards.
Table 8-6 Power and Active/Standby—All Cards
RED
Amber
GREEN
OFF
LED
Power
Active/
Standby
Flashing
Solid
Initialization
and diagnosis
is underway
but not
complete
Hardware
failure
detected;
replace the
card
N/A
N/A
Flashing
Solid
Flashing
N/A
N/A
N/A
The card is
unlocked and in
Standby mode.1
Synchronization
with the Active
card is not
complete.
The card is
unlocked. The
card type does not
match the
provisioned card
type or the card is
placed in an
invalid slot.2
The card is
unlocked and in
Standby mode.
Synchronization
with the Active
card is complete.
Solid
Initialization is
complete and
the card is
operational.
The Active
card is
unlocked and
operational.
No power
The card is
locked or
initialization
is not
complete.
1
Does not apply to GbE or OC-N cards.
2
For the Traverse platform, refer to Appendix A—“Card Placement Planning and Guidelines,” page 12-1 for valid card placement
guidelines.
Release OPS4.0.x
Turin Networks
Page 8-13
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Clean Fiber Optic MPX Connectors
Clean Fiber
Optic MPX
Connectors
It is critical that the cable and card 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 cards using fiber optic magnification equipment. Turin
also recommends that you clean the fiber optic cable and card 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 cards in the Traverse shelf.
Follow all warnings and instructions included in card packaging to prevent
electrostatic damage.
Important: Handle cards by the edges and faceplate only. Do not touch
any card connectors or components.
Important: Do not touch the end of the MPX connectors.
Page 8-14
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Clean Fiber Optic MPX Connectors
Table 8-7 Clean Cable and Card 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 the 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-9.
Release OPS4.0.x
Turin Networks
Page 8-15
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Clean Fiber Optic MPX Connectors
Table 8-7 Clean Cable and Card MPX Connectors (continued)
Step
Procedure
5
Align the “white reference marker” on the MPX connector with the white
stripe on the left side of the Traverse 600 fiber optic backplane housing.
White Stripe
Reference Markers
Housing A
Housing B
OPS 00085
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 card MPX connector(s).
Dust Cap on MPX
Connector
OPS 00083
Figure 8-6 Optical Card MPX Connector
Page 8-16
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Clean Fiber Optic MPX Connectors
Table 8-7 Clean Cable and Card MPX Connectors (continued)
Step
Release OPS4.0.x
Procedure
9
Clean the optical card 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 Card.
Turin Networks
Page 8-17
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Insert a Replacement Module
Insert a
Replacement
Module
Important: Always use a properly grounded Electrostatic Discharge
(ESD) wrist strap when handling Traverse cards (cards). Plug the ESD
wrist strap into the ESD jack provided on the Traverse front inlet fan card,
standalone air ramp, or other confirmed source of earth ground. Refer to
ESD Jack Locations, page 6-7.
‘
Important: Do not install Traverse cards until all installation and cabling
procedures are complete.
Important: Handle cards by the edges and faceplate only. Do not touch
any card connectors or components.
Important: Observe all electrostatic sensitive device warnings and
precautions when handling Traverse cards.
Important: Insert the card into the Traverse shelf using the guides at the
top and bottom of the card cage for proper alignment. Make sure the card
is vertical, from top to bottom, and that the card stays in the guides from
the front to the back of the shelf.
Important: Do not place an electrical card (of another type) in the slot
directly to the left of any 10/100BaseTX-inclusive card:
• NGE
• NGE Plus
• Legacy Ethernet
Important: Cards should insert easily into the Traverse shelf. Do not
force the card into position. If the card does not insert easily, slide it back
out, verify you are placing it in the correct position and inserting the card
into the correct guides top and bottom.
Important: Insert the card in the Traverse 600 shelf using the guides for
proper alignment. If the Traverse 600 shelf is installed horizontally make
sure the card is horizontal, from left to right, and that the card stays in the
guides.
Page 8-18
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Insert a Replacement Module
Important: To ensure EMI protection and proper cooling, place one-slot
wide blank faceplates in any empty Traverse slots.
Follow these steps to insert a card.
Table 8-8 Insert a Card
Step
Procedure
1
Is this an optical card with MPX connectors?
• If yes, complete the Clean MPX Connectors procedure before
proceeding.
• If no, continue to Step 2.
2
Flip the card locking tabs up. Hold the card with the tabs parallel to the top
and bottom of the card.
Guide Pins
Locking Tabs in Open
Position
OPS 00083
Figure 8-7 Card Locking Tabs in the Unlocked Position
Release OPS4.0.x
Turin Networks
Page 8-19
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Insert a Replacement Module
Table 8-8 Insert a Card (continued)
Step
Procedure
3
Important: Each slot in the Traverse shelf has guides to properly align
the card into position for contact with the main and mesh backplanes. Use
these guides to ensure the card is properly aligned. This is easier to do if
you are eye level with the shelf. The card should insert easily into the
Traverse shelf. Do not force the card into position.
Insert the card 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 card is vertical, from top to bottom, and that the card stays in the
guides from the front to the back of the shelf.
Card Cage Guides for
Card Alignment
Figure 8-8 Traverse 1600 or Traverse 2000 Shelf with Guides
Insert the card 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 card is horizontal (from left to right) and
that the card stays in the guides from the front to the back of the shelf.
Card Cage Guides for Card
Alignment
Figure 8-9 Traverse 600 Shelf with Guides
Page 8-20
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Insert a Replacement Module
Table 8-8 Insert a Card (continued)
Step
Procedure
4
Push the center of the card faceplate until the locking tabs begin to close
and the locking tabs start to roll around the lip of the Traverse shelf. The
optical card 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
card to lock the card in place.
Locking Tabs in
Closed Position
Figure 8-10 Card Tabs in the Locked Position
Release OPS4.0.x
6
Press the tabs into their locked position to secure the card. The card 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 Card procedure is complete.
Turin Networks
Page 8-21
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Replace the Front Inlet Fan Tray Module
Replace the
Front Inlet Fan
Tray Module
The front inlet fan tray holder is bundled and shipped with the Traverse 1600 and
Traverse 2000 systems. The fan tray module, including the fans, is shipped separately.
Proceed with the following steps to install the fan tray module into the fan tray holder.
Important: The instructions below support the redesigned front inlet fan
tray with integrated air ramp unit. Refer to Replace the Fan Tray Module
(legacy), page 8-27 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 Traverse 1600 and Traverse 2000 Fan Assembly
Step
Procedure
1
Lift the front inlet fan card to be level with the front inlet fan tray holder.
Slide the fan card into the front of the fan tray holder and push it straight in
until the two connectors engage.
2
The front inlet fan card is in the correct position when it is flush with the
front of the fan tray holder.
Important: Do not force the fan card 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.
OPS 00088
Captive Fasteners
Figure 8-11 Front Inlet Fan Card Captive Fasteners
4
Page 8-22
Continue to the next procedure, Insert a Traverse 1600 and Traverse 2000
Fan Air Filter.
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Front Inlet Fan Tray Air Filter Installation
Front Inlet Fan
Tray Air Filter
Installation
The front inlet fan module requires a foam air filter that is placed at the top of the front
inlet fan tray holder after the fan module is installed.
Important: The instructions below support the redesigned front inlet fan
tray with integrated air ramp unit. Refer to Fan Tray Air Filter
Installation (legacy), page 8-29 if you are installing an original fan tray
air filter.
The front inlet fan tray air filters are available in 63% or 80% arrestance at 300 FPM—
feet per minute (91.4 meters per minute) depending on your installation requirements.
The following procedure provides step-by-step instructions on how to insert the front
inlet fan tray air filter.
Table 8-10 Insert a Traverse 1600 and Traverse 2000 Fan Air Filter
Step
1
Procedure
Grasp the air filter flexible pull tab.
OPS 00056
Pull Tab (top view)
Figure 8-12 Front Inlet Air Filter
Release OPS4.0.x
2
Insert the air filter in the gap between the top of the front inlet fan card 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 Install a Fan Tray Air Filter with Springs (Legacy) procedure is
complete.
Turin Networks
Page 8-23
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Replace the Traverse 600 Fan Assembly
Replace the
Traverse 600
Fan Assembly
The Traverse 600 fan module with integral fan tray is bundled and shipped with the
Traverse 600 system. Proceed with the following steps to install the fan assembly.
Important: Wear a properly grounded Electrostatic Discharge (ESD)
wrist strap when installing the fan tray module as it contains static-sensitive
components.
Table 8-11 Insert a Traverse 600 Fan Assembly
Step
Procedure
1
Loosen the two captive screws on the right-front cover of the Traverse 600
fan assembly to release it.
OPS 00089
Captive
Fasteners
Figure 8-13 Fan Assembly Front Cover - Traverse 600
2
Page 8-24
Open the right-front fan assembly cover.
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Replace the Traverse 600 Fan Assembly
Table 8-11 Insert a Traverse 600 Fan Assembly (continued)
Step
Procedure
3
Hold the fan assembly vertically with the fan card 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 card into position. If it does not plug
in easily, slide it back out. Check for any obstructions or a damaged
connector that might prevent it from sliding into position and verify it is
lined up in the correct guides.
Traverse 600
Shelf
Fan Assembly
OPS 00090
Figure 8-14 Traverse 600 Fan Assembly Installation
4
Release OPS4.0.x
Continue to the next procedure, Insert a Traverse 600 Fan Air Filter.
Turin Networks
Page 8-25
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Fan Assembly Air Filter Installation (Traverse 600)
Fan Assembly
Air Filter
Installation
(Traverse 600)
The Traverse 600 fan assembly (fan module with integral fan tray) requires a foam air
filter that is placed to the left of the fan assembly after the fan module is installed.
The Traverse 600 fan air filters are available in 63% or 80% arrestance at 300 FPM—
feet per minute (91.4 meters per minute) depending on your installation requirements.
The following procedure provides step-by-step instructions on how to insert the air
filter.
Table 8-12 Insert a Traverse 600 Fan Air Filter
Step
1
Procedure
Grasp the air filter flexible pull tab.
Pull Tab (top view)
OPS 00057
Figure 8-15 Traverse 600 Fan Assembly Air Filter
Page 8-26
2
Insert the air filter in the gap between the fan assembly and the left of the
fan cage. Slide the air filter along the guides until the filter is flush.
3
The Install a Fan Tray Air Filter with Springs (Legacy) procedure is
complete.
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Replace the Fan Tray Module (legacy)
Replace the
Fan Tray
Module
(legacy)
This topic applies to the original fan tray unit without an integrated air ramp (legacy,
pre-Release 1.4). Refer to Replace the Front Inlet Fan Tray Module, page 8-22 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-24 if you are
installing the fan assembly for the Traverse 600 shelf.
The (legacy) fan tray holder is bundled and shipped with the Traverse 1600 and
Traverse 2000 system. The fan tray module, including the fans, is shipped separately.
Proceed with the following steps to install the fan tray module into the fan tray holder.
Important: Wear a properly grounded Electrostatic Discharge (ESD)
wrist strap when installing the fan tray module as it contains static-sensitive
components.
Table 8-13 Insert a Fan Tray Card (Legacy)
Step
Procedure
1
Loosen the captive fasteners on the fan tray holder front cover to release it.
OPS 00059
Captive Fasteners
Figure 8-16 Fan Tray Holder Front Cover
2
Release OPS4.0.x
Lower the fan tray holder front cover.
Turin Networks
Page 8-27
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Replace the Fan Tray Module (legacy)
Table 8-13 Insert a Fan Tray Card (Legacy) (continued)
Step
Procedure
3
Lift the fan tray card until it is level with the fan tray holder. Slide the fan
tray card into the fan tray holder along the guides. Push it straight in until it
connects to the fan tray holder.
Fan Tray Card Connector
Fan Tray Holder
Guides
Figure 8-17 Traverse 1600 Fan Tray Card Installation
Fan Tray Card Connector
Fan Tray Holder
Guides
Figure 8-18 Traverse 2000 Fan Tray Card Installation
4
The fan tray card 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 card into position. If it does not plug
in easily, slide it back out. Check for any obstructions or a damaged
connector that may prevent it from sliding into position and verify it is in
the correct guides.
5
Page 8-28
Continue to the next procedure, Install a Fan Tray Air Filter with Springs
(Legacy) or Install a Fan Tray Air Filter with Handle (Legacy).
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Fan Tray Air Filter Installation (legacy)
Fan Tray Air
Filter
Installation
(legacy)
This topic applies to the air filters for the original fan tray unit without an integrated air
ramp (pre-Release 1.4). Refer to Front Inlet Fan Tray Air Filter Installation,
page 8-23 if you are installing the front inlet fan tray air filter into the redesigned front
inlet fan tray holder with integrated air ramp unit.
Table 8-14 Install a Fan Tray Air Filter with Springs (Legacy)
Step
1
Procedure
Rotate the air filter pull-tabs out.
Springs
OPS 00058
Pull Tabs
Figure 8-19 Air Filter with Springs
Release OPS4.0.x
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 card 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.
Turin Networks
Page 8-29
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Install a Fan Tray Air Filter with Handle (Legacy)
Table 8-14 Install a Fan Tray Air Filter with Springs (Legacy) (continued)
Step
6
Procedure
Lift the fan tray holder front cover into its closed position. Tighten the
captive fasteners to secure it.
OPS 00059
Captive Fasteners
Figure 8-20 Fan Tray Holder Front Cover
Note: The front cover closes very easily when the fan tray card and air
filter are in position. If the cover does not close easily, check the fan tray
card to make sure it is recessed from the front of the fan tray holder.
7
Install a Fan
Tray Air Filter
with Handle
(Legacy)
The Install a Fan Tray Air Filter with Springs (Legacy) procedure is
complete.
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 Install a Fan Tray Air Filter with Handle (Legacy)
Step
Procedure
1
Hold the air filter with the metal window-pane side down with the handle
facing to the front.
OPS 00060
Handle
Figure 8-21 Air Filter with Handle
2
Page 8-30
Insert the air filter in the gap between the fan tray card and the top of the
fan tray holder.
Turin Networks
Release OPS4.0.x
Chapter 1 Replacing Existing Traverse Hardware
Install a Fan Tray Air Filter with Handle (Legacy)
Table 8-15 Install a Fan Tray Air Filter with Handle (Legacy) (continued)
Step
Procedure
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 card.
4
Lift the fan tray holder front cover into its closed position. Tighten the
captive fasteners to secure it.
OPS 00059
Captive Fasteners
Figure 8-22 Fan Tray Holder Front Cover
Note: The front cover closes very easily when the fan tray card and air
filter are correctly in position. If the cover does not close easily, check the
fan tray card to make sure it is recessed from the front of the fan tray
holder.
5
Release OPS4.0.x
The Install a Fan Tray Air Filter with Handle (Legacy) procedure is
complete.
Turin Networks
Page 8-31
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Install a Fan Tray Air Filter with Handle (Legacy)
Page 8-32
Turin Networks
Release OPS4.0.x
S ECTION 8HARDWARE U PGRADES
Chapter 2
Upgrade 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-33
• Required Equipment and Tools, page 8-34
• FIFT Upgrade Instructions, page 8-34
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.
Release OPS4.0.x
Turin Networks
Page 8-33
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Required Equipment and Tools
Required
Equipment and
Tools
The following equipment and tools are required for this upgrade:
• Front inlet fan tray holder
• Front inlet fan module
• Air 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:
Table 8-16 Front Inlet Fan Tray Holder Upgrade Instructions
Step
1
Page 8-34
Instructions
1
Check the New Fan Module, page 8-35 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 the
Traverse Installation and Commissioning Guide, Section 7—Hardware
Installation Procedures, Chapter 2—“Traverse System Hardware
Installation,” Install the Front Inlet Fan Tray Holder, page 7-9.
8
The Front Inlet Fan Tray Holder Upgrade Instructions are complete.
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.
Turin Networks
Release OPS4.0.x
Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray
Check the New Fan Module
Check the New
Fan Module
Check the new FIFT fan module as follows:
Table 8-17 New Fan Module Check
Step
Procedure
1
From the rear of the existing fan tray module, loosen the two thumbscrews
on the power cable cover (located on the left-hand side).
Power Cable Cover
Front
Figure 8-23 Existing Fan Tray Holder Back Panel
Release OPS4.0.x
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.
Turin Networks
Page 8-35
Node Operations and Maintenance Guide, Section 8: Hardware Upgrades
Check the New Fan Module
Page 8-36
Turin Networks
Release OPS4.0.x
S ECTION 9
A PPENDICES
S ECTION 9
Contents
Appendix A
Module Placement Planning and Guidelines
Module Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Traverse 1600 Module Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Traverse 2000 Card Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Traverse 600 Card Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Appendix B
Traverse SNMP v1/v2c Agent and MIBs
Supported Traverse SNMP MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Configure the Traverse SNMP Agent Parameters from TransNav . . . . . . . . . 9-22
Location of SNMP MIB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
List of Figures
Figure 9-1
Figure 9-2
Admin Menu—SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . 9-22
Node SNMP Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Table 9-1
Table 9-2
Table 9-3
Table 9-4
Table 9-5
Card Placement Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Redundancy Rules for GCM Types . . . . . . . . . . . . . . . . . . . . . . . 9-5
Traverse 1600 Card Placement Guidelines . . . . . . . . . . . . . . . . . 9-6
Traverse 2000 Card Placement Guidelines . . . . . . . . . . . . . . . . . 9-11
Traverse 600 Card Placement Guidelines . . . . . . . . . . . . . . . . . . 9-15
List of Tables
Release OPS4.0.x
Turin Networks
Page i
Node Operations and Maintenance Guide, Section 9 Appendices
Page ii
Turin Networks
Release OPS4.0.x
S ECTION 9APPENDICES
Appendix A
Module Placement Planning and Guidelines
Introduction
It is important to plan for card placement during installation, cabling, and start-up
activities for the Traverse system. The following tables provide card placement
guidelines for the Traverse shelf, including:
• Valid slot placement for GCM, optical, electrical, and VT/VC switching cards
• Equipment protection (1:N, where N=1, 2), working, and protection card
placement
• Unprotected card placement
Important: The Traverse system allows the network operator an
in-service upgrade capability (protection switching) to replace older cards
with newer cards with minimal traffic interruption for each card in any
1:N protection group.
Important: Do not place an electrical card (of another type) in the slot
directly to the left of any 10/100BaseTX-inclusive card:
• NGE
• NGE Plus
• Legacy Ethernet
Important: To ensure EMI protection and proper cooling, place one-slot
wide blank faceplates in any empty Traverse slots.
This appendix contains information on the following topics:
• Module Placement Guidelines, page 9-2
• Traverse 1600 Module Placement, page 9-6
• Traverse 2000 Card Placement, page 9-11
• Traverse 600 Card Placement, page 9-15
Release OPS4.0.x
Turin Networks
Page 9-1
Node Operations and Maintenance Guide, Section 9: Appendices
Module Placement Guidelines
Module
Placement
Guidelines
The following table provides guidelines for placement of modules in a Traverse shelf:
Table 9-1 Card Placement Guidelines
Card Type
Traverse
1600
Slot #s
Traverse
2000
Slot #s
Traverse
600
Slot #s
GCMA
and
GCMB
(slots 15
and 16)
GCMA
and
GCMB
(slots 19
and 20)
GCMA
and
GCMB
(slots 5
and 6)
Comments
(Front-shelf Perspective)
GCM
•
•
•
•
•
•
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/VCX
• GCM with OC-48/STM-16 plus
VTX/VCX
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 cards.
Electrical
•
•
•
•
•
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 card (of
another type) to the left of any
10/100BaseTX-inclusive card.
In a 1:1 equipment protection scheme with a
2-slot electrical connector card (ECM), either
the left- or right-adjacent card from the
protection card is the working card.
In a 1:2 equipment protection scheme, the
center card protects the left- and right-adjacent
working cards.
In an unprotected scheme, place cards in any
valid slot; the 2-slot DS3/E3 ECM provides
access to only the right-most card, so place an
optic card in the left-most slot. The 3-slot
DS3/E3 and 3-slot E1 ECM provides access to
only the center and right-most cards, so place
an optic card in the left-most slot.
(SONET network only) The DS3 Transmux
card 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 card protects all remaining adjacent cards.
Page 9-2
Turin Networks
Release OPS4.0.x
Appendix A Module Placement Planning and Guidelines
Module Placement Guidelines
Table 9-1 Card Placement Guidelines (continued)
Card Type
Traverse
1600
Slot #s
Traverse
2000
Slot #s
Traverse
600
Slot #s
1–12
1–16
1–4
Comments
(Front-shelf Perspective)
Ethernet (Next Generation)
NGE and NGE Plus:
• GbE [LX, SX] plus 10/100BaseTX
Combo [CEP]
• GbE TX plus GbE [LX or SX] plus
10/100BaseTX Combo [CEP]
Important: Do not place an electrical card (of
another type) to the left of any
10/100BaseTX-inclusive card.
In a 1:1 equipment protection scheme with a
2-slot Ethernet Protection ECM, either the
left- or right-adjacent card from the protection
card is the working card.
NGE only:
• GbE CWDM plus 10/100BaseTX
Combo
• GbE SX plus GbE CWDM plus
10/100BaseTX Combo
In an unprotected scheme, place cards in any
valid slot. The 2-slot Ethernet Protection ECM
provides access to only the right-most card, so
place an optic card in the left-most slot.
Use the following options when placing any
10/100BaseTX-inclusive cards in a Traverse
shelf with DS1, DS3/E3/EC-1 CC, DS3/EC-1
Transmux, or E1 cards:
• Place 10/100BaseTX-inclusive cards
directly to the left of DS1, DS3/E3/EC-1
CC, DS3/EC-1 Transmux, or E1 cards. An
OC-N/STM-N card or 1-slot wide blank
faceplate is not required if the
10/100BaseTX-inclusive cards are placed
to the left of electrical interface cards.
or
• Place an OC-N/STM-N card or a 1-slot
wide blank faceplate between the
10/100BaseTX and an electrical interface
card if the 10/100BaseTX-inclusive card is
placed to the right of the electrical interface
card.
Ethernet (Dual Slot GbE)
• 10GBASE-LR
1–14
1–18
• 10-port 1GbE card, no optics
1–12
1–16
Release OPS4.0.x
Turin Networks
n/a
None
Requires an SFP connector card. See Traverse
Installation and Commissioning Guide,
Section 2—Network Interface Specifications,
Chapter 1—“Fiber Optic Interface Cabling
Specifications,” GbE-10 SCM, Fiber
Assignments, and SFPs, page 2-4.
Page 9-3
Node Operations and Maintenance Guide, Section 9: Appendices
Module Placement Guidelines
Table 9-1 Card Placement Guidelines (continued)
Card Type
Traverse
1600
Slot #s
Traverse
2000
Slot #s
Traverse
600
Slot #s
1–14
1–18
1-4
None
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 cards require two slots
for placement. The left side of the
OC-192/STM-64 card is placed in an odd
numbered slot.
1–14
1–18
1-4
The VT/TU 5G Switch card supports 1:N
equipment protection where:
• N=1 to 9 in a Traverse 2000
(SONET network only)
• N=1 (SDH network only)
Comments
(Front-shelf Perspective)
SONET/SDH
•
•
•
•
OC-3/STM-1
OC-12/STM-4
OC-48/STM-16
OC-48/STM-16 with VTX/VCX
(legacy)
• OC-192/STM-64
VT/TU Switching
VT/TU 5G Switch
This card has no ECM requirement. One card
protects all adjacent cards.
Important: Place an OC-N/STM-N or 1-slot blank faceplate between any
10/100BaseTX-inclusive card and an electrical card (of another type), if the
10/100BaseTX-inclusive card is placed to the right of an electrical interface
card. A blank faceplate or OC-N/STM-N card is not required if the
10/100BaseTX-inclusive card is placed to the left of an electrical card.
Important: To ensure EMI protection and proper cooling, place one-slot
wide blank faceplates in any empty Traverse slots.
Turin recommends the following card 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) cards 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 cards next to the GCM cards. Place additional cards
toward the center of the shelf as required.
• Place OC-N/STM-N and GbE cards (optical cards) beginning in the right-most
available slot (starting at Traverse 1600 slot 14 or Traverse 2000 slot 18). Place
additional cards towards the center of the shelf as required.
Page 9-4
Turin Networks
Release OPS4.0.x
Appendix A Module Placement Planning and Guidelines
Module Placement Guidelines
The following table shows the redundancy rules for all GCM types:
Table 9-2 Redundancy Rules for GCM Types
Active GCM
1
Release OPS4.0.x
Standby GCM
GCM
GCM
GCM
GCM Enhanced | Universal1
GCM Enhanced | Universal1
GCM
GCM Enhanced | Universal
GCM Enhanced | Universal
GCM with OC-N/STM-N
GCM with OC-N/STM-N
GCM Enhanced or Universal environmental alarm function should not be used in this combination.
Turin Networks
Page 9-5
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 1600 Module Placement
Traverse 1600
Module
Placement
The following table provides card placement guidelines for the Traverse 1600 shelf.
Legend: Gray Fill=valid slot for card, No Fill=invalid card slot, Standby or Active
(S/A), Protecting (P), Working (W), Open (O).
Important: For standard electrical connector card (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-15 for ECM slot placement
details.
Important: For standard 10-port GbE card SFP connector card (SCM) placement, the
2-slot SCMs plug into slot n+1 of an n and n+1 slot combination. For example, in a
Traverse 1600 slot 11 and 12 combination, the 2-slot SCM plugs into the slot 12
backplane connectors.
Table 9-3 Traverse 1600 Card Placement Guidelines
Traverse 1600 Slot Numbers
Card Type
1
2
3
4
5
6
7
8
9
10
11
12
GCM
• GCM
• Enhanced GCM1
• GCM OC-12/STM-41
• GCM OC-48/STM-161
OPTICAL (Note: Optical cards are protected at the port level. There are no slot or card placement restrictions for optical working/protection.)
• OC-3/STM-1
• OC-12/STM-4
• OC-48/STM-16
W
• OC-192/STM-64
W
W
W
W
W
W
W
W
W
W
W
Slots 1/2
Slots 3/4
Slots 5/6
Slots 7/8
Slots 9/10
Slots 11/12
Slots 1/2
P
Slots 3/4
W/P
Slots 5/6
W/P
Slots 7/8
W/P
Slots 9/10
W/P
Slots 11/12
W/P
ETHERNET (Dual slot)
• 1-port 10GbE
• 10-port GbE
P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
ETHERNET (Single slot) 1:1 equipment protection with a 2-slot Ethernet Protection ECM
(Note: The Ethernet Combo cards have optical ports and electrical ports. The card placement restriction is due to the electrical ports.)
Page 9-6
Turin Networks
Release OPS4.0.x
W/P
W
Release OPS4.0.x
Table 9-3 Traverse 1600 Card Placement Guidelines (continued)
Traverse 1600 Slot Numbers
Card Type
NGE and NGE Plus:
• GbE [LX, SX] plus
10/100BaseTX Combo
[CEP]
• GbE TX plus GbE [LX or
SX] plus 10/100BaseTX
Combo [CEP]
2
3
4
5
6
7
8
9
10
11
12
P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W
W
W
W
W
W
W
W
W
13
14
15
16
NGE only:
• GbE CWDM plus
10/100BaseTX Combo
• GbE SX plus GbE CWDM
plus 10/100BaseTX Combo
ETHERNET (Single slot) unprotected with a 2-slot 10/100BaseT ECM
NGE and NGE Plus:
• GbE [LX, SX] plus
10/100BaseTX Combo
[CEP]
• GbE TX plus GbE [LX or
SX] plus 10/100BaseTX
Combo [CEP]
NGE only:
• GbE CWDM plus
10/100BaseTX Combo
• GbE SX plus GbE CWDM
plus 10/100BaseTX Combo
W
W
W
W
Page 9-7
Appendix A Module Placement Planning and Guidelines
Traverse 1600 Module Placement
Turin Networks
1
Traverse 1600 Slot Numbers
Card Type
1
2
3
4
5
6
7
8
9
10
11
12
ETHERNET (Single slot) unprotected with a 2-slot Ethernet (Protection) ECM
NGE and NGE Plus:
• GbE [LX, SX] plus
10/100BaseTX Combo
[CEP]
• GbE TX plus GbE [LX or
SX] plus 10/100BaseTX
Combo [CEP]
O
W/O
W/O
Turin Networks
W/O
W/O
W/O
W/O
W/O
W/O
W/O
W/O
W
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P
W/P/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
NGE only:
• GbE CWDM plus
10/100BaseTX Combo
• GbE SX plus GbE CWDM
plus 10/100BaseTX Combo
TDM 1:2 equipment protection with the corresponding ECM
•
•
•
•
DS1
DS3/E3/EC-1 CC
DS3/EC-1 Transmux
E1
W
W/P
TDM 1:1 equipment protection with a 2-slot ECM
•
•
•
•
DS1
DS3/E3/EC-1 CC
DS3/EC-1 Transmux
E1
W/P
W/P
TDM 1:1 equipment protection with a 3-slot ECM
Release OPS4.0.x
• DS3/E3/EC-1 CC
• DS3/EC-1 Transmux
• E1
W/P/O
W/P/O
TDM unprotected with the corresponding ECM
13
14
15
16
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 1600 Module Placement
Page 9-8
Table 9-3 Traverse 1600 Card Placement Guidelines (continued)
Release OPS4.0.x
Table 9-3 Traverse 1600 Card Placement Guidelines (continued)
Traverse 1600 Slot Numbers
Card Type
• DS1,
• E1
1
2
3
4
5
6
7
8
9
10
11
12
W
W
W
W
W
W
W
W
W
W
W
W
W/O
W/O
W
W/O
W
W
W/P
W/P
13
14
W/P
W/P
15
16
TDM unprotected with a 2-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.)
• 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
TDM unprotected with a 3-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.)
• 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
Turin Networks
VT/VC Switching 1:N equipment protection (Note: No ECM requirement with VT/VC switching cards.)
W/P
VT/TU 5G Switch
GCM with optics plus VTX
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
W/P
W/P
W/P
W/P
W/P
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
VT/VC Switching unprotected
VT/TU 5G Switch
2
GCM with optics plus VTX
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/MSP, UPSR/SNCP, or BLSR/MS-SPRing protection group.
Important: Place an OC-N or one-slot wide blank faceplate between any 10/100BaseTX-inclusive card and an electrical card (of
another type), if the 10/100BaseTX-inclusive card is placed to the right of an electrical interface card. A blank faceplate or OC-N card
is not required if the 10/100BaseTX-inclusive card is placed to the left of an electrical card.
Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling.
Page 9-9
Appendix A Module Placement Planning and Guidelines
Traverse 1600 Module Placement
2
Turin Networks
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 1600 Module Placement
Page 9-10
Release OPS4.0.x
Release OPS4.0.x
Traverse 2000
Card
Placement
The following table provides card placement guidelines for the Traverse 2000 shelf.
Legend: Gray Fill=valid slot for card, No Fill=invalid card slot, Standby or Active (S/A), Protecting (P), Working (W), Open
(O).
Important: For standard electrical connector card (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-15 for ECM slot placement details.
Important: For standard 10-port GbE card SFP connector card (SCM) placement, the 2-slot SCMs plug into slot n+1 of an
n and n+1 slot combination. For example, in a Traverse 1600 slot 11 and 12 combination, the 2-slot SCM plugs into the slot 12
backplane connectors.
Table 9-4 Traverse 2000 Card Placement Guidelines
Traverse 2000 Slot Numbers
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
GCM
GCM
Enhanced GCM1
GCM OC-12/STM-41
GCM OC-48/STM-161
OPTICAL (Note: Optical cards are protected at the port level. There are no slot or card placement restrictions for optical working/protection.)
• OC-3/STM-1
• OC-12/STM-4
• OC-48/STM-16
OC-192/STM-64
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
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
• 1-port 10GbE
Slots 1/2
P
Slots 3/4
W/P
Slots 5/6
W/P
Slots 7/8
W/P
Slots 9/10
W/P
Slots 11/12
W/P
Slots 13/14
W/P
Slots 15/16
W/P
Slots 17/18
W
• 10-port GbE
P
W/
P
W/
P
W/
P
W/
P
ETHERNET (Dual slot)
Page 9-11
W/
P
W/
P
W/
P
W/
P
W/
P
W/
P
W/
P
W/
P
W
W/
P
W
19
20
S/A
S/A
Appendix A Module Placement Planning and Guidelines
Traverse 2000 Card Placement
Turin Networks
Card Type
Traverse 2000 Slot Numbers
Card Type
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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
ETHERNET unprotected with a 2-slot 10/100BaseT ECM
NGE and NGE Plus:
• GbE [LX, SX] plus
10/100BaseTX Combo
[CEP]
• GbE TX plus GbE [LX or
SX] plus 10/100BaseTX
Combo [CEP]
W
W
W
W
Turin Networks
NGE only:
• GbE CWDM plus
10/100BaseTX Combo
• GbE SX plus GbE CWDM
plus 10/100BaseTX Combo
ETHERNET unprotected with a 2-slot Ethernet (Protection) ECM
NGE and NGE Plus:
• GbE [LX, SX] plus
10/100BaseTX Combo
[CEP]
• GbE TX plus GbE [LX or
SX] plus 10/100BaseTX
Combo [CEP]
O
W/
O
W/
O
W/
O
NGE only:
• GbE CWDM plus
10/100BaseTX Combo
• GbE SX plus GbE CWDM
plus 10/100BaseTX Combo
Release OPS4.0.x
TDM 1:2 equipment protection with corresponding ECM
W/
O
17
18
19
20
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 2000 Card Placement
Page 9-12
Table 9-4 Traverse 2000 Card Placement Guidelines (continued)
Release OPS4.0.x
Table 9-4 Traverse 2000 Card Placement Guidelines (continued)
Traverse 2000 Slot Numbers
Card Type
•
•
•
•
DS1
DS3/E3/EC-1 CC
DS3/EC-1 Transmux
E1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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
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/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
W
W
W
W
W
W
W
W
W
W
W
W
W/
O
W/
O
W/
O
W
17
18
W/
P
W/
P
19
20
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
• DS3/E3/EC-1 CC
• DS3/EC-1 Transmux
• E1
W/
P/O
W/
P/O
W/
P/O
TDM unprotected with the corresponding ECM
• DS1
• E1
W
W
W
TDM unprotected with a 2-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.)
• 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
TDM unprotected with a 3-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.)
• 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
W/
P
W/
P
W/
P
W/
P
W/
P
W/
P
VT/VC Switching with 1:N equipment protection (Note: No ECM requirement with VT/VC switching cards.)
Page 9-13
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
Appendix A Module Placement Planning and Guidelines
Traverse 2000 Card Placement
Turin Networks
TDM 1:1 equipment protection with a 3-slot ECM
Traverse 2000 Slot Numbers
Card Type
GCM with optics plus VTX2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
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
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
19
VT/VC Switching unprotected
VT/TU 5G Switch without
Equipment Protection
GCM with optics plus VTX2
Turin Networks
1
Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with a Enhanced GCM for GCM redundancy.
2
While the VTX can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1 APS/MSP, UPSR/SNCP, or BLSR/MS-SPRing
protection group.
Important: Place an OC-N or wide blank faceplate between any 10/100BaseTX-inclusive card and an electrical card (of another
type) if the 10/100BaseTX-inclusive card is placed to the right of an electrical interface card. A blank faceplate or OC-N card is not
required if the 10/100BaseTX-inclusive card is placed to the left of an electrical card.
Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling.
20
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 2000 Card Placement
Page 9-14
Table 9-4 Traverse 2000 Card Placement Guidelines (continued)
Release OPS4.0.x
Release OPS4.0.x
Traverse 600
Card
Placement
The following table provides card placement guidelines for the Traverse 600 shelf.
Legend: Gray Fill=valid slot for card, No Fill=invalid card slot, Standby or Active (S/A), Protecting (P), Working (W), Open
(O).
Important: For standard electrical connector card (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
the Traverse Installation and Commissioning Guide, Section 2—Network Interface Specifications for ECM slot placement
details.
Table 9-5 Traverse 600 Card Placement Guidelines
Traverse 600 Slot Numbers
Card Type
1
2
3
4
6
S/A
S/A
• GCM
• Enhanced GCM1
• GCM OC-12/STM-41
• GCM OC-48/STM-161
OPTICAL (Note: Optical cards are protected at the port level. There are no slot or card placement restrictions for optical
working/protection.)
• OC-3/STM-1
• OC-12/STM-4
• OC-48/STM-16
W
W
W
W
• OC-192/STM-64
(Note: Not available on the Traverse 600.)
ETHERNET (Dual slot)
(Note: Not available on the Traverse 600.)
ETHERNET (Single slot) 1:1 equipment protection with a 2-slot Ethernet Protection ECM
Page 9-15
Appendix A Module Placement Planning and Guidelines
Traverse 600 Card Placement
Turin Networks
GCM
5
Traverse 600 Slot Numbers
Card Type
NGE and NGE Plus:
• GbE [LX, SX] plus 10/100BaseTX Combo [CEP]
• GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo
[CEP]
1
2
3
4
P
W/P
W/P
W
W
W
W
NGE only:
• GbE CWDM plus 10/100BaseTX Combo
• GbE SX plus GbE CWDM plus 10/100BaseTX Combo
ETHERNET (Single slot) unprotected with a 2-slot 10/100BaseT ECM
Turin Networks
NGE and NGE Plus:
• GbE [LX, SX] plus 10/100BaseTX Combo [CEP]
• GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo
[CEP]
W
NGE only:
• GbE CWDM plus 10/100BaseTX Combo
• GbE SX plus GbE CWDM plus 10/100BaseTX Combo
ETHERNET (Single slot) unprotected with a 2-slot Ethernet (Protection) ECM
NGE and NGE Plus:
• GbE [LX, SX] plus 10/100BaseTX Combo [CEP]
• GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo
[CEP]
O
W/O
W/O
W
W
W/P
W/P
W
NGE only:
• GbE CWDM plus 10/100BaseTX Combo
• GbE SX plus GbE CWDM plus 10/100BaseTX Combo
TDM 1:2 equipment protection with the corresponding ECM
Release OPS4.0.x
•
•
•
•
DS1
DS3/E3/EC-1 CC
DS3/EC-1 Transmux
E1
5
6
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 600 Card Placement
Page 9-16
Table 9-5 Traverse 600 Card Placement Guidelines (continued)
Release OPS4.0.x
Table 9-5 Traverse 600 Card Placement Guidelines (continued)
Traverse 600 Slot Numbers
Card Type
1
2
3
4
W/P
W/P
W/P
W/P
W/P/O
W/P/O
W/P/O
W/P/O
W
W
W
W
5
6
TDM 1:1 equipment protection with a 2-slot ECM
•
•
•
•
DS1
DS3/E3/EC-1 CC
DS3/EC-1 Transmux
E1
TDM 1:1 equipment protection with a 3-slot ECM
• DS3/E3/EC-1 CC
• DS3/EC-1 Transmux
• DS1
• E1
TDM unprotected with a 2-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.)
• DS3/E3/EC-1 CC
• DS3/EC-1 Transmux
O
W/O
W/O
W
TDM unprotected with a 3-slot DS3/E3 ECM (Note: the card placement restriction is due to the electrical connector card.)
O
• DS3/E3/EC-1 CC
• DS3/EC-1 Transmux
W/O
W
W
VT/VC Switching with 1:N Equipment Protection (Note: No ECM requirement with VT/VC switching cards.)
VT/TU 5G Switch
W/P
2
W/P
W/P
W/P
W/P
W/P
W/P
W/P
VT/TU 5G Switch
W
W
W
W
OC-48/STM-16 with VTX
W
W
W
W
OC-48/STM-16 with VTX
VT/VC Switching without Equipment Protection
Page 9-17
Appendix A Module Placement Planning and Guidelines
Traverse 600 Card Placement
Turin Networks
TDM unprotected with the corresponding ECM
Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with a Enhanced
GCM for GCM redundancy.
2
While the VTX Switch can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1
APS/MSP, UPSR/SNCP, or BLSR/MS-SPRing protection group.
Important: Place an OC-N/STM-N or wide blank faceplate between any
10/100BaseTX-inclusive card and an electrical card (of another type) if the
10/100BaseTX-inclusive card is placed to the right of an electrical interface card. A blank
faceplate or OC-N/STM-N card is not required if the 10/100BaseTX-inclusive card is placed
to the left of an electrical card.
Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and
proper cooling.
Turin Networks
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 600 Card Placement
Page 9-18
1
Release OPS4.0.x
Release OPS4.0.x
Page 9-19
Appendix A Module Placement Planning and Guidelines
Traverse 600 Card Placement
Turin Networks
Turin Networks
Node Operations and Maintenance Guide, Section 9: Appendices
Traverse 600 Card Placement
Page 9-20
Release OPS4.0.x
S ECTION 9APPENDICES
Appendix B
Traverse 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:
n
Supported Traverse SNMP MIBs, page 9-21
n
Configure the Traverse SNMP Agent Parameters from TransNav, page 9-22
n
Location of SNMP MIB File, page 9-23
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®.
n
RFC 1213: System group of MIB-II
n
RFC 2737: Physical Entity table of Entity MIB, Version 2
n
RFC 2863: The Interfaces Group MIB used for physical Ethernet interfaces only,
the Interfaces and Extension Interfaces tables
n
Turin enterprise (proprietary) SNMP MIB:
– EMS Alert table
– Set of traps
All counters are copies of Traverse PM 24-hour counters and is consistent with the way
the TransNav MIBs support counters.
Release OPS3.1.x
Turin Networks
Page 9-21
Node Operations and Maintenance Guide, Section 9: Appendices
Configure the Traverse SNMP Agent Parameters from TransNav
Configure the
Traverse SNMP
Agent
Parameters
from TransNav
Turin supports an SNMP agent directly on the Traverse system. The Traverse SNMP
agent access is available on a physical node only; pre-provisioned 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
Page 9-22
Set through the CLI during node commissioning.
Turin Networks
Release OPS3.1.x
Appendix B Traverse SNMP v1/v2c Agent and MIBs
Location of SNMP MIB File
Read Community: An alphanumeric 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 alphanumeric character string parameters, there is a
corresponding Confirm parameter to check for matching string entry.
Write Community: An alphanumeric 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 alphanumeric 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 as follows:
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
Release OPS3.1.x
The Turin enterprise (proprietary) SNMP MIB (filename=ems.mib) file is located in
the same directory where you installed the server application.
Turin Networks
Page 9-23
Node Operations and Maintenance Guide, Section 9: Appendices
Location of SNMP MIB File
Page 9-24
Turin Networks
Release OPS3.1.x
I NDEX
Numerics
1 for 1 equipment protection
module placement, 9-1
1 for 2 equipment protection
module placement, 9-1
1 for N equipment protection
module placement, 9-1
10/100BaseTX
module placement
precaution statement, 8-18, 9-1
10/100BaseTX port
performance monitoring, 2-67
A
Access Identifier
test access, 5-2, 5-5
Activate software
protected modules, 7-31
unprotected modules, 7-34
Activate time, 7-22, 7-23, 7-25, 7-31, 7-37, 7-46, 7-65, 766, 7-68, 7-69
Activation
status, 7-24, 7-32, 7-66, 7-68
type, 7-31
Active Hop, 1-13, 1-16, 2-11, 2-13
Administrative state
card or port
lock, 4-20
unlock, 4-20
AID, see Access Identifier
Air filters
cooling function, 6-2
replacement, 6-7
Alarm
categories, 1-2
default
severities, 4-2
severity levels, 1-21
definitions, 1-5
filtering, 1-19
indication signal seconds
DS1 port, 2-20
list
HP-RFI, 1-55
management
customization, 1-7
profile
creation, 1-9
Release TR3.0.x
DS1 port, 1-10
DS3 port, 1-10
DS3⁄EC3 port, 1-10
E1 port, 1-10
E3 port, 1-10
EOS ctp, 1-10
EOS port, 1-10
GbE port, 1-10
LAG, 1-10
Mux, 1-10
probable cause, 1-8
SDH EOS ctp, 1-10
SDH EOS port, 1-10
SDH high order path, 1-10
SDH low order path, 1-10
SDH port, 1-10
server, 1-10
shelf, 1-10
SONET port, 1-10
SONET sts, 1-10
SONET vt, 1-10
synchronize, 1-11
recommended actions, 1-21
reporting, 1-2
hierarchy, 1-6
severity levels
default, 1-1
StickyMode, 1-20
types, 1-2
view, 1-6
Alarms
HP-SQM (port), 1-54
list
ACO, 1-23
ACO_CLEAR, 1-23
ADMINTASK, 1-23
AIRCOND, 1-23
AIRDRYR, 1-23
AIS-L, 1-23
AIS-P, 1-24
AIS-S, 1-24
AIS-V, 1-24
AIS-VC, 1-25
ALS, 1-25
ALS-TX-OFF, 1-25
APSAISCLEAR, 1-26
APS-AIS-P, 1-25
APSB, 1-26
APSBF, 1-26
Turin Networks
Index-1
Index
COM, 1-38
CONTROL, 1-39
CTS, 1-39
DBCRPT, 1-40
DBFAIL, 1-40
DBMIS, 1-40
DBRED, 1-40
DBSIGN, 1-41
DCCFAIL, 1-41
DOWN, 1-42
DQL, 1-42
DS1AIS, 1-42
DS1LOF, 1-42
DS1LOS, 1-42
DS1RAI, 1-43
DS3AIS, 1-43
DS3RAI, 1-43
DSR, 1-43
DTR, 1-43
E1AIS, 1-43
E1LOMCAS, 1-43
E1LOMCRC, 1-43
E1RAI, 1-44
E3 AIS, 1-44
E3 RAI, 1-44
EFMFAIL, 1-44
ENGINE, 1-44
ENGOPRG, 1-44
EQCOMM, 1-44
EQFRCSW, 1-44
EQINV, 1-45
EQLOCK, 1-45
EQMANSW, 1-45
EQMIS, 1-45
EQPT, 1-45
EQRMV, 1-46
ERFI-V, 1-46
EXER_SWITCH, 1-46
EXPLGS, 1-46
EXTA-REF1-ALM, 1-46
EXTA-REF2-ALM, 1-46
EXTA-REF3-ALM, 1-47
EXTA-REF4-ALM, 1-47
EXTB-REF1-ALM, 1-47
EXTB-REF2-ALM, 1-47
EXTB-REF3-ALM, 1-47
EXTB-REF4-ALM, 1-47
FANCOMM, 1-48
FANCOND, 1-48
FANFLTR, 1-48
FANRMV, 1-48
FEP, 1-48
FILE_UPLOAD, 1-48
APSCFGMIS, 1-26
APSCM, 1-26
APSDICLEAR, 1-28
APSIMP, 1-26
APSINC, 1-27
APSLOP, 1-27
APSLOPCLEAR, 1-27
APS-LOP-P, 1-25
APSLOSCLEAR, 1-27
APSMM, 1-27
APSPATHCLEAR, 1-27
APSPDI, 1-28
APSREL, 1-28
APS-SDBER-P, 1-25
APSSDCLEAR, 1-28
APS-SFBER-P, 1-25
APSSFCLEAR, 1-28
APSUNEQCLEAR, 1-28
APS-UNEQ-P, 1-26
APSWTR, 1-29
AU-AIS, 1-29
AU-LOP, 1-29
AUTHFAIL, 1-29
AUTOPRV, 1-29
AUTO-TX-ON, 1-30
BADPKTRX, 1-30
BATDSCHRG, 1-30
BATTERY, 1-30
BERSD-L, 1-31
BERSD-P, 1-32
BERSD-V, 1-33
BERSD-VC, 1-33
BERSF-L, 1-34
BERSF-P, 1-35
BERSF-V, 1-36
BERSF-VC, 1-36
BITSA-FRC, 1-36
BITSA-LOCK, 1-37
BITSA-MAN, 1-37
BITSB-FRC, 1-37
BITSB-LOCK, 1-37
BITSB-MAN, 1-37
BITSGEN, 1-37
BITSRBOC, 1-37
BLSR_NOT_SYNC, 1-37
BLSR_SYNC_UNKNOWN, 1-37
BOARDFAIL, 1-37
BPSIG, 1-38
CFGERR, 1-38
CLEAR, 1-38
CLFAIL, 1-38
CLFAN, 1-38
CLRLOOP, 1-38
Index-2
Turin Networks
Release TR3.0.x
Index
LINKFAIL, 1-60
LNKBCPTY, 1-60
LNKBLKCNT, 1-60
LOA, 1-62
LOCK_WORK1, 1-63
LOCK_WORK10, 1-63
LOCK_WORK11, 1-63
LOCK_WORK12, 1-63
LOCK_WORK13, 1-63
LOCK_WORK14, 1-64
LOCK_WORK2, 1-64
LOCK_WORK3, 1-64
LOCK_WORK4, 1-64
LOCK_WORK5, 1-64
LOCK_WORK6, 1-64
LOCK_WORK7, 1-65
LOCK_WORK8, 1-65
LOCK_WORK9, 1-65
LOCKOUT, 1-62
LOCKOUT-LPS, 1-63
LOF, 1-66
LOG, 1-66
LOGINFAIL, 1-67
LOGINSUCC, 1-67
LOGINTERM, 1-67
LOL, 1-67
LO-LBC, 1-62
LOM, 1-67
LOM-P, 1-67
LOM-V, 1-67
LO-OPR, 1-62
LO-OPT, 1-62
LOP, VC, 1-69
LOP, VT, 1-68
LOP-P, 1-68
LOS, 1-69
LO-TEMP, 1-62
LO-VCC, 1-62
LP-BERSD, 1-70
LP-BERSF, 1-70
LPBKEQPT, 1-70
LPBKFACILITY, 1-71
LPBKINBAND, 1-71
LPBKTERM, 1-71
LP-LOM, 1-71
LP-MND, 1-71
LP-PLM, 1-72
LP-RDI, 1-72
LP-RFI, 1-72
LP-RFICON, 1-72
LP-RFIPAY, 1-72
LP-RFISVR, 1-72
LP-SQM, 1-73
FIRDETR, 1-48
FIRE, 1-48
FLOOD, 1-48
FLOW-DEGRADED, 1-49
FLOW-LEARNED, 1-49
FLOWS-UNLEARNED, 1-49
FLOW-UNLEARNED, 1-49
FLOW-UNPROTECTED, 1-49
FOPR, 1-49
FOPT, 1-50
FORCE_ONLINE, 1-50
FORCED, 1-50
FORCED_ON_EAST, 1-51
FORCED_ON_PROT, 1-50
FORCED_ON_SECT1, 1-50
FORCED_ON_SECT2, 1-51
FORCED_ON_WEST, 1-51
FORCED_ON_WORK, 1-51
FUSE, 1-51
GENFAIL, 1-51
GFPLOF, 1-51
GIDERR, 1-52
GIDM, 1-52
H4-LOM, 1-52
HIAIR, 1-52
HIHUM, 1-52
HITEMP, 1-53
HIWTR, 1-53
HP-BERSD, 1-53
HP-BERSF, 1-54
HP-LOM, 1-54
HP-MND, 1-54
HP-PLM, 1-54
HP-RDI, 1-55
HP-RFICON, 1-55
HP-RFIPAY, 1-55
HP-RFISVR, 1-55
HP-SQM, 1-54
HP-TIM, 1-55
HP-UNEQ, 1-56
HWFAULT, 1-56
IDLE, 1-56
INCOMPATSW, 1-56
INDICATION, 1-57
INTRUDER, 1-56
KBYTE, 1-57
LBC, 1-59
LBCNRML, 1-59
LCAS-REM, 1-59
LCAS-RES, 1-59
LEAK, 1-59
LFD, 1-59
LINK_FRCD_DIS, 1-60
Release TR3.0.x
Turin Networks
Index-3
Index
PLCPRFI, 1-80
PLCR, 1-80
PLCT, 1-80
PLINESQL, 1-81
PLM, 1-81
PLM-P, 1-81
PLM-V, 1-81
PLM-VC, 1-81
PMCFG, 1-82
PMDATALOST, 1-82
POWER, 1-82
PS, 1-82
PUMPFAIL, 1-82
PWFAIL-A, 1-82
PWFAIL-B, 1-82
PWR-48, 1-82
QEFAIL, 1-82
RECTFAIL, 1-82
RECTHIGH, 1-83
RECTLOW, 1-83
REMOTE-LINKFAIL, 1-83
RESOURCE_MISMATCH, 1-83
RFICON, 1-86
RFICON-V, 1-86
RFICON-VC, 1-86
RFI-L, 1-84
RFI-P, 1-84
RFIPAY, 1-87
RFIPAY-V, 1-87
RFIPAY-VC, 1-87
RFISVR, 1-88
RFISVR-V, 1-88
RFISVR-VC, 1-88
RFI-V, 1-85
RFI-VC, 1-85
RLSD, 1-89
RMLF, 1-83
RS-TIM, 1-89
RTS, 1-89
SENSORFAIL, 1-89
SERVER_LOGINFAIL, 1-89
SERVER_ROLE, 1-89
SETOPER, 1-89
SFO, 1-89
SFPMIS, 1-90
SFPRMV, 1-90
SHELFMIS, 1-90
SMOKE, 1-90
SQLCHTBL, 1-90
SQM, 1-90
SQM-P, 1-90
SQM-V, 1-91
SSF, 1-91
LP-TIM, 1-73
LP-UNEQ, 1-73
LSDBOVFL, 1-73
LSM, 1-73
LWBATVG, 1-73
LWFUEL, 1-73
LWHUM, 1-73
LWPRES, 1-73
LWTEMP, 1-73
LWWTR, 1-73
MAN_ON_PROT, 1-74
MAN_ON_WORK, 1-74
MAN-TX-OFF, 1-74
MAN-TX-ON, 1-74
MANUAL, 1-74
MAXAGE, 1-74
MBD-P, 1-74
MISC, 1-74
MND-V, 1-74
MPU_BATTERY_A, 1-75
MPU_BATTERY_B, 1-75
MS-AIS, 1-75
MS-BERSD, 1-75
MS-BERSF, 1-76
MS-RDI, 1-76
MSSP_NOT_SYNC, 1-76
MSSP_SYNC_UNKNOWN, 1-76
MULT_PRIMARY_SERVER, 1-76
NEIGHSC, 1-76
NETSYNC, 1-77
NEWLSA, 1-77
NO_OUTPUT, 1-77
NO_PRIMARY_SERVER, 1-77
NODEEQMIS, 1-77
NODEMIS, 1-77
NODESYNC, 1-78
NO-REMOTE-LCAS, 1-78
NPM, 1-78
OPENDR, 1-78
OPR, 1-78
OPT, 1-78
OPTNORM, 1-78
ORPNORM, 1-78
OVERTEMP, 1-79
OVERVOLTAGE_A, 1-79
OVERVOLTAGE_B, 1-79
PCASQLCH, 1-79
PDI-n (1, 1-80
PDI-n (n, 1-79
PDI-n (n>4), 1-80
PKTRETX, 1-80
PLC, 1-80
PLCPLOF, 1-80
Index-4
Turin Networks
Release TR3.0.x
Index
SVC_ERROR, 1-91
SW_UPG, 1-92
SW_UPG_PROG, 1-92
SWCRPT, 1-91
SWERR, 1-91
SWITCH, 1-91, 1-92
SWITCH_TO_PROT, 1-91
SWITCH_TO_SECT1, 1-92
SWITCH_TO_SECT2, 1-92
SWMIS, 1-92
SYNCFAIL, 1-93
SYSREF, 1-92, 1-93
T2OOF, 1-93
T2XBIT, 1-93
TA200_COM, 1-93
TA200_PM13E_G747FESmry, 1-94
TA200_PM13E_G747OOFSmry, 1-94
TCA, 1-95
TEMP, 1-95
TEMPCRIT, 1-95
TEMPWARN, 1-95
TIM, 1-95
TIMEDOUT, 1-96
TIMEOUTWARN, 1-96
TIM-P, 1-95
TIM-S, 1-96
TIM-V, 1-96
TIU-V, 1-96
TLC, 1-97
TLCR, 1-97
TLCT, 1-97
TOOMANYEVENTS, 1-97
TOPOMIS, 1-97
TOXIC, 1-97
TSSALM, 1-100
TSS-EXTA-OOB-A, 1-97
TSS-EXTA-OOB-B, 1-97
TSS-EXTB-OOB-A, 1-97
TSS-EXTB-OOB-B, 1-97
TSS-FRC, 1-98
TSS-FREERUN-GCMA, 1-98
TSS-FREERUN-GCMB, 1-98
TSSGEN, 1-100
TSS-HOLDOVER-GCMA, 1-98
TSS-HOLDOVER-GCMB, 1-98
TSS-LINE1-OOB-GCMA, 1-98, 1-99
TSS-LINE1-OOB-GCMB, 1-98
TSS-LINE2-OOB-GCMA, 1-98
TSS-LINE2-OOB-GCMB, 1-98
TSS-LINE3-OOB-GCMA, 1-99
TSS-LINE3-OOB-GCMB, 1-99
TSS-LINE4-OOB-GCMB, 1-99
TSS-LOCK, 1-99
TSS-MAN, 1-99
Release TR3.0.x
TSSREF, 1-100
TSS-REF1-ALM, 1-99
TSS-REF2-ALM, 1-99
TSS-REF3-ALM, 1-99
TSS-REF4-ALM, 1-100
TSS-REFL-GCMA, 1-100
TSS-REFL-GCMB, 1-100
TSS-REFS, 1-100
TSSSETS, 1-100
TSS-SSM, 1-100
TU-AIS, 1-24, 1-101
TU-LOP, 1-101
TX-OFF-LI, 1-101
TX-ON-LI, 1-101
UNDERVOLTAGE_A, 1-102
UNDERVOLTAGE_B, 1-102
UNEQ, 1-102
UNEQ-P, 1-102
UNEQ-V, 1-103
UNEQ-VC, 1-103
UP, 1-103
VCC, 1-103
VENTFAIL, 1-103
WARMREBOOT, 1-103
WLMIS, 1-103
X86_ABORT, 1-104
X86_CRC, 1-104
XPT-FAIL-RX, 1-104
XPT-FAIL-TX, 1-104
XPTRX, 1-104
XPTTX, 1-104
B
Background block errors
LO VC3 path, 2-47
LO VC3 path, far end, 2-49
SDH port–MS, 2-51
SDH port–MS, far end, 2-54
SDH port–RS, 2-50
VC11 path, 2-55
VC11 path, far end, 2-57
VC12 path, 2-55
VC12 path, far end, 2-57
VC3 path, 2-47
VC3 path, far end, 2-49
VC4 path, 2-47
VC4 path, far end, 2-49
Backward compatibility
software, 7-4, 7-51, 8-2
Base path, 7-13, 7-57
Bulk service activation
unavailable resources, 1-110
Turin Networks
Index-5
Index
C
Capacity monitoring
intervals, 2-15
parameters
SONET, 2-37
print data, 2-15
refresh values, 2-15
reset counters, 2-15
samples, 2-15
save data, 2-15
SDH section, 2-59
SONET section, 2-37
threshold crossing alert
number generated, 2-4
VT/TU data
viewing, 2-15
Captive fasteners
PDAP-2S, 6-14
PDAP-4S, 6-20
Circuit breaker
PDAP-2S
replacing, 6-11
toggle switch, 6-12
Cleaning MPX connectors, 8-14
Clear
activation time, 7-25, 7-68
CLI
commands
conventions, 6-24
CLI node commands
exec node database backup, 6-24
Coding violations
DS1 port, 2-20, 2-21
DS3 port, 2-23
(CBit), 2-24
(CBit), far end, 2-25
(PBit), 2-23
Line
EC1 port, 2-26
Line, far-end
EC1 port, 2-27
Section
EC1 port, 2-26
SONET line, 2-29
SONET line, far end, 2-31
SONET path, 2-33
SONET path, far end, 2-34
SONET section, 2-29
SONET VT path, 2-35
SONET VT path, far end, 2-36
Compatibility
alarms, 7-4, 7-51, 8-2
product matrix, 7-4, 7-51, 8-2
Index-6
replacement modules, 7-4, 7-51, 8-2
software, 7-4, 7-51, 8-2
software version, 7-4, 7-51, 8-2
Connectors
cleaning, 8-14
Controlled slip seconds
DS1 port, 2-21
DS1 port, far end, 2-22
Counters, resetting, see Performance monitoring
Creating
alarm profiles, 1-9
PM templates, 2-2
Current SW version, 7-24, 7-25, 7-32, 7-67, 7-68
CVFE
coding violations, far end–line, 2-27
D
Deactivate Ethernet service, 7-44
Default
alarm and event severity levels, 1-1, 1-21
severities
alarms, 4-2
DFAD, see Dual facility access digroup
Diagnostics
alarm cut-off, 4-21
environmental alarm conditions, 4-1
LED lamp test, 4-21
loopback tests, 4-11
power on self test, 4-21
transmit and receive signal levels, 4-3, 4-7
Download
archive
from Infocenter, 7-3, 7-10, 7-50, 7-53
time by module, 7-15, 7-59
DS1
facility loopback, 4-13
port alarm profile, 1-10
DS1 port
alarm profile, 1-10
performance monitoring, 2-20
FE CCS_P, 2-22
FE ES_L, 2-21
FE ES_P, 2-21
FE FC_P, 2-22
FE SEF_P, 2-22
FE SES_P, 2-22
FE UAS_P, 2-22
NE AISS_P, 2-20
NE CSS_P, 2-21
NE CV_L, 2-20
NE CV_P, 2-20, 2-21
NE ES_L, 2-20
NE ES_P, 2-20
Turin Networks
Release TR3.0.x
Index
NE FC_L, 2-21
NE LOSS_L, 2-20
NE SAS_P, 2-21
NE SES_L, 2-20
NE SES_P, 2-20
NE UAS_P, 2-21
DS3
facility loopback, 4-13
DS3 CC
facility loopback tests, 4-13
DS3 port
alarm profile, 1-10
performance monitoring, 2-23
FE CVC-P (CBit), 2-25
FE ESC-P (CBit), 2-25
FE FC-P (PBit), 2-25
FE SESC-P (CBit), 2-25
FE UASC-P (CBit), 2-25
NE CVC-P (CBit), 2-24
NE CV-L, 2-23
NE CV-P (PBit), 2-23
NE ESC-P (CBit), 2-24
NE ES-L, 2-23
NE ES-P (PBit), 2-23
NE FC-P (PBit), 2-24
NE SESC-P (CBit), 2-24
NE SES-L, 2-23
NE SES-P (PBit), 2-23
NE UASC-P (CBit), 2-24
NE UAS-P (PBit), 2-23
DS3/E3/EC-1
12-port, 8-9, 9-2
24-port, 8-9, 9-2
module placement, 8-9, 9-2
DS3/EC-1
Transmux, 8-9, 9-2
DS3⁄EC3 port
alarm profile, 1-10
Dual facility access digroup
test access point, 5-2
E
E1 port
alarm profile, 1-10
facility loopback, 4-14
facility loopback tests, 4-14
performance monitoring, 2-40
terminal loopback, 4-14
E3 port
alarm profile, 1-10
facility loopback, 4-14
tests, 4-14
performance monitoring, 2-43
Release TR3.0.x
terminal loopback, 4-14
EAM, see Environmental Alarm Module
EC1 port
performance monitoring, 2-26
EC-3
terminal loopback tests, 4-13
Electrical and optical signals
monitoring, 2-1
Electrostatic discharge protection, 8-4
EMS
service error codes, 1-107, 1-109
software compatibility, 8-2
EMSI
mux, 2-8
Environmental Alarm Module
guides, 6-22
plastic standoff
replacing, 6-21
Environmental alarms
observing
incorrect conditions, 4-1
symptom, incorrect input/output, 4-2
EOS
ctp
alarm profile, 1-10
performance monitoring
GFP FCS DISCARDS, 2-62
RX BROADCAST, 2-62
RX BYTES, 2-62, 2-63
RX FRAMES, 2-62
RX MTU DISCARDS, 2-63
RX MULTICAST, 2-62
RX UNICAST, 2-62
TX BROADCAST, 2-62
TX BYTES, 2-62
TX DISCARDS, 2-62
TX FRAMES, 2-62
TX UNICAST, 2-62
port
alarm profile, 1-10
Equipment protection
module placement
1 for 1, 9-1
1 for 2, 9-1
1 for N, 9-1
Equipped state
card or port
equipped, 4-20
non-equipped, 4-20
Error codes
EMS, 1-107, 1-109
Errored blocks
LO VC3 path, 2-46
Turin Networks
Index-7
Index
LO VC3 path, far end, 2-48
SDH port–MS, 2-51
SDH port–MS, far end, 2-53
SDH port–RS, 2-50
VC11 path, 2-55
VC11 path, far end, 2-57
VC12 path, 2-55
VC12 path, far end, 2-57
VC3 path, 2-46
VC3 path, far end, 2-48
VC4 path, 2-46
VC4 path, far end, 2-48
Errored seconds
DS1 port, 2-20
far end, 2-21
DS1 port, far end, 2-21
DS3 port, 2-23
DS3 port (CBit), 2-24
far end, 2-25
DS3 port (PBit), 2-23
Line, EC1 port, 2-26
Line, far end
EC1 port, 2-27
LO VC3 path, 2-46
far end, 2-48
SDH port–MS, 2-51
far end, 2-53
SDH port–RS, 2-50
Section
EC1 port, 2-27
SONET line, 2-30
far end, 2-31
SONET path, 2-33
SONET path, far end, 2-34
SONET section, 2-29
SONET VT path, 2-35
far end, 2-36
VC11 path, 2-55
far end, 2-57
VC12 path, 2-55
far end, 2-57
VC3 path, 2-46
far end, 2-48
VC4 path, 2-46
far end, 2-48
ESFE
errored seconds
far end, line, 2-27
Ethernet
dual-slot, 9-6, 9-11, 9-15
LEDs, 3-11, 3-12
module placement, 9-6
performance monitoring
Index-8
RX, 2-68
RX ALIGNMENT ERR, 2-69
RX BROADCAST, 2-68
RX BYTES, 2-69, 2-70
RX BYTES BAD, 2-69
RX DELAY DISCARDS, 2-69
RX DISCARDS, 2-69
RX FCS ERR, 2-69
RX FRAMES, 2-68
RX MTU DISCARDS, 2-69
RX MULTICAST, 2-68
RX NO DELIMITER, 2-68
RX PAUSE, 2-69
RX PKT > 1518, 2-68
RX PKT 1024-1518, 2-68
RX PKT 128-255, 2-68
RX PKT 256-511, 2-68
RX PKT 512-1023, 2-68
RX PKT 64, 2-68
RX PKT 65-127, 2-68
RX UNICAST, 2-68
TX BROADCAST, 2-67
TX BYTES, 2-69, 2-70
TX BYTES BAD, 2-69
TX DEFERRED FRAMES (10/100 only), 2-69
TX DISCARDS, 2-69
TX EXCESSIVE COLL (10/00 only), 2-70
TX FRAMES, 2-67
TX LATE COLL (T10/00 only), 2-70
TX MULTICAST, 2-62, 2-67
TX MULTIPLE COLL (10/100 only), 2-69
TX PAUSE, 2-69
TX PKT > 1518, 2-67
TX PKT 1024-1518, 2-67
TX PKT 128-255, 2-67
TX PKT 256-511, 2-67
TX PKT 512-1023, 2-67
TX PKT 64, 2-67
TX PKT 65-127, 2-67
TX SINGLE COLL (10/100 only), 2-69
TX UNICAST, 2-67
performance parameters, 2-61
protection ECM, 9-6
services
deactivate, 7-44
unprotected with 10⁄100BaseT ECM, 9-7, 9-12, 9-16
unprotected with Ethernet (protection) ECM, 9-8, 912, 9-16
Ethernet port
terminal loopbacks, 4-15
Event
categories, 1-2
default severity levels, 1-21
Turin Networks
Release TR3.0.x
Index
logs, 1-2
recommended actions, 1-21
reporting, 1-2
severity levels
default, 1-1
types, 1-2
F
Facility access digroup
test access point, 5-2
Facility loopback
DS1, 4-12
DS3, 4-12
Facility payload loopback
DS1, 4-13
DS3, 4-13
E1, 4-14
E3, 4-14
FAD, see Facility access digroup
Failure counts
DS1 port, 2-21
DS1 port, far end, 2-22
DS3 port (PBit), 2-24
DS3 port (PBit), far end, 2-25
EC1 port, 2-26
Line, far end
EC1 port, 2-28
LO VC3 path, 2-47
LO VC3 path, far end, 2-49
SDH port–MS, 2-52
SDH port–MS, far end, 2-54
SONET line, 2-30
SONET line, far end, 2-32
VC11 path, 2-56
VC11 path, far end, 2-58
VC12 path, 2-56
VC12 path, far end, 2-58
VC3 path, 2-47
VC3 path, far end, 2-49
VC4 path, 2-47
VC4 path, far end, 2-49
Fan
fan tray and module, 6-1
maintenance
air filter, 6-2
front inlet fan tray module, 6-1
speeds, 6-2
tray air filters, 6-2
replacing, 6-7
tray holder LEDs, 3-4, 3-5
tray module
replacing, 8-22, 8-24, 8-27
Release TR3.0.x
upgrade to FIFT, 8-33
Fault management
customization, 1-7
viewing alarms, 1-17
FC
failure count, line, 2-26
FCFE
failure count, line, 2-28
Fiber optic
cabling, 8-15, 8-16
Filtering alarms, 1-19
Filters
air, 6-2
Force switch, 7-29, 7-33
Front inlet tray fan
upgrade, 8-33
Fuse
replacing
PDAP-2S, 6-10, 6-12
PDAP-4S, 6-19
G
GbE
port
alarm profile, 1-10
performance monitoring, 2-67
GCM
alarm LEDs, 3-9
list, 8-12, 9-5
module placement, 9-6
Power On Self Test (POST), 4-21
redundancy rules, 8-12, 9-5
status
active⁄standby, 7-22, 7-65
protection, 7-22, 7-65
with VTX/VCX, 8-9, 9-2
GFP FCS DISCARDS
EOS port, 2-62
GMT
fuse block
PDAP-2S, 6-12
PDAP-4S, 6-19
replacing fuse
PDAP-2S, 6-12
PDAP-4S, 6-19
Guides
EAM, 6-22
PDAP-2S LED module, 6-15
PDAP-4S LED module, 6-20
Turin Networks
Index-9
Index
H
Hierarchy
alarms, 1-6
I
Interval
capacity monitoring, 2-15
performance monitoring, 2-9, 2-12
IP address
node-ip, 9-22
L
LEDs
electrical module port, 3-10
Ethernet, 3-11, 3-12
fan tray holder, 3-4, 3-5
GCM
alarm, 3-9
power and standby, 8-13
module, 3-7
status, 3-1
optical modules, 3-11
PDAP, 3-2
PDAP-2S, 3-2
PDAP-4S, 3-2
power and standby, 3-8
status
Light emitting diodes, see LEDs
Line
CVFE (coding violations, far end), 2-27
FC (failure count), 2-26
FC (failure counts, far end), 2-28
SESFE (severely errored seconds, far end), 2-27
UASFE (unavailable seconds, far end), 2-28
LO VC3 path
performance monitoring
BBE-LP, 2-47
EB-LP, 2-46
ES-LP, 2-46
FC-LP, 2-47
FE BBE-LP, 2-49
FE EB-LP, 2-48
FE ES-LP, 2-48
FE FC-LP, 2-49
FE SES-LP, 2-48
FE UAS-LP, 2-49
NPJC-DET-LP, 2-48
NPJC-GEN-LP, 2-48
PPJC-DET-LP, 2-47
PPJC-GEN-LP, 2-48
SES-LP, 2-47
UAS-LP, 2-47
Index-10
Loopback
facility
DS1, 4-12
DS3, 4-12
Loopback tests, 4-11
description, 4-11
DS3 CC facility, 4-13
E1 facility, 4-14
E1 terminal, 4-14
E3 facility, 4-14
E3 terminal, 4-14
EC-3 terminal, 4-13
Ethernet terminal, 4-15
faciity
DS3/EC-1, 4-12
facility
DS1 facility, 4-12
DS3 CC, 4-12
DS3 TMUX, 4-12
E1, 4-12
E3, 4-12
EC1, 4-12
SDH facility, 4-17
SDH terminal, 4-17
SONET facility, 4-17
SONET terminal, 4-17
STM-1E terminal, 4-13
terminal
DS1, 4-12
DS3, 4-12
DS3 CC, 4-12
DS3 TMUX, 4-12
EC1, 4-12
Loss of signal seconds
DS1 port, 2-20
M
Maintenance
alarm board
PDAP-4S, 6-20
fan tray air filter, 6-2
replacement, 6-7
fuse
PDAP-2S, 6-10, 6-12
PDAP-4S, 6-19
PDAP-2S
replace circuit breaker, 6-11
PDAP-2S alarm board, 6-14
PDAP-4S TPA fuse, 6-17
replacing EAM, 6-21
routine, shelf, 6-1
Management System
event logs, 1-2
Turin Networks
Release TR3.0.x
Index
login, 7-51
verify software version, 7-19, 7-63, 8-3
Measured
SFP optic port
supply voltage, 2-28, 2-71
temperature, 2-28, 2-71
TX bias current, 2-28, 2-71
TX input power, 2-28, 2-71
TX output power, 2-28, 2-71
Module
GCM list, 8-12, 9-5
inserting, 8-4
placement
planning guidelines, 9-1
power and standby LEDs, 3-8
preparation
removal and replacement, 8-6
replacing, 8-1, 8-4, 8-33
software
download times, 7-15, 7-59
software version compatibility, 7-4, 7-51, 8-2
Module placement
equipment protection
1 for 1, 9-1
1 for 2, 9-1
1 for N, 9-1
10/100BaseTx-inclusive, 9-1
Monitoring
performance, 2-1
VT/TU capacity, 2-1
MPX connectors
cleaning, 8-14
cleaning material, 7-3, 8-4
inspection, 8-14
Multiplex section
performance monitoring
BBE-MS, 2-51
EB-MS, 2-51
ES-MS, 2-51
FC-MS, 2-52
FE BBE-MS, 2-54
FE EB-MS, 2-53
FE ES-MS, 2-53
FE FC-MS, 2-54
FE UAS-MS, 2-53
PSCP-MS, 2-52
PSCW-MS, 2-52
PSDP-MS, 2-52
PSDW-MS, 2-52
SES-MS, 2-51
UAS-MS, 2-51
Mux
alarm profile, 1-10
Release TR3.0.x
EMSI, 2-8
N
Negative pointer justifications detected
LO VC3 path, 2-48
VC11 path, 2-56
VC12 path, 2-56
VC3 path, 2-48
VC4 path, 2-48
Negative pointer justifications generated
LO VC3 path, 2-48
VC11 path, 2-56
VC12 path, 2-56
VC3 path, 2-48
VC4 path, 2-48
Node
ID, 9-22
IP, 9-22
IP address, 9-22
O
Operational state
card or port
disabled, 4-20
enabled, 4-20
Optic
module placement, 9-6
modules, 8-10, 9-4
Optical power specifications, 4-4
P
Password, 7-14, 7-58
PDAP-15A
replace GMT fuse, 6-10
PDAP-2S
see Power Distribution and Alarm Panel
captive fasteners, 6-14
circuit breaker, 6-12
GMT
fuse block, 6-12
LED
module, 6-15
LEDs, 3-2
replace circuit breaker, 6-11
replacing
alarm board, 6-14
PDAP-4S
see Power Distribution and Alarm Panel
captive fasteners, 6-20
GMT
fuse block, 6-19
LED module guides, 6-20
Turin Networks
Index-11
Index
LEDs, 3-2
replacing
alarm board, 6-20
TPA fuse, 6-17
TPA fuse, 6-18
Performance monitoring, 2-1
10/100BaseTX port, 2-67
DS1 port, 2-20
DS3 port, 2-23
E1 port, 2-40
E3 port, 2-43
EC1 port, 2-26
FE BBE_P
E1 port far end, 2-42
FE CV-P
E3 port near end, 2-45
FE EB_P
E1 port far end, 2-42
E3 port near end, 2-45
FE ES_L
E1 port far end, 2-42
FE ES_P
E1 port far end, 2-42
E3 port near end, 2-45
FE FC_P
E1 port far end, 2-42
FE SES_P
E1 port far end, 2-42
E3 port near end, 2-45
FE UAS_P
E1 port far end, 2-42
E3 port near end, 2-45
GbE port, 2-67
intervals, 2-9, 2-12
NE AISS_P
E1 port near end, 2-41
NE BBE_P
E1 port near end, 2-41
E3 port near end, 2-43
NE BBER_P
E1 port near end, 2-41
E3 port near end, 2-44
NE CV_L
E1 port near end, 2-40
E3 port near end, 2-43
NE CV-P (PBit)
E3 port near end, 2-43
NE EB_P
E1 port near end, 2-40
E3 port near end, 2-43
NE ES_L
E1 port near end, 2-40
E3 port near end, 2-43
Index-12
NE ES_P
E1 port near end, 2-41
E3 port near end, 2-43
NE ESR_P
E1 port near end, 2-41
E3 port near end, 2-44
NE FAS_L
E1 port near end, 2-40
NE FC_L
E1 port near end, 2-40
NE FC_P
E3 port near end, 2-44
NE LOSS_L
E1 port near end, 2-40
E3 port near end, 2-43
NE SES_L
E1 port near end, 2-40
E3 port near end, 2-43
NE SES_P
E1 port near end, 2-41
E3 port near end, 2-44
NE SESR_P
E1 port near end, 2-41
E3 port near end, 2-44
NE UAS_P
E1 port near end, 2-41
E3 port near end, 2-44
printing PM data, 2-10, 2-12
refreshing PM values, 2-10, 2-12
reports, generating
resetting PM counters
samples, 2-9, 2-12
saving data, 2-10, 2-12
SDH path, 2-46, 2-55
SDH port, 2-50
services
SONET STS, 2-33
SONET VT, 2-35
services (SONET VT), 2-35
SONET port, 2-29
template
synchronize, 2-4
templates, 2-2
timing
refresh time, 2-8
samples, 2-8
viewing port PM data, 2-9, 2-15
viewing service PM data, 2-11, 2-13
VT/TU capacity
viewing, 2-15
Performance parameters
Ethernet, 2-61
SDH, 2-39
Turin Networks
Release TR3.0.x
Index
SONET, 2-19
Periodic conditions
monitoring, 2-1
Plastic standoff, see Environmental Alarm Module
PM
see Performance monitoring
Pointer justifications difference
VC11 path, 2-57
VC12 path, 2-57
Pointer justifications seconds detected
VC11 path, 2-56
VC12 path, 2-56
Pointer justifications seconds generated
VC11 path, 2-57
VC12 path, 2-57
Port
number
TransAccess 200 Mux, 9-23
Positive pointer justifications detected
LO VC3 path, 2-47
VC11 path, 2-56
VC12 path, 2-56
VC3 path, 2-47
VC4 path, 2-47
Positive pointer justifications generated
LO VC3 path, 2-48
VC11 path, 2-56
VC12 path, 2-56
VC3 path, 2-48
VC4 path, 2-48
Power and standby LEDs, 3-8
Power Distribution and Alarm Panel
alarm board
replacing, 6-14
LEDs, 3-2
replacing
circuit board, 6-20
circuit breaker, 6-11
TPA fuse, 6-17
Power On Self Test (POST) for GCM, 4-21
Probable Cause, 1-19
Problems, see Symptoms
Procedures (GUI)
clear protection switch, 7-42
perform a forced switch, 7-39
perform a manual switch, 7-41
software upgrade
activate GCM, 7-36, 7-37, 7-65, 7-69
Protected modules, 7-31
Protection
electrical modules, 8-9, 9-2
Ethernet, 8-10, 9-3
groups, 7-31
Release TR3.0.x
switch
forced, 7-29
release, 7-29
Protection switch
forced, 7-33
release, 7-33
Protection switch count
protecting
SDH port–MS, 2-52
SONET line, 2-31
working
SDH port–MS, 2-52
SONET line, 2-30
Protection switch duration
protecting
SDH port–MS, 2-52
SONET line, 2-31
working
SDH port–MS, 2-52
SONET line, 2-31
R
Read community
TransAccess 200 Mux, 9-23
Recommended actions
alarms and events, 1-21
non-alarmed symptoms, 4-2
Refreshing PM values, 2-10, 2-12
Regenerator section
performance monitoring
BBE-RS, 2-50
EB-RS, 2-50
ES-RS, 2-50
SES-RS, 2-50
Release path, 7-16, 7-60
Release protection switch, 7-29, 7-33
Remote test access, 5-3
Remote test unit
test access
Replacing
alarm board
PDAP-2S, 6-14
PDAP-4S, 6-20
circuit breaker
PDAP-2S, 6-11
EAM circuit board, 6-21
fan tray module, 8-22, 8-24, 8-27
fuse
PDAP-2S, 6-10, 6-12
PDAP-4S, 6-19
GCM
power and standby LEDs, 8-13
modules, 8-1, 8-33
Turin Networks
Index-13
Index
compatibility, 7-4, 7-51, 8-2
required equipment, 7-3, 7-50, 8-4, 8-34
Reporting alarms and events, 1-2
Reports, see Performance monitoring
Resetting counters, Emphasis1>see Performance
monitoring
RTU, see Remote test unit
RX
Ethernet port, 2-68
RX ALIGNMENT ERR
Ethernet port, 2-69
RX BROADCAST
EOS port, 2-62
Ethernet port, 2-68
RX BYTES
EOS port, 2-62, 2-63
Ethernet port, 2-69, 2-70
RX BYTES BAD
Ethernet port, 2-69
RX DELAY DISCARDS
Ethernet port, 2-69
RX DISCARDS
Ethernet port, 2-69
RX FCS ERR
Ethernet port, 2-69
RX FRAMES
EOS port, 2-62
Ethernet port, 2-68
RX MTU DISCARDS
EOS port, 2-63
Ethernet port, 2-69
RX MULTICAST
EOS port, 2-62
Ethernet port, 2-68
RX NO DELIMITER
Ethernet port, 2-68
RX PAUSE
Ethernet port, 2-69
RX PKT > 1518
Ethernet port, 2-68
RX PKT 1024-1518
Ethernet port, 2-68
RX PKT 128-255
Ethernet port, 2-68
RX PKT 256-511
Ethernet port, 2-68
RX PKT 512-1023
Ethernet port, 2-68
RX PKT 64
Ethernet port, 2-68
RX PKT 65-127
Ethernet port, 2-68
RX UNICAST
EOS port, 2-62
Index-14
Ethernet port, 2-68
S
SDH
alarm profile
HO path, 1-10
LO path, 1-10
port, 1-10
path
performance monitoring, 2-46, 2-55
performance parameters, 2-39
SDH port
facility loopback tests, 4-17
performance monitoring, 2-50
BBE-MS, 2-51
BBE-RS, 2-50
EB-MS, 2-51
EB-RS, 2-50
ES-MS, 2-51
ES-RS, 2-50
FC-MS, 2-52
FE BBE-MS, 2-54
FE EB-MS, 2-53
FE ES-MS, 2-53
FE FC-MS, 2-54
FE UAS-MS, 2-53
PSCP-MS, 2-52
PSCW-MS, 2-52
PSDP-MS, 2-52
PSDW-MS, 2-52
SES-MS, 2-51
SES-RS, 2-50
UAS-MS, 2-51
terminal loopback tests, 4-17
SDH section
capacity monitoring
parameters, 2-59
Security monitoring
administrative use, 1-1, 1-21
PM information
not collecting, 2-1, 2-19, 2-39, 2-61
Self test, GCM, see GCM, Power On Self Test
Server alarm profile, 1-10
Server IP address, 7-13, 7-57
Service
performance monitoring
SONET VT, 2-35
performance monitoring SONET STS, 2-33
Service error codes
EMS, 1-109
system resources unavailable (1035), 1-110
SESFE
severely errored seconds, far end–line, 2-27
Turin Networks
Release TR3.0.x
Index
Severely errored frames
alarm indication signal seconds
DS1 port, 2-21
Severely errored framing seconds
DS1 port, far end, 2-22
Section
EC1 port, 2-27
SONET section, 2-29
Severely errored seconds
DS1 port, 2-20
DS1 port, far end, 2-22
DS3 port, 2-23
DS3 port (CBit), 2-24
DS3 port (CBit), far end, 2-25
DS3 port (PBit), 2-23
Line
EC1 port, 2-26
Line, far end
EC1 port, 2-27
LO VC3 path, 2-47
LO VC3 path, far end, 2-48
SDH port–MS, 2-51
SDH port–MS, far end, 2-53
SDH port–RS, 2-50
Section
EC1 port, 2-27
SONET line, 2-30
SONET line, far end, 2-32
SONET path, 2-33
SONET path, far end, 2-34
SONET section, 2-29
SONET VT path, 2-35
SONET VT path, far end, 2-36
VC11 path, 2-55
VC11 path, far end, 2-57
VC12 path, 2-55
VC12 path, far end, 2-57
VC3 path, 2-47
VC3 path, far end, 2-48
VC4 path, 2-47
VC4 path, far end, 2-48
Severity
NSA, 1-8
SA, 1-8
sort by, 1-19
Severity levels
alarm and event
defaults, 1-1, 1-21
defined, 1-5
SFP optic port
performance monitoring
measured supply voltage, 2-28, 2-71
measured temperature, 2-28, 2-71
Release TR3.0.x
measured TX bias current, 2-28, 2-71
measured TX input power, 2-28, 2-71
measured TX output power, 2-28, 2-71
Shelf alarm profile, 1-10
SNMP
ems.mib, 9-23
MIB, 9-23
node
agent port, 9-22
configuration, 9-22
Software
activation, 7-31
compatibility, 7-4, 7-51, 8-2
download
abort, 7-17, 7-61
clear, 7-17, 7-61
status, 7-17, 7-61
download times, 7-15, 7-59
upgrade, 7-1, 7-49
activate GCM, 7-22, 7-26, 7-36, 7-37, 7-47, 765, 7-69
activate time, 7-23, 7-25, 7-31, 7-66, 7-68
hitless warm reboot, 7-7
status, 7-17, 7-61
upgrade order, 7-31
upgrade type
initiate, 7-16, 7-60
version
current, 7-19, 7-63, 8-3
standby, 7-18, 7-62
verify, 7-19, 7-63, 8-3
SONET
performance parameters, 2-19
port
alarm profile, 1-10
STS
alarm profile, 1-10
VT
alarm profile, 1-10
SONET line
performance monitoring
CV-L, 2-29
ES-L, 2-30
FC-L, 2-30
FE CV-L, 2-31
FE ES-L, 2-31
FE FC-L, 2-32
FE SES-L, 2-32
FE UAS-L, 2-32
PSCP-L, 2-31
PSCW-L, 2-30
PSDP-L, 2-31
PSDW-L, 2-31
Turin Networks
Index-15
Index
SES-L, 2-30
UAS-L, 2-30
SONET path
performance monitoring
CV-P, 2-33
ES-P, 2-33
FE CV-P, 2-34
FE ES-P, 2-34
FE SES-P, 2-34
FE UAS-P, 2-34
SES-P, 2-33
UAS-P, 2-33
SONET port
facility loopback tests, 4-17
performance monitoring, 2-29
terminal loopback tests, 4-17
SONET section
capacity monitoring
capacity available, 2-37
STS available, 2-37
STS used, 2-37
VT available, 2-37
VT used, 2-37
performance monitoring
CV-S, 2-29
ES-S, 2-29
SEFS-S, 2-29
SES-S, 2-29
SONET VT path
performance monitoring
CV-V, 2-35
ES-V, 2-35
FE CV-V, 2-36
FE ES-V, 2-36
FE SES-V, 2-36
FE UAS-V, 2-36
SES-V, 2-35
UAS-V, 2-35
Speed
cooling fan, 6-2
Standby
hop, 2-11
module, 7-43
Status
activation, 7-24, 7-66, 7-68
time, 7-32
GCM protection, 7-22, 7-65
StickyMode, see Alarm
STM-1E
terminal loopback tests, 4-13
SWMIS, 7-24, 7-26, 7-30, 7-67, 7-68
Symptoms
incorrect environmental alarms, 4-2
recommended actions, 4-2
Index-16
System resources
unavailable, 1-110
T
TAC, see Test access cross-connect
TAP, see Test access point
Templates
performance monitoring, 2-2
Termination point
TP, test access, 5-2
Test Access
ADM, 5-1
DCS3/1, 5-1
digital signals, 5-1
facility access digroup, 5-2
intrusive, 5-1
non-intrusive, 5-1
remote test unit, 5-2
termination point, 5-2
test system controller (TSC), 5-23
Test access, 5-5
AID, 5-2
cross-connect, 5-2
DS1 module, 5-8
DS3 module, 5-8
DS3 transmux module, 5-8
dual facility access digroup, 5-2
E1 module, 5-8
management system, 5-8
monitor, 5-9
OC-N/STM-N, 5-8
per side split, 5-13
point, 5-2
remote test access, 5-3
series split, 5-17
test system controller, 5-2
VCX component, 5-8
VT/TU 5G switch, 5-8
Test system controller, 5-2
TSC, 5-23
Threshold crossing alert
capacity monitoring
number generated, 2-4
Thresholds
capacity parameter settings, 2-4
PM parameter settings, 2-4
Toggle switch
PDAP-2S circuit breaker, 6-12
TP
termination point, test access, 5-2
TPA fuse
PDAP-4S, 6-18
TransAccess 200 Mux
Turin Networks
Release TR3.0.x
Index
port number, 9-23
read community, 9-23
write community, 9-23
Transmit and receive signal levels, 4-3, 4-7
Transmux
DS3/EC-1, 8-9, 9-2
Troubleshooting
error codes, 1-107
loopback tests, 4-11
transmit and receive signal levels, 4-3, 4-7
TSC, see Test access test system controller
TX BROADCAST
EOS port, 2-62
Ethernet port, 2-67
TX BYTES
EOS port, 2-62
Ethernet port, 2-69, 2-70
TX BYTES BAD
Ethernet port, 2-69
TX DEFERRED FRAMES
Ethernet port (T10/00 only), 2-69
TX DISCARDS
EOS port, 2-62
Ethernet port, 2-69
TX EXCESSIVE COLL
Ethernet port (10/100 only), 2-70
TX FRAMES
EOS port, 2-62
Ethernet port, 2-67
TX LATE COLL
Ethernet port (10/100 only), 2-70
TX MULTICAST
Ethernet port, 2-62, 2-67
TX MULTIPLE COLL
Ethernet port (10/-100 only), 2-69
TX PAUSE
Ethernet port, 2-69
TX PKT > 1518
Ethernet port, 2-67
TX PKT 1024-1518
Ethernet port, 2-67
TX PKT 128-255
Ethernet port, 2-67
TX PKT 256-511
Ethernet port, 2-67
TX PKT 512-1023
Ethernet port, 2-67
TX PKT 64
Ethernet port, 2-67
TX PKT 65-127
Ethernet port, 2-67
TX SINGLE COLL
Ethernet port (10/00 only), 2-69
TX UNICAST
Release TR3.0.x
EOS port, 2-62
Ethernet port, 2-67
U
UASFE
unavailable seconds
far end, line, 2-28
Unavailable seconds
DS1 port, 2-21
DS1 port, far end, 2-22
DS3 port (CBit), 2-24
DS3 port (CBit), far end, 2-25
DS3 port (PBit), 2-23
Line
EC1 port, 2-26
Line, far-end
EC1 port, 2-28
LO VC3 path, 2-47
LO VC3 path, far end, 2-49
SDH port–MS, 2-51
SDH port–MS, far end, 2-53
SONET line, 2-30
SONET line, far end, 2-32
SONET path, 2-33
SONET path, far end, 2-34
SONET VT path, 2-35
SONET VT path, far end, 2-36
VC11 path, 2-56
VC11 path, far end, 2-58
VC12 path, 2-56
VC12 path, far end, 2-58
VC3 path, 2-47
VC3 path, far end, 2-49
VC4 path, 2-47
VC4 path, far end, 2-49
Upgrade
tray fan
front inlet, 8-33
Upgrading software, 7-1, 7-49
Username, 7-13, 7-57
V
VC11 path
performance monitoring
BBE-LP, 2-55
EB-LP, 2-55
ES-LP, 2-55
FC-LP, 2-56
FE BBE-LP, 2-57
FE EB-LP, 2-57
FE ES-LP, 2-57
FE FC-LP, 2-58
FE SES-LP, 2-57
Turin Networks
Index-17
Index
FE UAS-LP, 2-58
NPJC-DET-LP, 2-56
NPJC-GEN-LP, 2-56
PJCD-LP, 2-57
PJCS-DET-LP, 2-56
PJCS-GEN-LP, 2-57
PPJC-DET-LP, 2-56
PPJC-GEN-LP, 2-56
SES-LP, 2-55
UAS-LP, 2-56
VC12 path
performance monitoring
BBE-LP, 2-55
EB-LP, 2-55
ES-LP, 2-55
FC-LP, 2-56
FE BBE-LP, 2-57
FE EB-LP, 2-57
FE ES-LP, 2-57
FE FC-LP, 2-58
FE SES-LP, 2-57
FE UAS-LP, 2-58
NPJC-DET-LP, 2-56
NPJC-GEN-LP, 2-56
PJCD-LP, 2-57
PJCS-DET-LP, 2-56
PJCS-GEN-LP, 2-57
PPJC-DET-LP, 2-56
PPJC-GEN-LP, 2-56
SES-LP, 2-55
UAS-LP, 2-56
VC3 path
performance monitoring
BBE-HP, 2-47
EB-HP, 2-46
ES-HP, 2-46
FC-HP, 2-47
FE BBE-HP, 2-49
FE EB-HP, 2-48
FE ES-HP, 2-48
FE FC-HP, 2-49
FE SES-HP, 2-48
FE UAS-HP, 2-49
NPJC-DET-HP, 2-48
NPJC-GEN-HP, 2-48
PPJC-DET-HP, 2-47
PPJC-GEN-HP, 2-48
SES-HP, 2-47
UAS-HP, 2-47
VC4 path
performance monitoring
BBE-HP, 2-47
EB-HP, 2-46
Index-18
ES-HP, 2-46
FC-HP, 2-47
FE BBE-HP, 2-49
FE EB-HP, 2-48
FE ES-HP, 2-48
FE FC-HP, 2-49
FE SES-HP, 2-48
FE UAS-HP, 2-49
NPJC-DET-HP, 2-48
NPJC-GEN-HP, 2-48
PPJC-DET-HP, 2-47
PPJC-GEN-HP, 2-48
SES-HP, 2-47
UAS-HP, 2-47
Viewing
alarms, 1-6, 1-17
all nodes, 1-17
card, 1-17
one node, 1-17
port, 1-17
service CTP, 1-17
PM data
port, 2-9, 2-15
service, 2-11, 2-13
VT/TU Switch
module placement, 8-11, 9-4
W
Warm reboot
hitless software upgrade, 7-7
Write community
TransAccess 200 Mux, 9-23
Turin Networks
Release TR3.0.x
Index
Release TR3.0.x
Turin Networks
Index-19
Index
Index-20
Turin Networks
Release TR3.0.x
Index
Release TR3.0.x
Turin Networks
Index-21
Index
Index-22
Turin Networks
Release TR3.0.x
Index
Release TR3.0.x
Turin Networks
Index-23
Index
Index-24
Turin Networks
Release TR3.0.x
Index
Release TR3.0.x
Turin Networks
Index-25
Index
Index-26
Turin Networks
Release TR3.0.x
Visit our website at:
www.turinnetworks.com
Release OPS4.0.x
Operations Documentation
800-0011-OPS40