Creating a second Pod and Public IP ranges

[Brian Fitzpatrick]

Hi all,

We have been building a Cloudstack 4.15.2 environment  using Ubuntu 20.04 and 
KVM.

We have thus far only built one Pod with some clusters and hosts in clusters 
sharing nfs storage.

The existing Pod is on a physical subnet 10.250.0.0/22 (private address) but 
Public in terms of out on our network.

We have assigned some Public IP address ranges 10.250.2.xxx - 10.250.2.yyy ie. 
within this physical /22 network.

I would like to add a second Pod on a new subnet 10.250.20.0/22.

I guess, in order to support virtual routers hosted onto that new Pod, I need 
to add a new Public IP range that falls within it?

ie. 10.250.22.xxx - 10.250.22.yyy ?

There doesn't seem to be a way to link a Public IP range to a Pod? I haven't 
tested this yet but does it just link the Public range with the Pod subnet and 
gateway automatically ? associating the gateway?

So if somebody creates a network and it lives on Pod2 the Virtual router and 
network gets a public IP from that network. Or is there something I have to do 
to associate Public IP ranges to Pods?

Hope this makes sense?

Thanks

Brian

Re: cloudstack-sysvmadm access to 8096

[Brian Fitzpatrick]

Hi Wei,

Thanks for this. I still have it.

I initially upgraded from 4.15 to 4.15.1 but it failed as I didn't have the 
template. I downgraded back to 4.15 and first noticed then. I had the 404 
screen (as shown in your bug thread).

I re upgraded back to 4.15.1 but still have it. Not the 404 screen but the 
error x for input string: " ", an no hosts listed

I tried to change the Locale (as suggested) to en_US.UTF-8

(it was en-GB)

but I still get the error.

Thanks

Brian


-Original Message-
From: Wei ZHOU 
mailto:wei%20zhou%20%3custcweiz...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: cloudstack-sysvmadm access to 8096
Date: Sat, 24 Jul 2021 18:32:24 +0200


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



Hi Brian,


It is a known issue in cloudstack 4.15.0, it should has been fixed in

4.15.1.0.

<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcloudstack%2Fpull%2F4900data=04%7C01%7Cb.fitzpatrick%40chester.ac.uk%7C0c39026de7404d017d9f08d94ec0a4ec%7C18843e6e1846456ca05c500f0aee12f6%7C0%7C0%7C637627412094010279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000sdata=1PJ2HSyaBSXxLIoxIGqgWEeAU1K153poPvQs%2BAuF8cM%3Dreserved=0>

https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcloudstack%2Fpull%2F4900data=04%7C01%7Cb.fitzpatrick%40chester.ac.uk%7C0c39026de7404d017d9f08d94ec0a4ec%7C18843e6e1846456ca05c500f0aee12f6%7C0%7C0%7C637627412094010279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000sdata=1PJ2HSyaBSXxLIoxIGqgWEeAU1K153poPvQs%2BAuF8cM%3Dreserved=0



-Wei


On Saturday, 24 July 2021, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

wrote:


Thanks Wei,


I have now managed to register the 4.15.1 template, re upgraded and ran

the cloudstack-sysvmadm scripts

remembering to set the API port back to 0


All seems ok except I still can't see any hosts listed under

infrastructure.


I don't get a 404 screen any more but no hosts listed and a x for input

string " " error


Brian


-Original Message-

From: Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

mailto:brian%20fitzpatrick%20%3cb.fitzpatr...@chester.ac.uk>

brian%20fitzpatrick%20%3cb.fitzpatr...@chester.ac.uk

%3e>>

Reply-To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>

To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

 <

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:22us...@cloudstack.apache.org>

22us...@cloudstack.apache.org

<mailto:%22%20%3cus...@cloudstack.apache.org>

%22%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: cloudstack-sysvmadm access to 8096

Date: Fri, 23 Jul 2021 18:37:05 +



CAUTION !



This email was NOT sent using a University of Chester account, so we are

unable to verify the identity of the sender. Do not click links or open

attachments unless you recognise the sender and know the content is safe.



=




Hi Wei,



apt installed back to 4.15.0 versions



I seem now to have a problem registering the new systemvm template



I am using KVM, fill in the template for new url download as per

instruction, but appears to be a problem downloading 'Ready false'



Is there a way of force trying again?, I can't seem to delete it



Also, I appear to have lost my hosts list, they are running but the

infrastructure hosts page shows a '404 error' and 'Request Failed (431) For

input string " "'



Thanks very much for your help



Brian



-Original Message-


From: Wei ZHOU <


mailto:ustcweiz...@gmail.com>

ustcweiz...@gmail.com

>


<mailto:ustcweiz...@gmail.com>

ustcweiz...@gmail.com



mailto:wei%20zhou%20%3custcweiz...@gmail.com>

wei%20zhou%20%3custcweiz...@gmail.com

>


<mailto:wei%20zhou%20%3custcweiz...@gmail.com>

wei%20zhou%20%3custcweiz...@gmail.com



%3e>>


Reply-To:


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org



mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org





To: users <


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.or

Re: cloudstack-sysvmadm access to 8096

[Brian Fitzpatrick]

Thanks Wei,

I have now managed to register the 4.15.1 template, re upgraded and ran the 
cloudstack-sysvmadm scripts
remembering to set the API port back to 0

All seems ok except I still can't see any hosts listed under infrastructure.

I don't get a 404 screen any more but no hosts listed and a x for input string 
" " error

Brian

