Hi Vivek, Your first message arrived fine. This sounds like ingress/egress rules which are causing the issue - google/CSdocs should provide some good information on this. Can you fully install guest VMs or are you just testing with SystemVMs?
Thanks, Marty On 24 April 2014 08:30, Vivek Sampara <ravensnowb...@gmail.com> wrote: > Hi guys, > > Im not sure if the previous mail got through as it guidelines say, i > should resend it in plain text, so i am sending this again. > > We've tried 3 Different types of cloudstack installations . 1. Basic > .2 Advanced without security Groups , 3. Advanced with security group > chekbox but in all these settings , we couldn't access the VMS. > Sometimes we could ping them but just cannot SSH. Although we were > able to SSH from the Cloudstack server using the same IP. > > Here is what we trying to implement. I've attached the image of my > work place. We are just trying to access the VMS Created by cloudstack > from my laptop , dev machine 1 and dev machine 2. > > I left zone's guest cidr as 10.1.1.0/24 > CloudStack management server (csman1) running on CentOS 6.5: 192.168.1.149 > The storage server (nas1): 192.168.44.2 ( 192.168.1.149 ) > The CentOS 6.5 KVM hypervisor (kvm1): ( 192.168.1.149 ) > The default gateway for the management network: 192.168.44.254 ( 192.168.1.1 ) > The default gateway for the public network: 192.168.65.254 ( 192.168.1.1 ) > Management IP range dedicated to System VM communication: ( > 192.168.1.150 ) to ( 192.168.1.170 ) - POD RANGE > Public IP range dedicated to CloudStack use: ( 192.168.1.180 ) to ( > 192.168.1.200 ) Public Network > > My Laptop IP : 101, > Dev Machine 1 IP : 102 > Dev Machine 2 IP : 103 > > We kept trying suggestions from different blogs for over 79 times. > Including OS re installation, Cloudstack reinstallation, Changing KVM > from acton-systemvm-02062012.qcow2.bz2 and > systemvm64template-2014-01-14-master-kvm.qcow2.bz2 . > > Any Help ? > > Thanks
