Hello,
We have successfully replaced the hardware appliances in our Maestro environment. In the next step we now want to activate further virtual systems and want or should probably adapt the virtual system configuration of the existing system. Now two questions:
1. the R81.20 Admin Guide also says: “If you change the number of CoreXL Firewall instances on a virtual system, there will be some downtime for that virtual system.” I was of the opinion that this restriction no longer exists in R81.20. Does anyone have experience with this -> can I change the number of CoreXL Firewall instances via the Smartconsole on the VS object without downtime or do I really need to plan for downtime?
2. we have 3 9700 appliances in our Maestro environment, with default distribution SND/FW_worker so 3*28 fw_worker / 3*4 SNDs
The current coreXL configuration is: 2 VS -> 14 v. instances + 2 VS -> 2 v. instances -> so already slightly overbooked. However, the overall environment is running well and is still far from the load limit.
What would be the recommended coreXL setup in the target design with 7 virtual systems with partly very different workloads?
a)2*7 v. instances + 2*1 v. instances + 3*4 v. instances =28 v. instances, -> this would make it more difficult to adapt to different workloads and I would have to adapt the existing systems.
b) or can I simply overbook, as the allocation is only virtual anyway -> e.g. 2*14 v. instances + 2*2 v. instances + 3*8 v. instances = 56 v. instances. Especially as I theoretically have 3*28 cores available in the Maestro network, i.e. 84 fw_worker cores
What is your experience?