-Original Message-----
From: Brian Fitzpatrick 
mailto:brian%20fitzpatrick%20%3cb.fitzpatr...@chester.ac.uk%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: cloudstack-sysvmadm access to 8096
Date: Fri, 23 Jul 2021 18:37:05 +


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



Hi Wei,


apt installed back to 4.15.0 versions


I seem now to have a problem registering the new systemvm template


I am using KVM, fill in the template for new url download as per instruction, 
but appears to be a problem downloading 'Ready false'


Is there a way of force trying again?, I can't seem to delete it


Also, I appear to have lost my hosts list, they are running but the 
infrastructure hosts page shows a '404 error' and 'Request Failed (431) For 
input string " "'


Thanks very much for your help


Brian


-Original Message-

From: Wei ZHOU <

<mailto:ustcweiz...@gmail.com>

ustcweiz...@gmail.com

mailto:wei%20zhou%20%3custcweiz...@gmail.com>

wei%20zhou%20%3custcweiz...@gmail.com

%3e>>

Reply-To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>

To: users <

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users%20%3cus...@cloudstack.apache.org>

users%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: cloudstack-sysvmadm access to 8096

Date: Fri, 23 Jul 2021 18:54:28 +0200



CAUTION !



This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.



=




Hi Brian,



It seems your management server is not started. You can check the error in


log file /var/log/cloudstack/management/management-server.log



since cloudstack 4.15.1.0, cloudstack will check systemvm template before


database changes in upgrade, so if you forget to register systemvm


template, it is not a big issue any more.


what you need to do: (1) downgrade cloudstack (2) register new systemvm


template; (3) upgrade cloudstack.



cloudstack 4.16 will provide an option to install a new systemvm template


from rpm/deb packages.



-Wei




On Fri, 23 Jul 2021 at 16:56, Brian Fitzpatrick <


mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>


<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk





wrote:



Hi Wei,



Thanks very much for the reply



I have updated the mysql and restarted the management server but


unfortunately I am still getting the error



curl: (7) Failed to connect to localhost port 8096: Connection refused



when I run



cloudstack-sysvmadm



I am not sure the management server is fully starting up as a result of my


upgrade. I think I made a mistake in not updating the templates before the


ubuntu 20.04 apt update and upgrade



I am not sure on the best option, either resolve this connection refused


or try to rollback the upgrade (but I am not sure what state that will


leave me in?)



Thanks



Brian



-Original Message-


From: Wei ZHOU <


mailto:ustcweiz...@gmail.com>

ustcweiz...@gmail.com

>


<mailto:ustcweiz...@gmail.com>

ustcweiz...@gmail.com



mailto:wei%20zhou%20%3custcweiz...@gmail.com>

wei%20zhou%20%3custcweiz...@gmail.com

>


<mailto:wei%20zhou%20%3custcweiz...@gmail.com>

wei%20zhou%20%3custcweiz...@gmail.com



%3e>>


Reply-To:


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org



mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org





To: users <


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org



mailto:users%20%3cus...@cloudstack.apache.org>

users%20%3cus...@cloudstack.apache.org

>


<mailto:users%20%3cus...@cloudstack.apache.org>

users%20%3cus...@cloudstack.apache.org



%3e>>


Subject: Re: cloudstack-sysvmadm access to 8096


Dat

Re: cloudstack-sysvmadm access to 8096

[Brian Fitzpatrick]

Hi Wei,

apt installed back to 4.15.0 versions

I seem now to have a problem registering the new systemvm template

I am using KVM, fill in the template for new url download as per instruction, 
but appears to be a problem downloading 'Ready false'

Is there a way of force trying again?, I can't seem to delete it

Also, I appear to have lost my hosts list, they are running but the 
infrastructure hosts page shows a '404 error' and 'Request Failed (431) For 
input string " "'

Thanks very much for your help

Brian

-Original Message-
From: Wei ZHOU 
mailto:wei%20zhou%20%3custcweiz...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: cloudstack-sysvmadm access to 8096
Date: Fri, 23 Jul 2021 18:54:28 +0200


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



Hi Brian,


It seems your management server is not started. You can check the error in

log file /var/log/cloudstack/management/management-server.log


since cloudstack 4.15.1.0, cloudstack will check systemvm template before

database changes in upgrade, so if you forget to register systemvm

template, it is not a big issue any more.

what you need to do: (1) downgrade cloudstack (2) register new systemvm

template; (3) upgrade cloudstack.


cloudstack 4.16 will provide an option to install a new systemvm template

from rpm/deb packages.


-Wei



On Fri, 23 Jul 2021 at 16:56, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

wrote:


Hi Wei,


Thanks very much for the reply


I have updated the mysql and restarted the management server but

unfortunately I am still getting the error


curl: (7) Failed to connect to localhost port 8096: Connection refused


when I run


cloudstack-sysvmadm


I am not sure the management server is fully starting up as a result of my

upgrade. I think I made a mistake in not updating the templates before the

ubuntu 20.04 apt update and upgrade


I am not sure on the best option, either resolve this connection refused

or try to rollback the upgrade (but I am not sure what state that will

leave me in?)


Thanks


Brian


-Original Message-

From: Wei ZHOU <

<mailto:ustcweiz...@gmail.com>

ustcweiz...@gmail.com

mailto:wei%20zhou%20%3custcweiz...@gmail.com>

wei%20zhou%20%3custcweiz...@gmail.com

%3e>>

Reply-To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>

To: users <

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users%20%3cus...@cloudstack.apache.org>

