[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

1916.0. "VMS V6.2 + AXP2100 + FDDI Problem" by GRANPA::BARABIA () Tue Jan 02 1996 09:54

    We recently installed an AXP 2100 at our customer site. We did the
    installs/configs of OpenVMS V6.2, DECNET,LAT PATHWORKS for OpenVMS
    LanManager and PATHWORKS for Macintosh using the DEFEA FDDI controller.
    The primary use of the systems is as a PATHWORKS server supporting
    about 300+ clients. 
    
    When we put the system up for use, we very quickly experienced network
    related problems with all protocols to and from the 2100. This problem
    would appear as the user load increased and then would seem to resolve
    itself after a couple hours. We tried to troubleshoot this problem for
    2-3 days but were forced to disable the FDDI controller and switch to
    the Ethernet port so users could use the system.
    
    The customers network group tried troubleshooting the network hardware
    components as well as the system but could not come up with any useable
    diagnostics that could uncover a problem. Since we could not afford the
    system to be un-useable, we needed to quickly switch back to the
    Ethernet port. Since we've been using the Ethernet port, we've not
    experienced any problems.
    
    PATHWORKS engineering is looking into possible problems with FDDI
    boards since there is an issue with NETBIOS and the FDDI hardware
    however this problem should not affect DECNET or LAT which we could
    not use when the problem occured. I unfortunately did not have time to
    get detailed troubleshooting info before they switched back to
    Ethernet.
    
    Customer has a concern there could be a problem with VMS V6.2 on AXP's
    using FDDI. They have 2 7610's using FDDI with VMS V6.1. He's planning
    to upgrade those systems to VMS6.2 but again is concerned that he could
    then have an FDDI problem.
    
    Are there any known issues with VMS V6.2 and the DEFEA or any other
    FDDI controller? So far I've not seen anything on this in this or other
    notes conferences so I thought I'd post this.
    
    Any input would be greatly appreciated.
    
    Thanks
    Barry A

T.R	Title	User	Personal Name	Date	Lines
1916.1		STAR::STOCKDALE		`Wed Jan 03 1996 08:52`	12
	>> Are there any known issues with VMS V6.2 and the DEFEA or any other >> FDDI controller? So far I've not seen anything on this in this or other >> notes conferences so I thought I'd post this. There is only one known possible problem with the DEFEA driver on V6.2 and it has to do with recovery after a cable disconnect. Whether this problem is actually a driver problem is still undetermined. From the testing done for qual of V6.2 and V6.2-1H1 the DEFEA has worked flawlessly, albeit slower than the PCI FDDI adapter the DEFPA. - Dick
1916.2	Firmware Versions?	GRANPA::BARABIA		`Wed Jan 03 1996 09:05`	11
	Since I posted my base note, someone else mentioned we should take a look at the AXP 2100 firmware settings making sure its up to rev an to check the EISA configuration for the DEFEA. I'm hoping to get soem help from our hardware guy on this but I was wondering if there are guidelines anywhere on recommendations on firmware and or EISA config settings beyond the defaults for the AXP 2100 and DEFEA. As far as I know, we are running with default settings but I need to double check this with the hardware guy. Thanks for the input. Barry A
1916.3		NETCAD::STEFANI	Machines to humanize	`Wed Jan 03 1996 11:31`	13
	>>guidelines anywhere on recommendations on firmware and or EISA config >>settings beyond the defaults for the AXP 2100 and DEFEA. As far as I >>know, we are running with default settings but I need to double check >>this with the hardware guy. I can't comment on system firmware settings, but the DEFEA EISA configuration is fairly straightforward. You have to select a non-conflicting memory and IRQ assignment. You should make sure that the DEFEA is running its latest on-board firmware (v2.46) and the current Alpha FW CD has a utility that will take care of this for you. I believe there's also an OpenVMS utility (LANCP?) to do this as well. /l
1916.4	Mikie Likes it	CIVPR1::MARKIS	Depends on Your Perspective, Ofcourse ...	`Mon Feb 12 1996 19:17`	9
	Barry, Contact Michael Simmons @ "civpr1::simmons". Our department has hundreds of Alphas running EISA FDDI Cards. We are also using the PCI FDDI Cards in A1000's, in addition to the EISA FDDI Cards. He is "Keeper of the Patches" for VMS V6.1 and V6.2, for this Group. He will be back from Phoenix on the 14th of February. He may also assist you with any "SYSGEN" Params that might need reconfiguring to efficiently support FDDI on the ALPHA's. Chris
1916.5	Ck 1878, too	CIVPR1::MARKIS	Depends on Your Perspective, Ofcourse ...	`Mon Feb 12 1996 19:30`	4
	Barry, Also check "1878" to see if this is similar to your problem .... Chris :)