Troubleshooting guide
9 — NE maintenance
Alcatel-Lucent 5620 Service Aware Manager 9-55
5620 SAM
System Administrator Guide
3 Navigate the file system as required. Perform one of the following actions to open
a directory and list the contents:
a Double-click on the directory row in the list.
b Select the directory row and press <CTRL>O.
c Type the path to the directory in the Path field and click Go.
4 If you opened the browser using the 5620 SAM main menu or from the Software
Upgrade form, you can browse another NE file system using the same form, if
required.
i Click Disconnect to end the browsing session.
ii Enter the IP address of the NE that you need to browse in the field at the top
of the form and click Connect.
5 Close the form.
Procedure 9-37 To troubleshoot a failed configuration deployment
The 5620 SAM continues to retry deployments after a failed or incomplete deployment
attempt, based on the 5620 SAM deployment policy, as configured in Procedure 9-2.
When there is a deployment error, a number of problems can occur. For example:
• The 5620 SAM database may lose synchronization with the device database.
• Configuration changes requested using the client GUI may clash with
configuration changes, retries, and recovery applications developed by an OSS
system using the 5620 SAM-O interface or by an operator using a CLI.
When a failed or incomplete deployment or a failed SNMP configuration request occurs,
a Problems Encountered form appears automatically, displaying error information
about the failure(s).
For example, view detailed information on a failed deployment:
Select a failed deployment entry and click Properties. An error form opens.
Click Details to view detailed diagnostic information about the failure(s).
Click View Affected Object. An object properties form opens, in which you can navigate
to the object which caused the failure.
Note 1 — The Request Id and Task Name fields on the Problems
Encountered form can be used for troubleshooting using the Task
Manager application.
Note 2 — The Problems Encountered form can also appear for
non-deployment generated errors.
Release 13.0 R2 | May 2015 | 3HE 09815 AAAB TQZZA Edition 01