advertisement
Alerts — Reference
This page provides the following information:
• Common Tasks
– Alert Log Settings
– New Alert View Filter
– New Alert Application Launch Action
– New Alert Email Action
– New Alert Ignore Action
– New Alert Trap Forward Action
– SNMP V3 Trap Configuration
• Alert Logs
– Alert View Filters
◦ All Alerts
◦ All Internal Alerts
◦ Critical Alerts
◦ Info Alerts
◦ Normal Alerts
◦ Unknown Alerts
◦ Warning Alerts
• Alert Actions
– Application Launch
– Ignore
– Trap Forwarding
• Alert Categories
• Manage MIBs
• Manage Traps
Alert Logs
You can view alerts from Alerts Logs . The Alert Logs allow you to view all alerts filtered by the active view filter.
The criteria for matching the alerts in the view filter include:
• Alert severity. See
.
• Alert category or source. See
Category and Sources Association
.
• Alert device or device group source. See
•
Alert date, time, or day of week. See Date and Time Range .
• Alert acknowledged flag. See
.
17
255
Related links
Configuring alert log settings
Setting up email notifications
Predefined Alert View Filters
The following table lists the predefined alert view filters.
Table 186. Predefined Alert View Filters
Field
All Alerts
Critical Alerts
Info Alerts
Normal Alerts
Unknown Alerts
Warning Alerts
Description
Select to view all the alerts.
Select to view all the systems that are critical.
Select to view informational alerts.
Select to view normal alerts.
Select to view alerts that OpenManage Essentials cannot categorize.
Select to view all the warnings.
Select Continuous Updates to enable the user interface to update automatically when new alerts are received.
Alert Logs Fields
Table 187. Alert Logs Fields
Field
Severity
Acknowledged
Time
Device
Details
Category
Source
Description
The alert severity
Whether the alert has been acknowledged or not by the user.
The date and time the alert was generated.
The device which generated the alert.
The message contained in the alert.
The categorization of the alert.
The name of the alert source definition.
Group By Column
To group by in All Alerts , drag the All Alert column that you want to group by and drop it in Drag a column header and drop it here to group by that column .
For example, In All Alerts , if you want to group by severity, select Severity and drag and drop it in the Drag a column header and drop it here to group by that column bar.
The alerts are displayed by severity.
256
Alert Details
Table 188. Alert Details
Field
Severity
Acknowledged
Recommended Resolution
Device
Time
Category
Source
Description
SNMP Enterprise OID
SNMP Generic Trap OID
SNMP Specific Trap OID
Description
The alert severity.
Whether the alert has been acknowledged or not by the user.
Click to view the recommended resolution for the issue that resulted in the alert.
NOTE: The recommended resolution is available only for alerts received from either OMSA installed on the server or the iDRAC of the server. Alerts received from OMSA include the recommended resolution only if the
Enhanced Message Format option is enabled in OMSA.
The device which generated the alert.
The date and time the alert was generated.
The categorization of the alert.
The name of the alert source definition.
The message contained in the alert.
Provides the enterprise OID (SNMP OID prefix) of the management information base (MIB) file that defines the event source that you want to monitor.
Provides the generic trap ID of the SNMP trap that you want to monitor from the desired event source. See the Dell
OpenManage Server Administrator SNMP Reference Guide at dell.com/OpenManageManuals for more information on SNMP traps.
Provides the specific trap ID of the SNMP trap that you want to monitor from the desired event source. See the Dell
OpenManage Server Administrator SNMP Reference Guide at dell.com/OpenManageManuals for more information on SNMP traps.
Alert Log Settings
Configure settings which control the size, messaging, and purge settings of the Alert Logs.
Table 189. Alert Log Settings
Field
Maximum size of Alert Logs
Log a warning when the Alert Log size reaches
When the Alert Logs reach the Maximum size, purge
Description
Determines the maximum number of alerts the alert logs can have before purging occurs.
A warning alert is sent to the application log when this size is reached.
Purges the specified number of alerts when the maximum size is reached.
257
Field
Save Purged Alerts
Purged Alerts Location
Description
If selected, the specified number of alerts are purged and saved in a .csv file.
Specifies the location where the purged alerts are saved as a .csv file.
Alert View Filters
NOTE: You can receive alert notifications from OpenManage Essentials on your Android or iOS device by installing and
setting up the OpenManage Mobile application. For more information, see OpenManage Mobile Settings
and the
Dell
OpenManage Mobile User’s Guide
at dell.com/OpenManageManuals.
Alert Filter Name
In OpenManage Essentials, you use alert filters that are associated with alert actions to implement alerting capabilities. For example:
• You can create alert action associations to trigger actions, such as sending e-mails, when an alert condition is met.
• You can create ignore, exclude, or both associations to ignore SNMP traps and CIM indications when they are received. You use these associations to suppress alert floods.
• You can create alert view filters to customize the Alert Logs view.
For more information about creating alert action associations, see
Use this window to perform the following tasks:
• Create new alert action associations, ignore/exclude filters, and alert view associations.
• View summary information for alert action associations, ignore/exclude associations, and alert view filters.
• Edit, delete, rename, and copy alert action associations, ignore/exclude associations, and alert view filters.
Severity
This page provides a list of alert severity.
Table 190. Severity
Field
Name
Enabled
Severity
All
Unknown
Info
Normal
Warning
Critical
Description
Name of the item (applicable only for ignore action and view filter).
Select to enable the alert action (applicable only for ignore action).
The available alert types.
Select to include all types of alerts.
Select to include unknown alerts.
Select to include informational alerts.
Select to include normal alerts.
Select to include warning alerts.
Select to include critical alerts.
258
Acknowledgement
Table 191. Acknowledgement
Field
Limit alerts based on the acknowledge flag
Match only acknowledged alerts
Match only unacknowledged alerts
Description
Select to configure the alert view filter to display alerts based on whether the alerts have been acknowledged or not. This option is disabled by default.
Select to display acknowledged alerts.
Select to display unacknowledged alerts.
Summary — Alert View Filter
The Summary page is shown on the final page of the Alert View Filter wizard or when clicking the View Summary right-click option in the tree.
Table 192. Alert View Filter
Field
Name
Type
Description
Associated Severity
Associated Alert Categories
Associated Alert Sources
Associated Device Groups
Associated Devices
Associated Date Range
Associated Time Range
Associated Days
Associate Acknowledge
Description
The name of the alert action.
The alert action type — App Launch, Email, Ignore, Trap, and
Forward.
The description of the alert action.
The alert severity criteria used when matching alerts.
The alert category criteria used when matching alerts.
The alert source criteria used when matching alerts.
The alert source device group criteria used when matching alerts.
The alert source device criteria used when matching alerts.
The alert date range criteria used when matching alerts.
The alert time range criteria used when matching alerts.
The alert days criteria used when matching alerts.
If enabled, uses the alert acknowledged flag when matching alerts.
Alert Actions
Alert actions are triggered when an incoming alert matches the specific criteria defined in the alert action. The criteria for matching the alert include:
• Alert severity. See
.
• Alert category or source. See
Category and Sources Association
.
• Alert device or device group source. See
•
Alert date, time, or day of week. See Date and Time Range .
There are four types of alert actions:
• Alert Application Launch Action — Launch a script or batch file when the alert action criteria is matched.
• Alert Email Action — Send an e-mail when the alert action criteria is matched.
• Alert Ignore Action — Ignore the alert when the alert action criteria is matched.
259
• Alert Trap Forward Action — Forward the SNMP Trap to another management console when the alert action criteria is matched.
By default, new alert actions are enabled. If you want to turn off the alert action without deleting it, you can disable it either through the right-click menu or the edit wizard for the alert action.
Several common alert action use cases are pre-installed in the disabled state to illustrate common usage. When using these preinstalled actions, it is recommended to clone the example to a new action specific to your needs. Make sure to enable and test the new action during this process.
Name and Description
Table 193. Name and Description
Field
Name
Description
Enabled
Description
The name of the alert action.
The description of the e-mail action.
Select to activate the alert action.
Severity Association
Table 194. Severity Association
Field
Severity
All
Unknown
Info
Normal
Warning
Critical
Description
The available alert types.
Select to include all types of alerts.
Select to include unknown alerts.
Select to include informational alerts.
Select to include normal alerts.
Select to include warning alerts.
Select to include critical alerts.
Application Launch Configuration
Use this window to configure the application that you want to launch and to test the launch.
NOTE: Alert actions are run when a matching alert is received so the alert application launch action is a script or batch file that does not require user interaction.
Table 195. Application Launch Configuration
Field
Executable Name
Arguments
Description
Specifies the fully qualified path name and file name of the executable file that launches the application program.
Specifies or edits any required or desired command line parameters to be used in launching the application program. You can use the following variable substitutions to specify information in the Arguments field:
• $n = Device
• $ip = Device IP
• $m = Message
• $d = Date
• $t = Time
260
Field
Test Action
Description
• $sev = Severity
• $st = Service Tag
• $r = Recommended Resolution
• $e = Enterprise OID
• $sp = Specific trap ID
• $g = Generic trap ID
• $cn = Alert Category Name
• $sn = Alert Source Name
• $pkn = Package Name
• $at = Asset Tag
• $loc = Device Location
• $mod = Model Name
Executable file : If you have an executable file (for example, createTroubleTicket.exe), to create a trouble ticket with parameters –arg1, -arg2, and so on; configure the alert application launch as follows:
• Executable Name (with the full path): C:\temp
\createTroubleTicket.exe
• Argument: -arg1 –arg2
When the alert action is triggered, it runs the command C:\temp
\createTroubleTicket.exe –arg1 -arg2 to perform the associated application launch alert action.
Batch file : If you have a batch file (for example, createTroubleTicket.bat), to create a trouble ticket with parameters –arg1, -arg2, and so on, configure the alert application launch as follows:
• Executable Name (with the full path): C:\temp
\createTroubleTicket.bat
• Argument: -arg1 –arg2
When the alert action is triggered, it runs the command C:\temp
\createTroubleTicket.bat –arg1 -arg2 to perform the associated application launch alert action.
VB script : When configuring vb script files as an alert action, provide the executable and arguments as follows. For example, if you have a script (createTroubleTicket.vbs), to create a trouble ticket that contains one parameter arg1, configure the application launch as follows:
• Executable Name: cscript.exe or C:\Windows
\System32\cscript.exe (full path)
• Argument: C:\temp\createTroubleTicket.vbs arg1
When the alert action is triggered, it runs the command cscript.exe C:\temp\ createTroubleTicket.vbs arg1 to perform the associated application launch alert action.
NOTE: If an alert action is not working, ensure that you have entered complete command from the command prompt.
See the sample alert action under Application Launch alert action for more information.
Allows you to test the application launch.
261
Field Description
NOTE: Alert actions are run when a matching alert is received; so the alert application launch action is a script or batch file that does not require user interaction.
E-Mail Configuration
You can configure Essentials so that you receive e-mail each time the alert associations for your devices meet specific alert criteria.
For example, you may want to receive an e-mail message for all warning and critical alerts.
Use this window to specify the parameters for configuring the e-mail alert action.
Table 196. E-Mail Configuration
Field
To
From
Subject
Message
Email Settings
Test Action
Description
Specifies a valid e-mail address served by the company's SMTP server of the person who is to receive the e-mail.
Specifies the originating e-mail address.
Specify the e-mail subject using text or the available alert tokens.
Specify the e-mail message using text or the available alert tokens.
Select to provide the SMTP server name or IP address.
Allows you to test the e-mail action.
NOTE: After sending the test e-mail, verify that the email was received successfully and has the expected content.
NOTE: Alert tokens are substituted at the time the alert action occurs. They are not substituted for a test action.
NOTE: Certain paging vendors support alphanumeric paging through e-mail. OpenManage Essentials supports paging through the e-mail option.
Trap Forwarding
Simple Network Management Protocol (SNMP) traps are generated in response to changes in the status of sensors and other monitored parameters on a managed device. To correctly forward these traps, you must configure an SNMP trap destination, defined either by IP address or host name. For information about forwarding SNMPv1 and SNMP v2 traps in both the original format
and OMEssentials format, see Forwarding Alerts Use Case Scenarios
.
For example, you may want to use trap forwarding if you are in a multi-tiered enterprise environment using OpenManage Essentials to create associations and forward traps to the enterprise manager.
If the trap is being processed locally and then forwarded to the destination or it is just forwarded to the destination.
Use this window to specify the parameters for configuring trap forwarding.
Table 197. Trap Forwarding
Field
Destination
Community
Forward Trap in Original Format
Description
Provide the IP address or host name for the system that is hosting the enterprise management application.
Provide the SNMP community to which the destination IP address or host name belongs.
Select this check box to forward the trap in the same format received by OpenManage Essentials.
262
Field
Test Action
Description
Forwards a test trap to the specified destination using the specified community string.
SNMP V3 Configuration
The following table describes the fields displayed in the SNMP V3 Configuration .
Table 198. SNMP V3 Configuration
Field
Agent IP Address
Engine ID
Username
Authentication Protocol
Authentication Password
Encryption Protocol
Encryption Password
Refresh
Add New
Import
Export
Save
Delete
Description
Provide the SNMP agent IP address.
Provide the unique engine ID of the SNMP agent.
Provide the user name required to execute the task on the device.
Select the authentication protocol for the discovery of the devices. The available options are MD5, SHA1, and none. The device must be configured using the same authentication protocol for the discovery to be successful. If the authentication protocol is selected to be none, then the encryption option is also disabled.
Provide the authentication password.
Select the encryption protocol for the discovery of the devices.
The available options are AES, DES, and none. The device must be configured using the same encryption protocol for the discovery to be successful.
Provide the encryption password.
Click to refresh the SNMP V3 Configuration page to display the added SNMP V3 traps.
Click to configure the SNMP V3 traps manually.
Click to import the .csv file containing the SNMP V3 trap credentials.
Click to export the SNMP V3 trap credentials to a .csv file.
Click to save the SNMP V3 traps after importing the credentials from a .csv file or by providing the credentials manually.
Click to delete the selected SNMP V3 traps from the list.
SNMP V3 Configuration Wizard
Table 199. SNMP V3 Configuration Wizard
Field
Agent IP Address
Engine ID
Username
Authentication Protocol
Description
Provide the SNMP agent IP address.
Provide the unique engine ID of the SNMP agent.
Provide the user name required to execute the task on the device.
Select the authentication protocol for the discovery of the devices. The available options are MD5, SHA1, and none. The device must be configured using the same authentication protocol for the discovery to be successful. If the authentication protocol is selected to be none, then the encryption option is also disabled.
263
Field
Authentication Password
Encryption Protocol
Encryption Password
Description
Provide the authentication password.
Select the encryption protocol for the discovery of the devices.
The available options are AES, DES, and none. The device must be configured using the same encryption protocol for the discovery to be successful.
Provide the encryption password.
Category and Sources Association
OpenManage Essentials has many alert categories and sources that are predefined and prepopulated for management agents. Select any of the predefined alert categories or sources to associate it with the alert action or filter. For more information and the complete list of categories and alert sources, see
Device Association
You can select predefined groups (device types), custom groups, specific devices, or a device query. Device association currently only covers predefined groups.
For custom groups, create a custom group using the New Custom Group Wizard . The custom group shows up in the tree.
To use device query, select a query from the list.
Click New to create a new device query to search and assign the devices to the alert action.
Click Edit to change the query logic.
Select groups or devices from the tree, you can use the query option to create a specific criteria for the selection.
Device Query Options
Table 200. Device Query Options
Field
Select a query
New
Edit
All Devices
Clients
HA Clusters
KVM
Microsoft Virtualization Servers
Modular Systems
Network Devices
OOB Unclassified Devices
Power Devices
Printers
RAC
Servers
Storage Devices
Description
Select a query from the drop-down list.
Add a new query.
Edit an existing query.
Select to include all the Devices that is managed in
OpenManage Essentials.
Select to include client devices, such as desktops, portables, and workstations.
Select to include High Availability server clusters.
Select to include keyboard video mouse devices.
Select to include Microsoft Virtualization Servers.
Select to include Modular Systems.
Select to include Network Devices.
Select to include out of band Unclassified Devices like Lifecycle
Controller enabled devices.
Select to include PDUs and UPS.
Select to include Printers.
Select to include devices with Remote Access controllers.
Select to include Dell servers.
Select to include storage devices.
264
Field
Unknown
VMware ESX Servers
Date and Time Range
Table 201. Date and Time Range
Field
Limit Date Range
Limit Time Range
Limit Days
Description
Select to include unknown devices.
Select to include VMware ESX servers.
Description
Specifies a specific date range to match alerts.
Specifies a specific time range to match alerts.
Select to specify the days on which to enable the alert association. If you do not enable this option, the association is applied continuously within the time frame that you specify.
Each of these fields are exclusive of the other, so selecting date
8/1/11- 10/1/11, 1am to 4 AM, Friday, will match alerts on only
Fridays from 1-4 AM only within that date range.
NOTE: It is possible to input a date range and days selection that will never produce a result. For example,
9/1/11 and Monday — since 9/1/11 was a Thursday, it will never match.
If none of these are checked, it means that the alert selection will have no date/time filter.
Alert Action — Duplicate Alert Correlation
Table 202. Duplicate Alert Correlation
Field
Yes. Only duplicate alerts that match this filter will be executed.
Ignore duplicate alerts that are received during the interval (1 second - 24 hours).
No
Description
Enabling this option deletes duplicate alerts (with the same ID and from the same device) received within the specified overabundance of alerts to the console.
interval. Use this option to prevent a device from sending an
Select this option and set the required time interval to ignore duplicate alerts. This option can be used to ignore alerts for maximum of 24 hours.
Select this option if you do not want duplicate alerts to run at increased duration.
Summary — Alert Action Details
View and edit selections.
The alert action details screen is shown on the final page of the alert action wizards or when clicking any alert action in the tree.
The alert action will have a subset of the following properties, depending on alert action type and filter criteria chosen (this probably should be a table):
Table 203. Summary — Alert Action Details
Field
Name
Action Enabled
Description
The name of the alert action.
Specifies if the alert action is enabled or disabled.
265
Field
Type
Description
To
From
Subject
Message
Destination
Community
Executable Name
Arguments
Associated Severity
Associated Alert Categories
Associated Alert Sources
Associated Device Groups
Associated Devices
Associated Date Range
Associated Time Range
Associated Days
Minimum Repeat Time
Description
The alert action type — App Launch, Email, Ignore, and
Trap Forward.
The description of the alert action.
The e-mail addresses to which the e-mail is sent.
The e-mail address from whom the e-mail originates.
The subject of the e-mail which may include alert tokens.
The message of the e-mail which may include alert tokens.
The destination name or IP address used for trap forwarding.
The community string used for trap forwarding.
The name of the executable, script, or batch file to be used by the alert action.
The command line arguments used when invoking the alert action.
The alert severity criteria used when matching alerts.
The alert category criteria used when matching alerts.
The alert source criteria used when matching alerts.
The alert source device group criteria used when matching alerts.
The alert source device criteria used when matching alerts.
The alert date range criteria used when matching alerts.
The alert time range criteria used when matching alerts.
The alert days criteria used when matching alerts.
If enabled, specifies the minimum time in seconds between two of the same alerts from the same device.
Alert Categories
OpenManage Essentials has many alert categories and sources that are predefined and pre populated for management agents.
Alert categories are organizational levels of the Alert Categories tree. Alert sources specify the low level details of each alert. To monitor the alert categories and sources, apply an alert action association to the alert source or to its parent category.
This page provides a list of categories and the alerts sources within that category. Use this page to configure alerts based on categories.
Alert Categories Options
Table 204. Alert Categories Options
Field
Brocade-Switch
Compellent
Advanced Infrastructure Management
Environmental
Description
Select this category to include alerts for Brocade-Switch.
Select this category to include alerts for Compellent storage devices.
Select this category to include alerts for Advanced
Infrastructure Management.
Select this category to include alerts for temperature, fan enclosure, fan speed, thermal, and cooling.
266
Field
EqualLogic Storage
FC-Switch
General Redundancy
HyperV Server iDRAC
Juniper-Switch
Keyboard-Video-Mouse (KVM)
Memory
Network
Other
PDU
Physical Disk
Power
Power Center
Printers
Processor
Removable Flash Media
Security
Storage Enclosure
Storage Peripheral
Storage Software
System Events
Tape
Test Events
Unknown
UPS
Virtual Disk
VMware ESX Server
Edit Trap Definitions
Table 205. Edit Trap Definitions
Field
Trap Name or Enterprise OID
Search
Event Category
Description
Select this category to include alerts for EqualLogic storage.
Select this category to include alerts for Fibre Channel switches.
Select this category to include alerts for General Redundancy.
Select this category to include alerts for HyperV Server.
Select this category to include alerts for iDRAC.
Select this category to include alerts for Juniper switches.
Select this category to include alerts for KVMs.
Select this category to include alerts for memory.
Select this category to include alerts related to Dell Networking switches.
Select this category to include alerts for other devices.
Select this category to include alerts for PDUs.
Select this category to include alerts for physical disks.
Select this category to include alerts for power.
Select this category to include alerts for power center.
Select this category to include alerts for printers.
Select this category to include alerts for processor.
Select this category to include alerts for removable flash media.
Select this category to include alerts for security.
Select this category to include alerts for storage enclosures.
Select this category to include alerts for storage peripherals.
Select this category to include alerts for storage software.
Select this category to include alerts for system events.
Select this category to include alerts for tape drives.
Select this category to include alerts for test events.
Select this category to include unknown alerts related statuses.
Select this category to include alerts for UPS.
Select this category to include alerts for virtual disks.
Select this category to include alerts for VMware ESX servers.
Description
Field to provide the trap name or enterprise OID of the trap you want to edit.
Click to search the OpenManage Essentials database for the trap name or enterprise OID that you provided.
Click to display the event categories defined in the
OpenManage Essentials database. You can select a category to
267
Field Description display all the traps defined for that category in the Edit Trap(s) grid. You can also navigate and select a particular trap from the category.
Edit Traps
Name
Category Name
Severity
Format String
Enterprise OID
Description
Generic Trap ID
Specific Trap ID
Save
Displays the trap name.
Displays the category name of the trap.
Displays the severity of the trap.
Displays the message string that is displayed in the
OpenManage Essentials alert logs.
Displays the enterprise OID (SNMP OID prefix) of the event source that you want to monitor.
Displays the trap description.
Displays the generic trap ID of the SNMP trap that you want to monitor from the required event source.
Displays the specific trap ID of the SNMP trap that you want to monitor from the required event source.
Click to save the changes to the OpenManage Essentials database.
Alert Source
Each Alert Category contains alert sources. Click an alert category to view alert sources. Expand a category to view the list of alert sources, and select an alert source.
Table 206. Alert Source
Field
Name
Type
Catalog
Severity
Format string
Description
The name of the new alert source, for example, myFanAlert.
The protocol information.
Provides the catalog information.
Specifies the severity assigned to the alert that is triggered if the alert source generates the specified SNMP trap.
Provides the message string that appears in the Alert Logs if the alert source generates an alert of sufficient severity to trigger the alert. You can use formatting commands to specify parts of the message string. For SNMP, the valid formatting commands are:
$n = system name
$d = date
$t = time
$s = severity
$e = enterprise object identifier (OID)
$sp = specific trap OID
$g = generic trap OID
$1 - $# = varbind values
268
Field
SNMP Enterprise OID
SNMP Generic Trap OID
SNMP Specific Trap OID
Description
Provides the enterprise OID (SNMP OID prefix) of the management information base (MIB) file that defines the event source that you want to monitor.
Provides the generic trap ID of the SNMP trap that you want to monitor from the desired event source. See the Dell
OpenManage Server Administrator SNMP Reference Guide at dell.com/OpenManageManuals for more information on
SNMP traps.
Provides the specific trap ID of the SNMP trap that you want to monitor from the desired event source. See the Dell
OpenManage Server Administrator SNMP Reference Guide at dell.com/OpenManageManuals for more information on
SNMP traps.
Manage MIBs
Manage MIBs Pane
The Manage MIBs pane consists of:
• Import MIB view — To import the MIB file. See
• Remove MIB
Manage Traps Pane
The Manage Traps pane consists of:
• Custom Trap Definitions
view — To add trap definitions to OpenManage Essentials database. See Adding Traps
.
• Reset Built-in Trap Definitions
view — To reset a pre-defined trap that you edited. See Reverting Traps .
Import MIB
Table 207. Import MIB
Field
Select files for upload
Select the MIB File
Browse
Event Details
Category Name
Description
Displays the MIB files that you have selected for upload.
Displays the path of the file selected for parsing.
Click to navigate to the file location.
Severity
Apply the selected event category to all traps
Apply the selected severity to all traps
Select to display the event category names defined in
OpenManage Essentials and the category name of the parsed
MIB.
Select to display the severity defined in OpenManage Essentials.
Select to change the category name of all the traps.
NOTE: If you do not select the check box, you have to manually select the traps and select the category name from the drop-down list.
Select this check box to change the severity of all the traps.
269
Field Description
NOTE: If you do not select the check box, you have to manually select the traps and select the severity from the drop-down list.
Traps Available for Import
Name
Category Name
Severity
Format String
Enterprise OID
Description
Generic Trap ID
Specific Trap ID
Displays the trap name from the MIB file.
Displays the category name of the trap.
Displays the severity of the trap. You can modify the severity of the trap to:
• Unknown
• Info
• Normal
• Warning
• Critical
•
By Value. See Severity Configuration By Value
.
Displays the trap description.
Displays the enterprise OID (SNMP OID prefix) of the MIB file that defines the event source that you want to monitor.
Displays the description of the trap.
Displays the generic trap ID of the SNMP trap that you want to monitor from the required event source.
Displays the specific trap ID of the SNMP trap that you want to monitor from the required event source.
Click to revert the severity of all the traps to the default values.
Click to import traps to the OpenManage Essentials database.
Reset All
Import Traps
Severity Configuration by Value
The Severity Configuration By Value window enables you to specify the severity of the alert based on the value of one or more variable bindings associated with the trap.
Table 208. Severity Configuration by Value
Field
Trap Variable
Severity
Object ID
Object Value
Add New
Select the Variable
OK
Reset
Description
Displays the trap variable index.
Displays the severity assigned for each object value or object ID.
Displays the numerical value based on the trap variable index.
Displays the string value based on the trap variable index.
Click to add the severity configuration.
Select the trap variable that you want to update.
Click to save the changes.
Click to revert the severity of the trap to the default values.
270
Remove MIB
Table 209. Remove MIB
Field
Imported MIB(s)
Remove MIB
Description
Displays the list of MIBs that are imported in the OpenManage
Essentials database.
Click to remove the imported MIBs from the OpenManage
Essentials database.
Troubleshooting MIB Import
Issue : The MIB Import displays the following error message: Dependent MIB files need to be imported. Please import: RFC1155-SMI to the Mib Repository before continuing to import this Mib .
Cause : An MIB file may be dependent on another MIB file. While parsing a source MIB file, all the files referred by the source MIB file must be present in the reference directory or the MIB repository. The error message is displayed because the referred MIB file is missing from the reference directory.
Resolution : To resolve this issue:
• Ensure that you have administrator privileges in OpenManage Essentials. You must launch OpenManage Essentials at least once before importing the MIB file.
• Retrieve the missing MIB file and add the file to the reference directory. If there are multiple dependencies of the parent MIB on more than one file, import all the required MIB files, and then parse the parent MIB file.
NOTE: The above resolution also applies for an invalid MIB file.
Issue : Unable to parse the MIB file.
Resolution : Check the logs to see if there are any MIB compiler issues. If there are no compiler issues, compile the MIB using a standard MIB compiler and verify whether the MIB is properly defined.
Issue : Unable to import the parsed trap definitions into OpenManage Essentials after parsing the MIB file.
Resolution : See the Readme at C:\Program Files (x86)\Dell\MIBImport for the list of MIB files that cannot be imported into
OpenManage Essentials.
Manage Traps
Custom Trap Definitions
Table 210. Custom Trap Definitions
Field
Add Trap
Category Name
Description
Unknown Traps
Description
Trap Name
Generic ID
To select the event category names defined in OpenManage
Essentials or to provide a new category name.
Click to display the unknown traps received in OpenManage
Essentials.
To provide the trap description.
To provide or edit the trap name.
To provide or edit the generic trap ID of the SNMP trap that you want to monitor from the required event source.
271
Field
Enterprise OID
Specific ID
Format String
Severity
Add Trap
Delete User-Defined Traps
Name
Category Name
Severity
Enterprise OID
Description
Format String
Generic Trap ID
Specific Trap ID
Delete Trap
Reset Built-in Trap Definitions
Table 211. Reset Built-in Trap Definitions
Field
Edited Traps
Name
Category Name
Severity
Enterprise OID
272
Description
To provide or edit the enterprise OID (SNMP OID prefix) of the event source that you want to monitor.
To provide the specific trap ID of the SNMP trap that you want to monitor from the required event source.
To provide or edit the message string that is displayed in the
OpenManage Essentials alert logs.
Displays the severity of the trap. You can modify the severity of the trap to:
• Unknown
• Info
• Normal
• Warning
• Critical
•
By Varbind Value. See Severity Configuration By Value
.
Click to add the trap definition to the User-defined Trap(s) grid.
Displays the trap name.
Displays the category name of the trap.
Displays the severity of the trap.
Displays the enterprise OID (SNMP OID prefix) of the event source that you want to monitor.
Displays the trap description
Displays the message string that is displayed in the
OpenManage Essentials alert logs.
Displays the generic trap ID of the SNMP trap that you want to monitor from the required event source.
Displays the specific trap ID of the SNMP trap that you want to monitor from the required event source.
Click to delete the selected traps.
Description
Displays the trap name.
Displays the category name of the trap.
Displays the severity of the trap.
Displays the enterprise OID (SNMP OID prefix) of the event source that you want to monitor.
Field
Format String
Description
Generic Trap ID
Specific Trap ID
Revert Traps
Description
Displays the message string that is displayed in the
OpenManage Essentials alert logs.
Displays the trap description
Displays the generic trap ID of the SNMP trap that you want to monitor from the required event source.
Displays the specific trap ID of the SNMP trap that you want to monitor from the required event source.
Click to revert the state of the selected traps to the original state in the OpenManage Essentials database.
273
advertisement