Part No.

205970-H
November 2004

4655 Great America Parkway

Santa Clara, CA 95054

Release Notes for Optivity

NMS 10.3

*205970-H*
2

Copyright © 2004 Nortel Networks

All rights reserved. November 2004.
The information in this document is subject to change without notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate and reliable, but are presented without express or implied
warranty. Users must take full responsibility for their applications of any products specified in this document. The
information in this document is proprietary to Nortel Networks Inc.
The software described in this document is furnished under a license agreement and may be used only in accordance
with the terms of that license. The software license agreement is included in this document.
Trademarks
Nortel Networks, the Nortel Networks logo, the Globemark, Accelar, Alteon, BayStack, Business Communications
Manager, Centillion, Meridian, Optivity, Passport, and Versalar are trademarks of Nortel Networks.
Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated.
Oracle is a trademark of Oracle Corporation.
OpenView and HP-UX are trademarks of Hewlett-Packard Corporation.
IBM, NetView, Tivoli, TME, and TME 10 are trademarks of IBM Corporation.
Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.
Netscape Navigator is a trademark of Netscape Communications Corporation.
UNIX is a registered trademark of X/Open Company Limited.
Sun, Solaris, and Java are trademarks or registered trademarks of Sun Microsystems, Incorporated.
The asterisk after a name denotes a trademarked item.

Restricted rights legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software,
the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the
Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of conditions
In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the
right to make changes to the products described in this document without notice.
Nortel Networks Inc. does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All
rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above
copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials,
and other materials related to such distribution and use acknowledge that such portions of the software were developed
by the University of California, Berkeley. The name of the University may not be used to endorse or promote products
derived from such portions of the software without specific prior written permission.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

205970-H
 3

In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains
restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third
parties).

Nortel Networks Inc. Optivity* network management software license agree-

ment
NOTICE: Please carefully read this license agreement before copying or using the accompanying Optivity network
management software or installing the hardware unit with pre-enabled Optivity network management software (each of
which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT
ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS
AGREEMENT ARE THE ONLY TERMS UNDER WHICH NORTEL NETWORKS WILL PERMIT YOU TO USE
THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the original
shipping container, within 30 days of purchase to obtain a credit for the full purchase price.
1. License grant. Nortel Networks Inc. (“Nortel Networks”) grants the end user of the Software (“Licensee”) a personal,
nonexclusive license: a) to use the Software either on a single computer or, if applicable, on a single authorized device
identified by host ID; b) to copy the Software solely for backup purposes in support of authorized use of the Software;
and c) to use and copy the associated user manual solely in support of authorized use of the Software by Licensee. This
license applies to the Software only and does not extend to Nortel Networks Agent software or other Nortel Networks
software products. Nortel Networks Agent software or other Nortel Networks software products are licensed for use
under the terms of the applicable Nortel Networks Inc. Software License Agreement that accompanies such software and
upon payment by the end user of the applicable license fees for such software.
2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws.
Nortel Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Nortel Networks or its licensors. The copyright notice must be reproduced and included with any copy
of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any
competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or any
copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the
Software or user manuals, in whole or in part. The Software and user manuals embody Nortel Networks’ and its
licensors’ confidential and proprietary intellectual property. Licensee shall not disclose to any third party the Software,
or any information about the operation, design, performance, or implementation of the Software and user manuals that is
confidential to Nortel Networks and its licensors; however, Licensee may grant permission to its consultants,
subcontractors, and agents to use the Software at Licensee’s facility, provided they have agreed to use the Software only
in accordance with the terms of this license.
3. Limited warranty. Nortel Networks warrants each item of Software, as delivered by Nortel Networks and properly
installed and operated on Nortel Networks hardware or other equipment it is originally licensed for, to function
substantially as described in its accompanying user manual during its warranty period, which begins on the date
Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole
remedy Nortel Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be
included in a future Software release. Nortel Networks further warrants to Licensee that the media on which the
Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days
from the date the Software is first shipped to Licensee. Nortel Networks will replace defective media at no charge if it is
returned to Nortel Networks during the warranty period along with proof of the date of shipment. This warranty does not
apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility
for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from
the Software. Nortel Networks does not warrant a) that the functions contained in the software will meet the Licensee’s
requirements, b) that the Software will operate in the hardware or software combinations that the Licensee may select, c)
that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Software
will be corrected. Nortel Networks is not obligated to remedy any Software defect that cannot be reproduced with the
latest Software release. These warranties do not apply to the Software if it has been (i) altered, except by Nortel
Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the
defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE FOREGOING
WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER

