Exalytics In-Memory Machine X2-4
 
Oracle Exalytics Software
 

PLA-Support>Eng Systems>Exalytics>Oracle Exalytics>DB: Exalytics_EST
 
_Old GCS Categories>ST>Server>Engineered Systems>Exalytics>Installation
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-6918538829>

Applies to:

Symptoms

When running the Exalytics configure_network_for_exalytics.sh script, it fails with error:

[EXALOGIC_WARN:GENERAL] Failed connectivity test

However, the network interfaces can be successfully pinged when running the verification steps in Section 4.6.4 Verifying the Configuration of the Oracle Exalytics In-Memory Machine Owner's Guide.

Cause

This issue occurs due to <Bug 16479929> - CONFIGURE_NETWORK_FOR_EXALYTICS.SH SCRIPT REPORTS "FAILED CONNECTIVITY TEST".  During an initial installation, the configure_network_for_exalytics.sh script returns 'Failed connectivity test', for some connections, if the configuration does not include usage of eth0 (the first on-board 1G Ethernet port). For example:

[EXALOGIC_WARN:GENERAL] Failed connectivity test to 172.16.13.11
[EXALOGIC_WARN:GENERAL] Failed connectivity test to 172.16.13.43

Unpublished Bug 14739931 CONFIGURE_NETWORK_FOR_EXALYTICS.SH SHOULD BE ABLE TO DE-CONFIGURE INTERFACES also contributes to this issue, as the script does not "clean up" any prior, or default, network configurations. The script assumes that the eth0 will be used and the existing eth0 configuration, (defined when the OS is loaded during manufacture), is left as is, unless the option to configure the 1G Ethernet ports is selected at script run time.

In this specific case, only the two 10G ports were to be configured, and made into a bond for use. When selecting this setup, the eth0 port was left with the originally configured IP of 192.168.1.4. Since there were no Ethernet cables connected (nor any 192.168.1 net), the connectivity tests failed when attempting to use the eth0 connection.
 

Solution

Until a fix is available, use the following steps to prevent connectivity errors and correctly deconfigure the eth0 connection:

1. Check the routing table to determine the default route, (i.e. the eth0 IP), by running the command:

2. Make a backup copy of the /etc/hosts file and then comment out the eth0 line in the file.

3. Check /etc/sysconfig/network to make sure there isn't a value for GATEWAY, and/or the value is correct. Again, in this case, the value gateway was empty, and no changes were needed. If changes are needed, first make a backup copy.

4. Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file, (after making a backup of the file), and replace the current config, with the following example to unconfigure it:

5. Restart the network service, i.e.:

6. Re-execute the configure_network_for_exalytics.sh script and select the appropriate network settings.

7. Check the ifcfg-bond* files to make sure they are properly configured.

8. Check for rule-* and route-* files (none existed).

9. Recheck routing table by running the "netstat -rn" command to confirm setup. In this case, the routing table correctly showed the eth4/5 bond(10G) route as the default.
 

References

This solution has no attachment