Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

If my active fibre path becomes unavailable the node reboots automatically

georgehorlacherFeb 5 2013 — edited Mar 28 2013
2 Node Cluster on Oracle Linux 6.2

I have an 11.2.0.3 cluster RAC installed using ASM voting disks and an ASM disk hosting a database. I'm testing the failover for multipaths. I disable one path and check connectivity then re-enable it using a Cisco Fabric manager. On some paths - I'm assuming its the active path, the server almost immediately reboots after disabling the path (shutting down the port). I have 8 paths to each LUN and Multipath -ll shows output such as:

mpathf (26366623936333162) dm-15 WTSSR__B,INVICTA
size=2.1T features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 1:0:0:7 sdf 8:80 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 1:0:1:7 sdr 65:16 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 1:0:2:7 sdad 65:208 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 1:0:3:7 sdap 66:144 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:0:7 sdbb 67:80 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:1:7 sdbn 68:16 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:2:7 sdbz 68:208 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
`- 2:0:3:7 sdcl 69:144 active ready running

When I created the asm disks I ran: oracleasm createdisk BIGDISK /dev/dm-15
I'm not sure if that is a problem, but the database is running fine as is the cluster.

One other thing - Its booting from SAN and when I installed it found the multipath device and installed fine to the LUNs (both Nodes). I did have to edit the /etc/multipath.conf and comment out the blacklist options before multipath -ll would show all the paths. However I did not do anything else with that file. I did notice in some of my reading that possibly I should have in the multipath.conf file a wwid followed by an iSCSI unique identifier, but since multipath -ll is showing all these paths I have not manually made multipath updates to the config file.

I'm no sure whats wrong, if I configured something wrong like the multipath.conf needs more path information, or if there is a config setting to prevent the nodes from rebooting too quickly if a path is taken away?

Edited by: GeorgeHorlacher on Feb 5, 2013 3:59 PM
This post has been answered by Dude! on Mar 28 2013
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 25 2013
Added on Feb 5 2013
12 comments
4,535 views