Verify connectivity

Verify connectivity

We recommend that you verify network connectivity to the Internet and among the nodes before proceeding further.

  1. From the controller node, test access to the Internet:

    # ping -c 4 docs.openstack.org
    PING files02.openstack.org (23.253.125.17) 56(84) bytes of data.
    64 bytes from files02.openstack.org (23.253.125.17): icmp_seq=1 ttl=43 time=125 ms
    64 bytes from files02.openstack.org (23.253.125.17): icmp_seq=2 ttl=43 time=125 ms
    64 bytes from files02.openstack.org (23.253.125.17): icmp_seq=3 ttl=43 time=125 ms
    64 bytes from files02.openstack.org (23.253.125.17): icmp_seq=4 ttl=43 time=125 ms
    
    
    --- files02.openstack.org ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 125.192/125.282/125.399/0.441 ms
    
  2. From the controller node, test access to the management interface on the compute node:

    # ping -c 4 compute1
    
    PING compute1 (10.0.0.31) 56(84) bytes of data.
    64 bytes from compute1 (10.0.0.31): icmp_seq=1 ttl=64 time=0.263 ms
    64 bytes from compute1 (10.0.0.31): icmp_seq=2 ttl=64 time=0.202 ms
    64 bytes from compute1 (10.0.0.31): icmp_seq=3 ttl=64 time=0.203 ms
    64 bytes from compute1 (10.0.0.31): icmp_seq=4 ttl=64 time=0.202 ms
    
    --- compute1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3000ms
    rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms
    
  3. From the compute node, test access to the Internet:

    # ping -c 4 openstack.org
    
    PING openstack.org (174.143.194.225) 56(84) bytes of data.
    64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
    64 bytes from 174.143.194.225: icmp_seq=2 ttl=54 time=17.5 ms
    64 bytes from 174.143.194.225: icmp_seq=3 ttl=54 time=17.5 ms
    64 bytes from 174.143.194.225: icmp_seq=4 ttl=54 time=17.4 ms
    
    --- openstack.org ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3022ms
    rtt min/avg/max/mdev = 17.489/17.715/18.346/0.364 ms
    
  4. From the compute node, test access to the management interface on the controller node:

    # ping -c 4 controller
    
    PING controller (10.0.0.11) 56(84) bytes of data.
    64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.263 ms
    64 bytes from controller (10.0.0.11): icmp_seq=2 ttl=64 time=0.202 ms
    64 bytes from controller (10.0.0.11): icmp_seq=3 ttl=64 time=0.203 ms
    64 bytes from controller (10.0.0.11): icmp_seq=4 ttl=64 time=0.202 ms
    
    --- controller ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3000ms
    rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms
    

Note

RHEL, CentOS and SUSE distributions enable a restrictive firewall by default. During the installation process, certain steps will fail unless you alter or disable the firewall. For more information about securing your environment, refer to the OpenStack Security Guide.

Ubuntu does not enable a restrictive firewall by default. For more information about securing your environment, refer to the OpenStack Security Guide.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.