Remote node states

Remote nodes can have one of the states in Table 6.1, “Remote node states”.

Table 6.1. Remote node states

StateDescription
UndiscoveredNode cannot be discovered. Network address information is not available from this remote node. Remote node is unavailable.
DiscoveredThe network address information for this node is discovered, either using dynamic or static discovery, but no connection could be established to the node. Remote node is unavailable.
In Up NotifierNode is transitioning to an Up state. This is a transitory state. Any installed node available notifiers are being executed.
UpActive connections are available to this node. Remote node is active.
In Down NotifierNode is transitioning to the Down state. This is a transitory state. Any installed node unavailable notifiers are being executed.
DownNode is inactive. No connections are active to this node, and new connection attempts fail with an error. Remote node is unavailable.
Duplicate LocationA duplicate location code was detected during connection establishment. No communication can occur with this node until this error is corrected. Remote node is unavailable.
Duplicate TimestampA duplicate installation time-stamp was detected during connection establishment. No communication can occur with this node until this error is corrected. Remote node is unavailable.
Unsupported ProtocolAn unsupported protocol version was detected during connection establishment. No communication can occur with this node until this error is corrected. Remote node is unavailable.

Remote node state change notifiers

Application installed node state change notifiers are called when a remote node transitions from active to unavailable and from unavailable to active. The In Up Notifier and In Down Notifier states defined in Table 6.1, “Remote node states” are seen when a node notifier is being called.

When a node state change notifier is installed, it is guaranteed to be called for all active remote nodes already discovered by the local node. Node notifier execution is serialized for a specific remote node. A call to a notifier must complete before another notifier is called. For example, if a remote node becomes unavailable while an active notifier is being executed, the unavailable notifier is not called until the active notifier completes.

Node state change notifiers are called in a transaction.