Nortel INM 4.1 Instruction Manual

Release Notes
*NTse68HD.0100*
Integrated Network Management Products
INM Broadband Release 4.1
Release Notes For Release 4.1
Document release: Issue 1.0
Date: November 1998

INM Release 4.1 Release Notes Issue 1.0
Integrated Network Management Products
INM Broadband Release 4.1
Release Notes For Release 4.1
1998 Northern Telecom
All rights reserved
Ethernet is a trademark of Xerox Corporation.
HP is a trademark of Hewlett-Packard Co.
NCD is a trademark of Network Computing Devices
S/DMS AccessNode is a trademark of Northern Telecom.
S/DMS TransportNode is a trademark of Northern Telecom.
Tektronix is a trademark of Tektronix Corporation.
UNIX is a registered trademark of UNIX System Laboratories, Inc.
VT100 is a trademark of Digital Equipment Corporation of Maynard, Mass.
X Window System is a trademark of the Massachusetts Institute of Technology.
Document status: Issue 1.0
Date: November 1998

iv of 32
INM Broadband Release 4.1 Issue 1.0
Publication history
November 1998
1.0 (Caroline Samson)
- Official release for INM 4.1 GA.

Table of Contents vof32
INM Release 4.1 Release Notes Issue 1.0
Table of Contents
About this document 7
Structure of the document 7
Audience 7
Summary of Features 9
Release Notes for INM 4.1 GUI 13
1. Installation 13
2. PM Threshold Provisioning 13
3. Protection Status and Control 14
4. Federated Networks 14
5. Partitioned Access 15
6. Configuration Management 15
7. AccessNode/AccessNode Express 16
8. Bridging 17
9. MOAs 17
10. Fault Management 18
11. Connection Management 18
12. OC-192 Release 5.0 WEB UI 20
13. Remote Inventory and Shelf Level Graphics 20
14. On Line Help 20
15. Trouble Ticketing 20
Release Notes for INM 4.1 Building Blocks 21
1. Installation 21
2. Common issues to all Building Blocks. 21
3. AMGUI (Application Management GUI). 21
4. CORBA Gateway 22
5. SONET MOA 22
6. FMBB (Fault Management Building Block) 23
7. RMBB (Resource Management Building Block) 23
8. PMBB (Performance Management Building Block) 23
9. CMBB (Connection Management Building Block) 24
List of Terms 25
Appendix:
Technical support and information 29
INM Customer Care: How to reach us 29
Critical Issues 29
Product Warranty 30
INM Product Services 30

vi of 32 Table of Contents
INM Broadband Release 4.1 Issue 1.0

INM Release 4.1 Release Notes Issue 1.0
7of32
About this document
This document describes the INM Broadband Release 4.1 release notes (for
the GUI and the Building Blocks) that the users should be aware of before
using the software application.
The items that are listed in this document will be addressed in the upcoming
releases of INM Broadband.
It is strongly recommended that users and administrators read all relevant User
Guides prior to installing and using the product.
Structure of the document
This document is structured in a way to highlight the major considerations for
each of the features introduced in this release (GUI as well as Building
Blocks). The two main sections of the document are entitled Release Notes for
INM 4.1 GUI and Release Notes for INM 4.1 Building Blocks, and are divided
into several subsections corresponding to the actual new features introduced in
INM Broadband Release 4.1.
Audience This Release Notes document has been specifically prepared for the following
audience:
INM 4.1 GUI section
• INM Broadband Software Administrators
• INM Broadband Users
INM 4.1 Building Blocks section
• INM Broadband CORBA Programmers

8of32 About this document
INM Broadband Release 4.1 Issue 1.0

