OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: advanced networking with public IPs direct to VMs


No, watching the management server logs when I pull the power on one of the compute nodes it recognises the host is not responding to a ping and eventually marks the host status as "Alert" in the UI but it never tries to migrate the VMs that was running on the node.


>From memory when I put everything on one NIC (management, storage and guest traffic) the host status is marked as "Down" not alert which makes me think there is something not supported with multiple NICs and failover.


It is almost as though with multiple NICs the manager knows that there is a problem with the node but cannot definitely say it is down and so it cannot migrate the VM in case it is still running on that node.


I have been at this for well over a month now (off and on) and apart from when I used a single NIC VM HA has never worked. If the configuration I have posted looks okay then maybe it is just not supported unless of course you know differently ?


I did think it may be the default gateway being set to the guest VM subnet but if I don't do this then the SSVM has issues with communication.


I am going to do a side by side comparison of the management server logs for single NIC vs dual NICs (management/storage on one NIC, the other NIC for guest VMs) and see if there is anything obvious that stands out.


That aside if I can't get this working then can I just assign a public IP subnet to the guest VM when setting up advanced networking and if so how does it then in effect bypass the virtual router (in terms of NAT) or do I not need to worry about this ?

Thanks
________________________________
From: Rafael Weingärtner <rafaelweingartner@xxxxxxxxx>
Sent: 04 June 2018 21:15
To: users
Subject: Re: advanced networking with public IPs direct to VMs

Everything seems to be normal at a first glance. Do you see some sort of
error in the log files?

On Mon, Jun 4, 2018 at 11:39 AM, Jon Marshall <jms.123@xxxxxxxxxxxxx> wrote:

> CS version 4.11
>
> VM HA at the moment (not Host HA as yet)
>
> KVM
>
>
> For the management node just one NIC - 172.30.3.2/26 assigned to physical
> NIC.
>
>
> For the compute nodes -
>
>
> 3 NICs so as an example from one compute node -
>
>
> ifcfg-eth0
>
> BRIDGE=cloudbr0
>
>
> ifcfg-eth1
>
> BRIDGE=cloudbr1
>
>
> ifcfg-eth2
>
> BRIDGE=cloudbr2
>
>
> then the 3 bridges -
>
>
> ifcfg-cloudbr0
>
> ip address 172.30.3.3/26    <--- management network
>
>
> if-cloudbr1
>
> ip address 172.30.4.3/25  <-- guest traffic
>
> gateway 172.30.4.1
>
>
>
> ifcfg-cloubr2
>
> ip address 172.30.5.3 /28 <-- storage traffic
>
>
> traffic labels would be cloudbr0, cloudbr1, cloudbr2
>
>
> Can only get failover working when I put all traffic on same NIC.
>
>
>
> ________________________________
> From: Rafael Weingärtner <rafaelweingartner@xxxxxxxxx>
> Sent: 04 June 2018 15:31
> To: users
> Subject: Re: advanced networking with public IPs direct to VMs
>
> What type of failover are you talking about?
> What version are you using?
> What hypervisor are you using?
> How are you configuring your NICs in the hypervisor?
> How are you configuring the traffic labels in ACS?
>
> On Mon, Jun 4, 2018 at 11:29 AM, Jon Marshall <jms.123@xxxxxxxxxxxxx>
> wrote:
>
> > Hi all
> >
> >
> > I am close to giving up on basic networking as I just cannot get failover
> > working with multiple NICs (I am not even sure it is supported).
> >
> >
> > What I would like is to use 3 NICs for management, storage and guest
> > traffic. I would like to assign public IPs direct to the VMs which is
> why I
> > originally chose basic.
> >
> >
> > If I switch to advanced networking do I just configure a guest VM with
> > public IPs on one NIC and not both with the public traffic -
> >
> >
> > would this work ?
> >
>
>
>
> --
> Rafael Weingärtner
>



--
Rafael Weingärtner