PRIMECLUSTER Installation and Administration Guide 4.6

M.5 Changes in PRIMECLUSTER 4.6A00 from 4.3A20

Incompatible command

The following commands of PRIMECLUSTER 4.6A00 are incompatible with PRIMECLUSTER 4.3A20.

• M.5.1 hvshut command

• M.5.2 hvswitch command

• M.5.3 hvdump command

Incompatible functions

The following functions of PRIMECLUSTER 4.6A00 are incompatible with PRIMECLUSTER 4.3A20.

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

• M.5.5 Operator intervention request

• M.5.6 Setting Up Fsystem Resources

• M.5.7 Configuring the IPMI Shutdown Agent

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

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

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

• M.5.11 Display of the resource fault trace

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

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

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

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

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

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

Incompatible messages

The following messages of PRIMECLUSTER 4.6A00 are incompatible with PRIMECLUSTER 4.3A20.

• M.5.16 Changes of RMS console message

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