Configuring System Settings

Configuring an SNMP v1 and v2c community

An SNMP community is a grouping of equipment for SNMP-based network administration purposes. You can add up to three SNMP communities so that SNMP managers can connect to the FortiMail unit to view system information and receive SNMP traps. You can configure each community differently for SNMP traps and to monitor different events. You can add the IP addresses of up to eight SNMP managers to each community.

To configure an SNMP community

  1. Go to System > Configuration > SNMP.
  2. Under Community, click New to add a community or select a community and click Edit.

The SNMP Community page appears.

  1. Configure the following:
GUI item Description
Name Enter a name to identify the SNMP community. If you are editing an existing community, you cannot change the name.

You can add up to 16 communities.

Enable Enable to send traps to and allow queries from the community’s SNMP managers.
GUI item Description
Community Hosts Lists SNMP managers that can use the settings in this SNMP community to monitor the FortiMail unit. Click Create to create a new entry.

You can add up to 16 hosts.

IP Address Enter the IP address of an SNMP manager. By default, the IP address is 0.0.0.0, so that any SNMP manager can use this SNMP community.
Delete

(button)

Click to remove this SNMP manager.
Create

(button)

Click to add a new default entry to the Hosts list that you can edit as needed.
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 FortiMail unit. Mark the Enable check box to activate queries for each SNMP version.
Traps Enter the Local Port and Remote Port numbers (162 local, 162 remote by default) that the FortiMail unit uses to send SNMP v1 and SNMP v2c traps to the SNMP managers in this community. Enable traps for each SNMP version that the SNMP managers use.
SNMP Event Enable each SNMP event for which the FortiMail unit should send traps to the SNMP managers in this community.

Note: Since FortiMail checks its status in a scheduled interval, not all the events will trigger traps. For example, FortiMail checks its hardware status every 60 seconds. This means that if the power is off for a few seconds but is back on before the next status check, no system event trap will be sent.

Configuring an SNMP v3 user

SNMP v3 adds more security by using authentication and privacy encryption. You can specify an SNMP v3 user on FortiMail so that SNMP managers can connect to the FortiMail unit to view system information and receive SNMP traps.

To configure an SNMP v3 user

  1. Go to System > Configuration > SNMP.
  2. Under Users, click New to add a user or select a user and click Edit.

The SNMPv3 User page appears.

You can add up to 16 users.

  1. Configure the following:
GUI item Description
User name Enter a name to identify the SNMP user. If you are editing an existing user, you cannot change the name.
Enable Enable to send traps to and allow queries from the user’s SNMP managers.
GUI item Description
Security level Choose one of the three security levels:

•      No authentication, no privacy: This option is similar to SNMP v1 and v2.

•      Authentication, no privacy: This option enables authentication only. The SNMP manager needs to supply a password that matches the password you specify on FortiMail. You must also specify the authentication protocol (either SHA1 or MD5).

•      Authentication, privacy: This option enables both authentication and encryption. You must specify the protocols and passwords. Both the protocols and passwords on the SNMP manager and FortiMail must match.

Authenticatio n Protocol For Security level, if you select either Authentication option, you must specify the authentication protocol and password. Both the authentication protocol and password on the SNMP manager and FortiMail must match.
Privacy protocol For Security level, if you select Privacy, you must specify the encryption protocol and password. Both the encryption protocol and password on the SNMP manager and FortiMail must match.
Notification

Hosts

Lists the SNMP managers that FortiMail will send traps to. Click Create to create a new entry. You can add up to 16 host.
IP Address Enter the IP address of an SNMP manager. By default, the IP address is 0.0.0.0, so that any SNMP manager can use this SNMP user.
Delete

(button)

Click to remove this SNMP manager.
Create

(button)

Click to add a new default entry to the Hosts list that you can edit as needed.
Queries Enter the Port number (161 by default) that the SNMP managers use for SNMP v3 queries to receive configuration information from the FortiMail unit. Select the Enable check box to activate queries.
Traps Enter the Local Port and Remote Port numbers (162 local, 162 remote by default) that the FortiMail unit uses to send SNMP v3 traps to the SNMP managers. Select the Enable check box to activate traps.
SNMP Event Enable each SNMP event for which the FortiMail unit should send traps to the SNMP managers.

Note: Since FortiMail checks its status in a scheduled interval, not all the events will trigger traps. For example, FortiMail checks its hardware status every 60 seconds. This means that if the power is off for a few seconds but is back on before the next status check, no system event trap will be sent.

FortiMail MIBs

The FortiMail SNMP agent supports Fortinet proprietary MIBs as well as standard RFC 1213 and RFC 2665 MIBs. RFC support includes support for the parts of RFC 2665 (Ethernet-like MIB) and the parts of RFC 1213 (MIB II) that apply to FortiMail unit configuration.

