Configure Panorama for Network Segmentation

Verify that the Panorama appliances and firewalls support multiple interfaces, and have the prerequisite software versions and configurations.
The M-Series appliances must run Panorama 8.0 or later to use a separate interface for deploying updates and to use multiple interfaces for device management and log collection. The M-200 and M-600 appliances must run Panorama 8.1 or later. Panorama appliances deployed on ESXi, vCloud, Air, Hyper-V and KVM must run Panorama 8.1 or later.
If you deployed a Panorama or Log Collector as a virtual appliance, verify the Supported Interfaces for the Panorama Virtual Appliance.
The M-Series appliances must run Panorama 6.1 or later to use separate interfaces for log collection or Collector Group communication.
The initial configuration of each Panorama management server is complete. This includes configuration of the MGT interface.
To configure an IPv6 IP address for the Panorama MGT interface, you must configure both an IPv4
and IPv6 to successfully configure Panorama using an IPv6 IP address. Panorama does not support configuring the MGT interface with only an IPv6 IP address.
Log Collectors and Collector Groups are configured. This includes configuration of the MGT interface on the Log Collectors.
To configure an IPv6 IP address for the MGT interface of a Log Collector, you must configure both an IPv4
and IPv6 to successfully configure Panorama using an IPv6 IP address. Panorama does not support configuring the MGT interface with only an IPv6 IP address.
The initial configuration of the firewalls is complete, you have added the firewalls to Panorama as managed devices, and the firewalls in each subnetwork are assigned to a separate template.
The initial configuration of WildFire appliances is complete and you have added WildFire appliances to Panorama as managed devices.
Configure the interfaces on the solitary (non-HA) or active (HA) Panorama management server.
Because the MGT interface was configured during initial Panorama configuration, you don’t have to configure it again.
Perform these steps for each interface:
Log in to the Panorama Web Interface of the solitary (non-HA) or active (HA) Panorama management server.
Select
Panorama
Setup
Interfaces
.
Click an Interface Name to edit the interface.
Select
<interface-name>
to enable the interface.
Configure one or both of these field sets based on the IP protocols of your network:
IPv4—
IP Address
,
Netmask
, and
Default Gateway
IPv6—
IPv6 Address/Prefix Length
and
Default IPv6 Gateway
Select the services that the interface supports:
Device Management and Device Log Collection
—Manage firewalls, Log Collectors, and WildFire appliances and appliance clusters, collect logs that the Log Collectors generate, and query the Log Collectors for report information. To support a segmented network, you can enable these services on multiple interfaces.
Collector Group Communication
—Communicate with the Collector Groups that Panorama manages across all subnetworks.
Device Deployment
—Deploy software and content updates to managed firewalls, Log Collectors, and WildFire appliances and appliance clusters across all subnetworks.
Click
OK
to save your changes to the interface.
Click
Commit
Commit to Panorama
and
Commit
your changes.
Click
Commit
Push to Devices
and push the changes to the Collector Group that contain the Log Collectors you modified.
(
HA only
) Configure the interfaces on the passive Panorama management server.
Log in to the Panorama Web Interface of the active Panorama management server.
Select
Panorama
Managed Collectors
and select the passive HA peer.
Select
Interfaces
and click an interface to edit.
Check the
Enable Interface
box to enable the interface.
Configure one or both of these field sets based on the IP protocols of your network:
IPv4—
IP Address
,
Netmask
, and
Default Gateway
IPv6—
IPv6 Address/Prefix Length
and
Default IPv6 Gateway
Select the services that the interface supports:
Device Management and Device Log Collection
—Manage firewalls, Log Collectors, and WildFire appliances and appliance clusters, collect logs that the Log Collectors generate, and query the Log Collectors for report information. To support a segmented network, you can enable these services on multiple interfaces.
Collector Group Communication
—Communicate with the Collector Groups that Panorama manages across all subnetworks.
Device Deployment
—Deploy software and content updates to managed firewalls, Log Collectors, and WildFire appliances and appliance clusters across all subnetworks.
Click
OK
to save your changes to the interface.
Select
Commit
Commit and Push
to commit your changes to Panorama and to push the changes to Collector Groups that contain the passive HA peer you modified.
Configure each Log Collector to connect with a Panorama interface.
To support a segmented network, you can connect the Log Collectors in each subnetwork to separate Panorama interfaces. The interfaces must have
Device Management and Device Log Collection
enabled, as described in the previous step.
Log in to the Panorama Web Interface of the solitary (non-HA) or active (HA) Panorama management server.

