Please see my responses inline, prefixed by [SL].
On Nov 26, 2014, at 9:08 AM, frank weed <zorbusthekni...@gmail.com> wrote:
>> - You should not have an IP address assigned to enp0s3, which I'm assuming
>> is the physical interface in this VirtualBox VM. And the link status for
>> this interface is up, yes?
>
> Yes enp0s3 is the physical interface in Vitrualbox. There is no ip address
> assign to enp0s3.
>
>> - In addition to assigning an IP address to mgmt0, make sure you actually
>> set the mgmt0 interface to up ("ip link set mgmt0 up", if memory serves
>> correctly).
>
> So would that mean, enp0s3 and ovsbr0 be down?
[SL] No, enp0s3 needs to be up, but without an IP address. ovsbr0 should just
be whatever it defaults to (I don't recall having to manipulate/modify ovsbr0
at all.)
>> - Stupid question, I know, but you're sure that the VirtualBox networking
>> configuration isn't getting in the way, right?
>
> Yes, Virtualbox networking configuration is correct. If reset the
> configuration to where enp0s3 is the only one up and has an IP then the host
> is reachable on the network.
>
>> - Using "ovsbr0" instead of "mgmt0" is functionally equivalent, as far as I
>> know. The fact that assigning an IP address to ovsbr0 works but mgmt0
>> doesn't work leads me to believe the issue is with the
>> configuration/operation of the mgmt0 interface.
>
> So here is sample configured that I used on mgmt0:
>
> ovs-vsctl add-port ovsbr0 mgmt0 -- set interface mgmt0 type=internal
> ip addr add 192.168.0.2/24 broadcast 192.168.0.255 dev enp0s3
> ip route add default via 192.168.0.1
> Should it be different?
[SL] You're adding the IP address to enp0s3. Try modifying your first command
to this:
ip addr add 192.168.0.2/24 broadcast 192.168.0.255 dev mgmt0
Then be sure to set the mgmt0 interface to up:
ip link set mgmt0 up
> On Mon, Nov 24, 2014 at 8:55 AM, Scott Lowe <scott.l...@scottlowe.org> wrote:
> Please see my responses inline, prefixed by [SL].
>
>
> On Sun, Nov 16, 2014 at 06:24:20PM -0800, frank weed wrote:
>
> > I haved been trying to configure openvswitch to where I have a port for the
> > host that will be the mgmt port and then have virtual machine client
> > connected to it as well. Here is my setup:
> >
> > [root@localhost ~]# cat /etc/redhat-release
> > CentOS Linux release 7.0.1406 (Core)
> >
> > [root@localhost ~]# uname -a
> > Linux localhost.localdomain 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30
> > 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> >
> > Machine Type: Virtualbox
> >
> > [root@localhost ~]# ovs-vsctl show
> > xxxxxxx-xxxx-xxxxx-xxxx-xxxxx
> > Bridge "ovsbr0"
> > Port "enp0s3"
> > Interface "enp0s3"
> > Port "ovsbr0"
> > Interface "ovsbr0"
> > type: internal
> > Port "mgmt0"
> > Interface "mgmt0"
> > type: internal
> > ovs_version: "2.3.0"
> >
> > If I try to configure mgmt0 with the host ip, and I can not ping to the
> > host or out side of the host. If I configure the ovsbr0 with the host ip,
> > I can ping host and ping out side of the host. I even tried not configuring
> > the interfaces with an ip and just setup openvswitch. I can see on tcpdump
> > that the port mgmt0 is getting arp requests from other hosts. If I setup
> > mgmt0 with the host ip I do not see tcpdump getting any arp request on the
> > mgmt0 port.
> >
> > My question is, I am wondering why mgmt0 is not accessible on the network
> > when it is configured with a host ip. Also, is their something that I am
> > missing that I need to make this setup work?
>
>
> Hi Frank, this is a setup that *should* work. A few questions/thoughts:
>
> - You should not have an IP address assigned to enp0s3, which I'm assuming is
> the physical interface in this VirtualBox VM. And the link status for this
> interface is up, yes?
>
> - In addition to assigning an IP address to mgmt0, make sure you actually set
> the mgmt0 interface to up ("ip link set mgmt0 up", if memory serves
> correctly).
>
> - Stupid question, I know, but you're sure that the VirtualBox networking
> configuration isn't getting in the way, right?
>
> - Using "ovsbr0" instead of "mgmt0" is functionally equivalent, as far as I
> know. The fact that assigning an IP address to ovsbr0 works but mgmt0 doesn't
> work leads me to believe the issue is with the configuration/operation of the
> mgmt0 interface.
--
Scott
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
