Hi Stuart, I believe it's a limitation of the switches. We use C3's in a similar fashion, so in a stack of three or more, we use the port mappings to create dual member/port LAG's with design for single member failure and business continuity:
* Lag.0.1 = ge.1.21, ge.2.21 * Lag.0.2 = ge.3.21, ge.1.22 * Lag.0.3 = ge.2.22, ge.3.22 * Lag.0.4 = ge.1.23, ge.2.23 * Lag.0.5 = ge.3.23, ge.1.24 * Lag.0.6 = ge.2.24, ge.3.24 How many ports would you want to use in a LAG? Note that due to the port buffer size on C's, other hardware platforms may serve you better. We have migrated, in instances, from C3 stacks to SSA's. Sincerely, Jolyon Ansuz Senior Network and Communications Administrator Communications Infrastructure Information Technology University of New England Armidale NSW 2351 "Most of the things worth doing in the world had been declared impossible before they were done.", Louis D. Brandeis -++- From: Stuart McRobert [mailto:[email protected]] Sent: Thursday, 4 August 2011 12:27 PM To: Enterasys Customer Mailing List Subject: [enterasys] LACP ports in a C2 Stack Hi Everyone, I was hoping someone could shed some light on configuring static LACP ports in a C2 stacked environment. Basically I have two C2 (C2G124-48)switches configured in a stack however based upon the information I have read the C2's are only capable of 6 LAG ports(lag.0.1-0.6) in total. I would have assumed that with two switches in a stack this would have doubled to twelve ports as when you halve it, 3 lag ports per switch isn't many? Any assistance would be much appreciated. Regards, Stuart McRobert ICT Infrastructure and Systems Support - Manager Department of Sport and Recreation | (08) 9492 9851 | (08) 9492 9711 | [email protected] www.dsr.wa.gov.au 246 Vincent Street, LEEDERVILLE, W.A, 6007 PO BOX 329, LEEDERVILLE, W.A, 6903 . --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]
