By default, client applications can see both physical slots and virtual HA slots. Directing applications at the physical slots bypasses the high availability and load balancing functionality. An application must be directed at the virtual HA slot to use HA load balancing and redundancy. HA Only mode hides the physical slots and leaves only the HA group slots visible to applications, simplifying the PKCS#11 slot numbering
If an HA group member partition fails and/or is recovered, while HAonly is enabled, then slot numbers do not change.
If an HA group member partition fails and/or is recovered, while HAonly is not enabled, all visible slot numbers can change, including the HA group virtual slots. This can cause applications to direct operations to the wrong slot.
If a physical slot in the HA group receives a direct request, the results will not be replicated on the other partitions in the group (see HA Troubleshooting) When HA Only mode is enabled, the HA virtual slots are not affected by partition slot changes.
The virtual slot defaults to slot 0, unless this behavior is modified by
Thales recommends enabling HAonly mode on all clients running HA groups.
NOTE Individual partition slots are still visible in LunaCM when HA Only mode is enabled. They are hidden only from client applications. Use CKdemo (Option 11) to see the slot numbers to use with client applications.
To enable HA Only mode
1.Enable HA Only mode in LunaCM.
lunacm:> hagroup haonly -enable
2.[Optional] Since LunaCM still displays the partitions, you can check the status of HA Only mode at any time.
lunacm:> hagroup haonly -show
To disable HA Only mode
1.Disable HA Only mode in LunaCM.
lunacm:> hagroup haonly -disable
