|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback
us-support.external.hp.com)Date: Sun Sep 09 2001 - 11:09:11 CDT
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 800 10.X patch digest
Created: Sun Sep 9 3:05:04 PDT 2001
Table of Contents:
Document ID Title
--------------- -----------
PHSS_24797 s700_800 10.20 OV NNM6.1 Consolidated Patch 4
PHSS_24875 s700_800 10.X OpenMail B.07.00 September 01 Periodic Patch
PHSS_24873 s700_800 10.X OpenMail B.06.00 September 01 Periodic Patch
PHKL_25094 s800 10.20 Cumulative mmap, mprotect patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_24797
Date Loaded: 20010906
Title: s700_800 10.20 OV NNM6.1 Consolidated Patch 4
Patch Name: PHSS_24797
Patch Description: s700_800 10.20 OV NNM6.1 Consolidated Patch 4
Creation Date: 01/08/28
Post Date: 01/09/06
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OpenView Network Node Manager 6.1
Filesets:
OVNNMgr.OVMIB-CONTRIB,B.06.10.00
OVNNMgr.OVNNM-RUN,B.06.10.00 OVNNMgr.OVNNMGR-JPN,B.06.10.00
OVNNMgr.OVWWW-JPN,B.06.10.00
OVNNMgrMan.OVNNM-RUN-MAN,B.06.10.00
OVNNMgrRtDOC.OVNNMWELENGDOC,B.06.10.00
OVPlatform.OVDB-RUN,B.06.10.00
OVPlatform.OVEVENT-MIN,B.06.10.00
OVPlatform.OVMIN,B.06.10.00 OVPlatform.OVPMD-MIN,B.06.10.00
OVPlatform.OVRPT-RUN,B.06.10.00
OVPlatform.OVSNMP-MIN,B.06.10.00 OVPlatform.OVWIN,B.06.10.00
OVPlatform.OVWIN-BGROUND,B.06.10.00
OVPlatform.OVWWW-EVNT,B.06.10.00
OVPlatform.OVWWW-FW,B.06.10.00
OVPlatformDevKit.OVWIN-PRG,B.06.10.00
OVPlatformDevMan.OVWIN-PRG-MAN,B.06.10.00
OVPlatformMan.OVEVENTMIN-MAN,B.06.10.00
OVPlatformMan.OVMIN-MAN,B.06.10.00
OVPlatformMan.OVSNMP-MIN-MAN,B.06.10.00
OVPlatformMan.OVWIN-MAN,B.06.10.00
OVSNMPDevKit.OVSNMP-PRG,B.06.10.00
OVSNMPDevMan.OVSNMP-PRG-MAN,B.06.10.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_24797
Symptoms:
PHSS_24797:
Cumulative Consolidated Patch
PHSS_24785:
After installing patch PHSS_24442/3 the Access parameter
for Action blocks in www registration files is ignored.
This removes the ability to configure launcher access
based on user roles (i.e., all launcher items are
accessible to all users)
PHSS_24775:
On dual NNM + DM installations, large CMIP traps (6K or 7K)
cause pmd to coredump. Stack trace: OVsnmpAsn_build_int()
in libovsnmp is top entry on the stack.
PHSS_24773:
When the -k nonIPStatusPolls=false option is used with
netmon, netmon will not poll the level2 interfaces using
snmp anymore, but instead sends a ping to 0.0.0.0 for
level2 interfaces.
PHSS_24768:
Netmon dumps core with a stack trace similar to the
following:
_OVlogCrash (a, 1, ffffffff, 114ab8, 0, 0) + 690
__0FSfatalSignalHandleri (a, 0, ffbec0d0, 0, 0, 0) + 44
sigacthandler (a, 0, ffbec0d0, 4, 0, b35740) + 28
OVsnmpAddTypedVarBind (b49180, f9ce8, 122728, 5, 0, 0) +
328
printRequest (b49180, 1, 9, ffbeccd0, 1, ffbec8d0) + 28c
nextSnmpRequest (b49180, b49840, 64b2b8, 1, 1, 1) + 89c
gotSnmpResponse (b49180, b42858, b497e0, fed98938,
ffbece00, 12ffa4) +150c
recv_snmp (a0, b42858, b497e0, b49180, fec32110, fef1613c)
+ 868
_OVsnmpRecvCallback (b3fee0, b497e0, b49a78, ffbed700, 0,
0) + 300
_OVsnmpInputPending (b3fee0, b42868, 0, fec32110, 0, 0) +
90
OVsnmpRead (ffbedd3c, 21, fec39d14, fec3517c, ffbedc3c,
1a) + 180
__0FKNetmonLoopv (3b40820a, 0, 0, 135bb4, 400, ff357d04) +
12b8
main (4, ffbef07c, ffbef090, 114400, 0, 0) + 20c0
_start (0, 0, 0, 0, 0, 0) + dc
PHSS_24764:
NNM does not support Unisphere Networks ERX devices.
These devices report 96000 interfaces in their
interface table. This can cause netmon to core dump
due to lack of memory when trying to read all these
interfaces in prior to adding the data to the
topology.
PHSS_24748:
Some NNM programs crash when large object-ids or hostnames
are used.
PHSS_24746:
Netmon will occasionally abort in recv_snmp.
PHSS_24731:
If customers attempt to use NNM 6.1 from remote consoles,
then ipmap will return an error stating
"Fatal Ipmap Error: Cannot connect to pmd: bind(): cannot
assign requested address".
The problem was that the binding of addresses should not
have been done on remote consoles.
PHSS_24726:
Threshold and rearm values in snmpCollect get rounded off
if they are very large values ( > 7 digits)
PHSS_24721:
On some Solaris systems, ovhelp core dumped upon startup
when LANG=ja. It did not core dump for LANG=C, japanese or
ja_JP.PCK.
PHSS_24719:
When an event filter is created in xnmevents with a number
of sources, and then exported to a file, some filter source
entries are omitted in the saved file.
PHSS_24713:
Dragging a symbol from another submap to a submap with
point-to-point layout caused the symbol to jump down to the
lower left corner of the submap, instead of where the user
placed the symbol. This happened only with point-to-point
submaps with autolayout on.
PHSS_24675:
snmpCollect slow on initialization.
PHSS_24666:
The ECS ScheduledMaintenance circuit can fail to correlate
events when a WeekDay OutageSpecification is used.
PHSS_24442:
The NNM Launcher hangs forever at "40% done" when invoked,
if all of the following conditions are true :
-"User Login" is enabled (via session.conf file)
-The htgroup file is changed to only allow access to
specific users (i.e. not using the default "+" wildcard
that allows access to all users)
-A user is added (using ovhtpasswd), and this user is not
included in the lists for any of the groups in htgroup.
-The launcher registration files include only menus and
tabs that have no group-level restrictions.
If all of the above are true, then the Launcher will never
get past the "40%" stage.
Secondary symptom: If the browser's "Java Console" is
open, an error message about a "Null Pointer" exception
will show up there at the time of the failure.
PHSS_24415:
An NNM 6.1 Management Station cannot manage an NNM 6.2
Collection Station. This NNM 6.1 patch is required in
order for an NNM 6.1 Management Station to successfully
manage a 6.2 Collection Station.
PHSS_24411:
In certain cases it is impossible to add a node to NNM's
object database after that same node has been deleted.
This is typically seen when using the "loadhosts" command
to add the node. The loadhosts command will fail with the
error message:
ERROR: Could not add node nodename to topology:
OVW Database Failure: Object not found
PHSS_24362:
Corrupted gif89 format images caused ovw to core dump.
Also, closing Network Presenter could occasionally cause
the root submap to suddenly be displayed on the ovw session
in place of the home submap.
PHSS_24297:
Web Alarm Category window is too narrow if wide category
names exist. Colored buttons disappear off left side and
label text is truncated on right side.
PHSS_24202:
1) Currently there is a need to enable snmp packet tracing
in order to determine the reason why the snmp session was
opened - this introduces a huge amount of data for a small
piece of information. Using the 0x10000000 trace mask
traces open/close of SNMP sessions, but does not identify
reason for creation of the session.
2) Netmon process aborts with the following functions
contained in the stack backtrace (found in
netmon_err.log or drwtsn.log):
createLlaOnlyNode
_layoutDeviceTableEntry
This can happen when nodes that do not support
IP or IPX are configured to be discoverd in
an unmanaged state in the $OV_CONF/oid_to_type
file.
PHSS_24166:
1. In the Web Alarm Browser correlation display window
("Alarm Details"), long descriptive text fields are
truncated. If one attempts to view the fields by
scrolling, a blank window is encountered.
2. Alarm browser details window does not show events with
empty descriptive text.
3. Alarm browser details window corrupts text containing
'|' character
PHSS_24141:
When the ECS ScheduledMaintenance circuit was configured
with an OutageTimeSpecification that included a specific
WeekDay, the circuit could fail during the last seven days
of the month. In some cases the circuit fails to enable,
in other cases the circuit fails to suppress events during
an Outage. In either case, a range error is logged in the
pmd.log0 file.
PHSS_24069:
On some systems, the NNM process "ovdbcheck" dies
occasionally. This generates an OV_DBdown event in the
alarms browser, and the "ovstatus -c ovdbcheck" command
yields the following message:
Data Warehouse unaccessible. Exit(1)
This error is caused by a very transient condition. The
ovdbcheck process can be started again without any problem.
PHSS_24067:
If the user stops and restarts jovw.exe from the same
browser session, jovw did not receive automatic updates of
changes in the ovw map, e.g. symbol moves, deletes, etc.
PHSS_24018:
The mibExpr.conf(4) manpage implies that the COMBINED
syntax can be used with any type of indirection. Yet when
it is used with the "datarate" category, snmpCollect and
xnmgraph always fail to find any instances to collect on.
PHSS_24016:
If a previous invocation of snmpCollect ungracefully exited
without removing file $OV_DB/snmpCollect/snmpCollectPid,
then running "snmpCollect -S" will produce an error message
- as expected, but the PID number which it reports that it
cannot find is always "22".
PHSS_24008:
xnmsnmpconf -import will remove all characters after the
pound sign in community strings.
PHSS_24002:
xnmtopoconf will not run on a system with a limited
license.
Also,
xnmtopoconf -[un]manageobj station objects
gives the error
Error: station <whatever> is not the local station
if the station specified is a remote collection station.
PHSS_24000:
Pressing "OK" on the ovw Map Properties Dialog box forced
an ipmap synchronization even if no IP Map attributes had
changed.
PHSS_23977:
ipmap would core dump in OVwFormatSymbolType() when
attempting to write out an error message after failing to
create a new symbol.
[/opt/OV/lib/libovutil.2]
( 1) 0xc0bb4f44 _OVlogCrash + 0x264
[/opt/OV/lib/libovutil.2]
( 2) 0x000119b8 fatalSignalHandler__Fi + 0x8c
[/opt/OV/bin/ipmap]
( 3) 0xc0142c30 _sigreturn [/lib/libc.1]
( 4) 0xc0088800 strlen + 0x20 [/lib/libc.1]
( 5) 0xc0d806bc
send_string__8_BaseMsgFR11_MsgChannelPCc + 0x78
[/opt/OV/lib/libovw.2]
( 6) 0xc0d7cb44
sendParameter__8_BaseMsgFR11_MsgChannelR9Parameter +
0xa0 [/opt/OV/lib/libovw.2]
( 7) 0xc0d7de88 send__8_BaseMsgFR11_MsgChannel + 0x6c
[/opt/OV/lib/libovw.2]
( 8) 0xc0d8ec00 send__7_APiMsgFR11_MsgChannel + 0x3c
[/opt/OV/lib/libovw.2]
( 9) 0xc0dab5e4 _OVwFormatSymbolType__FPc + 0xa0
[/opt/OV/lib/libovw.2]
(10) 0xc0d92540 OVwFormatSymbolType + 0x1c
[/opt/OV/lib/libovw.2]
(11) 0x0002548c
formatSymbolCreateInfo__FP19OVwSymbolCreateInfoi +
0x9c [/opt/OV/bin/ipmap]
PHSS_23974:
On Solaris systems that have installed Cisco applications,
most NNM data warehouse commands (ovdwtrend, ovcoltosql,
ovcolsum, ovcoldelsql, ovdwevent, ovdwquery, ovdbcheck,
ovdweventflt and ovdwtopo) will abort with the following
error message:
ld.so.1: ovdwquery: fatal: relocation error:
file /opt/OV/lib/libodbc.so:
symbolSQLGetPrivateProfileString:
referenced symbol not found
This problem is observed on Solaris machines that set the
LD_LIBRARY_PATH environment variable to include (prepend)
a Cisco library path.
Note: This is primarily a Solaris problem; however, the
linking of the NNM data warehouse commands was revised for
all NNM platforms in order to preclude the possibility
of a similar problem on other platforms.
PHSS_23926:
Negative coordinates reported by APIs on Unix.
OVW could core dump if application called OVwCreateSymbols
() with less-than-filled out fields for the OVwSymbolInfo
struct.
PHSS_23924:
xnmgraph crashes when graphing live data from a node whose
Selection name is different from from its node name.
PHSS_23912:
Report Presenter can hang or abort when there is a very
large number of reports in the reporting directory. This
is most likely to occur if Daily reports are retained for
more than 3 or 4 months. In some cases reports were
displayed by the Report Presenter but not all of the
reports were displayed.
PHSS_23905:
ovw hangs when the open map is deleted and User Default Map
does not exist in the available maps list.
PHSS_23839:
The ovalarmsrv process can coredump if the correlation log
files get corrupted.
PHSS_23828:
1) Some 3Com switch devices have a SLIP interface with a
pre-configurd IP address. These devices get the
isBridge attribute cleared and will not do Bridge MIB
layout. This is true even if the SLIP address has
been added to the netmon.noDiscover file.
2) Netmon aborts with coredump (on Unix) or application
exception (on NT). The netmon_err.log file may show
a stack backtrace having many different possible paths.
3) When NNM is attempting to determine whether a node
down is a primary or secondary failure, it will
assume that an intermediate interface is still up
without checking it. It will not realize that
the intervening router is the one that has gone
down for maybe 30 seconds, given default polling
configuration.
PHSS_23779:
ovactiond does not format automatic actions properly.
PHSS_23775:
If there are no symbols selected in the map, the
"goto_levelAbove" toolbar button only goes up one level.
Subsequent button presses display the current submap. This
also happens with the menu pick "View->Up One Level".
Also, nodes with administrative status (Testing, Restricted
and Disabled) did not have their status colors displayed in
the scoping pane.
PHSS_23743:
A large volume of trend data exporting can cause
snmpCollect to exit because it cannot obtain a lock on its
binary database. This exit will occur when the "ovdwtrend"
or "ovcoltosql" commands are executed in order to export
the trend data. When this problem occurs, the following
entry will appear in the snmpCollect trace file
($OV_LOG/snmpCol.trace):
07/18/00 17:19:13 Cannot lock snmpCollect database
/var/opt/OV/share/databases/snmpCollect/. (Exiting
snmpCollect)
PHSS_23729:
If you configure a MIB collection for an object-id but
define it to be an EXPRESSION, then when you define a
collection on it, snmpCollect coredumps.
PHSS_23727:
In Ovlauncher the webappmon demandpoll window does not have
scroll bar.
PHSS_23703:
xnmbrowser crashes while describing MIB variable.
Also, NT dialog does not display all dialog items.
PHSS_23700:
1) Web alarm browser truncates long messages
2) Web alarm browser throws exception if many new events
arrive while scrolling
3) Web alarm browser doesn't show events with null messages
4) Web alarm browser blank screen seen while scrolling and
loading data
PHSS_23667:
OVsnmpConfPrint* functions fail with segmentation
violation on NT.
PHSS_23649:
When multiple sw loopback IP interfaces are present on a
node (typically a router) NNM does not consistently choose
the numerically lowest address, from among these sw
loopback interfaces, for node name assignment. This is
contrary to NNM node naming rules which, all others
influences being equal, favor the lowest address.
PHSS_23637:
ovdwevent -exportmaxrecords core dumps.
Stack trace shows the code in _OVEventDbFreeEvent
PHSS_23629:
If the "Submaps in Map" dialog box is displayed, and a
submap is deleted, moving the scroll bar or expanding a "+"
button would occasionally cause ovw to core dump.
PHSS_23607:
When there is no ICMP connectivity from the NNM system
to an IP address, netmon can not maintain status for
that IP address. This may happen if there is no known
IP route to that address, or if there is an intervening
firewall that does not allow ICMP messages to pass
through it. Netmon needs to be able to maintain status
on such IP addresses via SNMP, as long as at least one
interface on the monitored system is reachable via SNMP.
PHSS_23600:
The Service Information Portal (SIP) 2.0 alarm module needs
additional information from ovalarmsrv in the form of a
sortable timestamp for each event. Without this additional
timestamp, SIP cannot properly sort events by time when it
accesses an NNM server running in a different locale.
PHSS_23586:
Fault->Network Connectivity functions under the
web-based java ovw can sometimes cause the browser
to issue an "Internal Server Error". This is most
frequent using the Ping function but can happen
with other functions as well.
PHSS_23584:
ovtopmd can abort if a topology filter is enabled which
uses the sysObjectID, and a new MIB gets loaded.
PHSS_23582:
netmon hangs at irregular intervals.
PHSS_23473:
This fixes 2 related problems occurring with 2 different
applications, both happening on HPUX 11.x only :
OMNIBACK:
With a recent HPUX 11.x upgrade, OmniBack has problems
while starting/stopping ovstart/ovspmd: When ovstop is run,
ovspmd reports (for most of the NNM processes) that it
was forced to kill them, first with SIGTERM, then SIGKILL.
It then hangs, with the child processes all remaining up
as "<defunct>" processes, forcing the user to kill ovspmd.
MC/ServiceGuard:
Again, with a recent 11.x upgrade, ovstart/ovspmd are
having problems when invoked by MC/SG. But the symptoms
this time are during the ovstart phase: None of the NNM
processes ever get started, and ovstart hangs forever.
PHSS_23458:
The ovlaunch debug parameter does not work as intended
PHSS_23448:
When IT/O A.05.34 is running with NNM 6.1 on an HPUX 10.20
system, and a new node is added via IT/O menus, running
ovtopofix -c will remove the "IP Hostname" field from the
node, followed by an unsuccessful attempt to delete the
entire node. The field removal causes IT/O to function
incorrectly.
PHSS_23442:
When configuring event filtering with xnmevents:
1)Attempting to add a source that is already added does
not give a warning message in the case of "Add Selected"
button under the source tab of Filter Configurator, but
"Add" and "Add from map" buttons give warning messages.
2)In the same way, attempting to add a source with out
selecting any source gives an error message in the case of
"Add" and "Add from map" buttons but not in the case of
"Add Selected" button.
PHSS_23420:
mibExpr.conf file had some expressions which were wrong
and some comments had to be corrected, mainly for the
expressions which were using 64 bit values and high-speed
expressions.The corrections were under two files
/ovutil/mibExpr.conf and /ovutil/mibExprGuru.conf
PHSS_23404:
If ovdwevent -export is used to export
OV_Ack_Alarm, OV_Unack_Alarm, OV_Delete_Alarm,
OV_ChgCat_Alarm or OV_ChgSev_Alarm events, the
nnm_event_varbinds table of the data warehouse
database will only show a partial list of
the event_uuids of the events that were
acknowledged, deleted, etc. The rest will be
truncated. This only occurs if ovdweventflt
is used to filter these types of alarms.
ovdwevent -export can cause an ODBC error:
"Numeric value out of range",
if there are filters in place from the ovdweventflt
command and if a prior export has been done.
For the failure to occur, there should be data in
the nnm_event_limits and nnm_event_data tables.
This can be checked with ovdwquery.
This generally does not occur with the embedded
database, but only with databases such as Oracle
or SQL Server.
PHSS_23402:
In certain cases, if a user added a symbol to a submap
that was not created by ipmap the following error message
was generated in the event logs.SymbolMgr::findSymbol():
obj->getSubmap() failed. Map = default, SubmapId = 452,
ObjectId = 1515.
PHSS_23392:
jovw did not display all the status colors for connections.
PHSS_23364:
When using the Network Presenter (jovw) with the Netscape
browser running on HP-UX or Solaris, a hang in jovw can
occur when the initialization bar is at 10%. This hang
occurs when requesting a map OTHER than the map opened by
the first ovw session on the NNM platform. This would
typically occur when using the "MapName" directive in the
jovw URL. When this hang occurs, the java console will
display messages similar to the following:
<machine:sessionId> : map names do not match[map3 !=
default]
Can not get user name, using anonymous
PHSS_23348:
Network Presenter: Fault -> Network Connectivity -> Ping
and Fault -> Network Connectivity -> Remote Ping does not
show a continuous output as is documented in HP OpenView
Web Online Help.
PHSS_23346:
doOVFormatDate gives the same error message for two
different error sources.
PHSS_23344:
Would like NNM to be able to be given a list of SNMP
community strings to test for a given range of IP and/or
Ethernet addresses. Also would like NNM to maintain the
SNMP configuration database with this information. This
process is refered to as SNMP Community String Discovery.
PHSS_23330:
1)ovweb login fails with the following error message:
"PROCESS START FAILURE The ovsessionmgr process was not
able to start
2)For a node with multiple IP addresses, NNM may end up
using an address to name the node which is an address
that does not give SNMP connectivity. When this is
the case, menu-bar utilities that query the selected
node will receive timeouts.
PHSS_23322:
An ovw application created a transient submap when its
symbol was double-clicked (exploded). However, due to the
symbol's parent object and other applications interested in
that parent object, the application's transient submap was
immediately reset to persistent upon display.
PHSS_23220:
1. ovbackup.ovpl doesn't back up the $OV_WWW directory.
This includes the www configuration files as well as
the password files for users.
2. If the $OVSNMP_CONF_FILE variable exists (specifying
the location of the SNMP configuration database) and
ovbackup is run with the -d option (specifying the
location for the backup) then ovbackup returns an error
stating that the SNMP configuration database could not be
backed up.
PHSS_23211:
Bad sysObjectId causes ovtopmd on a Collection Station to
crash (Segmentation Violation) during synchronization with
Management Station (ovrepld).
PHSS_23209:
Message Box dialog used to display "Test SNMP" data does
not use scrollbars on Unix. So when testing a data
collection with a high number of instances (like a large
switch) the Message window can continue expanding beyond
the height of the screen. And since ther are no
scrollbars on the Unix Message Box window the initial
information reported from "Test SNMP" can't be seen.
PHSS_23199:
The system that a Management Station (MS) is running on is
rebooted, while 7 or 8 Collection Stations (CS) are still
connected to it. Then 30-60 minutes after the MS reboots,
pmd on 1 or 2 of the CS's shuts itself down, reporting a
"Select failure".
PHSS_23197:
When an OV_AppUngracefulExit alarm is generated, it causes
the following error to be logged to pmd.log0
L ERROR OV_EVENT:03 0000:0000 00000000:00000
000 Jul 19 17:07:28 ovEvent.C :2521
| PM_NO_ERROR
| Could convert V2 Notify to V1 Trap: Invalid
SNMP operation (OVsnmpErrno:10)
This means that the event can't enter the ECS engine, and
therefore is not a candidate for correlation. Consequently
it is not possible to suppress this alarm using ECS.
PHSS_23187:
1. There are several problems related to pmd/ECS
performance on NT. Processes such as netmon and
snmpCollect may not receive a pause event because the
event subsystem is busy. nmdemandpoll may fail because the
poll event does not get sent to netmon before timing out.
2. ovalarmsrv may hang or report a corrupt event header.
The web alarm browser will not display any new events or
respond to any operator actions.
PHSS_23157:
The user can double-click on an application while the
Modify MIB Application or Add MIB Application window is
currently displayed. This causes the window to be
corrupted and xnmbuilder eventually core dumps.
PHSS_23119:
Three symptoms are addressed in this Patch:
After Openview is started, using the "ovstart" command, on
Unix platforms, a "defunct" process is present on the
system until OpenView is stopped. The parent PID of this
defunct process is the PID of ovdbcheck.
The ovdbcheck process does not participate in OpenView
PAUSE and RESUME processing.
Some messages in the "ovdbcheck.log" file indicate database
connectivity errors when, in fact, the situation is normal.
PHSS_23008:
If a Collection Station (CS) is powered down, and during
that time its Managment Station (MS) is taken out of the
network and stays off line when the CS is powered back up,
the CS's Alarm browser will appear to hang for a long
period until the failed MS is back online.
PHSS_22973:
1. When an NNM system is configured as a Management
Station with remote Collection Stations (xnmtopoconf -
manage collectionstation) and then later ALL the
collection stations are unmanaged, ovrepld dies with an
illegal memory access in the copyStation routine.
2. ovrepld on the management station gets stuck in a loop
trying to get the status of an interface from a collection
station. The problem occurs when the collection station
fails and the management station does failover status
polling. While the collection station is down, the
management station determines that an interface is down.
When the collection station comes back up, that same
interface happens to be deleted on the collection
station. The MS keeps requesting interface status from
the CS, not knowing there is a delete request further down
in its queue.
No more updates are processed from the collection station,
but the most obvious symptom is that the Station Failover
Release in never observed in the Alarm Browser on the
management station.
PHSS_22954:
This patch addresses two symptoms when running the command
"ovdbsetup -o" to configure the NNM Data Warehouse for use
with the Oracle RDBMS:
1. This command does not check for the existence of
environment variable "TNS_ADMIN" which is optionally used
by Oracle to identify the location of the SQLNET/NET8
configuration files.
2. This command does not allow the user to optionally
override the location of the SQLNET/NET8 configuration
files.
PHSS_22952:
Network Presenter's menu action Tools->Web
Browser->Management Page incorrectly encodes the
ManagementURL attribute string as well as adding "http:"
and ":280". The URL finally invoked does not work.
PHSS_22808:
Network Presenter hangs at 40% during initialization phase
due to NullPointerException if submap has no toolbar
entries.
PHSS_22789:
1) Certain network devices provide many hints for
discovering new nodes very frequently. Because of this,
NNM ends up polling those devices every 5 minutes looking
for hints of new nodes to discover. This keeps the network
devices way too busy servicing NNM.
2) Netmon could abort if all tracing bits were turned on.
PHSS_22746:
If two non-interactive ovw sessions (ovw -copyMap, ovw
-deleteMap, or ovw -mapcount) are run at the same time,
ovuispmd terminates unexpectedly with the message "Forced
to exit before all clients unregistered".
PHSS_22725:
The NNM ovalarmsrv process aborted intermittantly when the
NNM events database contained events with long (>505 bytes)
event descriptions.
PHSS_22723:
Applications using ovsnmp library to receive V1 enterprise
specific traps and OVgeneric traps leak Memory for every
trap that is received. The leak stops if the sessions flag
OVSNMP_V2API is set.
PHSS_22666:
Customer Views submBld dumps core in getNetworkLocation on
Solaris2.7 with network count greater than 100. Core dump
happens after some organizations and resource associations
are added to the CV database (using ovcustomer).
PHSS_22659:
The NNM ipmap application can abort when doing a map export
(Map-->Export) operation. This problem occurs when a
location symbol is added to the Internet submap and then
network symbols are moved to the location symbol's submap.
Exporting a map with this configuration can cause the
ipmap abort. The abort happens most often on the
Windows/2000 platform.
PHSS_22645:
Administrative status colors (Unmanaged, Testing,
Restricted, and Disabled) were not correctly displayed on a
Network Presenter submap.
PHSS_22638:
i) Dashed lines of thickness greater than 1 are drawn with
thickness of 1 on Windows NT.
ii) Thickness of Connection class is not propagated as
default thickness for Connection sub-classes (types) with
no thickness specified.
PHSS_22582:
netmon aborts. Stack backtrace in netmon_err.log
(on Unix) or drwtsn.log (on NT) might include
the following sequence of functions in its stack
backtrace:
changeNetDefaultSeg ()
rmNetDefaultSeg ()
removeSegFromNetwork ()
removePrimarySeg ()
removeSegFromTopo ()
delSegCmd ()
PHSS_22580:
Events related to changes in the NNM topology
(such as status changes) are not being received
or acted upon by NNM.
PHSS_22577:
ovbackup does not back up symbolic links if they are in a
directory that contains subdirectories.
PHSS_22423:
Consolidated Patch
PHSS_22408:
1. A link up event from a router will pair with any link
down from the same router since the source is the agent
address. The link down in this case is correlated under the
link up, and the result a valid link down is hidden from
view.
2. If a child event was suppressed/correlated by a parent
event, the parent event was still output.
PHSS_22406:
When ovstop is executed or a system shutdown is performed,
pmd throws an exception or produces a core dump.
PHSS_22402:
xnmappmon core dumps on "demandpoll"
PHSS_22400:
On HPUX and SOLARIS systems when ovhtpasswd is run it will
accept passwords greater than 8 characters in length. When
logging into ovlaunch.exe with a password greater than 8
characters a message is displayed that states "Login not
recognized".
PHSS_22398:
When a secondary failure occurs and the ConnectorDown
correlation is enabled, the node status events for the
secondary devices should be correlated under the primary
failure. This correlation works correctly on the remote
Collection Station but not on the Management Station.
PHSS_22395:
1 When Generic traps are enabled and the event source is
set to "*", generic events do not correctly correlate
under the first event of each type.
2 When Generic traps are enabled and the event source is
set to "agent-addr", events do not correctly correlated
under the correct agent-addr source when the event sources
contain a '0' in the network address.
PHSS_22388:
JAGad12808:
Submitting a large string of data (5000 bytes) on
ovalarmsrv's listening port results in a core dump.
JAGad24341:
ovalarmsrv coredumps when new event categories exists.
JAGad24345:
ovalarmsrv exits abnormally when OVPORTAL is being
stressed.
PHSS_22386:
Two symptoms are fixed in this patch. First, if the $PATH
environment variable includes the path to a Java Runtime
Environment (JRE), NNM's ovrequestd process will fail if
this JRE is not compatible with the JRE that is shipped
with NNM. Second, when events are exported to the data
warehouse by the NNM Reporting facility (ovrequestd) on
Japanese systems, the event "message" field in the data
warehouse will contain garbage that looks similar to the
following:
"\203C\203\223\203t\203F\202\252\...."
The above "message" field can be observed, using ovdwquery,
with the following SQL statement:
select message from nnm_event_detail;
PHSS_22384:
For OvWebHelp, the background of the active toolbar button
was not always highlighted. As well for Japanese
OvWebHelp, some of the tool tips for the toolbar buttons
displayed in English rather than Japanese.
Note: In order to see the Japanese tool tips properly when
using a Unix netscape browser, the following resource must
be set:
*tipLabel.fontList:
-dt-interface system-medium-*-*-S*-*-*-*-*-*-*-*-*:
PHSS_22375:
When manually adding a node via the GUI, there is a small
chance that netmon will abort. The stack backtrace from
the netmon_err.log or drwtsn.log file will include the
following procedures:
netmon!clearCritRouteRefsInNet
netmon!moveNetToUnvisitedList
netmon!delIface
netmon!removeDupIface
netmon!addNodeCmd
PHSS_22355:
The installation of patch family [NNM_00575 PHSS_21997
PHSS_21998 PSOV_02758] causes sessionmgr to improperly
parse the roles defined in $OV_SHARE/www/etc/htgroup when
multiple users are included for a given role (e.g.
"NetworkAdmin: ovuser1 ovuser2"). Only the first user ends
up with items in the Web Launcher that include lines
restricting access to the problematic roles (e.g., "Access
NetworkAdmin;").
PHSS_22336:
When a user scrolled the list of submaps in the Submaps in
Map dialog box, Xt Warnings would appear and ovw would
eventually core dump. This was seen when a large number of
symbol classes were added to ovw.
PHSS_22334:
Whenever ovtrapd was recieving a 0 byte SNMP trap, it was
exiting with the message "EOF on recv() for SNMP trap".
PHSS_22332:
If a connection symbol had both a label and a text
annotation displayed, the text annotation overlapped the
label and made both hard to see.
PHSS_22301:
JAVA SNMP MIB Browser Object ID parsing.
PHSS_22299:
While not impacting the results of the code, the verbose
error messages are wrong because of a misplaced else
statement and may confuse someone trying to debug a
problem. Utilization data is returned and then the message:
" ifHighSpeed should be supported"
PHSS_22297:
In xnmevents, the same trap was being put under different
categories or with different severity at different times.
The Cu. had an enterprise specific generic trap (Link_Up)
defined along with the generic SNMP_Link_Up trap
definitions. At times, xnmevents used to treat the
enterprise specific generic trap according to
definition of the SNMP_Link_Up trap, and was showing it
with different (wrong) text and severity.
PHSS_22292:
In Solaris , the MIB browser crashes in case a space is
given in the MIB OID. While editing the OID , if a space is
typed by mistake , the browser immediately crashes and
dumps.
PHSS_22283:
xnmloadmib won't load mib which has default value of size
more than 64 bytes.
PHSS_22242:
Events that are configured as IGNORE or LOGONLY are passed
from the OV_EVENT stack to xnmevents or ovalrmsrv even
though they should not be displayed. Ultimately, the
events are not displayed, but handling these events in
xnmevents and ovalrmsrv is inefficient. This
causes
unnecessary CPU usage and reduces overall event throughput
to the Alarm
Browsers.
PHSS_22240:
The ovdbsetup* script(s) can fail and exit prematurely if
the shell's environment is different than it expects. This
script is generally only run by users right after an NNM
installation, when a user wants to replace the default
"flat-file" NNM db with Oracle or Informix or other db's,
and runs this script to set up the necessary connections
between the NNM installation and the Oracle (Informix, etc)
installation. And a related file - ovdbtrend_dsko.sh - in
the same directory ($OV_BIN) which is called by the above
scripts, needs similar fixes.
PHSS_22238:
ovactiond and snmpCollect man page missing -s option text
ovtopofix -I option and ovactiond -u option text incomplete
netmon.noDiscover link not working on netmon reference page
PHSS_22236:
Memory leak when adding and removing objects from ovwdb
object database.
PHSS_22221:
This patch addresses two symptoms:
1. The "-sumnoweekends" option of the "ovdwtrend" command
does not work properly. It abnormally terminates with the
following error message:
Cannot specify weekend filter when -si is not "r" or "d"
This error message is followed by a lengthy "usage"
message. This happens on all NNM platforms.
2. When SQL Server 6.5 is used for the data warehouse
repository, the "ovdwtrend -export" command will fail if a
MIB expression exceeds 256 bytes. The user will see the
following error message:
ODBC Error detected
MSG = [Microsoft][ODBC SQL Server Driver]String data,
right truncation
SQLSTATE = 22001
NATIVE ERROR = 0
During SELECT descript_id FROM snmp_trend_desc WHERE
mib_oid = ? and
mib_expr = ?
MSG = [Microsoft][ODBC SQL Server Driver]String data,
right truncation
SQLSTATE = 22001
NATIVE ERROR = 0
During SELECT descript_id FROM snmp_trend_desc WHERE
mib_oid = ? and
mib_expr = ?
MSG = [Microsoft][ODBC SQL Server Driver]String data,
right truncation
SQLSTATE = 22001
NATIVE ERROR = 0
During SELECT descript_id FROM snmp_trend_desc WHERE
mib_oid = ? and
mib_expr = ?
PHSS_22219:
In certain cases when reports are scheduled with the e-
mail option the reports are not generated and the e-mail
is not sent.
PHSS_22212:
ovbackup fails during the Data WareHouse backup with a
"FAILURE" message in the ovbackup.log file or with
a popup dialog box that appears after a supposed
sucessful ovrestore complaining of an internal SOLID error
(corrupt database).
PHSS_22210:
If the user rapidly selected/deselected the Set Filters...
dialog box for xnmevents, occasionally the dialog box could
lose its geometry and grow lengthwise. The only way to
restore the dialog box back to its default height is to
stop and restart xnmevents.
PHSS_22173:
The comments field for objects is limited to 256 bytes.
ovw, however, allowed the comments field to be greater than
256 bytes if the user included multibyte characters. ovw
would then core dump the next time it attempted to display
the properties for the object. This was also a problem for
maps, submaps and snapshots.
PHSS_22171:
There are several errors and omissions in the man page and
"usage" statement for the ovdweventflt command. Some
enhancements are also needed for the ovdweventflt command.
The command needs to display the NNM_EVENT_LIMITS table
contents and it needs to be able to clear this table.
PHSS_22153:
Using Internet Explorer, if a user brought up the Network
Presenter multiple times (e.g. by selecting an alarm in the
Alarm Browser and selecting "Show Node in Network
Presenter"), Network Presenter menu items did not work
properly on the second time. This was not a problem with
netscape.
PHSS_22130:
The root layout specified in the app-defaults file is taken
into account when the user uses "Map->New" menu option, but
status propagation is not. Similarly if he uses "ovw
-newmap" or "ovw -map" to create a new map, the status
propagation specified in app-defaults file is taken into
account while root layout is not.
PHSS_22115:
* When running ovw -fields, processing continues until an
exit with the following message:
-----------------------------------------
File: /etc/opt/OV/share/fields/C/<whatever>.fields
Line: xyz
Error: error setting enumeration value "some-field" for
field SNMPAgent: Connection to database lost
-----------------------------------------
* ovstatus on ovwdb would reveal that it had died on a
segmentation violation
* nettl standard log shows:
Fatal database error No space left on device (errno 28:
ENOSPC)
(But there is LOTS of space left on the disk)
* If you save the field definitions which ARE added (using
ovobjprint -e) to a file, then remove trailing CRs and
other miscellanous garbage, a "wc -c" represents the
field enumeration size for this installation. If it is
near or above 8k then it is likely that this problem is
present.
PHSS_22110:
When NNM receives a trap from certain network devices,
such as a Cisco Model AS5300 (IOS 12.0), netmon
sometimes exits ungracefully. The message in the
netmon.trace file is:
TRAP: topoEventDispatch returned -3: topo_error =
Cannot receive topology event: Received an
unexpected SNMP Trap or Inform message
PHSS_22108:
xnmloadmib will give a large number of warnings when
loading a mib with "--#ARGUMENTS {}" as part of the trap
definitions.
PHSS_22094:
Using $E in trapd.conf appends dot to variable
PHSS_22068:
The ovw submap background image of China depicts Taiwan as
a separate entity from China. Customers also want an image
of China where Taiwan is depicted as part of China.
PHSS_22064:
This problem can occur on all platforms supported by NNM
6.1 and all browsers supported by NNM6.1. This problem
occurs when the number of leaves or branches at any given
level in the NNM Report Presenter tree exceeds 64.
For example if the General Availability daily report has
been generated for the past 64 days the NNM Reporter
Presenter will list the 64 daily reports in the Inventory -
> General Inventory -> daily folder. On the 65th day when
the Report Presenter is displayed the page will not be
loaded.
If viewing the Report Presenter with Netscape Navigator,
select Java Console from the Communicatar -> Tools menu.
The following is displayed:
java.lang.ArrayIndexOutOfBoundsException: 64
at ax.a([DashoPro-V1.0-051598])
at hp.ov.reporting.TreePanel.parseTree([DashoPro-V1.0-
051598])
at hp.ov.reporting.applet.TreeApplet.init([DashoPro-
V1.0-051598])
* at
netscape.applet.DerivedAppletFrame$InitAppletEvent.dispatch
(DerivedAppletFrame.java:553)
at
java.awt.EventDispatchThread$EventPump.dispatchEvents
(EventDispatchThread.java:81)
at java.awt.EventDispatchThread.run
(EventDispatchThread.java:135)
at
netscape.applet.DerivedAppletFrame$AppletEventDispatchThrea
d.run
(DerivedAppletFrame.java:911)
If using the Report Presenter with Internet Explore, place
the mouse pointer over the left frame of the Report
Presenter page the following message is displayed in the
the Internet Explorer status bar:
"exception: java.lang.ArrayIndexOutOfBoundsException"
PHSS_22061:
The HP OpenView Console Login (ovlaunch.exe) allows access
to the HP OpenView Launcher Java application. The problem
is that the user must click in the login box in order to
begin entering his or her login information.
PHSS_22055:
This problem occurs only on HP-UX systems running NNM 6.1
in the Central timezone of the United States and Canada.
The primary symptom of this problem is that the NNM
Reporting feature will fail to generate any reports that
contain data. The reports will simply say that there is no
data available to report. An examination of the log file
"var/opt/OV/log/ovrequestd.log" yields further evidence of
this defect. Each entry in this log file is time-stamped.
If the time-stamps reflect GMT (for example,
Jul_7_2000_02:59:33_PM_GMT), then this defect is present.
(The time-stamps in the Central timezone should reflect CST
or CDT.)
PHSS_22051:
A router with some non-IP interfaces goes down. All
interfaces turn red. After the router comes back up,
all IP interfaces turn green within the status polling
interval (default 5 minutes), but the non-IP interfaces
remain red until one of two things happens: a demand
poll is done, or the configuration check poll happens
(default once per day).
PHSS_22049:
This is an NNM Data Warehouse problem.
The export of trend data (command "ovdwtrend -export")
and/or the aggregation of trend data (command "ovdwtrend
-sum") abort with a "primary key unique constraint
violation" error. Here is a sample error output:
$ ovdwtrend -export -sum
ODBC Error detected
MSG = [Solid][SOLID ODBC Driver][SOLID Server]SOLID
Database Error
10033: Primary key unique constraint violation
SQLSTATE = 23000
NATIVE ERROR = 10033
ERROR: ovcoltosql: Error writing data:
Note that while the above example involved the embedded
SOLID database, this error can occur with any type of
database management software.
PHSS_22028:
When items in the launch window are expanded, scroll bars
become active but do not function properly. Slider may be
missing, or may not allow scrolling to end of range.
PHSS_22026:
If a user closed the ovw exit dialog box via the window
manager instead of selecting OK or Cancel, the user could
no longer exit ovw via Map->Exit.
PHSS_22018:
Some interface contains colon (':') character in its
interface's description. In such environment, "xnmgraph"
fails to draw graph of 'Error Rate' & 'Error Percentage'
(ie ovw:Fault->Interface Errors->Error Rate &
ovw:Fault->interface Errors->Error Percentate).
Because colon (':') is the special character for the
"xnmgraph" to divide its input arguments of mib
specification.
For above operation, "ovexprguru" application will make
an expression and inputs for xnmgraph.
PHSS_21997:
ovsessionmgr may hang or abort.
active sessions become invalid after specified timeout.
apps using libovwww may experience memory leaks.
apps using libovwww may experience file descriptor leaks.
no implementation for _WebSession::GetUserPasswd().
PHSS_21930:
In xnmpolling, under "IP Discovery" configuration area,
the toggle button for "Fixed Discovery Polling Interval"
was not getting enabled even though fixed discovery polling
had been chosen previously.
PHSS_21920:
Java apps using LibOvw API hang in AsyncMsgChannel waiting
for a reply message when ovw server returns message too
quickly (fast server, slow client machines).
Network Presenter exhibits the hang with progress bar at
10% during initialization phase.
PHSS_21918:
All OVwDbGet<whatever> calls return invalid results if
LibOvw.OVwDbInit called instead of LibOvw.OVwInitSession.
PHSS_21916:
If $OVwBitmapDir was defined, ovw only searched the first
directory in the list rather than searching all the
directories listed.
PHSS_21870:
ovw would crash intermittently when viewing the capability
attributes of an object.
PHSS_21860:
Changes to the SNMP Address field of a node discovered
by a remote collection station are not propagated to
the management station.
PHSS_21851:
xnmgraph->view->statistics window doesn't show complete
statistics.
PHSS_21848:
xnmgraph gives application error when it graphs live SNMP
data from a device with lot of interfaces ( > 25).
PHSS_21846:
Selecting NNM->Patches and Updates from the help menu on
ovw causes an Invalid request.
PHSS_21839:
xnmcollect -snmpColConfFile <filename> fails.
PHSS_21837:
If ovw session is started to an X-terminal and xterminal is
turned off then, ovpause fails for ovuispmd.
PHSS_21823:
When a name that does not resolve to a valid IP address
is placed in the MaintenanceList parameter. The Scheduled
Maintenance event is not generated and events that should
be correlated under the Scheduled Maintenance event are
discarded instead of being correlated.
When a large number of events enter the correlation
the event throughput performance drops.
PHSS_21783:
Web alarm browser doesn't scroll to display the latest
alarm.
PHSS_21557:
Consolidated Patch
PHSS_21550:
pmd memory usage grows very large when the ECS
RepeatedEvents circuit is enabled, particularly if there
was a large number of events from many different 'key
combinations' (unique combinations of event source and
event type).
PHSS_21547:
The PairWise circuit outputs events immediately even though
they may be correlated within the PairedTimeWindow time.
If there is an automatic action associated with the event,
it still gets executed. It should be possible to suppress
these events, and therefore associated actions, if a
matching event arrives within the PairedTimeWindow.
PHSS_21538:
Availability Report was wrongly showing device as down when
it did not exist in the network
PHSS_21536:
On some systems with a long locale name, such as
"Norwegian_(Bokmid)_Norway.1252, ovw core dumped on startup
while loading bitmaps.
PHSS_21528:
ovsessionmgr refuses connections and/or hangs and/or
crashes after 60 sessions are created.
PHSS_21526:
ITO Developer's License could only manage one node and one
connector. Need license to manage 25 nodes and 5
connectors.
PHSS_21500:
On HP-UX ServiceGuard configurations that share "/opt/OV",
the Network Logging and Tracing facility (nettl) will FAIL
to start at system boot time even though the NNM
ServiceGuard Whitepaper recommendations (regarding shared
binares) were followed.
PHSS_21497:
ovcoltrim does not allow a user to delete reduced data
that has not been aggregated.
PHSS_21477:
After installing PHSS_21160 and its equivalents, for some
customers SNMP utilities like snmpwalk were resulting in a
timeout and were not getting the responses.
PHSS_21475:
"org" etc are hidden when you are way up to ".iso" on Java
MIB browser using Internet Explorer.
PHSS_21473:
If you build an application registration file (ARF) that
contains an "Enroll Connect" block as the first (or only)
Enroll block, then the "regverify" command that checks ARF
syntax will yield incorrect results.
Here is the incorrect Error output (where "reg1" is the
ARF):
=======================================================
$ regverify reg1
[parsing reg1]...
------------------------------
File: reg1
Line: 6
Error: fatal: internal error at grammar.Y(1509)
------------------------------
errors: 1, warnings: 0
>>>total: errors: 1, warnings: 0
------------------------------
PHSS_21441:
In the absence of name resolution for a node, and if the
node does not have a software loopback address, the name
should be set to the lowest non-migratable ip-address
PHSS_21416:
The -R option was added to the ovw -mapcount man page in
NNM6.01 however, it is missing from the 6.1 man page.
PHSS_21413:
libovsnmp library does not support encoding/decoding of
OIDs starting with .2.
PHSS_21407:
When the ECS Connector Down circuit is enabled, and the
extraAnalysis parameter is set to 'true', pmd memory usage
grows by a large amount.
PHSS_21405:
On NNM 6.1x, netmon will fail with a core dump (Unix) or
application exception (NT). At stack backtrace from the
netmon_err.log file (or drwtsn.log on NT) will show
the failure to be in the following area:
oldLlaEntry
layoutConnectorPortTable
dot1dBridgeActions
gotSnmpResponse
This will only happen if the "-k segRedux=true" option
is specified on the netmon command line. It can happen
in any network environment, but is especially prone to
happen in an environment where Cisco Fast EtherChannel
is being used.
PHSS_21403:
IPMap can dump core while handling changeInterfaceFlags
events.
PHSS_21401:
Creation of a new database for NNM 6.10 on Oracle 8.1.5
would fail because of obsolete parameters being
referenced. The script that would fail was ovdbsetupo1.sh,
and the parameters were "sequence_cache_hash_buckets" and
"sequence_cache_entries"
PHSS_21307:
After doing an ovrestore -analytical, the solid database
can fail to start (with various assertion failures). This
can be due to a missing log directory as specified in
solid.ini, or due to log file version mismatches.
PHSS_21297:
1) Certain catastrophic events can leave the NNM topology
database in a corrupt state. Such events might include a
power failure or a disk filling up. When ovtopmd reopens
the database after this event, sometimes it detects the
corruption, but silently starts up anyway. In one case, the
list of interfaces was corrupted, causing ovtopmd to
startup with no interfaces. This caused netmon to
rediscover all the interfaces again, and they would be
added to the map. All the old interfaces were still in the
map, making the map very hard to read.
2) When the NNM database is removed and rebuilt from
scratch, an event is generated which says that the license
will expire 60 days from now. This happens even if a
permanent license is installed. Ovstop/ovstart reverts to
the permanent license.
PHSS_21295:
OVw core dumps when executing using a popup menu to delete
a symbol that does not exist.
PHSS_21277:
Some of the on-line help and manuals had obsolete
information.
PHSS_21255:
The Cu. had misunderstood the purpose of -g option.
PHSS_21252:
Correlated Events cause Alarm browser to jump.
PHSS_21249:
There are three symptoms addressed by this patch. All
occur when assigning GIF image files as backgrounds for ovw
submaps. GIF image files produced by Microsoft PowerPoint
are likely to exhibit these symtoms. First, some GIF
images created by PowerPoint 97 fail to load as a submap
background. The error message is "Background graphic file
"xxx.GIF" cannot be loaded for submap "xxx". Second, some
GIF images produced by PowerPoint 2000 are not drawn
correctly in the submap background. These renderings are
completely unrecognizable. Third, some GIF images produced
by PowerPoint 2000 cause ovw to dump core when they are
being loaded as a submap background
PHSS_21245:
When a call is made to OVsnmpEventOpen() with a filter
parameter of approximately 4000 bytes length or larger,
either an undocumented SNMP_BUILD_PDU_ERROR will result,
or pmd will abort when the next event is received.
PHSS_21243:
netmon core dumps in function OVsnmpAsn_parse_int()
PHSS_21177:
Network Presenter will abort its search for a map if an ovw
session refuses a connection (i.e., if NP is not
registered). In addition, if 2 or more ports are
encountered which do not have an ovw session running, NP
will abort its search.
PHSS_21174:
As shipped in NNM6.0, ovdwevent exported "most" events
from the Binary Event Store. NNM6.1 shipped with the
default of only exporting the events directly used by the
reporting solution. Therefore, after upgrading to NNM6.1
the customer may not see all the events expected in the
Data Warehouse.
Since NNM 6.1 changed the types of events being exported to
the Data Warehouse, the NNM Excel Alarm Templates report on
significantly different data in NNM 6.1 than in NNM 6.0;
therefore, Excel spreadsheets based on these templates show
very different numbers in NNM 6.1 than in NNM 6.0.
The Excel availability templates are obsolete in NNM 6.1
and they are no longer shipped with NNM 6.1; however,
customers upgrading from NNM 6.0 will still have these
availability templates on their system. They do not
function correctly in NNM 6.1.
PHSS_21170:
Two defects are fixed by this patch:
1. java.io.EOFException's are reported to the Java console
from hp.ov.libovw.MsgChannel.peek when application is
not registered with ovw.
2. Network Presenter hangs sporadically at 10% stage of
initialization. Uninitialized variable causes null
pointer exception which can cause any Java libovw
application to fail during call to OVwInitSession.
PHSS_21168:
3rd party integrations that do not provide a 16x16 gif
image for a symbol end up with blank displays in Network
Presenter's scope pane and textual content view for nodes
using that symbol. The "generic symbol" should be shown
in these instances.
PHSS_21166:
When running the Report Presenter, strange characters may
appear in the browser display, or the Report Presenter
may abort.
PHSS_21162:
1)Netmon seems to always time out and abort its poll of a
certain device. This can be seen in the nmdemandpoll output
that netmon times out in the IP Addr table.
Another possible symptom of the same problem is that netmon
begins using a wrong IP address to query this certain
device. In the middle of a configuration check operation
(like nmdemandpoll), the address being used for the
requests changes from the correct address to a different
address.
2) Customer has many Cisco Catalyst switches with router
modules (RSM) in them. Whenever the customer reconfigures
the RSM to add a new IP address for a new connected subnet,
NNM discovers this new address as a distinct node rather
than adding the new address to the existing RSM node. The
only way to clear up the problem is to delete both nodes
and rediscover it. The version of IOS running in the RSM
is 11.2(16)P, but other versions may exhibit the same
behavior.
3) If the management station has not been discovered (for
example, if the management station is excluded by the
discovery filter), then it is possible that netmon can
abort when managing a network, or at other times.
The stack backtrace that shows up in the netmon_err.log
file (or in the drwtsn.log file on NT) should include the
following elements:
markTopoWithCritRoutes ()
recalcAllCritRoutesForTopo ()
manageRegion ()
4) Netmon aborts periodically. This has been observed when
the management environment includes an HPJ3210A
AdvanceStack 10BT switching hub management module.
PHSS_21159:
1. Utilities like snmpwalk, the mib browser were not reading
the NNM-INTERFACE entry in the ov.conf file.
2. xnmevents will core dump when you choose Actions->Alarm
Details
PHSS_21157:
ovw coredumps when a menuitem is deleted dynamically,using
the OVwDeleteMenuItem() call.
PHSS_21152:
IPMap will localize the "Internet" symbol label, even if
ipmap is run with "-u" option or with the
IPMAP_NO_SYMBOL_CHANGES environment variable set.
PHSS_21150:
If for one MIB entry more than 1 collections to the same
node are grouped together, then snmpCollect fails to
collect for all collection entries below this group.
PHSS_21146:
The ConnectorDown correlation does not correlate secondary
failure events under the primary node down event.
The ScheduledMaintenance correlation does not output the
ScheduledMaintenance event in all cases. When the change
event severity varbind is added to an event, the PairWise
correlation does not suppress the Delete Alarm or
Acknowledge Alarm events.
PHSS_21143:
If an application called OVwVerifyDrop() to deny a drop onto
a target symbol or submap, ovw would sometimes core dump.
As well, the error dialog box with the error message from
OVwVerifyDrop was not always displayed.
PHSS_21141:
When a crash log was created the user name was not included
in the log file.
PHSS_21139:
Alarm Browser displays threshold value as x.xx (2 digit
precision) whereas snmpColDump displays it as x.xxxxxxxx (
8 digit precision).
eg: If the Threshold value is 0.12688888, xnmevents
displays it as 0.13, and snmpColDump shows it as
0.12688888.
PHSS_21137:
OVwAddInput() fails when inside a callback since
SR4000134510. This api will generate a PERMISSION DENIED
error when OVwAddInput is called within a callback program.
PHSS_21135:
1) ovalarmsrv core dumps and cannot be restarted.
2) assigning an event to a new category causes ovalarmsrv to
dump core and be unstartable.
PHSS_21133:
If $OVW_BITMAPS/$LANG directory exists, ovw running under
$LANG cannnot find any of its bitmaps.
PHSS_21073:
The bitmaps for the MUX symbol had incorrect white
backgrounds.
PHSS_21015:
Japanese characters are garbled when an item in the treelist
is selected.
PHSS_20982:
A URL launched from the Launcher comes up with the incorrect
size and features.
PHSS_20938:
On Japanese systems, the event severity "Major" was cropped
in the xnmevents event browser
PHSS_20795:
Consolidated Patch
PHSS_20790:
When running Japanese NNM, there were certain help links
that were broken. These included links for CDE help,
WinNT help or webhelp. The links that were broken were
in the "What's New with NNM..." help topics.
-----------------------------------------------------------
Network Presenter has no "Find By ..." functionality.
-----------------------------------------------------------
Category string truncated by one char. The formatted
Category string selected by "$c" can have its last character
truncated off in certain cases. This was seen by customers
of HP OpenView Operations Center, but could possibly be seen
by customers of other OpenView Third-Party applications.
-----------------------------------------------------------
JAGab75821 : ITO trap interceptor dies on libovutil memory
overwrite.
This problem was seen only by HP OpenView Operations Center
customers, when the process "opctrapi" or "opctrapi.dll"
died and/or coredumped.
JAGab81561 : Need 2 ITO function names unmangled for NT
This problem will not be seen by customers outside of HP.
-----------------------------------------------------------
ovalarmsrv will fail to start if the default ports
2345 and 2346 are in use by another application.
-----------------------------------------------------------
ovrepld may abort with an application exception. This
has been seen on both Service Pack 4 and 5. Although this
problem has not been seen on Unix platforms, it is possible
that it could show up. The following excerpt from the
ovrepld_err.log shows the important part of the stack trace:
ovtopm!freeIfInfo+0x2d
ovtopm!freeObject+0x73
ovtopm!freeWrapperList+0x21
ovrepld!Action::~Action+0x16a
ovrepld!Action::`scalar deleting destructor'+0xf
ovrepld!CollectionStation::actionDone+0xe5
ovrepld!csAddedNewObject+0xd58
ovrepld!handleAction+0x37
ovrepld!Action::execute+0x31
-----------------------------------------------------------
When copying/pasting a symbol from the root submap into
another submap and then highlighting the symbol ovw core
dumps.
-----------------------------------------------------------
When running xnmevents with an Japanese EUC $LANG variable,
e.g. LANG=ja on Solaris or LANG=ja_JP.eucJP on HP-UX, the
right mouse popup window would sometimes show garbled
characters for the Japanese event text. As well, on some
Solaris displays, the events were not correctly displayed.
-----------------------------------------------------------
In some cases OVwDbListObjectsByFieldValues() returns some
incorrect objects that do not have all the field values
specified in the argument list.
-----------------------------------------------------------
On a symbol that is 'executable'. If the "Modify/Describe"
dialog box is brought up and the length of the dialog box
increased and then the 'Action' changed. The Selection text
box gets misplaced (sometimes its not visible).
-----------------------------------------------------------
Non-existent files specified in filter set definitions get
created with zero length. Can't specify a drive letter on
NT in a filter set definition.
-----------------------------------------------------------
pmd coredumps on SOLARIS and NT immediately after a trap
arrives from a broken SNMP agent that includes a VarBind
of type IPaddress which has a length of 0 instead of the
required length of 4 bytes.
-----------------------------------------------------------
On NT, with xnmevents in minimized state, if we make any
modifications through xnmtrap and then save, xnmevents will
hang using up 100% CPU time.
-----------------------------------------------------------
On Japanese NT, the Snapshot Properties dialog box was not
localized in Japanese. It also had no help topic. Finally,
it would occasionally cause ovw to core dump after it was
closed.
-----------------------------------------------------------
jalarm is unable to filter alarms by node names if they are
not fully qualified (no DNS in use).
-----------------------------------------------------------
If snmpCol.conf has multiple collection entries for the
same variable and same node, but with different instance
list, it fails to collect all the instances.
-----------------------------------------------------------
If one or more applications ungracefully disconnect from the
ovEvent stack ( part of pmd ), it is possible that pmd will
coredump with the function deleteApplication being in the
stack.
-----------------------------------------------------------
When ovrepld is sync'ing with a new collection station
(either at startup or newly-managed station), on NT, you can
not have nmdemandpoll successfully join the sync. It will
say one is already in progress. Future syncs will join OK.
Works fine on Unix platforms.
-----------------------------------------------------------
If an SNMP trap arrives at the management station which
contains 0.0.0.0 for the agent IP address, netmon will
sometimes abort.
If a router is configured to send SNMP traps to the
management station, and the router generates frequent
link-up traps, the management station can keep the router
very busy by doing a lengthy poll every time a link-up trap
is generated. This poll could include pulling the entire
ARP cache from the device.
When running ovstart, it appears that all the daemon
processes have started correctly. However, very shortly
after the ovstart is complete, it may be noticed that netmon
has terminated. An ovstatus will say that netmon is loading
its databases, but has exited with a status value of one.
When netmon does topology layout, it chooses a root device
which is the reference point for all the nodes/devices on a
subnet to position themself. If netmon choose a root device
that is not in NORMAL status on a subnet, netmon will not be
able to layout the topology for that subnet. All nodes in
that subnet will be put in segment1.
When managing certain Cisco devices with the newest IOS,
it is possible to see events containing the following
message:
"Agent in distress: spinning in ifTable. Aborting request!
Consider unmanaging node."
-----------------------------------------------------------
On NT, the "About Application Help" was missing from the
Event Export application.
-----------------------------------------------------------
When executing program sample app1, a symbol is added to the
submap and then is deleted after 20 seconds. Hold down on a
popup menu for that symbol until it is deleted then try to
execute the popup menu on it. ovw core dumps.
-----------------------------------------------------------
For 8606109734: Ovspmd sends OV_DaemonTerminated events when
daemons unexpectedly die. However, events are being
generated for processes being stopped by ovstop, and not
sending events for processes dying while ovstop is being run
for other processes or for processes that have been paused.
-----------------------------------------------------------
For 8606108882: Ovspmd uses the file
$OV_CONF/analysis/ovdwenvs.conf for setting the environment
variable SHLIB_PATH on HPUX and LD_LIBRARY_PATH on Solaris.
This is for Data Warehouse access to the ODBC libraries and
database drivers.
However, in setting this variable, ovspmd overwrites the
value rather than prepending the value from
$OV_CONF/analysis/ovdwenvs.conf. Third-party applications,
that rely on these variables to operate, are broken by the
fact that the environmental variable does not contain the
value specified at the starting of ovspmd.
-----------------------------------------------------------
ovmapcount -ruvD dumps core.
-----------------------------------------------------------
Web ARF items incorrectly ordered (precedence and
application name ignored) in Launcher, NetPresenter and
regverify.
NetPresenter:
Menus and toolbar buttons do not gray according to
selection rules and min/max specifications.
TargetSymbolType ignored for popup menus
PopupMenu in ARF not handled correctly
(cascading menus from popup not functioning)
-----------------------------------------------------------
Loadhosts command not working correctly using the syntax
loadhosts -p -c [IP Address] -n #. It should ping each of
the ip addresses starting at the initial address and
counting up # number of nodes. If the ping does not return
a response, the node will not be added. Using this command
on a range with actual machines in this range, the response
returned is always ping timed out, regardless of the
presence of a physical machine. Executing a simple ping to
the ip address does work, however the -p switch will not.
-----------------------------------------------------------
This is a problem on Windows NT only.
loadhosts -p -c [IP Address] -n # should ping each of the
ip addresses starting at the initial address and counting
up # number of nodes. If the ping does not return a
response, the node will not be added. Using this command
on a range with actual machines in this range, the response
returned is always ping timed out, regardless of the
presence of a physical machine. Executing a simple ping to
the ip address does work, however the -p switch will not.
-----------------------------------------------------------
This is a problem on Windows NT only.
Ovdbcheck cannot connect to the embedded database engine,
ovdbrun, after ovdwconfig.ovpl -type embedded is run. This
leads ovdbcheck to fail, and ovstatus -c ovdbcheck will show
that the database is inaccessible.
-----------------------------------------------------------
In Japanese, the label for "TopM Connector Count" was
incorrect.
-----------------------------------------------------------
On Japanese NT, only one digit is displayed for the seconds
column for events. This happens for events with dates in
October, November and December. This did not happen on
non-Japanese NT systems.
-----------------------------------------------------------
New alarm categories are clipped in Japanese mode, this is
particularly bad when the number of categories exceeds 8.
-----------------------------------------------------------
If the various environment variables provided by ovw
(OVwFieldDir, OVwRegDir, and [most notably] OVwSymDir) are
set and include trailing language-specific components in
the paths, Network Presenter will fail to read symbol
information. All symbols will show up with generic icons
in its scope (leftmost) pane, and no symbols will show up
in the graphical content pane.
-----------------------------------------------------------
If you set a background graphic in a submap, then change
the background graphic to a different one, the next time
you start ovw the graphic displayed will be the first one
applied.
Ex.
Open OVW, apply the Colorado graphic to the Root Submap,
Changed the Colorado graphic to California for the Root
Submap,close OVW and reopen.Root Submap displays the
Colorado graphic.
-----------------------------------------------------------
rnetstat will crash with an exception violation when
querying the routing table from a NNM NT Management Station.
-----------------------------------------------------------
If a new application is created through xnmbuilder and then
ovw is restarted and the menu path for the new application
is edited, it doesn't get written to the application
registration file. This causes the menu item to disappear
next time ovw is restarted.
-----------------------------------------------------------
Select a symbol in ovw and try to change its symbol type.
When the symbol type dialog box comes up do a selection so
that no one symbol type gets fully selected. This leads ovw
to coredump.
-----------------------------------------------------------
xnmloadmib leaks huge amounts of memory when loading mib
files. Results in malloc failures.
-----------------------------------------------------------
After installing ITO to work with Oracle 7.3.4 on HPUX
10.20, running ovdbsetup -o can cause ITO daemon ovacomm to
not run. Ovstatus reports back that the daemon died with a
signal 6 due is an unresolved reference.
Also, the Data Warehouse programs may or may not work. They
also receive unresolved references.
-----------------------------------------------------------
Programs snmpCollect and ovcoltosql can corrupt binary data
files in $OV_DB/snmpCollect if the disk fills. The write
will only write the available space which might be less than
the size of the fixed-length record. Once this occurs, then
the binary datafile is corrupted, and while subsequent
writes will work, it will not be able to be read by
ovcoltosql or snmpColDump.
-----------------------------------------------------------
The ipmap process appears to hang when it is doing the
initial map synchronization at map open time. In reality,
it just takes a very long time. Looking at the map reveals
that there are a huge number of segments attached to a node
which does not have this many interfaces (could be thousands
of interfaces).
-----------------------------------------------------------
NNM/NT6.0 Japanese and NNM/UNIX6.0
Japanese:
When upgrading 5.0x to 6.0, alarm category labels aren't
converted from
"xxx Events" to "xxx Alarms".
-----------------------------------------------------------
Timestamps such as creation time and modified time are
different between the operational database, evaluated by
ovtopodump -l <oid>, and the relational database. The
relational database timestamp is the timestamp that the
entry was added and not the creation or modification time
of the object.
-----------------------------------------------------------
xnmcollect will give Internal Error when you select multiple
Mib Objects and then do one of Copy or Modify or Show Data
menu operations.
-----------------------------------------------------------
A large event that can be formatted by xnmevents cannot be
handled by ovactiond resulting in an error message in
ovactiond.log
-----------------------------------------------------------
Upon running ovstop, on occasion, ovalarmsrv will get killed
with a signal 15. This is due to ovalarmsrv not having
enough time to finish writing to the statelog.
-----------------------------------------------------------
On 11.0 systems, ovalarmsrv would generate one of the
following two messages after running for a period of time:
First possible message:
ovalarmsrv opening connection for listener port.
ovalarmsrv opening connection for service port.
MSD thread exception: pthread_create failed , code = 11
Exiting!
Second possible message:
ovalarmsrv opening connection for listener port.
ovalarmsrv opening connection for service port.
MSD thread exception: pthread_detach failed, code = 3
Exiting!
These messages would appear under
/var/opt/OV/share/log/ovalarmsrv.trace and the ovstatus
of ovalarmsrv would be something to the effect of
"MSD thread exception: ... failed, code ??, exiting."
-----------------------------------------------------------
When MapHeight and MapWidth are set in the NT Registry as
resources for ovw, MapHeight seems to be ignored.
-----------------------------------------------------------
If large numbers of submaps are open at once, when the user
opens up yet another submap, ovw either core dumps or the
new submap has unusable menus.
-----------------------------------------------------------
ovdwevent -export doesn't populate the event message field
in either the solid or oracle databases. The message field
doesn't exist.
-----------------------------------------------------------
If you modify the ipmap registration file, and add "-D n",
existing maps can have their persistence level changed
without required synchronization. Changes to the ipmap
registration file are supposed to modify new maps (or maps
being migrated from pre-3.31 versions) only, not existing
maps.
-----------------------------------------------------------
When opening xnmappmon with the -commandHeading option,
using Kanji characters in that command heading. The
bottom couple of pixels of some of the Kanji characters
are truncated.
-----------------------------------------------------------
If IP Addresses are specified in the event source file, then
events are not put in the proper category.
-----------------------------------------------------------
xnmcollect either reports an internal error or core dumps
(or does none of the above but will still have a memory
error if NT), when you modify a mib collection, delete
that mib collection, and then add a new mib collection.
-----------------------------------------------------------
When installing a permanent license, the license expiration
date in the global topology object in ovwdb is formatted
incorrectly, giving the (false) impression that the license
expired in 1970. The license still works, but it looks
wrong.
-----------------------------------------------------------
start Data Collection & Thresholds: /opt/OV/bin>xnmcollect &
select any MIB object and double click on the only entry
in the MIB object collection summary. A window pops up to
modify the MIB object choosen. Delete the default entry in
Polling interval and choose Configure Threshold
Event/Configure Rearm Event button. An error messages pops
up with the following message, which is not clear.
empty string on string "". Usage: <NUMBER>[smhdwy].
It should have been empty string on Polling Interval.
-----------------------------------------------------------
If the number of lines to be graphed exceeds 25 then only
the first 25 lines are displayed. On UNIX its possible to
change one of those lines being displayed with another one
which you want to see. On NT its only possible to add more
lines to the display.
-----------------------------------------------------------
Collect data over a large period of time using snmpCollect
and then graph it using xnmgraph. Now change the display
width to a small value and try to move the "Display
Interval" scroll bar position. You will see that the scroll
bar button always returns to somewhere near the starting
position.
-----------------------------------------------------------
When selecting "current license" in the ovnnmPassword
dialog, only licenses that have a start date that is current
will show up. Any licenses with a start date in the future
will not be shown.
-----------------------------------------------------------
When pressing on the first link listed in the launcher
welcome page, an error is presented because the URL does not
exist.
-----------------------------------------------------------
If you start moving around a symbol that an application
subsequently deletes, ovw core dumps.
-----------------------------------------------------------
On double clicking an explodable symbol with a submap
attached to it, if the parent submap is closed before the
child submap can come up, ovw coredumps.
-----------------------------------------------------------
In a EUC kanji japanese environment, xnmevents core dumps
with SIGBUS for certain events.
-----------------------------------------------------------
findroute coredumps when an agent returns an invalid ifIndex
-----------------------------------------------------------
If the value of noReducePercent in the
/usr/lib/X11/app-defaults/XNmgraph file is set to either 99
or 100% then xnmgraph hangs when graphing certain
collections.
-----------------------------------------------------------
When starting openview services from the NT start menu,
there is no notification that startup has completed.
Defect Description:
PHSS_24797:
Cumulative Consolidated Patch
Resolution:
Cumulative Consolidated Patch
PHSS_24785:
The test added in PHSS_24442 to detect null strings prior
to checking "access" contents was not parenthesized
correctly.
Resolution:
Code changed to correctly test "access" contents.
PHSS_24775:
libovsnmp: Mis-handling of the forwarding of traps from
CMIP to SNMP.
libovEvent: Mis-handling of the reporting of errors in the
forwarding of traps from CMIP to SNMP.
Resolution:
Large CMIP traps in dual NNM+DM installations no longer
coredump pmd. An informative error message is put into
$OV_LOG/pmd.trc* warning of the discard of the oversized
trap.
PHSS_24773:
The polling logic assumed that if SNMP status polling was
turned off (per the nonIPStatusPolls=false option) then
the device should be pinged.
Resolution:
For level2 devices, the nonIPStatusPolls flag is checked
before trying to determine which type of polling should be
used.
PHSS_24768:
Netmon could core when discovering devices with invalid
sysObjectIDs.
Resolution:
The code has been fixed to check the sysObjectID before
storing the information in the database.
PHSS_24764:
This problem is caused by the fact that netmon will
attempt to read the entire interface table on the
device, and it will consume too much memory to hold
all that information.
Resolution:
A new flag has been defined which may be used
in the oid_to_type file. See the oid_to_type
reference page for the N flag. This flag
will cause netmon to only pull entries from
the interface tables which are associated
with entries in the ipAddrTable. This will
leave the vast majority of entries in the
interface tables unread, and thus will not
consume excess memory and network bandwidth.
PHSS_24748:
Function _OVinetHostAddress does not handle hostnames
larger than 256 characters properly.
Function OVmib_read_numeric_objid does not do any boundary
check when converting object-id strings to array of sub-
ids.
Resolution:
_OVinetHostAddress function now returns proper error
values when the hostname is larger than 256 characters.
OVmib_read_numeric_objid does boundary check on the passed
array.
PHSS_24746:
There is a timing condition which will
be hit occasionally where netmon will
be trying to use SNMP to poll the status
of a non-IP interface, but it does not
find what it expects. This can happen
on any version of the netmon binary
dated March 2001 or later.
Resolution:
Netmon has been modified to handle
more gracefully the unexpected
condition, and it will no longer
abort.
PHSS_24731:
The cause of the problem stems from binding the IP address
in $OV_CONF/ov.conf to the connection to pmd. This
interface, specified by NNM_INTERFACE, does not exist on
the remote console, and consequently, the bind fails. The
logic should have only been entered if running on the
server.
Resolution:
Remote consoles can not bind sockets to IP address
specified in $OV_CONF/ov.conf. The logic did not take
this into account.
PHSS_24726:
When xnmcollect is used to configure threshold and rearm
values it writes these values using fprintf("%g"). The
values thus get rounded off when they are written to the
snmpCol.conf file.
Resolution:
The format used when threshold and rearm values are
written has been changed from fprintf("%g") to fprintf
("%.15lg"). This prevents rounding off unless the values
are greater than 15 digits.
PHSS_24721:
On Unix, ovhelp creates the path for the message catalog
that the help viewer is going to use. The path includes
the $LANG variable. Unfortunately, ovhelp did not allocate
enough space for the name of the help file, which sometimes
caused memory to be overwritten and caused a segmentation
fault, especially if $LANG was a short name such as "ja".
Resolution:
ovhelp now allocates enough space to build the message
catalog path name.
PHSS_24719:
Filter sources are internally stored in a Hash Table, with
hash slots being determined by integral summation of
characters in source string. Sources with equivalent Hash
slot values are chained in a linked list in their slot.
When the eventFilter is exported, a check is made to
eliminate exporting of duplicate entries. A defective
comparison is made which results in some non-duplicated
entries being omitted from exported event Filter.
Resolution:
Correct the defective comparison call.
PHSS_24713:
The symbol did not have its proper placement set when the
point-to-point submap did layout, forcing the symbol down
to the holding area region.
Resolution:
The symbol is now properly placed before the point-to-point
submap does layout.
PHSS_24675:
snmpCollect validates the instances of MIB expressions. If
there is a large number of MIB expressions in snmpCol.conf
file, it results in slow startup of snmpCollect. The
existing options "-I always" and "-I startup" do not
provide any performance improvement in case of MIB
expressions, even if the instances are specified.
The customer wants the same capability in NNM6.1, that
they had in NNM5.01, about being able to turn off the
check when snmpCollect is evaluating MIB expressions.
Resolution:
Provided two options "-I startupNoExprChk" and "-I
alwaysNoExprChk" that was added in NNM5.01 through the
patch PHSS_19925. Using these options the customer can
decide to turn off validation of expression instances
either only for the startup or always.
PHSS_24666:
When the ScheduledMaintenance circuit determined that the
next Scheduled Maintenance period was in the next month,
the month was incremented but the day was not
reinitialized to 1. This caused the ScheduledMaintenance
circuit to fail to determine the next Scheduled
Maintenance period and alarms were not correlated.
Resolution:
The appropriate parameter is now reinitialized under these
circumstances.
PHSS_24442:
There are 2 defects. The Java engine has a known defect
that causes the null-pointer exception when it is passed
an empty list.
But the ultimate cause of the problem is that
ovlaunchreg.exe is passing this empty list as its output,
when it should not be doing so. When no group-level
restrictions are placed in the registration files, then
all users should have access to all menus and tabs, even
those users who are not included in any groups in the
htgroup file.
Resolution:
The Java applet with the "40%" figure now completes its
task, and the "HP OpenView Launcher" window comes up as
expected.
PHSS_24415:
The NNM 6.1 ovrepld process and the NNM 6.1 xnmtopoconf
command do not recognize the topology database version used
in NNM 6.2.
Resolution:
xnmtopoconf and ovrepld in NNM 6.1 were changed to accept
the topology database version used by NNM 6.2.
PHSS_24411:
In some cases a node gets deleted from the object database,
but the database cache does not get cleaned up properly.
This cache problem prevents the node from subsequently
being added back into the object database.
Resolution:
The code was modified to properly clear the cache when a
node is deleted from the object datbase.
PHSS_24362:
ovw did not do error checking when reading in gif89 images;
corrupted images caused ovw to overwrite memory.
On ovw startup, the initial home submap displayed did not
have its user-initiated reference count set. Network
Presenter uses OVwLoadSubmap and OVwUnloadSubmap to load
and unload its submap. The OVwUnloadSubmap call when
Network Presenter exited caused the home submap to be
closed because its user-initiated reference count was not
set. If there were no other submaps displayed, the root
submap was displayed in its place.
Resolution:
ovw now performs additional error-checking when loading
gif89 images.
ovw also now sets the user-initiated reference count on the
home submap when it is displayed upon startup.
PHSS_24297:
Web Alarm Category window widths were hard-coded in CGI
program that generates HTML parameters. Did not account
for number of characters in labels nor the size of font
with which they are displayed. Window content was centered
and allowed buttons and text to roll off both sides.
Resolution:
ovalarm.exe has been modified to detect wide labels and
generate maximum widths needed to allow proper display of
buttons and labels. It attempts to account for wider fonts
used in certain locales. Window contents are now
left-justified.
PHSS_24202:
1) The tracing feature of netmon does not include the
reason for opening an SNMP session when tracing
the session creation.
2) The process of adding the non-IP node in an
unmanaged state will cause an abort if there
is a failure to add the node to the database.
Resolution:
1) The SNMP session tracing messages have been
enhanced to include the reason for creation
of the session.
2) The netmon process has been changed so that it
will not abort when it encounters an error adding
a node to the database.
PHSS_24166:
1.The component used to display alarms in the details
window had some internal limitations and implementation
deficiencies which prevented it from displaying text
messages longer than the screen width. Its scrolling model
failed when zero-width columns were included (as does the
alarm browser)
2. Parsing was incorrect for empty fields
3. Internal mechanism used '|' character as separator char.
Resolution:
1. Replaced tree control component with more robust version
2. Fixed parser to handle empty fields.
3. Replaced internal mechanism for storing field info.
PHSS_24141:
The ScheduledMaintenance circuit is designed to handle an
end of month transition, but in one instance an internally
calculated month day value being used in an intermediate
calculation caused a range error even though the value was
valid in that instance.
Resolution:
The ScheduledMaintenance circuit will no longer throw a
range error in that particular case.
PHSS_24069:
This problem is caused by a transient condition where
ovdbcheck fails to connect to the data warehouse's embedded
database. ovdbcheck subsequently aborts.
Resolution:
The ovdbcheck code was modified to retry the database
connection twice before giving up. Since the error
condition is very transient, this keeps ovdbcheck from
dying. The code was also modified to gather more
diagnostic information about the connect failure which
will be placed in the ovdbcheck.log file. (It is
still not known why this connection failure occurs.)
PHSS_24067:
jovw was not properly re-initializing its state when it was
restarted from the same browser session.
Resolution:
jovw now reinitializes correctly when restarted from the
same browser session.
PHSS_24018:
The COMBINED keyword only worked with the utilization
indirection category, but the manpage failed to mention
that.
Resolution:
First, libovutil has now been changed so that COMBINED
indirect collections work with both the datarate and
utilization categories (but no others). Secondly, the
mibExpr.conf(4) manpage now states this fact.
PHSS_24016:
Instead of printing the PID number, it was printing the
signal number it was trying to send to the PID (SIGIO = 22)
Resolution:
The error message now includes the correct PID number.
PHSS_24008:
The pound sign indicates the start of a comment. The
function that read each line from the imported file would
search for the pound sign and ignore any text after
it.
Resolution:
To allow pound sign within community strings, the pound
sign should be prefixed with a backslash.
The function that reads lines from the imported file has
been changed so that it now checks if a backslash prefixes
the pound sign. If so, it is no longer considered a
comment but part of the configuration entry.
PHSS_24002:
xnmtopoconf is meant to manage remote collection stations
and therefore the requirement that its system have an
unlimited license is by design.
The restriction on the station during a manageobj or
unmanageobj is because of additional functionality that
was never implemented. Despite the fact that from the man
page or usage you might infer the station specified in an
[un]manageobj can be remote, this was in fact never
implemented.
Resolution:
The usage text (xnmtopoconf -?) and the man page (and NT
NNMRef.hlp file) will be corrected to make it clear that
the station specified in a manageobj or unmanageobj must
be the local station.
PHSS_24000:
ipmap did not check to see if any IP Map attributes had
changed before starting the synchronization.
Resolution:
ipmap now checks to see if any IP Map attributes have
changed, and only performs the synchronization when at
least one attribute has been modified.
PHSS_23977:
When ipmap failed to create a symbol it attempted to log
certain symbol info fields which were not valid.
Resolution:
ipmap only logs those symbol info fields which are valid.
PHSS_23974:
This problem is caused by conflicting versions of odbc
library "libodbcinst.so". Both NNM and Cisco use this
library but, unfortunately, they use different versions of
this library. When the LD_LIBRARY_PATH environment variable
prepends the Cisco library path, the NNM data warehouse
commands attempt to use the Cisco version of the library
instead of the NNM version.
Resolution:
Modifications have been made to the software build process
for the data warehouse commands. They are now built in
such a way that they will not be influenced by
LD_LIBRARY_PATH when loading the odbc libraries at run
time.
PHSS_23926:
Layout was not being done when needed or layout needed to
be disabled until all symbols were moved.
The local variable sym_type in ovwCreateSymbols() was not
initialized and could be accessed without being set first.
Resolution:
Added call to layout or disabled layout until all symbols
were moved.
Initialize the local variable sym_type in ovwCreateSymbols
PHSS_23924:
We use the node name, as returned by ovexprguru, to
retrieve the object Id (Ovw Id) instead of using the
Selection name, through OVwDbSelectionNameToObjectId().
Resolution:
Use the Selection name in retrieving the Object Id of the
node instead of the node name.
Also, to prevent any crash from occurring, validate any
data retrieved using the above object Id.
PHSS_23912:
There were two causes for this problem: 1) the algorithm
for traversing the Reports directories did not properly
close the directories when done. 2) The buffer for
sending the report tree to the web browser sometimes
overflowed.
Resolution:
The reporting directories are now closed when
nnmRptPresnter is done traversing them. The Java report
tree buffer is now sent to the browser with multiple
writes of a size suitable to the operating system.
PHSS_23905:
If the map name appearing as User Default Map does not
exist in the maps list, ovw tries to open a non-existent
map and hangs.
Resolution:
An error message is displayed indicating that the User
Default Map does not exist in the maps list and directs the
user to choose a valid map name from the maps list and set
it as User Default Map.
PHSS_23839:
The logic which deals with corrupted, or non-existent
correlation log files, does not handle a correlation count
of zero correctly.
Resolution:
The code which handles a zero correlation count has been
fixed to deal with corrupted or non-existant correlation
log files.
PHSS_23828:
1) The existence of the SLIP address causes netmon to
count more than one IP network that this device
is connected to, and this prevents bridge MIB
layout from happening. Also, this is counted
before the netmon.noDiscover addresses are
applied.
2) There is a case if the user's network contains certain
network devices (from Cabletron, and possibly some
other vendors) which require the L flag to be set
in oid_to_type, but the flag is not set as it should be.
After a number of map edits, this can cause the device
to have an interface object stored in the NNM database
as being connected to a segment, but not connected to
any netowrk. This is an unallowable state which can
cause netmon to abort.
3) When netmon checks the elements along the critical
path, it will not status-check an interface if
it has been checked "recently", where "recently" is
defined as "10% of the configured status poll interval".
Resolution:
1) Netmon has been changed so that it will check the
netmon.noDiscover file for an address prior to
counting that address as a potential network
connection. Also, interfaces with 192.168.101.1
which are SLIP interfaces will not be discovered
at all (unless a 192.168.101.0 network exists in
the database), so that there will not be lots of
"Duplicate IP address" events generated needlessly.
2) Netmon has been modified so that it will check
for interfaces being connected to segments
but not being connected to networks, and will
connect the interface to the network that the
segment belongs to.
3) Netmon has been changed so that the definition of
"recently" is "within the last second".
PHSS_23779:
The formatting function used by ovactiond was not the
right one to use.
Resolution:
Now ovactiond calls a different formatting function for
automatic actions.
PHSS_23775:
jovw did not properly reset the focus cursor in the scoping
pane if there were no symbols selected in the map.
Also, nodes with administrative status were inadvertently
excluded from the list of nodes with their colors
displayed.
Resolution:
jovw now correctly resets the focus cursor regardless of
selection.
Also, the jovw scoping pane now displays the status color
for nodes with administrative status.
PHSS_23743:
Whenever trend data is exported, the "ovcoltosql" command
locks the snmpCollect binary database long enough to move
the binary collection files to a working directory. If the
number of collections is large enough, the file move
operation locks the database for too long and snmpCollect
exits because it cannot obtain the database lock.
Resolution:
Instead of locking the snmpCollect binary database for one
long duration time period in order to move all the binary
collection files, ovcoltosql is being changed to process
the binary collection files in smaller groups. The
database will now be locked for the move of each group, but
the duration of each lock will be much shorter since fewer
files are being moved in each group.
PHSS_23729:
When parsing through the MIB entry in snmpCol.conf
snmpCollect checks if the object id does NOT start with
a ".". If so it assumes that the MIB defined, is for an
EXPRESSION. Else it assumes that the MIB defined is for an
object-id. However no check is done to see if the type of
the MIB definition is EXPRESSION or otherwise. Down the
line however this causes snmpCollect to try go get
information on this expression and it coredumps.
Resolution:
Now if a MIB is defined for an object-id then a check is
done to see if the type is EXPRESSION. If so snmpCollect
errors out with a message.
PHSS_23727:
The registration file snmpviewer did not have the code
part to implement the scrollbar.
Resolution:
The registration file snmpviewer was modified to provide
scrollbar in webappmon demand poll window.
PHSS_23703:
The buffer used to hold the Objects and Index strings are
not large enough, causing buffer overrun. Also, we did not
check for the possibility of buffer overrun and prevent it
from happening.
For NT dialog, it was simply a mismatch between Unix and NT
dialogs.
Resolution:
- Increment the buffer size to 1K and add code to detect
and prevent buffer overrun by truncating string to fit into
buffer.
- Update NT Describe MIB dialogs to include Units, Index
and Objects dialog items.
PHSS_23700:
Text truncated due to internal limitations of component.
Data cache did not grow in some cases.
Parsing was incorrect for empty fields.
Scrolling caused too many pages to be loaded.
Resolution:
Replaced table component with more functional version,
allows traversal within text cells to view data.
Changed cache so it is dynamically resized.
Fixed parser to handle empty fields.
Changed scrolling to defer motion until scroll is released.
PHSS_23667:
When developing applications using the OVsnmpConfPrint*
functions on NT they need to be built with the /MD option
instead of the default /MLd option.
Resolution:
The man pages are changed to inform the user to use /MD
option instead of the default /MLd option when developing
applications on NT using the OVsnmpConfPrint* functions.
PHSS_23649:
The NNM node name selection routine, chooseNodeName(), used
the address of the first sw loopback interface that it
found in the device's IP interface table. It should have
considered all the sw loopback interfaces, choosing the one
with the numerically lowest IP address.
Resolution:
The code in the chooseNodeName() function has been modified
to consider all sw loopback interfaces in a device's IP
interface table. The one with the numerically lowest IP
address is now favored.
PHSS_23637:
Caused by incorrectly calling the routine
_OVEventDbFreeEvent twice (thus attempting to
free the same structure twice) in the case of
-exportmaxrecords being specified.
Resolution:
Code corrected so as not to call this
routine twice.
PHSS_23629:
ovw did not refresh the submap list used in the dialog box,
so it attempted to retrieve information about the deleted
submap, causing a NULL pointer dereference.
Resolution:
If the deleted submap is in the submap list for the dialog
box, ovw now refreshes the submap list and displays a
dialog box telling the user that the list has been updated.
PHSS_23607:
Netmon cannot use ICMP to test interfaces which have no
route to them.
Resolution:
A new feature was implemented that allows the user
to specify ranges of IP addresses which will be
status polled with SNMP rather than ICMP. See the
netmon.snmpStatus and netmon.statusMapping man
pages included with this patch.
PHSS_23600:
The ovalarmsrv process does not provide a sortable
timestamp in the events that it packages for its clients
such as the SIP alarm module. This becomes a problem when
the SIP client is running in a locale different from the
ovalarmsrv process.
Resolution:
A timestamp (seconds since the epoch) is now being provided
by ovalarmsrv in each event that it packages for a client.
This additional information has no effect on the current
NNM web alarm browser.
PHSS_23586:
Caused by a coding error in the webappmon.exe
program which allowed the same structure to
be freed twice, thus causing webappmon.exe
to abort, which manifests to the user as a
browser Internal Server Error.
Resolution:
The program $OV_WWW/cgi-bin/webappmon.exe was
corrected to not free the same structure twice.
PHSS_23584:
ovtopmd caches a pointer to the loaded mib information.
If the loaded mib tree gets re-read for some reason,
this cached pointer will become invalid.
Resolution:
The caching logic has been fixed so when the underlying mib
has been re-read, the pointer will be refreshed with the
latest mib tree.
PHSS_23582:
netmon tries to update a node in the topology and is
waiting for ovtopmd to respond. Under some conditions,
ovtopmd could wait for an indefinite period of time on a
receive.
Resolution:
ovtopodump was found to cause this problem and
consequently fixed, no longer causing ovtopmd to hang.
PHSS_23473:
In order to be more POSIX-compliant, a recent 11.x upgrade
changed the behavior of process-startups so that they all
inherit the signal procmask of their parent process instead
of starting with a cleared procmask. So if a parent blocks
any signal, it means that the child process will now start
off with that signal blocked as well. OmniBack and MC/SG
both invoke ovstart, making them parent processes - so they
pass on blocked signals to ovstart, and thence to ovspmd.
OmniBack was blocking SIGCHLD, which ovspmd depends on when
it is shutting down NNM processes - in order to determine
when a child has finally shut down.
MC/SG was blocking SIGALRM, which ovstart depends on to
wake itself up from the sleep that it goes into while it's
giving time to ovspmd to complete its startup.
Resolution:
ovstart now compensates for any inherited signal-blocking
(passed to it by parent processes) by clearing all blocked
signals upon startup. With the inheritance, this means it
will pass a cleared procmask on to ovspmd as well. This
essentially restores the behavior present before the 11.X
O/S changes. This patch exists in HPUX 10.X and SOLARIS
versions as well, in case the same POSIX-compliant changes
are implemented in them in the near future. No similar
changes are anticipated for NT.
PHSS_23458:
The path to the debug file is not correct.
Resolution:
The path has now been corrected.
PHSS_23448:
This happens because the node created by IT/O has an "IP
Hostname" field in the object database, yet it has no
corresponding entry in the topology database. This makes it
look like it is a "lost IP node object" that was partially
created by netmon and never finished. [See the "-c" option
in ovtopofix(1m)] Since removing this type of node is one
of ovtopofix's defined "clean-up" tasks, it tries to remove
the interface field and then the node itself from the
object database.
Resolution:
When ovtopofix encounters one of these nodes that appears
to be a "lost IP node object", it now first checks to see
if the node was apparently created by another application.
It does this by looking for the presence of certain field
names in the suspect node. If present, then it does not
attempt any cleanup of that node.
PHSS_23442:
There was no code implemented to handle the above mentioned
cases.
Resolution:
1)Code was written to provide the warning and error
messages.
2)The sourceToggle button which was redundant in NT was
removed.
PHSS_23420:
The defect was mainly in wrong expressions.The expressions
IfHCHDplxUtilization, IfVHCHDplxUtilization,
IfHCCombFDplxUtilization, IfVHCCombFDplxUtiization and
IfFRPct* expressions had error.
Resolution:
The defects in expressions were fixed and wrong comments
were corrected. This fix does not solve the problem due to
inconsistency in usage of packet oriented and octet values
in the same expression. This was because a long time was
already taken to come up with a decision and it was
intended to clean up as much as possible now.
PHSS_23404:
The Varchar fields of the data warehouse databases
are a maximum of 256 characters. However, the varbind
with the event uuid list can be thousands of characters
long. The program truncates the data before writing
to the database.
The numeric range error is caused by incorrect type
casting when passing a parameter to the ODBC
routines.
Resolution:
A new option, -exportsplituuids, was added to
ovdwevent. This option will cause additional
varbinds to be output to the nnm_event_varbinds
table, which have one uuid per varbind. This will
only occur for the following events:
OV_Ack_Alarm, OV_Unack_Alarm, OV_Delete_Alarm,
OV_ChgSev_Alarm, and OV_ChgCat_Alarm. In addition,
these events will only be exported if ovdweventflt is
used to specify that these events should be exported.
Thus a customer will be able to access all of the
uuids as follows:
1) ovdwquery;
2) SELECT event_uuid FROM nnm_event_detail WHERE ... ;
3) SELECT ... FROM nnm_event_varbinds WHERE
event_uuid='..output from the first select.. '.
The numeric range error was fixed by correcting
the type casting prior to the call to the ODBC
routines.
PHSS_23402:
Ipmap was calling the findSymbol routine to find a symbol
on the submap. Since the submap is not one created by
ipmap, the ipmap application does not keep track of the
symbols. In cases where the symbol is on a submap not
created by ipmap the findSymbol routine was not correctly
checking if the submap was one the ipmap application was
interested in.. Because this check was not done correctly
the error message was generated in error whenever the
symbol was not found.
Resolution:
Modify the ipmap findSymbol routine to include a check to
verify that the symbol is located on a submap that ipmap
created and is interested in. Do not create this error
message if the symbol is on a submap that ipmap did not
create. Only create this error message if the symbol is
not found on a submap that ipmap created and is interested
in.
PHSS_23392:
jovw only drew Critical connections as red, and all other
connections were drawn as black.
Resolution:
jovw now draws all connections with their status color,
except for Normal, Unknown and Unmanaged. ovw draws these
three statuses with black, so jovw also draws these with
black.
PHSS_23364:
For some reason, the Network Presenter's (jovw's) listener
thread, that listens for API messages and OVw events on the
inbound socket, is blocked on a read of the inbound data
stream. It should see an API message from ovw, but it does
not.
This happens during session initialization where jovw is
attempting to contact the SECOND ovw session. The problem
seems to be related to incomplete or incorrect shutdown of
the first ovw session.
Resolution:
The order of shutdown tasks, that are executed when an ovw
session is being terminated, has been changed. The inbound
socket is now closed before stopping the listener thread.
PHSS_23348:
Network Presenter was not designed to support these
functionalities. It presents the result of Ping or Remote
Ping operations.
Resolution:
HP OpenView Web Online Help Documentation changed to align
with what exactly Network Presenter's Ping and Remote Ping
operations support.
PHSS_23346:
Same error message was used for two different error
sources.
Resolution:
Changed the second error message to describe the second
error source.
PHSS_23344:
This is an enhancement to netmon.
Resolution:
The user can now configure a netmon.cmstr file in order
for NNM to perform community string discovery. See the
netmon.cmstr man page (or reference page if running on
Windows) for more information on the format and
interpretation of the netmon.cmstr file as well as
examples.
PHSS_23330:
1) The getservbyname call used returns the port number in
network byte order. The port number was not being
converted to host byte order before being passed along to
the next call.
2) Some network environments have firewalls that prevent
SNMP traffic from being passed, and a particular managed
node might have one address on each side of the firewall.
In this case, the management station will receive timeouts
if it tries to use the wrong IP address for its SNMP
queries. Even though the netmon process is capable of
trying all available IP addresses and remembering which
one gives successful SNMP responses, this preferred SNMP
address is not made available to the SNMP applications
which are integrated on the ovw menubar.
Resolution:
1) Convert the port number to host byte order before
passing it along to the next call.
2) There is a new field defined in the ovwdb database
called "Preferred SNMP Address", which will be updated with
the corresponding information that exists in the topology
database. The Application Registration Files within NNM
can be modified to take advantage of this new field so
that the corresponding application can use the correct
IP address. Please see the "Special Installation
Instructions" section of the patch text file for more
information.
PLEASE NOTE:
Installation of this patch will over-write the
the $OV_FIELDS/C/snmp_fields registration file. Also,
if this patch is uninstalled, the Preferred SNMP Address
field will not be removed from the database.
PHSS_23322:
As the symbol was exploded and the submap created, ovw
incorrectly decided that this submap should be persistent
due to its parent object.
Resolution:
ovw now no longer changes a submap to persistent when its
parent symbol is exploded.
PHSS_23220:
1. $OV_WWW was not in the list of directories to be
backed up.
2. The ovsnmp_conf_loc file was always saved in $OV_TMP,
which is not the correct directory when a destination is
specified with the -d option in the ovbackup command.
Resolution:
1. $OV_WWW is now in the list of directories to be
backed up.
2. The ovsnmp_conf_loc file is now saved in the backup
directory ($staging_area).
NOTE: See Special Installation Instructions below for
instructions on enabling these fixes. They will not be
enabled by default.
PHSS_23211:
After ovtopmd has fetched the node object, a validity check
is made on the sysObjectId by checking that the first
component of the mib subtree is less than 4. For a
sysObjectId like 65.25.1.2, it fails and it results in the
object of sysObjectId being freed and nullified.
Unfortunately we subsequently attempt to dereference the
sysObjectId without checking if it is valid. And this
results in the crash.
Resolution:
Modified the validation routine to resolve the problem.
PHSS_23209:
Since the NNM/NT code generates a scrollbar window, the
NNM/UX code should also generate a scrollbar window for
the TEST SNMP results.
Resolution:
Add a scrolled window to the Unix Message Box dialog.
PHSS_23199:
As the MS is going down, a number of the notifications that
it sends out to the CS's of its imminent shutdown are
somehow not fully sent out, because on the CS end they show
up as data on a socket that is 0-length. This starts a
chain of events resulting in the eventual "Select failure"
error message and the self-shutdown of pmd.
Resolution:
The pmd/ovEvent module (libovevent.sl) on the CS will now
properly handle the erroneous socket data.
PHSS_23197:
When an application "ungracefully" disconnects from pmd,
the ovEvent stack needs to inform other interested appls
of this fact. To save a tiny bit on performance, it does
not generate a real trap, but instead simulates the
situation where a trap has just arrived and needs to go
through the usual processing. But the trap data it creates
has some fields set in such a way that the trap is
eventually rejected just before it gets sent to the ECS.
So the pmd.log0 error message is seen, and the trap never
gets into the ECS.
Resolution:
The contents/format of the internal trap are now changed,
so that the trap is properly processed by ECS. The error
message in pmd.log0 is no longer there, and these events
can now be correlated.
PHSS_23187:
1. On NT, the OV_EVENT stack in pmd was commiting records
to disk when it was not necessary. This caused a
significant slow down of event processing in pmd.
2. When a partial event packet was received from pmd,
ovalarmsrv did not process it correctly. This caused
ovalarmsrv to believe the next event packet was corrupt
and close down the thread reading events from pmd.
Resolution:
1. Event records written to the BES are only committed to
the disk immediately when the event logs are being
initialized or being rolled over.
2. ovalarmsrv now properly handles the case when a
partial event packet is read from pmd.
PHSS_23157:
xnmbuilder did not keep track of its state and allowed the
modify operation to proceed without cleaning up the
previous operation. This eventually caused a NULL pointer
dereference.
Resolution:
xnmbuilder now properly keeps track of its state and
disallows any modify operation while it is currently in an
Add, Modify or Delete operation. If the user double-clicks
on the application that is currently being modified, then
the Modify MIB Application window is raised to the top of
the window stack.
PHSS_23119:
The ovdbcheck process does not properly process a SIGCHLD
signal. This results in a defunct process that does not go
away until OpenView is stopped.
The ovdbcheck process does not listen for OpenView PAUSE
and RESUME messages from the ovspmd process. While
Openview is PAUSED, ovdbcheck continues it periodic
database connectivity checks. This becomes problematic if
the customer wishes to shut database access while OpenView
is PAUSED for backups.
Before attempting to start the embedded database, the
ovdbcheck process attempts to connect to the database in
order to determine if it is already running. If the
database is not yet running, a normal situation, the
connect attempt fails and ERRORS are logged to the
ovdbcheck.log file. These errors are misleading because
there really is no problem. The database will subsequently
be started and a second connect attempt will be succesful.
Resolution:
The ovdbcheck process now ignores the SIGCHLD signal. This
allows the defunct child process to go away.
The ovdbcheck process is now capable of handling OpenView
PAUSE and RESUME messages. When in a paused state,
ovdbcheck suspends its periodic database connectivity
checks. Note: the ovdbcheck.lrf file must be modified in
order to enable the handling of PAUSE and RESUME messages.
See the special patch installation instructions for more
information.
The ovdbcheck.log file is now annotated to explain that the
first ERROR in attempting to connect to the database may be
a normal situation, a result of the database not yet
started.
PHSS_23008:
Local pmd (Collection station) attempts to connect to
remote pmd (Management Station) in a blocking mode (default
socket connection mode). And since the remote pmd's host is
not on the network, the connect() call hangs for a long
time (at least >10 minutes)
Resolution:
Make the local pmd connect to the remote pmd in a
non-blocking mode.
PHSS_22973:
1. ovrepld is attempting to process the collection station
list when there are no collection stations managed.
2. ovrepld on the management station gets stuck in a loop
trying to get the status of an interface from a collection
station even though that interface has been deleted on the
collection station.
Resolution:
1. ovrepld now checks for a null station before attempting
to do any processing on it.
2. ovrepld now stops trying to get an interface's status
if the interface has been deleted on the collection
station.
PHSS_22954:
The ovdbsetupo3.sh shell script, invoked by "ovdbsetup -o",
fails to check for the existence of environment variable
"TNS_ADMIN" when determining the location of the Oracle
SQLNET/NET8 configuration files. This script also fails to
allow the user to optionally override this location.
Resolution:
This patch changes shell script ovdbsetupo3.sh so that it
checks for environment variable "TNS_ADMIN" when
determining the location of the SQLNET/NET8 configuration
files. This script is also changed to enable the user to
optionally provide the location of these configuration
files.
PHSS_22952:
Network Presenter did not correctly identify the Management
Page action, and encoded the URL. As well, the webbrowser
registration file for the Management Page action always
prepended "http://" and appended ":280".
Resolution:
The webbrowser registration file now passes the
ManagementURL attribute through without change to Network
Presenter. As well, Network Presenter recognizes the
Management Page action and does not encode the URL.
PHSS_22808:
MenuMgr was not checking for null menu entries list.
Resolution:
Modified source code to check for null menu entries list
in appropriate places.
PHSS_22789:
1) NNM will automatically adjust the interval at which it
polls devices for new hints. Devices which are more
fruitful sources of hints will be polled more frequently.
The minimum delay between these discovery polls is hard
coded at 5 minutes.
2) A printf format had a %s where it should have had a %d.
Resolution:
1) This problem is fixed by adding a new command line
option to netmon which allows the customer to
define the minimum wait time between discovery polls.
The option is "minimumAutoAdjust", specified in minutes.
2) The printf format was corrected.
PHSS_22746:
ovuispmd did not properly track the two interactive
sessions because ovw registered them with the identical
name.
Resolution:
ovw now registers its non-interactive sessions with
ovuispmd using a unique identifier.
PHSS_22725:
The ovalarmsrv code failed to null terminate long (>505
bytes) event description strings. This resulted in memory
corruption that sometimes caused ovalarmsrv to abort.
Resolution:
The ovalarmsrv code was modified to ensure that long event
description strings get null terminated.
PHSS_22723:
When an application can receive only v1 traps, the incoming
V2 Trap/Inform is convertd to a V1 Trap Pdu. The
v2notifyOID (enterprise field) of the pdu is translated
into v1enterprise, v1generic and v1specific. While doing
this, the enterprise field is not appropriately freed.
Resolution:
The enterprise field is freed appropriately.
PHSS_22666:
Buffer over-run. The code is set up to handle an
environment of 100 networks or less. This would normally
be fine except some ISP's are associating multiple
resources to individual organizations which results in
large network counts, 2k -5k+.
Resolution:
Function now checks the cache (buffer) size, and resets
it's counter accordingly.
Also added a statement to free memory previously
allocated, yet not deallocated.
PHSS_22659:
The ipmap abort is caused by a code defect where the same
memory is freed twice.
Resolution:
The ipmap code was changed so that the same memory would no
longer be freed twice.
PHSS_22645:
Network Presenter did not have a color specified for these
statuses, so they defaulted to black.
Resolution:
Network Presenter now correctly specifies the colors for
these statuses.
PHSS_22638:
i) An incorrect Pen style was used for drawing lines.
ii)No check was made to determine if the line thickness was
specified for the Connection sub-class.
Resolution:
i) Used The correct style (PS_GEOMETRIC | PS_USERSTYLE)
when creating the Pen for drawing lines (ExtCreatePen()).
ii)Checked if a thickness entry was parsed for each
Connection type (sub-class). If not, we use the thickness
entry for the Connection class as default thickness
PHSS_22582:
Certain devices (such as Cisco routers) use a
"software loopback" pseudo-interface to hold a
well-known IP address by which the router should
always be accessible. NNM will normally
disconnect such interfaces from networks and
segments when it finds them. Netmon was
disconnecting this interface from these objects
in the wrong order.
Resolution:
netmon has been changed to disconnect the network
and segment in the proper order to eliminate the
abort.
PHSS_22580:
If ovtopmd generates a very large number of events
quickly at startup time, its internal event
buffer gets corrupted in such a way that no more
events are being sent to pmd.
Resolution:
The ovtopmd internal event buffer has been changed
so that it works properly now.
PHSS_22577:
The code that handles backing up subdirectories within a
directory did not check to see if there were symbolic links
in that directory as well.
Resolution:
The code now correctly checks for symbolic links in all
cases and backs them up and restores them properly.
Note: ovbackup backs up the symbolic links, but does not
attempt to back up whatever the symbolic link is pointing
to, since NNM has no way to know what that is. That is the
responsibility of the user/administrator. An exception
would be if the link is to a directory that NNM happens to
back up anyway.
PHSS_22423:
Consolidated Patch
PHSS_22408:
1. The InputEventTypeListStringSources table can be used to
match the IfName (in addition to the "agent-addr" specified
in InputEventTypeList). The PairWise circuit logic did not
always handle this properly.
2. There was no check to see if the parent event should be
suppressed.
Resolution:
1. The PairWise circuit logic was corrected so the
InputEventTypeList and InputEventTypeListStringSources
tables are processed correctly.
2. A parent event that pairs with a child can now be
inhbited if the InhibitParentOfInhibitedChild parameter is
set to true.
PHSS_22406:
pmd is attempting to clean up a table twice while exiting.
This causes an exception/core dump to occur in the
purgetab() function.
This problem occurs when patch NNM_00598, PHSS_22242,
PHSS_22243, or PSOV_02801 is installed.
Resolution:
Check that the table pointer is valid before trying to
access it.
PHSS_22402:
Not enough memory was being allocated for an array.
Resolution:
Increased the array were were allocated by one.
PHSS_22400:
The password was being truncated to 8 characters without
warning the user that this truncation had occurred.
Resolution:
Increased the maximum password length to 24 characters.
Added code to verify that both the password and user name
are not greater than 24 characters in length.
PHSS_22398:
The first time a secondary failure event arrives at the
Management Station, ovrepld sends out the appropriate
secondary failure IF status event. Any subsequent time a
secondary failure event arrives at the MS for that
interface, ovrepld sends out the IF status event, but does
not identify the event as a secondary. The ConnectorDown
circuit does not see the secondary failure varbind and
treats the event as a primary failure.
Resolution:
The critical interface uuid modified flag is now set every
time an IF status change is being reported for a secondary
failure.
PHSS_22395:
The correlation was matching correctly on event type and
agent-addr but did was not match correctly when the event
source was set to "*". A function call was returning a
invalid translation for IP address when a '0' was
contained in the network address.
Resolution:
Correlation logic was corrected to bypass the match on
agent-addr when the event source was configured as "*".
Changed logic to make use of an internal ECS call to
translate the agent-addr octet to an IP address. Note: The
correlation has been updated but is dependent upon the
latest ECS consolidated patch for the correct version of
the internal function.
PHSS_22388:
JAGad12808:
Core dump problems were caused by buffer overflows.
Inadequate sizes of buffers were allocated to hold
nul-terminated data. Thus, causing data overrun.
JAGad24341:
ovalarmsrv loops through all available categories returning
the appropriate strings. By making the category ID 63, the
intermediate categories happen to be null. This causes the
core dump on solaris, a null pointer dereference within the
sprintf() command.
JAGad24345:
ovalarmsrv caught the select() error and exited abnormally
Resolution:
JAGad12808:
Made buffer sizes adequate to prevent overflows.
JAGad24341:
Made sure null strings are not passed to the sprintf()
command. That is, check string for the null first.
JAGad24345:
Made changes to ignore an error return of EINTR from
select() call.
PHSS_22386:
The ovrequestd process mistakenly used whichever JRE it
found in $PATH. When events were exported via ovrequestd,
the environment variable "$LANG" was not being set in the
environment that launched the export operation. This
resulted in the selection of the "trapd.conf" file in the
wrong language.
Resolution:
The code was changed to ensure that ovrequestd would select
the correct JRE. The code was changed to ensure that
ovrequestd would launch its tasks with $LANG set.
PHSS_22384:
The OvWebHelp .htm file had a syntax error in the line that
specified the blue background for the active toolbar
button. As well, the .htm file for the Tasks page was not
localized.
Resolution:
The syntax error has been corrected and the Tasks page has
been properly localized.
PHSS_22375:
In the process of handling a manually-added node, there are
certain steps that netmon must go through. The problem is
caused by the fact that netmon was not going through these
steps in the proper order. The only time this problem
should be seen is when netmon is in the process of
discovering a node at precisely the same time that the user
is adding that same node via the map GUI.
Resolution:
Netmon has been changed to handle all the steps
of manually adding a node in the proper order.
PHSS_22355:
Sessionmgr incorrectly parses multi-user role definitions.
Resolution:
Changed code to fix tokenizer in sessionmgr
PHSS_22336:
The code that drew the outer shapes next to the submap
names in the list did not check to see if the submap parent
symbol was a connection. In addition, ovw assumed that
there would be less than 50 symbol classes and did not
check for array indices out of bounds.
Resolution:
ovw now first checks to see if the submap parent symbol is
a connection and does not draw a pixmap for those submaps.
It also dynamically allocates an array for the pixmaps and
increases that if needed.
PHSS_22334:
The code was explicitly doing an exit on recieving
a 0 byte SNMP trap.
Resolution:
Changed the code so that it will not exit on recieving
a 0 byte SNMP trap. It will just return.
PHSS_22332:
ovw incorrectly calculated the placement of text
annotations for connection symbols.
Resolution:
ovw now correctly calculates the placement of the text
annotation on connection symbols so the text annotation no
longer overlaps the label.
PHSS_22301:
The current process of parsing the Object ID HTML form
field does not check for a variety of formats that may be
entered by the user.
Resolution:
The parsing logic has been improved resulting in a more
robust check for entries in the Object ID field.
PHSS_22299:
Else statement responsible for the debug message
"ifHighSpeed should be supported..." is misplaced, it
should be under the previous if statement where we know
the interface is highspeed because ifSpeed is MAX_INT, but
we did not find the highspeed var bind, or it was not
greater than 0. Otherwise the debug message is printed
reguardless.
Resolution:
Move the else statement in question to line up & follow
if (OVsnmpVbExists(vb) && OVsnmpVbInt32(vb) > 0 )
not
if ( OVsnmpVbInt32(vb) == UINT_MAX )
PHSS_22297:
The problem was occuring because when the oids were being
compared, the oid lengths that were getting used for
comparison was not getting set properly under this
condition.
Resolution:
Fixed the code so that the oid lengths are being set
properly while comparing.
PHSS_22292:
The defect was because null pointers were not handled
properly in the case of Solaris.
Resolution:
Code was implemented to handle null pointers in the case of
Solaris also. Earlier they were handled in case of WINNT
with an IFDEF. This was removed to handle null pointers in
case of all platforms.
PHSS_22283:
Maximum token length allowed was 64 bytes in all the cases.
Resolution:
Default value of size upto 65536 byte are allowed now.
PHSS_22242:
There are two problems:
1. For events configured as IGNORE, the check to see
if an event was IGNORE was not being done properly. These
events are therefore passed to xnmevents and ovalrmsrv.
2. Events that are configured as IGNORE or LOGONLY may
have other events correlated under them by an ECS
circuit. When this happens, a CORR_IND event is sent to
xnmevents and ovalrmsrv so that the correlation indicator
is displayed in the Alarm Browser. A list is kept
of events that have had a corresponding CORR_IND event sent
so that additional CORR_IND events are not sent later on.
The size of the list is too small to save an adequate
history of events that have had CORR_IND events sent.
Resolution:
Problem 1 was fixed by checking to see if an event is
IGNORE, and if it is, suppress sending the event to
xnmevents and ovalrmsrv.
Problem 2 was fixed by changing the CORR_IND event list to
a hash table with greater capacity.
PHSS_22240:
There are various assumptions made by ovdbsetup* scripts
about the environment of the shell that is invoking it, and
about the availability of file systems and their permission
levels. Under some conditions, some of these assumptions
can cause the script to fail and exit prematurely.
Resolution:
The script has been made much more robust.
PHSS_22238:
ovactiond and snmpCollect man pages are missing option
specifications and the ovtopofix -I and ovactiond -u
options are incomplete.
Resolution:
Update man pages with correct text.
PHSS_22236:
Memory allocated to objects added to hash table was not
freed when the object was removed from hash table.
Resolution:
When objects are removed from hash table the associated
memory was freed.
PHSS_22221:
The "-sumnoweeknds" option of the "ovdwtrend" command
contained a code defect. This resulted in the ovdwtrend
command passing an invalid option to the underlying
"ovcolsum" command that actually performs the data
aggregation.
The "ovdwtrend -export" command (which invokes the
ovcoltosql command to perform the export operation) was not
properly truncating long (>256 byte) MIB expresions so that
they could be handled by the SQL Server 6.5 database.
Resolution:
The code was patched to correctly handle the
"-sumnowekends" option to the "ovdwtrend" command. The
code was patched to properly truncate long MIB expressions
for the SQL Server 6.5 data repository.
PHSS_22219:
Both a carriage return and a line feed were not being sent
to terminate SMTP commands. Multiple 220 responses were
not being read from the socket.
Resolution:
All SMTP commands are terminated with a carriage return
and line feed. The socket is cleared of multiple 220
responese.
PHSS_22212:
The solidBackupIsActive() subroutine in ovbackup.pm
simply wasn't waiting long enough to say Solid is complete
with its backup. The routine queries SOLID and then greps
for the text 'ACTIVE' Yet the query statement (ADMIN
COMMAND 'status backup') is missing a ';' to complete the
query, so it is automatically rejected. And since 'ACTIVE'
is not present in the return text from SOLID, the
subroutine believes SOLID is no longer active. Therefore
okay to continue with the remaining ovbackup tasks.
Resolution:
Add the missing ';' to "ADMIN COMMAND 'status backup'"
Also changed $ENV{TMP} to $ENV{OV_TMP} in
solidBackupIsActive() for variables $statQryFile and
$statOutFile
PHSS_22210:
When some of the toggle buttons on the Set Filters.. dialog
box are selected, they cause additional widgets to appear
in the dialog box panes for that toggle. The rapid
sequence of selects/deselects, combined with the addition
of the extra widgets and raising the dialog box window
sometimes caused the Set Filters... dialog box to lose its
geometry.
Resolution:
The dialog box no longer raises itself when a toggle is
selected, allowing xnmevents to properly add its additional
widgets without any geometry problems.
PHSS_22173:
ovw was counting the number of characters in the comments
field rather than the number of bytes.
Resolution:
ovw now checks the number of bytes in the comments field to
ensure that the comments field does not contain more than
256 bytes.
PHSS_22171:
The ovdweventflt command needs modification to correct its
"usage" statement and to add "display" and "clean" options.
The ovdweventflt man page needs corrections for errors and
omissions.
Resolution:
The ovdweventflt command was modified to correct its
"usage" statement and to add "display" and "clean" options.
The "display" option can be used to display the contents of
the NNM_EVENT_LIMITS table in the data warehouse. The
"clean" option can be used to delete the contents of the
NNM_EVENT_LIMITS table.
The man page for ovdweventflt was modified to correct
errors and omissions.
PHSS_22153:
Network Presenter used an invalid Application Context to
invoke the URL for the menu item, which failed.
Resolution:
Network Presenter now checks and uses the current
Application Context to invoke the URL for the menu item.
PHSS_22130:
When "ovw -newmap" or "ovw -map" was invoked, it used a
funtion openMap, to create a new map. This function never
used the root layout. When the "Map->New" menu option is
used, the function that created the "New Map" dialog box
put the status propagation as default.
Resolution:
The function openMap has been modified to accept rootLayout
also as a parameter. The dialog box code has also been
changed to take into account the status propagation set in
the app-defaults file.
PHSS_22115:
Current design of ovwdb forces all the enumeration names
associated with a specific enumerated field to be
stored in a single database record, and this record
size is limited to 8k bytes. When the record size
is exceded, ovwdb aborts.
Resolution:
The ovwdb enum_info database has been changed to store
the enum constants for a field into multiple database
records rather than all in one. This eliminates the size
restriction on the cumulative size of the constants, as
well as eliminating the hard-coded limit of 1000 entries
per enum field.
PLEASE NOTE: Installation of this patch will update the
format of ovwdb. This new format is incompatible with
earlier versions of the NNM code. If you think you might
want to de-install this patch, you MUST make a backup of
your NNM data prior to installing the patch, and then
you must restore this backup at the time the patch is
de-installed.
PHSS_22110:
The problem is caused by the event interface failing to
process the format of the incoming trap. Netmon is
told that pmd went away rather than being told
that there was a decode error.
Resolution:
The event interface was modified to return an
error code that indicates a conversion failure
so that netmon does the right thing and does
not exit.
PHSS_22108:
The xnmloadmib code was not handling the case of empty
braces properly.
Resolution:
The problem was occuring because of pointer not being
initialized properly. Fixed the code so that pointer is
initiazlied to NULL, which resolves the problem.
PHSS_22094:
A piece of code which was originally redundent was changed
with the intention of removing the redundence, which had
caused the defect.
Resolution:
Removed the redundent code.
PHSS_22068:
A second background image of China is needed that includes
Taiwan as part of China.
Resolution:
A second background image of China was added to NNM 6.1.
This image is "china1.gif".
PHSS_22064:
This problem occurs when the number of leaves or branches
at any given level in the NNM Report Presenter tree
exceeds 64. This is caused by a fixed length array of 64
objects being used to hold the branches or leaves at each
level of the NNM Report Presenter tree. When more than
64 objects are added to the array an
java.lang.ArrayIndexOutOfBoundsException is thrown and the
excecution of the applet is halted.
Resolution:
The fix requires a code change to the nnmReporting Jar
file. This fix changes the fixed length array to a
dynamic data structure.
PHSS_22061:
The Java template files, which contain the HTML for the
login session, do not set focus in the login form field.
Resolution:
The Java template files have been changed resulting in
focus being set in the login form field.
PHSS_22055:
The code defect is in a table that converts the HP-UX
timezones to Java timezones. The entry for the Central
timezone contains an invalid character.
Resolution:
A code change was made to correct the Central timezone
entry in the HP-UX timezone conversion table.
PHSS_22051:
If secondary failure polling options are enabled, and
if NNM is not able to determine the critical route
paths through the topology, then there is a case where
the status polls for non-IP interfaces does not update
the database.
Resolution:
This problem was fixed by changing the code to update
the database with the correct status in all cases.
PHSS_22049:
Several defects have been found that can cause the "primary
key unique constraint violation" error:
1. An error occured in the computation of "epoch time"
during the rollover to daylight savings time.
2. The Data Collector sometimes collects from multiple IP
interfaces on the same node.
3. Sometimes a specific data collection was incorrectly
rolled into the next hourly aggregation period.
Resolution:
The code was changed in three ways. The epoch time
calculation was fixed so that it will be correct during
daylight savings roll forward/back. A data collection will
no longer be rolled into the next hourly aggregation
period. The export operation will no longer abort if it
encounters a duplicate data collection.
PHSS_22028:
Some code incorrectly tested for the browser version rather
than the JVM version, and passed inappropriate arguments to
scrolling calls.
Resolution:
Modified code to properly check for JVM version and vendor,
and to take appropriate action based on known behaviors of
those specific JVMs.
PHSS_22026:
ovw did not register for the close via window manager
callback; when the dialog box was closed via the window
manager, ovw continued to wait in a separate event loop
rather than cancelling the operation and returning to the
normal event loop.
Resolution:
ovw now registers for the close via window manager callback
and performs the same actions as if the user selected the
"Cancel" button.
PHSS_22018:
No code is implemented in 'ovexprguru' to check for
colons (':') in interface's description which is retrieved
from object database.
Resolution:
Code is implemented to check for colons (':') in
interface's description and replaces it with slash ('/').
PHSS_21997:
mismanagement of memory, file descriptors, and threads was
causing shortage of resources resulting in hang or abort.
session timeout was not reset when a session was accessed.
lack of explicit usage model for memory, file descriptors,
and threads.
incomplete implementation (missing method).
Resolution:
tightened up use of memory, file descriptor, and threads.
added mechanism for resetting timeout for active sessions.
implemented missing method.
PHSS_21930:
There is no code implemented to initialize the toggle
button.
Resolution:
Code is implemented to intialize the toggle button.
PHSS_21920:
AsyncMsgChannel.setReplyMsgAndWaitForReply() did not test
to see if reply message had already arrived prior to
entering calling wait()
Resolution:
Modified code to test for existence of reply message before
calling wait()
PHSS_21918:
Java LibOvw OVwDbInit() does not properly initialize
hp.ov.libovw.LibOvw.
Resolution:
OVwDbInit now properly sets internal flag.
PHSS_21916:
During its search for bitmaps, ovw inadvertently overwrote
the value of $OVwBitmapDir.
Resolution:
ovw now makes its own copy of $OVwBitmapDir for processing
so the original is not overwritten.
PHSS_21870:
The object had an enumerated field assigned to it, however,
the field had no enumerations defined for it. ovw did not
recognize the partially defined enumerated field and
subsequently accessed an invalid pointer.
Resolution:
ovw now correctly identifies partially defined enumerated
fields, and no longer accesses invalid pointers.
PHSS_21860:
There is a typographical error in ovrepld which causes
changes to the SNMP Address field to be ignored.
Resolution:
The typographical error has been removed from ovrepld
so that the SNMP ADDRESS will be properly updated.
PHSS_21851:
xnmgraph->view->statistics window doesn't have verticall
scroll bar.
Resolution:
Included vertical & horizontal scroll bar.
PHSS_21848:
When the "Configure Data Collector" option is invoked from
xnmgraph, a policy is created containing the node name, the
Instance list on which the collection is to happen etc.
While doing so, enough memory is not allocated for instance
list. This causes memory corruption when trying to add new
instances.
Resolution:
Sufficient memory is allocated for the instances in the
CollectNode constructor. A new member function
addInstances() has been added which takes care of
reallocating memory if needed.
PHSS_21846:
The URL is parsed incorrectly before being passed to the
browser, causing the browser to return an Invalid Request
Error.
Resolution:
A function has been added to correctly parse the URL
before being passed to the browser.
PHSS_21839:
This happens because of any array containing junk when its
expected to be NULL.
Resolution:
The array meant for containing the "OtherFile" name is
nulled out.
PHSS_21837:
Two reasons caused this
1. When an X-terminal is switched off ovw takes about 600
seconds to timeout the X-session and exit. So ovpause
timesout before the ovw session can exit.
2. If ovpause timeout is increased to a value greater than
600 sec, ovw session exits but ovuispmd still waits for a
PAUSE acknowledgement.
Resolution:
I have changed code in ovuispmd so that it no longer waits
for a pause response from an ovw session that has exited.
PHSS_21823:
The correlation was not properly handling the return code
from the hostname resolution call which caused the
correlation to discard valid events to early.
The correlation was iterating through loops to check for
valid name matches for each event seen in the correlation.
The additional loop processing for events from the same
source was unnecessary.
Resolution:
The return code from the hostname resolution call was not
being handled so the default action set up was to discard
the event. The ECDL was modified to correctly handle the
return code from the hostname resolution.
The ECDL was modified to execute the loops only when
necessary.
PHSS_21783:
The grid was not set to scroll to the new event arrived.
Resolution:
Modified the grid to scroll, to display the new event
arrived.
PHSS_21557:
Consolidated Patch
PHSS_21550:
The tables that hold the first events for correlation with
later events never deleted these events, unless they were
replaced by a later event, in which case there was still an
event left in the table for that 'key combination'. One
event was saved for each 'key combination' that entered the
circuit.
Resolution:
Two new circuit parameters were added to the Repeated Event
circuit to control how long events are saved in the tables
that hold the first events. These parameters are
HoldFirstEventTime and MaxHoldFirstEvents. For a complete
discussion of these parameters and how to adjust them, see
the RepeatedEvent.param file or examine the parameter
descriptions with the ECS Configuration GUI.
PHSS_21547:
The 'child' event (the first event of a pair being
considered for correlation) was always output immediately.
Resolution:
There is a new parameter, ChildEventImmediateOutput, which
can be used to control when child events are output. If
the ChildEventImmediateOutput parameter is "true"
(default), child events are output immediately as described
in the PairWise circuit description. If the
ChildEventImmediateOutput parameter is "false", the default
behavior is modified as follows: child events will be held
for the duration of the PairedTimeWindow. If a matching
parent event occurs from the same source, within the
appropriate amount of time, it 'suppresses' the child
event. To 'suppress' means that the child event is never
output. The child event is still correlated under the
parent event.
PHSS_21538:
The device had been removed from the network and it was in
REMOVED state in the topoDB. ovdwtopo was exporting
devices
in REMOVED state also to the datawarehouse. Hence the
availability report was picking it up and showing it as
down.
Resolution:
Add checks to ovdwtopo to prevent it from exporting devices
if they are in either REMOVED or INVISIBLE state.
PHSS_21536:
ovw miscalculated the length of a string and accessing
memory beyond the end of the string.
Resolution:
ovw now correctly calculates the length of the string, and
does not access past the end.
PHSS_21528:
Incorrect threading code causes thread allocation failure.
Resolution:
Code changed to correctly allocate detached threads.
PHSS_21526:
The header file specified the ITO Developer Product to
support 25 nodes, however, the code was never instrumented
to support it. The number of connectors also need changed
from 1 to 5.
Resolution:
Changed source file to specify one ITO Developer License
will support 25 nodes and 5 connectors.
PHSS_21500:
This problem is caused by library libovextfmt including
library libov in its link step. This creates a dependency
of libovextfmt upon libov which will not be available at
boot time in an NNM "shared binary" configuration under
HP-UX ServiceGuard.
Resolution:
The link of libovextfmt was modified to directly include
the object files it needs from libov. This library is,
therefore, no longer linked with libov.
PHSS_21497:
ovcoltrim requires that reduced data be aggregated before
being deleted.
Resolution:
Added new option, -deleteOverride, to ovcoltrim. This new
option overrides delete restrictions on reduced data.
Previously, reduced data had to be aggregated to be
deleted, but this doesn't always fit the usage model.
PHSS_21477:
There was a fix released in PHSS_21160 which was reading
the NNM_INTERFACE variable in ov.conf. If that variable
was not present, it was using the first available ip
address. The socket created by the SNMP utilities were
getting bound to this address and in the case of some
customers, there was no route back from the destination
machine back to this address, and this was resulting in
the
queries getting timed out.
Resolution:
The library will read NNM_INTERFACE if it is present in
ov.conf file. If it is not present, it will use the
default
"any" address. If NNM_INTERFACE is present and if it is
desired that the SNMP utilities not use this variable(pre
PHSS_21160 behaviour), then
add "IGNORE_NNM_IF_FOR_SNMP=ON"
to ov.conf. This will make all the SNMP utilitities to
ignore NNM_INTERFACE setting.
PHSS_21475:
The COLSPAN set while printing the MIB tree is 100 which
is high.
Resolution:
The COLPSAN in printHtml() has been reduced to 30.
PHSS_21473:
There is a coding error in the "ovwparser" library. This
library defines the syntax rules used by regverify. The
coding error causes regverify to abort with an internal
error.
Resolution:
The ovwparser library was modified to correct the coding
error.
PHSS_21441:
The logic for finding the lowest non-migratable ipaddress
was wrong.
Resolution:
The logic for selecting the lowest non-migratable address
has been corrected.
PHSS_21416:
The Learning products system changed from 6.01 to 6.1 and
the man page changes were not merged forward from 6.01 to
6.1.
Resolution:
Re-added the -R option man page information for ovw
-mapcount.
PHSS_21413:
The Code to handle encoding/decoding of OIDs starting
with .2 was not available in libovsnmp.
Resolution:
Relevant Code has been added to encode/decode OIDs
starting with .2 according to the BER encoding rules.
PHSS_21407:
In the ECS Connector Down circuit, events were never being
deleted from the extraAnalysis tables unless a later event
from the same source entered that table. Even then, the
new event simply replaced the old event. Over time, and
sometimes very rapidly, events entering the circuit from
many different sources resulted in a very large amount
of permanent pmd memory growth.
Resolution:
Events entering the extraAnalysis portion of the Connector
Down circuit will only be saved in the tables for the
period defined by the maxNodeStatusWait parameter. The
circuit logic was simplified to improve throughput.
PHSS_21405:
Netmon would use a coding loop to traverse the
network topology. In some cases, a function
call within the loop could free memory that
was being used to control the loop. This was
causing netmon to access freed memory and get
an exception.
Resolution:
Netmon has been changed so that it checks to make sure the
loop variables are still valid before continuing through
its loop.
PHSS_21403:
IPMap was not checking for existence of a submap object
before calling a method on that object.
Resolution:
Modified IPMap to check for existence of submap objects
before calling changeInterfaceFlags on that object.
PHSS_21401:
ovdbsetupo1.sh used obsoleted parameters during database
creation on Oracle 8.1.5
Resolution:
modified ovdbsetupo1.sh to detect Oracle 8.1.* and remove
references to obsolete parameters.
PHSS_21307:
nnm_restore.ovpl was not parsing solid.ini to determine the
destination of log files (as specified in the
"FileNameTemplate=" configuration entry).
Resolution:
Modified nnm_restore.ovpl to 1. verify existence of log
file directory, 2. clear log file directory of log files,
3. save pre-restore database to enable undo of restore.
PHSS_21297:
1)When ovtopmd attempts to open the topology database,
it does not check for failure codes when it receives
an empty list from the open routine.
2) Ovtopmd incorrectly calculates the license when it
starts on an empty database.
Resolution:
1) This problem was fixed by causing the load of a corrupt
database to generate an error event suggesting
corrective action. Note that this will not catch all
possible corruptions.
2) This problem was fixed by changing the license checking
code to more correctly calculate when the license should
expire.
PHSS_21295:
When selecting a popup menu on a symbol, a dialog box
appears for confirmation. If the original symbol is
deleted before the dialog box is acknowledged there is no
checks to confirm if the symbol still exists.
Resolution:
A check was put in place in the dialog code to verify a
valid symbol exists prior to the delete.
PHSS_21277:
Several help topics had old information and links.
Resolution:
The on-line help files and manuals have been updated.
PHSS_21255:
The -g option for loadhosts was not properly explained in
the man page
Resolution:
Updated the man page with some more examples so that
it clearly explains the usage of -g option
PHSS_21252:
When ever a correlated event comes in, the browser jumps
to display the event it got correlated to, confusing the
user.
Resolution:
Browser displays the latest event, irrespective of
correlation
PHSS_21249:
The ovw image library does not handle GIF Extension blocks
in GIF87a images. The ovw image library does not correctly
set the color depth in GIF87a image files that contain
local color tables. The ovw image library calls a function
that can fail and it does not check the return code from
that function.
Resolution:
The ovw image library code was changed to recognize GIF
extension blocks in GIF87a images. The code was changed to
correctly set the color depth for GIF image files with
local color tables. The code was changed to check the
return code from a function that could fail.
PHSS_21245:
The pmd logging and tracing buffers were not large enough
to accomodate a very large filter specification. These
buffers can be used even when logging and tracing are not
enabled. For even larger filter specifications, the
OVsnmpEventOpen() call returned SNMP_BUILD_PDU_ERROR,
which is undocumented.
Resolution:
The pmd logging and tracing buffers have been increased to
accomodate the largest possible filter specification.
OVsnmpEventOpen() now limits the filter specification to
4000 bytes. If a filter larger than that is specified, the
following error message is returned:
SNMP_ERR_BAD_EVENT_FILTER
Filter length must be <= 4000 bytes
PHSS_21243:
The check on whether the integer length is greater than
sizeof(int)
is not being done properly.
Resolution:
The validation of integer length is done properly.
PHSS_21177:
Network Presenter code assumed that if an ovw was
encountered that did not have NP registered, all other
instances would not have NP registered, either.
It also only allowed for encountering at most two (not
necessarily consecutive) "empty" ports (ones which were not
running an ovw session). It quit when the second empty
port was seen.
Resolution:
The code has been modified to allow search to continue
after a connection to an ovw session is refused, and it
will tolerate up to 8 consecutive "empty" ports before
aborting the search for a map.
PHSS_21174:
As shipped in NNM6.0, ovdwevent exported "most" events
from the Binary Event Store. NNM6.1 shipped with the
default of only exporting the events directly used by the
reporting solution. Since NNM 6.1 changed the types of
events being exported to the Data Warehouse, the NNM Excel
Alarm Templates report on significantly different data in
NNM 6.1 than in NNM 6.0. The Excel availability templates
are obsolete in NNM 6.1 and they are no longer shipped with
NNM 6.1; however, customers upgrading from NNM 6.0 will
still have these availability templates on their system.
Resolution:
NNM6.1 modified to have the same default behavior as
NNM6.0. In addition, the user now has more control over
which events get exported.
The README file for the NNM Excel templates has been
modified to explain that reports generated from these
templates are dependent upon the types of data being
exported and the frequency of export operations. Also, the
README file now explains that the availability templates
are obsolete in NNM 6.1.
PHSS_21170:
1. Java libovw receives unexpected EOF condition on message
channel when application is unregistered. Continues to
attempt reads after EOF is seen.
2. A race condition existed in Java libovw which sometimes
resulted in an uninitialized variable and subsequent
null pointer exception. Uncaught exception in Network
Presenter caused it to hang at 10% stage of
initialization.
Resolution:
1. added code to handle EOF exception in libovw
2. added code to fix race condition in libovw
PHSS_21168:
Network Presenter was not checking for existence of the
needed size of graphic to display in scope pane and
textual content view. It used the generic symbol when no
symbol information was found, but failed to do so if other
sizes of the indicated symbol existed.
Resolution:
The code has been changed so it detects missing sizes of
symbols and substitutes the generic symbol in those cases.
PHSS_21166:
The pointer from a getenv() call was being saved and
used, even though the pointer may become invalid
later on.
Resolution:
The pointer will now be valid at all times, since it now
points to a saved copy of the getenv() string.
PHSS_21162:
1) Both of these symptoms are caused by the same problem.
Certain devices have been observed to return SNMP responses
from a different IP address than the one used to send the
request. When netmon begins pulling the IP address table,
it may inadvertantly switch which IP address it uses to the
one from which the previous response came from. This can
cause the timeout to happen if the new address is
unreachable from the management station.
2) The problem stems from the fact that the SNMP agent on
the RSM fails to return any physical address for its
interfaces when the interfaces.ifTable. The physical
addresses for these interfaces are discovered by netmon by
reading the ARP cache from other nodes within the network.
When netmon discoveres the newly added address/interface,
it fails to recognize that it belongs to the same node as
the other addresses because of this failure in the RSM SNMP
MIB. As a result, a new node is created rather than simply
adding the new interface to the existing node.
3)When a network becomes managed, netmon will attempt to
calculate the critical routes for that network back to the
management station, if it exists in the database. The
problem is that the filter prevents the management station
from being discovered, and there is a timing window where
netmon can think it found the management station when it
really has not done so. This will cause netmon to
dereference a bad pointer.
4) This problem was caused by an error handling routine
that expected a pointer to the offending SNMP pdu, but when
there is a timeout, there is no pdu to point to. This was
causing netmon to dereference a bad pointer and abort.
Resolution:
1)Netmon has been changed so that it will not
switch IP addresses in the middle of a
polling operation, even if the SNMP response
from the polled node comes from a new IP addr.
2)Netmon has been modified such that when it tries
to compare two nodes to see if they support the
same IP addresses, it will make the correct determination
even if one of the addresses is reported with a
zero MAC address.
3)Netmon has been changed so that it will not
try to use a partially-discovered managment
station in its critical route calculations.
4)The error-handling routine inside netmon has been
changed to not require an offending packet.
PHSS_21159:
1. The code which was opening the snmp session was not
checking the ov.conf file at all.
2. The dump was occuring as code was trying get a value
from an array index which was way greater than the array
size.
Resolution:
Fixed the library so that it checks the ov.conf file and
uses the value for NNM-INTERFACE if its present. Also added
code to check the index to prevent the dump.
PHSS_21157:
There was a NULL pointer access because no check is done to
see if the MenuItem is empty.
Resolution:
I have added a check, so that ovw returns an error if
theMenuItem is not empty.
PHSS_21152:
IPMap was overriding the user-specified no_symbol_changes
option when changing the label on the Internet symbol.
Resolution:
Changed the Internet symbol label localization code to
honor the user-specified no_symbol_changes flag.
PHSS_21150:
This happend because the iterator used to iterate thru the
collection list keeps information about the next element
in the list. If the next element was removed from the
list, ( which would happen in this case), the iterator
fails to iterate thru the rest of the list.
Resolution:
Now the iterator is reinitialized after each pass thru the
list of collections.
PHSS_21146:
ConnectorDown - Secondary failure events were being output
when the 'Extra Analysis' flag was turned on.
ScheduledMaintenance - The correlation assumed the trigger
event would always be an OpenView event. In cases where the
trigger events was not an OpenView event the Scheduled
Maintenance event would not be output by the correlation.
PairWise - The OV_Ack_Alarm and OV_Delete_Alarm events were
created by modifying and existing event. In cases where
varbinds were being used to change the severity of an event
the varbinds were not being removed from the new events.
Resolution:
The ConnectorDown correlation was changed to suppress all
secondary failure events unless they originated from an
important node or the annotation server did not respond.
The ScheduledMaintance correlation was changed to create
the OV_Planned_Outage event instead of modifying the trigger
event. The PairWise correlation was changed to create the
OV_Ack_Alarm and OV_Delete_Alarm event instead of modifying
the trigger events.
PHSS_21143:
ovw was not properly retaining enough information for the
OVwVerifyDrop() callback. As a result, a NULL pointer was
dereferenced.
Resolution:
ovw now saves the appropriate information so OVwVerifyDrop()
works properly.
PHSS_21141:
None - The user name was added to the crash log as a result
of changes made to implement NNM on terminal servers.
Resolution:
Added the user name to the output of the crash log file.
PHSS_21139:
snmpCollect when sending out the event, formats the
threshold value with "%.02lf" instead of "%.08lf"
Resolution:
Changed the format of threshold value from "%.021f"
to "%.08lg". Since the format is %.08lg, the floating
point number argument is printed in style f or e, with the
precision specifying the number of significant digits. The
style used depends on the value converted. Style is used
only if the exponent resulting from the conversion is
greater than or equal to the precision. Trailing zeros are
remove from the result. A radix character appears only if
it is followed by a digit.
PHSS_21137:
For SR4000134510, the functionality allowing OVwAddInput()
to be called withing a callback function was disallowed. A
PERMISSION DENIED error is always generated. Due to
customer query we are going to allow this functionality back
into the product.
Resolution:
The functionality to allow OVwAddInput to be called within a
callback has been readded.
PHSS_21135:
1. CommandList.C contains a method called addCommand that
passes a NULL command to a freeing routing under some
conditions.
2. In the processChangeCategoryEvent() function, the icat
variable was not being initialized so that when an event
category came in that did not match the list of categories,
the catalog number (represented by icat) was uninitialized
and caused an eventual core dump.
Resolution:
1. free_ClientCommand provides checking for null pointers
2. ill-defined categories are checked before assigning an
event to a new category
PHSS_21133:
The code that searched for bitmaps was not properly looking
in both the $OVW_BITMAPS/$LANG and $OVW_BITMAPS/C
directories.
Resolution:
The bitmaps handling code now follows the same procedure as
the registration file handling code.
PHSS_21073:
The pixmap and gif files for the MUX symbol were incorrect.
Resolution:
The pixmap and gif files for the MUX symbol were
regenerated.
PHSS_21015:
JavaScript is not very usable for treelist support. When an
item is selected, the Language aspect is lost.
Resolution:
Java treelist leveraged from the reporting GUI works well
for snmpviewer. This GUI will be used instead of the
JavaScript version.
PHSS_20982:
The window specifications for urls that are launched from
the Launcher are either ignored or set incorrectly from
what is specified in the WLRF WebWindow specifications.
Resolution:
Fixed the launcher processes to adhere to the specifications
in the WLRFs.
PHSS_20938:
The event severity field did not have enough room to fit
all the Japanese characters.
Resolution:
The event severity field now has enough room to fit the
Japanese characters for "Major".
PHSS_20795:
Consolidated Patch
PHSS_20790:
There were two problems, first the CDE help and WinNT help
were missing a topic for the "What's New with NNM..." As
well, the html webhelp had an incorrect link that was
broken.
Resolution:
The updated CDE and WinNT help files now include all the
"What's New with NNM..." topics. As well, the html
webhelp now has the correct link.
-----------------------------------------------------------
"Find By ..." features were not implemented in Network
Presenter in the original release.
Resolution:
Network Presenter "Find By ..." functionality has been
fixed.
-----------------------------------------------------------
The formatted Category string gets truncated.
A memory overwrite caused the coredump.
Resolution:
All three problems fixed by code changes within libovutil/
ovutil.dll.
-----------------------------------------------------------
ovalarmsrv had two hard coded ports which were not
configurable by the end user. This was a design choice
since at the time Java had no way of accessing
/etc/services. The launching programs have been modified to
pass the java code the correct ports.
Resolution:
ovalarmsrv was modified to use the services file to lookup
the default port numbers. The entries ovalarmsrv &
ovalarmsrv_cmd now specify the ports that are used by
ovalarmsrv during startup. The launching programs have been
changed to access this information as well.
-----------------------------------------------------------
Ovrepld maintains a list of memory objects needing to be
freed at the end of an action. In one case, ovrepld placed
the same object on this list twice, causing the memory to be
freed twice. This would cause the application exception on
NT when running with Service Packs 4 or 5, which have much
more agressive memory management strategies, and are more
sensitive to these types of coding errors.
Resolution:
Ovrepld was changed so that it does not try to free the same
memory twice.
-----------------------------------------------------------
Code had been previously added to display the top submap of
a highlighted symbol based on the appname and an algorithm.
However, it did not check for the possiblity appname would
be null. The root submap is created by ovw not by an
application so the appname was never set.
Also, other checks weren't being made in the code for user
created submaps vs application (other than ipmap) created
submaps. So, those cases were missing.
Resolution:
Added to the existing code a check for a null appname in
addition to checking different scenarios involving user
created submaps and application submaps other than ipmap.
-----------------------------------------------------------
OVwHighlightObject() will now display the submap on top that
first has a symbol in an ipmap created submap. Otherwise,
it bases it on the lowest submapid.
For the EUC problem, xnmevents was incorrectly interpreting
the first byte of a multibyte character as a place to split
the event text. For the Solaris display problem, xnmevents
was not correctly determining the width and height of the
events.
Resolution:
xnmevents now correctly finds white space to split the event
text and displays the characters correctly. As well,
xnmevents also determines the width and height of the event
text.
-----------------------------------------------------------
For each field in an object the function checks if the
field exists in the field-value list and then compares the
value set, for the field, for that object with the value
supplied, for the field, in the field-value list. In the
case of a name field, a different kind of check is done;
the value of the name field in the field value list is used
to search for the corresponding object id. No check was
however done to see if the object id returned is of the
object for which the fields are being matched.
Resolution:
Now the object-ids are compared for a match.
-----------------------------------------------------------
Even though the text box widget is attached properly, its
resizeWidth property is set to TRUE. So when a new action
is selected, the text box tries to resize itself causing the
widget to be misplaced.
Resolution:
I have changed the code so that the text box has
resizeWidth property set to FALSE. Instead the size of the
selected string is calculated and the textbox resized
accordingly.
-----------------------------------------------------------
1. Files were opened even if they didn't exist.
2. Parser didn't have support for drive letters.
Resolution:
1. Added ios::nocreate to ifstream constructor.
2. Added support for drive letters to parser.
-----------------------------------------------------------
Several places in the code that deal with Varbinds - such
as trap processing, trap formatting, tracing & logging -
are all assuming that the PDU syntax is legal at this point.
If not, these modules can print out garbage characters or
even coredump.
Resolution:
A search was made for all places where this might possibly
happen, and fixes were put into all rhe places found.
-----------------------------------------------------------
A part of the code which updates the window was getting into
an infinite loop under minimized state. That was the cause
for the hang.
Resolution:
Changed the code so that the infinite loop does not occur.
-----------------------------------------------------------
The snapshot properties dialog box did not have an
equivalent Japanese version. Moreover, ovw should display
the Map Properties dialog, which is properly localized and
does not core dump.
Resolution:
The Map->Snapshot->Properties menu pick now brings up the
Map Properties dialog box with the snapshot's information.
-----------------------------------------------------------
A function matchFilters() in Client.cpp of the ovalarmsrv
process was filtering too much.
Resolution:
The segment of code that did the overfiltering has been
removed.
-----------------------------------------------------------
A search for a collection in a collection list can be done
based on node name or based on both node name and instance
list. The code was written assuming that if a NULL instance
list is passed to the search routine, the routine will use
only node name for the search. This is not however the case.
Resolution:
The search routine is modified so that it does not dump on
a NULL instance list. Also the code that is calling it has
been modified to pass the correct parameters.
-----------------------------------------------------------
The code deleted applications while higher level function
calls were processing the application list. This caused
doubly freeing memory, accessing the freed memory for the
application, or corrupting the traversal of the application
list. Since the memory was corrupted in terms of the
operations being done on the application structure or
application list, then pmd would coredump.
Resolution:
The code now disables applications rather than deleting them
during application list processing. This ensures that the
application list remains intact throughout event processing.
-----------------------------------------------------------
Upon the receipt of the next event, the application list is
evaluated for disabled applications and these are removed
prior to processing the newly received event.
Ovrepld maintains a flag on a per-collection-station basis
that indicates whether there is currently a demand-poll in
progress for that station. This field is not correctly
initialized on NT platforms.
Resolution:
Ovrepld was changed so that it correctly initializes the
demand-poll flag.
-----------------------------------------------------------
1) The cause of this problem is that netmon is attempting to
dereference some pointers which normally are initialized
to meaningful values. If the agent address is zero,
these pointers will not be initialized, and this can
cause netmon to abort with a bad memory reference.
Currently, netmon will initiate a configuration poll
followed by a discovery poll of a node that sends it a
link-up trap. Normally, these polls would happen at
infrequent intervals, but if the node generates lots of
link-up traps, these polls will end up happening very often.
These polls can consume significant computing cycles on the
device being polled.
3) When the netmon process initializes itself, after loading
the topology database, it tries to initialize a portion of
the event correlation subsystem known as the "ECS Annotation
Server". This module requires that a certain capability
field "isMgX" be defined in the object database. If this
field is absent, netmon will exit without producing any
error messages.
4) The original design of netmon overlooked this detail of
check for root device's if_status. This defect will only
occur when netmon select a root device that has
if_status != NORMAL.
5) The latest Cisco IOS will dynamically add and remove
entries from the interface MIB table as ISDN connections
come and go. If netmon begins pulling the interface table
when there are (for example) 10 interfaces, and then
interface 11 gets added before netmon completes pulling this
table, it will report this event. Netmon is pulling the
ifNumber variable before pulling the table, and it will
complain if it finds more entries in the table than ifNumber
reported.
Resolution:
1) Netmon was changed to always initialize the pointers
to meaningful values before looking at them.
2) This problem is fixed by modifying netmon so that it will
only initiate the configuration poll if the link-up trap
indicates an interface that we do not already know about.
This should be an infrequent situation.
3) This problem has been fixed by changing netmon to
generate an error message to be displayed by ovstatus,
explaining the problem and how to fix it.
4) This defect is fixed by changing netmon to only select an
interface as root device when it's if_status is NORMAL.
5) Netmon was changed to no longer look at the ifNumber for
a managed node, and to use other methods to detect a
spinning ifTable.
-----------------------------------------------------------
The help topic index for the application was incorrect.
Resolution:
The registration file for this application now has the
correct help topic index.
-----------------------------------------------------------
In many cases when a symbol is deleted and is a popup symbol
the code was not resetting the popup information.
Resolution:
Added code to the map symbol deletion code that resets the
popup symbol information.
-----------------------------------------------------------
For 8606109734: There are two conditions that determine
whether an event is sent or not. They are the fact that a
connection exists between ovstop and ovspmd, and the state
of the daemon being either RUNNING or NOT_RUNNING.
On NT, there is a race condition between the disconnection
of ovstop from ovspmd and the receipt of the SIGCHLD signal
from the death of the daemons being stopped. This leads the
code to believe that the daemon was not stopped by ovstop,
and consequently, an event is generated.
In the case of a daemon unexpectedly dying while ovstop is
being run for other daemons, there is no logic to determine
that the daemon should send an event. Since there is a
connection between ovstop and ovspmd, no event is sent when
one should.
In the last case, since the process is in PAUSED state, then
the state check for RUNNING or NOT_RUNNING will fail, and
consequently, the event will not be sent when it should.
For 8606108882: the logic for managing the setting of
SHLIB_PATH or LD_LIBRARY_PATH should have considered the
need for the value set prior to starting ovspmd to be passed
to third-party applications. Rather than overwriting the
value, the code should have prepended the value from
$OV_CONF/analysis/ovdwenvs.conf to the value from the
environment if the variable was set.
Resolution:
For 8606109734: The fix to the code was to create a flag to
determine whether to send or not send the event. The logic
is that during ovstart, those daemons that are being started
will have the flag set to send the event on unexpected
termination. On ovstop, the flag is cleared for those
processes that are being stopped.
For 8606108882: Ovspmd saves a copy of SHLIB_PATH ( HPUX )
or LD_LIBRARY_PATH ( Solaris ) at startup, and the code will
prepend the value specified in
$OV_CONF/analysis/ovdwenvs.conf to the value prior to
starting daemons.
-----------------------------------------------------------
ovmapcount -r deletes objects in the Map Database which do
not have corresponding objects in the object database. A
list iterator goes through a list of Mapobjects and checks
if the object exists in the object database. If it does not,
it calls MapObject::doDelete. This deletes all symbols,
child submaps etc connected with the object and then adds
the object to the list of objects to be deleted. When
deleting the connection symbols connected with the
MapObject, the current Mapobject changes. The changed
MapObject gets deleted in the current iteration. Later when
the changed MapObject gets its chance to be deleted, it
finds that its already been deleted. Dumps Core.
Resolution:
In MapObject::doDelete, we save the current object getting
deleted. At the end when we are about to add the current
object to the list of objects to be deleted, we check
whether its changed. If it is, we do not add it otherwise
we go about deleting it.
-----------------------------------------------------------
In Network Presenter precedence ordering was simply not
implemented.
NetPresenter ENH: menu graying was not implemented in
initial release
NetPresenter: TargetSymbolType was not implemented
NetPresenter: PopupMenu construct was not being parsed
correctly.
Resolution:
The CGI ARF parser library has been modified to sort
the various registrations according to the documented
criteria.
NetPresenter has been enhanced to account for the various
criteria that specify when menu items and toolbar buttons
should be active or inactive (normal or grayed)
NetPresenter has been modified to take capability fields
of popup menu's target object into account when building
the popup menu.
NetPresenter menu manager was modified to correctly parse
the PopupMenu construct
-----------------------------------------------------------
The problem is caused by the fact that loadhosts is using a
function in ovutil.dll to send the pings, and this library
function is not properly adjusting the byte-order of the IP
address before attempting the ping.
Resolution:
This patch corrects the byte-ordering expected by the
utility function in ovutil.dll, and corrects the byte-
ordering used by netcheck.exe and xnmtopoconf.exe, which
was wrong.
-----------------------------------------------------------
The defect was that the data source name is ovdbrun and not
ShMem NNM, which is the communications mechanism used for
client/server database communications.
Resolution:
The resolution is to change the value of defaultrdb in the
script at line 99 to be ovdbrun.
-----------------------------------------------------------
The Japanese registration files for ipmap had the same label
for both "TopM Connector Count" and "TopM Segment Count"
Resolution:
The Japanese registration files now have the correct labels
for each field.
-----------------------------------------------------------
xnmevents was incorrectly calculating the width of the date
field, truncating the last column of the seconds field.
Resolution:
xnmevents now correctly calculates the width of the widest
possible date.
-----------------------------------------------------------
The defective code was in ovalarmlaunch.cpp, in the main
program. OvWwwInit(), which initializes the language, was
being called too late.
Resolution:
in the Main() function for the alarmbrowser, the OvWwwInit
() function is moved to before the call to
read_trapspec_file() so that the LANG will contain the right
value (i.e. lang is initialized in OvWwwInit()) before the
trapd.conf file is read. In that way, the Japanese version
is the one that is read instead of the C version of the
file.
-----------------------------------------------------------
The environment variable OVwSymDir affects both ovw and
Network Presenter. However, Network Presenter and ovw
process its contents in different, inconsistent manners.
ovw takes the paths provided by the env var and uses them
as absolute paths, not attempting to determine if they have
language-appropriate components. NetPresenter, on the
other hand, is taking the contents and appending
language-specific components in an effort to find
appropriate subdirectories. When the paths already contain
language-appropriate components, NetPresenter appends yet
another, then fails to find the composed directories as
they do not exist.
Resolution:
libovwparser has been modified to look for and remove
trailing language-specific and language-generic
(read: "C") components prior to passing the contents
of the environment variables OVwSymDir, OVwRegDir, and
OVwFieldDir to the part of the library that looks for
language-specific subdirectories. It has also been
modified so it uses the value returned by setlocale()
for LC_MESSAGES rather than $LANG to build
language-specific subdirectory paths.
regverify has been modified to use the library code
described above to process path names.
-----------------------------------------------------------
The flag which records changes to the background graphics
is not set for this condition: change from one background
graphic to another.
Resolution:
"change from one background graphic to another" is included
to a list of conditions based on which the flag which
records changes to the bacground graphics is set
-----------------------------------------------------------
The SNMP agent on the NT Management station does not return
the data properly for Get-Bulk requests. rnetstat uses
get-bulk to retrieve data from the NT MS. And rnetstat was
not able to properly handle the improper get-bulk response
data returned from the NT MS.
Resolution:
Modified rnetstat so that in case get-bulk response does not
contain proper data, then it will get the data column by
column.
-----------------------------------------------------------
This happens due to the difference in the way in which the
functions attached to menu items on the menubar are
interpreted by the parsing routines and the ovw
applications. Applications assume that these functions will
have a context expression of 'AllContext' while the parser
gives them a context of 'EverReady'.
Resolution:
The specific case in which the applications request for a
function with a context expression of 'AllContext' while the
function actually has a context expression of 'EverReady' is
been taken care in the search routine.
-----------------------------------------------------------
When no symbol type gets selected, The symbol index pointer
that is used in the function that changes the symbol is
NULL. No check is made for this NULL pointer. This leads to
an access violation.
Resolution:
In functions where the symbol or connection change is
handled, a check has been put to see if the symbol index
pointer is NULL.
-----------------------------------------------------------
Memory was not being freed in several places.
Resolution:
Memory has been freed in appropriate places.
-----------------------------------------------------------
NNM needed to have the Oracle fileset Pro*Cobol installed to
rebuild libclntsh.sl. This check was not done.
Oracle patches now require that libnsl_s be compiled in.
This was not in the original makefile clntsh.mk that Oracle
shipped.
Resolution:
A check for the missing file was added to ovdbsetupo1.sh to
verify that the file from the Pro*Cobol fileset was
available. This ensures that the rebuilding of libclntsh.sl
will not cause unresolved references for NNM.
The makefile was updated to now use libnsl_s if it exists on
the system.
-----------------------------------------------------------
The defect was that the file should have been truncated on a
partial write.
Resolution:
The file is truncated back to the end of the last full
record in the file.
-----------------------------------------------------------
The problem has to do with a case where a connector device
(repeater or switch) is not getting properly "oriented".
"Oriented" means that the device tells us which of its ports
it hears a reference address that NNM has chosen for that
network, which is called the "root device". If the
connector can not tell us which port hears the "root
device", NNM is not able to properly lay out that connector,
and should not create any more than one segment attached to
that device.
There is a defect in the netmon process where it was
attempting to lay out segments around a connector device
which was not oriented. This can cause many different
mis-behaviors, such as the continual creation of many
thousands of ficticious interfaces and segments. Such
behavior can make ipmap take a very long time to synchronize
a map.
Resolution:
This problem is fixed by changing netmon to properly check
to make sure a device is oriented before attempting to do
layout relative to that device.
-----------------------------------------------------------
Message catalogs did not have the two words,
"Events" and "Alarms" translated.
Also, the algorithm for converting the text was
incorrect and did not make the modifications
correctly.
Resolution:
The algoritm was fixed and the
util_libs.2 message catalog were fixed.
-----------------------------------------------------------
The defect is that the relational database needs to maintain
timestamps to allow for reports to be written against these
fields. For example, a report of objects created during a
period of time would not work.
Resolution:
There is a flag that denotes that timestamps should not be
updated. Ovtopoconv, which was the code that was the basis
of ovdwtopo, used this flag, but ovdwtopo had it removed.
-----------------------------------------------------------
The menu options Copy, Modify and Show Data should be
in-sensitive when user selects more than one mib object.
Resolution:
When user selects more than one mib object in the xnmcollect
gui, the menu options Copy, Modify and Show Data will be
greyed out.
xnmevents has 5000 byte buffer for processing events, but
ovactiond has only 2048.
Resolution:
Increased the buffer size of ovactiond to 5000.
-----------------------------------------------------------
The defect was that the lrf file, ovalarmsrv.lrf, should
have specified 120 seconds. This is what ovalarmsrv is
expecting to have before ovspmd sends the signal.
Resolution:
The timeout has been set to 120 seconds for the
ovalarmsrv.lrf file.
-----------------------------------------------------------
There was an improperly configured kernel parameter
on HPUX 11.0.
ovalarmsrv was not detaching all threads properly.
Resolution:
There appear to be two problems on 11.0 which are related to
this defect.
The configurable kernel parameter max_thread_proc defaults
to 64. During an event storm every new event added results
in a thread being created in ovalarmsrv. ovalarmsrv can
quickly consume 64 threads in this case. Similarly
onfigured Suns allow up to 2048 threads per process. This
is more than sufficient to handle these storms.
The first basic recommended change is to increase the kernel
parameter max_thread_proc to 2048. The maximum value allowed
might be constrained by nproc being too low. This value can
be increased by modifying the parameter maxusers to ~200
The second part of the problem here is that threads being
created on 11.0 in ovalarmsrv which are not being detached.
A non-detached thread, is a non-recovered system resource.
The code needs to change to detach all threads.
-----------------------------------------------------------
Both MapHeight and MapWidth are of type Dimension, which is
an unsigned short of 2 bytes. But they are read in as DWORD
which is of 4 bytes from the Registry using
RegQueryValueEx(). Thus MapHeight which is read first into
memory gets overwritten by the MapWidth value which is read
immediately after.
Resolution:
RegQueryValueEx() is passed a temporary variable and the
DWORD values for MapHeight and Mapwidth are read into it.
Then they are casted to unsigned short and then put into the
memory allocated for the resource. Thus the overwriting is
prevented.
-----------------------------------------------------------
ovw was running out of resources, but did not detect the
problem.
Resolution:
ovw now limits the number of submaps open, to avoid running
out of resources.
-----------------------------------------------------------
After investigating this problem it only occurs on 11.X.
11.X has a different memory model than 10.X, Solaris, NT.
It does not write data based on a 4byte boundary as the
other platforms.
The problem was an array bound overwrite. A character array
had been declared with one character short. The last
character which was a null terminator was written into the
next data byte. This next data byte happened to be the
first character of the message array. So, the first
character in the message array was null.
Resolution:
The size of the array for the date was enlarged to ensure
enough space for the data.
-----------------------------------------------------------
ipmap is not setting the Initial Verify switch properly, and
so persistence levels
can be changed on existing maps by modifying the
registration file.
This is not supposed to happen.
Resolution:
Changed ipmap to set Initial Verify switch upon creation or
initial load of map.
-----------------------------------------------------------
This is caused by the label "widget" used by xnmappmon
being a few pixels too small.
Resolution:
Modified the wnmappmon.rc so that the label widget
has enough height to contain the Kanji characters.
-----------------------------------------------------------
The code was not checking properly for the IP Address.
Resolution:
Proper check has been incorporated on the IP Address
-----------------------------------------------------------
This defect is caused by a global variable which is
pointing off to free'ed memory. The modify will cause
the variable to be set, the delete will delete the
area of memory it is pointing to, the add will then try
to use that memory to fill default values.
Resolution:
Changed the code so that it resets the global variable
if it deletes what it's pointing to.
-----------------------------------------------------------
The date formatter is not noting the sentinel value
correctly, so that the string saved to ovwdb reads some time
in 1970 rather than "never expires".
Resolution:
Changed call to format_time() to be _OVLICFormatDate().
-----------------------------------------------------------
When the error to be displayed is that "the string is
empty", the string variable, which is empty in the first
place, is being displayed to the user as "empty string on
string $string" which shows up as "empty string on string
"" "
Resolution:
The string variable is checked to see if it is empty.
If so then the name associated with this string, which the
user sees on the UI, viz., Polling Interval, is displayed
in the error message as "empty string on string Polling
Interval"
-----------------------------------------------------------
There is no provision in NT to replace a collection that is
being displayed with another one, that is being collected
but not currently displayed because of limit on the number
of lines that can be displayed.
Resolution:
A new button [Replace] has been added to the 'Line
Configuration' dialog box. On pressing this button a dialog
box pops up that shows all the collections that are
currently not being displayed. Selecting one of these lines
and pressing OK will cause this new collection to replace
the one that was selected in the 'Line Configuration' dialog
box.
-----------------------------------------------------------
When a scroll bar is moved the button position is returned
as a value between 0-32767.
This value needs to be mapped to
the actual scroll bar length (min-max).
This mapping was not
properly occuring.
Resolution:
The position of the scroll bar button, as returned by the
function, is now recalculated using a macro. This macro
transposes the value between 0-32767 to a value
between min
and max of the actual scroll bar.
-----------------------------------------------------------
ovnnmPassword is operating as it should. It only shows
valid passwords for the current realtime date. So, any
licenses for testing purposes that have been entered with a
start date in the future aren't considered valid.
Resolution:
Because of a number of issues, it would be to hard to
redesign this so ovnnmPassword recognizes passwords with
future start dates. So, a warning was added to
ovnnmPassword that gets generated when the user enters a
password through the GUI with a future start date.
-----------------------------------------------------------
The URL is simply incorrect, due to the
fact that it changed right after the release
of NNM 6.0
Resolution:
The URL has been corrected
-----------------------------------------------------------
In several places in the mwActions.C file, namely functions:
_mwMoveStart()
_mwLButtonUP()
_mwMoveMouse()
_mwMoving()
_mwMoveEnd()
the icon pointer was retrieved and used, yet it was null,
having just been deleted. This dereferenced a NULL pointer
and caused a core dump on NT.
Resolution:
A new check was made to see if the icon is null. If it is
NULL, the the state of icon_moving is set to false and the
function returns
-----------------------------------------------------------
The position of the child submap on the screen is decided
by the position of its parent. When the child submap comes
up it tries to locate the coordinates of the parent. In case
the parent is already closed then the function fails to find
the location of the parent and coredumps
Resolution:
To take care of this boundary case a check is implemented.
If the parent is no longer valid then a coordinate value of
(0,0) is returned for the parent.
-----------------------------------------------------------
The routine that extracts description from an event is
assuming the node field to be greater than a certain size.
During formatting, if the node happens to have a name in
japanese language, the characters could be more than 1 byte
in length. This causes improper formatting and finally
leads to a core dump.
Resolution:
Now no assumption is made on the size of the node field.
-----------------------------------------------------------
findroute tries to query the ifEntry based on an invalid
ifIndex. This causes the agent to return one or more packets
with null varbind entries. The code is not checking for
NULL, and this causes a coredump. The same thing happens
when a query to ARP cache is done.
Resolution:
A check has been added in both storeIfEntry and
storeArpEntry functions to check for NULL varbinds.
-----------------------------------------------------------
The parameters being passed to the function
(shiftLatestData) that reduces the data to be graphed were
wrong when the value of noReducePercent was 100. This
prevented data from being reduced. Since the data was not
reduced the function was called again and again in a loop.
When the value was 99% in certain cases the number of points
to be merged would come down to 1. Since a minimum of 2
points are required for the merge, the merge never occured.
This also caused an infinite loop.
Resolution:
Now the correct parameters are being passed to the function
shifLatestData.
In addition if the number of points to be merged comes down
to 1 then it is treated in the same way as when the value of
noReducePercent is 100.
-----------------------------------------------------------
There was no completion state being communicated from ovspmd
to ovstart.
Resolution:
Added completion state communication to ovspmd.
SR:
8606208332 8606198470 8606207914 8606207014 8606206368
8606207927 8606207272 8606208303 8606205181 8606112461
8606196798 8606200367 8606206501 8606182861 8606206560
8606193890 8606200734 8606194634 8606193368 8606196210
8606184761 8606193427 8606195686 8606163748 8606193919
8606184718 8606184661 8606181224 8606187163 8606188054
8606192654 8606182117 8606181221 8606180991 8606188667
8606164874 8606158089 8606181144 8606187001 8606174051
8606180345 8606183292 8606159962 8606168074 8606181324
8606178713 8606186007 8606179008 8606176511 8606182233
8606158937 8606167878 8606165934 8606126308 8606156207
8606178817 8606146083 8606173390 8606135598 8606178549
8606172170 5003459347 8606184497 8606169415 8606135378
8606175989 8606157949 8606172049 8606147265 8606154432
8606140170 8606146335 8606173875 8606179719 8606154617
8606146538 8606154149 8606163626 8606173837 8606173134
8606180092 1653310789 8606161561 8606173692 8606168719
8606162558 8606165664 8606168944 8606147580 8606157083
8606172142 8606140611 8606170778 8606161773 8606166909
8606163529 8606142857 8606156306 8606157483 8606155201
8606159548 8606156271 8606126644 8606157855 8606160975
8606156123 8606159597 8606162606 8606157822 8606140956
8606136514 8606159143 8606159948 8606146598 8606152495
8606140795 8606145318 8606145726 8606143479 8606155028
8606155024 8606154365 8606138672 8606155973 8606135231
8606155165 8606145581 8606156272 8606141776 8606156831
8606147360 8606154448 8606137446 8606144280 8606135819
8606133597 8606133599 8606133592 8606156017 4000134569
8606135683 8606136926 8606135919 8606144312 8606146921
8606144318 8606156056 8606139990 8606134614 8606143411
8606152466 8606136649 8606138853 8606135141 8606142854
8606147243 8606136871 8606140478 8606137235 8606140544
8606132074 8606135897 8606135941 8606139084 8606134163
8606140286 8606135035 8606137119 8606139923 8606139757
8606135818 8606139259 8606143378 8606138665 8606135418
8606132645 8606127790 8606131304 8606135076 8606134890
8606133326 8606134658 8606131091 8606127552 8606127799
8606132829 8606134901 8606125710 8606133061 8606128730
8606129297 8606132910 8606131529 8606129673 8606130115
8606129346 8606107995 8606124599 8606127748 8606128737
8606128658 8606126265 8606128112 8606125083 8606127679
8606129304 8606127209 8606126160 8606127119 8606112822
8606127418 8606128603 8606128129 8606129204 8606126451
8606114064 8606128970 8606112806 8606110740 8606125075
8606125085 8606123997 8606125343 8606114688 8606124072
8606114572 8606124734 8606126397 8606105527 4701422725
8606107116 8606126138 8606126148 8606112246 8606109344
8606123927 8606126952 8606107504 8606124721 8606103926
4701429449 8606124258 8606126583 8606114722 8606113943
8606107500 8606107501 8606105207 8606103506 8606109600
8606106814 8606105563 8606105086 8606104393 1653298042
8606106339 8606105089 8606106578 8606106939 8606114001
8606102140 8606107110 4701430272 8606110442 8606103512
8606103711 8606107114 8606104603 8606104720 1653311852
5003468702 8606108080 8606110367 8606106309 8606107555
8606109734 8606104767 8606108882 8606109576 4000123123
8606114610 8606106313 4701429332 8606110419 8606111707
4701411694 4701422386 8606106073 8606106118 8606112275
1653304493 8606104490 8606105463 8606101667 8606113449
8606102919 8606105745 8606103848 4701429738 1653309864
8606103885 8606107089 8606104498 8606104978 8606108695
8606108858 1653288985 4701430090 8606112208 8606101472
8606107052 8606105633 8606110945 1653309195 8606105557
8606106769 8606109879 4701428102 8606114032
Patch Files:
/opt/OV/www/cgi-bin/ovlaunchreg.exe
/opt/OV/www/cgi-bin/Main/Snmp
/opt/OV/www/cgi-bin/webappmon.exe
/opt/OV/www/cgi-bin/ovlaunch.exe
/opt/OV/www/cgi-bin/ovlogin.exe
/opt/OV/www/cgi-bin/OpenView5.exe
/opt/OV/www/cgi-bin/jovwreg.exe
/opt/OV/www/cgi-bin/snmpviewer.exe
/opt/OV/www/cgi-bin/ovalarm.exe
/opt/OV/www/htdocs/classes/jovw/debug.jovw.jar
/opt/OV/www/htdocs/classes/jovw/jovw.jar
/opt/OV/www/htdocs/classes/launcher/debug.ovlaunch.jar
/opt/OV/www/htdocs/classes/launcher/ovlaunch.jar
/opt/OV/www/htdocs/classes/jalarm/debug.jalarm.jar
/opt/OV/www/htdocs/classes/jalarm/jalarm.jar
/opt/OV/www/htdocs/classes/libovw.jar
/opt/OV/www/htdocs/classes/debug.libovw.jar
/opt/OV/www/htdocs/classes/nnmReporting/
debug.nnmReporting.jar
/opt/OV/www/htdocs/classes/nnmReporting/nnmReporting.jar
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/cnttsk.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/nnmswitchref.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/nnmswitchtsk.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/cntref.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/rptref.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/rpttsk.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/cxtglos.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/cxtoth.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/cxtref.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Scope/scpref.htm
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Scope/scptsk.htm
/opt/OV/www/htdocs/C/launcher/login.tmpl
/opt/OV/www/htdocs/C/launcher/retry.tmpl
/opt/OV/www/htdocs/C/launcher/launcher.tmpl
/opt/OV/www/htdocs/C/launcher/jscript.html
/opt/OV/www/htdocs/C/launcher/browser.html
/opt/OV/www/htdocs/C/launcher/welcome.html
/opt/OV/www/htdocs/C/launcher/webwin.html
/opt/OV/www/htdocs/C/launcher/javadoc/html/intro.html
/opt/OV/www/htdocs/C/launcher/javadoc/html/ovlogo_l.gif
/opt/OV/www/htdocs/C/launcher/javadoc/html/start.html
/opt/OV/www/htdocs/C/launcher/javadoc/sample/
TestSession.java
/opt/OV/www/htdocs/C/launcher/javadoc/doc/AllNames.html
/opt/OV/www/htdocs/C/launcher/javadoc/doc/
Package-hp.ov.session.html
/opt/OV/www/htdocs/C/launcher/javadoc/doc/
hp.ov.session.NoSessionException.html
/opt/OV/www/htdocs/C/launcher/javadoc/doc/
hp.ov.session.Session.html
/opt/OV/www/htdocs/C/launcher/javadoc/doc/packages.html
/opt/OV/www/htdocs/C/launcher/javadoc/doc/tree.html
/opt/OV/www/htdocs/C/launcher/javadoc/index.html
/opt/OV/www/htdocs/C/launcher/welcomecontent.html
/opt/OV/www/htdocs/C/launcher/welcometopics.html
/opt/OV/www/htdocs/C/launcher/js_replace.tmpl
/opt/OV/www/htdocs/C/launcher/js_replace_br.tmpl
/opt/OV/www/htdocs/C/nnm/snmpviewer/tree.tmpl
/opt/OV/www/htdocs/C/ReleaseNotes/ReadmeAll_NNMGR.html
/opt/OV/www/htdocs/C/ReleaseNotes/ReadmeNew_NNMGR.html
/opt/OV/www/htdocs/C/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html
/opt/OV/www/htdocs/C/ReleaseNotes/ReadmeInstall_NNMGR.html
/opt/OV/www/htdocs/C/java_libovw/doc/AllNames.html
/opt/OV/www/htdocs/C/java_libovw/doc/
Package-hp.ov.libovw.html
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.LibOvw.html
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.OVwLocateResultSymbol.html
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwMapInfo.html
/opt/OV/www/htdocs/C/java_libovw/doc/tree.html
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwLocationInfo.html
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwLocationList.html
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.16.gif
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.20.gif
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.26.gif
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.32.gif
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.38.gif
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.44.gif
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.50.gif
/opt/OV/www/htdocs/bitmaps/C/misc/binoc.16.gif
/opt/OV/www/htdocs/bitmaps/C/misc/binoc.20.gif
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
cnttsk.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
rptref.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
nnmswitchref.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
nnmswitchtsk.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
rpttsk.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
cntref.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Context/
cxtglos.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Context/
cxtoth.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Context/
cxtref.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Scope/scpref.htm
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Scope/scptsk.htm
/opt/OV/www/htdocs/ja_JP.SJIS/launcher/login.tmpl
/opt/OV/www/htdocs/ja_JP.SJIS/launcher/retry.tmpl
/opt/OV/www/htdocs/ja_JP.SJIS/launcher/welcometopics.html
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeAll_NNMGR.html
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeNew_NNMGR.html
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeInstall_NNMGR.html
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
cnttsk.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
rptref.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
nnmswitchref.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
nnmswitchtsk.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
rpttsk.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
cntref.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Context/
cxtglos.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Context/
cxtoth.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Context/
cxtref.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Scope/
scpref.htm
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Scope/
scptsk.htm
/opt/OV/www/htdocs/ja_JP.eucJP/launcher/login.tmpl
/opt/OV/www/htdocs/ja_JP.eucJP/launcher/retry.tmpl
/opt/OV/www/htdocs/ja_JP.eucJP/launcher/welcometopics.html
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeAll_NNMGR.html
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeNew_NNMGR.html
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeInstall_NNMGR.html
/opt/OV/www/bin/htpasswd
/opt/OV/lib/libovwww.2
/opt/OV/lib/libovwparser.2
/opt/OV/lib/libovsnmp.2
/opt/OV/lib/libov.2
/opt/OV/lib/libovutil.2
/opt/OV/lib/libovgui.2
/opt/OV/lib/libovextfmt.2
/opt/OV/lib/libevent.2
/opt/OV/lib/libovtopm.2
/opt/OV/lib/libovfilter.2
/opt/OV/lib/libovw.2
/opt/OV/lib/nls/ja_JP.SJIS/xnmsnmpconf.cat
/opt/OV/lib/nls/ja_JP.SJIS/events.cat
/opt/OV/lib/nls/ja_JP.SJIS/util_libs.cat
/opt/OV/lib/nls/ja_JP.eucJP/xnmsnmpconf.cat
/opt/OV/lib/nls/ja_JP.eucJP/events.cat
/opt/OV/lib/nls/ja_JP.eucJP/util_libs.cat
/opt/OV/bin/ovsessionmgr
/opt/OV/bin/regverify
/opt/OV/bin/ovstart
/opt/OV/bin/ovstop
/opt/OV/bin/ovstatus
/opt/OV/bin/ovspmd
/opt/OV/bin/xnmevents
/opt/OV/bin/ovactiond
/opt/OV/bin/ovtrapd
/opt/OV/bin/netmon
/opt/OV/bin/ovrepld
/opt/OV/bin/loadhosts
/opt/OV/bin/snmpCollect
/opt/OV/bin/xnmcollect
/opt/OV/bin/xnmtopoconf
/opt/OV/bin/xnmgraph
/opt/OV/bin/ipmap
/opt/OV/bin/ovtopodump
/opt/OV/bin/ovtopofix
/opt/OV/bin/ovtopmd
/opt/OV/bin/xnmbuilder
/opt/OV/bin/Perl/lib/ovbackup.pm
/opt/OV/bin/ovexprguru
/opt/OV/bin/xnmbrowser
/opt/OV/bin/xnmpolling
/opt/OV/bin/ovweb
/opt/OV/bin/findroute
/opt/OV/bin/xnmappmon
/opt/OV/bin/rnetstat
/opt/OV/bin/netcheck
/opt/OV/bin/ovhelp
/opt/OV/bin/ovw
/opt/OV/bin/ovwdb
/opt/OV/bin/ovuispmd
/opt/OV/bin/ovalarmsrv
/opt/OV/bin/ovalarmadm
/opt/OV/bin/ovdbcheck
/opt/OV/bin/ovdwtrend
/opt/OV/bin/ovcolsum
/opt/OV/bin/ovcoltosql
/opt/OV/bin/ovcoldelsql
/opt/OV/bin/ovdwevent
/opt/OV/bin/ovdweventflt
/opt/OV/bin/ovdwtopo
/opt/OV/bin/ovdwquery
/opt/OV/bin/ovcolqsql
/opt/OV/bin/ovdbsetupo1.sh
/opt/OV/bin/ovdbsetupo3.sh
/opt/OV/bin/ovdbsetupo2.sh
/opt/OV/bin/ovdbtrend_dsko.sh
/opt/OV/bin/request_create
/opt/OV/bin/request_delete
/opt/OV/bin/request_list
/opt/OV/bin/request_status
/opt/OV/bin/ovrequestd
/opt/OV/bin/ovcwd
/opt/OV/bin/ovreppublish
/opt/OV/bin/xnmsnmpconf
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/
webbrowser
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/jovw
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/
snmpviewer
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/terminal
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/
mibbrowser
/opt/OV/newconfig/OVWWW-FW/www/registration/launcher/C/jovw
/opt/OV/newconfig/OVWWW-FW/www/registration/launcher/C/
snmpviewer
/opt/OV/newconfig/OVWWW-FW/www/registration/launcher/C/
mibbrowser
/opt/OV/newconfig/OVWWW-FW/www/etc/htpasswd
/opt/OV/newconfig/OVMIN/conf/ovbackup/checkpoint/
operational/nnm_checkpoint.ovpl
/opt/OV/newconfig/OVMIN/conf/ovbackup/restore/operational/
nnm_restore.ovpl
/opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/PairWise.ds
/opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/RepeatedEvent.ds
/opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/C/
RepeatedEvent.param
/opt/OV/newconfig/OVNNM-RUN/fields/C/snmp_fields
/opt/OV/newconfig/OVNNM-RUN/conf/mibExpr.conf
/opt/OV/newconfig/OVNNM-RUN/conf/mibExprGuru.conf
/opt/OV/newconfig/OVNNM-RUN/conf/ov.conf
/opt/OV/newconfig/OVNNM-RUN/registration/C/terminal
/opt/OV/newconfig/OVNNM-RUN/nnm.sdl
/opt/OV/newconfig/OVNNM-RUN/nnmswitch.sdl
/opt/OV/newconfig/OVWIN/bitmaps.tar.Z
/opt/OV/newconfig/OVWWW-EVNT/lrf/ovalarmsrv.lrf
/opt/OV/newconfig/OVWWW-EVNT/www/registration/jovw/C/alarmbr
/opt/OV/newconfig/OVWWW-EVNT/www/registration/launcher/C/
ecscmg
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/webbrowser
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/jovw
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/snmpviewer
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/alarmbr
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/terminal
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/mibbrowser
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/webbrowser
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/jovw
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/snmpviewer
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/alarmbr
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/terminal
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/mibbrowser
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/jovw
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/snmpviewer
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/ecscmg
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/mibbrowser
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/jovw
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/snmpviewer
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/ecscmg
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/mibbrowser
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.SJIS/
terminal
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.SJIS/ipmap
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.eucJP/
terminal
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.eucJP/ipmap
/opt/OV/newconfig/OVNNMGR-JPN/ecsCircuits/ja_JP.SJIS/
RepeatedEvent.param
/opt/OV/newconfig/OVNNMGR-JPN/ecsCircuits/ja_JP.eucJP/
RepeatedEvent.param
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.SJIS/NNM/nnm.sdl
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.SJIS/
SwitchTopology/nnmswitch.sdl
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.eucJP/NNM/nnm.sdl
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.eucJP/
SwitchTopology/nnmswitch.sdl
/opt/OV/man/man4.Z/oid_to_type.4
/opt/OV/man/man4.Z/mibExpr.conf.4
/opt/OV/man/man4.Z/netmon.snmpStatus.4
/opt/OV/man/man4.Z/netmon.statusMapping.4
/opt/OV/man/man4.Z/netmon.cmstr.4
/opt/OV/man/man4.Z/ov.conf.4
/opt/OV/man/man4.Z/ovsnmp.conf.4
/opt/OV/man/man1m.Z/xnmtopoconf.1m
/opt/OV/man/man1m.Z/netmon.1m
/opt/OV/man/man1m.Z/ovtopofix.1m
/opt/OV/man/man1m.Z/snmpCollect.1m
/opt/OV/man/man1m.Z/switchdiscovery.1m
/opt/OV/man/man1m.Z/loadhosts.1m
/opt/OV/man/man1m.Z/ovdbcheck.1m
/opt/OV/man/man1m.Z/ovactiond.1m
/opt/OV/man/man1m.Z/ovalarmsrv.1m
/opt/OV/man/man1m.Z/ovalarmadm.1m
/opt/OV/man/man1.Z/ovdwevent.1
/opt/OV/man/man1.Z/ovdwtrend.1
/opt/OV/man/man1.Z/ovcolsum.1
/opt/OV/man/man1.Z/ovdweventflt.1
/opt/OV/man/man1.Z/ovcoldelsql.1
/opt/OV/man/man1.Z/switchmap.1
/opt/OV/man/man1.Z/xnmsnmpconf.1
/opt/OV/man/man1.Z/ovw.1
/opt/OV/man/man3.Z/OVsnmpConfPrintCntl.3
/opt/OV/man/man3.Z/OVsnmpConfPrintDest.3
/opt/OV/man/man3.Z/OVsnmpConfPrintEntry.3
/opt/OV/man/man3.Z/OVwGetLocations.3
/opt/OV/man/man3.Z/OVwGetLocationsByAttribute.3
/opt/OV/man/man3.Z/OVwGetLocationsByComment.3
/opt/OV/man/man3.Z/OVwGetLocationsBySelectionName.3
/opt/OV/man/man3.Z/OVwGetLocationsBySymbolLabel.3
/opt/OV/man/man3.Z/OVwGetLocationsBySymbolStatus.3
/opt/OV/man/man3.Z/OVwGetLocationsBySymbolType.3
/opt/OV/man/man3.Z/OVwFreeLocationList.3
/opt/OV/man/man3.Z/OVwDisplaySubmap.3
/opt/OV/man/man3.Z/OVwCloseSubmap.3
/opt/OV/include/OV/ovw.h
/opt/OV/contrib/NNM/baseliner/mibExpr.conf
/opt/OV/contrib/NNM/ovalarm/ovalarm.ovpl
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
J1240-90014.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
J1240-90014.edr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
J1240-90014.tag
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
equation.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
example.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
figure.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
proced.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
table.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
toc.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/figures/
gfx1.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/figures/
gfx2.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/index/
index.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/index/
vocab.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/
J1240-90014.qrs
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/
hytime.cat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/
styles.ent
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx1.cgm
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx2.cgm
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx3.cgm
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx4.cgm
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx5.tif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
J1240-90005.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
J1240-90005.edr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
J1240-90005.tag
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
equation.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
example.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
figure.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
proced.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
table.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
toc.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/index/
index.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/index/
vocab.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/
J1240-90005.qrs
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/
hytime.cat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/
styles.ent
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
graphics/wizard.tif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
graphics/invrept.tif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx1.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx10.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx11.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx12.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx2.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx3.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx4.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx5.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx6.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx7.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx8.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx9.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
J1240-90015.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
table.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
example.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
toc.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
proced.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
equation.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
figure.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
J1240-90015.tag
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
J1240-90015.edr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/index/
vocab.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/index/
index.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/
styles.ent
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/
hytime.cat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/
J1240-90015.qrs
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
table.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
example.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
toc.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
proced.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
equation.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
figure.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
J1240-90048.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
J1240-90048.edr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
J1240-90048.tag
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/index/
vocab.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/index/
index.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/
styles.ent
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/
J1240-90048.qrs
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/
J1240-90033.qrs
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
J1240-90033.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
J1240-90033.edr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
J1240-90033.tag
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
equation.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
example.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
figure.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
proced.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
table.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
toc.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx1.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx10.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx11.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx12.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx13.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx2.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx3.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx4.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx5.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx6.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx7.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx8.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx9.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/ST_status.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/ad_status.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/adjacent.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/connect_status.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/cp.tif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/multi_connect.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/multi_device.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/nlabel.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/node.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/root.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/showinterface.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/stalarms.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/switchpol.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/switchport.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/switchto.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/webst.gif
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/
hytime.cat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/index/
index.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/index/
vocab.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/
styles.ent
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/
J1240-90026.qrs
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
J1240-90026.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
J1240-90026.edr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
J1240-90026.tag
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
equation.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
example.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
figure.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
proced.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
table.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
toc.tdr
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/index/
index.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/index/
vocab.dat
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/
styles.ent
/opt/OV/doc/dynatext/NNMWelEngDoc/ents/map.txt
/opt/OV/doc/dynatext/NNMWelEngDoc/booklist.txt
/opt/OV/opi/opi_proc/opiproc
/etc/opt/OV/share/conf/ovbackup/restore/analytical/
nnm_restore.ovpl
/etc/opt/OV/share/conf/stacks/pmd/libovEvent.sl
/etc/opt/OV/share/conf/ecs/circuits/ScheduledMaintenance.eco
/etc/opt/OV/share/conf/ecs/circuits/PairWise.eco
/etc/opt/OV/share/conf/ecs/circuits/C/PairWise.param
/etc/opt/OV/share/conf/ecs/circuits/C/
RepeatedEvent_param.mod
/etc/opt/OV/share/conf/ecs/circuits/C/PairWise_param.mod
/etc/opt/OV/share/conf/ecs/circuits/PairWise_update.pl
/etc/opt/OV/share/conf/ecs/circuits/RepeatedEvent.eco
/etc/opt/OV/share/conf/ecs/circuits/RepeatedEvent_update.pl
/etc/opt/OV/share/conf/ecs/circuits/RepeatedEvent_ds.mod
/etc/opt/OV/share/conf/ecs/circuits/PairWise_ds.mod
/etc/opt/OV/share/conf/ecs/circuits/ConnectorDown.eco
/etc/opt/OV/share/conf/ecs/circuits/ja_JP.SJIS/
PairWise.param
/etc/opt/OV/share/conf/ecs/circuits/ja_JP.eucJP/
PairWise.param
/etc/opt/OV/share/conf/analysis/sqlScripts/
export_minimal.sql
/etc/opt/OV/share/conf/analysis/excelTemplates/NNM/
README_excelTemplates.txt
/etc/opt/OV/share/www/conf/NNM.spec
/etc/opt/OV/share/backgrounds/china1.gif
/var/opt/OV/share/help/C/NNM/nnm.sdl
/var/opt/OV/share/help/C/SwitchTopology/nnmswitch.sdl
/var/opt/OV/share/help/ja_JP.SJIS/NNM/nnm.sdl
/var/opt/OV/share/help/ja_JP.SJIS/SwitchTopology/
nnmswitch.sdl
/var/opt/OV/share/help/ja_JP.eucJP/NNM/nnm.sdl
/var/opt/OV/share/help/ja_JP.eucJP/SwitchTopology/
nnmswitch.sdl
what(1) Output:
/opt/OV/www/cgi-bin/ovlaunchreg.exe:
ovlaunchreg.exe
/opt/OV/www/cgi-bin/Main/Snmp:
None
/opt/OV/www/cgi-bin/webappmon.exe:
None
/opt/OV/www/cgi-bin/ovlaunch.exe:
None
/opt/OV/www/cgi-bin/ovlogin.exe:
None
/opt/OV/www/cgi-bin/OpenView5.exe:
None
/opt/OV/www/cgi-bin/jovwreg.exe:
None
/opt/OV/www/cgi-bin/snmpviewer.exe:
None
/opt/OV/www/cgi-bin/ovalarm.exe:
None
/opt/OV/www/htdocs/classes/jovw/debug.jovw.jar:
None
/opt/OV/www/htdocs/classes/jovw/jovw.jar:
None
/opt/OV/www/htdocs/classes/launcher/debug.ovlaunch.jar:
None
/opt/OV/www/htdocs/classes/launcher/ovlaunch.jar:
None
/opt/OV/www/htdocs/classes/jalarm/debug.jalarm.jar:
None
/opt/OV/www/htdocs/classes/jalarm/jalarm.jar:
None
/opt/OV/www/htdocs/classes/libovw.jar:
None
/opt/OV/www/htdocs/classes/debug.libovw.jar:
None
/opt/OV/www/htdocs/classes/nnmReporting/
debug.nnmReporting.jar:
None
/opt/OV/www/htdocs/classes/nnmReporting/nnmReporting.jar:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/cnttsk.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/nnmswitchref.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/nnmswitchtsk.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/cntref.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/rptref.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/rpttsk.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/cxtglos.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/cxtoth.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/cxtref.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Scope/scpref.htm:
None
/opt/OV/www/htdocs/C/OvWebHelp/nnm/Scope/scptsk.htm:
None
/opt/OV/www/htdocs/C/launcher/login.tmpl:
None
/opt/OV/www/htdocs/C/launcher/retry.tmpl:
None
/opt/OV/www/htdocs/C/launcher/launcher.tmpl:
None
/opt/OV/www/htdocs/C/launcher/jscript.html:
None
/opt/OV/www/htdocs/C/launcher/browser.html:
None
/opt/OV/www/htdocs/C/launcher/welcome.html:
None
/opt/OV/www/htdocs/C/launcher/webwin.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/html/intro.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/html/ovlogo_l.gif:
None
/opt/OV/www/htdocs/C/launcher/javadoc/html/start.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/sample/
TestSession.java:
None
/opt/OV/www/htdocs/C/launcher/javadoc/doc/AllNames.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/doc/
Package-hp.ov.session.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/doc/
hp.ov.session.NoSessionException.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/doc/
hp.ov.session.Session.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/doc/packages.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/doc/tree.html:
None
/opt/OV/www/htdocs/C/launcher/javadoc/index.html:
None
/opt/OV/www/htdocs/C/launcher/welcomecontent.html:
None
/opt/OV/www/htdocs/C/launcher/welcometopics.html:
None
/opt/OV/www/htdocs/C/launcher/js_replace.tmpl:
None
/opt/OV/www/htdocs/C/launcher/js_replace_br.tmpl:
None
/opt/OV/www/htdocs/C/nnm/snmpviewer/tree.tmpl:
None
/opt/OV/www/htdocs/C/ReleaseNotes/ReadmeAll_NNMGR.html:
HP OpenView NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/www/htdocs/C/ReleaseNotes/ReadmeNew_NNMGR.html:
None
/opt/OV/www/htdocs/C/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html:
None
/opt/OV/www/htdocs/C/ReleaseNotes/ReadmeInstall_NNMGR.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/AllNames.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/
Package-hp.ov.libovw.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.LibOvw.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.OVwLocateResultSymbol.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwMapInfo.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/tree.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwLocationInfo.html:
None
/opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwLocationList.html:
None
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.16.gif:
None
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.20.gif:
None
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.26.gif:
None
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.32.gif:
None
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.38.gif:
None
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.44.gif:
None
/opt/OV/www/htdocs/bitmaps/C/cards/mux_c.50.gif:
None
/opt/OV/www/htdocs/bitmaps/C/misc/binoc.16.gif:
None
/opt/OV/www/htdocs/bitmaps/C/misc/binoc.20.gif:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
cnttsk.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
rptref.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
nnmswitchref.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
nnmswitchtsk.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
rpttsk.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Content/
cntref.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Context/
cxtglos.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Context/
cxtoth.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Context/
cxtref.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Scope/
scpref.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/Scope/
scptsk.htm:
None
/opt/OV/www/htdocs/ja_JP.SJIS/launcher/login.tmpl:
None
/opt/OV/www/htdocs/ja_JP.SJIS/launcher/retry.tmpl:
None
/opt/OV/www/htdocs/ja_JP.SJIS/launcher/welcometopics.html:
None
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeAll_NNMGR.html:
HP OpenView NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeNew_NNMGR.html:
None
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html:
None
/opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeInstall_NNMGR.html:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
cnttsk.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
rptref.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
nnmswitchref.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
nnmswitchtsk.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
rpttsk.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Content/
cntref.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Context/
cxtglos.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Context/
cxtoth.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Context/
cxtref.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Scope/
scpref.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/Scope/
scptsk.htm:
None
/opt/OV/www/htdocs/ja_JP.eucJP/launcher/login.tmpl:
None
/opt/OV/www/htdocs/ja_JP.eucJP/launcher/retry.tmpl:
None
/opt/OV/www/htdocs/ja_JP.eucJP/launcher/welcometopics.html:
None
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeAll_NNMGR.html:
HP OpenView NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeNew_NNMGR.html:
None
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html:
None
/opt/OV/www/htdocs/ja_JP.eucJP/ReleaseNotes/
ReadmeInstall_NNMGR.html:
None
/opt/OV/www/bin/htpasswd:
None
/opt/OV/lib/libovwww.2:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovwparser.2:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovsnmp.2:
libovsnmp
rnetstat
HP OpenView SNMP Dev Kit NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libov.2:
HP OpenView ov library NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovutil.2:
HP OpenView ov utility library (HP Internal only) NN
M Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovgui.2:
HP OpenView ov gui library (HP Internal only) NNM Re
lease B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
Debug Widget Code
/opt/OV/lib/libovextfmt.2:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libevent.2:
HP OpenView Event Store Access Library (HP Internal
only) NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovtopm.2:
libovtopm.sl
HP OpenView Topology NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovfilter.2:
libovfilter
HP OpenView Filter library (HP Internal only) NNM Re
lease B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/libovw.2:
HP OpenView Windows NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/lib/nls/ja_JP.SJIS/xnmsnmpconf.cat:
None
/opt/OV/lib/nls/ja_JP.SJIS/events.cat:
None
/opt/OV/lib/nls/ja_JP.SJIS/util_libs.cat:
None
/opt/OV/lib/nls/ja_JP.eucJP/xnmsnmpconf.cat:
None
/opt/OV/lib/nls/ja_JP.eucJP/events.cat:
None
/opt/OV/lib/nls/ja_JP.eucJP/util_libs.cat:
None
/opt/OV/bin/ovsessionmgr:
ovsessionmgr
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/regverify:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovstart:
ovstart/ovstop/ovstatus
HP OpenView ICVT NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovstop:
ovstart/ovstop/ovstatus
HP OpenView ICVT NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovstatus:
ovstart/ovstop/ovstatus
HP OpenView ICVT NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovspmd:
ovspmd
HP OpenView ICVT NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmevents:
xnmevents
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovactiond:
ovactiond
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovtrapd:
ovtrapd
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/netmon:
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
netmon
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
annoio.c $Revision: 1.45 $ $Date: 1998/04/01 06:27:2
6 $
None
sockstack.c $Revision: 1.68 $ $Date: 1998/06/09 01:1
6:51 $
value.c $Revision$ $Date$
ECS.c $Revision: 1.9 $ $Date: 1998/04/22 23:30:06 $
ECS 3.0 (STABLE_3_x_980808)
ECS REV: 980808.1708(opt) HP-UX B.10.10 Server A.05.
03
trace.c $Revision: 1.12 $ $Date: 1998/03/12 04:48:38
$
None
fatal.c $Revision: 1.13 $ $Date: 1998/05/07 02:26:33
$
None
log.c $Revision: 1.7 $ $Date: 1997/07/04 07:34:11 $
None
mesgbuf.c $Revision: 1.18 $ $Date: 1998/05/07 00:28:
35 $
None
sequence.c $Revision: 1.17 $ $Date: 1998/01/28 03:39
:17 $
vstring.c $Revision$ $Date$
/opt/OV/bin/ovrepld:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovrepld
/opt/OV/bin/loadhosts:
loadhosts
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/snmpCollect:
snmpCollect
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmcollect:
xnmcollect
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmtopoconf:
xnmtopoconf
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmgraph:
xnmgraph
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ipmap:
ipmap
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovtopodump:
ovtopodump
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovtopofix:
ovtopofix
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovtopmd:
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
ovtopmd
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
Copyright 1992-1997 SNMP Research, Incorporated
SNMP Research Distribution version 14.2.1.7
/opt/OV/bin/xnmbuilder:
xnmbuilder
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/Perl/lib/ovbackup.pm:
None
/opt/OV/bin/ovexprguru:
ovexprguru
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmbrowser:
xnmbrowser
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmpolling:
xnmpolling
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovweb:
ovweb
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/findroute:
findroute
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmappmon:
xnmappmon
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/rnetstat:
rnetstat
if-mib
fr-mib
ds1-mib
ds3-mib
sonet-mib
if-mib
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/netcheck:
netcheck
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovhelp:
ovhelp
HP OpenView Windows NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovw:
HP OpenView Windows NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
HP IL EFS v 2.1 bl03; Image EFS Library for HP-UX 8
.07+ & MPower 'libilefs.sl'
ovw
/opt/OV/bin/ovwdb:
ovwdb
HP OpenView Windows NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovuispmd:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovalarmsrv:
ovalarmsrv
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovalarmadm:
ovalarmadm
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovdbcheck:
ovDbCheckOdbc
HP OpenView DataBase Tools NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovdwtrend:
ovdwtrend
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovcolsum:
ovcolsum
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovcoltosql:
ovcoltosql/ovcolsql/ovcoldelsql
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovcoldelsql:
ovcoldelsql
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovdwevent:
oveventexp
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovdweventflt:
ovEventFlt
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovdwtopo:
ovdwtopo
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovdwquery:
ovdwquery
HP OpenView DataBase Tools NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovcolqsql:
ovcolqsql
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
ovDwCommon
/opt/OV/bin/ovdbsetupo1.sh:
ovdbsetupo1.sh
HP OpenView DBtools: NNM NNM Release B.06.10 Aug 2
8 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/bin/ovdbsetupo3.sh:
ovdbsetupo3.sh
HP OpenView DBtools: NNM NNM Release B.06.10 Aug 2
8 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
$Revision: /main/PULSAR/PULSAR_REP/11 $
/opt/OV/bin/ovdbsetupo2.sh:
ovdbsetup2o.sh
HP OpenView DBtools: NNM NNM Release B.06.10 Aug 2
8 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
$Revision: /main/PULSAR/HALLEY/PULSAR_REP/1 $
/opt/OV/bin/ovdbtrend_dsko.sh:
ovdbtrend_dsko.sh
HP OpenView NNM NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/bin/request_create:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/request_delete:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/request_list:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/request_status:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovrequestd:
ovrequestd
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovcwd:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/ovreppublish:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/opt/OV/bin/xnmsnmpconf:
HP OpenView Network Node Manager NNM Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
xnmsnmpconf
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/
webbrowser:
HP OpenView Network Node Manager Web Browser Launche
r
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/jovw:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/
snmpviewer:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/terminal:
None
/opt/OV/newconfig/OVWWW-FW/www/registration/jovw/C/
mibbrowser:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-FW/www/registration/launcher/C/jovw:
None
/opt/OV/newconfig/OVWWW-FW/www/registration/launcher/C/
snmpviewer:
None
/opt/OV/newconfig/OVWWW-FW/www/registration/launcher/C/
mibbrowser:
None
/opt/OV/newconfig/OVWWW-FW/www/etc/htpasswd:
None
/opt/OV/newconfig/OVMIN/conf/ovbackup/checkpoint/
operational/nnm_checkpoint.ovpl:
None
/opt/OV/newconfig/OVMIN/conf/ovbackup/restore/operational/
nnm_restore.ovpl:
None
/opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/PairWise.ds:
None
/opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/RepeatedEvent.ds:
None
/opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/C/
RepeatedEvent.param:
None
/opt/OV/newconfig/OVNNM-RUN/fields/C/snmp_fields:
HP OpenView NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/newconfig/OVNNM-RUN/conf/mibExpr.conf:
mibExpr.conf
HP OpenView NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/newconfig/OVNNM-RUN/conf/mibExprGuru.conf:
mibExpr.conf
HP OpenView NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/newconfig/OVNNM-RUN/conf/ov.conf:
None
/opt/OV/newconfig/OVNNM-RUN/registration/C/terminal:
None
/opt/OV/newconfig/OVNNM-RUN/nnm.sdl:
None
/opt/OV/newconfig/OVNNM-RUN/nnmswitch.sdl:
None
/opt/OV/newconfig/OVWIN/bitmaps.tar.Z:
None
/opt/OV/newconfig/OVWWW-EVNT/lrf/ovalarmsrv.lrf:
None
/opt/OV/newconfig/OVWWW-EVNT/www/registration/jovw/C/
alarmbr:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-EVNT/www/registration/launcher/C/
ecscmg:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/webbrowser:
HP OpenView Network Node Manager Web Browser Launche
r
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/jovw:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/snmpviewer:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/alarmbr:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/terminal:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.SJIS/mibbrowser:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/webbrowser:
HP OpenView Network Node Manager Web Browser Launche
r
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/jovw:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/snmpviewer:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/alarmbr:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/terminal:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/jovw/
ja_JP.eucJP/mibbrowser:
HP OpenView Windows Menu Registration
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/jovw:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/snmpviewer:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/ecscmg:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.SJIS/mibbrowser:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/jovw:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/snmpviewer:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/ecscmg:
None
/opt/OV/newconfig/OVWWW-JPN/www/registration/launcher/
ja_JP.eucJP/mibbrowser:
None
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.SJIS/
terminal:
None
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.SJIS/ipmap:
None
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.eucJP/
terminal:
None
/opt/OV/newconfig/OVNNMGR-JPN/registration/ja_JP.eucJP/
ipmap:
None
/opt/OV/newconfig/OVNNMGR-JPN/ecsCircuits/ja_JP.SJIS/
RepeatedEvent.param:
None
/opt/OV/newconfig/OVNNMGR-JPN/ecsCircuits/ja_JP.eucJP/
RepeatedEvent.param:
None
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.SJIS/NNM/nnm.sdl:
None
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.SJIS/
SwitchTopology/nnmswitch.sdl:
None
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.eucJP/NNM/nnm.sdl:
None
/opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.eucJP/
SwitchTopology/nnmswitch.sdl:
None
/opt/OV/man/man4.Z/oid_to_type.4:
None
/opt/OV/man/man4.Z/mibExpr.conf.4:
None
/opt/OV/man/man4.Z/netmon.snmpStatus.4:
None
/opt/OV/man/man4.Z/netmon.statusMapping.4:
None
/opt/OV/man/man4.Z/netmon.cmstr.4:
None
/opt/OV/man/man4.Z/ov.conf.4:
None
/opt/OV/man/man4.Z/ovsnmp.conf.4:
None
/opt/OV/man/man1m.Z/xnmtopoconf.1m:
None
/opt/OV/man/man1m.Z/netmon.1m:
None
/opt/OV/man/man1m.Z/ovtopofix.1m:
None
/opt/OV/man/man1m.Z/snmpCollect.1m:
None
/opt/OV/man/man1m.Z/switchdiscovery.1m:
None
/opt/OV/man/man1m.Z/loadhosts.1m:
None
/opt/OV/man/man1m.Z/ovdbcheck.1m:
None
/opt/OV/man/man1m.Z/ovactiond.1m:
None
/opt/OV/man/man1m.Z/ovalarmsrv.1m:
None
/opt/OV/man/man1m.Z/ovalarmadm.1m:
None
/opt/OV/man/man1.Z/ovdwevent.1:
None
/opt/OV/man/man1.Z/ovdwtrend.1:
None
/opt/OV/man/man1.Z/ovcolsum.1:
None
/opt/OV/man/man1.Z/ovdweventflt.1:
None
/opt/OV/man/man1.Z/ovcoldelsql.1:
None
/opt/OV/man/man1.Z/switchmap.1:
None
/opt/OV/man/man1.Z/xnmsnmpconf.1:
None
/opt/OV/man/man1.Z/ovw.1:
None
/opt/OV/man/man3.Z/OVsnmpConfPrintCntl.3:
None
/opt/OV/man/man3.Z/OVsnmpConfPrintDest.3:
None
/opt/OV/man/man3.Z/OVsnmpConfPrintEntry.3:
None
/opt/OV/man/man3.Z/OVwGetLocations.3:
None
/opt/OV/man/man3.Z/OVwGetLocationsByAttribute.3:
None
/opt/OV/man/man3.Z/OVwGetLocationsByComment.3:
None
/opt/OV/man/man3.Z/OVwGetLocationsBySelectionName.3:
None
/opt/OV/man/man3.Z/OVwGetLocationsBySymbolLabel.3:
None
/opt/OV/man/man3.Z/OVwGetLocationsBySymbolStatus.3:
None
/opt/OV/man/man3.Z/OVwGetLocationsBySymbolType.3:
None
/opt/OV/man/man3.Z/OVwFreeLocationList.3:
None
/opt/OV/man/man3.Z/OVwDisplaySubmap.3:
None
/opt/OV/man/man3.Z/OVwCloseSubmap.3:
None
/opt/OV/include/OV/ovw.h:
Copyright (c) 1990-2001 Hewlett-Packard Company
ovw.h HP OpenView SNMP library NNM Release B.06.10
Aug 28 2001
/opt/OV/contrib/NNM/baseliner/mibExpr.conf:
None
/opt/OV/contrib/NNM/ovalarm/ovalarm.ovpl:
ovalarm
HP OpenView NNM Release B.06.10 Aug 28 2001
Copyright (c) 1990-2001 Hewlett-Packard Company
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
J1240-90014.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
J1240-90014.edr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
J1240-90014.tag:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
equation.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
example.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
figure.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
proced.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
table.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/ebt/
toc.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/figures/
gfx1.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/figures/
gfx2.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/index/
index.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/index/
vocab.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/
J1240-90014.qrs:
None
guide.qrs 1.2 /fs/david/rtmp/llf/temp/s.guide.qrs
94/09/21 1.2 17:16:42 --
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/
hytime.cat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90014/
styles.ent:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx1.cgm:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx2.cgm:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx3.cgm:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx4.cgm:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/figures/
gfx5.tif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
J1240-90005.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
J1240-90005.edr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
J1240-90005.tag:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
equation.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
example.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
figure.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
proced.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
table.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/ebt/
toc.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/index/
index.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/index/
vocab.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/
J1240-90005.qrs:
None
guide.qrs 1.2 /fs/david/rtmp/llf/temp/s.guide.qrs
94/09/21 1.2 17:16:42 --
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/
hytime.cat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90005/
styles.ent:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
graphics/wizard.tif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
graphics/invrept.tif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx1.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx10.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx11.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx12.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx2.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx3.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx4.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx5.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx6.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx7.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx8.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/figures/
gfx9.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
J1240-90015.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
table.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
example.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
toc.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
proced.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
equation.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
figure.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
J1240-90015.tag:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/ebt/
J1240-90015.edr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/index/
vocab.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/index/
index.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/
styles.ent:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/
hytime.cat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90015/
J1240-90015.qrs:
None
guide.qrs 1.2 /fs/david/rtmp/llf/temp/s.guide.qrs
94/09/21 1.2 17:16:42 --
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
table.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
example.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
toc.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
proced.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
equation.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
figure.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
J1240-90048.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
J1240-90048.edr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/ebt/
J1240-90048.tag:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/index/
vocab.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/index/
index.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/
styles.ent:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90048/
J1240-90048.qrs:
None
guide.qrs 1.2 /fs/david/rtmp/llf/temp/s.guide.qrs
94/09/21 1.2 17:16:42 --
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/
J1240-90033.qrs:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
J1240-90033.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
J1240-90033.edr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
J1240-90033.tag:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
equation.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
example.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
figure.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
proced.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
table.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/ebt/
toc.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx1.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx10.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx11.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx12.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx13.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx2.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx3.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx4.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx5.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx6.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx7.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx8.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
gfx9.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/ST_status.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/ad_status.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/adjacent.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/connect_status.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/cp.tif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/multi_connect.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/multi_device.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/nlabel.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/node.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/root.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/showinterface.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/stalarms.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/switchpol.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/switchport.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/switchto.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/figures/
graphics/webst.gif:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/
hytime.cat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/index/
index.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/index/
vocab.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90033/
styles.ent:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/
J1240-90026.qrs:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
J1240-90026.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
J1240-90026.edr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
J1240-90026.tag:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
equation.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
example.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
figure.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
proced.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
table.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/ebt/
toc.tdr:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/index/
index.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/index/
vocab.dat:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/books/J1240-90026/
styles.ent:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/ents/map.txt:
None
/opt/OV/doc/dynatext/NNMWelEngDoc/booklist.txt:
None
/opt/OV/opi/opi_proc/opiproc:
HP OpenView OPI Process TMN Pre-Release A.05.03 (Pre
-Alpha)
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-1999 Hewlett-Packard Co., All Ri
ghts Reserved.
DM1042: pm_main.c 25Feb1999
FLEXlm 6.0d (liblmgr.a), Copyright (C) 1988-1997 Glo
betrotter Software, Inc.
/etc/opt/OV/share/conf/ovbackup/restore/analytical/
nnm_restore.ovpl:
None
/etc/opt/OV/share/conf/stacks/pmd/libovEvent.sl:
OV_EVENT OPI Stack
HP OpenView OPI Stack OV_EVENT (HP Internal only) NN
M Release B.06.10
PATCH PHSS_24797, 08282001
HP 9000 S700/S800 HP-UX 10.x
Copyright (c) 1990-2001 Hewlett-Packard Co., All Ri
ghts Reserved.
/etc/opt/OV/share/conf/ecs/circuits/
ScheduledMaintenance.eco:
None
/etc/opt/OV/share/conf/ecs/circuits/PairWise.eco:
None
/etc/opt/OV/share/conf/ecs/circuits/C/PairWise.param:
None
/etc/opt/OV/share/conf/ecs/circuits/C/
RepeatedEvent_param.mod:
None
/etc/opt/OV/share/conf/ecs/circuits/C/PairWise_param.mod:
None
/etc/opt/OV/share/conf/ecs/circuits/PairWise_update.pl:
None
/etc/opt/OV/share/conf/ecs/circuits/RepeatedEvent.eco:
None
/etc/opt/OV/share/conf/ecs/circuits/RepeatedEvent_update.pl:
None
/etc/opt/OV/share/conf/ecs/circuits/RepeatedEvent_ds.mod:
None
/etc/opt/OV/share/conf/ecs/circuits/PairWise_ds.mod:
None
/etc/opt/OV/share/conf/ecs/circuits/ConnectorDown.eco:
None
/etc/opt/OV/share/conf/ecs/circuits/ja_JP.SJIS/
PairWise.param:
None
/etc/opt/OV/share/conf/ecs/circuits/ja_JP.eucJP/
PairWise.param:
None
/etc/opt/OV/share/conf/analysis/sqlScripts/
export_minimal.sql:
None
/etc/opt/OV/share/conf/analysis/excelTemplates/NNM/
README_excelTemplates.txt:
None
/etc/opt/OV/share/www/conf/NNM.spec:
HP OpenView NNM Event Browser Specification
/etc/opt/OV/share/backgrounds/china1.gif:
None
/var/opt/OV/share/help/C/NNM/nnm.sdl:
None
/var/opt/OV/share/help/C/SwitchTopology/nnmswitch.sdl:
None
/var/opt/OV/share/help/ja_JP.SJIS/NNM/nnm.sdl:
None
/var/opt/OV/share/help/ja_JP.SJIS/SwitchTopology/
nnmswitch.sdl:
None
/var/opt/OV/share/help/ja_JP.eucJP/NNM/nnm.sdl:
None
/var/opt/OV/share/help/ja_JP.eucJP/SwitchTopology/
nnmswitch.sdl:
None
cksum(1) Output:
3191209623 36980 /opt/OV/www/cgi-bin/ovlaunchreg.exe
1726318976 36944 /opt/OV/www/cgi-bin/Main/Snmp
2404779433 86372 /opt/OV/www/cgi-bin/webappmon.exe
1735935210 49261 /opt/OV/www/cgi-bin/ovlaunch.exe
2203515928 36945 /opt/OV/www/cgi-bin/ovlogin.exe
1313653668 32824 /opt/OV/www/cgi-bin/OpenView5.exe
496185521 36971 /opt/OV/www/cgi-bin/jovwreg.exe
3048897349 57573 /opt/OV/www/cgi-bin/snmpviewer.exe
3258593950 36951 /opt/OV/www/cgi-bin/ovalarm.exe
1210322302 768205 /opt/OV/www/htdocs/classes/jovw/
debug.jovw.jar
2975750808 387843 /opt/OV/www/htdocs/classes/jovw/jovw.jar
130641318 183841 /opt/OV/www/htdocs/classes/launcher/
debug.ovlaunch.jar
1890096841 100723 /opt/OV/www/htdocs/classes/launcher/
ovlaunch.jar
2918746763 1474544 /opt/OV/www/htdocs/classes/jalarm/
debug.jalarm.jar
3747332254 443028 /opt/OV/www/htdocs/classes/jalarm/
jalarm.jar
1147445360 68295 /opt/OV/www/htdocs/classes/libovw.jar
3356468270 97648 /opt/OV/www/htdocs/classes/debug.libovw.jar
3247011342 232529 /opt/OV/www/htdocs/classes/nnmReporting/
debug.nnmReporting.jar
1077428974 141885 /opt/OV/www/htdocs/classes/nnmReporting/
nnmReporting.jar
373549120 74925 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/
cnttsk.htm
4294967295 0 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/
nnmswitchref.htm
4294967295 0 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/
nnmswitchtsk.htm
4282643422 103951 /opt/OV/www/htdocs/C/OvWebHelp/nnm/
Content/cntref.htm
1456593577 32747 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/
rptref.htm
2516927940 18600 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Content/
rpttsk.htm
2789006433 1966 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/
cxtglos.htm
505383375 1923 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/
cxtoth.htm
3373254043 1926 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Context/
cxtref.htm
3380139535 1386 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Scope/
scpref.htm
318480530 7329 /opt/OV/www/htdocs/C/OvWebHelp/nnm/Scope/
scptsk.htm
3878534488 2107 /opt/OV/www/htdocs/C/launcher/login.tmpl
1975537296 2186 /opt/OV/www/htdocs/C/launcher/retry.tmpl
895135206 494 /opt/OV/www/htdocs/C/launcher/launcher.tmpl
2647619607 159 /opt/OV/www/htdocs/C/launcher/jscript.html
131784169 954 /opt/OV/www/htdocs/C/launcher/browser.html
2512083219 325 /opt/OV/www/htdocs/C/launcher/welcome.html
4176933757 985 /opt/OV/www/htdocs/C/launcher/webwin.html
2485352827 790 /opt/OV/www/htdocs/C/launcher/javadoc/html/
intro.html
1300363032 3750 /opt/OV/www/htdocs/C/launcher/javadoc/html/
ovlogo_l.gif
2121604598 1137 /opt/OV/www/htdocs/C/launcher/javadoc/html/
start.html
1556873455 1837 /opt/OV/www/htdocs/C/launcher/javadoc/
sample/TestSession.java
3867048521 5355 /opt/OV/www/htdocs/C/launcher/javadoc/doc/
AllNames.html
4019653418 792 /opt/OV/www/htdocs/C/launcher/javadoc/doc/
Package-hp.ov.session.html
2186119121 2478 /opt/OV/www/htdocs/C/launcher/javadoc/doc/
hp.ov.session.NoSessionException.html
1416114733 10676 /opt/OV/www/htdocs/C/launcher/javadoc/doc/
hp.ov.session.Session.html
4271993430 583 /opt/OV/www/htdocs/C/launcher/javadoc/doc/
packages.html
1097055172 746 /opt/OV/www/htdocs/C/launcher/javadoc/doc/
tree.html
3822024475 173 /opt/OV/www/htdocs/C/launcher/javadoc/
index.html
4186746783 1123 /opt/OV/www/htdocs/C/launcher/
welcomecontent.html
2075023081 1436 /opt/OV/www/htdocs/C/launcher/
welcometopics.html
2086269311 333 /opt/OV/www/htdocs/C/launcher/js_replace.tmpl
2977763346 404 /opt/OV/www/htdocs/C/launcher/
js_replace_br.tmpl
3433203989 622 /opt/OV/www/htdocs/C/nnm/snmpviewer/tree.tmpl
2930786216 179372 /opt/OV/www/htdocs/C/ReleaseNotes/
ReadmeAll_NNMGR.html
322491848 19147 /opt/OV/www/htdocs/C/ReleaseNotes/
ReadmeNew_NNMGR.html
3011468269 59101 /opt/OV/www/htdocs/C/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html
1088772702 27220 /opt/OV/www/htdocs/C/ReleaseNotes/
ReadmeInstall_NNMGR.html
3195083582 195893 /opt/OV/www/htdocs/C/java_libovw/doc/
AllNames.html
1644278485 5056 /opt/OV/www/htdocs/C/java_libovw/doc/
Package-hp.ov.libovw.html
1247540795 162596 /opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.LibOvw.html
1076029548 2685 /opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.OVwLocateResultSymbol.html
1508116291 3731 /opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwMapInfo.html
1384771755 6360 /opt/OV/www/htdocs/C/java_libovw/doc/
tree.html
3085302665 3141 /opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwLocationInfo.html
630439029 2679 /opt/OV/www/htdocs/C/java_libovw/doc/
hp.ov.libovw.OVwLocationList.html
3165103517 952 /opt/OV/www/htdocs/bitmaps/C/cards/
mux_c.16.gif
1136893815 927 /opt/OV/www/htdocs/bitmaps/C/cards/
mux_c.20.gif
557641612 965 /opt/OV/www/htdocs/bitmaps/C/cards/
mux_c.26.gif
222388923 1004 /opt/OV/www/htdocs/bitmaps/C/cards/
mux_c.32.gif
3676266387 1031 /opt/OV/www/htdocs/bitmaps/C/cards/
mux_c.38.gif
1749087680 1076 /opt/OV/www/htdocs/bitmaps/C/cards/
mux_c.44.gif
64856280 1109 /opt/OV/www/htdocs/bitmaps/C/cards/
mux_c.50.gif
374304949 893 /opt/OV/www/htdocs/bitmaps/C/misc/binoc.16.gif
3458433795 186 /opt/OV/www/htdocs/bitmaps/C/misc/
binoc.20.gif
2254895431 71923 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/
nnm/Content/cnttsk.htm
1253201116 33385 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/
nnm/Content/rptref.htm
4294967295 0 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/
Content/nnmswitchref.htm
4294967295 0 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/
Content/nnmswitchtsk.htm
2738775795 19049 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/
nnm/Content/rpttsk.htm
4013368359 87664 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/
nnm/Content/cntref.htm
1115995608 1965 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/
Context/cxtglos.htm
3843481746 1919 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/
Context/cxtoth.htm
123951736 1917 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/
Context/cxtref.htm
234654565 1415 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/
Scope/scpref.htm
547881139 6933 /opt/OV/www/htdocs/ja_JP.SJIS/OvWebHelp/nnm/
Scope/scptsk.htm
853854313 2114 /opt/OV/www/htdocs/ja_JP.SJIS/launcher/
login.tmpl
199403137 2217 /opt/OV/www/htdocs/ja_JP.SJIS/launcher/
retry.tmpl
1865645901 1457 /opt/OV/www/htdocs/ja_JP.SJIS/launcher/
welcometopics.html
2672721588 166140 /opt/OV/www/htdocs/ja_JP.SJIS/
ReleaseNotes/ReadmeAll_NNMGR.html
2674778477 18304 /opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeNew_NNMGR.html
505354552 59072 /opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeKnownProblems_NNMGR.html
2165749353 45323 /opt/OV/www/htdocs/ja_JP.SJIS/ReleaseNotes/
ReadmeInstall_NNMGR.html
753373036 71923 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Content/cnttsk.htm
3872925397 33390 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Content/rptref.htm
4294967295 0 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/
Content/nnmswitchref.htm
4294967295 0 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/nnm/
Content/nnmswitchtsk.htm
849770849 19049 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Content/rpttsk.htm
2353239521 87664 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Content/cntref.htm
3784385732 1965 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Context/cxtglos.htm
2610610100 1919 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Context/cxtoth.htm
1140541754 1917 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Context/cxtref.htm
1738438376 1415 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Scope/scpref.htm
2903750201 6933 /opt/OV/www/htdocs/ja_JP.eucJP/OvWebHelp/
nnm/Scope/scptsk.htm
338076303 2114 /opt/OV/www/htdocs/ja_JP.eucJP/launcher/
login.tmpl
1073500129 2217 /opt/OV/www/htdocs/ja_JP.eucJP/launcher/
retry.tmpl
2856464958 1457 /opt/OV/www/htdocs/ja_JP.eucJP/launcher/
welcometopics.html
1424879909 166138 /opt/OV/www/htdocs/ja_JP.eucJP/
ReleaseNotes/ReadmeAll_NNMGR.html
3219172659 18303 /opt/OV/www/htdocs/ja_JP.eucJP/
ReleaseNotes/ReadmeNew_NNMGR.html
1998030499 59073 /opt/OV/www/htdocs/ja_JP.eucJP/
ReleaseNotes/ReadmeKnownProblems_NNMGR.html
2308170325 45324 /opt/OV/www/htdocs/ja_JP.eucJP/
ReleaseNotes/ReadmeInstall_NNMGR.html
4288836297 32858 /opt/OV/www/bin/htpasswd
2246673163 2388961 /opt/OV/lib/libovwww.2
50295032 419308 /opt/OV/lib/libovwparser.2
3812187731 477522 /opt/OV/lib/libovsnmp.2
1106472992 230719 /opt/OV/lib/libov.2
2228653385 679120 /opt/OV/lib/libovutil.2
3763463059 300246 /opt/OV/lib/libovgui.2
768995489 24643 /opt/OV/lib/libovextfmt.2
1519187026 301106 /opt/OV/lib/libevent.2
2386525527 1035374 /opt/OV/lib/libovtopm.2
553687679 519894 /opt/OV/lib/libovfilter.2
2245898358 783203 /opt/OV/lib/libovw.2
3648544720 17463 /opt/OV/lib/nls/ja_JP.SJIS/xnmsnmpconf.cat
3017905211 77514 /opt/OV/lib/nls/ja_JP.SJIS/events.cat
3067850710 52254 /opt/OV/lib/nls/ja_JP.SJIS/util_libs.cat
4066227453 17463 /opt/OV/lib/nls/ja_JP.eucJP/xnmsnmpconf.cat
1981049286 77514 /opt/OV/lib/nls/ja_JP.eucJP/events.cat
4204142615 52254 /opt/OV/lib/nls/ja_JP.eucJP/util_libs.cat
3338607446 74045 /opt/OV/bin/ovsessionmgr
2433721710 32841 /opt/OV/bin/regverify
1300286866 73909 /opt/OV/bin/ovstart
1300286866 73909 /opt/OV/bin/ovstop
1300286866 73909 /opt/OV/bin/ovstatus
1672508614 447116 /opt/OV/bin/ovspmd
4066719189 221892 /opt/OV/bin/xnmevents
4101753694 41054 /opt/OV/bin/ovactiond
521116423 45179 /opt/OV/bin/ovtrapd
799007730 880697 /opt/OV/bin/netmon
2604563906 296733 /opt/OV/bin/ovrepld
2184633292 57522 /opt/OV/bin/loadhosts
2553213868 131451 /opt/OV/bin/snmpCollect
3302365907 147860 /opt/OV/bin/xnmcollect
933100185 135688 /opt/OV/bin/xnmtopoconf
1089690080 258667 /opt/OV/bin/xnmgraph
1299294132 584542 /opt/OV/bin/ipmap
695428432 32852 /opt/OV/bin/ovtopodump
3918979213 82211 /opt/OV/bin/ovtopofix
2039740899 366648 /opt/OV/bin/ovtopmd
252710988 135702 /opt/OV/bin/xnmbuilder
3570779999 21265 /opt/OV/bin/Perl/lib/ovbackup.pm
1356177396 41063 /opt/OV/bin/ovexprguru
3318559185 123360 /opt/OV/bin/xnmbrowser
276971572 73930 /opt/OV/bin/xnmpolling
855298861 41120 /opt/OV/bin/ovweb
496274527 41144 /opt/OV/bin/findroute
1270992978 119261 /opt/OV/bin/xnmappmon
3018192382 127435 /opt/OV/bin/rnetstat
295272102 45203 /opt/OV/bin/netcheck
1644303750 90382 /opt/OV/bin/ovhelp
2512277880 2695050 /opt/OV/bin/ovw
1924491925 387422 /opt/OV/bin/ovwdb
1736960969 82252 /opt/OV/bin/ovuispmd
162340573 715119 /opt/OV/bin/ovalarmsrv
19846124 32851 /opt/OV/bin/ovalarmadm
1251376117 77998 /opt/OV/bin/ovdbcheck
2669366256 69855 /opt/OV/bin/ovdwtrend
297079515 90412 /opt/OV/bin/ovcolsum
1475921476 193259 /opt/OV/bin/ovcoltosql
1950679212 94493 /opt/OV/bin/ovcoldelsql
10973069 115010 /opt/OV/bin/ovdwevent
3337276627 65824 /opt/OV/bin/ovdweventflt
3421163330 115077 /opt/OV/bin/ovdwtopo
2901876514 57498 /opt/OV/bin/ovdwquery
2589616830 168644 /opt/OV/bin/ovcolqsql
1834866788 35448 /opt/OV/bin/ovdbsetupo1.sh
3960742092 28015 /opt/OV/bin/ovdbsetupo3.sh
2140709816 17807 /opt/OV/bin/ovdbsetupo2.sh
4017619844 9175 /opt/OV/bin/ovdbtrend_dsko.sh
1468757438 41091 /opt/OV/bin/request_create
1544271682 36984 /opt/OV/bin/request_delete
819803687 36984 /opt/OV/bin/request_list
3635456295 36984 /opt/OV/bin/request_status
767993130 49292 /opt/OV/bin/ovrequestd
1483938704 32853 /opt/OV/bin/ovcwd
2194740675 102856 /opt/OV/bin/ovreppublish
4145725899 98629 /opt/OV/bin/xnmsnmpconf
2849747930 1071 /opt/OV/newconfig/OVWWW-FW/www/registration/
jovw/C/webbrowser
3378955724 6522 /opt/OV/newconfig/OVWWW-FW/www/registration/
jovw/C/jovw
1444021603 3900 /opt/OV/newconfig/OVWWW-FW/www/registration/
jovw/C/snmpviewer
4031252763 1257 /opt/OV/newconfig/OVWWW-FW/www/registration/
jovw/C/terminal
2801412809 907 /opt/OV/newconfig/OVWWW-FW/www/registration/
jovw/C/mibbrowser
3139235473 7142 /opt/OV/newconfig/OVWWW-FW/www/registration/
launcher/C/jovw
992130700 15565 /opt/OV/newconfig/OVWWW-FW/www/registration/
launcher/C/snmpviewer
2095501528 4214 /opt/OV/newconfig/OVWWW-FW/www/registration/
launcher/C/mibbrowser
2013145193 27 /opt/OV/newconfig/OVWWW-FW/www/etc/htpasswd
3945211162 16213 /opt/OV/newconfig/OVMIN/conf/ovbackup/
checkpoint/operational/nnm_checkpoint.ovpl
3026795733 19614 /opt/OV/newconfig/OVMIN/conf/ovbackup/
restore/operational/nnm_restore.ovpl
1215985844 3809 /opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/
PairWise.ds
3495016429 1013 /opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/
RepeatedEvent.ds
1660480161 15555 /opt/OV/newconfig/OVEVENT-MIN/ecsCircuits/
C/RepeatedEvent.param
2078406515 7528 /opt/OV/newconfig/OVNNM-RUN/fields/C/
snmp_fields
1836703755 5418 /opt/OV/newconfig/OVNNM-RUN/conf/
mibExpr.conf
3025106839 29161 /opt/OV/newconfig/OVNNM-RUN/conf/
mibExprGuru.conf
2419638961 2104 /opt/OV/newconfig/OVNNM-RUN/conf/ov.conf
2884904380 2957 /opt/OV/newconfig/OVNNM-RUN/registration/C/
terminal
2241264656 850492 /opt/OV/newconfig/OVNNM-RUN/nnm.sdl
4294967295 0 /opt/OV/newconfig/OVNNM-RUN/nnmswitch.sdl
226627911 620869 /opt/OV/newconfig/OVWIN/bitmaps.tar.Z
669836078 418 /opt/OV/newconfig/OVWWW-EVNT/lrf/
ovalarmsrv.lrf
368766561 881 /opt/OV/newconfig/OVWWW-EVNT/www/registration/
jovw/C/alarmbr
302981792 8956 /opt/OV/newconfig/OVWWW-EVNT/www/
registration/launcher/C/ecscmg
1721440681 1043 /opt/OV/newconfig/OVWWW-JPN/www/
registration/jovw/ja_JP.SJIS/webbrowser
726144118 6601 /opt/OV/newconfig/OVWWW-JPN/www/registration/
jovw/ja_JP.SJIS/jovw
1349280190 3905 /opt/OV/newconfig/OVWWW-JPN/www/
registration/jovw/ja_JP.SJIS/snmpviewer
1789631279 890 /opt/OV/newconfig/OVWWW-JPN/www/registration/
jovw/ja_JP.SJIS/alarmbr
1985997333 1238 /opt/OV/newconfig/OVWWW-JPN/www/
registration/jovw/ja_JP.SJIS/terminal
2504926140 910 /opt/OV/newconfig/OVWWW-JPN/www/registration/
jovw/ja_JP.SJIS/mibbrowser
4236774677 1043 /opt/OV/newconfig/OVWWW-JPN/www/
registration/jovw/ja_JP.eucJP/webbrowser
2947821190 6601 /opt/OV/newconfig/OVWWW-JPN/www/
registration/jovw/ja_JP.eucJP/jovw
351489743 3905 /opt/OV/newconfig/OVWWW-JPN/www/registration/
jovw/ja_JP.eucJP/snmpviewer
1026014575 890 /opt/OV/newconfig/OVWWW-JPN/www/registration/
jovw/ja_JP.eucJP/alarmbr
1284563703 1238 /opt/OV/newconfig/OVWWW-JPN/www/
registration/jovw/ja_JP.eucJP/terminal
362578882 910 /opt/OV/newconfig/OVWWW-JPN/www/registration/
jovw/ja_JP.eucJP/mibbrowser
3452121955 7352 /opt/OV/newconfig/OVWWW-JPN/www/
registration/launcher/ja_JP.SJIS/jovw
3148298073 15887 /opt/OV/newconfig/OVWWW-JPN/www/
registration/launcher/ja_JP.SJIS/snmpviewer
319712906 8921 /opt/OV/newconfig/OVWWW-JPN/www/registration/
launcher/ja_JP.SJIS/ecscmg
576458786 4307 /opt/OV/newconfig/OVWWW-JPN/www/registration/
launcher/ja_JP.SJIS/mibbrowser
552130634 7352 /opt/OV/newconfig/OVWWW-JPN/www/registration/
launcher/ja_JP.eucJP/jovw
1119349992 15887 /opt/OV/newconfig/OVWWW-JPN/www/
registration/launcher/ja_JP.eucJP/snmpviewer
958876449 8921 /opt/OV/newconfig/OVWWW-JPN/www/registration/
launcher/ja_JP.eucJP/ecscmg
1374143851 4307 /opt/OV/newconfig/OVWWW-JPN/www/
registration/launcher/ja_JP.eucJP/mibbrowser
2593912657 2972 /opt/OV/newconfig/OVNNMGR-JPN/registration/
ja_JP.SJIS/terminal
1792292337 12840 /opt/OV/newconfig/OVNNMGR-JPN/registration/
ja_JP.SJIS/ipmap
1175959488 2972 /opt/OV/newconfig/OVNNMGR-JPN/registration/
ja_JP.eucJP/terminal
1304054424 12840 /opt/OV/newconfig/OVNNMGR-JPN/registration/
ja_JP.eucJP/ipmap
2801521938 15685 /opt/OV/newconfig/OVNNMGR-JPN/ecsCircuits/
ja_JP.SJIS/RepeatedEvent.param
2508694468 15685 /opt/OV/newconfig/OVNNMGR-JPN/ecsCircuits/
ja_JP.eucJP/RepeatedEvent.param
2569868253 845515 /opt/OV/newconfig/OVNNMGR-JPN/help/
ja_JP.SJIS/NNM/nnm.sdl
4294967295 0 /opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.SJIS/
SwitchTopology/nnmswitch.sdl
2455239344 841869 /opt/OV/newconfig/OVNNMGR-JPN/help/
ja_JP.eucJP/NNM/nnm.sdl
4294967295 0 /opt/OV/newconfig/OVNNMGR-JPN/help/ja_JP.eucJP/
SwitchTopology/nnmswitch.sdl
3480419736 7262 /opt/OV/man/man4.Z/oid_to_type.4
2746650776 4663 /opt/OV/man/man4.Z/mibExpr.conf.4
3432953254 1902 /opt/OV/man/man4.Z/netmon.snmpStatus.4
1700745768 1799 /opt/OV/man/man4.Z/netmon.statusMapping.4
1902302606 3406 /opt/OV/man/man4.Z/netmon.cmstr.4
1605253724 2143 /opt/OV/man/man4.Z/ov.conf.4
1702334886 11006 /opt/OV/man/man4.Z/ovsnmp.conf.4
2179313005 6656 /opt/OV/man/man1m.Z/xnmtopoconf.1m
1938268330 12335 /opt/OV/man/man1m.Z/netmon.1m
2526823549 5131 /opt/OV/man/man1m.Z/ovtopofix.1m
2938761452 5907 /opt/OV/man/man1m.Z/snmpCollect.1m
4294967295 0 /opt/OV/man/man1m.Z/switchdiscovery.1m
1983680233 4474 /opt/OV/man/man1m.Z/loadhosts.1m
622424973 3368 /opt/OV/man/man1m.Z/ovdbcheck.1m
1998548136 2179 /opt/OV/man/man1m.Z/ovactiond.1m
798681740 1536 /opt/OV/man/man1m.Z/ovalarmsrv.1m
3829057175 1838 /opt/OV/man/man1m.Z/ovalarmadm.1m
1838416341 5188 /opt/OV/man/man1.Z/ovdwevent.1
1570823530 6239 /opt/OV/man/man1.Z/ovdwtrend.1
4031518566 3472 /opt/OV/man/man1.Z/ovcolsum.1
1399683962 6274 /opt/OV/man/man1.Z/ovdweventflt.1
470682086 4321 /opt/OV/man/man1.Z/ovcoldelsql.1
4294967295 0 /opt/OV/man/man1.Z/switchmap.1
916859395 9136 /opt/OV/man/man1.Z/xnmsnmpconf.1
3157535295 11617 /opt/OV/man/man1.Z/ovw.1
610934490 826 /opt/OV/man/man3.Z/OVsnmpConfPrintCntl.3
4071670196 1095 /opt/OV/man/man3.Z/OVsnmpConfPrintDest.3
716822568 1230 /opt/OV/man/man3.Z/OVsnmpConfPrintEntry.3
1226676834 3019 /opt/OV/man/man3.Z/OVwGetLocations.3
1226676834 3019 /opt/OV/man/man3.Z/
OVwGetLocationsByAttribute.3
1226676834 3019 /opt/OV/man/man3.Z/
OVwGetLocationsByComment.3
1226676834 3019 /opt/OV/man/man3.Z/
OVwGetLocationsBySelectionName.3
1226676834 3019 /opt/OV/man/man3.Z/
OVwGetLocationsBySymbolLabel.3
1226676834 3019 /opt/OV/man/man3.Z/
OVwGetLocationsBySymbolStatus.3
1226676834 3019 /opt/OV/man/man3.Z/
OVwGetLocationsBySymbolType.3
1226676834 3019 /opt/OV/man/man3.Z/OVwFreeLocationList.3
2190702122 1549 /opt/OV/man/man3.Z/OVwDisplaySubmap.3
2190702122 1549 /opt/OV/man/man3.Z/OVwCloseSubmap.3
310617331 89021 /opt/OV/include/OV/ovw.h
2252942936 1033 /opt/OV/contrib/NNM/baseliner/mibExpr.conf
3315764226 3376 /opt/OV/contrib/NNM/ovalarm/ovalarm.ovpl
1101941190 17953 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/J1240-90014.dat
2071391486 17351 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/J1240-90014.edr
3455139158 1023 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/J1240-90014.tag
4059069443 89 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/equation.tdr
4059069443 89 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/example.tdr
4113703801 209 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/figure.tdr
4059069443 89 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/proced.tdr
2573492642 146 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/table.tdr
950796147 1313 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/ebt/toc.tdr
551855168 20707 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/figures/gfx1.gif
3040113773 12238 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/figures/gfx2.gif
2265243310 48694 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/index/index.dat
47750095 6687 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/index/vocab.dat
1745157994 1497 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/J1240-90014.qrs
1339019252 34 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/hytime.cat
3380861677 58 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90014/styles.ent
2211820732 101686 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/figures/gfx1.cgm
2324199060 54188 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/figures/gfx2.cgm
3869219880 1460 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/figures/gfx3.cgm
3445864513 1888096 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/figures/gfx4.cgm
1113464496 101130 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/figures/gfx5.tif
3155828730 69407 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/J1240-90005.dat
304628895 72231 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/J1240-90005.edr
1680751742 1391 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/J1240-90005.tag
3454569684 90 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/equation.tdr
3454569684 90 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/example.tdr
2611824885 308 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/figure.tdr
3454569684 90 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/proced.tdr
2960859124 1018 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/table.tdr
3315626512 3177 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/ebt/toc.tdr
796282847 152482 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/index/index.dat
60336828 11573 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/index/vocab.dat
1745157994 1497 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/J1240-90005.qrs
3621599193 85 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/hytime.cat
3380861677 58 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90005/styles.ent
1348905868 188888 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/graphics/wizard.tif
285071649 98192 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/graphics/invrept.tif
2838185146 19054 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx1.gif
2497966492 7671 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx10.gif
2965088191 8791 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx11.gif
2298663987 25239 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx12.gif
694024032 11526 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx2.gif
1021218032 19001 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx3.gif
3120658973 5835 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx4.gif
3983412501 14709 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx5.gif
3354317519 16938 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx6.gif
3259428287 46474 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx7.gif
1732199569 36550 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx8.gif
3681166140 42217 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/figures/gfx9.gif
3121516511 105358 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/J1240-90015.dat
1789554598 1477 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/table.tdr
2265133994 89 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/example.tdr
37638979 8043 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/toc.tdr
2265133994 89 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/proced.tdr
2265133994 89 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/equation.tdr
620694246 643 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/figure.tdr
889302681 2361 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/J1240-90015.tag
2014213158 134790 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/ebt/J1240-90015.edr
1048464565 18153 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/index/vocab.dat
4184099415 260238 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/index/index.dat
3380861677 58 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/styles.ent
3178843656 207 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/hytime.cat
1745157994 1497 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90015/J1240-90015.qrs
501429536 203 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/table.tdr
3002353539 88 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/example.tdr
2675947521 1431 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/toc.tdr
3002353539 88 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/proced.tdr
3002353539 88 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/equation.tdr
3002353539 88 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/figure.tdr
2291369495 14340 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/J1240-90048.dat
166698605 12659 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/J1240-90048.edr
3206417269 789 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/ebt/J1240-90048.tag
3475594134 5957 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/index/vocab.dat
3937040360 36709 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/index/index.dat
3380861677 58 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/styles.ent
1745157994 1497 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90048/J1240-90048.qrs
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/J1240-90033.qrs
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/J1240-90033.dat
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/J1240-90033.edr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/J1240-90033.tag
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/equation.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/example.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/figure.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/proced.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/table.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/ebt/toc.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx1.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx10.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx11.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx12.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx13.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx2.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx3.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx4.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx5.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx6.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx7.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx8.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/gfx9.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/ST_status.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/ad_status.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/adjacent.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/connect_status.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/cp.tif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/multi_connect.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/multi_device.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/nlabel.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/node.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/root.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/showinterface.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/stalarms.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/switchpol.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/switchport.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/switchto.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/figures/graphics/webst.gif
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/hytime.cat
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/index/index.dat
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/index/vocab.dat
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90033/styles.ent
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/J1240-90026.qrs
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/J1240-90026.dat
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/J1240-90026.edr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/J1240-90026.tag
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/equation.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/example.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/figure.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/proced.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/table.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/ebt/toc.tdr
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/index/index.dat
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/index/vocab.dat
4294967295 0 /opt/OV/doc/dynatext/NNMWelEngDoc/books/
J1240-90026/styles.ent
2302052690 5837 /opt/OV/doc/dynatext/NNMWelEngDoc/ents/
map.txt
2348963375 566 /opt/OV/doc/dynatext/NNMWelEngDoc/
booklist.txt
4185660917 740270 /opt/OV/opi/opi_proc/opiproc
3467445070 11164 /etc/opt/OV/share/conf/ovbackup/restore/
analytical/nnm_restore.ovpl
2605440157 123212 /etc/opt/OV/share/conf/stacks/pmd/
libovEvent.sl
2209417694 219370 /etc/opt/OV/share/conf/ecs/circuits/
ScheduledMaintenance.eco
2104183276 124710 /etc/opt/OV/share/conf/ecs/circuits/
PairWise.eco
3542371414 14718 /etc/opt/OV/share/conf/ecs/circuits/C/
PairWise.param
4022292297 1104 /etc/opt/OV/share/conf/ecs/circuits/C/
RepeatedEvent_param.mod
3449595392 1411 /etc/opt/OV/share/conf/ecs/circuits/C/
PairWise_param.mod
943049129 2299 /etc/opt/OV/share/conf/ecs/circuits/
PairWise_update.pl
858598682 208841 /etc/opt/OV/share/conf/ecs/circuits/
RepeatedEvent.eco
4178082607 2527 /etc/opt/OV/share/conf/ecs/circuits/
RepeatedEvent_update.pl
95810160 77 /etc/opt/OV/share/conf/ecs/circuits/
RepeatedEvent_ds.mod
2623609734 46 /etc/opt/OV/share/conf/ecs/circuits/
PairWise_ds.mod
3851583117 211978 /etc/opt/OV/share/conf/ecs/circuits/
ConnectorDown.eco
99119130 14085 /etc/opt/OV/share/conf/ecs/circuits/
ja_JP.SJIS/PairWise.param
2287633481 14085 /etc/opt/OV/share/conf/ecs/circuits/
ja_JP.eucJP/PairWise.param
3826913572 1495 /etc/opt/OV/share/conf/analysis/sqlScripts/
export_minimal.sql
939267442 8406 /etc/opt/OV/share/conf/analysis/
excelTemplates/NNM/README_excelTemplates.txt
2394916865 8636 /etc/opt/OV/share/www/conf/NNM.spec
1228260363 33932 /etc/opt/OV/share/backgrounds/china1.gif
2241264656 850492 /var/opt/OV/share/help/C/NNM/nnm.sdl
4294967295 0 /var/opt/OV/share/help/C/SwitchTopology/
nnmswitch.sdl
2569868253 845515 /var/opt/OV/share/help/ja_JP.SJIS/NNM/
nnm.sdl
4294967295 0 /var/opt/OV/share/help/ja_JP.SJIS/
SwitchTopology/nnmswitch.sdl
2455239344 841869 /var/opt/OV/share/help/ja_JP.eucJP/NNM/
nnm.sdl
4294967295 0 /var/opt/OV/share/help/ja_JP.eucJP/
SwitchTopology/nnmswitch.sdl
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_20790 PHSS_20795 PHSS_20938 PHSS_20982 PHSS_21015 PHSS_21073
PHSS_21133 PHSS_21135 PHSS_21137 PHSS_21139 PHSS_21141 PHSS_21143
PHSS_21146 PHSS_21150 PHSS_21152 PHSS_21157 PHSS_21159 PHSS_21162
PHSS_21166 PHSS_21168 PHSS_21170 PHSS_21174 PHSS_21177 PHSS_21243
PHSS_21245 PHSS_21249 PHSS_21252 PHSS_21255 PHSS_21277 PHSS_21295
PHSS_21297 PHSS_21307 PHSS_21401 PHSS_21403 PHSS_21405 PHSS_21407
PHSS_21413 PHSS_21416 PHSS_21441 PHSS_21473 PHSS_21475 PHSS_21477
PHSS_21497 PHSS_21500 PHSS_21526 PHSS_21528 PHSS_21536 PHSS_21538
PHSS_21547 PHSS_21550 PHSS_21557 PHSS_21783 PHSS_21823 PHSS_21837
PHSS_21839 PHSS_21846 PHSS_21848 PHSS_21851 PHSS_21860 PHSS_21870
PHSS_21916 PHSS_21918 PHSS_21920 PHSS_21930 PHSS_21997 PHSS_22018
PHSS_22026 PHSS_22028 PHSS_22049 PHSS_22051 PHSS_22055 PHSS_22061
PHSS_22064 PHSS_22068 PHSS_22094 PHSS_22108 PHSS_22110 PHSS_22115
PHSS_22130 PHSS_22153 PHSS_22171 PHSS_22173 PHSS_22210 PHSS_22212
PHSS_22219 PHSS_22221 PHSS_22236 PHSS_22238 PHSS_22240 PHSS_22242
PHSS_22283 PHSS_22292 PHSS_22297 PHSS_22299 PHSS_22301 PHSS_22332
PHSS_22334 PHSS_22336 PHSS_22355 PHSS_22375 PHSS_22384 PHSS_22386
PHSS_22388 PHSS_22395 PHSS_22398 PHSS_22400 PHSS_22402 PHSS_22406
PHSS_22408 PHSS_22423 PHSS_22577 PHSS_22580 PHSS_22582 PHSS_22638
PHSS_22645 PHSS_22659 PHSS_22666 PHSS_22723 PHSS_22725 PHSS_22746
PHSS_22789 PHSS_22808 PHSS_22952 PHSS_22954 PHSS_22973 PHSS_23008
PHSS_23119 PHSS_23157 PHSS_23187 PHSS_23197 PHSS_23199 PHSS_23209
PHSS_23211 PHSS_23220 PHSS_23322 PHSS_23330 PHSS_23344 PHSS_23346
PHSS_23348 PHSS_23364 PHSS_23392 PHSS_23402 PHSS_23404 PHSS_23420
PHSS_23442 PHSS_23448 PHSS_23458 PHSS_23473 PHSS_23582 PHSS_23584
PHSS_23586 PHSS_23600 PHSS_23607 PHSS_23629 PHSS_23637 PHSS_23649
PHSS_23667 PHSS_23700 PHSS_23703 PHSS_23727 PHSS_23729 PHSS_23743
PHSS_23775 PHSS_23779 PHSS_23828 PHSS_23839 PHSS_23905 PHSS_23912
PHSS_23924 PHSS_23926 PHSS_23974 PHSS_23977 PHSS_24000 PHSS_24002
PHSS_24008 PHSS_24016 PHSS_24018 PHSS_24067 PHSS_24069 PHSS_24141
PHSS_24166 PHSS_24202 PHSS_24297 PHSS_24362 PHSS_24411 PHSS_24415
PHSS_24442 PHSS_24666 PHSS_24675 PHSS_24713 PHSS_24719 PHSS_24721
PHSS_24726 PHSS_24731 PHSS_24746 PHSS_24748 PHSS_24764 PHSS_24768
PHSS_24773 PHSS_24775 PHSS_24785
Equivalent Patches:
PHSS_24798:
s700: 11.00
s800: 11.00
PSOV_02988:
sparcSOL: 2.5 2.6 2.7 2.8
NNM_00767:
intelNT: 4.00 4.01
intelWIN2000: 1.00
Patch Package Size: 35620 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_24797
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_24797.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_24797. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_24797.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_24797.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
========================================================
BEFORE LOADING THIS PATCH...
If there are any ovw sessions running on either the
Management Station or on any Management Consoles, these
sessions need to be closed. The "ovstop" command
should then be executed.
WARNING : the patch will not install if any
Network Node Manager processes are
detected.
BACKUP ALL OpenView DIRECTORIES TO TAPE. This
pre-caution ensures that if you have problems after
installing the patch, you will be able to restore your
current state from tape.
NOTE : ovstart is NOT executed after the patch is loaded
You will need to manually run ovstart.
Also, in order to keep a history of the patches
installed on your system the post-install script
will attempt to copy this <patch_name>.text file
to /usr/OV/ReleaseNotes/patches
(or /opt/OV/ReleaseNotes/patches). Please make
sure this file is in /tmp before installation.
========================================================
This patch supersedes one or more previous patches. If the
superseded patches included special installation
instructions those instructions can be found below.
PHSS_24768:
.
PHSS_24731:
.
PHSS_24442:
n/a
PHSS_24018:
n/a
PHSS_24016:
n/a
PHSS_23839:
.
PHSS_23700:
On UN*X versions, due to a bug in the Java virtual machine,
Netscape may not display editable text fields in the events
area properly. Workaround is to run
'netscape -xrm "*XmTextField*marginHeight:1"'
PHSS_23584:
.
PHSS_23582:
.
PHSS_23442:
None
PHSS_23420:
Special installation instructions.
----------------------------------
The customer should use the commands
xnmcollect -loadExpr
$OV_NEW_CONF/OVNNM-RUN/conf/mibExpr.conf
xnmcollect -loadExpr
$OV_NEW_CONF/OVNNM-RUN/conf/mibExprGuru.conf
to copy the files in the patch to
$OV_CONF/mibExpr.conf as the patch installs
the files mibExpr.conf and mibExprGuru.conf under the
newconfig directory.
PHSS_23330:
Installation of this patch will overwrite
$OV_FIELDS/C/snmp_fields. In order to get the new field
populated for each node in the database, the following
steps need to be taken:
ovstart
ovstop netmon
ovtopofix -O #that is an upper-case oh, not a zero
ovstart netmon
Also, the snmp_fields file contains the definition of the
SNMPAgent enumerated field, which may have been edited by
the customer. In order to restore entries in this
enumeration that may have been lost by patch installation,
the customer can run "ovobjprint -f" and look for the field
id for the SNMPAgent field, and then run
"ovobjprint -e fid" where "fid" is the field id for that
field. This output will list all the enumerations
currently in the database, and if any are missing from
snmp_fields, they can be added at that point.
PHSS_23220:
Because the files included with this patch are
customizable by an administrator, the patch installation
will not copy these files directly to the
$OV_CONF/ovbackup/... directory. The files included with
this patch will be placed in
$OV_NEW_CONF/OVMIN/conf/ovbackup/...
checkpoint/operational/nnm_checkpoint.ovpl and
restore/operational/nnm_restore.ovpl
If any customizations have been made to these files in the
$OV_CONF/ovbackup/... directory, these changes will need
to be merged with the files in $OV_NEW_CONF, and the
resulting merged files placed in:
$OV_CONF/ovbackup/checkpoint/operational/
nnm_checkpoint.ovpl and
$OV_CONF/ovbackup/restore/operational/nnm_restore.ovpl
If no changes have been made to the original files, simply
copy:
$OV_NEW_CONF/OVMIN/conf/ovbackup/...
checkpoint/operational/nnm_checkpoint.ovpl and
restore/operational/nnm_restore.ovpl
to:
$OV_CONF/ovbackup/checkpoint/operational/
nnm_checkpoint.ovpl and
$OV_CONF/ovbackup/restore/operational/nnm_restore.ovpl
PHSS_23199:
N/A
PHSS_23197:
N/A
PHSS_23119:
The ovdbcheck executable in this patch is capable of
handling OpenView PAUSE and RESUME messages. This
functionality will not, however, be enabled unless the
"ovdbcheck.lrf" file is modified and re-registered. To
enable ovdbcheck's new PAUSE/RESUME logic, do the following
as superuser:
1. Install this patch. (Don't start Openview yet.)
2. Modify file /etc/opt/OV/share/lrf/ovdbcheck.lrf
(\openview\lrf\ovdbcheck.lrf on Windows) in the following
manner:
Add the PAUSE option to this line in the file:
OVs_YES_START::-ovspmd:OVs_WELL_BEHAVED:90:
The modifed line should look like:
OVs_YES_START::-ovspmd:OVs_WELL_BEHAVED:90:PAUSE
Re-register the ovdbcheck.lrf file using the following
command:
$ ovaddobj ovdbcheck.lrf
OpenView can now be started and the ovdbcheck will now
process PAUSE and RESUME messages.
Note: If this patch is REMOVED, the PAUSE option MUST be
removed (and re-registered) from the ovdbcheck.lrf file.
Otherwise, the "ovpause" command will unsuccesssfully try
to pause the ovdbcheck process.
PHSS_22952:
To complete installation of this patch on HP-UX and Solaris
systems, manually copy the webbrowser registration files to
the Network Presenter registration file directory. This is
not required on NT or Windows 2000 systems.
Do this after backing up the OpenView directories and
installing this patch. As root, execute the following
commands:
cd $OV_NEW_CONF/OVWWW-FW/www/registration/jovw/C/
cp webbrowser $OV_WWW_REG/jovw/C/
cd $OV_NEW_CONF/OVWWW-JPN/www/registration/jovw/$LANG
cp webbrowser $OV_WWW_REG/jovw/$LANG/
PHSS_22666:
This defect fix only affects cusomters who have Customer
Views installed.
PHSS_22423:
!!! ATTENTION !!!
It is important to backup your openview database before
installing this patch. The database format is modified in
this patch. Therefore, after uninstalling this patch
the openview database must either be removed and
recreated or restored from backup.
PHSS_22395:
The fix for SR Number 8606145726 requires the installation
of the latest Event Correlation Services (ECS) consolidated
patch dated September 2000 or later.
PHSS_21307:
This patch replaces
$OV_CONF/ovbackup/restore/analytical/nnm_restore.ovpl.
However, if you have previously run ovbackup and would
like to run ovrestore, you will have to replace this file
in the backup structure.
For example, if your backup is at $OV_TMP/ovbackup, replace
$OV_TMP/ovbackup/etc/opt/OV/share/
conf/ovbackup/restore/analytical/nnm_restore.ovpl with the
new version of the file.
This is only necessary if you are using the Solid database
to store analytical data.
-----End of Document ID: PHSS_24797------------------------------------------
Document ID: PHSS_24875
Date Loaded: 20010905
Title: s700_800 10.X OpenMail B.07.00 September 01 Periodic Patch
Patch Name: PHSS_24875
Patch Description: s700_800 10.X OpenMail B.07.00 September 01 Periodic Patch
Creation Date: 01/08/22
Post Date: 01/09/05
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OpenMail B.07.00
Filesets:
OpenMail.OM-ADM,B.07.00 OpenMail.OM-AMECAT,B.07.00
OpenMail.OM-AMEICE,B.07.00 OpenMail.OM-AMEPAW,B.07.00
OpenMail.OM-AMEPSS,B.07.00 OpenMail.OM-APPL,B.07.00
OpenMail.OM-BB,B.07.00 OpenMail.OM-CHSICE,B.07.00
OpenMail.OM-CHSPAW,B.07.00 OpenMail.OM-CORE,B.07.00
OpenMail.OM-DESK,B.07.00 OpenMail.OM-DSYNC,B.07.00
OpenMail.OM-ENGCAT,B.07.00 OpenMail.OM-ENGICE,B.07.00
OpenMail.OM-ENGPAW,B.07.00 OpenMail.OM-ENGPSS,B.07.00
OpenMail.OM-FINICE,B.07.00 OpenMail.OM-FINPAW,B.07.00
OpenMail.OM-FREICE,B.07.00 OpenMail.OM-FREPAW,B.07.00
OpenMail.OM-GERICE,B.07.00 OpenMail.OM-GERPAW,B.07.00
OpenMail.OM-IMAP4,B.07.00 OpenMail.OM-ITAICE,B.07.00
OpenMail.OM-ITAPAW,B.07.00 OpenMail.OM-KORICE,B.07.00
OpenMail.OM-KORPAW,B.07.00 OpenMail.OM-LC,B.07.00
OpenMail.OM-LDAP,B.07.00 OpenMail.OM-MAN,B.07.00
OpenMail.OM-NIPICE,B.07.00 OpenMail.OM-NIPPAW,B.07.00
OpenMail.OM-PMOVER,B.07.00 OpenMail.OM-POP3,B.07.00
OpenMail.OM-PTBICE,B.07.00 OpenMail.OM-PTBPAW,B.07.00
OpenMail.OM-RC,B.07.00 OpenMail.OM-SMS,B.07.00
OpenMail.OM-SPAICE,B.07.00 OpenMail.OM-SPAPAW,B.07.00
OpenMail.OM-SWEICE,B.07.00 OpenMail.OM-SWEPAW,B.07.00
OpenMail.OM-UNIX,B.07.00 OpenMail.OM-WEBADM,B.07.00
OpenMail.OM-X400,B.07.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_24875
Symptoms:
PHSS_24875:
CR: JAGad30137 SR: 8606160818
OpenMail B.06.00.00 + MayPP00
unix.in might hang and a message queued on the sendmail
queue when the message contains one part only, which is a
distribution list.
Workaround: Prior to sending the DL, add some text in the
body part of the message.
CR: JAGad31466 SR: 8606162150
One-way disrsync agreement between OpenMail and Exchange
(over OMEXCONN). Updates are done on the Exchange server.
When modifying attributes 111 and PHONE-1, then the next
dirsync results in the full loss of tis modified entry
within the OM directory. (However, the next dirsync cycle
will add the corrected entry again).
CR: JAGad49568 SR: 8606180347
Defining more than one sender name on the omtidyu
command-line makes omtidyu substitute the last defined name
as all defined names.
For example:
omtidyu -B -u "daniel wink" -R -T i -n -w "gren elliot" -n
-w "iain parker"
will return :
CRITERIA : Messages in the InTray NOT matching "iain parker
" in SENDER field AND NOT matching "iain parker " in SENDER
field.
CR: JAGad65896 SR: 8606196695
HPUX 11.x - 10.x
Openmail 6.0 Dec '00 PP
The incoming internet gateway, unix.in, loops if supplied
with a bad RCPT_TO or Arpa ORN that contains more than one
sign.
For instance,
To:
_//org/co/admd/prmd////RFC-822/ppinetia.coma.b.c
CR: JAGad67601 SR: 8606198411
Message with a large distribution list (thousands of
recipients) can take a long, long time to pass through the
X.400 gateway (from OpenMail to X.400).
CR: JAGad68810 SR: 8606199624
omshowcda -d <dir_name> displays the mask used to extract
directory entries. The format of this mask changed with GR6
PP-Mar. It used to be:
S/G/I
and now it is:
S=/G=/I=
This will also occur for other directory related commands
that display attribute masks.
CR: JAGad69036 SR: 8606199850
WC6.0 and PAW corrupts the autoreply covering text in the
languages Japenese, Korean and simplified Chinese when the
rule is listed. The covering text is not corrupted when
viewed from within the auto-replied message.
CR: JAGad69543 SR: 8606200362
Occasionally some message body parts, which require base 64
mime encoding, cause the item.browse binary to perform a
segmentation violation. This occurs when a user attempts to
read the message from the intray or folder area using an
IMAP client (Netscape communicator).
CR: JAGad70640 SR: 8606201464
Some scripts included in the OM-APPL component assume that
the 'cut' command is located in /usr/bin. In RedHat 7.1,
'cut' is located in /bin. The scripts affected are
omaddapp, omaddapppdl, omaddapppdln, omdelapp, omdelapppdl,
omdelapppdln, omshowapp, omshowapppdl and omshowapppdln.
CR: JAGad70641 SR: 8606201465
During installation of patch PHSS_23491 the script vvice
attempts to create the directory
/var/opt/openmail/temp/vv_bkp_log and fails. The directory
/var/opt/openmail/temp has the sensitivity label "SYSTEM
INSIDE" and the vvice script is executed from within the
"SYSTEM" environment and therefore does not have
sufficient privileges to perform the operation.
During installation of the patch PHSS_23491, vvsync
attempts to copy the portal.daemon and kill.portal binaries
from /opt/openmail/bin to the CHROOTED bin directory and
fails. These binaries do not form part of the OpenMail
B.07.xx.xx components and therfore are not present in the
OpenMail bin directory.
During installation of the patch PHSS_23491, user
configurable settings are not retained in the general.cfg
CR: JAGad71090 SR: 8606201916
Web Client 6.0 may, under certain cirumstances, display the
incorrect item count when listing items in the tray areas
or the folder areas.
CR: JAGad71959 SR: 8606202785
Clear/signed S/MIME message sent into OpenMail via Internet
g/w cannot be browsed by IMAP client. The multipart/signed
part of the message is empty.
The message can be successfully read by the OMGUI client.
CR: JAGad74578 SR: 8606205403
Some messages that have come from the internet contain
attachments that cannot be opened when using an IMAP client
(eg. Internet Explorer or Netscape).
Typically these are messages that only contain an
attachment and no covering text, but other types of message
structure may also suffer from this problem.
The user typically sees a copy progress bar that just
stops, the transfer of the attachment does not complete.
The format of attachment within the MIME message is not
correct - it should be base64 and in fact the data is
unencoded.
CR: JAGad74715 SR: 8606205540
This applies to B.06.00.00 and B.07.00.00
Use of ldapmodify to replace the mhsORAddress or omAddress
attributes does not work if attempting to replace existing
individual attributes, other than S, S-TX, G and G-TX.
For instance, if the entry for S=user111 has an OU1
configured, then
# ldapmodify -L UTF8-N -D "cn=clim, o=Openmail" -v
dn: cn=user111, o=OpenMail
changetype: modify
replace: mhsORAddresses
mhsORAddresses: S=user111/ou1=japan3
gives
ldap_modify: Operations error
ldap_modify: additional info: [OM 16092] An attribute has
multiple values, but is notconfigured as multi-value.
Parameter : Directory Entry Modifier
Attribute : OU1Max allowed size : 32
Required syntax : PRINTABLE-STRING
The error can also be seen on the server side, on the
omslapd debug output.
The recommended method is to use ldapmodify to modify the
individual attributes explicitly.
For instance, the input to ldapmodify would be
dn:...
changetype: modify
replace: 5
5: <new_OU1_value>
The internal names of the OU<n> attributes are used as they
are not mapped by default in the ~openmail/sys/ldap.attribs
file. Mappings could of course be added to this file, so
that more meaningful tags could be used in ldapmodify.
CR: JAGad75038 SR: 8606205863
Directory entries added using omaddent that contain
OCTET-STRING attributes have octets with certain values
stripped out. ommodent shows the same problem.
The FREEBUSY directory attributes used by Outlook FreeBusy
lookup are examples of OCTET-STRING data. A situation where
the FREEBUSY attributes may become incorrect is when
omdiropt is run on the FREEBUSY directory. This is because
omdiropt uses omaddent.
Octet \014 (14 decimal) is one value that gets stripped.
There may be some other values.
CR: JAGad75517 SR: 8606206344
The problem is seen on Linux with OM 7 only.
The problem is that issuing a valid IMAP command causes the
IMAP4 server to crash, which should not happen.
With the test mailbox, issuing the commands:
. login "username" "password"
. select inbox
. fetch 2 (BODY.PEEK[3.HEADER.FIELDS (Resent-Date)])
causes the crash.
CR: JAGad75975 SR: 8606206802
The problem is with the way that sendmail converts the
address and OpenMail subsequently parses it.
If an entry has the format \", then sendmail quotes it and
adds an extra \ to the \" sequence.
So us\"er <user.local>, goes to "us\\"er" <user/local>,
Openmail then splits up the address list using commans as
the separator. If a separator is in a quote, it ignores it.
In the above example, the quote after the \\ is taken to be
a closing quote. This means that things get out of sync, as
the last quote is taken to be an opening, rather than
closing, quote and the address list becomes mangled.
In addition, the mangled address list may now contain
entries in excess of 1024 characters This can cause a fatal
error.
CR: JAGad79081 SR: 8606209895
Certain printable chars may be used in the components, e.g.
Surname, of OM Personal Names, but should be represented by
special characters on input (see man page omattribs). Such
a char is that 'space' should be input as '_' to allow for
Surnames like "Van Gogh".
IMAP makes no allowance for this mapping, and so fails to
login because the username as input does not exist as an OM
user.
CR: JAGad80029 SR: 8606210842
OpenMail may fail to configure auxiliary child processes
correctly when using the omsetscv command. This results in
the child processes not terminating via the omshut command.
CR: JAGad83734 SR: 8606214543
This applies to B.07, when configured to allow duplicate
internet addresses in the directory. This is the default
for servers upgraded from an earlier version of OpenMail,
but not for new B.07 installations.
Using OMGUI to send a message, if an internet name is
entered that is in the OpenMail system directory twice and
the Dist. List is checked then a System Error 2 is
generated and the connection is lost (the UAL session is
terminated). This only occurs if individual name checking
is turned off.
This is caused by an error in the UAL Checklist command,
when attempting to return the duplicate entries as
alternatives. Note that, prior to B.07, UAL CheckList did
not actually return alternatives when searching on the
internet address field.
See also the related CR JAGad 83932, which is not planned
for fixing in the September 2001 Periodic Patch.
PHSS_23490:
CR: JAGab39939 SR: 8606100957
Omfmtent -u creates output that is corrupted. This occures
when an attribute name is specified and the attribute value
is not. The format of the output is incorrect because it
lists the attribute name but assigns no value to it making
the output unusable in scripts.
ie:
Input to omfmtent :
s=kessler/i=c/g=richard/q=/ou1=hdqt
Output of omfmtent :
1=kessler/3=c/2=richard/4/5=hdqt
As you can see by the above example, the output from the
omfmtent command is missing an "=" after the 4.
CR: JAGab68963 SR: 8606102906
The new server feature of REPEAT REMINDERS in the OMGUI and
MOB GUI do not stop sending out reminders after the Expiry
date.
CR: JAGad31664 SR: 8606162348
Can't reply in OMGUI and ccMail to messages from internet
whose address has comments.
CR: JAGad35090 SR: 8606165799
If 2 OpenMail users have the same name (but different
mailnodes) Single User Restore sometimes selects the wrong
message store to be restored.
CR: JAGad40563 SR: 8606171299
The web clients do not work with HTTPS and the Apache web
server.
When the user tries to signon they are presented with the
following message:
Bad Request
Your browser sent a request that this server could not
understand.
Reason: You're speaking plain HTTP to an SSL-enabled server
port.
CR: JAGad41471 SR: 8606172211
The UAL sometimes aborts on Redhat 7.0 systems when using
the directory relay service, with the following in the
OpenMail log:
SERIOUS ERROR Remote Client (U/I Access) 11.30.00 07:47:57
[OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 28277;
code = 0. Procedure trace follows:
-> pc_recv_logical_block
<- pc_recv_logical_block
<- pc_recvmessage
-> ual_SendMessage
<- ual_SendMessage
-> ual_RecvReply
-> ual_GetFreeBusyTime
-> ual_ConvORNCheck
-> ual_ConvertORN
-> ual_GetUserCharSet
<- ual_GetUserCharSet
<- ual_ConvertORN
<- ual_ConvORNCheck
-> ual_GetUsersHost
-> nm_ParseORN
<- nm_ParseORN
User Name: UAL TestUser2 / Test, UAL
Pid of logging process: 28277
CR: JAGad42968 SR: 8606173711
It is possible using Outlook with a MAPI connection to
OpenMail to send a message with an internet address
containing 8-bit characters in the domain name.
The outgoing Internet Gateway discards these domain names,
causing an attempt to be made to deliver the message to a
recipient with the same address but no domain name.
This is not correct: if an address is invalid, message
delivery should not be attempted to a partial address in
this manner, as there are potential privacy issues.
CR: JAGad43052 SR: 8606173797
When a message with accented characters in the subject is
copied across message stores using Netscape messenger, the
subject of the message has the MIME character set specifier
in it when viewed using omcontain, OMGUI, Outlook. The
subject appears OK when using Netscape Messenger.
CR: JAGad44030 SR: 8606174784
Openmail does not have a converter from unicode to IA5, but
it does have one from unicode to ISO8859_1.
When the item browser is used to display a text message
using the default format, it has no problem in displaying
the message if OM_DEF_USER_CHAR is set to ISO8859_1 in the
configuration file.
However, if OM_DEF_USER_CHAR is set to IA5, then the item
browser isn't able to do the conversion and reports an
error. As the error reported in the log file was that a
character set conversion between MIME-UTF8 and IA5 was
failing, then this is probably the case.
The second problem is the way that the item browser
displays the message in MIME format.
Adding the mapping of UTF-8 to UTF8 in the mime.cs file
means that the character set for the message is now UTF8
which is recognised by OpenMail and the message is
correctly displayed on most clients. However, for Netscape
Messenger, which uses the item browser MIME option, there
is a problem.
The steering file ~sys/brwmime.str specified that generally
character sets should be converted to ISO8859_1 unless
otherwise specified. This means that the item browser
attempts a conversion from UTF8 to ISO8859_1 and fails.
It should be noted that UNICODE is not generally supported
on OpenMail when messages are in the MIME format.
CR: JAGad45429 SR: 8606176189
When using PAW and Web Client 6.0 rule names may be
displayed incorrectly in Korean, Japanese and Simplified
Chinese versions. This may cause the browser to hang.
CR: JAGad45449 SR: 8606176209
Outlook OFS: Item created offline and synced, and then
modified offline but synced online causes a duplicate to be
created.
CR: JAGad45880 SR: 8606176642
The IMAP/item.browse aborts with a segmentation violation
on LINUX, when trying to encode an html attachment into
"Quoted-Printable" format.
CR: JAGad46439 SR: 8606177205
For an OpenMail server that is configured to support
Czech...
Messages being sent from X400 with 1992 standard General
Text: context-specific 0 (23 octets):
GeneralString (21 octets):
1b 28 42 0f 1b 2d 42 1b 7e 31 31 31 31 b1 ea 32 32 32
. ( B . . - B . ~ 1 1 1 1 . . 2 2 2
are not correctly converted by the X400 In Mapper. They
should be converted to files of type 1736 with character
set T61BASE, and the data of the file should be consistent
with this.
CR: JAGad46896 SR: 8606177664
The OpenMail Internet gateway rejects multipart/signed
messages if one of its composite, multipart or message,
part's boundary-end markers is missing.
CR: JAGad47713 SR: 8606178486
1) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
If a multibyte string contains an *, this is assumed to be
a wildcard.
2) Username incorrectly displayed if it contains TX fields.
The TX fields are concatenated to earlier field values.
This is also a problem with other address list attributes.
3) The -l option is not displayed.
This displays a list of the requested folders and should be
displayed in the full listing.
4) The error/usage string is not displayed if not options
are specified.
omtidyu either returns nothing, or prompts for the password
for the defult user.
5) The -q option does not work.
The -q option produce similar output to a full report, and
more information than a summary report.
6) The msg type selection is not output.
When a full report is requested, the information on each
item should include the message type.
7) The -f option no longer includes WB.
CR: JAGad48103 SR: 8606178878
If omprepsur is not able to salvage certain files, omdosur
is supposed to substitute some dummy containers instead and
then continue to create a valid omcpoutu archive. Infact,
omdosur was aborting straight after processing the missing
container and so was creating a corrupt omcpoutu archive.
CR: JAGad50818 SR: 8606181602
If a message is sent from a user who has an INTERNET_ADDR
defined, to another machine, e.g. via the SMINTFC gateway,
replies to that message do not get returned via the same
route - they always get returned via the INTERNET gateway.
This occurs when the receiving server does does not have
the user's INTERNET_ADDR defined in the directory, and when
the sending server is version GR7
CR: JAGad52689 SR: 8606183476
This applies to omsmtpd in Release 7.
With heavy usage, the SMTP Relay port 25 listener
occasionally stops with a Select error - Bad File Number.
The omshowlog output contains:
ERROR SMTP Relay (SMTPD Relay
Pr) 03.02.01 13:34:27
[OM.DMON 2163] Failed in select.
Error: 'Bad file number'
Alternatively, after logging this error, omsmtpd may hang.
In this case, there will be more than one copy of omsmtpd
running, and the parent will be waiting for the child
processes, and vice versa.
Temporary Workaround:
Stop and restart the daemon.
Or, if Authorisation or Anti-spam features are not in use,
turn off the relay, and rely on sendmail & ommapsmtp to
route incoming messages correctly.
CR: JAGad55411 SR: 8606186206
When shutting down the Remote Client Interface a
segmentation violation is occuring in the Notification
Monitor occasionally because of a buffer over-run or
under-run.
CR: JAGad56484 SR: 8606187277
The OpenMail delegate implementation does not include an
equivalent for Exchange's "Delegate can see my private
items" option (disabled by default in Exchange). Hence when
forwarding Meeting Requests no distinction is made between
Private items and others.
CR: JAGad56620 SR: 8606187413
Message delivery rulesets are not working with empty
subjects.
CR: JAGad57754 SR: 8606188546
omredirtcp logs errors "getsockname: Bad file number" when
no error has occurred.
CR: JAGad58840 SR: 8606189626
MAPI addressbook download fails when trying to download a
directory whose first entry is a large entry such as a pdl
because a buffer overflow occurs.
CR: JAGad63387 SR: 8606194177
A coding defect while processing MIME data sometimes causes
a fatal error within the item.browse binary.
On the Netscape Client the user is presented with the
message:
"The current command did not succeed. The mail server
responded: Some of the requested messages no longer exist."
CR: JAGad64229 SR: 8606195023
Some of the OpenMail patch install scripts may use return
codes which are invalid in Software Distibutor (SD). In
addition, symbolic names such as $SUCCESS, $FAILURE and
$WARNING should be instead of 0, 1 and 2.
Some of the messages do not follow the conventions, with a
word such as ERROR in column 1 of the first line only, and
the text indented to column 10.
CR: JAGad64671 SR: 8606195467
When performing searches of large message stores if the
ual.remote associated with the in.imap41d terminates due to
inactivity or is deliberately killed then in.imap41d goes
into a spin. When using TOP or glance the in.imap41d
processes appear to be consuming a lot of CPU activity,
however, they will not impact on system performance
because the kernel will have assigned them a low priority.
CR: JAGad66344 SR: 8606197150
When installing OpenMail B.07.00, file
~openmail/release.sys/smtpd.cfg is updated to contain the
current domain name in place of the string %LOCALDOMAIN%.
This is also done whenever a new OpenMail instance is
created.
When a patch is installed, the patch scripts need to repeat
this edit.
This does not affect ~openmail/sys/smtpd.cfg which is
intended to be tailored by the OpenMail administrator. This
file is not changed during patch installation.
Defect Description:
PHSS_24875:
CR: JAGad30137 SR: 8606160818
This form of message is not a multi-part message, and the
code that reads and processes the '.' terminator in this
case omitted to include the newline character in the check.
Hence the code attempted to continue to read stdin, and
hence the hang, as unix.in is waiting for more from
sendmail
CR: JAGad31466 SR: 8606162150
Exchange Connector resyncs were removing any
entry that had a non-addressing attribute changed on the
Exchange side - this was caused by the fact that the DS
entries coming from Exchange do NOT have a LID attribute so
the normal method of getting the entry using DA_SOURCE_LID
does not work.
CR: JAGad49568 SR: 8606180347
Multiple sender names on the omtidyu command line were all
held in a single buffer resulting in the last senders name
to be registered for all the sender names.
CR: JAGad65896 SR: 8606196695
This was caused by an error in the code that scans Arpa
ORNs, when attempting to map domain names to Openmail
mailnodes using the unixmap.in configuration file.
CR: JAGad67601 SR: 8606198411
The code that is used to build the PDUs for outgoing X.400
messages is not under our control, we use XAPI libraries to
give us a higher level interface to ASN.1 structures and
independence from the underlying MTA. This code is not
particularly efficient and it uses quite large structures
in memory when a PDU is being contructed. In the case of a
message that has a Distribution List with 10,000 names it
will take a long time and use a lot of resources.
The fix for this problem is to add some general.cfg options
to replace large distribution lists with a single name
distribution list. This will not prevent the message from
reaching the intended recipients, but it will speed up the
transfer of the message through the X.400 gateway. If this
DL replacement occurs then the message cannot be
successfully replied to 'all' (as the original distribution
list has been removed).
The general.cfg options are:
X4O_MAX_DL_NAMES=n
where n is the maximum number of names allowed in a
DistList before they get replaced with a single stub DL
name. Default is the current behaviour... there is no
limit.
where the string contains the stub DistList name in
positional ORN format (each ORN field separated with a '/'
character). %s can be used in this string and will be
substituted with the number of names found in the original
DistList. For example: X4O_MAX_DL_NAMES=1000
X4O_MAX_DL_NAMES_ORN=DistList/%s-Name///Black/Hole
will produce a name that the user sees as:
TO: 1001-Name DistList /Black,Hole
when a DistList with 1001 names is send through the X.400
gateway. The default for this ORN string is:
DISTRIBUTION-LIST/%s-NAME///MAIL-SYS
CR: JAGad68810 SR: 8606199624
The fix for JAGab39939 (omfmtent produces illegal directory
entries for entries with null values) has caused omshowcda
to display the directory mask to be displayed differently.
CR: JAGad69036 SR: 8606199850
The cause of the corrupted Korean, Japanese and Simplified
Chinese strings was due to an internal formating error.
CR: JAGad69543 SR: 8606200362
A coding defect within the item.browse binary resulted in a
failure while mime encoding a message.
CR: JAGad70640 SR: 8606201464
Some scripts supplied with OM-APPL specified the full path
name for the 'cut' command. They needed to be enhanced to
support a different location on some OS versions.
CR: JAGad70641 SR: 8606201465
The scripts vvice and vvysnc where not updated for OpenMail
B.07.00 periodic patches
CR: JAGad71090 SR: 8606201916
Hidden items within the message store were included within
the item count when listing the tray or folder areas.
CR: JAGad71959 SR: 8606202785
The mime browsing library only expects to be dealing with
message components in a serialised file. There are
occasions when the components of a message are not
serialised - when this is the case the browse of that item
returns nothing.
CR: JAGad74578 SR: 8606205403
The MIME header is slightly strange inasmuch as the value
is separated from the tag by two spaces. For example:
Content-Transfer-Encoding: base64
This causes the MIME generation routines (in some
circumstances) to misinterpret the MIME header field value.
In this particular case the MIME header has come in from
outside of OpenMail and is being retained in the
inetMessageHeader object file associated with the message.
CR: JAGad74715 SR: 8606205540
A coding error resulted in the mhsORAddress and omAddress
attribute being mapped only to the the Openmail S, S-TX, G
and G-TX attributes for the modify:replace option.
Consequently, when building the OpenMail modification data,
only the former surname and givenname attributes were
deleted and 2 values were supplied for OU1 and other
modified attributes.
CR: JAGad75038 SR: 8606205863
When processing ORNs, omaddent converts to T61 and then
breaks the ORN down into a set of T61 substrings. This may
mean adding some bytes (T61 characters) at the start of
each substring. For non-T61 values, these bytes are later
removed before the value is stored in the directory. This
defect was also removing bytes whose values are the same as
the T61 characters, but which were not added by the initial
parsing.
CR: JAGad75517 SR: 8606206344
The code that constructs the command output was erroneously
attempting to dereference a pointer whose value was NULL.
CR: JAGad75975 SR: 8606206802
Sendmail modifies entries of the form
user/"test <user/test>
to
"user//"test" <user/test>.
Openmail takes this and assumes that the second " ends the
quoted text, then the third quote opens further quoted text
and the To: input can become out of sync.
Further, it becomes possible for mangled addresses to be
greater in size that that expected causing a serious error
to occur.
CR: JAGad79081 SR: 8606209895
A coding defect in the IMAP Server does not take any
account of the special chars in OM Personal Names as input
and therefore fails to map them into those they represent.
CR: JAGad80029 SR: 8606210842
The child process IDs were corrupted within the process ID
configuration file due to incorrect file locking mechanisms
CR: JAGad83734 SR: 8606214543
UAL Checklist searches on the internet address field, and
records in the DL the entries with alternatives/duplicates.
Later it reprocesses the DL, re-searching to get the
alternatives in a new file, which is then appended to the
DL. However, the re-search is on the X400 attributes, not
on the internet address, and the alternatives file is not
created. But the attempt to append continued anyway, and
tried to open a non-existent file.
PHSS_23490:
CR: JAGab39939 SR: 8606100957
The parser does not take into account the case when there
is an attribute name but no attribute value.
CR: JAGab68963 SR: 8606102906
When a Repeat Reminder is set, the message is placed in the
message list DEFER.UA by the UAL. While calculating the
next submission date-time of the message, the final
reminder date is calculated based on the current date and
the value of the current reminder.
If the next submission date of the reminder message is less
than the final reminder date, then the message is placed on
the Service router for routing. Otherwise it is deleted
from the message list, so that no more repeat reminders
will be sent. But since the final reminder date is
calculated using the current date the submission date is
ALWAYS less than the final reminder date.
CR: JAGad31664 SR: 8606162348
The Outgoing Internet Gateway is confused by addresses that
can be generated by the cc:Mail client, such as :
"S=Friendly Name .gren/OU1=mime/
DDT1=RFC-822/DDV1=Friendly Name <grennowhere.hp.com>/
INTERNET-ADDR=Friendly Name <grennowhere.hp.com>"
===========================================================
A coding defect in the ux component tries to enclose the
"Comment <userdomain>" within angle brackets <>, by only
inserting a start bracket < at the beginning, before
passing it to Sendmail, resulting in unmatched brackets,
which naturally generates a Sendmail error.
CR: JAGad35090 SR: 8606165799
The algorithm used to select the approprate user's message
store to restore selects the last message store that
matches just the name part of the user's address.
CR: JAGad40563 SR: 8606171299
The Root-URL is used initially when sending back the
Location: header on signon. The SERVER-PROTOCOL environment
variable is used to construct part of the URL. It appears
that the Apache web server sets the SERVER-PROTOCOL
variable to HTTP/1.0 regardless of whether you are talking
HTTP or HTTPS, however it identifies the fact that we are
talking HTTPS by setting the environment variable
HTTPS="on"
CR: JAGad41471 SR: 8606172211
A segmentation fault occures when parsing a blank line at
the top of the mnMapFile which is located in the
var/opt/openmail/sys directory.
CR: JAGad42968 SR: 8606173711
A design defect in the mim component restricts the search
for an internet address within an ORN to the ordinary DDA
fields of the ORN. However an 8-bit address is stored in a
teletex DDA-TX field, which is ignored by this search and
so the internet address is effectively discarded.
CR: JAGad43052 SR: 8606173797
The IMAP daemon was not converting MIME subject before
copying an item into the OpenMail message store.
CR: JAGad44030 SR: 8606174784
The item browser fails to convert UTF8 to ISO8859_1 when a
message is in MIME format, even though a converter exists.
It recognises that a converter exists, but fails to convert
the UTF8 characters to UCS2 first in the case of the MIME
format. The conversion is then incorrect. In the case of
non MIME text, this two stage conversion is completed
successfully.
UNICODE conversions for MIME formatted messages are not
generally supported in OpenMail and so the 2 step
conversion required had not been implemented.
CR: JAGad45429 SR: 8606176189
When the rule name is read from the OpenMail Auto-Actions
file, tcl expects the format of the string to be UTF-8.
OpenMail does not store the rule names in UTf-8 format,
thus if the rule name is modified in anyway then it becomes
corrupted.
CR: JAGad45449 SR: 8606176209
When a folder is listed (UAL_PRPLST/UAL_LIST) any messages
in the list that not have TextPreview data setup get it
dynamically generated. This causes the ModifiedDate in the
ctner to be updated. This updated ModifiedDate in the ctner
means that the sync. process treats this as a conflict. The
fix is to suppress the ModifiedDate update for this
behind-the-scenes modification. As far a synchronisation
goes the TextPreview is a 'computed' field, dynamically
created in an offline store and is not synchronised data-
so this change is good both architecturally and
pragmatically.
CR: JAGad45880 SR: 8606176642
The attempted encoding of a ' ' character followed by a
'n' as the 1015 and 1016 characters of a line in an html
attachment resulted in the premature abort of the
item.browser and a subsequent segmentation violation.
CR: JAGad46439 SR: 8606177205
The General Text handling code at the incoming X400
interface was written on the assumption that the
interchange charset for non-Latin-1 single byte languages
would be based on an ISO8859_n charset, as used in General
Text bodyparts.
When the Czech version of OpenMail was done, it was decided
to use T61BASE as the interchange charset. However, the
X400 incoming mapper was not changed to properly convert
and map the bodyparts.
CR: JAGad46896 SR: 8606177664
A coding defect in the ux component tries to run off the
end of the temporary file holding the Multipart/Signed part
of the Sendmail message, when this part has missing
end-boundaries of composite contents types, Multipart or
Message.
CR: JAGad47713 SR: 8606178486
) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
The * character is assumed to be the wildcard character in
all cases. This may not be so for certain MB strings.
2) Username incorrectly displayed if it contains TX fields.
The display routine does not take the address group
separator 027 into consideration.
3) The -l option is not displayed.
This is an enhancement request.
4) The error/usage string is not displayed if not options
are specified.
A check to no parameters is not done.
5) The -q option does not work.
The reporting mechanism displays a full report if a SUMMARY
report is not requested, rather than if a FULL report is
requested.
6) The msg type selection is not output.
This is an enhancement request.
7) The -f option no longer includes WB.
In GR7, the -T w option is used to display the waste basket
CR: JAGad48103 SR: 8606178878
Some changes introduced to omdosur as part of the 5.20 MAPI
work, was failing to take into account the possibility of a
missing container.
CR: JAGad50818 SR: 8606181602
When the OMGUI processes a reply, it takes the Distribution
List of the original message and supplies it to UAL
Checklist, requesting Lookup of the 167 attribute in the
UnixMap directory for ORNs that have a group 5 internet
address field.
Messages received from GR7 may contain the internet address
of Openmail users as well as of internet users. If the GR7
internet addresses are not present in the directory of the
server where the reply is constructed, the 167 lookup will
fail to find a match. The code then assumes the recipient
is an internet user and adds the address of the internet
Gateway to the ORN.
CR: JAGad52689 SR: 8606183476
When the relay is heavily loaded, it creates one or more
child relay processes to share the incoming requests. The
child processes later stop when they have been idle for a
while (30 seconds by default). The select error can occur
when the parent is processing the Termination signal from
the child, if the signal is received between when the code
decides to look for input from the child (FD SET) and doing
the select.
After hitting this error, the code does not explicitly stop
the child relay processes, but does wait for them to die.
As the child processes may be waiting for instructions from
the parent, a hang can occur.
CR: JAGad55411 SR: 8606186206
The segmentation violation in the Notification Monitor is
caused by dirty data in a buffer which then causes a buffer
under-run or over-run to then occur. This dirty data
appears to be generated by a large number of
deregistrations for notifications which happens when the
RCI is shut down and timing problems cause a write to the
buffer to be killed thus generating the dirty data which is
then read. The current write is in two stages with the
possibility that the process can be terminated inbetween
these two writes.
CR: JAGad56484 SR: 8606187277
Currently the client does not set up a filter on the
Outlook delegate redirection to prevent private items being
redirected.
The best solution to this problem is to change the server
code so that by default a private Outlook meeting request
will NOT be redirected to a delegate. This behaviour can be
overridden by the LD_SENSITIVE_ITEM_DELEG_REDIR=TRUE
config option (user.cfg and general.cfg)
CR: JAGad56620 SR: 8606187413
Subject is not currently matched (via user-supplied script)
if the subject of the message is null (blank).
The fix is to change the code to allow a blank subject to
be matched. The old behaviour will be reinstated by setting
the RSL_MATCH_BLANK_SUBJECT=FALSE
general.cfg option.
CR: JAGad57754 SR: 8606188546
Porting changes for Linux have caused a problem with the
EINTR signal handling to become visible in the syslog.
EINTR signal handling corrected so that this interrupt is
silently swallowed.
CR: JAGad58840 SR: 8606189626
The failure to download the directory was caused by a
buffer overflow when reading in a large directory entry in
order to pass them to the client.
CR: JAGad63387 SR: 8606194177
The cause of this failure was due to incorrectly parsing
the Content-Disposition response header which sometimes
resulted in corrupted memory.
CR: JAGad64229 SR: 8606195023
The patch installation scripts contained hard-coded exit
codes of 0, 1 and 2, instead of the preferred $SUCCESS,
etc. Also, there were some cases where values other than 0,
1 or 2 could be returned.
CR: JAGad64671 SR: 8606195467
in.imap41d was going into a spin in the function imapsearch
because although conn->state was set to TERMINATED when the
ual socket had died this was not checked for.
CR: JAGad66344 SR: 8606197150
~openmail/release.sys/smtpd.cfg was replaced by an
unconfigured file during patch installation. It is now
edited so it contains a domain name. This is similar to the
work done during initial B.07.00 installation.
SR:
8606160818 8606162150 8606180347 8606196695 8606198411
8606199624 8606199850 8606200362 8606201464 8606201465
8606201916 8606202785 8606205403 8606205540 8606205863
8606206344 8606206802 8606209895 8606210842 8606214543
8606100957 8606102906 8606162348 8606165799 8606171299
8606172211 8606173711 8606173797 8606174784 8606176189
8606176209 8606176642 8606177205 8606177664 8606178486
8606178878 8606181602 8606183476 8606186206 8606187277
8606187413 8606188546 8606189626 8606194177 8606195023
8606195467 8606197150
Patch Files:
/opt/openmail/patch/filesets/OM-ADM
/opt/openmail/patch/filesets/OM-AMECAT
/opt/openmail/patch/filesets/OM-AMEICE
/opt/openmail/patch/filesets/OM-AMEPAW
/opt/openmail/patch/filesets/OM-AMEPSS
/opt/openmail/patch/filesets/OM-APPL
/opt/openmail/patch/filesets/OM-BB
/opt/openmail/patch/filesets/OM-CHSICE
/opt/openmail/patch/filesets/OM-CHSPAW
/opt/openmail/patch/filesets/OM-CORE
/opt/openmail/patch/filesets/OM-DESK
/opt/openmail/patch/filesets/OM-DSYNC
/opt/openmail/patch/filesets/OM-ENGCAT
/opt/openmail/patch/filesets/OM-ENGICE
/opt/openmail/patch/filesets/OM-ENGPAW
/opt/openmail/patch/filesets/OM-ENGPSS
/opt/openmail/patch/filesets/OM-FINICE
/opt/openmail/patch/filesets/OM-FINPAW
/opt/openmail/patch/filesets/OM-FREICE
/opt/openmail/patch/filesets/OM-FREPAW
/opt/openmail/patch/filesets/OM-GERICE
/opt/openmail/patch/filesets/OM-GERPAW
/opt/openmail/patch/filesets/OM-IMAP4
/opt/openmail/patch/filesets/OM-ITAICE
/opt/openmail/patch/filesets/OM-ITAPAW
/opt/openmail/patch/filesets/OM-KORICE
/opt/openmail/patch/filesets/OM-KORPAW
/opt/openmail/patch/filesets/OM-LC
/opt/openmail/patch/filesets/OM-LDAP
/opt/openmail/patch/filesets/OM-MAN
/opt/openmail/patch/filesets/OM-NIPICE
/opt/openmail/patch/filesets/OM-NIPPAW
/opt/openmail/patch/filesets/OM-PMOVER
/opt/openmail/patch/filesets/OM-POP3
/opt/openmail/patch/filesets/OM-PTBICE
/opt/openmail/patch/filesets/OM-PTBPAW
/opt/openmail/patch/filesets/OM-RC
/opt/openmail/patch/filesets/OM-SMS
/opt/openmail/patch/filesets/OM-SPAICE
/opt/openmail/patch/filesets/OM-SPAPAW
/opt/openmail/patch/filesets/OM-SWEICE
/opt/openmail/patch/filesets/OM-SWEPAW
/opt/openmail/patch/filesets/OM-UNIX
/opt/openmail/patch/filesets/OM-WEBADM
/opt/openmail/patch/filesets/OM-X400
/opt/openmail/patch/ompatch
/opt/openmail/patch/PHSS_24875/omunpatch
/opt/openmail/patch/PHSS_24875/ompatch.idx
what(1) Output:
/opt/openmail/patch/filesets/OM-ADM:
No what strings
/opt/openmail/patch/filesets/OM-AMECAT:
No what strings
/opt/openmail/patch/filesets/OM-AMEICE:
No what strings
/opt/openmail/patch/filesets/OM-AMEPAW:
No what strings
/opt/openmail/patch/filesets/OM-AMEPSS:
No what strings
/opt/openmail/patch/filesets/OM-APPL:
No what strings
/opt/openmail/patch/filesets/OM-BB:
No what strings
/opt/openmail/patch/filesets/OM-CHSICE:
No what strings
/opt/openmail/patch/filesets/OM-CHSPAW:
No what strings
/opt/openmail/patch/filesets/OM-CORE:
No what strings
/opt/openmail/patch/filesets/OM-DESK:
No what strings
/opt/openmail/patch/filesets/OM-DSYNC:
No what strings
/opt/openmail/patch/filesets/OM-ENGCAT:
No what strings
/opt/openmail/patch/filesets/OM-ENGICE:
No what strings
/opt/openmail/patch/filesets/OM-ENGPAW:
No what strings
/opt/openmail/patch/filesets/OM-ENGPSS:
No what strings
/opt/openmail/patch/filesets/OM-FINICE:
No what strings
/opt/openmail/patch/filesets/OM-FINPAW:
No what strings
/opt/openmail/patch/filesets/OM-FREICE:
No what strings
/opt/openmail/patch/filesets/OM-FREPAW:
No what strings
/opt/openmail/patch/filesets/OM-GERICE:
No what strings
/opt/openmail/patch/filesets/OM-GERPAW:
No what strings
/opt/openmail/patch/filesets/OM-IMAP4:
No what strings
/opt/openmail/patch/filesets/OM-ITAICE:
No what strings
/opt/openmail/patch/filesets/OM-ITAPAW:
No what strings
/opt/openmail/patch/filesets/OM-KORICE:
No what strings
/opt/openmail/patch/filesets/OM-KORPAW:
No what strings
/opt/openmail/patch/filesets/OM-LC:
No what strings
/opt/openmail/patch/filesets/OM-LDAP:
No what strings
/opt/openmail/patch/filesets/OM-MAN:
No what strings
/opt/openmail/patch/filesets/OM-NIPICE:
No what strings
/opt/openmail/patch/filesets/OM-NIPPAW:
No what strings
/opt/openmail/patch/filesets/OM-PMOVER:
No what strings
/opt/openmail/patch/filesets/OM-POP3:
No what strings
/opt/openmail/patch/filesets/OM-PTBICE:
No what strings
/opt/openmail/patch/filesets/OM-PTBPAW:
No what strings
/opt/openmail/patch/filesets/OM-RC:
No what strings
/opt/openmail/patch/filesets/OM-SMS:
No what strings
/opt/openmail/patch/filesets/OM-SPAICE:
No what strings
/opt/openmail/patch/filesets/OM-SPAPAW:
No what strings
/opt/openmail/patch/filesets/OM-SWEICE:
No what strings
/opt/openmail/patch/filesets/OM-SWEPAW:
No what strings
/opt/openmail/patch/filesets/OM-UNIX:
No what strings
/opt/openmail/patch/filesets/OM-WEBADM:
No what strings
/opt/openmail/patch/filesets/OM-X400:
No what strings
/opt/openmail/patch/ompatch:
$Header: sh_patch.gen /main/gr7_patch/2 2001/05/25 1
9:57:32 pl $
/opt/openmail/patch/PHSS_24875/omunpatch:
$Header: sh_unpat.gen,v
/opt/openmail/patch/PHSS_24875/ompatch.idx:
No what strings
cksum(1) Output:
2563010459 867870 /opt/openmail/patch/filesets/OM-ADM
123293032 217298 /opt/openmail/patch/filesets/OM-AMECAT
3527150296 11625 /opt/openmail/patch/filesets/OM-AMEICE
187311781 3002 /opt/openmail/patch/filesets/OM-AMEPAW
140089432 22204 /opt/openmail/patch/filesets/OM-AMEPSS
105824458 178043 /opt/openmail/patch/filesets/OM-APPL
3319223691 83447 /opt/openmail/patch/filesets/OM-BB
238726588 11569 /opt/openmail/patch/filesets/OM-CHSICE
2825477539 2985 /opt/openmail/patch/filesets/OM-CHSPAW
2894316148 11775686 /opt/openmail/patch/filesets/OM-CORE
2982144279 107753 /opt/openmail/patch/filesets/OM-DESK
799011246 174294 /opt/openmail/patch/filesets/OM-DSYNC
1674303856 217296 /opt/openmail/patch/filesets/OM-ENGCAT
3790901248 11602 /opt/openmail/patch/filesets/OM-ENGICE
2235330151 3005 /opt/openmail/patch/filesets/OM-ENGPAW
795982391 22201 /opt/openmail/patch/filesets/OM-ENGPSS
2755330426 11592 /opt/openmail/patch/filesets/OM-FINICE
2544443159 2995 /opt/openmail/patch/filesets/OM-FINPAW
2530289775 11568 /opt/openmail/patch/filesets/OM-FREICE
3584823076 3002 /opt/openmail/patch/filesets/OM-FREPAW
3281301337 11564 /opt/openmail/patch/filesets/OM-GERICE
2906193592 2997 /opt/openmail/patch/filesets/OM-GERPAW
966295597 82283 /opt/openmail/patch/filesets/OM-IMAP4
330946973 11595 /opt/openmail/patch/filesets/OM-ITAICE
4148776937 2994 /opt/openmail/patch/filesets/OM-ITAPAW
86296471 11541 /opt/openmail/patch/filesets/OM-KORICE
747298057 2990 /opt/openmail/patch/filesets/OM-KORPAW
4132779009 721406 /opt/openmail/patch/filesets/OM-LC
1996253070 84127 /opt/openmail/patch/filesets/OM-LDAP
3312224094 6906 /opt/openmail/patch/filesets/OM-MAN
3121064114 11616 /opt/openmail/patch/filesets/OM-NIPICE
1057547640 2987 /opt/openmail/patch/filesets/OM-NIPPAW
2222530952 63342 /opt/openmail/patch/filesets/OM-PMOVER
3112748287 24599 /opt/openmail/patch/filesets/OM-POP3
2242362813 11570 /opt/openmail/patch/filesets/OM-PTBICE
3086417870 2989 /opt/openmail/patch/filesets/OM-PTBPAW
1213499564 477008 /opt/openmail/patch/filesets/OM-RC
103652571 208071 /opt/openmail/patch/filesets/OM-SMS
2266880193 11595 /opt/openmail/patch/filesets/OM-SPAICE
675133638 2984 /opt/openmail/patch/filesets/OM-SPAPAW
1310431551 11607 /opt/openmail/patch/filesets/OM-SWEICE
2706322921 3006 /opt/openmail/patch/filesets/OM-SWEPAW
4241761766 129578 /opt/openmail/patch/filesets/OM-UNIX
1645463432 717023 /opt/openmail/patch/filesets/OM-WEBADM
2204386602 1020766 /opt/openmail/patch/filesets/OM-X400
839793273 26586 /opt/openmail/patch/ompatch
4120277454 11249 /opt/openmail/patch/PHSS_24875/omunpatch
245439138 87529 /opt/openmail/patch/PHSS_24875/ompatch.idx
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_23490
Equivalent Patches:
PHSS_24876:
s700: 11.00 11.04 11.11
s800: 11.00 11.04 11.11
PFSS_17032:
sparcSUN: 5.6 5.7 5.8
PASS_17032:
AIX: 4.3
PLSS_17036:
intelLinux: RedHat7.0
Patch Package Size: 17220 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_24875
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_24875.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_24875. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_24875.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_24875.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
SUBSYSTEM_SHUT
=================================================
PHSS_24875:
=================================================
CR: JAGad75038 SR: 8606205863
-------------------------------
Directory entries that have been affected by the defect
should be rewritten with the correct values.
A way to force the republishing the FreeBusy info.
is for the user to do the following in Outlook:
Tools/Options/Preferences tab
- Calendar Options
- FreeBusy Options
- Set publish <n> months... to 0 and hit OK
- FreeBusy Options
- Set publish <n> months... to what is was
before (eg 2) and hit OK
This will cause the FreeBusy info to be rewritten to the
server.
NOTE: OpenMail must be shutdown before installing
this patch.
----------------------------------------------------------
This patch will need the following minimum disk
space requirements:
/opt/openmail/patch : 60 MB
NOTE: ServiceGuard Installations will need twice
this amount.
----------------------------------------------------------
-----End of Document ID: PHSS_24875------------------------------------------
Document ID: PHSS_24873
Date Loaded: 20010905
Title: s700_800 10.X OpenMail B.06.00 September 01 Periodic Patch
Patch Name: PHSS_24873
Patch Description: s700_800 10.X OpenMail B.06.00 September 01 Periodic Patch
Creation Date: 01/08/22
Post Date: 01/09/05
Hardware Platforms - OS Releases:
s700: 10.20 10.24 10.30
s800: 10.20 10.24 10.30
Products:
OpenMail B.06.00
Filesets:
OpenMail.OM-ADM,B.06.00 OpenMail.OM-AMECAT,B.06.00
OpenMail.OM-AMEICE,B.06.00 OpenMail.OM-APPL,B.06.00
OpenMail.OM-BB,B.06.00 OpenMail.OM-CCMOB,B.06.00
OpenMail.OM-CHSCAT,B.06.00 OpenMail.OM-CHSICE,B.06.00
OpenMail.OM-CHSPSS,B.06.00 OpenMail.OM-CORE,B.06.00
OpenMail.OM-DESK,B.06.00 OpenMail.OM-DSYNC,B.06.00
OpenMail.OM-ENGCAT,B.06.00 OpenMail.OM-ENGICE,B.06.00
OpenMail.OM-FINCAT,B.06.00 OpenMail.OM-FINICE,B.06.00
OpenMail.OM-FRECAT,B.06.00 OpenMail.OM-FREICE,B.06.00
OpenMail.OM-GERCAT,B.06.00 OpenMail.OM-GERICE,B.06.00
OpenMail.OM-IMAP4,B.06.00 OpenMail.OM-ITACAT,B.06.00
OpenMail.OM-ITAICE,B.06.00 OpenMail.OM-KORCAT,B.06.00
OpenMail.OM-KORICE,B.06.00 OpenMail.OM-KORPSS,B.06.00
OpenMail.OM-LC,B.06.00 OpenMail.OM-LDAP,B.06.00
OpenMail.OM-MAN,B.06.00 OpenMail.OM-NIPCAT,B.06.00
OpenMail.OM-NIPICE,B.06.00 OpenMail.OM-NIPPSS,B.06.00
OpenMail.OM-NIPWEB,B.06.00 OpenMail.OM-NOTES,B.06.00
OpenMail.OM-PMOVER,B.06.00 OpenMail.OM-POP3,B.06.00
OpenMail.OM-PTBCAT,B.06.00 OpenMail.OM-PTBICE,B.06.00
OpenMail.OM-RC,B.06.00 OpenMail.OM-SMS,B.06.00
OpenMail.OM-SPACAT,B.06.00 OpenMail.OM-SPAICE,B.06.00
OpenMail.OM-SWECAT,B.06.00 OpenMail.OM-SWEICE,B.06.00
OpenMail.OM-UNIX,B.06.00 OpenMail.OM-X400,B.06.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_24873
Symptoms:
PHSS_24873:
CR: JAGad30137 SR: 8606160818
OpenMail B.06.00.00 + MayPP00
unix.in might hang and a message queued on the sendmail
queue when the message contains one part only, which is a
distribution list.
Workaround: Prior to sending the DL, add some text in the
body part of the message.
CR: JAGad31466 SR: 8606162150
One-way disrsync agreement between OpenMail and Exchange
(over OMEXCONN). Updates are done on the Exchange server.
When modifying attributes 111 and PHONE-1, then the next
dirsync results in the full loss of tis modified entry
within the OM directory. (However, the next dirsync cycle
will add the corrected entry again).
CR: JAGad65896 SR: 8606196695
HPUX 11.x - 10.x
Openmail 6.0 Dec '00 PP
The incoming internet gateway, unix.in, loops if supplied
with a bad RCPT_TO or Arpa ORN that contains more than one
sign.
For instance,
To:
_//org/co/admd/prmd////RFC-822/ppinetia.coma.b.c
CR: JAGad67601 SR: 8606198411
Message with a large distribution list (thousands of
recipients) can take a long, long time to pass through the
X.400 gateway (from OpenMail to X.400).
CR: JAGad68810 SR: 8606199624
omshowcda -d <dir_name> displays the mask used to extract
directory entries. The format of this mask changed with GR6
PP-Mar. It used to be:
S/G/I
and now it is:
S=/G=/I=
This will also occur for other directory related commands
that display attribute masks.
CR: JAGad69543 SR: 8606200362
Occasionally some message body parts, which require base 64
mime encoding, cause the item.browse binary to perform a
segmentation violation. This occurs when a user attempts to
read the message from the intray or folder area using an
IMAP client (Netscape communicator).
CR: JAGad70640 SR: 8606201464
Some scripts included in the OM-APPL component assume that
the 'cut' command is located in /usr/bin. In RedHat 7.1,
'cut' is located in /bin. The scripts affected are
omaddapp, omaddapppdl, omaddapppdln, omdelapp, omdelapppdl,
omdelapppdln, omshowapp, omshowapppdl and omshowapppdln.
CR: JAGad71090 SR: 8606201916
Web Client 6.0 may, under certain cirumstances, display the
incorrect item count when listing items in the tray areas
or the folder areas.
CR: JAGad73144 SR: 8606203966
Requesting virtual licences from other machines using GR6
Dec 2000 PP fails in some cases, and the license server may
abort. The failure happens when there is a decaying license
in the shadow file. omaudlic on the other machine shows
that the licences have been granted. The failure depends on
the order of entries within the shadow file, and therefore
appears to be intermittent. It does not seem to be related
to any one platform.
CR: JAGad74715 SR: 8606205540
This applies to B.06.00.00 and B.07.00.00
Use of ldapmodify to replace the mhsORAddress or omAddress
attributes does not work if attempting to replace existing
individual attributes, other than S, S-TX, G and G-TX.
For instance, if the entry for S=user111 has an OU1
configured, then
# ldapmodify -L UTF8-N -D "cn=clim, o=Openmail" -v
dn: cn=user111, o=OpenMail
changetype: modify
replace: mhsORAddresses
mhsORAddresses: S=user111/ou1=japan3
gives
ldap_modify: Operations error
ldap_modify: additional info: [OM 16092] An attribute has
multiple values, but is notconfigured as multi-value.
Parameter : Directory Entry Modifier
Attribute : OU1Max allowed size : 32
Required syntax : PRINTABLE-STRING
The error can also be seen on the server side, on the
omslapd debug output.
The recommended method is to use ldapmodify to modify the
individual attributes explicitly.
For instance, the input to ldapmodify would be
dn:...
changetype: modify
replace: 5
5: <new_OU1_value>
The internal names of the OU<n> attributes are used as they
are not mapped by default in the ~openmail/sys/ldap.attribs
file. Mappings could of course be added to this file, so
that more meaningful tags could be used in ldapmodify.
CR: JAGad75038 SR: 8606205863
Directory entries added using omaddent that contain
OCTET-STRING attributes have octets with certain values
stripped out. ommodent shows the same problem.
The FREEBUSY directory attributes used by Outlook FreeBusy
lookup are examples of OCTET-STRING data. A situation where
the FREEBUSY attributes may become incorrect is when
omdiropt is run on the FREEBUSY directory. This is because
omdiropt uses omaddent.
Octet \014 (14 decimal) is one value that gets stripped.
There may be some other values.
CR: JAGad75975 SR: 8606206802
The problem is with the way that sendmail converts the
address and OpenMail subsequently parses it.
If an entry has the format \", then sendmail quotes it and
adds an extra \ to the \" sequence.
So us\"er <user.local>, goes to "us\\"er" <user/local>,
Openmail then splits up the address list using commans as
the separator. If a separator is in a quote, it ignores it.
In the above example, the quote after the \\ is taken to be
a closing quote. This means that things get out of sync, as
the last quote is taken to be an opening, rather than
closing, quote and the address list becomes mangled.
In addition, the mangled address list may now contain
entries in excess of 1024 characters This can cause a fatal
error.
CR: JAGad79081 SR: 8606209895
Certain printable chars may be used in the components, e.g.
Surname, of OM Personal Names, but should be represented by
special characters on input (see man page omattribs). Such
a char is that 'space' should be input as '_' to allow for
Surnames like "Van Gogh".
IMAP makes no allowance for this mapping, and so fails to
login because the username as input does not exist as an OM
user.
PHSS_24094:
CR: JAGad40563 SR: 8606171299
The web clients do not work with HTTPS and the Apache web
server.
When the user tries to signon they are presented with the
following message:
Bad Request
Your browser sent a request that this server could not
understand.
Reason: You're speaking plain HTTP to an SSL-enabled server
port.
CR: JAGad44030 SR: 8606174784
Openmail does not have a converter from unicode to IA5, but
it does have one from unicode to ISO8859_1.
When the item browser is used to display a text message
using the default format, it has no problem in displaying
the message if OM_DEF_USER_CHAR is set to ISO8859_1 in the
configuration file.
However, if OM_DEF_USER_CHAR is set to IA5, then the item
browser isn't able to do the conversion and reports an
error. As the error reported in the log file was that a
character set conversion between MIME-UTF8 and IA5 was
failing, then this is probably the case.
The second problem is the way that the item browser
displays the message in MIME format.
Adding the mapping of UTF-8 to UTF8 in the mime.cs file
means that the character set for the message is now UTF8
which is recognised by OpenMail and the message is
correctly displayed on most clients. However, for Netscape
Messenger, which uses the item browser MIME option, there
is a problem.
The steering file ~sys/brwmime.str specified that generally
character sets should be converted to ISO8859_1 unless
otherwise specified. This means that the item browser
attempts a conversion from UTF8 to ISO8859_1 and fails.
It should be noted that UNICODE is not generally supported
on OpenMail when messages are in the MIME format.
CR: JAGad45881 SR: 8606176644
Omcontain aborts with a segmentation violation on LINUX,
when trying to delete a message attachment located in the
user's intray and results in the message attachment
remaining in the intray.
CR: JAGad46439 SR: 8606177205
For an OpenMail server that is configured to support
Czech...
Messages being sent from X400 with 1992 standard General
Text: context-specific 0 (23 octets):
GeneralString (21 octets):
1b 28 42 0f 1b 2d 42 1b 7e 31 31 31 31 b1 ea 32 32 32
. ( B . . - B . ~ 1 1 1 1 . . 2 2 2
are not correctly converted by the X400 In Mapper. They
should be converted to files of type 1736 with character
set T61BASE, and the data of the file should be consistent
with this.
CR: JAGad47890 SR: 8606178664
Some vir*ses can be flagged as being clean if the machine
on which they were scanned had been incorrectly configured
for scanning.
CR: JAGad48440 SR: 8606179216
8-bit text (e.g. German national chars) is displayed as
7-bit by IMAP clients, Netscape and Outlook Express.
CR: JAGad50818 SR: 8606181602
If a message is sent from a user who has an INTERNET_ADDR
defined, to another machine, e.g. via the SMINTFC gateway,
replies to that message do not get returned via the same
route - they always get returned via the INTERNET gateway.
This occurs when the receiving server does does not have
the user's INTERNET_ADDR defined in the directory, and when
the sending server is version GR7
CR: JAGad53837 SR: 8606184631
Large attachments (>30K) in forwarded messages are not
visible to Netscape IMAP client after moving from intray to
another folder.
CR: JAGad55411 SR: 8606186206
When shutting down the Remote Client Interface a
segmentation violation is occuring in the Notification
Monitor occasionally because of a buffer over-run or
under-run.
CR: JAGad56484 SR: 8606187277
The OpenMail delegate implementation does not include an
equivalent for Exchange's "Delegate can see my private
items" option (disabled by default in Exchange). Hence when
forwarding Meeting Requests no distinction is made between
Private items and others.
CR: JAGad56620 SR: 8606187413
Message delivery rulesets are not working with empty
subjects.
CR: JAGad57754 SR: 8606188546
omredirtcp logs errors "getsockname: Bad file number" when
no error has occurred.
CR: JAGad57988 SR: 8606188772
Messages containing ARPA Message Headers (e.g. Subject:)
with 8-bit text (e.g. German national chars) are displayed
in MIME source format by Netscape IMAP clients. This occurs
on the 2nd. and subsequent re- browse of the message. The
initial browse of the message is displayed correctly.
CR: JAGad58840 SR: 8606189626
MAPI addressbook download fails when trying to download a
directory whose first entry is a large entry such as a pdl
because a buffer overflow occurs.
CR: JAGad63387 SR: 8606194177
A coding defect while processing MIME data sometimes causes
a fatal error within the item.browse binary.
On the Netscape Client the user is presented with the
message:
"The current command did not succeed. The mail server
responded: Some of the requested messages no longer exist."
CR: JAGad64229 SR: 8606195023
Some of the OpenMail patch install scripts may use return
codes which are invalid in Software Distibutor (SD). In
addition, symbolic names such as $SUCCESS, $FAILURE and
$WARNING should be instead of 0, 1 and 2.
Some of the messages do not follow the conventions, with a
word such as ERROR in column 1 of the first line only, and
the text indented to column 10.
CR: JAGad64671 SR: 8606195467
When performing searches of large message stores if the
ual.remote associated with the in.imap41d terminates due to
inactivity or is deliberately killed then in.imap41d goes
into a spin. When using TOP or glance the in.imap41d
processes appear to be consuming a lot of CPU activity,
however, they will not impact on system performance
because the kernel will have assigned them a low priority.
PHSS_23342:
CR: JAGab33574 SR: 1653231704
OpenMail for Solaris's service router will abort if a
distribution list contains a blank name in it.
The following error is logged and can be seen using
omshowlog :
SERIOUS ERROR Service Router(Service Router)
09.04.97 [OM 10250] Process about to terminate due to
error. Signal (Segmentation Violation) trapped by process
4613; code = 0. Procedure trace follows:
< - da_GetAttribDefn
-> nm_GetFieldMemPtr
< - nm_GetFieldMemPtr
-> da_GetAttribDefn
-> da_GetMemAttribDefn
< - da_GetAttribDefn
-> nm_GetFieldMemPtr
< - nm_GetFieldMemPtr
-> da_GetAttribDefn
CR: JAGab39939 SR: 8606100957
Omfmtent -u creates output that is corrupted. This occures
when an attribute name is specified and the attribute value
is not. The format of the output is incorrect because it
lists the attribute name but assigns no value to it making
the output unusable in scripts.
ie:
Input to omfmtent :
s=kessler/i=c/g=richard/q=/ou1=hdqt
Output of omfmtent :
1=kessler/3=c/2=richard/4/5=hdqt
As you can see by the above example, the output from the
omfmtent command is missing an "=" after the 4.
CR: JAGab68963 SR: 8606102906
The new server feature of REPEAT REMINDERS in the OMGUI and
MOB GUI do not stop sending out reminders after the Expiry
date.
CR: JAGad24268 SR: 8606154951
omupdtis and associated commands sometimes report illegal
message store container references e.g.
~/sys/1000035/0000001:3
CR: JAGad31664 SR: 8606162348
Can't reply in OMGUI and ccMail to messages from internet
whose address has comments.
CR: JAGad35090 SR: 8606165799
If 2 OpenMail users have the same name (but different
mailnodes) Single User Restore sometimes selects the wrong
message store to be restored.
CR: JAGad41463 SR: 8606172203
The Application Link Layer component does not pass all the
basic acceptance tests on Solaris.
CR: JAGad41471 SR: 8606172211
The UAL sometimes aborts on Redhat 7.0 systems when using
the directory relay service, with the following in the
OpenMail log:
SERIOUS ERROR Remote Client (U/I Access) 11.30.00 07:47:57
[OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 28277;
code = 0. Procedure trace follows:
-> pc_recv_logical_block
<- pc_recv_logical_block
<- pc_recvmessage
-> ual_SendMessage
<- ual_SendMessage
-> ual_RecvReply
-> ual_GetFreeBusyTime
-> ual_ConvORNCheck
-> ual_ConvertORN
-> ual_GetUserCharSet
<- ual_GetUserCharSet
<- ual_ConvertORN
<- ual_ConvORNCheck
-> ual_GetUsersHost
-> nm_ParseORN
<- nm_ParseORN
User Name: UAL TestUser2 / Test, UAL
Pid of logging process: 28277
CR: JAGad41637 SR: 8606172377
Wrong user config file being used when accessing a delegate
mailbox.
CR: JAGad42631 SR: 8606173373
Openmail GR6 experiencing OM 1209 whenever omscan is run.
omscan logs errors in the log file which are nothing to
worry about and are normal behaviour. These errors should
be correctly trapped to avoid worrying administrators that
they may be a problem
CR: JAGad43052 SR: 8606173797
When a message with accented characters in the subject is
copied across message stores using Netscape messenger, the
subject of the message has the MIME character set specifier
in it when viewed using omcontain, OMGUI, Outlook. The
subject appears OK when using Netscape Messenger.
CR: JAGad43053 SR: 8606173798
When a message is copied from one message store to another
using Netscape Message, and an accented character exists in
it's content, then the message content file is corrupted.
However, the content of the message remains OK in the IMAP
index file. This means that the content can be viewed using
Netscape Message, but not when using OMGUI or Outlook.
CR: JAGad44810 SR: 8606175570
If a user has an address attribute with a backslash in,
then when the user's address is validated (checked) the
address attributes are displayed within the freeform field
(to:). If a backslash is present it prevents the message
being sent and displays the message "the user name is not
routable"
CR: JAGad45449 SR: 8606176209
Outlook OFS: Item created offline and synced, and then
modified offline but synced online causes a duplicate to be
created.
CR: JAGad45880 SR: 8606176642
The IMAP/item.browse aborts with a segmentation violation
on LINUX, when trying to encode an html attachment into
"Quoted-Printable" format.
CR: JAGad46896 SR: 8606177664
The OpenMail Internet gateway rejects multipart/signed
messages if one of its composite, multipart or message,
part's boundary-end markers is missing.
CR: JAGad48103 SR: 8606178878
If omprepsur is not able to salvage certain files, omdosur
is supposed to substitute some dummy containers instead and
then continue to create a valid omcpoutu archive. Infact,
omdosur was aborting straight after processing the missing
container and so was creating a corrupt omcpoutu archive.
CR: JAGad49581 SR: 8606180360
The original fix for JAGac29290 was missing two files:
i4target_ux10 and i4target_ux11. They should be included.
JAGac29290 added the ability to run OpenMail on systems
where the LSSERV component was not installed.
PHSS_23081:
CR: JAGad41842 SR: 8606172582
Outlook OFS: The UAL_GETSYNC extracts T.61 text content
files without performing any character set conversion on
them.
This affects Czech text that is synchronized and will also
affect Japanese, Korean and Chinese text.
CR: JAGad42033 SR: 8606172773
Itemed moved from Inbox whilst offline gets sync'ed twice:
Once when the MOVE is synced, and then again when the
folder is next synced.
CR: JAGad42115 SR: 8606172855
When 2 Outlook clients are connected to the same user
mailbox (eg. delegate and principal) there are occasions
when Calendar data is changed offline and the appointment
date emboldening is not updated for the online user after a
sync.
CR: JAGad42645 SR: 8606173387
They are occasions when the synchronization a folder
(typically the Inbox) will not pick up all of the newly
added messages.
This is most likely to occur on Inboxes with more than 32
items that have had items added and deleted since the last
synchronization. The items not sync'ed to the local Inbox
will be in a block starting with one delivered immediately
after the last sync.
CR: JAGad42878 SR: 8606173621
Message that is deleted completely on the server and
modified offline causes a sync. error when the folder is
next synced.
CR: JAGad44420 SR: 8606175176
Using Outlook OFS can cause spurious WARNINGs to be
reported in the OpenMail error log. Happens most frequently
when mailing messages that get saved to the Drafts folder
during message construction.
The warnings of the following type:
WARNING Remote Client (U/I Access )
01.04.01 11:11:35 [OM.UI 578] The Direct Reference supplied
is invalid User Name: JONATHAN GEORGE / HP-Pinewood, om1
-> ual_MatchSyncLogEntry
<- ual_MatchSyncLogEntry
-> ct_ofs_read
<- ct_ofs_read
-> ual_MatchSyncLogEntry
<- ual_MatchSyncLogEntry
-> ual_MatchSyncLogEntry
<- ual_MatchSyncLogEntry
-> ual_ListChangeLogAdd
-> ual_ResolveDirectRef
-> ct_FindDITEntryByRef
-> ct_DecodeDirectRef
<- ct_DecodeDirectRef
-> ct_FindDITEntry
<- ct_FindDITEntry
<- ct_FindDITEntryByRef
PHSS_22929:
CR: JAGad38822 SR: 8606169547
The Content Disposition and Content ID fields of a message
become corrupt when replying/forwarding using the Ccmail 6
client.
PHSS_22995:
CR: JAGad29260 SR: 8606159934
If a message coming in through the unix gateway, destined
for a Notes user, contains an empty From address in the
header section (HFrom: <>), omrouter non-delivers this
message and the following error messages are logged:
08/29/2000 12:39:11 PM OMRTR-GW1210: Failed to add entry
to text list.Entry : *NumCCRecips*Bad*
08/29/2000 12:39:11 PM OMRTR-GW2190: Sending Non-Delivery
Notification to ...
08/29/2000 12:39:11 PM OMRTR-GW2191: Successfully sent
Non-Delivery
PHSS_22990:
CR: JAGad42968 SR: 8606173711
It is possible using Outlook with a MAPI connection to
OpenMail to send a message with an internet address
containing 8-bit characters in the domain name.
The outgoing Internet Gateway discards these domain names,
causing an attempt to be made to deliver the message to a
recipient with the same address but no domain name.
This is not correct: if an address is invalid, message
delivery should not be attempted to a partial address in
this manner, as there are potential privacy issues.
PHSS_22699:
CR: JAGad21983 SR: 8606152653
The UXO_CHECK_TYPES_OF_DDA general.cfg configuration option
can be used to specify synonyms for the RFC-822 domain
defined attrubute type (DDT1).
However, for addresses which are NOT routed through the
internet gateway, those using DDT1=RFC-822 are treated
differently to those which use DDT1=<synonym for RFC-822>
For instance, assuming :
There is a route for "unix" through the internet gateway.
There is a route for "if" through the SendMail interface.
general.cfg contains these settings :
UXI_NAME_MAPPING=TRUE
UXO_NAME_MAPPING=TRUE
BRW_NAME_MAPPING=TRUE
UXO_CHECK_TYPES_OF_DDA=a,RFC-822,HPMEXT1,HPMEXT2,HPMEXT3,HP
EXT4
Then, the addresses are :
As entered Displayed in internet mailbox
a/unix(RFC-822|rm.cow) rm.cow
b/unix(a|rm.cow) rm.cow
c/if (RFC-822|rm.cow) rm.cow
d/if (a|rm.cow) d/if////////a/r#a#m#f#cowm.cow
There are arguments both ways for treating the addresses
routed through "if", however, the treatment should be
consistent.
CR: JAGad25146 SR: 8606155833
No way to specify aliases when creating many users with
'omaddu -bulk'.
CR: JAGad25316 SR: 8606156005
On an Ensim Linux machine.
When child processes terminate, they do not disappear
completely as expected, instead they become zombie
processes. These zombie processes are marked with <defunct>
when looking at process id information on a system.
This in turn can cause some processes, such as advmail.sckd
to hang using large amounts of system resource.
This will also cause problems when the system runs out of
available process ids because they are all tied up by
zombie processes.
CR: JAGad26547 SR: 8606157213
Subject and body of message generated for Japanese users
exceeding their message store limit should be in Japanese.
CR: JAGad27572 SR: 8606158242
According to RFC-1741 binhex file attachments should not be
encoded for transport. Item browser by default uses base64
encoding on binary files, with the result that the Eudora
client is unable to handle the binhex file attachment.
CR: JAGad28647 SR: 8606159318
Service Router takes a long time to stop (omoff -d 0 -s
router) and memory consumption is incrementing on heavily
loaded systems when vir*s ruleset is enabled
(ALL-ROUTER.VIR).
In fact each message that passes through service router
causes a loss of just over 1K of memory.
CR: JAGad28840 SR: 8606159513
Various inconsistencies have been identified in the code
within function definitions or calls, e.g. missing or extra
parameters or wrong type of parameter.
CR: JAGad29235 SR: 8606159909
Automatic filing of an incoming message to a folder by the
OpenMail auto-actions doesn't update the item count on the
Web Client folder page in the current session.
CR: JAGad29644 SR: 8606160320
The Service Router suffers from [OM 28874] errors when
processing certain messages from the SendMail interface
When doing filetype coercion on the binary attachment it is
reading past the end of file while trying to work out what
the file type is.
CR: JAGad29892 SR: 8606160571
Extensions to the UAL protocol required to support MAPI
Offline Folder Sync. development (OpenMail/MAPI B.06.00
release).
CR: JAGad31458 SR: 8606162142
Using OpenMail Graphical Interface version B.06.00.00 with
OpenMail B.06 and the client language set to GERMAN, it is
no longer possible to logon.
CR: JAGad31479 SR: 8606162163
On an Ensim machine, the IMAP server randomly drops socket
connections to the UAL giving the error message:
sock3/BYE: r {OpenMail IMAP Server not available}
CR: JAGad32112 SR: 8606162796
Netscape Messenger hangs during first access of a message
with a pathname containing backslash characters in the
content-type.
CR: JAGad33512 SR: 8606164212
The folder size is not updated in the Web Client 5.10
Filing Cabinet listing even after filing a few messages to
the folder. The user needs to logoff and re-login to view
the updated size.
CR: JAGad33773 SR: 8606164474
The OpenMail Internet gateway rejects multipart/signed
messages if one of the multipart boundary-end markers is
missing. Similarly, if such a message is encountered in the
OpenMail message store, the Item Browser may hang while
attempting to display the message.
CR: JAGad34214 SR: 8606164917
OpenMail GR6 + Oct00PP - Outlook Express (IMAP) fails to
download a message that contains a "special" character in
the friendly name. Special = ()"
CR: JAGad34502 SR: 8606165208
Under some circumstances moving or copying a message to the
Bulletin Board Area (rather than an individual BB) causes a
fatal UAL error: "The content record requested does not
exist in this container."
CR: JAGad34729 SR: 8606165435
The top line in the script is #!/bin/sh which does not
exist on machines running solaris.
CR: JAGad37344 SR: 8606168062
A new username that differs from an existing one in case
only (eg. "John deVere" as compared to "John Devere") was
not recognised as clashing, potentially resulting in more
than one user with the same name.
CR: JAGad37410 SR: 8606168129
omlicmon aborts when virtual licensing is used and OpenMail
is not omshut/omrc for long periods (months). Same issue
also would show up when not using virtual licensing, but
when the nodelock file is "touched" a lot.
omlicmon aborts with the following in omshowlog output:
SERIOUS ERROR Licence Monito(Licence Monito) 10.15.00
19:30:16 [OM 14460] Unexpected error in License monitor.
Group = 1; Reason = 24.
Error text follows :
Too many open files
SERIOUS ERROR Licence Monito(Licence Monito) 10.15.00
19:30:16 [SYS 24] Too many open files
File Name: OMDATADIR/temp/0ge23mu
-> lic_OpenShadowFile
<- lic_OpenShadowFile
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
<- im_CrNewTempItem
-> lic_ListShadowFile
<- lic_ListShadowFile
-> lic_CloseShadowFile
<- lic_CloseShadowFile
-> lic_OpenShadowFile
<- lic_OpenShadowFile
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
CR: JAGad37711 SR: 8606168431
The OpenMail notif.mon program does not output entry and
exit procedure-level trace to the omshowlog log files.
PHSS_22457:
CR: JAGad30987 SR: 8606161671
OpenMail support required for MAPI Offline Folder Sync. EEP
PHSS_22361:
CR: JAGab84570 SR: 8606112256
Randomly lost BB ACL flag, causes ACLs to be relaxed on BBs.
CR: JAGad05041 SR: 8606135910
Even if the UAL_MSTORE_SIZE_LIMIT is specified and
UAL_SIZE_MSG_TO_ENU is set to TRUE in the user's
configuration file, when this user's message store size
exceeds limit, no message is sent to the ENU to notify this
fact.
CR: JAGad05207 SR: 8606136077
Multibyte subject of warning message for mbox exceeding the
size limit is garbled when viewed with IMAP4 and POP3
clients.
CR: JAGad11128 SR: 8606141768
omcpinu fails to restore mailboxes with the error
"[OM.PM 1004] Internal problem detected, see the log files"
CR: JAGad13619 SR: 8606144279
Unix gateway aborts when certain messages are being sent
out. These messages originate from the cc:Mail client and
have an invalid CONTENT_FILE record, containing
miscellaneous text from the message in the
CONTENT-DISPOSITION field.
CR: JAGad14574 SR: 8606145237
When a tray is accessed by an IMAP client, a sequence number
is assigned to each item.
omcpinu does not assign unique sequence numbers to items
which it copies into a user's message store. This means that
IMAP clients, e.g. Netscape Messager, can become confused
and fail to display all items in the user's tray.
CR: JAGad15232 SR: 8606145896
Multiple OM 16130 errors get logged to the fatal log file
when a Japanese OMGUI client is used to print a message via
the OpenMail server.
CR: JAGad15339 SR: 8606146003
If an address has the i-tx field and using address mapping
format 3 then the address comes out as
name.i*i.surnamexxx.yyy.zzz
CR: JAGad21220 SR: 8606151881
Following ServiceGuard Failover, omrc sometimes exits with
the following error:
"omrc : There are still ual.remote/ual.local
processes running from a previous OpenMail start-up.
If you wish to restart OpenMail cleanly,
run omshut or wait for the following
processes to terminate, then run omrc:
Active Session PID:"
CR: JAGad21785 SR: 8606152455
The format of sendmail.cf has changed for Sendmail 8.10.
OpenMail needs to be able to configure this file during
installation.
CR: JAGad21810 SR: 8606152480
OpenMail gets compilation errors when built with RedHat 6.3.
CR: JAGad23468 SR: 8606154150
If you install Openmail B.06 on a Linux machine e.g. using
"rpm -i" and then remove it e.g. using "rpm -e" a lot of
files get left on the machine.
CR: JAGad23509 SR: 8606154191
Linux RedHat 6.3 ships xinetd instead of inetd. This means
that during OpenMail installation the openmailpxy and ccmtp
services are not set up correctly.
CR: JAGad23675 SR: 8606154357
unix.in process terminates with bus error when processing a
TNEF attachment.
CR: JAGad23678 SR: 8606154360
Message "The server responded: Cannot append that message"
is displayed when trying to move a message from the (local)
"Sent Items" folder to an OpenMail folder using Outlook.
If UAL tracing is switched on, the problem seems to be in
the UAL include file command processing :
INCLUDE FILE Command: Flags=0x20001,
File='OMDATADIR/user/u000091/TMPA22529/02rbts9'
INCLUDE FILE Command: MsgRef=0, DirectRef=000fdda33baa2e12,
ToCode=0, FromCode=0 CharSet=iso-8859-1
INCLUDE FILE Command: Subject = ''
INCLUDE FILE Command: Creator = ''
INCLUDE FILE Reply : NewItemRef=0, NewAbsRef=0, DirectRef=,
Error Text =''
**** REPLY Error Number = 1502 Group = 0, Reason = 0
GET ERROR MSG Command: ErrNo=1502, ErrNoExtra1=0,
ErrNoExtra2=0 GET ERROR MSG Reply: ErrorText1:
Requested conversion is not available on this system
GET ERROR MSG Reply: ErrorText2:
CR: JAGad24043 SR: 8606154726
Certain types of non-delivery notification from OpenDesk
(such as when a message is sent to an invalid OpenDesk
mailnode) do not have the correct Ack ID, after the OpenMail
Desk gateway has processed it. If the original message came
in via X400, then this problem can lead to the OpenMail X400
gateway rejecting the NDN because the ACK ID does not
contain the original CAP (Country, Admin Domain and Private
Domain) information.
CR: JAGad25016 SR: 8606155703
RedHat's rpmlint reports lots of errors regarding the
openmail rpm packages. The number of these errors needs to
be reduced.
CR: JAGad27743 SR: 8606158413
If the general.cfg setting :
MDC_DDS_DELETE_DATA=TRUE
is active, then messages browsed using IMAP
clients appear to be blank.
PHSS_21944:
CR: JAGab33837 SR: 1653262501
If a recepient name in the DL is ambiguous while sending a
message or while checking DL names from the Web Client 5.10,
the list of alternate names is always sorted on the default
sorting order even if an alternate sorting order has been
specified in the profile file (using the tag
DL-ALT-NAME-SORT).
CR: JAGab63204 SR: 8606101643
This is an interoperability problem and an ER for Web
Clients.
When the Web Client attaches a local file, the file name is
not displayed correctly on Internet clients (Outlook Express
in IE4).
The worst situation occurs when a BINARY file is attached
(e.g., BMP). The filename is lost and, because it is a
binary, OE will display the item's filename as something
like ATT00225.dat. It is almost impossible to open such item
because both the filetype and filename extension are
unknown.
Happens for both Web Client 5.10 and Web Client 6.0.
CR: JAGab72994 SR: 8606105114
IMAP clients are unable to view attachments of messages
which have no body parts (i.e. the message is only an
attachment).
CR: JAGac29290 SR: 8606114526
It should be possible to install and run OpenMail on HP-UX
systems where the LSSERV components have not been installed.
This already works on Solaris and Linux.
CR: JAGad00687 SR: 8606131537
While viewing the auto-answer text in PAW using IE, line
breaks are getting removed and the entire text is appearing
in a single line. This problem does not occur on Netscape.
In addition, the column size of the auto-answer text box
should be increased to 72-80 characters so that the
cut/paste operation from clipboard will be easier. The
current column size is 40.
CR: JAGad01673 SR: 8606132524
The background search process fails to do a search on the
contents of a note.
CR: JAGad01880 SR: 8606132732
The unix gateway fails to parse certain incoming messages
containing Delivery Status Notification reports.
CR: JAGad02855 SR: 8606133711
Desk Gateway socket handler (desksock.recv) could sometimes
abort with an ENOBUFS error, if memory is short on the
machine.
CR: JAGad03000 SR: 8606133860
If an attempt is made to update the 000002k file (which
holds Outlook delegate information) by using tfbrowse to
convert this to a textual representation, edit the textual
representation and then convert it back to transaction file
format, corruption takes place.
For instance, if the name "Outlook Delegate/local" is the
name of the delegate and this process is undergone without
any edits, after replacing the 000002k file with the new
file, the Delegates tab under Tools,Options shows
"Delegate/Outlook///local" where before it showed "Outlook
Delegate".
CR: JAGad03146 SR: 8606134007
Login problem with Web Client 6.0.
CR: JAGad03894 SR: 8606134759
omlimits warning messages are not delivered to a user's
mailbox when the mailbox size has been exceeded. The problem
is specific to users who are using a different language
setting to the openmail server.
CR: JAGad04005 SR: 8606134871
Japanese cc:Mail Mobile users has a reply problem when the
original message is created by Outlook + MAPI.
CR: JAGad04018 SR: 8606134884
With the general.cfg option :
BRW_NAME_MAPPING=TRUE
enabled.
The name mapping behaviour is not applied to "Return-Path:"
lines for messages originating within the OpenMail network.
For instance, if the OpenMail user "auser/local" had an
internet address mapping of "auserlaza.not.hp.com", then a
message from this OpenMail user will contain the following
lines when browsed using an IMAP or POP3 client :
Return-Path: <auser/locallaza.not.hp.com>
From: auserlaza.not.hp.com
CR: JAGad05750 SR: 8606136626
Problems decoding UTF7 for non-ASCII folder names in IMAP
client
CR: JAGad06793 SR: 8606137667
When submitting messages via the SMS2000 X25 protocol, the
originator sometimes got back an NDN with the following
error text:
'Message unable to be mapped at gateway' [OM 9400]
Supplementary Information:
(SMS) SMS2000: Operation rejected because argument
value(s) missing or invalid. [Result = 1]
In all cases that were investigated, the recipient had
infact received the SMS message, so the NDN was very
misleading. Also, when this happened, the recipient would
sometimes receive the message two or three times.
CR: JAGad07023 SR: 8606137874
Opendesk Gateway (outgoing) sometimes aborts, when trying to
map the ACK database file into memory.
CR: JAGad07491 SR: 8606138290
Attachment descriptions of file attachment are corrupted
when accessing a B.06.00 OpenMail server using
WinOMGUI-J or the ICE-NIPPON web client profile.
The filecode is displayed instead of the file description.
The display in WinOMGUI-J looks something like :
KONO KOMOKU NO TAIPU HA p. (2147) DE
TEKISUTOTOSHITE..DEKIMASEN
Where capitals represent Japanese Katakana/Hiragana
characters.
CR: JAGad08966 SR: 8606139655
The Mime internet gateway does not recognise fred.txt.vbs as
being of type "vbs". The extension after the final dot
should be used when determining the type of a file
CR: JAGad11000 SR: 8606141637
In certain network environments, since the changes to the
UAL file transfer protocol made in the February 2000
periodic patches, some UAL sessions could disconnect or hang
when sending messages.
CR: JAGad11143 SR: 8606141783
With the genearal.cfg tweak SR_FILTER_TYPES_OF_ATT=2188
set,the vbs attachment name is deleted but not the
Content-Disposition header from the vbs attachment.
CR: JAGad12244 SR: 8606142895
An extension of the UAL_GETFIL command is required to allow
a client to obtain the name of a server file that contains
the settings for the parameters to the Outlook secur*ty
patch. These settings must configurable on both a system and
per user basis.
CR: JAGad12543 SR: 8606143206
The portal daemon dies if the tweak UAL_SINGLE_TEMP_DIR has
been specified in the general.cfg file and a hostname lookup
request with a new character set is received from a Web
Client 6.0 session.
CR: JAGad12554 SR: 8606143218
If an ACL is created for a Request Server Script, and a user
with a space character in its mailnode name is added to that
ACL with execute permissions, any request made by that user
to that script fails. The user should be able to access the
script if they have been added to the ACL with the
appropriate permissions.
CR: JAGad21211 SR: 8606151872
Cannot back-out Feb00 or May00 Periodic patches, to a
pre-Feb00 version. omunpatch would report errors of the
following form:
ld.so.1: omeval: fatal: relocation error: file
OMBINDIR/lib/libom_nfda.so: symbol
er_ErrorInfo: referenced symbol not found
Note, backing out from May00 to Feb00 is OK.
PHSS_21439:
CR: JAGab32379 SR: 1653240259
Unix gateway aborts with OM-UX 1131 if DDV1 address
has multibyte characters
CR: JAGab32452 SR: 5003366708
Event logging in all areas of SMS is poor.
CR: JAGab32488 SR: 5003454405
Messages sent with precedence bulk, junk, or list receive
many autoreply messages back (when recipients switch on the
autoreply) which is unnecessary.
CR: JAGab33999 SR: 1653285569
Missing CREATOR rec. from Del. Envelope causes X400 to
non-deliver msg.
CR: JAGab34077 SR: 1653296350
Acks are not being re-routed when the SR_RESOLVE_MASK
general.cfg option is set.
CR: JAGab34096 SR: 1653298653
When using a PDL within another PDL, the PDL can end up
pointing at itself as its parent
CR: JAGab34157 SR: 1653306589
omscan when run in fix mode (omscan -a -f) removes
"lost+found" directories, making fsck impossible
CR: JAGab34186 SR: 1653310714
OpenMail does not deliver incoming internet messages
correctly when there are whitespaces around the "=" in a
MIME Parameter in the qf file, e.g.
'HContent-Type: Multipart/mixed; boundary = "123456789"'
(Note the spaces around the '=').
On a SUN/Solaris server the messsage is rejected with an [OM
10250] error. On a HP-UX server, the message is delivered,
but without the bodyparts.
CR: JAGab34785 SR: 5003465195
Openmail GUI 6.0 allows users to send Repeat Reminder
messages, under some circunstances, the messages disappear
completely from the client's Out box, eventhough, the
messages are still being sent out as scheduled.
CR: JAGab34850 SR: D500253328
Some general.cfg values could contain charset names that
include an underscore. For instance at incoming Desk and
UNIX gateways.
But general.cfg disallows use of underscore, or replaces it
with space maybe. As a result,
the above gateways do not work for such character sets.
CR: JAGab74208 SR: 8606105866
On GR6 create a message and send it to yourself using
Outlook. Using omcontain check that the Inbox and Sent Items
(Pending Tray) copies of the message have an object file
(MAPI.ObjectProperties).
omcpoutu the user, delete the user, re-add the user, omcpinu
the user.
Now use omcontain to check the message object file - it's
gone!
CR: JAGab74694 SR: 8606105948
ORNs in text version of tf with no '/' are lost by tfbrowse
-g
CR: JAGab76033 SR: 8606106702
Local Delivery aborts when File in ~openmail/data is
missing.
CR: JAGab76643 SR: 8606107035
If the UAL monitor makes 3 unsuccessful consecutive attempts
to connect, then it is terminated. There is no delay between
these attempts and resulting termination means that the
monitor has to be restarted before any further requests can
be handled.
A tweek, allowing a time delay between attempts to connect,
and further additional attempts before failing, would mean
that this problem was less likely to happen.
CR: JAGab78064 SR: 8606107773
Items containing more than one 'Content-Disposition' lines
for an item can cause IMAP4 clients to hang when trying to
browse the item.
CR: JAGab78752 SR: 8606108351
Local delivery fails with a bus error, reporting the
following trace when the LD_AUTOREPLY_CHECK_ON is set and
multiple Local Deliveries are in operation.
SERIOUS ERROR Local Delivery(Local Delivery)
10.28.99 10:36:09 [OM 10250] Process about to terminate due
to error. Signal (Bus Error) trapped by process 6957; code =
0. Procedure trace follows:
<- tf_GetINT32
-> tf_MarkPrevRecord
<- tf_MarkPrevRecord
-> tf_GetINT32
<- tf_GetINT32
-> tf_GetINT32
<- tf_GetINT32
-> tf_ReadRecord
<- tf_ReadRecord
-> tf_GetINT16
<- tf_GetINT16
-> tf_GetINT32
<- tf_GetINT32
-> ld_AAReplyAlreadySent
-> im_ItemRef2FName
<- im_ItemRef2FName
CR: JAGab82030 SR: 8606109330
cc:Mail Mobile 6.22 OpenMail edition cannot reply to
messages which contain RTF files. When an attempt is made
to reply to the message, the original RTF text is displayed,
however, no modifications can be made to it.
Items which have original filenames (created by Outlook
clients) were being treated as file attachments regardless
of whether they had actually now been converted to text.
CR: JAGab82546 SR: 8606109847
The problem occurs when a quoted-printable subject field of
a message containing multiple 8-bit characters separated by
a '?' character is received at the unix gateway. Only the
8-bit characters before the '?' are decoded correctly.
CR: JAGab84515 SR: 8606112206
Japanese messages which are stored in a folder on the server
using IMAP4 are not readable from other standard OpenMail
clients.
CR: JAGab84577 SR: 8606112263
Serialised file handles are not free'd after container
compaction has occured. This can cause Local Delivery to
abort when it runs out of file handles. The following error
is generated: [OM 28870] "To many serialised items open".
CR: JAGac29346 SR: 8606114582
omcheck -i does not work on Linux, for filesets where the
check data file is less than 8K in size (e.g. everything
except the OM-CORE fileset).
CR: JAGac29459 SR: 8606114696
MIME Content disposition still has filename under some
conditions when it need not. This causes problems for some
clients (mostly MS ones)
Also, Content-Dispositions are mixed. For example, a
multipart alternative body part has the first alternative
marked as inline and the other as an attachment when they
should both be inline or attachments.
CR: JAGac39658 SR: 8606124275
The unix gateway crashes when receiving certain incoming
messages. The message is not delivered and no non-delivery
acknowledgement is returned.
CR: JAGac40185 SR: 8606124793
There are particular messages that arrive through the
internet(mime) gateway that causes "Outlook" to lose
connection upon reading the folder where they are located
in.
With "omgui" there is no problem is accessing/reading the
folder/msg.
Outlook's error-message when opening the folder with the
problem msg in:
UAL Network Error:
Failed to send data. The connection may have been lost.
Software caused connection reset.
Connection Type: Windows Sockets
The ual.remote session aborted on the server; in omshowlog
you'll find:
SERIOUS ERROR Remote Client (U/I Access ) 12.30.99
08:16:58 [OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 22383;
code = 0. Procedure trace follows:
-> ual_IsMappingAvail
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- ual_IsMappingAvail
-> ual_IsMappingAvail
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- ual_IsMappingAvail
User Name: kinderkanal / hppine83, 01>!]
CR: JAGac40230 SR: 8606124838
The unix gateway truncates the incoming UUENCODED attachment
file name at the first space.
CR: JAGac42791 SR: 8606125848
omdbmon sometimes aborts with SYS:22 error
CR: JAGac78718 SR: 8606127917
ccmobile users cannot reply to Microsoft RTF messages.
Even with ConvertToRTF=1 set in ccmtp.ini, the reply is
virtually illegible to the Outlook user as the standard
cc:mail reply colours of yellow text on a blue background
become yellow text on a white background.
CR: JAGac79005 SR: 8606128205
The checks introduced by JAGab33916 to detect whether
an X400 user is infact local, did not work with non-delivery
rulesets
CR: JAGac86611 SR: 8606129065
item.browse sometimes aborts when processing a msg with
multibyte attachment.
CR: JAGac86632 SR: 8606129086
ualth doesn't always detect new messages arriving in
intrays.
CR: JAGac86756 SR: 8606129210
omaddu without options causes segmentation violation on
Solaris & Linux systems (GR6+Feb2000 PP)
When omaddu is executed with invalid arguments, the usage
strings are printed in a different way on Linux & Solaris &
are in improper format. On Linux, some garbage charecters
appear in the Usage string. On Solaris, each usage string is
printed twice.
CR: JAGac86786 SR: 8606129240
Segmentation Violation in test viral scanning library.
CR: JAGac86878 SR: 8606129332
Dirsync impacts client directory access significantly
CR: JAGac87789 SR: 8606129454
The directory synchronisation program does not modify the
slave directory entry correctly when attributes have been
removed (deleted) from the master directory entry.
Note:
This problem only occurs when the 'omresyncds' command is
used to trigger a directory resynchronisation.
The normal directory resynchronisation does not exhibit this
problem.
CR: JAGac87845 SR: 8606129510
This is an enhancement. Mobile devices do not understand
HTML and they do not support Javascript and Frames, hence a
new profile is required for connecting to OpenMail from such
devices.
CR: JAGac87847 SR: 8606129512
When OpenMail is installed, certain directories such as /etc
are left with the wrong permissions. Sendmail 8.9 is very
strict about permissions and it will issue a large number of
error messages; it may even stop delivering the mail
altogether. OpenMail does not warn the user about this
problem. omrc should issue a warning when the permissions
are wrong.
CR: JAGac87851 SR: 8606129516
Web Client profile selection page is not accepting the HTTPS
protocol in the URL
CR: JAGac88829 SR: 8606129914
The November 1999 and February 2000 B.06.00 periodic patches
incorrectly documented the default value for the
general.cfg setting UXO_ITEMSUB_IS_FNAME as being TRUE.
CR: JAGac95131 SR: 8606130260
When a message enters OpenMail through the internet gateway,
the comments that are on an smtp address are lost. And
consequently, they cannot be displayed when the message is
read.
For example, the sender:
"John A. Smith" <103343.1432compuserve.com>
is saved as
<103343.1432compuserve.com>
CR: JAGac95600 SR: 8606130710
in.imap41d crashes when attempting to accept a client
connection (on an already busy machine with many clients
connected).
CR: JAGad00184 SR: 8606131026
Missing system shared library is causing webselect.cgi to
abort when it is accessed in a VirtualVault environment.
CR: JAGad00185 SR: 8606131027
The portal daemon uses a default value of 3 for the number
&nb