The FortiMail MIBs are listed in Table 22. You can obtain these MIB files from Fortinet technical support. To communicate with the SNMP agent, you must compile these MIBs into your SNMP manager.

Your SNMP manager may already include standard and private MIBs in a compiled database that is ready to use. You must add the Fortinet proprietary MIB to this database. If the standard MIBs used by the Fortinet SNMP agent are already compiled into your SNMP manager you do not have to compile them again.

Table 22:FortiMail MIBs

MIB file name Description
fortimail.mib Displays the proprietary Fortinet MIB includes detailed FortiMail system configuration information. Your SNMP manager requires this information to monitor FortiMail configuration settings. For more information, see “MIB fields” on page 274.
fortimail.trap.mib Displays the proprietary Fortinet trap MIB includes FortiMail trap information. Your SNMP manager requires this information to receive traps from the FortiMail SNMP agent. For more information, see “FortiMail traps” on page 273.

FortiMail traps

The FortiMail unit’s SNMP agent can send traps to SNMP managers that you have added to SNMP communities. To receive traps, you must load and compile the FortMail trap MIB into the SNMP manager.

All traps sent include the trap message as well as the FortiMail unit serial number and host name.

Trap Description
fmlTrapCpuHighThreshold Trap sent if CPU usage becomes too high.
fmlTrapMemLowThreshold Trap sent if memory usage becomes too high.
fmlTrapLogDiskHighThreshold Trap sent if log disk usage becomes too high.
fmlTrapMailDiskHighThreshold Trap sent if mailbox disk usage becomes too high.
fmlTrapMailDeferredQueueHighThres hold Trap sent if the number of deferred email messages becomes too great.
fmlTrapAvThresholdEvent Trap sent when the number of detected viruses reaches the threshold.
fmlTrapSpamThresholdEvent Trap sent when the number of spam email messages reaches the threshold.
fmlTrapSystemEvent Trap sent when system shuts down, reboots, upgrades, etc.
fmlTrapRAIDEvent Trap sent for RAID operations.
fmlTrapHAEvent Trap sent when an HA event occurs.
Trap Description
fmlTrapArchiveEvent Trap sent when remote archive event occurs.
fmlTrapIpChange Trap sent when the IP address of the specified interface has been changed.

MIB fields

The Fortinet MIB contains fields reporting current FortiMail unit status information. The tables below list the names of the MIB fields and describe the status information available for each. You can view more details about the information available from all Fortinet MIB fields by compiling the MIB file into your SNMP manager and browsing the MIB fields.

Table 23: MIB fields

MIB field Description
fmlSysModel FortiMail model number, such as 400 for the FortiMail-400.
fmlSysSerial FortiMail unit serial number.
fmlSysVersion The firmware version currently running on the FortiMail unit.
fmlSysVersionAv The antivirus definition version installed on the FortiMail unit.
fmlSysOpMode The operation mode (gateway, transparent, or server) of the FortiMail unit.
fmlSysCpuUsage The current CPU usage (%).
fmlSysMemUsage The current memory utilization (%).
fmlSysLogDiskUsage The log disk usage (%).

fmlSysMailDiskUsage The mail disk usage (%).

fmlSysSesCount The current IP session count.
fmlSysEventCode System component events.
fmlRAIDCode RAID system events.
fmlRAIDDevName RAID device name.
fmlHAEventId HA event type ID.
fmlHAUnitIp Unit IP address where the event occurs.
fmlHAEventReason The reason for the HA event.
fmlArchiveServerIp IP address of the remote Archive Server.
fmlArchiveFilename Archive mail file name.

Table 24:System options MIB field

MIB field Description
fmlSysOptIdleTimeout Idle period after which the administrator is automatically logged out off the system.

fmlSysOptAuthTimeout Authentication idle timeout value.

fmlSysOptsLan Web administration language.
fmlSysOptsLcdProt Whether LCD control buttons protection is enabled or disabled.

Table 25:System session MIB fields

MIB field Description
fmlIpSessTable FortiMail IP sessions table.
fmlIpSessEntry Particular IP session information.
fmlIpSessIndex An index value that uniquely identifies an IP session.
fmlIpSessProto The protocol of the connection.

fmlIpSessFromAddr The session source IP address,

fmlIpSessFromPort The session source port number.
fmlIpSessToAddr The session destination IP address.
fmlIpSessToPort The session destination port number.
fmlIpSessExp Time (in seconds) until the session expires.

Table 26: Mail options MIB fields

MIB field Description
fmlMailOptionsDeferQueu e The current number of deferred email messages.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.