Traverse Operations Documentation. Operations and Maintenance Guide

Transcription

1 Force10 Networks Inc. Traverse Operations Documentation Operations and Maintenance Guide Release OPS4.2.2 Publication Date: April 2009 Document Number: OPS422 Rev. A

2 Copyright 2009 Force10 Networks, Inc. All rights reserved. Printed in the U.S.A. April Force10 Networks reserves the right to change, modify, revise this publication without notice. Trademarks Force10 Networks, and 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 Conditions In the interest of improving internal design, operational function, and/or reliability, Force10 Networks reserves the right to make changes to products described in this document without notice. Force10 Networks does not assume any liability that may occur due to the use or application of the product(s) described herein.

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

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

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

6 Operations and Maintenance Guide, Section 1 Fault Management Chapter 2 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, TA Alarms/Events, TE Chapter 3 TransNav GUI Service Error Codes Service Activation Failure TransNav GUI Service Error Codes Page ii Force10 Networks Release OPS4.2.2

7 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 Network alarms display at the network Map View level or Network level on the navigation tree. Alarms for node groups display the number of alarms for each group, including the node groups and nodes contained in that group. Events Events (other than alarm fault events) are state-less alerts indicating configuration changes, operator actions, performance changes, and other standard operations. If a card (module) does not appear to generate events, contact the System Administrator. The card may be reserved for administrative use. Alarms Alarms are fault events indicating abnormal single-state or multi-state conditions requiring system operator attention. A single-state condition example is a hardware device failure. The hardware device is either in the failed condition or not. Each alarm is characterized by alarm severity, service affecting status, and whether the alarm is active or clear. If a condition persists, the alarm is active. If the fault condition is resolved, either automatically or by operator action, the alarm is clear. This chapter provides information on: Event Types, page 1-2 Event Logs, page 1-2 Events Tab, page 1-3 Alarms Tab, page 1-4 Network Alarm Summary Window, page 1-5 Customizing Alarms, page 1-7 Suppressing Alarms, page 1-13 Viewing Alarms, page 1-16 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 while working with this product. Release OPS4.2.2 Force10 Networks Page 1-1

8 Operations and Maintenance Guide, Section 1: Fault Management Event Types Event Types Event Logs Events alert the operator to changes to the system. Each of these changes are logged and can be any one of the following event types: Provisioning events. The node has made a change to its configuration in response to a request from a management entity. Performance events. The value of a Performance Management (PM) parameter has crossed a provisioned threshold. This threshold crossing alert (TCA) may indicate service deterioration and require operator attention. Security events. A user has logged in or out of the node, an attempted login has failed, or a user has made some change to the user account database. Normal operational events. Normal and expected occurrences, such as initialization completed or control plane connection established with other nodes. They are logged for information only. Fault events (alarms). Fault conditions that may affect service and require operator attention. Fault events generate and clear 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). 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. 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 GUI Guide, Section 2 Management Server Procedures, Chapter 3 Server Administration Procedures, Setting Up Report Parameters, page 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 4 Generating and Viewing Reports, Generating Reports, page Page 1-2 Force10 Networks Release OPS4.2.2

9 Chapter 1 Managing Alarms and Events Events Tab Events Tab The TransNav GUI Events tab displays a list of events for users to quickly view and analyze state-less alerts. Figure 1-1 Map View, Events Tab Release OPS4.2.2 Force10 Networks Page 1-3

10 Operations and Maintenance Guide, Section 1: Fault Management Alarms Tab Alarms Tab The TransNav GUI Alarms tab displays a list of alarms for users to quickly view, analyze, and resolve fault conditions. If a node or group is in an alarm state, it displays on the Map View object in the color of the highest level alarm severity with a caption indicating the number and type of alarm. (Groups display the color of the most severe alarm present in the nodes or groups within that group.) For example, in Figure 1-2 the node TE100SIGTWO has four critical (4C) alarms, so it is colored red with the caption 4C. The + indicates other alarms exist at a lower severity. For alarms tab definitions, refer to: Alarm Severity Levels, page 1-5 Alarm Hierarchy, page 1-6 Customizing Alarms, page 1-7 Map View Display Alarm Caption Node Object Alarms List StickyMode View Selector Alarms Tab Sort by Column Detail View Set Filters New Window Command Command Command Print Command Save Command Figure 1-2 Alarms Tab Page 1-4 Force10 Networks Release OPS4.2.2

11 Chapter 1 Managing Alarms and Events Alarm Severity Levels Network Alarm Summary Window The TransNav network alarm summary window shows counts of outstanding Critical (C), Major (M), Minor (m) alarms, and Warnings (W). Alarm Summary Figure 1-3 Network Alarm Summary Window Network alarms display at the network Map View level or network level on the navigation tree. Groups display the number of alarms for each group, including the groups and nodes contained in that group. To view node group alarms, click the group in the navigation tree or go to the Group Map of the group. Service Affecting Status Alarm Severity Levels Two levels of service affecting status are used in the alarm definitions: Service Affecting (SA): Indicates that a service affecting condition has occurred and an immediate corrective action is required. Non-Service Affecting (NSA): Indicates that a non-service affecting condition has occurred. Service affecting alarms apply when protection is not available. This same alarm is considered non-service affecting if the equipment or facility is protected. Alarms listed as non-service affecting do not affect service regardless of equipment or facility protection scheme. Some alarms are always service affecting, some are always non-service affecting, and some can be either, depending on the circumstances. 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: Critical (red): A severe, service affecting condition has occurred. Immediate corrective action is imperative, regardless of the time of the day or day of the week. Major (orange): A hardware or software condition has occurred that indicates a serious disruption of service or the malfunctioning or failure of important circuits. This requires the immediate attention and response of a technician to restore or maintain system capability. The urgency is less than in critical situations because of a lesser immediate or impending effect on service or system performance. Release OPS4.2.2 Force10 Networks Page 1-5

12 Operations and Maintenance Guide, Section 1: Fault Management Alarm Hierarchy Minor (yellow): Trouble has occurred that does not have a serious effect on service to customers or trouble in circuits has occurred that is not essential to node operation. Corrective action should be taken in order to prevent a more serious fault. Warning (cyan/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 Hierarchy Traverse Card LEDs This system conforms to the alarm reporting hierarchy set forth in the Telcordia General Requirements GR-253, ETSI , and ITU recommendation G.783. The locations of common and specific card LEDs is shown in the following graphic. PWR (Power) ACTV/ STNBY (Active/Standby) DS1, DS3/E3, E1, OC-N/STM-N and ETH Port Indicators Alarms: CRITICAL/MAJOR MINOR ACO ON ACO Optical Port Timing: LOCKED/ UNLOCKED FREE RUN/ HOLDOVER ETHERNET LINK OSS and Craft 10/100BaseT Ethernet Interface (RJ-45) RS-232 Interface (DB-9) DS1 DS3/E3 E1 OC-N/ STM-N VT Switch Ethernet EGCM OPS Figure 1-4 Physical Card LEDs Page 1-6 Force10 Networks Release OPS4.2.2

13 Chapter 1 Managing Alarms and Events Alarm Profiles Customizing Alarms Alarm Profiles The TransNav GUI provides functions for creating new, modifying default, and assigning alarm profiles in order to customize alarm parameter settings (e.g., severity level) based on your network requirements. Refer to the following topics: Alarm Profiles, page 1-7 Creating a New Alarm Profile, page 1-8 Assigning a Port Alarm Profile, page 1-10 Alarm profiles allow users to customize alarms based on severity, service affecting status, and whether to enable or disable (suppress) alarm generation. Note: Create EC-3/STM-1E alarm profiles with the SONET/SDH templates, like that for the OC-3/STM-1 ports. Sort by Column Figure 1-5 Alarm Profile Dialog Box Click a column heading to sort the alarms by that category. The Name and Probable Cause columns can be sorted in alphabetical or reverse alphabetical order. The Severity NSA and Severity SA columns can be sorted in ascending or descending severity. The ServiceAffecting and Enabled columns can be sorted by select/clear. Click the column heading again to switch from one sorting category to the other. Release OPS4.2.2 Force10 Networks Page 1-7

14 Operations and Maintenance Guide, Section 1: Fault Management Creating a New Alarm Profile Creating a New Alarm Profile The following procedure describes how to create an Alarm Profile template. Table 1-1 Creating a New Alarm Profile Step Procedure 1 In Map View, from the Admin menu, click Alarm Profiles. Figure 1-6 Alarm Profiles Dialog Box Page 1-8 Force10 Networks Release OPS4.2.2

15 Chapter 1 Managing Alarms and Events Creating a New Alarm Profile Table 1-1 Creating a New Alarm Profile (continued) Step Procedure 2 From the Type drop-down list, select the type of alarm profile you want to create: ds1_ptp: SONET DS1 port ds3_ptp: SONET DS3/EC1 ports (previously called ds_ptp) e1_ptp: SDH E1 port e3_ptp: SDH E3 port eos: SONET EOS port eos_ctp: SONET EOS connection termination point ethernet_ptp: Ethernet port lag: (Ethernet) Link aggregated group sdh_eos: SDH EOS port sdh_eos_ctp: SDH EOS connection termination point sdh_hp: SDH high order path (VC4 or VC3) sdh_lp: SDH VC3 low order path sdh_ptp: SDH port server: TransNav server platform shelf: Traverse or TraverseEdge node sonet_ptp: SONET port sonet_sts: SONET STS path sonet_vt: SONET VT path ta200: TransAccess 200 Mux 3 Click Add to view the alarm profile, then enter a Name for the alarm profile. The example shown below is an ethernet_ptp alarm profile with default values. Figure 1-7 Alarm Profile Dialog Box Release OPS4.2.2 Force10 Networks Page 1-9

16 Operations and Maintenance Guide, Section 1: Fault Management Assigning an Alarm Profile Table 1-1 Creating a New Alarm Profile (continued) Step Procedure 4 To modify the alarm entry settings, make a selection from the drop-down list or check the box in the row of the following columns: Severity NSA: Alarm severity when it is non-service affecting. Severity SA: Alarm severity when it is service affecting; this severity only applies if ServiceAffecting is selected. ServiceAffecting: Select to make the alarm service affecting. Clear the checkbox to make the alarm non-service affecting. Enabled: Select to enable the alarm. Clear to disable the alarm. Click OK. A user prompt appears. 5 Click Yes to synchronize the alarm profile to make it available to other nodes. Click No if you do not want to synchronize the new template. 6 Click Done in the Alarm Profiles dialog box. 7 The Creating a New Alarm Profile procedure is complete. Assigning an Alarm Profile Assigning a Port Alarm Profile Choose one of the following topics by object type (e.g., port) to assign an alarm profile: Assigning a Port Alarm Profile, page 1-10 Assigning a Subport Alarm Profile, page 1-11 Assigning a Service Path Alarm Profile, page 1-11 The following procedure describes how to assign a port alarm profile template to a port. Table 1-2 Assigning a Port Alarm Profile Step Procedure 1 In Shelf View, select a 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. Page 1-10 Force10 Networks Release OPS4.2.2

17 Chapter 1 Managing Alarms and Events Assigning a Service Path Alarm Profile Assigning a Subport Alarm Profile The following procedure describes how to assign a port alarm profile template to a DS3 Transmux subport. Table 1-3 Assigning a Subport Alarm Profile Step Procedure 1 In Shelf View, select a DS3 Transmux card port. 2 Click the Config tab. 3 From the Subport row, Alarm Profile column list, select a port (ptp) alarm profile template matching the embedded signal subport type (e.g., ds1_ptp). 4 Click Apply. 5 The Assigning a Subport Alarm Profile procedure is complete. Assigning a Service Path Alarm Profile The following procedure describes how to assign a path alarm profile template to a service connection termination point (CTP) within an end-to-end transport path. Table 1-4 Assigning a Service Path Alarm Profile Step Procedure 1 From any view, click the Service tab. Figure 1-8 Service Tab 2 Select a service. Right-click and select Show TxRx Path to display the Path Display for Services screen. Release OPS4.2.2 Force10 Networks Page 1-11

18 Operations and Maintenance Guide, Section 1: Fault Management Assigning a Service Path Alarm Profile Table 1-4 Assigning a Service Path Alarm Profile (continued) Step Procedure 3 Click the CTP tab to display the CTP dialog box. 3 Figure 1-9 Path Display for Services Screen 4 From the Path Display for Service screen, Tx or Rx table row, select an Active Hop. Your selection displays in the EndPoint field of the CTP screen. Page 1-12 Force10 Networks Release OPS4.2.2

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

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

21 Chapter 1 Managing Alarms and Events Service CTP Path Alarm Suppression Table 1-6 Suppress Service CTP Path Alarms (continued) Step Procedure 3 Select a service. Right-click and select Show TxRx Path to display the Path Display for Services screen. 3 5a 4 5b 6 7 Figure 1-11 Path Display for Services Screen 4 Click the CTP tab to display the CTP screen. 5 From the Path Display for Service screen, Tx or Rx table row, select an Active Hop (5b). Your selection inserts into the EndPoint field in the CTP screen (5b). 6 Click the Lock icon at the bottom left portion of the screen (6) to change the administrative state to locked. 7 Click Apply (7). 8 The Suppress Service CTP Path Alarms procedure is complete. Release OPS4.2.2 Force10 Networks Page 1-15

22 Operations and Maintenance Guide, Section 1: Fault Management Viewing Alarms Viewing Alarms The TransNav GUI displays alarm information for users to view, analyze, and resolve fault conditions quickly. The alarms shown can be for different levels of object granularity: by node group (includes all the nodes and groups within that group) all nodes, one node, a card, a port, or a service connection termination point (CTP) within an end-to-end transport path. Note: If a map for a group is displayed, only the alarms for nodes within that group display in the alarm summary list. The following procedure describes how to view alarms described in Figure 1-2. Table 1-7 Viewing Alarms Step Procedure 1 Which alarms to view? All nodes. In Map View, click the Alarms tab to view the alarm list and functions. Go to Step 3. Node. In Map View, select a node. Card. In Shelf View, select a card. Port. In Shelf View, select a port. Service CTP. Click the Services tab. Right-click on a service and select Show TxRx Path. Select an Active Hop. 2 Click the Alarms tab to view the alarm list and functions. 3 Choose one (or more) of the following viewing functions: Alarm Tallies, go to the next step Detail View, go to Step 5 Map View Display, go to Step 7 New Window, go to Step 8 Print, go to Step 9 Save, go to Step 10 Set Filters, go to Step 11 Sort by Column, go to Step 12 StickyMode, go to Step 13 4 Alarm Tallies Look in the lower-left corner of the Alarms tab to see the alarm tallies as follows: Raised Alarms: The number of alarms raised by the system. Displayed Alarms: The number of alarms in the display list. Go to Step Detail View From the alarm list, select an alarm. Page 1-16 Force10 Networks Release OPS4.2.2

23 Chapter 1 Managing Alarms and Events Viewing Alarms Table 1-7 Viewing Alarms (continued) Step Procedure 6 Click Detail View to display the Alert Detail (View Main) dialog box and view highlighted alarm details. Go to Step Map View Display The Map View displays in the upper half of the GUI screen. If a node is in an alarm state, it displays on the Map View node object in the color of the highest level alarm severity with a caption indicating the number and type of alarm. For example, in Figure 1-2, the node TE100SIGTWO has four critical (4C) alarms, so it is colored red with the caption 4C. The + indicates other alarms exist at a lower severity. For definitions of the severity levels, see Alarm Severity Levels, page 1-5. Go to Step New Window From the Alarms tab, click New Window to open a new alarm window. Note: Multiple alarm windows can be opened, each with independently configurable filters. Go to Step Print Click Print to print the contents of the Alarms tab alarms list. Go to Step Save Click Save to save alarm information to a text file. Go to Step 14. Release OPS4.2.2 Force10 Networks Page 1-17

24 Operations and Maintenance Guide, Section 1: Fault Management Viewing Alarms Table 1-7 Viewing Alarms (continued) Step Procedure 11 Set Filters From the Alarms tab, click Set Filters to set the alarm filters. Note: Alarms can be filtered by Source, Probable Cause, Time, Severity, and Acknowledged By categories. Go to Step 14. Figure 1-12 Alarm Filter Dialog Box 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. Page 1-18 Force10 Networks Release OPS4.2.2

25 Chapter 1 Managing Alarms and Events Viewing Alarms Table 1-7 Viewing Alarms (continued) Step Procedure 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. Release OPS4.2.2 Force10 Networks Page 1-19

26 Operations and Maintenance Guide, Section 1: Fault Management Viewing Alarms Page 1-20 Force10 Networks Release OPS4.2.2

27 SECTION 1 SECTION 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, TA200 Alarms/Events, TA200 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 Release OPS4.2.2 Force10 Networks Page 1-21

28 Operations and Maintenance Guide, Section 1: Fault Management inputs and outputs are supported by the optional Environmental Alarm Module (EAM) located on the main backplane. These alarms are defined using the TransNav management system. Refer to the Traverse Installation and Commissioning Guide or the TraverseEdge 100 User Guide for details on environmental alarm connections. Note: For Loss of Signal alarms, see the information in Section 4 Diagnostics, Chapter 2 Traverse Transmit and Receive Signal Levels, page 4-3 or Chapter 3 TraverseEdge 100 Transmit and Receive Signal Levels, page 4-7. Contact the Force10 Technical Assistance Center (TAC) if you need assistance. Page 1-22 Force10 Networks Release OPS4.2.2

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

30 Page 1-24 Force10 Networks Release OPS4.2.2 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition AIS-P: Alarm indication signal Path AIS-P-TX: Alarm indication signal Path, Transmit AIS-S 1 : Alarm indication signal Service Alarm Profiles ds3_ptp (ds_ptp) e3_ptp ta200 te50 sonet_ptp sonet_sts te206 node te206 node ds3_ptp (ds_ptp) e3_ptp sdh_ptp sonet_ptp sonet_service Probable Cause The STS signal demultiplexed from the DS3 or EC-1 contains an AIS. This AIS can result from an upstream failure along the STS path. The STS signal demultiplexed from the OC-N/STM-N contains an AIS. This AIS can result from an upstream failure along the STS path. 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. An upstream failure occurred at the Service layer. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical Check the equipment (module/port) upstream. Clear upstream alarms. Verify your payload connections. SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your payload connections. SA Critical Minor Check the equipment upstream. Clear downstream alarms. Verify your payload connections. Warning Info Check the equipment upstream. Clear upstream alarms. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

31 Release OPS4.2.2 Force10 Networks Page 1-25 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition AIS-V 1 : Alarm indication signal VT AIS-VC: Alarm indication signal - VC ALS: Automatic laser shutdown ALS-TX-OFF: Transmitter automatically disabled APS-AIS-P 1 : Automatic protection ( multiplex section protection - MSP) Administrative Unit switching Alarm Indication Signal Path Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sonet_ptp sonet_vt sonet_sts te206 node ta200 te50 An upstream failure occurred at the VT path layer. An upstream failure occurred at the VT path layer. SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your VT payload connections. SA Critical Critical Check the equipment upstream. Clear upstream alarms. Verify your VT payload connections. sdh_ptp See TU-AIS. n/a n/a n/a See TU-AIS. e1_ptp sdh_ptp ethernet_ptp sdh_ptp sonet_ptp ethernet_ptp sdh_ptp sonet_ptp shelf Probable Cause An upstream failure occurred at the VC path layer. Transmitter of the optical interface has been turned off automatically after detection of LOS on the receiver. Event logged against the optical interface upon ALS alarm condition. A protection switch has occurred due to an AIS-P alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your VC payload connections. Critical Minor Transmitter has been shutdown per G.664. Check remote port transmitter state and fiber and resolve LOS condition. Info Info (Informational; no action required.) Info Info See AIS-P. Recommended Action Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

32 Page 1-26 Force10 Networks Release OPS4.2.2 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APS-LOP-P 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Pointer Path APS-SDBER-P 1 : Automatic protection switching (multiplex section protection - MSP) Signal Degrade Bit Error Rate Path APS-SFBER-P 1 : Automatic protection switching (multiplex section protection - MSP) Signal Fail Bit Error Rate Path APS-UNEQ-P 1 : Automatic protection switching (multiplex section protection - MSP) Unequipped (High Order) Path APSAISCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Alarm Indication Signal Clear APSB: Automatic protection switch (multiplex section protection - MSP) byte failure APSBF: Automatic protection switch byte failure APSCFGMIS: Automatic protection switch (multiplex section protection - MSP) configuration mismatch Alarm Profiles shelf shelf shelf shelf shelf sonet_ptp sdh_ptp sonet_ptp sdh_ptp te206 node sonet_ptp sdh_ptp Probable Cause A protection switch has occurred due to an LOP-P alarm. A protection switch has occurred because of an SDBER-P alarm. A protection switch has occurred because of an SFBER-P alarm. A protection switch has occurred because of an UNEQ STS path alarm. A protection switch which occurred because of an AIS alarm has been cleared. 1+1 linear APS reports this alarm if the bidirectional mode is set and the APS K1/K2 bytes are in an invalid state. 1+1 linear APS reports this alarm if bidirectional mode is set and K2 bits 6-8 are any of these values: 0,1,2,3. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info See LOP-P. Info Info See SDBER-P. Info Info See SFBER-P. Info Info See UNEQ-P. Recommended Action Info Info If frequent protection switching occurs, check the revertive WTR period setting. Minor Minor Check for OC-N module failures. Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes. Minor Minor Check that the fiber is connected properly to the remote node. Check that a remote 1+1 linear PG exists. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

33 Release OPS4.2.2 Force10 Networks Page 1-27 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APSCM: Automatic protection switch (multiplex section protection - MSP) channel mismatch APSIMP: Improper automatic protection switching (multiplex section protection - MSP) code APSINC: Inconsistent automatic protection switching (multiplex section protection - MSP) code APSLOPCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Pointer Clear APSLOS 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Signal Alarm Profiles sonet_ptp sdh_ptp te206 node sonet_ptp sdh_ptp sonet_ptp sdh_ptp shelf shelf Probable Cause 1+1 linear APS reports this alarm if the bidirectional mode is set and the APS K1/K2 bytes are in an invalid state. 1+1 linear APS reports this alarm if the bidirectional mode is set and the APS K1/K2 bytes are in an invalid state.. On a 2F BLSR, the automatic protection switching codes are inconsistent. Three consecutive frames do not contain identical APS bytes, giving the receiving equipment conflicting commands about switching. A protection switch that occurred because an LOP-P alarm has been cleared. A protection switch has occurred because of an LOS alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Minor Minor Check for OC-N module failures. Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes. Minor Minor Reseat the modules at the near end and upstream nodes. Examine the incoming SONET overhead with an optical test set to confirm invalid K bytes. Minor Minor Check for other alarms, especially BERSD-L and BERSF-L. Clear these alarms. Verify the local receive optical levels, as well as the upstream transmit optical levels. Clean the optical connectors. Reseat the modules at the near end and upstream nodes. Check the protection mode for the far-end node. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info See LOS. Recommended Action Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

34 Page 1-28 Force10 Networks Release OPS4.2.2 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APSLOSCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Loss of Signal Clear APSMM 1 : Automatic protection switch (multiplex section protection - MSP) mode mismatch APSPATHCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Path Clear APSPDI 1 : Automatic protection switching (multiplex section protection - MSP) Path Defect Indication APSPDICLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Path Defect Indication Clear APS-PROTECT: Auto Switch to Working APSREL: Automatic protection switching (multiplex section protection - MSP) release Alarm Profiles shelf sonet_ptp sdh_ptp te206 node shelf shelf shelf te206 node shelf Probable Cause A protection switch that occurred because an LOS alarm has been cleared. There is a mismatch of the protection switching schemes at the two ends of the span. A protection switch that occurred because a path alarm has been cleared. A protection switch has occurred because of a PDI alarm. A protection switch that occurred because a PDI alarm has been cleared. A protection switch to the working facility that occurred because of an alarm clearing or Wait-To-Restore timer expiration. The alarm condition that caused an automatic protection switch has been cleared. This occurs when a protection group has been configured as non-revertive. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info If frequent protection switching occurs, check the revertive WTR period setting. Minor Minor Check protection modes at both ends. Verify that both ends are set for bidirectional or unidirectional. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info See PDI. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Recommended Action (Informational; no action required.) Info Info (Informational; no action required.) Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

35 Release OPS4.2.2 Force10 Networks Page 1-29 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition APSSDCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Signal Degrade Clear APSSFCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Signal Fail Clear APSUNEQCLEAR 1 : Automatic protection switching (multiplex section protection - MSP) Unequipped Clear APS-WORK: Auto Switch to Protect APSWTR: Transition to Wait to Restore mode (multiplex section protection - MSP) AU-AIS: Administrative Unit Alarm Indication Signal Alarm Profiles shelf shelf shelf te206 node shelf te206 node ds3_ptp sdh_hp sdh_ptp Probable Cause A protection switch that occurred because a SDBER-P alarm has been cleared. A protection switch that occurred because a SFBER-P alarm has been cleared. A protection switch that occurred because an UNEQ STS path alarm has been cleared. A protection switch to the protection faciilty that occurred because of an alarm on the working facility. Traffic is in the process of switching back to working channels. This occurs when a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group has been configured as revertive. The STM signal demultiplexed from the STM-N contains an AIS. This AIS can result from an upstream failure along the STM path. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Info If frequent protection switching occurs, check the revertive WTR period setting. Info Recommended Action Check the working facility for alarms. Info Info If frequent protection switching occurs, check the revertive WTR period setting. SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your payload connections. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

36 Page 1-30 Force10 Networks Release OPS4.2.2 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition AU-LOP: Administrative Unit Loss of Pointer AUTHFAIL 1 : OSPF authentication key or type mismatch AUTOPRV 1 : Auto provisioning error AUTO-TX-ON: Transmitter automatically enabled BADPKTRX 1 : Received an OSPF packet that cannot be parsed BATDSCHRG 2 : Battery is discharging Alarm Profiles ds3_ptp sdh_hp sdh_ptp shelf sonet_ptp sdh_ptp ethernet_ptp sdh_ptp sonet_ptp Probable Cause Valid AU pointer bytes are missing from the SDH overhead. An OSPF packet has been received whose authentication key or type conflicts with this node s authentication key or type. A signal failure has occurred on the ring and the user has added new cross-connect data. When the system attempts to auto provision the squelch tables, they cannot be updated, triggering the alarm. Event against the optical interface when the transmitter has been turned on automatically. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check the cabling and physical connections on the reporting card. Verify cross-connects. Check network timing synchronization. Verify that the expected bandwidth and received bandwidth are the same. If the alarm persists, replace the module. Minor Minor Retry authentication with new key or type. Minor Minor Clear the signal failure. Info Info (Informational; no action required.) shelf OSPF packet cannot be parsed. Minor Minor Check configuration and PM. shelf Battery is discharging. Minor Minor Check and follow your method of procedures. BATTERY: Battery has failed shelf Battery has failed. Minor Minor Check and follow your method of procedures. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

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

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

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

40 Page 1-34 Force10 Networks Release OPS4.2.2 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BERSF-L: Bit Error Rate signal fail Line ds3_ptp (ds_ptp) e3_ptp 1 shelf te50 Alarm Profiles sonet_ptp te206 node Probable Cause The BER on the incoming EC-1 line has exceeded the signal fail threshold. The BER on the incoming BITS has exceeded the signal fail threshold. 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. Fiber could be bent or damaged. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning Check cable connectors and module ports. Warning Warning Check cable connectors. SA Warning Warning Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an OC-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and fiber connection. Check fiber for bends or damage. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

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

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

43 Release OPS4.2.2 Force10 Networks Page 1-37 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BITSA-LOCK: Lockout - Derived DS1 System BITS 1 BITSA-MAN: Manual switch - Derived DS1 System BITS 1 BITSB-FRC: Forced switch - Derived DS1 System BITS 2 BITSB-LOCK: Lockout - Derived DS1 System BITS 2 BITSB-MAN: Manual switch - Derived DS1 System BITS 2 shelf A lockout is in process on this timing reference. Warning Warning Clear the Lockout switch command. shelf A manual switch is in process. Warning Warning Clear the Manual switch command. shelf A forced switch is in process. Warning Warning Clear the Forced switch command. shelf A lockout is in process on this timing reference. Warning Warning Clear the Lockout switch command. shelf A manual switch is in process. Warning Warning Clear the Manual switch command. BITSGEN 1 : BITS event shelf Unused. Info Info Unused. BITSRBOC 1 : BITS RBOC detect shelf Unused. Info Info Unused. BLOCK-TO-FWD: Ethernet Transition from Block to Forward BLSR_NOT_SYNC: BLSR ring is out of sync BLSR_SYNC_UNKNOWN: BLSR unknown error Alarm Profiles te206 node server server Probable Cause One of the nodes in the BLSR/MS-SPRing is out of sync with the other nodes in the ring possibly due to invalid K bytes. BLSR/MS-SPRing synchronization status is unknown. Service Affecting Default Major Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical Check for OC-N/STM-N module failures. Examine the incoming SONET/SDH overhead with an optical test set to confirm inconsistent or invalid K bytes. Issue an init command to re-initialize the ring. Warning Warning Check for OC-N/STM-N module failures. Examine the incoming SONET/SDH overhead with an optical test set to confirm inconsistent or invalid K bytes. Issue a sync command to re-synchronize the ring. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

44 Page 1-38 Force10 Networks Release OPS4.2.2 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition BOARDFAIL: Board failure alarm ta200 BPSIG: The backplane cannot communicate with other modules CFGERR 1 : OSPF configuration parameter mismatch) The OMX3 or PM13 board may not be seated correctly in the chassis or has failed. shelf Module defect. Backplane slot defect. shelf A packet was received whose configuration parameters conflict with the node s configuration parameters. CLEAR: Clear switch request shelf A Clear switch command has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. CLFAIL: Cooling fan failure shelf The cooling fan or the power source may have a defect. SA Critical Critical Check that the module is inserted correctly into the chassis. Otherwise, run diagnostics to test the state of the module. SA Critical Minor Replace the module. If the same alarm persists, try another slot in the shelf. Minor Minor Check the configuration. Info Info (Informational; no action required.) Minor Minor Check the state of the cooling fan or the power. CLFAN: Fan failed shelf The cooling fan is defective. Minor Minor Check the state of the cooling fan or the power source. Replace the fan unit, as necesary. CLRLOOP: Clear loopback Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp eop eop_ctp ethernet_ptp sonet_ptp sdh_ptp Probable Cause CMTFLT: Commit Failure te206 node Connection to TE-206 from TransNav GUI failed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action A loopback has been cleared. Warning Warning (Informational; no action required.) Info Info Manually commit the software. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, A through C

45 Release OPS4.2.2 Force10 Networks Page 1-39 Table 1-8 Alarms, Events and Recommended Actions, A through C (continued) Alarm: Definition COM: Communication failure server The management server cannot synchronize with the node. CONTROL: Control alarm on MPS IM ta200 te50 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). SA Warning Warning Check that the node name was entered exactly as configured with the node-level CLI (the node name is case-sensitive). te50 The control signal is not present. SA Critical Critical Check connectivity and the multi-protocol serial (MPS) interface module (IM) alarm monitor configuration. CTS: Clear to send on MPS IM te50 A clear to send (CTS) signal is not yet received on the MPS IM alarm monitoring system. 1 Not supported in this release. Alarm Profiles 2 Environmental alarm inputs are customized by each operator. Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical Check connectivity and configuration. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, A through C

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

47 Release OPS4.2.2 Force10 Networks Page 1-41 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DBSIGN: Database signature mismatch DCCFAIL: Data Communications Channel fail Alarm Profiles ds3_ptp e1_ptp e3_ptp ethernet_ptp sdh_ptp sonet_ptp server shelf ta200 te50 ds3_ptp (ds_ptp) ds3_ptp (ds_ptp) e3_ptp 1 sonet_ptp sonet_sts sdh_hp sdh_lp sdh_ptp te206 node Probable Cause 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. Not supported on EC-1. SA Major Major Not supported; no action required. 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. The DCC on the TE-206 has failed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Major Minor Check the OC-N interface. Check for a fiber cut and OC-N LOS alarms. Verify the remote OC-N interface has Control Data enabled and is active. Filter local alarms as necessary until remote link comes active. Info Minor Verify the DCC interface is active. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

48 Page 1-42 Force10 Networks Release OPS4.2.2 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DOWN 1 : Out of service DQL 1 : Degraded quality level DS1AIS: Alarm indication signal - DS1 DS1AIS-TX: Alarm Indication Signal - transmit, DS1 Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp ethernet_ptp server shelf sonet_ptp sdh_ptp sonet_service ta200 te50 ds3_ptp ds_ptp e3_ptp shelf sonet_ptp sdh_ptp ds1_ptp ta200 te50 te206 node te206 nod Probable Cause Unused. Minor Minor Unused. The incoming signal has a degraded quality level. Minor Minor Check and clean connections. The DS1 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. The DS1 output signal contains an AIS. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Minor Info Inspect and clear alarms from the downstreamasynchronous equipment. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

49 Release OPS4.2.2 Force10 Networks Page 1-43 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DS1 Loss of frame - DS1 DS1LOF: Loss of frame - DS1 ds1_ptp te206 node 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). 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 DS1RAI-TX: Remote alarm indication transmitted DS3AIS: Alarm indication signal - DS3 DS3AIS-TX: Alarm Indication Signal - transmit, DS3 Alarm Profiles ds1_ptp te50 te206 node 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. te206 node The near-end node has detected a defect signal on an outgoing DS1. The local node is sending a bad DS1 signal towards the DS-X. ds3_ptp ds_ptp ta200 te50 te206 node te206 node Probable Cause The DS3 input signal contains an AIS. The DS3 output signal contains an AIS. DS3FEAC-AIS: te206 node The DS3 FEAC channel is receiving AIS indication. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) 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. Warning Warning Verify that the connections between the DS-X and the DS1 module are secure. Verify that the DS1 signal exiting the near end of the SONET network is error-free. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. SA Minor Minor Inspect and clear alarms from the downstreamasynchronous equipment. Info Recommended Action Check upstream equipment for the source of AIS. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

50 Page 1-44 Force10 Networks Release OPS4.2.2 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DS3FEAC-EQPT: DS3 FEAC Equipment Failure DS3FEAC-IDLE: DS3 FEAC Idle Signal DS3FEAC-LOF: DS3 FEAC Loss of Frame DS3FEAC-LOS: DS3 FEAC Loss of Signal te206 node te206 node te206 node te206 node The DS3 FEAC channel is receiving Equipment Failure indication. The DS3 FEAC channel is receiving Idle indication. The DS3 FEAC channel is receiving Loss of Frame indication. The DS3 FEAC channel is receiving Loss of Signal indication. DS3LOF: Loss of frame, DS3 te206 node The DS3 input contains a LOF that is a mismatch of the line format between the Traverse and the upstream asynchronous equipment. DS3RAI: Remote alarm indication DS3RAI-TX: Remote alarm indication transmitted Alarm Profiles ds3_ptp ds_ptp ta200 te50 te206 node Probable Cause The far-end node has detected a defect signal on an incoming DS3. The local node is sending a bad DS3 signal towards the DS-X. te206 node The near-end node has detected a defect signal on an outgoing DS3. The local node is sending a bad DS3 signal towards the DS-X. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info Check upstream equipment for source of Equipment Failure. Check upstream equipment for source of Idle. Info Check upstream e. Info Recommended Action Check upstream equipment for source of Loss of Signal. 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). Warning Warning Verify that the connections between the DS-X and the DS3 module are secure. Verify that the DS3 signal entering the far end of the SONET network is error-free. Warning Warning Verify that the connections between the DS-X and the DS3 module are secure. Verify that the DS3 signal exiting the near end of the SONET network is error-free. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

