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
Device and Service Template Configuration Overview (SRC CLI)
To configure dynamic authorization using the SIC you need to configure:
- Device template—Specifies the router make, model and capability.
- Service template—Specifies any services that you want to enable for your router. What services are available vary from router to router, so it is important that you understand the properties of your router to successfully implement custom services.
- Global service template—Specifies rendering used as part of any mode of any service template. Global service templates are used to control rendering of service-independent requests, such as Abort-Session. A global service template is unique in that its modes, attributes, and variables are available to all services that you define. Global service templates are therefore a mandatory part of any SIC COA configuration.
Device Template Configuration Overview (SRC CLI)
Device templates specify the activation behavior of services and how the router handles multiple requests.
To configure device templates, you specify the capability and its associated value. The associated value is dependent on the specified capability. Table 42 describes the available capabilities and associated values.
Table 42: Device Template Capabilities and Associated Values
Capability | Value |
---|---|
Activation—Specify service access/activation behavior. | None (default value)—Indicates that the router is not capable of activating services during initial authorization or activation. Access-Accept—Indicates that the router supports activating services only in RADIUS Access-Accept messages. CoA—Indicates that the router supports activating services in COA only. Both—Enables both Access-Accept and COA requests. |
Modification—Specify service modification behavior. | False (default value)—This attribute must be set to false. |
Bundle—Indicates whether and how the router handles multiple service activation/deactivations in one COA. | None (default value)—Indicates no bundling. Single—Indicates the router accepts multiple requests. |
Service and Global Service Template Configuration Overview (SRC CLI)
Service templates specify any services that you want to enable for your router. What services are available vary from router to router, so it is important that you understand the properties of your router to successfully implement custom services.
Global service templates specify rendering used as part of any mode of any service template. Global service templates are used to control rendering of service-independent requests, such as Abort-Session. A global service template is unique in that its modes, attributes, and variables are available to all services that you define. Global service templates are therefore a mandatory part of any SIC COA configuration.
You need to configure the following items for both the service and global service template:
- Mode
- Attributes
- Variable
Mode
Service and global service templates have groups of data called mode that each service must specify. A mode contains attributes and variables, which are explained in the next sections. It is mandatory to configure the mode for each service and global temple. You must use the provided modes; you cannot create new modes.
Table 43 lists the modes and attributes for global service templates.
Table 43: Service Template Modes
Mode | Description |
---|---|
Activation | Activates services on request from the SAE. |
Deactivation | Deactivates services on request from the SAE. |
Initial-Authorization | Initial activation of services in the Access-Accept message. |
Service-Correlation-Id | Assigns an ID number when any other mode is initiated. The SRC software uses this identification number internally. |
Service-Profile-Download | Used for Cisco routers only. See Caveat (Cisco Only). |
Table 44 lists the modes and attributes for global service templates.
Table 44: Global Service Template Modes
Mode | Description |
---|---|
Authentication | Use this mode for optional rendering of the request in the case of an Initial-Authorization. Usually this mode is empty, since no additional rendering is required. Unlike modes in service templates, this mode renders requests to the SRC software and not to the router. |
Accounting | Use this mode to control the rendering of the accounting request sent to the SAE. Accounting is a post-authorization service, and it uses the ID numbers and names from the service activation rendering. |
Abort-Session | Use this mode for rendering of RADIUS disconnect request (DM) upon abort session request from the SAE. |
Caveat (Cisco Only)
Cisco routers require an additional step to complete service activation. When the SIC activates a service on a Cisco router, the router sends an extra Access-Request to the SIC to retrieve the service profile. The SIC then sends back an Access-Accept response with VSAs representing the service profile. In response to the extra Access-Request, the SIC has to send all VSAs generated by the previous rendering process. The router then activates the service. This means that the SIC has to render the activation twice. In the second rendering a special mode, Service-Profile-Download is used.
This activation process is different from the usual scenario. Extra Access-Requests happen prior to the SIC response to an SAE request. Therefore, you can minimize the first rendering and place most of the work on the SAE download mode by doing the following:
The Service-Profile-Download mode in the supplied Cisco router configuration template is used to render the answer to the Cisco Profile Download request. The Initial-Authorization or Activation modes are used to render the first Access-Accept or COA message in the packet. To comply with the Cisco requirement to have only the service name in the first Access-Accept or COA message, the Initial-Authorization or Activation modes should contain the attribute for the service name only, and the rest of parameters should be specified using the shared sic group identifier device-template id service-template name mode service-profile-download statement.
- In the activation mode, specify only the service name.
- In the service-policy-download mode, specify the rest of the needed parameters.
See your Cisco documentation for more information.
Attributes
All modes have attributes. Attributes define which RADIUS attributes are generated as a result of rendering. All attributes create data that appears in the RADIUS attributes (such as VSAs) generated by the rendering process. It is important to understand that modes are the very core of the rendering process.
Table 45 lists the attributes, explains their parameters, and describes their behavior.
Table 45: Attributes for All Modes
Attribute | Description |
---|---|
required | If the renderer finds the attribute in the downstream AAA server response, it copies the value into the RADIUS message for the router. Otherwise, the rendering fails. Options
|
override | Whether or not the renderer finds the attribute in the downstream AAA server response, it creates the attribute name with the specified value. Options
|
default | If the renderer finds the attribute in the downstream AAA server response, it copies the value into the RADIUS message. Otherwise, it creates the attribute name with the specified value. Options
|
normal | If the renderer finds the attribute in the downstream AAA server response, it copies the value into the RADIUS message for the router. Otherwise, no action occurs. Unlike required-attribute, the rendering does not fail in this case. Options
|
parameterized | The most powerful and flexible part of the template. It generates attribute values using a format specification, which makes it the most flexible of the attributes. Options
|
Variables
Modes can also have variables, which control the rendering process. Variables are subtags under modes. You can use them to render information that is not part of RADIUS attributes. They provide inner logic for the rendering process. Nothing defined by variables appears in VSAs sent to the router.
Variables have three configuration options, described in Table 46.
Table 46: Variables
Option | Description |
---|---|
name | The variable name |
value | The value, usually an integer |
type | The data type, integer or string |
A rule for processing variables: while rendering, when the SIC encounters a variable with a new value, and that variable already has a different value, the rendering stops and sends the results to the SAE. The SAE generates a RADIUS message and resumes rendering with the new value. Thus, it creates two VSAs, one each for the variable values. This correlates with the Bundle capability.
Overriding the Service Correlation ID
You can also use variables to override the service-correlation-id mode. For example,
variable name= "CreateServiceCorrelationId" value="0"
overrides the service-correlation-id mode, so no identification number is created.
Tagged Attributes
The SIC supports tagged attributes, which are an extension of the RADIUS protocol. Refer to RFC 2868 (http://www.ietf.org/rfc/rfc2868) for a description of this feature.
If you have bundle=single and you want to send a single COA activating two services, these activation requests must have the same RADIUS attributes, but with different values. To discriminate between attributes from two separate activation requests, you must use a unique tag for each.
Specify tagged attributes using the shared sic group identifier device-template id service-template name mode (activation|deactivation|initial-authorization|service-correlation-id|service-profile-download) attributes tagged-group name statement.
![]() | Note: Each service template is restricted to have only one tagged group; for attributes configured under the tagged-group, only attributes that support tags are affected. Otherwise, it has no effect if the configured attributes does not support tagging. |
The attributes described in Table 45 are also support for tagged attribute configurations.
Related Documentation
- Managing Dynamic Services on RADIUS-Enabled Devices
- SIC Dynamic Authorization Support Overview
- How the Dynamic Authorization Process Works in the SIC