users%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: cloudstack-sysvmadm access to 8096

Date: Fri, 23 Jul 2021 16:27:18 +0200



CAUTION !



This email was NOT sent using a University of Chester account, so we are

unable to verify the identity of the sender. Do not click links or open

attachments unless you recognise the sender and know the content is safe.



=




If you have access to database



mysql > update cloud.configuration set value='8096' where


name='integration.api.port';



then restart mgt server



-Wei





On Fri, 23 Jul 2021 at 16:19, Brian Fitzpatrick <


mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>


<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk





wrote:



Hello all,



I wonder if you could help, I have managed to get myself stuck in an


upgrade from 4.15.0 to 4.15.1



(I think I overlooked a stage, apologies)



I have lost my management interface (only one - small-test install)



I need to run the cloudstack-sysvmadm script



but I am getting the error



port 8096: Connection refused



I can't see a way of enabling api access without the web interface (which


isn't working)



Is there a way up doing this through command line?



Thanks



Brian

Re: cloudstack-sysvmadm access to 8096

[Brian Fitzpatrick]

Hi Wei,

Thanks very much for this

I'll follow your three steps

Much appreciated

Brian

-Original Message-
From: Wei ZHOU 
mailto:wei%20zhou%20%3custcweiz...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: cloudstack-sysvmadm access to 8096
Date: Fri, 23 Jul 2021 18:54:28 +0200


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



Hi Brian,


It seems your management server is not started. You can check the error in

log file /var/log/cloudstack/management/management-server.log


since cloudstack 4.15.1.0, cloudstack will check systemvm template before

database changes in upgrade, so if you forget to register systemvm

template, it is not a big issue any more.

what you need to do: (1) downgrade cloudstack (2) register new systemvm

template; (3) upgrade cloudstack.


cloudstack 4.16 will provide an option to install a new systemvm template

from rpm/deb packages.


-Wei



On Fri, 23 Jul 2021 at 16:56, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

wrote:


Hi Wei,


Thanks very much for the reply


I have updated the mysql and restarted the management server but

unfortunately I am still getting the error


curl: (7) Failed to connect to localhost port 8096: Connection refused


when I run


cloudstack-sysvmadm


I am not sure the management server is fully starting up as a result of my

upgrade. I think I made a mistake in not updating the templates before the

ubuntu 20.04 apt update and upgrade


I am not sure on the best option, either resolve this connection refused

or try to rollback the upgrade (but I am not sure what state that will

leave me in?)


Thanks


Brian


-Original Message-

From: Wei ZHOU <

<mailto:ustcweiz...@gmail.com>

ustcweiz...@gmail.com

mailto:wei%20zhou%20%3custcweiz...@gmail.com>

wei%20zhou%20%3custcweiz...@gmail.com

%3e>>

Reply-To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>

To: users <

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users%20%3cus...@cloudstack.apache.org>

users%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: cloudstack-sysvmadm access to 8096

Date: Fri, 23 Jul 2021 16:27:18 +0200



CAUTION !



This email was NOT sent using a University of Chester account, so we are

unable to verify the identity of the sender. Do not click links or open

attachments unless you recognise the sender and know the content is safe.



=




If you have access to database



mysql > update cloud.configuration set value='8096' where


name='integration.api.port';



then restart mgt server



-Wei





On Fri, 23 Jul 2021 at 16:19, Brian Fitzpatrick <


mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>


<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk





wrote:



Hello all,



I wonder if you could help, I have managed to get myself stuck in an


upgrade from 4.15.0 to 4.15.1



(I think I overlooked a stage, apologies)



I have lost my management interface (only one - small-test install)



I need to run the cloudstack-sysvmadm script



but I am getting the error



port 8096: Connection refused



I can't see a way of enabling api access without the web interface (which


isn't working)



Is there a way up doing this through command line?



Thanks



Brian

Re: cloudstack-sysvmadm access to 8096

[Brian Fitzpatrick]

Hi Wei,

Thanks very much for the reply

I have updated the mysql and restarted the management server but unfortunately 
I am still getting the error

curl: (7) Failed to connect to localhost port 8096: Connection refused

when I run

cloudstack-sysvmadm

I am not sure the management server is fully starting up as a result of my 
upgrade. I think I made a mistake in not updating the templates before the 
ubuntu 20.04 apt update and upgrade

I am not sure on the best option, either resolve this connection refused or try 
to rollback the upgrade (but I am not sure what state that will leave me in?)

Thanks

Brian

-Original Message-
From: Wei ZHOU 
mailto:wei%20zhou%20%3custcweiz...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: cloudstack-sysvmadm access to 8096
Date: Fri, 23 Jul 2021 16:27:18 +0200


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



If you have access to database


mysql > update cloud.configuration set value='8096' where

name='integration.api.port';


then restart mgt server


-Wei




On Fri, 23 Jul 2021 at 16:19, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

wrote:


Hello all,


I wonder if you could help, I have managed to get myself stuck in an

upgrade from 4.15.0 to 4.15.1


(I think I overlooked a stage, apologies)


I have lost my management interface (only one - small-test install)


I need to run the cloudstack-sysvmadm script


but I am getting the error


port 8096: Connection refused


I can't see a way of enabling api access without the web interface (which

isn't working)


Is there a way up doing this through command line?


Thanks


Brian

cloudstack-sysvmadm access to 8096

[Brian Fitzpatrick]

Hello all,

