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 ...
124 Setting up I/O fencingTroubleshooting I/O fencingregistered with them. Given this conflicting information about system 2,system 1 does not join the cluster and returns an error from vxfenconfig thatresembles:vxfenconfig: ERROR: There exists the potential for a preexisting split-brain. The coordinator disks list no nodes which are in the current membership. However, they also list nodes which are not in the current membership.I/O Fencing Disabled!Also, the following information is displayed on the console: vxfen: WARNING: Potentially a preexisting split-brain. Dropping out of cluster. Refer to user documentation for steps required to clear preexisting split-brain. I/O Fencing DISABLED! gab: GAB:20032: Port b closedHowever, the same error can occur when the private network links are workingand both systems go down, system 1 restarts, and system 2 fails to come backup. From the view of the cluster from system 1, system 2 may still have theregistrations on the coordinator disks.Case 1: system 2 up, system 1 ejected(actual potential split brain)Determine if system1 is up or not. If it is up and running, shut it down and repairthe private network links to remove the split brain condition. restart system 1.Case 2: system 2 down, system 1 ejected(apparent potential split brain)1 Physically verify that system 2 is down.2 Verify the systems currently registered with the coordinator disks. Use thefollowing command:# vxfenadm -g all -f /etc/vxfentabThe output of this command identifies the keys registered with thecoordinator disks.3 Clear the keys on the coordinator disks as well as the data disks using thecommand /opt/VRTSvcs/rac/bin/vxfenclearpre.See “Clearing keys after split brain using vxfenclearpre command” onpage 125.4 Make any necessary repairs to system 2 and restart.
Setting up I/O fencingTroubleshooting I/O fencing125Clearing keys after split brain using vxfenclearpre commandWhen you have encountered a split brain condition, use the vxfenclearprecommand to remove SCSI-3 registrations and reservations on the coordinatordisks as well as on the data disks in all shared disk groups.To clear keys after split brain1 Shut down all other nodes in the cluster that have access to the sharedstorage. This prevents data corruption.2 Start the script:# cd /opt/VRTSvcs/vxfen/bin# ./vxfenclearpre3 Read the script’s introduction and warning. Then, you can choose to let thescript run.Do you still want to continue: [y/n] (default : n) yInformational messages resembling the following may appear on theconsole of one of the nodes in the cluster when a node is ejected from a disk/LUN: scsi: WARNING: /sbus@3,0/lpfs@0,0/sd@0,1(sd91): Error for Command: Error Level: Informational scsi: Requested Block: 0 Error Block 0 scsi: Vendor: Serial Number: 0400759B006E scsi: Sense Key: Unit Attention scsi: ASC: 0x2a (), ASCQ: 0x4, FRU: 0x0These informational messages may be ignored.Cleaning up the coordinator disks...Cleaning up the data disks for all shared disk groups...Successfully removed SCSI-3 persistent registration and reservations from the coordinator disks as well as the shared data disks.Reboot the server to proceed with normal cluster startup...#4 Restart all nodes in the cluster.Adding or removing coordinator disksReview the following information to:■Replace coordinator disk in the coordinator disk group
- 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 120 and 121: 120 Setting up I/O fencingAbout the
- Page 122 and 123: 122 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
- Page 170 and 171: 170 Installing VCS on a single node
- Page 172 and 173: 172 Installing VCS on a single node
124 Setting up I/O fencingTroubleshooting I/O fencingregistered with them. Given this conflicting in<strong>for</strong>mation about system 2,system 1 does not join the cluster and returns an error from vxfenconfig thatresembles:vxfenconfig: ERROR: There exists the potential <strong>for</strong> a preexisting split-brain. The coordinator disks list no nodes which are in the current membership. However, they also list nodes which are not in the current membership.I/O Fencing Disabled!Also, the following in<strong>for</strong>mation is displayed on the console: vxfen: WARNING: Potentially a preexisting split-brain. Dropping out of cluster. Refer to user documentation <strong>for</strong> steps required to clear preexisting split-brain. I/O Fencing DISABLED! gab: GAB:20032: Port b closedHowever, the same error can occur when the private network links are workingand both systems go down, system 1 restarts, and system 2 fails to come backup. From the view of the cluster from system 1, system 2 may still have theregistrations on the coordinator disks.Case 1: system 2 up, system 1 ejected(actual potential split brain)Determine if system1 is up or not. If it is up and running, shut it down and repairthe private network links to remove the split brain condition. restart system 1.Case 2: system 2 down, system 1 ejected(apparent potential split brain)1 Physically verify that system 2 is down.2 Verify the systems currently registered with the coordinator disks. Use thefollowing command:# vxfenadm -g all -f /etc/vxfentabThe output of this command identifies the keys registered with thecoordinator disks.3 Clear the keys on the coordinator disks as well as the data disks using thecommand /opt/VRTSvcs/rac/bin/vxfenclearpre.See “Clearing keys after split brain using vxfenclearpre command” onpage 125.4 Make any necessary repairs to system 2 and restart.
Change language