Question on Utrix CI config
Andrew W. Potter
awpsys at ultb.isc.rit.edu
Fri Dec 15 09:13:39 AEST 1989
Here is a strange one:
I am asking the question here because our configuration is an unsupported
configuration consisting of an Ultrix VAX 6000-410 and a number of VAX 8XXX
running VMS sharing the same CI.
Recently we upgraded our Ultrix system to a 6000 series system from a 11/785
The 11/785 ran Ultrix V3 in our mixed CI environment just fine for over
a year. The 6000 system runs fine with the following exception.
What I get is a lot of error log entries in the Ultrix errorlog
reporting an established and broken down connection. The connection
data is alwaus the text "A TMK Special". I have enclosed an extract of
our errorlog at the end of this text.
The ultrix system shares the CI only to have shared access to the
HSC based tape drives. The Ultrix disks are running off a KDB50
(although when we ran the 785, we ran the ultrix disks off the HSC.
The only cavaet that we have found here is to be extra careful to
keep ultrix and VMS away from each others disks. I have discussed this
extensively in the past.)
My question is: Is there any way to stop this message from
continously filling my ultrix error log? What is a "TMK Special"?
I am including in this message output from the VMS "Show cluster" command.
output from "uerf" and a copy of my Ultrix Config file. The only
way I can prevent the errorlogger "elsd" from filling my /var partion
is to softlink the file /var/adm/syserr/syserr.ultb to /dev/null.
esld does not use too much CPU doing this logging so it has worked, but
is not the way I want to have to run this system.
Any suggestions anyone has would be most appreciated.
- Andrew Potter
- Rochester Institute of Technology
- Awpsys at ultb.isc.rit.edu
- Awpsys at ritvax.BITNET
********** Output from a VMS "show cluster" command (Node Ultb is ultrix)
View of Cluster from system ID 1027 node: VAXC 14-DEC-1989 15:26:30
SYSTEMS MEMBERS CIRCUITS
NODE HW_TYPE SOFTWARE STATUS LPORT RP RP_TYP REM_STA
VAXC VAX 8800 VMS V5.1 MEMBER PAA0 10 CIBCA- ENAB
SNEEZY HS70 HSC V394 PAA0 0 HSC70 M_ENAB
ULTB 6200 ? PAA0 2 CIBCA- ENAB
VAXD VAX 8550 VMS V5.1 MEMBER PAA0 8 CIBCI ENAB
VAXN VAX 8350 VMS V5.1 MEMBER PAA0 9 CIBCA- ENAB
VAXB VAX 8700 VMS V5.1 MEMBER PAA0 6 CIBCI ENAB
GRUMPY HS70 HSC V394 PAA0 1 HSC70 M_ENAB
HAPPY HS70 HSC V394 PAA0 7 HSC70 M_ENAB
VAXA VAX 8650 VMS V5.1 MEMBER PAA0 5 CI780 ENAB
********** Output from "uerf" on the ultrix node.
SCS ERROR CODE SYSAP TERMINATED CONNECTION
x01000002
SEVERITY : WARNING
LOCAL SYSAP NAME SCS$DIRECTORY
LOCAL CONN DATA A TMK Special
LOCAL CONN ID x0472000B
LOCAL STATION ID x000000000405
CONN STATE x0006
********************************* ENTRY 90. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 202. SCS EVENTS
SEQUENCE NUMBER 2985.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Thu Dec 14 15:08:39 1989 EST
OCCURRED ON SYSTEM ultb
SYSTEM ID x0B000004 MICROCODE REV = 4.
SYSTYPE REG. x02100101
FIRMWARE REV = 16.
PROCESSOR TYPE KA63A
----- UNIT INFORMATION -----
UNIT TYPE CIBCA-BA
CONTROLLER NO. 0.
----- COMMON INFO -----
SCS ERROR CODE SYSAP ESTABLISHED NEW CONECTION
x01000002
SEVERITY : WARNING
LOCAL SYSAP NAME SCS$DIRECTORY
LOCAL CONN DATA A TMK Special
LOCAL CONN ID x0470000B
LOCAL STATION ID x000000000405
CONN STATE x0006
************ Config file for this Ultrix system "ultb"
************ System is actually a VAX 6000-410, but it won't make
************ under V3.1b unless you say it is a 6200.
ident "ULTB"
machine vax
cpu "VAX6200"
maxusers 64
processors 1
maxuprc 50
physmem 32
timezone 5 dst 1
options LAT
options QUOTA
options INET
options EMULFLT
options NFS
options RPC
options DLI
options BSC
options UFS
options DECNET
options DLI
config vmunix root on ra2a swap on ra2b and ra3b and ra4b dumps on ra2b
adapter vaxbi13 at nexus ?
adapter vaxbi14 at nexus ?
adapter ci0 at nexus ?
adapter xmi0 at nexus ?
controller hsc0 at ci0 cinode 0
tape tms1 at hsc0 drive 1
tape tms11 at hsc0 drive 11
tape tms13 at hsc0 drive 13
controller hsc1 at ci0 cinode 1
tape tms0 at hsc1 drive 0
tape tms10 at hsc1 drive 10
tape tms12 at hsc1 drive 12
controller hsc7 at ci0 cinode 7
controller aie0 at vaxbi13 node6
controller aie1 at vaxbi14 node6
controller bvpssp3 at aie1 vector bvpsspintr
tape tms6 at bvpssp3 drive 6
controller kdb0 at vaxbi14 node4
controller uq4 at kdb0 vector uqintr
disk ra2 at uq4 drive 2
disk ra3 at uq4 drive 3
disk ra4 at uq4 drive 4
device bvpni0 at aie0 vector bvpniintr
device dmb0 at vaxbi13 node3 flags 0xff vector dmbsint dmbaint dmblint
device dmb1 at vaxbi14 node2 flags 0xff vector dmbsint dmbaint dmblint
device dmb2 at vaxbi14 node3 flags 0xff vector dmbsint dmbaint dmblint
scs_sysid 1029
pseudo-device pty
pseudo-device loop
pseudo-device inet
pseudo-device ether
pseudo-device lat
pseudo-device lta
pseudo-device rpc
pseudo-device nfs
pseudo-device dli
pseudo-device bsc
pseudo-device ufs
pseudo-device decnet
pseudo-device scsnet
--
Andrew W. Potter Bitnet: awpsys at ritvax.BITNET
Systems Programmer Internet: awpsys at ultb.isc.rit.edu
Information Systems and Computing
Rochester Institute of Technology, Rochester NY, 14623 (716) 475-6994
More information about the Comp.unix.ultrix
mailing list