51 Release OPS4.2.2 Force10 Networks Page 1-45 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition DSR: Data set ready on MPS IM te50 The data set ready signal is not yet received on the MPS IM alarm monitoring system. DTR: Data terminal ready on MPS IM E1AIS: Alarm indication signal - E1 E1LOMCAS: Alarm indication signal - E1 E1LOMCRC: Alarm indication signal - E1 E1RAI: Remote alarm indication E3 AIS: Alarm indication signal - E3 E3 RAI: Remote alarm indication Alarm Profiles te50 e1_ptp ta200 te50 Probable Cause The data terminal ready signal is not yet received on the MPS IM alarm monitoring system. SA Critical Critical Check the node, connectivity, and the configuration. SA Critical Critical Check the DTE and modem connectivity and the configuration. The E1 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. e1_ptp Loss of Multiframe CAS. Critical Critical Check the interface. e1_ptp Loss of Multiframe CRC. Critical Critical Check the interface. e1_ptp The far-end node has Warning Warning Verify that the connections between the detected a defect signal on an E-X and the E1 module are secure. te50 incoming E1. SA Critical Critical Verify that the E1 signal entering the far The local node is sending a end of the SDH network is error-free. bad E1 signal towards the E-X. e3_ptp The E3 input contains an AIS. SA Critical Critical Inspect and clear alarms from the upstream asynchronous equipment. e3_ptp The far-end node has detected a defect signal on an incoming E3. The local node is sending a bad E3 signal towards the E-X. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action 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. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

52 Page 1-46 Force10 Networks Release OPS4.2.2 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition 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. 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. EQCOMM 1 : Communication link failed EQFRCSW 1 : Forced protection switch Equipment Minor Minor Monitor for further internal queue engine failures. shelf The link is down. SA Critical Critical Check the link connections. shelf A forced protection switch command has been executed on a 1:1 equipment protection group. EQINS: Equipment inserted te206 node A new cassette has been inserted into the node EQINV: Equipment invalid EQLOCK 1 : Protection lockout Equipment EQMANSW 1 : Manual protection switch Equipment Alarm Profiles shelf te206 node shelf shelf Probable Cause An invalid piece of equipment has been used. A lockout protection switch command has been executed on a 1:1 equipment protection group. A manual protection switch command has been executed on a 1:1 equipment protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Warning Warning If the reason for executing the forced switch command no longer exists, clear the switch command. Info Recommended Action Informational only. No action required. Critical Critical Plug in a valid piece of equipment. Warning Warning If the reason for executing the lockout switch command no longer exists, clear the switch command. Warning Warning If the reason for executing the manual switch command no longer exists, clear the switch command. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

53 Release OPS4.2.2 Force10 Networks Page 1-47 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition EQMIS: Equipment mismatch EQPT: Equipment malfunction / failure. EQRMV: Equipment removed ERFI-V: Enhanced (two bit) Remote failure indication VT Path Alarm Profiles shelf te206 node server te206 node shelf te206 node shelf te206 node ds1_ptp Probable Cause 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. A hardware failure has occurred. SA Critical Critical Check and reseat equipment. If this fails to clear the alarm, replace the equipment if necessary. A hardware failure has occurred on the reporting module. A module is not properly seated or it has been removed. 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. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Reseat the module. If this fails to clear the alarm, replace the module if necessary. SA Critical Minor Plug in the correct module or delete the module using the TransNav system if that slot is not being used. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms such as LOP-V, AIS-V, PLM-V, TIM-V, and UNEQ-V from the far-end node. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

54 Page 1-48 Force10 Networks Release OPS4.2.2 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition ETHRING-FAIL: Invalid Ethernet Ring Configuration EXER_SWITCH: Exercise switch on remote node te206 node shelf A root bridge has not been configured for the ETHRING. Checking status of remote node via exercise command (using K1/K2 bytes) for 1+1 bidirectional protection group. Info Configure a root bridge for the ETHRING. Info Info (Informational only; no action required.) EXPLGS: Explosive gas shelf Explosive gas detected. Minor Minor Check and follow your method of procedures. EXTA-REF1-ALM: Primary reference in alarm EXTA-REF2-ALM: Secondary reference in alarm EXTA-REF3-ALM: Third reference in alarm EXTA-REF4-ALM: Fourth reference in alarm Alarm Profiles shelf shelf shelf shelf Probable Cause 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. 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. 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. 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. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

55 Release OPS4.2.2 Force10 Networks Page 1-49 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition EXTB-REF1-ALM: Primary reference in alarm. EXTB-REF2-ALM: Secondary reference in alarm EXTB-REF3-ALM: Third reference in alarm EXTB-REF4-ALM: Fourth reference in alarm FANCOMM: Fan tray communication failure Alarm Profiles shelf shelf shelf shelf shelf Probable Cause 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. 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. 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. 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. Communication failure with the fan tray. FANCOND: Fan tray condition shelf EEPROM failure or thermistor failure. FANFLTR: Fan filter shelf Temperature has exceeded 49 ºC. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Warning Warning Clear the LOS, LOF, or AIS-L alarm. Refer to the recommended actions for those alarms in this table. Minor Minor Reseat the fan tray. Warning Warning Replace the fan tray. Minor Minor Check that the temperature of the room is not abnormally high. Replace the fan tray air filter. FANRMV: Fan tray removed shelf Fan tray has been removed. Minor Minor Install the fan tray. Recommended Action Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

56 Page 1-50 Force10 Networks Release OPS4.2.2 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FEP 1 : Far-end protection failure FILE_UPLOAD: Single file transfer sonet_ptp sdh_ptp te206 node An APS switching channel signal failure has occurred on the protect module coming into the node. Minor Minor Check the equipment on the other end of the fiber. shelf File upload is in process. Info Info (Informational only; no action required.) FIRDETR: Fire detector failure shelf Fire detection equipment has failed. Minor Minor Check fire detection equipment and power source. Check and follow your method of procedures. FIRE 2 : Fire shelf Fire detected. Minor Minor Check and follow your method of procedures. FLOOD 2 : Flood shelf Flood detected. Minor Minor Check and follow your method of procedures. FLOW-DEGRADED: VPG Degraded Flow FLOW-LEARNED: Learned VLAN Flow FLOW-UNLEARNED: Unlearned VLAN Flow Alarm Profiles ethernet_ptp ethernet_ptp ethernet_ptp Probable Cause The system is currently forwarding a Poor, Lost, or Null copy of a learned flow. Note: Flow alarms are received on the working port of the Virtual Protection Group (VPG). The system has learned a VLAN flow. The system has unlearned a single VLAN flow either automatically or through an operator request. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Major Major The system clears flow-related alarms once it unlearns the flow. Info Info Informational only; no action required. Info Info Informational only; no action required. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

57 Release OPS4.2.2 Force10 Networks Page 1-51 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FLOWS-UNLEARNED: Unlearned All VLAN Flows FLOW-UNPROTECTED: VPG Unprotected Flow FOPR: Failure of protocol - receive FOPT: Failure of protocol - transmit Alarm Profiles ethernet_ptp ethernet_ptp eos eop sdh_eos eos eop sdh_eos Probable Cause The system has unlearned all the VLAN flows through an operator request. The system is currently forwarding a Good copy of a learned flow when the status of the flow on the other port in the VPG is anything other than Good. Note: Flow alarms are received on the working port of the VPG. LCAS has detected unexpected behavior by the remote LCAS peer. LCAS has detected unexpected behavior by the remote LCAS peer. 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. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info Informational only; no action required. Minor Minor The system clears flow-related alarms once it unlearns the flow. SA Critical Critical Check remote peer for proper configuration. SA Critical Critical Check remote peer for proper configuration. SA Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

58 Page 1-52 Force10 Networks Release OPS4.2.2 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FORCED: Forced protection switching FORCED_ON_PROT: Forced protection switch on protecting unit FORCED_ON_SECT1: Forced protection switch on optimized 1+1 APS working section 1 FORCED_ON_SECT2: Forced protection switch on optimized 1+1 APS working section 2 FORCED_ON_WORK: Forced protection switch on working unit Alarm Profiles shelf te206 node shelf te206 node shelf shelf shelf te206 node Probable Cause A forced protection switch has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. A forced protection switch has been performed on a protection group. A forced switch has been performed on the optimized 1+1 APS bi-directional working section 1. Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge. A forced switch has been performed on the optimized 1+1 APS bi-directional working section 2. Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge. A forced protection switch has been performed on the working unit. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

59 Release OPS4.2.2 Force10 Networks Page 1-53 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition FORCED-EAST: Forced switch applied on east facility FORCED-WEST: Forced switch applied on wast facility Alarm Profiles shelf shelf Probable Cause A forced protection switch has been performed on the east facility. A forced protection switch has been performed on the west facility. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Warning Warning Verify that the reason for performing the forced switch no longer exists. Clear the switch command. FUSE: Fuse failure shelf A fuse has failed. Minor Minor Check and follow your method of procedures. FWMIS: Firmware mismatch te206 node The current running firmware revision does not match the current running software revision. Major Perform a firmware upgrade to resolve the mismatch. GENFAIL 2 : Generator failure shelf Generator has failed. Minor Minor Check and follow your method of procedures. GFPLOF: Loss of frame shelf Generic Framing Procedure (GFP) framing problem on the incoming bit stream. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Inspect all VC bundle facilities. Check remote sites for module removal/failure alarms or disabled Ethernet transmitter. Check the cable and interface. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K

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

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

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

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

64 Page 1-58 Force10 Networks Release OPS4.2.2 Table 1-9 Alarms, Events and Recommended Actions, D through K (continued) Alarm: Definition HP-UNEQ: Unequipped - High order Path HWFAULT: Hardware fault IDLE: Idle signal detection INCOMPATSW: Incompatible software ds3_ptp sdh_hp sdh_ptp shelf te206 ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp eop eop_ctp server shelf No payload is received on an activated service. A hardware fault has occurred. This corresponds to the CASFA alarm on the TE-206 node. Service is not provisioned over the interface. Software is incompatible between modules that are attempting communication with each other. INTRUDER: Intrusion shelf Minor Minor INDICATION: Indication Alarm on MPS IM KBYTE: Default K byte Alarm Profiles te50 SA Critical Critical sonet_ptp sdh_ptp Probable Cause Far end protection mode mismatch. K1/K2 bytes not sent. For example, a BLSR may have one node configured as a UPSR, and a node in a UPSR would not send the two valid K1/K2 bytes expected by a BLSR system. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check your connection. Connect your proper payload. Check the service source. SA Critical Critical See Hardware Fault Detection, page 1-60 for further details. Take appropriate action, as necessary. SA Warning Warning Check the interface. On eop and eop_ctp members, affects DS1 and DS3 port members only. Check the far-end node. Critical Critical Check the current software versions and compatibility IDs of the modules. One module s current software version must be at least the compatibility ID (the lowest software version the other module can work with) of the other module. Perform software upgrade as necessary for software compatibility. Minor Minor Check protection mode for far-end node. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, D through K

65 Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, D through K 1 Not supported in this release. 2 Environmental alarm inputs are customized by each operator. Release OPS4.2.2 Force10 Networks Page 1-59

66 Operations and Maintenance Guide, Section 1: Fault Management Hardware Fault Detection Figure 1-13 Hardware Fault Detection for NGE, NGE Plus, and EoPDH Cards Hardware Fault Detection Figure 1-14 Hardware Fault Detection for 10GbE and GbE-10 Cards Page 1-60 Force10 Networks Release OPS4.2.2

67 Release OPS4.2.2 Force10 Networks Page 1-61 Alarms/Events, L through S Table 1-10 Alarms, Events and Recommended Actions, L through S Alarm: Definition LBC: TXlaser bias current threshold violation LBCNRML 1 : Laser bias current normalized threshold crossing alert. Alarm Profiles ethernet_ptp sdh_ptp sonet_ptp shelf Probable Cause TXlaser bias current threshold violation. 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. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Warning Warning Check laser bias. Recommended Action shelf Power level out of range. Warning Warning Measure power level using optical power meter; replace module if below threshold. LCAS-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) LCAS-RES: LCAS restore vc bundle EOS event to indicate member was restored to operation in an LCAS-enabled VC bundle. (Location: Near-end, Direction: received) Info Info Check for LCAS (GIDERR, SSF) or member path alarms and proceed as directed. Info Info Informational; no action required. LEAK 2 : Leak shelf Leak detected. Minor Minor Check and follow your method of procedures. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

68 Page 1-62 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LFD: Loss of Frame Delineation LINKFAIL: Link failure LINK_FRCD_DIS: Duplex mode mismatch LNKBCPTY: Link broadcast message parity error Alarm Profiles eos sdh_eos eop ethernet_ptp te206 node ethernet_ptp Probable Cause GFP has lost sync. SA Critical Critical Check the paths associated with the EOS or EOP members for alarms. Transmitter/receiver failure. Fiber connection lost. A module along the path has been removed. There is a Duplex mode port parameter mismatch between the near- and far-end Ethernet ports. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Critical Check connectors, cables, and modules. Check Ethernet port configuration, Integrity Status parameter for details. See the TransNav Management System GUI Guide, Section 5 Equipment, Chapter 4 Ethernet Equipment, Ethernet Equipment, page SA Critical Critical Check the Duplex mode of the Ethernet interfaces. Alarm clearing criteria: First, at the Force10 Ethernet interface: Lock the offending Ethernet interface. Then, at the link partner interface: Lock the offending Ethernet interface. Turn off auto-negotiation. Set the Duplex parameter to forced half-duplex mode. Then, at the Force10 Ethernet interface: Unlock the offending Ethernet interface. Finally, at the link partner interface: Unlock the offending Ethernet interface. shelf Unused. Minor Minor Unused. Recommended Action Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

69 Release OPS4.2.2 Force10 Networks Page 1-63 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LNKBLKCNT: Link block count error LNKBLKPTY: Link block parity error shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. LNKCRC: Link CRC error shelf Unused. Minor Minor Unused. LNKCSUM: Link checksum error shelf Unused. Minor Minor Unused. LNKDOWN: Link down shelf Unused. Info Info Unused. LNKERR: Unrecognized link error shelf Unused. Minor Minor Unused. LNKOVFL: Link overflow shelf Unused. Minor Minor Unused. LNKPAPTY: Link path alarm parity error 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 Alarm Profiles Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. shelf Unused. Minor Minor Unused. Recommended Action Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

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

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

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

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

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

75 Release OPS4.2.2 Force10 Networks Page 1-69 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOG: Loss of Group LOGINFAIL: Login failed LOGINSUCC: Login successful LOGINTERM: Login terminated eop sdh_eos server shelf server shelf server shelf Loss of Group. SA Critical Critical Check the paths associated with the EOS or EOP members for alarms. Login attempt has failed. Info Info Try again. Check the login log; contact your system administrator persistent login failures could indicate possible hacking. Login has succeeded. Info Info Informational; no action required. Login has terminated. Info Info Informational; no action required. LOL: Loss of link te50 SA Critical Critical LOM 1 : Loss of Multiframe, Rx path LOMCRC: Loss of Multiframe, CRC LOM-P: Loss of Multiframe synchronization - STS Alarm Profiles ethernet_ptp sdh_ptp shelf eop eop_ctp te206 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 eop eop_ctp eos eos_ctp Probable Cause Loss of Multiframe CRC on the incoming signal An error is detected in the paths multiframe indicator. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Warning Warning This is an EOP member alarm for E1 port members only. Informational: indicates an incoming LOM condition. 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. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

76 Page 1-70 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOM-V: Loss of Multiframe synchronization - VT LOP-P: Loss of Pointer Path Alarm Profiles eos eos_ctp eop_ctp ds3_ptp (ds_ptp) e3_ptp sonet_ptp sonet_sts te206 node An error is detected in the path s multiframe indicator. Valid H1/H2 pointer bytes are missing from the STS path overhead. 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. SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. Verify that the expected bandwidth and received bandwidth are the same. If the alarm persists, replace the module. ethernet_ptp 1 Valid pointer bytes are missing. SA Critical Minor Check the cabling and physical connections on the reporting module. ta200 te50 Probable Cause Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Valid pointer bytes are missing. SA Critical Critical Check the cabling and physical connections on the reporting module. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

77 Release OPS4.2.2 Force10 Networks Page 1-71 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOP-V 1 : Loss of Pointer VT LOP-VC 1 : Loss of Pointer VC Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sonet_ptp sonet_vt sonet_sts te206 node ta200 te50 Valid pointer bytes are missing from the VT overhead. Valid pointer bytes are missing from the VT overhead. SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. SA Critical Critical Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. sdh_ptp See TU-LOP. n/a n/a n/a See TU-LOP. e1_ptp sdh_ptp Probable Cause Valid pointer bytes are missing from the VC overhead. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

78 Page 1-72 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LOS: Loss of signal LP-BERSD: Bit error rate signal degrade - Low order Path Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e1_ptp e3_ptp ta200 te50 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_ptp sdh_ptp te206 node sdh_hp sdh-lp sdh_ptp Probable Cause OC-N loss of signal. Fiber may not be correctly connected to the module, or no signal exists on the line. Upstream equipment failure or fiber cut may cause this alarm. The STM signal demultiplexed and dropped from the STM-N has exceeded its signal degrade threshold. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check the upstream node for OC-N module failure/removal. Check the fiber connection. Verify the receive optical levels. Verify good optical connections to the local and far-end OC-N modules. Warning Warning Examine the network for other low order path bit error rate problems and retrieve PM data to find a possible common source of the bit errors. Perform loopback tests to isolate the problem. Check cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

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

80 Page 1-74 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LPBKINBAND: Inband loopback active LPBKTERM: Terminal loopback active LP-LOM: Low order path Loss of multiframe synchronization LP-MND: Low order path Member not de-skewable LP-PLM: Payload label mismatch received - Low order Path Alarm Profiles ds3_ptp eop eop_ctp ds1_ptp ds_ptp e1_ptp e3_ptp ethernet_ptp sdh_ptp shelf sonet_ptp te206 node sdh_eos sdh_eos_ctp sdh_eos sdh_eos_ctp sdh_hp sdh-lp sdh_ptp Probable Cause An inband loopback is active. Warning Warning Validate this state. On EOP ports, occurs on DS1 and DS3 members only. Clear loopback, as required. A terminal loopback is active. Warning Warning Validate this state. Clear loopback, as required. An error is detected in the paths multiframe indicator. Differential Delay exceeded on EOS member and the member was removed from the group. Invalid byte in the Low Order path overhead. The payload does not match what the signal label is reporting. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical This is an eos_ctp member alarm. If not using LCAS, check that EOS member order matches that of the remote EOS. Note: This alarm does not apply for Gigabit Ethernet cards. 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 for Gigabit Ethernet cards. SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

81 Release OPS4.2.2 Force10 Networks Page 1-75 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition LP-RDI: Remote Defect Indication - Low order Path LP-RFI: Remote Failure Indication - Low order Path LP-RFICON: Remote failure indication, connectivity defect - Low order Path LP-RFIPAY: Remote failure indication, payload defect - Low order Path LP-RFISVR: Remote failure indication, server defect - Low order Path Alarm Profiles sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp Probable Cause Valid STM-N framing is not detected or AU-AIS is received from the source. The signal demultiplexed from the STM-N contains a remote failure indication. The far-end node has detected path defects coming from the local site. Far end path has an LP-UNEQ or LP-TIM alarm. Far end path has a LP-PLM alarm. Far end path has an AU-AIS or AU-LOP alarm. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Check STM-N framing source. See AU-AIS. Warning Warning Determine the defects found at the far-end node. Verify your payload connections. Clear path alarms from the far-end node. Warning Warning Verify your payload connections. Check for far end alarms, especially LP-UNEQ and LP-TIM. Refer to the recommended actions for LP-UNEQ and LP-TIM. Warning Warning Verify your payload connections. Check for far end alarms, especially LP-PLM. Refer to the recommended actions for LP-PLM. Warning Info Verify your payload connections. Check for far end alarms, especially AU-AIS and AU-LOP. Refer to the recommended actions for AU-AIS and AU-LOP. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

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

83 Release OPS4.2.2 Force10 Networks Page 1-77 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition MANUAL: Manual protection switching MAN_ON_PROT: Manual protection switching MAN_ON_WORK: Manual protection switching MAN-TX-OFF: Transmitter manually disabled MAN-TX-ON: Transmitter manually enabled shel te206 node shelf te206 node shelf te206 node ethernet_ptp sdh_ptp sonet_ptp ethernet_ptp sdh_ptp sonet_ptp A manual protection switch has been executed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. A manual protection switch has been executed on the protecting port of a protection group. A manual protection switch has been executed on a working port of a protection group. Operator disabled the optical laser. Operator enabled the optical laser. Info Info Informational; no action required. Info Info Informational; no action required. Info Info Informational; no action required. Info Info Informational; no action required. Info Info Informational; no action required. MAXAGE 1 : Maximum age shelf Unused. Minor Minor Unused. MISC: Misc (default) shelf Minor Minor MND: PDH member not de-skewable. MND-P: Member not de-skewable - STS Alarm Profiles eop eop_ctp eos eos_ctp Probable Cause Differential Delay exceeded on EOP member; the member was removed from the group. Differential Delay exceeded on EOS member and the member was removed from the group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical 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. SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

84 Page 1-78 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition MND-V: Member not de-skewable - VT MPU_BATTERY_A: Battery A alarm MPU_BATTERY_B: Battery B alarm MS-AIS: Alarm Indication Signal - Multiplex Section Alarm Profiles eos eos_ctp Differential Delay exceeded on EOS member and the member was removed from the group. ta200 SA Critical Critical ta200 SA Critical Critical sdh_ptp Probable Cause An upstream failure occurred at the multiplex section layer. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Critical This is an eos_ctp member alarm. Check the EOS member status to determine which paths have exceeded the delay and reroute them. Note: This alarm does not apply to Gigabit Ethernet cards. SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your multiplex section payload connections. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

85 Release OPS4.2.2 Force10 Networks Page 1-79 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition MS-BERSD: BER signal degrade - Multiplex Section MS-BERSF: BER signal fail - Multiplex Section Alarm Profiles Probable Cause sdh_ptp The BER on the incoming STM-N line has exceeded the signal degrade threshold. A connector in the STM-N optical link could be dirty. An STM-N module hardware problem could exist. Fiber could be bent or damaged. sdh_ptp The BER on the incoming STM-N line has exceeded the signal fail threshold. A connector in the STM-N optical link could be dirty. An STM-N module hardware problem could exist. Fiber could be bent or damaged. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Critical Minor Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and fiber connection. Check fiber for bends or damage. If the problem persists, contact Force10 s Technical Assistance Center (TAC). Critical Minor Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an STM-N module is a possible source of the bit errors, perform a manual protection switch to the protection unit. If the BER alarm clears, replace the defective working unit. Check the remote (source) Transmit and fiber connection. Check fiber for bends or damage. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

86 Page 1-80 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition MS-RDI: Remote Defect Indicator - Multiplex Section MSSP_NOT_SYNC: MS-SP Ring synchronization failure MSSP_SYNC_UNKNOWN: Unknown error sdh_ptp server server Valid STM-N framing is not detected or MS-AIS is received from the source. One of the nodes in the MS-SP Ring is out of sync with the other nodes in the ring possibly due to invalid K bytes. MSSP ring synchronization status is unknown. MULT_PRIMARY_SERVER server There are multiple primary servers discovered. Only one primary server is allowed. Warning Warning Check STM-N framing source. See MS-AIS. SA Critical Critical Check for OC-N module failures. Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes. Warning Warning Issue sync command to resynchronize the ring. SA Major Warning Restore the environment to one primary server. NEIGHSC 1 shelf Unused. Minor Minor Unused. NETSYNC: Network object synchronization failure server Master network objects (e.g., alarm profiles) are out of synchronization with propagated node objects. Warning Warning Resynchronize using the TransNav GUI. NEWLSA 1 shelf Unused. Minor Minor Unused. NO_OUTPUT: Output Signal Activity Failure NO_PRIMARY_SERVER: No primary TransNav server Alarm Profiles ta200 SA Critical Critical server Probable Cause The primary server was not found. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Major Warning Check connectivity. If no primary server in the network, set up a primary server in the network environment. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

87 Release OPS4.2.2 Force10 Networks Page 1-81 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition NODEEQMIS: Node equipment mismatch NODEIDMIS: Node ID mismatch NODESYNC: Node synchronization NO-REMOTE-LCAS: No remote LCAS NPM: No provisioned members OSPF-AIMM: OSPF Area ID Mismatch Alarm Profiles server sonet_ptp sdh_ptp Server-Agent equipment mismatch. The node ID selected is already in use. server Discovery of and synchronization with a new node. GCM protection switch. eos eop sdh_eos shelf eos eop sdh_eos lag te206 node Probable Cause The remote peer does not have LCAS capability or the capability is undetermined. No members have been provisioned. The OSPF Area configuration does not match the configuration of other routers in the network. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Critical Determine if the TransNav server or the node contains the correct module configuration. If the TransNav server contains the correct module configuration, use the node-level CLI to lock, restart, and delete the module. The alarm should be deleted. If the node contains the correct module configuration, delete the node. During autodiscovery, the correct information will be forwarded to the TransNav server and the alarm should be deleted. Minor Minor Check all node IDs. Verify that they are each unique. Warning Warning Wait for node synchronization to complete. Check network server connections. Warning Warning Enable LCAS on the remote nodes EOS or EOP. Check remote peer configuration, capability, and connectivity. SA Critical Critical Add CTP members to the EOS or EOP port. Add ports to the LAG. Info Recommended Action Configure OSPF Area to be consistent in the network. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

88 Page 1-82 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition OSPF-DIMM: OSPF Router Dead Interval Mismatch OSPF-HIMM: OSPF Hello Interval Mismatch te206 node te206 node OPENDR: Door open shelf A door is open in the environment. OPR: Optical power received threshold violation OPT: Optical power transmitted threshold violation ORPNORM 1 : Optical receive power normalized threshold crossing alert OTPNORM 1 : Optical transmit power normalized threshold crossing alert OVERTEMP: Fan tray temperature has exceeded a maximum value Alarm Profiles ethernet_ptp sdh_ptp sonet_ptp shelf ethernet_ptp sdh_ptp sonet_ptp shelf Received optical power does not meet guaranteed value. 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. Info Info Minor Minor Validate that the door should be open. Close the door, as necessary. Warning Warning Check interface. Warning Warning Measure power level using optical power meter. shelf Unused. Warning Warning Unused. shelf Unused. Warning Warning Unused. shelf Probable Cause Fan tray temperature has exceeded 56ºC. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check that the temperature of the room is not abnormally high. Replace the fan tray air filter. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

89 Release OPS4.2.2 Force10 Networks Page 1-83 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition OVERVOLTAGE_A 1 : Exceeded a maximum voltage value - Enhanced GCM_A OVERVOLTAGE_B 1 : Exceeded a maximum voltage value - Enhanced GCM_B PCASQLCH 1 : PCA channel squelched PDI-n (P, n<2) 1 : Payload defect indicator PDI-n (1<n<5) 1 :Payload defect indicator Alarm Profiles shelf shelf sonet_ptp sdh_ptp ds3_ptp (ds_ptp) e3_ptp sdh_hp sdh-lp sdh_ptp sonet_sts sonet_ptp sdh_ptp ds3_ptp (ds_ptp) e3_ptp sonet_ptp sdh_ptp Probable Cause GCM_A has triggered due to an over voltage condition. The Enhanced GCM triggers the over-voltage alarm at VDC. It clears this alarm at VDC. GCM_B has triggered due to an over voltage condition. The Enhanced GCM triggers the over-voltage alarm at VDC. It clears this alarm at VDC. Extra traffic carried on protection channel(s) has been squelched due to a protection switch. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Minor Minor Check power system, breaker, fuse, and related cabling for power input A. Minor Minor Check power system, breaker, fuse, and related cabling for power input B. Minor Minor Clear the protection switch. Check equipment ring topology configuration. Payload defect indication. SA Minor Minor Check cable connectors and module ports. Payload defect indication. Minor Minor Clean the fiber connections. Payload defect indication. SA Major Minor For DS3/EC1 modules, check cable connectors and module ports. Payload defect indication. SA Major Minor For OC-N modules, clean the fiber connections. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

90 Page 1-84 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition PDI-n (n>4) 1 :Payload defect indicator PKTRETX 1 : An OSPF packet has been retransmitted ds3_ptp (ds_ptp) e3_ptp sonet_ptp sdh_ptp Payload defect indication. SA Critical Minor For DS3/EC1 modules, check cable connectors and module ports. Payload defect indication. SA Critical Minor For OC-N modules, clean the fiber connections. shelf Unused. Minor Minor Unused. PLC: Partial loss of capacity lag At least one port in the LAG is down. PLCPLOF 1 : PLCP (Physical Layer Convergence Procedure) loss of frame PLCPRFI 1 : PLCP (Physical Layer Convergence Procedure) Remote Failure Indication PLCR: Partial loss of capacity - receive PLCT: Partial loss of capacity - transmit PLINESQL 1 : Persistent line squelching Alarm Profiles ds3_ptp (ds_ptp) e3_ptp ds3_ptp (ds_ptp) e3_ptp eos eop sdh_eos eos eop sdh_eos sonet_ptp sdh_ptp Probable Cause SA Critical Critical At least one port in the LAG is down. Check for proper cabling and that local and remote port configurations match. Unused. SA Critical Minor Unused. Unused. Warning Info Unused. Capacity loss on path. SA Critical Critical Check the paths associated with the EOS and EOP members for alarms. Capacity loss on path. SA Critical Critical Check the paths associated with the EOS or EOP members for alarms. STS (high order) path on the reporting OC-N/STM-N line has been squelched to avoid a misconnection. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Warning Warning Contact Force10 s Technical Assistance Center (TAC). Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

91 Release OPS4.2.2 Force10 Networks Page 1-85 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition PLM:Payload label mismatch received PLM-P: Path label mismatch PLM-V: Payload label mismatch received PLM-VC: Payload label mismatch received - VC Alarm Profiles ds3_ptp (ds_ptp) e3_ptp sonet_ptp sonet_sts ta200 te50 te206 node ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sonet_ptp sonet_vt sonet_sts te206 node Invalid C2 byte (signal label byte) in the SONET path overhead. The payload does not match what the signal label is reporting. Payload label mismatch on the path. Invalid byte in the path overhead. The payload does not match what the signal label is reporting. te50 Invalid byte in the path overhead. The payload does not match what the signal label is reporting. e1_ptp sdh_ptp Probable Cause Invalid byte in the path overhead. The payload does not match what the signal label is reporting. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Warning Warning Verify that the payload is the same as the provisioned payload/service. SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Warning Warning Connect correct payload. Verify that the payload is the same as the provisioned payload/service. SA Critical Minor Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

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

93 Release OPS4.2.2 Force10 Networks Page 1-87 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) RAI Alarm: Definition eop eop_ctp The far-end node has detected a framing problem on an incoming signal. - Warning Warning Check the paths associated with the EOP members RECTFAIL 2 : Rectifier failure shelf Rectifier has failed. Minor Minor Check and follow your method of procedures. RECTHIGH 2 : Rectifier high voltage RECTLOW 2 : Rectifier low voltage shelf Rectifier has high voltage. Minor Minor Check and follow your method of procedures. shelf Rectifier has low voltage. Minor Minor Check and follow your method of procedures. RMLF: Remote link failure lag A failure has occurred at the remote end of the link. REMOTE-LINKFAIL: Remote loss of client signal RESOURCE_MISMATCH: STSRM/VTRM Resource Mismatch Alarm Profiles ethernet_ptp shelf Probable Cause Link Integrity enabled and indicating that the remote Ethernet port is down. An uncommon alarm. The resource mismatch may occur as a result of a non-active GCM controller condition. The management system configuration does not match that of the line card. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Critical Critical Check the cable and configuration at the remote port. SA Critical Critical Check the cable and configuration at the remote port. SA Critical Minor Contact Force10 s Technical Assistance Center (TAC). Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

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

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

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

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

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

99 Release OPS4.2.2 Force10 Networks Page 1-93 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition RFLF: Remote Line Failure te206 node The far end GbE interface is detecting a loss of signal. RMTLOOP: FEAC Loopback and FDL Loopback RLSD: Receive Line Signal Detect on MPS IM RS-TIM: Trace identifier mismatch RTS: Request to send on MPS IM SENSORFAIL: Thermal sensor failure SERVER_LOGINFAIL: Server login to node failed SERVER_ROLE SETOPER: Set operation performed Alarm Profiles te206 node The far end DS3 interface has initiated a remote loopback using the FEAC channel or the FDL channel. Info Info Check the GbE fiber. Informational only. No action required. te50 Line signal not detected. SA Critical Critical Check connectivity and configuration at the remote end. sdh_ptp The expected path trace string does not match the received path trace string. SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. te50 Request to send not present. SA Critical Critical Check connectivity and configuration. shelf server server shelf server shelf Probable Cause The thermal sensor on a line or control module has failed. Node login authentication failed. Event identifies the server role as primary or secondary. A set operation has been performed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action 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. Critical Critical Try again. Contact your system administrator persistent login failures could indicate possible hacking. Info Info Informational; no action required. Info Info Informational; no action required. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

100 Page 1-94 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition SFO 1 : Sync frequency offset ds3_ptp (ds_ptp) sonet_ptp e3_ptp sdh_ptp SFPFAIL: SFP Fault te206 node A fault has been detected with the SFP. SFPMIS: SFP mismatch SFPRMV: SFP removed ethernet_ptp sdh_ptp sonet_ptp shelf te206 node ethernet_ptp sdh_ptp sonet_ptp shelf EC-1 or SONET facility timing. Minor Minor Check timing signal quality. SONET facility timing. Minor Minor Check timing signal quality. There is a mismatch on the SFP interface. SFP-UNKNOWN:? te206 node An SFP has been detected that is not certified for use with the system. SHELFMIS: Shelf type mismatch Alarm Profiles server Probable Cause Critical Minor Replace the faulty SFP. Critical Minor Check interface. The SFP has been removed. Critical Minor Check interface. The PreProvision shelf type does not match the actual shelf type. SA Critical Minor Replace the unknown SFP with a Force10 certified SFP. Warning Warning Delete the node. During autodiscovery, the correct node type should be discovered. SMOKE 2 : Smoke detected shelf Smoke detected. Minor Minor Check and follow your method of procedures. SNTP-FAIL te206 node The TE-206 node cannot communicate with the SNTP server. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Check the availability of the SNTP server. Verify the TE-206 SNTP configuration. Verify network connectivity from the TE-206 to the SNTP server. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

101 Release OPS4.2.2 Force10 Networks Page 1-95 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition SQLCHTBL 1 : Squelch table mismatch SQM 1 : Sequence number change SQM-P: Sequence ID mismatch- STS SQM-V: Sequence ID mismatch- VT Alarm Profiles sonet_ptp sdh_ptp ethernet_ptp shelf eop eop_ctp te206 node eos eos_ctp eos eos_ctp Probable Cause Alarm is raised as a circuit is being added to or deleted from a BLSR. May also be caused by incomplete provisioning of the STS channels. Unused for Traverse. The TE-206 member sequence number is in error. The member sequence number is in error. The member sequence number is in error. SSF: Server Signal Fail shelf All LCAS VC bundle members have failed. Also see path alarms for each VC bundle member (facility). The VC bundle operational state is set to Disabled until at least one member returns. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action 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. SA Critical Minor Unused for ethernet_ptp and shelf. Member alarm for virtual concatentation faults on EOP members. SA Critical Critical This is an eos_ctp member alarm. If non-lcas, check that the order of members in the remote EOS matches the local order. SA Critical 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. SA Critical Minor Inspect all VC bundle facilities. Check remote sites for module removal/failure alarms or disabled Ethernet transmitter. Check the cables and interfaces. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, L through S

