Thank you Pearl. we managed to resolve it. On Fri, Jan 5, 2024 at 7:42 PM Pearl d'Silva <pearl.dsi...@shapeblue.com> wrote:
> Hi Palash, > > Can you try using cloudmonkey to first enable the virtualrouterelement (if > it is currently disabled) before enabling the network service provider via > UI. You can do it using: > > cloudmonkey configure virtualrouterelement id=<VirtualRouter Element ID> > enabled=true > > the virtual router element id can be found using the network service > provider id on the UI (where you are attempting to enable the provider): > cloudmonkey list virtualrouterelement nspid=<nsp_id> > > Once the router element has been enabled, the network service provider > would get enabled successfully. > > Regards, > Pearl > > > > > > > > > ------------------------------ > *From:* Palash Biswas <palash...@gmail.com> > *Sent:* January 5, 2024 5:45 AM > *To:* users@cloudstack.apache.org <users@cloudstack.apache.org> > *Subject:* Cloudstack Error: Fail to enable Virtual Router services. > > Hi, > > As current we able up Cloudstack with SystemVM (Console Proxy and SSVM), > we are trying create isolated network and found out the network offering is > empty. Hence, we go to our Cloudstack Zone -> Physical Network to do > verification services and found out virtual router is not up. When we try > manual start enable the services but it show fail with messages > “(VirtualRouter) Provider is not ready, cannot Enable the provider, please > configure the provider first”. > > Do anyone can kindly advise where the something or area that we can > further troubleshoot look into it. > > Attach a screenshot and management log. > > Regards > Palash > > >
