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
- 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
- peers
- SNMP support
- Diameter server
- DOCSIS protocol
- documentation
- domains
- dynamic RADIUS authorization requests
E
- end-to-end services
- event notification, PCMM network
- configuration statements
- description
- properties, configuring
F
- flexible RADIUS authentication plug-ins
G
- Gx router driver
- application information, configuring
- dynamic PCC rules, configuring
- flow information, configuring
- Gx policies for dynamic PCC rules, configuring
- Gx policies for static PCC rules, configuring
- overview
- policies, configuration statements
- policies, configuring
- policy list, configuring
- QoS information, configuring
- redirect information, configuring
- static PCC rules, configuring
- steering information, configuring
I
- intelligent-service-edge device driver
- configuring initialization scripts
- 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
- Juniper Policy Server. See JPS
L
- login process
M
- manuals
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 servers
- adding application manager groups
- adding objects to directory
- role, in PCMM architecture
- specifying application managers
- specifying SAE communities
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
Related Documentation
Example: Using the Sample Packet-Mirroring Application
To use the sample packet-mirroring application:
- Download the SRC sample applications to your system from the Juniper Networks website:
- Locate the file that contains the service definition:
/SDK/scriptServices/packetMirroring/ldif/service.ldif - Import the sample service definition to the Juniper Networks
Database on the C Series Controller. To load the sample data into
the database, you can use an LDAP tool, such as ldapadd.
You can obtain ldapadd from the following website:
To load data into the Juniper Networks database, you need the IP address of the database and the database credentials. The default bind distinguished name (DN) for the database is cn=umcadmin, o=umc and the password is admin123.
- Copy the /lib/pm.jar file used by the script service to the /opt/UMC/sae /var/run directory on the C Series Controller.
- Modify the service substitutions for your environment.
You can make these substitutions by defining the parameter substitutions in the packetMirroring service (serviceName=packetMirroring, o=Services, o=umc) with the SRC CLI or by passing the values through the SAE core API.
For information about parameter substitutions, see Configuring Parameters for the Script Service for Packet Mirroring. For information about passing the values through the SAE core API, see Defining RADIUS Attributes for Dynamic Authorization Requests with the SAE Core API.
- Configure a subscription to the packetMirroring service
that is activated on login.
For information about subscriptions, see Subscriptions Overview.
- If you are modifying the sample application, copy the sae.jar and logger.jar files from the SKD/lib directory, and add the sae.jar and logger.jar files to the class path when you compile your application.
Example: Packet Mirroring for PPP Subscribers
When a PPP subscriber is subscribed to the packet-mirroring service, configure the service as an activate-on-login service at user connection time. After the subscriber has logged in through the SAE remote API, the packet-mirroring service can be subscribed to the PPP subscriber and activated. When the service is activated, a COA request is sent to the router running JunosE Software that includes the PPP subscriber’s accounting session ID to start packet mirroring for this subscriber.
Example: Packet Mirroring for DHCP Subscribers
When a DHCP subscriber is subscribed to the packet-mirroring service, configure the service as an activate-on-login service at user connection time. After the subscriber has logged in through the SAE remote API, the packet-mirroring service can be subscribed to the DHCP subscriber and activated. When the service is activated, a COA request is sent to the router running JunosE Software that includes the DHCP subscriber’s IP address and virtual router name for the router running JunosE Software to start packet mirroring for this subscriber.
Configuring DHCP Subscriber Sessions
You can use DHCP option 82 to identify the subscriber session. For example, if you set DHCP option 82 as the user login name, an external application can use this setting to search for the subscriber session. The following subscriber classification script illustrates this example:
->?sub?(interfaceName=<-dhcp[82].suboptions[1].string->)] loginType = “ ADDR” [<-retailerDN->??sub?(uniqueID=<-userName->)] retailerDN != “ “ & userName != “ “ [<-unauthenticatedUserDn->] loginType == "ADDR" loginType == "AUTHADDR"
Disabling RADIUS Authentication for DHCP Subscribers
Packet mirroring for DHCP subscribers does not involve RADIUS authentication, so you might have to configure authentication to grant all IP subscriber management interfaces access without authentication. For example, configure the router running JunosE Software with the following authentication:
You can still configure other subscribers to use RADIUS authentication. For example, configure the router running JunosE Software with the following authentication for PPP subscribers:
