You apply STP settings to the lag.0.1 port. Lag takes control of the physical
port when the aggregation forms, it then changes the physical port/interface's
operstatus to the dormant state and the lag's port becomes operational. At
that point STP stops sending BPDU frames out each physical port and starts
sending them out the "lag" port. but now only one BPDU regardless of the
number of physical ports in the lag. the bridge port that is active is the lag
port.
So you would issue these two commands:
set spantree lp lag.0.1 enable
set spantree lpcapablepartner lag.0.1 true
// this tells the switch it can expect certain behaviors only supported by
LP and allows it to report immediately when it is missing.
Always be sure to provision port settings on the physical ports as well. This
is done in case the lag does not form for some reason (a failed lacp state
machine for example). Typically the port would be set to disable bridging-
"set port spantree portenable tg.1.1,2 disable"
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Friday, August 19, 2011 4:52 PM
To: Enterasys Customer Mailing List
Subject: RE:[enterasys] Rstp and loop protect
Hi Ernie,
How should I configure lp (especially on lags)?
E.G.
S1
ISL on lag.0.1 (=tg.1.1+tg.1.2)
Is the following config correct ?
set spantree lp lag.0.1 enable
set spantree lpcapablepartner lag.0.1
or should I also add:
set spantree lp tg.1.1
set spantree lp tg.1.2
set spantree lpcapablepartner tg.1.1
set spantree lpcapablepartner tg.1.2
S2
same config as on S1
What do you recommend?
Thanks in advance for the helpfull information.
Franco
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
