이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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.17. 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
      Copy to Clipboard Toggle word wrap
      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
      Copy to Clipboard Toggle word wrap
      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
      Copy to Clipboard Toggle word wrap
  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
    Copy to Clipboard Toggle word wrap

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
    Copy to Clipboard Toggle word wrap
    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
    Copy to Clipboard Toggle word wrap
    Start the ip netns exec command in a bash shell so that subsequent commands can be invoked without the ip netns exec command.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat