You are setting up an HPE Aruba Networking VIA solution for a company. You have already created a VPN pool with IP addresses for the remote clients. During tests, however, the clients do not receive IP addresses from that pool. What is one setting to check?

In HPE Aruba Networking's role-based access control architecture, network policies, including IP address assignment, are tied to user roles. When a VIA client successfully authenticates to the gateway (formerly controller), it is assigned a specific user role. This role dictates which VLAN the user is placed into. The gateway's internal DHCP server assigns an IP address from a pool that is configured for that specific VLAN. If the VIA clients are not receiving IPs from the intended pool, a common misconfiguration is that the user role assigned to them does not correctly map to the VLAN associated with that IP pool. Why Incorrect Options are Wrong
A. That the pool uses valid, public IP addresses that are assigned to the company VPN client address pools should use private (RFC 1918) IP addresses. The gateway performs Network Address Translation (NAT) for traffic destined for the internet.
C. That the pool uses an IP subnet that is different from any subnet configured on the VPNC While this is a mandatory configuration for correct routing, the direct mechanism for assigning an address from a specific pool to a user is the role configuration.
D. That the pool is referenced in the clients' VIA Connection Profile The VIA Connection Profile contains server and authentication information for the client. The IP address assignment is a server-side function managed by the gateway, not the client profile. --- References
1. Aruba Campus WLAN Design and Deployment Guide (Validated Reference Design), Version 16.10, Page 268, Section: "VIA User Role". The guide states, "The VIA user role must be configured to place the user in the VIA VLAN." This directly confirms that the user role is the mechanism that assigns a user to a VLAN, which is in turn associated with the IP address pool.
2. ArubaOS 8.10.0.0 User Guide, Page 1186, Section: "Configuring Roles and Policies". This section details the configuration of user roles. The user-role command context includes the vlan parameter, which explicitly links a role to a VLAN. This demonstrates that the role is the correct place to check for the VLAN/pool association.
3. Aruba Networks, "Virtual Intranet Access (VIA) Solution Guide", Page 16, Figure 10: "VIA Configuration Flow". This guide illustrates the configuration sequence. Step 5 is "Create User Role," and Step 6 is "Assign VLAN to Role." This workflow highlights that associating the VLAN (and by extension, its IP pool) with the user role is a fundamental step in the VIA setup process.