Traverse Operations Guide - Force10 · 2010-03-12 · Operations and Maintenance Guide, Section 1: Fault Management Event List on the Events Tab Page 1-4 Force10 Networks Release

Traverse Operations GuideRelease TR3.2.3 March 2010 Edition 1

Copyright © 2010 Force10 Networks, Inc.

All rights reserved. Force10 Networks ® reserves the right to change, modify, revise this publication without notice.

TrademarksForce10 Networks® and E-Series® are registered trademarks of Force10 Networks, Inc. Traverse, TraverseEdge, TraversePacketEdge, TransAccess, are registered trademarks of Force10 Networks, Inc. Force10, the Force10 logo, and TransNav are trademarks of Force10 Networks, Inc. or its affiliates in the United States and other countries and are protected by U.S. and international copyright laws. All other brand and product names are registered trademarks or trademarks of their respective holders. Statement of ConditionsIn the interest of improving internal design, operational function, and/or reliability, Force10 Networks, Inc. reserves the right to make changes to products described in this document without notice. Force10 Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) described herein.

Release OPS4.2.3 Force10 Networks Page i

OPERATIONS AND MAINTENANCE GUIDE

Contents

Section 1 Fault ManagementChapter 1 Managing Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Chapter 2 Alarms, Events, and Recommended Actions . . . . . . . . . . . . . . . . . . . . . . . . 1-33Chapter 3 Service Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-137

Section 2 Performance MonitoringChapter 1 Managing Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Chapter 2 SONET Performance Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Chapter 3 SDH Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Chapter 4 Ethernet Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63

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

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

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

Section 6 Routine MaintenanceChapter 1 Routine Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Operations and Maintenance Guide

Page ii Force10 Networks Release OPS4.2.3

Chapter 2 Node Database Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23

Section 7 Software UpgradesChapter 1 Release TR3.2.3 Traverse Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . 7-1Chapter 2 Release TE3.2.x TE-100 System Software Upgrade . . . . . . . . . . . . . . . . . . 7-53

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

Section 9 AppendicesAppendix A Module Placement Planning and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

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


SECTION 1 FAULT MANAGEMENTSECTION 1SECTION 1

Contents

Chapter 1Managing Alarms and Events

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

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

Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Events Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Event List on the Events Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Changing Column Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Sorting Events List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Changing Event Retrieval Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Viewing Event Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Grouping Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Setting Event Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Event Filters, Source Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Event Filters, Probable Cause Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Event Filters, Time Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Event Filters, Severity Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Saving and Importing User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Network Alarm Summary Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Service Affecting Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Alarm Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Alarm Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Traverse Card LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Customizing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Alarm Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Alarm Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Sort by Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Creating a New Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Assigning an Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Assigning a Port Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Assigning a Subport Alarm Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

Operations and Maintenance Guide, Section 1 Fault Management


Assigning a Service Path Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21Suppressing Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23Manually Suppress Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Automatic Suppression of Service CTP Path Alarms . . . . . . . . . . . . . . . . . . . 1-24Viewing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Alarm Tallies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28Detail View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28Map View Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29New Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Set Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30Sort by Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30StickyMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

Chapter 2Alarms, Events, and Recommended Actions

Alarms/Events, A through C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35Alarms/Events, D through K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52Hardware Fault Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71Alarms/Events, L through S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-72Alarms/Events, T through TZ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108Alarms/Events U through Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-116Alarms/Events, TA200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-119Alarms/Events, TE-206 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-136

Chapter 3Service Error Codes

Service Activation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-138Service Error Codes and Recommended Actions . . . . . . . . . . . . . . . . . . . . . . 1-139

Release OPS4.2.3 Force10 Networks Page 1-1

SECTION 1FAULT MANAGEMENT

Chapter 1 Managing Alarms and Events

Introduction During normal operation of the Force10 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-13.

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• Event Logs• Events Tab• Alarms Tab• Network Alarm Summary Window• Customizing Alarms• Suppressing Alarms• Viewing Alarms

For management system references, see the TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 2—“Alarms.”

Contact the Force10 Technical Assistance Center (TAC) if you need assistance.

Operations and Maintenance Guide, Section 1: Fault ManagementEvent Types

Page 1-2 Force10 Networks Release OPS4.2.3

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 events. The system raises an event, such as an alarm, when it first detects a fault condition. While the fault condition persists, the event is active. When the system detects that a fault condition no longer exists, it clears the even. 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 the Traverse General Control Card (GCM) or TraverseEdge 100 system card. The data from the log can be viewed using the node-level CLI or server-level CLI. 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 in the /report/output directory. This log provides easy access to information about recent events. Use the Report Scheduler to schedule a report to save the data in the Event Log.

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 log of events that occur on the node or server. If the Event Log is on the Traverse General Control Card (GCM) or TraverseEdge 100 System card, the last 300 events are logged. Events are kept for a maximum of 3 days with a maximum limit of 10,000 events possible. If the output file directory is on the TransNav server, the system automatically deletes all files after the value set in the ReportRemovalPeriod (days) parameter is reached. For more information, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Setting Up Report Parameters.

Force10 recommends performing regular backups of the log files. Use the Report Scheduler to set up a regularly generated report on events. For details, see the TransNav Management System GUI Guide, Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports,” Generating Reports.

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

Operations and Maintenance Guide, Section 1: Fault ManagementEvent List on the Events Tab


Event List on the Events Tab

The event list is context-sensitive (see Events Tab, page 1-3). • Click a specific node in Map View to display only events associated with that node.• Click the map outside of a specific node to display all domain-wide events. The

number of domain-wide events is listed in queried Events. The number of displayed events is displayed in displayed Events. Both fields appear in the lower left of the Events tab.

• In Shelf View, click a specific card or port to display only events associated with that card or port.

• Click outside the shelf to display all events associated with that node.

Changing Column Order

To change the order in which a column is displayed on the Events tab, hold down the Shift key and click and drag a column heading to the desired location.

Sorting Events List

Click a column heading to sort the events list by that category. Column headings can be sorted in ascending or descending order. Click the column heading again to switch from ascending to descending order. Hold down the Shift key and click a second column heading to sort the second category within the first category. Hold down the Shift key and click the second column again to switch between ascending and descending order within the first category.

Command buttons are as follows:• Settings: Specify the time period and refresh interval within which to display

events. Displays the Event Retrieval Settings View (Main) dialog box. See Changing Event Retrieval Settings, page 1-5.

• Refresh: Display events according to Event Retrieval Settings View (Main) dialog box (Figure 1-2).

• Detail View: View highlighted event details. Displays the Event Detail (View Main) dialog box. See Viewing Event Details, page 1-6.

• Set Filters: Set filters to display events. Displays the Event Filter (View Main) dialog box. See Setting Event Filters, page 1-8.

• New Window: Opens an independent Event View dialog box which inherits the event filters set for the Events tab. You can change the filters on this dialog box by clicking Set Filters.

• Print: Print contents of Events tab.• Save: Save event information to a text file.

Chapter 1 Managing Alarms and EventsChanging Event Retrieval Settings


Changing Event Retrieval Settings

From the Events tab, click the Settings button to specify the time period and refresh interval within which to display events. The Event Retrieval Setting (View Main) dialog box displays.

Figure 1-2 Event Retrieval Settings (View Main) Dialog Box

The Event Retrieval Settings (View Main) dialog box allows you to set the following information:• Retrieve Events up to: Select the ending time to retrieve events:

– Now (default)– Define. When this is selected, the field is replaced with a date/time entry. Use

the up and down arrows or enter the ending time to retrieve events.• for: Select the amount of time to retrieve events:

– 1 min– 5 min– 15 min (default)– 30 min– 45 min– 1 hr– 2 hr– 4 hr

• Automatic Refresh: Select to automatically retrieve events according to the Retrieve Events up to, for, and every settings. Clear the checkbox to manually retrieve events.

• every: Select the refresh interval. Valid values are:– 1 min– 5 min– 15 min (default)– 30 min– 45 min– 1 hr– 2 hr– 4 hr

• Wrap line in Description Column: Select this checkbox to show the entire description of the event on the Events tab, in the Desc column.

Command buttons are as follows:• Refresh Now: Retrieve events according to the settings in the dialog box.• Ok: Close the dialog box.

Operations and Maintenance Guide, Section 1: Fault ManagementViewing Event Details


Viewing Event Details

From the Events tab, select an event from the events list. Double-click the selected event or click the Detail View button. The Event Detail (View Main) dialog box displays.

Figure 1-3 Event Detail (View Main) Dialog Box

The Event Detail (View Main) dialog box allows you to view the following information about the selected event:• ID: Event identification number• Probable Cause: Describes the probable cause of the event• Creation Time: Time the event was created• Description: Description of the event• Severity: Severity of the event• Source: Source of the event

Click Done to close the dialog box.

Chapter 1 Managing Alarms and EventsGrouping Events


Grouping Events

From the Events tab, select an event from the event list. Hold the Ctrl key down and select other events to add to the group. You can now perform operations on a group of events.

You can perform operations on selected events in two additional ways:• Click the Events menu.• Right-click an event or group of events.

The following shortcut menu is displayed:

Figure 1-4 Events Menu and Events Tab Shortcut Menu

Menu selections are as follows:• Set Filters: Displays the Event Filter (View Main) dialog box.• New Window: Opens an independent Event View dialog box, which inherits the

event filters set for the Events tab. You can change the filters on this dialog box by clicking Set Filters.

• Detail View: View highlighted event details. Displays the Event Detail (View Main) dialog box.

• Settings: Specify the time period and refresh interval within which to display events. Displays the Event Retrieval Settings (View Main) dialog box.

• Refresh: Displays events according to the Event Retrieval Settings (View Main) dialog box.

Operations and Maintenance Guide, Section 1: Fault ManagementSetting Event Filters


Setting Event Filters

On the Events tab, click Set Filters. The Event Filter (View Main) dialog box displays.

Figure 1-5 Event Filter (View Main) Dialog Box, Source Tab

The Event Filter (View Main) dialog box has the following tabs:• Event Filters, Source Tab, page 1-8• Event Filters, Probable Cause Tab, page 1-9• Event Filters, Time Tab, page 1-9• Event Filters, Severity Tab, page 1-10

After you make changes to any filter, click Apply, then click Done.• Click Apply to apply changes to the filter.• Click Done to close the dialog box.

Event Filters, Source Tab

You can choose to include or exclude events from specific sources from being displayed on the Events tab. Select the Active checkbox to make the Source filter active. Clear the Active checkbox to make the Source filter inactive.

To display events from a specific source, highlight the source in the left box and click the right arrow to move it to the right box. Click Include. To exclude a list of sources, click Exclude. Use the * as a wildcard character. For example, typing Cypress* in the Available Sources box and clicking the right arrow would include all event sources whose name begins with Cypress.

Chapter 1 Managing Alarms and EventsEvent Filters, Time Tab


Event Filters, Probable Cause Tab

Click the Probable Cause tab to include or exclude specific event types from displaying on the Events tab.

Figure 1-6 Event Filter (View Main) Dialog Box, Probable Cause Tab

Select the Active checkbox to make the Probable Cause filter active. Clear the Active checkbox to make the Probable Cause filter inactive.

To display a specific event type, highlight the event in the left box and click the right arrow to move it to the right box. Click Include. To exclude a list of event types, click Exclude.

Event Filters, Time Tab

Click the Time tab to specify the time periods within which to display events.

Figure 1-7 Event Filter (View Main) Dialog Box, Time Tab

Select the Active checkbox to make the Time filter active. Clear the Active checkbox to make the Time filter inactive.

Operations and Maintenance Guide, Section 1: Fault ManagementEvent Filters, Severity Tab


Click one of the three following option buttons:• Before: Display events which occurred before the time specified.• After: Display events which occurred after the time specified.• Between _ and _: Display events which occurred between the times specified.

Click the up arrow to go forward in time and the down arrow to go back in time.

Event Filters, Severity Tab

Click the Severity tab to specify the severity of events to display.

Figure 1-8 Event Filter (View Main) Dialog Box, Severity Tab

Select the Active checkbox to make the Severity filter active. Clear the Active checkbox to make the Severity filter inactive.

Select one or more of the following event severities to display: • Critical• Major• Minor• Warning• Clear• Info

Saving and Importing User Preferences

You can save alarm and event filter and sort settings and import these settings from another user. For details, see the TransNav Management System GUI Guide, Section 2—Administrative Tasks, Chapter 4—“TransNav User Preferences,” Saving and Importing User Preferences.

Chapter 1 Managing Alarms and EventsAlarms 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-9 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• Alarm Hierarchy • Customizing Alarms

Figure 1-9 Alarms Tab

StickyModeDetail View Set Filters New WindowCommand Command Command

PrintCommand

SaveCommand

View Selector

Sort by Column

Map View

Alarm Caption

Node Object

Alarms

Display

List

Alarms Tab

Operations and Maintenance Guide, Section 1: Fault ManagementNetwork Alarm Summary Window


Network Alarm Summary Window

The TransNav network alarm summary window shows counts of outstanding Critical (C), Major (M), Minor (m) alarms, and Warnings (W).

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

For an explanation of the colors associated with each alarm type, see Alarm Severity Levels.

Service Affecting Status

Two levels of service affecting status are used in the alarm definitions:• Service Affecting (SA): Indicates that a service affecting condition has occurred

and an immediate corrective action is required.• Non-Service Affecting (NSA): Indicates that a non-service affecting condition

has occurred.

Service affecting alarms apply when protection is not available. This same alarm is considered non-service affecting if the equipment or facility is protected and the alarm is raised on the standby equipment or facility. Alarms listed as non-service affecting do not affect service regardless of equipment or facility protection scheme. For more information on how service affecting alarms are conducted, see Alarm Behavior.

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. Each alarm type is color coded for easy identification:• 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.

Alarm Summary

Chapter 1 Managing Alarms and EventsAlarm Hierarchy


• Major (orange): A hardware or software condition has occurred that indicates a serious disruption of service or the malfunctioning or failure of important circuits. This requires the immediate attention and response of a technician to restore or maintain system capability. The urgency is less than in critical situations because of a lesser immediate or impending effect on service or system performance.

• Minor (yellow): Trouble has occurred that does not have a serious 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/aqua): 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 Behavior

Alarms are generated depending on the configuration of an alarm and the settings in the SA/NSA parameter. If the SA/NSA parameter in the alarm configuration profile is set to disabled, the alarm will always display the NSA values. If the SA/NSA parameter in the alarm configuration profile is set to enabled, the appropriate values from the condition values are used.

Line alarms, such as RFI, cause the Availability Status of alarms to change to Degrade. Resolve the alarm to clear the availability status.

Alarm Hierarchy

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

Operations and Maintenance Guide, Section 1: Fault ManagementTraverse Card LEDs


Traverse Card LEDs

The locations of common and specific card LEDs is shown in the following graphic.

Figure 1-11 Physical Card LEDs

DS3/E3 OC-N/STM-N Ethernet

DS1, DS3/E3,E1, OC-N/STM-N

and ETH PortIndicators

ETHERNET LINKOSS and Craft

Alarms:CRITICAL/MAJOR

MINOR

Timing:LOCKED/

UNLOCKEDFREE RUN/HOLDOVER

RS-232 Interface(DB-9)

EGCM

ACO ON

10/100BaseTEthernet Interface

(RJ-45)

DS1 VTSwitch

ACO

PWR(Power)

ACTV/STNBY

(Active/Standby)Optical

Port

E1OPS 00015

Chapter 1 Managing Alarms and EventsAlarm Profiles


Customizing Alarms

The TransNav GUI provides functions for creating new, modifying default, and assigning alarm profiles in order to customize alarm parameter settings (e.g., severity level) based on your network requirements. Refer to the following topics:• Alarm Profiles• Creating a New Alarm Profile• Assigning a Port Alarm Profile

Alarm Profiles Alarm profiles allow users to customize alarms based on severity, service affecting status, and whether to enable or disable (suppress) alarm generation. If a flag is set in the Service Affecting column in the Alarm Profile dialog box for alarms to be reported from an unprotected facility or from equipment or a facility in a protection group, the system uses the alarm severity defined in the Severity SA column. If the flag in the Service Affecting column is not selected, the system uses the alarm severity defined in the Severity NSA column.

Figure 1-12 Alarm Profile Dialog Box

Operations and Maintenance Guide, Section 1: Fault ManagementAlarm Profiles


Alarm Properties

Select an alarm profile and click Properties to view additional information about the alarm profile selected.

Figure 1-13 Alarm Profile, Properties Screen

Sort by Column

Click a column heading to sort the alarms by that category. The Name and Probable Cause columns can be sorted in alphabetical or reverse alphabetical order. The Severity NSA and Severity SA columns can be sorted in ascending or descending severity. The ServiceAffecting and Enabled columns can be sorted by select/clear. Click the column heading again to switch from one sorting category to the other.

Figure 1-14 Alarm Profile, Properties Screen with Reorganized Columns

Chapter 1 Managing Alarms and EventsCreating a New Alarm Profile


Creating a New Alarm Profile

The following procedure describes how to create an Alarm Profile template.

Table 1-1 Creating a New Alarm Profile

Step Procedure

1 In Map View, from the Admin menu, click Alarm Profiles.

Figure 1-15 Alarm Profiles Dialog Box

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


2 From the Type drop-down list, select the type of alarm profile you want to create:• ds1_ptp: SONET DS1 port• ds3_ptp: SONET DS3/EC1 ports• e1_ptp: SDH E1 port• e3_ptp: SDH E3 port• eop: Ethernet-over-PDH port• eop_ctp: Ethernet-over-PDH port connection termination point• 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• ta200: TransAccess 200 Mux • te50: TraverseEdge 50

3 Click Add to view the alarm profile, then enter a Name for the alarm profile. The example shown below is an eos_ alarm profile with default values.

Figure 1-16 Alarm Profile Dialog Box

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

Step Procedure

Chapter 1 Managing Alarms and EventsAssigning an Alarm Profile


Assigning an Alarm Profile

Choose one of the following topics by object type (e.g., port) to assign an alarm profile:• Assigning a Port Alarm Profile• Assigning a Subport Alarm Profile• Assigning a Service Path Alarm Profile

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 Synchronize to synchronize the alarm profile to make it available to other nodes.

Click OK to return to the previous dialog box or click Cancel to cancel the changes.

5 Click Close in the Alarm Profiles dialog box.

6 The Creating a New Alarm Profile procedure is complete.

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

Step Procedure

Operations and Maintenance Guide, Section 1: Fault ManagementAssigning a Port Alarm Profile


Assigning a Port Alarm Profile

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

Assigning a Subport Alarm Profile

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

Table 1-2 Assigning a Port Alarm Profile

Step Procedure

1 In Shelf View, select a card port.

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.

Table 1-3 Assigning a Subport Alarm Profile

Step Procedure

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


3 From the Subport row, Alarm Profile column list, select a port (ptp) alarm profile template matching the embedded signal subport type (e.g., ds1_ptp).

4 Click Apply.

5 The Assigning a Subport Alarm Profile procedure is complete.

Chapter 1 Managing Alarms and EventsAssigning a Service Path Alarm Profile


Assigning a Service Path Alarm Profile

The following procedure describes how to assign a path alarm profile template to a service connection termination point within an end-to-end transport path.

Table 1-4 Assigning a Service Path Alarm Profile

Step Procedure

1 From any view, click the Service tab.

Figure 1-17 Service Tab

2 Select a service. Right-click and select Show TxRx Path to display the Path Display for Services screen.

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

Figure 1-18 Path Display for Services Screen

Operations and Maintenance Guide, Section 1: Fault ManagementAssigning a Service Path Alarm Profile


4 From the Path Display for Service screen, in either the Tx or Rx table row, select an Active Hop. Your selection displays in the EndPoint field of the CTP screen.

Figure 1-19 Path Display for Services Screen, CTP Tab

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

Step Procedure

3

Chapter 1 Managing Alarms and EventsSuppressing Alarms


Suppressing Alarms

The TransNav GUI provides an alarm suppression function through the administrative state of an object. When the administrative state of a containing object is set to suppress alarms, then any object contained within obeys the parent object without consideration of its own current administrative state.

Refer to the following topics:• Manually Suppress Port Alarms• Automatic Suppression of Service CTP Path Alarms

5 From the Alarm Profile parameter, select one of the following profile values:• useParent: The alarm profile of the containing object (Parent) based

on the following (superset and subset) definitions:– Port: Contains line and path alarms and is the superset.– High order path: Contains high and low order path alarms and is a

subset of port profiles.– Low order path: Contains only low order path alarms and is a finer

subset of high order path profiles.– STS path. Contains STS and VT path alarms and is a subset of

port profiles.– VT path: Contains only VT path alarms and is a finer subset of

STS path profiles.• default: The default alarm profile matching the CTP object type.• <user-defined>: Depending on the CTP object type, a user-defined

alarm profile of one of the following path alarm profile types:– sdh_hp– sdh_lp– sonet_sts– sonet_vt

6 Click Apply.

7 The Assigning a Service Path Alarm Profile procedure is complete.

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

Step Procedure

Operations and Maintenance Guide, Section 1: Fault ManagementManually Suppress Port Alarms


Manually Suppress Port Alarms

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

Automatic Suppression of Service CTP Path Alarms

The automatic in service state on the CTPs is inherited from the optical port on the Traverse node where the CTP resides. If the automatic in service setting on the port is changed, the service must be de-activated, then re-activated for the changes to take effect. If the automatic in service feature is enabled on a port that is in a protection group, the enable and disable actions must be performed on the working port.

To start the countdown of the automatic in service timer on the CTP, the following criteria must be met:• the admin state of the service must be locked• the automatic in service setting on the port must be enabled• the originating service endpoint (CTP) cannot have any alarms

When these criteria are met, the automatic in service timer on the CTP is set to the value defined on the node and begins to count down. When the service is unlocked, the automatic in service timer value is set to zero.

The Alarm Suppression of CTPs on a service can be locked and unlocked individually. This action does not control the automatic-in-service state on the CTPs. The admin state on the CTPs is driven by the admin state on the service. When the admin state of the service is locked, the admin state of all CTPs in the service are also locked, however, the CTPs still appear unlocked. The lock icon displayed next to “Alarm Suppression” indicates whether alarms on the CTP are suppressed or not.

If the CTP is on a DS1-MUX, DS3-TMX, STS1-TMX or VT-MUX service, only the STS endpoint values display. Each STS endpoint has 28 VT1.5 endpoints associated with it. If the timer on any single VT1.5 endpoint reaches 0, the service will unlock. This could be misleading. To see all 28 VT1.5 with alarms, unlock the service.

Table 1-5 Manually Suppress Port Alarms

Step Procedure

1 In Shelf View, select the card port.

2 Click the Config tab to display the Card Configuration dialog box.

3 Click the Lock icon at the bottom left portion of the screen to change the administrative state to locked and click Apply.

4 The Manually Suppress Port Alarms procedure is complete.

Chapter 1 Managing Alarms and EventsAutomatic Suppression of Service CTP Path Alarms


The following procedure describes how service CTP (connection termination point) path alarms are automatically suppressed.

Table 1-6 Automatically 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. Select a service. Right-click and select Admin State and Lock to lock the service.

Figure 1-20 Service Tab

3 Select the same service and select Show TxRx Path.

Figure 1-21 Service Tab, Show TxRx Path

Operations and Maintenance Guide, Section 1: Fault ManagementAutomatic Suppression of Service CTP Path Alarms


4 The Path Display for Services screen displays. Click the CTP tab to display the CTP screen at the bottom of the screen.


5 From the Path Display for Service screen, on either the Tx or Rx table row, select a service endpoint value in the Active Hop column. Your selection inserts into the EndPoint field in the CTP screen and the CTP Status button is activated.

Figure 1-23 CTP Tab with Endpoint Data

6 Click the CTP Status button to display the CTP Status dialog box.

Figure 1-24 CTP Status Dialog Box, Received Path Overhead Tab

The Path Overhead tab displays with label and path trace information for the transmitted or received signal selected. Click Refresh to update the information.

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

Step Procedure

Chapter 1 Managing Alarms and EventsAutomatic Suppression of Service CTP Path Alarms


7 Click the Automatic In Service tab.

Figure 1-25 CTP Status Dialog Box, Automatic In Service Tab

Automatic in service state: Indicates if the CTP is set to automatically suppress alarms and performance monitoring reports. Valid values are:• Enabled: Alarms and performance monitoring reports will be

automatically suppressed. • Disabled: Alarms and performance monitoring reports will be

reported.

Remaining automatic in service time: Indicates the amount of time remaining before the CTP port is unlocked. When 0 minutes is reached, alarms and performance monitoring reports will no longer be automatically suppressed. New alarms will restart the counter if 0 minutes has not been reached. The amount of time is set at the node level.

The CTP value is independent of the port unlocking.

Click Refresh to refresh the information displayed. Click Close to return to the Path Display for Service screen.

8 Click Apply.

9 The Automatically Suppress Service CTP Path Alarms procedure is complete. De-activate, then reactivate the service to enable the changes.

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

Step Procedure

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

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.

Chapter 1 Managing Alarms and EventsViewing Alarms


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

Go to Step 14.

7 Map View Display

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-9, 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-12.

Go to Step 14.

8 New Window

From the Alarms tab, click New Window to open a new alarm window.

Note: Multiple alarm windows can be opened, each with independently configurable filters.

Go to Step 14.

9 Print

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

Go to Step 14.

10 Save

Click Save to save alarm information to a text file.

Go to Step 14.

Table 1-7 Viewing Alarms (continued)

Step Procedure



11 Set Filters

From the Alarms tab, click Set Filters to set the alarm filters.

Note: Alarms can be filtered by Source, Probable Cause, Time, Severity, and Acknowledged By categories.

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


Step Procedure

Chapter 1 Managing Alarms and EventsViewing Alarms


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

Force10 recommends that you open a new window before you select StickyMode so new alarms continue to be reported.

14 Do you want to perform another alarm display function?• Yes. Go to Step 3.• No. The Viewing Alarms procedure is complete.


Step Procedure




SECTION 1SECTION 1FAULT MANAGEMENT

Chapter 2 Alarms, Events, and Recommended Actions

Introduction During normal operation of the Force10 product family, various conditions may arise that require attention by network operations. Events and alarms alert you to Traverse and TE-206 system operational changes.

This chapter includes an alphabetic list of the following alarms, events, and recommended actions.• Alarms/Events, A through C• Alarms/Events, D through K• Hardware Fault Detection• Alarms/Events, L through S• Alarms/Events, T through TZ• Alarms/Events U through Z• Alarms/Events, TE-206

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 TransNav GUI alarm summary.

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)

Operations and Maintenance Guide, Section 1: Fault Management


located on the main backplane. These alarms are defined using the TransNav management system. Refer to the Traverse Installation and Commissioning Guide or the TraverseEdge 100 User Guide for details on environmental alarm connections.

Note: For Loss of Signal alarms, see the information in Section 4—Diagnostics, Chapter 2—“Traverse Transmit and Receive Signal Levels,” page 4-3 or Chapter 3—“TraverseEdge 100 Transmit and Receive Signal Levels,” page 4-7.

Contact the Force10 Technical Assistance Center (TAC) if you need assistance.

Chapter2

Alarm

s, Events, and Recom

mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-35

Alarms/Events, A through C

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

Alarm: Definition Alarm Profiles Probable Cause

Service Affecting Default

Default SeverityRecommended Action

SA (Unprotected)

NSA (Protected)

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

– Info Info (Informational; no action required.)

ACO_CLEAR: Clear Alarm Cut Off

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

ADMINTASK: Administrative task

server An administrative task was executed.


AIRCOND: Air Conditioning System Fail

shelf Air conditioning system failed. – Minor Minor Check and repair the air conditioning equipment, as necesary.

AIRDRYR: Air Dryer Fail shelf Air dryer failed. – Minor Minor Check and repair the air dryer equipment, as necesary.

AIS-L: Alarm Indication signal – Line

ds1_ptpds3_ptp(ds_ptp)e3_ptp1

ta200te50te206 node

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

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

Clear upstream alarms.

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

SA Critical Minor Check the BITS upstream.


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

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


Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, A through C

Page 1-36Force10 N

etworks

Release O

PS4.2.3

AIS-P: Alarm indication signal – Path

ds3_ptp(ds_ptp)e3_ptpta200te50

The STS signal demultiplexed from the DS3 or EC-1 contains an AIS. This AIS can result from an upstream failure along the STS path.

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


Verify your payload connections.

sonet_ptpsonet_sts te206 node

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

SA Critical Minor Check the equipment upstream.



AIS-P-TX: Alarm indication signal – Path, Transmit

te206 node The STS signal demultiplexed from the OC-N/STM-N contains an AIS. This AIS can result from a downstream failure along the STS path.


Clear downstream alarms.


AIS-S: Alarm indication signal – Service

ds3_ptp(ds_ptp)e3_ptpsdh_ptpsonet_ptpsonet_service

An upstream failure occurred at the Service layer.

– Warning Info Check the equipment upstream.


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




SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-37

AIS-V: Alarm indication signal – VT

ds1_ptpds3_ptp(ds_ptp)e3_ptpshelfsonet_ptpsonet_vtsonet_stste206 node

An upstream failure occurred at the VT path layer.



Verify your VT payload connections.

ta200te50

An upstream failure occurred at the VT path layer.

SA Critical Critical Check the equipment upstream.


Verify your VT payload connections.

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

AIS-VC: Alarm indication signal - VC

e1_ptpsdh_ptp

An upstream failure occurred at the VC path layer.



Verify your VC payload connections.

ALS: Automatic laser shutdown ethernet_ptpsdh_ptpsonet_ptp

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

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

ALS-TX-OFF: Transmitter automatically disabled

ethernet_ptpsdh_ptpsonet_ptp

Event logged against the optical interface upon ALS alarm condition.


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

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

– Info Info See AIS-P.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-38Force10 N

etworks

Release O

PS4.2.3

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

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

– Info Info See LOP-P.

APS-SDBER-P: 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-P: 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.

APS-UNEQ-P: 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.

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

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

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

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

sonet_ptpsdh_ptp

1+1 linear APS reports this alarm if the bidirectional mode is set and the APS K1/K2 bytes are in an invalid state.

– Minor Minor Check for OC-N module failures.

Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes.APSBF: Automatic protection

switch byte failuresonet_ptpsdh_ptp te206 node

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

sonet_ptpsdh_ptp

1+1 linear APS reports this alarm if bidirectional mode is set and K2 bits 6-8 are any of these values: 0,1,2,3.

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

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





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-39

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

sonet_ptpsdh_ptpte206 node

1+1 linear APS reports this alarm if the bidirectional mode is set and the APS K1/K2 bytes are in an invalid state.

– Minor Minor Check for OC-N module failures.

Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes.

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

sonet_ptpsdh_ptp

1+1 linear APS reports this alarm if the bidirectional mode is set and the APS K1/K2 bytes are in an invalid state. .

– Minor Minor Reseat the modules at the near end and upstream nodes.

Examine the incoming SONET overhead with an optical test set to confirm invalid K bytes.

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

sonet_ptpsdh_ptp

On a 2F BLSR, the automatic protection switching codes are inconsistent. Three consecutive frames do not contain identical APS bytes, giving the receiving equipment conflicting commands about switching.

– Minor Minor Check for other alarms, especially BERSD-L and BERSF-L. Clear these alarms.

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

Clean the optical connectors.

Reseat the modules at the near end and upstream nodes.

Check the protection mode for the far-end node.

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

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


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

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

– Info Info See LOS.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-40Force10 N

etworks

Release O

PS4.2.3

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

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


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

sonet_ptpsdh_ptp te206 node

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.

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

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


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

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

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


APS-PROTECT: Auto Switch to Working

te206 node A protection switch to the working facility that occurred because of an alarm clearing or Wait-To-Restore timer expiration.

Info (Informational; no action required.)

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.






SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-41

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

shelf A protection switch that occurred because a SDBER-P alarm has been cleared.


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

shelf A protection switch that occurred because a SFBER-P alarm has been cleared.


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

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


APS-WORK: Auto Switch to Protect

te206 node A protection switch to the protection faciilty that occurred because of an alarm on the working facility.

Info Check the working facility for alarms.

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

shelfte206 node

Traffic is in the process of switching back to working channels. This occurs when a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group has been configured as revertive.


AU-AIS: Administrative Unit Alarm Indication Signal

ds3_ptpsdh_hpsdh_ptp

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








SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-42Force10 N

etworks

Release O

PS4.2.3

AU-LOP: Administrative Unit Loss of Pointer


Valid AU pointer bytes are missing from the SDH overhead.

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

Verify cross-connects.

Check network timing synchronization.

Verify that the expected bandwidth and received bandwidth are the same.

If the alarm persists, replace the module.

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.

AUTOPRV: Auto provisioning error

sonet_ptpsdh_ptp

A signal failure has occurred on the ring and the user has added new cross-connect data. When the system attempts to auto provision the squelch tables, they cannot be updated, triggering the alarm.

– Minor Minor Clear the signal failure.

AUTO-TX-ON: Transmitter automatically enabled


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


BADPKTRX: Received an OSPF packet that cannot be parsed

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

BATDSCHRG: Battery is discharging

shelf Battery is discharging. – Minor Minor Check and follow your method of procedures.

BATTERY: Battery has failed shelf Battery has failed. – Minor Minor Check and follow your method of procedures.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-43

BERSD-L: Bit ErrorRate signal degrade – Line

ds3_ptp(ds_ptp)e3_ptp1

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

SA Warning Warning Check cable connectors and module ports.

If an EC-1 module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective “working” unit.

Check the remote (source) Transmit and cable connection.

shelfte50

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

– Warning Warning Check cable connectors.

sonet_ptpte206 node

• The BER on the incoming OC-N line has exceeded the signal degrade threshold.

• A connector in the OC-N optical link could be dirty.

• An OC-N module hardware problem could exist.

• Fiber could be bent or damaged.

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

Verify good optical connections.

Clean optical cable connectors and module ports.

If an OC-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective “working” unit.

Check the remote (source) Transmit and fiber connection.

Check fiber for bends or damage.

If the problem persists, contact Force10 ’s Technical Assistance Center (TAC).





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-44Force10 N

etworks

Release O

PS4.2.3

BERSD-P: Bit Error Rate signal degrade – Path


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

SA Warning Warning Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors.

Perform loopback tests to isolate the problem.

Check cable connectors and module ports.


sonet_ptpsonet_stste206 node

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




If an OC-N/STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective “working” unit.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-45

BERSD-V: BitError Rate signal degrade – VT Path


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




sonet_ptpsonet_stssonet_vtshelfte206 node

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




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

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

e1_ptpsdh_ptp

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








SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-46Force10 N

etworks

Release O

PS4.2.3

BERSF-L: Bit Error Rate signal fail – Line


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

SA Warning Warning Check cable connectors and module ports.

shelfte50

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

– Warning Warning Check cable connectors.

sonet_ptp te206 node

• The BER on the incoming OC-N line has exceeded the signal fail threshold.

• A connector in the OC-N optical link may be dirty.

• An OC-N module hardware problem may exist.


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










SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-47

BERSF-P: Bit Error Rate signal fail – Path


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





sonet_ptpsonet_stste206 node

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









SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-48Force10 N

etworks

Release O

PS4.2.3

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


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




sonet_ptpsonet_vtsonet_stste206 node

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




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




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

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

e1_ptpsdh_ptp

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




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

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





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-49

BITSA-LOCK: Lockout - Derived DS1 System BITS 1

shelf A lockout is in process on this timing reference.

– Warning Warning Clear the Lockout switch command.

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

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

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

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

BITSB-LOCK: Lockout - Derived DS1 System BITS 2

shelf A lockout is in process on this timing reference.

– Warning Warning Clear the Lockout switch command.

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

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

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

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

BLOCK-TO-FWD: Ethernet Transition from Block to Forward

te206 node Major

BLSR_NOT_SYNC: BLSR ring is out of sync

server One of the nodes in the BLSR/MS-SPRing is out of sync with the other nodes in the ring possibly due to invalid K bytes.

SA Critical Critical Check for OC-N/STM-N module failures. Examine the incoming SONET/SDH overhead with an optical test set to confirm inconsistent or invalid K bytes.

Issue an init command to re-initialize the ring.

BLSR_SYNC_UNKNOWN: BLSR unknown error

server BLSR/MS-SPRing synchronization status is unknown.

– Warning Warning Check for OC-N/STM-N module failures. Examine the incoming SONET/SDH overhead with an optical test set to confirm inconsistent or invalid K bytes.

Issue a sync command to re-synchronize the ring.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-50Force10 N

etworks

Release O

PS4.2.3

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

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

BPSIG: The backplane cannot communicate with other modules

shelf • Module defect.• Backplane slot defect.

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

CFGERR: OSPF configuration parameter mismatch)

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

– Minor Minor Check the configuration.

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


CLFAIL: Cooling fan failure shelf The cooling fan or the power source may have a defect.

– Minor Minor Check the state of the cooling fan or the power.

CLFAN: Fan failed shelf The cooling fan is defective. – Minor Minor Check the state of the cooling fan or the power source. Replace the fan unit, as necesary.

CLRLOOP: Clear loopback ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpeopeop_ctpethernet_ptpsonet_ptpsdh_ptp

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

CMTFLT: Commit Failure te206 node Connection to TE-206 from TransNav GUI failed.

Info Info Manually commit the software.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, A

through C

Release O

PS4.2.3Force10 N

etworks

Page 1-51

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

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

ta200te50

The management server cannot synchronize with the node.

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

CONTROL: Control alarm on MPS IM

te50 The control signal is not present. SA Critical Critical Check connectivity and the multi-protocol serial (MPS) interface module (IM) alarm monitor configuration.

CTS: Clear to send on MPS IM te50 A clear to send (CTS) signal is not yet received on the MPS IM alarm monitoring system.

SA Critical Critical Check connectivity and configuration.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, D through K

Page 1-52Force10 N

etworks

Release O

PS4.2.3

Alarms/Events, D through K

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




SA (Unprotected)

NSA (Protected)

DBCRPT: Database corruption servershelf

The active database fails to start. – Minor Minor This alarm will not be visible due to action taken by the software to recover from this condition. If the alarm generates, contact Force10 ’s Technical Assistance Center (TAC).

DBFAIL: Database failed servershelf

A failure has occurred on the active database upon GCM initialization or some other temporary loss of connectivity. The database is inaccessible as a result of connection failures or abnormal shutdown of database software.

SA Critical Minor If this condition does not resolve itself in a few minutes, contact Force10 ’s Technical Assistance Center (TAC).

DBMIS: Database version mismatch

servershelf

The database engine software version is incompatible with the node software as a result of improper upgrade of software. This condition will not occur during normal upgrade.

Some database operations will fail, but the node is still usable.

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

• Contact Force10 ’s Technical Assistance Center (TAC).

DBRED: Redundant Database failed

servershelf

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

SA Minor Minor • If the standby GCM is rebooting, the condition will clear when the active GCM goes hot.

• Otherwise, reboot the standby GCM and allow time for the GCMs to go hot.

• If no resolution, contact Force10 ’s Technical Assistance Center (TAC).

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-53

DBSIGN: Database signature mismatch

ds3_ptpe1_ptpe3_ptpethernet_ptpsdh_ptpsonet_ptpservershelfta200te50

The database content does not match the node commissioning parameter values. The database is unusable.

The commissioning parameters may have not been provisioned.

A GCM may have been moved from one node to another node.

This alarm is only visible via the node-level CLI when the TransNav server will not connect to the node due to improper commissioning.

SA Major Minor • If the TransNav server connects, and this alarm is present, verify commissioning parameters, then reboot the node.

• If the TransNav server does not connect to the node, use the Craft port on the active GCM to commission the node via CLI, verify commissioning parameters, then reboot the node.

DCCFAIL: Data Communications Channel fail

ds3_ptp(ds_ptp)

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


sonet_ptpsonet_stssdh_hpsdh_lpsdh_ptp

• The DCC on the incoming OC-N has failed.

• The OC-N port is not connected or the fiber is cut along the path.

• The remote link is not active.

NSA Major Minor • Check the OC-N interface. • Check for a fiber cut and OC-N LOS

alarms.• Verify the remote OC-N interface has

Control Data enabled and is active. Filter local alarms as necessary until remote link comes active.

te206 The DCC on the TE-206 has failed.

Info Minor Verify the DCC interface is active.

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




SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-54Force10 N

etworks

Release O

PS4.2.3

DOWN1: Out of service ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpethernet_ptpservershelfsonet_ptpsdh_ptpsonet_serviceta200te50

Unused. – Minor Minor Unused.

DQL1: Degraded quality level ds3_ptpds_ptpe3_ptpshelfsonet_ptpsdh_ptp

The incoming signal has a degraded quality level.

– Minor Minor Check and clean connections.

DS1AIS: Alarm indication signal - DS1

ds1_ptpta200te50te206

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

DS1AIS-TX: Alarm Indication Signal - transmit, DS1

te206 The DS1 output signal contains an AIS.

SA Minor Info Inspect and clear alarms from the downstreamasynchronous equipment.

DS1 Loss of frame - DS1DS1LOF: Loss of frame - DS1

ds1_ptpte206

The DS1 input contains a LOF which is a mismatch of the line format between the Traverse and the upstream asynchronous equipment.

SA Critical Critical If the Line format on the Traverse sets to SF or ESF, verify the line forma (SF, ESF) of the incoming signal from the upstream asynchronous device.

If the Line format on the Traverse sets to Unframed, call Force10 ’s Technical Assistance Center (TAC).





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-55

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.

DS1RAI: Remote alarm indication

ds1_ptpte50te206

• The far-end node has detected a defect signal on an incoming DS1.

• The local node is sending a bad DS1 signal towards the DS-X.

– Warning Warning Verify that the connections between the DS-X and the DS1 module are secure.

Verify that the DS1 signal entering the far end of the SONET network is error-free.

DS1RAI-TX: Remote alarm indication transmitted

te206 • The near-end node has detected a defect signal on an outgoing DS1.



Verify that the DS1 signal exiting the near end of the SONET network is error-free.

DS3AIS: Alarm indication signal - DS3

ds3_ptpds_ptpta200te50 te206

The DS3 input signal contains an AIS.

SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment.

DS3AIS-TX: Alarm Indication Signal - transmit, DS3

te206 The DS3 output signal contains an AIS.

SA Minor Minor Inspect and clear alarms from the downstreamasynchronous equipment.

DS3FEAC-AIS: te206 The DS3 FEAC channel is receiving AIS indication.

Info Check upstream equipment for the source of AIS.

DS3FEAC-EQPT: DS3 FEAC Equipment Failure

te206 The DS3 FEAC channel is receiving Equipment Failure indication.

Info Check upstream equipment for source of Equipment Failure.

DS3FEAC-IDLE: DS3 FEAC Idle Signal

te206 The DS3 FEAC channel is receiving Idle indication.

Info Check upstream equipment for source of Idle.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-56Force10 N

etworks

Release O

PS4.2.3

DS3FEAC-LOF: DS3 FEAC Loss of Frame

te206 The DS3 FEAC channel is receiving Loss of Frame indication.

Info Check upstream e.

DS3FEAC-LOS: DS3 FEAC Loss of Signal

te206 The DS3 FEAC channel is receiving Loss of Signal indication.

Info Check upstream equipment for source of Loss of Signal.

DS3LOF: Loss of frame, DS3 te206 The DS3 input contains a LOF that is a mismatch of the line format between the Traverse and the upstream asynchronous equipment.

SA Critical Critical If the Line format on the Traverse sets to SF or ESF, verify the line forma (SF, ESF) of the incoming signal from the upstream asynchronous device.


DS3RAI: Remote alarm indication

ds3_ptpds_ptpta200te50te206

• The far-end node has detected a defect signal on an incoming DS3.



Verify that the DS3 signal entering the far end of the SONET network is error-free.

DS3RAI-TX: Remote alarm indication transmitted

te206 • The near-end node has detected a defect signal on an outgoing DS3.



Verify that the DS3 signal exiting the near end of the SONET network is error-free.

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

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





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-57

DTR: Data terminal ready on MPS IM

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

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

E1AIS: Alarm indication signal - E1

e1_ptpta200te50

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

E1LOMCAS: Alarm indication signal - E1

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

E1LOMCRC: Alarm indication signal - E1

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

E1RAI: Remote alarm indication

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

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

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

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

te50 SA Critical Critical

E3 AIS: Alarm indication signal - E3

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

E3 RAI: Remote alarm indication

e3_ptp • The far-end node has detected a defect signal on an incoming E3.

• The local node is sending a bad E3 signal towards the E-X.

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

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

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

SA Critical Critical Reboot card and consult Force10 ’s Technical Assistance Center (TAC), if alarm persists.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-58Force10 N

etworks

Release O

PS4.2.3

ENGINE: Engine failure shelf Internal queue engine failure. – Minor Minor Reboot card and consult Force10 ’s Technical Assistance Center (TAC), if alarm persists.

ENGOPRG: Engine operating shelf Internal queue engine is operating again.

– Minor Minor Monitor for further internal queue engine failures.

EQCOMM1: Communication link failed

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

EQFRCSW1: Forced protection switch – Equipment

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

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

EQHICPU: Equipment high CPU usage

shelf NSA Major Major

EQINS: Equipment inserted te206 A new cassette has been inserted into the node

Info Informational only. No action required.

EQINV: Equipment invalid shelf te206

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.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-59

EQMIS: Equipment mismatch shelf te206

Type of equipment plugged in does not match the provisioned type or the module is not allowed in the slot.

Note: GCM, Enhanced GCM, and GCM with integrated optics are considered different module types.

SA Critical Minor Determine if the TransNav server or the node contains the correct module configuration. Please refer to Appendix A—“Module Placement Planning and Guidelines” for module placement details.

If the TransNav server contains the correct module configuration, replace the module with the correct module type. The alarm should be cleared.

If the node contains the correct module configuration, lock, restart, and delete the module. During auto discovery, the correct configuration information will be forwarded to the TransNav server and the alarm should be cleared.

EQPT: Equipment malfunction / failure.

server te206

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 te206

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.

EQRMV: Equipment removed shelfte206

A module is not properly seated or it has been removed.

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

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

ds1_ptp The VT signal demultiplexed from the DS1 contains ERFI-V (RFISVR-V, RFICON-V, and RFIPAY-V).

The far-end node has detected path defects coming from the local site.

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


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





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-60Force10 N

etworks

Release O

PS4.2.3

ETHRING-FAIL: Invalid Ethernet Ring Configuration

te206 A root bridge has not been configured for the ETHRING.

Info Configure a root bridge for the ETHRING.

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.


EXTA-REF3-ALM: Third reference in alarm

shelf Third reference for Derived DS1 System SASE 1 is alarmed due to source signal failure or unavailability due to a LOS, LOF or AIS-L alarm.


EXTA-REF4-ALM: Fourth reference in alarm

shelf Fourth reference for Derived DS1 System SASE 1 is alarmed due to source signal failure or unavailability due to a LOS, LOF or AIS-L alarm.






SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-61

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.


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.


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.


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.


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.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-62Force10 N

etworks

Release O

PS4.2.3

FEP1: Far-end protection failure sonet_ptpsdh_ptpte206

An APS switching channel signal failure has occurred on the protect module coming into the node.

– Minor Minor Check the equipment on the other end of the fiber.

FILE_UPLOAD: Single file transfer

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

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

– Minor Minor Check fire detection equipment and power source.

Check and follow your method of procedures.

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

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

FOPR: Failure of protocol - receive

eoseopsdh_eos

LCAS has detected unexpected behavior by the remote LCAS peer.

SA Critical Critical Check remote peer for proper configuration.

FOPT: Failure of protocol - transmit

eoseopsdh_eos

LCAS has detected unexpected behavior by the remote LCAS peer.

SA Critical Critical Check remote peer for proper configuration.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-63

FORCE_ONLINE ta200 The selected module is forced online. A 50 ms ‘hit’ occurs on the T1 traffic during the switch.

Redundancy is disabled while a force protection switch is active. Any failures to the on-line module are not protected. Therefore, the status LED will be turned yellow to indicate a maintenance condition is active.

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

Clear the switch command.

FORCED: Forced protection switching

shelf te206

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

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


FORCED_ON_PROT: Forced protection switch on protecting unit

shelf te206

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



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

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

Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge.







SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-64Force10 N

etworks

Release O

PS4.2.3

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

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




FORCED_ON_WORK: Forced protection switch on working unit

shelf te206

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



FORCED-EAST: Forced switch applied on east facility

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



FORCED-WEST: Forced switch applied on wast facility

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



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

FWMIS: Firmware mismatch te206 The current running firmware revision does not match the current running software revision.

Major Perform a firmware upgrade to resolve the mismatch.

GENFAIL2: Generator failure shelf Generator has failed. – Minor Minor Check and follow your method of procedures.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-65

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.

GIDERR: LCAS group ID mismatch

shelf A link capacity adjustment scheme (LCAS) group ID member of the VC bundle shows one of the following conditions are present on the path:

• LOP• LOM• AIS• LOS

The VC bundle continues to operate.



• Check the cable and interface.

GIDM: Group ID mismatch eossdh_eoseop

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

H4-LOM: H4 Loss of multiframe

ds3_ptpsdh_hpsdh_lpsdh_ptpsonet_ptpsonet_sts

H4 Loss of multiframe. SA Critical Minor Incoming STS should contain VTs.

HIAIR: High airflow shelf High airflow detected. – Minor Minor Check and follow your method of procedures.

HIHUM: High humidity shelf Humidity is too high. – Minor Minor Check and follow your method of procedures.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-66Force10 N

etworks

Release O

PS4.2.3

HITEMP: High temperature shelf Temperature is too high. – Minor Minor Check that the temperature in the room is not abnormally high.

Ensure that nothing prevents the fan tray from passing air through the Traverse shelf.

Ensure that blank faceplates are inserted in empty slots in the Traverse shelf to help airflow. Blank faceplates must be ordered separately.

Check the condition of the air filter to see if it needs replacement. • If the filter is clean, take the fan tray

assembly out of the Traverse shelf. • Reinsert the fan tray, making sure the

back of the fan tray connects to the rear of the Traverse shelf.

If the fan does not run or the alarm persists, replace the fan tray.

HIWTR: High Water shelf The water level has exceeded the threshold.

– Minor Minor Check and follow your method of procedures.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-67

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


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

– Warning Warning Examine the network for other high order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors.



If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective “working” unit.

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


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

– Warning Warning Examine the network for other high order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors.

Perform loopback tests to isolate theproblem.



HP-LOM: High order path Loss of multiframe

sdh_eossdh_eos_ctp

An error is detected in the paths multiframe indicator.

SA Critical Critical This is an eos_ctp member alarm. If not using LCAS, check that EOS member order matches that of the remote EOS.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-68Force10 N

etworks

Release O

PS4.2.3

HP-MND: High order path Member not deskewable

sdh_eossdh_eos_ctp

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

SA Critical Critical This is an eos_ctp member alarm.

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

HP-SQM: High order path Sequence ID mismatch

sdh_eossdh_eos_ctp

The member sequence number is in error.


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

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


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

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

SA Critical Minor Connect correct payload.

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

HP-RDI: Remote Defect Indication - High order Path


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

– Warning Warning Check STM-N framing source.

See AU-AIS.

See MS-AIS.

HP-RFI: Remote Failure Indication - High order Path

sdh_hpsdh_ptp

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

• The far-end node has detected path defects coming from the local site.



Clear path alarms from the far-end node.

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


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

– Warning Warning Verify your payload connections.

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

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





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events, D

through K

Release O

PS4.2.3Force10 N

etworks

Page 1-69

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


Far end path has a HP-PLM alarm.


Check for far end alarms, especially HP-PLM.

Refer to the recommended actions for HP-PLM.

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


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

– Warning Info Verify your payload connections.

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

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

HP-TIM: Trace identifier mismatch - High order Path


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

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

Match the path trace string on both ends of the path.

HP-UNEQ: Unequipped - High order Path


No payload is received on an activated service.

SA Critical Minor Check your connection.

Connect your proper payload.

Check the service source.

HWFAULT: Hardware fault shelf

te206

A hardware fault has occurred.

This corresponds to the CASFA alarm on the TE-206 node.

SA Critical Critical See Hardware Fault Detection, page 1-71 for further details. Take appropriate action, as necessary.

IDLE: Idle signal detection ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptp eop eop_ctp

Service is not provisioned over the interface.

SA Warning Warning Check the interface. On eop and eop_ctp members, affects DS1 and DS3 port members only.

Check the far-end node.





SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-70Force10 N

etworks

Release O

PS4.2.3

INCOMPATSW: Incompatible software

servershelf

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

– Critical Critical Check the current software versions and compatibility IDs of the modules.

One module’s current software version must be at least the compatibility ID (the lowest software version the other module can work with) of the other module.

Perform software upgrade as necessary for software compatibility.

INTRUDER: Intrusion shelf – Minor Minor

INDICATION: Indication Alarm on MPS IM

te50 SA Critical Critical

KBYTE: Default K byte sonet_ptpsdh_ptp

Far end protection mode mismatch. K1/K2 bytes not sent. For example, a BLSR may have one node configured as a UPSR, and a node in a UPSR would not send the two valid K1/K2 bytes expected by a BLSR system.

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

1 Not supported in this release.

2 Environmental alarm inputs are customized by each operator.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsH

ardware Fault D

etection

Release O

PS4.2.3Force10 N

etworks

Page 1-71

Hardware Fault Detection

Figure 1-27 Hardware Fault Detection for NGE, NGE Plus, and EoPDH Cards

Figure 1-28 Hardware Fault Detection for 10GbE and GbE-10 Cards

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, L through S

Page 1-72Force10 N

etworks

Release O

PS4.2.3

Alarms/Events, L through S

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




SA (Unprotected)

NSA(Protected)

LBC: TXlaser bias current threshold violation

ethernet_ptpsdh_ptpsonet_ptpshelf

TXlaser bias current threshold violation.

For Ethernet only: brief generation of this alarm occurs after a 1:1 equipment PG protection switch because the transmit laser is off on the standby card prior to PG protection switch.

– 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-INACTIVE: eop Remote system not using LCAS NSA Warning Warning Informational for EOP DS1 and DS3 ports only; no action required

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.

Chapter2

Alarm


mended A

ctionsA

larms/Events, L through S

Release O

PS4.2.3Force10 N

etworks

Page 1-73

LFD: Loss of Frame Delineation eossdh_eoseop

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

LINKFAIL: Link failure ethernet_ptpte206 node

• Transmitter/receiver failure.• Fiber connection lost.• A module along the path has

been removed.

SA Critical Critical Check connectors, cables, and modules.

Check Ethernet port configuration, Integrity Status parameter for details. See the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 4—“Ethernet Equipment,” Ethernet Equipment.

LNKBCPTY: Link broadcast message parity error

shelf Unused. – Minor Minor Unused.

LNKBLKCNT: Link block count error


LNKBLKPTY: Link block parity error


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

LNKCSUM: Link checksum error


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

LNKERR: Unrecognized link error


LNKOVFL: Link overflow shelf Unused. Minor Minor Unused.

LNKPAPTY: Link path alarm parity error


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




SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-74Force10 N

etworks

Release O

PS4.2.3

LNKRXCORR: Link receive corruption


LNKRXDROP: Link receive drop


LNKRXLEN: Link receive length error


LNKRXSTAT: Link receive stat count error


LNKTXCORR: Link transmit corruption


LNKTXDROP Link transmit drop


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

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 Force10 ’s 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.






SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-75

LO-TEMP: Internal temp exceeds low alarm threshold

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


LO-VCC: Internal voltage exceeds low alarm threshold

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


LOA: Loss of Alignment eoseopsdh_eos te206 node

Differential Delay exceeded on active EOS member.

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

LOCKOUT: Lockout automatic protection switching

shelf te206 node

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.

LOCKOUT-LPS: Lockout of Protection Ring

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

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

LOCK_WORK1: Lockout automatic protection switching

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









SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-76Force10 N

etworks

Release O

PS4.2.3























SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-77



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






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














SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-78Force10 N

etworks

Release O

PS4.2.3

LOF: Loss of frame ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpeop eop_ctp ta200te50

Framing problem on the incoming signal.

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

Check remote sites for module removal/failure alarms.

Check the cable and interface.

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

SA Major Major Inspect all facilities related to the STS Bundle.

Check remote sites for module removal/failure alarms or disabled Ethernet transmitter.

Check the cable and interface.

shelf Framing problem on the incoming BITS.

– Minor Minor Inspect all facilities related to the BITS.

Check remote sites for BITS alarms.

Check the cable connection.

sonet_ptpsdh_ptp te206 node

Framing problem on the incoming OC-N signal.

On TE-206, framing problem on the incoming and outgoing OC-N signal.

SA Critical Minor Inspect all facilities related to the OC-N link.



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

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





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-79

LOG: Loss of Group eopsdh_eos

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

LOGINFAIL: Login failed servershelf

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

system administrator – persistent login failures could indicate possible hacking.

LOGINSUCC: Login successful servershelf

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

LOGINTERM: Login terminated

servershelf

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

LOL: Loss of link te50 SA Critical Critical

LOM1: Loss of Multiframe, Rx path

ethernet_ptpsdh_ptpshelfeopeop_ctpte206 node

Unused on Traverse.

For TE-206 nodes, this is Loss of Multiframe on Transmit.

SA Critical Minor Unused on Traverse.

te50 SA Warning Warning

LOMCRC: Loss of Multiframe, CRC

eopeop_ctp

Loss of Multiframe CRC on the incoming signal

SA Warning Warning This is an EOP member alarm for E1 port members only. Informational: indicates an incoming LOM condition.

LOM-P: Loss of Multiframe synchronization - STS

eoseos_ctp


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.





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-80Force10 N

etworks

Release O

PS4.2.3

LOM-V: Loss of Multiframe synchronization - VT

eoseos_ctpeop_ctp

An error is detected in the path’s multiframe indicator.

SA Critical Critical This is an eos_ctp or eop_ctp member alarm. If not using LCAS, check that the EOS or EOP member order matches that of the remote EOS or EOP.

Note: This alarm does not apply for Gigabit Ethernet cards.

LOP-P: Loss of Pointer – Path ds3_ptp(ds_ptp)e3_ptpsonet_ptpsonet_sts te206 node

Valid H1/H2 pointer bytes are missing from the STS path overhead.

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





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

ta200te50

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





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-81

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

Valid pointer bytes are missing from the VT overhead.





ta200te50

Valid pointer bytes are missing from the VT overhead.

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




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

LOP-VC1: Loss of Pointer – VC e1_ptpsdh_ptp

Valid pointer bytes are missing from the VC overhead.









SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-82Force10 N

etworks

Release O

PS4.2.3

LOS: Loss of signal ds1_ptpds3_ptp(ds_ptp)e1_ptpe3_ptpta200te50

• Loss of signal on a port interface input.

• The cabling may not be correctly connected to the module, or no signal exists on the line.

• Upstream equipment failure or cable cut may cause this alarm.

SA Critical Critical Check the cable and interface.

Verify that the port is in service.

Use a test set to confirm that a valid signal exists on the line.

shelf Loss of signal on BITS 1 or 2. – Minor Minor Check the cable and interface.

sonet_ptpsdh_ptpte206 node

• OC-N loss of signal. • Fiber may not be correctly

connected to the module, or no signal exists on the line.

• Upstream equipment failure or fiber cut may cause this alarm.

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

Check the fiber connection.

Verify the receive optical levels.


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

sdh_hpsdh-lpsdh_ptp

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

– Warning Warning Examine the network for other low order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors.








SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-83

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

sdh_hpsdh-lpsdh_ptp

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

– Warning Warning Examine the network for other low order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors.




LPBKEQPT: Equipment loopback active

ds1_ptpds3_ptpe1_ptpethernet_ptpsdh_ptpsonet_ptp

Equipment is in active loopback state.

– Warning Warning Validate this state.

Clear loopback, as required.

LPBKFACILITY: Facility loopback active

ds1_ptpds3_ptpe1_ptpe3_ptp eopeop_ctpethernet_ptpsdh_ptpshelfsonet_ptp te206 node

Facility is in active loopback state.

– Warning Warning Validate this state.






SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-84Force10 N

etworks

Release O

PS4.2.3

LPBKINBAND: Inband loopback active

ds3_ptpeop eop_ctp

An inband loopback is active. – Warning Warning Validate this state. On EOP ports, occurs on DS1 and DS3 members only.


LPBKTERM: Terminal loopback active

ds1_ptpds_ptpe1_ptpe3_ptpethernet_ptpsdh_ptpshelfsonet_ptp te206 node

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


LP-LOM: Low order path Loss of multiframe synchronization

sdh_eos sdh_eos_ctp



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


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

sdh_eos sdh_eos_ctp



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


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

sdh_hpsdh-lpsdh_ptp

• Invalid byte in the Low Order path overhead.








SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-85

LP-RDI: Remote Defect Indication - Low order Path

sdh_hpsdh-lpsdh_ptp

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

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

LP-RFI: Remote Failure Indication - Low order Path

sdh_hpsdh-lpsdh_ptp

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

• The far-end node has detected path defects coming from the local site.



Clear path alarms from the far-end node.

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

sdh_hpsdh-lpsdh_ptp

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


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

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

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

sdh_hpsdh-lpsdh_ptp

Far end path has a LP-PLM alarm.


Check for far end alarms, especially LP-PLM.

Refer to the recommended actions for LP-PLM.

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

sdh_hpsdh-lpsdh_ptp

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

– Warning Info Verify your payload connections.

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

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





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-86Force10 N

etworks

Release O

PS4.2.3

LP-SQM: Low order path Sequence ID mismatch

sdh_eossdh_eos_ctp


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


LP-TIM: Trace identifier mismatch - Low order Path

ssdh_hpsdh-lpsdh_ptp

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



LP-UNEQ: Unequipped - Low order Path

sdh_hpsdh-lpsdh_ptp


SA Critical Minor Check your connection.

Connect your proper payload.

Check the service source.

LSDBOVFL1: Exceeded maximum number of LSAs


LSM1: Loss of sync message shelf Unused. – Minor Minor Unused.

LWBATVG: Battery is low shelf The battery is low. – Minor Minor Recharge the battery.

LWFUEL: Low fuel shelf The fuel level is low. – Minor Minor Refuel.

LWHUM: Low humidity shelf The humidity is low. – Minor Minor Check your method of procedures.

LWPRES: Low cable press shelf Cable pressure is low. – Minor Minor Check your method of procedures.

LWTEMP: Low temperature shelf The temperature is too low. – Minor Minor Check the environment for temperature drop.

Check your method of procedures.

LWWTR: Low water shelf The water level is too low. – Minor Minor Check your method of procedures.





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-87

MANUAL: Manual protection switching

shelte206 node

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


MAN_ON_PROT: Manual protection switching

shelfte206 node

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


MAN_ON_WORK: Manual protection switching

shelfte206 node

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


MAN-TX-OFF: Transmitter manually disabled


Operator disabled the optical laser.


MAN-TX-ON: Transmitter manually enabled


Operator enabled the optical laser.


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

MISC: Misc (default) shelf – Minor Minor

MND: PDH member not de-skewable.

eop eop_ctp

Differential Delay exceeded on EOP member; the member was removed from the group.

SA Critical Minor This is an eop and eop_ctp member alarm. Check the EOP member status to determine which paths have exceeded the delay and reroute them.

MND-P: Member not de-skewable - STS

eoseos_ctp


SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them.





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-88Force10 N

etworks

Release O

PS4.2.3

MND-V: Member not de-skewable - VT

eoseos_ctp


SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them.

Note: This alarm does not apply to Gigabit Ethernet cards.

MPU_BATTERY_A: Battery A alarm

ta200 SA Critical Critical

MPU_BATTERY_B: Battery B alarm


MS-AIS: Alarm Indication Signal - Multiplex Section

sdh_ptp An upstream failure occurred at the multiplex section layer.



Verify your multiplex section payload connections.





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-89

MS-BERSD: BER signal degrade - Multiplex Section

sdh_ptp • The BER on the incoming STM-N line has exceeded the signal degrade threshold.

• A connector in the STM-N optical link could be dirty.

• An STM-N module hardware problem could exist.


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






If the problem persists, contact Force10 ’s Technical Assistance Center (TAC).

MS-BERSF: BER signal fail - Multiplex Section

sdh_ptp • The BER on the incoming STM-N line has exceeded the signal fail threshold.

• A connector in the STM-N optical link could be dirty.

• An STM-N module hardware problem could exist.


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










SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-90Force10 N

etworks

Release O

PS4.2.3

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.

NETSYNC: Network object synchronization failure

server Master network objects (e.g., alarm profiles) are out of synchronization with propagated node objects.

– Warning Warning Resynchronize using the TransNav GUI.

NEWLSA1 shelf Unused. – Minor Minor Unused.

NO_OUTPUT: Output Signal Activity Failure


NO_PRIMARY_SERVER: No primary TransNav server

server The primary server was not found.

SA Major Warning Check connectivity.

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





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-91

NODEEQMIS: Node equipment mismatch

server Server-Agent equipment mismatch.

SA Critical Critical Determine if the TransNav server or the node contains the correct module configuration.

If the TransNav server contains the correct module configuration, use the node-level CLI to lock, restart, and delete the module. The alarm should be deleted.

If the node contains the correct module configuration, delete the node.

During autodiscovery, the correct information will be forwarded to the TransNav server and the alarm should be deleted.

NODEIDMIS: Node ID mismatch

sonet_ptpsdh_ptp

The node ID selected is already in use.

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

NODESYNC: Node synchronization

server • Discovery of and synchronization with a new node.

• GCM protection switch.

– Warning Warning • Wait for node synchronization to complete.

• Check network server connections.

NO-REMOTE-LCAS: No remote LCAS

eos eopsdh_eosshelf

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

– Warning Warning Enable LCAS on the remote nodes’ EOS or EOP.

Check remote peer configuration, capability, and connectivity.

NPM: No provisioned members eoseopsdh_eoslag

No members have been provisioned.

SA Critical Critical Add CTP members to the EOS or EOP port.

Add ports to the LAG.

OSPF-AIMM: OSPF Area ID Mismatch

te206 node The OSPF Area configuration does not match the configuration of other routers in the network.

Info Configure OSPF Area to be consistent in the network.





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-92Force10 N

etworks

Release O

PS4.2.3

OSPF-DIMM: OSPF Router Dead Interval Mismatch

te206 node Info

OSPF-HIMM: OSPF Hello Interval Mismatch

te206 node Info

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

– Minor Minor Validate that the door should be open.

Close the door, as necessary.

OPR: Optical power received threshold violation


Received optical power does not meet guaranteed value.

– Warning Warning Check interface.

OPT: Optical power transmitted threshold violation


Current is outside guaranteed bounds.

For Ethernet only: brief generation of this alarm occurs after a 1:1 equipment PG protection switch because the transmit laser is off on the standby card prior to PG protection switch.

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

OVERTEMP: Fan tray temperature has exceeded a maximum value

shelf Fan tray temperature has exceeded 56ºC.

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

Replace the fan tray air filter.





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-93

OVERVOLTAGE_A1: Exceeded a maximum voltage value - Enhanced GCM_A

shelf GCM_A has triggered due to an over voltage condition.

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

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

OVERVOLTAGE_B1: Exceeded a maximum voltage value - Enhanced GCM_B

shelf GCM_B has triggered due to an over voltage condition.

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

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

PCASQLCH1: PCA channel squelched

sonet_ptpsdh_ptp

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

– Minor Minor Clear the protection switch.

Check equipment ring topology configuration.

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

ds3_ptp(ds_ptp)e3_ptpsdh_hpsdh-lpsdh_ptpsonet_sts

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

sonet_ptpsdh_ptp

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

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

ds3_ptp(ds_ptp)e3_ptp

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

sonet_ptpsdh_ptp

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





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-94Force10 N

etworks

Release O

PS4.2.3

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


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

sonet_ptpsdh_ptp

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

PKTRETX1: An OSPF packet has been retransmitted


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

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

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

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


Unused. SA Critical Minor Unused.

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


Unused. – Warning Info Unused.

PLCR: Partial loss of capacity - receive

eoseopsdh_eos

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

PLCT: Partial loss of capacity - transmit

eoseop sdh_eos

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

PLINESQL1: Persistent line squelching

sonet_ptpsdh_ptp

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






SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-95

PLM:Payload label mismatch received

ds3_ptp(ds_ptp)e3_ptpsonet_ptpsonet_sts

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




PLM-P: Path label mismatch ta200te50 te206 node

Payload label mismatch on the path.

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

PLM-V: Payload label mismatch received

ds1_ptpds3_ptp(ds_ptp)e3_ptpshelfsonet_ptpsonet_vtsonet_stste206 node

• Invalid byte in the path overhead.




te50 • Invalid byte in the path overhead.


– Warning Warning Connect correct payload.


PLM-VC: Payload label mismatch received - VC

e1_ptpsdh_ptp

• Invalid byte in the path overhead.








SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-96Force10 N

etworks

Release O

PS4.2.3

PMCFG: PM configuration error

ds3_ptp(ds_ptp)e1_ptpe3_ptpethernet_ptpsonet_ptpsdh_ptp

PM configuration is incorrect. – Warning Warning Check configuration.

PMDATALOST: Performance data lost

servershelf

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

POWER: Commercial power failure

shelf The commercial power source has failed.


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

– Info Info Check the equipment.

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

PWFAIL-A: Power problem—power input A failed

shelfte206 node

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


PWFAIL-B: Power problem —power input B failed

shelf te206 node

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


PWR-48: 48 VDC power supply failure

shelfte206 node

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


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

SA Critical Critical Contact Force10 ’s Technical Assistance Center (TAC).





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-97

RAI eopeop_ctp

The far-end node has detected a framing problem on an incoming signal.

- Warning Warning Check the paths associated with the EOP members

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

RECTHIGH2: Rectifier high voltage

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

RECTLOW2: Rectifier low voltage

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

RMLF: Remote link failure lag A failure has occurred at the remote end of the link.

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

REMOTE-LINKFAIL: Remote loss of client signal

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

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

RESOURCE_MISMATCH: STSRM/VTRM Resource Mismatch

shelf An uncommon alarm. The resource mismatch may occur as a result of a non-active GCM controller condition. The management system configuration does not match that of the line card.

SA Critical Minor Contact Force10 ’s Technical Assistance Center (TAC).





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-98Force10 N

etworks

Release O

PS4.2.3

RFI-L: Remote failure indication – Line

ds3_ptp(ds_ptp)ta200te50

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

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

– Warning Warning Check module/port.

Check cable and connections.

Check for and resolve LOS, LOF, and AIS alarms in the far-end node.

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

– Warning Warning Check module/port.

Check for and resolve LOS, LOF, and AIS-L alarms in the far-end node.

Verify the output of the local OC-N module for level degradation/dirty optical connectors.


Check the fiber connection on adjacent equipment.

RFI-P: Remote failure indication – Path


ta200te50

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




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

sonet_ptp sonet_sts te206 node

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


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


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





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-99

RFI-V: Remote failure indication

ds1_ptpds3_ptp(ds_ptp)sonet_ptpsonet_vtsonet_stsshelfta200te50te206 node

The VT signal demultiplexed from the DS1 contains an RFI-V.

The far-end node has detected VT path defects coming from the local site.



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

e3_ptp1

sdh_ptpThe low order signal demultiplexed from the STM contains an RFI-V.

The far-end node has detected low order path defects coming from the local site.



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

RFI-VC: Remote failure indication

e1_ptpsdh_ptp

• The low order signal demultiplexed from the STM contains an RFI-VC.

• The far-end node has detected low order path defects coming from the local site.



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





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-100Force10 N

etworks

Release O

PS4.2.3

RFICON: Remote failure indication – Connectivity defect

ds3_ptp(ds_ptp)sonet_ptpsonet_sts

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

SA Warning Info Verify your payload connections.

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

Refer to the recommended actions for UNEQ and TIM.

e3_ptpsdh_ptp

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


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

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

RFICON-V: Remote failure indication – Connectivity defect

ds1_ptpds3_ptp(ds_ptp)shelfsonet_ptpsonet_vtsonet_sts

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


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

Refer to the recommended actions for UNEQ and TIM.

e3_ptpsdh_ptp

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




RFICON-VC: Remote failure indication – Connectivity defect

e1_ptpsdh_ptp

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








SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-101

RFIPAY: Remote failure indication – Payload defect

ds3_ptp(ds_ptp)sonet_ptpsonet_sts

Far end path has a PLM-P alarm.


Check for far end alarms, especially PLM-P.

Refer to the recommended actions for PLM.

e3_ptpsdh_ptp

Far end path has a HP-PLM alarm.


Check for far end alarms, especially HP-PLM.

Refer to the recommended actions for HP-PLM.

RFIPAY-V: Remote failure indication – Payload defect


Far end path has a PLM-V alarm.


Check for far end alarms, especially PLM-V.

Refer to the recommended actions for PLM.

e3_ptpsdh_ptp





RFIPAY-VC: Remote failure indication – Payload defect

e1_ptpsdh_ptp









SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-102Force10 N

etworks

Release O

PS4.2.3

RFISVR: Remote failure indication – Server defect

ds1_ptpds3_ptp(ds_ptp)sonet_ptpsonet_sts

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


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

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

e3_ptpsdh_ptp

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


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

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

RFISVR-V: Remote failure indication – Server defect


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


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

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

e3_ptpsdh_ptp

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


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

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

RFISVR-VC: Remote failure indication – Server defect

e1_ptpsdh_ptp

The far end path has a TU-AIS or TU-LOP alarm.


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

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





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-103

RFLF: Remote Line Failure te206 node The far end GbE interface is detecting a loss of signal.

Info Info Check the GbE fiber.

RMTLOOP: FEAC Loopback and FDL Loopback

te206 node The far end DS3 interface has initiated a remote loopback using the FEAC channel or the FDL channel.

Informational only. No action required.

RLSD: Receive Line Signal Detect on MPS IM

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

RS-TIM: Trace identifier mismatch

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



RTS: Request to send on MPS IM

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

SENSORFAIL: Thermal sensor failure

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

– Major Major Check that the temperature of the room or equipment is not abnormally high.

Contact Force10 ’s Technical Assistance Center (TAC) for assistance if the temperature is normal and this failure persists.

SERVER_LOGINFAIL: Server login to node failed

server Node login authentication failed.

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

persistent login failures could indicate possible hacking.

SERVER_ROLE servershelf

Event identifies the server role as primary or secondary.


SETOPER: Set operation performed

servershelf

A set operation has been performed.






SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-104Force10 N

etworks

Release O

PS4.2.3

SFO1: Sync frequency offset ds3_ptp(ds_ptp)sonet_ptp

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

e3_ptpsdh_ptp

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

SFPFAIL: SFP Fault te206 node A fault has been detected with the SFP.

Critical Minor Replace the faulty SFP.

SFPMIS: SFP mismatch ethernet_ptpsdh_ptpsonet_ptpshelfte206 node

There is a mismatch on the SFP interface.

– Critical Minor Check interface.

SFPRMV: SFP removed ethernet_ptpsdh_ptpsonet_ptpshelf

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

SFP-UNKNOWN: ? te206 node An SFP has been detected that is not certified for use with the system.

SA Critical Minor Replace the unknown SFP with a Force10 certified SFP.

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.

SNTP-FAIL te206 node The TE-206 node cannot communicate with the SNTP server.

Check the availability of the SNTP server.

Verify the TE-206 SNTP configuration.

Verify network connectivity from the TE-206 to the SNTP server.





SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-105

SQLCHTBL1: Squelch table mismatch

sonet_ptpsdh_ptp

• Alarm is raised as a circuit is being added to or deleted from a BLSR.

• May also be caused by incomplete provisioning of the STS channels.

– Minor Minor If a circuit is being added, the alarm will clear after the circuit has been completely built into the ring by adding all the necessary cross-connections.

Be sure that the STS channels have been properly provisioned. Check equipment ring topology configuration.

SQM1: Sequence number change

ethernet_ptpshelfeopeop_ctp te206 node

Unused for Traverse.

The TE-206 member sequence number is in error.

SA Critical Minor Unused for ethernet_ptp and shelf.

Member alarm for virtual concatentation faults on EOP members.

SQM-P: Sequence ID mismatch- STS

eoseos_ctp


SA Critical Critical This is an eos_ctp member alarm. If non-LCAS, check that the order of members in the remote EOS matches the local order.

SQM-V: Sequence ID mismatch- VT

eoseos_ctp


SA Critical Critical This is an eos_ctp member alarm. If non-LCAS, check that the order of members in the remote EOS matches the local order.

Note: This alarm does not apply to Gigabit Ethernet cards.

SSF: Server Signal Fail shelf All LCAS VC bundle members have failed. Also see path alarms for each VC bundle member (facility). The VC bundle operational state is set to Disabled until at least one member returns.



• Check the cables and interfaces.





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-106Force10 N

etworks

Release O

PS4.2.3

SUM-V: VT Alarm Summary te206 node One or more alarms exists for VT paths within the STS-1.

Critical Minor Check the conditions of the VT paths within the STS-1.

SVC_STATUS1: Service status report

servershelf

Unused. – Info Info Unused.

SWCRPT: Software corruption servershelf

Software did not load or loaded with errors.

SA Critical Minor Contact Force10 ’s Technical Assistance Center (TAC).

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

– Info Info Contact Force10 ’s Technical Assistance Center (TAC).

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

SWITCH_TO_PROT: Traffic switch to Protection

shelf te206 node

Traffic has switched to the standby module, port, or channel for a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group.


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

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







SA (Unprotected)

NSA(Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-107

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

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


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

degraded performance or other relevant alarm conditions.

SWITCH_TO_WORK: Traffic switch to Working

shelf te206 node

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


SWMIS: Software version mismatch

all objects te206 node

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

– Minor Minor Reinstall correct software.

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


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

SYSREF: System reference lock failed

shelf te206 node

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

SYSREF_EVENT: System lost reference lock

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

SYNCFAIL2: Synchronization reference failure

sonet_ptpsdh_ptp

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

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





SA (Unprotected)

NSA(Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, T through TZ

Page 1-108Force10 N

etworks

Release O

PS4.2.3

Alarms/Events, T through TZ

Table 1-11 Alarms, Events and Recommended Actions, T through TZ




SA (Unprotected)

NSA (Protected)

TCA: Threshold crossing alert ds1_ptpds3_ptp(ds_ptp)e3_ptpethernet_ptpsonet_ptpsdh_ptp te206 node

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

For a list of corresponding TE-206 alarms, see Alarms/Events, TE-206, page -89

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

TEMP: Internal temperature threshold violation


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

TEMPCRIT: Temperature critical

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

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

TEMPWARN: Temperature warning

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

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

TIM: Trace identifier mismatch ds3_ptp(ds_ptp)e3_ptpsonet_ptpsdh_ptp

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



Chapter2

Alarm


mended A

ctionsA

larms/Events, T through TZ

Release O

PS4.2.3Force10 N

etworks

Page 1-109

TIM-P: Trace identifier mismatch - Path

e3_ptpsonet_ptpsonet_sts te50 te206 node

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



TIM-S: Trace identifier mismatch - Section

e3_ptpsonet_ptpte50

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

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

Match the section trace string at each end.

TIM-V: Trail trace mismatch - VT

ds1_ptpds3_ptp(ds_ptp)e3_ptpshelfsdh_ptpsonet_ptpsonet_vtsonet_stste50

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

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

Match the VT trail trace string at each end.

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

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

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

Match the VT trail trace string at each end.

TIMEDOUT: Session terminated

servershelf

The user session has been idle for two hours.

– Info Info Start a new user session.

Table 1-11 Alarms, Events and Recommended Actions, T through TZ (continued)




SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-110Force10 N

etworks

Release O

PS4.2.3

TIMEOUTWARN: Session terminate warning

servershelf

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

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

TIU-V: Trail trace mismatch - VT

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

TLC: Total loss of capacity lag All ports in the LAG are down. SA Critical Critical Check for proper cabling and that local and remote port configurations match.

TLCR: Total loss of capacity - receive

eos eop [sdh_eos

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

TLCT: Total loss of capacity - transmit

eos eop sdh_eos

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

TOOMANYEVENTS: Too many events in the server

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

TOPOMIS: Topology mismatch sonet_ptpsdh_ptp

Topology is mismatched. – Minor Minor Check topologies.

TOXIC1: Toxic gas detected shelf Toxic gas detected. – Minor Minor Check and follow your method of procedures

TSS-ABS-DIFF: Timing internal clock failure


TSS-EXT-LOCK: Timing external source lock failed on standby


TSS-EXT-MAX: Timing external source PPM offset exceeds acceptable range






SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-111

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 Force10 ’s 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.


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

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


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

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


TSS-FRC: Forced protection switching on timing

shelf te206 node

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

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


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

shelf te206 node

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






SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-112Force10 N

etworks

Release O

PS4.2.3

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

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


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

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




















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.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-113

TSS-MAN: Manual protection switching on timing

shelfte206 node

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

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

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

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


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

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


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

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


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

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


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

shelf All BITS or line timing sources are alarmed.

– Major Major Restore primary and secondary timing references.

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

shelf All BITS or line timing sources are alarmed.

– Major Major Restore primary and secondary timing references.

TSS-REFS: 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.






SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm


Page 1-114Force10 N

etworks

Release O

PS4.2.3

TSSALM: Timing reference alarm

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

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

TSSSETS: SETS status shelf Timing subsystem event. – Info Info Informational; no action required.

TU-AIS: Alarm indication signal – Tributary Unit)

sdh_hpsdh-lpsdh_ptp

An upstream failure occurred at the tributary unit path layer.



Verify your tributary unit payload connections.

TU-LOP: Loss of Pointer – Tributary Unit

sdh_hpsdh-lpsdh_ptp

Valid pointer bytes are missing from the tributary unit overhead.

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




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

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

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

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

1 Environmental alarm inputs are customized by each operator.





SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events U

through Z

Release O

PS4.2.3Force10 N

etworks

Page 1-115

Alarms/Events U through Z

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




SA (Unprotected)

NSA (Protected)

UNDERVOLTAGE_A1: Below the minimum voltage value - Enhanced GCM_A

shelf GCM_A has triggered due to an under voltage condition.

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


UNDERVOLTAGE_B1: Below the minimum voltage value - Enhanced GCM_B

shelf GCM_B has triggered due to an under voltage condition.

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


UNEQ: Rx Path unequipped code received

ethernet_ptp No payload is received on an activated service.

SA Critical Minor Check your interface connection.

Connect your proper payload and service source.

UNEQ-P: Unequipped code signal label received

ds3_ptp(ds_ptp)e3_ptpsonet_ptpsonet_stste50 te206 node




UNEQ-P-TX: Unequipped code signal label transmitted

te206 node No payload is transmitted on an activated service.


Connect your proper payload and service destination.

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events U through Z

Page 1-116Force10 N

etworks

Release O

PS4.2.3

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

ds1_ptpds3_ptp(ds_ptp)shelfsonet_ptpsonet_vtsonet_stste50 te206 node




e3_ptpsdh_ptp

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

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

e1_ptpsdh_ptp




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

VCC: Internal voltage threshold violation


Supply voltage doe not meet guarantee.

– Warning Warning Call Force10 ’s Technical Assistance Center.

VENTFAIL2: Ventilation system failure

shelf Ventilation system has failed. – Minor Minor Check and follow your method of procedures.

WARMREBOOT shelf Module warm reboot request in process. Until complete (within 60 seconds), module does not respond to provisioning requests or protection switch triggers.

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

WLMIS: Configured wavelength mismatch with hardware

sdh_ptpsonet_ptp TE-206 node

Incorrect provisioning. SA Major Minor Check interface and configuration.

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




SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA

larms/Events U

through Z

Release O

PS4.2.3Force10 N

etworks

Page 1-117

X86_ABORT shelf Receiving X.86 encapsulation abort condition.

SA Critical Minor Check interface and configuration.

X86_CRC shelf Receiving X.86 encapsulation CRC errors.

SA Critical Minor Check interface and configuration.

XPT-FAIL-RX: Receiver connection failure

ethernet_ptp Link Integrity detected transport failure in the receive direction.

SA Critical Critical Check EOS members for path alarms.

XPT-FAIL-TX: Transmitter connection failure

ethernet_ptp Link Integrity detected transport failure in the transmit direction.


XPTRX: Receive transport failure

lag Link Integrity detected transport failure in the receive direction.


XPTTX: Transmit transport failure

lag Link Integrity detected transport failure in the transmit direction.


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

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




SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TA200

Page 1-118Force10 N

etworks

Release O

PS4.2.3

Alarms/Events, TA200

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




SA (Unprotected)

(Protected)

T2OOF: T2 Line - Out of frame ta200 T2 is out of frame. SA Critical Critical Check the configuration.

T2XBIT: T2 Remote (Far-End) Failure

ta200 On T2OOF alarm detection, the remote PM13 sends T2XBIT out the T3 interface.

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

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

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

TA200_PM13E_G747FESmry: PM13e T3 747 Out of frame

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

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

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

SA Critical Critical Check the remote end configuration.

Chapter2

Alarm


mended A

ctionsA

larms/Events, TE-206

Release O

PS4.2.3Force10 N

etworks

Page 1-119

Alarms/Events, TE-206

The following list contains alarms for the TE-206 nodes and the corresponding TransNav alarms. This information is needed to change the severity of alarms on the TE-206 node.

Modification of alarm severity and SA/NSA attributes for TE-206 alarms can only be done on TE-206 nodes.

Table 1-14 Alarms, Events and Recommended Actions, TE-206

TE-206 AlarmCorresponding

TransNavAlarm(s)

Probable CauseService

Affecting Default


SA (Unprotected)

NSA (Protected)

AIS: Alarm Indication Signal

DS3 AISDS1 AISDS3 AIS-TX DS1 AIS-TX

The input and export signals on a DS1 or DS3 interface contains an AIS.

SA Minor Info Inspect and clear alarms from the upstream and downstream asynchronous equipment.

AIS-L: Alarm Indication Signal - Line

AIS-L The input and export signals on a DS1 or DS3 interface contains an AIS.

SA Minor Info Check the equipment (module/port) upstream and downstream.

Clear alarms.

AIS-P: Alarm Indication Signal - Path

AIS-PAIS-P-TX

The STS signal demultiplexed from the DS3 contains an AIS which can result from an upstream or downstream failure along the STS path.


Clear alarms.


AIS-V: Alarm Indication Signal - VT

AIS-V An upstream failure occurred at the VC path layer.


Clear alarms.

Verify your VT payload connections

APSB: APS Protection Switch Byte Failure

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

Minor Check for OC-N module failures

Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes.

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TE-206

Page 1-120Force10 N

etworks

Release O

PS4.2.3

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

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

Minor

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

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

AUTOSWSYNCH: Automatic Switch Synchronization

AUTOSWSYNCH A protection switch to a new timing source has occurred.

Info Check the timing sources for alarms.

CASALIEN: Alien Cassette

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

Critical Plug in a valid piece of equipment.

CASFA: Cassette Fuse Failure

HWFAULT: Hardware fault

A hardware fault has occurred. SA Critical Minor Take appropriate action, as necessary.

CASFLT: Cassette Failure EQPT: Equipment malfunction / failure

A hardware failure has occurred on the reporting module.

SA Critical Minor Check and reseat equipment. If this fails to clear the alarm, replace the equipment if necessary.

CASINS: Cassette Inserted

EQINS A new cassette has been inserted into a TE-206 node.

Info

Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued)


TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-121

CASMM EQMIS Type of equipment plugged in does not match the provisioned type or the module/cassette is not allowed in the slot.

Major Determine if the TE-206 node contains the correct module configuration.

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.

CASRMVD: Cassette Removed

EQPT A cassette has been removed from a TE-206 node.

Info

CMTFLT: Connection to TransNav GUI failed

CM TFLT Connection to TE-206 from TransNav GUI failed.

Info Check for and resolve any firmware mismatch.

Manually commit the software.

EOC: Embedded Operations Channel Failure

DCCFAIL • 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.

Minor • Check the OC-N interface. • Check for a fiber cut and OC-N LOS

alarms.• Verify the remote OC-N interface has

Control Data enabled and is active. Filter local alarms as necessary until remote link comes active.

ETHBLKTOFWD: Ethernet Transition from Block to Forward

BLOCK-TO-FWD Ethernet port RSTP state has changed from blocking to forwarding.

SA Major Informational only. No action required.

ETHRINGFAIL: Invalid Ethernet Ring Configuration

ETHRING-FAIL A root bridge has not been configured for the ETHRING.

Info Configure a root bridge for the ETHRING.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TE-206

Page 1-122Force10 N

etworks

Release O

PS4.2.3

EXBER: Excessive Bit Error Rate

BERSF-L (OC48/OC12/OC3)BERSF-P (HO path)BERSF-V (VT1.5)

• The BER on the incoming OC-N line has exceeded the signal fail threshold.

• A connector in the OC-N optical link may be dirty.

• An OC-N module hardware problem may exist.


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

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






Examine the network for other path bit error rate problems and retrieve PM data to find a possible common source of the bit errors.



FDLLPBK: FDL Loopback

RMTLOOP Far end DS1 interface has initiated a remote loopback using the FDL channel.

Info

FEACAIS: DS3 FEAC AIS

DS3FEAC-AIS The DS3 FEAC channel is receiving AIS indication.

Info Check upstream equipment for source of AIS.

FEACEQFLTNSA: DS3 FEAC Equipment Failure (NSA)

DS3FEAC-EQPT(use SA/NSA)

The DS3 FEAC channel is receiving Equipment Failure indication.

Info Check upstream equipment for source of Equipment Failure.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-123

FEACEQFLTSA: DS3 FEAC Equipment Failure (SA)

DS3FEAC-EQPT (use SA/NSA)

The DS3 FEAC channel is receiving Equipment Failure indication.

SA Info Check upstream equipment for source of Equipment Failure.

FEACIDLE: DS3 FEAC Idle Signal

DS3FEAC-IDLE The DS3 FEAC channel is receiving Idle Signal indication.

Info Check upstream equipment for source of Idle.

FEACLOS: DS3 FEAC LOS

DS3FEAC-LOS The DS3 FEAC channel is receiving Loss of Signal indication.

Info Check upstream equipment for source of Loss of Signal.

FEACLPBK: FEAC Loopback

RMTLOOP Far end DS3 interface has initiated a remote loopback using the FEAC channel.

Info Informational only. No action requried.

FEACOOF: DS3 FEAC OOF

DS3FEAC-LOF The DS3 FEAC channel is receiving Loss of Frame indication.

Info If the Line format on the Traverse sets to SF or ESF, verify the line forma (SF, ESF) of the incoming signal from the upstream asynchronous device.


FEPRLF: Far End Protection Line Failure

FEP An APS switching channel signal failure has occurred on the protect module coming into the node.

– Minor Check the equipment on the other end of the fiber.

FRCDSWRING1: Forced Switch to Ring 1

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

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




TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TE-206

Page 1-124Force10 N

etworks

Release O

PS4.2.3

FRCDSWRING2: Forced Switch to Ring 2

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

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


FRCDSWSYNC: Forced Sync Switch

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

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

FRCDWKSWBK: Forced protection switch on protecting unit

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

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


FRCDWKSWPR: Forced protection switch on working unit

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

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


FWMM: Firmware Mismatch

None. This is a te206 alarm only

The current running firmware revision does not match the current running software revision.

Major Perform firmware upgrade to resolve firmware mismatch.

HLDOVR: Holdover TSS-HOLDOVER There are no available external references so the GCMA (or GCMB) is referencing the local oscillator.

(SA) Major If this alarm persists for more than 5 minutes, contact Force10 ’s Technical Assistance Center (TAC).

HWFLT: Description is Fault specific

EQPT A hardware failure has occurred on the reporting cassette.

SA Critical Minor Check and reseat the equipment or cassette. If this fails to clear the alarm, replace the cassette if necessary.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-125

HWMM: Hardware Mismatch

EQMIS Type of equipment plugged in does not match the provisioned type or the module is not allowed in the slot.

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

LOA: Loss of Alignment LOA Differential Delay exceeded on active EOS member.

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

LOC: Loss of Carrier LINKFAIL • Transmitter/receiver failure.• Fiber connection lost.• A module along the path has

been removed.

SA Critical Minor Check connectors, cables, and modules.


LOCKOUTOFPR: Lockout of Protect

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

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

LOCKOUTRING2: Lockout of Ring 2

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

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



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TE-206

Page 1-126Force10 N

etworks

Release O

PS4.2.3

LOF: Loss of Frame LOF (OC48/OC12/OC3)DS1LOFDS3LOF

Framing problem on the incoming OC-N signal.

SA Critical Minor Inspect all facilities related to the OC-N link.



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


LOL: Loss of Light LINKFAIL • Transmitter/receiver failure.• Fiber connection lost.• A module along the path has

been removed.



LOM: Loss of Multiframe LOM Loss of Multiframe on Transmit. SA Critical Minor Unused in Traverse.

LOP: Loss of Pointer Path LOP-P Valid H1/H2 pointer bytes are missing from the STS path overhead.








TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-127

LOP-V: Loss of Pointer VT Path

LOP-V Valid pointer bytes are missing from the VT overhead.





LOS: Loss of Signal LOS • OC-N loss of signal. • Fiber may not be correctly

connected to the module, or no signal exists on the line.

• Upstream equipment failure or fiber cut may cause this alarm.

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

Check the fiber connection.

Verify the receive optical levels.


LOSYNC: Loss of Synchronization

LINKFAIL • Transmitter/receiver failure.• Fiber connection lost.• A module along the path has

been removed.



LPBK-FAC: Facility Loopback Active

LPBKFACILITY Facility is in active loopback state.

Info Validate this state.


LPBK-TERM: Terminal Loopback Active

LPBKTERM A terminal loopback is active. Info Validate this state.


MANSWRING1: Manual Switch to Ring 1

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

Info Informational; no action required.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TE-206

Page 1-128Force10 N

etworks

Release O

PS4.2.3

MANSWRING2: Manual Switch to Ring 2

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


MANSWSYNC: Manual protection switching on timing

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

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

MANWKSWBK: Manual Switch to Working

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


MANWKSWBK: Manual Switch to Working

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


MANWKSWPR: Manual Switch to Protect

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

Info Info Informational; no action required.

MANWKSWPR: Manual Switch to Protect

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

Info Info Informational; no action required.

OSPFAIMM: OSPF Area ID Mismatch

OSPF-AIMM The OSPF Area configuration does not match the configuration of other routers in the network.

Info Configure the OSPF Area to be consistent in the network.

OSPFHIMM: OSPF Hello Interval Mismatch

OSPF-HIMM The OSPF Hello Interval does not match the configuration of other routers in the network.

Info Configure the OSPF Hello Interval to be consistent in the network.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-129

OSPFRDIMM: OSPF Router Dead Interval Mismatch

OSPF-DIMM The OSPF Router Dead configuration does not match the configuration of other routers in the network.

Info Configure OSPF Router Dead to be consistent in the network.

PLM-P: Payload Label Mismatch

PLM-P Payload label mismatch on the path.

SA Critical Minor Verify that the payload is the same as the provisioned payload/service.

PLM-V: VT Payload Label Mismatch VT Path

PLM-V • Invalid byte in the path overhead.


Minor Connect correct payload.


PWRA: Low -48V Power Side A

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

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

PWRB: Low -48V Power Side B

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

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

PWRHI: Excessive (in Absolute Value) - 48V Power

PWR-48 (in Traverse documentation )

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

Major Check and follow your method of procedures.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TE-206

Page 1-130Force10 N

etworks

Release O

PS4.2.3

RAI: Remote Alarm Indication

DS3RAIDS1RADS3RAI-TX DS1RAI-TX

• The far-end node has detected a defect signal on an incoming DS3. For TE-206 nodes, the defect signal is detected on incoming or outgoing DS3.

• The local node is sending a bad DS3 signal towards the DS-X. For TE-206 nodes, the defect signal is detected on incoming or outgoing DS3.

Info • Verify 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. For TE-206 nodes, verify the DS3 signals entering or exiting the far end of the SONET network are error-free.

RFI-L: Remote Failure Indication - Line

RFI-L • 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.

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

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


Info • 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.

RFI-V: Remote Failure Indication - VT

RFI-V 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.

Info • 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.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-131

RFLF: Remote Line Failure

None. This is a te206 alarm only.

The far end GbE interface is detecting a Loss of Signal.

Info Info Check the GbE fiber.

RFOFF: Remote Fault Offline

Info

SD: Bit ErrorRate signal degrade – Line

BERSD-L (OC48/OC12/OC3)BERSD-P (HO Path)BERSD-V (VT1.5)

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

SA Critical Minor • Check cable connectors and module ports.

• If an EC-1 module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective “working” unit.

• Check the remote (source) Transmit and cable connection.

SFPALIEN: Alien SFP SFP-UNKNOWN An SFP has been detected that is not certified for use with the system.

SA Critical Minor Replace the unknown SFP with a Force10 certified SFP.

SFPFLT: SFP Fault SFPFAIL A fault has been detected with the SFP.

SA Critical Minor Replace the faulty SFP.

SFPMM: SFP Mismatch SFPMIS There is a mismatch on the SFP interface.

SA Critical Minor Check interface.

SNTPFLT: SNTP Time Failure

SNTP-FAIL The TE-206 cannot communicate with the SNTP server.

Minor • Check the availability of the SNTP server.

• Verify the TE-206 SNTP configuration.• Verify network connectivity from the

TE-206 to the SNTP server.

SOFTMM: Software Version Mismatch

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

Major Reinstall correct software.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-132

SQM: Sequence number change

SQM Unused SA Critical Minor Unused for ethernet_ptp and shelf. Member alarm for virtual concatentation faults on EOP members.

SUM-V: VT Alarm Summary

SUM-V One or more alarms exist for VT paths within the STS-1.

SA Critical Minor Check teh conditions on the VT paths within the STS-1.

SWRING1: Auto Switch to Ring 1

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

Info • Verify that the switch was expected.• Check the switch-from section for


SWRING2: Auto Switch to Ring 2

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


SYNC: System reference lock failed

SYSREF Lock on system reference is lost. Minor Check system reference.

SYNCHSTATCHNG: Sychronization Status Message Change

SYNCHSTATCHNG The Synchronization Status messages has changes on the timing reference.


TCA: Threshold Crossing Alert

TCA The associated Performance Monitoring parameter has crossed the configured threshold.

Info

TIM-P: Trace Identifier Mismatch - Path

TIM-P The expected path trace string does not match the received path trace string.

Minor • Check configuration of path source or cross-connect.

• Match the path trace string on both ends of the path.



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Alarm

s/Events, TE-206

Page 1-133Force10 N

etworks

Release O

PS4.2.3

UNEQ-P: Unequipped code signal label received or transmitted

UNEQ-PUNEQ-P-TX

Unequipped code signal label received or transmitted

Minor

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

UNEQ-V No payload is received on an activated service.

Minor • Check your interface connection.• Connect your proper payload and

service source.

WKSWBK: Auto Switch to Working

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

Info • Verify that the switch was expected.• Check the switch-from section for


WKSWBK: Auto Switch to Working

APS-PROTECT A protection switch to the working facility that occurred because of an alarm clearing or Wait-To-Restore timer option.


WKSWPR: Auto Switch to Protect

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


WKSWPR: Auto Switch to Protect

APS-WORK A protection switch to the working facility that occurred because of an alarm on the working facility.

Info



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Chapter2

Alarm


mended A

ctionsA


Release O

PS4.2.3Force10 N

etworks

Page 1-134

WLMM: Configured wavelength mismatch with hardware

WLMIS Incorrect provisioning. SA Critical Minor Check interface and configuration.

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

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

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



TransNavAlarm(s)


Affecting Default


SA (Unprotected)

NSA (Protected)

Operations and M

aintenance Guide, S

ection1: Fault M

anagement

Page 1-135Force10 N

etworks

Release O

PS4.2.3

Chapter2

Alarm


mended A

ctions

Release O

PS4.2.3Force10 N

etworks

Page 1-136


SECTION 1FAULT MANAGEMENT

Chapter 3 Service Error Codes

Introduction This document contains TransNav service error code information to assist you in troubleshooting TransNav management system service request failure indications. See the figure below.

This chapter includes the following topics:• Service Activation Failure• Service Error Codes and Recommended Actions

Figure 1-29 TransNav GUI Service Request Error Window

Operations and Maintenance Guide, Section 1: Fault ManagementService Activation Failure


Service Activation Failure

If a service request activation fails, use the following Service Request—Show Last Error procedure to help trace and resolve the problem.

Table 1-15 Service Request—Show Last Error

Step Procedure

1 Select the service request entry.

Figure 1-30 Service Request Failure

2 From the Services menu, select Show Last Error.

Figure 1-31 Services Menu—Show Last Error Option

3 Observe the service error code information and refer to Table 1-16 Service Error Codes and Recommended Actions, page 1-139 for further troubleshooting details.

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

Service ActivationFailure

Indication

Service Error Code

InformationEntryRequest

Chapter3

Service E

rror Codes

Service Error Codes and R

ecomm

ended Actions

Release O

PS4.2.3Force10 N

etworks

Page 1-139

Service Error Codes and Recommended Actions

Service error codes for the TransNav management stem 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-16 Service Error Codes and Recommended Actions

Service Error Code

Service Error Code String Definition Probable Cause Recommended Action

1 Internal error A system error occurred. If the problem persists, contact the Force10 Technical Assistance Center.

1007 RSVP (resource reservation protocol) - 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,

perform a GCM switchover.• As a last resort, restart the node.

1008 RSVP - 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,


1009 RSVP - 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,


1016 RSVP - No path for reservation Remote node or link failure. Retry service request.

1025 RSVP - 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.

Operations and M

aintenance Guide, S

ection1: Fault M

anagement


ecomm

ended Actions

Page 1-140Force10 N

etworks

Release O

PS4.2.3

1034 RSVP - Resources not available Service resources completely used. Most typically, this applies to STS resources.

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

Select another resource and retry the service request.

1035 RSVP - 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, then retry the service request.

• If you were using the Bulk Activation tool, make note of the first service request error identified. Retry service activation, one-by-one.

1036 RSVP - 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, then retry the service request.

• If you were using the Bulk Activation tool, make note of the first service request error identified. Retry service activation, one-by-one.

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.

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

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

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

Service Error Code


Chapter3

Service E

rror Codes


ecomm

ended Actions

Release O

PS4.2.3Force10 N

etworks

Page 1-141

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 Force10 Technical Assistance Center

1217 Cannot find the service The service or cross-connect identifier has been lost. If the problem persists, contact the Force10 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 The slot is already in use in a protection group. Make another slot selection and retry the service request.

1227 PG 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.

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.


Service Error Code


Operations and M

aintenance Guide, S

ection1: Fault M

anagement


ecomm

ended Actions

Page 1-142Force10 N

etworks

Release O

PS4.2.3

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 operation on line cards

Failure occurred while creating the protection group. If the problem persists, contact the Force10 Technical Assistance Center.

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

1247 No UPSR PG created for the requested UPSR service

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

1254 Invalid span or tributary card given in the transparent service

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


Service Error Code


Chapter3

Service E

rror Codes


ecomm

ended Actions

Release O

PS4.2.3Force10 N

etworks

Page 1-143

1258 DCC tunnel interface is in a transparent ring

The selected port is in a transparent ring. Select another port and retry the service request.

1259 DCC tunnel STS is in use The STS specified is already in use. Select another STS and retry the service request.

1263 E2E service request; forward direction STS already in use

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

1264 E2E service request; forward direction STS already in use

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

Check STS. Select another STS and retry the service request.

1265 E2E service request; reverse direction STS already in use



1266 E2E service request; reverse direction STS already in use



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

Make correct constraint selections and retry the service request.

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

Select another interface and retry the service request.

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

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

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 Force10 Technical Assistance Center.

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



Service Error Code


Operations and M

aintenance Guide, S

ection1: Fault M

anagement


ecomm

ended Actions

Page 1-144Force10 N

etworks

Release O

PS4.2.3

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


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


1277 Label word invalid Invalid directional resource request • Check uni- and bi-directional settings.• If the problem persists, contact the Force10 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 Force10 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 Force10 Technical Assistance Center.

1284 Invalid BLSR link check The STS number requested must be equivalent across the E2E BLSR path.

One of the STS labels along the path is already in use OR a card has been inadvertently pulled during the E2E service request selection process.

Check STS number availability across the entire BLSR path.

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

1285 BLSR label unavailable The STS number in the E2E BLSR service request is in use.

Reactivate BLSR service request.

If previously attempting service request using Bulk Activation, retry on a one-by-one basis for better traceability.

1286 Invalid BLSR constraints. System error during the E2E BLSR service request. If the problem persists, contact the Force10 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.


Service Error Code


Chapter3

Service E

rror Codes


ecomm

ended Actions

Release O

PS4.2.3Force10 N

etworks

Page 1-145

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

Control channel down Retry the service request.

1292 DCC bytes for interfaces in a 1+1 PG 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.

1423 CSPF - Protected tunnel must egress east port of the UPSR

Attempted activation of protected tunnel egressing the west port of a UPSR.

Use one of the following actions to remedy this error:• Reverse the source and destination endpoints of the protected

tunnel • Provision the tunnel to use the other path around the UPSR.

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.

3021 LC FM (Line card flow manager) 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.


Service Error Code


Operations and M

aintenance Guide, S

ection1: Fault M

anagement


ecomm

ended Actions

Page 1-146Force10 N

etworks

Release O

PS4.2.3

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 p2p service and is incompatible with the service in the activation request.


3228 Optical facility requested in service is in use for a transparent LAN service

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


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

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.


Service Error Code


Chapter3

Service E

rror Codes


ecomm

ended Actions

Release O

PS4.2.3Force10 N

etworks

Page 1-147

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 and is therefore 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.2.3 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.


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

The SONET endpoint is already in use with another IAS service with a different participation type.

All services using a SONET endpoint must have the same participation type (SUBSCRIBER or PROVIDER).


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

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

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

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

Traffic contract resource allocation failure during service request. All traffic contracts are in use.

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.

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


Service Error Code


Operations and M

aintenance Guide, S

ection1: Fault M

anagement


ecomm

ended Actions

Page 1-148Force10 N

etworks

Release O

PS4.2.3

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.

Each Ethernet card supports (typically) 24 SONET endpoints.


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.

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.

A VLAN ID can only be used for TLS on one Ethernet card at a time in a node.

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

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


Service Error Code


Chapter3

Service E

rror Codes


ecomm

ended Actions

Release O

PS4.2.3Force10 N

etworks

Page 1-149

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

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


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

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


3600 VT resource request is in use The VT resource requested is already in use. Check VT. Make another VT selection and retry the service request.

3601 STS resources between the cards are all used up

• VT Switch 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.


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.

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

A system error occurred during the GCM replication process.


3622 STS resource is already being used The STS resource requested is already in use. Make another STS selection (with appropriate bandwidth) and retry the service request.


Service Error Code


Operations and M

aintenance Guide, S

ection1: Fault M

anagement


ecomm

ended Actions

Page 1-150Force10 N

etworks

Release O

PS4.2.3

3817 All tunnels on Ethernet card already allocated

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

Each Ethernet card supports (typically) 24 SONET endpoints.

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

3818 Minimum Best Effort bandwidth requirements unavailable

Resource allocation request failure. SONET termination point resources required for Best Effort class of service are unavailable so the service request cannot complete.

Premium class of service services are using the required bandwidth.

Deactivate one or more services using SONET termination points with the Premium class of service to free up resources, then retry the new service request.

3820 Ethernet card must be created before adding services

The Ethernet 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 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, then retry the new service request.

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

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


Service Error Code



SECTION 2 PERFORMANCE MONITORINGSECTION 2SECTION 2

Contents

Chapter 1Managing Performance

Creating or Modifying a Monitoring Template . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Assigning a PM Template to a Traverse Node . . . . . . . . . . . . . . . . . . . . . . . . 2-5Assigning a Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Assigning an EOS Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Assigning an EOP Port PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Changing a Member PDH PM Template for an EOP PDH Member . . . . . . . . 2-7Assigning a Subport PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Assigning a Service PM Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Viewing PM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

PM Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Viewing Port or Subport PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Viewing Service Path PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Viewing Signal Path Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Viewing Capacity Monitoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Generating a PM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Assigning a Template to a TE-206 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Scheduling TE-206 PM Collection Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Chapter 2SONET Performance Parameters

DS1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22DS3 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25EC-1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28SONET Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31SONET STS Path Layer PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36SONET VT Path Layer PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39SONET Capacity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

Chapter 3SDH Performance Parameters

E1 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44E3 Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47SDH High and Low Order Path PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49SDH Port PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53SDH VC-11 and VC-12 Path PM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58SDH Capacity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61

Chapter 4Ethernet Performance Parameters

Operations and Maintenance Guide, Section 2 Performance Monitoring


Ethernet 10GbE Equipment PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64EoPDH Equipment PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66NGE Equipment PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69Ethernet Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71Ethernet Service Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74EOS Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76EOP Port PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78

EOP Port PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78EOP Port Member PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79

Small Form-Factor Pluggable Optical Port PM . . . . . . . . . . . . . . . . . . . . . . . . 2-80


SECTION 2PERFORMANCE MONITORING

Chapter 1 Managing Performance

Introduction The TransNav management system provides performance monitoring (PM) functions to monitor electrical, optical, and Ethernet signals. It also provides capacity monitoring functions to gather switch capacity data for VT and TU 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.

See the following procedures to set up performance monitoring on Traverse nodes:• Creating or Modifying a Monitoring Template, page 2-2• Assigning a PM Template to a Traverse Node, page 2-5• Viewing PM Data, page 2-9

– PM Timing, page 2-9• Viewing Capacity Monitoring Data, page 2-16• Report Generation, page 2-17• Generating a PM Report, page 2-18

Cards (modules) that do not collect PM information may be reserved for administrative use; contact your system Administrator.

For further information on performance monitoring and capacity monitoring of Traverse nodes, and the management system, see the TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 1—“Performance Monitoring”.

Use the following procedures to set up and view performance monitoring data on TE-206 nodes from TransNav: • Assigning a Template to a TE-206 Node, page 2-19• Scheduling TE-206 PM Collection Times, page 2-20

Note: These procedures document the methods used to view TE-206 performance monitoring data from the TransNav GUI. For additional information about available reports for the TE-206 nodes, see the TransNav Xpert Users Guide.

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


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.

Note: Changes to a service PM template can only be made if the service is inactive and is not on an end-to-end service.

The following procedure describes how to create or modify a monitoring template.

Important: Default threshold values in the sonet_ptp_pm and sdh_ptp_pm template are based on performance monitoring for OC-3 and STM-1 rates, respectively. Force10 recommends customizing these templates for rates other than OC-3 and STM-1.

Table 2-1 Creating or Modifying a PM Template

Step Procedure

1 In Map View, select Admin, then Performance Templates. The Performance Templates dialog box displays.

Figure 2-1 Performance Templates Dialog Box

Chapter 1 Managing PerformanceCreating or Modifying a Monitoring Template


2 From the Type drop-down list, select the template type. Each ptp template is used for port or subport; each path template is used for service performance monitoring; each capacity template is used for switch capacity monitoring; each eqp template is used for equipment performance monitoring. To display the types in alphabetical order, click the Type heading in the dialog box.• 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• eop_ptp_pm: Ethernet over PDH port performance monitoring• eos_ptp_pm: Ethernet over SONET/SDH port performance

monitoring• ethernet_10ge_eq_pm: Ethernet equipment performance monitoring

for 10GbE and GbE-10 cards• ethernet_eopdh_eq_pm: Ethernet over PDH equipment performance

monitoring for EoPDH cards• ethernet_eq_pm: Ethernet equipment performance monitoring fpr

NGE and NGE Plus cards• 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

• te206_pm: TE-206 node performance monitoring• vt_path_pm: SONET virtual tributary (VT) path performance

monitoring

3 Creating a template?• Yes. Go to the next step.• No. Go to Step 5.

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

Step Procedure

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


4 Click Add, then enter a Name for the template. Go to Step 6.

Note: Force10 recommends making a copy of the default template and naming it ‘original’. This avoids changing the default value on the Configuration screen for all cards and ports or on the Create/Edit EOP screens for EOP ports. For TE-206 nodes, this prevents PM collection from being enabled on all TE-206 nodes.

5 Double-click the template row to open the Configuration Template dialog box.

6 Set the 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.)

Note: For eop_ptp_pm and ethernet_eopdh_eq_pm templates, select the Non-resetting PM check box to prevent the value in the 24-hour period from resetting to “0” every 24 hours. • 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. For TE-206 nodes, if the Collect check box is selected, all PM data for the nodes is collected.

Note: For capacity monitoring, only VT/TU switching information is captured for reports. STS paths are not included when determining available capacity.

Note: The number of parameters you select affects the file size. If the output files are stored on the server, the server performance could be affected. For information on changing the output directory, see the TransNav Provisioning Guide, Chapter 5—“Generating and Viewing Reports,” Generating Reports.


Step Procedure

Chapter 1 Managing PerformanceAssigning a PM Template to a Traverse Node


Assigning a PM Template to a Traverse Node

Choose one of the following topics by object type (e.g., port) to assign a PM template for a Traverse node:• Assigning a Port PM Template, page 2-6• Assigning an EOS Port PM Template, page 2-6• Assigning an EOP Port PM Template, page 2-7• Assigning a Subport PM Template, page 2-8• Assigning a Service PM Template, page 2-8

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 A confirmation dialog box displays. 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.


Step Procedure

Operations and Maintenance Guide, Section 2: Performance MonitoringAssigning a Port PM Template


Assigning a Port PM Template

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

Assigning an EOS Port PM Template

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

Table 2-2 Assigning a Port PM Template

Step Procedure

1 In Shelf View, click a card port.

2 Click the Config tab. The Port Configuration screen appears.

3 From the PM Template parameter list, select a port PM (ptp) template. If you have not created or modified a template, only the default value appears.

4 Click Apply.

5 The Assigning a Port PM Template procedure is complete.

Table 2-3 Assigning an EOS Port PM Template

Step Procedure

1 In Shelf View, click the Ethernet tab.

2 Select the EOS subtab and click an EOS port from the EOS port list, then click Edit.

3 Click Advanced. The EOS Advanced Parameters dialog box displays.

4 From the PM Template parameter list, select an eos_ptp_pm template. If you have not created or modified a template, only the default value appears.

5 Click Apply.

6 The Assigning an EOS Port PM Template procedure is complete.

Chapter 1 Managing PerformanceChanging a Member PDH PM Template for an EOP PDH Member


Assigning an EOP Port PM Template

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

Changing a Member PDH PM Template for an EOP PDH Member

Member PDH PM templates are usually assigned to PDH members at the time the EOP port is created. The following procedure describes how to change a PM template for an existing EOP PDH member.

For information on assigning a Member PDH PM Template to a new EOP port, see the TransNav Provisioning Guide, Section 7—Configuring Ethernet, Chapter 6—“Ethernet Over PDH (EOP)”.

Table 2-4 Assigning an EOP Port PM Template

Step Procedure


2 Select the EOP subtab and click an EOP port from the EOP port list, then click Edit.

3 Click Advanced. The EOP Advanced Parameters dialog box displays.

4 From the PM Template parameter list, select an eop_ptp_pm template. If you have not created or modified a template, only the default value appears.

5 Click OK. A Synchronize Template message displays “Would you like to synchronize the new Template?” Click Yes to synchronize the template or No.

6 The Assigning an EOS Port PM Template procedure is complete.

Table 2-5 Changing a Member PDH PM Template for EOP PDH Members

Step Procedure


2 Select the EOP subtab and click an EOP port from the EOP port list, then click Edit.

3 From the Member PDH PM Template parameter list, select a template (ds1_ptp_pm, ds3_ptp_pm, e1_ptp_pm, or e3_ptp_pm). The available template types match the bandwidth value in the PDH Member Type parameter (DS1, DS3, E1, or E3). If you have not created or modified a template, only the default value appears. Go to Step 5.

4 Click Apply.

5 The Changing a Member PDH PM Template for EOP PDH Members procedure is complete.

Operations and Maintenance Guide, Section 2: Performance MonitoringAssigning a Subport PM Template


Assigning a Subport PM Template

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

Assigning a Service PM Template

The following procedure describes how to assign a path PM template to a service. The service PM template is selected during service creation or editing.

Note: Changes to the PM template can only be made if the service is inactive and is not on an end-to-end service.

Table 2-6 Assigning a Subport PM Template

Step Procedure

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


3 From the Subport row, PM Template column list, select a port (ptp) PM template matching the embedded signal subport type (e.g., ds1_ptp).

4 Click Apply.

5 The Assigning a Subport PM Template procedure is complete.

Table 2-7 Assigning a Service PM Template

Step Procedure

1 From any view, click the Service tab.

2 Creating or editing a service?• Creating: Click Add to access the Create Service tab.• Editing: Double-click a service row to access the Edit Service tab.

3 Click Advanced to access the Advanced Parameters dialog box.

Chapter 1 Managing PerformanceViewing PM Data


Viewing PM Data

Choose one of the following topics by object type (e.g., port) to view PM data for Traverse nodes. • Viewing Port or Subport PM Data, page 2-10• Viewing Service Path PM Data, page 2-12

To schedule PM data for TE-206 nodes, see the following section:• Scheduling TE-206 PM Collection Times, page 2-20

4 The Advanced Parameters dialog box appears.

From the Source PM Template and Destination PM Template or Service Port PM list, select a PM template.

Figure 2-3 Service PM Template Parameters

5 Click Done and continue creating or editing the service.

6 The Assigning a Service PM Template procedure is complete.

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

Step Procedure

3

4

PM Timing. Performance monitor on-screen Samples (bin) column timestamps use the Traverse node time. The on-screen PM Refresh Time uses the TransNav GUI time. The Traverse node time and TransNav GUI time can be different if they are in different time zones.

Operations and Maintenance Guide, Section 2: Performance MonitoringViewing 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-8 Viewing Port or Subport PM Data

Step Procedure

1 In Shelf View, click the Performance tab and select a port or a subport.

Figure 2-4 Object Selection for PM

2 On the Interval 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 current and previous.

Chapter 1 Managing PerformanceViewing Port or Subport PM Data


3 Click Refresh to re-display updated PM values.

Figure 2-5 Port Performance Tab

4 If you click Reset, the counters reset to zero.

Note: If the Non-resetting PM check box was selected for any Ethernet template, the Refresh Time parameter will not be updated.

5 Click Print to print the current screen.

6 Click Save to save the PM data to a file.

7 The Viewing Port or Subport PM Data procedure is complete.

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

Step Procedure

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


Viewing Service Path PM Data

The following procedure describes how to view service path PM data.

Table 2-9 Viewing Service PM Data

Step Procedure

1 In Shelf View, click the Service tab.

2 Select a service. Right-click and select Show Tx/Rx Path to display the Path Display for Service screen.


3 Click the PM (Performance) tab to display the PM screen.

4 From the Path Display for Service screen, for either a Tx or Rx table row, select an Active or Standby Hop. Your selection appears in the Hop Id field on the PM tab.

5 Click Refresh on the PM tab to display the performance monitoring data.

Chapter 1 Managing PerformanceViewing Service Path PM Data


6 On the Interval list you can select 15-minute or 24-hour intervals. You can view up to thirty-two 15-minute or two 24-hour Samples current and previous.

Figure 2-7 Service Performance (PM) Tab

7 Click Refresh to re-display updated PM values.

8 If you click Reset, the counters reset to zero.


10 Click Save to save the PM data to a file.

11 The Viewing Service PM Data procedure is complete.

Table 2-9 Viewing Service PM Data (continued)

Step Procedure

Operations and Maintenance Guide, Section 2: Performance MonitoringViewing 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-10 Viewing Signal Path Trace Data

Step Procedure

1 In Shelf View, click the Service tab.

2 Select a service. Right-click and select Show Tx/Rx Path to display the Path Display for Service screen.

Figure 2-8 Path Display for Service Screen

3 Click the CTP tab to display the CTP screen.

4 From the Path Display for Service screen, for either a Tx or Rx table row, select an Active Hop. Your selection appears in the EndPoint field on the CTP tab.

Chapter 1 Managing PerformanceViewing Signal Path Trace Data


5 In the Alarm Profile field, one of the following profile values displays:• useParent: The alarm profile of the containing object (Parent) based

on the following superset and subset definitions:– Port: Contains line and path alarms and is the superset.– High order path: Contains high and low order path alarms and is a

subset of port profiles.– Low order path: Contains only low order path alarms and is a finer

subset of high order path profiles.– STS path. Contains STS and VT path alarms and is a subset of

port profiles.– VT path: Contains only VT path alarms and is a finer subset of

STS path profiles.• default: The default alarm profile matching the CTP object type.• <user-defined>: Depending on the CTP object type, this value

indicates a user-defined alarm profile of one of the following path alarm profile types:– sdh_hp– sdh_lp– sonet_sts– sonet_vt

6 Click Received/Transmitted Path Overhead. The Received/ Transmitted Path Overhead dialog box displays. (The name of the button and the resulting dialog box corresponds to whether you selected a Tx or Rx active hop.)

Figure 2-9 Path Overhead Dialog Box

7 Click Refresh to display updated PM values.

8 Click Done to return to the previous screen.

9 The Viewing Signal Path Trace Data procedure is complete.

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

Step Procedure

Operations and Maintenance Guide, Section 2: Performance MonitoringViewing 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-11 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 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 current and previous.

3 Click Refresh to re-display updated capacity monitoring values.

Figure 2-10 Viewing VT/TU Capacity Monitoring Data

4 If you click Reset, an error message displays. The counters do not reset to zero.


6 Click Save to save the capacity monitoring data to a file.

7 The Viewing VT/TU Capacity Monitoring Data procedure is complete.

Chapter 1 Managing PerformanceReport Generation


Report Generation

Through the TransNav management system, you have the ability to create different reports. You can customize the reports for your own uses, as well as specify generation dates and generation periods.

Performance monitoring data for TE-206 nodes is collected by TransNav and stored in the EMS directory on the server. To view the output data collected by the report, go to the \report\output directory. (This is the only way to access large TE-206 reports.) The report displays in the following format:

<Report name > _mm.dd.yyyy.hh.mm

The file must be opened with a basic document editor such as NotePad or WordPad.

Create 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-11 Event Report Sample

Operations and Maintenance Guide, Section 2: Performance MonitoringGenerating a PM Report


Generating a PM Report

The following procedure describes how to create a PM report.

For information on scheduling reports, refer to the TransNav Management System GUI Guide, Section 2— Administrative Tasks, Chapter 5—“Generating and Viewing Reports,” Using the Report Scheduler.

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 Monitoring Template.

Table 2-12 PM Report Generation

Step Procedure

1 From the Admin menu, select Reports. The Reports screen displays.

Figure 2-12 Reports Screen

2 Select a PM report from the Report Schedulers list.

3 Click Generate Now. Entries appear in the Report List section.

4 Select a Report List entry.

5 Click View Report.

6 The PM Report Generation procedure is complete.

Chapter 1 Managing PerformanceAssigning a Template to a TE-206 Node


Assigning a Template to a TE-206 Node

The following procedure describes how to assign a PM template to a TE-206 node.

Table 2-13 Assigning a Template to a TE-206 Node

Step Procedure

1 In Shelf View, double-click a TE-206 node to establish connection. The selected shelf GUI displays.

Figure 2-13 Select TE-206 Node Template


3 From the PM Template Name, select the name of the PM template. Click Apply.

4 The Assigning a Template to a TE-206 Node procedure is complete.

Operations and Maintenance Guide, Section 2: Performance MonitoringScheduling TE-206 PM Collection Times


Scheduling TE-206 PM Collection Times

The following procedure describes setting up PM collection times for TE-206 nodes from TransNav:

To generate a PM report for a TE-206 node from TransNav, follow the instructions in Generating a PM Report.

Table 2-14 Scheduling TE-206 PM Collection Times

1 From Map View, establish connection to the TE-206 node that you want to set up PM data collection times. The WebCraft GUI displays with a graphical view of the node.

2 On the WebCraft GUI, click the Administration tab.

3 Under Performance Monitoring, select Daily Collection Start Time.

4 The start time is represented by 24 integers (00-23) to indicate a 24-hour clock. 00 refers to 12:00a.m. and so on. The default is 17:00.

Figure 2-14 Set the Daily Collection Time

Select the time to start the 24 hour collection and click OK to set the new start time.

5 The Scheduling TE-206 PM Collection Times procedure is complete.



Chapter 2 SONET Performance Parameters

Introduction This chapter provides performance parameter information for:• DS1 Port PM, page 2-22• DS3 Port PM, page 2-25• EC-1 Port PM, page 2-28 • SONET Port PM, page 2-31• SONET STS Path Layer PM, page 2-36• SONET VT Path Layer PM, page 2-39• SONET Capacity Monitoring, page 2-41


For further information on performance monitoring and the management system, see the TransNav Management System GUI Guide.

Operations and Maintenance Guide, Section 2: Performance MonitoringDS1 Port PM


DS1 Port PM The Traverse system provides near- and far-end DS1 port PM parameters (ds1_ptp_pm).

Table 2-15 DS1 Port PM Parameters—Near End

Parameter Definition 15-min Threshold

Daily Threshold

Line—Near End

CV (Code Violations)

Count of both bipolar violations (BPV) and excessive zeros (EXZ) occurring over the accumulation period. An EXZ increments the CV Line count by one regardless of the length of the zero string.

1–16383

Default: 13340

1–1048575

Default: 133400

ES(Errored Seconds)

Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded.

1–900

Default: 65

1–65535

Default: 648

SES (Severely Errored Seconds)

Count of 1-second intervals during which BPVs plus EXZs exceed 1544, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded.

1–63

Default: 10

1–4095

Default: 100

LOSS(Loss of Signal Seconds

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

1–63

Default: 10

1–4095

Default: 100

Path—Near End

CV(Code Violations)

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

1–16383

Default: 13296

1–1048575

Default: 132960

ES(Errored Seconds)

Count of 1-second intervals containing any of the following:• CRC-6 errors (ESF)• CS events (ESF, SF)• SEF defects (ESF, SF)• LOS defects (ESF, SF)• FE errors (SF)

1–900

Default: 65

1–65535

Default: 648

SES(Severely Errored Seconds)

Count of 1-second intervals containing:• 320 or more CRC-6 errors (ESF)• 8 or more FE events (SF)• one or more SEF or LOS defects (ESF, SF)

1–63

Default: 10

1–4095

Default: 100

Chapter 2 SONET Performance ParametersDS1 Port PM


AISS(Alarm Indication Signal Seconds)

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

1–63

Default: 10

1–4095

Default: 100

SAS(Severely Errored Frames/Alarm Indication Signal Seconds)

Count of 1-second intervals containing one or more of either SEF defects or LOS/AIS defects.

1–63

Default: 2

1–4095

Default: 17

CSS(Controlled Slip Seconds

Counts of 1-second intervals containing one or more controlled slips.

1–63

Default: 2

1–4095

Default: 17

UAS(Unavailable Seconds)

Count of 1-second intervals for which the DS1 path is unavailable.

1–63

Default: 10

1–4095

Default: 100

FC(Failure Counts)

Count of the number of near-end failure events on the path. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–72

Default: 4

1–4094

Default: 40

Table 2-16 DS1 Port PM Parameters—Far End


Daily Threshold

Line—Far End

ES (Errored Seconds)


1–900

Default: 65

1–65535

Default: 648

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


Daily Threshold



Path—Far End


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

1–16383

Default: 13296

1–1048575

Default: 132960

ES (Errored Seconds–Path)


1–900

Default: 65

1–65535

Default: 648

SES (Severely Errored Seconds–Path)

Count of 1-second intervals containing:• 320 or more CRC-6 errors (ESF)• 8 or more FE events (SF)• 1 or more SEF or LOS defects (ESF, SF)

1–63

Default: 10

1–4095

Default: 100

SEFS (Severely Errored Framing Seconds–Path)

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

1–63

Default: 2

1–4095

Default: 17

CSS (Controlled Slip Seconds–Path)

Counts of 1-second intervals containing one or more controlled slips.

1–63

Default: 2

1–4095

Default: 17

UAS(Unavailable Seconds–Path)


1–63

Default: 10

1–4095

Default: 100

FC (Failure Count–Path)

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

Default: 10

1–4095

Default: 100

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


Daily Threshold



DS3 Port PM The Traverse system provides near- and far-end DS3 (clear channel or transmux) port PM parameters.

Table 2-17 DS3 Port PM Parameters—Near End


Daily Threshold

Line—Near End


Count of both bipolar violations (BPV) and excessive zeros (EXZ) occurring over the accumulation period. An EXZ increments the CV Line count by one regardless of the length of the zero string. BPVs that are part of the zero substitution code are excluded.

1–16383

Default: 387

1–1048575

Default: 3865



1–900

Default: 25

1–65535

Default: 250


Count of seconds during which BPVs plus EXZs exceed 44, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded.

1–63

Default: 4

1–4095

Default: 40

Path PBit—Near End


Count of P-bit parity check CVs. The receipt of non-identical P-bits corresponding to the same DS3 M-Frame also constitutes a parity check CV.

1–16383

Default: 382

1–1048575

Default: 3820

ES (Errored Seconds

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

1–900

Default: 25

1–65535

Default: 250


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

1–63

Default: 4

1–4095

Default: 40

UAS (Unavailable Seconds)

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

1–63

Default: 10

1–4095

Default: 10



FC (Failure Counts)

Count of the number of near-end path failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–63

Default: 4

1–4095

Default: 40

Path CBit—Near End

CV(Code Violations)

Both CP-bit parity CVs (CVCP-P) and CVP-P counts are defined and may be supported since they can convey different information. The first is the count of CP-bit parity errors occurring in the accumulation period. The CVP-P parameter count is the same as described above.

1–16383

Default: 382

1–1048575

Default: 3820

ESC (Errored Seconds)

Two versions of the ES parameter may be accumulated and stored. The ESCP-P parameter is a count of seconds containing one or more CP-bit parity errors, one or more SEF defects, or one or more LOS defects. The ESP-P parameter count is the same as described above.

1–900

Default: 25

1–65535

Default: 250

SESC (Severely Errored Seconds)

Two versions of the SES parameter may be accumulated and stored. The SESCP-P parameter is a count of seconds containing more than 44 CP-bit parity errors, one or more SEF defects, or one or more LOS defects. The SESP-P parameter is the same as described above.

1–63

Default: 4

1–4095

Default: 40

UASC (Unavailable Seconds–C-bit parity application)


1–63

Default: 10

1–4095

Default: 10

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


Daily Threshold



Table 2-18 DS3 Port PM Parameters—Far End


Daily Threshold

Path PBit—Far End

FCFE (Failure Counts)

Count of the number of far-end path failure events. A failure event begins when the RFI-P failure is declared, and ends when the RFI-P failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–63

Default: 4

1–4095

Default: 40

Path CBit—Far End

CVFE (Code Violations)

Counted when the three FEBE bits in an M-frame are not all set to 1.

1–16383

Default: 382

1–1048575

Default: 3820

ESFE (Errored Seconds)

Count of 1-second intervals containing one or more M-frames with the three FEBE bits not all set to one, or one or more far-end SEF/LOS defects.

1–900

Default: 25

1–65535

Default: 250

SESFE (Severely Errored Seconds)

Count of 1-second intervals containing one or more than 44 M-frames with the three FEBE bits not all set to one, or one or more far-end SEF/LOS defects.

1–63

Default: 4

1–4095

Default: 40

UASFE (Unavailable Seconds


1–63

Default: 10

1–4095

Default: 10

Operations and Maintenance Guide, Section 2: Performance MonitoringEC-1 Port PM


EC-1 Port PM The Traverse system provides near- and far-end EC-1 port PM parameters.

Table 2-19 EC1 Port PM Parameters—Near-End


Daily Threshold

SECTION


Count of BIP-8 errors that are detected at the section layer of the incoming signal.

Count of BIP errors detected at the section layer (i.e., using the B1 bytes in the incoming SONET signal). Up to 8 section BIP errors can be detected per STS-N frame, with each error incrementing the CV-S register.

1–16383

Default: 382

1–1048575

Default: 3820


Count of 1-second intervals during which (at any point during the second) at least one section layer BIP error was detected or an SEF or LOS defect was present

1–900

Default: 25

1–65535

Default: 250


Count of the seconds during which 154 or more section layer BIP errors were detected or an SEF or LOS defect was present.

1–900

Default: 4

1–65535

Default: 40

SEFS (Severely Errored Framing Seconds)

Count of 1-second intervals during which (at any point during the second) an SEF defect was present. An SEF defect is detected when an incoming signal has a minimum of four consecutive errored framing patterns.

1–900

Default: 2

1–65535

Default: 8

LINE

CV (Coding Violations)

Count of BIP errors detected at the line layer (i.e., using the B2 bytes in the incoming SONET signal). Up to 8xN BIP errors can be detected per STS-N frame, with each error incrementing the CV-L current second register.

1–16383

Default: 387

1–1048575

Default: 3865


Count of the seconds during which (at any point during the second) at least one Line layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present.

1–900

Default: 25

1–65535

Default: 250


Count of the seconds during which 52 or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present.

1–63

Default: 4

1–4095

Default: 40

Chapter 2 SONET Performance ParametersEC-1 Port PM



Count of the seconds during which the Line was considered unavailable. A Line becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ls, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ls.

1–63

Default: 4

1–4095

Default: 40

FC (Failure Counts)

Count of the number of near-end Line failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–63

Default: 4

1–4095

Default: 40

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


Daily Threshold

Table 2-20 EC1 Port PM Parameters—Far-End

Parameter Definition 15-min Threshold Daily Threshold

LINE

CVFE (Coding Violations–Far-End)

Count of the number of BIP errors detected by the far-end LTE and reported back to the near-end LTE using the REI-L indication in the Line overhead. For SONET signals at rates below OC-48, up to 8xN BIP errors per STS-N frame can be indicated using the REI-L. For OC-48 signals, up to 255 BIP errors per STS-N frame can be indicated. The CV-LFE current second register increments for each BIP error indicated by the incoming REI-L.

1–16383

Default: 387

1–1048575

Default: 3865

ESFE (Errored Seconds–Far-End)

Count of the seconds during which (at any point during the second) at least one Line BIP error was reported by the far-end LTE (using the REI-L indication) or an RDI-L defect was present.

1–900

Default: 25

1–65535

Default: 250

SESFE (Severely Errored Seconds–Far-End)

Count of the seconds during which K or more Line BIP errors were reported by the far-end LTE or an RDI-L defect was present. The number of reported far-end BIP errors causing a second to be considered an SES-LFE.

1–63

Default: 4

1–4095

Default: 40

Operations and Maintenance Guide, Section 2: Performance MonitoringEC-1 Port PM


UASFE (Unavailable Seconds–Far-End)

Count of the seconds during which the Line is considered unavailable at the far end. A Line is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-LFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-LFEs.

1–63

Default: 4

1–4095

Default: 40

FCFE (Failure Counts–Far-End)

Count of the number of far-end Line failure events. A failure event begins when the RFI-L failure is declared, and ends when the RFI-L failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–63

Default: 4

1–4095

Default: 40

Table 2-20 EC1 Port PM Parameters—Far-End (continued)


Table 2-21 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.

Chapter 2 SONET Performance ParametersSONET Port PM


SONET Port PM

The Traverse system provides the following near- and far-end SONET port performance monitoring parameters.

Important: Default threshold values in the sonet_ptp_pm template are based on performance monitoring for OC-3 rates. Force10 recommends customizing this template for rates other than OC-3.

Table 2-22 SONET Port PM—Near End


Section—Near End

CV (Coding Violation)

Count of BIP (Bit Interleaved Parity) errors detected at the Section layer (i.e., using the B1 byte in the incoming SONET signal). Up to 8 section BIP errors can be detected per STS-N frame, with each error incrementing the CV-S register.

1–16383

Default: 382

1–1048575

Default: 3820


Count of 1-second intervals during which (at any point during the second) at least one Section layer BIP error was detected or an SEF or LOS defect was present.

1–900

Default: 25

1–65535

Default: 250


Count of the seconds during which K or more Section layer BIP errors were detected or an SEF or LOS defect was present. K has the following values: • 154 for OC3• 615 for OC12• 2459 for OC48• 8854 for OC192

1–900

Default: 4

1–65535

Default: 40

SEFS(Severely Errored Framing Seconds)

Count of 1-second intervals during which (at any point during the second) an SEF defect was present. An SEF defect is detected when an incoming signal has a minimum of four consecutive errored framing patterns.

1–900

Default: 2

1–65535

Default: 8

CBiFEC (OC192 interfaces only) (Corrected bits by Forward Error Correction)

Count of number of corrected bites in the forward direction. Indicates the quality of the line using the number of FEC corrections.

1–16383

Default: 382

1–1048575

Default: 3820

Operations and Maintenance Guide, Section 2: Performance MonitoringSONET Port PM


CByFEC

(OC-192 interfaces only) (Corrected bytes by Forward Error Correction)

Count of number of corrected bytes in the forward direction. Indicates the quality of the line using the number of FEC corrections.

1–16383

Default: 382

1–1048575

Default: 3820

Line—Near End

CV (Coding Violation)

Count of BIP errors detected at the Line layer (i.e., using the B2 bytes in the incoming SONET signal). Up to 8xN BIP errors can be detected per STS-N frame, with each error incrementing the CV-L current second register.

1–16383

Default: 1146

1–1048575

Default: 11460


Count of the seconds during which (at any point during the second) at least one Line layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present.

1–900

Default: 25

1–65535

Default: 250


Count of the seconds during which K or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: • 154 for OC3• 615 for OC12• 2459 for OC48• 8854 for OC192

1–900

Default: 4

1–65535

Default: 40

Table 2-22 SONET Port PM—Near End (continued)





Count of the seconds during which the Line was considered unavailable. A Line becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ls, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ls.

1–900

Default: 4

1–65535

Default: 40

FC (Failure Counts)

Count of the number of near-end Line failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–72

Default: 4

1–4094

Default: 40

Table 2-22 SONET Port PM—Near End (continued)


Table 2-23 SONET Port PM Parameters—Far End


Daily Threshold

Line—Far End

CVFE (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 OC-48, up to 8xN BIP errors per STS-N frame can be indicated using the REI-L. For OC-48 signals, up to 255 BIP errors per STS-N frame can be indicated. The CV-LFE current second register increments for each BIP error indicated by the incoming REI-L.

1–16383

Default: 1146

1–1048575

Default: 11460

ESFE (Errored Seconds–Far End)

Count of the seconds during which (at any point during the second) at least one Line BIP error was reported by the far-end LTE (using the REI-L indication) or an RDI-L defect was present.

1–900

Default: 25

1–65535

Default: 250

Operations and Maintenance Guide, Section 2: Performance MonitoringSONET Port PM


SESFE (Severely Errored Seconds– Far End)

Count of the seconds during which K or more Line BIP errors were reported by the far-end LTE or an RDI-L defect was present. The number of reported far-end BIP errors causing a second to be considered an SES-LFE. K has the following values: • 154 for OC3• 615 for OC12• 2459 for OC48• 8854 for OC-192

1–900

Default: 4

1–65535

Default: 40

UASFE (Unavailable Seconds)

Count of the seconds during which the Line is considered unavailable at the far end. A Line is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-LFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-LFEs.

1–900

Default: 4

1–65535

Default: 40


Count of the number of far-end Line failure events. A failure event begins when the RFI-L failure is declared, and ends when the RFI-L failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–72

Default: 4

1–4094

Default: 40

PSCW (Protection Switch Counts Working)

Count of the number of times that an OC-N line service (i.e., BLSR, 1+1 ASP) switches from the working to the protecting line. This count also includes the number of times the service (revertive) switches back from the protecting to the working line.

1–63

Default: 2

1–255

Default: 10

PSDW (Protection Switch Duration Working)

Count of the seconds that the working line was being used to carry an OC-N line service (i.e., BLSR, 1+1 ASP).

1–900

Default: 4

1–65535

Default: 40

Table 2-23 SONET Port PM Parameters—Far End (continued)


Daily Threshold



PSCP(Protection Switch Counts Protecting)

Count of the number of times that an OC-N line service (i.e., BLSR, 1+1 ASP) switches from the protecting to any working line. This count also includes the number of times service (revertive) switches back from the protecting to the working line.

1–63

Default: 2

1–255

Default: 10

PSDP(Protection Switching Duration Protecting)

Count of the seconds that the protecting line was being used to carry OC-N line service (i.e., BLSR, 1+1 ASP).

1–900

Default: 4

1–65535

Default: 40

Table 2-23 SONET Port PM Parameters—Far End (continued)


Daily Threshold

Operations and Maintenance Guide, Section 2: Performance MonitoringSONET STS Path Layer PM


SONET STS Path Layer PM

The Traverse system provides the following performance monitoring parameters for SONET STS path layer services (sonet_path_pm).

Table 2-24 SONET STS Path PM Parameters—Near End



Count of BIP errors detected at the STS Path layer (i.e., using the B3 byte in the incoming STS path overhead). Up to 8 BIP errors can be detected per frame, with each error incrementing the CV-P current second register.

1–16383

Default: 1146

1–1048575

Default: 11460

ES(Errored Seconds)

Count of the seconds during which (at any point during the second) at least one path BIP error was detected, or an LOS (or a lower-layer, traffic-related, near-end defect), an LOP-P or, if the STS PTE monitoring the path supports ERDI-P for that path, an UNEQ-P or TIM-P (Trace Identifier Mismatch) defect was present.

1–900

Default: 25

1–65535

Default: 250


Count of the seconds during which 2400 or more path BIP errors were detected, or an LOS (or a lower-layer, traffic-related, near-end defect), an LOP-P or, if the STS PTE monitoring the path supports ERDI-P for that path, an UNEQ-P or TIM-P defect was present. The number of BIP errors causes a second to be considered an SES-P.

1–900

Default: 4

1–65535

Default: 40


Count of the seconds during which the path was considered unavailable. A path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ps and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps.

1–900

Default: 4

1–65535

Default: 40

RTD (Round Trip Delay)

Query the current round trip delay in milliseconds. The thresholds are not cumulative.

1–1000

Default: 0

1–1000

Default: 0

RTDA(Round Trip Delay, Average)

Query the average round trip delay in milliseconds. The thresholds are not cumulative.

1–1000

Default: 0

1–1000

Default: 0

Chapter 2 SONET Performance ParametersSONET STS Path Layer PM


RTDM(Round Trip Delay, Maximum)

Query the maximum round trip delay in milliseconds. The thresholds are not cumulative.

1–1000

Default: 0

1–1000

Default: 0

RTDS(Round Trip Delayed Seconds)

Count of the number of seconds when measured delay exceeds the expected delay. The system will raise a TCA when the measured delay exceeds the PM threshold.

1-900

Default: 25

1-65535

Default: 250

RTDTO(Round Trip Delay, Time Out)

Count of the number of seconds when delay measurement is not available due to time out (i.e., the monitoring of CTP times out and resets upon not receiving the tag within one second). The timeout seconds only accumulate when a valid F3 byte is received.

1-900

Default: 25

1-65535

Default: 250

Table 2-24 SONET STS Path PM Parameters—Near End (continued)


Table 2-25 SONET STS Path PM Parameters—Far End


CVFE(Coding Violations)

Count of the number of BIP errors detected by the far-end STS PTE and reported back to the near-end STS PTE using the REI-P indication in the STS Path overhead. Up to 8 BIP errors per frame can be indicated. The CV-PFE current second register increments for each BIP error indicated by the incoming REI-P.

1–16383

Default: 1146

1–1048575

Default: 11460


Count of the seconds during which (at any point during the second) at least one STS Path BIP error was reported by the far-end STS PTE (using the REI-P indication), a one-bit RDI-P was present, or (if ERDI-P is supported) an ERDI-P Server or Connectivity defect was present.

1–900

Default: 25

1–65535

Default: 250

Operations and Maintenance Guide, Section 2: Performance MonitoringSONET STS Path Layer PM



Count of the seconds during which 2400 or more STS Path BIP errors were reported by the far-end STS PTE, a one-bit RDI-P was present, or (if ERDI-P is supported) an ERDI-P Server or connectivity defect was present. The number of reported far-end BIP errors causing a second to be considered an SES-PFE.

1–900

Default: 4

1–65535

Default: 40


Count of the seconds during which the STS Path is considered unavailable at the far end. A path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-PFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-PFEs.

1–900

Default: 4

1–65535

Default: 40

Table 2-25 SONET STS Path PM Parameters—Far End (continued)


Chapter 2 SONET Performance ParametersSONET VT Path Layer PM


SONET VT Path Layer PM

The Traverse system provides the following performance monitoring parameters for SONET VT path layer services (vt_path_pm).

Table 2-26 SONET VT Path PM Parameters—Near End


Daily Threshold


Count of BIP errors detected at the VT Path layer (i.e., using bits 1 and 2 of the V5 byte in the incoming VT Path overhead). Up to 2 BIP errors can be detected per VT superframe, with each error incrementing the CV–V current second register.

1–16383

Default: 156

1–1048575

Default: 14976


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), an LOP–V defect or, if the VT PTE monitoring the path supports ERDI–V for that path, an UNEQ–V defect was present.

1–900

Default: 65

1–65535

Default: 648


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), an LOP–V defect or, if the VT PTE monitoring the path supports ERDI–V for that path, an UNEQ–V defect was present.

1–900

Default: 10

1–65535

Default: 100


Count of the seconds during which the VT Path was considered unavailable. A VT Path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES–Vs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES–Vs.

1–900

Default: 10

1–65535

Default: 100

Operations and Maintenance Guide, Section 2: Performance MonitoringSONET VT Path Layer PM


Table 2-27 SONET VT Path PM Parameters—Far End


Daily Threshold

CVFE (Coding Violations)

Count of the number of BIP errors detected by the far-end VT PTE and reported back to the near-end VT PTE using the REI–V indication in the VT Path overhead. Note that only 1 BIP error can be indicated per VT superframe using the REI–V bit (out of the two BIP errors that can be detected). The CV–VFE current second register increments for each BIP error indicated by the incoming REI–V.

1–16383

Default: 156

1–1048575

Default: 14796


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) an ERDI–V Server or Connectivity defect was present.

1–900

Default: 65

1–65535

Default: 648


Count of the seconds during which 600 or more VT Path BIP errors were reported by the far-end VT PTE, a one-bit RDI–V defect was present, or (if ERDI–V is supported) an ERDI–V Server or Connectivity defect was present. The number of reported far-end BIP errors causing a second to be considered an SES–VFE.

1–900

Default: 10

1–65535

Default: 100


Count of the seconds during which the VT Path is considered unavailable at the far end. A VT Path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES–VFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES–VFEs.

1–900

Default: 10

1–65535

Default: 100

Chapter 2 SONET Performance ParametersSONET Capacity Monitoring


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-28 SONET Capacity Monitoring


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

Default: 0

0–100

Default: 0

Operations and Maintenance Guide, Section 2: Performance MonitoringSONET Capacity Monitoring




Chapter 3 SDH Performance Parameters

Introduction This chapter provides performance parameter information for:• E1 Port PM, page 2-44• E3 Port PM, page 2-47• SDH High and Low Order Path PM, page 2-49• SDH Port PM, page 2-53• SDH VC-11 and VC-12 Path PM, page 2-58• SDH Capacity Monitoring, page 2-61



Operations and Maintenance Guide, Section 2: Performance MonitoringE1 Port PM


E1 Port PM The Traverse system provides the following near- and far-end E1 port performance monitoring parameters (e1_ptp_pm)_.

Table 2-29 E1 Port PM Parameters—Near End


Daily Threshold

Line–Near End

FC (Failure Counts)

Count of the number of near-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–72

Default: 4

1–4094

Default: 40


Count of both BPVs (Bipolar Violations) and EXZs (Excessive Zeros) occurring over the accumulation period. An EXZ increments the CV Line count by one regardless of the length of the zero string.

1–16383

Default: 13340

1–1048575

Default: 133400



1–900

Default: 65

1–65535

Default: 648


Count of 1-second intervals during which BPVs plus EXZs exceed 2048, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded.

1–63

Default: 10

1–4095

Default: 100

LOSS (Loss of Signal Seconds


1–63

Default: 10

1–4095

Default: 100

FAS (Frame Alignment Signal)

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

1–63Default: 2

1–4095Default: 17

Line—Far End



1–900

Default: 65

1–65535

Default: 648

Path—Near End

EB (Errored Blocks)

Count of the number of blocks containing one or more bit errors.

1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

Chapter 3 SDH Performance ParametersE1 Port PM




1–900

Default: 65

1–65535

Default: 648


Count of 1-second intervals containing:• 320 or more CRC-6 errors (ESF)• 8 or more FE events (SF)• one or more SEF or LOS defects (ESF, SF)

1–63

Default: 10

1–4095

Default: 100

AISS (Alarm Indication Signal Seconds)

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

1–63

Default: 10

1–4095

Default: 100



1–63

Default: 10

1–4095

Default: 100

BBE (Background Block Error)

An errored block not occurring as part of an SES. 1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

ESR (Errored Seconds Ratio)

The ratio of ES to total seconds in available time during a fixed measurement interval.

1–65535

Default: 4

1–65535

Default: 10

SESR (Severely Errored Seconds Ratio)

The ratio of SES to total seconds in available time during a fixed measurement interval.

1–65535

Default: 4

1–65535

Default: 10

BBER (Background Block Error Ratio)

The ratio of Background Block Errors (BBE) to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs.

1–65535

Default: 4

1–65535

Default: 10

Table 2-29 E1 Port PM Parameters—Near End (continued)


Daily Threshold



Table 2-30 E1 Port PM Parameters—Far End


Daily Threshold

Path—Far End



1–900

Default: 65

1–65535

Default: 648


Count of 1-second intervals containing:• 320 or more CRC-6 errors (ESF)• 8 or more FE events (SF)• one or more SEF or LOS defects (ESF,

SF)

1–63

Default: 10

1–4095

Default: 100



1–63

Default: 10

1–4095

Default: 100

EB (Errored Blocks)


1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

FC (Failure Count)

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

Default: 10

1–4095Default: 100


An errored block not occurring as part of an SES.

1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296

Chapter 3 SDH Performance ParametersE3 Port PM


E3 Port PM The Traverse system provides the following near- and far-end E3 port performance monitoring parameters (e3_ptp_pm).

Table 2-31 E3 Port PM Parameters–Near End


Line—Near End


Count of both BPVs (Bipolar Violations) and EXZs (Excessive Zeros) occurring over the accumulation period. An EXZ shall increment the CV Line count by one regardless of the length of the zero string. BPVs that are part of the zero substitution code are excluded.

Default: 387 Default: 3865





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.


LOSS (Loss of Signal Seconds


1–63

Default: 10

1–4095

Default: 100

Path - Near End

EB (Errored Blocks)


1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296



1–900

Default: 25

1–65535

Default: 250



1–63

Default: 4

1–4095

Default: 40





1–63

Default: 10

1–4095

Default: 10

FC (Failure Counts)

Count of the number of near-end path failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–63

Default: 10

1–4095

Default: 40

Table 2-31 E3 Port PM Parameters–Near End (continued)


Table 2-32 E3 Port PM Parameters—Far End


Path—Far End

EB (Errored Blocks)


1–8 x 106

Default: 1329

1–8 x 108

Default: 13,296



1–900

Default: 25

1–65535

Default: 250



1–63

Default: 4

1–4095

Default: 40

UAS (Unavailable Seconds


1–63

Default: 10

1–4095

Default: 10

FC (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.


Chapter 3 SDH Performance ParametersSDH High and Low Order Path PM


SDH High and Low Order Path PM

The Traverse system provides the following SDH high order (VC-4 or VC-3) and low order (VC-3) path performance monitoring parameters (sdh_hp_path_pm and sdh_lp_path_pm).

The following table lists the block size and the threshold for errored blocks for each path layer.

The following table lists the supported performance monitoring parameters for SDH paths.

Table 2-33 Number of Errored Blocks that Constitute an SES

VC type Bits/Block Blocks/Second Threshold of EBs for SES

VC-3 6120 8000 2400

VC-4 18,792 8000 2400

VC-4-4c 75,168 8000 2400

VC-4-16c 300,672 8000 2400

Table 2-34 SDH High Order VC Path andLow Order VC3 PM Parameters—Near End


EB

(Errored Block)

A block is a set of consecutive bits associated with the path. An errored block contains one or more bits with an error.

See Table 2-33 Number of Errored Blocks that Constitute an SES, page 2-49 to determine how many bits are in one block for each container type (VC-N).

1–7,200,000

Default: 20,000

1–691,200,000

Default: 200,000

ES

(Errored Seconds)

Count of 1-second period with at least one errored block or one defect.

1–900

Default: 25

1–86,400

Default: 250

Operations and Maintenance Guide, Section 2: Performance MonitoringSDH High and Low Order Path PM


SES

(Severely Errored Seconds)

Count of a 1-second period which contains 30% or more errored blocks or at least one defect. See Table 2-33 Number of Errored Blocks that Constitute an SES, page 2-49 to determine how many errored blocks constitute an SES on the path.

When a near-end SES occurs as a result of a near-end defect, the far-end performance is not evaluated during that second.

However, if a near-end SES occurs as a result of 30% or more EBs, performance monitoring at the far end continues.

1–900

Default: 4

1–86,400

Default: 40

UAS

(Unavailable Seconds)

Count of the seconds during which the path was considered unavailable. A path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ps, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps.

1–900

Default: 4

1–86,400

Default: 40

BBE

(Background Block Error)

Count of errored blocks not occurring as part of Severely Errored Seconds.

1–7,200,000

Default: 20,000

1–691,200,000

Default: 200,000

FC

(Failure Counts)


1–900

Default: 2

1–225

Default: 10

RTD

(Round Trip Delay)

Query the current round trip delay in milliseconds. The thresholds are not cumulative.

1–1000

Default: 0

1–1000

Default: 0

RTDA

(Round Trip Delay, Average)

Query the average round trip delay in milliseconds. The thresholds are not cumulative.

1–1000

Default: 0

1–1000

Default: 0

Table 2-34 SDH High Order VC Path andLow Order VC3 PM Parameters—Near End (continued)


Chapter 3 SDH Performance ParametersSDH High and Low Order Path PM


RTDM

(Round Trip Delay, Maximum)

Query the maximum round trip delay in milliseconds. The thresholds are not cumulative.

1–1000

Default: 0

1–1000

Default: 0

RTDS

(Round Trip Delayed Seconds)

Count of the number of seconds when measured delay exceeds the expected delay. The system will raise a TCA when the measured delay exceeds the PM threshold.

1-900

Default: 25

1-65535

Default: 250

RTDTO

(Round Trip Delay, Time Out)

Count of the number of seconds when delay measurement is not available due to time out (i.e., the monitoring of CTP times out and resets upon not receiving the tag within one second). The timeout seconds only accumulate when a valid F3 byte is received.

1-900

Default: 25

1-65535

Default: 250

PPJCP Det

(Positive Pointer Justifications Detected)

Count of the positive pointer justifications detected on the path.

1–1,048,575

Default: 60

1–16,777,215

Default: 6000

NPJCP Det

(Negative Pointer Justifications Detected)

Count of the negative pointer justifications detected on the path.

1–1,048,575

Default: 60

1–16,777,215

Default: 6000

PPJCP Gen (Positive Pointer Justifications Generated)

Count of the positive pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference.

1–1,048,575

Default: 60

1–16,777,215

Default: 6000

NPJCP (Negative Pointer Justifications Generated)

Count of the negative pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference.

1–1,048,575

Default: 60

1–16,777,215

Default: 6000

Table 2-34 SDH High Order VC Path andLow Order VC3 PM Parameters—Near End (continued)


Operations and Maintenance Guide, Section 2: Performance MonitoringSDH High and Low Order Path PM


Table 2-35 SDH High Order VC Path andLow Order VC3 PM Parameters—Far End


EBFE

(Errored Blocks)

Count of the number of BIP errors detected by the far-end node and reported back to the near-end node using the overhead bytes. Up to 8 BIP errors per frame can be indicated.

1–7200000

Default: 20,000

1–691200000

Default: 30,000

ESFE

(Errored Seconds)

Count of the seconds during which (at any point during the second) at least one defect is detected at the far end.

1–900

Default: 20

1–65535

Default: 200

SESFE


Count of seconds which contains 30% or more errored blocks or at least one defect at the far end.

1–900

Default: 3

1–65535

Default: 10

UASFE

(Unavailable Seconds)

Count of the seconds during which the path is considered unavailable at the far end. A path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-PFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-PFEs.

1–900

Default: 3

1–65535

Default: 10

BBEFE


Count of errored blocks at the far end not occurring as part of Severely Errored Seconds.

1–7200000

Default: 36,000

1–691200000

Default: 48,000

FCFE

(Failure Counts)

Count of the number of far-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–900

Default: 2

1–225

Default: 10

Chapter 3 SDH Performance ParametersSDH Port PM


SDH Port PM The Traverse system provides the following near- and far-end SDH port performance monitoring parameters.

Important: Default threshold values in the sdh_ptp_pm template are based on performance monitoring for STM-1 rates. Force10 recommends customizing this template for rates other than STM-1.

Table 2-36 SDH Port PM—Near End


Regenerator Section—Near End

EB (Errored Block)

Count of BIP (Bit Interleaved Parity) errors detected at the regenerator section layer (i.e., using the B1 byte in the incoming SDH signal). Up to 8 section BIP errors can be detected per STM-N frame, with each error incrementing the EB-RS register.

1–7200000

Default: 10,000

1–691200000

Default: 100,000

Recommended defaults for rates other than STM-1:

STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000

ES(Errored Seconds)

Count of 1-second intervals during which (at any point during the second) at least one regenerator section layer BIP error was detected or at least one defect was present.

1–900

Default: 25

1–65535

Default: 250


Count of the seconds during which K or more regenerator section layer BIP errors were detected or at least one defect was present. K has the following values: • 154 for STM1• 615 for STM4• 2459 for STM16• 8854 for STM64

1–900

Default: 4

1–86,400

Default: 40


Count of error block not occurring as part of Severely Errored Seconds.

1–7200000

Default: 10,000

1–691200000

Default: 100,000


STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000

Operations and Maintenance Guide, Section 2: Performance MonitoringSDH Port PM


Multiplex Section—Near End

EB(Errored Blocks)

Count of BIP errors detected at the multiplex section layer. Up to 8 section BIP errors can be detected per STM frame, with each error incrementing the EB-MS register.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

Default: 288,000

ES Errored Seconds)

Count of the seconds during which (at any point during the second) at least one multiplex section layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present.

1–900

Default: 25

1–86,400

Default: 250

SES


Count of the seconds during which K or more multiplex section layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: • 154 for STM1• 615 for STM4• 2459 for STM16• 8854 for STM64

1–900

Default: 4

1–86,400

Default: 40


Count of the seconds during which the multiplex section was considered unavailable. A multiplex section becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-MSs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-MSs.

1–900

Default: 4

1–65535

Default: 40

Table 2-36 SDH Port PM—Near End (continued)




BBE (Error Blocks)

Count of BIP errors detected at the multiplex section layer (i.e., using the B1 byte in the incoming SDH signal). Up to 8 section BIP errors can be detected per STM-N frame, with each error incrementing the EB-MS register.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

Default: 288,000

FC (Failure Counts)

Count of the number of near-end multiplex section failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–72

Default: 4

1–4094

Default: 40

Table 2-36 SDH Port PM—Near End (continued)


Table 2-37 SDH Port PM—Far End


Multiplex Section—Far End

EBFE (Errored Blocks

Count of BIP errors detected at the multiplex section layer. Up to 8 section BIP errors can be detected per STM frame, with each error incrementing the EB-MS register.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

Default: 288,000


STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000

ESFE (Errored Seconds

Count of the seconds during which (at any point during the second) at least one multiplex section layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present.

1–900

Default: 25

1–86,400

Default: 250

Operations and Maintenance Guide, Section 2: Performance MonitoringSDH Port PM



Count of the seconds during which K or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: • 154 for STM1• 615 for STM4• 2459 for STM16• 8854 for STM64

1–900

Default: 4

1–86,400

Default: 40


Count of the seconds during which the multiplex section was considered unavailable. A multiplex section becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-MSs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-MSs.

1–900

Default: 4

1–65535

Default: 40

BBEFE (Error Blocks)

Count of BIP errors detected at the multiplex section layer (i.e., using the B2 byte in the incoming SDH signal). Up to 8 section BIP errors can be detected per STM-N frame, with each error incrementing the EB-MS register.

1–1.10592 x 1010

Defaults: 28,800

1–1.03168 x 1012

Default: 288,000


STM-0: 9,600STM-4: 115,200STM-16: 460,800STM-64:1,843,200

STM-0: 96,000STM-4: 288,000STM-16: 1,152,000STM-64: 18,432,000


Count of the number of far end multiplex section failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–72

Default: 4

1–4094

Default: 40

Table 2-37 SDH Port PM—Far End (continued)




PSCWS (Protection Switch Count Working)

Count of the number of times that an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) switches from the working to the protecting facility. This count also includes the number of times the service (revertive) switches back from the protecting to the working facility.

1–63

Default: 2

1–255

Default: 10

PSDW-MS (Protection Switch Duration Working)

Count of the seconds that the working facility was being used to carry an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP).

1–900

Default: 300

1–86,400

Default: 600

PSCP-MS (Protection Switch Count Protecting)

Count of the number of times that an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) switches from the protecting to any working facility. This count also includes the number of times the service (revertive) switches back from the protecting to the working facility.

1–63

Default: 2

1–255

Default: 10

PSDP-MS (Protection Switch Duration Protecting)

Count of the seconds that the protecting facility was being used to carry an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP).

1–900

Default: 300

1–86,400

Default: 600

Table 2-37 SDH Port PM—Far End (continued)


Operations and Maintenance Guide, Section 2: Performance MonitoringSDH VC-11 and VC-12 Path PM


SDH VC-11 and VC-12 Path PM

The Traverse system provides the following SDH VC-11 and VC-12 path performance monitoring parameters (sdh_vc11_path_pm and sdh_vc12_path_pm).

The following table lists the block size and the threshold for errored blocks for each low order path layer.

The following table lists the supported performance monitoring parameters for SDH paths.

Table 2-38 Number of Errored Blocks that Constitute an SES

VC Type Bits/Block Blocks/Second Threshold of EBs for SES

VC-11 832 2000 600

VC-12 1120 2000 600

Table 2-39 SDH VC-11 and VC-12 Path PM Parameters—Near End


EB (Errored Blocks)

A block is a set of consecutive bits associated with the path. An errored block contains one or more bits with an error.

See Table 2-38 Number of Errored Blocks that Constitute an SES, page 2-58 to determine how many bits are in one block for each container type (VC-N).

1–1.8 x 106

Default: 5,000

1–1.8x108

Default: 50,000

ES(Errored Seconds)

Count of 1-second period with at least one errored block or one defect.

1–900

Default: 25

1–65,535

Default: 250


Count of a 1-second period which contains 30% or more errored blocks or at least one defect. See Table 2-38 Number of Errored Blocks that Constitute an SES, page 2-58 to determine how many errored blocks constitute an SES on the path.

When a near-end SES occurs as a result of a near-end defect, the far-end performance is not evaluated during that second.

However, if a near-end SES occurs as a result of 30% or more EBs, performance monitoring at the far end continues.

1–900

Default: 4

1–65,535

Default: 40

Chapter 3 SDH Performance ParametersSDH VC-11 and VC-12 Path PM



Count of the seconds during which the path was considered unavailable. A path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ps, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps.

1–900

Default: 4

1–65,535

Default: 40

FC (Failure Counts)


1–72

Default: 2

1–4,095

Default: 10


Count of errored blocks not occurring as part of Severely Errored Seconds.

1–1.8 x 106

Default: 5,000

1–1.8x108

Default: 50,000

PPJCP Det

(Positive Pointer Justifications Detected)

Count of the positive pointer justifications detected on the path.

1–32,767

Default: 30

1–2,097,151

Default: 300

NPJCP Det (Negative Pointer Justifications Detected)

Count of the negative pointer justifications detected on the path.

1–32,767

Default: 30

1–2,097,151

Default: 300

PPJCP Gen (Positive Pointer Justifications Generated)

Count of the positive pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference.

1–32,767

Default: 30

1–2,097,151

Default: 300

NPJCP Gen (Negative Pointer Justifications Generated)

Count of the negative pointer justifications generated on the path to reconcile the frequency of the path with the local timing reference.

1–32,767

Default: 30

1–2,097,151

Default: 300

Table 2-39 SDH VC-11 and VC-12 Path PM Parameters—Near End (continued)


Operations and Maintenance Guide, Section 2: Performance MonitoringSDH VC-11 and VC-12 Path PM


Table 2-40 SDH VC-11 and VC-12 Path PM Parameters—Far End


EBFE

(Errored Blocks)

Count of the number of BIP errors detected by the far-end node and reported back to the near-end node using the overhead bytes. Up to 8 BIP errors per frame can be indicated.

1–1.8 x 106

Default: 5,000

1–1.8x108

Default: 50,000

ESFE

(Errored Seconds)

Count of the seconds during which (at any point during the second) at least one defect is detected at the far end.

1–900

Default: 25

1–65,535

Default: 250


Count of seconds which contains 30% or more errored blocks or at least one defect at the far end.

1–900

Default: 4

1–65,535

Default: 40


Count of the seconds during which the path is considered unavailable at the far end. A path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-PFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-PFEs.

1–900

Default: 4

1–65,535

Default: 40

BBEFE


Count of errored blocks at the far end not occurring as part of Severely Errored Seconds.

1–1.8 x 106

Default: 5,000

1–1.8x108

Default: 50,000


Count of the number of far-end failure events on the line. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

1–72

Default: 2

1–4,095

Default: 10

Chapter 3 SDH Performance ParametersSDH Capacity Monitoring


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. By default, values for all thresholds are collected.

Table 2-41 SDH Capacity Monitoring


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


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

0–96 0–96


0–2016 0-2016

Operations and Maintenance Guide, Section 2: Performance MonitoringSDH Capacity Monitoring


VC-12 Available The number of additional VC-12 paths that could be created on the VT/TU card. This reflects the sum of:• 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.

0–2016 0-2016


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

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

0–100

Default: 0

0–100

Default: 0

Table 2-41 SDH Capacity Monitoring (continued)




Chapter 4 Ethernet Performance Parameters

Introduction This chapter provides performance monitoring parameter information for:• Ethernet 10GbE Equipment PM, page 2-64• EoPDH Equipment PM, page 2-66• NGE Equipment PM, page 2-69• Ethernet Port PM, page 2-71• Ethernet Service Port PM, page 2-74• EOS Port PM, page 2-76• EOP Port PM Parameters, page 2-78• Small Form-Factor Pluggable Optical Port PM, page 2-80


To generate performance monitoring data, the Collect check box of each parameter for which you wish to view data must be selected on the corresponding PM template. For more information, see Chapter 1—“Managing Performance,” Creating or Modifying a Monitoring Template, page 2-2.


Operations and Maintenance Guide, Section 2: Performance MonitoringEthernet 10GbE Equipment PM


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-42 Ethernet 10GbE Equipment PM Parameters

Parameter(Exclusive Parameter Note)

Definition Counter type

Non-resetting PM When selected, the 24-hour count for the selected template will not automatically reset every 24 hours. When disabled (not selected), the counter resets to 0 every 24 hours and can be manually reset through operator command. The default is Disabled.

Not applicable

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

G3Spi4RxOverrun 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

G3SwcBufRAMOverrun 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

G3SwcPckHdrOverrun 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

G3SwcFCBOverrun Frames discarded due to lack of frame control blocks resources. This counter could increment under heavy load.

Frame

G3SwcDPResetAbort 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

W3TxFifoIngFCDisc 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

Chapter 4 Ethernet Performance ParametersEthernet 10GbE Equipment PM


G3PortTxOverrun Ethernet or CPU port TX overruns which occurred in the TX FIFO of the port module. This counter could increment as the result of service deactivation in the presence of port transmission.

Event

G3SwcIngressShort Frames discarded when entering the switch core because they are short. Can occur as a result of bit errors or short packets received on the EOS.

Frame

G3SwcIngressPViol Protocol violations which occurred when entering the switch core. This counter could increment as a result of bit errors on the EOS.

Event

G3SwcFreeUnderrun Frames discarded because buffer memory could not be allocated fast enough internally. This can occur if a burst (>300) of very short frames (<=18 bytes) is injected into the switch core back to back.

Frame

G3Spi4RxAbort Frames discarded because the packets were received with an Abort from the framer. This counter could increment as a result of bit errors on the EOS.

Frame

G3SwcIngressLong Frames discarded when entering the switch core because they are long. This counter could increment as a result of bit errors on the Ethernet port or EOS.

Frame

Table 2-42 Ethernet 10GbE Equipment PM Parameters (continued)



Operations and Maintenance Guide, Section 2: Performance MonitoringEoPDH Equipment PM


EoPDH Equipment PM

The system provides the following performance monitoring and counters for EoPDH equipment events that occur during normal operation. For example, discarded frames or excessive traffic on a service.

Table 2-43 EoPDH Equipment PM Parameters




Not applicable

LAN SPI3 RX FIFO OVERRUNS

Count of overrun events on FIFO for SPI-3 bus in LAN to Gardenia direction.

EoPDH 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, EOS, and EOP ports. The most likely cause of the congestion is an excess of aggregate traffic arriving EoPDH from the Ethernet ports.

There could be several events for a single discarded frame, or one event for several discarded frames.

Event

LAN SPI3 TX CRC ERRORS Count of SPI-3 CRC error events in the Gardenia to LAN direction.


Event

LAN SPI3 TX PROTOCOL ERRORS

Count of protocol error events in the Gardenia to LAN direction. Protocol events include SPI-3 CRC errors, protocol violations or parity errors.


Event

LAN TX OVERSIZE COUNT Frames discarded before transmission on the physical port because they exceeded the size limit of EoPDH’s PHY. These frames are well over the EoPDH 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.

This is a normal condition that can arise when there is more multicast traffic than the system can handle.

Errored seconds

GARDENIA BUFFER ABORTS

Count of seconds during which Gardenia discarded frames due to inability to access RLDRAM buffer memory.

This could occur if ingress traffic contains a high volume of 81-byte frames.

Errored seconds

Chapter 4 Ethernet Performance ParametersEoPDH Equipment PM


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.

EoPDH increments this counter when it discards an ingress frame from an EOS (WAN-side) or EOP port due to inability of the internal switch to handle aggregate traffic arriving from Ethernet, EOS, or EOP ports. The most likely cause of the congestion is an excess of aggregate traffic arriving at the EoPDH card from the Ethernet ports.


Event

WAN ENCAPSULATION UNDERRUN

Underrun events on SPI-3 bus in Gardenia to WAN direction.


Event

WAN TX ABORTS Frames discarded due to unspecified errors in Gardenia to WAN direction.

Frame

WAN RX UPDATE DISCARDS Count of frames discarded in WAN to Gardenia direction because they could not be forwarded.

EoPDH increments this counter when it discards an ingress frame from an EOS or EOP port, because a) the VLAN ID could not be matched to an activated service, or b) the MAC address table forwards this frame’s destination address to a nonexistent port.

Frame

WAN TX SPI3 ERRORS Number of frames received on the external SPI-3 interface with protocol violation or parity error. Single word frames with error are not counted.

Event

WAN ENCAP INPUT ABORTS Number of packets aborted on the input to the Encapsulation block.

Frame

WAN ENCAP PROTOCOL VIOLATIONS

Number of internal protocol violations on the input to the Encapsulation block.

Event

WAN ENCAP TOO MUCH DATA

Number of frames received by the Encapsulation block where more data was received than was expected based on the length.

Frame

Table 2-43 EoPDH Equipment PM Parameters (continued)



Operations and Maintenance Guide, Section 2: Performance MonitoringEoPDH Equipment PM


WAN ENCAP TOO FEW DATA

Number of frames received by the Encapsulation block where less data was received than was expected based on the length

Frame

WAN ENCAP TOO SHORT Number of packets received by the Encapsulation block where the data length is too small to be encapsulated to GFP, LAPS, or PPP and therefore discarded.

Frame

Table 2-43 EoPDH Equipment PM Parameters (continued)



Chapter 4 Ethernet Performance ParametersNGE Equipment PM


NGE Equipment PM

The system provides the following performance monitoring and counters for NGE equipment (NGE and NGE Plus) events that occur during normal operation. For example, discarded frames or excessive traffic on a service.

Table 2-44 NGE Equipment PM Parameters




Not applicable

LAN SPI3 RX FIFO OVERRUNS

Count of overrun events on FIFO for SPI-3 bus in LAN to Gardenia direction.

NGE increments this counter when it discards an ingress frame from an Ethernet port due to inability of the internal switch to handle aggregate traffic arriving from Ethernet and EOS ports. The most likely cause of the congestion is an excess of aggregate traffic arriving at NGE cards from the Ethernet ports.


Event

LAN SPI3 TX CRC ERRORS Count of SPI-3 CRC error events in the Gardenia to LAN direction.


Event

LAN SPI3 TX PROTOCOL ERRORS

Count of protocol error events in the Gardenia to LAN direction. Protocol events include SPI-3 CRC errors, protocol violations or parity errors.


Event

LAN TX OVERSIZE COUNT 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.

This is a normal condition that can arise when there is more multicast traffic than the system can handle.

Errored seconds

Operations and Maintenance Guide, Section 2: Performance MonitoringNGE Equipment PM


GARDENIA BUFFER ABORTS

Count of seconds during which Gardenia discarded frames due to inability to access RLDRAM buffer memory.

This could occur if ingress traffic contains a high volume of 81-byte frames.

Errored seconds

GARDENIA SPI3 RX PROTOCOL ERRORS

Count of seconds during which Gardenia detected a SPI-3 RX interface protocol error in either the LAN to Gardenia or WAN to Gardenia direction.

Errored seconds

WAN RX FIFO OVERRUNS Count of overrun events on FIFO for SPI-3 bus in WAN to Gardenia direction.

NGE increments this counter when it discards an ingress frame from an EOS (WAN-side) port due to inability of the internal switch to handle aggregate traffic arriving from Ethernet and EOS ports. The most likely cause of the congestion is an excess of aggregate traffic arriving at the NGE card from the Ethernet ports.


Event

WAN ENCAPSULATION UNDERRUN

Underrun events on SPI-3 bus in Gardenia to WAN direction.


Event

WAN TX ABORTS Frames discarded due to unspecified errors in Gardenia to WAN direction.

Frame

Table 2-44 NGE Equipment PM Parameters (continued)



Chapter 4 Ethernet Performance ParametersEthernet Port PM


Ethernet Port PM

The system provides the following performance monitoring parameters and counters for Fast Ethernet (10/100BaseTX), Gigabit Ethernet (GbE), and 10GbE ports and the GbE ports on the GbE-10 card.

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, EoPDH, and TE-100 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 GFP 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-45 Ethernet Port PM Parameters


Definition


TX UNICAST1 The number of unicast frames transmitted with no errors.

TX MULTICAST1 The number of multicast frames that are not broadcast, transmitted with no errors.

TX BROADCAST The number of broadcast frames transmitted with no errors.

TX FRAMES1 The number of frames transmitted (unicast, multicast, and broadcast) with no errors.

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.

Operations and Maintenance Guide, Section 2: Performance MonitoringEthernet Port PM


RX > MAX FRAME SIZE The number of received frames that exceed the maximum valid packet length for the port.

RX < 64 The number of frames received, less than 64 bytes in length, received with no errors.

RX PKT 64(Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10)

The number of received 64-byte frames, including bad frames.

RX PKT 65-127(Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10)

The number of received frames, 65 to 127 bytes in length, including bad frames.









RX PKT > 1518(Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10)

The number of received frames, greater than or equal to 1519 bytes in length, including bad frames.

RX DISCARDS2,3,4 The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol.

TX DISCARDS(Traverse NGE, 10GbE, GbE-10, and EoPDH only)

The number of outbound frames discarded by this port due to aborted frames and underruns.

RX DELAY DISCARDS(TE-100 Ethernet only)

Number of frames discarded by this interface due to excessive transit delay through the bridge.

RX MTU DISCARDS(Not applicable to TE-100 Ethernet)

Number of frames discarded by this interface due to an excessive size.

RX FCS ERR5 Number of frames received which are an integral number of octets and do not pass the FCS check.

Table 2-45 Ethernet Port PM Parameters (continued)


Definition

Chapter 4 Ethernet Performance ParametersEthernet Port PM


RX MAC CTL DISCARDS (Traverse 10GbE or GbE-10 only)

The number of received “MAC control” frames that were discarded due to invalid addresses.

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.

RX BYTES2 The number of bytes received in good frames.

TX SINGLE COLL(10/100BaseTX only)

The number of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. Also counted as a successful transmission. Half-duplex operation only.

TX MULTIPLE COLL(10/100BaseTX only)

The number of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. Also counted as a successful transmission. Half-duplex operation only.

TX DEFERRED FRAMES(10/100BaseTX only)

The number of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. Does not include frames involved in collisions. Half-duplex operation only.

TX LATE COLL(10/100BaseTX only)

The number of times that a collision is detected on a particular interface later than one slotTime into the transmission of a packet. Half-duplex operation only.

TX EXCESSIVE COLL(10/100BaseTX only)

The number of frames for which transmission on a particular interface fails due to excessive collisions. Half-duplex operation only.

1 Traverse NGE, 10GbE, GbE-10, or EoPDH do not include PAUSE frames.

2 Traverse NGE, 10GbE, GbE-10, or EoPDH include packets that are < 64 or > MTU with CRC errors.

3 Traverse NGE, 10GbE, GbE-10, or EoPDH cards 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, GbE-10, or EoPDH include PAUSE frames.

Table 2-45 Ethernet Port PM Parameters (continued)


Definition

Operations and Maintenance Guide, Section 2: Performance MonitoringEthernet Service Port PM


Ethernet Service Port PM

The system provides the following performance monitoring parameters and counters for the ports on the following Traverse cards: NGE (both NGE and NGE Plus), 10GbE, GbE-10, or EoPDH.

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-46 Ethernet Service Port PM Parameters


Definition


TX BYTES (NGE, NGE Plus, and EoPDH 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).

On an NGE card, when RSTP puts an EOS in a blocking state, the RX path is disabled and no packets are forwarded to the blocked EOS.

When a port on a 10GbE or GBE-10 card is in an RSTP blocking state, the transmissions are blocked and recorded as TX RED discards.

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.

Chapter 4 Ethernet Performance ParametersEthernet Service Port PM


RX LOCAL DISCARDS (NGE, NGE Plus, and EoPDH only)

The number of packets received on this port for this service, but discarded because the destination address has been learned on the ingress port.

The counter increments when a packet having a DMAC that matches a MAC address in the MAC table and the port on which the packet was received is on the same port in the MAC table entry. Since L2 switching cannot return packets to the originating port, the packets are dropped.

RX HARDWARE PACKET DISCARDS

On NGE and EoPDH cards, indicates the number of packets dropped due to Spanning Tree port blocking. The number of packets were received on this port for this service, but were discarded due to an unclassifiable hardware error. This state can also occur if RSTP has put respective EOS in a blocking state. Broadcast or unicast unknown SMAC address packets received from other nodes in the network are discarded as RX hardware packet discards.

On 10GbE and GbE-10 ports, indicates the number of local discards, Spanning Tree discards, and packets discarded due to an unclassifiable hardware error.

Table 2-46 Ethernet Service Port PM Parameters (continued)


Definition

Operations and Maintenance Guide, Section 2: Performance MonitoringEOS Port PM


EOS Port PM The system provides the following performance monitoring parameters and counters for EOS ports.

Important: The EOS Port PM Parameters table contains common, as well as exclusive, PM (where noted) for Traverse NGE (both NGE and NGE Plus), 10GbE, GbE-10, EoPDH, and TE-100 Ethernet cards.

Note: The EOS Port and EOP Port PM byte counts include the 8-byte GFP header, allowing users to view the precise loads being handled by the EOS or EOP 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 GFP 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.

To view performance data for a card, from 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-47 EOS Port PM Parameters


Definition


TX UNICAST(TE-100 Ethernet only)

The number of unicast frames transmitted with no errors.

TX MULTICAST(TE-100 Ethernet only)

The number of multicast frames that are not broadcast, transmitted with no errors.

TX BROADCAST(TE-100 Ethernet only)

The number of broadcast frames transmitted with no errors.

TX FRAMES1 The number of frames transmitted (unicast, multicast, and broadcast) with no errors.

TX BYTES2,3 The number of bytes transmitted in good frames.

TX DISCARDS(Traverse NGE and EoPDH only)

The number of outbound frames received by this port which were discarded.

RX UNICAST(TE-100 Ethernet only)

The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors.

RX MULTICAST(TE-100 Ethernet only)

The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors.

Chapter 4 Ethernet Performance ParametersEOS Port PM


RX BROADCAST(TE-100 Ethernet only)

The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors.

RX FRAMES1 The number of frames received (unicast, multicast, and broadcast) with no errors.

RX BYTES23 The number of bytes received in good frames.

RX DISCARDS(Traverse NGE and EoPDH only)

The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol.

RX FCS ERR (Traverse 10GbE or GbE-10 only)

The number of received frames that were discarded due to incorrect Ethernet CRC.

GFP FCS DISCARDS4

(Traverse NGE and EoPDH only)The number of GFP frames discarded due to frame checksum (FCS) errors.

GFP CHEC DISCARDS The number of GFP frames discarded due to uncorrectable core header (cHEC) checksum errors.

GFP PHEC DISCARDS(Traverse NGE and EoPDH only)

The number of GFP frames discarded due to due to uncorrectable “payload header” (extension or type header) checksum (eHEC, tHEC) errors.

GFP FCS OR PHEC DISCARDS(TE-100 Ethernet only)

The number of GFP frames discarded due to frame checksum (FCS) errors, plus GFP frames discarded due to uncorrectable “payload header” (extension or type header) checksum (eHEC, tHEC) errors.

RX MTU DISCARDS(TE-100 Ethernet only)

The number of frames discarded by this interface due to an excessive size.

GFP HEC CORRECTIONS GFP frames received with single-bit HEC errors (cHEC, eHEC or tHEC) that have been corrected.

1 Traverse NGE and TE-100 Ethernet exclude CMF frames.

2 Traverse NGE and EoPDH has a complete GFP Frame, excluding CMF frames.

3 TE-100 Ethernet has Ethernet Frame only.

4 Traverse NGE and EoPDH payload FCS, includes CMF frames.

Table 2-47 EOS Port PM Parameters (continued)


Definition

Operations and Maintenance Guide, Section 2: Performance MonitoringEOP Port PM Parameters


EOP Port PM Parameters

Two Performance Monitoring templates exist for use with the EOP ports on EoPDH cards. One template controls collection of PM counters that apply to the EOP port as a whole. The other template collects PM counters for PDH events on the individual members of the EOP port. Both are provisioned on the EOP port but are used for different reasons.

EOP Port PM

The EOP port PM template (eop_pm) includes Ethernet Frame and octet counters, as well as GFP error counters. These counters apply to the non-PDH portion of the EOP port.

In Shelf View, click the Ethernet tab, click the EOP subtab, click an EOP port from the EOP port list, then click the Performance tab.

Table 2-48 EOP Port PM Parameters


Definition


TX UNICAST The number of unicast frames transmitted with no errors.

TX MULTICAST 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 FRAMES The number of frames transmitted (unicast, multicast, and broadcast) with no errors.

TX BYTES The number of bytes transmitted in good frames.

TX DISCARDS The number of outbound frames received by this port which were discarded.

RX UNICAST The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors.

RX MULTICAST 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 FRAMES The number of frames received (unicast, multicast, and broadcast) with no errors.

RX BYTES The number of bytes received in good frames.

Chapter 4 Ethernet Performance ParametersEOP Port PM Parameters


EOP Port Member PM

Each member of an EOP port is a virtual PDH port and has its own PM information. This information includes PM counters a physical PDH port such as near-end and far-end CV, ES, and SES values.

The EOP port member PM template is provisioned for one EOP port, but collects information for all the same counters on the EOP port members. For a SONET system, the port members are either DS1 or DS3. For SDH systems, the port members are either E1 or E3. For example, a DS1 EOP port with 8 members will have a single ds1_ptp_pm template. The template controls the data for all 8 sets of PM counters on that port. Each set of data can be viewed separately.

In Shelf View, click the Ethernet tab, click the EOP subtab, select an EOP port from the EOP port list, then click the Performance tab, select the Port Member from the port pulldown and then click Refresh. The values display for the port member selected (for SONET, either DS1 or DS3; for SDH, either E1 or E3). For definitions of the Ethernet port parameters, refer to Ethernet Port PM, page 2-71.

RX DISCARDS The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol.

RX FCS ERRORS The number of received frames that were discarded due to incorrect Ethernet CRC.

GFP FCS DISCARDS 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.

GFP FCS OR PHEC DISCARDS 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.

RX MTU DISCARDS The number of frames discarded by this interface due to an excessive size.

GFP HEC CORRECTIONS GFP frames received with single-bit HEC errors (cHEC, eHEC or tHEC) that have been corrected.

Table 2-48 EOP Port PM Parameters (continued)


Definition

Operations and Maintenance Guide, Section 2: Performance MonitoringSmall Form-Factor Pluggable Optical Port PM


Small Form-Factor Pluggable Optical Port PM

The Traverse system provides the following performance (diagnostic) monitoring parameters for the small form-factor pluggable (SFP) and 10 Gigabit small form-factor pluggable (XFP) optical ports.

To view SFP or XFP information, select an optical card and click the Config tab. To verify the card has an SFP or XFP, check the description of the HW Description field. To view the SFP or XFP information, refer to the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 2—“SONET Equipment,” SFP Port Parameters.

Table 2-49 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.


SECTION 3 EQUIPMENT LED STATUSSECTION 3SECTION 3

Contents

Chapter 1LEDs and Module Status

PDAP LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Front Inlet Fan Tray Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Power and Standby LED Indicators—All Modules . . . . . . . . . . . . . . . . . . . . . 3-6General Control Module (GCM) LED Indicators . . . . . . . . . . . . . . . . . . . . . . . 3-7Electrical Module Port LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Optical Module Port LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Ethernet Module Port LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Ethernet Termination Connector LED Indicators. . . . . . . . . . . . . . . . . . . . . . . 3-10Visual Status During and After Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Flashing red. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Solid green . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Operations and Maintenance Guide, Section 3 Equipment LED Status



SECTION 3EQUIPMENT LED STATUS

Chapter 1 LEDs and Module Status

Introduction Light emitting diodes (LEDs) exist on several pieces of Force10 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-3• Power and Standby LED Indicators—All Modules, page 3-6• General Control Module (GCM) LED Indicators, page 3-7• Electrical Module Port LED Indicators, page 3-8• Optical Module Port LED Indicators, page 3-9• Ethernet Module Port LED Indicators, page 3-9• Ethernet Termination Connector LED Indicators, page 3-10• Visual Status During and After Start-up, page 3-11

Operations and Maintenance Guide, Section 3: Equipment LED StatusPDAP LEDs


PDAP LEDs The following drawings illustrate 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.

Figure 3-1 PDAP-2S LEDs

Figure 3-2 PDAP-4S LEDs

The LEDs in the following table apply to LEDs on the PDAP-2S and PDAP-4S.

Table 3-1 PDAP LEDs

LED RED GREEN AMBER OFF

Critical Summary

Alarm

At least one critical alarm in

the rack.

N/A N/A No critical alarms for the entire rack.

GMT Fuse BlockPower

At least one fuse failure in GMT

Fuse Block “A” or “B.”

All fuses are good in GMT Fuse

Block “A” or “B.”

N/A No power.

InputPower

N/A Power from Battery “A” or

“B” input.

N/A No power.

Major Summary

Alarm

At least one major alarm in the rack.

N/A N/A No major alarms for the entire rack.

Chapter 1 LEDs and Module StatusFront Inlet Fan Tray Module LEDs


Front Inlet Fan Tray Module LEDs

The following drawing shows the location of the front inlet fan tray module LEDs. Refer to Table 3-2 Front Inlet Fan Card LEDs for information on how to interpret LED indicators.

Figure 3-3 Front Inlet Fan Card with LEDs

Minor Summary

Alarm

N/A N/A At least one minor alarm exists in the

rack.

No minor alarms for the entire rack.

TPA Fuse Power

(PDAP-4S only)

The TPA fuse has failed.

N/A N/A TPA fuse is good.

Table 3-1 PDAP LEDs (continued)

LED RED GREEN AMBER OFF

Power (green)

Fan Failure (red)

Power (green)

Fan Failure (red)

Operations and Maintenance Guide, Section 3: Equipment LED StatusFront Inlet Fan Tray Module LEDs


The locations of common and specific card LEDs is shown in the following graphic.

Table 3-2 Front Inlet Fan Card LEDs

LED RED GREEN OFF

Power N/A Power on No power

Fan Failure

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

N/A

• All fans are working.• Communication with

GCM is good.• All temperature

indications are good.

Chapter 1 LEDs and Module StatusFront Inlet Fan Tray Module LEDs


Figure 3-4 Physical Card LEDs

DS3/E3 OC-N/STM-N Ethernet

DS1, DS3/E3,E1, OC-N/STM-N

and ETH PortIndicators

ETHERNET LINKOSS and Craft

Alarms:CRITICAL/MAJOR

MINOR

Timing:LOCKED/

UNLOCKEDFREE RUN/HOLDOVER

RS-232 Interface(DB-9)

EGCM

ACO ON

10/100BaseTEthernet Interface

(RJ-45)

DS1 VTSwitch

ACO

PWR(Power)

ACTV/STNBY

(Active/Standby)Optical

Port

E1OPS 00015

Operations and Maintenance Guide, Section 3: Equipment LED StatusPower 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-3 Power and Active/Standby—All Cards

LEDRED Amber GREEN OFF

Flashing Solid Flashing Solid Flashing Solid

Power

Initialization and diagnosis is underway but not complete.

Hardware failure

detected; replace the

card.

N/A N/A N/A

Initialization is complete and

the card is operational.

No power.

Active/ Standby 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.

The Active card is unlocked and operational.

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.

Chapter 1 LEDs and Module StatusGeneral 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-4 GCM Alarms

LEDRED AMBER

OFFSolid Solid

Critical/ Major

One or more critical or major alarms are active. Indicates a service-affecting event(s) and requires immediate action.

N/A

No critical or major alarms

Minor N/A

One or more minor alarms are active. Indicates a non-service-affecting event(s). Take action to prevent a more serious problem.

No minor alarms

Alarm Cutoff (ACO)

N/AThe audible alarm is cut off (silenced).

The audible alarm is not cut off (not silenced).

Table 3-5 Timing Subsystem

LEDRED GREEN AMBER

OFFSolid Flashing Solid Flashing Solid

Locked/ Unlocked

Selected timing input reference is lost.

Lost-phase mode. LED flashes at 500ms on/off rate.

Locked to a timing input reference1 N/A N/A

Initialization is not complete or the GCM is in free-run mode.

Free-run/ Hold-over N/A

Tracking a timing reference signal, but not completely out of free-run mode. LED flashes at 500ms on/off rate.

Free-run mode2 Transitioning out of hold-over mode, but not Locked. LED flashes at 500ms on/off rate.

Hold-over mode.3

Initialization is not complete or the GCM is locked to a timing input reference1.

1 Timing input references are: T1, Composite Clock, or OC-N line timing reference.

2 A valid timing input reference is not available and the GCM is unable to acquire an estimate for hold-over, or the GCM is configured for free-run mode.

3 The external timing reference is degraded or lost and no other input references are available for system synchronization. The GCM was locked to its selected timing input reference and established a valid frequency estimate before going into hold-over mode.

Operations and Maintenance Guide, Section 3: Equipment LED StatusElectrical Module Port LED Indicators


:

Electrical Module Port LED Indicators

The LEDs in the following table apply to electrical (DS1, DS3, E1, E3, and VT/TU Switch) cards only.

Table 3-6 Ethernet Link (OSS and Craft 10/100BaseT)

LEDRED GREEN OFF

Flashing Solid Flashing Solid

Ethernet Port

Running diagnostics or in loopback mode.

Port is unlocked, but there is no link integrity/signal.

Transmitting or receiving frames.

Operational, the link is active.

Port is locked.

Table 3-7 Electrical Card/Port Status

RED GREEN OFF

LED Flashing Solid Flashing Solid

Ports

Running diagnostics or in loopback mode.

Unlocked and a port failure is detected (LOS, LOF/OOF, AIS, RFI)

N/A

Unlocked and receiving a valid signal.

Card initialization is not complete, the card is in Standby mode, or the port is locked.

Chapter 1 LEDs and Module StatusEthernet 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 opti-cal ports (OC-12/STM-4 or OC-48/STM-16) on the GCM with integrated optics cards.

Ethernet Module Port 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-8 Optical Card/Port Status

RED GREEN OFF

LED Flashing Solid Flashing Solid

Ports

Running diagnostics or in loopback mode

Unlocked and a port failure is detected (LOS, LOF/OOF, AIS, RFI)

Unlocked and receiving a valid signal; in Standby mode for a 1+1 facility protection group

Unlocked and receiving a valid signal

Card initialization is not complete or the port is locked

Table 3-9 GbE and Fast Ethernet Port

LEDRED GREEN OFF


Ethernet Port


Unlocked no link integrity/signal detected

Unlocked and transmitting or receiving frames

Unlocked and operational. The Ethernet link is active.


Operations and Maintenance Guide, Section 3: Equipment LED StatusEthernet 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-10 GbE and Fast Ethernet Port

LEDRED GREEN OFF


Ethernet Port


Unlocked no link integrity/signal detected

Unlocked and transmitting or receiving frames

Unlocked and operational. The Ethernet link is active.


Chapter 1 LEDs and Module StatusVisual Status During and After Start-up


Visual Status During and After Start-up

The GCM power LED indicates the status of start-up and initialization. The GCM power LED will go through the following sequence:

Flashing red

Power On Self Test (POST) is started 1.

Solid green

Initialization complete and successful.

1 The POST takes approximately one minute to run and it invokes the LED activity for initialization.

Important: The solid green Active/Standby LED indicates the active GCM card. Use the CLI to commission and configure the active GCM.

Table 3-11 Power and Active/Standby—GCM Cards



Power

Initializing; POST is started.

Hardware failure detected; replace the card.

N/A N/A Node is in commissioning

mode

Passed initialization and is operational

No power

Active/ Standby

N/A N/A Standby mode;

synchroniza-tion with the Active card

is not complete.

Card type does not match the provisioned card type or the card is placed in an invalid slot.1

Standby mode; synchroniza-tion with the active card is complete.

Active and operational


1 Please refer to Appendix A—“Card Placement Planning and Guidelines,” page 12-1 for valid card placement guidelines.

Operations and Maintenance Guide, Section 3: Equipment LED StatusVisual Status During and After Start-up



SECTION 4 DIAGNOSTICSSECTION 4

Contents

Chapter 1Diagnostics Overview

Symptoms and Recommended Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Chapter 2Traverse Transmit and Receive Signal Levels

Traverse Optical Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Chapter 3TraverseEdge 100 Transmit and Receive Signal Levels

TE-100 Optical Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Chapter 4Loopback Tests

DS1 and DS3 Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12DS1 and DS3 Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . 4-12DS1 and DS3 Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

E1 and E3 Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13E1 and E3 Facility Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13E1 and E3 Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Ethernet Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14NGE and EoPDH Ethernet Facility Loopback . . . . . . . . . . . . . . . . . . . . . 4-14Ethernet Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Facility Loopback on EOP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15SONET/SDH Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

SONET/SDH Facility Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16SONET/SDH Terminal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Performing Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Chapter 5Other Diagnostics

Power On Self Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Alarm Cut-Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21LED Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Operations and Maintenance Guide, Section 4 Diagnostics



SECTION 4DIAGNOSTICS

Chapter 1 Diagnostics Overview

Introduction The diagnostics section provides various diagnostic tips and tools to assist you isolate, and find resolution to, abnormal conditions observed while monitoring the Traverse system.

This chapter includes the following topics:• Symptoms and Recommended Actions, page 4-2• Chapter 2—“Traverse Transmit and Receive Signal Levels,” page 4-3• Chapter 3—“TraverseEdge 100 Transmit and Receive Signal Levels,” page 4-7• Chapter 4—“Loopback Tests,” page 4-11• Chapter 5—“Other Diagnostics,” page 4-21

Operations and M

aintenance Guide, S

ection4: D

iagnosticsSym

ptoms and R

ecomm

ended Actions

Page 4-2Force10 N

etworks

Release O

PS4.2.3

Symptoms and Recommended Actions

During normal operation of the Traverse system various symptoms (non-alarm/event conditions) may arise that require attention by network operations.

Table 4-1 Symptoms and Recommended Actions below describes 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 on symptom observation

Table 4-1 Symptoms and Recommended Actions

System Area Symptom Description Scope Probable Cause Recommended Action

Environmental Alarms

Environmental Alarm input or output is incorrect.

Node • Incorrect alarm cable connections

• Environmental Alarm Module (EAM) failure

• Incorrect alarm cable connections. See the Traverse Installation and Commissioning Guide, Section 1—Fault Management, Chapter 2—“Alarms, Events, and Recommended Actions,” page 1-33

• Replace EAM. See Section 6—Routine Maintenance, Chapter 1—“Routine Maintenance,” Environmental Alarm Module Replacement (Traverse only), page 6-20



Chapter 2 Traverse Transmit and Receive Signal Levels

Introduction This chapter provides optical parameter specifications to assist you in handling a Loss of Signal (LOS) condition on a Traverse optical module.

Operations and M

aintenance Guide, S

ection4: D

iagnosticsTraverse O

ptical Interface Specifications

Page 4-4Force10 N

etworks

Release O

PS4.2.3

Traverse Optical Interface Specifications

The table below provides a summary of all optical interface specifications.

OPTIC 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 10dB attenuation is required for long reach optics.

Table 4-2 Traverse Optical Interface Specification Summary Table

Optical Interface Card Optic Type

Typical Nominal TX Wavelength

TX Wavelength

Range

RX Wavelength

Range

Transmitter Output Power1

Receiver Signal1,2

Guaranteed Link

Budget1

Distance Objective 3, 4

(nm) (nm) (nm) (dBm) (dBm) (dB) (mi) (km)

Fast Ethernet(10/100)

100BaseFX (GbE/Fast Ethernet combo)

1310 1261 to 1360 1260 to 1600 -16 to -14 -29 to -14 13 20.2 32.5

GbE 1000Base-X (SFP)Pluggable SFP

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

GbE CWDM 1470 to 1610(8 channels at 20 nm intervals)

1260 to 1620 -1 to 4 -18 to -0 17 24.85 40

10GbE(XFP)Pluggable SFP

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/STM-1 OC-3 IR1/STM-1 SH1 / S-1.1 1310 1261 to 1360 1260 to 1600 -16 to -8 -28 to -7 12 9.32 15

OC-3 LR2/STM-1 LH2 / L-1.2 1550 1480 to 1580 1260 to 1600 -6 to 0 -32 to -10 26 49.71 80

OC-12/STM-4 OC-12 IR1/STM-4 SH15 / S-4.1 1310 1274 to 1356 1260 to 1600 -16 to -8 -27 to -7 11 9.32 15

OC-12 LR2/STM-4 LH25 / L-4.2 1550 1480 to 1580 1260 to 1600 -4 to 2 -26 to -8 22 49.71 80

Chapter2

Traverse Transmit and R

eceive Signal Levels

Traverse Optical Interface Specifications

Release O

PS4.2.3Force10 N

etworks

Page 4-5

OC-48/STM-16 OC-48 SR1/STM-16 SH15 / I-16 1310 1266 to 1360 1260 to 1600 -11 to -3 -17 to -3 6 1.24 2

OC-48 IR1/STM-16 SH15 / S.16.1

1310 1260 to 1360 1260 to 1600 -6 to 0 -17 to 0 11 9.32 15

OC-48 LR1/STM-16 LH15 / L-16.1

1310 1280 to 1335 1260 to 1600 -3 to 3 -26 to -8 23 24.85 40

OC-48 LR2/STM-16 LH25 / L-16.2

1550 1500 to 1580 1260 to 1600 -3 to 3 -25 to -8 22 49.71 80

OC-48 LR2/STM-16 LH CWDM 1470 to 1610(8 channels at 20 nm intervals)

1260 to 1620 -1 to 5 -25 to -8 24 49.71 80

OC-48 ELR/STM-16 LH ITU DWDM

1529.55 to 1562.23 (42 channels)

1260 to 1600 -1 to 4 -26 to -8 25 62.14 100

OC-48 VR2/STM-16 VLH 1550 1530 to 1560 1260 to 1600 4 to 10 -25 to -8 29 62.14 100

OC-48 VR/STM-16 VLH DWDM

1529.55 to 1562.23 (42 channels)

1260 to 1600 4 to 10 -25 to -8 29 62.14 100

OC-192/STM-646 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

Table 4-2 Traverse Optical Interface Specification Summary Table (continued)

Optical Interface Card Optic Type

Typical Nominal TX Wavelength

TX Wavelength

Range

RX Wavelength

Range

Transmitter Output Power1

Receiver Signal1,2

Guaranteed Link

Budget1

Distance Objective 3, 4

(nm) (nm) (nm) (dBm) (dBm) (dB) (mi) (km)

Operations and M

aintenance Guide, S

ection4: D

iagnosticsTraverse O


Page 4-6Force10 N

etworks

Release O

PS4.2.3

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 223 -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, connectors, 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, connectors, etc.).

4 Force10 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 3 TraverseEdge 100 Transmit and Receive Signal Levels

Introduction This chapter provides optical parameter specifications to assist you in handling a Loss of Signal (LOS) condition on a TraverseEdge 100 optical port.

Operations and M

aintenance Guide, S

ection4: D

iagnosticsTE-100 O


Page 4-8Force10 N

etworks

Release O

PS4.2.3

TE-100 Optical Interface Specifications

The table below summarizes all optical interface specifications. This table represents data for Force10 -approved SFPs. Additional SFPs may now be available; contact your Force10 sales representative.

Table Notes:• 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.

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 Force10 or equipment damage may occur, thus voiding any TE-100 warranty.

Table 4-3 SONET, STM, and GbE Optics for the TE-100

Application Approx Distance

(km)

Tx Power Range(dBm)

Rx Power Range(dBm)

Dispersion Penalty

(db)

Attenuation Range

Extinction Ratio (dB)

Tx Wavelength

Range(nm)

RxWavelength

Range(nm)

Dispersion Tolerance (ps/nm)

Temperature Range (degC)SONET STM

OC-3 IR-1 STM-1 S-1.1 15 -15 to -8 -29 to -7 0 0 to 14 8.2 1261 to 1360 1260 to 1600 0 -40 to 85

OC-3 LR-2 STM-1 L-1.2 80 -5 to 0 -33 to -10 1 10 to 28 10 1480 to 1580 1260 to 1600 0 -40 to 85

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 -40 to 85

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 -40 to 85

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 -40 to 85

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 -40 to 85

OC-48 LR-2 STM-16 L-16.2 80 0 to 5 -26 to -8 2 13 to 26 8.2 1470 to 1610 1260 to 1600 1760 -5 to 70

OC-48 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 -40 to 85

OC-48 ELR STM-16 100 0 to 4 -27 to -8 2 12 to 27 8.2 1529.55 to 1562.23

1260 to 1600 1750 0 to 70

1000Base SX 1000Base SX 0.555 -9.5 to -4 -17 to -3 0 0 to 7.5 9 830 to 860 770 to 860 0 -40 to 85

1000Base LX 1000Base LX 10 -9 to -3 -19 to -3 0 0 to 10 9 1270 to 1360 1270 to 1355 0 -40 to 85

1000Base ZX 1000Base ZX 80 0 to 5 -23 to -3 1 8 to 23 9 1530 to 1580 1260 to 1620 1600 -40 to 85

Operations and M

aintenance Guide, S

ection4: D

iagnosticsTE-100 O


Page 4-9Force10 N

etworks

Release O

PS4.2.3

Operations and Maintenance Guide, Section 4: DiagnosticsTE-100 Optical Interface Specifications




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

Important: Facility and terminal loopbacks cannot be performed on most ports, part of a BLSR/MS-SP Ring, or on a 1+1 APS/MSP protection group. Facility loopbacks can be performed on EOP ports.

This chapter contains the following card-specific loopback tests:• DS1 and DS3 Loopback Tests, page 4-12• E1 and E3 Loopback Tests, page 4-13• Ethernet Loopback Tests, page 4-14• SONET/SDH Loopback Tests, page 4-16

See Performing Loopback Tests, page 4-17 for a step-by-step procedure on how to perform loopback tests.

See Equipment States, page 4-19 for a discussion of the Traverse operational and administrative states.

WARNING! Loopback tests interrupt traffic flow; do not perform them on nodes providing service.

Operations and Maintenance Guide, Section 4: DiagnosticsDS1 and DS3 Loopback Tests


DS1 and DS3 Loopback Tests

DS1 and DS3 Facility Payload Loopback

Each node or EOP port supports a facility payload loopback for each incoming received DS-x signal. The facility must first be taken out of service before starting the loopback test.

The facility payload loopback connects the incoming received DS-x signal immediately to the associated return transmitter as shown in Figure 4-1. During this loopback, AIS is inserted and sent to the far end.

Figure 4-1 DS-x Facility Payload Loopback

DS1 and DS3 Terminal Loopback

The node supports terminal loopback for each DS-x signal. The facility must first be taken out of service before starting the loopback test.

For DS1 and DS3 terminal loopback, the signal is looped back toward the SONET/SDH system just before being transmitted toward the DS-x line as shown in Figure 4-2. This loopback is used to verify the receiver associated with the interface and the integrity of the transmitted DS-x signal.

Figure 4-2 DS-x Terminal Loopback

OPS 00027

DS-x card Trunk card

LIU LIUAIS

DS-x facility underloopback test

TestSet

Servicebetween ports

DS-x card Trunk card

LIU LIU

DS-x facility underloopback test

TestSet

Service set upbetween ports

OPS 00028

Chapter 4 Loopback TestsE1 and E3 Loopback Tests


E1 and E3 Loopback Tests

E1 and E3 Facility Payload Loopback

The node supports a facility payload loopback for each incoming received E-x signal. The facility must first be taken out of service prior to initiating the loopback test.

The facility payload loopback connects the incoming received E-x signal immediately to the associated return transmitter, as shown in Figure 4-1. During this loopback, AIS is inserted and sent to the far end.

Figure 4-3 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 before starting the loopback test.

For E1 and E3 terminal loopback, the signal is looped back toward the SONET/SDH system just before being transmitted toward the E-x line, as shown in Figure 4-2. This loopback is used to verify the receiver associated with the interface and the integrity of the transmitted E-x signal.

Figure 4-4 E-x Terminal Loopback

OPS 00029

E-x module Trunk module

LIU LIUAIS

E-x facility underloopback test

TestSet


E-x module Trunk module

LIU LIU

E-x facility underloopback test

TestSet


OPS 00030

Operations and Maintenance Guide, Section 4: DiagnosticsEthernet Loopback Tests


Ethernet Loopback Tests

NGE and EoPDH Ethernet Facility Loopback

The node supports a facility payload loopback for next-generation Ethernet interfaces. All packets that the Ethernet card receives from a CPE port are transmitted back on the same CPE port. Service providers can use this to check the local cabling from CPE device to the node.

Facility loopback does not affect traffic flow on any other Ethernet port. If an Ethernet port is in an activated Ethernet service, the system prohibits facility loopback. If facility loopback is active, the system prohibits the activation of any Ethernet service.

The facility payload loopback connects the incoming received signal immediately to the associated return transmitter, as shown in Figure 4-5. The facility loopback is in effect across card reboot.

Figure 4-5 Ethernet Facility Payload Loopback

Ethernet Terminal Loopback

The node supports terminal loopback for next-generation Ethernet interfaces. Ethernet terminal loopback uses the forwarding relationship established by an Ethernet service to loop back packets to their sources, instead of transmitting them out the looped-back facility. This function requires the facility be in use by one or more activated Ethernet services that use point-to-point forwarding. (i.e., Line services).

Important: When facility loopback is on for the next-generation Ethernet port, and when no other Ethernet ports on this card are sending or receiving frames, 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.

Ethernet frames

OPS 00031

Ethernet card

Ethernetfacility inFacility

Loopback

Traverse Node

Chapter 4 Loopback TestsFacility Loopback on EOP Ports


For Ethernet terminal loopback, the signal is looped back toward the SONET/SDH system just before being transmitted toward the Ethernet interface.

Figure 4-6 Ethernet Terminal Loopback

Facility Loopback on EOP Ports

Facility loopback on an EOPDH card occurs when a manual facility loopback is applied to the EOP port member. The PDH signal, shown in red in the following diagram, sends a copy of a received PDH signal to the transmit PDH signal while continuing to forward the received PDH signal to the EOP port’s VCAT or GFP function.

Figure 4-7 EOP Port Member Facility Loopback

The system allows up to 16 concurrent facility loopback settings on any EOP port member. A loopback facility alarm (LPBKFACILITY) is raised on the EOP port member while the local loopback is in effect.

Ethernetfacility inTerminalLoopback GFP-encapsulated

Ethernet overSONET / SDH

OPS 00032

Ethernet cardNode

EOS port

L ActivatedLineservice(s)O (i)

SL

Trunk Card

EoPDH card OC-N/STM-Ntransport card

LIUTest Set

PDHmember

OPS 00094

GFP,VCAT

EthernetSwitch

PDH payloadgenerated and

consumed here

Operations and Maintenance Guide, Section 4: DiagnosticsSONET/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 before starting 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-8. During this loopback, AIS is inserted and sent to the far end.

Figure 4-8 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 before starting 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-9. Terminal loopback is used to verify the integrity of the electronics associated with the framer or the transmitted signal.

Figure 4-9 SONET/SDH Terminal Loopback

OC-N module OC-N module

LIU LIUAIS

SONET facilityunder loopback test

STS-NSTS-N

TestSet


OPS 00033

OC-N/STM-Nmodule

OC-N/STM-Nmodule

LIU LIU

SONET/SDH facilityunder loopback test

TestSet


OPS 00034

Chapter 4 Loopback TestsPerforming Loopback Tests


Performing Loopback Tests

Before performing loopback testing, the port’s administrative state must first be changed to Unlocked.

Use the vendor’s procedures for setting up your test equipment, then follow the procedure below to perform loopback tests on a port.

The loopback state or port lock/unlock state is be restored after a node database restore operation is performed. Instead, the system uses the current state of the port to override what was stored in the node database.

Important: Loopback tests interrupt data flow; do not perform them on a port providing service.

Table 4-4 Performing Loopback Tests

Step Procedure

1 In the GUI, display the Shelf View of the node on which you will perform loopback tests. If you are currently in Map View, double-click the node to switch to the Shelf View.

2 Select a port on the appropriate card.


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.

8 From the Loopback drop-down list, select one of the following types of loopback tests to run:

– Facility: Troubleshoot the line interface unit (LIU) of a card, the backplane, and the cable.

– Terminal: Troubleshoot a circuit path and loop back from the card.

Figure 4-10 Setting Up a Loopback Test

Operations and Maintenance Guide, Section 4: DiagnosticsPerforming Loopback Tests


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. Take corrective action.

11 After receiving feedback on the test equipment about the success or failure of the loopback test, clear the loopback test.

Select Clear on the Loopback status drop-down list, then click Apply.

12 The Performing Loopback Tests procedure is complete.

Table 4-4 Performing Loopback Tests (continued)

Step Procedure

Chapter 4 Loopback TestsEquipment States


Equipment States

Icons in the bottom left-hand corner of the Config tab indicate the state of the card or port.

Figure 4-11 Equipment States

Equipped State: Displays one of the following values:• Equipped: Indicates the equipped state of the card or port. When Equipped, the

equipment is present in the system.• Non-Equipped: When selected, indicates the card or port is Non-Equipped; the

equipment is not present in the system.

Operational State: Displays one of the following values:• 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 values 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.

Operational state

Equipped state

Administrative state

Operations and Maintenance Guide, Section 4: DiagnosticsEquipment States




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

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-activate. Press the ACO button on the active module to silence the audible alarm and have the ACO LED change color 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 display 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.

Operations and Maintenance Guide, Section 4: DiagnosticsLED Lamp Test



SECTION 5 TEST ACCESSSECTION 5

Contents

Chapter 1Traverse Test Access

Local Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Remote Test Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Mode Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Access Identifier (AID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Monitor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Split Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Feature Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Test Access Mode Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Monitor Test Access Example (MONE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Per Side Split Test Access Example (SPLTE) . . . . . . . . . . . . . . . . . . . . . . . . 5-13Series Split Test Access Example (SPLTA) . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Chapter 2Traverse Test Access Guidelines for the Spirent BRTU Interface

Traverse Platform and Spirent BRTU Interoperability . . . . . . . . . . . . . . . . . . . 5-22Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface . . . . 5-23

Operations and Maintenance Guide, Section 5 Test Access



SECTION 5TEST ACCESS

Chapter 1 Traverse Test Access

Introduction (SONET network only) Traverse Test Access on digital cross-connect (DCS3/1) systems and Add-drop Multiplexer (ADM) systems provides for non-intrusive monitoring and intrusive split testing of DS3/STS-1 and DS1/VT1.5 digital signals.

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

For parameter descriptions, see the TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 5—“Test Access”.

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

Operations and Maintenance Guide, Section 5: Test AccessLocal Test Access


Local Test Access

The figure below shows the digital signal for monitoring or testing drops at a logical, pre-configured test access point (TAP). You pre-configure 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. You establish TACs through the node-level control link or TransNav management system interface. With the test access cross-connects in service, you can monitor or perform tests using the test system controller (TSC) user interface to the RTU.

The Traverse system automatically disconnects all in-service TACs and restores all the original services upon reboot or communication loss with the RTU.

Figure 5-1 Local Traverse DCS3/1 Test Access

OPS 00039

TestSystem

Controller(TSC)

Test Access Point (TAP)(e.g., DS1 port)

ManagementSystem

(GUI, CLI, or TL1)

DCS3/1

RemoteTestUnit

(RTU)

Patch Panel

Node-level Control Link(CLI or TL1)Termination Point (TP)

of the Circuit Under Test

TransNav

Chapter 1 Traverse Test AccessRemote Test Access


Remote Test Access

The figure below shows the Remote test access that provides for the configuration of and access to TAPs at a remote location or network element. 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 figure below shows the remote test access network configuration. At the top of the figure is the Traverse DCS3/1. A static STS-1 or VT1.5 path is created across the service provider network from the remote multiplexer to the Traverse DCS3/1. A remote test unit (RTU) is connected with physical TAPs to a remote access multiplexer. When references are made to the logical VT1.5 level TAPs on the Traverse DCS3/1, the resulting test access configurations are effectively cross-connected to DS1 ports on the remote multiplexer for testing.

Figure 5-2 Remote Traverse DCS3/1 Test Access

OPS 00040

SONETNetwork

Remote Test Unit(RTU)

Remote AccessMultiplexer

Physical TAPs (e.g., DS1)

Logical TAPs(e.g., VT1.5 on OC-N port)

DCS3/1

STS-1or VTPath

Operations and Maintenance Guide, Section 5: Test AccessMode Configurations


Mode Configurations

There are multiple monitor and split test access mode configurations available for use with bidirectional, unidirectional, and unmapped DS3/STS-1 and DS1/VT1.5 services.

The Traverse system supports the following test access mode configurations:• Monitor Configurations, page 5-6• Split Configurations, page 5-7

Each test access mode supports a set of service types. The following table lists the test access mode versus service compatibility matrix where A = Allowed, NA = Not Allowed.

Table 5-1 Test Access Mode vs. Service Compatibility Matrix

ModeService

Bidirectional Unidirectional Unmapped

MONE A A A

MONEF A NA NA

MONF A NA NA

SPLTA A A NA

SPLTB A NA NA

SPLTE A A A

SPLTEF A NA NA

SPLTF A NA NA

Chapter 1 Traverse Test AccessAccess Identifier (AID)


Access Identifier (AID)

The access identifier (AID) is a simple or compound string to uniquely identify a Traverse service (ingress or egress) endpoint.

Although the endpoint is the same, the actual AID format differs between the TransNav management system or node-level access interfaces (GUI and TL1) quite simply because there are underlying interface structural differences.• TransNav GUI AID Format—For example, the AID format for a DS1 port facility

is the following compound string group s(1-M)(DS1), p(1-28)(DS1). The s stands for slot. The M is 4 for the Traverse 600, 12 for the Traverse 1600, or 16 for the Traverse 2000, offering all possible module (card) slot choices. The p stands for port. The port number choices are from 1 to 28. DS1 identifies the module and port type, respectively. See Figure 5-3 TransNav GUI AID Format Example below.For service endpoint mapping definitions, refer to the TransNav Provisioning Guide, Section 9—Appendices, Appendix B—“Service Endpoints”

Figure 5-3 TransNav GUI AID Format Example

• TL1 AID Format—For example, the AID format for a DS1 port facility is FAC-(1-M)-(1-28). (FAC stands for facility.) The M is 4 offering 1 to 4 possible module (card) slot choices on the Traverse 600, 12 offering 1 to 12 possible module slot choices on the Traverse 1600, or 16 offering 1 to 16 possible module slot choices for the Traverse 2000. The port number choices are from 1 to 28.For a list of TL1-specific Traverse system AID formats, refer to the TransNav Management System TL1 Guide, Appendix C—AIDs.

Operations and Maintenance Guide, Section 5: Test AccessMonitor Configurations


Monitor Configurations

Each monitor configuration is non-intrusive. The original service remains intact so there is no disruption to customer traffic while monitoring the data flow.

Test access provides three monitor mode configurations:• MONE - Monitor unidirectional data flow from ingress to egress termination point• MONF - Monitor unidirectional data flow from egress to ingress termination point1

• MONEF - Monitor bidirectional data flow from both the ingress and egress termination points

Figure 5-4 Monitor Configurations

1 If MONF is configured with a DFAD instead of the standard FAD, it uses the second FAD.

FAD

E F

MONF Test Access

FAD

E F

MONE Test Access

FAD

E F

MONEF Test Access

FADOPS 00042

Chapter 1 Traverse Test AccessSplit Configurations


Split Configurations

Each split configuration is intrusive. These configurations disable the original service so there is disruption to customer traffic. There are two kinds of split configurations: series and per side.

Test access provides five split mode configurations:• SPLTE - Per side split on the ingress termination point to test the ingress service• SPLTF - Per side split on the egress termination point to test the egress service2

• SPLTEF - Per side split on both the ingress and egress termination points to simultaneously test services

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

Figure 5-5 Split Configurations

2 If SPLTF is configured with a DFAD instead of the common FAD, it uses the second FAD.

3 If SPLTB is configured with a DFAD instead of the standard FAD, it uses the second FAD.

A

B

SPLTB Test Access

FAD

A

B

SPLTA Test Access

FAD

E

F

SPLTF Test Access

FAD

E

F

SPLTE Test Access

FAD

FAD

E

F

SPLTEF Test Access

FAD OPS 00043

Operations and Maintenance Guide, Section 5: Test AccessFeature Set Options


Feature Set Options

The Traverse system provides the following full feature set module and user access interface options to support DCS3/1 test access applications. Choose those options 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 supports SONET STS-1 or SDH TU-3/TUG-3/AU-3 mapping of DS3/E3/EC-1 client signals.

– DS3/EC-1 Transmux—The DS3/EC-1 Transmux module is a single-slot 12-port module that provides DS3 transmultiplexing (transmux) functions for channelized DS3 access to the Traverse platform. In addition to transmux functionality, any port can be independently configured for DS3 clear channel or EC-1 through the user interface.

– OC-N/STM-N—The OC-N/STM-N modules integrate the capabilities of a high-performance SONET/SDH Add-Drop Multiplexer (ADM) and a non-blocking cross-connect in a single module. The OC-N/STM-N module ports can be used as a trunk interface or for the aggregation and grooming of SONET/SDH services.

– Virtual Tributary/Tributary Unit (VT/TU) Switch—The VT/TU 5G Switch module integrates wideband switching and grooming functions into the Traverse platform. This module has a termination capacity of 5 Gbps for up to 32 STS-3c/AU-4 equivalents or 96 STS-1/AU-3 equivalents.

– Virtual Tributary Cross-connect (VTX)—The OC-48/STM-16 and GCM modules with an integrated virtual tributary/container (VT/VC) cross-connect component (VTX/VCX) known simply as VTX. The VTX component has a termination capacity of 2.5 Gbps for up to 16 STS-3c/AU-4 equivalents or 48 STS-1/AU-3 equivalents.

• User Access Interfaces:– Node-level Control Link—Direct test access configuration management via

standards-compliant node-level TL1 (Transaction Language 1) or CLI (Command Line Interface) control link interface from the TSC or RTU to the Traverse general control module. The physical connection of the control link is between the Traverse DCS3/1 system general control module (GCM) and the remote test system utilizing the Ethernet interface. The CLI interface also supports the RS-232 interface.

– TransNav Management System—Direct test access configuration management via the TransNav graphical user interface (GUI), CLI, or TL1 interface. Refer to the TransNav Management System Product Overview Guide.

Chapter 1 Traverse Test AccessMonitor Test Access Example (MONE)


Configuration Management

You can manage the test access feature through the GUI, CLI, or TL1 interface. Each interface is unique and offers the ability to create, change mode, view, disconnect, and report on test access configurations.• GUI—The procedures in this chapter use this interface. For further information,

refer to the TransNav Management System GUI Guide.• CLI—CLI scripts may be written to automate test access. These scripts run in the

TSC or the RTU itself. For further information, refer to the TransNav Management System CLI Guide.

• TL1—TL1 scripts may be written to automate test access. These scripts run in the TSC or the RTU itself. This interface is interoperable with the Spirent® network tester, BRTU with REACT® remote test OSS. For further information, refer to the TransNav Management System TL1 Guide.

Test Access Mode Examples

The test access mode examples identified below use the TransNav management system as the user interface for configuration management.

See one of the following test access mode examples:• Monitor Test Access Example (MONE), page 5-9• Series Split Test Access Example (SPLTA), page 5-17• Per Side Split Test Access Example (SPLTE), page 5-13

Monitor Test Access Example (MONE)

The MONE (Monitor-E) monitor test access configuration is non-intrusive. There is no disruption to customer traffic.

The figure below shows a MONE monitor test access configuration. 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.

Figure 5-6 Monitor Test Access Configuration—MONE

Service to be Tested

Monitor Test Access(Non-Intrusive)

TAP (e.g., DS1)

DCS D1S1

TAP1

DCS D1S1

OPS 00011

Operations and Maintenance Guide, Section 5: Test AccessMonitor 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)

Chapter 1 Traverse Test AccessMonitor Test Access Example (MONE)


3 From the Test Access tab, TAC sub-tab, create a Monitor-E (MONE) TAC from the source (S1) to a logical TAP.

Note: Use the Switch Mode button to switch from one mode configuration to another. For valid mode changes, see Table 5-1 Test Access Mode vs. Service Compatibility Matrix.

Figure 5-8 MONE TAC Example

Table 5-2 Monitor Test Access Configuration—MONE (continued)

Step Procedure

TAP1MONE Mode Service ID Connected State

Switch Mode command

Operations and Maintenance Guide, Section 5: Test AccessMonitor Test Access Example (MONE)


4 The original service remains intact (enabled) as seen when you select the Service tab.

Figure 5-9 Service with MONE TAC Example

5 With the TAC enabled to the RTU, you can now monitor the ingress (S1) to egress (D1) data flow at the source service under test.

6 To disconnect the TAC from the original (and still active) service, simply remove the TAC.

7 The Monitor Test Access Configuration—MONE procedure is complete.

Table 5-2 Monitor Test Access Configuration—MONE (continued)

Step Procedure

Service ID Enabled Operational State

Chapter 1 Traverse Test AccessPer Side Split Test Access Example (SPLTE)


Per Side Split Test Access Example (SPLTE)

The SPLTE per side split test access configuration is intrusive.

The figure below shows a SPLTE per side split test access configuration. At the top of the figure, a service is provisioned and activated between the source (S1) and destination (D1). The original service operational state is enabled and the service state is active. The service under the test operational state is disabled.

Figure 5-10 Per Side Split Test Access Configuration—SPLTE


Per Side Split Test Access(Intrusive)

TAP (e.g., DS1)

DCS D1S1

TAP1

DCS D1S1

OPS 00047

Operations and Maintenance Guide, Section 5: Test AccessPer Side Split Test Access Example (SPLTE)


Use the following procedure to create the per side split test access configuration.

Table 5-3 Per Side Split Test Access Configuration—SPLTE

Step Procedure

1 Physically connect the cables for TAP from the remote test unit (RTU) into the patch panel connected to the Traverse DSC3/1.

2 Using the TransNav GUI, from the Test Access, TAP tab, create a logical test access point (TAP) (single FAD) of the same type as the source termination point (S1).

Figure 5-11 Example VT TAP (Single FAD)

Chapter 1 Traverse Test AccessPer Side Split Test Access Example (SPLTE)


3 From the Test Access tab, TAC sub-tab, create a per side split (SPLTE) test access cross-connect (TAC) from the source (S1) to a logical TAP.


Figure 5-12 SPLTE TAC Example

Table 5-3 Per Side Split Test Access Configuration—SPLTE (continued)

Step Procedure

TAP2SPLTE Mode Service ID Connected State

Switch Mode command

Operations and Maintenance Guide, Section 5: Test AccessPer Side Split Test Access Example (SPLTE)


4 The system disables the original service as seen when you select the Service tab.

Figure 5-13 Service with SPLTE TAC Example

5 With the TAC enabled to the RTU, you can now run various tests on the source service under test.

Note: An alarm indication signal (AIS) is automatically transmitted in the direction of D1 to show service disruption due to the test configuration.

6 To remove the TAC from the original (and still active) service, simply remove the TAC.

Note: The system restores the original service state.

7 The Per Side Split Test Access Configuration—SPLTE procedure is complete.

Table 5-3 Per Side Split Test Access Configuration—SPLTE (continued)

Step Procedure


Chapter 1 Traverse Test AccessSeries Split Test Access Example (SPLTA)


Series Split Test Access Example (SPLTA)

The SPLTA series split test access configuration is intrusive.

The figure below shows a SPLTA series split test access configuration. At the top of the figure, a service is provisioned and activated between the source (S1) and destination (D1). The original service operational state is enabled and the service state is active. The service under the test operational state is disabled.

Figure 5-14 Series Split Test Access Configuration—SPLTA


Series Split Test Access(Intrusive)

TAP (e.g., DS1)

DCS D1S1

TAP1

DCS D1S1

OPS 00051

Operations and Maintenance Guide, Section 5: Test AccessSeries Split Test Access Example (SPLTA)


Use the following procedure to create the series split test access configuration.

Table 5-4 Series Split Test Access Configuration—SPLTA

Step Procedure

1 Physically connect the cables for TAP (test access point) from the remote test unit (RTU) into the patch panel connected to the Traverse DSC3/1.

2 Using the TransNav GUI, from the Test Access tab, TAP sub-tab, create a logical TAP (single FAD) of the same type as the source termination point (S1).

Figure 5-15 Example DS1 TAP (Single FAD)

Chapter 1 Traverse Test AccessSeries Split Test Access Example (SPLTA)


3 From the Test Access tab, TAP sub-tab, create a series split (SPLTA) test access cross-connect (TAC) from the source (S1) to a logical TAP.


Figure 5-16 SPLTA TAC Example

Table 5-4 Series Split Test Access Configuration—SPLTA (continued)

Step Procedure

TAP3SPLTE Mode Service ID Connected State

Switch Mode command

Operations and Maintenance Guide, Section 5: Test AccessSeries Split Test Access Example (SPLTA)


4 The system disables the original service as seen when you select the Service tab.

Figure 5-17 Service with SPLTA TAC Example

5 With the TAC enabled to the RTU, you can now run various tests on the source service under test.

6 To remove the TAC from the original (and still active) service, simply remove the TAC.

Note: The system restores the original service state.

7 The Series Split Test Access Configuration—SPLTA procedure is complete.

Table 5-4 Series Split Test Access Configuration—SPLTA (continued)

Step Procedure



SECTION 5TEST ACCESS

Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface

Introduction This section 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”.

Operations and Maintenance Guide, Section 5: Test AccessTraverse Platform and Spirent BRTU Interoperability


Traverse Platform and Spirent BRTU Interoperability

The Traverse platform interoperates with the Spirent® Communication’s Broadband Remote Test Unit (BRTU) network tester to provide integrated test access functionality. The Traverse system, TransNav management system graphical user interface (GUI), and Spirent BRTU with REACT® remote test Operations Support System (OSS) enables carriers to test and monitor any DS1/VT1.5 or DS3/STS-1 service provisioned on the Traverse switch fabric.

Figure 5-18 Force10 TransNav GUI and Spirent BRTU REACT OSS Example

Spirent REACT OSSForce10 TransNav GUI

Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU InterfaceGuidelines to Set Up the Traverse Test Access Spirent BRTU Interface


Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface

Use the following guidelines to set up Traverse test access interoperability with the Spirent BRTU. Read through all of these guidelines before you begin the system setup.• The Username and Password TransNav management system parameters must be

in all caps format. For parameter descriptions, refer to the TransNav Management System GUI Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures”.

• 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 Provisioning Guide, Section 9—Appendices, Appendix B—“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 5—Test Access, Chapter 1—“Traverse Test Access” 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.

Operations and Maintenance Guide, Section 5: Test AccessGuidelines to Set Up the Traverse Test Access Spirent BRTU Interface



SECTION 6 ROUTINE MAINTENANCESECTION 6SECTION 6

Contents

Chapter 1Routine Maintenance

Fan Air Filter Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Fan Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000) . . . . . 6-1Fan Module with Integral Fan Tray (Traverse 600) . . . . . . . . . . . . . . . . . 6-1Fan Assembly (TE-100). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Air Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Air Filter Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Air Filter Replacement (Traverse 1600 and Traverse 2000) . . . . . . . . . . . . . . 6-2Fan Tray Air Filter Replacement (Traverse 600). . . . . . . . . . . . . . . . . . . . . . . 6-4Air Filter Replacement (TE-100) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5PDAP Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6PDAP-15A GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6PDAP-2S Circuit Breaker Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7PDAP-2S GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8PDAP-2S LED Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10PDAP-4S TPA Fuse Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13PDAP-4S GMT Fuse Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15PDAP-4S LED Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16Environmental Alarm Module Replacement (Traverse only). . . . . . . . . . . . . . 6-17Non-Field Replaceable Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Chapter 2Node Database Backup and Restore

Backing Up Traverse Node Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Guidelines for Traverse Node Database Backups . . . . . . . . . . . . . . . . . . . . . 6-20Traverse Node Database Restore Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . 6-20

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21Backup and Restore CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

exec node database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21Syntax Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21exec node database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21Syntax Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22

Troubleshooting Traverse Node Backup and Restore . . . . . . . . . . . . . . . . . . 6-22TE-206 Node Database Backup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22

Operations and Maintenance Guide, Section 6 Routine Maintenance


TE-206 Node Backups from the TransNav GUI . . . . . . . . . . . . . . . . . . . . . . . 6-23


SECTION 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-9• Environmental Alarm Module Replacement (Traverse only), page 6-20

Fan Air Filter Maintenance

The fan maintenance topics are as follows:• Fan Assemblies, page 6-1• Air Filters, page 6-2• Air Filter Replacement, page 6-2

Fan Assemblies

Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000)

The Traverse 1600 and Traverse 2000 fan assembly (fan tray with integrated air ramp and fan module) cools the control modules and service modules in the shelf. The Traverse 1600 fan assembly has 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.

Operations and Maintenance Guide, Section 6: Routine MaintenanceAir Filters


Air Filters The air filters on the Traverse and TE-100 systems play a very important role in the cooling function of the modules.

There are environmental factors that could decrease the amount of time required between air filter replacements. Check these environmental factors regularly. Any unusual environmental circumstance at the site that causes an increase in temperature and/or particulate matter in the air might affect performance (for example, new equipment installation).

Air Filter Replacement

The fan air filter replacement topics are as follows:• Air Filter Replacement (Traverse 1600 and Traverse 2000), page 6-2• Fan Tray Air Filter Replacement (Traverse 600), page 6-6• Air Filter Replacement (TE-100), page 6-8

Air Filter Replacement (Traverse 1600 and Traverse 2000)

When the front inlet fan tray air filter (for either Traverse 1600 or Traverse 2000) has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter.

Required Equipment: New front inlet fan tray air filter.

Important: Fan tray air filters should be checked at six-month intervals and replaced as necessary.

Important: Regularly monitor the speeds of the cooling fans in order to accurately determine air filter replacement intervals. An increase in overall fan speed may indicate a clogged filter.

Chapter 1 Routine MaintenanceAir Filter Replacement (Traverse 1600 and Traverse 2000)


Table 6-1 Install a Fan Tray Air Filter with Springs (Legacy)

Step Procedure

1 If you are replacing an old air filter, carefully remove the old air filter from the fan tray holder to avoid contaminating the equipment.

2 Insert the new air filter. Rotate the air filter pull-tabs out.

Figure 6-1 Air Filter with Springs

3 Hold the air filter with the metal window-pane side down and the springs to the back.

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

5 With the springs fully compressed, lift the front edge of the air filter up and over the retaining flanges and release it.

6 Rotate the pull-tabs so they are parallel to the front edge of the air filter.

OPS 00058

Springs

Pull Tabs

Operations and Maintenance Guide, Section 6: Routine MaintenanceInstall a Fan Tray Air Filter with Handle (Legacy)


Install a Fan Tray Air Filter with Handle (Legacy)

The following procedure provides steps on how to install the fan tray filter with a handle on the front edge.

7 Lift the fan tray holder front cover into its closed position. Tighten the captive fasteners to secure it.

Figure 6-2 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.

8 The Install a Fan Tray Air Filter with Springs (Legacy) procedure is complete.

Table 6-1 Install a Fan Tray Air Filter with Springs (Legacy) (continued)

Step Procedure

OPS 00059

Captive Fasteners

Table 6-2 Install a Fan Tray Air Filter with Handle (Legacy)

Step Procedure

1 If you are replacing an old air filter, carefully remove the old air filter from the fan tray holder to avoid contaminationg the equipment.

2 Hold the air filter with the metal window-pane side down with the handle facing to the front.

Figure 6-3 Air Filter with Handle

OPS 00060

Handle

Chapter 1 Routine MaintenanceInstall a Fan Tray Air Filter with Handle (Legacy)


3 Insert the air filter in the gap between the fan tray card and the top of the fan tray holder.

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



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.

6 The Install a Fan Tray Air Filter with Handle (Legacy) procedure is complete.

Table 6-2 Install a Fan Tray Air Filter with Handle (Legacy) (continued)

Step Procedure

OPS 00059

Captive Fasteners

Operations and Maintenance Guide, Section 6: Routine MaintenanceFan Tray Air Filter Replacement (Traverse 600)


Fan Tray Air Filter Replacement (Traverse 600)

When the Traverse 600 fan air filter has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter.

Required Equipment: New air filter

Table 6-3 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.

Figure 6-5 Fan Assembly Front Cover - Traverse 600

2 Open the right-front fan assembly cover.

OPS 00089

Captive Fasteners

Chapter 1 Routine MaintenanceFan Tray Air Filter Replacement (Traverse 600)


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.

Figure 6-6 Traverse 600 Fan Assembly Installation

4 The Fan Tray Air Filter Replacement (Traverse 600)Insert a Traverse 600 Fan Assembly procedure is complete.

Table 6-3 Insert a Traverse 600 Fan Assembly (continued)

Step Procedure

OPS 00090

Traverse 600 Shelf

Fan Assembly

Operations and Maintenance Guide, Section 6: Routine MaintenanceAir Filter Replacement (TE-100)


Air Filter Replacement (TE-100)

When the TE-100 fan air filter has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter.

Required Equipment: New air filter

The fan assembly is in a vertical slot on the left front of the shelf. It draws ambient air through the perforation on the left wall and forces the air over the system and interface modules in the horizontal slots.

The fan assembly must be removed before the air filter can be replaced because the metal air filter attaches to the side of the fan assembly.

The following procedure provides step-by-step instructions on how to replace the TE-100 air filter.

Table 6-4 Replace the Fan Air Filter (TE-100)

Step Procedure

1 Loosen the captive fastener that holds the fan assembly in place.

2 Slide the fan assembly out of the fan cage.

Figure 6-7 Fan Cage and Assembly

3 Carefully remove the old air filter from the fan assembly to avoid contaminating the equipment.

Figure 6-8 Removing the Air Filter

4 Make sure the new air filter is clean and free of dust particles.

Captive Fastener

Fan Cage

Pull up on the air filter

Chapter 1 Routine MaintenancePDAP-15A GMT Fuse Replacement


PDAP Maintenance

The Power Distribution and Alarm Panel (PDAP) maintenance topics are as follows:• PDAP-15A GMT Fuse Replacement, page 6-9• PDAP-2S Circuit Breaker Replacement, page 6-10• PDAP-2S GMT Fuse Replacement, page 6-11• PDAP-2S LED Module Replacement, page 6-13• PDAP-4S TPA Fuse Replacement, page 6-16• PDAP-4S GMT Fuse Replacement, page 6-18• PDAP-4S LED Module Replacement, page 6-19

PDAP-15A GMT Fuse Replacement

The PDAP-15A provides GMT fuses (from 0.25 amps to 15 amps per fuse) for up to ten pieces of auxiliary equipment. The PDAP’s field replaceable fuses are accessible without having to remove the front panel.

Use the following procedure to replace a failed GMT fuse.

5 Slide the air filter into place, lining up the small tabs with the small holes on the fan assembly.

Figure 6-9 Attaching the Air Filter

6 Slide the fan assembly back into the fan cage.

Important: Do not force the fan assembly into position. If it does not plug in easily, slide it back out and check for any obstructions that might prevent it from sliding into position.

7 Tighten the captive fastener to secure the fan assembly in place.

8 The Replace the Fan Air Filter (TE-100) procedure is complete.

Table 6-4 Replace the Fan Air Filter (TE-100) (continued)

Step Procedure

Tabs Lined up with Holes

WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits.

Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-2S Circuit Breaker Replacement


PDAP-2S Circuit Breaker Replacement

The Power Distribution and Alarm Panel (PDAP-2S) contains field replaceable 40 ampere (amp) circuit breakers.1 Each pair of A and B circuit breakers (e.g., A1, B1) provides redundant circuit protection per shelf. Power will not be lost to the shelf if a circuit breaker fails.

Use the following procedure to replace a failed circuit breaker.

Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-15A). Plug the ESD wrist strap into an ESD jack or other confirmed source of earth ground.

Table 6-5 Replacing PDAP-15A GMT Fuses

Step Procedure

1 Remove the GMT fuse by pulling it straight out.1

Figure 6-10 PDAP-15A Front View

1 The GMT fuses protrude from the PDAP-15A front panel to allow access for fuse removal and insertion without having to remove the front panel.

2 Replace the failed GMT fuse with a new one of equal current rating.

3 The Replacing PDAP-2S GMT Fuses procedure is complete.

GMT Fuses

Alarm LEDs

1 Optional PDAP-2S circuit breakers are available up to a 50 amp maximum.


Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-2S). Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground.

Chapter 1 Routine MaintenancePDAP-2S GMT Fuse Replacement


PDAP-2S GMT Fuse Replacement

The PDAP-2S contains two fuse blocks (A and B) of ten field replaceable GMT fuses. Each block has a 100 amp maximum load. Each pair of A and B GMT fuses (e.g., A1, B1) provides redundant power (from 0.25 to 10 amps per fuse) to one of up to ten pieces of auxiliary equipment.


Table 6-6 Replacing PDAP-2S Circuit Breakers

Step Procedure

1 If the toggle switch on the failed circuit breaker is in the On position, switch it off.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.



Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-2S GMT Fuse Replacement


Table 6-7 Replacing PDAP-2S GMT Fuses

Step Procedure


Figure 6-11 PDAP-2S GMT Fuses



1 The GMT fuses protrude from the PDAP-2S front panel to allow access for fuse removal and insertion without having to remove the front panel.

Chapter 1 Routine MaintenancePDAP-2S LED Module Replacement


PDAP-2S LED Module Replacement

The Power Distribution and Alarm Panel (PDAP-2S) system alarm LEDs (Critical, Major, Minor), power input A and B LEDs, and GMT A and B fuse block failure LEDs are on one field replaceable module.

Use the following procedure to replace the PDAP-2S LED module.

Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the PDAP-2S. Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground.

Table 6-8 Replacing PDAP-2S LED Module

Step Procedure

1 Loosen the two captive fasteners on the PDAP-2S front cover to release it.

Figure 6-12 PDAP-2S Assembly - Remove Front Cover

2 Remove the front cover.

Captive Fasteners

Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-2S LED Module Replacement


3 Locate the nonfunctional module with a white pull tab at the center of the PDAP-2S.

Figure 6-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 Replace the front cover.

Table 6-8 Replacing PDAP-2S LED Module (continued)

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.

Table 6-8 Replacing PDAP-2S LED Module (continued)

Step Procedure

Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-4S TPA Fuse Replacement


PDAP-4S TPA Fuse Replacement

The Power Distribution and Alarm Panel (PDAP-4S) contains field replaceable 40 amp TPA fuses.2 Each pair of A and B TPA fuses (e.g., A1, B1) provides redundant protection per shelf. Power will not be lost to the shelf if a TPA fuse fails.

Use the following procedure to replace a failed TPA fuse.

2 Optional PDAP-4S TPA fuses are available up to a 50 amp maximum.



Chapter 1 Routine MaintenancePDAP-4S TPA Fuse Replacement


Table 6-9 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

3 Replace the failed TPA fuse with a new one of equal current rating (Force10 recommends using 40 amp fuses).

4 Insert the TPA fuse holder by pushing it straight in.

5 The Replacing PDAP-4S TPA Fuses procedure is complete.

1 The TPA fuses protrude from the PDAP-4S front panel to allow access for fuse removal and insertion without having to remove the front panel.

Operations and Maintenance Guide, Section 6: Routine MaintenancePDAP-4S GMT Fuse Replacement


PDAP-4S GMT Fuse Replacement

The PDAP-4S contains two fuse blocks (A and B) of five field replaceable GMT fuses. Each block has a 65 amp maximum load. Each pair of A and B GMT fuses (e.g., A1, B1) provides redundant power (from 0.25 to 15 amps per fuse) to one of up to five pieces of auxiliary equipment.




Table 6-10 Replacing PDAP-4S GMT Fuses

Step Procedure


Figure 6-17 PDAP-4S GMT Fuses

1 The GMT fuses protrude from the PDAP-4S front panel to allow access for fuse removal and insertion without having to remove the front panel.





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-11 Replacing PDAP-4S LED Module

Step Procedure

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

4 Tighten the two captive fasteners on the faceplate to secure it.

5 The Replacing PDAP-4S LED Module procedure is complete.

Operations and Maintenance Guide, Section 6: Routine MaintenanceEnvironmental Alarm Module Replacement (Traverse only)


Environmental Alarm Module Replacement (Traverse only)

The Environmental Alarm Module (EAM) located on the Traverse main back plane supports the environmental telemetry inputs and outputs. The EAM is an optional, field replaceable module required to support environmental alarm input/output functionality. Environmental signals are accessed through wire-wrap posts located on the main backplane, allowing the EAM to be replaced without disconnecting alarm wiring.

Use the following procedure to replace the EAM on the Traverse backplane.

Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working with the EAM and the main backplane. Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground.

Table 6-12 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 Prepare to insert the new EAM by holding the module upright along the long edges with the pins facing toward the main backplane.

Chapter 1 Routine MaintenanceNon-Field Replaceable Fuses


Non-Field Replaceable Fuses

The following components in the Traverse system contain non-field replaceable fuses:• Control module• Service interface module• Fan tray

If a Traverse module requires (non-field replaceable) fuse replacement, call the Force10 Technical Assistance Center. If the fan tray requires fuse replacement, it will need to be replaced with a new fan tray unit.

3 Insert the module into the main backplane EAM connector using the plastic standoff and proper alignment guides. The plastic standoff tab clicks into place when the module is properly seated.

Important: The module should insert easily into the main backplane connector. Do not force it into position. If the module does not insert easily, pull it back out and verify you are placing it in the correct position and inserting it along the plastic standoff and proper alignment guides.

Figure 6-20 EAM Alignment

4 The Replacing EAM procedure is complete.

Table 6-12 Replacing EAM (continued)

Step Procedure

Long edge

Pins facing Proper Alignment Guide

Plastic Standoff Guide

Main Backplane

Operations and Maintenance Guide, Section 6: Routine MaintenanceNon-Field Replaceable Fuses



SECTION 6ROUTINE MAINTENANCE

Chapter 2 Node Database Backup and Restore

Introduction This chapter provides information on backing up and restoring the node databases for Traverse nodes and TE-206 nodes that are managed by the TransNav GUI. For Traverse nodes, the backups and restoration can be done using either the TransNav GUI or CLI commands. For TE-206 nodes, backups and restorations can be done using the TransNav GUI. For information on backing up TE-206 node databases from the node, see the TraverseEdge 206 Users Guide.

For backing up Traverse node databases, the following sections are included in this chapter:• Backing Up Traverse Node Databases• Guidelines for Traverse Node Database Backups• Traverse Node Database Restore Guidelines• Backup and Restore CLI Commands• Troubleshooting Traverse Node Backup and Restore

For backing up TE-206 node databases, the following sections are included in this chapter:• TE-206 Node Database Backup Overview• TE-206 Node Backups from the TransNav GUI

Backing Up Traverse Node Databases

Traverse node databases can be backed up in one of two methods: to an FTP server or to the GCM card. Node-level CLI commands are used for the backup and restore procedures for Traverse nodes.

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

Operations and Maintenance Guide, Section 6: Routine MaintenanceGuidelines for Traverse Node Database Backups


Guidelines for Traverse Node Database Backups

If the Traverse node has minimal services, the backup will take one or two minutes. 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.– 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.

Force10 recommends backing up the node database during a maintenance period, especially if optical cards exist on the shelf.

Traverse Node Database Restore Guidelines

For Traverse nodes, the restoration process takes 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 Traverse node 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.

Note: Node databases can only be restored to the same node from which they were backed up.Command descriptions use the following conventions:

Table 6-13 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.

Chapter 2 Node Database Backup and RestoreBackup and Restore CLI Commands


Backup and Restore CLI Commands

Use the following CLI commands to backup and restore the Traverse node database.

exec node database backup. Use the exec node database backup command to back up the Traverse node database.

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.

Boldface Boldface indicates literal commands and keywords that are entered exactly as shown.

Note: You can abbreviate literal commands. See the Section 1—Overview and Quick Reference, Chapter 1—“CLI Overview,” Using Shortcuts, page 1-12.

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.

Table 6-13 CLI Command Conventions

Command Description

Operations and Maintenance Guide, Section 6: Routine MaintenanceTroubleshooting Traverse Node Backup and Restore


Syntax

exec node database restore [host ip address user-name UserName password password [path blank][filename nodeDB.xxx]]

Syntax Description

ip address - IP address of the FTP server where the database is backed up

user-name - username to use when accessing the FTP server

password - password to use when accessing the FTP server

path - enter the path on the FTP site from where the database will be restored

filename - enter the file name of the database file

Troubleshoot-ing Traverse Node Backup and Restore

If problems occur when restoring a Traverse node backup, it may be due to one of the following reasons:

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.

TE-206 Node Database Backup Overview

From the TransNav server, backups of TE-206 node databases can be performed from the Admin menu by selecting the Node Backup Scheduler option. Backups can be scheduled either for a regular automatic backup without operator intervention, or manually with explicit operator action. Regularly scheduled backups are unprotected by default. Only the last three unprotected backups are retained. The rest are

Chapter 2 Node Database Backup and RestoreTE-206 Node Backups from the TransNav GUI


automatically deleted when the next scheduled backup occurs. Manually created backup database files are protected by default and must be removed manually.

At minimum, TransNav stores three backup copies of the TE-206 node database in the \\ems_(release)\nodedb directory on the management system server. Each stored copy identifies the node ID, date, and time that the backup file was created.

Important: Manually deleting the files in the \\ems_(release)\nodedb directory prevents the TE-206 node database from being accessible from TransNav.

To ensure the latest TE-206 node configuration is exported, manually backup the TE-206 database prior to exporting the EMS.

Backed up TE-206 node databases are restored upon a manual request. When the TransNav database is exported or imported, TE-206 node databases are included.

Note: For specific steps to back up the TE-206 node databases from TransNav, see TE-206 Node Backups from the TransNav GUI, page 6-27.

TE-206 Node Backups from the TransNav GUI

Perform TE-206 node database backups from the TransNav GUI using the Admin menu, Node Backup Scheduler option. The Node Backup Scheduler can be set to backup the databases of a group of nodes or to backup the database of all TE-206 nodes in the network.

If multiple servers exist in the network, the database backup scheduler runs only on the primary server.

Note: For Release TN4.2.1, this menu option is available only to back up TE-206 node databases. Traverse node databases must be backed up using CLI commands as described in Backup and Restore CLI Commands.

Operations and Maintenance Guide, Section 6: Routine MaintenanceTE-206 Node Backups from the TransNav GUI


Figure 6-21 Initial Node Backup Scheduler Dialog Box

To create manual backup or to schedule an automatic backup, select Action, Create. The Create Backup Scheduler dialog box displays.

Figure 6-22 Create Backup Scheduler Dialog Box

Name: Enter a name to identify the backup being created.



Backup Period: Indicate the length of time before the next backup. Valid values are: 1 hour, 3 hours, 6 hours, 12 hours, 1day, 2 days, 3 days, 4 days, 5 days, 6 days, 1 week (default), 2 weeks, 3 weeks, 4 weeks.

Next Backup Time: Select the time for the backup to occur. For automatically scheduled backups, the default backup time will correspond to the current time PLUS the selected backup period.

Description: Enter a description of the backup.

Enabled: Select this checkbox to activate the backup schedule.

Node Membership Configuration: Select the TE-206 node(s) to be included in the group of nodes to have database information backed up for the period being created. Use the Add and Remove buttons to move the name of the selected TE-206 node(s) from the Candidate Nodes pane to the Member Nodes pane.

Click OK to create the backup schedule. A confirmation message displays.

To change any options in the backup schedule, select Action, Edit. To delete the backup schedule, select Action, Delete. To run the scheduled backup manually, select Action, Run Schedule.

After the backup schedule has been set, the schedule information displays on the Node Backup Schedule dialog box in the Schedule Specifications screen. Right-click on any column to display a shortcut menu allowing you to create, edit, delete or run the selected backup schedule.

To view the node names of TE-206 nodes included in the selected backup schedule, click the Node Count column. The node names included in the specified schedule display in the Schedule Specification Members screen in the lower half of the dialog box. The system-assigned schedule member ID, node name, last successful backup date, last backup attempted date, and last backup attempt status for each node display.



Figure 6-23 Node Backup Scheduler Dialog Box, Scheduled Backup

Once created, TE-206 node backups can be managed from the TransNav map view. From the map view, select the TE-206 node, right-click and select Manage Node Backups from the shortcut menu. The Manage Node Backups dialog box displays.

Figure 6-24 Manage Node Backups Dialog Box

ID: Indicates the system-generated identifier of the scheduled backup.

Database Version: Indicates the unique identifier of the backup file from the nodedb directory.

Software Version: Indicates the software version of the backup file.

Protected: A checkbox. If selected, indicates if the backup is protected from deletion by the automatic database backup schedule. Manually-initiated backups are always marked as protected. To change the value in the checkbox, right-click the cell and select Protect or Unprotect.



Backup Time: Identifies the date and time the backup was performed.

Backup Size: Indicates the size of the backup file.

Description: Indicates if the backup was scheduled or manually generated.

Each stored copy identifies the node ID, date, and time that the backup file was created.




SECTION 7 SOFTWARE UPGRADESSECTION 7

Contents

Chapter 1Release TR3.2.2 Traverse Software Upgrade

Release TR3.2.2 Upgrade Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Node Software Upgrade Flowchart (Top Level) . . . . . . . . . . . . . . . . . . . . . . . 7-2Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Traverse Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

TransNav Management System GUI Commands and Conventions . . . . . . . . 7-4Compatibility and Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4General Software Compatibility Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Traverse System SW Upgrade Compatibility Notes . . . . . . . . . . . . . . . . . . . . 7-5

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Software Upgrade for TR3.2.x Maintenance Releases . . . . . . . . . . . . . . 7-5Software Upgrade from Release TR2.1.x or TR3.0.x to TR3.2.x . . . . . . 7-6

Guidelines for Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-8Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-8Module Software Download Set-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Card Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15BLSR/MS-SP Ring on GCM with Optics Software Activation . . . . . . . . . . . . . 7-18Control Module Software Upgrade Activation . . . . . . . . . . . . . . . . . . . . . . . . . 7-22Software Upgrade Activate (all other protected modules). . . . . . . . . . . . . . . . 7-27Software Upgrade Activate (all unprotected modules) . . . . . . . . . . . . . . . . . . 7-30Spare Control Module Software Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32Spare Module Software Activation (All Other Types) . . . . . . . . . . . . . . . . . . . 7-33Verify Protection Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34Perform a Forced Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35Perform a Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36Clear Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38Software Revert Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40

Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Revert TransNav Management System Software . . . . . . . . . . . . . . . . . . 7-41

Post-Remote Node— Upgrade the Spare Control Module Software . . . . . . . 7-41

Operations and Maintenance Guide, Section 7 Software Upgrades


User- selectable FPGA Upgrade Capability . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43Overview to Upgrade TE-206 Nodes from TransNav . . . . . . . . . . . . . . . . . . . 7-44Requirements for Upgrading TE-206 Node Software . . . . . . . . . . . . . . . . . . . 7-46Downloading TE-206 Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46Upgrading TE-206 Node Software from TransNav . . . . . . . . . . . . . . . . . . . . . 7-48

Chapter 2Release TE3.2.x TE-100 System Software Upgrade

Release TE3.2.x Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52Required Equipment and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52

Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52TE-100 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52

TransNav Management System GUI Commands and Conventions . . . . . . . . 7-53Compatibility and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53General Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53TE-100 Platform SW Upgrade Compatibility Notes . . . . . . . . . . . . . . . . . . . . . 7-54Guidelines for Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Node Software Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-55Download Node Software to the TransNav Server . . . . . . . . . . . . . . . . . . . . . 7-55Module Software Download Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57Card Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62Software Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62Activate Software - Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64Spare Control Module Software Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68Software Revert Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69

Revert Node Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69Revert TransNav Management System Software . . . . . . . . . . . . . . . . . . 7-70


SECTION 7SOFTWARE UPGRADES

Chapter 1 Release TR3.2.3 Traverse Software Upgrade

Introduction This chapter provides the following information including steps on how to initiate and complete software upgrades to Traverse nodes in your network using the TransNav GUI.

Complete the TR3.2.3 software upgrade of all cards in a Traverse node using the release TN4.2.3 TransNav management system graphical user interface (GUI).• Release TR3.2.3 Upgrade Overview, page 7-1• Node Software Upgrade Flowchart (Top Level), page 7-3• Before You Begin, page 7-4• Required Equipment and Tools, page 7-4• TransNav Management System GUI Commands and Conventions, page 7-5• Compatibility and Guidelines, page 7-5• Traverse Node Software Upgrade Process, page 7-8• Software Revert Procedure, page 7-42• Post-Remote Node— Upgrade the Spare Control Card Software, page 7-43• User- selectable FPGA Upgrade Capability, page 7-45

To upgrade software to TE-206 nodes using the TransNav GUI, see the following information:• Overview to Upgrade TE-206 Nodes from TransNav, page 7-46• Requirements for Upgrading TE-206 Node Software, page 7-48• Downloading TE-206 Node Software, page 7-48• Upgrading TE-206 Node Software from TransNav, page 7-50

Release TR3.2.3 Upgrade Overview

Release TR3.2.3 provides a unified release for the Traverse and TransNav products supporting SONET networks and services.

This software release supports:• Traverse in-service software upgrade to TR3.2.3 from the following previous

releases: TR3.0.0.7, TR3.2.1 and TR3.2.2 • Point releases (as necessary) for the TR3.2.3 Traverse nodes. • Upgrades of TE-206 nodes from the TransNav system. • Remote upgrade capability.

Operations and Maintenance Guide, Section 7: Software UpgradesRelease TR3.2.3 Upgrade Overview


• User-selectable Field Programmable Gate Array (FPGA) upgrade capability.• Simultaneous TransNav Management System (TN4.2.3) software management of

the following associated releases:– Traverse Releases TR3.0.0.7, TR3.2.1, TR3.2.2, and TR3.2.3– TE-100 nodes on Release TE3.0.x, TE3.2.2, or TE3.2.3– TE-206 nodes on Release R04.06.x

Note: If your systems are on an earlier release, contact your Sales representative.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeNode Software Upgrade Flowchart (Top Level)


Node Software Upgrade Flowchart (Top Level)

The diagram below shows a top-level flow for the node software upgrade process.

Figure 7-1 Node Software Upgrade Process Flowchart

OPS 00071

Node Software UpgradeTop-Level Flowchart

Begin

Read release nodes, upgrade

compatibility notes, guidelines, and all upgrade

procedures

Operations Manager creates a

comprehensive upgrade plan

Point release upgrade?

Go to Page 2

YES

NO

Is this a major release

upgrade?

YES

NO

Is your software on an earlier

release not listed for upgrade?

YES

Contact your Sales

representative

End

Operations Manager

Upgrade Team

Follow the Node

Upgrade Process

Read and understand the release notes, upgrade

compatibility notes , guidelines, upgrade

procedures, and your company's comprehensive

upgrade plan

IMPORTANT! For details, refer to the specific software upgrade procedures in the manual or contact the Technical Assistance Center .

Operations and Maintenance Guide, Section 7: Software UpgradesBefore You Begin


Before You Begin

Review these requirements before you begin.

Required Equipment and Tools

The following equipment and tools are required for a Traverse system software upgrade to a node or multiple nodes in a domain:• TransNav management system server connected to a gateway Traverse node• Access to the Force10 corporate website at www.force10networks.com

Note: Use this procedure to install the management server software from the Force10 Networks corporate website. A Customer Portal Account is required. If you do not have a Customer Portal Account, you can request one from the Force10 website at www.force10networks.com by selecting Services & Support, then Account Request.

The following hardware equipment and tools are required to place cards in a Traverse shelf.

General

• Electrostatic Discharge (ESD) wrist strap• Eye protection• 1-slot wide blank faceplates for any empty slots to ensure EMI protection and

proper cooling. Blank faceplates must be ordered separately.

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)

Table 7-1 Traverse Node Software Upgrade Requirements

Requirement Reference

Compose and have ready for the Upgrade Team a comprehensive network upgrade plan.

Your company’s Operations Manager is responsible for this task.

Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company’s comprehensive upgrade plan.

• See Release Notes TR3.2.3 and TN4.2.3.• Read through this entire chapter• If you have TE-206 nodes in your network, read the

TraverseEdge 206 Users Guide, Chapter 18, Maintenance.• Contact your company’s Operations Manager.

The software upgrade feature for this release supports Traverse TR3.0.0.7, TR3.2.1 or TR3.2.2 to TR3.2.3 and TransNav TN4.1.3, TN4.2.1 or TN4.2.2 to TN4.2.3 upgrades.

If you are upgrading from an earlier Traverse or TransNav software release, contact the Force10 Technical Assistance Center.

Have the required equipment and tools ready.

Required Equipment and Tools, page 7-4

www.turinnetworks.com




Chapter 1 Release TR3.2.3 Traverse Software UpgradeGeneral Software Compatibility Notes


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

Compatibility and Guidelines

Read the compatibility topics that are relevant to your specific upgrade.• General Software Compatibility Notes, page 7-5• Traverse System SW Upgrade Compatibility Notes, page 7-6• 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. You activate the new software 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 before 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):• Position 1 shows the major software release number.• Position 2 shows the minor software release number.• Position 3 shows the release build number.• Position 4 shows 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.

Table 7-2 TransNav GUI Command Descriptions

Command Description

Boldface Boldface indicates dialog boxes, fields, menus, and list names.

Italics Italics indicate information that you supply.

Operations and Maintenance Guide, Section 7: Software UpgradesTraverse 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.2.3 TransNav management system software:– simultaneously manages Release TR3.2.1, TR3.2.2 and TR3.2.3 Traverse

nodes.– manages the in-service software upgrade from Release TR3.0.0.7, TR3.2.1or

TR3.2.2 to TR3.2.3, as well as, any TR3.2.x maintenance releases.– manages a network of mixed nodes running Release TR3.2.1, TR3.2.2, and

TR3.2.3 for functions including:• Service management (provisioning, activation, deactivation, deletion, etc.)• Alarms and performance monitoring (on-demand and periodic)• Node and card addition and deletion• Loopback• External commands on protection groups

– manages a network of mixed nodes running TraverseEdge 100 (TE-100) Release TE3.0.x, TE3.2.2, or TE3.2.3.

– manages a network of mixed nodes running TraverseEdge 206 (TE-206) Release R04.06.0x

• The remote upgrade capability manages the arrival of older version cards and allows for remote download and activation of such cards to the TR3.2.3 release.

• Line-derived timing cards (e.g., OC-3/STM-1) support only one timing reference. 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 cards). Upon in-service replacement, the Traverse system raises and alarm and uses the timing reference of the lowest-numbered port on the card that was previously provisioned with multiple timing references, and ignores the timing provisioning for the higher-numbered ports.

• The Traverse system allows in-service replacement and upgrade of a UTMX-24 card with a UTMX-48 card, but not vice versa.

Software Upgrade for TR3.2.3 Release

• Hitless software upgrade and warm restart are available, unless otherwise noted in the specific maintenance software Release Notes.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeGuidelines for Software Upgrade


• In-service, hitless software upgrade support is available.

Software Upgrade from Traverse Release TR3.0.0.7 and TR3.2.x to TR3.2.3

• Support for in-service Traverse node software upgrades from Release TR3.0.0.7, TR3.2.1, or TR3.2.2 to TR3.2.3 for all network topologies: UPSR, BLSR, linear 1+1 chain, mesh, or combinations of these topologies.

Guidelines for Software Upgrade

Review the following guidelines for software upgrades:• 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.

• 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 downloads to the control cards (i.e., Traverse GCM) at least 5 minutes apart.

• Perform an upgrade on spare cards, 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 Card Software, page 7-43 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 for TR3.2.3 define any potential

exceptions. This document resides on the Force10 website at www.force10networks.com on the Customer Support website. A Customer Portal Account is required. If you do not have a Customer Portal Account, you can request one from the Force10 website at www.force10networks.com by selecting Services & Support, then Account Request.




Operations and Maintenance Guide, Section 7: Software UpgradesTraverse Node Software Upgrade Process


Traverse Node Software Upgrade Process

Traverse and TransNav support in-service software upgrades from Release TR3.0.0.7, TR3.2.1, or TR3.2.2 to TR3.2.3. Depending on your requirements and current software load, you can choose either a hitless (warm restart) or a service-affecting (cold reboot) upgrade.

Note: If you have one or more nodes in your system with a node name that begins with a number, call the Force10 Technical Assistance Center before upgrading

Note: If you have TE-206 nodes that are managed by TransNav, see the TraverseEdge 206 Users Guide, Chapter 18, Maintenance, for upgrade instructions.

Complete the software upgrade procedures in the following order:

You must first download the software for the upgrade from the Force10 Networks corporate website 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.

Download the TransNav Management System or Traverse node software from the Force10 Networks corporate website (www.force10networks.com). From Services &

Table 7-3 Traverse Node Software Upgrade Process

Step Procedure Reference

1 Have you read through, and do you understand, all the Before You Begin items?

Before You Begin, page 7-4

2 Do you have the required equipment and tools ready?


3 Upgrade the Traverse software (includes first exporting the current database off the TransNav server).

Note: Do not uninstall the previous version. Mark the directory as “-old” and remove the Icon from the desktop.

Note: NETSYNC alarms occur when you start the GUI, after the server software upgrade, and before upgrading the node software. The master network objects (e.g., alarm profiles) are out of synchronization with propagated node objects.

TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Upgrade Server Software, page 2-48

4 Download the new Traverse node software to the TransNav server.

Download Node Software to the TransNav Server, page 7-9

5 Download the software to the cards. Module Software Download Set-up, page 7-11

6 Activate the new software. Software Activation Process, page 7-17

7 The Traverse Node Software Upgrade Process is complete.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeDownload Traverse Node Software to the TransNav Server


Support, select Customer Login. Enter your Force10 User ID and Password, then click Login.

Download Traverse Node Software to the TransNav Server

Use these steps to download the Traverse node software to the TransNav server.

Table 7-4 Download Traverse Node Software to the TransNav Server

Step Procedure

1 Navigate to the directory where the Traverse node software files were previously downloaded from the Force10 Networks website.

Figure 7-2 Example—PC System Explorer Window File Listing

2 Right-click the flash.n.n.n.n.zip file (where n.n.n.n is the latest software release number). For Windows PC systems, select the WinZip > Extract to command. For Solaris systems, use the gunzip command.

Operations and Maintenance Guide, Section 7: Software UpgradesDownload Traverse Node Software to the TransNav Server


3 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-3 Extract Dialog Box

4 The Download Traverse Node Software to the TransNav Server procedure is complete. Continue to Step 5 of the Traverse Node Software Upgrade Process, page 7-8.


Step Procedure

Chapter 1 Release TR3.2.3 Traverse Software UpgradeCard Software Download Set-up


Card Software Download Set-up

Software upgrades are done at the node level. The following procedure provides steps on how to begin a software upgrade by setting software download times for each card using the SW Upgrade dialog box.

Important: Due to repartitioning of the FLASH chip, GCM upgrades to Release TR3.2.3 will take approximately 8 to 0 minutes per GCM to upgrade instead of the 2 to 3 minutes necessary on to upgrade on earlier releases. Additionally, the Power LED on the GCM cards will blink red/green while the Active Standby light remains dark. Additionally, the Major/Critical and Minor LEDs may blink or may remain dark. THIS IS EXPECTED BEHAVIOR FOR UPGRADES TO THIS RELEASE.

Table 7-5 Card Software Download Set-up

Step Procedure

1 Verify the card software versions. Refer to Card Software Version Verification, page 7-17.

2 In Shelf View, select SW Upgrade from the Admin menu to display the SW Upgrade dialog box.

Figure 7-4 SW Upgrade Dialog Box

3 Server IP Address: Enter the TransNav server IP address where the new node software version was downloaded.

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

Operations and Maintenance Guide, Section 7: Software UpgradesCard Software Download Set-up


5 Username: Enter the user name with File Transfer Protocol (FTP) permission access to the TransNav server where the new node software version resides.

(For example: ftpusername)

6 Password: Enter the user password with FTP permission access to the TransNav server where the new node software version resides.

(For example: ftppassword)

7 Click 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 values must be set by the system before the download starts. Default is INIT.

Table 7-5 Card Software Download Set-up (continued)

Step Procedure



8 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: Force10 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: Force10 recommends you download the control cards individually, three line cards at a time and one node at a time.

Figure 7-5 Download Time Settings


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.

Figure 7-6 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 for each card.

Upgrade Type: 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 the Technical Assistance Center.

12 Repeat Steps 7 through 11 for each card in the node.


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

.

Figure 7-7 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 Force10’s Technical Assistance Center if the software download fails a second time.


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.

17 The Card Software Download Set-up procedure is complete.

Depending on the procedure where you started, return to either:• Step 6 of the Node Software Upgrade Flowchart (Top Level),

page 7-3• Step 3 of the Spare Card Software Activation (All Other Types),

page 7-35

Return to Step 6 of the Traverse Node Software Upgrade Process, page 7-8.


Step Procedure

Chapter 1 Release TR3.2.3 Traverse Software UpgradeSoftware Activation Process


Card Software Version Verification

You can determine the software version number of a card using the TransNav GUI. The software version and serial number display in the Config tab in Shelf View. Follow these steps to verify the software version.

Software Activation Process

The new software is not active until the software is activated and system reboots each card. The reboot loads and executes the new software and, in the case of the control card, upgrades the database.

Table 7-6 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.

Figure 7-8 Card Configuration Dialog Box

3 The software version displays 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.

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.

Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Activation Process


Important: The software upgrade activate process is considered service-affecting unless all services are protected. Therefore, Force10 recommends that activation be scheduled/completed one card at a time. This requires you to observe the reboot process and set the activate time for each card after the previous card 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 card.

Important: Any unprotected traffic residing on an Enhanced GCM (EGCM) with Optics card will experience an outage until the EGCM is restored from activation.

Important: During software activation, the card automatically reboot. Do not execute any external commands on the cards 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 card. Once the line cards 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.

Important: If you are performing software activation on an Ethernet card that is using RSTP, selecting the “warm reboot” option may result in service interruption of network-wide Ethernet applications that include Bridge services on that card. Force10 recommends that you deactivate Bridge services on an Ethernet card that is using RSTP before scheduling a software upgrade with a warm reboot of that card.

Table 7-7 Software Activation Process


1 Did you complete the upgrade of TransNav EMS server and client software and download the node software to the TransNav server?


2 Did you download the node software to the TransNav server?

Traverse Node Software Upgrade Process, page 7-8

3 Is the card software download complete?

Card Software Download Set-up, page 7-11

4 Do you have your network nodes in a BLSR/MS-SP Ring network with Traverse Enhanced GCMs with Optics?

• Activate software for all cards set up in a BLSR/MS-SP Ring protection group. See BLSR/MS-SP Ring on GCM with Optics Software Activation, page 7-20

• Continue to Step 6 of this process to software upgrade activate all other protected cards.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeSoftware Activation Process


5 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 cards at a later time (see page 7-43)

Control Card Software Upgrade Activation, page 7-24

6 Activate software for all cards set up in a protection group.

Software Upgrade Activate (All Other Protected Cards), page 7-29

7 Activate software for all unprotected cards.

Software Upgrade Activate (All Unprotected Cards), page 7-32

8 Activate software for all other types of spare cards, unless you are using the remote upgrade capability and want to upgrade your spare cards at a later time.

Spare Card Software Activation (All Other Types), page 7-35

9 The Software Activation Process is complete.

Table 7-7 Software Activation Process (continued)


Operations and Maintenance Guide, Section 7: Software UpgradesBLSR/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 card. The reboot loads and executes the new software, and in the case of the control card, upgrades the database.

The activation is scheduled for each card based on the date and time entered in the Activate Time field of the SW Activation dialog box. Follow these step-by-step instructions to set up software upgrade activation for GCMs with Optics in a BLSR/MS-SP Ring.

Important: The following procedure applies to Traverse nodes only.

Important: Do not start the Activate Software—BLSR/MS-SP Ring GCM with Optic Cards 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 cards.

Table 7-8 Activate Software—BLSR/MS-SP Ring GCM with Optic Cards

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 card and click the Config tab.

3 Verify Active/Standby GCM with Optics Protection Status using the Card Configuration dialog box.

Figure 7-9 Card Configuration GCM Protection Status

4 Execute a BLSR/MS-SP Ring Forced Switch on the standby GCM with Optics card following the procedure in Perform a Forced Switch, page 7-37.

Check the BLSR/MS-SP Ring state and verify that Force is issued on the near- and far-end.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeBLSR/MS-SP Ring on GCM with Optics Software Activation


5 Click the standby GCM with Optics Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter.

Figure 7-10 SW Activation—Activate Time

6 Select the activation type—Act Type (default=NSA). Service Affecting (SA) is required for standby GCM with Optics card 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 card

regardless of its active or standby status. • SPARE (non-service-affecting): Will activate and reboot the spare

(standby) control card. Only use this option in the instance where the standby and active control cards have already been upgraded and activated.

7 Select to warm reboot (Warm Rbt) this card. To learn more about those cards that allow a warm reboot upgrade, see the table Cold Reboot Matrix for Cards on Upgrade from Previous Releases to Release TRx.x.x, in the Release Notes.

8 Select to ignore the FPGA upgrade available on this card. See User- selectable FPGA Upgrade Capability, page 7-45 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, Force10 recommends that (by default) you accept all FPGA upgrades so as not to create an upgrade deviation in your network.

9 Click Update.


Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesBLSR/MS-SP Ring on GCM with Optics Software Activation


10 View the status of the software activation in the Act Status field of the SW Upgrade dialog box. The following status displays:• NONE: Software activation has not begun.• INPROGRESS: Software activation has begun, but is not complete.• OK: Software activation has successfully completed.• FAILED: Software activation has failed. Retry software activation.

Contact Force10 TAC if software activation fails a second time.

Important: The activation status will show INPROGRESS, then NONE until the card 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 column.

Figure 7-11 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 Clear Protection Switch, page 7-40.

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 card following the procedure in Perform a Forced Switch, page 7-37.

Check the BLSR/MS-SP Ring state and verify that Force is issued on the near- and far-end.


Step Procedure

Chapter 1 Release TR3.2.3 Traverse Software UpgradeBLSR/MS-SP Ring on GCM with Optics Software Activation


16 Click the active GCM with Optics card 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 card by right-clicking the card 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 card 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


(standby) control card. Only use this option in the instance where the standby and active control cards have already been upgraded and activated.

18 Select to warm reboot (Warm Rbt) this card. To learn more about those cards that allow a warm reboot upgrade, see the table, Cold Reboot Matrix for Cards on Upgrade from Previous Releases to Release TRx.x.x, in the Release Notes.



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

22 With the now standby (previously active) GCM with Optics card 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.


Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesControl Card Software Upgrade Activation


Control Card Software Upgrade Activation

The new software is not active until the system reboots each card. The reboot activates the backup partition with the newly downloaded software on the control card at each node.

The activation is scheduled for each card 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.

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 cards 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 Clear Protection Switch, page 7-40.

Verify that the BLSR/MS-SP Ring has returned to normal operation.

25 If you have spare GCM with Optic cards to software upgrade at this time (i.e., you are not using the remote upgrade capability), remove the standby GCM with Optics card from the shelf and install the spare GCM with Optics. Complete the Spare Control Card Software Activation, page 7-34 procedure.

26 The Activate Software—BLSR/MS-SP Ring GCM with Optic Cards procedure is complete. Return back to Step 4 of the Software Activation Process, page 7-18.


Step Procedure

Important: Do not start the Activate Software—Control Card 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 cards.

Table 7-9 Activate Software—Control Card

Step Procedure


2 In Shelf View, select a control card and click the Config tab.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeControl Card Software Upgrade Activation


3 Verify the Protection Status of the Active/Standby control card using the Card Configuration dialog box.

Figure 7-12 Card Configuration Protection Status

4 Click the standby control card Activate Time field in the SW Activation dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter.


5 Select the activation type Act Type (default=NSA). Change to SA for standby control card activation.

Valid values are:• NSA (non-service-affecting): Default. Will not activate an active

control card. • SA (service-affecting): Will activate and reboot the control card


(standby) control card. Use this option only when the standby and active control cards have already been upgraded and activated.

6 If the card does not require a cold restart, then select to warm restart (Warm Rbt) this card.

Table 7-9 Activate Software—Control Card (continued)

Step Procedure





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 Force10 TAC if the software activation fails a second time.

Important: The activation status will show INPROGRESS and then NONE until the card 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 Force10 TAC.

.


11 With the standby control card 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.

12 A SWMIS: Software version mismatch alarm is generated since the standby control card software version is now mismatched with the active control card. This is normal behavior.


Step Procedure

Chapter 1 Release TR3.2.3 Traverse Software UpgradeControl Card Software Upgrade Activation


13 If the control cards contain integrated VTX/VCX cards in a protection group (e.g., GCM with VTX/VCX), you must perform a Manual switch on the active card (card with the old software) to change its state to standby. Refer to the procedure, Perform a Manual Switch, on page 7-38 for details.

Note: The manual protection switch on certain cards is necessary due to FPGA changes.

14 After the manual switch is complete, repeat Steps 3 through 12, for the now standby card (card with the old software) of the protection group.

15 Release (clear) the protection switch after activation is complete on the standby card to return it to its original active status. Refer to the Clear Protection Switch procedure on page 7-40 for details.

16 Click the active control card 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 card by right-clicking the card 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 card.




(standby) control card. Use this option only when the standby and active control cards have already been upgraded and activated.

18 Select to warm reboot (Warm Rbt) this card.



20 Click Update.


Step Procedure



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 Force10 TAC if the software activation fails a second time.

Important: The activation status will show INPROGRESS, then NONE until the card 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 card causes the new software to upgrade and a switchover to the protection card.

23 With the now standby (previously active) control card 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 card clears as both control card software versions now match. However, this alarm is now generated for all other cards in the system as their software versions are now mismatched with the active control card. This is normal behavior.

25 If you have spare control cards to software upgrade at this time (i.e., you are not using the Remote Upgrade feature), remove the standby control card from the shelf and install the spare (standby) control card. Complete the Spare Control Card Software Activation, page 7-34 procedure.

26 The Activate Software—Control Card procedure is complete. Continue to Step 6 of the Software Activation Process, page 7-19.


Step Procedure

Chapter 1 Release TR3.2.3 Traverse Software UpgradeSoftware Upgrade Activate (All Other Protected Cards)


Software Upgrade Activate (All Other Protected Cards)

Follow these step-by-step instructions to set up software upgrade activation for all other protected cards.

Important: Upgrade the entire protection group first before continuing to the next protection group.

Table 7-10 Activate Software —All Other Protected Cards

Step Procedure

1 Proceed with software upgrade activation for other protected cards after the software activation has successfully completed on both the control cards (Act Status=OK) and any service-affecting alarms on the node are cleared.

Software upgrade activation on other protected cards must be performed in the following order for all cards set up in a protection group:• Set the Activate Time so the standby card 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 card to change its state to standby.

• Set the Activate Time for the active card.• Release the protection switch.

2 Verify and record the standby/active status for cards/ports set up in a protection group. Refer to the Verify Protection Status procedure on page 7-36 for more details.

3 Click the standby card 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.


Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Upgrade Activate (All Other Protected Cards)


4 Set the activation type Act Type to SA for the card.

Valid types are:

NSA (non-service-affecting): Default. Will not activate a card if it has any active services.

SA (service-affecting): Activates the software and reboots the card regardless of any services.

5 If the card does not require a cold restart, then select to warm restart (Warm Rbt) this card.



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


Table 7-10 Activate Software —All Other Protected Cards (continued)

Step Procedure

8 9

Chapter 1 Release TR3.2.3 Traverse Software UpgradeSoftware Upgrade Activate (All Other Protected Cards)


10 With the standby card 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 card.

11 If the cards contain integrated VTX/VCX cards in a protection group, perform a Manual Switch on the active card (card with the old software) to change its state to standby. Refer to the Perform a Manual Switch procedure on page 7-38 for details.

Note: The manual protection switch on certain cards is necessary due to FPGA changes.

12 After the manual switch is complete, repeat Steps 3 through 10 for the now standby card (card with the old software) of the protection group.

13 Release (clear) the protection switch after activation is complete on the standby card to return it to its original active status. Refer to the Clear Protection Switch procedure on page 7-40 for details.

14 Repeat Steps 2 through 13 for the next protection group.

15 The Activate Software —All Other Protected Cards procedure is complete. Continue to Step 7 of the Software Activation Process, page 7-17.

Table 7-10 Activate Software —All Other Protected Cards (continued)

Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Upgrade Activate (All Unprotected Cards)


Software Upgrade Activate (All Unprotected Cards)

Use the following step-by-step instructions to set up software upgrade activation for all unprotected cards:

Table 7-11 Activate Software —All Unprotected Cards

Step Procedure

1 Proceed with software upgrade activation on all unprotected cards after the software activation has successfully completed (Act Status=OK) on both the control cards and then on all other protected cards before clearing any service-affecting alarms on the node.

2 Click the unprotected card Activate Time field to display the current date and time. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter.


3 Select the activation type Act Type and set to SA for the card.



regardless of its active or standby status.

4 If the card does not require a cold restart, select to warm restart (Warm Rbt) this card.



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 Force10 TAC if software activation fails a second time.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeSoftware Upgrade Activate (All Unprotected Cards)


8 Verify the new software version displays in SW Activation dialog box, Current SW Ver field.


9 With the unprotected card 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 card.

10 Repeat Steps 2 through 9 for all unprotected cards.

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 Cards procedure is complete.

Depending on the procedure from which you came, continue to either:• Step 8 of the Software Activation Process, page 7-19• Step 4 of the Spare Card Software Activation (All Other Types),

page 7-35

Table 7-11 Activate Software —All Unprotected Cards (continued)

Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesSpare Control Card Software Activation


Spare Control Card Software Activation

The new software is not active until the system activates the software and reboots the spare (standby) control card. The reboot loads and executes the new software.

The activation is scheduled for each card 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 cards.

Important: This procedure assumes you have completed upgrading (downloading and activating the new software for) the standby and active control cards.

Important: A spare control card can only be upgraded in a shelf that has the same type of control card. For example, if the standby Traverse GCM is a GCM with OC-48 card, you can only upgrade GCM with OC-48 cards in this procedure. If the standby TE-100 system card is an OC-48 card, you can only upgrade with another OC-48 system card.

Table 7-12 Activate Software—Spare Control Cards

Step Procedure

1 Remove the upgraded standby control card by restarting the card through the TransNav management system, then removing the card from the shelf.

2 Insert the spare (standby) control card.

3 Once the spare control card is online and the EQRMV/EQCOMM alarms are clear, download the new software version to the card using the Card Software Download Set-up, page 7-11 procedure.

4 Once the new software downloads to the spare control card, activate the software using the steps described for the standby control card in the Control Card Software Upgrade Activation, page 7-24 procedure.

5 Repeat Steps 1 through 4 for each spare control card.

6 Once the upgrade and activation is complete for all the spare control cards you can either:• Leave the last spare in place to act as the new standby card.• Replace the original standby control card back into the standby slot

and continue the procedure.

7 The Activate Software—Spare Control Cards 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-22• Step 26 of the procedure Control Card Software Upgrade

Activation, page 7-28

Chapter 1 Release TR3.2.3 Traverse Software UpgradeSpare Card Software Activation (All Other Types)


Spare Card Software Activation (All Other Types)

The new software is not active until the system activates the software and reboots the spare cards that are not control cards. The reboot loads and executes the new software.

The activation is scheduled for each card 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 cards.

Table 7-13 Activate Software—Spare Cards (All Other Types)

Step Procedure

1 Insert the spare card in an unused slot in the shelf that has an empty slot to both the left and the right of the spare card.

2 Once the spare card is online and the EQRMV/EQCOMM alarms are clear, download the new software version to the card using the Card Software Download Set-up, page 7-11 procedure.

3 Once the new software downloads to the spare card, activate the software using the steps described in the Software Upgrade Activate (All Other Protected Cards), page 7-29 procedure.

4 Repeat Steps 1 through 3 for each spare card.

5 The Activate Software—Spare Cards (All Other Types) procedure is complete. Continue to Step 9 of the Software Activation Process, page 7-19.

Operations and Maintenance Guide, Section 7: Software UpgradesVerify Protection Status


Verify Protection Status

Follow these step-by-step instructions to verify the protection status (Standby or Active) of a card/port in a protection group:

Table 7-14 Verify Protection Status

Step Procedure

1 From Map View, double-click on a node to display the Shelf View.

2 Click the Protection tab to display the Protection Groups dialog box.

Figure 7-19 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.

Figure 7-20 Equipment Protection Group Configuration Dialog Box

6 The Verify Protection Status procedure is complete.

Continue to Step 3 of the procedure Software Upgrade Activate (All Other Protected Cards), page 7-29.

2

5

Chapter 1 Release TR3.2.3 Traverse Software UpgradePerform a Forced Switch


Perform a Forced Switch

Use the following step-by-step instructions to perform a user-initiated forced protection switch.

Table 7-15 Perform a Forced Switch

Step Procedure

1 In Shelf View, click the Protection tab to display the Protection Groups dialog box.




4 Right-click the card or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Forced from the shortcut menu.

Figure 7-22 Protection Group—Forced Switch

5 The Confirm Force Switch dialog box displays. Click Yes to confirm.

Figure 7-23 Confirm Force Switch Dialog Box

6 Check the Alarms dialog box to verify the EQFAIL: equipment failure alarm caused by the forced protection switch has cleared.

Operations and Maintenance Guide, Section 7: Software UpgradesPerform a Manual Switch


Perform a Manual Switch

For cards 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 card (with the old software) from the active to the standby state.

Note: This procedure is required for cold restart activation only.

7 The active card 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 card, then return to Step 4.• active card, then return to Step 15.

Table 7-15 Perform a Forced Switch (continued)

Step Procedure

Table 7-16 Perform a Manual Switch

Step Procedure





Chapter 1 Release TR3.2.3 Traverse Software UpgradePerform a Manual Switch


4 Right-click the card or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Manual from the shortcut menu.

Figure 7-25 Protection Group—Manual Switch

5 The Confirm Manual Switch dialog box displays. Click Yes to confirm.

Figure 7-26 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 card or port is switched to standby.

8 The Perform a Manual Switch procedure is complete.

If you were in the procedure:• Control Card Software Upgrade Activation, then return to Step 14.• Software Upgrade Activate (All Other Protected Cards), then

return to Step 12.

Table 7-16 Perform a Manual Switch (continued)

Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesClear Protection Switch


Clear Protection Switch

Use the following step-by-step instructions to clear (release) a user-initiated protection switch.

Table 7-17 Clear Protection Switch

Step Procedure

1 From Map View, double-click on a node to display the Shelf View.




4 Click Edit to display the Protection Group Creation dialog box.

5 Right-click the Standby card/port in the Protection Group Creation dialog box to display a shortcut menu. Select Clear from the shortcut menu.

Figure 7-28 Protection Group—Clear Protection Switch

Chapter 1 Release TR3.2.3 Traverse Software UpgradeClear Protection Switch


6 The Confirm Release dialog box displays. Click Yes to confirm the force switch release.

Figure 7-29 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 card 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 card, then return to Step 14.– active card, then return to Step 24.

• Software Upgrade Activate (All Other Protected Cards), then return to Step 14.

Table 7-17 Clear Protection Switch (continued)

Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Revert Procedure


Software Revert Procedure

Use the following procedures to revert to a previous software version used on the node and TransNav management system.• Revert Node Software, page 7-42• Revert TransNav Management System Software, page 7-43

Revert Node Software

Important: This procedure is service affecting.

Important: If you expect to revert an entire node, Force10 recommends you call the Technical Assistance Center for assistance.

Table 7-18 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):beginexec upgrade switch-to-stdby-load slot <slot#>Are you sure you want to execute this command?YES.endexec node restartAre you sure you want to execute this command?YES.

3 Verify the node software level has been revised to the desired version and that the system is running the desired software load.

4 The Revert Node Software procedure is complete.

Chapter 1 Release TR3.2.3 Traverse Software UpgradePost-Remote Node— Upgrade the Spare Control Card Software


Revert TransNav Management System Software

Post-Remote Node— Upgrade the Spare Control Card Software

If you initially used the remote upgrade capability to upgrade the software version on your network nodes, the software on your spare cards 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 card (i.e., Traverse GCM or TE-100 system card). The reboot activates the backup partition with the newly downloaded software on the spare control card.

The activation is set based on the date and time entered in the Activate Time field of the SW Activation dialog box. Use these step-by-step instructions to set up software upgrade activation for spare control cards in the case where the other cards on the node have already been upgraded.

Table 7-19 Revert TransNav Management System Software

Step Procedure

1 Stop the upgraded TransNav server.

2 Start the previous version of software on the TransNav server.

3 Open the previous software version of the Client GUI. Verify the nodes and services are correct (i.e., nodesync/com are cleared).

4 The Revert TransNav Management System Software procedure is complete.

Important: This procedure assumes you have completed upgrading (downloading and activating the new software for) the standby and active control cards.

Important: A spare control card can only be upgraded in a shelf that has the same type of control card. For example, if the standby Traverse GCM is a GCM with OC-48 card, you can only upgrade GCM with OC-48 cards in this procedure. If the standby TE-100 system card is an OC-48 card, you can only upgrade with another OC-48 system card.

Table 7-20 Post-Remote Node —Upgrade the Spare Control Card

Step Procedure

1 Remove the previously upgraded standby control card by first restarting the card through the TransNav management system using a cold reboot, then removing the card from the shelf.

Operations and Maintenance Guide, Section 7: Software UpgradesPost-Remote Node— Upgrade the Spare Control Card Software


2 Insert the spare (standby) control card.

Important: Once the spare control card 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 card using the procedure in the procedure Card Software Download Set-up, page 7-11.

4 When the desired software is loaded onto the spare control card, activate the software using the steps described for the standby control card in the procedure described in procedure Control Card Software Upgrade Activation, page 7-24. You must change the value in the ActType field to SPARE.

Note: After the upgrade, the EQRMV and EQCOMM alarms clear.

5 Repeat Steps 1 through 4 for each spare control card.

6 Once the upgrade and activation is complete for all the spare control cards you can either:• Leave the last spare in place to act as the new standby card.• Place the original standby control card back into the standby slot and

continue the procedure.

7 The Post-Remote Node —Upgrade the Spare Control Card procedure is complete.

Table 7-20 Post-Remote Node —Upgrade the Spare Control Card (continued)

Step Procedure

Chapter 1 Release TR3.2.3 Traverse Software UpgradeUser- selectable FPGA Upgrade Capability


User- selectable FPGA Upgrade Capability

In some cases, upgrading from one Traverse release to another requires a new FPGA image for a card or set of cards. 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 card software change because it is non-critical in nature to your deployment. This capability allows the upgrade to proceed in a hitless fashion without loading the new FPGA image.

From the SW Activation dialog box, if you select to ignore the new FPGA image and the existing FPGA image remains compatible with the new FPGA image, the system performs a force warm upgrade for the card.

Figure 7-30 User-selectable FPGA Upgrade Parameter

Important: If a decision has been made to use Ignore FPGA, Force10 recommends upgrading to the new FPGA image as soon as possible during a network maintenance window.

Operations and Maintenance Guide, Section 7: Software UpgradesOverview to Upgrade TE-206 Nodes from TransNav


Overview to Upgrade TE-206 Nodes from TransNav

The TransNav GUI can be used to manage systems that include TE-206 nodes using functions including performing software downloads, upgrades, commits and fallbacks remotely to TE-206 nodes.

The following directories have been added to the Force10EMS directory on the management server to facilitate managing TE-206 nodes: nodedb, nodesoftware, and tl1log.

From the TransNav GUI, the following basic functions can be performed on the TE-206 nodes:

Software Upgrade: The complete process of downloading software to the NE and switching the running software on the NE from a previous version to a newer version. Software Upgrade (using the EMS) can only be performed on one NE at a time. If the software has already been downloaded onto the NE, the software upgrade process automatically skips the download step. The NE undergoes a soft reset during the software upgrade process which is non-traffic affecting, however, communication to the node is lost during the upgrade process. After the upgrade process the new software will be in the Not Commit State. In this state, the software will automatically Fallback to the previous load as a result of an NE reset. To prevent this from happening, you should transition the NE to either the Commit or Commit with Fallback state.

Software Download: The process of transferring the software from the EMS to the NE. It is a subset of the Software Upgrade process. Software Download is available as a separate function for two reasons; Use the Software Download function if you prefer to download the new software to the NE at one point in time, and then upgrade the NE to the software at a future point in time (possibly during the maintenance window that night); Use the Software Download function to download the software on multiple NEs simultaneously.

Note: To fully upgrade an NE, use the Software Upgrade feature. If you want to bulk software download first and then upgrade at a later time, first use Software Download and then Software Upgrade.

NE Software Commit: After an NE has been upgraded to new software, the NE is in the Not Commit state. In this state the software will automatically Fallback to the previous load as a result of an NE reset. To prevent this from happening, move the NE to either the Commit or Commit with Fallback state. Committing software locks the new software load into the NE. The states are described below:• Not Commit: Default state after a software upgrade. In the Not Commit state, an

NE reset causes the node to Fallback to the previous software version. • Commit - Software has been Committed on the NE. There is no Fallback option

after the NE has entered the Commit state. • Commit with Fallback: (CommitFallBk) Commit the software on the NE, but

allows you the option of falling back for a specified period of between 1 and 120 hours. After the fallback timer expires, the node automatically transitions to the Commit state.

Fallback: Software fallback is the process of reverting the software back to the old version from the new version. This is usually done because a problem has been discovered on the new software load. Fallback can only be performed on a node that is in the Not Commit state or the Commit with fallback state.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeOverview to Upgrade TE-206 Nodes from TransNav


Resolve Firmware Mismatch: If the NE contains new software that is expecting new firmware, the NE generates a firmware mismatch alarm. The EMS resolves the firmware mismatch alarm by loading the new firmware into the node. The new firmware may be part of the software load that is downloaded, but it is not upgraded during software upgrade. To resolve the firmware mismatch, the EMS must hard reset the NE which causes at least one traffic switch during the hard reset process.

Resolve Software Mismatch: If the NE contains software on one or more CCTs that does not match the rest of the node, the NE generates a software mismatch alarm. The EMS resolves this software mismatch alarms by loading the correct software on all the mismatched CCTs and performs a software upgrade (after user confirmation) on the system components that contain the incorrect version of software. This process is non-service affecting.

Figure 7-31 NE Software Dialog Box, View Software

TID - The TID of the NE

Vendor - The maker of the NE.

Model - The model number of the NE.

Current Version - The currently running version of the NE software

Secondary Version - The software loaded in the NEs secondary bank of RAM. If software has been downloaded but not yet upgraded, it appears in the Secondary Version field. During a software upgrade, the software loaded in the secondary bank becomes the currently running version of software; the current version becomes the secondary version.

Latest Version Available - This field is related to the software loads on the TransNav Server. It displays the latest version of software available in the TransNav software download directory for the given NE type.

Status - The current status of the software on the NE (Commit, Not Committed, Commit with Fallback, Commit with FWMM, or Disconnected).

Operations and Maintenance Guide, Section 7: Software UpgradesRequirements for Upgrading TE-206 Node Software


Requirements for Upgrading TE-206 Node Software

Review the following guidelines prior to upgrading TE-206 node software from the TransNav GUI:• TE-206 nodes must be running release R04.06.00 software to be discovered by

TransNav release TN4.2.3 or higher. (TE-206 nodes running Release R04.050.00 or lower must be upgraded from an external application, such as TN-Xpert or TN-Sight/TL1).

• Upgrades of TE-206 node software from the TransNav GUI must be performed manually; they cannot be scheduled.

• Upgrade software version must be in the nodesoftware directory in the EMS directory on the server prior to upgrading TE-206 node software.

Downloads can be performed across multiple TE-206 nodes simultaneously.

Downloading TE-206 Node Software

Use the following procedure to download node-level software from the TransNav management system for discovered TE-206 nodes for upgrade at a later time. Prior to downloading the TE-206 software, be sure the requirements for upgrading the software have been met. For more information, see the section, Requirements for Upgrading TE-206 Node Software. To fully upgrade the software on a node, see the section Upgrading TE-206 Node Software from TransNav.

Table 7-21 Downloading TE-206 Node Software

1 In the TransNav GUI, from Map View select the TE-206 node to update.

2 Select Admin, SW Upgrade. The NE Software dialog box displays.

Figure 7-32 NE Software Dialog Box

3 The current running version and state of the software for the nodes and equipment is listed. Highlight the node to where the software will be downloaded. To download to multiple nodes simultaneously, click the first node, hold the Shift key and click the last node to upgrade.

Note: Force10recommends upgrading a maximum of five nodes at a time.

Chapter 1 Release TR3.2.3 Traverse Software UpgradeDownloading TE-206 Node Software


4 While the nodes are highlighted (continue to hold down the Shift key), right-click and select Download from the shortcut menu. The Select Software Version dialog box displays.

Figure 7-33 Select Software Version Dialog Box

Select the software version to be used from the Software Versions parameter.

5 Click OK to begin downloading the selected software version. The NE Software Download dialog box displays.

6 Click Start at the bottom of the dialog box to begin the download. The status displays in the Status pane:

Figure 7-34 NE Software Download Dialog Box, Status

7 When the download completes, click Close.

8 The Downloading TE-206 Node Software procedure is complete.

Table 7-21 Downloading TE-206 Node Software

Operations and Maintenance Guide, Section 7: Software UpgradesUpgrading TE-206 Node Software from TransNav


Upgrading TE-206 Node Software from TransNav

The complete process of downloading software to the node and switching the running software on the node from a previous version to a newer version is performed by an upgrade. This process can only be performed on one node at a time. If the software has already been downloaded onto the node, the download step is ignored. During the upgrade, the node undergoes a soft reset. The soft reset is non-traffic affecting, however communication to the node is lost during the upgrade process.

Before beginning the upgrade, be sure the requirements for upgrading the software have been met. For more information, see Requirements for Upgrading TE-206 Node Software.

Upgrading TE-206 nodes from TransNav consists of first upgrading the software and, if necessary, the firmware and bootloader.

Table 7-22 Upgrading TE-206 Node Software from TransNav

1 In the TransNav GUI, from Map View select the specific TE-206 node to upgrade.

2 Select Admin, SW Upgrade. The NE Software dialog box displays.

Figure 7-35 NE Software Dialog Box

3 Highlight the TE-206 node to be upgraded.

Figure 7-36 Select TE-206 Node to Upgrade

Chapter 1 Release TR3.2.3 Traverse Software UpgradeUpgrading TE-206 Node Software from TransNav


4 From the NE Software dialog box, select Actions, Upgrade from the menu or right-click for a pull-down menu. The NE Software Upgrade dialog box displays.

Click Start at the bottom of the dialog box to begin the upgrade. The upgrade status displays in the Status pane.

A node database backup is performed and the software downloaded to the node if it was not previously downloaded. Some items are disabled based on the status of the software on the node.

5 When the software upgrade completes, click Close.

6 If necessary, upgrade the firmware and bootloader.

7 The Upgrading TE-206 Node Software from TransNav procedure is complete.

Table 7-22 Upgrading TE-206 Node Software from TransNav

Operations and Maintenance Guide, Section 7: Software UpgradesUpgrading TE-206 Node Software from TransNav



SECTION 7SOFTWARE UPGRADES

Chapter 2 Release TE3.2.x TE-100 System Software Upgrade

Introduction Complete the Release TE3.2.x software upgrade of all TraverseEdge 100 (TE-100) modules using the 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 TE3.2.x Upgrade Overview, page 7-53• Before You Begin, page 7-54• Required Equipment and Tools, page 7-54• TransNav Management System GUI Commands and Conventions, page 7-55• Compatibility and Guidelines, page 7-55• Node Software Upgrade Process, page 7-57• Software Revert Procedure, page 7-73

Release TE3.2.x Upgrade Overview

Release TE3.2.3 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 TE3.0.x to Release TE3.2.3—not an

in-service upgrade• In-service software upgrade TE3.2.x point releases (as necessary) for TE-100

nodes• TE-100 warm reboot and hitless upgrade features are unavailable• Simultaneous TransNav management system node software management to

accommodate longer-term upgrade paths:– Release TR3.0.0.7, TR3.2.1 and TR3.2.2 Traverse nodes– Release TE3.2.x TE-100 nodes– Release R04.06.01 TE-206 nodes

Operations and Maintenance Guide, Section 7: Software UpgradesBefore You Begin


Before You Begin

Review this information before you begin.


This section lists required equipment and tools for both hardware and software upgrades.

Software

The following items are required to upgrade TE-100 system software to a node or multiple nodes in a domain:• TransNav management system server connected to a TE-100 node or gateway

Traverse node• The Infocenter website (www.force10networks.com)

Note: If you do not have access to the Infocenter website, contact your local sales representative.

Hardware

Use the following hardware equipment and tools 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. Blank faceplates must be ordered separately.

TE-100 Shelf

• 1 or 2 System modules (and any spares)

Table 7-23 Node Software Upgrade Requirements

Requirement Reference

Compose and have ready for the Upgrade Team a comprehensive network upgrade plan.

Your company’s Operations Manager is responsible for this task.

Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company’s comprehensive upgrade plan.

• Refer to Release Notes TE3.2.3 • Read through this entire chapter• Contact your company’s Operations Manager

The software upgrade feature for this release supports TransNav 3.1.x to TN3.2.3 upgrades.

If you are upgrading from an earlier TransNav software release, contact the Force10Technical Assistance Center (TAC).

Have the required equipment and tools ready.



Chapter 2 Release TE3.2.x TE-100 System Software UpgradeGeneral Software Compatibility


TransNav Management System GUI Commands and Conventions

This document provides node software upgrade procedures using the TransNav GUI. Refer to the TransNav Management System Product Overview Guide to become familiar with the TransNav system.

The following conventions are used in the procedure tables.

Compatibility and Guidelines

Read the compatibility topics that are relevant to your specific upgrade.• General Software Compatibility, page 7-55• TE-100 Platform SW Upgrade Compatibility Notes, page 7-56• Guidelines for Software Upgrade, page 7-56

General Software Compatibility








Table 7-24 TransNav GUI Command Descriptions

Command Description

Boldface Boldface indicates dialog boxes, fields, menus, and list names.

Italics Italics indicate information that you supply.

Operations and Maintenance Guide, Section 7: Software UpgradesTE-100 Platform SW Upgrade Compatibility Notes



TE-100 Platform SW Upgrade Compatibility Notes

Review this information to understand the important compatibility items for the TE-100 and TransNav TN4.2.x software release.• TE-100 software upgrade from Release TE3.0.x.y to Release TE3.2.3. This is not

an in-service upgrade.• In-service TE3.2.x point release software upgrades (as necessary) for TE-100

nodes.• TransNav manages the in-service software upgrade for Release TE3.2.x

maintenance releases.• TE-100 hitless upgrade and warm reboot features are unavailable in this release.

Guidelines for Software Upgrade

Review the following guidelines for software upgrade:• Conduct upgrades in a specific maintenance window when you expect no

user-initiated service state changes.• Start the upgrade from the services egress node of the network (if possible).• Do not perform any new service creation, deletion, activation or deactivation (e.g.,

for Ethernet) until you complete the upgrade on the TransNav server and all network nodes.

• Do not change any fiber/link or other network (node, slot, port) objects during the upgrade.

• Due to the use of FTP libraries, bulk software downloads may fail so schedule software 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 TN3.2.x define any potential

exceptions.

Node Software Upgrade Process

Complete the software upgrade procedures in the following order:

Table 7-25 Node Software Upgrade Process


1 Have you read through, and do you understand, all of the Before You Begin items?

Before You Begin, page 7-54

2 Do you have the required equipment and tools ready?


Chapter 2 Release TE3.2.x TE-100 System Software UpgradeDownload Node Software to the TransNav Server


Download Node Software to the TransNav Server

You must first download the software for the upgrade from the Force10 Networks corporate website 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.

Download the TransNav Management System or Traverse node software from the Force10 Networks corporate website (www.force10networks.com). From Services & Support, select Customer Login. Enter your Force10 User ID and Password, then click Login.

3 Upgrade the TransNav management system server software (includes first exporting the current database off the TransNav server).

Note: Do not uninstall the previous software version. Mark the directory as old and remove the icon from the desktop.


4 Download the new node software to the TransNav server.


5 Download the software to the modules.

Module Software Download Set-up, page 7-60

6 Activate the new software. Software Activation Process, page 7-66

7 The Node Software Upgrade Process is complete.

Table 7-25 Node Software Upgrade Process (continued)


Operations and Maintenance Guide, Section 7: Software UpgradesDownload Traverse Node Software to the TransNav Server


Download Traverse Node Software to the TransNav Server

Use these steps to download the Traverse node software to the TransNav server.


Step Procedure

1 Navigate to the directory where the Traverse node software files were previously downloaded from the Force10 Networks website.

Figure 7-37 Example—PC System Explorer Window File Listing

2 Right-click the flash.n.n.n.n.zip file (where n.n.n.n is the latest software release number). For Windows PC systems, select the WinZip > Extract to command. For Solaris systems, use the gunzip command.

Chapter 2 Release TE3.2.x TE-100 System Software UpgradeDownload Traverse Node Software to the TransNav Server


3 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-38 Extract Dialog Box

4 The Download Traverse Node Software to the TransNav Server procedure is complete. Continue to Step 5 of the Traverse Node Software Upgrade Process, page 7-8.


Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesModule Software Download Set-up


Module Software Download Set-up

Software upgrades are done at the node level. The following procedure provides steps on how to begin a software upgrade by setting software download times for each card using the SW Upgrade dialog box.

Important: Due to repartitioning of the FLASH chip, GCM upgrades to Release TR3.2.3 will take approximately 8 to 0 minutes per GCM to upgrade instead of the 2 to 3 minutes necessary on to upgrade on earlier releases. Additionally, the Power LED on the GCM cards will blink red/green while the Active Standby light remains dark. Additionally, the Major/Critical and Minor LEDs may blink or may remain dark. THIS IS EXPECTED BEHAVIOR FOR UPGRADES TO THIS RELEASE.

Table 7-27 Card Software Download Set-up

Step Procedure

1 Verify the card software versions. Refer to Module Software Download Set-up, page 7-60.

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.

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

Chapter 2 Release TE3.2.x TE-100 System Software UpgradeModule Software Download Set-up


5 Username: Enter the user name with File Transfer Protocol (FTP) permission access to the TransNav server where the new node software version resides.

(For example: ftpusername)

6 Password: Enter the user password with FTP permission access to the TransNav server where the new node software version resides.

(For example: ftppassword)

7 Click 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 values must be set by the system before the download starts. Default is INIT.


Step Procedure



8 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: Force10 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: Force10 recommends you download the control cards individually, three line cards at a time and one node at a time.

Figure 7-40 Download Time Settings


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.

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 for each card.

Upgrade Type: 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 the Technical Assistance Center.

12 Repeat Steps 7 through 11 for each card in the node.


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

.

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 Force10’s Technical Assistance Center if the software download fails a second time.


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.

17 The Card Software Download Set-up procedure is complete.

Depending on the procedure where you started, return to either:• Step 6 of the Node Software Upgrade Flowchart (Top Level),

page 7-3• Step 3 of the Spare Card Software Activation (All Other Types),

page 7-35

Return to Step 6 of the Traverse Node Software Upgrade Process, page 7-8.


Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesCard Software Version Verification


Card Software Version Verification


Software Activation Process

The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software.


Step Procedure






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 working inward.

Important: During software activation, the modules automatically reboot. Do not execute any external commands on the modules during software activation.

Chapter 2 Release TE3.2.x TE-100 System Software UpgradeSoftware Activation Process


Table 7-29 Software Activation Process


1 Did you complete the upgrade of TransNav EMS server and client software, and download the node software to the TransNav server?

See the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Upgrade Server Software, page 2-48

2 Did you download the node software to the TransNav server?


3 Is the module software download complete?

Module Software Download Set-up, page 7-60

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.2.3 Traverse Software Upgrade,” Post-Remote Node— Upgrade the Spare Control Card Software, page 7-43).

• Active control module

Activate Software - Control Module, page 7-68

5 The Software Activation Process is complete. Continue to Step 7 of the Node Software Upgrade Process, page 7-57.

Operations and Maintenance Guide, Section 7: Software UpgradesActivate Software - Control Module


Activate Software - Control Module

The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software on the control module.

The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for control modules.

Important: Do not start the Activate Software— Control Module procedure until the downloaded software version displays in the SW Upgrade dialog box, Standby SW Ver field for all modules, indicating the software download has successfully completed.

Table 7-30 Activate Software— Control Module

Step Procedure


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.

Figure 7-44 Card Configuration Protection Status

3

Chapter 2 Release TE3.2.x TE-100 System Software UpgradeActivate Software - Control Module


4 Click the standby control module Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter.

Figure 7-45 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 Force10Technical Assistance Center if the software activation fails a second time.

Table 7-30 Activate Software— Control Module (continued)

Step Procedure

4

Operations and Maintenance Guide, Section 7: Software UpgradesActivate Software - Control Module


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 Force10Technical Assistance Center.

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-72 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:• 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 Force10Technical Assistance Center if the software activation fails a second time.


Step Procedure

Chapter 2 Release TE3.2.x TE-100 System Software UpgradeActivate Software - Control Module


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.

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


Step Procedure

Operations and Maintenance Guide, Section 7: Software UpgradesSpare Control Module Software Activation


Spare Control Module Software Activation

The new software is not active until the system reboots the spare (standby) control module. The reboot activates the backup partition with the newly downloaded software on the spare control module.

The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for spare control modules.

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. if the standby TE-100 System module is an OC-48 module, you can only upgrade with another OC-48 system module.

Table 7-31 Activate Software—Spare Control Modules

Step Procedure

1 Remove the upgraded standby control module by restarting the module through the TransNav management system, then removing the module from the shelf.

2 Insert the spare (standby) control module.

3 Once the spare control module is online and the EQRMV and EQCOMM alarms are clear, download the new software version to the module using the Table 7-27 Card Software Download Set-up, page 7-60 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-30 Activate Software— Control Module, page 7-68 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 Activate Software - Control Module, page 7-70.

Chapter 2 Release TE3.2.x TE-100 System Software UpgradeSoftware 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-73• Revert TransNav Management System Software, page 7-74

Revert Node Software

Important: This procedure is service affecting.

Important: If you expect to revert an entire node, Force10 recommends you call the Technical Assistance Center for assistance.

Table 7-32 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):beginexec upgrade switch-to-stdby-load slot <slot#>Are you sure you want to execute this command?YES.endexec node restartAre you sure you want to execute this command?YES.

3 Verify the node software level has been revised to the desired version and that the system is running the desired software load.

4 The Revert Node Software procedure is complete.

Operations and Maintenance Guide, Section 7: Software UpgradesSoftware Revert Procedure


Revert TransNav Management System Software

Table 7-33 Revert TransNav Management System Software

Step Procedure

1 Stop the upgraded TransNav server.

2 Start the previous version of software on the TransNav server.

3 Open the previous software version of the Client GUI. Verify the nodes and services are correct (i.e., nodesync/com are cleared).

4 The Revert TransNav Management System Software procedure is complete.


SECTION 8 HARDWARE UPGRADESSECTION 8

Contents

Chapter 1Replacing Existing Traverse Hardware

Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Fan Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Software Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Software Version Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Electrostatic Discharge Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Traverse Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Replacement Module—Type and Software Version . . . . . . . . . . . . . . . . . . . . 8-4Preparing a Module for Removal and Replacement . . . . . . . . . . . . . . . . . . . . 8-6Remove a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Module Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9GCM Module Replacement as Standby— LED Indicators . . . . . . . . . . . . . . . 8-14Clean Fiber Optic MPX Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15Insert a Replacement Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19Replace the Front Inlet Fan Tray Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Front Inlet Fan Tray Air Filter Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26Replace the Traverse 600 Fan Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27Fan Assembly Air Filter Installation (Traverse 600) . . . . . . . . . . . . . . . . . . . . 8-29

Chapter 2Upgrade to a Traverse Front Inlet Fan Tray

Precautions and Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Required Equipment and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32FIFT Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Check the New Fan Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33

Operations and Maintenance Guide, Section 8 Hardware Upgrades



SECTION 8HARDWARE UPGRADES

Chapter 1 Replacing Existing Traverse Hardware

Introduction During the course of normal operation, various conditions may arise that require network operations personnel to replace existing system equipment. This section describes Traverse module and fan equipment replacement.

Modules

All modules in the Traverse system, including the General Control Modules (GCMs), are “hot-swappable” and can be removed and replaced while the system is in operation. During replacement procedures, service is interrupted to all connections on the removed modules. For related information about adding and removing modules using the TransNav GUI, see the TransNav Management System GUI Guide, Section 3—Network, Chapter 1—“Creating and Deleting Equipment.”

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 Guidelines, page 8-9• GCM Module Replacement as Standby— LED Indicators, page 8-14• Clean Fiber Optic MPX Connectors, page 8-15• Insert a Replacement Module, page 8-19

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

The fan equipment replacement topics are as follows:

Operations and Maintenance Guide, Section 8: Hardware UpgradesSoftware Compatibility


• 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-23• Front Inlet Fan Tray Air Filter Replacement, page 8-26• Replace the Traverse 600 Fan Assembly, page 8-29• Fan Assembly Air Filter Installation (Traverse 600), page 8-31

Software Compatibility









Refer to Section 7—Software Upgrades, Chapter 1—“Release TR3.2.3 Traverse Software Upgrade” for software upgrade procedures.

Chapter 1 Replacing Existing Traverse HardwareSoftware Version Verification


Software Version Verification



Step Procedure






Operations and Maintenance Guide, Section 8: Hardware UpgradesElectrostatic Discharge Protection


Electrostatic Discharge Protection

Wear a properly grounded Electrostatic Discharge (ESD) wrist strap during the following installation and maintenance activities to avoid damaging the Traverse integrated circuits:• While handling any Traverse module• When connecting copper or optical cables to the PDAP, Traverse main backplane,

fiber optic backplane, and fan tray module


The following hardware equipment and tools are required to place cards in a Traverse shelf.

General

• Electrostatic Discharge (ESD) wrist strap• Eye protection• 1-slot wide blank faceplates for any empty slots to ensure EMI protection and

proper cooling. Blank faceplates must be ordered separately.

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.2.3 Traverse Software Upgrade” for procedures on how to convert software versions on a replacement module.

Chapter 1 Replacing Existing Traverse HardwareReplacement 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 to indicate 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

Operations and Maintenance Guide, Section 8: Hardware UpgradesPreparing a Module for Removal and Replacement


Preparing a Module for Removal and Replacement

The following procedures provide step-by-step instructions on how to prepare a module for removal and replacement using the TransNav GUI.

Important: GCM, Enhanced GCM (EGCM), Universal GCM (UGCM), and GCMs with integrated optics are considered different modules and must be physically removed and deleted via TransNav prior to replacement with a different GCM module type to avoid an EQMIS: Equipment Mismatch alarm.

Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older GCM modules with the newer GCM modules in a redundant configuration. The following replacement rules apply:

Replace:• GCM with a UGCM• EGCM (without optics) with a UGCM• EGCM (with OC-12/STM-4) with a UGCM with 1-port

OC-12/STM-4• EGCM (with OC-48/STM-16) with a UGCM with OC-48/STM-16

Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older DS3, E3, EC-1, and DS3 Transmux modules with the newer DS3, E3, EC-1, and DS3 Transmux modules with no greater than 50 ms traffic interruption for each module in any 1:N (where N=1,2) protection group.

Table 8-2 Preparing a Module for Removal and Replacement

Step Procedure

1 In the TransNav GUI, go to Shelf View.

2 Click the module to be removed.

3 Click the Config tab to display the Card Configuration dialog box.

4 Click the Lock icon at the bottom left portion of the screen to change the Administrative state to locked and click Apply.

Note: Force10 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.

Chapter 1 Replacing Existing Traverse HardwarePreparing a Module for Removal and Replacement


6 In the TransNav GUI, right-click the module and select Delete Card to delete the card or Replace with Card to replace with a different type of module.

7 Place the new module in the Traverse shelf. Refer to the following sequence of topics for important details:• Module Placement Guidelines, page 8-9• GCM Module Replacement as Standby— LED Indicators,

page 8-14 (Standby GCM module replacement only.)• Clean Fiber Optic MPX Connectors, page 8-15• Insert a Replacement Module, page 8-19

8 Click the Lock icon at the bottom left portion of the screen to change the Administrative state to unlock and click Apply.

9 The Preparing a Module for Removal and Replacement procedure is complete.

Table 8-2 Preparing a Module for Removal and Replacement (continued)

Step Procedure

Operations and Maintenance Guide, Section 8: Hardware UpgradesRemove a Module


Remove a Module

Follow these steps 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 Procedure

1 Flip the locking tabs up to unlock the card.

Figure 8-3 Card Tabs in the Unlocked Position

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.

OPS 00083

Locking Tabs inOpen Position

Chapter 1 Replacing Existing Traverse HardwareModule Placement Guidelines


Module Placement Guidelines

The following restrictions apply for module placement in a Traverse shelf.

Refer to Appendix A—“Module Placement Planning and Guidelines,” page 9-1 for additional information.

Table 8-4 Card Placement Guidelines

Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s

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

GCMA and

GCMB (slots 15 and 16)

GCMA and

GCMB(slots 19 and 20)

GCMA and

GCMB(slots 5 and 6)

Redundant GCMs are recommended for equipment protection. However, if only one GCM is used, it can be placed in either slot GCMA or GCMB.

Redundant GCMs can be different types. See Table 8-5 Redundancy Rules for GCM Types for a list of control cards.

Electrical

• DS1• DS3/E3/EC-1 CC (12-port)• DS3/E3/EC-1 CC (24-port)• DS3/EC-1 Transmux• E1• Universal Transmux (24-port or

48-port) (UTMX-24 or UTMX-48)

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 optical 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 optical card in the left-most slot.

For Optical Transmux card placement, see Optical Transmux in this table.

Optical Transmux

Operations and Maintenance Guide, Section 8: Hardware UpgradesModule Placement Guidelines


• DS3/EC-1 Transmux 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. (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.

• UTMX-24 or UTMX-48 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. (SONET network only) The UTMX cards support 1:N equipment protection for high-density optical transmux applications, where N=1 to 4 in a Traverse 2000. This application has no DS3/E3 ECM requirement. One card protects all remaining adjacent cards.

Table 8-4 Card Placement Guidelines (continued)

Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s




Ethernet (Next Generation)

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

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 Ethernet Protection ECM, either the left- or right-adjacent card from the protection card is the working card.

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 optical card in the left-most slot.

Use one of 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 faceplate1 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 faceplate1 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 n/a None

• 10-port GbE card, no optics 1–12 1–16 Requires an SFP connector card. See the 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.

In a 1:1 equipment protection scheme, the working and protect cards are placed in slots adjacent to each other. The protection card must be on the left; the working card on the right.

Ethernet over PDH (EoPDH)


Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


Operations and Maintenance Guide, Section 8: Hardware UpgradesModule Placement Guidelines


• GbE [LX, SX] plus 10/100BaseTX Combo [CEP/EoPDH]

• GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP/EoPDH]

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 Ethernet Protection ECM, either the left- or right-adjacent card from the protection card is the working card.





SONET/SDH

• OC-3/STM-1• OC-12/STM-4• OC-48/STM-16

1–14 1–18 1-4 None

• OC-192/STM-64 1/2, 3/4, 5/6, 7/8,

9/10, 11/12, and

13/14

1/2, 3/4, 5/6, 7/8,

9/10, 11/12, 13/14, 15/16,

and 17/18

n/a The OC-192/STM-64 cards require two slots for placement. The left side of the OC-192/STM-64 card is placed in an odd numbered slot.


Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s




Force10 recommends the following card placement scheme:• Place DS1, DS3, E3, EC-1 CC, DS3/EC-1 Transmux, 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.

VT/TU Switching

VT/TU 5G Switch 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)

This card has no ECM requirement. One card protects all adjacent cards.

1 Blank faceplates must be ordered separately.


Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


Important: For electrical port usage only, place an OC-N/STM-N or 1-slot blank faceplate1 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 interface card.

If the 10/100BaseTX-inclusive card also contains optical ports, and if the user intends to ONLY use the optical ports, this electrical port usage restriction does not apply.

Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots.

Operations and Maintenance Guide, Section 8: Hardware UpgradesGCM Module Replacement as Standby— LED Indicators


The following table lists the redundancy rules for all GCM types:

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.

Table 8-5 Redundancy Rules for GCM Types

Active GCM Standby GCM

GCM GCM

GCM GCM Enhanced | Universal1

1 GCM Enhanced or Universal environmental alarm function should not be used in this combination.

GCM Enhanced | Universal1 GCM

GCM Enhanced | Universal GCM Enhanced | Universal

GCM with OC-N/STM-N GCM with OC-N/STM-N

Table 8-6 Power and Active/Standby—GCM Cards



Power


Hardware failure detected; replace the card.

N/A N/A Node is in commissioning

mode

Passed initialization and is operational

No power

Active/ Standby

N/A N/A Standby mode;

synchroniza-tion with the Active card

is not complete.

Card type does not match the provisioned card type or the card is placed in an invalid slot.1

Standby mode; synchroniza-tion with the active card is complete.

Active and operational


1 Please refer to Appendix A—“Card Placement Planning and Guidelines,” page 12-1 for valid card placement guidelines.

Chapter 1 Replacing Existing Traverse HardwareClean 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. Force10 recommends that you visually inspect the MPX connectors on both the fiber optic cables and optical cards using fiber optic magnification equipment. Force10 also recommends that you clean the fiber optic cable and card MPX connectors using the following procedure.

OPTIC 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 when power is applied. Laser output is invisible and eye damage can result. Follow these safety features to prevent looking into the optical connector.

OPTIC 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. Follow this safety feature as it is designed to prevent eye damage.

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

Operations and Maintenance Guide, Section 8: Hardware UpgradesClean 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.

Chapter 1 Replacing Existing Traverse HardwareClean Fiber Optic MPX Connectors


5 Align the “white reference marker” on the MPX connector with the white stripe on the left side of the Traverse 600 fiber optic backplane housing.

Figure 8-5 Traverse 600 Fiber Optic Backplane Housing A and B

6 Gently push the MPX connector back into the correct fiber optic backplane housing.

7 Repeat Steps 2 through 6 for each MPX connector.

8 Remove the dust cap from the optical card MPX connector(s).

Figure 8-6 Optical Card MPX Connector

Table 8-7 Clean Cable and Card MPX Connectors (continued)

Step Procedure

OPS 00085

Housing A

Housing B

White StripeReference Markers

OPS 00083

Dust Cap on MPX Connector

Operations and Maintenance Guide, Section 8: Hardware UpgradesClean Fiber Optic MPX Connectors


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.

Table 8-7 Clean Cable and Card MPX Connectors (continued)

Step Procedure

Chapter 1 Replacing Existing Traverse HardwareInsert 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• EoPDH

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.

Operations and Maintenance Guide, Section 8: Hardware UpgradesInsert a Replacement Module


Follow these steps to insert a card.

Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots. Blank faceplates must be ordered separately.

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.

Figure 8-7 Card Locking Tabs in the Unlocked Position

OPS 00083

Guide Pins

Locking Tabs in Open Position

Chapter 1 Replacing Existing Traverse HardwareInsert a Replacement Module


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.

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.

Figure 8-9 Traverse 600 Shelf with Guides

Table 8-8 Insert a Card (continued)

Step Procedure

Card Cage Guides for Card Alignment

Card Cage Guides for Card Alignment

Operations and Maintenance Guide, Section 8: Hardware UpgradesInsert a Replacement Module


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.

Figure 8-10 Card Tabs in the Locked Position

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.

Table 8-8 Insert a Card (continued)

Step Procedure

Locking Tabs inClosed Position

Chapter 1 Replacing Existing Traverse HardwareReplace the Front Inlet Fan Tray Module


Replace the Front Inlet Fan Tray Module

The front inlet fan tray assembly is bundled and shipped with the Traverse 1600 and Traverse 2000 systems. Proceed with the following steps to replace the fan tray module into an existing installation.

Note: This procedure is not service affecting if it is completed within 6 minutes. Typical time for completion of this procedure is 3 minutes.

Note: Have all necessary materials on the work site prior to beginning this procedure.

Note: Normal fan operation is indicated by the green LED being illuminated and the red LED being extinguished. An illuminated red LED indicates a fault condition on that fan module.

Important: The instructions below support the redesigned front inlet fan tray with integrated air ramp unit.

Important: Wear a properly grounded Electrostatic Discharge (ESD) wrist strap when installing the fan module as it contains static-sensitive components.

Table 8-9 Replace a Traverse 1600 and Traverse 2000 Fan Assembly

Step Procedure

1 Loosen the captive thumb screws on the fan module (card) front cover to release it.

Figure 8-11 Front Inlet Fan Module Captive Thumb Screws

2 Use the captive thumb screws as handles to aid in the removal of the fan module.

Important: Use caution when initially handling the fan module. The fans will still be rotating for a short period of time after removal.

OPS 00088

Captive Thumb Screws

Operations and Maintenance Guide, Section 8: Hardware UpgradesReplace the Front Inlet Fan Tray Module


3 Lift the front inlet fan module to be level with the front inlet fan tray holder. Slide the fan module into the front of the fan tray holder along the guides. Push the module straight in until the two connectors engage.

WARNING! The fans will begin to rotate as soon as the power connection mates to the fan module holder.

Figure 8-12 Traverse 1600 Front Inlet Fan Module Installation

4 The front inlet fan module is in the correct position when it is slightly recessed from the front of the fan module holder.

Important: Do not force the fan module into position. If it does not plug in easily, slide it back out. Check for any obstructions or a damaged connector that might prevent it from sliding into position and verify it is in the correct guides before attempting to insert it again.

Table 8-9 Replace a Traverse 1600 and Traverse 2000 Fan Assembly (continued)

Step Procedure

Fan Module Connectors

Fan Tray Holder Guide


Chapter 1 Replacing Existing Traverse HardwareReplace the Front Inlet Fan Tray Module


5 Align and tighten the captive thumb screws to secure the fan module front cover.

Figure 8-13 Front Inlet Fan Module Captive Thumb Screws

6 Continue to the next procedure, Insert a Traverse 1600 and Traverse 2000 Fan Air Filter.

Table 8-9 Replace a Traverse 1600 and Traverse 2000 Fan Assembly (continued)

Step Procedure

OPS 00088


Operations and Maintenance Guide, Section 8: Hardware UpgradesFront Inlet Fan Tray Air Filter Replacement


Front Inlet Fan Tray Air Filter Replacement

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.

Table 8-10 Install a Fan Tray Air Filter with Springs (Legacy)

Step Procedure


2 Insert the new air filter. Rotate the air filter pull-tabs out.

Figure 8-14 Air Filter with Springs

3 Hold the air filter with the metal window-pane side down and the springs to the back.

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

5 With the springs fully compressed, lift the front edge of the air filter up and over the retaining flanges and release it.

6 Rotate the pull-tabs so they are parallel to the front edge of the air filter.

OPS 00058

Springs

Pull Tabs

Chapter 1 Replacing Existing Traverse HardwareInstall a Fan Tray Air Filter with Handle (Legacy)


Install a Fan Tray Air Filter with Handle (Legacy)

The following procedure provides steps on how to install the fan tray filter with a handle on the front edge.



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.


Table 8-10 Install a Fan Tray Air Filter with Springs (Legacy) (continued)

Step Procedure

OPS 00059

Captive Fasteners

Table 8-11 Install a Fan Tray Air Filter with Handle (Legacy)

Step Procedure

1 If you are replacing an old air filter, carefully remove the old air filter from the fan tray holder to avoid contaminationg the equipment.

2 Hold the air filter with the metal window-pane side down with the handle facing to the front.

Figure 8-16 Air Filter with Handle

OPS 00060

Handle

Operations and Maintenance Guide, Section 8: Hardware UpgradesInstall a Fan Tray Air Filter with Handle (Legacy)


3 Insert the air filter in the gap between the fan tray card and the top of the fan tray holder.

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



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.

6 The Install a Fan Tray Air Filter with Handle (Legacy) procedure is complete.

Table 8-11 Install a Fan Tray Air Filter with Handle (Legacy) (continued)

Step Procedure

OPS 00059

Captive Fasteners

Chapter 1 Replacing Existing Traverse HardwareReplace 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-12 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.

Figure 8-18 Fan Assembly Front Cover - Traverse 600

2 Open the right-front fan assembly cover.

OPS 00089

Captive Fasteners

Operations and Maintenance Guide, Section 8: Hardware UpgradesReplace the Traverse 600 Fan Assembly


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.

Figure 8-19 Traverse 600 Fan Assembly Installation

4 The Replace the Traverse 600 Fan AssemblyInsert a Traverse 600 Fan Assembly procedure is complete.

Table 8-12 Insert a Traverse 600 Fan Assembly (continued)

Step Procedure

OPS 00090

Traverse 600 Shelf

Fan Assembly

Chapter 1 Replacing Existing Traverse HardwareFan 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-13 Insert a Traverse 600 Fan Air Filter

Step Procedure


2 Install the new air filter. Grasp the air filter flexible pull tab.

Figure 8-20 Traverse 600 Fan Assembly Air Filter

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


OPS 00057Pull Tab (top view)

Operations and Maintenance Guide, Section 8: Hardware UpgradesFan Assembly Air Filter Installation (Traverse 600)



SECTION 8SECTION 8HARDWARE UPGRADES

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.

WARNING! Depending on the number of modules in the shelf and the room temperature, Force10 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: 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.

Operations and Maintenance Guide, Section 8: Hardware UpgradesRequired Equipment and Tools



The following equipment and tools are required for this upgrade:• Front inlet fan tray holder• Front inlet fan module• Air filter1

• Large straight slot screwdriver or 5/16-inch hex socket• Two technicians (to decrease the replacement time, have one in front and one in

back of the rack)• Stepladder (optional)• Electrostatic Discharge (ESD) wrist strap

FIFT Upgrade Instructions

Follow these FIFT upgrade instructions:

1 Front inlet fan tray air filters are available in 63% arrestance at 300 feet per minute (91.4 meters per minute) and 80% arrestance at 300 feet per minute (91.4 meters per minute) depending on your installation requirements.

Table 8-14 Front Inlet Fan Tray Holder Upgrade Instructions

Step Instructions

1 Check the New Fan Module, page 8-35 to ensure proper power up.

2 Power down the existing fan.

3 Is there an air ramp below the existing fan tray?• Yes. Remove it.• No. Go to the next step.

4 To avoid contamination to the equipment, carefully pull the air filter from the fan tray holder.

5 Remove the existing fan tray module.

6 Remove the power cable from the rear of the fan tray holder.

7 Remove the fan tray holder.

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

9 The Front Inlet Fan Tray Holder Upgrade Instructions are complete.

Chapter 2 Upgrade to a Traverse Front Inlet Fan TrayCheck the New Fan Module


Check the New Fan Module

Check the new FIFT fan module as follows:

Table 8-15 New Fan Module Check

Step Procedure

1 From the rear of the existing fan tray module, loosen the two thumbscrews on the power cable cover (located on the left-hand side).

Figure 8-21 Existing Fan Tray Holder Back Panel

2 Unplug the power cable from the existing fan tray module.

3 Plug the power cable into the new FIFT fan module to verify power up.

4 Unplug the power cable from the new FIFT fan tray module.

5 Plug the power cable back into the existing fan module.

6 Did the new FIFT fan module power up?• Yes. Go to Step 9.• No. Go to Step 7.

7 Tighten the thumbscrews on the existing power cable cover and stop the upgrade procedure.

8 RMA the tested fan module.

9 The New Fan Module Check procedure is complete.

Front

Power Cable Cover

Operations and Maintenance Guide, Section 8: Hardware UpgradesCheck the New Fan Module



SECTION 9 APPENDICESSECTION 9

Contents

Appendix AModule Placement Planning and Guidelines

Module Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Traverse 1600 Module Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7Traverse 2000 Card Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12Traverse 600 Card Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Operations and Maintenance Guide, Section 9 Appendices



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

This appendix contains information on the following topics:• Module Placement Guidelines, page 9-2• Traverse 1600 Module Placement, page 9-7• Traverse 2000 Card Placement, page 9-12• Traverse 600 Card Placement, page 9-16

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

Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots. Blank faceplates must be ordered separately.

Operations and Maintenance Guide, Section 9: AppendicesModule Placement Guidelines


Module Placement Guidelines

The following table lists guidelines for placement of modules in a Traverse shelf:

Table 9-1 Card Placement Guidelines

Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


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

GCMA and

GCMB (slots 15 and 16)

GCMA and

GCMB(slots 19 and 20)

GCMA and

GCMB(slots 5 and 6)

Redundant GCMs are recommended for equipment protection. However, if only one GCM is used, it can be placed in either slot GCMA or GCMB.

Redundant GCMs can be different types. See Table 9-2 Redundancy Rules for GCM Types for a list of control cards.

Electrical

• DS1• DS3/E3/EC-1 CC (12-port)• DS3/E3/EC-1 CC (24-port)• DS3/EC-1 Transmux• E1• Universal Transmux (24-port or

48-port) (UTMX-24 or UTMX-48)

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 optical 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 optical card in the left-most slot.

For Optical Transmux card placement, see Optical Transmux in this table.

Optical Transmux

• DS3/EC-1 Transmux 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. (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.

Appendix A Module Placement Planning and GuidelinesModule Placement Guidelines


• UTMX-24 or UTMX-48 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. (SONET network only) The UTMX cards support 1:N equipment protection for high-density optical transmux applications, where N=1 to 4 in a Traverse 2000. This application has no DS3/E3 ECM requirement. One card protects all remaining adjacent cards.

Ethernet (Next Generation)

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

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 Ethernet Protection ECM, either the left- or right-adjacent card from the protection card is the working card.





Ethernet (Dual Slot GbE)


Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s




• 10GBASE-LR 1–14 1–18 n/a None

• 10-port GbE card, no optics 1–12 1–16 Requires an SFP connector card. See the 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.

In a 1:1 equipment protection scheme, the working and protect cards are placed in slots adjacent to each other. The protection card must be on the left; the working card on the right.

Ethernet over PDH (EoPDH)

• GbE [LX, SX] plus 10/100BaseTX Combo [CEP/EoPDH]

• GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP/EoPDH]

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 Ethernet Protection ECM, either the left- or right-adjacent card from the protection card is the working card.






Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


Appendix A Module Placement Planning and GuidelinesModule Placement Guidelines


Force10 recommends the following card placement scheme:• Place DS1, DS3, E3, EC-1 CC, DS3/EC-1 Transmux, 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).

SONET/SDH


1–14 1–18 1-4 None

• OC-192/STM-64 1/2, 3/4, 5/6, 7/8,

9/10, 11/12, and

13/14

1/2, 3/4, 5/6, 7/8,

9/10, 11/12, 13/14, 15/16,

and 17/18

n/a The OC-192/STM-64 cards require two slots for placement. The left side of the OC-192/STM-64 card is placed in an odd numbered slot.

VT/TU Switching

VT/TU 5G Switch 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)

This card has no ECM requirement. One card protects all adjacent cards.

1 Blank faceplates must be ordered separately.


Card TypeTraverse

1600 Slot #s

Traverse 2000

Slot #s

Traverse 600

Slot #s


Important: For electrical port usage only, place an OC-N/STM-N or 1-slot blank faceplate1 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 interface card.


Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots.



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

The following table lists the redundancy rules for all GCM types:

Table 9-2 Redundancy Rules for GCM Types

Active GCM Standby GCM

GCM GCM

GCM GCM Enhanced | Universal1

1 GCM Enhanced or Universal environmental alarm function should not be used in this combination.

GCM Enhanced | Universal1 GCM

GCM Enhanced | Universal GCM Enhanced | Universal

GCM with OC-N/STM-N GCM with OC-N/STM-N

Operations and M

aintenance Guide, S

ection9: A

ppendicesTraverse 1600 M

odule Placement

Page 9-7Force10 N

etworks

Release O

PS4.2.3

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 3—“ECM Interface Specifications” 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

Card TypeTraverse 1600 Slot Numbers

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

GCM S/A S/A

• GCM

• Enhanced GCM1

• GCM OC-12/STM-41


OPTICAL (Note: Optical cards are protected at the port level. There are no slot or card placement restrictions for optical working/protection.)


W W W W W W W W W W W W W W

• OC-192/STM-64 Slots 1/2 Slots 3/4 Slots 5/6 Slots 7/8 Slots 9/10 Slots 11/12 Slots 13/14

ETHERNET (Dual slot)

Operations and M

aintenance Guide, S

ection9: A


odule Placement

Page 9-8Force10 N

etworks

Release O

PS4.2.3

• 1-port 10GbE• 10-port GbE

Slots 1/2P

Slots 3/4W/P

Slots 5/6W/P

Slots 7/8W/P

Slots 9/10W/P

Slots 11/12W/P

Slots 13/14W

ETHERNET (Single slot) 1:1 equipment protection with a 2-slot Ethernet Protection ECM

(Note: The Ethernet Combo cards have both optical ports and electrical ports. The card placement restriction is due to the electrical ports.)

NGE, NGE Plus, EoPDH:• GbE [LX, SX] plus

10/100BaseTX Combo [CEP\[EoPDH]]

• GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP\[EoPDH]]

NGE only:• GbE CWDM plus

10/100BaseTX Combo• GbE SX plus GbE CWDM

plus 10/100BaseTX Combo

P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W

ETHERNET (Single slot) unprotected with a 2-slot 10/100BaseT ECM







W W W W W W W W W W W W

ETHERNET (Single slot) unprotected with a 2-slot Ethernet (Protection) ECM

Table 9-3 Traverse 1600 Card Placement Guidelines (continued)


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Appendix A

Module P

lacement P

lanning and Guidelines

Traverse 1600 Module Placem

ent

Release O

PS4.2.3Force10 N

etworks

Page 9-9







O W/O W/O W/O W/O W/O W/O W/O W/O W/O W/O W

TDM 1:2 equipment protection with the corresponding ECM

• DS1 • DS3/E3/EC-1 CC • DS3/EC-1 Transmux• E1

W W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W

TDM 1:1 equipment protection with a 2-slot ECM

• DS1 • DS3/E3/EC-1 CC • DS3/EC-1 Transmux • E1

W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P


• DS3/E3/EC-1 CC • DS3/EC-1 Transmux• E1

W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O

TDM unprotected with the corresponding ECM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Operations and M

aintenance Guide, S

ection9: A


odule Placement

Page 9-10Force10 N

etworks

Release O

PS4.2.3

• DS1 • E1

W W W W W W W W W W W W

TDM unprotected with a 2-slot DS3/E3 ECM (Note: The 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/O W/O W/O W/O W/O W/O W/O W W

VT/VC Switching 1:N equipment protection (Note: No ECM requirement with VT/VC switching cards.)

VT/TU 5G Switch W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P

GCM with optics plus VTX2 W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P

VT/VC Switching unprotected

VT/TU 5G Switch W W W W W W W W W W W W W W

GCM with optics plus VTX2 W W W W W W W W W W W W W W

1 Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with an 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: For electrical port usage only, 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.




1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Appendix A

Module P

lacement P


Traverse 1600 Module Placem

ent

Release O

PS4.2.3Force10 N

etworks

Page 9-11

Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling. Blank faceplates must be ordered separately.

Operations and M

aintenance Guide, S

ection9: A

ppendicesTraverse 2000 C

ard Placement

Page 9-12Force10 N

etworks

Release O

PS4.2.3

Traverse 2000 Card Placement



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 3—“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.



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

GCM S/A S/A

GCM

Enhanced GCM1

GCM OC-12/STM-41

GCM OC-48/STM-161



W W W W W W W W W W W W W W W W W W

OC-192/STM-64 Slots 1/2 Slots 3/4 Slots 5/6 Slots 7/8 Slots 9/10 Slots 11/12 Slots 13/14 Slots 15/16 Slots 17/18

ETHERNET (Dual slot)

• 1-port 10GbE Slots 1/2P

Slots 3/4W/P

Slots 5/6W/P

Slots 7/8W/P

Slots 9/10W/P

Slots 11/12W/P

Slots 13/14W/P

Slots 15/16W/P

Slots 17/18W

Appendix A

Module P

lacement P


Traverse 2000 Card Placem

ent

Release O

PS4.2.3Force10 N

etworks

Page 9-13

• 10-port GbE 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

ETHERNET unprotected with a 2-slot 10/100BaseT ECM







W W W W W W W W W W W W W W W W

ETHERNET unprotected with a 2-slot Ethernet (Protection) ECM







O W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W

TDM 1:2 equipment protection with corresponding ECM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Operations and M

aintenance Guide, S

ection9: A


ard Placement

Page 9-14Force10 N

etworks

Release O

PS4.2.3


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

W/P

W/P


• DS3/E3/EC-1 CC • DS3/EC-1 Transmux• E1

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O

W/P/O


• DS1 • E1

W W W W W W W W W W W W W W W W



O W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W


• DS3/E3/EC-1 CC• DS3/EC-1 Transmux

O W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W/O

W W

VT/VC Switching with 1:N equipment protection (Note: No ECM requirement with VT/VC switching cards.)



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Appendix A

Module P

lacement P



ent

Release O

PS4.2.3Force10 N

etworks

Page 9-15

VT/TU 5G Switch with 1:1 Equipment Protection

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

GCM with optics plus VTX2 W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

W/P

VT/VC Switching unprotected

VT/TU 5G Switch without Equipment Protection

W W W W W W W W W W W W W W W W W W

GCM with optics plus VTX2 W W W W W W W W W W W W W W W W W W


2 While the VTX can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1 APS/MSP, UPSR/SNCP, or BLSR/MS-SPRing protection group.



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20




Operations and M

aintenance Guide, S

ection9: A


ard Placement

Page 9-16Force10 N

etworks

Release O

PS4.2.3

Traverse 600 Card Placement



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.



1 2 3 4 5 6

GCM S/A S/A

• GCM

• Enhanced GCM1





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

Appendix A

Module P

lacement P



ent

Release O

PS4.2.3Force10 N

etworks

Page 9-17

NGE, NGE Plus, EoPDH:• GbE [LX, SX] plus 10/100BaseTX Combo

[CEP\[EoPDH]]• GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo

[CEP\[EoPDH]]

NGE only:• GbE CWDM plus 10/100BaseTX Combo• GbE SX plus GbE CWDM plus 10/100BaseTX Combo

P W/P W/P W

ETHERNET (Single slot) unprotected with a 2-slot 10/100BaseT ECM



[CEP\[EoPDH]]


W W W W

ETHERNET (Single slot) unprotected with a 2-slot Ethernet (Protection) ECM



[CEP\[EoPDH]]


O W/O W/O W



1 2 3 4 5 6

Operations and M

aintenance Guide, S

ection9: A


ard Placement

Page 9-18Force10 N

etworks

Release O

PS4.2.3

TDM 1:2 equipment protection with the corresponding ECM


W W/P W/P W



W/P W/P W/P W/P



W/P/O W/P/O W/P/O W/P/O


• DS1 • E1

W W W W



O W/O W/O W

TDM unprotected with a 3-slot DS3/E3 ECM (Note: the card placement restriction is due to the electrical connector card.)


O 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 W/P W/P W/P

OC-48/STM-16 with VTX2 W/P W/P W/P W/P



1 2 3 4 5 6

Appendix A

Module P

lacement P



ent

Release O

PS4.2.3Force10 N

etworks

Page 9-19

VT/VC Switching without Equipment Protection

VT/TU 5G Switch W W W W

OC-48/STM-16 with VTX W W W W


2 While the VTX Switch can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1 APS/MSP, UPSR/SNCP, or BLSR/MS-SPRing protection group.


If the 10/100BaseTX-inclusive card also contains optical ports. If the user intends to ONLY use the optical ports, this electrical port usage restriction does not apply.




1 2 3 4 5 6

Operations and M

aintenance Guide, S

ection9: A


ard Placement

Page 9-20Force10 N

etworks

Release O

PS4.2.3

Release OPS4.2.3 Force10 Networks Page 1

INDEX

Numerics1 for 1 equipment protection

module placement, 9-11 for 2 equipment protection

module placement, 9-11 for N equipment protection

module placement, 9-110/100BaseT

module placementprecaution statement, 8-19

10/100BaseTXmodule placement

precaution statement, 9-1port

performance monitoring, 2-71

AAccess

identifiertest access, 5-2, 5-5

Activatesoftware

protected modules, 7-29unprotected modules, 7-32

status, 7-22time, 7-20, 7-21, 7-23, 7-29, 7-35, 7-43, 7-68, 7-69,

7-70, 7-72type, 7-30

Activationstatus, 7-30, 7-69, 7-70

Activehop, 2-12, 2-14

Administrativestate

card or port, 4-19AID, see Access identifierAir

filtercooling function, 6-2replacement, 6-2

Alarmsavailability status

behavior, 1-13behavior

NSA/SA settings, 1-13categories, 1-2colors, 1-12

defaultseverity levels, 1-33, 4-2

definition, 1-1definitions, 1-12filter, 1-30generate

front inlet fan tray, 8-23, 8-33HP-SQM (port), 1-68list, 1-33

APSMM (port), 1-120APSWTR (MSP) (shelf), 1-134COM (TA200), 1-51COM (te50), 1-51DBCRPT, 1-52DBFAIL, 1-52DBMIS, 1-52DBRED, 1-52DBSIGN, 1-53DCCFAIL, 1-53DOWN, 1-54DQL, 1-54DS1AIS, 1-54DS1LOF, 1-54DS1LOS, 1-55DS1RAI, 1-55DS3AIS, 1-55DS3RAI, 1-55, 1-56DSR, 1-56DTR, 1-57E1AIS, 1-57E1LOMCAS, 1-57E1LOMCRC, 1-57E1RAI, 1-57E3 AIS, 1-57E3 RAI, 1-57EFMFAIL, 1-57ENGINE, 1-58ENGOPRG, 1-58EQCOMM, 1-58EQFRCSW, 1-58EQINV, 1-58, 1-120EQLOCK, 1-58EQMANSW, 1-58EQMIS, 1-59EQPT, 1-59EQRMV, 1-59ERFI-V, 1-59EXER_SWITCH, 1-60EXPLGS, 1-60

Page 2 Force10 Networks Release OPS4.2.3

EXTA-REF1-ALM, 1-60EXTA-REF2-ALM, 1-60EXTA-REF3-ALM, 1-60EXTA-REF4-ALM, 1-60EXTB-REF1-ALM, 1-61EXTB-REF2-ALM, 1-61EXTB-REF3-ALM, 1-61EXTB-REF4-ALM, 1-61FANCOMM, 1-61FANCOND, 1-61FANFLTR, 1-61FANRMV, 1-61FEP, 1-62FILE_UPLOAD, 1-62FIRDETR, 1-62FIRE, 1-62FLOOD, 1-62FOPR, 1-62FOPT, 1-62FORCE_ONLINE, 1-63FORCED, 1-63FORCED_ON_EAST, 1-64FORCED_ON_PROT, 1-63FORCED_ON_SECT1, 1-63FORCED_ON_SECT2, 1-64FORCED_ON_WEST, 1-64FORCED_ON_WORK, 1-64, 1-124FUSE, 1-64GENFAIL, 1-64GFPLOF, 1-65GIDERR, 1-65GIDM, 1-65H4-LOM, 1-65HIAIR, 1-65HIHUM, 1-65HITEMP, 1-66HIWTR, 1-66HP-BERSD, 1-67HP-BERSF, 1-67HP-LOM, 1-67HP-MND, 1-68HP-PLM, 1-68HP-RDI, 1-68HP-RFI, 1-68HP-RFICON, 1-68HP-RFIPAY, 1-69HP-RFISVR, 1-69HP-SQM, 1-68HP-TIM, 1-69HP-UNEQ, 1-69HWFAULT, 1-69IDLE, 1-69INCOMPATSW, 1-70

INDICATION, 1-70INTRUDER, 1-70KBYTE, 1-70LBC, 1-72LBCNRML, 1-72LCAS-INACTIVE, 1-72LCAS-REM, 1-72LCAS-RES, 1-72LEAK, 1-72LFD, 1-73LINKFAIL, 1-73LNKBCPTY, 1-73LNKBLKCNT, 1-73LOA, 1-75LOCK_WORK1, 1-75LOCK_WORK10, 1-75LOCK_WORK11, 1-76LOCK_WORK12, 1-76LOCK_WORK13, 1-76LOCK_WORK14, 1-76LOCK_WORK2, 1-76LOCK_WORK3, 1-76LOCK_WORK4, 1-77LOCK_WORK5, 1-77LOCK_WORK6, 1-77LOCK_WORK7, 1-77LOCK_WORK8, 1-77LOCK_WORK9, 1-77LOCKOUT, 1-75LOCKOUT-LPS, 1-75LOF, 1-78LOG, 1-79LOGINFAIL, 1-79LOGINSUCC, 1-79LOGINTERM, 1-79LOL, 1-79LO-LBC, 1-74LOM, 1-79LOM-P, 1-79LOM-V, 1-80LO-OPR, 1-74LO-OPT, 1-74LOP- VT, 1-81LOP-P, 1-80LOP-VC, 1-81LOS, 1-82LO-TEMP, 1-75LO-VCC, 1-75LP-BERSD, 1-82LP-BERSF, 1-83LPBKEQPT, 1-83LPBKFACILITY, 1-83LPBKINBAND, 1-84


LPBKTERM, 1-84LP-LOM, 1-84LP-MND, 1-84LP-PLM, 1-84LP-RDI, 1-85LP-RFI, 1-85LP-RFICON, 1-85LP-RFIPAY, 1-85LP-RFISVR, 1-85LP-SQM, 1-86LP-TIM, 1-86LP-UNEQ, 1-86LSDBOVFL, 1-86LSM, 1-86LWBATVG, 1-86LWFUEL, 1-86LWHUM, 1-86LWPRES, 1-86LWTEMP, 1-86LWWTR, 1-86MAN_ON_PROT, 1-87MAN_ON_WORK, 1-87MAN-TX-OFF, 1-87MAN-TX-ON, 1-87MANUAL, 1-87MAXAGE, 1-87MBD-P, 1-87MISC, 1-87MND (EoPDH), 1-87MND-V, 1-88MPU_BATTERY_A, 1-88MPU_BATTERY_B, 1-88MS-AIS, 1-88MS-BERSD, 1-89MS-BERSF, 1-89MS-RDI, 1-90MSSP_NOT_SYNC, 1-90MSSP_SYNC_UNKNOWN, 1-90MULT_PRIMARY_SERVER, 1-90NEIGHSC, 1-90NETSYNC, 1-90NEWLSA, 1-90NO_OUTPUT, 1-90NO_PRIMARY_SERVER, 1-90NODEEQMIS, 1-91NODEMIS, 1-91NODESYNC, 1-91NO-REMOTE-LCAS, 1-91NPM, 1-91OPENDR, 1-92OPR, 1-92OPT, 1-92OPTNORM, 1-92

ORPNORM, 1-92OVERTEMP, 1-92OVERVOLTAGE_A, 1-93OVERVOLTAGE_B, 1-93PCASQLCH, 1-93PDI-n, 1-93PKTRETX, 1-94PLC, 1-94PLCPLOF, 1-94PLCPRFI, 1-94PLCR, 1-94PLCT, 1-94PLINESQL, 1-94PLM, 1-95PLM-P, 1-95PLM-V, 1-95PLM-VC, 1-95PMCFG, 1-96PMDATALOST, 1-96POWER, 1-96PS, 1-96PUMPFAIL, 1-96PWFAIL-A, 1-96PWFAIL-B, 1-96PWR-48, 1-96QEFAIL, 1-96RAI, 1-97RECTFAIL, 1-97RECTHIGH, 1-97RECTLOW, 1-97REMOTE-LINKFAIL, 1-97RESOURCE_MISMATCH, 1-97RFICON, 1-100RFICON-V, 1-100RFICON-VC, 1-100RFI-L, 1-98RFI-P, 1-98RFIPAY, 1-101RFIPAY-V, 1-101RFIPAY-VC, 1-101RFISVR, 1-102RFISVR-V, 1-102RFISVR-VC, 1-102RFI-V, 1-99RFI-VC, 1-99RLSD, 1-103RMLF, 1-97RS-TIM, 1-103RTS, 1-103SENSORFAIL, 1-103SERVER_LOGINFAIL, 1-103SERVER_ROLE, 1-103SETOPER, 1-103


SFO, 1-104SFPMIS, 1-104SFPRMV, 1-104SHELFMIS, 1-104SMOKE, 1-104SQLCHTBL, 1-105SQM, 1-105SQM-P, 1-105SQM-V, 1-105SSF, 1-105SVC_ERROR, 1-106SW_UPG, 1-107SW_UPG_PROG, 1-107SWCRPT, 1-106SWERR, 1-106SWITCH, 1-106, 1-107SWITCH_TO_PROT, 1-106SWITCH_TO_SECT1, 1-106SWITCH_TO_SECT2, 1-107SWMIS, 1-107SYNCFAIL, 1-107SYSREF, 1-107SYSREF_EVENT, 1-107T2OOF, 1-118, 1-119T2XBIT, 1-118TA200_CLOCK, 1-118TA200_PM13E_G747FESmry, 1-118TA200_PM13E_G747OOFSmry, 1-118TCA, 1-108TE-206, 1-119TEMP, 1-108TEMPCRIT, 1-108TEMPWARN, 1-108TIM, 1-108TIMEDOUT, 1-109TIMEOUTWARN, 1-110TIM-P, 1-109TIM-S, 1-109TIM-V, 1-109TIU-V, 1-109, 1-110TLC, 1-110TLCR, 1-110TLCT, 1-110TOOMANYEVENTS, 1-110TOPOMIS, 1-110TOXIC, 1-110TSSALM, 1-114TSS-EXTA-OOB-A, 1-111TSS-EXTA-OOB-B, 1-111TSS-EXTB-OOB-A, 1-111TSS-EXTB-OOB-B, 1-111TSS-FRC, 1-111TSS-FREERUN-GCMA, 1-111

TSS-FREERUN-GCMB, 1-111TSSGEN, 1-114TSS-HOLDOVER-GCMA, 1-111TSS-HOLDOVER-GCMB, 1-111TSS-LINE1-OOB-GCMA, 1-112TSS-LINE1-OOB-GCMB, 1-112TSS-LINE2-OOB-GCMA, 1-112TSS-LINE2-OOB-GCMB, 1-112TSS-LINE3-OOB-GCMA, 1-112TSS-LINE3-OOB-GCMB, 1-112TSS-LINE4-OOB-GCMB, 1-112TSS-LOCK, 1-112TSS-MAN, 1-113TSSREF, 1-114TSS-REF1-ALM, 1-113TSS-REF2-ALM, 1-113TSS-REF3-ALM, 1-113TSS-REF4-ALM, 1-113TSS-REFL-GCMA, 1-113TSS-REFL-GCMB, 1-113TSS-REFS, 1-113TSSSETS, 1-114TSS-SSM, 1-113TU-AIS, 1-114TU-AIS (optical port), 1-37TU-LOP, 1-114TX-OFF-LI, 1-114TX-ON-LI, 1-114UNDERVOLTAGE_A, 1-115UNDERVOLTAGE_B, 1-115UNEQ, 1-115UNEQ-P, 1-115UNEQ-V, 1-116UNEQ-VC, 1-116UP, 1-116VCC, 1-116VENTFAIL, 1-116WARMREBOOT, 1-116WLMIS, 1-116X86_ABORT, 1-117X86_CRC, 1-117XPT-FAIL-RX, 1-117XPT-FAIL-TX, 1-117XPTRX, 1-117XPTTX, 1-117

managementcustomization, 1-15

profilecreation, 1-17DS1 port, 1-18DS3 port, 1-18DS3⁄EC3 port, 1-18E1 port, 1-18


E3 port, 1-18EOP ctp, 1-18EOP port, 1-18EOS ctp, 1-18EOS port, 1-18GbE port, 1-18LAG, 1-18Mux, 1-18probable cause, 1-16SDH EOS ctp, 1-18SDH EOS port, 1-18SDH high order path, 1-18SDH low order path, 1-18SDH port, 1-18server, 1-18shelf, 1-18SONET port, 1-18SONET sts, 1-18SONET vt, 1-18synchronize, 1-19TE50, 1-18

recommended actions, 1-33reporting, 1-2

hierarchy, 1-13settings, 1-10severity

default levels, 1-1sort by, 1-30

software upgradeSWMIS, 7-28

StickyMode, 1-31suppress

service CTP automatically, 1-24types, 1-2view, 1-13viewing, 1-28

Automatic in Serviceservice CTP path alarms

overview, 1-24Availability status

alarmdegrade, 1-13

BBackground

block errorsLO VC3 path, 2-50LO VC3 path, far end, 2-52SDH port–MS, 2-55SDH port–MS, far end, 2-56SDH port–RS, 2-53VC11 path, 2-59VC11 path, far end, 2-60

VC12 path, 2-59VC12 path, far end, 2-60VC3 path, 2-50VC3 path, far end, 2-52VC4 path, 2-50VC4 path, far end, 2-52

BackupsTE-206

manage from GUI, 6-30TE-206 nodes, 6-26

Backward compatibilitysoftware, 7-5, 7-55, 8-2

Base path, 7-11, 7-60Bulk service activation

unavailable resources, 1-140

CCapacity monitoring

intervals, 2-16parameters

SONET, 2-41print data, 2-16refresh values, 2-16samples, 2-16save data, 2-16SDH section parameters, 2-61SONET section, 2-41threshold crossing alert

number generated, 2-4VT/TU data

viewing, 2-16Captive fasteners

PDAP-2S, 6-13PDAP-4S, 6-19

Cardadministrative state, 4-19equipped state, 4-19GCM list, 8-14, 9-6operational state, 4-19optic, 8-12, 9-5placement

planning guidelines, 9-1protection

DS3/EC-1, 8-10, 9-2electrical, 8-9, 9-2Ethernet, 8-11, 9-3GCM, 8-9, 9-2UTMX, 8-10, 9-3

Circuit breakerPDAP-2S

replacing, 6-10toggle switch, 6-11

Cleaning MPX connectors, 8-15


Clearactivation time, 7-23, 7-70

CLIcommands

conventions, 6-24exec node database backup, 6-25exec node database restore, 6-25node, 6-23

Coding violationsDS1 port, 2-22line layer, far-end

EC1 port, 2-29SONET line layer, 2-32SONET line layer, far end, 2-33SONET path, 2-36SONET path, far end, 2-37SONET section layer, 2-31SONET VT path, 2-39SONET VT path, far end, 2-40

Colorsalarm

, 1-12Compatibility

alarms, 7-5, 7-55, 8-2product matrix, 7-5, 7-55, 8-2replacement modules, 7-5, 7-55, 8-2software, 7-5, 7-55, 8-2software version, 7-5, 7-55, 8-2

Connectors, cleaning, 8-15Corrected bits by forward error correction

SONET section layer, 2-31Corrected bytes by forward error correction

SONET section layer, 2-32Counter

resetting, see Performance monitoringCreate

alarm profiles, 1-17Current

SW version, 7-22, 7-23, 7-70, 7-71CVFE

coding violations, far end–line, 2-29

DDefault

alarm and event severity levels, 1-1, 1-33severities

alarms, 4-2DFAD, see Dual facility access digroupDiagnostics

alarm cut-off, 4-21environmental alarm conditions, 4-1LED lamp test, 4-21loopback tests, 4-11

power on self test, 4-21transmit and receive signal levels, 4-3, 4-7

Downloadarchive

from Force10 website, 7-4from Infocenter, 7-54

time by module, 7-13, 7-62DS1

portalarm profile, 1-18performance monitoring, 2-22

port, SDHperformance monitoring parameters, 2-22

DS3port

alarm profile, 1-18performance monitoring, 2-25

DS3/E3/EC-112-port, 8-9, 9-224-port, 8-9, 9-2card placement, 8-9, 9-2

DS3/EC-1Transmux, 8-9, 9-2

DS3⁄EC3port

alarm profile, 1-18Dual facility access digroup

test access point, 5-2

EE1

portalarm profile, 1-18facility loopback, 4-13facility loopback tests, 4-13performance monitoring, 2-44terminal loopback, 4-13

E3port

alarm profile, 1-18facility loopback, 4-13

tests, 4-13performance monitoring, 2-47terminal loopback, 4-13

EAM, see Environmental Alarm ModuleEC1

portperformance monitoring, 2-28

Electrostatic dischargeprotection, 8-4

EMSservice error codes, 1-137, 1-139


software compatibility, 8-2Endpoint

servicesCTP alarm suppression, 1-24

Environmentalalarm module

guides, 6-21plastic standoffreplacing, 6-20

alarmsobserving incorrect conditions, 4-1symptom, incorrect input/output, 4-2

EOPalarm profile

ctp, 1-18port, 1-18

EOSctp

alarm profile, 1-18performance monitoring

GFP FCS DISCARDS, 2-77, 2-79RX BROADCAST, 2-77, 2-78RX BYTES, 2-77, 2-78, 2-79RX FRAMES, 2-77, 2-78RX MTU DISCARDS, 2-77, 2-79RX MULTICAST, 2-76, 2-78RX UNICAST, 2-76, 2-78TX BROADCAST, 2-76, 2-78TX BYTES, 2-76, 2-78TX DISCARDS, 2-76, 2-77, 2-78, 2-79TX FRAMES, 2-76, 2-78TX UNICAST, 2-76, 2-78

portalarm profile, 1-18

Equipment protectionmodule placement

1 for 1, 9-11 for 2, 9-11 for N, 9-1

Equipped statecard or port, 4-19

Error codesEMS, 1-137service

EMS, 1-139Errored blocks

LO VC3 path, 2-49LO VC3 path, far end, 2-52SDH port–MS, 2-54SDH port–MS, far end, 2-55SDH port–RS, 2-53VC11 path, 2-58VC11 path, far end, 2-60

VC12 path, 2-58VC12 path, far end, 2-60VC3 path, 2-49VC3 path, far end, 2-52VC4 path, 2-49VC4 path, far end, 2-52

Errored secondsline layer, far end

EC1 port, 2-29LO VC3 path, 2-49

far end, 2-52SDH port–MS, 2-54

far end, 2-55SDH port–RS, 2-53SONET line layer, 2-32

far end, 2-33SONET path, 2-36SONET path, far end, 2-37SONET section layer, 2-31SONET VT path, 2-39

far end, 2-40VC11 path, 2-58




far end, 2-52Errors

show last, 1-139ESFE

errored secondsline layer, far end, 2-29

Ethernetdual-slot, 9-7, 9-12, 9-16LEDs, 3-9, 3-10module placement, 9-8performance monitoring

RX, 2-72RX BROADCAST, 2-71RX BYTES, 2-73, 2-74RX DELAY DISCARDS, 2-72RX DISCARDS, 2-72RX FCS ERR, 2-72RX FRAMES, 2-71RX MTU DISCARDS, 2-72RX MULTICAST, 2-71RX PAUSE, 2-73RX PKT > 1518, 2-72RX PKT 1024-1518, 2-72RX PKT 128-255, 2-72RX PKT 256-511, 2-72


RX PKT 512-1023, 2-72RX PKT 64, 2-72RX PKT 65-127, 2-72RX UNICAST, 2-71TX BROADCAST, 2-71TX BYTES, 2-73, 2-74TX DEFERRED FRAMES (10/100 only), 2-73TX DISCARDS, 2-72TX EXCESSIVE COLL (10/00 only), 2-73TX FRAMES, 2-71TX LATE COLL (T10/00 only), 2-73TX MULTICAST, 2-71, 2-76, 2-78TX MULTIPLE COLL (10/100 only), 2-73TX PAUSE, 2-73TX SINGLE COLL (10/100 only), 2-73TX UNICAST, 2-71

performance parameters, 2-63port

terminal loopbacks, 4-14protection ECM, 9-8unprotected with 10⁄100BaseT ECM, 9-8, 9-13, 9-17unprotected with Ethernet (protection) ECM, 9-8, 9-

13, 9-17Event

categories, 1-2default severity levels, 1-33filter

setting, 1-8list

detail view, 1-4grouping, 1-7new window, 1-4refresh, 1-4set filters, 1-4settings, 1-4sorting, 1-4

logserver output, 1-2

logs, 1-2recommended actions, 1-33reporting, 1-2settings, 1-10severity levels

default, 1-1tab

column order, 1-4types, 1-2

Eventsdefinition, 1-1

FFacility

access digroup

test access point, 5-2loopback

DS1, 4-12DS3, 4-12

payload loopbackE1, 4-13E3, 4-13

FAD, see Facility access digroupFailure counts

line layer, far endEC1 port, 2-30

LO VC3 path, 2-50LO VC3 path, far end, 2-52SDH port–MS, 2-55SDH port–MS, far end, 2-56SONET line layer, 2-33SONET line layer, far end, 2-34VC11 path, 2-59VC11 path, far end, 2-60VC12 path, 2-59VC12 path, far end, 2-60VC3 path, 2-50VC3 path, far end, 2-52VC4 path, 2-50VC4 path, far end, 2-52

Fanfan tray and module, 6-1maintenance

air filter, 6-2front inlet fan tray module, 6-1

speeds, 6-2tray

air filters, 6-2tray air filters

replacing, 6-2tray holder

inlet fan LEDs, 3-3tray module

replacing, 8-23, 8-29upgrade to FIFT, 8-33

Faultmanagement

customization, 1-15viewing alarms, 1-28

FCFE see Failure countsFiber optic

cabling, 8-16, 8-17Filter

airrole, 6-2

alarms, 1-30Force switch, 7-27, 7-31


Front inlet trayfan upgrade, 8-33

Fusereplacing

GMT, 6-9PDAP-2S, 6-9, 6-11PDAP-4S, 6-18

GGbE

portalarm profile, 1-18performance monitoring, 2-71

GCMalarm LEDs, 3-7list, 8-14, 9-6module placement, 9-7Power On Self Test (POST), 4-21redundancy rules, 8-14, 9-6status

active/standby, 7-20active⁄standby, 7-68protection, 7-20, 7-68

with VTX/VCX, 8-9, 9-2GFP

FCS DISCARDSEOS port, 2-77, 2-79

GMTfuse block

PDAP-2S, 6-11PDAP-4S, 6-18

replacing fusePDAP-2S, 6-11PDAP-4S, 6-18

GuidesEAM, 6-21PDAP-2S LED module, 6-14PDAP-4S LED module, 6-19

HHierarchy

alarms, 1-13

IInserting modules, 8-4Interval

capacity monitoring, 2-16performance monitoring, 2-10, 2-13

LLast error

show, 1-139LEDs

electrical module port, 3-8Ethernet, 3-9, 3-10fan tray holder

inlet, 3-3GCM

alarm, 3-7power and standby, 8-14

locations, 1-14, 3-4module

status, 3-1optical modules, 3-9PDAP, 3-2PDAP-2S, 3-2PDAP-4S, 3-2power and standby, 3-6statusvisual status

GCM start-up, 3-11Light emitting diodes, see LEDsLine

CVFE (coding violations, far end), 2-29FC (failure counts, far end)SESFE (severely errored seconds, far end), 2-29UASFE (unavailable seconds, far end), 2-30

LO VC3 pathperformance monitoring

BBE-LP, 2-50EB-LP, 2-49ES-LP, 2-49FC-LP, 2-50FE BBE-LP, 2-52FE EB-LP, 2-52FE ES-LP, 2-52FE FC-LP, 2-52FE SES-LP, 2-52FE UAS-LP, 2-52NPJC-DET-LP, 2-51NPJC-GEN-LP, 2-51PPJC-DET-LP, 2-51PPJC-GEN-LP, 2-51SES-LP, 2-50UAS-LP, 2-50

Loopbackfacility

DS1, 4-12DS3, 4-12

optical receiverpower restriction, 4-4

tests, 4-11description, 4-11E1 facility, 4-13


E1 terminal, 4-13E3 facility, 4-13E3 terminal, 4-13Ethernet terminal, 4-14facility

DS1 facility, 4-12DS3 CC, 4-12DS3 TMUX, 4-12DS3/EC-1, 4-12E1, 4-12E3, 4-12EC1, 4-12

SDH facility, 4-16SDH terminal, 4-16SONET facility, 4-16SONET terminal, 4-16terminal

DS1, 4-12DS3, 4-12DS3 CC, 4-12DS3 TMUX, 4-12EC1, 4-12

MMaintenance

alarm boardPDAP-2S, 6-13PDAP-4S, 6-19

fan trayair filter, 6-2air filter replacement, 6-2

fusePDAP-2S, 6-9, 6-11PDAP-4S, 6-18

replace circuit breakerPDAP-2S, 6-10

replacing EAM, 6-20routine, shelf, 6-1TPA fuse

PDAP-4S, 6-16Management

systemevent logs, 1-2login, 7-55verify software version, 7-17, 7-66, 8-3

MeasuredSFP optic port

supply voltage, 2-30, 2-80temperature, 2-30, 2-80TX bias current, 2-30, 2-80TX input power, 2-30, 2-80

TX output power, 2-30, 2-80Modules

GCM list, 8-14, 9-6inserting, 8-4placement

equipment protection, 9-1planning guidelines, 9-1

power and standby LEDs, 3-6replacing, 8-1, 8-33

preparations, 8-6required equipment, 8-4

softwaredownload times, 7-13, 7-62

software version compatibility, 7-5, 7-55, 8-2Monitoring

performance, 2-1signals

types, 2-1VT/TU capacity, 2-1

MPX connectorscleaning, 8-15cleaning material, 7-4, 8-4inspection, 8-15

Multiplex sectionperformance monitoring parameters, 2-54

Muxalarm profile, 1-18

NNegative pointer justifications detected

LO VC3 path, 2-51VC11 path, 2-59VC12 path, 2-59VC3 path, 2-51VC4 path, 2-51

Negative pointer justifications generatedLO VC3 path, 2-51VC11 path, 2-59VC12 path, 2-59VC3 path, 2-51VC4 path, 2-51

Nodeupgrade

see Upgrade

OOC-192

power restriction, 4-4Operational

statecard or port, 4-19


Opticcards, 8-12, 9-5module placement, 9-7

Opticalpower specifications, 4-4

PPassword, 7-12, 7-61Path

overheadview hop, 2-15

PDAP-15Areplace GMT fuse, 6-9

PDAP-2S see Power Distribution and Alarm Panelcaptive fasteners, 6-13circuit breaker, 6-11GMT

fuse block, 6-11LED

module, 6-14LEDs, 3-2replace circuit breaker, 6-10replacing

alarm board, 6-13PDAP-4S

see Power Distribution and Alarm Panelcaptive fasteners, 6-19GMT

fuse block, 6-18LED module guides, 6-19LEDs, 3-2replacing

alarm board, 6-19TPA fuse, 6-16

TPA fuse, 6-17Performance monitoring, 2-1

10/100BaseTX port, 2-71DS1 port, 2-22DS3 port, 2-25E1 port, 2-44E3 port, 2-47EC1 port, 2-28FE BBE_P

E1 port far end, 2-46FE EB_P

E1 port far end, 2-46E3 port near end, 2-48

FE ES_LE1 port far end, 2-44

FE ES_PE1 port far end, 2-46E3 port near end, 2-48

FE FC_PE1 port far end, 2-46

FE SES_PE1 port far end, 2-46E3 port near end, 2-48

FE UAS_PE1 port far end, 2-46E3 port near end, 2-48

GbE port, 2-71intervals, 2-10, 2-13NE AISS_P

E1 port near end, 2-45NE BBE_P

E1 port near end, 2-45NE BBER_P

E1 port near end, 2-45NE CV_L

E1 port near end, 2-44E3 port near end, 2-47

NE EB_PE1 port near end, 2-44, 2-47, 2-48

NE ES_LE1 port near end, 2-44E3 port near end, 2-47

NE ES_PE1 port near end, 2-45E3 port near end, 2-47

NE ESR_PE1 port near end, 2-45

NE FAS_LE1 port near end, 2-44

NE FC_LE1 port near end, 2-44

NE FC_PE3 port near end, 2-48

NE LOSS_LE1 port near end, 2-44E3 port near end, 2-47

NE SES_LE1 port near end, 2-44E3 port near end, 2-47

NE SES_PE1 port near end, 2-45E3 port near end, 2-47

NE SESR_PE1 port near end, 2-45

NE UAS_PE1 port near end, 2-45E3 port near end, 2-48

printing PM data, 2-11, 2-13refreshing PM values, 2-11, 2-13reports

generating, 2-17


resetting PM counterssamples, 2-10, 2-13saving data, 2-11, 2-13SDH path, 2-49, 2-58SDH port, 2-53services

SONET STS, 2-36SONET VT, 2-39

SONET port parameters, 2-31template

synchronize, 2-5templates

restriction, changing on service PM, 2-2, 2-8timing

refresh time, 2-9samples, 2-9

viewing port PM data, 2-10, 2-16viewing service PM data, 2-12, 2-14VT/TU capacity

viewing, 2-16Performance monitoring template

EOP port, 2-78EOP port member, 2-79Ethernet

service port, 2-74Performance parameters

Ethernet, 2-63SDH, 2-43SONET, 2-21

Periodic conditionsmonitoring, 2-1

Plastic standoff, see Environmental Alarm ModulePM

see Performance monitoringPort

administrative state, 4-19equipped state, 4-19operational state, 4-19

Positive pointer justifications detectedLO VC3 path, 2-51VC11 path, 2-59VC12 path, 2-59VC3 path, 2-51VC4 path, 2-51

Positive pointer justifications generatedLO VC3 path, 2-51VC11 path, 2-59VC12 path, 2-59VC3 path, 2-51VC4 path, 2-51

Powerrestriction

optical cards, 4-4

Power and standby LEDs, 3-6Power Distribution and Alarm Panel

alarm boardreplacing, 6-13

LEDs, 3-2replacing

circuit board, 6-19circuit breaker, 6-10TPA fuse, 6-16

Power On Self Test (POST) for GCM, 4-21Problems, see SymptomsProtected modules, 7-29Protection

card, 8-10, 9-3DS3/EC-1, 8-10, 9-2electrical, 8-9, 9-2Ethernet, 8-11, 9-3GCM, 8-9, 9-2

Ethernet, 8-12, 9-4groups, 7-29switch

forced, 7-27release, 7-27

Protection switchforced, 7-31release, 7-31

Protection switch countprotecting

SDH port–MS, 2-57SONET line layer, 2-35

workingSDH port–MS, 2-57SONET line layer, 2-34

Protection switch durationprotecting

SDH port–MS, 2-57SONET line layer, 2-35

workingSDH port–MS, 2-57SONET line layer, 2-34

RRecommended actions

alarms and events, 1-33non-alarmed symptoms, 4-2

Refreshing PM values, 2-11, 2-13Regenerator section

performance monitoringEB-RS, 2-53ES-RS, 2-53SES-RS, 2-53

performance monitoring parameters, 2-53Release path, 7-14, 7-63


Release protection switch, 7-27, 7-31Remote test access, 5-3Replacing

alarm boardPDAP-2S, 6-13PDAP-4S, 6-19

cardsrequired equipment, 7-4

circuit breakerPDAP-2S, 6-10

EAM circuit board, 6-20fan tray module, 8-23, 8-29fuse

PDAP-2S, 6-9, 6-11PDAP-4S, 6-18

GCMpower and standby LEDs, 8-14

modules, 8-1, 8-4, 8-33compatibility, 7-5, 7-55, 8-2required equipment, 7-54, 8-4, 8-34

Reports, see also AlarmsReports, see also EventsResetting counters, see Performance monitoringRTU, see Remote test unitRX

Ethernet port, 2-72RX BROADCAST

EOS port, 2-77, 2-78Ethernet port, 2-71

RX BYTESEOS port, 2-77, 2-78, 2-79Ethernet port, 2-73, 2-74

RX DELAY DISCARDSEthernet port, 2-72

RX DISCARDSEthernet port, 2-72

RX FCS ERREthernet port, 2-72

RX FRAMESEOS port, 2-77, 2-78Ethernet port, 2-71

RX MTU DISCARDSEOS port, 2-77, 2-79Ethernet port, 2-72

RX MULTICASTEOS port, 2-76, 2-78Ethernet port, 2-71

RX PAUSEEthernet port, 2-73

RX PKT > 1518Ethernet port, 2-72

RX PKT 1024-1518Ethernet port, 2-72




RX PKT 64Ethernet port, 2-72


RX UNICASTEOS port, 2-76, 2-78Ethernet port, 2-71

SSDH

alarm profileHO path, 1-18LO path, 1-18port, 1-18

pathperformance monitoring, 2-49, 2-58


facility loopback tests, 4-16terminal loopback tests, 4-16

SDH portperformance monitoring, 2-53

Securitymonitoring

administrative use, 1-33administrative use, events, 1-1PM information, not collecting, 2-1, 2-21, 2-43,

2-63Self test, GCM

see GCM, Power On Self TestServer alarm profile, 1-18Server IP address, 7-11, 7-60Service

performance monitoringSONET VT, 2-39

performance monitoring SONET STS, 2-36Service error codes

EMS, 1-139system resources unavailable (1035), 1-140

SESFEseverely errored seconds, far end–line, 2-29

Severely errored framing secondsSONET section layer, 2-31

Severely errored secondsline layer, far end

EC1 port, 2-29LO VC3 path, 2-50


LO VC3 path, far end, 2-52SDH port–MS, 2-54SDH port–MS, far end, 2-56SDH port–RS, 2-53SONET line layer, 2-32SONET line layer, far end, 2-34SONET path, 2-36SONET path, far end, 2-38SONET section layer, 2-31SONET VT path, 2-39SONET VT path, far end, 2-40VC11 path, 2-58VC11 path, far end, 2-60VC12 path, 2-58VC12 path, far end, 2-60VC3 path, 2-50VC3 path, far end, 2-52VC4 path, 2-50VC4 path, far end, 2-52

SeverityNSA, 1-16SA, 1-16

Severity levelsalarm and event

defaults, 1-1, 1-33defined, 1-12

SFP optic portperformance monitoring

measured supply voltage, 2-30, 2-80measured temperature, 2-30, 2-80measured TX bias current, 2-30, 2-80measured TX input power, 2-30, 2-80measured TX output power, 2-30, 2-80

Shelfalarm profile, 1-18

Showlast error, 1-139

Signalmonitoring, 2-1

Softwareactivation, 7-29compatibility, 7-5, 7-55, 8-2download

abort, 7-15, 7-64clear, 7-15, 7-64status, 7-15, 7-64

download times, 7-13, 7-62upgrade, 7-1, 7-53

activate GCM, 7-20, 7-24, 7-34, 7-35, 7-43, 7-68, 7-72

activate time, 7-21, 7-23, 7-29, 7-69, 7-70hitless warm reboot, 7-8status, 7-15, 7-64

upgrade order, 7-29upgrade type

initiate, 7-14, 7-63version

current, 7-17, 7-30, 7-66, 8-3standby, 7-16, 7-65verify, 7-17, 7-66, 8-3

SONETcapacity monitoring parameters, 2-41line layer

performance monitoring parameters, 2-32performance monitoring, port parameters, 2-33

performance monitoringpath parameters, 2-36

performance monitorngVT path, 2-39


alarm profile, 1-18facility loopback tests, 4-16performance monitoring parameters, 2-31terminal loopback tests, 4-16

section layerperformance monitoring parameters, 2-31

STSalarm profile, 1-18

VTalarm profile, 1-18

Speedcooling fan, 6-2

Standbyhop, 2-12module, 7-40, 7-41

Start-upLED

GCM visual status, 3-11Status

activation, 7-22, 7-69, 7-70time, 7-30

GCM protection, 7-20, 7-68StickyMode, see AlarmsSymptoms

incorrect environmental alarms, 4-2recommended actions, 4-2

System resourcesunavailable, 1-140

TTabs

events, see Event tabTAC, see Test access cross-connectTAP, see Test access point


TE-206list

alarms, 1-119events, 1-119

TE50alarm profile, 1-18

Termination pointTP, test access, 5-2

Test Accesstest system controller (TSC), 5-23

Test access, 5-5ADM, 5-1AID, 5-2cross-connect, 5-2DCS3/1, 5-1digital signals, 5-1DS1 module, 5-8DS3 module, 5-8DS3 transmux module, 5-8dual facility access digroup, 5-2E1 module, 5-8facility access digroup, 5-2intrusive, 5-1management system, 5-8monitor, 5-9non-intrusive, 5-1OC-N/STM-N, 5-8per side split, 5-13point, 5-2remote test access, 5-3remote test unit, 5-2series split, 5-17termination point, 5-2test system controller, 5-2VCX component, 5-8VT/TU 5G switch, 5-8

Test system controller, 5-2TSC, 5-23

Threshold crossing alertcapacity monitoring

number generated, 2-4Thresholds

capacity parameter settings, 2-4PM parameter settings, 2-4

Toggle switchPDAP-2S circuit breaker, 6-11

TPtermination point, test access, 5-2

TPA fusePDAP-4S, 6-17

Transmit and receive signal levels, 4-3, 4-7Transmux

DS3/EC-1, 8-9, 9-2

UTMX-24, 8-9, 9-2UTMX-48, 8-9, 9-2

Troubleshootingerror codes, 1-137loopback tests, 4-11transmit and receive signal levels, 4-3, 4-7

troubleshooting, 4-11TSC, see Test access test system controllerTX BROADCAST

EOS port, 2-76, 2-78Ethernet port, 2-71

TX BYTESEOS port, 2-76, 2-78Ethernet port, 2-73, 2-74

TX DEFERRED FRAMESEthernet port (T10/00 only), 2-73

TX DISCARDSEOS port, 2-76, 2-77, 2-78, 2-79Ethernet port, 2-72

TX EXCESSIVE COLLEthernet port (10/100 only), 2-73

TX FRAMESEOS port, 2-76, 2-78Ethernet port, 2-71

TX LATE COLLEthernet port (10/100 only), 2-73

TX MULTICASTEthernet port, 2-71, 2-76, 2-78

TX MULTIPLE COLLEthernet port (10/-100 only), 2-73

TX PAUSEEthernet port, 2-73

TX SINGLE COLLEthernet port (10/00 only), 2-73

TX UNICASTEOS port, 2-76, 2-78Ethernet port, 2-71

UUASFE

unavailable secondsfar end, line, 2-30

Unavailable secondsline layer, far-end

EC1 port, 2-30LO VC3 path, 2-50LO VC3 path, far end, 2-52SDH port–MS, 2-54SDH port–MS, far end, 2-56SONET line layer, 2-33SONET line layer, far end, 2-34SONET path, 2-36SONET path, far end, 2-38


SONET VT path, 2-39SONET VT path, far end, 2-40VC11 path, 2-59VC11 path, far end, 2-60VC12 path, 2-59VC12 path, far end, 2-60VC3 path, 2-50VC3 path, far end, 2-52VC4 path, 2-50VC4 path, far end, 2-52

Upgradesoftware, 7-1

TE-100, 7-53Traverse node, 7-1

tray fanfront inlet, 8-33

Username, 7-12, 7-61UTMX, 8-10, 9-3

Transmux, 8-9, 9-2

VVC11 path

performance monitoring, parameters, 2-58VC12 path

performance monitoring, parameters, 2-58VC3

pathperformance monitoring parameters, 2-49, 2-51

VC4path

performance monitoring parameters, 2-49, 2-51Viewing

alarms, 1-13, 1-28all nodes, 1-28card, 1-28one node, 1-28port, 1-28service CTP, 1-28

PM dataport, 2-10, 2-16service, 2-12, 2-14

VT/TU Switchcard placement, 8-13, 9-5

WWarm reboot

hitless software upgrade, 7-8

Documents

Traverse Operations Guide - Force10 · 2010-03-12 · Operations and Maintenance Guide, Section 1: Fault Management Event List on the Events Tab Page 1-4 Force10 Networks Release