Accessnode/Accessnode Express - Nortel INM 4.1 Release Note

Nortel inm 4.1 software: release note
Hide thumbs Also See for INM 4.1:
Table of Contents

Advertisement

16 of 32
Release Notes for INM 4.1 GUI
4 When OC-3 Express or Express CX NEs are removed from a span of
5 If the Ethernet cable is disconnected and then reconnected from an INM
6 When the user attempts to login to an NE while he already has a login

7. AccessNode/AccessNode Express

1 When the user adds ANX VM (Voice Module) NEs from the GNE, the
2 An incompatibility in the generic fault management MOA interface when
INM Broadband Release 4.1
regen NE is decommissioned from the OPC before being detached from
the INM traffic link, the configuration will be missing traffic links where
links used to be attached to the regen. The user should perform the
following steps:
- Using the OPC Commissioning Manager, recommission the regen (using
the same NE Id).
- Open the GNE (or if one is running with multiple views, switch to another
view and come back).
- The traffic link(s) are displayed attached to the regen NE.
- Using the GNE Layout menu command "Attach Regens to <traffic
link>", remove the regen from the traffic link(s). This must be done one
link at a time. For each link, after invoking the "attach" command, click on
the two endpoints but not the regen.
- Save the view from the GNE.
- Using the OPC Commissioning Manager, decommission the regen.
control and then re-added to the span of control, they do not appear in the
correct location in the GNB (sometimes the GNE also). As a workaround,
if any NE is to be removed from a Span of Control, all NEs in the Span of
Control should be deleted and then re-added in the same order they were
originally added (including the previously removed NEs). This ensures NE
IDs are assigned to the NEs by the MOA in the same order.
workstation, the behavior of the NE login sessions that were running at the
time is undetermined. Depending on the software/hardware combination,
the session might be closed or kept open for a certain period of time. If this
happens, the user simply needs to restart the login session normally.
session with that NE, the existing login window is not brought to the
foreground and a new login session appears and asking for an ID and
password.
newly added ANX VM NEs are placed underneath existing ANX VM NEs
already in the view. The user can move the NEs in order to see all of them.
bridging pre-OPC28 bridge files causes any "new" NE types to show up as
unknown icons (without the bitmap and the text) on the GNB. "New" types
are NEs that are not originally listed upon installation in the
/opt/nortel/inm04/noc/config/neTypeinfo/neTypes file. In INM 4.1, only
the Data Module for the AccessNode Express falls into this category.
Therefore the customer will not be able to log into the Data Module or view
the Shelf Level Graphics for the Data Module thus effectively meaning that
the Data Module cannot be managed from INM. The user should go
Issue 1.0

Advertisement

Table of Contents
loading

This manual is also suitable for:

Inm broadband 4.1

Table of Contents