I wonder if you could help, I have managed to get myself stuck in an upgrade 
from 4.15.0 to 4.15.1

(I think I overlooked a stage, apologies)

I have lost my management interface (only one - small-test install)

I need to run the cloudstack-sysvmadm script

but I am getting the error

port 8096: Connection refused

I can't see a way of enabling api access without the web interface (which isn't 
working)

Is there a way up doing this through command line?

Thanks

Brian

Re: Management server reboot appears to cause vms on other hosts to shutdown?

[Brian Fitzpatrick]

ah...

Thanks Andrija that's good to know!

much appreciated

Brian


-Original Message-
From: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: Management server reboot appears to cause vms on other hosts to 
shutdown?
Date: Mon, 28 Jun 2021 19:12:32 +0200


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



Each (KVM) cloudstacl agent executes a heartbeat script (every 1min or so),

trying to write to a primary NFS server, ensuring it has the connectivity

working.


If this heartbeat fails - agent will say - "ok I'm stupid and less

reliable, NFS storage must be HA, so let me reboot myself/host in order to

regain access to NFS" (which is on your mgmt server)


/usr/lib64/cloud/agent/scripts/vm/hypervisor/kvm/kvmheartbeat.sh


Comment the line " echo b > /proc/sysrq-trigger " and KVM agent will NOT

reboot itself when NFS is unavailable. Something that is also wise to do in

production as well (trust me ... )



Cheers,



On Mon, 28 Jun 2021 at 18:57, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

wrote:


Hi Andrija,


Thanks for the reply


There is NFS primary storage on the management server but it doesn't have

any vm volumes on it, they are on other NFS primary servers.


So I thought I should have been safe to reboot


All vms on other hosts, vm volumes on other nfs shares living on other

servers, system vms and routers also on other servers


So all (I am fairly certain) that was on the server I rebooted was the one

and only Management server and mysql


Thanks


Brian


-Original Message-

From: Andrija Panic <

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

mailto:andrija%20panic%20%3candrija.pa...@gmail.com>

andrija%20panic%20%3candrija.pa...@gmail.com

%3e>>

Reply-To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>

To: users <

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users%20%3cus...@cloudstack.apache.org>

users%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: Management server reboot appears to cause vms on other hosts

to shutdown?

Date: Mon, 28 Jun 2021 17:44:57 +0200



CAUTION !



This email was NOT sent using a University of Chester account, so we are

unable to verify the identity of the sender. Do not click links or open

attachments unless you recognise the sender and know the content is safe.



=




NFS primary storage also on your management server?



On Sat, 26 Jun 2021 at 10:36, Brian Fitzpatrick <


mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>


<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk





wrote:



Hi Jordan,



Thanks for your reply. Apologies I might not have been clear.



The management server is aware of the vm and when I set the host that is


also the same server that is running the management server (and mysql) into


maintenance mode, I can see it not longer has any running vms on it. They


have migrated to other hosts. Cloud stack can see them. Bu when I then to


an apt update and reboot the management server, the vms on the other hosts


seem to have shutdown.



The reboot did take a while (15-20 mins), but I am surprised that it has


affected other kvm hosts, which I thought should just carry on running.


Unless I have missed something that was still on the management(and mysql)


server.



Thanks



Brian



-Original Message-


From: Yordan Kostov <


mailto:yord...@nsogroup.com>

yord...@nsogroup.com

>


<mailto:yord...@nsogroup.com>

yord...@nsogroup.com



mailto:yordan%20kostov%20%3cyord...@nsogroup.com>

yordan%20kostov%20%3cyord...@nsogroup.com

>


<mailto:yordan%20kostov%20%3cyord...@nsogroup.com>

yordan%20kostov%20%3cyord...@nsogroup.com



%3e>>


Reply-To:


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org



mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org





To:


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org



 <


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

Re: Management server reboot appears to cause vms on other hosts to shutdown?

[Brian Fitzpatrick]

Hi Andrija,

Thanks for the reply

There is NFS primary storage on the management server but it doesn't have any 
vm volumes on it, they are on other NFS primary servers.

So I thought I should have been safe to reboot

All vms on other hosts, vm volumes on other nfs shares living on other servers, 
system vms and routers also on other servers

So all (I am fairly certain) that was on the server I rebooted was the one and 
only Management server and mysql

Thanks

Brian

-Original Message-
From: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: Management server reboot appears to cause vms on other hosts to 
shutdown?
Date: Mon, 28 Jun 2021 17:44:57 +0200


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



NFS primary storage also on your management server?


On Sat, 26 Jun 2021 at 10:36, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

wrote:


Hi Jordan,


Thanks for your reply. Apologies I might not have been clear.


The management server is aware of the vm and when I set the host that is

also the same server that is running the management server (and mysql) into

maintenance mode, I can see it not longer has any running vms on it. They

have migrated to other hosts. Cloud stack can see them. Bu when I then to

an apt update and reboot the management server, the vms on the other hosts

seem to have shutdown.


The reboot did take a while (15-20 mins), but I am surprised that it has

affected other kvm hosts, which I thought should just carry on running.

Unless I have missed something that was still on the management(and mysql)

server.


Thanks


Brian


-Original Message-

From: Yordan Kostov <

<mailto:yord...@nsogroup.com>

yord...@nsogroup.com

mailto:yordan%20kostov%20%3cyord...@nsogroup.com>

yordan%20kostov%20%3cyord...@nsogroup.com

%3e>>

Reply-To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>

To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

 <

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

mailto:22us...@cloudstack.apache.org>

