Trap MIB files
The Trap MIB Files view allows you to enter a configuration to interpret SNMP trap MIB information sent from a device and associate it with events and alarms in FortiNAC.
Requirements
- FortiNAC can only receive traps through SNMPv1 and SNMPv2 communications.
- To receive and interpret traps from devices or applications on your network, those devices or applications must be modeled in FortiNAC and have an associated IP address.
- The device or application must have traps configured to be sent to the IP address of the FortiNAC server or Control Server.
- Map events to Alarms. When a trap is received, FortiNAC compares the trap to the information listed in the Trap MIB Files and searches for a match. If a match is found, an event is generated. If corresponding alarms have been mapped to the event, alarms are also triggered.
- Multiple traps can be added to a single Trap MIB.
|
It is recommended that you generate and capture a trap from the sending device to make sure that you are entering the correct information when configuring the Trap MIB files. |
Settings
|
|
IP address OID, MAC address OID and user ID OID are not all required. Any one OID can be used to identify the host or user that triggered the trap. |
|
Field |
Definition |
|
MIB File Name |
Name of the MIB file. FortiNAC creates the file when the Custom Trap data is entered. Any MIB file can have multiple custom traps. |
|
Trap OID |
The Trap OID compiled by FortiNAC based on the data entered in the Custom Trap section. More than one Custom Trap can be associated with a single Trap MIB file. |
|
Label |
Label used to identify the trap in the event and alarm configuration. |
|
Specific Type |
This a number that is specific to the sending device. For example, if you are looking for a trap from a Cisco device, you would enter a number that corresponds to Cisco specific traps. |
|
Enterprise OID |
OID associated with the enterprise or manufacturer of the device sending the trap. For example, if FortiNAC were watching for traps from a Cisco device the enterprise OID would be 1.3.6.1.4.1.9. |
|
IP address OID |
OID associated with the trap varbinds that contain the IP address of the host that is triggering the trap. |
|
MAC address OID |
OID associated with the trap varbinds that contain the Physical Address of the host that is triggering the trap. |
|
User ID OID |
OID associated with the trap varbinds that contain the user ID of the user logged onto the host that is triggering the trap. |
|
Alarm Cause |
Textual description of the probable cause of the alarm. |
|
Event Format (Java |
Textual description of the event which includes a variable for the varbind information to be displayed from the trap. For example, if you have entered "Event caused by {4}." Whatever data is contained in the fifth varbind in the trap, is included in the message. The number 4 represents the fifth varbind because the count begins with 0. |
|
Buttons |
|
|
Export |
Exports the data displayed to a file in the default downloads location. File types include CSV, Excel, PDF, or RTF. See Export data. |
|
Add MIB |
Opens the Add MIB dialog and allows you to add both the MIB and the associated custom trap. |
|
Add Custom Trap |
Select a MIB in the Trap MIBs list and use this option to add another custom trap to the MIB. Opens the Add MIB dialog with the name of the selected MIB completed and blank custom trap fields. |
|
Modify |
If the MIB is selected, allows you to modify the name. If the custom trap is selected, allows you to modify the trap information. |
Configure MIB files and custom traps
- Click System > Settings.
- Expand the System Communication folder.
- Select Trap MIB Files from the tree.
- Click Add MIB or select a MIB and click Add Custom Trap.
- Enter the trap information using the settings shown in the table.
-
Click OK to save.