Manualshelf

Owners Manual

ManualsBrandsDell ManualsComputer equipmentOpenManage Network Manager
11121314151617181920
Table Of Contents
New Features/Devices Supported in 6.5
12
• A new Scheduled Maintenance (Next 30 Days), Historical Maintenance Log, & All
Future and Historical Maintenance Logs reports and Maintenance Logs Template
have been pre-seeded. These reports capture maintenance log entries that have
been entered on a managed devices. The maintenance log information can be
also seen in detail page of a managed devices under maintenance info tab.
(28811)
• Event Processing Rule (EPR) types have been re-categorized. The prior category
“Pre-Processing” was split into three new categories “Protocol Translation”,
“Stream Based Correlation” and “Event Definition Override”. Each EPR type that
was previously within the “Pre-Processing” category was assigned to one of these
three new categories on the basis of the when these rules come into play within
the event life cycle. The prior category “Post-Processing” was renamed
“Automation”. (28493)
• Variable Binding Definitions can now be viewed and edited through a new
portlet, which was added to the “Definitions and Rules” page. (28493)
• The Event Definition edit screen was enhanced to allow users to configure service
propagation, entity lookup type, mining of variable bindings, and automated
parent/child correlation for root-cause analysis. These features could previously
only be configured through XML and required the server to be restarted to take
effect, but these features are all now fully configurable through the GUI. (28493)
• Automation Event Processing Rules can now have explicit member entities,
which is a convenient way of configuring the EPR to only be triggered by events
that are associated with these member entities. Explicit membership also allows
for the default filter criteria and/or action parameters to be overridden by
parameters that are associated with the explicit members. (28493)
• The general discovery profile options were modified to include the “Attempt to
enable SNMP” option and “Equipment Type” list for SNMP device configuration.
(28812, 29809)
• Syslog escalation was enhanced to allow for alarm suppression and also for the
severity of the resulting event to be determined by the severity from the original
syslog message. (26090)
• Any event can now be forwarded to a northbound interface as a syslog message
or as an HTTP REST call. Northbound forwarding of SNMP traps is still supported
so now users can choose from any of these three message types when creating an
Event Processing Rule to forward events northbound. (27926)
• Traffic Flow Application names can now be edited. This is useful if custom L7
applications are used. In prior versions, only the L4 protocol name and port
number should show for custom application names, but these can now be edited
through the GUI. (28596)
• In the expanded traffic flow portlet, in the table of aggregate values that appears
below the line graph, the values now have a higher degree of precision. In
previous versions, these values were rounded to the nearest whole number, but
now the values can include fractions of up to two decimal places. (27506)