TechLibrary

[+] Expand All

[-] Collapse All

SRC PE 4.11.x Network Guide
- Copyright and Trademark Information
- Table of Contents
- List of Figures
- List of Tables
- About the Documentation
- Operating the SAE
  - Overview of the SAE
    - Role of the SAE
    - Connections to Managed Devices
    - SAE Support for Dual-Stack Configuration
    - SAE Support for Gx Router Driver
    - SAE Plug-Ins
    - Tracking and Controlling Subscriber and Service Sessions with SAE APIs
      - SAE Core API
      - SAE CORBA Remote API
    - SAE Accounting
  - Configuring the SAE (SRC CLI)
  - Managing Subscriber and Service Session Data (SRC CLI)
    - Storing Subscriber and Service Session Data
    - Configuring the Session Store Feature (SRC CLI)
    - Configuring the Number of Threads for Sessions (SRC CLI)
  - Managing SAE Data (SRC CLI)
  - Managing SAE Data (C-Web Interface)
- Using Juniper Networks Routers in the SRC Network
  - Using JunosE Routers in the SRC Network (SRC CLI)
    - COPS Connection Between JunosE Routers and the SAE
      - Highly Available Connections to JunosE Routers
    - Adding JunosE Routers and Virtual Routers (SRC CLI)
    - Configuring the SAE to Manage JunosE Routers (SRC CLI)
    - How SNMP Obtains Information from Routers for the SRC Software
    - Developing Router Initialization Scripts for Network Devices and Juniper Networks Routers
    - Specifying JunosE Router Initialization Scripts on the SAE (SRC CLI)
    - Updating Local IP Address Pools for JunosE Virtual Routers (SRC CLI)
    - Updating Quality of Service Profiles for JunosE Virtual Routers (SRC CLI)
    - Accessing the Router CLI
    - Starting the SRC Client on a JunosE Router
    - Stopping the SRC Client on a JunosE Router
    - Monitoring Interactions Between the SAE and the Router Running JunosE Software
    - Troubleshooting Problems with Managing JunosE Routers
    - Viewing the State of JunosE Device Drivers (SRC CLI)
    - Viewing Statistics for Specific JunosE Device Drivers (SRC CLI)
    - Viewing Statistics for All JunosE Device Drivers (SRC CLI)
    - Viewing the State of JunosE Device Drivers (C-Web Interface)
    - Viewing Statistics for All JunosE Device Drivers (C-Web Interface)
  - Using Devices Running Junos OS in the SRC Network (SRC CLI)
  - Managing Junos DMI Devices Using the SRC Software
  - Managing Routers Running Junos OS and Acting as a PCEF Using the SRC Software (SRC CLI)
- Using Network Devices in the SRC Network
  - Integrating Third-Party Network Devices into the SRC Network (SRC CLI)
    - Integrating Network Devices into the SRC Network Overview
    - Logging In Subscribers and Creating Sessions
    - Configuration Tasks for Integrating Third-Party Network Devices (SRC CLI)
    - Setting Up Script Services
    - Adding Objects for Network Devices (SRC CLI)
    - Adding Virtual Router Objects (SRC CLI)
    - Setting Up SAE Communities (SRC CLI)
      - Configuring the SAE Community Manager
      - Specifying the Community Manager in the SAE Device Driver
    - Configuring SAE Properties for the Event Notification API (SRC CLI)
    - Developing Router Initialization Scripts for Network Devices and Juniper Networks Routers
    - Copying Initialization Scripts to the C Series Controller
    - Specifying Initialization Scripts on the SAE (SRC CLI)
    - Using SNMP to Retrieve Information from Network Devices
    - Configuring Global SNMP Communities in the SRC Software (SRC CLI)
    - Using the NIC Resolver in Environments That Have Third-Party Devices (SRC CLI)