102 Page 1-96 Force10 Networks Release OPS4.2.2 Table 1-10 Alarms, Events and Recommended Actions, L through S (continued) Alarm: Definition SUM-V: VT Alarm Summary te206 node One or more alarms exists for VT paths within the STS-1. SVC_STATUS 1 : Service status report SWCRPT: Software corruption server shelf server shelf Critical Minor Check the conditions of the VT paths within the STS-1. Unused. Info Info Unused. Software did not load or loaded with errors. SWERR: Software error all objects The software has detected an unexpected error. SA Critical Minor Contact Force10 s Technical Assistance Center (TAC). Info Info Contact Force10 s Technical Assistance Center (TAC). SWITCH 1 : Pointer switch ethernet_ptp Unused. SA Critical Minor Unused. SWITCH_TO_PROT: Traffic switch to Protection SWITCH_TO_SECT1: Traffic switch on optimized 1+1 APS working section 1 Alarm Profiles shelf te206 node shelf Probable Cause Traffic has switched to the standby module, port, or channel for a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. Traffic has switched on the optimized 1+1 APS bi-directional working section 1. Note: Section 1 and 2 are equal working sections, each with a permanent traffic bridge. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info Informational; no action required. Info Info Informational; no action required. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, L through S

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

104 Page 1-98 Force10 Networks Release OPS4.2.2 Alarms/Events, T through TZ Table 1-11 Alarms, Events and Recommended Actions, T through TZ Alarm: Definition TCA: Threshold crossing alert TEMP: Internal temperature threshold violation TEMPCRIT: Temperature critical TEMPWARN: Temperature warning TIM: Trace identifier mismatch Alarm Profiles ds1_ptp ds3_ptp (ds_ptp) e3_ptp ethernet_ptp sonet_ptp sdh_ptp te206 node ethernet_ptp sdh_ptp sonet_ptp shelf shelf shelf ds3_ptp (ds_ptp) e3_ptp sonet_ptp sdh_ptp Probable Cause A threshold crossing alert can be generated for each port PM parameter. The PM parameter is displayed in the Description column of the Events tab. For a 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 Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action Info Info Check PM for the integrity of the communications channel. Temperature is too great. Warning Warning Card overtemp. Check fans and filter. A module s temperature has exceeded 65ºC. A module s temperature has exceeded 59ºC. The expected path trace string (J1 byte in the path overhead) does not match the received path trace string. Minor Minor Check the fan tray for proper functioning. Replace as necessary. Minor Minor Check the fan speed change. The alarm should clear once the fan speed changes. SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, T through TZ

105 Release OPS4.2.2 Force10 Networks Page 1-99 Table 1-11 Alarms, Events and Recommended Actions, T through TZ (continued) Alarm: Definition TIM-P: Trace identifier mismatch - Path TIM-S: Trace identifier mismatch - Section TIM-V: Trail trace mismatch - VT TIU-V: Trail trace unstable -VT TIMEDOUT: Session terminated Alarm Profiles e3_ptp sonet_ptp sonet_sts te50 te206 node e3_ptp sonet_ptp te50 ds1_ptp ds3_ptp (ds_ptp) e3_ptp shelf sdh_ptp sonet_ptp sonet_vt sonet_sts te50 ds1_ptp ds3_ptp (ds_ptp) e3_ptp sdh_ptp sonet_ptp sonet_vt sonet_sts server shelf Probable Cause The expected path trace string does not match the received path trace string. The expected section trace (J0 byte) string does not match the received section trace string. The expected VT trail trace (J2 byte) string does not match the received VT trail trace string. The expected VT trail trace string match at received VT trail trace string is unstable. The user session has been idle for two hours. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. SA Critical Minor Check configuration of section source or cross-connect. Match the section trace string at each end. SA Critical Minor Check configuration of VT trail trace source or cross-connect. Match the VT trail trace string at each end. SA Critical Minor Check configuration of VT trail trace source or cross-connect. Match the VT trail trace string at each end. Info Info Start a new user session. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, T through TZ

106 Page Force10 Networks Release OPS4.2.2 Table 1-11 Alarms, Events and Recommended Actions, T through TZ (continued) Alarm: Definition TIMEOUTWARN: Session terminate warning TIU-V: Trail trace mismatch - VT server shelf The user session has been idle for 1 hour and 55 minutes; the session will terminate in 5 minutes. Info Info Perform a user action to stop session termination. 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 TLCT: Total loss of capacity - transmit TOOMANYEVENTS: Too many events in the server TOPOMIS: Topology mismatch eos eop [ sdh_eos 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. 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. server Server event log too large. Critical Critical Clear event log. sonet_ptp sdh_ptp Topology is mismatched. Minor Minor Check topologies. TOXIC 1 : Toxic gas detected shelf Toxic gas detected. Minor Minor Check and follow your method of procedures TSS-EXTA-OOB-A: Controller A EXT A - Out of Band TSS-EXTA-OOB-B: Controller B EXT A - Out of Band Alarm Profiles shelf shelf Probable Cause Controller A EXT A reference is out of local oscillator qualification frequency range. Controller B EXT A reference is out of local oscillator qualification frequency range. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor If this alarm persists for more than 5 minutes, contact Force10 s Technical Assistance Center (TAC). SA Critical Minor If this alarm persists for more than 5 minutes, contact Force10 s Technical Assistance Center (TAC). Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, T through TZ

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

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

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

110 Page Force10 Networks Release OPS4.2.2 Table 1-11 Alarms, Events and Recommended Actions, T through TZ (continued) Alarm: Definition 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) TU-LOP: Loss of Pointer Tributary Unit TX-OFF-LI:Transmitter off due to link indication TX-ON-LI:Transmitter on due to link indication Alarm Profiles sdh_hp sdh-lp sdh_ptp sdh_hp sdh-lp sdh_ptp 1 Environmental alarm inputs are customized by each operator. Probable Cause An upstream failure occurred at the tributary unit path layer. Valid pointer bytes are missing from the tributary unit overhead. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Minor Check the equipment upstream. Clear upstream alarms. Verify your tributary unit payload connections. SA Critical Minor Check the cabling and physical connections on the reporting card. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. ethernet_ptp The module is in standby mode. Info Info Information only. ethernet_ptp The module is in active mode. Info Info Information only. Recommended Action Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, T through TZ

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

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

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

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

115 Release OPS4.2.2 Force10 Networks Page 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. Table 1-14 Alarms, Events and Recommended Actions, TE-206 TE-206 Alarm AIS: Alarm Indication Signal AIS-L: Alarm Indication Signal - Line AIS-P: Alarm Indication Signal - Path AIS-V: Alarm Indication Signal - VT APSB: APS Protection Switch Byte Failure Corresponding TransNav Alarm(s) DS3 AIS DS1 AIS DS3 AIS-TX DS1 AIS-TX AIS-L AIS-P AIS-P-TX AIS-V APSB Probable Cause The input and export signals on a DS1 or DS3 interface contains an AIS. The input and export signals on a DS1 or DS3 interface contains an AIS. The STS signal demultiplexed from the DS3 contains an AIS which can result from an upstream or downstream failure along the STS path. An upstream failure occurred at the VC path layer. On a 2F BLSR, the APS K1/K2 bytes are in an invalid state. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Minor Info Inspect and clear alarms from the upstream and downstream asynchronous equipment. SA Minor Info Check the equipment (module/port) upstream and downstream. Clear alarms. SA Minor Info Check the equipment (module/port) upstream and downstream. Clear alarms. Verify your payload connections. SA Minor Info Check the equipment (module/port) upstream and downstream. Clear alarms. Verify your VT payload connections Minor Check for OC-N module failures Examine the incoming SONET overhead with an optical test set to confirm inconsistent or invalid K bytes. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

116 Page Force10 Networks Release OPS4.2.2 Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm APSCM: Automatic protection switch (multiplex section protection -MSP) channel mismatch APSMM: Automatic protection switch (multiplex section protection - MSP) mode mismatch AUTOSWSYNCH: Automatic Switch Synchronization CASALIEN: Alien Cassette CASFA: Cassette Fuse Failure CASFLT: Cassette Failure CASINS: Cassette Inserted APSCM APSMM AUTOSWSYNCH EQINV: Equipment invalid HWFAULT: Hardware fault EQPT: Equipment malfunction / failure EQINS Corresponding TransNav Alarm(s) Probable Cause On a 2F BLSR, the local node is not receiving the K1/K2 values it is expecting. There is a mismatch of the protection switching schemes at the two ends of the span. A protection switch to a new timing source has occurred. An invalid piece of equipment has been used. Minor Minor Minor Check protection modes at both ends. Verify that both ends are set for bidirectional or unidirectional. Info Critical Check the timing sources for alarms. Plug in a valid piece of equipment. A hardware fault has occurred. SA Critical Minor Take appropriate action, as necessary. A hardware failure has occurred on the reporting module. A new cassette has been inserted into a TE-206 node. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Minor Check and reseat equipment. If this fails to clear the alarm, replace the equipment if necessary. Info Recommended Action Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TE-206

117 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm CASMM EQMIS Type of equipment plugged in does not match the provisioned type or the module/cassette is not allowed in the slot. CASRMVD: Cassette Removed CMTFLT: Connection to TransNav GUI failed EOC: Embedded Operations Channel Failure ETHBLKTOFWD: Ethernet Transition from Block to Forward ETHRINGFAIL: Invalid Ethernet Ring Configuration EQPT Corresponding TransNav Alarm(s) CM TFLT A cassette has been removed from a TE-206 node. Connection to TE-206 from TransNav GUI failed. 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. BLOCK-TO-FWD ETHRING-FAIL Probable Cause Ethernet port RSTP state has changed from blocking to forwarding. A root bridge has not been configured for the ETHRING. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Major Info Info 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. Check for and resolve any firmware mismatch. Manually commit the software. 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. SA Major Informational only. No action required. Info Recommended Action Configure a root bridge for the ETHRING. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

118 Page Force10 Networks Release OPS4.2.2 Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm EXBER: Excessive Bit Error Rate FDLLPBK: FDL Loopback FEACAIS: DS3 FEAC AIS FEACEQFLTNSA: DS3 FEAC Equipment Failure (NSA) Corresponding TransNav Alarm(s) BERSF-L (OC48/OC12/OC3) BERSF-P (HO path) BERSF-V (VT1.5) RMTLOOP DS3FEAC-AIS DS3FEAC-EQPT(use SA/NSA) Probable Cause 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. Fiber could be bent or damaged. The VT signal demultiplexed and dropped from the OC-N has exceeded its signal fail threshold. Far end DS1 interface has initiated a remote loopback using the FDL channel. The DS3 FEAC channel is receiving AIS indication. The DS3 FEAC channel is receiving Equipment Failure indication. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Critical Minor Verify the local receive optical levels, as well as the upstream transmit levels. Verify good optical connections. Clean optical cable connectors and module ports. If an 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. 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. Info Info Info Recommended Action Check upstream equipment for source of AIS. Check upstream equipment for source of Equipment Failure. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TE-206

119 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm FEACEQFLTSA: DS3 FEAC Equipment Failure (SA) FEACIDLE: DS3 FEAC Idle Signal FEACLOS: DS3 FEAC LOS FEACLPBK: FEAC Loopback FEACOOF: DS3 FEAC OOF FEPRLF: Far End Protection Line Failure FRCDSWRING1: Forced Switch to Ring 1 DS3FEAC-EQPT (use SA/NSA) DS3FEAC-IDLE DS3FEAC-LOS RMTLOOP DS3FEAC-LOF FEP Corresponding TransNav Alarm(s) FORCED Probable Cause The DS3 FEAC channel is receiving Equipment Failure indication. The DS3 FEAC channel is receiving Idle Signal indication. The DS3 FEAC channel is receiving Loss of Signal indication. Far end DS3 interface has initiated a remote loopback using the FEAC channel. The DS3 FEAC channel is receiving Loss of Frame indication. An APS switching channel signal failure has occurred on the protect module coming into the node. A forced protection switch has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) SA Info Check upstream equipment for source of Equipment Failure. Info Info Info Info Recommended Action Check upstream equipment for source of Idle. Check upstream equipment for source of Loss of Signal. Informational only. No action requried. 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). Minor Check the equipment on the other end of the fiber. Info Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

120 Page Force10 Networks Release OPS4.2.2 Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm FRCDSWRING2: Forced Switch to Ring 2 FRCDSWSYNC: Forced Sync Switch FRCDWKSWBK: Forced protection switch on protecting unit FRCDWKSWPR: Forced protection switch on working unit FWMM: Firmware Mismatch FORCED TSS-FRC FORCED_ON_PROT FORCED_ON_WORK None. This is a te206 alarm only A forced protection switch has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. A forced protection switch command has been performed on the BITS or line timing source. A forced protection switch has been performed on a protection group. A forced protection switch has been performed on the working unit. The current running firmware revision does not match the current running software revision. HLDOVR: Holdover TSS-HOLDOVER There are no available external references so the GCMA (or GCMB) is referencing the local oscillator. HWFLT: Description is Fault specific EQPT Corresponding TransNav Alarm(s) Probable Cause A hardware failure has occurred on the reporting cassette. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Info Info Info Major Recommended Action If the reason for executing the forced switch no longer exists, clear the switch command. Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Verify that the reason for performing the forced switch no longer exists. Clear the switch command. Perform firmware upgrade to resolve firmware mismatch. (SA) Major If this alarm persists for more than 5 minutes, contact Force10 s Technical Assistance Center (TAC). SA Critical Minor Check and reseat the equipment or cassette. If this fails to clear the alarm, replace the cassette if necessary. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TE-206

121 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm HWMM: Hardware Mismatch EQMIS Type of equipment plugged in does not match the provisioned type or the module is not allowed in the slot. LOA: Loss of Alignment LOA Differential Delay exceeded on active EOS member. LOC: Loss of Carrier LINKFAIL Transmitter/receiver failure. Fiber connection lost. A module along the path has been removed. LOCKOUTOFPR: Lockout of Protect LOCKOUTRING2: Lockout of Ring 2 Corresponding TransNav Alarm(s) LOCKOUT LOCKOUT Probable Cause A lockout protection switch command has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. A lockout protection switch command has been performed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) 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. SA Critical Minor Check the EOS or EOP member status to determine which paths have exceeded the delay and reroute them. SA Critical Minor Check connectors, cables, and modules. Check Ethernet port configuration, Integrity Status parameter for details. See the TransNav Management System GUI Guide, Section 5 Equipment, Chapter 4 Ethernet Equipment, Ethernet Equipment, page Info Info Recommended Action If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. If protection required, investigate and remedy lockout provisioning. Otherwise, no action required. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

122 Page Force10 Networks Release OPS4.2.2 Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm LOF: Loss of Frame Corresponding TransNav Alarm(s) LOF (OC48/OC12/OC3) DS1LOF DS3LOF Probable Cause Framing problem on the incoming OC-N signal. LOL: Loss of Light LINKFAIL Transmitter/receiver failure. Fiber connection lost. A module along the path has been removed. SA Critical Minor Inspect all facilities related to the OC-N link. Verify the local receive optical levels, as well as the upstream transmit optical levels. Clean the optical connectors. Check the upstream node for OC-N module failure/removal. Verify good optical connections to the local and far-end OC-N modules. SA Critical Minor Check connectors, cables, and modules. Check Ethernet port configuration, Integrity Status parameter for details. See the TransNav Management System GUI Guide, Section 5 Equipment, Chapter 4 Ethernet Equipment, Ethernet Equipment, page 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. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. Verify that the expected bandwidth and received bandwidth are the same. If the alarm persists, replace the module. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TE-206

123 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm 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. LOSYNC: Loss of Synchronization LPBK-FAC: Facility Loopback Active LPBK-TERM: Terminal Loopback Active MANSWRING1: Manual Switch to Ring 1 Corresponding TransNav Alarm(s) LINKFAIL Transmitter/receiver failure. Fiber connection lost. A module along the path has been removed. LPBKFACILITY Facility is in active loopback state. SA Critical Minor Check the cabling and physical connections on the reporting module. Verify cross-connects. Check network timing synchronization. If the alarm persists, replace the module. SA Critical Minor Check the upstream node for OC-N module failure/removal. Check the fiber connection. Verify the receive optical levels. Verify good optical connections to the local and far-end OC-N modules. SA Critical Minor Check connectors, cables, and modules. Check Ethernet port configuration, Integrity Status parameter for details. See the TransNav Management System GUI Guide, Section 5 Equipment, Chapter 4 Ethernet Equipment, Ethernet Equipment, page Info Validate this state. Clear loopback, as required. LPBKTERM A terminal loopback is active. Info Validate this state. Clear loopback, as required. MANUAL Probable Cause A manual protection switch has been executed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Recommended Action Informational; no action required. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

124 Page Force10 Networks Release OPS4.2.2 Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm MANSWRING2: Manual Switch to Ring 2 MANSWSYNC: Manual protection switching on timing MANWKSWBK: Manual Switch to Working MANWKSWBK: Manual Switch to Working MANWKSWPR: Manual Switch to Protect MANWKSWPR: Manual Switch to Protect OSPFAIMM: OSPF Area ID Mismatch OSPFHIMM: OSPF Hello Interval Mismatch Corresponding TransNav Alarm(s) MANUAL TSS-MAN MAN_ON_PROT MAN_ON_PROT MAN_ON_WORK MAN_ON_WORK OSPF-AIMM OSPF-HIMM Probable Cause A manual protection switch has been executed on a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. A manual protection switch command has been performed on the BITS or line timing source. A manual protection switch has been executed on the protecting port of a protection group. A manual protection switch has been executed on the protecting port of a protection group. A manual protection switch has been executed on a working port of a protection group. A manual protection switch has been executed on a working port of a protection group. The OSPF Area configuration does not match the configuration of other routers in the network. The OSPF Hello Interval does not match the configuration of other routers in the network. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info Info Info Informational; no action required. If the reason for executing the manual switch no longer exists, clear the switch command. Informational; no action required. Informational; no action required. Info Info Informational; no action required. Info Info Informational; no action required. Info Info Recommended Action Configure the OSPF Area to be consistent in the network. Configure the OSPF Hello Interval to be consistent in the network. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TE-206

125 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm OSPFRDIMM: OSPF Router Dead Interval Mismatch PLM-P: Payload Label Mismatch PLM-V: VT Payload Label Mismatch VT Path PWRA: Low -48V Power Side A PWRB: Low -48V Power Side B PWRHI: Excessive (in Absolute Value) - 48V Power OSPF-DIMM PLM-P Corresponding TransNav Alarm(s) The OSPF Router Dead configuration does not match the configuration of other routers in the network. Payload label mismatch on the path. PLM-V Invalid byte in the path overhead. The payload does not match what the signal label is reporting. PWFAIL-A PWFAIL-B PWR-48 in TR docs Probable Cause GMT A fuse, cabling, circuit breaker, or power system unit has failed. GMT B fuse, cabling, circuit breaker, or power system unit has failed. Commercial fuse, cabling, circuit breaker, or power system unit has failed. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Configure OSPF Router Dead to be consistent in the network. SA Critical Minor Verify that the payload is the same as the provisioned payload/service. Minor Minor Minor Major Recommended Action Connect correct payload. Verify that the payload is the same as the provisioned payload/service. Check power system, breaker, fuse, and related cabling for power input A. Check power system, breaker, fuse, and related cabling for power input B. Check and follow your method of procedures. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

126 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm RAI: Remote Alarm Indication RFI-L: Remote Failure Indication - Line RFI-P: Remote Failure Indication - Path RFI-V: Remote Failure Indication - VT DS3RAI DS1RA DS3RAI-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. 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. RFI-P RFI-V Corresponding TransNav Alarm(s) Probable Cause The STS-1 signal demultiplexed from the OC-N contains an RFI-P. The far-end node has detected path defects coming from the local site. 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. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Recommended Action 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. 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. 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. 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. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

127 Page Force10 Networks Release OPS4.2.2 Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm RFLF: Remote Line Failure RFOFF: Remote Fault Offline SD: Bit ErrorRate signal degrade Line None. This is a te206 alarm only. BERSD-L (OC48/OC12/OC3) BERSD-P (HO Path) BERSD-V (VT1.5) The far end GbE interface is detecting a Loss of Signal. The BER on the incoming EC-1 line has exceeded the signal degrade threshold. SFPALIEN: Alien SFP SFP-UNKNOWN An SFP has been detected that is not certified for use with the system. SFPFLT: SFP Fault SFPFAIL A fault has been detected with the SFP. SFPMM: SFP Mismatch SFPMIS There is a mismatch on the SFP interface. SNTPFLT: SNTP Time Failure SOFTMM: Software Version Mismatch Corresponding TransNav Alarm(s) SNTP-FAIL SWMIS Probable Cause The TE-206 cannot communicate with the SNTP server. The reporting module is not running with the same software version as the active GCM. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info Check the GbE fiber. Info 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. SA Critical Minor Replace the unknown SFP with a Force10 certified SFP. SA Critical Minor Replace the faulty SFP. SA Critical Minor Check interface. 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. Major Recommended Action Reinstall correct software. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TE-206

128 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm SQM: Sequence number change SUM-V: VT Alarm Summary SWRING1: Auto Switch to Ring 1 SWRING2: Auto Switch to Ring 2 SYNC: System reference lock failed SYNCHSTATCHNG: Sychronization Status Message Change TCA: Threshold Crossing Alert TIM-P: Trace Identifier Mismatch - Path SQM Unused SA Critical Minor Unused for ethernet_ptp and shelf. Member alarm for virtual concatentation faults on EOP members. SUM-V SWITCH_TO_WORK SWITCH_TO_PROTECT One or more alarms exist for VT paths within the STS-1. 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. Traffic has switched to the standby module, port, or channel for a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group. SA Critical Minor Check teh conditions on the VT paths within the STS-1. Info Verify that the switch was expected. Check the switch-from section for degraded performance or other relevant alarm conditions. Info Informational; no action required. SYSREF Lock on system reference is lost. Minor Check system reference. SYNCHSTATCHNG TCA TIM-P Corresponding TransNav Alarm(s) Probable Cause The Synchronization Status messages has changes on the timing reference. The associated Performance Monitoring parameter has crossed the configured threshold. The expected path trace string does not match the received path trace string. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Info Recommended Action Informational; no action required. Minor Check configuration of path source or cross-connect. Match the path trace string on both ends of the path. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

129 Page Force10 Networks Release OPS4.2.2 Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm UNEQ-P: Unequipped code signal label received or transmitted UNEQ-V: Unequipped code signal label received - VT path WKSWBK: Auto Switch to Working WKSWBK: Auto Switch to Working WKSWPR: Auto Switch to Protect WKSWPR: Auto Switch to Protect Corresponding TransNav Alarm(s) UNEQ-P UNEQ-P-TX UNEQ-V SWITCH_TO_WORK APS-PROTECT SWITCH_TO_PROT APS-WORK Probable Cause Unequipped code signal label received or transmitted No payload is received on an activated service. 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. A protection switch to the working facility that occurred because of an alarm clearing or Wait-To-Restore timer option. 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. A protection switch to the working facility that occurred because of an alarm on the working facility. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Minor Minor Check your interface connection. Connect your proper payload and service source. Info Verify that the switch was expected. Check the switch-from section for degraded performance or other relevant alarm conditions. Info Info Info Recommended Action Informational; no action required. Informational; no action required. Operations and Maintenance Guide, Section 1: Fault Management Alarms/Events, TE-206

130 Release OPS4.2.2 Force10 Networks Page Table 1-14 Alarms, Events and Recommended Actions, TE-206 (continued) TE-206 Alarm WLMM: Configured wavelength mismatch with hardware WTR: Transition to Wait to Restore mode (multiplex section protection - MSP) Corresponding TransNav Alarm(s) WLMIS Incorrect provisioning. SA Critical Minor Check interface and configuration. APSWTR Probable Cause Traffic is in the process of switching back to working channels. This occurs when a 1:1 equipment, 1+1 facility, or BLSR/MS-SP Ring protection group has been configured as revertive. Service Affecting Default Default Severity SA (Unprotected) NSA (Protected) Info Recommended Action If frequent protection switching occurs, check the revertive WTR period setting. Chapter 2 Alarms, Events, and Recommended Actions Alarms/Events, TE-206

131 Chapter 2 Alarms, Events, and Recommended Actions Release OPS4.2.2 Force10 Networks Page 1-125

132 Operations and Maintenance Guide, Section 1: Fault Management Page Force10 Networks Release OPS4.2.2

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

134 Operations and Maintenance Guide, Section 1: Fault Management Service Activation Failure Service Activation Failure If a service request activation fails, use the following Service Request Show Last Error procedure to help trace and resolve the problem. Table 1-15 Service Request Show Last Error Step Procedure 1 Select the service request entry. Service Request Entry Service Error Code Information Figure 1-16 Service Request Failure 2 From the Services menu, select Show Last Error. Activation Failure Indication Figure 1-17 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 for further troubleshooting details. 4 The Service Request Show Last Error procedure is complete. Page Force10 Networks Release OPS4.2.2

135 Release OPS4.2.2 Force10 Networks Page TransNav GUI Service Error Codes TransNav GUI service error codes are listed in the following table in ascending, numerical order. Each error code table entry contains the following information: The service error code as visible in the service request error window. Service error code string definition as visible in the service request error window. Probable cause(s) for service request failure. Recommended action(s) to take upon receiving the service error code indication. Table 1-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 RSVP (resource reservation protocol) error - MIB SET operation failed 1008 RSVP (resource reservation protocol) error - MIB GET operation failed 1009 RSVP (resource reservation protocol) error - MIB TEST operation failed 1016 RSVP (resource reservation protocol) error - No path for reservation Residual resources from a previous service were not cleared due to a switchover. (e.g., a service deletion request in process when a switchover occurred.) Residual resources from a previous service were not cleared due to a switchover. (e.g., a service deletion request in process when a switchover occurred.) Residual resources from a previous service were not cleared due to a switchover. (e.g., a service deletion request in process when a switchover occurred.) Remote node or link failure. Try to deactivate/reactivate the new service. If deactivation/reactivation does not resolve the problem, then perform a GCM switchover. As a last resort, restart the node. Try to deactivate/reactive the new service. If deactivation/reactivation does not resolve the problem, then perform a GCM switchover. As a last resort, restart the node. Try to deactivate/reactive the new service. If deactivation/reactivation does not resolve the problem, then perform a GCM switchover. As a last resort, restart the node. Retry service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

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

137 Release OPS4.2.2 Force10 Networks Page Table 1-16 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 1209 Invalid Protection interface Unsupported interface identified in the request. For example, an Ethernet I/F in 1+1 protection group request Resources not available Port is locked STS is completely used 1215 Error while processing a service request Card not responding. Check the interface specified in the original request. Make a new request with a valid interface. Unlock the port Select a different STS with sufficient bandwidth Reseat the 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 Interface already exists The interface is already in use. Make another interface selection and retry the service request Slot already exists The slot is already in use. Make another slot selection and retry the service request PG (protection group) already exists The protection group is already in use. Make another protection group selection and retry the service request Interface exists in a protection group The interface is already in use in a protection group. Make another interface selection and retry the service request Slot exists in a PG (protection group) 1227 PG (protection group) already used by a service The slot is already in use in a protection group. The protection group is already in use. Make another slot selection and retry the service request. Make another protection group selection and retry the service request Interface already used by a service The interface is already in use in a service. Make another interface selection and retry the service request Slot already used by a service The slot is already in use in a service. Make another slot selection and retry the service request Error in processing UPSR (unidirectional path switched ring) request Probable Cause Trying to use an unavailable UPSR protection group. Recommended Action Create the UPSR protection group and retry the service request. Chapter 3 TransNav GUI Service Error Codes TransNav GUI Service Error Codes

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

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

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

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

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

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

144 Page Force10 Networks Release OPS4.2.2 Table 1-16 Service Error Codes and Recommended Actions (continued) Service Error Code Service Error Code String Definition 3247 No free traffic contracts are available on the Ethernet card specified in service 3256 EA is not ready to receive MP requests 3271 Maximum number of TDM endpoints bound to Ethernet card 3272 Maximum number of TLS TDM endpoints bound to Ethernet card 3273 Maximum number of TLS instances on Ethernet card Probable Cause 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. Ethernet management command occurs while the GCM is still initializing and unable to handle the request. A large number of Ethernet requests occur in a very short period of time. SONET endpoint resource allocation failure during service request. All SONET endpoints are already in use. Each Ethernet card supports (typically) 24 SONET endpoints. The limit for Transparent LAN Service (TLS) SONET endpoints has been reached. There can only be a maximum of two TLS SONET endpoints on an Ethernet 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. Recommended Action Deactivate some service using a traffic contract to free up resources and retry the new service request. Retry the service request as this is a transient condition. Deactivate the conflicting service using the SONET endpoint and retry the new service request. Deactivate all services using one of the other TLS SONET endpoints and retry the new service request. Deactivate all of the active services using another TLS instance and retry the service request. Operations and Maintenance Guide, Section 1: Fault Management TransNav GUI Service Error Codes

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

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

147 SECTION 2 PERFORMANCE MONITORING SECTION 2 SECTION 2 Contents Chapter 1 Managing Performance Creating or Modifying a Monitoring Template Assigning a PM Template to a Traverse Node Assigning a Port PM Template Assigning an EOS Port PM Template Assigning an EOP Port PM Template Changing a Member PDH PM Template for an EOP PDH Member Assigning a Subport PM Template Assigning a Service PM Template Viewing PM Data PM Timing Viewing Port or Subport PM Data Viewing Service Path PM Data Viewing Signal Path Trace Data Viewing Capacity Monitoring Data Report Generation Generating a PM Report Generating Reports for Traverse nodes Generating Reports for TE-206 nodes Assigning a Template to a TE-206 Node Scheduling TE-206 PM Collection Times Chapter 2 SONET Performance Parameters DS1 Port PM DS3 Port PM EC-1 Port PM SONET Port PM SONET STS Path Layer PM SONET VT Path Layer PM SONET Capacity Monitoring Chapter 3 SDH Performance Parameters Release OPS4.2.2 Force10 Networks Page i

148 Operations and Maintenance Guide, Section 2 Performance Monitoring E1 Port PM E3 Port PM SDH High and Low Order Path PM SDH Port PM SDH VC-11 and VC-12 Path PM SDH Capacity Monitoring Chapter 4 Ethernet Performance Parameters Ethernet 10GbE Equipment PM EoPDH Equipment PM Ethernet Equipment PM Ethernet Port PM Ethernet Service Port PM EOS Port PM EOP Port PM Parameters EOP Port PM EOP Port Member PM Small Form-Factor Pluggable Optical Port PM Page ii Force10 Networks Release OPS4.2.2

149 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-6 Viewing PM Data, page 2-10 PM Timing, page 2-10 Viewing Capacity Monitoring Data, page 2-17 Report Generation, page 2-18 Generating a PM Report, page 2-19 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. Use the following procedures to set up and view performance monitoring data on TE-206 nodes from TransNav: 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. Assigning a Template to a TE-206 Node, page 2-20 Scheduling TE-206 PM Collection Times, page 2-21 Release OPS4.2.2 Force10 Networks Page 2-1

150 Operations and Maintenance Guide, Section 2: Performance Monitoring Creating 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. 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. The following procedure describes how to create or modify a monitoring template. Page 2-2 Force10 Networks Release OPS4.2.2

151 Chapter 1 Managing Performance Creating or Modifying a Monitoring Template Table 2-1 Creating or Modifying a PM Template Step Procedure 1 In Map View, select Admin, then Performance Templates. The Performance Templates dialog box displays. Figure 2-1 Performance Templates Dialog Box Release OPS4.2.2 Force10 Networks Page 2-3

152 Operations and Maintenance Guide, Section 2: Performance Monitoring Creating or Modifying a Monitoring Template Table 2-1 Creating or Modifying a PM Template (continued) Step Procedure 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 Page 2-4 Force10 Networks Release OPS4.2.2

153 Chapter 1 Managing Performance Creating or Modifying a Monitoring Template Table 2-1 Creating or Modifying a PM Template (continued) Step Procedure 3 Creating a template? Yes. Go to the next step. No. Go to Step 5. 4 Click Add, then enter a Name for the template. Go to Step 6. Note: Force10 recommends making a copy of the default template and naming it original. This will avoid 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 Traverse Provisioning Guide, Chapter 4 Generating and Viewing Reports, Generating Reports, page Release OPS4.2.2 Force10 Networks Page 2-5

154 Operations and Maintenance Guide, Section 2: Performance Monitoring Assigning a PM Template to a Traverse Node Table 2-1 Creating or Modifying a PM Template (continued) Step Procedure 9 Click OK. The example shown below is a DS1 port performance monitoring template with standard default values and Collect (for the Report function) set. Figure 2-2 DS1 PM Configuration Template Dialog Box 10 Click Yes to synchronize the template to make it available to other nodes. Click No if you do not want to synchronize the new template. Figure 2-3 Synchronize Template Dialog Box 11 Click Done in the Performance Templates dialog box. 12 The Creating or Modifying a PM Template procedure is complete. 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-7 Assigning an EOS Port PM Template, page 2-7 Assigning an EOP Port PM Template, page 2-8 Assigning a Subport PM Template, page 2-9 Assigning a Service PM Template, page 2-9 Page 2-6 Force10 Networks Release OPS4.2.2

155 Chapter 1 Managing Performance Assigning an EOS Port PM Template Assigning a Port PM Template The following procedure describes how to assign a port PM template to a card 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. Assigning an EOS Port PM Template The following procedure describes how to assign an EOS port PM template to an EOS port. Table 2-3 Assigning an EOS Port PM Template Step Procedure 1 In Shelf View, click the Ethernet tab. 2 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. Release OPS4.2.2 Force10 Networks Page 2-7

156 Operations and Maintenance Guide, Section 2: Performance Monitoring Assigning an EOP Port PM Template Assigning an EOP Port PM Template The following procedure describes how to assign an EOP port PM template to an EOP port. Table 2-4 Assigning an EOP Port PM Template Step Procedure 1 In Shelf View, click the Ethernet tab. 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. 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 Traverse Provisioning Guide, Section 7 Configuring Ethernet, Chapter 6 Ethernet Over PDH (EOP), Creating EOP Ports, page Table 2-5 Changing a Member PDH PM Template for EOP PDH Members Step Procedure 1 In Shelf View, click the Ethernet tab. 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. Page 2-8 Force10 Networks Release OPS4.2.2

157 Chapter 1 Managing Performance Assigning a Service PM Template Assigning a Subport PM Template The following procedure describes how to assign a port PM template to a DS3 Transmux subport. Table 2-6 Assigning a Subport PM Template Step Procedure 1 In Shelf View, select a DS3 Transmux card port. 2 Click the Config tab. 3 From the Subport row, PM Template column list, select a port (ptp) PM template matching the embedded signal subport type (e.g., ds1_ptp). 4 Click Apply. 5 The Assigning a Subport PM Template procedure is complete. Assigning a Service PM Template The following procedure describes how to assign a path PM template to a service. The service PM template is selected during service creation or editing. Table 2-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. Release OPS4.2.2 Force10 Networks Page 2-9

