[HECnet] VAXcluster MOP boot losing link?

[Mark Benson]

When I boot my 3-machine SimH VAXcluster, my MOP booted VAX system I
am seeing this:


%VAXcluster, system loaded from node DARMOK (AA-00-04-00-33-18)

%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
    OpenVMS (TM) VAX Version V7.3         Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
%SYSINIT, waiting to form or join a VMScluster system
%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE DARMOK

%CNXMAN,   sending VAXcluster membership request to system PIVAX2
%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE DARMOK

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE DARMOK

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE DARMOK

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE DARMOK

%PEA0, Port has Closed Virtual Circuit - REMOTE NODE DARMOK

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE PIVAX2

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE PIVAX2

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE PIVAX2

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE PIVAX2

%CNXMAN,   lost connection to system DARMOK
%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE PIVAX2

%CNXMAN,   sending VAXcluster membership request to system PIVAX2
%CNXMAN,   now a VAXcluster member -- system PIVAX3
%CNXMAN,   re-established connection to system DARMOK

Is this;


%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE DARMOK

%PEA0, Excessive packet losses on LAN Path from XQA to XQA on REMOTE NODE DARMOK


normal? It seems to happen at boot in the same place in the sequence.
I wonder if it's the OS bootstrap reconfiguring the XQA0: interface?

I don't know, though, just looked odd.

-- 

Mark