Post-discovery actions on discovered NEs

Overview

In a discovery rule, you can create and specify a post-discovery action to perform on the successfully discovered NEs included in the rule. The NFM-P performs the post-discovery action automatically at the end of rule execution.

A post-discovery action requires an NFM-P control script that manages the auto-configuration actions performed on discovered NEs.

For example, an operator specifies a control script as a post-discovery action in a discovery rule for a subnet. The control script co-ordinates the execution of device-specific child control scripts. The child control scripts call XML API scripts that each configure a group of discovered NEs, such as aggregation ring or IP backhaul NEs. After the NFM-P executes the discovery rule, it invokes the control script to auto-configure the successfully discovered NEs in the subnet.

Note: Because a post-discovery action is intended to be autonomous, the NFM-P displays an error message and halts a post-discovery action that requires user interaction.

Workflows could be used to perform post-discovery actions..

From the Managed State tab of the Discovery Manager form, you can do the following:

• List the post-discovery action associated with each managed NE.

• View the status of the script execution as it occurs.

• View the script run result.

The Node Discovery Control form of an NE displays additional information and allows post-discovery action management. See To manage a post-discovery action failure on an NE for more information.

Post-discovery action design considerations

The following conditions apply to post-discovery actions.

• The NFM-P performs no logic validation of the associated scripts.

• Deletion of the associated control script is blocked.

• After a discovery rule runs, the action is not automatically executed on new NEs that are added to the rule. To execute the action on the new NEs, you must rescan the network using the rule.

• An action is performed on an NE only when the Full Resync Status of the NE is Full Resync Done.

• If a device fails discovery, the action is not performed, and the script execution status is Not Executed. Resynchronization of the NE does not invoke the script or change the execution status.

• If the control script execution fails, an alarm is raised.

• After a post-discovery action is performed on an NE:

  • Unmanaging and remanaging the NE has no effect.

  • Deleting and rediscovering the NE causes the action to be performed on the NE.