All
Could you please verify that you enabled lacp at the port level
Thank you
Jason

On Dec 12, 2010, at 7:35 PM, "Stephen Loeckle" <[email protected]> 
wrote:

> Your thinking is correct. However, we couldn't imagine a scenario in which a 
> loop would be unintentionally created on the S4. We only have edge switches 
> and 10 vmware hosts plugged into the box.
> 
> ----- Original Message -----
> From: "Egbert Rodriguez Hernandez" <[email protected]>
> To: "Enterasys Customer Mailing List" <[email protected]>
> Sent: Sunday, December 12, 2010 6:13:36 PM
> Subject: RE: [enterasys] S4 Chassis Interconnected with Foundry EdgeIron 
> 4802cf
> 
> 
> 
> 
> Hi Stephen, 
> 
> 
> 
> That’s the exactly scenario that we are facing. We are going to change a 
> BigIron 8000 for a S4 Chassis. Actually, the passing communication is doing 
> well if and only if the spanning tree is disabled in the Foundry’s uplinks 
> port to the S4 Chassis, but still enable globally on both. In your case that 
> you disabled the spanning tree globally in the S4 Chassis, what are you doing 
> for stop loops in the S4 Chassis? I mean, because if the spanning tree is 
> disabled globally I think that no matter if the spanning tree portadmin 
> status is enable on ports, it will not work… or my thinking is wrong? 
> 
> 
> 
> 
> Egbert Rodriguez Hernandez 
> 
> Jr. Network Engineer 
> 
> CCTV Level I, ESE 
> 
> Caribbean Micro Services 
> 
> Tel. 787-620-7780 x4327 
> 
> Fax.787-620-7784 
> 
> Mobile.787-224-0193 
> 
> www.caribbeanmicro.com 
> 
> 
> 
> CONFIDENTIALITY NOTE: The information contained in this e-mail and its 
> attachments are proprietary and confidential to Caribbean Micro Services, 
> Inc.(CMS), its affiliates or its clients. They may not be disclosed, 
> distributed, used, copied or modified in any way without CMS, Inc.s 
> authorization. If you are not the intended recipient of this email, you are 
> not an authorized person. If the reader of this message is not the intended 
> recipient, please delete it and notify its original sender immediately. CMS, 
> Inc. and its affiliates do not assume any liability for damages resulting 
> from emails that have been sent or altered without their consent. Moreover, 
> CMS, Inc. has taken precautions to safeguard its email communications, but 
> cannot assure that such is the case and disclaim any responsibility 
> attributable thereof. 
> 
> 
> 
> 
> 
> From: Stephen Loeckle [mailto:[email protected]] 
> Sent: Sunday, December 12, 2010 7:12 PM 
> To: Enterasys Customer Mailing List 
> Subject: Re: [enterasys] S4 Chassis Interconnected with Foundry EdgeIron 
> 4802cf 
> 
> 
> 
> 
> Hi Egbert, 
> 
> I just finished an install at a college where we replaced a bigiron 8000 with 
> a S4. We still have all the foundry edge switches running the IDFs on campus. 
> In order for this to work for us with redundant links to the foundry edge 
> switches, we disabled STP globally in the S4 and in each foundry switch and 
> configured LACP for the uplink trunks. STP and LACP don't mix as STP is 
> trying to bring down the redundant link and LACP is trying to use it for load 
> balancing. 
> 
> Stephen 
> ----- Original Message -----
> 
> 
> From: "Egbert Rodriguez Hernandez" <[email protected]> 
> To: "Enterasys Customer Mailing List" <[email protected]> 
> Sent: Sunday, December 12, 2010 3:52:49 PM 
> Subject: [enterasys] S4 Chassis Interconnected with Foundry EdgeIron 4802cf 
> 
> 
> 
> 
> Hi, 
> 
> 
> 
> There someone have this scenario before or already deployed? I’m trying to 
> connect the S4 Chassis (CORE) to some Foundry EdgeIron Switches (DISTRIBUTION 
> and EDGE) and the only way that I’m able to pass communication between links 
> is disabling the spanning tree on the Foundry uplink port to the S4 Chassis. 
> If I have enable the spanning tree globally and on the uplinks port in both 
> the communication hangover. The firmware operation code of the EdgeIron 
> 4802cf is 2.2.4.29. The S4 Chassis has the latest firmware installed 
> 7.11.01.0026 released on 01-Nov-2010. 
> 
> 
> 
> If have LACP configured in both the only way that I’m able to pass 
> communication between both is disabling the spanning tree on the S4 Chassis 
> uplink port, because the Foundry’s one when configured the LACP it disable 
> automatically the spanning tree on the ports forming the LACP and in the LACP 
> itself. 
> 
> 
> 
> Egbert Rodriguez Hernandez 
> 
> Jr. Network Engineer 
> 
> CCTV Level I, ESE 
> 
> Caribbean Micro Services 
> 
> Tel. 787-620-7780 x4327 
> 
> Fax.787-620-7784 
> 
> Mobile.787-224-0193 
> 
> www.caribbeanmicro.com 
> 
> 
> 
> CONFIDENTIALITY NOTE: The information contained in this e-mail and its 
> attachments are proprietary and confidential to Caribbean Micro Services, 
> Inc.(CMS), its affiliates or its clients. They may not be disclosed, 
> distributed, used, copied or modified in any way without CMS, Inc.s 
> authorization. If you are not the intended recipient of this email, you are 
> not an authorized person. If the reader of this message is not the intended 
> recipient, please delete it and notify its original sender immediately. CMS, 
> Inc. and its affiliates do not assume any liability for damages resulting 
> from emails that have been sent or altered without their consent. Moreover, 
> CMS, Inc. has taken precautions to safeguard its email communications, but 
> cannot assure that such is the case and disclaim any responsibility 
> attributable thereof. 
> 
> 
> 
>    • --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] 
> 
> 
> 
> 
>    • --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]
> 


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

Reply via email to