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 ...
180 Advanced topics related to installing VCSReconciling major/minor numbers for NFS shared disks■If the instance numbers are being used on both nodes, edit /etc/path_to_inst on both nodes. Change the instance number associatedwith the device name to an unused number greater than the highestnumber used by other devices. For example, the output of step b showsthe instance numbers used by all devices (from 0 to 29), so edit the file /etc/path_to_inst on each node and reset the instance numbers to30.5 Type the following command to reboot each node on which /etc/path_to_inst was modified:# reboot -- -rvChecking the major and minor number for VxVM volumesThe following sections describe checking and changing, if necessary, the majorand minor numbers for VxVM volumes used by cluster systems.To check major and minor numbers on VxVM volumes1 Place the VCS command directory in your path. For example:# export PATH=$PATH:/usr/sbin:/sbin:/opt/VRTS/bin2 To list the devices, use the ls -lL block_device command on eachnode:# ls -lL /dev/vx/dsk/shareddg/vol3On Node A, the output may resemble:brw------- 1 root root 32,43000 Mar 22 16:41 /dev/vx/dsk/shareddg/vol3On Node B, the output may resemble:brw------- 1 root root 36,43000 Mar 22 16:41 /dev/vx/dsk/shareddg/vol33 Import the associated shared disk group on each node.4 Use the following command on each node exporting an NFS file system. Thecommand displays the major numbers for vxio and vxspec used by VeritasVolume Manager (other major numbers are also displayed, but only vxioand vxspec are of concern for reconciliation):# grep vx /etc/name_to_majorOutput on Node A:vxdmp 30vxio 32vxspec 33vxfen 87vxglm 91Output on Node B:vxdmp 30vxio 36
Advanced topics related to installing VCSLLT over UDP181vxspec 37vxfen 87vxglm 915 To change Node B’s major numbers for vxio and vxspec to match those ofNode A, use the command:haremajor -vx major_number_vxio major_number_vxspecFor example, enter:# haremajor -vx 32 33If the command succeeds, proceed to step 8. If this command fails, youreceive a report similar to the following:Error: Preexisiting major number 32These are available numbers on this system: 128...Check /etc/name_to_major on all systems foravailable numbers.6 If you receive this report, use the haremajor command on Node A tochange the major number (32/33) to match that of Node B (36/37). Forexample, enter:# haremajor -vx 36 37If the command fails again, you receive a report similar to the following:Error: Preexisiting major number 36These are available numbers on this node: 126...Check /etc/name_to_major on all systems foravailable numbers.7 If you receive the second report, choose the larger of the two availablenumbers (in this example, 128), and use this number in the haremajorcommand to reconcile the major numbers. Type the following command onboth nodes:# haremajor -vx 128 1298 Reboot each node on which haremajor was successful.9 If the minor numbers match, proceed to reconcile the major and minornumbers of your next NFS block device.10 If the block device on which the minor number does not match is a volume,consult the vxdg(1M) manual page for instructions on reconciling theVeritas Volume Manager minor numbers, with specific reference to thereminor option.Node where the vxio driver number have been changed require rebooting.LLT over UDPVCS 5.0 provides the option of using LLT over the UDP (User Datagram Protocol)layer for clusters using wide-area networks and routers. UDP makes LLT packetsroutable and thus able to span longer distances more economically.
- 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
- Page 174 and 175: 174 Installing VCS on a single node
- Page 176 and 177: 176 Installing VCS on a single node
- Page 178 and 179: 178 Advanced topics related to inst
- Page 182 and 183: 182 Advanced topics related to inst
- Page 184 and 185: 184 Advanced topics related to inst
- Page 186 and 187: 186 Advanced topics related to inst
- Page 188 and 189: 188 Advanced topics related to inst
- Page 190 and 191: 190 Advanced topics related to inst
- Page 192 and 193: 192 Advanced topics related to inst
- Page 194 and 195: 194 Configuring the Symantec Licens
- Page 196 and 197: 196 Configuring the Symantec Licens
- Page 198 and 199: 198 Configuring the Symantec Licens
- Page 200 and 201: 200 IndexDdata disksfor I/O fencing
- Page 202 and 203: 202 IndexrequirementsEthernet contr
- Page 204: 204 Index
Advanced topics related to installing VCSLLT over UDP181vxspec 37vxfen 87vxglm 915 To change Node B’s major numbers <strong>for</strong> vxio and vxspec to match those ofNode A, use the command:haremajor -vx major_number_vxio major_number_vxspecFor example, enter:# haremajor -vx 32 33If the command succeeds, proceed to step 8. If this command fails, youreceive a report similar to the following:Error: Preexisiting major number 32These are available numbers on this system: 128...Check /etc/name_to_major on all systems <strong>for</strong>available numbers.6 If you receive this report, use the haremajor command on Node A tochange the major number (32/33) to match that of Node B (36/37). Forexample, enter:# haremajor -vx 36 37If the command fails again, you receive a report similar to the following:Error: Preexisiting major number 36These are available numbers on this node: 126...Check /etc/name_to_major on all systems <strong>for</strong>available numbers.7 If you receive the second report, choose the larger of the two availablenumbers (in this example, 128), and use this number in the haremajorcommand to reconcile the major numbers. Type the following command onboth nodes:# haremajor -vx 128 1298 Reboot each node on which haremajor was successful.9 If the minor numbers match, proceed to reconcile the major and minornumbers of your next NFS block device.10 If the block device on which the minor number does not match is a volume,consult the vxdg(1M) manual page <strong>for</strong> instructions on reconciling theVeritas Volume Manager minor numbers, with specific reference to thereminor option.Node where the vxio driver number have been changed require rebooting.LLT over UDPVCS <strong>5.0</strong> provides the option of using LLT over the UDP (User Datagram Protocol)layer <strong>for</strong> clusters using wide-area networks and routers. UDP makes LLT packetsroutable and thus able to span longer distances more economically.
Change language