Cloud Managed Networks

Hi Airheads,

We are currently executing a large-scale migration project from AOS8 to AOS10 for a client environment. During the infrastructure alignment, we encountered a challenge regarding the DHCP Relay Option 82 configuration.

In the legacy AOS8 (Architecture), we utilized a custom XML file and interface-level commands as follows:

<response-element class="" ng-version="0.0.0-PLACEHOLDER"></response-element>

ip dhcp option-82 <xml-file-name-in-flash>
!
interface vlan 25
  option-82

<response-element class="" ng-version="0.0.0-PLACEHOLDER"></response-element>

As we transition to AOS10 and Aruba Central orchestration, we've noticed that the CLI-based custom XML injection for Option 82 is handled differently. We are looking for the best practice to achieve the same granularity of circuit-id/remote-id insertion within the AOS10 Gateway profile.

Our key questions are:

1. How can we replicate the custom DHCP Option 82 format in Aruba Central (AOS10 Gateway Group/Device level)?

2. Is there a specific UI workflow or Advanced Settings (JSON/CLI Snippet) required to define the Option 82 sub-options in AOS10, given that the local flash XML method is no longer applicable?

3. Does AOS10 support the same level of flexibility for Circuit-ID customization per VLAN as AOS8 did?

We would appreciate any insights or reference documentation from those who have successfully implemented high-density DHCP Relay configurations in an AOS10 production environment.

there is DHCP option 82 with XML support for AOS10 APs. And from the online documentation it seems it does support circuit-id.

I have not done it myself but hopefully this will provide a starting point.