|
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 Nov 04 2001 - 07:47:34 CST
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 Nov 4 3:05:03 PST 2001
Table of Contents:
Document ID Title
--------------- -----------
PHSS_24986 s700_800 10.20 OV OB4.00 patch - SSEA packet
PHSS_24984 s700_800 10.20 OV OB4.00 patch - EMC packet
PHSS_25471 s700_800 10.20 OV ITO6.0X NT Agent Patch A.06.09
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_24986
Date Loaded: 20011031
Title: s700_800 10.20 OV OB4.00 patch - SSEA packet
Patch Name: PHSS_24986
Patch Description: s700_800 10.20 OV OB4.00 patch - SSEA packet
Creation Date: 01/10/29
Post Date: 01/10/31
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OmniBackII A.04.00
Filesets:
OMNIBACK-II.OMNI-SSEA-P,A.04.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_24986
Symptoms:
PHSS_24986:
Id = HSLco27782, SR: H555005757
SSEA Integration backup fails with an error:
"[Major] From: SSEA<hostname> "" Time: <time>
File system <path> could not be mounted
to <path>. ([16] Device busy).
Id = HSLco28452, SR: H555006026
SSEA Integration backup fails with an error:
"[Major] From: SSEA<hostname> "" Time: <time>
Volume group /dev/<vg-name> could not be
activated.
Id = NSMex04611, SR: H555006245
SSEA Integration backup fails with an error:
"[Critical] From: SSEA<hostname> "" Time:<time>
Unexpected close reading message from the agent
on the Backup System. (Unknown internal error.)
Defect Description:
PHSS_24986:
Id = HSLco27782
Session fails when backup system is left enabled,
SSEA_PRESERVE_MOUNTPOINTS is set to 1 in .omnirc
file and backup is restarted.
Resolution:
Mountpoint is rechecked becouse it can change.
Id = HSLco28452
If the volume group is located in a cluster on the
application side, it is not possible to activate
this volume group in "rw" mode on the backup side.
Resolution:
By default volume group on the backup side is activated
in read only mode, unless the "Enable the backup system
in read/write mode" option is set for the backup.
Id = NSMex04611
Because of the large number of backup volumes agent and
backup session manager lost connection to the ssea on
the application side in the middle of resolve function.
Resolution:
Buffer concatenation is fixed.
Part of SSPUX400_004.
SR:
H555006245 H555006026 H555005757
Patch Files:
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.04.00/
packet.Z
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.04.00/
packet.Z
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.04.00/
packet.Z
what(1) Output:
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.04.00/
packet.Z:
None
cksum(1) Output:
2289704829 472427 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-1020/A.04.00/packet.Z
947304901 472697 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-11/A.04.00/packet.Z
2494510309 220271 /opt/omni/databases/vendor/ssea/sun/sparc/
solaris-7/A.04.00/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_24987:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 1200 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_24986
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_24986.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_24986. 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_24986.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_24986.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_24986:
NOTE!
This patch has to be installed on the Installation
Server host.
The OB2 SSEA agent must be redistributed to the SSEA
client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the SSEA agent, refer to
the OmniBackII Installation guide.
Patch includes the following Site Specific Patches:
SSPUX400_004
-----End of Document ID: PHSS_24986------------------------------------------
Document ID: PHSS_24984
Date Loaded: 20011030
Title: s700_800 10.20 OV OB4.00 patch - EMC packet
Patch Name: PHSS_24984
Patch Description: s700_800 10.20 OV OB4.00 patch - EMC packet
Creation Date: 01/10/29
Post Date: 01/10/30
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OmniBackII A.04.00
Filesets:
OMNIBACK-II.OMNI-EMC-P,A.04.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_24984
Symptoms:
PHSS_24984:
Id = HSLco27761, SR: H555005750
Restore fails with an error:
"[Major] From: SYMA<hostname> "" Time:<time>
[223:125] Resolving of object /sg_sap has failed.
(None of backup host resolved object.)"
Id = NSMex04505, SR: H555006043
Restore fails with an error:
"[Minor] From: VRDA<hostname> "SAP" Time:<time>
/oracle/R3E/sapdata2/el46bd_2/el46bd.data2
Can not open: ([30] Read-only file system)
=> not restored."
Defect Description:
PHSS_24984:
Id = HSLco27761
If you select more then 3 SAP files for restore using
split-mirror, backup fails.
Resolution:
An additional check is made to see whether the object
is in SYMA_OS_EXCLUDE state.
Id = NSMex04505
During the restore some file systems are mounted as
read-only, so the restore fails.
Resolution:
An additional condition is set for enabling the
read-only mode.
SR:
H555005750 H555006043
Patch Files:
/opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.04.00/
packet.Z
/opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.04.00/
packet.Z
what(1) Output:
/opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.04.00/
packet.Z:
None
/opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.04.00/
packet.Z:
None
cksum(1) Output:
2452691019 525401 /opt/omni/databases/vendor/emc/hp/s800/
hp-ux-1020/A.04.00/packet.Z
2245563753 525616 /opt/omni/databases/vendor/emc/hp/s800/
hp-ux-11/A.04.00/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_24985:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 1080 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_24984
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_24984.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_24984. 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_24984.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_24984.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_24984:
NOTE!
This patch has to be installed on the Installation
Server host.
The OB2 EMC agent must be redistributed to the EMC
client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the EMC agent, refer to the OmniBackII
Installation guide.
-----End of Document ID: PHSS_24984------------------------------------------
Document ID: PHSS_25471
Date Loaded: 20011029
Title: s700_800 10.20 OV ITO6.0X NT Agent Patch A.06.09
Patch Name: PHSS_25471
Patch Description: s700_800 10.20 OV ITO6.0X NT Agent Patch A.06.09
Creation Date: 01/10/25
Post Date: 01/10/29
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OpenView IT/Operations 6.0
Filesets:
OVOPC-CLT.OVOPC-NT-CLT,A.06.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25471
Symptoms:
PHSS_25471:
- SR: B555008220
The <$MSG_TIME_CREATED> variable is not substituted in
the message template.
- SR: B555010899
opcdista requests distribution data from a wrong manager
if there is a secondary manager with the same short
hostname than the appropriate primary manager.
- SR: B555011979
Pattern matching hangs if only single byte Japanese
HANKAKU KANA characters are used.
- SR: B555011990
ECS event log (ecevilg) has invalid time difference to
the next message which can cause the ECS simulator
to hang or appear to hang when loading an event log file
with such values.
- SR: 8606179902
During (de)installation of the NT agent
the installation might abort with error messages
saying that it can't remove libopc.dll or opcapi.dll.
This can occur when you have installed VP-IS.
- SR: 8606205415
opcsetup might report an error during manual NT agent
installation when the value for [Setup Drive] contains
trailing spaces in opcsetup.inf.
- SR: 8606206616
opcntprocs.exe or itoprocs.exe may hang on the agent
system, therefore the process monitoring will fail.
- SR: 8606208283
The NT user privilege "Increase Quota" needs to be
assigned to the 'HP ITO account', which is not done
during the agent installation. If this is missing, the
agent may not be able to perform a full user switch with
password to a different account. This could result in
problems when executing tools or scheduled commands on
the managed node that require full network access.
- SR: 8606212295
The agent deployment/installation on a Windows NT/2000
node might fail, because files are locked or agent
processes can't be stopped.
- SR: 8606213476
The distribution to nodes may hang or fail. This is more
likely to happen while distributing to Windows NT/2000
nodes rather than on UNIX nodes. On Windows NT/Windows
2000 nodes the control agent may produces a Dr. Watson
error.
- SR: B555009193
VBscript.dll delivered with Windows NT/ Windows 2000
VPO/VPW agent has wrong version and doesn't work with the
Script Engine of VPO/VPW
- SR: B555009481
The process monitor itoprocs.exe/opcntprocs.exe doesn't
report correct values with the first call when the
process name is longer than 15 characters.
- SR: B555009745
The template default of the object field of a monitor
template is not used.
- SR: B555010038
After installing SPI templates (e.g. DB SPI) and then
after reinstalling the agent, the agent may not find
commands.
- SR: B555010620
Some messages are missing in the Japanese message
catalog. You get a Cannot generate message error.
- SR: B555010819
opcsetup aborts in case the opcsetup.inf file
has unix ascii format, the problem are the different
line ends between UNIX and Windows.
- SR: B555010879
opctrapi aborts during template distribution if
conditions with the 'Suppress Identical Output Messages'
features are used
- SR: B555010948
Nested alternatives were not handled correctly in the
pattern matching algorithm, e.g. the pattern '[a|b]c|d'
was handled like '[a|b|d]c'.
- SR: B555010980
Traps without a SNMP variable are not matched because
server patch adds an extra attribute to the template.
- SR: B555011256
The agent process opcle.exe may crash on Windows 2000
nodes while monitoring the new event logs coming with
Windows 2000.
- SR: B555011422
opcragt/opcagt -stop and opcagt -kill might fail
when a subagent process can't be killed or stopped
- SR: B555011436
When monitoring real time performance data with the
Windows NT/Windows 2000 agent, there may be a number of
"Perflib" messages created in the application event log.
These "Perflib" messages will occur when you don't want
to monitor the object the messages are created by. On
some systems it may happen that OvNtDiag.exe/itodiag.exe
hangs while retrieving system information.
- SR: B555011497
Trap interceptor aborts after reboot - can't open SNMP
session
- SR: B555011510
opcle might create a DrWatson when the path to an Event
log message (usually a DLL) on Windows NT/Windows 2000 is
divisible by four.
- SR: B555011540
The VPW agent installation is not aware of existing VPO
and ITO installations, and the VPO agent installation is
not aware of existing VPW installations. The old agent
binaries installed by the other OpenView management
software (VPO/VPW/ITO) are not removed from the system.
- SR: B555011594
The original message text of a logfile encapsulator
message is wrong if <$LOGPATH> or <$LOGFILE> is used.
- SR: R555011075
The control agent aborts when calling 'opctemplate -d -
all'.
PHSS_24050:
- SR: 8606171814
itodiag.exe causes NT security event log messages on
remote PC when checking for diskspace on network drives
where the HP ITO account has no permissions to.
- SR: 8606180891
The template default for the service name is not used.
- SR: 8606181988
the event interceptor doesn't forward on
"forward unmatched" if a "supress unmatched" condition
is used in a second template
- SR: 8606183491
itodiag reports wrong values for diskspace
- SR: 8606188773
When issuing an opcragt -distrib to an NT node the
command doesn't exit until the distribution is completed
on the NT node, this behavior is in opposite to the UNIX
nodes, where it returns after just starting the
distribution process on the node.
- SR: B555009120
message from NT 4.0 nodes might have wrong time
in the time created on managed node field after
after changing the TZ on such a node
- SR: B555009740
When using the agent message logging with multibyte
character messages you might get wrong formats.
- SR: B555009756
When creating a template with an automatic action e.g.:
progx.exe \\<node>\share-x
And taking the <node> as variable it isn't replaced with
the correct value.
- SR: B555010012
The HP ITO Installation Server service might fail.
- SR: B555010186
When using the VPO application Virtual Term PC in the
group NT Tools and sending CTRL+C to this terminal window
on the UNIX side it might be, that the cmd.exe and
opcvterm.exe doesn't stop on the NT side. Cmd.exe instead
starts using a lot of CPU.
- SR: B555010324
The command "opcagt -kill" might not kill all VPO
processes on a NT node.
- SR: B555010449
The agent deinstallation doesn't remove the registry
keys:
HKEY_LOCAL_MACHINE/SOFTWARE/Hewlett-Packard/Openview and
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa/M
SV1_0
even when they are empty.
- SR: B555010563
The monitor agent often reports 'Can't start monitor
script for object 'Process_msdev'. Script still running.
(OpC30-610)'. Sometimes this is caused by a hanging
monitor binary.
PHSS_22883:
- Automatic Actions can't start applications that display a
user interface.
- The Event Interceptor might get into a looping state when
running on an NNM system and the ovtrapd is stopped.
- Multiple issues with the agent on MS Terminal Server
systems running on NT 4.0.
- Perl script might show strange behavior when called
as monitor.
- Logfile encapsulator might report an access violation
when reading EventLog message.
- Agent has to run as 'HP ITO account' user.
- Agent installation might fail with 'Error from
InformManager' when the Management Server is a multi
homed host.
- Agent installation adds the agent path to the system
environment without checking if it's already there. Agent
deinstallation doesn't remove this path at all.
- Japanese messages might have wrong characters.
PHSS_22008:
- ITO requires the setting of all IP addresses in
opc.hosts for NT multi homed hosts.
- The control agent aborts when the /usr/OV/tmp/OpC/bin
directory does not exist.
- The installation aborts with the NetGetDCName API
failing: network path not found.
- The event correlation agent might abort.
- In some situations the the source IP address of an
incoming trap has the wrong byte ordering.
- When there are many quickly incoming traps, the Event
Interceptor does not handle them but instead buffers
until there are new traps arriving.
- Event Interceptor aborts when running on an NNM system
and an invalid trap is received.
- After distributing of templates to NT system, sometimes
there is a message in the errorlog about failures while
suspending threads.
- Several changes for firewall environments. For detailed
information refer to the VPO Firewall Configuration
White Paper version 3.0
- The 'Processes' application on Windows 2000 produces a
Dr.Watson window.
- Event Interceptor aborts after receiving trap with
unresolvable IP address.
- If buffer file size limitation is enabled, the agent may
discard low-severity messages even if there is still
space in the buffer file.
- The execution of monitors or applications might try to
execute a directory.
Defect Description:
PHSS_25471:
- SR: B555010899
opcdista requests distribution data from a wrong manager
if there is a secondary manager with the same short
hostname than the appropriate primary manager because it
searches the whole list in for each name it tries to
match first the long then the short name. Instead it
should try the long names for all systems first and only
then try to match using the short names.
- SR: B555011990
read procedure missed first digit of the time stamp
of the previous ECS messages
- SR: 8606179902
During (de)installation the set-up replaces/removes
some DLLs which can be accessed via API calls and
therefore be locked outside of VPO agent and so they
can't be replaced. This may happen with SPIs
(e.g. VP-IS).
In order to avoid this, it is necessary to stop all
services and processes which use the DLLs.
Now the set-up process stops and then restarts all
affected services.
- SR: 8606205415
Using a drive letter with trailing blanks causes
problems with NT API calls, and problems also
occur when generating paths based on this drive letter.
To avoid this opcsetup cuts the trailing blanks during
reading the values from opcsetup.inf.
- SR: 8606208283
When the user 'HP ITO Account' (or any other
user set that the agent runs as) does not have the
privilege "Increase Quotas" and also the group does not
have, the agent can't perform a full switch user with
password check. The privilege is now assigned to the
agent user during agent installation time.
- SR: 8606212295
Removal and copying of files is not possible while
they are in use under Windows NT/Windows 2000.
To ensure the correct remove and copy operation,
all known agent processes and other agent
programs which are likely to hang, or take longer will be
stopped before files are copied or removed.
If the copy or remove still fails, there is a list
of processes running on the system in the inst.log.
It might be that one of these processes caused the
problem. This list is for troubleshooting purposes.
- SR: 8606213476
While the agent receives several RPC calls, like "Start
Distribution", "Execute Action" or "Set Primary Manager"
in parallel, it may happen that the call results in a
conflict within the control agent, which causes the
control agent to bring a Dr. Watson window.
This conflict can also occur on UNIX but the control
agent doesn't die, rather the RPC request may fail.
With this version the RPC calls which could cause
conflicts are serialised.
- SR: B555009481
The process monitor itoprocs.exe/opcntprocs.exe does not
report any value for processes with names longer than 15
characters with the first call.
This problem is fixed in the new process monitor,
which uses different API layers.
This should avoid masses of PerfLib messages seen
when the process monitor is running.
On some systems it has shown that the start of the
process monitor might cause System Event Log Messages
with the following content:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10002
Date: 2/22/2001
Time: 2:11:52 PM
User: <ComputerName>\HP ITO account
Computer: <ComputerName>
Description: Access denied attempting to launch a DCOM
Server. The server is: {0C0A3666-30C9-11D0-8F20-
00805F2CD064} The user is HP ITO account
This event is generated by the Machine Debug Manager DCOM
object which is coming with Microsoft IIS 4.0 or 5.0
to avoid this messages please see the following Microsoft
article:
Q290398
http://support.microsoft.com/support/kb/articles/Q290/3/9
8.ASP
- SR: B555010038
When SPIs change the environment variable PATH in the
way that by adding (for example) \usr\OV\bin\OpC\test or
similar this path is changed/removed during the
(de)installation of the agent.
Now the set-up program searches for the complete path
correctly ended so that it doesn't overwrite or remove
the wrong paths.
- SR: B555010879
When freeing the allocated memory, a wrong frunction was
used.
- SR: B555010948
The grammar was changed to allow nested alternatives and
process it correctly.
- SR: B555011436
The reoccurring "PerfLib" messages is due to the agent
always reading all performance data of the machine.
With this patch the monitor agent and also
itodiag.exe/ovntdiag.exe are changed to use a different
API layer of Microsoft APIs.
Querying of performance data is dedicated
to the required object and counter.
itodiag.exe/ovntdiag.exe is made independent from other
libraries delivered with the agent.
PLEASE NOTE:
There will still be other "PerfLib" and also other
messages regarding to the performance counters in the
application Event Log, but the number of these messages
is no higher than if you start perfmon.
IMPORTANT: These messages are generated after each
start of an application which reads performance data.
This means each time itodiag.exe/ovntdiag.exe or the
agent is started you will get these messages.
Event message Event ID: 3101 might also occur on systems
running Windows 2000 with Service Pack 1 or below.
Please see the following Microsoft article and web page
for detailed information:
Q257760
(http://support.microsoft.com/support/kb/articles/Q257/7/
60.ASP)
With Windows 2000 it has been seen that the LogicalDisk
Performance Counter doesn't show: C:, D: and so on but
instead HarddriveVolume1, HarddriveVolume2.
The result of this will be that the template/policies
which are monitoring the LogicalDisk object might not
work any longer. There are no additional information, why
this name change has been done.
- SR: B555011497
The trap interceptor may abort during a reboot of a
Windows NT/Windows 2000 node with the message "can't
open SNMP session". The reason is that the SNMP service
just takes to long to start.
Now the agent waits at maximum 30 seconds for the SNMP
service to start till this error message is generated.
- SR: B555011540
The agent installation of VPO/VPW only removes agent
components which currently reside in the target
installation directory. This patch the installation
checks whether there are old agents entered in the
NT/Win2k Registry and removes them.
for SR's not listed in this section please see
the list of symptoms
PHSS_24050:
- SR: 8606171814
A new command line option "/nonwdrives" is added for
itodiag.exe. When sepcifying this option for itodiag.exe
it doesn't collect information about name, file system
and total and free disk space of any mapped network
drives.
- SR: B555009756
The handling of special characters like "<" and ">" is
changed when a "\<" is found in the text for an automatic
action the behavior depends on the next ">" when this
character is masked with "\" as well everything is taken
as normal text, otherwise a variable is searched.
- SR: B555010449
The implementation of the deinstallation assumed that
these keys are always used by other applications as well.
Therefore they were not removed. Now it is checked
whether there are other keys/values below this
registration keys and if not they are removed.
for SR's not listed in this section please see
the list of symptoms
PHSS_22883:
- The ITO agent can now run as non 'HP ITO account' user.
This also includes the 'SYSTEM' account.
Installation instruction:
Use the manual installation. Before calling the
'opc_inst.bat' script, an additional entry can be added to
the 'opcsetup.inf' file to specify the run user for the
agent:
[Agent User]
SYSTEM
Instead of 'SYSTEM', any other name could be specified. In
this case the user account is created.
If 'SYSTEM' is given, no user account is created (no
'opc_op' either).
NOTE: User names may not contain space characters.
If a user name is specified in 'opcsetup.inf', the agent
will be installed using this account name, no matter if
there was already an agent installed using another
account.
If a different user is specified in 'opcsetup.inf', the
account created by the existing agent is not removed but
left on the system. It has to be removed manually.
If no user name is specified in 'opcsetup.inf', the
installation will check if there is already an agent
installed. If it finds one, the same user will be used.
If a user is specified or found to be used by an old
agent, and the password specified was not correct for this
account, the user is removed and re-created. It has the
same name afterwards but a different internal user ID.
Applications:
-------------
- All applications configured to run as 'opc_op' or
'HP ITO account' have to be changed to specify a user
that exists on the system.
- All monitoring executables will be run as the specified
account. This might restrict some of the access rights
to monitored applications.
- The 'SYSTEM' account does not have any network access
capabilities.
Remote installation:
--------------------
- On Domain Controllers there is the Installation Server
service that executes the installation on remote systems
in this domain. If this service is modified to run as
'SYSTEM', the remote installation is not possible at all
(the 'SYSTEM' account does not have any access rights
for remote systems).
- If remote execution is wanted, the Installation Server
service can be configured to run as a domain user that
has Domain Admin user rights.
PHSS_22008:
check the list of the symptoms
SR:
R555011075 R555003313 B555011990 B555011979 B555011594
B555011540 B555011510 B555011497 B555011436 B555011422
B555011256 B555011108 B555010980 B555010948 B555010899
B555010879 B555010819 B555010620 B555010563 B555010449
B555010324 B555010186 B555010038 B555010012 B555009756
B555009745 B555009740 B555009712 B555009553 B555009481
B555009412 B555009388 B555009360 B555009201 B555009193
B555009153 B555009120 B555009099 B555008912 B555008754
B555008729 B555008663 B555008526 B555008314 B555008309
B555008220 B555008180 B555007966 B555007883 B555007847
B555007840 B555007752 B555007619 B555007602 B555007549
B555007478 B555007056 B555005125 8606214799 8606213476
8606212295 8606208283 8606206616 8606205415 8606188773
8606183491 8606181988 8606180891 8606179902 8606171814
8606161695 8606140211
Patch Files:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opc_pkg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/unzip.exe
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/unzip.txt
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opc_inst.bat
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opc_pre.bat
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opcsetup.inf
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/monitor/itoprocs.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/monitor/sms_chk.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/monitor/mf_service.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/mfluse.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itomserv.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itoreg.cfg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/opcdf.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/opcps.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itodiag.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/pdh.dll.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itokill.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itoreg.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itosdown.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itouser.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/opcprfls.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/mf_app.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
AgentPlatform
what(1) Output:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opc_pkg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/unzip.exe:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/unzip.txt:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opc_inst.bat:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opc_pre.bat:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/opcsetup.inf:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/monitor/itoprocs.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/monitor/sms_chk.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/monitor/mf_service.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/mfluse.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itomserv.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itoreg.cfg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/opcdf.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/opcps.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itodiag.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/pdh.dll.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itokill.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itoreg.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itosdown.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/itouser.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/opcprfls.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.09/RPC_DCE_TCP/cmds/mf_app.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
AgentPlatform:
None
cksum(1) Output:
2112376157 6278003 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/opc_pkg.Z
3162183940 113152 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/unzip.exe
1939298735 508 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/unzip.txt
4115030442 1664 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/opc_inst.bat
2405569119 1715 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/opc_pre.bat
1709918629 133 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/opcsetup.inf
2452231119 5966 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/monitor/
itoprocs.exe.Z
345227238 132 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/monitor/
sms_chk.bat.Z
3876037765 129 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/monitor/
mf_service.bat.Z
2768355422 3926 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
mfluse.exe.Z
2088494086 49779 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
itomserv.exe.Z
1586237090 188 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
itoreg.cfg.Z
2003580432 38 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
opcdf.bat.Z
849569434 41 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
opcps.bat.Z
606657056 22497 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
itodiag.exe.Z
2576066882 103311 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
pdh.dll.Z
622302383 6864 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
itokill.exe.Z
3379227416 13779 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
itoreg.exe.Z
3585411024 46678 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
itosdown.exe.Z
1460494396 51633 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
itouser.exe.Z
1221751499 10113 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
opcprfls.exe.Z
1588307382 751 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.09/RPC_DCE_TCP/cmds/
mf_app.bat.Z
3689235447 6469 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/AgentPlatform
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_22008 PHSS_22883 PHSS_24050
Equivalent Patches:
PHSS_25472:
s700: 11.00
s800: 11.00
Patch Package Size: 6670 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_25471
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25471.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25471. 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_25471.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_25471.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
o It provides bug fixes and enhancements for the
VPO A.06.00 Management Server system.
o DO NOT use this patch with older releases of ITO,
for example versions A.05.00, A.05.11 or A.05.30
(A) Patch Installation Instructions
-------------------------------
(A1) Install the patch, following the standard
installation instructions.
For backing up the system before installing
a patch, you may use opc_backup(1m)
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED
(either from the VPO Administrator's GUI
or from command line using inst.sh) WHILE
RUNNING SWINSTALL.
Don't be afraid of the '-x autoreboot=true'
option above. There won't be a reboot due
to this VPO patch.
You can skip this option if you like.
NOTE: This patch must be installed on the VPO Management
Server system, NOT on an VPO Managed Node directly.
Changes will take effect on managed nodes by means of
VPO Software Distribution (using 'Force Update' if
there is already an agent installed on the managed
node). See chapter 2 of the VPO Administrator's
Reference manual for more information.
- The ITO agent can now run as non 'HP ITO account' user.
This also includes the 'SYSTEM' account.
Installation instruction:
Use the manual installation. Before calling the
'opc_inst.bat' script, an additional entry can be added to
the 'opcsetup.inf' file to specify the run user for the
agent:
[Agent User]
SYSTEM
Instead of 'SYSTEM', any other name could be specified. In
this case the user account is created.
If 'SYSTEM' is given, no user account is created (no
'opc_op' either).
NOTE: User names may not contain space characters.
If a user name is specified in 'opcsetup.inf', the agent
will be installed using this account name, no matter if
there was already an agent installed using another
account.
If a different user is specified in 'opcsetup.inf', the
account created by the existing agent is not removed but
left on the system. It has to be removed manually.
If no user name is specified in 'opcsetup.inf', the
installation will check if there is already an agent
installed. If it finds one, the same user will be used.
If a user is specified or found to be used by an old
agent, and the password specified was not correct for this
account, the user is removed and re-created. It has the
same name afterwards but a different internal user ID.
Applications:
-------------
- All applications configured to run as 'opc_op' or
'HP ITO account' have to be changed to specify a user
that exists on the system.
- All monitoring executables will be run as the specified
account. This might restrict some of the access rights
to monitored applications.
- The 'SYSTEM' account does not have any network access
capabilities.
Remote installation:
--------------------
- On Domain Controllers there is the Installation Server
service that executes the installation on remote systems
in this domain. If this service is modified to run as
'SYSTEM', the remote installation is not possible at all
(the 'SYSTEM' account does not have any access rights
for remote systems).
- If remote execution is wanted, the Installation Server
service can be configured to run as a domain user that
has Domain Admin user rights.
(B) Patch Deinstallation Instructions
---------------------------------
(B1) To deinstall the patch PHSS_25471 run swremove:
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
from the ITO Administrator's GUI or from
command line using inst.sh) WHILE RUNNING
SWREMOVE.
# swremove PHSS_25471
-----End of Document ID: PHSS_25471------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]