Deploy Panorama with Dedicated Log Collectors
The following figures illustrate Panorama in a distributed log collection deployment. In these examples, the Panorama management server comprises two M-100 or M-500 appliances in Panorama mode that are deployed in an active/passive high availability (HA) configuration. Alternatively, you can use an HA pair of Panorama virtual appliances. The firewalls send logs to Dedicated Log Collectors (M-Series appliances in Log Collector mode). This is the recommended configuration if the firewalls generate over 10,000 logs/second.
If you will assign more than one Log Collector to a Collector Group, see Caveats for a Collector Group with Multiple Log Collectors to understand the requirements, risks, and recommended mitigations.
Perform the following steps to deploy Panorama with Dedicated Log Collectors. Skip any steps you have already performed (for example, the initial setup).
- 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:
For each virtual appliance (if any):
- Rack mount the M-Series appliance. Refer to the M-Series Hardware Reference Guide for instructions.
- Perform Initial Configuration of the M-Series Appliance.
- 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 the Panorama management server (virtual appliance or M-Series appliance), you must also Set Up HA on Panorama.
- 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.
- Switch from Panorama mode to Log Collector mode on each
Panorama management server 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
> 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-modeIf the mode change succeeded, the output displays:
- Connect to the M-Series appliance in one of the following ways:
- 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
- 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.
- At the CLI of each Log Collector, enter the following command to display its 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 PanoramaManaged 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 Interfaces, click 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) 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 to save your changes.
- Select CommitCommit to Panorama and Commit your
changes.This step is required before you can enable logging disks on the Log Collectors.
- Verify that the PanoramaManaged 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 (Step 9).
- Enable the logging disks on each Log Collector.Use the web interface of the primary Panorama management server peer to perform these steps:
- Select PanoramaManaged Collectors and edit the Log Collector.
- Select Disks, Add each disk pair, and click OK.
- Select CommitCommit to Panorama and Commit your changes.
- (Recommended) Configure the Ethernet1, Ethernet2, Ethernet3, Ethernet4,
and Ethernet5 interfaces if the Log Collector
will use them for Device Log Collection (receiving
logs from firewalls) and Collector Group Communication.By default, the Log Collector uses the MGT interface for log collection and Collector Group communication. Assigning other interfaces to these functions enables you to reserve the MGT interface for management traffic. In an environment with heavy log traffic, consider using the 10Gbps interfaces (Ethernet4 and Ethernet5) on the M-500 appliance for log collection and Collector Group communication. To load balance the logging traffic across interfaces, you can enable Device Log Collection on multiple interfaces.Use the web interface of the primary Panorama management server peer to perform these steps for each Log Collector:
- Select PanoramaManaged Collectors, edit the Log Collector, and select Interfaces.
- Perform the following steps for each interface:
- Click the name of the interface to edit it.
- Select <interface-name> to enable the interface.
- Complete one or both of the following field sets based on the IP protocols of your network:IPv4—IP Address, Netmask, and Default GatewayIPv6—IPv6 Address/Prefix Length and Default IPv6 Gateway
- Select the Device Management Services that the interface supports:Device Log Collection—You can assign one or more interfaces.Collector Group Communication—You can assign only one interface.
- Click OK to save your changes to the interface.
- Click OK to save your changes to the Log Collector.
- Select CommitCommit to Panorama and Commit your changes to the Panorama configuration.
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.
the 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 PanoramaCollector Groups and Add the Collector Group.
- Enter a Name to identify the Collector Group.
- Add one or more Log Collectors
to the Collector Group Members list.In any single Collector Group, all the Log Collectors must run on the same Panorama model: all M-600 appliances, all M-500 appliances, all M-200 appliances, all M-100 appliances, or all Panorama virtual appliances.
- (Best Practice) Enable log redundancy across collectors if you add multiple Log Collectors to a single Collector group. This option requires each Log Collector to have the same number of logging disks.
- (Optional) Select Monitoring and configure the settings if you will use SNMP to monitor Log Collector statistics and traps.
- Select Device Log Forwarding and
configure the Log Forwarding Preferences list. This list defines
which firewalls forward logs to which Log Collectors. 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 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 Multiple Dedicated Log Collectors Per Collector Group.
- Click OK to save your changes to the Collector Group.
- Select CommitCommit and Push and then Commit and Push your changes to Panorama and to the Collector Groups you added.
- Select PanoramaManaged 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 from firewalls to Panorama.Use the web interface of the primary Panorama management server peer to:
Managed Collectors and Collector Groups
Managed Collectors and Collector Groups Panorama uses Log Collectors to aggregate logs from managed firewalls. When generating reports, Panorama queries the Log Collectors for log ...
Deploy Panorama M-Series Appliances with Local Log Collecto...
Deploy Panorama M-Series Appliances with Local Log Collectors The following figures illustrate Panorama in a centralized log collection deployment. In these examples, the Panorama management ...
Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
Procedure to migrate logs from a decommissioned M-Series appliance in a HA pair to a new M-Series appliance of the same model. ...
Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
Procedure to migrate logs from a decommissioned M-Series appliance in a HA pair to a new M-Series appliance of a different model. ...
Migrate Logs to a New M-Series Appliance in Log Collector M...
Migrate Logs to a New M-Series Appliance in Log Collector Mode If you need to replace an M-600, M-500, M-200 or M-100 appliance in Log ...
Move a Log Collector to a Different Collector Group
Move a Log Collector to a Different Collector Group M-600, M-500, M-200, M-100 and Panorama virtual appliances can have one or more Log Collectors in ...
Manage Collector Groups
Manage Collector Groups A Collector Group is 1 to 16 Log Collectors that operate as a single logical unit for collecting firewall logs. You must ...
Set Up the M-Series Appliance as a Log Collector
Set Up the M-Series Appliance as a Log Collector If you want a dedicated appliance for log collection, configure an M-100, M-200, M-500, M-600 appliance ...
Migrate Log Collectors after Failure/RMA of Non-HA Panorama
Migrate Log Collectors after Failure/RMA of Non-HA Panorama If a system failure occurs on a Panorama management server that is not deployed in a high ...