22us...@cloudstack.apache.org

<mailto:%22%20%3cus...@cloudstack.apache.org>

%22%20%3cus...@cloudstack.apache.org

%3e>>

Subject: RE: Management server reboot appears to cause vms on other hosts

to shutdown?

Date: Fri, 25 Jun 2021 09:10:44 +



CAUTION !



This email was NOT sent using a University of Chester account, so we are

unable to verify the identity of the sender. Do not click links or open

attachments unless you recognise the sender and know the content is safe.



=




Hello Brian,



May be I did not understand very well but from what you say I get

that the management server + SQL and NFS are on the same physical hosts

that are being managed by cloudstack?


If those VMs are not visible in Cloudstack, the system is not

aware that they exist so it wont try to roll them to another host if you

perform hypervisor host reboot.



Best regards,


Jordan



-Original Message-


From: Brian Fitzpatrick <


mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>


<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk





Sent: Friday, June 25, 2021 12:06 PM


To:


mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org

>


<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org




Subject: Management server reboot appears to cause vms on other hosts to

shutdown?




[X] This message came from outside your organization




Hi all,



Still relatively new to CloudStack and learning, testing etc.



I have created 1 management server with mysql on it and created 2 clusters

with a nfs primary storage server in each and a number of hosts in each.



I have been working through the servers, putting them in maintenance mode

(noting the vm migrations), updating and rebooting them. All working fine



I then wanted to update and reboot the server running the management and

mysql. It is also a host, so I set it in maintenance mode so no vms running

on it.



I thought if I update it and reboot, all I would lose for a period of time

was access to the management server, the vms should keep running on their

various hosts



The reboot, took longer than usual, it seemed to hang for 15-20mins before

shutting down and rebooting. To my surprise though I lost contact to all

the vms on the other hosts.



They all 

Re: Management server reboot appears to cause vms on other hosts to shutdown?

[Brian Fitzpatrick]

Hi Jordan,

Thanks for your reply. Apologies I might not have been clear.

The management server is aware of the vm and when I set the host that is also 
the same server that is running the management server (and mysql) into 
maintenance mode, I can see it not longer has any running vms on it. They have 
migrated to other hosts. Cloud stack can see them. Bu when I then to an apt 
update and reboot the management server, the vms on the other hosts seem to 
have shutdown.

The reboot did take a while (15-20 mins), but I am surprised that it has 
affected other kvm hosts, which I thought should just carry on running. Unless 
I have missed something that was still on the management(and mysql) server.

Thanks

Brian

-Original Message-
From: Yordan Kostov 
mailto:yordan%20kostov%20%3cyord...@nsogroup.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: RE: Management server reboot appears to cause vms on other hosts to 
shutdown?
Date: Fri, 25 Jun 2021 09:10:44 +


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



Hello Brian,


May be I did not understand very well but from what you say I get that 
the management server + SQL and NFS are on the same physical hosts that are 
being managed by cloudstack?

If those VMs are not visible in Cloudstack, the system is not aware 
that they exist so it wont try to roll them to another host if you perform 
hypervisor host reboot.


Best regards,

Jordan


-Original Message-

From: Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

Sent: Friday, June 25, 2021 12:06 PM

To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org


Subject: Management server reboot appears to cause vms on other hosts to 
shutdown?



[X] This message came from outside your organization



Hi all,


Still relatively new to CloudStack and learning, testing etc.


I have created 1 management server with mysql on it and created 2 clusters with 
a nfs primary storage server in each and a number of hosts in each.


I have been working through the servers, putting them in maintenance mode 
(noting the vm migrations), updating and rebooting them. All working fine


I then wanted to update and reboot the server running the management and mysql. 
It is also a host, so I set it in maintenance mode so no vms running on it.


I thought if I update it and reboot, all I would lose for a period of time was 
access to the management server, the vms should keep running on their various 
hosts


The reboot, took longer than usual, it seemed to hang for 15-20mins before 
shutting down and rebooting. To my surprise though I lost contact to all the 
vms on the other hosts.


They all shut down.


Apologies, if I have missed something here, I thought I understood. All virtual 
routers and system vms appeared to be running on the other hosts.


Is it because the management server took a while to reboot, the other hosts 
have lost contact and shutdown their vms? seems odd?


Any suggestions, help welcome. As I say, still learning!


Thanks


Brian

Re: Management server reboot appears to cause vms on other hosts to shutdown?

[Brian Fitzpatrick]

Hi Jordan,

Thanks for your reply. Apologies I might not have been clear.

The management server is aware of the vm and when I set the host that is also 
the same server that is running the management server (and mysql) into 
maintenance mode, I can see it not longer has any running vms on it (including 
system vms and routers). They have migrated to other hosts. Cloud stack can see 
them. But when I then to an apt update and reboot the management server, the 
vms on the other hosts seem to have shutdown.

The reboot did take a while (15-20 mins), but I am surprised that it has 
affected other kvm hosts, which I thought should just carry on running. Unless 
I have missed something that was still on the management(and mysql) server.

Thanks

Brian

-Original Message-
From: Yordan Kostov 
mailto:yordan%20kostov%20%3cyord...@nsogroup.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: RE: Management server reboot appears to cause vms on other hosts to 
shutdown?
Date: Fri, 25 Jun 2021 09:10:44 +


CAUTION !


This email was NOT sent using a University of Chester account, so we are unable 
to verify the identity of the sender. Do not click links or open attachments 
unless you recognise the sender and know the content is safe.


