Conference azur::mcc

2956.0. "ELM spanning tree problems" by SUBWAY::REILLY (Mike Reilly - New York Bank District) Thu May 07 1992 12:04

    I am experiencing two problems with the ELM Spanning tree FM. 
    
    a) The spanning tree root of the network is a Vitalink bridge, so I
    get an error when the FM attempts to query the bridge. Should this
    prevent the building of the remainder of the spanning tree below the
    root bridge? I would have thought that a spanning tree discovery
    algorithm would have started at the 'leaf' entries and worked it's
    way up the tree using the designated bridge variable to build a map.
    Not having access to a particular bridge should not prevent the
    building of parts of the spanning tree below the unreachable bridge.
    
    b) There is a small section of the network running 802.1d, I get an 
    error message as this portion is being built as well.  
    
    (I)  Building logical spanning tree topology map...
    (E)  Cannot find/poll spanning tree root: 08-00-7C-00-0B-8F
    Cannot build spanning tree map for this root bridge
    (I)  Writing topology map file...
    (E)  Error writing icon for entity bridge.spmb01.
    (E)  Fatal error occurred during map file generation.
    
    
    The entity bridge.spmb01 is the an 802.1d LB150, and it looks like
    the Spanning Tree FM writes the icon to the map file. Here is the
    entire map file produced by this run.
    
    
     version 0
     domain JPM_DEV:.domain.span_tree
     last_x 0.975000 last_y -0.333000
    
     object_type 7
       text Spanning Tree Root:  08-00-7C-00-0B-8F
       x 1.300000 y 0.449550
    
     object_type 7
       text Spanning Tree Mode:  LAN Bridge 100 Mode
       x 1.300000 y 0.416250
    
     object_type 7
       text Spanning Tree Root:  08-00-2B-14-81-DF
       x 1.950000 y 0.782550
    
     object_type 7
       text Spanning Tree Mode:  IEEE 802.1 Mode
       x 1.950000 y 0.749250
    
     object_type 1
      icon_file mcc_bridge_lanbridge_150_icon.dat
      mcc_code 9
      center_x 1.950000 center_y 0.666000
      text_x 1.995833 text_y 0.666000
      name bridge.spmb01
    
    
    
    I have also noticed that the bridge name is bridge.spmb01 not
    .bridge.spmb01, is this a problem?
    
    
    Thanks,
    
    Mike

Hello,

I am also having the problem described in .0 and am not able to generate a map
because autoconfig is unable to access the root bridge which is a Vitalink Bridge.

Regards,

Peter Lamb

    A lot of users are experiencing the problem of building a map when
    the root can't be polled for its spanning tree attributes.
    I am working on a fix that will "map around" the root when this
    happens.   Thank you for bring this to my attention.  I'll let
    you know when I have something for you to try.
    
    re .0
    
    (E)  Error writing icon for entity bridge.spmb01.
    (E)  Fatal error occurred during map file generation.
    
    
    This error usually occurs when an icon file is missing from
    mcc_icons.   Check mcc_icons for mcc_bridge*icon.dat to 
    see if you have all of the bridge icons.   It looks like the
    file mcc_bridge_lanbridge_150_icon.dat may be missing.
    
    Thanks,
    
    Bob