Modern network access control (NAC) platforms, like Arista Guardian for Network Identity (AGNI), work best as centralized policy engines rather than edge-facing endpoints. By positioning a BIG-IP as a RADIUS proxy between your access points (APs) and AGNI, you align with that design while tackling a few big hurdles in security and scalability.
Hi everyone! In this “How I did it” installment, I’m walking through how I used BIG-IP Local Traffic Manager (LTM) to provide RADIUS proxy services for an Arista AGNI cluster. Check out the swim lane diagram below for a look at how the RADIUS traffic actually flows through this setup.
Alright! Let’s take a look at how I did it.
Configure the BIG-IP as a RADIUS Proxy
To utilize the BIG-IP as a complete RADIUS proxy, I’ll need to create several resources including:
- Backend CloudVision AGNI pool - Will receive inbound authentication and accounting requests from my external access points (APs)
- RADIUS load balancing profile - used to ensure connection persistence to backend AGNI pool members
- SNAT Pool - Utilizing a SNAT Pool gives AGNI a stable, deterministic set of source IP identities for authentication and CoA/PoD, ensuring reliable session correlation, scale, and resilience instead of tying all AP sessions to a single source address.
- Virtual Address List - An address listing matching the SNAT Pool list. The list will be used by a virtual server to receive outbound CoA requests from the AGNI server(s).
- iRule - The iRule is used in the AGNI proxy flow to deterministically select a trusted source IP and explicitly forward CoA/PoD packets to the correct access point, which BIG‑IP cannot do with standard SNAT or virtual server behavior alone.
- Two (2) Virtual Servers - Used for Access Point (AP) initiated Authentication/accounting requests and CloudVision AGNI CoA requests.
Create the CloudVision AGNI backend pool
From the BIG-IP UI, I navigated to ‘Local Traffic’ --> ‘Pools’ --> ‘Pool List’ and clicked on the ‘+’ sign.
I provided a name for my backend pool, select ‘gateway_icmp’ for the health monitor, and selected ‘Least Connections’ for the load balancing method. For the pool members, I added in each of my CloudVision AGNI nodes. To enable high availability and scalability, I have deployed two (2) AGNI devices - the primary node and a read-only copy. Once added, I selected ‘Finished’ to create the pool.
Create a RADIUS load balancing profile
The BIG‑IP RADIUS profile exists to make BIG‑IP RADIUS‑aware by parsing RADIUS packets and enabling RADIUS‑specific features—most importantly, allowing iRules to read, modify, and act on RADIUS attributes (AVPs) for authentication, accounting, and CoA/PoD handling. Additionally, by specifying a persistence attribute, it can provide load balancing persistence to the backend AGNI server pool. From the UI, I navigated to ‘Local Traffic’ --> ‘Services’ --> ‘RADIUS’ and selected the ‘+’ sign.
I provided a name for the new profile as well as provide the appropriate RADIUS attribute. In this case I used ‘31’ which corresponds to the RADIUS calling-station-id (the originating device MAC). I selected ‘Finished’ to create the new profile, (see below).
Create SNAT Pool
From the UI, I navigated to ‘Local Traffic’ --> ‘Address Translation’ --> ‘SNAT Pool List’ and selected the ‘+’ sign.
I provided a name for the pool and added in available IP addresses to the SNAT Pool member list. The BIG-IP will use these addresses as the source address when connecting to the backend AGNI pool members. Likewise, on the AGNI portal, (in a later step) I created access devices that correspond to these SNAT addresses. With the IP addresses added, I selected ‘Finished’ to create the SNAT pool.
Below is the newly created SNAT Pool.
Create Address List
I created an Address list for use by my RADIUS CoA listening virtual server. The virtual, (created in a later step) will listen on these addresses for RADIUS CoA calls initiated by the CloudVision AGNI servers. These listening addresses match the previously created SNAT pool members. From the UI I navigated to ‘Shared Objects’ --> ‘Address Lists’ and select ‘Create’ from the right side of the main window.
I provided a name for the list and added in the relevant IP addresses. In a later step, I reference this list when creating the RADIUS CoA virtual server. I Selected ‘Save’ to create the list, (see below).
Create CoA persistence iRule
While the RADIUS profile ensures persistence with connections to the backend CloudVision AGNI load balancing pool, I also needed to ensure persistence with respect to AGNI-initiated calls out to the external access points, (via the BIG-IP). To accomplish this, I created an iRule and associated it to the RADIUS CoA virtual server in a later step.
The iRule, in conjunction with the RADIUS profile provides persistence for CoA calls by deriving a stable key from a RADIUS Calling‑Station‑Id attribute to deterministically select the same SNAT source IP and destination path, so every CoA/PoD for a given client is sent from the same BIG‑IP identity and reliably accepted by the access point (AP) as part of the same logical session. The iRule then reads the included RADIUS attribute ‘4’ to derive the appropriate destination address (AP’s management IP) and forwards the CoA call to the originating AP.
I navigated to ‘Local Traffic’ --> ‘iRules’ --> ‘iRule List’ and selected the ‘+’ sign.
I provided a name for the iRule and placed the following TCL iRule code in the edit window.
when RULE_INIT { # the name of the SNAT Pool - must be created separately prior to iRule creation set static::snatpool_name "radius_coa_pool" set static::members_cmd "members -list $static::snatpool_name" unset -nocomplain static::snat_ips set static::i 0 foreach static::snat_ip [eval $static::members_cmd] { set static::snat_ips($static::i) [lindex $static::snat_ip 0] incr static::i } set static::array_size [array size static::snat_ips] log local0.info "AGNI CoA/PoD SNAT initialized with $static::array_size SNAT IPs" } when CLIENT_DATA { if { [UDP::local_port] == 3799 && ([RADIUS::code] == 40 || [RADIUS::code] == 43) && $static::array_size > 0 } { # Get AP IP from NAS-IP-Address (AVP 4) as IPv4 if { [catch { set ap_ip [RADIUS::avp 4 ip4] } ] } { log local0.warn "CoA/PoD: unable to read NAS-IP-Address (AVP 4). Not forwarding." return } # Guard against empty/invalid AP IP if { $ap_ip eq "" || $ap_ip eq "0.0.0.0" } { log local0.warn "CoA/PoD: NAS-IP-Address missing/invalid ('$ap_ip'). Not forwarding." return } # Deterministic key: Calling-Station-Id (31) else Acct-Session-Id (44) set key [RADIUS::avp 31] if { $key eq "" } { set key [RADIUS::avp 44] } if { $key eq "" } { log local0.warn "CoA/PoD: no CSID (31) or Acct-Session-Id (44). Not forwarding." return } # Pick SNAT IP deterministically set idx [expr { abs([crc32 $key]) % $static::array_size }] set snat_ip $static::snat_ips($idx) snat $snat_ip # Forward to AP:3799 (node bypasses pool/LB) log local0.info "CoA/PoD: forwarding to AP $ap_ip:3799 using SNAT $snat_ip key '$key' code [RADIUS::code]" node $ap_ip 3799 } }
I selected ‘Finished’ to create the iRule on the BIG-IP.
Create the RADIUS virtual servers
I created two (2) virtual servers to handle RADIUS proxy traffic. First, I created a virtual server listening on the external side of the BIG-IP. This virtual will receive authentication and accounting requests, (UDP ports 1812/1813 respectively) from my access point(s). Additionally, I created a virtual server listening on the internal side of my BIG-IP. This virtual will receive CoA requests from the AGNI devices and forward the requests to the related external access point.
Create RADIUS Auth/Accounting server
From the BIG-IP UI, I navigated to ‘Local Traffic’ --> ‘Virtual Servers’ --> ‘Virtual Server List’ and selected the ‘+’ sign.
I provided a name for the virtual server and a destination address. The destination address will be used by the access point(s) to direct RADIUS authentication and accounting requests. Since the virtual will need to listen to both ports 1812 and 1813, I selected ‘* All Ports’. I selected ‘Advanced’ on the configuration page to expose the RADIUS profile field. For the protocol, I selected ‘UDP’.
For the RADIUS profile, I selected my previously created profile.
For source address translation, I selected ‘SNAT’ and associated my previously create SNAT Pool.
For the default backend pool, I selected my previously created AGNI backend pool. NOTE: I did not select either a default or fallback persistence profile. Persistence will be handled by the attached RADIUS profile. I selected ‘Finished’ to create the virtual server.
Create RADIUS CoA server
As previously mentioned, I also needed to create a virtual server to receive and forward AGNI-initiated CoA calls destined for the external APs. From the UI, I once again navigated to ‘Local Traffic’ --> ‘Virtual Servers’ --> ‘Virtual Server List’ and selected the ‘+’ sign.
I provided a name for the virtual server. For the destination address I selected the ‘Address List’ radio button and associated the previously created address list. I entered the standard CoA port of ‘3799’ , ‘Advanced’ and ‘UDP’ for the protocol.
I scrolled down the configuration page and selected the previously created RADIUS profile.
In the Resources section, I selected my previously created iRule from the ‘Available’ list and moved it to the ‘Enabled’ list box. Like the previously created virtual server, I left the persistence fields at ‘None’ and selected ‘Finished’ to create the virtual server.
I now had the BIG-IP configured to act as a proxy for both inbound authentication/accounting and outbound CoA RADIUS communications. My next task was to create access devices on my CloudVision AGNI cluster.
Create Arista CloudVision AGNI access device
I needed to create two (2) access devices - one for each SNAT Pool address member - to interact with the AGNI platform. From the primary CloudVision AGNI node UI, I navigated to ‘Access Devices’ --> ‘Devices’ and selected ‘Add or Import’ from the main window.
I provided a name for the access device. For the IP address I used the first address of my previously created BIG-IP SNAT pool. Since I utilized a non-Arista RADIUS-supported AP, I selected ‘Generic’ for the vendor and provided the RADIUS shared secret. Additionally, I specified a previously created AGNI device group name and selected ‘Add Device’ to create the access device.
I repeated the above steps to create a second access device corresponding to my other SNAT Pool member address.
Configure access point RADIUS authentication server endpoints
The last step in my RADIUS configuration was to update my external access point. CloudVision Agni supports a variety of third-party access points. The only hard requirement is that the access point (AP) must support RADIUS authentication. For this solution I utilized a Ubiquiti UniFi U7 Pro wireless access point.
As illustrated in the above diagram, the AP will send RADIUS authentication/accounting requests to the BIG-IP, (acting as a RADIUS proxy). To that end, I needed to create a RADIUS configuration pointing to the BIG-IP proxy virtual server. In addition, for CoA calls, (initiated by the AGNI cluster) the AP must be configured to accept RADIUS calls from the BIG-IP proxy. To enable this, I needed to create RADIUS server configuration on the AP that included the BIG-IP SNAT pool member addresses as well as virtual server listening IP address, (see below).
Viewing connected sessions in CloudVision AGNI
Now that all systems were configured, I was able to successfully, (and securely) authenticate and connect external users to my network via the edge AP using RADIUS authentication.
Additional Links
F5 BIG-IP Local Traffic Manager
Arista Guardian for Network Identity (AGNI)
RADIUS Authentication Overview





























