From: Ryan, Jeff (jryan@wamnetgov.com)
Date: Thu Jul 08 2004 - 10:18:45 GMT-3
On the router Ethernet interfaces that are participating in your bridge
group, you can use the "bridge-group # spanning-disabled" command. This
will stop any STP loops.
Jeff Ryan
Chief Engineer
Design & Implementation
WAM!NET Government Services, Inc.
13665 Dulles Technology Drive, Herndon, VA 20171
Office: 703-480-2581
Mobile: 301-675-7344
AIM: Jeff Ryan WN Get my pgp key @ http://pgpkeys.mit.edu
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Koen Peetermans
Sent: Thursday, July 08, 2004 4:55 AM
To: ccielab@groupstudy.com
Subject: DLSW bridge-groups and Cat Layer2 switching.
Hi,
What would be the correlation of a (DLSW) bridge group spanning tree and
the
spanning tree running on the catalyst where the DLSW Ethernet interfaces
are
connected to ?
Since the bridge group uses protocol IEEE, wouldn't there be a risk of
the
bridge group "participating" in the spanning tree running on the
catalysts ?
I has really weird behaviour when running DLSW, CDP frames going over
the
DLSW clouds, intermittent connection loss to the routers doing DLSW,
.....
Having LSAP filters on DLSW would solve some of these issues, but I'm
still
wondering if the bridge-group can mess-up the catalyst spanning tree.
Am I correct ?
Kind regards,
Koen.
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:49 GMT-3