Important: The following process is applicable to Solaris systems running 5.0 MP3 or higher.
The following EMC CLARiiON devices are presented to a Solaris server using Veritas DMP as the multipathing solution.
Array Volume Identifier Support
As configurations in data centers scale up and more SAN devices and nodes have to be managed, there is a greater need for consistency and predictability in device naming.
Storage Foundation(SF) support two device naming schemes - Operating System Native (OSN) naming and Enclosure Based Names (EBN)
Enclosure name consistency usually is not a problem and even when hosts are connected to multiple enclosures of the same type, the number of enclosures is small enough that consistency can be ensured through manual configurations.
Device index consistency that uniquely identifies the device within that enclosure on the other hand can be inconsistent.
To overcome this limitation SF 5.0 MP3 introduces a third naming convention sometimes referred as "EBN_AVID" to enable device name consistency
EBN = Enclosure Based Naming
AVID = Array Volume Identifier
How the introduction of the AVID features makes life easier
With the introduction of the new EBN_AVID naming scheme, identifying storage devices becomes far easier with consistent device naming across multiple nodes connected to the same storage and the disk access name will never change as it is based on the name defined at the array level.
When SF does not have access to a device AVID, it retrieves another unique LUN identifier called LUN serial number
SF will sort the devices based on the LUN serial number (LSN) and uses the index to create the suffix for the device name. All nodes that see the same set of devices, will have the same sorted list, leading to consistent device indices across the cluster.
Finally, Storage Foundation supports a scalable framework allowing users to fully customize the device names on a host by applying a 'device naming file' that associates custom names with cabinet and LUN serial numbers.
# vxddladm get namingscheme
NAMING_SCHEME PERSISTENCE LOWERCASE USE_AVID
============================================================
Enclosure Based Yes Yes Yes
Note: EBN_AVID co-existence with EMC PowerPath controlled devices is not supported, therefore, the EBN_AVID naming convention is suppressed
How to view the EMC CLARiiON devices associated with StorageGroup "vcssx065_066"
Sample output
# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 storagegroup -list -gname vcssx065_066 -host
Storage Group Name: vcssx065_066
Storage Group UID: 24:1D:66:4B:F2:12:DE:11:91:E0:00:60:16:1E:66:AC
HBA/SP Pairs:
HBA UID SP Name SPPort
------- ------- ------
20:00:00:E0:8B:14:0C:04:21:00:00:E0:8B:14:0C:04 SP A 4
Host name: vcssx066
20:00:00:E0:8B:14:0C:04:21:00:00:E0:8B:14:0C:04 SP B 4
Host name: vcssx066
HLU/ALU Pairs:
HLU Number ALU Number
---------- ----------
0 600
1 601
2 602
3 604
5 605
4 603
HLU/SLU Pairs:
HLU No. SNAP SHOT UID SNAP SHOT NAME
------ ----------------------------------------------- --------------
6 60:06:01:60:3A:31:1F:00:36:8A:EF:49:4E:D1:DF:11 lun600_fd_snapshot
7 60:06:01:60:3A:31:1F:00:38:9B:D5:9F:59:D1:DF:11 lun601_fd_snapshot
8 60:06:01:60:3A:31:1F:00:7C:EB:C3:03:5A:D1:DF:11 lun602_fd_snapshot
Shareable: YES
How to view the EMC MirrorView SnapView session content for EMC CLARiiON IP address "10.209.64.29"
Sample output
# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -listsessions
Name of the session: VCS_fd_session
Number of read requests serviced by the snapview cache pool: 0
Total number of read requests on the snapview logical unit: 0
Number of reads from the TLU: 0
Number of writes requests in the session: 0
Number of writes requests to cache that triggered a COW: 0
Total number of writes requests on the snapview target logical unit: 0
Number of writes requests larger than the chunk size: 0
Cache Capacity in GB: 87.879211
Session Usage: 0
List of Target Logical Units: LUN 600, LUN 602, LUN 601
snap Logical Units UID: 60:06:01:60:3A:31:1F:00:36:8A:EF:49:4E:D1:DF:11, 60:06:01:60:3A:31:1F:00:7C:EB:C3:03:5A:D1:DF:11, 60:06:01:60:3A:31:1F:00:38:9B:D5:9F:
59:D1:DF:11
snap Logical Units Name: lun600_fd_snapshot, lun602_fd_snapshot, lun601_fd_snapshot
Session in persistence: YES
Session creation time: 10/05/10 19:56:23
Session state: Normal
Ensure no stale device entries exist and refresh Volume Manager
Note: It is critical that no Stale device entries exist in /dev/[r]dsk prior to the discover of the new EMC CLARiiON devices.
# devfsadm -Cvc disk
Refresh Volume Manager and update the /etc/vx/disk.info file
# vxdisk scandisks
# vxddladm assign names
Enable Solaris to discover the new EMC CLARiiON SnapView (snapshot) devices
# cfgadm -alo show_FCP_dev
Ap_Id Type Receptacle Occupant Condition
c1 fc-fabric connected configured unknown
c1::5006016041e02d28,0 disk connected configured unknown
c1::5006016841e0a366,0 disk connected configured unknown
c1::5006016841e0a366,1 disk connected configured unknown
c1::5006016841e0a366,2 disk connected configured unknown
c1::5006016841e0a366,3 disk connected configured unknown
c1::5006016841e0a366,4 disk connected configured unknown
c1::5006016841e0a366,5 disk connected configured unknown
c1::5006016841e0a366,6 disk connected configured unknown
c1::5006016841e0a366,7 disk connected configured unknown
c1::5006016841e0a366,8 disk connected configured unknown
c1::50060e8005650921 unavailable connected unconfigured failed
#
Note: The EMC CLARiiON snapshot devices are "5006016841e0a366,6", "5006016841e0a366,7" and "5006016841e0a366,8".
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0 auto:sliced c2t0d0 rootdg online
disk_1 auto:sliced c2t0d0-s0 rootdg2 online
emc_clariion0_600 auto - - error
emc_clariion0_601 auto - - error
emc_clariion0_602 auto - - error
emc_clariion0_603 auto - - error
emc_clariion0_604 auto - - error
emc_clariion0_605 auto - - error
# vxdisk scandisks
Note: The EMC CLARiiON snapshot devices are now visible to Volume Manager
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0 auto:sliced c2t0d0 rootdg online
disk_1 auto:sliced c2t0d0-s0 rootdg2 online
emc_clariion0_600 auto - - error
emc_clariion0_600_1 auto:cdsdisk - - online
emc_clariion0_601 auto - - error
emc_clariion0_601_1 auto:cdsdisk - - online
emc_clariion0_602 auto - - error
emc_clariion0_602_1 auto:cdsdisk - - online
emc_clariion0_603 auto - - error
emc_clariion0_604 auto - - error
emc_clariion0_605 auto - - error
Note: The Volume Manager related diskgroup(s) can be imported at this time.