 |
≫ |
|
|
|
パッチ名: PHCO_35425
パッチ摘要: s700_800 11.23 VRTS 5.0 MP1 VRTSvxfenコマンドパッチ
作成日: 07/01/24
公開日: 07/04/11
ハードウェアプラットフォームおよびOSリリース:
s700: 11.23
s800: 11.23
現象:
PHCO_35425:
1.(SR:8606452624 CR:JAGag09438)
VERITAS不具合番号: 648208
VxFENのシャットダウン時に、次のようなメッセージが
/var/VRTSvcs/log/vxfen.logに記録されます。
/sbin/vxfenadm: illegal option -- g
2.(SR:8606450180 CR:JAGag07271)
VERITAS不具合番号: 701667
VxFENが不正に、記録するメッセージに"VXFEN"ではなく"VCS FEN"というラベ
ルを付けます。
vmunix: VCS FEN ERROR V-11-1-25 Unable to join running
3.(SR:8606466945 CR:JAGag22389)
VERITAS不具合番号: 845783
/dev/vxfendに対するopen()がエラーになっても、vxfendがerrnoを記録しませ
ん。
VERITAS不具合番号: 845904
/dev/vxfenに対するopen()がエラーになっても、vxfenconfigがerrnoを記録し
ません。
4.(SR:8606466902 CR:JAGag22352)
VERITAS不具合番号: 844914
/sbin/vxfen-startupがエラーになるため、Serviceguardがそのノード上でTOC
を実行します。
問題点の説明:
PHCO_35425:
1.(SR:8606452624 CR:JAGag09438)
VERITAS不具合番号: 648208
VxFENのシャットダウン時に、次のようなメッセージが
/var/VRTSvcs/log/vxfen.logに記録されていました。
/sbin/vxfenadm: illegal option -- g
vxfen-shutdownスクリプトは、"vxfenadm -g"の出力を取り込もうとしていま
した。しかし、Serviceguard環境では、これはサポートされません。
解決方法:
Serviceguard環境で実行する場合は、"vxfenadm -g"を呼び出さないように
vxfen-shutdownスクリプトを修正しました。
2.(SR:8606450180 CR:JAGag07271)
VERITAS不具合番号: 701667
VxFENはHP SGとSymantec VCSを両方搭載しているので、これらの製品のいずれ
かに偏ったメッセージを表示してはいけません。
解決方法:
メッセージを次のように変更しました。
vmunix: VXFEN ERROR V-11-1-25 Unable to join running
3.(SR:8606466945 CR:JAGag22389)
VERITAS不具合番号: 845783
open("/dev/vxfend")がエラーになっても、open()によって設定されたerrnoが
記録されませんでした。Cのソース内のメッセージにはエラー番号が含まれて
いましたが、メッセージカタログ内のメッセージは不完全でした。
解決方法:
Cのソースコード内のメッセージを使ってカタログ内のメッセージを更新しま
した。
VERITAS不具合番号: 845904
open("/dev/vxfen")がエラーになっても、open()によって設定されたerrnoが
記録されませんでした。
解決方法:
errnoを記録するようにCのソースを変更し、かつ、メッセージカタログも更新
しました。
4.(SR:8606466902 CR:JAGag22352)
VERITAS不具合番号: 844914
8ノードクラスタ(ノード1、ノード2、... ノード8)のケースで説明します。
ノード6の結合中に、ノード8がクラッシュしたとします。この場合、クラスタ
はfencing中なので、ノード6は結合を中断するよう要求されます。ここで、
ノード7が結合を開始しようとします。ところが、ノード6がポート"b"をメン
バーシップのままにしているため、vxfenはfencingを開始します。そのため、
ノード7は結合を中断するよう要求されます。ここで、ノード7はクラスタから
離脱し、ノード6は、vxfen-startup時の再試行により、結合を続けますが、
クラスタはノード7を締め出し、ノード6の結合を禁止します。
このように、不安定な状態になる可能性がありました。
解決方法:
べき乗バックオフアルゴリズムを使って再試行間隔を求めるようにコードを修
正しました。乱数ジェネレータの初期値としてノードidを指定します。
-----------------------------------------------------------------------------
Patch Name: PHCO_35425
Patch Description: s700_800 11.23 VRTS 5.0 MP1 VRTSvxfen Command Patch
Creation Date: 07/01/24
Post Date: 07/04/11
Hardware Platforms - OS Releases:
s700: 11.23
s800: 11.23
Products:
VRTSvxfen 5.0 MP1
Filesets:
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_IA,v=HP
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.0,fa=HP-UX_B.11.23_IA,v=Symantec
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_PA,v=HP
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.0,fa=HP-UX_B.11.23_PA,v=Symantec
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_35425
Symptoms:
PHCO_35425:
( SR:8606452624 CR:JAGag09438 )
VERITAS Incident Number: 648208
When shutting down VxFEN /var/VRTSvcs/log/vxfen.log shows
the following message
/sbin/vxfenadm: illegal option -- g
( SR:8606450180 CR:JAGag07271 )
VERITAS Incident Number: 701667
VxFEN will label the message it logs with "VCS FEN".
It will be proper to label the messages with "VXFEN"
instead.
vmunix: VCS FEN ERROR V-11-1-25 Unable to join running
( SR:8606466945 CR:JAGag22389 )
VERITAS Incident Number: 845783
vxfend does not log errno if open() fails on /dev/vxfend.
VERITAS Incident Number: 845904
vxfenconfig does not log errno if open() fails on /dev/vxfen
( SR:8606466902 CR:JAGag22352 )
VERITAS Incident Number: 844914
/sbin/vxfen-startup fails and consequently Serviceguard TOCs
the node.
Defect Description:
PHCO_35425:
( SR:8606452624 CR:JAGag09438 )
VERITAS Incident Number: 648208
Problem Description:
When shutting down VxFEN /var/VRTSvcs/log/vxfen.log shows
the following message
/sbin/vxfenadm: illegal option -- g
The vxfen-shutdown script was capturing the output of
vxfenadm -g. This is not supported in a Serviceguard
environment.
Resolution:
Changed the vxfen-shutdown script to not call vxfenadm -g
if running in a Serviceguard environment.
( SR:8606450180 CR:JAGag07271 )
VERITAS Incident Number: 701667
Problem Description:
Since VxFEN ships with both HP SG and Symantec VCS it
should not show biased affinity toward either of the
products.
Resolution:
Reworded messages to VXFEN.
vmunix: VXFEN ERROR V-11-1-25 Unable to join running
( SR:8606466945 CR:JAGag22389 )
VERITAS Incident Number: 845783
Problem Description:
if open("/dev/vxfend") fails,
the errno set by open() is not logged.
The string in C source does log the error number, but the
message in the message catalog is incomplete.
Resolution:
Update message in catalog with message in C source code.
VERITAS Incident Number: 845904
Problem Description:
if open("/dev/vxfen") fails,
the errno set by open() is not logged.
Resolution:
Changed the C source to log errno and updated the message
catalog.
( SR:8606466902 CR:JAGag22352 )
VERITAS Incident Number: 844914
Problem Description:
Consider a 8 node cluster (numbered 1..8)
node 8 crashes and at this same time node 6 is joining.
however since cluster is fencing, node 6 is asked to abort
join. Now node 7 tries to join. However since node 6 is
leaving port 'b' membership, vxfen starts fencing.
Hence node 7 is asked to abort join. node 7 is dropping out
of the cluster now and node 6 is joining because of the
retry in vxfen-startup but now the cluster
is fencing out node 7 and disallows node 6 to join.
Thus stable state is not possible.
Resolution:
The delays between retries are now obtained using
the binary exponential backoff algorithm.
The random number generator is seeded with node id.
Enhancement:
No
SR:
8606452624 8606450180 8606466945 8606466902
Patch Files:
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_IA,v=HP:
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.0,fa=HP-UX_B.11.23_IA,
v=Symantec:
/sbin/vxfen-shutdown
/sbin/vxfend
/sbin/init.d/vxfen
/opt/VRTS/messages/en/vxfen.bmc
/opt/VRTS/messages/en/vxfen.bmcmap
/sbin/vxfenconfig
/sbin/vxfen-startup
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_PA,v=HP:
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.0,fa=HP-UX_B.11.23_PA,
v=Symantec:
/sbin/vxfen-shutdown
/sbin/vxfend
/sbin/init.d/vxfen
/opt/VRTS/messages/en/vxfen.bmc
/opt/VRTS/messages/en/vxfen.bmcmap
/sbin/vxfenconfig
/sbin/vxfen-startup
what(1) Output:
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_IA,v=HP:
/sbin/vxfen-shutdown:
vxfen:$RCSfile: vxfen-shutdown,v $ $Revision: 1.4.4.
1.2.1 $
/sbin/vxfend:
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
/sbin/init.d/vxfen:
vxfen:$RCSfile: vxfen_hp1123,v $ $Revision: 1.14.12.
1 $
/opt/VRTS/messages/en/vxfen.bmc:
None
/opt/VRTS/messages/en/vxfen.bmcmap:
None
/sbin/vxfenconfig:
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
comms:$RCSfile: lltapi.h,v $ $Revision: 4.55 $
comms:$RCSfile: gabioc.h,v $ $Revision: 4.14 $
comms:$RCSfile: gabvers.h,v $ $Revision: 4.4 $
comms:$RCSfile: gaberrno.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_cmd.h,v $ $Revision: 1.11.6.2
$
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
vxfen:$RCSfile: vxfen_lib.h,v $ $Revision: 1.16.34.2
$
vxfen:$RCSfile: vxfenconfig.c,v $ $Revision: 1.86.4.
1.2.1 $
/sbin/vxfen-startup:
vxfen:$RCSfile: vxfen-startup,v $ $Revision: 1.3.12.
1 $
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_PA,v=HP:
/sbin/vxfen-shutdown:
vxfen:$RCSfile: vxfen-shutdown,v $ $Revision: 1.4.4.
1.2.1 $
/sbin/vxfend:
$Revision: 92453-07 linker linker crt0.o B.11.41 040
906 $
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
/sbin/init.d/vxfen:
vxfen:$RCSfile: vxfen_hp1123,v $ $Revision: 1.14.12.
1 $
/opt/VRTS/messages/en/vxfen.bmc:
None
/opt/VRTS/messages/en/vxfen.bmcmap:
None
/sbin/vxfenconfig:
$Revision: 92453-07 linker linker crt0.o B.11.41 040
906 $
vxfen:$RCSfile: vxfen_lib.h,v $ $Revision: 1.16.34.2
$
vxfen:$RCSfile: vxfen_usr_hp.h,v $ $Revision: 2.9 $
vxfen:$RCSfile: vxfen_usr.h,v $ $Revision: 2.53.4.1
$
vxfen:$RCSfile: vxfen_cmd.h,v $ $Revision: 1.11.6.2
$
vxfen:$RCSfile: vxfenconfig.c,v $ $Revision: 1.86.4.
1.2.1 $
comms:$RCSfile: gaberrno.h,v $ $Revision: 4.2 $
comms:$RCSfile: gabvers.h,v $ $Revision: 4.4 $
comms:$RCSfile: gabioc.h,v $ $Revision: 4.14 $
comms:$RCSfile: lltapi.h,v $ $Revision: 4.55 $
vxfen:$RCSfile: vxfen_scsi3_hp.h,v $ $Revision: 2.8
$
comms:$RCSfile: gabhdr.h,v $ $Revision: 4.2 $
/sbin/vxfen-startup:
vxfen:$RCSfile: vxfen-startup,v $ $Revision: 1.3.12.
1 $
cksum(1) Output:
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_IA,v=HP:
976872877 3266 /sbin/vxfen-shutdown
4215232937 400212 /sbin/vxfend
2127500492 9011 /sbin/init.d/vxfen
502396237 22477 /opt/VRTS/messages/en/vxfen.bmc
1479522412 156 /opt/VRTS/messages/en/vxfen.bmcmap
423175671 215956 /sbin/vxfenconfig
195038146 3695 /sbin/vxfen-startup
VRTSvxfen.VRTSVXFEN-RUN,fr=5.0.0.1,fa=HP-UX_B.11.23_PA,v=HP:
976872877 3266 /sbin/vxfen-shutdown
214928309 381304 /sbin/vxfend
2127500492 9011 /sbin/init.d/vxfen
3226758879 22477 /opt/VRTS/messages/en/vxfen.bmc
1479522412 156 /opt/VRTS/messages/en/vxfen.bmcmap
2925148592 261024 /sbin/vxfenconfig
195038146 3695 /sbin/vxfen-startup
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 470 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_35425
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_35425.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_35425. 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_35425.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHCO_35425.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_35425.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
|
