Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

 A  C  D  E  F  G  I  J  L  M  N  P  Q  R  S  T  W

 

A

address pools    
assigned IP subscribers    
configuring
address pools.     See IP address pools    
application manager    
role, in PCMM environment
assigned IP subscribers    
PCMM network    12
address pools
IP address pools
setting timeouts
voice over IP
 

C

cable modem termination system.     See CMTS devices    
client type 1, PCMM
client type 2, PCMM
CMTS devices    
adding objects to directory    
SRC CLI
adding virtual router objects to directory    
SRC CLI
configuration statements    12
role
CMTS locator    
monitoring    
C-Web interface
SRC CLI
COA script services, configuring
configuration wizard    
fair usage    
configuration overview
running
running    12
configuration wizards    
fair usage    
overview
overview    12
conventions    
notice icons
text
custom RADIUS authentication plug-ins
customer support    1
contacting JTAC
 

D

Data over Cable Service Interface Specifications.     See DOCSIS protocol    
Diameter    
peers    
configuring    12
SNMP support
Diameter server    
clients, viewing    
SRC CLI
message flows, viewing    
SRC CLI
message handler, viewing    
SRC CLI
monitoring    
SRC CLI
peers, viewing    
SRC CLI
server process, viewing    
SRC CLI
server requests, viewing    
SRC CLI
statistics, viewing    
SRC CLI
status, viewing    
SRC CLI
DOCSIS protocol
documentation    
comments on
domains    
IP service edge
IP subscriber edge
radio frequency
dynamic RADIUS authorization requests    
RADIUS packets, defining    12
 

E

end-to-end services
event notification, PCMM network    
configuration statements
description
properties, configuring    
SRC CLI
 

F

flexible RADIUS authentication plug-ins    
configuring
 

G

Gx router driver    
application information, configuring    
SRC CLI
dynamic PCC rules, configuring    
SRC CLI
flow information, configuring    
SRC CLI
Gx policies for dynamic PCC rules, configuring    
SRC CLI
Gx policies for static PCC rules, configuring    
SRC CLI
overview
policies, configuration statements    
SRC CLI
policies, configuring    
SRC CLI
policy list, configuring    
SRC CLI
QoS information, configuring    
SRC CLI
redirect information, configuring    
SRC CLI
static PCC rules, configuring    
SRC CLI
steering information, configuring    
SRC CLI
 

I

intelligent-service-edge device driver    
configuring initialization scripts    
SRC CLI
IP address pools    
assigned IP subscribers
assigned IP subscribers, configuring    
SRC CLI
local address pools, configuring    
SRC CLI
static pools, configuring    
SRC CLI
 

J

JPS (Juniper Policy Server)    
application manager-to-policy server interface, configuring
application manager-to-policy server interface, monitoring    
C-Web interface    12
SRC CLI
architecture
CMTS devices, monitoring    
C-Web interface
CMTS locator, monitoring    
C-Web interface
SRC CLI
JPS state, monitoring
logging, configuring
logging, modifying
message flows, monitoring    
C-Web interface
SRC CLI
message handler, monitoring    
C-Web interface
SRC CLI
monitoring    
C-Web interface
SRC CLI    12
operational status
overview
policy server-to-CMTS interface, configuring
policy server-to-CMTS interface, monitoring    
C-Web interface    12
SRC CLI
policy server-to-RKS interface, configuring
policy server-to-RKS interface, monitoring    
C-Web interface
SRC CLI
server process, monitoring    
C-Web interface
SRC CLI
starting    
SRC CLI
stopping    
SRC CLI
subscriber address mappings, configuring
subscriber configuration, modifying
Juniper Policy Server.     See JPS    
 

L

login process    
assigned IP subscribers, PCMM
 

M

manuals    
comments on
 

N

NIC (network information collector)    
IP address pools, configuring    
SRC CLI
notice icons
 

P

packet mirroring, configuring
PCMM (PacketCable Multimedia)    
application manager, role
client type 1
client type 2
CMTS device, role
configuring SAE    
SRC CLI
creating sessions
description
end-to-end QoS architecture
end-to-end services
integrating SRC software
IP service edge domain
IP subscriber edge domain
logging in subscribers    
assigned IP method
overview
overview
policy server, role
provisioning end-to-end services
record-keeping server
RF domain
SAE
SAE communities
session store
single-phase resource reservation model
SRC software in    
description
traffic profiles
video-on-demand example
videoconferencing example
PCMM device driver    
configuration statements
configuring    
SRC CLI
PCMM record-keeping server plug-in    
configuration statements
configuring    
SRC CLI
description
plug-ins    
PCMM record-keeping server plug-in
policy servers    
adding application manager groups    
SRC CLI
adding objects to directory    
SRC CLI
role, in PCMM architecture
specifying application managers    
SRC CLI
specifying SAE communities    
SRC CLI
 

Q

QoS (quality of service)    
PCMM environments    
end-to-end QoS architecture
extending to service edge domain
extending to subscriber edge domain
searching for policies in directory
QoS profile-tracking plug-in    
description
QoS profiles, routers running JunosE Software    
how tracking works
managing dynamically
updating directory, using    
qosProfilePublish
quality of service.     See QoS    
 

