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 ...
120 Setting up I/O fencingAbout the vxfenadm utilityTable 5-5I/O fencing scenariosEvent Node A: What Node B: What Operator actionhappens?happens?The diskarraycontainingtwo of thethreecoordinatordisks ispowered off.Node A continues tooperate as long as nonodes leave the cluster.Node B continues tooperate as long as nonodes leave thecluster.Node B leavesthe clusterand the diskarray is stillpowered off.Node A races for amajority of coordinatordisks. Node A failsbecause only one ofthree coordinator disksis available. Node Aremoves itself from thecluster.Node B leaves thecluster.Power on failed diskarray and restart I/Ofencing driver toenable Node A toregister with allcoordinator disks.About the vxfenadm utilityAdministrators can use the vxfenadm command to troubleshoot and test fencingconfigurations. The command’s options for use by administrators are:-g read and display keys-i read SCSI inquiry information from device-m register with disks-n make a reservation with disks-p remove registrations made by other systems-r read reservations-x remove registrations
Setting up I/O fencingAbout the vxfenadm utility121Registration key formattingThe key defined by VxVM associated with a disk group consists of seven bytesmaximum. This key becomes unique among the systems when the VxVMprefixes it with the ID of the system. The key used for I/O fencing, therefore,consists of eight bytes.0 7NodeIDVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedThe keys currently assigned to disks can be displayed by using the vxfenadmcommand. For example, from the system with node ID 1, display the key for the disk /dev/rdsk/c2t1d0s2 by entering:# vxfenadm -g /dev/rdsk/c2t1d0s2Reading SCSI Registration Keys...Device Name: /dev/rdsk/c2t1d0s2Total Number of Keys: 1key[0]:Key Value [Numeric Format]: 65,45,45,45,45,45,45,45Key Value [Character Format]: A------The -g option of vxfenadm displays all eight bytes of a key value in two formats.In the numeric format, the first byte, representing the Node ID, contains thesystem ID plus 65. The remaining bytes contain the ASCII values of the letters ofthe key, in this case, “-------”. In the next line, the node ID 0 is expressed as “A;”node ID 1 would be “B.”
- 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 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 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
- Page 162 and 163: 162 Adding and removing cluster nod
- Page 164 and 165: 164 Adding and removing cluster nod
- Page 166 and 167: 166 Installing VCS on a single node
- Page 168 and 169: 168 Installing VCS on a single node
Setting up I/O fencingAbout the vxfenadm utility121Registration key <strong>for</strong>mattingThe key defined by VxVM associated with a disk group consists of seven bytesmaximum. This key becomes unique among the systems when the VxVMprefixes it with the ID of the system. The key used <strong>for</strong> I/O fencing, there<strong>for</strong>e,consists of eight bytes.0 7NodeIDVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedVxVMDefinedThe keys currently assigned to disks can be displayed by using the vxfenadmcommand. For example, from the system with node ID 1, display the key <strong>for</strong> the disk /dev/rdsk/c2t1d0s2 by entering:# vxfenadm -g /dev/rdsk/c2t1d0s2Reading SCSI Registration Keys...Device Name: /dev/rdsk/c2t1d0s2Total Number of Keys: 1key[0]:Key Value [Numeric Format]: 65,45,45,45,45,45,45,45Key Value [Character Format]: A------The -g option of vxfenadm displays all eight bytes of a key value in two <strong>for</strong>mats.In the numeric <strong>for</strong>mat, the first byte, representing the Node ID, contains thesystem ID plus 65. The remaining bytes contain the ASCII values of the letters ofthe key, in this case, “-------”. In the next line, the node ID 0 is expressed as “A;”node ID 1 would be “B.”