Fortinet black logo

Administration Guide

SNMP

SNMP

SNMP enables FortiIsolator administrators to monitor hardware on client’s network.

An admin user can configure the hardware, such as the FortiIsolator SNMP agent, to report system information and send traps (alarms or event messages) to SNMP managers. SNMP traps alert admin users to events that happen, such as the session limit is about to reach.

The FortiIsolator SNMP implementation is read-only. SNMP managers have read-only access to FortiIsolator system information through queries, and can receive trap messages from the FortiIsolator unit.

SNMP configuration

Before a remote SNMP manager can connect to the FortiIsolator SNMP agent, configurations must be made on FortiIsolator interface and community string in order to accept SNMP connections.

To configure a FortiIsolator interface and Community string to accept SNMP connections in the GUI:
  1. Go to System > SNMP.
  2. Under interface dropdown list, select an interface.
  3. In the Community box, enter SNMP community string.
  4. Click OK.

To configure a FortiIsolator interface to accept SNMP connections in the CLI:

set snmpd-interface <internal|external|mgmt|ha>

set snmpd-interface mgmt

To configure a Community string to accept SNMP connections in the CLI:

set snmpd-community <fis_community>

set snmpd-community fis_public

File: /var/log/syslog/snmpd.conf

rocommunity fis_public default -V systemonly

To configure SNMP traps:
  • For SNMP v1 and v2:

    set session-threshold [1-100]

    set session-threshold 5

    set trap-host-ip <host-ip>

    set trap-host-ip 192.168.1.100

    set trap-host-community <host-community>

    set trap-host-community public

    File: /etc/snmp/ snmptrapd.conf

    authCommunity log,execute,net public

  • For SNMP v3:

    set session-threshold [1-100]

    set session-threshold 5

    set trap-host-ip <host-ip>

    set trap-host-ip 192.168.1.100

    set trap-host-community <host-community>

    set trap-host-community fis_public

    File: /etc/snmp/ snmptrapd.conf

    authCommunity log,execute,net fis_public

    set snmpd-v3-user <user name> <disabled | enabled>

    set snmpd-v3-user fis_user 1

    set snmpd-auth-method-pwd <1|2 MD5|SHA> <auth password>

    set snmpd-auth-method-pwd 1 password

    set snmpd-trap-enable <disabled | enabled>

    set snmpd-trap-enable 1

    set snmpd-trap-event <event num> <0|1 disabled | enabled>

    0: CHECK_SESSION_THRESHOLD

    1: MGMT_IP_OFF_DAYS

    set snmpd-trap-event 1 1

To configure SNMP server, include these settings in SNMP .conf files:
  • For SNMP v1 and v2:

    > cat /etc/snmp/snmp.conf

    mibs +ALL

    > cat /etc/snmp/snmpd.conf

    rocommunity fis_public default -V systemonly

    > cat /var/log/syslog/snmptrapd.conf

    authCommunity log,execute,net public

  • For SNMP v3:

    > cat /etc/snmp/snmp.conf

    mibs +ALL

    > cat /etc/snmp/snmpd.conf

    rocommunity fis_public default -V systemonly

    > cat /var/log/syslog/snmptrapd.conf

    authCommunity log,execute,net fis_public

    authUser log,execute,net fis_user auth

Example results from SNMP traps:
  • For SNMP v1 and v2:

    > tail -f /var/log/syslog | grep snmp

    Apr 14 15:07:00 bigdata snmptrapd[32688]: 2021-04-14 15:07:00 <UNKNOWN> [UDP: [FIS_IP]:56623->[SNMP_Server_IP]:162]:#012DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1460730) 4:03:27.30#011SNMPv2-MIB::snmpTrapOID.0 = OID: FORTINET-FORTIISOLATOR-MIB::fisTrapSessOverThreshold#011FORTINET-FORTIISOLATOR-MIB::fisSessUsage = INTEGER: 5

    Apr 14 15:07:00 bigdata snmptrapd[32688]: 2021-04-14 15:07:00 <UNKNOWN> [UDP: [FIS_IP]:56623->[SNMP_Server_IP]:162]:#012DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1460730) 4:03:27.30#011SNMPv2-MIB::snmpTrapOID.0 = OID: FORTINET-FORTIISOLATOR-MIB::fisTrapSessOverThreshold#011FORTINET-FORTIISOLATOR-MIB::fisSessUsage = INTEGER: 5

  • For SNMP v3:

    > sudo snmptrapd -C -c /etc/snmp/snmptrapd.conf -f -Dusm -Lo

    registered debug token usm, 1

    Log handling defined - disabling stderr

    usmUser: created a new user fis_user at 80 00 1F 88 80 92 69 F2 3A F8 B8 E9 62 00 00 00 00

    NET-SNMP version 5.7.3 AgentX subagent connected

    NET-SNMP version 5.7.3

    usm: USM processing begun...

    usm: match on user fis_user

    usm: Verification succeeded.

    usm: USM processing completed.

    2022-08-04 16:28:10 <UNKNOWN> [UDP: [172.30.157.35]:34557->[172.30.157.208]:162]:

    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17079281) 1 day, 23:26:32.81 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.12356.199.2.0.101 SNMPv2-SMI::enterprises.12356.199.6.2.2 = INTEGER: 9

    usm: USM processing begun...

    usm: match on user fis_user

    usm: Verification succeeded.

    usm: USM processing completed.

    2022-08-04 16:29:10 <UNKNOWN> [UDP: [172.30.157.35]:41908->[172.30.157.208]:162]:

    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17085283) 1 day, 23:27:32.83 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.12356.199.2.0.101 SNMPv2-SMI::enterprises.12356.199.6.2.2 = INTEGER: 9

