[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

1659.0. "VAX 4000/300 & DEFQA" by GRANPA::TKURTZ () Mon Apr 24 1995 16:45

    	Hi,
    I would appreciate any help here. I recently installed defqa-sf's in a
    number of VAX 4000/400's without a problem. I could see the fddi
    controller at the halt prompt by doing a "show dev" or a "show
    ethernet". However, while attempting to upgrade VAX4000/300's I could
    not see it (at the halt prompt). I cruised Tima for any concrete
    information but came up empty. Unfortunately, these systems are
    production which limits downtime. I know the customer is at VMS
     5.5-2 and has yet to install the driver. I also realize he should
    upgrade to VMS 5.5-2H4 or above. 
    
    Here is what I suspect.
    1. Firmware level does not know about the DEFQA option yet.
    2. DEFQA in a VAX4000/300 acts much like a PC using a CD-ROM
       in that it is only seen when the driver is loaded.
    
    I need concrete information on this as soon as possible. the official
    word is that the VAX4000/300 does support the DEFQA but little else
    information available.
    
    					Thanks,
    				       Tom Kurtz  
                                          MCS

T.R	Title	User	Personal Name	Date	Lines
1659.1		STAR::STOCKDALE		`Tue Apr 25 1995 11:30`	5
	I have a 4000-300 with a couple of DEFQAs in it that are alleged to work (its powered down), so I'm pretty sure the DEFQA is supported in that system. - Dick (VMS LAN driver group)
1659.2	maybe incorrect dip switch settings	STAR::GAGNE	David Gagne - UNIX Development	`Tue Apr 25 1995 15:12`	7
	I believe there are some dip switches on the DEFQA to set the CSR addresses. If these are set wrong, then the device will not show up or be functional. It has been a while since I did anything on the Qbus, but I think it's the CONFIG command in SYSGEN that can be used to determine the setting of the CSR dip switches.
1659.3	Catch 22	GRANPA::TKURTZ		`Tue Apr 25 1995 15:49`	18
	David, I tried to do just as you have suggested but found that the customer's version of VMS 5.5-2 did not recognize the driver. The nodes I am upgrading are used as pathworks servers. There are no options added, just the bare minimum included with the cpu and memory (DSSI & Ethernet). I used the starting addresses of 761400 & 764400 with no results. What bothers me about this problem is why I can see the DEFQA at the halt prompt on a VAX4000/400 but not on a VAX4000/300. I at least want the assurance of knowing whether or not the model 300 is more driver dependant before scheduling more down time for these systems to add these DEFQA's. RE: .1 Would it be possible for you to power up your model 300 and do a "show dev" or " show ethernet". This would help in establishing where we stand. Thanks Guys, Tom Kurtz
1659.4	look closely at the 4000/300	STAR::GAGNE	David Gagne - UNIX Development	`Tue Apr 25 1995 16:49`	18
	The CSR addresses must be set for every single system. Even if you have two systems that are the same model, you must still set the CSR addresses for each system. The CSR address values are based upon what you have on your Qbus. So if the VAX4000/400 has nothing but the DEFQAs on the Qbus, then you configure only the two DEFQAs. If the VAX4000/300 has something else on the Qbus, then you must include that in the configuration information to get the proper CSR settings for the DEFQAs. There should be some sort of SHOW command that will tell you what you currently have configured on the Qbus (again, a SYSGEN command); maybe SHOW/CONFIG??? Try that command on the VAX4000/300 to see if there's anything else on the Qbus. The VAX4000/300 that Dick was talking about does properly use the DEFQAs. They were tested on that machine during driver development.