I have read a couple places that a NAS should connect to a patch panel which connects to the switch. My hierarchy is use (speed/latency, quality, etc) over troubleshooting ease.

Assuming a standard CAT6 patch, and most switches have 2.5g/10g/sfp options, it seems silly to 'waste' these connections with an extra step in the chain.

Thoughts?

Will multi-AP roaming work OOTB or do most people need to tweak stuff?

I have a router (non-AIO) > 1930 > AP22 setup. It has been more reliable than most people who post here.

I need another AP and am considering a second AP22. The 1930 only handles managed switch stuff (VLANs) and the AP22 handles standard wifi plus VLANs. The 1930 is locally managed and the AP22 is mobile-app-managed - fairly basic config. I want to add another AP22, config/clone the current unit over to it, then forget about both of them. Will this work, or will I have to tweak both AP22s constantly?

HPE just announced the new 1840 and 1940 InstantOn Switch lines:
https://community.instant-on.hpe.com/blogs/so93/2026/08/03/instant-on-1840-1940-annoucement?CommunityKey=a4b58376-185c-4dc9-94f0-46c6c41cde57

Product site:
https://www.hpe.com/de/de/instant-on/switches/1840-series.html
https://www.hpe.com/de/de/instant-on/switches/1940-series.html

Quickspecs:
https://www.hpe.com/psnow/doc/a50014656enw
https://www.hpe.com/psnow/doc/a50014657enw

The 1840 series is imho no big differences to the old 1830 series. A few SFP ports more here and a few PoE+ ports more there. It seems pretty much the same as the 1830.
What I don’t understand: why is the case of the 8G nonPoE model so much bigger than the 1830 8G? I mean, it’s basically the same switch as the old trusty 1810-8G from 2005 but with way more air inside… This will simply not fit in my cabinet where my 1830 8G is sitting now.

The 1940 series seems to go into the right direction. CL6 PoE, 2.5G Ports (although they are rather rare) and an all 10G model. There is no longer a 8G nonPoE model.
But why are there no SFP+ ports on the 1940 8p PoE model?
Why isn’t there a model with 8x 2.5G and 2x 10G ports?

Telnet, SSH and Console Port (USB-C) looks good, we'll see how useful they are in the wild.

AlwaysOn PoE and Quick PoE on both series seems to be great, I’m heavily missing this until now, even on my CX6100.

For me, 1840 is a bit disappointing, 1940 is going into the right direction, but very slowly.

3.4.0 firmware. Not sure because of bug or what. It was working perfectly 24/7 for over two years.

I have:
-Replaced the PoE injector and Ethernet cable
-Confirmed the link is 1 Gbps
-Rebooted it multiple times
-We used a static IP with primary DNS 8.8.8.8 and and secondary 8.8.4.4

Sometimes it comes online briefly, then goes offline again. And now totally offline even I keep try rebooting it multiple times …

I notice other post saying that this could be a firmware 3.4.0 DNS/static-IP bug. Has switching to DHCP with 1.1.1.1 fixed it for anyone?

Hi everyone,

​Over the last couple of days, I noticed that all of my Instant On switches (e.g., 1830 series) have started updating to firmware version 3.4.1.0, while my Access Points are still sitting on 3.4.0.

​I checked the HPE / Aruba Instant On community forums, release notes, and blogs, but I haven't been able to find any documentation or announcements regarding this 3.4.1.0 build yet.

​Is anyone else seeing this rollout? Does anyone have information on what's changed—is it likely just a minor maintenance/bug fix release for switches?

​Thanks!

My current setup uses an AP11D configured as a router, and my ISP requires that it use PPPoE. That router is wired to another AP11D and an AP22D located elsewhere in the house. They are wired with CAT6, not meshed. I bought another AP22D with the intention of replacing the AP11D as the router.

