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 Event Handlers Overview
Event handlers define how the SRC VTA processes events. An event handler configuration includes the following options:
- Events—Type of event including tracking, update, or callback event; for example, a service-start tracking event.
- Priority—Priority at which event handlers are evaluated and executed. Event handlers are evaluated and executed from low to high.
- Condition—Condition that the event handler evaluates to determine whether the event handler should process the event.
- Actions—List of actions to be performed by the event handler.
You can set up multiple event handlers to process events. For example, the first event handler could retrieve the balance for a quota account, and the next event handler could refill the quota account depending on whether the condition of the second event handler is met.
When an event is received, the corresponding event type and condition configured for the event handler are evaluated based on the priority. When a condition is met, the corresponding actions are performed according to the event attributes. The action can update or add event attributes to the events for subsequent processing of the same event. An action can invoke a function provided by any processor. After an event handler has completed its processing, event processing continues with the next applicable event handler.
The SRC VTA communicates with the SAE through the Enterprise JavaBean (EJB) adapter plug-in. When an event is sent by the ejb-adapter plug-in on the SAE, it is received by the SAEEventListener, which places the event in the event queue. Because you can have multiple VTA instances, each SRC VTA has a separate SAEEventListener. The SRC VTA takes events one by one and presents them to an ordered sequence of event handlers. Each event handler includes a list of actions. If the event handler is configured to handle the event, it acts on the event based on the configured actions—for example, updating a balance or starting a service. Each action can specify a function.
The ejb-adapter plug-in can use either the round-robin algorithm or the primary/backup algorithm to send events from the SAE to the SRC VTAs. When you configure the ejb-adapter plug-in, you specify a comma-separated list of SRC VTA IP addresses or hostnames. When you use the round-robin algorithm, an outgoing event from the SAE is sent to each of the SRC VTAs specified in the comma-separated list until it is handled by one of the SRC VTAs. When you use the primary/backup algorithm, the first SRC VTA in the comma-separated list is the primary SRC VTA; all others are secondary SRC VTAs. All outgoing events from the SAE are forwarded to the primary SRC VTA until it becomes full or inaccessible. When the handling of an event fails in the primary SRC VTA, the event is sent to the secondary VTAs in a round-robin fashion until one of the secondary SRC VTAs handles the event. On successful handling of the event, the secondary SRC VTA is promoted and becomes the new primary SRC VTA.
Priority
When you configure an event handler, you need to specify the priority for evaluating and running the event handler. The priority is an integer where the smaller number has the higher priority. The event handler with the highest priority receives the event, determines whether the event’s type is the same as the event type of the event handler, and determines whether the event satisfies the condition of the event handler. When an event handler finishes processing an event, the next applicable event handler according to the priority of the event handler processes the event.
Events
Each SRC VTA event corresponds to one subscriber and contains some attributes. The SRC VTA supports the following event types:
- Service and subscriber tracking events from the SAE; for example, start or stop tracking events.
- Account update events triggered by updating database accounts.
- Callback events triggered by an SRC VTA API call.
Various events can be received by the SRC VTA from the SAE. Table 49 describes the events supported by the SRC VTA.
Table 49: SRC VTA Event Types
Event | Description |
account-update | Database update event |
callback:callid | External callback event for the specified call |
service-interim:service name | Service interim–tracking event for the specified service |
service-start:service name | Service start–tracking event for the specified service |
service-stop:service name | Service stop–tracking event for the specified service |
user-interim | User interim–tracking event |
user-start | User start–tracking event |
user-stop | User stop–tracking event |
The service-name is the name of any configured SRC service.
To process an event, the event handler must be configured to handle the particular event type. You configure which events are handled by the event handler with the shared vta group name event-handler event-handler-name events events statement. Separate events with a comma. You can configure an event handler to handle multiple event types. If an event handler is configured to handle an event, it can pass that event to a sequence of actions.
An example of an event is:
The SRC software supports wildcard characters to configure an event for the specified service in event handler.
Event Attributes
Each event carries attributes. Table 50 describes the types of attributes that are available for each type of event.
Table 50: Event Attributes
Event Type | Available Attributes |
---|---|
Service and subscriber tracking events from the SAE |
|
Account update events |
|
Callback events |
|
Glob Pattern
Use glob pattern matching when you configure an event for the specified service in event handler. The pattern matching happens only when SRC VTA receives a new service event from the SAE. After the pattern matching, the service name related event handlers are evaluated and executed based on the priority.
Use the following wildcard characters when you configure an event for the specified service in event-handler:
- *—Matches any substring.
- ?—Matches any single character.
- [range]—Matches a single character in the specified range. Ranges can have the form a-z, abcd, 0-9 or A-Z.
- [!range]—Matches a single character outside the specified character or range of characters.
An example of an event for the specified service with a wildcard pattern:
Matches any service event that starts with Int8192-Usage_ and ends with a value other than 1, 2, or 3. In this case, the ‘does not match’ condition is checked because in this case the pattern begins with “!”.
Table 51 lists some examples of events with wildcard pattern and conditions.
Table 51: Wildcard Pattern and Conditions
Wildcard Pattern | Match Condition | Does not Match Condition |
---|---|---|
Int8192-Usage | Int8192-Usage | Int8192-VTA |
Int8192-Usage?3.3 | Int8192-Usage_3.3 Int8192-Usage13.3 Int8192-Usage-3.3 | Int8192-Usage3.3 |
Int8192-Usage_[0-3%] | Int8192-Usage_1 Int8192-Usage_% | Int8192-Usage_6 |
Int8192-Usage_[1-47a-f] | Int8192-Usage_2 Int8192-Usage_7 Int8192-Usage_c | Int8192-Usage_6 Int8192-Usage_g Int8192-Usage_C |
Int8192-Usage_[!a-c] | Int8192-Usage_d Int8192-Usage_1 | Int8192-Usage_a Int8192-Usage_b |
Int8192-Usage_[!1-3] | Int8192-Usage_6 Int8192-Usage_4 | Int8192-Usage_2 Int8192-Usage_1 |
Guidelines for Using Glob Pattern in an Event Handler
Keep in mind the following considerations when using a wildcard pattern to configure service name related event in event-handler:
- Glob matches are case sensitive.
- A minor change in wildcard pattern may match unexpected events.
- Must be aware of wildcard pattern and choose a wise configuration.
Follow these guidelines when using wildcard pattern:
- Enclose patterns in double quotes.
For example:
root@c5bng-src10# set RecordUsage events "service-start:Quota[2-3]" - Verify the VTA information logs after you configure a wildcard pattern in the VTA event handler and confirm that the event handlers are loaded as expected.
- It is advised to use the same wildcard pattern throughout
the event configuration, when you use a wildcard character for a service
name in event-handler.
For example:
In GetQuota eventhandler configuration, if you use “service-start:Video-*” wildcard pattern for matching all the corresponding events and you want to match the same set of services in NoQuota eventhandler configuration, you must use the same “service-start:Video-*” wildcard pattern.
- When you use the event name with a wildcard pattern which
is also the service name, both the service name and the wildcard pattern
matching the service name are considered for processing.
For Example:
For the “service-interim:Sample[1-6]Test” event, the wildcard matches service names such as Sample[1-6]Test (which is a part of the event), Sample1Test, Sample2Test, Sample3Test, Sample4Test, Sample5Test, and Sample6Test.
- When you specify the priority for evaluating and running an event handler, you must set different priorities for different event handlers. The event gets dropped when it has more than one event handler with same priority.
Condition
Each event handler evaluates conditions to determine whether it should handle the event. You specify the condition as a script written in the JavaScript programming language that must return one of the following values:
- True—Event handler should handle the event.
- False—Event handler should not handle the event.
If the condition is met, the SRC VTA performs the corresponding actions based on the event attributes. An action invokes a function and provides the parameters required by that function to the db-engine processor. If no condition is specified, true is returned as the value. If a referenced attribute does not exist in the event, the referenced attribute’s value is null. Following is an example condition:
![]() | Note: In any condition or other JavaScript script, event attributes are referred to by enclosing them in angle < > brackets. |
Actions
When you configure an event handler, you specify actions that the event handler executes in response to an event; for example, updating an account balance, starting a service, or stopping a service. An action is performed only if the event matches the specified event type and condition you configure for the event handler. An action can invoke functions provided by any processor.
![]() | 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. |
Related Documentation
- Testing the SRC VTA Configuration Overview
- How the SRC VTA Works
- Configuring Event Handlers (SRC CLI)
- Configuring Actions Overview
- Configuring Actions for SRC VTA Event Handlers (SRC CLI)