Mapping SAE Plug-In Attributes to Fields in the Subscriber Sessions Table (SRC CLI)

Note: Any fields in the subscriber sessions table that have a “not null” requirement must be mapped to either a request attribute or variable.

Use the following configuration statements to map an attribute in the subscriber sessions table to an SAE plugin attribute:

shared database cluster (primary) attribute-associations entity nameshared database cluster primary attribute-associations table name field name { sae-plugin-attribute sae-plugin-attribute ;}

The following procedure can be performed from any node.

To map an attribute in the subscriber sessions table to an SAE plugin attribute:

  1. (Optional) From configuration mode, access the configuration statement that configures the name of the table in the SSR database to which you want to make an association. For example, to map the subscriber sessions table attribute VpnID to the SAE plugin attribute vpn-id:
    user@host# edit shared database cluster primary attribute-associations entity subscriber-sessions
  2. Specify the name of the field in the subscriber sessions table and the SAE plugin attribute.
    [edit shared database cluster primary attribute-associations entity subscriber-sessions]user@host# set field VpnID sae-plugin-attribute vpn-id
  3. Commit the configuration.
    user@host# commit

Related Documentation