R

RADIUS    
vendor-specific attributes for wireless ISP roaming
record-keeping server.     See RKS    
RKS (record-keeping server)    
peers, configuration statements
peers, configuring in plug-ins    
SRC CLI
plug-in
plug-in, configuration statements
plug-in, configuring    
SRC CLI
role in PCMM environment
roaming wireless environment
 

S

SAE (service activation engine)    
configuring as an application manager    
SRC CLI
PCMM environment
redundancy.     See SAE communities    
SAE (service activation engine), configuring    
community manager    
SRC CLI
event notification API properties    
SRC CLI
PCMM device driver    
SRC CLI    12
SAE communities    
configuration overview    
SRC CLI
configuration statements
configuring manager    
SRC CLI
defining members    
SRC CLI
description
service flows
services    
voice over IP (VoIP)
session store    
in PCMM environment
single phase resource reservation model, PCMM
subscriber    
wireless environment
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
traffic policies, PCMM
 

W

wireless environment

Configuring Subscriber Access for a Wireless Location

Tasks to use the SAE to manage a wireless access point that participates in a roaming agreement are:

  1. Configuring RADIUS Authentication
  2. Creating Subscriber Access to an ISP
  3. Creating Web Access
  4. Setting Idle Timeout Options for the SAE

Configuring RADIUS Authentication

You configure RADIUS authentication for users who connect from a wireless location, and set up RADIUS authentication to support a roaming environment between wireless Internet service providers. You can use the Flexible RADIUS Authentication plug-in that is provided with the SRC software, or you can create a custom RADIUS authentication plug-in.

Configuring a Custom RADIUS Authentication Plug-In

If you create a custom plug-in, be sure that it supports the same RADIUS attributes as those configured for the flexible RADIUS authentication plug-in. See Configuring the Flexible RADIUS Authentication Plug-In.

For information about creating a custom plug-in, see SAE CORBA Plug-In Service Provider Interface (SPI) on the Juniper Networks website at: https://www.juniper.net/techpubs/software/management/src/api-index.html.

Configuring the Flexible RADIUS Authentication Plug-In

The default flexible RADIUS authentication plug-in, flexRadiusAuth, provides support for RADIUS vendor-specific attributes for WISPr, which are listed in the following procedure. These attributes use the IANA private enterprise number 14122 assigned to the Wi-Fi Alliance. For more information about these attributes, see http://www.wi-fialliance.org/opensection/wispr.asp.

You should be familiar with the general procedure for configuring the flexible RADIUS authentication plug-in before configuring it to include the WISPr attributes. For information about configuring the flexible RADIUS authentication plug-in, see Configuring Tracking Plug-Ins (SRC CLI).

When you configure the plug-in, you can use the following standard attribute values to set values in authentication response packets:

  • setAcctInterimTime
  • setSubstitution
  • setTerminateTime

Examples in the following procedure show how you can use these attribute values.

To configure the plug-in to support a roaming environment:

  1. Configure attributes.
    • Required attributes:
      • An identifier for the wireless location:
        vendor-specific.WISPr.Location-ID=Identifier

        This attribute can be an interface description (ifAlias) or other value that identifies the JunosE interface to which the wireless access point connects.

      • The URL of the start page returned by the RADIUS server of the ISP:
        vendor-specific.WISPr.Redirection-URL=Command to make the URL available to the SRC software

        For example:

        vendor-specific.WISPr.Redirection-URL=setProperty(“ startURL=%s” % ATTR)

        The default configuration sets a session property named startURL.

      • The URL of a page that a subscriber can use to log out of the network:
        vendor-specific.WISPr.Logoff-URL=URL of a log out page
    • Bandwidth attributes (recommended):
      • The maximum transmission rate in bits per second:
        vendor-specific.WISPr.Bandwidth-Max-Up=Command to make the rate available to the SRC software

        For example:

        vendor-specific.WISPr.Bandwidth-Max-Up=setSubstitution(“ max_up_rate=%s” % ATTR)
      • The maximum receive rate in bits per second:
        vendor-specific.WISPr.Bandwidth-Max-Down=Command to make the rate available to the SRC software

        For example:

        vendor-specific.WISPr.Bandwidth-Max-Down=setSubstitution(“ max_down_rate=%s” % \ ATTR)
    • Optional attributes:
      • The name of the wireless location:
        vendor-specific.WISPr.Location-Name=Name of the wireless location
      • The date and time that the subscriber session is to end:
        vendor-specific.WISPr.Session-Terminate-Time=Command to set the session terminate time

        For example:

        vendor-specific.WISPr.Session-Terminate-Time=setTerminateTime(ATTR)
      • The end of the subscriber session at the end of the billing day:
        vendor-specific.WISPr.Session-Terminate-End-Of-Day=ATTR or setTerminateTime("00:00:00")

        If the operator of the wireless location does not support daily billing, do not configure this attribute, and remove it if present.

      • A service type for billing:
        vendor-specific.WISPr.Billing-Class-Of-Service=Service type
  2. For each attribute that you configure, configure the packet type to which the attribute applies. Table 5 shows the packet types associated with each attribute.

    Table 5: Packet Types for RADIUS Attributes

    RADIUS Attribute

    Associated RADIUS Packet Definition

    vendor-specific.WISPr.Location-ID

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Location-ID

    vendor-specific.WISPr.Redirection-URL

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Redirection-URL

    vendor-specific.WISPr.Logoff-URL

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Logoff-URL

    vendor-specific.WISPr.Bandwidth-Max-Up

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Bandwidth-Max-Up

    vendor-specific.WISPr.Maximum-Max-Down

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Maximum-Max-Down

    vendor-specific.WISPr.Location-Name

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Location-Name

    vendor-specific.WISPr.Session-Terminate-Time

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Session-Terminate-Time

    vendor-specific.WISPr.Session-Terminate-
    End-Of-Day

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Session-Terminate-End-Of-Day

    vendor-specific.WISPr.Billing-Class-Of-Service

    RadiusPacket.stdAuth.auth.vendor-specific.WISPr.Billing-Class-Of-Service