=



Hello Brian,


May be I did not understand very well but from what you say I get that 
the management server + SQL and NFS are on the same physical hosts that are 
being managed by cloudstack?

If those VMs are not visible in Cloudstack, the system is not aware 
that they exist so it wont try to roll them to another host if you perform 
hypervisor host reboot.


Best regards,

Jordan


-Original Message-

From: Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

Sent: Friday, June 25, 2021 12:06 PM

To:

<mailto:users@cloudstack.apache.org>

users@cloudstack.apache.org


Subject: Management server reboot appears to cause vms on other hosts to 
shutdown?



[X] This message came from outside your organization



Hi all,


Still relatively new to CloudStack and learning, testing etc.


I have created 1 management server with mysql on it and created 2 clusters with 
a nfs primary storage server in each and a number of hosts in each.


I have been working through the servers, putting them in maintenance mode 
(noting the vm migrations), updating and rebooting them. All working fine


I then wanted to update and reboot the server running the management and mysql. 
It is also a host, so I set it in maintenance mode so no vms running on it.


I thought if I update it and reboot, all I would lose for a period of time was 
access to the management server, the vms should keep running on their various 
hosts


The reboot, took longer than usual, it seemed to hang for 15-20mins before 
shutting down and rebooting. To my surprise though I lost contact to all the 
vms on the other hosts.


They all shut down.


Apologies, if I have missed something here, I thought I understood. All virtual 
routers and system vms appeared to be running on the other hosts.


Is it because the management server took a while to reboot, the other hosts 
have lost contact and shutdown their vms? seems odd?


Any suggestions, help welcome. As I say, still learning!


Thanks


Brian

Re: Management server reboot appears to cause vms on other hosts to shutdown?

[Brian Fitzpatrick]

Apologies

I should have of stated

Running CloudStack 4.15.0
Ubuntu 20.04
KVM

-Original Message-
From: b.fitzpatr...@chester.ac.uk
To: users@cloudstack.apache.org
Subject: Management server reboot appears to cause vms on other hosts to 
shutdown?
Date: Fri, 25 Jun 2021 10:06:19 +0100

Hi all,

Still relatively new to CloudStack and learning, testing etc.

I have created 1 management server with mysql on it and created 2 clusters with 
a nfs primary storage server in each and a number of hosts in each.

I have been working through the servers, putting them in maintenance mode 
(noting the vm migrations), updating and rebooting them. All working fine

I then wanted to update and reboot the server running the management and mysql. 
It is also a host, so I set it in maintenance mode so no vms running on it.

I thought if I update it and reboot, all I would lose for a period of time was 
access to the management server, the vms should keep running on their various 
hosts

The reboot, took longer than usual, it seemed to hang for 15-20mins before 
shutting down and rebooting. To my surprise though I lost contact to all the 
vms on the other hosts.

They all shut down.

Apologies, if I have missed something here, I thought I understood. All virtual 
routers and system vms appeared to be running on the other hosts.

Is it because the management server took a while to reboot, the other hosts 
have lost contact and shutdown their vms? seems odd?

Any suggestions, help welcome. As I say, still learning!

Thanks

Brian

Management server reboot appears to cause vms on other hosts to shutdown?

[Brian Fitzpatrick]

Hi all,

Still relatively new to CloudStack and learning, testing etc.

I have created 1 management server with mysql on it and created 2 clusters with 
a nfs primary storage server in each and a number of hosts in each.

I have been working through the servers, putting them in maintenance mode 
(noting the vm migrations), updating and rebooting them. All working fine

I then wanted to update and reboot the server running the management and mysql. 
It is also a host, so I set it in maintenance mode so no vms running on it.

I thought if I update it and reboot, all I would lose for a period of time was 
access to the management server, the vms should keep running on their various 
hosts

The reboot, took longer than usual, it seemed to hang for 15-20mins before 
shutting down and rebooting. To my surprise though I lost contact to all the 
vms on the other hosts.

They all shut down.

Apologies, if I have missed something here, I thought I understood. All virtual 
routers and system vms appeared to be running on the other hosts.

Is it because the management server took a while to reboot, the other hosts 
have lost contact and shutdown their vms? seems odd?

Any suggestions, help welcome. As I say, still learning!

Thanks

Brian

Re: Remote Access VPN

[Brian Fitzpatrick]

Thanks Andrija,

I will look through the setup again, I think the default iprange is on a 
separate network

Thanks

Brian

-Original Message-
From: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: Remote Access VPN
Date: Tue, 25 May 2021 23:30:46 +0200


CAUTION !


This email originated outside of the University of Chester. Do not click links 
or open attachments unless you recognise the sender and know the content is 
safe.


=



Another thing to keep in mind - if you work from office - usually there can

be only 1 IPSEC with L2TP connection from your office to outside/same IP -

i.e. you and your colleague can not connect at the same time to the same

public IP (i.e. to the same Remove VPN).



On Tue, 25 May 2021 at 23:29, Andrija Panic <

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

> wrote:


Hi Brian,


remote.access.vpn.client.iprange  should be set to some subnet OUTSIDE

your local network (where your laptop/PC is connected to / home/office) and

the Isolated network - so it should be "3rd" network.


For Windows, you there was a nice link somewhere...: here is one for

windows 8 - but same/identical is applicable for Windows 10:

