Configuring UDP Ports for RADIUS Plug-Ins
In RADIUS packets that RADIUS plug-ins send to a RADIUS server, the plug-in uses an identifier field to match requests to replies. This field provides for a maximum of 256 identifiers. Once all identifiers are used, the plug-in cannot send any more requests until it receives replies that match the requests already sent. In high-load systems, this limit can slow performance.
To overcome this limitation, you can configure a pool of UDP ports for RADIUS plug-ins. Having a pool of ports allows RADIUS plug-ins to create one queue per port to wait for RADIUS replies. Each queue can wait for 256 RADIUS packets. The RADIUS plug-ins send RADIUS packets through the pool of ports in a round-robin mode.
You can configure a global source UDP port or pool of ports that RADIUS plug-ins use to communicate with RADIUS servers. You can also configure UDP ports for each plug-in instance. If you do not configure a UDP port for a plug-in instance, the plug-in uses the global UDP port.
Configuring Global UDP Ports
To configure global UDP ports with SDX Configuration Editor:
- In the navigation pane, select a directory configuration object for the SAE that you want to configure.
- Select the Miscellaneous tab, and expand the Global RADIUS UDP Port section.
![]()
- Fill in the field as described in Global RADIUS UDP Port Field.
Global RADIUS UDP Port Field
Use the field in this section to specify a global UPD port for RADIUS plug-ins.
UDP Port
- Source UDP port or a pool of ports that RADIUS plug-ins use to communicate with RADIUS servers.
- Value—You can enter a single port number, a pool of port numbers, or a list of port numbers and port ranges.