[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

2085.0. "DEVREQERR when connect to DECserver thru FDDI(DEMFA)" by KAOT01::WATTERS () Thu Jul 11 1996 12:18

    I have a customer who can't connect to his terminal servers w/o
    getting the following error on a mcr ncp conn node.....
    	SYSTEM-F-DEVREQERR, device request error
    
    I found an article in STARS that mentions that there is a new FXDRIVER
    X-27 (customer's got x-24). Where can I get this driver?????
    
    
    Article: {Elev} Unable to access DECservers via TSM; DEMFA controller.
    
    
    Thanks,
    
    Andy

T.R Title User Personal
Name Date Lines

2085.1 19584::STOCKDALE Wed Jul 17 1996 15:55 18

T.R	Title	User	Personal Name	Date	Lines
2085.1		19584::STOCKDALE		`Wed Jul 17 1996 15:55`	18
	'Device request error' is the error returned by FXDRIVER to the user (MOP) that is trying to start when an error is gotten on the command to the DEMFA to start up the user. There was a problem where stale status wasn't overwritten by the DEMFA when a command was complete fixed by X-24 to clear the status field before each command was issued. X-25,26,27 were unrelated to this problem (NCP connect). Since it works as near as I can tell on the 6000 system in this cluster using multiple users at the same time to do connects, I'd suggest ensuring the DEMFA firmware is up-to-date (V1.3 or later) and determine the steps resulting in the inability to connect. My guess is that this condition comes about after some other problem, ie. after rebooting (using V6.2 and up-to-date firmware), you should be able to connect, but later on the problem manifests itself. - Dick

'Device request error' is the error returned by FXDRIVER to the user
(MOP) that is trying to start when an error is gotten on the command
to the DEMFA to start up the user.

There was a problem where stale status wasn't overwritten by the DEMFA
when a command was complete fixed by X-24 to clear the status field
before each command was issued.  X-25,26,27 were unrelated to this
problem (NCP connect).

Since it works as near as I can tell on the 6000 system in this
cluster using multiple users at the same time to do connects, I'd
suggest ensuring the DEMFA firmware is up-to-date (V1.3 or later)
and determine the steps resulting in the inability to connect.  My
guess is that this condition comes about after some other problem,
ie. after rebooting (using V6.2 and up-to-date firmware), you
should be able to connect, but later on the problem manifests itself.

- Dick