戻る
-
タイトル
Is it possible to monitor the health state of a Safeguard Appliance using a web page? -
説明
Does Safeguard have a web page that can be monitored by a load balancer (For example F5) for health states in case the appliance is unavailable or in maintenance mode?
Is there a recommended API endpoint to monitor for load balancer health? -
対策
Safeguard has a Notification Service API that can be accessed via the following URL:
SPP 6.13.1 or below:https://ip_address/service/notification/v3/Status/State
or
SPP 7.0 and above:https://ip_address/service/notification/v4/Status/State
The following table lists the appliance states and what actions are available when the appliance is in a particular state.Appliance state and description Actions available EnrollingReplica (Only applies to replica appliances in a cluster.)A transitional state where a replica appliance is being added to a cluster and is not available for access. From this state, the appliance goes into Maintenance mode to complete the enroll operation.Wait for operation to complete before logging into appliance.InitializingA transitional state where the appliance is initializing to start, but is not yet available for access.Wait for operation to complete before logging into appliance.MaintenanceAppliance is performing maintenance tasks and is not available for access.Wait for maintenance tasks to complete before logging into appliance.LeavingCluster (Only applies to replica appliances in a cluster.)A transitional state where a replica appliance is being unjoined from a cluster and is not available for access. From this state, the appliance goes into Maintenance mode to complete the unjoin operation.Wait for operation to complete before logging into appliance.OfflineAppliance is not available for access.Wait for appliance to come back online before logging in. OfflineAppliance is not available for access.Manually enable Offline Workflow mode. Once online operations are resumed, the appliance is returned to Maintenance mode. For more information, see Enable offline workflow.OnlineThe appliance is a primary and has consensus. Or the appliance is a replica and has both consensus and connectivity to the primary.Log into appliance.In this state, access request workflow is available from all clustered appliances that are online and able to communicate.PatchPending (Only applies to replica appliances in a cluster.)Upon cluster patch, the primary appliance instructs all replicas to enter PatchPending state. The primary appliance then patches and upon completion, instructs the PatchPending replicas to install the patch one at a time.You can log into a replica with a PatchPending state.You can initially perform access request workflow on a replica in PatchPending state; however, during the cluster upgrade, when the majority of the cluster members have upgraded, access request worklfow migrates from the PatchPending side of the cluster to the upgraded side of the cluster. During this time, access request workflow is unavailable on any appliance still in the PatchPending state.PrimaryNoQuorum (Only applies to the primary appliance in a cluster.)The primary appliance is in a Read-only mode while attempting to get the lease, but can't because the cluster does not have consensus. The appliance continues to attempt getting the lease and when it does, the appliance state goes back to Online.If the appliance is powered on, you can log into an appliance with a PrimaryNoQuorum state; however, it will be in a Read-only mode.In this state, access request workflow is not available from the primary appliance, but may be available from other appliances in the cluster.For example, if the primary cannot communicate with the rest of the nodes in the cluster, but the rest of the nodes can communicate between themselves (ReplicaWithQuorum state), then access request workflow will be available from these replica appliances even though it is not available from the primary appliance.QuarantineAppliance is broken or in an unknown state.Requires manual intervention to recover.Go to recovery kiosk to recover. For more information, seeRecovery kiosk.ReplicaDisconnected (Applies to replica appliances in a cluster.)A replica appliance is available for access; however, both of the following conditions apply:
- The replica appliance cannot communicate with the primary appliance in the cluster and
- The remaining nodes in the cluster that the replica appliance can communicate with do not have consensus.
You can log into a replica with a ReplicaDisconnected state, but access request workflow is disabled.If the replica appliance cannot communicate with the other nodes in the cluster, but the remaining nodes can communicate with each other, then access request workflow will be available from those appliances even though it is not available from the appliance that cannot communicate with them.ReplicaNoQuorum (Applies to replica appliances in a cluster.)A replica appliance can communicate with the primary appliance; however, the remaining nodes in the cluster do not reach consensus. Once the cluster regains consensus, the replica appliance will go into the Online state.You can log into a replica with a ReplicaNoQuorum state, but access request workflow is disabled.In this state, access request workflow is not available from the primary appliance, but may be available from other replicas.For example, in a cluster of five appliances, if the primary and a single replica cannot communicate with the remaining replicas in the cluster, but the other three replicas in the cluster can communicate between themselves (ReplicaWithQuorum state), then access request workflow will be available from the replicas that are online and communicating even though it is not available from the primary and replica that cannot communicate.ReplicaWithQuorum (Applies to replica appliances in a cluster.)A replica appliance cannot communicate with the primary appliance; however, the remaining nodes in the cluster have reached consensus.You can log into a replica with a ReplicaWithQuorum state. In this state, access request workflow is available from any clustered appliance that is online and able to communicate. TransitioningToPrimary (Only applies to replica appliances in a cluster.)A transitional state where a replica appliance is being promoted to be the new primary and is not available for access.Wait for operation to complete before logging into appliance.TransitioningToReplica (Only applies to the primary appliance in a cluster.)A transitional state where a primary appliance is being demoted to a replica and is not available for access.Wait for operation to complete before logging into appliance.ShuttingDownA transitional state where an appliance is shutting down and is not available for access.Wait for operation to complete before logging into appliance.StandaloneReadOnlyState used for replicas unjoined from a cluster or a primary appliance restored from a backup. The appliance can be activated.Log into appliance.See Activating a read-only appliance for how to activate a Read-only appliance so you can add, delete and modify data, apply access request workflow, and so on.UnknownAppliance is broken or in an unknown state.Requires manual intervention to recover.Go to recovery kiosk to recover. For more information, see Recovery kiosk.