Man Pages

Sun Cluster 3.0 Data Service Man Pages

To display Sun Cluster 3.0 data service man pages, install the latest patches for the Sun Cluster 3.0 data services that you installed on Sun Cluster 3.1 software. See Patches and Required Firmware Levels for more information.

After you have applied the patch, access the Sun Cluster 3.0 data service man pages by issuing the man -M command with the full man page path as the argument. The following example opens the Apache man page.

% man -M /opt/SUNWscapc/man SUNW.apache

Consider exporting your MANPATH to enable access to Sun Cluster 3.0 data service man pages without specifying the full path. The following example describes command input for adding the Apache man page path to your MANPATH and displaying the Apache man page.

% MANPATH=/opt/SUNWscapc/man:$MANPATH; export MANPATH
% man SUNW.apache

scconf_transp_adap_wrsm(1M)

The following scconf_transp_adap_wrsm(1M) man page replaces the existing scconf_transp_adap_wrsm(1M) man page.

NAME

scconf_transp_adap_wrsm.1m- configure the wrsm transport adapter

DESCRIPTION

wrsm adapters may be configured as cluster transport adapters. These adapters can only be used with transport types dlpi.

The wrsm adapter connects to a transport junction or to another wrsm adapter on a different node. In either case, the connection is made through a transport cable.

Although you can connect the wrsm adapters directly by using a point-to-point configuration, Sun Cluster software requires that you specify a transport junction, a virtual transport junction. For example, if node1:wrsm1 is connected to node2:wsrm1 directly through a cable, you must specify the following configuration information.

node1:wrsm1 <--cable1--> Transport Junction sw_wrsm1 <--cable2--> node2:wrsm1

The transport junction, whether a virtual switch or a hardware switch, must have a specific name. The name must be sw_wrsmN where the adapter is wrsmN. This requirement reflects a Wildcat restriction that requires that all wrsm controllers on the same Wildcat network have the same instance number.

When a transport junction is used and the endpoints of the transport cable are configured using scconf, scinstall, or other tools, you are asked to specify a port name on the transport junction. You can provide any port name, or accept the default, as long as the name is unique for the transport junction.

The default sets the port name to the node ID that hosts the adapter at the other end of the cable.

Refer to scconf(1M) for more configuration details.

There are no user configurable properties for cluster transport adapters of this type.

SEE ALSO

scconf(1M), scinstall(1M), wrsmconf(1M), wrsmstat(1M), wrsm(7D), wrsmd(7D)

scconf_transp_adap_sci(1M)

The scconf_transp_adap_sci(1M) man page states that SCI transport adapters can be used with the rsm transport type. This support statement is incorrect. SCI transport adapters do not support the rsm transport type. SCI transport adapters support the dlpi transport type only.

scconf_transp_adap_sci(1M)

The following sentence clarifies the name of an SCI–PCI adapter. This information is not currently included in the scconf_transp_adap_sci(1M) man page.

New Information:

Use the name sciN to specify an SCI adapter.

scgdevs(1M)

The following paragraph clarifies behavior of the scgdevs command. This information is not currently included in the scgdevs(1M) man page.

New Information:

scgdevs(1M) called from the local node will perform its work on remote nodes asynchronously. Therefore, command completion on the local node does not necessarily mean it has completed its work cluster wide.

SUNW.sap_ci(5)

• There is an error in the Name section. The Name section should read as follows:

  sap_ci, SUNW.sap_ci and SUNW.sap_ci_v2 - Resource type implementations for Sun Cluster HA for SAP central instance.

• There is an error in the Description section. The Description section should read as follows:

  The Resource Group Manager (RGM) manages the SAP data service for Sun Cluster software. Configure the Sun Cluster HA for SAP central instance as a logical-hostname resource and an SAP central instance resource.

SUNW.sap_as(5)

• There is an error in the Name section. The Name section should read as follows:

  sap_as, SUNW.sap_as - Resource type implementation for Sun Cluster HA for SAP as a failover data service.

  sap_as, SUNW.sap_as_v2 - Resource type implementation for Sun Cluster HA for SAP as a failover data service or a scalable data service.

• There is an error in the Description section. The Description section should read as follows:

  The Resource Group Manager (RGM) manages the SAP data service for Sun Cluster software. If you are setting up the Sun Cluster HA for SAP application server as a failover data service configure it as a logical-hostname resource and an SAP application-server resource. If you are setting up the Sun Cluster HA for SAP application-server as a scalable data service configure it as a scalable SAP application-server resource.

rg_properties(5)

The following new resource group property should be added to the rg_properties(5) man page.

Auto_start_on_new_cluster

This property controls whether the Resource Group Manager starts the resource group automatically when a new cluster is forming.

The default is TRUE. If set to TRUE, the Resource Group Manager attempts to start the resource group automatically to achieve Desired_primaries when all nodes of the cluster are simultaneously rebooted. If set to FALSE, the Resource Group does not start automatically when the cluster is rebooted. .If set to FALSE, the Resource Group does not automatically start when the cluster is rebooted. The resource group will remain offline until the first time it is manually switched onlin using scswitch (1M). After that, it will resume normal failover behavior.

Category: Optional Default: True Tunable: Any time

rt_properties(5)

In this release, the current API_version has been incremented to 3 from its previous value of 2. To prevent a resource type from registering on an earlier version of Sun Cluster software, declare API_version=3. For more information, see rt_reg (4) and rt_properties (5).