 |
≫ |
|
|
|
パッチ名: PHCO_35213
パッチ摘要: s700_800 11.23 VRTS 5.0 MP1 VRTSobc33コマンドパッチ
作成日: 07/04/05
公開日: 07/04/11
ハードウェアプラットフォームおよびOSリリース:
s700: 11.23
s800: 11.23
現象:
PHCO_35213:
(SR:8606430161 CR:JAGaf89620)
1. vxsvcサービスは、csf_resolv.confファイルを使って実行します。ところ
が、一部のエントリがこのファイル内にないと、以下のようなエラーメッ
セージがターミナルに表示されます。
line: 7, Error - parse error ...[以下省略].
2. cfgsecurity.shの実行中に、以下のようなエラーメッセージが表示されま
す。cfgsecurity.shは、VEAのセキュリティ構成を手動で設定する際に使用
する構成スクリプトです。エラーメッセージは以下のとおりです。
Established trust with the broker
devgiri.vxindia.veritas.com
vea_domain private domain is present in the AB. NOT
creating new one. User vea_agent exists in the private
domain vea_domain
Saved long term credential for user vea_agent in the
domain vea_domain
Set the security info for the agent Root ( auth host
devgiri.vxindia.veritas.com port 1556 AgentId vea_agent
domain
vea_domain@devgiri.vxindia.veritas.com)
Root agent's security is High
VEA veaconfig ERROR V-40-49444-10 Invalid agent name
specified.
3. "veaconfig -c add_user"の実行中に、vxsvcでコアダンプが取られます。
スタックトレースは、"問題点の説明"セクションを参照してください。
4. VRTSobcパッケージのインストール時に、マンページがインストールされま
せん。
5. インストール時に使用するファイルのパーミッションが不適切(非安全)で
す。
6. HP OEMのデフォルト構成はHost Controllerでなければなりません。
7. "veaconfig -c agent_info -a actionagent"が"Unable to access the
file /opt/VRTSaa/etc/domain.cf"というメッセージを表示します。
8. vxfingerは、vxsvcシステムにログインしているユーザー数を表示するユー
ティリティです。ところが、このユーティリティのターミナルでの出力が
適切にフォーマットされていません。
9. "others"の読み取りパーミッションをクリティカルファイル/ログから削除
する必要があります。
問題点の説明:
PHCO_35213:
(SR:8606430161 CR:JAGaf89620)
1.(Symantec不具合番号: 375835)
csf_resolve.conf内に一部のエントリがないと、"parse error"というメッセ
ージが表示されていました。
解決方法:
"parse error"というメッセージを画面に表示しないように、csf_resolv.conf
の読み取り/解析コードを修正しました。
2.(Symantec不具合番号:413940)
cfgsecurity.shの実行中に、以下のようなエラーメッセージが表示されていま
した。cfgsecurity.shは、VEAのセキュリティ構成を手動で設定する際に使用
する構成スクリプトです。表示されるエラーメッセージは以下のとおりです。
Established trust with the broker
devgiri.vxindia.veritas.com
vea_domain private domain is present in the AB. NOT
creating new one.
User vea_agent exists in the private domain vea_domain
Saved long term credential for user vea_agent in the
Domain vea_domain
Set the security info for the agent Root ( auth host
devgiri.vxindia.veritas.com port 1556 AgentId vea_agent
domain
vea_domain@devgiri.vxindia.veritas.com)
Root agent's security is High
VEA veaconfig ERROR V-40-49444-10 Invalid agent name
specified.
解決方法:
不要なエラーメッセージを表示しないようにスクリプトを修正しました。
3.(Symantec不具合番号: 511497)
"veaconfig -c add_user"を実行すると、vxsvcでコアダンプが取られていまし
た。スタックトレースは以下のとおりです。
fec32d40 strcmp (e99820, 0, fcc0460c, 0, fcc044e4, 1) + 234
fee1215c _VxlstrcmpA (e99820, 0, c100000f, c100000f, b54108, 1) + 34
fef6bd64 VxlstrcmpA (e99820, 0, 4b6235, fcc04708, 1, 0) + 34
00065898 __1cRModifyPermissions6Fpc0000IInL_isis_objid__I_
(fcc05854, e9f0d0, 843a78, ea04b0, e96518, 0) + 16800021944
__1cNDAuthzControl6FnL_isis_objid_IIpv1II1pGpnU
_VxApiProgressPacket__cp
knK_isis_guid_p0p1_I_ (fcc05b44, 1, 1, b46e50, b4ed40, 0) + 8cc
00020114 MRegnControl (fcc05c14, 1, 1, b46e50, b4ed40, 0) + 444
fefa68dc
__1cIProviderMVxapiControl6MnL_isis_objid_IIpv2II2pGpnU
_VxApiProgressPa
cket__cpknK_isis_guid_p1p2_I_ (fcc05c3c, fcc0603c, 1, 1,
b46e50, b4ed40) + 1f4
fef52428 PrCallProvider (b46b60, fcc063c0, fcc06644, 1,
1, b46e50) + cc8
fef54e20 PrCallDispatch (69b8d8, fcc065e0, fcc06644, 1,
1, b46e50) + b40
0007c83c ci_invoke (fcc06634, 17e, fcc0691c, 0, fcc0676c,
fcc06768) + 2ec
0007a7bc
__1cZVxPALObjectManagementImplGInvoke6MrknHVeritasDVEAF
TypesGBinary_r4n
0DKBinary_out__v_ (603b90, fcc06934, fcc0691c, fcc0683c,
1, 562f8c) + 1dc
000d4848
__1cLPOA_VeritasDVEAQObjectManagementLInvoke_skel6FrnRTAO
_ServerRequest
_pv5_v_ (fcc06d40, 603ba0, fcc06a90, d45f8, 57c070, 0)
+ 250
002293a0
__1cPTAO_ServantBasebBsynchronous_upcall_dispatch6MrnRTAO
_ServerRequest
_pv3_v_ (603b98, fcc06d40, fcc06a90, 603ba0, 24bb84,
577e14) + f0
000db844
__1cLPOA_VeritasDVEAQObjectManagementJ_dispatch6MrnRTAO
_ServerRequest_p
v_v_ (603ba0, fcc06d40, fcc06a90, fcc06d40, fcc06b00,
5a3560) + 54
001fd6a8
__1cSTAO_Object_AdapterQdispatch_servant6MrknNTAO_Object
Key_rnRTAO_Serv
erRequest_nQCORBA_Object_out__i_ (0, fcc06dac, fcc06d40,
fcc06b6c, 1, 562f8c)
解決方法:
メモリーリーク特定ツールを使ってコアコードパスを検証し、その結果に基づ
いて必要な修正を行いました。これで、メモリー破壊問題やメモリーリークは
すべて解決されます。
4.(Symantec不具合番号: 601955)
VRTSobcパッケージのインストール時に、マンページがインストールされませ
んでした。
解決方法:
マンページもインストールするようにVRTSobc.psfを修正しました。
5.(Symantec不具合番号: 611323)
インストール時に使用するファイルのパーミッションが不適切(非安全)でした。
インストール時の安全でないファイルパーミッション - 最近、お客様から、
ログファイル、インストールディレクトリおよびsetuid/setgidバイナリが
world-writable(あらゆるユーザーによる書き込みが可能な状態)になっている
というご指摘を受けました。
解決方法:
777ではなく644のパーミッションを持つ状態ファイルを作成するコードを追加
しました。また、setuidビットをvxguidgenユーティリティのパーミッション
に追加しました。さらに、"chmod u+s vxguidgen"を実行するコードを追加し
ました。
6.(Symantec不具合番号: 612450)
HP OEMのデフォルト構成はHost Controllerでなければなりません(特に、
VRTSob/VRTSobc/VRTSccgパッケージの場合)。
解決方法:
HP OEMの場合は、VRTSob/VRTSobcパッケージのインストール時のデフォルト構
成をHost Controllerモードに設定するようにコードを修正しました。
7.(Symantec不具合番号: 616023)
"veaconfig -c agent_info -a actionagent"が"Unable to access the file
/opt/VRTSaa/etc/domain.cf"というメッセージを表示していました。
また、(CMHがインストールされている)あるホスト上で、
"/opt/VRTSobc/pal33/bin/veaconfig -c agent_info -a"コマンドを実行する
と、以下のエラーメッセージが表示されていました。
ERROR: File "/opt/VRTSobc/pal33/etc/alerttypes.xml"should
have mtime
"1154324018" but the actual mtime is "1148635188".
ERROR: File "/opt/VRTSobc/pal33/etc/interfaceform.xml"
should have mtime "1154324018" but the actual
mtime is "1155721167".
ERROR: File "/opt/VRTSobc/pal33/etc/interfaceform.xml"
should have size "16666" bytes but the actual
size is "17492" bytes.
ERROR: File "/opt/VRTSobc/pal33/etc/objecttypes.xml"
should have mtime "1154324018" but the actual
mtime is "1155721165".
ERROR: File "/opt/VRTSobc/pal33/etc/objecttypes.xml"
should have size "2769" bytes but the actual
size is "3114" bytes.
ERROR: File "/opt/VRTSobc/pal33/etc/securityform.xml"
should have mtime "1154324018" but the actual
mtime is "1155721170".
ERROR: File "/opt/VRTSobc/pal33/etc/securityform.xml"
should have size "1387" bytes but the actual size
is "1311" bytes.
ERROR: Fileset "VRTSobc33.VRTSOBC33,l=/,r=3.3.722.0" had
file errors.
ERROR: Control file "configure" should have cksum "
2182245702" but the actual cksum is "3039531648".
解決方法:
対応するVRTSobc33パケージを"volatile"とマークするようにパッチスクリプ
トを修正しました。これで、以後、swverifyエラーは起きません。
8.(Symantec不具合番号: 616700)
vxfingerは、vxsvcシステムにログインしているユーザー数を表示するユーテ
ィリティです。ところが、このユーティリティのターミナルでの出力が、適切
にフォーマットされていませんでした。
1) ホスト名が正しく表示されない。
2) 名前が"???"と表示される。
解決方法:
出力フォーマットを修正しました。
9.(Symantec不具合番号: 704038)
"others"の読み取りパーミッションをクリティカルファイル/ログから削除す
る必要があります。
解決方法:
"chmod 0750 /etc/vx/isis"と"chmod 0750 /var/vx/isis"を追加しました。
-----------------------------------------------------------------------------
Patch Name: PHCO_35213
Patch Description: s700_800 11.23 VRTS 5.0 MP1 VRTSobc33 Command Patch
Creation Date: 07/04/05
Post Date: 07/04/11
Hardware Platforms - OS Releases:
s700: 11.23
s800: 11.23
Products:
VRTSobc33 3.3.722.0
Filesets:
VRTSobc33.VRTSOBC33,fr=3.3.722.0,fa=HP-UX_B.11.23_IA/PA,v=HP
VRTSobc33.VRTSOBC33,fr=3.3.721.0,fa=HP-UX_B.11.23_IA/PA,v=Symantec
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_35213: ABORT CORRUPTION
Category Tags:
defect_repair general_release critical halts_system
corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_35213
Symptoms:
PHCO_35213:
( SR: 8606430161 CR: JAGaf89620 )
1. csf_resolv.conf file is used by vxsvc service for
execution. If some entries are missing in this file,
following error messages are displayed on the terminal.
line: 7, Error - parse error ...[cannot continue].
2. Following error message displayed while running
cfgsecurity.sh, this is the configuration script
which is used to manually setup security configuration for
VEA.
Error message is as follows:
Established trust with the broker
devgiri.vxindia.veritas.com
vea_domain private domain is present in the AB. NOT
creating new one. User vea_agent exists in the private
domain vea_domain
Saved long term credential for user vea_agent in the
domain vea_domain
Set the security info for the agent Root ( auth host
devgiri.vxindia.veritas.com port 1556 AgentId vea_agent
domain
vea_domain@devgiri.vxindia.veritas.com)
Root agent's security is High
VEA veaconfig ERROR V-40-49444-10 Invalid agent name
specified.
3. veaconfig -c add_user causes vxsvc to core dump
Please see defect description for stack strace.
4. No man pages are installed with VRTSobc package.
5. Insecure file permissions at install time
6. HP OEM default configuration has to be Host Controller.
7. veaconfig -c agent_info -a actionagent, showing the
message--'Unable to access the file
/opt/VRTSaa/etc/domain.cf'
8.vxfinger is the utility which shows how many users are
logged into the vxsvc system. Output of this utility on
the terminal was not properly formatted
9.Need to remove read permissions for others from
critical files and logs
Defect Description:
PHCO_35213:
( SR: 8606430161 CR: JAGaf89620 )
1. (Symantec Incident Number: 375835 )
Parse error message sent out when entries are missing in
csf_resolve.conf
Resolution: Changes were made to code which is
reading/parsing this csf_resolv.conf and stop displaying
the parse error message on screen.
2. ( Symantec Incident Number:413940)
Following error message displayed while running
cfgsecurity.sh, this is the configuration script
which is used to manually setup security configuration
for VEA.
Error message is as follows:
Established trust with the broker
devgiri.vxindia.veritas.com
vea_domain private domain is present in the AB. NOT
creating new one.
User vea_agent exists in the private domain vea_domain
Saved long term credential for user vea_agent in the
Domain vea_domain
Set the security info for the agent Root ( auth host
devgiri.vxindia.veritas.com port 1556 AgentId vea_agent
domain
vea_domain@devgiri.vxindia.veritas.com)
Root agent's security is High
VEA veaconfig ERROR V-40-49444-10 Invalid agent name
specified.
Resolution:
Modified the scripts to avoid displaying unwanted error
messages.
3. ( Symantec Incident Number : 511497 )
veaconfig -c add_user causes vxsvc to core dump
Following is the stack strace.
fec32d40 strcmp (e99820, 0, fcc0460c, 0, fcc044e4, 1)
+ 234
fee1215c _VxlstrcmpA (e99820, 0, c100000f, c100000f,
b54108, 1) + 34
fef6bd64 VxlstrcmpA (e99820, 0, 4b6235, fcc04708, 1, 0)
+ 34
00065898 __1cRModifyPermissions6Fpc0000IInL_isis_objid__I_
(fcc05854, e9f0d0,
84
3a78, ea04b0, e96518, 0) + 168
00021944
__1cNDAuthzControl6FnL_isis_objid_IIpv1II1pGpnU
_VxApiProgressPacket__cp
knK_isis_guid_p0p1_I_ (fcc05b44, 1, 1, b46e50, b4ed40, 0)
+ 8cc
00020114 MRegnControl (fcc05c14, 1, 1, b46e50, b4ed40, 0)
+ 444
fefa68dc
__1cIProviderMVxapiControl6MnL_isis_objid_IIpv2II2pGpnU
_VxApiProgressPa
cket__cpknK_isis_guid_p1p2_I_ (fcc05c3c, fcc0603c, 1, 1,
b46e50, b4ed40) + 1f4
fef52428 PrCallProvider (b46b60, fcc063c0, fcc06644, 1,
1, b46e50) + cc8
fef54e20 PrCallDispatch (69b8d8, fcc065e0, fcc06644, 1,
1, b46e50) + b40
0007c83c ci_invoke (fcc06634, 17e, fcc0691c, 0, fcc0676c,
fcc06768) + 2ec
0007a7bc
__1cZVxPALObjectManagementImplGInvoke6MrknHVeritasDVEAF
TypesGBinary_r4n
0DKBinary_out__v_ (603b90, fcc06934, fcc0691c, fcc0683c,
1, 562f8c) + 1dc
000d4848
__1cLPOA_VeritasDVEAQObjectManagementLInvoke_skel6FrnRTAO
_ServerRequest
_pv5_v_ (fcc06d40, 603ba0, fcc06a90, d45f8, 57c070, 0)
+ 250
002293a0
__1cPTAO_ServantBasebBsynchronous_upcall_dispatch6MrnRTAO
_ServerRequest
_pv3_v_ (603b98, fcc06d40, fcc06a90, 603ba0, 24bb84,
577e14) + f0
000db844
__1cLPOA_VeritasDVEAQObjectManagementJ_dispatch6MrnRTAO
_ServerRequest_p
v_v_ (603ba0, fcc06d40, fcc06a90, fcc06d40, fcc06b00,
5a3560) + 54
001fd6a8
__1cSTAO_Object_AdapterQdispatch_servant6MrknNTAO_Object
Key_rnRTAO_Serv
erRequest_nQCORBA_Object_out__i_ (0, fcc06dac, fcc06d40,
fcc06b6c, 1, 562f8c)
Resolution : Verified the core code path through memory
leak identification tools and fixed the issue. All Memory
corruption issue and memory leak identified were fixed.
4. ( Symantec Incident Number : 601955 )
No man pages are installed with VRTSobc package.
Resolution :
The changes for VRTSobc.psf mandated these changes.
5. ( Symantec Incident Number : 611323 )
Insecure file permissions at install time
"Insecure file permissions at install time - we have a
recent customer escalation regarding world-writable log
files and install directories, as well as setuid/setgid
binaries.
Resolution :
Added code to create the state file with 644
permissions instead of 777. Added setuid bit to
permissions of vxguidgen utility
Added code to chmod u+s vxguidgen.
6. ( Symantec Incident Number : 612450 )
HP OEM default configuration has to be Host Controller.
(particularly for VRTSob, VRTSobc, VRTSccg and VRTSaa
packages).
Resolution :
For HP OEM, the default configuration upon package
installation of VRTSob and VRTSobc has to be set to Host
Controller mode.
7. ( Symantec Incident Number 616023 )
veaconfig -c agent_info -a actionagent, showing the
message--'Unable to access the file
/opt/VRTSaa/etc/domain.cf'
On a host(CMH installed) when running the command
/opt/VRTSobc/pal33/bin/veaconfig -c agent_info -a
ERROR: File "/opt/VRTSobc/pal33/etc/alerttypes.xml"should
have mtime
"1154324018" but the actual mtime is "1148635188".
ERROR: File "/opt/VRTSobc/pal33/etc/interfaceform.xml"
should have mtime "1154324018" but the actual
mtime is "1155721167".
ERROR: File "/opt/VRTSobc/pal33/etc/interfaceform.xml"
should have size "16666" bytes but the actual
size is "17492" bytes.
ERROR: File "/opt/VRTSobc/pal33/etc/objecttypes.xml"
should have mtime "1154324018" but the actual
mtime is "1155721165".
ERROR: File "/opt/VRTSobc/pal33/etc/objecttypes.xml"
should have size "2769" bytes but the actual
size is "3114" bytes.
ERROR: File "/opt/VRTSobc/pal33/etc/securityform.xml"
should have mtime "1154324018" but the actual
mtime is "1155721170".
ERROR: File "/opt/VRTSobc/pal33/etc/securityform.xml"
should have size "1387" bytes but the actual size
is "1311" bytes.
ERROR: Fileset "VRTSobc33.VRTSOBC33,l=/,r=3.3.722.0" had
file errors.
ERROR: Control file "configure" should have cksum "
2182245702" but the actual cksum is "3039531648".
Resolution:
This patch script would mark the corresponding VRTSobc33
Packages xml file as volatile thus avoiding swverify
errors in future.
8. ( Symantec Incident Number 616700 )
vxfinger is the utility which shows how many users are
logged into the vxsvc system. Output of this utility on
the terminal was not properly formatted
1) Hostname is not displayed completely.
2) Name shown as '???'
Resolution: Fixed the output format.
9. ( Symantec Incident Number 704038 )
Need to remove read permissions for others from
critical files and logs
Resolution:
Added "chmod 0750 /etc/vx/isis" and
"chmod 0750 /var/vx/isis".
Enhancement:
No
SR:
8606430161
Patch Files:
VRTSobc33.VRTSOBC33,fr=3.3.722.0,fa=HP-UX_B.11.23_IA/PA,
v=HP:
VRTSobc33.VRTSOBC33,fr=3.3.721.0,fa=HP-UX_B.11.23_IA/PA,
v=Symantec:
/opt/VRTSobc/pal33/bin/pal_get
/opt/VRTSobc/pal33/bin/palclient
/opt/VRTSobc/pal33/bin/vea_get
/opt/VRTSobc/pal33/bin/veaconfig
/opt/VRTSobc/pal33/bin/veainfo
/opt/VRTSobc/pal33/bin/vxalerttype
/opt/VRTSobc/pal33/bin/vxfinger
/opt/VRTSobc/pal33/bin/vxguidgen
/opt/VRTSobc/pal33/bin/vxini
/opt/VRTSobc/pal33/bin/vxinterface
/opt/VRTSobc/pal33/bin/vxobjecttype
/opt/VRTSobc/pal33/bin/vxpal
/opt/VRTSobc/pal33/bin/vxpalctrl
/opt/VRTSobc/pal33/bin/vxregctl
/opt/VRTSobc/pal33/bin/vxsecaz
/opt/VRTSobc/pal33/etc/interfaceform.xml
/opt/VRTSobc/pal33/install/OBC_RegEntries.install
/opt/VRTSobc/pal33/install/OBC_RegEntries.uninstall
/opt/VRTSobc/pal33/install/VRTSobc.log
/opt/VRTSobc/pal33/install/cfgsecurity.sh
/opt/VRTSobc/pal33/install/setup_rgd.pl
/opt/VRTSobc/pal33/lib/libcsfinterface3.sl
/opt/VRTSobc/pal33/lib/libcsfsupport3.sl
/opt/VRTSobc/pal33/lib/libdb-4.4.sl
/opt/VRTSobc/pal33/lib/libleafregn.sl
/opt/VRTSobc/pal33/lib/libpal_at.sl
/opt/VRTSobc/pal33/lib/librgd.sl
/opt/VRTSobc/pal33/lib/libvea_cl.sl
/opt/VRTSobc/pal33/lib/libvxACE.sl.3
/opt/VRTSobc/pal33/lib/libvxPBX.sl
/opt/VRTSobc/pal33/lib/libvxPBXCommon.sl
/opt/VRTSobc/pal33/lib/libvxPBXIOP.sl
/opt/VRTSobc/pal33/lib/libvxPBXVxSS.sl
/opt/VRTSobc/pal33/lib/libvxTAO.sl.3
/opt/VRTSobc/pal33/lib/libvxTAO_CustomEndpointSelectors.sl
/opt/VRTSobc/pal33/lib/libvxTAO_Messaging.sl.3
/opt/VRTSobc/pal33/lib/libvxVxSSIOP.sl
/opt/VRTSobc/pal33/lib/libvxcparser.sl
/opt/VRTSobc/pal33/lib/libvxpal3.sl
/opt/VRTSobc/pal33/lib/libvxveautil.sl
/opt/VRTSobc/pal33/msgcats/cli/catalog/en/
climessagecatalog.txt
/opt/VRTSobc/pal33/msgcats/cli/catalog/en/veaconfig.txt
/opt/VRTSobc/pal33/msgcats/system/IsisSkin/java/1033/
SystemMessageCatalog.txt
what(1) Output:
VRTSobc33.VRTSOBC33,fr=3.3.722.0,fa=HP-UX_B.11.23_IA/PA,
v=HP:
/opt/VRTSobc/pal33/bin/pal_get:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/palclient:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vea_get:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/veaconfig:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/veainfo:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxalerttype:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxfinger:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxguidgen:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxini:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxinterface:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxobjecttype:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxpal:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxpalctrl:
None
/opt/VRTSobc/pal33/bin/vxregctl:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/bin/vxsecaz:
$Revision: 92453-07 linker linker crt0.o B.11.33 020
605 $
/opt/VRTSobc/pal33/etc/interfaceform.xml:
None
/opt/VRTSobc/pal33/install/OBC_RegEntries.install:
None
/opt/VRTSobc/pal33/install/OBC_RegEntries.uninstall:
None
/opt/VRTSobc/pal33/install/VRTSobc.log:
None
/opt/VRTSobc/pal33/install/cfgsecurity.sh:
None
/opt/VRTSobc/pal33/install/setup_rgd.pl:
None
/opt/VRTSobc/pal33/lib/libcsfinterface3.sl:
None
/opt/VRTSobc/pal33/lib/libcsfsupport3.sl:
None
/opt/VRTSobc/pal33/lib/libdb-4.4.sl:
None
/opt/VRTSobc/pal33/lib/libleafregn.sl:
None
/opt/VRTSobc/pal33/lib/libpal_at.sl:
None
/opt/VRTSobc/pal33/lib/librgd.sl:
None
/opt/VRTSobc/pal33/lib/libvea_cl.sl:
None
/opt/VRTSobc/pal33/lib/libvxACE.sl.3:
VxPSP VERSION: 3.1.1.3 BUILT: Jun 8 2006 19:22:09
/opt/VRTSobc/pal33/lib/libvxPBX.sl:
$Header: NAME: Symantec Private Branch Exchange VE
RSION: v1.3.24.0 Copyright 2005. Symantec
Corporation. All Rights Reserved. $
/opt/VRTSobc/pal33/lib/libvxPBXCommon.sl:
$Header: NAME: Symantec Private Branch Exchange VE
RSION: v1.3.24.0 Copyright 2005. Symantec
Corporation. All Rights Reserved. $
/opt/VRTSobc/pal33/lib/libvxPBXIOP.sl:
$Header: NAME: Symantec Private Branch Exchange VE
RSION: v1.3.24.0 Copyright 2005. Symantec
Corporation. All Rights Reserved. $
/opt/VRTSobc/pal33/lib/libvxPBXVxSS.sl:
$Header: NAME: Symantec Private Branch Exchange VE
RSION: v1.3.24.0 Copyright 2005. Symantec
Corporation. All Rights Reserved. $
$Id: api.c,v 1.23.2.11 2006/10/10 09:16:33 svadapal
Exp $
$Id: rmm_make_path.c,v 1.3.4.7 2006/08/16 21:29:31 j
anand Exp $
/opt/VRTSobc/pal33/lib/libvxTAO.sl.3:
VxPSP VERSION: 3.1.1.3 BUILT: Jun 8 2006 19:22:09
/opt/VRTSobc/pal33/lib/libvxTAO_CustomEndpointSelectors.sl:
VxPSP VERSION: 3.1.1.3 BUILT: Jun 8 2006 19:22:09
/opt/VRTSobc/pal33/lib/libvxTAO_Messaging.sl.3:
VxPSP VERSION: 3.1.0.0 BUILT: Oct 16 2005 13:10:47
/opt/VRTSobc/pal33/lib/libvxVxSSIOP.sl:
$Header: NAME: Symantec Private Branch Exchange VE
RSION: v1.3.24.0 Copyright 2005. Symantec
Corporation. All Rights Reserved. $
/opt/VRTSobc/pal33/lib/libvxcparser.sl:
None
/opt/VRTSobc/pal33/lib/libvxpal3.sl:
None
/opt/VRTSobc/pal33/lib/libvxveautil.sl:
None
/opt/VRTSobc/pal33/msgcats/cli/catalog/en/
climessagecatalog.txt:
None
/opt/VRTSobc/pal33/msgcats/cli/catalog/en/veaconfig.txt:
None
/opt/VRTSobc/pal33/msgcats/system/IsisSkin/java/1033/
SystemMessageCatalog.txt:
None
cksum(1) Output:
VRTSobc33.VRTSOBC33,fr=3.3.722.0,fa=HP-UX_B.11.23_IA/PA,
v=HP:
1229411687 45056 /opt/VRTSobc/pal33/bin/pal_get
3755109015 135168 /opt/VRTSobc/pal33/bin/palclient
3027567833 49152 /opt/VRTSobc/pal33/bin/vea_get
819428581 2170880 /opt/VRTSobc/pal33/bin/veaconfig
3733282033 69632 /opt/VRTSobc/pal33/bin/veainfo
2647701706 425984 /opt/VRTSobc/pal33/bin/vxalerttype
1229717274 53248 /opt/VRTSobc/pal33/bin/vxfinger
4141128817 45056 /opt/VRTSobc/pal33/bin/vxguidgen
4135775694 49152 /opt/VRTSobc/pal33/bin/vxini
3538509143 425984 /opt/VRTSobc/pal33/bin/vxinterface
3978830535 425984 /opt/VRTSobc/pal33/bin/vxobjecttype
1207407486 249856 /opt/VRTSobc/pal33/bin/vxpal
876348438 5335 /opt/VRTSobc/pal33/bin/vxpalctrl
1222182624 106496 /opt/VRTSobc/pal33/bin/vxregctl
3774936343 499712 /opt/VRTSobc/pal33/bin/vxsecaz
504081042 20569 /opt/VRTSobc/pal33/etc/interfaceform.xml
1007525076 8410 /opt/VRTSobc/pal33/install/
OBC_RegEntries.install
2879306932 2000 /opt/VRTSobc/pal33/install/
OBC_RegEntries.uninstall
2608348105 5081 /opt/VRTSobc/pal33/install/VRTSobc.log
2046783740 8661 /opt/VRTSobc/pal33/install/cfgsecurity.sh
1690948862 6385 /opt/VRTSobc/pal33/install/setup_rgd.pl
2231632320 2998272 /opt/VRTSobc/pal33/lib/
libcsfinterface3.sl
3458548350 2719744 /opt/VRTSobc/pal33/lib/libcsfsupport3.sl
525046020 1470464 /opt/VRTSobc/pal33/lib/libdb-4.4.sl
536689592 1388544 /opt/VRTSobc/pal33/lib/libleafregn.sl
2631180967 16384 /opt/VRTSobc/pal33/lib/libpal_at.sl
1665310381 2277376 /opt/VRTSobc/pal33/lib/librgd.sl
3937227600 299008 /opt/VRTSobc/pal33/lib/libvea_cl.sl
510449311 4116480 /opt/VRTSobc/pal33/lib/libvxACE.sl.3
2703571395 81920 /opt/VRTSobc/pal33/lib/libvxPBX.sl
2630493611 57344 /opt/VRTSobc/pal33/lib/libvxPBXCommon.sl
2349061050 1085440 /opt/VRTSobc/pal33/lib/libvxPBXIOP.sl
1984160003 1149536 /opt/VRTSobc/pal33/lib/libvxPBXVxSS.sl
3846966780 6213632 /opt/VRTSobc/pal33/lib/libvxTAO.sl.3
3660862124 184320 /opt/VRTSobc/pal33/lib/
libvxTAO_CustomEndpointSelectors.sl
1647850018 1093632 /opt/VRTSobc/pal33/lib/
libvxTAO_Messaging.sl.3
1350901768 1622016 /opt/VRTSobc/pal33/lib/libvxVxSSIOP.sl
4269730677 1368064 /opt/VRTSobc/pal33/lib/libvxcparser.sl
2500404139 3608576 /opt/VRTSobc/pal33/lib/libvxpal3.sl
4203655105 1849728 /opt/VRTSobc/pal33/lib/libvxveautil.sl
2704239035 45539 /opt/VRTSobc/pal33/msgcats/cli/catalog/en/
climessagecatalog.txt
40401026 66246 /opt/VRTSobc/pal33/msgcats/cli/catalog/en/
veaconfig.txt
92797289 55387 /opt/VRTSobc/pal33/msgcats/system/IsisSkin/
java/1033/SystemMessageCatalog.txt
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 10790 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 PHCO_35213
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_35213.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_35213. 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 PHCO_35213.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHCO_35213.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_35213.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
|
