Set Up The Panorama Virtual Appliance as a Log Collector

How to set up a Panorama virtual appliance on AWS, AWS GovCloud, Microsoft Azure, KVM, Hyper-V, or ESXi as a Dedicated Log Collector.
If you want a dedicated virtual appliance for log collection, configure a Panorama virtual appliance on ESXi, AWS, AWS GovCloud, Azure, Google Cloud Platform, KVM, or Hyper-V in Log Collector mode. To do this, you first perform the initial configuration of the virtual appliance in Panorama mode, which includes licensing, installing software and content updates, and configuring the management (MGT) interface. You then switch the Panorama virtual appliance to Log Collector mode and complete the Log Collector configuration. Additionally, if you want to use dedicated M-Series Appliance Interfaces (
recommended
) instead of the MGT interface for log collection and Collector Group communication, you must first configure the interfaces for the Panorama management server, then configure them for the Log Collector, and then perform a Panorama commit followed by a Collector Group commit.
Perform the following steps to set up a new virtual appliance as a Log Collector or to convert an existing virtual appliance that was previously deployed as a Panorama management server.
Switching the virtual appliance from Panorama mode to Log Collector mode reboots the appliance, deletes the local Log Collector, deletes any existing log data, and deletes all configurations except the management access settings. Switching the mode does not delete licenses, software updates, or content updates.
  1. Set up the Panorama virtual appliance management server that will manage the Log Collector if you have not already done so.
  2. Record the management IP addresses of the Panorama management server.
    If you deployed Panorama in a high availability (HA) configuration, you need the IP address of each HA peer.
    1. Log in to the web interface of the Panorama management server.
    2. Record the
      IP Address
      of the solitary (non-HA) or active (HA) Panorama by selecting
      Panorama
      Setup
      Management
      and checking the Management Interface Settings.
    3. For an HA deployment, record the
      Peer HA IP Address
      of the passive Panorama by selecting
      Panorama
      High Availability
      and checking the Setup section.
  3. Set up the Panorama virtual appliance that will serve as a Dedicated Log Collector.
    If you previously deployed this appliance as a Panorama management server, you can skip this step because the MGT interface is already configured and the licenses and updates are already installed.
    The Panorama virtual appliance in Log Collector mode does not have a web interface for configuration tasks, only a CLI. Therefore, before changing the mode on the Panorama virtual appliance, use the web interface in Panorama mode to:
  4. (
    Panorama on Azure only
    ) Modify the admin password.
    The Dedicated Log Collector supports only the admin Administrator user in order to change in to Log Collector mode. Modify the admin password to allow you to log in using the admin Administrator user.
    1. Select
      Panorama
      Administrators
      and select
      admin
      .
    2. Enter the
      Password
      ,
      Confirm Password
      and click
      OK
      .
    3. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes.
  5. (
    Panorama on AWS and Azure only
    ) Delete all users, except for the admin user.
    1. Select
      Panorama
      Administrators
      .
    2. Select the existing Administrators, except admin, and
      Delete
      .
    3. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes.
  6. Switch from Panorama mode to Log Collector mode.
    1. Switch to Log Collector mode by entering the following command:
      >
      request system system-mode logger
    2. Enter
      Y
      to confirm the mode change. The virtual appliance reboots. If the reboot process terminates your terminal emulation software session, reconnect to the virtual 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.
    3. Log back in to the CLI.
    4. 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
  7. Enable connectivity between the Log Collector and Panorama management server.
    Enter the following commands at the Log Collector CLI, where
    <IPaddress1>
    is for the MGT interface of the solitary (non-HA) or active (HA) Panorama and
    <IPaddress2>
    is for the MGT interface of the passive (HA) Panorama, if applicable.
    >
    configure
    #
    set deviceconfig system panorama-server
    <IPaddress1>
    panorama-server-2
    <IPaddress2>
    #
    commit
    #
    exit
  8. Record the serial number of the Log Collector.
    You need the serial number to add the Log Collector as a managed collector on the Panorama management server.
    1. At the Log Collector CLI, enter the following command to display its serial number.
      >
      show system info | match serial
    2. Record the serial number.
  9. Add the Log Collector as a managed collector to the Panorama management server.
    1. Select
      Panorama
      Managed Collectors
      and
      Add
      a managed collector.
    2. In the
      General
      settings, enter the serial number (
      Collector S/N
      ) you recorded for the Log Collector.
    3. In the
      Panorama Server IP
      field, enter the IP address or FQDN of the solitary (non-HA) or active (HA) Panorama. For HA deployments, enter the IP address or FQDN of the passive Panorama peer in the
      Panorama Server IP 2
      field.
      These IP addresses must specify a Panorama interface that has
      Device Management and Device Log Collection
      services enabled. By default, these services are enabled only on the MGT interface. However, you might have enabled the services on other interfaces when you Set Up the M-Series Appliance that is a Panorama management server.
    4. Select
      Interfaces
      , click
      Management
      , and enter the
      Public IP Address
      of the Dedicated Log Collector.
    5. Click
      OK
      twice to save your changes to the Log Collector.
    6. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes to the Panorama configuration.
    7. Verify that
      Panorama
      Managed Collectors
      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.
  10. Enable the logging disks.
    1. Select
      Panorama
      Managed Collectors
      and edit the Log Collector.
    2. Select
      Disks
      and
      Add
      each disk.
    3. Click
      OK
      to save your changes.
    4. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes to the Panorama configuration.
  11. (
    Recommended
    ) Configure the
    Ethernet1
    ,
    Ethernet2
    ,
    Ethernet3
    ,
    Ethernet4
    , and
    Ethernet5
    interfaces if the Panorama management server and Log Collector will use them for
    Device Log Collection
    (receiving logs from firewalls) and
    Collector Group Communication
    .
    If you previously deployed the Log Collector as a Panorama management server and configured these interfaces, you must reconfigure them because switching to Log Collector mode would have deleted all configurations except the management access settings.
    1. Configure each interface on the Panorama management server (other than the MGT interface) if you haven’t already:
      1. Select
        Panorama
        Setup
        Interfaces
        and click the Interface Name.
      2. Select
        <interface-name>
        to enable the interface.
      3. Complete one or both of the following field sets based on the IP protocols of your network:
        • For ESXi
          • IPv4—
            Public IP Address
            ,
            IP Address
            ,
            Netmask
            , and
            Default Gateway
            IPv6—
            IPv6 Address/Prefix Length
            and
            Default IPv6 Gateway
        • For AWS, Azure, and Google™ Cloud Platform
          • Public IP address
      4. Select the Device Management Services that the interface supports:
        Device Management and Device Log Collection
        —You can assign one or more interfaces.
        Collector Group Communication
        —You can assign only one interface.
        Device Deployment
        (software and content updates)—You can assign only one interface.
      5. Click
        OK
        to save your changes.
    2. Configure each interface on the Log Collector (other than the MGT interface):
      1. Select
        Panorama
        Managed Collectors
        and edit the Log Collector.
      2. Select
        Interfaces
        and click the name of the interface.
      3. Select
        <interface-name>
        to enable the interface.
      4. Complete one or both of the following field sets based on the IP protocols of your network:
        • For ESXi
          • IPv4—
            Public IP Address
            ,
            IP Address
            ,
            Netmask
            , and
            Default Gateway
            IPv6—
            IPv6 Address/Prefix Length
            and
            Default IPv6 Gateway
        • For AWS and Azure
          • Public IP address
      5. 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.
      6. Click
        OK
        to save your changes to the interface.
    3. Click
      OK
      to save your changes to the Log Collector.
    4. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes to the Panorama configuration.
  12. (
    Optional
    ) If your deployment is using custom certificates for authentication between Panorama and managed devices, deploy the custom client device certificate. For more information, see Set Up Authentication Using Custom Certificates.
    1. Select
      Panorama
      Certificate Management
      Certificate Profile
      and choose the certificate profile from the drop-down or click
      New Certificate Profile
      to create one.
    2. Select
      Panorama
      Managed Collectors
      Add
      Communication
      for a Log Collector.
    3. Select the
      Secure Client Communication
      check box.
    4. Select the type of device certificate the Type drop-down.
      • If you are using a local device certificate, select the
        Certificate
        and
        Certificate Profile
        from the respective drop-downs.
      • If you are using SCEP as the device certificate, select the
        SCEP Profile
        and
        Certificate Profile
        from the respective drop-downs.
    5. Click
      OK
      .
  13. (
    Optional
    ) Configure Secure Server Communication Sn a Log Collector. For more information, see Set Up Authentication Using Custom Certificates.
    1. Select
      Panorama
      Managed Collectors
      Add
      Communication
      .
    2. Verify that the
      Custom Certificate Only
      check box is not selected. This allows you to continue managing all devices while migrating to custom certificates.
      When the Custom Certificate Only check box is selected, the Log Collector does not authenticate and cannot receive logs from devices using predefined certificates.
    3. Select the SSL/TLS service profile from the
      SSL/TLS Service Profile
      drop-down. This SSL/TLS service profile applies to all SSL connections between the Log Collector and devices sending it logs.
    4. Select the certificate profile from the
      Certificate Profile
      drop-down.
    5. Select
      Authorize Client Based on Serial Number
      to have the server check clients against the serial numbers of managed devices. The client certificate must have the special keyword $UDID set as the CN to authorize based on serial numbers.
    6. In
      Disconnect Wait Time (min)
      , enter the number of minutes Panorama should wait before breaking and reestablishing the connection with its managed devices. This field is blank by default and the range is 0 to 44,640 minutes.
      The disconnect wait time does not begin counting down until you commit the new configuration.
    7. (
      Optional
      ) Configure an authorization list.
      1. Click
        Add
        under Authorization List.
      2. Select the
        Subject
        or
        Subject Alt Name
        as the Identifier type.
      3. Enter an identifier of the selected type.
      4. Click
        OK
        .
      5. Select
        Check Authorization List
        to enforce the authorization list.
    8. Click
      OK
      .
    9. Select
      Commit
      Commit to Panorama
      .
  14. Assign the Log Collector to a Collector Group.
    1. Configure a Collector Group. You must perform a Panorama commit and then a Collector Group commit to synchronize the Log Collector configuration with Panorama and to put the Eth1, Eth2, Eth3, Eth4, and Eth5 interfaces (if you configured them) in an operational state on the Log Collector.
      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.
      As a 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.
    2. 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.
    3. Access the Log Collector CLI and enter the following command to verify that its interfaces are operational:
      >
      show interface all
      The output displays the
      state
      as
      up
      for each interface that is operational.
    4. If the Collector Group has multiple Log Collectors, Troubleshoot Connectivity to Network Resources to verify they can communicate with each other by performing a Ping connectivity test for each interface that the Log Collectors use. For the
      source
      IP address, specify the interface of one of the Log Collectors. For the
      host
      IP address, specify the matching interface of another Log Collector in the same Collector Group.
  15. Next steps...
    To enable the Log Collector to receive firewall logs:

Related Documentation