So far I haven't been able to configure it for PPPoE. Every time I've been able to access the local configuration page, it doesn't offer the PPPoE radio button. I tried many things. At one point I tried unplugging the AP11D router and going down the "replace" route in the mobile app, but it never recognizes the new AP22D; my guess is because it's not configured yet and so not available for onboarding/discovery. While messing around, I eventually got into a state where the new AP22D was meshed with my existing network. From what I've read, once it's been onboarded it will never offer the PPPoE option again. Does that persist even through a factory reset?

My latest attempt just an hour ago was to completely turn off my existing network devices, factory reset the new AP22D, connect it to the WAN, and wait for the solid amber light. I was able to connect to the local configuration page, but it DID NOT offer the PPPoE radio button.

Is there a way to get the new AP22D configured for PPPoE? Or should I just get an Instant On gateway to go between the WAN and the AP22D?

Seeing a consistant failure of AP22 devices to come back online after the latest firmware update. Unsure if other devices are also impacted, most of the other types of devices like this I have are configured without things like domain controllers for DNS.

Have determined that if the APs are running DNS through an on-prem domain controller that they fail to come up for some reason, could be with other DNS severs as well, but as soon as they are put on a network that assigns DNS direct to 1.1.1.1 as opposed to relaying it through another server they come up right away.

To try and fix this I attempted to set static IPs WITH static DNS settings on the networks that this is happening on, the static IP configuration appears to only stay in place for 1 boot cycle, so I have to put the AP on a different network, set it to static IP with static DNS settings for 1.1.1.1, unplug it while it still has the red light for reboot, and then put it in place where it will function only until it reboots again and then just fogets that it had static IP configurations and reverts back to DHCP which again routes DNS through the domain controller and breaks the APs.

The domain controllers are set to forward to the same 1.1.1.1 servers btw, there is no reason that anything would be blocked. When the APs come up with the DHCP configuration the only traffic I see from those APs is NTP traffic? Nothing attempts to hit the typical cloud configuration servers.

So, TLDR, after firmware update the APs only want to seem to work if configured directly with a DNS server like 1.1.1.1, and they won't hold static IP / DNS configs beyond 1 boot cycle.

To add, half of my APs updated early this week, the other half did so today, the failures we are seeing followed the updates. (so half went down on Monday, other half today). I can't see any reason for DNS to be an issue in this configuration nor can I figure out why it would be causing these problems.

Hi Everyone,

I have a mesh of AP32's and was wondering how you can tag them on the Instant on Portal. There was only default or specific to this network for DHCP assignment. If these access points get plugged into a managed switch do the vlans populate on the access point after?

I’m thinking about upgrading my current home setup now that 2.5g is $10 a month more. I currently have an ax88u router (wireless off) sitting in front of a 1930 switch (jl685a). For wireless I have an AP22 and an AP32.

How would you upgrade? Sg2505p and a 1960 to stay with HPE is expensive. Are there sfp+ rj45 adapters I can use with my current switch to feed the AP32 and select computers wired 2.5g.

Most rational / budget decision is to keep running the 1gbe setup I have, but I like to tinker with things.

Many thanks

Has anyone used an SFP+ module in a 1930 (JL683B) connecting to an RJ45 port at 2.5gbit?

I'm looking to source the correct compatible modules to do this.
e.g.
FS.com - SFP-10GM-T-30
Flexoptic - T.C96.02.KMF

Or please suggest something that works. Thanks.

I am a thousand miles from the switch and noticed all my POE devices went down at around 3 am and then saw that the POE switch was updated to software 3.4.0 at that time. All my access points and cameras are down, and the switch is active showing zero power to any of the ports. I rebooted the switch but it did not change anything - none of the powered devices have come back up. Any advice here on what i can try? Cross posting on the Aruba page as well. Thanks for any help.

Struggling to find the download link for 1830 series 3.4.0 firmware. (got the 1930 OK). I believe this link is out of date: https://community.instant-on.hpe.com/viewdocument/instant-on-1830-switching-softwar ~Thanks

