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.

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

    I’ve been a big proponent of HP Procurve switches in the enterprise but if cloud connectivity is going to be a requirement then I’d rather just go in with Cisco/meraki.

    Avoiding the confusing licensing/connectivity requirements were why I used procurve in the first place