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:

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:

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!

@Herman Robers

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!

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:

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!

@Herman Robers

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!

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:

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!

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!

@Herman Robers

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!

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:

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!