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 an SRC VTA Shared Group Configuration (SRC CLI)

    Creating and Configuring an SRC VTA Shared Group Configuration (SRC CLI)

    You can set up multiple SRC VTAs; each SRC VTA is configured as a separate group with its own shared configuration.

    Use the following statements to configure an SRC VTA shared configuration:

    shared vta group name { subscriber-id-solution subscriber-id-solution ; nic-proxy nic-proxy; }

    To configure an SRC VTA shared configuration:

    1. From configuration mode, access the statement that configures an SRC VTA shared group configuration. For example, to configure an SRC VTA group called vta1:
      [edit]user@host# edit shared vta group vta1
    2. Specify the subscriber-id-solution option. This option specifies a data key that uniquely identifies subscriber accounts and sessions in the external database. Some settings also provide information that the NIC and the SAE use to identify subscribers.
      [edit shared vta group vta1]user@host# set subscriber-id-solution subscriber-id-solution

      For more information about configuring the subscriber-id-solution option, see Keys Used to Specify the Subscriber ID Solution (SRC CLI).

    3. Specify the location of the NIC proxy configuration relative to the configuration properties for the SRC VTA.
      [edit shared vta group vta1]user@host# set nic-proxy nic-proxy

      Set this option to the name you configured under the [edit shared vta nic-proxy-configuration name] configuration statement. See Configuring NIC Proxies for the SRC VTA.

      If you are using a NIC to map subscriber identifiers to an SAE, and you select an SRC VTA subscriber ID value that provides a data key for the NIC, specify the NIC proxy that uses that data key.

    4. Verify your configuration.
      [edit shared vta group vta1]user@host# show
    5. Commit your configuration.
      [edit shared vta group vta1]user@host# commit

    Note: You must enable the new SRC VTA instance with the enable component vta-name command.

    Keys Used to Specify the Subscriber ID Solution (SRC CLI)

    You use the subscriber-id-solution option under the shared vta group name configuration statement to specify keys for managing accounts and sessions. Table 1 shows the keys that you can specify for the SRC VTA to query the database, NIC, and SAE. For the SRC VTA to use a subscriber identifier, the plug-in event must include the corresponding NIC or SAE attributes that are listed in Table 1 (attributes that start with PA_). For more information about plug-in attributes, see the documentation for the SAE CORBA plug-in on the Juniper Networks website at

    Table 1: Keys That the SRC VTA Constructs to Manage Accounts and Sessions

    Subscriber’s Identifier

    Database Key

    Corresponding NIC Key

    Corresponding SAE Key

    accounting-id

    PA_ACCOUNTING_ID

    PA_ACCOUNTING_ID

    IP address that is returned from the NIC lookup

    user-dn

    PA_USER_DN

    PA_USER_DN

    PA_USER_DN

    interface-alias

    PA_INTERFACE_ALIAS

    None

    None

    interface-alias-and-router

    PA_INTERFACE_ALIAS@
    PA_ROUTER_NAME

    PA_ROUTER_NAME

    None

    interface-and-router

    PA_INTERFACE_NAME@
    PA_ROUTER_NAME

    PA_ROUTER_NAME

    PA_INTERFACE_NAME

    login-name

    PA_LOGIN_NAME

    PA_LOGIN_NAME

    PA_LOGIN_NAME

    (default)

    mac-address

    PA_USER_MAC_
    ADDRESS

    None

    None

    primary-user-name (PPP login name or public DHCP name)

    PA_PRIMARY_USER_
    NAME

    None

    PA_PRIMARY_USER_
    NAME

    nas-port-id-and-router

    PA_PORT_ID@
    PA_ROUTER_NAME

    None

    None

    login-name, user-dn, and interface-and-router also provide data keys for the NIC and the SAE; the other settings do not.

    Modified: 2015-06-21