Select

Panorama

Managed Collectors

and edit the Log Collector.

In the

Panorama Server IP

field, enter the IP address of an interface on the solitary (non-HA) or active (HA) Panorama.

(

HA only

) In the

Panorama Server IP 2

field, enter the IP address of an interface on the passive Panorama that will support

Device Management and Device Log Collection

if failover occurs on the active Panorama.

Click

OK

to save your changes.

Select

Commit

Commit and Push

to commit your changes to Panorama and to push the changes to Collector Groups that contain the Log Collector you modified.

Perform the following steps on each Dedicated Log Collector:

Access the Log Collector CLI by using emulation software such as PuTTY to open a SSH session to the Log Collector using its MGT interface IP address. When prompted, log in using Panorama administrator credentials.

Run the following commands, where

<IPaddress1>

is for the solitary (non-HA) or active (HA) Panorama and

<IPaddress2>

is for the passive Panorama (if applicable).

> 
configure  
# 
set deviceconfig system panorama-server 
<IPaddress1> panorama-server-2 
<IPaddress2>  
# 
commit  
(
HA only
) Configure an interface on the passive Panorama management server to deploy updates in case the active Panorama fails over.
Log in to the Panorama Web Interface of the passive Panorama management server.
Select
Panorama
Setup
Interfaces
.
Click an Interface Name to edit the interface.
Select
<interface-name>
to enable the interface.
Configure one or both of these field sets based on the IP protocols of your network:
IPv4—
IP Address
,
Netmask
, and
Default Gateway
IPv6—
IPv6 Address/Prefix Length
and
Default IPv6 Gateway
Select
Device Deployment
.
Click
OK
to save your changes.
Click
Commit
Commit to Panorama
and
Commit
your changes.
Configure the interfaces that the Log Collectors will use to collect logs from firewalls and communicate with other Log Collectors.
Because the MGT interface was configured during initial configuration of the Log Collectors, you don’t have to configure it again.
Log in to the Panorama Web Interface of the solitary (non-HA) or active (HA) Panorama management server.
Select
Panorama
Managed Collectors
and edit the Log Collector.
Select
Interfaces
and perform the following steps for each interface:
Click an interface name to edit that interface.
Select
<interface-name>
to enable the interface.
Configure one or both of the following field sets based on the IP protocols of your network.
I
Pv4
—
IP Address
,
Netmask
, and
Default Gateway
IPv6
—
IPv6 Address/Prefix Length
and
Default IPv6 Gateway
Select the functions that the interface supports:
Device Log Collection
—Collect logs from firewalls. You can load balance the logging traffic by enabling multiple interfaces to perform this function.
Collector Group Communication
—Communicate with other Log Collectors in the Collector Group.
Click
OK
to save your changes to the interface.
Click
OK
to save your changes to the Log Collector.
Select
Commit
Commit and Push
to commit your changes to Panorama and to push the changes to Collector Groups that contain the Log Collectors you modified.
Select
Panorama
Managed Collectors
to verify that the Log Collectors are synchronized and connected with Panorama.
The Configuration Status column should display
InSync
and the Run Time Status column should display
connected
.
Configure the firewalls to connect with a Panorama interface.
To support a segmented network, you can connect the firewalls in each subnetwork to separate Panorama interfaces. The interfaces must have
Device Management and Device Log Collection
enabled. This step assumes that you use separate templates to configure the firewalls in separate subnetworks.
In this example deployment, Panorama uses these interfaces to manage the firewalls but not to collect firewall logs. You specify which Dedicated Log Collectors will collect firewall logs when you configure Collector Groups.
Log in to the Panorama Web Interface of the solitary (non-HA) or active (HA) Panorama management server.
On Panorama, select
Device
Setup
Management
, select a
Template
and edit the Panorama Settings.
In the first
Panorama Servers
field, enter the IP address of an interface on the solitary (non-HA) or active (HA) Panorama.
(
HA only
) In the second
Panorama Servers
field, enter the IP address of an interface on the passive Panorama that will support device management if failover occurs.
Click
OK
to save your changes.
Select
Commit
Commit and Push
to commit your changes to Panorama and push the template changes to firewalls.
Select
Panorama
Managed Devices
to verify that the firewalls are synchronized and connected with Panorama.
The Device State column should display
Connected
. The Shared Policy and Template columns should display
InSync
.