Resynchronization of the automation adapter

If events to be forwarded to the automation adapter are lost during error situations, information about first-level automation resources that is collected by the end-to-end automation manager cannot be kept up to date.

As long as the asynchronous communication path from the primary agent to the automation adapter is available despite the error situation, the end-to-end automation manager is notified that the automation domain is offline. As soon as the end-to-end automation manager is informed that the domain is online again, the end-to-end automation manager has to request initial status information for all resources known by it in the affected automation domain. Such a resynchronization of the end-to-end automation manager with the first-level automation might cause increased traffic rate.

Error situations that the automation adapter has to be resynchronized after are:

• A stop or abend of the NetView INGPXDST communication task
• A recycle of the automation manager, when the start type is WARM or COLD. In case of a HOT restart, a resynchronization is only necessary if the outage took longer than two minutes or the time interval that is defined with the advanced automation option AOF_E2E_TKOVR_TIMEOUT.