<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftheresnomon.co%2Fconnecting-to-cloudstack-vpn-from-windows-8-8807b41af700data=04%7C01%7Cb.fitzpatrick%40chester.ac.uk%7C363792b0184d4afe72df08d91fc46e91%7C18843e6e1846456ca05c500f0aee12f6%7C0%7C0%7C637575750798430384%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=v3RTii5lx4lS%2B%2FTXNYkht9BN%2FNUWRPyyjxxXoffU8HQ%3Dreserved=0>

https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftheresnomon.co%2Fconnecting-to-cloudstack-vpn-from-windows-8-8807b41af700data=04%7C01%7Cb.fitzpatrick%40chester.ac.uk%7C363792b0184d4afe72df08d91fc46e91%7C18843e6e1846456ca05c500f0aee12f6%7C0%7C0%7C637575750798430384%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=v3RTii5lx4lS%2B%2FTXNYkht9BN%2FNUWRPyyjxxXoffU8HQ%3Dreserved=0



Hope that helps


Best,


On Tue, 25 May 2021 at 22:34, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

> wrote:


**Apologies not sure this was originally posted**


Hi all,


I am trying to setup Remote Access VPN on an DefaultIsolatedSourceNAT

network


I have created the VPN and a VPN user and pasted the shared key into a

Windows client but I am getting an error stating


the L2TP connection attempt failed because the security layer encountered

a processing error


I have looked through the documentation and have set


Requires encryption

MS-CHAP v2

PPP -> Enable LCP extensions


I haven't however changed the CloudStack parameter


remote.access.vpn.client.iprange setting from it's default, does this

need to be altered to match guest isolated network CIDR's? Not sure how the

virtual router sets up the VPN


Or am I doing something else wrong?


Thanks


Brian




--


Andrija Panić




--


Andrija Panić

Remote Access VPN

[Brian Fitzpatrick]

**Apologies not sure this was originally posted**

Hi all,

I am trying to setup Remote Access VPN on an DefaultIsolatedSourceNAT network

I have created the VPN and a VPN user and pasted the shared key into a Windows 
client but I am getting an error stating

the L2TP connection attempt failed because the security layer encountered a 
processing error

I have looked through the documentation and have set

Requires encryption
MS-CHAP v2
PPP -> Enable LCP extensions

I haven't however changed the CloudStack parameter

remote.access.vpn.client.iprange setting from it's default, does this need to 
be altered to match guest isolated network CIDR's? Not sure how the virtual 
router sets up the VPN

Or am I doing something else wrong?

Thanks

Brian

Remote access VPN

[Brian Fitzpatrick]

Hi all,

I am trying to setup Remote Access VPN on an DefaultIsolatedSourceNAT network

I have created the VPN and a VPN user and pasted the shared key into a Windows 
client but I am getting an error stating

the L2TP connection attempt failed because the security layer encountered a 
processing error

I have looked through the documentation and have set

Requires encryption
MS-CHAP v2
PPP -> Enable LCP extensions

I haven't however changed the CloudStack parameter

remote.access.vpn.client.iprange setting from it's default, does this need to 
be altered to match guest isolated network CIDR's? Not sure how the virtual 
router sets up the VPN

Or am I doing something else wrong?

Thanks

Brian

Re: Isolated guest network vlan between KVM hosts

[Brian Fitzpatrick]

Thanks Andrija,

I have done as you have suggested and moved vm1 on host1 and vm2 on host2 and 
ping fails between the vms

Unfortunately I am not managing the switch settings so I will ask to look into 
the trunk ports and whether they are ware of the vlan id.