Creating Subscriber Access to an ISP

Configure a service that lets subscribers connect to an ISP through a captive portal, a single webpage to which subscribers connect. The policies associated with the service should specify a Junos OS policing or JunosE rate-limiting policy to set the maximum bandwidth at which:

  • A subscriber can send traffic.
  • A subscriber can receive traffic.

When you configure the policies, define the bandwidth values as parameters so that the policies can be applied across a number of subscribers.

To configure a service to access the ISP:

  1. Create the SRC service to use RADIUS authentication.

    See Adding a Normal Service (SRC CLI).

  2. Create a policy group the sets the maximum bandwidth at which a subscriber can send traffic, and the maximum bandwidth at which a subscriber can receive traffic. Use parameters to set these values.

    To configure policies, see:

    • Configuring Policy Groups (SRC CLI)
    • Configuring Global Parameters (SRC CLI)
    • Configuring Local Parameters (SRC CLI)

For example, you can create a policy configuration that includes:

  • A local parameter named max_up_rate that sets the maximum rate at which the subscriber can send data
  • A local parameter named max_down_rate that sets the maximum rate at which the subscriber can receive data
  • A policy group Receive(Downstream) that references max_down_rate
  • A policy group Send(Upstream) that references max_up_rate

Substitutions for these parameters can then be referenced in the RADIUS attributes:

vendor-specific.WISPr.Bandwidth-Max-Up=setSubstitution(“ max_up_rate=%s” % ATTR)vendor-specific.WISPr.Bandwidth-Max-Down=setSubstitution(“ max_down_rate=%s” % ATTR)

Creating Web Access

When subscribers connect to and log in to a wireless access point, they are directed to a single webpage that is referred to as a captive portal page. This page is part of a service selection portal. A captive portal page receives and manages redirected Web requests. The SRC Application Library provides an unsupported, demonstration application for a residential service selection portal.

When creating a captive portal page for a wireless roaming environment, configure the page to:

  • Start an access service that is configured to be authenticated by the RADIUS server of the ISP.
  • After the access service starts, redirect the subscriber to the page specified by the Redirect-URL RADIUS attribute. This page is the start page for the subscriber's home ISP.

    You can retrieve the URL of the start page from the service session property startURL. Note that startURL is the default name used for the flexible RADIUS authentication plug-in; you can assign a different name to this property.

    You can use the Subscriber.readSubscription() method in the Common Object Request Broker Architecture (CORBA) remote application programming interface (API) to retrieve the redirect URL.

Note that when you develop the portal, you can use the following methods in the SAE CORBA remote API to retrieve session data after the access service starts:

  • Subscriber.readSubscriber()
  • Subscriber.readSubscription()

For more information about these methods, see the SAE CORBA remote API documentation on the Juniper Networks website at

https://www.juniper.net/techpubs/software/management/src/api-index.html.

Setting Idle Timeout Options for the SAE

You can configure the following options to ensure that the timeout values are consistent with the requirements for your environment:

  • Idle timeout—Defines how long a session is idle before the connection is closed.
  • Adjust session time—Adjusts the session time reported in an accounting messaged by subtracting idle time from the time if the session times out.

To configure the timeout settings:

  1. Configure the service activation authentication through a RADIUS server to return an idle timeout. This configuration requires that the RADIUS server returns the idle timeout vendor-specific attribute (VSA).

    or

    Configure the idle timeout in the SRC service definition. For example:

    [edit services global service service1]user@host# set idle-timeout 5

    Although an interval up to 5 minutes is typically recommended, for the SRC software, we recommend a minimum of 15 minutes.

  2. Configure the adjust-session-time statement for the SAE to ensure that session time is accurately reported for accounting purposes. For example:
    [edit shared sae group wireless configuration]user@host# set idle-timeout adjust-session-time

Related Documentation

Modified: 2016-05-27