Running Secure SD-WAN Engines as Master Engines
There are some hardware requirements and configuration limitations when you use an Secure SD-WAN Engine as a Master Engine.
Running the Secure SD-WAN Engine as a Master Engine does not require a third-party virtualization platform. When you run Secure SD-WAN as a Master Engine, the Secure SD-WAN hardware provides the virtual environment and resources for the hosted Virtual Engines.
You can run Master Engines on the following types of hardware platforms:
- Purpose-built Secure SD-WAN appliances with 64-bit architecture
- Third-party hardware with 64-bit architecture that meets the hardware requirements
For information about system requirements, see the Release Notes.
The following limitations apply when you use an Secure SD-WAN Engine as a Master Engine:
- Each Master Engine must run on a separate 64-bit physical device.
When Secure SD-WAN Engine is running on a virtualization platform or a cloud virtualization platform, Master Engines and Virtual Engines are not supported.
- All Virtual Engines hosted by a Master Engine or Master Engine cluster must have the same role and the same Failure Mode (fail-open or fail-close).
- Master Engines can allocate VLANs or interfaces to Virtual Engines. If the Failure Mode of the Virtual IPS engines or Virtual Layer 2 Engines is Normal (fail-close) and you want to allocate VLANs to several engines, you must use the Master Engine cluster in standby mode.