A new screen has been added to troubleshoot radius sessions that have issues.
The list of issues detected and displayed are as follows:
- Sessions with no ip (0.0.0.0) assigned. (These radius sessions should be disconnected to force a new IP assignment.)
- Sessions that have duplicate IP’s assigned – two or more active sessions using the same IP address. (These radius sessions should be disconnected to force a new IP assignment.)
- Duplicate IP Pool allocated IP’s – Two pool entries allocated to the same mac address on the same NAS. (The radius sessions should be disconnected to force a new IP assignment, and stale pool entries will then auto expire.)
- Stale IP Pool entries – Pool entry allocated where the radius session is no longer active. (This will be cleared automatically as pool entries expire after 2 hours of inactivity.)
- UnallocatedIP Pool entries – Pool entries that match an active radius session but has not been assigned. (This may be valid in some instances, as not all radius sessions will use pools, and static radius ip ranges may overlap pool ranges.)
- Wrong Pool IP’s assigned – Radius sessions where an IP address out of the wrong pool has been assigned. (These radius sessions should be disconnected to force a new IP assignment.)
All the entries have an action button next to each entry, which either allows you to disconnect the radius session or clear the ip pool entry.
Note, that there are several switches under the radius settings screen that determines how session maintenance will be handled.
These settings will do the maintenance required to keep the radius sessions tidy, but can introduce additional overhead to the system.
Note, that the use of IP Pools together with static IP’s must be carefully reviewed (as there must not be an overlap between the two). This may cause some radius sessions to be continuously disconnected. This is because the system tries to re-connect a session that it believes has been issued an IP address incorrectly.