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
Configuring the NIC Proxy for the Pseudo-RADIUS Authorization Server (SRC CLI)
When the check-lease-limit-with-sae option is set to true, you must configure the NIC proxy so that the pseudo-RADIUS authorization server can find the SAE managing the interface and determine the number of subscriber sessions already established on the interface (that is, the number of leases on the interface). The NIC proxy must be configured for a NIC scenario that maps VRs to SAEs.
Tasks to configure the NIC proxy are:
- Configuring Resolution Information for a NIC Proxy
- Changing the Configuration for the NIC Proxy Cache
- Configuring a NIC Proxy for NIC Replication
Configuring Resolution Information for a NIC Proxy
Use the following configuration statements to configure the NIC proxy:
slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic resolution {resolver-name resolver-name; constraints constraints; }
To configure resolution information for a NIC proxy:
- From configuration mode, access the configuration statement
that configures the NIC proxy configuration. In this sample procedure,
the NIC proxy called radius-authorization-nic is configured. user@host# edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic resolution
- Specify the resolution information for this NIC proxy.[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic resolution]user@host# set ?
For more information about configuring resolution information for a NIC proxy, see Configuring Resolution Information for a NIC Proxy (SRC CLI).
- (Optional) Verify your configuration. [edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic resolution]user@host# show
Changing the Configuration for the NIC Proxy Cache
You can modify cache properties for the NIC proxy to optimize the resolution performance for your network configuration and system resources. Typically, you can use the default settings for the cache properties. The configuration statements are available at the Advanced editing level.
Use the following configuration statements to change values for the NIC proxy cache:
slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic cache {cache-size cache-size; cache-cleanup-interval cache-cleanup-interval; cache-entry-age cache-entry-age; }
To configure the cache for a NIC proxy:
- From configuration mode, access the configuration statement
that specifies the NIC proxy configuration. In this sample procedure,
the NIC proxy called radius-authorization-nic is configured. user@host# edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic cache
- Specify the cache properties for the NIC proxy. [edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic cache]user@host# set ?
For more information about configuring the cache for a NIC proxy, see Changing the Configuration for the NIC Proxy Cache (SRC CLI).
- (Optional) Verify your configuration.
[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic cache] user@host# show cache-size 10000; cache-cleanup-interval 15;
Configuring a NIC Proxy for NIC Replication
Typically, you configure NIC replication to keep the NIC highly available. You configure NIC host selection to specify the groups of NIC hosts to be contacted to resolve a request, and to define how the NIC proxy handles NIC hosts that the proxy is unable to contact. The configuration statements are available at the Normal editing level.
Use the following configuration statements to configure NIC host selection for a NIC proxy:
slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic nic-host-selection
{groups groups; selection-criteria (roundRobin | randomPick | priorityList); }
slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic nic-host-selection
blacklisting {try-next-system-on-error; number-of-retries-before-blacklisting number-of-retries-before-blacklisting; blacklist-retry-interval blacklist-retry-interval; }
To configure a NIC proxy to use NIC replication:
- From configuration mode, access the configuration statement
that specifies the NIC proxy configuration. In this sample procedure,
the NIC proxy called radius-authorization-nic is configured. user@host# edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection
- (Optional) Configure NIC host selection for a NIC proxy.[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection]user@host# set ?
For more information about configuring NIC host selection for a NIC proxy, see Configuring a NIC Proxy for NIC Replication (SRC CLI).
- (Optional) Verify your configuration.
[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection] user@host# show groups ; selection-criteria roundRobin;
- Access the configuration statement that specifies the
NIC proxy configuration for blacklisting—the process of handling
nonresponsive NIC hosts. [edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection]user@host# edit blacklisting [edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection blacklisting]
- (Optional) Configure blacklisting for a NIC proxy. [edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection blacklisting]user@host# set ?
For more information about configuring NIC host selection for a NIC proxy, see Configuring a NIC Proxy for NIC Replication (SRC CLI).
- (Optional) Verify your configuration.
[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection blacklisting]user@host# show[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection blacklisting] user@host# show try-next-system-on-error; number-of-retries-before-blacklisting 3; blacklist-retry-interval 15;
Related Documentation
- Configuring External Subscriber Monitor (SRC CLI)
- Configuring Pseudo–RADIUS Authorization Server Properties (SRC CLI)
- Extracting RADIUS Attributes with the Pseudo–RADIUS Authorization Server (SRC CLI)
- Enabling the Pseudo-RADIUS Authorization Server (SRC CLI)
