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 ...
104 Setting up I/O fencingSetting up I/O fencing for VCSTo initialize disks1 Make the new disks recognizable. On each node, enter:# lsdev -Cc disk2 If the Array Support Library (ASL) for the array you are adding is notinstalled, obtain and install it on each node before proceeding. The ASL forthe supported storage device you are adding is available from the disk arrayvendor or Symantec technical support.3 Verify that the ASL for the disk array is installed on each of the nodes. Runthe following command on each node and examine the output to verify theinstallation of ASL. The following output is a sample:# vxddladm listsupport allLIBNAMEVID==============================================================libvxCLARiiON.so DGClibvxcscovrts.so CSCOVRTSlibvxemc.soEMC4 Scan all disk drives and their attributes, update the VxVM device list, andreconfigure DMP with the new devices. Type:# vxdisk scandisksSee the Veritas Volume Manager documentation for details on adding andconfiguring disks.5 To initialize the disks as VxVM disks, use one of the following methods:Setting up coordinator disk groups■■Use the interactive vxdiskadm utility to initialize the disks as VxVMdisks.For more information see the Veritas Volume ManagersAdministrator’s Guide.Use the vxdisksetup command to initialize a disk as a VxVM disk.vxdisksetup -i device_name format=cdsdiskThe example specifies the CDS format:# vxdisksetup -i c2t13d0s2 format=cdsdiskRepeat this command for each disk you intend to use as a coordinatordisk.I/O fencing requires coordinator disks that are configured in a disk group andaccessible to each node in the cluster. These disks enables the vxfen driver toresolve potential split brain conditions and prevent data corruption. Make sureto meet the requirements for coordinator disks and then create the coordinatordisk group.
Setting up I/O fencingSetting up I/O fencing for VCS105Requirements for coordinator disksAfter adding and initializing disks for use as coordinator disks, make surecoordinator disks meet the following requirements:■■■■■■■You must have three coordinator disks.Each of the coordinator disks must use a physically separate disk or LUN.Each of the coordinator disks should exist on a different disk array, ifpossible.You must initialize each disk as a VxVM disk.The coordinator disks must support SCSI-3 persistent reservations.See “Testing the shared disks for SCSI-3” on page 101.The coordinator disks must exist in a disk group (for example,vxfencoorddg).See “Creating the coordinator disk group and setting the coordinatorattribute” on page 105.Symantec recommends using hardware-based mirroring for coordinatordisks.Creating the coordinator disk group and setting thecoordinator attributeFrom one node, create a disk group named vxfencoorddg. This group mustcontain three disks or LUNs.You must also set the coordinator attribute for the coordinator disk group.VxVM uses this attribute to prevent the reassignment of coordinator disks toother disk groups.Note that if you create a coordinator disk group as a regular disk group, you canturn on the coordinator attribute in Volume Manager. You do this with a vxdgset coordinator=on command.Refer to the Veritas Volume Manager Administrator’s Guide for details oncreating disk groups.The example procedure assumes that the disks have the device names c1t1d0s0,c2t1d0s0, and c3t1d0s0.
- Page 54 and 55: 54 Installing and configuring VCSIn
- Page 56 and 57: 56 Installing and configuring VCSIn
- Page 58 and 59: 58 Installing and configuring VCSIn
- Page 60 and 61: 60 Installing and configuring VCSIn
- 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 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 112 and 113: 112 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
104 Setting up I/O fencingSetting up I/O fencing <strong>for</strong> VCSTo initialize disks1 Make the new disks recognizable. On each node, enter:# lsdev -Cc disk2 If the Array Support Library (ASL) <strong>for</strong> the array you are adding is notinstalled, obtain and install it on each node be<strong>for</strong>e proceeding. The ASL <strong>for</strong>the supported storage device you are adding is available from the disk arrayvendor or Symantec technical support.3 Verify that the ASL <strong>for</strong> the disk array is installed on each of the nodes. Runthe following command on each node and examine the output to verify theinstallation of ASL. The following output is a sample:# vxddladm listsupport allLIBNAMEVID==============================================================libvxCLARiiON.so DGClibvxcscovrts.so CSCOVRTSlibvxemc.soEMC4 Scan all disk drives and their attributes, update the VxVM device list, andreconfigure DMP with the new devices. Type:# vxdisk scandisksSee the Veritas Volume Manager documentation <strong>for</strong> details on adding andconfiguring disks.5 To initialize the disks as VxVM disks, use one of the following methods:Setting up coordinator disk groups■■Use the interactive vxdiskadm utility to initialize the disks as VxVMdisks.For more in<strong>for</strong>mation see the Veritas Volume ManagersAdministrator’s <strong>Guide</strong>.Use the vxdisksetup command to initialize a disk as a VxVM disk.vxdisksetup -i device_name <strong>for</strong>mat=cdsdiskThe example specifies the CDS <strong>for</strong>mat:# vxdisksetup -i c2t13d0s2 <strong>for</strong>mat=cdsdiskRepeat this command <strong>for</strong> each disk you intend to use as a coordinatordisk.I/O fencing requires coordinator disks that are configured in a disk group andaccessible to each node in the cluster. These disks enables the vxfen driver toresolve potential split brain conditions and prevent data corruption. Make sureto meet the requirements <strong>for</strong> coordinator disks and then create the coordinatordisk group.
Change language