The Netprobe behaviour and configuration follows specific behaviours, depending on its Gateway connection.
Disconnection behaviour Copied
If a Gateway to self-announcing Netprobe (SAN) connection is disconnected, either due to network failure or one party dropping the connection for one of the reasons stated above, then the following rules apply:
- The Netprobe waits a configurable timeout for the Gateway (or a hot-standby Gateway) to reconnect. Once this timeout is exceeded, the SAN reverts to polling all the Gateways specified in its Setup File and look for another Gateway to announce itself to.
- If a connection is disconnected, then the Gateway keeps the SAN in its directory for a configurable timeout, and attempts to reconnect. Once this timeout is exceeded, the Gateway removes the SAN from the live directory and ceases attempting to connect to it.
- If a connection is rejected by the Netprobe, then the Gateway immediately removes the Netprobe from the live directory and ceases attempting to connect to it.
Disassociate Probe Command Copied
The Disassociate Probe command can be used to remove a SAN from a Gateway. This command is available on SANs with a connection status that is not
Only use this command when a SAN has failed, or has moved to another Gateway but the original Gateway was not notified. This can happen when there is a load-balancer between the SAN and the Gateway, or the connection was suspended.
CautionIf the SAN is up when this command is used, it may connect to a different Gateway. If the SAN does connect to a different Gateway, any snooze or user assignment information is lost.
This command is not available on imported SANs.
Hot Standby Gateways Copied
Where Hot Standby Gateway pairs are used, both should be specified in the Netprobe Setup File. A non-active Gateway will refuse to accept the Netprobe so there is no risk of the Netprobe choosing a secondary Gateway while the primary is still up.