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:
To configure an SRC VTA shared configuration:
From configuration mode, access the statement that configures an SRC VTA shared group configuration. For example, to configure an SRC VTA group called vta1:user@host# edit shared vta group vta1
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).
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.
Verify your configuration.[edit shared vta group vta1]user@host# show
Commit your configuration.[edit shared vta group vta1]user@host# commit
You must enable the new SRC VTA instance with the enable component vta-name command.