Configure secure heartbeats
secureHeartbeats parameter of the set cluster command.
-
Secure heartbeats must be configured from the cluster IP address.
-
Ensure that all the cluster nodes are running release 14.1 build 12.30 or later.
Configure secure heartbeats using the CLI
-
Enable the secure heartbeats.
set cluster instance <clId> secureHeartbeats ENABLED -
Save the configuration.
save ns config -
Verify the configuration.
sh cluster instance <clid>
> set cluster instance 1 secureHeartbeats ENABLED
Warning: [The Secure Heartbeats feature must be set in the cluster IP (CLIP) address.]
Done
> save ns config
Done
> sh cluster instance 1
1) Cluster ID: 1
Dead Interval: 3 secs
Hello Interval: 200 msecs
Preemption: DISABLED
Propagation: ENABLED
Quorum Type: MAJORITY
INC State: DISABLED
Process Local: DISABLED
Retain Connections: NO
Heterogeneous: NO
Backplane based view: DISABLED
Cluster sync strict mode: DISABLED
DFD Retain L2 Params: DISABLED
Cluster Proxy Arp Status: ENABLED
Secure Heartbeats: ENABLED
Cluster Status: ENABLED(admin), ENABLED(operational), UP
WARNING(s):
(1) - There are no spotted SNIPs configured on the cluster. Spotted SNIPs can help improve cluster performance.
Member Nodes:
Node ID Node IP Health Admin State Operational State
------- ------- ------ ----------- -----------------
1) 1 10.102.58.124 UP ACTIVE ACTIVE
2) 2 10.102.58.125 UP ACTIVE ACTIVE
3) 0 10.102.58.123* UP ACTIVE ACTIVE(Configuration Coordinator)
Done
-
set cluster instance <clId> secureHeartbeats DISABLED -
save ns config
Configure secure heartbeats using the GUI
-
Navigate to System > Cluster.
-
In the details pane, click the Manage Cluster link.
-
In the Configure cluster instance page, select the Secure Heartbeats checkbox.
-
Click Save, and then click Yes.