Cluster Server Installation Guide for Solaris x64 5.0 - Storage ...
Cluster Server Installation Guide for Solaris x64 5.0 - Storage ... Cluster Server Installation Guide for Solaris x64 5.0 - Storage ...
112 Setting up I/O fencingAdditional I/O fencing informationALL tests on the disk /dev/rdsk/c4t1d0s2 have PASSED.The disk is now ready to be configured for I/O Fencing on node south as a COORDINATOR DISK.4 After you test all disks in the disk group, the vxfencoorddg disk group isready for use.Removing and replacing a failed diskIf a disk in the coordinator disk group fails verification, remove the failed disk or LUN from the vxfencoorddg disk group, replace it with another, and retest the disk group.If you need to replace a disk in an active coordinator disk group, refer to the troubleshooting procedure.See “Adding or removing coordinator disks” on page 125.To remove and replace a failed disk1 Use the vxdiskadm utility to remove the failed disk from the disk group.Refer to the Veritas Volume Manager Administrator’s Guide.2 Add a new disk to the node, initialize it, and add it to the coordinator diskgroup.See “Initializing disks” on page 103.See “Setting up coordinator disk groups” on page 104.3 Retest the disk group.Using the -r option for non-destructive testingTo test disk devices containing data you want to preserve, you can use the -roption with the -m, -f, or -g options, which are described in the followingsections. For example, to use the -m option and the -r option, you can run theutility by entering:# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -rmWhen invoked with the -r option, the utility does not use tests that write to thedisks. Therefore, it does not test the disks for all of the usual conditions of use.Using the -m optionReview the procedure to test the shared disks. The utility uses the -m option.See “Testing the shared disks for SCSI-3” on page 101.
Setting up I/O fencingAdditional I/O fencing information113Using the -f optionUse the -f option to test disks that are listed in a text file. For example, you cancreate a file to test two disks shared by systems north and south that mightresemble:north /dev/rdsk/c2t2d1s2 south /dev/rdsk/c3t2d1s2north /dev/rdsk/c2t2d1s2 south /dev/rdsk/c3t2d1s2where the first disk is listed in the first line and is seen by north as /dev/rdsk/c2t2d1s2 and by south as /dev/rdsk/c3t2d1s2. The other disk, in the second line,is seen as /dev/rdsk/c2t2d2s2 from north and /dev/rdsk/c3t2d2s2 from south.Typically, the list of disks could be extensive.Suppose you created the file named disks_blue. To test the disks, you wouldenter:# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -f disks_blueThe utility reports the test results one disk at a time, just as for the -m option.You can redirect the test results to a text file. Precede the command with “yes”to acknowledge that the testing destroys any data on the disks to be tested.Caution: Be advised that by redirecting the command’s output to a file, awarning that the testing destroys data on the disks cannot be seen until thetesting is done.For example:# yes | /opt/VRTSvcs/vxfen/bin/vxfentsthdw -f disks_blue > blue_test.txtUsing the -g optionUse the -g option to test all disks within a disk group. For example, you create atemporary disk group consisting of all disks in a disk array and test the group.Note: Do not import the test disk group as shared; that is, do not use the -soption.The utility reports the test results one disk at a time. You can redirect the testresults to a text file for review.# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -g red_disks_dg > redtest.txtAfter testing, destroy the disk group and put the disks into disk groups as youneed.
- Page 62 and 63: 62 Installing and configuring VCSIn
- Page 64 and 65: 64 Installing and configuring VCSIn
- Page 66 and 67: 66 Installing and configuring VCSIn
- Page 68 and 69: 68 Installing and configuring VCSPe
- Page 70 and 71: 70 Installing and configuring VCSPe
- Page 72 and 73: 72 Installing and configuring VCSPe
- Page 74 and 75: 74 Installing and configuring VCSPe
- Page 76 and 77: 76 Installing and configuring VCSCh
- Page 78 and 79: 78 Installing and configuring VCSAb
- Page 80 and 81: 80 Installing and configuring VCSAb
- Page 82 and 83: 82 Installing and configuring VCSUn
- Page 84 and 85: 84 Manually installing and configur
- Page 86 and 87: 86 Manually installing and configur
- Page 88 and 89: 88 Manually installing and configur
- Page 90 and 91: 90 Manually installing and configur
- Page 92 and 93: 92 Manually installing and configur
- Page 94 and 95: 94 Manually installing and configur
- Page 96 and 97: 96 Manually installing and configur
- Page 98 and 99: 98 Setting up I/O fencingAbout I/O
- Page 100 and 101: 100 Setting up I/O fencingPreparing
- Page 102 and 103: 102 Setting up I/O fencingPreparing
- Page 104 and 105: 104 Setting up I/O fencingSetting u
- Page 106 and 107: 106 Setting up I/O fencingSetting u
- Page 108 and 109: 108 Setting up I/O fencingSetting u
- Page 110 and 111: 110 Setting up I/O fencingAdditiona
- Page 114 and 115: 114 Setting up I/O fencingAdditiona
- Page 116 and 117: 116 Setting up I/O fencingHow I/O f
- Page 118 and 119: 118 Setting up I/O fencingHow I/O f
- Page 120 and 121: 120 Setting up I/O fencingAbout the
- Page 122 and 123: 122 Setting up I/O fencingTroublesh
- Page 124 and 125: 124 Setting up I/O fencingTroublesh
- Page 126 and 127: 126 Setting up I/O fencingTroublesh
- Page 128 and 129: 128 Setting up I/O fencingTroublesh
- Page 130 and 131: 130 Verifying the VCS installationV
- Page 132 and 133: 132 Verifying the VCS installationV
- Page 134 and 135: 134 Verifying the VCS installationV
- Page 136 and 137: 136 Verifying the VCS installationV
- Page 138 and 139: 138 Verifying the VCS installationV
- Page 140 and 141: 140 Verifying the VCS installationV
- Page 142 and 143: 142 Verifying the VCS installationA
- Page 144 and 145: 144 Upgrading to VCS 5.0Upgrading V
- Page 146 and 147: 146 Upgrading to VCS 5.0Upgrading V
- Page 148 and 149: 148 Upgrading to VCS 5.0Upgrading V
- Page 150 and 151: 150 Upgrading to VCS 5.0Upgrading V
- Page 152 and 153: 152 Upgrading to VCS 5.0Upgrading t
- Page 154 and 155: 154 Upgrading to VCS 5.0
- Page 156 and 157: 156 Adding and removing cluster nod
- Page 158 and 159: 158 Adding and removing cluster nod
- Page 160 and 161: 160 Adding and removing cluster nod
112 Setting up I/O fencingAdditional I/O fencing in<strong>for</strong>mationALL tests on the disk /dev/rdsk/c4t1d0s2 have PASSED.The disk is now ready to be configured <strong>for</strong> I/O Fencing on node south as a COORDINATOR DISK.4 After you test all disks in the disk group, the vxfencoorddg disk group isready <strong>for</strong> use.Removing and replacing a failed diskIf a disk in the coordinator disk group fails verification, remove the failed disk or LUN from the vxfencoorddg disk group, replace it with another, and retest the disk group.If you need to replace a disk in an active coordinator disk group, refer to the troubleshooting procedure.See “Adding or removing coordinator disks” on page 125.To remove and replace a failed disk1 Use the vxdiskadm utility to remove the failed disk from the disk group.Refer to the Veritas Volume Manager Administrator’s <strong>Guide</strong>.2 Add a new disk to the node, initialize it, and add it to the coordinator diskgroup.See “Initializing disks” on page 103.See “Setting up coordinator disk groups” on page 104.3 Retest the disk group.Using the -r option <strong>for</strong> non-destructive testingTo test disk devices containing data you want to preserve, you can use the -roption with the -m, -f, or -g options, which are described in the followingsections. For example, to use the -m option and the -r option, you can run theutility by entering:# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -rmWhen invoked with the -r option, the utility does not use tests that write to thedisks. There<strong>for</strong>e, it does not test the disks <strong>for</strong> all of the usual conditions of use.Using the -m optionReview the procedure to test the shared disks. The utility uses the -m option.See “Testing the shared disks <strong>for</strong> SCSI-3” on page 101.