Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster 4.0 |
1. Introduction to Administering Oracle Solaris Cluster
2. Oracle Solaris Cluster and RBAC
3. Shutting Down and Booting a Cluster
4. Data Replication Approaches
5. Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems
Overview of Administering Global Devices and the Global Namespace
Global Device Permissions for Solaris Volume Manager
Dynamic Reconfiguration With Global Devices
Overview of Administering Cluster File Systems
Cluster File System Restrictions
How to Update the Global-Devices Namespace
How to Change the Size of a lofi Device That Is Used for the Global-Devices Namespace
Migrating the Global-Devices Namespace
How to Migrate the Global-Devices Namespace From a Dedicated Partition to a lofi Device
How to Migrate the Global-Devices Namespace From a lofi Device to a Dedicated Partition
Adding and Registering Device Groups
How to Add and Register a Device Group (Solaris Volume Manager)
How to Add and Register a Device Group (Raw-Disk)
How to Add and Register a Replicated Device Group (ZFS)
How to Remove and Unregister a Device Group (Solaris Volume Manager)
How to Remove a Node From All Device Groups
How to Remove a Node From a Device Group (Solaris Volume Manager)
How to Remove a Node From a Raw-Disk Device Group
How to Change Device Group Properties
How to Set the Desired Number of Secondaries for a Device Group
How to List a Device Group Configuration
How to Switch the Primary for a Device Group
How to Put a Device Group in Maintenance State
Administering the SCSI Protocol Settings for Storage Devices
How to Display the Default Global SCSI Protocol Settings for All Storage Devices
How to Display the SCSI Protocol of a Single Storage Device
How to Change the Default Global Fencing Protocol Settings for All Storage Devices
How to Change the Fencing Protocol for a Single Storage Device
Administering Cluster File Systems
How to Add a Cluster File System
How to Remove a Cluster File System
How to Check Global Mounts in a Cluster
Administering Disk-Path Monitoring
How to Print Failed Disk Paths
How to Resolve a Disk-Path Status Error
How to Monitor Disk Paths From a File
How to Enable the Automatic Rebooting of a Node When All Monitored Shared-Disk Paths Fail
How to Disable the Automatic Rebooting of a Node When All Monitored Shared-Disk Paths Fail
7. Administering Cluster Interconnects and Public Networks
10. Configuring Control of CPU Usage
Oracle Solaris Cluster software installation automatically assigns SCSI reservations to all storage devices. Use the following procedures to check the settings of devices and, if necessary, to override the setting for a device.
How to Display the Default Global SCSI Protocol Settings for All Storage Devices
How to Change the Default Global Fencing Protocol Settings for All Storage Devices
How to Change the Fencing Protocol for a Single Storage Device
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
# cluster show -t global
For more information, see the cluster(1CL) man page.
Example 5-12 Displaying the Default Global SCSI Protocol Settings for All Storage Devices
The following example displays the SCSI protocol settings for all storage devices on the cluster.
# cluster show -t global === Cluster === Cluster Name: racerxx clusterid: 0x4FES2C888 installmode: disabled heartbeat_timeout: 10000 heartbeat_quantum: 1000 private_netaddr: 172.16.0.0 private_netmask: 255.255.111.0 max_nodes: 64 max_privatenets: 10 udp_session_timeout: 480 concentrate_load: False global_fencing: prefer3 Node List: phys-racerxx-1, phys-racerxx-2
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
# cldevice show device
The name of the device path or a device name.
For more information, see the cldevice(1CL)man page.
Example 5-13 Displaying the SCSI Protocol of a Single Device
The following example displays the SCSI protocol for the device /dev/rdsk/c4t8d0.
# cldevice show /dev/rdsk/c4t8d0 === DID Device Instances === DID Device Name: /dev/did/rdsk/d3 Full Device Path: phappy1:/dev/rdsk/c4t8d0 Full Device Path: phappy2:/dev/rdsk/c4t8d0 Replication: none default_fencing: global
You can turn fencing on or off globally for all storage devices connected to a cluster. The default fencing setting of a single storage device overrides the global setting when the device's default fencing is set to pathcount, prefer3, or nofencing. If the default fencing setting of a storage device is set to global, the storage device will use the global setting. For example, if a storage device has the default setting pathcount, the setting will not change if you use this procedure to change the global SCSI protocol settings to prefer3. You must use the How to Change the Fencing Protocol for a Single Storage Device procedure to change the default setting of a single device.
Caution - If fencing is turned off under the wrong circumstances, your data can be vulnerable to corruption during application failover. Examine this data corruption possibility carefully when you are considering turning fencing off. Fencing can be turned off if the shared storage device does not support the SCSI protocol or if you want to allow access to the cluster's storage from hosts outside the cluster. |
To change the default fencing setting for a quorum device, you must unconfigure the device, change the fencing setting, and reconfigure the quorum device. If you plan to turn fencing off and back on regularly for devices that include quorum devices, consider configuring quorum through a quorum server service to eliminate interruptions in quorum operation.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
cluster set -p global_fencing={pathcount | prefer3 | nofencing | nofencing-noscrub}
Sets the current global default fencing algorithm for all shared devices.
Uses the SCSI-3 protocol for devices with more than two paths.
Determines the fencing protocol by the number of DID paths that are attached to the shared device. The pathcount setting is used for quorum devices.
Turns fencing off by setting the fencing status for all storage devices.
Scrubbing the device ensures that the device is cleared of all persistent SCSI reservation information and allows access to the storage from systems outside the cluster. Use the nofencing-noscrub option only for storage devices that have severe problems with SCSI reservations.
Example 5-14 Setting the Default Global Fencing Protocol Settings for All Storage Devices
The following example sets the fencing protocol for all storage devices on the cluster to the SCSI-3 protocol.
# cluster set -p global_fencing=prefer3
You can also set the fencing protocol for a single storage device.
Note - To change the default fencing setting for a quorum device, you must unconfigure the device, change the fencing setting, and reconfigure the quorum device. If you plan to turn fencing off and back on regularly for devices that include quorum devices, consider configuring quorum through a quorum server service to eliminate interruptions in quorum operation.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
Caution - If fencing is turned off under the wrong circumstances, your data can be vulnerable to corruption during application failover. Examine this data corruption possibility carefully when you are considering turning fencing off. Fencing can be turned off if the shared storage device does not support the SCSI protocol or if you want to allow access to the cluster's storage from hosts outside the cluster. |
cldevice set -p default_fencing ={pathcount | \ scsi3 | global | nofencing | nofencing-noscrub} device
Modifies the default_fencing property of the device.
Determines the fencing protocol by the number of DID paths that are attached to the shared device.
Uses the SCSI-3 protocol.
Uses the global default fencing setting. The global setting is used for non-quorum devices.
Turns fencing off by setting the fencing status for the specified DID instance.
Scrubbing the device ensures that the device is cleared of all persistent SCSI reservation information and allows access to the storage device from systems outside the cluster. Use the nofencing-noscrub option only for storage devices that have severe problems with SCSI reservations.
Specifies the name of the device path or device name.
For more information, see the cluster(1CL) man page.
Example 5-15 Setting the Fencing Protocol of a Single Device
The following example sets the device d5, specified by device number, to the SCSI-3 protocol.
# cldevice set -p default_fencing=prefer3 d5
The following example turns default fencing off for the d11 device.
#cldevice set -p default_fencing=nofencing d11