Hi again, > Well, do you have loop protect enabled? If so, is it enabled on the port > in question? What does that other switch do with the respective BPDUs?
Loop protect is not enabled here. Wouldn't make sense either way since this is not a non-designated port. > What kind of spanning tree is configured on that other switch? If only I knew ;-) > BTW I think it is quite strange that you have a "private network" > comprising at least one switch connected to your LAN. If this means that > some other LAN outside your control is connected to your own LAN, you > have a recipe for trouble... It's a custom setup by a vendor and we only have partial control over that... > If you do not expect any BPDUs incoming on port ge.1.13, you should > configure it as an access port (edge port) and enable spanguard to block > the port if a BPDU comes that way. Spanguard is disabled since this is a core switch, therefore most ports are indeed non-edge ports. > If the other switch in question sends spurious BPDUs, you might even > consider disabling STP on that port... BUT I'd rather replace (or fix) > that "other" switch. I fully agree. > A correct setup would have all switches in your layer 2 network > participate in the spanning tree, of course. No objection here either... For now I have tried to prepare myself for the upcoming sniffing session tomorrow and now I am wondering about the PortID in the BPDU frame. If I receive a value of e.g. 0x8085, then the port ID would be 133 (0x85 = decimal 133). What index is that? Thanks! Marki --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
