Red Hat Training

A Red Hat training course is available for Red Hat OpenStack Platform

7.7. Validate the OpenStack Networking Installation

To begin using OpenStack Networking, you must deploy networking components to Compute nodes. You must also define initial networks and routers. It is, however, possible to perform basic sanity checking of the OpenStack Networking deployment by following the steps outlined in this procedure.

Procedure 7.14. Validate the OpenStack Networking Installation

  1. On All Nodes

    1. Verify that the customized Red Hat Enterprise Linux kernel intended for use with Red Hat OpenStack Platform is running:
      # uname --kernel-release
      2.6.32-358.6.2.openstack.el6.x86_64
      If the kernel release value returned does not contain the string openstack, update the kernel and reboot the system.
    2. Ensure that the installed IP utilities support network namespaces:
      # ip netns
      If an error indicating that the argument is not recognised or supported is returned, update the system using yum.
  2. On Service Nodes

    1. Ensure that the neutron-server service is running:
      # openstack-status | grep neutron-server
      neutron-server:                         active
  3. On Network Nodes

    Ensure that the following services are running:
    • DHCP agent (neutron-dhcp-agent)
    • L3 agent (neutron-l3-agent)
    • Plug-in agent, if applicable (neutron-openvswitch-agent or neutron-linuxbridge-agent)
    • Metadata agent (neutron-metadata-agent)
    # openstack-status | grep SERVICENAME

7.7.1. Troubleshoot OpenStack Networking Issues

This section discusses the commands you can use and procedures you can follow to troubleshoot OpenStack Networking issues.
Debugging Networking Device
  • Use the ip a command to display all the physical and virtual devices.
  • Use the ovs-vsctl show command to display the interfaces and bridges in a virtual switch.
  • Use the ovs-dpctl show command to show datapaths on the switch.
Tracking Networking Packets
  • Check where packets are not getting through:
    # tcpdump -n -i INTERFACE -e -w FILENAME
    Replace INTERFACE with the name of the network interface to check. The interface name can be the name of the bridge or host Ethernet device.
    The -e flag ensures that the link-level header is printed (in which the vlan tag will appear).
    The -w flag is optional. Use it if you want to write the output to a file. If not, the output is written to the standard output (stdout).
    For more information about tcpdump, see its manual page.
Debugging Network Namespaces
  • Use the ip netns list command to list all known network namespaces.
  • Show routing tables inside specific namespaces:
    # ip netns exec NAMESPACE_ID bash
    # route -n
    Start the ip netns exec command in a bash shell so that subsequent commands can be invoked without the ip netns exec command.