此内容没有您所选择的语言版本。
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
On All Nodes
- Verify that the customized Red Hat Enterprise Linux kernel intended for use with Red Hat OpenStack Platform is running:
#uname --kernel-release2.6.32-358.6.2.openstack.el6.x86_64If the kernel release value returned does not contain the stringopenstack, update the kernel and reboot the system. - Ensure that the installed IP utilities support network namespaces:
#ip netnsIf an error indicating that the argument is not recognised or supported is returned, update the system usingyum.
On Service Nodes
- Ensure that the
neutron-serverservice is running:#openstack-status | grep neutron-serverneutron-server: active
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-agentorneutron-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 acommand to display all the physical and virtual devices. - Use the
ovs-vsctl showcommand to display the interfaces and bridges in a virtual switch. - Use the
ovs-dpctl showcommand to show datapaths on the switch.
- Tracking Networking Packets
- Check where packets are not getting through:
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.#tcpdump -n -i INTERFACE -e -w FILENAMEThe-eflag ensures that the link-level header is printed (in which thevlantag will appear).The-wflag 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 abouttcpdump, see its manual page.
- Debugging Network Namespaces
- Use the
ip netns listcommand to list all known network namespaces. - Show routing tables inside specific namespaces:
Start the#ip netns exec NAMESPACE_ID bash#route -nip netns execcommand in a bash shell so that subsequent commands can be invoked without theip netns execcommand.
