 |
Index for
Section 8 |
|
 |
Alphabetical
listing for D |
|
 |
Bottom of
page |
|
drd_ivp(8)
NAME
drd_ivp - Validates the integrity and operation of the distributed raw disk
(DRD) subsystem (provided on Production Server configurations only)
SYNOPSIS
/usr/sbin/drd_ivp [flags]
FLAGS
-c Performs DRD configuration validation tests.
-d Displays additional debugging output.
-h Displays help.
-p Displays the Cluster Configuration Information table.
-r Creates DRD device special files representing DRD services that
are provided by other ASEs in the cluster. This flag applies
only to clusters consisting of multiple ASEs.
-t Performs tuning parameter tests.
-v Performs ASE_ID validation tests.
DESCRIPTION
The drd_ivp utility is an installation verification procedure (IVP) that
validates the integrity and operation of the DRD subsystem. It is called by
the cluster IVP utility, clu_ivp(8); you can also invoke it as a separate
utility
You can run this utility on any cluster member system after you use the
asemgr utility in each ASE to populate the member list in each ASE
database. Because the drd_ivp utility obtains the status of other member
systems remotely, you only need to run it on one member system.
Note
The drd_ivp utility cannot guarantee that DRD functionality is fully
operational. It cannot check for either the existence or correct
configuration of individual services, nor can it determine whether the
cluster hardware has been configured correctly.
If the requested validation tests succeed, the drd_ivp utility returns a
success status (0). If any validation tests fail, the utility displays
indicating the specific problem and returns an error status (1).
The following tests are available:
· DRD configuration validation test (-c flag)
· ASE_ID validation test (-v flag)
· Tuning parameter test (-t flag)
The flags you specify to the drd_ivp utility determine which kinds of tests
it performs.
When invoked with the -c flag, the drd_ivp utility performs a set of DRD
configuration validation tests. These tests:
· Check that the DRD subsystem is configured.
· Verify that the block shipping service daemon (bssd) is registered
with the Remote Procedure Call (RPC) portmapper daemon and is
responsive to block shipping client (bsc) requests in the DRD
subsystem.
· Check that the TruCluster Production Server Software license Product
Authorization Key (PAK) is registered.
When invoked with the -v flag, the utility obtains each cluster member
system's ASE_ID from its /etc/rc.config file and attempts to construct a
consistent picture of the membership of the cluster's ASE configuration. If
it cannot do this (because some members of the ASE are down or because the
ASE daemons on certain member systems are not operational), the utility
displays a message of the following form:
Unable to determine which nodes are in the same ASE as node <clunode>
After it determines the ASE_ID of each cluster member, the drd_ivp utility
verifies that all nodes adhere to the following configuration requirements
for ASE_IDs:
· A node can be a member of only one ASE.
· Each ASE must have a unique ASE_ID.
· All nodes within the same ASE must have the same ASE_ID.
Note
The drd_ivp utility does not validate that the ASE_ID value used in
the ASE database is consistent with the member system's current
ASE_ID. Use extreme caution when changing a node's ASE_ID. See the
TruCluster Software Products Administration guide for instructions for
doing so.
When invoked with the -t flag, the drd_ivp utility validates the settings
of the DRD subsystem's tunable attributes, obtains performance statistics
from the running system, and compares them to threshold values that are
prescribed for the DRD subsystem's tunable attributes. If the current
value of an attribute exceeds its threshold value, the utility suggests a
correction. The correction usually involves changing the attribute's value
or a DRD subsystem parameter in the /etc/sysconfigtab file. A system
reboot is required for these tuning changes to take effect. See drd(7) for
a list the DRD subsystem's tunable attributes.
To collect peak usage statistics, use the drd_ivp utility with the -t flag
whenever the cluster is heavily loaded. Because different cluster members
may need to be tuned differently based on disk access patterns, run the
utility with the -t flag on each member system. Use the -d flag in
conjunction with the -t flag to display the progress and status of each of
the DRD tuning parameter tests.
When invoked with the -p flag, the drd_ivp utility displays the Cluster
Configuration Information table. The table includes the following
information for each cluster member system:
__________________________________________
Heading Description
__________________________________________
Hostname
Memory Channel IP name (as
defined by the CLUSTER_NET
configuration variable in the
member system's /etc/rc.config
file)
ASE_ID
System's ASE_ID (as defined by
the ASE_ID configuration
variable in the member
system's /etc/rc.config file)
BSSD Reg
Indicates whether the bssd
daemon is registered with the
RPC portmapper daemon (Yes or
No)
BSSD Resp
Indicates whether the bssd
daemon responds to RPC
requests (Yes or No)
DRD Conf
Indicates whether the DRD
subsystem is configured (Yes
or No)
Lic Reg
Indicates whether the
TruCluster Production Server
Software PAK has been
registered (Yes, No, or
Unknown)
__________________________________________
When invoked on each member system with the -r flag, the drd_ivp utility
ensures that the device special files that identify DRD devices are
synchronized across all cluster members.
When you add a DRD service within an ASE, the asemgr utility creates the
corresponding device special files on all member systems within the ASE.
If a cluster consists of a single ASE, you do not need to perform any
additional steps to make the service accessible clusterwide. If the
cluster comprises multiple ASEs, the asemgr utility displays a message
recommending that you use the drd_mknod command to create, one at a time,
the DRD device special files on nodes outside the serving ASE. This is
necessary because the scope of the asemgr utility is restricted to a single
ASE.
The drd_ivp -r command is used only in clusters containing multiple ASEs.
It is an efficient alternative to the drd_mknod utility when you are adding
several new DRD services at a time or when you are setting up a new ASE
with services provided by another ASE in the cluster. It automatically
runs the drd_mknod command for each of a series of DRD services being added
to the cluster. If necessary, it creates the required device special files.
Because it creates these files only on the local member, you must execute
this command on each cluster member so that all DRD services served from
each of the cluster's ASEs are available to client systems clusterwide.
Before executing the drd_ivp -r command, run the cluster validation tests
to ensure that the cluster's DRD configuration is correct:
# drd_ivp -p -v -c
The -r flag automates the creation of DRD device special files, but does
not automate their deletion. To delete DRD device special files, use the
-d option to the drd_mknod command.
EXAMPLES
The following command runs the ASE_ID and DRD configuration validation
tests and displays the Cluster Configuration Information table:
% drd_ivp -p -v -c
It displays output similar to the following:
Cluster Configuration Information
Hostname ASE_ID BSSD BSSD DRD Lic
Reg Resp Conf Reg
------------------------------------------------
rclu11 1 Yes Yes Yes Yes
rclu12 1 Yes Yes Yes Yes
rclu3 0 Yes Yes Yes Yes
rclu4 0 Yes Yes Yes Yes
DRD configuration validation test succeeded.
ASE_ID validation tests succeeded.
---------------------------------------------------
The following command verifies that the device special files, which
identify DRD devices in a cluster, are synchronized across all members in a
cluster consisting of multiple ASEs. If necessary, it creates the device
special files required for DRD functionality on the current member system.
% drd_ivp -d -r
.
.
.
Creating DRD device special files for services within other ASEs...
Completed DRD file creation.
The following command runs the DRD tuning parameter tests in verbose mode:
% drd_ivp -d -t
Obtaining cluster configuration information.
nodes: 2
milesrm (ASE_ID = 0) DRD is configured on node milesrm
drd_pak_registered to milesrm, PAK is registered.
BSSD registered on milesrm
BSSD responding on milesrm
davisrm (ASE_ID = 0) DRD is configured on node davisrm
drd_pak_registered to davisrm, PAK is registered.
BSSD registered on davisrm
BSSD responding on davisrm
Performing tuning parameter tests...
The "drd-bssd-busy" is 0, which is below the threshold value of 10.
The "drd-max-hash-length" is 1, which is below the threshold value of 50.
The "MC read wait %" is 0, which is below the threshold value of 5.
The "MC write wait %" is 0, which is below the threshold value of 5.
The "MC read unaligned %" is 0, which is below the threshold value of 20.
The "MC write unaligned %" is 0, which is below the threshold value of 20.
No tuning problems were detected.
FILE
/usr/sbin/drd_ivp
Specifies the command path.
RELATED INFORMATION
drd(7), asemgr(8), bsc_biod(8), bssd(8), clu_ivp(8), drd_balance(8),
drd_dma(8), drd_mknod(8), mknod(8)
|
Index for
Section 8 |
|
|
Alphabetical
listing for D |
|
 |
Top of
page |
|