Chat now with support
Chat with Support

We are currently performing website maintenance, any feature requiring sign-in is temporarily unavailable, if you have an issue requiring immediate assistance please call 800-306-9329

Foglight for Integrations 5.6.3 - User and Reference Guide

Using Foglight for Integrations Reference

SNMP Trap Receiver Workflow

Foglight for Integrations includes default MIBs containing trap definitions that can be used to format Simple Network Management Protocol (SNMP) Traps that Foglight receives as third-party Alarms. By receiving SNMP traps, you are able to capture information regarding the state of many devices and all their related objects.
MIBs containing trap definitions can be loaded into Foglight. These trap definitions can be configured and grouped in order to produce Foglight alarms. An SNMP trap receiver agent is deployed to a server and listens on a specific port. The agent understands which traps are enabled and how to format them into Foglight alarms based on the mentioned configuration. Managed devices are configured to forward traps to that particular server or port that the agent is deployed on. When a trap is received, the SNMP trap receiver agent, listening on that server or port, forwards enabled traps to the Management Server as alarms. These alarms are fed into Foglight as third-party alarms. Traps that are not enabled can be written to a log or sent in to the alarm browser. This is configured in the Agent Properties. For more information, Configuring Agent Properties for the SNMP Trap Agent .
Figure 1. Sample alarm
The source for the alarm is the host that initiated the trap. These third-party alarms have additional alarm properties. The key properties are the Technology Monitor which indicates which agent produced an alarm and the trap variables that were available on the trap.
The sourceId property contains the trap name if a trap group is not defined. When a trap group is defined, the trap group name is used.
An unformatted trap is a trap that is not defined in Foglight. A trap is defined when the Trap Definition is loaded into Foglight by loading its MIB file. If the trap definition is defined in Foglight, it is no longer considered unformatted. Agent properties display one of the following, when traps are sent in Foglight without a trap definition.
•
Undefined_Trap_Creates_Alarm
•
Undefined_Trap_Alarm_Duration
•
Undefined_Trap_Severity
To format, select the Configuration dashboard from the navigation panel, under Dashboards > Integration > SNMP Trap Administration, and click the Format link. For more information about formatting traps, see Configuring Alarms from SNMP Trap Definitions .
Any variables that the MIB does not recognize is passed in on the alarm with the property name of Unresolved_Trap_Variable. Trap variables that the MIB recognizes are preceded with Variable_ followed by the variable name. For example, Variable_ifAdminStatus.
The technology monitor contains the namespace and the agent name used when defining the agent.
For more information, see Understanding the XML Data and Loading MIB Definitions .

External Acknowledgement and Clearing of Alarms Workflow

Foglight for Integrations includes the ability to receive external XML data that can be used to acknowledge or clear alarms existing in Foglight. External systems can format an XML document and feed the ID of an alarm into Foglight to perform this function.

Configuring Foglight for Integrations

Working in the Alarm Properties Dashboard
To view the alarm properties:
•
On the navigation panel under Dashboards, click Integration > Property Administration > Alarm Properties.
The Alarm Properties view displays the Supplied Properties view and the Added Properties view.
Figure 2. Alarm Properties view
To add an alarm property:
1
On the navigation panel, under Dashboards, click Integration > Property Administration > Alarm Properties.
2
In the upper left corner of the view, click .
The Add Property dialog box appears.
3
In the Name box, type a unique name for the property.
4
In the Type list, click one of the following:
•
String — This value can include numeric characters, alphanumeric characters, and symbols
•
Boolean — True or False
•
Integer — A whole number between the values of -2147483648 and 2147483647
•
Long — A whole number with a range larger than Integer
•
Float — A 32-bit floating point number
•
Double — A 64-bit floating point number
Optional — select the IS List check box if you want a property to allow multiple values. Clear the check box if you want to allow only one value.
5
Click Save.
The property is listed in the Added Properties view.

Working in the Alarm Properties Dashboard

To view the alarm properties:
•
On the navigation panel under Dashboards, click Integration > Property Administration > Alarm Properties.
The Alarm Properties view displays the Supplied Properties view and the Added Properties view.
Figure 2. Alarm Properties view
To add an alarm property:
1
On the navigation panel, under Dashboards, click Integration > Property Administration > Alarm Properties.
2
In the upper left corner of the view, click .
The Add Property dialog box appears.
3
In the Name box, type a unique name for the property.
4
In the Type list, click one of the following:
•
String — This value can include numeric characters, alphanumeric characters, and symbols
•
Boolean — True or False
•
Integer — A whole number between the values of -2147483648 and 2147483647
•
Long — A whole number with a range larger than Integer
•
Float — A 32-bit floating point number
•
Double — A 64-bit floating point number
Optional — select the IS List check box if you want a property to allow multiple values. Clear the check box if you want to allow only one value.
5
Click Save.
The property is listed in the Added Properties view.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating