Ask Your Question
2

icehouse dhcp tap-port issue

asked 2014-09-22 15:33:26 -0500

makton gravatar image

I been beating my head over this. The tap port for the DHCP service on my "demo" network is tagged to 4095, instead of the vlan for the "demo network"

root@ostack-net:~# ovs-vsctl show
2614e0df-7213-4131-9232-aa3c72ce442e
    Bridge br-int
        fail_mode: secure
        Port "tapc5a1129e-3b"
            tag: 4095
            Interface "tapc5a1129e-3b"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "qr-5e87c241-0a"
            tag: 1
            Interface "qr-5e87c241-0a"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
    Bridge br-ex
        Port "br6"
            Interface "br6"
        Port br-ex
            Interface br-ex
                type: internal
        Port "qg-aea6ec2d-99"
            Interface "qg-aea6ec2d-99"
                type: internal
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "gre-c0a80802"
            Interface "gre-c0a80802"
                type: gre
                options: {in_key=flow, local_ip="192.168.8.1", out_key=flow, remote_ip="192.168.8.2"}
    ovs_version: "2.0.2"

I was able to get the DHCP working by manually changing the tag ID to the vlan id of the "demo" network (1), but this doesn't solve the reason for the system not setting it up properly, in the first place.

I'm not see any errors in the logs for either neutron or ovs. Anyone seen this and have an idea where I can look to resove it?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
3

answered 2014-09-22 22:41:43 -0500

makton gravatar image

Ok, I believe we have a resolution. Neutron is creating the DHCP port with the vlan tag of 4095. However, I never created a second network to see what it does, till now.

Using my "demo" account in "Horizon", I created a second network and router. The DHCP port on this new network and router uses the vlan tag of the IPs, aka it works!!. Any network made after is working properly. I deleted the first network and recreated it with a properly assigned tag ID.

It is possible that I used the incorrect user when creating the network, causing the incorrect tag ID on the DHCP, and using "Horizon" as the demo user and creating this way solved the issue.

I answered my own question. lol

edit flag offensive delete link more

Comments

Thanks for sharing

SGPJ gravatar imageSGPJ ( 2014-09-27 08:07:57 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-09-22 15:33:26 -0500

Seen: 3,310 times

Last updated: Sep 22 '14