INM Release 4.1 Release Notes Issue 1.0
9of32
Summary of Features
The new features offered by the Integrated Network Management Broadband
Release 4.1 applications are summarized below.
• Protection Status and Control GUI and Contract Interfaces (CI) which
provide GUI enhancements to support protection status display and
protection control for linear systems (1:1, 1+1, 1:N), 2 fiber-ring systems
(OC-12 and OC-48 BLSR), as well as OC-192 4-fiber rings. Protection
control will provide the ability to issue high speed protection control and
lockout commands from the Graphical Network Browser. This feature will
also provide the open, standards-based Contract Interfaces using the
CORBA Interface Definition Language (IDL) to perform high speed
protection switch control on the topologies mentioned above.
•Linear and 1:N Traffic Display which provide GUI enhancements to
support the traffic display for linear systems (1:1, 1+1, 1:N).
•OC48 Release 14 support (Connection Management Interface
Enhancements) which provide enhancements to the Connection
Management Building Block (CMBB) Contract Interface (CI) to support
connection provisioning of concatenated STS-3c (Uni/Bi) and STS-12c
(Uni/Bi) connections on OC-48 BLSR systems. Enhancements to
termination inventory and information services are also provided in order
to support OC-3 tributary cards on OC-48 Ring (BLSR) systems.
• Drop and Continue on Protection (DCP) GUI and Contract Interface
provides support for the new DCP provisioning scheme to be used when
provisioning uni-directional or bi-directional matched node connections
on OC-12 TBM and OC-48 BLSR systems. Enhancements to the GUI
support the selection of either the Drop and Continue on Working (DCW)
or the DCP provisioning scheme for creating bi-directional or
uni-directional matched node connections. As well, the editing of an
existing uni-directional or bi-directional matched node connection from
the DCW to the DCP scheme and vice versa is supported. Enhancements
to the Connection Management Building Block (CMBB) Contract
Interface (CI) provide the same DCP provisioning and editing capabilities
through the open, standards based CI using the CORBA Interface
Definition Language (IDL).