SNMP

SNMP enables FortiIsolator administrators to monitor hardware on client’s network.

An admin user can configure the hardware, such as the FortiIsolator SNMP agent, to report system information and send traps (alarms or event messages) to SNMP managers. SNMP traps alert admin users to events that happen, such as the session limit is about to reach.

The FortiIsolator SNMP implementation is read-only. SNMP managers have read-only access to FortiIsolator system information through queries, and can receive trap messages from the FortiIsolator unit.

SNMP configuration

Before a remote SNMP manager can connect to the FortiIsolator SNMP agent, configurations must be made on FortiIsolator interface and community string in order to accept SNMP connections.

To configure a FortiIsolator interface and Community string to accept SNMP connections in the GUI:
  1. Go to System > SNMP.
  2. Under interface dropdown list, select an interface.
  3. In the Community box, enter SNMP community string.
  4. Click OK.

To configure a FortiIsolator interface to accept SNMP connections in the CLI:

set snmpd-interface <internal|external|mgmt|ha>

set snmpd-interface mgmt

To configure a Community string to accept SNMP connections in the CLI:

set snmpd-community <fis_community>

set snmpd-community fis_public

File: /var/log/syslog/snmpd.conf

rocommunity fis_public default -V systemonly

To configure SNMP traps:
  • For SNMP v1 and v2:

    set session-threshold [1-100]

    set session-threshold 5

    set trap-host-ip <host-ip>

    set trap-host-ip 192.168.1.100

    set trap-host-community <host-community>

    set trap-host-community public

    File: /etc/snmp/ snmptrapd.conf

    authCommunity log,execute,net public

  • For SNMP v3:

    set session-threshold [1-100]

    set session-threshold 5

    set trap-host-ip <host-ip>

    set trap-host-ip 192.168.1.100

    set trap-host-community <host-community>

    set trap-host-community fis_public

    File: /etc/snmp/ snmptrapd.conf

    authCommunity log,execute,net fis_public

    set snmpd-v3-user <user name> <disabled | enabled>

    set snmpd-v3-user fis_user 1

    set snmpd-auth-method-pwd <1|2 MD5|SHA> <auth password>

    set snmpd-auth-method-pwd 1 password

    set snmpd-trap-enable <disabled | enabled>

    set snmpd-trap-enable 1

    set snmpd-trap-event <event num> <0|1 disabled | enabled>

    0: CHECK_SESSION_THRESHOLD

    1: MGMT_IP_OFF_DAYS

    set snmpd-trap-event 1 1

To configure SNMP server, include these settings in SNMP .conf files:
  • For SNMP v1 and v2:

    > cat /etc/snmp/snmp.conf

    mibs +ALL

    > cat /etc/snmp/snmpd.conf

    rocommunity fis_public default -V systemonly

    > cat /var/log/syslog/snmptrapd.conf

    authCommunity log,execute,net public

  • For SNMP v3:

    > cat /etc/snmp/snmp.conf

    mibs +ALL

    > cat /etc/snmp/snmpd.conf

    rocommunity fis_public default -V systemonly

    > cat /var/log/syslog/snmptrapd.conf

    authCommunity log,execute,net fis_public

    authUser log,execute,net fis_user auth

Example results from SNMP traps:
  • For SNMP v1 and v2:

    > tail -f /var/log/syslog | grep snmp

    Apr 14 15:07:00 bigdata snmptrapd[32688]: 2021-04-14 15:07:00 <UNKNOWN> [UDP: [FIS_IP]:56623->[SNMP_Server_IP]:162]:#012DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1460730) 4:03:27.30#011SNMPv2-MIB::snmpTrapOID.0 = OID: FORTINET-FORTIISOLATOR-MIB::fisTrapSessOverThreshold#011FORTINET-FORTIISOLATOR-MIB::fisSessUsage = INTEGER: 5

    Apr 14 15:07:00 bigdata snmptrapd[32688]: 2021-04-14 15:07:00 <UNKNOWN> [UDP: [FIS_IP]:56623->[SNMP_Server_IP]:162]:#012DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1460730) 4:03:27.30#011SNMPv2-MIB::snmpTrapOID.0 = OID: FORTINET-FORTIISOLATOR-MIB::fisTrapSessOverThreshold#011FORTINET-FORTIISOLATOR-MIB::fisSessUsage = INTEGER: 5

  • For SNMP v3:

    > sudo snmptrapd -C -c /etc/snmp/snmptrapd.conf -f -Dusm -Lo

    registered debug token usm, 1

    Log handling defined - disabling stderr

    usmUser: created a new user fis_user at 80 00 1F 88 80 92 69 F2 3A F8 B8 E9 62 00 00 00 00

    NET-SNMP version 5.7.3 AgentX subagent connected

    NET-SNMP version 5.7.3

    usm: USM processing begun...

    usm: match on user fis_user

    usm: Verification succeeded.

    usm: USM processing completed.

    2022-08-04 16:28:10 <UNKNOWN> [UDP: [172.30.157.35]:34557->[172.30.157.208]:162]:

    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17079281) 1 day, 23:26:32.81 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.12356.199.2.0.101 SNMPv2-SMI::enterprises.12356.199.6.2.2 = INTEGER: 9

    usm: USM processing begun...

    usm: match on user fis_user

    usm: Verification succeeded.

    usm: USM processing completed.

    2022-08-04 16:29:10 <UNKNOWN> [UDP: [172.30.157.35]:41908->[172.30.157.208]:162]:

    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17085283) 1 day, 23:27:32.83 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.12356.199.2.0.101 SNMPv2-SMI::enterprises.12356.199.6.2.2 = INTEGER: 9