158 Operations and Maintenance Guide, Section 2: Performance Monitoring Viewing PM Data Table 2-7 Assigning a Service PM Template (continued) Step Procedure 4 The Advanced Parameters dialog box appears. From the Source PM Template and Destination PM Template or Service Port PM list, select a PM template. 4 3 Figure 2-4 Service PM Template Parameters 5 Click Done and continue creating or editing the service. 6 The Assigning a Service PM Template procedure is complete. 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-11 Viewing Service Path PM Data, page 2-13 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. To schedule PM data for TE-206 nodes, see the following section: Scheduling TE-206 PM Collection Times, page 2-21 Page 2-10 Force10 Networks Release OPS4.2.2

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

160 Operations and Maintenance Guide, Section 2: Performance Monitoring Viewing Port or Subport PM Data Table 2-8 Viewing Port or Subport PM Data (continued) Step Procedure 3 Click Refresh to re-display updated PM values. 2a 2b Figure 2-6 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. Page 2-12 Force10 Networks Release OPS4.2.2

161 Chapter 1 Managing Performance Viewing Service Path PM Data Viewing Service Path PM Data The following procedure describes how to view service path PM data. Table 2-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. 2 4a 3 4b 5 Figure 2-7 Path Display for Services Screen 3 Click the PM (Performance) tab to display the PM screen. 4 From the Path Display for Service screen, for either a Tx or Rx table row, select an Active or Standby Hop (4a). Your selection appears in the Hop Id field on the PM tab (4b). 5 Click the Refresh button on the PM tab to display the performance monitoring data. Release OPS4.2.2 Force10 Networks Page 2-13

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

163 Chapter 1 Managing Performance Viewing Signal Path Trace Data Viewing Signal Path Trace Data The following procedure describes how to view transmission and received signal path trace information. Table 2-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. 2 4a 3 4b 5 Figure 2-9 Path Display for Service Screen 3 Click the CTP tab to display the CTP screen. 4 From the Path Display for Service screen, for either a Tx or Rx table row, select an Active Hop (4a). Your selection appears in the EndPoint field on the CTP tab (4b). Release OPS4.2.2 Force10 Networks Page 2-15

164 Operations and Maintenance Guide, Section 2: Performance Monitoring Viewing Signal Path Trace Data Table 2-10 Viewing Signal Path Trace Data (continued) Step Procedure 5 In the Alarm Profile field, one of the following profile values displays: useparent: The alarm profile of the containing object (Parent) based on the following superset and subset definitions: Port: Contains line and path alarms and is the superset. High-order path: Contains high- and low-order path alarms and is a subset of port profiles. Low-order path: Contains only low-order path alarms and is a finer subset of high-order path profiles. STS path. Contains STS and VT path alarms and is a subset of port profiles. VT path: Contains only VT path alarms and is a finer subset of STS path profiles. default: The default alarm profile matching the CTP object type. <user-defined>: Depending on the CTP object type, this value indicates a user-defined alarm profile of one of the following path alarm profile types: sdh_hp sdh_lp sonet_sts sonet_vt 6 Click Received/Transmitted Path Overhead. The Received/ Transmitted Path Overhead dialog box displays. (The name of the button and the resulting dialog box corresponds to whether you selected a Tx or Rx active hop.) Figure 2-10 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. Page 2-16 Force10 Networks Release OPS4.2.2

165 Chapter 1 Managing Performance Viewing Capacity Monitoring Data Viewing Capacity Monitoring Data The following procedure describes how to view VT or TU capacity monitoring data. The capacity monitoring data shows the numbers of paths used or available at the instant the information is captured. Unlike the performance monitoring data, the capacity monitoring data is not accumulated for each period. If the VT card where the capacity is being monitored is in a 1:n protection group, only the capacity of the working card will be collected. Table 2-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 (2a) list (see the graphic in the next step), you can select 15-minute or 24-hour intervals. You can view up to thirty-two 15-minute or two 24-hour Samples (2b) current and previous. 3 Click Refresh to re-display updated capacity monitoring values. 2a 2b Figure 2-11 Viewing VT/TU Capacity Monitoring Data 4 If you click Reset, an error message displays. The counters do not reset to zero. 5 Click Print to print the current screen. 6 Click Save to save the capacity monitoring data to a file. 7 The Viewing VT/TU Capacity Monitoring Data procedure is complete. Release OPS4.2.2 Force10 Networks Page 2-17

166 Operations and Maintenance Guide, Section 2: Performance Monitoring Report 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-12 Event Report Sample Page 2-18 Force10 Networks Release OPS4.2.2

167 Chapter 1 Managing Performance Generating 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 4 Generating and Viewing Reports, Using the Report Scheduler, page 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, page 2-2. Table 2-12 PM Report Generation Step Procedure 1 From the Admin menu, select Reports. The Reports screen displays ,4 5 Figure 2-13 Reports Screen 2 Select a PM report from the Report Schedulers list. 3 Click Generate Now. Entries appear in the Report List section. 4 Select a Report List entry. 5 Click View Report. 6 The PM Report Generation procedure is complete. Release OPS4.2.2 Force10 Networks Page 2-19

168 Operations and Maintenance Guide, Section 2: Performance Monitoring Assigning 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. 2 2 Click the Config tab (2). Figure 2-14 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. Page 2-20 Force10 Networks Release OPS4.2.2

169 Chapter 1 Managing Performance Scheduling 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: 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-15 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. To generate a PM report for a TE-206 node from TransNav, follow the instructions in Generating a PM Report. Release OPS4.2.2 Force10 Networks Page 2-21

170 Operations and Maintenance Guide, Section 2: Performance Monitoring Scheduling TE-206 PM Collection Times Page 2-22 Force10 Networks Release OPS4.2.2

171 SECTION 2PERFORMANCE MONITORING Chapter 2 SONET Performance Parameters Introduction This chapter provides performance parameter information for: DS1 Port PM, page 2-24 DS3 Port PM, page 2-27 EC-1 Port PM, page 2-30 SONET Port PM, page 2-33 SONET STS Path Layer PM, page 2-38 SONET VT Path Layer PM, page 2-40 SONET Capacity Monitoring, page 2-42 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 the management system, see the TransNav Management System GUI Guide. Release OPS4.2.2 Force10 Networks Page 2-23

