Configuring interfaces for Master NGFW Engines

Master NGFW Engines can have two types of interfaces: interfaces for the Master NGFW Engine's own traffic, and interfaces that are used by the Virtual NGFW Engines hosted on the Master NGFW Engine.

You can add Physical Interfaces and VLAN Interfaces to a Master NGFW Engine. If you want to use a Physical Interface or VLAN Interface to host a Virtual NGFW Engine, you must select a Virtual Resource for the interface. The same Virtual Resource can be used on more than one Master NGFW Engine interface to allocate multiple interfaces to the same Virtual NGFW Engine. If you want the Virtual NGFW Engine to have multiple interfaces, you must use the same Virtual Resource on more than one Master NGFW Engine interface.

If you want to use a Physical Interface or VLAN Interface for the Master NGFW Engine’s own traffic, you must not select a Virtual Resource for the interface. You can configure several IPv4 addresses on each Physical Interface or VLAN Interface that does not have a Virtual Resource associated with it. The interfaces for the Master NGFW Engine’s own traffic are only used for system communications.

By default, the Physical Interface definitions for the Master NGFW Engine are mapped to the actual network interfaces on the Master NGFW Engine hardware in numerical order. If necessary, you can change the mapping using command-line tools on the Master NGFW Engine. This mapping can be done differently from one Master NGFW Engine node to another. Make sure that the interface that represents the same network interface on each Master NGFW Engine node is correctly cabled to the same network.