As long as I can rule out the linux nic/bridge setup and Cloudstack config. 
(which I guess I can't fully, but I know where to look)

Thanks

Brian

-Original Message-
From: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: Isolated guest network vlan between KVM hosts
Date: Wed, 28 Apr 2021 14:46:20 +0200


CAUTION !


This email originated outside of the University of Chester. Do not click links 
or open attachments unless you recognise the sender and know the content is 
safe.


=



Hi there,


to further help your self, make sure you have VM1 on host1, VM2 on host2,

both VMs in the same network -  and try to ping VM2 from VM1 and the other

way around - if that fails - then, as you suggested, you do have Switch

configuration issue which doesn't allow traffic to pass from host1 to host2.

You need to configure switch ports in TRUNK mode with all VLANs that you

added as you the vlan range in ACS to be used by GUEST traffic.


Of course, based on your setup, make sure you don't break other traffic

(management/storage/public) when you touch your switch ports.


Best,






On Wed, 28 Apr 2021 at 12:53, Brian Fitzpatrick <

<mailto:b.fitzpatr...@chester.ac.uk>

b.fitzpatr...@chester.ac.uk

>

wrote:


Hi all,


I am new to this list and new to cloudstack, so apologies if this is an

obvious problem


I am trying to learn CloudStack and have setup a simple advanced

networking zone, 1 pod, 1 cluster, 2 hosts connected via the same

layer2 cisco switch, 1 nic in each host (Ubuntu, KVM)


If I setup a guest isolated lan and add a vm (setting up egress,

firewall, port fowarding), the vm can get out onto the public/internet

via the virtual router that gets automatically setup for my guest

network.


However if I move the vm to another host, it's internet stops working.


If I then move the virtual router to the same host it starts again.


So I guess it's something to do with isolated vlan tagging between

hosts via the switch?


I am not sure whether it's the switch, whether I am trying to do this

via one nic or settings I have missed in cloudstack.


my netplan host file(s) contain the same type of config; one on ip .25

one on ip .23 same subnet


  ethernets:

ens4f0np0:

  dhcp4: false

  dhcp6: false

  mtu: 1550


 bridges:

cloudbr0:

  interfaces: [ens4f0np0]

  addresses:

  - 10.250.0.25/22

  gateway4: 10.250.0.1

  nameservers:

addresses:

- 10.58.2.140

- 10.58.2.141


  mtu: 1500

  parameters:

stp: true

forward-delay: 4

  dhcp4: no

  dhcp6: no


The isolated guest network has vlan id allocated of 603


When I move a vm from one host to another, a vlan interface appears to

be created on the new kvm host


cloudbr0:  mtu 1550 qdisc noqueue

state UP group default qlen 1000

link/ether bc:97:e1:be:72:10 brd ff:ff:ff:ff:ff:ff

inet 10.250.0.25/22 brd 10.250.3.255 scope global cloudbr0

   valid_lft forever preferred_lft forever

inet6 fe80::be97:e1ff:febe:7210/64 scope link

   valid_lft forever preferred_lft forever


cloud0:  mtu 1500 qdisc noqueue state

UP group default qlen 1000

link/ether fe:00:a9:fe:32:cc brd ff:ff:ff:ff:ff:ff

inet 169.254.0.1/16 scope global cloud0

   valid_lft forever preferred_lft forever

inet6 fe80::40c4:4eff:fe5e:dcc0/64 scope link

   valid_lft forever preferred_lft forever


ens4f0np0.603@ens4f0np0:  mtu 1550

qdisc noqueue master brens4f0np0-603 state UP group default qlen 1000

link/ether bc:97:e1:be:72:10 brd ff:ff:ff:ff:ff:ff

inet6 fe80::be97:e1ff:febe:7210/64 scope link

   valid_lft forever preferred_lft forever


brens4f0np0-603:  mtu 1550 qdisc

noqueue state UP group default qlen 1000

link/ether bc:97:e1:be:72:10 brd ff:ff:ff:ff:ff:ff

inet6 fe80::e0d0:90ff:fe6a:71a7/64 scope link

   valid_lft forever preferred_lft forever


As I say the public/internet stops working


Not sure whether it's a switch port config, Linux nic config, or

something in Cloudstack


Very grateful of any pointers as to where to start looking to resolve

this issue


Thanks


Brian


Brian Fitzpatrick








--


Andrija Panić

Isolated guest network vlan between KVM hosts

[Brian Fitzpatrick]

Hi all,

I am new to this list and new to cloudstack, so apologies if this is an
obvious problem

I am trying to learn CloudStack and have setup a simple advanced
networking zone, 1 pod, 1 cluster, 2 hosts connected via the same
layer2 cisco switch, 1 nic in each host (Ubuntu, KVM)

If I setup a guest isolated lan and add a vm (setting up egress,
firewall, port fowarding), the vm can get out onto the public/internet
via the virtual router that gets automatically setup for my guest
network. 

However if I move the vm to another host, it's internet stops working. 

If I then move the virtual router to the same host it starts again. 

So I guess it's something to do with isolated vlan tagging between
hosts via the switch? 

I am not sure whether it's the switch, whether I am trying to do this
via one nic or settings I have missed in cloudstack. 

my netplan host file(s) contain the same type of config; one on ip .25
one on ip .23 same subnet

  ethernets:
ens4f0np0:
  dhcp4: false
  dhcp6: false
  mtu: 1550

 bridges:
cloudbr0:
  interfaces: [ens4f0np0]
  addresses:
  - 10.250.0.25/22
  gateway4: 10.250.0.1
  nameservers:
addresses:
- 10.58.2.140
- 10.58.2.141

  mtu: 1500
  parameters:
stp: true
forward-delay: 4
  dhcp4: no
  dhcp6: no

The isolated guest network has vlan id allocated of 603

When I move a vm from one host to another, a vlan interface appears to
be created on the new kvm host

cloudbr0:  mtu 1550 qdisc noqueue
state UP group default qlen 1000
link/ether bc:97:e1:be:72:10 brd ff:ff:ff:ff:ff:ff
inet 10.250.0.25/22 brd 10.250.3.255 scope global cloudbr0
   valid_lft forever preferred_lft forever
inet6 fe80::be97:e1ff:febe:7210/64 scope link 
   valid_lft forever preferred_lft forever
   
cloud0:  mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether fe:00:a9:fe:32:cc brd ff:ff:ff:ff:ff:ff
inet 169.254.0.1/16 scope global cloud0
   valid_lft forever preferred_lft forever
inet6 fe80::40c4:4eff:fe5e:dcc0/64 scope link 
   valid_lft forever preferred_lft forever

ens4f0np0.603@ens4f0np0:  mtu 1550
qdisc noqueue master brens4f0np0-603 state UP group default qlen 1000
link/ether bc:97:e1:be:72:10 brd ff:ff:ff:ff:ff:ff
inet6 fe80::be97:e1ff:febe:7210/64 scope link 
   valid_lft forever preferred_lft forever

brens4f0np0-603:  mtu 1550 qdisc
noqueue state UP group default qlen 1000
link/ether bc:97:e1:be:72:10 brd ff:ff:ff:ff:ff:ff
inet6 fe80::e0d0:90ff:fe6a:71a7/64 scope link 
   valid_lft forever preferred_lft forever

As I say the public/internet stops working

Not sure whether it's a switch port config, Linux nic config, or
something in Cloudstack 

Very grateful of any pointers as to where to start looking to resolve
this issue

Thanks

Brian

Brian Fitzpatrick