PRIMECLUSTER Installation and Administration Guide 4.5

N.3 Changes in PRIMECLUSTER 4.5A10 from 4.1A30

Incompatible commands

The following commands of PRIMECLUSTER 4.5A10 are incompatible with PRIMECLUSTER 4.1A30.

• N.3.1 ciptool command

• N.3.2 sdtool command

• N.3.3 hvshut command

• N.3.4 hvswitch command

• N.3.5 hvdump command

Incompatible functions

The following functions of PRIMECLUSTER 4.5A10 are incompatible with PRIMECLUSTER 4.1A30.

• N.3.6 Posting Notification of a Resource Failure or Recovery

• N.3.7 Operator Intervention Request

• N.3.8 Operation Procedures and Displayed Items for Cluster Application Setup and Modification

• N.3.9 Setting Up Fsystem Resources

• N.3.10 Client Environment for Web-Based Admin View

• N.3.11 Changes of the Behavior of CF Startup

• N.3.12 HV_CONNECT_TIMEOUT

• N.3.13 Changes of the ports used by RMS

• N.3.14 Changes of the port number used by the shutdown facility

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

• N.3.16 Display of the resource fault trace

• N.3.17 Change of /etc/cip.cf file

• N.3.18 Changes in CF over IP setting window of CF Wizard

Incompatible messages

The following messages of PRIMECLUSTER 4.5A10 are incompatible with PRIMECLUSTER 4.1A30.

• N.3.19 Changes of the RMS message

• N.3.20 Changes of the importance of the message in the RMS wizard

• N.3.21 Changes of RMS console message

• N.3.22 Changes of the response message for the operator intervention request