Bug ID 488166: Provide an option to delete the session if IP class address Limit reached when new IP being added and create a new one instead.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP PEM(all modules)

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5

Opened: Oct 31, 2014

Severity: 3-Major


When Multiple IP feature is supported, If a new IP needs to be add to session will fail if IP address limit is reached for particular class of IP addresses. So, if old IPs are not removed from the session even though subscriber may not be using it, we disallow new IP assignment and hence subscriber traffic might be blocked/not polcied as IP address was not added to session.


Session does not get created by radius, but by traffic and there is no subscriber ID assigned to it. PCRF may decline to give policy and hence Subscriber traffic may not be policed as expected.


IP class address limit for the session and new IP address add for the same same subscriber session arrives.



Fix Information

Now added a db variable Tmm.pem.session.delete.if.max.ipaddr.per.class.exceeded which is by default set to TRUE. Now. when a new IP address add request comes via Radius and Session IP limit has reached, then we delete the current session and create a new one altogether. So that new Subscriber session is not affected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips