Rakesh, so this is, as you may conclude now, an OS/template thing, and
nothing to do with ACS - ACD configures DHCP server inaode VR and also
tries to attach new NIC inside a VM, the rest is up to the OS.
Best,
On Thu, 13 Aug 2020, 09:44 Rakesh Venkatesh,
wrote:
> Hi Andrija
>
> Yes if I config
Hi Andrija
Yes if I configure eth1 manually inside VM to get Ip from dhcp then ping
works fine but not sure how to do this inside windows vm
On Wed, Aug 12, 2020 at 10:43 PM Andrija Panic
wrote:
> Hi Rakesh,
>
> if you configure eth1 manually inside a VM, but set it to obtain the IP via
> DHCP,
Hi Rakesh,
if you configure eth1 manually inside a VM, but set it to obtain the IP via
DHCP, does it obtain the IP properly then?
Best,
On Tue, 11 Aug 2020, 12:41 Rakesh Venkatesh,
wrote:
> Wei,
>
> This was the test done on ubuntu os. The initial issue was found on windows
> vm.
>
> Even if i
Wei,
This was the test done on ubuntu os. The initial issue was found on windows
vm.
Even if it can be solved by adding some config inside the vm, do we need to
do every time we delete/add additional NIC's to vm? That will be extra work
all the time right?
On Mon, Aug 10, 2020 at 5:43 PM Wei ZHO
Hi Rakesh,
It is not a bug. you need to configure the networks inside vm. for example
/etc/network/interfaces in old ubuntu versions or /etc/netplan in newer
ubuntu versions.
-Wei
On Monday, 10 August 2020, Rakesh Venkatesh
wrote:
> Hello Thomas
>
>
> Thanks for the reply. It looks like the NI
Ok no problem.
As suggested, I manually edited /etc/network/interfaces files to add eth1
and restarted networking service.
Ping works fine now from VR
# ping 10.10.2.25
PING 10.10.2.25 (10.10.2.25): 56 data bytes
64 bytes from 10.10.2.25: icmp_seq=0 ttl=64 time=1.981 ms
64 bytes from 10.10.2.25:
Sorry, I've not used v4.14, so someone else can comment on it being a bug.
I would advise you to enable the related nic in the file named interfaces
and restart the network service to check if that works.
On Mon, 10 Aug 2020, 8:29 pm Rakesh Venkatesh,
wrote:
> Hello Thomas
>
>
> Thanks for the
Hello Thomas
Thanks for the reply. It looks like the NIC is not configured properly in
VM. I dont see IP 10.10.2.23 being configured
# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host
Hello Venkatesh,
I'm guessing from the output provided that you have tried to ping the ip
from the VR.
Have you checked if the NIC is up on the VM?
you can run tcpdump on the related VM to check if the icmp packets are
reaching the VM.
Regards
Thomas
On Mon, 10 Aug 2020, 8:06 pm Rakesh Venkates
Hello,
I have created a VPC with three tiers in it (tier1, tier2. tier3) using
cloudstack 4.14.0.0 version with Ubuntu16 as OS for mgt, agent
I created a VM in tier1 and I am able to ping its IP address
# ping 10.10.1.51
PING 10.10.1.51 (10.10.1.51): 56 data bytes
64 bytes from 10.10.1.51: icmp_s
10 matches
Mail list logo
