Limitations

This Stale Sessions Cleanup feature has the following limitations:

  • Operations that depend on indexes for the stale sessions require either of the following:

    • The sessions must be present at the same subscriber that is reconnecting with the same DNN.

    • The associated framed IPv6 prefix is assigned to the same or the different subscriber session.

    If the subscriber has reconnected with a different DNN or framed IPv6 prefix is not reassigned to a different session, the sessions are not identified as stale.

  • The stale detection and cleanup procedures use the SupiDnnKey values. Indexes of the older session are not created based on the SupiDnnKey values.

    If the stale session is created before an upgrade, and a new session is created for the same SUPI and DNN combination postupgrade, then the older session is not identified as stale.

  • If the system has multiple stale sessions with the framed IPv6 prefix key, the corresponding index is associated only with the latest session.

    When a new session is created with then same key then only one session gets associated.