Network problems occurred during rac_grid self-check. rac_grid self-check Network

Network problems occurred during rac_grid self-check. rac_grid self-check Network

Original Works are from the blog of "Deep Blue blog". You are welcome to reprint them. Please note the following source when reprinting them. Otherwise, you will be held legally liable for copyright.

Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/40735481 

Environment: Cent0S 6.4 64bit, grid 64bit

The "TCP connectivity of subnet" issue occurs during self-check.

[Problem]
Manually perform grid self-check and report the following error:
[Grid @ xzxt1 grid] $./runcluvfy. sh stage-pre crsinst-n xzxt1, xzxt2-fixup-verbose

............Check: Node connectivity of subnet "192.168.56.0"  Source                          Destination                     Connected?        ------------------------------  ------------------------------  ----------------  xzxt2[192.168.56.31]            xzxt1[192.168.56.30]            yes             Result: Node connectivity passed for subnet "192.168.56.0" with node(s) xzxt2,xzxt1Check: TCP connectivity of subnet "192.168.56.0"  Source                          Destination                     Connected?        ------------------------------  ------------------------------  ----------------  xzxt1:192.168.56.30             xzxt2:192.168.56.31             failed          ERROR: PRVF-7617 : Node connectivity between "xzxt1 : 192.168.56.30" and "xzxt2 : 192.168.56.31" failedResult: TCP connectivity check failed for subnet "192.168.56.0"Check: Node connectivity of subnet "10.10.10.0"  Source                          Destination                     Connected?        ------------------------------  ------------------------------  ----------------  xzxt2[10.10.10.91]              xzxt1[10.10.10.90]              yes             Result: Node connectivity passed for subnet "10.10.10.0" with node(s) xzxt2,xzxt1Check: TCP connectivity of subnet "10.10.10.0"  Source                          Destination                     Connected?        ------------------------------  ------------------------------  ----------------  xzxt1:10.10.10.90               xzxt2:10.10.10.91               failed          ERROR: PRVF-7617 : Node connectivity between "xzxt1 : 10.10.10.90" and "xzxt2 : 10.10.10.91" failedResult: TCP connectivity check failed for subnet "10.10.10.0"Interfaces found on subnet "192.168.56.0" that are likely candidates for VIP are:xzxt2 eth0:192.168.56.31xzxt1 eth0:192.168.56.30WARNING: Could not find a suitable set of interfaces for the private interconnectChecking subnet mask consistency...Subnet mask consistency check passed for subnet "192.168.56.0".Subnet mask consistency check passed for subnet "10.10.10.0".Subnet mask consistency check passed.Result: Node connectivity check failedChecking multicast communication...Checking subnet "192.168.56.0" for multicast communication with multicast group "230.0.1.0"...PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.31" on node "xzxt2"PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.30" on node "xzxt1"PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.31" on node "xzxt2"PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.30" on node "xzxt1"Checking subnet "192.168.56.0" for multicast communication with multicast group "224.0.0.251"...PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.31" on node "xzxt2"PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.30" on node "xzxt1"PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.31" on node "xzxt2"PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.30" on node "xzxt1"Checking subnet "10.10.10.0" for multicast communication with multicast group "230.0.1.0"...PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.91" on node "xzxt2"PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.90" on node "xzxt1"PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.91" on node "xzxt2"PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.90" on node "xzxt1"Checking subnet "10.10.10.0" for multicast communication with multicast group "224.0.0.251"...PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.91" on node "xzxt2"PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.90" on node "xzxt1"PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.91" on node "xzxt2"PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.90" on node "xzxt1"............

[Solution]
[Root @ xzxt1 network-scripts] # vi ifcfg-eth0
-- Remove GATEWAY = 192.168.56.1
DEVICE = eth0
ONBOOT = yes
BOOTPROTO = static
IPADDR = 192.168.56.30
NETMASK = 255.255.255.0

[Root @ xzxt1 network-scripts] # vi ifcfg-eth1
-- Remove GATEWAY = 10.10.10.1
DEVICE = eth1
ONBOOT = yes
BOOTPROTO = static
IPADDR = 10.10.10.90
NETMASK = 255.255.255.0

After the server is restarted, the problem does not occur again.

 

Original Works are from the blog of "Deep Blue blog". You are welcome to reprint them. Please note the following source when reprinting them. Otherwise, you will be held legally liable for copyright.

Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/40735481 

 

 

How to solve self-check Problems

Floppy Disk (s) fail or Floppy Disk (s) fail (80) or Floppy Disk (s) fail (40)

Unable to drive the floppy disk drive.

If the system prompts that the drive cannot be found, first check whether the power cord and data cable of the drive are loose or reverse. It is best to put the drive on another machine and try it if none of them work, so I had to buy another one. Fortunately, the current market is not expensive.

Hard disk install failure

Hard Disk Installation failed. This is because the power cord or data cable of the hard disk may not be properly connected or the hard disk jumper is improperly set. Friends can check whether all the hard drive connections are plugged in to see if the Jumper settings of the two hard drives on the same data cable are the same. If the two hard disks are the same, you only need to set the jumper of the two hard disks (one as the Master disk and the other as the Slave disk ).

Hard disk (s) diagnosis fail

An error occurred during hard disk diagnosis. This problem usually occurs when a hardware fault occurs inside the hard disk. You can try it on another machine. If the problem persists, you have to fix it. If the hard disk is still in the replacement period, it is best to change it!

Hardware Monitor found an error, enter power management setup for details, Press F1 to continue, DEL to enter SETUP

When an error is detected in the monitoring function, go to power management setup to View Details, Press F1 to start the program, and press DEL to enter the CMOS settings. Some of the better mainboards now have the hardware monitoring function. You can set the temperature monitoring of the motherboard and CPU, the voltage output accuracy monitoring of the voltage regulator, and the monitoring of the fan speed, when the above monitoring feature detects an exception at startup, this will occur. Then, friends can choose power management setup in the CMOS settings, in the ** Fan Monitor **, ** Thermal Monitor **, and ** Voltage Monitor ** on the right side, check which part of the monitoring has triggered an exception and then resolve it.

Keyboard error or no keyboard present

Incorrect keyboard or missed keyboard. Check whether the interface between the keyboard and the motherboard is connected. If the keyboard is connected, the keyboard port of the motherboard is broken. If the motherboard is still in the warranty period, you can contact the dealer or the motherboard manufacturer to solve the problem.

Memory test fail

Memory detection failed. Re-plugging the memory stick to see if it can be solved. This problem is generally caused by incompatibility between the mixed memory stick. If you have any conditions, replace it with another one! If only one memory stick is used, it must be a problem with the memory stick itself. It is better to change one stick quickly!

Override enable-Defaults loaded

The current CMOS settings cannot start the system. Load the preset values in the BIOS to start the system. Generally, the configuration in CMOS is incorrect. after entering the CMOS settings, you can select load setup defaults to LOAD the original value of the system and restart the system to solve this problem.

Press ESC to skip memory test

Memory check in progress. You can press ESC to skip this step. This is because the second, third, and fourth tests of the memory are not set to be skipped in CMOS, and four memory tests will be executed at startup. Of course, you can also Press ESC to end the memory check, however, it is too troublesome to do this after each boot. You can enter the CMOS settings and select bios features setup to Enabled the Quick Power On Self Test, after the storage, restart.

Resum ...... remaining full text>

How can I cancel the network self-check before the system starts?

Tune the BIOSS of the motherboard. It seems that you can turn off the integrated peripherals-> onboard LAN boot rom to disabled.