Conference 7.286::fddi

561.0. "MDF and LAT "funnies"/features ?" by LARVAE::HARVEY (Baldly going into the unknown...) Thu May 07 1992 13:39

      Further to a previous note from Adrian Leate and DECnet "funnies", we 
      are seeing some strange LAT (and possibly similar DECnet) behaviour in 
      our second MDF installation too.
    
      We are running LAT over the ethernet controllers of FDDI connected nodes.
      A DECbridge 510 in each lobe connects the ethernet to the FDDI. 
      There are no bridge filters installed.
    
      Symptoms:
      A terminal server on the same ethernet segment can see/offer ALL LAT 
      services from nodes on that segment - including the FDDI connected (MDF) 
      nodes.
    
      A remote lobe terminal server (connecting over the FDDI backbone via 
      DECbridge 510) can see/offer LAT services of all the ethernet connected 
      nodes but cannot see/offer the LAT services of the FDDI connected nodes.
    
      This situation works the same for terminal servers on each lobe's 
      ethernet segments   ie. it's consistent at least !
    
      Anyone have any ideas ? We are chasing up the startup sequence of LAT at 
      the moment as it appears there are problems if you start it over one 
      circuit, stop it and restart over another circuit   ie. stop LAT over 
      FDDI and restart over ethernet etc. This may be the culprit in our 
      current configuration.
    
      Thanks in advance
    
      Rog