Top
PRIMECLUSTERGlobal Link Services Configuration and AdministrationGuide 4.5Redundant Line Control Function
FUJITSU Software

F.9.3 Other incompatible items

F.9.3.1 Changing the installation directory

[Contents]

The installation directory of the package was changed from "/opt" to "/etc/opt."

[Changes]

Before modification

The installation directory of the package is "/opt."

After modification

The installation directory of the package is "/etc/opt."

Also, the actual command path maintains the compatibility by creating symbolic link to the previous modification of installation directory.

F.9.3.2 Initial settings for link status monitoring

[Contents]

If the HUB monitoring function is set, the link status monitoring function is enabled.

[Changes]

Before modification

The link status monitoring function is in inactive status and NIC link down is not detected.

After modification

The link status monitoring function is in active status and NIC link down is detected.

F.9.3.3 Initial setting values for the standby interface inactivation method

[Contents]

The initial setting of the standby interface inactivation method is "plumb."

[Changes]

Before modification

Initial is set to "unplumb" and the standby NIC is in "unplumb" status.

After modification

Initial is set to "plumb" and the standby NIC is in "down" status.

F.9.3.4 Detecting hang-up of the ping command

[Contents]

In the following monitoring functions, a hang-up of the ping command can be detected.

[Changes]

Before modification

When the ping command hangs, an error in the route cannot be detected.

After modification

When the ping command hangs, an error in the route is detected. The operation after the route error is detected is the same as the operation after an error is detected in each communication mode.

In the user command execution function of the NIC switching mode, to be able to determine the type of error detected by the HUB monitoring function, added param2 to the argument when executing user commands.

For user command execution function of NIC switching mode, refer to "(2) When detected an error in a transfer route" in "3.6.10.1 Settings for NIC switching mode" for details.

F.9.3.5 Output messages to the console

[Contents]

Changes were made so that the following messages will not be output on the console. However, you can change the settings so that these messages are output to the console as in the settings of previous versions.

[Changes]

Before modification

Messages are output both in the system log and the console.

After modification

Messages are only output in the system log.

If you want messages to be output also in the console as it was previously, add "disable_console" parameter to the following settings file and set its value to "0."

/etc/opt/FJSVhanet/config/ctld.param

#
#  HA-Net Configuration File
#
#       Each entry is of the form:
#
#       <param> <value or string>
#

observ_msg                      0       # suppress observe message
transition_mode                 0       # resource status transition mode
logicalif_takeover_type         1       # takeover Zone and RAC interface
disable_console                 0 <- Add parameter and set to "0"

F.9.3.6 Fujitsu hot standby protocol

[Contents]

Changed the procedures for if message transmission failed when using Fujitsu hot standby protocol in GS/SURE linkage mode.

[Changes]

Before modification

The following error message is output.

ERROR: 80590: internal error.(*) [sock.c(***)]

After modification

The following error message is output.

WARNING: 93200: cannot send fhsp message. (dest=hostip, code)

See "A.1.3 Console output messages (numbers 800 to 900)" for details on the messages.

F.9.3.7 Changing the startup timing of the HUB monitoring function

[Contents]

The startup timing of the HUB monitoring function during system startup was changed to enable faster detection of transfer route failures.

[Changes]

Before modification

Could not detect a transfer route failure after the zones service (svc:/system/zones) was started.

The settings file (service.sh) for Redundant Line Control function service of the user command execution function will be executed after the zones service has been started.

After modification

Changed so that transfer route failures can be detected before the remote disk service (NFS client, iSCSI initiator) has been started.

The timing for the execution of the settings file (service.sh) for the transmission path redundancy function of the user command execution function is done earlier.

If using a settings file, see "C.6.1.7 Example of configuration with GS/SURE linkage mode" and modify the script.

F.9.3.8 Self-check function

[Contents]

The driver hang up detection time for the self-check function is set to 60 seconds.

Tuning a driver hang up detection time has become possible. See "G.3.3.4 A virtual driver hang up was detected by the Self-Check function" for details.

[Changes]

Before modification

After modification