9 — Troubleshooting 5620 SAM clients
9-10 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
2 When a deployment fails and you receive a deployment alarm, check the
following:
i Using CLI, check on the device whether the deployment change is on the
device.
ii If the change is on the device, the deployment alarm was likely raised
because the configuration already exists on the device. Clear the failed
deployment and resynchronize the device with the 5620 SAM.
If the change is not on the device, collect the information from the
deployment properties form and contact your Alcatel-Lucent support
representative.
3 For client OSS applications, perform the following:
i Browse real-time alarms received via JMS. An alarm denoting a deployment
failure contains the following text:
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.
ii Find the following text in the alarm:
Attribute: requestID=requestID
The parameter specifies the request id sent with the original request. The
request id should be unique per request.
iii Determine the original request using the request id.
iv Troubleshoot the original request. If there are problems with the original
request, clear the deployer, fix the request, and send the new request. See
the 5620 SAM-O OSS Interface Developer Guide for more information.
v If there are no problems with the original request, the failure may be caused
by a network communication or device failure, or by packet collisions caused
by conflicting configurations. You can:
• resend the request
• troubleshoot your network or device
Note — These steps describe how to troubleshoot asynchronous
deployment requests only. Alcatel-Lucent recommends that
deployment requests be made in asynchronous mode.
To Next Page
Loading...
