[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:	DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:	Welcome to the Digital UNIX Conference
Moderator:	SMURF::DENHAM

Created:	Thu Mar 16 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	10068
Total number of notes:	35879

8833.0. "bootp over FDDI?" by GRIFUN::BENVI () Fri Feb 14 1997 09:09

Hi all,
	a customer told me that we don't supply bootp services over FDDI lines.
Is it true? I looked bootptab manpage and I found no hardware type (ht) code for FDDI.
However note 4108.1 in this conference stated that support over EISA FDDI would be
added on DUnix 4.0....
Is there a definite answer? I'm looking for PCI FDDI....

Thanks
	Angelo

T.R	Title	User	Personal Name	Date	Lines
8833.1		netrix.lkg.dec.com::thomas	The Code Warrior	`Fri Feb 14 1997 13:54`	4
	FDDI looks like Ethernet as far as bootp is concerned so it does work. You can ris over FDDI and that uses bootp.
8833.2	Some more info	NETRIX::"haley@zk3.dec.com"	Brian Haley	`Fri Feb 14 1997 14:42`	20
	Hi, As Matt said, bootp over fddi works. Just to embellish a little on that, strictly speaking of RIS, the bootp support comes from the console code (except on TurboChannel platforms). As of V4.0, which shipped with the 3.5 firmware cd, there was only _one_ platform that couldn't RIS over fddi - the TurboLaser (V3.0-9 firmware). There was a fix on the next spin, but it didn't make the 3.5 cd. All other platforms worked fine. Since I did most of the RIS adapter qual on V4.0, I can tell you that the majority of problems wasn't with the firmware, we finally got that fixed, but was with improperly configured /etc/bootptab files. Make sure you have both the sm and gw fields correct or you'll spend a lot of time spinning your wheels. -Brian [Posted by WWW Notes gateway]
8833.3	my two cents...	NETRIX::"ftw@zk3.dec.com"	Farrell Woods	`Mon Feb 17 1997 13:45`	20
	I'm not sure what perspective .0 is coming from. bootpd will answer requests that come in over any broadcast-capable network interface. bootpd will serve information to any Ethernet, FDDI or even token ring client. As Matt said the "ht" tag for Ethernet and FDDI are the same... The RIS cases that Brian talks about are a little more specific. I seem to recall though that for the turbochannel machines, the bootp client is part of the console. But that's relevent only if you're booting over the built-in Ethernet interface. TC option cards have their own firmware. I also seem to remember specifically that Jensen/Culzean have some firmware issues. They may not behave if you attempt to install 4.X via RIS and they're not supported as dataless clients. However that shouldn't prevent these and tlasers (etc.) from acting as bootp servers. -- Farrell [Posted by WWW Notes gateway]