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
- 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
Adding Network Devices (SRC CLI)
To set up the MX Series router so that it can be managed by the SAE:
- From configuration mode, access the statements that configure
network devices. This sample procedure uses mx1 as the name of the
router.user@host# edit shared network device mx1
- Set the type of device to junos-ise. [edit shared network device mx1] user@host# set device-type junos-ise
- (Optional) Specify the origin hostname. This example procedure
uses mx1-origin-host as the origin hostname. If the origin hostname
is not configured, SAE uses the device name (mx1 in the example) as
the origin hostname. If configured, the mentioned origin hostname
must match the origin hostname of the Diameter peer (for example,
MX Series router).[edit shared network device mx1] user@host# set origin-host mx1-origin-host
Note: If the origin hostname is configured under the [edit shared network device name] hierarchy, the device name does not need to be same as the origin hostname of the Diameter peer. Otherwise, the device name must match the origin hostname of the Diameter peer.
- Specify the configured peers associated with the device.
See Configuring Diameter Peers (SRC CLI). [edit shared network device mx1] 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 must match the JSRC 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 mx1] user@host# edit virtual-router *
where * matches any JSRC partition. You can also specify that the JSRC 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 mx1 virtual-router default]user@host# set sae-connection [sae-connection...]
- (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 mx1 virtual-router default]user@host# set vpn-id (vpn-id | VRF)
- (Optional) Verify your configuration.
[edit shared network device mx1] user@host# show device-type junos-ise; origin-host mx1-origin-host; peers bng-srcmx480b; virtual-router * { sae-connection 10.212.10.2; vpn-id 123; }
