Is it possible to enable the AI on a lab setup? Mean do we need contracts and licenses to have it?
Some features do require a license, but you can connect to Infinity Portal for trial purposes.
ElasticXL do not allow update installation via CPUSE or via Smartconsole, will be available in future?
ElasticXL currently requires a clean install. Migrating from ClusterXL to ElasticXL is planned. The upgrade process from ElasticXL installations will be documented when the next version is available.
GARP are sent also with maestro if SMO fail?
With ElasticXL, we do not use an orchestrator. However, if the primary/pivot/SMO fails in ElasticXL cluster, a gratuitous ARP will be sent with its own MAC.
Are there any updates on automating Maestro major upgrades and JHF installs? Currently, JHFs have to be installed manually on MHO1, MHO2, first half of SG, second half of SG which could easily take 3-4h. I'd like to be able to trigger an upgrade from Mgmt which then logs onto MHOs, and SGMs to download the JHFs and install them one by one.
Yes there are some improvements in R82.
Do all nodes in ElasticXL have control plane and data plane active?
Data Plane separation is not supported with ElasticXL
Does ElasticXL still use CCP protocol?
yes
9000 series don't support ElasticXL?
Correct, though we expect to support it soon.
When the main member sends traffic to a secondary member for handling, how is that traffic addressed ? to the MAC of the secondary member? To the Sync IP?
Forwarding is done exactly the same as in a classic Pivot ClusterXL: via production interface it is received, with a special forward MAC address in the way.
How many member are allowed in a single ElasticXL cluster?
A single ElasticXL cluster can have two sites, each with up to three members. Gateways within the site are active-active whereas the sites are active/passive (only one can be active at a time).
What happens if the SMO fails?
The next code added to the cluster is promoted to the SMO.
VSX is not supported on Smart-1 Cloud, so if we want the Smart-1 Cloud we need to understand how to migrate from R81.20 VSX to R82 VSNext?
Right now, this must be done manually. We are working on a conversion tool, stay tuned!
What about interface sharing between VS in VSnext? Is it possible?
yes, you can set up a virtual bridge to share a physical interface
So there is no need to use the MHOs in the hardware setup? so three SGMs (9000/19000) per site and elasticXL. It really depends. If you are looking for a scalable environment, you need Maestro. ElasticXL is not scalable, and even with 3 appliances in a load-sharing config, you will get much less performance than with MHO + 3 appliances.
Does the HTTPS policy have a hit count?
Not currently.
Any improvements on standard SNMP monitoring for Maestro?
Yes, see: https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ScalablePlatforms_AdminGuide/Conte...
also related: https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ScalablePlatforms_AdminGuide/Conte...
Any idea about when R82 will be recommended?
All we can say, soon
