[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1666.0. "DEFQA and Pathworks on VMS for Netware" by GIDDAY::STANISLAUS () Mon May 01 1995 03:31
We installed a DEFQA on a VAX4000-500A and ran NET$CONFIGURE ADVANCED
and chose DEVICE CONFIGURATION to run DECnet/OSI on FDDI (FQA0) instead of
Ethernet (EZA0). This worked fine. Ofcourse we had to do some FXA to FQA0
logical definitions since we were running DECnet/OSI ver 5.6B.
We did a DEF/SYS/EXEC LAT$DEVICE FQA0 to make LAT run on FDDI and not
on Ethernet. This worked fine as well.
Then we ran PWVN$CONFIG to make Pathworks use FDDI and not Ethernet.
This command procedure PWCCVN$CONFIG.COM did not see the FDDI device. It only
sees the Ethernet device on this VAX4000-500A. Customer wants to disconnect
Ethernet and use all protocols on DEFQA and hence bought the DEFQA.
Any suggestions on why PWVN$CONFIG does not see the DEFQA.
Alphonse
T.R | Title | User | Personal Name | Date | Lines |
---|
1666.1 | Pathworks for VMS (Netware) I am talking about is ver 1.0c | GIDDAY::STANISLAUS | | Mon May 01 1995 06:14 | 0
|