Thanks Markus, okay so that got it out of dormant and up, but it still won't 
let the switch come up if I unplug it from the second core. One thing I should 
probably mention on this is that there are two lags between the cores. A 20 gig 
lag with two 10 gig ports in it and a 2 gig lag with two copper gig links. If I 
unplug the 2 gig lag then the core goes down. If I leave that one plugged up 
and bring down the 20 gig lag then nothing happens and the link stays up. I've 
been thinking ever sense I inherited this installation that something was wrong 
there and I'm not sure if this is related to my other issue or not, but it 
seems feasible.

Bruce Hopkins
Security Administrator OIIT
Off: 229-430-6349

All that is valuable in human society depends upon the opportunity for 
development accorded the individual. 
Albert Einstein 

-----Original Message-----
From: Kaiser, Markus [mailto:[email protected]] 
Sent: Monday, March 07, 2011 9:11 AM
To: Enterasys Customer Mailing List
Cc: Enterasys Customer Mailing List
Subject: Re: [enterasys] Dormant and Blocking Ports

Dormant means, there is a higher protocol active, which takes control over the 
physical ports. In most cases this is 802.1ad LACP protocol.

LACP is enabled by default and if you connect two ports between two devices, 
then a logical port (lag.x.x) is created via LACP protocol. If this happens, 
you need to tag (vlan egress list) all required vlans also to the formed     
lag.x.x port (check via show lacp command), not just the physical port.

If you don't want to use LACP and STP instead for redundant links, you can 
disable LACP globally (set lacp disable) or per port (set port lacp port ge.x.x 
disable) or for all ports (set port lacp port *.*.* disable).

This should solve your problem.

Cheers,
Markus

Sent via iPhone.

On 07.03.2011, at 14:57, "Hopkins, Bruce" 
<[email protected]<mailto:[email protected]>> wrote:

Just wanted to put this out there in case anyone has ever seen it. I have a 
dual core configuration with N7 chassis. This was set up so that the edge 
switches each had a fiber plugged into each core. I'm working on dropping out 
this second core and as a result I'm dropping the second connection. For the 
most part this has went without incident, but I have a couple of these where 
the port they are plugged into on the core I'm keeping is set to dormant and 
spantree is blocking. So essentially when I disconnect the edge for the second 
core the switch goes down. I've tried everything I can think of to get the 
ports to come off dormant and forward traffic but it does not matter. Even 
plugging into another port on these two vlans( there are only two that are 
affected) will set that port as blocking. I've looked at the edge sw2ithces and 
do not see anything that should be causing this. I've also looked to make sure 
I did not have a loop on the edge switches.

I've got a call into GTAC right now, but I was just wonder if any one else had 
ever seen anything like this and could get me a clue or tell me how to force 
the ports to start forwarding traffic.

Bruce Hopkins
Security Administrator OIIT
Off: 229-430-6349

All that is valuable in human society depends upon the opportunity for 
development accorded the individual.
Albert Einstein


  *   --To unsubscribe from enterasys, send email to <mailto:[email protected]> 
[email protected]<mailto:[email protected]> with the body: unsubscribe enterasys 
[email protected]<mailto:[email protected]>


---
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]

Reply via email to