Date: September 30, 2004
Name: 7.1.4-TIV-NVD-{OperatingSystem}-FP0002
Component: IBM Tivoli NetView Version 7.1.4
PTF Number: U800154 (UNIX) or XR23262 (Windows)
Note: Before using this information and the product it supports, read the information in the "Notices" section at the end of this document.
This section provides general information about this fix pack. It is strongly recommended that you read this entire document before you install this fix pack.
This fix pack consists of five packages, one each for RS6000 AIX(R), SUN SPARC Solaris, Linux Intel(TM), Linux 390, and Microsoft(R) Windows(R). You need to use the appropriate package on each platform on which an IBM(R) Tivoli(R) NetView (R)native server or client has been installed.
For Red Hat Enterprise Linux Advance Server 3.0 and SuSE Linux Enterprise Server (SLES) 9, a new CD has been added to the base NetView 7.1.4 kit and a standard IBM Tivoli NetView install is required.
This fix pack also contains a set of corrections for the NetView ETL code used by and contained within the Tivoli Data Warehouse. In order to apply the corrections to the NetView ETL code within the Tivoli Data Warehouse, see the 1.1.0-anm-fp02.readme file associated with this fix pack.
None.
Because IBM Tivoli NetView does not produce patches, there are no patches superseded by this fix pack. However, all test fixes for IBM Tivoli NetView 7.1.4 that are covered in the APARs corrected in this fix pack section of this readme are superseded.
Please note that the following operating systems are not supported in this release:
The following items are new in IBM Tivoli NetView Fix Pack 02.
For Red Hat Enterprise Linux Advance Server 3.0 and SuSE Linux Enterprise Server (SLES) 9, if the firewall is turned on, SNMP traps do not pass through. Moreover, the firewall is turned on by default. Therefore, in order for IBM Tivoli NetView to receive traps from external agents, the firewall must be turned off.
IBM Tivoli NetView provides support for monitoring the Cisco PIX firewall failover conditions. NetView can monitor the failover state of the PIX devices during normal status polling. When a failover occurs, a new event is generated announcing whether the active addresses are on the primary or secondary device. In addition the operator can see on the map when the Active addresses are on the Secondary device indicating a failover has occurred and action should be taken to prevent a further failure disabling the firewalls. The management interface shows USER2 status which is usually purple (by default). This propagates to change the PIX device symbol to marginal. When the Active addresses are returned to the Primary device, an event announces this fact and the status on the map returns to Normal.
Use the netmon.seed file for configuration for both the PIX Firewall failover machines and to set and lock the SNMP address.
For more information on the PIX firewall failover support see the /usr/OV/doc/PixFailoverReadme.pdf file.
A new capability now allows a NetView administrator to set and lock the SNMP address for any device.
For more information, see the A modified netmon.seed file section.
Two new tokens in the seed file are now recognized by netmon.
PIX Firewalls typically swap interfaces between the primary and secondary units on failover. In addition, SNMP access is generally restricted, but access via one address is required. IBM Tivoli NetView monitors the PIX machines for failover. For more information see the document, /usr/OV/docs/PixFailoverReadme.pdf.
Use the prefix '>' followed by the IP address of each machine accessible for SNMP. Wildcards and ranges are permitted, but host names are not. Below is an example:
>172.30.100.2
>172.30.100.3
This token automatically enables netmon to poll the Cisco MIB for failover, sets and locks the SNMP address, and enables SNMP status polling for this node.
By default IBM Tivoli NetView attempts to change the SNMP address for a node when that interface is known to be down. However, it would be useful to override this behavior for certain nodes.
Use the prefix '=' followed by the IP address that should be set and locked for SNMP queries. Wildcards and ranges are permitted but host names are not.
This token is used to set the SNMP address and lock it so that IBM Tivoli NetView will not attempt to change the SNMP address.
When IBM Tivoli Switch Analyzer (ITSA) is installed with IBM Tivoli NetView, it correlates outages to a layer 2 root cause. When the root cause is a switch, NetView changes the icon color for the switch to yellow, to indicate a layer 2 problem with the ports. The new Layer2Status object provides a visualization of the layer 2 status by representing it as a new interface object under the switch. The default label for this new object is "Layer2Status," and the selection name is "<switchhostname>:Layer2Status." The status of the switch icon is based on the standard propagation schemes of the IP interface and the new Layer2Status object, with the caveat that the IP status takes precedence when it is more severe.
ITSA is responsible for setting the ovwdb field "Layer2Status" on the switch when there is a correlated problem and ITSA resets the status when the problem is resolved. The status of the new Layer2Status object reflects the value in the "Layer2Status" field. When this status changes to Marginal, netmon issues an "Interface Layer2Status marginal" event. This event has the same specific ID as the Interface Down event. When the layer 2 status returns to Normal, the standard interface event, "Interface UP," is sent for the Layer2Status object.
The existing Layer2Status events for the switch node continue to be sent and are used by ipmap. The new Layer2Status object fields can be seen using ovobjprint.
The following messages appear in the event browser when new Layer2Status objects are created.
Note: The <switch name> message is displayed for each switch.
The ovtopodump -r command has been modified to only list each interface for a given node once. For a node with more than one interface on the same network, it used to print all the interfaces for every node.
Three changes have been implemented to provide better management of user accounts.
Before, the only way to change user passwords was by running the Web Console Security application on the NetView server or by having a NetView administrator edit /usr/OV/www/conf/NetViewRealm.properties with a text editor. Now, users can reset their own passwords.
New files have been created to support password expiration.
Below are instructions for using the new Web Console Security features.
As part of IBM Tivoli NetView Fix Pack 02 installation, a new file, NetViewRealm.xml, gets created. Initially, NetViewRealm.xml will be set up so that passwords never expire.
<NetViewRealm validFor="-1"/>
In this case, passwords never expire. When the value of the "validFor=" attribute is -1, NetViewRealm should be an empty element.
To re-enable the change password feature when the current value for the "validFor=" attribute is -1, a NetView administrator needs to either:
Note: Once generateNetViewRealmXML has been run, all the user accounts will be set to expire at the same time based on the "validFor=" attribute. Users are warned in advance to change their passwords. If users do not change their passwords, their user accounts will be deleted. See the Logging on after the password has expired section for more details.
The NetviewRealm.xml file contains attributes related to user account password expiration. The attributes are as follows:
Below is an example of an NetViewRealm.xml file with user accounts.
<NetViewRealm validFor="186" expireWarning="21" dateFormat="yyyyMMdd"> <Account name="jane" since="20040701"/> <Account name="john" since="20040701"/> <Account name="maria" since="20040701"/> " ... </NetViewRealm>
To add new Web Console user accounts and to keep the NetViewRealm files synchronized, use one of the following methods:
This method will pick up the current general password expiration settings from the NetViewRealm.xml for the new users. For details on how to modify the general password expiration settings, see the Editing NetViewRealm.xml section.
When NetView administrators need to add lots of users, manually editing the NetViewRealm.properties is simpler than using Web Console Security.
After updating the NetViewRealm.properties file, instead of manually adding corresponding updates to the NetViewRealm.xml file, an administrator can just add (or remove) Web Console Security user account information to the NetViewRealm.properties file and then run generateNetViewRealmXML to update the NetViewRealm.xml file.
Note: After adding users to the NetViewRealm.properties file, the NetView administrator should bring up Web Consle Security and specify to save updates. As before, this will encrypt the passwords of any users which were manually added.
Note: Always recycle the Web Server after adding/deleting Web Console user accounts.
A new button was added to the NetView Web Console log on screen:
This new button enables users to change their passwords when they log on to the NetView Web Console.
After entering their username and password in the Web Console log on screen, they can click Change Password.
An authentication check request is sent to server. The cursor changes to an hour-glass until a response is received.
If authentication succeeds, the log on dialog closes. Next the user should follow the steps under "Changing the Password."
If the passwords do not match, the user gets the error message, "The passwords do not match." Both password fields are cleared. Focus moves to the first password field. At this point, the user should try again.
In either case, focus moves to the OK button. The OK button is the default button.
The password change request is sent to the Web Server. The cursor changes to an hour-glass until a response is received. If the password change succeeds, the log on dialog is closed and the Web Console is started.
A user's new password cannot be the same as the old password.
Possible errors:
A dialog appears with error message "Password file is busy. Try again?" and two buttons Yes and No. The Yes button is the default.
If the user presses the Enter key or clicks Yes, the Error dialog is closed. Repeat this step (resend password change request).
If the user clicks No, the Error dialog is closed. The log on dialog is closed and the Web Console is started.
A dialog appears with the error message "Realm property file access time-out. Please try again later." The one button, the OK button, is enabled. If the user presses the Enter key or clicks OK, the Error dialog is closed. Repeat the change password step to resend the password change request. If the user gets this error message after several tries, the administrator might be using Web Console security. Web Console security locks the password files and the user is unable to change the password while the files are locked. The user should press the button to close the Change Password dialog and start the Web Console. The user should contact the Administrator about the access timeout.
Immediately after successfully logging on, before the log on dialog is closed, the user is notified that the password is about to expire and prompted to change it. The new password takes effect immediately.
If a user's password has expired, the user cannot log on to the Web Console and must contact the NetView administrator for a new password.
The NetView administrator must use Web Console Security to reset the user's password and/or to restore the user's account if the daily task which removes accounts with expired passwords (from NetViewRealm.properties) has removed the account.
This daily task removes accounts with expired passwords and logs information about the removed accounts in ${jetty.home}/logs/expiredpasswords.log. A NetView administrator can use this information to reinstate the accounts.
A NetView administrator can manually edit the NetViewRealm.xml file to update the various attributes related to password expiration.
Once password expiration has been enabled (see the Initializing Web Console Security settings section), a NetView administrator can disable it again by setting the value of the "validFor=" attribute in NetViewRealm.xml to -1 and running generateNetViewRealmXML. In this case, generateNetViewRealmXML deletes all the Account name entries leaving NetViewRealm as an empty element.
A NetView administrator can change the length of time passwords are valid by changing the value of the "validFor=" attribute in NetViewRealm.xml.
To change when users are notified that their passwords are about to expire, change the value of the "expireWarning=" attribute. The default value is 21 days. In other words, when users log on within three weeks of their expiration date, they get a "Your password will expire in 21 [20, ...] days. Do you want to change it now?" dialog.
The NetView administrator should only change the values of the "expireWarning=" and "validFor=" attributes. Administrators should not change the Account elements.
<NetViewRealm validFor="30" expireWarning="7" dateFormat="yyyyMMdd"> <Account name="jane" since="20040701"/> <Account name="john" since="20040628"/> <Account name="maria" since="20040627"/> ... </NetViewRealm>
In this case, the maximum password age is 30 days. If today is July 28, 2004, Jane must change her password on or before July 31. When Jane signs on to the Web Console today, she is told that her password will expire in 3 days and asked if she wants to change it. John must change his password today. When John signs on to the Web Console today, he is told that his password will expire today and asked if he wants to change it. There is a chance his password may expire while he is using the Web Console. Since Maria's password has already expired, she has to get a NetView administrator to change her password for her. Actually, most likely, Maria's account will already have been removed from the file by the daily expired password removal task.
Note: The "since=" attribute is the date the password was last changed. This allows the administrator to change the value of the "validFor=" attribute without needing to recalculate the "since=" attribute values.
Note: After editing NetViewRealm files, run generateNetViewRealmXML and recycle the Web Server.
The Global Acknowledge/Unacknowledge function in IBM Tivoli NetView for UNIX now works for user-created non-IP map objects.
On both UNIX and Windows, it is now possible to acknowledge map objects whose object status is Normal.
The trapd daemon on Windows can now receive external SNMPv2 traps. Incoming SNMPv2 traps are translated to their SNMPv1 equivalent. trapd also acknowledges SNMPV2 INFORMs.
To receive SNMPv2 traps, trapd must be reconfigured to listen for traps on the incoming trap port (usually 162) directly. It cannot receive SNMPv2 traps through the Microsoft(R) Windows Trap Service. To configure trapd to listen for traps on port 162:
> ovstop > nvservice -stop
HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\NetView\CurrentVersion\trapdSharePort162
HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\NetView\CurrentVersion\trapdTrapReceptionPort
> net stop snmptrap
> nvservice -remove > nvservice -install -username .\NetView -password <password>
Note that incoming SNMPv2 traps that contain 64-bit values are dropped from the translated SNMPv1 traps. If tracing is enabled for trapd, the dropped value is logged to the trace file.
The nvmaputil manage-interface/unmanage-interface subcommands now accepts either an IP address or a selection name. If the IP address is used and it is either not found or there are multiple objects with same IP address, nvmaputil exits and suggest that the user enter the selection name.
Note: AutoTrace exists only on UNIX.
A new script, /usr/OV/service/nvAT has been created to control the function of the AutoTrace subsystem without requiring a system reboot. This scripts incorporates the steps outlined in previous release notes for controlling AutoTrace.
Usage statement:
Usage: nvAT [start|status|stop]
nvAT [/h | /?]
start : Initialize the AutoTrace subsystem and start the NetView channel
status : Display the status of the AutoTrace subsystem
stop : Stop the NetView channel and the AutoTrace subsystem
/h : Help
/? : This usage statement
The modified Web Console Switch Management Views show the VLAN on which every port is located. This is done through community string indexing. This entails using the community string <community name>@<port number> where <community name> is the community string for the device and <port number> is the VLAN port number from the switch's VLAN table.
These changes apply only to switches that support the Cisco BRIDGE_MIB, in effect, Cisco Catalyst switches. Others switches are displayed without VLAN information.
Cisco lists the following as providing support:
See: http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a008015773e.shtml
Displaying VLAN information:
Limitations in this implementation:
When configuring a NetView client using the Add/Change Server option in the Server Setup tool, ICMP echo request (ping) is used to test the connection to the proposed NetView server. In past releases, if the ping did not give a valid response, then NetView assumed that the chosen NetView server machine was either invalid or unreachable and did not allow the client to be configured using that server. Now, if the ping fails, the Server Setup tool will display a warning and continue configuration.
In the Server Setup tool, the option Maintain -> Clear databases -> Clear object/topology/map databases, remove customizations now re-creates the default SmartSets. In previous releases of IBM Tivoli NetView, the default SmartSets were removed by this option.
A new script, /usr/OV/service/nvPerms, has been shipped that restricts the permissions on the IBM Tivoli NetView files and directories in order to tighten security. Users can type
man nvPermsonce the fix pack has been installed to get additional information.
nvPerm script simply resets the permissions on the Tivoli NetView files and directories so that:
Note: nvPerms can not be used in the NetView native client/server environment.
APAR IY53703 introduces a new environment variable for use by trapd to help the user better control the formatting of variables containing hexadecimal data in strings. Currently, trapd tries to interpret this data as printable, in order to make the output in trapd.log and the event windows as readable as possible, unless over half the string contains unprintable characters. However sometimes users know that the entire string should be printed as hexadecimal data, such as when it is really a MAC address. Users who wish to have trapd more strictly interpret hexadecimal data, and dump an entire string to hexadecimal unless all of it is printable, should set the TRAPD_STRICT_HEX_FORMAT environment variable in order for this to happen.
On UNIX, create a /usr/OV/bin/netnmrc.pre file with the following line, or add the line to an existing file of that name:
export TRAPD_STRICT_HEX_FORMAT=TRUE
Then all the daemons must be restarted so that they inherit this variable. Either reboot the NetView machine or use "ovstop nvsecd" to stop all the daemons. Then use "/etc/netnmrc" (AIX) or "/etc/init.d/netnmrc" (Solaris or Linux) to enable this change.
On Windows, set the environment variable using the control panel:
Control Panel --> System Environment --> Advanced --> Environment Variables System --> Add Variable Name Value TRAPD_STRICT_HEX_FORMAT TRUE
Then reboot the NetView machine in order to enable the change.
Due to APAR IY56563, a new option, "Add collected data to the NetView Warehouse?," was added to the UNIX snmpCollect daemon options in serversetup.
This new option is "yes" by default. Specifying this option as "yes" causes the snmpCollect daemon to be started with the -w option that enables adding collected data to the NetView Warehouse. Specifying this option as "no" disables adding collected data to the NetView Warehouse.
Note: This new option does not show up in the UNIX smit path to setting options for the snmpCollect daemon in this fix pack, only in the serversetup path. The workaround is to use serversetup instead of smit.
As part of APAR IY58514, the following two snmpCollect commands were added:
Disconnects snmpCollect from the NetView Tivoli Data Warehouse database, but allows snmpCollect to continue to run. It is not available on zLinux.
Causes snmpCollect to connect to the NetView Tivoli Data Warehouse database without having to recycle snmpCollect. It is not available on zLinux.
For UNIX, a new trapd.conf file is shipped with this fix pack. Changes to trapd.conf fix problems related to APAR IY57432 with sending interface lists to the Tivoli Enterprise Console on events, as well problems on Linux related to APAR IY52871 with launching the MIB browser from the Events Window on Linux.
If trapd.conf in /usr/OV/conf/C (not the obsolete trapd.conf file in /usr/OV/conf) has not been customized, simply replace it with the new trapd.conf from /usr/OV/newconfig/OVSNMP-RUN. If, however, the original trapd.conf has been modified, manually add the changes into the original file. For details, see the sections on Sending interface lists to the Tivoli Enterprise Console on events and Changes to trapd.conf for launching the MIB browser.
Note: See the New in Fix Pack 01 section for information on the Windows trapd.conf file.
As mentioned in the A new trapd.conf file section above, the new trapd.conf shipped with this fix pack fixes the problem described by APAR IY52871 with launching the MIB browser from the Events Window on Linux.
If the original trapd.conf has been modified, manually add the changes in the new trapd.conf into the original trapd.conf file. Otherwise, simply use the new trapd.conf.
The suggested method is to use xnmtrap to edit the trapd.conf file because doing so causes trapd to automatically reload it when you are finished. You must make the edit as root.
/usr/OV/bin/xnmbrowser -node "`awk '{if (NR==1)print $10}'`
to this:
/usr/OV/bin/xnmbrowser -node "`awk '{if (NR==1)print $10}'` "
Note that you may make this change using another editor also. Locate the line that reads:
ACTION 0 "Browse MIB" /usr/OV/bin/xnmbrowser -node "`awk '{if (NR==1)print $10}'`
and change it to this:
ACTION 0 "Browse MIB" /usr/OV/bin/xnmbrowser -node "`awk '{if (NR==1)print $10}'` "
Then save the file. Then you must either restart trapd or issue the command "/usr/OV/bin/event -e FMTCHG" to cause it to re-read the file.
APAR PJ29821 (Windows) and IY57432 (UNIX) deal with certain events failing to parse correctly when sent to the Tivoli Enterprise Console(R). The reason for this is that, in certain environments, some nodes and routers have so many interfaces (in excess of 30), that the interface list, sent as varbind 8, is too large for the Tivoli Enterprise Console to parse correctly. This problem is addressed by no longer sending the interface list to the Tivoli Enterprise Console, as part of those events.
In IBM Tivoli NetView for UNIX, this is controlled by the slot map entries in trapd.conf. The fix for UNIX will ship a new trapd.conf (in /usr/OV/newconfig/OVSNMP-RUN) but this will not automatically replace the customized one that the user currently has installed in /usr/OV/conf/C/trapd.conf. Therefore, users should make this modification manually on their current systems (or if trapd.conf has not been customized, simply replace the current one with the new one).
Using xnmtrap, modify each of the following entries in trapd.conf, first clicking the T/EC Slot Map. Then in the window that pops up, select the "iflist" entry and click Delete. Then click OK for each, and "OK" again to complete the edit for that trap. Continue until you are finished. Then press "OK" to finally exit xnmtrap.
IBM_NVNM_EV 50790400 (Node Marginal)
IBM_NVNUP_EV 58916864 (Node Up)
IBM_NVNDWN_EV 58916865 (Node Down)
ROUTDOWN_EV 58916971 (Router Down)
ROUTUNREACH_EV 58916972 (Router Unreachable)
ROUTERUP_EV 58916973 (Router Up)
ROUTMARG_EV 58916974 (Router Marginal)
In IBM Tivoli NetView for Windows, this is controlled by the entries in the file \usr\ov\conf\tecad_nv6k.cds. The fix for Windows will ship a new tecad_nv6k.cds, but in \usr\ov\newconfig\tecad. This new file will not replace the customized file that the user has in \usr\ov\conf\tecad_nv6k.cds. Therefore, in order to avoid the problem, users should make this modification manually on their current systems.
In the \usr\ov\conf\tecad_nv6k.cds file, locate the entries for each of the following traps:
Under the SELECT statement, remove the line that reads:
6: ATTR(=, "VB_8") ;
Under the MAP statement, remove the line that reads
iflist = $V6 ;
For example, the Node Up entry as shipped looks like this:
CLASS TEC_ITS_NODE_STATUS
SELECT
1: ATTR(=,$ENTERPRISE) , VALUE(PREFIX, "1.3.6.1.4.1.2.6.3" ) ;
2: $SPECIFIC = 58916864 ;
3: ATTR(=, "nvObject" ) ;
4: ATTR(=, "nvEventDescr" ) ;
5: ATTR(=, "nvApplNbr" ) ;
6: ATTR(=, "VB_8") ;
FETCH
1: IPADDR($V3);
MAP
origin = $F1 ;
hostname = $V3 ;
msg = $V4 ;
category = $V5 ;
nodestatus = 1 ; # UP
iflist = $V6 ;
nvhostname = $ADAPTER_IP ; # Required for ALL TEC_ITS events
END
The user will want to make it look like this:
CLASS TEC_ITS_NODE_STATUS
SELECT
1: ATTR(=,$ENTERPRISE) , VALUE(PREFIX, "1.3.6.1.4.1.2.6.3" ) ;
2: $SPECIFIC = 58916864 ;
3: ATTR(=, "nvObject" ) ;
4: ATTR(=, "nvEventDescr" ) ;
5: ATTR(=, "nvApplNbr" ) ;
FETCH
1: IPADDR($V3);
MAP
origin = $F1 ;
hostname = $V3 ;
msg = $V4 ;
category = $V5 ;
nodestatus = 1 ; # UP
nvhostname = $ADAPTER_IP ; # Required for ALL TEC_ITS events
END
IBM Tivoli NetView for Windows users can implement the new rule set, overridestatus_user1.rs, which replaces the broken rule set, setstatusseverity.rs. A new document, \usr\ov\doc\Rulesets_on_Windows.readme, documents the rule set samples for use with the correlation daemon, nvcord. setstatusseverity.rs should be deleted by the user. It will not be shipped in future releases.
The three new options listed below have been added to the xnmsnmpconf command. Note: The characters in brackets ([]) are optional.
Removes all entries from the SNMP configuration nodedb files (nodedb.dir and nodedb.pag) that contain entries for specific nodes.
Removes all entries from the SNMP configuration wilddb files (wilddb.dir and wilddb.pag) that contain entries for IP address wildcards.
Removes all entries from the SNMP configuration colldb files (colldb.dir and colldb.pag) that contain entries for SmartSets.
Note: The SNMP configuration files are in the /usr/OV/conf/ovsnmp.conf_db directory.
With the three new options and the previously existing "xnmsnmpconf -clearCache," this now means the SNMP configuration database can be entirely cleared out by following the steps below.
Note: Prior to clearing out the SNMP configuration database, save/make note of any xnmsnmpconf customizations (such as the default community name, IP Address Wildcards.) After clearing out the SNMP configuration database, restore these customizations using either the xnmsnmpconf -import command or the xnmsnmpconf GUI.
In conjunction with APARs IY56279 and IY60528, three new options have been added to the tecint.conf file on UNIX to control the behavior of the internal Tivoli Enterprise Console adapter in nvserverd. By default these options are commented out, but the user may uncomment them by removing the pound sign (#) that precedes them in order to alter nvserverd behavior as described below. A new man page for tecint.conf has been provided to document these options.
When set to 'Yes' or "YES', this flag causes nvserverd to create the /usr/OV/log/nvserverd.log of events being sent to the Tivoli Enterprise Console. Also recorded here are startup parameters of the internal adapter itself as well as error messages concerning the internal adapter should any be recorded. This error information was previously only available in the nettl logs. Using this flag in the tecint.conf file removes the need to export an environment variable, NVSERVERD_TRACE_TEC_EVENTS=YES, in /usr/OV/bin/netnmrc.pre to control the logging function. Moreover, it overrides that variable if present. If the "NvserverdTraceTecEvents=" flag is not present in the tecint.conf file or if it is commented out, the default behavior is that no nvserverd.log is created.
When set to 'No' or "NO', this flag causes nvserverd to open a session with the correlation daemon, nvcorrd, requesting not to be primed with recent events, as event windows are. The default behavior is that the Tivoli Enterprise Console rule set is primed. Priming it increases the probability that duplicate events will be sent to the Tivoli Enterprise Console when nvserverd is stopped and restarted while nvcorrd remains active. Using this entry removes the need to export an environment variable, NVSERVERD_PRIME_TEC_EVENTS=NO, in /usr/OV/bin/netnmrc.pre to control the priming function. Moreover, it overrides that variable if present.
When set to 'Yes' or "YES', this flag causes nvserverd to revert to its pre-NetView 7.1.4 behavior and to send the user-configurable NetView severity on events sent to the Tivoli Enterprise Console. Event severity was dropped in 7.1.4 originally because it interfered with the working of new Tivoli Enterprise Console rules shipped in IBM Tivoli Enterprise Console Version 3.9 (and in FixPacks for versions 3.8 and 3.7.1). These new Tivoli Enterprise Console rules automatically set the event severity of NetView internal events upon receipt at the Tivoli Enterprise Console server, and escalated it or de-escalated it based on event correlation and time open at the Tivoli Enterprise Console server. However, many users are not ready to migrate to using these new rules and require that NetView severity still be sent in order for their own custom rules to work. The new "NvserverdSendSeverityTecEvents=" flag is therefore provided as a migration aid. Using this entry removes the need to export an environment variable, NVSERVERD_SEND_SEVERITY_TEC_EVENTS=YES, in /usr/OV/bin/netnmrc.pre to control the sending of severity. Moreover, it overrides that variable if present. If the "NvserverdSendSeverityTecEvents=" flag is not present in the tecint.conf file, or if it is commented out, the default behavior is that no severity field is sent on default events. Explicitly coded severity in a slotmap field is not affected by this changes.
The following items were new in IBM Tivoli NetView Fix Pack 01.
APAR IY48379 described a problem where the ovstop command does not always stop the tdwdaemon. A modified tdwdaemon.lrf was created and included in this fix pack that corrects the problem. To install this correction on a UNIX platform, the tdwdaemon.lrf file in the installation must be replaced using the following steps:
To back this correction out, follow the above directions, replacing the two copy steps with a single copy of the saved lrf file back to its original location.
The location sensitive topology functionality (location.conf) has been enhanced to allow IP address ranges and wild cards in gateway entries. Ranges or wild cards may be used in any part of the gateway IP address. Wild cards may not be used in a gateway name.
The following change (which should be applied to the comment section of the location.conf file manually) describes the changes to the gateway name or address field:
The format of a gateway entry is:
<location name> <gateway name or address>
where location name is the name of the location under which this gateway should be placed, and gateway name or address is the name of the gateway or the IP address of one of its interfaces in dotted-decimal notation. Wild cards and ranges are allowed in gateway IP addresses (meaning, 5.25-30.2.8 or 3.5.*.*). Wild cards are not allowed in gateway names (myrouter.company.com).
Example gateway entries:
If a gateway matches more than one gateway entry, one entry is arbitrarily chosen. To help in resolving overlapping gateway entries, warning messages about gateway interfaces that match more than one entry are displayed in the location.log file. These are only warning messages; they do not indicate any problem with the gateway/router placement.
A modified netmon.seed file for APAR IY47145 is shipped with this fix pack. This file documents that in order to explicitly discover a node and make it SNMP-managed there must be two entries in the netmon.seed file: one to discover the node and the second for SNMP management. This fix pack places the modified netmon.seed file in the /usr/OV/newconfig/IBMVA-RUN/ subdirectory on UNIX, and the \usr\ov\newconfig\netmon subdirectory on Windows.
By default, up to seven alternate community names can be specified in communityNames.conf file. You can modify the maximum number of alternative community names allowed by setting the environment variable MaximumCommunityNames in the netmon.conf file to a value between 0 and 100.
A new trapd.conf file is shipped with this fix pack. This trapd.conf file no longer accidentally truncates several values in the HPCIFxxx traps in the trapd.conf file for NetView for Windows. This file can be found in \usr\ov\newconfig\ovsnmp-run\trapd.conf. If you want to use this file and you have not customized \usr\ov\conf\trapd.conf, you can use it to replace the one found in \usr\ov\conf\trapd.conf. If, however, the original file has been modified, you must merge the two files.
If you are having trouble finding services when using servmon to do ITM queries, you may need to enable secondary IP address retrieval for servmon initialization.
Enable secondary IP address retrieval for servmon during servmon initialization by adding a line in servmon.conf consisting of just SECONDARY_IPADDRS. By default, secondary IP addresses are not retrieved during servmon initialization.
However, enabling this function is very performance intensive. It would be best to allow NetView to stabilize before making the change. Then, once NetView is running, complete the following:
Since NetView for UNIX Version 5.1, the Action node rule set has added three additional variables to the end of every trap passing through it (in order):
In NetView 6.0.3, a new variable, NVATTR_COUNT was added to tell the user how many variables the trap now contains, and it permitted easier reference of these last three:
These additional varbinds are now exported into three, easy to reference variables:
mib2trap mib_file addtrap_output_file [baroc_file] [base_event_class_name]
If you want to continue using the old base class, Nvserverd_Event, you can do so by specifying it as the fourth (optional) parameter, in the following way because the command now supports any user-defined base event class:
mib2trap mib_file addtrap_output_file baroc_file Nvserverd_Event
The origin field of an event sent to Tivoli Enterprise Console by the internal Tivoli Enterprise Console adapter in nvserverd always contains the IP address of the NetView server. The adapter_host field contains either the fully qualified domain name of the NetView server or the same IP address as the origin field. Short names can no longer be used for the adapter host field in order to facilitate event responses and forwarding at the Tivoli Enterprise Console server.
The Java MIB Loader no longer puts MIBs that failed to load into the list of loaded MIBs. It also now warns you if loading a MIB is skipped and reminds you that, for the Java MIB loader, the only valid extensions for MIB files are .mib, .my, and .def.
The file installed on Solaris as /etc/snmp/conf/mgragentd.rsrc has been changed so that the command field reads just 'command = "" ' (a null command entry) from its former value, 'command = /usr/bin/echo mgragentd registered with snmpdx'. The purpose of this change is to avoid any possibility of a defunct process being created when snmpdx is restarted. However, the file is only installed once, on the initial installation of NetView, and the current copy on your system is not updated by this fix pack. Therefore, if you wish to have this change before the next release, you must manually insert this change into the /etc/snmp/conf/mgragentd.rsrc file.
As of NetView V7.1.2, the Tivoli Enterprise Console class definitions used by NetView were upgraded. The previous Tivoli Enterprise Console Event class definitions used by NetView are no longer supported, and you are expected to use the new class definitions because future migration will not support the old class definitions.
Depending on your system configuration and level of operating system, you may need to upgrade to a newer version of the JRE once a NetView V7.1.4 Fix Pack is installed. If the NetView Web Console causes a core dump after a fix pack has been installed, you can request the JRE upgrade from IBM Tivoli Customer Support by asking for fix IY45265 for the appropriate platforms and installing it on your systems.
If the snmpCollect daemon is deferring more collections than seem appropriate, the problem may be because the default wait time of 3 seconds may not be enough time for the snmpCollect daemon to receive the reply.
To allow more time for collections, do the following:
When NetView security is enabled, the Tivoli NetView server's fully qualified host name must appear as the first host name for the server's entry in the server's /etc/hosts file. Otherwise, the NetView client's credentials cannot be verified, and when a message is sent from the server in the Security Administration dialogue, Error(35) is reported.
When using a Tivoli NetView native server/client configuration on UNIX, the native NetView client must be stopped and restarted if the platform on which the NetView server resides is rebooted. The reboot and subsequent restart of the NetView server causes the loss of session information regarding the native client, and the client must be stopped and restarted to restore that information.
The wildcard range in the seed file limits the discovery to be in the range for all managed networks. It does not force netmon to discover any new node in that range, and it does not force netmon to create a new network. However, for the seeded entry (single IP or host name), netmon always attempts to discover the entry and to create a network if it is needed.
To enforce the discovery of an "island-network" (that is, a network with no router connection to NetView server), you must add one explicit (seeded) node entry in that network into the seed file to force the node discovery and network creation. In addition, to expand discovery on other devices in that network, you must ensure the seeded entry is SNMP enabled.
In the SNMP Configuration Panel of the xnmsnmpconf application, the field Retry Count indicates the total attempts on a ping or SNMP request. The count includes the initial poll, so a value of "1" indicates one attempt should be made, a value of "2" indicates an initial attempt and one retry if it fails, etc.
If the daily Web Server log files are taking up too much space on your system, in addition to lowering the number of days that these request logs are retained (as described in detail in the IBM Tivoli NetView 7.1.4 for UNIX Release Notes), there are several additional actions you can take:
The Query Interval determines how often Web Consoles send a request to check whether the Web Server is still alive.
Normally, there is no need to customize this parameter. However, if the daily servlet request logs (yyyy_mm_dd.request.log in /usr/OV/www/logs for UNIX or in \usr\ov\www\logs for Windows) are routinely much too large, you can increase the Query Interval so that fewer EventChannel query log entries are created. However, this change also increases the lag time before Web Consoles realize that the Web Server has gone down.
This can be configured in the queryIntervalSec parameter for the EventChannel Servlet in the /usr/OV/www/webapps/netview/WEB-INF/web.xml file for UNIX or in the \usr\ov\www\webapps\netview\WEB-INF\web.xml file for Windows.
The Client Refresh rate determines how often Web Consoles ask the Web Server to refresh the events for the Web Consoles' event browsers.
Normally, there is no need to customize this parameter. However, if the daily servlet request logs (yyyy_mm_dd.request.log in /usr/OV/www/logs for UNIX or in \usr\ov\www\logs for Windows) are routinely much too large, you can increase the Client Refresh rate so that fewer EventBrowser event request log entries are created. However, this change also decreases the frequency with which the EventBrowser data is updated in the Web Consoles.
This can be configured in the clientRefreshRate parameter for the EventBrowser Servlet in the /usr/OV/www/webapps/netview/WEB-INF/web.xml file for UNIX or in the \usr\ov\www\webapps\netview\WEB-INF\web.xml file for Windows.
Both of these actions, as well as lowering the number of days the logs are retained, can be performed on a NetView Web Server running on either a UNIX platform or a Windows platform.
IBM Tivoli NetView 7.1.4 requires the latest Tivoli Enterprise Console releases (3.8 + Fix Pack 01, 3.9) if Tivoli Enterprise Console-forwarding is enabled. This is due to changes in the trap parameters sent from NetView to Tivoli Enterprise Console, which is only known to the latest Tivoli Enterprise Console releases.
When configuring a client/server system for the first time on the Solaris operating system, you might see an error message during the "Add Client Access" stage that says:
!-> error message "Can't open /etc/dfs/sharetab" (3 times)-> Operation completed
This is because the file /etc/dfs/sharetab does not exist on Solaris until created. The client setup creates the file after failing to access it, so the error messages does not indicate failure.
The Security Audit Configuration dialog box has two panes.
The upper pane contains the Select Audit Categories field. Use the On and Off buttons in this field to select the categories of audit records that should be stored. Refer to the IBM Tivoli NetView for UNIX Administrator's Guide for information about the events recorded under each category.
The lower pane contains the following fields, which can be used to control the size and location of audit log files:
Neither the NetView UNIX or Windows Administrator's guides nor the comments in itm_attributes.conf and servmon.conf nor the comments in the man pages for servmon correctly and clearly explain how and when servmon creates Service SmartSets.
The servmon daemon does not automatically create Service SmartSets for service attribute entries (see both itm_attributes.conf and servmon.conf). If you would like to have a Service SmartSet, you should add an entry to servmon.conf for that service (or uncomment the commented-out line, if there is already one for that service, making any necessary changes). See servmon.conf for details. Then stop and restart the servmon daemon to pick up the changes.
Alternatively, you can manually create the SmartSet on your own. For Windows, the status for nodes under the SmartSet submap depends only upon the service status. However, for User SmartSets, the status for nodes depends upon both the IP status and the service status. For UNIX, while Service SmartSets are supported, service icons are not created and the service status does not contribute to the overall status of a node.
Additional Notes on servmon:
The following customer-reported problems are addressed in IBM Tivoli NetView V7.1.4 by this fix pack:
| APAR # | Platform | Description |
|---|---|---|
| IY49659 | UNIX |
For AIX 5.1, commands launched by ovactiond are not killed when wait time is exceeded. |
| IY50486 | Windows UNIX |
IBM Tivoli NetView's DB2 Availability Database has duplicate records (see IY53390 and IY55671). |
| IY51398 | Windows UNIX |
nvdbformat performance improvement |
| IY52871 | UNIX |
IBM Tivoli NetView's events application additional actions of browse mib and sorting events all fail with shared library load errors. |
| IY53390 | Windows UNIX |
ETL1 inserting availability data into TWH_CDW results in duplication of node (comp_id) and measurement values pairs. |
| IY53554 | UNIX |
The mibtable command gets stuck looping while attempting to retrieve status tables from the MLM MIBs. |
| IY53580 | UNIX |
APM data collection is returning the same value over and over again. |
| IY53703 | Windows UNIX |
trapd does not format hexadecimal data in traps as expected. |
| IY54430 | UNIX |
netviewd fails to start. The message in the ovstatus output stanza is "Exiting for unknown reason." The work around for this is documented in this fix pack. |
| IY54434 | Windows UNIX |
For complex SmartSets, the nvUtil evaluation command did not always yield the correct results, especially if the right-hand side of the rule ended with a NOT operator (for example, !(xxxx)) and had multiple && conditions. |
| IY54452 | UNIX |
Backup the /usr/OV/ITSL2 file during NetView migration. |
| IY54575 | UNIX |
On Linux, nvcorrd cores when delete [] is called for an array that was not dynamically allocated. |
| IY54590 | UNIX |
ovtopofix should delete empty networks. |
| IY55011 | UNIX |
nvUtil exits when it comes across an object with no Selection Name in the list of objects retrieved from the ovw database, issuing the following message: "GetValues failed - OVwDbGetFieldValuesByObjects returned NULL values. Verify that the ovwdb cache size is greater than the number of objects in the database." |
| IY55025 | UNIX |
The netview_root.log file gets filled with font errors on AIX 5.2 because the "/usr/OV/app-defaults" directory contains imb850 fonts, which are not supported with LANG=en_US. |
| IY55219 | Windows UNIX |
netmon cores on Solaris if DEMANDPOLL and PING STATUS POLL hit at the same time. |
| IY55256 | UNIX |
nvsecd cores launching nvsec_admin if subdirectories exist in /usr/OV/security/C/Domains/*. |
| IY55354 | UNIX |
HSRP interface gets deleted and recreated every minute. |
| IY55559 | UNIX |
The addition of the AutoTrace facility in NetView 7.1.4 caused major performance degradation to snmpwalk. |
| IY55671 | Windows UNIX |
tdwdaemon is adding multiple records to the Avail DB for the same status event because of the way netmon is generating events. |
| IY55689 | Windows UNIX |
Layer 2 status does not propagate correctly to switch icons on SmartSet or custom maps. |
| IY55803 | UNIX |
IBM Tivoli NetView's online books and helps have Netscape hard-coded as the browser to use. |
| IY55831 | UNIX |
Spurious ovwdb hang during communications with ovspmd |
| IY55966 | UNIX |
Holding the spacebar down causes ovw_binary to core in about 20 seconds. |
| IY55972 | UNIX |
$AGENT_ADDR does not resolve host name in forwarded events to the Tivoli Enterprise Console. |
| IY56095 | UNIX |
Two "NODE UNMANAGED" traps for one UNMANAGE action. |
| IY56157 | UNIX |
Slow performance when closing multiple NetView windows causing the maps to grey out and hang around for awhile. |
| IY56279 | UNIX |
Duplicate events may be sent to the Tivoli Enterprise Console if users do ovtop/ovstart nvserverd without stopping nvcorrd as well. |
| IY56323 | UNIX |
The NMAVAILABILITY=TRUE flag in netmon.conf doesn't work. Regardless of the setting in netmon.conf, no available data was being created in /usr/OV/databases/availData_yyymmdd. |
| IY56338 | Windows UNIX |
netmon does not resolve seed file names that start with a digit. |
| IY56522 | UNIX |
On Linux, netcheck TCP routine displays incorrect error message: "ERROR: Could not connect to port 5888: Connection refused." |
| IY56534 | UNIX |
The UNIX -R option (Remove empty networks and segments) for ovtopofix now works by itself, not just in conjunction with the -A and -a options. |
| IY56563 | Windows UNIX |
serversetup does not include the ability to set snmpCollect's -w flag. This results in the Tivoli Data Warehouse function being disabled. |
| IY56564 | Windows UNIX |
snmpCollect's -w flag is not documented in the IBM Tivoli NetView Warehouse Enablement Pack Implementation Guide or in the snmpCollect man pages. |
| IY56565 | UNIX |
No DB2 activity tracing messages/options related to snmpCollect writing data to the NetView warehouse database. |
| IY56637 | Windows UNIX |
The command "netmon -a 160" does not dump the value of the TDWAVAILABILITY flag. |
| IY56671 | Windows UNIX |
Enumerations are lost from the NetView database after a ovstop/ovstop nvsecd, /etc/netnmrc is performed. |
| IY56958 | Windows UNIX |
Eliminate major memory leak in nvcold that is triggered by running nvUtil evaluate commands. |
| IY57192 | UNIX |
Zooming on submaps doesn't always work. |
| IY57383 | UNIX |
nvtecia -reload does not work with tme_nvserverd; the process dies. |
| IY57388 | UNIX |
On Linux, rulesets have problems with nodes that do not have names. |
| IY57432 | UNIX |
Parsing failure at the Tivoli Enterprise Console for IBM Tivoli NetView events with big interface lists (varbind 8). |
| IY57468 | UNIX |
Turning off "Poll for Status" doesn't disable SnmpStatus poll, but it does disable ICMP ping. |
| IY57469 | UNIX |
When all settings from the Topology/Status Polling Configuration are turned off, explicit seed file entries are not discovered. |
| IY57579 | UNIX |
IY4909 can cause performance problems during netmon startup. |
| IY57654 | UNIX |
ovtopmd cores when there are incomplete objects left in the database. It occurs only in rare cases. |
| IY58119 | UNIX |
Users used the SmartSet editor (collectioned) dialog to create SmartSets where the first definition was a "two word" attribute and the second definition was an IN_COLLECTION test. Creating the SmartSet was successful. However, when the user subsequently tried to modify that SmartSet using the SmartSet editor dialog, the SmartSet editor said "SmartSet cannot be correctly expressed in dialog. Text editor used instead." |
| IY58244 | Windows UNIX |
nvdbformat gave wrong results with some selectrule definitions. |
| IY58305 | UNIX |
ovw_binary cores when resizing window. |
| IY58392 | UNIX |
trapgend fails to properly parse CORE_DUMP on AIX 5.2. |
| IY58404 | Windows UNIX |
If there are problems with the first address, snmp_addr in the netmon cache should not be changed to be the second address if the second address also fails. |
| IY58428 | UNIX |
netmon exits with a signal 13 after Ctrl-C is issued to stop a nmdemandpoll. |
| IY58512 | UNIX |
snmpCollect is not closing DB2 database connections, which results in many connections still listed as active even though they are not being used. |
| IY58514 | Windows UNIX |
Using serversetup for tdwdaemon to create the DB2 NetView warehouse database unnecessarily issues a db2stop/db2start. |
| IY58551 | UNIX |
mib2trap does not add slotmap embedded comments into the baroc file. |
| IY58586 | UNIX |
The user brings up the SmartSet editor (collectioned) either from the native NetView console or from the command line. The user then clicks Add -> Modify and then switches the Definition type to Subnet. The user then clicks Calculate, types in an IP address and Subnet Mask, and then clicks Calculate. collectioned then cores with a Segmentation Fault. |
| IY58772 | UNIX |
The sqlstate and sqlcode values are not being written to the snmpCol.trace file during failures between snmpCollect-UNIX and DB2. |
| IY58780 | Windows UNIX |
Icon size in the submapexplorer is sometimes calculated incorrectly. |
| IY59196 | Windows UNIX |
ovtopmd cores due to memory leaks. |
| IY59201 | Windows UNIX |
ovtopmd grows in size when objects are deleted from the map. |
| IY59424 | Windows UNIX |
Incorrect status report on SnmpStatus poll whenever there is a timeout on the request. |
| IY59537 | Windows UNIX |
servmon does not clear the SmartSet ovw database entry when a node is deleted. |
| IY60528 | UNIX |
NetView event severity is no longer sent on Tivoli Enterprise Console events in 7.1.4. Add an environment variable to nvseverd to cause it to put severity back on but omit the severity by default. |
| IY60701 | UNIX |
netmon reports interface down events for the rest of the interfaces once hitting an "Snmp error: no such name" on one of the SNMP status requests (req = SNMPStatus). |
| IY60978 | UNIX |
Global acknowledging does not work for location objects. |
| IY61174 | Windows UNIX |
Error in /usr/OV/conf/tdwdaemon.log: "Wrong number of parameters" |
| PJ29495 | Windows |
The setstatusseverity.rs ruleset is broken. |
| PJ29522 | Windows UNIX |
The API call "OVwFieldNameToFieldId" fails if NetView is recycled and the client application is not. A new ovw API, OVwDbDone(), was added so that applications can recover from a lost connection to ovwdb. |
| PJ29525 | Windows |
User created backgrounds for submaps were not being displayed. |
| PJ29701 | Windows UNIX |
NetView SmartSet not created for ITM services. |
| PJ29726 | Windows UNIX |
Restrict SNMP status polling to discovered interfaces. |
| PJ29734 | UNIX |
When the UNIX xnmgraph View -> Statistics is saved to a file, the output line field is limited to 20 characters in the output file. |
| PJ29812 | Windows |
The Windows Tivoli Enterprise Console-forwarding daemon (tecad_nv6k) stops working after consuming lots of memory (determined by looking at the Task Manager Window). |
| PJ29814 | Windows |
"Configure Data Export to DB2 for use in TEDW" does not add the -w flag to snmpcollect so that it writes records to DB2. Moreover, nvsetup.exe configuration for snmpcollect does not update the ovsuf and snmpCol.lrf files with the Warehouse "-w" flag. |
| PJ29821 | Windows |
Parsing failure at the Tivoli Enterprise Console for NetView events with big interface lists (varbind 8). |
| PJ29910 | Windows UNIX |
SQL statements were missing single quotes around zeroes in an SQL command file. |
The following customer-reported problems were fixed in IBM Tivoli NetView V7.1.4 by Fix Pack 01:
| APAR # | Platform | Description | |
|---|---|---|---|
| IY41085 | Windows UNIX |
ISDN status monitoring does not work on Cisco routers due to the organization of MIB data. | |
| IY42473 | UNIX |
NetView does not restart applications that are registered with the "-restart" parameter. | |
| IY47145 | Windows UNIX |
Documentation request to explicitly state requirements on the entries in the netmon seed file to discover and SNMP manage nodes. (See the entry for this APAR in the Product Notes section below) | |
| IY47892 | Windows UNIX |
The ovesmd daemon is making DNS requests on networks and network segments, unnecessarily degrading performance of the DNS server. | |
| IY48379 | Windows UNIX |
The ovstop nvsecd command does not stop the tdwdaemon (See Product Notes below to implement this correction). | |
| IY48447 | Windows |
Error in help message panel for object status for specific traps. | |
| IY48542 | UNIX |
The trapd daemon causes a core dump with a buffer overflow. | |
| IY49032 | UNIX |
The serversetup application on Solaris and Linux contains AIX-specific terminology and options. | |
| IY49405 | UNIX |
CNAT data is not migrated from earlier versions of NetView V7.1.x to NetView V7.1.4. | |
| IY49428 | Windows UNIX |
The nvdbformat application "TopM Interface List" is always prepended by a Carriage Return. | |
| IY49532 | Windows UNIX |
The nvdbformat application does not complete and gives incorrect output. | |
| IY49546 | UNIX |
The printtool application causes a core dump on Tivoli NetView V7.1.3 on Linux. | |
| IY49787 | UNIX |
NetView 7.1.3 ovw_binary core. | |
| IY49953 | UNIX |
The nvauth executable cores with a segmentation fault when bad data is given. | |
| IY49954 | UNIX |
An overflow condition occurs on the command line parameters of the nvauth executable. | |
| IY49955 | UNIX |
The nvauth executable causes a core dump when the password command line argument is longer than expected. | |
| IY49975 | UNIX |
The ipmap executable never ends synchronization and causes a core dump when GLOBAL ACKNOWLEDGE is enabled. | |
| IY49985 | UNIX |
The pmd daemon causes a core dump when its port is scanned by third-party software. | |
| IY50013 | UNIX |
The nvlockd daemon causes a core dump when its port is scanned by third-party software. | |
| IY50133 | UNIX |
Installation of NetView 7.1.4 on AIX 4.3.3 ML 10 fails starting nvsecd with the error message "ovstart: unable to contact ovspmd: No such file or directory." | |
| IY50196 | Windows UNIX |
Request for additional alternative community names. | |
| IY50227 | Windows |
Unnecessary trace messages in servmon.log. | |
| IY50265 | UNIX |
The nvcorrd daemon causes a core dump when bad data is written to the nvcorrd socket. | |
| IY50266 | UNIX |
The actionsvr daemon causes a core dump when bad data is written to its socket. | |
| IY50394 | Windows UNIX |
The IPMAP application causes a core dump after migrating from NetView 7.1.2 to NetView 7.1.3. | |
| IY50461 | Windows UNIX |
Provide support in location.conf for wildcard IP addresses for routers. | |
| IY50464 | Windows UNIX |
The netmon daemon is discovering several devices and setting them as unmanaged even though configured to manage newly discovered nodes. | |
| IY50663 | UNIX |
The ovtopmd daemon and the ovtopofix command run much more slowly when AutoTrace is turned on. | |
| IY50702 | Windows UNIX |
An ITSA-managed switch may not have the correct symbol status shown in ipmap. | |
| IY50954 | UNIX |
The snmpCollect daemon does not collect on an IP address if the address resolves to a host name. | |
| IY50990 | Windows UNIX |
The netmon daemon doesn't wait the configured amount of time to perform status polling after a restart. | |
| IY51064 | Windows UNIX |
Query Database Field node does not work for an interface selection name in a ruleset. | |
| IY51125 | Windows UNIX |
Errors using SNMP wildcards in the netmon seed file in NetView 7.1.3. | |
| IY51162 | UNIX |
Trap slot values with long names are being truncated to 15 characters when it is saved. | |
| IY51181 | UNIX |
The right scrollbar becomes non-functional in the seed file editor. | |
| IY51516 | Windows UNIX |
The nvrsEdit application does not display an error if it cannot handle a ruleset correctly at open. | |
| IY51641 | UNIX |
The nvserverd daemon causes a core dump due to a buffer being too small to properly format a very large trap. | |
| IY51700 | Windows UNIX |
IBM Tivoli NetView 7.1.4 requires latest the IBM Tivoli Enterprise Console releases if Tivoli Enterprise Console-forwarding is enabled. | |
| IY51778 | Windows UNIX |
Behavior of range of addresses in netmon seed file differs from previous release (see the product note below). | |
| IY51844 | Windows UNIX |
Rediscovery of routers does not work. | |
| IY52086 | UNIX |
Need to clarify the meaning of the "retries" parameter for the netmon daemon (see product note below). | |
| IY52227 | UNIX |
Need to be able to acknowledge layer 2 marginal status on a switch that has an IP status of normal. | |
| IY52295 | UNIX |
Need to add ping count control to non-AIX NetView UNIX platforms. It is already on AIX. | |
| IY52234 | UNIX |
Upgrading to 7.1.4 results in incorrect IP topology counts in the Relational Database when the ipgettopoinfo command is run. | |
| IY52320 | UNIX |
The SNMP configuration look up routine is now returning NetView's default value instead of user's setting in Global Default. | |
| IY52341 | Windows UNIX |
The ipmap executable is coring on NetView 7.1.3 Fix Pack 1 on AIX 5.1. | |
| IY52351 | Windows UNIX |
Several traps causing DNS requests for network and segment addresses. | |
| IY52394 | Windows UNIX |
The nvcorrd daemon causes a core dump in function setstatednode with signal 11. | |
| IY52429 | UNIX |
In NetView 7.1.4, a trap slot with host name in a Tivoli Enterprise Console event is left blank if host name has a hyphen (-) in it. | |
| IY52758 | UNIX |
The xnmgraph application is calculating wrong y-axis values. | |
| IY52773 | Windows UNIX |
Netmon causes a core dump with a signal 11 every 10 minutes. | |
| IY52820 | UNIX |
The trapd daemon is coring on a regular basis in NetView 7.1.4 on AIX 5.2. | |
| IY53038 | UNIX |
On NetView 7.1.3/7.1.4 for Linux, non-root users are not allowed to start the GUI due to a missing line in the startup script. | |
| IY53188 | Windows UNIX |
Document the fact that users can modify the maximum number of community names by setting the following variable in netmon.conf file: MaximumCommunityNames=x. The value of x can be from 0 to 100. | |
| IY53205 | Windows UNIX |
Attempt to add status monitoring of ITM resource model to servmon did not work. | |
| IY53244 | UNIX |
Garbage printed in the nvgethost command usage. | |
| IY53271 | Windows UNIX |
The trapd daemon stops when toggling tracing or logging on zLinux. | |
| IY53400 | UNIX |
The xnmloadmib2 and xnmbrowser2 applications cannot run if NetView security is enabled. No Security Registration Files exist. | |
| IY53554 | UNIX |
The mibtable command loops on Mid-Level Manager MIBs. | |
| IY53666 | UNIX |
The trapd daemon stops with a signal 13 when the trapd.log reaches its maximum size. | |
| IY53704 | UNIX |
Problem editing a Set State node in the NVRSEdit application. | |
| IY53727 | Windows UNIX |
An incorrect symbol is showing up on map for several interfaces. | |
| IY53780 | UNIX |
The netmon daemon pings unwanted interfaces. | |
| IY53804 | Windows UNIX |
The nvdbformat application is coring after applying NetView 7.1.3 Fix Pack 2 | |
| IY53928 | Windows UNIX |
A servmon daemon performance problem exists in NetView 7.1.4. | |
| IY54371 | Windows UNIX |
"Interface Unreachable" events occur on every polling cycle when RFI is enabled. | |
| IY54644 | Windows UNIX |
NetView Web Console hanging. | |
| IY54964 | Windows UNIX |
The netmon daemon is trying to poll thousands of interfaces simultaneously on large networks. | |
| IY55374 | UNIX |
Unclear documentation for using the snmpd64v1 agent on AIX 5.2 | |
| PJ29055 | Windows |
Output of the origin tecad default slot values for certain traps is incorrect. | |
| PJ29416 | Windows |
The hostname field is being left blank when forwarding events to Tivoli Enterprise Console. | |
| PJ29421 | Windows UNIX |
The ovobjprint command is not displaying all appropriate information on large databases. | |
| PJ29460 | Windows |
Issue with icon selection name and label when netmon discovers a router whose first interface is not in DNS. | |
| PJ29480 | Windows |
Node status is not properly updated after a service symbol is deleted based on Service Down interval. | |
| PJ29481 | Windows |
Node status in SmartSet may be incorrect when node comes back up. | |
| PJ29503 | Windows UNIX |
Deleted service symbols may propagate incorrect status. | |
| PJ29517 | Windows |
The nvcord daemons exchanges a "$A" value incorrectly for an event that passed through an activated ruleset. | |
| PJ29580 | Windows |
The "filter by" option on the Collected Data objects properties screen does not reflect data if the "<" or ">" options are used. | |
| PJ29586 | Windows UNIX |
Cannot get/set fields with a comma in them using the nvdbformat/nvdbimport commands. | |
| PJ29588 | Windows UNIX |
Excessive number of truncation errors logged when using NetView ETLs. | |
| PJ29644 | Windows |
NetView for Windows trapd daemon exception on null IP address from Microsoft Trap Service. | |
| PJ29651 | Windows UNIX |
NetView Warehouse Enablement Pack failing to insert destination data because of string truncation errors." | |
| PJ29653 | Windows UNIX |
NetView Warehouse Enablement Pack missing historical data for the reports showing percent outage for both month and yearly reports. | |
| PJ29654 | Windows UNIX |
NetView ETL2 is not calculating availability accurately in all cases. | |
| PJ29666 | Windows |
The snmpCollect daemon repeats snmpget requests when the number of objects to collect exceeds 16. | |
| PJ29671 | Windows |
Graph function not working for previously defined data collection. |
In order to install IBM Tivoli NetView V7.1.4 Fix Pack 02 on a system, you must meet the following prerequisites:
You must download the appropriate package for that platform and make it available to the system on which it is to be installed.
You must be logged into the system with the same user account that performed the original NetView V7.1.4 installation (the root account on UNIX).
The system must already contain an IBM Tivoli NetView Version 7.1.4 installation.
The system on which the fix pack is to be installed must have enough free space to do the following:
Installations that contain a previous IBM Tivoli NetView fix pack may recover most of the space used by that fix pack by deleting the /usr/OV/service/V713/Fix PackX directory on UNIX, or the \usr\ov\service\v713\Fix PackX directory on Windows prior to installing this fix pack. Please note, however, that doing so removes the ability to back out the previous fix pack, as well as the ability to install code fixes that require the previous fix pack in order to install.
The table below describes the amount of space required on each platform for each of the space requirements described above.
Operating System |
Space Required for Installation1 |
Space Required for Upgraded Product2 |
|---|---|---|
RS6000 AIX |
719 Mb |
378 Mb |
SunOS Solaris |
818 Mb |
433 Mb |
Linux Intel |
685 Mb |
360 Mb |
Linux 390 |
616 Mb |
324 Mb |
Windows |
103 Mb |
61 Mb |
1This space is required in whatever location the user places the Fix Pack installation package. 2This space is required in /usr/OV on UNIX or in \usr\ov on Windows. |
||
Most of the space required to contain the fix pack contents in /usr/OV or \usr\ov (the space described in the second column) can be returned to the system by deleting the contents of the /usr/OV/service/V714/FixPack2 (on UNIX) or \usr\ov\service\V714\FixPack2 (on Windows) directory. However, doing so removes the ability to back out the fix pack. Do not delete the FixPack2 subdirectory itself; this subdirectory must exist in order to install fixes that have this fix pack as a prerequisite.
For Red Hat Enterprise Linux Advance Server 3.0 i386 (32 bit) and s390 (31 bit) and SuSE Linux Enterprise Server (SLES) 9.0 i386 (32 bit) and s390 (31 bit), a new NetView 7.1.4 Linux CD has been added to the base NetView 7.1.4 kit and a standard fresh IBM Tivoli NetView install is required. This new CD is ONLY for new installations on Red Hat Enterprise Linux Advance Server 3.0 i386 (32 bit) and s390 (31 bit) and SuSE Linux Enterprise Server (SLES) 9.0 i386 (32 bit) and s390 (31 bit).
For the IBM Tivoli NetView installation on Red Hat Enterprise Linux Advance Server 3.0 i386 (32 bit) and s390 (31 bit) and SuSE Linux Enterprise Server (SLES) 9.0 i386 (32 bit) and s390 (31 bit) to work correctly, the following Linux packages must be installed first.
The user must install the optional Red Hat i386 package, compat-libstdc++-7.3-2.96.122, or the s390 package, compat-libstdc++-7.2-2.95.3.78. This package can be found on the Red Hat Enterprise Linux Advance Server 3.0 Update 1 or 2 CD set.
In order to correct ifIndex and ipAdEntIfIndex mismatches in the ifIndex reference by IP-MIB, the user needs to update the net-snmp rpms to the following levels:
rpm -i --force pdksh-5.2.14.8.i386.rpm (or pdksh-5.2.14-248.s390.rpm)
Verify it via the command below.
rpm -q pdksh
Note: On SLES 9, the Xvfb package is XFree86-Xvfb, rather than xextra.
During a new installation, if at least one package in each group is not found, then installation prerequisite checking fails and installation aborts.
For Red Hat Enterprise Linux Advance Server 3.0 i386 (32 bit) and s390 (31 bit) and SuSE Linux Enterprise Server (SLES) 9.0 i386 (32 bit) and s390 (31 bit), get the new NetView 7.1.4 Linux CD from IBM and follow the existing directions for a Standard install.
For all other platforms, perform the following steps to install the fix pack:
Users using the Secure Socket Layer (SSL) protocol either need to (1) turn off SSL via the NetView serversetup application, or (2) copy the file /usr/OV/www/webapps/netview/WEB-INF/web.xml (on UNIX) or \usr\ov\www\webapps\netview\WEB-INF\web.xml (on Windows) to a temporary location.
If you are installing the fix pack on a NetView for UNIX client, ensure that the client is disconnected from the NetView Server by completing the following:
Open a new window, copy the package into a local subdirectory on the operating system on which the fix pack is to be installed, and change directory to that subdirectory.
Prior to copying the package, ensure that the space available in this subdirectory is larger than the space required for installation of the IBM Tivoli NetView 7.1.4 Fix Pack 02 on this operating system.
Extract the installation script by doing one of the following:
zcat 7.1.4-TIV-NVD-{OperatingSystem}-FP0002.tar.Z | tar -xvf - install
7.1.4-TIV-NVD-Win32-FP0002.exe
Run the installation script:
./install
install
install noversioncheck
When installing the fix pack on a native NetView client installation, it reports a set of errors that cetain files (for example nvexportd.jar, nvexportd.lrf, and notfoundhandler.class) could not be copied. These files are not necessary for a client installation, and the errors should be ignored.
In the event that you encounter any other errors during the installation (regardless if the installation process itself reports success), complete the following:
Restart the NetView daemons on UNIX either by rebooting the machine, or by executing the netnmrc script (/etc/netnmrc on AIX, /etc/init.d/netnmrc on Solaris or Linux). Restart the NetView daemons on Windows either by rebooting the machine, or by using the netview command, or by clicking on the NetView icon.
Note: If the NetView installation is using a SQL database on Windows, restart the SQL server before you restart the NetView daemons.
Reinstall any NetView Web Console installations from the upgraded native NetView Server installation. This can be downloaded from the following URL, after the NetView server has been upgraded:
http://server:8080/download
For the Web Console on Windows, the files below contain the fix pack updates. If you have been using the thin client, then the nvwc_thin.zip should be applied. If you have been using the full Web Console, then the nvwcinstall.exe should be applied.
nvwc_thin.zip (thin Web Console for Windows) nvwcinstall.exe (self extracting installation)
For the Web Console on UNIX, the following file contains the fix pack updates:
nvwc.tar (Web Console for UNIX)
Note that when upgrading a NetView Web Console from a NetView fix pack UNIX server, this version of the NetView Web Console package should be used. The full version (nvwc_xxx_jre_1.3.tar) of the NetView Web Console does not contain the Fix Pack updates. After the Fix Pack has been installed on a NetView server, the package nvwc.tar must be applied on top of the full package whenever the full package is installed.
As a part of the fix pack installation, a copy of each file that is replaced during the installation is saved in the /usr/OV/service/V714/FixPack2 on UNIX or the \usr\ov\service\V714\FixPack2 on Windows subdirectory. If you want, you may uninstall the fix pack by running the backout script contained in that directory and the system returns to the state that it was in prior to the fix pack installation.
Note: For Windows, the backout script must be run from the \usr\ov\service\V714\FixPack2 subdirectory. Similarly, for UNIX, the backout script must be run from the /usr/OV/service/V714/FixPack2 subdirectory.
Any NetView fixes installed on the system after the fix pack is installed must be backed out prior to backing out the fix pack.
Note: If you do ovstop followed by ovstart or run /etc/init.d/netmrc, nslookup may core again.
To determine whether a /usr/OV/PD/cores/ovspmd/core is due to this problem, run the following command on the core file:
strings core | moreIf the string nslookup appears in the output, the core can safely be ignored.
TDWAVAILABILITY=FALSE
IBM Tivoli NetView may have discovery and status updating problems for IBM Tivoli NetView managed machines that are running SNMPv3 agent daemons. These problems can be eliminated by ensuring that the SNMP daemon of the managed machines are linked to an SNMPv1 daemon and not linked to an SNMPv3 daemon.
UNIX users who use the Web Console with a large NetView database, should:
On AIX, netviewd fails to start if the correct X11 Xvfb is not running.
If netviewd fails to start on AIX because the correct X11 xvfb is not running (APARs IY54430 and IY58569), the user needs to add grep ":2" | into the /etc/netnmrc file as shown below.
# Start Xvfb Xserver
#
pid=`/bin/ps -ef | /bin/grep vfb | /bin/grep -v grep | grep ":2" | /bin/awk '{print $2}'`
Nodes with "Discover Node(s) Managed" unchecked via xnmsnmpconf (UNIX) or due to the settings in the oid_to_type file that are discovered while the Native NetView Console is up, show up on the map as "Unknown," rather than as "Unmanaged."
The work around (documented in APAR IY58520) is to make sure the Native NetView console is down when these nodes are being discovered or to unmanage the nodes manually from the GUI once they show up on the map as "Unknown." Moreover, if the user wants to manage the node, the user first must unmanage it and then manage it.
Manipulation of the Korn shell history file from a .kshrc file is not recommended. Several of the installation mechanisms used by NetView expect the standard history file to be set; if it is not, the prerequisite checking and the actual NetView installation fails.
Some users have encountered difficulties when using the stand-alone IBM Tivoli NetView installation on a system that has the Tivoli Framework installed in a customized location. To avoid these difficulties, it is recommended that if you want to retain the Framework in the environment, you should install IBM Tivoli NetView via the standard Tivoli Framework installation. If the Framework was installed only to support NetView and is no longer desired, then you should complete the following:
When you attempt to run nvColToSQL you may get the following error message:
Database Server is not present or not enough disk space for log files, temp files and rollback segment or table does not exists in the databaseThis message can occur if there are too many snmpCollect files to process (usually more than 500). If you get this message, you can use the following script to process the files. This script processes each file one at a time and saves the output to the log file.
#!/bin/sh LOG=/usr/OV/log/nvColToSQL.log date > $LOG # CREATE NEW LOG EACH TIME # Loop all files that do not have ! or archive in name for file in `ls /usr/OV/databases/snmpCollect | grep -v "\!" | grep -v "archive"` donvColToSQL -f $file -m 64 >> $LOG 2>> $LOG RC=$? echo "* FILE <$file> Return Code <$RC>" >> $LOGdone
The help for SNMPV2 command on NetView for Windows V7.1, found by opening the Help menu item, selecting Help Topics, selecting the Find tab, entering snmp, selecting SNMPV2 from the list, and selecting Tools -> MIB -> SNMPV2 -> Load Command is no longer valid and should be ignored.
Due to a quirk in the Linux operating system and the formatting of the NetView for UNIX man pages, the man pages do not display properly on Linux systems unless the Linux terminal window is greater than 80 characters wide. To correct the formatting, enlarge the terminal window by using your mouse to drag the right border of the window farther to the right.
In NetView for Windows, admin down interfaces (status USER1) can incorrectly change to a critical status when the interface is unmanaged and then managed again due to netmon's use of the ICMP ping. The admin down status of the interface won't be picked up again until the next Config Check or demand poll. To prevent the admin down interfaces from being reported as critical in this situation, configure the router with the admin down interfaces to use SnmpStatus poll instead of ICMP poll in the netmon seed file.
On Tivoli NetView for Windows on Windows 2003, attempting to send a message to a client or server (Server Setup -> Client/Server -> Send Message tab) may result in a popup with a "NO MESSAGE" error. This may be due to the Windows Messenger service not being enabled; the default is to leave the service disabled after installation on Windows 2003. To enable the Messenger Service, complete the following:
When a SmartSet submap is opened in Tivoli NetView for UNIX, collmap overrides any user-customized labels for generic symbols with the selection name for the object. A workaround is to configure and use a nongeneric symbol for the object.
On some Linux platforms, the operating system may not properly shut down some of the threads of the Tivoli NetView for UNIX Java daemons, occasionally resulting in problems restarting the NetView daemons. A "force" option has been added to the nvKill command to shut down all rogue NetView daemons and threads and clear out the sockets, allowing the daemons to be restarted properly if this situation arises. If the NetView daemons appear to be hung (the restart has lasted longer than 10 minutes), type the command
at a command prompt, and then use the netnmrc or the netview command to restart the daemons in the normal manner.
If a NetView for Windows installation was migrated from a previous version, then the NetView.exe executable locks up when using "Find by Other Properties" under the simple tab of the find dialog due to the file /usr/ov/conf/c/finddialog.conf having a <CR><LF> changed to just a <CR>.
To fix the problem, load the finddialog.conf file into the Windows Wordpad program and then save the file. WordPad changes a <CR> to <CR><LF>. Note: The Windows Notepad program does not work.
When installing and backing out the NetView for 7.1.4 Fix Pack 02 on an installation of NetView with the Japanese language pack on a Solaris system, the NetView GUI has failed to start with an error message of "Error retrieving mapdb field info: Null field value." To recover from this error when it occurs, perform the following steps:
The Windows and AIX Web Consoles do not connect to a Solaris NetView Server when double-byte characters are used in the user ID. However, a Solaris 8 web console can connect to a Solaris NetView server when double-byte characters are used in the user ID.
When using the Japanese language pack, the default value of a map snapshot name (for example "Snapshot 1"), when used, is not displayed in the snapshot menu of the Server Setup Window. The created snapshot is displayed when you select File -> Map Snapshot -> Open. It can also be viewed when the ovmapsnap CLI command is used.
IBM Tivoli NetView for Windows users should implement the new ruleset, overridestatus_user1.rs, instead of the broken ruleset, setstatusseverity.rs. The broken setstatusseverity.rs ruleset puts the correlation daemon into a loop, continually sending bogus status change events to the trapd daemon, until both it and the Tivoli Enterprise Console adapter daemon are overwhelmed. This ruleset is removed from the product in a future release, but it cannot be removed in a maintenance release.
Note: Once the Fix Pack has been installed, a user can refer to the new \usr\ov\doc\Rulesets_on_Windows.readme for more information on rulesets.
This section reflects documentation updates that will be added in future releases.
Documentation for the new Tivoli NetView functions described in this Readme will be added to the appropriate Tivoli NetView publications in future releases.
Neither the IBM Tivoli NetView for UNIX Administrator's Guide nor the IBM Tivoli for Windows User's Guide correctly and clearly explain how and when servmon creates Service SmartSets. They will be updated as decribed in the Fix pack notes section of this Readme.
Listed below are documentation changes to the IBM Tivoli NetView, Version 7.1.4 Warehouse Enablement Pack Implementation Guide for Tivoli Enterprise Data Warehouse, Version 1.1.0 Revised April, 2004.
Note: The Tivoli Enterprise Data Warehouse, as it was named for version 1.1, no longer ships with IBM Tivoli NetView. Version 1.2, which was renamed Tivoli Data Warehouse, now ships with IBM Tivoli NetView. The documentation will be updated to reflect this change.
Under the section "3.9 Post-installation procedures" on page 13, change the sub-section heading: 3.9.1 Verifying the tdwdaemon daemon configuration to read: 3.9.1 Verifying the tdwdaemon and snmpcollect daemon configurations.
In section 3.9.1, change the text: The tdwdaemon daemon configuration for use with performance information to read: The snmpcollect daemon configuration for use with performance information.
In this same section, 3.9.1, the text, "If you are using the performance warehouse pack, you must also perform the procedure in "Error! Reference source not found." on page Error! Bookmark not defined." does not indicate the page/section because of a document publishing error. This document publishing error will be fixed.
On page 14, change the section title: 3.9.1.2 Verifying the tdwdaemon daemon configuration for use with performance information to read: 3.9.1.2 Verifying the snmpcollect daemon configuration for use with performance information.
In section 3.9.1.2, change all references of tdwdaemon to snmpcollect.
In section 3.9.1.2, also add the following new information at the bottom of section 3.9.1.2. This includes information about the "-w" option.
/usr/OV/bin/serversetupon the command line to start the Server Setup application.
Note to be added to future versions of the IBM Tivoli NetView Release Notes and to the WebConsole User's Guide:
In addition to requiring the default map open (with the name "default"), the Scope feature of the NetView Web Console requires that this map be open in read/write mode. Users can configure web accounts to effectively view "read-only" maps by just removing the manage/unmanage and acknowledge/unacknowledge actions from the role their account is configured for. Although users using such an account would really be viewing a read-write map, they would not be able to modify the map in any way and therefore it would effectively be read-only.
In the IBM Tivoli NetView for UNIX Release Notes, Version 7.1.4, "Product Notes," page 49, the paragraph beginning with "The Tivoli NetView for UNIX product running on the AIX Version 5.2 operating system" is incorrect. It should read as follows:
The Tivoli NetView for UNIX product running on the AIX Version 5.2 operating system only supports the snmpdv1 version of the SNMP daemon. If the 64-bit operating system is being used, then the following procedure changes to snmpd64v1 and not snmpdv1, which is what is supported. snmpdv1 and snmpd64v1 are both SNMPv1 agents. It is impossible for snmpdv1 to run on the 64-bit kernel instead of snmpd64v1. Use the following procedure to determine which version of the daemon is running on your system and change the SNMP daemon version.
The IBM Tivoli NetView Release Notes for NetView V7.1.3 and V7.1.4, Linux Software Prerequisites section, mistakenly refers to pdksh-5.2.14-248.s390.rpm as the package to use from the NetView for Linux 390 CD.
However, the RPM shipped on the CD is really pdksh-5.2.14-197.s390.rpm, and the release notes should reflect this.
In the IBM Tivoli NetView for UNIX Release Notes Version 7.1.4, the command given on page 8 to confirm that the Tivoli NetView AutoTrace function is stopped is incorrect:
/usr/OV/bin/atctl v infoThe command should be:
/usr/OV/bin/atctl -v info
In order to use the Shift-In/Shift-Out mechanism, you need to run nvauth first.
Note on specifying time values to be added to the IBM Tivoli NetView for UNIX Administrator's Guide, Chapter 5, "Correlating, Filtering, and Configuring Events," under "Types of Ruleset Nodes":
When an event is first pulled from the event stream, it is given a time stamp to be used in determining its eligibility for processing in time-critical operations within a ruleset, such as Pass-on-Match, Reset-on-Match, or Threshold operations. This time stamp on the event remains unchanged during all subsequent processing. Determinations as to whether an event should be held or discarded are made, therefore, based upon the time that the event was received. This makes all subsequent time comparisons after the first one cumulative. Should you wish to add two time-critical operations back-to-back, you must allow for this cumulative time. Thus, for example, should you wish to code two Reset-on-Match nodes, back-to-back, within the same ruleset, and have the first one hold the event for two minutes and the second one hold it for an additional minute, then you must specify a two-minute time value in the first Reset node, but a three-minute time value in the second one, to allow for the two minutes that have already expired before the event passes to the second Reset-on-Match node. Failure to allow for this results in unintended results, typically with events not being held as long as you intended.
In the IBM Tivoli NetView for UNIX Administrator's Guide, Chapter 5, under "Environment Variables for Trap Data," the information given in the Fix pack notes section of this Readme document regarding the exported varbinds "NVSEV," "NVSRC," and "NVCAT" should be included.
In the IBM Tivoli NetView for UNIX Version 7 Administrator's Guide, the following line near the bottom of page 164 is no longer true and needs to be removed:
When the node name does not resolve to an IP address, the community name public is used to send the SNMP request.
The IBM Tivoli NetView Web Console User's Guide needs to include the system requirements for Microsoft Internet Explorer for those users who wish to run the NetView Web Console on a system using that browser. Minimum requirements are a 450 MHz machine with 256 MB of RAM. For a production system, the recommendation is 800 MHz with at least 256 MB.
The rest of the note on page 34 is correct.
- To be able to successfully install the NetView ETLs in a Tivoli Data Warehouse environment that is distributed across more than one machine, the machines where the TWH_CDW and TWH_MART databases exist must also have the corresponding Tivoli Enterprise Data Warehouse components installed:
- "Central Data Warehouse" component must be installed on the server containing the TWH_CDW database.
- "Data mart" component must be installed on the server containing the TWH_MART database.
The description of the Thresh command "-T" option in the NetView for Windows Programmer's Reference Manual is not entirely correct. For the "-T" option it states:
Specifies the NetView enterprise-specific trap to be sent when the threshold is exceeded. This threshold must be an odd value in the range of 1001 to 1999, or the default value of 58720263.The statement should be changed to:
Specifies the NetView enterprise-specific trap to be sent when the threshold is met. This trap number must be an odd value in the range of 1001 to 1999, or the default value of 58720263.
The current online help for the "Send Trap Number" field when defining a MIB from which to collect data in NetView for Windows is incomplete and needs to be expanded upon. The following line should be added to the help information:
Specifies the trap number that is to be sent when the collected data meets the value in the Threshold field. This trap number must be an odd value between 1001 to 1999, or the default value of 58720263.This help can be invoked by completing the following:
The help panel for "Agent Policy Manager Filter Panel" Throttle Settings should be updated to include the 256 byte length limitation in the Armed and Disarmed commands:
8. Click Throttle Settings to specify the number of matching traps that are sent to the top-level manager. These values are used only if the Action field is set to throttle Traps. The Armed Command and Disarmed Command fields have a length limitation of 256 bytes.
If you have a problem with any Tivoli product, refer to the following IBM Software Support Web site: http://www.ibm.com/software/sysmgmt/products/support
If you want to contact software support, see the IBM Software Support Guide at the following Web site: http://techsupport.services.ibm.com/guides/handbook.html
The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information:
This information was developed for products and services offered in the U.S.A. IBM might not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service might be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described 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, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:I
IBM World Trade Asia Corporation
Licensing2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the products and/or the programs described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
2Z4A/10111400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
IBM, AIX, S/390, NetView, zSeries, Tivoli, and Tivoli Enterprise Console are trademarks of International Business Machines Corporation in the United States, other countries or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks of others.