Ask Your Question
0

br-ex getting random mac in kolla-ansible

asked 2018-02-08 04:16:37 -0500

akarki gravatar image

Hi, i am trying to install openstack(kolla ansible stable/pike) over openstack(kolla ansible stable/pike). 3 vm are use to install openstack 1 controller 2 compute. after deployment mac provided to br-ex seems to random. where does br-ex defines it mac..should it not be mac of neutron external interface

edit retag flag offensive close merge delete

Comments

br-ex is not same device as external interface, is a new interface with its own mac address others will have network issues with 2 devices sharing same mac.

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2018-02-09 05:11:42 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2018-03-15 11:20:47 -0500

nahian gravatar image

updated 2018-03-15 11:22:37 -0500

Though it is not the exact answer to your question, nevertheless As Eduardo said its not the same mac address, I am giving an example, Here you see the neu_ext_int, which is the neutron external interface, and br-ex, both have different mac addresses. And neutron external interface is bound to br-ex.

2: neu_ext_int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovs-system state UP group default qlen 1000
    link/ether fa:16:3e:ff:e0:05 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.15/24 brd 192.168.1.255 scope global neu_ext_int
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:feff:e005/64 scope link
       valid_lft forever preferred_lft forever
3: net_int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fa:16:3e:ff:00:05 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.15/24 brd 192.168.2.255 scope global net_int
       valid_lft forever preferred_lft forever
    inet 192.168.2.9/32 scope global net_int
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:feff:5/64 scope link
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:48:bd:ba:2e brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
5: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether ca:ee:5b:f3:c2:b0 brd ff:ff:ff:ff:ff:ff
6: vxlan_sys_4789: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000
    link/ether 5a:0e:76:e5:f0:cd brd ff:ff:ff:ff:ff:ff
    inet6 fe80::580e:76ff:fee5:f0cd/64 scope link
       valid_lft forever preferred_lft forever
7: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 9e:de:82:8b:ab:4a brd ff:ff:ff:ff:ff:ff
8: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 52:64:7a:98:3a:41 brd ff:ff:ff:ff:ff:ff
11: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 82:1c:11:54:1c:4f brd ff:ff:ff:ff:ff:ff

AND

 Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port neu_ext_int
            Interface neu_ext_int
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port br-ex
            Interface br-ex
                type: internal

You can get this information by running ovs-vsctl show command by executing Openvswitch docker container.

docker exec openvswitch_vswitchd ovs-vsctl show
edit flag offensive delete link more

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: 2018-02-08 04:16:37 -0500

Seen: 92 times

Last updated: Mar 15 '18