Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring the Fields in the Subscriber Sessions Table (SRC CLI)

    The format of subscriber identity information stored for each session is managed by the subscriber sessions table, which is controlled by the cluster’s client node/management servers. The configuration of the subscriber sessions table is copied to all nodes in the cluster, so all nodes operate with the same information.

    The preconfigured schema defines the table’s indexes. The default set of database fields in the subscriber sessions table addresses the needs of most carriers, however you can modify certain fields to address unique needs and situations. SSR Database Schema describes the default configuration and fields that can be modified.

    Note: Changes to the SSR database schema requires you to restart all SRC components.

    Use the following configuration statements to modify the fields in the subscriber sessions table:

    shared database cluster primary schema table subscriber-sessions field name { type [(int | string | binary)];size size;require-value;indexed;default default;variable-length;}

    To configure the subscriber sessions table:

    1. (Optional) From configuration mode, access the statement to configure the fields in the subscriber sessions table. For example, to add a new field called DeviceName:
      user@host# edit shared database cluster primary schema table subscriber-sessions field name
    2. (Optional) Specify the field type. Values for type correspond to legal SQL data types. For example, to specify the new field as a text string:
      [edit shared database cluster primary schema table subscriber-sessions field name] user@host# set type string
    3. (Optional) Specify the field size in bytes. For example, to specify the field size as two bytes:
      [edit shared database cluster primary schema table subscriber-sessions field name] user@host# set size 2
    4. (Optional) Specify whether null values are allowed for the value of the field. For example, to specify that a value is required:
      [edit shared database cluster primary schema table subscriber-sessions field name] user@host# set require-value
    5. (Optional) Specify whether you want the table to be indexed by this field. For example, to specify that the table is indexed by this field:
      [edit shared database cluster primary schema table subscriber-sessions field name] user@host# set indexed
    6. (Optional) Specify the default value for the field corresponding to the type. For example, to specify the default as nas123:
      [edit shared database cluster primary schema table subscriber-sessions field name] user@host# set default nas123
    7. (Optional) If the type is specified as either binary or string, specify whether the value is variable. If set, the SQL data type will be varbinary or varchar, respectively. For example, to specify the type as variable:
      [edit shared database cluster primary schema table subscriber-sessions field name] user@host# set variable-length

    Modified: 2016-12-29