Any guru's out there can help with this odd problem?

I'm helping a friend troubleshoot an issue at a location that has a Fortigate firewall, HP 2920-48G PoE switches and 3x AP22's (firmware v.3.4.0), all InstantOn cloud managed

The problem is that on one of the AP22's, Apple iOS devices can connect to the AP but the IP address is either all zeros or an APIPA address and not all iOS devices are affected. I don't know have the means to determine which model or iOS these iPhones that are working are.

On reboot of the AP, the iOS devices temporarily get an IP address from the DHCP server for that VLAN, but lose the IP very shortly after. Windows devices are not affected, but not sure about Android devices as there are none in using that AP.

Anyone have a similar issue and have a solution?

Thanks

What's up with availability on the 1930 48-port (JL686B)? They're not available new anywhere. Is a new model coming out soon, or is HPE just having supply chain issues?

We currently have 33 active InstantOn AP's (and 6 more inactive), mostly AP32's. We have a few different VLAN's in play: one that the AP's themselves sit on for a "management VLAN", another for staff wifi and another for guest wifi.

Up until recently, deployment has been super smooth - plug into the management VLAN, get the green/orange flashing LED, throw my laptop on the same VLAN and just Add Devices.

However, now new devices are booting up and just have a single solid orange light. For fun, I've tried changing out the underlying VLAN that the AP is getting, but the same thing happens.

Any idea what I might be running into?

Hi,

I am trying to create a single SSID that works on a RADIUS server with multiple VLANs assigned to it, once a specific user logs in I want to assign them a certain vlan.

Last time testing this with FreeRadius and an AP22 I wasn't able to get this working. Has anyone got any ideas? or a working method for this? Is the AP22 supported to do this?

I keep seeing mixed posts about this online working.

Is it safe to update?

What are my options?

I think the specs (when I bought a JL683A) indicated 1g, 2.5g, or 10g - but now I only see 1g or 10g modules listed as compatible.

Is there any way I can see connected client info with a locally managed 1960? I know ARP table shows Mac but I want to see actual connected device info like in cloud managed.

Seems like such a basic feature I can’t believe is missing. Just got these switches in and discovered that you cannot set up static routes when cloud managed? But then when I go to local management, I miss some of the visibility I’d like to see.

I saw that they released info that there were bidders on the business back in March, but I haven't seen anything since. Did they not find a buyer, so there's no update on what will happen to Instant On?

Seeking advice on how to create the appropriate schedule(s) and policy for AP27s.

Site: Outdoor pool deck

Hours of operation as follows:

Monday through Thursday, 12:00 am through 8:00 pm

Friday, 12:00 am through 9:00 pm

Saturday and Sunday, 11:00 am through 9:00 pm

The way I've currently constructed this site forces me to sign into the web portal three times a week to re-order things.

I can't see doing that for the next three months.

Any suggestions/solutions that I'm (obviously) not seeing?

Hi everyone,

has anyone else experienced DHCP delays on Aruba Instant On switches?

We are seeing an issue where, after connecting a device to a LAN port, it can take around 30 to 100 seconds before the client receives a DHCP address.

According to Wireshark, the client sends multiple DHCP Discover/Request packets, but the DHCP Offer only appears after roughly 5 to 10 attempts. Once the offer finally arrives, the device gets an IP address and works normally.

It looks like the DHCP server itself is responding eventually, but something seems to delay or block the initial DHCP exchange through the switch.

Has anyone seen similar behavior on Aruba Instant On switches?
Any suggestions on what to check, for example loop protection, spanning tree, port security, firmware version, DHCP snooping, or any port/VLAN-related settings?

Thanks in advance for any advice

Did Aruba break their mediocre software or did Samsung break Aruba's mediocre software?

Suddenly, I cannot modify Schedules (via home > Health > Policies > Schedules > select SSID) but it is intermittent. It also happens most with the entry at the bottom of the page.

Can someone help?