Sun Cluster Geographic Edition Man Pages

This section discusses errors and omissions from the Sun Cluster Geographic Edition man pages.

Fence_level Parameter Described in the geopg Man Page Must Be Set to never or async (6265011)

Problem Summary: If the fence_level parameter is not set to never or async, data replication might not function properly when the secondary site goes down.

Workaround: To avoid application failure on the primary cluster, specify a Fence_level of never or async.

If you have special requirements to use a Fence_level of data or status, consult your Sun representative.

geopg Man Page Does Not Document the Maximum Timeout Limit (6284337)

Problem Summary: The geopg man page does not document the upper limit of the timeout property.

Workaround: The timeout property now has a maximum of 1000000 seconds.

geopg Man Page Does Not Adequately Describe the Timeout Property (6287531)

Problem Summary: The geopg man page does adequately describe the purpose of the timeout property.

Workaround: The timeout period is the longest time Sun Cluster Geographic Edition waits for a response after a geopg command is executed, such as start, stop, switchover, and takeover. If the command does not respond within the timeout period, Sun Cluster Geographic Edition reports the operation as timed out, even if the underlying command that was executed eventually completes successfully.

The timeout period applies to operations on a per-cluster basis. An operation with a local scope times out if the operation does not complete after the specified timeout period.

An operation with a global scope consists of an action on the local cluster and an action on the remote cluster. The local and remote action are timed separately. So, an operation with a global scope times out if the local operation does not complete after the specified timeout period or if the remote operation does not complete after the specified timeout period.

For example, the following operation is launched with a local scope:

# geopg start -e Local

If the timeout property is set to 200 seconds, then the geopg start operation times out if the operation does not complete after 200 seconds.

The same operation is launched with a global scope:

# geopg start -e Global

If the timeout property is set to 200 seconds, then the geopg start operation times out if the operation does not complete on the local cluster after 200 seconds or if the operation does not complete on the remote cluster after 200 seconds. If the local action takes 150 seconds and the remote action takes 150 seconds, the operation does not time out.

The protection group timeout value is estimated. Not every operation on a protection group is timed against the timeout period. For example, the time taken to initialize the data structure and check for the precondition of the operation are not timed in the timeout period.

geops Man Page Incorrectly Documents the Notification_EmailAddrs Property (6289105)

Problem Summary: The geops incorrectly gives the property for setting the notification email address as Notification_EmailAddrss.

Workaround: The correct property name for the notification email address is Notification_EmailAddrs.

Default Heartbeat Port Number Incorrect in the geohb Man Page (6289264)

Problem Summary: The default TCP/UDP heartbeat port number is given as 8765 in the man page. However, this port number has been assigned to someone else by the Internet Assigned Numbers Authority (IANA).

Workaround: To avoid any potential conflicts, the TCP/UDP now uses port number 2084 by default.

Wrong Syntax for Adding Resource Groups and Device Groups in geopg Man Page (6284809)

Problem Summary: The syntax for adding resource group and device groups is not correct in the geopg man page.

Workaround: The correct syntax for adding a resource group is geopg add-resource-group resource-group protection-group-name. The correct syntax for adding a device group is geopg add-device-group device-group protection-group-name.

Incorrect Example in the geohb Man Page (6290885)

Problem Summary: The geohb man page contains the following incorrect example in the DESCRIPTION section:

To create a heartbeat plug-in that is named command1, use the following:

# geohb add paris-to-newyork -g command1 -p Query_cmd=/usr/bin/hb/

Workaround: The example should read as follows:

To add a custom heartbeat plug-in that is named command1 to the paris-to-newyork heartbeat, use the following:

# geohb add-plugin -p Query_cmd=/usr/bin/hb/ command1 paris-to-newyork

Wrong Description of the geops udpate Command (6297733)

Problem Summary: The geops udpate command synchronizes information with the partner cluster. The command cannot update a partnership while the cluster is disconnected from the partner cluster.

Workaround: Do not use the geops udpate command to update a partnership while the cluster is disconnected from the partner cluster.

Extra Characters In the Man Pages (6302385)

Problem Summary: The characters “ 6 appear randomly in the man pages.

Workaround: Disregard these extra characters.

Man Pages Contain Incorrect Subcommands (6304746)

Problem Summary: The geohb(1M) and the geopg(1M) man pages contain some references to incorrect subcommands in the examples.

Workaround: Always refer to the correct usage information by using the command--help command.