- play_arrow Overview
- play_arrow Use Juniper BNG CUPS
- Use Juniper BNG CUPS with Multiple Geographical Redundancy
- Use Dynamic Address Pools in Juniper BNG CUPS
- Juniper BNG CUPS High Availability
- Use Juniper BNG CUPS Subscriber Groups
- Use BNG User Plane Maintenance
- Use Juniper BNG CUPS Smart Session Load Balancing
- Use Juniper BNG CUPS for Subscriber Steering
- Use Juniper BNG CUPS Multicast
- Use Juniper BNG CUPS Lawful Intercept
- Use Juniper BNG CUPS Captive Portal and Content Delivery Services
- Configure Agent Circuit Identifier and IFL Sets in Juniper BNG CUPS
- Understanding DVLAN (Single/Dual tag) for Subscriber Services Scaling (Junos Evolved for ACX7100-48L, ACX7332, and ACX7348 Devices)
- How to Use the Juniper BNG CUPS Controller Utility Commands
- Troubleshooting and Monitoring Juniper BNG CUPS
- play_arrow Juniper BNG CUPS Controller CLI Operational Statements
- play_arrow Juniper BNG User Plane CLI Configuration Statements
- Juniper BNG User Plane CLI Configuration Statements
- auto-configure
- captive-portal-content-delivery-profile (Services)
- dynamic-profile (Stacked VLAN)
- flexible-vlan-tagging (Interfaces)
- hierarchical-scheduler
- ranges (Dynamic Stacked VLAN)
- service-set (Dynamic Service Sets)
- service-set-options
- services (Captive Portal Content Delivery)
- stacked-vlan-tagging
- play_arrow Juniper BNG User Plane CLI Operational Commands
ON THIS PAGE
Juniper BNG CUPS Controller CLI Configuration Statements
This topic provides an overview of configuration commands, including syntax and option descriptions, that you use with Juniper BNG CUPS Controller.
address-pool-manager
Syntax
address-pool-manager {
inet ip-address;
port port-number;
local-reserve{
partition partition-name{
prefix ipv4-prefix;
}
auto-reclamation {
drain-delay number;
}
apportion-delay number;
}
secrets {
certificate certificate-file;
key private-key-file;
ca-cert cacertificate-file;
}
}
]
Hierarchy Level
[edit groups bbe-common-|0 - 4| access]
Description
Configures Juniper Address Pool Manager's (APM) connection to Juniper BNG CUPS. This configuration is done on the Juniper BNG Controller.
Options
inet ip-address | APM's IPv4 address. |
port port-number | The port that APM is listening on for incoming address pool manager connections. |
local-reserve | A BNG CUPS Controller configured set of partitions. Partitions can be either IPv4 or IPv6 addresses. |
Partition partition-name | The configured partion. |
prefix ipv4-prefix | Specify an IPv4 prefix to include in the partition. |
drain-delay number | Specifies a hold down time to wait after reconnecting with APM, to start draining local pools. |
apportion-delay number | Specifies a hold down time to wait before entering the local apportionment mode, following the loss of connectivity with APM. |
secrets | If the gRPC Network Management Interface (gMI) connection is secured, configure any Transport Layer Security (TLS) keys, as follows:
|
bng-controller
Syntax
bng-controller {
bng-controller-name bng-cups-controller-name;
security-profiles security-profile-name {
ca-cert-file-name ca-certificate-name;
cert-file-name certificate-name;
key-file-name key-name;
}
user-plane {
bng-user-plane-name {
transport {
inet ip-address;
inet6 ip-address;
security-profile security-profile-name {
}
dynamic-address-pools {
partion partition-name;
}
user-plane-profile bng-user-plane-profile-name;
}
}
control-plane-instances {
control-plane-instance-name {
control-plane-config-group control-plane-config-group-name;
user-plane bng-user-plane-name;
}
}
subscriber-groups {
}
load-balancing-groups {
}
}
}
}
}Hierarchy Level
[edit groups bbe-bng-director]
Description
Configures system wide attributes for the BNG CUPS Controller, such as the
user-plane configuration and the
control-plane-instances configuration.
Configures the BNG CUPS Controller system.
Options
| bng-controller-name bng-cups-controller-name | The bng-cups-controller-name is a mandatory reference to the local system and can be 1 to 12 characters long. You can combine uppercase letters and lowercase letters, numbers, hyphens, and periods in this reference but cannot start or end it with a hyphen. |
security-profile | Secify a security profile. See security-profiles. |
user-plane | Specify the BNG User Planes to be associated with the BNG CUPS Controller. See user-planes (bng-controller). |
control-plane-instances | |
subscriber-groups | See subscriber-groups. |
load-balancing-groups | See load-balancing-groups. |
captive-portal-content-delivery
Syntax
captive-portal-content-delivery {
profile name
dynamic;
}Hierarchy Level
[edit groups bbe-common-|0 - 4| services]
Description
Configure the HTTP redirect service by specifying the location to which a
subscriber's initial Web browser session is redirected, enabling initial
provisioning and service selection for the subscriber. Use the statement at the
[edit groups bbe-common-|0 - 4| services] hierarchy level
for converged services CPCD. This command runs on the BNG CUPS Controller.
Required Privilege Level
services—To view this statement in the configuration.
services–control—To add this statement to the configuration.
Release Information
Command introduced in Juniper BNG CUPS Release 23.1R1.
captive-portal-content-delivery-profile
Syntax
captive-portal-content-delivery-profile profile-name;
Hierarchy Level
[edit groups bbe-common-|0 - 4| services service-set service-set-name]
Description
Configure converged HTTP redirect services on the Routing Engine. This command runs on the BNG CUPS Controller.
Options
captive-portal-content-delivery-profile
profile-name—Name of the CPCD profile.
Required Privilege Level
services—To view this statement in the configuration.
services–control—To add this statement to the configuration.
Release Information
Statement introduced before Juniper BNG CUPS Release 23.1.
control-plane-instances
Syntax
control-plane-instances{
control-plane-instance-name{
control-plane-config-group control-plane-config-group-name;
user-plane user-plane-name;
}
}
Hierarchy Level
[edit groups bbe-bng-director bng-controller]
Description
Control plane instances to which BNG User Planes are mapped. This mapping enables you to easily move BNG User Planes from one control plane instance to another to adapt to changing scaling or use case demands. A control plane instance is assigned to a control plane configuration group.
Options
control-plane-instance-name | Name of the control plane instance. |
control-plane-config-group
control-plane-config-group-name | Specify the name of an existing control plane configuration group from which the control plane instance obtains its configuration. |
user-plane user-plane-name | Specify the name of a BNG User Plane assigned to the control plane instance. You can assign more than one BNG User Plane to a control plane instance. |
domain-profile
Syntax
domain-profile domain-profile-name{
family{
inet ip-address | inet6 ip-address{
partion-type [delegated-prefix | non-temporary-address | router-advertisement];
preferred-prefix-length number;
allocation-length number;
install-discard-routes{
tag number;
backup-tag number;
}
source-partition-qualifier string;
excluded-address last-octet number;
dhcp-gateway-address-last-octet number;
protocol-attributes dhcp-attribute;
}
}
Hierarchy Level
[edit groups bbe-common-|0 - 4| access address-assignment]
Description
Configures the domain profile. The domain profile defines the BNG attributes for creating domains. The domain is created based on the framed pool received from RADIUS.
Options
domain-profile
domain-profile-name | Set the name of the domain profile. |
family | Specify an address family protocol. Specify |
partion-type [delegated-prefix | non-temporary-address |
router-advertisement] | Only applies to |
preferred-prefix-length number | Define the preferred prefix length.
|
allocation-length number | Define the allocation length of the IPv6 address or prefix that are assigned from the dynamic address pool prefix to the subscriber. This option is supported only for the inet6 address family. |
source-partition-qualifier
string | (Optional) A string that is applied as a suffix to the domain’s location, to create a partition name that is passed to Juniper Address Pool Manager. |
excluded-address last-octet
number | (Optional) When you configure the preceding code phrase, the domain profile excludes all addresses with a domain pool prefix that matches the specified last-octet value. This option is supported only for the inet address family.
|
dhcp-gateway-address-last-octet
number | specifies the value of the last byte to reserve in each dynamic pool
prefix to be used as the DHCP gateway address for the DHCP Local
Server. For example, if the dynamically allocated pool prefix is
192.32.6.0/24 and |
protocol-attributes
dhcp-attribute | Specifies the name of the protocol attributes profile that defines the DHCP attributes to use for dynamic pools created in the domain. |
install-discard-routes tag number backup-tag
number | (Optional) Indicates that you must configure a discard route (with the associated route tag supplied with the pool prefix) separately on the BNG User Planes to import these routes into the exported route set. Valid route tags are 0..2^(32-1) |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Juniper BNG CUPS Release 23.4R1.
igmp
Syntax
igmp {
interface interface-name {
(accounting | no-accounting);
disable;
distributed;
group-limit limit;
group-policy [ policy-names ];
immediate-leave;
oif-map map-name;
passive;
promiscuous-mode;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-policy-name;
static {
group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
}
}
version version;
}
}
Hierarchy Level
[edit groups bbe-common-|0 - 4| dynamic-profiles profile-name protocols]
Description
Enable IGMP on an interface and configure interface-specific properties. This command runs on the BNG CUPS Controller.
Options
interface-name—Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Juniper BNG CUPS Release 22.4R1.
load-balancing-groups
Syntax
load-balancing-groups {
group-name;
user-plane bng-user-plane-name{
weight-based-mode{
port port-number{
max-weight max-weight-number;
preferred;
}
report-based-mode
port port-number{
preferred;
]
}
Hierarchy Level
[edit groups bbe-bng-director bng-controller]
Description
Enables load balancing on Juniper BNG CUPS. This command runs on the BNG CUPS Controller.
Options
group-name | Specify the load balancing group name. |
user-plane bng-user-plane-name | Specify the BNG User Plane that is associated with the BNG CUPS Controller for load balancing. |
weight-based-mode | Used to configure weight-based load balancing. |
report-based-mode | Used to configure report-based load balancing. |
port port-identifier | Specify the logical port that is associated with the BNG CUPS Controller load balancing. You use the format up:user-plane-name:physical-port-name. |
max-weight max-weight-number | Specify the maximum weight value (1 through 255) for the logical port. |
mld
Syntax
mld {
interface interface-name {
(accounting | no-accounting);
disable;
distributed;
group-limit limit;
group-policy [ policy-names ];
group-threshold value;
immediate-leave;
log-interval seconds;
oif-map [ map-names ];
passive;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-policy-name;
static {
group multicast-group-address {
exclude;
group-count number
group-increment increment
source ip-address {
source-count number;
source-increment increment;
}
}
}
version version;
}
}Hierarchy Level
[edit groups bbe-common-|0 - 4| dynamic-profiles profile-name protocols]
Description
Enable MLD on an interface and configure interface-specific properties. This command runs on the BNG CUPS Controller.
Options
interface-name—Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Juniper BNG CUPS Release 22.4R1.
overrides
Syntax
overrides {
no-unsolicited-ra;
statistics-reporting-interval seconds;
}
Hierarchy Level
[edit groups bbe-common-|0 - 4| user-plane-profiles user-plane-profile-name]
Description
Override the default configuration settings for the enhanced subscriber management software for subscriber management.
Options
statistics-reporting-interval seconds | The interval at which statistics are reported from a BNG User Plane to the BNG CUPS Controller. The statistics reporting interval is reported in seconds.
|
no-unsolicited-ra | Disable the default transmission and periodic refresh of unsolicited
Router Advertisement messages by the router when the subscriber
interface is created, and at configured periodic intervals
thereafter. When you include the |
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
partition
Syntax
partition partition-name;
Hierarchy Level
[edit groups bbe-bng-director bng-controller user-planes bng-user-plane-name dynamic-address-pools-plane]
Description
Defines the BNG User Plane partition attribute. The partition attribute defines the source partition defined by a dynamic address pool source. The dynamic pool source can be either APM or local-reserve.
For Juniper BNG CUPS to operate with Juniper Address Pool Manager, you must configure the partition attribute.
Options
partition partition-name | Name of the partition. |
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
pfcp
Syntax
pfcp {
retransmission-timer seconds;
retries number;
heartbeat-interval seconds;
enable-tracing
}
Hierarchy Level
[edit groups bbe-common-|0 - 4| user-plane-profiles user-plane-profile-name]
Description
Sets the Packet Forwarding Control Protocol (PFCP) protocol attributes for the control plane manager and any other daemons using Packet Forwarding Control Protocol to communicate with their peers.
Options
pfcp | Specify the Packet Forwarding Control Protocol protocol attributes. Note: We recommend that you configure the BNG CUPS Controller and the BNG User Planes with the same Packet Forwarding Control Protocol attributes.
|
prefix-advertisement
Syntax
prefix-advertisement {
family inet {
tag number;
backup-tag number;
prefix ip-address;
{
family inet6 {
tag number;
backup-tag number;
prefix ip-address;
}
}
Hierarchy Level
[edit groups bbe-bng-director bng-controller subscriber-group subscriber-group-name subscriber-group-name routing-instances routing-instance-name]
Description
Supports the DHCP relay L3 wholesale model. You configure a dedicated routing
instance for a retailer and assign it to a subscriber group. You use the
prefix-advertisement command to configure the IPv4 or IPv6
prefixes, that represent the pool of IPv4 or IPv6 addresses and prefixes
assigned to the subscriber by the retailer. You can also configure optional
route tags for route advertisement.
Options
family inet—You can configure the following: |
|
family inet6—You can configure the following: |
|
routing-engine-services
Syntax
routing-engine-services;
Hierarchy Level
[edit groups bbe-common-|0 - 4| services service-set service-set-name service-set-options]
Description
When configuring a Routing Engine-based captive portal service, specify the service set options to apply to a service set. This command runs on the BNG CUPS Controller.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Juniper BNG CUPS Release 23.1.
security-profiles
Syntax
security-profiles profile-name{
ca-cert-file-name ca-certificate-name;
cert-file-name certificate-name;
key-file-name key-name;
}
Hierarchy Level
[edit groups bbe-bng-director bng-controller]
Description
Defines one or more profiles that specify security requirements to secure the BNG CUPS Controller channels to the BNG User Planes using Data Transport Layer Security and Transport Layer Security. If the security-profiles is not configured, the related BNG CUPS Controller or BNG CUPS User Plane assumes that the transport interfaces are not secure.
Options
security-profiles profile-name | Give the security profile a name. |
ca-cert-file-name
ca-certificate-name | Name of the CA profile. |
cert-file-name certificate-name | Name of the public certificate. |
key-file-name key-name | Name of the private key pair. |
service-set
Syntax
service-set service-set-name {
service-set-options {
routing-engine-services;
}
captive-portal-content-delivery-profile profile-name;
}Hierarchy Level
[edit groups bbe-common-|0 - 4| service-set service-set-name]
Description
Define one or more service sets. Service sets are applied to an interface. If you
define multiple service sets, the router software evaluates the filters in the
order in which they appear in the configuration. You can use the predefined
dynamic interface variables $junos-input-service-set,
$junos-output-service-set,
$junos-input-ipv6-service-set, and
$junos-output-ipv6-service-set. This command runs on the
BNG CUPS Controller.
Options
service-set-name | Name of the service set. |
service-set-options | Specify service set options (see service-set-options). |
routing-engine-services | Specify routing engine services configuration (see routing-engine-services). |
captive-portal-content-delivery-profile
profile-name | Name of the CPCD profile (see captive-portal-content-delivery-profile). |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Juniper BNG CUPS Release 23.1R1.
service-set-options
Syntax
service-set-options {
routing-engine-services;
}
Hierarchy Level
[edit groups bbe-common-|0 - 4| service-set service-set-name]
Description
Specify the service set options to apply to a service set. This command runs on the BNG CUPS Controller.
Options
routing-engine-services | Specify routing engine services configuration (see routing-engine-services). |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Juniper BNG CUPS Release 23.1R1.
static-address-pools
Syntax
static-address-pools {
pool-name {
tag number;
backup-tag number
}
}
Hierarchy Level
[edit groups bbe-bng-director bng-controller subscriber-group subscriber-group-name subscriber-group-name routing-instances default]
Description
Sets the assignment of a statically configured address pool used to assign subscriber IPv4 or IPv6 addresses for a subscriber group. The address pool can also be configured with optional route tags on a network instance basis. For each specified static pool for a specified routing instance, a discard route can be derived from the pool network or prefix configuration for route advertisement.
Options
pool-name | Specify the name of the address pool. |
tag number | (Optional) Set the active route tag. |
backup-tag number | (Optional) Set the backup route tag. |
subscriber-group (control-plane-managed-mode)
Syntax
subscriber-group
subscriber-group-name subscriber-group-name{
virtual-mac mac-address;
control-plane-managed-mode{
preferred-user-plane-name user-plane-name;
redundancy-interface alpha{
logical-port up:user-plane-name:logical-port-name,up:user-plane-name:logical-port-name;
}
redundancy-interface beta {
logical-port up:user-plane-name:logical-port-name,up:user-plane-name:logical-port-name;
}
}
}Hierarchy Level
[edit groups bbe-bng-director bng-controller]
Description
A group of subscribers. Subscriber sessions that are subject to the same restoration capability are placed into the same subscriber group. Grouping subscribers together helps to increase core routing efficiency. The use of subscriber groups minimizes the messaging, which reduces the elapsed time between the detection of a failure (or any request to switchover from active to backup) and the restoration of the service.
Options
subscriber-group-name subscriber-group-name | Specify the subscriber group name. |
| virtual-mac mac-address | A logical MAC address assigned to the subscriber group that is used for all communication between the BNG CUPS Controller and the subscriber sessions assigned to the subscriber group. This ensures that the same MAC address is used by the BNG CUPS Controller for communication with subscriber sessions, irrespective of which BNG User Plane is currently active for the subscriber group. A virtual MAC address is required for a resiliency subscriber group. |
control-plane-managed-mode | Establishes that the BNG CUPS Controller determines which BNG User Plane is the active one for a resiliency subscriber group |
preferred-user-plane-name user-plane-name | When operating in control plane managed mode for a resiliency subscriber group, it establishes which of the member BNG User Planes is the preferred active BNG User Plane. |
redundancy-interface alpha |
Configures a named set of logical ports on a BNG User Plane that is assigned to the subscriber group. |
redundancy-interface beta |
For a resiliency subscriber group, you configure a named set of
logical ports on the BNG User Planes that are assigned to the
subscriber group. The two redundancy interfaces form a resiliency
subscriber group, that for
|
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
subscriber-group (user-plane-managed-mode)
Syntax
subscriber-group
subscriber-group-name subscriber-group-name{
virtual-mac mac-address;
user-plane-managed-mode{
redundancy-interface alpha{
logical-port up:user-plane-name:logical-port-name,up:user-plane-name:logical-port-name;
}
}Hierarchy Level
[edit groups bbe-bng-director bng-controller]
Description
A group of subscribers. Subscriber sessions that are subject to the same restoration capability are placed into the same subscriber group. Grouping subscribers together helps to increase core routing efficiency. The use of subscriber groups minimizes the messaging, which reduces the elapsed time between the detection of a failure (or any request to switchover from active to backup) and the restoration of the service.
Options
subscriber-group-name subscriber-group-name | Specify the subscriber group name. |
| virtual-mac mac-address | A logical MAC address assigned to the subscriber group that is used for all communication between the BNG CUPS Controller and the subscriber sessions assigned to the subscriber group. This ensures that the same MAC address is used by the BNG CUPS Controller for communication with subscriber sessions, irrespective of which BNG User Plane is currently active for the subscriber group. A virtual MAC address is required for a resiliency subscriber group. |
user-plane-managed-mode | Establishes that the BNG User Plane determines which BNG User Plane is the active one for a resiliency subscriber group |
redundancy-interface alpha |
Configures a named set of logical ports on a BNG User Plane that is assigned to the subscriber group. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
subscriber-group-default-tag
Syntax
subscriber-group-default-tag {
tag number;
backup-tag number;
}
Hierarchy Level
[edit groups bbe-common-|0 - 4| access address-assignment]
Description
Configures active and backup global tags for subscriber groups.
Options
tag number | Set the global active tag. |
backup-tag number | Set the global backup tag. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Juniper BNG CUPS Release 23.4R1.
transport
Syntax
transport {
inet ip-address;
security-profile security-profile-name;
}
Hierarchy Level
[edit groups bbe-bng-dirctor bng-controller user-planes bng-user-plane-name]
Description
Defines the transport security for all BNG CUPS Controller and BNG User Plane
inter-communication. You use the transport command to configure either the BNG
CUPS Controller or the BNG User Planes, depending on which option you choose at
the mode level of the hierarchy.
Options
inet ip-address | The IP address of either the BNG CUPS Controller or the BNG User Plane that you are configuring. |
security-profile
security-profile-name | Specify the configured security profile that lists the CA profile, public certificate, and private key pair. |
user-plane-profiles
Syntax
user-plane-profiles {
user-plane-profile-name {
capabilities {
hardware-family (juniper-mx | juniper-acx)
}
pfcp {
retransmission-timer seconds;
retries number;
heartbeat-interval seconds;
}
interfaces interface-name {
auto-configure {
stacked-vlan-ranges {
dynamic-profile <dynamic-profile-name> {
accept any;
ranges {
any,any;
}
}
}
remove-when-no-subscribers;
}
}
}
}
}Hierarchy Level
[edit groups bbe-common-|0 - 4|]
Description
The user-plane-profiles statement uses a template to configuring
a BNG User Plane in terms of interfaces, pfcp behavior, and subscriber
management override behavior. The user-plane-profiles statement
is specified as part of the BNG User Plane configuration in the
bbe-bng-director configuration group. It is defined in the
common group configuration that is part of the
control-plane-instance configuration. When a BNG User Plane is
assigned to a control-plane-instance during its configuration,
the BNG User Plane's user-plane-profile must be defined in the
control plane instance's control-plane-config-group (bbe-common-|0 - 4|).
Options
user-plane-profile-name | Name of the user plane profile. |
hardware-family | Specify configuration pertaining to the capabilities of the BNG User
Plane type. Currently, only the |
pfcp | Specify the PFCP configuration to be used for the BNG User Plane (see pfcp). |
interfaces interface-name | Specify interfaces configuration to be used for the BNG User Plane (see . |
user-planes (bng-controller)
Syntax
user-planes {
bng-user-plane-name {
transport {
inet ip-address;
security-profile security-profile-name;
}
dynamic-address-pools {
partion partition-name;
}
user-plane-profile bng-user-plane-profile-name;
}
}Hierarchy Level
[edit groups bbe-bng-director bng-controller]
Description
Define the BNG User Planes that are authorized to associate with the BNG CUPS Controller. You must list each BNG User Plane.
Options
user-plane-name | Name of the BNG User Plane. |
transport | Specify transport information. See transport. |
dynamic-address-pools | Specify the dynamic address pool related configuration. You should at least configure the partition name. |
partition partition-name | The partition from which IPv4 and IPv6 addresses and prefixes are assigned. |
user-plane-profile
user-plane-profile-name | Specify one or more user plane profiles. See user-plane-profiles. |
weight
Syntax
weight weight-number;
Hierarchy Level
[edit groups bbe-common-|1 - 4| dynamic-profiles dynamic-profiles-name interfaces interface-name unit interface-unit load-balance] [edit dynamic-profiles dynamic-profiles-name interfaces interface-set interface-set-name load-balance]
Description
Sets the load balancing weight for either subscribers or the logical interface set.
You can define weight based on your needs. You can define it by using subscriber bandwidth, logical interface set bandwidth, or an even number of subscribers per logical interface set. This command runs on the BNG CUPS Controller.
Options
weight weight-number | Defines the load balancing weight value (1 through 255). |
Required Privilege Level
root—To view this statement in the configuration.
root—To add this statement to the configuration.
