test

Sun Cluster 3.0 U1 Hardware Guide

Configuring a Sun StorEdge A3500/A3500FC System

This section describes the procedures for configuring a StorEdge A3500/A3500FC system after installing Sun Cluster software. Table 7-1 lists these procedures.

Configuring a StorEdge A3500/A3500FC system before installing Sun Cluster software is the same as doing so in a non-cluster environment. For procedures on configuring StorEdge A3500/A3500FC systems before installing Sun Cluster, see the Sun StorEdge RAID Manager User's Guide.

Table 7-1 Task Map: Configuring StorEdge A3500/A3500FC Disk Drives

Task 

For Instructions, Go To 

Create a logical unit number (LUN). 

"How to Create a LUN"

Remove a LUN. 

"How to Delete a LUN"

Reset the StorEdge A3500/A3500FC configuration. 

"How to Reset StorEdge A3500/A3500FC LUN Configuration"

Rebalance running LUNs. 

Follow the same procedure that is used in a non-cluster environment. 

Sun StorEdge RAID Manager User's Guide

 

Sun StorEdge RAID Manager Release Notes

Create a hot spare. 

Follow the same procedure that is used in a non-cluster environment. 

Sun StorEdge RAID Manager User's Guide

 

Sun StorEdge RAID Manager Release Notes

Delete a hot spare. 

Follow the same procedure that is used in a non-cluster environment. 

Sun StorEdge RAID Manager User's Guide

 

Sun StorEdge RAID Manager Release Notes

Increase the size of a drive group. 

Follow the same procedure that is used in a non-cluster environment. 

Sun StorEdge RAID Manager User's Guide

 

Sun StorEdge RAID Manager Release Notes

How to Create a LUN

Use this procedure to create a logical unit number (LUN) from unassigned disk drives or remaining capacity. See the Sun StorEdge RAID Manager Release Notes for the latest information about LUN administration.

This product supports the use of hardware RAID and host-based software RAID. For host-based software RAID, this product supports RAID levels 0+1 and 1+0.

Note -

You must use hardware RAID for Oracle Parallel Server (OPS) data stored on the StorEdge A3500/A3500FC arrays. Do not place OPS data under volume management control. You must place all non-OPS data that is stored on the 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 StorEdge A3500/A3500FC system's hardware redundancy to ensure that independent hardware failures do not impact data availability. By mirroring across separate arrays, host-based software RAID ensures that independent hardware failures do not impact data availability when an entire 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.

Note -

When you use host-based software RAID with hardware RAID, the hardware RAID levels you use affect the hardware maintenance procedures because they affect volume management administration. If you use hardware RAID level 1, 3, or 5, you can perform most maintenance procedures in "Maintaining a StorEdge A3500/A3500FC System" without volume management disruptions. If you use hardware RAID level 0, some maintenance procedures in "Maintaining a StorEdge A3500/A3500FC System" require additional volume management administration because the availability of the LUNs is impacted.

  1. With all cluster nodes booted and attached to the StorEdge A3500/A3500FC system, create the LUN on one node.

    Shortly after the LUN formatting completes, a logical name for the new LUN appears in /dev/rdsk on all cluster nodes that are attached to the StorEdge A3500/A3500FC system.

    For the procedure on creating a LUN, see the Sun StorEdge RAID Manager User's Guide.

    Note -

    If the following warning message is displayed, ignore it and 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

    Note -

    Use the format(1M) command to verify Solaris logical device names.

  2. Copy the /etc/raid/rdac_address file from the node on which you created the LUN to the other node to ensure consistency across both nodes.

  3. Ensure that the new logical name for the LUN you created in Step 1 appears in the /dev/rdsk directory on both nodes by running the hot_add command on both nodes:


    # /etc/raid/bin/hot_add

  4. On one node, update the global device namespace:


    # scgdevs

  5. Use the scdidadm command to verify that the DID numbers for the LUNs are the same on both nodes. In the sample output that follows, the DID numbers are different:


    # scdidadm -L
... 
33       e07a:/dev/rdsk/c1t4d2          /dev/did/rdsk/d33
33       e07c:/dev/rdsk/c0t4d2          /dev/did/rdsk/d33

  6. Are the DID numbers you received from running the scdidadm command in Step 5 the same for both your nodes?

  7. If you want a volume manager to manage the new LUN you created in Step 1, run the appropriate Solstice DiskSuite or VERITAS Volume Manager commands to incorporate the new LUN into a diskset or disk group.

    For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