172 Operations and Maintenance Guide, Section 2: Performance Monitoring DS1 Port PM DS1 Port PM The Traverse system provides near- and far-end DS1 port PM parameters (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) ES (Errored Seconds) SES (Severely Errored Seconds) LOSS (Loss of Signal Seconds Path Near End CV (Code Violations) ES (Errored Seconds) SES (Severely Errored Seconds) Count of both bipolar violations (BPV) and excessive zeros (EXZ) occurring over the accumulation period. An EXZ increments the CV Line count by one regardless of the length of the zero string. Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded. Count of 1-second intervals during which BPVs plus EXZs exceed 1544, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded. Count of one or more 1-second intervals containing LOS defects. Count of frame synchronization bit errors in the SF format or a count of CRC-6 errors in the ESF format. Count of 1-second intervals containing any of the following: CRC-6 errors (ESF) CS events (ESF, SF) SEF defects (ESF, SF) LOS defects (ESF, SF) FE errors (SF) Count of 1-second intervals containing: 320 or more CRC-6 errors (ESF) 8 or more FE events (SF) one or more SEF or LOS defects (ESF, SF) Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: 100 Page 2-24 Force10 Networks Release OPS4.2.2

173 Chapter 2 SONET Performance Parameters DS1 Port PM Table 2-15 DS1 Port PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold AISS (Alarm Indication Signal Seconds) Count of 1-second intervals containing one or more AIS defects 1 63 Default: 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 Default: Default: 17 CSS (Controlled Slip Seconds Counts of 1-second intervals containing one or more controlled slips Default: Default: 17 UAS (Unavailable Seconds) Count of 1-second intervals for which the DS1 path is unavailable Default: 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 Default: Default: 40 Table 2-16 DS1 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Line Far End 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 Default: Default: 648 Release OPS4.2.2 Force10 Networks Page 2-25

174 Operations and Maintenance Guide, Section 2: Performance Monitoring DS1 Port PM Table 2-16 DS1 Port PM Parameters Far End (continued) Parameter Definition 15-min Threshold Daily Threshold Path Far End CV (Code Violations) ES (Errored Seconds Path) SES (Severely Errored Seconds Path) SEFS (Severely Errored Framing Seconds Path) CSS (Controlled Slip Seconds Path) UAS (Unavailable Seconds Path) FC (Failure Count Path) Count of frame synchronization bit errors (FE) in the SF format or a count of CRC-6 errors in the ESF format. Count of 1-second intervals containing any of the following: CRC-6 errors (ESF) CS events (ESF, SF) SEF defects (ESF, SF) LOS defects (ESF, SF) FE errors (SF) Count of 1-second intervals containing: 320 or more CRC-6 errors (ESF) 8 or more FE events (SF) 1 or more SEF or LOS defects (ESF, SF) Count of 1-second intervals containing one or more SEF defects. Counts of 1-second intervals containing one or more controlled slips. Count of 1-second intervals for which the DS1 path is unavailable Default: Default: Default: Default: Default: Default: 10 Count of far-end path failure (RAI) events Default: Default: Default: Default: Default: Default: Default: Default: 100 Page 2-26 Force10 Networks Release OPS4.2.2

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

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

177 Chapter 2 SONET Performance Parameters DS3 Port PM Table 2-18 DS3 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Path PBit Far End FCFE (Failure Counts) Path CBit Far End CVFE (Code Violations) ESFE (Errored Seconds) SESFE (Severely Errored Seconds) UASFE (Unavailable Seconds 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. Counted when the three FEBE bits in an M-frame are not all set to 1. 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. 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. Count of 1-second intervals during which the DS3 path is unavailable Default: Default: Default: Default: Default: Default: Default: Default: Default: Default: 10 Release OPS4.2.2 Force10 Networks Page 2-29

178 Operations and Maintenance Guide, Section 2: Performance Monitoring EC-1 Port PM EC-1 Port PM The Traverse system provides near- and far-end EC-1 port PM parameters. Table 2-19 EC1 Port PM Parameters Near-End Parameter Definition 15-min Threshold Daily Threshold SECTION CV (Code Violations) Count of BIP-8 errors that are detected at the section layer of the incoming signal. Count of BIP errors detected at the section layer (i.e., using the B1 bytes in the incoming SONET signal). Up to 8 section BIP errors can be detected per STS-N frame, with each error incrementing the CV-S register Default: Default: 3820 ES (Errored Seconds) Count of 1-second intervals during which (at any point during the second) at least one section layer BIP error was detected or an SEF or LOS defect was present Default: Default: 250 SES (Severely Errored Seconds) Count of the seconds during which 154 or more section layer BIP errors were detected or an SEF or LOS defect was present Default: Default: 40 SEFS (Severely Errored Framing Seconds) Count of 1-second intervals during which (at any point during the second) an SEF defect was present. An SEF defect is detected when an incoming signal has a minimum of four consecutive errored framing patterns Default: Default: 8 LINE 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 Default: Default: 3865 ES (Errored Seconds) Count of the seconds during which (at any point during the second) at least one Line layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present Default: Default: 250 SES (Severely Errored Seconds) Count of the seconds during which 52 or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present Default: Default: 40 Page 2-30 Force10 Networks Release OPS4.2.2

179 Chapter 2 SONET Performance Parameters EC-1 Port PM Table 2-19 EC1 Port PM Parameters Near-End (continued) Parameter Definition 15-min Threshold Daily Threshold UAS (Unavailable Seconds) Count of the seconds during which the Line was considered unavailable. A Line becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ls, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ls Default: Default: 40 FC (Failure Counts) Count of the number of near-end Line failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 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 Default: 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 Default: 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 Default: Default: 40 Release OPS4.2.2 Force10 Networks Page 2-31

180 Operations and Maintenance Guide, Section 2: Performance Monitoring EC-1 Port PM Table 2-20 EC1 Port PM Parameters Far-End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 Default: 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 Default: Default: 40 Table 2-21 SFP (and XFP) Optical Port PM Parameters Parameter Measured Temperature Measured Supply Voltage Measured TX Bias Current Measured TX Output Power Measured TX Input Power Definition A measure of the internal transceiver temperature yielding a value within the total range of -128 to +128 celsius. A measure of the internal transceiver supply voltage yielding a value within the total range of 0 to volts. A measure of the TX bias current yielding a value within the total range of 0 to 131 ma. A measure of the TX output power based on the measurement of laser monitor photodiode current and yielding a value within the total range of 0 to mw. A measure of the TX input power yielding a value within the total range of 0 to mw (~ -40 to +8.2 dbm). Absolute accuracy is dependent upon the exact optical wavelength. Page 2-32 Force10 Networks Release OPS4.2.2

181 Chapter 2 SONET Performance Parameters SONET Port PM SONET Port PM The Traverse system provides the following near- and far-end SONET port performance monitoring parameters. Important: Default threshold values in the sonet_ptp_pm template are based on performance monitoring for OC-3 rates. Force10 recommends customizing this template for rates other than OC-3. Table 2-22 SONET Port PM Near End Parameter Definition 15-min Threshold Daily Threshold 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 Default: Default: 3820 ES (Errored Seconds) Count of 1-second intervals during which (at any point during the second) at least one Section layer BIP error was detected or an SEF or LOS defect was present Default: Default: 250 SES (Severely Errored Seconds) Count of the seconds during which K or more Section layer BIP errors were detected or an SEF or LOS defect was present. K has the following values: 154 for OC3 615 for OC for OC for OC Default: Default: 40 SEFS (Severely Errored Framing Seconds) Count of 1-second intervals during which (at any point during the second) an SEF defect was present. An SEF defect is detected when an incoming signal has a minimum of four consecutive errored framing patterns Default: Default: 8 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 Default: Default: 3820 Release OPS4.2.2 Force10 Networks Page 2-33

182 Operations and Maintenance Guide, Section 2: Performance Monitoring SONET Port PM Table2-22 SONET Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 Default: 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 Default: Default: ES (Errored Seconds) Count of the seconds during which (at any point during the second) at least one Line layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present Default: Default: 250 SES (Severely Errored Seconds) Count of the seconds during which K or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: 154 for OC3 615 for OC for OC for OC Default: Default: 40 Page 2-34 Force10 Networks Release OPS4.2.2

183 Chapter 2 SONET Performance Parameters SONET Port PM Table 2-22 SONET Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold UAS (Unavailable Seconds) Count of the seconds during which the Line was considered unavailable. A Line becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ls, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ls Default: Default: 40 FC (Failure Counts) Count of the number of near-end Line failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 Table 2-23 SONET Port PM Parameters Far End Parameter Definition 15-min Threshold 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 Default: Default: 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 Default: Default: 250 Release OPS4.2.2 Force10 Networks Page 2-35

184 Operations and Maintenance Guide, Section 2: Performance Monitoring SONET Port PM Table2-23 SONET Port PM Parameters Far End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 OC for OC for OC Default: 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 Default: Default: 40 FCFE (Failure Counts) Count of the number of far-end Line failure events. A failure event begins when the RFI-L failure is declared, and ends when the RFI-L failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: 40 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 Default: 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) Default: Default: 40 Page 2-36 Force10 Networks Release OPS4.2.2

185 Chapter 2 SONET Performance Parameters SONET Port PM Table 2-23 SONET Port PM Parameters Far End (continued) Parameter Definition 15-min Threshold 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 Default: 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) Default: Default: 40 Release OPS4.2.2 Force10 Networks Page 2-37

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

187 Chapter 2 SONET Performance Parameters SONET STS Path Layer PM Table 2-25 SONET STS Path PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold 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 Default: Default: ESFE (Errored Seconds) Count of the seconds during which (at any point during the second) at least one STS Path BIP error was reported by the far-end STS PTE (using the REI-P indication), a one-bit RDI-P was present, or (if ERDI-P is supported) an ERDI-P Server or Connectivity defect was present Default: Default: 250 SESFE (Severely Errored Seconds) Count of the seconds during which 2400 or more STS Path BIP errors were reported by the far-end STS PTE, a one-bit RDI-P was present, or (if ERDI-P is supported) an ERDI-P Server or connectivity defect was present. The number of reported far-end BIP errors causing a second to be considered an SES-PFE Default: Default: 40 UASFE (Unavailable Seconds) Count of the seconds during which the STS Path is considered unavailable at the far end. A path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES-PFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-PFEs Default: Default: 40 Release OPS4.2.2 Force10 Networks Page 2-39

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

189 Chapter 2 SONET Performance Parameters SONET VT Path Layer PM Table 2-27 SONET VT Path PM Parameters Far End Parameter Definition 15-min Threshold 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 Default: Default: ESFE (Errored Seconds) Count of the seconds during which (at any point during the second) at least one VT Path BIP error was reported by the far-end VT PTE (using the REI V indication), a one-bit RDI V defect was present, or (if ERDI V is supported) an ERDI V Server or Connectivity defect was present Default: Default: 648 SESFE (Severely Errored Seconds) Count of the seconds during which 600 or more VT Path BIP errors were reported by the far-end VT PTE, a one-bit RDI V defect was present, or (if ERDI V is supported) an ERDI V Server or Connectivity defect was present. The number of reported far-end BIP errors causing a second to be considered an SES VFE Default: Default: 100 UASFE (Unavailable Seconds) Count of the seconds during which the VT Path is considered unavailable at the far end. A VT Path is considered unavailable at the far end at the onset of 10 consecutive seconds that qualify as SES VFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES VFEs Default: Default: 100 Release OPS4.2.2 Force10 Networks Page 2-41

190 Operations and Maintenance Guide, Section 2: Performance Monitoring SONET 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 Parameter Definition 15-min Threshold Daily Threshold STS Used STS Available VT Used VT Available Capacity Available The number of STS paths that are currently used on the VT/TU card. The number of additional STS paths that could be created on the VT/TU card. The number of VT1.5 paths that are currently used on the VT/TU card. The number of additional VT1.5 paths that could be created on the VT/TU card. 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 Default: 0 Default: 0 Page 2-42 Force10 Networks Release OPS4.2.2

191 SECTION 2PERFORMANCE 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 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 the management system, see the TransNav Management System GUI Guide. Release OPS4.2.2 Force10 Networks Page 2-43

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

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

194 Operations and Maintenance Guide, Section 2: Performance Monitoring E1 Port PM Table 2-30 E1 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Path Far End ES (Errored Seconds) SES (Severely Errored Seconds) UAS (Unavailable Seconds) EB (Errored Blocks) FC (Failure Count) BBE (Background Block Error) Count of 1-second intervals containing any of the following: CRC-6 errors (ESF) CS events (ESF, SF) SEF defects (ESF, SF) LOS defects (ESF, SF) FE errors (SF) Count of 1-second intervals containing: 320 or more CRC-6 errors (ESF) 8 or more FE events (SF) one or more SEF or LOS defects (ESF, SF) Count of 1-second intervals for which the DS1 path is unavailable. Count of the number of blocks containing one or more bit errors Default: Default: Default: x 10 6 Default: 1329 Count of far-end path failure (RAI) events Default: 10 An errored block not occurring as part of an SES. 1 8 x 10 6 Default: Default: Default: Default: x 10 8 Default: 13, Default: x 10 8 Default: 13,296 Page 2-46 Force10 Networks Release OPS4.2.2

195 Chapter 3 SDH Performance Parameters E3 Port PM E3 Port PM The Traverse system provides the following near- and far-end E3 port performance monitoring parameters (e3_ptp_pm). Table 2-31 E3 Port PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold Line Near End CV (Code Violations) ES (Errored Seconds) SES (Severely Errored Seconds) LOSS (Loss of Signal Seconds Path - Near End CV (Code Violations) ES (Errored Seconds) SES (Severely Errored Seconds) Count of both BPVs (Bipolar Violations) and EXZs (Excessive Zeros) occurring over the accumulation period. An EXZ shall increment the CV Line count by one regardless of the length of the zero string. BPVs that are part of the zero substitution code are excluded. Count of seconds containing one or more BPVs, one or more EXZs, or one or more LOS defects. BPVs that are part of the zero substitution code are excluded. Count of seconds during which BPVs plus EXZs exceed 44, or one or more LOS defects occur. BPVs that are part of the zero substitution code are excluded. Count of one or more 1-second intervals containing LOS defects. Count of P-bit parity check CVs. The receipt of non-identical P-bits corresponding to the same DS3 M-Frame also constitutes a parity check CV. Count of seconds containing one or more P-bit parity errors, one or more SEF defects, or one or more LOS defects. Count of seconds containing more than 44 P-bit parity violations, one or more SEF defects, or one or more LOS defects. Default: 387 Default: 3865 Default: 25 Default: 250 Default: 4 Default: Default: 10 Default: Default: 382 Default: Default: 25 Default: Default: 4 Default: 40 Release OPS4.2.2 Force10 Networks Page 2-47

196 Operations and Maintenance Guide, Section 2: Performance Monitoring E3 Port PM Table 2-31 E3 Port PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold UAS (Unavailable Seconds) Count of 1-second intervals during which the DS3 path is unavailable Default: 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 Default: Default: 40 Table 2-32 E3 Port PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold Path Far End CV (Coding Violations) ES (Errored Seconds) SES (Severely Errored Seconds) UAS (Unavailable Seconds FC (Failure Counts) 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. Count of seconds containing one or more P-bit parity errors, one or more SEF defects, or one or more LOS defects. Count of seconds containing more than 44 P-bit parity violations, one or more SEF defects, or one or more LOS defects. Count of 1-second intervals during which the DS3 path is unavailable. Count of the number of far-end path failure events. A failure event begins when the RFI-P failure is declared, and ends when the RFI-P failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: Default: 25 Default: Default: 4 Default: Default: 10 Default: 10 Default: 4 Default: 40 Page 2-48 Force10 Networks Release OPS4.2.2

197 Chapter 3 SDH Performance Parameters SDH High and Low Order Path PM SDH High and Low Order Path PM The Traverse system provides the following SDH high order (VC-4 or VC-3) and low order (VC-3) path performance monitoring parameters (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. Table2-33 Number of Errored Blocks that Constitute an SES VC type Bits/Block Blocks/Second Threshold of EBs for SES VC VC-4 18, VC-4-4c 75, VC-4-16c 300, The following table lists the supported performance monitoring parameters for SDH paths. Table 2-34 SDH High Order VC Path and Low Order VC3 PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold 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. 1 7,200,000 Default: 20, ,200,000 Default: 200,000 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). ES (Errored Seconds) Count of 1-second period with at least one errored block or one defect Default: ,400 Default: 250 Release OPS4.2.2 Force10 Networks Page 2-49

198 Operations and Maintenance Guide, Section 2: Performance Monitoring SDH High and Low Order Path PM Table 2-34 SDH High Order VC Path and Low Order VC3 PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 Default: ,400 Default: 40 When a near-end SES occurs as a result of a near-end defect, the far-end performance is not evaluated during that second. However, if a near-end SES occurs as a result of 30% or more EBs, performance monitoring at the far end continues. UAS (Unavailable Seconds) Count of the seconds during which the path was considered unavailable. A path becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-Ps, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps Default: ,400 Default: 40 BBE (Background Block Error) Count of errored blocks not occurring as part of Severely Errored Seconds. 1 7,200,000 Default: 20, ,200,000 Default: 200,000 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 Default: Default: 10 PPJCP Det (Positive Pointer Justifications Detected) Count of the positive pointer justifications detected on the path. 1 1,048,575 Default: ,777,215 Default: 6000 Page 2-50 Force10 Networks Release OPS4.2.2

199 Chapter 3 SDH Performance Parameters SDH High and Low Order Path PM Table 2-34 SDH High Order VC Path and Low Order VC3 PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold NPJCP Det (Negative Pointer Justifications Detected) Count of the negative pointer justifications detected on the path. 1 1,048,575 Default: ,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: ,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: ,777,215 Default: 6000 Table 2-35 SDH High Order VC Path and Low Order VC3 PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold 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 Default: 20, 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 Default: Default: 200 SESFE (Severely Errored Seconds) Count of seconds which contains 30% or more errored blocks or at least one defect at the far end Default: Default: 10 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 Default: Default: 10 Release OPS4.2.2 Force10 Networks Page 2-51

200 Operations and Maintenance Guide, Section 2: Performance Monitoring SDH High and Low Order Path PM Table 2-35 SDH High Order VC Path and Low Order VC3 PM Parameters Far End (continued) Parameter Definition 15-min Threshold Daily Threshold BBEFE (Background Block Error) Count of errored blocks at the far end not occurring as part of Severely Errored Seconds Default: 36, 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 Default: Default: 10 Page 2-52 Force10 Networks Release OPS4.2.2

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

202 Operations and Maintenance Guide, Section 2: Performance Monitoring SDH Port PM Table 2-36 SDH Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 x Defaults: 28, x 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 Default: ,400 Default: 250 SES (Severely Errored Seconds) Count of the seconds during which K or more multiplex section layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: 154 for STM1 615 for STM for STM for STM Default: ,400 Default: 40 UAS (Unavailable Seconds) Count of the seconds during which the multiplex section was considered unavailable. A multiplex section becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-MSs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-MSs Default: Default: 40 Page 2-54 Force10 Networks Release OPS4.2.2

203 Chapter 3 SDH Performance Parameters SDH Port PM Table 2-36 SDH Port PM Near End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 x Defaults: 28, x 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 Default: Default: 40 Table 2-37 SDH Port PM Far End Parameter Definition 15-min Threshold Daily Threshold Multiplex Section Far End EBFE (Errored Blocks ESFE (Errored Seconds Count of BIP errors detected at the multiplex section layer. Up to 8 section BIP errors can be detected per STM frame, with each error incrementing the EB-MS register. Count of the seconds during which (at any point during the second) at least one multiplex section layer BIP error was detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present x Defaults: 28, x Default: 288,000 Recommended defaults for rates other than STM-1: STM-0: 9,600 STM-4: 115,200 STM-16: 460,800 STM-64:1,843, Default: 25 STM-0: 96,000 STM-4: 288,000 STM-16: 1,152,000 STM-64: 18,432, ,400 Default: 250 Release OPS4.2.2 Force10 Networks Page 2-55

204 Operations and Maintenance Guide, Section 2: Performance Monitoring SDH Port PM Table 2-37 SDH Port PM Far End (continued) Parameter Definition 15-min Threshold Daily Threshold SESFE (Severely Errored Seconds) UASFE (Unavailable Seconds) BBEFE (Error Blocks) FCFE (Failure Counts) Count of the seconds during which K or more Line layer BIP errors were detected or an LOS defect (or a lower-layer, traffic-related, near-end defect) was present. K has the following values: 154 for STM1 615 for STM for STM for STM64 Count of the seconds during which the multiplex section was considered unavailable. A multiplex section becomes unavailable at the onset of 10 consecutive seconds that qualify as SES-MSs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-MSs. Count of BIP errors detected at the multiplex section layer (i.e., using the B2 byte in the incoming SDH signal). Up to 8 section BIP errors can be detected per STM-N frame, with each error incrementing the EB-MS register. Count of the number of far end multiplex section failure events. A failure event begins when the LOS failure (or a lower-layer, traffic-related, near-end failure) is declared, and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins Default: Default: x Defaults: 28, ,400 Default: Default: x Default: 288,000 Recommended defaults for rates other than STM-1: STM-0: 9,600 STM-4: 115,200 STM-16: 460,800 STM-64:1,843, Default: 4 STM-0: 96,000 STM-4: 288,000 STM-16: 1,152,000 STM-64: 18,432, Default: 40 Page 2-56 Force10 Networks Release OPS4.2.2

205 Chapter 3 SDH Performance Parameters SDH Port PM Table 2-37 SDH Port PM Far End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 Default: Default: 10 PSDW-MS (Protection Switch Duration Working) Count of the seconds that the working facility was being used to carry an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) Default: ,400 Default: 600 PSCP-MS (Protection Switch Count Protecting) Count of the number of times that an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) switches from the protecting to any working facility. This count also includes the number of times the service (revertive) switches back from the protecting to the working facility Default: Default: 10 PSDP-MS (Protection Switch Duration Protecting) Count of the seconds that the protecting facility was being used to carry an STM multiplex section service (i.e., MS-SP Ring, 1+1 MSP) Default: ,400 Default: 600 Release OPS4.2.2 Force10 Networks Page 2-57

206 Operations and Maintenance Guide, Section 2: Performance Monitoring SDH VC-11 and VC-12 Path PM SDH VC-11 and VC-12 Path PM The Traverse system provides the following SDH VC-11 and VC-12 path performance monitoring parameters (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. Table2-38 Number of Errored Blocks that Constitute an SES VC type Bits/Block Blocks/Second Threshold of EBs for SES VC VC The following table lists the supported performance monitoring parameters for SDH paths. Table 2-39 SDH VC-11 and VC-12 Path PM Parameters Near End Parameter Definition 15-min Threshold Daily Threshold 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 x 10 6 Default: 5, x10 8 Default: 50,000 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). ES (Errored Seconds) Count of 1-second period with at least one errored block or one defect Default: ,535 Default: 250 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-38 Number of Errored Blocks that Constitute an SES, page 2-58 to determine how many errored blocks constitute an SES on the path Default: ,535 Default: 40 When a near-end SES occurs as a result of a near-end defect, the far-end performance is not evaluated during that second. However, if a near-end SES occurs as a result of 30% or more EBs, performance monitoring at the far end continues. Page 2-58 Force10 Networks Release OPS4.2.2

207 Chapter 3 SDH Performance Parameters SDH VC-11 and VC-12 Path PM Table 2-39 SDH VC-11 and VC-12 Path PM Parameters Near End (continued) Parameter Definition 15-min Threshold Daily Threshold 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 Default: ,535 Default: 40 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 Default: 2 1 4,095 Default: 10 BBE (Background Block Error) Count of errored blocks not occurring as part of Severely Errored Seconds x 10 6 Default: 5, x10 8 Default: 50,000 PPJCP Det (Positive Pointer Justifications Detected) Count of the positive pointer justifications detected on the path. 1 32,767 Default: ,097,151 Default: 300 NPJCP Det (Negative Pointer Justifications Detected) Count of the negative pointer justifications detected on the path. 1 32,767 Default: ,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: ,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: ,097,151 Default: 300 Release OPS4.2.2 Force10 Networks Page 2-59

208 Operations and Maintenance Guide, Section 2: Performance Monitoring SDH VC-11 and VC-12 Path PM Table 2-40 SDH VC-11 and VC-12 Path PM Parameters Far End Parameter Definition 15-min Threshold Daily Threshold 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 x 10 6 Default: 5, x10 8 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 Default: ,535 Default: 250 SESFE (Severely Errored Seconds) Count of seconds which contains 30% or more errored blocks or at least one defect at the far end Default: ,535 Default: 40 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 Default: ,535 Default: 40 BBEFE (Background Block Error) Count of errored blocks at the far end not occurring as part of Severely Errored Seconds x 10 6 Default: 5, x10 8 Default: 50,000 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 Default: 2 1 4,095 Default: 10 Page 2-60 Force10 Networks Release OPS4.2.2

209 Chapter 3 SDH Performance Parameters SDH 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 Parameter Definition 15-min Threshold Daily Threshold VC-4 Used VC-4 Available VC-3 Used VC-3 Available TU-3 Used TU-3 Available VC-12 Used The number of VC-4 paths currently used on the VT/TU card. The number of additional VC-4 paths that could be created on the VT/TU card. The number of VC-3 paths currently used on the VT/TU card. The number of additional VC-3 paths that could be created on the VT/TU card. 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. 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. The number of VC-12 paths currently used on the VT/TU card Release OPS4.2.2 Force10 Networks Page 2-61

210 Operations and Maintenance Guide, Section 2: Performance Monitoring SDH Capacity Monitoring Table2-41 SDH Capacity Monitoring (continued) Parameter Definition 15-min Threshold Daily Threshold VC-12 Available VC-11 Used VC-11 Available Capacity 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. The number of VC-11 paths currently used on the VT/TU card. 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. 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 Default: 0 Default: 0 Page 2-62 Force10 Networks Release OPS4.2.2

211 SECTION 2PERFORMANCE MONITORING 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 Ethernet 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 Cards (modules) that do not collect PM information may be reserved for administrative use; contact your system Administrator. 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. For further information on performance monitoring and the management system, see the TransNav Management System GUI Guide. Release OPS4.2.2 Force10 Networks Page 2-63

212 Operations and Maintenance Guide, Section 2: Performance Monitoring Ethernet 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 G3CpDiscards G3Spi4RxOverrun G3SwcBufRAMOverrun G3SwcPckHdrOverrun G3SwcFCBOverrun G3SwcDPResetAbort W3TxFifoIngFCDisc W3TxAborts 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. 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. 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. 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. 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. Frames discarded due to lack of frame control blocks resources. This counter could increment under heavy load. 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. Frames discarded due to FIFO overflow. This counter could increment under heavy load of 64-byte frames. 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. Not applicable Frame Event Frame Frame Frame Frame Frame Frame Page 2-64 Force10 Networks Release OPS4.2.2

213 Chapter 4 Ethernet Performance Parameters Ethernet 10GbE Equipment PM Table 2-42 Ethernet 10GbE Equipment PM Parameters (continued) Parameter (Exclusive Parameter Note) G3PortTxOverrun G3SwcIngressShort G3SwcIngressPViol G3SwcFreeUnderrun G3Spi4RxAbort G3SwcIngressLong Definition 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. 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. Protocol violations which occurred when entering the switch core. This counter could increment as a result of bit errors on the EOS. 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. 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. 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. Counter type Event Frame Event Frame Frame Frame Release OPS4.2.2 Force10 Networks Page 2-65

214 Operations and Maintenance Guide, Section 2: Performance Monitoring EoPDH 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 Parameter (Exclusive Parameter Note) Definition Counter type Non-resetting PM LAN SPI3 RX FIFO OVERRUNS LAN SPI3 TX CRC ERRORS LAN SPI3 TX PROTOCOL ERRORS LAN TX OVERSIZE COUNT GARDENIA FLT DISCARDS GARDENIA BUFFER ABORTS 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. 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. Count of SPI-3 CRC error events in the Gardenia to LAN direction. There could be several events for a single discarded frame, or one event for several discarded frames. Count of protocol error events in the Gardenia to LAN direction. Protocol events include SPI-3 CRC errors, protocol violations or parity errors. There could be several events for a single discarded frame, or one event for several discarded frames. 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. Count of seconds during which Gardenia discarded frames due to overflow of internal multicast queue. This is a normal condition that can arise when there is more multicast traffic than the system can handle. Count of seconds during which Gardenia discarded frames due to inability to access RLDRAM buffer memory. This could occur if ingress traffic contains a high volume of 81-byte frames. Not applicable Event Event Event Frame Errored seconds Errored seconds Page 2-66 Force10 Networks Release OPS4.2.2

215 Chapter 4 Ethernet Performance Parameters EoPDH Equipment PM Table 2-43 EoPDH Equipment PM Parameters (continued) Parameter (Exclusive Parameter Note) GARDENIA SPI3 RX PROTOCOL ERRORS WAN RX FIFO OVERRUNS WAN ENCAPSULATION UNDERRUN WAN TX ABORTS WAN RX UPDATE DISCARDS WAN TX SPI3 ERRORS WAN ENCAP INPUT ABORTS WAN ENCAP PROTOCOL VIOLATIONS WAN ENCAP TOO MUCH DATA Definition Count of seconds during which Gardenia detected a SPI-3 RX interface protocol error in either the LAN to Gardenia or WAN to Gardenia direction. Count of overrun events on FIFO for SPI-3 bus in WAN to Gardenia direction. 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. There could be several events for a single discarded frame, or one event for several discarded frames. Underrun events on SPI-3 bus in Gardenia to WAN direction. There could be several events for a single discarded frame, or one event for several discarded frames. Frames discarded due to unspecified errors in Gardenia to WAN direction. 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. Number of frames received on the external SPI-3 interface with protocol violation or parity error. Single word frames with error are not counted. Number of packets aborted on the input to the Encapsulation block. Number of internal protocol violations on the input to the Encapsulation block. Number of frames received by the Encapsulation block where more data was received than was expected based on the length. Counter type Errored seconds Event Event Frame Frame Event Frame Event Frame Release OPS4.2.2 Force10 Networks Page 2-67

216 Operations and Maintenance Guide, Section 2: Performance Monitoring EoPDH Equipment PM Table2-43 EoPDH Equipment PM Parameters (continued) Parameter (Exclusive Parameter Note) WAN ENCAP TOO FEW DATA WAN ENCAP TOO SHORT Definition Number of frames received by the Encapsulation block where less data was received than was expected based on the length 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. Counter type Frame Frame Page 2-68 Force10 Networks Release OPS4.2.2

217 Chapter 4 Ethernet Performance Parameters Ethernet Equipment PM Ethernet 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 Ethernet Equipment PM Parameters Parameter (Exclusive Parameter Note) Definition Counter type Non-resetting PM LAN SPI3 RX FIFO OVERRUNS LAN SPI3 TX CRC ERRORS LAN SPI3 TX PROTOCOL ERRORS LAN TX OVERSIZE COUNT GARDENIA FLT DISCARDS 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. 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. There could be several events for a single discarded frame, or one event for several discarded frames. Count of SPI-3 CRC error events in the Gardenia to LAN direction. There could be several events for a single discarded frame, or one event for several discarded frames. Count of protocol error events in the Gardenia to LAN direction. Protocol events include SPI-3 CRC errors, protocol violations or parity errors. There could be several events for a single discarded frame, or one event for several discarded frames. 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. 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. Not applicable Event Event Event Frame Errored seconds Release OPS4.2.2 Force10 Networks Page 2-69

218 Operations and Maintenance Guide, Section 2: Performance Monitoring Ethernet Equipment PM Table2-44 Ethernet Equipment PM Parameters (continued) Parameter (Exclusive Parameter Note) GARDENIA BUFFER ABORTS GARDENIA SPI3 RX PROTOCOL ERRORS WAN RX FIFO OVERRUNS WAN ENCAPSULATION UNDERRUN WAN TX ABORTS Definition Count of seconds during which Gardenia discarded frames due to inability to access RLDRAM buffer memory. This could occur if ingress traffic contains a high volume of 81-byte frames. Count of seconds during which Gardenia detected a SPI-3 RX interface protocol error in either the LAN to Gardenia or WAN to Gardenia direction. Count of overrun events on FIFO for SPI-3 bus in WAN to Gardenia direction. NGE increments this counter when it discards an ingress frame from an EOS (WAN-side) port due to inability of the internal switch to handle aggregate traffic arriving from Ethernet and EOS ports. The most likely cause of the congestion is an excess of aggregate traffic arriving at the NGE card from the Ethernet ports. There could be several events for a single discarded frame, or one event for several discarded frames. Underrun events on SPI-3 bus in Gardenia to WAN direction. There could be several events for a single discarded frame, or one event for several discarded frames. Frames discarded due to unspecified errors in Gardenia to WAN direction. Counter type Errored seconds Errored seconds Event Event Frame Page 2-70 Force10 Networks Release OPS4.2.2

219 Chapter 4 Ethernet Performance Parameters Ethernet 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 Parameter (Exclusive Parameter Note) Non-resetting PM TX UNICAST 1 TX MULTICAST 1 TX BROADCAST TX FRAMES 1 RX UNICAST 1 RX MULTICAST 1 RX BROADCAST RX FRAMES 1 Definition 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. The number of unicast frames transmitted with no errors. The number of multicast frames that are not broadcast, transmitted with no errors. The number of broadcast frames transmitted with no errors. The number of frames transmitted (unicast, multicast, and broadcast) with no errors. The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors. The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors. The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors. The number of frames received (unicast, multicast, and broadcast) with no errors. Release OPS4.2.2 Force10 Networks Page 2-71

220 Operations and Maintenance Guide, Section 2: Performance Monitoring Ethernet Port PM Table 2-45 Ethernet Port PM Parameters (continued) RX > MAX FRAME SIZE RX < 64 Parameter (Exclusive Parameter Note) RX PKT 64 (Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10) RX PKT (Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10) RX PKT (Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10) RX PKT (Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10) RX PKT (Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10) RX PKT (Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10) RX PKT > 1518 (Not applicable to Traverse NGE, EoPDH, 10GbE, or GBE-10) RX DISCARDS 2,3,4 TX DISCARDS (Traverse NGE, 10GbE, GbE-10, and EoPDH only) RX DELAY DISCARDS (TE-100 Ethernet only) RX MTU DISCARDS (Not applicable to TE-100 Ethernet) RX FCS ERR 5 Definition The number of received frames that exceed the maximum valid packet length for the port. The number of frames received, less than 64 bytes in length, received with no errors. The number of received 64-byte frames, including bad frames. The number of received frames, 65 to 127 bytes in length, including bad frames. The number of received frames, 128 to 255 bytes in length, including bad frames. The number of received frames, 256 to 511 bytes in length, including bad frames. The number of received frames, 512 to 1023 bytes in length, including bad frames. The number of received frames, 1024 to 1518 bytes in length, including bad frames. The number of received frames, greater than or equal to 1519 bytes in length, including bad frames. The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol. The number of outbound frames discarded by this port due to aborted frames and underruns. Number of frames discarded by this interface due to excessive transit delay through the bridge. Number of frames discarded by this interface due to an excessive size. Number of frames received which are an integral number of octets and do not pass the FCS check. Page 2-72 Force10 Networks Release OPS4.2.2

221 Chapter 4 Ethernet Performance Parameters Ethernet Port PM Table 2-45 Ethernet Port PM Parameters (continued) RX MAC CTL DISCARDS (Traverse 10GbE or GbE-10 only) RX PAUSE TX PAUSE TX BYTES 6 RX BYTES 2 Parameter (Exclusive Parameter Note) TX SINGLE COLL (10/100BaseTX only) TX MULTIPLE COLL (10/100BaseTX only) TX DEFERRED FRAMES (10/100BaseTX only) TX LATE COLL (10/100BaseTX only) TX EXCESSIVE COLL (10/100BaseTX only) Definition The number of received MAC control frames that were discarded due to invalid addresses. The number of received pause control frames. The number of transmitted pause control frames. The number of bytes transmitted in good frames. The number of bytes received in good frames. The number of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. Also counted as a successful transmission. Half-duplex operation only. The number of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. Also counted as a successful transmission. Half-duplex operation only. The number of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. Does not include frames involved in collisions. Half-duplex operation only. The number of times that a collision is detected on a particular interface later than one slottime into the transmission of a packet. Half-duplex operation only. The number of frames for which transmission on a particular interface fails due to excessive collisions. Half-duplex operation only. 1 Traverse NGE, 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. Release OPS4.2.2 Force10 Networks Page 2-73

222 Operations and Maintenance Guide, Section 2: Performance Monitoring Ethernet 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 Parameter (Exclusive Parameter Note) Non-resetting PM TX BYTES (NGE, NGE Plus, and EoPDH only) TX PACKETS TX RED DISCARDS RX BYTES 2 RX PACKETS Definition 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. The number of bytes contained in packets queued for transmitted to this port for this service, including internal overhead per packet. The number of packets queued for transmission to this port for this service. The number of packets that were not queued for transmission to this port for this service because they were discarded due to Random Early Discard (RED). 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. The number of bytes received on this port for this service, including internal overhead per packet. The number of packets received on this port for this service. Page 2-74 Force10 Networks Release OPS4.2.2

223 Chapter 4 Ethernet Performance Parameters Ethernet Service Port PM Table 2-46 Ethernet Service Port PM Parameters (continued) Parameter (Exclusive Parameter Note) RX LOCAL DISCARDS (NGE, NGE Plus, and EoPDH only) RX HARDWARE PACKET DISCARDS Definition 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. 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. Release OPS4.2.2 Force10 Networks Page 2-75

224 Operations and Maintenance Guide, Section 2: Performance Monitoring EOS 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 Parameter (Exclusive Parameter Note) Non-resetting PM TX UNICAST (TE-100 Ethernet only) TX MULTICAST (TE-100 Ethernet only) TX BROADCAST (TE-100 Ethernet only) TX FRAMES 1 TX BYTES 2,3 TX DISCARDS (Traverse NGE and EoPDH only) RX UNICAST (TE-100 Ethernet only) RX MULTICAST (TE-100 Ethernet only) Definition 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. The number of unicast frames transmitted with no errors. The number of multicast frames that are not broadcast, transmitted with no errors. The number of broadcast frames transmitted with no errors. The number of frames transmitted (unicast, multicast, and broadcast) with no errors. The number of bytes transmitted in good frames. The number of outbound frames received by this port which were discarded. The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors. The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors. Page 2-76 Force10 Networks Release OPS4.2.2

225 Chapter 4 Ethernet Performance Parameters EOS Port PM Table 2-47 EOS Port PM Parameters (continued) RX BROADCAST (TE-100 Ethernet only) RX FRAMES 1 RX BYTES 23 Parameter (Exclusive Parameter Note) RX DISCARDS (Traverse NGE and EoPDH only) RX FCS ERR (Traverse 10GbE or GbE-10 only) GFP FCS DISCARDS 4 (Traverse NGE and EoPDH only) GFP CHEC DISCARDS GFP PHEC DISCARDS (Traverse NGE and EoPDH only) GFP FCS OR PHEC DISCARDS (TE-100 Ethernet only) RX MTU DISCARDS (TE-100 Ethernet only) GFP HEC CORRECTIONS Definition The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors. The number of frames received (unicast, multicast, and broadcast) with no errors. The number of bytes received in good frames. The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol. The number of received frames that were discarded due to incorrect Ethernet CRC. The number of GFP frames discarded due to frame checksum (FCS) errors. The number of GFP frames discarded due to uncorrectable core header (chec) checksum errors. The number of GFP frames discarded due to due to uncorrectable payload header (extension or type header) checksum (ehec, thec) errors. The number of GFP frames discarded due to frame checksum (FCS) errors, plus GFP frames discarded due to uncorrectable payload header (extension or type header) checksum (ehec, thec) errors. The number of frames discarded by this interface due to an excessive size. GFP frames received with single-bit HEC errors (chec, ehec or thec) that have been corrected. 1 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. Release OPS4.2.2 Force10 Networks Page 2-77

226 Operations and Maintenance Guide, Section 2: Performance Monitoring EOP 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 Parameter (Exclusive Parameter Note) Definition Non-resetting PM TX UNICAST TX MULTICAST TX BROADCAST TX FRAMES TX BYTES TX DISCARDS 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. The number of unicast frames transmitted with no errors. The number of multicast frames that are not broadcast, transmitted with no errors. The number of broadcast frames transmitted with no errors. The number of frames transmitted (unicast, multicast, and broadcast) with no errors. The number of bytes transmitted in good frames. The number of outbound frames received by this port which were discarded. RX UNICAST The number of unicast frames received, with length between 64 bytes and the maximum size, with no errors. RX MULTICAST RX BROADCAST RX FRAMES RX BYTES The number of multicast frames received, with length between 64 bytes and the maximum size, with no errors. The number of broadcast frames received, with length between 64 bytes and the maximum size, with no errors. The number of frames received (unicast, multicast, and broadcast) with no errors. The number of bytes received in good frames. Page 2-78 Force10 Networks Release OPS4.2.2

227 Chapter 4 Ethernet Performance Parameters EOP Port PM Parameters Table 2-48 EOP Port PM Parameters (continued) Parameter (Exclusive Parameter Note) RX DISCARDS RX FCS ERRORS GFP FCS DISCARDS GFP CHEC DISCARDS GFP PHEC DISCARDS GFP FCS OR PHEC DISCARDS RX MTU DISCARDS GFP HEC CORRECTIONS Definition The number of inbound frames discarded by this port due to errors, and thus, unable to forward to a higher-layer protocol. The number of received frames that were discarded due to incorrect Ethernet CRC. The number of GFP frames discarded due to frame checksum (FCS) errors. The number of GFP frames discarded due to uncorrectable core header (chec) checksum errors. The number of GFP frames discarded due to due to uncorrectable payload header (extension or type header) checksum (ehec, thec) errors. The number of GFP frames discarded due to frame checksum (FCS) errors, plus GFP frames discarded due to uncorrectable payload header (extension or type header) checksum (ehec, thec) errors. The number of frames discarded by this interface due to an excessive size. GFP frames received with single-bit HEC errors (chec, ehec or thec) that have been corrected. 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 Release OPS4.2.2 Force10 Networks Page 2-79

228 Operations and Maintenance Guide, Section 2: Performance Monitoring Small 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, page Table 2-49 SFP (and XFP) Optical Port PM Parameters Parameter Measured Temperature Measured Supply Voltage Measured TX Bias Current Measured TX Output Power Measured TX Input Power Definition A measure of the internal transceiver temperature yielding a value within the total range of -128 to +128 celsius. A measure of the internal transceiver supply voltage yielding a value within the total range of 0 to volts. A measure of the TX bias current yielding a value within the total range of 0 to 131 ma. A measure of the TX output power based on the measurement of laser monitor photodiode current and yielding a value within the total range of 0 to mw. A measure of the TX input power yielding a value within the total range of 0 to mw (~ -40 to +8.2 dbm). Absolute accuracy is dependent upon the exact optical wavelength. Page 2-80 Force10 Networks Release OPS4.2.2

229 SECTION 3 EQUIPMENT LED STATUS SECTION 3 SECTION 3 Contents Chapter 1 LEDs and Module Status PDAP LEDs Front Inlet Fan Tray Module LEDs Power and Standby LED Indicators All Modules General Control Module (GCM) LED Indicators Electrical Module Port LED Indicators Optical Module Port LED Indicators Ethernet Module Port LED Indicators Ethernet Termination Connector LED Indicators Visual Status During and After Start-up Flashing red Solid green Release OPS4.2.2 Force10 Networks Page i

230 Operations and Maintenance Guide, Section 3 Equipment LED Status Page ii Force10 Networks Release OPS4.2.2

231 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-4 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 Release OPS4.2.2 Force10 Networks Page 3-1

232 Operations and Maintenance Guide, Section 3: Equipment LED Status PDAP 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 Block Power At least one fuse failure in GMT Fuse Block A or B. All fuses are good in GMT Fuse Block A or B. N/A No power. Input Power N/A Power from Battery A or B input. N/A No power. Major Summary Alarm At least one major alarm in the rack. N/A N/A No major alarms for the entire rack. Page 3-2 Force10 Networks Release OPS4.2.2

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

234 Operations and Maintenance Guide, Section 3: Equipment LED Status Front 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. Traverse 1600 FIFT Fan Failure (red) Power (green) Traverse 600 FIFT Fan Failure (red) Power (green) OPS Figure 3-3 Front Inlet Fan Card with LEDs 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. Page 3-4 Force10 Networks Release OPS4.2.2

235 Chapter 1 LEDs and Module Status Front Inlet Fan Tray Module LEDs Figure 3-4 The locations of common and specific card LEDs is shown in the following graphic. PWR (Power) ACTV/ STNBY (Active/Standby) DS1, DS3/E3, E1, OC-N/STM-N and ETH Port Indicators Alarms: CRITICAL/MAJOR MINOR ACO ON ACO Optical Port Timing: LOCKED/ UNLOCKED FREE RUN/ HOLDOVER ETHERNET LINK OSS and Craft 10/100BaseT Ethernet Interface (RJ-45) RS-232 Interface (DB-9) DS1 DS3/E3 E1 OC-N/ STM-N VT Switch Ethernet EGCM OPS Figure 3-5 Physical Card LEDs Release OPS4.2.2 Force10 Networks Page 3-5

236 Operations and Maintenance Guide, Section 3: Equipment LED Status Power and Standby LED Indicators All Modules Power and Standby LED Indicators All Modules The LEDs in the following tables apply to all cards. Table 3-3 Power and Active/Standby All Cards LED RED Amber GREEN OFF Flashing Solid Flashing Solid Flashing Solid Power Initialization and diagnosis is underway but not complete. Hardware failure detected; replace the 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. Page 3-6 Force10 Networks Release OPS4.2.2

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

238 Operations and Maintenance Guide, Section 3: Equipment LED Status Electrical Module Port LED Indicators : Table 3-6 Ethernet Link (OSS and Craft 10/100BaseT) LED RED GREEN OFF Flashing Solid Flashing Solid Ethernet Port Running diagnostics or in loopback mode. Port is unlocked, but there is no link integrity/ signal. Transmitting or receiving frames. Operational, the link is active. Port is locked. Electrical Module Port LED Indicators The LEDs in the following table apply to electrical (DS1, DS3, E1, E3, and VT/TU Switch) cards only. 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. Page 3-8 Force10 Networks Release OPS4.2.2

239 Chapter 1 LEDs and Module Status Ethernet Module Port LED Indicators Optical Module Port LED Indicators The LEDs in the following table apply to optical cards (OC-N/STM-N) and to the optical ports (OC-12/STM-4 or OC-48/STM-16) on the GCM with integrated optics cards. Table 3-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 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-9 GbE and Fast Ethernet Port LED RED GREEN OFF Flashing Solid Flashing Solid Ethernet Port Running diagnostics or in loopback mode Unlocked no link integrity/ signal detected Unlocked and transmitting or receiving frames Unlocked and operational. The Ethernet link is active. Card initialization is not complete or the port is locked Release OPS4.2.2 Force10 Networks Page 3-9

240 Operations and Maintenance Guide, Section 3: Equipment LED Status Ethernet Termination Connector LED Indicators Ethernet Termination Connector LED Indicators The LEDs in the following table apply to the optical 10GbE, GbE-10, GbE and FE (100Base FX and 10/100BaseTX) combination cards. Table 3-10 GbE and Fast Ethernet Port LED RED GREEN OFF Flashing Solid Flashing Solid Ethernet Port Running diagnostics or in loopback mode Unlocked no link integrity/ signal detected Unlocked and transmitting or receiving frames Unlocked and operational. The Ethernet link is active. Card initialization is not complete or the port is locked Page 3-10 Force10 Networks Release OPS4.2.2

241 Chapter 1 LEDs and Module Status Visual 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. 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 LED RED Amber GREEN OFF Flashing Solid Flashing Solid Flashing Solid 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; synchronization 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; synchronization with the active card is complete. Active and operational Initializing; POST is started. 1 Please refer to Appendix A Card Placement Planning and Guidelines, page 12-1 for valid card placement guidelines. 1 The POST takes approximately one minute to run and it invokes the LED activity for initialization. Release OPS4.2.2 Force10 Networks Page 3-11

242 Operations and Maintenance Guide, Section 3: Equipment LED Status Visual Status During and After Start-up Page 3-12 Force10 Networks Release OPS4.2.2

243 SECTION 4 DIAGNOSTICS SECTION 4 Contents Chapter 1 Diagnostics Overview Symptoms and Recommended Actions Chapter 2 Traverse Transmit and Receive Signal Levels Traverse Optical Interface Specifications Fast Ethernet GbE GbE OC-3/STM OC-12/STM OC-48/STM OC-192/STM Chapter 3 TraverseEdge 100 Transmit and Receive Signal Levels TE-100 Optical Interface Specifications Chapter 4 Loopback Tests DS1 and DS3 Loopback Tests DS1 and DS3 Facility Payload Loopback DS1 and DS3 Terminal Loopback E1 and E3 Loopback Tests E1 and E3 Facility Payload Loopback E1 and E3 Terminal Loopback Ethernet Loopback Tests NGE and EoPDH Ethernet Facility Loopback Ethernet Terminal Loopback Facility Loopback on EOP Ports SONET/SDH Loopback Tests SONET/SDH Facility Loopback SONET/SDH Terminal Loopback Performing Loopback Tests Equipment States Chapter 5 Other Diagnostics Power On Self Test Alarm Cut-Off Release OPS4.2.2 Force10 Networks Page i

244 Operations and Maintenance Guide, Section 4 Diagnostics LED Lamp Test Page ii Force10 Networks Release OPS4.2.2

245 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 2-9 Chapter 5 Other Diagnostics, page 4-19 Release OPS4.2.2 Force10 Networks Page 4-1

246 Page 4-2 Force10 Networks Release OPS4.2.2 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 Environmental Alarms OC-192 Module Symptom Description Scope Probable Cause Recommended Action Environmental Alarm input or output is incorrect. Upon installation into the shelf slot, the (R1.3 and above) enhanced OC-192 module does not initialize or come operational. The module LEDs continue flashing. Node Incorrect alarm cable connections Environmental Alarm Module (EAM) failure Node OC-192 module was installed in a node with pre-release 1.3 software. Incorrect alarm cable connections. See the Traverse Installation and Commissioning Guide, Section 1 Fault Management, Chapter 2 Alarms, Events, and Recommended Actions, page 1-21 Replace EAM. See Section 6 Routine Maintenance, Chapter 1 Routine Maintenance, Environmental Alarm Module Replacement (Traverse only), page 6-17 Check the current software version. Perform software upgrade as necessary for software compatibility. See Section 7 Software Upgrades, Chapter 1 Release TR3.2.2 Traverse Software Upgrade, page 7-1 Operations and Maintenance Guide, Section 4: Diagnostics Symptoms and Recommended Actions

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

248 Page 4-4 Force10 Networks Release OPS4.2.2 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 Optical Interface Specification Summary Table Optical Interface Card Optic Type Typical Nominal TX Wavelength TX Wavelength Range RX Wavelength Range Transmitter Output Power 1 Receiver Signal 1,2 Guaranteed Link Budget 1 Distance Objective 3, 4 (nm) (nm) (nm) (dbm) (dbm) (db) (mi) (km) Fast Ethernet 100BaseFX (GbE/Fast Ethernet combo) to to to to GbE GbE SX to to to to GbE LX to to to to GbE ZX to to to to GbE CWDM 1470 to 1610 (8 channels at 20 nm intervals) 1260 to to 4-18 to GbE 10GbE LR to to to to GbE ER to to to 2-13 to GbE ZR to to to 4-23 to OC-3/STM-1 OC-3 IR1/STM-1 SH to to to to OC-3 LR2/STM-1 LH to to to 0-32 to OC-12/STM-4 OC-12 IR1/STM-4 SH to to to to OC-12 LR2/STM-4 LH to to to 2-26 to Operations and Maintenance Guide, Section 4: Diagnostics Traverse Optical Interface Specifications

249 Release OPS4.2.2 Force10 Networks Page 4-5 Table 4-2 Optical Interface Specification Summary Table (continued) Optical Interface Card Optic Type Typical Nominal TX Wavelength OC-48/STM-16 OC-48 SR1/STM-16 SH to to to to OC-48 IR1/STM-16 SH to to to 0-17 to OC-48 LR1/STM-16 LH to to to 3-26 to OC-48 LR2/STM-16 LH to to to 3-25 to OC-48 LR2/STM-16 LH CWDM 1470 to 1610 (8 channels at 20 nm intervals) 1260 to to 5-25 to OC-48 ELR/STM-16 LH ITU DWDM to (42 channels) 1260 to to 4-26 to OC-48 VR2/STM-16 VLH to to to to OC-192/STM-64 6 OC-192 SR1/STM-64 SH to to to to OC-192 IR2/STM-64 SH to to to 2-15 to OC-192 LR2/STM-64 LH to to to 7-20 to OC-192 LR/STM-64 LH ITU DWDM to (42 channels) 1290 to to 7-20 to OC-192 ELR/STM-64 LH ITU DWDM to (42 channels) 1290 to to 7-23 to These values account for the connector loss from connection to the optical interface and the worst case optical path penalty. 2 Pseudo Random Bit Sequence, Bit Error Rate is PRBS, BER=10-12 TX Wavelength Range RX Wavelength Range 3 Per IEEE 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 db/km for 1550 nm (including splices, connectors, etc.). 4 Turin recommends customers to take actual fiber readings as these values are based on standards qualification. Transmitter Output Power 1 Receiver Signal 1,2 Guaranteed Link Budget 1 Distance Objective 3, 4 (nm) (nm) (nm) (dbm) (dbm) (db) (mi) (km) 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. Chapter 2 Traverse Transmit and Receive Signal Levels Traverse Optical Interface Specifications

250 Operations and Maintenance Guide, Section 4: Diagnostics Traverse Optical Interface Specifications 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. 6 Page 4-6 Force10 Networks Release OPS4.2.2

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

252 Page 4-8 Force10 Networks Release OPS4.2.2 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 4-3 SONET, STM, and GbE Optics SONET Application STM WARNING! The optical receiver of the OC-N long-reach optics can be damaged permanently if overloaded. Do not connect the optical transmitter directly to the optical receiver without proper attenuation. A minimum of 10 db attenuation is required for long reach optics. Important: Only use SFPs approved by Force10 or equipment damage may occur, thus voiding any TE-100 warranty. Approx Distance (km) Tx Power Range (dbm) Rx Power Range (dbm) Dispersion Penalty (db) Attenuation Range Extinction Ratio (db) Tx Wavelength Range (nm) Rx Wavelength Range (nm) Dispersion Tolerance (ps/nm) 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. Temperature Range (degc) OC-3 IR-1 STM-1 S to to to to to to 85 OC-3 LR-2 STM-1 L to 0-33 to to to to to 70 OC-12 IR-1 STM-4 S to to to to to to 85 OC-12 LR-2 STM-4 L to 2-27 to to to to to 70 OC-48 SR-1 STM-16 I to to to to to to 70 OC-48 IR-1 STM-16 S to 0-18 to to to to to 70 OC-48 LR-1 STM-16 L to 3-27 to to to to to 70 OC-48 LR-2 STM-16 L to 3-26 to to to to to 70 OC-48 LR-2 STM-16 L to 5-26 to to to to to 70 OC-48 ELR STM to 4-27 to to to to to Base SX 1000Base SX to to to to to to Base LX 1000Base LX 10-9 to to to to to to Base ZX 1000Base ZX 80 0 to 4-22 to to to to to 70 Operations and Maintenance Guide, Section 4: Diagnostics TE-100 Optical Interface Specifications

253 SECTION 2DIAGNOSTICS Chapter 4 Loopback Tests Introduction The TransNav Management System provides diagnostic loopback testing for troubleshooting ports and spans. The system supports the following loopback tests: Facility To troubleshoot the line interface unit of a card, the backplane, or the cabling Terminal To troubleshoot a circuit path and loop back to the card WARNING! Loopback tests interrupt traffic flow; do not perform them on nodes providing service. Important: Facility and terminal loopbacks cannot be performed on 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 2-10 E1 and E3 Loopback Tests, page 2-11 Ethernet Loopback Tests, page 2-12 SONET/SDH Loopback Tests, page 2-14 See Performing Loopback Tests, page 2-15 for a step-by-step procedure on how to perform loopback tests. See Equipment States, page 2-17 for a discussion of the Traverse operational and administrative states. Release OPS4.2.2 Force10 Networks Page 2-9

254 Operations and Maintenance Guide, Section 2: Diagnostics DS1 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. Service between ports DS-x card Trunk card Test Set LIU AIS LIU DS-x facility under loopback test OPS 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. Service set up between ports DS-x card Trunk card LIU LIU Test Set DS-x facility under loopback test OPS Figure 4-2 DS-x Terminal Loopback Page 2-10 Force10 Networks Release OPS4.2.2

255 Chapter 4 Loopback Tests E1 and E3 Loopback Tests E1 and E3 Loopback Tests E1 and E3 Facility Payload Loopback The node supports a facility payload loopback for each incoming received E-x signal. The facility must first be taken out of service prior to initiating the loopback test. The facility payload loopback connects the incoming received E-x signal immediately to the associated return transmitter, as shown in Figure 4-1. During this loopback, AIS is inserted and sent to the far end. Service between ports E-x module Trunk module Test Set LIU AIS LIU E-x facility under loopback test OPS 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. Service set up between ports E-x module Trunk module LIU LIU Test Set E-x facility under loopback test OPS Figure 4-4 E-x Terminal Loopback Release OPS4.2.2 Force10 Networks Page 2-11

256 Operations and Maintenance Guide, Section 2: Diagnostics Ethernet 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. 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. 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. Ethernet card Traverse Node Ethernet frames Ethernet facility in Facility Loopback OPS 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). Page 2-12 Force10 Networks Release OPS4.2.2

257 Chapter 4 Loopback Tests Facility 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. EOS port Ethernet facility in Terminal Loopback L L Ethernet card Activated Line service(s) O (i) S Node Trunk Card GFP-encapsulated Ethernet over SONET / SDH OPS 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. EoPDH card OC-N/STM-N transport card Ethernet Switch GFP, VCAT PDH member LIU Test Set PDH payload generated and consumed here OPS 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. Release OPS4.2.2 Force10 Networks Page 2-13

258 Operations and Maintenance Guide, Section 2: Diagnostics SONET/SDH Loopback Tests SONET/SDH Loopback Tests SONET/SDH Facility Loopback The node supports a facility payload loopback for each OC-N/STM-N facility (including the OC-12/STM-4 and OC-48/STM-16 facility on the Traverse GCM). The facility must first be taken out of service 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. Service between ports STS-N OC-N module OC-N module STS-N Test Set LIU AIS LIU SONET facility under loopback test OPS 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. Service set up between ports OC-N/STM-N module OC-N/STM-N module LIU LIU Test Set SONET/SDH facility under loopback test OPS Figure 4-9 SONET/SDH Terminal Loopback Page 2-14 Force10 Networks Release OPS4.2.2

259 Chapter 4 Loopback Tests Performing Loopback Tests Performing Loopback Tests Before performing loopback testing, the port s administrative state must first be changed to Unlocked. Important: Loopback tests interrupt data flow; do not perform them on a port providing service. Use the vendor s procedures for setting up your test equipment, then follow the procedure below to perform loopback tests on a port. The loopback state or port lock/unlock state is be restored after a node database restore operation is performed. Instead, the system uses the current state of the port to override what was stored in the node database. Table 4-4 Performing Loopback Tests Step Procedure 1 In the GUI, display the Shelf View of the node on which you will perform loopback tests. If you are currently in Map View, double-click the node to switch to the Shelf View. 2 Select a port on the appropriate card. 3 Click the Config tab. 4 To unlock a port that is currently locked, click the Locked icon in the lower left corner to display the Unlocked icon, then click Apply. 5 Is this an OC-N/STM-N port? Yes. Disable the Config tab Control Data parameter. No. Go to the next step. 6 Click Apply. 7 Click the Diagnostic tab. 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 Release OPS4.2.2 Force10 Networks Page 2-15

260 Operations and Maintenance Guide, Section 2: Diagnostics Performing Loopback Tests Table 4-4 Performing Loopback Tests (continued) Step Procedure 9 For DS3/EC-1 ports only, select the Test Signal Type: (Planned for future release.) Clear (default) PRBS (Pseudo random bit sequence): PRBS Fixed-24Bit: Repeating 24-bit pattern ( ) 10 Click Apply to run the loopback test. If the loopback test fails, there is a problem with the signal path. 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. Page 2-16 Force10 Networks Release OPS4.2.2

261 Chapter 4 Loopback Tests Equipment States Equipment States Icons in the bottom left-hand corner of the Config tab indicate the state of the card or port. Equipped state Operational state Administrative state 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. Release OPS4.2.2 Force10 Networks Page 2-17

262 Operations and Maintenance Guide, Section 2: Diagnostics Equipment States Page 2-18 Force10 Networks Release OPS4.2.2

263 SECTION 4DIAGNOSTICS Chapter 5 Other Diagnostics Introduction Power On Self Test Alarm Cut-Off LED Lamp Test This chapter provides other general diagnostics: Power On Self Test, page 4-19 Alarm Cut-Off, page 4-19 LED Lamp Test, page 4-19 The Traverse and TE-100 system runs the Power On Self Test (POST) diagnostic test sequence on the Traverse general control module (GCM) and TE-100 System module at system startup, respectively. The POST determines whether all system components are working properly and takes approximately one minute to run, during which time the power LED displays solid RED. The POST runs on both the working and protection modules Any and all POST failures cause a fail-over The POST invokes LED activity for test progress, and pass and fail notification For a complete description of the LEDs in the system, see Chapter 1 LEDs and Module Status, page 3-1. The Alarm Cut-Off (ACO) button on the front of the Traverse GCM and TE-100 System module causes the audible sound for major and critical alarms to silence or re-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. 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. Release OPS4.2.2 Force10 Networks Page 4-19

264 Operations and Maintenance Guide, Section 4: Diagnostics LED Lamp Test Page 4-20 Force10 Networks Release OPS4.2.2

265 SECTION 5 TEST ACCESS SECTION 5 Contents Chapter 1 Traverse Test Access Local Test Access Remote Test Access Mode Configurations Access Identifier (AID) Monitor Configurations Split Configurations Feature Set Options Configuration Management Test Access Mode Examples Monitor Test Access Example (MONE) Per Side Split Test Access Example (SPLTE) Series Split Test Access Example (SPLTA) Chapter 2 Traverse Test Access Guidelines for the Spirent BRTU Interface Traverse Platform and Spirent BRTU Interoperability Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface Release OPS4.2.2 Force10 Networks Page i

266 Operations and Maintenance Guide, Section 5 Test Access Page ii Force10 Networks Release OPS4.2.2

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

268 Operations and Maintenance Guide, Section 5: Test Access Local 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 establishe 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. TransNav Management System (GUI, CLI, or TL1) Test System Controller (TSC) DCS3/1 Termination Point (TP) of the Circuit Under Test Node-level Control Link (CLI or TL1) Test Access Point (TAP) (e.g., DS1 port) Patch Panel Remote Test Unit (RTU) OPS Figure 5-1 Local Traverse DCS3/1 Test Access Page 5-2 Force10 Networks Release OPS4.2.2

269 Chapter 1 Traverse Test Access Remote 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. DCS3/1 Logical TAPs (e.g., VT1.5 on OC-N port) STS-1 or VT Path SONET Network Remote Access Multiplexer Physical TAPs (e.g., DS1) Remote Test Unit (RTU) OPS Figure 5-2 Remote Traverse DCS3/1 Test Access Release OPS4.2.2 Force10 Networks Page 5-3

270 Operations and Maintenance Guide, Section 5: Test Access Mode Configurations Mode Configurations There are multiple monitor and split test access mode configurations available for use with bidirectional, unidirectional, and unmapped DS3/STS-1 and DS1/VT1.5 services. The Traverse system supports the following test access mode configurations: Monitor Configurations, page 5-6 Split Configurations, page 5-7 Each test access mode supports a set of service types. The following table 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 Mode Service Bidirectional Unidirectional Unmapped MONE A A A MONEF A NA NA MONF A NA NA SPLTA A A NA SPLTB A NA NA SPLTE A A A SPLTEF A NA NA SPLTF A NA NA Page 5-4 Force10 Networks Release OPS4.2.2

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

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

273 Chapter 1 Traverse Test Access Split Configurations Split Configurations Each split configuration is intrusive. These configurations disable the original service so there is disruption to customer traffic. There are two kinds of split configurations: series and per side. Test access provides five split mode configurations: SPLTE - Per side split on the ingress termination point to test the ingress service SPLTF - Per side split on the egress termination point to test the egress service 3 SPLTEF - Per side split on both the ingress and egress termination points to 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 point 4 SPLTA Test Access SPLTB Test Access A A B B FAD FAD SPLTE Test Access SPLTF Test Access E F E F FAD SPLTEF Test Access FAD E F FAD FAD OPS Figure 5-5 Split Configurations 3 If SPLTF is configured with a DFAD instead of the common FAD, it uses the second FAD. 4 If SPLTB is configured with a DFAD instead of the standard FAD, it uses the second FAD. Release OPS4.2.2 Force10 Networks Page 5-7

274 Operations and Maintenance Guide, Section 5: Test Access Feature Set Options Feature Set Options The Traverse system provides the following full feature set module and user access interface options to support DCS3/1 test access applications. Choose those 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. Page 5-8 Force10 Networks Release OPS4.2.2

275 Chapter 1 Traverse Test Access Monitor Test Access Example (MONE) Configuration Management Test Access Mode Examples Monitor Test Access Example (MONE) 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. 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 The MONE (Monitor-E) monitor test access configuration is non-intrusive. There is no disruption to customer traffic. The figure below shows amone 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. Service to be Tested S1 DCS D1 TAP (e.g., DS1) Monitor Test Access (Non-Intrusive) S1 DCS D1 TAP1 OPS Figure 5-6 Monitor Test Access Configuration MONE Release OPS4.2.2 Force10 Networks Page 5-9

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

277 Chapter 1 Traverse Test Access Monitor Test Access Example (MONE) Table 5-2 Monitor Test Access Configuration MONE (continued) Step Procedure 3 From the Test Access tab, TAC sub-tab, create a Monitor-E (MONE) TAC from the source (S1) to a logical TAP. Note: Use the Switch Mode button to switch from one mode configuration to another. For valid mode changes, see Table 5-1 Test Access Mode vs. Service Compatibility Matrix. MONE Mode TAP1 Service ID Connected State Switch Mode command Figure 5-8 MONE TAC Example Release OPS4.2.2 Force10 Networks Page 5-11

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

279 Chapter 1 Traverse Test Access Per Side Split Test Access Example (SPLTE) Per Side Split Test Access Example (SPLTE) The SPLTE per side split test access configuration is intrusive. 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. Service to be Tested S1 DCS D1 TAP (e.g., DS1) Per Side Split Test Access (Intrusive) S1 DCS D1 TAP1 OPS Figure 5-10 Per Side Split Test Access Configuration SPLTE Release OPS4.2.2 Force10 Networks Page 5-13

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

281 Chapter 1 Traverse Test Access Per Side Split Test Access Example (SPLTE) Table 5-3 Per Side Split Test Access Configuration SPLTE (continued) Step Procedure 3 From the Test Access tab, TAC sub-tab, create a per side split (SPLTE) test access cross-connect (TAC) from the source (S1) to a logical TAP. Note: Use the Switch Mode button to switch from one mode configuration to another. For valid mode changes, see Table 5-1 Test Access Mode vs. Service Compatibility Matrix. SPLTE Mode TAP2 Service ID Connected State Switch Mode command Figure 5-12 SPLTE TAC Example Release OPS4.2.2 Force10 Networks Page 5-15

282 Operations and Maintenance Guide, Section 5: Test Access Per Side Split Test Access Example (SPLTE) Table 5-3 Per Side Split Test Access Configuration SPLTE (continued) Step Procedure 4 The system disables the original service as seen when you select the Service tab. Service ID Enabled Operational State Figure 5-13 Service with SPLTE TAC Example 5 With the TAC enabled to the RTU, you can now run various tests on the source service under test. Note: An alarm indication signal (AIS) is automatically transmitted in the direction of D1 to 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. Page 5-16 Force10 Networks Release OPS4.2.2

283 Chapter 1 Traverse Test Access Series Split Test Access Example (SPLTA) Series Split Test Access Example (SPLTA) The SPLTA series split test access configuration is intrusive. 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. Service to be Tested S1 DCS D1 TAP (e.g., DS1) Series Split Test Access (Intrusive) S1 DCS D1 TAP1 OPS Figure 5-14 Series Split Test Access Configuration SPLTA Release OPS4.2.2 Force10 Networks Page 5-17

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

285 Chapter 1 Traverse Test Access Series Split Test Access Example (SPLTA) Table 5-4 Series Split Test Access Configuration SPLTA (continued) Step Procedure 3 From the Test Access tab, TAP sub-tab, create a series split (SPLTA) test access cross-connect (TAC) from the source (S1) to a logical TAP. Note: Use the Switch Mode button to switch from one mode configuration to another. For valid mode changes, see Table 5-1 Test Access Mode vs. Service Compatibility Matrix. SPLTE Mode TAP3 Service ID Connected State Switch Mode command Figure 5-16 SPLTA TAC Example Release OPS4.2.2 Force10 Networks Page 5-19

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

287 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, page 5-1. Release OPS4.2.2 Force10 Networks Page 5-21

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

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

290 Operations and Maintenance Guide, Section 5: Test Access Guidelines to Set Up the Traverse Test Access Spirent BRTU Interface Page 5-24 Force10 Networks Release OPS4.2.2

291 SECTION 6 ROUTINE MAINTENANCE SECTION 6 SECTION 6 Contents Chapter 1 Routine Maintenance Fan Air Filter Maintenance Fan Assemblies Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000) Fan Module with Integral Fan Tray (Traverse 600) Fan Assembly (TE-100) Air Filters Air Filter Replacement Air Filter Replacement (Traverse 1600 and Traverse 2000) Fan Tray Air Filter Replacement (Traverse 600) Air Filter Replacement (TE-100) PDAP Maintenance PDAP-15A GMT Fuse Replacement PDAP-2S Circuit Breaker Replacement PDAP-2S GMT Fuse Replacement PDAP-2S LED Module Replacement PDAP-4S TPA Fuse Replacement PDAP-4S GMT Fuse Replacement PDAP-4S LED Module Replacement Environmental Alarm Module Replacement (Traverse only) Non-Field Replaceable Fuses Chapter 2 Node Database Backup and Restore Backing Up Traverse Node Databases Guidelines for Traverse Node Database Backups Traverse Node Database Restore Guidelines Help Backup and Restore CLI Commands exec node database backup Syntax Syntax Description exec node database restore Syntax Syntax Description Troubleshooting Traverse Node Backup and Restore TE-206 Node Database Backup Overview Release OPS4.2.2 Force10 Networks Page i

292 Operations and Maintenance Guide, Section 6 Routine Maintenance TE-206 Node Backups from the TransNav GUI Page ii Force10 Networks Release OPS4.2.2

293 SECTION 6ROUTINE MAINTENANCE Chapter 1 Routine Maintenance Introduction Fan Air Filter Maintenance Fan Assemblies This chapter provides routine maintenance tasks for node-specific system equipment: Fan Air Filter Maintenance, page 6-1 PDAP Maintenance, page 6-6 Environmental Alarm Module Replacement (Traverse only), page 6-17 The fan maintenance topics are as follows: Fan Assemblies, page 6-1 Air Filters, page 6-2 Air Filter Replacement, page 6-2 Front Inlet Fan Tray Module (Traverse 1600 and Traverse 2000) The Traverse 1600 and Traverse 2000 fan assembly (fan tray with integrated air ramp and fan module) cools the control modules and service modules in the shelf. The Traverse 1600 fan assembly has 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. Release OPS4.2.2 Force10 Networks Page 6-1

294 Operations and Maintenance Guide, Section 6: Routine Maintenance Air 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. Important: Fan tray air filters should be checked at six-month intervals and replaced as necessary. 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). 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. Air Filter Replacement Air Filter Replacement (Traverse 1600 and Traverse 2000) The fan air filter replacement topics are as follows: Air Filter Replacement (Traverse 1600 and Traverse 2000), page 6-2 Fan Tray Air Filter Replacement (Traverse 600), page 6-4 Air Filter Replacement (TE-100), page 6-5 When the front inlet fan tray air filter (for either Traverse 1600 or Traverse 2000) has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter. Required Equipment: New front inlet fan tray air filter. The front inlet fan tray air filters are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. Page 6-2 Force10 Networks Release OPS4.2.2

