Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!cernvax!hslrswi!francis From: francis@hslrswi.UUCP (Francis Demierre) Newsgroups: comp.sys.ibm.pc.rt Subject: Re: Connecting IBM PC RT to Ethernet Keywords: Ethernet TCP/IP Message-ID: <934@hslrswi.UUCP> Date: 5 May 89 14:16:41 GMT References: <1667@ucqais.uc.edu> Reply-To: francis@hslrswi.UUCP (Francis Demierre) Organization: ASCOM Hasler AG, CH-3000 Berne 14, Switzerland Lines: 138 In article <1667@ucqais.uc.edu> rainwatr@ucqais.uc.edu (Donald J. Rainwater) writes: >I have an IBM PC RT running AIX 2.2.1 that I would like to connect to our >Ethernet network. I've run an Ethernet transceiver drop cable (2 10 meter >sections) to a port on a DELNI, and the RT TCP/IP configuration files >have been properly set up (as far as I can tell). There are VAXen on the >Ethernet that run SRI Multinet (TCP/IP), and one of them is set up as my >domain name server. > >When the RT is started, it tries to configure the ethernet device (net0). >After a period of time, I get a console message saying that net0 has timed >out, and that the device has been removed from the configuration. > >Has anyone done what I'm attempting? Any information would be greatly >appreciated. Thanks in advance. >-- >Don Rainwater, University of Cincinnati Computer Center >rainwatr@ucbeh.san.uc.edu >rainwatr@ucbeh.bitnet >rainwatr@ucqais.uc.edu - check the switches on you Ethernet card to determine the interrupt level and the memory address to which it is configured. The values shown below in the 'devices' output are working for me and 'il1 9' is a safe interrupt level (it is not to be used exclusively by any devices as far as I know). You could try these values. I cannot remember now where the switch positions are described, it is probably in the 'Hardware reference Manual' or in one of the Red books - Check that the interrupt level selected dos not conflict with another of your adapters that want to uses the same level exclusively. Required interrupt level are described somewhere under heading "Conflicting Adapter interrupt level". I am sorry to be so vague, but I'm writing this from home and do not have any RT books at hand :-). - I got some problems when I tried to set the 'inetlen' and 'r_inetlen' to a small value (timed out). I recommend to used the values shown below in the '/etc/net' file. - In the version 2.2.1 of the 'devices' command, it was not possible to set the 'il1' value to '9'. You have to manually edit the '/etc/ddi/enet' file to set the interrupt value to 9 and to allow interrupt level 9 (see below). Then run the devices to set your 'net0' parameters. ------------------------------------------------------------------------------ This is the description of the adapter 'net0' as shown with the 'devices' command: Current Possible Name Description Choice Choices rsa Bus ROM Start Address 98000 80000 - f8000 rea Bus ROM End Address 99fff 81fff - f9fff brsa Bus RAM Start Address 9a000 82000 - fa000 brea Bus RAM End Address 9ffff 87fff - fffff [ ... some text deleted ... ] noi Num. of Interupt Levels Used 1 1 il1 Intrpt Level # of 1st Intrpt 9 3,4,5,7,9 si1 1st Interupt Level is Shared false true,false [ ... some text deleted ... ] nidl Net ID Length 2 1 - 255 nidd Net ID Displacement 12 0 - 255 srbt SLIH Ring Buffer Threshold 10 0 - 255 [ ... some text deleted ... ] ------------------------------------------------------------------------------ This is the content of the '/etc/ddi/enet' file (used to check arguments given in the 'devices' command as well as to fix the default values) : default: [ ... some text deleted ... ] il1 = 9 <------------------------------------