Edge closet design

[DJaquays]

We’re getting ready to refresh a significant number of edge closets and are looking to change up a few things. Our primary goals are:

• Support 2.5/5gbps links for our WAPs.
• Reduce/eliminate total downtime of the wired network and wireless network
• Save money

The current thought is to do something like the following:

• Place 2 higher-end switches capable of multi-gigabit links to handle the WAPs (max ~20 APs/closet)
• Fill out the remaining port needs with lower-end PoE switches

The question is, what’s the best way to accomplish the first 3 points following the second two. My initial thought would be to take the two higher-end switches (either 5520s or x465s) and set them up as an MLAG and the lower-end switches (either x440s or v400s) as a “stack” (with the understanding that V400s don’t actually stack and assuming that V400s can be uplinked to an MLAG). This should allow any one of the 3 entities to go down for whatever reason (hopefully just firmware updates) without taking the other 2 down.

Diagram of what I think is a good idea until people tell me why I’m being dumb:

Am I missing anything? I understand that nothing benefits from the MLAG except for the stack and the uplink to the core. Is there a better way to accomplish what I’m after?

[DJaquays]

I was about to say that MU-MIMO support is non-existent outside of phones, but now I see the Intel AX200 supports MU-MIMO so perhaps that will change. Do remember that 2.4Gbps is the data rate, not the achieved throughput. I also tend to discount 80MHz channels and 2.4GHz but the former will become relevant with wifi 6E APs. You’ll be upgrading your APs before 7 years BTW, Extreme drops AP software support 2 years after end-of-sale (which is too early IMHO, but that’s another argument). But if your switches need to last that long then 2.5Gbps ports for APs are probably worth it

We don't purchase extreme wireless products, it's all HPE/Aruba and they do not APs that quickly. Our current APs were purchased in 2013.

[StephanH]

Hello,

now I have a final answer from GTAC:

The AP510 supports redundant power via PoE.

[DJaquays]

The short answer is: probably. We generally upgrade our networking equipment every 7-10-ish years. So we have to think about what the environment is going to look like in 5 years, when there’s been enough time for significant change in end user technology because we still have multiple years before the next refresh. We’re a medical school and healthcare facility, so we have some significant device-dense areas, bandwidth intense applications (VDI, Citrix, telehealth, virtual classrooms, remote lecturers, Netflix, spotify), and patient care critical devices (though we’re not a hospital, so not life/death level critical). Couple that with a significant group of endusers (students) who expect to walk in with the latest and greatest devices and have the best experience.

The spec sheet of the APs we’re moving to says this:

• P type: Indoor, dual radio, 5GHz and 2.4GHz 802.11ax 4x4 MIMO
• 5GHz radio: Four spatial stream Single User (SU) MIMO for up to 2.4Gbps wireless data rate with individual 4SS HE80 (or 2SS HE160) 802.11ax client devices, or with four 1SS or two 2SS HE80 802.11ax MU-MIMO capable client devices simultaneously
• 2.4GHz radio: Four spatial stream Single User (SU) MIMO for up to 1,150Mbps wireless data rate with individual 4SS HE40 802.11ax client devices or with two 2SS HE40 802.11ax MU-MIMO capable client devices simultaneously

That seems to indicate that you can exceed 1gbps by a lot with 2SS devices and 80MHz channels

[DJaquays]

Yeah, my concern was specifically around making sure the switch design (mlag ↔ mlag ↔ stack) would work and that there wasn’t a better/different way to accomplish what I think we want to. The APs will be HPE/Aruba 500 series, which have 2 ethernet ports that can be configured as an LACP group, but in most of our environment, it’s not really worth the added overhead to build it out that way, especially since we don't have the structured cabling to support that today.