295 Chapter 1 Routine Maintenance Air Filter Replacement (Traverse 1600 and Traverse 2000) The following procedure provides step-by-step instructions on how to insert the front inlet fan tray air filter. Table 6-1 Insert a Traverse 1600 and Traverse 2000 Fan Air Filter Step 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 Install the new air filter. Grasp the air filter flexible pull tab. OPS Pull Tab (top view) Figure 6-1 Front Inlet Air Filter 3 Insert the air filter in the gap between the top of the front inlet fan card and the top of the front inlet fan tray holder. Slide the air filter along the fan tray holder guides until the filter is flush with the front of the fan tray holder. 4 The Insert a Traverse 1600 and Traverse 2000 Fan Air Filter procedure is complete. Release OPS4.2.2 Force10 Networks Page 6-3

296 Operations and Maintenance Guide, Section 6: Routine Maintenance Fan Tray Air Filter Replacement (Traverse 600) Fan Tray Air Filter Replacement (Traverse 600) When the Traverse 600 fan air filter has been in place for at least six months, or other environmental factors have contributed to requiring an air filter replacement, use the following procedure to replace the air filter. Required Equipment: New air filter The Traverse 600 fan air filters are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. The following procedure provides step-by-step instructions on how to insert the air filter. Table 6-2 Insert a Traverse 600 Fan Air Filter Step 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 Install the new air filter. Grasp the air filter flexible pull tab. OPS Figure 6-2 Traverse 600 Fan Assembly Air Filter Pull Tab (top view) 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. 4 The Insert a Traverse 1600 and Traverse 2000 Fan Air Filter procedure is complete. Page 6-4 Force10 Networks Release OPS4.2.2

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

298 Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP Maintenance Table 6-3 Replace the Fan Air Filter (TE-100) (continued) Step Procedure 5 Slide the air filter into place, lining up the small tabs with the small holes on the fan assembly. Tabs Lined up with Holes Figure 6-5 Attaching the Air Filter 6 Slide the fan assembly back into the fan cage. Important: Do not force the fan assembly into position. If it does not plug in easily, slide it back out and check for any obstructions that might prevent it from sliding into position. 7 Tighten the captive fastener to secure the fan assembly in place. 8 The Replace the Fan Air Filter (TE-100) procedure is complete. PDAP Maintenance PDAP-15A GMT Fuse Replacement The Power Distribution and Alarm Panel (PDAP) maintenance topics are as follows: PDAP-15A GMT Fuse Replacement, page 6-6 PDAP-2S Circuit Breaker Replacement, page 6-7 PDAP-2S GMT Fuse Replacement, page 6-8 PDAP-2S LED Module Replacement, page 6-10 PDAP-4S TPA Fuse Replacement, page 6-13 PDAP-4S GMT Fuse Replacement, page 6-15 PDAP-4S LED Module Replacement, page 6-16 The PDAP-15A provides GMT fuses (from 0.25 amps to 15 amps per fuse) for up to ten pieces of auxiliary equipment. The PDAP s field replaceable fuses are accessible without having to remove the front panel. Use the following procedure to replace a failed GMT fuse. WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits. Page 6-6 Force10 Networks Release OPS4.2.2

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

300 Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-2S GMT Fuse Replacement Table 6-5 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. PDAP-2S GMT Fuse Replacement The PDAP-2S contains two fuse blocks (A and B) of ten field replaceable GMT fuses. Each block has a 100 amp maximum load. Each pair of A and B GMT fuses (e.g., A1, B1) provides redundant power (from 0.25 to 10 amps per fuse) to one of up to ten pieces of auxiliary equipment. Use the following procedure to replace a failed GMT fuse. WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the Power Distribution and Alarm Panel (PDAP-2S). Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Page 6-8 Force10 Networks Release OPS4.2.2

301 Chapter 1 Routine Maintenance PDAP-2S GMT Fuse Replacement Table 6-6 Replacing PDAP-2S GMT Fuses Step Procedure 1 Remove the GMT fuse by pulling it straight out. 1 Figure 6-7 PDAP-2S GMT Fuses 2 Replace the failed GMT fuse with a new one of equal current rating. 3 The Replacing PDAP-2S GMT Fuses procedure is complete. 1 The GMT fuses protrude from the PDAP-2S front panel to allow access for fuse removal and insertion without having to remove the front panel. Release OPS4.2.2 Force10 Networks Page 6-9

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

303 Chapter 1 Routine Maintenance PDAP-2S LED Module Replacement Table 6-7 Replacing PDAP-2S LED Module (continued) Step Procedure 3 Locate the nonfunctional module with a white pull tab at the center of the PDAP-2S. Figure 6-9 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. 6 Replace the front cover. Figure 6-10 PDAP-2S LED Module Guides Release OPS4.2.2 Force10 Networks Page 6-11

304 Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-2S LED Module Replacement Table 6-7 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. Page 6-12 Force10 Networks Release OPS4.2.2

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

306 Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-4S TPA Fuse Replacement Table 6-8 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-11 PDAP-4S TPA Fuses 2 Remove the TPA fuse holder by pulling it straight out. 1 Figure 6-12 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. Page 6-14 Force10 Networks Release OPS4.2.2

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

308 Operations and Maintenance Guide, Section 6: Routine Maintenance PDAP-4S LED Module Replacement PDAP-4S LED Module Replacement The Power Distribution and Alarm Panel (PDAP-4S) system alarm LEDs (Critical, Major, Minor), power input A and B LEDs, and TPA/GMT fuse block failure LED (for both A and B) are on one field replaceable module. Use the following procedure to replace the PDAP-4S LED module. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working on the PDAP-4S. Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Table 6-10 Replacing PDAP-4S LED Module Step Procedure 1 Loosen the two PDAP-4S LED faceplate captive fasteners to release it. Figure 6-14 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. Page 6-16 Force10 Networks Release OPS4.2.2

309 Chapter 1 Routine Maintenance Environmental Alarm Module Replacement (Traverse only) Environmental Alarm Module Replacement (Traverse only) The Environmental Alarm Module (EAM) located on the Traverse main back plane supports the environmental telemetry inputs and outputs. The EAM is an optional, field replaceable module required to support environmental alarm input/output functionality. Environmental signals are accessed through wire-wrap posts located on the main backplane, allowing the EAM to be replaced without disconnecting alarm wiring. Use the following procedure to replace the EAM on the Traverse backplane. Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when working with the EAM and the main backplane. Plug the ESD wrist strap into the ESD jack provided on the air ramp or other confirmed source of earth ground. Table 6-11 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-15 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. Release OPS4.2.2 Force10 Networks Page 6-17

310 Operations and Maintenance Guide, Section 6: Routine Maintenance Non-Field Replaceable Fuses Table 6-11 Replacing EAM (continued) Step Procedure 3 Insert the module into the main backplane EAM connector using the plastic standoff and proper alignment guides. The plastic standoff tab clicks into place when the module is properly seated. Important: The module should insert easily into the main backplane connector. Do not force it into position. If the module does not insert easily, pull it back out and verify you are placing it in the correct position and inserting it along the plastic standoff and proper alignment guides. Long edge Pins facing Main Backplane Proper Alignment Guide Plastic Standoff Guide Figure 6-16 EAM Alignment 4 The Replacing EAM procedure is complete. Non-Field Replaceable Fuses The following components in the Traverse system contain non-field replaceable fuses: Control module Service interface module Fan tray If a Traverse module requires (non-field replaceable) fuse replacement, 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. Page 6-18 Force10 Networks Release OPS4.2.2

311 SECTION 2ROUTINE MAINTENANCE Chapter 2 Node Database Backup and Restore Introduction Backing Up Traverse Node Databases 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 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 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. Release OPS4.2.2 Force10 Networks Page 2-19

312 Operations and Maintenance Guide, Section 2: Routine Maintenance Guidelines 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 (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. Command descriptions use the following conventions: Table 2-12 CLI Command Conventions Command Description Vertical bars ( ) separate alternative, mutually exclusive elements. You must enter one of the options as part of the command. [ ] Square brackets ([ ]) indicate optional elements. { } Braces ({ }) indicate a required choice of a command element. Boldface Boldface indicates literal commands and keywords that are entered exactly as shown. Note: You can abbreviate literal commands. See the Section 1 Overview and Quick Reference, Chapter 1 CLI Overview, Using Shortcuts, page Page 2-20 Force10 Networks Release OPS4.2.2

313 Chapter 2 Node Database Backup and Restore Backup and Restore CLI Commands Table 2-12 CLI Command Conventions Command Italics Boldface Underlined Description Italics indicate arguments for which you supply values. Boldface Underlined or underlined in parentheses (value) is a default value if you do not provide your own. Default values are set when an object (such as a service or interface) is created using the create command. 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 user-name password path filename - IP address of the FTP server where the database will be backed up - username to use when accessing the FTP server - password to use when accessing the FTP server - enter the path on the FTP site where the database will be backed up - enter the file name to call the database file l exec node database restore. Use the exec node database restore command to restore the Traverse node database. Syntax exec node database restore [host ip address user-name UserName password password [path blank][filename nodedb.xxx]] Syntax Description ip address - IP address of the FTP server where the database is backed up Release OPS4.2.2 Force10 Networks Page 2-21

314 Operations and Maintenance Guide, Section 2: Routine Maintenance Troubleshooting Traverse Node Backup and Restore user-name password path filename - username to use when accessing the FTP server - password to use when accessing the FTP server - enter the path on the FTP site from where the database will be restored - enter the file name of the database file Troubleshooting Traverse Node Backup and Restore TE-206 Node Database Backup Overview 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. 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 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. Page 2-22 Force10 Networks Release OPS4.2.2

315 Chapter 2 Node Database Backup and Restore TE-206 Node Backups from the TransNav GUI 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 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. Figure 2-17 Initial Node Backup Scheduler Dialog Box Release OPS4.2.2 Force10 Networks Page 2-23

316 Operations and Maintenance Guide, Section 2: Routine Maintenance TE-206 Node Backups from the TransNav GUI To create manual backup or to schedule an automatic backup, select Action, Create. The Create Backup Scheduler dialog box displays. Figure 2-18 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. Page 2-24 Force10 Networks Release OPS4.2.2

317 Chapter 2 Node Database Backup and Restore TE-206 Node Backups from the TransNav GUI 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 2-19 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 2-20 Manage Node Backups Dialog Box ID: Indicates the system-generated identifier of the scheduled backup. Release OPS4.2.2 Force10 Networks Page 2-25

318 Operations and Maintenance Guide, Section 2: Routine Maintenance TE-206 Node Backups from the TransNav GUI 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. Page 2-26 Force10 Networks Release OPS4.2.2

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

320 Operations and Maintenance Guide, Section 7 Software Upgrades User- selectable FPGA Upgrade Capability Overview to Upgrade TE-206 Nodes from TransNav Requirements for Upgrading TE-206 Node Software Downloading TE-206 Node Software Upgrading TE-206 Node Software from TransNav Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Release TE3.2.x Upgrade Overview Before You Begin Required Equipment and Tools Software Hardware General TE-100 Shelf TransNav Management System GUI Commands and Conventions Compatibility and Guidelines General Software Compatibility TE-100 Platform SW Upgrade Compatibility Notes Guidelines for Software Upgrade Node Software Upgrade Process Download Node Software to the TransNav Server Download Node Software to the TransNav Server Module Software Download Set-up Card Software Version Verification Software Activation Process Activate Software - Control Module Spare Control Module Software Activation Software Revert Procedure Revert Node Software Revert TransNav Management System Software Page ii Force10 Networks Release OPS4.2.2

321 SECTION 7SOFTWARE UPGRADES Chapter 1 Release TR3.2.2 Traverse Software Upgrade Introduction Release TR3.2.2 Upgrade Overview This chapter provides the following information including steps on how to initiate and complete software upgrades to nodes in your network using the TransNav GUI. Complete the TR3.2.2 software upgrade of all modules in a Traverse node using the release TN4.2.2 TransNav management system graphical user interface (GUI). Release TR3.2.2 Upgrade Overview, page 7-1 Node Software Upgrade Flowchart (Top Level), page 7-2 Before You Begin, page 7-3 Required Equipment and Tools, page 7-3 TransNav Management System GUI Commands and Conventions, page 7-4 Compatibility and Guidelines, page 7-4 Node Software Upgrade Process, page 7-7 Software Revert Procedure, page 7-40 Post-Remote Node Upgrade the Spare Control Module Software, page 7-41 User- selectable FPGA Upgrade Capability, page 7-43 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-44 Requirements for Upgrading TE-206 Node Software, page 7-46 Downloading TE-206 Node Software, page 7-46 Upgrading TE-206 Node Software from TransNav, page 7-48 Release TR3.2.2 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.2 from the following previous releases: TR2.1.x, TR3.0.x, and TR3.1.x. Point releases (as necessary) for the TR3.2.x Traverse nodes. Upgrades of TE-206 nodes from the TransNav system. Remote upgrade capability. User-selectable Field Programmable Gate Array (FPGA) upgrade capability. Release OPS4.2.2 Force10 Networks Page 7-1

322 Operations and Maintenance Guide, Section 7: Software Upgrades Node Software Upgrade Flowchart (Top Level) Simultaneous TransNav Management System (TN4.2.2) software management of Traverse Release TR2.1.x, TR3.0.x, TE3.2.x and TE3.0.x TE-100 nodes to accommodate longer-term upgrade paths. Node Software Upgrade Flowchart (Top Level) The diagram below shows a top-level flow for the node software upgrade process. Node Software Upgrade to Release TR3.2.x Top-Level Flowchart {IMPORTANT! For details, refer to the specific software upgrade procedures in the manual} Begin Read release nodes, upgrade compatibility notes, guidelines, and all upgrade procedures Operations Manager Operations Manager creates a comprehensive upgrade plan Read and understand the release notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company's comprehensive upgrade plan Upgrade Team Point release upgrade? YES NO TR2.1.x, TR3.0.x to TR3.2.x major release upgrade? YES Follow the Node Upgrade Process Go to Page 2 NO pre-tr2.1.x release upgrade? YES Contact Technical Assistance Center (TAC) End OPS Figure 7-1 Node Software Upgrade Process Flowchart Page 7-2 Force10 Networks Release OPS4.2.2

323 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Required Equipment and Tools Before You Begin Review these requirements before you begin. Table 7-1 Node Software Upgrade Requirements Requirement Compose and have ready for the Upgrade Team a comprehensive network upgrade plan. Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company s comprehensive upgrade plan. The software upgrade feature for this release supports Traverse TR2.1.x or TR3.0.x to TR3.2.x and TransNav TN4.0.x to TN4.2.x upgrades. Have the required equipment and tools ready. Reference Your company s Operations Manager is responsible for this task. See Release Notes TR3.2.x ( TR32). 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. If you are upgrading from an earlier Traverse or TransNav software release, contact the Force10 TAC. Required Equipment and Tools, page 7-3 Required Equipment and Tools The following equipment and tools are required for a Traverse system software upgrade to a node or multiple nodes in a domain: TransNav management system server connected to a gateway Traverse node Access to the online Infocenter website at Note: If you do not have access to the Infocenter, user registration is required. Contact your local sales representative to register. 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 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 Release OPS4.2.2 Force10 Networks Page 7-3

324 Operations and Maintenance Guide, Section 7: Software Upgrades TransNav Management System GUI Commands and Conventions System interface module (SIM) cards Note: The number and combination of SIMs is based on your network requirements and physical cabling at the Traverse main and fiber optic backplanes. TransNav Management System GUI Commands and Conventions This document provides node software upgrade procedures using the TransNav GUI. Refer to the TransNav Management System Product Overview Guide to become familiar with the TransNav system. The following conventions are used in the procedure tables. Table 7-2 TransNav GUI Command Descriptions Command Boldface Italics Description Boldface indicates dialog boxes, fields, menus, and list names. Italics indicate information that you supply. Compatibility and Guidelines General Software Compatibility Notes Read the compatibility topics that are relevant to your specific upgrade. General Software Compatibility Notes, page 7-4 Traverse System SW Upgrade Compatibility Notes, page 7-5 Guidelines for Software Upgrade, page 7-6 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: ): 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. Page 7-4 Force10 Networks Release OPS4.2.2

325 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Traverse System SW Upgrade Compatibility Notes The Active control card with a (major.x.x.x) software version higher than the TransNav management system can support. In these cases, use the procedures in this section to upgrade or rollback the software version on the replacement card. A SWMIS: Software version mismatch alarm is generated when a replacement card with either an earlier or later (major.minor.build.x) version of software than the software running on the control card is placed in the node. In this case, use the procedures in this section to upgrade or rollback the software version on the replacement card. Traverse System SW Upgrade Compatibility Notes Review this information to understand the important compatibility items for Traverse and TransNav software releases. General Release TN4.2.x TransNav management system software: simultaneously manages Release TR2.1.x, TR3.0.x, and TR3.2.x Traverse nodes. manages the in-service software upgrade from Release TR2.1.x or TR3.0.x to TR3.2.x, as well as, any TR3.0.x maintenance releases. manages a network of mixed nodes running Release TR2.1.x, TR3.0.x, and TR3.2.x for functions including: Service management (provisioning, activation, deactivation, deletion, etc.) Alarms and performance monitoring (on-demand and periodic) Node and module addition and deletion Loopback External commands on protection groups The remote upgrade capability manages the arrival of older version modules and allows for remote download and activation of such modules to the TR3.2.x release. For TR2.1 and subsequent releases, line-derived timing modules (e.g., OC-3/STM-1) support only one timing reference. In pre-tr2.1 releases, line-derived timing modules would support multiple timing references. When a service provider replaces an old card with a new card, they should plan for and make the line-derived timing reference provisioning changes accordingly (i.e., move the timing references to different modules). Upon in-service replacement, the Traverse system raises and alarm and uses the timing reference of the lowest-numbered port on the module that was previously provisioned with multiple timing references, and ignores the timing provisioning for the higher-numbered ports. 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.x Maintenance Releases Hitless software upgrade and warm restart are available, unless otherwise noted in the specific maintenance software Release Notes document. Release OPS4.2.2 Force10 Networks Page 7-5

326 Operations and Maintenance Guide, Section 7: Software Upgrades Guidelines for Software Upgrade In-service, hitless software upgrade support is available for Release TR3.2.x and future maintenance releases. Software Upgrade from Release TR2.1.x or TR3.0.x to TR3.2.x Support for in-service software upgrades from Release TR2.1.x or TR3.0.x to TR3.2.x 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 modules (i.e., Traverse GCM) at least 5 minutes apart. Perform an upgrade on spare modules, unless you are using the remote upgrade capability and plan to upgrade spares at a later time (see Post-Remote Node Upgrade the Spare Control Module Software, page 7-41 for details). In either case, always upgrade (download and activate) both the standby and active GCM cards before upgrading any spare GCM cards. Software upgrade is to be errorless. Release Notes TR3.2.1 ( TR321) defines any potential exceptions. This document resides on the Infocenter website at and user registration is required to access it. To register, contact your sales account team. Page 7-6 Force10 Networks Release OPS4.2.2

327 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Node Software Upgrade Process Node Software Upgrade Process Traverse and TransNav support in-service software upgrade from Release TR2.1.x or TR3.0.x to TR 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 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: Table 7-3 Node Software Upgrade Process Step Procedure Reference 1 Have you read through, and do you understand, all the Before You Begin items? 2 Do you have the required equipment and tools ready? 3 Upgrade the TransNav Management System server software (includes first exporting the current database off the TransNav server). Note: Do not uninstall the previous version. Mark the directory as old and remove the Icon from the desktop. Note: NETSYNC alarms occur when you start the GUI, after the server software upgrade, and before upgrading the node software. The master network objects (e.g., alarm profiles) are out of synchronization with propagated node objects. 4 Download the new node software to the TransNav server. Before You Begin, page 7-3 Required Equipment and Tools, page 7-3 TransNav Management System Server Guide, Section 2 Management Server Procedures, Chapter 3 Server Administration Procedures, Upgrade Server Software, page 2-49 Download Node Software to the TransNav Server, page Download the software to the cards. Module Software Download Set-up, page Activate the new software. Software Activation Process, page The Node Software Upgrade Process is complete. Release OPS4.2.2 Force10 Networks Page 7-7

328 Operations and Maintenance Guide, Section 7: Software Upgrades Download Node Software to the TransNav Server Download Node Software to the TransNav Server Download Node Software to the TransNav Server You must first download the node software for the upgrade from the Infocenter onto a TransNav server before proceeding with the upgrade procedures. Choose one of the following download procedures, depending on the TransNav EMS platform (i.e., PC or Solaris) for your network. The Infocenter can be accessed at User registration is required. To register for the Force10 Infocenter, contact your sales account team. Download Node Software to the TransNav Server, page 7-8 Use these steps to download node software to the TransNav server. Table 7-4 Download Node Software to the TransNav Server Step Procedure 1 Navigate to the directory where the software files were previously downloaded from the Infocenter. 2 In an Explorer window, navigate to the drive containing the temporary download directory. Figure 7-2 Example PC System Explorer Window File Listing 3 Right-click on the flash.n.n.n.n.zip file (where n.n.n.n is the latest software release number). For PC systems, select the Extract to command. For Solaris systems, use the gunzip command. Figure 7-3 Explorer Extract to Command Page 7-8 Force10 Networks Release OPS4.2.2

329 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Download Node Software to the TransNav Server Table 7-4 Download Node Software to the TransNav Server Step Procedure 4 From the Extract dialog box, select a user-defined folder path directory (e.g., /upgrade/files), then click Extract to download the flash files into the /<user-defined>/flash directory. Important: Verify the Use folder names check box is selected to keep the./flash relative path structure in the zip file intact upon download. Figure 7-4 Extract Dialog Box 5 After the file extraction completes, the WinZip dialog box for the zip file archive remains open. Select File, then Exit to exit the dialog box. 6 The Download Node Software to the TransNav Server procedure is complete. Continue to Step 5 of the Node Software Upgrade Process, page 7-7. Release OPS4.2.2 Force10 Networks Page 7-9

330 Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Module Software Download Set-up Software upgrades are done at the node level. The following procedure provides steps on how to begin a software upgrade by setting software download times for each card using the SW Upgrade dialog box. Table 7-5 Card Software Download Set-up Step Procedure 1 Verify the card software versions. Refer to Card Software Version Verification, page In Shelf View, select SW Upgrade from the Admin menu to display the SW Upgrade dialog box. Figure 7-5 SW Upgrade Dialog Box 3 Server IP Address: Enter the TransNav server IP address where the new node software version was downloaded from the Infocenter. (For example: aaa.bbb.ccc.ddd) 4 Base Path: Enter the directory path on the TransNav server to the node software files. (For example: /files/node/flash) 5 Username: Enter the user name with File Transfer Protocol (FTP) permission access to the TransNav server where the new node software version resides. (For example: ftpusername) 6 Password: Enter the user password with FTP permission access to the TransNav server where the new node software version resides. (For example: ftppassword) 7 Click 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. Page 7-10 Force10 Networks Release OPS4.2.2

331 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Module Software Download Set-up 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, 7 Figure 7-6 Download Time Settings Release OPS4.2.2 Force10 Networks Page 7-11

332 Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Table 7-5 Card Software Download Set-up (continued) Step Procedure 9 From the Download Time drop-down box, select Set time to manually adjust the time. Select part of the time string (e.g., month, day, hour). Use the up and down arrows or manually re-enter the time to reset the value. 8 Figure 7-7 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. Page 7-12 Force10 Networks Release OPS4.2.2

333 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Module Software Download Set-up Table 7-5 Card Software Download Set-up (continued) Step Procedure 13 You can Clear Download Time for any card by right-clicking the card in the SW Upgrade dialog box and clicking the Update button. If necessary, you can Abort Download to any card by right-clicking the card in the SW Upgrade dialog box. Note: 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. 12 Figure 7-8 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. Release OPS4.2.2 Force10 Networks Page 7-13

334 Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Table 7-5 Card Software Download Set-up (continued) Step Procedure 16 Continue only when the Download Status is OK and the newly downloaded software version displays in Standby SW Version field for all cards (select each card row and check the Standby SW Version field). This indicates the software download has successfully completed. 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-2 Step 3 of the Spare Module Software Activation (All Other Types), page 7-33 Page 7-14 Force10 Networks Release OPS4.2.2

335 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Software 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. 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. 2 Figure 7-9 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: ): 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. Software Activation Process The new software is not active until the software is activated and system reboots each module. The reboot loads and executes the new software, and in the case of the control module, upgrades the database. Important: Read all important notes below before beginning the activation process. Important: Software activation should start at the node farthest from the server that is connected to the head-end node, then work inward. Release OPS4.2.2 Force10 Networks Page 7-15

336 Operations and Maintenance Guide, Section 7: Software Upgrades Software 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 module at a time. This requires you to observe the reboot process and set the activate time for each module after the previous module reboot is complete. Check the Alarms dialog box to verify that the equipment alarm, caused by the reboot, has cleared before setting the activate time for the next module. Important: Any unprotected traffic residing on an Enhanced GCM (EGCM) with Optics module will experience an outage until the EGCM is restored from activation. Important: During software activation, the modules automatically reboot. Do not execute any external commands on the modules during software activation. Important: If you are upgrading a BLSR/MS-SP Ring network without GCMs with Optics, make sure to perform a lockout on the span before activating the line module. Once the line modules for the span on both nodes have been activated, release the force switch. Perform this step on each span in the BLSR/MS-SP Ring network. Table 7-7 Software Activation Process Step Procedure Reference 1 Did you complete the upgrade of TransNav EMS server and client software and download the node software to the TransNav server? 2 Did you download the node software to the TransNav server? 3 Is the module software download complete? 4 Do you have your network nodes in a BLSR/MS-SP Ring network with Traverse Enhanced GCMs with Optics? Section 2 Management Server Procedures, Chapter 1 Server Administration Procedures, Upgrade Server Software, page 2-12 Download Node Software to the TransNav Server, page 7-8 Module Software Download Set-up, page 7-10 Activate software for all modules set up in a BLSR/MS-SP Ring protection group. See BLSR/MS-SP Ring on GCM with Optics Software Activation, page 7-18 Continue to Step 6 of this process to software upgrade activate all other protected modules. Page 7-16 Force10 Networks Release OPS4.2.2

337 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Software Activation Process Table 7-7 Software Activation Process (continued) Step Procedure Reference 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 modules at a later time (see page 7-41) 6 Activate software for all modules set up in a protection group. 7 Activate software for all unprotected modules. 8 Activate software for all other types of spare modules, unless you are using the remote upgrade capability and want to upgrade your spare modules at a later time. Control Module Software Upgrade Activation, page 7-22 Software Upgrade Activate (all other protected modules), page 7-27 Software Upgrade Activate (all unprotected modules), page 7-30 Spare Module Software Activation (All Other Types), page The Software Activation Process is complete. Release OPS4.2.2 Force10 Networks Page 7-17

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

