Testing the SRC VTA Configuration Overview
You can use SRC VTA test commands to simulate events and test a specific SRC VTA group configuration. You can simulate subscriber-tracking events, service-tracking events, and callback events.
There are two steps involved in configuring and testing the SRC VTA configuration.
- First, you need to define the SRC VTA test events. You define a test event by assigning values to a set of attributes. The attributes you can assign to the test event depends on the event type you specify. SRC VTA test event configurations are stored in the Juniper Networks database so that you can reference them when executing SRC VTA test commands from any C Series Controller.
- After you define a test event, you can reference the test event when you execute test commands.
Table 1 lists the event types and the configuration statements you use to define SRC VTA test events.
Table 1: SRC VTA Event Types and Test Event Configuration Statements
| Test Events | Configuration Statement Used to Define the Test Event | Event Type |
Subscriber-and service-tracking test events | Use the following statement to configure subscriber- and service-tracking test events: shared vta test-events event-name type type attributes { The event-name variable is an arbitrary name you specify for the event. When you execute a test command, you specify this name for the test-event variable. See Table 2 for setting the attribute-name variable for either subscriber- or service-tracking test events. | You can define the following event types for the event-type variable when defining subscriber-tracking events:
You can define the following event types for the event-type variable when defining service-tracking events:
|
Callback test events | Use the following statement to configure callback test events: shared vta test-events type call-back:name callback-attributes { You can define the following attribute type for callback test events:
The event-name variable is an arbitrary name you specify for the event. When you execute a test command, you specify this name for the test-event variable. | The only event type you can define for callback test events is callback. |
Table 2: Attributes for Subscriber- and Service-Tracking Test Events
| Attributes Supported for Subscriber-Tracking Events | Attributes Supported for Service-Tracking Events |
PA_ACCOUNTING_ID | PA_ACCOUNTING_ID |
PA_AUTH_USER_ID | PA_AGGR_ACCOUNTING_ID |
PA_DHCP_PACKET | PA_AGGR_AUTH_USER_ID |
PA_EVENT_TIME | PA_AGGR_LOGIN_NAME |
PA_EVENT_TIME_MILLISECOND | PA_AGGR_SESSION_ID |
PA_IF_RADIUS_CLASS | PA_AGGR_USER_DN |
PA_IF_SESSION_ID | PA_AGGR_USER_INET_ADDRESS |
PA_INTERFACE_ALIAS | PA_AUTH_USER_ID |
PA_INTERFACE_DESCR | PA_DHCP_PACKET |
PA_INTERFACE_NAME | PA_DOWNSTREAM_BANDWIDTH |
PA_LOGIN_ID | PA_EVENT_TIME |
PA_LOGIN_NAME | PA_EVENT_TIME_MILLISECOND |
PA_NAS_INET_ADDRESS | PA_IF_RADIUS_CLASS |
PA_NAS_IP | PA_IF_SESSION_ID |
PA_NAS_PORT | PA_IN_OCTETS |
PA_OPERATIONAL | PA_IN_PACKETS |
PA_PORT_ID | PA_INTERFACE_ALIAS |
PA_PRIMARY_USER_NAME | PA_INTERFACE_DESCR |
PA_RADIUS_CLASS | PA_INTERFACE_NAME |
PA_ROUTER_NAME | PA_LOGIN_ID |
PA_SESSION_TIMEOUT | PA_LOGIN_NAME |
PA_SSP_HOST | PA_NAS_INET_ADDRESS |
PA_SUBSCRIPTION_NAME | PA_NAS_IP |
PA_TERMINATE_CAUSE | PA_NAS_PORT |
PA_USER_DN | PA_OPERATIONAL |
PA_USER_INET_ADDRESS | PA_OUT_OCTETS |
PA_USER_IP_ADDRESS | PA_OUT_PACKETS |
PA_USER_MAC_ADDRESS | PA_PORT_ID |
PA_USER_RADIUS_CLASS | PA_PRIMARY_USER_NAME |
PA_USER_TYPE | PA_RADIUS_CLASS |
PA_ROUTER_NAME | |
PA_SERVICE_NAME | |
PA_SERVICE_SCOPE | |
PA_SERVICE_SESSION_NAME | |
PA_SERVICE_SESSION_TAG | |
PA_SESSION_ID | |
PA_SESSION_TIME | |
PA_SSP_HOST | |
PA_SUBSCRIPTION_NAME | |
PA_TERMINATE_CAUSE | |
PA_UPSTREAM_BANDWIDTH | |
PA_USER_DN | |
PA_USER_INET_ADDRESS | |
PA_USER_IP_ADDRESS | |
PA_USER_MAC_ADDRESS | |
PA_USER_RADIUS_CLASS | |
PA_USER_TYPE |
