Use this procedure to create a logical unit number (LUN) from unassigned disk drives or remaining capacity. See theSun StorEdge RAID Manager Release Notes for the latest information about LUN administration.
You must use hardware RAID for Oracle Parallel Server (OPS) data stored on the storage array. Do not place OPS data under volume management control. You must place all non-OPS data that is stored on the storage arrays under volume management control. Use either hardware RAID, host-based software RAID, or both types of RAID to manage your non-OPS data.
Hardware RAID uses the storage array's or storage system's hardware redundancy to ensure that independent hardware failures do not impact data availability. If you mirror across separate storage arrays, host-based software RAID ensures that independent hardware failures do not impact data availability when an entire storage array is offline. Although you can use hardware RAID and host-based software RAID concurrently, you need only one RAID solution to maintain a high degree of data availability.
When you use host-based software RAID with hardware RAID, the hardware RAID levels you use affect hardware maintenance. If you use hardware RAID level 1, 3, or 5, you can perform most maintenance procedures without volume management disruptions. If you use hardware RAID level 0, some maintenance procedures require additional volume management administration because the availability of the LUNs is impacted.
Do not configure LUNs as quorum devices. The use of LUNs as quorum devices is not supported.
With all nodes booted and attached to the storage system, create the LUN on one node.
After the LUN formatting completes, a logical name for the new LUN appears in /dev/rdsk on all nodes. These nodes are attached to the storage system.
For the procedure about how to create a LUN, see the Sun StorEdge RAID Manager User’s Guide.
If the following warning message displays, ignore the message. Continue with the next step.
scsi: WARNING: /sbus@40,0/SUNW,socal@0,0/sf@1,0/ssd@w200200a0b80740db,4 (ssd0): corrupt label - wrong magic number
Use the format(1M) command to verify Solaris logical device names.
Copy the /etc/raid/rdac_address file from the node on which you created the LUN to the other node. If you copy this file to the other node, you ensure consistency across both nodes.
Ensure that the new logical name for the LUN that you created appears in the /dev/rdsk directory on both nodes.
On one node, update the global device namespace.
Ensure that the device ID numbers for the LUNs are the same on both nodes. In the sample output that follows, the device ID numbers are different.
# scdidadm -L ... 33 e07a:/dev/rdsk/c1t4d2 /dev/did/rdsk/d33 33 e07c:/dev/rdsk/c0t4d2 /dev/did/rdsk/d34
Are the device ID numbers that you received from running the scdidadm command in Step 5 the same for both nodes?
If you want a volume manager to manage the new LUN, incorporate the new LUN into a diskset or disk group.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.