[Users] Same VLAN id, for different physical networks.
Alfred Angelov
alfred at space2u.com
Mon Jun 10 19:21:01 UTC 2013
Hey,
I might not have been clear on the description, let me try to be more
clear:
I got three physically different networks:
- access network (gives internet access and has routes etc)
- backup network (is an internal network without routing)
- storage network (is used for ovirtmngt and connection to a storage
sollution)
Both networks have separate switches and and cables, etc; but for
simplicity’s
sake I use same VLAN IDs on both of them for those VPSses/Servers that have
a VLAN.
In ovirt I have different NICs for those two networks; it looks
something like this:
- NIC1 - access network untagged
- NIC2 - access network VLANs (this actually a bonded interface of two
NICs so it provides
redundancy - this works fine)
- NIC3 - backup network untagged
- NIC4 - backup network VLANs (this is not bonded, as it does not need
redundancy)
- NIC5/6 - storage network (which is also a bonded interface that is
also the ovirtmngmt network)
I run the same network setup on all the hosts (currently 4).
As said NIC2 and NIC4 are used for VLANS, so when I wanted to add VLAN 4
for the access and
backup network I have gotten the error:
> Error: The specified VLAN ID (4) is already in use.
I hope this makes things more clear?
Mvh
Alfred Angelov
On 06/10/2013 08:02 PM, Itamar Heim wrote:
> On 06/10/2013 04:48 PM, Alfred Angelov wrote:
>> Hey,
>>
>> in my ovirt datacenter, I have two physical networks (one I use for
>> access, and one is internal for runing backups etc). They have different
>> IP addresses, but are created with same VLAN ids on both physical
>> networks.
>>
>> When I try to add those two networks in ovirt i get a (when I try to add
>> a VLAN with id 4):
>>
>> Error: The specified VLAN ID (4) is already in use.
>>
>> Anyone had simmilar issues and is there a way to fix this?
>>
>
> may i ask about the use case of using two interfaces on same vlan?
> I assume they are connected to same switch?
> (it means probably outbound routing goes only via one of the two
> interfaces?)
More information about the Users
mailing list