SNMP¶
Fudo Enterprise’s status can be monitored over SNMPv3 protocol.
Configuring SNMP¶
- From the left menu, select > .
- Go to the General tab.
- In the SNMP section, enter the username and password for SNMP authentication.
- From the Encryption method drop-down list, select the algorithm used to encrypt SNMP communication (AES or DES).
- From the Authentication method drop-down list, select either SHA or MD5.
- Select the SNMPv3 option.
- From the Source address drop-down list, select the IP address that will be used for communication with other systems via SNMP.
- Enter the port.
- Click .
Note
When listening on Any, SNMP will follow the routing from the default routing table 0. When listening on specific IP, SNMP will follow the routing configured on the interface where the IP address is configured.
Configuring SNMPv3 TRAP¶
On Policies violation, Fudo is able to send a SNMPv3 TRAP, fudoPolicyViolationNotification with information containing during which session which user violated which policy. For more details check Fudo’s MIB definition in the following section.
To configure SNMP TRAPs, the administrator has to configure the service in the System settings and enable it for a particular policy.
To configure the policy for sending SNMPv3 TRAP notifications about suspicious sessions, follow below procedure:
- From the left menu, select > .
- Go to the General tab.
- In the SNMP section, enter the username and password for SNMP authentication.
- From the Encryption method drop-down list, select the algorithm used to encrypt SNMP communication (AES or DES).
- From the Authentication method drop-down list, select either SHA or MD5.
- Select the SNMPv3 Trap option.
- In the Address field, select the IP address that will be used to communicate with other systems via SNMP.
- Enter the port.
- Click .
As Fudo Enterprise uses SNMPv3 for sending TRAPs, the manager software (such as snmptrapd from Net-SNMP) has to know the user’s name and password.
Note
The fudoPolicyViolationNotification TRAP contains Fudo object identifiers: sessionId, userId and policyId. As all identifiers in Fudo Enterprise are 64-bit integers and SNMP doesn’t support 64-bit integers natively, those ids are encoded as big-endian 8-byte arrays.
SNMP MIBs¶
Fudo Enterprise supports following MIBs:
- MIB-II (RFC 1213)
- HOST-RESOURCES-MIB (RFC 2790) - partly supported
- UCD-SNMP-MIB.
Getting SNMP readings using snmpwalk¶
Note
Getting SNMP readings requires installing Net-SNMP 5.7.3.
Fetching all SNMP information
snmpwalk -v3 -u "${SNMP_USER}" -a SHA -A "${SNMP_PASSWORD}" -x AES -X "${SNMP_PASSWORD}" -l authPriv "${FUDO_IP}" .1
Fetching specific SNMP information
snmpwalk -v3 -u "${SNMP_USER}" -a SHA -A "${SNMP_PASSWORD}" -x AES -X "${SNMP_PASSWORD}" -l authPriv "${FUDO_IP}" .1.3.6.1.4.1.24410
| Data specifier | Description |
|---|---|
| .1.3.6.1.4.1.24410.1.1.1 | Disk status (ZFS status) |
| .1.3.6.1.4.1.24410.1.1.2 | Power supply status Note This feature is not supported on all Fudo Enterprise units. Contact technical support for more information. |
| .1.3.6.1.4.1.24410.1.1.3 | CPU temperatures |
| .1.3.6.1.4.1.24410.1.1.4 | S.M.A.R.T status |
Fudo Enterprise Specific SNMP Extensions¶
Overview
Extensions enable monitoring the number of active sessions, ZFS status, PSU status (if available), CPU temperature on all cores, S.M.A.R.T status such as temperature, health or reallocated sectors.
MIB specification file
MIB specification files (Fudo Security Common MIB and Fudo Security PAM MIB) are available for downloading at the > in the Maintenance and supervision section.
Note
In Fudo Enterprise 5.5.8, the MIB definition has been updated. The FUDO-SECURITY-COMMON-MIB.txt file has been modified accordingly, and smartHealth now supports only the following states: ok (1) and failed (2).
Related topics: