-
Title
What is the best way for a TPAM administrator to verify/monitor the health of a TPAM appliance? -
Description
What is the best way for a TPAM administrator to verify/monitor the health of a TPAM appliance?
What options are available from the product to monitor the HA clustering?It is possible to get the current status of the Primary / Replica console appliances?
-
Cause
-
Resolution
One method of checking the operational status of any TPAM appliance (2.2 through 2.5) is via the /status HTML page on each appliance, e.g.: https://ipaddress/status. This page updates every minute, and shows the current state of that specific appliance.
The various states are:
Cluster Role• Primary - Acts as the information source for the cluster. Only one primary allowed per cluster.• Replica - redundant appliance that is kept in synch with the primary. Can be configured to automatically fail over if it loses contact with the primary.• Standalone - this role only applies to DPAs enrolled in the cluster and cannot be changed.
Run Level
• Operational - TPAM is fully functional• Maintenance - In this mode users can only log on to the /admin and /config interfaces.
Appliance Status (Added in 2.5.920)• Active - Device is active in the cluster• Not Active - Device is ignored in replication
Replication Status
• Failed Over - a replica has lost contact with the primary in the cluster and the failover time out has expired.• Failing Back - a replica has re-established contact with the primary and the failback time out has expired.• Replicating - normal status for a healthy primary.• Standby - normal status for a healthy replica or a primary with no replicas defined.• Unknown - when you have added a new cluster member but not but not uploaded the enrollment bundle or when a TPAM appliance is restarted but has not gossiped yet.• Updating - Displayed when a replica is applying an update from the primary.
State
• Failed - appears when a cluster member has not gossiped within the last minute, but has prior gossip activity in the past.• Healthy - communicating with other cluster members.• Unknown - when you have added a new cluster member but not but not uploaded the enrollment bundle or when a TPAM appliance is restarted but has not gossiped yet.Below are examples of the data returned when connecting to the https://ipaddress/status page:
From a Failed Over Replica (i.e. Users can logon to the /tpam interface) :Appliance Name: TPAMCONSOLE_Replica Cluster Role: Replica Run Level: Operational Replication Status: FailedOver State: Healthy Last Update: Fri Jan 3 09:00:00 2015
From a Primary in normal conditions:
Appliance Name: TPAMCONSOLE_Primary Cluster Role: Primary Run Level: Operational Replication Status: Replicating State: Healthy Last Update: Fri Jan 3 09:00:00 2015
From a Replica in normal conditions :
Appliance Name: TPAMCONSOLE_Replica Cluster Role: Replica Run Level: Operational Replication Status: Standby State: Healthy Last Update: Fri Jan 3 09:00:00 2015