- Locating Subscriber Management Information
  - Locating Subscriber Information with the NIC
    - Locating Subscriber Management Information
      - NIC Client/Server Mode
      - NIC Local Host Mode
    - Mapping Subscribers to a Managing SAE
    - High Availability for NIC
      - High Availability in Existing NIC Configurations
      - NIC Replication
    - Planning a NIC Implementation
    - NIC Configuration Scenarios
    - NIC Agents Used in the NIC Configuration Scenarios
    - Router Initialization Scripts with NIC Configuration Scenarios
  - Configuring the NIC (SRC CLI)
    - Configuration Statements for the NIC
    - Before You Configure the NIC
    - Configuring the NIC (SRC CLI)
    - Reviewing and Changing Operating Properties for the NIC (SRC CLI)
      - Reviewing the Default NIC Operating Properties
      - Changing NIC Operating Properties
    - Configuring NIC Replication (SRC CLI)
    - Configuring a NIC Scenario (SRC CLI)
    - Configuring Advanced NIC Features
    - Verifying Configuration for the NIC (SRC CLI)
    - Starting the NIC (SRC CLI)
    - Testing a NIC Resolution (SRC CLI)
    - Stopping a NIC Host on a C Series Controller (SRC CLI)
    - Restarting the NIC (SRC CLI)
    - Restarting a NIC Agent (SRC CLI)
    - Restarting a NIC Resolver (SRC CLI)
    - Changing NIC Configurations (SRC CLI)
  - Obtaining Interface Configuration for OnePopStaticRouteIp or OnePopVrfIp
  - Configuring Applications to Communicate with an SAE
    - NIC Proxy Configuration Overview
    - Before You Configure a NIC Proxy
  - Configuring SRC Applications to Communicate with an SAE (SRC CLI)
  - Developing Applications That Use NIC
  - NIC Resolution Process
    - NIC Resolution Process Overview
      - NIC Realms
      - Key to Value Resolution
    - NIC Data Types
    - Constraints as NIC Data Types
  - NIC Configuration Scenarios
    - NIC Configuration Scenarios Overview
    - OnePop Scenario
    - OnePopPcmm Scenario
      - Centralized Configuration
      - Distributed Configuration
    - OnePopDynamicIp Scenario
      - Centralized Configuration
      - Distributed Configuration
    - OnePopSharedIp Scenario
      - Centralized Configuration
      - Distributed Configuration
    - OnePopStaticRouteIp Scenario
      - Centralized Configuration
      - Distributed Configuration
    - OnePopVrfIp Scenario
      - Centralized Configuration
      - Distributed Configuration
    - OnePopAcctId Scenario
    - OnePopDualStackAcctId Scenario
      - SAE Plug-in Agent Considerations
    - OnePopLogin Scenario
      - Centralized Configuration
      - Distributed Configuration
    - OnePopLoginPull Scenario
    - OnePopPrimaryUser
      - Centralized Configuration
      - Distributed Configuration
    - OnePopDnSharedIp Scenario
      - Centralized Configuration
      - Distributed Configuration
    - OnePopAllRealms Scenario
    - OnePopTunnel Scenario
      - Centralized Configuration
    - OnePopPrefixIp Scenario
    - MultiPop Scenario
- Providing Admission Control with SRC ACP
  - Overview of Providing Admission Control with SRC ACP
  - Configuring Admission Control (SRC CLI)
    - Configuration Statements for SRC ACP
    - Configuring SRC ACP (SRC CLI)
    - Creating Grouped Configurations for SRC ACP (SRC CLI)
    - Configuring Local Properties for SRC ACP (SRC CLI)
    - Configuring the SAE for SRC ACP (SRC CLI)
    - Configuring SRC ACP Properties (SRC CLI)
    - Configuring SRC ACP to Manage the Edge Network (SRC CLI)
    - Configuring SRC ACP to Manage the Backbone Network (SRC CLI)
    - Defining SRC ACP Congestion Point Usage Trap Thresholds (SRC CLI)
  - Configuring Congestion Point Classification (SRC CLI)
    - Congestion Point Classification Overview
      - Congestion Point Classification Scripts
      - Congestion Point Profiles
    - Configuration Statements for Congestion Point Classification
    - Classifying Congestion Points (SRC CLI)
      - Configuring Targets and Criteria for Classification Scripts
      - Configuring Classification Scripts Contents for Classification Scripts
      - Configuring Congestion Point Classification Targets
        Congestion Point Classification Criteria
    - Defining a Congestion Point Profile (SRC CLI)
    - Congestion Point Expressions
  - Managing SRC ACP (SRC CLI)
  - Monitoring Admission Control (SRC CLI)
  - Monitoring Admission Control (C-Web Interface)