339 Chapter 1 Release TR3.2.2 Traverse Software Upgrade BLSR/MS-SP Ring on GCM with Optics Software Activation Table 7-8 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 5 Click the standby GCM with Optics Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. 6 Figure 7-11 SW Activation Activate Time 6 Select the activation type Act Type (default=nsa). Service Affecting (SA) is required for standby GCM with Optics module activation. Valid values are: NSA (non-service-affecting): Default. Will not activate an active node GCM. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Only use this option in the instance where the standby and active control modules have already been upgraded and activated. 7 Select to warm reboot (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the table, Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TRx.x.x, in the Release Notes. 8 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-43 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. Release OPS4.2.2 Force10 Networks Page 7-19

340 Operations and Maintenance Guide, Section 7: Software Upgrades BLSR/MS-SP Ring on GCM with Optics Software Activation Table 7-8 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 10 View the status of the software activation in the Act Status field of the SW Upgrade dialog box. The following status displays: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry software activation. Contact Force10 TAC if software activation fails a second time. Important: The activation status will show INPROGRESS, then NONE until the module has completed the upgrade; then it will show OK. This is normal behavior. 11 Verify that the new software version activation is complete and it displays in the SW Activation dialog box, Current SW Ver column Figure 7-12 Act Status and Current SW Ver Fields 12 With the standby GCM with Optics selected in Shelf View, select the Alarms tab and check the Alarms dialog box. Verify that the EQFAIL: equipment failure alarm caused by the reboot has cleared. 13 A SWMIS: Software version mismatch alarm is generated since the standby GCM with Optics software version is now mismatched with the active GCM with Optics. This is normal behavior. 14 Clear the near-end Forced Switch using the procedure in Table 7-17 Clear Protection Switch, page Verify that the BLSR/MS-SP Ring has returned to normal operation. If not, initialize the BLSR/MS-SP Ring. 15 Execute a BLSR/MS-SP Ring Forced Switch on the active GCM with Optics module following the procedure in Table 7-15 Perform a Forced Switch, page Check the BLSR/MS-SP Ring state and verify that Force is issued on the near- and far-end. Page 7-20 Force10 Networks Release OPS4.2.2

341 Chapter 1 Release TR3.2.2 Traverse Software Upgrade BLSR/MS-SP Ring on GCM with Optics Software Activation Table 7-8 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 16 Click the active GCM with Optics module Activate Time field in the SW Activation dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. Note: You can clear the Activation Time for any module by right-clicking the module in the SW Activation dialog box and selecting Clear Activation Time from the shortcut menu. 17 Select the activation type Act Type (default=nsa). Service Affecting (SA) is required for standby GCM with Optics module activation. Valid values are: NSA (non-service-affecting): Default. Will not reboot (activate) an active node GCM. SA (service-affecting): Will activate and reboot the node GCM regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Only use this option in the instance where the standby and active control modules have already been upgraded and activated. 18 Select to warm reboot (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the table, Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TRx.x.x, in the Release Notes. 19 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-43 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. 20 Click Update. 21 Verify that the new software version activation is complete and it is displayed in the SW Activation dialog box, Current SW Ver field. Note: Activating the active GCM causes the new software to upgrade and a switchover to the protection module. 22 With the now standby (previously active) GCM with Optics module selected in Shelf View, select the Alarms tab and check the Alarms dialog box. Verify the EQFAIL: equipment failure alarm caused by the reboot has cleared. Release OPS4.2.2 Force10 Networks Page 7-21

342 Operations and Maintenance Guide, Section 7: Software Upgrades Control Module Software Upgrade Activation Table 7-8 Activate Software BLSR/MS-SP Ring GCM with Optic Modules Step Procedure 23 The SWMIS: Software version mismatch alarm generated on the previously standby GCM with Optics clears as both GCM with Optics software versions now match. However, this alarm is now generated for all other modules in the system as their software versions are now mismatched with the active GCM with Optics. This is normal behavior. 24 Clear the near-end Forced Switch using the procedure in Table 7-17 Clear Protection Switch, page Verify that the BLSR/MS-SP Ring has returned to normal operation. 25 If you have spare GCM with Optic modules to software upgrade at this time (i.e., you are not using the remote upgrade capability), remove the standby GCM with Optics module from the shelf and install the spare GCM with Optics. Complete the Spare Control Module Software Activation, page 7-32 procedure. 26 The Activate Software BLSR/MS-SP Ring GCM with Optic Modules procedure is complete. Return back to Step 4 of the Software Activation Process, page Control Module Software Upgrade Activation The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software on the control module at each node. Important: Do not start the Activate Software Control Module procedure until the downloaded software version displays. This indicates the software download has completed successfully. The software version displays in the SW Activation dialog box, Standby SW Ver field for all modules. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Activation dialog box. Follow these step-by-step instructions to set up software upgrade activation for node GCMs. Table 7-9 Activate Software Control Module Step Procedure 1 Verify the network is alarm free or validate and record any alarms present prior to activation. 2 In Shelf View, select a control module and click the Config tab. Page 7-22 Force10 Networks Release OPS4.2.2

343 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Control Module Software Upgrade Activation Table 7-9 Activate Software Control Module (continued) Step Procedure 3 Verify the Protection Status of the Active/Standby control module using the Card Configuration dialog box. 3 Figure 7-13 Card Configuration Protection Status 4 Click the standby control module Activate Time field in the SW Activation dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. 4 Figure 7-14 SW Activation Activate Time 5 Select the activation type Act Type (default=nsa). Change to SA for standby control module activation. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control module. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Use this option only when the standby and active control modules have already been upgraded and activated. 6 If the module does not require a cold restart, then select to warm restart (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the table, Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TRx.x.x, in the Release Notes. Release OPS4.2.2 Force10 Networks Page 7-23

344 Operations and Maintenance Guide, Section 7: Software Upgrades Control Module Software Upgrade Activation Table 7-9 Activate Software Control Module (continued) Step Procedure 7 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-43 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. 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 module has completed the upgrade; then it will show OK. This is normal behavior. 10 Verify that the new software version activation is complete and it displays in the SW Activation dialog box, Current SW Ver field. Important: If there are any unexpected discrepancies here, STOP and contact Force10 TAC Figure 7-15 Act Status and Current SW Ver Fields 11 With the standby control module selected in Shelf View, select the Alarms tab and check the Alarms dialog box. 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 module software version is now mismatched with the active control module. This is normal behavior. Page 7-24 Force10 Networks Release OPS4.2.2

345 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Control Module Software Upgrade Activation Table 7-9 Activate Software Control Module (continued) Step Procedure 13 If the control modules contain integrated VTX/VCX modules in a protection group (e.g., GCM with VTX/VCX), you must perform a Manual switch on the active module (module with the old software) to change its state to standby. Refer to the procedure, Perform a Manual Switch, on page 7-36 for details. Note: The manual protection switch on certain modules is necessary due to FPGA changes. 14 After the manual switch is complete, repeat Steps 3 through 12, for the now standby module (module with the old software) of the protection group. 15 Release (clear) the protection switch after activation is complete on the standby module to return it to its original active status. Refer to the Clear Protection Switch procedure on page 7-38 for details. 16 Click the active control module Activate Time field in the SW Activation dialog box to display the current date and time. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. Note: Clear the Activation Time for any module by right-clicking the module in the SW Activation dialog box and selecting Clear Activation Time from the shortcut menu. 17 Act Type (default=nsa). Select SA (service-affecting) activation type for the active control module. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control module. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. SPARE (non-service-affecting): Will activate and reboot the spare (standby) control module. Use this option only when the standby and active control modules have already been upgraded and activated. 18 Select to warm reboot (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the table, Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TRx.x.x, in the Release Notes. Release OPS4.2.2 Force10 Networks Page 7-25

346 Operations and Maintenance Guide, Section 7: Software Upgrades Control Module Software Upgrade Activation Table 7-9 Activate Software Control Module (continued) Step Procedure 19 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-43 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. 20 Click Update. 21 View the status of the software activation in the Act Status field of the SW Activation dialog box. The following status types display: NONE: Software activation has not begun. INPROGRESS: Software activation has begun, but is not complete. OK: Software activation has successfully completed. FAILED: Software activation has failed. Retry the software activation. Contact the Force10 TAC if the software activation fails a second time. Important: The activation status will show INPROGRESS, then NONE until the module has completed the upgrade; then it will show OK. This is normal behavior. 22 Verify that the new software version activation is complete and it is displayed in the SW Activation dialog box, Current SW Ver field. Note: Activating the active control module causes the new software to upgrade and a switchover to the protection module. 23 With the now standby (previously active) control module selected in Shelf View, select the Alarms tab. Check the Alarms dialog box to verify the EQFAIL: equipment failure alarm caused by the reboot has cleared. 24 The SWMIS: Software version mismatch alarm generated on the previously standby control module clears as both control module software versions now match. However, this alarm is now generated for all other modules in the system as their software versions are now mismatched with the active control module. This is normal behavior. 25 If you have spare control modules to software upgrade at this time (i.e., you are not using the Remote Upgrade feature), remove the standby control module from the shelf and install the spare (standby) control module. Complete the Spare Control Module Software Activation, page 7-32 procedure. 26 The Activate Software Control Module procedure is complete. Continue to Step 6 of the Software Activation Process, page Page 7-26 Force10 Networks Release OPS4.2.2

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

348 Operations and Maintenance Guide, Section 7: Software Upgrades Software Upgrade Activate (all other protected modules) Table 7-10 Activate Software All Other Protected Modules (continued) Step Procedure 4 Set the activation type Act Type to SA for the module. Valid types are: NSA (non-service-affecting): Default. Will not activate a module if it has any active services. SA (service-affecting): Activates the software and reboots the module regardless of any services. 5 If the module does not require a cold restart, then select to warm restart (Warm Rbt) this module. To learn more about those modules that allow a warm reboot upgrade, see the table, Cold Reboot Matrix for Modules on Upgrade from Previous Releases, in the Release Notes. 6 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-43 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. 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. 8 9 Figure 7-17 Act Status and Current SW Ver Fields Page 7-28 Force10 Networks Release OPS4.2.2

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

350 Operations and Maintenance Guide, Section 7: Software Upgrades Software Upgrade Activate (all unprotected modules) Software Upgrade Activate (all unprotected modules) Use the following step-by-step instructions to set up software upgrade activation for all unprotected modules: Table 7-11 Activate Software All Unprotected Modules Step Procedure 1 Proceed with software upgrade activation on all unprotected modules after the software activation has successfully completed (Act Status=OK) on both the control modules and then on all other protected modules before clearing any service-affecting alarms on the node. 2 Click the unprotected module Activate Time field to display the current date and time. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. 2 Figure 7-18 SW Activation Activate Time 3 Select the activation type Act Type and set to SA for the module. Valid values are: NSA (non-service-affecting): Default. Will not activate an active control module. SA (service-affecting): Will activate and reboot the control module regardless of its active or standby status. 4 If the module does not require a cold restart, select to warm restart (Warm Rbt) this module. To learn more about the modules that allow a warm reboot upgrade, seethe table, Cold Reboot Matrix for Modules on Upgrade from Previous Releases to Release TRx.x.x, in the Release Notes. 5 Select to ignore the FPGA upgrade available on this module. See Userselectable FPGA Upgrade Capability, page 7-43 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. 6 Click Update. Page 7-30 Force10 Networks Release OPS4.2.2

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

352 Operations and Maintenance Guide, Section 7: Software Upgrades Spare Control Module Software Activation Spare Control Module Software Activation The new software is not active until the system activates the software and reboots the spare (standby) control module. The reboot loads and executes the new software. Important: This procedure assumes you have completed upgrading (downloading and activating the new software for) the standby and active control modules. Important: A spare control module can only be upgraded in a shelf that has the same type of control module. For example, if the standby Traverse GCM is a GCM with OC-48 module, you can only upgrade GCM with OC-48 modules in this procedure. If the standby TE-100 System module is an OC-48 module, you can only upgrade with another OC-48 system module. The activation is scheduled for each module at the node based on the date and time entered in the Activate Time field of the SW Activation dialog box. Follow these step-by-step instructions to set up software upgrade activation for spare control modules. Table 7-12 Activate Software Spare Control Modules Step Procedure 1 Remove the upgraded standby control module by restarting the module through the TransNav management system, then removing the module from the shelf. 2 Insert the spare (standby) control module. 3 Once the spare control module is online and the EQRMV/EQCOMM alarms are clear, download the new software version to the module using the Table 7-5 Card Software Download Set-up, page 7-10 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-9 Activate Software Control Module, page 7-22 procedure. 5 Repeat Steps 1 through 4 for each spare control module. 6 Once the upgrade and activation is complete for all the spare control modules you can either: Leave the last spare in place to act as the new standby module. Replace the original standby control module back into the standby slot and continue the procedure. 7 The Activate Software Spare Control Modules procedure is complete. Depending on the procedure from which you came, continue to either: Step 24 of the procedure BLSR/MS-SP Ring on GCM with Optics Software Activation, page 7-20 Step 26 of the procedure Control Module Software Upgrade Activation, page 7-26 Page 7-32 Force10 Networks Release OPS4.2.2

353 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Spare Module Software Activation (All Other Types) Spare Module Software Activation (All Other Types) The new software is not active until the system activates the software and reboots the spare modules that are not control modules. The reboot loads and executes the new software. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Activation dialog box. Use the following step-by-step instructions to set up the software upgrade activation for the spare modules. Table 7-13 Activate Software Spare Modules (All Other Types) Step Procedure 1 Insert the spare module in an unused slot in the shelf that has an empty slot to both the left and the right of the spare module. 2 Once the spare module is online and the EQRMV/EQCOMM alarms are clear, download the new software version to the module using the Module Software Download Set-up, page 7-10 procedure. 3 Once the new software downloads to the spare module, activate the software using the steps described in the Software Upgrade Activate (all other protected modules), page 7-27 procedure. 4 Repeat Steps 1 through 3 for each spare module. 5 The Activate Software Spare Modules (All Other Types) procedure is complete. Continue to Step 9 of the Software Activation Process, page Release OPS4.2.2 Force10 Networks Page 7-33

354 Operations and Maintenance Guide, Section 7: Software Upgrades Verify Protection Status Verify Protection Status Follow these step-by-step instructions to verify the protection status (Standby or Active) of a module/port in a protection group: Table 7-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. 2 Figure 7-20 Protection Groups Dialog Box 3 Select the protection group. 4 Click Edit to display the Protection Group Configuration dialog box. 5 The status displays in the Protection field - either Active or Standby. 5 Figure 7-21 Equipment Protection Group Configuration Dialog Box 6 The Verify Protection Status procedure is complete. Continue to Step 3 of the Software Upgrade Activate (all other protected modules), page Page 7-34 Force10 Networks Release OPS4.2.2

355 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Perform 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. 1 2 Select the protection group. Figure 7-22 Protection Groups Dialog Box 3 Click Edit to display the Protection Group Configuration dialog box. 4 Right-click the module or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Forced from the shortcut menu. 4 Figure 7-23 Protection Group Forced Switch 5 The Confirm Force Switch dialog box displays. Click Yes to confirm. Figure 7-24 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. Release OPS4.2.2 Force10 Networks Page 7-35

356 Operations and Maintenance Guide, Section 7: Software Upgrades Perform a Manual Switch Table 7-15 Perform a Forced Switch (continued) Step Procedure 7 The active module or port is switched to standby. 8 The Perform a Forced Switch procedure is complete. If you were in the procedure BLSR/MS-SP Ring on GCM with Optics Software Activation to activate the: standby module, then return to Step 4. active module, then return to Step 15. Perform a Manual Switch For modules in a protection group requiring a cold restart activation due to FPGA changes, a manual protection switch is necessary. Follow these step-by-step instructions to perform a manual protection switch to switch the active module (with the old software) from the active to the standby state. Note: This procedure is required for cold restart activation only. Table 7-16 Perform a Manual Switch Step Procedure 1 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 1 2 Select the protection group. Figure 7-25 Protection Groups Dialog Box 3 Click Edit to display the Protection Group Configuration dialog box. Page 7-36 Force10 Networks Release OPS4.2.2

357 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Perform a Manual Switch Table7-16 Perform a Manual Switch (continued) Step Procedure 4 Right-click the module or port with an Active Protection status in the Protection Group Configuration dialog box to display a shortcut menu. Select Manual from the shortcut menu. 4 Figure 7-26 Protection Group Manual Switch 5 The Confirm Manual Switch dialog box displays. Click Yes to confirm. Figure 7-27 Confirm Manual Switch Dialog Box 6 Check the Alarms dialog box to verify the EQFAIL: equipment failure alarm caused by the forced protection switch has cleared. 7 The active module or port is switched to standby. 8 The Perform a Manual Switch procedure is complete. If you were in the procedure: Control Module Software Upgrade Activation, then return to Step 14. Software Upgrade Activate (all other protected modules), then return to Step 12. Release OPS4.2.2 Force10 Networks Page 7-37

358 Operations and Maintenance Guide, Section 7: Software Upgrades Clear Protection Switch Clear Protection Switch Use the following step-by-step instructions to clear (release) a user-initiated protection switch. Table7-17 Clear Protection Switch Step Procedure 1 From Map View, double-click on a node to display the Shelf View. 2 In Shelf View, click the Protection tab to display the Protection Groups dialog box. 2 3 Select the protection group. Figure 7-28 Protection Groups Dialog Box 4 Click Edit to display the Protection Group Creation dialog box. 5 Right-click the Standby module/port in the Protection Group Creation dialog box to display a shortcut menu. Select Clear from the shortcut menu. 5 Figure 7-29 Protection Group Clear Protection Switch Page 7-38 Force10 Networks Release OPS4.2.2

359 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Clear Protection Switch Table 7-17 Clear Protection Switch (continued) Step Procedure 6 The Confirm Release dialog box displays. Click Yes to confirm the force switch release. Figure 7-30 Confirm Release Dialog Box 7 Check the Alarms dialog box to verify the EQFAIL: equipment failure alarm caused by the protection switch release has cleared. 8 The standby module or port is switched back to its original active status. 9 The Clear Protection Switch procedure is complete. If you were in the procedure: BLSR/MS-SP Ring on GCM with Optics Software Activation to activate the: standby module, then return to Step 14. active module, then return to Step 24. Software Upgrade Activate (all other protected modules), then return to Step 14. Release OPS4.2.2 Force10 Networks Page 7-39

360 Operations and Maintenance Guide, Section 7: Software Upgrades Software Revert Procedure Software Revert Procedure Use the following procedures to revert to a previous software version used on the node and TransNav management system. Revert Node Software, page 7-40 Revert TransNav Management System Software, page 7-41 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. Table7-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): begin exec upgrade switch-to-stdby-load slot <slot#> Are you sure you want to execute this command? YES. end exec node restart Are you sure you want to execute this command? YES. 3 Verify the node software level has been revised to the desired version and that the system is running the desired software load. 4 The Revert Node Software procedure is complete. Page 7-40 Force10 Networks Release OPS4.2.2

361 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Post-Remote Node Upgrade the Spare Control Module Software Revert TransNav Management System Software 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. Post-Remote Node Upgrade the Spare Control Module Software If you initially used the remote upgrade capability to upgrade the software version on your network nodes, the software on your spare modules likely needs to still be upgraded. The following procedure gives step-by-step instructions to perform this function. The new software is not active until the system reboots the spare (standby) control module (i.e., Traverse GCM or TE-100 System module). The reboot activates the backup partition with the newly downloaded software on the spare control module. Important: This procedure assumes you have completed upgrading (downloading and activating the new software for) the standby and active control modules. Important: A spare control module can only be upgraded in a shelf that has the same type of control module. For example, if the standby Traverse GCM is a GCM with OC-48 module, you can only upgrade GCM with OC-48 modules in this procedure. If the standby TE-100 System module is an OC-48 module, you can only upgrade with another OC-48 system module. The activation is set based on the date and time entered in the Activate Time field of the SW Activation dialog box. Use these step-by-step instructions to set up software Release OPS4.2.2 Force10 Networks Page 7-41

362 Operations and Maintenance Guide, Section 7: Software Upgrades Post-Remote Node Upgrade the Spare Control Module Software upgrade activation for spare control modules in the case where the other modules on the node have already been upgraded. Table 7-20 Post-Remote Node Upgrade the Spare Control Module Step Procedure 1 Remove the previously upgraded standby control module by first restarting the module through the TransNav management system using a cold reboot, then removing the module from the shelf. 2 Insert the spare (standby) control module. Important: Once the spare control module is online, the following alarms generate: EQRMV and EQCOMM. From this point, you have up to 30 minutes to complete the download and activation process. The versions and other data will be invalid until the upgrade is complete. 3 Download the desired software version to the spare control module using the procedure in Table 7-5 Card Software Download Set-up, page When the desired software is loaded onto the spare control module, activate the software using the steps described for the standby control module in the procedure described in Table 7-9 Activate Software Control Module, page You must change the value in the ActType field to SPARE. Note: After the upgrade, the EQRMV and EQCOMM alarms clear. 5 Repeat Steps 1 through 4 for each spare control module. 6 Once the upgrade and activation is complete for all the spare control modules you can either: Leave the last spare in place to act as the new standby module. Place the original standby control module back into the standby slot and continue the procedure. 7 The Post-Remote Node Upgrade the Spare Control Module procedure is complete. Page 7-42 Force10 Networks Release OPS4.2.2

363 Chapter 1 Release TR3.2.2 Traverse Software Upgrade User- selectable FPGA Upgrade Capability Userselectable FPGA Upgrade Capability In some cases, upgrading from one Traverse release to another requires a new FPGA image for a module or set of modules. Accepting this new FPGA image can resolve an issue that is unique to a certain deployment. The user-selectable FPGA upgrade capability (force warm reboot) gives you the choice to ignore the FPGA module software change because it is non-critical in nature to your deployment. This capability allows the upgrade to proceed in a hitless fashion without loading the new FPGA image. Important: If a decision has been made to use Ignore FPGA, Force10 recommends upgrading to the new FPGA image as soon as possible during a network maintenance window. From the SW Activation dialog box, if you select to ignore the new FPGA image and the existing FPGA image remains compatible with the new FPGA image, the system performs a force warm upgrade for the module. Important: The Ignore FPGA function is only available from Traverse software releases TR2.1.2.x and forward. Figure 7-31 User-selectable FPGA Upgrade Parameter Release OPS4.2.2 Force10 Networks Page 7-43

364 Operations and Maintenance Guide, Section 7: Software Upgrades Overview to Upgrade TE-206 Nodes from TransNav Overview to Upgrade TE-206 Nodes from TransNav TransNav Release TN4.2.1 introduces the ability to manage TraverseEdge 206 (TE-206) nodes from the TransNav GUI. The TransNav management system can be used to perform software downloads, upgrades, commits and fallbacks remotely to TE-206 nodes. With this release, the following directories have been added to the Force10 EMS 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 Page 7-44 Force10 Networks Release OPS4.2.2

365 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Overview to Upgrade TE-206 Nodes from TransNav 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. 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-32 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). Release OPS4.2.2 Force10 Networks Page 7-45

366 Operations and Maintenance Guide, Section 7: Software Upgrades Requirements for Upgrading TE-206 Node Software Requirements for Upgrading TE-206 Node Software Downloading 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 R software to be discovered by TransNav release TN4.2.1 or higher. (TE-206 nodes running Release R 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. 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 Requirements for Upgrading TE-206 Node Software. To fully upgrade the software on a node, see 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-33 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: Force10 recommends upgrading a maximum of five nodes at a time. Page 7-46 Force10 Networks Release OPS4.2.2

367 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Downloading TE-206 Node Software Table 7-21 Downloading 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-34 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-35 NE Software Download Dialog Box, Status 7 When the download completes, click Close. 8 The Downloading TE-206 Node Software procedure is complete. Release OPS4.2.2 Force10 Networks Page 7-47

368 Operations and Maintenance Guide, Section 7: Software Upgrades Upgrading 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-36 NE Software Dialog Box 3 Highlight the TE-206 node to be upgraded. Figure 7-37 Select TE-206 Node to Upgrade Page 7-48 Force10 Networks Release OPS4.2.2

369 Chapter 1 Release TR3.2.2 Traverse Software Upgrade Upgrading TE-206 Node Software from TransNav Table 7-22 Upgrading 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. Release OPS4.2.2 Force10 Networks Page 7-49

370 Operations and Maintenance Guide, Section 7: Software Upgrades Upgrading TE-206 Node Software from TransNav Page 7-50 Force10 Networks Release OPS4.2.2

371 SECTION 7SOFTWARE UPGRADES Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Introduction Release TE3.2.x Upgrade Overview 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-51 Before You Begin, page 7-52 Required Equipment and Tools, page 7-52 TransNav Management System GUI Commands and Conventions, page 7-53 Compatibility and Guidelines, page 7-53 Node Software Upgrade Process, page 7-54 Software Revert Procedure, page 7-69 Release TE3.2.x 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 3.0.x to Release TE3.2.x not an in-service upgrade In-service software upgrade TE3.2.x point releases (as necessary) for TE-100 nodes 1 TE-100 warm reboot and hitless upgrade features are unavailable Simultaneous TransNav management system node software management to accommodate longer-term upgrade paths: Release 2.0.x.y, TR2.1.x and TR3.0.x Traverse nodes Release TE3.2.x TE-100 nodes 1 TE-100 warm reboot and hitless upgrade features are planned for a future release. Release OPS4.2.2 Force10 Networks Page 7-51

372 Operations and Maintenance Guide, Section 7: Software Upgrades Before You Begin Before You Begin Review this information before you begin. Table 7-23 Node Software Upgrade Requirements Requirement Compose and have ready for the Upgrade Team a comprehensive network upgrade plan. Read through and understand the Release Notes, upgrade compatibility notes, guidelines, upgrade procedures, and your company s comprehensive upgrade plan. The software upgrade feature for this release supports TransNav 2.0 to 3.2.x upgrades. Have the required equipment and tools ready. Reference Your company s Operations Manager is responsible for this task. Refer to Release Notes 3.2.x Read through this entire chapter Contact your company s Operations Manager If you are upgrading from an earlier TransNav software release, contact the Force10 Technical Assistance Center (TAC). Required Equipment and Tools, page 7-52 Required Equipment and Tools 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 ( 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. TE-100 Shelf 1 or 2 System modules (and any spares) Page 7-52 Force10 Networks Release OPS4.2.2

373 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade General Software Compatibility TransNav Management System GUI Commands and Conventions This document provides node software upgrade procedures using the TransNav GUI. Refer to the TransNav Management System Product Overview Guide to become familiar with the TransNav system. The following conventions are used in the procedure tables. Table 7-24 TransNav GUI Command Descriptions Command Boldface Italics Description Boldface indicates dialog boxes, fields, menus, and list names. Italics indicate information that you supply. Compatibility and Guidelines General Software Compatibility Read the compatibility topics that are relevant to your specific upgrade. General Software Compatibility, page 7-53 TE-100 Platform SW Upgrade Compatibility Notes, page 7-54 Guidelines for Software Upgrade, page 7-54 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: ): 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. The Active control card with a (major.x.x.x) software version higher than the TransNav management system can support. In these cases, use the procedures in this section to upgrade or rollback the software version on the replacement card. Release OPS4.2.2 Force10 Networks Page 7-53

374 Operations and Maintenance Guide, Section 7: Software Upgrades TE-100 Platform SW Upgrade Compatibility Notes A SWMIS: Software version mismatch alarm is generated when a replacement card with either an earlier or later (major.minor.build.x) version of software than the software running on the control card is placed in the node. In this case, use the procedures in this section to upgrade or rollback the software version on the replacement card. TE-100 Platform SW Upgrade Compatibility Notes Guidelines for Software Upgrade Node Software Upgrade Process Review this information to understand the important compatibility items for the TE-100 and TransNav 4.2.x software release. TE-100 software upgrade from Release TE3.0.x.y to Release TE3.2.x. 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 3.2.x maintenance releases. TE-100 hitless upgrade and warm reboot features are unavailable in this release. 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 3.2.x define any potential exceptions. Complete the software upgrade procedures in the following order: Table 7-25 Node Software Upgrade Process Step Procedure Reference 1 Have you read through, and do you understand, all of the Before You Begin items? 2 Do you have the required equipment and tools ready? Before You Begin, page 7-52 Required Equipment and Tools, page 7-52 Page 7-54 Force10 Networks Release OPS4.2.2

375 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Download Node Software to the TransNav Server Table 7-25 Node Software Upgrade Process (continued) Step Procedure Reference 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. TransNav Management System Server Guide, Section 2 Management Server Procedures, Chapter 3 Server Administration Procedures, Upgrade Server Software, page 2-49 Download Node Software to the TransNav Server, page 7-55 Module Software Download Set-up, page Activate the new software. Software Activation Process, page The Node Software Upgrade Process is complete. Download Node Software to the TransNav Server Download Node Software to the TransNav Server You must first download the node software for the upgrade from the Infocenter onto a TransNav server before proceeding with the upgrade procedures. Choose one of the following download procedures, depending on the TransNav EMS platform (i.e., PC or Solaris) for your network. The Infocenter can be accessed at User registration is required. To register for the Force10 Infocenter, contact your sales account team. Download Node Software to the TransNav Server, page 7-55 Use these steps to download node software to the TransNav server. Table7-26 Download Node Software to the TransNav Server Step Procedure 1 Navigate to the directory where the software files were previously downloaded from the Infocenter. 2 In an Explorer window, navigate to the drive containing the temporary download directory. Figure 7-38 Example PC System Explorer Window File Listing Release OPS4.2.2 Force10 Networks Page 7-55

376 Operations and Maintenance Guide, Section 7: Software Upgrades Download Node Software to the TransNav Server Table7-26 Download Node Software to the TransNav Server Step Procedure 3 Right-click on the flash.n.n.n.n.zip file (where n.n.n.n is the latest software release number). For PC systems, select the Extract to command. For Solaris systems, use the gunzip command. Figure 7-39 Explorer Extract to Command 4 From the Extract dialog box, select a user-defined folder path directory (e.g., /upgrade/files), then click Extract to download the flash files into the /<user-defined>/flash directory. Important: Verify the Use folder names check box is selected to keep the./flash relative path structure in the zip file intact upon download. Figure 7-40 Extract Dialog Box 5 After the file extraction completes, the WinZip dialog box for the zip file archive remains open. Select File, then Exit to exit the dialog box. 6 The Download Node Software to the TransNav Server procedure is complete. Continue to Step 5 of the Node Software Upgrade Process, page 7-7. Page 7-56 Force10 Networks Release OPS4.2.2

377 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Module Software Download Set-up Module Software Download Set-up Software upgrades are done at the node level. The following procedure provides steps on how to begin a software upgrade by setting software download times for each card using the SW Upgrade dialog box. Table 7-27 Card Software Download Set-up Step Procedure 1 Verify the card software versions. Refer to Module Software Download Set-up, page In Shelf View, select SW Upgrade from the Admin menu to display the SW Upgrade dialog box. Figure 7-41 SW Upgrade Dialog Box 3 Server IP Address: Enter the TransNav server IP address where the new node software version was downloaded from the Infocenter. (For example: aaa.bbb.ccc.ddd) 4 Base Path: Enter the directory path on the TransNav server to the node software files. (For example: /files/node/flash) 5 Username: Enter the user name with File Transfer Protocol (FTP) permission access to the TransNav server where the new node software version resides. (For example: ftpusername) 6 Password: Enter the user password with FTP permission access to the TransNav server where the new node software version resides. (For example: ftppassword) 7 Click 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. Release OPS4.2.2 Force10 Networks Page 7-57

378 Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Table7-27 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, 7 Figure 7-42 Download Time Settings Page 7-58 Force10 Networks Release OPS4.2.2

379 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Module Software Download Set-up Table 7-27 Card Software Download Set-up (continued) Step Procedure 9 From the Download Time drop-down box, select Set time to manually adjust the time. Select part of the time string (e.g., month, day, hour). Use the up and down arrows or manually re-enter the time to reset the value. 8 Figure 7-43 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. Release OPS4.2.2 Force10 Networks Page 7-59

380 Operations and Maintenance Guide, Section 7: Software Upgrades Module Software Download Set-up Table7-27 Card Software Download Set-up (continued) Step Procedure 13 You can Clear Download Time for any card by right-clicking the card in the SW Upgrade dialog box and clicking the Update button. If necessary, you can Abort Download to any card by right-clicking the card in the SW Upgrade dialog box. Note: 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. 12 Figure 7-44 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. Page 7-60 Force10 Networks Release OPS4.2.2

381 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Module Software Download Set-up Table 7-27 Card Software Download Set-up (continued) Step Procedure 16 Continue only when the Download Status is OK and the newly downloaded software version displays in Standby SW Version field for all cards (select each card row and check the Standby SW Version field). This indicates the software download has successfully completed. 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-2 Step 3 of the Spare Module Software Activation (All Other Types), page 7-33 Release OPS4.2.2 Force10 Networks Page 7-61

382 Operations and Maintenance Guide, Section 7: Software Upgrades Card Software Version Verification 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. Table 7-28 Card Software Version Number Verification Step Procedure 1 In Shelf View, click a card to select it. 2 Click the Config tab to view current software version information. 2 Figure 7-45 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: ): 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. Software Activation Process The new software is not active until the system reboots each module. The reboot activates the backup partition with the newly downloaded software. Important: Read all important notes below before beginning the activation process. Important: Software activation should start at the node farthest from the server that is connected to the head end node, then working inward. Page 7-62 Force10 Networks Release OPS4.2.2

383 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Software Activation Process Important: During software activation, the modules automatically reboot. Do not execute any external commands on the modules during software activation. Table 7-29 Software Activation Process Step Procedure Reference 1 Did you complete the upgrade of TransNav EMS server and client software, and download the node software to the TransNav server? 2 Did you download the node software to the TransNav server? 3 Is the module software download complete? 4 Activate software for: Standby control module Spare (standby) control module(s), 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.2 Traverse Software Upgrade, Post-Remote Node Upgrade the Spare Control Module Software, page 7-41). Active control module Section 2 Management Server Procedures, Chapter 1 Server Administration Procedures, Upgrade Server Software, page 2-12 Download Node Software to the TransNav Server, page 7-55 Module Software Download Set-up, page 7-57 Activate Software - Control Module, page The Software Activation Process is complete. Continue to Step 7 of the Node Software Upgrade Process, page Release OPS4.2.2 Force10 Networks Page 7-63

384 Operations and Maintenance Guide, Section 7: Software Upgrades Activate 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. Important: Do not start the Activate Software Control Module procedure until the downloaded software version displays in the SW Upgrade dialog box, Standby SW Ver field for all modules, indicating the software download has successfully completed. The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for control modules. Table 7-30 Activate Software Control Module Step Procedure 1 Verify the network is alarm free or validate and record any alarms present prior to activation. 2 In Shelf View, select a control module and click the Config tab. 3 Verify the Protection Status of the Active/Standby control module using the Card Configuration dialog box. 3 Figure 7-46 Card Configuration Protection Status Page 7-64 Force10 Networks Release OPS4.2.2

385 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Activate Software - Control Module Table 7-30 Activate Software Control Module (continued) Step Procedure 4 Click the standby control module Activate Time field in the SW Upgrade dialog box; the current date and time displays. Use the Activate Time up and down arrows to reset the date and time or select the date, time, hour, or minute fields and then re-enter. 4 Figure 7-47 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 Force10 Technical Assistance Center if the software activation fails a second time. 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 Force10 Technical Assistance Center. Release OPS4.2.2 Force10 Networks Page 7-65

386 Operations and Maintenance Guide, Section 7: Software Upgrades Activate Software - Control Module Table 7-30 Activate Software Control Module (continued) Step Procedure 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-68 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 Force10 the Technical Assistance Center if the software activation fails a second time. Page 7-66 Force10 Networks Release OPS4.2.2

387 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Activate Software - Control Module Table 7-30 Activate Software Control Module (continued) Step Procedure 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 Release OPS4.2.2 Force10 Networks Page 7-67

388 Operations and Maintenance Guide, Section 7: Software Upgrades Spare Control Module Software Activation Spare Control Module Software Activation The new software is not active until the system reboots the spare (standby) control module. The reboot activates the backup partition with the newly downloaded software on the spare control module. Important: This procedure assumes you have completed upgrading the standby control module and have not yet activated the active control module. Important: A spare control module can only be upgraded in a shelf that has the same type of control module. For example, if the standby Traverse GCM is a GCM with OC-48 module, you can only upgrade GCM with OC-48 modules in this procedure. Likewise, The activation is scheduled for each module based on the date and time entered in the Activate Time field of the SW Upgrade dialog box. Follow these step-by-step instructions to set up software upgrade activation for spare control modules. Table 7-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-57 procedure. 4 Once the new software downloads to the spare control module, activate the software using the steps described for the standby control module in the Table 7-30 Activate Software Control Module, page 7-64 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 Page 7-68 Force10 Networks Release OPS4.2.2

389 Chapter 2 Release TE3.2.x TE-100 System Software Upgrade Software Revert Procedure Software Revert Procedure Use the following procedures to revert to a previous software version used on the node and TransNav management system. Revert Node Software, page 7-69 Revert TransNav Management System Software, page 7-70 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. Table7-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): begin exec upgrade switch-to-stdby-load slot <slot#> Are you sure you want to execute this command? YES. end exec node restart Are you sure you want to execute this command? YES. 3 Verify the node software level has been revised to the desired version and that the system is running the desired software load. 4 The Revert Node Software procedure is complete. Release OPS4.2.2 Force10 Networks Page 7-69

