Using Optivity NMS 10.3 Applications: Part No. 207569-F November 2004 4655 Great America Parkway Santa Clara, CA 95054

Part No.
207569-F
November 2004
4655 Great America Parkway

Santa Clara, CA 95054
Using Optivity NMS 10.3

Applications
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, Bay Networks, BayStack, Centillion, Meridian, Optivity,
Passport, and Unified Networks are trademarks of Nortel Networks.
Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated.
HP and OpenView are trademarks of Hewlett-Packard Corporation.
Oracle is a trademark of Oracle Corporation.
Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation.
Netscape Navigator is a trademark of Netscape Communications Corporation.
Solaris is a trademark of Sun Microsystems, Incorporated.
UNIX is a registered trademark of X/Open Company Limited.
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.
207569-F
3
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.
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

agreement
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.
Using Optivity NMS 10.3 Applications

4
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
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.
207569-F
5
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.

6
207569-F
7
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Hard-copy technical manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Flexible architectural approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

What's new in Optivity NMS 10.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Optivity NMS 10.3 applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
OmniView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Path Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
TD Continuity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Fault Summary/Fault Correlator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Call View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Legacy applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Administrative functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Community Strings Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Monitor Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

8 Contents
OIT Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Disdevice and dislink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Integration with Optivity Telephony Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
How this manual is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Using online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Send us feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Chapter 2
Specifying access to Optivity NMS applications with Access Control
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Access Control Administration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Getting started with Access Control Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Access Control Administration features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Optivity NMS access administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Access permission tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Starting Access Control Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Access Control Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Menu bar and toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Optivity Users pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Permission pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Permission Groups pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Working with Access Control Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Enabling and disabling access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Adding Optivity NMS users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Removing Optivity users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Setting user permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Changing permission settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Attaching and detaching permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Adding permission groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Attaching permission groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Changing permission groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Assigning view domains to ONMS users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Assigning services to ONMS users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Changing the look and feel of the window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
207569-F
Contents 9
Troubleshooting Access Control Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Resolving problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Chapter 3
Specifying access to devices with the Community Strings Editor . . . . . 101
Community Strings Editor overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Getting started with the Community Strings Editor . . . . . . . . . . . . . . . . . . . . . . . . . . 102
About community strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Default community strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
IP address syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Understanding wildcards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
About user security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Understanding user security services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Starting the Community Strings Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Access permissions for Community Strings Editor . . . . . . . . . . . . . . . . . . . . . . . 109
Community Strings Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Menu bar and toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Individual view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Working with the Community Strings Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Working with community strings entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Adding a new community string entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Modifying a community string entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Deleting a community string entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Changing the order of community string entries . . . . . . . . . . . . . . . . . . . . . . 121
Resetting changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Refreshing the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Saving changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Working with SNMPv3 users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Adding SNMPv3 users to an entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Modifying an SNMPv3 user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Deleting an SNMPv3 user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

10 Contents
Selecting SNMPv1 traps if SNMPv3 trap registration fails . . . . . . . . . . . . . . 128

Working with Telnet and SSL settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Configuring Telnet settings for an entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Configuring SSL settings for an entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Importing and exporting community strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Importing a community strings file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Understanding Timeout value conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Exporting a community strings file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Troubleshooting the Community Strings Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Chapter 4
Discovering your network with AutoTopology Manager . . . . . . . . . . . . . 137
AutoTopology Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Getting started with the AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Starting AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
AutoTopology Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Access Control for AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Understanding the age-out process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Understanding discovery seeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Working with AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Discovering the network with AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . 148
Setting network discovery parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Setting discovery options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Starting and stopping topology discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Scheduling rediscovery with Auto Rediscovery . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Detecting multicast changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Viewing topology discovery details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Working with discovery seeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Creating a new discovery seed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Limiting discovery using IP ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Viewing or editing an existing discovery seed . . . . . . . . . . . . . . . . . . . . . . . . 160
Deleting a discovery seed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Working with view domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
207569-F
Contents 11
Creating view domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Editing or deleting view domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Viewing view domain information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Using On-Demand discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Working with Range Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Enabling Range Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Entering Range Ping IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Using Routerless discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Managing connections with the Out-of-band Editor . . . . . . . . . . . . . . . . . . . . . . . 171
In-band and out-of-band Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Identifying out-of-band interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Validating WLAN access points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Customizing the AutoTopology Manager window . . . . . . . . . . . . . . . . . . . . . . . . 174
Setting the look and feel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Hiding or displaying the toolbar, status bar, and auto-rediscovery status area 175
Troubleshooting the AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Chapter 5
Navigating the InfoCenter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
InfoCenter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Getting started with InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
About InfoCenter user access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Starting InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Parts of the InfoCenter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Folder tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Folder pane Shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Displaying or hiding the folder pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Contents pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Folder views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Folder view layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Folder view presentation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Folder view layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Opening a folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Folder view shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Object shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

12 Contents
Displaying or hiding the view summary details . . . . . . . . . . . . . . . . . . . . . . . 202

Saving changes to graphical folder views with Auto Save . . . . . . . . . . . . . . . 203
Navigating between Auto-Save settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Enabling and disabling Auto Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Changing Auto Save between Yes and No . . . . . . . . . . . . . . . . . . . . . . . 205
Folder view preferences and defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Changing the default folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Changing the current view format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Changing the current view layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Changing the current view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Displaying or hiding icon labels in folder views . . . . . . . . . . . . . . . . . . . . 210
Displaying DNS or system names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Displaying or hiding a background image . . . . . . . . . . . . . . . . . . . . . . . . 212
Setting InfoCenter print options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Closing a folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Organizing information in tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Displaying or hiding tabular view grid lines . . . . . . . . . . . . . . . . . . . . . . . 213
Sorting table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Resizing table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Repositioning table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Hiding table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Opening InfoCenter menus in a Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Toolbar panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Stacking toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Dragging a toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Floating and docking a toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Opening and closing toolbars in the toolbar panel . . . . . . . . . . . . . . . . . . . . 226
Resizing the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
InfoCenter toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Displaying or hiding the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Advanced graphic viewing tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Using the select tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Selecting an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Dragging an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
207569-F
Contents 13
Opening an object shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Resizing an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Using the Zoom tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Zooming in or out on a graphic view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Using marquee zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Using interactive zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Using custom zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Using fit in window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Pan view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Follow link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Using the overview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Linking nodes in the graphical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Creating a link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Cancelling a link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Using the InfoCenter launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Displaying or hiding the launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Displaying or hiding a launchpad tools and text labels . . . . . . . . . . . . . . . . . 245
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Displaying or hiding the status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Displaying a legend of object icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Viewing downloaded plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Viewing available services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
About Optivity integrated applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Recognizing application categories in InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . 250
Recognizing applications you can start from InfoCenter . . . . . . . . . . . . . . . . . . 251
Starting applications from the Admin menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Starting applications from the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Starting applications from the launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Starting applications from the shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Chapter 6
Organizing your network with InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . 255
About folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Predefined folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Discovering your network resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

14 Contents
Adding and removing view domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Rediscovering network resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
About folder properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Folder scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Object name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Object type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Object subtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Device type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Subnet assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Folder filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Filter attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Relational operators for filter attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Logical operators for filter attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Presentation tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Folder details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Creating and configuring custom folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Creating a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Renaming a custom folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Configuring search properties for custom folders . . . . . . . . . . . . . . . . . . . . . . . . 270
Configuring presentation properties for custom folders . . . . . . . . . . . . . . . . . . . 273
Selecting a folder background color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Working with folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Opening a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Saving a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Saving a folder as an image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Increasing the memory allocation using the Java Control Panel . . . . . . . . . . 280
Decreasing the size of the image being saved . . . . . . . . . . . . . . . . . . . . . . . 280
Selecting print setup options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Previewing a page before printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Printing a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Saving Custom folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Opening a customized folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Creating an undo aged out objects folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Copying folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
207569-F
Contents 15
Copying objects between folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Exporting folder contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Deleting a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Sharing custom folder queries with other InfoCenter users . . . . . . . . . . . . . . . . . 291
Sharing or unsharing a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Copying a shared folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Exporting a folder definition to a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Importing a folder definition from a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Resetting a folder view to factory defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Working with objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Object attributes used in topology processes . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Object attributes used in InfoCenter and Fault Summary processes . . . . . . . . . 297
Viewing or modifying object properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Viewing object details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Creating a new object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Cutting an object from a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Pasting an object into a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Recovering an object cut from a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Removing an object with age out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Restoring an object removed with age out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Permanently deleting an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Launching Optivity NMS applications from multiple objects . . . . . . . . . . . . . . . . 305
Displaying traversal views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Using the expand by hops feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Expanding by hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
About remote selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Using remote selection between InfoCenter views . . . . . . . . . . . . . . . . . . . . . . . 309
Using remote selection between Optivity NMS applications . . . . . . . . . . . . . . . . 310
Using Net Aware Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Working with InfoCenter search functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Finding an object in a folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Finding an object in the Optivity NMS database . . . . . . . . . . . . . . . . . . . . . . . . . 312
Visualizing MLT and SMLT configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Troubleshooting InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

16 Contents
Chapter 7
Monitoring network health with InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . 317
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Selecting fault management categories for alarm monitoring . . . . . . . . . . . . . . . . . . 318
About the Alarms folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Color coding alarm status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Alarm colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Selecting a color for an alarm level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Enabling status color propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Calculating fault status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Fault status criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Fault correlator status calculation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Choosing the fault management calculation method . . . . . . . . . . . . . . . . . . . . . . 327
Unmanaging devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Unmanaging and managing interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Chapter 8
Managing multicast sessions and protocols with Optivity NMS . . . . . . . 329
Discovering multicast elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Manually rediscovering multicast sessions . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Manually rediscovering a single session . . . . . . . . . . . . . . . . . . . . . . . . 331
Manually rediscovering multiple sessions . . . . . . . . . . . . . . . . . . . . . . . . 332
Selecting sessions for auto-rediscovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Selecting or deselecting a single multicast session for auto-rediscovery 333
Selecting or deselecting multiple multicast sessions for auto rediscovery 334
Working with multicast sessions and session baselines . . . . . . . . . . . . . . . . . . . . . . 335
Understanding active and inactive baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Saving multicast session baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Deleting session baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Viewing session baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Listing the baselines for a multicast session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Designating baselines as active or inactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Comparing multicast session baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Comparing a multicast session with the active baseline . . . . . . . . . . . . . . . . 343
Comparing any baseline with its multicast session . . . . . . . . . . . . . . . . . . . . 345
207569-F
Contents 17
Comparing multicast session baselines with each other . . . . . . . . . . . . . . . . 345

Working with multicast view baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Saving multicast session view baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Saving multicast routing view baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Comparing multicast view baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Comparing multicast view baselines with each other . . . . . . . . . . . . . . . . . . 349
Comparing multicast view baselines with the current network . . . . . . . . . . . 351
Exporting and importing baseline data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Chapter 9
Managing IP Virtual Private Networks with Optivity NMS . . . . . . . . . . . . 355
Discovering IP-VPN elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Visualizing IP-VPN devices and tunnels with InfoCenter . . . . . . . . . . . . . . . . . . . . . . 356
Viewing IP-VPN devices and VPN tunnels in the IP-VPN folder . . . . . . . . . . . . . 356
Viewing IP-VPN devices, physical links, subnets and devices in the physical layer view
357
Viewing IP-VPN devices and VPN tunnels in the IP-VPN Service view . . . . . . . 357
Viewing performance statistics for IP-VPN elements . . . . . . . . . . . . . . . . . . . . . . . . . 358
Viewing performance statistics for IP-VPN devices in OmniView . . . . . . . . . . . . 358
Viewing performance statistics for VPN tunnels . . . . . . . . . . . . . . . . . . . . . . . . . 358
Chapter 10
Managing IP telephony systems with Optivity NMS . . . . . . . . . . . . . . . . . 359
Discovering IP telephony devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Visualizing IP telephony elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Viewing IP telephony systems with InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Viewing parts of an IP Telephony system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Viewing software components of an IP Telephony system . . . . . . . . . . . . . . . . . 363
Viewing physical links between IP Telephony devices and other data devices . . 364
Viewing VLAN membership for IP telephony components . . . . . . . . . . . . . . . . . 365
Viewing performance statistics for IP telephony systems and components . . . . . . . . 366
Viewing performance statistics for an IP telephony system . . . . . . . . . . . . . . . . . 366
Viewing performance statistics for components of an IP telephony system . . . . 367

18 Contents
Chapter 11
Managing virtual private LAN services devices with Optivity NMS . . . . 369
VPLS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Discovering VPLS elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Visualizing VPLS elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Viewing VPLS services in InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Viewing VPLS devices, transport domains, and VPLS links in InfoCenter . . . . . 372
Transforming an InfoCenter folder view to the VPLS layer . . . . . . . . . . . . . . . . . 372
Viewing VLPS elements on the InfoCenter physical layer . . . . . . . . . . . . . . . . . . 373
Viewing VLPS elements on the InfoCenter Data Link layer . . . . . . . . . . . . . . . . . 374
Viewing User Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Viewing VPLS services for a UNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Testing Transport Domain Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Chapter 12
Testing Transport Domain Continuity with TD Continuity Test . . . . . . . . 379
TD Continuity Test overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Getting started with TD Continuity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Starting TD Continuity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
TD Continuity Test window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Test table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Working with TD Continuity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Working with test entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Adding a new test entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Editing a test entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Deleting a test entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Starting and stopping a TDC test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Viewing TDC test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Understanding TDC test errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Changing the look and feel of the window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Exporting test configurations to a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Exporting test results to a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
207569-F
Contents 19
Chapter 13
Monitoring devices with OmniView and MView . . . . . . . . . . . . . . . . . . . . 393
OmniView and MView overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

OmniView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Getting started with OmniView and MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Access permissions for OmniView and MView . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Starting OmniView and MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
OmniView and MView command line options . . . . . . . . . . . . . . . . . . . . . . . . 399
OmniView and MView URL options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Guidelines for starting MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
OmniView and MView window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Understanding the navigation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Understanding the monitor pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Understanding the OmniView graph window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
OmniView graph window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Graph window menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Graph window toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Parts of a graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Working with OmniView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Working with network resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Browsing resources with the navigation pane . . . . . . . . . . . . . . . . . . . . . . . . 424
Adding a network resource to the navigation pane . . . . . . . . . . . . . . . . . . . . 425
Finding network resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Listing monitored resources and elements . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Using workspaces to save and restore views . . . . . . . . . . . . . . . . . . . . . . . . 430
Working with existing statistics panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Viewing statistics for a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Viewing statistics with bar indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Reading bar indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Understanding statistics types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Understanding network utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Viewing network utilization for half-duplex operation . . . . . . . . . . . . . . . 437

20 Contents
Viewing network utilization for full-duplex operation . . . . . . . . . . . . . . . . 438

Sorting a table column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Minimizing and maximizing statistics panes . . . . . . . . . . . . . . . . . . . . . . . . . 442
Changing the statistic types displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Selecting table cells for graphing or exporting . . . . . . . . . . . . . . . . . . . . . . . 444
Reordering columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Setting polling parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Closing a statistics pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Viewing information about MIB objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Viewing statistics in a multi-device pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Understanding the conditions for viewing statistics . . . . . . . . . . . . . . . . 448
Understanding the display formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Opening a multi-device pane to view statistics . . . . . . . . . . . . . . . . . . . . 451
Adding other network elements to an open multi-device pane . . . . . . . . 454
Working with custom statistics panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Creating a customized statistics pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Customizing an existing pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Searching for a MIB object by name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Creating a MIB expression for a custom statistics pane . . . . . . . . . . . . . . . . 460
Validating a MIB object or MIB expression . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Working with graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Viewing statistics graphically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Viewing line graph traces separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Combining separated graph traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Rotating line or bar graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Changing the OmniView graph type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Regrouping bar or pie graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Applying or removing a graph legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Viewing graph values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Viewing graphing symbols (line graph only) . . . . . . . . . . . . . . . . . . . . . . . . . 466
Changing the OmniView graph scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Enlarging and shrinking the graph with zoom . . . . . . . . . . . . . . . . . . . . . . . . 467
Scrolling through the graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Displaying information about a data point . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Importing and exporting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
207569-F
Contents 21
Saving statistics with print to file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

Importing statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Exporting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Exporting statistics from the OmniView window . . . . . . . . . . . . . . . . . . . 472
Exporting statistics from a graph window . . . . . . . . . . . . . . . . . . . . . . . . 475
Comparing exported statistics with current statistics . . . . . . . . . . . . . . . . . . 476
Customizing OmniView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Configuring how OmniView displays statistics panes . . . . . . . . . . . . . . . . . . 476
Configuring how OmniView displays resource icons . . . . . . . . . . . . . . . . . . . 477
Configuring how OmniView coordinates sorting and polling . . . . . . . . . . . . . 478
Configuring how OmniView displays MAC addresses . . . . . . . . . . . . . . . . . 479
Configuring how OmniView displays bar indicators . . . . . . . . . . . . . . . . . . . 479
Configuring how OmniView displays graphs . . . . . . . . . . . . . . . . . . . . . . . . . 480
Changing the look and feel of OmniView . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Hiding or displaying the toolbar or status bar . . . . . . . . . . . . . . . . . . . . . . . . 482
Working with unsupported devices and agents . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Error messages for unsupported devices and agents . . . . . . . . . . . . . . . . . . 482
Understanding the error log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Working with RMON and SMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Working with RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Working with RMON Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Working with SMON Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Using OmniView for protocol visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Displaying protocol statistics for a RIP2 domain . . . . . . . . . . . . . . . . . . . . . . 489
Displaying protocol statistics for an OSPF area object . . . . . . . . . . . . . . . . . 490
Displaying protocol statistics for a RIP2 router in the unicast layer . . . . . . . . 492
Displaying protocol statistics for an OSPF router in the unicast layer . . . . . . 493
Displaying protocol statistics for an OSPF ABR link . . . . . . . . . . . . . . . . . . . 494
Displaying protocol statistics for an OSPF ASBR link . . . . . . . . . . . . . . . . . . 495
Displaying protocol statistics for a multicast session object . . . . . . . . . . . . . 496
Displaying protocol statistics for a router in the multicast sessions layer . . . 497
Displaying protocol statistics for a router interface running frame relay . . . . 498
Displaying protocol statistics for a PVC link in the frame relay layer . . . . . . . 500
Displaying protocol statistics for an IP-VPN link . . . . . . . . . . . . . . . . . . . . . . 501
Working with MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

22 Contents
Monitoring RMON and SMON data types with MView . . . . . . . . . . . . . . . . . . . . 502

Segment statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Ethernet segment statistic table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Token ring segment statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Performance history statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Ethernet performance history table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Ethernet fault history table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Token ring performance history table . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Token ring fault history table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
User history table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Protocol distribution statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Network layer (NL) protocol distribution table . . . . . . . . . . . . . . . . . . . . . 508
Application layer (AL) protocol distribution table . . . . . . . . . . . . . . . . . . . 508
Accounting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
VLAN distribution statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Priority distribution statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Viewing with port profile data with MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Troubleshooting OmniView and MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
OmniView error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Resolving problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Verifying that an interface exists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Verifying RMON status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
OmniView known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Chapter 14
Managing network management applications with Application Launch 521
Application Launch overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

Getting started with Application Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Starting Application Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Modify Application Launch dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Working with Application Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Execution Environment command line syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Reserved symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
ParserElement types and syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Special symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
207569-F
Contents 23
Terminal symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

Execution environment syntax production rules . . . . . . . . . . . . . . . . . . . . . . 530
Viewing application support for a resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Viewing applications from Application Launch . . . . . . . . . . . . . . . . . . . . . . . 532
Viewing applications from InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Modifying the launch configuration for an application . . . . . . . . . . . . . . . . . . . . . 534
Adding a new application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Selecting supported network resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Specifying the application execution environment . . . . . . . . . . . . . . . . . . . . . . . 536
Deleting an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Application Launch error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Chapter 15
Specifying the level of statistics gathering with Monitor Options . . . . . 541
Getting started with Monitor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

Starting Monitor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Monitor Options dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Default monitoring options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Network discovery options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Fault management processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Determining monitoring options for objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Working with monitor options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Setting user access for Monitor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Retaining or overriding parent monitoring options . . . . . . . . . . . . . . . . . . . . . . . 548
Customizing monitor options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Editing monitor options defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Troubleshooting Monitor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Chapter 16
Configuring devices with Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . 553
Expanded View overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

Getting started with Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Access permissions for Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Starting Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
How Expanded View displays device information . . . . . . . . . . . . . . . . . . . . . . . . 557

24 Contents
Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

Supported agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Unknown devices and agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Expanded View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Contents pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Front view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Chassis status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Logical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Expanded View shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Management windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Management window menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Management window toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Working with Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Identifying Expanded View Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Selecting Expanded View objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Managing the whole device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Managing Expanded View objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Setting Expanded View preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Starting other Optivity NMS applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Managing faults with Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Monitoring LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Displaying object status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Displaying object diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Resetting an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Disabling or enabling an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Managing device configuration with Expanded View . . . . . . . . . . . . . . . . . . . . . . 581
Displaying an object profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Displaying nodes attached to an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Displaying VLANs and segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Displaying VLANs and segment highlighting . . . . . . . . . . . . . . . . . . . . . . . . 584
Method 1—Viewing all segments at the same time . . . . . . . . . . . . . . . . 584
Method 2—Viewing one segment at a time . . . . . . . . . . . . . . . . . . . . . . 585
Using a trap receiver table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
207569-F
Contents 25
Adding a trap receiver table entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586

Modifying a trap receiver table entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Finding a trap receiver table entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Deleting a trap receiver table entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Viewing performance information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Selecting multiple ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Selecting multiple ports individually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Selecting a range of ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Deselecting multiple ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Configuring multiple ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Troubleshooting Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Chapter 17
Managing ATM traffic with Call View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Call View overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

Getting started with CallView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Supported ATM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Starting Call View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Call View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Object shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Contents area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Call View views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
CallView graphical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
CallView tabular view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
CallCount graphical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
CallCount tabular view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Call Table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
ATM calls supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Color coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Working with Call View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

26 Contents
Using common Call View commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

Adding an ATM object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Stopping a Call View process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Deselecting objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Inverting the selection of objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Interpreting the health status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Cutting an object from a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Deleting an object from a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Clearing ATM objects from a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Copying and pasting ATM nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Finding an object in a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Searching the CallView/CallCount table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Using special search characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Changing the view layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Changing the window environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Expanding by hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Using remote selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Moving the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Displaying objects by DNS name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Setting the DNS name display option . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Setting the DNS name display default . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Working with ATM calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Analyzing CallView calls with Call Delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Filtering ATM calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Working with graphical and tabular views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Displaying a CallView or CallCount graphical view . . . . . . . . . . . . . . . . . . . . 626
Displaying a CallView or CallCount tabular view . . . . . . . . . . . . . . . . . . . . . . 627
Displaying a call table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Resizing tabular columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Repositioning tabular columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Sorting the CallView/CallCount table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Closing a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Working with object attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Displaying the object shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Displaying object attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
207569-F
Contents 27
Displaying link attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

Printing with Call View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Printing a view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Printing the call table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Troubleshooting Call View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Call View messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Chapter 18
Managing events with Fault Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Fault Summary overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Event color codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Getting started with Fault Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Starting Fault Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Access permissions for Fault Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Fault Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Positioning the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Navigation pane and filter tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Contents pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Filter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Filter window toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Filter window status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Working with Fault Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Working with events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Viewing events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Viewing event details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Unmonitoring events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Deleting events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Refreshing displayed events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Using filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Executing filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Paging through filter results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Sorting filter results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

28 Contents
Organizing filters with the filter tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

Adding folders to the filter tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Deleting filters or folders from the filter tree . . . . . . . . . . . . . . . . . . . . . . . . . 655
Saving filters to different locations on the filter tree . . . . . . . . . . . . . . . . . . . . 655
Creating and modifying filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Opening an existing filter for editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Creating a new filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Saving Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Understanding filter elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Understanding logical AND and OR groups . . . . . . . . . . . . . . . . . . . . . . 658
Understanding the NOT operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Understanding property filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Understanding property filter relationships . . . . . . . . . . . . . . . . . . . . . . . 664
Working with filter elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Adding a logical group to a filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Changing the logical group type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Negating the logical group type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Adding a property filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Editing a property filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Deleting a logical group or property filter . . . . . . . . . . . . . . . . . . . . . . . . 668
Event filter example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Working with fault scripts and trap forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Configuring scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Script path guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Script parameter guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Fault script example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Fault name definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Adding a fault script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Deleting a fault script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Configuring trap forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Troubleshooting Fault Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Fault Summary does not start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Fault Summary does not display faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Fault Summary does not display traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
207569-F
Contents 29
Fault Scripts are not getting executed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681

Fault states are not updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Connection to the server is lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Fault management services or daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Names of trap server services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Fault management services in the Windows environment . . . . . . . . . . . . . . 684
Fault management services in the UNIX environment . . . . . . . . . . . . . . . . . 685
Verifying that services or daemons run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Stopping and starting services or daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Stopping services in the Windows NT or Windows 2000 environment . . . . . 687
Stopping daemons in the UNIX environment . . . . . . . . . . . . . . . . . . . . . . . . 688
Starting services in the Windows NT or Windows 2000 environment . . . . . . 689
Starting daemons in the UNIX environment . . . . . . . . . . . . . . . . . . . . . . . . . 690
Viewing debug information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Managing the trap database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Purging traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
Backing up the trap database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Restoring the trap database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Chapter 19
Managing Network Assets with Device Inventory Viewer . . . . . . . . . . . . 695
Device Inventory Viewer overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

Getting started with the Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Starting Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Device Inventory Viewer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Navigation pane and asset tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Access Control for Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Working with Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Viewing asset lists and asset properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Listing members of an asset type or subtype . . . . . . . . . . . . . . . . . . . . . . . . 703
Viewing properties for an asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Editing device properties for an asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Viewing information for a module or port . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Refreshing Device Inventory Viewer displays . . . . . . . . . . . . . . . . . . . . . . . . 708

30 Contents
Checking for updated agent versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

Printing asset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Adding and removing assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Synchronizing the asset database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Manually adding assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
Manually removing assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Exporting asset information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Importing asset information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Working with asset types and properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Adding asset types and sub types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Adding and removing properties for a type . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Adding new properties to an asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Deleting properties from an asset type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Managing the Device Inventory Viewer database . . . . . . . . . . . . . . . . . . . . . . . . 726
Backing up the Device Inventory Viewer database . . . . . . . . . . . . . . . . . . . . 726
Restoring the Device Inventory Viewer database . . . . . . . . . . . . . . . . . . . . . 726
Removing the Device Inventory Viewer database . . . . . . . . . . . . . . . . . . . . . 727
Troubleshooting the Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
Chapter 20
Tracing paths and locating end nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Path Trace overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

Getting started with Path Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Access permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Path Trace terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
About end nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Path Trace information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Working with Path Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Tracing a path between two devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Locating an end node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Starting other Optivity NMS applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Troubleshooting using Path Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Object fault colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Viewing error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
207569-F
Contents 31
Chapter 21
Managing data with the Database Admin Tool . . . . . . . . . . . . . . . . . . . . . 743
Database Admin Tool overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743

Getting started with the Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Access permissions for the Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . 744
Database definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Starting the Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Database Admin Tool window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Database pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Element pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
Working with the Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Working with databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Importing a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Importing a database from the Database Admin Tool database pane . . 753
Importing a database from the Database Admin Tool shortcut menu . . 756
Exporting a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
Exporting a database from the Database Admin Tool database pane . . 758
Exporting a database using the Database Admin Tool shortcut menu . . 760
Deleting databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
Deleting a database using Database Admin Tool . . . . . . . . . . . . . . . . . . 761
Deleting a database at the command line . . . . . . . . . . . . . . . . . . . . . . . 762
Resetting the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Working with elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Retrieving elements of a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
Viewing element properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
Working with database status tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Viewing Optivity NMS status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Viewing Oracle status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Starting and shutting down an Oracle instance . . . . . . . . . . . . . . . . . . . . . . . 767
Troubleshooting Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

32 Contents
Chapter 22
Administering device support using OIT . . . . . . . . . . . . . . . . . . . . . . . . . 769
OIT overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769

Getting started with OIT Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Devices and device management applications . . . . . . . . . . . . . . . . . . . . . . . . . . 771
Obtaining support for new or updated devices and applications . . . . . . . . . . 771
Understanding the OIT installation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
Starting the OIT applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Access permissions for OIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
OIT Administration Tool window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Working with the OIT Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Viewing an inventory of installed OIT files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Viewing an OIT module and trap information . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
Saving the list of installed OIT packages as a text file . . . . . . . . . . . . . . . . . . . . . 779
Installing an OIT package that is already downloaded . . . . . . . . . . . . . . . . . . . . 780
Using the OIT Administration Tool to update installed OIT packages . . . . . . . . . 782
Updating OIT packages using the OIT Administration Tool . . . . . . . . . . . . . . 783
Cancelling an OIT Administration Tool update process . . . . . . . . . . . . . . . . 784
Configuring an FTP proxy server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
Working with oitInstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Installing device support using oitInstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Adding device support through oitInstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
Launching a device management application . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
Device support added in Optivity NMS 10.3 using OIT . . . . . . . . . . . . . . . . . . . . . . . 788
Troubleshooting OIT Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
Chapter 23
Managing network access with BaySecure LAN Access. . . . . . . . . . . . . 793
BaySecure LAN Access overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793

Getting started with BaySecure LAN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
BaySecure security components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
Hardware functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Agent functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Software functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
207569-F
Contents 33
BaySecure security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796

Understanding intrusion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
Understanding eavesdrop protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Understanding autolearn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Understanding node access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Allowed nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Allowed nodes plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Access permissions for BaySecure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
Starting BaySecure LAN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
BaySecure LAN Access window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
BaySecure menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
BaySecure toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Device information table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
Working with BaySecure LAN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
BaySecure security process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Viewing the latest information in the BaySecure window . . . . . . . . . . . . . . . . . . . 811
Viewing device properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Saving security configuration changes to device NVRAM . . . . . . . . . . . . . . . . . . 811
Setting device SNMP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Viewing device security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Creating a node access list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Configuring security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Understanding BaySecure security modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Disabled security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Sequential security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
ListMin security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
ListMax security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
Only1Min security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
Only1Max security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Checked1Min security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Checked1Max security mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Troubleshooting BaySecure LAN Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
BaySecure operational note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Appendix A

34 Contents
Using discovery command line utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . 835
disdevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
dislink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Appendix B
Modifying Fault Correlator startup files. . . . . . . . . . . . . . . . . . . . . . . . . . . 841
Fault Correlator startup files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842

Vendor specification file syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Configuration files for third-party applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Trap specification file syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Trap specification file variable definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
Trap specification file macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Syntax for trap definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Fault specification file syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Fault specification file variable definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Fault specification file clauses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Examples of Fault Correlator definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Examples of trap definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Examples of fault definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
Increment fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Toggle fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Increment and toggle fault examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Increment fault example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Toggle fault example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
Fault correlator terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Fault object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Toggle fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Fault state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Fault category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Fault severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Network entity state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
207569-F
35
Figures
Figure 1 Accessing Optivity NMS 10.3 client applications . . . . . . . . . . . . . . . . . . . 60

Figure 2 Typical Optivity NMS 10.3 online Help system . . . . . . . . . . . . . . . . . . . . . 73
Figure 3 Access Control Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 4 Access Control Switch dialog box (enabled and disabled) . . . . . . . . . . . . 85
Figure 5 Add/Remove Optivity Users dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 6 Attach/Detach Permissions dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 7 Add Permission Group dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 8 Attach Permission Group dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 9 Assign View Domains and Services dialog box (View domain tab shown) 96
Figure 10 Assign View Domains and Services dialog box (Service tab shown) . . . . 97
Figure 11 Service Allocation Changed dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 12 Community strings and SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 13 SNMPv3 security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 14 Community Strings Editor—Individual view . . . . . . . . . . . . . . . . . . . . . . 110
Figure 15 Community Strings Editor window—Table view . . . . . . . . . . . . . . . . . . . 111
Figure 16 Configure Community Strings Entry dialog box . . . . . . . . . . . . . . . . . . . 118
Figure 17 IP address text box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 18 Read and write community strings text boxes . . . . . . . . . . . . . . . . . . . . 119
Figure 19 Up and Down buttons below IP Range list or table . . . . . . . . . . . . . . . . . 122
Figure 20 Marking the check box for Use SNMPv1 traps if SNMPv3 trap registration.
129
Figure 21 Choose Import Type dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 22 AutoTopology Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Figure 23 Auto Rediscovery dialog box (General tab showing) . . . . . . . . . . . . . . . 154
Figure 24 Auto Rediscovery status on AutoTopology Manager window . . . . . . . . . 155
Figure 25 Seed Information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 26 IP Range dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 27 View Domain Editor dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 28 View Domain Information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

36 Figures
Figure 29 On Demand Discovery dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Figure 30 IP Address Range(s) dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 31 Routerless Discovery dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 32 Out-of-band editor dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 33 Access Point Validate dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 34 Optivity NMS InfoCenter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 35 Parts of the InfoCenter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 36 Folder pane shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 37 InfoCenter folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Figure 38 Folder view shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 39 Object shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 40 Auto Save setting on status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 41 Save Changes prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 42 Show confirmation dialog always (Auto Save) setting . . . . . . . . . . . . . . 205
Figure 43 Save Changes dialog box (Do not show again check box cleared) . . . . 205
Figure 44 Save Changes dialog box (Do not show again check box marked) . . . . 206
Figure 45 InfoCenter Preferences dialog box View tab . . . . . . . . . . . . . . . . . . . . . . 208
Figure 46 InfoCenter Preferences dialog box Global tab . . . . . . . . . . . . . . . . . . . . 211
Figure 47 Resizing columns by dragging column heading dividers . . . . . . . . . . . . 215
Figure 48 InfoCenter Web browser window with Menu toolbar button . . . . . . . . . . 223
Figure 49 Stacking toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 50 Dragging a toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 51 Floating and docking a toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 52 Toolbar shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 53 More button shown on a resized toolbar . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 54 Presentation toolbar at regular and reduced size . . . . . . . . . . . . . . . . . . 228
Figure 55 Selecting an icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Figure 56 Window tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 57 Overview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Figure 58 Visual link created between two nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Figure 59 InfoCenter launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 60 Legend dialog box — all icon types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 61 Legend dialog box — Probe icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 62 Launch Options dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 63 View domains folder showing domains within database view . . . . . . . . . 258
207569-F
Figures 37
Figure 64 Typical status bar indication of rediscovery . . . . . . . . . . . . . . . . . . . . . . 260

Figure 65 Example of Folder pane with new folder . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 66 Folder Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 67 Folder properties dialog box Advanced view . . . . . . . . . . . . . . . . . . . . . 272
Figure 68 Presentation tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 69 Background Color dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Figure 70 InfoCenter folder pane shortcut menu and submenu . . . . . . . . . . . . . . . 278
Figure 71 Save As dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Figure 72 Folder pane with new folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Figure 73 New Folder Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Figure 74 Export Folder Content file override confirmation . . . . . . . . . . . . . . . . . . 289
Figure 75 Delete dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Figure 76 Sharing shortcut menu command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Figure 77 Folder properties dialog box, Sharing tab . . . . . . . . . . . . . . . . . . . . . . . . 293
Figure 78 Device Detail View for a router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Figure 79 Error—No objects in traversal view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Figure 80 Red dot indicating incomplete traversal view . . . . . . . . . . . . . . . . . . . . . 307
Figure 81 Find dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Figure 82 Find Object dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Figure 83 SMLT configuration (data link layer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Figure 84 SMLT configuration, subnet transformed to physical layer . . . . . . . . . . . 314
Figure 85 InfoCenter Preferences dialog box Alarm tab . . . . . . . . . . . . . . . . . . . . . 319
Figure 86 Alarm color dialog box HSB tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Figure 87 Alarm color dialog box RGB tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Figure 88 Folder properties dialog box Presentation tab . . . . . . . . . . . . . . . . . . . . 324
Figure 89 Manually rediscovering a single multicast session . . . . . . . . . . . . . . . . . 331
Figure 90 Selecting multiple multicast sessions for rediscovery . . . . . . . . . . . . . . . 332
Figure 91 Adding a multicast session to the watch list (removing similar) . . . . . . . 333
Figure 92 Auto-rediscovery indicated by isWatched column . . . . . . . . . . . . . . . . . 334
Figure 93 Selecting multiple multicast sessions for auto rediscovery . . . . . . . . . . . 335
Figure 94 Saving a multicast session baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Figure 95 Save Baseline dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Figure 96 Deleting all baselines for a multicast session . . . . . . . . . . . . . . . . . . . . . 338
Figure 97 Session baseline view (tabular presentation) . . . . . . . . . . . . . . . . . . . . . 339
Figure 98 Session baseline view (graphical presentation) . . . . . . . . . . . . . . . . . . . 340

38 Figures
Figure 99 Listing baselines for a multicast session . . . . . . . . . . . . . . . . . . . . . . . . . 341

Figure 100 All Baseline temporary folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 101 Setting a baseline as active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Figure 102 Comparing a multicast session with its active baseline . . . . . . . . . . . . . 343
Figure 103 Temporary window showing results of comparison . . . . . . . . . . . . . . . . 344
Figure 104 Baselines/Multicast sessions folder ordered by label . . . . . . . . . . . . . . . 346
Figure 105 Shortcut menu for Multicast/Sessions folder . . . . . . . . . . . . . . . . . . . . . 347
Figure 106 New View Baseline alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Figure 107 Shortcut menu for Multicast/Routing folder . . . . . . . . . . . . . . . . . . . . . . . 348
Figure 108 New View Baseline alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 109 Comparing view baselines (routing view shown, session view similar) . 350
Figure 110 Comparing view baselines (routing shown, session similar) . . . . . . . . . 351
Figure 111 Comparing a view baseline with the current network . . . . . . . . . . . . . . . 352
Figure 112 Baseline Export alert box with name of file exported to . . . . . . . . . . . . . 353
Figure 113 Selecting baseline file to import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Figure 114 InfoCenter status bar showing database import in progress . . . . . . . . . 353
Figure 115 InfoCenter status bar showing database imported successfully . . . . . . . 354
Figure 116 Opening the IP-VPN folder in the InfoCenter folder tree . . . . . . . . . . . . . 357
Figure 117 Opening the InfoCenter Resources/IP Telephony folder . . . . . . . . . . . . . 362
Figure 118 Typical InfoCenter IP Telephony folder . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Figure 119 Temporary folder view for IP telephony system . . . . . . . . . . . . . . . . . . . 363
Figure 120 Subnet Aware menu choice for IP telephony system . . . . . . . . . . . . . . . 364
Figure 121 Temporary subnet aware folder view for IP telephony system . . . . . . . . 365
Figure 122 Temporary folder view for logical VLAN view of Succession 1000 system 366
Figure 123 Launching OmniView on an IP telephony system . . . . . . . . . . . . . . . . . 367
Figure 124 Launching OmniView on a component of an IP telephony system . . . . . 367
Figure 125 The InfoCenter VPLS folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Figure 126 VPLS folder view (Tabular presentation shown) . . . . . . . . . . . . . . . . . . . 371
Figure 127 VPLS elements shown in temporary folder. . . . . . . . . . . . . . . . . . . . . . . 372
Figure 128 Switches folder transformed to the VPLS layer . . . . . . . . . . . . . . . . . . . 373
Figure 129 Physical layer view of VPLS folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Figure 130 Data link layer view of VPLS folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Figure 131 Shortcut menu for VPLS or VPLS device . . . . . . . . . . . . . . . . . . . . . . . . 376
Figure 132 Temporary UNIs folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Figure 133 Shortcut menu for UNIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
207569-F
Figures 39
Figure 134 Temporary VPLS folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Figure 135 TD Continuity Test window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Figure 136 New/Edit TDC Test Entry dialog box (advanced shown, basic similar) . . 387
Figure 137 Delete test entry confirmation alert box . . . . . . . . . . . . . . . . . . . . . . . . . 388
Figure 138 TDC Results window (Results tab shown) . . . . . . . . . . . . . . . . . . . . . . . 389
Figure 139 Parts of the OmniView window (MView similar) . . . . . . . . . . . . . . . . . . . 405
Figure 140 OmniView navigation pane (MView similar) . . . . . . . . . . . . . . . . . . . . . . 413
Figure 141 Parts of the OmniView monitor pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Figure 142 OmniView graph window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Figure 143 OmniView graph parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Figure 144 OmniView specify entity to be monitored dialog box . . . . . . . . . . . . . . . 426
Figure 145 Monitor New Entity dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Figure 146 Find Network Element dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Figure 147 Select the file to save to dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Figure 148 Select the file which contains the workspace configuration dialog box . 432
Figure 149 Memory Utilization Table element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Figure 150 Statistics shown by bar indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Figure 151 Relative bar indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Figure 152 Ports-by-Slot, Slot 2 network element, and Activity leaf selected . . . . . . 437
Figure 153 Invalid network utilization data on the first poll . . . . . . . . . . . . . . . . . . . . 438
Figure 154 Valid network utilization data for slot 2, port2 on the second poll . . . . . . 438
Figure 155 Ports-by-Slot, Slot 1 network element, and Activity leaf selected . . . . . . 439
Figure 156 Invalid full-duplex network utilization data on the first poll . . . . . . . . . . . 440
Figure 157 Valid network utilization data on the second poll . . . . . . . . . . . . . . . . . . 441
Figure 158 Sorting column in descending order . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Figure 159 Minimizing a single statistics by clicking in the title bar . . . . . . . . . . . . . 442
Figure 160 Maximizing the statistics pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Figure 161 Clicking the resource icon to minimize all statistics panes . . . . . . . . . . . 443
Figure 162 Example of expanding resource icon panes . . . . . . . . . . . . . . . . . . . . . . 443
Figure 163 Selecting a whole column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Figure 164 Selecting multiple adjacent cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Figure 165 Reordering statistics pane columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Figure 166 Polling Parameters dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Figure 167 Example of the intersection of statistical data . . . . . . . . . . . . . . . . . . . . 450
Figure 168 Example of the union of statistical data . . . . . . . . . . . . . . . . . . . . . . . . . 451

40 Figures
Figure 169 Multi-device element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452

Figure 170 Network element for the second device . . . . . . . . . . . . . . . . . . . . . . . . . 453
Figure 171 Statistics displayed in a multi-device pane . . . . . . . . . . . . . . . . . . . . . . . 453
Figure 172 Network element displayed in active pane . . . . . . . . . . . . . . . . . . . . . . . 454
Figure 173 Updated multi-device showing statistics for added network elements . . 455
Figure 174 Add Table dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Figure 175 Modify Table dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Figure 176 Searching for a MIB object by name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Figure 177 Example of list of MIB objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Figure 178 Validate Expression dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Figure 179 Viewing bar and pie graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Figure 180 Example of data and time value for a specific point on graph . . . . . . . . 470
Figure 181 Example of Export Data dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Figure 182 Choose Data Series to Save dialog box example . . . . . . . . . . . . . . . . . . 474
Figure 183 OmniView Preferences dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Figure 184 Bar Indicator Fill Color dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Figure 185 OmniView log file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Figure 186 Unknown device error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Figure 187 Unsupported or unknown device omniview_root.log file . . . . . . . . . . . . . 484
Figure 188 Example of an expanded RMON tree . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Figure 189 Example of an expanded SMON tree . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Figure 190 Example of a RMON Statistics Group . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Figure 191 Example of SMON statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Figure 192 Protocol Visualization example for RIP2 domain routers . . . . . . . . . . . . 490
Figure 193 Display of OSPF area routers in the contents pane . . . . . . . . . . . . . . . . 491
Figure 194 Display of OSPF area routers in the monitor pane . . . . . . . . . . . . . . . . . 492
Figure 195 Example for a RIP2 router in a unicast layer . . . . . . . . . . . . . . . . . . . . . 493
Figure 196 Example of an OSPF router in a unicast layer . . . . . . . . . . . . . . . . . . . . 494
Figure 197 Example of an OSPF ABR link in navigational pane . . . . . . . . . . . . . . . 495
Figure 198 Example of an OSPF ABR link in contents pane . . . . . . . . . . . . . . . . . . 495
Figure 199 Example of protocol statistics of an OSPF ASBR link . . . . . . . . . . . . . . 496
Figure 200 Example of a multicast session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Figure 201 Example of a router in a multicast session layer . . . . . . . . . . . . . . . . . . . 498
Figure 202 OmniView navigational pane for router interface running frame relay . . 499
Figure 203 OmniView contents pane for a router interface running frame relay . . . . 499
207569-F
Figures 41
Figure 204 OmniView navigation pane for a PCV link in frame relay . . . . . . . . . . . . 500
Figure 205 Contents pane for a router interface running frame relay . . . . . . . . . . . . 501
Figure 206 Ethernet segment statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Figure 207 Token ring segment statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Figure 208 Ethernet performance history statistics table . . . . . . . . . . . . . . . . . . . . . 506
Figure 209 Ethernet fault history statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Figure 210 Token ring performance history statistics table . . . . . . . . . . . . . . . . . . . . 506
Figure 211 Token ring fault history statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Figure 212 usrHistory statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Figure 213 Network layer (NL) protocol distribution statistics table . . . . . . . . . . . . . 508
Figure 214 Application layer (AL) protocol distribution statistics table . . . . . . . . . . . 508
Figure 215 Accounting user history statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Figure 216 VLAN distribution statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Figure 217 Priority distribution statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Figure 218 Port profile information displayed in a MView window . . . . . . . . . . . . . . 511
Figure 219 Parts of the Modify Application Launch dialog box . . . . . . . . . . . . . . . . . 522
Figure 220 Modify Application Launch dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Figure 221 Object shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Figure 222 Modify Application Launch dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Figure 223 Monitor Options dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Figure 224 Example of an Expanded View showing a BayStack device (front view) 560
Figure 225 Front panel of a BayStack 100BASE-T device . . . . . . . . . . . . . . . . . . . . 566
Figure 226 Chassis status view of a BayStack device . . . . . . . . . . . . . . . . . . . . . . . 567
Figure 227 Logical view of a Centillion device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Figure 228 Management window for a System 5000 device . . . . . . . . . . . . . . . . . . 572
Figure 229 Expanded View Preferences dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 577
Figure 230 System 5000 Profile window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Figure 231 Show Nodes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Figure 232 Add Row dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Figure 233 Modify Row dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Figure 234 Example of Find Row dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Figure 235 Parts of the Call View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Figure 236 CallView graphical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Figure 237 CallCount graphical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Figure 238 Find an Object dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

42 Figures
Figure 239 Find Row dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

Figure 240 Set Preferences dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Figure 241 Resizing tabular columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Figure 242 View an Object Attributes dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
Figure 243 Link Object Attributes dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Figure 244 Typical Fault Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Figure 245 Navigation pane and filter tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Figure 246 Filter window status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Figure 247 Unmonitor Event(s) dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Figure 248 Delete Event(s) alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Figure 249 Empty AND group (default group), shown with 2x magnification. . . . . . . 659
Figure 250 Equivalent single-property groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Figure 251 Non-equivalent multi-property groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Figure 252 Negated group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Figure 253 Negating a single property with the <> relationship . . . . . . . . . . . . . . . . 660
Figure 254 Change Group Type submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Figure 255 Negated logical group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Figure 256 Removing negation from a logical group . . . . . . . . . . . . . . . . . . . . . . . . 666
Figure 257 Selecting property filter options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Figure 258 Finished property filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Figure 259 Example filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Figure 260 Alternate method for negating an operator . . . . . . . . . . . . . . . . . . . . . . . 670
Figure 261 Configure Fault Scripts dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Figure 262 Edit Fault Script dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Figure 263 Configure Trap Forwarding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Figure 264 Fault Summary initialization message . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Figure 265 Fault Summary User Preferences message . . . . . . . . . . . . . . . . . . . . . . 682
Figure 266 Device Inventory Viewer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Figure 267 Typical Type window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Figure 268 Typical asset information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Figure 269 Update Successful alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Figure 270 Module Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Figure 271 Module Information window showing slot information . . . . . . . . . . . . . . 708
Figure 272 Agent Version Upgrades window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Figure 273 Seed Synchronization dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
207569-F
Figures 43
Figure 274 Database synchronization alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712

Figure 275 New Device dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
Figure 276 Asset Information window (adding a new device) . . . . . . . . . . . . . . . . . . 713
Figure 277 Export Assets dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Figure 278 Import Assets find file dialog box (Windows shown, UNIX similar) . . . . . 716
Figure 279 Import Assets wizard - selecting Device Type column . . . . . . . . . . . . . . 717
Figure 280 Import Assets wizard - mapping types . . . . . . . . . . . . . . . . . . . . . . . . . . 718
Figure 281 Import Assets wizard - selecting a device type . . . . . . . . . . . . . . . . . . . . 718
Figure 282 Import Assets wizard - mapping properties . . . . . . . . . . . . . . . . . . . . . . 719
Figure 283 Import Assets wizard - confirm mappings . . . . . . . . . . . . . . . . . . . . . . . 720
Figure 284 New Type dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Figure 285 New Sub Type dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Figure 286 Typical type properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Figure 287 Add Property alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Figure 288 New Property dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Figure 289 Delete Property alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Figure 290 Direct and indirect connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Figure 291 Path Trace Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Figure 292 Enter Path Information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Figure 293 Progress alert box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Figure 294 PathTrace information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Figure 295 Enter Trace Information dialog box (Single end node selected) . . . . . . . 739
Figure 296 Progress alert box (locating an end node) . . . . . . . . . . . . . . . . . . . . . . . 740
Figure 297 PathTrace information window (locating an end node) . . . . . . . . . . . . . . 740
Figure 298 Parts of the Database Admin Tool window . . . . . . . . . . . . . . . . . . . . . . . 748
Figure 299 Database Admin Tool Menu toolbar button in a Web browser . . . . . . . . 750
Figure 300 Database pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Figure 301 Element pane parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
Figure 302 Import Database dialog box in UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Figure 303 Import Database dialog box in Windows . . . . . . . . . . . . . . . . . . . . . . . . 755
Figure 304 Export Database dialog box In UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Figure 305 Export Database dialog box in Windows . . . . . . . . . . . . . . . . . . . . . . . . 759
Figure 306 View Element Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Figure 307 Optivity status message box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Figure 308 Oracle Status message box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

44 Figures
Figure 309 OIT Administration Tool window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

Figure 310 Package Information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
Figure 311 Package Information traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Figure 312 OIT packages saved as a text file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
Figure 313 Open dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
Figure 314 AdminToolConf.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
Figure 315 BaySecure Connect to Optivity Server dialog box . . . . . . . . . . . . . . . . . 804
Figure 316 Parts of the BaySecure LAN Access window . . . . . . . . . . . . . . . . . . . . . 805
Figure 317 BaySecure Set SNMP Parameters dialog box . . . . . . . . . . . . . . . . . . . . 813
Figure 318 BaySecure Status dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Figure 319 BaySecure Node Access dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Figure 320 BaySecure Add Node Access dialog box . . . . . . . . . . . . . . . . . . . . . . . . 816
Figure 321 BaySecure Show Nodes dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Figure 322 BaySecure Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Figure 323 BaySecure Modify Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . 819
Figure 324 BaySecure Add Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . 820
Figure 325 Example fault time line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
207569-F
45
Tables
Table 1 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 2 Optivity NMS 10.3 legacy applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Table 3 Access Control Administration features . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 4 Access permission tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 5 Starting Access Control Administration . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 6 Parts of the Access Control Administration window . . . . . . . . . . . . . . . . . 81
Table 7 Access Control Administration menu commands and toolbar buttons . . . 81
Table 8 Access Control Administration problems and resolutions . . . . . . . . . . . . . 99
Table 9 Common Access Control Administration error messages . . . . . . . . . . . . 99
Table 10 Community string matching examples . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Table 11 Starting Community Strings Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 12 Access permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Table 13 Parts of the Community Strings Editor window . . . . . . . . . . . . . . . . . . . . 111
Table 14 Menu bar commands and toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . 112
Table 15 Parts of the table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Table 16 Parts of the individual view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Table 17 Community string order example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 18 Community Strings Editor file import types . . . . . . . . . . . . . . . . . . . . . . . 132
Table 19 Timeout value conversion examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Table 20 Common Community Strings Editor problems . . . . . . . . . . . . . . . . . . . . 135
Table 21 Starting AutoTopology Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Table 22 Parts of the AutoTopology Manager window . . . . . . . . . . . . . . . . . . . . . . 141
Table 24 Access control tokens for AutoTopology Manager . . . . . . . . . . . . . . . . . 145
Table 25 Discovery seed information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Table 26 Summary of discovery parameters and options . . . . . . . . . . . . . . . . . . . 150
Table 27 Summary of discovery options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Table 28 AutoTopology Manager status messages . . . . . . . . . . . . . . . . . . . . . . . . 176
Table 29 Starting InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

46 Tables
Table 30 Parts of the InfoCenter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Table 31 InfoCenter folder tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Table 32 Folder pane shortcut menu commands . . . . . . . . . . . . . . . . . . . . . . . . . 191
Table 33 InfoCenter folder view layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Table 34 InfoCenter folder view presentation types . . . . . . . . . . . . . . . . . . . . . . . . 196
Table 35 InfoCenter folder view layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Table 36 Parts of the InfoCenter folder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 37 Folder view shortcut menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Table 38 Object shortcut menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Table 39 InfoCenter Auto Save settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Table 40 Default folder view preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Table 41 InfoCenter menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Table 42 Partial view of InfoCenter toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Table 43 InfoCenter toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Table 44 InfoCenter status bar fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Table 45 InfoCenter application categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Table 46 InfoCenter elements used to start Optivity NMS applications . . . . . . . . 251
Table 47 Predefined InfoCenter folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Table 48 Rediscovery processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Table 49 InfoCenter object types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Table 50 Folder preferences — filter attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Table 51 Filter attribute relational operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Table 52 Filter attribute logical operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Table 53 InfoCenter special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Table 54 Attributes used by topology processes . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Table 55 Attributes used in InfoCenter and Fault Summary processes . . . . . . . . . 297
Table 56 Additional objects removed during a permanent delete . . . . . . . . . . . . . 304
Table 57 Traversal views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Table 58 Expand by hops layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Table 59 Remote selection between Optivity NMS applications . . . . . . . . . . . . . . 309
Table 60 InfoCenter common problems and solutions . . . . . . . . . . . . . . . . . . . . . 315
Table 61 Fault category definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Table 62 InfoCenter alarm states and color coding . . . . . . . . . . . . . . . . . . . . . . . . 320
Table 63 InfoCenter fault status criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Table 64 Alarm status calculation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
207569-F
Tables 47
Table 65 Icons for multicast sessions and baselines . . . . . . . . . . . . . . . . . . . . . . . 336

Table 66 Multicast session comparison colors . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Table 67 Required IP Telephony Community strings entry settings . . . . . . . . . . . 360
Table 68 Starting TD Continuity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Table 69 Parts of the TD Continuity Test window . . . . . . . . . . . . . . . . . . . . . . . . . 382
Table 71 TD Continuity Test window test table . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Table 72 Types of network resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Table 73 Access Control permission tokens for OmniView . . . . . . . . . . . . . . . . . . 396
Table 74 Starting OmniView or MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Table 75 OmniView command line parameter options . . . . . . . . . . . . . . . . . . . . . 400
Table 76 Data type templates for the MView -Q option . . . . . . . . . . . . . . . . . . . . . 401
Table 77 URL options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Table 78 Web browser parameter options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Table 79 Guidelines for starting MView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Table 80 Parts of the OmniView window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Table 81 OmniView menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Table 82 OmniView toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Table 83 Parts of the OmniView navigation pane . . . . . . . . . . . . . . . . . . . . . . . . . 414
Table 84 Parts of the OmniView monitor pane . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Table 85 Parts of the OmniView Graph window . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Table 86 Graph window menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Table 87 Graph window toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Table 88 Parts of an OmniView graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Table 89 Statistics types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Table 90 How full-duplex devices displays network utilization data . . . . . . . . . . . . 439
Table 91 Multiple device terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Table 92 Network management data types specified by the -Q option . . . . . . . . . 503
Table 93 OmniView error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Table 94 OmniView problems and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Table 95 Example of port information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Table 96 Modify Application Launch dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Table 97 ParserElement descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Table 98 Special symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Table 99 Terminal symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

48 Tables
Table 100 Execution environment syntax production rules . . . . . . . . . . . . . . . . . . . 530

Table 101 Execution environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Table 102 Application Launch error messages and solutions . . . . . . . . . . . . . . . . . 538
Table 103 Monitor Options dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Table 104 Monitor Options levels of network discovery . . . . . . . . . . . . . . . . . . . . . . 546
Table 105 Monitor Options fault management processes . . . . . . . . . . . . . . . . . . . . 547
Table 106 Monitoring options for objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Table 107 Troubleshooting Monitor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Table 108 Access privilege levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Table 109 Starting Expanded View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Table 110 superev file options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Table 111 Parts of the Expanded View window . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Table 112 Expanded View menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Table 113 Toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Table 114 Shortcut menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Table 115 Management window parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Table 116 Management window menus and commands . . . . . . . . . . . . . . . . . . . . 573
Table 117 Management window toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Table 118 Profile information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Table 119 Expanded View error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Table 120 Call View application layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Table 121 ATM object types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Table 122 Starting Call View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Table 123 Call View start file options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Table 124 Parts of the Call View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Table 125 Object shortcut menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Table 126 Call View toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Table 127 Status bar elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Table 128 CallView graphical view elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Table 129 Call View tabular view columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Table 130 CallCount graphical view elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Table 131 CallCount tabular view columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Table 132 Call Table tabular view columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Table 133 ATM call types and labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Table 134 Call view icon and link colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
207569-F
Tables 49
Table 135 Special search characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

Table 136 Call Delta colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Table 137 Common Call View problems and solutions . . . . . . . . . . . . . . . . . . . . . . 633
Table 138 Call View messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Table 139 Event types reported by Fault Summary . . . . . . . . . . . . . . . . . . . . . . . . 635
Table 140 Event color codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Table 141 Starting Fault Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Table 142 Fault Summary command line options . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Table 143 Parts of the Fault Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Table 145 Parts of the Fault Summary navigation pane . . . . . . . . . . . . . . . . . . . . . 645
Table 146 Filter window toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Table 147 Fault Summary preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Table 148 Types of logical groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Table 149 Property filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Table 150 Typical property filter relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Table 151 Fault script parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Table 152 Fault script IP address examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Table 153 Fault management services and daemons . . . . . . . . . . . . . . . . . . . . . . . 683
Table 154 Fault management services with debug output . . . . . . . . . . . . . . . . . . . 691
Table 155 Starting Device Inventory Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Table 156 Parts of the Device Inventory Viewer window . . . . . . . . . . . . . . . . . . . . . 698
Table 158 Typical asset properties, shown in alphabetic order . . . . . . . . . . . . . . . . 705
Table 159 Device Inventory Viewer error messages and remedial actions . . . . . . . 728
Table 160 Path Trace terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Table 161 Default Path Trace object fault colors . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Table 162 Common problems and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Table 163 Database Admin Tool access permissions . . . . . . . . . . . . . . . . . . . . . . . 744
Table 164 Optivity NMS databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Table 165 Starting Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Table 166 Database Admin Tool window parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Table 167 Database Admin Tool menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Table 168 Database pane parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
Table 169 Element pane parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751

50 Tables
Table 170 How to work with elements in the element pane . . . . . . . . . . . . . . . . . . 752
Table 171 How to work with database objects in the element pane . . . . . . . . . . . . 764
Table 172 Database Admin Tool problem solutions . . . . . . . . . . . . . . . . . . . . . . . . 767
Table 173 How devices and device applications are distributed . . . . . . . . . . . . . . . 771
Table 174 Starting OIT Administration Tool and oitinstall . . . . . . . . . . . . . . . . . . . . 774
Table 175 Access permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Table 176 Parts of the OIT Administration Tool window . . . . . . . . . . . . . . . . . . . . . 775
Table 178 User-selected file types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
Table 179 Device agents supported in Optivity NMS 10.3 . . . . . . . . . . . . . . . . . . . 788
Table 180 Common OIT Administration Tool problems . . . . . . . . . . . . . . . . . . . . . . 791
Table 181 Types of intrusion control supported by BaySecure . . . . . . . . . . . . . . . . 797
Table 182 Type of eavesdrop protection supported by BaySecure . . . . . . . . . . . . . 798
Table 183 BaySecure LAN Access baysec start file options . . . . . . . . . . . . . . . . . . 803
Table 184 BaySecure LAN Access window parts . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Table 185 BaySecure menu bar commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Table 186 BaySecure toolbar buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Table 187 BaySecure security modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Table 188 Disabled mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Table 189 Sequential mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Table 190 ListMin mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
Table 191 ListMax mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
Table 192 Only1Min mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Table 193 Only1Max mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
Table 194 Checked1Min mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Table 195 Checked1Max mode security actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
Table 196 disdevice parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
Table 197 dislink parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Table 198 Typical Vendor Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Table 199 Variable definitions in traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
Table 200 Trap specification file macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Table 201 Trap syntax elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Table 202 Fault specification variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Table 203 Fault specification clauses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Table 204 Increment fault elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
207569-F
Tables 51
Table 205 Toggle fault elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857

Table 206 States of an incremental fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Table 207 States of a toggle fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Table 208 Alarm status and severity levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868

52 Tables
207569-F
53
Preface
Optivity* Network Management System (NMS) 10.3 is an integrated set of tools

designed to deliver system-level network management.
Before you begin

This guide is intended for network managers using a Microsoft* Windows* or
UNIX*-based management station. Prior knowledge of Optivity NMS software is
not required. This guide assumes that you have the following background:
• Working knowledge of the Windows or UNIX operating system

• Understanding of the transmission and management protocols used on your
network
• Experience with windowing systems or graphical user interfaces (GUIs)
• Familiarity with the network management platform (for example, HP*
OpenView Network Node Manager or Tivoli TME 10 NetView) on the
system with which you are using Optivity NMS

54 Preface
Text conventions
This guide uses the following text conventions:
angle brackets (< >) Indicate that you choose the text to enter based on the
description inside the brackets. Do not type the
brackets when entering the command.
Example: If the command syntax is
ping <ip_address>, you enter
ping 192.32.10.12
bold Courier text Indicates command names and options and text that
you need to enter.
Example: Enter callview.
brackets ([ ]) Indicate optional elements in syntax descriptions. Do
not type the brackets when entering the command.
optstatus [-f], you can enter either optstatus or
optstatus -f.
italic text Indicates new terms, book titles, and variables in
command syntax descriptions. Where a variable is two
or more words, the words are connected by an
underscore.
callview -I <IP_address>, IP_address is one
variable and you substitute one value for it.
plain Courier Indicates command syntax and system output, for
text example, prompts and system messages.
Example:
Process: Trap Registration Daemon
Required Status: Must Run
Current Status: Running
separator ( > ) Shows menu paths.
Example: Options > Remote Selection turns on remote
selection between Optivity NMS applications.
207569-F
Preface 55
Acronyms
This guide uses the acronyms described in Table 1.
Table 1 Acronyms
Acronym Description
ASA authorized source address

ASCII american standard code for information interchange
ATM asynchronous transfer mode
BUS broadcast and unknown server
CSV comma separated values
DHCP dynamic host configuration protocol
DNS domain name server
ELAN emulated LAN
ERC express routing code
GUI graphical user interface
HSB hue/saturation/brightness
HTML hypertext markup language
IC InfoCenter
ICMP Internet Control Message Protocol
IP Internet Protocol
ISO International Organization for Standardization
JRE Java* run-time environment
LAN local area network
LANE LAN emulation
LECS LAN emulation configuration server
LED light emitting diode
LES LAN emulation server
LSA last source address
MAC media access control

56 Preface
Table 1 Acronyms (continued)
Acronym Description
MIB management information base

MS-DOS* Microsoft disk operating system
NMM network management module
NMS network management system
NSAP network service access point
NVRAM non-volatile RAM
OID object identifier
OIT Optivity integration toolkit
PVC permanent virtual circuit
RAM random access memory
RGB red/green/blue
RMON remote monitoring
SNMP Simple Network Management Protocol
SVC switched virtual circuit
TCP/IP Transmission Control Protocol/Internet Protocol
URL universal resource locator
UNI user network interface
VCC virtual channel connection
VCI virtual channel identifier
VLAN virtual LAN
VPI virtual path identifier
VPLS virtual private LAN service
WAN wide area network
207569-F
Preface 57
Related publications
For more information about using Optivity Network Management System (NMS)
10.3, refer to the following publications:
• Using Optivity NMS 10.3 Applications (part number 207569-F) (This
document)
In addition to the integrated Optivity NMS 10.3 Online Help system, this
document describes how to use the integrated Optivity NMS tools and
applications to proactively get the most out of your network resources.
This document is located on the Optivity NMS 10.3 for Windows* CLIENT
Only and Documentation CD.
You can view the Optivity NMS Online Help System while you use Optivity
by choosing Help > <application_name> Help from any application.
• Installing and Administering Optivity NMS 10.3 (part number 205969-H)
Describes how to install Optivity NMS software and get started using Optivity
NMS to management your network.
• Release Notes for Optivity NMS 10.3 (Part number 205970-H)
Contains the latest information about Optivity NMS 10.3, including
informational notes, known problems, and bug fixes.
• Quick Installation and Startup for Optivity NMS 10.3 for Windows*
(Part number 217232-A)
Provides quick procedures for installing Optivity NMS 10.3 on a Windows
machine.
• Quick Installation and Startup for Optivity NMS 10.3 for Solaris
Provides quick installation procedures for installing Optivity NMS 10.3 on a
Solaris machine.
• Quick Installation and Startup for Optivity NMS 10.3 for HP-UX
Provides quick installation procedures for installing Optivity NMS 10.3 on an
HP-UX machine.

58 Preface
Hard-copy 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.
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.
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.
207569-F
59
Chapter 1
Introduction
Optivity Network Management System (NMS) 10.3 is an integrated suite of

applications that deliver system-level management to converging campus and
enterprise networks.
Optivity NMS 10.3 is a primary component of Unified Networks*, a solution set

from Nortel Networks designed to create greater value for customers worldwide
through the integration of voice, video, and data networking. Through Unified
Networks, enterprises can leverage LAN and WAN convergence, application and
infrastructure convergence, and voice and data convergence to achieve greater
efficiency and reduced operational cost. Unified Networks provides a systematic
transition from today's disparate networks.
The Optivity NMS 10.3 common graphical interfaces and proven technology
provide the necessary tools to manage the converging Unified Network. Optivity
NMS 10.3 provides graphical views from physical connections between LAN and
WANs to the logical connections of a VLAN.
Flexible architectural approach

The tools used to access network data are as critical as the data itself. This
approach has provided the basis for the architectural changes in Optivity NMS
10.3, facilitating Web-based access and letting you manage the network from any
location.
New application interfaces in Optivity NMS 10.3 are written in the Sun
Microsystems Java programming language. This feature lets you load the client
application onto a Microsoft Windows NT* system, a Microsoft Windows 2000
Server or Windows 2000 Advanced Server, or Windows 98 system, or a Solaris*
workstation and maintain the same look and feel, functionality, and breadth of

60 Chapter 1 Introduction
features. In addition, access through the World Wide Web provides the same
application interface. This consistency reduces the time and resources associated
with adapting to an unfamiliar user environment. The example in Figure 1 shows
several different ways of running the Optivity NMS 10.3 client applications.
Figure 1 Accessing Optivity NMS 10.3 client applications
UNIX Windows NT Windows 98 Windows 2000 Web browser

client client client Professional client client
UNIX Server
network management station
9163EC
Complementing the Java-based client utilities, a set of powerful network

management services or daemons reside on a centralized Optivity NMS 10.3
server. These services or daemons need not be located on the same system as the
client utilities, allowing remote access across the intranet. Unlike many client/
server pairs, the Optivity NMS 10.3 client application is not bound to a single
server, thus delivering access to any Optivity NMS 10.3 server on the network
from one client installation.
In addition, new applications within Optivity NMS 10.3 have been engineered to
be “data driven.” This allows the applications to take advantage of the Optivity
Integration Toolkit. Nortel Networks is now able to create Optivity NMS 10.3
support files that can be delivered with new products and installed with the
Optivity Integration Toolkit, providing “Day One” support for strategic new
products.
For more information about installing new device support, see the chapter
“Installing new device support” in Installing and Administering Optivity NMS
10.3 (part number 205969-H).
207569-F
Chapter 1 Introduction 61
What's new in Optivity NMS 10.3

Optivity NMS 10.3 includes the following new features and functions:
• 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. See “Limiting discovery using IP ranges” on page 158 for more
information.
• 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.
See the following sections for more information about managing view
domains:
— “Assigning view domains to ONMS users” on page 95
— “Working with view domains” on page 161
— “Adding and removing view domains” on page 257
• 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. See “Assigning services to ONMS users” on page 97 for
more information about assigning services.
• 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. See
“Sharing custom folder queries with other InfoCenter users” on page 291 for
more information.

• SNMPv3 discovery - When autotopology discovery encounters devices

configured for SNMPv3, it uses SNMPv3 protocol to get data from the
devices. To use this feature, you must enter SNMPv3 community string
parameters using Community Strings editor.
Optivity NMS 10.3 applications

The following sections describe the Optivity NMS 10.3 applications:
• “InfoCenter‚” next
• “OmniView” on page 63
• “Path Trace” on page 64
• “Device Inventory Viewer” on page 64
• “TD Continuity Test” on page 64
• “Fault Summary/Fault Correlator” on page 65
• “Expanded View” on page 65
• “Call View” on page 65
• “Legacy applications” on page 66
InfoCenter
InfoCenter provides a centralized location for you to view your network resources
and launch local or Web-based applications. InfoCenter also provides a central
launch point for other network resource management products such as Device
Manager for Passport routing switches. Using an intuitive, folder-based interface,
you can group your devices into logical groups by device type, location,
criticality, fault status, or any number of other pertinent attributes.
The InfoCenter display lets you choose from one of two viewing formats:
• Graphical view lets you view the contents of a folder as icons, but with the
added feature of physical and logical connections.
• Tabular view displays the contents of a folder in text format, allowing a large
amount of data to be displayed in a small window space.
207569-F
InfoCenter also lets you move through the logical layers of the network—from
Internet down to physical—displaying intranetwork devices, logical concepts
(such as VLANs), and end nodes.
Fault status is instantly displayed in all views within InfoCenter. In addition, the
Alarms folders themselves reflect the fault status of the devices within them,
letting you spot potential problems in the network at a glance.
For more information about InfoCenter, see:
• Chapter 5, “Navigating the InfoCenter window,” on page 181

• Chapter 6, “Organizing your network with InfoCenter,” on page 255
• Chapter 7, “Monitoring network health with InfoCenter,” on page 317
OmniView
The OmniView performance monitoring application uses a tree-structured

interface to simplify navigation. OmniView simplifies the process of moving
between network concepts—from subnets down to ports on a device, or from the
port level to the VLAN or subnet level—making it easy for you to launch the
appropriate software needed to gather intelligent data reports.
You can display information gathered by OmniView in tabular or graphical

format. Tabular output is grouped by “panes” of information containing the data
objects that you need most often. You can easily graph these queries by selecting a
group of data points from the pane and choosing the type of graph. You can select
from pie chart, line graph, or bar graph output.
OmniView users can also create customized panes of information to query the
data that is most important to them. Using an intuitive MIB browser-like interface,
you can select any supported MIB object as an attribute of the pane. In addition,
you can perform simple mathematical functions upon multiple MIB objects,
letting you set up MIB equations for statistics such as utilization or bandwidth
computation.
For more information, see Chapter 13, “Monitoring devices with OmniView and
MView,” on page 393.

Path Trace
The InfoCenter Path Trace tool lets you view and troubleshoot paths between
devices. You can also use Path Trace to focus on a potentially faulty device
attached to a single end node. This feature lets you use Path Trace to diagnose
issues with clients, servers or other devices in the network. Path Trace also
indicates fault status of objects with the standard colors used in InfoCenter.
Path Trace is designed to help you localize the source of network problems. By
using Path Trace and InfoCenter together, you can establish a monitoring baseline
for link or device characteristics by saving data into InfoCenter folders for
retrieval and comparison at a later date. You can then use InfoCenter’s tool set to
further isolate the issue down to the data link or physical level, or to expand the
trace to view the logical topology around the problem.
For more information, see Chapter 20, “Tracing paths and locating end nodes,” on
page 731.
Device Inventory Viewer
Device Inventory Viewer lets you view and manage information about your
network assets, including information about modules installed inside hubs,
switches, and chassis. It also lets you view and edit information about the versions
of agent software running on devices in the inventory.
For more information, see Chapter 19, “Managing Network Assets with Device
Inventory Viewer,” on page 695.
TD Continuity Test
TD Continuity Test provides a powerful set of tools for troubleshooting

internetworking traffic for TLS services. TD continuity testing lets you simulate
the customer's data path traffic. The test sends and receives test packets and
reports test results. It also lets you can also check for misconfiguration on the local
and remote ports.
207569-F
TD Continuity Test is both a debugging tool and Service Level Agreement (SLA)
tool. You can use it to validate all end points, test connectivity, and determine
round trip delay measurements for SLA purposes. You can also configure TD
Continuity Test to automatically perform periodic checks of all endpoints of the
VPN (source UNI to the far end UNI).
For more information, see Chapter 12, “Testing Transport Domain Continuity
with TD Continuity Test,” on page 379.
Fault Summary/Fault Correlator
Optivity NMS 10.3 provides an intelligent fault engine that links into the topology
database to provide true correlation and aggregation of faults. These faults are
then summarized in a graphically-oriented viewer that offers solutions to the faults
displayed. For more information about Fault Summary, see Chapter 18,
“Managing events with Fault Summary,” on page 635.
In addition to using the Fault Summary application, you can also customize the
operation of the Fault Correlator engine by editing the Fault Correlator startup
files. For more information, see Appendix B, “Modifying Fault Correlator startup
files,” on page 841.
Expanded View
Expanded View presents a physical graphical view of a given network device,

letting you monitor, configure, and retrieve statistics from the device. For more
information, see Chapter 16, “Configuring devices with Expanded View,” on page
553.
Call View
Call View provides a graphical display of all ATM entities and virtual circuits
included in dynamically configured Centillion* ATM networks. For more
information, see Chapter 17, “Managing ATM traffic with Call View,” on page
595.

Legacy applications
In addition to the new and updated applications described in the previous sections,
Optivity NMS 10.3 retains the following legacy applications that are no longer
fully supported, but are still installed (optionally) on the Optivity NMS server:
Table 2 Optivity NMS 10.3 legacy applications
Legacy Application Executable Where installed
LANarchitect UNIX: • Windows server:

./vlan_vv –I <ip_address> \opt\lnms\unsupported
Windows, for System 5000: • UNIX server:
vlanui.exe /5k –n<ip_address> /opt/lnms/unsupported
Windows, for 28000-Series switch:

vlanui.exe /28k –n<ip_address>
Threshold Manager UNIX:
./thman –I<ip_address>
Windows:
thldmgr.exe –n<ip_address>
Expanded View for UNIX:
System 2000 and ./ev –I <ip_address>
System 3000 hubs
Windows:
expview.exe –n<ip_address>
PCAP/TAP UNIX: • UNIX:
1. cd $LNMSHOME/unsupported/ $LNMSHOME/
walts unsupported/walts
2. run WALTS_ENABLE • Windows:
$LNMSHOME/
3. run ./pcap unsupported/
Windows: PCAPTAP
To install, double-click on
PCAPTAP.EXE from Windows NT
Explorer.
The installation will put PCAP Config
and Network Tap into your Start
menu under Programs.
207569-F
Table 2 Optivity NMS 10.3 legacy applications (continued)
Legacy Application Executable Where installed
Redundant Link ./rlink –I <ip_address> • UNIX server only:

Manager /opt/lnms/unsupported
Conversation Steering ./css –I <ip_address>
Control
BaySecure LAN UNIX: • Windows client:
Access ./baysec -I <ip_address> \opt\lnms\bin
Windows: • UNIX client:
baysec.bat -I <ip_address> /opt/lnms/bin
These legacy applications (with the exception of BaySecure LAN Access) are not
Java- or Web-based, and you must start them locally from the Optivity NMS 10.3
server.
Administrative functions
Optivity NMS 10.3 contains several features that help you achieve better control
over what data is collected, how it is collected, and who has access to the data.
The following sections describe the Optivity NMS 10.3 administrative functions:
• “Access Control‚” next

• “Community Strings Editor” on page 68
• “Monitor Level” on page 68
• “Database Admin Tool” on page 68
• “AutoTopology Manager” on page 68
• “OIT Administration Tool” on page 69
• “Disdevice and dislink” on page 69
Access Control
Access Control lets you limit access to applications and application functions on a
per-user basis. You can use this tool to limit Optivity NMS users to read-only or
read/write access, or restrict them from accessing sensitive applications and/or
functions.

In addition, you can create a customized group of access permissions, allowing

quick and easy assignment of access privileges to specific users. For more
information, see Chapter 2, “Specifying access to Optivity NMS applications with
Access Control Administration,” on page 75.
Community Strings Editor
The Community Strings Editor lets you add, delete, modify, or rearrange entries
that specify device access via SNMPv1, SNMPv3, SSL, and Telnet. The
Community Strings Editor stores information about community strings in the
Optivity NMS 10.3 topology database. For more information, see Chapter 3,
“Specifying access to devices with the Community Strings Editor,” on page 101.
Monitor Level
The levels of monitoring in Optivity NMS 10.3 become much more refined as you
gain full control over how you want your networks managed. The InfoCenter
Monitor Level window lets you control fault correlation, ICMP polling, trap
registration, and topology on a subnet, segment, device, or router interface. For
more information, see Chapter 15, “Specifying the level of statistics gathering
with Monitor Options,” on page 541.
Database Admin Tool
The Database Admin Tool provides you with a quick, effective method of backing
up critical Optivity NMS 10.3 application and user databases. You can also use the
Database Admin tool to configure the views that will be most useful to users of
the Optivity NMS 10.3 applications. For more information, see Chapter 21,
“Managing data with the Database Admin Tool,” on page 743.
AutoTopology Manager
The AutoTopology Manager lets you monitor and manage the topology discovery
process running on the Optivity NMS server. Use the AutoTopology Manager to
start and stop the discovery process and observe the status of the discovery
process. For more information, see Chapter 4, “Discovering your network with
AutoTopology Manager,” on page 137.
207569-F
OIT Administration Tool
The OIT Administration Tool provides a graphical interface that lets you
administer device support. You can install new, upgrade current, and view all
devices that are installed on the Optivity NMS server.
Disdevice and dislink
Disdevice and dislink are command-line topology utilities that you can use to
discover single devices or links on single devices, or multiple devices and links.
You can also use these commands to do a full discovery on portions of the
network, and also debug topology issues. For more information, see Appendix A,
“Using discovery command line utilities,” on page 835.
Integration with Optivity Telephony Manager

If you use Optivity Telephony Manager (OTM), you can integrate OTM with
Optivity NMS. Integrating OTM with Optivity NMS lets you manage Meridian*
voice switches from Optivity NMS InfoCenter.
For more information about integrating OTM with Optivity NMS, see Optivity
Telephony Manager Installation and Configuration (part number 553-3001-230).
How this manual is organized

This manual is organized so that the topics covered by each chapter appear in the
order in which you will most likely need them.
The first four chapters are dedicated to introductory topics, and to applications
that you use as you get started with Optivity NMS 10.3:
• Chapter 1, “Introduction,” on page 59 introduces you to Optivity NMS 10.3.

• Chapter 2, “Specifying access to Optivity NMS applications with Access

Control Administration,” on page 75 tells you how to use Access Control
administration to configure access to the various Optivity NMS 10.3
applications. You will be most interested in this chapter if you administer an
Optivity installation that is used by several Optivity users.
• Chapter 3, “Specifying access to devices with the Community Strings Editor,”
on page 101 tells how to build a database of SNMP community strings that
Optivity NMS 10.3 can use to communicate with network devices.
• Chapter 4, “Discovering your network with AutoTopology Manager,” on page
137 tells how to use the AutoTopology Manager application to start the
topology discovery process that populates the Optivity NMS 10.3 database
with devices.
The next three chapters cover various aspects of InfoCenter, the center for
Optivity NMS 10.3 operations:
• Chapter 5, “Navigating the InfoCenter window,” on page 181 introduces you

to InfoCenter, and describes various aspects of the InfoCenter interface.
• Chapter 6, “Organizing your network with InfoCenter,” on page 255 describes
how you can use InfoCenter folders to organize your network. You can use the
predefined InfoCenter folders, or you can create your own custom folders.
• Chapter 7, “Monitoring network health with InfoCenter,” on page 317
describes how to use the InfoCenter fault management feature to visually
monitor the health status of your network devices.
The next five chapters describe how to use Optivity NMS 10.3 applications to
monitor and manage specific types of network devices and protocols:
• Chapter 8, “Managing multicast sessions and protocols with Optivity NMS,”

on page 329 describes how to use Optivity NMS applications to discover and
visualize multicast sessions and protocols.
• Chapter 9, “Managing IP Virtual Private Networks with Optivity NMS,” on
page 355 describes how to use Optivity NMS applications to discover and
visualize Contivity IP-VPN devices and tunnels.
• Chapter 10, “Managing IP telephony systems with Optivity NMS,” on page
359 describes how to use Optivity NMS applications to discover and monitor
Succession and Meridian IP Telephony systems and devices.
207569-F
• Chapter 11, “Managing virtual private LAN services devices with Optivity
NMS,” on page 369 describes how to use Optivity NMS applications to
discover and manage OPTera Metro VPLS devices and services.
The next 12 chapters describe the Optivity NMS 10.3 applications that you can
use to monitor and manage your network:
• Chapter 12, “Testing Transport Domain Continuity with TD Continuity Test,”

on page 379 describes how to use TD Continuity Test to test TD continuity for
VPLSs on OPTera Metro OM1000-series and OM-8000-series devices.
• Chapter 13, “Monitoring devices with OmniView and MView,” on page 393
describes how to use OmniView to view performance statistics for network
resources in both graphic and tabular form.
• Chapter 14, “Managing network management applications with Application
Launch,” on page 521 describes how to use Application Launch to configure
InfoCenter to launch certain network management applications in specific
circumstances.
• Chapter 15, “Specifying the level of statistics gathering with Monitor
Options,” on page 541 describes how you configure Optivity NMS 10.3 to
obtain the desired level of network monitoring. You can also use Monitor
Options to control fault correlation, ICMP polling, trap registration, and
topology discovery on a subnet, segment, device, or a router interface.
• Chapter 16, “Configuring devices with Expanded View,” on page 553
describes how to use Expanded View to view and configure network devices
using SNMP.
• Chapter 17, “Managing ATM traffic with Call View,” on page 595 describes
how to use Call View to monitor and manage traffic in ATM networks.
• Chapter 18, “Managing events with Fault Summary,” on page 635 describes
how to use Fault Summary to evaluate network performance based on faults.
You can also configure Fault Summary to execute predefined actions in the
case of certain fault conditions.
• Chapter 19, “Managing Network Assets with Device Inventory Viewer,” on
page 695 describes how to use The Device Inventory Viewer to view and
manage information about your network assets, including information about
modules installed inside hubs, switches, and chassis. It also lets you view and
edit information about the versions of agent software running on devices in
the inventory.

• Chapter 20, “Tracing paths and locating end nodes,” on page 731 describes
how to view information about the network path between any two managed
objects on your network. The Path Trace feature also lets you locate end nodes
such as user workstations.
This manual also includes two appendixes that contain information about
command line discovery utilities and configuring background Optivity NMS 10.3
processes:
• Appendix A, “Using discovery command line utilities,” on page 835 describes

how to use the dislink and disdevice command line utilities to discover single
devices or links on single devices, or multiple devices and links. You can also
use these commands to do a full discovery on portions of the network, and
also debug topology issues.
• Appendix B, “Modifying Fault Correlator startup files,” on page 841 explains
how to add new traps, change correlation parameters, and configure new rules
to handle fault conditions specific to your network.
Using online Help

All of the Optivity NMS 10.3 applications described in this manual contain
extensive context-sensitive online Help systems. For all applications, the Help
system is at least as comprehensive as the manual chapter on the application. Look
in online Help whenever you need more information about an application
interface or a procedure as you work. To open Help, choose Help > Using
[application name], or click the Help button in any application dialog box.
207569-F
The Optivity NMS 10.3 Help systems are in the form of Web pages that you view
using the default browser on your system. Figure 2 shows a typical Optivity NMS
10.3 Help system opened in a Netscape Navigator* Web browser window.
Figure 2 Typical Optivity NMS 10.3 online Help system
When you run Optivity NMS 10.3 applications at an Optivity NMS 10.3 client
station, the Web pages for Help topics are retrieved from directories on that
station. When you run Optivity NMS 10.3 applications in a Web browser window,
the Help pages are served from the Optivity NMS 10.3 server where you are
logged in.
The Optivity NMS 10.3 online Help systems display Help content in the right
frame of the browser, and four navigation tabs in the left frame:
• Contents - Shows a table of contents for the Help system.

— Click the (+) or (-) symbols to expand or collapse headings.

— Click the book or page icons to view Help topics.

• Index - Shows an alphabetical index of keywords and common terms.
• Search - Lists topics containing a given word or phrase. Enter a word or
phrase in the text box and press [Enter].
• Favorites - Lets you bookmark Help topics for later reference. Click Add
Current to add the current Help topic to the list. To remove a topic, select a
topic and click Delete.
You can also view descriptions of toolbar buttons and menu commands in the
application window status bars. Point to the button or command, and read the
description in the status bar.
Send us feedback
We would like to hear from you if you have any comments, questions, or
concerns about this or other items of Optivity documentation. Please email us
at nmsdoc@nortelnetworks.com with any feedback you would like to offer.
207569-F
75
Chapter 2
Specifying access to Optivity NMS applications
with Access Control Administration
This chapter is divided into the following major sections:
• “Access Control Administration overview‚” next

• “Getting started with Access Control Administration” on page 76
• “Working with Access Control Administration” on page 84
• “Troubleshooting Access Control Administration” on page 98
Access Control Administration overview

Access Control Administration lets you control user access to Optivity NMS
applications, components, services, and view domains. By default, access control
is disabled, letting any Optivity user log in to InfoCenter and run all Optivity
NMS applications.
The following sections describe operations that Optivity NMS access

administrators can perform with Access Control Administration:
• “Enabling and disabling access control” on page 85

• “Adding Optivity NMS users” on page 86
• “Removing Optivity users” on page 87
• “Setting user permissions” on page 88
• “Changing permission settings” on page 89
• “Adding permission groups” on page 91
• “Attaching permission groups” on page 93
• “Assigning view domains to ONMS users” on page 95
• “Assigning services to ONMS users” on page 97

76 Chapter 2 Specifying access to Optivity NMS applications with Access Control Administration
Getting started with Access Control Administration

The following sections introduce Access Control Administration and tell how to
get started using it:
• “Access Control Administration features‚” next

• “Optivity NMS access administrators” on page 77
• “Access permission tokens” on page 78
• “Starting Access Control Administration” on page 79
• “Access Control Administration window” on page 80
Access Control Administration features
Network managers control user access to Optivity NMS in the InfoCenter Access
Control Administration window.
The Access Control Administration window uses a system of permission tokens to

represent Optivity NMS applications and functions. You manage access by
adding, removing, or modifying permission tokens for configured Optivity NMS
users.
Table 3 describes the main features of Optivity NMS Access Control

Administration.
Table 3 Access Control Administration features
Feature Description
Optivity user Operating system user who can view or modify Optivity NMS
components. You can configure any user that has a valid operating
system user ID as an Optivity user. See “Optivity NMS access
administrators” on page 77 for information about Optivity superusers.
Access Optivity NMS user with read/write access to all permission tokens. The
administrator two fixed access administrators are:
• Administrator
• root
Permission Identification label for the Optivity NMS application components you can
token administer with Access Control Administration. Some applications have
more than one permission token. You cannot add or delete available
tokens. See “Attaching and detaching permissions” on page 89 for more
information.
207569-F
Chapter 2 Specifying access to Optivity NMS applications with Access Control Administration 77
Table 3 Access Control Administration features (continued)
Feature Description
Access A permission token setting that establishes the level of access to Optivity
permission NMS components for individual users and groups of users. Valid
permission settings are:
• Read – Users can view data, but cannot change or add data.
• Read/write – Users can modify database information and window
preferences.
See “Attaching and detaching permissions” on page 89 for more
information.
Permission Set of permission tokens with preconfigured access permissions. For
group example, the default OPTIVITY_ADMIN permission group contains all of
the available tokens set to read/write access. The default
OPTIVITY_VIEW permission group contains all tokens set to read-only.
You can save time setting permissions by attaching a permission group to
Optivity users who have similar access requirements. For more
information, see “Attaching permission groups” on page 93, “Changing
permission groups” on page 95, and “Adding permission groups” on
page 91.
Optivity NMS access administrators
The following users are automatically configured as Optivity NMS access

administrators:
• Administrator
• root
The access administrator has read/write access to all permission tokens. You
cannot delete or modify access permissions for the Administrator or root, and
cannot remove them as Optivity users.
Optivity NMS access administrators inherit the password of the operating system
root and Administrator users on the Optivity NMS server.
Any Optivity NMS user configured with read/write access to every token can
administer all Access Control Administration features, but the root and
Administrator access administrators remain fixed as a security protection.

Access permission tokens
Table 4 lists the permission tokens you can control with Access Control
Administration.
Table 4 Access permission tokens
Token name Provides access to…
ACCESS_CONTROL InfoCenter Access Control Administration window.

BAY_SECURE BaySecure LAN Access application.
COMMUNITY_STRINGS InfoCenter Community Strings Editor window.
CV_VIEW Call View ATM window.
DB_ADMIN_ACCT InfoCenter Database Admin Tool.
DISCOVERY_ADMIN Lets users configure rediscovery preferences and auto
rediscovery parameters, stop all discoveries including
discoveries started by other users, view log messages,
change discovery preferences. Can only be assigned with
read/write permission.
DIV Device Inventory Viewer.
FS_ACCESS Fault Summary application.
IC InfoCenter folder manipulation.
IC_ADMIN InfoCenter folder access and Monitor Options window
NPT_ACCESS InfoCenter Path Trace window.
OM_READ_STATS OmniView read statistics and preferences.
OM_SNMP_SETS OmniView SNMP Set actions.
OM_CONF_ALLUSERS OmniView global templates.
OM_CONF_TEMPL OmniView individual templates.
SE_READ_STATS Expanded View read statistics and preferences
SE_SNMP_SETS Expanded View SNMP Set actions.
SERVICE_ASSIGN Lets users assign services to other users. Can only be
assigned with read/write permission.
TOPUI_ACCESS Lets users run topology discovery.
TDC_READ_STATS TD Continuity Read Stats and preference changes
TDC_SNMP_SETS TD Continuity SNMP set actions.
VIEW_DOMAIN_MGMT Lets users create, delete, edit, and assign view domains to
other users. Can only be assigned with read/write
permission.
207569-F
Starting Access Control Administration
To start Access Control Administration:
1 Take one of the actions shown in Table 5.
Table 5 Starting Access Control Administration
To start Access
Control
Administration
from: Do this:
InfoCenter Choose Admin > Access Control
Note: If the Access Control menu command is disabled, it means

you do not have the proper access permissions to use Access
Control Administration.
Windows Start Choose Start > Programs > Optivity > AccessAdmin
menu
Windows cd %lnmshome%\bin
command prompt
accessadmin
UNIX command cd $LNMSHOME/bin
prompt
accessadmin
Web browser Point your Web browser to:
http://[IP or hostname of ONMS server]
Click the Access Control Administration icon on the Optivity Web

page.
Note: You can use your Web browser’s Bookmark or Favorites

feature to bookmark the Access Control Administration application.
Doing so saves the URL for Access Control Administration.
If you are not starting Access Control Administration from InfoCenter, the
Connect to Optivity Server dialog box opens.
2 If prompted, enter your login information and click OK.
The Access Control Administration window opens.

To begin using Access Control Administration features, enable access control. See
“Enabling and disabling access control” on page 85 for more information.
Access Control Administration window
The Access Control Administration window has six parts as shown in Figure 3.
Figure 3 Access Control Administration window
Menu bar and

toolbar
Optivity Users
pane
Permission
pane
Permission
Groups pane
Status bar
207569-F
Table 6 describes the Access Control Administration window parts.
Table 6 Parts of the Access Control Administration window
Part Description
Menu bar and toolbar Provides access to all available commands.

See “Menu bar and toolbar‚” next for information about the menu
commands and toolbar buttons.
Optivity Users pane Lists the system users configured to use Optivity NMS.
See “Optivity Users pane” on page 83 for more information.
Permission pane Lists the permission tokens configured for a selected Optivity user
or permission group.
See “Permission pane” on page 83 for more information.
Permission Groups Lists the permission groups configured.
pane See “Permission Groups pane” on page 84 for more information.
Status bar Provides information about current activity in the window,
including the Optivity NMS server host name, user name, and
whether Access Control Administration features are enabled or
disabled.
See “Status bar” on page 84 for more information.
Menu bar and toolbar
The Access Control Administration menu bar and toolbar let you configure access
permissions, change the appearance of the Access Control Administration
window, get online Help, and exit the window.
If you open Access Control Administration in a Web browser, the menu bar does
not display. Instead, you use the Menu tool on the toolbar to open a shortcut menu
of Access Control Administration menus.
Table 7 describes the menu bar commands and toolbar buttons.
Table 7 Access Control Administration menu commands and toolbar buttons
Toolbar
Menu Command Description
button
File Exit Exits Access Control Administration.

Table 7 Access Control Administration menu commands and toolbar buttons (continued)
Toolbar
button
View Display Turns the display of the toolbar on and off in the Access Control
Toolbar Administration window.
Display Status Turns the display of the status bar on and off in the Access Control
Bar Administration window.
Look and Feel Provides options for choosing a familiar window interface Access
Control Administration window interface. You can choose Metal,
CDE/Motif, or Microsoft Windows as the user interface type.
Actions Add/Remove Opens the Add/Remove Optivity Users dialog box, where you can
Optivity Users add or remove users who can log in to Optivity NMS.
See “Adding Optivity NMS users” on page 86, and “Removing
Optivity users” on page 87 for more information.
Add Opens the Add Permission Group dialog box, where you can
Permission create a new permission group.
Group See “Adding permission groups” on page 91 for more information.
Attach/Detach Opens the Attach/Detach Permissions dialog box, where you can
Permission attach and detach individual permission tokens to or from users or
permission groups.
See “Attaching and detaching permissions” on page 89 for more
information.
Attach Opens the Attach Permission Group dialog box, where you can
Permission attach a permission group to an Optivity NMS user.
Group See “Attaching permission groups” on page 93 for more
information.
Assign View Opens the Assign View Domains and Services dialog box to let
Domain you assign view domains to Optivity NMS users. See “Assigning
view domains to ONMS users” on page 95 for more information.
Assign Opens the Assign View Domains and Services dialog box to let
Services you assign services to Optivity NMS users. See “Assigning
services to ONMS users” on page 97 for more information.
Access Opens the Access Control Switch dialog box, where you can
Control enable or disable access control.
Switch See “Enabling and disabling access control” on page 85, for more
information.
207569-F
Table 7 Access Control Administration menu commands and toolbar buttons (continued)
Toolbar
button
Help Access Opens the Access Control Administration window Help.
Control Help
Using Help Displays a Help topic describing how to use the Access Control
Administration window Help system.
About Access Displays the startup screen for the Access Control Administration
Control window. This screen includes copyright and version information.
Administration
Optivity Users pane
The Optivity Users pane, located in the upper left area of the Access Control
Administration window, lists all system users configured for Optivity NMS
access.
Permission pane
The Permission pane, located on the right side of the Access Control
Administration window, lists the Optivity NMS application tokens currently set
for a user or permission group. The table in the Permission pane contains the
token name, current permission setting, and a brief description of each token.
To view the tokens configured for a user:
Click the user name in the Optivity Users pane.
To view the tokens configured for a permission group:
Click the group name in the Permission Groups pane.
To change the permission setting of a listed token:
1 Right-click the permission setting.

A shortcut menu opens.
2 Choose Read/Write or Read Only.

Permission Groups pane
The Permission Groups pane, located in the lower left area of the Access Control
Administration window, lists configured permission groups.
Select a permission group by clicking the group name. The current permission
settings for that group are displayed in the Select a permission group by clicking
the group name. The current permission settings for that group are displayed in
the Permission pane.
The default groups are:
• OPTIVITY_ADMIN (all tokens read/write)

• OPTIVITY_VIEW (all tokens read-only)
Status bar
The status bar, located along the bottom of the Access Control Administration
window, lists:
• The result of the most recent operation (usually this value is “OK”)
• The Optivity NMS server host name
• The current user name
• Whether Access Control Administration features are enabled or disabled
Working with Access Control Administration

The following sections describe how to work with Access Control Administration:
• “Enabling and disabling access control‚” next

• “Adding Optivity NMS users” on page 86
• “Removing Optivity users” on page 87
• “Setting user permissions” on page 88
• “Changing permission settings” on page 89
• “Attaching and detaching permissions” on page 89
• “Adding permission groups” on page 91
207569-F
• “Attaching permission groups” on page 93

• “Changing permission groups” on page 95
• “Assigning view domains to ONMS users” on page 95
• “Assigning services to ONMS users” on page 97
• “Changing the look and feel of the window” on page 98
Enabling and disabling access control
Access control is disabled by default. With access control disabled, any user with
a valid system user ID can access any Optivity NMS component. To use Access
Control Administration features you must turn on access control.
Note: Only Optivity NMS access administrators or users with read/write

access control permission to the ACCESS_CONTROL token can enable
access control.
To enable access control on the connected Optivity NMS server:
1 If you have not already done so, start Access Control Administration. For
more information, see “Starting Access Control Administration” on page 79.
2 On the Access Control Administration toolbar, click Access Control Switch.
The Access Control Switch dialog box (Figure 4) opens. The dialog box
shows the whether access control is enabled or disabled, and prompts whether
you want to change it.
Figure 4 Access Control Switch dialog box (enabled and disabled)
For detailed information about the Access Control Switch dialog box, click
Help in the dialog box.

3 Click OK to change the state of access control, or click cancel to leave it as it

is.
Note: After you enable access control, only root and Administrator can
access Optivity NMS. You must add users and configure their permission
tokens to allow access to other Optivity users.
If you disable access control after configuring permission settings, the

most recent configuration is active if you re-enable access control.
Note: After you change the access control state, users who are logged
into InfoCenter and Autotopology Manager are prompted to log out and
reconnect.
Adding Optivity NMS users
When you first enable access control, the default Optivity NMS users are
Administrator and root. No other system user can log in to view or modify
Optivity NMS database objects.
Note: Only users with read/write permission to the

ACCESS_CONTROL token can enable access control.
To add an Optivity NMS user:
1 Open the Access Control Administration window.

For more information, see “Starting Access Control Administration” on
page 79.
2 Open the Add/Remove Optivity Users dialog box (Figure 5) in one of the
following ways:
• From the Access Control Administration menu bar, choose
Actions > Add/Remove Users.
• On the toolbar, click Add/Remove Users.
207569-F
Figure 5 Add/Remove Optivity Users dialog box
For detailed information about the Add/Remove Optivity Users dialog box,
click Help in the dialog box.
3 Type a user name or select a user to add from the Local Users or System Users
list.
4 Click the > button between the two lists to move the selected user into the
Optivity Users list.
5 When you are done adding users, click Close.
6 Set access permissions for the new user.
See “Setting user permissions” on page 88 for more information.
Removing Optivity users

When you delete an Optivity user, the user can no longer access any Optivity
NMS applications unless you disable Access Control Administration.

ACCESS_CONTROL token can remove an Optivity user. You cannot
delete Administrator, root, or your own user name.

To remove an Optivity user:

page 79.
2 Open the Add/Remove Optivity Users dialog box in one of the following
ways:
Actions > Add/Remove Users.
• On the toolbar, click Add/Remove Users.
For detailed information about the Add/Remove Optivity Users dialog box,
3 Select a user in the Optivity Users pane.

4 Click the < button between the two lists to remove the selected user from the
Optivity Users list.
5 Click OK.
Setting user permissions
After you add an Optivity NMS user, you must add tokens for the Optivity NMS
components the user can access.
Choose one of the following methods:
• Attach the preconfigured set of tokens in a permission group.

To attach a permission group to an Optivity user, see “Attaching permission
groups” on page 93.
• Attach the token for each Optivity NMS application the user will access.
To attach user tokens individually, see “Attaching and detaching permissions”
on page 89.

ACCESS_CONTROL token can configure access permissions.
207569-F
Changing permission settings

After you assign tokens for a user or permission group, you can change the
read-only or read/write permission value of each token.

To change the permission setting of a configured token:

page 79.
2 Select an Optivity user in the Optivity Users pane or a permission group in the
Permission Groups pane.
3 Select a token in the Permission pane.
4 To the right of the token name, right-click in the Permission column.
A shortcut menu opens.
5 Choose Read/Write or Read Only.
Note: To grant access to any InfoCenter component, you must also grant
access to the IC and IC_ADMIN tokens. To restrict user access to
components, be sure to deny read/write access to the
ACCESS_CONTROL token for that user. Otherwise, the user can set
their own permissions in the Access Control Administration window.
Attaching and detaching permissions

To configure access permissions for Optivity users and permission groups, do the
following:
• Attach or detach the permission tokens for Optivity NMS applications.

• Set the attached tokens to read-only or read/write access.

To attach and detach permission tokens for an Optivity user or permission group:

page 79.
Select a user in the Optivity Users pane or a permission group in the

Permission Groups pane.

2 Open the Attach/Detach Permissions dialog box (Figure 6) in one of the

following ways:
Actions > Attach/Detach Permissions.
• On the toolbar, click Attach/Detach Permissions.
207569-F
Figure 6 Attach/Detach Permissions dialog box.
For detailed information about the Attach/Detach Permissions dialog box,

3 Attach or detach tokens.

• To attach a token, select the token in the All Available Permission pane;
then, click the >>> button.
• To detach a token, select the token in the Attached Tokens pane; then,
click the <<< button.
Adding permission groups
You create permission groups to establish preconfigured sets of permission

tokens. You can then attach the permission group to Optivity users who have
similar access requirements rather than attaching each permission token to each
user.

The default OPTIVITY_ADMIN permission group contains all of the available

tokens set to read/write access. The default OPTIVITY_VIEW permission group
contains all tokens set to read-only.
Note: Only users with read/write access to the ACCESS_CONTROL

token can configure permission groups.
To add a permission group:

page 79.
2 Open the Add Permission Group dialog box (Figure 7) in one of the following
ways:
Actions > Add Permission Group.
• On the toolbar, click Add Permission Group.
Figure 7 Add Permission Group dialog box
For detailed information about the Add Permission Group dialog box, click
3 Enter a group name.

4 Click Add.
The new group name is now displayed in the Permission Groups pane.
5 Attach the permission tokens for this group.

See “Attaching and detaching permissions” on page 89.
207569-F
Attaching permission groups
Attach a permission group to quickly assign a preconfigured set of tokens to one

or more Optivity user. After you attach the permission group, you can customize
the configured permissions for each user as necessary.

ACCESS_CONTROL token can attach a permission group. Group
permissions override any previously configured user tokens.
To attach a permission group to an Optivity user:
1 Select a user in the Optivity Users pane.

2 Open the Attach Permission Group dialog box (Figure 8) in one of the
following ways:
Actions > Attach Permission Group.
• In the toolbar, click Attach Permission Group.

Figure 8 Attach Permission Group dialog box
For detailed information about the Attach Permission Group dialog box, click
3 Select a group in the All Available Groups list.

4 Click the >>> button to move the tokens for the selected group to the Attached
tokens list.
The Tokens For This Group pane lists all available tokens and their current
permission settings. The Attached Tokens pane lists the tokens currently
attached to the selected permission group.
5 If necessary, customize the permission group.

See “Changing permission groups” on page 95 for more information.
6 Click OK.
207569-F
Changing permission groups
After you create a permission group and attach its tokens, you can modify the
permission group by:
• Attaching or detaching additional tokens

See “Attaching and detaching permissions” on page 89 for more information.
• Changing the permission level of one or more tokens
See “Changing permission settings” on page 89 for more information.

ACCESS_CONTROL token can configure permission groups.
Assigning view domains to ONMS users
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. See “Working with view domains”
on page 161 for more information about creating and changing view domains.
Note: In order to assign view domains to ONMS users:

• Access Control must be enabled. See “Enabling and disabling access
control” on page 85 for more information.
• You must have read/write permission to the
VIEW_DOMAIN_MGMT token to assign view domains. See
“Access permission tokens” on page 78 for more information.
To assign view domains to ONMS users:
1 In Access Control Administrator, choose Actions > Assign view domain.

The Assign View Domains and Services dialog box opens with the View
Domain tab forward (Figure 9).

Figure 9 Assign View Domains and Services dialog box (View domain tab
shown)
2 From the Users menu, choose the user to whom you want to assign the view
domain.
3 In the Available View Domains list, choose one or more view domains by
clicking or with Shift+Click and Ctrl+Click.
4 Use the >> and > buttons to move the selected view domains from the
Available View Domains list to the User’s View Domains list.
5 Click OK to apply your changes and close the dialog box, or click Apply to
apply your changes but leave the dialog box open.
The view domains are automatically added to the user views. Users who are
connected to InfoCenter see the changes without having to log-off from
InfoCenter.
207569-F
Assigning services to ONMS users
Note: In order to assign view domains to ONMS users:

• Access Control must be enabled. See “Enabling and disabling access
control” on page 85 for more information.
• You must have read/write permission to the SERVICE_ASSIGN
token to assign view domains. See “Access permission tokens” on
page 78 for more information.
To assign services to ONMS users:
1 In Access Control Administrator, choose Actions > Assign service.

The Assign View Domains and Services dialog box opens with the Service tab
forward (Figure 10).
Figure 10 Assign View Domains and Services dialog box (Service tab shown)
2 Use the check boxes in the Service tab table to assign services to Optivity
NMS users.
3 Click OK to apply your changes and close the dialog box, or click Apply to
apply your changes but leave the dialog box open.

When you change service allocations for any Optivity NMS users that are
using InfoCenter, the Service Allocation Changed dialog box (Figure 11)
opens to alert them to the change. They must exit and restart InfoCenter in
order to view or manage the new services.
Figure 11 Service Allocation Changed dialog box
Changing the look and feel of the window
Access Control Administration lets you change the look and feel of the Access
Control Administration window to best match the operating system under which it
is running.
To change the look and feel of the Access Control Administration window:
1 From the Access Control Administration menu bar, choose View > Look and
feel.
The Look and Feel shortcut opens.
2 Choose the selection that best matches your computing environment.
Troubleshooting Access Control Administration

The following sections describe how to troubleshoot Access Control
Administration problems:
• “Resolving problems‚” next

• “Error messages” on page 99
207569-F
Resolving problems
Table 8 suggests techniques for resolving problems or interpreting unexpected

results.
Table 8 Access Control Administration problems and resolutions
Problem Resolution
An Optivity user cannot Optivity users require access to launch InfoCenter. Log in as an
launch InfoCenter. Optivity Administrator to add InfoCenter to the user’s list of
access tokens.
An Optivity user cannot Log in as an Optivity Administrator to add IC_ADMIN to the
open InfoCenter user’s list of access tokens.
Administration menus.
The Access Control The application control database was not properly set up
Administration window during postinstallation. Contact the Technical Support Center.
opens empty, without Access Control Administration requires the following items to
default permission operate properly:
tokens or access
administrator users in • Db/AppControlDB.db/access.schema
the User and Permission • registration/webpotsrvr/access_admin.reg
panes.
The toolbar buttons When you drag the Access Control Administration toolbar to a
have the wrong different location and then change the Look and Feel setting,
background color. the toolbar buttons sometimes retain the color of the previous
setting. The toolbar button background color has no effect on
the operation of the application.
Error messages
Table 9 describes the error messages you might encounter while using the Access
Control Administration window.
Table 9 Common Access Control Administration error messages
Error message Description
Access Admin. cannot remove You cannot remove root or Administrator

this user. users.
You may not change any of the You cannot remove or change the
superuser permissions. permission setting for any root or
Administrator tokens.

100 Chapter 2 Specifying access to Optivity NMS applications with Access Control Administra-
Table 9 Common Access Control Administration error messages (continued)
Error message Description
Login name starting with You cannot use spaces when specifying
blanks or trailing blanks. an Optivity username.
Extra blanks are removed.
Login name must be less than 50 When you add an Optivity user, you
characters. Try again. cannot use more than 50 characters to
specify the user name.
Permission group name must be When you add a permission group, you
less than 50 characters. Try cannot use more than 50 characters to
again. specify the group name.
207569-F
101
Chapter 3
Specifying access to devices with the Community
Strings Editor
• “Community Strings Editor overview‚” next

• “Getting started with the Community Strings Editor” on page 102
• “Working with the Community Strings Editor” on page 116
• “Troubleshooting the Community Strings Editor” on page 135
Community Strings Editor overview

The Community Strings Editor lets you add, delete, modify, or rearrange
non-default SNMP read and read/write community strings that control access to
your network devices. Use the Community Strings Editor to manage non-default
community strings, so that Optivity NMS applications can discover and access
devices that use those community strings.
You can also use the Community Strings Editor to import and export community
strings to and from files. This feature lets you easily exchange lists of community
strings with other Optivity NMS server, or with HP OpenView platforms. For
more information, see “Importing a community strings file” on page 131 and
“Exporting a community strings file” on page 133.

102 Chapter 3 Specifying access to devices with the Community Strings Editor
The Community Strings Editor also supports the SNMPv3 user security model
(USM) that lets you administer user security to accommodate your network
requirements. The USM lets you specify authentication and privacy security
features for:
• Each user
• Multiple users for a specific IP or a range of IP addresses
• A single Optivity user for trap registration
The Community Strings Editor stores information about community strings and
security in the Optivity NMS topology database.
Getting started with the Community Strings Editor

The following sections introduce the Community Strings Editor and tell how to
• “About community strings‚” next

• “Default community strings” on page 104
• “About user security” on page 106
• “Starting the Community Strings Editor” on page 108
• “Access permissions for Community Strings Editor” on page 109
• “Community Strings Editor window” on page 110
• “IP address syntax” on page 104
• “Understanding wildcards” on page 105
About community strings
In an SNMP network, SNMP community strings control management access to

network devices.
An SNMP community is a logical relationship between SNMP agent software

running on network devices and one or more SNMP management station. Each
device agent limits access to its management information base (MIB) by defining
read only and read/write communities with specific ASCII text strings as
passwords—the SNMP community strings.
207569-F
Chapter 3 Specifying access to devices with the Community Strings Editor 103
• Read-only community members can view configuration and performance

information in the MIB.
• Read/write community members can view and change configuration and
performance data.
Communication between an SNMP management station and managed devices

works as follows:
• When an application needs information from a managed device, it reads the

management station community strings database, finds a match for the device
IP address, and retrieves the community string.
• The management station sends an SNMP message to the device that includes
the community string.
• The device agent verifies that the management station is using the correct
read-only or read/write password (community string).
• If the password is correct, the agent allows the management station read or
write access to the device management information base (MIB). Otherwise, it
denies access.
Figure 12 shows this process.
Figure 12 Community strings and SNMP
Hub device
SNMP Management agent SNMP
community station community
string: ny string: ny
SNMP Get with community string = ny
Community string is validated, SNMP get response.

5709

Default community strings
Many network devices are configured with default community strings:
• The default read community string is Public.

When a device read community string is set to Public, every management
station has read access to the device MIB.
• The default write community string is Private.
When a device read/write community string is set to Private, the device denies
write access to all management stations.
To configure the Optivity NMS server with write access to a particular device
MIB, you must change the default Write community string. First change the
community string for the device agent, then add or change the Optivity NMS
server community string for that device.
After you initially set the SNMP community strings for your network, you may
want to change them periodically for enhanced security.
IP address syntax
Each 32-bit IP address contains four octet values that together specify the network
address ID and the host ID for a device.
Use the following format to specify IP addresses in the community strings table or
in the IP Range Table:
<value>.<value>.<value>.<value>
where each <value> is one of the following:
• An integer 0 to 255.
• A range of valid integer values. For example, 120-127.
The dash (-) is the only valid character to indicate a range.
• An asterisk (*) wildcard to match the range 0-255.
The asterisk (*) is the only valid wildcard character.
207569-F
Understanding wildcards
When you configure a community string, you can specify a wildcard as one or
more octet in the device IP address. For example, use wildcards to specify a group
of network or host IDs that use the same community string.
To communicate with a managed device, Optivity NMS reads the community

strings table to find a match for the IP address. A wildcard matches all values for a
particular octet. You can specify 1 to 4 wildcards in an IP address. The wildcard
character is the asterisk (*).
How you order IP addresses within the IP Range Table affects the way Optivity
matches address entries to hosts in the network. Address matching begins with the
first entry in the table. Make sure that IP addresses that contain wildcards do not
overlap or exclude other IP address entries in the table.
Table 10 shows some examples of how IP address matching works with and
without wildcards.
Table 10 Community string matching examples
IP address Description
134.177.125.31 Matches only the specified IP address.

134.177.125.1-31 Matches all addresses in the range 134.177.125.1 to
134.177.125.31.
134.177.125.* Matches all addresses in the range 134.177.125.1 to
134.177.125.255.
134.177.125-128.* Matches all addresses in the range 134.177.125.* to
134.177.128.*
*.*.*.* Matches all addresses. This is usually the last entry in the
community strings table, used to specify default community strings
for devices without specific entries in the table.

About user security
The Community Strings Editor implements the SNMPv3 USM defined in RFC
2574, and supports three important USM security services: authentication,
privacy, and access control. To deliver these services in a flexible and efficient
manner, the USM introduces the concept of a principal, which is the entity on
whose behalf services are provided or processing takes place.
A principal can be any of the following:
• An individual acting in a particular role

• A set of individuals, with each acting in a particular role
• An application or set of applications, or a combinations thereof
In essence, a principal operates from a management station and issues SNMP

commands to agent systems. The identity of the principal and the target agent
together determine the security features that are invoked, including:
• Authentication
• Privacy
• Access control
The use of principals allows security policies to be tailored to the specific

principal, agent, and information exchange (Figure 13), and gives security
managers considerable flexibility in assigning network authorization to users.
The principal in the USM is represented by a user, who is identified by user name.
207569-F
Figure 13 SNMPv3 security features
Transmission from manager

to agent can be authenticated
Manager to guarantee identity of sender Agent
and integrity and timeliness
of message
Agent
Manager
DES encryption
SNMPv3 messages
can be encrypted
to ensure privacy
Agent enforces access-control

policy to restrict each principal
Agent
to certain actions on certain
portions of its data
Manager 10689EB
Understanding user security services
The Community Strings Editor lets you administer authentication and privacy
security services to protect your network against the following threats:
• Modification of Information—An entity could alter an in-transit message

generated by an authorized entity in such a way as to effect unauthorized
management operations, including the setting of object values.
• Masquerade—Unauthorized management operations attempted by an entity
masquerading as an authorized entity
• Message Stream Modification—SNMP is designed to operate over a
connectionless transport protocol. There is a threat that SNMP messages
could be reordered, delayed, or replayed (duplicated) to effect unauthorized
management operations.
• Disclosure—An entity could observe exchanges between a manager and an
agent and thereby learn the values of managed objects and learn of trap
events.

Community strings security does not provide protection against the threats listed
above.
Starting the Community Strings Editor
To start the Community Strings Editor:
Table 11 Starting Community Strings Editor
To start
Community
Strings Editor
from: Do this:
InfoCenter Choose Admin > Community Strings
Note: If the Community Strings Editor menu command is disabled, it

means you do not have the proper access permissions to use
Community Strings Editor.
Windows Start Choose Start > Programs > Optivity > CommunityString
menu
command prompt
comstrings
prompt
comstrings
Click the Community Strings Editor icon on the Optivity Web page.

feature to bookmark the Community Strings Editor application.
Doing so saves the URL for Community Strings Editor.
If you are not starting Community Strings Editor from InfoCenter, the
207569-F
The Community Strings Editor window opens.
Access permissions for Community Strings Editor
When access control is enabled on the Optivity NMS server, the Community
Strings Editor requires the following permission tokens:
• IC
• IC_ADMIN
• COMMUNITY_STRINGS
Table 12 shows the level of access a user has with read-only, read/write, or no
access to the three required permission tokens.
Table 12 Access permissions
Permission Access
None No access. The Community String Editor window does not open.
Read only User can view the Community strings table, but cannot add, delete,
modify, or change the order of entries. Import, export, and save
commands are also disabled.
Read/write User has full access to all features of the Community Strings Editor.

Community Strings Editor window
The Community Strings Editor window has two views: Individual view and Table
view.
Figure 14 shows the Individual view.
Figure 14 Community Strings Editor—Individual view
Menu bar
Toolbar
Specific IP
table
Entry
Details
area
IP range
table
Status bar
207569-F
Figure 16 shows the Table view.
Figure 15 Community Strings Editor window—Table view
Menu bar
Toolbar
Security
type tabs
Specific IP
Table
IP Range
Table
User Details
area (SNMP
tab only)
Table 13 describes the parts of the Community Strings Editor window.
Table 13 Parts of the Community Strings Editor window
Part Description
Menu bar Provides access to all available Community Strings Editor commands.
See “Menu bar and toolbar” on page 112 for more information.
Toolbar Provides quick access to commonly used Community Strings Editor
commands.

Table 13 Parts of the Community Strings Editor window (continued)
Part Description
View area Shows you the community string entries in either the Individual view or the
Table view. See “Table view” on page 114 and “Individual view” on page 115
for more information.
Status bar Displays information about the selected menu bar command, the server
hostname, user name and access privileges.
See “Status bar” on page 116 for more information.
The Community Strings Editor menu bar and toolbar contain commands that let
you add and manipulate SNMP non-default community strings that are stored in
the Optivity application control database.
Table 14 shows the menu names, command names, toolbar buttons, and command
descriptions.
Table 14 Menu bar commands and toolbar buttons
Toolbar
button
Menu Opens the Community Strings Editor menu in a Web browser.
File Import Data Imports a new community strings file, overwriting any existing
community strings configured for the Optivity NMS server. You can
import community strings files in both Optivity and HP OpenView*
.CSV file format.
See “Importing a community strings file” on page 131 for more
information.
Export Data Exports the existing community strings information in the Optivity
database to a file to the server file system. You can export
community strings files in both Optivity and HP OpenView.CSV file
format.
See “Exporting a community strings file” on page 133 for more
information.
Save Saves all community string entry changes that you have made in the
Community Strings Editor window to the Optivity application control
database.
See “Saving changes” on page 124 for more information.
Exit Closes the Community Strings Editor window.
207569-F
Table 14 Menu bar commands and toolbar buttons (continued)
Toolbar
button
Edit New Opens the Configure Community Strings Entry dialog box to let you
create a new community strings entry.
See “Adding a new community string entry” on page 117 for more
information.
Edit Opens the selected entry in a Configure Community Strings Entry
dialog box to let you edit the entry.
See “Modifying a community string entry” on page 120 for more
information.
Delete Deletes the selected community strings entry.
See “Deleting a community string entry” on page 121 for more
information.
Reset Discards all of the changes you have made since the last save. See
“Resetting changes” on page 123 for more information.
Refresh Refreshes the Community Strings Editor display with current

information from the Optivity NMS database. Also discards all of the
changes you have made since the last save. See “Refreshing the
display” on page 123 for more information.
View Display Toolbar Shows or hides the toolbar.
Display Status Shows or hides the status bar.
Bar
View Type Opens a submenu that lets you choose either of two view types:
• Table
• Individual
Look and Feel Changes the appearance of the Community Strings Editor window.
A submenu opens—Metal, CDE/Motif, and Windows—for you to
select the appearance command that you want. The default option is
Windows.
Help Community Opens the Community Strings Editor online Help.
Strings Editor
Help
Using Help Opens online Help about how to use the Community Strings Editor
online Help.
About Displays the software version and copyright information for the
Community Community Strings Editor application.
Strings Editor

View Area
The following sections describe the two types of view shown in the view area of
the Community Strings Editor:
• “Table view‚” next

• “Individual view” on page 115
While using either view, you can easily modify any community strings entry by
double-clicking the entry. Doing so opens the entry in a Configure Community
Strings Entry dialog box. You can also add, modify, or delete entries using the
Edit menu or the shortcut menu that opens when you right-click an entry. See
“Working with community strings entries” on page 117 for more information.
Table view
The table view shows you at a glance all of the community string entries and their
settings for any of the three supported security types. This view has one tab for
each security type. Each tab shows you all of the community string entries and
their settings for the security type.
For every tab, the table view shows a Specific IP table and an IP range table. The
columns of the table show the settings for the security type. The following table
describes the parts of the SNMP tab in the table view.
207569-F
Table 15 describes the parts of the table view.
Table 15 Parts of the table view
Part Description
SNMP tab • Shows whether Optivity NMS uses SNMPv1 traps if SNMPv3 trap
registration fails. See “Selecting SNMPv1 traps if SNMPv3 trap
registration fails” on page 128 for more information.
• Shows for each entry:
— IP address or IP range for the entry
— SNMP read and write community strings
— Timeout interval and retry number
— Whether the device or range is SNMPv3 aware
See “Working with community strings entries” on page 117 and “Working
with SNMPv3 users” on page 124 for more information.
Telnet tab Shows for each entry:
• Telnet user name, password, and privileged password
• Telnet Timeout interval, retry number, and prompt
See “Working with Telnet and SSL settings” on page 129 for more
information.
SSL tab Shows for each entry the SSL user name, password, and port See “Working
with Telnet and SSL settings” on page 129 for more information.
Individual view
The individual view shows all of the SNMP, Telnet, and SSL settings for a
selected community string entry.
Table 16 describes the parts of the individual view.
Table 16 Parts of the individual view
Part Description
Specific IP list Lists all of the community strings entries for specific devices

Table 16 Parts of the individual view (continued)
Part Description
IP range list Lists all of the community strings entries for ranges of devices
Details area This area on the right side of the view shows the following settings for
the selected entry in the Specific IP list or the IP range list:
• IP address or IP range for the entry
• SNMP read and write community strings
• Timeout interval and retry number
• Whether the device or range is SNMPv3 aware
• Details for all SNMPv3 users
• Telnet user name, password, and privileged password
• Telnet Timeout interval, retry number, and prompt
• SSL user name, password, and port
See “Working with community strings entries” on page 117 for more
information about modifying the settings for the entry or for or adding
new entries.
Status bar
The status bar in the Community Strings Editor window displays the following
information:
• Toolbar and menu command descriptions

• Error and information messages.
• Whether you are currently connected to the Optivity NMS server
• Current user name.
• Your Access Control privileges.
Working with the Community Strings Editor

The Community Strings Editor lets you set up SNMP configuration options to
support your network arrangement. The following sections describe how to
configure community strings and user details:
• “Working with community strings entries‚” next

• “Working with SNMPv3 users” on page 124
207569-F
• “Working with Telnet and SSL settings” on page 129

• “Importing and exporting community strings” on page 130
Working with community strings entries
The following sections describe how to perform basic operations with community
strings entries:
• “Adding a new community string entry‚” next

• “Modifying a community string entry” on page 120
• “Deleting a community string entry” on page 121
• “Changing the order of community string entries” on page 121
• “Resetting changes” on page 123
• “Refreshing the display” on page 123
• “Saving changes” on page 124
Adding a new community string entry
Add community string entries or devices or ranges of devices in your network that
use non-default SNMP community strings. If devices on your network use default
community strings, you do not need to add entries for them.
At a minimum, you must configure basic SNMP settings for every entry.
Additionally, you can configure SNMPv3 users, Telnet settings, and SSL settings
for entries.
To add a new community string entry:
1 Do one of the following:

• On the toolbar, click Create New Entry
• On the menu bar, choose Edit > New
The Configure Community Strings Entry dialog box opens (Figure 16).

Figure 16 Configure Community Strings Entry dialog box
2 In the IP Address text box, type a valid IP address (Figure 17).
Figure 17 IP address text box
The Community Strings Editor checks the IP address for correct syntax.
207569-F
See “IP address syntax” on page 104 and “Understanding wildcards” on

Note: Community string matching begins with the first entry in the
table. When you add a new community string, place entries with
wildcards carefully.
3 Enter the read and read/write community strings for the device (Figure 18).
Figure 18 Read and write community strings text boxes
The strings must be 50 characters or less.
4 Type a timeout interval between 1 and 99 seconds to specify the amount of

time the management application waits for a response before attempting to
retry the SNMP request.
The value must be an integer.
5 Type a retry value between 1 and 99 to specify the maximum number of

retries the management application attempts before designating the device as
unreachable.
The value must be an integer.
6 (Optional) Configure SNMPv3, Telnet, and SSL settings for the entry. For
more information, see:
• “Adding SNMPv3 users to an entry” on page 125
• “Configuring Telnet settings for an entry” on page 129
• “Configuring SSL settings for an entry” on page 130
7 Click OK.
Community Strings Editor closes the Configure Community Strings Entry
dialog box and adds the entry to either the Specific IP Table or the IP Range
Table as appropriate.


• From the menu bar, choose File > Save.
• On the toolbar, click Save.
Community Strings Editor applies your changes to the Optivity NMS
database.
Modifying a community string entry
You can change any value in a non-default SNMP community string entry in the
community strings table. When you click the Change button, the change is added
to the Community strings table.
To modify a community string entry:
1 In any Community strings table, chose the community string entry you want
to change.
You can choose an entry from any of the following locations:
• Specific IP list (individual view)
• IP range list (individual view)
• Specific IP list (any tab of the table view)
• IP range list (any tab of the table view)
• Double-click the entry
• Right-click the entry and choose Edit from the shortcut menu.
• Click the entry and click Edit selected entry on the toolbar.
• Click the entry and choose Edit > Edit on the menu bar.
The entry opens in a Configure Community Strings Entry dialog box.
3 Enter your changes in the dialog box. For more information, see “Modifying
an SNMPv3 user” on page 126, “Configuring Telnet settings for an entry” on
page 129, and “Configuring SSL settings for an entry” on page 130.
4 Click OK.
dialog box and modifies the entry on the Specific IP Table or the IP Range
Table.
207569-F

database.
Deleting a community string entry
You can delete any non-default SNMP community strings entry in either the
Specific IP Table or the IP Range Table.
To delete a community string:
1 In either the either the Specific IP Table or the IP Range Table, click a row.
The row is highlighted.
2 Click Delete.
The table row entry is deleted.

database.
Note: You cannot delete the default entry (*.*.*.*).
Changing the order of community string entries

You can change the order of nondefault community strings entries in the
community table with wildcard IP addresses.
Optivity Autotopology searches for non-default SNMP community string entries

with exact IP addresses first, then searches for community string entries with
wildcard IP addresses. Higher entries in the table are evaluated before lower
entries.

Table 17 shows examples of how Optivity NMS responds to the order of IP

addresses.
Table 17 Community string order example
IP address Read community Result
134.177.123.* public1 For a community string fetch for

134.177.123.122, public1 is selected.
134.177.*.* public2
134.177.*.* public2 For a community string fetch for
134.177.123.122, public2 is selected
134.177.123.* public1
See “Understanding wildcards” on page 105 for more information.
To change the order of community string entries in the community strings table:
1 In any IP range list or table, select the community string entry or entries you
want to move.
You can choose an entry from any of the following locations:
• IP range list (individual view)
• IP range table (any tab of the table view)
You can choose more than one entry at a time using Ctrl+click and
Shift+click.
When you select entries in the IP range list or table, the Community Strings
Editor enables the Up and Down arrow buttons.
2 Click Up or Down to move the entry or entries to the desired position
(Figure 19).
Figure 19 Up and Down buttons below IP Range list or table
Each click moves the entry or entries one position in the table.
207569-F

database.
Resetting changes
Changes that you make in the community strings table are temporarily stored in
memory.
To discard all changes and reset the table to the last saved set of community
strings:
Click Reset.
Note: Once you reset the table, all changes since the last save are lost.
To keep your changes, you must use the toolbar or menu bar Save
command before you exit the Community Strings Editor window.
Refreshing the display
Use the refresh feature to reload the Community Strings Editor display with the
latest community strings information from the Optivity NMS database. This
feature is useful if changes have been made to the database since the Community
Strings Editor was last opened or refreshed. However, refreshing the display
discards any changes you have made since the last save. So you may want to save
the current changes before you refresh the display.
To discard all changes and refresh the Community Strings Editor display from the
Optivity NMS database:
Click Reset.

Note: Once you refresh the display, all changes since the last save are
lost. To keep your changes, you must use the toolbar or menu bar Save
command before you exit the Community Strings Editor window.
Saving changes
Changes that you make in the community strings table are temporarily stored in
memory.
To save non-default SNMP community strings information to the Optivity

Topology database:
Do one of the following:

database.
Working with SNMPv3 users
The following sections describe how to perform manage SNMPv3 users for
community strings entries:
• “Adding SNMPv3 users to an entry‚” next

• “Modifying an SNMPv3 user” on page 126
• “Deleting an SNMPv3 user” on page 127
• “Selecting SNMPv1 traps if SNMPv3 trap registration fails‚” next
207569-F
Adding SNMPv3 users to an entry
The Community Strings Editor lets you add the following users to community
string entries:
• Optivity user
The Optivity user is used for discovering SNMPv3 devices, SNMPv3 trap
registration, and receiving SNMPv3 traps. If you do not configure the Optivity
user correctly for a device, Optivity NMS fails to receive SNMPv3 traps for
that device, and the snmpEngineID is not stored in the Optivity NMS
database.
You can add one Optivity user for each IP address. If you try to add a second
Optivity user, the system displays a message advising you that an Optivity
user is already configured for that selected IP address.
In this case, if you want to designate another user name as an Optivity user,
you must de-select the Optivity user check box for the first Optivity user,
before you can add a subsequent Optivity user.
• Individual user
You add and specify authentication and privacy security features for each user
or multiple users for a specific IP or a range of IP addresses.
To add an SNMPv3 user:
1 If you haven’t already done so, open a Configure Community Strings Entry
dialog box for the entry for which you want to configure the telnet settings.
See “Adding a new community string entry” on page 117 or “Modifying a
community string entry” on page 120 for more information.
2 On the Configure Community Strings Entry dialog box, click the SNMP tab
to bring it to the front.
3 Mark the SNMPv3 aware device check box to enable the SNMPv3 features on
the tab.
You must enter at least the SNMPv3 user name. You will probably need to
also enter and confirm the telnet password. Depending on your device
configurations, you may also need to enter the privileged password, prompt,
timeout value, and retry value.

4 To designate the user as the Optivity user, mark the Optivity User check box.
5 Type an authentication key (optional) in the Authentication Key text box.
You must re-enter the authentication key.
6 Re-enter the authentication key.

The Privacy Key text box is enabled.
7 Type a privacy key (optional) in the Privacy Key text box.
You must re-enter the privacy key.
8 Re-enter the privacy key.
9 Click Add User.
The user entry is added to the User Details Table.
10 On the Configure Community Strings Entry dialog box, click OK.
database.
Modifying an SNMPv3 user
The Community Strings Editor lets you modify the Optivity user or individual
user properties. After modifying user properties you must click the Change User
button before you can complete either of the following steps:
• Modify the corresponding community strings.

• Click Save to save user properties to the database.
To modify a user entry:
dialog box for the entry for which you want to change the SNMPv3 user
settings. See “Adding a new community string entry” on page 117 or
“Modifying a community string entry” on page 120 for more information.
207569-F
3 On the User Details table, click the row for the SNMPv3 user you want to
modify.
4 In the properties area, modify the SNMPv3 user properties.
5 Click Update.
Community Strings Editor applies your changes to the User Details table.
6 Click OK.
dialog box.
database.
Deleting an SNMPv3 user
The Community Strings Editor lets you delete a user. If you delete an Optivity
user and do not configure another Optivity user for the respective IP address,
SNMPv3 traps are not received by the Optivity NMS server for that IP address.
The system displays a confirmation message informing you that you will not
receive SNMPv3 traps. You are prompted to continue or stop the deletion process.
To delete an SNMPv3 user:
dialog box for the entry for which you want to delete an SNMPv3 user. See
“Adding a new community string entry” on page 117 or “Modifying a
3 On the User Details table, click the row for the SNMPv3 user you want to
delete.

4 Click Delete.
Note: If you delete the SNMPv3 user designated as the Optivity user, you
must designate another user as the Optivity user.
5 If necessary, designate a different SNMPv3 user. See “Modifying an SNMPv3

user” on page 126 for more information.
6 Click Update.
Community Strings Editor applies your changes to the User Details table.
7 Click OK.
dialog box.
database.
Selecting SNMPv1 traps if SNMPv3 trap registration fails
The Community Strings Editor lets you configure a global preference that causes
the system to default to the community strings authorization if SNMPv3 trap
registration fails.
Some possible reasons for SNMPv3 trap registration to fail are:
• The authentication key is rejected

• The privacy key is rejected
• The user does not have permissions set in Access Control
If the option “Use SNMPv1 traps if SNMPv3 trap registration fails” is selected,
the system will receive SNMPv1 traps. If the option is not marked, no traps are
received by the system.
207569-F
To enable the Optivity NMS server to receive SNMPv1 traps:
1 On the toolbar, Click show data as table to switch to the table view.
2 If necessary, in the view area click the SNMP tab to bring it to the front.
3 Mark the check box for Use SNMPv1 traps if SNMPv3 trap registration fails.
Figure 20 Marking the check box for Use SNMPv1 traps if SNMPv3 trap
registration.
4 On the toolbar, click Save to apply the change to the Optivity NMS database.
Working with Telnet and SSL settings
The following sections describe how to configure Telnet and SSL security settings
for community strings entries:
• “Configuring Telnet settings for an entry‚” next

• “Configuring SSL settings for an entry” on page 130
Configuring Telnet settings for an entry
To configure telnet settings for either an existing entry or a new entry:
2 On the Configure Community Strings Entry dialog box, click the Telnet tab to
bring it to the front.

3 On the Telnet tab, enter the necessary telnet login information.

You must enter at least the IP address and telnet user name. You will probably
need to also enter and confirm the telnet password. Depending on your device
configurations, you may also need to enter the privileged password, prompt,
timeout value, and retry value.
4 If you are done configuring the community strings entry, click OK.
Otherwise, click either the SNMP tab or the SSL tab to configure the settings
on that tab.
Configuring SSL settings for an entry
To configure telnet settings for either an existing entry or a new entry:
2 On the Configure Community Strings Entry dialog box, click the SSL tab to
bring it to the front.
3 On the SSL tab, enter the necessary login information.
You must enter at least the IP address and SSL user name. You will probably
need to also enter and confirm the SSL password.
4 If you are done configuring the community strings entry, click OK.
Otherwise, click either the SNMP tab or the Telnet tab to configure the
settings on that tab.
Importing and exporting community strings
The following sections describe how to import community string entries from
files, and also how to export entries to files. You can use these features to transfer
and coordinate community strings between Optivity NMS and other network
management applications and platforms:
• “Importing a community strings file‚” next

• “Understanding Timeout value conversion” on page 133
• “Exporting a community strings file” on page 133
207569-F
Importing a community strings file
You can import a community strings file into the Optivity database using the
Community Strings Editor. Use this feature when you:
• Migrate from one operating system platform to another

• Transfer from one Optivity NMS server to another server
Note: Nortel Networks recommends that you not modify community

strings files manually.
A community strings file can contain from one to many community strings and
properties. When you save an imported community strings file, it completely
overwrites the existing community strings and properties that exist in the local
Optivity NMS database.
An imported HP OpenView community strings file does not support the Telnet
login password and SNMPv3. Therefore, Telnet and SNMPv3 information is not
imported.
When you import a community strings file in HP OpenView format, the

Community Strings Editor automatically converts the timeout values.
See “Understanding Timeout value conversion” on page 133 for more

information.
Note: You cannot import community string files using the Community
Strings Editor Web browser interface.
To import a new community strings file:
1 Save the community strings file that you want to import.

2 From the Community Strings Editor menu bar, choose either File > Import
Data >Optivity format or File > Import Data >HP-OV format.
Use the command that matches the file type you are importing.
The Import Community Strings dialog box opens.

3 Locate and select the community strings file that you want to import.
The file must be in comma separated value or in HP OpenView format.
4 Click OK.
5 The Choose Import Type dialog box opens to prompt you how to import the
entries in the file (Figure 21).
Figure 21 Choose Import Type dialog box
6 Click one of the choices described in Table 18.
Table 18 Community Strings Editor file import types
Click this... To do this...
Replace only Delete all existing community strings entries in the Optivity NMS
database and replace them with the community strings from the file.
Append and Add the entries in the file to the Optivity NMS database. Entries in the
Replace database that duplicate entries in the file are replaced by entries in the
file. All non-duplicate entries in the file are appended to the database.
Append and Append all entries in the file to the database. Duplicate entries are
retain retained.

207569-F
Understanding Timeout value conversion
The Community Strings Editor automatically converts the Timeout parameter

when you import a file in HP OpenView format. The HP OpenView Timeout is a
real number in 1/10 of a second. Optivity NMS Timeout is an integer between 1
and 99. The Community Strings Editor rounds the Timeout value to the nearest
non-zero integer.
Table 19 shows examples of the value conversions.
Table 19 Timeout value conversion examples
Converted Optivity
HP OpenView timeout
NMS timeout value
value (seconds)
(seconds)
5.2 5
5.6 6
1.23 1
2.88 3
0.80 1
0.30 1
Exporting a community strings file
Using Community Strings Editor, you can export the community strings
information in the Optivity NMS database to a file. Community Strings Editor lets
you export a community strings file in comma-separated value or HP OpenView
file format. You can use the community strings file as a backup while you make
changes to existing community strings, or to import new community strings to
another Optivity NMS server system.
For security when you export, Telnet password and SNMPv3 information is not
readable. Additionally, the Telnet login, password, and SNMPv3 information is
ignored for HP OpenView file format.

When you export an Optivity NMS community strings file in HP OpenView

format, the Optivity NMS time out value information is automatically converted
to the HP OpenView values.
Note: Nortel Networks strongly recommends that you not edit a

community strings file.
To export the current community strings data:
1 From the Community Strings Editor menu bar, choose File > Export data.
The Export Community Strings dialog box opens.
2 Go to the location on the Optivity NMS server file system where you want to
save the exported file.
3 Type a name for the file and choose the file format for the file.
4 Click OK.
207569-F
Troubleshooting the Community Strings Editor

results.
Table 20 Common Community Strings Editor problems
Problem Resolution
The Community Strings Editor Verify that:

does not start. • The cstrings.reg file is in the directory weboptsrvr/
registration beneath the Optivity NMS home
directory.
• The cstrings.schema file is in the directories db/
AppControlDB.db and schemas/AppControlDB
beneath the Optivity NMS home directory.
Also be sure that the Optivity user has access
permission to the IC, IC_ADMIN, and
COMMUNITY_STRINGS permission tokens in the
Access Control Administration window.
See Chapter 2, “Specifying access to Optivity NMS
applications with Access Control Administration,” on
You see the following message: This is the expected behavior, not a problem. The
Community Strings Community Strings Editor is not applicable when a
network management system such as HP OpenView
Editor has determined
or Tivoli NetView is installed on the Optivity NMS
that the community server station.
strings are managed by
If you want Optivity NMS to manage community
another platform other
strings, do the following:
than Optivity.
Optivity applications 1. Uninstall the other network management software.
will not use the 2. Uninstall Optivity NMS.
Optivity database for 3. Reinstall Optivity NMS.
getting the Community
Strings in this case.
Do you want to use the
Optivity database?
You cannot add a community Verify that you have fewer than 500 community strings
string entry. configured. You can add a maximum of 500
community strings.
You cannot add, delete, change Verify that you have read/write access to the
the order of, reset, save, import, COMMUNITY_STRINGS permission token in the
or export entries in the IP InfoCenter Access Control Administration window.
(community strings) table.

Table 20 Common Community Strings Editor problems (continued)
Problem Resolution
The values in the IP (community Perform a Save on the table. A reset restores the IP
strings) table are not what you (community strings) table values to the last SAVE
expected after clicking the Reset performed.
button.
You receive an error while trying If one or more line of the *.csv file you are trying to
to import a new community import does not match the expected format, the error
strings file. message provides the line number of each incorrect
entry. Contact Nortel Networks Customer Support
with this information.
207569-F
137
Chapter 4
Discovering your network with AutoTopology
Manager
• “AutoTopology Manager overview‚” next

• “Getting started with the AutoTopology Manager” on page 139
• “Working with AutoTopology Manager” on page 147
• “Troubleshooting the AutoTopology Manager” on page 176
AutoTopology Manager overview

The InfoCenter AutoTopology Manager lets you monitor and manage the
topology discovery process running on the Optivity NMS server. Use the
AutoTopology Manager to start and stop the discovery process and observe the
status of the discovery process.
The AutoTopology Manager provides search tools, user-selectable preferences,

and discovery options that let you customize topology discovery criteria that:
• Enhances topology discovery—You can use AutoTopology Manager to set

discovery options. Preference options such as Range Ping and Beyond Arp
can enhance topology discovery to perform a complete and efficient discovery
of Nortel Network devices.
• Enhances device filtering—AutoTopology Manager uses sysObjectId to filter
out devices. You can configure AutoTopology Manager preferences to
remember MAC addresses that were filtered out during previous discoveries,
which makes the filtering process faster.

138 Chapter 4 Discovering your network with AutoTopology Manager
• Enhances scaling and performance—You can configure discovery options for

your particular network discovery needs:
— Select the layer: network, data link, and end nodes
— Select the protocols: unicast, multicast, frame relay, IP-VPN and VPLS
— On-Demand Discovery to select an existing seed, select a reduced set of
discovery options and parameters, and quickly start a topology discovery.
The topcd daemon running on the Optivity server performs the topology
discovery. This daemon manages the following topology applications that also run
on the Optivity server:
• Network Layer topology—(toprt) Discovers routers and subnets by

downloading the routing tables and ipAddrTable from routers. Router
Topology starts with the ipAddrTable of the seed router, and obtains the
addresses of other routers from ipRouteTable. Router Topology queries all of
the routers that it discovers using this process. However, it only adds routers
with IP addresses within the specified subnet address range to the Optivity
NMS database.
• Data Link Layer topology—(topst) Uses information previously added to the
Optivity database to locate Nortel Networks devices within subnets. Subnet
topology queries the Nortel Networks devices about device and logical
topology, but does not query about workstations or end nodes. The topst
process filters out Nortel Network devices from non-Nortel Network devices
and updates the database to account for these devices.
• End Node Topology—(topdt) Uses information from Nortel Networks devices
to discover the workstations and end nodes connected to the Nortel Networks
devices.
• Protocol Discovery—(protur, protmr, protfr, protvpn, protvpls) Discovers
unicast, multicast, and frame relay protocols running on routers discovered by
Router Topology. The protur, protmr, and protfr processes are started by topcd
process and exit once they have completed their task.
Note: In addition to SNMP, the Telnet login name and password of the
network device are required to run multicast discovery of BayRS* routers
and to use the Path Trace feature.
When the discovery process is started, the topcd daemon runs the topology
applications in the order listed above.
207569-F
Chapter 4 Discovering your network with AutoTopology Manager 139
You also use AutoTopology Manager to configure the discovery seed setup.
Discovery seed range determines what portions of the network are discovered,
which determines which portions of the network you view in InfoCenter.
In addition to the normal discovery processes, AutoTopology Manager also

includes a routerless discovery that you can use to discover devices in subnets
where you do not know the IP address of a seed router. For more information, see
“Using Routerless discovery” on page 169.
Getting started with the AutoTopology Manager

See the following sections for information about getting started with
AutoTopology Manager:
• “Starting AutoTopology Manager‚” next

• “AutoTopology Manager window” on page 141
• “Access Control for AutoTopology Manager” on page 145
• “Understanding the age-out process” on page 146
• “Understanding discovery seeds” on page 146
Starting AutoTopology Manager
To start AutoTopology Manager:
Table 21 Starting AutoTopology Manager
To start
AutoTopology
Manager from: Do this:
InfoCenter Choose Admin > AutoTopology Manager
Note: If the AutoTopology Manager menu command is disabled, it

AutoTopology Manager.
Windows Start Choose Start > Programs > Optivity > AutoTopology Manager
menu

Table 21 Starting AutoTopology Manager (continued)
To start
AutoTopology
Manager from: Do this:
command prompt
topui
prompt
topui
Click the AutoTopology Manager icon on the Optivity Web page.

feature to bookmark the AutoTopology Manager application. Doing
so saves the URL for AutoTopology Manager.
If you are not starting AutoTopology Manager from InfoCenter, the Connect
to Optivity Server dialog box opens.
The AutoTopology Manager window opens.
207569-F
AutoTopology Manager window
The AutoTopology Manager window (Figure 22) lets you view and control the
Optivity topology discovery process running on the Optivity server.
Figure 22 AutoTopology Manager window
Menu bar
and toolbar
Progress
pane
Auto-rediscovery
status area
Status bar
Done box
In Progress box
Remaining box
Table 22 describes the parts of the AutoTopology Manager window.
Table 22 Parts of the AutoTopology Manager window
Part Description
Menu bar Provides access to all available commands. See “Menu bar and
toolbar” on page 142 for more information.
Toolbar Provides quick access to commonly used AutoTopology Manager
functions. See “Menu bar and toolbar” on page 142 for more
information.

Table 22 Parts of the AutoTopology Manager window (continued)
Part Description
Progress pane Displays status messages that show the progress of the current
topology discovery process.
See “Troubleshooting the AutoTopology Manager” on page 176 for
more information.
Done box During network layer discovery, shows the number of routers that have
been queried.
During data link layer discovery, shows the number of subnets for
which discovery has been completed.
During end node discovery, shows the number of Nortel Networks
devices for which end node topology has been completed.
In Progress box During network layer discovery, shows the number of routers are
currently being queried.
During data link layer discovery, shows the number of subnets
currently being discovered.
devices for which end node topology is currently under way.
Remaining box During network layer discovery, always shows 0, because the network
layer discovery process has no way of determining how many routers
remain to be discovered.
During data link layer discovery, shows the number of subnets for
which data link layer discovery has not started.
devices for which end node discovery has yet not been started.
Auto-rediscovery Shows the current auto-rediscovery status and settings (if
status area View > Display Auto Rediscovery Status is enabled). See “Scheduling
rediscovery with Auto Rediscovery” on page 153 for more information.
Status bar Displays information about the current status of the AutoTopology
Manager:
• The name of the Optivity server that the client application is
connecting to.
• Progress information for the current operation.
• A description of the toolbar button over which the pointer is
currently positioned.
The AutoTopology Manager menu bar commands and toolbar buttons provide
quick access to all AutoTopology Manager commands.
207569-F
If you open AutoTopology Manager in a Web browser, the menu bar does not
display. Instead, you use the Menu tool on the toolbar to open a shortcut menu of
AutoTopology Manager menus.
Table 23 describes the AutoTopology Manager menu bar commands and toolbar
buttons.
Toolbar
Menu Command button Description
Menu Opens the AutoTopology Manager menu in a Web browser.
Lets you drag the toolbar.
File Exit Quits the AutoTopology Manager client application.

View Display Tool Bar Displays or hides the toolbar.
Display Status Bar Displays or hides the status bar.
Display Auto Displays or hides the Auto Rediscovery Status area of the
Rediscovery Status AutoTopology Manager window.
Look and Feel Changes the appearance of the AutoTopology Manager
window.
See “Customizing the AutoTopology Manager window” on
Multicast Status Opens the Multicast Status window, which shows you details of
the differences between your multicast network and either the
previous discovery or the active baseline.
Log Detail Opens the Details window, which displays status messages
that show you the status of the discovery process.
View Domain Opens the View domain information dialog box to let you view a
Information list of your view domains and the IP addresses and ranges
within the domains. See “Viewing view domain information” on

Toolbar
Discovery Start Discovery Starts the autotopology discovery process.
Stop Discovery Stops the autotopology discovery process.
Routerless Opens the Routerless Discovery dialog box, to let you discover
Discovery devices in a subnet where you don’t know a seed router. See
“Using Routerless discovery” on page 169 for more
information.
On-Demand Opens the On-Demand Discovery dialog box, which lets you
Discovery select an existing seed, select a reduced set of discovery
options and parameters, and quickly start a topology discovery.
See “Using On-Demand discovery” on page 165 for more
information.
Settings Enter Seed Opens the Seed Information dialog box, which lets you view or
Specification edit discovery seeds.
Enter View Domain Opens the View domain editor dialog box to let you create and
Specification edit view domains. See “Working with view domains” on
Out of Band Editor Opens the Out-of-band Editor dialog box to let you mark
subnets or interfaces in the Optivity NMS topology database
that use out-of-band connections for network management
traffic. See “Managing connections with the Out-of-band Editor”
on page 171 for more information.
Auto Re-Discovery Opens the Auto Rediscovery dialog box to let you configure and
schedule automatic rediscovery. See “Scheduling rediscovery
with Auto Rediscovery” on page 153 for more information.
Preferences Opens the Preferences dialog box to let you specify global
discovery parameters for all seeds.
Options Opens the Options dialog box to let you set discovery and
protocol options.
Help AutoTopology Opens online Help for the AutoTopology Manager window.
Manager Help
Using Help Opens online Help on using the online Help system.
About Topology Displays version and copyright information for the AutoTopology
Manager Manager application.
207569-F
Access Control for AutoTopology Manager
Table 24 describes the tokens that control your access to AutoTopology Manager
functions. Functions for which you do not hold the appropriate token permissions
are disabled:
Table 24 Access control tokens for AutoTopology Manager
Token Attached with Read-Only Attached with Read/Write

permission permission
TOPUI_ACCESS Lets you: Grants you full access to all

• Open AutoTopology Autotopology Manager
Manager functions.
• View discovery status
details
• View view domain
information
DISCOVERY_ADMIN N/A Lets you:
• Configure rediscovery
preferences and
auto-rediscovery
parameters
• Stop all discoveries
including discoveries
started by other users,
• View log messages,
• Change discovery
preferences
VIEW_DOMAIN_MGMT N/A Lets you create, delete edit
and assign view domains.
An Optivity NMS administrator sets user access to the AutoTopology Manager

window by configuring access to the tokens with the Access Control
Administration window. For information about setting access control permissions,
see Chapter 2, “Specifying access to Optivity NMS applications with Access
Control Administration,” on page 75.

Understanding the age-out process
Devices that were previously added to the Optivity NMS database, but can no
longer be discovered by the topology applications, are removed from the database
by a process called age out. This process removes devices from the database when
they are no longer connected to the network.
The age-out process starts when any of the various topology applications fail to
discover a network resource that had previously been discovered by the same
application. When the resource fails to respond to queries by the topology
application, the topology application marks the database entry of the resource
with the date and time. At every subsequent discovery, the topology application
checks the elapsed time since the last time the resource responded to a query. If
the elapsed time is greater than the maximum allowed, the topology application
removes the device entry from the Optivity NMS database. You specify the
age-out period on the AutoTopology Manager Preferences dialog box General tab.
Devices that are discovered using Range Ping are also subject to the age-out
process. For example, a device was discovered when you use Range Ping in
association with seed 1. However, the device is not discovered when you did not
use Range Ping with seed 2. In this case, the device is marked for the age-out
process.
Understanding discovery seeds
A discovery seed is a set of information that specifies what the topology discovery
process discovers. Seeds are stored in the Optivity topology database on the
Optivity server.
207569-F
Each discovery seed contains the information shown in Table 25.
Table 25 Discovery seed information
Item Description
Name The unique name of the seed.

Start Address The IP address of the router (or other device) from which the discovery
originates. The router topology application starts discovering routers by
downloading the ipAddrTable and routing tables from the device at the
seed address.
If the specified device does not have routing tables, the router topology
application attempts to start discovery at the default gateway specified
for the device.
Subnet The range of subnet addresses that define the topology discovery
Range process. Only subnets, devices, and nodes within the specified range
are discovered.
IP address The range of IP addresses that define the topology discovery process.
Range Only devices and nodes within the specified range are discovered. IP
(Optional) address ranges take precedence over the subnet range.
Working with AutoTopology Manager

The following sections describe how to use AutoTopology Manager:
• “Discovering the network with AutoTopology Manager‚” next

• “Setting network discovery parameters” on page 149
• “Starting and stopping topology discovery” on page 152
• “Scheduling rediscovery with Auto Rediscovery” on page 153
• “Detecting multicast changes” on page 155
• “Viewing topology discovery details” on page 156
• “Working with discovery seeds” on page 156
• “Working with view domains” on page 161
• “Using On-Demand discovery” on page 165
• “Working with Range Ping” on page 167
• “Using Routerless discovery” on page 169
• “Managing connections with the Out-of-band Editor” on page 171
• “Validating WLAN access points” on page 173

• “Customizing the AutoTopology Manager window” on page 174
Discovering the network with AutoTopology Manager
To discover the network using AutoTopology Manager:
1 Make sure that you have entered community strings and user security
permissions for all of the services that you intend to discover. The
AutoTopology applications must have SNMP read community strings and
user security permissions for the all of the devices to be discovered.
If Optivity NMS is installed on a network management platform such as HP
OpenView or Tivoli NetView, use the community string management utilities
in the platform software to enter and manage the community strings.
If Optivity NMS is installed platformless, use the Optivity Community Strings

Editor as described in Chapter 3, “Specifying access to devices with the
Community Strings Editor,” on page 101.
2 Open the Autotopology Manager window.

For more information, see “Starting AutoTopology Manager” on page 139.
3 Do the following:
a Review the default AutoTopology preferences and make changes as
appropriate for the topology discovery you want to run. See “Setting
Preferences” on page 149 for more information.
b Review the default AutoTopology discovery options and make changes as
appropriate for the topology discovery you want to run. See “Setting
discovery options” on page 151 for more information.
4 Configure one or more discovery seeds using the Seed Information dialog
box.
Discovery seeds are the starting points that the topology applications and
daemons use to discover subnets, devices, and end nodes. For more
information on configuring discovery seeds, see “Creating a new discovery
seed” on page 156.
5 Click Start Discovery to start the discovery process.
207569-F
For more information, see “Starting and stopping topology discovery” on

page 152.
6 Monitor the discovery process using the progress pane of the AutoTopology
Manager window or the Details window.
For more information about the status and error messages that might appear,
see “Troubleshooting the AutoTopology Manager” on page 176.
7 To check the results of the discovery process, review the status messages in
the Details window. If devices or subnets do not appear as they should, try
adjusting topology seeds and community strings and running the discovery
process again.
Setting network discovery parameters
The AutoTopology Manager lets you configure network discovery parameters and
options that enhance the topology discovery of network entities (routers, switches,
subnets, and so forth) in your network. The parameters and options configured are
globally effective for each user and for all seeds created by each respective user.
• Preferences—You configure network discovery preferences in the Preferences

dialog box. See “Setting Preferences” on page 149 for more information.
• Options—You configure discovery options in the Options dialog box. See
“Setting discovery options” on page 151 for more information.
Setting Preferences
The AutoTopology Manager lets you configure global preferences that define how
topology process discovers your network. Preferences are arranged as follows:
• General
• Range Ring
• Network Layer
• Data Link Layer
• End Node
• Protocols
• Global

You must have administrator (Windows) or root (UNIX) permission to specify

Range Ping parameters. Range Ping is a global preference that applies to all users.
To configure preferences:.
From the AutoTopology Manager menu, click Settings > Preferences.
The Preferences dialog box opens to the General tab.
Table 26 describes the network discovery preferences and discovery options

default settings.
Table 26 Summary of discovery parameters and options
Tab Preferences Default
General SNMP Timeout 3 seconds

SNMP Retry Count 1
Telnet Timeout 20 seconds
Telnet Retry Count 3
Topology Data Age Out Period 168 hours
Rediscovery Hours 0
Rediscovery Days 0
Debug Level 0
Log Level 0
Use Community Strings Device specific
Enable MIB table dump Not selected
Enable DNS query Not selected
Range Ping Enable Range Ping Not selected
IP Address Range(s)
Ping Timeout 100 milliseconds
Ping Max Retries 3
Ping Age Out 0 hours
Ping non-responding address within known Not selected
subnets
Network Layer Router Discovery Hops 20
Enable ARP Cache Not selected
207569-F
Table 26 Summary of discovery parameters and options (continued)
Tab Preferences Default
Data Link Parallel Subnet Discovery 30

Layer
Enable saving VLAN data model Selected
Beyond ARP Mode:
None Selected
Seedless Subnets Only Not selected
All Subnets Not selected
Enable Beyond SONMP Not selected
Enable vendor ID filter Selected
Enable MLT/SMLT/DMLT Discovery Selected
End Nodes Parallel Device Discovery Count 30
Protocols Collect additional routing details Selected
Collect additional device configuration details Selected
Baseline comparison Compare with rolling
baseline
Generate traps Not selected
Global Display Label Default
Setting discovery options
The AutoTopology Manager lets you configure discovery options that define the
scope of the topology discovery. You set the following:
• Network layer options

• Protocol options
To configure discovery options:.
From the AutoTopology Manager menu, click Settings > Options.
The Options dialog box opens.

Table 27 describes the network discovery preferences and discovery options.
Table 27 Summary of discovery options
Option Default
Network layer options:
Network Layer Discovery Selected
Data Link Layer Discovery Selected
End Nodes Discovery Selected
Protocol Discovery options
Unicast Discovery Not selected
Multicast Discovery* Not selected
Multicast Sessions Discovery Not selected
Multicast Routing Discovery Not selected
Frame Relay Discovery Not selected
IP Virtual Private Network Selected
Discovery†
Virtual Private LAN Discovery‡ Selected
* Only enabled for users assigned Multicast service
† Only enabled if IP-VPN plug-in is installed on server and only for users assigned
Multicast service
‡ Only enabled if VPLS plug-in is installed on server and only for users assigned
Multicast service
Starting and stopping topology discovery
To start the topology discovery process:
• From the menu bar, choose Discovery > Start Discovery.

• On the toolbar, click Start Discovery.
AutoTopology begins the discovery process on all discovery seeds for which
the status is not “done.”
207569-F
To stop the topology discovery process:
• From the menu bar, choose Discovery > Stop Discovery.

• On the toolbar, click Stop Discovery.
Scheduling rediscovery with Auto Rediscovery
Use the Auto Rediscovery feature to periodically rediscover your network. This
feature helps make sure that the Optivity NMS topology database is always up to
date.
Note: You must have read/write permission to the

DISCOVERY_ADMIN token to use the Auto Rediscovery features.
To configure Auto Rediscovery:
1 From the AutoTopology Manager menu, choose Settings > Auto Rediscovery.

The Auto Rediscovery dialog box opens with the General tab forward as
shown in (Figure 23).
Figure 23 Auto Rediscovery dialog box (General tab showing)
2 On the General tab, choose general settings for auto-rediscovery.

If you enable general auto rediscovery, at a minimum, you must:
• Select at least one seed
• Select at least one day of the week
• Enter an hour
3 On the Multicast tab, choose settings for multicast auto-rediscovery:
Note: Multicast tab items are only available if you are assigned the
Multicast service. See “Assigning services to ONMS users” on page 97
• Select at least one seed

• Enable at least one of the following:
— Routing rediscovery
— Session rediscovery
• Enter a base interval
207569-F
• Enter the number of intervals between routing rediscoveries, if enabled

• Select whether to update all multicast sessions or only watched sessions.
See Using Optivity NMS 10.3 Applications (part number 207569-F) for
more information about managing multicast sessions.
4 (Optional) Click Apply to save your changes but leave the dialog box to set or
change other parameters.
5 Click OK to save your changes and close the dialog box.
If View > Display Auto Rediscovery Status is enabled, AutoTopology
Manager displays your auto rediscovery settings in the status bar at the bottom
of the AutoTopology Manager window (Figure 24).
Figure 24 Auto Rediscovery status on AutoTopology Manager window
Detecting multicast changes
You can use the multicast discovery features of AutoTopology Manager to detect
changes in your multicast network. When changes are detected between either the
previous discovery or the active baselines, AutoTopology Manager opens the
Multicast Notification window to alert you to the changes.
To configure AutoTopology Manager to alert you to Multicast changes:
1 From the AutoTopology Manager menu bar, choose Settings > Preferences
The Preferences dialog box opens.
2 Click the Protocols tab to bring it to the front.
3 On the Protocols tab, choose one of the following:
• Compare with rolling baseline to compare the multicast network with the
previous discovery
• Compare with active baseline to compare the multicast network with
active session and view baselines.
4 Click OK to save your settings and close the dialog box.

Viewing topology discovery details
To view the details of the topology discovery process:
• From the menu bar, choose View > Log Detail.

• On the toolbar, click Details.
The Details window opens.
Working with discovery seeds
The following sections describe how to manage discovery seeds with

AutoTopology Manager:
• “Creating a new discovery seed‚” next

• “Limiting discovery using IP ranges” on page 158
• “Viewing or editing an existing discovery seed” on page 160
• “Deleting a discovery seed” on page 161
Creating a new discovery seed
AutoTopology Manager lets you specify unique seeds for subsequent discoveries.
You can specify up to 32 characters in the name. Spaces and special characters are
not allowed in the name.
To create a new discovery seed:

• From the menu bar, choose Discovery > Enter Seed Specification.
• On the toolbar, click Enter Seed Specification.
207569-F
The Seed Information dialog box (Figure 25) opens.
Figure 25 Seed Information dialog box
For detailed information about the Seed Information dialog box, click Help in
the dialog box.
2 In the Discovery Seed Name box, enter a name for a new discovery seed.
3 In the IP Address to Start Discovery text box, enter the IP address of the
device from which to start the discovery process.
This is the first device from which AutoTopology attempts to download the
routing tables and ARP cache. If the specified device does not have routing
tables, the router topology application attempts to start discovery at the default
gateway specified for the device.
4 In the Start Subnet Address Range text box, enter the lowest subnet address to
be discovered. Enter a subnet address rather than a device address. Subnet
addresses usually end in 0, for example 10.127.2.0.
5 In the End Subnet Address Range text box, enter the highest subnet address to
be discovered. As with the Start Subnet Address Range text box, use a subnet
address, not the address of a specific device. For example, 10.127.90.255.
Only subnets within the specified range are discovered. Within each subnet,
the topology applications attempt to discover every device and node.

6 (Optional) Click Advanced to open the IP Range dialog box. Use this dialog
box to limit the discovery to a specific range or set of ranges of IP addresses.
See “Limiting discovery using IP ranges‚” next for more information.
7 Click Apply to add the new topology seed to the Optivity database.
8 Repeat steps 2 through 6 as necessary to create other discovery seeds.
9 When you are finished creating discovery seeds, click Close to close the Seed
Information dialog box.
10 Click OK.
Limiting discovery using IP ranges
AutoTopology Manager lets you limit a discovery to network elements within a

range or set of ranges of IP addresses. Only those devices within the subnet
address range and also within the IP address ranges will be discovered.
To limit discovery using IP ranges:
1 In AutoTopology Manager, choose Settings > Enter seed specification.

The seed specification dialog box opens.
2 Create a seed as described in Using Optivity NMS 10.2 Applications.
3 Click Advanced.
207569-F
The IP Range dialog box opens (Figure 26).
Figure 26 IP Range dialog box
4 (Optional) Click Show View Domains to open the View domain information
dialog box.
You can use the View domain information dialog box to view a list of your
view domains. That list helps you create IP address ranges for discovery seeds
by showing you which IP address ranges fall within your view domains.
Autotopology will discover only those devices within your view domains. If
you create discovery seeds with IP addresses or ranges that are outside your
view domains, Autotopology will not discover the devices that are outside
your view domains.
5 In the IP/IP Range box, type an IP range. Valid entries are:
• A single IP address, for example “10.126.1.1”
• A range of IP addresses, for example “10.126.1.1-10.126.255.255”
6 Click Add to add the IP range to the IP/IP Range Entries list

7 Repeat steps 5 and 6 until the IP/IP Range Entries list contains the IP ranges
you want to discover.
8 Click OK to apply your changes and close the dialog box.
9 In the Seed Information dialog box, click Apply to apply your changes.
A confirmation dialog box prompts you to confirm the changes to the seed.
10 Click Yes to confirm the changes.
11 Click Close to close the Seed Information dialog box.
12 In the Autotopology Manager window, choose Discovery > Start discovery to
start the discovery.
Viewing or editing an existing discovery seed
To view or edit an existing topology seed:

The Seed Information dialog box (Figure 25 on page 157) opens.
the dialog box.
2 In the Discovery Seed Name box, click the down arrow to select from among
the previously defined seeds.
3 View or change the seed configuration information.
4 When you are done changing a discovery seed, click Apply to save the
changes.
If you choose a different seed from the Discovery Seed Name box before you
click Apply, changes you have made to the previous seed are lost.
5 Repeat steps 2 through 4 as necessary to view or edit other discovery seeds.

6 When you are finished viewing or editing discovery seeds, click Close to
close the Seed Information dialog box.
207569-F
Deleting a discovery seed
To delete an existing discovery seed:

The Seed Information dialog box (Figure 25 on page 157) opens.
the dialog box.
2 In the Discovery Seed Name box, select a previously defined seed.

3 Click Delete to delete the selected discovery seed.
4 Repeat steps 2 and 3 as necessary to delete other discovery seeds.
5 When you are finished deleting discovery seeds, click Close to close the Seed
Information dialog box.
Working with 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.
In previous Optivity NMS releases, some of the functions now done by view
domains was done by discovery seeds. Users could add seeds to their database
views to view the network resources discovered by those seeds. Administrators
could use seed-based access control to control which Optivity NMS users had
access to each seed.
Optivity NMS 10.3 introduces view domains to extend the functionality of seeds
while separating the discovering and viewing of resources. In Optivity NMS 10.3,
discovery seeds only control what is discovered in AutoTopology Manager, while
control of what Optivity NMS users can view and manage is dictated by view
domains.

Optivity NMS automatically creates and maintains a view domain for every
discovery seed. You cannot delete these automatically-created view domains.
See the following sections for more information about creating and managing
view domains:
• “Creating view domains‚” next

• “Editing or deleting view domains” on page 164
• “Viewing view domain information” on page 165
For information about assigning view domains to Optivity NMS users, see
“Assigning view domains to ONMS users” on page 95.
Creating view domains
AutoTopology Manager automatically creates a new view domain for every new
seed. You can also create view domains independently of a seed.
To create a new view domain:
1 In AutoTopology Manager, choose Settings > Enter view domain

specification.
The View domain editor dialog box opens (Figure 27).
207569-F
Figure 27 View Domain Editor dialog box
2 In the View Domain Name box, type the name for the new view domain.
If the box contains the name of an existing view domain, drag the text of that
name and type the new name so that it replaces the old name.
3 In the IP/IP Range box, type an IP range. Valid entries are:
• A single IP address, for example “10.126.1.1”
• A range of IP addresses, for example “10.126.1.1-10.126.255.255”
4 Click Add to add the IP range to the IP/IP Range Entries list
5 Repeat steps 3 and 4 until the IP/IP Range Entries list contains all of the IP
addresses and ranges for the view domain.
6 Click Apply to apply your changes.

Editing or deleting view domains
To edit or delete view domains:
1 In AutoTopology Manager, choose Settings > Enter view domain

specification.
The View domain editor dialog box opens.
2 In the View Domain Name menu, choose a view domain.
• To delete the entire view domain:
a Click Delete.
An alert box prompts you to confirm the deletion.
b Click OK.
c Click Apply.
• To add an IP address or range to the view domain:
a Enter the IP address or range in the IP/IP Range box.
b Click Add.
c Click Apply.
• To remove an IP address or range from the view domain:
a In the IP/IP Range Entries list, select an IP address or range.
b Click Remove.
c Click Apply.
• To edit an IP address or range in the view domain:
a In the IP/IP Range Entries list, select an IP address or range.
The address or range appears in the IP/IP Range box.
b In the IP/IP Range box, edit the address or range.
c Click Update.
Your changes are applied to the entry in the IP/IP Range Entries list.
4 Click Close to close the dialog box.
207569-F
Viewing view domain information
To view information about your view domains in AutoTopology Manager:
In AutoTopology Manager, choose View > View domain information.
The View domain information dialog box opens (Figure 28).
Figure 28 View Domain Information dialog box
Using On-Demand discovery
On-demand discovery is a feature that lets you select an existing seed, select a
reduced set of discovery options and parameters, and quickly start a topology
discovery.
To perform an on-demand discovery:
1 From the AutoTopology Manager menu bar, choose Discovery > On-Demand
Discovery.

The On-Demand Discovery dialog box opens as shown in Figure 29.
Figure 29 On Demand Discovery dialog box
2 In the Select a Seed list, click on one of the discovery seeds.

If there are no seeds in the list, you must create a discovery seed before you
can proceed. See “Creating a new discovery seed” on page 156 for more
information.
3 In the Select Topology Discovery area, choose one or more of the discovery
processes that you want to run.
Note: For newly-created seeds, Autotopology can only discover end

nodes after both Network Layer Discovery and Data Link Layer
Discovery have been run. If no previous discovery has been run, when
you select End Nodes Discovery you cannot deselect either Network
Layer Discovery or Data Link Layer Discovery.
207569-F
4 In the Select Protocol(s) area, choose one or more of the protocols you want to
discover.
5 Click Start Discovery.
AutoTopology Manager starts the on-demand discovery.
Working with Range Ping
Range Ping is a topology process that you can use to discover devices that are on
previously-discovered subnets, but are not recorded in ARP caches. Range ping
sends ICMP echo packets to every device and subnet within a selected range. You
can specify individual addresses, ranges of addresses, or combinations of the two.
When enabled, range ping runs every time that the Data Link Layer topology
(topst) application runs.
Nortel Networks recommends that you avoid using range ping unless some
devices are not being discovered by the other topology processes. Range ping
creates a substantial amount of network traffic, and is time intensive.
The following sections describe how to use AutoTopology Manager Range Ping
features:
• “Enabling Range Ping‚” next

• “Entering Range Ping IP addresses” on page 168
Enabling Range Ping
To enable Range Ping:
Note: Only access administrators can enable Range Ping. For more
information about access privileges, see Chapter 2, “Specifying access to
Optivity NMS applications with Access Control Administration,” on page
75.
1 From the AutoTopology Manager menu, click Settings > Preferences.

2 Click the Range Ping tab.

The Preferences dialog box Range Ping tab opens.

3 Click Enable Range Ping.
Entering Range Ping IP addresses
Optivity NMS Range Ping lets you specify the IP address or range of IP address
for use during a discovery process.
Use the following format to specify IP addresses in the IP Range(s) dialog box:
• IP addresses of the format <value>.<value>.<value>.<value>, where

<value> can be either:
— An integer 0 to 255.
— An asterisk (*) wildcard to match the range 0-255 within an address, for
example, “10.127.*.*”. The asterisk (*) is the only valid wildcard
character.
• A dash (-) character to indicate a range of valid addresses. For example,
“10.120.0.09-10.127.0.0”. Do not include spaces before or after the dash.
• A comma to separate individual addresses. For example,
“10.120.3.6,10.120.3.9”.
To enter an IP address:
1 From the AutoTopology Manager menu, click Settings > Preferences.

2 Click the Range Ping tab.
The Preferences dialog box Range Ping tab opens.
3 If it is not checked, click Enable Range Ping. See “Enabling Range Ping” on
page 167 for more information about enabling Range Ping.
4 Click Edit.
207569-F
The IP Range(s) dialog box opens as shown in Figure 30.
Figure 30 IP Address Range(s) dialog box
5 Type an IP address or range of IP addresses in the Input box.

6 Click Add.
The entry is transferred from the Input box to the Current List area.
7 Repeat step 5 and 6 to add more IP addresses.
8 Click OK.
The entries are saved to the IP Range(s) dialog box list.
Using Routerless discovery
The AutoTopology Manager Routerless discovery feature lets you discover

subnets even when you do not know the IP address of a seed router on the subnet.
Routerless discovery uses the range ping and beyond ARP features to find devices
within a specified IP address range.

To use routerless discovery:
1 If you haven’t already done so, open the AutoTopology Manager window.
For more information, see “Starting AutoTopology Manager” on page 139.
2 From the AutoTopology Manager menu bar, choose Discovery > Routerless
discovery.
The Routerless Discovery dialog box opens (Figure 31).
Figure 31 Routerless Discovery dialog box
3 In the Discovery Seed Name box, type a name for the routerless discovery
seed.
4 Type the subnet address and subnet mask in the appropriate boxes.
5 (Optional) Click Advanced and use the IP Range dialog box to specify IP
ranges to limit the routerless discovery. See “Limiting discovery using IP
ranges” on page 158 for more information.
6 Click Start.
AutoTopology Manager creates a routerless discovery seed and performs
routerless discovery on the indicated subnet.
207569-F
Managing connections with the Out-of-band Editor
The Out-of-band Editor window lets you identify out-of-band interfaces in the
Optivity topology database. Rediscovery processes and Expanded View use the
out-of-band interfaces for SNMP data collection whenever possible. This feature
reduces the management traffic overhead on your primary data network.
See the following sections for more information about using the Out-of-band
editor:
• “In-band and out-of-band Overview‚” next

• “Identifying out-of-band interfaces” on page 171
In-band and out-of-band Overview
The term “Out-of-band” refers to communication that does not follow the same
path as normal data. When used with data network management, it means a
separate (i.e. parallel) network is used to monitor and control a data network.
In some cases, administrators build a parallel network that carries SNMP traffic
between a network management stations and each of the network devices. This
second network reduces or eliminates SNMP traffic on the mission-critical
production network.
Identifying out-of-band interfaces
The Autotopology manager lets you identify out-of-band interfaces in the Optivity
topology database.
To mark out-of-band and in-band interfaces:
1 If you haven’t already done so, start the Autotopology Manager.

See “Starting AutoTopology Manager” on page 139 for more information.
2 From the Autotopology Manager menu bar, choose Settings > Out-of-Band
Editor.
3 The Out-of-Band Editor dialog box opens (Figure 32).

Figure 32 Out-of-band editor dialog box
4 In the IP Ranges box, enter the IP address range or ranges within which you
want to identify out-of-band interfaces.
You can use * wildcards, commas, or hyphens to specify ranges. For example:
• 10.126.*.*
or
• 10.124.21.0, 10.126.23.0
or
• 10.124.21.0-10.126.29.0
5 Click Update Lists to refresh the in-band and out-of-band lists with the
subnets or interfaces in the selected IP range.
207569-F
6 Use the Mark Out-of-band radio buttons to set the mode by which you
identify out-of-band interfaces:
• Choose By Subnet to display all of the subnets within the selected IP
ranges. Marking a subnet as out-of-band identifies all of the interfaces
discovered within the subnet as out-of-band interfaces.
• Choose By Interface to display all of the interfaces within the selected IP
ranges. Marking an interface identifies that interface as out-of-band.
7 Use the directional buttons (>, >>, <, and <<) to move entries between the
In-band and Out-of-band lists as appropriate.
8 When you are done identifying subnets or interfaces for in-band and
out-of-band communication, click Apply.
After the next autotopology discovery cycle, Optivity protocol visualization
processes and Expanded View use the out-of-band interfaces instead of the
primary network whenever possible.
Validating WLAN access points
Whenever AutoTopology discovers new wireless LAN access points on your

network, AutoTopology Manager opens a dialog box to alert you of the new
access points. This feature advises you of new access points on the network, and
helps you find and disable rogue access points that may have been installed on
your network.
To validate WLAN access points:
1 When the Access Point Validate dialog box (Figure 33) opens, examine the
MAC addresses and IP addresses of the devices in the Newly discovered
Access Points list.

Figure 33 Access Point Validate dialog box
2 In the Newly discovered Access Points list, select those devices you recognize
as valid and authorized.
3 Click >> to move the valid and authorized devices to the Valid Access Points
list.
When these devices are discovered in future rediscoveries, you will not be
alerted.
4 For devices that you do not recognize as valid and authorized, use InfoCenter
to determine the device network connectivity so that you can find and disable
the device.
Customizing the AutoTopology Manager window

The following sections describe how you can customize the AutoTopology
Manager window:
• “Setting the look and feel‚” next

• “Hiding or displaying the toolbar, status bar, and auto-rediscovery status area”
on page 175
207569-F
Setting the look and feel
You can easily change the look and feel of the AutoTopology Manager window to
match the other applications on your computer.
To change the look and feel of the AutoTopology Manager window:
1 From the AutoTopology Manager menu bar, choose View > Look and Feel.
A shortcut opens, offering you several choices.
2 Choose the Look and Feel menu selection that best matches your computing
environment.
Hiding or displaying the toolbar, status bar, and

auto-rediscovery status area
You can customize the AutoTopology Manager window by hiding or displaying

the toolbar, status bar, and auto-rediscovery area.
To hide or display the toolbar:
From the AutoTopology Manager menu bar, choose View > Display Tool
Bar.
To hide or display the status bar:
From the AutoTopology Manager menu bar, choose View > Display Status
Bar
To hide or display the auto rediscovery status area:
From the AutoTopology Manager menu bar, choose View > Display Auto
Rediscovery Status
The Multicast notification window alerts you to changes in your multicast

network. AutoTopology Manager opens this window when the topology
applications detect differences between either the previous discovery or the active
baseline. See Detecting multicast changes for more information.

Troubleshooting the AutoTopology Manager

The AutoTopology Manager provides messages about the status of an operation.
The messages shown in Table 28 may be displayed in the progress pane of the
AutoTopology Manager window, or in the AutoTopology Manager details
window.
Table 28 AutoTopology Manager status messages
Message Description
Auto Topology Daemon is The AutoTopology Manager established

running communication with the topcd daemon.
Chassis <MAC Address> The end node topology application (topdt) has
done finished getting end node information from the
Nortel Networks device at the specified MAC
address.
Checking Database for The topcd daemon is reading seeds from the
discovery seeds Optivity NMS database and passing them to the
AutoTopology Manager application.
Click Start Discovery Click Start Discovery on the toolbar, or choose
button/menu to start Discovery > Start Discovery to start the topology
discovery process.
Create/modify discovery You must create at least one seed in order to
seeds to begin discovery perform a topology discovery.
Discovery started by The specified user has started a topology
user “user_name” discovery.
Endnode Discovery is up Discovery is either complete or there is no seed

to date specification entered.
Found Router <IP The Router Topology application has found the
Address> next router within the discovery range.
Got EndNode Topology The topcd daemon received notification (in the
trigger form of a topst trigger in the Optivity database) that
the subnet topology application (topst) has finished
subnet topology discovery, and that it can start the
end node topology application (topdt).
Got Router Topology The topcd daemon received notification (in the
trigger form of a toprt trigger in the Optivity NMS
database) that the end node topology application
(toprt) has finished router discovery. The topcd
daemon starts the Router Topology application if it
detects that seeds have been added or modified in
the Optivity database.
207569-F
Table 28 AutoTopology Manager status messages (continued)
Message Description
Got Subnet Topology The topcd daemon received notification (in the
trigger form of a topst trigger in the Optivity NMS
database) that the Router Topology application
(toprt) has finished router discovery, and that it can
start the subnet topology application (topst).
Initializing… The AutoTopology Manager is initializing.
Initiate The topcd daemon is attempting to establish
Endnode-Workstation communication with the end node topology
discovery application. This message usually appears 2 or 3
times.
Initiate Router The topcd daemon is attempting to establish
Discovery communication with the Router Discovery
application. This message usually appears 2 or 3
times.
Initiate Subnet The topcd daemon is attempting to establish
Discovery communication with the subnet topology
application. This message usually appears 2 or 3
times.
Launching /usr/lnms/bin/ The topcd daemon found that the end node
topdt topology application was not running, so the
daemon started the application.
Launching /usr/lnms/bin/ The topcd daemon found that the router topology
toprt application was not running, so the daemon
started the application.
Launching /usr/lnms/bin/ The topcd daemon found that the subnet topology
topst application was not running, so the daemon
started the application.
None found, Router No active discovery seeds have been found.
Discovery will NOT start
Processing Start The AutoTopology Manager has sent a start
Discovery request request to the topcd daemon.
Processing Subnet The subnet discovery application is discovering

<subnet ip> logical and physical subnets.
Querying Optivity DB for The topcd daemon is checking the Optivity NMS
new seeds. database for any discovery seeds that might have
been added while the topology discovery was in
progress.
Router <IP Address> done The router topology application finished getting
network information from the router at the
specified IP address.

Message Description
Router and Subnet Logical and physical topology discovery is

Discovery Completed complete for all subnets within the specified
ranges.
Router Discovery The router topology application has finished
Complete discovering routers.
Router Discovery is up All of the routers in the current set of discovery

to date seeds are represented in the Optivity database.
Router, Subnet and All discovery processes are complete.

Endnode Discovery Workstations have been added to the Optivity
Completed NMS database.
Seed “seed_name” created The AutoTopology Manager added the specified

by user "user_name" seed to the Optivity database.
Start Router <IP The Router Topology application started

Address> downloading all routing tables and other relevant
tables from the specified router.
Subnet <subnet ip> done The subnet discovery application finished
discovering logical and physical subnets. All the
devices in the subnet are visible in InfoCenter.
Subnet <subnet ip> The topcd daemon started the subnet discovery
started application to discover logical and physical
subnets.
Subnet Discovery is up Discovery is either complete or there is no seed
to date specification entered.
Timeout (snmp) <IP One of the topology applications failed to establish

Address> SNMP communication with the device at the
specified IP address.
Trigger Endnode The subnet discovery application alerted the topcd
Discovery daemon that the subnet discovery is complete.
The topcd daemon starts the endnode discovery
application.
Trigger Router Discovery The endnode discovery application alerted the
topcd daemon that the end node discovery is
complete. If new discovery seeds have been
defined since the topology discovery process was
started, the topcd daemon starts the router
discovery application again.
207569-F
Message Description
Trigger Subnet Discovery The router discovery application alerted the topcd
daemon that the router discovery is complete. The
topcd daemon starts the subnet discovery
application.
Use Seed Specification You must create at least one seed in order to
dialog to create seed perform a topology discovery.

207569-F
181
Chapter 5
Navigating the InfoCenter window
This chapter provides information about starting InfoCenter, and navigating the
InfoCenter window. It contains the following topics:
• “InfoCenter overview‚” next

• “Getting started with InfoCenter” on page 182
• “Parts of the InfoCenter window” on page 185
• “About Optivity integrated applications” on page 249
InfoCenter overview
InfoCenter provides a centralized location for you to visualize your network
resources and launch local or Web-based applications to:
• Set user permissions, set application preferences, discover network topology,

configure community strings, and manage the database.
• Assemble devices into logical groups (such as device type, location, fault
status, or routing protocol) using the InfoCenter folder-based interface.
• Spot potential problems in the network at a glance. Move through the logical
layers of the network, from Internet down to physical, displaying intranetwork
devices, logical concepts (such as VLANs), and end nodes. Display fault
status instantly in tabular or graphical views. View device labels, DNS names,
SysNames or IP addresses.
• Start local or Web-based Optivity NMS applications, or other element
manager products, such as Device Manager for Passport routing switches.
• Display fault status instantly in all views. Save data on device characteristics
into folders for retrieval and comparison, or to isolate an issue down to the
data link or physical level.

182 Chapter 5 Navigating the InfoCenter window
InfoCenter provides the performance and scalability that you need to display up to
10000 objects. InfoCenter’s advanced graphics viewing tools let you view your
discovered network from a single node to the complete discovered network in a
single folder view.
For example, you can use zoom, pan, and overview window tools to locate
specific areas of a network map. You can print folder contents in table or graph
format or in a document format that you design using print setup options. You can
also preview the document before you print it.
For information about InfoCenter’s administration tools, see the following

chapters:
• Chapter 2, “Specifying access to Optivity NMS applications with Access

Control Administration,” on page 75
• Chapter 3, “Specifying access to devices with the Community Strings Editor,”
on page 101
• Chapter 4, “Discovering your network with AutoTopology Manager,” on page
137
• Chapter 14, “Managing network management applications with Application
Launch,” on page 521
• Chapter 15, “Specifying the level of statistics gathering with Monitor
Options,” on page 541
• Chapter 21, “Managing data with the Database Admin Tool,” on page 743
Getting started with InfoCenter

The following sections will help you get started using InfoCenter:
• “About InfoCenter user access‚” next

• “Starting InfoCenter” on page 183
207569-F
Chapter 5 Navigating the InfoCenter window 183
About InfoCenter user access
To access InfoCenter, you must have:
• A valid user account

• A valid password
From the InfoCenter Access Control Administration window, an Optivity NMS

administrator can limit access to applications and functions on a per-user basis by
assigning permission tokens. The following are the permission tokens for
InfoCenter:
• IC_ADMIN (permits user to access folders and the Monitor Options window)
• IC (permits user to manipulate the folders within InfoCenter)
You can also limit users to read-only access, or allow full read-write access.
Administrators can also create customized access groups.
For more information about setting user access, see Chapter 2, “Specifying access
to Optivity NMS applications with Access Control Administration,” on page 75.
Starting InfoCenter
To start InfoCenter:
Table 29 Starting InfoCenter
To start
InfoCenter from: Do this:
Windows Start Choose Start > Programs > Optivity > InfoCenter
menu
Windows cd \Optivity\NMS\bin
command prompt
infocenter

Table 29 Starting InfoCenter (continued)
To start
InfoCenter from: Do this:
UNIX command cd /Optivity/NMS/bin
prompt
infocenter
Web browser http://[IP or hostname of ONMS server]
Click InfoCenter icon on Optivity Web page
The InfoCenter Connect to Optivity Server dialog box opens.

2 Enter your login information and click OK.
The Optivity NMS InfoCenter window (Figure 34) opens.
Figure 34 Optivity NMS InfoCenter window
Note: On UNIX, you may not be able to connect multiple InfoCenter

clients to an Optivity NMS server. The workaround for this issue is to
increase the number of file descriptors on the Optivity NMS server.
207569-F
Parts of the InfoCenter window

Figure 35 shows the parts of the InfoCenter window as they appear when you
open InfoCenter.
Note: The menu bar does not appear in a Web browser. If you open
InfoCenter in a Web browser, you use the menu tool on the toolbar to
open menus.
Figure 35 Parts of the InfoCenter window
Menu
bar
Toolbar
panel
Folder
tree
Folder
view
Contents
panel
Launchpad
Status bar

Table 30 describes the parts of the InfoCenter window.
Table 30 Parts of the InfoCenter window
Part Description
Menu bar Provides menu access to InfoCenter commands.

Toolbar panel Provides single-click access to commonly used InfoCenter
commands.
Contents pane Displays the contents of the currently selected folder, or the results of
the most recent search. Multiple folders may be open in separate
display windows at the same time. Folders may be displayed in either
graphical or tabular view formats.
Folder views Displays the contents of a single folder in either graphical or tabular
format.
Folder tree Displays a tree view of the current InfoCenter folder hierarchy.
Using the Starts other applications, such as ping, Telnet, OmniView, and MView.
InfoCenter By default, the launchpad is closed when the InfoCenter window first
launchpad opens.
Status bar Displays the status of current InfoCenter activity.
Folder tree
The folder tree in the left pane of the InfoCenter window gives you a folder-based
interface for grouping network objects, alarms, view domains, and shared custom
folders. The discovered resources in your network are reflected in the folder tree.
At installation, the folders are organized for optimal network monitoring.
Table 31 lists and describes the folders in the folder tree.
Table 31 InfoCenter folder tree
Folder Description
InfoCenter Top level of folder tree.

Alarms Contains fault management alarm status folders, color-coded to reflect the status
of the subfolder object that is currently in the most severe state. See “Monitoring
network health with InfoCenter” on page 317 for more information.
Critical Contains devices with a “critical” alarm status.
Warning Contains devices with a “warning” alarm status.
Caution Contains devices with a “caution” alarm status.
207569-F
Table 31 InfoCenter folder tree (continued)
Folder Description
Baselines Contains Multicast routing, session, and view baseline folders. See “Managing
multicast sessions and protocols with Optivity NMS” on page 329 for more
information.
This folder and its subfolders only appear if you are assigned the Multicast
service. Optivity NMS administrators assign services using Access Control
Administration. See “Viewing available services” on page 249 to check your
services. See the Chapter 2, “Specifying access to Optivity NMS applications with
Access Control Administration,” on page 75 for information on assigning services.
Multicast Contains Multicast routing view baselines. See “Saving multicast routing view
Routing baselines” on page 348 for more information.
Multicast Contains Multicast session baselines. See “Saving multicast session view
Sessions baselines” on page 347 for more information.
Multicast Contains Multicast view baselines. See “Saving multicast session baselines” on
Views page 336 for more information.
Custom Contains user-created folders (queries) that can be shared. You can add folders
under this folder. See “Creating and configuring custom folders” on page 268 for
more information.
View Domains Contains your view domains. See “Adding and removing view domains” on

Folder Description
Resources Contains resource subfolders.

Bridges Contains bridges.
ELANs Contains ELANs.
Hubs Contains hubs.
IP-Telephony Contains IP-telephony systems such as:

• Succession 1000
• MCS 5100 Multimedia Communications System
• Meridian 1
• Business Communication Manager (BCM)
See Chapter 10, “Managing IP telephony systems with Optivity NMS,” on page
359 for more information.
This folder only appears if you are assigned the VOIP service. Optivity NMS
administrators assign services using Access Control Administration. See “Viewing
available services” on page 249 to check your services. See the Chapter 2,
“Specifying access to Optivity NMS applications with Access Control
Administration,” on page 75 for information on assigning services.
IP-VPN Contains IP-VPN elements such as Contivity devices and tunnels. See Chapter 9,
“Managing IP Virtual Private Networks with Optivity NMS,” on page 355 for more
information.
This folder only appears if you are assigned the IP-VPN service. Optivity NMS
Internet Contains internetworking objects.
207569-F
Folder Description
Management Contains management servers.

servers
Multicast Contains multicast elements.
This folder and its subfolders only appear if you are assigned the Multicast
service. Optivity NMS administrators assign services using Access Control
Administration. See “Viewing available services” on page 249 to check your
services. See the Chapter 2, “Specifying access to Optivity NMS applications with
Access Control Administration,” on page 75 for information on assigning services.
Routing Contains multicast routing.
Sessions Contains multicast sessions.
Probes Contains probes.
Routers Contains routers.
Security Contains security clusters.

clusters
Segments Contains network segments.
Subnets Contains subnets.
Switch Contains switch communities

Communities
Switches Contains switches
Unicast Contains unicast protocols
VLANs Contains VLANs

Local Contains local VLANs, which are the actual VLANs configured on a device.
VLANs
Logical Contains logical VLANs, which are logical groupings of the local VLANs based on
VLANs the subnet whose traffic is carried on those local VLANs.
VPLS Contains Virtual Private LAN Services elements. See Chapter 11, “Managing
virtual private LAN services devices with Optivity NMS,” on page 369 for more
information.
This folder only appears if you are assigned the VPLS service. Optivity NMS
WANs Contains WAN networks and frame relay protocols
WLAN Contains wireless LAN devices

Devices

Note: Before you can view your network resources in resource folders,
you must run discovery from AutoTopology Manager. For more
information, see Chapter 4, “Discovering your network with
For more information about folders and the query process, see “Predefined
folders” on page 256.
Folder pane Shortcut menu
You can right-click any folder to open the folder shortcut menu (Figure 36).
Figure 36 Folder pane shortcut menu
Folder pane
shortcut menu
207569-F
Table 38 describes the folder pane shortcut menu commands.
Table 32 Folder pane shortcut menu commands
Command Description
Open Opens a submenu for you to choose a folder format (graphical or

tabular) in which to open the selected folder.
Export Folder Exports the contents of a folder to a file on your client system. For
Contents more information, see “Exporting folder contents” on page 289.
Delete Deletes the selected folder. For more information, see “Deleting a
folder” on page 290.
Rename Allows you to edit the name of the selected folder. For more
information, see “Renaming a custom folder” on page 269.
Sharing Opens the Folder Properties dialog box Sharing tab to let you share
the selected custom folder with other Optivity NMS users. For more
information, see “Sharing custom folder queries with other InfoCenter
users” on page 291.
Copy Copies the current selection to the clipboard. For more information,
see “Copying folders” on page 287.
Paste Pastes the contents of the clipboard into the folder.
Properties Opens the Folder Properties dialog box. For detailed information
about the Folder Properties dialog box, click Help on the dialog box.
Displaying or hiding the folder pane
The Folder browser preference lets you choose whether or not to display the folder
pane. By default, the folder pane is displayed, but you can hide it to provide more
viewing area in the contents pane. When you set the preference to hide the folder
pane, InfoCenter always hides it, until you reset the preference again. You can
select Display Folder pane from the View menu to display it during the current
session.
To set your preference for showing or hiding the folder pane:
1 From the InfoCenter menu bar, choose Options > Set Preferences.
The Preferences dialog box opens (see Figure 56 on page 235).
For detailed information about the Preferences dialog box, click Help on the
dialog box.
2 Click the Window tab to bring it to the front.

3 To hide the folder pane, check Hide in the Folder browser area. To display the
folder pane, uncheck Hide.
4 Click OK to close the dialog box and save your changes.
Your preference for showing or hiding the folder pane is changed. Until you
change the preference again, InfoCenter always uses this setting.
To display or hide the folder pane for the current session:
From the InfoCenter menu bar, Choose View > Display Folder Browser.
Contents pane
The contents pane (Figure 37) is the right-hand pane in the main InfoCenter
window, and is positioned to the right of the folder pane. The contents pane
displays the contents of the currently selected folder, or the results of the most
recent search.
Folder views
Folder views are the windows in the contents pane that display folder contents.
For every view, there are two or three dimensions that contribute to what you see
in the view:
• Layer - Shows you one of several logical layer views of your network. See
“Folder view layers‚” next for more information.
• Presentation type - Your choices are graphic and tabular. See “Folder view
presentation types” on page 196 for more information.
• Layout type (graphic views only) - Arranges graphic icons in one of several
layout styles. See “Folder view layouts” on page 196 for more information.
The following sections describe how to use folder views:
• “Opening a folder view” on page 197

• “Folder view shortcut menu” on page 198
• “Object shortcut menu” on page 200
• “Displaying or hiding the view summary details” on page 202
• “Folder view preferences and defaults” on page 206
207569-F
• “Saving changes to graphical folder views with Auto Save” on page 203
• “Navigating between Auto-Save settings” on page 204
• “Setting InfoCenter print options” on page 213
• “Closing a folder view” on page 213
• “Organizing information in tables” on page 213
Folder view layers
At installation, folders default in the database layer, the most detailed view. You
can transform the orientation of the current folder to emphasize another network
layer. For example, using either the View menu or one of the tools from the
toolbar, you can change from a database layer view to an Internet layer view of the
objects in the current view. The InfoCenter display layers are listed and described
in Table 33, that also shows the toolbar button you can use to transform the view.
Table 33 InfoCenter folder view layers
Toolbar
Layer button Description
Database The database layer view is the most detailed folder view. You
can see folder contents and interconnected links and
discovered devices (irrespective of the object layer attribute)
as they are represented in the Optivity NMS database,
independent of the topology.
Internet Displays layer 3 network elements and interconnect links
(Network) from the database as well as layer 3 logical links derived from
the topology database. Passport nodes will display, but their
trunks display only if running interLAN switch (ILS) routing.
You can see routing between IP subnets. Routers are
connected to subnets and WANs at the Internet layer.
Broadcast domains and routing between broadcast domains
also occur at the Internet layer.
Datalink Displays layer 2 network elements and interconnecting links
from the topology database as well as layer 2 logical links
derived from the topology database.
You can see collision domains and bridging or switching
between the collision domains. You can also see switches
connected to logical segments and other switches.
Physical Displays layer 1 networking elements and interconnect links
from the topology database. You can see physical
connectivity between hubs, switches, and routers.

Table 33 InfoCenter folder view layers (continued)
Toolbar
WAN Trunk Displays a WAN trunk view of the current folder.
Switch Displays a set of switches interconnected by trunk links. You

Community can see all of the VLANs configured in a switch community
and the routing between these VLANs in this view. Passport
nodes and trunks are not displayed in this view.
VLAN Displays the details of a specific VLAN. You can see all of the
switches participating in the VLAN and all of the logical trunk
links that are forwarding traffic between switches in the
VLAN. Passport nodes and trunks are not displayed in this
view
End Node Displays the end nodes connected to the network objects in
the current folder view. Passport nodes and trunks are not
displayed in this view.
Unicast Displays OSPF objects, RIP objects, and ABR links for the
Protocols current folder view containing routers/router links/subnets.
Frame Relay Displays PVC links of all routers, and routers running frame
relay for the current WAN folder view containing routers.
VPLS View Displays OPTera Metro VPLS devices and elements. See
Chapter 11, “Managing virtual private LAN services devices
with Optivity NMS,” on page 369 for more information.
This view and its toolbar button are only available if you are
assigned the VPLS Service by an Optivity NMS
administrator. See “Viewing available services” on page 249
to check your services. See Chapter 2, “Specifying access to
Optivity NMS applications with Access Control
Administration,” on page 75 for information on assigning
services.
Multicast Displays multicast session objects for the routers and
sessions subnets in the current folder view. See Chapter 8, “Managing
multicast sessions and protocols with Optivity NMS,” on page
assigned the Multicast Service by an Optivity NMS
services.
207569-F
Table 33 InfoCenter folder view layers (continued)
Toolbar
Multicast Displays multicast routing objects for the routers and subnets
routing in the current folder view. See Chapter 8, “Managing
multicast sessions and protocols with Optivity NMS,” on page
329.
assigned the Multicast Service by an Optivity NMS
services.
IP-VPN View Displays Contivity devices and aggregate VPN tunnels. See
Chapter 9, “Managing IP Virtual Private Networks with
Optivity NMS,” on page 355 for more information.
assigned the IP-VPN Service by an Optivity NMS
services.

Folder view presentation types
Table 34 describes folder view presentation types and shows their associated
toolbar buttons.
Table 34 InfoCenter folder view presentation types
Toolbar
button Format Description
Graphical Folder contents are represented by icons, designated by either IP
address, DNS name and label, or system name. Icons are
color-coded to reflect the operational status of a network object.
You can rearrange the icons manually and save the custom layout
either manually or automatically (See “Saving changes to
graphical folder views with Auto Save” on page 203). However, if
the folder contents change, then the customized layout might
change the next time the folder opens.
Tabular Folder contents are displayed in the form of a sortable, scrollable,
column-based table. The rows are color-coded to reflect a
network object’s operational status. You can also resize or
reposition the columns. Displays device label, IP address, and
DNS name. This is the default format at installation.
Folder view layouts
You can change the layout of a graphical view, for example, from a view that
emphasizes the network hierarchy to a view that more clearly distinguishes
individual objects.
Table 35 shows the available folder view layouts.
Table 35 InfoCenter folder view layouts
Toolbar
Layout button Description
Symmetrical Nodes and links are spread outward from a central point.
This layout is more spread out than the hierarchical layout,
but lines (links) cross each other less.
Hierarchical Nodes and links are arranged by precedence. A vertical
orientation is used to display the network hierarchy. This
layout is more compact than a symmetrical layout, but can
have more lines (links) that cross each other.
207569-F
Table 35 InfoCenter folder view layouts (continued)
Toolbar
Layout button Description
Tree Show the parent-child relationship with the child nodes
arranged on levels farther from the root node than their
parents.
Circular Nodes and links connect in a circular pattern.
Orthogonal Nodes and links connect at perpendicular intersections.
Custom Manually arrange the position of nodes and links.
Grid Icons are placed in a grid and arranged from left to right, top
to bottom, in the order they were retrieved (until sorted).
Label Layout Arranges link labels to be clearly visible with minimum

overlap. The label layout function expends system resources.
Show Labels Displays or hides icon labels for graphical folder views.
Opening a folder view
To open a folder view in the contents pane, double-click a folder (Figure 37).
Figure 37 InfoCenter folder view
Title bar
View Summary
Display area

The layout of the folder view depends on the settings of the View tab of the
Preferences dialog box:
• If the Default Layout setting is Last Viewed Layout, the folder view is shown
in the same layout as it was the last time it was closed.
• If the Default Layout setting is any other setting, the folder view is shown in
that layout regardless of its format the last time it was closed.
See “Folder view preferences and defaults” on page 206 for more information
about folder view settings.
Table 36 lists and describes the parts of the folder view.
Table 36 Parts of the InfoCenter folder view
Component Description
Title bar Name of folder and subfolder, for example, /Resources/Switches.

View Summary Shows you:
• Objects: number of objects currently in the folder
• Created: localized day, date, and time the folder was created
• Last Modified: localized day, date, and time the contents of the
folder last changed
• Change Count: the +/- difference between the number of objects
currently in the folder, and the number in the folder at the time it was
first opened
Display area Folder contents in a specified format (graphical or tabular).
Folder view shortcut menu
You can use the folder view shortcut menu to get quick access to folder commands
without using the menu bar. The folder view must be in the graphical format to use
the shortcut menu.
Note: The folder view shortcut menu is not available for tabular views.
207569-F
To open the folder view shortcut menu:
From the contents pane, right-click a graphical folder view.

Make sure you right-click a folder view and not an object. Right-clicking an
object opens the object shortcut menu instead of the folder view shortcut
menu.
The shortcut menu (Figure 38) opens.
Figure 38 Folder view shortcut menu
Table 37 describes the folder view shortcut menu commands.
Table 37 Folder view shortcut menu commands
Command Description
Open Opens a submenu of folder formats (graphical or tabular) for opening

the folder in a different view format.
Export Folder Exports the contents of the folder to a file on your client system.
Contents
Paste Pastes the contents of the clipboard into the folder.
Properties Opens the Folder Properties dialog box for viewing or changing the
folder’s properties.

Object shortcut menu
You can use the object shortcut menu to get quick access to object commands
without using the menu bar. The object shortcut menu contains only commands
that are relevant to the selected device. The menu will contain different sets of
commands for different devices.
To open the object shortcut menu:
From an open folder view in the contents pane, right-click an object.

Make sure you right-click an object. Right-clicking any other area of the
folder opens the folder view shortcut menu instead of the object shortcut
menu.
The shortcut menu (Figure 39) opens.
Figure 39 Object shortcut menu
207569-F
Table 38 describes typical object shortcut menu commands. Not all of these
commands will appear for every device type.
Table 38 Object shortcut menu commands
Command Description
Fault Starts any Optivity NMS fault management applications configured to

start for the selected object. See “Recognizing application categories
in InfoCenter” on page 250 for more information.
Accounting Starts Optivity NMS MView User History if configured to start for the
object.
Configuration Starts any Optivity NMS configuration applications configured to start
for the object.
For multicast objects, implements the multicast protocol visualization
rediscovery features.
Performance Starts any Optivity NMS performance applications configured to start
for the object.
Weblinks Links directly to Nortel Networks e-business Web sites.
Open Displays a traversal view of any discovered objects in a temporary
folder. See “Displaying traversal views” on page 305 for more
information.
Cut Moves the selected object to the clipboard. See “Cutting an object
from a view” on page 300 for more information.
Copy Copies the selected object to the clipboard. See “Copying objects
between folders” on page 288 for more information.
Net Aware Finds all ancestors and descendants of an object in all currently-open
Select folder views. See “Using Net Aware Select” on page 310 for more
information.
Device View Opens the Device Detail View window for the selected device.
Age Out Marks the selected device for deletion if it is not found on the next
topology discovery cycle. See “Removing an object with age out” on
Delete Permanently deletes the selected folder or object. See “Permanently
deleting an object” on page 304 for more information.
Expand by Hops Expands the folder view to show the objects connected to the selected
object, or one hop away. Expanded objects are displayed in the same
folder view. Expanded objects are not stored in the folder definition.
See “Using the expand by hops feature” on page 307 for more
information.

Table 38 Object shortcut menu commands (continued)
Command Description
Baseline Opens a submenu of commands for working with multicast baselines.

See Chapter 8, “Managing multicast sessions and protocols with
Optivity NMS,” on page 329 for more information about using multicast
protocol visualization and baselining features.
Unmanage Declares the selected managed device as unmanaged. See
“Unmanaging devices” on page 327 for more information.
Manage Declares the selected unmanaged device as managed. See
“Unmanaging devices” on page 327 for more information.
Properties Opens the Object Properties dialog box. See “Viewing or modifying
object properties” on page 298 for more information.
Subnet Aware Shows the connection between parts of an IP Telephony system &
other network devices
Show UNIs Shows all the user network interfaces on the selected device
Show VPLS Shows all the VPLS services to which the selected UNI belongs
Show Local Shows all the VLANS configured on the selected device
VLANs
For more information about application launch configurations, see Chapter 14,
“Managing network management applications with Application Launch,” on page
521.
Displaying or hiding the view summary details
You can choose whether or not to always display the view summary in folder
views. By default, the view summary is displayed below the title bar, but you can
choose to hide this information. If you decide not to always display the view
summary, you can still show it for the current view.
To set your preference for showing or hiding the view summary details:
The Preferences dialog box opens with the General tab displayed.
dialog box.
2 Click the View tab of the Preferences dialog box.
207569-F
The View tab opens.

3 In the Default format section of the General area, do one of the following:
• To always show the view summary, check Display view summary.
• To always hide the view summary, uncheck Display view summary.
4 Click OK.
Your preference for showing or hiding view summary details is changed. Until
you change it again, InfoCenter always uses this setting.
To display or hide the view summary for the current view:
Choose View > Show View Summary.
The view summary details for the current view are displayed or hidden.
Saving changes to graphical folder views with Auto Save
You can use the InfoCenter Auto Save feature to automatically save any changes
you make to graphical folder views (for example device icon positions, layout
type, and layers).
All folder view changes are saved on a per-user basis; so each Optivity NMS user
has their own set of folder views. The folder view information is saved in the
Table 39 describes the four Auto Save settings:
Table 39 InfoCenter Auto Save settings
Setting Description
Yes InfoCenter saves your graphical folder view changes without prompting
every time you close the view.
No InfoCenter discards your graphical folder view changes without prompting
Disabled InfoCenter prompts whether you want to save graphical folder view changes
Read Only You have read only access to InfoCenter and cannot save folder view
changes

The current setting of Auto Save is shown on the InfoCenter status bar, as shown
in Figure 40.
Figure 40 Auto Save setting on status bar
When Auto Save is disabled, InfoCenter prompts whether you want to save your
changes when you close a view that you have changed, as shown in Figure 41.
Figure 41 Save Changes prompt
To change between the available Auto Save settings, see “Navigating between
Auto-Save settings‚” next.
Navigating between Auto-Save settings
The following sections describe how to navigate between the three Auto Save
settings:
• “Enabling and disabling Auto Save” on page 204

• “Changing Auto Save between Yes and No” on page 205
Enabling and disabling Auto Save
To enable the Auto Save feature using InfoCenter preferences:
1 On the InfoCenter menu bar, choose Options > Set Preferences.

207569-F
Figure 42 Show confirmation dialog always (Auto Save) setting

• To enable Auto Save, clear the Show confirmation dialog always check
box. The Auto Save setting changes to either Yes or No depending on the
last enabled Auto Save setting.
• To disable Auto Save, mark the Show confirmation dialog always check
box. The Auto Save setting changes to Disabled.
Changing Auto Save between Yes and No
To change Auto Save from Yes to No or from No to Yes:
1 Disable Auto Save as described in “Enabling and disabling Auto Save” on

page 204.
2 In InfoCenter, open any folder view.
3 If the folder view presentation is tabular, change it to graphical.
4 In the graphical folder view, drag any icon from its original position.
5 Close the graphical folder view.
6 InfoCenter prompts whether you want to save the changes
Figure 43 Save Changes dialog box (Do not show again check box cleared)

7 On the dialog box, mark the check box for Do not show again.
8 The dialog box changes to prompt you to save or discard all future changes.
Figure 44 Save Changes dialog box (Do not show again check box marked)
9 Click one of the following:

• Click Yes to All to set Auto Save to Yes
• Click No to All to set Auto Save to No
Your changes are reflected in the InfoCenter status bar.
Folder view preferences and defaults
You can specify a default format and layout in which all folder views open. You
can then change the current view as needed.
Table 40 shows the default preferences for the InfoCenter folder views.
Table 40 Default folder view preferences
Preference Default Description
Format Tabular Displays folder contents in the form of a sortable, scrollable,

column-based table. Displays device label, IP address, and
DNS name. The rows are color-coded to reflect a network
object’s operational status. You can also resize or reposition
the columns.
Layout Grid Displays the arrangement of nodes and links you set manually.
Layer Database Displays folder contents, interconnected links, and discovered
devices as they are represented in the Optivity NMS
database, independent of the object layer attributes and
topology.
207569-F
The following sections describe how to set folder view preferences:
• “Changing the default folder view‚” next

• “Changing the current view format” on page 208
• “Changing the current view layout” on page 209
• “Changing the current view layer” on page 209
• “Displaying or hiding icon labels in folder views” on page 210
• “Displaying DNS or system names” on page 211
• “Displaying or hiding a background image” on page 212
Changing the default folder view
You can change the default settings for the format and layout. The current open
view(s) are not affected by the new settings. To see the change in an open folder,
you must close it and then reopen it.
To modify the default view:
dialog box.
2 Click the View tab.
The View tab opens (Figure 45).

Figure 45 InfoCenter Preferences dialog box View tab
3 Select a folder view format and layout preference.

4 Click OK.
The new settings are saved as the default folder view preferences.
Changing the current view format
You can use the toolbar, the view menu, or the shortcut menu to change the format
(graphical or tabular) for the current view.
To change the display format for the current view, do one of the following:
• From the InfoCenter menu bar, choose View > Format, and choose a format
(graphical or tabular) from the submenu.
207569-F
• On the toolbar, click the toolbar button (Table 34) for the format you want to
view.
• Right-click the folder, choose Open from the shortcut menu, and choose a
format (graphical or tabular) from the submenu.
The current view changes to the format you selected. Other views are not affected.
Changing the current view layout
To select a different display layout for the current graphical view:
Select an open graphical view, and do one of the following:
• From the InfoCenter menu bar, choose View > Layout, and choose a
layout from the submenu.
• Click the toolbar button (Table 35) for the layout you want to view.
The graphical view changes to the selected layout. Other folder views are not
affected.
Changing the current view layer
You can transform the current folder view from one layer to another, using either
the toolbar or the View menu.
Note: You must enable discovery for Unicast, Multicast, and frame relay
in the AutoTopology Manager Discovery Options dialog box in order to
view objects in these layers. For more information about the Discovery
Options dialog box, see Chapter 4, “Discovering your network with
To change the layer for the current folder view:
• From the View menu, choose View > Layer, and choose a different layer
from the submenu.
• Click the toolbar button (Table 33) for the layer you want to view.

The current folder view transforms to the new layer. Other views are not
affected. If no objects are discovered for the transformation, an empty folder
is displayed.
Displaying or hiding icon labels in folder views
You can either show or hide the text labels adjacent to icons in folder views. After
you set your preference, InfoCenter uses this setting as the default for all folder
views. You can also change the setting for the current view only.
To show or hide icon labels in folder views:
dialog box.
The View tab opens.
3 In the Display area, do one of the following:
• To show icon labels in folder view, check Display labels.
• To hide icon labels in folder views, uncheck Display labels.
4 Click OK.
Your preference for showing or hiding icons labels in folder views is changed.
Until you change it again, InfoCenter always uses this setting.
To display or hide icon labels in the current view:
From the InfoCenter menu bar, choose View > Show Labels.
On the InfoCenter folder view layout toolbar, click Labels.
Labels in the current folder view are hidden or displayed. Other folder views
are not affected.
207569-F
Displaying DNS or system names
You can display the host name instead of the IP address for devices or their
interfaces. Host names are sometimes easier to recognize than IP addresses. These
host names are resolved from standard name resolution methods such as DNS
(Domain Name System) or the system hosts file.
Although Optivity NMS tabular views always display both, you can choose to
display either DNS names, system names, or IP addresses in graphical views. The
preference to display DNS names and system names is set globally for all Optivity
NMS applications from the InfoCenter Preferences dialog box.
To set the preference to display DNS names or system names instead of IP

addresses:
dialog box.
2 Click the Global tab.
The Global tab (Figure 46) opens.
Figure 46 InfoCenter Preferences dialog box Global tab
3 Choose Display DNS Names or Display System names as appropriate.

4 Click OK.

Optivity NMS devices and interfaces now display DNS names or system
names instead of IP addresses. You can change the display for the current
session from within each Optivity NMS application.
Displaying or hiding a background image
You can set your preference to either display or hide the graphical view
background image in folder views. Once you set your preference, InfoCenter
always uses this default setting. You can also change this setting for the current
folder view.
To display or hide the background image:
dialog box.
The View tab opens.
3 In the Graph display area, do one of the following:
• To display the image, check the Background Image check box.
• To hide the image, uncheck the Background Image check box.
4 Click OK.
To display or hide the background image in the current view:
From the InfoCenter menu bar, choose View > Show Background.
The background image selection is effective for the current folder view only.
Other folder views are not affected.
207569-F
Setting InfoCenter print options
You can use the Print Options area of the Preferences dialog box to choose
whether or not to print the summary information and background image when you
print from a folder. If you choose to print a background image, you must first
select an image from the Folder Properties dialog box (see “About folder
properties” on page 260).
To open the Preferences dialog box where you set print options, choose
Options > Set Preferences.
Closing a folder view
To close a folder view, select the folder view and do one of the following:
• Choose File > Close.

• Click the Windows folder in the upper left corner of the window, and choose
Close from the shortcut menu.
The folder view closes.
Organizing information in tables
The following sections describe how to organize information in tables:
• “Displaying or hiding tabular view grid lines‚” next

• “Sorting table columns” on page 214
• “Resizing table columns” on page 214
• “Repositioning table columns” on page 215
• “Hiding table columns” on page 215
Displaying or hiding tabular view grid lines
You can either display or hide grid lines in tables. At installation, the default is set
to display grid lines in tables.
To set the Tabular Display Grid option:

dialog box.
The View tab opens.
3 In the Tabular display area, do one of the following:
• To display the grid, check the Display grid check box.
• To hide the grid, uncheck the Display grid check box.
4 Click OK.
Sorting table columns
You can sort the information in table columns.
To sort information in the table using the View menu:
1 Select a tabular folder view and choose View > Sort.

2 From the Sort submenu, choose the column heading you want to sort.
The table is sorted in ascending order.
To sort folder view information from the folder view:
Select a tabular folder view and click a column heading.
The table is sorted in ascending order (alphabetically or numerically). Click

the column heading again to reverse the order. The sort order is lost when you
close the folder view.
Resizing table columns
You can resize table columns to show more information. To set the width of a
column, drag the divider between column headings to the desired width.
207569-F
Figure 47 shows the column headings divider.
Figure 47 Resizing columns by dragging column heading dividers
Drag divider to left or right

to adjust column width.
Repositioning table columns
You can reposition table columns in any order for the current view. To reposition a
table column, drag the column head to the new location. The new column order is
only effective for the current view, and is lost when you close the view.
Hiding table columns
You can hide the table columns that you do not want to view by right-clicking on
the column header of the column that you want to hide and choosing Hide.
To view the hidden column, right-click on the table header and choose Show All.
All hidden columns in the table reappear when you refresh the view or transform
between layers. The hidden column settings persist across InfoCenter sessions but
are not migrated across releases.

Menu bar
The InfoCenter menu bar contains the commands described in Table 41.
Note: The menu bar does not appear in a Web browser. Instead, in a Web
browser, you use a menu tool to open InfoCenter menus. For more
information, see “Opening InfoCenter menus in a Web browser” on
page 222.
207569-F
Table 41 InfoCenter menu commands
File New Opens a submenu with the following choices.

• Object—Opens the Object Properties dialog box for defining a new
object.
• Create Link—Creates a link between two physical devices or between a
physical device and an end node.
• Folder—Adds a new folder to the folder tree.
• Blank View—Opens the Folder Properties dialog box for defining a
folder.
• Find Object View—Opens the Find dialog box for locating an object.
Open Opens the Open dialog box for choosing a folder to open.
Close Closes the selected folder.
Save Saves changes to the selected folder view. This command is only available
when the selected folder view is for a folder under the Custom folder.
Save As Opens the Save As dialog box to let you save the selected folder view as a
new subfolder of the Custom folder.
Save As Image Opens the Save As Image dialog box to let you save a graphical folder view
as an image of JPG, SVG, or PNG format. This command is not available
when the selected folder view is in tabular presentation.
Sharing Shares or unshares the selected custom folder. See “Sharing custom folder
queries with other InfoCenter users” on page 291 for more information.
Export Folder Exports the selected folder definition to a file. See “Exporting a folder
Definition definition to a file” on page 294 for more information.
Import Folder Imports folder contents from a file. See “Importing a folder definition from a
file” on page 294 for more information.
Export Folder Exports the contents of a folder to a file on your client system. See
Contents “Exporting folder contents” on page 289 for more information.
Print Opens the system Print dialog box for printing to a printer or file.
Page Setup Opens the Page Setup dialog box for printing to a printer.
Print Preview Opens the Print Preview dialog box.
Exit Closes InfoCenter.

Table 41 InfoCenter menu commands (continued)
Edit Cut Moves the current selection to the clipboard. See “Cutting an object from a
view” on page 300 for more information.
Copy Copies the current selection to the clipboard. See “Copying folders” on
Paste Places the contents of the clipboard into the selected portion of the current
view. See “Pasting an object into a folder” on page 301 for more information.
Clear Removes the contents from a view without copying it to the clipboard.
Select All Selects all objects in the current view.
Net Aware Finds all ancestors and descendants of an object in all currently-open folder
Select views. See “Using Net Aware Select” on page 310 for more information.
Age Out Marks the selected device for deletion if it is not found on the next topology
discovery cycle. See “Removing an object with age out” on page 302 for
more information.
Delete Permanently deletes the selected folder or object. See “Permanently
deleting an object” on page 304 for more information.
Manage/ Toggles the selected object between managed and unmanaged. See
Unmanage “Unmanaging devices” on page 327 for more information.
Rename Renames the selected folder.
Properties Opens either the Folder Properties dialog box or the Object Properties
dialog box for editing.
Find Opens the Find dialog box and lets you specify an IP address, folder, or
name of an object to locate in the current folder. See “Finding an object in a
folder view” on page 311 for more information.
207569-F
View Display Toolbar Displays or hides the toolbar. For more information, see “Displaying or
hiding the toolbar” on page 234.
Display Folder Displays or hides the folder pane. For more information, see “Displaying or
Panel hiding the folder pane” on page 191.
Display Displays or hides the launchpad. For more information, see “Displaying or
Launchpad hiding the launchpad” on page 245.
Display Displays or hides the status bar.For more information, see “Displaying or
Statusbar hiding the status bar” on page 246.
Look and Feel Sets the Look and Feel to metal, CDE/motif, or Windows.
Format Opens a submenu for selecting a display format: Graphical or Tabular. For
more information, see “Folder view presentation types” on page 196.
Layout Opens a submenu for selecting a layout for the current view: Symmetrical,
Hierarchical, Tree, Circular, Orthogonal, Custom, Grid, Label, Auto Arrange,
None, Constant Aspect Ratio. For more information, see “Folder view
layouts” on page 196.
Layer Opens a submenu for selecting a layer for the current view: Database,
Internet, Datalink, Physical, Switch Community, WAN Trunk, VLAN, End
Node, Unicast protocols, Multicast protocols, or Frame Relay protocols. For
more information, see “Folder view layers” on page 193.
Sort Opens a submenu for selecting a table sort option for the current view. You
can select from the list of table columns to sort—Status, Label, Type,
Subtype, IP Label, DNS Label, Is ASBR, Rip Info, Ospf Info, Is FrameRelay,
Discovery Status, Net Addr, Net Mask. For more information, see “Sorting
table columns” on page 214.
Baseline Opens a submenu that lets you view and compare multicast baselines. See
Operations Chapter 8, “Managing multicast sessions and protocols with Optivity NMS,”
Select Selects a node or link to resize, move, or open the shortcut menu.

View Zoom Opens a submenu with the following choices:

(Continued) — Zoom In
— Zoom Out
— Marquee Zoom
— Interactive Zoom
— Custom Zoom
— Fit in View
See “Using the Zoom tools” on page 238 for more information.
Pan Lets you drag an object in the graphical view.
Follow Link Used to navigate to an end node connected to the link.
Overview Displays an overview of the graphical view.
Window
Expand by Expands the folder view to show the objects connected to the selected
Hops object, or one hop away. Expanded objects are displayed in the same folder
view. Expanded objects are not stored in the folder definition. For more
information, see “Using the expand by hops feature” on page 307.
Refresh Refreshes the display.
Path trace Lets you trace the network path between two nodes, or locate an end node.
See Chapter 20, “Tracing paths and locating end nodes,” on page 731.
Show View Shows or hides the View Summary. For more information, see “Displaying
Summary or hiding the view summary details” on page 202.
Show Shows or hides a specified background image or color. For more
Background information, see “Displaying or hiding a background image” on page 212.
Display Text Opens a submenu with the following choices:
— Display Default Names
— Display DNS Names
— Display system names
See “Displaying DNS or system names” on page 211 for more information.
Show Labels Shows or hides object labels in the current view. For more information, see
“Displaying or hiding icon labels in folder views” on page 210.
Reset to Resets the selected folder view to the factory default settings for format,
Factory layout, and layer.
Defaults
207569-F
Options Remote Sets the Remote Selection option to highlight devices within and between
selection Optivity NMS applications. For more information, see “About remote
selection” on page 309.
Display Legend Displays a Legend of the icons used to represent objects in InfoCenter. For
more information, see “Displaying a legend of object icons” on page 247.
Set Open the Preferences dialog box to let you set general, window, view,
Preferences alarm, or global preferences. For more information, see “Folder view
preferences and defaults” on page 206.
Admin Add View Adds the selected view domain to the current user’s Database View. For
Domain to view more information, see “Adding and removing view domains” on page 257.
Remove View Removes the selected view domain from the current user’s Database View.
Domain from For more information, see “Adding and removing view domains” on
view page 257.
Application Opens the Application Launch dialog box for starting local or Web-based
Launch Optivity NMS applications or other element manager products, such as
Device Manager for Passport routing switches. For more information, see
Chapter 14, “Managing network management applications with Application
Launch,” on page 521.
Monitor Opens the Monitor Options dialog box for controlling the level of network
Options monitoring. For more information, see Chapter 15, “Specifying the level of
statistics gathering with Monitor Options,” on page 541.
Device Opens the Device Inventory Viewer application for viewing and managing
Inventory network assets. See Chapter 19, “Managing Network Assets with Device
Viewer Inventory Viewer,” on page 695. for more information.
AutoTopology Opens the AutoTopology Manager application for managing the discovery
Manager process running on the Optivity NMS server. For more information, see
Chapter 4, “Discovering your network with AutoTopology Manager,” on page
137.
Access Control Opens the Access Control application for controlling user access to Optivity
NMS applications and application functions, or creating customized access
groups. For more information, see Chapter 2, “Specifying access to Optivity
NMS applications with Access Control Administration,” on page 75.
Community Opens the Community Strings Editor application for managing community
Strings strings for controlling access to your network. For more information, see
Chapter 3, “Specifying access to devices with the Community Strings
Editor,” on page 101.
Database Opens the Database Administration Tool application for backing up Optivity
application and user databases, or configuring views that will be most useful
to users. For more information, see Chapter 21, “Managing data with the
Database Admin Tool,” on page 743.

Tools Fault Lets you start Optivity NMS fault management applications.
Accounting Starts Optivity NMS MView User History
Configuration Lets you start Optivity NMS configuration applications.
Performance Lets you start Optivity NMS performance applications.
Weblinks Links directly to Nortel Networks e-business Web sites.
Window Tile Displays multiple views in a tiled presentation.
Cascade Displays multiple views in a cascaded presentation.
Restore Restores the window to its original size before it was maximized.
Close All Closes all open folder view windows.
<folder Provides a selection list of the current open folders. Select a folder from the
name(s)> list to bring it to the front of the display.
Help InfoCenter Opens the Table of Contents for InfoCenter Help.
Help
Using Help Opens a Help topic that describes how to use the Help system.
Nortel Opens the Nortel Networks home page.
Networks
Home Page
Online Support Opens the Nortel Networks Enterprise Global Services and Support page.
Downloaded Opens the Downloaded Plugin Styles dialog box to show you the Optivity
Plugin Styles NMS plug-ins that have been downloaded to the Optivity NMS client
system. See “Viewing downloaded plug-ins” on page 249 for more
information.
Show services Opens the Available User Services dialog box to show you a list of available
services. See “Viewing available services” on page 249 for more
information.
About Displays copyright and version information about InfoCenter.
InfoCenter
Opening InfoCenter menus in a Web browser
If you open InfoCenter in a Web browser, the menu bar is not displayed. To access
the menus, you use the first tool in the InfoCenter Web browser toolbar.
207569-F
To open the InfoCenter menu bar in a Web browser:
On the toolbar, click the Menu tool.
A shortcut menu opens (Figure 48), giving you access to the InfoCenter
menus and submenus.
Figure 48 InfoCenter Web browser window with Menu toolbar button
Menu tool
Shortcut menu
Toolbar panel
The InfoCenter toolbar panel contains a family of five separate toolbars organized
into the File, Edit, Presentation, View, and Layout command.
The following sections describe how you can manipulate the toolbars:
• “Stacking toolbars‚” next

• “Dragging a toolbar” on page 225
• “Floating and docking a toolbar” on page 226
• “Opening and closing toolbars in the toolbar panel” on page 226
• “Resizing the toolbar” on page 227
• “InfoCenter toolbar buttons” on page 229

Table 42 shows a partial view of each toolbar and the associated command
function.
Table 42 Partial view of InfoCenter toolbars
Toolbar Command
File
Edit
Presentation
View
Layout
Baseline
Stacking toolbars
InfoCenter lets you stack toolbars on top of one another. The maximum numbers
of rows is equal to the total number opened in the toolbar.
To stack a toolbar:
Drag the toolbar to a row.
Figure 49 shows toolbars stacked in four rows.
207569-F
Figure 49 Stacking toolbars
Dragging a toolbar
You can move a toolbar to another row in the toolbar panel or another location
within or outside of the InfoCenter window. To move the toolbar, drag it by the
handle to a location.
Figure 50 shows the toolbar handle.
Figure 50 Dragging a toolbar
Toolbar
handle

Floating and docking a toolbar
InfoCenter lets you float a toolbar outside of the toolbar panel. To float a toolbar,
drag the toolbar to a location outside of the toolbar panel. The toolbar opens in a
separate frame. You can move the toolbar anywhere in the screen. When you close
the frame, the toolbar is returned to its original location.
Figure 51 shows the toolbar floating in the InfoCenter window contents pane.
Figure 51 Floating and docking a toolbar
Floating toolbar
Opening and closing toolbars in the toolbar panel
InfoCenter lets you open and close toolbars in the toolbar panel. An opened
toolbar is displayed in the toolbar panel. A closed toolbar is removed from view in
the toolbar panel.
To open a toolbar:
1 Right click the toolbar panel.
207569-F
The toolbar panel shortcut menu opens as shown in Figure 52. A closed
toolbar is denoted by a de-selected command. The Edit, Presentation, and
Layout commands are de-selected.
Figure 52 Toolbar shortcut menu
2 Click toolbar names to add or remove them. Check marks show which
toolbars are currently on the toolbar panel.
To close a toolbar, do one of the following:
Right click a toolbar handle and choose Close.

Right click the toolbar panel and use the shortcut menu to remove the
toolbar.
Resizing the toolbar
Optivity NMS lets you resize the InfoCenter window. If you reduce the size of the
InfoCenter window, the toolbar panel also resizes and some icons disappear from
view. In this case, a More button and an expansion symbol are displayed on the
toolbar. The A fully minimized toolbar contains a single icon and the More button.
Figure 53 shows the More button and expansion symbol displayed on the
Presentation toolbar.
Figure 53 More button shown on a resized toolbar
More button

To display the icons that are not in view, click the More button. The toolbar
shortcut menu opens, listing the icons not in view.
To select which icons display in the resized toolbar:
1 Click the More button.

The toolbar shortcut menu opens, displaying the icons not in view. Figure 54
shows two examples: the Presentation toolbar at the regular size and the
Presentation toolbar resized.
In this example, because of its size, only three icons are displayed on the
toolbar and the other icons are listed in the toolbar shortcut menu.
Figure 54 Presentation toolbar at regular and reduced size
Regular size
toolbar
Resized
toolbar
Icons not in
view
2 Click an icon.
For example, the Grid layout icon is clicked and is swapped with the Tree
layout icon, as shown in Figure 55.
Figure 55 Selecting an icon
Grid layout
icon
Tree layout
icon
When a resized toolbar is dragged outside the toolbar panel, the toolbar is
expanded to show all of the icons.
207569-F
InfoCenter toolbar buttons
The toolbar provides quick access to commonly used InfoCenter functions.
To view the name of a toolbar button:
Point to the toolbar button.
Its name is displayed next to the toolbar button, and its function is displayed
in the status bar at the bottom of the window.
Table 43 lists and describes the InfoCenter toolbar buttons.
Table 43 InfoCenter toolbar buttons
Button Name Description
Menu When the InfoCenter window is displayed in a Web browser,

opens a menu of InfoCenter commands.
New Creates a new folder named New Folder.
Create link Creates a link between two physical devices or between a

physical device and an end node. You must specify the slot
and port.
Open Opens the Open dialog box that prompts for a folder name.
Save Saves the changes made to the current folder view.
Print Prints the contents of the selected folder.
Print preview Opens the Print Preview dialog box.
Help Opens Help.
Cut Moves the selection from the current view to the clipboard.
For more information, see “Cutting an object from a view” on
page 300.
Copy Copies the selection from the current view to the clipboard.
For more information, see “Copying folders” on page 287.

Table 43 InfoCenter toolbar buttons (continued)

Paste Places the contents of the clipboard into the selected portion
of the current view. For more information, see “Pasting an
object into a folder” on page 301.
Find Searches the active window (graphical or tabular format) for
the object’s label. Use (*) to match any number of characters,
or use a question mark (?) to match any single character.
Properties Opens the Folder Properties dialog box or Object Properties
dialog box for the selected object.
Graphical Displays folder contents in a graphical format, using links to

View depict any physical interconnections between network
devices. When graphical view is selected, you can access the
Layout submenu commands: symmetrical, hierarchical,
circular, orthogonal, or custom. For more information, see
“Folder view presentation types” on page 196.
Tabular View Displays folder contents in a table.
Select Lets you select nodes and links.

• Right click and selected node or link to open the
respective shortcut menu or to drag the node.
• Resize a node by dragging the resizing handle.
See “Using the select tool” on page 236 for more information.
Zoom in Zooms in on items in the graphic view. The zoom percent
increases when you click the graph. The click point is
centered in the graph. See “Zooming in or out on a graphic
Zoom out Zooms out on items in the graphic view. The zoom percent
decreases when you click the graph. The click point is
centered in the graph. See “Zooming in or out on a graphic
Marquee Lets you select an area of the graph to zoom into. The zoom
Zoom percentage increases when you click and drag the mouse
over an area. The zoom percentage is adjusted so that the
selected area fills the whole view. See “Using marquee zoom”
207569-F
Interactive Lets you select an area of the graph and scroll the view up
zoom and down.
• The zoom percentage increases when you click and drag
the mouse downwards.
• The zoom percentage decreases when you click and drag
the mouse upwards.
See “Using interactive zoom” on page 238 for more
information.
Custom zoom Lets you enter the zoom percentage in a dialog box. See
“Using custom zoom” on page 239 for more information.
Fit in window Adjusts the zoom percentage to display the whole graph in
the view area. See “Using fit in window” on page 239 for more
information.
Pan view Lets you drag the graph in any direction to view its contents.
See “Pan view” on page 240 for more information.
Follow link Scrolls the graph window from node to node along the
selected link.
• The graph window travels along the first outgoing link to
the link’s target node.
• If there are no outgoing links, the graph window travels
along the first incoming link to the link’s source node.
• If you click any link, the graph window travels along the
link to that link’s end node that is farthest away from the
cursor position.
See “Follow link” on page 240 for more information.
Overview A read-only window that contains only a read-only view of the
window active graph.
• The entire graph is shown within the overview window and
a highlighted rectangle covers the region that is displayed
in the active window.
• The highlighted rectangle lets you change the view by
changing the focal point and the zoom level of the active
graph window.
The overview window provides a mechanism to let you know
where you are in the context of the entire graph. See “Using
the overview window” on page 241 for more information.


Database Transforms the current view to a view of the Database. The
database layer view is the most detailed folder view. You can
see folder contents and interconnected links and discovered
devices (irrespective of the object layer attribute) as they are
represented in the Optivity NMS database, independent of the
topology.
See “Changing the current view layer” on page 209 for more
information.
Internet Transforms current view to a top-level (internet level) look --
routers, ip subnets, and LAN segments.
Datalink Transforms current view to a Data Link view (LAN segments

and bridges or switches in a subnet).
Physical Transforms current view to a Physical view (hubs, switches,

and routers within the Ethernet, FDDI, or token ring segment).
WAN Trunk Transforms the current view to a WAN trunk view.
Switch Transforms the current view to a view of the Switch

Community Community.
VLAN Transforms current view to a view of the VLAN layer.
End Node Opens the End Node Locator dialog box.
Unicast Displays OSPF objects, RIP objects, and ABR links for the
current folder view containing routers, router links, and
subnets.
Multicast Displays multicast session objects for the routers and subnets
sessions in the current folder view.
assigned the Multicast service by an Optivity NMS
services.
207569-F
Multicast Displays multicast routing objects for the routers and subnets
routing in the current folder view.
assigned the Multicast service by an Optivity NMS
services.
Frame Relay Displays PVC links of all routers, and routers running frame
relay for the current WAN folder view containing routers.
IP-VPN Displays Contivity devices and VPN tunnels. See Chapter 9,

Service “Managing IP Virtual Private Networks with Optivity NMS,” on
assigned the IP-VPN service by an Optivity NMS
services.
VPLS Displays OPTera Metro VPLS devices and tunnels. See
Chapter 11, “Managing virtual private LAN services devices
with Optivity NMS,” on page 369 for more information.
This toolbar button is only available if you are assigned the
VPLS Service by an Optivity NMS administrator. See
“Viewing available services” on page 249 to check your
services. See Chapter 2, “Specifying access to Optivity NMS
applications with Access Control Administration,” on page 75
for information on assigning services.
Expand by Automatically adds all links and objects to the folder view that
Hops are one hop away from the selected node. The links and
objects displayed when you Expand by Hops are not stored in
the folder definition. For more information, see “Using the
expand by hops feature” on page 307 or “Expanding by hops”
on page 308.
Refresh Updates the current view.
Path trace Displays the network path between two nodes. See
Chapter 20, “Tracing paths and locating end nodes,” on page


Symmetrical Replots a graphical display in a symmetrical layout.
Hierarchical Replots a graphical display in a hierarchical layout.
Tree Show the parent-child relationship with the child nodes

arranged on levels farther from the root node than their
parents.
Circular Replots a graphical display in a circular layout.
Orthogonal Replots a graphical display in an Orthogonal layout.
Custom Creates a customized view that you can name and save in the
Grid Displays or hides the table grid.
Label layout Arranges link labels to be clearly visible with minimum

overlap. The label layout function expends system resources.
Show Labels Displays or hides labels for network entities.
Save baseline Saves a baseline for the current multicast session or view.
See “Saving multicast session baselines” on page 336 for
more information.
Set baseline Toggles the selected baseline between active and inactive.
active/inactive See “Designating baselines as active or inactive” on page 341
Compare Compares the selected baseline with either the current
baseline session or view, or with another baseline of the same type.
See “Comparing multicast session baselines” on page 342 for
more information.
Delete Deletes the selected baseline. See “Deleting session
baseline baselines” on page 338 for more information.
Displaying or hiding the toolbar
You can hide the toolbar to gain more window area to view network information.
There are two ways to do this. If you set the toolbar preference to hide the toolbar,
it is always hidden when you open InfoCenter.
207569-F
To always hide (or display) the toolbar when you open InfoCenter:
For detailed information about the Preferences dialog box, click Help in the
dialog box.
2 Click the Window tab.
The Window tab (Figure 56) opens.
Figure 56 Window tab
3 In the Toolbar area, do one of the following:

• To hide the toolbar, check Hide.
• To display the toolbar, uncheck Hide.
4 Click OK.
The dialog box closes and the toolbar is displayed or hidden.

To display or hide the toolbar for the current session only:
From the InfoCenter menu bar, choose View > Display Toolbar.
Advanced graphic viewing tools
InfoCenter provides advanced graphic viewing tools that let you arrange, view,
and print folder contents in the graphical view. In summary, the advanced graphic
tools include the following features:
• “Using the select tool‚” next

• “Using the Zoom tools” on page 238
• “Pan view” on page 240
• “Follow link” on page 240
• “Using the overview window” on page 241
• “Linking nodes in the graphical view” on page 241
Using the select tool
InfoCenter lets you use the Select tool to select objects and links. The Select tool
is available by default in the graphic view. The following sections describe select
actions:
• “Selecting an object‚” next

• “Dragging an object” on page 237
• “Opening an object shortcut menu” on page 237
• “Resizing an object” on page 237
Selecting an object
To select an object:
1 Open a folder.
See “Opening a folder” on page 278 for more information.
• On the toolbar panel, click Graphical view.
207569-F
• From the InfoCenter menu, click View > Format > Graphical.
• On the toolbar, click Select.
• From the InfoCenter menu, click View > Select.
4 In the graphical folder view, click an object.
Dragging an object
To drag an object:
1 In the graphical view, do one of the following:

2 Click and drag the left mouse button on an object to a location.
Opening an object shortcut menu
To open the object shortcut menu:

2 Left click an object.
3 Right click the selected object.
The object shortcut menu opens.
Resizing an object
To resize an object:

2 Left click an object.

3 Drag the object’s resizing handle.
Using the Zoom tools
InfoCenter provides advanced zooming features that let you zoom in or out on a
graphical folder view. The following sections describe zoom operations:
• “Zooming in or out on a graphic view‚” next

• “Using marquee zoom” on page 238
• “Using interactive zoom” on page 238
• “Using custom zoom” on page 239
• “Using fit in window” on page 239
Zooming in or out on a graphic view
To zoom in or zoom out on a graphical view:

• On the toolbar, click Zoom in.
• On the toolbar, click Zoom out.
2 Click anywhere on the view.
Using marquee zoom
The marquee zoom lets you select an area of the graph to zoom into. The zoom
percentage increases when you click and drag the mouse over an area. The zoom
percentage is adjusted so that the selected area fills the whole view.
To perform marquee zoom:
1 On the toolbar panel, click Marquee zoom.

2 Left click and drag the left mouse button over an area.
The selected area is enlarged and fills the whole view.
Using interactive zoom
InfoCenter lets you select an area of a graph and scroll the view up and down.
207569-F
To perform an interactive zoom:
1 On the toolbar panel, click Interactive zoom.

• Left click and drag the left mouse button up.
The view reduces in size (zoom percentage decreases) when you click and
drag the mouse upwards.
• Left click and drag the left mouse button down.
The zoom percentage increases when you click and drag the mouse
downwards.
Using custom zoom
InfoCenter lets you customize the zoom factor by entering the zoom percentage in
a dialog box. By default, zoom is set to 100 percent.
To use custom zoom:
1 On the toolbar panel, click Custom zoom.

2 In the Custom Zoom dialog box, enter a zoom value and click OK.
Using fit in window
InfoCenter lets you fit all of the network objects in a window.
To arrange all of the objects in a window:
On the toolbar panel, click Fit in window.
All of the objects are displayed in the window.

Pan view
InfoCenter lets you use panning to drag a graph in any direction to view its
contents.
To pan a graph:
1 On the toolbar panel, click Pan.

2 Click and drag the left mouse button in the graph.
The view pans in the direction that you drag the Pan icon.
Follow link
InfoCenter lets you use follow link to navigate a link from origination to
destination. Follow link scrolls the graph window from node to node along the
selected link.
• The graph window travels along the first outgoing link to the link’s target
node.
• If there are no outgoing links, the graph window travels along the first
incoming link to the link’s source node.
• If you click any link, the graph window travels along the link to that link’s end
node that is farthest away from the cursor position.
To navigate a link:
1 On the toolbar panel, click Follow link.

2 Click a link.
207569-F
Using the overview window
InfoCenter lets you view an overview window that contains a read-only view of
the active graph. The entire graph is shown within the overview window and a
highlighted rectangle covers the region that is displayed in the active window. The
highlighted rectangle lets you change the view by changing the focal point and the
zoom level of the active graph window.
To open the overview window:
On the toolbar panel, click Overview window.
The Overview window opens. Figure 57 illustrates the overview window.
Figure 57 Overview window
Linking nodes in the graphical view
InfoCenter lets you use the Link creation tool to create visual links between nodes
in the graphical view. See the following sections for more information:
• “Creating a link‚” next

• “Cancelling a link” on page 242

Creating a link
To create a link:
1 On the InfoCenter toolbar, click Create Link.

The mouse pointer becomes the Create Link wand.
2 Click on the two objects that you want to link.
A visual link is established between the two nodes and the Object Properties
dialog box opens. Figure 58 illustrates a visual link created between two
switches.
Figure 58 Visual link created between two nodes
3 Enter the slot and port information in the Object Properties dialog box.
4 Click OK.
The link is created and the Object Properties dialog box closes.
Cancelling a link
You cancel a link in two ways:
• After a visible link is already created—In this case, the visible is created in the
graph and the Object Properties dialog box is opened.
• Before the visible link is created—In this case, the visible link is not created
in the graph and the Object Properties dialog box is not opened.
207569-F
To cancel a link before you finish creating it:
After you click the origination node, and before you click the second end
node, press [ESC] to abort the process.
The visual link is deleted from the graph and the link creation process is
cancelled. A new link is not created until you click OK in the Object Properties
dialog box.
Using the InfoCenter launchpad
The InfoCenter launchpad tools give you access to other applications and services.
When you click a launchpad tool, a dialog box opens from which you can choose
the application or service you want to launch. For example, the Fault tool launches
Fault Summary, Path Trace, End Node Locator, Ping, and Fault History. For more
information, see “About Optivity integrated applications” on page 249. Figure 59
shows the launchpad tools and the applications and services they launch.
The launchpad is hidden by default. See “Displaying or hiding the launchpad” on

page 245 to show the launchpad.

Figure 59 InfoCenter launchpad
Configuration
Expanded View
Telnet
Rediscover
Embedded Web Interface
Port Profile
TD Continuity Test
Security
Performance
Call View
Fault
OmniView
Events/Fault view
Segment Statistics
Events/Trap view
History
Events/Syslog view
Protocol Distribution
End Node Locator
VLAN Distribution Weblinks
Ping Accounting Priority Distribution Links to e-business
History MView Web sites
For detailed information about using the InfoCenter Launchpad, see “Starting
applications from the launchpad” on page 253.
Note: Other applications can appear in a selection dialog box if you

have other products loaded or integrated with Optivity NMS. For more
information, see “Managing network management applications with
Application Launch” on page 521.
207569-F
Displaying or hiding the launchpad
The launchpad is hidden when the InfoCenter window opens. If you use the
preference setting to show the launchpad, and then decide you want it hidden for
the current session, you can hide it without changing your preference setting.
To display or hide the launchpad for the current session:
From the InfoCenter menu bar, choose View > Display Launchpad.
To set your preference for either hiding or showing the launchpad:
dialog box.
The Window tab (Figure 56 on page 235) opens.
3 To hide the launchpad, check Hide. To show the launchpad, uncheck Hide.
4 Click OK.
The dialog box closes and the launchpad is displayed or hidden. Until you
change it again, InfoCenter always uses this setting.
Displaying or hiding a launchpad tools and text labels
You can choose to hide launchpad tools and text labels. Until you change it again,
InfoCenter always uses your setting.
To display or hide a launchpad tool or text label:
dialog box.


3 In the launchpad area:
• Click Display icons to toggle between hidden and displayed.
• Click Display labels to toggle between hidden and displayed.
4 Click OK.
Status bar
The status bar is located at the bottom of the InfoCenter window. Table 44
describes the parts of the InfoCenter status bar.
Table 44 InfoCenter status bar fields
Field Displays information about:
Message Menu When you move the pointer over a menu command or a tool, a
commands short message describes its use.
and tools
InfoCenter When you perform an InfoCenter operation, a short message
operations describes the operation.
Discovery The current status of AutoTopology discovery operations.
status
Auto Save Shows the current setting for the Auto Save feature. See “Saving changes to
graphical folder views with Auto Save” on page 203 for more information.
Start NMS The name of the server to which InfoCenter is connected.
Start The date and time the current InfoCenter session began.
User The login name of the current Optivity NMS user.
Displaying or hiding the status bar
To gain more space in the display window, you can set your preference to hide the
status bar. By default, the status bar is displayed. If you choose to always hide the
status bar, you have the option of displaying it for the current session.
To set your preference to show or hide the status bar:
207569-F
dialog box.
3 In the Status bar area, do one of the following:
• To hide the status bar, check Hide.
• To display the status bar, uncheck Hide.
4 Click OK.
The dialog box closes and the status bar is hidden or displayed. Your
preference for showing or hiding the Status bar is changed. Until you change
it again, InfoCenter will always use this setting.
To display or hide the status bar for the current session:
From the InfoCenter menu bar, choose View > Display Status Bar.
Displaying a legend of object icons
You can view the icons used to represent network objects. From the Legend dialog
box, you can view all types of icons, or just the icons that are used to represent
specific object types, such as probes.
To view icons used to represent network objects in InfoCenter:
1 Click Options > Display Legend.

The Legend dialog box opens, displaying all types of icons in the Icons
window.

Figure 60 Legend dialog box — all icon types
2 In the Object Type list, click an object type, such as Probe.

The icons used to represent probes are displayed in the Icons area (Figure 61).
Figure 61 Legend dialog box — Probe icons
3 Click OK.
The Legend dialog box closes.
207569-F
Viewing downloaded plug-ins
You use the Downloaded Plugin Styles dialog box to view a list of the Optivity
NMS plug-ins downloaded to an Optivity NMS client. The list also shows the
default presentation and layout styles for each plug-in.
To view a list of the downloaded plug-ins:
On the InfoCenter menu bar, choose Help > Downloaded Plugin Styles.
The Downloaded Plugin Styles dialog box opens.
Viewing available services
You can use the Available User Services dialog box to view a list of available
services assigned to you:
On the InfoCenter menu bar, choose Help > Show services.
See Chapter 2, “Specifying access to Optivity NMS applications with Access

Control Administration,” on page 75 for information on assigning services.
About Optivity integrated applications

InfoCenter is the top level control layer for Optivity NMS. You can use the
InfoCenter launch functions to transfer contextual information from InfoCenter to
other Optivity NMS applications that support specific functional areas, such as
fault management and configuration management. For more detailed information
about configuring Optivity NMS launch points, see Chapter 14, “Managing
network management applications with Application Launch,” on page 521.
The following topics describe these launch functions in InfoCenter:
• “Recognizing application categories in InfoCenter‚” next

• “Recognizing applications you can start from InfoCenter” on page 251
• “Starting applications from the Admin menu” on page 252
• “Starting applications from the Tools menu” on page 252

• “Starting applications from the launchpad” on page 253

• “Starting applications from the shortcut menu” on page 253
Recognizing application categories in InfoCenter
The InfoCenter Tools menu, launchpad, and contents pane shortcut menu group
applications into the categories shown in Table 45.
Table 45 InfoCenter application categories
Category Launchpad tool Applications
Fault Fault Summary

Ping
History
Accounting MView (with user history)
Configuration Expanded View

Telnet
Rediscover
Port Profile
Add to Watch List
Remove from Watch List
Save Baseline
Performance Call View
OmniView
Segment Statistics
History
VLAN Distribution
Priority Distribution
Security
WebLinks Corporate
Support
207569-F
Recognizing applications you can start from InfoCenter
You can start many applications from InfoCenter. Table 46 lists the elements you
can use to start Optivity NMS applications.
Table 46 InfoCenter elements used to start Optivity NMS applications
InfoCenter element Starts these applications
Admin menu Application Launch

Monitor Options
Device Inventory Viewer
Access Control
Community Strings Editor
Database Admin Tool
Tools menu Event View
Launchpad Trap View
Contents pane Syslog View
shortcut menu Rediscover
Port Profile
Ping
History
Expanded View
Telnet
CallView
OmniView
Segment Statistics
History
VLAN Distribution
Priority Distribution

Starting applications from the Admin menu
You can start many applications from the InfoCenter Admin menu.
To start an application from the Admin menu:
From the menu bar, choose an application from the Admin menu.
Starting applications from the Tools menu

You can start other applications from the Tools menu. Not all applications are
configured for all object types. When you select an object in a folder view, only
the applications that are configured to start for that object will be available in the
Tools menu.
To start an Optivity NMS application from the InfoCenter Tools menu:
1 In the folder pane, double-click a folder name.

The folder view opens in the contents pane.
2 In the folder view, select a network object (device or link).
The object is highlighted.
3 From the Tools menu, choose an application category.
A submenu of applications that are configured to start for the object opens.
4 From the submenu, choose an application.
5 If the object you selected has multiple values, such as interfaces or IP
addresses, choose one from the Launch Options dialog box (Figure 62).
6 Click OK.
The application starts.
207569-F
Figure 62 Launch Options dialog box
Starting applications from the launchpad
You can launch other applications from the launchpad. Although not all
applications are configured for all object types, those that are configured to start
for a selected object are available from the launchpad.
To start an application from the launchpad:
1 Select a network object (device or link) in a folder view.

2 On the InfoCenter launchpad, click an tool icon.
The Selection dialog box of applications configured to start for the object
opens.
3 Choose an application.
addresses, choose one from the Launch Options dialog box (Figure 62) and
click OK.
Starting applications from the shortcut menu
You can start other applications from the object shortcut menu. Although not all
applications are configured for all object types, those that are configured to start
for a selected object are available when you open the shortcut menu.

To start an application from the folder view shortcut menu:
1 Right-click a network object (device or link) in a folder view and choose an

application category from the object shortcut menu.
A submenu of applications configured to start for the object opens.
2 Select an application.
addresses, choose one from the Launch Options dialog box (Figure 62) and
click OK.
207569-F
255
Chapter 6
Organizing your network with InfoCenter
This chapter describes how to use InfoCenter as a central location for grouping
your network resources logically by device type, criticality, fault status, or other
pertinent category. It includes the following topics:
• “About folders‚” next

• “Predefined folders” on page 256
• “Discovering your network resources” on page 256
• “About folder properties” on page 260
• “Creating and configuring custom folders” on page 268
• “Working with folders” on page 277
• “Working with objects” on page 295
• “Working with InfoCenter search functions” on page 311
• “Visualizing MLT and SMLT configurations” on page 312
• “Troubleshooting InfoCenter” on page 315
About folders
InfoCenter lets you group and visualize your network resources using folders.
Folders store InfoCenter search results. Each time you open a folder, InfoCenter
queries the database for objects that match its definition and fall within your view
domains. Folder definitions are made up of:
• Folder scope (object type and subtype)

• Folder filter (attribute(s) that constrain the scope)
InfoCenter ships with folders whose scope and filter are already defined. You can
refine or change these definitions.

256 Chapter 6 Organizing your network with InfoCenter
Predefined folders
InfoCenter ships with the folders described in Table 47:
Table 47 Predefined InfoCenter folders
Folder Subfolders
Alarms Contains alarms of Critical, Warning, and Caution severity.

Baselines Contains Multicast Routing, Multicast Sessions, and Multicast Views.
Only present if Multicast plug-in is installed, and you are allocated the
Multicast service.
Custom Contains all of the custom folders you create.
View Domains Contains all of the view domains you have been assigned.
Resources Bridges, ELANs, Hubs, IP-Telephony, IP-VPN, Internet, Management
Servers, Multicast, Probes, Routers, Security Clusters, Segments,
Subnets, Switch Communities, Switches, Unicast, VLANs, VPLS,
WANs, WLAN Devices
Shared Contains all of the folders that other Optivity NMS users share with you.
For a description of these folders, see “Folder tree” on page 186.
Discovering your network resources

Before you can view any of your network resources in your resource folders, you
must make them visible to InfoCenter by doing the following:
Launch Optivity NMS AutoTopology Manager, enter a seed specification,

and run discovery.
For more information about the discovery process, see Chapter 4,

“Discovering your network with AutoTopology Manager,” on page 137.
Note: You must enable discovery for Unicast, Multicast, and frame relay
in the AutoTopology Manager Discovery Options dialog box in order to
view objects in these layers. For more information about the Discovery
Options dialog box, see Chapter 4, “Discovering your network with
207569-F
Chapter 6 Organizing your network with InfoCenter 257
The following sections describe various aspects of Optivity NMS network

discovery:
• “Adding and removing view domains‚” next

• “Rediscovering network resources” on page 259
Adding and removing view domains
In order to see discovered objects in your resource folders, your database view
must contain one or more view domains. Your resource folders show only the
devices within your database view.
You can tell which view domains are in your database view by looking at the View
Domains folder view. The view domains in your database view are shown in bold
text. View domains not in the database view are shown in normal text.

The view domains folder shows only those view domains that have been assigned
to you by an Optivity NMS administrator using Access Control Administration.
See Chapter 2, “Specifying access to Optivity NMS applications with Access
Control Administration,” on page 75 for more information about creating and
assigning view domains.
Figure 63 View domains folder showing domains within database view
Bold text
indicates view
domain in
database view
Normal text
indicates view
domain not in
database view
Note: InfoCenter automatically adds the view domains created during

AutoTopology discovery to your database view.
To add view domains to, or remove them from your database view:
1 From the InfoCenter folder tree, (+) expand the View Domains folder.
2 Select a view domain to add or remove.
• To add the domain, right-click the domain and choose Add view domain
to view, or choose Admin > Add View Domain from the InfoCenter menu
bar.
The view domain is added to your database view. The objects within the
domain are shown in your resource folders.
207569-F
• To remove the domain, right-click the domain and choose Remove view
domain from view, or choose Admin > Remove View Domain from the
InfoCenter menu bar.
The view domain is removed from your database view. The objects within
the domain are removed from your resource folders.
Rediscovering network resources
You can update InfoCenter objects by rediscovering a switch, hub, view domain,
or multicast protocol session. Rediscovery may take several minutes to complete.
When the rediscovery completes, the last update time of the object changes, and
the traversal views for subnets and multicast sessions are updated.
Note: To start rediscovery, the specific topology process must be

running. See Chapter 4, “Discovering your network with AutoTopology
Manager,” on page 137.
Rediscovery launches the discovery process and updates the database with current
information as shown in Table 48.
Table 48 Rediscovery processes
Object Description
Subnet Triggers the subnet discovery process (topst), and updates the traversal
view of subnet contents. If new switches or Hubs are discovered during
rediscovery, the end node discovery process (topdt) is triggered to
discover end nodes for these newly discovered devices.
View domain Triggers the router discover process (toprt). If new routers or subnets are
found, the topst process is triggered, followed by end node discovery
(topdt), and, if selected by the seed, multicast protocol discovery process
(protmr).

Table 48 Rediscovery processes (continued)
Object Description
Switch and Triggers the end node discovery process (topdt) to discover end nodes for
hub the selected switch or hub. If new end nodes are discovered, the multicast
protocol discovery process (protmr) is triggered to update the discovered
routers, subnets, and router links for the multicast session.
Multicast Triggers the multicast protocol discovery process (protmr) to rediscover
protocol the selected multicast session. Updates the traversal view (discovered
routers and subnets participating in the multicast session) for the
multicast session. If the session isn’t active at the time of rediscovery, the
session icon disappears from InfoCenter.
For more information about multicast protocol rediscovery, see Chapter 8,
“Managing multicast sessions and protocols with Optivity NMS,” on page
329.
To rediscover a resource or view domain:
1 In the contents pane, select a resource or view domain.

2 Right-click the resource and choose Configuration > Rediscover, or from the
menu bar choose Tools > Configuration > Rediscover.
The discovery process is launched. When complete, the last update time of the
object changes, and all related views are updated. During the rediscovery
process, the InfoCenter status bar shows the status of the operation
(Figure 64).
Figure 64 Typical status bar indication of rediscovery
About folder properties

You can define the content and presentation of any folder in the Folder Properties
dialog box. The following sections describe folder properties:
• “Folder scope‚” next

• “Folder filter” on page 262
• “Presentation tab” on page 267
207569-F
Folder scope
You define search scope and filter properties in the Search tab of the Folder
Properties dialog box. The search function retrieves and groups network objects
according to folder definitions. The following are the properties that define the
Search scope.
• “Object name‚” next

• “Object type” on page 261
• “Object subtype” on page 262
• “Device type” on page 262
• “Subnet assignment” on page 262
Object name
The InfoCenter Find command uses the object name or IP address to locate
objects. You can use numbers, characters, or a combination of both to name an
object. For more information about the Find command, see “Working with
InfoCenter search functions” on page 311.
Object type
Table 49 lists the types of network objects you can define for an InfoCenter folder.
The object type is related to the object subtype and device.
Table 49 InfoCenter object types
Agent Undiscovered Device Multicast Session

Hub Bridge OSPF Area
Switch Optivity Station Routing Domain
Router Seed Switch Community
Layer 3 Switch Probe VLAN
Cable Modem End Node Subnet
Enterprise Server Link Segment
Black Box Interface Wide Area Network
Bridge Cloud ELAN

Object subtype
The object subtype you define in a folder’s properties is dependent on its object
type. Some object types do not have subtypes.
Device type
The Device type you define in a folder’s properties is the type of network device
listed in the database. Available choices are limited to those available based on the
object type and subtype.
Subnet assignment
When defining a folder’s properties, you can manually assign the name of the
subnet in which the network object is located.
Folder filter
You use the Folder Properties dialog box to configure basic and advanced filter
properties for folder queries. Filter properties are further defined by the following:
• “Filter attributes‚” next

• “Relational operators for filter attributes” on page 266
• “Logical operators for filter attributes” on page 266
Filter attributes
Table 50 lists basic and advanced search filter attributes for the object type “All
Types.” To view advanced attributes, click Advanced in the Properties dialog box.
Table 50 Folder preferences — filter attributes
Attribute Type Value
Bridge Number integer The bridge number from the device.

DLCI 1 integer[] DLCI numbers for one end of a PVC Link.
DLCI 2 integer[] DLCI numbers for one end of a PVC Link.
DNS Label string[68] DNS name of a device.
207569-F
Table 50 Folder preferences — filter attributes (continued)
Discover Frame Relay integer Discovery status for frame relay protocols used by the
Autotopology process.
0 = disabled
1 = enabled
Discover Multicast integer Discovery status for multicast protocols used by the
0 = disabled
1 = enabled
Discover Unicast integer Discovery status for unicast protocols used by the
0 = disabled
1 = enabled
Discovery Status integer Discovery process status used by the Autotopology
process.
1 = Create
2 = Delete
3 = Progress
4 = Failed
5 = Empty
6 = Done
End Subnet Address string[] Ending subnet address for the Autotopology discovery
process.
IP Address string[32] IP address of a device’s interface
IP Label string[68] IP label of device
Interface 1 IP string[32] IP address of the interface on one side of a PVC Link
Interface 2 IP string[32] IP address of the interface on one side of a PVC Link
Is ASBR integer -1 = not discovered or unknown
1 = object is ASBR
Is Frame Relay integer -1 = not discovered or unknown
1 = object is Frame Relay
Label string[68] Network object label that is used to identify the object in a
folder view.
Link Speed integer Link speed
4 or 16 MB (token ring)
10 MB
100 MB
1 GB

Link Type integer Type of link

1 = OTHER
2 = ETHER10
3 = ETHER100
4 = TR4
5 = TR16
6 = FDDI
7 = NNI
8 = UNI
9 = LC_TRUNK
10 = BK_PLANE0
11 = BK_PART_OF
12 = X25
15 = LC_STANDBY
16 = ATM_VIRTUAL
17 = ATM_PHYSICAL
19 = INTER_VLAN
20 = INTRA_VLAN
Module Attachment 1 integer There are two module attachment 1 formats: 1bbxxx and
2bbxxx.
The encoded value of format 1bbxxx is defined as follows:
• 1—network management module (NNM)
• bb—slot where the NNM resides
• xxx—interface number
The encoded value of format 2bbxxx is defined as follows:
• 2—connectivity port on a board
• bb—slot where the board resides
• xxx—port module is connected to
For example, the encoded value for a module in slot 3 and
attached to port 2 is 203002.
Module Attachment 2 integer Same as Module Attachment 1.
Name string[64] Name of the network object.
Net Address string[40] Subnet address. The Net Addr is derived by subnetting the
router interface’s IP address.
Net Mask string[16] Subnet mask used for subnetting the LAN, for example,
255.255.255.0
Object 1 string[64] Name of the object on one side of the link
Object 2 string[64] Name of the object on one side of the link.
207569-F
OSPF Info integer Detailed information for router.

1 = Router is running OSPF
5 = Router is ABR
9 = Router is ASBR
13 = Router is ASBR and ABR
-1 = Router is not running OSPF
Port 1 integer Port number of one side of a segment link.
Port 2 integer Port number of one side of a segment link.
Ring Number integer Token ring number for the segment.
RIP Info integer Detailed router information.
1 = Router is running RIP
-1 = Router is not running RIP
Slot 1 integer Slot number of one side of a segment link.
Slot 2 integer Slot number of one side of a segment link.
Start Subnet Address string[] Starting subnet address used in the Autotopology discovery
process.
Status Integer 0 = Critical
1 = Warning
2 = Caution
3 = Operational
4 = object was created by the discovery process
5 = Discovery in progress
6 = Discovery failed
7 = Network object unmanaged
8 = Network object unknown
9 = Network object is aged out.
10 = Status count
Network objects with a status of “unknown” are displayed in
the system's background color.
Update Contained Element integer Value = 1.
Subtype string[32] Object subtype (see Scope window for list of supported
object subtypes).
Type string[32] Object type (see Scope window for list of supported object
types).
<Type>:<subtype>:<attribute> Groupings of object type with subtype and attribute. See
above values for the specific attribute possibilities.

Relational operators for filter attributes
Table 51 lists the valid operators that you can use with filter attributes.
Table 51 Filter attribute relational operators
Relational Operator Function
> Greater than

< Less than
>= Greater than or equal to
<= Less than or equal to
!= Not equal to (compare strings)
== Equal to (compare strings)
Logical operators for filter attributes
Each object type and subtype has a set of basic and advanced filter attributes that
you can combine to define the scope for the folder search. Table 52 lists the
logical operators that you can use to combine filter attributes.
Table 52 Filter attribute logical operators
Logical operator Function
NOT Excludes
AND Combines, must be both
OR At least one out of the list of choices
Use parentheses (“(“and “)”) to combine multiple assertions.
For example, when you apply the filter SNMP_RdCommunity==public to the

router scope, the query process returns only objects of router type that have public
read community strings.
207569-F
Special characters
You can use the special characters in Table 53 to define and execute the searches
used to determine folder content.
Table 53 InfoCenter special characters
Special
Character Function
? Matches any single character in the string.

For example, to find instances of both “gray” and “grey” in file names, type
gr?y.
* Matches any number of characters in the string.
For example, to find only file names that end with “region,” type
*region.
+ Matches one or more occurrences of a regular expression.
. Matches any character in the string.
[ ] Matches strings containing the individual characters enclosed within the
brackets.
Presentation tab
Use the Presentation tab to configure the presentation for custom folders. This
feature makes it easier for you to distinguish between folder views. You can define
how a custom folder looks (presentation) in the folder pane and in the contents
pane when you open it. The properties you use to do this are called presentation
properties, and you define them on the Presentation tab of the Folder Properties
dialog box. Presentation properties include the following:
• Description
• Background color
• Background image
• Aspect ratio
• Image layout
• Status propagation
Note: You can display either a background color or a background

image, but not both.

Note: To enable the transfer of fault management information to parent

folders and the alarms folder, the status propagation property must be
set.
Although you can merge folders, you cannot merge their definitions. For example,
you can merge a child switch folder with a parent router folder. Both folders
maintain their separate folder definitions and functions.
Folder details
The Details tab in the InfoCenter Folder Properties dialog box contains the
following folder details:
• Names of subfolders within this folder

• Date and time the folder was created
• Date and time the folder was last modified.
Creating and configuring custom folders

You can create subfolders, and define their properties, in the InfoCenter Custom
folder. The following topics describe how to create custom folders and modify
their properties:
• “Creating a folder‚” next

• “Renaming a custom folder” on page 269
• “Configuring search properties for custom folders” on page 270
• “Configuring presentation properties for custom folders” on page 273
• “Selecting a folder background color” on page 275
207569-F
Creating a folder
You can create folders in the InfoCenter Custom folder.
Note: You can only create and customize subfolders of the InfoCenter
Custom folder. All other folders are write-only.
To create a new custom folder:
1 Select the InfoCenter Custom folder.

• From the menu bar, choose File > New > Folder.
• On the toolbar, click New.
A folder is created and labeled New Folder (Figure 65). InfoCenter highlights
the folder name so that you can edit it.
Figure 65 Example of Folder pane with new folder
New folder
3 Enter the new name.

The folder is renamed. You can now assign folder properties.
Note: A folder name cannot exceed 255 characters, including spaces,

and it cannot contain any of the following characters: \ / : * ? “ < > |
Renaming a custom folder
To rename a custom folder:
1 From the folder pane, select the folder.

The folder is highlighted.


• From the InfoCenter menu bar, choose Edit > Rename.
• Right-click the folder and choose Rename from the shortcut menu.
The folder name is selected.
3 Enter the new name.
The folder is renamed.
Configuring search properties for custom folders

To configure search properties for a custom folder:
1 In either the folder pane or the contents pane, select the folder.
Note: If selecting from the contents pane, do not click within the folder
view, because you deselect the folder and select a network object instead.

• From the InfoCenter Menu bar, choose Edit > Properties.
• Right-click the folder and choose Properties from the shortcut menu.
The Folder Properties dialog box (Figure 66) opens with the folder’s name
displayed in the title bar. For detailed information about the Folder Properties
dialog box, click Help in the dialog box.
207569-F
Figure 66 Folder Properties dialog box
3 In the Search Scope area, select the object type(s) or subtype(s).

Use [Ctrl] + click to make multiple selections.
Note: If you select a subtype, do not click the minus (-) sign to collapse
the top level folder. Doing so selects the top level folder and deselects the
subtype. Your last selection is saved to the database.
4 In the Filter area, enter values for the attributes you want to set.
To make additional settings, click Advanced.
The Filter area displays the advanced settings. To return to the previous
attribute settings, click Basic.

Figure 67 Folder properties dialog box Advanced view
See “Folder filter” on page 262 for more information.

• To save your changes and remain in the dialog box, click Apply.
• To save your changes and close the dialog box, click OK.
• To discard your changes and remain in the dialog box, click Reset.
• To discard your changes and close the dialog box, click Cancel.
207569-F
Configuring presentation properties for custom folders
In the Presentation tab of the Properties dialog box, you can configure a custom
folder’s description, background color, icon size, background image, aspect ratio,
icon layout, image layout, and enable status propagation.
Note: You can only change folder properties for custom folders
To configure a custom folder’s presentation properties:
1 In either the folder pane or the contents pane, select the folder you want to
change.
Note: If you select from the contents pane, do not click within the folder
view. When you do this, you deselect the folder and select a network
object instead. If you select a network object and click properties, you
open the Object Properties dialog box instead of the Folder Properties
dialog box

The Folder Properties dialog box opens (Figure 66) with the folder’s name
displayed in the title bar.
For detailed information about the Folder Properties dialog box, click Help on
the dialog box.
3 Click the Presentation tab (Figure 68) to open it.

Figure 68 Presentation tab
4 Make the following settings as needed:

• To add a description, type a description in the Description text box.
• To make changes to icons, background image, aspect ratio, and layout,
click the down arrows and make selections.
• To enable alarm status to propagate to the object’s parent folders and the
Alarms folders, check the Status Propagation check box.
• To change the background color, see “Selecting a folder background
color” on page 275.
• To save your changes and remain in the dialog box, click Apply.
• To save your changes and close the dialog box, click OK.
• To discard your changes and remain in the dialog box, click Reset.
• To discard your changes and close the dialog box, click Cancel.
207569-F
Selecting a folder background color
You can select a background color for each folder. The background color displays
in the graphical view. You can edit the following aspects of a background color
from the Background Color dialog box:
• Choose a color from a color swatch.

• Adjust a color’s HSB (hue, saturation, and brightness).
• Adjust a color’s RGB (red, green, and blue) tones.
Note: You can either display a background color or a background

image, but not both at the same time.
To change a folder’s background color:
1 In either the folder pane or the contents pane, select the folder you want to
change.
Note: If you select from the contents pane, do not click within the folder
view. When you do this, you deselect the folder and select a network
object instead. If you select a network object and click properties, you
open the Object Properties dialog box instead of the Folder Properties
dialog box.

The Folder Properties dialog box opens with the folder’s name displayed in
the title bar.
For detailed information about the Background Color dialog box, click Help
in the dialog box.
3 Click the Presentation tab to open it.
4 Click the Background Color selection bar.
The Background Color dialog box opens.

Figure 69 Background Color dialog box
Swatches tab
HSB tab
RGB tab
5 Select from the Swatch tab by clicking a color.
207569-F

• To adjust the selected color’s HSB, click the HSB tab, click on an area of
the palette, and make adjustments by editing the values in the associated
text boxes, or moving the slider bar.
• To adjust the selected color’s RGB tones, click the RGB tab, and adjust
the red, green, and blue slider bars as desired.
7 To save your changes and close the dialog box, click OK.
The graphical view Background Color for the folder changes.
Working with folders

This section describes how to work with folders and covers the following topics:
• “Opening a folder‚” next

• “Saving a folder” on page 278
• “Saving a folder as an image” on page 279
• “Selecting print setup options” on page 281
• “Printing a folder” on page 282
• “Saving Custom folders” on page 282
• “Opening a customized folder” on page 284
• “Creating an undo aged out objects folder” on page 284
• “Copying folders” on page 287
• “Copying objects between folders” on page 288
• “Exporting folder contents” on page 289
• “Deleting a folder” on page 290
• “Sharing custom folder queries with other InfoCenter users” on page 291
• “Exporting a folder definition to a file” on page 294
• “Importing a folder definition from a file” on page 294
• “Resetting a folder view to factory defaults” on page 295

Opening a folder
To open a folder:
1 In the folder pane, expand a parent folder by doing one of the following:
• Click the plus sign (+) next to a folder.
• Select a folder and use the RIGHT ARROW key to expand it.
2 Select a folder.
3 In the folder pane, right-click a folder and choose either Open > Graphical
View or Open > tabular View from the shortcut menu.
Figure 70 InfoCenter folder pane shortcut menu and submenu
The selected folder opens in the contents pane in the format you chose.
Saving a folder
InfoCenter lets you save the current, open folder to a default name and location.
207569-F
To save a current, open folder:
1 In the contents pane, click an open folder.

• Choose File > Save, or click Save to save the file to the default location.
The folder is saved under the current name to the default location. You are
not prompted to name the folder or choose a destination location.
• Choose File > Save As and choose the location in which to save the
folder.
The newly named folder is saved to the new location. The current folder
still exists under its original name and location.
Saving a folder as an image
InfoCenter lets you save a folder in the graphical view as an image in either JPG,
SVG, or PNG format, to a file name and location that you specify.
Note: The PNG file format option is not available on Windows NT or

Windows 98.
To save a current, open folder as an image:
1 In the contents pane, click an open folder.

2 In the graphical view, choose File > Save As Image.
The Save As Image dialog box opens.
3 To specify criteria for the saved image file, do the following:
a In the Type box, select the image file format.
b In the File Name box, specify the file name and location where to save the
file.
c Select an option for image content.

d Adjust the image quality.

e Select the image size.
4 Click OK.
The image file is saved to the new location.
When you use InfoCenter in a browser window and try to save a graph as image
using File > Save as image, sometimes the image will not save. When this
happens, you will see an “OutOfMemory” exception in the Java plugin console.
If you experience this problem, use one or both of the following procedures to
save the image:
• “Increasing the memory allocation using the Java Control Panel‚” next
• “Decreasing the size of the image being saved” on page 280
Increasing the memory allocation using the Java Control Panel

1 Start the Java ControlPanel executable from one of the following locations:
• For Windows: Start > settings > Control Panel > Java Plugin.
• For Solaris: [javapluginhome]/jre/bin
• For HP-UX: /opt/java1.4/jre/bin
2 Open the Advanced tab
3 In the Java Runtime Parameters text box, enter the following:
-Xms64m -Xmx256m
Decreasing the size of the image being saved

1 In InfoCenter, choose File > Save as image.
2 In the Size area of the Save as Image dialog box, mark the Custom radio
button
3 In the Width and Height text boxes, enter smaller values.
4 Click OK.
207569-F
Selecting print setup options
To set up a page for printing a folder:
1 Open the folder in the contents pane.

• Choose File > Page Setup
• In the graph format, in the Print Preview dialog box, click Page Setup.
The Print Setup dialog box opens.
3 Select the print setup parameters.
4 Click OK.
The print setup options are applied.
Previewing a page before printing
InfoCenter lets you preview a document before you print it. In this case, the folder
contents must be in the graphical format.
To preview a document before printing:

• Choose View > Format > Graph.
• On the toolbar panel, click Graph.
• Choose File > Print Preview.
• On the toolbar, click Print Preview.
The Print Preview dialog box opens.
4 Select the print parameters.
5 Click Print.
The folder is printed.

Printing a folder
To print a folder:

• Choose File > Print
• On the toolbar, click Print.
The Print dialog box opens.
3 Select the print parameters.
4 Click Print.
The folder is printed.
Saving Custom folders
You can customize and save the graphical layout for any folder. You can also
select the viewing options for each folder. See “Configuring presentation
properties for custom folders” on page 273 for more information.
Each Optivity NMS user can have their own custom graphical layouts for every
folder. The folder customizations are saved in the Optivity NMS database.
To create and save a customized folder in the graphical view format:

• Open an existing folder.
• Create a new folder. See “Creating a folder” on page 269.
2 To select the graphical view, do one of the following:
• From the menu bar, choose View > Format > Graphical.
• On the toolbar, click Graphical View.
3 To select a layer, do one of the following:
• From the menu bar, choose View > Layer, and select a layer.
• On the toolbar, click a layer tool.
207569-F
4 From the menu bar, choose Edit > Select All.

5 To expand by hops, do one of the following:
• From the menu bar, choose View > Expand by Hops.
• On the toolbar, click Expand by Hops.
The connection between network objects is displayed. For more information,
see “Using the expand by hops feature” on page 307.
6 To reposition them, drag the network object icons.
7 From the menu bar, choose File > Save As.
The Save As dialog box (Figure 71) opens.
Figure 71 Save As dialog box
8 Click a parent folder.

The name of the parent folder is displayed in the Save in: box.
9 In the Folder name box, type the name of the folder.
Each Optivity NMS user can have their own custom layouts for every folder.
The folder customizations are saved in the Optivity NMS database.
10 To save the folder and close the dialog box, do one of the following:
• To save the folder with the current contents, Click Save As Contents. New
devices are not added to the folder.

• To save the customized folder, click Save. If you renamed the folder, the
customized folder is saved under the new name to the new location. The
original folder is not changed.
Opening a customized folder
To open and view a customized folder:
1 In the tree view, expand the parent folder by doing one of the following:
• Click the (+) plus sign next to the parent folder.
• Click the parent folder and use the RIGHT ARROW key.
2 Double-click the customized folder.
The folder opens.
Creating an undo aged out objects folder
InfoCenter lets you create a folder for objects that you remove using the age out
feature. You can set up the folder to contain all objects you age out, or selected
objects that you age out. You can then use the folder to un-age out the objects
later. See “Removing an object with age out” on page 302 for more information.
To create an undo aged-out objects folder:
1 In the folder pane, select the Custom folder.

2 To create the folder, do one of the following:
• From the InfoCenter menu bar, choose File > New > Folder.
• On the toolbar, click New.
A folder (Figure 72) is created with the label “New Folder.”
207569-F
Figure 72 Folder pane with new folder
new folder
3 Double-click the new folder.

An empty folder view is displayed in the contents pane.
4 In the contents pane, do one of the following:
• From the InfoCenter menu bar, choose Edit > Properties.
• On the toolbar, click Properties.
The new Folder Properties dialog box (Figure 73) opens.
For detailed information about the Folder Properties dialog box, click Help in
the dialog box.

Figure 73 New Folder Properties dialog box
5 In the Scope area, do one of the following:

• To store all aged out objects in the folder, select All Types from the Folder
tree.
• To store only specific object types in the folder, select them from the
Folder tree.
6 In the Filter area, scroll to the Status attribute, and type 9 (Network object is
aged-out) in the text box.
See “Filter attributes” on page 262 for more information.
7 To refresh the folder contents, do one of the following:
• To save the changes to the database and remain in the dialog box, click
Apply.
• To refresh the folder contents, save the changes to the database, and exit
the dialog box, click OK.
All previously aged-out objects are displayed in the folder.
207569-F
Copying folders
You can copy folders in InfoCenter. For example, you can copy a router folder
into a folder that contains switches. Both folders maintain their folder definitions.
Note: Although you can copy any InfoCenter folder, you can only paste
folders into the Custom folder or its subfolders.
To copy a folder in the folder pane:
1 In the folder pane, select the folder you want to copy.

• From the menu bar, choose Edit > Copy.
• On the toolbar, click Copy.
• In the folder pane, right-click the highlighted folder and choose Copy
from the shortcut menu.
A copy of the highlighted folder’s contents are placed on the clipboard.
3 In the folder tree, select a destination folder in which to place the copy.
4 To paste the copy into the destination folder, do one of the following:
• From the menu bar, choose Edit > Paste.
• On the toolbar, click Paste.
• In the folder pane, right-click the selected folder, and choose Paste from
the shortcut menu.
The highlighted folder is copied to the destination folder.

Copying objects between folders
When you copy objects between folders in InfoCenter, the destination folder takes
on the properties of the objects copied into it. For example, if you copy a router
into a switch folder, the properties of the router are assigned to the switch folder.
Note: You cannot copy multiple objects using the shortcut menu. If you
select multiple objects, and right-click, all but one object is deselected.
Also, although you can copy any InfoCenter folder, you can only paste
folders into the Custom folder or its subfolders.
To copy objects between folders:
1 Open the source and destination folders.

2 In the source folder, do one of the following:
• Click a single object.
• [Ctrl] + click multiple objects.
3 From the InfoCenter menu bar, choose Edit > Select All or press [Ctrl]+A.
The object(s) are highlighted.
• From the InfoCenter menu bar, choose Edit > Copy.
• Right-click the highlighted object and choose Copy from the shortcut
menu (for copying single objects).
The highlighted object(s) are copied onto the clipboard.
5 Click the destination folder.
• From the InfoCenter menu bar, choose Edit > Paste.
• Press [Ctrl]+V.
The object(s) are pasted into the destination folder.
207569-F
Exporting folder contents
You can export the contents of a folder to a file on your client system. The output
file is saved in the same columnar format used in the InfoCenter folder.
To export the contents of a folder to a file:
1 From either the folder pane or contents pane, select the folder to export.
In the folder pane, use [Ctrl] + click to select multiple folders.
• From the InfoCenter menu bar, choose File > Export Folder Content.
• In the folder pane, right-click the highlighted folder(s), and from the
shortcut menu, choose Export Folder Content.
• Right-click an open folder view, and from the shortcut menu, choose
Export Folder Content.
The Export Folder Content file selection dialog box opens.
3 In the Export Folder Content file selection dialog box, browse for a
destination file name, or type in a new filename.
4 Click Save.
If you saved to a new file, the folder is saved to the named file in the same
columnar format used in the folder view.
5 If you saved to an existing file, InfoCenter confirms the override with the
following message.
Figure 74 Export Folder Content file override confirmation

• To save the folder to the named destination file, click Yes.
• To choose another file, click No, and repeat steps 3-6.

The file is exported to the destination directory on your client system.
Deleting a folder
You can delete folders or subfolders. If you remove a parent folder, all of the
subfolders under the parent folder are also removed.
To delete a folder:
1 Select a folder by doing one of the following:

• In the folder pane, select a folder.
• In the contents pane, in a parent folder view, select a subfolder.
2 Open the delete dialog box by doing one of the following:
• From the menu bar, choose Edit > Delete.
• In the folder pane, right-click the selected folder and choose Delete from
the shortcut menu.
• In the contents pane, right-click the selected subfolder, and choose Delete
The Delete dialog box (Figure 75) opens for you to confirm that you want to
delete the folder.
Figure 75 Delete dialog box

• To delete the folder, click Yes.
• To close the dialog box without deleting the folder, click No.
207569-F
Sharing custom folder queries with other InfoCenter users
You can share custom folder query definitions with other users either on the same
system or a remote system. Sharing folder query definitions is useful if a folder
query is not required globally by all users, but if multiple users can benefit from a
single customization.
When you declare a folder as shared, it is marked in your Custom folder with a
shared icon. The other Optivity NMS users with whom you share the folder see it
in their Shared folder. Only the owner of a shared folder can delete the folder or
change any if its properties.
Note: When you share a custom folder, other Optivity NMS users with
whom it is shared will only see folder contents that are within the IP
address ranges defined in their view domains.
The following sections describe how to share folder query definitions:
• “Sharing or unsharing a folder‚” next

• “Copying a shared folder” on page 293
Sharing or unsharing a folder
If you create a folder definition from which other InfoCenter users may benefit,
you can share the customizations with users who have IC_ADMIN read/write
access. You can also unshare folders that you have previously marked as shared.
When you mark a folder as shared, its icon changes to a Windows shared folder
icon.
Note: If you attempt to share a system or global folder, InfoCenter

displays an error message telling you that these folders cannot be shared.

To share or unshare a folder:
1 In InfoCenter, do one of the following:

• Right-click on a custom folder and choose Sharing
• Select a custom folder and choose File > Sharing from the menu bar.
Figure 76 Sharing shortcut menu command
The Folder Properties dialog box opens with the Sharing tab at the front.
207569-F
Figure 77 Folder properties dialog box, Sharing tab
2 Use the radio buttons to select whether to share the folder to all ONMS users
or just to selected users.
If you chose to share the folder to only selected users, choose users in the All
Users list and use the arrow buttons to move them to the Share to list.
3 Click Apply to apply the sharing settings without closing the dialog box, or
click OK to save the settings and close the dialog box.
The folder appears in the Shared folder of the selected Optivity NMS users.
Copying a shared folder
To copy a shared folder(s) into your custom folder:
1 In the folder pane, right-click the folder(s) you want to copy from the shared
folder and choose Copy from the shortcut menu.

2 Right-click the top-level folder under which you want the shared folder to be
copied and choose Paste from the shortcut menu.
The shared folder(s) appear in the folder you designated. If there is a naming
conflict, a -1 is appended to the folder name.
Note: If you select a system or global folder, the Paste option is not
available.
Exporting a folder definition to a file
To export a folder definition to a file:
1 Select a folder whose definition you want to export.

2 Choose File > Export Folder Definition.
The Export Folder Definition dialog box opens.
3 Locate and select the destination file.
You can choose an existing file or create a new file.
4 Click OK.
The file definition is exported to the specified destination.xml file.
Importing a folder definition from a file

To import a folder definition from a file:
1 Select a target folder into which you want to import the folder definition.
2 Choose File > Import folder definition from a file.
The Import Folder Content dialog box opens.
3 Locate the file whose definition you want to import.
4 Click OK.
The target folder is updated with the imported folder definition. If there is a
naming conflict, InfoCenter prompts whether you want to overwrite the
existing folder.
207569-F
Resetting a folder view to factory defaults
InfoCenter lets you reset the currently active folder to the factory default settings
for presentation and layout styles.
To reset a folder to the factory defaults:
1 Open the folder view you want to restore to factory defaults.

See “Opening a folder” on page 278 for more information.
2 Click on the folder to make it the active folder.
3 Choose View > Reset to Factory Defaults.
InfoCenter prompts you to confirm the operation.
4 Click OK to confirm.
InfoCenter restores the folder presentation and layout styles to their factory
default settings.
Working with objects

The following sections describe object attributes and how to manage the
InfoCenter objects that represent network resources:
• “Object attributes used in topology processes‚” next

• “Object attributes used in InfoCenter and Fault Summary processes” on
page 297
• “Viewing or modifying object properties” on page 298
• “Creating a new object” on page 299
• “Cutting an object from a view” on page 300
• “Pasting an object into a folder” on page 301
• “Recovering an object cut from a view” on page 301
• “Removing an object with age out” on page 302
• “Restoring an object removed with age out” on page 303
• “Permanently deleting an object” on page 304
• “Launching Optivity NMS applications from multiple objects” on page 305

• “Displaying traversal views” on page 305

• “Using the expand by hops feature” on page 307
• “Expanding by hops” on page 308
• “About remote selection” on page 309
• “Using remote selection between InfoCenter views” on page 309
• “Using remote selection between Optivity NMS applications” on page 310
• “Using Net Aware Select” on page 310
Object attributes used in topology processes
Table 54 describes the object attributes used in topology processes. You can enter
or modify some of these attributes.
Table 54 Attributes used by topology processes
Attribute Value Parameters
Attachment1 Integer Encoded link object property for end node

topology. The format is 2ssppp, where:
• 2—connectivity port.
• ss—slot where the board resides.
• ppp—port number.
BelongFlatnetUnknown Integer This property is used by function. Normal value is
–1 or 1. If it is set to 1, that means that object is
not belong to any subnet.
Change_Count Integer This property is not used. The normal value is –1.
Priority Integer Set by the system. Do not change the value.
_bridge_number Integer Bridge number.
_interface_num Integer Interface number. The topology process gets this
number from ifTable of the device.
_interface_type Integer Interface type. The topology process gets this
number from ifTable of the device. The range is 1
to 69.
_vlan_type Integer Type of switch that configured the VLAN. The
range is 4 to 13.
_time_stamp long UNIX time stamp used by topology function for
age out. The default value is -1.
SegmentName string[128] Name of the segment that the object belongs to.
207569-F
Table 54 Attributes used by topology processes (continued)
Attribute Value Parameters
_sysObjectId string[128] Object ID provided by the device. The topology

process uses this string to identify the device.
IP_Address string[16] Address of the device interface.
Object attributes used in InfoCenter and Fault Summary

processes
Table 55 describes the object attributes used by InfoCenter and Fault Summary.
You can enter or modify these attributes.
Table 55 Attributes used in InfoCenter and Fault Summary processes
Paramet
Attribute er Description
Status Integer Object origination and status
Value Description
0 Autotopology discovered the network object. This is the only

value you can force the status to by editing the value in the
Object Properties dialog box.
1 An Optivity NMS user created or added the network object to
the Optivity NMS database.
2 An Optivity NMS user removed the network object with age
out.
MonLevel Monitor level.
fcStateConfSeverity Integer Fault management Configuration status.
fcStateLoadSeverity Integer Fault management Load status.
fcStateErrSeverity Integer Fault management Error Rate status.
_time_stamp Integer Time stamp used by topology function for age out. The default value is
-1.
fcStateSecSeverity Integer Fault management security status.
fcStateConnSeverity Integer Fault management connectivity status.
fcStateCompSeverity Integer Fault management component status.

Table 55 Attributes used in InfoCenter and Fault Summary processes (continued)
Paramet
Attribute er Description
fcStateChange Integer Fault management state change status.

Discovery_Status Integer Status of the discovery process. The range is 1 to 6. The value is used
by the topology process.
Viewing or modifying object properties
To view or modify object properties:
1 In any InfoCenter folder view, select a network object and do one of the
following to open the Object Properties dialog box:
• Choose Edit > Properties
The Object Properties dialog box opens, displaying the properties for the
selected network object.
For detailed information about the Object Properties dialog box, click Help on
the dialog box.
2 (Optional) In the dialog box, edit the object attribute you want to modify.
For more information about object attributes, see “Object attributes used in
topology processes” on page 296.
3 To close the dialog box, click OK.
Note: If you manually set the Label of any object, then that label will be
used to display the object instead of the label set in the database.
Viewing object details
You can view the details discovered about an object at the interface level,
including any logical entities, agents, and slot/port assignments. You can resize
the Device Detail View window split partitions.
207569-F
To view object details:
From an open folder in the contents pane, right-click an object and choose
Device View from the shortcut menu.
The Device Detail View window (Figure 78) opens.
Figure 78 Device Detail View for a router
You can also use the Device Detail View window to unmanage and manage the
interfaces of a device. See “Unmanaging and managing interfaces” on page 328
Creating a new object

You can add a network object to the database when Autotopology does not
discover it because a default object for it does not exist in the Optivity NMS
database.
InfoCenter lets you create a new object from object criteria in the Optivity NMS
database.
To create a new object:
1 From the menu bar, choose File > New > Object.
A new Object Properties dialog box opens.
2 In the Name text box, type the object’s name.

3 In the Type text box, select the object type.

InfoCenter assigns the device type in the Device box.
4 In the Subnet text box, type the name of the subnet to which the network
object is assigned.
5 In the Object Attribute/Value Entry table, enter each required value.
For more information about object attributes, see “Object attributes used in
topology processes” on page 296.
6 Click OK.
Cutting an object from a view
InfoCenter lets you cut object(s) from a view. Cutting an object from a folder view
modifies the folder’s properties. The last object cut remains on the clipboard.
To cut a managed object from a view:
1 In a folder view, select an object and do one of the following:

• From the InfoCenter menu bar, choose Edit > Cut.
• On the toolbar, click Cut.
• In the folder view, right-click an object and choose Cut from the shortcut
menu.
The object is cut from the view and moved to the clipboard.
2 To save your changes, do one of the following:
• From the InfoCenter menu bar, choose File > Save.
• Close the folder view and click Yes to confirm the cut.
The folder is saved. The folder definition is modified to exclude (filter out) the
object from future views. The folder's modified date and time are updated to
reflect the latest change to the folder properties.
207569-F
Pasting an object into a folder
InfoCenter lets you paste the last object you cut from a view back into the same
view or into another view.
Note: The destination folder must be open in the contents pane before
you can paste an object into it. See “Opening a folder” on page 278.
To paste an object cut from one folder view into another folder:
1 In the contents pane, open the destination folder and do one of the following:
• From the InfoCenter menu bar, choose Edit > Paste.
The object is pasted into the destination folder view and remains on the
clipboard.
2 To save the folder, do one of the following:
• From the InfoCenter menu bar, choose File > Save.
• Close the view and click Yes to confirm you want to save your changes.
The folder is saved. The folder definition is modified to include the object.
The folder’s modified date and time are updated to reflect the latest change to
the folder properties.
Recovering an object cut from a view
InfoCenter lets you recover an object that you cut from a view. The last object cut
from a view is placed on the clipboard. InfoCenter lets you paste the object from
the clipboard into the current view.
To recover an object cut from view that is not on the clipboard:
1 To open the folder, do one of the following:

• In the folder pane, select the folder from which the object was cut.
• In the folder pane, open the folder from which the object is cut.
• In the contents pane, select the folder from which the object is cut.

2 To open the Folder Properties dialog box do one of the following:

• Right-click the folder and choose Properties.
The Folder Properties dialog box opens with the filter attributes displayed in
the Filter group.
For detailed information about the Folder Properties dialog box, click Help on
the dialog box.
3 Click the filter attribute “&&exclude Name == object_name” for the object
you want to recover.
4 Click Delete.
5 Click OK.
The object is placed back into the current view.
Removing an object with age out
The age out feature changes the Status property of the selected object to 2. This
action marks the object as removed from the Optivity NMS database, and changes
the color of the object to the system’s background color. If a subsequent topology
discovery cycle does not encounter the object after the age out interval, it is then
permanently removed from the topology database. Its agent and associated
interfaces are also removed.
Note: The feature called Age Out in Optivity NMS 10.2 was called
Delete in previous Optivity NMS releases. This feature has been renamed
Age Out in version 10.2 so that the term Delete could be applied to a new
delete feature. This new delete feature lets you immediately delete an
object from the Optivity NMS database without waiting for the next
topology discovery cycle. See “Permanently deleting an object” on
You can also restore an object deleted with the age out feature. For more
information about undeleting aged-out objects, see “Restoring an object removed
with age out” on page 303.
207569-F
To delete an object using age out:
1 Select an object in a folder view and choose Edit > Age Out.
The Age out confirmation dialog box opens.
2 Click Yes.
Restoring an object removed with age out
InfoCenter lets you restore objects that you have removed using the age out
feature. When you restore such an object, it is returned to its original parent folder
if the parent folder’s definition has not changed.
To restore an object from an Undo folder:
1 Open the Deleted Items folder. See “Creating an undo aged out objects folder”
2 Select the object you want to restore.
3 Do one of the following to open the Object Properties dialog box:
• In the folder view, right-click the selected object and choose Properties
The Object Properties dialog box opens. The Status box entry is 2.
For detailed information about the Object Properties dialog box, click Help on
the dialog box.
4 In the Values box, enter 0 in the Value box.
• If the object was created by an Optivity NMS user who created or added it
to the Optivity NMS database, enter 1 in the Value box.
5 Click OK.

Permanently deleting an object
InfoCenter lets you delete objects permanently and immediately from the
topology database and from all folders and views. Unlike objects deleted using the
age out feature, permanently deleted objects cannot be restored. See “Removing
an object with age out” on page 302 for more information.
Note: You cannot delete an object when Autotopology discovery

processes are in progress or when the object is part of a multicast baseline
other than a rolling baseline
Table 56 describe the additional objects that are removed when you permanently
delete an object:
Table 56 Additional objects removed during a permanent delete
When you delete... It also removes...
Physical device • The device agent

• All interfaces for the agent
• All logical and physical links
• All local VLANs
• All connected end node links
• All associated VPN tunnels
End node • All related end node links
Physical link • All associated MLTs and SMLTs
• All associated flatnet links
To delete an object:
1 Select an object in a folder view and do one of the following:

• From the menu bar, choose Edit > Delete.
• Right-click the object and choose Delete from the shortcut menu
An alert box opens. If the alert box warns that the object is part of a baseline,
use it to view a list of the baselines that include the object. You can use that
information to delete the baselines so that you can delete the object.
2 Click Yes.
207569-F
Optivity NMS permanently removes the object and all related objects.
Launching Optivity NMS applications from multiple objects
If you select multiple objects in a folder view, you can launch those applications
that are available to both objects.
An Optivity NMS application’s registry entry indicates whether the application

supports multiple selections. If so, and you select multiple objects in a folder view,
a single instance of the program is launched for all selections. If multiple
selections are not supported, then a separate instance of the application is
launched for each selected network object.
When an Optivity NMS application starts, information about the object and the
object subtypes that it supports is sent to the application. The information defines
the context in which the application runs. The context can include the folder and
folder definition for an object, as well as any number of static folder properties.
Displaying traversal views
You can traverse network objects and display the traversal view as a temporary
folder. When you double-click a network object, depending on the type of object
selected and whether traversal objects are discovered, InfoCenter opens a
transformed view of it in a new view. You can perform any typical operation
(further transformation, expanding by hops, starting another application, etc.) in
the new view.
Table 57 describes the traversal views you can display.
Table 57 Traversal views
Object Displays
Subnet Data link layer of the subnet.

Switch community Switch community view.
Physical device (hub, End node view of the physical device.
switch, router)
VLAN VLAN view.
Segment Physical view of the segment.

Table 57 Traversal views (continued)
Object Displays
WAN trunk WAN trunk view of the device.

OSPF Domain The discovered OSPF Area, ABR/ASBR routers, ABR/ASBR
links for the OSPF domain.
RIP 2 Domain RIP2 protocol routers for the RIP2 domain.
OSPF Area Routers, router links, boundary router for the OSPF area.
Multicast Session Object The discovered routers, subnets, and router links for the
multicast session.
To traverse a network object and display any discovered objects in a temporary

folder:
Do one of the following.
• From an open folder view, double-click an object.

• Right-click an object and select Open from the shortcut menu.
A temporary folder opens displaying the discovered objects. You can further
transform the new folder or launch other applications from it. If no objects are
discovered for the new view, InfoCenter opens an error window (Figure 81):
Figure 79 Error—No objects in traversal view
When you traverse an object that contains some elements that are outside your
view domains, the temporary folder view shows a red dot in upper left corner of
the window.
207569-F
Figure 80 Red dot indicating incomplete traversal view
Red dot
Using the expand by hops feature

The expand by hops feature lets you expand a folder view to see the links and
objects directly connected to a specific object at a specific layer. When you
expand an object by hops, InfoCenter automatically updates its folder view with
all links and objects one hop away.
A hop is an intermediate connection in a string of connections linking two

network devices. On the Internet, for example, most data packets go through
several routers before they reach their final destination. Each time the packet is
forwarded to the next router, a hop occurs. The more hops, the longer it takes for
data to go from source to destination. Ping or Path Trace utilities tell you how
many hops it takes to get from point A to point B.
Table 58 describes how the expand by hops feature operates for a router:
Table 58 Expand by hops layers
Expanding this layer... Shows...
At the Internet layer Shows all the subnets that the object routes to.
At the physical layer Shows all the physical devices (hubs, switches) the
router is connected to.
At the switch community layer Shows all VLANs that the object routes to.
At the WAN trunk layer Shows all objects that WAN trunk devices route to.
At the database layer Expand by hops does not work at this layer.

The links and objects are displayed in the current folder view, but are not stored in
the folder definition. The next time you open the folder, the objects don’t display.
This feature works at every layer except the database layer. For more information
about view layers, see “Folder view layers” on page 193.
You can also use the expand by hops feature to expand a set of selected nodes. If
you select a subnet icon and choose expand by hops, all additional routers that are
one hop away are displayed.
Expanding by hops
The following is an example of how to use expand by hops.
To expand a router by hops:
1 Open the Routers resource folder.

2 If the folder view is at the database layer, choose another layer from the
toolbar. For more information, see “Changing the current view layer” on
page 209.
3 In the folder view, select a router.
4 To expand the view by hops, do one of the following:
• From the menu bar, choose View > Expand by Hops.
• On the toolbar, click Expand by Hops.
• Right-click the device, and choose Expand by Hops from the shortcut
menu.
All subnets one hop away from the selected router are added to the folder
view.
207569-F
About remote selection
You can use Remote Selection to select a device in one view and display it in
another view, for example:
• Selecting a device in one folder viewing it in a different format in another

folder view. The display format can be different.
• Selecting a device in one folder viewing it in the same format in another
folder view.
• Selecting a device in InfoCenter and showing it in another Optivity NMS
application.
• Showing a selected device in different instances of InfoCenter.
Table 59 summarizes how remote selection works between Optivity NMS

applications.
Table 59 Remote selection between Optivity NMS applications
Optivity NMS
Application Description
OmniView InfoCenter highlights objects selected in OmniView and vice versa.

Call View InfoCenter highlights database objects corresponding to the ATM
objects selected in Call View. This includes selection of network objects
like LEC, LES, LECS, and BUS as well as links and the corresponding
objects, for example switches and ELANS selected in InfoCenter.
Fault Summary InfoCenter highlights the network objects in Fault Summary.
Expanded View InfoCenter highlights a link and device when a port on a device is
selected in Expanded View.
For more information about using Remote Selection with various platforms or
browsers, see “Troubleshooting InfoCenter” on page 315.
Using remote selection between InfoCenter views
You can select a device in one folder view and display it in another folder view.
The display format can be different.

To use remote selection between InfoCenter views:
1 From the InfoCenter menu bar, choose Options > Remote Selection.
2 Open two folders.
3 Select a device in the current folder view.
If in view, the device is highlighted in the second view.
Using remote selection between Optivity NMS applications

You can select a device in InfoCenter and show the device in another Optivity
NMS application.
To use remote selection between Optivity NMS applications:
1 From the InfoCenter menu bar, choose Options > Remote Selection.
2 From the other Optivity NMS application, choose Remote Selection.
• In the InfoCenter folder view, select a network object.
• In the other Optivity NMS application, select a network object.
The selected network object is highlighted in the other application.
Using Net Aware Select

Net Aware Select feature selects all the children and parents of an object in all
open views.
For example, if you select a switch and use net aware select, it highlights the
subnet to which the switch belongs.
To use Net Aware Select:
1 Open views for all folders of interest to the operation.

2 Right-click an object and choose Net Aware Select
3 View the children and parent objects in the other views.
207569-F
Working with InfoCenter search functions

You can use InfoCenter search functions to locate information in the Optivity
NMS database, or to find an object in a folder view. This section includes the
following topics:
• “Finding an object in a folder view‚” next

• “Finding an object in the Optivity NMS database” on page 312
Finding an object in a folder view
InfoCenter lets you enter a search string to locate a managed object in a folder
view. You can search for objects by IP address, label, or name.
To find an object in the current folder view:
1 Open the Find dialog box by doing one of the following:

• From the menu bar, choose Edit > Find.
• On the toolbar, click Find.
The Find dialog box (Figure 81) opens.
Figure 81 Find dialog box
For detailed information about the Find dialog box, click Help on the dialog
box.
2 Type the search string (IP address, label, or name of the object).
3 Click Find Next.
InfoCenter locates the object and highlights it in the folder view.

Finding an object in the Optivity NMS database
InfoCenter lets you enter a search string to locate a managed object in the Optivity
NMS database. If the object is located, InfoCenter creates a new folder and
displays the search results in the new folder (labeled temporary).
You can search for objects by IP address, label, or name.
To find an object:
1 From the InfoCenter menu bar, choose File > New > Find Object View.
The Find Object dialog box (Figure 82) opens.
Figure 82 Find Object dialog box
2 Type a search string containing the IP address, label, or object name.

3 Click OK.
InfoCenter locates the object and opens a temporary folder in the contents
pane containing the object.
Visualizing MLT and SMLT configurations

Optivity NMS shows you MLT and SMLT configuration details when you view
networks that include these features.
To view SMLT and MLT features:
1 From the InfoCenter resource tree, open the Subnet folder.

2 From the Subnet folder, open a subnet that contains an MLT or SMLT
configuration.
207569-F
MLT and SMLT configurations and their labels are displayed as shown in
Figure 83.
Figure 83 SMLT configuration (data link layer)
To view the physical links of the SMLT or MLT configuration:
On the InfoCenter toolbar, click Physical to transform the subnet view to the
physical layer.

With the subnet folder transformed to the physical layer, the physical links of
the MLT and SMLT configurations and their labels are displayed as shown in
Figure 84.
Figure 84 SMLT configuration, subnet transformed to physical layer
You can also use OmniView to view statistics for MLT and SMLT links by
right-clicking a link and choosing Performance > OmniView from the shortcut
menu. For more information about OmniView, see Chapter 13, “Monitoring
devices with OmniView and MView,” on page 393.
207569-F
Troubleshooting InfoCenter
Table 60 describes InfoCenter problems and solutions.
Table 60 InfoCenter common problems and solutions
Problem Solution
Folder view is empty. Make sure that there is at least one view domain in your
database view. See “Adding and removing view domains” on
If you are viewing protocols, make sure you have enabled
discovery of the specific protocol. You must enable discovery
of Multicast, Unicast, and Frame Relay protocols in the
Discovery Options dialog in order to view these objects. For
more information, see Chapter 4, “Discovering your network
with AutoTopology Manager,” on page 137.
Aged out an object by mistake. Restore the object. See “Restoring an object removed with
age out” on page 303 for more information.
After you use the Database Administration To correct this problem, restart InfoCenter.
Tool to delete a database, InfoCenter On the UNIX platform, it is possible to delete or reinitialize a
displays the same information as before. database using the Database Administration Tool without first
stopping all other Optivity NMS processes. When you do this,
InfoCenter or any other Optivity NMS processes, do not
immediately reflect the deleted or reinitialized databases.
Optivity NMS processes continue to show old data for a period
of time and may crash.
The correct procedure (on both the UNIX and Windows
platforms) is to stop all other UNIX processes before you
delete or reinitialize any database. See Installing and
Administering Optivity NMS 10.3 for more information about
stopping and starting services and daemons.

207569-F
317
Chapter 7
Monitoring network health with InfoCenter
This chapter describes how to use InfoCenter to monitor fault conditions in your
network. It contains the following topics:
• “Overview‚” next
• “Selecting fault management categories for alarm monitoring” on page 318
• “About the Alarms folder” on page 319
• “Color coding alarm status” on page 320
• “Enabling status color propagation” on page 324
• “Calculating fault status” on page 325
Overview
The InfoCenter fault management feature lets you visually monitor the health of
your network devices. A device’s health is determined by the alarm level assigned
to the fault categories that are listed in Table 61.
Table 61 Fault category definitions
Fault category Description
Connectivity The physical or logical connection between devices.

Error rates The device’s error rate.
Components The state of one or more of the device’s physical components.
Load The traffic load being experienced by the device.
Security The security of the device.
Configuration The configuration of the network to which the device is
connected.

318 Chapter 7 Monitoring network health with InfoCenter
The color and location of a network object in one of the Alarms folders (Caution,
Critical, or Warning) indicates the status of the device’s overall health.
Selecting fault management categories for alarm

monitoring
You can select the categories for which InfoCenter will display health status
information about your network. By default, all of the fault management
categories are selected.
To choose the fault management categories you want to monitor:
dialog box.
2 Click the Alarm tab to bring it to the front (Figure 85).
207569-F
Chapter 7 Monitoring network health with InfoCenter 319
Figure 85 InfoCenter Preferences dialog box Alarm tab
3 Use the check boxes in the Categories area to enable or disable individual
fault management categories.
4 Click OK.
About the Alarms folder

The Alarms folder contains three subfolders:
• Critical
• Warning
• Caution
Whenever a network device experiences a fault condition, the device is identified

in one of the Alarms folders.

Alarms folders are color-coded. Each alarm level color is the same as the color
coding used to indicate the health status of a device. You can change the color.
Color coding alarm status

In the InfoCenter graphical views, icons representing network objects are
color-coded to reflect the current status of the object. In the tabular view, table
rows are color-coded to reflect the current status of the device.
Status information propagates up through the folder hierarchy, from subfolders to

the parent folder. The parent folder takes on the color of the object or subfolder
currently experiencing the highest severity level. Other folders containing devices
experiencing fault conditions take on the status or color of the network object with
the highest severity level. Network entities that represent containment or
aggregation relationships (for example, a segment) are color-coded the same as
folders.
The following sections describe alarm colors and how to select them:
• “Alarm colors‚” next

• “Selecting a color for an alarm level” on page 321
Alarm colors
Table 62 describes the alarm states and their color codes as established at the time
you installed Optivity NMS. You can change these settings.
Table 62 InfoCenter alarm states and color coding
Alarm state Default color Description
Critical Red The device is in a critical condition because it has failed

or is at risk of failing. You must take corrective action.
Warning Orange The device has experienced a nonfatal error or
condition. The situation is not critical, but you should
closely monitor it and investigate what caused the fault.
Caution Yellow The device has a low-severity problem. You should
monitor or investigate the problem.
207569-F
Table 62 InfoCenter alarm states and color coding
Alarm state Default color Description
Operational Green The device is functioning properly according to the fault

management criteria. There are no evident problems
with the device. The device is fully operational.
Unmanaged Blue The health status is unknown because the device is
unmanaged.
Selecting a color for an alarm level
The Alarm Level Color option lets you select a color for each alarm level. This
setting is applied to all Display windows. For example, red is the default setting
for critical alarms. Whenever there is a critical alarm anywhere in your network,
the following InfoCenter elements are displayed in red:
• The top level Alarms folder in the folder pane

• The Critical Alarms folder in the folder pane
• The contents of the Alarms Display window in the contents pane
• The object in the critical state in its device folder view
To select the color for an alarm level:
dialog box.
2 Click the Alarm tab to bring it to the front (Figure 85).
3 In the Levels area, click the alarm color you want to change.
The Alarm Color dialog box opens.
• Go to step 5 to use the HSB model to select the color.
• Click the RGB tab, and go to step 7 to use the RGB model to select the
color.
5 In the Alarm Color dialog box HSB tab (Figure 86), do the following:

a Click the color wheel to select the hue (color).

b Click the saturation/value selector to select the saturation and brightness
of the color.
c See the final color in the Color pad.
Figure 86 Alarm color dialog box HSB tab
207569-F
6 Click OK.
The selected Alarm color is changed.
7 In the Alarm Color dialog box RGB tab (Figure 87), drag the red, green, and
blue intensity sliders to achieve the desired color.
The Color pad displays the resulting color.
Figure 87 Alarm color dialog box RGB tab
8 Click OK.
Alarms display in the new color, if you have propagated the alarm status to the
Alarms folder.

Enabling status color propagation

InfoCenter lets you propagate the health status information for your custom
folders so that fault status color coding shows up in the folders. The default for a
new folder is not to propagate status information. If you want fault status color
coding to show up in a network resource folder, you must make a setting in the
folder’s properties.
Note: Fault status color propagation is only supported for Custom folders
and subfolders. It is not supported for any of the pre-defined InfoCenter
folders.
To propagate the health status of a custom folder:
1 Select a Custom folder from the Folder tree or the Contents pane.
2 Choose Edit > Properties.
The Folder Properties dialog box opens with the General tab displayed.
For detailed information about the Folder Properties dialog box, click Help in
the dialog box.
3 Click the Presentation tab to bring it to the front (Figure 88).
Figure 88 Folder properties dialog box Presentation tab
207569-F
4 Click Status Propagation.

5 Click OK to save your changes and close the dialog box.
Status now propagates from the network object to its parent folders and the
Alarms folders.
Calculating fault status

Optivity NMS calculates the values in a set of fault categories before showing an
alarm by changing the color of an icon in InfoCenter. These categories
(Connectivity, Errors, Components, Load, Security, and Configuration) can each
have a value of 0–10, where 0 means fully functional, and 10 means not
functional.
The following sections describe the elements of fault status calculation:
• “Fault status criteria‚” next

• “Fault correlator status calculation methods” on page 326
• “Choosing the fault management calculation method” on page 327
• “Unmanaging devices” on page 327
Fault status criteria
Fault status is calculated differently depending on whether the object is a device or

a component. For devices, the fault status is calculated according to the criteria
shown in Table 63. For components such as ports or slots, the default color is
based on half of the reported severity.
Table 63 InfoCenter fault status criteria
Severity Alarm Default color Label
10 0 Red Critical
9 0 Red Critical
8 0 Red Critical
7 0 Red Critical
6 1 Orange Warning

Table 63 InfoCenter fault status criteria (continued)
Severity Alarm Default color Label
5 1 Orange Warning
4 1 Orange Warning
3 2 Yellow Caution
2 2 Yellow Caution
1 2 Yellow Caution
0 3 Green Operational
NA Unmanaged Blue Unmanaged
After receiving an event, the Fault Correlator checks its state rules to change the
current state of the network object. Events include traps from devices and other
applications. Every event may have a state rule associated with it.
The severity of the problem is reflected in the severity level of the state rule. For
example, because a power supply failure is a critical problem it has a higher
severity level than that of the network management module saturation.
Fault correlator status calculation methods
The Fault Correlator uses one of the calculation methods described in Table 64 to
determine which color to use for an icon. You can choose either of these methods
to calculate alarm status. See “Choosing the fault management calculation
method‚” next for more information in setting the calculation method.
Table 64 Alarm status calculation methods
Method Description
Max The Max calculation method finds the maximum current value of the
fault category states when calculating alarm status value.
Mean The Mean calculation method finds the average value out of the six
fault categories. The Mean takes the sum of all the values and divides
the sum by the number of values. The quotient is compared to the value
and the corresponding alarm level determines the color of the alarm
folder.
207569-F
Choosing the fault management calculation method
You can select the Max (default) or Mean fault management calculation method in
the Set Preferences dialog box.
To set the calculation method:
dialog box.
2 Click the Alarm tab to bring it to the front (Figure 85 on page 319).
3 In the Calculation method area, click one of the following:
• Max to display the highest severity of any state
• Mean to display the average of all states
4 Click OK.
Unmanaging devices
In Optivity NMS 10.3, you can declare physical devices as unmanaged. When you
declare a device as unmanaged:
• Optivity NMS deregisters the Optivity NMS server from the device trap
receivers table.
• Optivity NMS deregisters the Optivity NMS server from the device syslog
receivers table.
• Optivity NMS does not perform Autotopology or protocol discovery on the
device.
• Optivity NMS disables the superping service or daemon from sending ping
requests to the device.
• All device interfaces are marked as unmanaged.
• All of the current faults for the device are changed to unmonitored status in
Fault Summary.
• The device status color switches to the selected color for an unmanaged
device (the default is blue).

To declare a device as Managed or Unmanaged:
Right-click the device and choose Manage or Unmanage from the shortcut
menu.
When you declare an unmanaged device as managed, Optivity NMS does the
following:
• Registers the Optivity NMS server in the device trap receivers table
• Marks all device interfaces as managed.
• Switches the device icon or table entry briefly to green, and then to the color
corresponding to the device health status for the selected color of an
unmanaged device.
• Enables the superping service or daemon to send ping requests to the device.
See Chapter 15, “Specifying the level of statistics gathering with Monitor
Options,” on page 541 for more information about levels of device management.
Unmanaging and managing interfaces
In addition to letting you unmanage and manage devices, Optivity NMS also lets
you unmanage and manage individual interfaces. Unmanaging an interface
disables Superping for the interface.
To unmanage or manage an interface:
1 In InfoCenter, open the folder containing the device with the interface you
want to unmanage or manage.
2 Right-click on the device and choose Device View.
The Device Detail View window opens. See “Viewing object details” on
page 298 for more information about the Device Detail View window.
3 On the Device Detail View window, expand an agent by clicking on its plus
sign (+).
The window shows the interfaces for the agent.
4 Right-click on an interface, and choose either Manage or Unmanange.
207569-F
329
Chapter 8
Managing multicast sessions and protocols with
Optivity NMS
This chapter describes how to manage multicast sessions and baselines with
Optivity NMS.
Note: You can only manage multicast sessions and protocols if you are
assigned the multicast service. Optivity NMS administrators assign
services using Access Control Administration. If you are not assigned the
multicast service, InfoCenter will not show the folders and toolbar
buttons you use to manage multicast elements.
See “Viewing available services” on page 249 to check your services. See
Chapter 2, “Specifying access to Optivity NMS applications with Access
Control Administration,” on page 75 for information on assigning
services.
InfoCenter lets you selectively rediscover multicast sessions that were found
during the initial discovery of the managed network.
Optivity NMS lets you save and compare two kinds of multicast baselines:
• Session baselines - Each session baseline contains a snapshot of a multicast

session. The baseline is a list of the routers, links, and subnets participating in
the session.
• View Baselines - A view baseline captures an entire InfoCenter folder view.
There are two types of View baselines:
— Routing View baselines - Captures a baseline of the InfoCenter Multicast/
Routing folder.

330 Chapter 8 Managing multicast sessions and protocols with Optivity NMS
— Session View baselines - Captures a baseline of the InfoCenter Multicast/

Sessions folder, and also captures baselines for each of the sessions in the
folder.
• “Discovering multicast elements‚” next

• “Understanding active and inactive baselines” on page 335
• “Working with multicast sessions and session baselines” on page 335
• “Working with multicast view baselines” on page 347
• “Exporting and importing baseline data” on page 352
Discovering multicast elements

The Optivity NMS autotopology applications discover multicast sessions and
routing configurations when the Multicast Discovery check boxes are marked on
the AutoTopology Manager Options dialog box. For more information on
discovering network devices and protocols, see Chapter 4, “Discovering your
network with AutoTopology Manager,” on page 137.
You can compare either session or view baselines with the most current discovery
of the network.
Manually rediscovering multicast sessions
You can select a single multicast session or multiple multicast sessions for manual
rediscovery. In this case, you must initiate each subsequent rediscovery process.
The Configuration > Rediscover command triggers a multicast discovery process
(protmr), to collect multicast routing information from all routers and layer-3
switches in the managed network. After data collection, protmr processes only the
data related to the selected session(s), and updates the database for any changes
found in the session(s).
The following sections describe how to manually rediscover single and multiple
multicast sessions:
• “Manually rediscovering a single session‚” next
207569-F
Chapter 8 Managing multicast sessions and protocols with Optivity NMS 331
• “Manually rediscovering multiple sessions” on page 332
You can compare a multicast baseline with:
• The current network

• Another baseline
For more information about saving and comparing baselines, see “Saving
multicast session baselines” on page 336 and “Comparing multicast session
baselines” on page 342.
Manually rediscovering a single session
To rediscover a single session:
1 In the InfoCenter folder tree, open the Resources/Multicast/Sessions folder.

2 In the Resources/Multicast/Sessions folder view, right-click on a session and
choose Configuration > Rediscover (Figure 89).
Figure 89 Manually rediscovering a single multicast session
A rediscovery is started against the selected session.

Manually rediscovering multiple sessions
To rediscover multiple sessions:

2 In the Resources/Multicast/Sessions folder view, use Ctrl+click or Shift+click
to select multiple multicast sessions.
3 On the InfoCenter menu bar, choose Tools > Configuration > Rediscover
(Figure 90).
Figure 90 Selecting multiple multicast sessions for rediscovery
Note: When selecting multiple sessions for rediscovery, you cannot use
the object shortcut menu. Right-clicking a session to open the menu
deselects the previously-selected sessions.
Rediscovery is started against the selected sessions.
Selecting sessions for auto-rediscovery
You can specify multicast sessions for auto-rediscovery by the Autotopology

applications. The following sections describe how to select sessions for
auto-rediscovery:
207569-F
• “Selecting or deselecting a single multicast session for auto-rediscovery‚”

next
• “Selecting or deselecting multiple multicast sessions for auto rediscovery” on
page 334
For information on scheduling auto rediscovery, see Chapter 4, “Discovering your

Selecting or deselecting a single multicast session for

auto-rediscovery
To select or deselect a single multicast session for auto-rediscovery, you add it to

or remove it from the watch list:
1 If you haven’t already done so, open the Resources/Multicast/Sessions folder.

2 Right-click a multicast session object.
3 From the Object shortcut menu, choose Configuration > Add to Watch list to
select the session for rediscovery, or choose Configuration > Remove from
Watch list to deselect it.
Figure 91 Adding a multicast session to the watch list (removing similar)

The entry in the isWatched column in the multicast folder view (Figure 92) is
changed to 1 to indicate that auto-rediscovery is selected for that multicast
session object, or to 0 to indicate that auto-rediscovery is deselected.
Figure 92 Auto-rediscovery indicated by isWatched column
isWatched = 1
means sessions
are on watch list
for rediscovery
Selecting or deselecting multiple multicast sessions for auto

rediscovery
To select or deselect multiple multicast sessions for auto rediscovery:

2 In the Resources/Multicast/Sessions folder view, use Ctrl+click or Shift+click
to select multiple multicast sessions.
3 On the InfoCenter menu bar, choose Tools > Configuration > Add to watch
list (Figure 93) to select the sessions for rediscovery, or choose Tools >
Configuration > Remove from Watch list to deselect them.
Note: When selecting multiple sessions for auto rediscovery, you cannot
use the object shortcut menu. Right-clicking a session to open the menu
207569-F
Figure 93 Selecting multiple multicast sessions for auto rediscovery
The entries in the isWatched column in the multicast folder view (Figure 92)
are changed to 1 to indicate that auto-rediscovery is selected for those
multicast sessions, or to 0 to indicate that auto-rediscovery is deselected.
Working with multicast sessions and session baselines

The following sections describe how to save and view multicast session baselines,
and how to compare sessions with their baselines:
• “Understanding active and inactive baselines‚” next

• “Saving multicast session baselines” on page 336
• “Deleting session baselines” on page 338
• “Viewing session baselines” on page 339
• “Listing the baselines for a multicast session” on page 340
• “Designating baselines as active or inactive” on page 341
• “Comparing multicast session baselines” on page 342
Understanding active and inactive baselines

You can save multiple baselines for each multicast session. However, for each
session there can only be one active baseline. The active baseline is the one that is
compared with the session by default.

In the InfoCenter Baselines/Multicast Sessions folder, active baselines are

identified by a red circle around the icon in the leftmost column of the folder view.
Inactive baselines are identified by icons without red circles.
Table 65 describes the icons you encounter while working with multicast sessions
and baselines.
Table 65 Icons for multicast sessions and baselines
Icon (2x
Folder magnification) Description
Baselines/ Multicast Active baseline

Sessions
Inactive baseline
Resources/ Multicast/ Session for which at least

Sessions one baseline exists
Session for which no

baselines exist
Saving multicast session baselines
You can save a view of a multicast session as a baseline in the database. You can
compare the results of a later discovery against the baseline to identify any
changes that occurred in the network. You can also compare baselines with each
other.
Note: InfoCenter only lets you save one baseline per session rediscovery.
The reason for this limitation is that changes in the session are only
detected during rediscovery. Any two baselines saved without an
intervening rediscovery would be identical.
To save a baseline for a Multicast session:
1 If you haven’t already done so, start InfoCenter.

207569-F
3 In the Resources/Multicast/Sessions folder view, right-click on a session and

choose Baseline > Save Baseline (Figure 94).
Figure 94 Saving a multicast session baseline
InfoCenter prompts whether you want the new baseline to be the active one.
Figure 95 Save Baseline dialog box
4 Click Yes to make the new baseline active, or click no to make the baseline
inactive.
InfoCenter saves a baseline for the session in the Baselines/Multicast Sessions
folder.

Deleting session baselines
To delete a session baseline:
1 If you haven’t already done so, open the Baselines/Multicast Sessions folder.
2 Right-click on any baseline and choose Baseline > Delete.
InfoCenter opens an alert box that prompts whether you are sure you want to
delete the baseline.
3 Click Yes to confirm.
InfoCenter deletes the selected baseline.
To delete all of the baselines for a multicast session:

2 In the folder, right-click on a multicast session and choose Baseline > Delete
All (Figure 96).
Figure 96 Deleting all baselines for a multicast session
207569-F
Viewing session baselines
To view a session baseline:
In the Baselines/Multicast Session folder, double-click on the baseline.
InfoCenter opens a temporary folder view for the session baseline. You can view
the baseline in either tabular presentation (Figure 97) or in graphical presentation
(Figure 98).
Figure 97 Session baseline view (tabular presentation)

Figure 98 Session baseline view (graphical presentation)
Listing the baselines for a multicast session
InfoCenter lets you view a list of all of the baselines for a multicast session. This
feature makes it easy to find and open baselines.
To list the baselines for a multicast session:

2 In the folder, right-click on a multicast session and choose Baseline > Show
all (Figure 99).
207569-F
Figure 99 Listing baselines for a multicast session
InfoCenter opens a temporary All Baseline folder view that shows all of the
baselines for the selected session in tabular presentation.
Figure 100 All Baseline temporary folder view
Designating baselines as active or inactive
For each multicast session, InfoCenter lets you save multiple baselines. However,
only one baseline can be designated as active for each session. The active baseline
is the one that is compared with the session by default.
To designate a baseline as active:
In any folder view containing baselines, right-click on a baseline and choose

Baseline > Set Active (Figure 101).

InfoCenter sets the baseline as active. If another baseline for the same session
was previously active, InfoCenter sets it to inactive. The icon for the baseline
changes after a few seconds, or the next time you refresh the folder.
The most effective folder view for this feature is the All Baseline temporary
folder view, since it shows which baseline is active for the session. See
“Listing the baselines for a multicast session” on page 340 for more
information.
Figure 101 Setting a baseline as active
To designate a baseline as inactive:
In any folder view containing baselines, right-click on an active baseline and

choose Baseline > Set Inactive.
InfoCenter sets the baseline as inactive. The icon for the baseline changes
after a few seconds, or the next time you refresh the folder.
Comparing multicast session baselines
InfoCenter lets you compare multicast sessions with previously saved baselines.
You can also compare multicast sessions baselines with each other. You use these
features to view a graphical display of the differences between the session and the
baseline or between the baselines.
The following sections describe the ways of comparing multicast sessions with
baselines:
• “Comparing a multicast session with the active baseline‚” next

• “Comparing any baseline with its multicast session” on page 345
207569-F
• “Comparing multicast session baselines with each other” on page 345
Comparing a multicast session with the active baseline
You can compare a multicast session with the currently active baseline. This
comparison is the easiest one to perform. For a more general procedure that also
lets you compare inactive baselines, see “Comparing any baseline with its
multicast session” on page 345.
To compare a multicast session with the currently active baseline:
In the InfoCenter Resources/Multicast/Sessions folder, right-click on a

session for which a baseline has been saved and choose Baseline > Compare
(Figure 102).
Figure 102 Comparing a multicast session with its active baseline
InfoCenter opens a temporary window that graphically shows the results of the
comparison between the session and its active baseline (Figure 103).

Figure 103 Temporary window showing results of comparison
The window shows the elements of the following types that comprise the session:
• Subnets
• Routers
• Session links
• Router links
Table 66 describes the colors that show the results of the comparison.
Table 66 Multicast session comparison colors
Color Description
Green Shows unchanged elements

Blue Shows added elements
Red Shows deleted elements
Yellow Shows changed elements
207569-F
Comparing any baseline with its multicast session
To compare any multicast baseline, active or inactive, with the current session:
1 If you haven’t already done so, open the Baselines/Multicast sessions folder.
2 Right-click on any baseline and choose Baseline > Compare.
InfoCenter opens a temporary window that graphically shows the results of
the comparison between the baseline and the current session (similar to
Figure 103).
Comparing multicast session baselines with each other
You can compare a two baselines for the same multicast session with each other.
This comparison shows you the differences between the session configuration at
different times in the past.
To compare two multicast session baselines with each other:
1 If you haven’t already done so, open the Baselines/Multicast sessions folder.
2 Click on the heading for the Label column to order the folder view by label.
This action organizes the view so that baselines are grouped by the sessions to
which they apply, making it easier to find the baselines that apply to a
particular session.

Figure 104 Baselines/Multicast sessions folder ordered by label
3 Use Ctrl+click or Shift+click to select two baselines for the same multicast
session.
On the InfoCenter menu bar, choose View > Baseline operations > Compare
On the InfoCenter Baseline toolbar, click Compare baseline
Note: When comparing two baselines with each other, you cannot use the
object shortcut menu. Right-clicking the second baseline to open the
menu deselects the first baseline.
InfoCenter opens a temporary window that graphically shows the results of the
comparison between the two baselines (similar to Figure 103).
207569-F
Working with multicast view baselines

There are two types of View baselines:
• Routing View baselines - Captures a baseline of the InfoCenter Multicast/

Routing folder
• Session View baselines - Captures a baseline of the InfoCenter Multicast/
Sessions folder, and also captures baselines for each of the sessions in the
folder
The following sections describe how to save and compare the different types of
multicast view baselines:
• “Saving multicast session view baselines‚” next

• “Saving multicast routing view baselines” on page 348
• “Comparing multicast view baselines” on page 349
Saving multicast session view baselines
InfoCenter lets you save a view baseline for all multicast sessions. A view
baseline is comprised of a list of all current multicast sessions and also individual
baselines for each session.
To save a multicast sessions view baseline:
1 In the InfoCenter folder tree, right-click on the Multicast/Sessions folder and

choose Baseline > Save View Baseline.
Figure 105 Shortcut menu for Multicast/Sessions folder

Figure 106 New View Baseline alert box
2 Click Yes to make the new view baseline active, or click No to make the view
baseline inactive.
InfoCenter saves the view baseline in the Baselines/Multicast Views folder.
Saving multicast routing view baselines
InfoCenter lets you save a view baseline for all multicast routing. A view baseline
is comprised of a list of all current multicast sessions and also individual baselines
for each session.
To save a multicast routing baseline:
1 In the InfoCenter folder tree, right-click on the Multicast/Routing folder and

choose Baseline > Save View Baseline.
Figure 107 Shortcut menu for Multicast/Routing folder
207569-F
Figure 108 New View Baseline alert box
2 Click Yes to make the new view baseline active, or click No to make the view
baseline inactive.
InfoCenter saves the view baseline in the Baselines/Multicast Routing folder.
Comparing multicast view baselines
The following sections describe how to compare baselines with each other and
also with the previous network discovery:
• “Comparing multicast view baselines with each other‚” next

• “Comparing multicast view baselines with the current network” on page 351
Comparing multicast view baselines with each other
To compare two multicast session view or multicast routing view baselines with
each other:
1 In the InfoCenter folder tree, open either the Baselines/Multicast Routing

folder or the Baselines/Multicast Views folder.
2 In the folder view, use Ctrl+click or Shift+click to select multiple view
baselines.
3 On the InfoCenter toolbar, click Compare Baseline (Figure 90).

Figure 109 Comparing view baselines (routing view shown, session view similar)
Note: When selecting multiple sessions for rediscovery, you cannot use
the object shortcut menu. Right-clicking a session to open the menu
InfoCenter opens a two-part window that shows you a comparison of the two
baselines (Figure 110).
207569-F
Figure 110 Comparing view baselines (routing shown, session similar)
Comparing multicast view baselines with the current network
To compare a multicast session view or multicast routing view baseline with the
current network:
1 In the InfoCenter folder tree, open either the Baselines/Multicast Routing

folder or the Baselines/Multicast Views folder.
2 In the folder view, select a view baseline.
3 On the InfoCenter toolbar, click Compare Baseline.
InfoCenter opens a two-part window that shows you a comparison of the two
baselines (Figure 110).

Figure 111 Comparing a view baseline with the current network
Exporting and importing baseline data

Optivity NMS lets you export all multicast view and session baseline data to a file
on the Optivity NMS server. You can use this feature along with the import
baseline data feature to transfer baseline data between Optivity NMS servers.
Note: Importing baseline data only works properly when the database of
the Optivity NMS server to which you are importing already contains all
of the devices in the baselines.
To export baseline data:
On the InfoCenter tool bar, choose View > Baseline Operations > Export
Baseline Data.
207569-F
Optivity NMS exports all baseline data to a file on the Optivity NMS server, and
then opens a Baseline Export alert box to show you the name of the file.
Figure 112 Baseline Export alert box with name of file exported to
To import baseline data:
1 On the InfoCenter tool bar, choose View > Baseline Operations > Export
Baseline Data.
InfoCenter opens a dialog box to let you choose which file to import the
baseline data from.
Figure 113 Selecting baseline file to import
2 Select a file and choose OK.

InfoCenter imports the baseline data from the selected file. During the import
operation, the status bar shows that the operation is in progress.
Figure 114 InfoCenter status bar showing database import in progress

The status bar also shows when the operation completes.
Figure 115 InfoCenter status bar showing database imported successfully
207569-F
355
Chapter 9
Managing IP Virtual Private Networks with Optivity
NMS
This chapter describes how to manage IP Virtual Private Networks with Optivity
NMS.
Unlike other chapters in this manual, this chapter is centered more on managing a
type of network than on using a particular Optivity NMS network management
application.
The following sections describe how to use Optivity NMS 10.3 to manage
IP-VPN devices and tunnels:
• “Discovering IP-VPN elements‚” next

• “Visualizing IP-VPN devices and tunnels with InfoCenter” on page 356
• “Viewing performance statistics for IP-VPN elements” on page 358
Note: You can only manage IP virtual private networks if you are
assigned the IP-VPN service. Optivity NMS administrators assign
IP-VPN service, InfoCenter will not show the folders and toolbar buttons
you use to manage IP-VPN elements.
services.

356 Chapter 9 Managing IP Virtual Private Networks with Optivity NMS
Discovering IP-VPN elements

The Optivity NMS autotopology applications discover IP-VPN devices and
services when the IP Virtual Private Network Discovery check box is marked on
the AutoTopology Manager Options dialog box.
For more information on discovering network devices, see Chapter 4,

Visualizing IP-VPN devices and tunnels with InfoCenter

The following sections describe how to open and view IP-VPN devices and
tunnels with InfoCenter:
• “Viewing IP-VPN devices and VPN tunnels in the IP-VPN folder‚” next
• “Viewing IP-VPN devices, physical links, subnets and devices in the physical
layer view” on page 357
• “Viewing IP-VPN devices and VPN tunnels in the IP-VPN Service view” on
page 357
Note: In order to view IP-VPN configurations using Optivity NMS, you

must add an entry for the Optivity NMS server to the SNMP-GET hosts
table on the Contivity devices you are managing. See your Contivity
documentation for more information.
Viewing IP-VPN devices and VPN tunnels in the IP-VPN

folder
To view IP-VPN devices and tunnels:
In the InfoCenter folder tree, open the Resources/IP-VPN folder

(Figure 116).
207569-F
Chapter 9 Managing IP Virtual Private Networks with Optivity NMS 357
Figure 116 Opening the IP-VPN folder in the InfoCenter folder tree
InfoCenter opens a folder view for the IP-VPN folder, showing the IP-VPN
devices and VPN tunnels on the Optivity NMS database.
Viewing IP-VPN devices, physical links, subnets and

devices in the physical layer view
You can use the InfoCenter physical layer view to view all IP-VPN devices,
physical links, subnets and devices:
1 In the InfoCenter folder tree, open the Resources/Internet folder.

2 On the InfoCenter toolbar, click Physical to transform the folder view to the
physical layer.
See “Folder view layers” on page 193 for more information about InfoCenter
layer transformations.
Viewing IP-VPN devices and VPN tunnels in the IP-VPN

Service view
The IP-VPN Service View layer shows you all of the IP-VPN devices and VPN
tunnels in any folder view.
To transform any folder view to the IP-VPN Service View layer:
On the InfoCenter toolbar, click IP-VPN Service View.

358 Chapter 9 Managing IP Virtual Private Networks with Optivity NMS
Viewing performance statistics for IP-VPN elements

The following sections describe how to view performance statistics for IP-VPN
devices and tunnels with OmniView. See Chapter 13, “Monitoring devices with
OmniView and MView,” on page 393 for more information about the OmniView
application:
• “Viewing performance statistics for IP-VPN devices in OmniView‚” next

• “Viewing performance statistics for VPN tunnels” on page 358
Viewing performance statistics for IP-VPN devices in

OmniView
To view performance statistics for IP-VPN devices in OmniView:
In an InfoCenter folder view, right-click on an IP-VPN device and choose

Performance > OmniView from the shortcut menu.
Optivity NMS opens an OmniView window to show performance statistics for the
selected device.
Viewing performance statistics for VPN tunnels
To view performance statistics for VPN tunnels in OmniView:
1 Open any InfoCenter folder view that contains an IP-VPN device.

2 On the InfoCenter tool bar, click IP-VPN Service View to transform the folder
to the IP-VPN Service View layer. See “Folder views” on page 192 for more
information about folder views and layers.
3 In the folder view, right-click on a tunnel and choose
Performance > OmniView from the shortcut menu.
207569-F
359
Chapter 10
Managing IP telephony systems with Optivity NMS
This chapter describes how to manage IP telephony systems with Optivity NMS.
Currently, Optivity NMS supports the following devices:
• Succession 1000 Release 3.0

• Meridian 1 Release 3.0 (Option 11 only)
application. This chapter includes information about using a variety of
management applications to manage IP telephony systems.
The following sections describe how to use Optivity NMS 10.3 to manage IP
telephony systems and devices:
• “Discovering IP telephony devices‚” next

• “Visualizing IP telephony elements” on page 361

360 Chapter 10 Managing IP telephony systems with Optivity NMS
• “Viewing performance statistics for IP telephony systems and components”

on page 366
Note: You can only manage IP-telephony elements if you are assigned
the VOIP service. Optivity NMS administrators assign services using
Access Control Administration. If you are not assigned the VOIP service,
InfoCenter will not show the folders and toolbar buttons you use to
manage IP-telephony elements.
services.
Discovering IP telephony devices

For each IP Telephony system or component, you must create a Community
strings entry that contains the settings shown in Table 67 in order for
AutoTopology Manager to correctly discover the system and components:
Table 67 Required IP Telephony Community strings entry settings
IP Telephony system Community strings entry settings

or component
Meridian 1 Telnet
Succession 1000 Telnet
MCS 5100 Telnet and SSL
Signaling server Telnet
ITG line card Telnet
See Chapter 3, “Specifying access to devices with the Community Strings Editor,”
on page 101 for more information about community string entries.
Also, Data Link Layer discovery must be enabled in AutoTopology Manager. See
Chapter 4, “Discovering your network with AutoTopology Manager,” on page 137
207569-F
Chapter 10 Managing IP telephony systems with Optivity NMS 361
Visualizing IP telephony elements

The following sections describe how to use Optivity NMS 10.3 to view IP
telephony systems and devices, and their relationships with other network devices
and elements:
• “Viewing IP telephony systems with InfoCenter‚” next

• “Viewing parts of an IP Telephony system” on page 362
• “Viewing software components of an IP Telephony system” on page 363
• “Viewing physical links between IP Telephony devices and other data
devices” on page 364
• “Viewing VLAN membership for IP telephony components” on page 365
Viewing IP telephony systems with InfoCenter
You use the IP telephony folder in the InfoCenter folder tree to view all of the IP
telephony systems in the Optivity NMS database. This folder contains:
• Succession 1000 Release 3.0

• Meridian 1 Release 3.0 (Option 11 only)

To view IP telephony systems with InfoCenter:
In the InfoCenter folder tree, open the Resources/IP telephony folder

(Figure 117).
Figure 117 Opening the InfoCenter Resources/IP Telephony folder
InfoCenter opens a folder view showing all of the IP telephony systems in the
Optivity NMS database. (Figure 117).
Figure 118 Typical InfoCenter IP Telephony folder
Viewing parts of an IP Telephony system
You can view the parts of an IP Telephony system in a temporary InfoCenter

folder.
207569-F
To view the parts of an IP Telephony system:
1 In the InfoCenter folder tree, open the Resources/IP telephony folder

(Figure 117).
2 In the IP Telephony folder, double-click on an IP Telephony system.
InfoCenter opens a temporary folder showing the parts of the selected IP
Telephony system (Figure 119).
Figure 119 Temporary folder view for IP telephony system
Viewing software components of an IP Telephony system
You can view the software components of certain IP Telephony systems in a

temporary InfoCenter folder. This feature is currently supported only on MCS
5100 systems.
Note: In order to view the software components of an IP telephony

device, you must use Community Strings Editor to create a community
string entry for the device that includes SSL login information. See
Chapter 3, “Specifying access to devices with the Community Strings
Editor,” on page 101 for more information about community strings
entries.
To view the software components of an IP Telephony system:
1 In InfoCenter, open the Resources/IP Telephony folder.

2 In the IP Telephony folder, double-click on an IP Telephony system.
InfoCenter opens a temporary folder view showing the parts of the selected IP
Telephony system.

3 In the IP Telephony system folder view, double-click on a component of the

IP telephony system to view a list of the software modules installed.
Viewing physical links between IP Telephony devices and

other data devices
You can use the InfoCenter Subnet Aware feature to view the connections between
parts of an IP Telephony system, and between that system and other network
devices. When launched on a device, the Subnet Aware feature shows all of the
devices and links in the subnet the device belongs to. When launched on a system,
it shows all the devices in the system.
To view physical links between IP Telephony devices and other data devices:
1 In InfoCenter, open the Resources/IP Telephony folder.

2 Right-click on an IP Telephony system and choose Subnet Aware from the
shortcut menu (Figure 120).
Figure 120 Subnet Aware menu choice for IP telephony system

207569-F
Figure 121 Temporary subnet aware folder view for IP telephony system
Viewing VLAN membership for IP telephony components
You can use the InfoCenter subnet folder to view the VLAN memberships of the
individual parts of an IP telephony system (call server, signaling server, and media
gateway)
To view the VLAN memberships of the parts of an IP telephony system:
1 In InfoCenter, open the Resources/VLANs/Logical VLANs folder.

2 Double-click on the logical VLAN containing the an IP telephony system
components.

Figure 122 Temporary folder view for logical VLAN view of Succession 1000
system
Viewing performance statistics for IP telephony systems

and components
The following sections describe how to use the OmniView application to view
statistics for IP telephony systems and components:
• “Viewing performance statistics for an IP telephony system‚” next

• “Viewing performance statistics for components of an IP telephony system”
on page 367
Viewing performance statistics for an IP telephony system
To use OmniView to view performance statistics for an IP telephony system such

as a Meridian 1 or a Succession 1000:
1 In InfoCenter, open a folder view containing the IP telephony system.

2 In the folder view, right-click an IP telephony system and choose Performance
> OmniView from the shortcut menu (Figure 123).
InfoCenter launches OmniView on the selected IP telephony system.
207569-F
Figure 123 Launching OmniView on an IP telephony system
Viewing performance statistics for components of an IP

telephony system
To use OmniView to view performance statistics for a component of an IP

telephony system such as a Meridian 1 or a Succession 1000:
1 In InfoCenter, open a folder view containing an IP telephony system.

2 In the folder view, double-click on the IP telephony system to open a
temporary folder view showing the components of the system.
3 In the temporary folder view, right-click an IP telephony component and
choose Performance > OmniView from the shortcut menu (Figure 123).
InfoCenter launches OmniView on the selected IP telephony component.
Figure 124 Launching OmniView on a component of an IP telephony system

207569-F
369
Chapter 11
Managing virtual private LAN services devices
with Optivity NMS
This chapter describes how to manage virtual private LAN services devices with
Optivity NMS.
application. This chapter includes information about using a variety of
management applications to manage VPLS.
Note: You can only manage virtual private LAN services devices if you
are assigned the VPLS service. Optivity NMS administrators assign
VPLS service, InfoCenter will not show the folders and toolbar buttons
you use to manage virtual private LAN services devices.
Installing and Administering Optivity NMS 10.3 (part number 205969-H)
for information on assigning services.
The following sections describe how to discover and manager VPLS devices and
services with Optivity NMS:
• “VPLS Overview‚” next

• “Discovering VPLS elements” on page 370
• “Visualizing VPLS elements” on page 370
• “Testing Transport Domain Continuity” on page 378

370 Chapter 11 Managing virtual private LAN services devices with Optivity NMS
VPLS Overview
VPLS is a standards-based approach to building Ethernet VPNs offered by Nortel
Networks. Unlike previous approaches, VPLS enables even the largest service
providers to roll out all types of managed Ethernet VPN services (including
Internet access, metro transport, and LAN-to-LAN interconnection) easily and
cost-effectively. VPLS ties geographically separate customer sites together as if
they share a common LAN segment.
Optivity NMS 10.3 supports the following VPLS devices:
• OPTera Metro 1200, 1400, and 1450 agent version 1.1 and later.
• OPTera Metro 8000 agent 2.0.1 and later.
Discovering VPLS elements

The Optivity NMS autotopology applications discover VPLS devices and services
whenever the Virtual Private LAN Discovery check box is marked on the
AutoTopology Manager Options dialog box.
For more information on discovering network devices, see Chapter 4,

Visualizing VPLS elements

The following sections describe how to open and view VPLS devices and services
with InfoCenter:
• “Viewing VPLS services in InfoCenter‚” next

• “Viewing VPLS devices, transport domains, and VPLS links in InfoCenter”
on page 372
• “Transforming an InfoCenter folder view to the VPLS layer” on page 372
• “Viewing VLPS elements on the InfoCenter physical layer” on page 373
• “Viewing VLPS elements on the InfoCenter Data Link layer” on page 374
• “Viewing User Network Interfaces” on page 375
207569-F
Chapter 11 Managing virtual private LAN services devices with Optivity NMS 371
• “Viewing VPLS services for a UNI” on page 377
Viewing VPLS services in InfoCenter
InfoCenter lets you view all VPLS services discovered on the network. See
“Discovering VPLS elements” on page 370 For more information about
discovering VPLS services.
To view all discovered VPLS services:
1 In the InfoCenter folder tree, open the Resources folder.

2 In the Resources folder, double-click the VPLS folder.
Figure 125 The InfoCenter VPLS folder
InfoCenter opens a view for the VPLS folder. The default view is a tabular
presentation view at the database layer.
Figure 126 VPLS folder view (Tabular presentation shown)

Viewing VPLS devices, transport domains, and VPLS links

in InfoCenter
InfoCenter lets you view all VPLS devices, their transport domains, and their
VPLS links:
1 In the InfoCenter folder tree, open the Resources/VPLS folder.

InfoCenter opens a view for the VPLS folder. The default view is a tabular
view at the database layer.
2 In the VPLS folder, double-click on any VPLS.
InfoCenter opens a temporary folder containing all of the devices, transport
domains, and links in the VPLS. (Figure 127).
Figure 127 VPLS elements shown in temporary folder.
Transforming an InfoCenter folder view to the VPLS layer
InfoCenter lets you transform any folder view to the VPLS layer. This feature
shows you all of the VPLS elements within the folder.
To transform any folder to the VPLS layer:
1 In the InfoCenter folder tree, open the folder.

2 On the InfoCenter toolbar, click VPLS View.
InfoCenter transforms the folder to the VPLS layer.
207569-F
Figure 128 Switches folder transformed to the VPLS layer
Viewing VLPS elements on the InfoCenter physical layer
InfoCenter lets you transform the VPLS folder view to the physical layer. This
feature shows you all of the VPLS devices and the physical links between them.
To transform the VPLS folder to the physical layer:

2 On the InfoCenter toolbar, click Physical layer.
InfoCenter transforms the folder to the VPLS layer (Figure 129).

Figure 129 Physical layer view of VPLS folder
Viewing VLPS elements on the InfoCenter Data Link layer
InfoCenter lets you transform the VPLS folder view to the data link layer. This
feature shows you all of the layer 2 network elements and interconnecting links
from the topology database as well as MLTs and layer 2 VPN tunnels derived
from the topology database.
You can see collision domains and bridging or switching between the collision
domains. You can also see switches connected to logical segments and other
switches.
To transform the VPLS folder to the physical layer:

2 On the InfoCenter toolbar, click Physical layer.
InfoCenter transforms the folder to the VPLS layer (Figure 129).
207569-F
Figure 130 Data link layer view of VPLS folder
Viewing User Network Interfaces
InfoCenter lets you view all of the UNIs on a device or within a VPLS:
In any folder view, right-click either a VPLS or a VLPS device and choose
Show UNIs from the shortcut menu.

Figure 131 Shortcut menu for VPLS or VPLS device
InfoCenter opens a temporary folder view showing all of the UNIs on the device
or within the VPLS.
Figure 132 Temporary UNIs folder view
207569-F
Viewing VPLS services for a UNI
InfoCenter lets you view all of the VPLS services to which a selected UNI
belongs:
In any folder view, right-click on a UNI and choose Show VPLS.
Figure 133 Shortcut menu for UNIs
InfoCenter opens a temporary folder view showing all of the VPLS services to
which a selected UNI belongs.
Figure 134 Temporary VPLS folder view

Testing Transport Domain Continuity

You can test TD continuity with the TD Continuity Test application. For more
information, see Chapter 12, “Testing Transport Domain Continuity with TD
Continuity Test,” on page 379.
207569-F
379
Chapter 12
Testing Transport Domain Continuity with TD
Continuity Test
• “TD Continuity Test overview‚” next

• “Getting started with TD Continuity Test” on page 381
• “Working with TD Continuity Test” on page 386
TD Continuity Test overview

TD Continuity Test provides a powerful set of tools for troubleshooting
internetworking traffic for TLS services. TD continuity testing lets you simulate
the customer's data path traffic. The test sends and receives test packets and
reports test results. It also lets you check for misconfiguration on the local and
remote ports.
TD Continuity Test is both a debugging tool and Service Level Agreement (SLA)
tool. You can use it to validate all end points, test connectivity, and determine
round trip delay measurements for SLA purposes. You can also configure TD
Continuity Test to automatically perform periodic checks of all endpoints of the
VPN (source UNI to the far end UNI).
You can use TD Continuity Test to calculate:
• Average delay for each endpoint

• Average delay across VPN
• Jitter for each endpoint
• Data path trace
• Data path round-trip delay

380 Chapter 12 Testing Transport Domain Continuity with TD Continuity Test
The UNI ports on an OPTera Metro 1000 device can be configured for transparent
or mapped service type. Ports configured for transparent service type pass traffic
on a single transparent domain (TD) identified by a single TDI. Ports configured
for mapped service type pass traffic on up to 60 TDs, each with a unique TDI. A
UNI port configured as transparent service type assigns all traffic to its associated
transparent domain using the transparent domain identifier (TDI). When
configured for mapped service type, the UNI port assigns traffic to various TDs
based on the VLAN ID; there is a one-to-one VLAN-to-TDI mapping.
The TD Continuity Test application is not dependant on discovery (OM1K as well

as VPLS Service) data. However if VPLS service discovery is completed before
invoking this application, user input for configuring TDC tests (creation of new
tests as well as modifying the existing ones) will be limited to valid data as per the
information available in the ONMS smop database and the boundaries defined in
the MIB definitions of respective fields. Otherwise only generic syntactic checks
and limit validations will be performed on user input.
The OM1k device is a carrier-managed or service-provider-managed edge device

for Optical Ethernet Layer 2 (OEL2) virtual private networks (VPNs) in MTUs or
MDUs across the metropolitan area network (MAN). The MDA uplink module
provides the network-to-network interface (NNI). The 12 10/100 Mbps
front-panel ports serve as user-to-network interfaces (UNIs). You can configure a
transparent domain (TD) to create VPNs. A TD is a logically separate layer 2
network for each customer.
Supported devices
In ONMS 10.2, the TD Continuity Test application supports the following

devices:
• OPTera Metro OM1200 agent version 1.2

• Passport 8600 agent version 3.5.0.OE
When launched on any other device or agent, the TD Continuity Test application
displays an appropriate error message.
207569-F
Chapter 12 Testing Transport Domain Continuity with TD Continuity Test 381
Getting started with TD Continuity Test

The following sections introduce TD Continuity Test and tell how to get started
using it:
• “Starting TD Continuity Test” on page 381

• “TD Continuity Test window” on page 382
Starting TD Continuity Test
To start TD Continuity Test, take one of the actions shown in Table 68.
Table 68 Starting TD Continuity Test
To start TD
Continuity Test
from: Do this:
InfoCenter In the InfoCenter window, right-click a supported device and choose

Configuration > TDC Continuity from the shortcut menu.
command prompt
tdc [-i ip_address]
prompt
tdc [-i ip_address]
Web browser 1. Open InfoCenter in a Web browser. See “Starting InfoCenter” on
2. In the InfoCenter window, right-click a supported device and
choose Configuration > TDC Continuity from the shortcut menu.
See “Supported devices” on page 380 for more information.

TD Continuity Test window
The TD Continuity Test window has six parts as shown in Figure 135.
Figure 135 TD Continuity Test window
Menu bar
and toolbar
Test table
Status bar
Table 69 describes the TD Continuity Test window parts.
Table 69 Parts of the TD Continuity Test window
Part Description
Menu bar Provides access to all available commands. See “Menu bar and toolbar‚”
and tool bar next for information about the menu commands.
Test table See “Test table” on page 384 for information.
Status bar Provides information about current activity in the window, including the
Optivity NMS server host name, user name, and whether TD Continuity Test
features are enabled or disabled. See “Status bar” on page 386 for more
information.
The TD Continuity Test menu bar commands and toolbar buttons provide quick
access to all TD Continuity Test commands.
If you open TD Continuity Test in a Web browser, the menu bar does not display.
Instead, you use the Menu tool on the toolbar to open a shortcut menu of TD
Continuity Test menus.
207569-F
Table 70 describes the TD Continuity Test menu bar commands and toolbar
buttons.
Toolbar
button
Menu Opens the Access Control Administration menu in a Web

browser.
File Export Exports the test configurations for the device to a text file in
comma-separated value format. See “Exporting test
configurations to a file” on page 391 for more information.
Exit Exits the TD Continuity Test application.
Edit New Opens the New/Modify TDC Test Entry dialog box dialog box to
let you create a new test entry.
Modify Opens the New/Modify TDC Test Entry dialog box dialog box to
let you modify the selected test entry.
Delete Deletes the selected test entry.
View Apply Applies the test configurations to the device.
Results Displays the results of the selected test in a TDC Results

window.
Refresh Refreshes the test table with the current tests configured on the
device.
Deselect Deselects the selected test entries. You can also use Ctrl+click
to deselect entries.
Look and Feel Lets you choose any of three window styles:
• Metal
• CDE/Motif
• Windows
See “Changing the look and feel of the window” on page 391 for
more information.
Display Toolbar Toggles the toolbar between displayed or hidden.
Display Status Toggles the status bar between displayed or hidden.
bar

Toolbar
button
Poll Interval Adjusts the interval at which the TD Continuity Test application
queries the network and refreshes the display with the latest test
configurations and results. The default value is Manual, which
refreshes only when you click Refresh or choose View >
Refresh.
Help TD Continuity Opens online Help for the TD Continuity Test window.
Test Help
Using Help Opens online Help on using the online Help system.
About TD Displays version and copyright information for the TD Continuity
Continuity Test Test application.
Test table
The test table on the TD Continuity Test window shows you a summary of the test
entries on the device or TDI. Table 71 describes the parts of the test table.
Table 71 TD Continuity Test window test table
Part Description
Test ID A unique ID number for the test

TDI The TDI number for the test
Src Port Ip The IP address of the source port for the test
Dest Port Ip The IP address of the destination port for the test
Test name The name configured for the test.
Action Controls the test execution. The options are:
• start — execute the test one time
• startPeriodic — begin periodic execution of a test
• abort — terminate the test if it is currently running
• abortPeriodic — cancel future executions of a periodictest (will not
halt a current test)
207569-F
Table 71 TD Continuity Test window test table (continued)
Part Description
Test type The type of test to be performed. Options are:

• Broadcast and Unicast
• Broadcast only
• Unicast only
• Multicast and unicast
• Multicast only
Trace type Shows time trace information. The options are:
• None (default) — Validates the provisioning associated with the
source ports, destination ports, and transport domains.
• Time — Collects the round-tip time of the packets between source
and destination.
• Trace — Collects the IP address, machine address, and port
information for nodes along the path from the source and
destination and back.
Test date The date on which the test was started.
Test time The time at which the test was started.
Action Lets you set view or change the execution of the test. Double-click on
the cell to open the Action menu. The choices are:
• start — Execute the test one time.
• startPeriodic — Begin periodic execution of a test.
• abort — Terminate the test if it is currently running.
• abortPeriodic — Cancel future executions of a periodic test (will
not halt a current test).
See “Starting and stopping a TDC test” on page 388 for more
information.
Scheduled Shows whether the test is currently scheduled to execute in periodic
mode:
• true — The test is scheduled to run at some future time, and will
execute as scheduled unless manually aborted.
• false — The test is not scheduled to run in periodic mode.
Result The result of the test. Values are:
• None — No results are available.
• In Progress — The test is in progress.
• Success — The test completed successfully.
• Fail — The test failed. The reason(s) for the failure are described in
the Error column of the Results tab of the TDC Results window.
See “Understanding TDC test errors” on page 390 for more information
about test result errors.

Status bar
The status bar, located along the bottom of the TD Continuity Test window, shows
the status of the application and of the current operation.
Working with TD Continuity Test

The following sections describe how to work with TD Continuity Test:
• “Working with test entries‚” next

• “Starting and stopping a TDC test” on page 388
• “Viewing TDC test results” on page 389
• “Changing the look and feel of the window” on page 391
• “Exporting test configurations to a file” on page 391
• “Exporting test results to a file” on page 392
Working with test entries
The following sections describe how to create and modify TDC test entries:
• “Adding a new test entry‚” next

• “Editing a test entry” on page 387
• “Deleting a test entry” on page 388
Adding a new test entry
To add a new TDC test entry to a device:
1 On the TD Continuity Test tool bar, click New Test.

TD Continuity Test opens an New/Modify TDC Test Entry dialog box to let
you configure the new test entry (Figure 136).
2 (Optional) Click Advanced to expand the dialog box to show the advanced
test features in addition to the basic features.
207569-F
Figure 136 New/Edit TDC Test Entry dialog box (advanced shown, basic similar)
3 Configure the settings for the new test entry.

Click Help on the dialog box for description of the various test settings.
4 Click OK to add the new test entry to the table in the TD Continuity Test
window.
5 Click Apply to device to apply the new test entry to the device.
Editing a test entry
To edit an existing test entry:
1 In the table on the TD Continuity Test window, select the test entry you want
to modify.
2 On the TD Continuity Test menu bar, click Edit > Modify.
TD Continuity Test opens an New/Modify TDC Test Entry dialog box to let
you modify the test entry (Figure 136).
3 (Optional) Click Advanced to expand the dialog box to show the advanced
test features in addition to the basic features.
4 Configure the settings for the modified test entry. Click Help on the dialog
box for description of the various test settings.

5 Click OK to update the table in the TD Continuity Test window with your
changes.
6 Click Apply to device to apply the modified test entry to the device.
Deleting a test entry
To delete an existing test entry:
1 In the table on the TD Continuity Test window, select the test entry you want
to delete.
2 On the TD Continuity Test menu bar, click Edit > Delete.
TD Continuity Test opens an alert box to prompt you to confirm the deletion
(Figure 137).
Figure 137 Delete test entry confirmation alert box
3 Click OK to remove the test entry from the table in the TD Continuity Test
window.
4 Click Apply to device to apply the deletion to the device.
Starting and stopping a TDC test
To start or stop a TDC test that you have configured on a device:
1 In the TD Continuity Test window TD Continuity Test window, find the entry
for the test you want to start.
2 In the Action column, double click on the entry for the test you want to start.
A menu of start options opens.
• To run the test once, choose start
207569-F
• To rerun the test periodically, choose startPeriodic

• To stop a test that is in progress, choose abort
• To stop a test that is configured to run periodically, choose abortPeriodic.
4 On the TD Continuity Test toolbar, click Apply changes to device.
5 After a short interval (10 seconds to a minute, depending on your devices and
network), click Refresh entries from device to refresh the display with the
latest configurations and test results from the device.
Viewing TDC test results
To view the results for TDC tests:
1 On the TD Continuity Test window, select the tests for which you want to
view results.
You can click a single entry, drag multiple entries, and use Shift+click and
Ctrl+click to select multiple entries. You can also use Ctrl+A to select all
entries.
2 On the TD Continuity Test menu bar, choose View > Results.
TD Continuity Test opens a TDC Results window with the Results tab at the
front to show you the test results (Figure 138).
3 Use the Results tab, History tab, and Trace tab of the TDC Results window to
view test results, history, and trace information for the selected tests.
Figure 138 TDC Results window (Results tab shown)

Understanding TDC test errors
The following list shows all of the TDC test error descriptions you can encounter
while using TD Continuity Test:
• TD nonexistent on destination port

• TD disabled on destination port
• TD not assigned to destination port
• TD filtered on destination NNI port
• destination port is NNI
• destination port is craft
• destination FDB test failed
• destination administrative state down
• destination operational state down
• destination port connectivity mismatch error
• destination port type mismatch
• destination port mode mismatch error
• destination MIB query failed
• destination system error
• invalid destination port
• destination port is CPU
• destination port mode mismatch warning
• destination port connectivity mismatch warning
• default priority used on destination
• IP not assigned on destination oel2 port
• static entry exists on destination port
• destination FDB table full warning
• TD nonexistent on source port
• TD not assigned to source port
• source FDB test failed
• source administrative state down
• source operational state down
• source system error
• no response
207569-F
• could not get trace information

• could not get time information
• source MIB query failed
• TD disabled on source port
• invalid source port
• all ports down on the source node
• unknown error
• source FDB test failed
• static entry exists on source port
• no FDB entry for dst MAC, unicast aborted
• RTT threshold exceeded
Changing the look and feel of the window
TD Continuity Test lets you change the look and feel of the TD Continuity Test
window to best match the operating system under which it is running.
To change the look and feel of the TD Continuity Test window:
1 From the TD Continuity Test menu bar, choose View > Look and feel.
The Look and Feel shortcut opens.
Exporting test configurations to a file

TD Continuity Test lets you export selected TDC test entries to a text file in
comma-separated values format.
To export test entries:
1 On the TD Continuity Test window, select the tests you want to export.
You can click a single entry, drag multiple entries, and use Shift+click and
Ctrl+click to select multiple entries. You can also use Ctrl+A to select all
entries.
2 On the TD Continuity Test menu bar, choose File > Export.

TD Continuity Test opens a save file dialog box to let you specify the location
and filename for the file.
3 Navigate to the folder or directory for the file you want to export the results to.
4 Enter a name for the file in the File Name box.
5 Click OK.
Exporting test results to a file
TD Continuity Test lets you export the results of selected TDC tests to a text file in
comma-separated values format.
To export test results:
1 If you haven’t already done so, open the tests for which you want to export
results in a TDC Results window. See “Viewing TDC test results” on
2 In the TDC Results, choose File > Export.
TD Continuity Test opens a save file dialog box to let you specify the location
and filename for the file.
3 Navigate to the folder or directory for the file you want to export the results to.
4 Enter a name for the file in the File Name box.
5 Click OK.
207569-F
393
Chapter 13
Monitoring devices with OmniView and MView
OmniView and MView are two different interfaces for the same Optivity NMS
monitoring application. OmniView is a general-purpose monitoring application,
while MView is specifically optimized for monitoring RMON and SMON
devices.
• “OmniView and MView overview‚” next

• “Getting started with OmniView and MView” on page 396
• “Working with OmniView” on page 423
• “Working with MView” on page 501
• “Troubleshooting OmniView and MView” on page 511
OmniView and MView overview

The following sections describe the OmniView and MView applications:
• “OmniView‚” next
• “MView” on page 395
OmniView
OmniView lets you monitor your network from the highest LAN levels down to
specific ports on a device. You can use OmniView to view statistics for network
resources in both graphic and tabular form. You can also use OmniView to view
the following:
• Protocol statistics for unicast, multicast, and frame relay network entities

394 Chapter 13 Monitoring devices with OmniView and MView
• Statistics for RMON and SMON MIB groups
The information displayed by OmniView comes from SNMP agent software

running on the network devices being monitored. The specific types of
information available in any particular view depend on the type and version of the
agent software in use.
Use OmniView to monitor the network resources listed in Table 72.
Table 72 Types of network resources
Icon Resource
Unicast
Multicast
Frame Relay
Hubs
Switches
Routers
WANs
Segments
Subnets
VLANs
ELANs
IP-VPNs
207569-F
Chapter 13 Monitoring devices with OmniView and MView 395
MView
MView lets you view remote monitoring (RMON) and switch monitoring
(SMON) information about your frame switched network in tabular or graphical
format.
MView uses the OmniView application window and interface. Where this chapter
refers to OmniView, that information applies to both OmniView and MView
unless otherwise noted.
Optivity NMS 10.3 integrates standard management information base (MIB)

support for the following:
• RFC 1757—RMON1 (Ethernet) statistics and history

• RFC 1513—RMON1 (token ring extension) statistics and history
• RFC 2021—RMON2 user history and protocol distribution
• RFC 2613—SMON VLAN distribution and priority distribution
You use MView to monitor and view RMON and SMON information from a
RMON or SMON device, end node, or a link to a RMON device. You can monitor
the following network management information:
• Ethernet or token ring segment statistics

• Ethernet or token ring performance and fault history—MView displays data
from the History group and userHistory (if the RMON device supports
RMON2).
• Protocol distribution—Provides data from the Protocol Distribution group.
MView displays the protocol distribution MIB table in two panes:
— Network layer pane
— Application layer pane
• Accounting—MView monitors usrHistory data and provides visual indication
of how network resource are used.
• VLAN distribution statistics
The information displayed by MView comes from SNMP agent software running
on the network devices being monitored. The specific types of information
available in any particular view depend on the type and version of the agent
software in use.

MView lets you start a monitoring session for one datasource (an interface or slot
and port) at a time. For example, a router can have multiple interfaces. MView lets
you select which interface to monitor.
MView also lets you select one or more RMON or SMON data types, for example,
segment statistics, performance history, and so forth, for one interface or slot and
port. MView displays the resultant data type information in their respective default
panes in the MView monitor pane.
You can also start MView to display the port profile characteristics of a link that
connects between a layer 2 switch and an end node.
Getting started with OmniView and MView

See the following sections for information about getting started with OmniView
and MView:
• “Access permissions for OmniView and MView‚” next

• “Starting OmniView and MView” on page 398
• “OmniView and MView window” on page 405
Access permissions for OmniView and MView
OmniView and MView share the same access permissions. Your access to both
applications depends on the OmniView Access Control permission tokens listed in
Table 73.
Table 73 Access Control permission tokens for OmniView
If attached with read

OmniView token If not attached
permission only
OM_READ_STATS You cannot start You can view any

OmniView. previously existing panes
and set preferences.
OM_CONF_TEMPL You cannot create any You cannot create any
user-specific statistics user-specific statistics
tables or graphs. tables or graphs.
207569-F
Table 73 Access Control permission tokens for OmniView (continued)
If attached with read

OmniView token If not attached
permission only
OM_CONF_ALLUSERS You cannot create any You cannot create any
all-user statistics tables all-user statistics tables
or graphs. or graphs.
OM_SNMP_SETS You cannot create any You cannot create any
all-user statistics tables all-user statistics tables
or graphs. or graphs.
An Optivity NMS administrator sets user access to OmniView by configuring

access to the OmniView tokens in the Access Control Administration window.
For more information about using Access Control Administration, see Chapter 2,
Administration,” on page 75.

Starting OmniView and MView
To start OmniView or MView, take one of the actions shown in Table 74. See
“Guidelines for starting MView” on page 404 for specific guidelines regarding
starting MView.
Table 74 Starting OmniView or MView
To start: From: Do this:
OmniView Windows Start Choose Start > Programs > Optivity > OmniView
menu
An InfoCenter Any of the following:
folder view • Right-click a network resource and choose
Performance > OmniView from the shortcut menu
• Select a network resource and click Performance Category Apps on
the InfoCenter launchpad
• Select a network resource and choose
Tools > Performance > OmniView from the InfoCenter menu bar
command prompt
omniview [<param_1>]...[<param_n>]
See “OmniView and MView command line options‚” next for more
information about optional OmniView command line parameters.
prompt
omniview [<param_1>]...[<param_n>]
information about optional OmniView command line parameters.
Web browser http://<ONMS server>/omniview.html
See “OmniView and MView URL options” on page 402 for more
information about optional OmniView URL parameters.
207569-F
Table 74 Starting OmniView or MView (continued)
MView An InfoCenter Any of the following:

folder view • Right-click an RMON or SMON resource and choose Performance
> <RMON statistics group>.
• Select a network resource and click Performance Category Apps on
the InfoCenter launchpad. From the Selection dialog box, choose an
RMON statistics group.
• Select a network resource and choose
Tools > Performance > <RMON_statistics_group> from the
InfoCenter menu bar
command prompt
mview [<param_1>]...[<param_n>]
information about optional OmniView command line parameters. If you
do not specify all of the required options, the Monitored entity dialog box
opens to prompt you for the missing parameters.
prompt
mview [<param_1>]...[<param_n>]
information about optional OmniView command line parameters. If you
do not specify all of the required options, the Monitored entity dialog box
opens to prompt you for the missing parameters.
Web browser http://<ONMS server>/mview.html
See “OmniView and MView URL options” on page 402 for more
information about optional OmniView URL parameters.
OmniView and MView command line options
OmniView provides optional commands to let you customize how OmniView

starts. You can start OmniView with one or more devices specified in the syntax of
the command line. This method starts OmniView with the specified devices in the
navigation pane.
Note: If you start OmniView from a UNIX or Windows command line,

the Tool menu commands are unavailable. If you start OmniView from
any other location, the Tool menu commands are available.

You can also start OmniView without specifying any devices in the command line.
If you start OmniView without specifying any options in the command line, the
Specify Entity to be Monitored dialog box opens, where you specify the device to
be monitored. If you click Cancel, OmniView starts without any devices in the
navigation pane. In this case you must add devices to the navigation pane after you
start OmniView. For more information, see “Adding a network resource to the
navigation pane” on page 425.
Table 75 describes the optional commands for the OmniView and MView
command lines.
Table 75 OmniView command line parameter options
Option Description
-I [<ip_addr>|<DNS>] Specifies a device by IP address or DNS name. You can specify

multiple devices in the command string by using -I parameter
multiple times.
OmniView or MView starts with the specified device(s) in the
navigation pane. You cannot use the -I parameter with non-device
resources such as WANs, ELANs, or VLANs.
-R <read> Specifies the SNMP read community string used to access the
device specified by the most recent -I parameter in the command
string.
-W <write> Specifies the SNMP write community string used to access the
string.
-O <label> Specifies a network resource by its label in the Optivity NMS
database. OmniView starts with the specified resource in the
navigation pane.
-auth <key> Specifies the authentication key used to access the SNMP V3
device.
-priv <key> Specifies the private key used to access the SNMP V3 device.
-H (MView only) Specifies the OmniView server name. The name you enter is
displayed in the OmniView login dialog box. The H option is
optional. The default name is localhost.
-T (MView only) Specifies the SNMP time out value in seconds. If the T option is
not specified, MView uses value specified in the Community
Strings editor.
-Q (MView only) Specifies the data type template that MView uses to monitor and
display information in the monitor pane.
-X (MView only) Specifies the interface index. The X option is not used with the S
or P parameter.
207569-F
Table 75 OmniView command line parameter options (continued)
Option Description
-S (MView only) Specifies the slot number. The S option has to be specified with
the P option, and should not be used with the X option.
-P (MView only) Specifies the port number. The P option has to be specified with
the S option, and should not be used with the X option
Table 76 describes the MView -Q options for specifying the data type
template.
Table 76 Data type templates for the MView -Q option
Data type template Data type
segstat Segment Statistics

perfhist Performance history
usrhist
faulthist Fault history
usrhist
nprotdist Protocol distribution
aprotdist
usrhist Accounting
vlandist VLAN distribution
priodist Priority distribution
pprofile Port profile
The following examples shows how to use the OmniView command line
parameter options:
omniview
omniview -I 10.127.233.5 -I 10.127.233.19
omniview -I 10.127.233.5 -R public -W quibble

-I 10.127.233.19 -R public -W quake
omniview -O iron -R public -W quibble -O zinc -R public

-W quake

mview
mview -I 10.127.233.5
mview -I 10.127.233.5 -X 1
mview -I 10.127.233.5 -X 1 -Q segstat -Q perfhist
Note: You must keep the Command Prompt window running for the
duration of the OmniView session.
OmniView and MView URL options
You can start OmniView in a Web browser and specify one or more devices in the
URL. This method starts OmniView with the specified devices already in the
navigation pane.
You can also start OmniView without specifying any devices in the URL. This
method starts OmniView without any devices in the navigation pane. In this case,
you must add devices to the navigation pane after you start OmniView. For more
information, see “Adding a network resource to the navigation pane” on page 425.
Table 77 describes the OmniView URL options.
Table 77 URL options
Option Description
host Specifies the host name or IP address of the system where OmniView is
installed.
? Indicates that the URL contains parameters that specify monitored devices.
207569-F
The parameter option (param_1 through param_n) can be any combination of the
options listed in Table 78, separated by plus signs (+).
Table 78 Web browser parameter options
Option Description
-I [<ip_addr>|<DNS>] Specifies a device by IP address or DNS name. You can specify

multiple devices in the command string by using -I parameter
multiple times.
OmniView starts with the specified device(s) in the navigation
pane. You cannot use the -I parameter with non-device
resources such as WANs, ELANs, or VLANs.
-R+<read> Specifies the SNMP read community string used to access the
string.
-W+<write> Specifies the SNMP write community string used to access the
string.
-O+<label> Specifies a network resource by its label in the Optivity NMS
database. OmniView starts with the specified resource in the
navigation pane.
-auth <key> Specifies the authentication key used to access the SNMP V3
device.
-priv <key> Specifies the private key used to access the SNMP V3 device.
-Q (MView only) Specifies the data type template that MView uses to monitor and
display information in the monitor pane.
-X (MView only) Specifies the interface index. The X option is not used with the S
or P parameter.
-S (MView only) Specifies the slot number. The S option has to be specified with
the P option, and should not be used with the X option.
-P (MView only) Specifies the port number. The P option has to be specified with
the S option, and should not be used with the X option
The following examples show to use the Web browser parameter options:
http://10.127.114.86/omniview.html
http://10.127.114.86/omniview.html?-I+10.127.51.15
+-I+10.127.51.13
http://10.127.114.86/omniview.html?-I+10.127.233.5+
-R+public+-W+quibble+-I+10.127.233.19+-R+public+-W+quake

http://10.127.114.86/omniview.html?-O+iron+-R+public+-W+
quibble+-O+zinc+-R+public+-W+quake
http://10.127.114.86/mview.html
http://10.127.114.86 mview.html?-I+10.127.51.15
http://10.127.114.86/mview.html?-I+10.127.233.5+
-R+public+-W+quibble+-X+1
http://10.127.114.86/mview.html?-I+10.127.233.5+
-R+public+-W+quibble+-X+1+-Q+segstat
Note: The URL syntax is similar to the UNIX and Windows command
syntax. However, in the URL syntax there are no spaces allowed.
Anywhere that you would use a space in the command line, you use a
plus sign (+) in the URL.
Note: You can use your Web browser’s Bookmark or Favorites feature
to bookmark the OmniView application. Doing so saves the URL for
OmniView and also the URL syntax for any specified devices.
Guidelines for starting MView
Table 79 describes the general guidelines for starting MView.
Table 79 Guidelines for starting MView
Starting from Guideline
InfoCenter If started from a host object, one IP address and slot and port index
from the connecting device is selected for monitoring.
Command line If started from the command line, MView is only started against a
RMON device. MView is not started against a link or an end node. If
you start MView without specifying a device, the Monitored Entity
dialog box opens. You must specify the device you want to monitor, to
start MView.
207569-F
Table 79 Guidelines for starting MView
Starting from Guideline
Probe If a probe has multiple interfaces, whether MView is started from

InfoCenter or the command line, the Probe Selection dialog box
opens. You must specify the device IP address and interface to start
MView against.
Non-database If MView is started against a device that is not in the Optivity NMS
device 10.3 database, the system checks to see if the device is a probe using
its sysObjId and VOGON database. If the device is not a probe and no
interface information is provided, an error message is displayed. In
this case, the error message alerts you that you must specify an
interface to monitor.
OmniView and MView window
The OmniView and MView windows have five parts as shown in Figure 139.
Figure 139 Parts of the OmniView window (MView similar)
Menu bar
Toolbar
buttons
Navigation
pane
Monitor
pane
Status bar

Table 80 describes the parts of the OmniView window.
Table 80 Parts of the OmniView window
Part Description
Menu bar Provides access to all available commands. Commands that are
displayed for a device depend on the network protocol, the type of
device, and the capabilities of the embedded agent.
For more information about the menu bar, see “Menu bar” on page 406.
Toolbar Provides quick access to commonly used commands, tools, and
integrated applications.
For more information about the toolbar, see “Toolbar buttons” on
page 411.
Navigation Lets you easily navigate to a particular device or level.
pane For more information about the navigation pane, see “Understanding the
Monitor Displays statistics panes and graph panes that show you current
pane statistics for the network elements being monitored.
For more information about the monitor pane, see “Understanding the
monitor pane” on page 414.
Status bar The status bar displays:
• The name of the currently selected statistics pane.
• The time of the last polling.
• The name of the menu command or toolbar button under the pointer.
Menu bar
The OmniView menu bar provides commands that let you navigate network
resources, work with statistics, and display statistics graphically. If you open
OmniView in a Web browser, the menu bar is not displayed, but is accessed from a
tool in the OmniView Web browser toolbar. The first tool in the toolbar opens a
shortcut menu of OmniView menus and submenus.
207569-F
Table 81 describes the OmniView menu commands.
Table 81 OmniView menu commands
Toolbar
button
Menu Opens the OmniView menu in a Web browser.
File Monitor New Opens the Monitor additional entity dialog box, where you specify
Entity a new object to be monitored.
For more information, see “Adding a network resource to the
Open Pane Opens a statistics pane in the monitor pane to display statistics
for the selected network element.
For more information, see “Viewing statistics for a network
element” on page 433.
Import Data Loads a previously saved data file into an OmniView graph
window.
For more information, see “Importing statistics” on page 471.
Export Data Opens the Export data dialog box to let you save statistics to a
data file.
For more information, see “Exporting statistics” on page 471.
Load Workspace Loads a previously saved arrangement of network elements,
tables, and graphs within the OmniView window.
For more information, see “Customizing OmniView” on page 476.
Save Workspace Saves the current arrangement of network elements, tables, and
graphs within the OmniView window.
Print Prints the selected statistics pane.
Print Page to File Prints the selected statistics pane to a file.
Recent Data Lists the most recently saved data files. Click a data file to load it.
Files
Recent Lists the most recently saved workspace files. Click a workspace
Workspaces file to load it.
For more information, see “Using workspaces to save and restore
views” on page 430.
Exit Exits OmniView.

Table 81 OmniView menu commands (continued)
Toolbar
button
Edit (Not Find Network Opens the Find network element dialog where you can locate a
available in Element network resource by any of several criteria.
MView). For more information, see “Exporting statistics” on page 471.
Find Next Automatically searches for the next network resource matching
the search criteria entered in the Find Network Element dialog
box.
View Display Toolbar Switches the toolbar between displayed and hidden.
For more information, see “Hiding or displaying the toolbar or
status bar” on page 482.
Display Status Switches the status bar between displayed and hidden.
Bar For more information, see “Hiding or displaying the toolbar or
status bar” on page 482.
Look and Feel Opens a submenu where you choose the color and style of the
OmniView window.
For more information, see “Changing the look and feel of
OmniView” on page 481.
Options Remote Switches the Remote Selection feature between on and off. The
Selection Remote Selection feature coordinates the highlighting of devices
between OmniView and InfoCenter.
Display Label Opens a submenu that lets you choose to identify devices by one
of the following labels:
• Default device IP label
• DNS name
• System name
Preferences Opens the Preference dialog box where you set preferences for
OmniView.
207569-F
Toolbar
button
Pane Close Pane Closes the selected pane.
Close All Closes all statistics panes.

Update Updates the selected statistics pane with the latest information
from the monitored device.
Update All Updates all statistics panes with the latest information from the
monitored devices.
Set Polling Opens the Polling parameters dialog box where you set the
polling for the selected object.
Set Polling for All Opens the Polling parameters dialog box where you set the
polling for all objects.
Data Type Opens a submenu that lets you choose the statistics types for the
selected pane
For more information, see “Understanding statistics types” on
page 435.
Clear Counters Clears all of the counters for the selected pane.
All Panes Opens a submenu that lets you select the percentage display
type for all panes.
Show Bar Adds bar indicators to the selected column.
Indicator For more information, see “Viewing statistics with bar indicators”
on page 434 and “Reading bar indicators” on page 434.
Export Opens an Export data dialog box to let you save statistics to a
data file.
Define New Pane Opens the Customize Pane Wizard where you create a custom
statistics pane.
For more information, see “Creating a customized statistics pane”
on page 455.
Customize Opens the Customize Pane Wizard where you customize an
existing statistics pane.
For more information, see “Customizing an existing pane” on
page 457.

Toolbar
button
Graphs New Line Graph Creates a line graph to display the contents of the selected table
cells. The command opens a submenu that lets you position the
new graph either in the monitor pane or in a new window. The
toolbar button opens the graph according to the settings of the
Charts tab in the Preferences dialog box.
New Bar Graph Creates a bar graph to display the contents of the selected table
toolbar button opens the graph according to the settings of he
New Pie Graph Creates a pie graph to display the contents of the selected table
toolbar button opens the graph according to the settings of he
Network Minimize Open Minimizes all of the statistics panes pertaining to the selected
Element Panes device.
This command is only available if a statistics pane is selected.
Maximize Open Maximizes all of the statistics panes pertaining to the selected
Panes device.
This command is only available if a statistics pane is selected.
List Monitored Displays submenus that list all monitored entities and their
Entities statistics panes. For more information, see “Listing monitored
resources and elements” on page 430.
Tools The Tools menu provides commands that start the corresponding Optivity NMS applications
specified in the Optivity Application Launch window. If you start OmniView from a UNIX or
Windows command line, the Tools menu commands are unavailable. If you start OmniView
from any other location, the Tool menu commands are available. For more information about
setting which applications you can start from OmniView, see the InfoCenter Application Launch
online Help system.
Window The Window menu displays a list of currently open graph windows. Choose a graph window
from the menu to bring it to the front.
Help OmniView Help Opens the OmniView online Help system in your default Web
browser.
Using Help Opens a Help topic describing how to use the Help system.
MIB Help Opens a window that displays text descriptions of all of the MIB
objects in the selected statistics pane.
About OmniView Displays copyright and version information about OmniView.
207569-F
Toolbar buttons
The toolbar buttons provide quick access to commonly used OmniView

commands.
Table 82 describes the OmniView toolbar buttons.
Table 82 OmniView toolbar buttons
Menu Opens the OmniView menu in a Web browser.
Monitor New Adds a new network resource to the navigation pane. The
Entity Monitor Additional Entity dialog box opens, which lets you
specify the new object to be monitored.
For more information, see “Adding a network resource to
the navigation pane” on page 425.
Open pane Opens a statistics pane in the monitor pane to display
statistics for the selected network element.
For more information, see “Viewing statistics for a
network element” on page 433.
Close Pane Closes the selected statistics pane.
Line Graph Creates a line graph to display the contents of the

selected table cells.
For more information, see “Viewing statistics graphically”
on page 463.
Bar Graph Creates a bar graph to display the contents of the
on page 463.
Pie Graph Creates a pie graph to display the contents of the
on page 463.
Polling Sets the polling interval for the selected statistics pane.
Interval For more information, see “Setting polling parameters” on
page 446.
Update Pane Updates the selected statistics pane with the latest
information from the monitored device.

Table 82 OmniView toolbar buttons (continued)
Update All Updates all statistics panes with the latest information
Panes from the monitored devices.
Scale box Provides three predefined scale settings: 50%, 100%,

and 200%. The scale is manually entered as a value
greater than 0 up to 200%.
For more information, see “Changing the OmniView
graph scale” on page 467
Enable/ Enables and disables the zoom in. For more information,
Disable Zoom see “Enlarging and shrinking the graph with zoom” on
In page 467
Zoom Out Zooms out to the previous view. For more information,
Previous see “Enlarging and shrinking the graph with zoom” on
page 467.
Zoom Out Top Zooms out to the original view. For more information, see
“Enlarging and shrinking the graph with zoom” on
page 467.
Understanding the navigation pane
Figure 140 shows the OmniView navigation pane. The navigation pane lets you
browse your network using a navigation tree, as shown in the following example.
207569-F
Figure 140 OmniView navigation pane (MView similar)
Resource
Node element (expanded)
Leaf elements
Node elements
(collapsed)
Note: The exact appearance of the OmniView or MView window may

differ depending on the setting of the Look and Feel option. For more
information about the Look and Feel option, see “Changing the look and
feel of OmniView” on page 481.

Table 83 describes the parts of the OmniView navigation pane.
Table 83 Parts of the OmniView navigation pane
Part Description
Resource Network resource, identified by icons:
OmniView MView
Network devices and groupings RMON or SMON entity such as:

such as: • Device (probe, switch)
• Devices (hubs, switches, and • End node
routers)
• Link to a RMON device
• Subnets
• Segments
• ELANs
• VLANs
Node You can expand node elements to show either leaf elements or other node
elements elements.
Leaf You can expand leaf elements to display statistics panes in the monitor
elements pane of the OmniView window.
A dot on the right side of a leaf element indicates that there is currently a
statistics pane open for that element. Click on the element to select the
matching statistics pane in the monitor pane.
If the dot is green, the device from which the statistics were obtained
responded normally to the last SMNP poll from Optivity NMS 10.3.
Understanding the monitor pane
The monitor pane of the OmniView window displays current statistics for the
network elements being monitored.
The statistics are displayed in panes that are grouped by resource. The groupings
are shown by different thicknesses of borders, and optionally by resource icons.
207569-F
Figure 141 shows the monitor pane parts.
Figure 141 Parts of the OmniView monitor pane.
Resource icon
Statistics pane
(maximized)
Resource border
Statistics pane
border
Statistics pane
(minimized)
Note: The exact appearance of the OmniView window may differ

depending on the setting of the Look and Feel option. For more
information about the Look and Feel option, see “Changing the look and
feel of OmniView” on page 481.

Table 84 describes the parts of the OmniView monitor pane.
Table 84 Parts of the OmniView monitor pane
Part Description
Resource Shows the type of resource for a group of statistics panes. To minimize
icon or maximize all of the statistics panes for a resource, click the icon.
To enable or disable the resource icons, use the OmniView Preference
dialog box.
For more information, see “Configuring how OmniView displays resource
icons” on page 477.
Statistics Shows statistics for network elements selected from the navigation pane
pane on the left side of the OmniView window.
You can minimize or maximize statistics panes to get the best view of the
statistics. You can also:
• Drag a statistics pane to a different location within a resource group.
• Drag a statistics pane so that it is next to another pane instead of
above or below it.
You cannot drag a statistics pane outside of its original resource
grouping.
Resource Shows the boundaries of a group of statistics panes for a network
border resource. The resource border is thicker than the regular statistics pane
border.
Statistics pane Shows the boundary of a single statistics pane. The statistics pane
border border is thinner than the resource border.
Understanding the OmniView graph window
The following sections describe the OmniView graph window:
• “OmniView graph window‚” next

• “Graph window menu commands” on page 418
• “Graph window toolbar” on page 421
• “Parts of a graph” on page 422
207569-F
OmniView graph window
The OmniView graph window lets you view statistics graphically, in the form of a
line, bar, or pie graph as shown in Figure 142.
Figure 142 OmniView graph window
Menu bar
Toolbar
Graph pane
To open a graph window, see “Viewing statistics graphically” on page 463.
Table 85 describes the parts of the OmniView graph window.
Table 85 Parts of the OmniView Graph window
Part Description
Menu bar Provides access to all of the available graphing commands. For more
information, see “Graph window menu commands” on page 418.
Toolbar Provides quick access to commonly used graphing commands. For
more information, see “Graph window toolbar” on page 421.
Graph pane Displays the parameters being graphed. The graph window may contain
more than one graph pane. For more information, see “Parts of a graph”
on page 422.

Graph window menu commands
The Graph window menu bar provides access to all of the available graphing
commands. Table 86 describes the Graph window menu commands.
Table 86 Graph window menu commands
Toolbar
button
File Open Graph Opens a graph saved as a file. For more information, see “Importing
Data statistics” on page 471.
Save Graph Saves graph data to a file. For more information, see “Exporting
Data statistics” on page 471.
Close Graph Removes the selected graph from the window.
Print Prints the selected graph pane.

Close Closes the graph window.
Window
207569-F
Table 86 Graph window menu commands (continued)
Toolbar
button
Format Rotate Rotates the selected graph by transposing the x and y axes. For
Graph more information, see “Rotating line or bar graphs” on page 465.
Regroup For bar and pie graphs, changes the way the bars or slices are
grouped. For more information, see “Regrouping bar or pie graphs”
on page 465.
Show Displays the graph legend. For more information, see “Applying or
Legend removing a graph legend” on page 466.
Show Displays the graph summary table.

Summary
Table
Show Marks data points on the traces of line graphs. For more
Symbols information, see “Viewing graphing symbols (line graph only)” on
page 466.
Show Values For bar, stacked bar, and pie graphs, shows the numerical values of
the different bars or pie slices. For more information, see “Viewing
graph values” on page 466.
Bar Format Selects one of the following graph types:
Stacked Bar
Format
Pie Format
Line Format
For more information, see “Changing the OmniView graph type” on

page 465.

Toolbar
button
Data Display Displays the total number of events since the counters were last
Totals cleared. For more information, see “Exporting statistics” on
page 471.
Display Displays the average change per second over the last polling
Deltas/Sec period. For more information, see “Exporting statistics” on
page 471.
Display Peak Displays the peak change per second since the counters were last
Delta/Sec cleared. For more information, see “Exporting statistics” on
page 471.
Display Displays the average change per second over the last polling
Average period. For more information, see “Exporting statistics” on
Delta/Sec page 471.
Reset Peak Resets the peak values of all traces of a line graph to zero.
Values
Freeze Freezes the selected graph. OmniView continues to collect data
from the device, but does not update the graph with it.
Choose this command a second time to unfreeze the graph.
OmniView displays the data collected while the graph was frozen.
Set Number Sets the number of data points shown on line graphs.
of Points
Graphs Separate Separates the traces of a line graph into separate graphs within the
graph window. For more information, see “Viewing line graph traces
separately” on page 464.
Combine Combines the traces of the selected graphs. For more information,
see “Combining separated graph traces” on page 464.
Compare Opens saved statistics from a file so that you can compare them
with with current statistics. For more information, see “Comparing
Saved exported statistics with current statistics” on page 476.
Compare Opens the current statistics so that you can compare them with
with saved statistics from a file. For more information, see “Comparing
Current exported statistics with current statistics” on page 476.
Layout Vertical Tile Tiles separated graphs vertically. Has no effect on combined
graphs.
Arrange in Tiles separated graphs in a grid with the selected number of
Grid columns. Has no effect on combined graphs.
207569-F
Toolbar
button
Help Help Opens OmniView online Help.
Using Help Opens online Help on using the OmniView online Help.
About Displays version and copyright information for OmniView.
OmniView
Graph window toolbar
The Graph window toolbar provides quick access to commonly used graphing
commands. Table 87 describes the Graph window toolbar buttons.
Table 87 Graph window toolbar buttons
Toolbar
Description
button
Opens a graph saved as a file. For more information, see “Importing

statistics” on page 471.
Saves graph data to a file. For more information, see “Exporting statistics”
on page 471.
Closes the graph window.
Displays the graph legend. For more information, see “Applying or

removing a graph legend” on page 466.
Rotates the selected graph by transposing the x and y axes. For more
information, see “Rotating line or bar graphs” on page 465.
For bar and pie graphs, changes the way the bars or slices are grouped.
For more information, see “Regrouping bar or pie graphs” on page 465.
Displays the graph summary table.

Table 87 Graph window toolbar buttons (continued)
Toolbar
Description
button
Selects one of the following graph types:
Bar
Stacked bar
Pie
Line
For more information, see “Changing the OmniView graph type” on

page 465.
Provides three predefined scale settings: 50%, 100%, and 200%. The
scale is manually entered as a value greater than 0 up to 200%. For more
information, see “Changing the OmniView graph scale” on page 467.
Enables and disables the zoom in. For more information, see “Enlarging
and shrinking the graph with zoom” on page 467.
Zooms out to the previous view. For more information, see “Enlarging and
shrinking the graph with zoom” on page 467.
Zooms out to the original view. For more information, see “Enlarging and
shrinking the graph with zoom” on page 467.
Parts of a graph
OmniView places a graph in a pane within a separate graph window, or within the
monitor pane of the OmniView window. Figure 143 shows the parts of an
OmniView graph.
207569-F
Figure 143 OmniView graph parts
Graph banner
Graph legend
Graph trace
Statistics table
Table 88 describes the parts of an OmniView graph.
Table 88 Parts of an OmniView graph
Part Description
Graph banner Displays information about the statistics being graphed.

Graph trace May be any of the following graph types:
• Line
• Bar
• Stacked bar
• Pie
Graph legend Shows which colors match the parameters being graphed.
Statistics table Displays information for the parameters being graphed.
Working with OmniView

The following sections describe how to use OmniView to collect network
statistics:
• “Working with network resources‚” next.

• “Working with existing statistics panes” on page 432.

• “Working with custom statistics panes” on page 455.

• “Working with graphics” on page 462.
• “Importing and exporting statistics” on page 470.
• “Customizing OmniView” on page 476.
• “Working with unsupported devices and agents” on page 482
• “Working with RMON and SMON” on page 484
• “Using OmniView for protocol visualization” on page 488
Working with network resources
The following sections describe how to work with network resources. Information
in this section organized as follows:
• “Browsing resources with the navigation pane‚” next

• “Adding a network resource to the navigation pane” on page 425
• “Finding network resources” on page 428
• “Listing monitored resources and elements” on page 430
• “Using workspaces to save and restore views” on page 430
Browsing resources with the navigation pane
After you start OmniView, you can use the navigation pane to view the elements
of a network resource. You can also use the navigation pane to view the network
resources to which the currently displayed elements belong. For example, if the
highest network resource displayed is a router, you can view the WAN (if any) to
which the router belongs.
To open an element of a network resource:
Click the plus sign or dot next to the resource or element.
OmniView displays the elements that belong to that element or resource.
207569-F
To browse to the next resource above those currently displayed:
Right-click the highest element in the hierarchy and choose Belongs to from
the shortcut menu.
OmniView adds the next higher resource to the navigation pane.
Adding a network resource to the navigation pane
If you started OmniView without specifying any options in the command line, the
Specify Entity to be Monitored dialog box opens (Figure 144), where you specify
the device to be monitored. If you click Cancel, OmniView starts without any
devices in the navigation pane.
Note: The OmniView specify entity to be monitored dialog box opens

when OmniView is started from the command line and no options are
specified. If the OmniView window is already open, and you click
File >Monitor New Entity, the Monitor New Entity dialog box opens.
Both dialog boxes provide the same options.

Figure 144 OmniView specify entity to be monitored dialog box
The following procedure describes how to specify an entity to be monitored.
To add a network resource (WAN, ELAN, VLAN, device, segment, or subnet) that
does not yet appear in the OmniView navigation pane:

• If the OmniView specify entity to be monitored dialog box opens, go to
step 2.
• If the OmniView window is already opened, from the OmniView menu
bar, choose File > Monitor New Entity.
The Monitor New Entity dialog box (Figure 145) opens.
207569-F
Figure 145 Monitor New Entity dialog box
2 Specify the entity to be monitored:

a Click IP Address/Hostname to specify the object by its IP address, or
click Database entity name to specify the device by its object name in the
Optivity database.
b (Optional) If you specify the object by its IP address, you can enter the
read and write community strings in the text boxes.
You only need to enter the community strings if the device uses
community strings that are not specified in either the Community Strings
Editor or by your network management platform software.
3 (Optional) If you want to initiate SNMPv3 communication with the device, do
the following:
Note: Entering the authentication and privacy key and engine ID does not
ensure SNMPv3 conversation. To enable SNMPv3 conversation, the
device must support SNMPv3 and the user must be authenticated in the
community strings database and on the device.
• Type an authentication key in the Authentication Key text box.

• Type a privacy key in the Privacy Key text box.

In this case, the authentication and privacy key takes precedence over the
values retrieved from the community strings database for the specified IP
address.
• Type the engine ID of the device in the Engine ID text box.
4 Click OK.
When OmniView establishes communication with specified object, it adds the
object to the OmniView navigation pane.
Note: When you add a new resource to the navigation pane, OmniView
does not reconcile the hierarchical relationship between the resources.
For example, if you add a WAN to a navigation pane that already
contains one of the routers in the WAN, both resources are shown at the
same level.
Finding network resources
OmniView lets you quickly find any of the following network resources within the
navigation pane using the Find command:
• Devices
• Subnets
• Segments
• ELANs
• VLANs
207569-F
To locate a network element in the navigation pane of the OmniView window:
1 From the OmniView menu bar, choose Edit > Find Network Element.
The Find Network Element dialog box (Figure 146) opens.
Figure 146 Find Network Element dialog box
2 Enter the object name or IP address or DNS name of the resource to be found.
3 Click Find.
OmniView highlights the first matching occurrence of the IP address or object
name.
If there are no matches, the words “No Match Found” appear on the Find
network Element dialog box. Try entering a different name for the resource.
If OmniView finds and highlights a resource that is not the one you are
looking for, click Find Next until it locates the correct resource.

Listing monitored resources and elements
To view a list of the network resources and elements currently being monitored by
OmniView:
From the OmniView menu bar, choose Network Element > List Monitored
Entities.
A submenu opens, showing all the resources and elements that OmniView is
currently monitoring.
Using workspaces to save and restore views
A workspace is a particular arrangement of network elements and statistics panes

within the OmniView window.
Saving a workspace creates a file that contains a record of that particular

arrangement of panes, tables, and graphs. A workspace file is saved on the
computer where the OmniView client software is running. By saving workspaces
and then reloading them at a later time, you can easily switch between the most
useful views of how your network is performing.
Note: Before you load a workspace, make sure that there are no open
statistics panes that you do not want closed. When you load a new
workspace, all of the statistics panes that were open prior to the loading
of the workspace are closed.
To save a workspace:
1 If you have not already done so, open all of the statistics panes and graph
panes that you want to appear in the saved workspace.
For more information about opening statistics and graph panes, see “Viewing
statistics for a network element” on page 433 and “Viewing statistics
graphically” on page 463.
2 From the OmniView menu bar, choose File > Save Workspace.
207569-F
The Select the file to save to dialog box (Figure 147) opens.
Figure 147 Select the file to save to dialog box
3 Select the directory and filename for the workspace file.

4 Click Save.
To load a workspace:
1 Make sure that there are no open statistics panes that you do not want closed.
If there are, consider either saving the current workspace, or starting a
separate OmniView session for the workspace you want to load.
2 From the OmniView menu bar, choose File > Load Workspace.
The Select the file which contains the workspace configuration dialog box
(Figure 148) opens.

Figure 148 Select the file which contains the workspace configuration dialog box
3 Choose the file containing the workspace you want to load.

4 Click Open.
Working with existing statistics panes
This following sections describe how to use the statistic pane feature to view
information about devices in your network:
• “Viewing statistics for a network element‚” next

• “Viewing statistics with bar indicators” on page 434
• “Reading bar indicators” on page 434
• “Understanding statistics types” on page 435
• “Sorting a table column” on page 441
• “Minimizing and maximizing statistics panes” on page 442
• “Changing the statistic types displayed” on page 444
• “Selecting table cells for graphing or exporting” on page 444
• “Reordering columns” on page 445
• “Setting polling parameters” on page 446
• “Closing a statistics pane” on page 447
• “Viewing information about MIB objects” on page 448
207569-F
Viewing statistics for a network element
OmniView displays statistics for network elements in panes that you open in the
monitor pane of the OmniView window.
To open a statistics pane for a network element:
1 In the navigation pane, select the network element for which you want to view
statistics.
Figure 149 shows the Memory Utilization Table element selected.
Figure 149 Memory Utilization Table element
Note: If the resource for which you want to view statistics does not
appear in the navigation pane, see “Adding a network resource to the
navigation pane” on page 425 to add the resource.

• Double-click the network element.
• Right-click the network element and choose Open Pane from the shortcut
menu.
• Click the network element and choose File > OpenPane.
OmniView opens a statistics pane for the selected network element in the
monitor pane.

Viewing statistics with bar indicators
OmniView lets you compare statistics by providing bar indicators you can include
in the columns of statistics panes. Figure 150 shows bar indicators.
Figure 150 Statistics shown by bar indicators
To add bar indicators to a column of a statistics pane:
• Right-click anywhere within the column where you want to view bar
indicators and choose Show Bar Indicator from the shortcut menu.
• Click anywhere within the column where you want to view bar indicators
and choose Pane > Show Bar Indicator.
Repeating either menu selection turns the bar indicators off again.
Note: If the bar indicators appear for absolute columns but not
percentage columns, check the settings on the Tables tab of the
Preferences dialog box. For more information, see “Configuring how
OmniView displays bar indicators” on page 479.
Reading bar indicators
The following sections describe the two types of bar indicators in OmniView:
• Relative bar indicators

• Percentage bar indicators
207569-F
Relative bar indicators, such as those shown in Figure 151, show the relationships
between the values in the various rows. The greatest value has a full-scale bar
indicator. All other values have bar indicators that show the relationship between
that value and the greatest value.
Figure 151 Relative bar indicators
Percentage bar indicators show the relationship between the value and 100%.
For example, a value of 100% is shown as a full-scale bar indicator. A value of

50% is shown as a half-scale bar indicator.
Note: If the bar indicators appear for absolute columns but not
percentage columns, check the settings on the Tables tab of the
Preferences dialog box. For more information, see “Configuring how
OmniView displays bar indicators” on page 479.
Understanding statistics types
OmniView displays four types of statistics in the statistics panes. Absolute

columns are those that display statistics in terms of numbers of events. Percentage
columns are those that display statistics in terms of percentages.

Table 89 describes the statistics types.
Table 89 Statistics types
Selection Absolute columns Percentage columns
Display Display the total number of events Current percentage value.

Totals since the counters were last cleared.
Display Display the average change per Current percentage value.
Deltas/Sec second over the last polling period.
Display Peak Display the peak change per second Display the peak value since
Deltas/Sec since the counters were last cleared. the counters were last cleared.
Display Average Display the average change per Display the average value
Deltas/Sec second over the last polling period. since the counters were last
cleared.
Understanding network utilization
OmniView lets you view network utilization statistics in all for points where
traffic leaves or enters a network segment. Knowing which interfaces have the
highest utilization might identify a need for more (or less) capacity. Highly
utilized interfaces can also represent potential bottlenecks. Under-utilized network
segments may represent potential cost savings. Balancing traffic between
over- and under-utilized segments can dramatically improve your network
performance.
OmniView lets you do the following:
• View network utilization for all leaf element activity panes for the following
node elements:
— Ports-by-slot
— Ports-by-backplane
— Segments
— Stations-by-DCE/DCM
• View network utilization for:
— Devices that support half-duplex operation
See “Viewing network utilization for half-duplex operation‚” next for
more information.
— Devices that support full-duplex operation
207569-F
See “Viewing network utilization for full-duplex operation” on page 438

Viewing network utilization for half-duplex operation
OmniView lets you view network utilization for devices that only support half-
duplex operation. You can view network utilization for all leaf element activity
panes for the following node elements:
• Ports-by-slot
• Ports-by-backplane
• Segments
• Stations-by-DCE/DCM
To view network utilization for a device operating in half-duplex mode:
1 In the navigation pane, double-click a supported network element.

The network element expands to show either leaf elements or other node
elements. Figure 152 shows the Ports-by-Slot network element expanded.
Figure 152 Ports-by-Slot, Slot 2 network element, and Activity leaf selected

• If the network element expanded to list leaf elements, double-click a leaf
element.
• If the network element expanded to list additional node elements, expand
a node element, and double-click a leaf element.
OmniView opens a statistics pane for the selected leaf element in the monitor
pane.

Figure 153 shows a network utilization value of 0% for slot 2, port 2. A value
of 0% indicates that the network utilization data is invalid. OmniView
displays invalid network utilization data on the first poll.
Figure 153 Invalid network utilization data on the first poll
Invalid network
utilization data
OmniView displays valid network utilization data for slot 2, port 2 on the second
poll (Figure 154).
Figure 154 Valid network utilization data for slot 2, port2 on the second poll
Valid network
utilization data
Viewing network utilization for full-duplex operation
OmniView lets you view network utilization for devices that support both half-
and full-duplex operation. In this case, two additional columns are added to the
statistics table: one for full-duplex inbound data and one for full-duplex outbound
data.
If a device supports full-duplex operation, but is configured to operate in

half-duplex mode, or as a result of auto negotiation, is placed in half-duplex mode,
the full-duplex inbound and outbound columns are disabled.
207569-F
Table 90 describes how OmniView displays network utilization data in the

statistics table for devices that support both half and full-duplex operation.
Table 90 How full-duplex devices displays network utilization data
Full-duplex Full-duplex
Slot-port Duplex Half-duplex
inbound outbound
1 Half 2% 0% 0%
2 Full 0% 2% 5%
3 Unknown 0% 0% 0%
You can view network utilization for all leaf element activity panes for the
following node elements:
• Ports-by-slot
• Ports-by-backplane
• Segments
• Stations-by-DCE/DCM
To view network utilization for a device operating in full-duplex mode:
1 In the navigation pane, double-click a supported network element.

The network element expands to show either leaf elements or other node
elements. Figure 155 shows the Ports-by-Slot network element expanded.
Figure 155 Ports-by-Slot, Slot 1 network element, and Activity leaf selected


• If the network element expanded to list leaf elements, double-click a leaf
element.
• If the network element expanded to list additional node elements, expand
a node element, and double-click a leaf element.
OmniView opens a statistics pane for the selected leaf element in the monitor
pane.
Figure 156 shows network utilization columns for half-duplex, full-duplex

inbound, and full-duplex outbound. All three columns display an invalid
network utilization value of 0% for slot 1, port 1. A value of 0% indicates that
the network utilization data is invalid. OmniView displays invalid network
utilization data on the first poll.
Figure 156 Invalid full-duplex network utilization data on the first poll
Half-duplex column is Invalid network

disabled in full-duplex utilization data
mode
OmniView displays valid full-duplex network utilization data for slot 1, port 1 on
the second poll (Figure 157).
207569-F
Figure 157 Valid network utilization data on the second poll
Half-duplex column is Valid network

disabled in full-duplex utilization data
mode
Sorting a table column
OmniView lets you sort the columns of any statistics table. You can sort columns
in either ascending or descending order.
To sort a table column into descending order:
Click the column header, as shown in Figure 158.
Figure 158 Sorting column in descending order

To sort the column into ascending order:.
Click the column header again.
Note: You can also configure OmniView so that it resorts the pane in the
order you want after every polling cycle. For more information, see
“Configuring how OmniView coordinates sorting and polling” on
page 478.
Minimizing and maximizing statistics panes
When you are not viewing a particular table in the monitor pane, you can
minimize it to save space and reduce clutter in the monitor pane.
To minimize a single statistics pane:
Double-click the title bar of the pane, as shown in Figure 159.
Figure 159 Minimizing a single statistics by clicking in the title bar
The statistics pane collapses so that only the title bar at the top is visible.
207569-F
To maximize a statistics pane:
Double-click the table title bar, as shown in Figure 160.
Figure 160 Maximizing the statistics pane
The statistics pane expands so that the entire pane is visible.
To minimize all of the statistics panes for a network resource:.
Click the resource icon in the left margin of the monitor pane, as shown in
Figure 161.
Figure 161 Clicking the resource icon to minimize all statistics panes
When you click on the icon again, all of the panes for the resource are
expanded as shown in Figure 162.
Figure 162 Example of expanding resource icon panes

Changing the statistic types displayed
OmniView lets you change the types of statistics displayed in statistics panes to
any of the following types:
• Totals
• Deltas/Sec
• Peak Deltas/Sec
• Avg Deltas/Sec
To change the statistics types for a single pane:
Right-click anywhere within the pane and choose the statistics display type
To change the statistics types for all panes:
From the OmniView menu bar, choose Pane > All Panes > [statistics type].
For more information, see “Understanding statistics types” on page 435.
Selecting table cells for graphing or exporting
You can select table cells for graphing or exporting using any of the following
methods:
To select an individual cell:
Click the cell.
207569-F
To select a whole column:
Click the column header as shown in Figure 163.
Figure 163 Selecting a whole column
To select multiple adjacent cells:
Drag vertically, horizontally, or diagonally as shown in Figure 164.
Figure 164 Selecting multiple adjacent cells
To select multiple cells that are not adjacent:
[Shift]+click the individual cells.
Reordering columns
To reorder the columns within a statistics pane:
Drag column headers left or right to new locations as shown in Figure 165.

Figure 165 Reordering statistics pane columns
The columns follow their headers to the new locations.
Setting polling parameters
OmniView lets you specify how often OmniView polls devices for the information
displayed in statistics panes.
Note: Nortel Networks recommends that you use polling intervals of no

shorter than about 10 seconds. At shorter polling intervals the extra
SNMP traffic that results from the increased polling may be disruptive,
and may also skew the performance statistics.
To set the polling interval for a single statistics pane:
1 Select the pane by clicking anywhere on the pane.

2 From the OmniView menu bar, choose Pane > Set Polling.
The Polling Parameters dialog box (Figure 166) opens.
207569-F
Figure 166 Polling Parameters dialog box
3 Enter a polling interval and click OK.
To set the polling interval for all statistics panes:
1 From the OmniView menu bar, choose Pane > Set Polling for All.
The Polling Parameters dialog box (Figure 166 on page 447) opens.
2 Enter a polling interval and click OK.
Closing a statistics pane
Closing a statistics pane removes it from the monitor pane.
To close a statistics pane, do one of the following:
• In the monitor pane, click anywhere in the statistics pane and from the
OmniView menu bar choose Pane > Close Pane.
• In the monitor pane, right-click anywhere in the statistics pane and from the
shortcut menu choose Close.
• In the navigation pane, select the network element for the statistics pane and
from the OmniView menu bar choose Pane > Close Pane.

• In the navigation pane, right-click the network element for the statistics pane
and from the shortcut menu choose Close Pane.
Viewing information about MIB objects
You can view text descriptions of all of the MIB objects displayed in a statistics
pane.
To view descriptions of MIB objects:
1 Select the statistics pane for which you want to view MIB object descriptions.
• Right-click anywhere in the pane and from the shortcut menu choose MIB
Help.
• From the OmniView menu bar, choose Help > MIB Help.
The MIB Help window opens. The MIB Help window displays text
descriptions of all of the MIB objects displayed in the statistics pane.
3 When you are done viewing the MIB Help, click OK.
Viewing statistics in a multi-device pane
The following sections describe how to use OmniView to view statistics for
multiple devices or entities in one pane and compare similar statistics. The
multi-device pane displays the IP address of and statistics for each device:
• “Understanding the conditions for viewing statistics‚” next

• “Opening a multi-device pane to view statistics” on page 451
• “Adding other network elements to an open multi-device pane” on page 454
• “Understanding the display formats” on page 449
Understanding the conditions for viewing statistics
The following conditions apply when you view the statistics for multiple devices
in one pane:
• Customization—The customization feature is not available.
207569-F
• MIB Help—In the multiple device pane, MIB Help is displayed for all the
MIB objects used for all the devices.
Table 91 describes the terms used to describe statistics in multiple device panes.
Table 91 Multiple device terminology
Term Description
Similar statistics Statistics that are comparable in terms of data type and meaning.
Data type Statistics from various devices are in a particular column and can be
any one of the following:
• All strings
• All integers
• All floats
• All percentages
and so forth.
Meaning Statistics in a particular column are from the same MIB object or a
comparable MIB object, or a similar expression calculation.
Understanding the display formats
OmniView uses the following display formats to organize statistical data:
• Intersection—The leaf elements for each device have identical statistic and
data types.
• Union—The leaf elements for each device have some statistics and data types
in common, but not all.
Figure 167 shows the intersection of statistical data. In this example, the statistics
columns and data types are identical for the module in slot 1 and the module in
slot 2.

Figure 167 Example of the intersection of statistical data
Figure 168 shows the union of statistical data. In this example, the data is
organized as follows:
• For the module in slot 2—The statistics columns and data types are identical,
but the same columns are blank for the module in slot 3.
• For the module in slot 3—The statistics columns and data types are identical,
but the columns are blank for the module in slot 2.
207569-F
Figure 168 Example of the union of statistical data
Opening a multi-device pane to view statistics
The are two methods available to view statistics for multiple devices in one pane:
• Open a multi-device pane—Described in this section.

• Add items to an open multi-device pane—For more information, see “Adding
other network elements to an open multi-device pane‚” next.
In the following scenario, there are no active panes for network elements for
which you want to view statistics.
To view statistics in a multi-device pane:
1 In the navigation pane, select the network element for a device for which you
want to view and compare statistics.
Figure 169 shows the SNMP InActivity element selected.

Figure 169 Multi-device element
2 In the navigation pane, [Ctrl]+click a similar network element for the second
device(s) for which you want to view and compare statistics.
Figure 170 shows the SNMP InActivity element selected for the second
device to be viewed in the multi-device pane.
207569-F
Figure 170 Network element for the second device
3 Right-click the last selection and choose Open pane from the shortcut menu.
If the network elements selected are similar statistics, the multi-device pane
opens. Figure 171 shows the statistics for the SNMP InActivity element for
two devices. The statistics are displayed in one multi-device pane.
Figure 171 Statistics displayed in a multi-device pane
If the network elements selected are not similar statistics, a Usage dialog box
opens, displaying an incompatibility message.

Adding other network elements to an open multi-device pane
To add the first network element to the multi-device pane:
Display the network element for the first device.
Figure 172 shows statistics for the first network element.
Figure 172 Network element displayed in active pane
For more information about viewing statistics for a network element, see
“Viewing statistics for a network element” on page 433.
To add additional network elements to the multi-device pane:
1 In the navigation pane, click the network element displayed in the active pane.
2 In the navigation pane, [Ctrl]+click a similar network element for the
device(s) for which you want to view and compare statistics.
3 Right-click the last selection and choose Open pane from the shortcut menu.
If the network elements selected are similar statistics, the multi-device pane
updates and displays statistics for the selected network elements. Figure 173
shows the updated multi-device pane.
207569-F
Figure 173 Updated multi-device showing statistics for added network elements
Working with custom statistics panes
The following sections describe how to customize statistics panes:
• “Creating a customized statistics pane‚” next

• “Customizing an existing pane” on page 457
• “Searching for a MIB object by name” on page 459
• “Creating a MIB expression for a custom statistics pane” on page 460
• “Validating a MIB object or MIB expression” on page 461
Note: You cannot customize multi-device panes.
Creating a customized statistics pane
OmniView lets you create custom statistics panes that show the statistics that you
need for a specific situation or network device.
Note: You can create custom panes only for network devices such as
hubs, switches, and routers. You cannot create custom panes for logical
resources such as subnets, segments, WANs, ELANs, or VLANs.
To add a custom statistics pane in OmniView:
1 From the OmniView menu bar, choose Pane > Define New Pane.
The Add Table dialog box (Figure 174) opens.

Figure 174 Add Table dialog box
2 Choose one of the following options:

• User [your user name]—Creates a new pane that only you can view.
• All Users—Creates a new pane that is available to all Optivity users.
3 Click OK.
The Add Pane wizard opens to the Pane title and initial poll interval prompt.
4 In the Pane Title box, replace the words “New Pane” with the pane title of
your choice.
5 In the Initial Poll Interval box, type the interval at which OmniView is to poll
the element for statistics.
6 Click OK.
The Column Names and MIB Expression prompt opens.
7 Click Add Row to add a new row to the Pane Contents box.
Each row in the Pane Contents box represents a column in the finished
statistics pane.
207569-F
8 In the MIB Expression cell of the new row, create a MIB expression.
A MIB expression consists of at least one MIB object, and may include
multiple MIB objects combined with mathematical operators. For more
information, see “Creating a MIB expression for a custom statistics pane” on
page 460.
9 In the Column Type cell, select either Float (floating point) or Percentage as
the column type.
10 In the Column Name cell, type a descriptive name for the column.
11 Repeat steps 7 through 10 to add other columns to the pane.
12 When you are done adding columns to the custom statistics pane, click Save.
Customizing an existing pane
OmniView lets you customize existing statistics panes so that they show the
statistics that you need for a specific situation or network resource.
Note: You can create custom panes only for network devices such as
hubs, switches, and routers. You cannot create custom panes for
non-hardware resources such as subnets, segments, WANs, ELANs, or
VLANs.
To customize an existing statistics pane in OmniView:
1 In the navigation pane, select the statistics pane that you want to customize.
2 From the OmniView menu bar, choose Pane > Customize.
The Modify Table dialog box (Figure 175) opens.

Figure 175 Modify Table dialog box
3 Choose one of the following options:

• User [your user name]—Creates a new pane that only you can view.
• All Users—Creates a new pane that is available to all Optivity users.
4 Click OK.
The Add Pane wizard opens to the Pane title and initial poll interval prompt.
5 In the Pane Title box, change the pane title if necessary.

6 In the Initial Poll Interval box, type the interval at which OmniView is to poll
the element for statistics.
7 Click OK.
The Column Names and MIB Expressions prompt opens.
8 In the Pane Contents box, modify the column names, column types, and MIB
expressions as necessary.
See “Creating a MIB expression for a custom statistics pane” on page 460”
9 When you are done customizing the statistics pane, click Save.
207569-F
Searching for a MIB object by name
When you are creating a new or custom statistics pane, OmniView lets you search
the MIB tree based on the first few characters of the MIB object name. OmniView
finds all of the MIB objects supported by the currently selected device that start
with the specified characters.
To search for a MIB object by name:
1 On the Column Names and MIB expressions prompt, enter the first few
characters of the MIB object in the text box at the top of the MIB tree as
shown in Figure 176.
Figure 176 Searching for a MIB object by name
2 Press [Enter].
OmniView displays a list of MIB objects that start with the specified
characters as shown in Figure 177.
Figure 177 Example of list of MIB objects
3 Click a MIB object on the list to select it.

OmniView expands the MIB tree to display the selected MIB object.

Creating a MIB expression for a custom statistics pane
When you are creating a custom statistics pane, OmniView lets you create MIB
expressions consisting of one or more MIB objects combined with mathematical
operators.
To create a MIB expression:
1 If you have not already done so, in the Column Names and MIB expressions
prompt click New Column.
For more information, see “Creating a customized statistics pane” on
page 455 or “Customizing an existing pane” on page 457.
2 In the Pane Contents list of the Enter Column Names and MIB Expressions
wizard prompt, double-click in a table cell in the MIB Expression column to
place the blinking text cursor in the cell.
3 In the MIB tree, navigate to the first MIB object to appear in the MIB
expression.
You can also search for MIB objects by name. For more information, see
“Searching for a MIB object by name” on page 459.
4 Use the menu below the MIB tree to choose either the absolute or the delta
version of the MIB object.
5 Click the MIB object.
OmniView adds the MIB object to the cell.
6 Click in the cell to place the text cursor in the cell.

7 Use the arrow keys to move the text cursor to the beginning or end of the MIB
object name.
8 Click a mathematical operator on the Enter Column Names and MIB
Expressions prompt, or use the /, *, -, or + keys on your keyboard.
9 In the MIB tree, click once on the next MIB object to appear in the MIB
expression.
OmniView adds the MIB object to the cell.
207569-F
10 Repeat steps 3 through 9 to add other MIB objects or mathematical operators

to the MIB expression.
You can also add spaces to the expression to make it more readable.
11 Double-check the MIB expression by moving the text cursor from the
beginning of the MIB expression to the end, reviewing the expression as it
scrolls past.
12 Test the MIB expression on the currently selected device by clicking Validate.
For more information, see “Validating a MIB object or MIB expression‚”
next.
Validating a MIB object or MIB expression
When you create MIB expressions for new or custom statistics panes, OmniView
lets you check whether a MIB expression works properly for the currently
selected device. OmniView tests the expression by performing SNMP GET
operations on all of the MIB objects in the expression, and then evaluating the
expression.
To validate a MIB expression:
1 On the Column Names and MIB expressions prompt, select a row in the Pane
Contents table.
2 Click Validate.
The Validate Expression dialog box (Figure 178) opens, displaying the results
of the validation.

Figure 178 Validate Expression dialog box
3 Review the results to check whether they are accurate and valid for the
expression.
4 Click OK.
Working with graphics
The following sections describe how OmniView lets you work with graphs:
• “Viewing line graph traces separately‚” next

• “Combining separated graph traces” on page 464
• “Rotating line or bar graphs” on page 465
• “Changing the OmniView graph type” on page 465
• “Regrouping bar or pie graphs” on page 465
• “Applying or removing a graph legend” on page 466
• “Viewing graph values” on page 466
• “Viewing graphing symbols (line graph only)” on page 466
• “Changing the OmniView graph scale” on page 467
• “Enlarging and shrinking the graph with zoom” on page 467
• “Scrolling through the graph” on page 469
• “Displaying information about a data point” on page 469
207569-F
Viewing statistics graphically
OmniView lets you view statistics in the form of bar graphs, line graphs, or pie
graphs. You can add these graphs to the monitor pane of the OmniView window,
or you can open them in separate windows.
To add a graph to the monitor pane:
1 Select the table cells that you want to graph.

For more information, see “Selecting table cells for graphing or exporting” on
page 444.
2 From the OmniView menu bar, choose Graphs > [graph type] > Add to Main
Window.
Where [graph type] is any of the three graph types on the menu.
OmniView opens the graph inside a new graph pane in the OmniView monitor
pane.
To open a graph in a separate window:
1 Select the table cells that you want to graph.

page 444.

2 From the OmniView menu bar, choose Graphs > [graph type] > Create New
Graph Window.
where [graph type] is any of the three graph types on the menu.
OmniView opens the graph inside a new graph window.
Note: You can also click one of the graph buttons (Line, Bar, or Pie) to
view a statistics graph. The graph opens in either in the monitor pane or
in a separate window depending on the settings of the Charts tab of the
Preferences dialog box.
Viewing line graph traces separately

You can separate the traces of a line graph so that each of the traces appears on its
own graph. (This option only applies to graphs displayed in a separate graph
window.)
To separate the traces of a line graph:
From the Graph window menu bar, choose Graphs > Separate.
OmniView displays the traces of the line graph in separate panes of the graph
window.
Combining separated graph traces
After graph traces are separated, you can recombine the traces.
To combine the traces of a separated graph:
1 On the graph window, [Ctrl]+click each of the graph panes that you want to
combine.
2 From the graph window menu bar, choose Graphs > Combine.
OmniView combines the selected graph traces onto a single graph pane.
207569-F
Rotating line or bar graphs
You can rotate OmniView line and bar graphs by transposing the X and Y axes.
To rotate a line or bar graph:
1 Click or [Ctrl]+click the graph pane(s) you want to rotate to select them.
• Right-click on the graph and choose Rotate from the shortcut menu.
• From the graph window menu bar, choose Format > Rotate.
• On the graph window toolbar, click Rotate Graph.
OmniView rotates the graphs in the selected graph panes.
Changing the OmniView graph type
To change the type of an existing graph:
Right-click anywhere on the graph pane and choose one of the following
graph types from the shortcut menu:
• Bar Chart
• Stacked Bar Chart
• Line Chart
• Pie Chart
The graph changes to the selected type.
Regrouping bar or pie graphs
You can regroup bar and pie graphs to make it easier to compare statistics.
To regroup a pie or bar graph, do one of the following:
• Right-click the graph and choose Regroup from the shortcut menu.
• From the Graph window menu bar, choose Format > Regroup.
OmniView regroups the graph.
To redisplay the original grouping, repeat the procedure.

Applying or removing a graph legend
A graph legend describes which colors and symbols match the parameters that are
graphed.
To turn the graph legend on or off:
Right-click anywhere on the graph and choose Show Legend from the
shortcut menu.
Viewing graph values
For bar and pie graphs, Optivity can display the current value represented on the
graph, as shown in Figure 179.
Figure 179 Viewing bar and pie graphs
To display graph values:
Right-click the graph and choose Show Values from the shortcut menu.
Viewing graphing symbols (line graph only)
Graphing symbols show the locations of the data points on a line graph.
207569-F
To turn the graphing symbols on or off:
Right-click anywhere on the graph and choose Show Symbols from the
shortcut menu.
Changing the OmniView graph scale
The Toolbar Scale box lets you select from three predefined scales: 50%, 100%
(default), and 200%. You can also manually enter an integer value greater than 0
up to 200%. Scaling is effective for the X and Y axis for the line graph, but does
not apply to pie charts.
The following conditions apply:
• In the OmniView main window—The default scale value is effective for all
graphs. You can set a unique scale value for each graph.
• In the graph window—The scale is effective for each single graphic.
To change the scale for a new graph window:
• Click the Scale box and choose a predefined value.

• Click in the Scale box and enter a value.
To change the scale for all graphs added to the main window:
• Click the Scale box and choose a predefined value.

• Click in the Scale box and enter a value.
Enlarging and shrinking the graph with zoom
The zoom feature lets you enlarge or shrink specific areas in the line graph and bar
graph. The zoom in option is not applicable for the pie chart.

To enable or disable zoom in:
• On the OmniView Graph window toolbar, click Enable/Disable Zoom In.

• On OmniView main window toolbar, click enable/Disable zoom In.
• Right-click the graph, and choose Enable Zoom In from the shortcut
menu.
To enlarge an area of a graph with zoom:
1 Enable zoom in.

2 Drag an area of the graph to enlarge it.
3 Repeat step 2 to continue to enlarge the area.
To enlarge an area of a graph when zoom in is disabled:.
Press [Ctrl] and drag an area of the graph.
The area is enlarged.
To zoom out to the top (original) view:
• On the OmniView Graph window toolbar, click Zoom Out Top.

• On the OmniView main window toolbar, choose Zoom Out Top.
• Right-click on the graph, and choose Zoom Out to Top View from the
shortcut menu.
• Press “t.”
207569-F
To zoom out to the previous view:
• On the OmniView Graph window toolbar, click Zoom Out Previous.

• On the OmniView main window toolbar, choose Zoom Out Previous.
• Right-click on the graph, and choose Zoom Out to Previous View from
the shortcut menu.
• Press “o.”
Scrolling through the graph
You can scroll a graph using the arrow keys. The following stipulations apply for
scrolling a graph:
• You cannot scroll below zero (0) on the Y axis.

• You cannot scroll pie charts.
• The view is not shifted if a new data points arrives until the data point goes
beyond X-axis’s maximum boundary. If the line graph is zoomed in, new data
point additions will not shift the view at all.
Displaying information about a data point
OmniView lets you display information about a data point on the graph that you
are viewing.
To view information about a data point:.
Point to the data point on the graph that you are interested in.
Information about that data point is displayed.

Figure 180 shows the data and time value for a specific point on the graph.

Figure 180 Example of data and time value for a specific point on graph
Importing and exporting statistics
The following sections describe how to import and export statistics:
• “Saving statistics with print to file‚” next

• “Importing statistics” on page 471
• “Exporting statistics” on page 471
Saving statistics with print to file
OmniView lets you save statistics by printing all of the open panes to either
HTML or ASCII files. This feature lets you view saved statistics with any text
editor or Web browser. The OmniView Print to File feature also lets you configure
OmniView to periodically overwrite the file with the latest statistics.
Note: The Print to File feature saves the statistics displayed in all open
statistics panes, even if the panes are minimized.
207569-F
To print the open panes to a file:
1 From the OmniView menu bar, choose File > Print Page to File.
The OmniView graph window opens.
2 Click to select the file type as either ASCII or HTML.

• Click Browse to browse to the file where you want to print the statistics.
• Enter the path and filename in the Filename text box.
4 If you want OmniView to periodically overwrite the file with the latest
statistics panes, mark the Periodically print to file check box and enter an
interval in the Interval text box.
5 Click OK.
Importing statistics
OmniView lets you import previously exported statistics into a graph window.
This feature lets you view statistics that you have previously exported to files.
To import statistics:

• From a Graph window menu bar, choose File > Open Graph Data.
• From the OmniView menu bar, choose File > Import Data.
A dialog box opens where you select a file.
2 Browse to the file to which you previously exported statistics, and click Open.
OmniView displays the imported statistics in a Graph window.
Exporting statistics
OmniView lets you export statistics to files so that you can review them later. You
can export statistics from either a statistics pane in the OmniView window, or
from a separate Graph window.

The following sections describe how to export statistics:
• “Exporting statistics from the OmniView window‚” next

• “Exporting statistics from a graph window” on page 475
Exporting statistics from the OmniView window
To export statistics from the OmniView window to a file:
1 If you have not already done so, open a statistics pane for the statistics you
want to export.
For more information about opening a statistics pane, see “Viewing statistics
for a network element” on page 433.
2 Select the cells containing the statistics to be exported.

page 444.
3 From the OmniView menu bar, choose File > Export Data.
The Export Data dialog box (Figure 181) opens.
207569-F
Figure 181 Example of Export Data dialog box
4 Confirm that the “Save the following data series” list contains the statistics to
be exported.
5 To change the list, click Modify Data Series.
The Choose Data Series to Save dialog box (Figure 182) opens.

Figure 182 Choose Data Series to Save dialog box example
6 Select whether to save only current statistics, or to also save ongoing

statistics:
• Click Save data currently stored in memory to export only those statistics
that are currently in memory.
• Click Save until [...] data points are collected, and enter a value for the
number of samples to collect to keep adding statistics to the file until the
specified number of samples have been collected.
7 If you are collecting ongoing statistics, select the sampling period for the data
collection.
• Click to clear the Use sampling period check box to use the default
polling period that is set on the OmniView toolbar.
• Select the Use sampling period of [...] check box and enter the number of
seconds between polling cycles to use a custom polling period.
8 Enter the path and name of the file to which you want the statistics exported,
or click Browse to browse to the file.
9 Click OK.
207569-F
Exporting statistics from a graph window
To export statistics from an OmniView Graph window to a file:
1 If you have not already done so, open a Graph window for the statistics you
want to export.
For more information about opening a Graph window, see “Viewing statistics
graphically” on page 463.
2 From the Graph window menu bar, choose File > Save Graph Data.
The Export Data dialog box (Figure 181 on page 473) opens.
3 Confirm that the “Save the following data series” list contains the statistics to
be exported.
4 To change the list, click Modify Data Series.
The Choose data series to save dialog box (Figure 182 on page 474) opens.
5 Select whether to save only current statistics, or to also save ongoing

statistics:
• Click Save data currently stored in memory to export only those statistics
that are currently in memory.
• Click Save until [...] data points are collected, and enter a value for the
number of samples to collect to keep adding statistics to the file until the
specified number of samples have been collected.
6 If you are collecting ongoing statistics, select the sampling period for the data
collection.
• Click to clear the Use sampling period check box to use the default
polling period that is set on the OmniView toolbar.
• Select the Use sampling period of [...] check box and enter the number of
seconds between polling cycles to use a custom polling period.
7 Enter the path and name of the file to which you want the statistics exported,
or click Browse to browse to the file.
8 Click OK.

Comparing exported statistics with current statistics
To compare exported statistics with current statistics:
1 If you have not already done so, import the saved statistics that you want to
compare with current statistics.
For more information, see “Importing statistics” on page 471.
2 In the Graph window containing the imported statistics, choose

Graphs > Compare with Current.
OmniView locates the current statistics that match the saved statistics and
displays both sets on the same graph.
Customizing OmniView
The following sections describe how to customize OmniView for your particular
application requirements:
• “Configuring how OmniView displays statistics panes‚” next

• “Configuring how OmniView displays resource icons” on page 477
• “Configuring how OmniView coordinates sorting and polling” on page 478
• “Configuring how OmniView displays MAC addresses” on page 479
• “Configuring how OmniView displays bar indicators” on page 479
• “Configuring how OmniView displays graphs” on page 480
• “Changing the look and feel of OmniView” on page 481
• “Hiding or displaying the toolbar or status bar” on page 482
Configuring how OmniView displays statistics panes
You can configure OmniView so that it displays statistics panes in one of two
ways:
• One at a time - Every time you open a new statistics pane, OmniView
automatically closes the previous pane. This configuration simplifies the
OmniView window when you only need to view one pane at a time.
207569-F
• Until manually closed - OmniView displays all opened panes until you
manually close them. This configuration lets you view many panes
simultaneously, making it easier to switch between panes.
To set how OmniView displays statistics panes:
1 From the OmniView menu bar, choose Options > Set Preferences.
The Preferences dialog box (Figure 183) opens with the General tab
displayed.
Figure 183 OmniView Preferences dialog box

• Select the Close all other open panes when a new pane is opened check
box to display only one statistics pane at a time
• Click to clear the Close all other open panes when a new pane is opened
check box to keep statistics panes open until you manually close them
3 Click OK.
Configuring how OmniView displays resource icons
You can configure OmniView to either hide or show the resource icons in the
monitor pane. These icons show you which statistics panes belong to each
network resource.

To set whether OmniView shows or hides the resource icons:
1 From the OmniView menu bar, choose Options > Preferences.

The Preferences dialog box (Figure 183 on page 477) opens with the General
tab displayed.

• Select the “Show Network Groupings” check box to show the network
resource icons
• Click to clear the “Show Network Groupings” check box to hide the
network resource icons
3 Click OK.
Configuring how OmniView coordinates sorting and polling
You can configure OmniView so that it sorts panes of statistics after every polling
cycle. When you do this, statistics are always displayed in the order of the desired
sort. However, when you have a combination of large panes and short polling
intervals, the statistics may change too fast for you to read them effectively.
To set how OmniView coordinates sorting and polling:

tab displayed.
2 Click the Tables tab to bring it to the front.

• Select the Sort Rows after every Poll check box to sort the statistics after
every polling cycle.
• Click to clear the Sort Rows after every Poll check box to sort the
columns only when you double-click on the column header.
4 Click OK.
207569-F
Configuring how OmniView displays MAC addresses
OmniView lets you view MAC addresses either in numerical form or with the first
half of the address converted into a vendor ID.
To select either the numerical or vendor ID forms:

tab displayed.

3 In the Show Vendor Name with MAC Address area, do one of the following:
• Select the Show Vendor Name with MAC Address check box to display
the first half of the address as a vendor ID
• Click to clear the Show Vendor Name with MAC Address check box to
show the MAC addresses numerically
4 Click OK.
Configuring how OmniView displays bar indicators
To configure the default settings for how OmniView displays bar indicators:

The Preference dialog box (Figure 183 on page 477) opens with the General
tab displayed.

3 Select or click to clear the Show bar indicators for percentage columns check
box.
4 To set the fill color for bar indicators, click Bar indicator fill color.
The Bar Indicator Fill Color dialog box (Figure 184) opens with the Swatches
tab displayed.

Figure 184 Bar Indicator Fill Color dialog box
5 Set the bar indicator fill color.

6 To set the border color for bar indicators, click Bar indicator border color.
The Choose Color dialog box (Figure 184) opens.
7 Set the bar indicator border color.

8 Click OK.
Configuring how OmniView displays graphs
To configure the default settings for how OmniView displays graphs:

tab displayed.
2 Click the Charts tab.
207569-F
3 To choose where graphs open, do one of the following:

• Select the Open Charts in Main Window check box to have OmniView
open graphs in the main window when you click on any of the Graph
toolbar buttons.
• Click to clear the Open Charts in Main Window check box to have
OmniView open graphs in separate graph windows when you click on any
of the Graph toolbar buttons.
4 To choose the axis type, do one of the following:
• Select the Transpose X and Y Axes check box to display line and bar
graphs with time as the vertical axis.
• Click to clear the Transpose X and Y Axes check box to display line and
bar graphs with time as the horizontal axis.
5 To include or omit summary tables, do one of the following:
• Select the Show stat table in line charts check box to have OmniView line
graphs include summary tables that display the data in tabular form.
• Click to clear the Show stat table in line charts check box to omit
summary tables from line graphs.
For more information, see “Parts of a graph” on page 422.
6 To include or omit numerical values, do one of the following:

• Select the Open values in bar charts check box to have OmniView bar
graphs include numerical values.
• Click to clear the Open values in bar charts check box to omit the
numerical values from bar graphs.
7 Click OK.
Changing the look and feel of OmniView
OmniView lets you change the look and feel of the OmniView window to best
match the operating system under which it is running.
To change the look and feel of the OmniView window:
1 From the OmniView menu bar, choose View > Look and feel.
The Look and Feel submenu opens.

Hiding or displaying the toolbar or status bar
To hide or display the OmniView toolbar:
From the OmniView menu bar, choose View > Display Toolbar.
To hide or display the OmniView status bar:
From the OmniView menu bar, choose View > Display Status bar.
Working with unsupported devices and agents
OmniView provides an error reporting function that identifies unsupported

devices, modules, and agents by providing the following:
• An Error log file that contains information about the unknown module,
device, or agent. The Error log file is created automatically. Only important
error conditions are logged to this file.
• Error messages including the IP address of the unknown module, device, or
agent.
The following sections describe how to work with unsupported devices and
agents:
• “Error messages for unsupported devices and agents‚” next

• “Understanding the error log file” on page 483
Error messages for unsupported devices and agents
For unsupported devices and agents, OmniView displays a detailed error message.
For example, the error message might indicate the sysObjId, and agent version
that OmniView failed to find matching information for in the database.
OmniView logs the following type of messages to the debug files:
• Error
207569-F
• Warning
• Debug
• Information
Understanding the error log file
The error file is located in the $LNMSHOME/log directory.
Figure 187 shows how information is formatted in the error log file.
Figure 185 OmniView log file format

<DATE>:<DB_OBJECT/IP (PID)>:<LOG_LEVEL><LOG STRING>
<(PID)>:<LOG_LEVEL><LOG STRING>
(when DB_OBJECT/IP unavailable at some point of the code)
where LOG_LEVEL is INFO or WARNING or ERROR
The characteristics of the error log file are:
• Created automatically. Once the file is created on a server machine, the most
current information is added to the end of the file.
• Only one instance of the file is created on the server machine. The file is
named omniview_user_name.log.
• The size is limited.
• No maintenance is required. Once the file reaches the size limit, old
information is over written (wrapped around).
• Error conditions such as the following are logged into the error log file:
— The application cannot proceed further
— Important data is missing from the topology, evomni, or MIB databases.
Figure 186 shows a warning message for an unknown device.

Figure 186 Unknown device error message
Figure 187 shows an example of an entry in debug log file for an unknown device.
Figure 187 Unsupported or unknown device omniview_root.log file
Working with RMON and SMON
OmniView probe support lets you view remote monitoring (RMON) and switch
monitoring (SMON) information about your frame switched network in tabular or
graphical format. Optivity NMS 10.3 integrates standard Management
Information Base (MIB) support for the following:
• RFC 1757—RMON1 (Ethernet) statistics and history

• RFC 1513—RMON1 (token ring extension) statistics and history
• RFC 2021—RMON2 user history and protocol distribution
• RFC 2613—SMON VLAN distribution and priority distribution
207569-F
You use OmniView to monitor and view RMON and SMON information derived
from a RMON or SMON device. The information displayed by OmniView comes
from SNMP agent software running on the network devices being monitored. The
specific types of information available in any particular view depends on the type
and version of the agent software in use.
The Optivity NMS 10.3 OmniView application (RMON and SMON) features are
similar to the MView application RMON and SMON features. Some of the major
differences between OmniView and MView are as follows:
• MView lets you view specific RMON and SMON information. For example,
if you are just interested in segment statistics, you can use MView to view that
information.
• MView lets you access RMON or SMON statistics faster, because you are
accessing a specific RMON or SMON group.
Working with RMON
To display RMON and SMON statistics for a device:
1 From the InfoCenter Resources folder, double-click Probes.

The probes folder opens. The IP address of probes and their sub type (RMON
or SMON) are listed.
2 Right-click a probe and choose Performance > OmniView.
The OmniView applications starts.
3 Expand the Interfaces node element.
The Interfaces node element hierarchy is displayed. Figure 188 illustrates an
expanded RMON tree in the OmniView navigational pane.

Figure 188 Example of an expanded RMON tree
Figure 189 illustrates an expanded SMON tree in the OmniView navigational

pane.
Figure 189 Example of an expanded SMON tree
207569-F
Working with RMON Statistics
To display RMON statistics:
1 Expand the RMON leaf element.

2 Expand a sub leaf element, such as the RMON statistic type.
3 Expand a RMON statistic type.
4 Double click Activity 1 and Activity 2.
For example, the Statistics Group is selected. Figure 190 illustrates statistics
displayed for the Statistics Group.
Figure 190 Example of a RMON Statistics Group
Working with SMON Statistics
To display SMON statistics:
Expand the SMON node element.
The SMON leaf elements are displayed. For example, the Priority
Distribution is selected. Figure 191 illustrates statistics displayed for the
Statistics Group.

Figure 191 Example of SMON statistics
Using OmniView for protocol visualization
OmniView works in conjunction with the AutoTopology Manager and InfoCenter

applications to monitor and display information about protocols running in a
network. The protocol visualization (PV) feature eliminates the boundaries
between LANs and WANs by providing an end-to-end management solution.
Protocol visualization lets you discover (AutoTopology Manager), manage

(InfoCenter), and display information about (OmniView) the protocols that are
running on the various devices in your network. Protocol visualization also lets
you know in which part of the network those protocols are running.
You use the AutoTopology Manager application to initiate any one of or all three
types of protocol discoveries:
• Unicast protocols (RIP2, OSPF)—Network devices running unicast protocols

are managed under the Unicast folder.
• Multicast protocols (DVRP, PIM, OSPF)—Network devices running
multicast protocols are managed under the Multicast folder.
207569-F
• Frame relay—Network devices running the Frame relay protocol are managed
under the WANs folder.
• VPLS—Network devices that are part of virtual private LAN services.
• IP-VPN—that are part of IP virtual private networks.
The following sections describe how to use OmniView protocol visualization

features:
• “Displaying protocol statistics for a RIP2 domain‚” next.

• “Displaying protocol statistics for an OSPF area object” on page 490.
• “Displaying protocol statistics for a RIP2 router in the unicast layer” on
page 492.
• “Displaying protocol statistics for an OSPF router in the unicast layer” on
page 493.
• “Displaying protocol statistics for an OSPF ABR link” on page 494.
• “Displaying protocol statistics for an OSPF ASBR link” on page 495
• “Displaying protocol statistics for a multicast session object” on page 496.
• “Displaying protocol statistics for a router in the multicast sessions layer” on
page 497.
• “Displaying protocol statistics for a router interface running frame relay” on
page 498.
• “Displaying protocol statistics for a PVC link in the frame relay layer” on
page 500
Note: Protocol visualization features are not available if OmniView is

started from the command line.
Displaying protocol statistics for a RIP2 domain
OmniView lets you display information about the protocols running in a RIP2
domain.
To display protocol statistics for a RIP2 domain:
1 In the InfoCenter Resources folder, double-click Unicast.

2 Right-click the RIP2 Domain and choose Performance > OmniView.
Note: OmniView is launched only if the routers are found that are related
to the RIP2 Domain. Otherwise a “No Routers found” message is
displayed in a message window.
The OmniView applications starts. The following objects are listed in the
navigation pane:
• Router objects that are part of the RIP2 domain
• Statistical panes for each router
Figure 192 illustrates an OmniView contents pane for the router objects that are
part of the RIP2 domain.
Figure 192 Protocol Visualization example for RIP2 domain routers
Displaying protocol statistics for an OSPF area object
OmniView lets you display protocol statistics for an OSPF area object.
To display protocol statistics for a OSPF area object:

2 Double-click an OSPF domain object.
207569-F
3 Right-click an OSPF area object and choose Performance > OmniView.
Note: OmniView will be launched only if the routers are found that are
related to the OSPF area object. Otherwise “No Routers found” message
is displayed in a message window.
contents pane:
• Router objects that are part of the OSPF area object
Figure 193 illustrates an OmniView contents pane listing router objects that are
part of the OSPF area object.
Figure 193 Display of OSPF area routers in the contents pane
Figure 194 shows the contents pane listing statistics for OmniView router objects
that are part of the OSPF area object.

Figure 194 Display of OSPF area routers in the monitor pane
Displaying protocol statistics for a RIP2 router in the unicast

layer
OmniView lets you display information about the protocols running on a RIP2
router in a unicast layer.
To display the protocol statistics for a RIP2 router in a unicast layer:

2 On the toolbar, click Unicast.
3 Double-click the RIP2 router.
The routing domain folder opens.
4 Right-click a router and choose Performance > OmniView.
contents pane:
• The router running RIP2
• Statistical panes displaying RIP information for the router
Note: OmniView displays the router and panes relevant to RIP2. If no

panes relevant to RIP2 are found, The message “No RIP2 panes found” is
displayed.
207569-F
Figure 195 illustrates an OmniView contents pane for a RIP2 router in a

unicast layer.
Figure 195 Example for a RIP2 router in a unicast layer
Displaying protocol statistics for an OSPF router in the unicast

layer
OmniView lets you display information about the protocols running on an OSPF
router in a unicast layer.
To display the protocol statistics for an OSPF router in a unicast layer:

A folder opens. RIP2 objects, OSPF area object, border routers, and links are
displayed.
2 On the toolbar, click Unicast.
3 Double-click the OSPF object.
A folder view opens containing the routers that are running OSPF protocols.
4 Right-click a router and choose Performance > OmniView.
The OmniView applications starts. OmniView displays the router and panes
relevant to OSPF.
Figure 196 illustrates an OmniView contents pane for an OSPF router in a
unicast layer.

Figure 196 Example of an OSPF router in a unicast layer
Displaying protocol statistics for an OSPF ABR link
OmniView lets you display protocol statistics for an OSPF ABR link. The ABR
link object provides two navigational items:
• Link information, for example the OSPF cost, interface index, and so forth.
• Statistical information, for example inOctets and outOctets on the link
(interface).
To display the protocol statistics for an OSPF ABR link:

displayed.
2 Double-click the OSPF domain object.
A folder view opens containing OSPF domains, routers, and ABR and ASBR
objects.
3 Right-click an OSPF ABR link and choose Performance > OmniView.
The OmniView applications starts and displays protocol statistics for the
OSPF ABR link.
Figure 198 illustrates an OmniView navigational pane display for an OSPF
ABR link.
207569-F
Figure 197 Example of an OSPF ABR link in navigational pane
Figure 198 illustrates an OmniView monitor contents pane display for an

OSPF ABR link.
Figure 198 Example of an OSPF ABR link in contents pane
Displaying protocol statistics for an OSPF ASBR link
OmniView lets you display protocol statistics for an OSPF ASBR link.
To display the protocol statistics for an OSPF ASBR link:

displayed.
2 Right-click an OSPF ASBR link and choose Performance > OmniView.

The OmniView applications starts and displays protocol statistics for the
OSPF ASBR link. The OSPF ASBR link object provides three items:
• Link information, for example the OSPF cost, interface index, protocol on
the other end (for example RIP2), and so forth.
• Statistical information, for example inOctets and outOctets on that link
(interface)
• Imported routes summary
Figure 199 illustrates an OmniView contents pane for an OSPF ABR link.
Figure 199 Example of protocol statistics of an OSPF ASBR link
Displaying protocol statistics for a multicast session object
OmniView lets you display protocol statistics for a multicast session object. You
can monitor multicast protocols such as:
• Distance vector multicast routing protocol (DVMRP)

• Protocol independent multicast (PIM)
• Internet group management protocol (IGMP)
To display the protocol statistics for a multicast session object:
1 In the InfoCenter Resources folder, double-click Multicast.

The multicast folder opens. Network devices that are running multicast
session protocols are displayed.
2 Right-click a multicast object and choose Performance > OmniView.
The OmniView applications starts and displays protocol statistics containing
the following information:
• Router objects that are part of the session object
207569-F
• Statistical panes for the router running multicast protocols
Note: If the system does not find any routers that are part of Session
object, the system will displays an information window with a message
“No Routers Found” and OmniView is not launched.
Figure 200 illustrates an OmniView contents pane for a multicast session.
Figure 200 Example of a multicast session
Displaying protocol statistics for a router in the multicast

sessions layer
OmniView lets you display protocol statistics for a router running multicast
session protocols. You can monitor multicast protocols such as:
• Distance Vector Multicast Routing Protocol (DVMRP)

• Protocol Independent Multicast (PIM)
• Internet Group Management Protocol (IGMP)
To display the protocol statistics for a router in a multicast session:
1 In the InfoCenter Resources folder, double-click Multicast.

The multicast folder opens, displaying routers, subnets, and router links: all
network entities that are running multicast session protocols are displayed.
2 On the toolbar, click Multicast.

3 Double click a multicast object

Multicast sessions objects are displayed.
4 Right-click a router object and choose Performance > OmniView.
The OmniView applications starts and displays multicast protocol statistics
containing the following information:
• Router objects that are part of the session object
• Statistical panes for the router running multicast protocols
Note: If the system does not find any panes relevant to Multicast
the system will display an information window “No Multicast
panes found.”
Figure 201 illustrates an OmniView contents pane for a router in a multicast

session layer.
Figure 201 Example of a router in a multicast session layer
Displaying protocol statistics for a router interface running

frame relay
OmniView lets you display protocol statistics for a router running frame relay on
one or more of the router’s interfaces.
To display the protocol statistics for a router interface in a frame relay layer:
1 In the InfoCenter Resources folder, double-click WAN.

The WANs folder opens, displaying the WAN objects.
2 On the toolbar, click Frame Relay.
207569-F
The network devices running frame relay and permanent virtual circuits
(PVCs) are displayed.
3 Right-click a router object and choose Performance > OmniView.
• Data link connection identifier (DLCI) table
• Frame relay (FR) circuit table
• Error table
Figure 203 illustrates an OmniView navigational pane display for a router
interface running frame relay.
Figure 202 OmniView navigational pane for router interface running frame
relay
Figure 203 illustrates an OmniView contents pane for a router interface

running frame relay.
Figure 203 OmniView contents pane for a router interface running frame relay

Displaying protocol statistics for a PVC link in the frame relay

layer
OmniView lets you display protocol statistics for a PVC link in a frame relay
layer.
To display the protocol statistics for a PVC link in a frame relay layer:
1 In the InfoCenter Resources folder, double-click WAN.

The WANs folder opens, displaying the WAN objects.
2 On the toolbar, click Frame Relay.
The network devices running frame relay and permanent virtual circuits
(PVCs) are displayed.
3 Right-click a PVC link and choose Performance > OmniView.
the following information.
• FR DLCI table
• FR circuit table
Figure 204 illustrates an OmniView navigation pane display for a PVC link in
frame relay.
Figure 204 OmniView navigation pane for a PCV link in frame relay
Figure 205 illustrates an OmniView contents pane display for a router

interface running frame relay.
207569-F
Figure 205 Contents pane for a router interface running frame relay
Displaying protocol statistics for an IP-VPN link
OmniView lets you display protocol statistics for an IP-VPN link.
To display the protocol statistics for an IP-VPN link:
1 In the InfoCenter Resources folder, double-click IP-VPN.

The IP-VPNs folder opens, displaying the IP-VPN objects.
2 Right-click an IP-VPN link and choose Performance > OmniView.
• Activity
• Interface
• Config
• VPN end devices
Working with MView

The following sections describe procedures that are unique to MView:
• “Monitoring RMON and SMON data types with MView‚” next

• “Viewing with port profile data with MView” on page 510

Monitoring RMON and SMON data types with MView
MView lets you monitor and analyze RMON and SMON data in tabular format.
You can view the data graphically and use the MView export feature to export the
data to a Microsoft Excel spreadsheet.
MView monitors information about a specific RMON MIB group. The data is
retrieved from an RMON or SMON device for a particular segment or selected
object. MView is launched from an RMON device, from an end node, or from a
link to a RMON device.
MView is started with the following guidelines:
• When MView is started against an RMON device, you are prompted to

specify the interface that is monitored.
• When MView is started against a link or an end node that is connected to a
RMON device, the system collects and displays data related to the selected
object.
For more information about starting MView, see “Starting OmniView and
MView” on page 398.
The following sections describe how MView monitors and displays information
about network management data types:
• “Segment statistics” on page 503

• “Performance history statistics” on page 504
• “Protocol distribution statistics” on page 508
• “Accounting statistics” on page 509
• “VLAN distribution statistics” on page 509
• “Priority distribution statistics” on page 509
207569-F
Table 92 lists the network management data types and their associated template.
Table 92 Network management data types specified by the -Q option
Data type Data type template
Segment statistics segstat

Performance history perfhist
usrhist
Fault history faulthist
usrhist
Protocol distribution nprotdist
aprotdistm
Accounting usrhist
VLAN distribution vlandist
Priority distribution priodist
For more information about using the -Q option command to specify a data type
template when starting MView, see “Starting OmniView and MView” on
page 398.”
Segment statistics
MView lets you monitor and analyze Ethernet or token ring statistics for a
segment. MView uses the following utilization formula:
(delta_Pkts * 160 + delta_Octets * 8) / (delta_SysUpTime/

100) / If-Speed
Note: For the above utilization, the assumption is that the probe
interface speed is the speed of the monitored network. In case of port
mirroring, this assumption might not be correct.
Ethernet segment statistic table
Figure 206 illustrates an Ethernet segment statistics table.

Figure 206 Ethernet segment statistics table
Token ring segment statistics table
Figure 207 illustrates an token ring segment statistics table.
Figure 207 Token ring segment statistics table
For more information about starting MView to monitor segment statistics, see
“Starting OmniView and MView” on page 398.
Performance history statistics
MView lets you monitor performance history for your network. You can collect
and analyze information for the following:
• RMON1 history group

• RMON2 userHistory group (if the RMON device supports RMON2)
207569-F
You must preconfigure the software to display data for the History or usrHistory
table. An alert dialog is displayed if the software is not configured to display data
for the History or usrHistory data.
Note: MView does not provide features for configuring the History or
usrHistory control table.
In cases where multiple control entries exist for a specified interface, MView does
the following:
• First tries to retrieve the corresponding data specified by the control entry that
has the control owner as “monitor.”
• If the control entry does not exist, the MView retrieves the corresponding data
of the first control entry for that interface
The following sections describe the history statistics that MView supports:
• “Ethernet performance history table‚” next.

• “Token ring performance history table” on page 506.
• “Ethernet fault history table” on page 506.
• “Token ring fault history table” on page 507.
Note: The unit for utilization column is percent, not hundredths of a

percent as defined in the MIB.

Ethernet performance history table
Figure 208 illustrates an Ethernet performance history statistics table.
Figure 208 Ethernet performance history statistics table
Ethernet fault history table
Figure 209 illustrates an Ethernet fault history statistics table.
Figure 209 Ethernet fault history statistics table
Token ring performance history table
Figure 210 illustrates a token ring performance history statistics table.
Figure 210 Token ring performance history statistics table
207569-F
Token ring fault history table
Figure 211 illustrates a token ring fault history statistics table.
Figure 211 Token ring fault history statistics table
User history table
The data presented for usrHistory table depends on how you configured the
usrHistory group.
Figure 212 illustrates a user history statistics table.
Figure 212 usrHistory statistics table

Protocol distribution statistics
MView displays the data from protocol distribution group for the following layers:
• Network layer (NL)

• Application layer (AL)
Network layer (NL) protocol distribution table
Figure 213 illustrates a network layer protocol distribution table.
Figure 213 Network layer (NL) protocol distribution statistics table
Application layer (AL) protocol distribution table
Figure 214 illustrates the application layer protocol distribution table.
Figure 214 Application layer (AL) protocol distribution statistics table
207569-F
Accounting statistics
MView lets you monitor usrHistory data to show clients usage of network
resources. The accounting data listed in the accounting user history table provides
accounting information such as an application and network usage. The presented
data depends on how you have configured the usrHistory group.
Figure 215 illustrates the accounting user history table.
Figure 215 Accounting user history statistics table
VLAN distribution statistics
MView lets you monitor information about VLANs. Figure 216 illustrates a
VLAN distribution statistics table.
Figure 216 VLAN distribution statistics table
Priority distribution statistics
MView lets you monitor information about priority statistics data. Figure 217
illustrates a priority distribution table.

Figure 217 Priority distribution statistics table
Viewing with port profile data with MView
MView lets you view the profile of a link that connects between a layer 2 switch
and an end node. MView displays the switch’s IP address, the slot and port to
which the link is attached, and the Port Profile leaf element in the navigation pane.
The Port Profile attributes about the particular link characteristics are displayed in
the monitor pane.
MView displays the following port profile information:
• Auto negotiation setting of attached port (ON/OFF)

• Port Link Speed of attached port (10/100/1000)
• Duplex setting of attached port (Half/Full)
• MAC address on the end node
The actual information displayed depends on the MIB data MView receives about
the switch’s slot and port configuration.
To display a port profile for an end node link:
• From the Tools menu in InfoCenter, click Tools > Configuration >
PortProfile.
207569-F
• From the command line in a Windows or UNIX environment, specify the

-Q pprofile option and enter:
omniview -I 10.127.233.5 -X 1 -Q pprofile
The MView windows opens (see Figure 218) and displays the link’s port
profile in the monitor pane. For more information about optional
parameters, see “Starting OmniView and MView” on page 398.
Figure 218 Port profile information displayed in a MView window
Troubleshooting OmniView and MView

The following sections provide information that let you troubleshoot OmniView:
• “OmniView error messages‚” next

• “Resolving problems” on page 515
• “OmniView known problems” on page 517

OmniView error messages
Table 93 describes OmniView error messages and their meanings.
Table 93 OmniView error messages
Message Description
You must select at least 1 Select at least one data series to export.
data series to export.
Unable to print to file: OmniView is unable to print to the file. Possible
<filename> reasons include:
• Inadequate write permission
• Invalid directory name
• Inadequate disk space
You do not have access The Optivity NMS Access Control feature is
permissions to [action]. enabled, and you do not have the appropriate
Check with your Optivity permission tokens to perform the action.
administrator
You do not have access to You do not have access to the file system. Most
the file system. likely to occur in applet mode.
File Not Found: <file Enter a valid file name.

name>
The cells selected are not You can only graph table cells that contain
chartable. Only numbers numerical values.
can be charted.
You cannot mix percentage You can only graph cells of the same type
type cells with non (percentage or absolute) on the same graph.
percentage type cells.
You do not have access You do not have adequate access permission to
permissions to modify customize or create new statistics panes. Check
panes. with an Optivity administrator regarding
OmniView configuration access.
permissions to add a new create new statistics panes for all Optivity NMS
pane for all users. Check users. Check with an Optivity administrator
with your Optivity regarding OmniView configuration access.
Administrator.
permissions to add a new create new statistics panes. Check with an
pane. Check with your Optivity administrator regarding OmniView
Optivity Administrator. configuration access.
207569-F
Table 93 OmniView error messages (continued)
Message Description
No access permissions for You do not have adequate access permission to

deleting of a customized delete custom statistics panes for all users.
all user pane Check with an Optivity administrator regarding
deleting of a customized delete custom statistics panes for all users.
user pane Check with an Optivity administrator regarding
Timed out waiting for The OmniView server is not responding.
OmniView Server
Invalid IP address. Enter a valid IP address.
Invalid database name. Enter a valid database name.
The server has The OmniView server has encountered a fatal
unexpectedly error. Check with an Optivity Administrator.
terminated the connection.
Unable to Delete The OmniView server could not delete the pane
from the database.
Unable to open pane. OmniView encountered an error trying to open
the statistics pane.
OmniView use OmniView. Check with an Optivity
administrator regarding OmniView configuration
access.
There was an error There was a problem monitoring the object.
monitoring <> Some or all Check the community strings and connectivity. If
of the panes have not been the object is an Optivity database name, check
opened that it is still in the database.
The hours must be 0 or Enter a number of hours greater than 0.

greater.
The minutes must be Enter a number of minutes from 0 through 59.
between 0 and 59.
The seconds must be Enter a number of seconds from 0 through 59.
between 0 and 59.
The data points field must Enter a valid number of data points.
contain a positive
integer.

Table 93 OmniView error messages (continued)
Message Description
You must enter the Enter a valid filename.

filename you wish to print
to.
Interval must be at least Enter a value of 1 or greater for the interval.
1.
Not a valid MIB: <MIB Enter a valid MIB name.
name>
Shouldn't mix numbers and You can only build MIB expressions using
non-numbers objects of the same type. For example, you
cannot mix numeric objects with text objects.
Unable to retrieve the OmniView could not retrieve values for the
following MIBs: specified MIB objects. Check that the MIB
<MID_object_name> expression is valid for the currently selected
device.
Unable to export to file: OmniView was unable to write data to the file.
<filename> Check that the file name is valid.
Parse exception in: The data file is corrupt.

<filename>
Graphs are incompatible. Make sure that you are not trying to combine
Cannot combine. graphs of absolute and percentage values.
The data series in the Make sure that you are not trying to compare
file are incompatible with graphs of absolute and percentage values.
the series in the graph.
Cannot retrieve type of MView is started against an incorrect slot and
interface port.
Failed to create control MView is started from InfoCenter or the

entry command line against a link to an end node or
against an end node. In this case, the interface
is down and the operational status is shown as
“Down.”
Failed to create control RMON is disabled for the device.
entry
207569-F
Resolving problems
Table 94 describes common OmniView problems and solutions.
Table 94 OmniView problems and solutions
Problem Solution
The device I want to monitor Add the device you want to monitor using the procedure in
does not show up in the “Adding a network resource to the navigation pane” on
navigation pane. page 425.
OmniView only displays one Change the OmniView configuration settings using the
statistics pane at a time. procedure in “Configuring how OmniView displays
statistics panes” on page 476.
The resource icons do not Change the OmniView configuration settings using the
appear on the monitor pane. procedure in “Configuring how OmniView displays
resource icons” on page 477.
A “No Access Allowed” alert Have an Optivity Administrator attach the necessary
box appears when I try to use OmniView access tokens. For more information about
an OmniView feature. OmniView tokens, see “Access permissions for OmniView
and MView” on page 396.
For more information about Optivity NMS Access Control,
see the InfoCenter Access Control Administration Help
system.
MView is started against a Verify that the interface exists. Log on to the device itself
slot and port and the system using Telnet and try to view the port information.
displays the error message For more information, see “Verifying that an interface
“Cannot retrieve type of exists” on page 516.
interface”
The interface is down. The Use the show ports info all command to verify the device
operational status is “down.” operational status. The Operational status column shows
The system displays the error the device operational status. If the operational status is
message “Failed to create “down,” MView cannot create a control entry and displays
control entry” an error message.
For more information, see “Verifying that an interface
exists” on page 516.
RMON is disabled on a Verify the status of RMON.
device. MView is not able to For more information, see “Verifying that an interface
create a control entry and exists‚” next.
displays the error message
“Failed to create control entry”

Verifying that an interface exists
To verify that an interface exists:
1 Use Telnet to log in to the device.

2 To view the port information, enter:
show ports info all
Table 95 illustrates the output of the command.
Table 95 Example of port information
Port Link Port Status Status

number Index Description trap lock MTU Physical address Admin operate
1/1 64 100BaseTX true false 1950 00:e0:7b:c9:5c:00 up up

1/2 65 100BaseTX true false 1950 00:e0:7b:c9:5c:01 up down
1/3 66 100BaseTX true false 1950 00:e0:7b:c9:5c:02 up down
The Port number column contains the slot and port. The Index column
contains the corresponding interface index. You can use this information to
verify that the required slot and port exist.
Note: The show ports info all command is used with Accelar
series (Accelar and Passport) devices.
Verifying RMON status
To verify RMON status:
At the command line, enter:
show rmon info
207569-F
The system output should be:

RMON Info:
Status: enable
MemorySize: 250000
TrapOption: toOwner
UtilMethod: half
Note: The show rmon info command is used with Accelar series
(Accelar and Passport) devices.
OmniView known problems
The following are known problems with the OmniView application:
• You may see the following message when opening a VLAN pane for
monitoring:
Unable to monitor.
You will not be able to monitor the VLAN xxx
since no agent associates with it.
This message displays when the VLAN object does not have an intra-VLAN
object relationship and its agent is one of the following:
• BayStack* 350 • Centillion 5000BH

• BayStack 304 • 28xxx
• BayStack 302 • 58K
• BayStack 303 • 5660
A VLAN default is created for every switch even though the agent may not
support the VLAN MIB. If the device does not support the VLAN MIB,
OmniView cannot provide VLAN information and you are not be able to
monitor the device.
Sometimes the VLAN object shown in Info Center is invalid or empty. If so,
Info Center displays the message No objects in traversal view when you click
the object.

Use the /usr/lnms/log/omniview_userid.log file to debug VLAN monitoring.

This file is created when OmniView is started.
• On the Windows NT platform, OmniView does not display all circuits.
OmniView only displays the circuit if one of the protocols on that circuit is
supported or the interface type of that circuit is supported.
• When you start OmniView against a Model 58000 switch and choose
Ports-by-Slot > Slot x > Diagnostics in the navigation pane, OmniView does
not display the slot-port index numbers. The slot-port index is displayed if
you choose Ports-by-Slot > Slot x > Status/Profile or
Ports-by-Slot > Slot x > Activity.
• When you start OmniView against a Centillion 100 TokenSpeed MCP host
module with a token ring host module (such as a Model 5502, 5505P, or
5575-F) in Slot n in the same chassis, and choose
Ports-by-Slot > Slot n > Status/Profile, OmniView does not display the
slot-port index in the table.
There is a known problem with OmniView displaying the correct slot and port
information when you start OmniView against BayStack devices.
• OmniView provides inaccurate MDA port level functionality for the following
BayStack Ethernet switches running agent version 1.2:
— BayStack 350-12T
The problem is with the agent version 1.2.
• On the Windows NT platform, there is a known problem when you start
OmniView against BayStack token ring hubs. You can open the node elements
from the Navigation pane and display statistics, but OmniView does not
display the index to show which port corresponds with which row.
• There is a known inconsistency with the way OmniView displays the Interface
Index and slot-port index for the Model 5660-FX Autonegotiating switch
module, Model 5675P-FX Ethernet host module, and Model 5300PS Ethernet
host module.
• There is a known problem when you start OmniView against a System 5000
hub. If you choose Segments > Activity or Segments > Diagnostics in the
navigation pane, OmniView displays all zeros (0) for the Segment Activity
and Segment Diagnostics totals.
207569-F
• The FDDI information displayed in OmniView does not include all the
information displayed in the Optivity NMS 10.3 release.
The version of OmniView in Optivity NMS 10.3 displayed information for
each station in the FDDI primary ring and FDDI secondary ring.
The version of OmniView in Optivity NMS 10.3 only displays information for
the local FDDI interfaces (the interfaces that are on the device being
monitored).

207569-F
521
Chapter 14
Managing network management applications with
Application Launch
This chapter describes how to configure how new and existing applications start in
Optivity NMS. It contains the following topics:
• “Application Launch overview‚” next

• “Getting started with Application Launch” on page 521
• “Working with Application Launch” on page 524
• “Application Launch error messages” on page 538
Application Launch overview
Application Launch lets you configure applications for managing your network
resources. You can specify the environment in which an application runs,
including operating platform and command line options. You can also specify the
number of devices an application manages. Application launch information is
stored in the Optivity NMS database.
At installation, all Optivity NMS applications (for example, Expanded View,

OmniView, and Fault Summary) are configured to start for specific network
resources.
Getting started with Application Launch

This following sections describe the InfoCenter Application Launch window and
how to configure applications that start from within Optivity NMS:
• “Starting Application Launch‚” next

522 Chapter 14 Managing network management applications with Application Launch
• “Modify Application Launch dialog box” on page 522
Starting Application Launch
To start Application Launch:
1 Start Optivity NMS InfoCenter.

2 From the menu bar, choose Admin > Application Launch.
The Modify Application Launch dialog box opens (Figure 219 on page 522).
Modify Application Launch dialog box
Figure 219 shows the Modify Application Launch dialog box.
Figure 219 Parts of the Modify Application Launch dialog box

Applications list Supported Resources
Execution Environments Command buttons
207569-F
Chapter 14 Managing network management applications with Application Launch 523
Table 96 describes the items in the Modify Application Launch dialog box.
Table 96 Modify Application Launch dialog box
Item Description
Applications List Displays all applications configured to start from within Optivity NMS.
By default, all integrated Optivity NMS applications are configured to
start for resources in your network.
The Applications list box includes the following information:
• Application Name
• Category - Shows either Fault, Performance, Configuration,
Accounting, Security, or Weblinks. (Determines shortcut menu
submenu for the application.)
• Description
In the Applications List Box, select an application to modify or delete
its start configuration. See “Specifying the application execution
environment” on page 536 and “Deleting an application” on page 537.
Add Adds a new application to start for supported network resources. See
“Adding a new application” on page 535.
Delete Removes an existing application that you do not want to start from
within Optivity NMS. See “Deleting an application” on page 537.
Refresh Checks each Application Launch command line entry to determine if
the command is present in your client’s path environmental variable.
Regenerates the Installed Apps.txt file in $LNMSHOME/conf. If its
executable file is not present in the path environmental variable, you
cannot launch the application from InfoCenter.
Execution Specifies the operating environment in which you want an application
Environments to start, including the platform (Windows NT, Windows 2000, UNIX, or
Area Web browser) and the executable command line options. See
“Specifying the application execution environment” on page 536.
Class Specifies that the application runs from the same Java Virtual
Machine as InfoCenter.
CmdLine Specifies that the application runs as a separate process.
Class/URL Specifies that the application runs from an HTML Web page.
Supported Displays a tree view of the network resource folders. Open a folder to
resources list see the network resources that could exist in your network.
The highlighted resources are supported by the application selected
in the Applications list box. In the Supported Resources list box, you
can select the network resource(s) for which you want an application
to start and manage. See “Application Launch error messages” on
page 538.
Mnemonic Specifies the keyboard shortcut that launches the application from the
shortcut menu.

Table 96 Modify Application Launch dialog box (continued)
Item Description
Resource Limit Specifies the maximum number of devices an application session can
manage. Type a number in the text box. Leaving the box blank
specifies an unlimited number of devices.
OK Stores the current application information in the Optivity NMS
database and closes the dialog box.
Apply Stores the current application information in the Optivity NMS
database without closing the dialog box. You can store a change, then
make more changes to apply and store.
Reset Ignores the changes you have made and reverts to the last stored
application information in the Optivity NMS database. Therefore, any
changes made after you click OK or Apply are lost.
Cancel Closes the dialog box without storing any changes.
Help Displays this Help topic.
Working with Application Launch

The following sections describe the Application Launch execution environment
command line syntax and how to work with Application Launch:
• “Execution Environment command line syntax‚” next

• “Viewing application support for a resource” on page 531
• “Modifying the launch configuration for an application” on page 534
• “Adding a new application” on page 535
• “Deleting an application” on page 537
• “Selecting supported network resources” on page 536
• “Specifying the application execution environment” on page 536
Execution Environment command line syntax

You use the Execution Environment command line syntax in the Execution
Environment area of the “Modify Application Launch dialog box” on page 522 to
start a network management application.
207569-F
The following sections describe the components used in the execution

environment:
• “Reserved symbols‚” next

• “ParserElement types and syntax” on page 526
• “Special symbols” on page 528
• “Terminal symbols” on page 529
• “Execution environment syntax production rules” on page 530
The Execution Environment command line is grammar encoded, and composed of

a collection of ParserElement components. The first component determines the
ParserElement type. Each other component represents a procedure to decode the
input command line.
The Application Launch expansion engine generates the final command line
required to execute an application. Thus, any command line that can be broken
down into ParserElements is valid for Application Launch.
Except for Simple Parser Elements, all other ParserElements need not be
separated by space characters (see “ParserElement types and syntax” on
page 526). Also, all white spaces between elements are replaced by a single space.
Reserved symbols
The following are the reserved symbols that have special significance within the
Application Launch expansion engine:
[@] [|] [\t] [!] [#] [*] [:] [=] [' '] [^]
[$] [%] [{] [}] [<] [>] [, ] [\] [&]
Note: You can place a backward slash, \, before reserved symbols to

nullify their significance.

ParserElement types and syntax
Table 97 defines the ParserElement types, syntax, and examples.
Table 97 ParserElement descriptions
ParserElement type Syntax/Example
Simple ParserElement Any sequence of non-reserved characters. The Application

Launch expansion engine copies the element contents from
the input command line to the final command line. This is
the only element that does not start with a unique special
character.
Example: very simple string “string with escape chars [\],
[@], [\], [#], [\], [%], [“].
Group ParserElement Groups one or more ParserElements and treats them as
one. You can also use this element to separate an element
from neighboring Simple ParserElements.
Syntax: { elem1 elem2 ... elemn }
Example: [2] {-I %IP_Address -R %Read_Community}
The four elements within the group, -I, %IP_Address, -R
and %Read_Community, are treated as a single element
and are repeated twice. The result is similar to:
-I 10.127.10.10 -R public -I 10.127.10.11 -R public
@{USER}_db
The value of the special keyword USER is substituted and
could result in root_db.
207569-F
Table 97 ParserElement descriptions (continued)
DBProperty ParserElement Substitutes a database property value at runtime. The

database property could be a static property associated
with a database class, or it could be an instance property
associated with a network resource instance. In the case of
an instance property, the property values of the devices that
you select are substituted. It is also possible to specify a
default value for a property. If the expansion engine fails to
get a property value from the database, then it uses a
default value.
Syntax:
%DatabaseName:ClassName:PropertyName=defaultValue
Except for the property name, all other fields are optional. If
a class name field exists, then it represents a static
property; otherwise it is a non-static property. If the
database name is missing for a static property, then it
searches the database of the logged in user for the static
property value.
Examples: %IP_Address
%Read_Community=public
%AccessState:State
%AppControlDB:AccessState:State
Counter ParserElement Specifies the number of times the next ParserElement
should be repeated.
Syntax: [number*] ParserElement OR
[number] ParserElement OR
[#] ParserElement
Where * and # are special symbols representing percent of
and remaining number of devices selected at run time,
respectively.
Example: [2] { -I %IP_Address }
[25*] { -I %IP_Address }
[#] { -I %IP_Address }
Assuming that there were four devices selected with
IP_Addresses, 10.125.10.1 through 10.125.10.4, the above
elements result in the following command lines.
-I 10.125.10.1 -I 10.125.10.2
-I 10.125.10.1 (25% of 4 == 2)
-I 10.125.10.1 -I 10.125.10.2 -I 10.125.10.3 -I 10.125.10.4

Table 97 ParserElement descriptions (continued)
Optional ParserElement Marks the next ParserElement as an optional part of the

final command line.
Syntax: ! ParserElement
While generating the final command line, the element
following ! is expanded and placed in the command line only
if it is non-null.
Example: ! { -P %Status }
Results in something like -P ACTIVE only when the value of
Status variable is non-null. Otherwise, the -P option is not
considered in the final command line.
Choice ParserElement Useful when only one database variable value is to be
substituted from a set of variable values. The expansion
engine selects the first variable with a non-null value,
starting from the left.
Syntax: < %var1 | %var2 | %var3 >
Keyword ParserElement Provides some client-side information to the applications
being launched.
Syntax: @Keyword or @{Keyword}
where Keyword can be one of the following:
− LOCAL_IP - substitutes the local host's IP address
− NMS_IP - substitutes the server machine's IP address
− USER - substitutes the Optivity user name
− PASSWORD - substitutes the password
− SERVER - substitutes the server host name
− URL_WITH_HOSTNAME_AND_PROTOCOL -
substitutes the base URL from the client application's URL.
The base URL consists of the protocol, server hostname,
and port information. This keyword is applicable only in
browser mode.
Special symbols
Table 98 defines the special symbols.
Table 98 Special symbols
Symbol Meaning
[*] Zero or more instances of

[+] One or more instance of
207569-F
Table 98 Special symbols (continued)
Symbol Meaning
[?] Zero or one instance of

[|] Either the left side or the right side of the symbol
Terminal symbols
Table 99 lists and defines the terminal symbols that are used in Application
Launch syntax production.
Table 99 Terminal symbols
Symbol Definition
[@] AT
[|] OR
[\t] TAB
[!] BANG
[#] HASH
[*] STAR
[:] COLON
[=] EQUAL
[] SPACE
[^] CARET
[$] DOLLAR
[{] LBRACE
[}] RBRACE
[<] ALBRACE
[>] ARBRACE
[ SLBRACE
] SRBRACE
[%] PERCENT
[&] AMPERSAND
[\\] BACKSLASH
0 to 9 <DIGIT>

Table 99 Terminal symbols (continued)
Symbol Definition
<DIGIT>+ <NUMBER>
[ ], [\t] <SPACE>
[ ] <WHITESPACE>
[@], [|], [\t], [!], <>
[#[, [*], [:], [=],
[' '], [^], [$], [%],
[{], [}], [<], [>],
[, ], [\,] [&]
All characters <NON_RES_CHARACTERS>
except the
<> set
Execution environment syntax production rules
Table 100 defines the Application Launch execution environment production

syntax.
Table 100 Execution environment syntax production rules
Command Syntax
CmdLine ( <ParserElement><WHITESPACE>* )+
ParserElement ( <SimpleParserElement> | <GroupParserElement> |
<DBPropertyParserElement> |
<CounterParserElement> | <OptinalParserElement> |
<ChoiceParserElement> | <KeywordParserElement> )
SimpleParserElement ( <LaunchCharacter> )+
LaunchCharacter ( <NON_RES_CHARACTER> | <BACKSLASH><> )
GroupParserElement ( <LBRACE> <ParserElement>+ <RBRACE> )
DBPropertyParserElement ( ( <InstancePropertyElement>
<DefaultValueElement>? ) | ( <ClassPropertyElement>
<DefaultValueElement>? ) | (
<ClassPropertyElementWithDB>
<DefaultValueElement>? ) )
InstancePropertyElement ( <PERCENT><PropertyName> )
ClassPropertyElement (<PERCENT><ClassName><COLON><PropertyNam
e> )
207569-F
Table 100 Execution environment syntax production rules (continued)
Command Syntax
ClassPropertyElementWithDB (<PERCENT><DBName><COLON><ClassName><C
OLON><PropertyName> )
DefaultValueElement ( <EQUAL><DefaultValue> )
PropertyName ( <SimpleGroupElement> )
ClassName ( <SimpleGroupElement> )
DBName ( <SimpleGroupElement> )
DefaultValue ( <SimpleGroupElement> )
SimpleGroupElement ( <CounterElement> <WHITESPACE>*
<ParserElement> )
CounterParserElement ( <SLBRACE><Counter> <SRBRACE> )
CounterElement ( <SLBRACE><Counter> <SRBRACE> )
Counter ( ( <NUMBER><STAR>? ) | <HASH> | ( <NUMBER>?
<CARROT> <NUMBER> ) )
OptionalParserElement ( <BANG> <WHITESPACE>* <ParserElement> )
ChoiceParserElement ( <ALBRACE> <ChoiceWithDelimiter>* <Choice>
<ARBRACE> )
ChoiceWithDelimiter ( <Choice><OR> )
Choice ( <SimpleGroupElement> )
KeywordParserElement ( <AT> <Keyword> )
Keyword ( "LOCAL_IP" | "NMS_IP" | "USER" | "PASSWORD" |
"SERVER" |
"URL_WITH_HOSTNAME_AND_PROTOCOL" )
Viewing application support for a resource

From either Application Launch or InfoCenter, you can view the network
management applications that are configured to start for a selected device. The
following sections describe how to view and configure applications for a resource:
• “Viewing applications from Application Launch‚” next

• “Viewing applications from InfoCenter” on page 533

Viewing applications from Application Launch
To view applications from Application Launch:
1 From the InfoCenter menu bar, choose Admin > Application Launch.
The Modify Application Launch dialog box opens (Figure 220).
Figure 220 Modify Application Launch dialog box
2 In the Applications List, select a network application.

The supported resources for that network management application are
highlighted in the tree in the Supported Resources list box.
3 To dismiss your changes and close the dialog box, click Cancel.
207569-F
Viewing applications from InfoCenter
To view applications from Info Center:
In the InfoCenter Contents pane, right-click an object and choose a network

management category from the shortcut menu (Figure 221):
• Fault
• Performance
• Configuration
• Accounting
• Security
• Weblinks
The application(s) configured for that device appear in a submenu
(Figure 221).
Figure 221 Object shortcut menu
4 Repeat Steps 1 and 2 to see what network management applications are

configured to start for other network resources.

Modifying the launch configuration for an application
To modify an existing network management application launch configuration for

an application that you want to start from within Optivity NMS:
The Modify Application Launch dialog box opens (Figure 222).
Figure 222 Modify Application Launch dialog box
2 In the Applications list box, select the application that you want to modify.
3 If necessary, modify the supported resources for the application.
4 If necessary, modify the execution environment settings for the application.
5 If necessary, modify the resource limit for the application.
• Click OK to save the changes and close the dialog box.
207569-F
• Click Apply to save changes and keep the dialog open to modify other
applications.
Adding a new application
To add a new network management application that you want to start from within
Optivity NMS:
1 Add the new application’s directory to the path environmental variable in

either the Windows System Properties dialog box, or the UNIX login
initialization file.
Note: If the executable is not present in your client’s path, you cannot
start the application in InfoCenter.
3 Click Add.
A default New Application entry appears in the Applications list.
4 Type an application name in the Applications Name column.
5 Click the Application Category column.
A list opens.
6 Select a category from the list.
7 Type a brief description for the application in the Description column.
8 Select the network resources the application can manage.
See “Selecting supported network resources” on page 536 for more
information.

9 Specify the execution environment for the application, including the operating
platform and the command line options.
See “Execution Environment command line syntax” on page 524 for more
information.
10 Type the device limit for the application.
11 To save the new launch point, click Apply.
12 Click Refresh.
Application Launch checks each of its command line entries to determine if
the application executable is present in your client’s path environmental
variable (see Step 1), and regenerates the Installed App.txt file in the
$LNMSHOME/conf directory.
13 To close the dialog box, click OK.
The new application’s launch information is added to your database and you
can launch the application from InfoCenter.
Selecting supported network resources
In the Supported Resources list of the Modify Application Launch dialog box, you
can select a single resource by clicking it. You can also use Shift+Click and
Ctrl+Click to select multiple resources.
Specifying the application execution environment

To specify how you want a network management application to start from within
Optivity NMS:
The Modify Application Launch dialog box opens.
2 Add a new application or modify an existing one.
See “Adding a new application” on page 535 or “Specifying the application
execution environment” on page 536.
207569-F
3 Specify an execution environment from Table 101, the operating platform,

and command line options.
Table 101 Execution environments
Execution
environment Description
Class Runs an application from the same Java Virtual Machine as InfoCenter.
In the text box, type the class name and the command line arguments
to be parsed to the application.
CmdLine Runs an application as a separate process. In the text box, type the
complete command to start the application.
URL Runs a application from an HTML Web page. In the text box, type the
Web page URL.
For more detailed information, see “Execution Environment command line

syntax” on page 524.
Deleting an application
To delete a network management application that you do not want to start from
within Optivity NMS:
2 In the Application list, select the application that you want to delete.
3 Click Delete.
4 Click OK.
The application launch information is removed from the database.

Application Launch error messages

Table 102 lists Application Launch error messages and solutions.
Table 102 Application Launch error messages and solutions
Message Solution
Invalid This error message is displayed when the application registration

entry at <index number> entry in the Applications list box is invalid. (The index
index: number in the Applications list box starts with 0.)
<index> This error message displays when one of the following occurs:
Application name is missing.
When you add a new application, a default New Application entry
appears in the Application List column of the Application list box. You
must type another application name.
Device limit can not be < 0.
The Device Limit value should be blank or a positive number. Leaving
this box blank or typing 0 indicates an unlimited device limit for your
new application entry. The Device Limit box does not have any
significance when you have not selected any resources in the
Supported Resources list box.
207569-F
Table 102 Application Launch error messages and solutions (continued)
Message Solution
Invalid All command lines can not be null.

entry at Add at least one command line in the Execution Environment area for
index: either UNIX, Windows NT, Windows 2000, or a Web browser for
<index> starting your new application. If supported, you can add a command
line for each environment.
(continued)
Invalid command line. There is a syntax error in one or more of
the Execution Environment command lines and one of the following
error messages appears:
• Escape character placed before ordinary symbol.
There is a set of reserved symbols to use to direct the command
line expansion engine. Use the backslash (\) escape character to
negate the special significance of any of these reserved symbols
only, and do not place it before normal characters.
For more information, see “Reserved symbols” on page 525.
• Extra special symbols encountered in the command
line. Special symbols are encountered at unexpected places.
• Enclosing } is missing. An opening or closing parenthesis is
missing in the Group element definition.
• Default Value expected. In a DBProperty element definition,
the default value field is missing. For example, there is no value
after =.
• Variable name expected. There is an error in the DBProperty
element name definition.
• DB Class name expected. There is an error in the database
class name definition of a DBProperty element.
• Database variable name expected. The name of a
DBProperty element is missing.

Table 102 Application Launch error messages and solutions (continued)
Message Solution
• ParserElement can not be nested within a variable

block. All the fields of a DBProperty element and keyword
element should only be a simple identifier or a Group element
containing an identifier. Violating this rule results in these
messages:
Invalid parser element after counter element.
Null counter element.
Invalid symbols within counter element.
Enclosing ] is missing. Error in the definition
of a Counter element.
Invalid placement of *. Error in the definition
of a Counter element.
Invalid parser element after option element.
Enclosing > missing. Error in the definition of
a Choice element.
Invalid parser element.
For more detailed information about the supported Execution
Environment command line syntax, see “Execution Environment
command line syntax” on page 524.
Invalid The device selections for the same application should be mutually
entry at exclusive. This error message is displayed when two entries with
index: identical names and overlapping resource lists exist. Duplicate
<index1> Application List entries are not allowed because the Application Launch
subsystem cannot identify a unique command line to execute for a
when
selected resource. Change the name or change the supported
compared to resource list.
the entry
at <index2>
Can’t have This error message is displayed when multiple schemas with the same
multiple Type and Subtype information are present in the AppControlDB
schemas per database. The Optivity schemas and Type/Subtype string pair should
type/ be unique. And also there should be a one-to-one mapping between
Type/Subtype pairs and schemas. This error could occur while adding
subtype
new device support using the Optivity Interface Toolkit (OIT). The error
combo. dialog box also displays the Type/Subtype information. Look at the
schemas definitions file, correct any problems, and recreate the
AppControlDB database.
207569-F
541
Chapter 15
Specifying the level of statistics gathering with
Monitor Options
Monitor Options is an Optivity NMS topology and fault management tool you use
to control the level of network monitoring. For example, Monitor Options
determines what level of device information AutoTopology Manager discovers for
a selected object—multilayer information versus device-only information and
whether or not to discover end nodes.
You can also use Monitor Options to control fault correlation, ICMP polling, trap
registration, syslog registration, and topology discovery on a subnet, segment,
device, or a router interface.
From Monitor Options, you can view the topology and fault management services
currently configured for an InfoCenter object or folder. If you do not change any
settings in the Monitor Options dialog box, the default Autotopology discovery
process will discover all layer 1 to 3 device information (multilayer topology),
plus end node information.
Getting started with Monitor Options

You access Monitor Options from InfoCenter. You can view or change network
monitoring and fault management options for an object, and/or its children, by
selecting the object in InfoCenter, and then choosing Admin > Monitor Options
to set the options.
Note: You must have an IC_ADMIN permission token with Read/Write

access privileges in order to change monitoring options. See “Setting
user access for Monitor Options” on page 548.

542 Chapter 15 Specifying the level of statistics gathering with Monitor Options
The following sections describe the Monitor Options application, and tell how to
start it:
• “Starting Monitor Options‚” next

• “Monitor Options dialog box” on page 543
• “Default monitoring options” on page 545
• “Network discovery options” on page 545
• “Fault management processes” on page 547
• “Determining monitoring options for objects” on page 547
Starting Monitor Options
Before you can start Monitor Options, you must select an object in the InfoCenter
main window. The Monitor Options menu selection in the Admin menu is
disabled until you select at least one object.
To start Monitor Options:
1 In an InfoCenter folder view, select one or more objects.

Use Shift+click and Ctrl+click to select multiple objects in a folder view.
Note: When more than one object is selected, Monitor Options opens
with default values shown, and not values from the selected devices.
The selected objects can be physical devices, a segment, or a subnet folder.

2 From the InfoCenter menu bar, choose Admin > Monitor Options.
The Monitor Options dialog box opens (Figure 223), displaying at the top the
name of the object and the current user’s access privileges.
207569-F
Chapter 15 Specifying the level of statistics gathering with Monitor Options 543
Monitor Options dialog box
Figure 223 shows the parts of the Monitor Options dialog box.
Note: The exact appearance of your dialog box depends on the

InfoCenter Look and Feel settings you make. For more information, see
“Organizing your network with InfoCenter” on page 255.
Figure 223 Monitor Options dialog box
Retain Monitor Options
Default/Customize
Topology area
Fault area
Edit Default

Table 103 describes the items in the Monitor Options dialog box.
Table 103 Monitor Options dialog box
Item Description
Retain Monitor Options Retains customized settings for a child object that differ from
those of its parent. Uncheck to apply the monitoring options
set for the object’s parent. For more information, see
“Retaining or overriding parent monitoring options” on
page 548.
Default Changes default settings that apply to all objects except
those for which you have established custom monitoring
options. For more information, see “Default monitoring
options” on page 545.
Customize Customizes the monitoring options for this device and its
children, except those children for which you have
established separate custom monitoring options. See
“Customizing monitor options” on page 549.
Optivity NMS stores customized monitor options in the
topology database. Customized information is lost if the
device is deleted or recreated.
Topology area Lets you establish monitoring options for topology services.
See “Network discovery options” on page 545.
Fault area Lets you establish monitoring options for fault management
processes. See “Fault management processes” on
page 547.
OK Saves the current settings and closes the Monitor Options
dialog box.
Cancel Closes the Monitor Options dialog box without saving
changes.
Apply Saves changes without closing the Monitor Options dialog
box.
Edit Default Retrieves the default Monitor Options settings from the
Application Control Database and allows editing.
Help Displays Monitor Options Help topics.
207569-F
Default monitoring options
If you make no changes to your default settings, Optivity NMS applies the
following monitor options by default:
• All topology objects inherit parent monitor settings. See “Retaining or

overriding parent monitoring options” on page 548 for more information.
• Multilayer autotopology service is active. See “Network discovery options‚”
next for more information.
• End node topology service is active. See “Network discovery options‚” next
• All fault monitoring processes except Syslog Registration and Protocol
Discovery are active. See “Fault management processes” on page 547 for
more information.
Monitor Options default settings are stored in the Optivity NMS application
control database and do not change when the topology database is deleted or
recreated.
Note: After you save monitor options changes for an object, the new
setting propagates to all descendants of the object, except those for
which you have checked the Retain Monitor Options checkbox.
Network discovery options
The topology area of the Monitor Options dialog box lets you establish the level
of network discovery. Optivity NMS uses information about discovered devices to
build its topology databases.

Table 104 describes the options available in the topology area of the Monitor
Options dialog box.
Table 104 Monitor Options levels of network discovery
Topology
option Description
Auto Topology Activates either Multilayer or Device Only monitoring for the object.
Multilayer Discovers the entire device and subnet structure of a network,
including:
Layer 3 - Topology information from all MIB-II compliant routers.
Layer 2 - Trunk and VLAN information from Nortel Networks switches.
Layer 1 - Interconnect port information from Nortel Networks shared
media hubs.
The Multilayer option provides the most information about selected
objects, and is enabled when you click Edit Default. You can also select
End Node Topology if you want to discover network address
information.
Some devices do not support Multilayer topology. See the device
release notes or installation manual for information.
Device Only Discovers only layer 1, physical device interconnections.
Choose this option for the following:
• devices that do not support or do not use multilayer topology (for
example, MIB-1 device, hubs, etc.)
• a subnet of hubs with no switches or routers
• if you only want port information
You can also select End Node Topology if you want to discover network
address information.
End Node Obtains network address information from workstations and end nodes
Topology connected to Nortel Networks and third-party devices. Available only
when Multilayer or Device Only autotopology is active.
Protocol Obtains network protocol information from Nortel Networks and
Topology third-party devices.
For information about topology services, see Chapter 4, “Discovering your

207569-F
Fault management processes
You can use the Fault section of the Monitor Options dialog box to establish how
Optivity NMS will manage your fault processes. Table 105 describes the available
fault management options.
Table 105 Monitor Options fault management processes
Process Description
Fault Correlator Correlates SNMP traps from this object.

Superping Sends a periodic ping message to test reachability of the object.
Trap Registration Registers Optivity NMS as a trap receiver for this object.
Syslog registration Registers Optivity NMS as a syslog message receiver for this
object.
Protocol discovery When enabled, the NMS station generates traps for routers added
and pruned during multicast rediscovery.
Determining monitoring options for objects
You cannot configure all network discovery and fault management options for
every object type. For example, it is not useful to apply Autotopology to a
component object.
Table 106 indicates the available network discovery or fault management options
for specific object types.
Table 106 Monitoring options for objects
Subnet Router Component

Monitor options folder link view
Auto Topology Y N N
End-Node Topology Y N Y
Fault Correlator Y N Y
Super Ping Y N Y
Trap Registration Y N Y
Syslog Registration Y Y Y
Protocol Discovery N N Y

Working with monitor options

When the Monitor Options dialog box opens, the access privileges of the current
user are displayed at the top. If you have read/write access to the IC_ADMIN
token, you can customize monitor options. If you have read-only access, you can
view the current monitor options, but you cannot change them. Your access
(read-only, read/write) for Monitor Options is the same as your access for
InfoCenter.
This section contains the following topics:
• “Setting user access for Monitor Options‚” next

• “Retaining or overriding parent monitoring options” on page 548
• “Customizing monitor options” on page 549
• “Editing monitor options defaults” on page 550
Setting user access for Monitor Options
Monitor Options is an administrative task in InfoCenter. You must have read/write

permissions for InfoCenter administrative tasks in order to change monitoring
options. Access is controlled by an Optivity NMS administrator who sets the IC
and IC_ADMIN permission tokens in the Access Control Administration window.
For information about setting user access, see Chapter 2, “Specifying access to
Optivity NMS applications with Access Control Administration,” on page 75.
Retaining or overriding parent monitoring options
By default, the monitor options of parent topology objects propagate to child

objects. You can override this default behavior using the Retain Monitor Options
check box.
• If you want parent object settings to propagate to this object, leave the Retain
Monitor Options box unchecked. You can still customize options for the
object, but your selections are updated if they conflict with settings for a
parent object.
• To bypass updates from parent object settings, check the Retain Monitor
Options box and customized settings for the selected object cannot be
overridden. The object does not inherit settings from a parent object.
207569-F
Customizing monitor options
If you have read/write access for InfoCenter, you can customize the Topology and
Fault monitor options for a particular device and its child objects (for example, all
devices in a segment).
Customized monitor options are stored in the topology database and are lost if the
device topology is deleted or recreated.
Note: To permanently change the monitoring for all objects, you should
edit the monitor options defaults instead.
To customize the monitoring options for an object:
1 In the InfoCenter folder pane, select a physical device, segment, or subnet.

2 Choose Admin > Monitor Options.
The Monitor Options dialog box (Figure 223 on page 543) opens.
3 Click Customize.
4 Select the topology and fault options for the object.
5 To prevent its parent’s settings from overriding the settings for this object,
click Retain Options.
• To save your settings and close the dialog box, click OK.
• To save your settings and keep the Monitor Options dialog box open, click
Apply.

Editing monitor options defaults
To change the monitor options for all objects, you can edit the default settings if
you have read/write access. Optivity NMS stores default settings in the application
control database. Default settings do not change when the topology database is
deleted or recreated.
Note: Changing the default settings for one object changes the settings
for all objects. To avoid changing the default settings for all objects, you
can customize the settings for a specific device instead.
To edit monitor options default settings:
1 In the Monitor Options dialog box (Figure 223 on page 543), click Edit
Default.
The settings revert to the system defaults.
2 Select the topology and fault options that you want to apply.
• To save your settings and close the dialog box, click OK.
• To save your settings and keep the Monitor Options dialog box open, click
Apply.
The new default settings are applied to all objects, except those for which you
have customized settings.
207569-F
Troubleshooting Monitor Options

Table 107 provides suggestions for troubleshooting Monitor Options.
Table 107 Troubleshooting Monitor Options
Problem Solution
Attempting to open the This error indicates one of the following:

Monitor Options window • You do not have permission to access InfoCenter
produces the following administrative tools. See “Working with monitor options”
message: on page 548 for more information.
Access to this object • The selected object is a device that does not support
denied or unsupported. Monitor Options in its schema. Select another object to
configure monitor options.
Some selections in the The selected object does not support all Monitor Options
Monitor Options dialog box services. See “Network discovery options” on page 545 to
are unavailable. determine the services you can configure for each object
type.
The Monitor Options menu You have not yet selected a supported object in the
selection is unavailable in InfoCenter main window. Select a supported object and the
the InfoCenter Admin menu selection displays.
menu.

207569-F
553
Chapter 16
Configuring devices with Expanded View
This chapter is organized into the following major sections:
• “Expanded View overview‚” next

• “Getting started with Expanded View” on page 554
• “Working with Expanded View” on page 575
• “Troubleshooting Expanded View” on page 591
Expanded View overview

Expanded View is an Optivity NMS application that manages internetworking
devices using the Simple Network Management Protocol (SNMP). Expanded
View is a graphical interface between you and the internetworking devices that
make up your network.
Expanded View allows you to remotely manage a device, just as though you were
in the wiring closet. It makes retrieval of fault, performance, and configuration
information for a device a point and click operation.
Expanded View displays a real-time physical view of the front panel of a device,
and all elements of each installed module, including LED panel status. From the
front panel view, you can view fault, configuration, and performance information
for the device, module, or single port.
Expanded View provides a back view of a device, including the backplane, power
supply, temperature sensor, and fan so you can quickly view device operation
status. A logical tree view of the configured backplane segments, VLANs, and
bridge groups in the device lets you see port configuration.

554 Chapter 16 Configuring devices with Expanded View
Expanded View lets you perform fault management tasks on selected device
objects (modules and ports), including resetting, disabling, and enabling.
Getting started with Expanded View

The following sections describe Expanded View and how to use the application to
manage devices in your network:
• “Access permissions for Expanded View‚” next

• “How Expanded View displays device information” on page 557
• “Supported devices” on page 557
• “Supported agents” on page 558
• “Starting Expanded View” on page 555
• “Expanded View window” on page 560
• “Management windows” on page 571
Access permissions for Expanded View
When you start Expanded View, you must type your login name, password, and
the host name for the Optivity server to which you want to connect. Optivity NMS
gets access privilege information from Optivity NMS Access Control, and starts
Expanded View accordingly. If Access Control is enabled, you must have rights to
the SE_READ_STATS and the SE_SNMP_SETS permission token to have
read-write privileges in Expanded View. For more information about Optivity
NMS access privileges, see the Access Control Help system.
Table 108 shows the access privilege levels and describes what you can do in
Expanded View.
Table 108 Access privilege levels
Access Description
None You cannot start Expanded View.
207569-F
Chapter 16 Configuring devices with Expanded View 555
Table 108 Access privilege levels (continued)
Access Description
Read-only You can start Expanded View. You can display the main window,
configuration, and statistics information. You cannot change SNMP
parameters.
Read/write You can start Expanded View. You can display the main window,
configuration, and statistics information. You can change preferences.
You can change SNMP parameters.
An Optivity NMS administrator sets user access to Expanded View by configuring

access to the Expanded View tokens in the Access Control Administration
window. For more information about using Access Control to set permission
tokens for Expanded View, see Chapter 2, “Specifying access to Optivity NMS
applications with Access Control Administration,” on page 75.
Starting Expanded View
To start Expanded View:
Table 109 Starting Expanded View
To start
Fault
Summary
from: Do this:
InfoCenter Use one of the following methods to start Expanded View from InfoCenter:
Menu bar Select a supported device and choose Tools > Configuration > Expanded
View.
Shortcut Right-click a supported device and choose Configuration > Expanded View.
menu
InfoCenter Select a supported device and click the Configuration launchpad icon.
Launchpad
OmniView Select a device in the OmniView navigation pane and choose
Tools > Configuration > Expanded View
Windows Choose Start > Programs > Optivity > Expanded View
Start menu

Table 109 Starting Expanded View (continued)
To start
Fault
Summary
from: Do this:
command
prompt superev [optional commands]
UNIX cd $LNMSHOME/bin
command
prompt superev [optional commands]
Click the Expanded View icon on the Optivity Web page.
Note: You can use your Web browser’s Bookmark or Favorites feature to bookmark the
Expanded View application. Doing so saves the URL for Expanded View.
Table 110 describes the optional commands for starting Expanded View from
a command line.
Table 110 superev file options
Option Usage
-I Specifies the IP address of the device you want to start Expanded View
against.
-O <label> Specifies a network resource by its label in the Optivity NMS database.
-H Specifies the Expanded View server name. The name you enter is
displayed in the Expanded View login dialog box.
-R Specifies the read community name.
-W Specifies the write community name.
-U Specifies the user name.
-P Specifies the password.
-auth <key> Specifies the authentication key used to access an SNMP V3 device.
-priv <key> Specifies the private key to access an SNMP V3 device.
207569-F
If you are not starting Expanded View from InfoCenter or OmniView, the
The Expanded View window opens.
How Expanded View displays device information
Expanded View displays monitoring and configuration information about a device

by accessing the following databases:
• OmniView database—Configuration and management information about the

supported device, MIB templates, front view display, and management menus.
• Management MIB database—Agent and MIB information.
• Topology database—Device IP address, read, and read/write community
strings.
• Application Control database—SNMP parameters and user preferences.
Supported devices
Expanded View supports the complete line of Nortel Networks modular and
stackable internetworking products, including:
• System 5000 Hub

• System 5005 Hub
• System 5DN00X Hub
• System 5000BH Hub
• System 5005BH Hub
• Passport 8103
• Passport 8106
• Passport 8110
• Passport 8110co
• Passport 8603
• Passport 8606
• Passport 8610
• Passport 8610co

• Business Policy Switch 2000

• BayStack 100BASE-T Hub
• BayStack Ethernet Stackable Hub
• BayStack 10/100 Ethernet Switch
• BayStack Token Ring Hub
• BayStack 301 Ethernet Switch
• BayStack 302 Switch
• BayStack 310-24T Switch
• BayStack 350 AutoSense Switch
• BayStack 350 12/24 Port Switch
• BayStack 420
• Centillion 50 Switch
• Centillion 100 Switch
• Centillion Ethernet Switch
• Centillion Token Ring Switch
• Centillion 5000BH Switch
• LattisSwitch 281xx Hub
• Model 28200 Ethernet Switch
• Model 28200 Ethernet Switch
• Model 5800BH Switch
• Model 3328 Switch
• Ethernet Workgroup Switch
• Multimedia Workgroup Switch
Supported agents
Expanded View supports the following SNMP agents running on a device.
207569-F
When you start Expanded View, it accesses the Management MIB database and
gets the agent and MIB information for the device. Agents determine Expanded
View device management and control functionality.
• 5310A - Version 1.2, Version 1.3, Version 1.4, Version 1.5

• 531X - Version 1.0, Version 1.1, Version 1.2, Version 1.3, Version 1.4, Version
1.5
• 551X - Version 1.0, Version 1.1, Version 1.2, Version 1.3, Version 1.4
• 591X - Version 1.0, Version 1.1
• 53DN - Version 1.2, Version 1.3
• Advanced BayStack10 - Version 1.3, Version 1.4
• Basic BayStack10 - Version 1.3, Version 1.4
• BayStack100 - Version 1.0, Version 1.1
• BayStack 500 - Version 1.0
• BayStack WGS - Version 1.0
• 58000 - Version 1.4
• 281XX - Version 1.1, Version 1.3, Version 1.4
• 28200 - Version 1.4
• Passport 8103, 8106, 8110, 8110co - Version 3.2.0, Version 3.2.1
• Passport 8603, 8606, 8610, 8610co - Version 3.2.0, Version 3.2.1
Unknown devices and agents
Expanded View lets you identify unknown devices, modules, and agents by
providing the following:
• An Error log file that contains information about the unknown module,
device, or agent. The Error log file is created automatically. Only important
error conditions are logged to this file.
For Windows, if the EV_TRC_FILE environment variable is defined, then log
messages are written to that file. If the EV_TRC_FILE environment variable
is not defined, then log messages are written to a log file named ev.log, which
is placed in the c:\temp directory.
For UNIX, the ev.log file is placed in the /tmp directory.

• Error messages including the IP address of the unknown module, device, or

agent.
For unsupported devices and agents, Expanded View displays a detailed error
message. For example, the error message might indicate the operation, sysObjId,
and agent version for which Expanded View failed to find matching information
in the database.
Expanded View window
The Expanded View window includes the parts as shown in the following
example.
The Expanded View window may appear differently depending on the View >
Look and Feel command that you have selected and whether or not you are
viewing Expanded View in a Web browser.
Figure 224 shows a BayStack device in Expanded View.
Figure 224 Example of an Expanded View showing a BayStack device

(front view)
Menu bar
Toolbar
Contents
pane
Status bar
207569-F
Table 111 describes the parts of the Expanded View window.
Table 111 Parts of the Expanded View window
Part Description
Menu bar Contains the commands for operating Expanded View. You can also
right-click an object in the Expanded View front view and open a
shortcut menu with management commands. For more information
about menu bar commands, see “Menu bar” on page 561.
Toolbar Provides quick access to commonly used Expanded View commands.
For more information about toolbar buttons, see “Toolbar” on page 565.
Status box Provides status information about the currently selected command.
Contents pane Displays one of three views: front view, chassis status view, and logical
view. For more information about the contents pane, see “Contents
pane” on page 565.
Status bar Displays status information, including the selected command
description, type of device object selected, and command status.
Menu bar
The Expanded View menu bar and equivalent toolbar buttons provide commands
that let you monitor and configure a managed device. If you open Expanded View
in a Web browser, the menu bar is not displayed, but is accessed from a tool in the
Expanded View Web browser toolbar. The first tool in the toolbar opens a shortcut
menu of Expanded View menus and submenus.
The Management menu that appears in the menu bar depends on the device that
Expanded View is managing and the agent running on that device.
Table 112 describes the Expanded View menus.
Table 112 Expanded View menus
Menu Command Tool Description
File Print Opens the Print dialog box where you specify print parameters.
You can print the front view, chassis status view, and logical
view.
Exit Closes all Expanded View management windows and quits the
application.

Table 112 Expanded View menus (continued)
View Display Shows and hides the Expanded View toolbar. When the toolbar
Toolbar is shown, the command has a check mark next to it.
Display Status Shows and hides the Expanded View status bar. When the
Bar status bar is shown, the command has a check mark next to it.
Look and Feel Displays a submenu with the following commands: Metal, CDE/
Motif, and Windows. These submenu commands change the
appearance and color scheme of the Expanded View window.
Front View Displays a real-time view of the front panel of a managed
device chassis, including all elements of the installed modules.
When the front view is shown, the command has a check mark
next to it.
For more information, see “Front view” on page 566.
Chassis Displays a view of the back of the managed device, including
Status the backplane, power supply, temperature sensor, and fan
operation. When the chassis view is shown, the command has
a check mark next to it. This command is unavailable if the
device does not support it.
For more information, see “Chassis status view” on page 567.
Logical View Shows a tree view of the selected device, including the
configured bridge groups, VLANs, and backplanes. When the
logical view is shown, the command has a check mark next to
it. This command is not available if the device does not support
it.
For more information, see “Logical view” on page 568.
207569-F
Option Remote Turns on and off the feature that highlights a device and a link
Selection from the selected port in Optivity NMS InfoCenter when you
select a port in Expanded View.
Show DNS Displays the DNS name of the current device. If the device
name does not have a DNS name, the device’s IP address is
displayed.
Preferences Opens the Set Preferences dialog box that lets you specify
default settings for some Expanded View display and
operational attributes.
For more information, see “Setting Expanded View
preferences” on page 577.
Update LED Updates the LEDs on the device.
Clear Removes highlighting of all segments configured on the device
Highlight in the front view.
For more information, see “Displaying VLANs and segment
highlighting” on page 584.
Save When turned on, highlights all segments configured on the
Highlight device in different colors. When turned off, highlights a single
segment configured on the device at one time.
Highlight All Highlights all segments configured on a device at one time in
different colors. This option is available only if you have turned
on Save Highlight.
Show VLAN/ Opens the Backplane/VLAN List dialog box that displays a
Segment listing all bridge groups, VLANs, and backplane information for
Information all modules in the device. You can save the information to a file
or print it to a printer.
Window Hide All Minimizes all management dialog boxes and displays that you
have opened from Expanded View.
Close All Closes all management dialog boxes and management

windows that you have opened from Expanded View.

Management Status Opens the Status window.

Profile Opens the Profile window.
Agent Profile Opens the Agent Profile window.
Show Nodes Opens the Show Nodes window.
Set Trap Opens the Trap Receiver Table window.
Receiver
Table
Reset History Opens the Reset History window that displays the date and
time when the device was reset, including the reason.
Error Log Opens the Error Log window that lists all of the error events for
the device.
Tools Fault Opens a submenu of the available fault management
applications for the device.
Accounting Opens a submenu of the available accounting management
Configuration Opens a submenu of available configuration management
Performance Opens a submenu of available performance monitoring
Security Opens a submenu of available security applications for the
selected device.
Weblinks Opens a submenu of Web link options:
• The Corporate option opens a submenu of Web link options
to Nortel Networks Home, News and Events, and Network
Management Products home pages.
• The Support options opens a submenu of Web link options
to Nortel Networks Global Service and Support,
Documentation, and Software Services home pages.
Help Expanded Opens the Expanded View online Help system in a Web
View browser.
Help
Using Help Opens an online Help system that describes how to use the
Optivity NMS online Help system.
About Opens the About Expanded View dialog box that displays the
Expanded application version number and copyright information.
View
207569-F
Toolbar
The Expanded View toolbar buttons provide quick access to commonly used
commands.
Table 113 describes the buttons on the Expanded View toolbar.
Table 113 Toolbar buttons
Menu Opens the Expanded View menu in a Web browser.
Enclose View Resizes the Expanded View window to its original

size (the size it was when you opened it.)
Hide Management Hides all open management windows.

Dialogs
Close Management Closes all open management windows.

Dialogs
Print Opens the Print dialog box that allows you to print the
Expanded View contents pane (front view, chassis
status view, and logical view).
Help Displays the Expanded View online Help system.
Contents pane
The Expanded View window contents pane is where the views of a managed
device are displayed and where you select objects upon which to perform
management commands.
The following sections describe the three views that open in the contents pane:
• “Front view‚” next

• “Chassis status view” on page 567
• “Logical view” on page 568

The front view of a managed device is the default view and opens in the contents
pane when you first start Expanded View.
Front view
The front view displays a real-time view of the front panel of a managed device,
including all installed modules. The front view is the default view that
automatically appears in the contents pane when you first start Expanded View.
All devices support the front view.
Expanded View includes two other views of a managed device: chassis status and
logical view. When either the chassis status or the logical view is displayed, you
can display the front view of the managed device again by choosing View > Front
View.
Figure 225 shows the front panel of a BayStack 100BASE-T device. It shows the
objects on the device that you can monitor and configure using Expanded View.
Figure 225 Front panel of a BayStack 100BASE-T device

Port
Module
Network management module (NMM)
LED display
207569-F
To identify the objects in the front view of a device, point to that object and view
the description in the status bar.
To configure or monitor an object in the front view of a device, right-click that

object, then choose the command that you want from the shortcut menu.
Chassis status view
The chassis status view provides a view and the current operational status of the
backplane connections, power supply, temperature sensors, and fans.
The chassis status view opens in the contents pane when you choose View >
Chassis Status.
To view the current status of an object, point to it. The name of the object and the
current operational status appears in the Status Bar.
Figure 226 shows a chassis status view of a BayStack device.
Figure 226 Chassis status view of a BayStack device
Backplane
Power supply
Chassis fan
A red object indicates an error condition. For example the red fan in the example
indicate that the fan is not operating.

The chassis status is not updated in real time. The status shown is the status that
was current when you first displayed the view. For a more current status, reopen
the view by choosing View > Chassis Status.
Note: The chassis status view is not available for a device if the agent
does not include power supply, temperature sensor, and fan information.
Logical view
The logical view displays the logical groupings that exist within the device. In
logical view, the ports and interfaces of the device are grouped based on their
attachment and virtual LAN information. You can also display the segment and
virtual LAN membership within a device from the Show VLAN Information
command in the Options menu.
The logical view opens in the contents pane when you choose View > Logical
View.
Figure 227 shows a logical view of a Centillion device.
Figure 227 Logical view of a Centillion device
207569-F
The logical view lets you perform certain fault, configuration, and performance
tasks on the virtual LAN components. You can also display objects (for example,
paths in FDDI host modules) that cannot be seen from the front view, but can be
managed by the agent. You cannot change, create, and remove virtual LANs from
the logical view.
Note: The logical view is not available for a device if the agent does not
include segment, VLAN, or bridge group information.
Expanded View shortcut menu
For each manageable object in the front view or logical view, you can open a
shortcut menu when you right-click that object. The shortcut menu lets you
display a management window that allows you to perform fault, configuration,
and performance management on a selected object.
The shortcut menu commands that are available depend on the object that you
selected and the agent running on that device. Table 114 describes some of the
possible shortcut menu commands. In each management window, choose Help >
MIB Help to view information about the displayed information.
Table 114 Shortcut menu commands
Fault Status Opens the Status window that shows operational

information for the selected object.
Port Status Opens the Status window that shows operational
information for the selected port.
Ring Status Opens the Status window that shows operational
information for the selected ring.
Split Backplane Splits the device backplane so that you can configure
more segments.
Join Backplane Joins the device backplane so that you can configure
fewer segments.
Reset Remotely restarts or reboots the selected object.
Enable Unpartitions the selected object.
Disable Disconnects the selected object by breaking its
communication with the device backplane. To
reconnect the device, use the Enable shortcut menu
command.

Table 114 Shortcut menu commands (continued)
Fault Diagnostics Opens a Diagnostics window that lets you view

registered errors against the selected object.
Port Diagnostics Opens a Diagnostics window that lets you view
registered errors against the selected port.
Cluster Opens a Diagnostics window that lets you view
Diagnostics registered errors against the selected cluster.
Isolating Opens a Diagnostics window that lets you view
Diagnostics registered errors against the selected object.
Non-Isolating Opens a Diagnostics window that lets you view
Diagnostics registered errors against the selected object.
Configuration Profile Opens the Profile window that shows you static
physical information about the selected object.
Agent Profile Opens the Profile window that shows you static
STP Profile Opens the Profile window that shows you static
Port Profile Opens the Profile window that shows you static
physical information about the selected port.
Ring Profile Opens the Profile window that shows you static
physical information about the selected ring.
Show Nodes Opens the Show Nodes window that shows you
information about each device connected to the
selected object.
Chassis Show Opens the Show Nodes window that shows you
Nodes information about each device connected to the
selected object.
Set Trap Opens the Set Trap Receiver window that lists
Receiver Table information about IP addresses that have sent alarm
messages to the management station. You can add,
modify, or delete Set Trap Receiver Table entries. See
“Using a trap receiver table” on page 585 for more
information.
Save Saves the current configuration on the device.
Configuration
Performance Activity Opens the Activity window that shows you the activity
and error statistics for the selected object, including
the total number, delta per second, accumulated
average, and peak measurements.
207569-F
Table 114 Shortcut menu commands (continued)
LAN Profile For an ATM device, opens the Profile window that
Emulation displays a LAN Emulation Server (LES) configuration
Server table. The table shows the operating status of the
ability of a LES to respond to (LAN Emulation Client)
LEC requests. In an error state the LES is unavailable
for service and may release all the existing virtual
channel connections (VCCs) and refuse service to all
clients.
LES/BUS For an ATM device, opens the LES/BUS Extension
Extension Profile Profile window that displays configuration information
about the LAN Emulation Server/ LES/BUS pair within
an ELAN.
LES/BUS Peer For an ATM device, opens the LES/BUS Peer Profile
Profile window that displays configuration information about a
LES/BUS pair within an ELAN.
Management windows
A management window opens when you choose a command from the:
• Management menu in the menu bar

• Management shortcut menu that opens when you right-click an object in the
front view of a device
Management windows provide monitoring information about the whole device or

the object in the logical view of a device upon which you right-click.
The commands that appear in the management window menu depend on the
device that Expanded View is managing or the object upon which you right-click.
The possible management windows are grouped in the following categories based
on their display format and the kinds of operations that you can perform:
• Read-only or read/write column display

• Read/write column display
• Single- or multiple-object read-only status information table
• Multiple-object read-only statistics table
• Read-only or read/write agent table

• Question dialog
For a description of the information in a management window, choose Help >

MIB Help.
Figure 228 shows the four parts of the management window.
Figure 228 Management window for a System 5000 device
Menu bar
Toolbar
Display
area
Status bar
Table 115 describes the management window parts.
Table 115 Management window parts
Part Description
Menu bar Contains commands for using Expanded View management windows.
Toolbar Provides quick access to commonly-used management window
commands.
Display area Displays the information for the selected device object from the
management information base (MIB).
Status bar The status bar includes two sections: left and right. The left section
displays the selected menu bar description. The right section displays the
command status, date, and time.
207569-F
Management window menu bar
Table 116 describes the possible menus and commands for the Expanded View
management window.
Table 116 Management window menus and commands
File Print Opens the Print dialog box that lets you print the
information in the display area of a management window.
Quit Closes the management window.
Edit Find Row Opens a dialog box that lets you type one or more column
values as matching criteria for finding a row in a table.
Add Row Opens a dialog box that lets you type the column values
for a new row and add a new row.
Modify Row Opens a dialog box that lets you modify one or more
column values for a row in a table.
Delete Row Removes the selected row from a table.
Hide Rows/ Hides one or more selected rows or columns in a table.
Columns
Show Rows/ Opens a dialog box that lets you select the rows and
Columns columns that you want shown in a table.
Options Clear Counters Removes the counter values for all MIB objects in a table.
Show Totals Shows the counter values for all calculated or MIB objects
in a table.
Show Delta/Sec Shows the delta per second values for all calculated or
MIB objects in a table.
Show Average Shows the average delta per second values for all
Delta/Sec calculated or MIB objects in a table.
Show Vendor/ Switches between showing MAC addresses in the vendor
Hex or hex format.
Export Opens a dialog box that lets you specify the parameters
for exporting the displayed data to a file.
Set Threshold Opens a dialog box that lets you set the threshold values
for one or more calculated or MIB objects in a table.
View Refresh Gets the latest management information from the network
for the device and displays it in the management window.

Table 116 Management window menus and commands (continued)
Poll 5, 10, 20, 30 Time in seconds that the management station

Seconds automatically polls the device for management
information.
Manual Polls the device for management information manually on
demand.
Set Opens a dialog box that lets you specify polling interval
and time out values.
Graph Line Graph Opens a window that shows the management information
in line graph format.
Bar Graph Opens a window that shows the management information
in bar graph format.
Pie Chart Opens a window that shows the management information
in pie chart format.
Help MIB Help Opens a window that displays a definition of the
information in a management window.
Management window toolbar buttons
The toolbar buttons provide quick access to commonly used management window
commands.
Table 117 describes the management window toolbar buttons.
Table 117 Management window toolbar buttons
Quit Closes the management window.
Apply Activates any changes you make in a management window.
Refresh Gets the latest management information for the Expanded View
object from the network.
207569-F
Table 117 Management window toolbar buttons
Print Prints the contents of the display area in the management window.
MIB Help Displays management information base (MIB) Help for the
management window. For more information about the information
in a management window, use the MIB Help.
Working with Expanded View

The following sections describe how to work with Expanded View to manage
your internetworking devices:
• “Identifying Expanded View Objects‚” next

• “Selecting Expanded View objects” on page 576
• “Managing the whole device” on page 576
• “Managing Expanded View objects” on page 576
• “Setting Expanded View preferences” on page 577
• “Starting other Optivity NMS applications” on page 577
• “Managing faults with Expanded View” on page 578
• “Managing device configuration with Expanded View” on page 581
• “Selecting multiple ports” on page 589
• “Configuring multiple ports” on page 590
Identifying Expanded View Objects
To identify objects in the front view or the chassis status view:
Point to the object.
The description of the object displays in the status bar.

Selecting Expanded View objects
Select an object in the front view, then perform a management command for that
object.
To select the whole device:
Do not click on any object in the front view.
The whole device is selected when you first open Expanded View. Use the
Expanded View menu bar commands to perform management commands that
apply to the whole device.
To select an object:
Point to an object, then right-click it.
A description displays in the status bar, and a shortcut menu opens. Use the
shortcut menu to perform network management commands.
Managing the whole device
The whole device is selected when you do not select an object. Use the commands
in the Management menu to monitor, troubleshoot, and manage the whole device.
The Management menu is available in the Expanded View menu bar depending
upon which device Expanded View is managing and depending on what agent is
running on that device.
Use the commands in the Tools menu to start other Optivity NMS network
management on the whole device.
Managing Expanded View objects
An Expanded View object can be a module or a port within a device chassis. An

object is selected when you click or right-click it.
When you right-click an object, a shortcut menu opens. Use the commands in the
shortcut menu to perform operations on the selected object.
207569-F
Setting Expanded View preferences
You can set preferences that include:
• Backplane, bridge group, and VLAN highlighting in the front view

• LED Polling interval
• Chassis polling interval
• Management window polling interval
• Display of the device DNS
The Expanded View preferences apply to the whole device.
To set preferences:
From the Front View window menu bar, choose Options > Preferences.
The Preferences dialog box opens with the General tab displayed
(Figure 229).
Figure 229 Expanded View Preferences dialog box
Starting other Optivity NMS applications
The Tools menu allows you to start other Optivity NMS applications from within
Expanded View. The Tools menu is divided into the five International
Organization for Standardization (ISO) network management categories:
• Fault

• Accounting
• Configuration
• Performance
• Security.
The applications that you can start depend on the applications that have been
configured in Application Launch to start from within Expanded View. (See the
Application Launch online Help system.)
To start another Optivity NMS application:
1 Start Optivity NMS InfoCenter.

2 Choose Tools > <application name>
Managing faults with Expanded View
Expanded View lets you manage system faults. You can detect faults, isolate
faults, and correct them. The following sections describe how to use Expanded
View to manage faults:
• “Monitoring LEDs‚” next.

• “Displaying object status” on page 579.
• “Displaying object diagnostics” on page 579.
• “Resetting an object” on page 580.
• “Disabling or enabling an object” on page 581.
Monitoring LEDs
In the front view, you can view the LED lights to monitor operating conditions
for the whole device or for a separate module. The LED color indicates normal or
fault operation status. For example, a green LED indicates normal operation. An
amber LED indicates a fault operation status.You can set the LED Poll Interval in
the Set preferences dialog box.
The color of an LED indicates normal or fault operation status. For example, a
green LED indicates normal operation. An amber LED indicates a fault operation
status.
207569-F
You can set the LED Poll Interval in the Set Preferences dialog box.
To monitor LEDs:
1 In the front view, double-click an LED.

An LED window opens.
2 View the LED indicators.

Refer to your device documentation for LED color indications.
Displaying object status
You can view configuration information about a selected object. This information
lets you see what has happened to a device, such as the addition or removal of a
module, attachment changes, configuration changes other than attachments or
removal, the last configuration change, and the system up time.
To display object status, do one of the following:
• From the Expanded View menu bar, choose Management > Status.
• Right-click the object and from the shortcut menu choose Fault > Status.
The Status window opens. Choose Help > MIB Help for a description of the
information in the Status window.
Displaying object diagnostics
You can view diagnostic information about the selected object. Diagnostic
information lets you diagnose object performance to determine whether or not the
object has registered any errors. If so, you can disconnect the object from the
network, correct the problem, and reconnect the object once error conditions are
corrected.

To display diagnostic information:
Right-click the object for which you want diagnostic information and choose
Fault > Diagnostics from the shortcut menu.
The Diagnostics window opens. Choose Help > MIB Help for a description of
the window information.
Resetting an object
You can remotely reset a module or a port. Resetting restarts an object. Reset an
object when you want configuration changes to take effect.
When reset, a network management module (NMM) performs the on-board

self-test, downloads the required software configuration and image files, and
comes online. A host module resets all ports (as well as the module itself).
Caution: The Reset command interrupts network operation.
To reset an object:
1 Select the object that you want to reset.

See “Selecting Expanded View objects” on page 576.
• From the Expanded View menu bar, choose Management > Reset.
• From a shortcut menu choose Fault > Reset.
A message is displayed asking you to confirm the reset action.
3 Click OK.
A message is displayed showing the status of the Reset command.
207569-F
Disabling or enabling an object
You can remotely disable or disconnect (partition or wrap) a module or port from
the network by breaking its connection with the device backplane. You can also
remotely bring an object online that you have previously disabled or taken offline
because of a fault condition.
To enable or disable an object, do one of the following:
• From the Expanded View menu bar, choose Fault > Enable or Fault >
Disable.
• Right-click the object and choose Fault > Enable or Fault > Disable from
the shortcut menu.
A message is displayed showing the status of the Enable or Disable command:
• Enable Successful—The object is now online.
• Enable Failed—The object was not enabled.
Managing device configuration with Expanded View
Expanded View lets you view the current physical configuration status of an
object, including attached nodes, and the backplane, VLAN, and segment
configuration.
The following sections describe how to use Expanded View to view and manage
device configuration.
• “Displaying an object profile‚” next.

• “Displaying nodes attached to an object” on page 583.
• “Displaying VLANs and segments” on page 584.
• “Displaying VLANs and segment highlighting” on page 584.
• “Using a trap receiver table” on page 585.
Expanded View also lets you perform port-based administration for a chassis. For
ports that are similar, you can select multiple ports and do any of the following:
• Enable all ports

• Disable all ports

• Set line all ports

• Set half- or full-duplex operation for all ports
Displaying an object profile
Expanded View lets you display profile information that helps you analyze the
operational status of the managed device. Table 118 describes the profile
information.
Table 118 Profile information
Profile type Description
Device Opens the Profile window that shows the chassis physical location,
description, contact person, version number, and serial number. For a
description of the information in the Profile window, choose Help > MIB
Help.
Port Opens the Port Profile window that shows data transmission information
for the port, including alignment errors, FCS errors, runt frames, too long
frames, fragments, very long events, short events, rate mismatches, back
off failures, auto partitions, short IPGs, null frames, port collisions, late
collisions, link status changes, and system up time. For a description of the
information in the Port Profile window, choose Help > MIB Help.
Agent Opens the Agent Profile window that shows the agent image version, the
local storage agent version, the current protocols supported by the agent,
the transport protocol to use after the next boot, the IP address to use to
get the agent at next boot, the source from which to load configuration
information at the next boot, source image file, and so forth. For a
description of the information in the Agent Profile window, choose Help >
MIB Help.
STP Opens the Spanning Tree Protocol Profile window that shows information
about the Spanning Tree Protocol used by the selected object. For a
description of the information in the STP Profile window, choose Help >
MIB Help.
To display profile information:

• From the Expanded View menu bar, choose Management > Profile.
• Right-click an object and choose Configuration > Port Profile, Agent
Profile, or STP Profile from the shortcut menu.
The Profile window opens (Figure 230).
207569-F
Figure 230 System 5000 Profile window
2 Choose Help > MIB Help for a description of the Port Profile window
information.
Displaying nodes attached to an object
You can display all nodes attached to a device, module, or port. The Nodes
window displays the slot, port, MAC address, and status of each node connected
to an object.
To show the nodes attached to an object:
1 Right-click the object for which you want to view the attached nodes and
choose Configuration > Show Nodes from the shortcut menu.
The Show Nodes window opens (Figure 231).

Figure 231 Show Nodes window
2 Choose Help > MIB Help for a description of the window information.
Displaying VLANs and segments
You can view the VLANs and segments that have been configured on a device.
There are several ways to display VLANs and segments:
• From the Expanded View menu bar, choose View > Logical View.
• Choose Option > Show VLAN/Segment Information.
• Turn on the VLAN and segment highlighting by choosing Option > Highlight
All.
Displaying VLANs and segment highlighting
Expanded View lets you use either of two methods to display VLANs and
segment highlighting.
• “Method 1—Viewing all segments at the same time‚” next

• “Method 2—Viewing one segment at a time” on page 585
Method 1—Viewing all segments at the same time
To view all VLANs and segments configured on a device in different colors:
1 Choose Option > Preferences and ensure that a highlight option is selected.
207569-F
The Set Preferences dialog box (Figure 229 on page 577) opens. If a highlight
option is not selected, select one and click OK.
2 From the Expanded View menu bar in the front view, choose Option >
Highlight All.
All segments configured on the device appear in different colors. This
command is available only if you have turned on the Option > Save Highlight
command.
Method 2—Viewing one segment at a time

1 Choose Option > Preferences and ensure that a highlight option is selected.
The Set Preferences dialog box (Figure 229 on page 577) opens. If a highlight
option is not selected, select one and click OK.
2 From the Expanded View menu bar in the front view, choose Option >
Highlight All.
3 Click on each module in the device.
The configured segments appear in different color highlighting. For more
information, see “Selecting Expanded View objects” on page 576.
To view segments one at a time:
1 Choose Option > Preferences.

The Set Preferences dialog box (Figure 229 on page 577) opens.
2 Select one of the highlight options.

3 From the Expanded View menu bar, choose Option > Save Highlight.
Using a trap receiver table
The Set Trap Receiver Table management window shows the Optivity NMS
management stations that have registered with the device to receive traps (fault
conditions).
The Set Trap Receiver Table opens when you choose Configuration > Set Trap
Receiver Table from an object shortcut menu.

The following sections describe how to manage a Set Trap Receiver Table:
• “Adding a trap receiver table entry‚” next

• “Modifying a trap receiver table entry” on page 587
• “Finding a trap receiver table entry” on page 588
• “Deleting a trap receiver table entry” on page 588
Adding a trap receiver table entry
To add a trap receiver table entry:
1 Right-click the object and choose Configuration > Set Trap Receiver Table.
2 From the Set Trap Receiver Table window menu bar, choose Edit > Add Row.
The Add Row dialog box opens (Figure 232).
Figure 232 Add Row dialog box
3 Type the IP address, community string, and aging time interval of the new
entry.
4 Click Apply to implement the changes.
The new entry is inserted as the last row in the table in the Set Trap Receiver
Table window. The Add Entry dialog box remains open so you can make
changes to the new entry.
207569-F
5 Click OK to save the changes and close the Add Row dialog box.
Modifying a trap receiver table entry
To modify a trap receiver table entry:
2 In the Set Trap Receiver table, select the row that you want to change and
choose Edit > Modify Row.
The Modify Row dialog box (Figure 233) opens.
Figure 233 Modify Row dialog box
3 Type the new information in the field(s) that you want to modify.
4 Click Apply to implement the changes.
The Modify Row dialog box remains open so you can continue to make
changes to the entry.
5 Click OK to save the changes and close the Modify Row dialog box.

Finding a trap receiver table entry
To find a trap receiver table entry:
2 From the Set Trap Receiver Table window menu bar, choose Edit > Find Row.
The Find Row dialog box opens (Figure 234).
Figure 234 Example of Find Row dialog box
3 Type the information you know about the entry that you want to find and click
OK.
The specified row is highlighted and displayed as the first row visible in the
table. If the entry is not found, the No matching row found message is
displayed. Click OK to close the message box.
4 Click Cancel to close the Find Row dialog box.
Deleting a trap receiver table entry
To delete a trap receiver table entry:
2 Select the row that you want to delete and choose Edit > Delete Selected Row.
The highlighted row is removed from the table.
207569-F
Viewing performance information
Expanded View lets you view performance information so that you can maintain a
low incidence of fault and thus optimize network performance.
You can display Activity information for the selected object. Use Activity
information to ensure that the managed device is operating optimally.
The Activity window displays data transmission information, including good

frames, good bytes, multicast frames, broadcast frames, and system uptime.
To display Activity information:
1 Select the object for which you want to view Activity information.
2 From the Expanded View menu bar, choose Configuration > Activity.
Selecting multiple ports
The following sections describe how Expanded View lets you select and deselect
multiple ports:
• “Selecting multiple ports individually‚” next

• “Selecting a range of ports” on page 590
• “Deselecting multiple ports” on page 590
Selecting multiple ports individually
To select multiple ports individually:
1 Point to a port.
2 [Ctrl] + click the port.
The port is highlighted.
3 Repeat steps 1 and 2 for multiple ports.

All of the selected ports are highlighted.

Selecting a range of ports
To select a range of ports:
1 Point to the first port in the range.

2 [Shift] + click the first port in the range.
The first port is highlighted.
3 [Shift] + click the last port in the range.

The range of ports is highlighted.
Deselecting multiple ports
To deselect multiple ports:
Left-click any highlighted port.
All of the highlighted ports are deselected.
Configuring multiple ports
To configure multiple ports:
1 Right-click a highlighted port and choose a command from the Port Bundle
shortcut menu.
• Click Yes to confirm the command action.
The Execution status dialog box opens.
• Click No.
The action is cancelled.
207569-F
Troubleshooting Expanded View

Table 119 lists the Expanded View error messages and their meaning.
Table 119 Expanded View error messages
Message Description
The format of IP address The IP address format is incorrect for the device
<xxx.xxx.xxx.xxx> is not you typed in the Connect to Server dialog box.
valid
The server has The Expanded View server is down because of
unexpectedly terminated some error on the server system.
the connection.
Fail to bring up Expanded The Expanded View server took more than five
View, can not get valid (5) minutes to send back the valid data about the
data from <device name> device to the client. The client software
terminated the process.
<user> is not permitted The user does not have access to start Expanded
to use EV (Expanded View) View.
Can not reach this The Expanded View server cannot connect to the
device, please make sure specified device or Expanded View does not
the device and Read/Write support the device.
community strings are
valid.
Please enter a valid A value you typed in an Expanded View
number management display is not valid.
Polling interval should A polling interval you entered is less than zero
be greater then 0 (0).
You do not have the write You do not have write privileges to change a read/
permission write value in an Expanded View management
display.
Operation failed The Expanded View operation that you wanted to
perform failed because of a connection problem
or some other reason.
Operation timed out The Expanded View SNMP operation that you
wanted to occur failed because of the polling
interval time out.

Known problems
The following are known problems for the Expanded View application.
• No submenus are available for a port when the menu is open on the status bar
of the Expanded View window.
To resolve this problem, enlarge the window and open the shortcut menu. The
menu is displayed correctly.
• The following are known problems with working with Expanded View on
BayStack devices.
— When you start Expanded View against a BayStack 450 series switch, and
choose Management > Profile to change the Image Save Mode to
writeifDiff, Expanded View displays the following error message:
“Applying failed”
This is an agent version 1.2 problem.
— When you start Expanded View against a BayStack 303 Ethernet switch,
modify the agent profile, and apply the changes, Expanded View displays
the following error message:
“Applying failed”
207569-F
— Expanded View provides inaccurate MDA port-level functionality for the

following Ethernet switches running agent version 1.2:
— There are known problems with the BayStack 350 and BayStack 450
agent version 1.2 when working with Expanded View.
The front panel LEDs are shown incorrectly when Expanded View starts
against the following products:
— BayStack 350-12T switch
The LEDs are shown incorrectly because agent version 1.2 does not
implement the LED matrix correctly.
Expanded View displays front panel LEDs off on the BayStack 450-12T
and BayStack 450-24T switch, when in fact they are on. This problem
occurs because the agent fails to poll the LED information correctly.
— The BayStack 350 switch running agent version 1.2 displays extra LEDs
in the bit map. This is wrong. The Up and Down LEDs should not be
displayed.

207569-F
595
Chapter 17
Managing ATM traffic with Call View
• “Call View overview‚” next

• “Getting started with CallView” on page 596
• “Working with Call View” on page 611
• “Troubleshooting Call View” on page 632
Call View overview

Call View displays information about Asynchronous Transfer Mode (ATM)
networks in graphical and tabular format.
The Call View application has two layers, CallView and CallCount. Table 120
summarizes the functions of these components and how they are referred to in this
document.
Table 120 Call View application layers
Layer Description
Call View The application that includes the CallView layer, CallCount layer, the Call
Table view, and so forth.
CallView The CallView layer displays information about ATM LAN emulation
(LANE) objects. Provides a CallTable option that lets you display,
interpret, and analyze ATM calls.
CallCount The CallCount layer displays information about the number of calls for
ATM switches and physical links.
CallView or Information that applies to both layers.
CallCount

596 Chapter 17 Managing ATM traffic with Call View
Call View supports filtering and selecting the following type of calls:
• Switched virtual circuit (SVC) calls

• Permanent virtual circuit (PVC) calls
• LAN emulation (LANE) control calls to the LAN emulation server (LES),
broadcast unknown server (BUS), and LAN emulation configuration server
(LECS)
• LANE data calls
• Point-to-point and point-to-multipoint data and control calls
Calls are shown for LANE networks. The call details include the following:
• IP address of a switch
• Call type
• Calling and called network service access point (NSAP) address
• Bridge group
• Slot, port, virtual path identifier (VPI), and virtual channel identifier (VCI).
For a LANE network, the information includes the role that the switch plays as
well. For example, LEC, LES, BUS, and so forth.
Call View displays ATM information for Centillion switches.
Getting started with CallView

See the following sections for information about getting started with Call View:
• “Supported ATM objects‚” next

• “Starting Call View” on page 598
• “Call View window” on page 599
• “Call View views” on page 603
• “Color coding” on page 610
207569-F
Chapter 17 Managing ATM traffic with Call View 597
Supported ATM objects
Call View supports the ATM objects shown in Table 121.
Table 121 ATM object types
Object Label
Icon Object Type
Displayed
Unknown Unknown. Identifies third party objects or objects in

switches that cannot be reached or queried
ExtLEC External LAN emulation client (LEC)
TurboCLC Turbo Centillion LAN client
CktSvCLC Circuit Saver Centillion LAN client

(standard LANE client)
TurboLEC Turbo LAN emulation client
CktSvLEC Circuit Saver LEC
PVCEndPT Permanent virtual circuit (PVC) endpoint
LES LAN emulation server (LES)
BUS Broadcast unknown server (BUS)
LECS LAN emulation configuration server (LECS)

Starting Call View
To start Call View:
Table 122 Starting Call View
To start Call
View from: Do this:
InfoCenter Use one of the following methods to start Call View from InfoCenter:
Note: In InfoCenter, Call View only starts when you select an ATM object, such as an ATM
switch, an emulated LAN (ELAN), and ATM subnets. Call View is not available for non-ATM
devices.
Menu bar Select either an ELAN or an ATM switch that is a member of an ELAN and
choose Tools > Performance > Call View.
Shortcut Right-click either an ELAN or an ATM switch that is a member of an ELAN
menu and choose Performance > Call View.
InfoCenter Select either an ELAN or an ATM switch that is a member of an ELAN and
Launchpad click the Performance Categories Apps launchpad icon.
command
prompt callview [optional commands]
command
prompt callview [optional commands]
Table 123 describes the optional commands for the call view start file.
Table 123 Call View start file options
Option Usage
-S Specifies the server hostname for the Call View application. If this option is
not used, the default server host is the local machine.
-O Specifies the ATM object IP addresses or ELAN/subnet names. You can
use the -O parameter with multiple addresses or names.
If you are not starting Call View from InfoCenter or OmniView, the Connect
207569-F

The Call View window opens.
Call View window
The Call View window has five parts as shown in Figure 235.
Figure 235 Parts of the Call View window
Menu bar
Toolbar
Contents
area
Display
window
Status bar
Table 124 describes the Call View window parts.
Table 124 Parts of the Call View window
Part Description
Menu bar Contains commands for operating Call View.

For more information, see “Menu bar‚” next.
Toolbar Provides quick access to commonly-used Call View commands.
For more information, see “Toolbar” on page 601.

Table 124 Parts of the Call View window (continued)
Part Description
Display window CallView and CallCount graphical and tabular views open in display
windows.
For more information, see “Display window” on page 603.
Contents area Viewing area of the Call View window. CallView and CallCount
graphical and tabular views are opened in the display window in the
contents pane.
For more information, see “Contents area” on page 603 and “Call
View views” on page 603.
Status bar Displays status information.
For more information, see “Status bar” on page 603.
Menu bar
When you run Call View in a UNIX or Windows environment, the menu bar
contains six menus: File, Edit, View, Options, Window, and Help.
The menu contains the same six menu selections as listed above and provides
menu options for other menu groups.
Object shortcut menu
The Call View object shortcut menu provides commands you can use on an ATM
network entity that you have chosen. The shortcut menu contains commands
specific to the object or its immediate context.
The object shortcut menu provides the following information and commands.
Table 125 describes the object shortcut menu commands.
Table 125 Object shortcut menu commands
Command Description
Cut from View Moves the selection(s) from the current view to the clipboard.
Copy from View Copies the selection(s) from the current view to the clipboard.
207569-F
Table 125 Object shortcut menu commands (continued)
Command Description
Expand By Hop Adds all links to the current view that are one hop away from the
selected node. After the expansion, the nodes are highlighted. If the
view cannot be expanded from a selected node, Call View selects
existing nodes that connect to that node. The links and objects
displayed by the Expand by Hop command are not stored in the
folder definition.
See “Expanding by hops” on page 620 for more information.
Show Attributes Displays the View an Object Attribute dialog box.
Show Call Table Displays the Call table.
Toolbar
The toolbar buttons provide quick access to commonly used Call View
commands.
The name of a button is displayed when you move the point over the button. The
status bar describes the button’s function.
The location of the toolbar is adjustable. See “Moving the toolbar” on page 622
Table 126 describes the Call View toolbar buttons.
Table 126 Call View toolbar buttons
CVGraph Displays the CallView graph view.
CVTable Displays the CallView table view.
CCGraph Displays the CallCount graph view.
CCTable Displays the CallCount table view.
Symmetrical Replots the display using a symmetrical layout.

Table 126 Call View toolbar buttons (continued)
Hierarchical Replots the display using a hierarchical layout.
Circular Replots the display using a circular layout.
Orthogonal Replots the display using an orthogonal layout.
Grid Displays or hides the table grid.
Show Labels Displays labels for the network entities.
Show SVC Displays SVC calls.

Calls
Show PVC Displays PVC calls.

Calls
Show Data Displays data calls.

Calls
Show Control Displays control calls.

Calls
Show Displays point-to-point calls.

Point-to-Point
Calls
Show Point-to- Displays point-to-multipoint calls.
Multipoint Calls
Refresh Redisplays the latest data.
Stop Stops the following processes:

• Adding ATM objects to a current view
• Expand by hop
• Copy or paste
• Refresh
207569-F
Contents area
CallView and CallCount views are displayed in a display window in the contents
area. Call View lets you open up to four display windows in the contents area.
Display window
The following sections describe the types of views that Call View displays
CallView and CallCount ATM network information in:
• “CallView graphical view‚” next

• “CallCount graphical view” on page 606
• “CallView tabular view” on page 605
• “CallCount tabular view” on page 607
Status bar
Table 127 describes the elements of the status bar:
Table 127 Status bar elements
Element Description
Status bar Provides the following information:

message area • The context of the activity in the current display window.
• The active menu bar or toolbar command.
Progress Shows the percentage of completion for the current operation as
indicator rectangular bar that “fills” from left to right.
Call View views
The following sections describe the views that you can use to monitor and manage
ATM calls:
• “CallView graphical view‚” next

• “CallView tabular view” on page 605
• “CallCount graphical view” on page 606
• “CallCount tabular view” on page 607

CallView graphical view
The CallView graphical view lets you graphically display all LANE entities,
virtual circuits of ATM networks, and LANE circuits. Figure 236 shows a
CallView graphical view.
Figure 236 CallView graphical view
Icon
Object label
Link
Link label
Table 128 describes the elements of the CallView graphical view.
Table 128 CallView graphical view elements
Element Description
Icon Represents a logical ATM object. To view more information about the
object, right-click the icon and choose Show Attributes from the
shortcut menu. This action opens the Object Attributes dialog box for
the object.
Object label Identifies the object represented by the icon. The label shows the DNS
name if the name is available and the Show DNS Names option is
enabled. Otherwise the label shows the object IP address.
Link The lines between icons represent links between LANE entities. To
view detailed link information, right-click the link and choose Show
Attributes from the shortcut menu. This action opens the Object
Attributes dialog box for the link.
Link label Shows information about a link. To view the link label, place the pointer
over a link.
207569-F
CallView tabular view
The CallView Tabular view lets you display ATM network information in a
tabular format. The tabular format allows you to quickly identify calls in large
ATM networks. You can size, sort, and search for information in the table.
Table 129 describes the columns in the CallView tabular view.
Table 129 Call View tabular view columns
Name Contents
Node Name ATM address of the selected object.

Node Type The LANE entity type of the node.
For more information, see “Supported ATM objects” on page 597.
Switch Label IP address of the switch where the ATM object is configured and the
ELAN membership of the ATM object.
ELAN Name ELAN name.
Call Type The type of the ATM call. For example, point-to-multipoint control call
over a permanent virtual path.
For more information, see “ATM calls supported” on page 609.
Calling Party Address of the ATM object originating the connection. The address
consists of the first 19 bytes of the ATM address, plus the turbo slot.
Type Type of the logical ATM object.
Switch IP address of the switch where the LANE entity resides.
Ifldx Interface index.
Slot/Port The slot where the physical module is located and the port on that
module where the call is originated.
Vpi/Vci The virtual path identifier and virtual circuit identifier for the call.
Health The health status of the calling ATM object. May be any of the following:
• Unknown
• InitState
• LECsConnect
• Configure
• Join
• InitRegist
• BusConnect
• Operational
Called Party Destination address of the ATM object for the connection. The address
consists of the first 19 bytes of the ATM address, plus the turbo slot.

Table 129 Call View tabular view columns (continued)
Name Contents
Type The LANE entity type of the node.

Switch IP address of the switch where the ATM object resides.
Slot/Port The slot where the physical module is located, and the port on that
module where the call terminates.
Health The health status of the called ATM object. The possible health statuses
are the same as shown above for the calling object.
CallCount graphical view
CallCount graphical view lets you view how many calls are present on a link and
the number of calls terminating at a switch. Figure 237 shows a CallView
graphical view.
Figure 237 CallCount graphical view
Icon
Object label
Link
Link label
207569-F
The elements of the CallCount graphical view are described in Table 130.
Table 130 CallCount graphical view elements
Element Description
Icon Represents an ATM object. To view more information about the object,
right-click the icon and choose Show Attributes from the shortcut menu.
This action opens the Object Attributes dialog box for the object.
Object label Identifies the object represented by the icon, and the number of calls
per node. The number of calls is shown after the forward slash (/)
symbol.
Link The lines between icons represent links between ATM objects. To view
detailed link information, right-click the link and choose Show Attributes
from the shortcut menu. This action opens the Object Attributes dialog
box for the link.
Link label Shows information about a link, including the slot/port information and
the number of calls. The calls are shown after the forward slash (/)
symbol. To view a link label, place the pointer over a link.
CallCount tabular view
The CallCount tabular view lets you display all of the switches and physical links
and the number of calls for that switch or link.
The tabular format allows you to quickly identify the number of calls in large
ATM networks. You can size, sort, and search for information in the table.
Table 131 describes the column headings in the CallCount tabular view.
Table 131 CallCount tabular view columns
Name Description
Switch Name Switch name.

IP Address IP address of the switch.
DB Label Label of the switch in database.
Count Num Call count number in this switch.
Link Name Name of the physical link.
1st EndPoint First end node's switch name of the link.
2nd EndPoint Second end node's switch name of the link.

Table 131 CallCount tabular view columns (continued)
Name Description
1st Label First end node's switch label of the link.

2nd Label Second end node's switch label of the link.
1st Count Call count number of the 1st endpoint in the link.
2nd Count Call count number of the 2nd endpoint in the link.
Call Table view
The Call Table view displays detailed information about all calls to and from the
selected node. This view is only available from the CallView layer. The Call Table
view provides the same link information as displayed in the CallView Tabular
view.
The Call Table tabular view columns are described in Table 132.
Table 132 Call Table tabular view columns
Name Contents
ELAN Name ELAN name.

Call Type Type of ATM call. For example, point-to-multipoint control call over a
permanent virtual path.
For more information, see “ATM calls supported” on page 609.
Calling Party ATM address of the ATM object originating the connection.
Type The ATM object type of the node.
Slot/Port The slot where the physical module is located and the port on that
module where the call is originated.
207569-F
Table 132 Call Table tabular view columns (continued)
Name Contents
Health The health status of the calling ATM object. May be any of the following:
• Unknown
• InitState
• LECsConnect
• Configure
• Join
• InitRegist
• BusConnect
• Operational
Called Party Destination ATM address of the ATM object for the connection.
Type The ATM object type of the node.
Slot/Port The slot where the physical module is located, and the port on that
module where the call terminates.
Health The health status of the called ATM object. The possible health
statuses are the same as shown above for the calling object.
ATM calls supported
Call View supports many types of ATM calls. Table 133 describes the ATM call
types reported in the Call Type column of a Call Table.
Table 133 ATM call types and labels
Call type Label displayed
Point-to-multipoint control call over a permanent virtual path P2mpCtrlPVP

Point-to-multipoint control call over a permanent virtual circuit P2mpCtrlPVC
Point-to-multipoint control call over a switched virtual circuit P2mpCtrlSVC
Point-to-multipoint data call over a permanent virtual path P2mpDatalPVP
Point-to-multipoint data call over a permanent virtual circuit P2mpDataPVC
Point-to-multipoint data call over a switched virtual circuit P2mpDataSVC

Table 133 ATM call types and labels (continued)
Call type Label displayed
Point-to-point control call over a switched virtual circuit P2pCtrlSVC

Point-to-point data call over a permanent virtual path P2pDataPVP
Point-to-point data call over a permanent virtual circuit P2pDataPVC
Point-to-point data call over a switched virtual circuit P2pDataSVC
Color coding
Call View lets you check the color of the icons within each view to easily monitor
the status of the object or device. For example, if a device icon is red, a critical
fault reported. You can then use Fault Summary to obtain more information about
the reported fault.
In Call View, you must click Refresh to update the icons.
Icons in a Call View window represent active or inactive nodes and change color
depending on the condition of the device or connector. The colors represent a
severity value range of 0–10, where 0 means that the device is fully functional.
The color indicates the fault severity based on the alarm preference settings in
InfoCenter. For example, red may indicate the device is nonfunctional, or it could
indicate that too many security violations but no connectivity problems have
occurred.
Table 134 describes the colors used to indicate health status.
Table 134 Call view icon and link colors
Color Value
Green 0—fully functional.

Red 7-10—high (critical) severity, where 10 represents a completely
nonfunctional device. This indicates a critical condition because the device
has failed or is at risk of failing. You must take action to remedy the
situation.
White Unknown device. Call View is not able to determine what type of device the
node is.
207569-F
Working with Call View

See the following sections for information about working with CallView:
• “Using common Call View commands‚” next

• “Working with ATM calls” on page 624
• “Working with graphical and tabular views” on page 626
• “Working with object attributes” on page 629
• “Printing with Call View” on page 631
Using common Call View commands
The following sections describe how to perform basic Call View operations:
• “Adding an ATM object‚” next

• “Stopping a Call View process” on page 612
• “Deselecting objects” on page 613
• “Inverting the selection of objects” on page 613
• “Interpreting the health status” on page 613
• “Cutting an object from a view” on page 614
• “Deleting an object from a view” on page 614
• “Clearing ATM objects from a view” on page 615
• “Copying and pasting ATM nodes” on page 615
• “Finding an object in a view” on page 616
• “Searching the CallView/CallCount table” on page 617
• “Using special search characters” on page 618
• “Changing the view layout” on page 619
• “Changing the window environment” on page 619
• “Expanding by hops” on page 620
• “Using remote selection” on page 620
• “Moving the toolbar” on page 622
• “Displaying objects by DNS name” on page 623

Adding an ATM object
Call View lets you add ATM objects to a CallView or CallCount graphical or
tabular view.
To add an ATM object to the CallView or CallCount view:
1 If a CallView or CallCount view is open, go to step 2, if not, do one of the

following:
• From the Call View menu bar, choose one of the following:
— View > Graphical > CallView Graphical View
— View > Graphical > CallCount Graphical View
• On the toolbar, click one of the following:
— CVGraph
— CVTable
— CCGraph
— CCTable.
An empty CallView or CallCount view opens.
2 From the Call View menu bar, choose Edit > Add.
The Add an Object dialog box opens.
For detailed information about the Add an Object dialog box, click Help in the
dialog box.
3 Specify the object search criteria.

4 Click OK.
The ATM object and corresponding objects are added to the current view.
Stopping a Call View process
Call View lets you stop the following processes:
• Adding ATM objects to a current view

• Expand by hop
• Paste
207569-F
• Refresh
Stopping a data transfer process results in an empty CallView or CallCount view.
To stop a process:
On the toolbar, click Stop.
Deselecting objects
To deselect the selected objects in the current view:
1 Click the display window that contains the highlighted objects.

2 From the Call View menu bar, choose Edit > Deselect All.
Inverting the selection of objects
To invert the selection of objects in the current view:
1 Click the display window that contains the highlighted objects.

2 From the Call View menu bar, choose Edit > Invert Selection.
All the initially highlighted objects are deselected and the previously
unselected objects are highlighted.
Interpreting the health status
Call View lets you monitor the health status of ATM objects displayed in a
CallView or CallCount graphical or tabular view.
The health of each ATM object is indicated by the color of the node (good
operational health is green and bad operational health is red). Objects for which
Call View cannot determine the health status are shown in white.
To interpret the health status of an ATM object:
1 Open a CallView or CallCount graphical or tabular view.


• In the graphical view, observe the color of the icons.
• In the tabular view, observe the color of the rows in the table.
3 If the color of an icon or row is red, see “Color coding” on page 610 for more
information.
Cutting an object from a view
Call View lets you cut a single object or multiple objects from a view, and moves
the object(s) to the clipboard.
The following rules apply for the Cut command:
• From the Edit menu, you can use the Cut command to remove single or
multiple objects.
• From the shortcut menu, you can use the Cut command to remove one object
at a time; multiple selection is not supported.
To remove an object from a view using the Edit menu:
1 Select the object(s) in the view.

• From the Call View menu bar, choose Edit > Cut
• Press [Ctrl]+X.
The object(s) is removed from the view to the clipboard.
Deleting an object from a view
To remove an object from a view without copying it to the clipboard:
1 Select the object(s) in the view.

2 From the Call View menu bar, choose Edit > Delete.
The object is removed from the view and not copied to the clipboard.
207569-F
Clearing ATM objects from a view
You use the Clear command to clear all objects in a view.
Note: The Clear, Cut, and Delete commands remove objects from the
associated graphical and tabular views.
To clear all objects from a view:
From the Call View menu bar, choose Edit > Clear.
The selected view is cleared. If a graphical and tabular view exist, both views
are cleared. The cleared item is not copied to the clipboard.
Copying and pasting ATM nodes
Call View lets you copy ATM nodes between multiple instances of Call View,
CallView and CallCount views, and between Call View and other Optivity NMS
applications.
Call View copies then pastes the object and its contents into the current layer. For
example, if you copy a Centillion 100 switch in an InfoCenter view, the switch
and all the calls in the switch are pasted into the current layer view.
Objects are highlighted when they are pasted into the view.
You cannot paste non ATM-call relevant objects such as hubs, switches, or routers
into a Call View layer.
To copy an ATM node from CallView to another destination (CallCount, another

instance of Call View, or another Optivity NMS application):
1 Open a CallView view.

2 Select the ATM node in CallView graphical or tabular view.
• From the Call View menu bar, choose Edit > Copy.
• Press [Ctrl]+C.

• Right-click the selected object, and from the shortcut menu, choose Copy.
• In another Optivity NMS application, copy an object(s).
• Click in the CallCount graphical or tabular view.
• Click in the CallView or CallCount view in the second instance of Call
View
• Click in the display window of the other Optivity NMS application.
• In the CallCount view, from the Call View menu bar, choose Edit > Paste.
• In the CallCount view, press [Ctrl]+V.
• In the second instance of Call View, from the Call View menu bar, choose
Edit > Paste.
• In the second instance of CallCount view, press [Ctrl]+V.
• In the other Optivity NMS application, from the menu bar, choose
Edit > Paste.
• In the other Optivity NMS application, press [Ctrl]+V.
The ATM object is pasted into the respective destination.
Finding an object in a view
Call View lets you enter a search string to locate an object in the current CallView
or CallCount graphical or tabular view. Call View highlights the object when the
object is located in the view.
You can use any of the following criteria to find an object:
• IP address
• label
• name
• DNS name
To find an object in the current view:
1 From the Call View menu bar, choose Edit > Find.
The Find an Object dialog box (Figure 238) opens.
207569-F
Figure 238 Find an Object dialog box
For detailed information about the Find an Object dialog box, click Help in
the dialog box.

• Type the IP address of the switch, and click OK.
• Click Label, and type the label of the switch.
• Click Name, and type the name of the switch.
• Click DNS Name and type the DNS name of the switch.
3 Click OK.
All the matching ATM entities within the switch are highlighted.
Searching the CallView/CallCount table
Call View lets you find the first instance of an object in the CallView or CallCount
table. The search criteria are derived from the CallView or CallCount attributes.
You can use the “*”, “?”, and “/” special characters. See “Using special search
characters‚” next for more information.
To search for information in a CallView or CallCount table:
1 Open a CallView or CallCount tabular view.

2 Click the tabular view.
3 From the Call View menu bar, choose Edit > Find Row.
The Find Row dialog box (Figure 239) opens.

Figure 239 Find Row dialog box
For detailed information about the Find Row dialog box, click Help in the
dialog box.
4 Type the search criteria in the attribute text boxes.

5 Click OK.
If the ATM object is in the table, the row where the first instance of the object
is located is highlighted. For a large table, you may need to scroll the table to
locate the highlighted item.
Using special search characters
You can use special characters in a search when you use the following commands:
• Add
207569-F
• Find
• Find Row
Table 135 describes the special characters that you can use in a search.
Table 135 Special search characters
Character Function
? Matches any single character in the string.

* Matches any number of characters in the string.
+ Matches one or more occurrences of a regular expression.
. Matches any character in the string.
[] Matches strings containing the individual characters enclosed within the
brackets.
To find only file names that end with “region”, type *region. To find instances of
both “gray” and “grey” in file names, type gr?y. Use an asterisk (*) to match any
number of characters, or use a question mark (?) to match any single character.
Changing the view layout
To change the view layout from the View menu:
1 Open a CallView or CallCount graphical view.

2 From the Call View menu bar, choose View > Layout.
The Layout submenu opens.
3 Choose a layout command.
To change the view layout from the toolbar:
1 Open a CallView or CallCount graphical view.

2 On the toolbar, click a layout command.
Changing the window environment
Call View lets you configure how the application displays windows.

To change the window environment:
1 From the Call View menu bar, choose View > Look and Feel.
The Look and Feel submenu opens.
2 Choose the window environment.
Expanding by hops
Call View lets you expand the current view by one hop from a selected node. You
can select multiple nodes if you initiate expand by hop from the Edit menu and a
single node if you initiate expand by hop from the shortcut menu.
After the expansion, the nodes are selected. If the view cannot be expanded from a
selected node, Call View selects existing nodes that connect to that node.
To display nodes one hop away using the Edit menu:

2 From the Call View menu bar, choose Expand by Hop.
Call View displays and highlights the nodes that are one hop away.
To display nodes one hop away using the shortcut menu:

2 Right-click the node you want to expand from.
3 Choose Expand by Hop.

Call View displays and highlights the nodes that are one hop away.
Using remote selection
Call View lets you use the remote selection feature to highlight the relationships
between CallView graphical and tabular views and between Call View and other
Optivity NMS applications.
207569-F
Call View lets you use remote selection to show the relationship for ELANs in
InfoCenter and Call View:
• When you highlight an ATM object in Call View, the corresponding ELAN is
highlighted in the InfoCenter ELANs folder, and the corresponding switch is
selected in the InfoCenter Switches folder.
• When you highlight an ELAN in InfoCenter, all of ATM entities that
participate in the ELAN are highlighted in Call View.
You can also use remote selection in these other instances:
• Between Call View and other views in InfoCenter or other Optivity NMS
applications
• Between multiple instances of Call View
• Between the CallView graphical and tabular view
• Between the CallCount graphical and tabular view
• Between the CallView and CallCount views
To show the relationship between CallView and CallCount views:
1 From the Call View menu bar, choose Options and check the Remote
Selection setting.
If the Remote Selection command is not checked, choose it. If a check
appears next to the Remote Selection command, close the menu without
choosing any of the commands.
2 Open both a CallView and a CallCount view.

The views can be either graphic or tabular.

• In the CallView window, click an ATM entity.
The corresponding ATM switch is highlighted in the CallCount view.
• In the CallCount window, click an ATM object.
The corresponding ATM entities are highlighted in the CallView view.

To show the relationship between CallView and CallCount views and another
Optivity NMS application:
1 From the Call View menu bar, choose Options and check the Remote
Selection setting.
If the Remote Selection command is not checked, choose it. If a check
appears next to the Remote Selection command, close the menu without
choosing any of the commands.
2 In the other Optivity NMS application, make sure that Remote Selection is
also enabled.
3 Open a CallView and CallCount graphical or tabular view.
• In the CallView window, click an ATM entity.
The corresponding ATM switch is highlighted in the CallCount view and
in the Optivity NMS application view.
• In the CallCount window, click an ATM object.
The corresponding ATM entities are highlighted in the CallView view and
the corresponding ATM switch is highlighted in the Optivity NMS
application view.
• In the Optivity NMS application view, click an ATM switch.
The corresponding ATM entities are highlighted in the CallView view and
the corresponding ATM switch is highlighted in the CallCount view.
Moving the toolbar
To move the toolbar:
Drag the toolbar to a new location.
To return the toolbar to its default location:
1 Click in a blank part of the toolbar and drag the toolbar into the contents area.
The toolbar redisplays in a horizontal plane.
207569-F
2 Close the toolbar.

The toolbar returns to its default location.
Displaying objects by DNS name
You can configure Call View to identify devices and objects by their DNS names,
where the DNS names are available. Where DNS names are not available, IP
addresses are used instead.
There are two ways you can configure the display of DNS names:
• You can set the Call View options for the display of DNS names in the current
instance of Call View. Your settings apply only to the current view and are
discarded when you close Call View. For more information, see “Setting the
DNS name display option‚” next.
• You can set the default for the display of DNS names. Your settings are saved
in the Optivity database, and are applied whenever you run Call View. For
more information, see “Setting the DNS name display default” on page 623.
Setting the DNS name display option
You can set the Call View options for the display of DNS names in the current
instance of Call View. Your settings apply only to the current view and are
discarded when you close Call View.
To set the display of DNS names for the current view:
On the Call View menu bar, choose Options > Show DNS Names to turn the
DNS name setting on or off.
A check mark appears next to the menu selection when the option is selected.
Setting the DNS name display default
You can set the default for the display of DNS names. Your settings are saved in
the Optivity database, and are applied whenever you run Call View.
To set the default for the display of DNS names:
1 On the Call View menu bar, choose Options > Set Preferences

The Set Preferences dialog box (Figure 240) opens.
Figure 240 Set Preferences dialog box
For detailed information about the Set Preferences dialog box, click Help in
the dialog box.

• Select the Display DNS Names check box to identify devices or objects
by their DNS names where available.
• Click to clear the Display DNS Names check box to identify devices or
objects by their IP addresses.
3 Click OK.
Working with ATM calls

The following sections describe Call View operations you can use with ATM
calls:
• “Analyzing CallView calls with Call Delta‚” next

• “Filtering ATM calls” on page 625
207569-F
Analyzing CallView calls with Call Delta
Call Delta is a CallView layer feature that uses colors to display the difference
between current calls and the previous calls. Table 136 shows the colors displayed
by Call Delta.
Table 136 Call Delta colors
Color Description
Red A new call or a call that is different from the previous poll.
Yellow The call has been dropped.
Green No change from previous poll.
To use Call Delta to display the difference between current and previous calls:
1 From the Call View menu bar, choose View > Call Delta.
2 On the toolbar, click Refresh.
Call View displays the current calls.
Filtering ATM calls
Call View lets you choose what type of ATM calls to display. Call View displays
the following type of calls:
• SVC/PVC
• LANE control/LANE data
• Point-to-point and point-to-multipoint
The default setting is to show all calls.
To filter ATM calls from the View menu:
1 Open a CallView graphical view.

2 From the Call View menu bar, choose View > Show Calls.
The Show submenu opens.
3 Click one of the menu selections to start the filter.

To filter ATM calls from the toolbar:

2 On the toolbar, click one of the call filters.
Working with graphical and tabular views
The following sections describe how to use Call View graphic and tabular views:
• “Displaying a CallView or CallCount graphical view‚” next

• “Displaying a CallView or CallCount tabular view” on page 627
• “Displaying a call table” on page 627
• “Resizing tabular columns” on page 627
• “Repositioning tabular columns” on page 628
• “Sorting the CallView/CallCount table” on page 628
• “Closing a view” on page 629
Displaying a CallView or CallCount graphical view
To display the CallView graphical view:
• From the Call View menu bar, choose View > Graphical View > CallView
Graphical View.
• On the toolbar, click CVGraph.
To display the CallCount graphical view:
• From the Call View menu bar, choose View > Graphical View>
CallCount Graphical View.
• On the toolbar, click CCGraph.
207569-F
Displaying a CallView or CallCount tabular view
To display the CallView tabular view:
• From the Call View menu bar, choose View > Tabular View > CallView
Tabular View.
• On the toolbar, click CVTable.
To display the CallCount Tabular view:
• From the Call View menu bar, choose View > Tabular View> CallCount
Tabular View.
• On the toolbar, click CCTable.
Displaying a call table
To display a call table for a particular node:

2 In the graphical view, click a node.
3 Right-click the selected node.
The Call Table opens.
Resizing tabular columns
To set the width of a column:
1 Display a folder view in the tabular display format.

• Drag the divider between column heads to the right to enlarge the column.
• Drag the divider between the column heads to the left to reduce the size of
the column.

Figure 241 shows the column head divider. Ellipses indicate that information
in the column is truncated.
Figure 241 Resizing tabular columns
Repositioning tabular columns
You can reposition tabular columns to view more information.
To reposition a table column:
Position the pointer over the column head and drag the column to the new
location.
Repositioning is effective for only the current view. Repositioning is lost

when you close the view.
Sorting the CallView/CallCount table
To sort a CallView or CallCount table:
Click the column heading.
If the column contains numbers, the column and table are sorted numerically. If
the column contains letters, the column and table are sorted alphabetically.
207569-F
Closing a view
To close a view:
• Click the window icon, and from the submenu, choose Close.
• Click the close button at the far right of the title bar.
All customized size settings and the data displayed in the table are cleared when
you close the table.
Working with object attributes
The following sections describe how to use Call View object attributes:
• “Displaying the object shortcut menu‚” next

• “Displaying object attributes” on page 629
• “Displaying link attributes” on page 630
Displaying the object shortcut menu
To display the object shortcut menu:
In the CallView graphical view, right-click an ATM object.
Displaying object attributes
To display ATM object attributes:
1 Open a CallView graphical or tabular view.

2 In the graphical or tabular view, right-click an ATM object.
3 Choose Show Attributes.

The View an object Attributes dialog box (Figure 242) opens.

Figure 242 View an Object Attributes dialog box
For detailed information about the View an object Attributes dialog box, click
Displaying link attributes
To display ATM link attributes:
1 Open a CallView graphical or tabular view.

2 In the graphical or tabular view, right-click an ATM link.
3 Choose Show Attributes.

The Link Object Attributes dialog box (Figure 243) opens.
207569-F
Figure 243 Link Object Attributes dialog box
For detailed information about the Link Object Attributes dialog box, click
Printing with Call View

The following sections describe how to print Call View views and tables:
• “Printing a view‚” next

• “Printing the call table” on page 632
Printing a view
To print a view:
1 Open a view.
2 Group and resize the view as appropriate.
3 From the Call View menu bar, choose File > Print.

4 Set the print options you want to use.

5 Click OK.
Printing the call table
To print the call table:
1 Right-click an ATM object.

2 Choose Show Call Table.

The selected ATM object call table opens.
3 From the Call View menu bar, choose File > Print.
4 Set the print options you want to use.

5 Click OK.
Troubleshooting Call View

The following sections describe how to investigate and resolve Call View
problems:

• “Call View messages” on page 633
207569-F
Resolving problems
Table 137 describes how to resolve problems.
Table 137 Common Call View problems and solutions
Problem Solution
Connection error: connection refused. Check that OptWeboptsrvr is running.

Connection failure: invalid user name. Type the correct user name.
Connection failure: authentication failed. Type the correct user name and password.
Call View messages
Table 138 describes the messages displayed in the Call View status bar.
Table 138 Call View messages
Message Description
SNMP polling for Call View is searching for the ATM object.
[IP-address] completed On the toolbar, click Stop to terminate the
operation.
No Objects found in The specified ATM object is not in the database.
DataBase From the InfoCenter application, open the Object
Properties dialog box and add the device.
No ATM Clients found The object is not on an ELAN.
ATM Call View process Call View server finished processing ATM Calls.
done
Processing ATM CallView Call View is processing ATM calls.
On the toolbar, click Stop to terminate the
operation.

207569-F
635
Chapter 18
Managing events with Fault Summary
This chapter is organized into the following major sections:
• “Fault Summary overview‚” next

• “Getting started with Fault Summary” on page 636
• “Working with Fault Summary” on page 648
• “Troubleshooting Fault Summary” on page 679
Fault Summary overview

Fault Summary reports information about network events that you can use to
evaluate network performance.
Table 139 describes the types of events reported by Fault Summary.
Table 139 Event types reported by Fault Summary
Event type Description
Faults Faults are network events reported by the Fault Correlator engine
running on the Optivity NMS server. The Fault Correlator evaluates
incoming SNMP traps and correlates the information in them to
determine most likely probable cause. Fault Correlator then passes the
faults to the Fault Summary application running on the Optivity NMS
client.
Syslog events Syslog events are events reported by devices with the Syslog protocol
described in RFC 3164. Fault Summary reports syslog events
as-received, without any correlation or processing.
Traps In addition to reporting faults that are correlated from SNMP traps, Fault
Summary also reports the raw traps without correlation.

636 Chapter 18 Managing events with Fault Summary
See “Event color codes‚” next for information about the color codes that Fault
Summary uses when reporting these events.
Event color codes
Table 140 describes the color coding of the various event types.
Table 140 Event color codes
Event type Color State
Fault Red Active + Critical

Colored based Orange Active + Medium
on event state
and severity Yellow Active + Low
Blue Cleared, Aged, Unmonitored
Trap Blue Critical
Colored based Medium
on severity
Low
Syslog Red Emergency (0) and Alert (1)
Colored based Orange Critical (2) and Error (3)
on Syslog
severity Yellow Warning (4) and Notice (5)
Blue Info (6) and Debug (7)
Getting started with Fault Summary

See the following sections for information about getting started with Fault
Summary.
• “Starting Fault Summary‚” next

• “Fault Summary window” on page 640
207569-F
Chapter 18 Managing events with Fault Summary 637
Starting Fault Summary
To start Fault Summary:
Table 141 Starting Fault Summary
To start
Fault
Summary
from: Do this:
InfoCenter Opening Fault Summary views from InfoCenter lets you view faults, traps, or syslog
messages pertaining to a selected device or protocol. Opening a Fault Summary view starts
the Fault Summary application, and also opens a filter window inside Fault Summary to
display the selected event view. If the Fault Summary application is already running when you
open a Fault Summary view, that view is opened within the Fault Summary application that is
already running.
Use one of the following methods to start Fault Summary from InfoCenter:
Menu bar Select an InfoCenter folder or object and choose one of the following:
• Tools > Fault > Events > Trap View to view SNMP traps
• Tools > Fault > Events > Syslog View to view Syslog events
• Tools > Fault > Events > Fault View to view correlated faults
Shortcut Right-click an InfoCenter folder or object and choose one of the following:
menu • Fault > Events > Trap View to view SNMP traps
• Fault > Events > Syslog View to view Syslog events
• Fault > Events > Fault View to view correlated faults
InfoCenter Select an InfoCenter folder or object and click the Fault Category Apps
Launchpad launchpad icon.
If more than one fault application applies to the selected element, the
Selection dialog box opens. Choose one of the three Events selections.
Windows Choose Start > Programs > Optivity > Fault Summary
Start menu
command
prompt faultsummary [optional commands]

Table 141 Starting Fault Summary (continued)
To start
Fault
Summary
from: Do this:
command
prompt faultsummary [optional commands]
Click the Fault Summary icon on the Optivity Web page.
Note: You can use your Web browser’s Bookmark or Favorites feature to bookmark the Fault
Summary application. Doing so saves the URL for Fault Summary.
Table 142 describes the optional commands for starting Fault Summary from
a Windows or UNIX command line.
Table 142 Fault Summary command line options
Option Usage
-help Displays syntax and usage for the faultsummary

command.
-debug [debuglevel] Opens Fault Summary in debug mode, which
displays and logs debugging information for
troubleshooting. The debuglevel parameter is an
integer that sets the level of detail. The
debuglevel ranges from 0 (least detail) to 3
(greatest detail).
-s server Specifies the IP address of the Optivity NMS
server
-u user [-password password] Specifies the Optivity NMS user name and
password
-t eventtype Specifies the type of event window to open in
Fault Summary. Options are:
• Fault
• Trap
• Syslog
207569-F
If you are not starting Fault Summary from InfoCenter, the Connect to
Optivity Server dialog box opens.
The Fault Summary window opens.
Access permissions for Fault Summary
To use Fault Summary, your Optivity user name must have the FS_ACCESS
permission token attached with either read/write or read-only access permission.
With read/write permission, you have full access to all Fault Summary functions.
With read-only access permission, you can:
• Open Fault Summary

• View event reports
• Create local filters
An Optivity NMS administrator sets user access to the Fault Summary window by
configuring access to the FS_ACCESS token in the Access Control
Administration window. For more information about using Access Control
Administration, see Chapter 2, “Specifying access to Optivity NMS applications
with Access Control Administration,” on page 75.

Fault Summary window
Figure 244 shows a typical Fault Summary window.
Figure 244 Typical Fault Summary window
Menu bar and

toolbar
Navigation
pane and filter
tree
Filter window
Contents pane
Status Bar
Table 143 describes the parts of the Fault Summary window:
Table 143 Parts of the Fault Summary window
Part Description
Menu bar and Provides access to all available Fault Summary commands. “Menu
toolbar bar and toolbar‚” next for more information.
Navigation pane and Lets you organize Fault Summary filters. See “Navigation pane
filter tree and filter tree” on page 644 for more information.
Contents pane Displays filter windows containing filter results. See “Contents
pane” on page 645 for more information.
207569-F
Table 143 Parts of the Fault Summary window (continued)
Part Description
Filter window Displays filter results. See “Filter window” on page 645 for more
information.
Status Bar The status bar shows you the current status of the Fault Summary
application:
• The IP address or hostname of the Optivity NMS server
• The user name you are logged in as
• Your access privileges in Fault Summary (R or R/W)
When you run Fault Summary in a UNIX or Windows environment, the menu bar
provides the seven menus as shown in Table 144. If you open Fault Summary in a
Web browser, the menu bar does not display. Instead, you use the Menu tool on
the toolbar to open a shortcut menu of Fault Summary menus.
Toolbar
File Save Filters Saves the current filters on the Optivity NMS server. For more
information, see “Saving Filters” on page 657.
Save Events Opens a submenu that lets you save all of the events in the
As database in any of the following formats:
HTML
XML
CSV (comma separated values)
TSV (tab separated values)
Close Closes the selected filter window in the contents pane.
Print Prints the contents of the selected filter window in the contents
pane.
Page Setup Lets you set printing parameters for Fault Summary.
Exit Closes the Fault Summary window.
Display Displays or hides the toolbar. When the toolbar is displayed, it is
Toolbar located under the menu bar.

Toolbar
View Display Displays or hides the toolbar. When the toolbar is displayed, it is
Toolbar located under the menu bar.
Display Displays or hides the status bar at the bottom of the window.
Status Bar
Look and Lets you choose any of three window styles:
Feel Metal
CDE/Motif
Windows
First Page Opens the first page of events in the active window of the contents
pane. See “Paging through filter results” on page 654 for more
information.
Next Page Opens the next page of events in the active window of the contents
pane. See “Paging through filter results” on page 654 for more
information.
Previous Opens the previous page of events in the active window of the
Page contents pane. See “Paging through filter results” on page 654 for
more information.
Refresh Redisplays all open event windows with the most recent events,
Events updated events, or new events. Does not redisplay a window that
contains events from a Load All operation. See “Refreshing
displayed events” on page 652 for more information.
Events Event Details Opens a details dialog box to show you detailed information about
the event. For more information, see “Viewing event details” on
page 650.
Unmonitor Opens the Unmonitor Event dialog box to let you unmonitor the
Event(s) selected events. For more information, see “Unmonitoring events”
on page 650.
Delete Deletes the selected events. See “Deleting events” on page 652 for
Event(s) more information.
Delete All Deletes all events.

Events
207569-F
Toolbar
Filters Execute Executes the selected filter. For more information, see “Executing
Filter filters” on page 653.
Edit Filter Opens the Filter Design window to let you edit the selected filter. For
more information, see “Creating a new filter” on page 657.
New Filter Opens the Filter Design window to let you create a new filter. This
button is only available when you select a folder to which you are
allowed to add filters. For more information, see “Creating a new
filter” on page 657.
New Filter Creates a new folder on the filter tree.
Folder
Rename Lets you rename the selected filter or folder.
Delete Deletes the selected filter or folder. See “Deleting filters or folders
from the filter tree” on page 655 for more information.
Options Trap Opens the Configure Trap Forwarding dialog box to let you configure
Forwarding trap forwarding. For more information, see “Configuring trap
forwarding” on page 678.
Fault Scripts Opens the Configure Fault Scripts dialog box to let you configure a
fault script. For more information, see “Configuring scripts” on
page 671.
Preferences Opens the Fault Summary Preferences dialog box to let you set your
preferences for using Fault Summary. See “Setting Preferences” on
Window Tile Tiles the windows in the contents pane.
Cascade Cascades the windows in the contents pane.
Restore Restores the windows in the contents pane.
Close All Closes all of the windows in the contents pane.
window list Shows you a list of all filter widows currently open.
Help Fault Opens online Help for Fault Summary.
Summary
Help
About Fault Displays copyright and version information about Fault Summary.
Summary

Positioning the toolbar
The Fault Summary toolbar provides quick access to commonly-used menu

commands. You can move the toolbar to a new location.
To move the toolbar:
Drag the toolbar to a new location.
To move the toolbar back to its default location:
Close the toolbar.
Navigation pane and filter tree
The Fault Summary navigation pane and filter tree (Figure 245) let you organize
filters into a hierarchy using folders and subfolders.
Figure 245 Navigation pane and filter tree
Events folder
Faults folder
User-created
folder
Dynamic folder
Filter (closed)
Filter (open)
Syslog folder
Traps folder
207569-F
Table 145 describes the parts of the navigation pane:.
Table 145 Parts of the Fault Summary navigation pane
Part Description
Events folder This default folder contains subfolders and filters for all events
reported by Fault Summary.
Faults folder This default folder contains subfolders and filters for faults
reported to Fault Summary by the Fault Correlator engine
running on the Optivity server.
User-created folder You can organize folders and filters by creating your own
subfolders. See “Adding folders to the filter tree” on page 655 for
more information.
Dynamic folder Contains filters for views opened for the network elements that
were selected when opening Fault Summary from InfoCenter.
Filter Tests events in the Optivity database against specified criteria.
For more information, see “Using filters” on page 653 and
“Creating and modifying filters” on page 656 for more
information.
Open filter Indicates that the contents pane is currently displaying the filter
results in a filter window.
Closed filter Indicates that the filter is not currently open.
Syslog folder This default folder contains subfolders and filters for syslog
events.
Traps folder This default folder contains subfolders and filters for SNMP
traps.
Contents pane
The contents pane displays the filter windows that you have opened. You can use
the commands on the Window menu to arrange the filter windows in the contents
pane.
Filter window
You open filter windows in the contents pane to display filter results. Each filter
window displays the results of executing the selected filter against the events
currently in the database.
There are three types of filter windows; one for each type of event:

• Faults
• Traps
• Syslogs
To open a filter window, do one of the following:
In the navigation pane, double-click on a filter

In the navigation pane, right-click on a filter and choose Execute Filter from
the shortcut menu.
In the navigation pane, select a filter. Then, from the menu bar choose
Filters > Execute Filter
In the navigation pane, select a filter. Then, on the toolbar click Execute
Filter
The following sections describe parts of the filter window:
• “Filter window toolbar‚” next

• “Filter window status bar” on page 647
Filter window toolbar
Each filter window contains a toolbar that you can use to execute commands
specific to the contents of the window. The following table lists and describes the
parts of the filter window toolbar.:
Table 146 Filter window toolbar
Tool Name Description
Page Size Sets the number of events displayed on each

page of the filter window. See “Paging through
filter results” on page 654 for more information.
First Page Opens the first page of events in the filter window.
See “Paging through filter results” on page 654 for
more information.
Previous Opens the previous page of events in the filter
Page window. See “Paging through filter results” on
Next Page Opens the next page of events in the filter window.
See “Paging through filter results” on page 654 for
more information.
207569-F
Table 146 Filter window toolbar
Refresh Redisplays all open event windows with the most

recent events, updated events, or new events.
See “Refreshing displayed events” on page 652
Edit Filter Opens the Filter Design window to let you edit the
selected filter. For more information, see
“Creating a new filter” on page 657.
Save Filters Saves the current filters. For more information,
see “Saving Filters” on page 657.
Filter window status bar
The filter window status bar (Figure 246) is located at the bottom of the filter
window inside the Fault Summary contents pane.
Figure 246 Filter window status bar
The filter window status bar shows you the following information about the events
you are currently viewing:
• The number of events on the current page

• The total number of events in the view
• The number of the current page

Working with Fault Summary

See the following sections for information about working with Fault Summary:
• “Setting Preferences‚” next

• “Working with events” on page 649
• “Using filters” on page 653
• “Organizing filters with the filter tree” on page 654
• “Creating and modifying filters” on page 656
• “Working with fault scripts and trap forwarding” on page 671
Setting Preferences
To set Fault Summary preferences:
1 From the menu bar, choose Options > Preferences.

The Fault Summary Preferences dialog box opens.
2 Set your preferences for the settings described in Fault Summary
preferencesTable 147.
Table 147 Fault Summary preferences
Tab Option Description Default
General Enable tool tips Enables pop-up text that describes Enabled
toolbar buttons
Default page size Sets the number of rows in filter 50 rows
windows
Look & feel Sets the graphic interface style. Metal
Fault Fault notification Sets whether your computer beeps Disabled
beep when a fault is received.
207569-F
Table 147 Fault Summary preferences
Tab Option Description Default
Syslog Syslog Sets whether your computer beeps Disabled

notification beep when a Syslog message is received.
Syslog message Sets the name of the file where Location provided
file name Syslog messages are read from (only to installation
relevant for UNIX server installation) program
Syslog message Sets the interval at which the Syslog 20 seconds
file read interval message file is read (only relevant for
UNIX server installation).
Syslog message Sets the interval at which the Syslog 12 hours
purge cycle time messages are purged from the
Optivity database.
Trap Trap notification Sets whether your computer beeps Disabled
beep when an SNMP trap is received.
Trap purge cycle Sets the interval at which SNMP traps 12 hours
time are purged from the Optivity
database.

• Click OK to save your settings
• Click Cancel to discard your settings
• Click Reset to restore the settings as they were when you opened the Fault
Summary Preferences dialog box.
• Click Set to Default to restore the settings to the default settings described
in Table 147.
Working with events

See the following sections for information about working with events in Fault
Summary:
• “Viewing events‚” next

• “Viewing event details” on page 650
• “Unmonitoring events” on page 650
• “Deleting events” on page 652
• “Refreshing displayed events” on page 652

Viewing events
In Fault Summary, you view events by executing filters on the events in the
Optivity database. The results of the filter operation are shown in a filter window
that opens in the contents pane of the Fault Summary window.
Note: When you view events, Fault Summary only shows you events for
devices within your view domains.
For information on executing filters, see “Executing filters” on page 653.
Viewing event details
To view detailed information about an event:
In a Filter window, double-click the fault, trap, or syslog event.
Fault Summary opens one of the following dialog boxes, depending on the type of
event:
• Fault Details dialog box

• Trap Details dialog box
• Syslog Details dialog box
Unmonitoring events
You can change the status of active or escalated faults. You make the faults
unmonitored and select to have the fault deleted after a specified amount of time.
Marking a fault as unmonitored is useful in the following circumstances:
• You have fixed the fault.

• You consider a particular fault to be unimportant, and do not want it to
contribute to the state of the device.
• You do not want to wait for the normal age-out of the fault, and want to
acknowledge (Unmonitor) the fault immediately to prevent it from
contributing to the state of the device.
207569-F
Fault Summary lets you change the status of faults to “Unmonitored.” You can
delete unmonitored faults from the database.
To cause a fault to be unmonitored:
1 Select one or more faults by clicking, dragging, or using Shift+click or

Ctrl+click.
2 Right-click any selected fault and choose Unmonitor Events from the shortcut
menu.
The Unmonitor Event(s) dialog box opens (Figure 247).
Figure 247 Unmonitor Event(s) dialog box
For detailed information about the Unmonitor Event(s) dialog box, click Help
in the dialog box.
3 From the time list, choose the unit of measure for time.
The unit of measure you selected is displayed.
4 In the Time box, type the time the fault is to remain unmonitored.
5 To delete the fault automatically after the unmonitored fault time, click Delete
Fault.
After the time period you entered expires, Fault Summary deletes the fault.
6 Click OK.
• From the Fault Summary menu, choose Options > Refresh.
• On the Fault Summary toolbar, click Refresh.

The Fault Summary window is updated with the latest faults. The
unmonitored fault transitions to the Unmonitored state or is deleted.
Deleting events
To permanently delete one or more events from the Optivity database:
1 In a filter window, select the event or events that you want to delete.
You can click a single event, or use Shift+click or Ctrl+click to select multiple
events.

• Right-click any of the selected events and choose Delete Events from the
shortcut menu.
• On the Fault Summary toolbar, click Delete Events.
• From the Fault Summary menu bar, choose Events > Delete Events.
An alert box (Figure 248) opens to prompt you to confirm that you want to
permanently delete the events.
Figure 248 Delete Event(s) alert box
3 Click OK to delete the events.
Refreshing displayed events
To refresh the Fault Summary window and display the latest faults:
• From the Fault Summary menu bar, choose Options > Refresh.
207569-F
• On the toolbar, click Refresh.
Using filters
Fault Summary filters are collections of conditions and operators you use to test
events to see if they match specified criteria. Each filters consists of a set of
properties organized into logical groups and connected by boolean expressions.
See the following sections for information about using filters:
• “Executing filters‚” next

• “Paging through filter results” on page 654
• “Sorting filter results” on page 654
See “Creating and modifying filters” on page 656 for information about creating
your own custom filters or modifying existing filters.
Executing filters
Executing a filter tests all of the faults, syslog events, or traps in the Optivity
database against the criteria in the filter. Fault Summary then opens a new Filter
window in the contents pane of the Fault Summary window to display the results
of the filter operation.
Note: When you execute filters, Fault Summary only shows you events
for devices within your view domains.
To execute a filter:
1 Select the filter in the filter tree.

For more information, see “Fault Summary window” on page 640.
• Double-click the filter
• On the toolbar, click Execute Filter.
• From the Filters menu, choose Execute Filter

• Right-click the selected filter and choose Execute Filter from the shortcut
menu.
Fault Summary opens a Filter window containing the results of the filter
operation.
Paging through filter results
When the number of events selected by a filter is greater than the page size, Fault
Summary splits the results up into multiple pages.
You can page through the filter results previous page, first page, and next page on
the toolbars of either the Filter window or the Fault Summary window. See
“Positioning the toolbar” on page 644 for more information.
Sorting filter results
You can sort filter results by the values in any column by clicking the column
headers in the Filter window where the results are displayed. Click the column
header once to sort the results in ascending order by the values in the column.
Click the header again to sort in descending order.
After sorting results, an arrow displays in the heading of the column by which the
results were sorted. The direction of the arrow (up or down) indicates whether the
results are in ascending or descending order.
Organizing filters with the filter tree
The filter tree in the navigation pane of the Fault Summary window lets you create
and maintain an organized hierarchy of filters. See the following sections for more
information about the filter tree:
• “Adding folders to the filter tree‚” next

• “Deleting filters or folders from the filter tree” on page 655
• “Saving filters to different locations on the filter tree” on page 655
207569-F
Adding folders to the filter tree
To add a folder to the filter tree:
1 In the navigation pane, click on the folder to which you want to add the new
folder.
• Right-click on the folder and choose Add Filter Folder from the shortcut
menu.
• From the menu bar, choose Filters > New Filter Folder.
Deleting filters or folders from the filter tree
To delete a filter or folder from the filter tree:
1 In the navigation pane, click on the filter or folder you want to delete.
• Right-click on the filter or folder and choose Delete from the shortcut
menu.
• From the menu bar, choose Filters > Delete.
Fault Summary opens an alert box to prompt you to confirm you want to
delete the filter or folder.
3 Click OK.
Saving filters to different locations on the filter tree
Fault Summary does not let you move filters to different locations on the filter
tree. However, you can achieve the same result by opening a filter, saving it to the
desired folder, and then deleting the original filter as described below.
Note: Fault Summary only lets you save filters within appropriate
branches of the filter tree. For example, you can only save fault filters on
fault branches of the tree.

To save a filter to a different location on the filter tree:
1 In the navigation pane, select the filter you want to save to a new location.
2 Do one of the following to execute the filter:
• Double-click the filter
• Right-click the filter and choose Execute Filter from the shortcut menu
• On the toolbar, click Execute Filter
• From the menu bar, choose Filters > Execute Filter
See “Executing filters” on page 653 for more information.
Fault Summary executes the filter, and opens a Filter window for the results in
the Contents pane of the Fault Summary window.
3 On the Filter window toolbar, click Save Filter.
A Save dialog box opens.
4 In the Save dialog box, navigate to the folder where you want to save the filter.
5 In the Filter Name box, enter the name for the filter.
6 Click Save.
Fault Summary saves a copy of the filter to the selected folder, and also opens
a new filter window for the new copy.
Creating and modifying filters
Fault Summary filters are collections of conditions and operators you use to test
events to see if they match specified criteria. Each filter consists of a set of
properties organized into logical groups and connected by boolean expressions.
In addition to using the default filters that are supplied with Fault Summary, you
can also modify the default filters, or create your own filters.
See the following sections for more information about creating and modifying
Fault Summary filters:
• “Opening an existing filter for editing‚” next

• “Creating a new filter” on page 657
• “Saving Filters” on page 657
207569-F
• “Understanding filter elements” on page 658

• “Event filter example” on page 669
Opening an existing filter for editing
To open an existing filter for editing:
1 In the filter tree, select the filter you want to edit.

• Right-click the filter and choose Edit Filter from the shortcut menu
• On the toolbar, click Edit Filter
• From the menu bar, choose Filters > Edit Filter
Fault Summary opens the filter for editing in the Filter Design window.
Creating a new filter
To create a new filter:
1 In the navigation pane, select the folder in which you want to create a new
filter.
• Right-click the folder and choose Add Filter from the shortcut menu
• On the toolbar, click New Filter
• From the menu bar, choose Filters > New Filter
Fault Summary opens the Filter Design window, where you compose the new
filter.
Saving Filters
Fault Summary saves filters in the Optivity database on the Optivity server.
To save the current filters, do one of the following:
On the toolbar, choose Save Filters

On the menu bar, choose File > Save Filters

Understanding filter elements
See the following sections for more information about the elements that make up
filters:
• “Understanding logical AND and OR groups‚” next

• “Understanding the NOT operator” on page 660
• “Understanding property filters” on page 660
• “Understanding property filter relationships” on page 664
Understanding logical AND and OR groups
Logical groups let you collect and arrange the operators in a filter. You can think
of logical groups as simply parentheses. Any time you add a logical group to a
filter, Fault Summary inserts both the opening and closing parentheses of the
group.
There are two types of logical groups: AND groups and OR groups. Table 148
describes the basic properties of the different group types.
Table 148 Types of logical groups
Group type Description
AND Combines property filters using boolean AND. The group is evaluated as
true only when all of the conditions of all of the property filters it contains are
met.
OR Combines property filters using boolean OR. The group is evaluated as true
when any of the property filters it contains are met.
The following figure shows an empty logical group. The group shown is the
default logical group included whenever you create a new filter. The “AND” label
just inside the opening parenthesis tells you that this is an AND group.
207569-F
Figure 249 Empty AND group (default group), shown with 2x magnification.
For filters containing only single properties, you can use either group type
interchangably. For example, the following two filters are equivalent, and produce
identical results:
Figure 250 Equivalent single-property groups
However, for any group that contains more than a single operator, AND and OR
groups are not equivalent. For example, the filters shown in Figure 251 are not
equivalent, and produce different results:
Figure 251 Non-equivalent multi-property groups
Fault Summary adds the AND and OR operators (as shown in the previous
example) whenever you add more than one property to a logical group.

Understanding the NOT operator
In addition to the AND and OR operators, you can also use the boolean NOT
operator to negate the evaluation of logical groups. Figure 252 shows a negated
group.
Figure 252 Negated group
The conditions of this sample filter are met by any event for which the status is not
New.
Note that for logical groups containing a single property, it is usually easier and
simpler to select a “does not equal” relationship such as < > instead of using the
NOT operator. However, for groups containing multiple properties, it is usually
better to use a NOT operator (Figure 253).
Figure 253 Negating a single property with the <> relationship
For a detailed example of how logical groups are used to construct complex
boolean expressions, see “Event filter example” on page 669.
Understanding property filters
Property filters are conditions that events are tested against when a filter is
executed.
207569-F
Table 149 describes the properties and values you can use when creating filters.
Table 149 Property filters
Filter Values Description
Agent DNS valid hostname DNS host name

Agent IP valid IP address IP address of the agent that reported the event
Assignee text string Name of the person assigned to the event
Category Connectivity Connection between devices. For example, a
link has gone down because a modem failed.
Errors Errors occurring on the device. For
example, the service port is down and out
of service.
Components State of one or more physical components of
the device. For example, a power supply has
failed.
Load The traffic load on the device. For example, a
Network Management Module becomes
saturated with an unusually high amount of
traffic.
Security Security of the device. For example, an attempt
has been made to contact a station having a
restricted access.
Config Configuration of the network that the device is
connected to. For example, an FDDI topology
change has occurred.
Other
Create date Click on ... to choose Date the event occurred
the date from a
calendar
Device label valid device label The device label
Device name text string The name of the device
Device subtype text string The device subtype
Device date and time The device timestamp (syslog filters only)
timestamp
Device type text string The device type
Enterprise OID text string SNMP object identifier (trap filters only)
Facility text string The device facility (syslog filters only)
Generic type integer The generic device type (trap filters only)

Table 149 Property filters (continued)
NMS DNS text string The DNS name of the network management
station that received the event.
NMS IP IP address The IP address of the network management
station that received the event.
Protocol protocol Protocol type of the fault. For example, the
protocol field shows token IST for IST link
down fault. Possible values are IST, SMLT,
OSPF, and DVMRP.
Reviewed Set or clear the check
box
Severity 0 - Low The device has a low severity problem.
(for faults) 1 - Low
2 - Low
3 - Low
4 - Medium The device has experienced a nonfatal error or
condition.
5 - Medium
6 - Medium
7 - Medium
8 - Medium
9 - Medium
10 - High The device has failed or is about to fail.
Severity 7 - Debug SNMP severity level
(for traps) 6 - Info
5 - Notice
4 - Warning
3 - Error
2 - Critical
1 - Alert
0 - Emergency
Unknown
207569-F
Slot Port S<slot The slot/port information; only for link

number>P<port down/up faults. Format is S<slot
number> number>P<port number>, for example
S2P10.
Specific type text string The specific device type (trap filters only)
State Active For increment faults, the fault correlator
received the required number of traps to
make the fault active. For toggle faults, the
fault correlator received the SET trap.
Escalated Valid only for increment faults. For each
trap received the fault correlator
increments the severity by 1. When the
maximum severity is reached the fault will
be transitioned from active state to
escalated state.
Cleared Valid only for toggle faults. When the fault
correlator receives the CLEAR trap the
fault state will be transitioned from active
state to cleared state.
Aged No more fault events have been received
during the interval specified in its aging
rules. All new traps become new faults.
Unmonitored Either the Fault Correlator has been restarted,
in which case it can no longer monitor the
current state of all previously reported active
and escalated faults, or you have set a fault
report to unmonitored by using the Unmonitor
Fault command.
Status New Fault is new
Assigned Fault is assigned to a person
Fixed Fault is fixed
Rejected Fault is rejected
Closed Fault is closed
Acknowledged Fault is acknowledged
System name text string The system name
System text string The system timestamp (syslog filters only)
timestamp
Tag text string The device tag (syslog filters only)

Traps text string The number of traps correlated into the fault
Vendor text string The vendor ID of the reporting device
Understanding property filter relationships
For most property filters, in addition to choosing a property filter and a value, you
can also choose the relationship between the property and the value. Table 150
describes the relationships available for most property filters.
Table 150 Typical property filter relationships
Relationship Description
= Equals
<> Does not equal
> Greater than
< Less than
>= Greater than or equal to
<= Less than or equal to
Working with filter elements
See the following sections for more information composing filters by combining
filter elements:
• “Adding a logical group to a filter‚” next

• “Changing the logical group type” on page 665
• “Negating the logical group type” on page 666
• “Adding a property filter” on page 667
• “Deleting a logical group or property filter” on page 668
207569-F
Adding a logical group to a filter
The Filter Design window lets you add new AND groups to a filter. If you want to
add an OR group, you must first add an AND group, and then change its type to
OR. See “Changing the logical group type‚” next for more information.
To add a logical group to a filter:
In the Filter Design window, right-click on the opening parenthesis of the

group above where you want to add the new group and choose Add Logical
Group from the shortcut menu.
Fault Summary adds a new AND group to the filter.
Changing the logical group type
After adding a logical group, you can change its type from AND to OR or from
OR to AND.
To change the logical group type:
1 In the Filter Design window, right-click on the group opening parenthesis and
choose Change Group Type from the shortcut menu.
2 Choose the group type from the submenu (Figure 254).
Figure 254 Change Group Type submenu
Fault Summary changes the group to the selected type.

Negating the logical group type
After adding a logical group, you can negate it using a logical NOT operator. You
can also remove negation from a negated group.
To negate a logical group:
In the Filter Design window, right-click on the group opening parenthesis

and choose Negate from the shortcut menu.
Fault Summary negates the group with a NOT operator (Figure 255).
Figure 255 Negated logical group
To remove negation from a logical group:
In the Filter Design window, right-click on the NOT operator and choose
Remove NOT from the shortcut menu.
Fault Summary removes the NOT operator from the group.
Figure 256 Removing negation from a logical group
207569-F
Adding a property filter
Property filters are conditions that events are tested against when a filter is
executed. See “Understanding property filters” on page 660 and “Understanding
property filter relationships” on page 664 for more information about property
filters.
To add a property filter when creating or modifying a filter:
1 In the Filter Design window, right-click the insertion point for the property
filter and choose Add Property Filter from the shortcut menu.
Fault Summary inserts the default property filter at the insertion point. The
default property filter is “Agent IP = 1.1.1.1”.
2 Click the default property filter.
Fault Summary shows the available property filter values and relationships
(Figure 257).
Figure 257 Selecting property filter options
3 Choose options from the property, relationship, and value menus.

See “Understanding property filters” on page 660 and “Understanding
property filter relationships” on page 664 for more information.
4 Click the OK text to the right of the filter.
Fault Summary shows the finished filter property (Figure 258).

Figure 258 Finished property filter
Editing a property filter
To edit a property filter:
1 In the Filter Design window, right-click the property filter you want to edit
and choose Edit from the shortcut menu.
2 Fault Summary shows the available property filter values and relationships
(Figure 257).
3 Choose options from the property, relationship, and value menus.
See “Understanding property filters” on page 660 and “Understanding
property filter relationships” on page 664 for more information.
4 Click the OK text to the right of the filter.
Fault Summary shows the finished filter property (Figure 258).
Deleting a logical group or property filter
To delete either a logical group or a property filter from a filter:
1 In the Filter Design window, right-click the property filter or logical group
you want to delete and choose Delete from the shortcut menu.
Fault Summary deletes the selected property filter or logical group.
207569-F
Event filter example
This section describes a possible application for a filter, and demonstrates how
you could implement such a filter using the Filter Design window.
Suppose that you want to view all the events for those that were reported by agents
on the subnets 10.127.5.0 and 10.127.9.0. Also, you want to see only the events
reported after 7/1/02, and only those for which 50 or more traps were reported.
But you don’t want to see the events that were acknowledged.
Logically, you could represent these conditions with the following boolean
expression:
(((Agent IP>=10.127.5.1)AND(Agent IP<10.127.5.255))OR((Agent

IP>=10.127.9.1)AND(Agent IP<10.127.9.255))AND(Create Date>=07/01/
2002)AND(Trap Count>=50)AND NOT(Status = Acknowledged)).

Figure 259 shows a filter that embodies the conditions stated above:
Figure 259 Example filter
Note that there is a shortcut that we could have taken regarding the Status
condition. Instead of using the AND NOT operators, it would have been simpler
to just use an AND operator, and for the Status condition use “(Status <>
Acknowledged)” as shown in Figure 260.
Figure 260 Alternate method for negating an operator
207569-F
Working with fault scripts and trap forwarding
Fault Summary provides two ways of configuring automatic responses to

incoming faults. You can configure scripts to run when specific faults are received,
and you can configure forwarding of traps to a specific management station.
See “Configuring scripts‚” next and “Configuring trap forwarding” on page 678
for more information about these features.
Configuring scripts
You can configure scripts that automatically run when certain faults are received
from a certain device. For example, you can configure a script that sends email,
starts a third-party application, or starts another Optivity NMS 10.3 application.
The scripts you enter through Fault Summary are executed by the Script Server
daemon. The Script Server and your scripts reside on the Optivity NMS 10.3
server. You must enter your scripts in a manner consistent with other commands
you would use on that server. For instance, if your Optivity NMS 10.3 server is a
UNIX station, your scripts must comply with UNIX command syntax. If your
Optivity NMS 10.3 server is a Windows station, use MS-DOS compliant
command syntax. Optivity NMS 10.3 does not check the syntax of scripts you
enter in Fault Summary. You must be sure to use the correct syntax, otherwise the
script may not function properly. In all cases, regardless of your server
environment, do not use any spaces or symbols in your script. Use script names in
your system path as described in “Script path guidelines” on page 671 and follow
the instructions in “Script parameter guidelines” on page 673.
Script path guidelines
Your scripts must be located in the system path where the Optivity NMS Fault
Correlator service, or daemon, is running. This system is the same as your
Optivity NMS 10.3 server.
Note: Ideally, your scripts are located in a single directory. If so, you
need only append (add) the path to your scripts once. If your scripts are
located in several directories you must append the path for all locations.

To enable scripts in a Windows environment:
1 From the Windows task bar, choose Start > Settings > Control Panel.
2 Double-click the System icon.
The System Properties dialog box opens.
• For Windows NT, click the Environment tab.
• For Windows 2000, click the Advanced tab and then click the
Environment tab.
4 In the System Variables field, select the Path variable.
5 In the Value field at the bottom of the Environment tab, append the path of
your script(s) to the string of path names.
For instance, enter:
C:\Optivity\NMS\apps\fc\fault_specs\<scriptpath>
where:
scriptpath is the path to the directory where your script is located.
6 Click Set and then click OK.

7 Reboot your system.
To enable scripts in a UNIX environment:
1 Stop the scriptsrv daemon.

• For the C shell, open the ~/.cshrc file and edit the shell search path to
include the following:
setenv PATH ${PATH}:/<path_to_the_script>/<script_name>
• For the Bourne and Korn shell, open the ~/.profile file and edit the shell
search path to include the following:
PATH=${PATH}:/<path_to_the_script>/<script_name>; export PATH
207569-F

• Log out of the shell and login again.
In this case, go to step 5.
• Source the file you just edited.
In this case, go to step 4.
4 To source the file, do one of the following:
• For the C shell, enter:
source ~/.cshrc
• For the Bourne and Korn shell, enter:
source ~/.profile
5 Restart the scriptsrv daemon.
Script parameter guidelines
The defined parameters listed in Table 151 let you configure scripts based on
various fault characteristics.
Table 151 Fault script parameters
Parameter Description
$FAULT_IP The IP address of the object generating the fault.

$FAULT_DESC The description of the fault.
$FAULT_CAUSE The cause of the fault.
$FAULT_TIME The time when the fault was generated.
$FAULT_SEVERITY The severity level of the fault.
$DNS_NAME The DNS name of the object generating the fault.
Fault script example
Be sure you select a fault name from the list of available faults, as it applies to the
device you want to monitor. Specify the IP address from which you want to obtain
fault information. Enter a script for an e-mail program such as Send_email. Select
the parameters for the information you want to obtain.

For instance, if you want to send fault time and cause data about an IP address
using e-mail program Send_email, enter the following in the Executable Name
field:
Send_email
Next, select and move the $FAULT_TIME and $FAULT_CAUSE parameter from
the Available Parameters field to the Selected Parameters field.
For instructions about creating and removing scripts, see “Adding a fault script”
on page 675 and “Deleting a fault script” on page 678.
Refer to Appendix A, “Modifying Fault Correlator startup files,” for information

about modifying Fault Correlator files.
Fault name definitions
Specific faults are defined by the Optivity Integration Toolkit (OIT) files for each
device. The fault names you can choose in the Fault Names list are directly
associated to the OIT files.
For instance, the following fault definition from the associated OIT file provides
the criteria that generate a fault for this device.
Fault "Nortel Device Card Down"

{
Type "Toggle";
Object "DEVICE";
Category "COMPONENTS";
EventThreshold 0;
TimeInterval 0;
AgeTime 0;
MaxSeverity 0; // The above 4 are only for increment type
Description "Card in slot $1 has gone down";
Cause "This trap is sent as a result of a card going out of
service";
Solution "Verify if card was manually pulled out or if the card is
faulty";
FaultVerification
{
MibObject "rcCardOperStatus";
MibType "INTEGER";
MibOid 1.3.6.1.4.1.2272.1.4.9.1.1.6;
Identity 1; // Points to the first trap content
ClearValue 1; // up(1)
207569-F
}
AssociatedTraps
{
TrapName "rcCardDown"
{
Severity 5;
Status "SET";
}
A fault name for this fault is generated and displayed in the Fault Names list.
You can select the fault name for this device when creating a script.
Adding a fault script
To add a new fault script:
1 Verify that you are logged in to your management station with administrative
(Windows) or root (UNIX) access privileges.
2 Verify that the Optivity NMS services or daemons are running properly.
For more information, see “Verifying that services or daemons run” on
page 685.
• From the Fault Summary menu bar, choose Options > Fault Scripts.
• On the toolbar, click Fault Scripts.
The Configure Fault Scripts dialog box opens (Figure 261).
Figure 261 Configure Fault Scripts dialog box
For detailed information about the Fault Scripts dialog box, click Help on the
Fault Script dialog box.

4 Click New.
The Edit Fault Script dialog box opens (Figure 262).
Figure 262 Edit Fault Script dialog box
Refer to “Fault name definitions” on page 674 for information about how fault
names are generated.
5 Choose the device type and subtype from the lists of available selections.
6 Choose a fault from the list of available faults in the Fault Name box.
7 In the IP Address box, type the IP address of the trap sender. You can use one
or more asterisks (*) as wild cards to indicate a range of IP addresses.
207569-F
Table 152 shows several examples of valid IP addresses.
Table 152 Fault script IP address examples
Address Description
10.127.2.1 Executes the script on receipt of specified fault from 10.127.2.1

10.127.2.* Executes the script on receipt of specified fault from any device in the
range 10.127.2.1 through 10.127.2.255.
10.127.*.2 Executes the script on receipt of specified fault from any device in the
range 10.127.1.2 through 10.127.255.2.
*.*.*.* Executes the script on receipt of specified fault from any device.
8 In the Executable Name box, enter a valid script, such as:

• Any script or program you can launch from a command line. For instance,
enter a script to access a third-party email or pager forwarding
application. Follow the script guidelines in “Script parameter guidelines”
on page 673.
• The name of an Optivity NMS 10.3 application, such as OmniView
• Enter one, or several, fault parameters from the list in Table 151 after the
script. The default is zero parameters. If you do not add any parameters
you will not receive any fault data.
Note: The default execute mode (Exec Mode) option is Always. Your
script always executes when the fault you select occurs, given the
parameters you have set.
9 Click > to move the selected script parameter(s) to the Selected Parameters
box.
10 Click OK.
The Edit Fault Script dialog box closes.
11 Click OK.
The Configure Fault Scripts dialog box closes.

Deleting a fault script
To delete an existing fault script:

• From the Fault Summary menu bar, choose View > Fault Scripts.
• Click Fault Scripts.
The Configure Fault Scripts dialog box (Figure 261 on page 675) opens.
2 In the Fault Script Configuration table, select a script to delete.

3 Click Delete.
Fault Summary deletes the selected script.
4 Click OK.
The Configure Fault Scripts dialog box closes.
Configuring trap forwarding
You can configure a trap forwarding table that automatically forwards fault
information in the form of traps to other management stations. In Optivity NMS
10.3, faults are forwarded only in SNMPv1 format.
To configure Fault Summary to forward faults to a specific management station:

• From the Fault Summary menu bar, choose Options > Trap Forwarding.
• Click Trap Forward.
The Configure Trap Forwarding dialog box opens (Figure 263).
207569-F
Figure 263 Configure Trap Forwarding dialog box
For detailed information about the Configure Trap Forwarding dialog box,
2 Click Add.
A new row appears in the Trap Forward Configuration table.
3 In the new row, click in the IP address column.

4 Enter the IP address of the management station to which you want the faults
forwarded. Use only one IP address. You cannot add multiple IP addresses or
IP address ranges.
5 In the new row, click in the Community Name column.
6 Change the default community name (public) to the read/write community
string name of the management station.
7 Click OK.
Troubleshooting Fault Summary

The following sections describe how to investigate and resolve Fault Summary
problems:

• “Fault management services or daemons” on page 683
• “Stopping and starting services or daemons” on page 687

• “Viewing debug information” on page 691

• “Managing the trap database” on page 692
Resolving problems
The following sections describe Fault Summary problems and their resolutions.
• “Fault Summary does not start‚” next

• “Fault Summary does not display faults” on page 681
• “Fault states are not updated” on page 682
• “Connection to the server is lost” on page 682
Fault Summary does not start
You cannot start the Fault Summary application and the message shown in
Figure 264 opens on the client system.
Figure 264 Fault Summary initialization message
To resolve this problem try the following on the server system:
• Check that the weboptsrvr service or daemon is running.

Refer to “Verifying that services or daemons run” on page 685 for more
information.
• Check that the Fault Summary webfsserver.reg registration file is in the
$LNMSHOME\weboptsrvr\registration directory.
207569-F
• Check that the Fault Summary server starts.
Fault Summary does not display faults
Faults are not displayed in the Fault Summary application, even when a device
sends a trap. The Fault Summary window does not display any faults.
To resolve this problem try the following:
• Check that you can see the devices sending traps. If faults are displayed, the
devices that are sending traps are not in your view.
• Check that the trap server and Fault Correlator service or daemon are running.
See “Verifying that services or daemons run” on page 685 for more
information.
Fault Summary does not display traps
Traps are not displayed in the Fault Summary application, even when a device
sends a trap.
• Check that the trap server service is running
Fault Scripts are not getting executed
• Check that the script server service is running.

• Check that the scripts are in the PATH (follow the script path guidelines
specified in “Script path guidelines” on page 671).
• In case of windows make sure that the extension .bat or .exe is specified in the
script name.

Fault states are not updated
Fault Summary does not update the state of a fault or the state of a fault does not
change. For example, the fault severity level does not change from Warning to
Critical.
To resolve this problem, try the following:
• Check that the fault correlator service is running.
Connection to the server is lost
Fault Summary is disconnected from the server and one or both of the following
occurred:
• A fault indicator error icon displays in the status bar.

• A message displays.
Figure 265 show the fault indicator error icon and the message box.
Figure 265 Fault Summary User Preferences message
• Exit the Fault Summary client application and restart the Fault Summary
application.
207569-F
Fault management services or daemons
Fault management processes running in the Windows environment are referred to

as “services.” Fault Summary processes running in the UNIX environment are
referred to as “daemons.” Fault management lets you start and stop services or
daemons. The services or daemons start automatically, and must be running for
the fault management system to operate.
In the Windows environment, the services are referenced by two names. In the
UNIX environment, the daemons are referenced by one name.
Table 153 describes the Fault Management services and daemons.
Table 153 Fault management services and daemons
Windows
Windows service UNIX daemon
command line file Description
name file name
name
OptTrapSrv trapsrv.exe trap_server_restart* Trap Server

trapsrv_NV.exe
trapsrv_OV.exe
trapsrv_Platformless
OptTrapReg trapreg.exe trap_registration_daemo Trap Registration
n_restart*
OptSyslogReg syslogreg.exe syslog_reg_restart* Syslog
Registration
OptSuperPing superping.exe superp_restart* Super Ping
OptStateRecorder state_recdr.exe sr_restart* State Recorder
OptFaultCorr fc_daemon.exe fc_restart* Fault Correlator
OptWeboptsrvr weboptsrvr.exe weboptsrvr_restart* Web Opt Server
OptScriptSrv scriptsrv.exe scriptsrv_restart* Scripting Server
OptSyslogProc syslogproc.exe syslogproc_restart* Syslog Processor
OptFaultSummary ebd.exe eb_restart* Fault Summary
server
See the following sections for more information about Fault Summary daemons
and services:
• “Names of trap server services‚” next

• “Fault management services in the Windows environment” on page 684

• “Fault management services in the UNIX environment” on page 685
• “Verifying that services or daemons run” on page 685
Names of trap server services
The trap server provides services that run on different platforms as follows:
• trapsrv_NV.exe—NetView
• trapsrv_OV.exe—Network Node Manager
• trapsrv_Platformless—No platform manager installed
Fault management services in the Windows environment
In the Windows environment, you use the Control Panel Services to stop the fault
management services.
You must stop the fault management services in the following sequence:
• OptTrapSrv, which also stops:

— OptFaultCorr
— OptStateRecorder
— OptSuperPing
• OptTrapReg
• OptWeboptsrvr
• OptSyslogProc
• OptFaultSummary
You cannot stop Fault Management services from the Windows command line.
See “Stopping services in the Windows NT or Windows 2000 environment” on
207569-F
Fault management services in the UNIX environment
In the UNIX environment, you use scripts to stop the fault management services.
You must stop the fault management services in the following sequence:
1 weboptsrvr_restart*
2 fc_restart*
3 scriptsrv_restart*
4 superp_restart*
5 sr_restart*
6 trap_registration_daemon_restart*
7 trap_server_restart*
8 syslogproc_restart
9 eb_restart
Verifying that services or daemons run
You can verify that Optivity NMS services and daemons are running in several
ways. You can access your Windows NT or Windows 2000 Control Panel, open a
Windows NT or Windows 2000 command line, or open a UNIX command line.
To verify if the Optivity NMS services are running in the Windows NT or

Windows 2000 environment from the Control panel:
1 On the Windows task bar, click Start.

The Windows Start menu opens.
2 Choose Settings.
The Settings shortcut menu opens.
3 Choose Control Panel.

The Control Panel window opens.
4 Click Services.

The Services dialog box opens.
5 Scroll to the section where the services begin with “Opt” and verify that the
status for the fault management services is “Started.”
To verify if the Optivity NMS services are running in the Windows NT or

Windows 2000 environment from the command line:
1 Open a Command Prompt window.

• Enter:
optstatus -f
The optstatus -f command displays the status of all Optivity NMS
services.
• Enter:
optstatus -fe
The optstatus -fe command displays the services that are not running.
To verify if the Optivity NMS daemons are running in the UNIX environment
from the command line:
1 Open a Terminal window.

• Enter:
optstatus -f
The optstatus -f command displays the status of all Optivity NMS
services.
• Enter:
optstatus -fe
The optstatus -fe command displays the services that are not running.
207569-F
Stopping and starting services or daemons
You may need to stop and then restart the Optivity NMS services or daemons on
your Windows NT, Windows 2000, or UNIX management station. See the
following sections for more information about managing the Fault Summary
daemons and services:
• “Stopping services in the Windows NT or Windows 2000 environment‚” next

• “Stopping daemons in the UNIX environment” on page 688
• “Starting services in the Windows NT or Windows 2000 environment” on
page 689
• “Starting daemons in the UNIX environment” on page 690
Stopping services in the Windows NT or Windows 2000

environment
You must stop the fault management services in a specific order. See “Fault
management services or daemons” on page 683 for more information.
To stop Fault Management services in the Windows NT or Windows 2000

environment:

2 Choose Settings.

4 Click Services.
5 Do the following:
a Select OptTrapSrv.
b Click Stop.

The Stopping dialog box opens.

c Click OK.
The Service Control message box opens. The OptTrapSrv, OptFaultCorr,
OptStateRecorder, and OptSuperPing services stop.
d Repeat step a, b, and c for the OptTrapReg, OptWeboptsrvr, OptScriptSrv,
and OptSyslogProc services.
e OptFaultSummary
f service.
Stopping daemons in the UNIX environment
You must stop the fault management daemons in a specific order. See “Fault
To stop Fault Management daemons at the UNIX command line:
1 Start a root session.

2 At the command line, enter the following commands in the sequence shown:
weboptsrvr_restart stop
fc_restart stop
superp_restart stop
sr_restart stop
trap_registration_daemon_restart stop
trap_server_restart stop
scriptsrv_restart stop
trap_server_restart stop
syslogproc_restart stop
eb_restart stop
3 At the command line, enter the following command:
optstatus -f
The status of the Optivity NMS daemons is displayed.
207569-F
Starting services in the Windows NT or Windows 2000

environment
You start Fault Management services in a specific order. See “Fault management
services or daemons” on page 683 for more information.
To start fault management services from the Windows NT or Windows 2000

control panel:

2 Choose Settings.

4 Click Services.
5 Select the following in the sequence shown:

• OptTrapReg, and click Start.
• OptTrapSrv, and click Start.
• OptStateRecorder, and click Start. Check that OptFaultCorr also starts.
• OptSuperPing, and click Start.
• OptFaultCorr, and click Start.
• OptScriptSrv, and click Start.
• OptWeboptsrvr, and click Start.
• OptScriptSrv, and click Start.
• OptSyslogProc, and click Start.

To start fault management services from the Windows NT command line:
1 Open nine Command Prompt windows.

2 In each Command Prompt window, enter:
cd <path>\Optivity\NMS\bin
Where path is the drive and install path to the Optivity directory.
3 At the bin directory prompt, in the following sequence, do the following:

• In window one, enter trapreg.exe.
• In window two, enter trapsrv.exe.
• In window three, enter state_recdr.exe.
• In window four, enter superping.exe.
• In window five, enter fc_daemon.exe.
• In window six, enter scriptsrv.exe
• In window seven, enter weboptsrvr.exe
• In window seven, enter syslogproc.exe
• In window seven, enter ebd.exe
4 Enter:
optstatus -f
The status of the Optivity NMS services is displayed.
Starting daemons in the UNIX environment
You must start fault management daemons in a specific order. See “Fault
1 Start a root session.

2 Open a Terminal window.
3 At the command line, enter:
cd $LNMSHOME/bin
4 At the bin directory prompt, in the following sequence, enter the following
and press Enter after each entry:
trap_registration_daemon_restart* start
207569-F
trap_server_restart* start
sr_restart* start
superp_restart* start
fc_restart* start
scriptsrv_restart* start
weboptsrvr_restart* start
syslogproc_restart* start
eb_restart* start
5 Enter:
optstatus -f
The status of Optivity NMS daemons is displayed.
Viewing debug information
The Fault Summary application lets you view debug information to resolve
problems. To view debug information, you must start the fault management
services from the command line.
Debug information is displayed in the Command Prompt window. Table 154

describes the services that provide debug information.
Table 154 Fault management services with debug output
File name Service Purpose
trapsrv.exe Trap Server Shows if traps are being received by the

management station.
superping.exe SuperPing Shows if the station is communicating with the
device, to get the state of the device.
fc_daemon.exe Fault Correlator Shows whether or not faults are getting
correlated and written to the database.
weboptsrvr.exe Web opt server Shows if faults are being received by Fault
Summary.
trapreg.exe Trap registration
state_recorder.exe State recorder
scriptsrv.exe Script server

Table 154 Fault management services with debug output (continued)
File name Service Purpose
syslogproc.exe Syslog processor

ebd.exe Fault Summary
app
To start any Fault Summary service in debug mode:
1 Open a Command Prompt window.

<file name> -d 3 -l 3?
Where <file name> is one of the file names shown in Table 154.
Managing the trap database
Starting with Optivity NMS version 10.3, traps are stored exclusively in a new
trap database that is separate from the fault database. The following sections
describe three new command-line utilities you can use to manage the trap
database:
• “Purging traps‚” next

• “Backing up the trap database” on page 694
• “Restoring the trap database” on page 694
Note: The input_db_contents and output_db_contents scripts do not

work for the trap database.
207569-F
Purging traps
You use the purgeTrap application to purge the trap database of some or all traps.
This application is periodically launched by the trapsrv service or daemon based
on the trap purge cycle set in Fault Summary.
The purgeTrap application is located in one of the following directories:
• Windows - %lnmshome%\bin
• UNIX - $LNMSHOME\bin
The purgeTrap syntax is as follows:
purgeTrap <interval>
Where <interval> is either:
• A non-zero integer specifying the age in hours of the traps to delete.

• 0 to delete all traps. The 0 option performs an SQL truncate operation that is
faster than integer values. You can only use the purgeTrap 0 option when the
trapsrv service or daemon is stopped.
For example:
purgeTrap 6
Deletes all traps older than six hours.
purgeTrap 0
Deletes all of the traps in the database.

Backing up the trap database
You use the script backup_trapdb to backup the trap database. This script creates
an Oracle dump file named trapdb.dmp in the specified directory.
The backup_trapdb script is located in one of the following directories:
The backup_trapdb syntax is as follows:
backup_trapdb <output_path>
Where <output_path> is the directory in which to create the trapdb.dmp file.
Restoring the trap database
You use the script restore_trapdb to restore the trap database. This script restores
the database from the trapdb.dmp Oracle dump file located in the specified
directory.
The restore_trapdb script is located in one of the following directories:
The restore_trapdb syntax is as follows:
restore_trapdb <input_path>
Where <input_path> is the directory containing the trapdb.dmp file from which
to restore the database.
207569-F
695
Chapter 19
Managing Network Assets with Device Inventory
Viewer
• “Device Inventory Viewer overview‚” next

• “Getting started with the Device Inventory Viewer” on page 695
• “Working with Device Inventory Viewer” on page 702
• “Troubleshooting the Device Inventory Viewer” on page 728
Device Inventory Viewer overview

The Device Inventory Viewer lets you view and manage information about your
network assets including information about modules installed inside hubs,
switches, and chassis. It also lets you view and edit information about the versions
of agent software running on devices in the inventory.
Getting started with the Device Inventory Viewer

See the following sections for information about getting started with Device
Inventory Viewer:
• “Starting Device Inventory Viewer‚” next

• “Device Inventory Viewer window” on page 697
• “Access Control for Device Inventory Viewer” on page 701

696 Chapter 19 Managing Network Assets with Device Inventory Viewer
Starting Device Inventory Viewer
To start Device Inventory Viewer:
Table 155 Starting Device Inventory Viewer
To start Device
Inventory Viewer
from: Do this:
InfoCenter Choose Admin > Device Inventory Viewer
Note: If the Device Inventory Viewer menu command is disabled, it

Device Inventory Viewer.
Windows Start Choose Start > Programs > Optivity > DeviceInventory
menu
command prompt
div
prompt
div
Click the Device Inventory Viewer icon on the Optivity Web page.

feature to bookmark the Device Inventory Viewer application. Doing
so saves the URL for Device Inventory Viewer.
If you are not starting Device Inventory Viewer from InfoCenter, the Connect
207569-F
Chapter 19 Managing Network Assets with Device Inventory Viewer 697
The Device Inventory Viewer window opens.
Note: The first time you start Device Inventory Viewer, the Seed
Synchronization dialog box opens to let you synchronize the Device
Inventory Viewer database. See “Synchronizing the asset database” on
Device Inventory Viewer window
The Device Inventory Viewer window lets you navigate and view network asset
information.
The Device Inventory Viewer window is shown in Figure 266.
Figure 266 Device Inventory Viewer window
Menu bar
Toolbar
Asset
tree
Contents
pane
View
window
Status bar

Table 156 describes the parts of the Device Inventory Viewer window.
Table 156 Parts of the Device Inventory Viewer window
Part Description
Menu bar Provides access to all available commands. See “Menu bar and
toolbar” on page 698 for more information.
Toolbar Provides quick access to commonly used Device Inventory Viewer
functions. See “Menu bar and toolbar” on page 698 for more
information.
Asset tree Shows you a hierarchical view of the network asset types and
subtypes.
Contents pane Displays windows that show lists of assets, modules, and pr.
Status bar Displays information about the current status of the Device Inventory
Viewer:
• The name of the Optivity server that the client software is
connected to.
• Progress information for the current operation:
— A green bullet indicates no current activity
— A red bullet indicates that database synchronization is in
progress
• A description of the toolbar button over which the pointer is
currently positioned.
The Device Inventory Viewer menu bar commands and toolbar buttons provide
quick access to all Device Inventory Viewer commands.
If you open Device Inventory Viewer in a Web browser, the menu bar does not
display. Instead, click the Menu tool on the toolbar to open a shortcut menu of
Device Inventory Viewer menus.
207569-F
Table 157 describes the Device Inventory Viewer menu bar commands and toolbar
buttons.
Toolbar
button
Menu Opens the Device Inventory Viewer menu in a Web browser.
Lets you drag the toolbar.

Toolbar
button
File New > Type Opens the New Type dialog box to let you create a new asset
type. See “Adding asset types and sub types” on page 721
New > Sub Type Opens the New Sub Type dialog box to let you create a new
asset sub type. See “Adding asset types and sub types” on
New > Device Opens the New Device dialog box to let you manually add a
new device to the asset database. See “Manually adding
assets” on page 712 for more information.
Open Opens a Type window for the selected type. See “Listing
members of an asset type or subtype” on page 703 for more
information.
Close Closes the selected window in the contents pane.
Delete Deletes the selected element. See “Manually removing

assets” on page 714 for more information.
Properties Opens the Asset Information window to let you view

information about the selected asset. See “Viewing
properties for an asset” on page 704 for more information.
Import Devices Opens the Import dialog box, which lets you import devices
into the asset database from a comma-separated text file.
See “Importing asset information” on page 715 for more
information.
Export Devices Opens the Export dialog box, which lets you export devices
from the asset database into a comma-separated text file.
See “Exporting asset information” on page 714 for more
information.
Print Prints the contents of the selected Type window. See
“Printing asset tables” on page 709 for more information.
Page Setup Opens the Page Setup dialog box, where you set printing
parameters.
Exit Closes the Device Inventory Viewer application.
View Refresh Refreshes the selected Type window with the latest
information from the device. See “Refreshing Device
Inventory Viewer displays” on page 708 for more information.
207569-F
Toolbar
button
Admin Check Agent Checks the agent software on devices in the inventory to see
Version if they have the latest versions. Notifies you If updated agents
are available. See “Checking for updated agent versions” on
Synchronize Opens the Seed Synchronization dialog box, where you
select topology seeds with which to synchronize the asset
database. See “Synchronizing the asset database” on
Window Tile Tiles the view windows in the contents pane.
Cascade Cascades the windows in the contents pane.
Restore Restores the windows in the contents pane.
Close All Closes all of the windows in the contents pane.
Help Device Inventory Opens online Help for Device Inventory Viewer.
Viewer Help
About Device Displays version and copyright information for the Device
Inventory Viewer Inventory Viewer application.
Navigation pane and asset tree
The navigation pane of the Device Inventory Viewer window lets you organize
inventory information into a hierarchy using folders and subfolders. These folders
and subfolders are displayed on the asset tree.
Access Control for Device Inventory Viewer
To use Device Inventory Viewer, your Optivity user name must have the DIV
With read/write access permission, you have full access to all Device Inventory
Viewer functions.

With read-only access permission, you can only:
• Open Device Inventory Viewer

• View asset details
• Export inventory tables
• Check agent versions
• Print asset information
An Optivity NMS administrator sets user access to the Device Inventory Viewer
window by configuring access to the DIV token in the Access Control
Administration window. For more information about using Access Control
Administration, see Chapter 2, “Specifying access to Optivity NMS applications
with Access Control Administration,” on page 75.
Working with Device Inventory Viewer

The following sections describe how to use Device Inventory Viewer:
• “Viewing asset lists and asset properties‚” next

• “Adding and removing assets” on page 710
• “Working with asset types and properties” on page 721
• “Managing the Device Inventory Viewer database” on page 726
207569-F
Viewing asset lists and asset properties
The following sections describe how to use Device Inventory Viewer to list and
view assets and asset properties:
• “Listing members of an asset type or subtype‚” next

• “Viewing properties for an asset” on page 704
• “Editing device properties for an asset” on page 706
• “Adding and removing properties for a type” on page 722
• “Viewing information for a module or port” on page 707
• “Refreshing Device Inventory Viewer displays” on page 708
• “Checking for updated agent versions” on page 709
• “Printing asset tables” on page 709
Listing members of an asset type or subtype
To view a list of assets that belong to a type or subtype:
1 On the asset tree, select the type and (if applicable) the subtype in which the
device is listed.
• Right-click the type or subtype and choose Open.
• Double-click the type or subtype.
• On the toolbar, click Open.
• From the menu bar, choose File > Open.
Device Inventory Viewer opens a Type window in the contents pane
(Figure 267). The Type window shows you a list of devices that belong to the
type and subtype.

Figure 267 Typical Type window
Viewing properties for an asset
Assets are physical devices discovered on the network. To view the properties of a
device in the inventory:
1 If you haven’t already done so, open a Type window for the asset type in the
contents pane. See “Listing members of an asset type or subtype” on page 703
2 In the Type window in the Device Inventory Viewer contents pane, select the
device.
• From the menu bar, choose File > Properties
• On the toolbar, click Properties
• Right-click the device and choose Properties
Device Inventory Viewer opens an Asset Information window to show you the
device properties (Figure 268).
207569-F
Figure 268 Typical asset information window
Table 158 describes the properties of a typical asset. In addition to these

properties, there may be additional custom properties that are not listed.
Table 158 Typical asset properties, shown in alphabetic order
Part Description
Agent Ver The version number of the agent software on the asset
DNS Name The asset DNS Name
HW Rev The hardware revision level of the asset
IP The asset IP address
Last Checked The date and time at which the asset was last checked
Last SNMP OK The date and time at which the asset was last responded to an
SNMP query
Last Sync OK The date and time at which the asset was synchronized into the
asset database.
Max Slots The number of slots in the chassis.
Name The asset name (Read-only)
Notes Notes about the asset
Serial No The asset serial number

Table 158 Typical asset properties, shown in alphabetic order (continued)
Part Description
SNMP Ver The SNMP version used by the asset

Status The current status of the asset
SubType The asset subtype (Read-only)
SysContact The asset system contact
SysDescr The system description
SysLocation The asset system location
SysName The asset system name
SysOid The asset system OID
Times Checked The number of times the asset has been checked
Type The asset type (Read-only)
Uptime The elapsed time since the asset was last reset.
Editing device properties for an asset
To set the device properties for an asset:
1 Open the Asset Information window as described in the procedure “Viewing

properties for an asset” on page 704.
2 Edit the device properties that you want to change.
Note: You cannot edit the Name, Type, or Subtype properties.
3 Do one of the following

• Click OK to apply your changes and close the window.
• Click Apply to apply your changes and leave the window open.
4 Device Inventory Viewer opens an alert box to tell you that the device
properties were changed (Figure 269).
207569-F
Figure 269 Update Successful alert box
Viewing information for a module or port
To view information for modules installed inside a device or chassis:
1 If you haven’t already done so, open a Type window for the asset type in the
contents pane. See “Listing members of an asset type or subtype” on page 703
2 In the Type window, select a device.
3 Do one of the following to open a Module Information window for the device:
• Double-click on the device
• From the menu bar, choose File > Open
• On the tool bar, click Open
Device Inventory Viewer opens a Module Information window for the
selected device (Figure 270).
Figure 270 Module Information window
4 On the module tree in the left pane of the window, click the element for which
you want to view information:

• Click the device at the top of the tree to view a table of information about
the modules installed in the device.
• Click a slot on the tree to view a table of information about the ports on
the module in that slot (Figure 271).
Figure 271 Module Information window showing slot information
The right pane of the window shows a table information for the selected
element.
Refreshing Device Inventory Viewer displays
While you are using Device Inventory Viewer, you can use the refresh feature to
make sure that you are viewing the latest information from the asset database. The
refresh feature refreshes the information displayed in the selected Device
Inventory Viewer type window. This feature shows you any changes that might
have been made to the database since you opened the view in Device Inventory
Viewer.
To refresh a Device Inventory Viewer type window:
1 Select the type window

• From the menu bar, choose View > Refresh
• On the tool bar, click Refresh
• In the asset tree, right-click the icon for an open display and choose
Refresh from the shortcut menu.
207569-F
Checking for updated agent versions
You can use Device Inventory Viewer to check whether updated agent software
versions are available for the devices in your network inventory. This feature
checks a listing of available agent software (OIT files) on the Nortel Networks
Web site. If updated agent software is available for any of the inventory devices,
Device Inventory Viewer lists the devices and agents.
To check for updated agent versions:
From the menu bar, choose Check Agent Versions.
The Agent Version Upgrades window opens (Figure 272). Use this window to
view a listing of assets and their current agents.
Figure 272 Agent Version Upgrades window
Printing asset tables
To print the contents of a Type window:
1 If you haven’t already done so, open the Type window for which you want to
print the contents.
• On the tool bar, click Print.

• From the menu bar, choose File > Print

3 Set printing parameters and click OK.
Adding and removing assets

Normally, new devices are added to the asset database when you synchronize the
asset database as described in “Synchronizing the asset database” on page 710. In
addition to this process, you can also manually add and delete devices. See the
following sections for information on manually adding and deleting devices:
• “Synchronizing the asset database‚” next

• “Manually adding assets” on page 712
• “Manually removing assets” on page 714
• “Importing asset information” on page 715
• “Exporting asset information” on page 714
Synchronizing the asset database
When you synchronize the asset database, Optivity NMS collects information
about physical devices from the Optivity topology database and adds it to the asset
database. Because Optivity uses the topology database as the starting point,
synchronize the asset database only after running Autotopology discovery at least
once.
Note: The synchronization process does not remove devices from the
asset database when they no longer appear in the topology database. See
“Manually removing assets” on page 714 for more information about
manually removing devices from the asset database.
To synchronize the asset database:

• On the tool bar, click Synchronize DIV Database
• From the menu bar, choose Admin > Synchronize
207569-F
2 Device Inventory Viewer opens the Seed Synchronization dialog box

(Figure 273).
Figure 273 Seed Synchronization dialog box
3 Select seeds from the NMS Seeds list, and click >> to move them to the
Repository Seeds list.
The NMS Seeds list shows all of the discovery seeds used by the
Autotopology applications to discover network devices. The Repository Seeds
list shows the subset of discovery seeds used to build the asset database. For
more information about Autotopology and discovery seeds, see Chapter 4,
4 (Optional) Use the Add all NMS seeds and Remove all repository seeds check
boxes to move all seeds from one list to the other. This feature is useful if you
use a great number of discovery seeds.
5 Click Start Sync.
Device Inventory Viewer synchronizes the asset database with the topology
database. During the synchronization process, and alert box shows the status
of the process (Figure 274).

Figure 274 Database synchronization alert box
Manually adding assets
In addition to having devices discovered by the Device Inventory Viewer

application, you can also manually add devices to the asset tree.
To manually add a device to the asset tree:
1 On the toolbar, click New device.

The New Device dialog box opens.
Figure 275 New Device dialog box
2 In the Device box, enter an IP address or hostname for the device.

3 From the Type menu, choose the asset type that matches the device.
207569-F
4 From the Sub Type menu, choose the sub type that matches the device. The
entries available from the Sub Type menu depend on what is selected in the
Type menu.
5 Click OK.
Device Inventory Viewer opens an Asset Information window (Figure 276) to
let you make any desired changes to the device entry in the asset database.
Figure 276 Asset Information window (adding a new device)
6 After making changes, click OK.

Device Inventory Viewer adds the new device to the selected type and sub
type.

Manually removing assets
Device Inventory Viewer lets you manually delete devices from the asset tree
when they are no longer part of your network inventory.
To manually delete a device from the asset tree:
1 If you haven’t already done so, open a Type window for the type of device you
want to delete.
2 For more information, see “Listing members of an asset type or subtype” on
page 703.
3 Select the device that you want to delete.
• From the menu bar, choose File > Delete
• On the toolbar, click Delete
Device Inventory Viewer removes the device from the Type window and from
the asset database.
Exporting asset information
Device Inventory Viewer lets you export asset information from type windows to
comma-separated value (.csv) text files. You can use this feature to save inventory
information to files.
You can also use this feature to move inventory information into spreadsheet
applications such as Microsoft Excel, where you can view, sort, and edit it. After
editing inventory information in the .csv file, you can also import it back into the
asset database with the Device Inventory Viewer import feature. See “Importing
asset information‚” next for more information.
To export the contents of a type window to a comma-separated value text file:
1 If you haven’t already done so, open a type window for the assets that you
want to export.
If you want to export all of the assets in the inventory, open the All assets type
at the top of the asset tree.
207569-F
• On the toolbar, click Export devices

• From the menu bar, choose File > Export devices.
The Export Assets dialog box opens (Figure 277).
Figure 277 Export Assets dialog box
3 Navigate to the directory where you want to save the inventory

4 In the File name box, enter a name for the file.
5 Click OK.
Device Inventory Viewer saves the asset information in the selected type to
the file.
Importing asset information
Device Inventory Viewer lets you export asset information from type windows to
comma-separated value (.csv) text files. You can use this feature to save inventory
information to files.

You can also use this feature to move inventory information into spreadsheet
applications such as Microsoft Excel, where you can view, sort, and edit it. After
editing inventory information in the .csv file, you can also import it back into the
asset database with the Device Inventory Viewer import feature. See “Importing
asset information‚” next for more information.
To import the contents of a comma-separated value text file into the asset
database:

• On the toolbar, click Import Devices
• From the menu bar, choose File > Import Devices
The Import Assets find file dialog box opens (Figure 278).
Figure 278 Import Assets find file dialog box (Windows shown, UNIX similar)
2 Navigate to the file containing the devices you want to import and click OK.
The Import Assets wizard window opens (Figure 279). The first wizard
prompt asks you to identify the Device Type column in the file.
207569-F
Figure 279 Import Assets wizard - selecting Device Type column
3 From the list of columns found in the selected file, choose the column that
represents the device type.
The import feature uses this information to determine which type each entry
in the file belongs to.
4 Click Next.
The wizard prompts you to identify the device sub-type.
represents the device sub-type.
6 Click Next.
The wizard prompts you to identify the device name.
represents the device name.
8 Click Next.
The wizard prompts you to map the device types found in the file to the types
in the asset database (Figure 280).

Figure 280 Import Assets wizard - mapping types
9 For each type in the file you want to import, click the Type in NMS cell and
choose a device type (Figure 281).
Figure 281 Import Assets wizard - selecting a device type
207569-F
10 For each type, use the Done and Skip check boxes to set whether or not
Device Inventory Viewer imports devices of that type from the file:
• For type you do want to import, click the Done check box.
• For type that you do not want to import from the file, click the Skip check
box.
11 Click Next.
The wizard prompts you to map the device properties found in the file to the
properties in the asset database (Figure 282).
Figure 282 Import Assets wizard - mapping properties
12 For each entry in the Types selected table, map all of the properties in the file
to the corresponding properties in the asset database.

To map a file property to a different property in the asset database, click the
Property in NMS entry and either select a different property or enter a new
property name.
13 For each property, use the Done and Skip check boxes to set whether or not
Device Inventory Viewer imports devices of that type from the file:
• For properties you do want to import, click the Done check box.
• For properties that you do not want to import from the file, click the Skip
check box.
14 Click Next.
The wizard shows you the type and property mappings you selected, and
prompts you to confirm the mappings (Figure 283).
Figure 283 Import Assets wizard - confirm mappings
207569-F
15 Click Next to import the contents of the file into the asset database.
Working with asset types and properties
See the following sections for information on working with asset types and
properties:
• “Adding asset types and sub types‚” next

• “Adding new properties to an asset” on page 723
• “Deleting properties from an asset type” on page 725
Adding asset types and sub types
You can customize the asset tree by adding new types, and by adding new sub
types within types.
To add a new asset type to the asset tree:
1 On the toolbar, click New type.

The New Type dialog box opens (Figure 284).
Figure 284 New Type dialog box
2 Enter a name for the new type and click OK.

Device Inventory Viewer creates the new type at the bottom of the asset tree,
and opens a Type properties window to let you edit, add, or remove properties.
See “Adding and removing properties for a type” on page 722 for more
information about editing type properties.
3 When you are done editing the properties, click OK.

To add a new subtype to an existing type:
1 Right-click the type in which you want to create a subtype, and choose Create
Sub Type from the shortcut menu.
The New Sub Type dialog box opens (Figure 285).
Figure 285 New Sub Type dialog box
2 Enter a name for the new sub type and click OK.
Device Inventory Viewer creates the new sub type within the selected type.
Adding and removing properties for a type
To view or edit the properties that are displayed for all devices of a type and its
subtypes:
1 In the Asset tree, select the type for which you want to edit the displayed
properties.
• From the menu bar, choose File > Properties
• On the toolbar, click Properties
• Right-click the device and choose Properties
Device Inventory Viewer opens a Type properties window to show you the
device properties (Figure 268).
207569-F
Figure 286 Typical type properties window
3 To remove a property, click the Remove check box for the property.
Note: You can only remove properties that have been added by Optivity
NMS users. You cannot remove the pre-defined properties that are
supplied with Optivity NMS.
4 To add a new property, click Add Property and enter the name of the new
property in the New Property dialog box.
5 When you are done making changes, click OK.
Adding new properties to an asset
Device Inventory Viewer lets you add new properties to an asset. This feature lets
you customize device properties so that you can track assets according to
additional properties. The new property applies to all assets of the selected type.

To add a new property to an asset type:
1 Open an Asset Information window for any device of the type. See “Viewing
2 On the Asset Information window, click Add.
An alert box prompts you to confirm that you want to add a new property
(Figure 287).
Figure 287 Add Property alert box
3 Click Yes.
The New Property dialog box opens (Figure 288).
Figure 288 New Property dialog box
4 In the Property box, type the name of the new property that you want to add.
5 (Optional) In the Value box, type the value for the property that you want to
apply to the selected asset.
Unlike the property, which applies to all assets of the selected type, the value
that you type applies only to the selected asset.
207569-F
6 Click OK.
7 Device Inventory Viewer adds the new property to all assets of the selected
type, and applies the property value to the selected asset.
Deleting properties from an asset type
Device Inventory Viewer lets you delete properties from the list of properties for
each device type. This feature lets you remove device properties so that you do not
want to use. The deleted property is removed from all assets of the same type as
the selected one.
To delete an property from an asset type:
1 Open an Asset Information window for any device of the type. See “Viewing
2 On the Asset Information window, select the property that you want to delete.
3 On the Asset Information window, click Delete.
Note: You can only remove properties that have been added by Optivity
NMS users. You cannot remove the pre-defined properties that are
supplied with Optivity NMS.
An alert box prompts you to confirm that you want to delete the selected
property (Figure 289).
Figure 289 Delete Property alert box
4 Click Yes.
5 Device Inventory Viewer deletes the property from all assets of the selected
type.

Managing the Device Inventory Viewer database
The Database Admin Tool does not backup or restore the inventory database used
by Device Inventory Viewer. The following sections describe how you backup,
restore, and remove the Device Inventory Viewer database:
• “Backing up the Device Inventory Viewer database‚” next

• “Restoring the Device Inventory Viewer database” on page 726
• “Removing the Device Inventory Viewer database” on page 727
Backing up the Device Inventory Viewer database
Use the following commands to backup the Device Inventory Viewer database:
• On UNIX:
$LNMSHOME/sbin/backup_divdb <path name>
• On Windows:
%lnmshome%\perl\bin\perl %lnmshome%\sbin\backup_divdb <path name>
Both commands backup the Device Inventory Viewer database to the file
divdb.dmp at the specified path.
Restoring the Device Inventory Viewer database
Use the following commands to restore the Device Inventory Viewer database:
• On UNIX:
$LNMSHOME/sbin/restore_divdb <path name>
• On Windows:
%lnmshome%\perl\bin\perl %lnmshome%\sbin\restore_divdb <path name>
Where <path name> is the path where the divdb.dmp file is located.
207569-F
Removing the Device Inventory Viewer database
To remove the Device Inventory Viewer database:
• On UNIX:
1 Use the following command to stop the DIV daemon:
$LNMSHOME/opt_install/div_restart stop
2 Execute these commands:
su - onmsorcl -c "/usr/lnms/bin/cr_divdb"
cd /usr/lnms/classes/com/baynetworks/div/dbi
/usr/lnms/bin/runimp Category.txt
/usr/lnms/bin/runimp Category_Attribute.txt
3 Use the following command to start the DIV daemon:
$LNMSHOME/opt_install/div_restart start
• On Windows:
1 Stop the DIV service with the command:
divs -stop
2 Execute these commands:
%lnmshome%\perl\bin\perl %lnmshome%/bin/cr_divdb
cd %lnmshome%\classes\com\baynetworks\div\dbi
%lnmshome%\perl\bin\perl %lnmshome%\bin\runimp Category.txt
%lnmshome%\perl\bin\perl %lnmshome%\bin\runimp Category_Attribute.txt
3 Start the DIV service with the command:

divs -start

Troubleshooting the Device Inventory Viewer

Table 159 lists the Device Inventory Viewer error messages, probable causes, and
remedial actions.
Table 159 Device Inventory Viewer error messages and remedial actions
Error Probable cause Suggested remedial action
Cannot add blank property You tried to create a new property Enter a name for the property
without entering a name.
Cannot add blank sub type You tried to add a new sub type with Enter a name for the sub type
the same name as an existing sub
type.
Cannot add blank type You tried to create a new type without Enter a name for the type
entering a name.
Cannot create device with You tried to create a new device Enter a name for the device
no name without entering a device name.
Cannot delete global sub You tried to delete a global sub type Select a non-global sub type to
type such as “Bay Networks Router” delete.
Cannot delete global type You tried to delete a global type such Select a non-global type to delete.
as “Switch” or “Router.”
Cannot find blank device You did not enter a search string in the Enter a valid device ID in the Find
Find dialog box. dialog box and try again.
Failed to add new device The application encountered an error Close and restart the application
while adding a new device.
Failed to create new sub
type
Failed to create new Type
Failed to delete device
Failed to delete property
Failed to delete sub type
Failed to delete Type
No more user defined The type already contains the Delete unused properties from the
properties can be added to maximum number of properties. type and try again.
the type
Property <prop name> You tried to add a new property with the Enter a different name for the
already exists! same name as an existing property. property.
Property name too long! You entered a property name that is too Enter a name for the property that is
Needs to be less than 32 long (greater than 32 characters). shorter than 32 characters.
characters
207569-F
Table 159 Device Inventory Viewer error messages and remedial actions (continued)
Error Probable cause Suggested remedial action
SubType already exists! You tried to add a new sub type with Enter a different name for the sub
the same name as an existing sub type.
type.
SubType needs to be a You entered a sub type name that Enter a sub type name that contains
single word with alphabets contains invalid characters. only alphanumeric characters.
and/or digits only
The property already exists You tried to add a new property with the Enter a different name for the
same name as an existing property. property.
The specified device You tried to add a new device with the Enter a different name for the device.
already exists same name as an existing device.
The sub type already exists You tried to add a new sub type with Enter a different name for the sub
the same name as an existing sub type.
type.
There are no repository You tried to synchronize the database Add a seed to the Repository Seeds
seeds to be synchronized without selecting any repository seeds list and try again.
This Type already exists You tried to add a new type with the Enter a different name for the type.
same name as an existing type.
Type already exists! You tried to add a new sub type with Enter a different name for the type.
the same name as an existing sub
type.
Type needs to be a single You entered a type name that contains Enter a sub type name that contains
word with alphabets and/or invalid characters. only alphanumeric characters.
digits only
Type size cannot exceed 30 You entered a property name that is too Enter a name for the type that is 30
characters long (greater than 32 characters). or fewer characters in length.

207569-F
731
Chapter 20
Tracing paths and locating end nodes
This chapter describes how to use the Path Trace feature to display path
information at the network layer and physical layer. It is divided into the following
major sections:
• “Path Trace overview‚” next

• “Getting started with Path Trace” on page 732
• “Working with Path Trace” on page 735
• “Troubleshooting using Path Trace” on page 741
You use Path Trace to identify all router interfaces and subnets that are forwarding
traffic between any two managed objects on your network. Path Trace also locates
end nodes such as end user workstations.
Path Trace overview

Path Trace uses Internet Control Message Protocol (ICMP), Simple Network
Management Protocol (SNMP), Telnet, and topology database information to
trace a path at the network layer, and relies on the topology database and SNMP
for physical layer tracing.
Path Trace displays the results of the trace in a view window in InfoCenter, and
also identifies MLT or SMLT links encountered along the path within subnets.
Path Trace graphically displays trace results in symmetrical, hierarchical, circular,
or orthogonal layout formats. You can start other Optivity NMS fault and
performance applications by right-clicking objects in a trace. You can also save a
trace to an InfoCenter folder and print a trace to your local printer.

732 Chapter 20 Tracing paths and locating end nodes
Path Trace uses several trace algorithms depending on the first router traced along
the path. You can specify end points in a trace using a host name, IP address,
system name, DNS name, or MAC address. You can run Path Trace on a subnet,
segment, or device.
Use Path Trace to detect network faults such as when a server is down, end node
to server operation is very slow, or router congestion.
For Path Trace to work optimally, do the following:
• Specify non-default read and read/write community strings of all managed

devices on your network using the Community Strings Editor or your
third-party network management application.
• Specify the Telnet login and password for all routers on your network using
the Community Strings Editor.
• Discover all managed devices and network resources using Topology
Manager. This process adds topology information to the Optivity NMS
topology database.
You can specify trace preferences on an individual basis or globally for all
subsequent traces.
Getting started with Path Trace

The following sections introduce the Path Trace application and describe how to
• “Access permissions‚” next

• “Path Trace terminology” on page 733
• “About end nodes” on page 734
• “Path Trace information window” on page 734
Access permissions
To use Path Trace, your Optivity user name must have the NPT_ACCESS
207569-F
Chapter 20 Tracing paths and locating end nodes 733
With read/write permission, you have full access to all Path Trace functions.
With read-only access permission, you can:
• Open Path Trace

• Run a path trace or locate end node function
An Optivity NMS administrator sets user access to Path Trace by configuring

access to the NPT_ACCESS token in the Access Control Administration window.
For information about setting access control permissions, see Chapter 2,
Administration,” on page 75.
Path Trace terminology
Table 160 describes terminology that you should understand when you use Path
Trace.
Table 160 Path Trace terminology
Feature Description
Live Trace A path trace that operates in the attached network first. If the live trace
fails or only partially succeeds, Path Trace attempts to determine the
full path from the Optivity topology database.
Database Trace A path trace that operates entirely using information from the Optivity
topology database.
Logical Path The subnets and routers between a source and destination host.
Path Trace uses SNMP and database algorithms to determine the
logical topology of routers. It locates end nodes but does not resolve
their logical topology.
The logical path traces the Network layer (layer 3) of the Open
Systems Interconnection (OSI) reference model.
Cached Trace A path trace based on cached information stored in the Optivity NMS
Server memory from previous traces.
By default, Path Trace stores all traces in memory and uses cached
information for new path traces.
Dynamic Trace When the IP address of network hosts are assigned using Dynamic
Host Configuration Protocol (DHCP), you can configure Path Trace to
dynamically trace the live network without using cached information.
You can configure both logical and physical tracing to be DHCP aware.

About end nodes
An end node is any device that is not a Nortel Networks device. Path Trace locates
devices connected directly or indirectly to Nortel Network devices in the subnet.
You can search for an end node using the following criteria:
• Name
• Label
• IP address
• MAC address
If an end node is connected to a switch that is a Nortel Networks device, the end
node is considered to be connected directly to the Nortel Networks device.
If an end node is connected to a switch that is not a Nortel Networks device, the
end node is defined as connected indirectly to the Nortel Networks device.
Figure 290 illustrates the concepts of direct and indirect connections.
Figure 290 Direct and indirect connections

End node
Nortel workstation
Networks
switch
Direct connection
End node
Nortel workstation
Networks Vendor
switch switch
Indirect connection
9329EA
Path Trace information window
The Path Trace information window opens in the InfoCenter window to

graphically display the results of a path trace or end node location.
207569-F
Objects within a trace or end node location are graphically represented using
InfoCenter topology icons. Links represent the path traced. Icon colors indicate
faults and differentiate parts of the path discovered in the live network from parts
determined from the topology database. The title bar displays the source and
destination IP address.
Figure 291 shows an example of a path trace information window.
Figure 291 Path Trace Information window
Using the Path Trace information window, you can right-click objects to start
other Optivity fault management applications against the path data. See “Starting
other Optivity NMS applications” on page 741 or more information.
Working with Path Trace

See the following sections for information about working with Path Trace.
• “Tracing a path between two devices‚” next

• “Locating an end node” on page 738
• “Starting other Optivity NMS applications” on page 741

Tracing a path between two devices
Path Trace can trace the path between two devices using information from the live
network or in the Optivity NMS Topology database.
To trace the path between two devices:
1 (Optional) on an InfoCenter folder view, click on two nodes.

Use Ctrl+click to select the second node.
• From the InfoCenter menu bar, choose View > PathTrace.
• On the InfoCenter toolbar, click the Path Trace button.
The Enter Path Information dialog box (Figure 292) opens.
Figure 292 Enter Path Information dialog box
3 Enter or change the host name, IP address, or MAC address of the source and
destination nodes.
4 Mark or clear the check boxes for the desired options.
207569-F
You must mark the Display Layer 2 Path check box to view MLT and SMLT
links on the active path. If the topology database has been updated since the
last time the path was traced, clear the Use cached Pathtrace information
check box to view the latest results.
5 Click Start.
A Progress alert box opens to show you the progress of the path trace
operation (Figure 293).
Figure 293 Progress alert box
When the trace completes a PathTrace Information window opens in the

InfoCenter contents pane to show a graphical layout of the trace results
(Figure 294).

Figure 294 PathTrace information window
If Path Trace is unable to trace the specified path, an Error Log window lists
error messages.
Locating an end node

Path Trace traces the path to an end node through your live network or by using
information in the Optivity NMS topology database. An end node trace involves
tracing from the end node to the device to which the end node is connected. Path
Trace initiates a live path trace by default.
The Trace in Progress status box indicates whether or not the trace is successful.
If the trace is successful the trace objects display in a window within the contents
pane.
To locate an end node:
1 (Optional) In an InfoCenter folder view, select an end node.

To view end nodes, transform the view to the End Node layer. See “Changing
the current view layer” on page 209 for information on changing to the end
node layer.
207569-F

• From the InfoCenter menu bar, choose View > PathTrace
• On the InfoCenter toolbar, click Path Trace
The Locate End Node dialog box (Figure 295) opens. If you selected a single
end node in step 1, the dialog box only shows options for locating an end
node.
Figure 295 Enter Trace Information dialog box (Single end node selected)
For detailed information about the Enter Trace Information dialog box, click
3 Type the host name, IP address, or MAC address of the end node.
4 Clear the Database Trace check box to do a live trace, or mark the check box
to only use data from the topology database.
Note: Choose Database Trace only if the end node already been
discovered by Autotopology. If the end node has not been discovered, a
database trace will fail.
5 Click Locate.

A Progress alert box opens to show you the progress of the operation
(Figure 296).
Figure 296 Progress alert box (locating an end node)
When the trace completes a PathTrace Information window opens in the

InfoCenter contents pane to show a graphical layout of the trace results
(Figure 297).
Figure 297 PathTrace information window (locating an end node)
If Path Trace is unable to locate the specified end node, an Error Log window
lists error messages.
207569-F
Starting other Optivity NMS applications
You can start other Optivity NMS fault and performance applications on objects in
a PathTrace Information window.
To start another Optivity NMS application on a traced object:
1 In the trace results window, right-click an object and choose either Fault or
Performance from the shortcut menu.
The submenu for that category command opens.
2 Choose the Optivity NMS application that you want.
Troubleshooting using Path Trace

The following sections describe how to investigate and resolve problems on your
network using Path Trace.
• “Object fault colors‚” next

• “Viewing error messages” on page 742
• “Resolving problems” on page 742
Object fault colors
Path Trace displays by default object fault color, so that you can immediately see a
fault on your network.
Table 161 defines the default object fault colors.
Table 161 Default Path Trace object fault colors
Color Fault
Blue Unmanaged object.

Green Object exists in the Optivity topology database and is operational.
Yellow Object returned a Caution fault.
Red Object returned an Alarm fault.

Viewing error messages
When Path Trace cannot trace a path or locate an end node that you specify, a
status box displays error messages that describe why the trace was not successful.
Resolving problems

results.
Table 162 Common problems and solutions
Problem Solution
Path Trace does not Verify that the apa.reg file is in the $LNMSHOME/registration/
start on a UNIX platform. weboptsrvr directory.
Path Trace does not Verify that the Optivity user has Read access to the IC,
start on any platform. IC_ADMIN, and NPT_ACCESS permission tokens in the
Access Control Administration window.
The View > PathTrace Verify that the Optivity user has Read/Write access to the
command is disabled. NPT_ACCESS permission token in the InfoCenter Access
You cannot initiate a Control Administration window.
trace.
You cannot start a You can start only one path trace at a time. Wait for the first
second trace. trace to complete before you initiate a second.
Live trace does not work You must set up Community Strings for the network using the
Community Strings Editor.
You cannot start Call You can only launch Call View from a Path Trace switch folder.
View from a Path Trace For example, if the same IP address appears both for a switch
hub folder. in a 5000 BH hub folder and in the switch folder, you cannot
start Call View from the IP address in the hub folder. You must
start Call View from the switch.
207569-F
743
Chapter 21
Managing data with the Database Admin Tool
• “Database Admin Tool overview‚” next

• “Getting started with the Database Admin Tool” on page 744
• “Working with the Database Admin Tool” on page 752
• “Troubleshooting Database Admin Tool” on page 767
Database Admin Tool overview

The Database Admin Tool lets you view and administer Optivity NMS application
and user databases.
Use the Database Admin Tool to:
• Import and export a database

• Delete a database
• Get elements of a database
• Display Optivity NMS and Oracle software operational status
• Reset the Optivity NMS database
• Start and stop the Oracle instance
• View element properties

744 Chapter 21 Managing data with the Database Admin Tool
Getting started with the Database Admin Tool

See the following sections for information about getting started with the Database
Admin Tool:
• “Access permissions for the Database Admin Tool‚” next

• “Database definitions” on page 744
• “Starting the Database Admin Tool” on page 746
• “Database Admin Tool window” on page 747
Access permissions for the Database Admin Tool
Your access to the Database Admin Tool depends on the permission tokens
assigned for your user name in Access Control. Table 163 describes the tokens
and permissions are required to access the Database Admin Tool.
Table 163 Database Admin Tool access permissions
Token Permission
DB_ADMIN_ACCESS Read/write
IC Read
IC_ADMIN Read
OM_READ_STATS Read
OM_CONF_TEMPL Read
OM_CONF_ALLUSERS Read
OM_SNMP_SETS Read
Database definitions
Optivity NMS uses the Oracle relational database management system for back
end data storage. The Optivity NMS database is implemented as a single Oracle
database consisting of data for eight core Optivity NMS databases (dynamic and
pre-packaged) and as many user databases as you want to define. Optivity NMS
installs a pre-packaged database. It also generates some databases dynamically, as
you create data or use a feature.
207569-F
Chapter 21 Managing data with the Database Admin Tool 745
Table 164 describes the Optivity NMS databases.
Table 164 Optivity NMS databases
Database name Description
AppControlDB Contains application user preferences and default configuration

settings, community string information for platformless environments,
access control information for user application authorization,
application launch point information, user-defined InfoCenter default
folder definitions, and InfoCenter custom folder information.
This database is pre-packaged with the Optivity NMS installation, and
data is added as you use Optivity NMS applications.
evomni Stores OmniView and Expanded View device MIB attribute
information such as ports, slots, and media type. Most information is
static. The database may contain customized information for
non-Nortel Networks devices.
This database is pre-packaged with the Optivity NMS installation.
fault Stores Fault Correlator information. The Fault Correlator application
processes all traps, converts them to faults, and places them in this
database. The size of the database is determined by options you set
in the Fault Correlator application.
vogon Stores all Autotopology configuration information.
smop Stores global topology information for hubs, switches, subnets, and
VLANS. It also stores all user seed information.
Optivity NMS generates this database dynamically after installation.
waldo Contains the same type of information as the smop.db database, but
the data comes from end-node discovery. Information is added to the
database only if end-node discovery is turned on.
mibdb Stores SNMP, Nortel Networks, and open user MIB-II information.
This database is pre-packaged with the Optivity NMS installation.
<Login_name> For each Optivity NMS user, stores a user database. Each user
database contains references to the smop.db database so users have
a subset of the smop.db information.
Optivity NMS generates this database dynamically.

The Optivity NMS database installer program installs the Optivity NMS database
in a location that you specify during the database installation process:
• For UNIX, the database directory is organized similar to the following:

<mount_point1>/app/oracle (Oracle software)
<mount_point1>/oradata/nmsdb (Optivity NMS database)
• For Windows NT* and Windows* 2000, the database directory is organized
similar to the following:
<drive>:\<folder_name>\oracle\ora92 (Oracle software)
<drive>:\<folder_name>\oradata\nmsdb (Optivity NMS database)
Starting the Database Admin Tool
Note: You must run the Database Administration Tool from the system
on which the server resides. When you use a client-only system, or when
you log in remotely, some Database menu options are unavailable under
the Admin menu.
To start Database Admin Tool:
Table 165 Starting Database Admin Tool
To start Database
Admin Tool from: Do this:
InfoCenter Choose Admin > Database
Note: If the Database menu command is disabled, it means you do

not have the proper access permissions to use Database Admin
Tool.
Windows Start Choose Start > Programs > Optivity > DatabaseAdmin
menu
command prompt
dbadmin
207569-F
Table 165 Starting Database Admin Tool (continued)
To start Database
Admin Tool from: Do this:
prompt
dbadmin
Click the Database Admin Tool icon on the Optivity Web page.

feature to bookmark the Database Admin Tool application. Doing so
saves the URL for Database Admin Tool.
If you are not starting Database Admin Tool from InfoCenter, the Connect to
Optivity Server dialog box opens.
The Database Admin Tool window opens.
Database Admin Tool window
The Database Admin Tool window has four parts as shown in Figure 298.

Figure 298 Parts of the Database Admin Tool window
Menu bar
Database
pane
Element
pane
Status
bar
Table 166 describes the Database Admin Tool window parts.
Table 166 Database Admin Tool window parts
Part Description
Menu bar Contains commands for operating Database Admin Tool. For more
information, see “Menu bar” on page 748.
Database pane Contains a list of all databases contained on the connected host. For
more information, see “Database pane” on page 750.
Element pane Contains a table of elements in the selected database. For more
information, see “Element pane” on page 751.
Status bar Displays error and informational messages from the application.
Menu bar
The Database Admin Tool menu bar provides commands that let you administer
Optivity NMS databases and access online Help. If you open the Database Admin
Tool in a Web browser, the menu bar is not displayed, but is accessed from a tool
in the Database Admin Tool Web browser toolbar. The first tool in the toolbar
opens a shortcut menu of Database Admin Tool menus and submenus.
207569-F
Table 167 describes the Database Admin Tool menus.
Table 167 Database Admin Tool menus
File Exit Disconnects from Database Admin Tool and closes the Database Admin
Tool window.
Database Import Imports the contents of the specified database file into the selected
database. For more information, see “Importing a database” on page 753.
Export Exports the contents of the selected database to the specified file. For
more information, see “Exporting a database” on page 758.
Delete Deletes all data from the selected database. The Delete command is not
available if mibdb.db or evomni.db is selected. For more information, see
“Deleting databases” on page 760.
Get Elements Displays the elements of the selected database in the element pane. For
more information, see “Retrieving elements of a database” on page 764.
Element View Properties Shows the properties of the selected element. For more information, see
“Viewing element properties” on page 764.
Tools Optivity Status Reports the operational status of Optivity NMS daemons or services. See
“Viewing Optivity NMS status” on page 766 for more information.
Oracle Status Reports the status of the Oracle database instance for Optivity NMS. See
“Viewing Oracle status” on page 766 for more information.
Start Oracle Starts the Oracle instance and Optivity NMS daemons or services. See
Instance “Starting and shutting down an Oracle instance” on page 767 for more
information.
Shutdown Oracle Stops the Optivity NMS server processes and stops the Oracle instance.
Instance See “Starting and shutting down an Oracle instance” on page 767 for
more information.
Reset Database Resets all Optivity NMS application databases to the factory default state,
as they were when Optivity NMS is first installed and before conducting a
topology discovery of your network. All customization, topology discovery
information, and fault data is lost. See “Resetting the database” on
page 763 and Release Notes for Optivity NMS 10.3 for more information.
Help Database Admin Opens the Database Admin Tool online Help.
Tool Help
Using Help Opens a Help topic about using the online Help system.
About the Displays version and copyright information for the Database Admin Tool.
Database Admin
Tool

Toolbar
The toolbar is available when the Database Admin Tool is started in a Web
browser. The toolbar button in Figure 299 opens the Database Admin Tool menu
in a Web browser.
Figure 299 Database Admin Tool Menu toolbar button in a Web browser
Database pane
The database pane contains a tree of folders that represent all databases that have
been defined in Optivity NMS.
When you click a database folder in the database pane, you can:
• Display the database elements in the element pane if they have already been
retrieved by the get element function.
• Use any of the database commands.
• See the number of elements in the selected database on the status bar.
Figure 300 shows the parts of the database pane.
Figure 300 Database pane
Optivity NMS server

User’s name database
Optivity NMS databases
207569-F
Table 168 describes the parts of the database pane.
Table 168 Database pane parts
Part Description
Optivity NMS server IP address or DNS name of the server where the database is
discovered.
User’s name database User’s name for which the database is created.
Optivity NMS databases A list of the Optivity NMS databases.
For more information, see “Database definitions” on
page 744.
Element pane
The element pane displays a table that lists the elements in the selected database.
Figure 301 shows the parts of the element pane.
Figure 301 Element pane parts
Element
category
Element
name
Table 169 describes the parts of the element pane.
Table 169 Element pane parts
Part Description
Element category Column heading for element data.

Element name Lists the name of the database element.

Table 170 describes how to work with elements in the element pane.
Table 170 How to work with elements in the element pane
Action Results
Click a database element Selects a single element.

Double click database element Displays the element properties.
Working with the Database Admin Tool

The Database Admin Tool lets you administer your database. The following
sections describe how to work with the Database Admin Tool:
• “Working with databases‚” next

• “Working with elements” on page 763
• “Working with database status tools” on page 765
Working with databases
The following sections describe how to work with databases:
• “Importing a database‚” next

• “Exporting a database” on page 758
• “Deleting databases” on page 760
• “Resetting the database” on page 763
207569-F
Importing a database
You can import (restore) a saved Optivity NMS database.
Note: Observe the following points when you import databases with
Database Admin Tool:
• You can only export or import an Optivity NMS database when you
run the Database Admin Tool on a system where the Optivity NMS
server software is installed. The export and import function are
disabled on a client-only installation.
• You can only export or import while running the Database Admin
Tool outside a Web browser. When running Database Admin Tool in
a Web browser, the export and import menu commands are disabled.
• Importing an Optivity NMS database adds the data from the saved
file to the specified database, but does not remove any of the
contents of the database. If you want to limit the contents of the
imported database to the contents of the backup file, delete the
database before you perform the import function. See “Retrieving
elements of a database” on page 764 for more information.
• You cannot import or export the evomni.db or mib.db databases.
• Nortel Networks recommends that you stop all Optivity NMS
daemons (UNIX) or services (Windows) before you delete or import
a database.
The following sections describe the two ways in which you can import a database
from an Optivity NMS server:
• “Importing a database from the Database Admin Tool database pane‚” next.
• “Importing a database from the Database Admin Tool shortcut menu” on
page 756.
Importing a database from the Database Admin Tool database pane
To import a database from the Database Admin Tool database pane:

• In the Windows environment, stop Optivity NMS services except the
Oracle instance.

• In the UNIX environment, stop Optivity NMS daemons.

• In Windows, in the Services dialog box, click the Optivity NMS
Weboptserver service and click Start.
• In UNIX, enter:
cd $LNMSHOME/opt_install
weboptsrvr_restart start
The Webopt server starts.
3 Start the Database Admin Tool.

For more information, see “Starting the Database Admin Tool” on page 746.
4 In the database pane, click a database name.
5 From the Database Admin Tool menu bar, choose Database > Import.
The Import Database dialog box opens. Figure 302 shows the Import
Database dialog box in the UNIX environment.
Figure 302 Import Database dialog box in UNIX
207569-F
Figure 303 shows the Import Database dialog box in the Windows
environment.
Figure 303 Import Database dialog box in Windows

• In the UNIX environment, do one of the following:
— Type the directory name in the Enter Path or folder name box and
click Enter.
click Update.
• In the Windows environment, navigate to the database directory.
The database file is displayed in the files pane.
7 Click the database file.
— Click Yes to continue with importing the database.
— Click No to cancel the operation.
— Click Open to import the database.
— Click Cancel abort the operation.


• In the Windows environment, start all Optivity NMS services.
• In the UNIX environment, start all Optivity NMS daemons.
Importing a database from the Database Admin Tool shortcut menu
To import a database from the Database Admin Tool shortcut menu:

• In the Windows environment, stop Optivity NMS services.
• In the UNIX environment, stop Optivity NMS daemons.
• In Windows, in the Services dialog box, click the Optivity NMS Webopt
server service and click Start.
• In UNIX, enter:

4 Right-click a database folder in the database pane and choose Import from the
shortcut menu.
The Import Database dialog box opens. (See Figure 302 on page 754 for
UNIX and Figure 303 on page 755 for Windows.)
207569-F

press Enter.
click Update.
The database file is displayed in the files pane.
6 Click the database file.

— Click Open to import the database.
— Click Cancel abort the operation.
— Click Yes to continue with importing the database.
— Click No to cancel the operation.
Caution: When you import one of the following databases, you must
import the other two at the same time:
• smop
• waldo (exists only if end node discovery is turned on)
• user database


Exporting a database
The Database Admin Tool lets you use the export (back up) function to save your
database.
Note: You can only export or import while running the Database Admin
Tool outside a Web browser. When running Database Admin Tool in a
Web browser, the export and import menu commands are disabled.
Also, you cannot import or export the evomni.db or mib.db databases.
As with any important data, periodically export the Optivity NMS database to
protect it from hard disk failure, accidental deletion, or other unexpected loss.
Backing up the database also gives you a “snapshot” of the database information
at a certain point in time. After you back up the database, you can later import the
backup copy of the database if this becomes necessary.
When you export an Optivity NMS database, you are only prompted for a single
file name for the backup.The file names are displayed in a message at the end of
the backup process.
The following sections describe the two ways in which you can export a database
from an Optivity NMS server:
• “Exporting a database from the Database Admin Tool database pane” on

page 758.
• “Exporting a database using the Database Admin Tool shortcut menu” on
page 760.
Exporting a database from the Database Admin Tool database pane
To export a database from the Database Admin Tool database pane:
1 In the database pane, click a database name.

2 From the Database Admin Tool menu bar, choose Database > Export.
The Export Database dialog box opens. Figure 304 shows the Export
Database dialog box in the UNIX environment.
207569-F
Figure 304 Export Database dialog box In UNIX
Figure 305 shows the Export Database dialog box in the Windows
environment.
Figure 305 Export Database dialog box in Windows
3 Enter a directory path and file name.

4 Click Save.
The system displays a message that the export operation is successful.
Exporting a database using the Database Admin Tool shortcut menu
To export a database using the Database Admin Tool shortcut menu:
1 Right-click a database folder in the database pane and choose Export from the
shortcut menu.
The Export Database dialog box opens. (See Figure 304 on page 759 for
UNIX and Figure 305 on page 759 for Windows.)
2 Enter a directory path and file name.

3 Click Save.
The system displays a message that the export operation is successful.
Caution: When you export one of the following databases, you must
export the other two at the same time:
• smop
• waldo (exists only if end node discovery is enabled)
• user database
Deleting databases
The Database Admin Tool lets you delete data from the selected database.
The Database Admin Tool does not let you delete data from the evomni or mibdb
database. You must use the rm_appdb utility from the UNIX or Windows
command line to remove data from the evomni or mibdb database. See “Deleting a
database at the command line” on page 762 for more information.
The following sections describe how to delete a database:
• “Deleting a database using Database Admin Tool‚” next

• “Deleting a database at the command line” on page 762
207569-F
See “Database definitions” on page 744 for more information about the databases.
Caution: Optivity NMS will not function properly if any of the

following databases are deleted:
• mibdb
• vogon
• appControlDB
• evomni
Make sure that all of the above databases are intact before you start
Optivity NMS applications.
Deleting a database using Database Admin Tool
To delete a database:
1 Close all Optivity NMS applications and windows.

• In the Windows environment, stop all Optivity NMS services.
• In the UNIX environment, stop all Optivity NMS daemons.
• In the Windows environment, in the Services dialog box, click the
Optivity NMS Webopt server service and click Start.
• In the UNIX environment, enter:

5 Click a database in the database pane.

6 From the Database Admin Tool menu bar, choose Database > Delete.
Note: The Delete command is not available if you select mibdb or

evomni database.
The data from the database is deleted.

Deleting a database at the command line
You can use the rm_appdb command line utility to delete all data from any of the
Optivity NMS databases, including evomni and mibdb.
Caution: The evomni and mibdb databases are required for Optivity
NMS applications to operate. If you delete either of these databases, you
must restore them from backup copies.
Note: The evomni and mibdb databases contains large amounts of data.
Deleting data from or importing data into these databases takes a
significant amount of time.
To delete a database at the command line:
1 Close all Optivity NMS applications and windows.

2 Use the following command to stop all Optivity NMS daemons or services:
optivity_apps stop
3 Use the following command to delete the database:
rm_appdb -p nms -f <database_name>
Where <database_name> specifies one of the databases listed in the section
“Database definitions” on page 744.
207569-F
Resetting the database
The Database Admin Tool lets you reset the Optivity NMS database to the factory
defaults.
Note: Resetting the database removes all customization and topology

discovery data. The database is returned to the state that it was in when
you first installed Optivity NMS software.
To reset the Optivity NMS database to factory defaults:

2 From the Database Admin Tool menu bar, choose Tools > Reset Database.
Database Admin Tool Opens a dialog box that prompts you to insert the
Optivity NMS software installation CD. The dialog box also prompts you to
enter the letter or name of the CD drive.
3 Insert the Optivity NMS 10.3 CLIENT and SERVER CD into the CD-ROM
drive.
4 Enter the letter or name of the CD drive in the text box.
Database Admin Tool reinstalls the pre-packaged Optivity NMS Oracle
database. The system displays a message indicating that the reset database
operation is successful. All Optivity NMS daemons are closed before the
database is reset to factory defaults. All Optivity NMS daemons are restarted
after the database is restored to factory defaults.
Working with elements
The following sections describe how Database Admin Tool lets you work with
specific elements for a database:
• “Retrieving elements of a database‚” next

• “Viewing element properties” on page 764

Retrieving elements of a database
The Database Admin Tool lets you monitor database elements in the element
pane. You use the Get Elements command to retrieve the elements of the selected
database.
Note: The Get Elements feature is disabled for the evomni and mibdb
databases.
To retrieve database elements:
1 In the database pane, select a database.

2 From the Database Admin Tool menu bar, choose Database > Get Elements.
Current elements for the selected database are displayed in the element pane.
Viewing element properties
Table 171 describes how to work with elements in the element pane.
Table 171 How to work with database objects in the element pane
Action Results
Click a database element Selects a single element.

Double-click a database element Displays the element properties.
207569-F
To view element properties for a database, do one of the following:
Right-click the element and choose Properties from the shortcut menu.
From the Database Admin Tool menu bar, choose Element > View Elements.
The View Element Properties dialog box opens (Figure 306).
Figure 306 View Element Properties dialog box
Working with database status tools

The following sections describe how Database Admin Tool lets you view the
status for Optivity NMS daemons or services and the Oracle software:
• “Viewing Optivity NMS status‚” next

• “Viewing Oracle status” on page 766
• “Starting and shutting down an Oracle instance” on page 767

Viewing Optivity NMS status
To get the status of Optivity NMS:
From the Database Admin Tool menu bar, choose Tools > Optivity Status.
The Optivity status message opens as shown in Figure 307, and displays
Optivity NMS status.
Figure 307 Optivity status message box
Viewing Oracle status
To view the Oracle status:
From the Database Admin Tool menu bar, choose Tools > Oracle Status.
The Oracle Status message opens as shown in Figure 308, and displays Oracle
status.
Figure 308 Oracle Status message box
207569-F
Starting and shutting down an Oracle instance
To start an Oracle instance:
From the Database Admin Tool menu bar, click > Tools > Start Oracle
Instance.
The Oracle instance starts and all Optivity NMS daemons or services start.
To shut down an Oracle instance:
From the Database Admin Tool menu bar, click Tools > Shutdown Oracle
Instance.
Optivity NMS daemons or services are stopped and the Oracle instance shut
down.
Troubleshooting Database Admin Tool

results with the Database Admin Tool.
Table 172 Database Admin Tool problem solutions
Problem Solution
An Optivity user cannot If access control is enabled on the Optivity NMS server,
launch Database Admin Tool. make sure all authorized users have read/write access to
the following permission tokens:
• IC
• IC_ADMIN
• DB_ADMIN_ACCT
See the Access Control Administration online Help for
more information about these tokens.

207569-F
769
Chapter 22
Administering device support using OIT
• “OIT overview” on page 769

• “Getting started with OIT Administration Tool” on page 770
• “Working with the OIT Administration Tool” on page 777
• “Working with oitInstall” on page 786
• “Device support added in Optivity NMS 10.3 using OIT” on page 788
• “Troubleshooting OIT Administration Tool” on page 791
OIT overview
The Optivity Integration Toolkit (OIT) lets you administer device support for new
and updated devices and agents. You can install OIT packages directly from the
Web or download and install OIT packages at a later date.
Optivity NMS provides two types of OIT applications that you can use to
administer device support:
• OIT Administration Tool (graphical interface)

• oitInstall (command line application)
The OIT Administration Tool provides a graphical user interface (GUI), from
which you can:
• View devices and agents currently supported or installed by Optivity NMS

• Install packages that are already downloaded
• View available packages for update and install the selected package
• View detailed trap and module information about devices that are installed

770 Chapter 22 Administering device support using OIT
• Print a text file report listing all of the installed devices
The oitInstall application is executed from the command line. You can use the
oitInstall application to also perform OIT-related administration tasks.
Getting started with OIT Administration Tool

The OIT Administration Tool lets you administer device support. You use the OIT
Administration Tool to install OIT packages. If new OIT updates are found, you
can download and install the selected OIT package, to add support for devices and
device management applications integrated into Optivity NMS.
Optivity NMS 10.3 provides modular support for devices and device management
software. Using the OIT Administration Tool, you can quickly integrate Nortel
Networks devices and device management applications without upgrading your
Optivity NMS installation. When you upgrade Optivity NMS with a specific
device support, you can use Optivity NMS to discover and manage that device
through existing Optivity NMS applications, such as OmniView, Expanded View,
or Fault Summary.
Device management applications can also be integrated through a launch point,

for example Device Manager for a Passport* 8610 switch or Element
Management System (EMS) for an Alteon* 2224 switch.
The following sections introduce the OIT Administration Tool and tell how to get
started using it:
• “Devices and device management applications‚” next

• “Understanding the OIT installation process” on page 773
• “Starting the OIT applications” on page 774
• “Access permissions for OIT” on page 774
• “OIT Administration Tool window” on page 775
207569-F
Chapter 22 Administering device support using OIT 771
Devices and device management applications
Nortel Networks distributes devices and device manager applications as follows:
• OIT files for devices are made available to you on the Web.
• OIT files for device management applications such as Site Manager and
Annex Manager are either posted on the Web or bundled with Optivity NMS.
However, the actual device management applications are available only
through the Web. Therefore, management application integration does not
occur automatically during the Optivity NMS 10.3 installation process.
For more information, see “Obtaining support for new or updated devices and
applications” on page 771.
Table 173 summarizes how Nortel Networks distributes devices and device
management applications.
Table 173 How devices and device applications are distributed
Packaged on the
Obtained from
Bundled with Optivity NMS
the Web?
Product Optivity NMS? software CD?
OIT files for device support No No Yes

OIT files for device Yes No Yes
management applications
Device management No No Yes
applications
Obtaining support for new or updated devices and applications
There are two possible scenarios for adding new device support to Optivity NMS
applications:
• If a new device OIT package is available before the latest major or minor
version of Optivity NMS ships, the new device support is bundled with
Optivity NMS. In this case, the new device is already added to the Optivity
NMS database. You do not need to integrate this device support into Optivity
NMS by using oitInstall.

• If the new device OIT package is available after the latest version of Optivity
NMS ships, the OIT file for the new device is posted on the Web. In this case,
the new device is not integrated into the Optivity NMS database. You obtain
the new device OIT file from the Web and use the OIT Administration Tool or
oitInstall application to update the Optivity NMS database with the new
device.
For more information about adding a device to the Optivity NMS database:
• In the Windows environment, see the Readme file in the

\Optivity\Oit\<device_name> directory.
• In the UNIX environment, see the readme file in the /usr/oit/
<device_management_application> directory.
• From the Web, see the readme file included with the downloaded OIT
package file.
There are two possible scenarios for obtaining support in Optivity NMS for a new
or updated device manager application:
• If an OIT package for the new or updated device management application is

bundled with Optivity NMS, download the device management applications
from the Web. After you complete the Optivity NMS installation, use the OIT
Administration Tool or oitInstall application to manually integrate the device
management application with Optivity NMS.
• Otherwise, download the OIT files for the device management application
that are posted on the Web. You must also obtain the device management
application from the Web and use the OIT Administration Tool or oitInstall
application to manually integrate the device management application with
Optivity NMS.
For more information about integrating a device management application with

Optivity NMS:
• In the Windows environment, see the readme file in the

C:\Optivity\OIT\<device_management_application> directory.
• For the UNIX environment, see the readme file in the /usr/oit
<device_management_application> directory.
• From the Web, view the readme file included with the OIT package.
207569-F
Understanding the OIT installation process
The OIT Administration Tool and oitInstall application let you extract the
necessary information that Optivity NMS needs for either a device or a device
management application and integrates it into Optivity NMS. This information
includes but is not limited to the following:
• Database schema definitions

• MIB information
• Trap information
• Device management application launch points from within Optivity NMS
applications
• Device discovery information
The OIT Administration Tool and oitInstall program does the following:
• Automatically stops and restarts all Optivity NMS daemons (UNIX) or

services (Windows).
• Automatically backs up the Optivity NMS databases (by default /usr/oit/oitdb
for UNIX and C:\Optivity\oit\oitdb for Windows). The OIT Administration
Tool and oitInstall program automatically restores the database if the device
support installation fails.
• Updates Optivity NMS with the new device and device management support,
and deletes the database backup if the integration is successful.
Note: If you do not need additional support for devices other than those
that Optivity NMS supports, you do NOT need to use the OIT
Administration Tool or oitInstall program.
Nortel Networks recommends that you maintain a separate backup of
Optivity NMS 10.3 databases before adding new device support. The
backups performed by the OIT Administration Tool and oitInstall
program are automatically deleted at the end of the install process. For
more information, see the Database Administration Tool Online Help or
Using Optivity NMS 10.3 Applications (part number 207569-F).

Starting the OIT applications
To start OIT Administration Tool or oitinstall, take one of the actions shown in
Table 174.
Table 174 Starting OIT Administration Tool and oitinstall
OIT Administration Windows cd %lnmshome%\bin

Tool (graphical command
interface) prompt oitadmin
command
prompt oitadmin
oitInstall (command Windows cd %lnmshome%\bin
line application) command
prompt oitInstall
command
prompt oitInstall
Access permissions for OIT
You must have administrative (Windows) or root (UNIX) permission to use he

OIT Administration Tool to install an OIT package.
Table 175 indicates the level of access a user has with read-only, read/write, or no
access to the three required permission tokens.
Table 175 Access permissions
Permission Access
None No access. The OIT Administration Tool window does not open.
Read only User can view the OIT Administration Tool, but cannot add, delete,
modify, or change the order of entries. Import, export, and save
commands are also disabled.
Read/write User has full access to all features of the OIT Administration Tool.
207569-F
OIT Administration Tool window
The OIT Administration Tool window is shown in Figure 309.
Figure 309 OIT Administration Tool window
Menu bar
Toolbar
Contents
area
Table 176 describes the parts of the OIT Administration Tool window.
Table 176 Parts of the OIT Administration Tool window
Part Description
Menu bar Provides access to all available OIT Administration Tool commands.
Toolbar Provides quick access to commonly used OIT Administration Tool
commands.
Contents area Displays the OIT packages currently installed on the system.
See “Viewing an inventory of installed OIT files” on page 777 for more
information.

The OIT Administration Tool menu bar and toolbar contain commands that let
you administer OIT packages for the Optivity NMS server.
Table 177 shows the menu names, command names, toolbar buttons, and
command descriptions.
Toolbar
button
Menu Opens the OIT Administration Tool menu in a Web browser.

File Save As Text Saves the installed OIT packages displayed in the OIT
Administration Tool contents area as a text file to the specified
location and file name.
See “Saving the list of installed OIT packages as a text file” on
page 779.
Exit Closes the OIT Administration Tool window.
View Package Info Shows package information for the selected component
Tools Install Component Installs an OIT package that is already downloaded.
Update Lets you access the Nortel Networks FTP server, to learn
Components about new and updated OIT packages. Lets you select an OIT
package to download and install.
Help OIT Administration Opens the OIT Administration Tool online Help.
Tool Help
Using Help Opens online Help about how to use the OIT Administration
Tool online Help.
About OIT Displays the software version and copyright information for the
Administration OIT Administration Tool application.
Tool
207569-F
Working with the OIT Administration Tool

The OIT Administration Tool provides a graphical user interface that lets you
administer OIT packages installed on the Optivity NMS server.
The following sections describe how to use the OIT Administration Tool:
• “Viewing an inventory of installed OIT files” on page 777

• “Viewing an OIT module and trap information” on page 778
• “Saving the list of installed OIT packages as a text file” on page 779
• “Installing an OIT package that is already downloaded” on page 780
• “Using the OIT Administration Tool to update installed OIT packages” on
page 782
Viewing an inventory of installed OIT files
The OIT Administration Tool lets you view information about all of the OIT
packages that are installed on the Optivity NMS server.
To start the OIT Administration application to view a list of OIT devices:
At the DOS or UNIX command line, enter:

oitadmin
The OIT Administration Tool window opens. All of the OIT packages that are
installed on the system (including OIT packages that are bundled with
Optivity NMS) are displayed in the contents area of the window. The contents
area contains:
• The device name
• Agent version
• OIT package name of all of the OIT packages currently installed

Viewing an OIT module and trap information
To view OIT module and trap information:
1 Double click a device row.

The Package Information dialog box opens as shown in (Figure 310).
Figure 310 Package Information dialog box
2 Click the Traps tab.

The Package Informations traps are displayed in (Figure 311).
207569-F
Figure 311 Package Information traps
Saving the list of installed OIT packages as a text file
To save the installed OIT packages as a text file:

• From the menu bar, click File > Save as Text.
• Press Ctrl + T
The Save As dialog box opens.
2 Type the path and name of the file in the respective boxes.
• In a Windows environment, click Save.
• In a UNIX environment, click OK.
The OIT packages displayed in the contents area are saved to a text file,
similar to (Figure 312).

Figure 312 OIT packages saved as a text file
Installing an OIT package that is already downloaded
The OIT Administration Tool lets you install an OIT package that is already
downloaded. After installing a package, the OIT Administration Tool updates the
list of installed OIT packages.
Table 178 list the different types files that you can install.
Table 178 User-selected file types
Type Description
tar Tape Archive file (UNIX)

gz Gnu Zip file (UNIX)
oit oit file (UNIX or Windows)
exe Exe file (Windows)
Or the file selected in an
install file with the filename:
install UNIX
install.bat Windows
207569-F
To install an OIT package that is already downloaded:

• In a Windows environment, open a command prompt or MS-DOS
window.
• In a UNIX environment, open a command tool or terminal window.
oitadmin
The OIT Administration Tool window opens
3 From the menu bar, click Tool > Install component.
The Open dialog box opens as shown in Figure 313.
Figure 313 Open dialog box

4 Navigate to the location of the OIT package you want to install.

5 Select the OIT file.
• In a Windows environment, click Open.
• In a UNIX environment, click OK.
The following series of events transpire:
• The OIT installation process starts, and the system displays the progress
and the status of the OIT installation process.
• The system displays a message indicating that the OIT installation is
completed.
The list of installed OIT packages is updated in the contents area.
Using the OIT Administration Tool to update installed OIT

packages
The OIT Administration Tool lets you access the Nortel Networks FTP server to
learn about new or updated OIT packages that are not already installed on your
Optivity NMS server. You can select a new or updated OIT package from the list
and use the OIT Administration Tool to do either of the following:
• Download and install the OIT package

• Download the OIT package only
After an OIT package is downloaded, the OIT Administration Tool prompts
you to install or not install the package. If choose not to install the package,
you can use the OIT Administration Tool to install it later date. See
“Cancelling an OIT Administration Tool update process and “Installing an
OIT package that is already downloaded” for more information.
207569-F
Updating OIT packages using the OIT Administration Tool
You must have direct FTP access to the Nortel Networks FTP Web site to use the
OIT Administration Tool to update OIT packages on your system. If a FTP proxy
server is used at your site to access the Internet, you must configure the OIT
Administration Tool to use the FTP proxy server to access the Nortel Networks
FTP Web site. See “Configuring an FTP proxy server” on page 784 for more
information.
To update OIT packages:

• In a Windows environment, open a command or MS-DOS prompt
window.
• In a UNIX environment, open a command tool or Terminal window.
oitadmin
The OIT Admin Tool window opens, displaying a list of all the installed OIT
packages.
3 From the menu bar, click Tool > Update package.
System displays the list of available OIT packages that are not installed.
4 Select the OIT package.
The OIT package is downloaded to the system. You are prompted to read the
readme file before proceeding with installation process.
5 Click Update.
readme file before proceeding with installation process and click yes to
proceed.
6 Click Yes to proceed with the installation.
The system displays a message that the installation is completed, and the
installed package is displayed in the contents area.

Cancelling an OIT Administration Tool update process
The OIT Administration Tool lets you cancel an installation process. In this case,
the OIT package is stored on the system but not installed.
To cancel an update option installation process:

window.
oitadmin
The OIT Administration Tool window opens, displaying a list of all the
installed OIT packages.
3 From the menu bar, click Tool > Update package.
System displays the list of available OIT packages that are not installed.
4 Select the OIT package.
5 Click Update.
readme file before proceeding with installation process and click yes to
proceed.
6 Click No to proceed with the installation.
The installation process is terminated.
Configuring an FTP proxy server
Optivity NMS lets you configure the OIT Administration Tool to use your FTP
proxy server to access the Nortel Networks FTP Web site. See “Using the OIT
Administration Tool to update installed OIT packages” on page 782 for more
information about installing OIT packages.
207569-F
To configure a FTP proxy server to access the Nortel Networks FTP Web site:

window.
2 Change to the following directory where the OIT Administration Tool
AdminToolConf.properties file is located.
$LNMSHOME/classes/com/baynetworks/oit/oitadmintool/app
3 Open the AdminToolConf.properties file in a text editor.
The AdminToolConf.properties file is displayed
Figure 314 AdminToolConf.properties file
4 Edit the AdminToolConf.properties file to add the following:

• FTPProxyHost
• FTPProxyPort
5 Save the file.

Working with oitInstall

Optivity NMS lets you use the oitInstall application from a Windows or UNIX
command line to administer device support. See “Working with the OIT
Administration Tool” on page 777 for information about using the OIT
Administration Tool.
The following sections describe how to use the oitInstall application:
• “Installing device support using oitInstall‚” next

• “Adding device support through oitInstall” on page 787
• “Launching a device management application” on page 788
Installing device support using oitInstall
This section provides a typical example of using the oitInstall application to install
new device support for Optivity NMS.
For specific information, refer to the installation instructions in the readme file for
each OIT package:
• For the Windows environment, see the readme file in the

C:\Optivity\OIT\<device_name> directory.
• For the UNIX environment, see the readme file in the
/usr/oit/<device_name> directory.
To manually install new device support for Optivity NMS:

• In a Windows environment, log in as Administrator.
• In a UNIX environment, log in as root.
window.
• In a UNIX environment, open a command tool or terminal window.
3 Down load the OIT package from the Web site.
207569-F
4 Unzip (Windows) or untar (UNIX) the OIT package into the following
location:
C:\Optivity\OIT (Windows)
/usr/oit (UNIX)
5 Change to the directory where the *.oit file is located for the device support
that you want in Optivity NMS.
You can access device upgrade OIT files from a product upgrade package, or
from a Web server. Follow the instructions in the readme files that are
included with your device upgrade.
OIT files are located in specific directories under $OITHOME.
(For example, for UNIX go to /usr/oit/<device_name>, and for Windows go
to C:\Optivity\oit\<device_name>. When you installed Optivity NMS, the
Installation program creates an $OITHOME environment variable for the
location of OIT device support integration files.
6 At the command prompt, enter:
oitInstall -u <pathname_to_OIT_file>
• For example, In a Windows environment, enter:

oitInstall -u C:\Optivity\oit\accelar\dm\lm\dmvm.oit
• For example, In a UNIX environment, enter:
oitInstall -u $OITHOME/accelar/accelar_1200
/accelar_1200.oit
The -u option upgrades Optivity NMS. If you do not specify the -u option, a
syntax check only is performed on the OIT file.
The device support process starts.
Adding device support through oitInstall
When you install Optivity NMS 10.3, the installation program updates the OIT
database with the information for all the added devices.
When you upgrade Optivity NMS 10.3 with new device support, the OIT database
is updated with an entry for the new device support.

Later, if Optivity NMS is uninstalled, during the uninstall process, a list of all the
installed OIT packages is generated from the OIT database and stored on the
system. When Optivity NMS 10.3 is reinstalled, the installation program
compares the generated list with the OIT package supported by respective version
of Optivity NMS. If there are any oit packages missing, the installation process
installs those OIT packages and makes sure that all device support is provided.
Launching a device management application

You can use OIT to add application launch entries to Optivity NMS. The Optivity
NMS server contains a collection of all possible scenarios for launching
applications from any Optivity NMS client. This feature lets you launch a device
management application from an Optivity NMS client station.
Device support added in Optivity NMS 10.3 using OIT

Table 179 describes the OIT devices that are integrated into Optivity NMS 10.3.
Table 179 Device agents supported in Optivity NMS 10.3
Device and agent Filename
Contivity 600 v4.7 NMS_ces600_v470_A.oit

Contivity Branch Access v7.2 NMS_contivityba_v720_A.oit
OPTeraMetro 1200 Version 1.0.0 NMS_om1200_v100_C.oit
OPTeraMetro 1200 Version 1.1.0 NMS_om1200_v110_B.oit
OPTeraMetro 1200 Version 1.2.0 NMS_om1200_v120_A.oit
207569-F

OPTeraMetro 8000 Version 2.0.1 NMS_om8003_v201_A02.oit
NMS_om8006_v201_A02.oit
NMS_om8010_v201_A02.oit
NMS_om8010co_v201_A02.oit
Alteon 2424 v20.1 NMS-Alteon2424-v201-A.oit
Wireless LAN AP2220 Version 1.1.16 NMS_AP2220_v110.oit
WSS2250 Version 1.1.0 NMS_WSS2250_v110_A.oit
BPS 2000 v2.5 NMS_bps2k_v250_A.oit
BPS 2000 v3.0 NMS_bps2k_v300_A.oit
BayStack 380-24F v2.1.0 NMS_bs380f_v210_A.oit
BayStack 460 v2.3 NMS_bs460_v230_A.oit
BayStack 460 v3.0 NMS_bs460_v300_A.oit
BayStack 470-48T v3.0 NMS_bs470_24T_v300_A.oit
Passport 1424T Version 2.1.0 NMS_pp1424t_v210_A.oit
Passport 8100 Version 3.3.2 NMS_pp8103_v332_A.oit
NMS_pp8106_v332_A.oit
NMS_pp8110co_v332_A.oit


Contivity 1700 v4.7 NMS_ces1700_v470_B.oit
Contivity 2700 v4.7 NMS_ces2700_v470_B.oit
Wireless LAN AP2221 v1.2.0 NMS_AP2220_v120_A.oit
Wireless LAN AP2221 v1.2.1 NMS_AP2220_v121_B.oit
Passport 1000 v2.1.0 there is no OIT file for this package
Passport 1612G v1.0 NMS_pp1612g_v100_A.oit
Passport 1624G v1.0 NMS_pp1624g_v100_A.oit
Passport 1648T v1.0 NMS_pp1648t_v100_A.oit
Passport 8100 v3.3.4 NMS_pp8103_v334_A.oit
BayStack 380-24T v3.0 NMS_bs380T_v300_A.oit
BayStack 380-24F v3.0 NMS_bs380F_v300_A.oit
BayStack 420-24T v3.0 NMS_BS420_24T_v300_A.oit
207569-F

Ethernet Switching Unit 1800 v2.0 NMS_esu1800_v200_A.oit
OpteraMetro 8000 v2.1.0 NMS_om8003_v210_A.oit
NMS_om8006_v210_A.oit
NMS_om8010_v210_A.oit
NMS_om8010co_v210_A.oit
Passport 8600 v3.5oe NMS_pp8603_v350oe_A.oit
NMS_pp8606_v350oe_A.oit
NMS_pp8610_v350oe_A.oit
NMS_pp8610co_v350oe_A.oit
Troubleshooting OIT Administration Tool

results.
Table 180 Common OIT Administration Tool problems
Problem Resolution
Error message: Select a valid OIT file and/or package to install.

Invalid type • On UNIX, valid types include: an OIT file (.oit) or OIT
selected. Cannot packages (.gz, .tar) or Install file.
proceed with • On Windows, valid types include: an OIT file (.oit) or
install. OIT package (.exe) or Install.bat file.

Table 180 Common OIT Administration Tool problems (continued)
Problem Resolution
Error messages: The possible causes for these error messages are:
• An invalid IP address is specified in the FTPProxyHost
Error connecting to field in the AdminToolConf.properties file. Enter a valid
the server. FTP IP address in this field.
Server stated: [9999 • An invalid Port number is specified in the FTPProxyPort
Connection timed out] field in the AdminToolConf.properties file. Enter a valid
Port number in this field.
• The IP address specified in the FTPProxyHost field of
Error connecting to the AdminToolConf.properties file cannot be reached.
the server. FTP Make sure that the device can be reached.
Server stated: [9999 • The FTPProxyPort value is missing when the
Operation timed out] FTPProxyHost is specified in AdminToolConf.properties
file. Enter a valid port value in properties file.
Error connecting to
the server. FTP
Server stated: [9999
Connection refused]
Error connecting to
the server
Error connecting to the The FTPProxyPort value is missing when the
server FTPProxyHost is specified in AdminToolConf.properties
file. Enter a valid port value in properties file.
Error occurred while On UNIX, you must have root privilege to install the OIT
installing OIT. package. Log into system with root authority and try to
Oit Install failed. install OIT package again.
207569-F
793
Chapter 23
Managing network access with BaySecure LAN
Access
• “BaySecure LAN Access overview‚” next

• “Getting started with BaySecure LAN Access” on page 794
• “Working with BaySecure LAN Access” on page 810
• “Understanding BaySecure security modes” on page 821
• “Troubleshooting BaySecure LAN Access” on page 834
BaySecure LAN Access overview

BaySecure LAN Access is an Optivity NMS security management application
that safeguards Ethernet networks from unauthorized intrusion and eavesdropping
and supports corrective security actions.
The BaySecure application consists of client and server software. The client
software resides on the Optivity NMS Client Management station. The server
software is one of the components of the Optivity NMS Server Management
station. The client and server software can reside on the same management station
or on different management stations.
BaySecure provides the following security features:
• Eavesdrop protection
• Intrusion control
• Node access
• Autolearn

794 Chapter 23 Managing network access with BaySecure LAN Access
BaySecure offers eight security modes that define who can access the network,
their access rights and privileges, and what security actions are taken against
unauthorized users. You configure these security modes using specific settings
applied either individually or simultaneously to hardware modules, agents, or the
Optivity NMS management station. See “BaySecure security components” on
page 794.
Getting started with BaySecure LAN Access

See the following sections for information about getting started with BaySecure
LAN Access:
• “BaySecure security components‚” next

• “Hardware functionality” on page 795
• “Agent functionality” on page 795
• “Software functionality” on page 796
• “BaySecure security features” on page 796
• “Access permissions for BaySecure” on page 801
• “Starting BaySecure LAN Access” on page 802
• “BaySecure LAN Access window” on page 804
BaySecure security components
BaySecure security requires the following components:
• Host module hardware consisting of System 5000, Distributed 5000, or

BayStack hubs and respective modules
• Agent software residing on an installed network management module
• Optivity network management software residing on the network management
station.
207569-F
Chapter 23 Managing network access with BaySecure LAN Access 795
Hardware functionality
BaySecure-supported host modules provide the following hardware-based

security functions:
• Eavesdrop protection–Prevents end stations from receiving confidential data

that is not explicitly addressed to them.
For more information, see “Understanding eavesdrop protection” on
page 798.
• Intrusion control–Ensures that only authorized users can access data on the
network.
For more information, see “Understanding intrusion control” on page 796.
• Autolearn–Simplifies the assignment and administration of authorized source
addresses.
For more information, see “Understanding autolearn” on page 799.
(For information about configuring supported hardware for security, see your
hardware configuration documentation.)
Agent functionality
BaySecure LAN Access agents are supported in the following two SNMP Agent
versions:
• Advanced SNMP agent–Provides powerful management capabilities, such as

thresholds, node security, dynamic mapping of network configuration, and
support for four RMON groups.
• Advanced Analyzer SNMP agent–In addition to the above, this agent also
contains full support for RMON groups and exclusive SuperRMON support.
BaySecure LAN Access agents allow Software-based intrusion control, which

provides multiple MAC addresses filtering based on Allowed nodes or Allowed
nodes plus (both Allowed Nodes and Not-Allowed Nodes) configuration tables.

Software functionality
BaySecure LAN Access in Optivity NMS provides a two-tiered approach to

enabling security:
• You first set the overall security mode for the associated segments, boards, or
ports.
• Then you set the Allowed/Not-Allowed Nodes entries for the secured
segment, board, or port.
For more information about the security process, see “BaySecure security
process” on page 810. For more information about the security modes, see
“Understanding BaySecure security modes” on page 821. For more information
about starting BaySecure, see “Starting BaySecure LAN Access” on page 802.
BaySecure security features
The following sections describe BaySecure security features:
• “Understanding intrusion control‚” next

• “Understanding eavesdrop protection” on page 798
• “Understanding autolearn” on page 799
Understanding intrusion control
Intrusion control, also known as “source address filtering,” ensures that only
authorized users can access data on the network.
On the path from the port to the network, intrusion control compares the source
MAC address of the incoming data terminal equipment (DTE) station frame to the
authorized source address of the host module port. If the source MAC address
does not match, either the frame transmission can be jammed or the port can be
partitioned from the Ethernet segments to which it is connected.
You can select any of the following actions to be taken when an unauthorized
station attempts to connect to the network using a port or slot secured with
intrusion control:
• No action is taken.
207569-F
• Jam—The port is immediately, but temporarily, jammed under control of the

host module which effectively scrambles the frame’s data field contents.
• Jam with warning—The violation is flagged for the network management
module (NMM) and appropriate action is taken under network management
control.
• Partition—The port is permanently partitioned in both directions.
Unpartitioning the port requires network manager or software-based
intervention.
• Partition with warning—The violation is flagged by a network management
trap message.
Table 181 summarizes the three types of intrusion control supported by

BaySecure.
Table 181 Types of intrusion control supported by BaySecure
Security type Security mode Hardware support
Hardware-based • Only1Min A subset of:

• Only1Max • System 5000
• Distributed 5000 modules
• BayStack 10BASE-T hubs
Software-based • ListMin Requires Advanced or Advanced Analyzer
• ListMax agents supported by:
• System 5000
• Distributed 5000 host modules
• BayStack 10BASE-T hubs
• BayStack Switches 302/303
Hardware- and • Checked1Min Supported by:
Software-based • Checked1Max • System 5000
(advanced intrusion
control) • Distributed 5000
• BayStack 10BASE-T host modules/units
• BayStack Switches 302/303
You configure intrusion control in BaySecure LAN Access using the Security
Type options in the Configuration dialog box. For more information, see
“Configuring security” on page 818.

Understanding eavesdrop protection
Eavesdrop protection, also know as “destination address filtering,” prevents an

end station from receiving confidential data that is not explicitly addressed to that
station. It ensures that specified authorized stations only receive addressed
confidential data.
BaySecure eavesdrop protection relies on the association of a single authorized

source address (ASA) for each port in the host module. The host module uses the
ASA to filter packets transmitted from the module to the end station.
Eavesdrop protection works after you configure the BaySecure LAN Access
security options and the host module shifts operation from the broadcast mode of
standard 10BASE-T Ethernet transmission to point-to-point secured 10BASE-T
transmission. (For information about configuring supported hardware for security,
see your hardware configuration documentation.)
Eavesdrop protection in BaySecure LAN Access is hardware-based, using

hardware chip sets and firmware. If eavesdrop protection is enabled through
Optivity NMS, the software agent instructs the hardware to begin filtering frames
originating from the network and going to an end station.
Table 182 summarizes the type of eavesdrop protection supported by BaySecure

LAN Access.
Table 182 Type of eavesdrop protection supported by BaySecure
Security type Security mode Hardware support
Hardware-based only • Sequential • System 5000

• ListMax • Distributed 5000 hubs and
• Only1Max • Specific 10Base-T hubs
• Checked1Max
You configure eavesdrop protection in BaySecure LAN Access using the Security
Options in the Configuration dialog box. For more information, see “Configuring
security” on page 818.
207569-F
Understanding autolearn
Autolearn, also known as “adaptive address learning,” simplifies the assignment

and administration of authorized source addresses.
BaySecure LAN Access supports two types of autolearn:
• One-shot autolearn–The host module automatically captures the MAC source

address of the first frame to be received at the port. This reduces configuration
requirements.
• Continuous autolearn–The host module automatically captures the MAC
source address for all incoming frames continuously. Continuous autolearn is
unique in its ability to provide eavesdrop protection.
You configure autolearn in BaySecure LAN Access using the Security >
Configuration command and the Address Learn Mode options in the
Configuration dialog box. For more information about configuring autolearn, see
“Configuring security” on page 818.
Understanding node access
Node access defines which nodes have access to the network.
There are two ways to specify network access to a node:
• Allowed nodes
• Allowed nodes plus
You configure node access in BaySecure LAN Access using the Node Access
dialog box. For more information about configuring node access, see “Creating a
node access list” on page 814.
Allowed nodes
Allowed Nodes is a list of approved users, based on their MAC address, whom
you want to allow to access the network. Allowed nodes is a feature of
Software-based intrusion control and differs from hardware-based intrusion
control in two ways:
• Software-based agents can support multiple MAC addresses.

• Software-based agents cannot provide real-time security; however, they do

prevent intrusion with a limited delay.
Software-based intrusion control agents perform a corrective security action based

on a specifically configured intrusion control security action definition.
Allowed nodes support through the NMM configuration files are supported by
System 5000, Distributed 5000, and Advanced BayStack modules running agents
version 1.5.x and above.
You configure node access in BaySecure LAN Access using the Node Access
dialog box. For more information about configuring node access, see “Creating a
node access list” on page 814.
Allowed nodes plus
Allowed nodes plus consists of a list of allowed nodes and not-allowed nodes.
Allowed nodes is a list of users who, based on their MAC address, are authorized
to access the network. Not-allowed nodes is a list of users who, based on their
MAC address, are denied access to the network. You can use allowed nodes and
Not-allowed Nodes entries together for multiple segments in the same chassis, as
well as to limit access on a specific segment.
Allowed Nodes Plus implicitly denies all stations when you enable any level of
security on a segment, board, or port basis (whether or not the security mode is
being applied to a BaySecure LAN Access-capable module).
Allowed nodes plus is an agent feature supported by System 5000, Distributed

5000, and BayStack NMMs running agent software version 1.5.x or higher.
You configure node access in BaySecure LAN Access using the Security > Node
Access command and the Node Access dialog box. See “Creating a node access
list” on page 814. for more information.
207569-F
Access permissions for BaySecure
Your access to BaySecure LAN Access depends on the Access Control permission
tokens listed below:
• Administrator—An Optivity NMS user account with administrator privileges

lets you perform both read and write (set) operations. For example, you can
view device security status and configure security status. You can save
security status to a device NVRAM. In Optivity NMS access control
administration, with access control enabled, you should select the
BAY_SECURE token with read/write permissions for a user.
• User—An Optivity NMS user account with user privileges lets you perform
only read operations. For example, you can only view security status. You
cannot configure security status. You also cannot save device security status
to a device NVRAM. In Optivity NMS Access Control Administration, with
access control enabled, you should select the BAY_SECURE token with
read-only permissions for a user.
• No Access—You cannot start BaySecure. A message tells you that you are not
authorized to use the system. In Access Control Administration, with access
control enabled, you do not specify a BAY_SECURE token for a user.
Note: For more detailed information about setting user privileges in

Optivity NMS, refer to the Access Control online Help system.
An Optivity NMS administrator sets user access to BaySecure by configuring

access to the BaySecure tokens in the Access Control Administration window. For
more information about using Access Control to set permission tokens for
BaySecure, see Chapter 2, “Specifying access to Optivity NMS applications with
Access Control Administration,” on page 75.

Starting BaySecure LAN Access
You can only start BaySecure LAN Access at a Windows or UNIX command line.
When you start BaySecure LAN Access, it checks to see that you have a valid user
name:
• On the Optivity NMS server that you specify.

• In Optivity NMS Access Control.
Note: You can run BaySecure LAN Access on one device at a time.
However, you can also:
• Start BaySecure LAN Access on the same device twice.
• Run several instances of BaySecure LAN Access at one time.
To start BaySecure LAN Access:

window.
2 Change to the directory where BaySecure LAN Access start files are located.
• In a Windows environment, change to the \Optivity\LNMS\bin directory.
• In a UNIX environment, change to the opt/optivity/lnms/lnms/bin
directory.
Note: On some systems, the path to your start files directory may be
different than the default paths. If you have customized your Optivity
NMS installation you should use your specific path to those directories.
207569-F

baysec [optional commands]
BaySecure LAN Access provides optional commands to let you customize

how BaySecure LAN Access starts.
Note: You must keep the Windows MS-DOS Command Prompt

window running while BaySecure is running. If you close the MS-DOS
Command Prompt window, BaySecure closes.
You can run BaySecure on one device at a time. To manage another
device, start Command Prompt again and start BaySecure.
If you start BaySecure without specifying an IP address, the Specify
Properties dialog box opens for you to specify an IP address.
Table 183 describes the optional commands for the baysec start file.
Table 183 BaySecure LAN Access baysec start file options
Option Usage
-I Specifies the IP address of the device you want to start BaySecure LAN
Access against.
-U Specifies the user name.
-H Specifies the BaySecure LAN Access server name. The name you enter is
displayed in the BaySecure LAN Access login dialog box.
-R Specifies the read community name.
-W Specifies the write community name.
-T Specifies the SNMP time out value in seconds.
For example:
baysec -I 10.222.111.18 -U jworldly
The Connect to Optivity Server dialog box (Figure 315) opens.

Figure 315 BaySecure Connect to Optivity Server dialog box
4 Type the following:

• A valid user name
• A password
• The Optivity server IP address or host name
5 Click OK.
The BaySecure LAN Access window opens. See Figure 316 on page 805.
BaySecure LAN Access window
The BaySecure LAN Access window opens when you run BaySecure LAN
Access on a modular device.
The BaySecure LAN Access window has four parts as shown in Figure 316. To
read more detailed information about the BaySecure LAN Access window, refer
to Table 184.
207569-F
Figure 316 Parts of the BaySecure LAN Access window
Menu bar
Toolbar
Device information
table
Status bar
Table 184 describes the BaySecure LAN Access window parts.
Table 184 BaySecure LAN Access window parts
Part Description
Menu bar The menu bar contains the commands that you can perform in
BaySecure LAN Access to provide security for your network. For more
information, see “BaySecure menu bar” on page 806.
Toolbar The toolbar provides quick access to commonly-used BaySecure LAN
Access commands. For more information, see “BaySecure toolbar” on
page 808.
Device The device information table shows basic information about the
information connected device upon which BaySecure LAN Access is running,
table including hardware and security configuration. For more information, see
“Device information table” on page 809.
Status bar Displays status information, including the selected command description.

BaySecure menu bar
Table 185 lists the available menu bar commands that allow you to configure
BaySecure security for the managed device.
Table 185 BaySecure menu bar commands
Toolbar
button
File Print Opens the Print dialog box and prints the security
information in the BaySecure window to your
default printer.
Exit Closes the BaySecure LAN Access window.
View Refresh Displays the latest information for a managed
device in the BaySecure LAN Access window.
For more information, see “Viewing the latest
information in the BaySecure window” on
page 811.
Device Opens the Device Info dialog box that shows
Properties basic information about the connected device,
including: chassis location, description, contact,
version, serial number, and agent version.
For more information, see “Viewing device
properties” on page 811.
Look and Feel Displays a submenu (Metal, CDE/Motif,
Windows) that lets you change the look of the
BaySecure window. The default option is
Windows.
207569-F
Table 185 BaySecure menu bar commands (continued)
Toolbar
button
Options Save to Opens the dialog box where you confirm whether
NVRAM or not you want BaySecure to save the current
security configuration to the managed device
nonvolatile RAM (NVRAM).
For more information, see “Saving security
configuration changes to device NVRAM” on
page 811.
Set SNMP Opens the Set SNMP Parameters dialog box that
Parameters lets you do the following for the connected
device:
• View the IP Address or host name.
• Change the read and read/write community
strings.
• Change the SNMP timeout in seconds.
Changing community strings lets you control
network access to a device.
For more information, see “Setting device SNMP
parameters” on page 812
Security Status Opens the Status dialog box that displays the
current security configuration for the selected
board or unit, including the security type, address
learn mode, software and hardware action.
For more information, see “Viewing device
security status” on page 814
Node access Opens the Node Access dialog box that displays
the nodes that are allowed and not allowed for
the connected device. The Node Access dialog
box also lets you create a node access list.
For more information, see “Creating a node
access list” on page 814.
Configuration Opens the Configuration dialog box that displays
the current security status for the connected
device. The Configuration dialog box also lets
you add security for the connected device,
including security type, address learn mode,
software and hardware action.
For more information, see “Configuring security”
on page 818.
Enable/ Enables or disables a port.
Disable OFF
Ports

Table 185 BaySecure menu bar commands (continued)
Toolbar
button
Help BaySecure Opens the BaySecure LAN Access online Help
LAN Access system.
Help
Using Help Opens basic information about using Help.
About Opens the About BaySecure dialog box that
BaySecure shows the software version and copyright
LAN Access information.
BaySecure toolbar
The BaySecure toolbar provides quick access to commonly-used BaySecure LAN

Access commands.
Table 186 describes the toolbar buttons.
Table 186 BaySecure toolbar buttons
Refresh Displays the latest security information for a connected device

in the BaySecure window. Clicking Refresh is the same as
choosing View > Refresh.
For more information, see “Viewing the latest information in
the BaySecure window” on page 811.
Device Opens the Device Info dialog box that displays information
Properties about the connected device, including: chassis location,
description, contact, version, serial number, and agent
version. This information indicates whether or not you can
secure a device using BaySecure.
Clicking Device Properties is the same as choosing View >
Device Properties.
For more information, see “Viewing device properties” on
page 811.
Print Prints the security information in the BaySecure window to
your default printer. Clicking Print is the same as choosing File
> Print.
207569-F
Table 186 BaySecure toolbar buttons (continued)
Save to Opens a message box where you determine whether or not

NVRAM you want BaySecure to save the current security configuration
for the connected device to its nonvolatile RAM (NVRAM).
Clicking Save to NVRAM is the same as choosing Options >
Save to NVRAM.
For more information, see “Saving security configuration
changes to device NVRAM” on page 811.
Help Displays the BaySecure LAN Access online Help system.
Clicking Help is the same as choosing Help > BaySecure LAN
Access Help.
Device information table
The Device information table in the BaySecure LAN Access window shows, in
tabular form, the unit or board number, board type, the number of ports, and the
current security configuration.
The device information table in this example depicts a modular device.
To select a board or unit from the device information table, click that row. Then
you can configure BaySecure security.
Note: If you are running BaySecure on a stackable device, the table

shows the unit number. The board number value is 0 (zero).

Working with BaySecure LAN Access

Information in this section is organized as follows:
• “BaySecure security process‚” next

• “Viewing the latest information in the BaySecure window” on page 811
• “Viewing device properties” on page 811
• “Saving security configuration changes to device NVRAM” on page 811
• “Setting device SNMP parameters” on page 812
• “Viewing device security status” on page 814
• “Creating a node access list” on page 814
• “Configuring security” on page 818
BaySecure security process
This procedure provides an overview of how to configure security using

BaySecure LAN Access.
To configure security in BaySecure LAN Access:
1 Start BaySecure on a BaySecure-supported device.

See “BaySecure security components” on page 794.
2 Set the SNMP parameters for the device.

See “Setting device SNMP parameters” on page 812.
3 Configure security for the device, specifying the security type, address learn
mode, software action, and hardware action.
See “Configuring security” on page 818.
4 Create the node access for the device.

See “Creating a node access list” on page 814.
207569-F
5 Save the security configuration to the device NVRAM if you want it to be

permanent.
See “Saving security configuration changes to device NVRAM” on page 811.
Note: If you do not save your security settings to NVRAM, they are in
effect as long as you do not reboot the device.
6 View the security status for the device.

From the BaySecure menu bar, choose Security > Status.
Viewing the latest information in the BaySecure window
To ensure that the latest information for a device appears in the BaySecure LAN
Access window:
From the BaySecure menu bar, choose View > Refresh.
Viewing device properties
The Device properties allow you to, at a glance, view basic information about the
managed device.
To view the device properties:
From the BaySecure menu bar, choose View > Device Properties.
The Device Info dialog box opens showing read-only information that has
been set on the managed device.
Saving security configuration changes to device NVRAM
You can save BaySecure security configuration changes to the managed device
nonvolatile random access memory (NVRAM). When you save security
configuration changes to device NVRAM, the changes are stored even during loss
of power. If you do not store the information to device NVRAM, the security
changes are effective until you reboot the managed device.

Save security configuration changes to a device NVRAM when you:
• Change any security setting

• Add, remove, or delete any security configuration
• Modify the node access list
To store changes in the device NVRAM:
1 Use BaySecure to configure security on the device.

See “Configuring security” on page 818 and “Creating a node access list” on
page 814.
2 From the BaySecure menu bar, choose Options > Save to NVRAM.
A message box opens where you confirm whether or not you want to save the
current security configuration to the managed device NVRAM.
Setting device SNMP parameters
You can control access to an SNMP network using passwords called SNMP
community strings. You can change the default community strings on the device
and on the management station.
There are two types of SNMP community strings:
• Read
• Read/write
The read community string controls which management stations can read the
management information base (MIB) of a particular device. The default read
community string is “public.”
The read/write community string controls which management stations can have
full access (read and write access) to the MIB of a particular device. The default
read/write community string is “private.”
207569-F
To set the SNMP parameters for a device:
1 From the BaySecure menu bar, choose Options > Set SNMP Parameters.
The Set SNMP Parameters dialog box (Figure 317) opens. The IP address or
device name of the managed device automatically appears in the IP Address/
Name field.
Figure 317 BaySecure Set SNMP Parameters dialog box
2 Type a read community string for the device.

3 Type a read/write community string.
4 (Optional) Type an SNMP time period in seconds within which you want the
device to time out if BaySecure does not connect.
5 Click OK.

Viewing device security status
To view the current security configuration for the selected board or unit:
1 In the BaySecure LAN Access window, select a board or a unit.

2 From the BaySecure menu bar, choose Security > Status.
The Status dialog box (Figure 318) opens showing a tabular view of the
current security configuration for the selected board or unit, including the
security type, address learn mode, the software action, the hardware action
and the security status.
Figure 318 BaySecure Status dialog box
Creating a node access list

Creating a node access list lets you determine which nodes have access to the
network. You can create an allowed node list and a not-allowed nodes list.
To create a node access list:
1 In the BaySecure LAN Access window, select the board or unit for which you
want to create node access.
207569-F
2 From the BaySecure menu bar, choose Security > Node Access.
The Node Access dialog box opens (Figure 319), retrieving the latest node
access information from the network.
Figure 319 BaySecure Node Access dialog box
3 Click Add.
The BaySecure Add Node Access dialog box (Figure 320) opens.

Figure 320 BaySecure Add Node Access dialog box
4 Select the Entry Type from the list.

5 Select the Segment Type from the list.
6 Select the Access Type from the list.
This list lets you determine whether the node is allowed or not allowed to
access the network.
7 Type the segment number, board number, port number, and the station
address, or click User List.
User List opens the Show Node dialog box that lists all of the nodes that have
access to the board or unit (Figure 321).
207569-F
Figure 321 BaySecure Show Nodes dialog box
8 Select the Node that you want and click Use.

The board number, port number, and the station address for that node is
automatically added to the Add Node Access dialog box.
9 Click OK.
The node is added to the list in the Node Access dialog box.
10 Click Close.
11 (Optional) Save the new node access information to the device NVRAM.
From the BaySecure menu bar, choose Options > Save to NVRAM.

Configuring security
BaySecure LAN Access lets you add, modify, or delete a security configuration.
To create a security configuration:
1 In the BaySecure LAN Access window, select the board or unit for which you
want to configure security.
2 From the BaySecure menu bar, choose Security > Configuration.
The Configuration dialog box opens (Figure 322) displaying the current
BaySecure security configuration for the selected board or unit.
Figure 322 BaySecure Configuration dialog box
3 Change the current security configuration, or add a new one.

• To change the configuration, click the board or unit in the table. The
Modify and Delete buttons are enabled. If you click Modify, the Modify
Configuration dialog box opens (Figure 323) displaying the current
BaySecure security options. If you click Delete, a dialog box opens where
you confirm whether or not you want to delete the BaySecure security
configuration.
207569-F
Figure 323 BaySecure Modify Configuration dialog box
• To add a BaySecure security configuration, you do not have to select a

board or unit. Click Add. The BaySecure Add Configuration dialog box
opens (Figure 324) providing the BaySecure security options from which
you can choose.

Figure 324 BaySecure Add Configuration dialog box
4 Click Refresh to view your latest security settings.

5 Click Close.
6 (Optional) Save the security configuration to the Device NVRAM.
From the BaySecure menu bar, choose Options > Save to NVRAM.
207569-F
Understanding BaySecure security modes

This section describes the BaySecure LAN Access security modes. For more
information, see “Understanding BaySecure security modes‚” next. Table 187
describes the eight BaySecure security modes.
Table 187 BaySecure security modes
NNM
Security mode Description
mode
1 Disabled Security disabled

2 Sequential Eavesdrop protection enabled
3 ListMin Software-based intrusion control
4 ListMax Software-based intrusion and eavesdrop protection
5 Only1Min Hardware-based intrusion control
6 Only1Max Hardware-based Intrusion and eavesdrop protection
7 Checked1Min Hardware- and software-based intrusion control
(advanced intrusion control)
8 Checked1Max Hardware- and software-based intrusion control With
eavesdrop protection
(advanced Intrusion and eavesdrop protection)
The BaySecure security modes allow you to implement a network security policy
that does either or both:
• Prevents unauthorized users from accessing network data not addressed

directly to their node or station (eavesdrop protection)
• Deters unauthorized hardware transmissions to the network (intrusion control)
See “Configuring security” on page 818 for more information.

Disabled security mode
(Security Disabled) The disabled mode disables all security features. If a

segment, board, or port is configured with this security setting, any user can
access, send, and/or receive data through any available port.
Use this security mode only to provide unrestricted network access or if data
traversing the network is not confidential.
Table 188 describes the security actions taken against authorized and
unauthorized users.
Table 188 Disabled mode security actions
User type Action
Authorized Nothing happens to any user. Normal 10BASE-T auto-partition rules and
all other user-defined thresholds apply.
Unauthorized Nothing happens to any unauthorized user. Normal 10BASE-T
auto-partition rules apply.
Sequential security mode
(Eavesdrop protection enabled) The sequential mode permits anyone to access a

port, one user at a time. The user receives traffic destined for that specific MAC
address, as well as any broadcast and multicast frames.
The sequential mode is a hardware-only option and does not provide notification
of any intruder violations.
Use this security mode if you want unrestricted user access to a port, yet want to
ensure that each user only receives data addressed to that authorized source
address (ASA), as well as broadcast and multicast frames.
207569-F
unauthorized users.
Table 189 Sequential mode security actions
User type Action
Authorized Minor filtering occurs when an approved user accesses the port. Frames
received are sent to their individual MAC address, as are broadcast and
multicast frames. Remaining traffic is translated as “jam” if the destination
address is not the current MAC address used by the authorized user.
Unauthorized Traffic at this port is either specifically destined to this current MAC
address or is an overhead broadcast and multicast frame. A network
analyzer or RMON probe attached at this port reveals only details of the
current session established by the last connected MAC address or
overhead broadcast and multicast frames.
ListMin security mode
(Software-based intrusion control) The ListMin mode permits any user

identified from an approved list to access the port. Approved users can access this
port to send and receive data on that segment.
The ListMin is an agent-only option, with software-based intrusion control

enabled. This option includes no eavesdrop protection; all users on the allowed
nodes list are permitted access to all data.
Use this security mode when you want only clearly identified individuals or
functional entities who match the authorized source address (ASA) to access the
network, but you do not care what data they have access to once they are on the
network.

unauthorized users.
Table 190 ListMin mode security actions
User type Action
Authorized Nothing happens to an approved user if their MAC address is either on

the allowed nodes list, or not on the not-allowed nodes list. Normal
10BASE-T rules and all other user-defined thresholds apply.
Unauthorized Users whose MAC address either does not match an entry on an allowed
nodes list or whose MAC address does match an entry in the not-allowed
nodes list will have one of four agent-based actions taken against them:
• No action taken.
• The NMM agent sends a warning (trap) to the devices in its
trap-receiver table, if a violation to the allowed/not-allowed nodes list
occurs.
• The NMM partitions the port if a violation to the allowed/not-allowed
nodes list occurs.
• The NMM agent simultaneously sends a warning (trap) to the devices
in its trap-receiver table and partitions the port if a violation to the
allowed/not-allowed nodes list occurs.
ListMax security mode
(Software-based intrusion control with eavesdrop protection) The ListMax

mode permits any user identified from an approved list to access the port.
Approved users can access this port to send data on that segment. However, each
user receives only traffic destined for that specific MAC address, as well as all
broadcast and multicast frames.
The ListMax mode is a hardware- and software-based mode, with hardware-based

eavesdrop protection and software-based intrusion control enabled.
Use this mode when you want only clearly identified individuals or functional
entities who match the authorized source address (ASA) to have access to the
network, want to provide them with unrestricted access privileges to send data
over the network, and yet want to restrict their access to certain data only.
207569-F
unauthorized users.
Table 191 ListMax mode security actions
User type Action
Authorized Minor filtering occurs if an approved user’s MAC address is either on the
allowed nodes list, or not on the not-allowed Nodes list. Frames received
are sent to their individual MAC address, as are broadcast and multicast
frames. Users can access resources and data related to their specific
jobs, but remaining traffic will be translated as “jam” if the destination
address is not the current MAC address used by the authorized user.
Unauthorized Users who either do not match an entry on an allowed nodes list or who
do match an entry in the not-allowed nodes list have one of four
agent-based actions taken against them:
• No action taken.
• The NMM agent sends a warning (trap) to the devices in its
trap-receiver table, if a violation to the allowed/not-allowed nodes list
occurs.
• The NMM partitions the port if a violation to the allowed/not-allowed
nodes list occurs.
• The NMM agent simultaneously sends a warning (trap) to the devices
in its trap-receiver table and partitions the port if a violation to the
allowed/not-allowed nodes list occurs.
Only1Min security mode
(Hardware-based intrusion control) The Only1Min mode permits only one user
to access the port. This user may be determined individually or selected on a
connectivity first-come-first-served basis (also known as one-shot autolearn). The
approved user can send and receive anything on that segment.
The Only1Min mode is a hardware and agent mode, with hardware-handled

violations. eavesdrop protection is disabled; intrusion control is enabled.
entities to have access to the network through a particular connection point and
want to provide them with unrestricted access privileges to send and receive data
over the network, from this connection point.

unauthorized users.
Table 192 Only1Min mode security actions
User type Action
Authorized Nothing happens to an approved user if the first connection to that port
was approved. If approved, normal 10BASE-T rules and all other
user-defined thresholds apply.
Unauthorized Users who are either not the first to access a port or not specifically listed
as an approved user have the following hardware and/or agent software
actions taken against them:
• Violators immediately have their network transmissions scrambled (in
the form of a jam) as they attempt to send data to the network. Their
connectivity is not terminated, but they are unable to connect to any
networked device since frames transmitted are meaningless strings of
ones and zeros.
networked device because frames transmitted are meaningless
strings of ones and zeros. In addition, the NMM agent sends a
warning (that is, a trap) to the devices in its trap-receiver table
notifying the network administrator of the violation and of the violator’s
MAC address.
• Violators are immediately partitioned by the host module.
• This security mode requires user intervention to reenable this port for
access by another authorized user.
• Violators are immediately partitioned by the host module, and the
NMM agent sends a warning (that is, a trap) to the devices in its
trap-receiver table, notifying the network administrator of the violation
and of the violator’s MAC address. (This security mode requires user
intervention to reenable this port for access by another authorized
user.)
Only1Max security mode
(Hardware- and software-based intrusion control/advanced intrusion

Control) The Only1Max mode permits only one user to access the port. This user
may be determined individually or selected on a connectivity
first-come-first-served basis (also known as one-shot autolearn). The approved
user receives only traffic destined for that port, as well as all broadcast and
multicast frames.
207569-F
The Only1Max option is a hardware and agent mode, with hardware-handled

violations. Both eavesdrop protection and intrusion control are enabled.
entities to:
• Have access to the network through a particular connection point.

• Provide users with unrestricted access privileges to send data over the
network from this connection point, yet want to restrict their access to certain
data only.
Note: The Only1Max option is the most secure setting of the BaySecure
security modes.

unauthorized users.
Table 193 Only1Max mode security actions
User type Action
Authorized An approved user’s data is filtered if the first connection to attach to that
port was approved. Frames received are sent to their individual MAC
address, as are broadcast and multicast frames. Users can access
resources and data related to their specific jobs, but remaining traffic will
be translated as “jam” if the destination address is not the current MAC
address used by the authorized user.
as an approved user have the following hardware and/or agent software
actions taken against them:
strings of ones and zeros.
strings of ones and zeros. In addition, the NMM agent sends a
warning (that is, a trap) to the devices in its trap-receiver table
notifying the network administrator of the violation and of the violator’s
MAC address.
• This security mode requires user intervention to reenable this port for
access by another authorized user.
and of the violator’s MAC address.
This security mode requires user intervention to reenable this port for access by
another authorized user.
207569-F
Checked1Min security mode
(Hardware- and software-based intrusion control)
(Advanced intrusion control) The Checked1Min mode permits only one user to
access the port. This user may be determined individually or selected on a
connectivity first-come-first-served basis (also known as one-shot autolearn) and
is double-checked against an “approved” or “not-approved” criteria list. The
approved user can send and receive data on that segment.
The Checked1Min mode is a hardware and agent mode, with agent-assisted

violation control. Intrusion control is enabled; eavesdrop protection is disabled.
Use this mode when you want to restrict port access to one user, selected from an
approved user list, yet do not care what data they might access once on the
network.
Note: An approved user who connects after a previously approved user

experiences a minor outage before service is restored because a newly
attached user changes the last source address (LSA) stored in the host
module firmware. If the new LSA is different from authorized source
address (ASA), the new user is viewed as an intruder. This situation
causes an immediate partition at the hardware level, but a double-check
of the new address is then compared to the allowed/not-allowed nodes
list maintained in the NMM agent. If the new user is a member of this
list, the agent unpartitions the port and updates the ASA on the host
module to the newly connected user. Therefore, the time it takes a
supplementary approved user to connect to the network is the time
necessary for the agent to check this new address against its list of
approved users. This procedure is normal for initial and subsequent
approved users.

If the most recent LSA is an unapproved user, the port cannot automatically
unpartitioned even if an approved user subsequently attaches to the port. The port
must be manually unpartitioned after a true violator is detected because the
unapproved user’s LSA is both partitioned and captured when it is compared to
the ASA, thereby blocking further communication with the network. The
partitioned and captured LSA, because it cannot communicate with the network,
cannot be updated or compared to the ASA to determine if the new user is either
authorized or unauthorized.
Because certain violations cause permanent partitioning of ports, an alternate

procedure to manual user intervention is to configure the s5time-partition
parameter in the BaySecure portion of the NMM configuration file. This feature
allows a timed unpartition of the port at user-defined intervals. After the port is
unpartitioned, if a subsequent violation occurs, a normal violation procedure is
begun. You set this option only through the NMM configuration file. You cannot
set it using standard SNMP set commands but is maintained in nonvolatile RAM
(NVRAM) upon reset or restart.
207569-F
unauthorized users.
Table 194 Checked1Min mode security actions
User type Action
Authorized Nothing happens to an approved user if the user is the first connection to
that port, or if the MAC address is recognized as the specific user
approved for that port AND meets the allowed/not allowed criteria. If
approved, normal 10BASE-T rules and all other user-defined thresholds
apply.
as an approved user are double-checked against both the allowed nodes
and not-allowed nodes lists. Unauthorized users have the following
hardware and/or agent software actions taken against them:
• This security mode requires administrator intervention to reenable the
port for authorized user access subsequent to access by an
unauthorized user.
trap-receiver table, notifying the network administrator of the violation,
and the violator’s MAC address.
unauthorized user.
• Violators are immediately partitioned by the host module. If the user is
listed in the allowed nodes list, or not listed in the not-allowed nodes
list, the port “autoheals” and unpartitions itself. (This option eliminates
the need for administrator intervention to reenable the port for
authorized user access subsequent to access by an unauthorized
user.)
Checked1Max security mode

(Hardware- and software-based intrusion control with eavesdrop protection)
(Advanced intrusion and eavesdrop protection) The Checked1Max mode

permits only one user to access the port. This user may be determined individually
or selected on a connectivity first-come-first-served basis and is double-checked
against an “approved” or “not-approved” criteria list. Approved users receive only
traffic destined for them, as well as all broadcast and multicast frames.

The Checked1Max mode is a hardware and agent mode, with hardware-handled

violations with agent assist. Both eavesdrop protection and intrusion control are
enabled.
Use this mode when you want to restrict port access to one user at a time, selected
from an approved user list, and want to restrict the data the user might access once
on the network.
Note: As with Mode 7: Checked1Min, an approved user who connects

after a previously approved user experiences a minor outage before
service is restored.
If the most recent LSA is an unapproved user, the port cannot automatically
unpartition even if an approved user subsequently attaches to the port. The port
must be manually unpartitioned after a true violator is detected because the
unapproved user’s LSA is both partitioned and captured when it is compared to
the ASA, thereby blocking further communication with the network. The
partitioned and captured LSA, because it cannot communicate with the network,
cannot be updated or compared to the ASA to determine if the new user is either
authorized or unauthorized.
The Checked1Max mode can also cause permanent port partitioning. Configure
the s5time-partition parameter in the BaySecure section of the configuration file.
This parameter allows a timed unpartition of the port at user-defined intervals.
After the port is unpartitioned, if a subsequent violation occurs, a normal violation
procedure is executed. You set the s5time parameter only through the NMM
configuration file. You cannot set it using standard SNMP set commands.
207569-F
unauthorized users.
Table 195 Checked1Max mode security actions
User type Action
Authorized There is minor filtering if the user is the first connection to that port, or if
the MAC address is recognized as the specific user approved for that port
AND meets the allowed/not allowed criteria. Frames received are sent to
their individual MAC address, as are broadcast and multicast frames.
Users can access resources and data related to their specific jobs, but
remaining traffic will be translated as “jam” if the destination address is
not the current MAC address used by the authorized user.
as an approved user are double-checked against both the allowed nodes
and not-allowed Nodes lists. Unauthorized users have the following
hardware and/or agent software actions taken against them:
unauthorized user.
and of the violator’s MAC address.
• This security mode eliminates the need for administrator intervention
to reenable the port for authorized user access subsequent to access
by an unauthorized user.
• Violators are immediately partitioned by the host module. If the user is
listed in the allowed nodes list, or not listed in the not-allowed nodes
list, the port “autoheals” and unpartitions itself.
This option eliminates the need for administrator intervention to reenable the port
for authorized user access subsequent to access by an authorized user.

Troubleshooting BaySecure LAN Access

This section provides information about troubleshooting BaySecure.
BaySecure operational note

The following errors may occur when you use BaySecure to configure security on
a device that does not have the correct agent version running. If one of these
events occurs, check the agent version on the device.
• Application Error (Dr. Watson error message).
• BaySecure disconnected from the server.
• BaySecure unsupported device.
207569-F
835
Appendix A
Using discovery command line utilities
This appendix describes two topology discovery command line utilities that are
included in Optivity NMS.
The following sections describe the two command line utilities. You can use these
utilities to discover devices and links on your network and add them to the
Optivity topology database:
• “disdevice‚” next
• “dislink” on page 837
You can use these utilities to discover single devices or links on single devices, or
multiple devices and links. You can also use these commands to do a full
discovery on portions of the network, and also debug topology issues.
One application of disdevice or dislink is when you have added a single new
device to the network. Instead of using the full suite of Optivity NMS topology
discovery tools to rediscover the entire network, you can just use disdevice or
dislink to discover only the new device and its links to the network.
The disdevice and dislink utilities are located on the Optivity NMS server, in the
following directory:
/opt/lnms/bin/
Note: The disdevice and dislink commands must be executed on the

Optivity NMS server. They will not work on an Optivity client
workstation.

836 Using discovery command line utilities
disdevice
The disdevice utility discovers either a single device, or multiple devices listed in
a file, and adds them to the Optivity database. It automatically assigns the
device(s) to the correct subnets (if any) in the database. If there is no subnet
corresponding to the device in the database the device is still accessible through
the resources folders in InfoCenter.
The syntax for the disdevice command is as follows:
disdevice -i <ipAddress>|-f <ipAddressFilename> [-d <debug

level>] [-l <log level>]
Where the parameters are as described in Table 196:
Table 196 disdevice parameters
-i <ipAddress> Specifies the IP address of a single device to be discovered.

-f <ipAddressFilename> Specifies the name of an ascii text file containing a list of IP
addresses of devices to be discovered. The file must contain
IP addresses in dotted-decimal format separated by line
breaks.
-d <debug level> Specifies the level of detail for debug messages. Values range
from 1 (least detail) to 11 (greatest detail).
-l <log level> Logs debug messages to the file disdevice.log in the current
directory. The log levels are the same as the debug levels.
examples:
disdevice -i 10.127.111.2
discovers the single device with IP address 10.127.111.2
disdevice -i 10.127.111.2 -d 11
discovers the single device with IP address 10.127.111.2, and displays level 11
debug messages
207569-F
Using discovery command line utilities 837
disdevice -i 10.127.111.2 -d 11 -l 11
discovers the single device with IP address 10.127.111.2, displays level 11 debug
messages, and logs level 11 messages to disdevice.log.
disdevice -f /tmp/ipfile -l 11
discovers the devices listed in the ascii text file /tmp/ipfile, and logs level 11
messages to disdevice.log.
The disdevice command also creates a device file and a wrn file like other
topology apps. These miscellaneous files could be empty.
dislink
The dislink utility discovers all the links that originate from a specified device or
list of devices, and adds them to the Optivity database. If the devices are not in the
Optivity database, dislink internally runs disdevice to add the devices first. It also
creates relevant subnets for all ip addresses it encounters. Because of its internal
use of the disdevice utility, dislink is inherently more powerful than disdevice.
To see the links created by dislink, select the device in InfoCenter and expand by
hops.
The syntax for the disdevice command is as follows:
dislink [[-i]|[-r]|[-v]<ipAddress>]|[-f <filename>]

[-s <seedname>][-d <debug level>][-l <log level>]
Where the parameters are as described in Table 197:
Table 197 dislink parameters
-i <ipAddress> Specifies the IP address of a single device from which links are to be
discovered.
-r <ipAddress> Specifies recursive mode, which creates all links for the device at
ipAddress and then runs dislink recursively for each endpoint.

Table 197 dislink parameters (continued)
-f <filename> Specifies the name of an ascii text file containing a list of IP addresses
of devices from which links are to be discovered in recursive mode.
The file must contain IP addresses in dotted-decimal format separated
by line breaks.
-v <ipAddress> Discovers all the VLAN objects (logical and local) encountered.
-s <seedname> Creates the specified seed in the topology database, and also
discovers all of the subnets encountered.
-d <debug level> Specifies the level of detail for debug messages. Values range from 1
(least detail) to 11 (greatest detail).
-l <log level> Logs debug messages to the file disdevice.log in the current directory.
The log levels are the same as the debug levels.
examples:
dislink -i 10.127.113.2
discovers links from the single device 10.127.113.2
dislink -r 10.127.113.2 -d 11 -l 11
discovers all devices and the links between them using recursive mode, starting
from the device 10.127.113.2. Also displays debug level 11 messages and logs
level 11 messages to disdevice.log.
dislink -f /tmp/ipfile -l 11
discovers links recursively from the devices listed in the ascii text file /tmp/ipfile,
and logs level 11 messages to disdevice.log.
dislink -v 10.127.113.2 -s linkseed2 -d 11 -l 11
does the following:
• Runs dislink -r on ipAddress. Note that dislink runs disdevice to discover

devices that are not already in the database
• Discovers all VLAN objects (logical and local) that dislink device encounters
• Create seed linkseed2 in the topology database
207569-F
Using discovery command line utilities 839
• Creates topology database entries for relevant subnets for all ip addresses it
encounters while running dislink -r
• Create topology database entries for subnet-to-device and links relationships,
so that you can see all the devices and links as part of the subnet

207569-F
841
Appendix B
Modifying Fault Correlator startup files
Fault Correlator is the daemon or service that provides fault correlation

information to the Optivity NMS Fault Summary application.
You can modify the Fault Correlator startup files to add new traps, change
correlation parameters, and configure new rules to handle fault conditions specific
to your network.
This appendix includes the following sections:
• “Fault Correlator startup files” on page 842

• “Vendor specification file syntax” on page 843
• “Configuration files for third-party applications” on page 843
• “Trap specification file syntax” on page 844
• “Trap specification file variable definitions” on page 845
• “Trap specification file macros” on page 846
• “Syntax for trap definitions” on page 847
• “Fault specification file syntax” on page 849
• “Examples of Fault Correlator definitions” on page 851
• “Increment and toggle fault examples” on page 859
• “Fault correlator terminology” on page 864

842 Modifying Fault Correlator startup files
Fault Correlator startup files

Fault Correlator loads three types of files when it starts:
UNIX
• $LNMSHOME/apps/fc/trap_specs/* contains all trap definitions.

• $LNMSHOME/apps/fc/fault_specs/* contains all fault definitions.
• $LNMSHOME/apps/fc/vendor_specs/* contains all vendor definitions.
• $LNMSHOME/apps/fc/protocol_specs/ProtocolSpects.txt identifies the faults
that affect logical elements like multicast sessions, OSPF and RIP elements,
and MLT/SMLT/IST links.
Windows
• %lnmshome%\apps\fc\vendor_specs\
• %lnmshome%\apps\fc\trap_specs\
• %lnmshome%\apps\fc\fault_specs
• %lnmshome%\apps\fc\protocol_specs\ProtocolSpects.txt identifies the faults
that affect logical elements like multicast sessions, OSPF and RIP elements,
and MLT/SMLT/IST links.
These files check incoming network events. All files are text files that you can edit
with any text editor.
In a platform-less environment (where there is no optional network management

system installed), all traps received by the daemon are logged in a fault database,
and viewed with the Fault Summary application. When Optivity NMS is installed
in conjunction with platform software, the platform’s trap daemon receives the
traps and forwards them to the Optivity NMS trap server.
The Logical State Recorder daemon computes states of “container” topology

objects. For physical device objects, the states are set directly by the Fault
Correlator daemon.
207569-F
Modifying Fault Correlator startup files 843
Vendor specification file syntax

The vendor specification file lists all vendor definitions for the Fault Correlator.
This information identifies the vendors of hardware producing incoming traps.
The definition of the syntax is as follows:
<VendorName>: <VendorOID>;
For example, see the vendor definition list in the Table 198.
Table 198 Typical Vendor Definitions
Vendor Vendor OID
IBM: 1.3.6.1.4.1.2
Cisco: 1.3.6.1.4.1.9
Nortel Networks: 1.3.6.1.4.1.45
Configuration files for third-party applications

Fault and trap configuration files are installed with Optivity NMS for the
following third-party applications:
• Yurie MX200/MX50
• FVC (Switch, V-Gate, V-Caster)
• ACP: NEC ATM switch
The yurifault.txt, fvcfault.txt, and acpfault.txt fault configuration files are installed
in the %lnmshome%\apps\fc\fault_specs directory.
The yuritrap.txt, fvctrap.txt, and acptrap.txt trap configuration files are installed in
the %lnmshome%\apps\fc\trap_specs directory.

Trap specification file syntax

The trap specification file lists all trap definitions and specifications for the Fault
Correlator. The syntax of this file is very similar to the ASN.1 syntax. There are
several modifications to the MIB-II trap specifications:
• All variables in the VARBIND list need to specify the OID and type.
• The ENTERPRISE name should be followed by OID. For SNMPv2c and
SNMPv3 traps, use the trap OID.
• The TRAPTYPE field specifies the type of trap: SNMPv1, SNMPv2c, or
SNMPv3.
• There are REFERENCE clauses as in the MIB-II trap definition.
• The trap number can be the token ANY which handles special cases such as
the Wellfleet series 7 trap definition where the trap number is really an integer
encoded with 4 octets. The trap number field is not required for SNMPv2c
and SNMPv3 traps.
• There is an optional TRAP_IDENT_CHECK clause, which allows the Event
Engine to identify a trap according to the incoming trap context. This clause is
needed to identify a Wellfleet trap if it is a post 7.8 trap or a pre-7.8 trap. This
clause is also useful for naming a trap according to the trap PDU context such
as the case of RMON traps.
• The FORWARD clause directs the Fault Correlator to forward the trap to
platform when the clause is set to ON. The default is OFF.
• The CORRELATE clause directs the Fault Correlator to process the trap when
the clause is set to ON. The default is ON.
• When both FORWARD and CORRELATE are set to OFF, the trap is ignored
completely.
• CONTENT—This clause lists the context data of the incoming trap that is to
be saved in the fault object for future correlation use.
207569-F
• IDENTIFY—This clause identifies an incoming trap. The Fault Correlator can

apply the basic counting rules for increment and toggle faults to correlate the
same type of traps with the same identification. This clause uses only the data
from the CONTENT clause and IP and SYSTETM variable from the trap
source (explained later).
• CATEGORY—This clause lists the category of the trap, for example, “Error
Events,” “Status Events,” and “Threshold Events.”
• SEVERITY—This clause identifies the severity of the trap.
• DESCRIPTION—This clause lists the description of the trap.
• CAUSE—This clause lists the cause for the trap.
• SOLUTION—This clause lists the solution for the trap.
• AGENTIP_INDEX—This clause specifies then index of the varbind to be
used as the agent IP address. When specified, this field gets the agent IP
address for fault correlation. The index starts from 1.
Trap specification file variable definitions

Table 199 lists the variable definitions that are used in the trap syntax, which are
understood by the Trap Specification Loader and Event Engine in the context of
the incoming trap. See “Trap specification file macros” on page 846 for more
information.
Table 199 Variable definitions in traps
Variable name Description
$TrapNumber The number of the incoming trap.

$VarBind[i] The incoming trap’s VARBIND value. The integer “i” is started
from 1.
$VarBindOID[i] The incoming trap’s ith VARBIND’s instance OID. The integer “i” is
started from 1.
$IP The IP address stored in the incoming trap PDU.
$SYSTEM The system id stored in each fault object that identifies a network
entity. The system id is created when the fault object is created, by
consulting mapping information in the topology database.

Trap specification file macros

Table 200 lists macros used in the following syntax that are understood by the
Trap Specification Loader and Event Engine.
Table 200 Trap specification file macros
Macro name Description
INT_EQ(int1, int2) This macro evaluates to TRUE if integer int1 equals to

integer int2. It returns FALSE otherwise.
INT_NEQ(int1, int2) This macro evaluates to TRUE if integer int1 is not equal to
integer int2. It returns FALSE otherwise.
OID_EQ(oid1, oid2, length) This macro evaluates to TRUE if OID oid1 equals to OID
oid2 up to the length. It returns FALSE otherwise. When
either oid1 or oid2 is null, this macro returns FALSE.
OID_NEQ(oid1, oid2, This macro evaluates to TRUE if OID oid1 is different from
length) OID oid2 up to the length. It returns FALSE otherwise.
When either oid1 or oid2 is null, this macro returns TRUE.
BYTE(UINT32, startByte, This macro returns an integer by extract numOfBytes from
numOfBytes) UINT32 (4 bytes unsigned integer) started from startByte.
The integer startByte starts from 1. Hence the
startByte+numOfBytes must be less than or equal to 5.
Byte 1 is the most significant byte.
INDEX(objectInstanceOID, This macro returns an array of index numbers started from
startIndex, numOfIndex) startIndex with length of numOfIndex. For example, the
s5CmSNode table is indexed by four objects:
s5CmsNodeIfIndx, s5CmsNodeBrdIndex,
s5CmSNodePortIndx, and s5CmSNodeMacAddr. If a trap
s5AuthViolation is returned which has
s5CmSNodeMacAddr as its varbind, you can get the slot
number by using: INDEX($VarBindOID[1], 2, 1).
207569-F
Syntax for trap definitions

The following example summarizes the trap syntax. Any character string
following // is treated as comment. See “Examples of trap definitions” on
page 851 for an example of trap definitions.
<TrapName> TRAP-DEFINITION-TYPE
ENTERPRISE <EnterpriseName> (<EnterpriseOID>)
TRAPTYPE <TrapType>
VARIABLES {<VariableList>}
FORWARD <Forward>
CORRELATE <Correlate>
CATEGORY <Category>
SEVERITY <Severity>
DESCRIPTION <Description>
CAUSE <Cause>
SOLUTION <Solution>
TRAP_NUMBER <TrapNumber>
TRAP_IDENT_CHECK {<TrapCheckList>}
CONTENT {<ContentList>} //Such as slot, port, ring #
IDENTIFY {<IdentifyList>}
;
Table 201 lists the trap syntax elements.
Table 201 Trap syntax elements
Element Syntax
<TrapName> := Any alphanumeric token without imbedded space

<EnterpriseName> := Any alphanumeric token without imbedded space
<EnterpriseOID> := Any OID representation (e.g. 1.3.6.1.4.1.18)
<TrapType> := v1 | v2c | v3
<VariableList> := <Variable> | <Variable>, <VariableList>
<Variable> := <VariableName> (<Type>: <OID>)
<VariableName> := Any alphanumeric token without imbedded space
<OID> := Any OID representation
<Type> := Counter | DisplayString | Enum| Gauge | Integer | IpAddress |
OCTET | OID |
PhysAddress | TimeTicks
<TrapNumber> := Integer | ANY
<Forward> := ON | OFF // default is OFF
<Correlate> := ON | OFF// default is ON

Table 201 Trap syntax elements (continued)
Element Syntax
<Category> := Error Events | Status Events | Threshold Events | Network

Topology Events | Node Configuration Events | Application Alert
Events
<Severity> := Integer (1 – Normal, 2 - Warning, 3 – Minor, 4 – Major, 5 -
Critical )
<Description> := String
<Cause> := String
<Solution> := String
<TrapCheckList> := <TrapCheck> | <TrapCheck> <Op> <TrapCheckList>
<Op>: := “&” | “|”
<TrapCheck> := <TrapIntCheck> | <TrapOIDCheck>
<TrapIntCheck> := INT_EQ(<CheckIntObject>, Integer) | //equal to the integer
INT_NEQ(<CheckIntObject>, Integer) //not equal to the integer
<CheckIntObject>: := <CheckIntVariable> | BYTE(<CheckIntVariable>, Integer,
Integer)
<CheckIntVariable>: := $IP | $TrapNumber | $VarBind[Integer] // This must be an
integer VARBIND
<TrapOIDCheck> := OID_EQ(<CheckOIDObject>, OID, Integer) | //equal to the OID
OID_NEQ(<CheckOIDObject>, OID, Integer) //not equal to the
OID
<CheckOIDObject> := <CheckOIDVariable> | INDEX(<CheckOIDVariable>, Integer,
Integer)
<CheckOIDVariable> := $VarBindOID[Integer] | $VarBind[Integer] // This must be an
OID VARBIND
<ContentList> := <Content> | <Content>, <ContentList>
<Content> := <ContentObject> | BYTE(<ContentObject>, Integer, Integer) |
INDEX($VarBindOID[Integer], Integer, Integer)
<ContentObject> := $TrapNumber | $VarBind[Integer]
<IdentifytList> := <IdentifyObject > | <IdentifyObject >, < IdentifytList>
<IdentifyObject> := $SYSTEM | $IP | $CONTENT[Integer]
<AgentIP_Index> := integer
207569-F
Fault specification file syntax

The fault specification file defines all faults the system handles as well as the
mapping from a trap to a fault. There are two types of faults: Increment Faults and
Toggle Faults.
Each fault type is defined separately. All fault objects have an array to store the
necessary information for later correlation. The mapping of traps to a fault is a
many-to-one relationship: one trap can only map to one fault. But one fault can
have many traps mapped to it.
Fault specification file variable definitions
Table 202 lists the fault specification file variable definitions that are understood
by the Trap Specification Loader and Event Engine in the context of the incoming
trap. See “Trap specification file macros” on page 846 for more information about
the macros used in the trap syntax.
Table 202 Fault specification variables
Variable Name Description
$TrapNumber The number of the incoming trap which is being mapped to

the fault object.
$IP The IP address stored in the incoming trap PDU.
$SYSTEM The system id stored in each fault object that identifies a
network entity. The system ID is created when a fault object is
created, by consulting mapping information in the topology
database.
$LAST_UPDATE_TIME This variable returns the respective fault object’s last update
time.

Fault specification file clauses
Table 203 describes the fault specification file clauses.
Table 203 Fault specification clauses
Clause Description
OBJECT This clause defines on what type of network object the faulty
condition has occurred. For example, the fault may indicate that
a faulty condition has occurred on a SLOT or on a CHASSIS.
CATEGORY The state of each network entity is calculated by a vector of
severity levels assigned to the fault category. This clause
specifies to which fault category the current fault belongs.
EVENT_THRESHOLD This clause specifies how many traps need to be received
within the time interval defined in the TIME_INTERVAL clause
for an increment fault to transition from a pre-active state to an
active state.
TIME_INTERVAL This clause defines the time interval within which all the latest
traps have to be received in order to make an increment fault
transition from the pre-active state to the active state.
AGE_TIME This clause defines the fault object’s life span. If the last trap
received for that fault is longer than the AGE_TIME, the fault is
aged out.
MAX_SEVERITY This clause defines the maximum severity a fault can have.
A fault is in escalated state when it reaches the maximum
severity level.
CAUSE This clause describes the possible cause of the fault.
SOLUTION This clause gives a possible solution to the problem.
TRAP_MAPPING This clause defines what traps map to the fault object in
question. This clause also defines the severity level each trap
contributes to the fault object’s severity. In the case of a toggle
fault, it also specifies if the trap sets the status of the fault or
clears it.
VERIFY_MIB_OBECT This clause defines the MIB object that the Fault Correlator
needs to check in order to clear the toggle fault.
CLEAR_VALUE This clause defines the value, returned by the SNMP GET
operation for the object defined in VERIFY_MIB_OBJECT, to
clear the toggle fault.
DESCRIPTION This clause describes the causes of the fault.
CLEAR_DESCRIPTION This clause describes the conditions that cleared the fault.
207569-F
Examples of Fault Correlator definitions

The following sections provide examples of Fault Correlator definitions.
Examples of trap definitions

The following are examples of trap definitions.
s5AuthViolation TRAP-DEFINITION-TYPE
TRAPTYPE v1
ENTERPRISE s5ComTrap (1.3.6.1.4.1.45.1.6.2.5)
VARIABLES { s5CmSNodeMacAddr (MAC_ADDR : 1.3.6.1.4.1.45.1.6.5.1.1.1.4)}
CORRELATE ON
CATEGORY "Status Events"
SEVERITY 1
DESCRIPTION "Authentication violation"
CAUSE ""
SOLUTION ""
TRAP_NUMBER 1
CONTENT {INDEX($VarBindOID[1], 2, 1), //Board Number
INDEX($VarBindOID[1], 3, 1), //Port Number
$VarBind[1] } //MAC
IDENTITY {$SYSTEM,
$CONTENT[1], //Board Number
$CONTENT[2], //Port Number
$CONTENT[3]} //MAC
;
wfSeries7Traps TRAP-DEFINITION-TYPE
TRAPTYPE v1
ENTERPRISE wellfleet (1.3.6.1.4.1.18)
VARIABLES wfFakeEventString (OCTET : 1.3.6.1.4.1.18.3.5.3.5.4.1),
wfHwSlot (Integer : 1.3.6.1.4.1.18.3.1.2.1.1),
wfLogTrapSeverity (Integer : 1.3.6.1.4.1.18.3.5.3.5.4.2)}
CORRELATE ON
SEVERITY 1
DESCRIPTION ""
CAUSE ""
SOLUTION ""
TRAP_NUMBER ANY // Wellfleet trap number is encoded with 4 bytes.
TRAP_IDENT_CHECK {INT_EQ(BYTE($TrapNumber, 2, 1), 0) & IN_EQ($VarBind[3], 5) }
CONTENT {$VarBind[1], $VarBind[2]}
IDENTIFY {$SYSTEM, $CONTENT[1], $CONTENT[2]}
;

The trap specification can also identify some standard traps that are extended by
vendors. For example, CISCO extended most of the generic MIBII traps by
adding new VARBINDs to those traps, such as the following coldStart trap:
coldStart TRAP-DEFINITION-TYPE
ENTERPRISE snmp
VARIABLES {sysUpTime, whyReload} // whyReload is the Cisco extension
DESCRIPTION “A coldStart trap signifies that the sending protocol entity is
reinitializing itself such that the agent's configuration or the
protocol entity implementation may be altered.”
::= 0
;
In the Trap Spec, you can define a trap specification for Fault Correlator in the
following way:
coldStart_cisco TRAP-DEFINITION-TYPE
TRAPTYPE v1
ENTERPRISE snmp (1.3.6.1.2.1.11)
VARIABLES {sysUpTime (Integer : 1.3.6.1.2.1.1.3), whyReload (OCTET :
1.3.6.1.4.1.9.2.1.2)}
CORRELATE ON
SEVERITY 1
DESCRIPTION “A coldStart trap signifies that the sending protocol entity is
reinitializing itself such that the agent's configuration or the
protocol entity implementation may be altered.”
CAUSE ""
SOLUTION ""
TRAP_NUMBER 0
CONTENT $VarBind[2]}
IDENTIFY {$SYSTEM, $CONTENT[1]}
;
207569-F
An example of SNMPv3 trap specification is given below.
T_RMON_1_RISING_ALARM_1_V3 TRAP-DEFINITION-TYPE
TRAPTYPE v3
ENTERPRISE rmon (1.3.6.1.2.1.16.0.1 )
VARIABLES { alarmIndex ( Integer : 1.3.6.1.2.1.16.3.1.1.1 ),
alarmVariable ( OID : 1.3.6.1.2.1.16.3.1.1.3 ),
alarmSampleType ( Enum : 1.3.6.1.2.1.16.3.1.1.4 ),
alarmValue ( Integer : 1.3.6.1.2.1.16.3.1.1.5 ),
alarmRisingThreshold ( Integer : 1.3.6.1.2.1.16.3.1.1.7 ) }
CORRELATE ON
CATEGORY "Error Events"
SEVERITY 1
DESCRIPTION "An RMON rising threshold of type $3 (alarmSampleType) for the
variable $2 (alarmVariable) has been exceeded. The alarm entry index
was $1, the alarm value was $4, the rising threshold was $5."
CAUSE "An RMON rising threshold was exceeded."
SOLUTION "An RMON rising threshold was exceeded."
CONTENT { $VarBind[1], //alarmIndex
$VarBind[2], //alarmVariable
$VarBind[3], //alarmSampleType
$VarBind[4], //alarmValue
$VarBind[5] } //alarmRisingThreshold
IDENTITY { $SYSTEM,
$IP,
$CONTENT[1] }
;
When Fault Correlator receives a trap PDU, it first compares the trap’s generic
number. If it is between 0 and 5, then this trap is a generic trap and Fault
Correlator checks all the OIDs of the varbinds to determine if they match the
declared varbinds in the trap specification. If the generic number is 6, then this
trap is a proprietary trap and Fault Correlator checks the enterprise OID, the
specific trap number, all the OIDs of the varbinds to determine if they match the
trap specification. When all of the items match, the Fault Correlator checks the
TRAP_IDENT_CHECK macro to make sure the incoming trap satisfies the
condition.
If the condition is also met, Fault Correlator then declares the incoming trap as the
trap in the trap spec, i.e. coldStart_cisco. A normal generic coldStart trap will not
match this spec since it does not match the varbind specification in this definition.
Hence you must make separate trap specification to Fault Correlator for both
coldStart traps, for example, one for the generic coldStart and one for Cisco
coldStart.

Examples of fault definitions
The following are examples of fault definitions.
F_Generic_4_AUTH_FAIL_G4_3K_5K INCREMENT-FAULT-TYPE
OBJECT GENERIC
CATEGORY SECURITY
EVENT_THRESHOLD 1
TIME_INTERVAL 900
AGE_TIME 5400
MAX_SEVERITY 5
FAULT_NAME "Auth Failure"
DESCRIPTION "The authentication failure count was exceeded by device
$1 utilizing the community string $2."
CAUSE "An unauthorized device has attempted to access the sending
device. "
SOLUTION "Determine identity of unauthorized device and verify community
strings and IP addresses of the devices in question. Find the
owner of the device reporting the problem and see what
applications may be causing this difficulty. Follow necessary
procedures to update devices with appropriate information."
TRAP_MAPPINGS {(T_Generic_5_AUTH_FAIL_G4_3K : 1),
(T_Generic_5_AUTH_FAIL_G4_5K : 1)}
;
F_Generic_3_LINK_DOWN_G2_G3 TOGGLE-FAULT-TYPE
OBJECT ROUTER_INT
CATEGORY CONNECTIVITY
AGE_TIME 432000
FAULT_NAME "Link Down"
DESCRIPTION "The communications link on interface $1 is down. "
CLEAR_DESCRIPTION"The communications link on interface $1 is now up. "
CAUSE "The sending device reports that one of its configured
communication links has failed. "
SOLUTION "Verify cable connections and links for the failed interface.
Reset interface, if necessary. When link comes up, check for any
side-effects. "
TRAP_MAPPINGS {(T_Generic_3_LINK_DOWN_G2 : 9 : SET),
(T_Generic_4_LINK_UP_G3 : 0 : CLEAR)}
;
207569-F
Increment fault
The definition of an increment fault is listed below. See “Increment fault example”
<FaultName> INCREMENT-FAULT-TYPE
OBJECT <ObjType>
CATEGORY <Category>
EVENT_THRESHOLD <EventThreshold>
TIME_INTERVAL <TimeInterval>
AGE_TIME <AgeTime>
MAX_SEVERITY <MaxSeverity>
CAUSE <Cause>
SOLUTION <Solution>
RAP_MAPPINGS {<TrapMappingList>}
;
Table 204 lists the increment fault elements.
Table 204 Increment fault elements
Element Description
<FaultName> := Any alphanumeric token without embedded space

<ObjType> := GENERIC | SEGMENT | ROUTER_INT | ROUTER |
SWITCH | CHASSIS | STATION | SLOT | PORT |
OTHER_OBJ
<Category> := LOAD | CONNECTIVITY | COMPONENTS | ERRORS |
SECURITY | CONFIG | OTHER_CTGRY
<EventThreshold> := Integer
<TimeInterval> := Integer
<AgeTime> := Integer
<Description> := <FaultTextString>
<Cause> := <FaultTextString>
<Solution> := <FaultTextString>
<FaultTextString> := “<FaultTextObject>”
<FaultTextObject> := <FaultTextObject> <FaultTextVariable>
<FaultTextObject> |
NULL | any string without {“ $ : ;}.
<FaultTextVariable> := $IP | $SYSTEM | $LAST_UPDATE_TIME |
$integer:<FaultPrintType>
<FaultPrintType> := Decimal | Hex | String

Table 204 Increment fault elements (continued)
Element Description
<TrapMappingList> := <TrapMapping> | <TrapMapping>, <TrapMappingList>

<FaultName> := Any alphanumeric token without embedded space
SWITCH | CHASSIS | STATION | SLOT | PORT |
OTHER_OBJ
SECURITY | CONFIG | OTHER_CTGRY
<EventThreshold> := Integer
<TimeInterval> := Integer
The syntax definition for FaultTextString allows the CAUSE and SOLUTION
clauses to contain a fault object context in its string. In general terms, the CAUSE
and SOLUTION clauses strings with imbedded fault object context in them. The
imbedded fault object context variables start with an escape character $. A
variable $integer denotes that the value of this variable is in the CONTENT array,
which is defined in the trap specification, with index being the integer. For
example, $1 is the value of CONTENT[1], etc.
207569-F
Toggle fault
Table 205 describes the definition for a toggle fault. See “Toggle fault example”
<FaultName> TOGGLE-FAULT-TYPE
OBJECT <ObjType>
CATEGORY <Category>
AGE_TIME <AgeTime>
VERIFY_MIB_OBJECT<VerifyMIBObject>
CLEAR_VALUE <ClearValue>
CLEAR-DESCRIPTION<Clear Description>
CAUSE <Cause>
SOLUTION <Solution>
TRAP_MAPPINGS {<TrapMappingList>}
;
Table 205 Toggle fault elements
Element Description
<FaultName> := Any alphanumeric token without imbedded space

SWITCH |
CHASSIS | STATION | SLOT | PORT | OTHER_OBJ
SECURITY |
CONFIG | OTHER_CTGRY
<AgeTime> := Integer
<VerifyMIBObject> := <MIB_Object_Name> (<Type> : <MIB_OID>) |
<MIB_Object_Name>
(<Type> : <MIB_OID> : <Instatance_Expr>)
<Instatance_Expr> := <Instance_Value> | <Instance_Value>,<Instance_Expr>
<Instance_Value> := Integer | $VarBind[Integer] | BYTE($VarBind[Integer],
Integer, Integer) |
$CONTENT[Integer] | BYTE($TrapNumber, Integer,
Integer) |
INDEX($VarBindOID[Integer], Integer, Integer)

<MIB_Object_Name> := Any alphanumeric token without imbedded space
<Type> := Counter | DisplayString | Enum| Gauge | Integer |
IpAddress | OCTET |
OID | PhysAddress | TimeTicks

Table 205 Toggle fault elements (continued)
Element Description
<MIB_OID> := Any OID representation (e.g. 1.3.6.1.4.1.18)

<ClearValue> := Any value string which will be converted to the type of
VerifyMIBObject>
<Description> := <FaultTextString>
<Clear-description> := <FaultTextString>
<Cause> := <FaultTextString>
<Solution> := <FaultTextString>
<FaultTextString> := “<FaultTextObject>”
<FaultTextObject> := <FaultTextObject> <FaultTextVariable>
<FaultTextObject> | NULL |
any string without {“ $ : ;}.
<FaultTextVariable> := $IP | $SYSTEM | $LAST_UPDATE_TIME | $integer:
<FaultPrintType>
<FaultPrintType> := Decimal | Hex | String
<TrapMappingList> := <TrapMapping> | <TrapMapping>, <TrapMappingList>
<TrapMapping> := (<TrapName> : <Severity> : <Status>)
<TrapName> := Any alphanumeric token without imbedded space
<Severity> := Integer | $CONTENT[Integer] | BYTE(<SeverityObj>,
Integer, Integer)
<SeverityObj> := $CONTENT[Integer] | $TrapNumber
<Status> := SET | CLEAR
207569-F
Increment and toggle fault examples

The following sections introduce two examples, one for an increment fault and the
other for a toggle fault.
Increment fault example
The following example is of an authentication trap sent by a System 5000 device.

The trap is defined in the Trap Specification file as shown in the table.
s5AuthViolation TRAP-DEFINITION-TYPE
TRAPTYPE v1
ENTERPRISE s5ComTrap (1.3.6.1.4.1.45.1.6.2.5)
VARIABLES { s5CmSNodeMacAddr (MAC_ADDR : 1.3.6.1.4.1.45.1.6.5.1.1.1.4) }
CORRELATE ON
SEVERITY 1
DESCRIPTION "Authentication violation"
CAUSE ""
SOLUTION ""
TRAP_NUMBER 1
CONTENT {INDEX($VarBindOID[1], 2, 1),//Board Number
INDEX($VarBindOID[1], 3, 1),//Port Number
$VarBind[1]//MAC
IDENTIFY {$SYSTEM, $CONTENT[1],//Board Number
$CONTENT[2],//Port Number
$CONTENT[3]//MAC
;

The following example shows how the above trap is defined In the fault
specification file.
F_S5_AUTH_VIOLATION_1 INCREMENT-FAULT-TYPE
OBJECT PORT
CATEGORY SECURITY
EVENT_THRESHOLD 3
TIME_INTERVAL 600
AGE_TIME 3600
MAX_SEVERITY 6
CAUSE “There is an authentication violation at system $IP, slot
$1:DEcimal and port $2:Decimal. The offending station has the MAC
address $3:Hex. The last violation occurred at $LAST_UPDATE_TIME.
This problem may be caused by invalid BaySecure configuration at
device $IP”
SOLUTION “Check the BaySecure configuration to correct the problem. If the
BaySecure is configured correctly, then disconnect the station
with the MAC address $3:Hex on slot $1:Decimal and port $2:Decimal
to avoid security being breached”
TRAP_MAPPLING {(s5AuthViolation : 1)}
;
The fault engine applies the default counting rule for increment fault to the traps
with the same identification.
Assume that several traps arrive as indicated in the time line shown in Figure 325:
Figure 325 Example fault time line
Time in
seconds
0 600 1200 1800 2400 3000 3600
Traps 1 2 3 4 5 6
9734EA
207569-F
The following is a list of actions in the Fault Correlator table as each trap arrives:
• When the Fault Correlator receives trap #1, the Event Engine looks up its trap
definition list and identifies the trap as s5AuthViolation trap.
• The Event Engine then looks up its trap to fault mapping and creates a new
fault object, F1, with the type being F_S5_AUTH_VIOLATION_1.
• The Event Engine inserts F1 into the Fault Object Space and sends Fault
Update Trigger to the Fault Engine.
• The Fault Engine uses the default rule for increment fault to try to correlate F1
with any existing faults. Since no existing fault can be correlated, F1 stays in
the Fault Object Space with the state as pre-active.
• The Fault Correlator receives trap #2 and #3. Again, the Event Engine maps
the incoming traps to the new fault objects F2 and F3 with the type being
F_S5_AUTH_VIOLATION_1.
• The Event Engine inserts the new faults into the Fault Object Space and
triggers the Fault Engine.
• The Fault Engine uses the default rule for increment fault to correlate F2 and
F3 with F1. The correlation updates the context for F1 and deletes F2 and F3
from the Fault Object Space.
• The F1 update starts an examination of the fault context. As defined in the
fault specification file, the EVENT_THRESHOLD is 3 and the
TIME_INTERVAL is 600. Although the event threshold condition has been
met, trap #1 is too far apart from trap F2 and F3 (> 600 seconds). The F1 fault
remains in pre-active state and with a severity level of 0.
• As the Fault Correlator receives trap #4 and the fault correlates with F1, F1
has three traps which are close enough (<= 600 seconds), to transition F1
from pre-active to active state. As defined in the fault definition, each trap
within the time interval will contribute 1 severity level to the fault object.
Since traps F2, F3, and F4 are received within the time interval, F1 now has a
severity level of 3.
• When F1 transitions from pre-active state to active state, update message are
sent to the Fault Database Recorder and the Network Entity State Engine to
record the change and to recalculate network entity state.
• When more traps arrive, each trap contributes one more severity level to F1.
When the maximum severity is reached, F1 is then transitioned from active
state to escalated state. Again, update messages are sent to the Fault Database
Recorder and the Network Entity State Engine to record such change and to
recalculate the network entity state.

• Since the maximum severity is 6 as defined in the fault definition, the severity
remains at 6 no matter how many more traps are received.
• Traps are aged-out when their life spans are greater than 3600 seconds
(AGE_TIME). When all the traps are aged out, F1 is aged-out also.
Toggle fault example
The following examples are of a linkDown and linkUp trap. The following table
shows how the two traps are defined in the Trap Specification file.
linkDown TRAP-DEFINITION-TYPE
TRAPTYPE v1
VARIABLES { ifIndex(Integer : 1.3.6.1.2.1.2.2.1.1) }
FORWARD ON
CORRELATE ON
SEVERITY 1
DESCRIPTION ""
CAUSE ""
SOLUTION ""
TRAP_NUMBER 2
CONTENT {$VarBind[1]}
IDENTIFY {$CONTENT[1]}
;
linkUp TRAP-DEFINITION-TYPE
TRAPTYPE V1
VARIABLES { ifIndex(ifIndex(Integer : 1.3.6.1.2.1.2.2.1.1) }
FORWARD ON
ORRELATE ON
SEVERITY 1
DESCRIPTION ""
CAUSE ""
SOLUTION ""
TRAP_NUMBER 3
CONTENT {$VarBind[1]}
IDENTIFY {$CONTENT[1]}
;
207569-F
The following example shows how the fault object is defined in the fault
specification file.
F_LINK_DOWN_G2 TOGGLE-FAULT-TYPE
OBJECT ROUTER_INT
CATEGORY CONNECTIVITY
AGE_TIME 432000// 5 days
CAUSE “The interface link $1:Decimal just went down at device $IP.
Either the link $1:Decimal connection is broken or the device with
address $IP is powered down.”
SOLUTION“If the status is still in SET state, please check if the
device
$IP is still up.”
TRAP_MAPPLING {(linkDown : 9 : SET),
(linkUp : 0 : CLEAR)}
;
The fault engine applies the default counting rule for toggle fault to the traps with
the same identification.
As in the case of the previous increment fault example, two traps arrive at the
Fault Correlator. The first trap is the linkDown trap and the second is the linkUp
trap. The process the Fault Correlator uses to handle these traps is listed below:
• When the Fault Correlator receives the linkDown trap, the Event Engine looks
up its trap definition list and identifies the trap as a linkDown trap.
• The Event Engine then looks up its trap to fault mapping and creates a new
fault object F1 with the type as F_LINK_DOWN_G2.
• The Event Engine inserts F1 into the Fault Object Space and sends Fault
Update Trigger to the Fault Engine
• The Fault Engine uses the default rule for toggle fault to try to correlate F1
with any existing faults. Since there is no existing fault that can be correlated,
F1 stays in the Fault Object Space with the status as SET and severity as 9.
• At the later time, the Fault Correlator receives the linkUp trap. The Event
Engine looks up its trap definition list and identifies the trap as a linkUp trap.
• The Event Engine then looks up its trap-to-fault mapping and creates a new
fault object, F2, with the type as F_LINK_DOWN_G2 but with status as CLEAR
and severity as 0.
• The Event Engine inserts F2 into the Fault Object Space and sends new Fault
Update Trigger to the Fault Engine.

• The Fault Engine uses the default rule for a toggle fault to correlate F2 with
F1. The correlation process updates the F1 status to CLEAR and sets its
severity to 0. The F2 fault object is also deleted from the Fault Object Space.
• When F1 changes state, an update message is sent to the Fault Database
Recorder and the Network Entity State Engine to record such change and to
recalculate network entity’s state.
• The fault object is aged-out when its life span is longer than five days (432000
seconds).
Fault correlator terminology

The Fault Correlator terms that you should know about are described in the
following sections.
Event
An event is either a trap coming from the network or an SNMP Get reply for a
previous issued SNMP GET operation. A trap from the network could be a raw
device trap, a platform trap, or an application trap.
Fault object
A fault object represents a specific condition that has occurred on a network entity
about which the network manager may need to be aware. There are two types of
faults in FC: increment and toggle.
Toggle fault
Toggle faults, as opposed to increment faults, have a precise “Active” or “Clear”

state. After the fault transitions to an “Active” state, it is possible to verify if the
fault has transition to a “Clear” state.
A fault first transitions to an “Active” state when a trap is received to that effect.
Usually, another trap, with a different trap number or one bearing a different value
in one of the “status” varbinds of the trap is received, which signifies a “Clear”
event.
207569-F
This causes the fault to transition to a “Clear” state. In most cases, the state can
also be verified by querying a “status” MIB variable on the faulty device. If no
“Clear” trap is defined, the SNMP MIB GET is the sole source of fault status
verification.
Fault state
Each fault object has a precise state at any given time.
Table 206 describes the states of an incremental fault.
Table 206 States of an incremental fault
State Description
Pre-active Signifies that some traps have been received from a particular
network entity but are not serious enough to constitute an active
fault.
Active Fault transitions from a pre-active state to the active state when the
number of traps for the same fault from the same network object
exceeded the Event Threshold specification within the time interval
specification.
Escalated Fault transitions from an active state to an escalated state when the
fault severity level reached the maximum allowed severity level.
Aged Fault transitions from the pre-active, active state to the aged state
when there was no additional traps of the same type received from
that particular network entity within a predetermined time interval
(age time interval).
Unmonitored Fault has been detected before, but for some reason the state of the
fault cannot be determined at the present time by the FC.

Table 207 describes the states of a toggle fault.
Table 207 States of a toggle fault
State Description
Active Signifies the presence of the faulty condition that needs the attention of
the network administrator.
Clear Signifies a faulty condition that has been cleared.
Aged A fault object can be transitioned from an active state to the aged state
when there is no additional trap of the same type received from that
particular network entity within a predetermined time interval (age time
interval).
Acknowledged The network administrator knows about the problem and does not wish
to be notified any more about the condition.
Unmonitored Represents a fault has been detected before, but for some reason the
state of the fault cannot be determined at the present time by the FC.
Fault category
In the Fault Correlator system, every fault object belongs to one of the following
fault categories:
• Connectivity
• Error Rate
• Component Condition
• Load
• Configuration
• Security
The state of a network object is calculated within each of these categories.
207569-F
Fault severity
Each fault in the system has a severity level that can range from 0 to 10. A fault
with a severity of 0 is in the system for information only. It does not indicate any
problem with the associated network object.
An example of such “fault” is the coldStart trap. The fault object created by
coldStart event only informs the network administrator that a system has just
connected to the network and is in the process of booting up. A fault of severity 10
indicates a very serious problem with the associated network object.
Network entity state
Each network entity, such as module, chassis, subnet, VLAN, and so forth, has a
precise state at each given moment. The state of the network entity is defined by a
vector of severity levels assigned to the fault categories.
The severity level of each category can range from 0 (fully functional, or “green”)
to 10 (non-functional, or “red”).
• Levels 1 to 3 are low severity.

• Levels 4 to 6 are medium severity.
• Levels 7 to 10 are high severity.
FC only records states for network entities that are stored in the topology
database. The state recorder daemon propagates the states to the logical level
objects (subnet, segment, and so forth) accordingly.

Table 208 summarizes the alarm status and severity level criteria.
Table 208 Alarm status and severity levels
Severity Alarm Default Alarm

Level Level Color Label
10 0 Red Critical
9 0 Red Critical
8 0 Red Critical
7 0 Red Critical
6 1 Orange Warning
5 1 Orange Warning
4 1 Orange Warning
3 2 Yellow Caution
2 2 Yellow Caution
1 2 Yellow Caution
0 3 Green Operational
NA Unmonitored Blue Unmonitored
207569-F
869
Index
A color coding 320

criteria 325
access administrators 77 Max and Mean calculation methods 326
access control 801 propagation, enabling 324
enabling 85 allowed nodes
token list 78 configuring 799
Access Control Administration software-based 799
error messages 99 support 799
menu bar 81 allowed nodes plus 799
Optivity Users pane 83 agent support 800
troubleshooting 98 configuring 800
window 80 hardware support 800
look and feel of 98
application
Permission Groups pane 84
deleting 537
Permission pane 83
device support in InfoCenter, viewing 531
status bar 84
launch configuration 534
Access permissions for OIT 774 supported network resources, selecting 536
access privileges for Expanded View 554 Application Launch
access to InfoCenter, about 183 deleting application 537
active baseline error messages 538
icon for 336 overview 521
starting 522
activity window 569
supported resources, selecting 536
adaptive address learning 799 window 522
administrative functions 67 asset categories
advanced intrusion control 829 adding 721
age out 146 adding properties to 722
age-out process understanding 146 asset database
exporting to file 714
Alarms folder, InfoCenter 186, 319
importing from file 715
colors, selecting 321
synchronizing 710
fault status
calculation method, choosing 327 asset tree 701
categories 317 assets
categories to monitor, choosing 318 adding and removing 710

870 Index
adding manually 712 AutoTopology Manager window

editing properties for 706 illustration of 141, 697
listing and viewing 702 look and feel of 175
manually removing 714 parts of 141, 697
ATM call types 609 status bar 142, 698
ATM calls Autotopology Manager window 68
analyzing 625
filtering 625 B
supported 609
background color, folders 275
ATM objects
adding 612 background image
adding to a view 612 InfoCenter view 212
clearing from view 615 printing 213
copying 615 backplane
cutting from view 614 connection status, viewing 567
deleting from view 614 highlighting, enabling 577
deselecting 613 Backplane/VLAN List dialog box 561
finding in view 616 backup_trapdb 694
inverting selection 613
pasting 615 bar Indicators
defaults, configuring 479
attributes indicators, percentage 435
adding and removing from a category 722 reading 434
adding to an asset 723 statistics, viewing 434
deleting from an asset 725
baseline
attributes, InfoCenter objects deleting 338
InfoCenter and Fault Summary 297
Topology 296 baselines
deleting all for a multicast session 338
Auto Save
changing between Yes and No 205 BaySecure LAN Access
described 203 overview 793
enabling or disabling 204 security components 793
security configuration process 810
autolearn security features 793
configuring 799 security modes 794, 821
continuous 799
one-shot 799 BaySecure LAN Access window
device information table 809
automatic fault responses toolbar buttons 806, 808
configuring
scripts 671 Bridge Group & VLAN, highlighting 577
trap forwarding 678 broadcast unknown server (BUS) 596
discovering the network with 148
status messages 176
207569-F
Index 871
C operational status of backplane 567

chassis status, viewing 567
call delta 625
Choice ParserElement 528
Call Table view 608
displaying 627 circular layout, InfoCenter 197
searching 617 colors, InfoCenter alarms 320
Call View columns
color code naming 455, 457
call delta 625 reordering 445
indicates status 610 sorting 441, 478
columns columns, moving in InfoCenter tables 215
repositioning 628
community strings
resizing 627
changing for security 812
sorting 628
default 104
file options 598
deleting 121
graphical view
described 812
CallCount 606
exporting 133
CallView 604
importing a new file 131
Help
modifying 120
on menus and toolbar buttons 603
reordering 121
icon color codes 610
resetting changes 123
messages
saving changes 124
progress indicator 603
timeout value conversion 133
status bar 603
stopping a process 612 Community Strings Editor
window access permissions for 109
contents area 603 IP address syntax 104
displaying shortcut menu 629 troubleshooting 135
menu bar 600 window 110
status bar 603 menu bar 112
toolbar buttons 601 status bar 116
toolbar 112
CallCount table
searching 617 configuration management, performing 581
sorting 628 contents pane 561, 565
CallView contents panel, InfoCenter
starting from Path Trace 742 description 192
CallView table views 192
sorting 628 continuous autolearn 799
Centillion 65 conventions, text 54
Chassis Show Nodes 569 copy
chassis status InfoCenter
objects, identifying 575 folders 287

872 Index
objects between folders 288 overview 743

shared folders 293 Database layer, InfoCenter 193, 232
Counter ParserElement 527 Datalink layer, InfoCenter 193
customer support 58 DBProperty ParserElement 527
customized folder, InfoCenter default
creating and saving 282 InfoCenter views 206
layout 197 changing 207
opening and viewing 284 monitor options 545
editing 550
D delete
daemons folder, InfoCenter 290
file names 683 object, InfoCenter
starting 690 undeleting 303
stopping 688 undo folder, creating 284
verifying deleting
from a Windows NT command line 686 object with age out 302
from the Windows NT control panel 685 objects permanently 304
on UNIX 686 deleting events 652
Database 748 destination address filtering 798
database device
backing up 758 back panel, viewing 567
definitions 745 backplane connection status 567
deleting 760 fan status 567
evomni 745 managing 576
Expanded View 745 power supply status 567
exporting (saving) 743, 758 selecting whole 576
Fault Correlator 745 temperature sensor status 567
get elements of 743 unknown 559
importing (restoring) 743 unsupported 482
MIB 745 device detail view, InfoCenter 298
OmniView 745
resetting 763 device filtering 137
smop 745 Device Inventory Viewer 695
topology 745 device NVRAM, saving security configuration
user 745 to 811, 820
verifying 743 device properties
vogon 745 command 808, 811
waldo 745 viewing 811
Database Admin Tool device support
database pane 750 integrating with Optivity NMS 9.1 773
element pane 751
main window 747 device upgrade, what happens 787
207569-F
Index 873
diagnostics E
command 569, 579
window 569, 580 eavesdrop protection
configuring 798
dialog boxes
Enabled mode 822
Access Control Switch 85
hardware-based 798
Add Permission Group 92
Add/Remove Optivity Users 86, 88 edit default monitor options 550
Attach Permission Group 93 elements defined 412
disabled security mode end node, locating using Path Trace 738
authorized user action 822 end nodes, InfoCenter
unauthorized user action 822 about 734
disabling a port 581 layer 194
disabling an object 578 error messages 512
disclosure 107 Application Launch 538
Monitor Options 551
discovery
options for 137 event
parameters for 149 unmonitoring 650
routerless 169 event details
viewing details 156 viewing 650
discovery seeds event filter
creating 156 example of 669
deleting 161 event, trap 864
understanding 146
Events
viewing or editing 160
working with 649
disdevice 836
events
dislink 837 deleting 652
display DNS names, global InfoCenter setting 211 deleting from Fault Summary 652
displaying activity 589 in Fault Summary 649
latest, displaying 652
displaying nodes attached to an object 583
viewing 650
displaying object profile 582
execution environment
displaying VLANs and segment highlighting 584 command line syntax 524
displaying VLANs and segments 584 ParserElement types and syntax 526
DNS names, displaying or hiding in production rules 530
InfoCenter 211 reserved symbols 525
special symbols 528
domain name server (DNS) 563, 577
terminal symbols 529
DVMRP network management application, specifying
displaying statistics for sessions 496 for 536
in Fault Summary filters 662
expand by hop 620
expand by hops, InfoCenter

874 Index
about 307 increment fault descriptions 865

how to 308 increment fault example 859
Expanded View Logical State Recorder daemon 842
access permissions 554 network entity state 867
access privileges 554 Network Entity State Engine 861, 864
how it works 553 startup files
menu bar commands 561 modifying 842
overview 553 startup files for Solaris 842
shortcut menu commands 569 startup files for Windows 842
starting terminology 864
from other Optivity NMS applications 577 toggle fault 857
start file options 556 toggle fault example 862
toggle fault states 866
Expanded View window 560, 561, 565
trap age out 862
export folder contents to a file 289 trap log file 842
export folder definition to a file 294 trap specification file
macros 846
F trap definition syntax 847
variable definitions 845
Fan status, viewing 567 trap specification file syntax 844
Fault Trouble Ticketing System Gateway 861, 864
described 635 vendor definitions 843
fault 865 vendor specification file 843
fault colors fault management processes, customizing 549
Path Trace, default 741 fault management services or daemons 683
fault configuration files, third-party fault management, performing 578, 579, 580, 581
applications 843 fault object 864
Fault Correlator 841 fault state 865
alarm status 868 fault status, InfoCenter
definitions 851 Alarms folder 319
trap 851, 854 calculation method, choosing 327
Event engine 861, 863 categories 317
fault categories 866 categories to monitor, choosing 318
Fault Database Recorder 861, 864 color coding 320
Fault engine 861, 863 colors, selecting 321
Fault Object Space 863 criteria 325
fault severity 867 Max and Mean calculation methods 326
fault severity levels 868 propagation, enabling 324
fault specification file
clauses 849 Fault Summary
syntax 849 events, updating 652
variable definitions 849 Fault Correlator daemon/service 841
increment fault 855 scripts
207569-F
Index 875
adding 675 folder properties

and Script Server 671 background color 275
configuring 671 filter attributes 262
deleting 678 logical operators for 266
example 673 relational operators for 266
IP address examples 677 special characters for 267
parameter definitions 673 folder details 268
trap forwarding presentation
configuring 678 about 267
Fault Summary window configuring 273
menu bar 641 search scope
toolbar buttons 644 device type 262
object name 261
feedback on Optivity documentation 74
object subtype 262
file options object type 261
Fault Summary 598 subnet assignment 262
filter elements folder view shortcut menu, InfoCenter 198
understanding 658
folders
working with 664
adding to the Fault Summary filter tree 655
filter results deleting from the Fault Summary filter tree 655
paging through 654
folders, InfoCenter
sorting 654
closing 213
filter tree 644 configuring search properties 270
filters copying 287
creating and modifying 656 copying objects between 288
creating new 657 copying shared 293
deleting 655 creating 269
executing 653 creating for undoing deleted objects 284
in Fault Summary 653 custom, opening 284
logical groups for 658 deleting 290
NOT operator for 660 exporting contents to a file 289
opening for editing 657 exporting definition to a file 294
organizing with the filter tree 654 importing definition from a file 294
property filters for 660 listed 186
saving 657 opening 278
saving to different folders in Fault presentation options 267
Summary 655 printing 282
using in Fault Summary 653 renaming 269
folder panel saving 278
InfoCenter saving customized layout 282
description 186 sharing 291
displaying or hiding 191 view formats 196
view layout 196
folder panel shortcut menu, InfoCenter 190

876 Index
format H
InfoCenter views 196
changing 208 health status
color coding 610
format, InfoCenter views 207
interpreting 613
Frame Relay layer, InfoCenter 194, 233
Help
Front panel of managed device on MIB objects 448
identifying objects 566 using 72
viewing 566
hierarchical layout, InfoCenter 196
Front View
identifying objects 575
selecting objects 576
I
icons
G identifying 247
icons, InfoCenter views
graph window 417 displaying or hiding labels 210
graphical format, InfoCenter 196 import folder definition 294
graphical view inactive baseline
CallCount 606 icon for 336
CallView 604
individual user
graphs adding 125
combining 464 modifying 126
defaults, configuring 480
legend, applying 466 InfoCenter
legend, removing 466 access to 78, 183
line traces, viewing separately 464 starting
opening 463 from the Windows NT Start menu 183
parts of 422 troubleshooting 315
regrouping 465 window
rotating 465 contents panel 192
symbols, viewing 466 folder panel 186
type, changing legend 465 launchpad 243
values, viewing 466 menu bar 216
status bar 246
green dot 412 Toolbar 223
grid layout, InfoCenter 197 views 192
grid lines, displaying in InfoCenter tables 213 InfoCenter folder for 188, 189
Group ParserElement 526 integrated Optivity applications, starting from
groups InfoCenter 251
attaching 93 interface
customizing 95 unmanaging or managing 328
Internet layer, InfoCenter 193
207569-F
Index 877
intrusion control 821 setting poll interval 577

advanced intrusion and eavesdrop legacy applications 66
protection 831
legend of objects, InfoCenter 247
configuring 797
hardware-based 797, 825, 829 LES/BUS Extension Profile
software-based 797, 799, 823, 829 command 569
software-based with eavesdrop protection 824 window 569
IP address LES/BUS Peer Profile
matching 105 window 569
wildcards 105 log file, error 482, 559
IP address examples, fault scripts 677 logical group
IP telephony 188 deleting 668
IP Telephony system logical groups
viewing parts of 362, 363 adding to filters 665
changing type 665
IP-VPN 188
negating 666
understanding 658
K Logical State Recorder daemon 842
Keyword ParserElement 528 Logical View 568
logical view 568
L look and feel, changing 481
LAN emulation (LANE) 595, 596
LAN emulation configuration server (LECS) 596 M
LAN emulation server (LES) 596 MAC addresses, changing how OmniView
launchpad displays 479
InfoCenter 243 management window
background bitmaps 245 parts of 571
displaying or hiding 245 poll interval, setting 577
displaying or hiding a tool 245
masquerade 107
layer, InfoCenter views
Max fault calculation, InfoCenter 326
changing 209
description 193 Mean fault calculation, InfoCenter 326
layout, InfoCenter views menu bar
changing 209 InfoCenter 216
default, changing 207 menu bar commands 112, 142, 382, 698, 776
description 196 Access Control Administration 81
leaf element described 412 AutoTopology Manager 142, 382, 698
BaySecure LAN Access 806
LED
Call View 600
monitoring 578
Community Strings Editor 112
poll interval 577, 579
Database Admin Tool 748

878 Index
Fault Summary 641 selecting for manual discovery 330

menu bar commands OmniView window 406
Menus, InfoCenter Web browser 222 N
message stream modification 107 navigation pane
MIB expression adding a network resource to 426
creating for a custom statistics pane 460 browsing resources with 424
validating 461 in OmniView window 405
MIB Help 579 understanding 412
MIB objects network discovery level, customizing 549

searching for by name 459 network management application
viewing descriptions of 448 device support in Application Launch 531
minus sign 412, 478 network service access point (NSAP) address 596
MLT configurations, viewing 312 node access
MLT links allowed nodes 799
identifying 731 allowed nodes plus 799, 800
identifying with Path Trace 737 command 800, 814
list 799
modification of information 107
node access list
Modify Application Launch dialog box 522 allowed nodes 814
Monitor Options creating 799, 800, 814
customizing 549 not-allowed nodes 800, 814
defaults 545 node element described 412
dialog box, parts of 544
propagating 545 node name and type 605
starting from InfoCenter 542 NVRAM, saving security configuration 811
troubleshooting 551
user access for 548 O
monitor pane 405, 414
object
monitored resources and entities listing 430 clearing from a view 615
multicast cutting from view 614
protocol visualization rediscovery 329 deleting 614
multicast baseline deselecting 613
saving a session 336 diagnostics, viewing 578
displaying attributes 629
multicast baseline report
enabling 581
opening 202
finding 616
multicast discovery identifying 575
protocol visualization options 152 inverting selection of 613
telnet login required for 138 managing 576
Multicast protocols layer, InfoCenter 194, 232 resetting 578, 579, 580
multicast session selecting 576
207569-F
Index 879
selecting whole object 576 from a Web browser 402

shortcut menu 600 start file options 399, 402
status, viewing 578, 579 window
object, InfoCenter about 393, 395
attributes illustration of 405
InfoCenter and Fault Summary 297 look and feel of 481
topology 296 menu bar 406
copying between folders 288 monitor pane 414, 415
creating 299 navigation pane 412, 414
cutting from a view 300 parts of 406
deleting with age out 302 RMON and SMON 484
details for, viewing 298 status bar 406
displaying traversal views 305 toolbar 411, 750
finding one-shot autolearn 799
in a folder view 311 Optional ParserElement 528
in the Optivity NMS database 312
options, discovery 151
launching applications from multiple
objects 305 Optivity integrated applications
legend 247 categories in InfoCenter 250
pasting into a folder 301 starting from InfoCenter 251
properties for Optivity Integration Toolkit (OIT)
modifying for 298 technology 769, 770
viewing 298 Optivity NMS applications, starting from Path
recovering 301 Trace 741
undeleting 303
Optivity user
OIT adding 125
oitInstall program 773 modifying 126
UNIX, location of files 787
OPTIVITY_ADMIN permission group 89
updating device support in Optivity 773
Windows, location of files 787 OPTIVITY_VIEW permission group 89
OIT Administration Tool orthogonal layout, InfoCenter 197
window 775 other Optivity NMS applications, starting 561
OIT Administration Tool window
menu bar 776 P
oitapplied.cnf OIT configuration file 787 parent monitor options, overriding 548
oitinstall command 787 ParserElement types and syntax
oitInstall program, location Choice 528
UNIX 773 Counter 527
Windows 773 DBProperty 527
oitinstall.cnf OIT configuration file 787 Keyword 526, 528
OmniView Optional 528
starting Simple 526

880 Index
Path Trace changing how OmniView coordinates with

contents pane sorting 478
fault colors 741 setting parameters for 446
overview 734 port profile
end nodes, locating a path to 738 data type template 401
overview 731 displaying 510
problems, resolving 742
Power supply status
protocols used 731
viewing 567
recommended specifications 732
starting CallView 742 power supply status, viewing 567
viewing log messages in 742 preferences 577
path trace preferences, InfoCenter views
fault colors 741 about 206
path trace results background image 213
fault colors 741 displaying DNS names 211
displaying or hiding
Path Trace window 734
a background image 212
performing configuration management 581 grid lines 213
permanent virtual circuit (PVC) 596 launchpad tools 245
permission the launchpad 245
attaching 89 the status bar 246
changing a token 89 the toolbar 234
defined 76 view summary details 202
detaching 89 icon labels 210
tokens 78 launchpad background bitmaps 245
print options 213
permission group
view summary 213
adding 91
attaching 93 preferences, setting 577
customizing 89, 95 print
list of 84 InfoCenter 282
Permission Groups pane 84 Print dialog box 561
Permission pane 83 print options, InfoCenter views 213
permission setting product support 58
changing for a token 83 profile window 569
permission tokens 76, 83 properties, InfoCenter object
Physical layer, InfoCenter 193 modifying 298
plug-ins viewing 298
listing 249 property filter
plus sign 412, 477 adding to filter 667
deleting 668
polling
editing 668
207569-F
Index 881
property filters resource icons

for Fault Summary filters 660 in monitor frame 414
relationships for 664 in navigation frame 477
protfr 138 setting defaults for 477
protmr 138 resources 414
described 412
protocols 138
finding in navigation pane 428
protur 138
Resources folder, InfoCenter 188
protvpls 138
restore_trapdb 694
protvpn 138
RMON
publications data types 396, 502
hard copy 58 entities 414
related 57 RFCs 395, 484
purgeTrap 693 RMON1 history group 504
RMON2 userHistory group 504
Q routerless discovery 169
queries, folder
copying 293 S
sharing 291 Save to NVRAM command 811
Quickhelp 74 scaling 138
scripts
R Fault Summary
read community string 812, 813 adding 675
deleting 678
read/write community string 812, 813
email example 673
rediscover 259 parameter guidelines 673
rediscovering 259 search
related publications 57 folder view 311
Release Notes for Optivity NMS 57 Optivity NMS database 312
properties, configuring in InfoCenter 270
remote selection
using 620 security
authentication 106
remote selection, InfoCenter components 794
about 309 configuration process 810
between InfoCenter views 309 current configuration, viewing 810, 812, 814
using between Optivity NMS applications 310 features 793
reserved symbols 525 getting latest information from network 811
Reset History command 561 modes 793
resolving problems 767 privacy 106
user-based 102, 106
resource border described 414
security features

882 Index
autolearn 799 identifying with Path Trace 737

Eavesdrop Protection 798 SMON
eavesdrop protection 798 data types 396, 502
node access 799 entities 414
security modes RFCs 395, 484
Checked1Max 831 SNMP parameters 813
Checked1Min 829
SNMP polling 633
described 821
Disabled 822 SNMP trap 635
ListMax 824 sorting changing how OmniView coordinates with
ListMin 823 polling 478
Only1Max 826 special characters 618
Only1Min 825
special symbols, execution environment command
Sequential 822
line syntax 528
security permissions 148
start file options 556
seed range 139
starting
services Access Control Administration 79
fault management names 683 TD Continuity Test 381
starting 689
starting other Optivity NMS applications 577
stopping 687
user-based 107 startup files
Fault Correlator 842
Set Preferences dialog box 561, 578
statistics
Set Trap Receiver Table window 569
changing the types displayed 444
shared folder, InfoCenter comparing saved with current 476
about 189 exporting 471
copying 293 importing saved 471
sharing 291 intersection of data 449
shortcut menu MIB Help 448
folder panel, InfoCenter 190 multiple device pane 448
folder view, InfoCenter 198 RMON 487
Web browser, InfoCenter 222 saving with Print to File 470
Shortcut menu commands 569 SMON 487
types 435
Show Nodes
union of data 449
window 569
viewing for a network element 433
Showing Activity 589 viewing for multiple devices in one pane 448
Simple ParserElement 526 viewing graphically 463
SMLT viewing with bar indicators 434
identifying 731 statistics panes
SMLT configurations, viewing 312 adding new customized 455
closing 447
SMLT links
customizing existing 457
207569-F
Index 883
in monitor frame 414 tabular view 607

minimizing and maximizing 442 CallCount 607
opening 433 CallView 605
setting defaults for 476 TD Continuity Test
viewing one at a time 476 window 382
status bar 561, 748 look and feel of 391
displaying or hiding 482 status bar 386
InfoCenter 246 technical publications 58
displaying or hiding 246
technical support 58
on the OmniView window 405
temperature sensor status, viewing 567
Status dialog box 814
terminal symbols 529
status of ATM entity
icon color 610 text conventions 54
interpreting 613 third-party applications
superping 547 fault configuration files 843
trap configuration files 843
support, Nortel Networks 58
threats, types of 107
switch
label 605 toggle fault 864
Switch Community layer, InfoCenter 194 tokens 78
changing permission 89
switched virtual circuit (SVC) 596
list of 78
symbols for execution environment command
toolbar
line 525
Call View 601
symmetrical layout, InfoCenter 196 displaying or hiding 482
Syslog event Fault Summary
described 635 buttons 644
moving 644
T graph window buttons 417, 421
InfoCenter 223
table displaying or hiding 234
Call Table 608 moving 622
CallCount 607 OmniView window buttons 405, 411
CallView 604, 605 toolbar buttons 565, 571
resizing columns 627 AutoTopology Manager 142, 698
searching 617 Community Strings Editor 112
sorting 628 OIT Administration Tool 776
table cells, selecting for graphing or exporting 444 TD Continuity Test 382
table columns, InfoCenter Toolbar Status box 565
displaying grid lines 213 topdt 138
resizing 214
sorting 214 topology discovery 152
starting 152
tabular format, InfoCenter 196

884 Index
topology process attributes, InfoCenter 296 removing 87

toprt 138 root 77
setting access for 88
topst 138
USM 102
tracing a path between two end nodes 736
Trap
described 635 V
trap configuration files, third party vendor specification file for Fault Correlator 843
applications 843 view
trap database, managing 692 changing the layout 619
trap forwarding clearing ATM objects from 615
configuring in Fault Summary 678 closing 629
displaying 626, 627
trap receiver table, using 585 graphical 604, 606, 626
traversal views, displaying in InfoCenter 305 printing 631
troubleshooting 767 tabular 605, 607, 608, 627
Access Control Administration 99 view domain 259
Community Strings Editor 135 rediscovering 259
error messages 512 view domain, InfoCenter
InfoCenter 315 rediscover 259
messages 633
Monitor Options 551 view domains
Path Trace 741 assigning to users 95
problem resolution 515 creating 162
resolving problems 633 editing or deleting 164
viewing information about 165
view summary, InfoCenter
U displaying or hiding 202
undelete print option 213
InfoCenter object 303 viewing event details 650
Unicast protocols layer, InfoCenter 194, 232 viewing events 650
user access views
InfoCenter 183 chassis status 567
Monitor Options 548 front view 566
user database 745 logical 568
user privileges 801 views, InfoCenter 192
user privileges for Expanded View 554 background color, selecting 275
background image, displaying or hiding 212
user-based security model (USM) 102
closing 213
users columns
adding 86 moving 215
Administrator 77 sizing 214
defined 76 sorting 214
207569-F
Index 885
cutting object from 300 changing environment 619

defaults 206 InfoCenter in a Web browser 222
deleting object from with age out 302 shortcut menu 600
displaying traversal 305 view 603
formats 196 windows
changing 208 Graph 417
changing default 207 OmniView 405, 406
grid lines, displaying or hiding 213
workspaces, saving and loading views with 430
icon labels, displaying or hiding 210
layers 193
changing 209
layout 196
changing 209
layouts
changing default 207
pasting object into 301
preferences 206
presentation options 267
print options, setting 213
recovering cut object 301
remote selection between 309
undeleting object 303
view summary
displaying or hiding 202
views, saving and restoring with workspaces 430
VLAN
local 189
logical 189
VLAN layer, InfoCenter 194
VPLS 189
W
WAN trunk layer, InfoCenter 194
Web browser
import and export database functions disabled
in 753, 758
Web browser, InfoCenter
opening menus in 222
window
AutoTopology Manager 141, 697, 698
Call View 599

Using Optivity NMS 10.3 Applications: Part No. 207569-F November 2004 4655 Great America Parkway Santa Clara, CA 95054

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Using Optivity NMS 10.3 Applications: Part No. 207569-F November 2004 4655 Great America Parkway Santa Clara, CA 95054

Uploaded by

Copyright:

Available Formats

Part No.

4655 Great America Parkway

Using Optivity NMS 10.3

Copyright © 2004 Nortel Networks

Restricted rights legend

Nortel Networks Inc. Optivity network management software license

Using Optivity NMS 10.3 Applications

Using Optivity NMS 10.3 Applications

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Flexible architectural approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Using Optivity NMS 10.3 Applications

OIT Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Access Control Administration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Troubleshooting Access Control Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Community Strings Editor overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Using Optivity NMS 10.3 Applications

Selecting SNMPv1 traps if SNMPv3 trap registration fails . . . . . . . . . . . . . . 128

AutoTopology Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Creating view domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

InfoCenter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Using Optivity NMS 10.3 Applications

Displaying or hiding the view summary details . . . . . . . . . . . . . . . . . . . . . . . 202

Opening an object shortcut menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

About folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Using Optivity NMS 10.3 Applications

Adding and removing view domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Copying objects between folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Using Optivity NMS 10.3 Applications

Discovering multicast elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Comparing multicast session baselines with each other . . . . . . . . . . . . . . . . 345

Discovering IP-VPN elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Discovering IP telephony devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Using Optivity NMS 10.3 Applications

VPLS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

TD Continuity Test overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

OmniView and MView overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

Using Optivity NMS 10.3 Applications

Viewing network utilization for full-duplex operation . . . . . . . . . . . . . . . . 438

Saving statistics with print to file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470

Using Optivity NMS 10.3 Applications

Monitoring RMON and SMON data types with MView . . . . . . . . . . . . . . . . . . . . 502

Application Launch overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

Terminal symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

Getting started with Monitor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

Expanded View overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

Using Optivity NMS 10.3 Applications

Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

Adding a trap receiver table entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586

Call View overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

Using Optivity NMS 10.3 Applications

Using common Call View commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

Displaying link attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

Fault Summary overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Using Optivity NMS 10.3 Applications

Organizing filters with the filter tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

Fault Scripts are not getting executed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681

Device Inventory Viewer overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

Using Optivity NMS 10.3 Applications

Checking for updated agent versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

Path Trace overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

Database Admin Tool overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743

Using Optivity NMS 10.3 Applications

OIT overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769