End-of-Life (EoL)

Monitor Panorama and Log Collector Statistics Using SNMP

You can configure an SNMP manager to request information from a Panorama management server and configure Panorama to respond. For example, the SNMP manager can request the high availability (HA) mode, Panorama state, and Panorama version. If the Panorama management server has a local Log Collector, then Panorama can also provide logging statistics: average logs per second, storage duration, retention periods, log disk usage, log forwarding status from individual firewalls to Panorama and external servers, and the status of firewall-to-Log Collector connections. Panorama doesn’t synchronize SNMP configurations between HA peers; you must enable SNMP requests and responses on each peer.
You can also configure a Dedicated Log Collector to respond to requests for the same logging statistics as the Panorama management server. This information is useful when evaluating whether you need to expand log storage capacity.
You can’t configure an SNMP manager to control Panorama or Log Collectors (using SET messages); an SNMP manager can only collect statistics (using GET messages).
For details on how Panorama implements SNMP, see SNMP Support.
  1. Configure the SNMP Manager to get statistics from Panorama and the Log Collectors.
    The following steps are an overview of the tasks you perform on the SNMP manager. For the specific steps, refer to the documentation of your SNMP manager.
    1. To enable the SNMP manager to interpret statistics, load the Supported MIBs and, if necessary, compile them.
    2. For each Panorama appliance that the SNMP manager will monitor, define its connection settings (IP address and port) and authentication settings (SNMPv2c community string or SNMPv3 username and password). All Panorama appliances use port 161.
      The SNMP manager can use the same or different connection and authentication settings for multiple Panorama management servers and Log Collectors. The settings must match those you define when you configure SNMP on Panorama (see Step Configure the Panorama management server to respond to statistics requests from an SNMP manager. and Step Configure the Dedicated Log Collectors (if any) to respond to SNMP requests.). For example, if you use SNMPv2c, the community string you define when configuring Panorama must match the community string you define in the SNMP manager for Panorama.
    3. Determine the object identifiers (OIDs) of the statistics you will monitor. For example, to monitor the logging rate, a MIB browser shows that this statistic corresponds to OID in PAN-PRODUCT-MIB.my. For details, see Use an SNMP Manager to Explore MIBs and Objects.
    4. Configure the SNMP manager to monitor the desired OIDs.
  2. Enable SNMP traffic on the management (MGT) interface of the Panorama management server.
    1. Select
      and edit the Management Interface Settings.
    2. In the Services section, select the
      check box and click
  3. Enable SNMP traffic on the management (MGT) interface of any M-Series appliances in Log Collector mode:
    1. Select
      Managed Collectors
      and select the Log Collector.
    2. Select the
      tab, select the
      check box, and click
  4. Configure the Panorama management server to respond to statistics requests from an SNMP manager.
    1. Select
      and, in the Miscellaneous section, click
      SNMP Setup
    2. Select the SNMP
      and configure the authentication values as follows. For version details, see SNMP Support.
      • V2c
        —Enter the
        SNMP Community String
        , which identifies a community of SNMP managers and monitored devices (Panorama, in this case), and serves as a password to authenticate the community members to each other.
        Don’t use the default community string
        ; it is well known and therefore not secure.
      • V3
        —Create at least one SNMP view group and one user. User accounts and views provide authentication, privacy, and access control when SNMP managers get statistics.
        —Each view is a paired OID and bitwise mask: the OID specifies a MIB, and the mask (in hexadecimal format) specifies which objects are accessible inside (include matching) or outside (exclude matching) that MIB. Click
        in the first list and enter a
        for the group of views. For each view in the group, click
        and configure the view
        , matching
        ), and
        in the second list, enter a username in the Users column, select the
        group from the drop-down, enter the authentication password (
        Auth Password
        ) used to authenticate to the SNMP manager, and enter the privacy password (
        Priv Password
        ) used to encrypt SNMP messages to the SNMP manager.
    3. Click
      to save the settings.
  5. Configure the Dedicated Log Collectors (if any) to respond to SNMP requests.
    For each Collector Group:
    1. Select
      Collector Groups
      and select the Collector Group.
    2. Select the
      tab, configure the same settings as in Step 4, and click
  6. Commit the changes to Panorama and push the changes to Collector Groups.
    1. Select
      Commit and Push
      Edit Selections
      in the Push Scope.
    2. Select
      Collector Groups
      you, select the Collector Groups you edited, and click
    3. Commit and Push
      your changes.
  7. Monitor the Panorama and Log Collector statistics in an SNMP manager.
    Refer to the documentation of your SNMP manager.

Recommended For You