Working on a medium sized office network which only has a single PoE switch for WAPs. About 200 users. No copper to the desk… It made sense to buy a second PoE switch to give a bit of redundancy, even if it’s for manually swapping cables in case switch A dies.

Plug in switch, wait for power up and decide to test the manual failover over lunch. Gateway plugged in, flashing lights. WAPs plugged in, flashing lights. Wireless network visible but can’t connect as there’s no DHCP. Swap everything back and we’re back in business.

The switch is unuseable until I’ve installed an app, created an account, onboarded to a “cloud” and configured from my phone.

Oh HP, how you have fallen from the rock-solid days of procurves and have degenerated to the unfortunately named Aruba “Always On”

Rant over.

  • mnvoronin@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Do you mean Aruba “Instant On”? If so, you are withholding some important bit of information.

    They are perfectly usable without an app or cloud console. Will get DHCP IP and you can log in to the local web interface and manage it that way. The caveat is that it has to be VLAN1.

  • ikidd@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I would have packed the fucker back up in the original box and sent it back. Fuck your app, HP. Oh, and fuck your printers, too.

  • DV8@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Like others stated, if it’s an Aruba Instant On switch, it’s easily configurable without any app or registration.

  • thorbot@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    I actually really appreciate just whipping out my phone and hitting “Adopt” when I am setting up new hardware at a site (UniFi stuff). It gets added, updated, and it’s done. Then I can leave and go manage it from the office.