learn how to set up raw disks for multi-node access and I/O fencing.
-
Make sure the PR_key_value attribute
is displayed in the lsattr -El hdisk# command.
If you do not have this information, contact your storage
vendor and request the ODM fileset for AIX . Storage vendors who
support and provide ODM fileset are: IBM, HDS, EMC, and HP.
-
With this information, set each node with the following:
-
All raw database devices should have
the PR_key_value set to the instance_id_number and
the reserve_policy set to PR_shared:
chdev -l hdisk#
-a PR_key_value=<instance_id number>
-a reserve_policy=PR_shared
-
The quorum device only is set to no_reserve:
chdev -l hdisk1 -a reserve_policy=no_reserve
-
Each node, with a unique node ID for each node:
chdev -l hdisk2 -a PR_key_value=1
-a reserve_policy=PR_shared
-
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 (for example, a non-network
information services (non-NIS) user).
-
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 default_roles=role_disk_access sybase
-
If you are setting up raw disks to provide multi-node access and IO fencing on IBM AIX follow these additional steps:
-
Create the user "sybase": mkuser sybase
-
Create role and grant to sybase:
mkrole authorizations=aix.device.manage.change role_disk_access
chuser role=role_disk_access default_roles=role_disk_access sybase
-
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
-
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_ $$