390 Operations and Maintenance Guide, Section 7: Software Upgrades Software 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. Page 7-70 Force10 Networks Release OPS4.2.2

391 SECTION 8 HARDWARE UPGRADES SECTION 8 Contents Chapter 1 Replacing Existing Traverse Hardware Modules Fan Equipment Software Compatibility Software Version Verification Electrostatic Discharge Protection Required Equipment and Tools General Traverse Shelf Replacement Module Type and Software Version Preparing a Module for Removal and Replacement Remove a Module Module Placement GCM Module Replacement as Standby LED Indicators Clean Fiber Optic MPX Connectors Insert a Replacement Module Replace the Front Inlet Fan Tray Module Front Inlet Fan Tray Air Filter Replacement Replace the Traverse 600 Fan Assembly Fan Assembly Air Filter Installation (Traverse 600) Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray Precautions and Assumptions Required Equipment and Tools FIFT Upgrade Instructions Check the New Fan Module Release OPS4.2.2 Force10 Networks Page i

392 Operations and Maintenance Guide, Section 8 Hardware Upgrades Page ii Force10 Networks Release OPS4.2.2

393 SECTION 8HARDWARE UPGRADES Chapter 1 Replacing Existing Traverse Hardware Introduction During the course of normal operation, various conditions may arise that require network operations personnel to replace existing system equipment. This section describes Traverse module and fan equipment replacement. Modules All modules in the Traverse system, including the General Control Modules (GCMs), are hot-swappable and can be removed and replaced while the system is in operation. During replacement procedures, service is interrupted to all connections on the removed modules. For related information about adding and removing modules using the TransNav GUI, see the TransNav Management System GUI Guide, Section 3 Network, Chapter 1 Creating and Deleting Equipment Using Preprovisioning. The module replacement topics in this chapter are as follows: Software Compatibility, page 8-2 Software Version Verification, page 8-3 Electrostatic Discharge Protection, page 8-4 Required Equipment and Tools, page 8-4 Replacement Module Type and Software Version, page 8-4 Preparing a Module for Removal and Replacement, page 8-6 Remove a Module, page 8-8 Module Placement, page 8-9 GCM Module Replacement as Standby LED Indicators, page 8-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, page Release OPS4.2.2 Force10 Networks Page 8-1

394 Operations and Maintenance Guide, Section 8: Hardware Upgrades Software Compatibility The fan equipment replacement topics are as follows: Section 8 Hardware Upgrades, Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray, page 8-31 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-27 Fan Assembly Air Filter Installation (Traverse 600), page 8-29 Software Compatibility Control Cards. Each control card is partitioned and capable of holding two versions of software. The new software is downloaded onto the card s backup partition during a software upgrade. 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: ): 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. The Active control card with a (major.x.x.x) software version higher than the TransNav management system can support. In these cases, use the procedures in this section to upgrade or rollback the software version on the replacement card. A SWMIS: Software version mismatch alarm is generated when a replacement card with either an earlier or later (major.minor.build.x) version of software than the software running on the control card is placed in the node. In this case, use the procedures in this section to upgrade or rollback the software version on the replacement card. Refer to Section 7 Software Upgrades, Chapter 1 Release TR3.2.2 Traverse Software Upgrade for software upgrade procedures. Page 8-2 Force10 Networks Release OPS4.2.2

395 Chapter 1 Replacing Existing Traverse Hardware Software Version Verification 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. Table 8-1 Card Software Version Number Verification Step Procedure 1 In Shelf View, click a card to select it. 2 Click the Config tab to view current software version information. 2 Figure 8-1 Card Configuration Dialog Box 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: ): 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. Release OPS4.2.2 Force10 Networks Page 8-3

396 Operations and Maintenance Guide, Section 8: Hardware Upgrades Electrostatic Discharge Protection Electrostatic Discharge Protection Required Equipment and Tools 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 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.2 Traverse Software Upgrade for procedures on how to convert software versions on a replacement module. Page 8-4 Force10 Networks Release OPS4.2.2

397 Chapter 1 Replacing Existing Traverse Hardware Replacement Module Type and Software Version Module of Different Type. If you replace a module with a different type of module, an Equipment Mismatch alarm is generated 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 Release OPS4.2.2 Force10 Networks Page 8-5

398 Operations and Maintenance Guide, Section 8: Hardware Upgrades Preparing a Module for Removal and Replacement Preparing a Module for Removal and Replacement The following procedures provide step-by-step instructions on how to prepare a module for removal and replacement using the TransNav GUI. Important: GCM, Enhanced GCM (EGCM), Universal GCM (UGCM), and GCMs with integrated optics are considered different modules and must be physically removed and deleted via TransNav prior to replacement with a different GCM module type to avoid an EQMIS: Equipment Mismatch alarm. Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older GCM modules with the newer GCM modules in a redundant configuration. The following replacement rules apply: Replace: GCM with a UGCM EGCM (without optics) with a UGCM EGCM (with OC-12/STM-4) with a UGCM with 1-port OC-12/STM-4 EGCM (with OC-48/STM-16) with a UGCM with OC-48/STM-16 Important: The Traverse system allows the network operator an in-service upgrade capability (protection switching) to replace older DS3, E3, EC-1, and DS3 Transmux modules with the newer DS3, E3, EC-1, and DS3 Transmux modules with no greater than 50 ms traffic interruption for each module in any 1:N (where N=1,2) protection group. Table 8-2 Preparing a Module for Removal and Replacement Step Procedure 1 In the TransNav GUI, go to Shelf View. 2 Click the module to be removed. 3 Click the Config tab to display the Card Configuration dialog box. 4 Click the Lock icon at the bottom left portion of the screen to change 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. Page 8-6 Force10 Networks Release OPS4.2.2

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

400 Operations and Maintenance Guide, Section 8: Hardware Upgrades Remove 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. Locking Tabs in Open Position OPS 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. Page 8-8 Force10 Networks Release OPS4.2.2

401 Chapter 1 Replacing Existing Traverse Hardware Module Placement Module Placement The following restrictions apply for module placement in a Traverse shelf. Refer to Appendix A Module Placement Planning and Guidelines, page 9-1 for additional information. Table 8-4 Card Placement Guidelines Card Type Traverse 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) 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 Release OPS4.2.2 Force10 Networks Page 8-9

402 Operations and Maintenance Guide, Section 8: Hardware Upgrades Module Placement Table 8-4 Card Placement Guidelines (continued) Card Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) DS3/EC-1 Transmux 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 This application has no DS3/E3 ECM requirement. One card protects all remaining adjacent cards. UTMX-24 or UTMX 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 This application has no DS3/E3 ECM requirement. One card protects all remaining adjacent cards. Page 8-10 Force10 Networks Release OPS4.2.2

403 Chapter 1 Replacing Existing Traverse Hardware Module Placement Table 8-4 Card Placement Guidelines (continued) Card Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) 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 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 faceplate is not required if the 10/100BaseTX-inclusive cards are placed to the left of electrical interface cards. or Place an OC-N/STM-N card or a 1-slot wide blank faceplate between the 10/100BaseTX and an electrical interface card if the 10/100BaseTX-inclusive card is placed to the right of the electrical interface card. Ethernet (Dual Slot GbE) 10GBASE-LR n/a None 10-port 1GbE card, no optics 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. Ethernet over PDH (EoPDH) Release OPS4.2.2 Force10 Networks Page 8-11

404 Operations and Maintenance Guide, Section 8: Hardware Upgrades Module Placement Table 8-4 Card Placement Guidelines (continued) Card Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) GbE [LX, SX] plus 10/100BaseTX Combo [CEP/EoPDH] GbE TX plus GbE [LX or SX] plus 10/100BaseTX Combo [CEP/EoPDH] 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 faceplate is not required if the 10/100BaseTX-inclusive cards are placed to the left of electrical interface cards. or Place an OC-N/STM-N card or a 1-slot wide blank faceplate between the 10/100BaseTX and an electrical interface card if the 10/100BaseTX-inclusive card is placed to the right of the electrical interface card. SONET/SDH OC-3/STM-1 OC-12/STM-4 OC-48/STM 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. Page 8-12 Force10 Networks Release OPS4.2.2

405 Chapter 1 Replacing Existing Traverse Hardware Module Placement Table 8-4 Card Placement Guidelines (continued) Card Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) VT/TU Switching VT/TU 5G Switch 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. 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 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. 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. Release OPS4.2.2 Force10 Networks Page 8-13

406 Operations and Maintenance Guide, Section 8: Hardware Upgrades GCM Module Replacement as Standby LED Indicators The following table lists the redundancy rules for all GCM types: Table 8-5 Redundancy Rules for GCM Types Active GCM Standby GCM GCM GCM GCM GCM Enhanced Universal 1 GCM Enhanced Universal 1 GCM Enhanced Universal GCM with OC-N/STM-N GCM GCM Enhanced Universal GCM with OC-N/STM-N 1 GCM Enhanced or Universal environmental alarm function should not be used in this combination. GCM Module Replacement as Standby LED Indicators When a new GCM module is placed as the standby module, the Power and Active/Standby LED indications are as shown in the following table. The LEDs in the following tables apply to all cards. Table 8-6 Power and Active/Standby All Cards LED RED Amber GREEN OFF Flashing Solid Flashing Solid Flashing Solid Power Initialization and diagnosis is underway but not complete. Hardware failure detected; replace the 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. Page 8-14 Force10 Networks Release OPS4.2.2

407 Chapter 1 Replacing Existing Traverse Hardware Clean Fiber Optic MPX Connectors Clean Fiber Optic MPX Connectors It is critical that the cable and card MPX connectors are clean to ensure proper operation. 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. Release OPS4.2.2 Force10 Networks Page 8-15

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

409 Chapter 1 Replacing Existing Traverse Hardware Clean Fiber Optic MPX Connectors Table 8-7 Clean Cable and Card MPX Connectors (continued) Step Procedure 5 Align the white reference marker on the MPX connector with the white stripe on the left side of the Traverse 600 fiber optic backplane housing. White Stripe Reference Markers Housing A Housing B OPS Figure 8-5 Traverse 600 Fiber Optic Backplane Housing A and B 6 Gently push the MPX connector back into the correct fiber optic backplane housing. 7 Repeat Steps 2 through 6 for each MPX connector. 8 Remove the dust cap from the optical card MPX connector(s). Dust Cap on MPX Connector OPS Figure 8-6 Optical Card MPX Connector Release OPS4.2.2 Force10 Networks Page 8-17

410 Operations and Maintenance Guide, Section 8: Hardware Upgrades Clean Fiber Optic MPX Connectors Table 8-7 Clean Cable and Card MPX Connectors (continued) Step Procedure 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. Page 8-18 Force10 Networks Release OPS4.2.2

411 Chapter 1 Replacing Existing Traverse Hardware Insert a Replacement Module Insert a Replacement Module Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when handling Traverse cards (cards). Plug the ESD wrist strap into the ESD jack provided on the Traverse front inlet fan card, standalone air ramp, or other confirmed source of earth ground. Refer to ESD Jack Locations, page 6-7. Important: Do not install Traverse cards until all installation and cabling procedures are complete. Important: Handle cards by the edges and faceplate only. Do not touch any card connectors or components. Important: Observe all electrostatic sensitive device warnings and precautions when handling Traverse cards. Important: Insert the card into the Traverse shelf using the guides at the top and bottom of the card cage for proper alignment. Make sure the card is vertical, from top to bottom, and that the card stays in the guides from the front to the back of the shelf. Important: Do not place an electrical card (of another type) in the slot directly to the left of any 10/100BaseTX-inclusive card: NGE NGE Plus EoPDH Legacy Ethernet Important: Cards should insert easily into the Traverse shelf. Do not force the card into position. If the card does not insert easily, slide it back out, verify you are placing it in the correct position and inserting the card into the correct guides top and bottom. Release OPS4.2.2 Force10 Networks Page 8-19

412 Operations and Maintenance Guide, Section 8: Hardware Upgrades Insert a Replacement Module 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. Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty Traverse slots. Follow these steps to insert a card. Table 8-8 Insert a Card Step Procedure 1 Is this an optical card with MPX connectors? If yes, complete the Clean MPX Connectors procedure before proceeding. If no, continue to Step 2. 2 Flip the card locking tabs up. Hold the card with the tabs parallel to the top and bottom of the card. Guide Pins Locking Tabs in Open Position OPS Figure 8-7 Card Locking Tabs in the Unlocked Position Page 8-20 Force10 Networks Release OPS4.2.2

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

414 Operations and Maintenance Guide, Section 8: Hardware Upgrades Insert a Replacement Module Table 8-8 Insert a Card (continued) Step Procedure 4 Push the center of the card faceplate until the locking tabs begin to close and the locking tabs start to roll around the lip of the Traverse shelf. The optical card makes an audible click indicating it is making contact with the fiber optic backplane connectors. 5 Push the locking tabs down. The tabs must close around each end of the card to lock the card in place. Locking Tabs in Closed Position Figure 8-10 Card Tabs in the Locked Position 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. Page 8-22 Force10 Networks Release OPS4.2.2

415 Chapter 1 Replacing Existing Traverse Hardware Replace 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. 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. 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. 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. Captive Thumb Screws OPS 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. Release OPS4.2.2 Force10 Networks Page 8-23

416 Operations and Maintenance Guide, Section 8: Hardware Upgrades Replace the Front Inlet Fan Tray Module Table 8-9 Replace a Traverse 1600 and Traverse 2000 Fan Assembly (continued) Step Procedure 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. Fan Module Connectors Fan Tray Holder Guide Captive Thumb Screws 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. Page 8-24 Force10 Networks Release OPS4.2.2

417 Chapter 1 Replacing Existing Traverse Hardware Replace the Front Inlet Fan Tray Module Table 8-9 Replace a Traverse 1600 and Traverse 2000 Fan Assembly (continued) Step Procedure 5 Align and tighten the captive thumb screws to secure the fan module front cover. Captive Thumb Screws Figure 8-13 Front Inlet Fan Module Captive Thumb Screws OPS Continue to the next procedure, Insert a Traverse 1600 and Traverse 2000 Fan Air Filter. Release OPS4.2.2 Force10 Networks Page 8-25

418 Operations and Maintenance Guide, Section 8: Hardware Upgrades Front 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. The front inlet fan tray air filters are available in 63% or 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. The following procedure provides step-by-step instructions on how to insert the front inlet fan tray air filter. Table 8-10 Insert a Traverse 1600 and Traverse 2000 Fan Air Filter Step 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 Install the new air filter. Grasp the air filter flexible pull tab. OPS Pull Tab (top view) Figure 8-14 Front Inlet Air Filter 3 Insert the air filter in the gap between the top of the front inlet fan card and the top of the front inlet fan tray holder. Slide the air filter along the fan tray holder guides until the filter is flush with the front of the fan tray holder. 4 The Insert a Traverse 1600 and Traverse 2000 Fan Air Filter procedure is complete. Page 8-26 Force10 Networks Release OPS4.2.2

419 Chapter 1 Replacing Existing Traverse Hardware Replace the Traverse 600 Fan Assembly Replace the Traverse 600 Fan Assembly The Traverse 600 fan module with integral fan tray is bundled and shipped with the Traverse 600 system. Proceed with the following steps to install the fan assembly. Important: Wear a properly grounded Electrostatic Discharge (ESD) wrist strap when installing the fan tray module as it contains static-sensitive components. Table 8-11 Insert a Traverse 600 Fan Assembly Step Procedure 1 Loosen the two captive screws on the right-front cover of the Traverse 600 fan assembly to release it. OPS Captive Fasteners Figure 8-15 Fan Assembly Front Cover - Traverse Open the right-front fan assembly cover. Release OPS4.2.2 Force10 Networks Page 8-27

420 Operations and Maintenance Guide, Section 8: Hardware Upgrades Replace the Traverse 600 Fan Assembly Table 8-11 Insert a Traverse 600 Fan Assembly (continued) Step Procedure 3 Hold the fan assembly vertically with the fan card facing left and lift it level with the fan cage. Slide the fan assembly into the fan cage along the guides and push it straight in until it connects to the back of the shelf. Important: Do not force the fan tray card into position. If it does not plug in easily, slide it back out. Check for any obstructions or a damaged connector that might prevent it from sliding into position and verify it is lined up in the correct guides. Traverse 600 Shelf Fan Assembly OPS Figure 8-16 Traverse 600 Fan Assembly Installation 4 The Fan Assembly Air Filter Installation (Traverse 600)Insert a Traverse 600 Fan Assembly procedure is complete. Page 8-28 Force10 Networks Release OPS4.2.2

421 Chapter 1 Replacing Existing Traverse Hardware Fan Assembly Air Filter Installation (Traverse 600) Fan Assembly Air Filter Installation (Traverse 600) The Traverse 600 fan assembly (fan module with integral fan tray) requires a foam air filter that is placed to the left of the fan assembly after the fan module is installed. 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. OPS Captive Fasteners Figure 8-17 Fan Assembly Front Cover - Traverse Open the right-front fan assembly cover. Release OPS4.2.2 Force10 Networks Page 8-29

422 Operations and Maintenance Guide, Section 8: Hardware Upgrades Fan Assembly Air Filter Installation (Traverse 600) Table 8-12 Insert a Traverse 600 Fan Assembly (continued) Step Procedure 3 Hold the fan assembly vertically with the fan card facing left and lift it level with the fan cage. Slide the fan assembly into the fan cage along the guides and push it straight in until it connects to the back of the shelf. Important: Do not force the fan tray card into position. If it does not plug in easily, slide it back out. Check for any obstructions or a damaged connector that might prevent it from sliding into position and verify it is lined up in the correct guides. Traverse 600 Shelf Fan Assembly OPS Figure 8-18 Traverse 600 Fan Assembly Installation 4 The Fan Assembly Air Filter Installation (Traverse 600)Insert a Traverse 600 Fan Assembly procedure is complete. Page 8-30 Force10 Networks Release OPS4.2.2

423 SECTION 8 SECTION 8HARDWARE UPGRADES Chapter 2 Upgrade to a Traverse Front Inlet Fan Tray Introduction Precautions and Assumptions This chapter provides upgrade instructions for replacing separate Traverse fan tray and air ramp assemblies with a single front inlet fan tray (FIFT) assembly: Precautions and Assumptions, page 8-31 Required Equipment and Tools, page 8-32 FIFT Upgrade Instructions, page 8-32 The following precautions and assumptions apply: WARNING! Plan this upgrade to avoid disruptions and keep the time to a minimum. This replacement operation should take no more than 4 to 5 minutes. A fully loaded Traverse shelf can sustain a non-service affecting temperature increase for approximately 6 minutes before it begins generating critical alarms. Depending on the number of modules in the shelf and the room temperature, 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: These upgrade instructions apply to nodes on software Release 1.4 or higher. Important: The existing separate fan tray holder and air ramp use 4 inches of height. This is the required minimum replacement space to allow easy insertion of the new FIFT. Release OPS4.2.2 Force10 Networks Page 8-31

424 Operations and Maintenance Guide, Section 8: Hardware Upgrades Required Equipment and Tools Required Equipment and Tools The following equipment and tools are required for this upgrade: Front inlet fan tray holder Front inlet fan module Air filter 1 Large straight slot screwdriver or 5/16-inch hex socket Two technicians (to decrease the replacement time, have one in front and one in back of the rack) Stepladder (optional) Electrostatic Discharge (ESD) wrist strap FIFT Upgrade Instructions Follow these FIFT upgrade instructions: Table 8-13 Front Inlet Fan Tray Holder Upgrade Instructions Step Instructions 1 Check the New Fan Module, page 8-33 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 The Front Inlet Fan Tray Holder Upgrade Instructions are complete. 1 Front inlet fan tray air filters are available in 63% arrestance at 300 FPM feet per minute (91.4 meters per minute) and 80% arrestance at 300 FPM feet per minute (91.4 meters per minute) depending on your installation requirements. Page 8-32 Force10 Networks Release OPS4.2.2

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

426 Operations and Maintenance Guide, Section 8: Hardware Upgrades Check the New Fan Module Page 8-34 Force10 Networks Release OPS4.2.2

427 SECTION 9 APPENDICES SECTION 9 Contents Appendix A Module Placement Planning and Guidelines Module Placement Guidelines Traverse 1600 Module Placement Traverse 2000 Card Placement Traverse 600 Card Placement Appendix B Traverse SNMP v1/v2c Agent and MIBs Supported Traverse SNMP MIBs Configure the Traverse SNMP Agent Parameters from TransNav Location of SNMP MIB File Release OPS4.2.2 Force10 Networks Page i

428 Operations and Maintenance Guide, Section 9 Appendices Page ii Force10 Networks Release OPS4.2.2

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

430 Operations and Maintenance Guide, Section 9: Appendices Module 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 Type Traverse 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 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) 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 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 This application has no DS3/E3 ECM requirement. One card protects all remaining adjacent cards. Page 9-2 Force10 Networks Release OPS4.2.2

431 Appendix A Module Placement Planning and Guidelines Module Placement Guidelines Table 9-1 Card Placement Guidelines (continued) Card Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) UTMX-24 or UTMX 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 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 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 faceplate is not required if the 10/100BaseTX-inclusive cards are placed to the left of electrical interface cards. or Place an OC-N/STM-N card or a 1-slot wide blank faceplate between the 10/100BaseTX and an electrical interface card if the 10/100BaseTX-inclusive card is placed to the right of the electrical interface card. Ethernet (Dual Slot GbE) Release OPS4.2.2 Force10 Networks Page 9-3

432 Operations and Maintenance Guide, Section 9: Appendices Module Placement Guidelines Table 9-1 Card Placement Guidelines (continued) Card Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) 10GBASE-LR n/a None 10-port 1GbE card, no optics 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. 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] 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 faceplate is not required if the 10/100BaseTX-inclusive cards are placed to the left of electrical interface cards. or Place an OC-N/STM-N card or a 1-slot wide blank faceplate between the 10/100BaseTX and an electrical interface card if the 10/100BaseTX-inclusive card is placed to the right of the electrical interface card. SONET/SDH OC-3/STM-1 OC-12/STM-4 OC-48/STM None Page 9-4 Force10 Networks Release OPS4.2.2

433 Appendix A Module Placement Planning and Guidelines Module Placement Guidelines Table 9-1 Card Placement Guidelines (continued) Card Type Traverse 1600 Slot #s Traverse 2000 Slot #s Traverse 600 Slot #s Comments (Front-shelf Perspective) OC-192/STM-64 1/2, 3/4, 5/6, 7/8, 9/10, 11/12, and 13/14 1/2, 3/4, 5/6, 7/8, 9/10, 11/12, 13/14, 15/16, and 17/18 n/a The OC-192/STM-64 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 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. 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 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. 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. Release OPS4.2.2 Force10 Networks Page 9-5

434 Operations and Maintenance Guide, Section 9: Appendices Module Placement Guidelines 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 Universal 1 GCM Enhanced Universal 1 GCM Enhanced Universal GCM with OC-N/STM-N GCM GCM Enhanced Universal GCM with OC-N/STM-N 1 GCM Enhanced or Universal environmental alarm function should not be used in this combination. Page 9-6 Force10 Networks Release OPS4.2.2

435 Appendix A Module Placement Planning and Guidelines Traverse 1600 Module Placement Traverse 1600 Module Placement The following table provides card placement guidelines for the Traverse 1600 shelf. Legend: Gray Fill=valid slot for card, No Fill=invalid card slot, Standby or Active (S/A), Protecting (P), Working (W), Open (O). Important: For standard electrical connector card (ECM) placement, the 2-slot ECMs plug into slot n of an n and n+1 slot combination. The 3-slot ECMs plug into slot n+1 of an n, n+1, and n+2 slot combination. For example, in a Traverse 1600 slot 11 and 12 combination, the 2-slot ECM plugs into the slot 11 backplane connectors. Some ECMs require specific placement, see the Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications, Chapter 2 ECM Interface Specifications, page 2-15 for ECM slot placement details. Important: For standard 10-port GbE card SFP connector card (SCM) placement, the 2-slot SCMs plug into slot n+1 of an n and n+1 slot combination. For example, in a Traverse 1600 slot 11 and 12 combination, the 2-slot SCM plugs into the slot 12 backplane connectors. Table 9-3 Traverse 1600 Card Placement Guidelines Card Type Traverse 1600 Slot Numbers GCM GCM Enhanced GCM 1 GCM OC-12/STM-4 1 GCM OC-48/STM-16 1 OPTICAL (Note: Optical cards are protected at the port level. There are no slot or card placement restrictions for optical working/protection.) OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 W W W W 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 Sl ETHERNET (Dual slot) 1-port 10GbE Slots 1/2 P Slots 3/4 W/P Slots 5/6 W/P Slots 7/8 W/P Slots 9/10 W/P Sl 10-port GbE P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P ETHERNET (Single slot) 1:1 equipment protection with a 2-slot Ethernet Protection ECM (Note: The Ethernet Combo cards have both optical ports and electrical ports. The card placement restriction is due to the electrical ports.) Release OPS4.2.2 Force10 Networks Page 9-7

436 Page 9-8 Force10 Networks Release OPS4.2.2 Table 9-3 Traverse 1600 Card Placement Guidelines (continued) Card Type 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 ETHERNET (Single slot) unprotected with a 2-slot 10/100BaseT ECM 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 Traverse 1600 Slot Numbers P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W W W W W W W W W W W W W Operations and Maintenance Guide, Section 9: Appendices Traverse 1600 Module Placement

437 Release OPS4.2.2 Force10 Networks Page 9-9 Table 9-3 Traverse 1600 Card Placement Guidelines (continued) Card Type ETHERNET (Single slot) unprotected with a 2-slot Ethernet (Protection) ECM 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 TDM 1:2 equipment protection with the corresponding ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 2-slot ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 3-slot ECM DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM unprotected with the corresponding ECM Traverse 1600 Slot Numbers O W/O W/O W/O W/O W/O W/O W/O W/O W/O W/O W W W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O W/P/O Appendix A Module Placement Planning and Guidelines Traverse 1600 Module Placement

438 Page 9-10 Force10 Networks Release OPS4.2.2 Table 9-3 Traverse 1600 Card Placement Guidelines (continued) DS1 E1 Card Type 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 TDM unprotected with a 3-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.) DS3/E3/EC-1 CC DS3/EC-1 Transmux O W/O W/O W/O W/O W/O W/O W/O W/O W/O W 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 VTX 2 W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P W/P VT/VC Switching unprotected Traverse 1600 Slot Numbers VT/TU 5G Switch W W W W W W W W W W W W W W GCM with optics plus VTX 2 W W W W W W W W W W W W W W 1 Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with 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. 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. Operations and Maintenance Guide, Section 9: Appendices Traverse 1600 Module Placement

439 Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling. Appendix A Module Placement Planning and Guidelines Traverse 1600 Module Placement Release OPS4.2.2 Force10 Networks Page 9-11

440 Page 9-12 Force10 Networks Release OPS4.2.2 Traverse 2000 Card Placement The following table provides card placement guidelines for the Traverse 2000 shelf. Legend: Gray Fill=valid slot for card, No Fill=invalid card slot, Standby or Active (S/A), Protecting (P), Working (W), Open (O). Important: For standard electrical connector card (ECM) placement, the 2-slot ECMs plug into slot n of an n and n+1 slot combination. The 3-slot ECMs plug into slot n+1 of an n, n+1, and n+2 slot combination. For example, in a Traverse 1600 slot 11 and 12 combination, the 2-slot ECM plugs into the slot 11 backplane connectors. Some ECMs require specific placement, see the Traverse Installation and Commissioning Guide, Section 2 Network Interface Specifications, Chapter 2 ECM Interface Specifications, page 2-15 for ECM slot placement details. Important: For standard 10-port GbE card SFP connector card (SCM) placement, the 2-slot SCMs plug into slot n+1 of an n and n+1 slot combination. For example, in a Traverse 1600 slot 11 and 12 combination, the 2-slot SCM plugs into the slot 12 backplane connectors. Table 9-4 Traverse 2000 Card Placement Guidelines Card Type Traverse 2000 Slot Numbers GCM S/A S/A GCM Enhanced GCM 1 GCM OC-12/STM-4 1 GCM OC-48/STM-16 1 OPTICAL (Note: Optical cards are protected at the port level. There are no slot or card placement restrictions for optical working/protection.) OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 W W W W 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/2 P Slots 3/4 W/P Slots 5/6 W/P Slots 7/8 W/P Slots 9/10 W/P Slots 11/12 W/P Slots 13/14 W/P Slots 15/16 W/P Slots 17/18 W Operations and Maintenance Guide, Section 9: Appendices Traverse 2000 Card Placement

441 Release OPS4.2.2 Force10 Networks Page 9-13 Table 9-4 Traverse 2000 Card Placement Guidelines (continued) Card Type 10-port GbE P W/ P ETHERNET unprotected with a 2-slot 10/100BaseT ECM 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 ETHERNET unprotected with a 2-slot Ethernet (Protection) ECM 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 W/ P W/ P W/ P W/ P W/ P W/ P W/ P W/ P W/ P W W/ P W W W W W W W W W W W W W W W W O W/ O TDM 1:2 equipment protection with corresponding ECM W/ O W/ O W/ O W/ O W/ O W/ O Traverse 2000 Slot Numbers W/ O W/ O W/ O W/ O W/ O W/ P W/ O W/ P W/ O W W Appendix A Module Placement Planning and Guidelines Traverse 2000 Card Placement

442 Page 9-14 Force10 Networks Release OPS4.2.2 Table 9-4 Traverse 2000 Card Placement Guidelines (continued) DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 W W/ P TDM 1:1 equipment protection with a 2-slot ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 W/ P W/ P TDM 1:1 equipment protection with a 3-slot ECM DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 W/ P/O W/ P/O TDM unprotected with the corresponding ECM DS1 E1 Card Type W/ P W/ P W/ P/O W/ P W/ P W/ P/O W/ P W/ P W/ P/O W/ P W/ P W/ P/O W/ P W/ P W/ P/O W/ P W/ P W/ P/O W W W W W W W W W W W W W W W W TDM unprotected with a 2-slot DS3/E3 ECM (Note: The 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 TDM unprotected with a 3-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.) DS3/E3/EC-1 CC DS3/EC-1 Transmux O W/ O W/ O W/ O W/ O W/ O W/ O W/ O W/ O W/ O W/ O W/ O Traverse 2000 Slot Numbers VT/VC Switching with 1:N equipment protection (Note: No ECM requirement with VT/VC switching cards.) W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P/O W/ O W/ O W/ P W/ P W/ P/O W/ O W W W/ P W/ P/O W W Operations and Maintenance Guide, Section 9: Appendices Traverse 2000 Card Placement

443 Release OPS4.2.2 Force10 Networks Page 9-15 Table 9-4 Traverse 2000 Card Placement Guidelines (continued) Card Type VT/TU 5G Switch with 1:1 Equipment Protection W/ P GCM with optics plus VTX 2 W/ P VT/VC Switching unprotected VT/TU 5G Switch without 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 Traverse 2000 Slot Numbers W/ P W/ P W W W W W W W W W W W W W W W W W W GCM with optics plus VTX 2 W W W W W W W W W W W W W W W W W W 1 Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with an Enhanced GCM for GCM redundancy. 2 While the VTX can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1 APS/MSP, UPSR/SNCP, or BLSR/MS-SPRing protection group. Important: 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. 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: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling. 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 Appendix A Module Placement Planning and Guidelines Traverse 2000 Card Placement

444 Operations and Maintenance Guide, Section 9: Appendices Traverse 2000 Card Placement Page 9-16 Force10 Networks Release OPS4.2.2

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

446 Page 9-18 Force10 Networks Release OPS4.2.2 Table 9-5 Traverse 600 Card Placement Guidelines (continued) Card Type 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 ETHERNET (Single slot) unprotected with a 2-slot 10/100BaseT ECM 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 ETHERNET (Single slot) unprotected with a 2-slot Ethernet (Protection) ECM 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 Traverse 600 Slot Numbers P W/P W/P W W W W W O W/O W/O W Operations and Maintenance Guide, Section 9: Appendices Traverse 600 Card Placement

447 Release OPS4.2.2 Force10 Networks Page 9-19 Table 9-5 Traverse 600 Card Placement Guidelines (continued) TDM 1:2 equipment protection with the corresponding ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 2-slot ECM DS1 DS3/E3/EC-1 CC DS3/EC-1 Transmux E1 TDM 1:1 equipment protection with a 3-slot ECM DS3/E3/EC-1 CC DS3/EC-1 Transmux TDM unprotected with the corresponding ECM DS1 E1 W W/P W/P W W/P W/P W/P W/P W/P/O W/P/O W/P/O W/P/O W W W W TDM unprotected with a 2-slot DS3/E3 ECM (Note: The card placement restriction is due to the electrical connector card.) DS3/E3/EC-1 CC DS3/EC-1 Transmux O W/O W/O W TDM unprotected with a 3-slot DS3/E3 ECM (Note: the card placement restriction is due to the electrical connector card.) DS3/E3/EC-1 CC DS3/EC-1 Transmux Card Type Traverse 600 Slot Numbers 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 VTX 2 W/P W/P W/P W/P Appendix A Module Placement Planning and Guidelines Traverse 600 Card Placement

448 Page 9-20 Force10 Networks Release OPS4.2.2 Table 9-5 Traverse 600 Card Placement Guidelines (continued) Card Type VT/VC Switching without Equipment Protection Traverse 600 Slot Numbers VT/TU 5G Switch W W W W OC-48/STM-16 with VTX W W W W 1 Redundant GCMs can be different types; e.g., a GCM with integrated optics (OC-12/STM-4 and OC-48/STM-16) placed with an Enhanced GCM for GCM redundancy. 2 While the VTX Switch can be in a 1:1 or unprotected protection group, the related OC-48/STM-16 facilities can be unprotected or in a 1+1 APS/MSP, UPSR/SNCP, or BLSR/MS-SPRing protection group. Important: 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. 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. Important: Place 1-slot wide blank faceplates in empty slots to ensure EMI protection and proper cooling. Operations and Maintenance Guide, Section 9: Appendices Traverse 600 Card Placement

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

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