- Using External Subscriber Monitor
  - Configuring External Subscriber Monitor with the SRC CLI
  - Monitoring External Subscriber Events with the SRC CLI
  - Monitoring External Subscriber Events with the C-Web Interface
- Using the Subscriber Information Collector
  - Overview of the Subscriber Information Collector
    - Subscriber Information Collector Overview
    - Managing Dynamic Services on RADIUS-Enabled Devices
    - SIC Dynamic Authorization Support Overview
      - Rendering
    - How the Dynamic Authorization Process Works in the SIC
    - Dynamic Authorization Targets (SRC CLI)
    - RADIUS Authentication/Authorization and Accounting Data Flow
    - Local and Shared Configurations for the SIC (SRC CLI)
      - Local Configuration
      - Shared Configuration
    - Accounting Method and Target (SRC CLI)
      - Using the Proxy RADIUS Accounting Method
    - Authentication Route Targets (SRC CLI)
    - Request Routing (SRC CLI)
      - Explicit Routing Rules
      - Implicit Routing Rules
    - SIC Editing Rules (SRC CLI)
    - RADIUS and Diameter Configuration for the SIC Overview (SRC CLI)
      - RADIUS Accounting and Authentication Listeners
      - SIC Diameter Server
        SIC Diameter Server Configuration Overview
      - RADIUS Network Elements
        Configuring Upstream RADIUS Network Elements Overview
        Configuring Downstream RADIUS Network Elements Overview
      - Using the Proxy Function to Define Implicit Routing Rules
    - Failover Policy
      - Failover Mode
        Round-Robin
        Primary or Backup
    - RADIUS and Diameter Transports
    - SIC Dictionaries and Device Models Overview (SRC CLI)
    - SIC Local Realms Overview
    - SIC Event Logging Overview (SRC CLI)
    - SNMP Support for the SIC Overview (SRC CLI)
  - Configuring the Subscriber Information Collector with the SRC CLI
    - SIC Configuration Summary
      - SIC RADIUS Configuration Summary (SRC CLI)
      - SIC RADIUS Dynamic Authorization Configuration Summary (SRC CLI)
      - SIC Diameter Configuration Summary (SRC CLI)
      - Configuring Management of RADIUS-Enabled Devices for the SIC (SRC CLI)
    - Configuring the Connection Between the SIC and the Juniper Networks Database (SRC CLI)
    - Creating an SIC Group and Server (SRC CLI)
    - Creating an SIC Server Instance (SRC CLI)
    - Configuring Dictionaries for the SIC Group (SRC CLI)
    - Configuring the Device Models Supported by the SIC Group (SRC CLI)
    - Configuring the RADIUS Accounting Listener for the SIC Group (SRC CLI)
      - Configuring the RADIUS Accounting Listener Queue Limits (SRC CLI)
      - Configuring the RADIUS Accounting Listener Transport (SRC CLI)
    - Configuring the RADIUS Authentication Listener for the SIC Group (SRC CLI)
      - Configuring the RADIUS Authentication Listener Queue Limits (SRC CLI)
      - Configuring the RADIUS Authentication Listener Transport (SRC CLI)
    - Configuring the Outbound RADIUS Transport of the SIC Group (SRC CLI)
    - Configuring the RADIUS Transport for an SIC Server (SRC CLI)
    - Configuring the SIC Diameter Server (SRC CLI)
      - Configuration Statements for the SIC Diameter Server (SRC CLI)
      - Configuring the SIC Diameter Server Identity (SRC CLI)
      - Configuring the SIC Diameter Server Peer (SRC CLI)
    - Configuring Upstream and Downstream RADIUS Network Elements (SRC CLI)
      - Configuration Statements for Downstream Network Elements and Accounting and Authentication Targets (SRC CLI)
      - Configuration Statements for Upstream Network Elements, Accounting and Authentication Clients, and Dynamic Authorization Targets (SRC CLI)
      - Creating a Network Element (SRC CLI)
      - Configuring the Device Models Supported in the Network Element (SRC CLI)
      - Configuring Upstream Network Elements and Accounting and Authentication Clients (SRC CLI)
      - Configuring Upstream Network Elements and Dynamic Authorization Targets (SRC CLI)
      - Configuring Downstream Network Elements and Accounting and Authentication Targets (SRC CLI)
        Configuring SIC Accounting Targets (SRC CLI)
        Configuring SIC Authentication Targets (SRC CLI)
      - Configuration Statements for SIC Group Failover Mode and Policy (SRC CLI)
      - Configuring Failover Mode and Policy (SRC CLI)
        Configuring Failover Mode (SRC CLI)
        Configuring Fast Fail Options for the Failover Policy
        Configuring Retry Options for the Failover Policy
    - Configuring What Realms Are Local to the SIC Group (SRC CLI)
    - Configuration Statements for SIC Editing Rules (SRC CLI)
    - Configuring the Optional Editing Rules Used by the SIC Group (SRC CLI)
    - Configuring the Accounting Method Used by the SIC Group (SRC CLI)
      - Configuring Proxy RADIUS as the Accounting Method (SRC CLI)
    - Configuring the Authentication Target Used by the SIC Server (SRC CLI)
    - Configuring Request Routing (SRC CLI)
      - Configuration Statements for SIC Explicit Accounting Routing Rules
      - Configuration Statements for SIC Explicit Authentication Routing Rules
      - Configuring Explicit Routing (SRC CLI)
      - Configuring Implicit Routing (SRC CLI)
    - Configuring Event Logging for an SIC Server (SRC CLI)
    - Configuring SNMP for the SIC Group (SRC CLI)
    - Example: Basic SIC Group Configuration (SRC CLI)
    - Configuring the NAS Groups (SRC CLI)
      - Configuring NAS Groups
      - Configuring the NAS Group Device Capabilities (SRC CLI)
      - Classifying Interfaces
      - Configuring NAS Group Routes
    - Configuring the SAE to Manage AAA Devices
    - Configuring AAA Policies (SRC CLI)
      - Configuring AAA Policy Lists
      - Configuring AAA Policy Rules
      - Configuring Template Activation Actions
  - Device and Service Templates for Dynamic Authorization (SRC CLI)
    - Device and Service Template Configuration Overview (SRC CLI)
      - Device Template Configuration Overview (SRC CLI)
      - Service and Global Service Template Configuration Overview (SRC CLI)
        Mode
        Caveat (Cisco Only)
        Attributes
        Variables
        Overriding the Service Correlation ID
        Tagged Attributes
    - Configuring Device Templates (SRC CLI)
    - Configuring the Device Capabilities Supported in the Device Template (SRC CLI)
    - Configuration Statements for SIC Service Templates (SRC CLI)
    - Configuring SIC Service Templates (SRC CLI)
    - Configuration Statements for Tagged Attributes in SIC Service Templates (SRC CLI)
    - Configuring Tagged Attributes in SIC Service Templates (SRC CLI)
    - Configuration Statements for SIC Global Service Templates (SRC CLI)
    - Configuring Global Service Templates (SRC CLI)
    - Sample Service Templates
      - Juniper Networks Routers Service Template
      - Cisco Router Service Template
  - Monitoring the Subscriber Information Collector with the SRC CLI
