Workflow To Troubleshoot Your Network Using 5620 Sam - Alcatel 5620 Troubleshooting Manual

3
2.3

Workflow to troubleshoot your network using 5620 SAM

The following workflow correlates the tasks in the 5620 SAM Network Management
Troubleshooting Guide with the problem-solving model described in section 1.2.
1
2
Category
Network problem
Network management problem
3
Alcatel 5620 Service Aware Manager, Release 2.1 R2
May 2005 95-5887-01-00-B
Store the files in a secure location until they are sent to support, and ensure that the
files are not overwritten. For example, if there are two 5620 SAM clients with
troubleshooting issues, do not place the two nms-client.xml files in the same
directory because one of them will be overwritten. Rename the files, as appropriate,
to identify each 5620 SAM client.
Establish an operational baseline for your network. See the 5620 SAM Routine
Maintenance Procedures Guide for more information.
Categorize the problem. Table 2-1 describes the general categories that are
associated with troubleshooting 5620 SAM.
Table 2-1 5620 SAM general troubleshooting categories
Identify the root cause of the problem and plan corrective action.
a For a network problem, see:
i Section 3.2 for specific information about the workflow to investigate and
resolve alarm conditions on a network object or customer service.
2 — Troubleshooting using 5620 SAM
Category description
A operational issue with the network managed by 5620 SAM
Alarms raised on network objects and services
Problems on services with no associated alarms
Topology maps to view network health
A domain, connectivity, platform-related, or configuration
problem
Network management domain and LAN troubleshooting
Solaris and Linux platform troubleshooting
PC operating system issues
GUI and OSS client 5620 SAM software issues
5620 SAM and 5620 SAM-O server software issues
5620 SAM database and Oracle software issues
Warning messages related to configuration issues
Problems Encountered form detailing programming exceptions
Activity log forms detailing user, database, and deployment
history
2-5