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-Series or Panorama virtual appliances in Panorama mode that are deployed in an active/passive high availability (HA) configuration. The firewalls send logs to Dedicated Log Collectors (M-Series or Panorama virtual appliances in Log Collector mode). This is the recommended configuration if the firewalls generate over 10,000 logs/second.
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.
- 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 or Panorama virtual appliance deletes any existing log data and deletes all configurations except the management access settings. After the switch, the M-Series or Panorama virtual appliance retains CLI access but loses web interface access.
- Connect to Panorama in one of the following ways:
- (M-Series appliances only) 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 Panorama management server 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
- EnterYto confirm the mode change. The Panorama management server reboots. If the reboot process terminates your terminal emulation software session, reconnect to Panorama to see the Panorama login prompt.If you see aCMS Loginprompt, 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:system-mode: logger
- 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.
- Add each Log Collector as a managed collector.
- SelectandPanoramaManaged CollectorsAddthe managed collector.
- In theGeneraltab, 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 thePanorama Server IPfield andPanorama Server IP 2field respectively. These fields are required.
- SelectInterfaces, clickManagement, and configure one or both of the following field sets for the MGT interface based on the IP protocols of your network.If you configure aPublic IP Addressfor the interface, Log Collectors in the Collector Group always use the public IP address for communication within the Collector Group. To ensure Log Collectors in a Collector use the private IP address to communicate, do not configure a public IP address.
- IPv4—IP Address,Netmask, andDefault Gateway
- IPv6—IPv6 Address/Prefix LengthandDefault IPv6 Gateway
- (Optional) SelectSNMPif you will use an SNMP manager to monitor Log Collector statistics.
- ClickOKto save your changes.
- SelectandCommitCommit to PanoramaCommityour changes.This step is required before you can enable logging disks on the Log Collectors.
- Verify that thepage 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.PanoramaManaged CollectorsAt 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:
- Selectand edit the Log Collector.PanoramaManaged Collectors
- SelectDisks,Addeach disk pair, and clickOK.
- SelectandCommitCommit to PanoramaCommityour changes.
- (Recommended) Configure theEthernet1,Ethernet2,Ethernet3,Ethernet4, andEthernet5interfaces if the Log Collector will use them forDevice Log Collection(receiving logs from firewalls) andCollector 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 (Ethernet4andEthernet5) on the M-500 appliance for log collection and Collector Group communication. To load balance the logging traffic across interfaces, you can enableDevice Log Collectionon multiple interfaces.Use the web interface of the primary Panorama management server peer to perform these steps for each Log Collector:
- Select, edit the Log Collector, and selectPanoramaManaged CollectorsInterfaces.
- 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, andDefault GatewayIPv6—IPv6 Address/Prefix LengthandDefault 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.
- ClickOKto save your changes to the interface.
- ClickOKto save your changes to the Log Collector.
- SelectandCommitCommit to PanoramaCommityour changes to the Panorama configuration.
- 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 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:
- SelectandPanoramaCollector GroupsAddthe Collector Group.
- Enter aNameto identify the Collector Group.
- Addone 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, or all Panorama virtual appliances.
- (Best Practice)Enable log redundancy across collectorsif 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) SelectMonitoringand configure the settings if you will use SNMP to monitor Log Collector statistics and traps.
- SelectDevice Log Forwardingand 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:
- 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.
- ClickOKto save your changes to the Collector Group.
- Selectand thenCommitCommit and PushCommit and Pushyour changes to Panorama and to the Collector Groups you added.
- Selectto verify that the Log Collector configuration is synchronized with Panorama.PanoramaManaged CollectorsThe 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:
Recommended For You
Recommended videos not found.