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

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

14 of 24 Release Notes
INM Broadband Release 3.1 Issue 1.0
the client side and updates the Management Server List incorrectly by
deleting the server from the Controller List.
2 After a connection is dropped from the preferred Direct Server, the
reluctant promoted INM can potentially use all the available connection
slots at the Controller and lock-out the preferred Direct server. In other
words, when a client is promoted, and if the maximum direct connections
to the Controller has been attained, then it will not be bumped out by a
server which has been initially configured to have a direct connection to
that Controller. The GNE user will have to decommission some of the
reluctant promoted connections, in order to free some slots at the
Controller.
3 If a reluctantly promoted controller is deleted from the list of controllers,
the GNB/GNE may exit unexpectedly. To avoid this problem the user
should wait until the promoted controller demotes, or edit the controller to
be monitored directly, save, and then delete the controller.
4 When importing large numbers of controllers in the GNE that result in very
large numbers of network elements (e.g. more than 1000 NEs) being added
to a single network window, sometimes the scroll bar will “jump” so that
the new network elements are not visible after they are added. Note that in
this situation, the new network elements have still been successfully added
to the window. It is just that they are not visible after being added like they
normally are because the scroll bar is not positioned at the very bottom of
the window. This problem might also occur in the GNB when large
numbers of network elements are added. It will not always be obvious that
new network elements have been successfully added to a network window
when more than 1000 network elements are added at once. This may cause
some initial confusion about where the new network elements are or may
cause the GNE user to believe that the operation has failed for some
reason. If this situation occurs, drag the scroll bar of the window in which
the network elements were added to the very bottom of the window. The
new network elements should then be visible.
5 Indirect MOAs show MOA software load in the SoBridge list
instead of the NE release (eg. MOA04BI is displayed instead of OC3 MOA
REL 2.0).
3. Problem Analyzer
1 The OC-48 High Power Transmitter and OpAmp Line and Section alarms
are not supported on this release of the Problem Analyzer. OC-48 High
Power Transmitter and OpAmp Line and Section alarms do not generate
problems on the GNB. Problems may be generated on the primary OC-48
cards instead of being pin-pointed to the HPTX or OpAmp cards.
4. Partitioned Access
1 If a GNB is displaying a view with at least one excluded and suspended
NE, resuming alarm reporting on one of those network elements will cause
the GNB’s status icon to change from the green checkmark to the yellow