[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

847.0. "CLUIVP error on two scsibusses" by HLFS00::SLAG_J () Mon Jun 02 1997 11:51

    Hello'
    
    I've been working on a NT Cluster with 2 ALPHA's 1000A, 2 common
    scsibusses (KZPSA) and 2 Raidarrays 310 (HSZ2.7Z). Running Windows 
    NT 4.0 and Digital clustering 1.1, using the HSZDISK driver 3.2.
    The failover is working fine. but the CLUSTER IVP give's an error.
    Is this a know problem ?
    The Administrator's guide for DIGITAL Clusters for Windows NT tells
    in the apendix A that the CLUIVP is an unsupported utility.
    Or do whe have a problem because wha have 2 scsibusses ?
    
    See the out put form thoe FMxxx.log files's.
    
    First whe started to run the CLUIVP on the BDC and then on the PDC.
    
    Jos SLag MCS-HHO
    
Logfile from the PDC node.
    
Digital Clusters for Windows NT(TM) 1.1-1222 Release (Build 1222)
Digital Equipment Corporation
Windows NT(TM) is a trademark of Microsoft Corporation.
Cluster Failover Manager Trace File
Opened on cluster ctadldn node CTABDC-DELDEN at 5/29/97 4:23:35 PM
by program C:\PROGRA~1\Digital\Cluster\cluivp.exe

05/29/1997 16:23:35.835 tid=182 trace started
16:23:43.632 tid=182 The Cluster Failover Manager Service is being stopped.
    File: E:\CluBuild\src\fm\cluivp\iofunc.c    Line: 1495
16:24:13.843 tid=182 The Installation Verification Program is starting.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 414
16:24:13.914 tid=182 The RPC test was successful.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 446
16:24:14.078 tid=182 The CIS test will be run for 5 iterations.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 435
16:24:37.382 tid=182 The CIS test was successful.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 446
16:24:41.679 tid=182 The CFMD test was successful.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 446
16:24:41.835 tid=182 The Disk test will be run for 5 iterations.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 435
16:24:42.125 tid=182 The Initiator Id test was successful.
    File: E:\CluBuild\src\fm\cluivp\disktest.c    Line: 735
16:24:42.250 tid=133 Driver processing partition table for \\.\PhysicalDrive0
16:24:42.250 tid=134 Driver processing partition table for \\.\PhysicalDrive1
16:24:42.554 tid=133 Driver processing partition table for \\.\PhysicalDrive0
16:24:42.570 tid=134 Driver processing partition table for \\.\PhysicalDrive1
16:24:42.828 tid=133 Driver processing partition table for \\.\PhysicalDrive0
16:24:42.960 tid=134 Driver processing partition table for \\.\PhysicalDrive1
16:24:43.140 tid=133 Driver processing partition table for \\.\PhysicalDrive0
16:24:43.281 tid=134 Driver processing partition table for \\.\PhysicalDrive1
16:24:43.578 tid=133 Driver processing partition table for \\.\PhysicalDrive0
16:24:43.859 tid=134 Driver processing partition table for \\.\PhysicalDrive1
16:24:44.156 tid=182 The Reservation test was successful.
    File: E:\CluBuild\src\fm\cluivp\disktest.c    Line: 789
16:24:52.312 tid=182 Unit attention/Bus Reset event was not delivered.
Analysis:
Device I/O error.
Scsi conformance.
Bus reset failed on peer.
Disk or adapter not reporting unit attention.
Driver problem.
    File: E:\CluBuild\src\fm\cluivp\iofunc.c    Line: 1147
16:24:52.500 tid=182 Disk \\.\PhysicalDrive0 did not pass the test;
SCSI id: (0, 0, 1, 0), Adapter: \\.\Scsi0: (deckzpsx).
    File: E:\CluBuild\src\fm\cluivp\disktest.c    Line: 1422
16:24:52.656 tid=182 Failure was reached at iteration 1.
    File: E:\CluBuild\src\fm\cluivp\disktest.c    Line: 1480
16:24:52.781 tid=182 The Unit Attention test was not successful.
    File: E:\CluBuild\src\fm\cluivp\disktest.c    Line: 814
16:24:52.960 tid=182 The Disk test was not successful.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 442
16:24:53.078 tid=182 The IVP did not finish successfully.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 375
16:26:55.742 tid=182 trace stopped

    Logfile from the BDC.
    
Digital Clusters for Windows NT(TM) 1.1-1222 Release (Build 1222)
Digital Equipment Corporation
Windows NT(TM) is a trademark of Microsoft Corporation.
Cluster Failover Manager Trace File
Opened on cluster ctadldn node CTAPDC-DELDEN at 5/29/97 4:22:37 PM
by program C:\PROGRA~1\Digital\Cluster\cluivp.exe

05/29/1997 16:22:37.234 tid=186 trace started
16:22:39.062 tid=186 The Cluster Failover Manager Service is being stopped.
    File: E:\CluBuild\src\fm\cluivp\iofunc.c    Line: 1495
16:23:09.273 tid=186 The IVP is now waiting for the IVP program
to be started on the other cluster node.
    File: E:\CluBuild\src\fm\cluivp\cluivp.c    Line: 353
16:24:22.742 tid=93  Driver processing partition table for \\.\PhysicalDrive0
16:24:22.835 tid=93  Driver processing partition table for \\.\PhysicalDrive1
16:24:23.101 tid=143 Driver processing partition table for \\.\PhysicalDrive0
16:24:23.234 tid=143 Driver processing partition table for \\.\PhysicalDrive1
16:24:23.390 tid=143 Driver processing partition table for \\.\PhysicalDrive0
16:24:23.531 tid=143 Driver processing partition table for \\.\PhysicalDrive1
16:24:23.671 tid=143 Driver processing partition table for \\.\PhysicalDrive0
16:24:23.820 tid=93  Driver processing partition table for \\.\PhysicalDrive1
16:24:24.132 tid=165 Driver processing partition table for \\.\PhysicalDrive0
16:24:24.312 tid=143 Driver processing partition table for \\.\PhysicalDrive1
16:26:28.976 tid=186 trace stopped

    
T.RTitleUserPersonal
Name
DateLines
847.1MSE1::PCOTEpress one now for personal nameMon Jun 02 1997 12:447

>    scsibusses (KZPSA) and 2 Raidarrays 310 (HSZ2.7Z). Running Windows 

   it's a known problem with hsof v2.7. Upgraded to the minimum
   revision of 3.0z-2 or to the latest revision of hsof 3.1.