Tivoli NetView for UNIX
Release Notes
Version 6.0.2
January, 2001
Copyright Notice
Copyright © 2001 by Tivoli Systems, an IBM Company, including this
documentation and all software. All rights reserved. May only be used
pursuant to a Tivoli Systems Software License Agreement or Addendum for
Tivoli Products to IBM Customer or License Agreement. No part of this
publication may be reproduced, transmitted, transcribed, stored in a
retrieval system, or translated into any computer language, in any form or
by any means, electronic, mechanical, magnetic, optical, chemical, manual,
or otherwise, without prior written permission of Tivoli Systems. The
document is not intended for production and is furnished "as is" without
warranty of any kind. All warranties on this document are hereby disclaimed
including the warranties of merchantability and fitness for a particular
purpose.
Copyright (C) Hewlett-Packard Company 1991, 1993. All rights
reserved.Reproduced by permission. This product is based, in part, on
Hewlett-Packard Company's OpenView product. Copyright (C) Dartmouth College
1992. All rights reserved. Reproduced by permission.
Note to U.S. Government Users -- Documentation related to restricted rights
-- Use, duplication or disclosure is subject to restrictions set forth in
GSA ADP Schedule Contract with IBM Corp.
TomeRaiderized by Ken Webster, Support Manager for Netview Unix/NT
ken.webster@tivoli.com
If you need support for your Netview product, please contact 800-Tivoli8.
Trademarks
The following product names are trademarks of Tivoli Systems or IBM
Corporation: AIX, AS/400, DB2, DFSMS/MVS, IBM, MVS/ESA, NetView,
OpenEdition, OS/2, OS/390, OS/400, RS/6000, RACF, System/390, Tivoli,
Tivoli Management Environment, Tivoli Ready, and TME 10.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks or
registered trademarks of Microsoft Corporation.
Java is a trademark of Sun Microsystems, Incorporated.
UNIX is a registered trademark in the United States and other countries
licensed exclusively through X/Open Company Limited.
Other company, product, and service names mentioned in this document may be
trademarks or service marks of others.
Notice
References in this publication to Tivoli Systems or IBM products, programs,
or services do not imply that they will be available in all countries in
which Tivoli Systems or IBM operates. Any reference to these products,
programs, or services is not intended to imply that only Tivoli Systems or
IBM products, programs, or services can be used. Subject to Tivoli System's
or IBM's valid intellectual property or other legally protectable right,
any functionally equivalent product, program, or service can be used
instead of the referenced product, program, or service. The evaluation and
verification of operation in conjunction with other products, except those
expressly designated by Tivoli Systems or IBM, are the responsibility of
the user.
Tivoli Systems or IBM may have patents or pending patent applications
covering subject matter in this document. The furnishing of this document
does not give you any license to these patents. You can send license
inquiries, in writing, to: IBM Director of Licensing, IBM Corporation,
North Castle Drive, Armonk, New York, 10504-1785, U.S.A.
Table of Contents
Introduction
New Features
System Requirements
Installation Notes
Patches Required for this Release
Defects Fixed in this Release
Product Limitations and Workarounds
Documentation Changes
Product Notes
Introduction
This document provides important information about Tivoli NetView for UNIX,
Version 6.0.2. These notes are the most current information for the product
and take precedence over all other documentation. Please note that the
version of Tivoli NetView described is an upgrade to Tivoli NetView for
UNIX V6.0 or Tivoli NetView for UNIX V6.0.1, and presumes that one of those
two products is already installed and working in the customer's
environment.
This document, together with the Tivoli NetView for UNIX V6.0 Release
Notes, and the Tivoli NetView for UNIX Installation and Configuration,
Version 6.0 book, provides all of the necessary information for planning
and performing the installation of Tivoli NetView for UNIX V6.0.2. Please
review all notes thoroughly before installing or using this product.
New Features
The following information describes new and changed functionality that has
been incorporated into the Tivoli NetView for UNIX product since the Tivoli
NetView for UNIX V6.0 release:
QuickTest
QuickTest is an enhanced ping tool that polls all managed interfaces and
quickly determines the complete status of the node. QuickTest displays the
ifAdminStatus and ifOperStatus of each interface for nodes that use SNMP to
poll for status. For all other nodes, QuickTest displays the ping result
for each interface. If the status of an interface has changed, the map is
updated and an event is sent.
QuickTest is available from the NetView console and NetView Web client by
selecting Test->QuickTest or Test->QuickTest Critical. You must have one or
more nodes selected to access the QuickTest menus. The Test->QuickTest
Critical menu item only polls interfaces that are currently marked as down.
The Test->QuickTest menu item polls all interfaces, regardless of their
current status.
You can also run QuickTest from the command line. The QuickTest command has
the following syntax:
quicktest nodelist [-z] [-P] [-F]
where nodelist specifies one or more nodes to be polled. This may be either
a single node name or a list of nodes separated by spaces or tabs.
Other options include:
-z
Only poll down interfaces.
-P
Use ping instead of SNMP requests to poll SNMP status nodes.
-F
Send an event for all polled interfaces, regardless of whether there is a
status change. Normally, an event is only sent when the status has changed.
Demand Poll Enhancements
During periods when the netmon daemon is busy, such as during initial
discovery or during bursts of status or configuration polling, it is not
uncommon for a demandpoll request to fail with a message that netmon was
too busy to perform the operation. The netmon daemon has been enhanced to
give demandpoll and quicktest operations priority, resulting in fewer such
failures.
Loadhosts Enhancement
The loadhosts utility now provides the capability to add new interfaces as
Unmanaged.
The input file for the loadhosts command specifies the interfaces to be
created in the NetView databases. A new token ! can be added to the
beginning of entries in this file to indicate that they should be created
as Unmanaged. This option overrides the -d switch on the loadhosts command
line (which specifies to create all interfaces as down).
In the following sample loadhost input file, the interface 14.8.2.100 is
created as Unmanaged:
!14.8.2.100 myrouter.ibm.com myroute
When using this loadhosts capability, the netmon -l switch should be set to
create new nodes as managed. You can do this on the netmon configuration
page of Server Setup.
Unsolicited Generic Traps
The netmon daemon now dynamically verifies and sets the status for the node
or interface when it receives the following generic traps: Warm Start, Cold
Start, Link Down, and Link Up.
Acknowledged Status Import/Export Capabilities
With the existing map-based behavior for Acknowledge, operators on client
machines must refresh the map to be notified that objects have been
acknowledged or unacknowledged. The acknowledged action is map-based and
only affects the current map. Also, acknowledging objects on read-only maps
is not persistent; restarting the console clears all the acknowledged
statuses. In addition, you cannot set the Acknowledged status from the
command line.
A new global-based mode for Acknowledge is available in Tivoli NetView for
UNIX V6.0.1. When global-based mode is set, the Acknowledged status is an
object attribute. All NetView clients are notified when an object is
acknowledged or unacknowledged immediately, regardless of which map is open
and even if the action is performed on a read-only map. In addition, the
Acknowledged status can be set on an object from the command line,
permitting the transfer of the Acknowledged status to backed up NetView
databases.
By default, the behavior for Acknowledged remains map-based. However, you
can set an environment variable to activate the new global-based behavior
for individual clients. You may want the old behavior for some clients and
the new behavior for others. For instance, you may have NetView client
users who do not need to see objects being acknowledged by the network
operations center.
Global-based Mode
This section describes the global-based mode in more detail.
To activate the global-based mode, set the environment variable
NVMAPGLOBALACK equal to 1 on the NetView machine. It must be set before you
invoke the NetView console.
You can acknowledge an object using one of three methods. The first, from
the map, uses the graphical user interface. The other two methods, from an
event or through nvdbimport, allow users greater control of the
Acknowledged state outside of the graphical user interface.
>From the Map. To acknowledge a map object, select the object and choose
Monitor->Acknowledge to set the field isAcknowledged to TRUE for that
object and generate an event to update all open maps (local or NFS)
connected to the NetView server. If a NetView console running in
global-based mode starts up later, the object shows as Acknowledged.
>From an event. To acknowledge an object from the command line, type:
event -b openview -e event -a object ID
Where event is either ACK_EV (acknowledge event) or UNACK_EV (unacknowledge
event), and object ID is the object ID of the object to be acknowledged in
the OVW database. For more information on this command, see the event man
page.
This event sets the status of the specified object to Acknowledged on all
open maps where the object's status is CRITICAL or MARGINAL. It also sets
the Acknowledged field to TRUE in open NetView maps. If no NetView sessions
are running in global-based mode, this field is not set. If Netview
consoles running in global-based mode start up later, the object shows as
acknowledged.
Using nvdbimport. To directly set the Ovw database field isAcknowledged for
chosen objects, use nvdbimport. See the nvdbimport man page for more
details.
Export/Import Utility for Acknowledged Status
You can review an example of using the event-based approach to set the
acknowledged state in the sample import/export utility script
/usr/OV/bin/acknowledgeUtil.
To use the script, type:
acknowledgeUtil -export -map mapname > filename
acknowledgeUtil - import < filename
A complete description of the arguments is given at the top of the script.
Only Critical and Marginal objects are changed to Acknowledged. Attempts to
Acknowledge normal objects during the import operation are silently
ignored.
Ping and SNMP Timeout Values
The netmon daemon no longer dynamically adjusts the ping and SNMP timeout
values. These values remain as configured in the SNMP Options dialog.
Router Fault Isolation Automatically Enabled
The Router Fault Isolation feature (also known as Event Suppression) is now
active by default in NetView. Router Fault Isolation attempts to
differentiate between nodes that are actually down and nodes that are
simply unreachable when the router servicing them is down. For a detailed
explanation of Router Fault Isolation, see the description in
/usr/OV/doc/RouterFaultIsolation.htm . If this feature is not desired, you
can turn it off using the -K 0 option for netmon.
This option has the following syntax:
-K 0 | 1
0
Turn Router Fault Isolation OFF
1
Turn Router Fault Isolation ON. This is the default.
To turn this feature off, add -K 0 to the netmon.lrf file and enter the
following commands:
/usr/OV/bin/ovstop netmon
/usr/OV/bin/ovdelobj /usr/OV/lrf/netmon.lrf
/usr/OV/bin/ovaddobj /usr/OV/lrf/netmon.lrf
/usr/OV/bin/ovstart netmon
Reduced Polling to Routers
As a part of the Router Fault Isolation feature, a new option -k 2 has been
added to netmon to prevent status polling to any router with a current
status of Unreachable.
If this option is used, it may be necessary to manually ping a node in an
occluded area to start recovery for some isolated routers.
This option has following syntax:
-k 0 | 1 | 2
0
Don't suppress any pings or SNMP requests.
1
Suppress pings and all SNMP requests to non-routers in Unreachable nodes.
This is the default.
2
Suppress pings and all SNMP requests to Unreachable routers.
To prevent status polling to any routers whose current status is
Unreachable, add -k 2 to the netmon.lrf file and enter the following
commands:
/usr/OV/bin/ovstop netmon
/usr/OV/bin/ovdelobj /usr/OV/lrf/netmon.lrf
/usr/OV/bin/ovaddobj /usr/OV/lrf/netmon.lrf
/usr/OV/bin/ovstart netmon
HSRP Interface Enhancements
The netmon daemon now allows customers to decide whether or not to use MAC
addresses found in the ARP tables to determine whether an interface is
HSRP. In previous releases of Tivoli NetView V6, the default netmon action
was to identify HSRP interfaces defined explicitly in the netmon seed file,
and then try to identify additional HSRP interfaces by looking for HSRP MAC
addresses in the ARP tables. In Tivoli NetView V6.0.2, netmon assumes all
HSRP interfaces are explicitly defined in the netmon seed file unless the
netmon -V option is given. If the -V option is given, netmon uses the same
algorithm for determining HSRP interfaces as in previous releases, looking
in both the netmon seed file and in the ARP tables.
Do not enable this option if you have HSRP routers with proxy ARP enabled.
Doing so will cause proxied ARP table entries to be icorrectly identified
as HSRP interfaces which will later need to be automatically deleted,
causing unwanted database and trap activity.
Redundant Gateway Support
The netmon daemon has been enhanced to support redundant gateways.
Commonly, redundant gateways are implemented as duplicate interfaces on
multiple routers rather than a virtual interface as in HSRP. Previously,
redundant gateways were reported as duplicate IP addresses. By placing the
redundant interface in the netmon seed file and prefixing it with the HSRP
flag (e.g. %192.168.0.1), the interface will be treated as an redundant
interface rather than an interface with an erroneously defined duplicate IP
address. The active router will then be HSRP polled.
Collecting MLM MIB Variables Synchronously
Mid-Level Manager for UNIX has added a new threshold environment variable
@sync which allows you to collect MIB variables synchronously (all at the
same time). For example,
@sync(MIB1, MIB2, MIB3...)
In the above example wildcarding is allowed. To collect a MIB variable from
several hosts:
@sync(host1:MIB1, host2:MIB1, ...) or
@sync(alias1:MIB1, alias2:MIB2, ...) or
alias:@sync(MIB1,MIB2)
However, MIB variable expressions such as the one shown below are not
supported:
@sync(MIB1, @sum(MIB2, MIB3), MIB4) or
@sync(MIB1 + MIB2)
Thresholding is allowed but the USER SHOULD BE AWARE that the thresholding
applies against ALL of the MIB variables regardless of type.
The results are placed in the MLM Threshold Results table. The results of
the first MIB variable is located by its Name in the Threshold Results
table. The results of each successive MIB variable is located by its Name
concatenated with a unique number id -n- where n is a number.
Event Correlation Upgrades
The Action Node defines a set of environment variables describing the event
for use by the command to be executed. The NVATTR_1, NVATTR_2... variables
describe the variable bindings. A new environment variable NVATTR_COUNT is
defined as containing the number of variable bindings passed to actionsvr;
those include the varbindings of the trap, and three appended to the end of
the list automatically - the trap category, source, and severity. In
addition, all the NVATTR_n variables (n is from 1 to 50) are unset prior to
being defined for each event so stale data is removed. If a variable
binding is defined but empty, the corresponding environment variable
NVATTR_n is set to "<novalue>"
Improved NetView Client Synchronization
The map synchronization process between the NetView client and server has
been enhanced to improve the synchronization time of client maps.
Additional MIBS and Traps
Thirty-one SNMP V1 versions of selected Cisco MIBs and two additional SNMP
V1 MIBs have been added to NetView in the /usr/OV/snmp_mibs subdirectory,
and the cisco.readme has been expanded. NetView users may find these useful
with snmpCollect.
A new trapd.conf has been provided in
/usr/OV/newconfig/OVSNMP-RUN/trapd.conf which contains forty-seven new
enterprises and one hundred and nine new traps, added for Cisco and Novell
devices.
Use nvaddtrapdconf to merge it with your existing trapd.conf via the
following commands:
cd /usr/OV/conf/C
cp trapd.conf trapd.conf.orig
nvaddtrapdconf /usr/OV/newconfig/OVSNMP-RUN/trapd.conf
System Requirements
In addition to the requirements described in the Tivoli NetView for UNIX
Installation and Configuration, Version 6.0 manual, the Tivoli NetView for
UNIX V6.0.2 installation temporarily requires an additional 150 Mb of disk
space in /usr/OV during the installation, and will use 40 Mb more of disk
space in /usr/OV after the installation is complete.
Installation Notes
Execute the "snapshot" function of the nvpatch script, found in the /BCK
directory of the Tivoli NetView for UNIX V6.0.2 installation media, on each
system containing a NetView server or client. For information on how to use
this script, see the README file found in the /BCK directory.
Install the Tivoli NetView for UNIX V6.0.2 Server Patch on all machines
running the Tivoli NetView V6.0.2 Server:
On the Desktop menu of the Tivoli Framework graphical user interface, click
on Install -> Install Patch and select Tivoli NetView Server V6.0.2 Patch
6.0-NVS-0002. Read each panel completely and correct any reported problems
before proceeding.
Verify that the patch installed successfully and that all daemons and
application are working correctly by examining the log files in the /tmp
directory, specifically the update.log file and any 6.0-NVS-0002_BIN_after.
* files. Search the update.log file for the following strings:
SEV_
ERROR
WARNING
and correct any errors associated with the strings.
If an error occurred during the patch installation process, there will be a
6.0-NVS-0002_BIN_after.error file in the /tmp directory; if no error
occurred, then there will be a 6.0-NVS-0002_BIN_after.debug file in the
/tmp directory.
If a patch installation fails or a severity 1 or severity 2 error occurs,
the reported problem must be corrected and the installation repeated. Prior
to re-performing the patch installation, do one of the following:
Perform the nvpatch script "backout" function (see the README file found in
the /BCK directory of the Tivoli NetView for UNIX V6.0.2 installation
media).
Remove the appropriate patch flag files stored within the Tivoli Framework
for the patch whose installation failed. The appropriate flag files are
listed in the table below. The $BINDIR environment variable is set by the
Tivoli Framework setup script found in the /etc/Tivoli directory.
Patch Type
Flag Files
Server
$BINDIR/.installed/pa_6.0-NVS-0002_BIN
$BINDIR/../../msg_cat/.installed/pa_6.0-NVS-0002_CAT
$BINDIR/../.installed/pa_6.0-NVS-0002_CNFTAR
$BINDIR/../.installed/pa_6.0-NVS-0002_TAR
Client
$BINDIR/.installed/pa_6.0-NVC-0002_BIN
$BINDIR/../../msg_cat/.installed/pa_6.0-NVC-0002_CAT
Database
$BINDIR/.installed/pa_6.0-NVD-0002_BIN
Once the patch installation has been attempted, Tivoli NetView is in an
unknown state and may not execute correctly until either the nvpatch script
"backout" function has been executed, or the patch installs successfully.
In the same manner as described for the server, install and verify the
installation of the Tivoli NetView for UNIX V6.0.2 Client Patch on each of
the client machines.
Please note that the installation window(s) from the server installation
(in the previous step) MUST BE CLOSED prior to beginning the client patch
installation; otherwise, the client installation will fail with several
Tivoli Framework error messages.
If the patch installation succeeds, there will be a
6.0-NVC-0002_BIN_after.debug file in the /tmp directory; if it did not,
then a 6.0-NVC-0002_BIN_after.error file will exist in the /tmp directory
which contains a description of the failure.
In the same manner as described for the server, install and verify the
installation of the Tivoli NetView for UNIX V6.0.2 Databases Patch on the
NetView servers.
If the patch installation succeeds, there will be a
6.0-NVD-0002_BIN_after.debug file in the /tmp directory; if it did not,
then a 6.0-NVD-0002_BIN_after.error file will exist in the /tmp directory
which contains a description of the failure.
If the Tivoli NetView Mid-Level Manager (MLM) update is desired, install it
at this time. For information on how to perform the installation, see the
readme files in the appropriate platform subdirectory under the /MLM
directory on the Tivoli NetView V6.0.2 installation CD-ROM.
Verify that all NetView daemons start and run properly on all machines that
had a NetView patch applied.
Patches Required for this Release
No additional patches are required for Tivoli NetView for UNIX V6.0.2.
Defects Fixed in this Release
The following customer-reported problems were fixed in Tivoli NetView for
UNIX V6.0.2:
IY09035
Map created with null/blank name
IY09037
Problem transferring Oracle data to MLM
IY09239
Problem running NgraphSunByDN on good snmpCollect data
IY09364
New map snapshop given same name as existing snapshots
IY09485
Deleting trap with large enterprise ID causes GUI shutdown
IY09575
Ovwls -l shows wrong owner/group on Solaris
IY10377
XNMGraph doc does not explain counter values well
IY10672
Using right mouse button in a snapshot freezes NetView
IY11411
NetStat giving duplicate PID numbers for a TAVVE program
IY11588
XXMap/GTMD coring after Solaris E-Fix applied
IY11666
JAVA.IO.IOEXCEPTION due to closed file descriptor
IY11722
NVTurboDataBase fails to compress .ovf file
IY11724
Free space fragmented in Database overflow files
IY11761
Ruleset action node reporting unreasonable syntax error
IY11808
Get Alias portion of demandpoll timing out
IY11888
Request for documentation additions/upgrades
IY11903
Man page for snmpColDump incorrect in V6.0
IY11985
NVutil cores when extracting fields from smartset
IY12046
Need fix for incompatibilities in ovtypes.h for AIX 4.3.3
IY12063
Unreachable status for routers incorrectly overridden
IY12073
PrintTool lists no queues if too many defined
IY12274
Netmon moving duplicate addresses but not refiguring status
IY12281
Flag reset on routers with unnumbered interfaces
IY12633
SNMPCollect will not collect on smartsets that contain proxies
IY12648
Need to allow unnumbered links on any interface type
IY12813
Release Notes instructions for changing hostname wrong
IY12916
NetviewNT - Web Client cores accessing maps
IY12975
IP Addresses in snmp configuration GUI will not demandpoll
IY13035
NetView 6.0 install on solaris 2.5.1 fails
IY13044
NetViewNT - Web Client not loading mibs
IY13052
Netmon will not start with AIX bos.net.tcp.client.4.3.3.20
IY13104
Netview not recognizing ICMP request issued by netcheck
IY13217
Smartset includes nodes that do not match rule
IY13246
NVServerD sends only last slot value in event to TEC
IY13377
Comment in /usr/OV/bin/netnmrc could cause problems
IY13531
NVSec_Admin cores when # of user definitions exceeds 500
IY13549
The getsysenv script fails on solaris
IY13941
The Mib2Trap manpage needs to be updated
IY13966
Netmon fails to get ovsnmp.conf data via IP wildcards
IY14015
Demand Poll "Down Since" date and time missing
IY14056
HSRP routers not being managed correctly
IY14228
Change in IOS invalidates CDP Cache Address
IY14241
SNMP using default community name when its not defined
IY14262
Netmon cores when Solaris RFI enabled
IY14397
Security does not allow login if hostname greater than 32 chars
IY14708
SNMP Address field in topology DB is incorrect
IY14889
SNMP Collection not working on Digital UNIX
IY15033
Netmon not handling redundant gateways correctly
The following customer-reported problems were fixed in Tivoli NetView for
UNIX V6.0.1 and succeeding releases:
IY00488
OVW_Binary core due to multiple Xwindow callbacks
IY00835
NVSecD memory leak on security authorization
IY03331
OVWDBMap won't delete object after NVTurboDatabase used
IY04379
Entries in oid_to_command not being translated properly
IY05734
NetMon cores on HP device
IY06092
Trapd cores when receiving bad trap
IY06361
XNMAppmon coring when closing due to non-null pointer
IY06629
Background lost on submap during close/reopen on DEC
IY06633
Deleting vertices not working on closed maps
IY06684
User can create map despite being restricted
IY06890
NVEvents cores when clicking outside of current event area
IY06506
"Admin Down" flag remains on node after status change.
IY06910
Trapgend not working after being pushed to remote system
IY06988
NetMon loops on HSRP interfaces with 1 SNMP address
IY06997
XNMLoadMIB2 fails to parse the "bits" construct
IY07219
NVColToSQL "CollectTime" var has only a 2 digit year
IY07220
Cisco 7206 Router not discovered by netmon
IY07308
Mnemonic character conflict in OVW "Edit" menu
IY07562
GTMD Memory Leak
IY07915
GTMD Icons not retaining customization on GUI restart
IY08209
OVW_Binary coring on bad pointer in NavTree
IY08325
OVW_Binary coring on Xwindows closecallback function
IY08822
NVSniffer hangs on Solaris when polling unreachable nodes
IY08824
NVSniffer -t hangs for timeout values under 1000
IY09037
Problem transferring MLM data to Oracle
IY09325
Multiple up events when NetMon & MLM on same box
IY09330
Collection rule fails when IPSTATUS=ACKNOWLEDGED
IY09476
Unnecessary messages filling netmon trace log
IY09812
Tell users ACKNOWLEDGE status shouldn't be propagated
IY09841
NVTecia -stop not sending "NVServerD Ending" event
IY09874
Icons going to wrong place on cut & paste operation
IY09934
Unable to configure NetView daemons via smitty
IY10027
XXMAP cores when show protocol is used
IY10052
Saving dynamic workspaces more than once gives error
IY10063
OVW_Binary cores when doing a cut/paste on the map
IY10451
NetView not showing DNS IP address sending trap to TEC
IY10623
On Solaris, cut/paste operation takes over an hour
IY10712
NVSecD memory leak on nvauth login/logout
IY10768
Running ovwexit produces core file on NetView NT 6.0
IY10776
Starting NetView UNIX via icon changes root dir permissions
PJ26956
NVWakeUp -n doesn't work with interface names with spaces
PJ26960
Use of ruleset containing event attribute as origin fails.
Product Limitations and Workarounds
Some NetView man pages are not visible to the man command on the Solaris
2.6 operating system. Until the correct operating system patch can be
determined, set the environment variable MANPATH to
/usr/share/man:/usr/OV/man.
If either the Tivoli desktop or Netscape runs at the same time as the
NetView graphical user interface on Tru64, an X resource problem can cause
part or all of the graphical user interface to core. To avoid this problem,
exit both Netscape and the Tivoli desktop prior to starting the NetView
graphical user interface.
The new QuickTest functions are not available from the NetView GUI or the
Web client when NetView is running in the Simplified Chinese, Japanese, or
Korean locales. These functions will be available for the NetView Language
kits in a future release.
Tivoli NetView V6.0 and succeeding maintenance releases do not support the
Java 2 technology found in JDK 2.0. Tivoli NetView V6 requires JRE 1.1.8 to
be installed on the system in order to run the Tivoli NetView Web Client as
an applet.
On Solaris, after installing the Tivoli NetView V6.0.2 client and server
patches, it may be necessary to refresh the snmp daemon on the server in
order to restore the client/server connection. If the client and server
cannot communicate after the patches have been installed, simply stop and
restart the snmp daemon on the NetView server machine.
AIX machines that use a GXT300P graphics adapter are having problems
running NetView after AIX 4.3.4 is installed. The device drivers in that
kit for the GXT300P graphics adapter do not handle the resizing of the
nvevents windows, and completely freeze up the system with an LED code of
185. The problem can be worked around by simply rejecting the updated
device driver filesets:
devices.pci.14107d01.rte 4.3.3.25
devices.pci.14107d01.X11 4.3.3.25
Installing MLM-AIX via the Tivoli Framework incorrectly sets MLMs default
trap file to "/var/adm/smv2/collect/midmand.col" when it should be
"/var/adm/smv2/log/smtrap.log". This corrupts the midmand.col file with
traps. This problem only exists on MLM-AIX since the Tivoli Framework does
not do the complete install for the other MLM-UNIX platforms. To correctly
install MLM-AIX via the Tivoli Framework:
Click and hold down the right mouse button on the NetView server icon on
the Tivoli desktop to display the icon's pull-down menu.
Select "Administer MLMs"
Select "Install/Control the Mid-Level Manager (MLM) on a node
Scroll down until "Full path name of trap file" is displayed
Change the default trap file to: "/var/adm/smv2/log/smtrap.log"
Documentation Changes
In the Tivoli NetView for UNIX Administrator's Guide, Version 6.0, table 4
on page 69 incorrectly indicates that the default compound status for a
symbol is acknowledged when all of the symbols in its child submaps are in
an Acknowledged state. The table should state that the node will be normal
when all nodes in its child submaps are acknowledged. The acknowledged
state is not propagated and is ignored for upwards propagation.
The Tivoli NetView for UNIX V6.0 Release Notes, Appendix B, describes
procedures for changing the IP address and/or hostname in the Tivoli
Framework database. These instructions do not work in all cases. The
instructions should be changed to have the user consult the Tivoli
Framework documentation and/or Tivoli Customer Support for assistant.
Additional documentation for the netmon -a flag has been placed in the
netmon man page for this release.
Product Notes
Solstice Enterprise Agent (SEA) Issues
In order to fix SEA problems on Solaris 2.8, the following patch must be
installed on both the client and server machines:
108869-02 (Solaris 2.8 kernel patch)
The following problems may occur when the NetView server is on a machine
running Solaris 2.7 and SEA 1.0.3:
The NetView graphical user interface does not come up on the client system,
or the client cannot connect to the server. The error message "ERROR:
Cannot connect to server daemons" or "Cannot contact the mgragentd daemon
for daemon status. Make sure that the mgragentd daemon is running on the
server" may display on the client.
NetView server machines are not recognized as NetView managers (isManager
field is not set to TRUE). The NetViews SmartSet is not populated when this
occurs.
To fix these problems, install the latest versions of the following patches
on both the client and server machines:
106541-10 (Solaris 2.7 kernel patch)
107709-06 (SEA 1.0.3 patch)
Reboot your system after installing these patches.
If you have an MLM installed on the same machine as the NetView server,
then you must also make the following change to the midmand.acl file:
Change:
acl = {
{
communities = public, private
access = read-write
managers = *
}
}
to:
acl = {
{
communities = private
access = read-write
managers = *
}
{
communities = public
access = read-only
managers = *
}
}
Solaris 2.8 Support
On Solaris 2.8, a system directory is missing that is required by the
Tivoli NetView installation process. You must create the directory
/usr/lib/locale/en_US/LC_MESSAGES manually if it does not exist in order
for the installation to complete successfully.
AIX 4.1.5 Support
The NetView Web client, Web server, Seed File Editor, and Submap Explorer
are not supported on AIX 4.1.5 because JRE version 1.1.8 is not supported
on AIX 4.1.5.
AIX 4.3.3 Support
APM distribution may hang for AIX users when running bos.net.tcp.client at
the 4.3.3.10 code level. Applying bos.net.tcp.client 4.3.3.14 resolves this
issue.
Tivoli NetView Web Client
If you are running the NetView Web Client as a stand-alone application, you
will need to download and reinstall the Web Client code from the URL
http://host:8080/download, where host is the name of your Tivoli NetView
V6.0.2 server. For more information on configuring and running the NetView
Web Client as a stand-alone application, see the URL
http://host:8080/Running.html and the Tivoli NetView for UNIX Release
Notes, V6.0
Cisco Works 2000 Integration
Tivoli NetView V6.0 initiated support of the Cisco Works 2000 integration
model. This release ships with the necessary adapters in the directories
/3rdParty/Cisco/AIX and /3rdParty/Cisco/Solaris on the installation CD-ROM.
The README files in each of those directories provides directions for
performing the integration. More information about these procedures and the
overall integration model can be found on the Cisco Web site at
http://cisco.com/warp/customer/cc/cisco/mkt/enm/cw2000/tech/cwnms_tb.html
(CCO login is required).
NetView Language Kit Support
The following language upgrades have been made since the Tivoli NetView for
UNIX V6.0 release:
When the Tivoli NetView Web client Event Browser connects to a Unix Web
server:
Event dates and severities are translated
Filtering by severity and the graph feature work correctly
Applications, such as the SNMP Configuration window, that run on the
NetView server and are displayed on the client now translate correctly when
displayed on Solaris.
The initial window size of the Server Setup and Client Setup applications
has been increased and no longer displays as only a title bar.
Additional text strings were translated in the following applications:
Agent Policy Manager
SmartSet Editor
Event Display
Security Administration
If you are planning on installing the Tivoli NetView Language kit, it must
be installed prior to installing Tivoli NetView for UNIX V6.0.2. If the
language kit is installed after Tivoli NetView for UNIX V6.0.2, then Tivoli
NetView V6.0.2 must be reinstalled.
NetView Mailing List
A public mailing list named NV-L is maintained by the The Kernel Group for
the discussion of Tivoli NetView and related topics. The primary use of
this forum is for NetView users to exchange ideas and is not an official
customer support channel. Tivoli employees may respond if they wish, but no
one is required to do so. Customers who seek an official response from
IBM/Tivoli should call their local IBM/Tivoli support number. In the USA,
customers may use 1-800-Tivoli-8 for this purpose.
All routine administrative requests (including subscriptions and
unsubscriptions) concerning this mailing list are handled by an automated
server. Instructions for subscribing, unsubscribing, policies, posting,
digest version, and searchable archives are available at
http://www.tkg.com/nv-l.
This mailing list replaces the netview-users mailing list that was run by
The University of California at Santa Barbara and the previous one
maintained by Stanford University
Sincerely,
Ken Webster
Tivoli Certified
Manager, Tivoli Netview UNIX/NT Support
Tivoli Systems Inc.
|