Release Notes for Optivity NMS 10.3

4

WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of its
own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered
files, data, or programs.
4. Limitation of liability. IN NO EVENT WILL NORTEL NETWORKS OR ITS LICENSORS BE LIABLE FOR
ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF
NORTEL NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT
SHALL THE LIABILITY OF NORTEL NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO NORTEL NETWORKS FOR THE SOFTWARE LICENSE.
5. Government licensees. This provision applies to all Software and documentation acquired directly or indirectly by or
on behalf of the United States Government. The Software and documentation are commercial products, licensed on the
open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.
6. Use of software in the European Community. This provision applies to all Software acquired for use within the
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the examination
of the Software to facilitate interoperability. Licensee agrees to notify Nortel Networks of any such intended examination
of the Software and may procure support and assistance from Nortel Networks.
7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to
Nortel Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the
Nortel Networks copyright; those restrictions relating to use and disclosure of Nortel Networks’ confidential information
shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if
Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason, Licensee
will immediately destroy or return to Nortel Networks the Software, user manuals, and all copies. Nortel Networks is not
liable to Licensee for damages in any form solely by reason of the termination of this license.
8. Export and re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data or
information without first obtaining any required export licenses or other governmental approvals. Without limiting the
foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first obtaining all
export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert any such
Software or technical data, or any direct product thereof, to any country to which such exports or re-exports are restricted
or embargoed under United States export control laws and regulations, or to any national or resident of such restricted or
embargoed countries; or (ii) provide the Software or related technical data or information to any military end user or for
any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons.
9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will
be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Nortel Networks Inc., 2375 N. Glenville Dr.,
Richardson, TX 75082.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN NORTEL NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST NORTEL
NETWORKS UNLESS NORTEL NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.