10 of 32 Summary of Features
INM Broadband Release 4.1 Issue 1.0
•PM Threshold Provisioning GUI and Contract Interface provides the user
the capability to get and set Performance Monitoring Threshold
parameters from within the INM Broadband GUI and PMBB
(Performance Management Building Block).
• OC3 Express Data Release 3.1 and 4.0 Contract Interfaces Support for
Fault Management, Connection Management, Performance Monitoring,
ResourceManagement.Thesupportforthenew EIM card is providedonly
through the INM Broadband GUI.
•OC192 Release 4 GUI and Contract Interfaces Support for Fault
Management, Remote Inventory (including Shelf Level Graphics),
Performance Monitoring and Connection Management (for 4 fiber BLSR
systems).
•Facility Provisioning Contract Interface Enhancements which support
additional attributes and additional facilities. This includes the support for
optical facilities (OC3, OC12, OC48) and electrical facilities (DS1, DS3,
STS1, STS3, STS12 and STS48 on OC3/OC12 TBM and OC48 Network
Elements.
•GUI Enhancements will be provided to the Alarm Dialog which will be
enhanced to permit resizing of the Dialog itself as well as different parts of
it. In addition, new GUI technology will allow the rearranging, removing,
restoring columns.
•Web User Interface for OC192 Support provides the user to login to the
OC-192 Network Element (which supports the Web UI) and use the new
Web Based NE User Interface that is being introduced in the
TransportNode OC-192 Release 5.0.
• Resource Management Contract Interfaces provide the equivalent support
and functionality existing in the INA Transport Release 2.0 by replacing
the Configuration INA DPE Contract Interfaces with the CORBA Contract
Interfaces (CI). The CORBA CIs will provide functionality for Network
Element discovery/query, equipment inventory query, as well as Facility
provisioning for OC3/OC12 TBM and OC48 systems.
• Integrated Fault Management provides integrated support for fault
information across multi-domain, multi-vendor networks. The Fault
Management Building Block (FMBB) provides open, standards based
contract interfaces using CORBA IDL supporting alarm query and alarm
notification functionality, as well as protection status and control.
•Express CX GUI Support of Fault Management, Performance Monitoring,
Remote Inventory, Electronic Software Delivery, Remote Login, Shelf
Level Graphics and Connection Management. The support for the Express
CXNetworkElementisprovidedthroughthe OC-3 Express MOA Release
3.1.

Summary of Features 11 of 32
INM Release 4.1 Release Notes Issue 1.0
•PC GUI Remote Login support (JungleMUX JNCI, OC-3 Express, and
AccessNode Express Voice Module) allows an INM Broadband user to
perform a remote login Reach-Through to the PC-GUI application running
on a Windows NT Server machine and running an Element Manager
application.
•AccessNodeExpressDataModule Support for Node Graphics,Shelf Level
Graphics as well as Remote Login.
•Scalability Enhancements for Contract Interfaces extends the engineering
limits introduced in the INM 3.1 to the new Contract Interfaces.
•Centralized Alarm Printing offers the capability to output the alarm
information for the raised and the cleared alarms: if the Centralized Alarm
Printing functionality is enabled, all raising and all clearing alarms are
printed out, in real time, as they occur.
•Trouble Ticketing offers the capability to select a fault from the Alarm
Details dialog of the Graphical Network Browser, and generate a
corresponding Trouble Ticket in Clarify’s Clear SupportTM product.

12 of 32 Summary of Features
INM Broadband Release 4.1 Issue 1.0

INM Release 4.1 Release Notes Issue 1.0
13 of 32
Release Notes for INM 4.1 GUI
1. Installation
It is strongly recommended that users read and understand the installation
procedures in the User Guide before installing INM Broadband Release 4.1
GUI.
2. PM Threshold Provisioning
1 When a confirmation message is displayed as a result of applying changes
that have been made on the PM Threshold parameters dialog, and the user
closes the PM Threshold dialog (using the top left corner of the window)
without responding to the confirmation message, then the confirmation
message stays open. If the user then clicks OK to the confirmation
message, the message “Modifying Thresholds” will stay on the screen and
the changes will not take effect. The only way to get rid of the “Modifying
Thresholds” message is to close the GNB and re-open it.
2 For the PM Threshold Provisioning feature, the user may navigate and
select data with the mouse; however, navigation and selection data with the
keyboard is unavailable at this time. This shortcoming will be corrected in
a future release of INM.
3 If the user opens the PM Threshold window and then opens the Protection
Status and Control window to retrieve some thresholds, then whenever the
PM Threshold window is in use (retrieving), the PSC window gets frozen.
If PM Threshold window is not in use (but still open), the PSC is available.
Therefore the user should wait for the PM Threshold query to complete,
and then perform protection control command(s) as desired.
4 When the user performs the following:
- select an NE
- open the PM Threshold window and select type
- exclude that NE from the view and saves the view
- hit the Retrieve button and acknowledge the displayed message
- enable full access to that NE, save the view and hit the Retrieve button
again
then the user will get an error message, although the user should be able to
retrieve thresholds as full access is enabled and saved. To avoid this

14 of 32 Release Notes for INM 4.1 GUI
INM Broadband Release 4.1 Issue 1.0
problem, the user should acknowledge the confirmation message upon its
first appearance and then close the PM Threshold GUI. Then the user
should wait until access is re-enabled before reopening the PM Threshold
GUI.
3. Protection Status and Control
1 When performing a network reconfiguration (OC-192 linear back-to-back
network into a 4FR Ring network, OC-12/48 Linear to Ring, OC-12
non-VTM to VTM), the INM GNB display does not always correctly
display the high speed connection or Ring traffic between ADMs. If traffic
is suspected to be out-of-date (i.e. links missing or status inconsistent with
OPC or NE protection status), then revalidate the span from the GNE.
2 INM Traffic Display of linear (1:1, 1+1, 1:N) and 4 Fiber Ring
configuration does not report/show that a protection line is in a troubled
state (i.e. incapable of carrying traffic). For protection channels, INM only
reports/shows whether it is idle or active (currently protecting traffic for a
working channel). The NE alarm reporting functionality of INM can be
used to detect problems on protection channels.
3 Traffic display will be disabled for 1:N systems where one protection
group is managed by one controller and the other protection group is
managed by another controller. Traffic display links will be missing
between NEs in different controllers. To obtain full traffic display,
protection status and control functionality, commission all NEs of the 1:N
in the same OPC. Or to simply provide visual appearance of the 1:N
system, use the Layout command of the Graphical Network Editor to paint
the missing fiber links.
4 In the GNB, when an auto-switch is active, the failed span is shown with a
yellow broken pipe. If a forced or a lock-out switch is applied on this failed
span (where the auto-switch is active), a full gray pipe with forced or
lock-out indicators will replace the yellow broken pipe. This could mislead
the user in thinking that only the forced or lock-out switch is active, and
that there is no trouble on the span. However, the Protection Status and
Control dialog will display the accurate information, so the user can verify
the status of the span with this dialog.
4. Federated Networks
1 In some cases alarm acknowledgments may not propagate to all INMs,
specifically when there is no federation connection already established
between all members of the federation.
2 If the user bridges an OC-48 Release 14.1 OPC with INM 4.1, then if the
user attempts to invoke the Connection Manager with INM 3.1, the
message “Attempting to load connection information” is displayed and
stays on the screen. The Connection Manager window never comes up.
3 In a federated environment, when an INM Release 4.1 client is connected
to an INM 3.1 server the following functionality limitations apply:

Release Notes for INM 4.1 GUI 15 of 32
INM Release 4.1 Release Notes Issue 1.0
Protection status functions: NOT AVAILABLE
Linear traffic display links: NOT AVAILABLE
BLSR traffic display: AVAILABLE
PC GUI Login: NOT AVAILABLE
OC-192 Connection Management: NOT AVAILABLE
All other INM functionality provided with INM Release 4.1 is available.
4 When a Client is indirectly monitoring both Primary and Backup
controllers through the same server, and if any one of the controllers
(primary or backup) is deleted from the server, this causes a promotion on
the client side and updates the Management Server List incorrectly by
deleting the server from the Controller List.
5 Whenimporting largenumbers of controllers intheGNE 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’s 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. The user is advised to import a
small quantity of NEs at one time. Furthermore, the user may use the
nested group capability in INM to separate and store the NEs.
5. Partitioned Access
1 When an NE is blue (lost association), then if the GNE user selects the “No
Alarms” option to filter out all alarms, then it is fine. However, if the GNE
user selects the “Filtered Alarms” option and wants to apply a specific
filter, then there will always be no alarms on the GNB even if there are
alarms that pass the filter. In other words, the user can see all alarms or no
alarms on the GNB.
6. Configuration Management
1 When a GNE user is in the process of adding or editing a controller (i.e.
Add or edit dialog still open), the GNE “Save” option is enabled even
though it should be disabled. If the GNE user tries to save the view while
adding or editing a controller, the INM can be put to an unstable state,
which may lead to a corrupt configuration file.
2 OC-3 Express circuit packs support the notion of primary and secondary
states. Sometimes 2 or more secondary states are combined together to
produce a composite secondary state which can exceed a length of 9
characters. INM currently supports a maximum of 9 characters, thus the
secondary state is truncated so it does not exceed 9 characters.
3 In the case were a regen NE has been attached to a traffic link (using the
GNE Layout menu command “Attach Regens to <traffic link>”) and the

16 of 32 Release Notes for INM 4.1 GUI
INM Broadband Release 4.1 Issue 1.0
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 ifone is running with multipleviews, switch toanother
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.
4 When OC-3 Express or Express CX NEs are removed from a span of
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
originallyadded(includingthe previouslyremovedNEs). This ensures NE
IDs are assigned to the NEs by the MOA in the same order.
5 If the Ethernet cable is disconnected and then reconnected from an INM
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.
6 When the user attempts to login to an NE while he already has a login
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.
7. AccessNode/AccessNode Express
1 When the user adds ANX VM (Voice Module) NEs from the GNE, the
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.
2 An incompatibility in the generic fault management MOA interface when
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.
Thereforethe customer willnotbe able tolog into the DataModule or view
theShelf Level Graphicsfor the DataModulethus effectivelymeaningthat
the Data Module cannot be managed from INM. The user should go

Release Notes for INM 4.1 GUI 17 of 32
INM Release 4.1 Release Notes Issue 1.0
through the normal steps of adding and bridging a controller, delete the
controller, and then re-add it.
3 When a CDS alarm is generated, the title for the CDS icon in the ABM
shelf-level graphics disappears. Therefore the user will no longer see the
title of the CDS icon. To correct the problem, if the CDS icon title is not
visible, the user should obscure it with another window and then bring the
ABM shelf window to the front again. This will cause the icon to re-draw
itself, and the icon title will reappear.
8. Bridging 1 Upon completion of a bridging operation, if there are Network Elements
that have communication problem to the OPC (i.e. loss of association), the
menu items for some of the required INM functionality that should be
enabled will be disabled for those Network Elements. Examples include
the "Show connections for NE" and "Query performance statistics" menu
items. To correct the problem, remove the IP address of the system that is
bridged (from the GNE), and re-connect back to it. This will enable all the
required menu items. Alternatively, the menu items will become
re-enabled without requiring this workaround when the association comes
back up to the affected Network Element(s).
9. MOAs1
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
login is implemented for MOA based Controllers (as opposed to OPCs).
The user could potentially open any number of login sessions consuming
more and more resources and ultimately affecting performance of other
functionality. The user has to take note of this limitation and ensure to keep
the number of open sessions per GNB session, at any time to 6.
3 When traversing from one Network Element to another via the Connection
Manager during a period when the topology information is invalid, and
when the SDCC communications are re-enabled at the affected NE, the
GNB would freeze as soon as the “Add Next Connection At” menu option
is chosen. In this situation, the GNB freezes and no menus could be
selected from the GNB (window or nodal). However, impact is limited to
traversing from one Network Element to another via the Connection
1An incompatibility exists between INM 4.1 and OC-3X TL1 MOA 2.0 and prior. The customer is
required to upgrade to OC-3X TL1 MOA Release 2.0.1 or greater to provide support for Remote
Inventory, Shelf Level Graphics and Performance Monitoring.

18 of 32 Release Notes for INM 4.1 GUI
INM Broadband Release 4.1 Issue 1.0
Manager during a period when the topology information is invalid. The
user should close and re-open the GNB.
4 For the OC-3 Express, the provisioned PEC will always be the same value
as the Physical PEC of the circuit pack. This is a limitation of the OC-3
Express NE since slots do not have the concept of a Provisioned PEC. No
workaround is available. This is a limitation of the OC-3 Express
architecture.
10. Fault Management
1 When the user sends a fast sequence of double clicks on some alarm
balloons, the alarm window is too busy refreshing, so that the pull down
menu under the alarm window “File” option does not show up. Therefore
the customer cannot use the “File” menu options. However there is a
workaround for each of the menu options: for the “Print Screen/Print
Window” options use the window object menu. For the “Close” option
double click the upper left corner of the window. For the “Help” option
invoke help from another item, then navigate through Netscape.
2 In a heavy alarm inflow, combined with alarm list scrolling, some alarm
lines display only the upper half of the characters. Scrolling the alarm list
corrects the problem.
3 The facility IRC Secondary Path Problem Type (Inter-Ring Secondary
Path fail) has been replaced with 2 new alarms: “Rx Inter-Ring secondary
feed fail” and “Tx loss of Inter-Ring secondary feed”. Currently, INM does
not support the correct construction of the unit string for these alarms.
When this alarm is propagated to the INM, the alarm window displays a
channel number when no channel number is present on the OPC or NE.
This is an inconsistency based on the old alarm format. The user is advised
to ignore the channel number associated with these two alarms.
4 First-alert alarms are alarms raised on OC12/OC48 systems from
subtending OC3 Express Systems. The OC3X first alert alarms appearing
provisionedon anOC12system do not properly propagate totheINM. The
unit field visible from the Active Alarms screen does not get updated
properly. In addition, after a period of 2 minutes with no SDCC between
an OC-12 system and the subtending OC-3 Express system, the
"First-Alert connection down" alarm gets raised and any other remote
alarms will be lost.
11. Connection Management
1 In the INM Connection Manager GUI, the STS channel selector field will
be incorrect with respect to the availability of some of the used channels
during an In-Service Rollover of a connection from the OPC Connection
Manager UI. Specifically, the destination channel for the rollover will be
marked as available, even though it is in use. As a result the user can select
such a used channel from the STS channel selector, or can enter a used
channel number in the Channel data entry field, and this used channel will
be shown as being valid at the GUI. However, after the “Apply” button is

Release Notes for INM 4.1 GUI 19 of 32
INM Release 4.1 Release Notes Issue 1.0
clicked, the connection provisioning will be rejected by the controller
(OPC) with the following message being displayed to the user: “The
connectionwas unable to beaddedto the controller’sdatabase.” Therefore,
the invalid connection will not get provisioned in the network.
2 When the INM Connection Manager GUI is used to convert an STS-1
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.
3 When adding a unidirectional Matched Node connection using the INM
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.
4 When 2 Connection Management windows (from 2 GNBs) are opened for
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.
5 When requesting a list of connections from a high speed traffic display link
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.
6 When creating VT connections that mix manual selection of
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.

20 of 32 Release Notes for INM 4.1 GUI
INM Broadband Release 4.1 Issue 1.0
12. OC-192 Release 5.0 WEB UI
1 If the user performs a WEB UI login to an NE, a new window is opened
for each login even though a Netscape window is already opened for that
NE.Therefore, the user should checkifthere is already aNetscapewindow
opened for that NE before performing a Web UI login.
13. Remote Inventory and Shelf Level Graphics
1 ShelfLevelGraphics only supports a maximum of 8 character Circuit Pack
names.
14. On Line Help
1 An error message is displayed from Netscape concerning lack of colors
when logging on the workstation. In addition, 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.
15. Trouble Ticketing
1 With UNIX Email Utility, each time INM sends a trouble ticket to Clarify,
the SMTP daemon, “sendmail”, adds some logging messages to
/var/adm/syslog/mail.log. This log file can grow in size over time. The
administrator can disable the logging, which will result in no further
updates (about the trouble ticketing) to the log file, by changing the line
“LogLevel=9”ofthefile/etc/mail/sendmail.cf to“LogLevel=0”.However,
evenifthe sendmail.cf file is changed as above,sendmail will keeplogging
other warning or error messages (for example, email host unknown or
domain name wrong) into mail.log. If the size of mail.log becomes too
large, the administrator may have to remove it manually to free up disk
space of the /var directory.