Kyle
[root@core01 nova]# ovs-ofctl dump-flows br-int
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=59187.486s, table=0, n_packets=197, n_bytes=10478,
priority=1 actions=NORMAL
[root@core01 nova]# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x1): ver:0x1, dpid:00004e4e9e814b4a
n_tables:255, n_buffers:256
features: capabilities:0xc7, actions:0xfff
1(gw-09656e2d-7f): addr:fa:16:3e:1e:ef:6f
config: 0
state: 0
2(tap3421ac3b-94): addr:d6:fd:56:fd:76:fd
config: 0
state: 0
current: 10MB-FD COPPER
LOCAL(br-int): addr:4e:4e:9e:81:4b:4a
config: PORT_DOWN
state: LINK_DOWN
OFPT_GET_CONFIG_REPLY (xid=0x3): frags=normal miss_send_len=0
On Wed, 2012-05-16 at 13:19 +0000, Kyle Mestery (kmestery) wrote:
On May 16, 2012, at 7:53 AM, Ask Stack wrote:
> Kyle
>
> Thanks. Below is my nova.conf
>
>
> [DEFAULT]
> logdir = /var/log/nova
> state_path = /var/lib/nova
> lock_path = /var/lib/nova/tmp
> dhcpbridge = /usr/bin/nova-dhcpbridge
> dhcpbridge_flagfile = /etc/nova/nova.conf
> force_dhcp_release = True
> injected_network_template = /usr/share/nova/interfaces.template
> libvirt_xml_template = /usr/share/nova/libvirt.xml.template
> libvirt_nonblocking = True
> vpn_client_template = /usr/share/nova/client.ovpn.template
> credentials_template = /usr/share/nova/novarc.template
> network_manager = nova.network.quantum.manager.QuantumManager
> #network_manager = nova.network.manager.FlatDHCPManager
> iscsi_helper = tgtadm
> sql_connection = mysql://nova:nova@localhost/nova
> connection_type = libvirt
> firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
> rpc_backend = nova.rpc.impl_qpid
> root_helper = sudo nova-rootwrap
> auth_strategy = keystone
> admin_token = a19c602bc5f8c10c47ea
> libvirt_vif_type = ethernet
> libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchDriver
> linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
> quantum_use_dhcp = True
OK, so you are using the old style libvirt + OVS driver. This means that Nova will be
creating tap devices during plug operations, and removing them during unplug operations.
In your case, it appears the tap is being added to the OVS bridge. You also have a gateway
device being added to the bridge as well. From your previous output, it looks like both
devices are up even, given your tcpdump output. So it's unclear to me why the ping
isn't working.
What does the output of "ovs-ofctl dump-flows br-int" indicate? It should be
setup to use L2 learning in your case, verify that.