A
- address pools
- assigned IP subscribers
- address pools. See IP address pools
- application manager
- assigned IP subscribers
- PCMM network 1, 2
- setting timeouts
- voice over IP
C
- cable modem termination system. See CMTS devices
- classify-traffic condition
- match direction, setting
- client type 1, PCMM
- client type 2, PCMM
- CMTS devices
- CMTS locator
- monitoring
- COA script services, configuring
- configuration wizard
- configuration wizards
- conventions
- custom RADIUS authentication plug-ins
- customer support 1
D
- Data over Cable Service Interface Specifications. See DOCSIS protocol
- Diameter
- Diameter server
- DOCSIS protocol
- documentation
- domains
- Dynamic policy changes
- dynamic RADIUS authorization requests
E
- end-to-end services
- event notification, PCMM network
- configuration statements
- description
- properties, configuring
F
- filter actions
- configuring
- flexible RADIUS authentication plug-ins
- forwarding class actions
- configuring
G
- Gx router driver
- application information, configuring
- dynamic PCC rules, configuring
- flow information, configuring
- overview
- policies, configuration statements
- policies, configuring
- policy list, configuring
- QoS information, configuring
- redirect information, configuring
- static PCC rules, configuring
- steering information, configuring
I
- IP address pools
- assigned IP subscribers
- assigned IP subscribers, configuring
- local address pools, configuring
- static pools, configuring
J
- JPS (Juniper Policy Server)
- application manager-to-policy server interface, configuring
- application manager-to-policy server interface, monitoring
- architecture
- CMTS devices, monitoring
- CMTS locator, monitoring
- JPS state, monitoring
- logging, configuring
- logging, modifying
- message flows, monitoring
- message handler, monitoring
- monitoring
- C-Web interface
- SRC CLI 1, 2
- operational status
- overview
- policy server-to-CMTS interface, configuring
- policy server-to-CMTS interface, monitoring
- policy server-to-RKS interface, configuring
- policy server-to-RKS interface, monitoring
- server process, monitoring
- starting
- stopping
- subscriber address mappings, configuring
- subscriber configuration, modifying
- JSRC
- JSRC and PTSP configuration example
- Juniper Policy Server. See JPS
L
- login process
M
- manuals
- MX Series router as a PTSP network device
- MX Series router as a PTSP network device, adding
N
- NIC (network information collector)
- IP address pools, configuring
- notice icons
P
- packet mirroring, configuring
- PCMM (PacketCable Multimedia)
- application manager, role
- client type 1
- client type 2
- CMTS device, role
- configuring SAE
- 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
- 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
- video-on-demand example
- videoconferencing example
- PCMM device driver
- configuration statements
- configuring
- PCMM record-keeping server plug-in
- configuration statements
- configuring
- description
- plug-ins
- policy actions
- filter
- forwarding class
- forwarding instance
- policy groups
- configuring
- policy servers
- adding application manager groups
- adding objects to directory
- role, in PCMM architecture
- specifying application managers
- specifying SAE communities
- PTSP
- PTSP actions
- PTSP classify-traffic condition
- PTSP classify-traffic conditions
- PTSP device driver
- PTSP on MX Series router
- PTSP on MX Series router, configuring
- PTSP policer instance
- PTSP policer instance, configuring
- PTSP policies
- PTSP policies, configuring
- PTSP policy list
- PTSP policy list, configuring
- PTSP policy rules
- network, specifying
- PTSP policy rules, configuring
- PTSP session store
- PTSP device driver session store, configuring
- PTSP traffic match
- conditions, setting
Q
- QoS (quality of service)
- QoS profile-tracking plug-in
- QoS profiles, routers running JunosE Software
- how tracking works
- managing dynamically
- updating directory, using
- quality of service. See QoS
R
- RADIUS
- record-keeping server. See RKS
- RKS (record-keeping server)
- peers, configuration statements
- peers, configuring in plug-ins
- plug-in
- plug-in, configuration statements
- plug-in, configuring
- role in PCMM environment
- roaming wireless environment
S
- SAE (service activation engine)
- configuring as an application manager
- PCMM environment
- redundancy. See SAE communities
- SAE (service activation engine), configuring
- SAE communities
- configuration overview
- configuration statements
- configuring manager
- defining members
- description
- service flows
- services
- session store
- single phase resource reservation model, PCMM
- subscriber
- support, technical See technical support
T
- technical support
- text conventions defined
- traffic policies, PCMM
W
Download This Guide
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:
- Configuring RADIUS Authentication
- Creating Subscriber Access to an ISP
- Creating Web Access
- 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:
- 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
- An identifier for the wireless location:
- 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)
- The maximum transmission rate in bits per second:
- 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
- The name of the wireless location:
- Required attributes:
- 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-DayRadiusPacket.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:
- Create the SRC service to use RADIUS authentication.
See Adding a Normal Service (SRC CLI).
- 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:
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:
- 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 5Although an interval up to 5 minutes is typically recommended, for the SRC software, we recommend a minimum of 15 minutes.
- 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
