Wired Intelligent Edge

Is it possible to set a static IP for an interface in the 6200M, using the Aruba "New Central" web GUI, or does that need to be done in the CLI?  

This was easy for me to do in Classic Central, but I can't figure out where to do it in "new" Central, without resorting to CLI.   The switch defaults to getting a DHCP-assigned IP address. 

Thanks!

-------------------------------------------

For new Central configuration of the IP address, you would need to create a VLAN first and get that applied. You would normally put that on Site level so all switches in the site can share the same VLAN(s).

Then on the device level, you create an override on the VLAN, then enable L3, and then you see a field to enter the IP:

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

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.
------------------------------

Thank you very much! "Enable L3" was the part I missed!

-------------------------------------------

Original Message:
Sent: Feb 23, 2026 02:26 AM
From: Herman Robers
Subject: Setting Static IP on a 6200M Interface in "New Central"

For new Central configuration of the IP address, you would need to create a VLAN first and get that applied. You would normally put that on Site level so all switches in the site can share the same VLAN(s).

Then on the device level, you create an override on the VLAN, then enable L3, and then you see a field to enter the IP:

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

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.
------------------------------

@HR-abaef5

What is the best way to move management/Central traffic off the default untagged (native) VLAN 1, and sinkhole untagged/native VLAN 1 traffic?

I have an uplink/trunk interface that carries multiple tagged VLANs to the switch. I can add those under "allowed VLANs," but how do I specify which of those allowed VLANs the switch uses for its management/Central traffic?

Thanks!

-------------------------------------------

Original Message:
Sent: Feb 23, 2026 02:26 AM
From: Herman Robers
Subject: Setting Static IP on a 6200M Interface in "New Central"

For new Central configuration of the IP address, you would need to create a VLAN first and get that applied. You would normally put that on Site level so all switches in the site can share the same VLAN(s).

Then on the device level, you create an override on the VLAN, then enable L3, and then you see a field to enter the IP:

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

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.
------------------------------

Just make sure you have valid DNS, IP, default gateway in the VLAN that you want to have for management/communication to Central, then remove VLAN 1 from all ports. It may be needed to configure a static IP on that VLAN as when VLAN 1 is active, it has DHCP client by default and the switch doesn't allow DHCP enabled on more than one interface (which I think is resolved or will be resolved to make this VLAN switch easier).

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

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: Feb 23, 2026 09:07 PM
From: technocrat
Subject: Setting Static IP on a 6200M Interface in "New Central"

@HR-abaef5

What is the best way to move management/Central traffic off the default untagged (native) VLAN 1, and sinkhole untagged/native VLAN 1 traffic?

I have an uplink/trunk interface that carries multiple tagged VLANs to the switch. I can add those under "allowed VLANs," but how do I specify which of those allowed VLANs the switch uses for its management/Central traffic?

Thanks!

Thanks.  For anyone viewing this, here's what I did to get this working in New Central:

1. Assigned a static IP to the VLAN I want to use for management, per the directions above. 
2. Set up an interface for trunking.  Set "Native VLAN" to an unused sinkhole VLAN that goes nowhere if you want to dump un-tagged traffic.  Set "Allowed VLANs" to include all VLANs you want on your trunk including the management VLAN, plus the sinkhole VLAN. 
3. System > DNS Server.  Add a DNS server, 8.8.8.8, or as desired. 
4. Routing and Overlays > Static Routing > Add and IP route.  Be sure "Create as a local profile" is selected, or you will not see the right options.  Set Destination 0.0.0.0/0, and select "specify outgoing interface" and set it to the VLAN you want to use for management. 

Done!

-------------------------------------------

Original Message:
Sent: Feb 23, 2026 09:07 PM
From: technocrat
Subject: Setting Static IP on a 6200M Interface in "New Central"

@HR-abaef5

What is the best way to move management/Central traffic off the default untagged (native) VLAN 1, and sinkhole untagged/native VLAN 1 traffic?

I have an uplink/trunk interface that carries multiple tagged VLANs to the switch. I can add those under "allowed VLANs," but how do I specify which of those allowed VLANs the switch uses for its management/Central traffic?

Thanks!

Just to add , you may setup a port profile for uplink and apply an interface profile at the site to ensure all devices coming online can get same desired uplink config automatically without needing to configure this on a per device basis.

 We are working to update documentation and will share the updated doc once available.

------------------------------
-Mubeesh
------------------------------

Original Message:
Sent: Feb 25, 2026 10:20 AM
From: technocrat
Subject: Setting Static IP on a 6200M Interface in "New Central"

Thanks.  For anyone viewing this, here's what I did to get this working in New Central:

1. Assigned a static IP to the VLAN I want to use for management, per the directions above. 
2. Set up an interface for trunking.  Set "Native VLAN" to an unused sinkhole VLAN that goes nowhere if you want to dump un-tagged traffic.  Set "Allowed VLANs" to include all VLANs you want on your trunk including the management VLAN, plus the sinkhole VLAN. 
3. System > DNS Server.  Add a DNS server, 8.8.8.8, or as desired. 
4. Routing and Overlays > Static Routing > Add and IP route.  Be sure "Create as a local profile" is selected, or you will not see the right options.  Set Destination 0.0.0.0/0, and select "specify outgoing interface" and set it to the VLAN you want to use for management. 

Done!

Original Message:
Sent: Feb 23, 2026 09:07 PM
From: technocrat
Subject: Setting Static IP on a 6200M Interface in "New Central"

@HR-abaef5

What is the best way to move management/Central traffic off the default untagged (native) VLAN 1, and sinkhole untagged/native VLAN 1 traffic?

I have an uplink/trunk interface that carries multiple tagged VLANs to the switch. I can add those under "allowed VLANs," but how do I specify which of those allowed VLANs the switch uses for its management/Central traffic?

Thanks!