Page 1 T R O U B L E S H O O T I N G G U I D E 3HE 05723 AAAD TQZZA Edition 01 Alcatel-Lucent Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2010 © Alcatel-Lucent. All rights reserved.
Page 2 The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.
Page 3 Alcatel-Lucent License Agreement SAMPLE END USER LICENSE AGREEMENT 1. LICENSE 1.1 Subject to the terms and conditions of this Agreement, Alcatel-Lucent grants to Customer and Customer accepts a nonexclusive, nontransferable license to use any software and related documentation provided by Alcatel-Lucent pursuant to this Agreement ("Licensed Program") for Customer's own internal...
Page 4 3.2 Alcatel-Lucent may terminate this Agreement: (a) upon notice to Customer if any amount payable to Alcatel-Lucent is not paid within thirty (30) days of the date on which payment is due; (b) if Customer becomes bankrupt, makes an assignment for the benefit of its creditors, or if its assets vest or become subject to the rights of any trustee, receiver or other administrator;...
Page 5 Alcatel-Lucent infringes any patent, copyright, trade secret or other intellectual property right, provided that Customer notifies Alcatel-Lucent within ten (10) days of the existence of the claim, gives Alcatel-Lucent sole control of the litigation or settlement of the claim, and provides all such assistance as Alcatel-Lucent may reasonably require.
Page 6 8.4 The Licensed Program may contain freeware or shareware obtained by Alcatel-Lucent from a third party source. No license fee has been paid by Alcatel-Lucent for the inclusion of any such freeware or shareware, and no license fee is charged to Customer for its use.
Page 7 8.9 No term or provision of this Agreement shall be deemed waived and no breach excused unless such waiver or consent is in writing and signed by the party claimed to have waived or consented. The waiver by either party of any right hereunder, or of the failure to perform or of a breach by the other party, shall not be deemed to be a waiver of any other right hereunder or of any other breach or failure by such other party, whether of a similar nature or otherwise.
Page 8 viii...
Page 9: Preface
5620 SAM documentation suite. Table 1 5620 SAM documentation 5620 SAM | 5650 CPAM Installation and Upgrade Guide The 5620 SAM | 5650 CPAM Installation and Upgrade Guide contains configuration information and procedures for: •...
Page 10 • Detailed procedures that list the configurable parameters on the associated forms There are dynamic links between the procedures in the 5620 SAM User Guide and the parameter descriptions in the 5620 SAM Parameter Guide. See Procedure for more information.
Page 11: Procedure 1 To Find The 5620 Sam User Documentation
5620 SAM functionality. 5620 SAM LTE User Guide The 5620 SAM LTE User Guide describes how to discover, configure, and manage LTE devices using the 5620 SAM. The guide is intended for LTE network planners, administrators, and operators.
Page 12: Procedure 2 To View 5620 Sam Parameter Guide Parameter
Procedure 2 To view 5620 SAM Parameter Guide parameter descriptions from the 5620 SAM User Guide You can click on a parameter name in a 5620 SAM User Guide procedure to open the matching parameter description in the 5620 SAM Parameter Guide. Ensure the following conditions are true beforehand: •...
Page 13: Procedures With Options Or Substeps
This step has a series of substeps that you must perform to complete the step. You must perform the following substeps. This is the first substep. This is the second substep. This is the third substep. You must perform this step. Alcatel-Lucent 5620 Service Aware Manager, Release xiii 8.0 R4 Aug 2010 3HE 05723 AAAD...
Page 14: Measurement Conventions
Caution indicates that the described activity or situation may, or will, cause service interruption. Note — Notes provide information that is, or may be, of special interest. Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723...
Page 15: Table Of Contents
Contents Preface 5620 SAM documentation suite ..............ix Procedure 1 To find the 5620 SAM user documentation......xi Procedure 2 To view 5620 SAM Parameter Guide parameter descriptions from the 5620 SAM User Guide ........ xii Prerequisites................... xii Conventions.................... xii Procedures with options or substeps ..........
Page 16 OAM diagnostics ..............2-4 Log files................2-4 Workflow for 5620 SAM troubleshooting ..........2-4 5620 SAM troubleshooting procedures ..........2-8 Procedure 2-1 To collect the 5620 SAM log files ....... 2-8 Troubleshooting the managed network 3 — Troubleshooting using network alarms Troubleshooting using network alarms ..........
Page 17 Procedure 5-2 To find the source of an alarm using a map....5-5 Network management troubleshooting 6 — 5620 SAM LogViewer 5620 SAM LogViewer overview ............6-2 Configuration ................. 6-2 Filters .................. 6-2 Plug-ins ................6-2 LogViewer GUI ................6-3 Overview ................
Page 18 Procedure 9-8 Problem: Device configuration backup not occurring ..9-11 Troubleshooting client GUI issues ........... 9-12 Procedure 9-9 Problem: 5620 SAM client GUI shuts down regularly..9-12 Procedure 9-10 Problem: Configuration change not displayed on 5620 SAM client GUI............9-12 Procedure 9-11 Problem: List or search function takes too long to complete................
Page 19 ......... 10-9 Procedure 10-8 Problem: All SNMP traps from managed devices are arriving at one 5620 SAM server, or no SNMP traps are arriving ..10-10 Procedure 10-9 Problem: Cannot manage new devices ....10-10 Procedure 10-10 Problem: Cannot discover more than one device, or device resynchronization fails .........
Page 20 Service disruption warning ............12-4 Duplicate configuration form conflicts .......... 12-5 12.2 Responding to 5620 SAM client GUI warning messages ......12-5 Procedure 12-1 To respond to a warning message ......12-5 13 — Troubleshooting with Problems Encountered forms 13-1 13.1...
Page 21: Troubleshooting Overview
Troubleshooting overview 1 — Troubleshooting process 2 — 5620 SAM troubleshooting Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 22 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 23: Troubleshooting Process
1 — Troubleshooting process 1.1 Troubleshooting process 1.2 Troubleshooting problem-solving model 1.3 Troubleshooting guidelines 1.4 Before you call support Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 24: Network Maintenance
The maintenance of the baseline information is critical because a network is not a static environment. See the 5620 SAM Maintenance Guide for more information on how to generate baseline information for 5620 SAM applications.
Page 25: Categorize The Problem
• Determine the network state before the problem appeared. • Extrapolate from network alarms and network events the cause of the symptoms. Try to reproduce the problem. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD...
Page 26: Plan Corrective Action And Resolve The Problem
1 — Troubleshooting process The following 5620 SAM features can help you identify the root cause of a problem: • alarms with vendor-specific and X.733 standardized probable causes • alarm history associated network conditions Plan corrective action and resolve the problem The corrective action required to resolve a problem depends on the problem type.
Page 27: Before You Call Support
Before you call support Collect the information listed in Table before you call your TAC or technical support representative. The list of Alcatel-Lucent support contacts is available from the Alcatel-Lucent home page at http://www.alcatel-lucent.com/support. Table 1-1 Troubleshooting data collection for support Action Collect the following •...
Page 28 1 — Troubleshooting process Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 29: 5620 Sam Troubleshooting
2 — 5620 SAM troubleshooting 2.1 5620 SAM troubleshooting process 2.2 5620 SAM troubleshooting tools 2.3 Workflow for 5620 SAM troubleshooting 2.4 5620 SAM troubleshooting procedures Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 30: 5620 Sam Troubleshooting Process
17556 Troubleshooting the managed-NE network You can use the 5620 SAM alarm and service monitoring functions to help you troubleshoot the network of managed NEs. Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 31: Troubleshooting The Network Management Domain
2 — 5620 SAM troubleshooting Alarms for network objects The 5620 SAM converts SNMP traps from NEs to events and alarms. You can then use the 5620 SAM to correlate the events and alarms to the managed object, configured services and policies. A correlated event or alarm can cause fault conditions on multiple network objects and services.
Page 32: 5620 Sam Troubleshooting Tools
2 — 5620 SAM troubleshooting 5620 SAM troubleshooting tools The 5620 SAM supports the use of OAM diagnostic tools and event logs to help identify the root cause of a network or network management problem. OAM diagnostics The 5620 SAM supports configurable in-band and out-of-band, packet-based OAM diagnostic tools to troubleshoot your network service.
Page 33 A domain, connectivity, platform, or configuration problem • Network management domain and LAN troubleshooting • Platform troubleshooting • 5620 SAM GUI and OSS client software issues • 5620 SAM main or auxiliary server software issues • 5620 SAM database and Oracle software issues •...
Page 34 Problem: Device configuration backup not occurring Procedure Problem: 5620 SAM client unable to communicate with 5620 SAM server Procedure Problem: Cannot start 5620 SAM client, or error message during client startup Procedure Problem: Cannot view 5620 SAM alarms using 5620 NM client Procedure...
Page 35 10-5 Problem: Excessive 5620 SAM server-to-client response time Procedure 10-6 Problem: Cannot start a 5620 SAM server, or unsure of 5620 SAM server status Procedure 10-1 Problem: All SNMP traps from managed devices are arriving at one 5620 SAM Procedure...
Page 36: 5620 Sam Troubleshooting Procedures
Use the following procedures for general 5620 SAM network troubleshooting. Procedure 2-1 To collect the 5620 SAM log files Perform this procedure to collect the relevant log files for troubleshooting a 5620 SAM database, server, or client problem. Note — After a system restart, 5620 SAM log files are backed up to directories that are named using a timestamp.
Page 37 5620_SAM_component.install.time.stdout.txt • 5620_SAM_component_InstallLog.log • where component is the 5620 SAM component name, for example, Database_Configurator, Server, or Client time is the installation start time For a Solaris database problem that is not related to installation, collect the following files: install_dir/admin/db_instance/bdump/alert_db_instance.log •...
Page 38 Alcatel-Lucent technical support. Log in to the 5620 SAM server station as the root user. Open a console window on the 5620 SAM server station. Navigate to the 5620 SAM server binary directory, typically /opt/5620sam/server/nms/bin directory.
Page 39 Store the files in a secure location to ensure that the files are not overwritten. For example, if there are two 5620 SAM clients that experience problems, rename the files to identify each 5620 SAM client and to prevent the overwriting of one file with another of the same name.
Page 40 2 — 5620 SAM troubleshooting 2-12 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 41: Troubleshooting The Managed Network
Troubleshooting the managed network 3 — Troubleshooting using network alarms 4 — Troubleshooting services and connectivity 5 — Troubleshooting using topology maps Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 42 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 43 3.2 Workflow to troubleshoot using network alarms 3.3 Troubleshooting using network alarms procedures 3.4 Sample problems 3-13 3.5 Alarm description tables 3-23 Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 44: Troubleshooting Using Network Alarms
Alarm Info forms managed object hierarchy table alarm description tables View the affected object states information. See Procedure 3-5. Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723...
Page 45: Troubleshooting Using Network Alarms Procedures
Use the following procedures to troubleshoot network problems using alarms. Procedure 3-1 To view and sort alarms in the dynamic alarm list Monitor the dynamic alarm list in the 5620 SAM alarm window and attempt to address alarms in the order that they are raised.
Page 46: Procedure 3-2 To View Object Alarms And Aggregated Object Alarms
Procedure 3-2 To view object alarms and aggregated object alarms You can use the navigation tree to view object alarm status, and aggregated alarm status for parent objects. See the 5620 SAM User Guide for more information about the relationship between objects, related alarms, and aggregated alarms.
Page 47 Therefore, the First Time Detected stamp is not a reliable indication of the exact time an event occurred and should be used only as an aid in troubleshooting. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723...
Page 48 3 — Troubleshooting using network alarms Table 3-1 Hierarchy of 5620 SAM-managed objects Level Managed object Alarm domain (domain descriptor) For alarm information see — General network management Accounting (accounting) Table or 5620 SAM objects Alarm mapping (trapmapper) Table 3-77...
Page 49 LSP binding MPLS (mpls) Table 3-41 Session RSVP (rsvp) Table 3-57 LDP interface or targeted peer LDP (ldp) Table 3-32 (2 of 3) Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 50: Procedure 3-4 To Acknowledge Alarms
Right-click on the selected alarm in the dynamic alarm list and choose Acknowledge Alarm(s) from the contextual menu. The Alarm Acknowledgement form opens. If required, add text in the Acknowledgement Text box. Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 51 Click on the OK button. A command confirmation appears. Click on the OK button to continue. A check mark appears for each of the selected alarms under the Ack. column in the dynamic alarm list. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010...
Page 52: Procedure 3-5 To Determine Probable Cause And Root Cause Using Alarm And Affected Object Information
Double-click on the selected alarm in the dynamic alarm list. The Alarm Info form opens as shown in the example in Figure 3-3. Figure 3-3 Alarm Info form 3-10 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 53 This does not clear the alarm on the affected object that you are investigating. Perform Procedure to review related object information. Alcatel-Lucent 5620 Service Aware Manager, Release 3-11 8.0 R4 Aug 2010 3HE 05723...
Page 54: Procedure 3-6 To Determine Root Cause Using Related Objects
Check the States information. This information should point to the root cause of the alarm. The problem should be found on the related, supporting object below the lowest level object in the alarm. 3-12 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 55: Sample Problems
Frame Size Problem alarm Troubleshooting a service equipment problem A problem in the sample network produces the list of alarms shown in Figure 3-6. Alcatel-Lucent 5620 Service Aware Manager, Release 3-13 8.0 R4 Aug 2010...
Page 56: Procedure 3-7 To Troubleshoot A Service Equipment Problem
Select the alarms related to this affected object and acknowledge the alarms. View alarm information for the affected object. Double-click on the alarm in the list to view the information in the Alarm Info form. 3-14 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 57: Procedure 3-8 To Clear Alarms Related To An Equipment Problem
Equipment Down alarms on LAG 1, automatically clear. Troubleshooting an underlying port state problem An underlying port state problem in the sample network produces the list of alarms shown in Figure 3-7. Alcatel-Lucent 5620 Service Aware Manager, Release 3-15 8.0 R4 Aug 2010...
Page 58: Procedure 3-9 To Troubleshoot An Underlying Port State Problem
In this case, the only alarm listed under Related Problems is the dynamic Lsp Down alarm. View alarm information for the affected object. Double-click on the alarm in the list to view the information in the Alarm Info form. 3-16 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723...
Page 59 Click on the Port tab button to view the underlying port state of the LAG member, as shown in Figure 3-8. The LAG Member 1/1/2 properties form shows the Underlying Port State: Shut Down. Alcatel-Lucent 5620 Service Aware Manager, Release 3-17 8.0 R4...
Page 60 In the equipment view of the navigation tree, choose port 1/1/2 under the Shelf object that supports LAG 1 (Site 10.1.200.53), and choose Properties from the contextual menu. The properties form opens, as shown in Figure 3-9. 3-18 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 61: Procedure 3-10 To Clear Alarms Related To An Underlying Port State Problem
LAG 1 at Site 10.1.200.53. The State is Admin Down. Choose the port and choose Turn Up from the contextual menu. Of the 18 alarms, 16 automatically clear. The remaining two alarms are Session alarms. Alcatel-Lucent 5620 Service Aware Manager, Release 3-19 8.0 R4...
Page 62: Troubleshooting A Service Configuration Problem
Affected object is SDP binding (formerly known as circuit). • Alarm type is configuration alarm. • Probable cause is frame size problem. • Domain is Service Tunnel Management. • 3-20 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 63: Procedure 3-12 To Clear A Frame Size Problem (Mtu Mismatch) Alarm
This procedure describes how to clear the SDP binding Frame Size Problem alarm described in this section. Choose Manage→Services from the 5620 SAM main menu. Configure the list filter criteria and click on the Search button. A list of services appears at the bottom of the Browse Services form.
Page 64 Click on the Apply button. The MTU configuration change is applied to customer, service, and site objects. The SDP binding and related service alarms clear automatically. 3-22 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723...
Page 65: Alarm Description Tables
3 — Troubleshooting using network alarms Alarm description tables The following tables describe the alarms that the 5620 SAM can raise. The tables are in alphabetical order by domain, and the alarms within each table are in alphabetical order. A Type or Probable cause value includes a numeric identifier.
Page 66 Type: ProtocolAlarm (1) Object Type (class): Peer maximum number of peer routes. Probable cause: prefixLimitNearing (3) Domain: bgp Implicitly cleared (self-clearing): No 3-24 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 67 Type: equipmentAlarm (3) Object Type (class): Operational State is Down. CrossConnectAggregationGroup Probable cause: CcagDown (163) Domain: ccag Implicitly cleared (self-clearing): Yes Alcatel-Lucent 5620 Service Aware Manager, Release 3-25 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 68 Unexpected Size or Bad Headers Probable cause: thresholdCrossed (12) Domain: circem stack crosses the threshold. Implicitly cleared (self-clearing): No (1 of 2) 3-26 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 69 DatabaseManager Probable cause: archivedLogsIssue (154) disk space.When database disk space Domain: db is low, the 5620 SAM first deletes the Implicitly cleared (self-clearing): No archive logs that have been applied to the standby database and raises the OldArchiveLogsDeleted alarm. If...
Page 70 5620 SAM system. (2 of 5) 3-28 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4...
Page 71 DatabaseManager Probable cause: archivedLogsIssue (154) low. In a standalone deployment, the Domain: db 5620 SAM deletes all archive logs. In Implicitly cleared (self-clearing): No a redundant deployment, the 5620 SAM deletes the applied archive logs, and can raise the alarm against the primary or standby database.
Page 72 (193) Domain: db Implicitly cleared (self-clearing): No Name: RealignmentOfDatabase Severity: Warning The alarm is raised when the primary 5620 SAM main server realigns itself Type: configurationAlarm (11) Object Type (class): with the preferred database by DatabaseManager Probable cause: databaseRealignment (455)
Page 73 Name: UnableDeleteArchivedLogs Severity: Major The alarm is raised when database disk space is low and the 5620 SAM is Type: databaseAlarm (29) Object Type (class): unable to delete the archive logs. DatabaseManager Probable cause: archivedLogsIssue (154)
Page 74 Type: environmentalAlarm (2) Object Type (class): Shelf threshold value. Probable cause: equipmentOvercooled Domain: equipment (838) Implicitly cleared (self-clearing): Yes (1 of 14) 3-32 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 75 Type: thresholdCrossed (6) Object Type (class): PhysicalPort Seconds crosses the threshold. Probable cause: thresholdCrossed (12) Domain: equipment Implicitly cleared (self-clearing): No (2 of 14) Alcatel-Lucent 5620 Service Aware Manager, Release 3-33 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 76 StackConfiguration Probable cause: stackNotInLoop (355) contains an unexpected element. Domain: equipment Implicitly cleared (self-clearing): Yes (3 of 14) 3-34 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 77 Type: storageAlarm (25) Object Type (class): FlashMemory compact flash unit. Probable cause: dataLoss (122) Domain: equipment Implicitly cleared (self-clearing): Yes (4 of 14) Alcatel-Lucent 5620 Service Aware Manager, Release 3-35 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 78 XFP approaches the minimum (50) DigitalDiagnosticMonitoring threshold value. Probable cause: aux2LowWarning (382) Domain: equipment Implicitly cleared (self-clearing): Yes (5 of 14) 3-36 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 79 Object Type (class): reaches the maximum threshold DigitalDiagnosticMonitoring Probable cause: temperatureHighAlarm value. (361) Domain: equipment Implicitly cleared (self-clearing): Yes (6 of 14) Alcatel-Lucent 5620 Service Aware Manager, Release 3-37 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 80 Object Type (class): the maximum threshold value. DigitalDiagnosticMonitoring Probable cause: txOutputPowerHighWarning (372) Domain: equipment Implicitly cleared (self-clearing): Yes (7 of 14) 3-38 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 81 Implicitly cleared (self-clearing): No based on the up time, slot number, and MAC address. Both slots subsequently enter pass-through mode. (8 of 14) Alcatel-Lucent 5620 Service Aware Manager, Release 3-39 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 82 Type: communicationsAlarm (4) Object Type (class): PhysicalPort Probable cause: Domain: equipment excessiveEnvironmentTemp (830) Implicitly cleared (self-clearing): Yes (9 of 14) 3-40 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 83 Type: equipmentAlarm (3) Object Type (class): Equipment Probable cause: lanFailure (467) Domain: equipment Implicitly cleared (self-clearing): Yes (10 of 14) Alcatel-Lucent 5620 Service Aware Manager, Release 3-41 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 84 Object Type (class): BaseCard specified complex in the specified Probable cause: pChipError (447) Domain: equipment direction. Implicitly cleared (self-clearing): Yes (11 of 14) 3-42 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 85 Object Type (class): Equipment type and the expected card type. Probable cause: equipmentMismatch (473) Domain: equipment Implicitly cleared (self-clearing): Yes (12 of 14) Alcatel-Lucent 5620 Service Aware Manager, Release 3-43 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 86 Object Type (class): The slot subsequently enters StackConfiguration Probable cause: pass-through mode. elementNotCompatibleWithExistingStack Domain: equipment (357) Implicitly cleared (self-clearing): No (13 of 14) 3-44 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 87 XPL Errors. Type: hardwareAnomaly (55) Object Type (class): DaughterCard Probable cause: xplError (443) Domain: equipment Implicitly cleared (self-clearing): Yes (14 of 14) Alcatel-Lucent 5620 Service Aware Manager, Release 3-45 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 88 OTU-enabled interface. Type: communicationsAlarm (4) Domain: ethernetequipment Probable cause: Implicitly cleared (self-clearing): Yes BackwardIncomingAlignmentError (578) (1 of 4) 3-46 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 89 Type: communicationsAlarm (4) Object Type (class): OtuInterface OTU-enabled interface. Probable cause: ODUAlarmIndicationSignal Domain: ethernetequipment (542) Implicitly cleared (self-clearing): Yes (2 of 4) Alcatel-Lucent 5620 Service Aware Manager, Release 3-47 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 90 Type: communicationsAlarm (4) Object Type (class): wavelength tracker interface. WaveLengthTracker Probable cause: EncoderDegrade (584) Domain: ethernetequipment Implicitly cleared (self-clearing): Yes (3 of 4) 3-48 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 91 EthernetTunnelEndpoint Probable cause: configurationMismatch Ethernet tunnel group (548) Domain: ethernettunnel configurations. Implicitly cleared (self-clearing): Yes (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 3-49 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 92 Alarm Attributes Additional information Name: DeploymentFailure Severity: Minor The alarm is raised when the 5620 SAM is unable to create, Type: deploymentFailure (5) Object Type (class): GenericObject modify, or delete a network object Probable cause: Domain: generic because of NE unreachability or a...
Page 93 Object Type (class): Site than Up, and the Administrative Probable cause: protocolDown (1) Domain: igmp State is Up. Implicitly cleared (self-clearing): Yes (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 3-51 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 94 Type: serviceAlarm (16) Object Type (class): IPSecTunnelBfd Probable cause: Domain: ipsec bfdSessionConnectionBroken (593) Implicitly cleared (self-clearing): Yes (1 of 2) 3-52 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 95 Type: equipmentAlarm (3) Object Type (class): AaGroup from one ISA-AA to another. Probable cause: isaAaGrpSwitchover (437) Domain: isa Implicitly cleared (self-clearing): No (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 3-53 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 96 Type: authenticationAlarm (14) Object Type (class): Site wrong authentication type. Probable cause: authFailure (46) Domain: isis Implicitly cleared (self-clearing): Yes (1 of 2) 3-54 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 97 Probable cause: StpException (228) Domain: l2fwd communication or a downstream Implicitly cleared (self-clearing): Yes loop. The alarm clears when the STP status changes. (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 3-55 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 98 STP root guard violation. Type: AccessInterfaceAlarm (32) Object Type (class): AccessInterfaceStp Probable cause: spanningTreeTopologyChanged (331) Domain: l2fwd Implicitly cleared (self-clearing): Yes (2 of 2) 3-56 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 99 Alarm Attributes Additional information Name: DuplicateVrfPolicy Severity: Warning The alarm is raised when the 5620 SAM detects a duplicate VRF Type: configurationAlarm (11) Object Type (class): policy in a VPRN. The alarm ServiceSiteImportPolicy, Probable cause: duplicateVrfPolicyExists information includes the VRF policy...
Page 100 IPv6 routes and the threshold value. Name: MVPNDuplicateVrfPolicy Severity: Warning The alarm is raised when the 5620 SAM detects a duplicate VRF Type: configurationAlarm (11) Object Type (class): policy in a multicast VPRN. The ServiceSiteMVPNExportPolicy, Probable cause: duplicateVrfPolicyExists...
Page 101 Domain: lag Implicitly cleared (self-clearing): Yes Name: McLagSourceBMacLsbMisconfigured Severity: Major The alarm is raised when the 5620 SAM detects a mismatch in the Type: configurationAlarm (11) Object Type (class): MultiChassisLag last 16 bits of the source backbone Probable cause: Domain: lag MAC address on the peer device.This...
Page 102 MAC address. Type: learnedPortSecurityAlarm (51) Object Type (class): LearnedPortSecurity Probable cause: portLearnedBridgedMAC (394) Domain: lps Implicitly cleared (self-clearing): Yes (1 of 2) 3-60 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 103 0 Name: LpsViolation Severity: Major The alarm is raised when the 5620 SAM detects an LPS violation. Type: learnedPortSecurityAlarm (51) Object Type (class): LearnedPortSecurity Probable cause: learnedPortSecurityViolation (393) Domain: lps...
Page 104 Alarm Attributes Additional information Name: MobileConnectorDown Severity: Minor The alarm is raised when the 5620 SAM no longer manages the EPS Type: EpcAlarm (59) Object Type (class): path instance of this mobile service MobileServiceConnector Probable cause: EpcDown (519) site. As a result, the service must be Domain: lteservice regenerated.
Page 105 Alarm Attributes Additional information Name: MobileSiteDown Severity: Minor The alarm is raised when the 5620 SAM no longer manages the EPS Type: EpcAlarm (59) Object Type (class): gateway instance of this mobile MobileServiceSite Probable cause: EpcDown (519) service site. As a result, the service Domain: lteservice must be regenerated.
Page 106 LI. Probable cause: Domain: mirrorli tMirrorSourceMacFltrChangeReject (423) Implicitly cleared (self-clearing): No (2 of 3) 3-64 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 107 The default problematicRetryStrategy value of reactive prevents the alarm from being raised. (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 3-65 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 108 LspPathReroutedToBypassTunnel (197) Implicitly cleared (self-clearing): Yes original tunnel and the actual hop returns to the primary path. (1 of 3) 3-66 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 109 S2L path Implicitly cleared (self-clearing): Yes Operational State changes to Up or the Administrative State changes to Down. (2 of 3) Alcatel-Lucent 5620 Service Aware Manager, Release 3-67 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 110 3 — Troubleshooting using network alarms Alarm Attributes Additional information Name: TunnelAdministrativelyDown Severity: Minor The alarm is raised when the 5620 SAM detects that an MPLS path Type: pathAlarm (12) Object Type (class): Tunnel is administratively down. Probable cause: Domain: mpls tunnelAdministrativelyDown (333)
Page 111 A cross connect is deleted. • The Operational State of one or more ports in the cross connect is Down. (2 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 3-69 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 112 Up to Down. The alarm Probable cause: protocolDown (1) Domain: msdp clears when the Administrative State Implicitly cleared (self-clearing): Yes returns to Up. 3-70 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 113 MC LAG are operationally down. Type: equipmentAlarm (3) Object Type (class): MultiChassisLagPeerSpecifics Probable cause: mcLagDown (295) Domain: multichassis Implicitly cleared (self-clearing): Yes (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 3-71 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 114 Alarm Attributes Additional information Name: McLagSourceBMacLsbMisconfigured Severity: Major The alarm is raised when the 5620 SAM detects a mismatch in the Type: configurationAlarm (11) Object Type (class): MultiChassisLag last 16 bits of the source backbone Probable cause: Domain: multichassis MAC address on the peer device.This...
Page 115 Table 3-46 Domain: netw Alarm Attributes Additional information Name: ActivitySwitch Severity: Critical The alarm is raised when a 5620 SAM main server activity switch occurs. Type: communicationsAlarm (4) Object Type (class): NmsSystem Probable cause: systemFailed (144) Domain: netw Implicitly cleared (self-clearing): No...
Page 116 Severity: Variable or indeterminate This user-definable alarm is raised against a generic NE when the Type: CommunicationAlarm (64) Object Type (class): 5620 SAM receives a trap from the NetworkElement Probable cause: User_Defined (558) generic NE that is mapped to the Domain: netw...
Page 117 Severity: Variable or indeterminate This user-definable alarm is raised against a generic NE when the Type: EnvironmentalAlarm (65) Object Type (class): 5620 SAM receives a trap from the NetworkElement Probable cause: User_Defined (558) generic NE that is mapped to the Domain: netw...
Page 118 Severity: Variable or indeterminate This user-definable alarm is raised against a generic NE when the Type: TransportAlarm (71) Object Type (class): 5620 SAM receives a trap from the NetworkElement Probable cause: User_Defined (558) generic NE that is mapped to the Domain: netw...
Page 119 The NE is resynchronized only if required. Name: MisconfiguredNode Severity: Major The alarm is raised when the 5620 SAM tries to discover an NE that Type: configurationAlarm (11) Object Type (class): Topology is not properly configured for Probable causes: Domain: netw management, for example, when •...
Page 120 Domain: netw Implicitly cleared (self-clearing): No Name: NodeRebooted Severity: Warning The alarm is raised when the 5620 SAM detects an NE reboot based Type: equipmentAlarm (3) Object Type (class): on the latest NE sysUpTime value. NetworkElement Probable cause: nodeReboot (25)
Page 121 MTUs match. physicalLinkPortsMisconfigured (181) Domain: netw Implicitly cleared (self-clearing): Yes Name: PollDeadlineMissed Severity: Warning The alarm is raised when a 5620 SAM server cannot finish browsing a Type: configurationAlarm (11) Object Type (class): statistics MIB before a polling NetworkElement Probable cause: tooManyItemsToPoll (183) interval expires.
Page 122 Implicitly cleared (self-clearing): Yes probable cause is an unreachable NE SNMP agent on the NE. By default, the 5620 SAM polls a managed NE every two minutes. If a poll fails, the alarm is raised.The 5620 SAM polls the NE two minutes after the first failure.
Page 123 Severity: Critical The alarm is raised when the global number of SNMP traps that await Type: communicationsAlarm (4) Object Type (class): NmsSystem processing by the 5620 SAM surpasses Probable cause: tooManyTrapsBuffered Domain: netw the system red threshold for trap (173)
Page 124 Name: TrapDestinationMisconfigured Severity: Major The alarm is raised when an SNMP trap destination other than the Type: configurationAlarm (11) Object Type (class): 5620 SAM is configured on an NE. NetworkElement Probable causes: Domain: netw • trapDestinationMisconfigured (26) Implicitly cleared (self-clearing): Yes •...
Page 125 Type: communicationsAlarm (4) Object Type (class): NmsSystem reaches the yellow threshold. When Probable cause: tooManyAlarms (182) Domain: netw this happens, the 5620 SAM discards Implicitly cleared (self-clearing): No non-critical alarms to keep the number below the threshold. (11 of 11)
Page 126 Implicitly cleared (self-clearing): No authentication type conflicts with the local NE authentication key or • authFailure (46) authentication type. (2 of 12) 3-84 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 127 Type: NeighborDown (20) Object Type (class): Interface down. Probable cause: NeighborDown (103) Domain: ospf Implicitly cleared (self-clearing): Yes (3 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-85 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 128 Type: NeighborDown (20) Object Type (class): down. AbstractNeighbor Probable cause: NeighborDown (103) Domain: ospf Implicitly cleared (self-clearing): Yes (4 of 12) 3-86 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 129 (45) Implicitly cleared (self-clearing): No with the local NE authentication key or authentication type. • authFailure (46) (5 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-87 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 130 (45) Implicitly cleared (self-clearing): No with the local NE authentication key or authentication type. • authFailure (46) (6 of 12) 3-88 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 131 • authTypeMismatch (45) Implicitly cleared (self-clearing): No the local NE authentication key or authentication type. • authFailure (46) (7 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-89 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 132 Implicitly cleared (self-clearing): No type conflicts with the local NE authentication key or authentication • authFailure (46) type. (8 of 12) 3-90 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 133 (45) Implicitly cleared (self-clearing): No with the local NE authentication key or authentication type. • authFailure (46) (9 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-91 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 134 (45) Implicitly cleared (self-clearing): No with the local NE authentication key or authentication type. • authFailure (46) (10 of 12) 3-92 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 135 Implicitly cleared (self-clearing): No • dbDescript (48) • lsReq (49) • lsUpdate (50) • lsAck (51) • nullPacket (52) (11 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-93 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 136 Type: configurationAlarm (11) Object Type (class): VirtualAnyCastRP Probable cause: missingStaticRPConfigurations (200) Domain: pim Implicitly cleared (self-clearing): Yes (1 of 2) 3-94 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 137 Probable cause: PppLoopbackDetected Domain: ppp tmnxPppRemoteMagicNumber, (259) Implicitly cleared (self-clearing): Yes which indicates that the link may be looped back. Alcatel-Lucent 5620 Service Aware Manager, Release 3-95 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 138 Type: communicationsAlarm (4) Object Type (class): RadioPortSpecifics Probable cause: incompatibleModulation (850) Domain: radioequipment Implicitly cleared (self-clearing): Yes (1 of 2) 3-96 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 139 Probable cause: Domain: radiusaccounting RADIUS servers specified in the radiusAccountingRequestFailure (260) Implicitly cleared (self-clearing): No RADIUS accounting policy. Alcatel-Lucent 5620 Service Aware Manager, Release 3-97 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 140 ResidentialSubscriberInstance Probable cause: resourceFull (53) watermark. Domain: ressubscr Implicitly cleared (self-clearing): Yes (1 of 2) 3-98 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 141 Domain: rmon Implicitly cleared (self-clearing): Yes Name: MissingFallingEvent Severity: Major The alarm is raised when the 5620 SAM cannot find the falling Type: configurationAlarm (11) Object Type (class): Alarm event object that is named in an Probable cause: incompleteConfig (225) Domain: rmon RMON policy alarm definition.
Page 142 Alarm Attributes Additional information Name: MissingRisingEvent Severity: Major The alarm is raised when the 5620 SAM cannot find the rising Type: configurationAlarm (11) Object Type (class): Alarm event object that is named in an Probable cause: incompleteConfig (225) Domain: rmon RMON policy alarm definition.
Page 143 Table 3-60 Domain: sas Alarm Attributes Additional information Name: SasAccountingAlarm Severity: Minor The alarm is raised when the 5620 SAM cannot find an SAA Type: oamAlarm (18) Object Type (class): TestSuite Accounting Policy. Probable cause: noAccountingPolicy (506) Domain: sas Implicitly cleared (self-clearing): No...
Page 144 Severity: Warning The alarm is raised when a configurable number of attempts to Type: communicationsAlarm (4) Object Type (class): log in to a 5620 SAM client fail. The TSecurityManager Probable cause: multipleSecurityViolations alarm information includes the user (336) Domain: security name.
Page 145 The alarm is raised when a durable JMS client is removed from the Type: communicationsAlarm (4) Object Type (class): User 5620 SAM because of a JMS server Probable cause: jmsServerRestart (401) Domain: security restart or switchover. Implicitly cleared (self-clearing): Yes...
Page 146 100 percent of Probable cause: licensedLimitExceeded Domain: security the license capacity. (106) Implicitly cleared (self-clearing): Yes (3 of 12) 3-104 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 147 90 to 100 percent of the Type: licensingAlarm (23) Domain: security license capacity. Probable cause: Implicitly cleared (self-clearing): Yes licensedLimitNearlyExceeded (133) (4 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-105 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 148 100 percent of the Type: licensingAlarm (23) Domain: security license capacity. Probable cause: licensedLimitExceeded Implicitly cleared (self-clearing): Yes (106) (5 of 12) 3-106 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 149 Object Type (class): License reaches 75 to 90 percent of the Probable cause: licensedLimitNearing (132) Domain: security license capacity. Implicitly cleared (self-clearing): Yes (6 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-107 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 150 Object Type (class): CpamLicense reaches 100 percent of the license Probable cause: Domain: security capacity. cpamLicensedLimitExceeded (285) Implicitly cleared (self-clearing): Yes (7 of 12) 3-108 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 151 75 to 90 percent of the Type: cpamLicensingAlarm (39) CpamLicenseScenario license capacity. Probable cause: cpamLicensedLimitNearing Domain: security (283) Implicitly cleared (self-clearing): Yes (8 of 12) Alcatel-Lucent 5620 Service Aware Manager, Release 3-109 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 152 Object Type (class): License reaches 100 percent of the license Probable cause: licensedLimitExceeded Domain: security capacity. (106) Implicitly cleared (self-clearing): Yes (9 of 12) 3-110 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 153 The alarm is raised when the number of OMS that are connected to the Type: licensingAlarm (23) Object Type (class): License 5620 SAM reaches 75 to 90 percent of Probable cause: licensedLimitNearing (132) Domain: security the license capacity. Implicitly cleared (self-clearing): Yes...
Page 154 The alarm is raised when the number of XMS that are connected to the Type: licensingAlarm (23) Object Type (class): License 5620 SAM reaches 75 to 90 percent of Probable cause: licensedLimitNearing (132) Domain: security the license capacity. Implicitly cleared (self-clearing): Yes...
Page 155 (58) • wrongDigest (59) • decryptionError (60) Name: NewSsh2ServerKeyDetected Severity: Warning The alarm is raised when a 5620 SAM main server detects a new public SSH Type: communicationsAlarm (4) Object Type (class): KnownHostKey key. Probable cause: ssh2ServerKeyMismatch Domain: security...
Page 156 Domain: server Implicitly cleared (self-clearing): Yes Name: HostnameMismatch Severity: Critical The alarm is raised when an auxiliary server host name in a 5620 SAM main Type: configurationAlarm (11) Object Type (class): AuxiliaryServer server configuration does not match Probable cause: hostnameMismatch (509)
Page 157 VLAN service, and by vRtrIfDHCPLeasePopulate for an IES or VPRN service. Name: sapDHCPProxyServerError Severity: Major The alarm is raised when the 5620 SAM is unable to proxy a DHCP Type: communicationsAlarm (4) Object Type (class): AccessInterface request. Probable cause: UnableProxyDHCPRequest Domain: service...
Page 158 VLAN is configured using a port that is not in Network mode. Name: TypeMismatch Severity: Critical The alarm is raised when one 5620 SAM service ID is associated Type: configurationAlarm (11) Object Type (class): Service with service sites that belong to Probable cause: Domain: service different service types.
Page 159 Implicitly cleared (self-clearing): Yes timingReferenceNotQualified (418) Name: SiteSyncDeploymentFailure Severity: Major The alarm is raised when the 5620 SAM tries to deploy a value for Type: equipmentAlarm (3) Object Type (class): SiteSync an object when a transaction that Probable cause: siteSyncFailure (441)
Page 160 SonetPortMonitorSpecifics Probable cause: sectionLossOfFrame (76) Domain: sonetequipment Implicitly cleared (self-clearing): Yes (1 of 3) 3-118 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 161 SonetChannelMonitorSpecifics Probable cause: on an NE. pathRemoteDefectIndication (65) Domain: sonetequipment Implicitly cleared (self-clearing): Yes (2 of 3) Alcatel-Lucent 5620 Service Aware Manager, Release 3-119 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 162 Probable cause: dualMaster (313) Domain: srrp Implicitly cleared (self-clearing): No Name: InstanceDown Severity: Major The alarm is raised when the 5620 SAM detects that an SRRP Type: configurationAlarm (11) Object Type (class): Instance instance is operationally down. Probable cause: instanceDown (216) Domain: srrp...
Page 163 Object Type (class): SdpBinding than the supported MTU size value. Probable cause: frameSizeProblem (33) Domain: svt Implicitly cleared (self-clearing): Yes (1 of 3) Alcatel-Lucent 5620 Service Aware Manager, Release 3-121 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 164 Domain: svt Administrative State is Up. Implicitly cleared (self-clearing): Yes Name: TunnelAdministrativelyDown Severity: Minor The alarm is raised when the 5620 SAM detects that a service Type: pathAlarm (12) Object Type (class): Tunnel tunnel is administratively down. Probable cause: Domain: svt...
Page 165 Table 3-73 Domain: sw Alarm Attributes Additional information Name: BootableConfigBackupFailed Severity: Major The alarm is raised when the 5620 SAM fails to back up a set of NE Type: configurationAlarm (11) Object Type (class): configuration files. BackupRestoreManager Probable cause: fileTransferFailure (89) Domain: sw...
Page 166 Type: softwareAlarm (19) Object Type (class): CardSoftware begins. Probable cause: softwareInitializing (94) Domain: sw Implicitly cleared (self-clearing): Yes (2 of 3) 3-124 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 167 3 — Troubleshooting using network alarms Alarm Attributes Additional information Name: SoftwareUpgradeFailed Severity: Major The alarm is raised when an NE software upgrade using the 5620 SAM Type: configurationAlarm (11) Object Type (class): fails. SoftwareUpgradeManager Probable cause: fileAccessError (90) Domain: sw...
Page 168 Object Type (class): channel has an OOF alarm condition. DS3E3ChannelSpecifics Probable cause: outOfFrame (100) Domain: tdmequipment Implicitly cleared (self-clearing): Yes (2 of 3) 3-126 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 169 Type: configurationAlarm (11) Object Type (class): invalid. The alarm is deprecated in TemplateBinding Probable cause: referencedObjectInvalid the 5620 SAM, Release 6.0 and later. (152) Domain: template Implicitly cleared (self-clearing): Yes Name: DependentObjectDeleted Severity: Major...
Page 170 Type: topologyAlarm (34) Object Type (class): Cpaa maximum threshold value. Probable cause: unstableBgpSpeaker (409) Domain: topology Implicitly cleared (self-clearing): Yes (1 of 4) 3-128 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 171 Probable cause: Domain: topology many external LSAs are flooding the manyExternalLSAsFloodingIntoIGP (271) Implicitly cleared (self-clearing): Yes IGP. (2 of 4) Alcatel-Lucent 5620 Service Aware Manager, Release 3-129 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 172 7701 CPAAs for IS-IS level Type: configurationAlarm (11) Object Type (class): Cpaa Probable cause: tooManyCpaaForIsisLevel2 Domain: topology (288) Implicitly cleared (self-clearing): Yes (3 of 4) 3-130 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 173 Alarm Attributes Additional information Name: TrapMapperQueueFull Severity: Critical The alarm is raised when the 5620 SAM detects that the queue for Type: queueFull (73) Object Type (class): traps that are to be mapped to TrapMapperManager Probable cause: trapRateTooHigh (564) alarms is full. Until queue space is...
Page 174 Domain: tunnelmgmt Implicitly cleared (self-clearing): No Name: TunnelElementInUseWarning Severity: Warning The alarm is raised when the 5620 SAM does not attempt to delete Type: configurationAlarm (11) Object Type (class): TopologyRule an obsolete or unused tunnel Probable cause: tunnelElementInUse (264) Domain: tunnelmgmt...
Page 175 Table 3-80 Domain: vll Alarm Attributes Additional information Name: CesBfrOverrun Severity: Major The alarm is raised when the 5620 SAM detects a jitter buffer Type: communicationsAlarm (4) Object Type (class): overrun. VllCesInterfaceSpecifics Probable cause: bufferOverrun (322) Domain: vll Implicitly cleared (self-clearing): Yes...
Page 176 The number of MAC addresses includes the static MAC addresses on the endpoint and the learned MAC addresses in the spoke SDPs that are associated with the endpoint. The alarm clears when the 5620 SAM receives the svcEndpointMacLimitAlarmCleared trap from the NE. Name:...
Page 177 Probable cause: missSpokeConfiguration Domain: vpls M-VPLS or VPLS. The alarm is not (172) Implicitly cleared (self-clearing): Yes raised by the 5620 SAM, Release 4.0 or later. Name: MldSnpgGrpDroppedLimitExceeded Severity: Warning The alarm is raised when a SAP drops an MLD group because the...
Page 178 Probable cause: hashLabelMismatch (826) Domain: vprn service. Implicitly cleared (self-clearing): Yes Name: InterfaceDown Severity: Major The alarm is raised when the 5620 SAM detects that an interface is Type: configurationAlarm (11) Object Type (class): operationally down. IPMirrorInterface Probable cause: interfaceDown (32) Domain: vprn...
Page 179 Domain: vrrp Implicitly cleared (self-clearing): No Name: InstanceDown Severity: Major The alarm is raised when the 5620 SAM detects that a VRRP Type: configurationAlarm (11) Object Type (class): instance is operationally down. AbstractInstance Probable cause: instanceDown (216) Domain: vrrp...
Page 180 Probable cause: interface is not referenced by the undefinedSchedulerReference (101) Domain: vs scheduler policy for the interface. Implicitly cleared (self-clearing): Yes 3-138 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 181: Troubleshooting Services And Connectivity
Troubleshooting services and connectivity 4.1 Troubleshooting services and connectivity 4.2 Workflow to troubleshoot a service or connectivity problem 4.3 Service and connectivity troubleshooting procedures Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01...
Page 182: Stm Oam Diagnostics For Troubleshooting
5620 SAM alarms. STM OAM diagnostics for troubleshooting You can use the 5620 SAM Service Test Manager, or STM, OAM diagnostic tools to troubleshoot a service or transport. The STM provides the ability to group OAM diagnostic tests into test suites for more comprehensive fault monitoring and troubleshooting.
Page 183: Workflow To Troubleshoot A Service Or Connectivity Problem
Verify the connectivity of the customer equipment using the entries in the FIB. See Procedure 4-3. Verify that the 5620 SAM service configuration aligns with the customer requirements. For example, ensure that 5620 SAM configuration uses the correct service type and SAP configuration, and that the circuit and site are included in the service.
Page 184: Service And Connectivity Troubleshooting Procedures
(For MPLS encapsulation, only.) If the LSP Trace results do not meet the requirements of your network, review the resource availability and configurations along the LSP expected routes. See Procedure 4-10. Contact your Alcatel-Lucent technical support representative if the problem persists. See chapter for more information.
Page 185: Of Service Components
General Procedure 4.2. If the operational state is Down and the administrative state is Up for one or more service components, the 5620 SAM generates an alarm. You must investigate the root problem on the underlying object. See chapter more information.
Page 186: Procedure 4-3 To Verify The Fib Configuration
Procedure 4-4 To verify connectivity for all egress points in a service using MAC Ping and MAC Trace Choose Tools→Service Test Manager (STM) from the 5620 SAM main menu. The Manage Tests form appears. Click on the Create button.
Page 187 FEC on the router interface is not the specified label. downstreamNotMac (6) The replying router is a downstream router, but it does not have the specified MAC address. (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD...
Page 188: Using Mef Mac Ping
Procedure 4-5 To verify connectivity for all egress points in a service using MEF MAC Ping Choose Tools→Service Test Manager (STM) from the 5620 SAM main menu. The Manage Tests form appears. Click on the Create button.
Page 189: Mtu Ping
MTU Ping Record the maximum frame transmission size for the service. Choose Manage→Service Tunnels from the 5620 SAM main menu. The Manage Service Tunnels form appears. Filter to list only the source and destination routers of the service tunnel and click on the Search button.
Page 190: Using Service Site Ping
Alcatel-Lucent technical support representative. See section more information. Procedure 4-7 To verify the end-to-end connectivity of a service using Service Site Ping Choose Tools→Service Test Manager (STM) from the 5620 SAM main menu. The Manage Tests form appears. Click on the Create button. 4-10...
Page 191 If the MAC Ping performed in Procedure failed: Investigate the status of the two SAPs used for the circuit. Correct the configuration issue related to the SAPs, if required. Alcatel-Lucent 5620 Service Aware Manager, Release 4-11 8.0 R4 Aug 2010...
Page 192: Tunnel Using Tunnel Ping
Procedure 4-8 To verify the end-to-end connectivity of a service tunnel using Tunnel Ping Choose Manage→Service Tunnels from the 5620 SAM main menu. The Manage Service Tunnels form appears. Filter to list only the source and destination routers of the service tunnel and click on the Search button.
Page 193 Double-click on the entry in the Tunnel Ping results form to view the diagnostic details. Review the diagnostic results and assess whether the configuration meets the network requirements. Table lists the displayed messages. Alcatel-Lucent 5620 Service Aware Manager, Release 4-13 8.0 R4 Aug 2010 3HE 05723 AAAD...
Page 194: Using Lsp Ping
Alcatel-Lucent technical support representative. See section more information. Procedure 4-9 To verify end-to-end connectivity of an MPLS LSP using LSP Ping Choose Tools→Service Test Manager (STM) from the 5620 SAM main menu. The Manage Tests form appears. Click on the Create button. 4-14...
Page 195 (9) One or more TLVs were not understood. If the LSP Ping passes, you have completed the workflow for troubleshooting services. Contact your Alcatel-Lucent technical support representative if the problem persists. See section for more information. If the LSP Ping fails, verify the administrative and operational status of the underlying L2 equipment.
Page 196: Trace
Alcatel-Lucent technical support representative. See section more information. Procedure 4-10 To review the route for an MPLS LSP using LSP Trace Choose Tools→Service Test Manager (STM) from the 5620 SAM main menu. The Manage Tests form appears. Click on the Create button.
Page 197: Procedure 4-11 To Review Acl Filter Properties
If a host is having a problem connecting to the network, one possibility for the problem is dropped packets as a result of anti-spoofing filters on the SAP. The 5620 SAM allows you to view the anti-spoof filters currently in effect on a SAP.
Page 198: The Snmpdump Utility
MIBs on a generic NE. The exported information may help with troubleshooting the generic NE configuration on the device or in the 5620 SAM. Log in to a 5620 SAM main server station as one of the following users: •...
Page 199 IF-MIB.ifEntry : 21 IP-MIB.ipAddrEntry : 5 MPLS-LSR-STD-MIB.mplsInterfaceEntry : 8 MPLS-TE-STD-MIB.mplsTunnelEntry : 0 MPLS-TE-STD-MIB.mplsTunnelHopEntry : 0 MPLS-TE-STD-MIB.mplsTunnelARHopEntry : 0 MPLS-TE-STD-MIB.mplsTunnelCHopEntry : 0 Alcatel-Lucent 5620 Service Aware Manager, Release 4-19 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 200 MPLS-LDP-STD-MIB.mplsLdpPeerEntry : 3 The utility is finished when the command prompt is displayed. To view the utility output, open the file using a MIB browser or a text editor. 4-20 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 201: Troubleshooting Using Topology Maps
5 — Troubleshooting using topology maps 5.1 Network topology map overview 5.2 Troubleshooting alarms using topology maps Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 202: Network Topology Map Overview
5 — Troubleshooting using topology maps Network topology map overview Several network topology maps are available on the 5620 SAM. The maps display network objects. You can open contextual menus and submenus to open forms with additional information. For more information about topology maps, see the 5620 SAM User Guide.
Page 203: Interpreting Map Status Indicators
The color of the upper right corner of the topology group icon indicates the aggregated link status of the links in the topology group. (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD...
Page 204: Troubleshooting Alarms Using Topology Maps
Purple indicates that a physical link is being diagnosed. Red indicates that the link is out of service or failed. (2 of 2) Table lists icon symbols and colors for 5620 SAM alarms. Table 5-4 Map alarm status indicators Map icon Alarm...
Page 205: Procedure 5-1 To Monitor Alarm Status On Maps
Click on the Properties button. The property form for the selected object opens. Click on the Faults tab button. The Faults tab form opens. View alarm status and diagnose the problem, as described in chapter 3. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723...
Page 206 5 — Troubleshooting using topology maps Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 207 9 — Troubleshooting 5620 SAM clients 10 — Troubleshooting 5620 SAM server issues 11 — Troubleshooting the 5620 SAM database 12 — 5620 SAM client GUI warning message output 13 — Troubleshooting with Problems Encountered forms 14 — Troubleshooting with the client activity log Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4...
Page 208 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 209: Sam Logviewer
5620 SAM LogViewer 6.1 5620 SAM LogViewer overview 6.2 LogViewer GUI 6.3 LogViewer CLI 6.4 LogViewer GUI procedures 6.5 LogViewer CLI procedures 6-15 Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 210: Sam Logviewer Overview
Automatically send a notification when a specified type of entry is logged. LogViewer is available on 5620 SAM main and auxiliary servers as a GUI and a CLI application. The GUI is more fully featured than the CLI, which is designed for use on a character-based console over a low-bandwidth connection, such as during a Telnet session.
Page 211: Logviewer Gui
A log tab that displays dynamic log updates also has a tool bar for common operations. Figure shows the LogViewer GUI with multiple open logs and describes the tool bar buttons on a tab that displays a currently active log. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD...
Page 212 You can open a tab to list static log entries, such as the contents of an archived log or a snapshot of entries from an active log, and can pause the updates to active logs. The GUI also includes a text-search function. Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4...
Page 213: Logviewer Cli
Log in to the 5620 SAM server as an administrator. Note — If the 5620 SAM server is installed on Solaris, you must log in as the samadmin user. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4...
Page 214 6 — 5620 SAM LogViewer Perform one of the following. If the 5620 SAM server is installed on Solaris, run the following script: path/nms/bin/logviewerui.bash where path is the 5620 SAM server installation location, typically /opt/5620sam/server If the 5620 SAM server is installed on Windows, run the following script: path\nms\bin\logviewerui.bat...
Page 215 Specify a text string to search for using the text field and search options on the form. Note — The LogViewer Find function does not support the use of regular expressions. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723...
Page 216 Log→Remove Selected Filters, or click on the Remove filter button in the main tool bar. If the log display is static, such as for an archived log or the result of a Find All operation, go to step 21. Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 217 The log entry lines are synchronized by timestamp. Dynamic log updates to each log are displayed as they occur. Blank entry lines serve as spacers to preserve the chronological order of the combined log entries. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010...
Page 218: Procedure 6-2 To Configure The Logviewer Application Using The Gui
Choose Edit→Options→General from the LogViewer main menu, or click on the Application options button in the main tool bar. The Options form opens with the General tab displayed. 6-10 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 219 Base File Messages Directory—Click in the parameter field and use the browser • form that opens to specify the base 5620 SAM log directory. Default Log Pattern—Edit this parameter to specify a regular expression that •...
Page 220: Procedure 6-3 To Manage Filters Using The Gui Filter Manager
Oracle Location—specifies the base 5620 SAM Oracle installation directory • • NMS Root—specifies the nms directory under the base 5620 SAM server installation directory Click on the Advanced tab to configure the parameters related to LogViewer performance. Caution — The parameters on the Advanced tab typically require configuration only when LogViewer has performance problems.
Page 221 Choose Log→Create from Selected from the LogViewer main menu, or click on the Create from entry button in the main tool bar. The Add Filter form opens and is populated with the current log-entry field values as match criteria. Alcatel-Lucent 5620 Service Aware Manager, Release 6-13 8.0 R4 Aug 2010...
Page 222: Procedure 6-4 To Specify A Plug-In Using The Logviewer Gui
If you choose the Bring to Front plug-in, perform the following steps. Specify a regular expression as a match criterion in the Message Filter field. Go to step 8. 6-14 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 223: Logviewer Cli Procedures
Perform this procedure to start the LogViewer CLI application and view one or more logs. Log in to the 5620 SAM server as an administrator. Note — If the 5620 SAM server is installed on Solaris, you must log in as the samadmin user. Alcatel-Lucent 5620 Service Aware Manager, Release 6-15 8.0 R4...
Page 224 Table options is one or more of the options listed in Table parameter is a parameter listed in Table If the 5620 SAM server is installed on a Windows PC, run the following script: path\nms\bin\logviewer.bat argument options parameter ↵ where...
Page 225 To view a log in the list, enter the name of a log at the prompt and press ↵. To view a log that is not listed, perform the following steps. Enter the following at the prompt: other ↵ The following prompt is displayed: Alcatel-Lucent 5620 Service Aware Manager, Release 6-17 8.0 R4 Aug 2010 3HE 05723...
Page 226 Enter a name for the filter and press ↵. The following prompts are displayed in sequence: Level: Logger: Thread: Timestamp: Message: 6-18 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 227 To reset the statistics counters for the current LogViewer session, perform the following steps. Press ↵ to enter command mode. Enter the following at the prompt: reset ↵ Alcatel-Lucent 5620 Service Aware Manager, Release 6-19 8.0 R4 Aug 2010 3HE 05723...
Page 228: Procedure 6-6 To Configure The Logviewer Cli
The following prompt is displayed: log-include> Enter the following at the prompt: add ↵ The following prompt is displayed: File Name (full path)? 6-20 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 229: Procedure 6-7 To Specify Plug-Ins Using The Cli
Perform this procedure to specify a plug-in for the current LogViewer CLI session. Open the LogViewer CLI. Press ↵ to enter command mode. Enter the following at the root prompt: plugin ↵ Alcatel-Lucent 5620 Service Aware Manager, Release 6-21 8.0 R4 Aug 2010 3HE 05723...
Page 230 You may be prompted for plug-in configuration information. Supply the information, as required. Note — The currently available plug-ins and the associated configuration options are described in Procedure 6-4. 6-22 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723...
Page 231: Troubleshooting Network Management Lan Issues
7 — Troubleshooting network management LAN issues 7.1 Troubleshooting network management domain LAN issues Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 232: Troubleshooting Network Management Domain Lan Issues
For information about network planning expertise, contact your Alcatel-Lucent technical support representative. See the 5620 SAM Planning Guide for more information about the bandwidth requirements. When you are using in-band management, ensure that the network devices used to transport the management traffic are up.
Page 233 LAN congestion may be a problem. Contact your IT department or check physical LAN connectivity according to your company policy. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010...
Page 234: Functions Are Unavailable
MTU or the devices are not configured to forward fragmented packets, causing resynchronizations to fail. The 5620 SAM-managed devices are configured to send SNMP packets of up to 9216 bytes. The 5620 SAM is typically configured to accept large SNMP packets.
Page 235 Verify that large packets can travel from the managed devices to the 5620 SAM • by using CLI to ping the IP address of the 5620 SAM server, with a large packet. Ensure that the firewalls between the managed devices and the 5620 SAM •...
Page 236 7 — Troubleshooting network management LAN issues Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 237: Troubleshooting Solaris And Windows Platforms
8 — Troubleshooting Solaris and Windows platforms 8.1 Troubleshooting Solaris platforms 8.2 Troubleshooting Windows platforms Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 238: Troubleshooting Solaris Platforms
Provide the data collected in this procedure. You can also perform other procedures: • If you are you performing a large listing operation using the 5620 SAM client GUI or OSS, check the LAN throughput using the netstat command, as described in Procedure 9-3.
Page 239 Spins on mutexes (lock not acquired on first try) if the smtx number increases sharply, for instance from 30 to 300, a system resource bottleneck is indicated (1 of 2) Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723...
Page 240 You can determine whether a machine is disk or I/O bound using the iostat command. You can also perform the following procedures: Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4...
Page 241 To collect data to determine whether there is a disk bottleneck, type: iostat -x time ↵ where time is the time, in seconds, over which you want to collect data. Alcatel-Lucent recommends that you start with 2 s. To stop the iostat command, press CTRL-C.
Page 242: Platform
To collect data, type: vmstat s ↵ where s is the time, in seconds, over which you want to collect data. Alcatel-Lucent recommends that you start with 2 s. Review the vmstat output. The following is a sample of vmstat data. See Table for a description of the vmstat report.
Page 243 Contact your technical support representative for information about adding new disks to provide the necessary swap space to stop memory bottlenecks. Perform Procedure to add emergency swap space to provide a temporary solution. Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD...
Page 244: The Solaris Platform Is Disk Bound
Use a text editor, such as vi or textedit, to edit the vfstab file by typing: vi /etc/vfstab ↵ Move the cursor to the last line in the vfstab file and type: Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4...
Page 245: Troubleshooting Windows Platforms
Troubleshooting Windows platforms Many of the commands in section and throughout the rest of the 5620 SAM Troubleshooting Guide can also be performed on a Windows platform PC. In all cases, the commands are run from the DOS command line. As well, you can check PC performance and running process details using the Task Manager.
Page 246 8 — Troubleshooting Solaris and Windows platforms 8-10 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 247: Troubleshooting 5620 Sam Clients
9 — Troubleshooting 5620 SAM clients 9.1 Troubleshooting common client application problems 9.2 Troubleshooting client GUI issues 9-12 Alcatel-Lucent 5620 Service Aware Manager, Release 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 248: Troubleshooting Common Client Application Problems
PC client • If the 5620 SAM client is installed on UNIX or Solaris and you receive a “Cannot execute” message when you try to run the client, the client executable file permission may have been reset by an event such as an auto-client update failure.
Page 249 Log on to the 5620 SAM server station as an administrative user. Note — If the 5620 SAM server is installed on Solaris, you must log in as the samadmin user. Open a console window.
Page 250: With 5620 Sam Server
Firewalls between the 5620 SAM clients and the server are correctly configured • To check that the 5620 SAM client points to the correct IP address and port of the server, open the nms-client.xml file using a text editor. The default file location is installation_directory/nms/config.
Page 251 -i s ↵ where s is the time, in seconds, over which you want to collect data. Alcatel-Lucent recommends that you start with 50 s Review the output. The following is sample netstat output:...
Page 252: Nm Client
To stop the netstat command, press CTRL-C. Check that the client platform is appropriately sized. See the 5620 SAM Planning Guide for more information. Procedure 9-4 Problem: Cannot view 5620 SAM alarms using 5620 NM client Possible causes include incorrectly configured param.cfg parameters on the 5620 NM to...
Page 253: Procedure 9-5 Problem: Unable To Print From Solaris Platform Client
9 — Troubleshooting 5620 SAM clients Procedure 9-5 Problem: Unable to print from Solaris platform client Printers are connected to clients to provide a printed record of alarms, the GUI, or text files. Note — Many printers have Ethernet connections. Troubleshooting these printers is beyond the scope of this document.
Page 254: Managed State
Possible causes are: a corrupt or incorrectly entered 5620 SAM server license key • the 5620 SAM server license key is not for the correct hostid • • the number of managed cards (MDAs) exceeds the 5620 SAM server license another application using a port required by the 5620 SAM server •...
Page 255: Configuration, But I Cannot See Any Results
Suspend Retries or Resume Retries button. You can clear a deployment by clicking on the Clear button. When you clear a deployer, no further attempt is made to reconcile the network device status with the 5620 SAM database. Affected objects should be resynchronized.
Page 256 Attribute: alarmClassTag Value: generic.DeploymentFailure The alarm also contains additional information, including the object affected by the alarm and the severity of the alarm. See the 5620 SAM-O OSS Interface Developer Guide for more information. Find the following text in the alarm: Attribute: requestID=requestID The parameter specifies the request id sent with the original request.
Page 257: Procedure 9-8 Problem: Device Configuration Backup Not Occurring
9 — Troubleshooting 5620 SAM clients Procedure 9-8 Problem: Device configuration backup not occurring Use the 5620 SAM client to check the device database backup settings. Choose Administration→NE Maintenance→Backup/Restore from the 5620 SAM main menu. The Backup/Restore form opens with the Backup/Restore Policy tab displayed.
Page 258: Troubleshooting Client Gui Issues
Procedure 9-10 Problem: Configuration change not displayed on 5620 SAM client GUI The 5620 SAM supports the configuration of certain complex objects, such as services, using a sequence of configuration forms and steps or templates. Additional configuration forms and steps may be contained within the main, or parent, configuration form.
Page 259: Complete
Alcatel-Lucent recommends that you use filters to restrict the number of items in a list or search operation to 10 000 or fewer. See the 5620 SAM User Guide for information about the 5620 SAM client GUI list and search functionality. See the 5620 SAM Planning Guide for information about 5620 SAM scalability and system capacity guidelines.
Page 260: Sam Client Gui
Procedure 9-14 Problem: Cannot open user documentation from 5620 SAM client GUI When the 5620 SAM client GUI cannot find a browser to launch the user documentation index file, it generates an error message indicating that no browser is available. There are multiple ways to fix this problem.
Page 261: Procedure 9-15 Problem: The 5620 Sam Client Gui Does Not Display Ne User Accounts Created, Modified, Or Deleted Using The Cli
NE user accounts created, modified, or deleted using the CLI When a NE user account is created, modified, or deleted using the CLI, the 5620 SAM client GUI does not update the user list in the NE User Profiles form. For increased security, the node does not send a trap for changes made to node user accounts.
Page 262 9 — Troubleshooting 5620 SAM clients 9-16 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 263: Troubleshooting 5620 Sam Server Issues
10 — Troubleshooting 5620 SAM server issues 10.1 Troubleshooting 5620 SAM server issues procedures 10-2 Alcatel-Lucent 5620 Service Aware Manager, Release 10-1 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 264: Of 5620 Sam Server Status
5620 SAM license capacity • Log in to the 5620 SAM server as an administrator. Note — If the 5620 SAM server is installed on Solaris, you must log in as the samadmin user. Open a console window. To check the status of a 5620 SAM main server, perform the following steps.
Page 265 10 — Troubleshooting 5620 SAM server issues If the 5620 SAM main server is installed on Windows, enter the following at the CLI prompt: path\nms\bin\nmsserver.bat appserver_status ↵ where path is the 5620 SAM server installation location, typically C:\5620sam\server The general 5620 SAM server application status is displayed.
Page 266 10 — Troubleshooting 5620 SAM server issues Option Description nms_info Returns the following information from the 5620 SAM database: • number of managed devices by device type; for example, 7750 SR • number of MDA ports by type • number of equipped ports by type •...
Page 267 10 — Troubleshooting 5620 SAM server issues To check the status of a 5620 SAM auxiliary server, perform the following steps. Enter the following at the CLI prompt: path/nms/bin/auxnmsserver.bash aux_status ↵ where path is the 5620 SAM server installation location, typically opt/5620sam/auxserver The general 5620 SAM server application status is displayed.
Page 268: Communicating
Verify that the database is running in the correct mode. • See the 5620 SAM Planning Guide for more information about the ports that must be available for the 5620 SAM to function. If the problem persists, collect the logs identified in Procedure and contact your Alcatel-Lucent support representative.
Page 269: Messages
See chapter for more information. Verify that the 5620 SAM server and client clocks are synchronized. To set the date and time for 5620 SAM server and client clocks, see the 5620 SAM Maintenance Guide for more information.
Page 270: Response Time
As the number of managed devices grows and as more GUI or OSS clients are brought online, the processing load on the 5620 SAM system increases. For optimum 5620 SAM performance, you must ensure that the 5620 SAM configuration meets the requirements in the 5620 SAM Planning Guide as your network expands.
Page 271: Or Alarm Performance Is Degraded
Caution — Exceeding the alarm limit configured in the nms-server.xml file may cause system performance problems. Check the status bar of the 5620 SAM client GUI status bar for indications that the maximum number of alarms for the system is reached.
Page 272: Procedure 10-8 Problem: All Snmp Traps From Managed Devices Are Arriving At One 5620 Sam Server, Or No Snmp Traps Are Arriving
5620 SAM server, or no SNMP traps are arriving When you install the 5620 SAM server, you specify the port on which SNMP traps arrive. In addition, two sets of configurations must be completed for SNMP trap notifications to work: •...
Page 273: Or Device Resynchronization Fails
5620 SAM. Check the license-key status. The 5620 SAM generates an alarm when a license limit is exceeded or nearly exceeded. View the dynamic alarm list on the 5620 SAM client GUI, or the JMS real-time alarm feed from the 5620 SAM OSS client application for alarms related to nearing or exceeding a license limit.
Page 274 For resynchronization issues that may be caused due to insufficient MIB polling intervals. Choose Administration→Mediation from the 5620 SAM main menu. The Mediation (Edit) form opens with the General tab selected. Ensure that the Polling Admin State is Up.
Page 275: Network Devices
When 5620 SAM performance is slow, especially when performing network device resynchronizations, SNMP and IP performance along the in-band or out-of-band interfaces between the network device and the 5620 SAM server may be the problem. Check the following: configuration of the LAN switch port and the 5620 SAM PC or workstation port •...
Page 276: Procedure 10-12 Problem: Statistics Are Rolling Over Too Quickly
OSS application requests data from the statistics tables less frequently • than the configured roll over interval FTP must be enabled on the managed device in order for the 5620 SAM to • retrieve statistics. Alcatel-Lucent recommends that statistics collection planning includes the following considerations to prevent the loss of statistics data.
Page 277 10 — Troubleshooting 5620 SAM server issues Open a command tool on the 5620 NM. Navigate to the AS IM directory on the 5620 NM by typing: /opt/netmgt/ALMAP/as/data/ascurim_0 ↵ Open the param.cfg file. Set the NSP_USE_NSP parameter to True. Ensure that the following param.cfg file parameters are configured to True: DROP_FREE_ALARMS •...
Page 278 10 — Troubleshooting 5620 SAM server issues 10-16 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 279: Troubleshooting The 5620 Sam Database
11 — Troubleshooting the 5620 SAM database 11.1 Database troubleshooting 11-2 Alcatel-Lucent 5620 Service Aware Manager, Release 11-1 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 280: Procedure 11-1 Problem: My Database Is Running Out Of Disk Space
Alcatel-Lucent technical-support representative for information about deleting archived log files. Perform a database backup using the 5620 SAM client GUI, as described in the 5620 SAM User Guide, or using the 5620 SAM database installer, as described in the 5620 SAM | 5650 CPAM Installation and Upgrade Guide.
Page 281: Creating Database Performance Issues
Overscheduling the number of database backups may affect database performance, as the PC or workstation uses system resources to create the backups. On a 5620 SAM client GUI, choose Administration→Database from the 5620 SAM main menu. The Database Manager form appears.
Page 282: Procedure 11-4 Problem: I Need To Restore A Database
Remove the existing database: Launch the database uninstaller to remove the existing database instance and follow the prompts, as described in the 5620 SAM | 5650 CPAM Installation and Upgrade Guide. Restart the PC or workstation as prompted by the uninstaller.
Page 283: Backup Sets Error
11 — Troubleshooting the 5620 SAM database Run the database installer, as described in the 5620 SAM | 5650 CPAM Installation and Upgrade Guide. Choose the options to specify a database restore: choose the restore a database from backup option •...
Page 284: Procedure 11-7 Problem: Primary Or Standby Database Is Down
Procedure 11-7 Problem: Primary or standby database is down The status bar of the 5620 SAM client GUI indicates that the primary or standby database is down. Warning — Performing database modifications using Oracle database tools can cause irreparable harm to the database and your network management data, and can void your Alcatel-Lucent warranty or support agreement.
Page 285: Listener Services Are Started
If you are unsure of the status of Oracle database and listener services, perform the following. Ensure that the database configuration is correct, as specified in the 5620 SAM | 5650 CPAM Installation and Upgrade Guide Perform one of the following actions. On Windows PCs: Choose Start→Settings→Control Panel→Administrative...
Page 286 The following sample shows the output of the proxy_status option. Proxy is UP The following sample shows the output of the db_version option. 5620 SAM Version 8.0 R1 - Built on Wed Apr 21 03:14:15 EST 2010 11-8 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4...
Page 287: Sam Client Gui Warning Message Output
12 — 5620 SAM client GUI warning message output 12.1 5620 SAM client GUI warning message overview 12-2 12.2 Responding to 5620 SAM client GUI warning messages 12-5 Alcatel-Lucent 5620 Service Aware Manager, Release 12-1 8.0 R4 Aug 2010 3HE 05723...
Page 288: Sam Client Gui Warning Message Overview
When an error condition is encountered that the 5620 SAM client has not anticipated, a Problems Encountered window is displayed. See section 13.1 for more information.
Page 289: Additional Information Required
12 — 5620 SAM client GUI warning message output Additional information required When the value selected for a parameter has a that requires another parameter to be configured, a warning message indicates the missing information that is required. For example, when you configure a new or existing user with MD5 or SHA as the value for the Authentication Protocol parameter, a password must be configured.
Page 290: Service Disruption Warning
12 — 5620 SAM client GUI warning message output Changes entered in the sub-form are not committed until you click on the OK or Apply button of the parent form. When you click on the OK or Apply button of the parent form, a final confirmation is displayed, as shown in Figure 12-4.
Page 291: Duplicate Configuration Form Conflicts
12 — 5620 SAM client GUI warning message output Verify that the requested action is appropriate. Click on the checkbox beside the statement “I understand the implications of this action” to continue with the action. Duplicate configuration form conflicts There are multiple ways to access a configuration form for the same object. For example, you can view the configuration form for a port by choosing Manage→Equipment, or you can access the port from the Application→Equipment...
Page 292 12 — 5620 SAM client GUI warning message output Correct the problem based on the information provided. For the example in Figure 12-8, configure the authentication order parameters. If you cannot correct the problem and continue to get the same warning message: Check the documentation to ensure that you are following the steps correctly.
Page 293: Troubleshooting With Problems Encountered Forms
13 — Troubleshooting with Problems Encountered forms 13.1 Problems Encountered form overview 13-2 13.2 Using Problems Encountered forms 13-3 Alcatel-Lucent 5620 Service Aware Manager, Release 13-1 8.0 R4 Aug 2010 3HE 05723 AAAD TQZZA Edition 01 Troubleshooting Guide...
Page 294: Problems Encountered Form Overview
The information may not be enough for you to correct the problem. The information can be used by your technical support representative to help resolve the problem. 13-2 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide...
Page 295: Using Problems Encountered Forms
Procedure 13-2. Click on the Close button to close the details window. If there is more than one problem, repeat steps to 4. Click on the Close button. Alcatel-Lucent 5620 Service Aware Manager, Release 13-3 8.0 R4 Aug 2010 3HE 05723...
Page 296: Support
For example, if you were trying to create a VLL service, record the details about the service that you were trying to create. Record the appropriate problem information, as described in section 1.3. Collect logs for your Alcatel-Lucent support representative, as described in Procedure 2-1. 13-4...
Page 297: Troubleshooting With The Client Activity Log
14 — Troubleshooting with the client activity log 14.1 The 5620 SAM Usage and Activity Records overview 14-2 14.2 Using the 5620 SAM Usage and Activity Records forms 14-4 Alcatel-Lucent 5620 Service Aware Manager, Release 14-1 8.0 R4 Aug 2010...
Page 298: The 5620 Sam Usage And Activity Records Overview
Table 14-1 describes the types of logs available in the 5620 SAM Usage and Activity Records form. Table 14-1 Log types available in the 5620 SAM Usage and Activity Records form Log name Description Database Log To view information about changes to the database...
Page 299 XML format. (Filtered lists of log entries can also be retrieved through the 5620 SAM-O interface.) You can use the XML log data as an archive mechanism or statistical analysis method. See the 5620 SAM-O OSS Interface Developer Guide for more information.
Page 300: Using The 5620 Sam Usage And Activity Records Forms
Violation of user permissions through the XML OSS interface Note The 5620 SAM also raises an alarm for log entries that are related to security. 14.2 Using the 5620 SAM Usage and Activity Records forms The following procedures describe how to use the 5620 SAM Usage and Activity Records form to correlate user requests and deployment activity.
Page 301: Problem
Use the filter in the User Request Log (userlog) to list the requests for the request ID that you obtained in step 6. The 5620 SAM displays the filter results in the Userlog display area. The Operation Source column identifies the user associated with the failed deployment.
Page 302: Request
Use the filter in the Deployment Log (userlog) to list the deployment results associated with the request ID that you obtained in step 4. The 5620 SAM displays the search results. Identify whether the user action resulted in a successful network deployment by reviewing the status of the Result column.
Page 303 You can perform other functions, such as displaying a count of the records or saving the records to a file for post-processing purposes, by right-clicking on a column heading and choosing an option from the contextual menu. Close the 5620 SAM Usage and Activity Records form. Alcatel-Lucent 5620 Service Aware Manager, Release 14-7 8.0 R4...
Page 304 14 — Troubleshooting with the client activity log 14-8 Alcatel-Lucent 5620 Service Aware Manager, Release Aug 2010 8.0 R4 Troubleshooting Guide 3HE 05723 AAAD TQZZA Edition 01...
Page 305: Technical Support
Customer documentation and product support Customer documentation http://www.alcatel-lucent.com/myaccess Product manuals and documentation updates are available at alcatel-lucent.com. If you are a new user and require access to this service, please contact your Alcatel-Lucent sales representative. Technical Support http://support.alcatel-lucent.com Documentation feedback...

Alcatel-Lucent 5620 Troubleshooting Manual

Preface

Troubleshooting Overview

1 Troubleshooting Process

5620 SAM Troubleshooting

Troubleshooting the Managed Network

3 Troubleshooting Using Network Alarms

4 Troubleshooting Services and Connectivity

5 Troubleshooting Using Topology Maps

6 SAM Logviewer

7 Troubleshooting Network Management LAN Issues

8 Troubleshooting Solaris and Windows Platforms

9 Troubleshooting 5620 SAM Clients

12 - 5620 SAM Client GUI Warning Message Output

10 - Troubleshooting 5620 SAM Server Issues

13 - Troubleshooting with Problems Encountered Forms

14 - Troubleshooting with the Client Activity Log

Quick Links

Troubleshooting

Related Manuals for Alcatel-Lucent 5620

Summary of Contents for Alcatel-Lucent 5620

Table of Contents