Configure Juniper BNG CUPS
This document presents sample configurations that you can use to set up Juniper BNG CUPS and configure subscriber access and subscriber management.
Configure PFCP Agent Circuit Identifier and IFL Sets
PFCP Agent Circuit Identifier (ACI) and IFL set configurations have specific requirements. IFL sets must be sets of client IFLs in PFCP mode. IFL sets of VLAN IFLs is not supported. (For configuring PFCP, see pfcp.
ACI virtual VLAN sets (ACI sets) are IFL sets of client IFLs, they are not VLAN IFLs.
All service related configurations of ACI sets must be defined in the client's IFL dynamic profile. Service configurations in the ACI dynamic profile are not supported.
For examples of service configurations, see the following:
- Example: Configure Class of Service
-
Example: Targeted Distribution Configuration for IFL for DHCP
-
Example: Targeted Distribution Configuration for IFL for PPPoE
-
Example: Targeted Distribution Configuration for IFL Sets for DHCP
-
Example: Targeted Distribution Configuration for IFL Sets for PPPoE
- Example: Configure Class of Service
- Example: Configure Dynamic Service VLAN Profile
- Example: Configure Dynamic ACI Virtual VLAN Profile
Example: Configure Class of Service
class-of-service {
forwarding-classes {
queue 0 BestEffort;
queue 1 Gold;
queue 2 RealTime;
}
scheduler-maps {
map-name {
forwarding-class class-name scheduler scheduler-name;
}
}
schedulers {
scheduler-name {
transmit-rate percent 25;
shaping-rate percent 80;
}
}
}
Example: Configure Dynamic Service VLAN Profile
dynamic-profiles {
profile-name {
interfaces {
demux0 {
unit interface-unit {
demux-source [ inet inet6 ];
vlan-tags outer stacked-vlan-id inner vlan-id;
auto-configure {
agent-circuit-identifier {
dynamic-profile example-aci-profile-with-no-services;
}
}
demux-options {
underlying-interface underlying-interface-name;
}
family inet {
unnumbered-address lo0.0;
}
family inet6 {
unnumbered-address lo0.0;
}
family pppoe {
duplicate-protection;
dynamic-profile ppp-dp-pp0;
}
}
}
}
protocols {
router-advertisement {
interface interface-name;
}
}
}
}
Example: Configure Dynamic ACI Virtual VLAN Profile
dynamic-profiles {
example-aci-profile-with-no-services {
interfaces {
interface-set interface-set-name {
interface interface-ifd-name;
}
}
}
}
Dynamic Client IFL profile:
dynamic-profiles {
example-client-dhcp-demux-profile {
interfaces {
interface-set interface-set-name {
interface demux0 {
unit interface-unit;
}
}
demux0 {
unit interface-unit {
demux-options {
underlying-interface underlying-interface-name;
}
family inet {
demux-source {
subscriber-ip-address;
}
unnumbered-address lo0.0;
}
family inet6 {
demux-source {
subscriber-ipv6-address;
}
unnumbered-address lo0.0;
}
}
}
}
protocols {
router-advertisement {
interface jnterface-name;
}
}
class-of-service {
traffic-control-profiles {
tcpSet {
scheduler-map schedular-map-name;
shaping-rate 1g;
guaranteed-rate 100m;
}
}
interfaces {
interface-set interface-set-name {
output-traffic-control-profile profile-name;
}
}
}
}
}
Configure Aggregated Ethernet Targeted Distribution over PFCP
Targeted distribution configuration for IFL and IFL set is supported only when configured in a client dynamic profile in PFCP mode. Targeted distribution is not supported for IFL and IFL set in a VLAN dynamic profile in PFCP mode.
- Example: Targeted Distribution Configuration for IFL for DHCP
- Example: Targeted Distribution Configuration for IFL for PPPoE
- Example: Targeted Distribution Configuration for IFL Sets for DHCP
- Example: Targeted Distribution Configuration for IFL Sets for PPPoE
Example: Targeted Distribution Configuration for IFL for DHCP
set dynamic-profiles client-dhcp-demux interfaces demux0 unit interface-unit targeted-distribution
Example: Targeted Distribution Configuration for IFL for PPPoE
set dynamic-profiles ppp-dp-pp0 interfaces pp0 unit interface-unit targeted-distribution
Example: Targeted Distribution Configuration for IFL Sets for DHCP
set dynamic-profiles client-dhcp-demux interfaces interface-set svlan-interface-set-name targeted-distribution set dynamic-profiles client-dhcp-demux interfaces demux0 unit interface-unit targeted-distribution
Example: Targeted Distribution Configuration for IFL Sets for PPPoE
set dynamic-profiles ppp-dp-pp0 interfaces interface-set svlan-interface-set-name targeted-distribution set dynamic-profiles ppp-dp-pp0 interfaces pp0 unit interface-unit targeted-distribution
Configure Multicast
You can set up multicast in your Juniper BNG CUPS environment. The following sections contain example configurations to help you set up multicast in Juniper BNG CUPS.
Configure Global Multicast Settings
You can use the following example configuration to help you configure global multicast settings.
Configure multicast on the BNG User Planes, as follows:
[edit]
protocols {
igmp {
query-interval 125;
query-response-interval 10;
query-last-member-interval 1;
robust-count 2;
}
mld {
query-interval 125;
query-response-interval 10;
query-last-member-interval 1;
robust-count 2;
}
}
policy-options {
policy-statement OIF-MAP-V4 {
term A {
from {
route-filter 230.10.10.1/24 orlonger;
route-filter 230.20.20.1/32 exact;
}
then {
map-to-interface ge-1/0/1.33;
accept;
}
}
then reject;
}
policy-statement OIF-MAP-V6 {
term A {
from {
route-filter ff3e:0:0:0:0:0:0:101/64 orlonger;
route-filter ff05:230::1/128 exact;
}
then {
map-to-interface ge-1/0/1.33;
accept;
}
}
then reject;
}
policy-statement igmp-group-policy {
term A1 {
from {
route-filter 230.0.0.1/24 orlonger;
}
then accept;
}
then reject;
}
policy-statement mld-group-policy {
term A1 {
from {
route-filter ff05::/64 orlonger;
}
then accept;
}
then reject;
}
policy-statement ssm-map-v4 {
term A1 {
from {
route-filter 230.0.0.1/24 orlonger;
}
then {
ssm-source 194.0.0.22;
accept;
}
}
}
policy-statement ssm-map-v6 {
term A1 {
from {
route-filter ff05::/64 orlonger;
}
then {
ssm-source 3000::1;
accept;
}
}
}
}
routing-options {
multicast {
ssm-groups 233.0.0.0/8;
cont-stats-collection-interval 600;
}
} Configure Centralized Multicast
You can use the following example configuration to help you configure a centralized multicast setup.
Configure centralized multicast on the BNG CUPS Controller, as follows:
[edit dynamic-profiles profile-name]
protocols {
igmp {
interface "$junos-interface-name" {
version 3;
immediate-leave;
promiscuous-mode;
ssm-map-policy ssm-map-v4;
group-policy igmp-group-policy;
oif-map OIF-MAP-V4;
}
}
} Configure Distributed Multicast
You can use the following example configuration to help you configure a distributed multicast setup.
Configure distributed multicast on the BNG CUPS Controller, as follows:
[edit dynamic-profiles profile-name]
protocols {
mld {
interface "$junos-interface-name" {
version 2;
immediate-leave;
promiscuous-mode;
distributed;
ssm-map-policy ssm-map-v6;
group-policy mld-group-policy;
}
}
}Configure Lawful Intercept
The radius-flow-tap configuration commands are split between the BNG
CUPS Controller and the BNG User Planes.
Configure Dynamic Tasking Control Protocol
You run all the Dynamic Tasking Control Protocol configurations on the BNG CUPS Controller.
Perform the following configuration on the BNG CUPS Controller:
[edit]
System {
login {
class <class-name> {
permissions flow-tap-operation;
}
user <user-name> {
uid <uid>;
class <class-name>;
authentication {
encrypted-password <string>
}
}
}
services {
flow-tap-dtcp {
ssh {
connection-limit <connection-limit>;
rate-limit <rate-limit>;
}
}
}
}