info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
VMS startup - building LLA devices
243 views
Skip to first unread message
Marc Van Dyck
Mar 15, 2023, 12:18:37 PM3/15/23
to
Very early in the OpenVMS startup sequence, VMS builds the LLA (Lan
failover) devices. Can someone tell me which file(s) the startup code
gets the information from to do that ?
--
Marc Van Dyck
failover) devices. Can someone tell me which file(s) the startup code
gets the information from to do that ?
--
Marc Van Dyck
Ian Miller
Mar 15, 2023, 1:34:10 PM3/15/23
to
Marc Van Dyck
Mar 17, 2023, 11:03:32 AM3/17/23
to
Ian Miller used his keyboard to write :
That's also what I was thinking. But no. Let me explain.
I have a system disk residing on a SAN that I must be able to boot
from two different hardwares. One is a BL870, the other is an RX2800.
So I built two different LAN$DEVICE_DATABASE.DAT files, one for each
config, and before reboot, we put in place the one that will be in
effect after the reboot. Should work, right ? Well, it doesn't. The
RX2800 has only EIxx devices, the BL870 has EIxx and EWxx ones. If
I'm on the blade, rename files to reboot on the RX, I still see EXxx
devices in the LAN config after the reboot.
Also, in the doc, it is said that this file can be moved to an other
location by defining a logical name. But how can that work when the
LLA formation is done so early in the boot sequence, way before DCL
even exists ?
--
Marc Van Dyck
I have a system disk residing on a SAN that I must be able to boot
from two different hardwares. One is a BL870, the other is an RX2800.
So I built two different LAN$DEVICE_DATABASE.DAT files, one for each
config, and before reboot, we put in place the one that will be in
effect after the reboot. Should work, right ? Well, it doesn't. The
RX2800 has only EIxx devices, the BL870 has EIxx and EWxx ones. If
I'm on the blade, rename files to reboot on the RX, I still see EXxx
devices in the LAN config after the reboot.
Also, in the doc, it is said that this file can be moved to an other
location by defining a logical name. But how can that work when the
LLA formation is done so early in the boot sequence, way before DCL
even exists ?
--
Marc Van Dyck
Ian Miller
Mar 17, 2023, 11:49:39 AM3/17/23
to
Marc Van Dyck
Mar 17, 2023, 12:29:22 PM3/17/23
to
on 17/03/2023, Ian Miller supposed :
I don't think so. As far as I can see, it happens much earlier, way
before SYS$SYSTEM:STARTUP.COM begins execution. I'm not at work today,
so I can't get to my systems, but next monday I will post a console
log showing that.
--
Marc Van Dyck
before SYS$SYSTEM:STARTUP.COM begins execution. I'm not at work today,
so I can't get to my systems, but next monday I will post a console
log showing that.
--
Marc Van Dyck
Volker Halle
Mar 17, 2023, 1:01:41 PM3/17/23
to
Marc,
you remember $ SET WATCH FILE/CLASS=MAJOR ( NOMAJOR to turn it off) ?
If you issue this command before invoking LANCP and change some settings on your LAN devices (i.e. defining a LAN failover set), you'll recognize this:
%XQP, Thread #0, Lookup LAN$DEVICE_DATABASE.SEQ;5 (11513,1,0) Status: 00000001
%XQP, Thread #0, Create/Access LAN$DEVICE_DATABASE.SEQ;6 (9733,1133,0) Status: 00000001
You'll find this file in SYS$SPECIFIC:[SYSEXE]LAN$DEVICE_DATABASE.SEQ
Give it a try and also provide a correct copy of that file before booting next time...
Volker.
you remember $ SET WATCH FILE/CLASS=MAJOR ( NOMAJOR to turn it off) ?
If you issue this command before invoking LANCP and change some settings on your LAN devices (i.e. defining a LAN failover set), you'll recognize this:
%XQP, Thread #0, Lookup LAN$DEVICE_DATABASE.SEQ;5 (11513,1,0) Status: 00000001
%XQP, Thread #0, Create/Access LAN$DEVICE_DATABASE.SEQ;6 (9733,1133,0) Status: 00000001
You'll find this file in SYS$SPECIFIC:[SYSEXE]LAN$DEVICE_DATABASE.SEQ
Give it a try and also provide a correct copy of that file before booting next time...
Volker.
Volker Halle
Mar 17, 2023, 1:11:57 PM3/17/23
to
Marc,
a confirmation (from the sources):
[SYSINI]SYSINIT may have to wait for LANACP - so this the link to your LAN$DEVICE_DATABASE.SEQ file. The LANACP_MAIN code has a path for opening that file using the primitive file system (used early during boot !).
Volker.
a confirmation (from the sources):
[SYSINI]SYSINIT may have to wait for LANACP - so this the link to your LAN$DEVICE_DATABASE.SEQ file. The LANACP_MAIN code has a path for opening that file using the primitive file system (used early during boot !).
Volker.
Marc Van Dyck
Mar 21, 2023, 10:53:08 AM3/21/23
to
Volker Halle pretended :
I confirm that this works. The .SEQ file is updated each time a
permanent LAN database modification is performed, and this file stays
in SYS$SYSTEM even if logicals are used to move the .DAT file somewhere
else, so the system startup knows where to find it.
Thank you Volker.
Marc.
--
Marc Van Dyck
permanent LAN database modification is performed, and this file stays
in SYS$SYSTEM even if logicals are used to move the .DAT file somewhere
else, so the system startup knows where to find it.
Thank you Volker.
Marc.
--
Marc Van Dyck
Marc Van Dyck
Mar 21, 2023, 10:56:42 AM3/21/23
to
Ian Miller pretended :
SYCONFIG and SYLOGICALS are executed :
---------------------------------------------------------------------
10-JAN-2023 11:05:18.01|Booting $1$DGA11591: FGD0.2124-0002-AC01-C11F
10-JAN-2023 11:05:18.81|
10-JAN-2023 11:05:18.81|%VMS_LOADER-I-TRANSFER: Starting VSI OpenVMS...
10-JAN-2023 11:05:19.40|
10-JAN-2023 11:05:19.40|PGQBT-I-INIT-UNIT, IPB, PCI device ID 0x2532, FW 4.04.04
10-JAN-2023 11:05:19.42|PGQBT-I-BUILT, version X-39, built on Mar 9 2021 @ 22:32:18
10-JAN-2023 11:05:19.82|PGQBT-I-LINK_WAIT, waiting for link to come up
10-JAN-2023 11:05:19.82|PGQBT-I-TOPO_WAIT, waiting for topology ID
10-JAN-2023 11:05:25.48|
10-JAN-2023 11:05:25.70|%RAD-I-ENABLED, RAD Support is enabled for 3 RADs
10-JAN-2023 11:05:25.70|
10-JAN-2023 11:05:25.70|
10-JAN-2023 11:05:25.70| VMS Software, Inc. OpenVMS (TM) IA64 Operating System, V8.4-2L3
10-JAN-2023 11:05:25.70| Copyright 2021 VMS Software, Inc.
10-JAN-2023 11:05:25.70|
10-JAN-2023 11:05:28.49|
10-JAN-2023 11:05:28.72|PGQBT-I-INIT-UNIT, boot driver, PCI device ID 0x2532, FW 4.04.04
10-JAN-2023 11:05:28.72|PGQBT-I-BUILT, version X-39, built on Mar 9 2021 @ 22:32:18
10-JAN-2023 11:05:29.13|PGQBT-I-LINK_WAIT, waiting for link to come up
10-JAN-2023 11:05:29.13|PGQBT-I-TOPO_WAIT, waiting for topology ID
10-JAN-2023 11:05:32.55|%DECnet-I-LOADED, network base image loaded, version = 05.84.0D
10-JAN-2023 11:05:40.29|
10-JAN-2023 11:05:40.44#%CNXMAN, Using remote access method for quorum disk
10-JAN-2023 11:05:40.44#%SMP-I-CPUTRN, CPU #2 has joined the active set.
10-JAN-2023 11:05:40.45#%SMP-I-CPUTRN, CPU #10 has joined the active set.
10-JAN-2023 11:05:40.45#%SMP-I-CPUTRN, CPU #3 has joined the active set.
10-JAN-2023 11:05:40.64#%SMP-I-CPUTRN, CPU #11 has joined the active set.
10-JAN-2023 11:05:40.64#%SMP-I-CPUTRN, CPU #14 has joined the active set.
10-JAN-2023 11:05:40.65#%SMP-I-CPUTRN, CPU #7 has joined the active set.
10-JAN-2023 11:05:40.65#%SMP-I-CPUTRN, CPU #15 has joined the active set.
10-JAN-2023 11:05:40.66#%SMP-I-CPUTRN, CPU #6 has joined the active set.
10-JAN-2023 11:05:40.66#%SMP-I-CPUTRN, CPU #9 has joined the active set.
10-JAN-2023 11:05:40.67#%SMP-I-CPUTRN, CPU #1 has joined the active set.
10-JAN-2023 11:05:40.84#%SMP-I-CPUTRN, CPU #8 has joined the active set.
10-JAN-2023 11:05:40.84#%SMP-I-CPUTRN, CPU #13 has joined the active set.
10-JAN-2023 11:05:40.85#%SMP-I-CPUTRN, CPU #5 has joined the active set.
10-JAN-2023 11:05:40.86#%SMP-I-CPUTRN, CPU #4 has joined the active set.
10-JAN-2023 11:05:42.89#%SMP-I-CPUTRN, CPU #12 has joined the active set.
10-JAN-2023 11:05:55.82|%VMScluster-I-LOADSECDB, loading the cluster security database
10-JAN-2023 11:05:57.50#%EWB0, Link up: 10 gbit, full duplex, flow control disabled
10-JAN-2023 11:05:57.92#%EWC0, Link up: 10 gbit, full duplex, flow control disabled
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN failset device created
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN failover device unavailable, EIB0 00-25-b3-b4-be-f9
10-JAN-2023 11:05:58.30#%LLA0, Logical LAN failover device added to failset, EIB0 00-25-b3-b4-be-f9
10-JAN-2023 11:05:58.30|%LLA0, Logical LAN failover device unavailable, EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:05:58.30#%LLA0, Logical LAN failover device added to failset, EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:05:58.31|%LLA0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.31#%LLA0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:58.32|%LLB0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.32|%LLB0, Logical LAN failset device created
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.50#%LLB0, Logical LAN failover device added to failset, EWB0 b4-99-ba-64-81-ae
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN failset device connected to EWB0 b4-99-ba-64-81-ae
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN failset device assigned MAC address 00-00-00-00-00-00
10-JAN-2023 11:05:58.51|%LLC0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN failset device created
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN failover device unavailable, EIC0 00-25-b3-b4-be-fa
10-JAN-2023 11:05:58.70#%LLC0, Logical LAN failover device added to failset, EIC0 00-25-b3-b4-be-fa
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.70#%LLC0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN failset device created
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN failover device unavailable, EWA0 b4-99-ba-64-81-aa
10-JAN-2023 11:05:58.90#%LLD0, Logical LAN failover device added to failset, EWA0 b4-99-ba-64-81-aa
10-JAN-2023 11:05:58.91|%LLD0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.10#%LLD0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN failset device created
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN failover device unavailable, EID0 00-25-b3-b4-be-fb
10-JAN-2023 11:05:59.15#%LLE0, Logical LAN failover device added to failset, EID0 00-25-b3-b4-be-fb
10-JAN-2023 11:05:59.16|%LLE0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.31#%LLE0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:59.31#%EWD0, Link up: 10 gbit, full duplex, flow control disabled
10-JAN-2023 11:05:59.31|%LLA0, Logical LAN event at 10-JAN-2023 11:05:58.04
10-JAN-2023 11:05:59.32#%LLA0, Logical LAN failover device available, EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:05:59.32|%LLA0, Logical LAN event at 10-JAN-2023 11:05:58.04
10-JAN-2023 11:05:59.32|%LLA0, Logical LAN failset device connected to EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:06:00.91|%LLA0, Logical LAN failset device assigned MAC address aa-00-00-b4-be-f9
10-JAN-2023 11:06:01.11#%EIA0, Link up: 1000 mbit, full duplex, flow control (receive only)
10-JAN-2023 11:06:01.12#%EIB0, Link up: 1000 mbit, full duplex, flow control (receive only)
10-JAN-2023 11:06:01.12|%LLA0, Logical LAN event at 10-JAN-2023 11:06:00.02
10-JAN-2023 11:06:04.09#%LLA0, Logical LAN failover device available, EIB0 00-25-b3-b4-be-f9
10-JAN-2023 11:06:04.34|%SYSINIT-I- found a valid OpenVMS Cluster quorum disk
10-JAN-2023 11:06:04.65|%SYSINIT-I- waiting to form or join an OpenVMS Cluster
10-JAN-2023 11:06:04.74#%CNXMAN, Using local access method for quorum disk
10-JAN-2023 11:06:04.76#%CNXMAN, Sending VMScluster membership request to system SAXO
10-JAN-2023 11:06:04.94#%CNXMAN, Established "connection" to quorum disk
10-JAN-2023 11:06:07.95#%CNXMAN, Now a VMScluster member -- system SLOW
10-JAN-2023 11:06:09.58|%STDRV-I-STARTUP, OpenVMS startup begun at 10-JAN-2023 11:06:07.03
10-JAN-2023 11:06:09.82|****************************[ 10-JAN-2023 11:06:08 ]****************************
10-JAN-2023 11:06:09.82|<RUN> : SYS$COMMON:[SYSMGR]SYLOGICALS.COM;58 *
10-JAN-2023 11:06:09.82|--------------------------------------------------------------------------------
10-JAN-2023 11:06:09.82|
10-JAN-2023 11:06:09.82|****************************[ 10-JAN-2023 11:06:08 ]****************************
10-JAN-2023 11:06:09.82|<RUN> : ITSE$ROOT:[PROCEDURES]SITE_IDENTIFICATION.COM;42 *
10-JAN-2023 11:06:10.02|--------------------------------------------------------------------------------
10-JAN-2023 11:06:10.02|
10-JAN-2023 11:06:10.02|10/01/23 11:06 -I- Boot SLOW (SGH425K7EN) - USER4 = 0 -
10-JAN-2023 11:06:10.02|
10-JAN-2023 11:06:10.02|10/01/23 11:06 -I- SLOW boot on AG site in STD mode -
10-JAN-2023 11:06:10.02|
10-JAN-2023 11:06:10.22|10/01/23 11:06 -I- SLOW USER4 parameter set back to 0 (Default) -
10-JAN-2023 11:06:10.22|
10-JAN-2023 11:06:10.22|--------------------------------------------------------------------------------
10-JAN-2023 11:06:10.22|<END> : ITSE$ROOT:[PROCEDURES]SITE_IDENTIFICATION.COM;42 *
10-JAN-2023 11:06:10.22|****************************[ 10-JAN-2023 11:06:09 ]****************************
10-JAN-2023 11:06:10.22|
10-JAN-2023 11:06:10.43|10/01/23 11:06 -I- Mounting SYSDISK2 and Quorum Disk -
10-JAN-2023 11:06:10.43|10-JAN-2023 11:06:09 -W- WRONG NOMENCLATURE - SYSDISK2 - $1$DGA11592: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:10.43|10-JAN-2023 11:06:09 -W- WRONG NOMENCLATURE - SYSDISK2 - $1$DGA12592: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:10.63|10-JAN-2023 11:06:09 -W- WRONG NOMENCLATURE - SYSDISK2 - $1$DGA13592: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:10.63|10-JAN-2023 11:06:09 -I- MOUNT TO PERFORM - SYSDISK2 - DSA2 - MEMBERS=> - $1$DGA11592: $1$DGA
10-JAN-2023 11:06:12.92|10-JAN-2023 11:06:09 -I- PROCESSOR=UNIQUE - SYSDISK2 - DSA2 - OPTIONS - INDIVIDUAL CACHEs ##
10-JAN-2023 11:06:13.04|10-JAN-2023 11:06:12 -S- MOUNT PERFORMED - SYSDISK2 - DSA2 - SUCCESS - SUCCESSFULY MOUNTED
10-JAN-2023 11:06:13.24|************************************************************************************************************
10-JAN-2023 11:06:13.24|10-JAN-2023 11:06:12 -W- WRONG NOMENCLATURE - QRMDISK1 - $1$DGA11590: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:13.49|10-JAN-2023 11:06:12 -I- MOUNT TO PERFORM - QRMDISK1 - $1$DGA11590 - MEMBERS=> - $1$DGA11590:
10-JAN-2023 11:06:13.49|10-JAN-2023 11:06:12 -S- MOUNT PERFORMED - QRMDISK1 - $1$DGA11590 - SUCCESS - SUCCESSFULY MOUNTED
10-JAN-2023 11:06:13.49|************************************************************************************************************
10-JAN-2023 11:06:13.49|
10-JAN-2023 11:06:13.69|10/01/23 11:06 -I- Defining Banksys Wide Logicals -
10-JAN-2023 11:06:13.69|
10-JAN-2023 11:06:13.69|****************************[ 10-JAN-2023 11:06:12 ]****************************
10-JAN-2023 11:06:13.69|<RUN> : ITSE$ROOT:[PROCEDURES]LOGICALS.COM;40 *
10-JAN-2023 11:06:13.89|--------------------------------------------------------------------------------
10-JAN-2023 11:06:13.89|
10-JAN-2023 11:06:13.89|10/01/23 11:06 -I- Defining Cluster Wide Logicals -
10-JAN-2023 11:06:13.89|
10-JAN-2023 11:06:13.89|10/01/23 11:06 -I- Defining SLOW Specific Logicals -
10-JAN-2023 11:06:13.89|
10-JAN-2023 11:06:13.89|--------------------------------------------------------------------------------
10-JAN-2023 11:06:13.89|<END> : ITSE$ROOT:[PROCEDURES]LOGICALS.COM;40 *
10-JAN-2023 11:06:13.89|****************************[ 10-JAN-2023 11:06:12 ]****************************
10-JAN-2023 11:06:14.09|--------------------------------------------------------------------------------
10-JAN-2023 11:06:14.09|<END> : SYS$COMMON:[SYSMGR]SYLOGICALS.COM;58 *
10-JAN-2023 11:06:14.09|****************************[ 10-JAN-2023 11:06:12 ]****************************
10-JAN-2023 11:06:14.09|
10-JAN-2023 11:06:14.09|****************************[ 10-JAN-2023 11:06:13 ]****************************
10-JAN-2023 11:06:14.29|<RUN> : SYS$COMMON:[SYSMGR]SYPAGSWPFILES.COM;2 *
10-JAN-2023 11:06:14.29|--------------------------------------------------------------------------------
10-JAN-2023 11:06:14.29|
10-JAN-2023 11:06:14.29|10/01/23 11:06 -I- Using OpenVMS Standard Page and Swap files -
10-JAN-2023 11:06:14.29|
10-JAN-2023 11:06:14.29|--------------------------------------------------------------------------------
10-JAN-2023 11:06:14.30|<END> : SYS$COMMON:[SYSMGR]SYPAGSWPFILES.COM;2 *
10-JAN-2023 11:06:14.50|****************************[ 10-JAN-2023 11:06:13 ]****************************
10-JAN-2023 11:06:14.50|%RUN-S-PROC_ID, identification of created process is 21000414
10-JAN-2023 11:06:14.50|%RUN-S-PROC_ID, identification of created process is 21000415
10-JAN-2023 11:06:14.70|%RUN-S-PROC_ID, identification of created process is 21000416
10-JAN-2023 11:06:14.70|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.64 %%%%%%%%%%%
10-JAN-2023 11:06:14.70|Operator _SLOW$OPA0: has been enabled, username SYSTEM
10-JAN-2023 11:06:14.70|
10-JAN-2023 11:06:14.70|%SET-I-NEWAUDSRV, identification of new audit server process is 2100041C
10-JAN-2023 11:06:14.90|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.64 %%%%%%%%%%%
10-JAN-2023 11:06:14.90|Operator status for operator _SLOW$OPA0:
10-JAN-2023 11:06:14.90|CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
10-JAN-2023 11:06:14.90|LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
10-JAN-2023 11:06:14.90|OPER11, OPER12
10-JAN-2023 11:06:14.90|
10-JAN-2023 11:06:14.90|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.10|Logfile has been initialized by operator _SLOW$OPA0:
10-JAN-2023 11:06:15.10|Logfile is SLOW::SYSDISK2:[SLOW]OPERATOR.LOG;1717
10-JAN-2023 11:06:15.10|
10-JAN-2023 11:06:15.10|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.10|Operator status for operator SLOW::SYSDISK2:[SLOW]OPERATOR.LOG;1717
10-JAN-2023 11:06:15.10|CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
10-JAN-2023 11:06:15.10|LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
10-JAN-2023 11:06:15.10|OPER11, OPER12
10-JAN-2023 11:06:15.10|
10-JAN-2023 11:06:15.30|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.30|11:05:46.76 Node SLOW (csid 00000000) is using remote access method for quorum disk
10-JAN-2023 11:06:15.30|
10-JAN-2023 11:06:15.30|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.30|11:06:03.77 Node SLOW (csid 00000000) is using local access method for quorum disk
10-JAN-2023 11:06:15.30|
10-JAN-2023 11:06:15.30|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|11:06:03.77 Node SLOW (csid 00000000) re-established "connection" to quorum disk
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.51|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|11:06:03.77 Node SLOW (csid 00010008) is now a VMScluster member
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.51|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|Operator _SAXO$FTA1: has been enabled, username SYSTEM
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.51|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.66 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|Operator _SAXO$OPA0: has been enabled, username SYSTEM
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.70|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.92 %%%%%%%%%%%
10-JAN-2023 11:06:15.70|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:15.71|%SECSRV-I-CIAEXISTCLU, security server using existing cluster intrusion database
10-JAN-2023 11:06:15.71|
10-JAN-2023 11:06:15.71|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.93 %%%%%%%%%%%
10-JAN-2023 11:06:15.71|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:15.90|%ACME-I-SERVERSTART, ACME_SERVER starting
10-JAN-2023 11:06:15.90|
10-JAN-2023 11:06:16.10|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.93 %%%%%%%%%%%
10-JAN-2023 11:06:16.10|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:16.10|%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up
10-JAN-2023 11:06:16.10|
10-JAN-2023 11:06:16.10|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.93 %%%%%%%%%%%
10-JAN-2023 11:06:16.11|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:16.11|%SECSRV-I-SERVERSTARTINGU, security server starting up
10-JAN-2023 11:06:16.11|
10-JAN-2023 11:06:16.11|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.94 %%%%%%%%%%%
10-JAN-2023 11:06:16.11|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:16.11|%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up
10-JAN-2023 11:06:23.47|
10-JAN-2023 11:06:23.60|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:22.52 %%%%%%%%%%%
10-JAN-2023 11:06:23.60|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:23.60|TDF-I-SETTDF TDF set new timezone differential
10-JAN-2023 11:06:23.60|
10-JAN-2023 11:06:23.60|Copyright 2015 VMS Software, Inc.
10-JAN-2023 11:06:23.60|%NET$STARTUP-I-IGNOREDECNET, logical NET$IGNORE_DECNET set - exiting procedure
10-JAN-2023 11:06:23.80|%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is BOOT
10-JAN-2023 11:06:24.00|%STARTUP-I-AUDITCONTINUE, audit server initialization complete
10-JAN-2023 11:06:24.00|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:22.85 %%%%%%%%%%%
10-JAN-2023 11:06:24.00|Message from user AUDIT$SERVER on SLOW
10-JAN-2023 11:06:24.00|Security alarm (SECURITY) and security audit (SECURITY) on SLOW, system id: 2133
10-JAN-2023 11:06:24.00|Auditable event: Audit server starting up
10-JAN-2023 11:06:24.20|Event time: 10-JAN-2023 11:06:22.84
10-JAN-2023 11:06:24.20|PID: 21000405
10-JAN-2023 11:06:24.20|Username: SYSTEM
10-JAN-2023 11:06:24.20|
10-JAN-2023 11:06:24.20|
10-JAN-2023 11:06:24.20|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:24.40|<RUN> : SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;4 *
10-JAN-2023 11:06:24.40|--------------------------------------------------------------------------------
10-JAN-2023 11:06:24.40#%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
10-JAN-2023 11:06:24.61|%DCL-I-TABNOTFND, previous table ITSE$RESULTS was not found - new table created
10-JAN-2023 11:06:24.61|
10-JAN-2023 11:06:24.61|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:24.61|<RUN> : ITSE$ROOT:[PROCEDURES]EXECUTE.COM;12 *
10-JAN-2023 11:06:24.80|--------------------------------------------------------------------------------
10-JAN-2023 11:06:24.80|
10-JAN-2023 11:06:24.80|10/01/23 11:06 -I- START - MOUNTDISK - Mount Disk - TimeOut: 55 min -
10-JAN-2023 11:06:24.80|
10-JAN-2023 11:06:24.80|--------------------------------------------------------------------------------
10-JAN-2023 11:06:24.81|<END> : ITSE$ROOT:[PROCEDURES]EXECUTE.COM;12 *
10-JAN-2023 11:06:24.81|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:24.81|
10-JAN-2023 11:06:25.00|10/01/23 11:06 -I- STARTUP_SLOW - Batch suite submitted -
10-JAN-2023 11:06:25.00|
10-JAN-2023 11:06:25.00|--------------------------------------------------------------------------------
10-JAN-2023 11:06:25.01|<END> : SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;4 *
10-JAN-2023 11:06:25.05|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:25.20#%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
10-JAN-2023 11:06:25.21|%RUN-S-PROC_ID, identification of created process is 21000429
10-JAN-2023 11:06:25.21|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:24.17 %%%%%%%%%%%
10-JAN-2023 11:06:25.21|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:25.40|%SMHANDLER-S-STARTUP, server management event handler startup
10-JAN-2023 11:06:25.40|
10-JAN-2023 11:06:25.40| SYSTEM job terminated at 10-JAN-2023 11:06:24.19
10-JAN-2023 11:06:25.40|
10-JAN-2023 11:06:25.40| Accounting information:
10-JAN-2023 11:06:25.40| Buffered I/O count: 4681 Peak working set size: 14992
10-JAN-2023 11:06:25.41| Direct I/O count: 5725 Peak virtual size: 299952
10-JAN-2023 11:06:25.41| Page faults: 6842 Mounted volumes: 2
10-JAN-2023 11:06:30.92| Charged CPU time: 0 00:00:01.51 Elapsed time: 0 00:00:17.29
--
Marc Van Dyck
>
> A quick bit of research shows LANACP started from VMS$DEVICE_STARTUP after
> SYCONFIG and SYLOGICALS.COM have been executed. As far as I know LANACP is
> the process that reads the LAN$DEVICE_DATABASE and creates the LL devices.
Here is a startup log showing that LLA devices are built way before
> A quick bit of research shows LANACP started from VMS$DEVICE_STARTUP after
> SYCONFIG and SYLOGICALS.COM have been executed. As far as I know LANACP is
> the process that reads the LAN$DEVICE_DATABASE and creates the LL devices.
SYCONFIG and SYLOGICALS are executed :
---------------------------------------------------------------------
10-JAN-2023 11:05:18.01|Booting $1$DGA11591: FGD0.2124-0002-AC01-C11F
10-JAN-2023 11:05:18.81|
10-JAN-2023 11:05:18.81|%VMS_LOADER-I-TRANSFER: Starting VSI OpenVMS...
10-JAN-2023 11:05:19.40|
10-JAN-2023 11:05:19.40|PGQBT-I-INIT-UNIT, IPB, PCI device ID 0x2532, FW 4.04.04
10-JAN-2023 11:05:19.42|PGQBT-I-BUILT, version X-39, built on Mar 9 2021 @ 22:32:18
10-JAN-2023 11:05:19.82|PGQBT-I-LINK_WAIT, waiting for link to come up
10-JAN-2023 11:05:19.82|PGQBT-I-TOPO_WAIT, waiting for topology ID
10-JAN-2023 11:05:25.48|
10-JAN-2023 11:05:25.70|%RAD-I-ENABLED, RAD Support is enabled for 3 RADs
10-JAN-2023 11:05:25.70|
10-JAN-2023 11:05:25.70|
10-JAN-2023 11:05:25.70| VMS Software, Inc. OpenVMS (TM) IA64 Operating System, V8.4-2L3
10-JAN-2023 11:05:25.70| Copyright 2021 VMS Software, Inc.
10-JAN-2023 11:05:25.70|
10-JAN-2023 11:05:28.49|
10-JAN-2023 11:05:28.72|PGQBT-I-INIT-UNIT, boot driver, PCI device ID 0x2532, FW 4.04.04
10-JAN-2023 11:05:28.72|PGQBT-I-BUILT, version X-39, built on Mar 9 2021 @ 22:32:18
10-JAN-2023 11:05:29.13|PGQBT-I-LINK_WAIT, waiting for link to come up
10-JAN-2023 11:05:29.13|PGQBT-I-TOPO_WAIT, waiting for topology ID
10-JAN-2023 11:05:32.55|%DECnet-I-LOADED, network base image loaded, version = 05.84.0D
10-JAN-2023 11:05:40.29|
10-JAN-2023 11:05:40.44#%CNXMAN, Using remote access method for quorum disk
10-JAN-2023 11:05:40.44#%SMP-I-CPUTRN, CPU #2 has joined the active set.
10-JAN-2023 11:05:40.45#%SMP-I-CPUTRN, CPU #10 has joined the active set.
10-JAN-2023 11:05:40.45#%SMP-I-CPUTRN, CPU #3 has joined the active set.
10-JAN-2023 11:05:40.64#%SMP-I-CPUTRN, CPU #11 has joined the active set.
10-JAN-2023 11:05:40.64#%SMP-I-CPUTRN, CPU #14 has joined the active set.
10-JAN-2023 11:05:40.65#%SMP-I-CPUTRN, CPU #7 has joined the active set.
10-JAN-2023 11:05:40.65#%SMP-I-CPUTRN, CPU #15 has joined the active set.
10-JAN-2023 11:05:40.66#%SMP-I-CPUTRN, CPU #6 has joined the active set.
10-JAN-2023 11:05:40.66#%SMP-I-CPUTRN, CPU #9 has joined the active set.
10-JAN-2023 11:05:40.67#%SMP-I-CPUTRN, CPU #1 has joined the active set.
10-JAN-2023 11:05:40.84#%SMP-I-CPUTRN, CPU #8 has joined the active set.
10-JAN-2023 11:05:40.84#%SMP-I-CPUTRN, CPU #13 has joined the active set.
10-JAN-2023 11:05:40.85#%SMP-I-CPUTRN, CPU #5 has joined the active set.
10-JAN-2023 11:05:40.86#%SMP-I-CPUTRN, CPU #4 has joined the active set.
10-JAN-2023 11:05:42.89#%SMP-I-CPUTRN, CPU #12 has joined the active set.
10-JAN-2023 11:05:55.82|%VMScluster-I-LOADSECDB, loading the cluster security database
10-JAN-2023 11:05:57.50#%EWB0, Link up: 10 gbit, full duplex, flow control disabled
10-JAN-2023 11:05:57.92#%EWC0, Link up: 10 gbit, full duplex, flow control disabled
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN failset device created
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.09|%LLA0, Logical LAN failover device unavailable, EIB0 00-25-b3-b4-be-f9
10-JAN-2023 11:05:58.30#%LLA0, Logical LAN failover device added to failset, EIB0 00-25-b3-b4-be-f9
10-JAN-2023 11:05:58.30|%LLA0, Logical LAN failover device unavailable, EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:05:58.30#%LLA0, Logical LAN failover device added to failset, EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:05:58.31|%LLA0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.31#%LLA0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:58.32|%LLB0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.32|%LLB0, Logical LAN failset device created
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.50#%LLB0, Logical LAN failover device added to failset, EWB0 b4-99-ba-64-81-ae
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN failset device connected to EWB0 b4-99-ba-64-81-ae
10-JAN-2023 11:05:58.50|%LLB0, Logical LAN failset device assigned MAC address 00-00-00-00-00-00
10-JAN-2023 11:05:58.51|%LLC0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN failset device created
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN failover device unavailable, EIC0 00-25-b3-b4-be-fa
10-JAN-2023 11:05:58.70#%LLC0, Logical LAN failover device added to failset, EIC0 00-25-b3-b4-be-fa
10-JAN-2023 11:05:58.70|%LLC0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.70#%LLC0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN failset device created
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:58.90|%LLD0, Logical LAN failover device unavailable, EWA0 b4-99-ba-64-81-aa
10-JAN-2023 11:05:58.90#%LLD0, Logical LAN failover device added to failset, EWA0 b4-99-ba-64-81-aa
10-JAN-2023 11:05:58.91|%LLD0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.10#%LLD0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN failset device created
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.10|%LLE0, Logical LAN failover device unavailable, EID0 00-25-b3-b4-be-fb
10-JAN-2023 11:05:59.15#%LLE0, Logical LAN failover device added to failset, EID0 00-25-b3-b4-be-fb
10-JAN-2023 11:05:59.16|%LLE0, Logical LAN event at 10-JAN-2023 11:05:57.04
10-JAN-2023 11:05:59.31#%LLE0, Logical LAN failover devices all unavailable
10-JAN-2023 11:05:59.31#%EWD0, Link up: 10 gbit, full duplex, flow control disabled
10-JAN-2023 11:05:59.31|%LLA0, Logical LAN event at 10-JAN-2023 11:05:58.04
10-JAN-2023 11:05:59.32#%LLA0, Logical LAN failover device available, EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:05:59.32|%LLA0, Logical LAN event at 10-JAN-2023 11:05:58.04
10-JAN-2023 11:05:59.32|%LLA0, Logical LAN failset device connected to EWD0 b4-99-ba-64-81-b6
10-JAN-2023 11:06:00.91|%LLA0, Logical LAN failset device assigned MAC address aa-00-00-b4-be-f9
10-JAN-2023 11:06:01.11#%EIA0, Link up: 1000 mbit, full duplex, flow control (receive only)
10-JAN-2023 11:06:01.12#%EIB0, Link up: 1000 mbit, full duplex, flow control (receive only)
10-JAN-2023 11:06:01.12|%LLA0, Logical LAN event at 10-JAN-2023 11:06:00.02
10-JAN-2023 11:06:04.09#%LLA0, Logical LAN failover device available, EIB0 00-25-b3-b4-be-f9
10-JAN-2023 11:06:04.34|%SYSINIT-I- found a valid OpenVMS Cluster quorum disk
10-JAN-2023 11:06:04.65|%SYSINIT-I- waiting to form or join an OpenVMS Cluster
10-JAN-2023 11:06:04.74#%CNXMAN, Using local access method for quorum disk
10-JAN-2023 11:06:04.76#%CNXMAN, Sending VMScluster membership request to system SAXO
10-JAN-2023 11:06:04.94#%CNXMAN, Established "connection" to quorum disk
10-JAN-2023 11:06:07.95#%CNXMAN, Now a VMScluster member -- system SLOW
10-JAN-2023 11:06:09.58|%STDRV-I-STARTUP, OpenVMS startup begun at 10-JAN-2023 11:06:07.03
10-JAN-2023 11:06:09.82|****************************[ 10-JAN-2023 11:06:08 ]****************************
10-JAN-2023 11:06:09.82|<RUN> : SYS$COMMON:[SYSMGR]SYLOGICALS.COM;58 *
10-JAN-2023 11:06:09.82|--------------------------------------------------------------------------------
10-JAN-2023 11:06:09.82|
10-JAN-2023 11:06:09.82|****************************[ 10-JAN-2023 11:06:08 ]****************************
10-JAN-2023 11:06:09.82|<RUN> : ITSE$ROOT:[PROCEDURES]SITE_IDENTIFICATION.COM;42 *
10-JAN-2023 11:06:10.02|--------------------------------------------------------------------------------
10-JAN-2023 11:06:10.02|
10-JAN-2023 11:06:10.02|10/01/23 11:06 -I- Boot SLOW (SGH425K7EN) - USER4 = 0 -
10-JAN-2023 11:06:10.02|
10-JAN-2023 11:06:10.02|10/01/23 11:06 -I- SLOW boot on AG site in STD mode -
10-JAN-2023 11:06:10.02|
10-JAN-2023 11:06:10.22|10/01/23 11:06 -I- SLOW USER4 parameter set back to 0 (Default) -
10-JAN-2023 11:06:10.22|
10-JAN-2023 11:06:10.22|--------------------------------------------------------------------------------
10-JAN-2023 11:06:10.22|<END> : ITSE$ROOT:[PROCEDURES]SITE_IDENTIFICATION.COM;42 *
10-JAN-2023 11:06:10.22|****************************[ 10-JAN-2023 11:06:09 ]****************************
10-JAN-2023 11:06:10.22|
10-JAN-2023 11:06:10.43|10/01/23 11:06 -I- Mounting SYSDISK2 and Quorum Disk -
10-JAN-2023 11:06:10.43|10-JAN-2023 11:06:09 -W- WRONG NOMENCLATURE - SYSDISK2 - $1$DGA11592: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:10.43|10-JAN-2023 11:06:09 -W- WRONG NOMENCLATURE - SYSDISK2 - $1$DGA12592: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:10.63|10-JAN-2023 11:06:09 -W- WRONG NOMENCLATURE - SYSDISK2 - $1$DGA13592: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:10.63|10-JAN-2023 11:06:09 -I- MOUNT TO PERFORM - SYSDISK2 - DSA2 - MEMBERS=> - $1$DGA11592: $1$DGA
10-JAN-2023 11:06:12.92|10-JAN-2023 11:06:09 -I- PROCESSOR=UNIQUE - SYSDISK2 - DSA2 - OPTIONS - INDIVIDUAL CACHEs ##
10-JAN-2023 11:06:13.04|10-JAN-2023 11:06:12 -S- MOUNT PERFORMED - SYSDISK2 - DSA2 - SUCCESS - SUCCESSFULY MOUNTED
10-JAN-2023 11:06:13.24|************************************************************************************************************
10-JAN-2023 11:06:13.24|10-JAN-2023 11:06:12 -W- WRONG NOMENCLATURE - QRMDISK1 - $1$DGA11590: - FORCE ON - ALLOWED TO PROCEED
10-JAN-2023 11:06:13.49|10-JAN-2023 11:06:12 -I- MOUNT TO PERFORM - QRMDISK1 - $1$DGA11590 - MEMBERS=> - $1$DGA11590:
10-JAN-2023 11:06:13.49|10-JAN-2023 11:06:12 -S- MOUNT PERFORMED - QRMDISK1 - $1$DGA11590 - SUCCESS - SUCCESSFULY MOUNTED
10-JAN-2023 11:06:13.49|************************************************************************************************************
10-JAN-2023 11:06:13.49|
10-JAN-2023 11:06:13.69|10/01/23 11:06 -I- Defining Banksys Wide Logicals -
10-JAN-2023 11:06:13.69|
10-JAN-2023 11:06:13.69|****************************[ 10-JAN-2023 11:06:12 ]****************************
10-JAN-2023 11:06:13.69|<RUN> : ITSE$ROOT:[PROCEDURES]LOGICALS.COM;40 *
10-JAN-2023 11:06:13.89|--------------------------------------------------------------------------------
10-JAN-2023 11:06:13.89|
10-JAN-2023 11:06:13.89|10/01/23 11:06 -I- Defining Cluster Wide Logicals -
10-JAN-2023 11:06:13.89|
10-JAN-2023 11:06:13.89|10/01/23 11:06 -I- Defining SLOW Specific Logicals -
10-JAN-2023 11:06:13.89|
10-JAN-2023 11:06:13.89|--------------------------------------------------------------------------------
10-JAN-2023 11:06:13.89|<END> : ITSE$ROOT:[PROCEDURES]LOGICALS.COM;40 *
10-JAN-2023 11:06:13.89|****************************[ 10-JAN-2023 11:06:12 ]****************************
10-JAN-2023 11:06:14.09|--------------------------------------------------------------------------------
10-JAN-2023 11:06:14.09|<END> : SYS$COMMON:[SYSMGR]SYLOGICALS.COM;58 *
10-JAN-2023 11:06:14.09|****************************[ 10-JAN-2023 11:06:12 ]****************************
10-JAN-2023 11:06:14.09|
10-JAN-2023 11:06:14.09|****************************[ 10-JAN-2023 11:06:13 ]****************************
10-JAN-2023 11:06:14.29|<RUN> : SYS$COMMON:[SYSMGR]SYPAGSWPFILES.COM;2 *
10-JAN-2023 11:06:14.29|--------------------------------------------------------------------------------
10-JAN-2023 11:06:14.29|
10-JAN-2023 11:06:14.29|10/01/23 11:06 -I- Using OpenVMS Standard Page and Swap files -
10-JAN-2023 11:06:14.29|
10-JAN-2023 11:06:14.29|--------------------------------------------------------------------------------
10-JAN-2023 11:06:14.30|<END> : SYS$COMMON:[SYSMGR]SYPAGSWPFILES.COM;2 *
10-JAN-2023 11:06:14.50|****************************[ 10-JAN-2023 11:06:13 ]****************************
10-JAN-2023 11:06:14.50|%RUN-S-PROC_ID, identification of created process is 21000414
10-JAN-2023 11:06:14.50|%RUN-S-PROC_ID, identification of created process is 21000415
10-JAN-2023 11:06:14.70|%RUN-S-PROC_ID, identification of created process is 21000416
10-JAN-2023 11:06:14.70|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.64 %%%%%%%%%%%
10-JAN-2023 11:06:14.70|Operator _SLOW$OPA0: has been enabled, username SYSTEM
10-JAN-2023 11:06:14.70|
10-JAN-2023 11:06:14.70|%SET-I-NEWAUDSRV, identification of new audit server process is 2100041C
10-JAN-2023 11:06:14.90|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.64 %%%%%%%%%%%
10-JAN-2023 11:06:14.90|Operator status for operator _SLOW$OPA0:
10-JAN-2023 11:06:14.90|CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
10-JAN-2023 11:06:14.90|LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
10-JAN-2023 11:06:14.90|OPER11, OPER12
10-JAN-2023 11:06:14.90|
10-JAN-2023 11:06:14.90|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.10|Logfile has been initialized by operator _SLOW$OPA0:
10-JAN-2023 11:06:15.10|Logfile is SLOW::SYSDISK2:[SLOW]OPERATOR.LOG;1717
10-JAN-2023 11:06:15.10|
10-JAN-2023 11:06:15.10|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.10|Operator status for operator SLOW::SYSDISK2:[SLOW]OPERATOR.LOG;1717
10-JAN-2023 11:06:15.10|CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
10-JAN-2023 11:06:15.10|LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
10-JAN-2023 11:06:15.10|OPER11, OPER12
10-JAN-2023 11:06:15.10|
10-JAN-2023 11:06:15.30|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.30|11:05:46.76 Node SLOW (csid 00000000) is using remote access method for quorum disk
10-JAN-2023 11:06:15.30|
10-JAN-2023 11:06:15.30|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.30|11:06:03.77 Node SLOW (csid 00000000) is using local access method for quorum disk
10-JAN-2023 11:06:15.30|
10-JAN-2023 11:06:15.30|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|11:06:03.77 Node SLOW (csid 00000000) re-established "connection" to quorum disk
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.51|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|11:06:03.77 Node SLOW (csid 00010008) is now a VMScluster member
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.51|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.65 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|Operator _SAXO$FTA1: has been enabled, username SYSTEM
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.51|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.66 %%%%%%%%%%%
10-JAN-2023 11:06:15.51|Operator _SAXO$OPA0: has been enabled, username SYSTEM
10-JAN-2023 11:06:15.51|
10-JAN-2023 11:06:15.70|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.92 %%%%%%%%%%%
10-JAN-2023 11:06:15.70|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:15.71|%SECSRV-I-CIAEXISTCLU, security server using existing cluster intrusion database
10-JAN-2023 11:06:15.71|
10-JAN-2023 11:06:15.71|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.93 %%%%%%%%%%%
10-JAN-2023 11:06:15.71|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:15.90|%ACME-I-SERVERSTART, ACME_SERVER starting
10-JAN-2023 11:06:15.90|
10-JAN-2023 11:06:16.10|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.93 %%%%%%%%%%%
10-JAN-2023 11:06:16.10|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:16.10|%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up
10-JAN-2023 11:06:16.10|
10-JAN-2023 11:06:16.10|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.93 %%%%%%%%%%%
10-JAN-2023 11:06:16.11|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:16.11|%SECSRV-I-SERVERSTARTINGU, security server starting up
10-JAN-2023 11:06:16.11|
10-JAN-2023 11:06:16.11|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:13.94 %%%%%%%%%%%
10-JAN-2023 11:06:16.11|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:16.11|%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up
10-JAN-2023 11:06:23.47|
10-JAN-2023 11:06:23.60|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:22.52 %%%%%%%%%%%
10-JAN-2023 11:06:23.60|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:23.60|TDF-I-SETTDF TDF set new timezone differential
10-JAN-2023 11:06:23.60|
10-JAN-2023 11:06:23.60|Copyright 2015 VMS Software, Inc.
10-JAN-2023 11:06:23.60|%NET$STARTUP-I-IGNOREDECNET, logical NET$IGNORE_DECNET set - exiting procedure
10-JAN-2023 11:06:23.80|%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is BOOT
10-JAN-2023 11:06:24.00|%STARTUP-I-AUDITCONTINUE, audit server initialization complete
10-JAN-2023 11:06:24.00|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:22.85 %%%%%%%%%%%
10-JAN-2023 11:06:24.00|Message from user AUDIT$SERVER on SLOW
10-JAN-2023 11:06:24.00|Security alarm (SECURITY) and security audit (SECURITY) on SLOW, system id: 2133
10-JAN-2023 11:06:24.00|Auditable event: Audit server starting up
10-JAN-2023 11:06:24.20|Event time: 10-JAN-2023 11:06:22.84
10-JAN-2023 11:06:24.20|PID: 21000405
10-JAN-2023 11:06:24.20|Username: SYSTEM
10-JAN-2023 11:06:24.20|
10-JAN-2023 11:06:24.20|
10-JAN-2023 11:06:24.20|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:24.40|<RUN> : SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;4 *
10-JAN-2023 11:06:24.40|--------------------------------------------------------------------------------
10-JAN-2023 11:06:24.40#%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
10-JAN-2023 11:06:24.61|%DCL-I-TABNOTFND, previous table ITSE$RESULTS was not found - new table created
10-JAN-2023 11:06:24.61|
10-JAN-2023 11:06:24.61|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:24.61|<RUN> : ITSE$ROOT:[PROCEDURES]EXECUTE.COM;12 *
10-JAN-2023 11:06:24.80|--------------------------------------------------------------------------------
10-JAN-2023 11:06:24.80|
10-JAN-2023 11:06:24.80|10/01/23 11:06 -I- START - MOUNTDISK - Mount Disk - TimeOut: 55 min -
10-JAN-2023 11:06:24.80|
10-JAN-2023 11:06:24.80|--------------------------------------------------------------------------------
10-JAN-2023 11:06:24.81|<END> : ITSE$ROOT:[PROCEDURES]EXECUTE.COM;12 *
10-JAN-2023 11:06:24.81|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:24.81|
10-JAN-2023 11:06:25.00|10/01/23 11:06 -I- STARTUP_SLOW - Batch suite submitted -
10-JAN-2023 11:06:25.00|
10-JAN-2023 11:06:25.00|--------------------------------------------------------------------------------
10-JAN-2023 11:06:25.01|<END> : SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;4 *
10-JAN-2023 11:06:25.05|****************************[ 10-JAN-2023 11:06:23 ]****************************
10-JAN-2023 11:06:25.20#%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
10-JAN-2023 11:06:25.21|%RUN-S-PROC_ID, identification of created process is 21000429
10-JAN-2023 11:06:25.21|%%%%%%%%%%% OPCOM 10-JAN-2023 11:06:24.17 %%%%%%%%%%%
10-JAN-2023 11:06:25.21|Message from user SYSTEM on SLOW
10-JAN-2023 11:06:25.40|%SMHANDLER-S-STARTUP, server management event handler startup
10-JAN-2023 11:06:25.40|
10-JAN-2023 11:06:25.40| SYSTEM job terminated at 10-JAN-2023 11:06:24.19
10-JAN-2023 11:06:25.40|
10-JAN-2023 11:06:25.40| Accounting information:
10-JAN-2023 11:06:25.40| Buffered I/O count: 4681 Peak working set size: 14992
10-JAN-2023 11:06:25.41| Direct I/O count: 5725 Peak virtual size: 299952
10-JAN-2023 11:06:25.41| Page faults: 6842 Mounted volumes: 2
10-JAN-2023 11:06:30.92| Charged CPU time: 0 00:00:01.51 Elapsed time: 0 00:00:17.29
--
Marc Van Dyck
fossey...@gmail.com
Mar 21, 2023, 1:34:49 PM3/21/23
to
Hi Marc Van Dyck,
It is LANACP that is run to create the LLx device along with VLx device early in boot
LANACP is both a server process started up by VMS$DEVICE_STARTUP.COM and
and image loaded during early boot to perform the network device creation and build.
I've had a conversation with Dick Stockdale about this a while ago.
The reason the LAN$DEVICE_DATABASE.SEQ had to be created in because when LANACP first runs early in boot there is no ability to process RMS indexed files.
Interestingly on X86 in system disk they have split the LANACP image into LANACP.exe and LANACP_BFS.exe and it is the latter along with the .SEQ file that reside on the Memory Disk with LANACP.exe and the.DAT file on the main system disk.
Cheers, Laurence
It is LANACP that is run to create the LLx device along with VLx device early in boot
LANACP is both a server process started up by VMS$DEVICE_STARTUP.COM and
and image loaded during early boot to perform the network device creation and build.
I've had a conversation with Dick Stockdale about this a while ago.
The reason the LAN$DEVICE_DATABASE.SEQ had to be created in because when LANACP first runs early in boot there is no ability to process RMS indexed files.
Interestingly on X86 in system disk they have split the LANACP image into LANACP.exe and LANACP_BFS.exe and it is the latter along with the .SEQ file that reside on the Memory Disk with LANACP.exe and the.DAT file on the main system disk.
Cheers, Laurence
Carl Friedberg
Mar 21, 2023, 10:20:09 PM3/21/23
to comp.os.vms to email gateway
At a former client, we were using LAN failover. We had a series of
minor problems, and decided LAN failover configuration caused more
problems than it solved. We had one failure in the years we were using
that configuration, and it did work. However, it was too complicated;
which outweighed potential benefits. At a convenient time, we removed
the LAN failover, and had just one connection from the Itanic servers
to the network switch (we were using two independent network switches,
but they were in fact Cisco linked, so there was a single point of
failure. I don't believe the single EWA0 config ever caused a problem,
and it was much simpler. This was in a 3 node Itanium cluster.
Carl Friedberg
> _______________________________________________
> Info-vax mailing list
> Info...@rbnsn.com
> http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com
--
www.comets.com
minor problems, and decided LAN failover configuration caused more
problems than it solved. We had one failure in the years we were using
that configuration, and it did work. However, it was too complicated;
which outweighed potential benefits. At a convenient time, we removed
the LAN failover, and had just one connection from the Itanic servers
to the network switch (we were using two independent network switches,
but they were in fact Cisco linked, so there was a single point of
failure. I don't believe the single EWA0 config ever caused a problem,
and it was much simpler. This was in a 3 node Itanium cluster.
Carl Friedberg
> Info-vax mailing list
> Info...@rbnsn.com
> http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com
--
www.comets.com
0 new messages