Latest revision as of 12:52, 11 May 2017

Overview

This document details how to check the VIP Status on a Swivel appliance. For information on VIP configuration see VIP on PINsafe Appliances, for further information on Swivel HA see High Availability with PINsafe.

Prerequisites

Swivel appliance

Heartbeat Status

PINsafe VIP Status Check through the CMI

On each Swivel Appliance in the cluster (Primary Master, Standby Master, but not DR)

1. Login to the PINsafe Command Management Interface (See CMI).

2. Select Heartbeat

3. Select Status

4. Check VIP is on the expected server (usually always on the primary

If the Primary appliance is shutdown, the VIP should fail across to the Standby appliance.

Swivel VIP status check through the command line

From the command line run the following:

service heartbeat status

• If it's not started you'll get something like:

[admin@standby ~]# service heartbeat status heartbeat is stopped. No process

• If it is started you'll get something like:

[admin@standby ~]# service heartbeat status heartbeat OK [pid 6855 et al] is running on standby.swivel.local [standby.swivel.local]...

Testing

Shutdown Primary Master, observe VIP on Standby, start Primary Master, observe VIP on Primary and Standby

Known Issues

Running multiple Swivel HA clusters without a cross over cable, on the same network may cause issues as they use multicast on port 694 UDP by default.

Troubleshooting

Heartbeat will not start see Heartbeat issues

Check the /var/log/messages on each appliance for error messages related to heartbeat, see Troubleshooting Files FAQ