Verify connectivity between the machines you’ll be installing
Eucalyptus on. Some Linux distributions provide default TCP/IP
firewalling rules that limit network access to machines. Disable
these default firewall settings before you install Eucalyptus
components to ensure that the components can communicate with
Note: Any firewall running on the CC must be
compatible with the dynamic changes performed by Eucalyptus when
working with security groups. Eucalyptus will flush the 'filter'
and 'nat' tables upon boot.
Verify component connectivity by performing the following checks
on the machines that will be running the listed Eucalyptus
Verify connection from an end-user to the CLC on TCP ports
8443 and 8773
Verify connection from an end-user to Walrus on TCP port
Verify connection from the CLC, SC, and NC (or VB) to SC on
TCP port 8773
Verify connection from the CLC, SC, and NC (or VB) to
Walrus on TCP port 8773
Verify connection from Walrus, SC, and VB to CLC on TCP
Verify connection from CLC to CC on TCP port 8774
Verify connection from CC to VB on TCP port 8773
Verify connection from CC to NC on TCP port 8775
Verify connection from NC (or VB) to Walrus on TCP port
8773. Or, you can verify the connection from the CC to
Walrus on port TCP 8773, and from an NC to the CC on TCP
Verify connection from public IP addresses of Eucalyptus
instances (metadata) and CC to CLC on TCP port 8773
Verify TCP connectivity between CLC, Walrus, SC and VB on
TCP port 8779 (or the first available port in range
Verify connection between CLC, Walrus, SC, and VB on UDP
Verify multicast connectivity for IP address 126.96.36.199
between CLC, Walrus, SC, and VB on UDP port 8773
If DNS is enabled, verify connection from an end-user and
instance IPs to DNS ports
If you use tgt (iSCSI open source target) for EBS storage,
verify connection from NC to SC on TCP port 3260
If you use VMware with Eucalyptus, verify the connection
from the VMware Broker to VMware (ESX, VSphere).
Test multicast connectivity between each CLC and Walrus, SC, and VMware broker host.
Clone the Eucalyptus deveutils repository
git clone https://github.com/eucalyptus/deveutils
Run the network-tomography tool on the Cloud Controller, Cluster
Controller, Storage Controller, and any machines running Walrus or VMware Broker,
passing a list of IP addresses for each of these machines.
./network-tomography 192.168.51.174 192.168.51.196 192.168.51.86 192.168.51.99
This tool may take up to an hour to run. Check the output for reports of packet loss.
If there is significant packet loss, ensure that your network is available and