Bug ID 435450: PEM Subscriber session is not working for subscriber traffic from non-zero routing domain

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP PEM(all modules)

Known Affected Versions:
11.4.0

Fixed In:
11.4.1 HF2, 11.4.1

Opened: Oct 25, 2013
Severity: 2-Critical
Related AskF5 Article:
K16033

Symptoms

The issue occurs when a customer deploys PEM in an environment with multiple Routing Domains (RD) for subscriber traffic. The subscriber sessions are created successfully using RADIUS for subscriber traffic on RD 0. The traffic arriving on a VLAN associated with any non-zero RD does not match the session created with RADIUS, thus causing issues with identifying the subscriber traffic and applying the correct policies.

Impact

Subscriber traffic arriving on a non-zero routing domain will have issue with identifying the subscriber traffic and applying the correct policies.

Conditions

This happens when PEM is deployed with subscriber traffic arrive BIGIP with multiple routing domains (i.e., multiple vlans)

Workaround

there is not work around

Fix Information

This fix will treat subscriber traffic from any routing domain as if they are from RD 0, so that as long as the customer can ensure there will be no overlapping IP addresses between different routing domains, PEM will work just fine.

Behavior Change