If your host is physically available and the operating system is up and running, but you cannot access your network to the Vertica cluster, then external connections might not be possible. Client software connections are failing, and users are not able to ssh to the host. From observing a hardware console connection, it looks like the host is still running.
Check if any of the following problems exist:
|1||Get the initial information from the NETWORK_USAGE system table.
||Upon getting information about the NETWORK_USAGE system table, proceed to Step 2.|
|2||Are you having problems pinging the default route IP address or router address?||If yes, the router is down or misconfigured. Reconfigure and restart the router. Consult with local network administrator.
If no, go to Step 3.
|3||If the firewall enabled?||If yes, disable the firewall, check settings, and go to Step 4.
If no, check the settings and go to Step 4.
|4||Are firewall settings blocking ports needed by Vertica?
Using default settings and blocking ports needed by Vertica can cause firewall problems.
|If yes, run the following commands to disable the firewall:
|5||Check the network ports in use:
If some of the ports are blocked, review list of ports required by Vertica and open ports on the firewall.
If no problems, go to Step 6.
|6||Has a DNS configuration error occurred?||If yes,
If no, go to Step 7.
|7||Is there a physical cable problem? Is the wrong network interface or cable in the wrong port?||If yes, ask the local network administrator to check the physical host and network cables.
If no, go to Step 8.
|8||Is the default network gateway configured incorrectly?||If yes, configure the gateway route. Without a default route, network traffic remains local on a server.
Use the following command to display route information:
|9||Do you have a bad IP address or a duplicate IP address?||If yes, check and modify the network IP address. Use ifconfig -a to verify the IP address and use ping to confirm the correct host using the IP address.
If no, go to Step 10.
|10||Is the network mask incorrect?||If yes, verify the network mask settings with your network administrator and update as needed.
Use the ifconfig –a command to review network settings and the network mask.
|11||Are you experiencing dropped packets or a slow network connection?||If yes, consult with your local network administrator regarding changes or settings.
To review network configuration settings or errors, use the command ifconfig -a and your specific network adapter.
Look for the following line in the output and a high number of errors and dropped packets:
|12||Is the physical network cable crimped or crushed between the server and the switch?||If yes, check and replace the network cable. Symptoms appear with a high number of dropped packets.
To review settings, use the command: ifconfig -a and your specific network adapter.
Look for the following line in the output and a high number of errors and dropped packets.
|13||Is the switch firmware version is out of date, or are patches needed?||If yes, install the necessary patches. Consult your network administrator about firmware patches.
If no, go to Step 14.
|14||Is the switch’s Network Address Translation (NAT) table incorrect or recently changed?||If yes, consult your local network administrator regarding changes or settings.
Verify and resolve network changes.
|15||Are Linux network drivers or are patches needed?||If yes, check that the network drivers are up to date.
Install patches if required. If not, run yum –update to perform any required updates and install patches.
If no, consult with Vertica technical support.