Note -

Do not configure StorEdge A3500/A3500FC LUNs as quorum devices; the use of StorEdge A3500/A3500FC LUNs as quorum devices is not supported.

How to Delete a LUN

Use this procedure to delete a LUN(s). See the Sun StorEdge RAID Manager Release Notes for the latest information about LUN administration.

Caution - Caution -

This procedure removes all data on the LUN you delete.

Caution - Caution -

Do not delete LUN 0.

  1. From one node that is connected to the StorEdge A3500/A3500FC system, use the format command to determine the paths to the LUN you are deleting (sample output follows):


    # format
AVAILABLE DISK SELECTIONS:
0. c0t5d0 <SYMBIOS-StorEdgeA3500FCr-0301 cyl3 alt2 hd64 sec64>
/pseudo/rdnexus@0/rdriver@5,0
1. c0t5d1 <SYMBIOS-StorEdgeA3500FCr-0301 cyl2025 alt2 hd64 sec64>
/pseudo/rdnexus@0/rdriver@5,1

  2. Does a volume manager manage the LUN you are deleting?

    • If not, go to Step 3.

    • If a volume manager does manage the LUN, run the appropriate Solstice DiskSuite or VERITAS Volume Manager commands to remove the LUN from any diskset or disk group. For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation. See the following paragraph for additional VERITAS Volume Manager commands that are required.

      LUNs that were managed by VERITAS Volume Manager must be completely removed from VERITAS Volume Manager control before you can delete them. To remove the LUNs, after you delete the LUN from any disk group, use the following commands: 


      # vxdisk offline cNtXdY
# vxdisk rm cNtXdY

  3. From one node, delete the LUN.

    For the procedure on deleting a LUN, see the Sun StorEdge RAID Manager User's Guide.

  4. Remove the paths to the LUN(s) you are deleting:


    # rm /dev/rdsk/cNtXdY*
# rm /dev/dsk/cNtXdY*

# rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  5. Use the lad command to determine the alternate paths to the LUN(s) you are deleting.

    The RAID Manager software creates two paths to the LUN in the /dev/osa/dev/rdsk directory. Substitute the cNtXdY number from the other controller module in the disk array to determine the alternate path.

    For example, with this configuration:


    # lad
c0t5d0 1T93600714 LUNS: 0 1
c1t4d0 1T93500595 LUNS: 2

    The alternate paths would be:


    /dev/osa/dev/dsk/c1t4d1*
/dev/osa/dev/rdsk/c1t4d1*

  6. Remove the alternate paths to the LUN(s) you are deleting:


    # rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  7. On both nodes, remove all obsolete device IDs (DID)s:


    # scdidadm -C

  8. Switch resources and device groups off the node:


    # scswitch -Sh nodename

  9. Shut down the node:


    # shutdown -y -g0 -i0

  10. Boot the node and wait for it to rejoin the cluster:


    # boot -r

  11. Repeat Step 3 through Step 10 on the other node that is attached to the StorEdge A3500/A3500FC system.

How to Reset StorEdge A3500/A3500FC LUN Configuration

Use this procedure to reset StorEdge A3500/A3500FC LUN configuration.

Caution - Caution -

Resetting LUN configuration results in a new DID number being assigned to LUN 0. This is because the software assigns a new worldwide number (WWN) to the new LUN.

  1. From one node that is connected to the StorEdge A3500/A3500FC system, use the format command to determine the paths to the LUN(s) you are resetting, as shown in the following example (sample output shown below):


    # format
AVAILABLE DISK SELECTIONS:
0. c0t5d0 <SYMBIOS-StorEdgeA3500FCr-0301 cyl3 alt2 hd64 sec64>
/pseudo/rdnexus@0/rdriver@5,0
1. c0t5d1 <SYMBIOS-StorEdgeA3500FCr-0301 cyl2025 alt2 hd64 sec64>
/pseudo/rdnexus@0/rdriver@5,1

  2. Does a volume manager manage the LUN(s) on the controller module you are resetting?

    • If not, go to Step 3.

    • If a volume manager does manage the LUN, run the appropriate Solstice DiskSuite or VERITAS Volume Manager commands to remove the LUN from any diskset or disk group. For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation. See the following paragraph for additional VERITAS Volume Manager commands that are required.

      LUNs that were managed by VERITAS Volume Manager must be completely removed from VERITAS Volume Manager control before you can delete them. To remove the LUNs, after you delete the LUN from any disk group, use the following commands: 


      # vxdisk offline cNtXdY
