Nortel INM 4.1 Release Note page 19

2 When the INM Connection Manager GUI is used to convert an STS-1
3 When adding a unidirectional Matched Node connection using the INM
4 When 2 Connection Management windows (from 2 GNBs) are opened for
5 When requesting a list of connections from a high speed traffic display link
6 When creating VT connections that mix manual selection of
INM Release 4.1 Release Notes
clicked, the connection provisioning will be rejected by the controller
(OPC) with the following message being displayed to the user: "The
connection was unable to be added to the controller's database." Therefore,
the invalid connection will not get provisioned in the network.
connection to 28 VT 1.5 connections on an OC-12 TBM system, the INM
Connection Manager GUI may, on some occasions, close with an error
dialog indicating that communications with the controller have been lost.
Note that in all cases the STS-1 to VT 1.5 conversion will have completed
successfully. The user must re-open the INM Connection Manager GUI.
Connection Manager GUI, if the user first selects the gateway nodes, then
toggles the route from "default" to "alternate", the route will stay as
alternate, and any subsequent attempts to change the route back to
"default" will not have any effect on the route of the connection (although
the selector button will show the connection as being on the "default"
route). In such a situation, the user can cancel the current connection add
operation and retry, in which case the "default" route will be selected.
the same OC-3 Express NE and if connections are modified from the craft
interface simultaneously, the connection changes made at the craft
interface are not captured in the Connection Management inventory
displays. Both Connection Management windows have to be closed and
re-opened in order to see the connections. This is due to the fact that the
OC-3 Express Network Element does not provide an automatic change
notification.
for 2 Node BLSR systems, the connection inventory may not be properly
displayed. In some cases, the connections will be properly displayed for
one link in the ring, but not for the other link. To avoid this problem, the
user should request selected connections in an alternate manner, either by
requesting all connections within the entire ring or requesting connections
for either of the NEs in the 2 node BLSR.
tributaries/channels with the auto-selection feature, there is an increased
probability that the selected tributaries may be incorrect. Typically, this
occurs when the auto-select is enabled after manual selection of
connection tributaries or channels within the same connection add/edit
request. It can also occur when manual selection follows auto-selection.
The user must manually reselect the invalid tributaries or channel based on
available inventory presented in either the Tributary Usage or Channel
Usage Dialogs.
Release Notes for INM 4.1 GUI 19 of 32
Issue 1.0