Different Nic mtu values cause rac 2-node ASM not to start ORA-27550 at the same time: Target ID protocol check failed., mtuora-27550

Source: Internet
Author: User

Different Nic mtu values cause rac 2-node ASM not to start ORA-27550 at the same time: Target ID protocol check failed., mtuora-27550

After installing 10205 rac, prepare to configure asm dg and find that ASM on node 2 cannot be started:

En12 is a private Nic

En13 is public Nic


----> 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 13 16:07:38 BEIST 2015
Maximum Tranmission Unit (mtu) of the ether adapter is different -------- inconsistent between MTU nodes
On the node running instance 1, and this node.
Ether adapters connecting the cluster nodes must be configured
With identical mtu on all the nodes, for Oracle.
Please ensure the mtu attribute of the ether adapter on all
Nodes are identical, before running Oracle.
Fri Feb 13 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 13 16:07:39 BEIST 2015
System state dump is made for local instance
Fri Feb 13 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 13 16:07:39 BEIST 2015
Trace dumping is refreshing Ming id = [cdmp_20150426160739]
Fri Feb 13 16:07:40 BEIST 2015


---- View Node 1 Network Information:

[Oracle @ dg1:/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 9000 10 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 2 network information:
[Oracle @ dg2:/oracle/app/oracle/product/10/db/dbs/] $ netstat-in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
En12 1500 link #2 0.1a.64.bb.82.64 104657 0 55568 3 0
En12 150010 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.20.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


[Oracle @ dg2:/oracle/app/oracle/product/10/db/dbs/] $ ifconfig-
En12: flags = 5e080863, c0 <UP, BROADCAST, NOTRAILERS, RUNNING, SIMPLEX, MULTICAST, GROUPRT, 64BIT, CHECKSUM_OFFLOAD (ACTIVE), mongog, 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), mongog, LARGESEND, CHAIN>
Inet 172.31.2.131 netmask 0xffffff00 broadcast 172.31.2.255
Inet 172.31.2.20.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.0000255
Inet6: 1/0
Tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1



Solution:

Adjust the mtu value of the NIC. Disable the cluster. And whether to enable the jumbo frame.


Not complete .....

~

~

BTW:

MTU
Purpose: limit the size of packets transmitted over the network.
Value: Default Value: configuration-dependent
Display: lsattr-E-l interface_name
Change: chdev-l interface_name-a mtu = NewValue
The command chdev cannot be changed during use. The change takes effect only after the reboot.
An alternative method is as follows:
Ifconfig interface_name mtu NewValue
This method changes the MTU size in a running system, but this value is not retained after the system is restarted.


Diagnosis: packet fragmentation statistics.
Adjust: Increase the MTU size of the network interface. For the Gigabit Ethernet Adapter, use the device property jumbo_frames = yes to enable huge frames (it is not enough to set the MTU value on the interface to 9000 ).




If network card aggregation is used, it may need to be removed. After the mtu of each network card is adjusted, the network card is re-aggregated. Otherwise, the following problems may occur:
# Chdev-l en12-a mtu= 9000
Method error (/usr/lib/methods/chgif ):
0514-068 Cause not known.
0821-532 ioctl (SIOCSIFMTU): A return value of a math subroutine is not within machine precision.
0821-103: The command/usr/sbin/ifconfig en12 inet 10.0.0.2 arp netmask 255.255.255.0 mtu 9000 up failed.
0821-007 cfgif: ifconfig command failed.
The status of "en12" Interface in the current running system is uncertain.
0821-103: The command/usr/lib/methods/cfgif-len12 failed.
0821-532 ioctl (SIOCSIFMTU): A return value of a math subroutine is not within machine precision.
0821-103: The command/usr/sbin/ifconfig en12 inet 10.0.0.2 arp netmask 255.255.255.0 mtu 9000 up failed.
0821-229 chgif: ifconfig command failed.
The status of "en12" Interface in the current running system is uncertain

 

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.