Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
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
Related Documentation
- Configuring Diameter Peers (SRC CLI)
- Adding Devices Running Junos OS and Virtual Routers (SRC CLI)
- Adding Objects for Network Devices (SRC CLI)
- Configuring the SAE to Manage Devices Running Junos OS (SRC CLI)
- Configuring the SAE to Obtain Information About Subscribers (SRC CLI)
- Configuring the PTSP Device Driver (SRC CLI)
Adding an MX Series Router as a PTSP Network Device (SRC CLI)
You can configure the service activation engine (SAE) to manage a packet-triggered subscribers and policy control (PTSP) network device on an MX Series router.
Use the following configuration statements to configure the network device:
shared network device name { device-type (junose | junos-ise | junos-ptsp | junos |
pcmm | thirdparty);origin-host origin-host;peers [peers...];}
shared network device name virtual-router name { sae-connection [sae-connection...];user-tracking-plug-in user-tracking-plug-in ...];authentication-plug-in [authentication-plug-in...];vpn-id vpn-id;}
To configure an MX Series router as a PTSP network device so that the router can be managed by the SAE:
- From configuration mode, access the statements that configure
network devices. This sample procedure uses mx-name as the name of
the router.user@host# edit shared network device mx-name
- Set the type of device to junos-ptsp. [edit shared network device mx-name] user@host# set device-type junos-ptsp
- (Optional) Specify the origin hostname of the MX Series
router. This example procedure uses mx-origin-host as the origin hostname.
The active SAE registers events from the router based on the configured
origin host attribute (mx-origin-host in the example). If the origin
host is not configured, SAE uses the device name (mx-name in the example)
instead. user@host# edit shared network origin-host mx-origin-host
- Specify the configured peers associated with the device.
See Configuring Diameter Peers (SRC CLI). [edit shared network device mx-name] user@host# set peers [peers...]
Note: MX Series routers support only a single peer connection.
- From configuration mode, access the statements for virtual
routers. The name you specify must match the PTSP partition configured
on the MX Series router, which is configured within the logical system:routing
instance context. This sample procedure uses the name * for the virtual
router.[edit shared network device mx-name] user@host# edit virtual-router *
where * matches any PTSP partition. You can also specify that the PTSP partition be configured in a logical system or in a logical system and routing instance. By default, logical system default and routing instance master are used.
- Specify the SAEs that can manage this router.[edit shared network device mx-name virtual-router default]user@host# set sae-connection [sae-connection...]
- (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 mx-name virtual-router default] user@host# set user-tracking-plug-in [user-tracking-plug-in...]
Set the user-tracking-plug-in option to the name of the configuration plug-in you configured with the edit shared sae configuration plug-ins name name ssr-writer statement.
- (Optional) Specify the plug-ins that authenticate subscribers
who log in through this virtual router.[edit shared network device mx-name virtual-router default]user@host# set authentication-plug-in [authentication-plug-in...]
- (Optional) Specify the VPN identifier used by this virtual
router. You can specify VRF instead of a string to use the VRF instance
reported by the device as the VPN identifier. In this case, the VPN
identifier is the name of the routing instance.[edit shared network device mx-name virtual-router default]user@host# set vpn-id (vpn-id | VRF)
- (Optional) Verify your configuration.
[edit shared network device mx-name] user@host# show
device-type junos-ptsp; interface-classifier { rule rule-1 { condition { interfaceName=*; } target /lib/default; } } origin-host bng-srcmx480b; peers bng-srcmx480b; virtual-router * { authentication-plug-in ldap-auth; sae-connection 10.212.10.2; user-tracking-plug-in fileAuth; vpn-id 123; }
Related Documentation
- Configuring Diameter Peers (SRC CLI)
- Adding Devices Running Junos OS and Virtual Routers (SRC CLI)
- Adding Objects for Network Devices (SRC CLI)
- Configuring the SAE to Manage Devices Running Junos OS (SRC CLI)
- Configuring the SAE to Obtain Information About Subscribers (SRC CLI)
- Configuring the PTSP Device Driver (SRC CLI)
