cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Dong <>
Subject Re: SSVM could not access Management Server.
Date Mon, 10 Nov 2014 23:34:21 GMT
Some more info, on SSVM I can see the following routes, there is route
there, so why SSVM(eth2: could not contact Management
Server( Can someone help here? Thanks
root@s-1-VM:~# ip route
default via dev eth2 dev eth0  proto kernel  scope link  src via dev eth1 via dev eth1 dev eth1  proto kernel  scope link  src dev eth2  proto kernel  scope link  src dev eth3  proto kernel  scope link  src

2014-11-10 15:12 GMT-06:00 Dan Dong <>:

> Hi, All,
>   When debugging why my ISOs could not be registered, I found when I
> logged into SSVM, I could not even ping the Management Server, although
> they are both in the network, so of course could not ping
> outside world. Here are my simple network settings of my cloud(1Management
> Server + 1 KVM hypervisor):
> 1. Management server have 2 NICs:
>            em2 pointing outside with
>            em1 pointing inside with (also serves as DNS
> and Gateway of the cloud)
> 2. One KVM hypervisor which has 1 NIC: em1 with
> 3. VMs created on KVM hypervisor will sit on the same network of
> The weird thing is that I can access the internet from the KVM hypervisor
> as NAT is enabled on the Management Server, but for the SSVM(IP of eth2:
> running on it, it could not even see the Management
> Server( on em1). Should one manually re-configure routing
> tables on the SSVM to solve this problem or it is caused by the initial
> network design of the cloud? Thanks!
> Cheers,
> Dan

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message