rhtyd opened a new issue #5716: URL: https://github.com/apache/cloudstack/issues/5716
With 4.16.0.0 release, if a VMware environment uses Vmxnet3 as the router nic controller then the isolated network VR deployment fails when router.extra.public.nics is not 0. However, VPC VR works in either case. The workaround with 4.16.0.0 is to either use (a) E1000 nic controller, or (b) use Vmxnet3 controller with the router.extra.public.nics set to 0 if the IaaS env has all public IP ranges in the same VLAN. The additional router nics are used when users acquire public IPs from IP ranges with different VLANs, otherwise these additional router nics aren't used in isolated network VR. As described in an old email by Kelvin below, the global setting and feature were introduced for legacy templates where hot-plugging wasn't supported: http://mail-archives.apache.org/mod_mbox/cloudstack-users/201304.mbox/%3ccd81efed.3b701%[email protected]%3E All modern systemvmtemplates had open-vm-tools installed and support hot-plugging which is what is used in the case of VPC VR, but nic-hotpluging isn't implemented for isolated network VR. ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ VR, Isolated Networks ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on main branch. --> ~~~ 4.16.0.0 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> VMware 6.7u3, with Vmxnet3 used a nic controller for routers/systemvms -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
