This section contains the information you need to plan your Sun Cluster HA for SWIFTAlliance Access installation and configuration.
This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for SWIFTAlliance Access only.
Your data service configuration might not be supported if you do not observe these restrictions.
You can configure the Sun Cluster HA for SWIFTAlliance Access only as a HA agent and not as a scalable agent.
You can install the SWIFTAlliance Access software on a global file system. Best practice is to use a failover file system. For SWIFTAlliance Access 5.5, you must install the IBM DCE software on local storage.
Only one SWIFTAlliance Access instance is supported by this agent.
For restrictions that apply to all data services, see the Sun Cluster Release Notes.
These requirements apply to Sun Cluster HA for SWIFTAlliance Access only. You must meet these requirements before you proceed with your Sun Cluster HA for SWIFTAlliance Access installation and configuration. Follow the SWIFTAlliance Access installation guide for the installation of the mandatory patch levels and the installation of the software.
Your data service configuration might not be supported if you do not adhere to these requirements.
Configure the Sun Cluster HA for SWIFTAlliance Access data service to protect a Sun Cluster instance and its respective components. These components, and their dependencies, are briefly described next.
Component |
Description |
---|---|
DCE daemon |
-> SUNW.LogicalHost resource |
SWIFTAlliance Access |
-> SUNW.LogicalHostresource -> SUNW.HAStoragePlus resource The SUNW.HAStoragePlus resource manages the SWIFTAlliance Access System Mount points and ensures that Sun Cluster is not started until these are mounted. -> DCE daemon (version 5.5 only) |
The Sun Cluster component has two configuration and registration files in the /opt/SUNWscsaa/util directory. These files enable you to register the Sun Cluster component with Sun Cluster.
Within these files, the appropriate dependencies have already been defined. You must update the saa_config file before you run the saa_register script.