OpenStack Operations Guide
by Tom Fifield, Diane Fleming, Anne Gentle, Lorin Hochstein, Jonathan Proulx, Everett Toews, Joe Topjian
Chapter 12. Network Troubleshooting
Network troubleshooting can unfortunately be a very difficult and
confusing procedure. A network issue can cause a problem at several points
in the cloud. Using a logical troubleshooting procedure can help mitigate
the confusion and more quickly isolate where exactly the network issue is.
This chapter aims to give you the information you need to identify any
issues for either nova-network or OpenStack Networking
(neutron) with Linux Bridge or Open vSwitch.
Using “ip a” to Check Interface States
On compute nodes and nodes running nova-network,
use the following command to see information about interfaces, including
information about IPs, VLANs, and whether your interfaces are
up:
#ip a
If you’re encountering any sort of networking difficulty, one good initial sanity check is to make sure that your interfaces are up. For example:
$ip a | grep state1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br100 state UP qlen 1000 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN 5: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
You can safely ignore the state of virbr0, which
is a default bridge created by libvirt and not used by OpenStack.
Visualizing nova-network Traffic in the Cloud
If you are logged in to an instance and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access