Creating or editing an SNMP community
An SNMP community is a grouping of devices for network administration purposes. Within that SNMP community, devices can communicate by sending and receiving traps and other information. One device can belong to multiple communities, such as one administrator terminal monitoring both a firewall SNMP and a printer SNMP community.
Add SNMP communities to your FortiPAM unit so that SNMP managers can view system information and receive SNMP traps. You can add up to three SNMP communities. Each community can have a different configuration for SNMP queries and traps and can be configured to monitor the FortiPAM unit for a different set of events. You can also add the IP addresses of up to sixteen SNMP managers to each community.
Enabling SNMP v1/v2c and selecting Create New in the SNMP v1/v2c pane opens the New SNMP Community page, which provides settings for configuring a new SNMP community. Double-clicking a community from the SNMP v1/v2c table opens the Edit SNMP Community page. Alternatively, select a community from the list and then select Edit to edit the SNMP community.
Configure the following settings in the New SNMP Community page or Edit SNMP Community page and click OK:
|
Community Name |
Enter a name to identify the SNMP community. After you create the SNMP community, you cannot edit the name. |
|||
|
Enabled |
Enable or disable the SNMP community. |
|||
|
Hosts Settings for configuring the hosts of an SNMP community. |
||||
|
Enter the IP address/netmask of the SNMP managers that can use the settings in this SNMP community to monitor the unit. You can also set the IP address to 0.0.0.0 to so that any SNMP manager can use this SNMP community. |
|||
|
Select one of the following: Accept queries and send traps, Accept queries only, or Send traps only. |
|||
|
Removes an SNMP manager from the list within the Hosts section. |
|||
|
Select to add a blank line to the Hosts list. You can add up to 16 SNMP managers to a single community. |
|||
|
Queries Settings for configuring queries for both SNMP v1 and v2c. |
||||
|
v1 Enabled |
Enable or disable SNMP v1 queries. |
|||
|
Enter the port number (161 by default) that the SNMP managers in this community use for SNMP v1 and SNMP v2c queries to receive configuration information from the unit. The SNMP client software and the unit must use the same port for queries. |
|||
|
Enable or disable SNMP v2c queries. |
|||
|
Traps Settings for configuring local and remote ports for both v1 and v2c. |
||||
|
Enable or disable SNMP v1 traps. |
|||
|
Enter the local port numbers (162 by default) that the unit uses to send SNMP v1 or SNMP v2c traps to the SNMP managers in this community. The SNMP client software and the unit must use the same port for traps. |
|||
|
Enter the remote port number (162 by default) that the unit uses to send SNMP traps to the SNMP managers in this community. The SNMP client software and the unit must use the same port for traps. |
|||
|
Enable or disable SNMP v2c traps. |
|||
|
SNMP Events Enable each SNMP event for which the unit should send traps to the SNMP managers in this community. Note: The CPU usage too high trapʼs sensitivity is slightly reduced by spreading values out over 8 polling cycles. This reduction prevents sharp spikes due to CPU intensive short-term events such as changing a policy. |
||||