PRIMECLUSTER Installation and Administration Guide 4.4

M.2 Changes in PRIMECLUSTER 4.4A00 from 4.1A20

Incompatible commands

The following commands of PRIMECLUSTER 4.4A00 are incompatible with PRIMECLUSTER 4.1A20.

• M.2.1 clgettree(1) command

• M.2.2 hvdisp command

• M.2.3 ciptool command

• M.2.4 sdtool command

• M.2.5 hvshut command

• M.2.6 hvswitch command

• M.2.7 hvdump command

Incompatible functions

The following functions of PRIMECLUSTER 4.4A00 are incompatible with PRIMECLUSTER 4.1A20.

• M.2.8 Posting Notification of a Resource Failure or Recovery

• M.2.9 Operator Intervention Request

• M.2.10 Node state

• M.2.11 Operation Procedures and Displayed Items for Cluster Application Setup and Modification

• M.2.12 Setting Up Fsystem Resources

• M.2.13 Client Environment for Web-Based Admin View

• M.2.14 Changes of the Behavior of CF Startup

• M.2.15 HV_CONNECT_TIMEOUT

• M.2.16 Changes of the ports used by RMS

• M.2.17 Changes of the port number used by the shutdown facility

• M.2.18 Changes of the target node to forcibly shut down when a heartbeat failure occurs

• M.2.19 Display of the resource fault trace

• M.2.20 Change of /etc/cip.cf file

• M.2.21 Changes in CF over IP setting window of CF Wizard

Incompatible messages

The following messages of PRIMECLUSTER 4.4A00 are incompatible with PRIMECLUSTER 4.1A20.

• M.2.22 Changes of the RMS message

• M.2.23 Changes of the importance of the message in the RMS wizard

• M.2.24 Changes of RMS console message

• M.2.25 Changes of the response message for the operator intervention request