Log Collector Configuration

Managed Collectors
to manage Log Collectors. When you
a new Log Collector as a managed collector, the settings you configure vary based on the location of the Log Collector and whether you deployed Panorama in a high availability (HA) configuration:
  • Dedicated Log Collector
    —When you add the Log Collector, initially the
    tab doesn’t display. You must enter the serial number (
    Collector S/N
    ) of the Log Collector, click
    , and then edit the Log Collector to display the interface settings.
  • Default Log Collector that is local to the solitary (non-HA) or active (HA) Panorama management server
    —After you enter the serial number (
    Collector S/N
    ) of the Panorama management server, the Collector dialog displays only the
    settings, and a subset of the
    settings. The Log Collector derives its values for all other settings from the configuration of the Panorama management server.
  • (
    HA only
    Default Log Collector that is local to the passive Panorama management server
    —Panorama treats this Log Collector as remote so you must configure it as you would configure a Dedicated Log Collector.
    The complete procedure to configure a Log Collector requires additional tasks.
What are you looking for?
Identify the Log Collector and define its connections to the Panorama management server and to external services.
Configure access to the Log Collector CLI.
Configure the interfaces that the Dedicated Log Collector uses for management traffic, Collector Group communication, and log collection.
Configure the RAID disks that store logs collected from firewalls.
Configure the Log Collector to receive user mapping information from User-ID agents.
Configure the Log Collector to authenticate with Windows User-ID Agents.
Configure security settings for communication with Panorama, other Log Collectors, and firewalls.

Recommended For You