[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

1771.0. "DECnet over DEFEA. " by KERNEL::LOTA () Fri Aug 04 1995 05:46

    Hi,
    
    On my ALPHA 2100 server, I'm using the FDDI interface and connect it to
    a DECconcentrator 500. On the same concentrator I have another machine
    with an FDDI card.
    
    The alpha is running VMS V6.2 and the FDDI device is DEFEA. I've
    configured DECnet over this device and can quite happily talk to the
    other node via DECnet.
    
    However, if I pull the FDDI cable out from the machine, and leave it
    out for 5 secs, and put in back in again, and try set host to other
    machine over the ring, my set host command hangs! If I fire up another
    window, and look at the information in NCP, my process hangs and goes
    into RWAST!!!
    
    The only way to clear the problem is to HALT the machine and bring it
    back up and it will keep working until such time as the FDDI cable is
    pulled out again and re-inserted.
    
    This problem was brought to my attention by a customer and I've now
    managed to reproduce it inhouse. Since then, we've had a different
    customer also highlighting the same problem, so this definately broken.
    
    I enclose some info below regarding the driver rev and such like. 
    
    
    Is there a patch to this problem? I'll be looking to get something
    offical into the system ie IPMT, so if this has been fixed please let
    me know. Otherwise, I'll IPMT the case next week.
    
    Thanks,
    
    Jas Lota
    (CSC UK)
    ----------------------------------------------------------------------
    $ ana/image/inter sys$loadable_images:sys$frdriver
      
           Image Identification Information
    
                    image name: "SYS$FRDRIVER"
                    image file identification: "X-3"
                    image file build identification: "X61Q-SSB-0000"
                    link date/time:  4-MAY-1995 22:59:21.84
                    linker identification: "A11-12"
    
    
    
    
    SDA> clue config
    
    System Configuration:
    ---------------------
    System Information:
    System Type    AlphaServer 2100 4/200                 Primary CPU ID 00
    Cycle Time     5.2 nsec (190 MHz)                     Pagesize      
    8192 Byte
    
    Memory Configuration:
    Cluster    PFN Start    PFN Count         Range (MByte)       Usage
     #03             0          256         0.0 MB -    2.0 MB    Console
     #04           256        16127         2.0 MB -  127.9 MB    System
     #05         16383            1       127.9 MB -  128.0 MB    Console
    
    Per-CPU Slot Processor Information:
    CPU ID         00                        CPU State   
    rc,pa,pp,cv,pv,pmv,pl
    CPU Type       EV4  Pass 3 (21064)       Halt PC      00000000 20000000
    PAL Code       5.48                      Halt PS      00000000 00001F00
    CPU Revision   ....                      Halt Code    00000000 00000000
    Serial Number  ..........                             Bootstrap or
    Powerfail
    Console Vers   V4.0-3
    
    
    
    
T.RTitleUserPersonal
Name
DateLines
1771.1A new version of SYS$FRDRIVER fixes this...KERNEL::LOTATue Jan 16 1996 04:1415
    I logged an IPMT on this problem and engineering fixed the problem by
    providing a new version of SYS$FRDRIVER.
    
            Image Identification Information
    
                    image name: "SYS$FRDRIVER"
                    image file identification: "X-3"
                    image file build identification: "X61Q-SSB-0000"
                    link date/time: 19-DEC-1995 00:15:08.04
                    linker identification: "A11-12"
    
    
    This fixed the problems we were seeing at three sites.
    
    Jas.
1771.2Location...KERNEL::LOTATue Jan 30 1996 10:426
    Patch on:
    	COMICS"ACCESS"::DSA400:[LOTA]SYS$FRDRIVER.EXE_V62R
    
    Don't know how long it will stay there..
    
    Jas.