Example 1: Configuring Retry Properties at the Network Element Instance Level

A specific vendor's network element often responds with a FUNCTION BUSY message, meaning that it cannot presently process commands and that the command should be retried at a later time (there is not necessarily any problem with the command itself, but the load on the network element is too large at this particular moment). Best practices dictate that a command will eventually succeed if tried 3 times with a 10 second interval between tries. To ensure that the command is properly retried, the service modeler should configure the retry properties at the network element instance level (see the following procedure). The work order will fail only if the configured Number of Retries is exceeded.

To configure retry properties at the network element instance level:

In the User Defined Exit Type editor, update the user-defined exit type configuration entry that corresponds to the FUNCTION BUSY response to specify an exit type of RETRY when this response message is encountered.
Modify the retry properties for any existing network element instances of that type.

To do this, update the retry values in the Network Element editor for each network element instance as follows:
- In the Number of Retries field, enter 3.
- In the Retry Interval field, enter 10. (seconds)
Modify the retry properties for any existing Dynamic NE Template used for network element instances of that type.

To do this, update the retry values in the Dynamic NE Template editor as follows:
- In the Number of Retries field, enter 3.
- In the Retry Interval field, enter 10. (seconds)
Ensure that all network element templates, network elements, and dynamic network element templates that were changed have been saved.

After saving, you can deploy the configuration to an ASAP environment for testing.