Deploy Panorama with Dedicated Log Collectors
|
Perform the initial setup of the Panorama management server (virtual appliances or M-Series appliances) and the Dedicated Log Collectors.
|
For each M-Series appliance:
Rack mount the M-Series appliance. Refer to the
M-100 or M-500 Hardware Reference Guide
for instructions.
Perform Initial Configuration of the M-Series Appliance.
To reduce the traffic load on the management (MGT) interface and to improve security for management traffic, Palo Alto Networks recommends configuring Panorama to use the Eth1 and Eth2 interfaces for log collection and Collector Group communication. You define these interfaces during initial configuration of the Panorama management server.
Configure each array.
This task is required to make the RAID disks available for logging. Optionally, you can add disks to
Increase Storage on the M-Series Appliance.
Register Panorama and Install Licenses.
Install Content and Software Updates for Panorama.
For each virtual appliance (if any):
Install the Panorama Virtual Appliance.
Perform Initial Configuration of the Panorama Virtual Appliance.
Register Panorama and Install Licenses.
Install Content and Software Updates for Panorama.
For the Panorama management server (virtual appliance or M-Series appliance), you must also
Set Up HA on Panorama.
|
Switch from Panorama mode to Log Collector mode on each M-Series appliance that will be a Dedicated Log Collector.
Switching the mode of an M-Series appliance deletes any existing log data and deletes all configurations except the management access settings. After the switch, the M-Series appliance retains CLI access but loses web interface access.
|
Connect to the M-Series appliance in one of the following ways:
Attach a serial cable from your computer to the Console port on the M-Series appliance. Then use terminal emulation software (9600-8-N-1) to connect.
Use terminal emulation software such as PuTTY to open an SSH session to the IP address that you specified for the MGT interface of the M-Series appliance during initial configuration.
Log in to the CLI when prompted. Use the default admin account and the password that you specified during initial configuration.
Switch to Log Collector mode by entering the following command:
>
request system system-mode logger
Enter Y to confirm the mode change. The M-Series appliance reboots. If the reboot process terminates your terminal emulation software session, reconnect to the M-Series appliance to see the Panorama login prompt.
If you see a
CMS Login
prompt, this means the Log Collector has not finished rebooting. Press Enter at the prompt without typing a username or password.
Log back in to the CLI.
Verify that the switch to Log Collector mode succeeded:
>
show system info | match system-mode
If the mode change succeeded, the output displays:
system-mode: logger
|
|
Record the serial number of each Log Collector.
You need the serial numbers to add the Log Collectors as managed collectors on the Panorama management server.
|
At the CLI of each Log Collector, enter the following command to display its serial number.
>
show system info | match serial
Record the serial number.
|
|
Add each Log Collector as a managed collector.
|
Use the web interface of the primary Panorama management server peer to
Configure a Managed Collector:
Select
Panorama > Managed Collectors
and
Add
the managed collector.
In the
General
tab, enter the serial number (
Collector S/N) you recorded for the Log Collector.
Enter the IP address or FQDN of the active and passive Panorama HA peers in the
Panorama Server IP
field and
Panorama Server IP 2
field respectively. These fields are required.
Select
Management
and configure one or both of the following field sets for the MGT interface based on the IP protocols of your network.
IPv4—
IP Address,
Netmask, and
Default Gateway
IPv6—
IPv6 Address/Prefix Length
and
Default IPv6 Gateway
(
Optional
) In the Management Interface Services section, select
SNMP
if you will use an SNMP manager to monitor Log Collector statistics.
Using SNMP requires additional steps besides configuring the Log Collector (see
Monitor Panorama and Log Collector Statistics Using SNMP).
Click
OK
and
Commit, set the
Commit Type
to
Panorama, and click
Commit
again. This step is required before you can enable logging disks on the Log Collectors.
Verify that the
Panorama > Managed Collectors
page lists the Log Collector you added. The Connected column displays a check mark to indicate that the Log Collector is connected to Panorama. You might have to wait a few minutes before the page displays the updated connection status.
At this point, the Configuration Status column displays Out of Sync and the Run Time Status column displays disconnected. The status will change to In Sync and connected after you configure a Collector Group later in this procedure.
|
|
Enable connectivity between each Log Collector and the Panorama management server.
This step is required before you can enable logging disks on the Log Collectors.
|
Enter the following commands at the CLI of each Log Collector.
<IPaddress1>
is for the MGT interface of the active Panorama and
<IPaddress2>
is for the MGT interface of the passive Panorama.
>
configure
#
set deviceconfig system panorama-server <IPaddress1> panorama-server-2 <IPaddress2>
#
commit
#
exit
|
|
Enable the logging disks on each Log Collector.
|
Use the web interface of the primary Panorama management server peer to perform these steps:
Select
Panorama > Managed Collectors
and edit the Log Collector.
Select
Disks
and
Add
each disk pair.
Click
OK
and
Commit, set the
Commit Type
to
Panorama, and click
Commit
again.
|
(
Optional
) Configure the
Eth1
and/or
Eth2
interfaces if the Log Collectors will use them for log collection and Collector Group communication.
These interfaces are available only if you configured them for the Panorama management server during initial configuration.
Palo Alto Networks recommends using
Eth1
and/or
Eth2
to reduce the traffic load on the MGT interface and to improve security for management traffic.
|
Use the web interface of the primary Panorama management server peer to perform these steps for each Log Collector:
Select
Panorama > Managed Collectors
and edit the Log Collector.
Configure the network settings of the
Eth1
and/or
Eth2
interfaces. For each interface, select the corresponding tab and configure one or both of the following 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
Click
OK
and
Commit, set the
Commit Type
to
Panorama, and click
Commit
again. This step is required before you can assign the Eth1 and Eth2 interfaces to logging functions.
Select
Panorama > Managed Collectors
and edit the Log Collector.
Select the interfaces (MGT, Eth1, or Eth2) that the Log Collector will use for
Device Log Collection
and
Collector Group Communication
(default is MGT).
Click
OK
to save your changes.
|
|
Add a Firewall as a Managed Device.
|
Use the web interface of the primary Panorama management server peer to perform this task for each firewall that will forward logs to Log Collectors.
|
|
Configure a Collector Group.
If each Collector Group will have one Log Collector, repeat this step for each Collector Group before continuing.
If you will assign all the Log Collectors to one Collector Group, perform this step only once.
|
Use the web interface of the primary Panorama management server peer to
Configure a Collector Group:
Select
Panorama > Collector Groups,
Add
a Collector Group, and enter a
Name
for it.
If you add multiple Log Collectors to a single Collector group,
Enable log redundancy across collectors
as a best practice. For redundancy, each Log Collector in the Collector Group requires the same number of disks.
(
Optional
) Select the
Monitoring
tab and configure the settings if you will use SNMP to monitor Log Collector statistics and traps.
Select the
Device Log Forwarding
tab and, in the Collector Group Members section, assign one or more Log Collectors.
All the Log Collectors for any particular Collector Group must be the same models, such as all M-100 appliances or all M-500 appliances.
In the Log Forwarding Preferences section, assign firewalls according to the number of Log Collectors in this Collector Group:
Single—Assign the firewalls that will forward logs to that Log Collector, as illustrated in
Figure: Single Dedicated Log Collector Per Collector Group.
Multiple—Assign each firewall to both Log Collectors for redundancy. When you configure the preferences, make Log Collector 1 the first priority for half the firewalls and make Log Collector 2 the first priority for the other half, as illustrated in
Figure: Multiple Dedicated Log Collectors Per Collector Group.
Click
OK
and
Commit, set the
Commit Type
to
Panorama, and click
Commit
again.
Click
Commit, set the
Commit Type
to
Collector Group, select the Collector Groups you added, and click
Commit
again.
Select
Panorama > Managed Collectors
to verify that the Log Collector configuration is synchronized with Panorama.
The Configuration Status column should display In Sync and the Run Time Status column should display connected.
|
|
Configure log forwarding.
|
Use the web interface of the primary Panorama management server peer to:
Configure Log Forwarding to Panorama.
Verify Log Forwarding to Panorama.
(
Optional
)
Configure Log Forwarding from Panorama to External Destinations.
|
