Different NIC MTU values cause the RAC 2 node ASM to not start Ora-27550:target ID protocol check failed at the same time.

When you are ready to configure ASM DG after installing 10205 RAC, it is found that ASM on node two cannot be started:

En12 for private network card

En13 for public network card

---->> View Oracle ASM Alert Log Error display:

LMD0 started with pid=6, OS id=565728
LMS0 started with pid=7, OS id=491812
Mman started with pid=8, OS id=594200
DBW0 started with pid=9, OS id=651626
LGWR started with pid=10, OS id=692672
CKPT started with pid=11, OS id=668066
Smon started with pid=12, OS id=696756
Rbal started with pid=13, OS id=700854
Gmon started with pid=14, OS id=688448
Fri Feb 16:07:38 beist 2015
Maximum tranmission Unit (MTU) of the ether adapter is different inconsistencies between MTU nodes--------
On the node running instance 1, and this node.
Ether adapters connecting the cluster nodes must be configured
With identical MTU in the nodes, for Oracle.
Ensure the MTU attribute of the ether adapter on all
Nodes is identical, before running Oracle.
Fri Feb 16:07:38 beist 2015
Errors in FILE/ORACLE/APP/ORACLE/ADMIN/+ASM/BDUMP/+ASM2_LMON_582048.TRC:
Ora-27550:target ID protocol check failed. Tid vers=%d, type=%d, remote instance number=%d, local instance number=%d
Lmon:terminating instance due to error 27550
Fri Feb 16:07:39 beist 2015
System state dump was made for local instance
Fri Feb 16:07:39 beist 2015
Errors in FILE/ORACLE/APP/ORACLE/ADMIN/+ASM/BDUMP/+ASM2_DIAG_614754.TRC:
Ora-27550:target ID protocol check failed. Tid vers=%d, type=%d, remote instance number=%d, local instance number=%d
Fri Feb 16:07:39 beist 2015
Trace dumping is performing id=[cdmp_20150213160739]
Fri Feb 16:07:40 beist 2015

----View Node One network information:

[Email protected]:/oracle/app/oracle/admin/+asm/bdump/] $netstat-in

Name Mtu Network Address ipkts ierrs opkts oerrs Coll
EN12 9000 link#2 0.1a.64.bb.82.8 286059 0 57330 3 0
EN12 900010 10.0.0.1 286059 0 57330 3 0
EN13 9000 link#3 0.1a.64.bb.82.9 17267057 0 15456852 24 0
EN13 9000 172.31.2 172.31.2.130 17267057 0 15456852 24 0
EN13 9000 172.31.2 172.31.2.132 17267057 0 15456852 24 0
Lo0 16896 link#1 380344 0 380439 0 0
Lo0 16896 127 127.0.0.1 380344 0 380439 0 0
Lo0 16896:: 1 380344 0 380439 0 0


----View Node two network information:
[Email protected]:/oracle/app/oracle/product/10/db/dbs/] $netstat-in
Name Mtu Network Address ipkts ierrs opkts oerrs Coll
En12 link#2 0.1a.64.bb.82.64 104657 0 55568 3 0
en12 10 10.0.0.2 104657 0 55568 3 0
EN13 9000 link#3 0.1a.64.bb.82.65 1538972 0 761507 21 0
EN13 9000 172.31.2 172.31.2.131 1538972 0 761507 21 0
EN13 9000 172.31.2 172.31.2.133 1538972 0 761507 21 0
Lo0 16896 link#1 112862 0 112928 0 0
Lo0 16896 127 127.0.0.1 112862 0 112928 0 0

Lo0 16896:: 1 112862 0 112928 0 0

[[Email protected]:/oracle/app/oracle/product/10/db/dbs/] $ifconfig-A
En12:flags=5e080863,c0<up,broadcast,notrailers,running,simplex,multicast,grouprt,64bit,checksum_offload ( ACTIVE),pseg,largesend,chain>
inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255
Tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
En13:flags=5e080863,c0<up,broadcast,notrailers,running,simplex,multicast,grouprt,64bit,checksum_offload ( ACTIVE),pseg,largesend,chain>
inet 172.31.2.131 netmask 0xffffff00 broadcast 172.31.2.255
inet 172.31.2.133 netmask 0xffffff00 broadcast 172.31.2.255
Tcp_sendspace 262144 tcp_recvspace 131072 rfc1323 1
Lo0:flags=e08084b<up,broadcast,loopback,running,simplex,multicast,grouprt,64bit>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
INET6:: 1/0
Tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1



Workaround:

Adjust the NIC MTU value. Note that you need to close the cluster. And whether Jumbo frames are enabled.

To be continued .....

~
~

Different NIC MTU values cause the RAC 2 node ASM to not start Ora-27550:target ID protocol check failed at the same time.