Example 2: Configuring Retry Properties at the Atomic Action Level

When trying to change the LEN on a specific vendor's network element, the network element responds with an INVALID STATE error message if the customer line is in use. In this scenario, best practices dictate that ASAP retry the atomic action 10 times with an interval of 300 seconds between each attempt before a failure is be generated. The following example demonstrates how the service modeler configures the retry properties at the atomic action level to meet this criteria.

In the User Defined Exit Type editor, update the user-defined exit type configuration entry that corresponds to the INVALID STATE response to specify an exit type of RETRY when this response message is encountered.
When examining this network element's retry requirement, there are two options that would support the requirement:
1. Modify the retry properties for the NE template (so that the configuration is carried over to any new network element instances that are created), for each network element instance of that type, and for each Dynamic NE template of that type.
2. Modify the retry properties for the specific service action (change LEN). In this example, assuming the change LEN atomic action is specific to the vendor equipment in question (either a common atomic action mapping to only one vendor and technology, or a vendor and technology-specific atomic action mapping to a single action processor), and assuming the retry behavior specified for this requirement is unique to the atomic action (change LEN), then simply update the retry properties for the atomic action.
  
  Note:
  Option a) requires multiple updates (to the NE Template, each network element instance, and each Dynamic NE Template). Option b) requires a single update.
Modify the retry properties for the change LEN atomic action.

Update the retry values in the Atomic Action editor as follows:
1. In the Number of Retries field, enter 10.
2. In the Retry Interval field, enter 300. (seconds)
Note:
To update the retry value in an editor field, activate the field by selecting the corresponding check box. Retry values have no digit limit but must be positive integers. Retry values can be 0 if overriding the ASAP.cfg configured retry values is required.
Save changes to atomic actions.

You can now deploy the configuration deployed to an ASAP environment for testing.