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

Conference 7.286::fddi

Title:	FDDI - The Next Generation

Moderator:	NETCAD::STEFANI

Created:	Thu Apr 27 1989
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2259
Total number of notes:	8590

1115.0. "Does the DEFTA Support Remote Boot Over FDDI...?" by CSC32::CSC32::BLACKMER (Ralph Blackmer CSC/CS/IISG Netsupport) Wed Oct 13 1993 18:30

I have a Call logged into the CSC requesting the "BOOT COMMAND" to boot his
3000-500 over FDDI.

His DEFTA is in the Turbochanel Slot 3. Does it require connection to the SCSI
for some reason?  OR  More likely,..can we boot the system via "BOOTP"?

He is attempting this from the console prompt but a SHO DEVICE does not yield
information about the FDDI controller installed in the Turbo Slot.

Also, what would the boot command be on the 3000-500 system to request a
downline load of the operating system across FDDI?

Ralph Blackmer
CSC Colorado
IISG Network Support

T.R	Title	User	Personal Name	Date	Lines
1115.1		NETRIX::thomas	The Code Warrior	`Wed Oct 13 1993 19:29`	2
	boot "3/ez0" for TC slot 3 using BOOTP boot "3/esa0" for TC slot 3 using MOP
1115.2	Thanks for the response	GUCCI::DMCCLOUD	Dennis McCloud - Eastern Client/Server Consultant	`Wed Oct 13 1993 20:15`	7
	Thanks for the answer. I'm the originator of the call to the CSC. We'll give it a try first thing tomorrow on the customer's network. We tried every possible combination of boot commands and just didn't happen to hit the magic combination of numbers, slashes, and Z's. Dennis
1115.3	BOOTP Boot Fails over FDDI	GUCCI::DMCCLOUD	Dennis McCloud - Eastern Client/Server Consultant	`Thu Oct 14 1993 14:41`	131
	The boot "3/ez0" worked - almost. It gets through most of the boot process but fails with the following error: trap: invalid memory read access from kernal mode We tried over ethernet and the same server/client combination work OK. Below is the console output from the boot error: DEC 3000 - M500 Digital Equipment Corporation System conducting power up tests ------------------------------------------------------------ Devnam Devstat -------- ------- CPU OK KN15-AA -V2.4-S45E-I077-sV1.0-DECchip 21064 P3.0 ASIC OK MEM OK 96MB NVR OK CXT OK SCC OK ptr(0) = Present keybd(2) = Present NI OK Ethernet Address: 08-00-2B-39-83-10 , TENBT SCSI OK ISDN OK TC3 OK - PMAF-FA ------------------------------------------------------------ System power up OK. 83 BOOT SYS INIT-S-CPU... INIT-S-RESET_TC... INIT-S-ASIC... INIT-S-MEM... INIT-S-NVR... INIT-S-CXT... INIT-S-SCC... INIT-S-NI... INIT-S-SCSI... INIT-S-ISDN... INIT-S-TC3... AUDIT_BOOT_STARTS ... AUDIT_CHECKSUM_GOOD AUDIT_LOAD_BEGINS AUDIT_LOAD_DONE . . . >>> boot "3/ez0" INIT-S-CPU... INIT-S-RESET_TC... INIT-S-ASIC... INIT-S-MEM... INIT-S-NVR... INIT-S-CXT... INIT-S-SCC... INIT-S-NI... INIT-S-SCSI... INIT-S-ISDN... INIT-S-TC3... AUDIT_BOOT_STARTS ... AUDIT_TCBOOT_NETWORK AUDIT_LOAD_BEGINS .................................................................................................................................................................. AUDIT_LOAD_DONE SAS Boot program Secondary program text=224270 data=545e10 bss=879e0 va=ffffffff00000000 entry=ffffffff00002000 Remapping image Mapimage vaddr=0xffffffff00000000 spfn=0x104 npfns=0x3f9 First usable physical address=0x208000 Current PAL Revision <0x10529> Switching to OSF PALcode Succeeded New PAL Revision <0x2011c> Starting image at ffffffff00002000 secondary cache was auto sized to 64 pages Alpha boot: available memory from 0xbe0000 to 0x6000000 DEC OSF/1 V1.3 (Rev. 110); Tue Jun 29 22:00:58 EDT 1993 physical memory = 94.00 megabytes. available memory = 79.82 megabytes. using 360 buffers containing 2.81 megabytes of memory tc0 at nexus scc0 at tc0 slot 7 tcds0 at tc0 slot 6 asc0 at tcds0 slot 0 rz3 at asc0 bus 0 target 3 lun 0 (DEC RZ28 (C) DEC 435E) asc1 at tcds0 slot 1 fb0 at tc0 slot 8 1280X1024 ln0: DEC LANCE Module Name: PMAD-BA ln0 at tc0 slot 7 ln0: DEC LANCE Ethernet Interface, hardware address: 08:00:2b:39:83:10 fta0: DEC DEFTA (PDQ) Module Name: PMAF-FA fta0 at tc0 slot 3 fta0: DMA Available. fta0: DEC DEFTA (PDQ) FDDI Interface, Hardware address: 08:00:2b:a2:b5:66 , Firmware rev: 1.1 DEC3000 - M500 system Firmware revision: 2.4 PALcode: OSF version 1.28 lvm0: configured. lvm1: configured. Booted from Network Interface (BOOTP 0 3 0 0 0 2 PMAF-FA) trap: invalid memory read access from kernel mode faulting virtual address: 0x0000000000000098 pc of faulting instruction: 0xffffffff0007a894 ra contents at time of fault: 0xffffffff0007a818 sp contents at time of fault: 0xffffffff90777e88 panic: kernel memory fault dumpsys: entered. DUMP: Attempting partial dump to dev 0x100001, offset 0, numpages 1728. 83 BOOT SYS INIT-S-CPU... INIT-S-RESET_TC... INIT-S-ASIC... INIT-S-MEM... INIT-S-NVR... INIT-S-CXT... INIT-S-SCC... INIT-S-NI... INIT-S-SCSI... ?01 EXT HLT PC= 00000000.00076C88 PSL= 00000000.00001F00 >>>
1115.4	firmware problem and osf	RHETT::WALTER		`Tue May 02 1995 18:09`	7
	I would suspect a firmware Rev problem. What is the firmware Rev of the DEFTA...it is cutoff in your note. The CPU should be at Rev. 4.0. It is not. Don Walter CSC/Atlanta [email protected]
1115.5		NETRIX::thomas	The Code Warrior	`Wed May 03 1995 09:07`	1
	Note that remote boot won't work under V4.2 without some patches to DEC OSF/1.