# vxdisk rm cNtXdY

  3. On one node, reset the LUN configuration.

    For the procedure for resetting StorEdge A3500/A3500FC LUN configuration, see the Sun StorEdge RAID Manager User's Guide.

    Note -

    Use the format command to verify Solaris logical device names.

  4. Set the controller module back to active/active mode (it was set to active/passive when reset).

    For more information on controller modes, see the Sun StorEdge RAID Manager Installation and Support Guide and the Sun StorEdge RAID Manager User's Guide.

  5. By using the format command, label the new LUN 0.

  6. Remove the paths to the old LUN(s) you reset:


    # rm /dev/rdsk/cNtXdY*
# rm /dev/dsk/cNtXdY*

# rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  7. Use the lad command to determine the alternate paths to the old LUN(s) you reset.

    The RAID Manager software creates two paths to the LUN in the /dev/osa/dev/rdsk directory. Substitute the cNtXdY number from the other controller module in the disk array to determine the alternate path.

    For example, with this configuration:


    # lad
c0t5d0 1T93600714 LUNS: 0 1
c1t4d0 1T93500595 LUNS: 2

    The alternate paths would be as follows. 


    /dev/osa/dev/dsk/c1t4d1*
/dev/osa/dev/rdsk/c1t4d1*

  8. Remove the alternate paths to the old LUN(s) you reset:


    # rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  9. Update device namespaces on both nodes:


    devfsadm -C

  10. Remove all obsolete DIDs on both nodes:


    # scdidadm -C

  11. Switch resources and device groups off the node:


    # scswitch -Sh nodename

  12. Shut down the node:


    # shutdown -y -g0 -i0

  13. Boot the node and wait for it to rejoin the cluster:


    # boot -r

    Note -

    If the following error message appears, ignore it and continue with the next step. The DID will be updated when the procedure is complete. device id for '/dev/rdsk/c0t5d0' does not match physical disk's id.

  14. After the node has rebooted and joined the cluster, repeat Step 6 through Step 13 on the other node that is attached to the StorEdge A3500/A3500FC system.

    The DID number for the original LUN 0 is removed and a new DID is assigned to LUN 0.

How to Correct Mismatched DID Numbers

Use this section to correct mismatched device ID (DID) numbers that might appear during the creation of A3500/A3500FC LUNs. You correct the mismatch by deleting Solaris and Sun Cluster paths to the LUNs that have DID numbers that are different. After rebooting, the paths are corrected.

Note -

Use this procedure only if you are directed to do so from "How to Create a LUN".

  1. From one node that is connected to the StorEdge A3500/A3500FC system, use the format command to determine the paths to the LUN(s) that have different DID numbers:


    # format

  2. Remove the paths to the LUN(s) that have different DID numbers:


    # rm /dev/rdsk/cNtXdY*
# rm /dev/dsk/cNtXdY*

# rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  3. Use the lad command to determine the alternate paths to the LUN(s) that have different DID numbers.

    The RAID Manager software creates two paths to the LUN in the /dev/osa/dev/rdsk directory. Substitute the cNtXdY number from the other controller module in the disk array to determine the alternate path.

    For example, with this configuration:


    # lad
c0t5d0 1T93600714 LUNS: 0 1
c1t4d0 1T93500595 LUNS: 2

    The alternate paths would be as follows.


    /dev/osa/dev/dsk/c1t4d1*
/dev/osa/dev/rdsk/c1t4d1*

  4. Remove the alternate paths to the LUN(s) that have different DID numbers:


    # rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  5. On both nodes, remove all obsolete DIDs:


    # scdidadm -C

  6. Switch resources and device groups off the node:


    # scswitch -Sh nodename

  7. Shut down the node:


    # shutdown -y -g0 -i0

  8. Boot the node and wait for it to rejoin the cluster:


    # boot -r

  9. Repeat Step 1 through Step 8 on the other node that is attached to the StorEdge A3500/A3500FC system.

  10. Return to "How to Create a LUN".