Problem: User performs action, such as saving a configuration, but cannot see any results

Causes

Possible causes are:

Steps
 
1 

For the NFM-P client, perform the following:

  1. Choose Administration→NE Maintenance→Deployment from the NFM-P main menu.

    The Deployment form opens. Incomplete deployments are listed, and deployer, tag, state and other information is displayed.

    The possible states for a deployment are:

    • Deployed

    • Not Deployed

    • Pending

    • Failed — Resource Unavailable. Failure occurred because one of the resources required to apply the configuration is not present in the NFM-P database

    • Failed — Configuration. Failure occurred because the configuration could not be applied to the specified objects

    • Failed — Partial. Failure occurred at deployment and some of the configuration can been sent to the network

    • Failed — Internal Error. Failure a occurred due to general error conditions. Code is intended as a catch-all code for all other possible errors

    • Cancelled

    • Postponed

    You can also suspend or resume deployment retries by clicking Suspend Retries or Resume Retries. You can clear a deployment by clicking Clear. When you clear a deployer, no further attempt is made to reconcile the network device status with the NFM-P database. Affected objects should be resynchronized.

    If a deployment is not sent to a managed device, the intended configuration change is not made on the device.

  2. Choose a failed deployment and click Properties to view additional information. The deployment properties form opens.

2 

When a deployment fails and you receive a deployment alarm, check the following steps:

  1. Using CLI, check on the device whether the deployment change is on the device.

  2. 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 NFM-P.

    If the change is not on the device, collect the information from the deployment properties form and contact your technical support representative.

3 

Note: These steps describe how to troubleshoot asynchronous deployment requests only. Nokia recommends that deployment requests be made in asynchronous mode.

For OSS clients, perform the following steps:

  1. 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 NSP NFM-P XML API Developer Guide for more information.

  2. 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.

  3. Determine the original request using the request id.

  4. 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 NSP NFM-P XML API Developer Guide for more information.

  5. 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

End of steps