Nortel INM 3.1, Руководство по выпуску

Страница: 15 / 24

Release Notes 15 of 24
INM Release 3.1 Release Notes Issue 1.0
triangle. Once in that state, the status icon will be “stuck” showing the
yellow triangle, even though all network elements are reporting. There is
no impact on actual alarm reporting: just the status icon.
2 The user cannot assign alarm filters to NEs as they are being enrolled. The
ability to select alarm filters and apply them against all future NEs is not
possible in this release. However, the ability to set up future NEs to show
all alarms or show no alarms is still possible. The user will have to assign
alarm filters to NEs after they are enrolled: he would select an NE, bring
up the alarm filter dialog and then select the alarm filters that will filter the
NEs alarms.
5. Alarm History
1 For Threshold Crossing Events that are provisioned as alerts, there will be
a corresponding record with the severity set to undetermined. Currently the
Alarm History function for these alert records is incapable of filtering them
out. The user will see some alert records in the browser which he should
not see based on the filter settings. These alerts cannot be filtered out. To
avoid the problem, the user may set alerts to alarms so that they can be
handled like other alarms.
6. Improved On-Line Help
1 The colors of the links that are displayed in the Netscape main window
(legend of icons for example) do not correspond to the colors that are
displayed in the GNB. For example, a turquoise link (active link) appears
as green and a loss of association (blue) appears as white. In addition to
that, when the user invokes Help from a Link object menu and is brought
to a table showing the Ring traffic Link states, the background color of the
link in the table is white (instead of blue which is the background color of
the Netscape main window) and therefore do not show the link colors
properly.
7. Bridging
1 In the GNB, the bridging status field in the Controller List Display for
indirectly monitored controllers, is reported as unknown when it is not.
Therefore the GNB users cannot determine the correct bridging status of
their indirect controllers. The user should check the GNB of the server
monitoring the controller or any GNE.
8. MOAs
1 When the user attempts to login to the MOA while he already has a login
session with that MOA, the existing login window is not brought to the
foreground as it happens for OPC logins. The user has to search through
the windows to find the login window.
2 MOA based Remote-login sessions are not subject to the INM limitation
of six concurrent active login sessions. This applies to all MOA logins
(OC3 Express, Titan, DV45), NPC logins, and NE logins (Titan NE, OC3
Express NEs). The reason is due to the different manner in which remote