- Controlling Volume Usage with the SRC VTA
  - Overview of Controlling Volume Usage with the SRC VTA
    - SRC VTA Overview
    - SRC VTA Architecture and Connections to Other SRC Components
    - How the SRC VTA Works
    - SRC VTA Operation
    - Configuring Event Handlers Overview
    - Configuring Actions Overview
      - On Error
    - Managing SRC VTA Accounts and Sessions Overview
      - Identifying Subscribers, SAEs, and Sessions
      - Managing SRC VTA Accounts and Sessions
    - Adjusting the Interim Accounting Interval Overview
    - Locating the SAE That Manages a Subscriber for the SRC VTA
    - Using JavaScript Programs in SRC VTA Configurations
    - SRC VTA SOAP Interface
      - SRC VTA SOAP Interface URL
    - Example: Limiting Subscriber Access Based on Account Balances
  - Prerequisites for Running the SRC VTA
  - Configuring the SRC VTA (SRC CLI)
    - Configuring an SRC VTA Shared Group Configuration (SRC CLI)
      - Creating and Configuring an SRC VTA Shared Group Configuration (SRC CLI)
      - Keys Used to Specify the Subscriber ID Solution (SRC CLI)
    - Configuring the Connection Between the SRC VTA and the External Account and Session Database (SRC CLI)
    - Cleaning Up the Sessions Records and SessionBalanceChanges Records from the SRC VTA Database (SRC CLI)
    - Configuring Actions for SRC VTA Event Handlers (SRC CLI)
    - Configuring Event Handlers (SRC CLI)
    - Configuring Event Queues for SRC VTA Groups (SRC CLI)
    - Configuring the DB-Engine Processor for the SRC VTA Group (SRC-CLI)
    - Configuring the Mailer Processor for the SRC VTA Group (SRC CLI)
      - Configuring the SRC VTA Mailer Processor to Send E-Mail Notifications (SRC CLI)
      - Configuring the SRC VTA to Send E-Mail Notifications (SRC CLI)
    - Configuring the SRC VTA Scripts Processor (SRC CLI)
    - Configuring SRC VTA Logging (SRC CLI)
      - Logging SRC VTA Messages to a Text File
      - Logging SRC VTA Messages to a System Logging Server
    - Enabling, Disabling, and Restarting the SRC VTA (SRC CLI)
    - Enabling the SOAP Interface for an SRC VTA Group (SRC CLI)
    - Methods for the SRC Volume Tracking Application SOAP Interface
    - SOAP Fault Codes for the SRC Volume Tracking Application
    - Using One SRC VTA Account for Multiple Subscriber Sessions
  - Managing the SRC VTA (SRC CLI)
  - Monitoring and Testing the SRC VTA

