Setting Up Raw Disks For Multi-Node Access and I/O Fencing

You can set up raw disks for multi-node access and I/O fencing.

1. Set each node with the following:
   1. Set reserve_policy to no_reserve on the quorum device and all raw database devices:

      chdev -l hdisk# -a reserve_policy=no_reserve

   2. Each node, with a unique node ID for each node:

      chdev -l hdisk2 -a reserve_policy=no_reserve

   If you are using an IBM System Storage device, you must install the latest versions of the Subsystem Device Driver Path Control Module (SDDPCM) and the Host Attachment for SDDPCM on AIX for the version of AIX and IBM System Storage device you are using. Downloaded these directly from the IBM Web site.

   Note: IBM DS8000 storage series requires SDDPCM 2.4.0.4 or higher.
2. Run the following as SU or SUDO before starting dataserver, and make sure you have the appropriate shell privileges to run dataserver:

   setsecattr -p iprivs=+PV_KER_RAS $$

   You can also run setsecattr with user “sybase” if it has the appropriate roles, such as a non-network information services (non-NIS) user.
3. Create a user with privileges to run programs using OpenX:

   mkuser sybase 
   mkrole authorizations=aix.device.manage.change role_disk_access 
   chuser roles=role_disk_access sybase 

4. If you are setting up raw disks to provide multi-node access and I/O fencing on IBM AIX, follow these additional steps:
   1. Create the user "sybase": mkuser sybase
   2. Create role and grant to sybase:

      mkrole authorizations=aix.device.manage.change role_disk_access
      	chuser roles=role_disk_access sybase

   3. Add the security ‘aix.security.proc.set’ for set security attribute:

      smit -> Security & Users -> RBAC -> Roles -> Change -> 
      		'role_disk_access' -> AUTHORIZATIONS +'aix.security.proc.set'
      	setkst

   4. Change user to sybase and set the security attribute (set this attribute as default):

      su – sybase
      	setsecattr –p iprivs=+PV_KER_RAS,PV_ROOT,PV_SU_ $$