Configuring the management VLAN statement in 2930F can be a bit confusing. Check this post if that may be the same in your case.
" If you set a management-vlan that vlan is not routed, and is only accessible by other devices on that vlan. It's designed to mimic the behavior of a physical oobm port.
It sounds like that's not the actual desire here [NOTE: This is in the original message], so just get rid of the management-vlan statement. You can lock it down as necessary using "ip authorized-managers" statements (switch management ACLs)"
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Oct 18, 2024 07:20 AM
From: Bernard Kolvesi
Subject: Aruba 2930F Management
Hello,
I have several Aruba switches including 3810M and 2930F. I went to configure management network for the switches including 3810M using oobm port and also for 2930F using defined management-vlan. When I try to add 3rd 2930F to management network, configuration went fine but I can not ping it nor access it with SSH. I tried another 2930F switch, but same issue. Anyone had same issue?
Kind regards.