Cluster Server Installation Guide for Solaris x64 5.0 - Storage ...

Setting up I/O fencingTroubleshooting I/O fencing1232 Read the existing keys:# vxfenadm -g all -f /tmp/disklistThe output from this command displays the key:Device Name: /dev/rdsk/c1t0d11s2Total Number Of Keys: 1key[0]:Key Value [Numeric Format]: 65,49,45,45,45,45,45,45Key Value [Character Format]: A1-----­3 If you know on which node the key was created, log in to that node and enterthe following command:# vxfenadm -x -kA1 -f /tmp/disklistThe key is removed.4 If you do not know on which node the key was created, follow step 5 throughstep 7 to remove the key.5 Register a second key “A2” temporarily with the disk:# vxfenadm -m -k A2 -f /tmp/disklistRegistration completed for disk path /dev/rdsk/c1t0d11s26 Remove the first key from the disk by preempting it with the second key:# vxfenadm -p -kA2 -f /tmp/disklist -vA1key: A2------ prempted the key: A1------ on disk /dev/rdsk/c1t0d11s27 Remove the temporary key assigned in step 5.# vxfenadm -x -kA2 -f /tmp/disklistDeleted the key : [A2------] from device /dev/rdsk/c1t0d11s2No registration keys exist for the disk.System panics to prevent potential data corruptionWhen a node experiences a split brain condition and is ejected from the cluster,it panics and displays the following console message:VXFEN:vxfen_plat_panic: Local cluster node ejected from cluster to prevent potential data corruption.How vxfen driver checks for pre-existing split brain conditionThe vxfen driver functions to prevent an ejected node from rejoining the clusterafter the failure of the private network links and before the private networklinks are repaired.For example, suppose the cluster of system 1 and system 2 is functioningnormally when the private network links are broken. Also suppose system 1 isthe ejected system. When system 1 restarts before the private network links arerestored, its membership configuration does not show system 2; however, whenit attempts to register with the coordinator disks, it discovers system 2 is