11:34 p.m.
In my test setup for oVirt 3.1, I have 3 switches -- two basic ones with
no VLAN support for mgmt, and storage, and a building switch with VLAN
support. The network operations team has configured a trunk with 2 dual
1 Gb links on the building switch. If I configure the two network
interfaces in oVirt with binding mode 4, and assign a logical network
to the link without specifying a VLAN, it works fine. I'm told the
default untagged VLAN is 494 (which is what I want). On the other hand,
if I simply hard-code VLAN 494 in the logical network setup, it doesn't
work - I get no network traffic. I'm told that the switch is setup
correctly, and the problem is on my side. How can I debug?
Thanks,
Jason.
12:28 a.m.
On 23 Jul 2013 21:34, "Jason Keltz" <jas(a)cse.yorku.ca> wrote:
In my test setup for oVirt 3.1, I have 3 switches -- two basic ones with
no VLAN
support for mgmt, and storage, and a building switch with VLAN
support. The network operations team has configured a trunk with 2 dual 1
Gb links on the building switch. If I configure the two network interfaces
in oVirt with binding mode 4, and assign a logical network to the link
without specifying a VLAN, it works fine. I'm told the default untagged
VLAN is 494 (which is what I want). On the other hand, if I simply
hard-code VLAN 494 in the logical network setup, it doesn't work - I get no
network traffic. I'm told that the switch is setup correctly, and the
problem is on my side. How can I debug?
Thanks,
Jason.
That sounds normal to me. Traffic coming in on the native untagged VLAN
wouldn't appear on the VLAN interface. I have a similar set up, and I've
assigned an unused VLAN as the native VLAN on the trunk, added the VLANs I
care about to the allowed VLANs list, and created the appropriate tagged
logical networks.
Hope this helps,
Martin
12:54 a.m.
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--1065524572-1995495953-1374616462=:21120
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
On Tue, 23 Jul 2013, Martin Goldstone wrote:
=20
=20
On 23 Jul 2013 21:34, "Jason Keltz" <jas(a)cse.yorku.ca> wrote:
>
> In my test setup for oVirt 3.1, I have 3 switches -- two basic ones wit=
h
no VLAN support for mgmt, and storage, and a building switch with
VLAN
support. =A0The network operations team has configured a trunk with 2 dua=
l 1
Gb links on the building switch. =A0If I configure the two network
interf=
aces
in oVirt =A0with binding mode 4, and assign a logical network to the
link
without specifying a VLAN, it works fine. =A0I'm told the default untagge=
d
VLAN is 494 (which is what I want). =A0On the other hand, if I
simply
hard-code VLAN 494 in the logical network setup, it doesn't work - I get =
no
network traffic. I'm told that the switch is setup correctly, and
the
problem is on my side. =A0How can I debug?
>
> Thanks,
>
> Jason.
>
=20
That sounds normal to me. Traffic coming in on the native untagged VLAN
wouldn't appear on the VLAN interface. I have a similar set up, and I've
assigned an unused VLAN as the native VLAN on the trunk, added the VLANs =
I
care about to the allowed VLANs list, and created the appropriate
tagged
logical networks.
Thanks, Martin. I thought that the native VLAN would come through on the=20
VLAN interface as well. While this would explain why I couldn't get at=20
VLAN 494, it wouldn't explain why I couldn't get at another of the VLANS=20
on the same link -- still no traffic. I do a tcpdump and see nothing (but=
=20
the LACP stats show the link is up).
Jason.
--1065524572-1995495953-1374616462=:21120--
4152
days inactive
4152
days old
2 comments
2 participants
participants (2)
-
Jason Keltz -
Martin Goldstone