Hello Ranjit, When you add secondary IPs to the instance, it means you will provide the same subnet IP in secondary interface of the NIC, So you have to configure your VM in such a way so that they can obtain the IP from DHCP ( You create sub interface of your primary interface i.e tho is your primary then eth0:0, eth0:1 is your sub interface .
If you are adding another network in your VM it means that you are adding a additional NIC in your VM thus - You will have to configure your second NIC config file inside of the VM so that it can get the IP from DHCP ( i.e eth0, eth1 ). Vivek Kumar Sr. Manager - Cloud & DevOps IndiQus Technologies M +91 7503460090 www.indiqus.com > On 23-Oct-2021, at 2:27 AM, Ranjit Jadhav <ranjeet.jad...@gmail.com> wrote: > > Thanks for getting back to me. At the ACS level network is configured fine > but at the OS level, it does not get updated. By default, OS is using DHCP. > > In this case, how can we automatically configure secondary IP on the server > i.e. CentOS, Ubuntu, Windows etc. > > Thank you, > Ranjit > > On Wed, Oct 20, 2021 at 12:05 PM Wei ZHOU <ustcweiz...@gmail.com> wrote: > >> Hi, >> >> For each isolated network with source NAT, cloudstack assigns a public IP >> to the network as the source NAT IP. Therefore it is not an issue. >> >> To add secondary IPs, go to vm details -> NICs tab -> choose a NIC -> click >> icon 'Edit secondary IPs'. >> >> -Wei >> >> On Tue, 19 Oct 2021 at 23:35, Ranjit Jadhav <ranjeet.jad...@gmail.com> >> wrote: >> >>> Hello guys, >>> >>> We are using Xenserver for host and configured Isolated Network ..... but >>> we are facing the following issues >>> >>> 1) One IP gets reserved for source-nat per user >>> >>> 2) How can we assign secondary IP to the instance. >>> >>> There are a few more issues/queries related to the network. >>> >>> Thanks and Regards, >>> Ranjit >>> >>
