 |
|
|
NAME
| | scdidadm - device
identifier configuration and administration utility wrapper |
SYNOPSIS
| | /usr/cluster/bin/scdidadm -c |
| | /usr/cluster/bin/scdidadm -C |
| | /usr/cluster/bin/scdidadm -r |
| | /usr/cluster/bin/scdidadm -R path | instance_number | all |
| | /usr/cluster/bin/scdidadm -l | -L [-h] [-o fmt] ... [path | instance_number] |
| | /usr/cluster/bin/scdidadm [-u] [-i] |
| | /usr/cluster/bin/scdidadm -U |
| | /usr/cluster/bin/scdidadm -v |
| |
The scdidadm utility administers the device identifier
(DID) pseudo device driver did(7).
The scdidadm utility performs the following primary
operations:
- Creates driver configuration files
- Modifies entries in the file
- Loads the current configuration into the kernel
- Lists the mapping between device entries and did driver instance numbers
The startup script /etc/init.d/bootcluster uses
the scdidadm utility to initialize the did
driver. You can also use scdidadm to update or query the
current device mapping between the devices present and the corresponding device
identifiers and did driver instance numbers.
The devfsadm(1m)
command creates the file system device entry points.
|
| |
The following options are supported:
- -c
- Performs a consistency
check against the kernel representation of the devices and the physical devices.
On failing a consistency check, an error message is displayed. The process
continues until all devices have been checked.
You need solaris.cluster.device.read RBAC authorization
to use this command option. See rbac(5).
- -C
- Removes all did references to underlying devices that have been detached from
the current node. Specify this option after the Solaris device commands have
been used to remove references to nonexistent devices on the cluster nodes.
You can only use this option from a node that is booted in cluster mode.
You need solaris.cluster.device.modify RBAC authorization
to use this command option. See rbac(5).
- -h
- Prints a header
when listing device mappings. This option is meaningful only when used with
the -l and -L options.
- -i
- Initializes the did driver. Use this option if you want to enable I/O requests to
the did driver.
You need solaris.cluster.device.modify RBAC authorization
to use this command option. See rbac(5).
- -l
- Lists the local
devices in the DID configuration file. The output of this command can be customized
using the -o option. When no -o options are
specified, the default listing displays the instance
number, the local fullpath, and the fullname.
You need solaris.cluster.device.read RBAC authorization
to use this command option. See rbac(5).
- -L
- Lists all the
paths, including those on remote hosts, of the devices in the DID configuration
file. The output of this command can be customized using the -o
option. When no -o options are specified, the default listing
displays the instance number, all local and remote fullpath strings, and the fullname.
You need solaris.cluster.device.read RBAC authorization
to use this command option. See rbac(5).
- -o fmt
- Lists the devices currently known to the did
driver according to the format specification fmt.
Multiple -o options can be specified. The fmt specification is interpreted as a comma-separated list of format
option arguments. This option is meaningful only when used with the -l and -L options. The available format option arguments
are the following:
-
instance
- Prints the instance number of the device known by the did
driver, for example, 1.
-
path
- Prints the physical path name of the device associated with this device
identifier, for example, /dev/rdsk/c0t3d0.
-
fullpath
- Prints the full physical path name of the device that is associated
with this device identifier. This path name includes the host, for example, phys-hostA:/dev/rdsk/c0t3d0.
-
host
- With the -L option, prints the names of all hosts that
have connectivity to the specified device, one per line. With the -l option, prints the name of the local host that has connectivity
to the specified device.
-
name
- Prints the DID name of the device associated with this device identifier,
for example, d1.
-
fullname
- Prints the full DID path name of the device associated with this device
identifier, for example, /dev/did/rdsk/d1.
-
diskid
- Prints the hexadecimal representation of the device identifier associated
with the instance of the device being listed.
-
asciidiskid
- Prints the ASCII representation of the device identifier associated
with the instance of the device being listed.
- -r
- Reconfigures
the database. When you specify this option, a thorough search of the rdsk and rmt device trees is conducted. A new
instance number is assigned for all device identifiers that were not recognized
before. A new path is added for each newly recognized device.
You can only use this option from a node that is booted in cluster mode.
You need solaris.cluster.device.modify RBAC authorization
to use this command option. See rbac(5).
- -R {path | instance_number | all}
- Performs a repair
procedure on a particular device instance. The argument to this command can
be either a particular physical device path that
has been replaced with a new device, or the instance_number
of the device that was just replaced. When used with the all
keyword, the scdidadm utility updates the configuration
data of all devices connected to the node.
You can only use this option from a node that is booted in cluster mode.
You need solaris.cluster.device.modify RBAC authorization
to use this command option. See rbac(5).
- -u
- Loads the device
identifier configuration table into the kernel. This option loads all the
currently known configuration information about device paths and their corresponding
instance numbers into the kernel.
You need solaris.cluster.device.modify RBAC authorization
to use this command option. See rbac(5).
- -U
- Converts an existing /etc/did.conf file into a set of Cluster Configuration Repository
(CCR) tables. If the tables already exist, this command
fails.
You need solaris.cluster.device.modify RBAC authorization
to use this command option. See rbac(5).
- -v
- Prints the version
number of this program.
|
| | Example 1. Adding Devices Attached to the Local Host to the CCRExample 2. Listing the Physical Path of the Device
| |
The following example lists the physical path of the device that corresponds
to instance 2 of the did driver:
| |
% scdidadm -l -o path 2
/dev/dsk/c1t4d0
|
|
Example 3. Specifying Multiple Format Options
| |
You can specify multiple format option arguments in either of the following
ways:
| |
% scdidadm -l -o path -o name 2
|
| |
% scdidadm -l -o path,name 2
|
In either example, the output might look like this:
|
Example 4. Performing a Repair Procedure
| |
The following example performs the repair procedure for a particular
device path. The device /dev/dsk/c1t4d0 has been replaced
with a new device with which a new device identifier is associated. The database
is updated to show that this new device identifier corresponds to the instance
number that was previously associated with the old device identifier:
|
Example 5. Performing a Repair Procedure
| |
An alternative method of performing a repair procedure is to use the
instance number associated with the device path. For example, if the instance
number for the device c1t4d0 in the previous example is 2, then the following syntax performs the same operation as the
previous example:
|
|
| |
The following exit values are returned:
-
0
- The command completed successfully.
-
1
- An error occurred.
|
| |
See attributes(5)
for descriptions of the following attributes:
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
| Availability | SUNWscu |
| Interface Stability | Evolving |
|
| |
devfsadm(1m), attributes(5), did(7)
Sun Cluster
3.1 System Administration Guide
|
| |
Each multiported tape drive or CD-ROM drive appears in the namespace
once per physical connection.
|
| Sun Cluster 3.1 | Go To Top | Last Changed 6 May 2003 |
Company Info
|
Contact
|
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
|