PRIMECLUSTER Installation and Administration Guide 4.7

M.4 Changes in PRIMECLUSTER 4.7A00 from 4.3A10

Incompatible commands

The following commands of PRIMECLUSTER 4.7A00 are incompatible with PRIMECLUSTER 4.3A10.

• M.4.1 sdtool command

• M.4.2 hvshut command

• M.4.3 hvswitch command

• M.4.4 hvdump command

Incompatible functions

The following functions of PRIMECLUSTER 4.7A00 are incompatible with PRIMECLUSTER 4.3A10.

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

• M.4.6 Operator Intervention Request

• M.4.7 Setting Up Fsystem Resources

• M.4.8 Changes of the ports used by RMS

• M.4.9 Configuring the IPMI Shutdown Agent

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

• M.4.11 Setting up the Host OS failover function used in the PRIMEQUEST KVM environment

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

• M.4.13 Display of the resource fault trace

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

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

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

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

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

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

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

Incompatible messages

The following messages of PRIMECLUSTER 4.7A00 are incompatible with PRIMECLUSTER 4.3A10.

• M.4.18 Changes of RMS console message

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