How To Setup UDEV Rules For RAC OCR And Voting Devices On SLES10, RHEL5, OEL5, OL5 [ID 414897.1]

1. Create The New UDEV Rules
1.1 Create UDEV Permission Rule Prior Up-To Version 11.1.0.7
1.2 Create UDEV Permission Rule For Version 11.2 And Later
2. Restart The UDEV Service

[@more@]

Applies to:

Linux OS - Version: 2.6.18-8 to 2.6.21
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.2.0.2.0 [Release: 10.1 to 11.2]
Linux x86
Linux x86-64
Linux Itanium
***Checked for relevance on 2011-01-22***

Linux Kernel - Version: 2.6.18-8 to 2.6.21

Goal

Real Application Clusters (RAC) requires special ownership (owner, group and permissions) for the OCR (Oracle Cluster Registry) and Voting devices on Linux.

In the 2.6 kernel, the UDEV system is the default method through which the kernel controls the creation of the special files that represent resources such as block devices. In Oracle 10g RAC, where raw devices are a mandatory requirement for use by CRS, raw devices require specific ownership and permissions. Prior to UDEV, device nodes could be created and their access permissions persistently set using the mknod(1) utility; the UDEV facility dynamically recreates the /dev content each reboot, preventing this approach. The solution is to add UDEV rules to set these attributes automatically. The configuration file syntax for UDEV in SLES10, RHEL5 and OEL5 have vary slightly compared depending on the software version.

For SuSE Linux Enterprise Server 10 (SLES10), UDEV rules for raw device permission setting should be placed into rule files under the /etc/udev/rules.d/ directory. The files are processed in ls(1) order, with default system rules contained in the 50-udev-default.rules file.

UDEV Filename Rules
Filenames begin with two decimal digits, to sequence the rules into ascending numerical order.
After a dash, filenames contain descriptive words.
The filename must end with ".rules" to be recognized.
Rule clauses using a double equal sign (==) are predicate matching patterns, to determine if the rest of the line should be processed.
Rule clauses are separated by a comma.
Rule clauses with only a single equal sign (=) are actions to be performed.
Content after a sharp sign / hash mark / octothorpe (#) is ignored as a comment.
Blank lines are OK.

From SLES10, there is no separation between rules for creating devices and rules for device permissions - both are now set from the same rule file. In order to alter the permissions for raw devices, create a permission rule file that sets the appropriate device permissions in therules.d/ directory, so that it is processed before the default rules:

Caution About Changing Files Owned By The Distribution

Do not change the default 50-udev-default.rules file. This file will be over-written should the UDEV package be updated. On RHEL5/OEL5, the UDEV rules file is called 50-udev.rules, otherwise the behavior is the same. Always use a separate, custom file.

Solution

1. Create The New UDEV Rules

Choose one of the following methods, depending upon your RAC version.

1.1 Create UDEV Permission Rule Prior Up-To Version 11.1.0.7

Create a custom UDEV permission rule file (for example, /etc/udev/rules.d/99-raw.rules) and ensure the file name lists after the default 50-xxx.rules file. The filename must end in ".rules" to be recognized.

Add the required raw device ownership and permissions, for example:

# /bin/cat /etc/udev/rules.d/99-raw.rules
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s %p", RESULT=="3600805f30016c0e0ad41ffa8e6d90001", NAME="raw1", ACTION=="add|change", OWNER="root", GROUP="oinstall", MODE="0640"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s %p", RESULT=="3600805f30016c0e0ae51efbfb2930002", NAME="raw2", ACTION=="add|change", OWNER="oracle", GROUP="oinstall", MODE="0660"

1.2 Create UDEV Permission Rule For Version 11.2 And Later

Create a UDEV rules file for the Oracle ASM devices, setting permissions to read/write for the group and owner (0660) for the installation owner and the group whose members are to be administrators of the grid infrastructure software.

For example, using the installation owner grid and using a role-based group configuration, with the OSASM group asmadmin:

# /bin/cat /etc/udev/rules.d/99-oracle-asmdevices.rules
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s %p", RESULT=="350002ac000010b52", NAME="vote1", ACTION=="add|change", OWNER="grid", GROUP="asmadmin", MODE="0660"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s %p", RESULT=="350002ac000020b52", NAME="vote2", ACTION=="add|change", OWNER="grid", GROUP="asmadmin", MODE="0660"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s %p", RESULT=="350002ac000030b52", NAME="vote3", ACTION=="add|change", OWNER="grid", GROUP="asmadmin", MODE="0660" 

Copy this rules.d/ file to all other nodes on the cluster. For example:
# /usr/bin/scp 99-oracle-asmdevices.rules root@node2:/etc/udev/rules.d/99-oracle-asmdevices.rules

2. Restart The UDEV Service

Restart the UDEV service as follows. Then verify the devices now reflect their intended ownership and permissions:

On SLES10:

# /etc/init.d/boot.udev stop
# /etc/init.d/boot.udev start

On RHEL5/OEL5/OL5:

# /sbin/udevcontrol reload_rules
# /sbin/start_udev

References

NOTE:465001.1 - Configuring raw devices (singlepath) for Oracle Clusterware 10g Release 2 (10.2.0) on RHEL5/OEL5
NOTE:564580.1 - Configuring raw devices (multipath) for Oracle Clusterware 10g Release 2 (10.2.0) on RHEL5/OEL5
NOTE:605828.1 - Configuring non-raw multipath devices for Oracle Clusterware 11g (11.1.0) on RHEL5/OEL5
http://www.worldwidewords.org/weirdwords/ww-oct1.htm

显示相关信息

返回页首

ITPub博客

How To Setup UDEV Rules For RAC OCR And Voting Devices