This article explains how to onboard HPE Aruba AOS-CX and Aruba AOS-S switches as Virtual Edge Nodes for policy enforcement.
This article covers onboarding the switches in Cloud Control Center. The switch commands, Access Policy configuration, and supported switch models are covered in separate articles:
| Topic | Article |
|---|---|
| Access Policy configuration | Configuring Access Policy for Aruba Switches |
| Switch commands for AOS-CX | Aruba AOS-CX Configuration Commands for Virtual Edge Node (VEN) Onboarding |
| Switch commands for AOS-S | Aruba AOS-S Configuration Commands for Virtual Edge Node (VEN) Onboarding |
| Supported switch models | Hardware Compatibility Matrix |
Overview
Elisity supports HPE Aruba AOS-CX and Aruba AOS-S (ArubaOS-Switch) switches as Virtual Edge Nodes for endpoint discovery, traffic visibility, and policy enforcement. The Virtual Edge detects the platform automatically from the switch, so no vendor selection is required during onboarding. Endpoint identity and Policy Group classification continue to use the standard Elisity model. Enforcement uses Access Policy, a platform-specific policy configuration that Elisity translates into Aruba user roles and policies. Access Policy is configured separately from, but alongside, microsegmentation policies in the Policy Matrix. See Configuring Access Policy for Aruba Switches.
Aruba Central is not supported for this integration. A Virtual Edge VM connects directly to each Aruba switch.
Terminology: Cloud Control Center labels the ordered Access Policy rule set an Access Policy Security Profile. It contains the ordered rules that Elisity translates into an Aruba AOS-CX port-access policy or an Aruba AOS-S user policy. This article refers to it as the Access Policy rule set except when identifying the exact page, field, or control in the interface.
How It Works
The Virtual Edge VM manages each Aruba switch directly over SSH. It discovers the switch, programs the Elisity configuration, and polls operational state. The switch sends MAC authentication requests and RADIUS accounting to the Virtual Edge, which terminates RADIUS for the switches it manages. When an endpoint is classified into a Policy Group, the Virtual Edge sends a Change of Authorization to apply the matching Aruba role. The switch exports flow telemetry to the Virtual Edge, which sends it to Cloud Control Center.
Prerequisites
Complete the following before onboarding a switch.
Switch Requirements
Before deployment, check the Hardware Compatibility Matrix, the source of truth for supported models and minimum switch software.
| Switch Family | Models | Minimum Switch Software |
|---|---|---|
| Aruba AOS-CX | HPE Aruba 6200, 6300, and 6400 CX Series | 10.15 or later (6200), 10.11 or later (6300, 6400) |
| Aruba AOS-S | HPE Aruba 2530, 2930, and 3810 Series | 16.11.0021 or later (earlier builds fail onboarding) |
Virtual Edge and Cloud Control Center Requirements
| Requirement | Details |
|---|---|
| Virtual Edge VM | Deploy a Virtual Edge VM using the Virtual Edge Hypervisor Deployment Guide, standalone or in a VE Group (see Virtual Edge Groups). Aruba switches can be managed only by a Virtual Edge VM. In a VE Group, every Virtual Edge must reach every Aruba switch that may be assigned to it. |
| Access Policy enabled globally and on the Policy Set | Enable Access Policy in Settings > System > Advanced and on the Policy Set for the Aruba switches before onboarding. A switch onboarded while the global setting is disabled reports a Degraded status. See Enabling Access Policy. |
| Time source (NTP) | A Network Time Protocol (NTP) source reachable from the Virtual Edge VM and every switch. Change of Authorization requests carry a timestamp, so a switch whose clock is not synchronized can reject the role changes the Virtual Edge sends. |
| Configuration management exclusion | Exclude the Elisity-managed configuration from any configuration-management system that pushes switch configuration, so it is not removed or overwritten. |
Connectivity Requirements
Configure routing and firewall policy to permit the following connections; for general Elisity connectivity requirements, see Platform Connectivity Requirements. Both switch families use the same connections; Aruba AOS-CX sends flow telemetry as IP Flow Information Export (IPFIX) and Aruba AOS-S as sFlow.
| Source | Destination | Protocol and Port | Purpose |
|---|---|---|---|
| Virtual Edge VM | Aruba Virtual Edge Node | TCP/22 | Switch discovery, configuration, and operational polling |
| Virtual Edge VM | Cloud Control Center | TCP/443 | Registration, policy state, identity, telemetry, and management |
| Virtual Edge VM | Aruba Virtual Edge Node | UDP/3799 | Change of Authorization |
| Aruba Virtual Edge Node | Virtual Edge VM | UDP/1812 | MAC authentication requests |
| Aruba Virtual Edge Node | Virtual Edge VM | UDP/1813 | RADIUS accounting and endpoint attachment updates |
| Aruba Virtual Edge Node | Virtual Edge VM | UDP/9996 | IPFIX flow telemetry (Aruba AOS-CX) or sFlow flow telemetry (Aruba AOS-S) |
Switch Preparation
| Requirement | Aruba AOS-CX | Aruba AOS-S |
|---|---|---|
| Switch credentials | A dedicated account in the administrators group (privilege 15). If Terminal Access Controller Access-Control System Plus (TACACS+) command authorization applies, allow the commands in Aruba AOS-CX Configuration Commands for Virtual Edge Node (VEN) Onboarding. | A dedicated account with manager-level privileges. If TACACS+ command authorization applies, allow the commands in Aruba AOS-S Configuration Commands for Virtual Edge Node (VEN) Onboarding. |
| SSH enabled | On the default Virtual Routing and Forwarding (VRF) instance, with the switch reachable on a routed in-band IP address in the default VRF. The out-of-band management interface (mgmt VRF) is not supported. |
IPv4 SSH. Onboard the switch on its primary in-band management IP address. |
| DHCP snooping | Not required. | Enabled globally and on the access VLANs. Onboarding does not complete until DHCP snooping is operational. |
Before enabling DHCP snooping, trust every uplink toward the DHCP server, including redundant uplinks; an untrusted uplink drops DHCP replies and clients on that switch get no address.
If an Aruba AOS-CX switch still carries Aruba Group Based Policy (GBP) configuration from Elisity, decommission it and contact Elisity Support before onboarding it again.
What Onboarding Changes on the Switch
Onboarding configures the Elisity RADIUS server and the initial role elisity_default_role on each switch, and MAC authentication and flow telemetry on User Network Interface (UNI) ports (access ports; see Criteria for Automatic Port Configuration). The initial role keeps unclassified devices online, so do not remove or rename it.
Enabling MAC authentication briefly interrupts each connected endpoint once, so onboard during a planned change window.
For the exact commands, see Aruba AOS-CX Configuration Commands for Virtual Edge Node (VEN) Onboarding or Aruba AOS-S Configuration Commands for Virtual Edge Node (VEN) Onboarding.
Caveats and Limitations
How Enforcement Differs on Aruba Switches
On Aruba switches, Elisity enforces policy with Access Policy instead of the Policy Matrix. Each source Policy Group gets one ordered Access Policy rule set, which Elisity programs on the switch as an Aruba user role and assigns to each endpoint through RADIUS. Rule destinations are static Policy Groups or IP addresses. An Access Policy is an allowlist: traffic from the device that no rule allows is dropped. Devices in a Policy Group with no Access Policy keep elisity_default_role, which allows all traffic. Standard Policies and Security Profiles do not apply to Aruba Virtual Edge Nodes. See How Access Policy Works in Configuring Access Policy for Aruba Switches.
Operational Behavior and Limitations
| Behavior | Details |
|---|---|
| Virtual Edge failover | If the active Virtual Edge in a VE Group fails, another Virtual Edge takes over the switch; allow several minutes for it to rebuild endpoint sessions before evaluating role assignments. |
| Existing Aruba roles | Roles and policies not created by Elisity, such as customer-managed 802.1X, voice, or ClearPass roles, stay in place. Elisity does change shared authentication settings. On Aruba AOS-CX, it binds global MAC authentication to the Elisity RADIUS server group and places MAC authentication ahead of 802.1X on each UNI. On Aruba AOS-S, it sets the global initial role, the MAC authentication method, and the MAC address format. If another RADIUS server, such as ClearPass, already performs MAC authentication on these switches, decide which system owns MAC authentication before onboarding. |
| Wireless clients | Ports with a wireless access point neighbor are classified as NNI, so wireless clients behind the access point are not discovered or enforced by the switch. |
| MAC addresses per port (Aruba AOS-S) | Each UNI authenticates up to 32 MAC addresses. Additional endpoints on the same port, such as devices behind an unmanaged switch or hub, are not authenticated, lose network access through that port, and do not appear in Cloud Control Center. |
| Endpoint discovery requires enforcement (Aruba AOS-S) | Aruba AOS-S discovers endpoints only through MAC authentication, so keep Enable Policy Enforcement selected. With it cleared, the Virtual Edge Node discovers no endpoints, and only sFlow continues. |
| Voice VLAN access ports (Aruba AOS-S) | A port tagged in one VLAN and untagged in another stays a Network-to-Network Interface (NNI), with no MAC authentication or endpoint discovery, until a host or IP phone neighbor is detected over Cisco Discovery Protocol (CDP) or Link Layer Discovery Protocol (LLDP), or until you set the port to UNI. See Criteria for Automatic Port Configuration. |
Adding an Aruba Virtual Edge Node in Cloud Control Center
Onboard during a planned change window; see Switch Preparation.
Step 1. Navigate to Edge Management > Virtual Edge Nodes, select the Virtual Edge Nodes tab, click + Add Virtual Edge Node, and select Add Single Virtual Edge Node to open the Virtual Edge Node Deployment Wizard. To onboard several switches at once, select Add Multiple Virtual Edge Nodes; see Bulk Onboarding Virtual Edges and Virtual Edge Nodes.
Step 2. Select the VE Group or standalone Virtual Edge that manages the switch. Standalone Virtual Edges are not supported when onboarding multiple Virtual Edge Nodes.
Step 3. Click Next, then select Switch as the Virtual Edge Node type.
Step 4. Enter the basic configuration for the switch.
| Field | Description |
|---|---|
| Management IP | The in-band management IP address described under SSH enabled in Prerequisites. Do not use a Hot Standby Router Protocol (HSRP), Virtual Router Redundancy Protocol (VRRP), Gateway Load Balancing Protocol (GLBP), secondary, or virtual IP address. |
| Description | An optional description for the Virtual Edge Node. |
| Set Switch Credentials | Required. Select Global Credentials and choose a credential set, or Custom Credentials and enter the username and password. Credential sets are created in Edge Management > Edge Settings > Global Credentials; see Managing Virtual Edges and Virtual Edge Nodes. The account can be local, TACACS, or RADIUS, with the privilege level in Prerequisites. Usernames are alphanumeric and may contain only _, +, \, /, and -; passwords cannot contain whitespace. |
Step 5. Optionally, expand Advanced Settings; see Advanced Settings.
Step 6. Inherit the Site Label and Distribution Zone from the parent Virtual Edge, or assign them to the Virtual Edge Node directly.
| Field | Description |
|---|---|
| Site Label | Select Inherit from VE, or Assign Manually and choose a Site Label. The Site Label assigns the node to a Policy Set; see Policy Sets and Site Labels. |
| Distribution Zone | Select Inherit from VE, an Access or Core Distribution Zone, or an Isolated Distribution Zone (the list depends on the selected Site Label). See Assigning Distribution Zones to Virtual Edge Nodes in Distribution Zones. |
Step 7. Click Next to open the summary. Click Edit on any section to return to it and change the configuration. When the summary is correct, click Finish. Onboarding begins immediately: progress shows in the Activity Panel, and the Virtual Edge Node and its status appear in Edge Management > Virtual Edge Nodes. See Checking the Status of a VEN Onboarding.
Advanced Settings
Expand Advanced Settings for the less common options.
The wizard lists every setting because the switch vendor is not known until the switch registers. The following table shows how each one applies to Aruba switches.
| Setting | Aruba switches |
|---|---|
| Enable Endpoint Discovery | Discovers and tracks endpoints on UNI ports. On Aruba switches, the ports with Endpoint Discovery are also the ports that receive MAC authentication. Aruba AOS-CX discovers endpoints through RADIUS accounting and IP client tracking; Aruba AOS-S discovers them through MAC authentication only. When it is cleared, no port gets discovery or MAC authentication until you configure ports in Port Configurations on Virtual Edge Nodes. |
| Enable Flow Telemetry | Sends flow records from the switch to the Virtual Edge for traffic visibility in Cloud Control Center: IPFIX on Aruba AOS-CX and sampled sFlow on Aruba AOS-S. On Aruba AOS-S, sFlow is sampled only on the ports where Endpoint Discovery is enabled, so Flow Telemetry needs Endpoint Discovery. See Endpoint Discovery and Flow Telemetry. |
| Enable External Endpoint Discovery Management (Cisco Only) | Does not apply to Aruba switches; leave it cleared. If it is selected, Cloud Control Center clears it when the switch registers and records an activity event. Clearing it also turns off Endpoint Discovery, so turn Endpoint Discovery back on in Port Configurations on Virtual Edge Nodes. See Configuring External Endpoint Discovery Management for Virtual Edge Nodes. |
| Enable Policy Enforcement | Programs Access Policy on the switch: the Elisity RADIUS server, MAC authentication on UNI ports, and the Aruba roles and policies for each Policy Group. Enabled by default. Once the Virtual Edge Node is in service, it can be cleared only after decommissioning. Aruba AOS-CX: clearing it onboards the switch in Discovery Only mode: endpoint discovery and flow telemetry, but no Elisity RADIUS, MAC authentication, or roles. Aruba AOS-S: clearing it stops endpoint discovery, because Aruba AOS-S discovers endpoints only through MAC authentication. For the Aruba AOS-S planning points, including the 32 MAC addresses per UNI and voice VLAN ports, see Caveats and Limitations. |
| Enable SXP Peer-Only Mode | Has no effect on Aruba switches; nothing is sent to the switch. Cloud Control Center accepts it only when Enable Policy Enforcement is cleared, so leave it cleared. |
| Enable Aggregation Role | Does not change the switch configuration on Aruba switches. It only changes how Cloud Control Center lists the node, as an aggregation switch. Leave it cleared. |
| Enable NAT Support | Sets separate inside and outside management IP addresses for a switch behind NAT. Applies to both families. See Virtual Edge Node NAT Support. |
| Enable Additional Flow Exporters | Not supported on Aruba switches. If exporters are added, Cloud Control Center removes them when the switch registers, and the switch exports flows only to the Virtual Edge. |
| Enable Access Port Discovery Protection | Keeps an access-mode port classified as UNI, with endpoint discovery, flow telemetry, and policy, when a switch or router neighbor is detected on it. Applies to Aruba AOS-CX only. Disabled by default; it starts at the global value in Edge Management > Edge Settings > Advanced Settings. See Configuring Access Port Discovery Protection for Virtual Edge Nodes. Aruba AOS-S: selecting it has no effect; the setting is ignored. |
To configure ports manually, or enable automatic configuration later, leave Endpoint Discovery and Flow Telemetry cleared; see Port Configurations on Virtual Edge Nodes.
Checking the Status of a VEN Onboarding
Onboarding progress is reported in the Activity Panel. Click the notification icon in the top right of Cloud Control Center and select the Activity tab of the Notifications panel; a blue dot on the icon indicates a new update. Filter events by Complete, Error, or In Progress, or click View All Activity for earlier events. As each onboarding step completes, it is marked with a green check mark and a Success status.
If a step fails, a red error indicator appears on it with a brief description of the issue, such as the switch being unreachable.
Once onboarding completes, the Virtual Edge Node shows Online in Edge Management > Virtual Edge Nodes, along with the switch hostname, model, number of discovered devices, and more.
If the switch does not come online, the Virtual Edge keeps retrying registration until you delete the Virtual Edge Node, so it registers on a later attempt once the cause is corrected. Check the following:
| Check | Details |
|---|---|
| Reachability and SSH | The Virtual Edge reaches the switch over SSH (TCP/22), and every connection in Connectivity Requirements succeeds. |
| Credentials | The account exists on the switch with the privilege level in Prerequisites, and matches the credentials entered in Cloud Control Center. |
| Management IP (Aruba AOS-CX) | The switch was onboarded on a routed in-band IP address in the default VRF. If it was onboarded on the out-of-band mgmt address, delete the Virtual Edge Node and onboard it again. |
| Switch model and software | The switch is a supported model running at least the minimum software in Switch Requirements. |
| DHCP snooping (Aruba AOS-S) | DHCP snooping is enabled and operational, with every uplink toward the DHCP server trusted. |
Port Configurations on Virtual Edge Nodes
Port configuration controls whether each port runs Endpoint Discovery and Flow Telemetry, which on Aruba switches also decides where Access Policy is enforced. Each port uses one of two configuration types:
- Automatic (default): Elisity enables or disables Endpoint Discovery and Flow Telemetry on the port based on the Criteria for Automatic Port Configuration.
- Manual: you enable or disable Endpoint Discovery and Flow Telemetry on the port yourself. You can return a port to Automatic at any time.
The Endpoint Discovery and Flow Telemetry settings in the onboarding wizard turn each feature on or off for the whole Virtual Edge Node; they do not change how ports are classified.
Important: On Aruba AOS-CX, Endpoint Discovery controls enforcement as well as visibility. A port with Endpoint Discovery enabled receives MAC Authentication Bypass in addition to client tracking. Disabling Endpoint Discovery on a port does not drop traffic, but it removes MAC Authentication Bypass and the assigned Elisity role along with client tracking, and the port reverts to its underlying switch configuration.
Endpoint Discovery and Flow Telemetry
Endpoint Discovery learns and tracks the devices connected to the switch. Flow Telemetry shows traffic patterns between endpoints. The two switch families collect this data differently.
| Capability | Aruba AOS-CX | Aruba AOS-S |
|---|---|---|
| Endpoint Discovery | RADIUS accounting during MAC authentication, with IP client tracking as a fallback for IP-to-MAC bindings. | RADIUS accounting during MAC authentication, with IP addresses learned through DHCP snooping. An endpoint appears once the switch learns its IP address. |
| Flow Telemetry | IPFIX, applied to each UNI interface in the ingress direction only. AOS-CX does not support egress flow monitoring. | Sampled sFlow on the ports where Endpoint Discovery is enabled. Traffic volumes are estimates, and brief or infrequent conversations may not appear. |
Aruba AOS-CX cannot pin a source interface for flow export. The Virtual Edge therefore collects every routing-interface IP address on the switch and accepts exported flows from any of them.
Criteria for Automatic Port Configuration
The Virtual Edge classifies each port as a UNI or a Network-to-Network Interface (NNI) and programs MAC authentication and flow telemetry only on UNIs, so uplinks, distribution links, and management interfaces stay untouched. Classification, including LLDP and CDP neighbor information, is re-evaluated about every five minutes.
Aruba AOS-CX
Link aggregation group (LAG), tunnel, loopback, VLAN, management, and Virtual Extensible LAN (VXLAN) interfaces, Virtual Switching Framework (VSF) stacking links, and routed (Layer 3) interfaces are not classified. They do not appear in the Port Configuration view and receive no Elisity configuration. Every other interface is classified by the first rule it matches, using Link Layer Discovery Protocol (LLDP) and Cisco Discovery Protocol (CDP) neighbor information, interface type, state, mode, and description:
| Order | Condition | Classification |
|---|---|---|
| 1 | LAG member port | NNI |
| 2 | Description matches a UNI keyword | UNI |
| 3 | Description matches an NNI keyword (default Router, Firewall, and NNI, not case-sensitive) |
NNI |
| 4 | Administratively disabled | NNI |
| 5 | Neighbor is a VMware ESX or ESXi host, advertises the Host capability, or is an IP phone | UNI |
| 6 | Neighbor is a wireless access point | NNI |
| 7 | Neighbor advertises the Router or Switch capability. A neighbor that advertises only the LLDP Bridge capability is not treated as a switch on Aruba AOS-CX, so set such ports to Manual or give them an NNI description keyword. | NNI, except an access-mode port with Access Port Discovery Protection enabled, which stays UNI |
| 8 | Trunk mode | NNI |
| 9 | All remaining ports | UNI |
Neighbors are checked before trunk mode, so a port with an IP phone on a trunk carrying a voice VLAN stays UNI. When a port has several neighbors, the first matching neighbor decides. A port set to Manual in Port Configuration uses its manual Expected Status regardless of these rules.
Aruba AOS-S
Classification uses each port's VLAN membership, LAG membership, administrative state, and LLDP or CDP neighbors. Description keywords and Access Port Discovery Protection do not apply.
| Condition | Classification |
|---|---|
| Tagged in two or more VLANs, only tagged VLANs, or a LAG member | NNI, even if set to UNI manually in Cloud Control Center |
| Tagged in one VLAN and untagged in another, such as an access port with a voice VLAN | NNI until a host or IP phone neighbor is detected, or until you set the port to UNI in Port Configuration |
| Administratively disabled | NNI |
| Neighbor is a host or IP phone | UNI |
| Neighbor is a router, switch, or wireless access point | NNI |
| All remaining ports | UNI |
Existing Flow Telemetry Configurations
Elisity adds its own flow configuration alongside any flow configuration already on the switch. The Virtual Edge does not remove or overwrite customer flow records, exporters, monitors, or sFlow receivers; they remain until you remove them on the switch or through your configuration-management platform.
Aruba AOS-CX. The Virtual Edge creates its own flow record, exporter, and monitor (ElisityFlowRecord, one ElisityFlowExporter-<n> per flow collector, and ElisityFlowMonitor) and applies the monitor in the ingress direction on each UNI interface. AOS-CX accepts one ingress flow monitor per interface, so an interface that already carries a customer monitor reports no Elisity flow telemetry until that monitor is removed. The Virtual Edge retries the interface configuration on a regular interval and applies it once the interface is free. Until then, the Flow Telemetry tab shows the interface with an Expected Status of Enabled and an Actual Status of Disabled.
Some AOS-CX models and software versions reject the IPFIX flow commands. On those switches flow telemetry stays off, while endpoint discovery and Access Policy continue to work: a flow configuration failure never blocks Access Policy. Contact Elisity Support if an AOS-CX Virtual Edge Node reports no flow telemetry.
Aruba AOS-S. AOS-S supports three sFlow receiver instances. The Virtual Edge configures itself as the receiver on the lowest unused instance, or on an instance that has no destination, and never changes an instance that already sends to another collector. If all three instances send to other collectors, flow telemetry is not configured on the switch until one is freed; Access Policy is not affected. Sampling is one in every 50 packets with a 20-second counter polling interval, applied on UNI ports only, so uplinks are never sampled. AOS-S sends sFlow to a single Virtual Edge address.
Configuring Interface Auto-Detection Using Description Keywords (Aruba AOS-CX)
You can set UNI and NNI rules for Virtual Edges in Cloud Control Center by entering keywords that match port descriptions. The Virtual Edge does not read port descriptions from Aruba AOS-S.
Step 1. Navigate to Edge Management > Edge Settings > Advanced Settings.
Step 2. Turn on Enable Discovery and Telemetry and enter the keywords that mark a port as UNI.
Step 3. Turn on Disable Discovery and Telemetry and enter the keywords that mark a port as NNI.
Step 4. Click Save Changes.
Note: System-level UNI and NNI environment variables, when set, override the keywords entered in Edge Management > Edge Settings > Advanced Settings. If the keywords have no effect, contact Elisity Support.
Modifying Port Configurations for a VEN
After onboarding, review the configuration of each port in Cloud Control Center and adjust it to your network design and the scope of your microsegmentation effort. If you left Endpoint Discovery and Flow Telemetry disabled during onboarding, enable automatic configuration or configure each port manually here.
On Aruba AOS-CX, changing a port between UNI and NNI interrupts its traffic while the change is applied, and a port that keeps changing drops traffic each time. If an unstable input, such as interface state, a neighbor, or a description, makes automatic classification flap, set the port to Manual.
Step 1. Navigate to Edge Management > Virtual Edge Nodes, open the more options menu in the Actions column of the Virtual Edge Node, and select Port Configuration.
Step 2. Select the Endpoint Discovery or Flow Telemetry tab. Each tab lists the switch ports.
| Column | What it shows |
|---|---|
| Port Name | The switch port. |
| Configuration Type | Automatic or Manual. |
| Expected Status | The configuration Cloud Control Center intends for the port. |
| Source | Read-only. What decided the automatic classification of the port, such as Interface Description, LLDP Host Capabilities, LAG Member, Trunk Mode, Shutdown, or Default when no specific rule matched. For every value, see Managing Virtual Edges and Virtual Edge Nodes. |
| Actual Status | What the Virtual Edge Node reports. It shows Pending until the first report, and a change can take up to 10 minutes to appear. |
| Actual Status is Enabled when | Aruba AOS-CX | Aruba AOS-S |
|---|---|---|
| Endpoint Discovery | IP client tracking is configured on the interface. | MAC authentication is configured on the port. |
| Flow Telemetry | The Elisity flow monitor is applied to the interface. | The port is sampled by the Elisity sFlow receiver. |
When Expected Status and Actual Status differ, the interface is highlighted and a banner above the list reports the number of mismatches. Select Show Mismatches Only to list just those interfaces. Administratively disabled interfaces are not reported as mismatches.
Step 3. Click Edit Configuration to open the port configuration editor.
If neither Endpoint Discovery nor Flow Telemetry is enabled for the Virtual Edge Node, first turn on Enable Endpoint Discovery on the Endpoint Discovery tab, or the matching toggle on the Flow Telemetry tab.
Step 4. In the port configuration editor, select the Configuration Type for each interface: Automatic (default) or Manual. For Manual, set the Expected Status to Enabled or Disabled. For Automatic, the status is set by classification and cannot be changed unless you change the configuration type.
Step 5. Click Save Changes to push the configuration to the Virtual Edge Node immediately. Nothing changes on the switch until you save.
Configure Access Policy
Before an Aruba Virtual Edge Node enforces policy, enable Access Policy globally and on the Policy Set, create an Access Policy rule set, and assign it to each source Policy Group.
In most cases, onboard Aruba switches to the same Policy Set as the switches that enforce microsegmentation policies. The Policy Set must contain every Policy Group the devices at the site need: a device that matches a global Policy Group missing from the Policy Set gets no Access Policy. See Policy Sets and Site Labels.
For the procedure, see Configuring Access Policy for Aruba Switches.
Validate the Deployment
| Check | Expected Result | If It Does Not |
|---|---|---|
| Virtual Edge Node | Online in Edge Management > Virtual Edge Nodes. | If it shows Degraded, confirm that Enable Access Policy is enabled in Settings > System > Advanced. Otherwise, see Checking the Status of a VEN Onboarding. |
| Port configuration | Each port has the intended Configuration Type. Access ports show an Expected Status of Enabled for Endpoint Discovery and Flow Telemetry where required, and uplinks show Disabled. Source shows the classification basis you expect for each port, such as Default for a port with an endpoint connected. Actual Status matches Expected Status, and no mismatch banner appears. | A change can take up to 10 minutes to appear in Actual Status. On Aruba AOS-CX, a Flow Telemetry mismatch can mean that another flow monitor occupies the interface; see Existing Flow Telemetry Configurations. On Aruba AOS-S, set a voice VLAN access port to UNI. |
| Devices | Connected devices appear in IdentityGraph and match the expected Policy Groups. | Confirm that the port is a UNI with Endpoint Discovery enabled. On Aruba AOS-S, confirm that DHCP snooping runs on the access VLAN with the uplinks trusted, and that the port has no more than 32 MAC addresses. |
| Access Policy | The source Policy Group shows the intended Access Policy with the status Active. To confirm the Access Policy for a device, see Assigning an Access Policy to a Policy Group. | A device that keeps elisity_default_role can mean that the Access Policy is in Simulation, the Policy Group is missing from the Policy Set, or Enable Access Policy Security Controls is off for the Policy Set. Also confirm that the switch clock is synchronized, because a switch whose clock is not synchronized can reject role changes. |
| Flow telemetry | Traffic Analytics receives flow records from the Virtual Edge Node. | On Aruba AOS-S, Flow Telemetry needs Endpoint Discovery and a free sFlow receiver instance. On Aruba AOS-CX, some models and software versions reject the flow commands; contact Elisity Support. |
| Switch configuration | The switch holds the Elisity RADIUS server with accounting and dynamic authorization, elisity_default_role, and the Elisity classes, policies, and roles, and each endpoint session carries the role for its Policy Group. On Aruba AOS-S, DHCP snooping stays enabled with the uplinks trusted. For the commands to check, see Aruba AOS-CX Configuration Commands for Virtual Edge Node (VEN) Onboarding or Aruba AOS-S Configuration Commands for Virtual Edge Node (VEN) Onboarding. |
A role for a Policy Group appears only after a matching device connects to that switch. |
Decommissioning and Deleting a Virtual Edge Node
Decommissioning a Virtual Edge Node removes the Elisity configuration from the switch but keeps the Virtual Edge Node in Cloud Control Center, so you can return it to service with a single click.
On Aruba AOS-S, decommissioning removes MAC authentication from the access ports, which re-authenticates each connected endpoint once. Settings that can only be reset rather than removed, such as the MAC address format and the per-port address limit, return to platform defaults, and custom values that existed before onboarding are not restored. The Virtual Edge also removes elisity_default_role and its allow policy. DHCP snooping is not changed.
Navigate to Edge Management > Virtual Edge Nodes, open the Virtual Edge Node, and click Decommission in the top right. The status changes to Decommissioned.
You can also decommission from the Virtual Edge Node list: open the more options menu in the Actions column and select Decommission Virtual Edge Node.
To decommission several Virtual Edge Nodes at once, select them with the check boxes on the left, click Bulk Actions, and select Decommission. The menu also offers Recommission, Change Group, Change Credentials, Delete, and Force Delete, and actions that do not apply to the current selection are unavailable. Force Delete is enabled when at least one selected Virtual Edge Node is in the Decommission Started or Decommission In Progress state; its confirmation lists the Virtual Edge Nodes to be permanently removed and skips any selected Virtual Edge Nodes that are not eligible.
Each method opens a confirmation dialog, with warnings or errors where applicable.
Progress shows in the Activity Panel; see Checking the Status of a VEN Onboarding.
After decommissioning, delete the Virtual Edge Node from Cloud Control Center, or leave it decommissioned to recommission later; both options are in the more options menu in the Actions column. To clear a decommission that has stalled in Decommission Started or Decommission In Progress, select Force Delete Virtual Edge Node. Force Delete permanently removes the node from Cloud Control Center even when the managing Virtual Edge is offline. Because it halts the decommission, Elisity configuration may remain on the switch.
Recommissioning a Virtual Edge Node
Recommission a Virtual Edge Node from the Decommissioned state the same way you decommission it: from the details view, the more options menu in the Actions column, or Bulk Actions. Recommission is also available from the Decommission Failed, Decommission Started, and Decommission In Progress states, and requires the Virtual Edge to be Online.
Recommissioning restores the full Elisity configuration and re-enables MAC Authentication Bypass on applicable access ports on both switch families, so recommission during a planned change window. The Activity Panel tracks each recommissioning step. If recommissioning fails, confirm that the switch is reachable from the Virtual Edge over SSH and that the Virtual Edge Node credentials are still valid. A Virtual Edge Node in Recommission Failed cannot be recommissioned; it recovers when it registers again, which the Virtual Edge retries on its own.
Related Articles
- Configuring Access Policy for Aruba Switches
- Aruba AOS-CX Configuration Commands for Virtual Edge Node (VEN) Onboarding
- Aruba AOS-S Configuration Commands for Virtual Edge Node (VEN) Onboarding
- Hardware Compatibility Matrix
- Configuring Access Port Discovery Protection for Virtual Edge Nodes
- Virtual Edge Hypervisor Deployment Guide
- Virtual Edge Groups
- Policy Sets and Site Labels
- Policy Groups
- Policy Matrix
- Platform Connectivity Requirements
- Bulk Onboarding Virtual Edges and Virtual Edge Nodes