Deploy Panorama Virtual Appliances with Local Log Collectors

You can configure firewalls to send logs to a Log Collector that runs locally on a Panorama virtual appliance in Panorama mode. In a high availability (HA) configuration, each Panorama HA peer can have a local Log Collector. You can assign the local Log Collectors on the HA peers to the same Collector Group or to separate Collector Groups, as illustrated in the following figures. Refer to the Setup Prerequisites for the Panorama Virtual Appliance to review the supported logs per second when deploying the Panorama virtual appliance with local Log Collectors in a VMware virtual infrastructure.

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 local Log Collectors. Skip any steps you have already performed (such as the initial setup).

1. Perform the initial setup of each Panorama virtual appliance.
   1. Install the Panorama Virtual Appliance. You must configure the following resources to ensure the virtual appliance starts in Panorama mode:
      • System disk with exactly 81GB of storage.
      • CPUs and memory that are sufficient for the quantity of logs that Panorama will receive and store.
      • Virtual logging disk with 2–24TB of storage.

      Panorama automatically divides the new disk into 2TB partitions, each of which will function as a separate virtual disk.
   2. Perform Initial Configuration of the Panorama Virtual Appliance.
   3. Register Panorama and Install Licenses.
   4. Install Content and Software Updates for Panorama.
2. Set up the Panorama virtual appliances in an HA configuration.
   1. Set Up HA on Panorama.
   2. Test Panorama HA Failover.
3. Add a Log Collector that is local to the primary Panorama.
   On the primary Panorama:
   1. Record the Panorama serial number.
      1. Access the Panorama web interface.
      2. Select Dashboard and record the Serial # in the General Information section.
   2. Add the Log Collector as a managed collector.
      1. Select PanoramaManaged Collectors and Add a new Log Collector.
      2. In the General settings, enter the serial number (Collector S/N) you recorded for Panorama.
      3. Click OK to save your changes.
      4. Select CommitCommit to Panorama.
         This step is required before you can add the virtual logging disks.
   3. Add the virtual logging disks.
      1. Select PanoramaManaged Collectors and edit the Log Collector by clicking its name.
         The Log Collector name has the same value as the hostname of the primary Panorama.
      2. Select Disks and Add the virtual logging disks.
      3. Click OK to save your changes.
      4. Select CommitCommit to Panorama.
4. Add a Log Collector that is local to the secondary Panorama.
   Panorama treats this Log Collector as remote because it does not run locally on the primary Panorama.
   1. Record the serial number of the secondary Panorama.
      1. Access the web interface of the secondary Panorama.
      2. Select Dashboard and record the Serial # in the General Information section.
   2. Access the web interface of the primary Panorama.
   3. Select PanoramaManaged Collectors and Add the Log Collector.
   4. In the General settings, enter the serial number (Collector S/N) you recorded for the secondary Panorama.
   5. Enter the IP address or FQDN of the primary and secondary Panorama HA peers in the Panorama Server IP field and Panorama Server IP 2 field respectively.
      Both of these fields are required.
   6. Click OK to save your changes to the Log Collector.
   7. Select CommitCommit to Panorama and Commit your changes.
      This step is required before you can add the virtual logging disks.
   8. Edit the Log Collector by clicking its name.
      The Log Collector name has the same value as the hostname of the secondary Panorama.
   9. Select Disks, Add the virtual logging disks, and click OK.
   10. Select CommitCommit to Panorama and Commit your changes.
5. Add a Firewall as a Managed Device.
   Use the primary Panorama to perform this task for each firewall that will forward logs to the Log Collectors.
6. Configure the Collector Group.
   Perform this step once if you will assign both Log Collectors to the same Collector Group. Otherwise, configure a Collector Group for each Log Collector.

   On the primary Panorama:
   1. Select PanoramaCollector Groups and Add a Collector Group.
   2. Add one or both Log Collectors as Collector Group Members.
      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.
   3. (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 virtual logging disks.
      Enabling redundancy doubles the amount of logs and log processing traffic in a Collector Group. If necessary, Expand Log Storage Capacity on the Panorama Virtual Appliance.
   4. 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 the Log Collector that is local to the primary Panorama, as illustrated in Single Log Collector Per Collector Group.
      • Multiple—Assign each firewall to both Log Collectors for redundancy. When you configure the preference list, 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 Log Collectors Per Collector Group.
   5. Click OK to save your changes.
   6. Select CommitCommit and Push and then Commit and Push your changes to Panorama and the Collector Groups you added.
7. Trigger failover on the primary Panorama so that the secondary Panorama becomes active.
   On the primary Panorama:
   1. Select PanoramaHigh Availability.
   2. Click Suspend local Panorama in the Operational Commands section.
8. Configure the connection from the secondary Panorama to the Log Collector that is local to the primary Panorama.
   On the secondary Panorama:
   1. In the Panorama web interface, select PanoramaManaged Collectors and select the Log Collector that is local to the primary Panorama.
   2. Enter the IP address or FQDN of the primary and secondary Panorama HA peers in the Panorama Server IP field and Panorama Server IP 2 field respectively.
      Both of these fields are required.
   3. Click OK to save your changes.
   4. Select CommitCommit and Push and then Commit and Push your changes to Panorama and the Collector Groups.
9. Restore HA functionality on the primary Panorama.
   1. Log in to the Panorama web interface of the primary Panorama.
   2. Select PanoramaHigh Availability.
   3. Make local Panorama functional for high availability.
10. Trigger fail-back on the secondary Panorama so that the primary Panorama becomes active.
    On the secondary Panorama:
    1. Select PanoramaHigh Availability.
    2. Click Suspend local Panorama in the Operational Commands section.
    3. Make local Panorama functional for high availability to restore HA functionality to the secondary Panorama.
    4. In the Dashboard, verify in the High Availability widget that the secondary Panorama is secondary-passive.
    5. Log in to the Panorama web interface of the primary Panorama and in the Dashboard, verify in the High Availability widget that the primary Panorama is primary-active.
11. Configure log forwarding from the firewalls to Panorama.
    On the primary Panorama to:
    1. Configure Log Forwarding to Panorama from firewalls.
    2. Verify Log Forwarding to Panorama.