I checked iptables rules and noticed when new VM is created, no iptables chain is created for it on the host. SGs don't work.
Please assist me. On Sat, Jun 13, 2020 at 6:12 PM Fariborz Navidan <mdvlinqu...@gmail.com> wrote: > Hello, > I found out the issue is with security groups. Some SGs are blocking DHCP > traffic. I already have ingress rules in place on the default SG. It works > for old VMs but it seems existing ingress rules do not apply on new VMs. > > Please guide me. > > On Sat, Jun 13, 2020 at 4:56 PM Fariborz Navidan <mdvlinqu...@gmail.com> > wrote: > >> Any idea? >> >> On Sat, Jun 13, 2020 at 1:16 AM Fariborz Navidan <mdvlinqu...@gmail.com> >> wrote: >> >>> Yes, it can ping the VR if I configure the allocated IP on the VM >>> manually. >>> >>> On Sat, Jun 13, 2020 at 12:57 AM Andrija Panic <andrija.pa...@gmail.com> >>> wrote: >>> >>>> If you configure the IP (from that network range) manually on the VM - >>>> can >>>> you ping VR IP (inside that network) - i.e. is there LAN connectivity >>>> between a VM and it's VR? >>>> >>>> >>>> >>>> On Fri, 12 Jun 2020 at 19:29, Fariborz Navidan <mdvlinqu...@gmail.com> >>>> wrote: >>>> >>>> > DHCP entry for assigned IP exists on the VR inside file >>>> > /etc/cloudstack/dhcpentry.json and /etc/dhcphosts.txt >>>> > >>>> > On Fri, Jun 12, 2020 at 6:59 PM Fariborz Navidan < >>>> mdvlinqu...@gmail.com> >>>> > wrote: >>>> > >>>> > > Hi, There is no 'Unable' message in management server log. >>>> > > >>>> > > Thanks >>>> > > >>>> > > On Fri, Jun 12, 2020 at 9:28 AM Vivek Kumar >>>> > > <vivek.ku...@indiqus.com.invalid> wrote: >>>> > > >>>> > >> Have you checked the management logs, Sometime router goes in >>>> read-only >>>> > >> file system, So in log it says - unable to apply dhcp entry on >>>> router >>>> > and >>>> > >> file system in read-only mode ( something like this ). If this is >>>> the >>>> > case >>>> > >> then you won’t be able to provision any new VMs. >>>> > >> >>>> > >> >>>> > >> >>>> > >> Vivek Kumar >>>> > >> Manager - Cloud & DevOps >>>> > >> IndiQus Technologies >>>> > >> 24*7 O +91 11 4055 1411 | M +91 7503460090 >>>> > >> www.indiqus.com <http://indiqus.com/> >>>> > >> >>>> > >> This message is intended only for the use of the individual or >>>> entity to >>>> > >> which it is addressed and may contain information that is >>>> confidential >>>> > >> and/or privileged. If you are not the intended recipient please >>>> delete >>>> > the >>>> > >> original message and any copy of it from your computer system. You >>>> are >>>> > >> hereby notified that any dissemination, distribution or copying of >>>> this >>>> > >> communication is strictly prohibited unless proper authorization >>>> has >>>> > been >>>> > >> obtained for such action. If you have received this communication >>>> in >>>> > error, >>>> > >> please notify the sender immediately. Although IndiQus attempts to >>>> sweep >>>> > >> e-mail and attachments for viruses, it does not guarantee that >>>> both are >>>> > >> virus-free and accepts no liability for any damage sustained as a >>>> > result of >>>> > >> viruses. >>>> > >> >>>> > >> > On 11-Jun-2020, at 10:02 PM, Fariborz Navidan < >>>> mdvlinqu...@gmail.com> >>>> > >> wrote: >>>> > >> > >>>> > >> > Hello, >>>> > >> > Suddenly the VR stopped offering IP config to VMs via DHCP. I >>>> have >>>> > tried >>>> > >> > restarting network, removing VR and performing fresh health >>>> check. >>>> > >> Health >>>> > >> > check does not report any failure. >>>> > >> > >>>> > >> > Please advise. >>>> > >> > TIA >>>> > >> >>>> > >> >>>> > >>>> >>>> >>>> -- >>>> >>>> Andrija Panić >>>> >>>
