When access points on VLAN 1000 can’t obtain addresses, check for a Layer 3 interface on the connected Aruba CX switch. An SVI in the AP subnet gives the switch a local routing presence, allowing DHCP requests to reach the server through relay configuration.

Multiple Choice

Which action may help fix DHCP issues on a pair of Aruba CX switches with APs connected to VLAN 1000?

DHCP relay needs a Layer 3 interface on the switch for the VLAN that the clients (APs) are in. Without an SVI for that VLAN, the switch has no local gateway or routing presence to forward DHCP requests to a DHCP server, so clients can’t obtain an IP. Adding a switched virtual interface for the subnet 10.102.39.0/24 on the Aruba CX 6100 that the APs are connected to gives the switch a proper L3 endpoint in that VLAN. With this SVI in place, the switch can route DHCP Discover messages toward the DHCP server (and you can configure the relay to the server’s IP on that SVI). This creates the necessary path for DHCP traffic and is a common first step to fix DHCP issues in VLAN-based deployments. The other options either reference commands that aren’t applicable in this context or rely on relay settings without a corresponding L3 interface in the APs’ VLAN, which would not be effective until the SVI exists.

When access points connect through an Aruba CX 6100 switch, a DHCP problem can look like a server issue, a trunk issue, or a relay issue. Sometimes the missing piece is more basic: the switch has no Layer 3 interface in the VLAN where those APs live.

That distinction matters in campus networks. A VLAN can carry traffic at Layer 2 without the switch having an IP address or routing role in it. But DHCP relay requires the switch to act at Layer 3. If the APs are on VLAN 1000 and the switch has no SVI for that VLAN, it lacks the local routing presence needed to forward their DHCP requests to a server on another subnet.

VLAN membership is not the same as a gateway

A VLAN groups devices into a shared Layer 2 broadcast domain. When an access point sends a DHCP Discover message, that request is broadcast within its VLAN. A DHCP server on the same subnet may hear it directly. If the server is elsewhere, a Layer 3 device must relay the request across subnet boundaries.

That device is typically a router or a switch with a switched virtual interface, or SVI. An SVI is a logical Layer 3 interface associated with a VLAN. It gives the switch an IP presence in that VLAN and can serve as the clients’ default gateway. It also provides a point where the switch can apply routing and DHCP relay settings.

Think of the VLAN as a room and the SVI as its doorway to the rest of the building. The room can exist without a doorway, but traffic cannot leave it through that switch. Adding a relay address alone doesn’t create the missing doorway.

Why the APs need an SVI on the Aruba CX 6100

In the scenario described, the APs connect to an Aruba CX 6100 and use VLAN 1000. The switch needs an SVI in the AP subnet, identified as 10.102.39.0/24, for DHCP relay to work from that device.

The SVI gives the CX 6100 a Layer 3 interface in the AP VLAN. Once that interface exists, the switch can receive the APs’ broadcast DHCP requests and forward them as unicast traffic toward the DHCP server. The relay function also adds information that helps the server identify the subnet from which the request came, so it can offer an address from the right pool.

This is why adding an SVI is the key first step in this case. A relay setting without a Layer 3 interface in the client VLAN has no suitable local interface from which to handle and forward those requests. The switch may carry VLAN 1000 at Layer 2, yet still be unable to relay DHCP for the APs.

The SVI’s address must belong to the subnet used by the APs. Network teams often choose an address from that subnet for the VLAN gateway, while keeping the DHCP pool and gateway details consistent with the network design. The precise address depends on the site’s addressing plan; the important point is that the interface represents the AP subnet on the switch.

DHCP relay, in plain terms

DHCP begins with a client that has no IP address. It broadcasts a Discover message, asking whether a DHCP server is available. Broadcasts generally stay within their local subnet, so a server on another network won’t receive that message automatically.

A DHCP relay agent bridges that gap. It listens for the local broadcast and forwards the request to a configured DHCP server. The server responds to the relay, which then passes the offer back to the client. For APs, this process is often invisible once it works: the access point starts up, gets an address, and contacts the services it needs.

But relay isn’t magic. It depends on a working Layer 3 interface in the client VLAN, a reachable DHCP server, and a valid address pool for the AP subnet. If any of those pieces is missing, the AP may sit without an address even though the cable is connected and the VLAN appears to be present.

What to check after adding the interface

Adding an SVI addresses an important gap, but it’s one part of a larger DHCP path. A useful troubleshooting sequence follows the traffic from the AP to the server and back:

  • Confirm that the AP-facing port carries VLAN 1000 as intended.

  • Check that VLAN 1000 is present and active on the Aruba CX 6100.

  • Verify that the SVI is configured with an address in 10.102.39.0/24 and is operational.

  • Configure or confirm DHCP relay toward the server’s IP address.

  • Check routing from the switch to the server, including any return route or access-control rule.

  • Confirm that the DHCP server has a scope for the AP subnet and that addresses remain available.

This sequence helps separate a VLAN problem from a routing problem. If the AP’s request never reaches the SVI, review the port and VLAN path. If the relay forwards the request but no offer returns, check the server scope, routing, and any filtering in between.

It’s also worth checking the client-facing details. The AP must use the expected VLAN, and the DHCP server must associate the relay request with the correct subnet. A small mismatch—such as a scope for a different network—can produce the same symptom as a failed relay: no usable address for the device.

Why a VSX setting or relay command may not solve it alone

Aruba CX deployments may use VSX for redundancy, and keeping relevant configurations consistent between peers is important. Still, VSX synchronization doesn’t replace the need for a Layer 3 interface in the VLAN where clients send their DHCP requests. If the CX 6100 connected to the APs lacks an SVI for VLAN 1000, changing synchronization settings on a VSX pair won’t create that local Layer 3 endpoint.

Likewise, a relay address is only useful when the switch has a valid interface and routing context for the client subnet. Configuring a destination server address can tell the switch where to forward requests, but it cannot by itself make an otherwise Layer 2-only VLAN capable of relaying them.

This distinction is easy to miss because VLANs and relay settings often appear side by side in a configuration. Yet they do different jobs. VLAN membership handles Layer 2 delivery; an SVI provides Layer 3 presence; DHCP relay moves requests between subnets. Each part depends on the others.

A small interface, a much clearer path

When APs on VLAN 1000 cannot obtain DHCP addresses through an Aruba CX 6100, check whether that switch has an SVI in the AP subnet, 10.102.39.0/24. Adding the SVI gives the switch the Layer 3 presence needed to support DHCP relay. From there, confirm the relay destination, routing, VLAN membership, and DHCP scope.

That approach keeps troubleshooting grounded in the traffic path instead of relying on a single command as a cure-all. The AP broadcasts locally; the SVI gives the switch a place to receive and route that traffic; the relay forwards it to the server. Once those roles fit together, the DHCP exchange has a clear route—and the AP can get on with connecting to the network.