| I am not sure exactly what you are trying to accomplish, but it
appears to me that you have created a spanning tree loop which is being
resolved by putting the ports into the spanning tree blocking state.
Since you say "LAT bridging", I assume that all of your ports are
running IEEE802.1d spanning tree.
MDL
|
| You are right of course, Mike, STP is blocking the link, I can see that now.
The Nis'es in parallel are there for redundancy, and in order to maintain that
redundancy for the routed protocols I guess we could disable bridging on one of
the Nis'es. Do you see any better solution ?
Erik
|
| I am not certain what you are trying to do with that topology, and
what the constraints are.
What services do the DECnis systems provide? I don't understand
exactly what your diagram is telling me.
If SLNIS1 and SLNIS2 are physically colocated with the two
GIGAswitch/FDDI systems, I'd start by dual homing the two DECnis
systems to different GIGAswitch/FDDI systems, instead of dual homing
each to the same GIGAswitch/FDDI system.
Allowing bridging to work on all the interfaces is going to result
in spanning tree blocking all but one connection as you have found out.
As far as I can see, your options are:
1) Live with spanning tree failover time (as you have now)
2) Disable the redundant bridging connections
3) If the Area 2 network is FDDI, connect it directly to the
GIGAswitch/FDDI system - I assume it isn't, otherwise there's no point
to the DECnis systems
4) Separate out the routing/bridging, either with additional
interfaces, or additional devices.
MDL
|