Note: Subscriber keys is a function that is applicable to RADIUS mode only. For more information on RADIUS configuration, see CMP Wireless User's Guide.
An
MPE device must create a data session to track the life cycle of the request and process of any subsequent Interim-Update messages or a
RADIUS Accounting-Stop message, when a
RADIUS Accounting-Start message is received from:
- An AAA server or from a broadband network gateway (BNG) system
- A RADIUS Interim-Update message is received for an unknown session
To create this session, the
MPE device determines a subscriber ID from the RADIUS message using subscriber keys. You configure subscriber keys using the
CMP system. Subscriber keys are associated with individual BNG systems.
The subscriber key is a combination of specified type-length values (TLVs) or vendor-specific attributes (VSAs) found in the RADIUS message. The order in which the attribute values are combined is defined in the
CMP system. After the subscriber key is computed, the key is matched against the subscribers defined on the
MPE device:
- If no match is found, the MPE device initiates an SPR database lookup:
- If the lookup succeeds, the request is parsed for creating a list of VSAs to be included in a RADIUS Change of Authorization (CoA) message and sent to the BNG system.
- If the lookup fails and if the RADIUS configuration value Validate User is set to true, the request is rejected.
- If a match is found, the MPE device creates a dummy user instance to store necessary information for later use.
For more information on CoA messages, see Managing RADIUS CoA Templates.