Monitoring Clusters

You can monitor clusters using the standard logging tools provided by the Pulse Connect Secure. In particular, you can use several cluster-specific SNMP traps to monitor events that occur on your cluster nodes, such as:

•External interface down

•Internal interface down

•Disabled node

•Changed virtual IP (VIP)

•Deleted cluster node (cluster stop)

Generally, it is desirable to configure your SNMP traps on a cluster-wide basis, so that any given cluster node can send its generated traps to the right target. Setting up cluster-wide configuration for the traps is particularly important when you also use a load balancer, because you may not know which node is responsible for a specific operation. In that case, the load balancer may independently determine which cluster node can manage an administrative session.

You can use SNMP traps that are included in the Pulse Secure Standard MIB to monitor these events. These traps include:

•iveNetExternalInterfaceDownTrap - Supplies type of event that brought down the external interface.

•iveNetInternalInterfaceDownTrap - Supplies type of event that brought down the internal interface.

•iveClusterDisableNodeTrap - Supplies the cluster name on which nodes have been disabled, along with a space separated list of disabled node names.

•iveClusterChangedVIPTrap - Supplies the type of the VIP, whether external or internal, and its value before and after the change.

•iveClusterDelete - Supplies the name of the cluster node on which the cluster delete event was initiated.

These traps are always enabled and available in the MIB. You cannot disable the traps.