|
|
|
|
|
When you configure fencing in raw mode, fencing disables secondary paths for DMP. Fencing disables secondary paths for DMP because for certain A/P arrays, DMP opens secondary paths with an exclusive flag, and keeps all paths permanently open. In raw mode, however, fencing needs to open all paths and register keys down those paths.
Due to DMP's exclusive hold on the paths, the vxfenconfig command cannot open those paths. To avoid the issue of DMP holding open the secondary paths, fencing disables the secondary paths from DMP's perspective, which causes DMP to close the paths. This disabling of secondary paths is done using the /etc/init.d/vxfen.rc script.
During a cluster reconfiguration, if a primary path is not available for any reason, fencing tries to use secondary paths for the attempted operation. The path was disabled from DMP's perspective, but all SCSI-3 operations are performed to the path's raw interface.
When you attempt to run the vxfentsthdw command, remember that DMP has an exclusive hold on the path, so run it only on primary paths. Use the vxdisk list command to determine the primary path to a disk.