Thank you Scott.
I think this is probably a case of inexperience in networking. 

Below is the information you asked for. I think the problem is that my server 
is connected to a DLink DIR-850L wireless router which is connected to the 
internet. My router does not support VLANs.
This more than likely explains why the VM cannot get a IP address. I would 
think I need the wireless router to support VLANs and VLAN trunking. 
Could this be the issue?


root@Ipnu-Nesia:/home/nesia# ovs-vsctl add-br ovsbr0
root@Ipnu-Nesia:/home/nesia# ovs-vsctl add-port ovsbr0 eno1
root@Ipnu-Nesia:/home/nesia# ovs-vsctl show
3c71bb82-137a-4013-a7eb-f2e63103c946
    Bridge "ovsbr0"
        Port "eno1"
            Interface "eno1"
        Port "ovsbr0"
            Interface "ovsbr0"
                type: internal
    ovs_version: “2.5.0"


root@Ipnu-Nesia:/home/nesia# virsh net-start ovs-network
Network ova-network started 

++++++++VMS Started
    The other twoVMS do not use port groups
root@Ipnu-Nesia:/home/nesia# ovs-vsctl show


3c71bb82-137a-4013-a7eb-f2e63103c946
    Bridge "ovsbr0"
        Port "eno1"
            Interface "eno1"
        Port "vnet0"
            Interface "vnet0"
        Port "vnet2"
            tag: 3
            Interface "vnet2"
        Port "ovsbr0"
            Interface "ovsbr0"
                type: internal
        Port "vnet1"
            Interface "vnet1"
    ovs_version: "2.5.0"

root@Ipnu-Nesia:/home/nesia# ovs-vsctl list port vnet2
_uuid               : a6db72e9-01da-4589-b70e-ccb8fef35fa7
bond_active_slave   : []
bond_downdelay      : 0
bond_fake_iface     : false
bond_mode           : []
bond_updelay        : 0
external_ids        : {}
fake_bridge         : false
interfaces          : [de2a7827-0658-4661-a75a-15de68cee6e4]
lacp                : []
mac                 : []
name                : "vnet2"
other_config        : {}
qos                 : []
rstp_statistics     : {}
rstp_status         : {}
statistics          : {}
status              : {}
tag                 : 3
trunks              : []
vlan_mode           : []

root@Ipnu-Nesia:/home/nesia# ovs-vsctl list port eno1
_uuid               : 0a0a7d07-a99f-4ebf-9582-ef55997d872c
bond_active_slave   : []
bond_downdelay      : 0
bond_fake_iface     : false
bond_mode           : []
bond_updelay        : 0
external_ids        : {}
fake_bridge         : false
interfaces          : [8df61c80-e5bb-4e26-afe0-1c185f501854]
lacp                : []
mac                 : []
name                : "eno1"
other_config        : {}
qos                 : []
rstp_statistics     : {}
rstp_status         : {}
statistics          : {}
status              : {}
tag                 : []
trunks              : []
vlan_mode           : []
root@Ipnu-Nesia:/home/nesia#


> On 10 Aug 2016, at 6:33 AM, Scott Lowe <scott.l...@scottlowe.org> wrote:
> 
> Please see my response below.
> 
> 
>> On Aug 9, 2016, at 1:02 AM, Randolph Hill <rdhil...@icloud.com> wrote:
>> 
>> New to setting up OVS with Vlans.
>> I performed the following steps below. When I  boot a  vm/domain, during the 
>> boot process the interface does not come up. 
>> 
>> 1. ovs-vctl add-br ovsbr0
>> 2. ovs-vsctl add-port ovsbr0 eno1
>> 3. ifconfig eno1 0
>> 4. dhclient ovsbr0
>> 5.  created the following network firm
>>     <network>
>>  <name>ovs-network</name>
>>  <forward mode='bridge'/>
>>  <bridge name='ovsbr0'/>
>>  <virtualport type='openvswitch'/>
>>  <portgroup name='vlan-01' default='yes'>
>>  </portgroup>
>>  <portgroup name='vlan-02'>
>>    <vlan>
>>      <tag id='2'/>
>>    </vlan>
>>  </portgroup>
>>  <portgroup name='vlan-03'>
>>    <vlan>
>>      <tag id='3'/>
>>    </vlan>
>>  </portgroup>
>>  <portgroup name='vlan-all'>
>>    <vlan trunk='yes'>
>>      <tag id='2'/>
>>      <tag id='3'/>
>>    </vlan>
>>  </portgroup>
>> </network>
>> 
>> 6. virsh net-define /var/tmp/ovs-network.xml
>> 7.  virsh net-start ovs-network
>> 8.  virsh net-autostart ovs-network
>> 
>> 
>> 9. Added entry to domain configuration file:
>>     <interface type='network'>
>>      <mac address='52:54:00:63:e4:44'/>
>>      <source network='ovs-network' portgroup='vlan-03'/>
>>      <model type='virtio'/>
>>      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
>> function='0x0'$
>>    </interface>
>> 
>> 
>> The domain proceeds boots after trying to bring up the interface for 3 
>> minutes.  a virtual port is create vnet2.
>> When I log into the domain, there is no IP address assigned.
>> 
>> Am I missing something?
> 
> 
> Everything seems OK, based on the information provided. Could you post the 
> output of `ovs-vsctl show`, as well as the output of `ovs-vsctl list port 
> vnet2` and `ovs-vsctl list port eno1`? BTW, I'm assuming that eno1 is your 
> physical uplink, yes?
> 
> A few things you can check/verify:
> 
> - Is VLAN 3 actually tagged by the physical switch on the eno1 uplink?
> - Has the eno1 link been set to UP using `ip link set eno1 up` (or the 
> equivalent)?
> 
> -- 
> Scott

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to