205970-H
 5

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Documentation on CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
What’s new in Optivity NMS 10.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Open issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Optivity NMS temporary files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Restoring Databases and Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Coresidency Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
OmniView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Fault System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Browser issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Optivity Integration Toolkit (OIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Platform integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Multicast issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
IP Telephony issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Agent support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Optivity NMS application and product support matrix . . . . . . . . . . . . . . . . . . . . . . . . . 19
Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Printed technical manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Windows and UNIX systems supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Release Notes for Optivity NMS 10.3

6

205970-H
 7

Introduction
This document contains important information supporting Nortel Networks*
Optivity* NMS 10.3. Read these release notes before you install Optivity
NMS 10.3 for the first time or migrate from Optivity NMS 10.2 to Optivity
NMS 10.3. The latest information about Optivity NMS, including patches,
technical bulletins, and fixed issues, is posted on the Nortel Networks Web site:
http://support.nortelnetworks.com.

Note: You cannot upgrade directly from Optivity NMS 10.1 or earlier to
Optivity NMS 10.3.

This document contains the following sections:

• “Documentation on CD‚” next

• “What’s new in Optivity NMS 10.3” on page 8
• “Open issues” on page 9
• “Agent support” on page 19
• “Optivity NMS application and product support matrix” on page 19
• “Where to find more information” on page 24

Note: Where this document refers generically to UNIX, it applies to both

HP-UX* and Solaris*. Specific references to HP-UX or Solaris apply
only to that UNIX type.

Documentation on CD
The documentation for Optivity NMS 10.3 is located on the Optivity NMS 10.3
Windows* CLIENT Only and Documentation CD. Open the Welcome.pdf file on
the root directory of the CD to browse the documentation using a graphical
interface of menus and links.

Release Notes for Optivity NMS 10.3

8

What’s new in Optivity NMS 10.3

Optivity NMS 10.3 includes the following new features and functions. See Using
Optivity NMS 10.3 Applications for more information about using these new
features:

• Enhanced discovery seeds - Optivity NMS 10.3 lets you configure discovery
seeds with IP addresses and ranges of addresses within which to discover the
network. Devices and subnets outside the specified ranges are omitted from
the discovery.
• View Domains - View domains are a new Optivity NMS concept introduced
in Optivity NMS 10.3. Each view domain consists of all of the network
elements within a range of IP addresses. Optivity NMS administrators can
assign specific view domains to specific Optivity NMS users. Users can use
Optivity NMS to view and manage only those network elements within their
view domains.
• Service Assignment - In Optivity NMS 10.3, you can assign the following
services to Optivity NMS users:
— Multicast
— IP-Telephony (VOIP)
— VLPS
— IP-VPN
Users to which services are not assigned cannot view service-related
InfoCenter folders.
• Enhanced InfoCenter folder sharing - In Optivity NMS 10.3, you can
designate specific users with whom to share InfoCenter folders. In previous
releases, folders were either not shared or were shared with all users.
• SNMPv3 discovery - When autotopology discovery encounters devices
configured for SNMPv3, it uses SNMPv3 protocol to get data from the
devices.

205970-H
 9

Open issues
This section describes open issues in Optivity NMS 10.3. Each issue is followed
by a Change Request (CR) number used for tracking purposes.

The following sections describe the open issues:

• “Installation‚” next
• “AutoTopology Manager” on page 10
• “InfoCenter” on page 11
• “OmniView” on page 12
• “MView” on page 12
• “Fault System” on page 13
• “Device Inventory Viewer” on page 15
• “Database Admin Tool” on page 15
• “Browser issues” on page 16
• “Optivity Integration Toolkit (OIT)” on page 16
• “Platform integration” on page 17
• “Multicast issues” on page 17
• “IP Telephony issues” on page 18

Installation

There are known issues regarding installing, uninstalling, or migrating to Optivity

NMS 10.3. The following sections describe the issues and their workarounds.

Optivity NMS temporary files

Optivity NMS 10.3 creates temp files under $LNMSHOME/db (UNIX) or

%lnmshome%\db (Windows). Note that Optivity NMS leaves some log files in
this directory, that get removed when you stop and restart Optivity NMS daemons
or services. (CR Q00607174)

Release Notes for Optivity NMS 10.3

10

Restoring Databases and Customizations

• When you are upgrading to or reinstalling Optivity NMS 10.3, the following
fault system preferences are not restored (CR Q01015808):
— Fault notification beep
— Syslog notification beep
— Trap notification beep
— Display DNS name
• If you are migrating your Optivity NMS 10.2 topology database to Optivity
NMS 10.3 using either the Database Admin Tool or database command line
utilities, you must restore the waldo database before you restore the smop
database. If you do not use this sequence, InfoCenter will not show the
previously-discovered end nodes. (CR Q01003890)
• If you create a custom folder in Optivity NMS 10.2 InfoCenter by copying an
existing global folder, or by copying devices from existing global folders,
when you upgrade to Optivity NMS 10.3 the folder is migrated but it is empty.
(CR Q01007322)

Coresidency Issues
• When you have Optivity NMS 10.3 installed on the same system as Optivity
Policy Server 4.0.1, and you have the following OIT files installed, objects
created with the otsclient command are not visible in InfoCenter
(CR Q01014256):
— NMS-OPS-v40-A.oit
— NMS_OPSApp_v40_A.oit
• When you have Optivity NMS 10.3 installed on the same system as Optivity
Telephony Manager, Optivity NMS does not work. (CR Q01014901)

AutoTopology Manager
• If you enter an invalid subnet mask while using the routerless discovery
feature, the subnet discovery process takes a long time to complete.
(CR Q00615975)

205970-H
 11

• Under Windows, Optivity NMS 10.3 is case sensitive regarding login names.
When you login as “Administrator” and create view domain, and then later
login as “administrator,” the domains you created do not appear in either the
InfoCenter View Domains folder or in the list of view domains in
AutoTopology Manager. The workaround for this issue is to always use the
same case when logging into Optivity NMS applications. (CR Q00981246)

InfoCenter
The following are known issues regarding the InfoCenter application:

• On UNIX, you may not be able to connect multiple InfoCenter clients to an

Optivity NMS server. The workaround for this is to increase the number of
file descriptors on the Optivity NMS server.
• When you remove an SNMPv3 device using the InfoCenter Edit > Delete
command or by right-clicking an object and choosing Delete from the
shortcut menu, Optivity NMS does not remove the SNMPv3 trap receiver
entry for the Optivity NMS management station. (CR Q00869894)
The workaround for this issue is: Before deleting the device, unmanage the
device by right-clicking it and choosing Unmanage from the shortcut menu.
• If a new Optivity NMS user opens InfoCenter for the first time while
Autotopology discovery is in progress, the InfoCenter folder tree may be
blank. Subsequent launches of InfoCenter by the same user will show the
same problem.
To fix this issue if it occurs open a command window (Windows) or a terminal
window (UNIX) on the Optivity NMS server, and execute the following
command:
rm_appdb -d <user_name>
Where <user_name> is the user name for the Optivity NMS user
experiencing the problem. Next, restart the InfoCenter client.
(CR Q00876856)

Release Notes for Optivity NMS 10.3

12

OmniView

The following are open issues with the OmniView application:

• OmniView does not display Ethernet (ENET) segment information correctly.

(CR Q00041583)
In some cases, only one or two segment summaries are displayed and one or
two segments are missing. However, the segment summary displays correctly
when you open the individual segments.
For token ring, the summary does not contain any content. However, the
segment summary displays correctly when you open the individual segments.
• When you attempt to create a customized statistics pane for an RMON device
as described in the section “Creating a customized statistics pane” on page
490 of Using Optivity NMS 10.3 Applications, the OmniView process on the
Optivity NMS server terminates abruptly. When this happens, you must close
and then restart the OmniView client application. (CR Q00862922)
• When you save an OmniView workspace that contains empty panes (for
example, for a device that is not configured to report certain statistics to
OmniView), and then load the workspace, the OmniView client application
may hang. When this happens, you must close and then restart the OmniView
client application. (CR Q00882465)
• Under Windows, OmniView is case sensitive regarding login names. When
you login as “Administrator” and customize panes, and then later login as
“administrator,” the panes you customized are no longer available. The
workaround for this issue is to always use the same case when logging into
Optivity NMS applications. (CR Q00982793)
• When you choose the option to identify devices by their DNS names, the
device labels in the navigation pane for MCS-5100 servers are blank.
(CR Q01018119)

MView

The following are open issues with the MView application:

• The Timestamp column of the MView history pane displays the relative time
when the statistics were observed. In this case, time is displayed as days,
hours, minutes, and seconds elapsed since the device was last reset. MView
does not show the absolute time. (CR Q00042281)

205970-H
 13

• Alteon devices do not support standard RMON MIBs. (CR Q00068588)

When you start MView against an Alteon device, MView displays the
following error message:
Unable to Map Slot Port to Interface.

• You may not be able to start MView from InfoCenter against Business Policy
Switch 2000 devices. You can start MView from the command line against
these devices by specifying the interface index as shown below.
(CR Q00428554)

mview -I <ip_ddress> -X <interface_id> -Q <operation_type>

For more information about starting MView from the command line, see
Using Optivity NMS 10.3 Applications.
• When you choose Options > Display Label > Display Sys Name to display the
system name of the device, the system name does not display. Instead, the
device IP address in the navigation pane becomes blank. (CR Q00882709)

Fault System

The following are open issues with the Fault Summary application, the Fault
Correlator service or daemon, and Superping:

• When launching Fault Summary from the command line, faults reported by
devices outside the user’s seeds are displayed. The expected behavior would
be to display only faults reported by devices within the seeds in the user’s
database view. Fault Summary behaves as expected when launched from
InfoCenter. (CR Q00585674)
• When changing the trap purge cycle and/or syslog purge cycle interval, the
change takes effect only after the completion of the current purge cycle.
(CR Q00601002)
• When you open Fault Summary on Succession 1000 and Meridian 1 IP
telephony devices, the F_NewAlarm_Critical fault shows up as low-severity
(yellow), and the F_NewAlarm_Minor fault shows up as high-severity (red).
(CR Q00880932)
To fix this issue:
1 Open the following file in a text editor:
LNMSHOME/apps/fc/trapspecs/cse1ktraps.txt

Release Notes for Optivity NMS 10.3

14

2 In the group of lines for T_NewAlarm_Critical, find the line containing the
following text:
TRAP_IDENT_CHECK {INT_EQ($VarBind[3],1)}
3 Change the line to:
TRAP_IDENT_CHECK {INT_EQ($VarBind[3],3)}
4 In the group of lines for T_NewAlarm_Minor, find the line containing the
following text:
TRAP_IDENT_CHECK {INT_EQ($VarBind[3],3)}
5 Change the line to:
TRAP_IDENT_CHECK {INT_EQ($VarBind[3],1)}
6 Save the file.
7 Stop and restart the Fault Correlator.
See the section “Stopping and starting services or daemons” on page 861
of Using Optivity NMS 10.3 Applications for instructions on stopping and
starting fault correlator services or daemons.
• Fault summary shows “interface unreachable” faults for non-management
interfaces on Contivity IP-VPN devices. Also, InfoCenter shows
corresponding alarms for these interfaces. (CR Q00794573)(CR Q01009028)
The workaround for this issue is to unmanage each Contivity
non-management interface as described in the section “Unmanaging and
managing interfaces” on page 355 of Using Optivity NMS 10.3 Applications.
• When you view faults for an MCS 5100 device that has been declared
unmanaged, the faults show up as active. The intended functionality is for the
faults to be unmonitored when the device is declared unmanaged.
(CR Q00879785)
• Trap purge does not work on UNIX systems on which Optivity NMS is
integrated with network management platforms such as NetView or
OpenView. (CR Q01023648)
• Fault script customizations created in Optivity NMS 10.2 are not migrated to
Optivity NMS 10.3. (CR Q01000095)

205970-H
 15

Device Inventory Viewer

The following are open issues with Device Inventory Viewer application:

• When you synchronize the asset database, sometimes the synchronization

process halts prematurely. The synchronization process normally takes
between 30 minutes and an hour. When you encounter this issue, you will see
that the progress numbers in the status bar do not increment. If this occurs,
restart the database synchronization by clicking on the Synchronize button on
the Device Inventory Viewer toolbar. (CR Q00883606)
• When you view device properties for MCS 5100 server or a Contivity IP-VPN
device, the agent version and SNMP version are shown incorrectly.
(CR Q00873754)(CR Q00873880)

Database Admin Tool

The following are open issues with the Database Admin Tool application:

• The trap registration enable and disable selection is lost after the Optivity
NMS database is reset. The Optivity NMS 10.3 factory default database is
installed with Autotrap Registration enabled for all devices on the network.
You can disable this option by executing input_db_contents on
AppControlDB database with mon_def_no_treg.txt file found under
$LNMSHOME/apps/appcontrol. (CR Q00427844)
For example, do one of the following:
— For Windows, enter the following command on one line:
%LNMSHOME%\bin\input_db_contents -db AppControlDB %LNMSHOME%\apps
\appcontrol\mon_def_no_treg.txt
— For UNIX, enter the following command on one line:
$LNMSHOME/bin/input_db_contents -db AppControlDB $LNMSHOME/apps
/appcontrol/mon_def_no_treg.txt
• When you use the Database Admin Tool to stop and restart Oracle, you cannot
view the MibDB database after the restart. The workaround for this issue is to
close and restart the Database Admin Tool after you stop and restart Oracle.
(CR Q00886298)

Release Notes for Optivity NMS 10.3

16

Browser issues

The following are open issues regarding starting Optivity NMS applications in a
Web browser:

• All platforms—When a browser window is resized, all Optivity NMS applets

are resized (Internet Explorer) or reloaded (Netscape*). In this case, the
browser window turns white for a period of time. (CR Q00320099)
• Remote selection does not work correctly between InfoCenter and OmniView
in a Web browser. (CR Q00600093)
• If you use Netscape as your preferred Web browser in a Windows 2000 or
Windows 98 environment, you must add it to the Optivity NMS 10.3 path
statement in the Windows 98 AUTOEXEC.BAT file. The default browser
setting is Internet Explorer. To use Netscape, edit the
%lnmshome%\conf\opcl_win.cnf file, and change DEFAULT_BROWSER
from IExplore to Netscape.

Optivity Integration Toolkit (OIT)

The drive or partition defined by the $OITHOME (UNIX) or %OITHOME%

(Windows) environment variable must have a minimum of 3 GB of free space to
successfully install OIT packages.

This space is used to back up the current Optivity NMS databases, before updating
the databases with OIT package data. If the OIT update process encounters an
error or fails for some reason, you can restore the backed up databases.

You can also set the OITBACKUPDIR environment variable to specify a database
backup directory that has adequate disk space.

205970-H
 17

Platform integration
• After Optivity NMS is uninstalled, if you start the NetView* platform
manager, the system displays error messages when opening the NetView
maps, and the NetView console does not open.
To start NetView without encountering error messages, before uninstalling
Optivity NMS:
1 From the NetView console menu bar, click Options > Console Settings.
2 Click When a Map is Opened.
3 Change the default setting from “Open the last set of submaps” to “Open
the home submaps.”
A workaround to this problem is to remove existing NetView topology
database and re-discover the network again.
• When you use the HP OpenView Remote Console to connect with an
OpenView server that is integrated with Optivity NMS, the Remote Console
menu items for Optivity NMS applications don’t work. (CR Q01015201)

Multicast issues
• In InfoCenter, when you add or remove a multicast session from the watch
list, you must manually refresh the folder view in order to show the changed
status for the IsWatched parameter. (CR Q00879677)
• In InfoCenter, when you save a baseline while Autotopology protocol
discovery is in progress, it will result in an invalid baseline. The workaround
for this issue is to open AutoTopology Manager and ensure that multicast
discovery is not in progress before saving a baseline.
(CR Q00830499)(CR Q00885412)
• In InfoCenter, when using the save baseline feature (Tools > Configuration >
Save Baseline) on Windows, you must select less than six multicast sessions.
Otherwise, the background process fails to exit normally. (CR Q00602758) If
this happens, use the Windows Task Manager to find the savebaseline
process and stop it.

Release Notes for Optivity NMS 10.3

18

• Clearing multicast status events may cause the events to appear incorrectly in
the InfoCenter Multicast Status window. You may observe this issue in any of
three ways: (CR Q00880852)
— If Multicast Status windows are opened from both InfoCenter and
AutoTopology Manager on any client machines of the same Optivity
NMS server, and the AutoTopology Manager user clears events in the
Multicast Status window, the InfoCenter Multicast Status window may
still show the cleared events. The intended functionality is to gray out the
cleared events.
— If you open the AutoTopology Manager window Preferences dialog box
Protocol tab and change the Multicast baseline comparison mode, the
InfoCenter Multicast Status window will still show all the events. The
intended functionality is to gray out all the events.
— If you open the AutoTopology Manager window Auto-rediscovery dialog
box Multicast tab and disable multicast auto-rediscovery, the InfoCenter
Multicast Status window will still show all the events. The intended
functionality is to gray out all the events.
• When Autotopology discovers changes in the multicast network, it sometimes
fails to open the Multicast Status window to alert you to the change.
(CR Q00973889)

IP Telephony issues
• If FTP communication between the Optivity NMS management station and a
Succession 1000 signaling server fails during Autotopology discovery, then
the Succession 1000 system is discovered as a Meridian 1 VOIP system. If
you double-click on the VOIP system in the IP Telephony folder, only the call
server is shown in the traversal view; the signaling server is absent. The
Succession 1000 signaling server and call server are discovered, and are
placed in the /Resources/Subnets folder.
• If FTP communication between the Optivity NMS management station and an
ITG line card fails during Autotopology discovery, the ITG line card will not
be discovered as a component of the VOIP system. If you double-click on the
VOIP system in the IP Telephony folder, only the call server is shown in the
traversal view; the ITG line card is absent. The ITG line card is discovered,
and is placed in the /Resources/Subnets folder.

205970-H
 19

One possible cause for this issue is that the FTP session limit for the ITG line
card has been reached. In this case, telnet to the ITG line card, issue the
cardReset command, and then run Autotopology rediscovery for the VOIP
system.

Agent support
For information on the new and existing agent support for Optivity NMS 10.3, see
Agent Support for Optivity NMS 10.3 (Part number 216729-B). This document is
available on the Internet at the Nortel Networks Web site. Go to the
www.nortelnetworks.com/documentation URL. Choose the Optivity product
family, and then click the Documentation link for Optivity Network Management
System.

Optivity NMS application and product support matrix

This section contains a matrix showing Optivity NMS applications and the Nortel
Networks products they support. Device OIT files that were available at the time
of this release have already been integrated in Optivity NMS 10.3 and can be
listed using the command dmt -I, or with the OIT Administration Tool
(oitadmintool). The readme files for those OIT files are also installed, and list
any known limitations in supporting those new device agents.

The following designations are used in Table 1.

Designation Meaning

Y Yes, support provided.

N No, not supported.
D Discovery of links is not performed.
P Passive (If module is present, LANarchitect will not support it, but it will
function with other supported modules present in the chassis.)
N/A Not applicable.

Release Notes for Optivity NMS 10.3

20

Table 1 Optivity NMS 10.3 application and product support matrix

Module or Component

Fault Correlator, Summary

Device Inventory Viewer

AutoTopology Manager
Model Number or

TD Continuity Test
Expanded View™
Agent Version

InfoCenter

OmniView

Call View

Multicast
MView
Passport
1102 Y Y Y Y N N N N Y N

1108 Y Y Y Y N N N N Y N

1202 Y Y Y Y N N N N Y N

1216 Y Y Y Y N N N N Y N

1216TF Y Y Y Y N N N N Y N

1250 Y Y Y Y N N N N Y N

Passport 1424T Y Y Y Y N Y N N Y N

Passport 1612G Y Y Y Y N Y N N Y N

Passport 1624G Y Y Y Y N Y N N Y N

Passport 1648T Y Y Y Y N Y N N Y N

Passport (Accelar) 1051 Y Y Y Y N N N N Y N

Passport (Accelar) 1050 Y Y Y Y N Y N N Y N

Passport 8100 v3.2.0, v3.2.4, Y Y Y Y N Y Y N Y N

v3.3.0, v3.3.2, v3.3.4, v3.5.0,
v3.5.1
Passport 8300 Y Y Y Y N Y N N Y N

Passport 8600 v3.2.0, v3.2.4, Y Y Y Y N Y Y N Y N

v3.3.0, v3.3.2, v3.3.4, v3.5.0,
v3.5.1
Centillion
C100 24-port TM Y Y Y Y N Y N N Y N

57622-MM57622-SM Y Y Y Y Y Y P N Y N

57622-MM OC-12C Y Y Y Y Y Y P N Y N

5720-31/5720-4 MDA Y Y Y Y Y Y P N Y N

205970-H
 21

Table 1 Optivity NMS 10.3 application and product support matrix (continued)

Module or Component

Fault Correlator, Summary

Device Inventory Viewer

AutoTopology Manager
Model Number or

TD Continuity Test
Expanded View™
Agent Version

InfoCenter

OmniView

Call View

Multicast
MView
Contivity IP-VPN
Contivity 600 Y Y Y Y N N N N Y N

Contivity 1010 Y Y Y Y N N N N Y N

Contivity 1050 Y Y Y Y N N N N Y N

Contivity 1100 Y Y Y Y N N N N Y N

Contivity 1500 Y Y Y Y N N N N Y N

Contivity 1600 Y Y Y Y N N N N Y N

Contivity 1700 Y Y Y Y N N N N Y N

Contivity 2500 Y Y Y Y N N N N Y N

Contivity 2600 Y Y Y Y N N N N Y N

Contivity 2700 Y Y Y Y N N N N Y N

Contivity 4600 Y Y Y Y N N N N Y N

Contivity 5000 Y Y Y Y N N N N Y N

Contivity Branch Access Y Y Y Y N N N N Y N

OPTera Metro
OPTeraMetro ESU 1200 Y Y Y Y N Y N N Y Y

OPTeraMetro ESU 1400 Y Y Y Y N Y N N Y Y

OPTeraMetro ESU 1450 Y Y Y Y N Y N N Y Y

OPTeraMetro ESU 1800 Y Y Y Y N Y N N Y Y

OPTeraMetro 8000 Y Y Y Y N Y N N Y N

OPTera Packet Edge Y Y Y Y N N N N Y N

BayStack Shared Media and System 5000

250 Y Y Y Y N Y N N Y N

253 Y Y Y Y N Y N N Y N

5660/5665 Y Y Y Y N Y P1 N Y N

Release Notes for Optivity NMS 10.3

22

Table 1 Optivity NMS 10.3 application and product support matrix (continued)

Module or Component

Fault Correlator, Summary

Device Inventory Viewer

AutoTopology Manager
Model Number or

TD Continuity Test
Expanded View™
Agent Version

InfoCenter

OmniView

Call View

Multicast
MView
5620-FX Y Y Y Y N Y P1 N Y N

5616SA w/5611 Y Y Y Y2 N Y Y N Y N

660/650 Y N N D N N N N Y N

BayStack Switches
303 Y Y Y Y N Y N N Y N

325-24T, 325-48T Y Y Y Y N Y N N Y N

350-12T, 350-24T Y Y Y Y3 N Y N N Y N

380-24F, 380-24T Y Y Y Y N Y N N Y N

410 Y Y Y Y N Y N N Y N

420 Y Y Y Y N Y N N Y N

425-24T, 425-48T Y Y Y Y N Y N N Y N

450-12T, 450-24T Y Y Y Y3 N Y N N Y N

450 Gigabit Interface Y Y Y D N Y N N Y N

460 Y Y Y Y N Y N N Y N

470-24T, 470-48T Y Y Y Y N Y N N Y N

5510-24T, 5510-48T Y Y Y Y N Y N N Y N

BPS 2000 Y Y Y Y N Y N N Y N

Remote Access
5399 Y Y Y D N Y P N Y N

RMON Probe
E202, E402, ET1100 Y N N Y N N Y N Y N

FE2100, FE2200, FE2400T, Y N N Y N N Y N Y N

FE2400F
T101, T202 Y N N D N N Y N Y N

FD2100, FD2200 Y N N D N N Y N Y N

205970-H
 23

Table 1 Optivity NMS 10.3 application and product support matrix (continued)

Module or Component

Fault Correlator, Summary

Device Inventory Viewer

AutoTopology Manager
Model Number or

TD Continuity Test
Expanded View™
Agent Version

InfoCenter

OmniView

Call View

Multicast
MView
FE1100, 10/100M Pocket Probe Y N N Y N N Y N Y N

Probe Agent v6.0 Y N N Y N N N N Y N

E100, E101, E404 Y N N Y N N Y N Y N

FE100, FE200 Y N N Y N N Y N Y N

F100, F200 Y N N D N N Y N Y N

Router
Nautica 4000 Y Y Y D N N N N Y N

57454 N N N N N N N N Y N

5782 VNR Y Y Y Y Y Y Y N Y N

BayRS Y Y Y Y N N N Y Y N

Wireless LAN
AP2220 Y Y Y Y N N N N Y N

AP2221 Y Y Y Y N N N N Y N

Security Switch 2250 Y N N Y N N N N Y N

Other modules
5625 N/ Y Y N/A5 N Y P N Y N
A5
5424 N/ Y Y N/A5 N Y P P Y N
A5
5525HD N/ Y Y N/A5 N Y P P Y N
A5
AS1704004 N/ Y Y N/A5 N Y P P Y N
A5
C100 16-Port
Centillion 20 Y Y Y N N Y N N Y N
24-Port TR Switch
AS130401x C100 OC-12 MCP Y Y Y N N Y N N Y N

BayStack 254 Y Y Y Y N Y N N Y N

Release Notes for Optivity NMS 10.3

24

Table 1 Optivity NMS 10.3 application and product support matrix (continued)

Module or Component

Fault Correlator, Summary

Device Inventory Viewer

AutoTopology Manager
Model Number or

TD Continuity Test
Expanded View™
Agent Version

InfoCenter

OmniView

Call View

Multicast
MView
BayStack 255 Y Y Y Y N Y N N Y N

Alteon 180E Y Y Y Y N N N Y Y N

Alteon 184 Y Y Y Y N N N Y Y N

Alteon AD3 Y Y Y Y N N N Y Y N

Alteon AD4 Y Y Y Y N N N Y Y N

Alteon 2224 Y Y Y Y N N N Y Y N

Alteon Switched Firewall (ASF) Y Y Y Y N N N N N N

Optivity Policy Server Y Y Y N N N N N N N

1 No VLAN MIB in the agent.

2 Model 5616 only, Model 5611 support added in Optivity NMS 9.0.
3 With the 2.0 version of the agent.
4 Model 5745 has no SNMP agent and no communication with CMB.
5 Host module.

Where to find more information

This section tells you where to look to find more information about
Optivity NMS.

Related publications
For more information about using Optivity NMS 10.3, refer to the Optivity
NMS 10.3 online Help or the following publications.

• Using Optivity NMS 10.3 Applications (Part number 207569-F)

• Installing and Administering Optivity NMS 10.3 (Part number 205969-H)

205970-H
 25

• Quick Installation and Startup of Optivity NMS 10.3 for Windows*

(Part number 217232-A)
• Quick Installation and Startup of Optivity NMS 10.3 for Solaris
(Part number 217233-A)
• Quick Installation and Startup of Optivity NMS 10.3 for HP-UX
(Part number 217234-A)

Printed technical manuals

You can print selected technical manuals and release notes free, directly from the
Internet. Go to the www.nortelnetworks.com/documentation URL. Find the
product for which you need documentation. Then locate the specific category and
model or version for your hardware or software product. Use Adobe* Acrobat
Reader* to open the manuals and release notes, search for the sections you need,
and print them on most standard printers. Go to Adobe Systems at the
www.adobe.com URL to download a free copy of Acrobat Reader.

Windows and UNIX systems supported

Optivity NMS supports server and client systems in Solaris, HP-UX, and
Windows environments. Detailed hardware and software requirements for these
environments are listed in Installing and Administering Optivity NMS 10.3.

How to get help

If you purchased a service contract for your Nortel Networks product from a
distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance.

If you purchased a Nortel Networks service program, contact Nortel Networks

Technical Support. To obtain contact information online, go to the
www.nortelnetworks.com/cgi-bin/comments/comments.cgi URL, then click on
Technical Support.

Release Notes for Optivity NMS 10.3

26

From the Technical Support page, you can open a Customer Service Request
online or find the telephone number for the nearest Technical Solutions Center.
If you are not connected to the Internet, you can call 1-800-4NORTEL
(1-800-466-7835) to learn the telephone number for the nearest Technical
Solutions Center.

An Express Routing Code (ERC) is available for many Nortel Networks products
and services. When you use an ERC, your call is routed to a technical support
person who specializes in supporting that product or service. To locate an ERC for
your product or service, go to the http://www.nortelnetworks.com/help/contact/
erc/index.html URL.

205970-H