Well, the guide (Quick guide) is targeting CentOS 6.8 AFAIK, I will see if I have some time to update that to CentOS 7 in near future - if that makes sense ?
On Wed, 17 Oct 2018 at 17:56, Simon Weller <swel...@ena.com.invalid> wrote: > In addition to Andrija's comments below, I'd recommend you use Centos 7.x > rather than 6.x, as Centos/RHEL development is targeted towards that > release now and has been for a couple of years. > > > - Si > > ________________________________ > From: Andrija Panic <andrija.pa...@gmail.com> > Sent: Wednesday, October 17, 2018 10:51 AM > To: users > Subject: Re: Problems configuring KVM host > > Hi Alexandre, > > irrelevant to your explanation above (which is good, to understand whole > setup!), there is something with network configuration on the Zone level, I > assume, per the message from the script: > > https://github.com/apache/cloudstack/blob/master/agent/bindir/cloud-setup-agent.in#L76 > > > Above is an quick-installation link that you followed (all fine! and you > move MGMT to separate server), but that article it has external links to > how to configure KVM host networking - so we don't know how did you > configure it. In general, the NIC configuration (from the quick guide) > should be modified so that NIC is part of the BRIDGE (IP parameters you can > move from NIC to Bridge or not, it should not be relevant for this sample > setup) - and make sure that this bridge is defined as the "KVM traffic > label" while you configured your Zone for probably both the Management and > the Guest Network (you can also edit already existing zone - disable zone, > edit Guest and Management network (inside physical network, inside zone) to > define new KVM traffic label and finally enable zone). > > Anyway, please post configuration that you applied on KVM host and Zone > level - since it seems that setup-agent script don't know what bridge to > use for Management and Guest traffic. > Btw, Management server logs are located > here: /var/log/cloudstack/management/management-server.log (on the > management server, obviously :) ) > > Cheers > > On Wed, 17 Oct 2018 at 16:27, Alexandre Bruyere < > bruyere.alexan...@gmail.com> > wrote: > > > Hello. > > > > I'm trying to set up a small Cloudstack setup on a test bench, but I'm > > having issues getting the host/agent running properly. > > > > First, here's the configuration of the test bench: > > > > Server #1: > > Hardware - Two active NICs: one that goes out to the company's network > > (we'll call it Outer), the other into a switch on the bench (into a > private > > subnet that we'll call Inner). HP Proliant DG380 G5 (2x quad-core Intel > > Xeon - they do not support nested virtualization, 6GB RAM, HP P400 RAID > > controller running a single SATA HDD) > > Software: ESXi 5.5. Two virtual routers, one for each NIC. Two virtual > > machines: an Ubuntu VM that acts as a NAT router and bridge between Inner > > and Outer (we'll call it RT), and a Cloudstack management server > > (functional, we'll call it CSMan) connected to Inner. > > > > Server #2: > > Hardware: One active NIC on Inner. Same hardware as Server #1 except it > is > > using a single SAS drive. > > Software: CentOS 6.10 KVM host configured as per the "KVM Setup and > > Installation" section of this guide: > > > > > https://cloudstack-documentation.readthedocs.io/en/4.11.1.0/quickinstallationguide/qig.html > > . NIC is configured with a static Inner IP, gateway is RT, DNS servers > are > > the company's. > > > > Switch: Completely unconfigured Netgear 24-port switch. On the Inner > > network, there is no DHCP or DNS setup (as the guide I used specifically > > says to not add one for the purposes of this setup) > > > > Laptop: Simple laptop, Windows 10, configured with an address on Outer, > > default gateway is RT. Connects to Server #1 via the vSphere client using > > an Outer address, connects to the VMs and Server #2 via PuTTY using an > > Inner address > > > > > > Now onto the problem: > > CSMan simply fails to add the host, and I can't find any information on > why > > that is (can't find logs). Server #2, on the other hand, fails to > complete > > the cloudstack-setup-agent command, returning the error "Failed to get > > default route. Please configure your network ot have a default route." > > > > Searching the issue only returns a few mail threads that failed to help, > > and searching the error only returns installation guides and what appears > > to be the source for Cloudstack. > > > > Where should I start to even troubleshoot the issue? > > > > Thank you very much for your help. > > > > > -- > > Andrija Panić > -- Andrija Panić
