1   | 
 Check for deployment failures. Deployment failures indicate that communication with a managed NE is failing. 
- 
Choose Administration→NE Maintenance→Deployment from the NFM-P main menu. The Deployment form opens.  
- 
Click Search to display the latest information. 
When no failed deployments are listed, deployment problems are not causing a synchronization issue.  
- 
If deployments are listed, view the state of a deployment in the State column. The possible deployment states include: 
- 
Canceled  
- 
Deployed  
- 
Failed (Configuration). Failure occurred because the configuration could not be applied to the specified objects.  
- 
Failed (Internal Error). Failure occurred due to general error conditions. The state is intended for all other possible errors.  
- 
Failed (Partial). Failure occurred at deployment and some of the configuration may have been sent to the network.  
- 
Failed (Resource Unavailable). Failure occurred because one of the resources required to apply the configuration is not in the main database.  
- 
Not Deployed  
- 
Pending  
- 
Postponed    
- 
Identify the source of the deployment problem. For example, for a Failed configuration state, ensure the configuration was performed correctly on the client GUI.   
  |