Oracle Solaris Cluster 3.3 System Manual page 24

Configuring Storage Arrays
Ensure that the new logical name for the LUN that you created appears in the /dev/rdsk
3
directory on both nodes.
# /etc/raid/bin/hot_add
On one node, update the global device namespace.
4
# cldevice populate
Ensure that the device ID numbers for the LUNs are the same on both nodes. In the sample
5
output that follows, the device ID numbers are different.
For an example of output indicating that the ID numbers have not been properly updated, see
Example
Run the following command:
# cldevice show
If the device ID numbers that you received from running the cldevice show or scdidadm
6
command in
If the device ID numbers that you received from running the cldevice show or scdidadm
7
command are different, perform the procedure in
Numbers"on page 29
(A1000 Only) If you want a volume manager to manage the new LUN, incorporate the new LUN
8
into a diskset or disk group.
For more information, see your Solaris Volume Manager or Veritas Volume Manager
documentation.
Note –
Verifying the Device IDs
Example 1–1
Step 5
are the same on both nodes. In the sample output that follows, the device ID numbers are
different.
# cldevice show
...
DID Device Name:
Full Device Path:
Full Device Path:
Replication:
default_fencing:
24 Oracle Solaris Cluster 3.3 With StorEdge A1000 Array, Netra st A1000 Array, or StorEdge A3500 System Manual
• May 2011, Revision A
1–1.
Step 5 are the same for both nodes, proceed to
before you proceed to
The StorEdge A3500 system does not support using LUNs as quorum devices.
in the preceding procedure directs you to verify that the device ID numbers for the LUNs
Step 8.
"How to Correct Mismatched Device ID
Step 8 of this procedure.
/dev/did/rdsk/d3
phys-schost-2:/dev/rdsk/c1t3d0
phys-schost-1:/dev/rdsk/c1t3d1
none
global