Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

This issue has been resolved. As I mentioned before that the DHCP request entered into the br-eth2 but was dropped and never came out. Bu using ovs-ofctl, it shows up as

root@dev1-openstack01:~# ovs-ofctl dump-flows br-eth2    
cookie=0x0, duration=137361.445s, table=0, n_packets=2451, n_bytes=611718, priority=2,in_port=3 actions=drop    
cookie=0x0, duration=137363.594s, table=0, n_packets=145375, n_bytes=9701297, priority=1 actions=NORMAL

However, the right flows should be

root@dev1-openstack01:~# ovs-ofctl dump-flows br-eth2
cookie=0x0, duration=137361.445s, table=0, n_packets=2451, n_bytes=611718, priority=2,in_port=3 actions=drop
cookie=0x0, duration=137358.345s, table=0, n_packets=3355, n_bytes=679043, priority=4,in_port=3,dl_vlan=1 actions=mod_vlan_vid:1000,NORMAL
cookie=0x0, duration=137363.594s, table=0, n_packets=145375, n_bytes=9701297, priority=1 actions=NORMAL

The second flow above is the one that will modify the DHCP request internal vlan tag 1 to external vlan tag 1000 and pass it through. The reason that it is missing from the original flows is because I have physical network typo in my configuration file. When ovs agent hit the error and stopped setting up the virtual bridge or did not know how to set it up, it caused the issue. After it is fixed, it went through correctly