[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | + OpenVMS Clusters - The best clusters in the world! + |
| Notice: | This conference is COMPANY CONFIDENTIAL. See #1.3 |
| Moderator: | PROXY::MOORE |
|
| Created: | Fri Aug 26 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5320 |
| Total number of notes: | 23384 |
5231.0. "TLZ07 not TMSCP served, V6.2??" by PRSSOS::MAILLARD (Denis MAILLARD) Tue Feb 18 1997 11:35
Does anyone know why in an Alpha V6.2 cluster, a TLZ07 would not be
TMSCP served while TMSCP_LOAD is set to 1 and TMSCP_SERVE_ALL is set to either 1
or 2? The cluster is homogenous both version and architecture wise, composed of
three Alpha nodes (named YFVAX4, YFVAX5 and YFVAX6, the names haven't changed
since the system was migrated to Alpha). Both MSCP and TMSCP modules are loaded
as part of the executive and the local disks are MSCP-served to the other
members without problem. SET DEVICE/SERVED on the TLZ07 has no effect.
Thanks for any hints or idea.
Denis.
Evidences:
YFVAX4:: > sh device/full mk
Magtape YFVAX4$MKA500:, device type TLZ07, is online, record-oriented device,
file-oriented device, error logging is enabled, controller supports
compaction (compaction enabled,).
Error count 37 Operations completed 17965692
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 0 Default buffer size 512
Density unknown Format Normal-11
Volume status: no-unload on dismount, beginning-of-tape, odd parity.
YFVAX4:: > anal/sys
OpenVMS (TM) Alpha System analyzer
SDA> sh device mk
I/O data structures
-------------------
DDB list
--------
Address Controller ACP Driver DPT
-------- ---------- ------ -------------------------- --------
80EFBE00 YFVAX4$MKA MTAACP SYS$MKDRIVER 80CA8400
Controller: YFVAX4$MKA
----------------------
--- Device Data Block (DDB) 80EFBE00 ---
ACP ident MTA Alloc. class 0 DDT address 80CA85A0
SB address 80C23A00
UCB address 80EFC300
--- Primary Channel Request Block (CRB) 80EFC1C0 ---
Reference count 1 Wait queue 80EFC1E0
Bus Array 00000000
IDB address 80EFC240
--- Interrupt Data Block (IDB) 80EFC240 ---
CSR address0 00000000 ADP address 00000000
CSR address1 00000000
Number of units 0
--- Driver Dispatch Table (DDT) 80CA85A0 ---
Errlog buf sz 268 Diag buf sz 0 FDT size 264
Start I/O 80C27300 Register dump 80CA9480 FDT address 80CA8610
Alt start I/O 80C09180 Unit init 80CA9060 Mnt verify 80C37650
Cancel I/O 80CA9410 Cloned UCB 80C09180
YFVAX4$MKA500 TLZ07 UCB address: 80EFC300
Device status: 00000010 online
Characteristics: 0C444021 rec,sqd,fod,avl,elg,idv,odv
01000200 nnm,scsi
Owner UIC [000001,000004] Operation count 17965692 ORB address 80EFC4C0
PID 00000000 Error count 37 DDB address 80EFBE00
Alloc. class 0 Reference count 0 DDT address 80CA85A0
Class/Type 02/3C Retry cnt/max 16/16 CRB address 80EFC1C0
Def. buf. size 512 BOFF 00000000 I/O wait queue 80EFC36C
DEVDEPEND 00010000 Byte count 00000000
DEVDEPND2 00600000 SVAPTE 00000000
DEVDEPND3 00500050 DEVSTS 00000000
FLCK index 3A Object count 0
DLCK address 80EFC280
%SDA-W-NOREAD, unable to access location 42333535
*** PORT I/O queue is empty ***
*** DEVICE I/O queue is empty ***
*** I/O request queue is empty ***
SDA> f 80EFC300
80EFC300 UCB$L_FQFL 80D8A038
UCB$L_MB_MSGQFL
UCB$L_RQFL
UCB$W_MB_SEED
UCB$W_UNIT_SEED
80EFC304 UCB$L_FQBL 80D8A038
UCB$L_MB_MSGQBL
UCB$L_RQBL
80EFC308 UCB$W_SIZE 01C0
80EFC30A UCB$B_TYPE 10
80EFC30B UCB$B_FLCK 3A
80EFC30C UCB$L_ASTQFL 80CA9098 DDT+00AF8
UCB$L_FPC
UCB$L_MB_W_AST
UCB$T_PARTNER
80EFC310 UCB$L_ASTQBL 002482C0
UCB$L_MB_R_AST
UCB$Q_FR3
80EFC314 00000000
80EFC318 UCB$L_FIRST 80EFC240 CRB+00080
UCB$Q_FR4
UCB$W_MSGMAX
UCB$W_MSGCNT
80EFC31C FFFFFFFF
80EFC320 UCB$W_BUFQUO 0000
UCB$W_DSTADDR
80EFC322 UCB$W_INIQUO 0000
UCB$W_SRCADDR
80EFC324 UCB$L_ORB 80EFC4C0 ORB
80EFC328 UCB$L_CPID 00000000
UCB$L_LOCKID
80EFC32C UCB$PS_CRAM 00000000
80EFC330 UCB$L_CRB 80EFC1C0 CRB
80EFC334 UCB$L_DLCK 80EFC280 CRB+000C0
80EFC338 UCB$L_DDB 80EFBE00 DDB
80EFC33C UCB$L_PID 00000000
80EFC340 UCB$L_LINK 00000000
80EFC344 UCB$L_VCB 00000000
80EFC348 UCB$L_DEVCHAR 0C444038
UCB$Q_DEVCHAR
80EFC34C UCB$L_DEVCHAR2 01000200
80EFC350 UCB$L_AFFINITY FFFFFFFF
80EFC354 UCB$L_ALTIOWQ 00000000
UCB$L_XTRA
80EFC358 UCB$B_DEVCLASS 02
80EFC359 UCB$B_DEVTYPE 3C
80EFC35A UCB$W_DEVBUFSIZ 0800
80EFC35C UCB$B_LOCSRV 00
UCB$B_SECTORS
UCB$L_DEVDEPEND
UCB$Q_DEVDEPEND
UCB$R_DEVDEPEND_Q_BLOCK
UCB$R_DISK_DEVDEPEND
UCB$R_NET_DEVDEPEND
UCB$R_TERM_DEVDEPEND
80EFC35D UCB$B_REMSRV 00
UCB$B_TRACKS
80EFC35E UCB$W_BYTESTOGO 0001
UCB$W_CYLINDERS
UCB$B_VERTSZ
80EFC360 UCB$L_DEVDEPND2 00200000
UCB$L_TT_DEVDP1
UCB$W_TU_FORMENU
80EFC364 UCB$L_DEVDEPND3 00500050
UCB$Q_DEVDEPEND2
UCB$R_DEVDEPEND2_Q_BLOCK
UCB$R_TMV_BCNT
UCB$W_TMV_BCNT1
UCB$W_TMV_BCNT2
80EFC368 UCB$L_DEVDEPND4 000E0050
UCB$W_TMV_BCNT3
UCB$W_TMV_BCNT4
80EFC36C UCB$L_IOQFL 80EFC36C UCB+0006C
80EFC370 UCB$L_IOQBL 80EFC36C UCB+0006C
80EFC374 UCB$W_UNIT 01F4
80EFC376 UCB$B_CM1 00
UCB$W_CHARGE
UCB$W_RWAITCNT
80EFC377 UCB$B_CM2 00
80EFC378 UCB$L_IRP 80E75100
80EFC37C UCB$L_REFC 00000000
80EFC380 UCB$B_DIPL 16
UCB$B_STATE
80EFC381 UCB$B_AMOD 03
80EFC382 UCB$W_FILL_0 0000
80EFC384 UCB$L_AMB 00000000
80EFC388 UCB$L_STS 00000010
80EFC38C UCB$L_DEVSTS 00000000
80EFC390 UCB$L_QLEN 00000000
80EFC394 UCB$L_DUETIM 00000000
80EFC398 UCB$L_OPCNT 01122289
80EFC39C UCB$L_SVPN 00000000
80EFC3A0 UCB$L_SVAPTE 00000000
80EFC3A4 UCB$L_BCNT 00000000
80EFC3A8 UCB$L_BOFF 00000000
80EFC3AC UCB$L_SOFTERRCNT 00000000
80EFC3B0 UCB$L_ERTCNT 00000010
80EFC3B4 UCB$L_ERTMAX 00000010
80EFC3B8 UCB$L_ERRCNT 00000025
80EFC3BC UCB$L_PDT 80DD9BC0
80EFC3C0 UCB$L_DDT 80CA85A0 DDT
80EFC3C4 UCB$PS_ADP 00000000
80EFC3C8 UCB$PS_CRCTX 00000000
80EFC3CC UCB$L_MEDIA_ID 6AE8CD07
80EFC3D0 UCB$PS_DTN 00000000
80EFC3D4 UCB$PS_DTN_LINK 00000000
80EFC3D8 UCB$PS_TOUTROUT 00000000
80EFC3DC 00000000
80EFC3E0 UCB$L_EMB 80D89818
80EFC3E4 UCB$L_FUNC 00000000
80EFC3E8 UCB$L_DPC 00000000
80EFC3EC 00000000
80EFC3F0 UCB$L_2P_DDB 00000000
80EFC3F4 UCB$L_2P_LINK 00000000
80EFC3F8 UCB$L_2P_ALTUCB 00000000
80EFC3FC 00000000
80EFC400 UCB$W_DIRSEQ 0000
80EFC402 UCB$B_ONLCNT 00
80EFC403 00
80EFC404 UCB$L_MAXBLOCK 00000000
UCB$L_RECORD
80EFC408 UCB$L_MAXBCNT 0000FFFF
80EFC40C UCB$L_DCCB 00000000
SDA> show exec
VMS Executive layout
---------------------
Image Base End Length SymVec
TMSCP
Nonpaged read only 8019A000 8019FE00 00005E00
Nonpaged read/write 80C68A00 80C69E00 00001400
Linked 4-MAY-1995 22:51 LDRIMG 80DCC240
MSCP
Nonpaged read only 80192000 80198E00 00006E00
Nonpaged read/write 80C66E00 80C68A00 00001C00
Linked 4-MAY-1995 22:45 LDRIMG 80DBBC80
SDA> Exit
YFVAX4:: > sh cluster
View of Cluster from system ID 10251 node: YFVAX4 22-JAN-1997 14:12:50
SYSTEMS MEMBERS
NODE SOFTWARE STATUS
YFVAX4 VMS V6.2 MEMBER
YFVAX5 VMS V6.2 MEMBER
YFVAX6 VMS V6.2 MEMBER
YFVAX4:: > mc sysgen
SYSGEN> SH/CLUSTER
Parameters in use: Active
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
VAXCLUSTER 2 1 0 2 Coded-valu
EXPECTED_VOTES 3 1 1 127 Votes
VOTES 1 1 0 127 Votes
RECNXINTERVAL 10 20 1 32767 Seconds D
DISK_QUORUM " " " " " " "ZZZZ" Ascii
QDSKVOTES 1 1 0 127 Votes
QDSKINTERVAL 1 10 1 32767 Seconds
ALLOCLASS 1 0 0 255 Pure-numbe
LOCKDIRWT 0 0 0 255 Pure-numbe
NISCS_CONV_BOOT 0 0 0 1 Boolean
NISCS_LOAD_PEA0 1 0 0 1 Boolean
NISCS_PORT_SERV 0 0 0 3 Bit-encode
MSCP_LOAD 1 0 0 16384 Coded-valu
TMSCP_LOAD 1 0 0 3 Coded-valu
MSCP_SERVE_ALL 1 0 0 2 Coded-valu
TMSCP_SERVE_ALL 1 0 0 3 Coded-valu
MSCP_BUFFER 128 128 16 -1 Coded-valu
MSCP_CREDITS 8 8 2 128 Coded-valu
TAPE_ALLOCLASS 0 0 0 255 Pure-numbe
NISCS_MAX_PKTSZ 1498 1498 1080 8192 Bytes
NISCS_LAN_OVRHD 18 18 0 256 Bytes
YFVAX4:: > a=f$getsyi("ARCH_NAME")
YFVAX4:: > sh sym a
A = "Alpha"
YFVAX4:: > a=f$getsyi("ARCH_TYPE")
YFVAX4:: > sh sym a
A = 2 Hex = 00000002 Octal = 00000000002
YFVAX4:: > a=f$getsyi("HW_MODEL")
YFVAX4:: > sh sym a
A = 1091 Hex = 00000443 Octal = 00000002103
YFVAX4:: > a=f$getsyi("HW_NAME")
YFVAX4:: > sh sym a
A = "AlphaServer 1000 4/233"
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5231.1 | | PRSSOS::MAILLARD | Denis MAILLARD | Thu Feb 20 1997 07:05 | 23 |
| Re .0: Any Idea?
One more precision: At boot time, the "%MSCPLOAD-I-CONFIGSCAN,
enabled automatic disk serving" message appears on the console, but not
the corresponding "%TMSCPLOAD-I-CONFIGSCAN, enabled automatic tape
serving" message, which tends to indicate that, while the TMSCP
executive module is indeed loaded at boot time (TMSCP_LOAD = 1 and we
can see it under SDA with the SDA> SHOW EXEC command), it is not
enabled, even though TMSCP_SERVE_ALL equals either 1 or 2.
But this %TMSCPLOAD-I-CONFIGSCAN appears on the consoles of the
other members of the cluster at boot time (their TMSCP* parameters have
the same values).
All the members of the cluster had grossly undersized NPAGEDYN
parameters, but setting it to a decent (for this site) value on the
system host to the TLZ07 did not change anything, the tape unit was
still not served after reboot.
I'll soon have a forced dump of the host system, taken just after a
reboot. I hope it'll help me to see what went wrong with enabling the
TMSCP server.
Denis.
|
| 5231.2 | | UTRTSC::thecow.uto.dec.com::JurVanDerBurg | Change mode to Panic! | Thu Feb 20 1997 07:52 | 13 |
| Denis,
Is the configure process dying for some reason? Is there a file
sys$manager:configure_error.log? Any other messages on the console?
Normally it will output the message about serving disks, after which it checks
if both tmscp_load and tmscp_serve_all are non-zero, and if true it calls the
routine scan_all_tape_devices of which the first thing done is to output the
tmscp_load-i-configscan message. This should be easy to check by running
configure with the debugger.
Jur.
|
| 5231.3 | | PRSSOS::MAILLARD | Denis MAILLARD | Fri Feb 21 1997 03:25 | 35 |
| Re .2: Jur, you were dead right, stupid of me not to have thought about
it... And @SYS$STARTUP CONFIGURE solved the problem: the TLZ07 is now
TMSCP served.
What it means is that the CONFIGURE process consistently dies at
boot time somewhere after having configured the MSCP disk and before
issuing the TMSCP CONFIGSCAN message. The question is why? It does not
generate any SYS$MANAGER:CONFIGURE_ERROR.LOG file, but I'll check
whether a .DMP file is generated, as CONFIGURE is started with the
/DUMP qualifier.
It'll not be very easy to troubleshoot as:
1) it is a production system and the customer is loath to make too much
experiments on it,
2) the only way to get connected to the system is through a VERY bad
modem connection after filing for permission with the customer's
management (a tedious process), I only managed to do it once and I
don't even have a functional modem at my disposal right now and,
3) the CONFIGURE process only dies at boot time; when you start it
later, it runs fine (that gives a way to solve the customer's
problem, but does not explain anything), so running it with debugger
will not help us to make any progress as it will not fail, only a
process dump from the startup phase might possibly help.
I'll see if I can get the customer to send me a process dump if
there is any and I'll try to analyse it on my system.
Do you think that it could be related to device firmware
initialisation problems or to SCSI bus reset or initialisation
problems? That's the only reason why I imagine it would fail at boot
time and not later.
Denis.
|
| 5231.4 | | PRSSOS::MAILLARD | Denis MAILLARD | Fri Feb 28 1997 06:27 | 13 |
| The whole thing has now been settled for a few days. I still don't
know why the TMSCP CONFIGSCAN message does not appear along with the
MSCP CONFIGSCAN message, before the starting of the STARTUP process but
I suppose it might be due to the fact that for configuration reasons
the TLZ07 takes too long to answer to the SCSI bus polling, or some
similar reason.
It simply turned out that, due to the fact that OSDS was installed
on the system, SYCONFIG.COM was used and, as STARTUP$AUTOCONFIGURE_ALL
was set to 0 in it, STARTUP simply did not start CONFIGURE. The
solution was to start it manually at the end of SYCONFIG.COM. Then the
TLZ07 is made available to the cluster via TMSCP.
Denis.
|