Description
In Sun[TM] Cluster 3.0 and 3.1 releases it was only possible to change "did" (device id) manually as it was automatically generated. In 3.2 it is still generated automatically however now there is an easy way to change it.

Steps to Follow
For various reasons it is sometimes necessary for cluster administrator to change "did" in Sun[TM] Cluster. The new 3.2 CLI command line interface provides a straight forward procedure to modify "did".

The following is an example how to rename did 6 to 12:
root# scdidadm -L
1        v4u-v120b:/dev/rdsk/c0t0d0     /dev/did/rdsk/d1
2        v4u-v120b:/dev/rdsk/c1t0d0     /dev/did/rdsk/d2
3        v4u-v120b:/dev/rdsk/c1t1d0     /dev/did/rdsk/d3
4        v4u-v120b:/dev/rdsk/c2t0d0     /dev/did/rdsk/d4
4        v4u-v120a:/dev/rdsk/c2t0d0     /dev/did/rdsk/d4
5        v4u-v120a:/dev/rdsk/c2t1d0     /dev/did/rdsk/d5
5        v4u-v120b:/dev/rdsk/c2t1d0     /dev/did/rdsk/d5
6        v4u-v120b:/dev/rdsk/c3t0d0     /dev/did/rdsk/d6  <===
6        v4u-v120a:/dev/rdsk/c3t0d0     /dev/did/rdsk/d6  <===
7        v4u-v120a:/dev/rdsk/c3t1d0     /dev/did/rdsk/d7
7        v4u-v120b:/dev/rdsk/c3t1d0     /dev/did/rdsk/d7
8        v4u-v120a:/dev/rdsk/c0t0d0     /dev/did/rdsk/d8
9        v4u-v120a:/dev/rdsk/c1t0d0     /dev/did/rdsk/d9
10       v4u-v120a:/dev/rdsk/c1t1d0     /dev/did/rdsk/d10
Note that scdidadm is the 3.1 and 3.0 ways of managing cluster did devices. The new 3.2 way of showing it is:
root# cldev show 6
=== DID Device Instances ===
DID Device Name:                                /dev/did/rdsk/d6
Full Device Path:                                v4u-v120a:/dev/rdsk/c3t0d0
Full Device Path:                                v4u-v120b:/dev/rdsk/c3t0d0
Replication:                                     none
default_fencing:                                 scsi3
root# cldevice rename -d 12 6
Moving instance "6" to "12".
To check the change:
root# scdidadm -L
1        v4u-v120b:/dev/rdsk/c0t0d0     /dev/did/rdsk/d1
2        v4u-v120b:/dev/rdsk/c1t0d0     /dev/did/rdsk/d2
3        v4u-v120b:/dev/rdsk/c1t1d0     /dev/did/rdsk/d3
4        v4u-v120b:/dev/rdsk/c2t0d0     /dev/did/rdsk/d4
4        v4u-v120a:/dev/rdsk/c2t0d0     /dev/did/rdsk/d4
5        v4u-v120a:/dev/rdsk/c2t1d0     /dev/did/rdsk/d5
5        v4u-v120b:/dev/rdsk/c2t1d0     /dev/did/rdsk/d5
7        v4u-v120a:/dev/rdsk/c3t1d0     /dev/did/rdsk/d7
7        v4u-v120b:/dev/rdsk/c3t1d0     /dev/did/rdsk/d7
8        v4u-v120a:/dev/rdsk/c0t0d0     /dev/did/rdsk/d8
9        v4u-v120a:/dev/rdsk/c1t0d0     /dev/did/rdsk/d9
10       v4u-v120a:/dev/rdsk/c1t1d0     /dev/did/rdsk/d10
12       v4u-v120a:/dev/rdsk/c3t0d0     /dev/did/rdsk/d12   <===
12       v4u-v120b:/dev/rdsk/c3t0d0     /dev/did/rdsk/d12   <===
Check change with new 3.2 CLI:
root# cldev show 12
=== DID Device Instances ===
DID Device Name:                                /dev/did/rdsk/d12
Full Device Path:                                v4u-v120b:/dev/rdsk/c3t0d0
Full Device Path:                                v4u-v120a:/dev/rdsk/c3t0d0
Replication:                                     none
default_fencing:                                 scsi3
root# cldev show 6
cldev:  (C727402) Could not locate instance "6".
(instance 6 is now gone)
Note that cldev command is a the same as cldevices command.