Thanks Rajani, I checked that the agent is running on SSVM:
root@s-1-VM:~# service cloud status
CloudStack cloud service (type=secstorage) is running: process id: 3887
When I run
*SSVM health check, it outputs:First DNS server is 192.168.0.100PING
192.168.0.100
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 192.168.0.0/24 network, so of course could not ping outside
world. Here are my simple network settings of my cloud(1Management
Some more info, on SSVM I can see the following routes, there is route
there, so why SSVM(eth2: 192.168.0.134) could not contact Management
Server(192.168.0.100)? Can someone help here? Thanks
root@s-1-VM:~# ip route
default via 192.168.0.100 dev eth2
169.254.0.0/16 dev eth0 proto kernel scope
Did you check if the agent is running on SSVM?
This wiki might help.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secondary+storage+troubleshooting
~Rajani
On Tue, Nov 11, 2014 at 5:04 AM, Dan Dong dongda...@gmail.com wrote:
Some more info, on SSVM I can see the
Maybe the problem is in the NIC configurations on the KVM Hypervisor?
auto em1
iface em1 inet static
address 192.168.0.101
netmask 255.255.255.0
gateway 192.168.0.100
dns-nameservers 192.168.0.100
auto cloudbr0
...
auto cloudbr1
...
Note that the default GW is pointed
