A
- access DNs
- accounting
- ACP (Admission Control Plug-In)
- redundancy
- ACP congestion point usage trap
- ACP. See SRC ACP
- action congestion points 1
- configuring
- monitoring
- address pools. See IP address pools
- Admission Control Plug-In. See SRC ACP
- agents See NIC agents
- allocating bandwidth to applications not controlled by SRC ACP
- APIs
- APIs (application programming interfaces)
- application programming interfaces. See APIs
- applications
- executing with SRC ACP
- external for use with SRC ACP 1, 2
- assigned IP subscribers
- third-party devices 1
- assigning
- ATM access network, using with SRC ACP
- attributes
- authentication plug-ins
- authentication target
- configuration
- authorizing and tracking services
B
- backbone congestion point profiles
- backbone congestion points 1
- backbone network
- backbone network management with SRC ACP
- background bandwidth
- bandwidth
- allocating to applications not controlled by SRC ACP
- background 1, 2
- configuring
- for services 1, 2
- for subscribers
- downstream
- upstream
- bandwidths and congestion points for subscribers
- basic group
- BEEP, devices running Junos OS 1
- configuring port
- BEEP, Devices running Junos OS
- Blocks Extensible Exchange Protocol. See BEEP
C
- certificate authority (CA)
- classification scripts
- congestion point classification
- configuring
- criteria 1, 2
- description
- how it works
- targets 1, 2
- clients
- gateway
- Common Object Request Broker Architecture. See CORBA
- community manager
- configuring, third-party devices
- component interactions
- configuration group, devices running Junos OS 1, 2
- configuration manager, instantiating for NIC
- congestion point applications
- congestion point classification 1, 2
- congestion point classification scripts. See classification scripts
- congestion point expressions 1, 2
- congestion point profiles 1
- congestion points 1, 2
- congestion points by IP address and associated service sessions
- monitoring
- congestion points by login name and associated service sessions
- monitoring
- congestion points by session ID and associated service sessions
- monitoring
- conventions
- COPS (Common Open Policy Service)
- connection with JunosE routers 1
- COPS-PR versus COPS XDR
- JunosE router connection
- CORBA (Common Object Request Broker Architecture)
- CORBA interfaces
- CORBA-based plug-in SPI. See plug-ins, external
- customer support 1
- customized interface modules
D
- database accounting method
- configuration
- deriving congestion points
- device drivers
- Gx
- Junos
- configuring, SRC CLI
- viewing state, C-Web interface
- viewing state, SRC CLI
- viewing statistics, C-Web interface 1, 2
- viewing statistics, SRC CLI 1, 2
- JunosE
- configuring, SRC CLI
- viewing state, SRC CLI
- viewing statistics, SRC CLI 1, 2
- devices running Junos OS
- Devices running Junos OS
- directory
- directory blacklist, deleting 1, 2
- distinguished name. See DN
- DMI
- DMI driver
- migrating
- DMI network device
- adding
- DMI, devices running Junos OS
- DN (distinguished name)
- DNs
- documentation
- domain maps
- downstream bandwidth
- downstream RADIUS network elements and accounting targets
- configuration statements
- downstream RADIUS network elements and authentication targets
- configuration statements
E
- edge congestion points
- assigning to subscribers
- deriving
- DNs of
- monitoring
- edge network 1, 2
- edge network management, configuring
- equipment registration
- event notification, PCMM network
- configuration statements
- properties, configuring
- event notification, third-party devices
- events, publishing
- external applications
- external plug-ins
- external plug-ins. See plug-ins
- External Subscriber Monitor
- acting as pseudo RADIUS server, C-Web interface
- agent process statistics, viewing
- configuring
- configuring basic local properties
- configuring client secret
- configuring directory connection properties
- configuring event notification
- configuring eventing properties
- configuring initial properties
- configuring logging destinations
- event notifications, monitoring
- event notifications, viewing
- IP address manager 1
- overview, C-Web interface
- starting
- statistics, monitoring
- statistics, viewing
- stopping
F
- failover parameters, SAE 1, 2
- fault recovery, SRC ACP
- files
G
- group
- creation
- groups, NIC hosts
- Gx router driver
- adding router acting as PCEF
- charging rule installation
- charging rule removal
- charging rule report
- Charging-Rule-Install
- Gx router driver, configuring
- overview
- SAE
- SAE (service activation engine)
- SAE plug-ins
- service accounting
- session creation
- session detach
- session reauthorization
- session updation
- viewing state, SRC CLI
H
- hosted internal plug-in
- hosted plug-ins. See plug-ins
I
- interactions between SRC ACP and other components 1, 2
- interface classification scripts
- interface modules, SAE
- interfaces, assigning to backbone congestion point profiles
- internal plug-ins. See plug-ins
- IOR
- IP address pools
- IP pools
J
- JunosE routers
- accessing router CLI
- COPS connection 1
- integration overview
- monitoring interactions with SAE
- router objects, adding
- SRC client 1
- troubleshooting
- VR objects
- adding individually, SRC CLI 1, 2
- discovering, SRC CLI
L
- LDAP access. See SAE (service activation engine), configuring
- local properties
- configuration
- logging properties
- login names
- login process
- login registration
M
- managing
- manuals
- methods
- modifying congestion points
- monitoring
N
- NAS port ID
- network devices
- SNMP communities, configuring
- network information collector. See NIC
- network interfaces 1, 2
- network publisher See NIC
- NIC (network information collector) 1, See also other NIC entries
- API
- configuration prerequisites
- configuration statements
- configuration, changing
- configuration, verifying
- data mapping
- default operating properties, viewing
- factory interface 1, 2
- logging
- monitors
- network publisher
- operating properties, changing
- overview
- planning implementation
- realms
- replication
- replication, configuring
- resolution processes 1, 2
- resolvers
- restarting
- results
- roles
- starting
- stopping
- testing
- viewing
- NIC agents
- configuration overview
- directory, configuring
- overview 1, 2
- restarting
- sae client agents, configuring
- sae plug-in agents, configuring
- NIC configuration scenarios
- changing 1
- MultiPop
- OnePop
- OnePopAcctId
- OnePopAllRealms
- OnePopDnSharedIp
- OnePopDynamicIp
- OnePopLogin
- OnePopLoginPull
- OnePopPcmm
- OnePopPrefixIp
- OnePopPrimaryUser
- OnePopSharedIp
- OnePopStaticRouteIp 1, 2
- OnePopTunnel
- OnePopVrfIp 1, 2
- overview 1, 2
- scenario-name
- NIC hosts
- NIC locators
- NIC proxies
- cache, configuring
- configuration overview
- configuration prerequisites
- instantiating
- logging
- NIC replication, configuring
- overview
- prerequisites
- removing instances
- requirements 1, 2
- resolution information, configuring
- resolution requests
- NIC Proxy for Pseudo-RADIUS server
- NIC proxy for Pseudo-RADIUS server
- NIC resolvers
- nic-network-publisher-configuration-statements
- notice icons
O
- operation
P
- PacketCable Multimedia. See PCMM
- PCMM (PacketCable Multimedia)
- plug-ins
- preventing
- priorityList
- properties
- proxy RADIUS accounting method
- configuration
- pseudo-RADIUS server
- publishing events
R
- RADIUS accounting listener
- RADIUS accounting listener queue limits
- configuration
- RADIUS accounting listener transport
- configuration
- RADIUS authentication listener queue limits
- configuration
- RADIUS authentication listener transport
- configuring
- randomPick
- realm
- See NIC realms
- redundancy, SRC ACP
- rendering
- resolution processes
- roles, NIC
- roundRobin
- router initialization scripts
- router object
- adding for third-party devices
- routers
- accessing router CLI
- adding devices running Junos OS
- adding JunosE
- configuring SAE to communicate with Junos Space
- integrating devices running Junos OS 1, 2, 3
- integrating JunosE
- SNMP communities, configuring
S
- SAE (service activation engine)
- accounting
- APIs. See APIs
- BEEP connection, devices running Junos OS
- COPS
- deleting directory blacklist 1, 2
- device running Junos OS client
- Diameter connection, devices running Junos OS
- disabling interactions with device running Junos OS
- enabling interactions with device running Junos OS
- failover parameters 1, 2
- Gx router driver
- monitoring interactions
- NIC replication, configuring
- overview
- PCMM environment
- plug-ins See plug-ins
- reloading configuration 1, 2, 3, 4
- role
- router initialization scripts. See router initialization scripts
- session store
- starting
- stopping
- SAE (service activation engine), configuring
- BEEP connection
- COPS connection
- directory eventing, SAE configuration data
- event notification API properties
- LDAP access, SRC CLI
- router initialization script location
- serialized data compression
- session job manager
- session store
- SRC ACP
- SAE (service activation engine),configuring
- SAE communities
- configuring, third-party devices
- description, third-party devices
- SAE remote interface
- script services
- serialized data compression, configuring
- service activation engine. See SAE
- services
- configuring bandwidth for 1, 2
- monitoring
- preventing activation
- reloading on SAE 1, 2
- session job manager, configuring
- session state registrar See SSR
- session store
- SIC
- SIC (subscriber information collector)
- accounting listener
- accounting methods
- authentication methods
- configuring basic SIC group
- database accounting method
- default attributes in tagged attribute group, configuring
- device capabilities, configuring
- device models
- device models, configuration
- device templates, configuring
- Diameter server
- Diameter server identity, configuring
- Diameter server peer, configuring
- Diameter server, configuring
- dictionaries
- dictionaries, configuration
- downstream network element
- dynamic authorization
- how the process works
- overview 1, 2, 3
- editing rules
- editing rules, configuration
- editing rules, configuration statements
- event logging
- event logging, configuration
- explicit authentication routing, configuration statements
- explicit routing rules
- explicit routing, configuration
- explicit routing, configuration statements
- failover mode
- failover policy
- global service template default attributes, configuring
- global service template mode, configuring
- global service template normal attributes, configuring
- global service template override attributes, configuring
- global service template parameterized attributes, configuring
- global service template required attributes, configuring
- global service template variables, configuring
- global service templates, configuring
- global service templates, creating
- global service templates, overview
- implicit routing rules
- implicit routing, configuration
- local and shared configuration
- local realms
- local realms, configuration
- normal attributes in tagged attribute group, configuring
- override attributes in tagged attribute group, configuring
- overview
- parameterized attributes in tagged attribute group, configuring
- primary/backup
- proxy accounting method
- proxy function
- RADIUS configuration
- RADIUS transport for server, configuring
- RADIUS transports
- request routing rules
- request routing, configuring
- required attributes in tagged attribute group, configuring
- round robin
- server instance, creation
- service template default attributes, configuring
- service template mode, configuring
- service template normal attributes, configuring
- service template override attributes, configuring
- service template parameterized attributes, configuring
- service template required attributes, configuring
- service template samples
- service template variables, configuring
- service template, configuration statements
- service template, tagged attribute configuration statements
- service templates, configuring
- service templates, creating
- service templates, overview
- SNMP support
- snmp, configuring
- statistics
- tagged attribute group, creating
- tagged attributes in, configuring
- upstream network element
- SIC accounting and authentication clients
- configuring
- SIC accounting and authentication targets
- configuring
- SIC accounting targets
- configuring
- SIC authentication targets
- configuring
- SIC dynamic authorization targets
- configuring
- SIC upstream and downstream network elements
- SNMP
- SNMP communities
- configuring
- SOAP
- Soap Fault Codes
- VTA
- SRC ACP (SRC Admission Control Plug-In) 1
- API
- ATM access network
- authorizing and tracking services
- backbone network management, configuring
- classification scripts
- configuring
- congestion points
- connections to services directory, configuring
- connections to subscribers’ directory, configuring
- CORBA interfaces, configuring
- data files
- data files, reorganizing
- description of
- event publishers, configuring
- external applications 1, 2
- external plug-in for SAE, configuring
- fault recovery
- groups, configuring 1, 2
- information from external applications, displaying
- interactions with other components
- logging properties, configuring
- monitoring
- operation, configuring
- preventing service activation
- properties
- redundancy 1
- SAE, configuring for
- starting
- state synchronization 1
- stopping
- subscribers, monitoring 1, 2
- supporting multiple SAEs
- using multiple SRC ACPs
- SRC ACP (SRC Admission Control Plug-In), congestion points
- SRC Admission Control Plug-In. See SRC ACP
- SRC client, JunosE routers
- SRC software process, Devices running Junos OS
- SRC software process, devices running Junos OS 1, 2
- SRC Volume Tracking Application
- SRC Volume-Tracking Application SRC Volume-Tracking Application See SRC VTA
- SOAP interface
- SRC Volume-Tracking Application (SRC VTA)
- account and session database connection, configuring See SRC CLI
- database deadlocks
- database to store account and session data, configuring See SRC CLI
- db-engine processor
- group, configuring See SRC CLI
- JDBC .jar file See installing
- keys to specify subscriber-id-solution See SRC CLI
- tracking events
- SRC Volume-Tracking Application (VTA)
- group
- SRC Volume-Tracking Application. See SRC VTA
- SRC VTA
- accounts and service sessions
- balance change history records
- events
- performance statistics
- session history records
- sessions
- SOAP API statistics
- subscriber accounts
- subscriber balance changes
- subscriber session history
- testing configuration
- SRC VTA (SRC Volume-Tracking Application (SRC VTA)
- SRC VTA (SRC Volume-Tracking Application)
- account and session database connection, configuration
- accounts
- description
- interim accounting interval, setting
- service
- subscriber
- usage metric, setting 1, 2, 3
- actions 1
- architecture
- bought account
- bought quota 1
- connections to SRC components
- database
- database engine processor
- db-engine processor
- e-mail notifications, sending
- event attributes
- event handlers
- event queue
- events 1
- example
- functions
- group, configuring
- how it works
- initial account balance
- initial account status
- interval accounting interval, setting 1, 2
- JavaScript programs
- keys to specify subscriber-id-solution
- logging events to a text file
- mail processor
- on-error
- operation process
- overview
- periodic account
- periodic quota 1
- processors
- providing volume-based services
- quota service 1
- related configuration tasks
- SAE events
- saving event messages on a system logging server
- script runner processor
- scripts
- external 1, 2
- JavaScript programs
- services
- sessions
- subscriber login with IP address
- types
- usage metric, configuring 1, 2, 3
- SRC VTA (Volume-Tracking Application)
- actions
- database deadlocks
- event handlers
- function
- on-error
- related configuration tasks
- SSR (session state registrar)
- adding a client node to an active cluster
- adding a management server to a client node in an active cluster
- adding data nodes to an active cluster
- attribute associations, configuring in an active cluster
- cluster configurations
- cluster network requirements
- cluster status, viewing
- configuration statements
- configuring
- cluster name
- cluster nodes
- database memory size
- geometry
- initial cluster
- management server
- subscriber sessions schema 1, 2
- creating
- database memory requirements, viewing
- database mode, viewing
- database modes
- database schema
- database schema, configuring in an active cluster
- database, viewing running configuration
- deleting
- disabling
- distributing the cluster configuration
- enabling
- impact of configuration changes
- making modifications to subscriber sessions table
- node groups
- node types
- overview
- placing
- planning the cluster topology
- planning worksheets
- removing
- restarting
- scaling the cluster
- server requirements
- supported configurations
- viewing, all subscriber sessions
- viewing, subscriber sessions by indexed field
- viewing, subscriber sessions by IP address
- viewing, total number of subscriber sessions
- starting
- state synchronization
- statistics, SRC ACP
- stopping SRC ACP
- subscriber information collector subscriber information collector See SIC
- authentication target, configuring
- basic group, configuring
- configuration summary
- configuring management of RADIUS-enabled devices for the SIC
- database accounting method, configuring
- default attributes in tagged attribute group, configuring See SIC
- device capabilities, configuring See SIC
- device models, configuring See SIC
- device templates, configuring See SIC
- Diameter configuration summary
- Diameter server See statements
- Diameter server identity, configuring See SIC
- Diameter server peer, configuring See SIC
- Diameter server, configuring See SIC
- dictionaries, configuring See SIC
- dynamic authorization
- editing rules, configuration statements See SIC
- editing rules, configuring See SIC
- event logging, configuring See SIC
- explicit authentication routing, configuration statements See SIC
- explicit routing, configuration statements See SIC
- explicit routing, configuring See SIC
- global service template default attributes, configuring See SIC
- global service template mode, configuring See SIC
- global service template normal attributes, configuring See SIC
- global service template override attributes, configuring See SIC
- global service template parameterized attributes, configuring See SIC
- global service template required attributes, configuring See SIC
- global service template variables, configuring See SIC
- global service templates, configuring See SIC
- global service templates, creating See SIC
- global service templates, overview See SIC
- group, creating
- implicit routing, configuring See SIC
- local properties
- local realms, configuring See SIC
- normal attributes in tagged attribute group, configuring See SIC
- outbound RADIUS transport for group, configuring See SIC
- override attributes in tagged attribute group, configuring See SIC
- parameterized attributes in tagged attribute group, configuring See SIC
- proxy RADIUS accounting method, configuring
- RADIUS accounting listener queue limits, configuring
- RADIUS accounting listener transport, configuring
- RADIUS accounting listener, configuring 1, 2
- RADIUS authentication listener queue limits, configuring
- RADIUS authentication listener transport, configuring
- RADIUS configuration summary
- RADIUS dynamic authorization configuration summary
- RADIUS transport for server, configuring See SIC
- request routing, configuring See SIC
- required attributes in tagged attribute group, configuring See SIC
- server instance, creating See SIC
- service template default attributes, configuring See SIC
- service template mode, configuring See SIC
- service template normal attributes, configuring See SIC
- service template override attributes, configuring See SIC
- service template parameterized attributes, configuring See SIC
- service template required attributes, configuring See SIC
- service template samples See SIC
- service template variables, configuring See SIC
- service template, configuration statements
- service template, tagged attribute configuration statements
- service templates, configuring See SIC
- service templates, creating See SIC
- service templates, overview See SIC
- snmp, configuring See SIC
- tagged attribute group, creating See SIC
- tagged attributes in service templates, configuring See SIC
- subscriber information collector (SIC)
- accounting and authentication clients
- accounting and authentication targets
- accounting targets
- authentication targets
- device models in network element
- dynamic authorization targets
- failover mode
- failover mode and policy
- fast fail options for the failover policy
- retry options for the failover policy
- upstream and downstream network elements
- subscribers
- assigning interfaces to
- configuring bandwidths and congestion points for 1, 2
- IP addresses
- login names
- monitoring
- provisioned and actual bandwidths
- subscriptions
- support, technical See technical support
T
- targets. See classification scripts
- technical support
- text conventions defined
- third-party devices
- creating sessions
- integrating into SRC network
- logging in subscribers
- provisioning with script services
- router objects, adding
- SAE communities
- VR objects, adding
- threads
- configuring for sessions
- tracking plug-ins
- troubleshooting
- tuning factors for background bandwidth
U
- upstream bandwidth
- upstream network elements, accounting and authentication clients, and dynamic authorization targets
V
- virtual routers
- Volume-Tracking Application (VTA)
- VTA See SRC VTA
- VTA (SRC Volume-Tracking Application)
- accounts
- event attributes
- event handlers 1
- event queue
- events
- SAEEventListener
- sessions
- VTA (Volume-Tracking Application)
- database to store account and session data, configuration
- prerequisites for running
- tracking events
W
- Web application server
- application deployment
- channel stack
- configuration statements
- configuring the Web application server
- installing Web applications inside
- local properties
- multicast-address
- node-id
- shared cluster name
- shared cluster nodes
- shared cluster properties
- starting
- Web Services Definition Language. See WSDL
- Web Services Gateway
- clients
- WSDL files
Download This Guide
Configuring Actions Overview
Actions are executed by event handlers in response to an event. For example, the action may update an account balance, start a service, or stop a service. You configure what action the event handler takes in response to an event when you configure an event handler. An action is performed only if an event matches the event type and condition specified in the event handler configuration. An action can invoke functions provided by any processor.
An action can update event attributes or add new attributes to an event for subsequent processing of the same event by subsequent actions in the same event handler, or in subsequent event handlers.
You define an action with the edit shared vta group name action action-name configuration statement. You refer to a previously defined action when you configure an event handler. Event handlers can refer to multiple actions. To configure an event handler to use a particular action, specify it as follows:
![]() | Note: We recommend that when you configure event handlers and their actions, you ensure that for any given event, all database operations are performed before any other operations that have permanent effects. This is because if a database error occurs—for example, due to normal contention for database records between different event threads—the SRC VTA rolls back the current database transaction (no changes are made to the database) and then restarts processing the event. If the event performs some other operation other than database operations before such an error, such as start a service, then that other operation is performed again when the event is reprocessed following the error. |
When you configure an action, you specify the following options:
- Function—The function that the action invokes
- Parameter—The parameters and corresponding values to be passed to the function
- On-error—What the event handler does in response to an error
Functions are variables that an action invokes, for example, to update database accounts. The function takes as input the configured parameters, the event, and the event context (which may include values created by previously executed actions). The SRC VTA provides a set of available functions. Each function takes a different set of input parameters. Table 52 describes the available SRC VTA functions and their associated input parameters.
Table 52: SRC VTA Functions and Input Parameters
Function Name | Description | Input Parameters |
db-engine-calculate-interim | Calculates the interim interval in the service-tracking event by using the interim interval function for the service, as defined with the shared vta group name processor db-engine service name interim-interval-function configuration statement. This function adds the following attribute to the event after the function is executed:
| None |
db-engine-calculate-usage | Calculates usage in the service-tracking event by using the usage metric function for the service, as defined with the shared vta group name processor db-engine service name usage-metric-function configuration statement. This function adds the following attributes to the event after the function is executed:
| None |
db-engine-get-accounts | Retrieves account data for the corresponding subscriber for the event. Data for multiple accounts is retrieved; accounts are identified by the accountName suffix. Accounts are defined with the shared vta group name processor db-engine account name configuration statement, where the account name corresponds to the _accountName suffix. Subsequent event handlers of the event can use the retrieved data. This function adds the following attributes to the event after the function is executed:
| None |
db-engine-terminate-session | Closes active SRC VTA sessions (for the subscriber for which the event occurred) that have a status of Start or Interim. It does not stop the corresponding services in the SAE. You can use this function to stop a session at the end of a billing period. Usage data collected after the SRC VTA session is stopped is stored in new SRC VTA session records. | None |
db-engine-update-accounts | Runs an account update script that changes the account balances of the corresponding subscriber for the event. Scripts are defined with the shared vta group name processor db-engine account-update-script name configuration statement. The predefined script name is used as input to this function. This function adds the following attributes to the event after the function is executed:
| script-name—Name of the account update script defined in the db-engine processor. |
mailer-send | Sends e-mail notifications when certain events occur. You can specify that e-mail notifications be sent to anyone, for example, subscribers, system administrators, or an automated billing system. |
|
sae-set-interim-interval | Sets the interim accounting interval for the service session identified in the event to be the value of the interimInterval attribute currently found in the event. Before this function is called, the db-engine-calculate-interim function of the db-engine processor must be called in order to place the interimInterval attribute into the event. | current-subscriber-only—Specifies whether the function is applied only to the subscriber identified in the event or to all subscribers who have the same subscriber ID.
|
sae-set-service-timeout | Sets the service session timeout for the service session identified in the event. |
|
sae-set-user-timeout | Sets the subscriber session timeout of the subscriber identified in the event. |
|
sae-start-service | Starts the specified service subscription. |
|
sae-stop-service | Stops the specified subscription to the specified service. |
|
scripts-run-external-script | Executes an external script that is present on the local SRC file system, as previously defined with the shared vta group name processor scripts external-script name configuration statement. |
|
scripts-run-javascript | Executes a script written in the JavaScript programming language that you previously defined by using the shared vta group name processor scripts javascript name configuration statement. |
Any parameters referenced in the script itself are taken from the event and passed to the function automatically. |
On Error
For each action, you must specify what the event handler does if an error occurs; you specify this with the on-error option. If an error occurs, the event handler can do one of the following:
- Abort-event-processing—Stop processing the current event.
- Go-to-next-action—Continue with the next action, if any, in the same event handler.
- Go-to-next-event-handler—Skip any remaining actions in the current event handler and proceed to the next event handler (if any).
Related Documentation
- How the SRC VTA Works
- Configuring Event Handlers Overview
- Configuring Actions for SRC VTA Event Handlers (SRC CLI)
- Configuring Event Handlers (SRC CLI)