5:23 a.m.
Hello,
I'm testing ovirt node, both 4.1.5 and 4.1.6rc2.
I see that in both versions the network stack is configured with
NetworkManager enabled.
With plain CentOS I always disabled NetworkManager and only used classical
network service alone, so I have not background with NM, related to
hypervisor.
I have configured a vlan (untagged) for VMs, using bonding mode=4 (802.3ad).
I have some problems with my VMs: they are reachable from some parts and
not from others.
In parallel I have already asked network guys to crosscheck network
configurations of the datacenter, but I would like to have confirmation
that other ones are already using with success the combination of:
- NetworkManager on hypervisor
- bonding mode = 4 for VMs traffic
Another question for another aspect I never understood: with an environment
in the past (before 3.5 times if I remember well) I used 802.3ad but I had
to set lacp_rate=1 (fast) because I had connection problems with the
default lacp_rate=0 (slow) parameter.
I see that still the default is lacp_rate=0
Could it be the same this time? Is there any reason to set default
lacp_rate=0 in oVirt (or the reverse... ;-)?
Thanks in advance,
Gianluca
6:43 a.m.
Just use the UI to manage your network interfaces.
On Wed, Sep 13, 2017 at 6:23 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
Hello,
I'm testing ovirt node, both 4.1.5 and 4.1.6rc2.
I see that in both versions the network stack is configured with
NetworkManager enabled.
With plain CentOS I always disabled NetworkManager and only used classical
network service alone, so I have not background with NM, related to
hypervisor.
I have configured a vlan (untagged) for VMs, using bonding mode=4
(802.3ad).
I have some problems with my VMs: they are reachable from some parts and
not from others.
In parallel I have already asked network guys to crosscheck network
configurations of the datacenter, but I would like to have confirmation
that other ones are already using with success the combination of:
- NetworkManager on hypervisor
- bonding mode = 4 for VMs traffic
Another question for another aspect I never understood: with an
environment in the past (before 3.5 times if I remember well) I used
802.3ad but I had to set lacp_rate=1 (fast) because I had connection
problems with the default lacp_rate=0 (slow) parameter.
I see that still the default is lacp_rate=0
Could it be the same this time? Is there any reason to set default
lacp_rate=0 in oVirt (or the reverse... ;-)?
Thanks in advance,
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
6:46 a.m.
On Wed, Sep 13, 2017 at 1:43 PM, Donny Davis <donny(a)fortnebula.com> wrote:
Just use the UI to manage your network interfaces.
Just used and prolems arose...
hence the question ;-)
In the mean time, as I have no control on network configuration from a
switch point of view, I have asked network guys to verify.
My question was to verify that NM + 802.3AD is used ok from others
6:53 a.m.
As long as the switch is setup for 802.3AD (LACP) then you should be fine.
I used the UI to setup my bond's and here is the output from my hypervisor
[root@virtnode-3 ~]# systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: enabled)
Active: active (running) since Mon 2017-09-11 19:07:06 UTC; 1 day 16h ago
Docs: man:NetworkManager(8)
Main PID: 952 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─952 /usr/sbin/NetworkManager --no-daemon
Sep 11 20:12:15 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160735.0612]
ifcfg-rh: Ignoring connection /etc/sysconfig/network-scripts/ifcfg-storage
(53b19d46-6b08-f...me:storage.
Sep 11 20:12:16 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160736.8563]
device (p3p1): link connected
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.0798]
device (p3p2): link connected
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.0839]
device (bond0): link connected
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.7324]
ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-bond0.600
(cad7be9f-9e8c-bcab-4...m bond0.600")
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.7324]
ifcfg-rh: Ignoring connection
/etc/sysconfig/network-scripts/ifcfg-bond0.600
(cad7be9f-9e8c-b...me:bond0.600.
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.7533]
manager: (bond0.600): new VLAN device
(/org/freedesktop/NetworkManager/Devices/37)
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.7705]
manager: (storage): new Bridge device
(/org/freedesktop/NetworkManager/Devices/38)
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.7905]
device (bond0.600): link connected
Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: <info>
[1505160737.8477]
device (storage): link connected
Hint: Some lines were ellipsized, use -l to show in full.
[root@virtnode-3 ~]# rpm -qa vdsm
vdsm-4.19.28-1.el7.centos.x86_64
[root@virtnode-3 ~]#
On Wed, Sep 13, 2017 at 7:46 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Wed, Sep 13, 2017 at 1:43 PM, Donny Davis
<donny(a)fortnebula.com> wrote:
> Just use the UI to manage your network interfaces.
>
>
Just used and prolems arose...
hence the question ;-)
In the mean time, as I have no control on network configuration from a
switch point of view, I have asked network guys to verify.
My question was to verify that NM + 802.3AD is used ok from others
7:04 a.m.
On Wed, Sep 13, 2017 at 1:53 PM, Donny Davis <donny(a)fortnebula.com> wrote:
As long as the switch is setup for 802.3AD (LACP) then you should be
fine.
I used the UI to setup my bond's and here is the output from my hypervisor
OK, thanks.
I suppose bond0 is where you have your lacp bonding
What do you get in output on your node with the command
cat /proc/net/bonding/bond0
?
Could it do any difference to do 802.3ad on a tagged or untagged vlan?
Thanks,
Gianluca
2419
days inactive
2419
days old
4 comments
2 participants
participants (2)
-
Donny Davis -
Gianluca Cecchi