Download This Guide

Download this guide: SRC PE 4.11.x Network Guide

Adding JunosE Routers and Virtual Routers (SRC CLI)

The SAE uses router and virtual router objects to manage interfaces on JunosE virtual routers. Each JunosE router in the SRC network and its virtual routers (VRs) must have a configuration.

There are three ways to add routers:

Adding Operative JunosE Routers and Virtual Routers

To add routers and JunosE VRs that are currently operative and have an operating SNMP agent:

In operational mode, enter the following command:
user@host> request network discovery network network <community community>
where:

network—Address (with or without mask) of the network to discover

community—Name of the SNMP community to which the devices belong

If you add a router using the discover network feature, the software adds the IP address of the first SNMP agent on the router to respond to the discover request.

After you add routers and JunosE VRs through network discovery, configure the virtual router’s managing SAE address.

Adding Routers Individually (SRC CLI)

Use the following configuration statements to add a router:

shared network device name {accounting-per-attachment;description description ;device-type (junose | junos | pcmm ); management-address management-address ; no-accounting-per-attachment;qos-profile [ qos-profile ...];}

To add a router:

From configuration mode, access the configuration statements that configure network devices. This procedure uses junose_boston as the name of the router.
user@host# edit shared network device junose_boston
The same procedure can be used for routers running Junos OS.

(Optional) Disable the accounting-per-attachment feature to calculate accounting for each policy list on the basis of the accounting flag status of each policy rule in the policy list.

[edit shared network device junose_boston]user@host# set no-accounting-per-attachment

Note:

To enable the accounting-per-attachment feature, configure the accounting-per-attachment option at the [edit shared network device] hierarchy.
By default, the accounting-per-attachment feature is not set.
You must restart the sscc connection for the configuration changes to take effect.
You can configure the accounting-per-attachment feature under the [edit shared sae group group-name configuration driver junose] or [edit shared network device] hierarchy. The settings configured under the [edit shared network device] hierarchy override the settings under the [edit shared sae group group-name configuration driver junose] hierarchy.

