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.
- 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.
- To enable the SNMP manager to interpret statistics, load the Supported MIBs and, if necessary, compile them.
- 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 Configure the Panorama management server to respond to statistics requests from an SNMP manager. and 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.
- 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 126.96.36.199.4.1.254188.8.131.52.1.1 in PAN-PRODUCT-MIB.my. For details, see Use an SNMP Manager to Explore MIBs and Objects.
- Configure the SNMP manager to monitor the desired OIDs.
- Enable SNMP traffic on the management (MGT) interface of the Panorama management server.
- Selectand edit the Management Interface Settings.PanoramaSetupManagement
- In the Services section, select theSNMPcheck box and clickOK.
- Enable SNMP traffic on the management (MGT) interface of any M-Series appliances in Log Collector mode:
- Selectand select the Log Collector.PanoramaManaged Collectors
- Select theManagementtab, select theSNMPcheck box, and clickOK.
- Configure the Panorama management server to respond to statistics requests from an SNMP manager.
- Selectand, in the Miscellaneous section, clickPanoramaSetupOperationsSNMP Setup.
- Select the SNMPVersionand configure the authentication values as follows. For version details, see SNMP Support.
- V2c—Enter theSNMP 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 stringpublic; 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.Views—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. ClickAddin the first list and enter aNamefor the group of views. For each view in the group, clickAddand configure the viewName,OID, matchingOption(includeorexclude), andMask.Users—ClickAddin the second list, enter a username in the Users column, select theViewgroup 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.
- ClickOKto save the settings.
- Configure the Dedicated Log Collectors (if any) to respond to SNMP requests.For each Collector Group:
- Selectand select the Collector Group.PanoramaCollector Groups
- Select theMonitoringtab, configure the same settings as in Step Configure the Panorama management server to respond to statistics requests from an SNMP manager., and clickOK.
- Commit the changes to Panorama and push the changes to Collector Groups.
- SelectandCommitCommit and PushEdit Selectionsin the Push Scope.
- SelectCollector Groupsyou, select the Collector Groups you edited, and clickOK.
- Commit and Pushyour changes.
- Monitor the Panorama and Log Collector statistics in an SNMP manager.Refer to the documentation of your SNMP manager.