[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

1710.0. "Unknown location accessed on the network adaptor" by CSC32::N_HENDERSON (Nancy Henderson CSC/CS, sort of) Tue Jun 06 1995 16:47

    Every time this AXP 2100 with dual fddi cards boots, they see about 5
    minutes of constant messages:
    
    	Unknown location accessed on the network adaptor.
    
    Section B1 of the Network Administration and Problem Solving guide
    says, "This is a hardware error."
    
    They've replaced the boards and get the same results.
    
    What other hardware might be causing this error?
    
    The messages eventually stop and things work, but there is a concern
    that something else might actually be wrong.
    
    Nancy
T.RTitleUserPersonal
Name		DateLines
1710.1NETRIX::thomasThe Code WarriorTue Jun 06 1995 17:152
This is either a driver bug or a firmware bug (in all likelyhood).
I'd guess a driver bug.
1710.2NETCAD::STEFANIWelcome to the Revolution!Tue Jun 06 1995 20:178
    Does this message appear in the SRM, or when the operating system comes
    up?  You may want to post the exact system configuration, system
    firmware revision, FDDI adapter model (EISA or PCI), and OS in the
    MVBLAB::SABLE Notes conference.  There is not enough information here
    to go on, but folks in the Sable conference should be able to verify
    that the system hardware/firmware is current.
    
    - Larry
1710.3System firmware of 3.9 shows the problemCSC32::N_HENDERSONNancy Henderson CSC/CS, sort ofTue Jun 13 1995 11:5417
    Thank you for your responses.
    
    The customer found this morning that one 2100 with system firmware of
    3.8 does not produce the messages on the console at system startup
    while the 2100 with system firmware version of 3.9 does.  When they
    backed off to firmware 3.8, the messages stopped appearing.
    
    In both cases, the defea-da hardware rev. is 2.0 and firmware is 2.3.
    
    Should I continue this discussion here, or move over to MVBLAB::SABLE?
    
    I guess what we would like to see is whether there could be a firmware
    revision which has any fixes supplied in 3.9, but which does not
    produce the error messages.
    
    Nancy
1710.4NETCAD::STEFANIWelcome to the Revolution!Tue Jun 13 1995 19:329
    >>Should I continue this discussion here, or move over to MVBLAB::SABLE?
    
    I would definitely move the discussion to the Sable Notes conference. 
    I know the AlphaServer 2100 engineers follow that conference and can
    either take this as an action item, or suggest an even newer version
    of firmware.
    
    Good luck,
       Larry
1710.5Heading to SABLE conference...CSC32::N_HENDERSONNancy Henderson CSC/CS, sort ofTue Jun 13 1995 19:499
    Larry,
    
    Thank you.  Just FYI, I have received another problem with defea on a
    2100 with firmware rev. 3.9.
    
    So, I will head over to MVBLAB::SABLE.
    
    Nancy