|
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_at_us-support-mail.external.hp.com)
Date: Sun Jul 21 2002 - 06:50:20 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 11.X patch digest
Created: Sun Jul 21 3:05:03 PDT 2002
Table of Contents:
Document ID Title
--------------- -----------
PHSS_27195 s700_800 11.11 TechPrintServ Periodic Patch
PHSS_27194 s700_800 11.00 TechPrintServ Periodic Patch
PHSS_27067 s700_800 11.00 OV ITO6.0X NT Agent Patch A.06.11
PHNE_27201 s700_800 11.00 IGELAN 1000Base-SX/T B.11.00.04 patch
PHNE_26369 s700_800 11.11 IGELAN 1000Base-SX/T B.11.11.[02-04] patch
PHKL_27279 s700_800 11.11 VxVM B.03.12.4 panic in vol_dump_disks()
PHKL_27070 s700_800 11.00 VxFS cumulative,I/O Throttling/sync daemon
PHKL_27003 s700_800 11.00 SCSI IO Subsystem Cumulative Patch
PHSS_27411 s700_800 11.X ISEE user interface functionality correction
PHSS_27015 s700_800 11.00 OV ITO6.0X OVO JavaGUI client A.07.10
PHSS_26871 s700_800 11.00 EMS (A.03.20) & HA Monitors (A.03.20) patch
PHKL_26239 s700_800 11.11 getmount_entry; rename; creat; mount/umount
PHCO_27910 s700_800 11.11 libc cumulative patch
PHCO_27120 s700_800 11.11 umount(1M) cumulative patch
PHCO_26701 s700_800 11.11 fsck(1M) sync switch patch
PHCO_26700 s700_800 11.11 fsck_vxfs(1M) sync switch patch
PHCO_26699 s700_800 11.11 fsck_hfs(1M) sync switch patch
PHCO_26334 s700_800 11.11 quotaon(1M) quotaoff(1M) cumulative patch
PHCO_26333 s700_800 11.11 fsclean(1M) cumulative patch
PHCO_26332 s700_800 11.11 umountall(1M) cumulative patch
PHCO_26331 s700_800 11.11 mountall(1M) cumulative patch
PHCO_26242 s700_800 11.11 mount(1M) cumulative patch
PHSS_27307 s700_800 11.04 Virtualvault 4.6 TGA reports missing CGI
PHSS_26978 s700_800 11.11 TC-SysSetup Cumulative Patch
PHSS_26927 s700_800 11.11 B2600 1.4 FW
PHSS_26926 s700_800 11.00 B2600 1.4 FW
PHKL_27364 s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,AIO,T600,FS,Hang
PHKL_27304 s700_800 11.11 SCSI Tape (stape) cumulative
PHKL_27303 s700_800 11.00 SCSI Tape (stape) cumulative
PHSS_27306 s700_800 11.04 Virtualvault 4.5 TGA reports missing CGI
PHSS_27262 s700_800 11.04 VirtualVault 4.0 TGA reports missing CGI
PHSS_26947 s700_800 11.11 EMS & HA Monitors (A.03.20.01) patch
PHCO_26960 s700_800 11.00 Pthread library cumulative patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_27195
Date Loaded: 20020719
Title: s700_800 11.11 TechPrintServ Periodic Patch
Patch Name: PHSS_27195
Patch Description: s700_800 11.11 TechPrintServ Periodic Patch
Creation Date: 02/07/04
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
TechPrintServ B.11.11
Filesets:
TechPrintServ.TPS-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
TechPrintServ.TPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
TechPrintServ.TPS-C-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
TechPrintServ.TPS-GER-I-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
TechPrintServ.TPS-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27195
Symptoms:
PHSS_27195:
1. Updating /etc/X11/Xstart file using tpsconfig
2. TPS aborts on print attempt if PHCO_25452 or
PHCO_26124 is installed
3. tpsconfig dumps core while configuring print servers
PHSS_25759:
1. Font server should automatically be configured when TPS
is configured.
2. X Print Server keeps on messaging.
3. Please add the HP Laserjet 5000N to the list of models
supported by TPS.
4. Printer model not read correctly from printer attribute
file at times.
5. The tpsconfig does not report any error when trying to
kill a non-running server.
6. TPS support for latest HP printers, esp. DJ2500.
7. Problem with invoking xpr
Defect Description:
PHSS_27195:
1. Updating /etc/X11/Xstart file using tpsconfig
2. TPS aborts on print attempt if PHCO_25452 or
PHCO_26124 is installed
3. tpsconfig dumps core while configuring print servers
PHSS_25759:
1. Font server should automatically be configured when TPS
is configured.
2. X Print Server keeps on messaging.
3. Please add the HP Laserjet 5000N to the list of models
supported by TPS.
4. Printer model not read correctly from printer attribute
file at times.
5. The tpsconfig does not report any error when trying to
kill a non-running server.
6. TPS support for latest HP printers, esp. DJ2500.
7. Problem with invoking xpr
Enhancement:
No (superseded patches contained enhancements)
PHSS_25759:
Enhancements were delivered in this patch or one it has
replaced. Please review the Defect Description text for
more information.
SR:
8606242412 8606255094 8606266550 5003460154 8606158503
8606172755 8606172757 8606206562 8606221220
Patch Files:
TechPrintServ.TPS-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/lib/X11/Xserver/brokers/print/Xpddx.1
/usr/lib/X11/Xserver/modules/print/hp/raster.1
/usr/lib/X11/Xserver/modules/print/hp/printer.1
TechPrintServ.TPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/sbin/tpsconfig
TechPrintServ.TPS-C-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/lib/X11/C/print/models/HPLJ5000N/model-config
/usr/lib/X11/C/print/models/HPLJ5000N/fonts
/usr/lib/X11/C/print/models/HPLJ5000N-PS/model-config
/usr/lib/X11/C/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N/fonts
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/model-config
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/fonts
/usr/lib/X11/C.iso88591/print/models/HPDESKJ2500C-PS/fonts
TechPrintServ.TPS-GER-I-SERV,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N/fonts
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/de_DE.iso88591/print/models/HPDESKJ2500C-PS/
fonts
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N/fonts
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/fr_FR.iso88591/print/models/HPDESKJ2500C-PS/
fonts
TechPrintServ.TPS-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/dt/share/man/man5.Z/tps.5
/usr/dt/share/man/man1m.Z/tpsconfig.1m
what(1) Output:
TechPrintServ.TPS-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/lib/X11/Xserver/brokers/print/Xpddx.1:
Xprint DDX driver Broker $Revision:$ $Date:$
X Window System, Version 11 R6+ HP-UX B.11.11.00 Dec
ember 2001 Patch Release
(build date: Wed Nov 28 10:49:48 IST 2001)
/usr/lib/X11/Xserver/modules/print/hp/raster.1:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Dec
ember 2001 Patch Release
(build date: Wed Nov 28 10:53:02 IST 2001)
/usr/lib/X11/Xserver/modules/print/hp/printer.1:
X Window System, Version 11 R6+ HP-UX B.11.11.00 Per
iodic Patch Release
(build date: Fri May 31 18:25:36 IST 2002)
TechPrintServ.TPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/sbin/tpsconfig:
View: /view/wt_jun02_1111, Build Type: wtjun02_1111
hpcde2.1
(build date: Wed Jul 3 14:34:03 IST 2002)
This program provides basic configuration
functions for the X Print Server
HP-UX A.10.30 and later
HP tpsconfig V.01.00
TechPrintServ.TPS-C-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/lib/X11/C/print/models/HPLJ5000N/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/C/print/models/HPLJ5000N-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/model-config:
None
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/fonts:
None
/usr/lib/X11/C.iso88591/print/models/HPDESKJ2500C-PS/fonts:
None
TechPrintServ.TPS-GER-I-SERV,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/de_DE.iso88591/print/models/HPDESKJ2500C-PS/
fonts:
None
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/fr_FR.iso88591/print/models/HPDESKJ2500C-PS/
fonts:
None
TechPrintServ.TPS-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/dt/share/man/man5.Z/tps.5:
None
/usr/dt/share/man/man1m.Z/tpsconfig.1m:
None
cksum(1) Output:
TechPrintServ.TPS-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
146524341 24576 /usr/lib/X11/Xserver/brokers/print/Xpddx.1
1623856174 36864 /usr/lib/X11/Xserver/modules/print/hp/
raster.1
1140643443 143360 /usr/lib/X11/Xserver/modules/print/hp/
printer.1
TechPrintServ.TPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
2453099939 40960 /usr/sbin/tpsconfig
TechPrintServ.TPS-C-SERV,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
2557094373 895 /usr/lib/X11/C/print/models/HPLJ5000N/
model-config
372694182 2048 /usr/lib/X11/C/print/models/HPLJ5000N/fonts
2791726251 3166 /usr/lib/X11/C/print/models/HPLJ5000N-PS/
model-config
1676891234 1024 /usr/lib/X11/C/print/models/HPLJ5000N-PS/
fonts
1058812761 2048 /usr/lib/X11/C.iso88591/print/models/
HPLJ5000N/fonts
1676891234 1024 /usr/lib/X11/C.iso88591/print/models/
HPLJ5000N-PS/fonts
848631901 3195 /usr/lib/X11/C/print/models/HPDESKJ2500C-PS/
model-config
4032257195 1024 /usr/lib/X11/C/print/models/HPDESKJ2500C-PS/
fonts
4032257195 1024 /usr/lib/X11/C.iso88591/print/models/
HPDESKJ2500C-PS/fonts
TechPrintServ.TPS-GER-I-SERV,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
1058812761 2048 /usr/lib/X11/de_DE.iso88591/print/models/
HPLJ5000N/fonts
1676891234 1024 /usr/lib/X11/de_DE.iso88591/print/models/
HPLJ5000N-PS/fonts
4032257195 1024 /usr/lib/X11/de_DE.iso88591/print/models/
HPDESKJ2500C-PS/fonts
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
1058812761 2048 /usr/lib/X11/fr_FR.iso88591/print/models/
HPLJ5000N/fonts
1676891234 1024 /usr/lib/X11/fr_FR.iso88591/print/models/
HPLJ5000N-PS/fonts
4032257195 1024 /usr/lib/X11/fr_FR.iso88591/print/models/
HPDESKJ2500C-PS/fonts
TechPrintServ.TPS-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
3986603607 6221 /usr/dt/share/man/man5.Z/tps.5
1447785863 3319 /usr/dt/share/man/man1m.Z/tpsconfig.1m
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_25759
Equivalent Patches:
PHSS_27194:
s700: 11.00
s800: 11.00
Patch Package Size: 310 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_27195
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27195.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27195. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_27195.text file is
available in the product readme:
swlist -l product -a readme -d 
/tmp/PHSS_27195.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27195.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_27195------------------------------------------
Document ID: PHSS_27194
Date Loaded: 20020719
Title: s700_800 11.00 TechPrintServ Periodic Patch
Patch Name: PHSS_27194
Patch Description: s700_800 11.00 TechPrintServ Periodic Patch
Creation Date: 02/06/04
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
TechPrintServ.TPS-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
TechPrintServ.TPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
TechPrintServ.TPS-C-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
TechPrintServ.TPS-GER-I-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
TechPrintServ.TPS-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27194
Symptoms:
PHSS_27194:
1. Updating /etc/X11/Xstart file using tpsconfig
2. TPS aborts on print attempt if PHCO_25452 or
PHCO_26124 is installed
3. tpsconfig dumps core while configuring print servers
PHSS_25758:
1. Font server should automatically be configured when TPS
is configured.
2. X Print Server keeps on messaging.
3. Please add the HP Laserjet 5000N to the list of models
supported by TPS.
4. printer model not read correctly from printer attribute
file at times.
5. tpsconfig does not report any error when trying to kill
a non-running server.
6. TPS support for latest HP printers, esp. DJ2500.
7. Problem with invoking xpr.
PHSS_22750:
1. Incorrect behavior of XFillPolygon.
2. Incomplete Roman8 font metrics for Postscript fonts.
3. Can't configure TPS sw to work using systems defined
printers- lpstat -a.
4. tpsconfig core dumps when in sys.resources a wrong entry
is set.
5. XP-PCL-MONO driver does not support GC functions.
6. TPS dumps core when using HPLJ3Si model printer.
7. With PHSS_20143,dtpad coredumps while using a pcl driver
to print.
8. When printing 2-day range (day view), 2nd page grid is
wrong.
PHSS_20143:
1. Technical print server prints blank or all
black pages.
PHSS_18431:
1. dtpdmd still fails in slow speed machines.
PHSS_16652:
1. dtpdmd does not startup while booting up.
Defect Description:
PHSS_27194:
1. Updating /etc/X11/Xstart file using tpsconfig
2. TPS aborts on print attempt if PHCO_25452 or
PHCO_26124 is installed
3. tpsconfig dumps core while configuring print servers
PHSS_25758:
1. Font server should automatically be configured when TPS
is configured.
2. X Print Server keeps on messaging.
3. Please add the HP Laserjet 5000N to the list of models
supported by TPS.
4. printer model not read correctly from printer attribute
file at times.
5. tpsconfig does not report any error when trying to kill
a non-running server.
6. TPS support for latest HP printers, esp. DJ2500.
7. Problem with invoking xpr.
PHSS_22750:
1. Incorrect behavior of XFillPolygon.
2. Incomplete Roman8 font metrics for Postscript fonts.
3. Can't configure TPS sw to work using systems defined
printers- lpstat -a.
4. tpsconfig core dumps when in sys.resources a wrong entry
is set.
5. XP-PCL-MONO driver does not support GC functions.
6. TPS dumps core when using HPLJ3Si model printer.
7. With PHSS_20143,dtpad coredumps while using a pcl driver
to print.
8. When printing 2-day range (day view), 2nd page grid is
wrong.
PHSS_20143:
1. TPS problem with certain Xserver patches.
Resolution:
Repaired TPS to send correct PCL initialization string
to printer.
PHSS_18431:
1. dtpdmd still fails in slow speed machines.
Resolution:
Fix involves in starting X Printserver and
dtpdmd as daemon to avoid resets by SIGHUP.
PHSS_16652:
1. CDE 11.00 dtpdmd for TPS terminated unexpectedly.
Enhancement:
No (superseded patches contained enhancements)
PHSS_25758:
Enhancements were delivered in this patch or one it has
replaced. Please review the Defect Description text for
more information.
SR:
8606242412 8606255094 8606266550 5003460154 8606158503
8606172755 8606172757 8606206562 8606221220 8606152076
8606134665 5003421669 8606161189 5003398768 1653277293
Patch Files:
TechPrintServ.TPS-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/sbin/init.d/tps.rc
/usr/lib/X11/Xserver/brokers/extensions/Xp.1
/usr/lib/X11/Xserver/brokers/print/Xpddx.1
/usr/lib/X11/Xserver/modules/extensions/hp/xp.1
/usr/lib/X11/Xserver/modules/print/hp/pcl.1
/usr/lib/X11/Xserver/modules/print/hp/pclmono.1
/usr/lib/X11/Xserver/modules/print/hp/pcllj3.1
/usr/lib/X11/Xserver/modules/print/hp/pcldj1200.1
/usr/lib/X11/Xserver/modules/print/hp/ps.1
/usr/lib/X11/Xserver/modules/print/hp/raster.1
/usr/lib/X11/Xserver/modules/print/hp/printer.1
TechPrintServ.TPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/sbin/tpsconfig
TechPrintServ.TPS-C-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/lib/X11/C/print/models/HPLJ5000N/model-config
/usr/lib/X11/C/print/models/HPLJ5000N/fonts
/usr/lib/X11/C/print/models/HPLJ5000N-PS/model-config
/usr/lib/X11/C/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N/fonts
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/model-config
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/fonts
/usr/lib/X11/C.iso88591/print/models/HPDESKJ2500C-PS/fonts
/usr/lib/X11/C/print/Xprinters
/usr/lib/X11/C/print/ddx-config/XP-PCL-COLOR/ddx-config
/usr/lib/X11/C/print/ddx-config/XP-PCL-DJ1200/ddx-config
/usr/lib/X11/C/print/ddx-config/XP-PCL-LJ3/ddx-config
/usr/lib/X11/C/print/ddx-config/XP-PCL-MONO/ddx-config
/usr/lib/X11/C/print/ddx-config/XP-POSTSCRIPT/ddx-config
/usr/lib/X11/C/print/ddx-config/XP-RASTER/ddx-config
/usr/lib/X11/C/print/ddx-config/XP-RASTER/pcl
/usr/lib/X11/C/print/ddx-config/XP-RASTER/postscript
/usr/lib/X11/C/print/models/HPDESIGNJ220/model-config
/usr/lib/X11/C/print/models/HPDESIGNJ330/model-config
/usr/lib/X11/C/print/models/HPDESIGNJ350C_350CM-PS/
model-config
/usr/lib/X11/C/print/models/HPDESIGNJ600/model-config
/usr/lib/X11/C/print/models/HPDESIGNJ650C_650CM-PS/
model-config
/usr/lib/X11/C/print/models/HPDESIGNJ750C_750CM-PS/
model-config
/usr/lib/X11/C/print/models/HPDESIGNJ755CM-PS/model-config
/usr/lib/X11/C/print/models/HPDESKJ1200C-PS/model-config
/usr/lib/X11/C/print/models/HPDESKJ1200C/model-config
/usr/lib/X11/C/print/models/HPDESKJ1600C_1600CM-PS/
model-config
/usr/lib/X11/C/print/models/HPDESKJ1600C_1600CM/model-config
/usr/lib/X11/C/print/models/HPLJ3-PS/model-config
/usr/lib/X11/C/print/models/HPLJ3/model-config
/usr/lib/X11/C/print/models/HPLJ3D-PS/model-config
/usr/lib/X11/C/print/models/HPLJ3D/model-config
/usr/lib/X11/C/print/models/HPLJ3P-PS/model-config
/usr/lib/X11/C/print/models/HPLJ3P/model-config
/usr/lib/X11/C/print/models/HPLJ3Si-PS/model-config
/usr/lib/X11/C/print/models/HPLJ3Si/model-config
/usr/lib/X11/C/print/models/HPLJ4+_4M+-PS/model-config
/usr/lib/X11/C/print/models/HPLJ4+_4M+/model-config
/usr/lib/X11/C/print/models/HPLJ4L_4ML-PS/model-config
/usr/lib/X11/C/print/models/HPLJ4L_4ML/model-config
/usr/lib/X11/C/print/models/HPLJ4P_4MP-PS/model-config
/usr/lib/X11/C/print/models/HPLJ4P_4MP/model-config
/usr/lib/X11/C/print/models/HPLJ4Si_4SiMX-PS/model-config
/usr/lib/X11/C/print/models/HPLJ4Si_4SiMX/model-config
/usr/lib/X11/C/print/models/HPLJ4V_4MV-PS/model-config
/usr/lib/X11/C/print/models/HPLJ4V_4MV/model-config
/usr/lib/X11/C/print/models/HPLJ4_4M-PS/model-config
/usr/lib/X11/C/print/models/HPLJ4_4M/model-config
/usr/lib/X11/C/print/models/HPLJ4color_4Mcolor-PS/
model-config
/usr/lib/X11/C/print/models/HPLJ4color_4Mcolor/model-config
/usr/lib/X11/C/print/models/HPLJ5L_5ML-PS/model-config
/usr/lib/X11/C/print/models/HPLJ5L_5ML/model-config
/usr/lib/X11/C/print/models/HPLJ5N_5MN-PS/model-config
/usr/lib/X11/C/print/models/HPLJ5N_5MN/model-config
/usr/lib/X11/C/print/models/HPLJ5P_5MP-PS/model-config
/usr/lib/X11/C/print/models/HPLJ5P_5MP/model-config
/usr/lib/X11/C/print/models/HPLJ5Si_5SiMX-PS/model-config
/usr/lib/X11/C/print/models/HPLJ5Si_5SiMX/model-config
/usr/lib/X11/C/print/models/HPLJ5_5M-PS/model-config
/usr/lib/X11/C/print/models/HPLJ5_5M/model-config
/usr/lib/X11/C/print/models/HPLJ5color_5Mcolor-PS/
model-config
/usr/lib/X11/C/print/models/HPLJ5color_5Mcolor/model-config
/usr/newconfig/etc/X11/C/print/attributes/document
/usr/newconfig/etc/X11/C/print/attributes/job
/usr/newconfig/etc/X11/C/print/attributes/printer
TechPrintServ.TPS-GER-I-SERV,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N/fonts
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/de_DE.iso88591/print/models/HPDESKJ2500C-PS/
fonts
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N/fonts
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N-PS/fonts
/usr/lib/X11/fr_FR.iso88591/print/models/HPDESKJ2500C-PS/
fonts
TechPrintServ.TPS-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/dt/share/man/man5.Z/tps.5
/usr/dt/share/man/man1m.Z/tpsconfig.1m
what(1) Output:
TechPrintServ.TPS-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/sbin/init.d/tps.rc:
None
/usr/lib/X11/Xserver/brokers/extensions/Xp.1:
HP_XP Extension Broker $Revision:$ $Date:$
Built for: HP-UX 11.00 ACE 9911 on HP-UX Daily, -O +
Onolimit
X Window System, Version 11 R6
(build date: Mon Sep 13 00:11:42 MDT 1999)
/usr/lib/X11/Xserver/brokers/print/Xpddx.1:
Xprint DDX driver Broker $Revision:$ $Date:$
X Window System, Version 11 R6+ HP-UX B.11.00.00 Dec
ember 2001 Patch Release
(build date: Wed Nov 28 10:37:49 IST 2001)
/usr/lib/X11/Xserver/modules/extensions/hp/xp.1:
Built for: HP-UX 11.00 ACE 9911 on HP-UX Daily, -O +
Onolimit
X Window System, Version 11 R6
(build date: Mon Sep 13 00:14:55 MDT 1999)
/usr/lib/X11/Xserver/modules/print/hp/pcl.1:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Dec
2000 Patch Release
(build date: Tue Dec 12 15:27:37 IST 2000)
/usr/lib/X11/Xserver/modules/print/hp/pclmono.1:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Dec
2000 Patch Release
(build date: Tue Dec 12 15:51:36 IST 2000)
/usr/lib/X11/Xserver/modules/print/hp/pcllj3.1:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Dec
2000 Patch Release
(build date: Tue Dec 12 15:46:04 IST 2000)
/usr/lib/X11/Xserver/modules/print/hp/pcldj1200.1:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Dec
2000 Patch Release
(build date: Tue Dec 12 15:36:27 IST 2000)
/usr/lib/X11/Xserver/modules/print/hp/ps.1:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Dec
2000 Patch Release
(build date: Tue Dec 12 15:24:03 IST 2000)
/usr/lib/X11/Xserver/modules/print/hp/raster.1:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Dec
ember 2001 Patch Release
(build date: Wed Nov 28 10:21:19 IST 2001)
/usr/lib/X11/Xserver/modules/print/hp/printer.1:
X Window System, Version 11 R6+ HP-UX B.11.00.00 Per
iodic Patch Release
(build date: Fri May 31 18:22:29 IST 2002)
TechPrintServ.TPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/sbin/tpsconfig:
View: /view/wt_jun02_1100, Build Type: wtjun02_1100
hpcde2.1
(build date: Wed Jul 3 14:22:25 IST 2002)
This program provides basic configuration
functions for the X Print Server
HP-UX A.10.30 and later
HP tpsconfig V.01.00
TechPrintServ.TPS-C-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/lib/X11/C/print/models/HPLJ5000N/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/C/print/models/HPLJ5000N-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/C.iso88591/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/model-config:
None
/usr/lib/X11/C/print/models/HPDESKJ2500C-PS/fonts:
None
/usr/lib/X11/C.iso88591/print/models/HPDESKJ2500C-PS/fonts:
None
/usr/lib/X11/C/print/Xprinters:
None
/usr/lib/X11/C/print/ddx-config/XP-PCL-COLOR/ddx-config:
None
/usr/lib/X11/C/print/ddx-config/XP-PCL-DJ1200/ddx-config:
None
/usr/lib/X11/C/print/ddx-config/XP-PCL-LJ3/ddx-config:
None
/usr/lib/X11/C/print/ddx-config/XP-PCL-MONO/ddx-config:
None
/usr/lib/X11/C/print/ddx-config/XP-POSTSCRIPT/ddx-config:
None
/usr/lib/X11/C/print/ddx-config/XP-RASTER/ddx-config:
None
/usr/lib/X11/C/print/ddx-config/XP-RASTER/pcl:
None
/usr/lib/X11/C/print/ddx-config/XP-RASTER/postscript:
None
/usr/lib/X11/C/print/models/HPDESIGNJ220/model-config:
None
/usr/lib/X11/C/print/models/HPDESIGNJ330/model-config:
None
/usr/lib/X11/C/print/models/HPDESIGNJ350C_350CM-PS/
model-config:
None
/usr/lib/X11/C/print/models/HPDESIGNJ600/model-config:
None
/usr/lib/X11/C/print/models/HPDESIGNJ650C_650CM-PS/
model-config:
None
/usr/lib/X11/C/print/models/HPDESIGNJ750C_750CM-PS/
model-config:
None
/usr/lib/X11/C/print/models/HPDESIGNJ755CM-PS/model-config:
None
/usr/lib/X11/C/print/models/HPDESKJ1200C-PS/model-config:
None
/usr/lib/X11/C/print/models/HPDESKJ1200C/model-config:
None
/usr/lib/X11/C/print/models/HPDESKJ1600C_1600CM-PS/
model-config:
None
/usr/lib/X11/C/print/models/HPDESKJ1600C_1600CM/
model-config:
None
/usr/lib/X11/C/print/models/HPLJ3-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ3/model-config:
None
/usr/lib/X11/C/print/models/HPLJ3D-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ3D/model-config:
None
/usr/lib/X11/C/print/models/HPLJ3P-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ3P/model-config:
None
/usr/lib/X11/C/print/models/HPLJ3Si-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ3Si/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4+_4M+-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4+_4M+/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4L_4ML-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4L_4ML/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4P_4MP-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4P_4MP/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4Si_4SiMX-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4Si_4SiMX/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4V_4MV-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4V_4MV/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4_4M-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4_4M/model-config:
None
/usr/lib/X11/C/print/models/HPLJ4color_4Mcolor-PS/
model-config:
None
/usr/lib/X11/C/print/models/HPLJ4color_4Mcolor/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5L_5ML-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5L_5ML/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5N_5MN-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5N_5MN/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5P_5MP-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5P_5MP/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5Si_5SiMX-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5Si_5SiMX/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5_5M-PS/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5_5M/model-config:
None
/usr/lib/X11/C/print/models/HPLJ5color_5Mcolor-PS/
model-config:
None
/usr/lib/X11/C/print/models/HPLJ5color_5Mcolor/model-config:
None
/usr/newconfig/etc/X11/C/print/attributes/document:
None
/usr/newconfig/etc/X11/C/print/attributes/job:
None
/usr/newconfig/etc/X11/C/print/attributes/printer:
None
TechPrintServ.TPS-GER-I-SERV,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/de_DE.iso88591/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/de_DE.iso88591/print/models/HPDESKJ2500C-PS/
fonts:
None
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N/fonts:
None
/usr/lib/X11/fr_FR.iso88591/print/models/HPLJ5000N-PS/fonts:
None
/usr/lib/X11/fr_FR.iso88591/print/models/HPDESKJ2500C-PS/
fonts:
None
TechPrintServ.TPS-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/dt/share/man/man5.Z/tps.5:
None
/usr/dt/share/man/man1m.Z/tpsconfig.1m:
None
cksum(1) Output:
TechPrintServ.TPS-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
704795715 2918 /sbin/init.d/tps.rc
2011311868 12288 /usr/lib/X11/Xserver/brokers/extensions/
Xp.1
3415082233 24576 /usr/lib/X11/Xserver/brokers/print/Xpddx.1
3151631414 40960 /usr/lib/X11/Xserver/modules/extensions/hp/
xp.1
3922509624 122880 /usr/lib/X11/Xserver/modules/print/hp/
pcl.1
3176390559 122880 /usr/lib/X11/Xserver/modules/print/hp/
pclmono.1
1160581147 118784 /usr/lib/X11/Xserver/modules/print/hp/
pcllj3.1
4051306568 122880 /usr/lib/X11/Xserver/modules/print/hp/
pcldj1200.1
2120541075 110592 /usr/lib/X11/Xserver/modules/print/hp/ps.1
1310789339 32768 /usr/lib/X11/Xserver/modules/print/hp/
raster.1
1593611396 131072 /usr/lib/X11/Xserver/modules/print/hp/
printer.1
TechPrintServ.TPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
995285876 40960 /usr/sbin/tpsconfig
TechPrintServ.TPS-C-SERV,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
2557094373 895 /usr/lib/X11/C/print/models/HPLJ5000N/
model-config
225729238 2048 /usr/lib/X11/C/print/models/HPLJ5000N/fonts
2791726251 3166 /usr/lib/X11/C/print/models/HPLJ5000N-PS/
model-config
2998329733 1024 /usr/lib/X11/C/print/models/HPLJ5000N-PS/
fonts
3897938825 2048 /usr/lib/X11/C.iso88591/print/models/
HPLJ5000N/fonts
2998329733 1024 /usr/lib/X11/C.iso88591/print/models/
HPLJ5000N-PS/fonts
848631901 3195 /usr/lib/X11/C/print/models/HPDESKJ2500C-PS/
model-config
2626225633 1024 /usr/lib/X11/C/print/models/HPDESKJ2500C-PS/
fonts
2626225633 1024 /usr/lib/X11/C.iso88591/print/models/
HPDESKJ2500C-PS/fonts
3331616808 1735 /usr/lib/X11/C/print/Xprinters
892884360 225 /usr/lib/X11/C/print/ddx-config/XP-PCL-COLOR/
ddx-config
3235348410 234 /usr/lib/X11/C/print/ddx-config/
XP-PCL-DJ1200/ddx-config
3934776043 222 /usr/lib/X11/C/print/ddx-config/XP-PCL-LJ3/
ddx-config
3844622675 162 /usr/lib/X11/C/print/ddx-config/XP-PCL-MONO/
ddx-config
786472644 220 /usr/lib/X11/C/print/ddx-config/XP-POSTSCRIPT/
ddx-config
2926026717 156 /usr/lib/X11/C/print/ddx-config/XP-RASTER/
ddx-config
214807386 1470 /usr/lib/X11/C/print/ddx-config/XP-RASTER/pcl
2600510636 251 /usr/lib/X11/C/print/ddx-config/XP-RASTER/
postscript
2739697433 3842 /usr/lib/X11/C/print/models/HPDESIGNJ220/
model-config
1447935401 3842 /usr/lib/X11/C/print/models/HPDESIGNJ330/
model-config
3082284170 3886 /usr/lib/X11/C/print/models/
HPDESIGNJ350C_350CM-PS/model-config
1665689009 3842 /usr/lib/X11/C/print/models/HPDESIGNJ600/
model-config
2922799191 3886 /usr/lib/X11/C/print/models/
HPDESIGNJ650C_650CM-PS/model-config
2847284334 3886 /usr/lib/X11/C/print/models/
HPDESIGNJ750C_750CM-PS/model-config
3917093393 3876 /usr/lib/X11/C/print/models/
HPDESIGNJ755CM-PS/model-config
1683316934 2567 /usr/lib/X11/C/print/models/HPDESKJ1200C-PS/
model-config
3014505256 989 /usr/lib/X11/C/print/models/HPDESKJ1200C/
model-config
1134121487 2563 /usr/lib/X11/C/print/models/
HPDESKJ1600C_1600CM-PS/model-config
489000303 984 /usr/lib/X11/C/print/models/
HPDESKJ1600C_1600CM/model-config
926078363 2547 /usr/lib/X11/C/print/models/HPLJ3-PS/
model-config
775801039 1067 /usr/lib/X11/C/print/models/HPLJ3/
model-config
181229960 2563 /usr/lib/X11/C/print/models/HPLJ3D-PS/
model-config
2210782582 1115 /usr/lib/X11/C/print/models/HPLJ3D/
model-config
4203157258 2549 /usr/lib/X11/C/print/models/HPLJ3P-PS/
model-config
751788714 1101 /usr/lib/X11/C/print/models/HPLJ3P/
model-config
2448762207 2565 /usr/lib/X11/C/print/models/HPLJ3Si-PS/
model-config
1686258782 1071 /usr/lib/X11/C/print/models/HPLJ3Si/
model-config
1874604788 2575 /usr/lib/X11/C/print/models/HPLJ4+_4M+-PS/
model-config
804491367 1155 /usr/lib/X11/C/print/models/HPLJ4+_4M+/
model-config
2516082615 2553 /usr/lib/X11/C/print/models/HPLJ4L_4ML-PS/
model-config
1375052195 1120 /usr/lib/X11/C/print/models/HPLJ4L_4ML/
model-config
302422992 2561 /usr/lib/X11/C/print/models/HPLJ4P_4MP-PS/
model-config
43023229 1128 /usr/lib/X11/C/print/models/HPLJ4P_4MP/
model-config
1040836525 2581 /usr/lib/X11/C/print/models/
HPLJ4Si_4SiMX-PS/model-config
1065991425 1134 /usr/lib/X11/C/print/models/HPLJ4Si_4SiMX/
model-config
584526430 3202 /usr/lib/X11/C/print/models/HPLJ4V_4MV-PS/
model-config
3740414111 1394 /usr/lib/X11/C/print/models/HPLJ4V_4MV/
model-config
2658697722 2557 /usr/lib/X11/C/print/models/HPLJ4_4M-PS/
model-config
1448554959 1137 /usr/lib/X11/C/print/models/HPLJ4_4M/
model-config
985089934 3151 /usr/lib/X11/C/print/models/
HPLJ4color_4Mcolor-PS/model-config
2987031699 913 /usr/lib/X11/C/print/models/
HPLJ4color_4Mcolor/model-config
445984929 2561 /usr/lib/X11/C/print/models/HPLJ5L_5ML-PS/
model-config
2589395771 1127 /usr/lib/X11/C/print/models/HPLJ5L_5ML/
model-config
2378352748 2575 /usr/lib/X11/C/print/models/HPLJ5N_5MN-PS/
model-config
2805417211 1711 /usr/lib/X11/C/print/models/HPLJ5N_5MN/
model-config
2362823217 2561 /usr/lib/X11/C/print/models/HPLJ5P_5MP-PS/
model-config
3092406659 1127 /usr/lib/X11/C/print/models/HPLJ5P_5MP/
model-config
1051246488 2581 /usr/lib/X11/C/print/models/
HPLJ5Si_5SiMX-PS/model-config
2936734523 1358 /usr/lib/X11/C/print/models/HPLJ5Si_5SiMX/
model-config
558673228 2571 /usr/lib/X11/C/print/models/HPLJ5_5M-PS/
model-config
3511996249 1707 /usr/lib/X11/C/print/models/HPLJ5_5M/
model-config
3965984278 3156 /usr/lib/X11/C/print/models/
HPLJ5color_5Mcolor-PS/model-config
3894154188 918 /usr/lib/X11/C/print/models/
HPLJ5color_5Mcolor/model-config
3747772473 838 /usr/newconfig/etc/X11/C/print/attributes/
document
4059755377 692 /usr/newconfig/etc/X11/C/print/attributes/job
1075723481 133 /usr/newconfig/etc/X11/C/print/attributes/
printer
TechPrintServ.TPS-GER-I-SERV,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
3897938825 2048 /usr/lib/X11/de_DE.iso88591/print/models/
HPLJ5000N/fonts
2998329733 1024 /usr/lib/X11/de_DE.iso88591/print/models/
HPLJ5000N-PS/fonts
2626225633 1024 /usr/lib/X11/de_DE.iso88591/print/models/
HPDESKJ2500C-PS/fonts
TechPrintServ.TPS-FRE-I-SERV,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
3897938825 2048 /usr/lib/X11/fr_FR.iso88591/print/models/
HPLJ5000N/fonts
2998329733 1024 /usr/lib/X11/fr_FR.iso88591/print/models/
HPLJ5000N-PS/fonts
2626225633 1024 /usr/lib/X11/fr_FR.iso88591/print/models/
HPDESKJ2500C-PS/fonts
TechPrintServ.TPS-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
3986603607 6221 /usr/dt/share/man/man5.Z/tps.5
1447785863 3319 /usr/dt/share/man/man1m.Z/tpsconfig.1m
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHSS_20140 PHSS_20142
s800: 11.00: PHSS_20140 PHSS_20142
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_16652 PHSS_18431 PHSS_20143 PHSS_22750 PHSS_25758
Equivalent Patches:
PHSS_27195:
s700: 11.11
s800: 11.11
Patch Package Size: 1120 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_27194
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27194.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27194. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_27194.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27194.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27194.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1. This patch supplies new versions of document, job and
printer in the /usr/newconfig/etc/X11/C/print/attributes
directory. These files have to be merged with those
present in /etc/X11/C/print/attributes directory.
2. To use this patch, the user should modify the dtlogin
config file in /etc/dt/config/Xconfig.
If /etc/dt/config/Xconfig is not present, please copy
from /usr/dt/config/Xconfig to /etc/dt/config/Xconfig.
Set the resource "Dtlogin*authorize: False". Then
restart the dtlogin daemon process or reboot the system.
3. There is another problem not fixed with this
patch. "dtpdm" may fail to start from "dtpdmd"
in some circumstances. When CDE is used with
"Xauthorization" true (which is the default
behaviour),"dtpdm" may not be authorized by the
X Display server, hence it failed with X
authorization error. This is due to the design of
"dtpdmd", therefore HP is considering to fix in
the future release.
There are several ways to get workaround this
error such as
- Use "xhost" command to allow Xclient to
connect to X display
Ex: $ xhost + name-of-localhost
- Modify /etc/X0.hosts
- Uncomment "Dtlogin*authorize: False" in
/etc/dt/config/Xconfig
When /etc/dt/config/Xconfig is not present, copy
it from /usr/dt/config/Xconfig and do the
modification. After modifying Xconfig file, restart
the dtlogin daemon process,or restart the system.
The reason for this customization is that the
"dtpdm" which is invoked by "dtpdmd" is NOT the
process of the user who has currently logged in CDE,
hence it doesn't have the proper authorization to
access the Xdisplay.
Please consider carefully which of these workarounds
will be suitable for your enviornment. Please refer
to xauth(1), xhost(1) and other materials about
"X Authorization".
Warning: Setting Dtlogin*authorize=False greatly
reduces control over the system and is
_not_ recommended.
-----End of Document ID: PHSS_27194------------------------------------------
Document ID: PHSS_27067
Date Loaded: 20020719
Title: s700_800 11.00 OV ITO6.0X NT Agent Patch A.06.11
Patch Name: PHSS_27067
Patch Description: s700_800 11.00 OV ITO6.0X NT Agent Patch A.06.11
Creation Date: 02/07/17
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView IT/Operations 6.0
Filesets:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27067
Symptoms:
PHSS_27067:
- SR: 8606227840
Variables in the template default message key are not
resolved for unmatched messages.
- SR: 8606233602
If using a pattern like '<*.prefix>ERR<*.suffix>', the
prefix variable will get assigned a wrong text if it
should be empty.
- SR: 8606236271
opcmona.exe might report an error that ov.dll can't be
found or the MIB monitoring doesn't work at all.
And the trap interception may fail.
- SR: 8606242614
Messages are incorrectly suppressed by the logfile
encapsulator if "suppress identical output messages" is
specified and the messages differ only in the values of
<$LOGFILE> and/or <$LOGPATH>.
- SR: 8606244523
When using the syntax <`script`> in the logfile template
and the script returns the same logfile name twice, the
opcle will abort.
- SR: 8606244582
The distribution/deployment of action/command/monitor
binaries might fail due to some of them being used.
- SR: B555012827
Support Windows XP with the VPO Windows agent.
Please see the "Defect Description" section below for
further details.
- SR: B555013157
The agent installation didn't show the installed
agent version all the time, showing the
version would be helpful to clearly say that the
correct version is installed.
- SR: B555013326
The monitor agent might not report when a performance
monitoring instance is missing.
And in case it reports the first time it doesn't
report it when the instance appears and then disappears
again.
- SR: B555013345
The agent installation may abort with Dr. Watson after
everything is done.
- SR: B555013371
Sometimes the new scheduled action template configuration
is not loaded after a distribution. Instead, the old
scheduled actions are still started.
- SR: B555013408
opcmona and itodiag/OvNtDiag might abort with Dr. Watson
when retrieving performance data.
- SR: B555013435
The message agent opcmsga hangs unpredictably. This is
more likely to happen on systems with a very high ICMP
traffic.
- SR: B555013510
Autoactions are not executed on NT systems in a NAT
environment.
- SR: B555013534
When the "HP ITO Installtion Server" service
gets started you may find the following event in your
Application event log:
EventID: 0xC0001B68 (7016) - The HP ITO Installation
Server service has
reported an invalid current state 0.
- SR: B555013540
opcsetup may report:
E-> Error from opc_ipinterf_getaddrs.
E-> Error from InitSetup.
E-> Setup program aborted.
- SR: B555013719
Message agent doesn't stop message buffering when the
management server is available again after a network
outage, fixed DNS problem or similar.
This can happen when the agent restarts/the machine
reboots during the network problem occured.
- SR: B555013757
The API interface opcmsg(3) or opcagtmsg_send(3)
may fail with error: OPC_ERR_CANT_INIT.
- SR: B555013796
When using itomserv.exe/opcntmserv.exe to list services
or devices where the Service Name or Description contains
Japanese Multibyte characters it may happen
that the text is truncated wrongly. The leads to a wrong
last character and maybe even to problem when displaying
this text in the Java or Motif UI.
- SR: B555013872
Agent installation sets full access rights for "HP ITO
account" on files in %SYSTEMROOT%\system32
(opcauth.dll and psapi.dll).
- SR: B555013891
In MoM environments, opcmsga does not return action
responses to SECONDARY managers, if their name is not
resolveable.
- SR: B555013936
agent installation may fail with a high number of the
following messages in the inst.log:
T-> Tracing information: Can't get status for service:
...
It can even happen that the install script reports
successfull but nothing gets installed.
This may happen when you have installed HP OpenView
Internet Services and not all MS Internet Information
Services.
- SR: B555013965
The pdh.dll delivered with the agent
has a memory leak as it is described
in Microsoft article: Q263221.
- SR: B555014083
When using the Windows Performance Counter functionality
with the montior agent, it may happen that the process
opcmona.exe shows memory leaks, handle leaks or even
crashes.
When using on a system where Oracle is installed it may
cause error messages in the Oracle log, because the
opcmona tries to retrieve performance information from
Oracle even if you do not monitor Oracle performance
values at all.
The same applies to itodiag.exe/OvNtDiag.exe.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
- SR: B555014101
Monitor agent may report error OPC30-783 and the
initialisation of the first template/policy using Windows
Performance data fails.
- SR: B555014132
During a distribution the agent may report an error like:
ITO responsible manager configuration. (OpC30-1203)
Cannot open file \usr\OV\tmp\OpC\cfgchg.
System Error Number: 13 (d) - The data is invalid.
(OpC20-63)
- SR: B555014212
opcle may report:
[ntle.c:3670]: OpC internal error: Cannot generate
message 1500 of set 0
System Error Number: 1966234 (1e009a) - (OpC0-1500)
- SR: B555014281
When using the Windows agent SDK (opcapi.h and
opcapi.lib) you may get linker unresolved symbol errors
when using one of the following API calls:
opcdata_type, opcdata_ldel, opcdata_ladd,
opcdata_lget_len, opcdata_lget_str, opcdata_lset_str,
opcdata_generate_id, opcdata_get_error_msg,
opcdata_lget_long, opcdata_lset_long, opccdata_clear,
opc_version
- SR: B555014319
When reading Windows Event logs the opcle.exe and
services.exe may start taking a lot of CPU time for a
longer period of time.
- SR: B555014328
opcevti.exe may abort when using <$x>.
- SR: B555014378
opcctla may crash when doing a distribution on a Windows
XP node in a NAT environment.
- SR: B553000162
After opcagt -stop, opcagt -status does tell that the
control agent does not run although it is running and
sometimes you get following error in the message browser:
ouput of kill -0 differs from internal pids-table for
index <number> (OpC30-1094)
PHSS_26050:
- SR: 8606222554
Certain policies in VPW do not work as expected, for
example:
VP_WIN-WINS-FwdAllInformation
VP_WIN-WINS-FwdAllWarnError
VP_WIN-DHCPCl_FwdAllInfo
VP_WIN-DHCPCl_FwdAllWarnError
This problem can also occur for VPO during condition
matching, matching the application and object attributes
are now case sensitive. For example, a message with
application "TEST" goes through but with
application "tEST" is unmatched.
- SR: 8606228146
opcntmserv.exe/itomserv.exe uses fixed width to display
the service names.
The defined values are 18 characters for the service
name and 25 for the description.
- SR: 8606228694
The logfile encapsulator often reports the message:
"The NT Eventlog <log name> was changed (cleared) and
the current position is no longer reachable.
ITO starts reading from the beginning of the Eventlog.
Some records might be lost. (OPC 30-149)"
- SR: B555007980
Local automatic actions are started immediately, even
though agent MSI is enabled in divert mode and Immediate
Local Automatic Action box is not checked.
- 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: B555010966
A message key relation containing <*> does not always
match message keys correctly. This results in messages
not being acknowledged when they should.
- SR: B555011638
Pattern matching can't match new line of multiline
messages.
- 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: B555012136
opcle stops in case one of the Windows 2000 event logs
is corrupt. Windows API error code is 1500.
- SR: B555012394
the NT performance monitoring might fail or report
that it can't find a performance counter or object.
- SR: B555012458
When using localized performance counter names instead of
using the default (english) names it might be that you
get messages that the counter is not found.
This can happen in case the localized counter name
contains special characters.
- SR: B555012508
The environment variable OvAgentDir might be not found
when using a SPI which is released after the release date
of OVO 7. Therefore the SPI may not work correctly.
- SR: B555012562
The control agent might crash while processing a
distribution. This only happens in very special
situations. So far it has been seen in environments
which are using firewalls.
- SR: B555012703
The installation of the NT agent might hang. The last
line in the inst.log reports:
I-> Service HP ITO Installation Server does not exist. No
need to delete it.
- SR: B555012871
The process opcle.exe might show a memory growth while
processing the Windows event log.
- SR: B555012930
When Oracle is installed on a Windows 2000/NT 4 system,
the command opcagt -start|-stop may take very long to
complete or even abort.
- SR: B555013096
several itoprocs.exe might hang instead of finishing.
PHSS_25472:
- 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: B555012022
After installing the NT agent on none
English Windows NT systems it may happen that the NT
Performance Monitoring as well as the tool itodiag
doesn't work correctly any longer.
The monitor agent sends "can't retrieve value for ..."
for all NTPerfMon templates and the options /cpuload and
/processes fail with itodiag.
This effect can occur on none English Windows NT systems
which have none English performance object/counter names,
this is true for German, French and so on. It is not true
for Japanese (this uses English names).
Additionaly these systems have to have a pdh.dll with
a version 5 or higher in their %SYSTEMROOT%\system32
directory. With a pdh.dll version 4 the problem doesn't
occur.
PHSS_25090:
- 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_24051:
- 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_22884:
- 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_22009:
- 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_27067:
- SR: 8606236271
Any SNMP related action on a node might fail in case the
ovsnmp.dll might be found somewhere in the %PATH%.
The reason is that the agent assumes that HP OpenView
Network Node Manager is installed as soon as this
dll can be found in the PATH.
This check is more forced now.
The agent checks the registry whether NNM is installed
or not and based on this the SNMP interface is
selected.
- SR: 8606242614
The variables <$LOGFILE> and <$LOGPATH> were replaced
after the suppression rules were evaluated. Therefore the
comparison did not use the actual logfile name or path,
but compared the string "<$LOGFILE>" or "<$LOGPATH>".
- SR: 8606244523
The opcle aborts when a <`script`> returns a logfile name
twice. This is because of referencing and handling the
same file twice.
To fix this, the opcle checks whether the same logfile
has been returned already and when adding to the internal
list, each logfile gets added exactly once.
- SR: B555012827
Together with the "Windows XP" support for the VPO
Windows agent, there are some changes that are results of
changes in the way "Windows XP" works, these
changes/issues are documented below.
As default templates for "Windows XP" you can
use the same than for "Windows 2000".
List of all known changes/issues:
- Users created by the agent setup (HP ITO account &
opc_op) appear on the XP Welcome Screen
- Dr. Watson shows internal program name instead of
binary name.
This may affect you when troubleshooting processes
should be necessary.
- "itouser /local" doesn't work correctly, but
returns errors.
The tool can't be used with this switch under
Windows XP.
- Mapped network drives no longer visible to all users
- Windows XP is capable to really separate several
user environments
and therefore also the network drives mapped by one
user can't be seen by the other one
- This is a new functionality of Windows XP and
may effect user who have shared tools
placed on network drives and using them in scripts
executed by the agent.
- To avoid this don't use mapped network drives
but the complete network path to access such tools.
- Bug in snmptrap.exe (Microsoft Article Q319680, see
http://support.microsoft.com)
Microsoft confirmed this to be bug in Windows XP and
will be fixed with the first service pack.
Microsoft may also provide a HotFix for users
needing this functionality.
The result is that you can't do trap interception
or MIB monitoring.
- SR: B555013326
The monitor agent might not report a missing
performance monitoring instance.
There are two different scenario:
1. performance monitoring without wildcards (?/*)
-> monitor agent might not report a missing
instance at all
2. performance monitoring with wildcards
-> monitor agent reports the missing instance
for the first time
but doesn't report it when the instance
(e.g. a process) appears and the disappears again
Both issues are fixed by changing the internal
triggers and return codes to indicate the missing
instance.
- SR: B555013345
opcsetup.exe may end with a Dr. Watson after
successfully installing the agent.
The problem only occurs on very few systems.
On these machines the Windows APIs abort when freeing
memory.
The behavior is changed to free differently.
- SR: B555013408
opcmona and itodiag/OvNtDiag may abort with a Dr. Watson
when they access performance data.
It seems that the API call PdhMakeCounterPath has on
some systems problems and aborts.
So the functionality provided by the call have been
replaced by a function written by our own.
- SR: B555013435
One thread tried to read from a socket while another
thread closed it. This could happen due to missing
locking of global data. This data is now guarded by a
mutex.
- SR: B555013534
The "HP ITO Installation Server" service doesn't
set the status correctly at startup and therefore
it reports an invalid status when the operating
system asks for it.
- SR: B555013540
Cause is a problem in the registry
That a TcpIP Device is there but
doesn't contain any entry for it's IPAddress.
Devices with such behavior are skipped now.
- SR: B555013719
Message agent remains in buffering mode even when
the management server is available again.
The reason is that the agent wasn't able to resolve
the management server name to an IP address at startup
and the agent doesn't try again during runtime.
This has been fixed by checking for a resolvable name
every time a message should be buffered till the name can
be resolved, after this the normal checkalive mechanism
which handles buffered message takes place.
- SR: B555013757
The APIs opcmsg(3) or opcagtmsg_send(3) assume
that the agent has been installed to the same
drive letter than they are running on.
In any other case they will fail to init, because
the message catalog can't be found and so the error
OPC_ERR_CANT_INIT is returned.
The APIs set and reset the drive in order to find
the correct message catalog now.
- SR: B555013796
itomserv.exe / opcntmserv.exe do truncate display and
service names and with Japanese multibyte characters it
can happen that the text is truncated exactly in the
middle of such a character.
This wrong character or better first part of a multibyte
character confuses the Java and the Motif UI and leads to
problems when calling this application.
With this version the truncation is done by using a
function which is aware of multibyte characters and
truncates them correctly.
- SR: B555013872
Agent installation sets unrequired file permissions
on files in %SYSTEMROOT%\system32 for "HP ITO account".
These unrequired file permissions have been removed
and should disappear when installing this patch.
- SR: B555013891
Even if the IP address of the management server was
specified in the mgrconf file, it was not used except for
the primary manager. This behaviour was changed to give
the mgrconf file precedence over name resolution.
- SR: B555013936
agent installation may fail with many of such messages:
T-> Tracing information: Can't get status for service: ..
in the inst.log file.
The install script may even report that the installation
was successfull but it wasn't.
The cause for this problem is that the installation tries
to stop MS Internet Information Services and OpenView
Internet Services in case OVIS has been installed and
fails when not all MS Internet Information Services are
installed. It then tries to stop the missing services in
a loop and in the end just dies or even brings a Dr.
Watson error message.
This fix just ignores the missing service and goes to the
next one.
- SR: B555013965
The memory leak which can occur as described in Microsoft
article Q263221. Has been fixed by Microsoft
by providing a new pdh.dll, which is included in the
patch.
- SR: B555014083
When accessing Windows Performance Counters via
templates or policies it is possible that the
opcmona shows a memory/handle leak or even crashes.
This is caused by the way the opcmona accesses the
Windows performance data. For backward compatibility
with the Performance Data Helper (PDH) DLL version 4, the
montior agent has to deal with the situation that this
DLL doesn't offer the functionality to do a query
for several performance instances at once by using
wildcards.
With the policies you can for instance monitor the
following:
\LogicalDisk\% Free Space\?\C: or even
\LogicalDisk\% Free Space\*
Internally the montior agent has to retrieve all
instances for the LogicalDisk object now. And then can
start monitoring. The retrival of these instances is done
via the API call PdhEnumObjects. This API call
causes the load of all available performance dlls, even
when they are not needed for the monitoring.
In case one of these DLLs has a leak or a bug causing a
crash, the monitor agent shows this behavior.
Version 5 of PDH offers a new function which allows
the collection of multiple instances with one call and
so avoids using PdhEnumObjects and this avoids the load
of all performance DLLs. The result is that the monitor
agent doesn't load a performance dll as long as you don't
use the performance object this dll is registered for.
Please note that as soon as you access a performance
object where the assigned performance dll has a problem,
you will see this problem in the monitor agent.
You can test whether the problem is caused by the monitor
agent or by a loaded performance dll by disabling all
templates/policies using performance objects and restart
the agent (opcagt -start).
After this enable the disabled templates/policies one
by one again. Each time you enabled one, restart the
agent. As soon as the monitor agent shows the problem
again. Check the template/policy for the monitored
performance object and you may then contact the provider
of this performance object for support.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
This can occur when there are only spaces in
one of the schedule fields (Minute, Hour, Day of the
Month, Month, Year, Day of the Week).
You can verify this by going to the conf/OpC directory on
the node and doing an opcdcode monitor. When
there are entries like WEEKDAY " " the problem can occur.
Now the monitor agent treats sequences of spaces like
an empty string that is a wildcard and uses all valid
values in the possible range.
For WEEKDAY this is 0-6.
- SR: B555014101
Monitor agent may report error OPC30-783 and the
initialisation of the first template/policy using Windows
Performance data fails.
This can be caused by a none critical problem in the
Windows registry. The monitor agent queries for the
languages, for which there are counter and object names.
When accessing some languages the system returns "NOT
FOUND" and the monitor agent internally reports this
errors and this causes the first template using this
source type to fail. All subsequent call will pass, since
the query of the registry is done only once to get all
performance counter and object names.
The opcmona ignores this error completely now.
- SR: B555014132
During a distribution the agent may report error number
OPC30-1203/OPC20-63 when trying to access the cfgchg
file.
The cause for this problem is that there are several
processes trying to get exclusive access to this file
at the same time. The problem has been fixed by doing a
retry for 10 times in case the error should occur with a
delay of one second.
- SR: B555014212
opcle may report:
[ntle.c:3670]: OpC internal error: Cannot generate
message 1500 of set 0
System Error Number: 1966234 (1e009a) - (OpC0-1500)
The cause is the a wrong error number in the logfile
encapsulator itself.
- SR: B555014281
When using the Windows agent SDK (opcapi.h and
opcapi.lib) you may get linker unresolved symbol errors.
Some of the APIs were not exported in the DLL and LIB and
therefore you get linker errors.
The missing exports have been added now.
- SR: B555014319
When reading Windows Event logs the opcle.exe and
services.exe may start taking a lot of CPU time for a
longer period of time.
The cause was a misleading return code from a Windows API
which says the event log is on it's end, but it wasn't so
the logfile encapsulator permanently looped on the same
event instead of proceeding with the next one.
This behavior has been fixed by doing some additional
checks whether the end of the event log has been really
reached. If not, the current event will be skipped.
- SR: B555014328
opcevti.exe may abort when using <$x>.
This issue is caused by traps having a timestamp
not in the range between 0 and 2147483647.
In case such a trap is received, the timestamp will be
reset to 0 now.
for SR's not listed in this section please see
the list of symptoms
PHSS_26050:
- SR: 8606222554
The condition test for the message attributes
application, object and message group are always done
case sensitive, therefore a message with the application
"TEST" matches but "tEST" it does not match.
With this patch an opcinfo flag is introduced, which
allows to switch between case sensitive and case
insensitive check.
flag : OPC_COND_FIELD_ICASE
type : boolean
default: FALSE
By setting this to true the policies mentioned above will
work.
- SR: 8606228146
opcntmserv.exe/itomserv.exe is only able to display
service names with a specific length of less than
18 characters.
This patch introduces a new option for the program
which allows to set the length via command line switch.
The new switch is called /width and takes as parameters
the width of the service name and the width of the
description.
Following example list the service name with a width
of 30 characters and completely hides the description.
> itomserv.exe /list s /width 30 0
The width switch is useful together with the /list and
/status option.
- SR: 8606228694
The logfile encapsulator often reports that the
NT event log has changed/cleared and therefore
the current position is no longer reachable and it
starts from beginning.
This was a problem in the handling of several different
templates/policies handling the same NT event log.
- 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: B555010966
The processing of the key relation is wrong for the log
file encapsulator. The problem is that all unresolved
entries followed by a resolved entry are removed.
Other unresolved entries are kept as is.
- SR: B555011638
VPO could not match for for new line of multi line
messages. Following changes have been made to allow this:
It is now possible to use ^M (\r) as field separator.
Introduced a new pattern </> to match any number of line
breaks (UNIX style \n or NT style \r\n) and <n/> to match
exactly n line breaks, for example <1/> will match
exactly one line break.
This change works only for sources that already can
create multi line messages (for example opcmsg or NT
event log), it does not allow multi line logfile
encapsulation.
This change requires a fix on the management server and
the agent. Therefore a patch on the management server and
a patch for the agent is required to use the new
functionality.
- SR: B555012136
Improved error handling, the opcle will send a message
about the corrupted event log and will stay alive.
As soon as the event log gets cleared the opcle will
again start monitoring.
- SR: B555012394
The NT performance monitoring might fail or report
that it can't find a performance counter or object.
Systems with such problems can have the following
problems:
1.they are localized and the registry key
HKEY_LOCAL_MACHINE,
SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Perflib\<langid>\Counter
does not exist
the same can happen to english Windows systems
with several languages installed
2.an application corrupted the name list for
the performance counter and objects
both problems are fixed by improving the error handling.
in case 1 the language which can't be read is just
ignored, this might lead to problems in case the language
which could not be read is the current system language,
because then the performance objects are not found.
For case 2 the monitor agent counts the performance
counter and objects found per language and compares all
numbers in case of a mismatch it reports an error. It
still tries to do performance monitoring, because the
inconsistency might even not affect the monitoring.
- SR: B555012458
When using localized performance counter names the agent
reads the template/policy in it's internal codeset which
may not match to the external system codeset.
This may lead to problems when the counter names
contains special characters, which are not part of the
first 128 characters in the ASCII codeset.
In this case a convertion is done from internal to
external codeset before doing the performance monitoring.
- SR: B555012508
The environment variable OvAgentDir is introduced
with OVO 7 for Microsoft Windows agents in order to
support SPIs and also customer developing their own
tools to have easier access to the base installation
directory of the Windows agent.
The changes which have been made for this variable have
been back merged to VPO A.06.x and VPW A.06.x to
make it possible to make SPIs compatible with these old
versions as well as with OVO 7.
- SR: B555012562
The control agent might abort with Dr. Watson message
while it processes a distribution request.
The problem might only occur from time to time because
it depends on the system, the data transfer rate
between agent and server and other factors.
In the end it's a timing issue between two threads which
should end in a specific order and especially in
environments with firewalls it seems that the threads
often end in the wrong order which leaded to the
crash because of pointers used in both threads.
The issue has been fixed by defining the pointer
differently so that they are not lost in case
a thread closes.
- SR: B555012871
The process opcle.exe might show a memory growth while
it is processing the Windows event log.
This can happen in case there are event log message
without message dlls to format the entries from the
event log to a normal format.
In such a case the opcle.exe uses a default format
and in this case a memory leak of around 30 bytes per
message can occur.
- SR: B555012930
The command opcagt -start/-stop might take very long
or even aborts. This can happen in case an Oracle DB
is installed. The problem itself is caused by the
Oracle performance dll which collects Oracle
performance data. This dll is used indirectly
because process information are collected while
using the performance registry and therefore Windows
loads and tries to open the Oracle performance counter.
It seems that these takes either very long or leads
to an abort.
With this version the process information are collected
differently by using a different Windows API (psapi)
and this should avoid this problem.
- SR: B555013096
itoprocs.exe might hang when several itoprocs.exe
are running at the same time.
The reason is a dead lock between all of them.
This is fixed by using a central mutex to protect
critical areas.
for SR's not listed in this section please see
the list of symptoms
PHSS_25472:
- 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: B555012022
As described in syptoms the problem is related to the
used pdh.dll version. There is a complete change between
version 4 and 5. With version 4 you always have to use
English performance object and counter names even on none
English Windows NTs. With version 5 you always have to
use the localized object/counter names.
This problem is fixed by a check for the version of this
pdh.dll and depending on this the performance
object/counter names are translated from any installed
language to the local language.
for SR's not listed in this section please see
the list of symptoms
PHSS_25090:
- 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_24051:
- 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_22884:
- 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_22009:
check the list of the symptoms
Enhancement:
No
SR:
R555011075 R555003313 B555014378 B555014328 B555014319
B555014281 B555014212 B555014132 B555014101 B555014093
B555014083 B555013965 B555013936 B555013891 B555013872
B555013796 B555013757 B555013719 B555013540 B555013534
B555013510 B555013494 B555013435 B555013408 B555013371
B555013345 B555013326 B555013157 B555013096 B555013075
B555012930 B555012871 B555012827 B555012703 B555012562
B555012508 B555012458 B555012394 B555012136 B555012022
B555011990 B555011990 B555011979 B555011979 B555011638
B555011594 B555011540 B555011510 B555011505 B555011497
B555011436 B555011422 B555011256 B555011108 B555010980
B555010966 B555010948 B555010899 B555010899 B555010879
B555010819 B555010620 B555010563 B555010449 B555010324
B555010186 B555010038 B555010012 B555009756 B555009745
B555009740 B555009712 B555009553 B555009481 B555009412
B555009388 B555009360 B555009340 B555009212 B555009201
B555009193 B555009155 B555009153 B555009120 B555009099
B555008912 B555008754 B555008729 B555008663 B555008526
B555008314 B555008309 B555008220 B555008220 B555008180
B555007980 B555007966 B555007883 B555007847 B555007840
B555007752 B555007619 B555007602 B555007549 B555007478
B555007056 B555005125 B553000162 8606244582 8606244523
8606242614 8606236271 8606233602 8606228694 8606228146
8606227840 8606222554 8606214799 8606213476 8606212295
8606208283 8606206616 8606205415 8606188773 8606183491
8606181988 8606180891 8606179902 8606171814 8606161695
8606140211
Patch Files:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opc_pkg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/unzip.exe
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/unzip.txt
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opc_inst.bat
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opc_pre.bat
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opcsetup.inf
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/monitor/itoprocs.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/monitor/sms_chk.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/monitor/mf_service.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/mfluse.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itomserv.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itoreg.cfg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/opcdf.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/opcps.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itodiag.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/pdh.dll.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itokill.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itoreg.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itosdown.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itouser.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/opcprfls.exe.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/mf_app.bat.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
AgentPlatform
what(1) Output:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opc_pkg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/unzip.exe:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/unzip.txt:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opc_inst.bat:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opc_pre.bat:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/opcsetup.inf:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/monitor/itoprocs.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/monitor/sms_chk.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/monitor/mf_service.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/mfluse.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itomserv.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itoreg.cfg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/opcdf.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/opcps.bat.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itodiag.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/pdh.dll.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itokill.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itoreg.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itosdown.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/itouser.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/RPC_DCE_TCP/cmds/opcprfls.exe.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
A.06.11/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:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
4235881212 6321115 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/opc_pkg.Z
3162183940 113152 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/unzip.exe
1939298735 508 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/unzip.txt
4115030442 1664 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/opc_inst.bat
2405569119 1715 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/opc_pre.bat
578689850 133 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/opcsetup.inf
3979346984 5970 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/monitor/
itoprocs.exe.Z
345227238 132 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/monitor/
sms_chk.bat.Z
3876037765 129 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/monitor/
mf_service.bat.Z
3018594274 3925 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
mfluse.exe.Z
1367046952 53057 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
itomserv.exe.Z
1586237090 188 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
itoreg.cfg.Z
2003580432 38 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
opcdf.bat.Z
849569434 41 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
opcps.bat.Z
455322206 26202 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
itodiag.exe.Z
2576066882 103311 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
pdh.dll.Z
3515256379 6863 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
itokill.exe.Z
1902029996 13775 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
itoreg.exe.Z
2383059122 46676 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
itosdown.exe.Z
129511429 53147 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
itouser.exe.Z
2347494828 10116 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
opcprfls.exe.Z
1588307382 751 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/ms/intel/nt/A.06.11/RPC_DCE_TCP/cmds/
mf_app.bat.Z
751817077 6473 /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_26050 PHSS_25472 PHSS_25090 PHSS_24051 PHSS_22884 PHSS_22009
Equivalent Patches:
ITOSOL_00152:
sparcSOL: 2.6 2.7 2.8
PHSS_27066:
s700: 10.20
s800: 10.20
Patch Package Size: 6730 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_27067
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27067.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27067. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_27067.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27067.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27067.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
(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.
If you are running VPO in a MC/ServiceGuard
installation:
- Note, that only files on the shared disk volume
at /var/opt/OV/share will be patched. Therefore
install the patch on one cluster node while the
shared disks are mounted. The server processes
may be running during patch installation.
- It is not necessary to install this patch on all
cluster nodes. Even if the software inventory on
the other cluster nodes will not be updated, the
patched files will be available there when the
shared disk is switched to them.
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_27067 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.
If you are running VPO in a MC/ServiceGuard
installation make sure to mount the shared
disks at the node and only at the node that
had them mounted during patch installation.
Otherwise restoration of the original files
onto the shared disk will fail.
# swremove PHSS_27067
-----End of Document ID: PHSS_27067------------------------------------------
Document ID: PHNE_27201
Date Loaded: 20020719
Title: s700_800 11.00 IGELAN 1000Base-SX/T B.11.00.04 patch
Patch Name: PHNE_27201
Patch Description: s700_800 11.00 IGELAN 1000Base-SX/T B.11.00.04 patch
Creation Date: 06/03/02
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
HP PCI Gigabit Ethernet Driver IGELAN B.11.00.04
Filesets:
IGELAN-DRV.IGELAN-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,v=HP
IGELAN-DRV.IGELAN-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_27201: HANG
Category Tags:
defect_repair general_release critical halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_27201
Symptoms:
PHNE_27201:
1. JAGae27935: Certain applications using UDP
( eg. NFS ) may encounter timeouts/hangs due
to bad UDP checksums.
2. JAGae23592: lanadmin -g mibstats <ppa> requires
user to hit Carriage Return to complete.
3. JAGae28274: Setting ifAdminStatus up/down on
igelan cards causes system to hang.
Defect Description:
PHNE_27201:
1. JAGae27935: The checksum calculation done by
the firmware is incorrect for certain message sizes
for UDP fragments.
Resolution: The firmware is fixed to handle the
scenario correctly.
2. JAGae23592: lanadmin requires the driver
shared library to define a function called
"disp_continue()". The igelan driver does not
currently define/use this function in its mibstats
display function, which is the cause of
this defect.
Resolution: The igelan driver now has the function
called disp_continue.
3. JAGae28274: System hang due to negative
spinlock depth.
Resolution: A locking bug in the driver has been
fixed to resolve the negative spinlock depth
problem.
Enhancement:
No
SR:
8606263610 8606259274 8606263948
Patch Files:
IGELAN-DRV.IGELAN-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,
v=HP:
/usr/conf/lib/libigelan.a
IGELAN-DRV.IGELAN-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,
v=HP:
/usr/lib/lanadmin/libdsigelan.1
/usr/lib/nls/msg/C/dsigelan.cat
what(1) Output:
IGELAN-DRV.IGELAN-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,
v=HP:
/usr/conf/lib/libigelan.a:
igelan_ilan Version: 1 Jun 5 2002
igelan Revision: B.11.00.06 Jun 5 2002
IGELAN-DRV.IGELAN-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,
v=HP:
/usr/lib/nls/msg/C/dsigelan.cat:
None
/usr/lib/lanadmin/libdsigelan.1:
None
cksum(1) Output:
IGELAN-DRV.IGELAN-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,
v=HP:
2948480989 593446 /usr/conf/lib/libigelan.a
IGELAN-DRV.IGELAN-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_64,
v=HP:
2103510366 9244 /usr/lib/nls/msg/C/dsigelan.cat
2876826284 53248 /usr/lib/lanadmin/libdsigelan.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 670 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 PHNE_27201
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_27201.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_27201. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_27201.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_27201.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_27201.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_27201------------------------------------------
Document ID: PHNE_26369
Date Loaded: 20020719
Title: s700_800 11.11 IGELAN 1000Base-SX/T B.11.11.[02-04] patch
Patch Name: PHNE_26369
Patch Description: s700_800 11.11 IGELAN 1000Base-SX/T B.11.11.[02-04] patch
Creation Date: 02/05/08
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
HP PCI Gigabit Ethernet Driver IGELAN B.11.11.02 B.11.11.04
Filesets:
IGELAN-DRV.IGELAN-KRN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,v=HP
IGELAN-DRV.IGELAN-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,v=HP
IGELAN-DRV.IGELAN-RUN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,v=HP
IGELAN-DRV.IGELAN-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_26369: PANIC HANG
Category Tags:
defect_repair hardware_enablement general_release critical
panic halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_26369
Symptoms:
PHNE_26369:
1. JAGae24114: Applications that are modeled on a strict
request/response behavior might see packet delays
for about one second when they are the sole traffic
generators over an igelan interface. This defect is
seen only with the igelan product in Application
Release of March 2002 (B.11.11.02).
2. JAGae27936: Certain applications using UDP ( eg. NFS )
may encounter timeouts/hangs due to bad UDP checksums.
3. JAGae28274: Setting ifAdminStatus up/down on igelan
cards causes system to hang.
4. JAGae08826: The lanscan catalog file was not delivered
as part of the igelan product in Application Release of
March 2002 (B.11.11.02).
5. JAGae20835: lanadmin -g mibstats <ppa> requires user
to hit Carriage Return to complete.
6. JAGae24310: The Gigabit Ethernet Adapters, A6825A and
A6847A were not supported by the igelan product in
Application Release March 2002 (B.11.11.02).
7. JAGae03711: The "Inbound Unknown Protocol" counter
displayed by the lanadmin display statistics command
may show incorrect value.
8. JAGae08074: Resetting the Gigabit Ethernet Adapter
in DEAD state may cause HPMC. The DEAD state
refers to the Driver State (IGELAN_DEAD) displayed
by the lanadmin -x card_info <ppa> command.
9. JAGae08407: Multiple OLAR suspend or the
Reset operations might leave the card in unusable
condition. When this problem happens, the green
LED on the card will be ON, indicating that the link
is UP, whereas the Driver State displayed by
lanadmin -x card_info shows that the link is
DOWN (IGELAN_OFFLINE), which puts the driver
in an unusable state.
10. JAGae08531: No warning is logged when the user
sets the speed to sub-gigabit speed with jumbo MTU
set.
11. JAGae09928: Sometimes the fiber card(A6847A)
part number might not be displayed by the
ioscan command.
12. JAGae13337: Issuing the lanadmin get stats
command when the Gigabit Ethernet Adapter
is in resetting or in suspended state may cause
HPMC.
13. JAGae18176: The lanadmin -x stats drv command
mis-spells the ifInUcastPkts_low.
14. JAGae18181: The lanadmin -x card_info command
has an incorrect format of displaying "Card Settings"
i.e, the line "Driver State:IGELAN_ONLINE", there
should be a space after ":".
15. JAGae18182: The format of the "PCI Subsystem ID
displayed by the lanadmin -x card_info command
is not correct.
16. JAGae18192: The statistics, "Out Packet Error"
displayed by the lanadmin -x stats drv command
is a duplicate of ifOutDiscard statistics.
17. JAGae20706: VLAN traffic fails after reset.
18. JAGae03122: The adapter's part number may not
be displayed correctly in ioscan description.
Defect Description:
PHNE_26369:
1. JAGae24114: Due to a timing issue between the receive
processing of the driver and the interrupt generation by
the igelan Media Access Controller hardware, some
received packets could go unprocessed by the driver,
and hence not sent up to the application, for as long
as one second.
Resolution: The hardware is instructed to regenerate
an interrupt whenever it notices that the driver has
not processed a status update from the card.
2. JAGae20835: The checksum calculation done by the
firmware is incorrect for certain message sizes for
UDP fragments.
Resolution: The firmware is fixed to handle the scenario
correctly.
3. JAGae28274: System hang due to negative spinlock
depth.
Resolution: A locking bug in the driver has been fixed to
resolve the negative spinlock depth problem.
4. JAGae08826: The Product Specification File did not
mention the lanscan catalog file, peigelan.cat and
hence it did not get delivered.
Resolution: The file peigelan.cat is delivered as part of
this patch.
5. JAGae20835: lanadmin requires the driver shared
library to define a function called "disp_continue()".
The igelan driver does not currently define/use
this function in its mibstats display function, which
is the cause of this defect.
Resolution: The igelan driver now has the function
called disp_continue.
6. JAGae24310: The Gigabit Adapters, A6825A and
A6847A are not supported.
Resolution: This patch supports the Gigabit Ethernet
Adapters, A6825A and A6847A that weren't
supported by igelan product Application Release
March 2002 (B.11.11.02).
7. JAGae03711: The "Inbound Unknown Protocol"
counter in the MIB statistics is updated twice.
Resolution: The function, which returns the MIB
statistics is not allowed to increment the
"Inbound Unknown Protocol" counter before
returning the MIB statistics, it just returns the
current value of it, because it has already been
updated as and when the packet is dropped for
Unknown Protocol reason.
8. JAGae08074: Registers are not set correctly
before reset, which may cause HPMC.
Resolution: Setup of registers done correctly.
9. JAGae08407: Link status changes are not detected
because a flag is setup incorrectly.
Resolution: Link status changes detected correctly.
10. JAGae08531: The necessary warning is not issued
whenever user tries to change the speed of
the link to sub-gigabit speed with JUMBO MTU
set, which is an unsupported configuration.
Resolution: The necessary warning is issued.
11. JAGae09928: EEPROM read fails because of
timeout.
Resolution: Timeout value has been increased to
enable successful read of EEPROM.
12. JAGae13337: Registers in card are accessed in
incorrect state.
Resolution: The state check is performed before
accessing the card.
13. JAGae18176: Incorrect spelling.
Resolution: The spelling is corrected.
14. JAGae18181: Incorrect formatting.
Resolution: The format has been corrected.
15. JAGae18182: Incorrect formatting.
Resolution: The format has been corrected.
16. JAGae18192: ifOutDiscard should display the
number of frames discarded by the card, while
"Out Packet Error"should display the number
of frames discarded by the driver.
Resolution: The statistics are displayed correctly.
17. JAGae20706: The link state of the physical interface
is updated incorrectly which causes the VLAN's link
state to remain down even though physical link is
up.
Resolution: Link state of physical interface is updated
correctly.
18. JAGae03122: The adapter's part number is not
initialized and hence ioscan description might not
display the adapter's correct part number.
Resolution: The adapter's part number is initialized
correctly.
Enhancement:
No
SR:
8606259796 8606263611 8606263948 8606241568 8606256520
8606259991 8606234513 8606239474 8606240657 8606241270
8606242693 8606246894 8606253842 8606253847 8606253848
8606253858 8606256391 8606233899
Patch Files:
IGELAN-DRV.IGELAN-KRN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,
v=HP:
IGELAN-DRV.IGELAN-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
/usr/conf/lib/libigelan.a
/usr/conf/master.d/igelan
IGELAN-DRV.IGELAN-RUN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,
v=HP:
IGELAN-DRV.IGELAN-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
/sbin/init.d/hpigelan
/usr/sbin/hpigelan_init
/sbin/rc1.d/K695hpigelan
/sbin/rc2.d/S305hpigelan
/usr/newconfig/etc/rc.config.d/hpigelanconf
/usr/lib/nls/msg/C/dsigelan.cat
/usr/lib/nls/msg/C/peigelan.cat
/usr/lib/lanadmin/libdsigelan.1
/usr/lib/lanscan/libpeigelan.1
/usr/lib/libfmigelan.1
/usr/lib/lanadmin/libdsigelan.sl
/usr/lib/lanscan/libpeigelan.sl
/usr/lib/libfmigelan.sl
/usr/lib/nls/msg/C/fmigelan.cat
/opt/networkdocs/igelan_ilan.pl
/opt/networkdocs/GigEther-01_relno.pdf
/opt/networkdocs/GigEther-01_quick_install.pdf
/opt/networkdocs/GigEther-01_README
what(1) Output:
IGELAN-DRV.IGELAN-KRN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,
v=HP:
/usr/conf/lib/libigelan.a:
igelan_ilan Version: 1 Jun 19 2002
igelan Revision: B.11.11.06 Jun 19 2002
$Revision: libigelan.a: Tue Jul 9 14:28:19 PDT
2002 $
/usr/conf/master.d/igelan:
$Revision: 1.1.106.2 $
IGELAN-DRV.IGELAN-RUN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,
v=HP:
/sbin/init.d/hpigelan:
None
/usr/sbin/hpigelan_init:
hpigelan_init
/sbin/rc1.d/K695hpigelan:
None
/sbin/rc2.d/S305hpigelan:
None
/usr/newconfig/etc/rc.config.d/hpigelanconf:
None
/usr/lib/nls/msg/C/dsigelan.cat:
None
/usr/lib/nls/msg/C/peigelan.cat:
None
/usr/lib/lanadmin/libdsigelan.1:
None
/usr/lib/lanscan/libpeigelan.1:
None
/usr/lib/libfmigelan.1:
None
/usr/lib/lanadmin/libdsigelan.sl:
None
/usr/lib/lanscan/libpeigelan.sl:
None
/usr/lib/libfmigelan.sl:
None
/usr/lib/nls/msg/C/fmigelan.cat:
None
/opt/networkdocs/igelan_ilan.pl:
None
/opt/networkdocs/GigEther-01_relno.pdf:
None
/opt/networkdocs/GigEther-01_quick_install.pdf:
None
/opt/networkdocs/GigEther-01_README:
None
cksum(1) Output:
IGELAN-DRV.IGELAN-KRN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,
v=HP:
1625058348 656714 /usr/conf/lib/libigelan.a
1174697750 3828 /usr/conf/master.d/igelan
IGELAN-DRV.IGELAN-RUN,fr=B.11.11.02,fa=HP-UX_B.11.11_64,
v=HP:
915883286 10490 /sbin/init.d/hpigelan
1842966010 8653 /usr/sbin/hpigelan_init
915883286 10490 /sbin/rc1.d/K695hpigelan
915883286 10490 /sbin/rc2.d/S305hpigelan
499614413 3037 /usr/newconfig/etc/rc.config.d/hpigelanconf
2103510366 9244 /usr/lib/nls/msg/C/dsigelan.cat
1422941188 114 /usr/lib/nls/msg/C/peigelan.cat
3573148884 135168 /usr/lib/lanadmin/libdsigelan.1
1752187859 12288 /usr/lib/lanscan/libpeigelan.1
2948430052 20480 /usr/lib/libfmigelan.1
3573148884 135168 /usr/lib/lanadmin/libdsigelan.sl
1752187859 12288 /usr/lib/lanscan/libpeigelan.sl
2948430052 20480 /usr/lib/libfmigelan.sl
1174060125 7929 /usr/lib/nls/msg/C/fmigelan.cat
2874910725 4118 /opt/networkdocs/igelan_ilan.pl
2480599940 709 /opt/networkdocs/GigEther-01_README
2116518901 85739 /opt/networkdocs/
GigEther-01_quick_install.pdf
4047271662 28782 /opt/networkdocs/GigEther-01_relno.pdf
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 1010 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 PHNE_26369
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_26369.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_26369. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_26369.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_26369.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_26369.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_26369------------------------------------------
Document ID: PHKL_27279
Date Loaded: 20020719
Title: s700_800 11.11 VxVM B.03.12.4 panic in vol_dump_disks()
Patch Name: PHKL_27279
Patch Description: s700_800 11.11 VxVM B.03.12.4 panic in vol_dump_disks()
Creation Date: 02/06/27
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
HPvxvm B.03.12.4
Filesets:
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_32,v=HP
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27279: PANIC
Category Tags:
defect_repair general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27279
Symptoms:
PHKL_27279:
System will panic when disk configuration is changed and
"vxdctl enable" is run while Glance is running.
Defect Description:
PHKL_27279:
The vol_dump_disks() function uses improper locking and is
exposed to a race condition: After vol_dump_disks has
allocated buffers to store information about a data
structure, the structure grows concurrently with
vol_dump_disks' execution. This causes vol_dump_disks to
overflow its buffers and corrupt kernel memory. Since
this is a memory corruption, the panic could occur
in various places, but vol_dump_disks() will almost
always be on the stack.
Resolution:
Fix locking strategy in vol_dump_disks(), and add new
overflow checks to be sure that memory corruption
will not occur. This patch also fixes related locking
problems in functions voldg_dump_groups() and
voldg_delete_finish().
SR:
8606264326
Patch Files:
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxvm.a(dg.o)
/usr/conf/lib/libvxvm.a(disk.o)
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxvm.a(dg.o)
/usr/conf/lib/libvxvm.a(disk.o)
what(1) Output:
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxvm.a(dg.o):
dg.c $Date: 2002/06/26 15:15:19 $Revision: r11.11/1
PATCH_11.11 (PHKL_27279)
/usr/conf/lib/libvxvm.a(disk.o):
disk.c $Date: 2002/06/26 15:14:52 $Revision: r11.11/
1 PATCH_11.11 (PHKL_27279)
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxvm.a(dg.o):
dg.c $Date: 2002/06/26 15:15:19 $Revision: r11.11/1
PATCH_11.11 (PHKL_27279)
/usr/conf/lib/libvxvm.a(disk.o):
disk.c $Date: 2002/06/26 15:14:52 $Revision: r11.11/
1 PATCH_11.11 (PHKL_27279)
cksum(1) Output:
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_32,v=HP:
2742674611 10140 /usr/conf/lib/libvxvm.a(dg.o)
499237044 7816 /usr/conf/lib/libvxvm.a(disk.o)
HPvxvm.VXVM-KRN,fr=B.03.12.4,fa=HP-UX_B.11.11_64,v=HP:
542664462 24256 /usr/conf/lib/libvxvm.a(dg.o)
734887618 16816 /usr/conf/lib/libvxvm.a(disk.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 80 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 PHKL_27279
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_27279.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_27279. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_27279.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_27279.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_27279.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_27279------------------------------------------
Document ID: PHKL_27070
Date Loaded: 20020719
Title: s700_800 11.00 VxFS cumulative,I/O Throttling/sync daemon
Patch Name: PHKL_27070
Patch Description: s700_800 11.00 VxFS cumulative,I/O Throttling/sync daemon
Creation Date: 02/07/17
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHKL_24905: PANIC
Category Tags:
defect_repair enhancement general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27070
Symptoms:
PHKL_27070:
( SR:8606197982 CR:JAGad67173 )
With PHKL_22312 installed, under heavy I/O, sync(2) and
processes that use sync(2) (such as sync(2), bdf(1M),
and login(1)) could experience long delays while dirty
buffers are flushed to disk.
PHKL_22312:
(SR: 8606157898 CR: JAGad27228)
Systems with heavy I/O to slow devices may sometimes
experience slow response time for processes trying to access
the respective device.
PHKL_24905:
( SR: 8606204945 CR: JAGad74121 )
Mounting a VxFS filesystem may panic the system. Stack
trace of the panic thread would look like:
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
ihandler+0x928
vx_spin_lock+0x30
vx_mapiodone+0x68
vx_mapiodone_bp+0x14
biodone+0x1f0
lv_complete+0xc4
lv_terminate+0xd4
lv_parwrite_done+0x470
lv_end+0x174
biodone+0x1f0
scsi_iodone+0x44
scsi_cbfn+0x4b0
fcpdev_scsi_comp+0x94
td_io_done+0x40
td_cdb_cbfn_start+0xb0
td_isr+0x1b4
epic_isr+0x58
mp_ext_interrupt+0x318
ihandler+0x904
PHKL_19481:
(SR: 5003436360 CR: JAGaa40337)
If the JFS is mounted with nolog option, it can not be
mounted again after unmounting it. The problem is easily
reproduced.
PHKL_26794:
( SR:8606233621 CR:JAGae02845 )
The 'st_nlink' field, as returned by stat(2), can be
inaccurate. This only occurs on VxFS filesystems with
PHKL_21210 (or any superseding patch) installed, the
vx_maxlink tunable is set to a value greater than 64k-1
and the number of directories created exceeds 64k-1.
PHKL_24201:
(SR: 8606184447 CR: JAGad53655)
VxFS directory sticky-bit not functioning according to
specification and man pages.
PHKL_21210:
(SR: 5003451625 CR: JAGaa93198)
Currently the number of subdirectories that can be
created is limitted to LINK_MAX. A new tunable has
now been added for VxFS (vx_maxlink) which will
allow this number to be changed to any value between
LINK_MAX and INT_MAX (See limits(5)).
If the tunable is not set the value of the limit
remains at LINK_MAX.
PHKL_18796:
SR: 1653264663 CR: JAGaa11143
If a VxFS file system has quotas turned on, but no quota
file is present, users can get open() and creat() failures
with error number '61449'.
Defect Description:
PHKL_27070:
( SR:8606197982 CR:JAGad67173 )
PHKL_22312 introduced a "throttling mechanism" to
prevent flushes of a large file from flooding a device
if the disk device could not keep up with the amount
of data being flushed. The large disk I/O queue would
cause slow response times for other processes trying to
access the respective device.
However, the throttling mechanism would cause processes
flushing buffers to wait for the disk to process I/O
requests before flushing more buffers, resulting in
extended delays when flushing dirty buffers.
Resolution:
When a sync(2) is performed, a new vxfs daemon thread
is created to handle the flushing of buffers on behalf
of sync(2). Also, a new tunable VX_NOTHROTTLE has been
created to enable or disable I/O throttling within VxFS.
PHKL_22312:
(SR: 8606157898 CR: JAGad27228)
The method used by VxFS filesystems for writing sequential
data is to asynchronously write data up to a limit and when
that limit is met to delay-write remaining data. This data
is flushed periodically. The adverse effect of having a
large amount of delayed-write data in the buffer cache is
that it can potentially flood the device with requests.
Resolution:
In order to slow the amount of I/O requests made to devices
that cannot keep up with demand a throttling mechanism will
be put in place for flushes from the buffer cache to VxFS
files that will prevent a device from being overloaded.
PHKL_24905:
(SR: 8606204945 CR: JAGad74121 )
After getting an error on a VxFS mount, a lock could be
prematurely released while an I/O to the device is still in
progress. Later, when the I/O is finished, de-referencing
the lock may panic the system.
Resolution:
Make sure that all the activities on the device are finished
before deallocating the lock.
PHKL_19481:
(SR: 5003436360 DTS: JAGaa40337)
A bug existed which, at unmount time, did not reset the
nolog flag if the filesystem had been mounted with the nolog
option. Any subsequent mount of this filesystem failed a
sanity check and the mount.
Resolution:
Unset the VX_NOLOG flag from the superblock when the file
system is unmounted.
PHKL_26794:
( SR:8606233621 CR:JAGae02845 )
vx_maxlink was first introduced with PHKL_21210. It
incorrectly allows the number of sub-directories in a
directory to exceed 64k-1, the maximum value that can
be displayed in the 'st_nlink' field, output by stat(2).
Hence, for vx_maxlink greater than 64k-1, st_nlink
overflows.
Resolution:
The vx_maxlink tunable is now limited to 64k-1. When
tuned to values greater than this, the operating system
will reset it to 64k-1.
PHKL_24201:
(SR: 8606184447 CR: JAGad53655)
VxFS directory sticky-bit not functioning according to
specification and man pages.
Resolution:
Make VxFS directory sticky-bit functionality conform
to specification and man pages.
PHKL_21210:
(SR: 5003451625 CR: JAGaa93198)
The number of subdirectories which can be created
for VxFS is limitted to LINK_MAX.
Resolution:
A new VxFS tunable (vx_maxlink) has been added which
allows this limit to be changed to any value between
LINK_MAX and INT_MAX (See limits(5)).
PHKL_18796:
SR: 1653264663 CR: JAGaa11143
No default was set for quota information, so without a
quota file, the user's uid and gid were undefined and
invalid.
Resolution:
Initialize group and user id's properly when there
is no quota file and quota is turned on.
SR:
1653264663 5003436360 5003451625 8606157898 8606184447
8606197982 8606204945 8606233621
Patch Files:
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_chain.o)
/usr/conf/lib/libvxfs_base.a(vx_config.o)
/usr/conf/lib/libvxfs_base.a(vx_dirop.o)
/usr/conf/lib/libvxfs_base.a(vx_mount.o)
/usr/conf/lib/libvxfs_base.a(vx_vfsops.o)
/usr/conf/master.d/vxfs
/usr/conf/space.h.d/vxfs.h
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_chain.o)
/usr/conf/lib/libvxfs_base.a(vx_config.o)
/usr/conf/lib/libvxfs_base.a(vx_dirop.o)
/usr/conf/lib/libvxfs_base.a(vx_mount.o)
/usr/conf/lib/libvxfs_base.a(vx_vfsops.o)
/usr/conf/master.d/vxfs
/usr/conf/space.h.d/vxfs.h
what(1) Output:
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_chain.o):
vx_chain.c $Date: 2002/07/16 14:55:39 $Revision: r11
ros/2 PATCH_11.00 (PHKL_27070)
/usr/conf/lib/libvxfs_base.a(vx_config.o):
vx_config.c $Date: 2002/05/22 14:05:50 $Revision: r1
1ros/6 PATCH_11.00 (PHKL_27070)
/usr/conf/lib/libvxfs_base.a(vx_dirop.o):
vx_dirop.c $Date: 2001/05/23 11:00:15 $Revision: r11
ros/5 PATCH_11.00 (PHKL_24201)
/usr/conf/lib/libvxfs_base.a(vx_mount.o):
vx_mount.c $Date: 2002/05/22 14:07:12 $Revision: r11
ros/5 PATCH_11.00 (PHKL_27070)
/usr/conf/lib/libvxfs_base.a(vx_vfsops.o):
vx_vfsops.c $Date: 2002/05/22 14:08:18 $Revision: r1
1ros/3 PATCH_11.00 (PHKL_27070)
/usr/conf/master.d/vxfs:
vxfs $Date: 2002/05/22 14:03:33 $Revision: r11ros/3
PATCH_11.00 (PHKL_27070)
/usr/conf/space.h.d/vxfs.h:
vxfs.h $Date: 2002/06/25 13:03:35 $Revision: r11ros/
2 PATCH_11.00 (PHKL_27070)
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_chain.o):
vx_chain.c $Date: 2002/07/16 14:55:39 $Revision: r11
ros/2 PATCH_11.00 (PHKL_27070)
/usr/conf/lib/libvxfs_base.a(vx_config.o):
vx_config.c $Date: 2002/05/22 14:05:50 $Revision: r1
1ros/6 PATCH_11.00 (PHKL_27070)
/usr/conf/lib/libvxfs_base.a(vx_dirop.o):
vx_dirop.c $Date: 2001/05/23 11:00:15 $Revision: r11
ros/5 PATCH_11.00 (PHKL_24201)
/usr/conf/lib/libvxfs_base.a(vx_mount.o):
vx_mount.c $Date: 2002/05/22 14:07:12 $Revision: r11
ros/5 PATCH_11.00 (PHKL_27070)
/usr/conf/lib/libvxfs_base.a(vx_vfsops.o):
vx_vfsops.c $Date: 2002/05/22 14:08:18 $Revision: r1
1ros/3 PATCH_11.00 (PHKL_27070)
/usr/conf/master.d/vxfs:
vxfs $Date: 2002/05/22 14:09:35 $Revision: r11ros/3
PATCH_11.00 (PHKL_27070)
/usr/conf/space.h.d/vxfs.h:
vxfs.h $Date: 2002/06/25 13:03:20 $Revision: r11ros/
2 PATCH_11.00 (PHKL_27070) */
cksum(1) Output:
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
758392094 6064 /usr/conf/lib/libvxfs_base.a(vx_chain.o)
3766943356 8316 /usr/conf/lib/libvxfs_base.a(vx_config.o)
3732352212 9044 /usr/conf/lib/libvxfs_base.a(vx_dirop.o)
3437323689 32068 /usr/conf/lib/libvxfs_base.a(vx_mount.o)
3401565249 17664 /usr/conf/lib/libvxfs_base.a(vx_vfsops.o)
2323883929 5054 /usr/conf/master.d/vxfs
2229146679 631 /usr/conf/space.h.d/vxfs.h
JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
2671912885 11968 /usr/conf/lib/libvxfs_base.a(vx_chain.o)
3477270381 17048 /usr/conf/lib/libvxfs_base.a(vx_config.o)
763713142 15952 /usr/conf/lib/libvxfs_base.a(vx_dirop.o)
1660686014 66264 /usr/conf/lib/libvxfs_base.a(vx_mount.o)
3102205156 43704 /usr/conf/lib/libvxfs_base.a(vx_vfsops.o)
2823206355 5053 /usr/conf/master.d/vxfs
1990722943 630 /usr/conf/space.h.d/vxfs.h
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHKL_18543
s800: 11.00: PHKL_18543
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_26794 PHKL_24905 PHKL_24201 PHKL_22312 PHKL_21210 PHKL_19481
PHKL_18796
Equivalent Patches: None
Patch Package Size: 300 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 PHKL_27070
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_27070.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_27070. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_27070.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_27070.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_27070.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHKL_27070:
A new system-wide tuneable, VX_NOTHROTTLE, is introduced
to enable or disable the I/O throttling mechanism. By
default, I/O throttling will be disabled (VX_NOTHROTTLE
set to 1). This is the pre-PHKL_22312 behavior. If you
are not experiencing performance problems due to high
disk I/O queues, there should be no need to enable I/O
throttling.
If long disk I/O queues are preventing other I/O from
completing in a timely manner, enabling I/O throttling by
setting VX_NOTHROTTLE to 0 may help reduce the disk I/O
queues, allowing other I/Os to complete sooner. Setting
VX_NOTHROTTLE to 0 is the equivalent behavior of PHKL_22312.
Please note, enabling I/O throttling may impact flush
performance as processes that flush large amounts of data
(such as sync(2) and bdf(1M)) will block until the amount
of data being flushed decreases.
PHKL_21210:
After patch is installed the vx_maxlink tunable can be
set in /stand/system. At that time the system needs to
be rebuilt and rebooted.
This patch depends on base patch PHKL_18543.
For successful installation please insure that PHKL_18543
is already installed, or that PHKL_18543 is included
in the same depot with this patch and PHKL_18543
is selected for installation.
-----End of Document ID: PHKL_27070------------------------------------------
Document ID: PHKL_27003
Date Loaded: 20020719
Title: s700_800 11.00 SCSI IO Subsystem Cumulative Patch
Patch Name: PHKL_27003
Patch Description: s700_800 11.00 SCSI IO Subsystem Cumulative Patch
Creation Date: 02/06/10
Post Date: 02/07/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
SCSI-Passthru.SPT2-DVR,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
SCSI-Passthru.SPT2-DVR,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27003: OTHER HANG
Please see the defect description for details
PHKL_26452: PANIC HANG
PHKL_25675: PANIC HANG
PHKL_24004: PANIC HANG OTHER
Update 11.00 to 11.11 fails.
PHKL_23281: PANIC HANG
PHKL_22941: HANG OTHER
See description for details on enhancements
PHKL_22759: OTHER
This patch replaces PHKL_22460 which addressed PANIC
HANG and MEMORY_LEAK symptoms.
PHKL_22460: PANIC HANG MEMORY_LEAK
PHKL_21607: PANIC HANG
PHKL_21504: PANIC
PHKL_20688: HANG
PHKL_20629: PANIC HANG
PHKL_20452: PANIC HANG ABORT CORRUPTION MEMORY_LEAK OTHER
See list of Defect Symptoms for details.
PHKL_20208: PANIC
PHKL_19245: PANIC
PHKL_17333: HANG
PHKL_13371: PANIC
PHKL_14688: PANIC
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic halts_system corruption
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27003
Symptoms:
PHKL_27003:
( SR:8606230706 CR:JAGad99756 )
When PHKL_22941 is installed and LVM is trying to switch
from the primary path to an alternate path, the SCSI
subsystem may report false read errors to LVM.
( SR:8606232873 CR:JAGae02101 )
Customer gets an I/O error on attempting to do more
than one backup on tape after installing PHKL_22460.
( SR:8606244278 CR:JAGae10766 )
The LVM I/Os hang due to the disk-driver retrying the
request forever, on getting a 'busy' status from disk.
Due to this, it was not possible to login or do any
work on the system.
( SR:8606249862 CR:JAGae16248 )
Some of the I/O requests may fail due to SCSI driver
not performing the retry operation.
PHKL_26452:
( SR:8606185203 CR:JAGad54405 )
System panics with a Data Page Fault when a read command is
issued on a SCSI pass through driver and the read failed
with a check condition on a deferred error :
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
b_pcxu_loop+0x58
privlbcopy+0x1c
scsi_fix_alignment_done+0x44
scsi_iodone+0xd4
scsi_cbfn+0x4b0
fcpdev_scsi_comp+0x94
fcpbh_scsi_comp+0x2cc
fcpbh_fcp_cbfn+0x14c
fcpbh_rcv_completer+0x108
fcT1_isr+0x900
sapic_interrupt+0x2c
mp_ext_interrupt+0x34c
ivti_patch_to_nop3+0x0
( SR:8606147432 CR:JAGad16775 )
On a K-Class system with no devices connected, if an
inquiry request is issued using the SIOC_IO command on a
SCSI pass through device (spt0) and an ioscan is also
issued, the system panics with the following stack trace :
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1e8
$ihndlr_rtn+0x0
s3_chain_ios+0x864
s3_check_ioq+0x5c
s3_io_request+0xac
s3_probe_request+0x1ac
s3_send_reply+0x234
s3_int_direct+0xe0
scsi3+0xf4
io_send+0x130
int_direct+0x74
mp_ext_interrupt+0x300
ivti_patch_to_nop3+0x0
idle+0x3bc
swidle_exit+0x0
( SR:8606225743 CR:JAGad94816 )
System panics with the following stack trace when an odd
byte aligned buffer, or greater than 64K-1 byte, read/write
request is issued to a raw disk device connected to an HP
Precision Bus fast-wide SCSI interface.
panic+0x14
invade_other_pools+0xb0
alloc_from_pool+0x80
io_send+0x58
d30_power_on_reply+0x8c
disc30+0x4ec
io_send+0x2a8
s3_send_power_on_req+0x3c
s3_pass_power_on+0x240
scsi3+0x364
io_send+0x124
d30_send_scsi_io_req+0x2dc
d30_rdwr+0x1cc
disc30+0x180
io_send+0x124
d3startio+0x6ac
d3startreq+0x90
d3pwrfail+0xc8
d3llioerr+0x3f4
disc3+0x194
io_send+0x2a8
disc3_strategy_real+0x22c
ioforw_int+0xd8
mp_ext_interrupt+0x6c
ivti_patch_to_nop3+0x0
( SR:8606216118 CR:JAGad85288 )
When the scsi bus is being opened and if an interrupt gets
serviced at the same time, the system panics with the
following stack trace :
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
c720_isr+0x890
sapic_interrupt+0x2c
mp_ext_interrupt+0x318
ivti_patch_to_nop3+0x0
bz_pre_sl_loop+0x4
c720_if_bus_open+0x318
scsi_lun_open+0x12d4
sctl_open+0x24
scsi_probe+0x370
parallel_scsi_probe+0x1a8
wsio_probe+0xe0
wsio_find_it+0x34
wsio_scan+0x70
gio_scan_subtree+0x188
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
io_scan+0x9c
do_io_scan+0x48
dev_config_ioctl+0xd8
spubind_cdev_ioctl+0x94
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1f4
syscall+0x480
$syscallrtn+0x0
( SR:8606223745 CR:JAGad92841 )
On workstation model C3700, the external narrow SCSI bus is
set up incorrectly. The 'diskinfo' command returns invalid
information and I/O's on this bus hang.
PHKL_25938:
( SR:8606186960 CR:JAGad56170 )
Bogus error messages "SCSI: asense data-done lbolt:..." are
displayed even if a device correctly returns sense data.
This is seen with Plasmon optical drives.
( SR:8606204859 CR:JAGad74037 )
The SCSI driver can not communicate with the target (nCipher
encryption device) that initiates speed and width
negotiation. This results in parity errors on the SCSI bus
and as a result SCSI bus resets.
( SR:8606193416 CR:JAGad62628 )
With PHKL_21607 or subsequent SCSI patch installed, if the
SCSI driver detects an error, the line below is displayed:
scb->cdb: 12 00 00 00 80 00 without the associated
information.
PHKL_25675:
( SR:8606137271 CR:JAGad06389 )
Some processes might become unkillable if many processes
access the same bus. This error condition has been
experienced only on systems with a hundred or more luns on
the same bus.
( SR:8606207857 CR:JAGad77034 )
The ioctl system call returns invalid values if called with
SIOC_GET_TGT_LIMITS or SIOC_GET_TGT_PARMS parameters for a
SCSI device controlled by the c8xx driver.
( SR:8606168360 CR:JAGad37642 )
A Data Page Fault panic occurs when an application uses
the sctl/ioctl passthrough interface with the read/write
data mismatching the buffer size. The stack trace would
look similar to the following:
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1e8
$ihndlr_rtn+0x0
lbcopy_pcxu_method+0xc
privlbcopy+0x1c
PHKL_24004:
( SR: 8606179935 CR: JAGad49157 )
If an error occurs that causes LVM to switch to an
alternate link (if configured) to access the physical
volume, a subsequent attempt to deactivate the volume
group with the command:
vgchange -a n [vg_name]
hangs.
( SR: 8606158737 CR: JAGad28067 )
The following informative message on the console and in
/var/adm/syslog/syslog.log unnecessary alarmed customers:
SCSI: Attempt to access partially open
device -- dev: %x
( SR:8606189487 CR: JAGad58701 )
An operating system update from 11.00 to 11.11 fails
during the kernel rebuild. The compilation of conf.c
fails with the the following messages:
WARNING: Duplicate tunable scsi_max_qdepth found
in /usr/conf/master.d/sctl.
Ignoring the following entry from
/usr/conf/master.d/sctl.
scsi_max_qdepth SCSI_MAX_QDEPTH 8
Compiling /stand/build/conf.c...
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 54: error 1588: "SCSI_MAX_QDEPTH" undefined.
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 54: error 1521: Incorrect initialization.
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 54: error 1521: Incorrect initialization.
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 72: error 1584: Inconsistent type declaration:
"scsi_max_qdepth".
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 72: error 1521: Incorrect initialization.
*** Error exit code 1
( SR: 8606199984 CR: JAGad69170 )
With heavy stress on Fibre Channel (FC) devices, the
system panics with the following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1e8
$ihndlr_rtn+0x0
scsi_is_synchronous_err+0x6c
scsi_action+0xb0
sd_retry+0x5c
scsi_cbfn+0x294
fcpdev_scsi_comp+0x20c
fcpbh_scsi_comp+0x5ec
fcpbh_fcp_cbfn+0x284
fcpbh_rcv_completer+0x450
fcT1_isr+0x77c
PHKL_23281:
( SR: 8606173791 CR: JAGad43048 )
A system panic occurs if a specific I/O logging level is
set while the system is experiencing I/O errors using the
passthrough driver. This panic may not occur if logging is
not enabled for investigation purposes. The panic causes
the following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
scsi_dmesg_log_io+0xf8
scsi_action+0x1b8
scsi_status_action+0x6c
scsi_cbfn+0x41c
scsi_fast_cbfn+0x1b0
c720_call_cbfns+0x60
c720_isr+0x5bc
epic_isr+0x58
mp_ext_interrupt+0x34c
ivti_patch_to_nop3+0x0
idle+0x164
swidle_exit+0x0
( SR: 8606161696 CR: JAGad31012 )
A defective SCSI bus controler generates many SCSI bus
resets and causes the system to panic. The panic results in
the following stack trace:
panic+0x14
settimeout_for_cpu+0x174
Ktimeout+0x3c
c720_reset_chip+0x129c
c720_isrRST+0x94
c720_isr+0x15cc
sapic_interrupt+0x2c
( SR: 8606176639 CR: JAGad45877 )
LVM requests to a Volume Group may hang instead of
switching to alternate link under certain disk failure
conditions. After TOC'ing the system, the resulting dump
showed the following stack trace of the lvmkd process:
_swtch+0x138
real_sleep+0x234
_sleep+0x14
scsi_sleep+0x34
scsi_iowait+0x54
scsi_cmdx+0x20c
scsi_cmd+0x3c
scsi_init_inquiry_data+0xe4
scsi_ioctl+0x1024
sdisk_ioctl+0x28
lv_check_dev_accessability+0x134
lv_bufio+0x23c
lv_test_a_link+0x8c
lv_check_pf_pvs+0x3a0
lvmkd_daemon+0xd4
lvmkd_fork+0xa0
lvmkd_init+0x1c
main+0x870
$vstart+0x34
$locore+0x74
PHKL_22941:
( SR: 8606112261 CR: JAGab84575 )
The same scsi queue depth can be set for all tagged
devices but not on a per device basis.
( SR: 8606135046 CR: JAGad04180 )
Frequent resets in systems with Fibre Channel devices
(possibly due to addition/removal of devices in the
loop) can cause excessive logging resulting in diag2
overrun or /var filesystem free space to be exhausted.
( SR: 8606158437 CR: JAGad27767 )
An XP256 array connected to a Fibre Channel adapter
can have placeholder LUNs with capacity zero. Using
scsictl command on those zero capacity LUNs causes an
unrecoverable process hang.
( SR: 8606166729 CR: JAGad36016 )
When a bus is shared between two systems, if one of the
systems continuously sends out bus resets, the I/Os from
the other system on this bus hang, consequently the
PV-Link switch would not occur.
( SR: 8606167125 CR: JAGad36411 )
Disk I/O hangs even when LVM PV-Link is configured.
The system could report a "DIAGNOSTIC SYSTEM WARNING".
The on-line diagnostic log would show an I/O Error.
( SR: 8606169435 CR: JAGad38710 )
High Availability systems hang when under heavy load
and many I/O errors are being returned by the scsi
driver (possibly due to a hardware problem).
PHKL_22759:
( SR: 8606169631 CR: JAGad38905 )
This patch replaces PHKL_22460.
The recent changes to SCSI services introduced within
PHKL_22460 to address Change Request JAGad04900 broke the
SIOC_IO ioctl interface. Any SIOC_IO ioctl sent down with a
null data buf (ie, test ready, rewind, etc) fails. This
will break backup applications and other Unix commands like
mc that send SIOC_IO ioctls with null data buffers.
PHKL_22460:
( SR: 8606158623 CR: JAGad27953 )
System can panic with a Data Page Fault panic in
scsi_start_bus_locked(). This defect has been found on a
V-class running ioscan after starting then halting
ServiceGuard in a single node configuration. It can
potentialy be found with other systems. The stack trace for
this is:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xa8c
nokgdb+0x8
scsi_start_bus_locked+0x5a4
scsi_start+0xb0
scsi_strategy_real+0x1a4
pa_ioforw_sched+0x360
scsi_probe+0x640
parallel_scsi_probe+0x100
wsio_probe+0xe0
wsio_find_it+0x34
wsio_scan+0x6c
gio_scan_subtree+0x188
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
gio_scan_subtree+0x1c4
io_scan+0xbc
do_io_scan+0x48
dev_config_ioctl+0xe8
spubind_cdev_ioctl+0x94
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x168
syscall+0x200
$syscallrtn+0x0
( SR: 8606157951 CR: JAGad27281 )
On a K-class or T-class machine with the HP-PB boards using
the scsi3 driver, this defect may cause some processes to
hang and SCSI abort messages will be found in the syslog
file. However, this defect has not been encountered by any
customers and the chances of experiencing it are extremely
low.
( SR: 8606155189 CR: JAGad24506 )
This problem would most likely show as an instruction fault
panic trying to execute address 0x.0. Careful debugging may
be able to produce a stack trace with:
c720_if_tgt_open+0xa4
scsi_tgt_open+0xf04
scsi_lun_open+0xf10
sdisk_open+0x1c
call_open_close+0xb5c
opend+0x2f4
spec_open+0xe8
vns_copen+0x4c
vn_open+0xdc
copen+0x128
open+0x44
syscall+0x5f4
$syscallrtn+0x0
( SR: 8606155173 CR: JAGad24490 )
This problem can occur on any system with heavy SCSI
I/O. Abort messages are likely to be seen in the syslog
file. The stack trace ended with:
c720_start+0xadc
c720_isrDeactivate+0x280
c720_cleanup+0x78
c720_done+0x6c
c720_isrCmdComp+0x164
c720_isrGuts+0xbcc
c720_isr+0x218
epic_isr+0xa4
mp_ext_interrupt+0x264
ivti_patch_to_nop3+0x0
spinunlock+0x48
lookuppn+0x1a4
vn_create+0xc0
mkdir+0x80
( SR: 8606155151 CR: JAGad24468 )
This problem could show up a process hang waiting for an I/O
to complete, or a memory leak of a 512 byte bucket on 32bit
kernels and 1024 byte bucket on 64bit kernels. It can occur
on any kind of machine during regular use of the system.
( SR: 8606133057 CR: JAGad02204 )
The sctl device driver was not designed to run on multiple
processors at the same time (i.e. MP safe). As a
consequence, all processes using the sctl device driver will
all be run on the same processor in a multi-processor
system. CPU load distribution will be uneven and may lead,
in the worst cases, to severe degradation of performance.
( SR: 8606135767 CR: JAGad04900 )
During regular use of the sctl driver requesting information
from a device, a data page fault panic occurs when an
unwritable buffer is given to the sctl driver. The stack
will show the following lines:
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1e8
$ihndlr_rtn+0x0
lbcopy_pcxu_method+0xc
privlbcopy+0x1c
( SR: 8606155155 CR: JAGad24472 )
This problem can be found on any system experiencing memory
pressure. A data page fault panic from c720_timer occured
when the system was running out of memory. SCSI aborts are
likely to be found in the syslog file. The stack trace
should show:
c720_timer+0x6e4
invoke_callouts_for_self+0x238
sw_service+0x108
mp_ext_interrupt+0x394
ivti_patch_to_nop3+0x0
idle+0x3c4
swidle_exit+0x0
( SR: 8606155022 CR: JAGad24339 )
The system will suffer performance degragation once a device
queue has been filled. The syslog file will include a
message reporting a QUEUE DEPTH message for the
corresponding device, and the depth gets set to 1. This is
never get reset. This problem was partially handled by a
previous patch (PHKL_21607), but needs to be completed.
This fix is not necessary to have a machine work properly
but it is needed for a proper and complete solution on
handling correctly the QUEUE FULL condition.
( SR: 8606125977 CR: JAGac46733 )
This problem would be seen as a data page fault panic in
LspToScratch. This panic can occur during regular use of
the c720 driver. The stack trace should end with:
LspToScratch+0x8
c720_isrSelect+0x38
c720_isrGuts+0x84c
c720_timer+0x668
invoke_callouts_for_self+0xc0
sw_service+0xb0
mp_ext_interrupt+0x144
( SR: 8606138825 CR: JAGad08088 )
A data page fault can occur during regular use of the c720
driver. Although no specific stack trace can be expected,
if ONE out of the five following functions appears near the
top of the stack trace, it is likely that this defect has
occurred:
c720_isrSelect()
c720_isrDataDone()
c720_isrExtMsgLenIn()
c720_isrWdtrRespRcvd()
c720_isrSdtrRespRcvd()
( SR: 8606155947 CR: JAGad25258 )
This problem is likely to show up as a hung
process. Debugging of the problem would provide the
following stack for this process:
_sleep+0x7d4
scsi_sleep+0x3c
scsi_lun_close+0x758
sdisk_close+0x10
call_open_close+0x504
closed+0xb0
spec_close+0x54
vn_close+0x48
vno_close+0x20
closef+0x68
close+0x48
syscall+0x480
$syscallrtn+0x0
( SR: 8606160406 CR: JAGad29728 )
SCSI bus throughput is not as expected on LVD SCSI boards.
These boards are 895 & 896 chip based boards. The system
will show slow performance from the LVD SCSI boards.
( SR: 8606105472 CR: JAGab73559 )
This is an enhancment that creates a persistent tunable to
manage the queue depth for all the SCSI tagged devices on a
system. The queue depth gives the number of maximum
concurrent I/O to the same device.
( SR: 8606160479 CR: JAGad29800 )
A data page fault panic from scsi_start occurs. The problem
can occur if the system is accessing multiple tape devices
on a single SCSI bus. The panic and stack trace will be:
panic: (display==0xb800, flags==0x0) Data page fault
The stack trace was:
scsi_start+0x18
scsi_retry+0xd8
invoke_callouts+0x160
softclock+0x38
sw_service+0x154
mp_ext_interrupt+0x2a0
$RDB_int_patch+0x58
mpn_splx_free_lock_ul4_brn_target+0x4
net_callout+0x90
netisr_netisr+0x1bc
netisr_daemon+0x68
PHKL_21989:
( SR: 8606142756 CR: JAGad12108 )
Any wide SCSI devices attached to the built-in narrow
single-ended SCSI bus using a 50 pin to 68 pin cable will
not function properly. The description shown by ioscan
for the built-in narrow single-ended SCSI bus will
incorrectly show the bus as "Wide".
PHKL_21607:
( SR: 8606132292 CR: JAGad01441 )
The QUEUE FULL handling has caused performance problems at
customer sites.
( SR: 8606130227 CR: JAGac95098 )
The "incomplete" field of the scsi_lun structure is keeping
track of the number of i/o requests pending for a specific
lun. This field is increasing to large numbers, which is
giving misleading information.
( SR: 8606132288 CR: JAGad01437 )
The stated limitations on lun numbering are that they must
start at zero and be in sequential order. If there are any
"gaps" in lun numbering, ioscan will not recognize the high
order luns above the gap. The request is for ioscan to
recognize all luns, regardless of lun numbering and order.
( SR: 8606132426 CR: JAGad01575 )
A typical SCSI message in the syslog contains a dev
(for device). It would be useful to have the hardware
path to make the log message more clear.
( SR: 8606106155 CR: JAGab75050 )
The system panics with Spinlock held too long. The
panic is most likely occuring on a debug kernel.
The end of the stack should show the following :
panic+0x14
check_held_time+0x42c
spinlock_delete+0x50
su_pre_check+0x144
c720_unlock+0x9c
c720_isr+0x254
( SR: 8606133146 CR: JAGad02293 )
A panic occured when assertion failed:
panic: assertion failed ((ReadLong(isc,(ubit32 *)&pScript
[Ent_PtCmd+4], &j), (j == PTR_TO_CHIPWORD( ((struct
c720_OutBuf *)lbp->uPhysOutBuf
( SR: 8606133067 CR: JAGad02214 )
LVM hangs due to I/O requests never being returned by the
IO subsystem. The message "Device violation of Contingent
Allegiance" is issued to syslog.
( SR: 8606133280 CR: JAGad02425 )
A SCSI spinlocok panic occured. The panic string was:
panic: assertion failed ((lisc)->cbfns == NULL)
( SR: 8606125811 CR: JAGac42754 )
The robotics LUN on a LVD/SE DDS4 Autoloader is not
discovered by ioscan when the autoloader is attached to
a HSC SE bus. The drive LUN is discovered and is attached
to stape correctly, but the robotics controller LUN doesn't
even come up as unclaimed.
PHKL_21504:
( SR: 8606125610 CR: JAGac41000 )
With vmtrace configured, the system panics with a data
memory protection fault and the following stack trace :
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
spinlock+0x14
scsi_lun_lock+0x14
sd_strategy_error+0x170
sd_strategy+0x12c
scsi_strategy_real+0xd78
ioforw_int+0xcc
mp_ext_interrupt+0x144
ivti_patch_to_nop3+0x0
idle+0x4dc
swidle_exit+0x0
This problem is reproducible on systems with SCSI LUNs
configured with no storage (i.e. zero storage size) and
occurs when an I/O request which attempts to access the
no-storage LUN coincides with an I/O request to close
the same LUN.
( SR: 8606130829 CR: JAGac97596 )
If SCSI SCRIPTS RAM is modified, pNext in
c720_bus_open_real() will not be pointing to the end of
SCRIPTS RAM.
PHKL_20688:
( SR: 8606127757 CR: JAGac78558 )
SCSI hardware failure causes system hang with multiple
processes waiting for I/O to return.
Multiple console messages are generated which read:
SCSI: Third party detected bus hang --
lbolt: xxxxxxxx, bus: x
PHKL_20629:
( SR: 8606112882 CR: JAGab93301 )
Panic using spt0 SCSI pass-thru or Omniback with patch
PHKL_20452 installed.
Panic stack trace:
proc[82] at 0x0326b780
("/opt/omni/lbin/bma -load 1.000000
-name hpcc557_DLTL-1.2 -po"):
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x4c
trap+0xea8
$RDB_trap_patch+0x38
spt_getbuf+0x18
spt_sioc_io+0x110
spt_ioctl+0x1c8
spubind_cdev_ioctl+0x88
spec_ioctl+0xb0
vno_ioctl+0x8c
ioctl+0x138
syscall+0x1c8
$syscallrtn+0x0
( SR: 8606110931 CR: JAGab83681 )
Panic in scsi_dmesg_log_io function of scsi driver:
"Data Page Fault at line# 1361 in wsio/scsi_ctl.c"
Panic Stack Trace:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
lbcopy_pcxu_method+0xc
privlbcopy+0x1c
scsi_dmesg_log_io+0x4e4
PHKL_20452:
( SR: 5003432120 CR: JAGaa22888 )
SCSI IO subsystem retries non-responsive SCSI devices
"forever". Appears to user as IO hang to a device or
Logical Volume.
( SR: 8606103129 CR: JAGaa44450 )
After opening a device defined as a scsi_fast_read or write
device, SCSI pass-through command mode stops working.
( SR: 8606103814 CR: JAGab19070 )
SCSI Data Page Fault panic: c720_isrAbort/$ihndlr_rtn.
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
c720_isrAbort+0x1c
c720_isr+0xc94
sapic_interrupt+0x2c
mp_ext_interrupt+0x33c
ivti_patch_to_nop3+0x0
idle+0x508
swidle_exit+0x0
( SR: 8606103810 CR: JAGab19072 )
System hung running SCSI disk IO, Filesystem, and LVM
stress test, due to SCSI controller looping forever to
process interrupts.
( SR: 1653307298 CR: JAGab20815 )
File system hang on two-way mirrored LVM configuration when
a disk drive in the mirror fails, due to infinite retries
on SCSI Parity Errors.
( SR: 8606100396 CR: JAGab31749 )
Machine can have HPMC while doing register dump of the SCSI
controller, if the SCSI IO Processor (SIOP) has not first
been stopped.
( SR: 8606103820 CR: JAGab39677 )
Data corruption can be experienced on early revision of
SCSI 896 controller chip, when Parity Errors occur on the
SCSI bus.
( SR: 8606103148 CR: JAGab69517 )
Data Page Fault panic in scsi_start_bus_locked from
parallel_scsi_probe.
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xa8c
nokgdb+0x8
scsi_start_bus_locked+0x5a4
scsi_start+0xb0
scsi_strategy_real+0x1a4
pa_ioforw_sched+0x360
scsi_probe+0x640
parallel_scsi_probe+0x100
wsio_probe+0xe0
wsio_find_it+0x34
wsio_scan+0x6c
gio_scan_subtree+0x188
gio_scan_subtree+0x1c4
io_scan+0xbc
do_io_scan+0x48
dev_config_ioctl+0xe8
spubind_cdev_ioctl+0x94
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x168
syscall+0x200
$syscallrtn+0x0
( SR: 8606103192 CR: JAGab69594 )
Infinite SCSI IO retries; appears to user as IO hang to a
device or Logical Volume.
( SR: 8606105969 CR: JAGab74731 )
SCSI Bus Reset occurs during an xstm firmware download to
disks on A,K,V class machines.
( SR: 8606106038 CR: JAGab74836 )
Ultra-II speeds not set correctly in scsi c720 driver, so
Ultra-II devices go slower than expected. Also, SCSI
speed and bus width set incorrectly on PCI-attached SCSI
controllers, as shown in ioscan(1M) output.
( SR: 8606103826 CR: JAGab76136 )
SCSI Unexpected Disconnect on DLT7000 tape drive.
( SR: 8606108198 CR: JAGab78589 )
Long system hangs when using the NIO pass-through driver.
( SR: 8606110476 CR: JAGab83179 )
Extended Interrupt Vectors would not work on 64-bit PA
RISC Processors.
( SR: 8606110477 CR: JAGab83180 )
Display values for SCSI Width and Mode are set incorrectly,
as shown by ioscan on some machines: J7000, J5000, C3000,
and B1000.
( SR: 8606110479 CR: JAGab83182 )
Data corruption with early 896 SCSI chip in 32-bit mode, as
observed on the SCSI bus.
( SR: 8606110481 CR: JAGab83184 )
Panic on dereference of NULL pointer "lsp" in the
msg_printf at the end of c720_isrGuts_LBP_STALL() routine.
( SR: 8606110616 CR: JAGab83364 )
Online Deletion causes memory leak.
( SR: 8606110653 CR: JAGab83401 )
SCSI Abort Message not working properly with PCI bus.
( SR: 8606110782 CR: JAGab83531 )
SIOP is started with an empty IO request.
PHKL_20208:
( SR: 1653281824 DTS: JAGaa42584 )
If immediate reporting is enabled and a deferred error
occurs, the system will panic with "scsi unrecovered
deferred error".
PHKL_19776:
( SR: 8606103698 CR: JAGab70738 )
( SR: 8606101027 CR: JAGab70313 )
LVM VG failover to alternate HW path takes up to 8 minutes.
( SR: 1653310672 CR: JAGab31999 )
A bad disk shows as good, based on cached INQUIRY data
which can be shown with "diskinfo -v <devfile>" on bad disk.
Note: the cause of this also affected above two CRs, so
this SCSI INQUIRY fix was required for this patch.
PHKL_19245:
( SR: 8606103582 DTS: JAGaa09970 )
Enhancement to add new IOCTL for issuing SCSI commands to
SCSI disks.
PHKL_19561:
( SR: 4701424978 DTS: JAGab13476 )
I/O error on reading odd-length records from tape device.
PHKL_17333:
( SR: 1653284257 DTS: JAGaa44107 )
NIO disks may become unresponsive, causing processes
which access them to hang and become unkillable.
PHKL_14807:
The previous patch has been recut to include compile-based
performance tuning. There is no functional change in this
patch.
PHKL_13371:
( SR: 4701376111 DTS: DSDe440799 )
The following has been the configuration that produced
the problem in practice, though this problem could
potentially occur on other configurations. When a
CASCADE (C2430D) device is connected to a T520 or
T600 and a probe goes down to the device
possibly from an ioscan running, it may get a
check condition. This leads to a
data page fault PANIC.
PHKL_19287:
( SR: 8606101377 DTS: JAGab17408 )
LVM failover to alternate path fails on logical volumes
configured on SCSI3 devices
PHKL_20157:
( SR: 8606107849 DTS: JAGab78147 )
c720 driver does not support SYM 53C895A SCSI chip
( SR: 8606107164 DTS: JAGab76873 )
Internal SCSI on N-class is identified as SE instead of LVD
( SR: 8606106038 DTS: JAGab76903 )
Ultra-2 speeds not set correctly in scsi c720 driver
( SR: 8606105969 DTS: JAGab74731 )
Reset during Firmware Download
( SR: 8606103151 DTS: JAGab69533 )
N/L sys. could NOT see disk when boots up with install
kernel
PHKL_17368:
Hot Spares configured on a NIKE will not be visable via SAM.
SAM issues the errors:
"Failed to open newly created LUN device file"
and
"SAM is unable to communicate with the device controller at
hardware path, x.xx. As a result, SAM cannot retrieve
information about the state of any LUNS owned by this
controller. SAM will display the LUNS owned by this
controller but use extreme caution when using LUNS. If this
controller is part of a dual controller disk array, the LUNs
may be listed twice instead of correctly being listed only
once. Again, use extreme caution when configuring LUNS."
SAM works fine when the HOT Spare(s) is removed.
PHKL_14688:
Data Page Fault panic when commands are repeatedly sent to
a device controlled by the scsi_pt driver, with I/O
activily on other devices on the same bus.
Defect Description:
PHKL_27003:
( SR:8606230706 CR:JAGad99756 )
After an LVM I/O times out, the flag L_FAIL_QUEUE_IO can
remain set and prevent LVM probes from being sent to the
device to see if it has returned on-line. Also, many SCSI
read error messages will be seen in syslog.
Resolution:
Only set the flag (L_FAIL_QUEUE_IO) if there are I/O
requests queued to be sent to the device.
( SR:8606232873 CR:JAGae02101 )
PHKL_22460 caused the c720 driver to only map the
sense buffer during bus open and re-used the
physical address for each I/O until the bus is
closed. However, while re-using the request sense
buffers between I/O requests, the driver was not
invalidating the buffer. This resulted in I/O error
due to stale data access from the cache during multiple
backups to tape.
Resolution:
Modify the request sense buffer handling code in c720
driver as below
1. Allocate and map one request sense buffer in
initialization function and re-use it during the life
of the card.
2. Invalidate the buffer after every completion status
receipt from device.
( SR:8606244278 CR:JAGae10766 )
The driver-retry logic causes the disk driver to retry
I/O requests forever on getting a 'busy' status from disk.
Even the LVM I/Os are retried forever, thereby giving an
impression that the process/system has hung.
Resolution:
Correct the retry logic of the disk driver so that the
LVM I/Os are retried only for the duration of the timeout
set.
( SR:8606249862 CR:JAGae16248 )
Upon detecting a timed out I/O request, the driver sets
a flag in the LUN data structure indicating, "do not
retry any requests for this LUN".
After a successful completion of a subsequent I/O
request, this flag should be cleared. However, when the
subsequent I/O request completes successfully, the
driver's normal completion path (in which this flag is
cleared) does not get executed and hence the flag remains
set. So, if any subsequent I/O requests do not complete
sucessfully, they are failed immediately without
performing the retry.
Resolution:
The fix is to make sure that the driver follows the normal
completion path for the first successful completion of
an I/O request following a failed I/O request.
PHKL_26452:
( SR:8606185203 CR:JAGad54405 )
When a SCSI pass-through read fails with a check condition
on a deferred error, the scsi function used to process the
completion of the I/O is incorrectly called twice. Since
the scsi function is called twice, the number of bytes to
be copied from the kernel space buffer to the user space
buffer in the kernel is incorrectly being incremented.
This resulted in writing past the end of the user space
buffer causing the system to panic with a Data Page Fault.
Resolution:
The fix is not to call the scsi function twice when there
is a deferred error.
( SR:8606147432 CR:JAGad16775 )
A kernel internal data structure for the scsi device was
freed when there were outstanding I/O requests.
Resolution:
The fix is to check if there are any outstanding I/O
requests, and only when there are none remaining,
to deallocate the data structure.
( SR:8606225743 CR:JAGad94816 )
Instead of returning an error up to the user level, the
disc3 driver retries the I/O over and over again causing
all the I/O message frames to be used up. This eventually
causes the system to panic.
Resolution:
The fix is to return EINVAL to the user level, if the I/O
request has an odd aligned buffer, or exceeds 64K-1 bytes.
( SR:8606216118 CR:JAGad85288 )
The system panics because of a race condition between the
scsi bus open and the interrupt being serviced. The
interrupt was getting serviced even before the internal
data structures in the bus open routine were completely
initialized.
Resolution:
The fix is to set a flag after initializing the data
structures in the scsi bus open routine. In the ISR
routine, a check is made to verify if this flag is set.
The interrupt is serviced only if this flag is set. The
flag is unset in the scsi bus close routine.
( SR:8606223745 CR:JAGad92841 )
The SCSI bus on the C7300 was not being correctly
identified as narrow. The bus was being set up incorrectly
as wide.
Resolution:
The SCSI bus identification routine was updated to
correctly identify the SCSI bus used on the C3700 as
narrow.
PHKL_25938:
( SR:8606186960 CR:JAGad56170 )
The SCSI driver incorrectly displays this message when the
device returns exactly the amount of sense data asked for.
Resolution:
This incorrect message log is removed in the SCSI driver.
( SR:8606204859 CR:JAGad74037 )
The SCSI driver does not distinguish between speed/width
negotiations initiated by the target or the driver.
The mismatch in the speed setting on the host and the target
results in Parity Error on the bus.
Resolution:
The SCSI driver now tracks whether the response from the
target is a response to host initiated negotiation or an
unsolicitated request from the target.
( SR:8606193416 CR:JAGad62628 )
The message scb->cdb: 12 00 00 00 80 00 is always logged.
The additional information to log with it is issued at
specific levels of SCSI interface driver logging.
Resolution:
The scb->cdb: 12 00 00 00 80 00 message is now logged at
the same level of logging as the additional information.
PHKL_25675:
( SR:8606137271 CR:JAGad06389 )
Under heavy I/O load on the same bus, when some per bus
resource (tag, nexus) becomes unavailable, I/Os are stored
in specific queues, waiting for the resource to become
available. Under some conditions, the queues are not
checked once the resource is once again available, leaving
the I/O requests unserviced. The corresponding processes
remain in an unkillable state, waiting for I/O completion or
failure that never occurs.
Resolution:
Additional tests were added to check if I/Os are pending in
the queues, and to process them if the resources are now
available.
( SR:8606207857 CR:JAGad77034 )
The SCSI services did not support the SIOC_GET_TGT_LIMITS
and SIOC_GET_TGT_PARMS ioctl for the c8xx driver.
Resolution:
SCSI services is enhanced to support these ioctls for the
c8xx driver.
( SR:8606168360 CR:JAGad37642 )
If a SCSI I/O is initiated using the sctl/ioctl passthrough
function and the transfer size is greater than the size of
the malloc'd buffer for this transfer, the system panics.
Resolution:
Check the access permissions of the buffer supplied by the
user before using it. This ensures the system won't panic
if the size of the I/O is greater than the size of the
buffer.
PHKL_24004:
( SR: 8606179935 Chart: JAGad49157 )
The command issued to close the LUN sleeps forever
because a counter for pending I/Os was not decremented
when returning the I/Os issued to a timed-out LUN.
Resolution:
The counter for tracking the pending I/Os is now
decremented when returning errors to I/Os issued to a
timed-out LUN.
( SR: 8606158737 Chart: JAGad28067 )
This informative message was always logged while trying
to access partially opened device (This is a device with
zero capacity).
Resolution:
This message is not logged by default for partially
opened devices. This message log can be enabled for
debuggging purposes by setting appropriate value in
scsi_log_mask.
( SR:8606189487 Chart: JAGad58701 )
New files introduced to 11.00 by a patch interfere with
an update to 11.11. The defect is seen on 11.00 systems
with PHKL_22460 or superseding patches. These patches
introduced two new files:
/usr/conf/master.d/scsi-disk and
/usr/conf/space.h.d/scsi-disk.h,
needed to define a new tunable (scsi_max_qdepth). 11.11
includes this tunable too, but in different files.
When recompiling the kernel, the compiler sees the
scsi_max_qdepth symbol defined in two files. It uses
the definition found in the first file. The compilation
fails because the tunable definition is different
(default value does not correspond to the same
constant).
Resolution:
A new script, scsi.clean, is created by this patch. The
file is installed in the /usr/lbin/sw/pre_kernel
directory. On updating to 11.11, this script is run and
removes scsi-disk and scsi-disk.h. The kernel build will
then be successful and the update process will complete.
Even though files are removed, the tunable settings are
kept across the update.
( SR: 8606199984 Chart: JAGad69170 )
A data page fault panic can occur if the scsi driver
tries to access stale sense data unconditionally, for a
SCSI error that had no associated sense data.
Resolution:
The scsi driver will now access sense data only when it
receives CHECK CONDITION error. Sense data will always
be valid during this error condition.
PHKL_23281:
( SR: 8606173791 CR: JAGad43048 )
Because the logging function was called by the passthrough
driver a pointer was not set. The logging function uses
this pointer to reference some elements causing the system
to panic.
Resolution:
The function checks if the calling driver is a passthrough
and if the pointer is set to NULL. If so, no specific I/O
logs are generated.
( SR: 8606161696 CR: JAGad31012 )
The SCSI bus reset management is handled poorly by the
system. On every SCSI bus reset, a new timer is generated
for later processing. This leads to a timer table overflow
which causes the system to panic.
Resolution:
The SCSI bus reset management was improved by the system
checking if a reset timer is set for the corresponding bus
each time the SCSI bus is reset. If a reset timer already
exists for that bus, the previous timer is removed and
another timer is set. Otherwise, a new timer is set for the
corresponding bus. This ensures that only one reset timer
can be set per reset on a specific SCSI bus and prevents
the possibility of timer table overflow resulting from a
defective SCSI card.
( SR: 8606176639 CR: JAGad45877 )
When a powerfail condition occurs, the LVM requests are
queued to the Powerfail queue and the lvmkd deamon will
attempt to test the links by sending a SCSI_INQUIRY request
to each link. If a device returns SCTL_INCOMPLETE, the
scsi code will retry the SCSI_INQUIRY every 2 seconds until
the inquiry is successful. If the inquiry is never
successful, the scsi driver will never return to the lvmkd,
and the powerfail recovery will hang rather than timing out
and switching to the alternate link.
Resolution:
On a SCSI_INQUIRY done through the sdisk_ioctl path where
the device returns SCTL_INCOMPLETE, the inquiry request
will be retried every 2 seconds, but now there is a maximum
of 5 retries.
PHKL_22941:
( SR: 8606112261 CR: JAGab84575 )
There was no mechanism available to set the scsi queue
depth tunable on a particular device.
Resolution:
A new ioctl interface is provided for setting the scsi
queue depth tunable for a particular device. However,
this change takes effect on subsequent device opens.
scsictl command is used to set the scsi queue depth
tunable on a device. It is defaulted to the value set by
global tunable "scsi_queue_depth" unless overridden by
the scsictl command.
( SR: 8606135046 CR: JAGad04180 )
The SCSI subsystem logs errors for each I/O attempt
in syslog.log. Bus resets being more common in Fibre
Channel systems, the errors for each retry attempt
could result in excessive error logs.
Resolution:
Recoverable errors are not logged except for Unit
attention or Deferred errors. However, the errors that
are persistent even after the maximum number of retries,
are logged once.
( SR: 8606158437 CR: JAGad27767 )
This was caused by the driver indefinitely retrying a
failing mode sense command on a LUN with capacity zero.
Resolution:
The mode sense command is not retried indefinitely and
the scsictl command now fails with an I/O error after
maximum retry attempts on such LUNs.
( SR: 8606166729 CR: JAGad36016 )
The LVM requests were retried indefinitely in the SCSI
subsystem when the device returns "unit attention"
error. This prevents LVM from recognizing this as an
error and switching to an alternate path.
Resolution:
The LVM requests are not retried indefinitely for such
errors, instead an error is returned after the maximum
retries, allowing LVM to switch-over to an alternate
path.
( SR: 8606167125 CR: JAGad36411 )
LVM requests were retried indefinitely when an invalid
driver-internal status was returned.
Resolution:
The LVM requests are not retried indefinitely when an
invalid driver-internal status is returned, instead
an error is returned to LVM after retrying in the
SCSI layer for the maximum number of attempts.
( SR: 8606169435 CR: JAGad38710 )
I/Os which timeout were not always being returned with
an error but being retried indefinitely. This resulted
in requests that had timed out, getting stuck in the
disk driver's queue, resulting in a hang.
Resolution:
The requests are tracked and those which timeout are
returned to the upper layer, thus allowing it to switch
to an alternate path if one is configured.
PHKL_22759:
( SR: 8606169631 CR: JAGad38905 )
The bad fix introduced into PHKL_22460 was to check the
write access on the buffer passed to the sctl driver
Commands are allowed to pass NULL pointers for the data
through the pass thru driver when they don't need any
return data. The I/O generated by those commands won't
pass the test and fail.
Resolution:
The fix is to totally remove the check introduced in
PHKL_22460 (for JAGad04900) so that all its other fixes
can be available.
The specific problem incorrectly fixed previously will
be addressed in a future patch.
PHKL_22460:
( SR: 8606158623 CR: JAGad27953 )
The system paniced because the SCSI driver tried to
dereference a field in a structure after the structure had
been freed.
Resolution:
The dd_lun structure is freed in two places in the code, one
in scsi_lun_open(), the other in scsi_lun_close(). However,
the scb_q_nonempty field is only NULLed out in
scsi_lun_open(), not scsi_lun_close(). The fix is to NULL
it out in both places.
( SR: 8606157951 CR: JAGad27281 )
During a regular use of a system, a request can be aborted.
When the abort is issued, if the controller returns an
error, the expected behavior is to resend the original
request. The active request needs to be initialized before
processing the I/O. In the current design, the request is
left untouched and therefore is not retried.
Resolution:
The active request that returned with an error is assigned
to NULL and is placed back on the request queue so that it
can be correctly resent.
( SR: 8606155189 CR: JAGad24506 )
The system tries to execute a callback function that has not
been initialized.
Resolution:
The callback function was set in the c720_isrRST routine
(initializing lisc->cbfns). A call to C720_START then
unlocks the bus, which leaves a window for another processor
waiting in an open routine to acquire it. The problem is
that lisc->cbfns is non-null. The fix for this is to remove
the UNLOCK,LOCK from C720_START which, after analysis, was
found to be unnecessary
( SR: 8606155173 CR: JAGad24490 )
The kernel did improper clean up in an abort condition.
A SCSI script MOVE instruction is patched in the cmd_setup
procedure in case of an abort to an INT instruction. The
instruction is not restored to MOVE in the cleanup of Abort.
Resolution:
The MOVE instruction is restored in the c720_cleanup_ABORT
procedure. This ensures that c720_start finds the command
bytes.
( SR: 8606155151 CR: JAGad24468 )
A buffer structure can get lost during heavy use of the SCSI
driver. Scsi_sp_start() does a dequeue of a buffer from
lp->special_scb_q queue and then tries to allocate a SCSI
control block (SCB). If the SCB allocation fails, the
routine simply returns and the buffer is not enqueued back.
This causes scsi_iowait() to wait forever, and the process
will hang. This also causes the buffer to be lost,
resulting in a memory leak.
Resolution:
The fix is to enqueue the buffer back into the head of the
queue if the SCB memory allocation fails in scsi_sp_start().
( SR: 8606133057 CR: JAGad02204 )
The sctl device driver's original design was not MP safe.
If an application makes heavy use of the driver, the code is
forced to execute on the same CPU. All processes using the
driver will accumulate on the same processor.
Resolution:
The necessary code to make the driver MP safe has been added
into the driver
( SR: 8606135767 CR: JAGad04900 )
A user application can pass an unwritable buffer (or portion
of it) to the sctl driver and it isn't verified before use.
We have to check the write access to this buffer before
trying to use it.
Resolution:
We validate the entire buffer prior to using it.
( SR: 8606155155 CR: JAGad24472 )
Memory was not available for error handling.
Resolution:
The system paniced because the kernel failed to preallocate
memory for its sense data. Due to this failure, a piece of
code, which sets the owner of the bus is skipped. The fix
is to do a dma setup during the opening of the bus. The
sense buffer is preallocated to ensure there is memory
available for the autosense.
( SR: 8606155022 CR: JAGad24339 )
Once a QUEUE FULL condition has been hit by a device, the
device is switch to untagged state. The device will then
process only one I/O at a time and stop queuing the I/Os.
The problem is that this condition is never reset even if
the device is back to a state where it can process queued
I/Os again.
Resolution:
The problem was that when we handle a QUEUE FULL condition
we turn off tagged queuing for that LUN, and never turn it
back on. A new algorithm was elaborated to throttle the
incoming bp rate by dynamically changing the queue depth
value. The fix actually completes that algorithm which only
partially fixed the problem (in PHKL_21607).
( SR: 8606125977 CR: JAGac46733 )
Some c720 driver information can be lost while trying to
recover from a non-responding device.
Resolution:
The c720_chip_hang() call may reset the value of lbp->owner
to NULL in some cases. If the lbp->owner is used after the
call it causes a panic. To avoid this panic, we cache this
information before calling the function.
( SR: 8606138825 CR: JAGad08088 )
A pointer is trusted and dereferenced in these functions.
We found that the pointer can be NULL for a variety of
corner-case reasons in the operation of the driver, and thus
checking for NULL should have been done and was not.
Resolution:
We now check the value of the pointer before dereferencing
it. If NULL, we dump the contents of the SCSI I/O card
registers to the syslog file and continue processing.
( SR: 8606155947 CR: JAGad25258 )
Twice in the code, we are missing wakeup().
Resolution:
It two places in the code, the lp->in_use field was
decremented but no corresponding wakeup() was called. This
defect is fixed by waking up the sleeping thread at the two
appropriate places.
( SR: 8606160406 CR: JAGad29728 )
The speed is defaulted improperly to Fast 20 on the LVD SCSI
boards where it should be Ultra2.
Resolution :
When the PDC settings are uninitialized for LVD SCSI boards,
the scsi speeds default for any board is Fast 20. LVD
boards were not taken care in the code that decides the
speed settings when the PDC settings are unitialized. The
switch statement deciding on the min_period, has been
changed to handle LVD boards (895 & 896).
( SR: 8606105472 CR: JAGab73559 )
The current architecture allows the queue depth to be set by
ioctl(). The value is not retained across reboots.
Resolution:
The driver code was enhanced to provide this feature. The
tag queue depth will now be controlled by a tunable value
(scsi_max_qdepth) which will not be lost after reboots.
( SR: 8606160479 CR: JAGad29800 )
The data page fault occurred when a stale pointer was
accessed while trying to resend the timed-out requests.
Resolution:
To solve this defect the timed-out I/O requests in internal
scsi queues are secured with proper locking.
PHKL_21989:
( SR: 8606142756 CR: JAGad12108 )
The built-in narrow single-ended SCSI bus on workstation
models J5600 and C3600 is incorrectly setup as a wide bus.
Resolution:
The model numbers J5600 and C3600 were added to conditionals
in the c720_init() and c720_pci_attach() routines.
PHKL_21607:
( SR: 8606132292 CR: JAGad01441 )
Specifically, the problem is that when a QUEUE FULL
condition occurs, tagged queuing is turned off for that
LUN, and is never turned back on when the queue empties.
For a complete solution a dynamic adjustment algorithm is
needed.
Resolution :
After a QUEUE FULL, we'll wait for any outstanding I/Os
to complete before turning tagged queuing back on, and then
we'll gradually increase the queue depth back up to the
previous max queue depth in such a way as to minimize the
likelihood of another immediate QUEUE FULL condition.
( SR: 8606130227 CR: JAGac95098 )
The "incomplete" field is decremented in the debug path in
SCSI services, but is not in the non-debug path. So non
debug kernel has incorrect information in this field.
Resolution:
The field is correctly updated, the way it is done in the
debug path.
( SR: 8606132288 CR: JAGad01437 )
This is a known limitation of ioscan and HSC bus. This
limitation was by design to reduce the scan times for HSC
devices.
Resolution:
A redesign of scsi_probe() has been completed which
minimized the time needed to probe and display all the
existing devices.
( SR: 8606132426 CR: JAGad01575 )
The scsi_dmesg_log_io() routine only gives the dev in
hexadecimal format.
Resolution:
The use of the GIO services help to translate the dev
into its hardware path
( SR: 8606106155 CR: JAGab75050 )
If we try to print from the isr (we may), get_printf_lock()
can wait up to 10mS per call if it cannot aquire the lock.
We easily do enough printing to exceed the allowed time to
keep a spinlock.
Resolution:
Several levels of messages have been introduce to greatly
reduce the number of printf() calls on a normal kernel and
on a debug kernel.
( SR: 8606133146 CR: JAGad02293 )
An unlock at the end of c720_start() allowed c720_timer()
to modify scripts memory. The assertion checked that the
scripts were not modified, hence failed.
Resolution:
Removed unlock/lock pair at the end of c720_start().
( SR: 8606133067 CR: JAGad02214 )
When the message is issued (typically caused by a bus RESET
during contingent allegiance condition (CAC)), the
corresponding I/O request is then lost and never returned
to the requestor, eventually causing a system hang.
Resolution:
When a bus RESET happens during a CAC, the c720 driver now
insures that all currently active I/O requests are posted
as incomplete and scheduled to be retried.
( SR: 8606133280 CR: JAGad02425 )
The routine controller c720_timer() uses C720_LOCK() which
uses assert to check the state of lisc->cbfns. Since
c720_timer() is called asynchronously to the rest of the
code, lisc->cbfns could be in any state, therefore should
not be checked
Resolution:
In c720_timer(), changed C720_LOCK(lisc) to
spinlock(lisc->id_lock) to avoid the assert.
( SR: 8606125811 CR: JAGac42754 )
The scsi_is_multilun() is hardcoded with various tape
devices, the list for which does not include this
particular device.
Resolution:
Take DDS4 autochangers into account in scsi_is_multilun().
PHKL_21504:
( SR: 8606125610 CR: JAGac41000 )
The in-use count for a SCSI LUN was not being incremented
before the lock on the LUN was released and the I/O request
completed. Since the in-use count was zero, a succeeding
I/O request to close the LUN deallocates memory for the LUN
lock. The driver then attempts to reacquire the LUN lock
which has since been deallocated causing a data memory
protection panic.
Resolution :
The SCSI LUN in-use count is being incremented before the
LUN is unlocked and biodone() called and decremented
after the call to biodone() and the LUN is again locked.
( SR: 8606130829 CR: JAGac97596 )
The calculation for a SCSI hardware memory pointer
incorrectly computed the number of bytes for the size of
SCSI SCRIPTS RAM.
Resolution :
The calculation was modified to use the sizeof() function
to return the number of bytes allocated to SCSI SCRIPTS
RAM.
PHKL_20688:
( SR: 8606127757 CR: JAGac78558 )
The SCSI driver detects a hardware failure and resets the
bus. However, the reset operation cannot resolve the bus
hang and the reset interrupt never occurs. Without a bus
reset timeout, the processes hang waiting for I/O's queued
for the bus. LVM expects either an I/O error or an EPOWERF
(timeout) to continue.
Resolution:
Added code to timeout on an unsuccessful bus reset and abort
the I/O with a return of EPOWERF.
PHKL_20629:
( SR: 8606112882 CR: JAGab93301 )
While resolving defect JAGab78589 (in SCSI pass-through
driver modules spt and spt0), patch PHKL_20452 introduced a
defect which resulted in memory initialized to the wrong
address.
Resolution:
Corrected initialization of memory buffer addresses.
( SR: 8606110931 CR: JAGab83681 )
SCSI message logging function was calling priviledged copy
routine with KERNELSPACE id and a stack buffer. Kernel
stack was moved out of KERNELSPACE in 64 bit system, which
caused Data Page Fault panic.
Resolution:
KERNELSPACE id was replaced with ldsid() function,
which uses correct space id for the buffer.
PHKL_20452:
( SR: 5003432120 CR: JAGaa22888 )
NOT READY devices are continually retried, extending beyond
pftimeout period, and until device becomes READY.
Resolution:
Cause IO retries to NOT READY devices to go to a
new routine (sd_retry_check) which limits the
retries to the pftimeout period if B_PFTIMEOUT set.
( SR: 8606103129 CR: JAGaa44450 )
scsi_fast_read & scsi_fast_write used driver switch table
in non-standard way causing unexpected side-effects on
pass-through functionality.
Resolution:
Removed scsi_fast_read/write because inserting them
into the driver switch table at open time causes
pass-through command mode to stop working.
( SR: 8606103814 CR: JAGab19070 )
No check for lsp NULL pointer in c720_isrAbort() before
dereference.
Resolution:
Check if lsp pointer is set in c720_isrAbort()
before using.
( SR: 8606103810 CR: JAGab19072 )
In open path the SIOP driver loops until all interrupts are
cleared, but there is no check to prevent looping forever
when either bad data or -1 is returned.
Resolution:
Added check to recover if return of -1 is received.
( SR: 1653307298 CR: JAGab20815 )
Driver resets SCSI bus on Parity Error, instead of aborting
and retrying.
Resolution:
Change in SIOP driver to Abort the I/O request on
Parity Error.
( SR: 8606100396 CR: JAGab31749 )
Wrong test condition in SCSI driver routine to log SIOP
register access.
Resolution:
Change test condition to only verify SIOP is not
running, or that we are only accessing the ISTAT
register.
( SR: 8606103820 CR: JAGab39677 )
Only enabled Master Parity checking for SIOPs 53C720 and
53C770, although this needs to be set for all SIOPs.
Resolution:
Removed check for specific SIOPs, and now enables
Master Parity checking for all SIOPs (including
PCI-attached).
( SR: 8606103148 CR: JAGab69517 )
Pointer not initialized to NULL in LUN open routine.
Resolution:
Initialized the pointer to NULL.
( SR: 8606103192 CR: JAGab69594 )
Infinite SCSI IO retry due to variable not getting set.
Resolution:
Set variable at end of strategy routine.
( SR: 8606105969 CR: JAGab74731 )
SIOP not started correctly after Bus Device Reset.
Resolution:
Call SIOP's startup routine following SCSI Bus
Device Reset.
( SR: 8606106038 CR: JAGab74836 )
SCSI Ultra-II speeds not negotiated for PCI-attached
Ultra-II adapters with Ultra-II devices.
Resolution:
Added SCSI Ultra-II speed negotiations for Ultra-II
adapters and devices.
( SR: 8606103826 CR: JAGab76136 )
Improper handling of WDTR and SDTR in some cases for
PCI-attached SIOPs.
Resolution:
Expanded script interrupt support & associated
scripts support for handling SDTR and WDTR, and
other conditions there weren't handled completely
correct.
( SR: 8606108198 CR: JAGab78589 )
Newly allocated memory for buf structure not initialized.
Resolution:
Fully initialized buf structure after allocation.
( SR: 8606110476 CR: JAGab83179 )
EIM mask of ~0x1f did not mask lower 6bits of register for
64-bit architecture, where as 32-bit architecture always
has 6th bit set to zero.
Resolution:
Changed EIM mask to ~0x3f to mask all 6 bits for
64-bit architecture.
( SR: 8606110477 CR: JAGab83180 )
Some machines return more data from the SIOPs for SCSI
Width, Speed, and Mode than was allowed by original design
of the SCSI driver.
Resolution:
Changed SCSI driver to provide buffer area for all
the Width, Speed, and Mode data returned from all
supported SIOPs.
( SR: 8606110479 CR: JAGab83182 )
Early revision 896 SCSI controllers send wrong data on the
SCSI bus under certain circumstances.
Resolution:
During initialization of 896, disabled the DPR bit
that permits this corner-case data corruption.
( SR: 8606110481 CR: JAGab83184 )
SCSI driver did not verify pointer was set before using it
in a printf call.
Resolution:
Checked for NULL pointer, and used the value zero
if pointer is not populated for printf call.
( SR: 8606110616 CR: JAGab83364 )
Pointer variable set incorrectly.
Resolution:
Correctly set the pointer variable.
( SR: 8606110653 CR: JAGab83401 )
Wrong value sent onto the SCSI bus for SCSI Abort Message
for PCI-attached SIOPs.
Resolution:
Changed the value used for the SCSI Abort Message
to be Endian-neutral in SIOP script initialization.
( SR: 8606110782 CR: JAGab83531 )
Populated SCSI LUN pointer before known to be needed.
Resolution:
Changed to only populate the SCSI LUN pointer when
required.
PHKL_20208:
( SR: 1653281824 DTS: JAGaa42584 )
When a device's write cache is enabled, the device may
signal successful completion of a write command upon
receiving (and caching) the data, but before the data has
been written to the media. This is referred to as
"immediate reporting". If an error (i.e. bad media) occurs
during the actual execution of the write to media, the data
can be lost. The device reports this error back to the
driver as an "unrecovered deferred error". The driver
panics.
Resolution:
The driver was modified to handle the "unrecovered deferred
error" by blocking all IO requests for the disk when a
deferred error occurs, until the device is closed and
reopened. It no longer panics the system.
PHKL_19776:
( SR: 8606103698 CR: JAGab70738 )
( SR: 8606101027 CR: JAGab70313 )
When SCSI disk was inaccessible, code would keep retrying
the failed IO continually.
To reproduce the LVM VG long failover times, do:
1. create LV with a 4-way PV on a dual-ported AutoRAID, with
two HW paths defined for the VG access (see vgdisplay)
2. with continual IO via the primary path, pull the SCSI
cable off from the primary path.
3. if it takes inordinately longer than the time set via
pvchange -t XX, to failover to alternate path, then you
duplicated the problem. if it takes about (2*XX)+15secs
then you've fixed the problem. Note that XX is the num
of seconds for pftimeout, set by pvchange -t XX. Also
note that the value of XX should be 30secs or longer.
Resolution:
Stopped retries on inaccessible devices, allow retries
when device is once again accessible.
( SR: 1653310672 CR: JAGab31999 )
Cached SCSI INQUIRY data was returned instead of going
directly to the disk for this information.
To reproduce the cached INQUIRY data problem, do:
1. boot up with a disk that can be removed from service.
2. use ioscan to identify the disk.
3. perform continual IO on the disk w/read, write to
/dev/null
4. power-off the disk.
5. perform diskinfo -v on the disk devfile:
If it shows full disk information, you've duplicated.
If it shows no such device or file, you've fixed it.
Resolution:
Perform SCSI INQUIRY directly to device, always.
Note: this fix was required for the Retries fix to
know when the disk was actually not accessible, and
to give positive recognition of becoming accessible,
for CR JAGab70738 and CR JAGab70313.
PHKL_19245:
( SR: 8606103582 DTS: JAGaa09970 )
WSIO did not support kernel SCSI Pass thru ioctl(), and SIO
did not support this for kernel or user space.
Resolution:
Enhanced the SCSI Pass thru ioctl(), SIOC_IO, on the WSIO
side to support calls from Kernel space too. Added SCSI
Pass thru ioctl() functionality on the SIO side; supports
calls from both User and Kernel space.
PHKL_19561:
( SR: 4701424978 DTS: JAGab13476 )
After installing the latest firmware in the HP-PB F/W SCSI
Adapter, reading an odd-length record from a tape device
that supports wide transfer mode causes an I/O error.
The HP-PB FW SCSI Adapter expected a specific sequence of
interactions by the driver when handling this event.
Resolution:
Change the sequence of interactions to that expected by the
card.
PHKL_17333:
( SR: 1653284257 DTS: JAGaa44107 )
NIO disks become unresponsive causing commands like "ioscan"
& "dd" to hang. This problem can only be seen on s800
systems, and happens because when the "frozen" bit is set in
the PDA for the disk, without any means of "unfreezing" it.
Resolution:
A target is put into the frozen state when an abort command
is sent to it. When the command completes all I/O queues
will be checked for additional abort commands. The
completion reply for the last abort command will unfreeze
the target.
PHKL_14807:
None; The previous patch was recut with enhanced
optimization. No code was changed.
PHKL_13371:
( SR: 4701376111 DTS: DSDe440799 )
When a check condition occurs on a probe to the CASCADE
device (C2430D), a panic occurs due to a code path that
is taken which leads to an uninitialized pointer being
dereferenced. Note that the CASCADE may not be the only
disk device that could cause this problem to occur.
The panic is a data page fault.
PHKL_19287:
( SR: 8606101377 DTS: JAGab17408 )
LVM failover to alternate path fails on logical volumes
configured on SCSI3 devices as the driver ingnores sense
data from SCSI3 devices.
Resolution: Modified scsi_sense_action() to process sense
data from SCSI3 devices too.
PHKL_20157:
( SR: 8606107849 DTS: JAGab78147 )
PCI ID for the 53C895A chip is not in the list of
supported PCI IDs. Therefore c720 driver does not
claim this chip.
Resolution:
Add 53C895A chip to the list of supported devices.
( SR: 8606107164 DTS: JAGab76873 )
c720 driver makes an erroneous assumption that unless an
interface is running at Ultra2 speeds, it is not in LVD
mode. N Class systems run the built-in LVD SCSI at Fast
speed, not Ultra2.
Resolution:
Make driver look at the actual SCSI bus mode irrespective
of bus speed and set the description accordingly.
( SR: 8606106038 DTS: JAGab76903 )
There was a logic problem in the checking for PCI HBA
cards which caused the driver to think that it was on
an Ultra card when it was actually on an Ultra-2 card.
Resolution:
Correct the logic error to make the driver detect Ultra2
card correctly.
( SR: 8606105969 DTS: JAGab74731 )
C720 driver does not restart the SCSI chip properly
when an unexpected disconnect occurs.
Resolution:
Remove the return statement that causes the routine
handling Unexpected disconnect return before
restarting the chip.
( SR: 8606103151 DTS: JAGab69533 )
c720 driver misinterpreted the data returned by the
firmware for the width of bus and erroneously
configured the SCSI interface as narrow when the
interface truely is wide. This caused communication
failure with the drives and thedrives were not
detected correctly.
Resolution:
Correct the interpretation of data returned by the firmware
for the width of the bus.
PHKL_17368:
In the scsi pass through driver, we check to see if the
device is scsi3 (so that we can set the "fast wide" flag).
A "lun report page command" is sent to hot spares (and they
are therefore visible to SAM) only if the "fast wide" flag
is set. To reproduce the defect, configure hot spare(s) on
a NIKE (attatched to a SCSI3 card) and run SAM.
Resolution:
A strcmp(drv_name,"scsi13") was being done; this should be
strcmp(drv_name,"scsi3").
PHKL_14688:
The scsi_pt driver issued a SCSI_CTRL_REQ_MSG to the
lower driver from spt_open() and exited, cleaning up the
active request, without waiting for command completion.
Reproduction method:: Have a device, say a tape drive,
on a bus along with other devices (disks). Bind the
tape device to the scsi_pt driver. Run 'dd' on the
other devices on the bus and repeatedly issue a
inquiry command to the tape drive. System panics
almost immediately.
SR:
1653256065 1653281824 1653284257 1653307298 1653310672
4701376111 4701424978 5003432120 5003440982 8606100396
8606101027 8606101377 8606103129 8606103148 8606103151
8606103192 8606103582 8606103698 8606103810 8606103814
8606103820 8606103826 8606105472 8606105969 8606106038
8606106155 8606107164 8606107849 8606108198 8606110476
8606110477 8606110479 8606110481 8606110616 8606110653
8606110782 8606112261 8606112882 8606125610 8606125811
8606125977 8606127757 8606130227 8606130829 8606132288
8606132292 8606132426 8606133057 8606133067 8606133146
8606133280 8606135046 8606135767 8606137271 8606138825
8606142756 8606147432 8606155022 8606155151 8606155155
8606155173 8606155189 8606155947 8606157951 8606158437
8606158623 8606158737 8606160406 8606160479 8606161696
8606166729 8606167125 8606168360 8606169435 8606169631
8606173791 8606176639 8606179935 8606185203 8606186960
8606189487 8606193416 8606199984 8606204859 8606207857
8606216118 8606223745 8606225743 8606230706 8606232873
8606244278 8606249862
Patch Files:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lb