(Optional) Add a description for the router.
[edit shared network device junose_boston] user@host# set description description
(Optional) Add the IP address of the router.
[edit shared network device junose_boston] user@host# set management-address management-address
(Optional) Specify the type of device that you are adding.
[edit shared network device junose_boston] user@host# set device-type junose
(Optional) Specify quality of service (QoS) profiles that are configured on the router.
[edit shared network device junose_boston] user@host# set qos-profile [ qos-profile ...]

(Optional) Verify your configuration.

[edit shared network device junose_boston] 
user@host# show 
no-accounting-per-attachment;
description "Juniper Networks E320";
management-address 10.10.8.27;
device-type junose;
qos-profile dhcp-default;
interface-classifier {
 rule rule-0 {
    script #;
  }
}

Adding Virtual Routers Individually (SRC CLI)

You can add a virtual router to an existing router.

Use the following configuration statements to add a virtual router:

shared network device name virtual-router name {sae-connection [ sae-connection ...]; snmp-read-community snmp-read-community ; snmp-write-community snmp-write-community ; scope [ scope ...]; local-address-pools local-address-pools ; static-address-pools static-address-pools ; tracking-plug-in [ tracking-plug-in ...];user-tracking-plug-in user-tracking-plug-in ...];authentication-plug-in [ authentication-plug-in ...];dual-stack-delay delayvpn-id vpn-id;}

To add a virtual router:

From configuration mode, access the configuration statements for virtual routers. This procedure uses junose_boston as the name of the router and vr1 as the name of the virtual router.
user@host# edit shared network device junose_boston virtual-router vr1
Specify the addresses of SAEs that can manage this router. This step is required for the SAE to work with the router.
[edit shared network device junose_boston virtual-router vr1] user@host# set sae-connection [ sae-connection ...]
To specify the active SAE and the redundant SAE, enter an exclamation point (!) after the hostname or IP address of the connected SAE. For example:
[edit shared network device junose_boston virtual-router vr1]user@host# set sae-connection [sae1! sae2!]
(Optional) Specify an SNMP community name for SNMP read-only operations for this virtual router.
[edit shared network device junose_boston virtual-router vr1] user@host# set snmp-read-community snmp-read-community
(Optional) Specify an SNMP community name for SNMP write operations for this virtual router.
[edit shared network device junose_boston virtual-router vr1] user@host# set snmp-write-community snmp-write-community
(Optional) Specify service scopes assigned to this virtual router. The scopes are available for subscribers connected to this virtual router for selecting customized versions of services.
[edit shared network device junose_boston virtual-router vr1] user@host# set scope [ scope ...]
(Optional) Specify the list of IP address pools that a virtual router currently manages and stores.
[edit shared network device junose_boston virtual-router vr1] user@host# set local-address-pools local-address-pools
(Optional) Specify the list of IP address pools that a virtual router manages but does not store.
[edit shared network device junose_boston virtual-router vr1] user@host# set static-address-pools static-address-pools
(Optional) Specify the plug-ins that track interfaces that the SAE manages on this virtual router.
[edit shared network device junose_boston virtual-router vr1] user@host# set tracking-plug-in [ tracking-plug-in ...]
(Optional) Specify a list of plug-ins that are notified of interface events for this virtual router.
[edit shared network device junose_boston virtual-router vr1] user@host# set authentication-plug-in [ authentication-plug-in ...]
(Optional) Specify a single-tracking plug-in or a list of tracking plug-ins used to track subscriber sessions associated with this virtual router.
[edit shared network device junose_boston virtual-router vr1] user@host# set user-tracking-plug-in [ user-tracking-plug-in ...]
Configure the delay time (in milliseconds) for dual-stack interfaces. dual-stack-delay is not configured by default.
[edit shared sae group west-region configuration driver junose] user@host# dual-stack-delay delay
(Optional) Specify the VPN identifier used by this virtual router. For edge devices, you can specify VRF instead of a string to use the VRF instance reported by the device as the VPN identifier. For example, if you specify VRF for a JunosE router, the VPN identifier is the name of the virtual router.
[edit shared network device junose_boston virtual-router vr1] user@host# set vpn-id (vpn-id | VRF)