• OpenManage Network Manager can automate sending e-mail if a configura-
tion file changes. If the e-mail attachment describing config changes is
empty, now the e-mail sent says "No changes" in the subject. (8934)
• To produce e-mails that do not count a shift in a config file line's position as a
change, modify the following property in
\owareapps\netrestore\lib\nr.properties (or, better, override it in
owareapps\installprops\lib\installed.properties):
#============================================
# NetConfig Move Omit Property:
# Terms specified will be used to let NetConfig
# know what movement changes in config files should be
# included in configuration changes emails.
#
# Note: This property is only used if
# identical(!) lines move in config files.
#
# Example:
# Old Changes:
#
# New Changes:
#
#
# In the above case the line moved from line 259 to 273.
# This change will show up in the email sent to the specified
# end user.
# To omit this change from the email, include 'ntp server' in
# the property below.
# Best practice is to place this property in
# ...\owareapps\installprops\lib\installed.properties
#============================================
#append.com.dorado.redcell.netrestore.backup.move.omit=,## Last
Event/Alarm Management
• Added Entity Description as a viewable field in the alarm manager. (6054)
• The filter manager inside the event processing rules editor now allows you to
filter by either entity or by entity name. (2199)
• You can now view affected services and customers for selected alarms by
right-clicking them. (4678)
• Added Alarm Suppression which can be initiated either manually or by a
schedule.
• Added Alarm Propagation
line 259: ntp server 10.20.0.1
line 273: ntp server 10.20.0.1
Open Manage Network Manager – Release Notes
3
Need help?
Do you have a question about the OpenManage Network Manager and is the answer not in the manual?
Questions and answers