Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!ucbvax!vax1.physics.oxford.ac.UK!MACALLSTR From: MACALLSTR@vax1.physics.oxford.ac.UK Newsgroups: comp.os.vms Subject: Ethernet LAT-Decserver-200 query : how is mnemonic/address info obtained? Message-ID: <8706221510.AA13608@ucbvax.Berkeley.EDU> Date: Mon, 22-Jun-87 11:12:16 EDT Article-I.D.: ucbvax.8706221510.AA13608 Posted: Mon Jun 22 11:12:16 1987 Date-Received: Tue, 23-Jun-87 04:26:41 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 43 Where does a LAT terminal server obtain its menmonic/address information for services on the Ethernet other than those situated locally on the terminal server? The Decserver-200 documentation appears only to have commands for defining local services. When a user issues a CONNECT command, where does the T.S. software look for the menomonic to Ethernet address translation? A few possibilities spring to mind. (1) Information is down-line loaded from the load host node when the terminal server is initialised. (2) Each LAT host node sends the information out to all known terminal servers when that node reboots. (4) Information is sent out a regular intervals. (5) The CONNECT command sends a request to the load host and picks up the information from there. The terminal server would cease to function or have to be reloaded if the load host stopped for any reason. (6) If (5), does all terminal server traffic continue through the load host ( surely not ?! ) or as a normal Ethernet broadcast to the particular service? The terminal server would cease to function or have to be reloaded if the load host stopped for any reason. (7) The terminal server monitors all Ethernet traffic and somehow picks up the addresses of live Ethernet nodes AND the node/service mnemonics. Doing this would be a significant overhead if EVERY packet has to be monitored. Perhaps there is some Ethernet LAT documentation which describes this? Enquiries to DEC Software Support suggest that (7) might be the answer. I don't yet have a terminal server to determine, empirically, what the mechanism might be. Does anyone have accurate information on this question? John