PRIMECLUSTER Installation and Administration Guide 4.7

M.2 Changes in PRIMECLUSTER 4.7A00 from 4.2A30

Incompatible commands

The following commands of PRIMECLUSTER 4.7A00 are incompatible with PRIMECLUSTER 4.2A30.

• M.2.1 sdtool command

• M.2.2 hvshut command

• M.2.3 hvswitch command

• M.2.4 hvdump command

Incompatible functions

The following functions of PRIMECLUSTER 4.7A00 are incompatible with PRIMECLUSTER 4.2A30.

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

• M.2.6 Operator Intervention Request

• M.2.7 Setting Up Fsystem Resources

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

• M.2.9 Changes of the Behavior of CF Startup

• M.2.10 HV_CONNECT_TIMEOUT

• M.2.11 Changes of the ports used by RMS

• M.2.12 Configuring the IPMI Shutdown Agent

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

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

• M.2.15 Display of the resource fault trace

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

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

• M.2.18 Changing "turnkey wizard "STANDBY"" of hvw command

• M.2.19 Change of the startup method of the Web-Based Admin View screen

• M.2.24 Registering/Deleting a network interface card in the resource database of the cluster resource management facility

• M.2.25 Change of the path of the environment variable java_home used in Web-Based Admin View

• M.2.26 Behavior of the resource where the MonitorOnly attribute is set

Incompatible messages

The following messages of PRIMECLUSTER 4.7A00 are incompatible with PRIMECLUSTER 4.2A30.

• M.2.20 Changes of the RMS message

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

• M.2.22 Changes of RMS console message

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