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!

Multicasting is needed only if you use HAIP. Right ?

User_4ZSEXMay 2 2017 — edited May 3 2017

GI version: 11.2.0.4

OS : RHEL 6.8

Hypervisor : VMWare ESX

Question1.

I need to install Oracle RAC on RHEL 6.8 on 2-node VMWare VMs.

cluvfy has reported the following warning for Multicasting. I gather that mulicasting is only needed when you use HAIP, a feature introduced in 11.2.0.2.

But, I am using bonded interface for my private network and hence I don't need HAIP. So, can I ignore the below warning and proceed with Grid Infrastructure installation ?

BTW.. cluvfy wrongly assumed that 10.5.167.0 is meant for private network. 10.5.167.0 subnet is actually meant for backups (RMAN).

Private IPs are actually 169.5.51.215 and 169.5.51.216 . The private interfaces are connected to a 1Gb switch.

Question2.

What is the reason for the error in red below "not able to communicate with.... the private interfaces 169.5.51.215 and 169.5.51.216 ?

Below, I am providing the excerpt from cluvfy and /etc/hosts file contents

1. Excerpt from cluvfy

Interfaces found on subnet "10.5.167.0" that are likely candidates for a private interconnect are:

apacwmsdb01 eth10:10.5.167.181

apacwmsdb02 eth12:10.5.167.182

WARNING:

Could not find a suitable set of interfaces for VIPs

WARNING:

Could not find a suitable set of interfaces with the same name for the private interconnect

Checking subnet mask consistency...

Subnet mask consistency check passed for subnet "10.5.167.0".

Subnet mask consistency check passed for subnet "10.5.148.0".

Subnet mask consistency check passed for subnet "169.5.51.0".

Subnet mask consistency check passed.

Result: Node connectivity check passed

Checking multicast communication...

Checking subnet "10.5.167.0" for multicast communication with multicast group "230.0.1.0"...

Check of subnet "10.5.167.0" for multicast communication with multicast group "230.0.1.0" passed.

Checking subnet "10.5.148.0" for multicast communication with multicast group "230.0.1.0"...

PRVG-11134 : Interface "10.5.148.38" on node "apacwmsdb01" is not able to communicate with interface "10.5.148.39" on node "apacwmsdb02"

Checking subnet "10.5.148.0" for multicast communication with multicast group "224.0.0.251"...

Check of subnet "10.5.148.0" for multicast communication with multicast group "224.0.0.251" passed.

Checking subnet "169.5.51.0" for multicast communication with multicast group "230.0.1.0"...

PRVG-11134 : Interface "169.5.51.215" on node "apacwmsdb01" is not able to communicate with interface "169.5.51.216" on node "apacwmsdb02"

PRVG-11134 : Interface "169.5.51.216" on node "apacwmsdb02" is not able to communicate with interface "169.5.51.215" on node "apacwmsdb01"

Checking subnet "169.5.51.0" for multicast communication with multicast group "224.0.0.251"...

Check of subnet "169.5.51.0" for multicast communication with multicast group "224.0.0.251" passed.

Check of multicast communication passed.

2. Following are the contents of /etc/hosts

####### Public IP ###############

10.5.148.38      apacwmsdb01.domain.net     apacwmsdb01

10.5.148.39      apacwmsdb02.domain.net     apacwmsdb02

##### Virtual IP ##############

10.5.148.50     apacwmsdb01-vip.domain.net      apacwmsdb01-vip

10.5.148.51     apacwmsdb02-vip.domain.net      apacwmsdb02-vip

#### Private IP ###############

169.5.51.215      apacwmsdb01-priv.domain.net      apacwmsdb01-priv

169.5.51.216      apacwmsdb02-priv.domain.net      apacwmsdb02-priv

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 31 2017
Added on May 2 2017
2 comments
609 views