command stringlengths 2 75 | syntax stringlengths 0 289k | hierarchy_level stringlengths 0 6.91k | description stringlengths 0 45.2k | options listlengths 0 499 | required_privilege_level stringlengths 0 330k | release_information stringlengths 0 3.14k | related_documentation listlengths 0 22 |
|---|---|---|---|---|---|---|---|
global-config (Services) | global-config {
cache-usage-enforcement-threshold cache-usage-enforcement-threshold;
certificate-cache-timeout seconds;
disable-cert-cache;
disable-deferred-profile-selection;
invalidate-cache-on-crl-update;
non-ssl-detection-threshold {
byte-threshold byte-threshold;
packet... | [edit services ssl proxy] | Specify the global proxy configuration. When SSL proxy is configured at a global level (within “services
ssl proxy”), it is visible across the system configurations on the device. | [
{
"name": "enforcement-threshold",
"desc": "Percentage of total cache size after which per logical system limits will be enforced. Range: 1 through 100"
},
{
"name": "certificate-cache-timeout",
"desc": ""
},
{
"name": "seconds",
"desc": "Regulates the certificate cache timeout. De... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. disable-cert-cache, certificate-cache-timeout, and
Invalidate-cache-on-crl-update options are introduced in Junos OS Release 18.1R1. | [
"SSL Proxy Overview",
"Configuring SSL Forward Proxy",
"Enabling Debugging and Tracing for SSL Proxy"
] |
global-dns-stats-log-timer | global-dns-stats-log-timer minutes; | [edit services web-filter profile profile-name] | Configure the interval for logging per-client statistics for filtering of DNS requests for disallowed
website domains. | [
{
"name": "minutes",
"desc": "The number of minutes in the logging interval. Default: 5 Range: 0 through 60"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1 on MX Series.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"DNS Request Filtering for Disallowed Website Domains"
] |
global-limit | global-limit global-limit; | [edit logical-systems name security utm default-configuration url-feed],
[edit logical-systems name tenants name security utm default-configuration url-feed],
[edit security utm default-configuration url-feed],
[edit tenants name security utm default-configuration url-feed] | Configure global URL feed limit. You can define the maximum number of URL feeds on your device. | [
{
"name": "global-limit",
"desc": "Configure the maximum number of URL feeds. Default: 20 Range: 1 through 50"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
global-load-balancing | global-load-balancing {
(helper-only | load-balancer-only);
profile-sharing
} | [edit fabric protocols bgp],
[edit logical-systems name protocols bgp],
[edit logical-systems name routing-instances name protocols bgp],
[edit logical-systems name tenants name routing-instances name protocols bgp],
[edit protocols bgp],
[edit routing-instances name protocols bgp],
[edit tenants name routing-instance... | Enable global load balancing (GLB). Global load balancing is hashing a route with multiple ECMP links
onto several links for load balancing. BGP sends next-next-hop node (NNHN) capability for the route it
advertises and monitors the link qualities of all local links with EBGP sessions and floods them to all
direct neig... | [
{
"name": "helper-only",
"desc": "(Optional) The node works as a helper and monitors the link quality."
},
{
"name": "load-balancer-only",
"desc": "(Optional) The node works as a load balancer. GLB only receives link qualities from neighboring nodes and uses the combined link quality of next-hop... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.2R1. | [
"Global Load Balancing (GLB)"
] |
global-mac-ip-limit | global-mac-ip-limit {
number;
} | [edit logical-systems name protocols l2-learning],
[edit protocols l2-learning] | Limit the number of entries that can be added systemwide to the MAC-IP bindings database. | [
{
"name": "number",
"desc": "Specify the maximum number of entries that can added systemwide to the MAC-IP bindings database.. When the specified maximum is reached, no new entries are added to the database. Range: 20 through 1,048,575."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R2.
Statement introduced in Junos OS Release 18.1R1 for QFX Series switches. | [
"EVPN Proxy ARP and ARP Suppression, and Proxy NDP and NDP Suppression"
] |
global-mac-ip-snooping | global-mac-ip-snooping; | [edit protocols l2-learning] | Enable the global mac-ip snooping feature. On EX4000, EX4100, EX4400, EX4650, and QFX5120
switches in a non-EVPN VLAN scenario, you can learn the MAC-IP information of the host by using this
command in the [edit protocols l2-learning] hierarchy. The MAC-IP information is displayed in the
output of the "show ethernet-sw... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [] |
global-mac-ip-table-aging-time | global-mac-ip-table-aging-time seconds; | [edit logical-systems logical-system-name protocols l2-learning],
[edit protocols l2-learning] | Configure the timeout interval systemwide for entries in the MAC-IP address bindings database. | [
{
"name": "seconds",
"desc": "Specify the time that is elapsed before entries in the MAC-IP bindings database are timed out and deleted. Range: 60 through 1 million seconds Default: 1200 seconds (20 minutes)"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1.
Statement introduced in Junos OS Release 18.1R1 for QFX Series switches. | [
"EVPN Proxy ARP and ARP Suppression, and Proxy NDP and NDP Suppression"
] |
global-mac-limit (Protocols) | global-mac-limit limit {
packet-action drop;
} | [edit protocols l2-learning] | Limit the number of media access control (MAC) addresses learned from the logical interfaces on the
router.
Default
131,071 MAC addresses
NOTE: SRX300, SRX320, SRX340, and SRX345 devices support 16,383 addresses, and
SRX1500 devices support 24,575 addresses. | [
{
"name": "limit",
"desc": "Number of MAC addresses that can be learned on the device."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.5. | [] |
global-mac-limit | global-mac-limit limit {
packet-action drop;
} | [edit protocols l2-learning] | (MX Series routers and EX Series switches only) Limit the number of media access control (MAC)
addresses learned from the logical interfaces on the router or switch.
Default
(MX Series) 393,215 MAC addresses
(EX9200) 524,287 MAC addresses | [
{
"name": "limit",
"desc": "Number of MAC addresses that can be learned systemwide."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Limiting the Number of MAC Addresses Learned from Each Logical Interface"
] |
global-mac-move | global-mac-move {
cooloff-time seconds;
disable-action;
exclusive-mac virtual-mac-mac-address/mask;
interface-recovery-time seconds;
log;
notification-time seconds;
reopen-time seconds;
statistical-approach-wait-time seconds;
threshold-count count;
threshold-time seconds;
... | [edit protocols l2-learning] | Set parameters for media access control (MAC) address move reporting.
Default
By default, MAC moves notify every second, with a threshold time of 1 second and a threshold count
of 50. | [
{
"name": "cooloff-time",
"desc": "Cooloff-time is the time interval during which no additional interface is disabled by the PE"
},
{
"name": "disable-action",
"desc": "(MX Series routers only) Disable the MAC move action feature globally. MAC move"
},
{
"name": "exclusive-mac",
"des... | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Support for logical systems added in Junos OS Release 9.6.
Support for disable-action and reopen-time added in Junos OS Release 13.2.
Support for exclusive-mac added in Junos OS Release 14.1X53-D45.
Statements cooloff-time, interface-recovery-time, statistical-approach-wait... | [
"Configuring MAC Move Parameters",
"MAC Moves Loop Prevention in VPLS Network Overview",
"Example: Configuring Loop Prevention in VPLS Network Due to MAC Moves"
] |
global-mac-statistics | global-mac-statistics; | [edit protocols l2-learning] | (MX Series routers and EX Series switches only) Enable MAC accounting for the entire router or switch.
Default
disabled | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support for logical systems added in Junos OS Release 9.6. | [
"Enabling MAC Accounting"
] |
global-mac-table-aging-time | global-mac-table-aging-time seconds; | [edit protocols l2-learning] | Configure the timeout interval for entries in the MAC table.
NOTE: The global-mac-table-aging-time statement appears in the Junos OS CLI for devices
that support the Enhanced Layer 2 Software (ELS) configuration style. If your device runs
software that does not support ELS, use the "mac-table-aging-time" on page 10695
... | [
{
"name": "seconds",
"desc": "Time elapsed before MAC table entries are timed out and entries are deleted from the table."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Statement modified in Junos OS Release 9.5.
Support for logical systems added in Junos OS Release 9.6. | [
"Configuring the MAC Table Timeout Interval",
"Configuring MAC Table Aging on Switches",
"Example: Configuring VLANs on Security Devices"
] |
global-mode (Protocols) | global-mode (switching | transparent-bridge) ; | [edit protocols l2-learning] | Specify the global mode for the SRX Series Firewall as Layer 2 transparent bridge mode or switching
mode. After changing the mode, you must reboot the device for the configuration to take effect.
Default
On SRX1500, the default Layer 2 global mode is transparent-bridge mode.
Starting with Junos OS Release 15.1X49-D100... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40. | [] |
global-no-control-mac-aging | global-no-control-mac-aging; | [edit logical-systems name protocols l2-learning],
[edit protocols l2-learning] | Disable control MAC-address aging from software. | [] | routing—To view this statement in the configuration.
routing–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [] |
global-no-mac-learning | global-no-mac-learning; | [edit protocols l2-learning] | Disable MAC learning on the entire device.
Default
MAC learning is enabled. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Statement modified for SRX Series in Junos OS Release 9.5.
Support for logical systems added in Junos OS Release 9.6. | [
"Disabling Layer 2 Learning and Forwarding",
"Understanding Q-in-Q Tunneling and VLAN Translation",
"Example: Configuring VLANs on Security Devices"
] |
global-options (Juniper Secure Connect) | global-options {
auth-token-valid-time seconds;
} | [edit security remote-access] | Define global parameters for Juniper Secure Connect remote access configuration. | [
{
"name": "auth-token-valid-time",
"desc": "Authentication token valid time (seconds). Default: 60 seconds Range: 1 through 300"
}
] | security | Statement introduced in Junos OS Release 20.3R1 | [
"Juniper Secure Connect Administrator Guide"
] |
global-parameters (Easy EVPN LAG Configuration) | global-parameters {
anycast-mac anycast-mac;
default-vlan-id vlan-id;
mtu {
overlay overlay-mtu;
underlay underlay-mtu;
}
no-irb-address-auto-derive;
start-aggregate-ethernet-index num;
virtual-gateway {
v4-mac v4-mac;
v6-mac v6-mac;
}
virtual-gateway-mac virtual-gateway-mac;
} | [edit services evpn] | Specify global parameters as part of a generated Ethernet VPN (EVPN) fabric configuration.
You use the statements in the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric
with Ethernet segment identifier (ESI) link aggregation groups (LAGs) in the topology. The feature you
enable with statemen... | [
{
"name": "anycast-mac",
"desc": ""
},
{
"name": "anycast-mac-address",
"desc": "Configure the device to globally use the specified anycast virtual gateway MAC address. You must configure this statement if you include the [edit services evpn evpn-vxlan irb name] use-anycast-address option for an... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
global-supplementary-blackout-timer (Host Fast Reroute) | global-supplementary-blackout-timer minutes; | [edit logical-systems logical-system-name routing-options host-fast-reroute],
[edit routing-options host-fast-reroute] | Set the blackout timer for all host fast-reroute (HFRR) profiles on the routing device.
When you configure HFRR, an optional ARP prefix limit sets a maximum for the number of ARP routes
and, therefore FRR routes created for each HFRR profile in the routing table. This limit prevents ARP
attacks from exhausting the virt... | [
{
"name": "minutes",
"desc": "Number of minutes, in addition to the ARP cache timeout value, before all HFRR profiles on the routing device are reactivated after the ARP prefix limit is exceeded. Range: 1 through 15 minutes"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring Link Protection with Host Fast Reroute"
] |
global-threshold | global-threshold number; | [edit chassis cluster redundancy-group group-number ip-monitoring] | Define global threshold for IP monitoring. This is the number that needs to be met or exceeded by all of
the cumulative weights of the monitored IP addresses to trigger a failover.
When a monitored address is marked as unreachable, the weight value associated with that address is
deducted from the the redundancy group... | [
{
"name": "number",
"desc": "Value at which the IP monitoring weight is applied against the redundancy group failover"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
global-wait-to-restore | global-wait-to-restore minutes; | [edit chassis synchronization] | Use this statement to configure the global time to wait before opening the interface to receive ESMC
messages.
When an interface’s signal transitions out of the signal fail state, it must be fault-free for the global-wait-
to-restore time before it is again considered by the clock selection process.
When the ESMC clock... | [
{
"name": "minutes",
"desc": "Set the time for the port signal to be up before the port is opened to receive and transmit ESMC messages. Range: 0 through 12 minutes Default: 5 minutes"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
global-weight | global-weight number; | [edit chassis cluster redundancy-group group-number ip-monitoring] | Define global weight for IP monitoring. This is the weight that is subtracted from the redundancy group
weight for all of the hosts being monitored. This number specifies the relative importance of IP address
monitored objects in the operation of the redundancy group.
Every monitored IP address is assigned a weight. If... | [
{
"name": "number",
"desc": "Combined weight assigned to all monitored IP addresses. A higher weight value indicates a"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
gnf | gnf id {
control-plane-bandwidth-percent percent;
description description;
fpcs fpcs;
af-name ;
collapsed-forward
} | [edit chassis network-slices guest-network-functions] | Define a GNF by assigning an ID to it.
Junos node slicing enables a single MX Series router to be partitioned to appear as multiple,
independent routers. Each partition has its own Junos control plane, which runs as a virtual machine
(VM), and a dedicated set of line cards. Each partition is called a guest network func... | [
{
"name": "id",
"desc": ""
},
{
"name": "GNF ID",
"desc": "Range: 1–10 The remaining statements are explained separately."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Setting Up Junos Node Slicing"
] |
gpid | gpid (ethernet | hdlc | ipv4 | pos-scrambling-crc-16 | pos-no-scrambling-crc-16 | pos-scrambling-
crc-32 | pos-no-scrambling-crc-32 | ppp); | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name lsp-
attributes],
[edit protocols mpls label-switched-path lsp-name lsp-attributes] | Specify the type of payload carried by the LSP. It can be any of the following:
•
ethernet—Ethernet (GPID value: 33)
•
hdlc—High-level Data Link Control (HDLC) (GPID value: 44)
•
ipv4—IP version 4 (GPID value: 0x0800)
•
pos-no-scrambling-crc-16—for interoperability with other vendors’ equipment (GPID value: 29)
•
pos-n... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
pos-scrambling-crc-16, pos-no-scrambling-crc-16, pos-scrambling-crc-32, and pos-no-scrambling-crc-32 options
added in Junos OS Release 8.0. | [
"Configuring the GPID"
] |
gprs | gprs {
gtp {
handover-default {
deny;
}
ip-group name {
address-book name {
address-set set-name;
}
}
profile (Security GTP) profile-name {
apn pattern-string {
imsi-prefix imsi-prefix-digits {
... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. Statement modified in Junos OS Release 15.1X49-D40. | [
"GPRS Overview",
"GTPv1 Message Filtering",
"SCTP Overview"
] |
gprs-gtp-profile | gprs-gtp-profile gprs-gtp-profile; | [edit logical-systems name security policies from-zone],
[edit logical-systems name security policies global policy name then],
[edit logical-systems name security policies stateful-firewall-rule name policy name then],
[edit logical-systems name tenants name security policies from-zone],
[edit logical-systems name ten... | Use the gprs-gtp-profile option to specify the name of the GPRS tunneling protocol profile. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Enabling GTP Inspection in Policies",
"Understanding GTP Inspection Objects",
"Example: Enabling GTPv2 Inspection in Policies"
] |
gprs-sctp-profile | gprs-sctp-profile gprs-sctp-profile; | [edit logical-systems name security policies from-zone],
[edit logical-systems name security policies global policy name then],
[edit logical-systems name security policies stateful-firewall-rule name policy name then],
[edit logical-systems name tenants name security policies from-zone],
[edit logical-systems name ten... | Use the gprs-sctp-profile option to specify the name of the GPRS stream control protocol profile. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"SCTP Packet Structure Overview"
] |
graceful-deletion-timeout | graceful-deletion-timeout seconds; | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Specify the time, in seconds, before completing graceful deletion of signaling. | [
{
"name": "seconds",
"desc": "Time before completing graceful deletion of signaling."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Graceful Deletion Timeout Interval"
] |
graceful-restart (Enabling Globally) | graceful-restart {
disable;
helper-disable;
maximum-helper-recovery-time seconds;
maximum-helper-restart-time seconds;
notify-duration seconds;
recovery-time seconds;
restart-duration seconds;
stale-routes-time seconds;
} | [edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit routing-options],
[edit routing-instances routing-instance-name routing-options] | You configure the graceful restart routing option globally to enable the feature, but not to enable
graceful restart for all routing protocols in a routing instance. To enable graceful restart globally, include
the graceful-restart statement under the [edit routing options] hierarchy level. This enables graceful
restar... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling Graceful Restart",
"Configuring Routing Protocols Graceful Restart",
"Configuring Graceful Restart for MPLS-Related Protocols",
"Configuring VPN Graceful Restart",
"Configuring Logical System Graceful Restart",
"Configuring Graceful Restart for QFabric Systems"
] |
graceful-restart (Fabric Control) | graceful-restart {
restart-timeseconds;
stale-routes-time seconds;
} | [edit fabric protocols fabric-control] | Configure graceful restart parameters for the fabric control in a QFabric system.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Understanding Routing Engines in the QFabric System"
] |
graceful-restart (Long-Lived for BGP Helper) | graceful-restart {
long-lived {
receiver {
enable:
disable;
}
advertise-to-non-llgr-neighbor {
omit-no-export;
}
}
} | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances instance-name protocols bgp],
[edit... | Configure the graceful restart capability for long-lived BGP sessions to enable BGP routing details to be
retained for a longer period. It in important to retain BGP data for a longer period when the BGP control
plane fails for some reason for slowly-restarting routers for a longer duration. Graceful restart allows a
... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
graceful-restart (Long-Lived for BGP Restarter) | graceful-restart {
disable-notification-flag;
disable-notification-extensions {
omit-no-export;
}
forwarding-state-bit (from-fib | set); /* Configurable to be common for all address families
*/
forwarding-state-bit (as-rr-client | from-fib); /* Configurable for each address family */
lo... | [edit logical-systems logical-system-name protocols bgp family (l2vpn | route-target | inet)
(labeled-unicast | flow)],
[edit logical-systems logical-system-name protocols bgp group group-name family (l2vpn | route-
target | inet) (labeled-unicast | flow)],
[edit logical-systems logical-system-name protocols bgp group... | Configure the graceful restart capability for long-lived BGP sessions on the restarting router to enable
BGP routing details to be retained for a longer period. It in important to retain BGP data for a longer
period when the BGP control plane fails for some reason for slowly-restarting routers for a longer
duration. Yo... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
graceful-restart (Multicast Snooping) | graceful-restart {
disable;
restart-duration seconds;
} | [edit multicast-snooping-options] | Establish the graceful restart duration for multicast snooping. You can set this value between 0 and 300
seconds. If you set the duration to 0, graceful restart is effectively disabled. Set this value slightly larger
than the IGMP query response interval.
Default
180 seconds | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Example: Configuring Multicast Snooping"
] |
graceful-restart (Protocols BGP) | graceful-restart {
disable;
restart-time seconds;
stale-routes-time seconds;
} | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit protocols bgp],
[edit protocols bgp group group-name],
[edit protocols bgp group group-na... | Configure graceful restart for BGP. Graceful restart allows a routing device undergoing a restart to
inform its adjacent neighbors and peers of its condition. Graceful restart is disabled by default. However,
helper mode, the ability to assist a neighboring router attempting a graceful restart, is enabled by
default.
... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Graceful Restart Options for BGP",
"Configuring Graceful Restart for QFabric Systems",
"Junos OS High Availability User Guide"
] |
graceful-restart (Protocols IS-IS) | graceful-restart {
disable;
helper-disable;
restart-duration seconds;
} | [edit logical-systems logical-system-name protocols isis],
[edit protocols isis] | Configure graceful restart parameters for IS-IS.
Graceful restart allows a routing device to restart with minimal effects to the network, and is enabled for
all routing protocols at the [edit routing-options] hierarchy level. When graceful restart is enabled, the
restarting routing device is not removed from the networ... | [
{
"name": "disable",
"desc": "Disable graceful restart for IS-IS."
},
{
"name": "helper-disable",
"desc": "Disable graceful restart helper capability. Helper mode is enabled by default."
},
{
"name": "restart-duration seconds",
"desc": "Time period for the restart to last, in seconds... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Routing Protocols Graceful Restart"
] |
graceful-restart (Protocols LDP) | graceful-restart {
disable;
helper-disable;
maximum-neighbor-recovery-time value;
reconnect-time seconds;
recovery-time value;
} | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Configure LDP graceful restart on the LDP primary protocol instance or for a specific routing instance.
NOTE: When you alter the graceful restart configuration at either the [edit routing-
options graceful-restart] or [edit protocols ldp graceful-restart] hierarchy levels, any
running LDP session is automatically rest... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring LDP Graceful Restart"
] |
graceful-restart (Protocols OSPF) | graceful-restart {
disable;
helper-disable (standard | restart-signaling | both);
no-strict-lsa-checking;
notify-duration seconds;
restart-duration seconds;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit protocols (ospf | ospf3)],
[edit routing-instances routing-instance-name protocols ospf] | Configure graceful restart for OSPF.
Graceful restart allows a routing device to restart with minimal effects to the network, and is enabled for
all routing protocols at the [edit routing-options] hierarchy level. | [
{
"name": "disable",
"desc": "Disable graceful restart for OSPF."
},
{
"name": "helper-disable",
"desc": ""
},
{
"name": "(standard |",
"desc": ""
},
{
"name": "restart-signaling|",
"desc": ""
},
{
"name": "both)",
"desc": "Disable helper mode for graceful res... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for the no-strict-lsa-checking statement introduced in Junos OS Release 8.5.
Support for the helper mode standard, restart-signaling, and both options introduced in Junos OS
Release 11.4. | [
"Example: Configuring Graceful Restart for OSPF",
"Example: Configuring the Helper Capability Mode for OSPFv2 Graceful Restart",
"Example: Configuring the Helper Capability Mode for OSPFv3 Graceful Restart",
"Example: Disabling Strict LSA Checking for OSPF Graceful Restart"
] |
graceful-restart (Protocols PIM) | graceful-restart {
disable;
no-bidirectional-mode;
restart-duration seconds;
} | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Configure PIM sparse mode graceful restart.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring PIM Sparse Mode Graceful Restart"
] |
graceful-restart (Protocols RIP) | graceful-restart {
disable;
restart-time seconds;
} | [edit logical-systems logical-system-name protocols rip],
[edit protocols rip] | Configure graceful restart for RIP. | [
{
"name": "disable",
"desc": "Disables graceful restart for RIP."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Junos OS High Availability User Guide"
] |
graceful-restart (Protocols RIPng) | graceful-restart {
disable;
restart-time seconds;
} | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng],
[edit protocols ripng],
[edit routing-instances routing-instance-name protocols ripng] | Configure graceful restart for RIPng. | [
{
"name": "disable",
"desc": "Disables graceful restart for RIPng."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances introduced in Junos OS Release 9.0. | [
"Junos OS High Availability User Guide"
] |
graceful-restart (Protocols RSVP) | graceful-restart {
disable;
helper-disable;
maximum-helper-recovery-time seconds;
maximum-helper-restart-time seconds;
} | [edit logical-systems logical-system-name routing-options],
[edit protocols rsvp],
[edit routing-options] | Configure graceful restart on the router. You must configure the graceful-restart statement at the [edit
routing-options] hierarchy level to enable graceful restart on the router. | [
{
"name": "disable",
"desc": "Disable graceful restart on the router or for RSVP."
},
{
"name": "helper-disable",
"desc": "Disable RSVP graceful restart helper mode (this option is only available at the [edit"
},
{
"name": "maximum-helper-recovery-time seconds",
"desc": "The maximum ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring RSVP Graceful Restart"
] |
graceful-shutdown (Protocols BGP) | graceful-shutdown {
receiver {
disable;
local-preference <value>;
}
sender {
local-preference <value>;
}
} | [edit protocols bgp],
[edit protocols bgp group group-name],
[edit protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-na... | Configure graceful shutdown feature for BGP. Graceful shutdown migrates traffic from one BGP next-
hop to another without interrupting the traffic flow. This feature can be enabled for both IBGP and
EBGP. The router on which the graceful shutdown is performed is known as the sender or initiator. The
receiver is the rou... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [] |
graceful-switchover (Chassis) | graceful-switchover; | [edit chassis redundancy] | For devices with more than one Routing Engine, including those in a Virtual Chassis or a Virtual Chassis
Fabric, configure the primary Routing Engine to switch over gracefully to a backup Routing Engine
without interruption to packet forwarding.
NOTE: The graceful-switchover statement at the [edit chassis redundancy] h... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding Graceful Routing Switchover",
"Configuring Graceful Routing Engine Switchover"
] |
gratuitous-arp-count | gratuitous-arp-count number; | [edit chassis cluster redundancy-group group-number] | Specify the number of gratuitous Address Resolution Protocol (ARP) requests to send on an active
interface after failover.
You can configure this option to specify the number of gratuitous ARP requests that an interface can
send to notify other network devices of its presence after the redundancy group it belongs to ha... | [
{
"name": "number",
"desc": "Number of gratuitous ARP requests that a newly elected primary device in a chassis cluster"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [] |
gratuitous-arp-reply | (gratuitous-arp-reply | no-gratuitous-arp-reply); | [edit interfaces interface-name],
[edit interfaces interface-range interface-range-name] | Enable processing of ARP updates received via gratuitous ARP reply messages.
Default
Updating of the ARP cache is disabled on all Ethernet interfaces. | [
{
"name": "gratuitous-arp-reply",
"desc": "Update the ARP cache."
},
{
"name": "no-gratuitous-arp-reply",
"desc": "Do not update the ARP cache."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
gre (Ids-option) | gre {
gre-4in4;
gre-4in6;
gre-6in4;
gre-6in6;
} | [edit security screen ids-option ids-option-name ip tunnel] | Configure IP tunnel GRE IDS option. | [
{
"name": "gre-4in4",
"desc": "Enable IP tunnel GRE 4in4 IDS option."
},
{
"name": "gre-4in6",
"desc": "Enable IP tunnel GRE 4in6 IDS option."
},
{
"name": "gre-6in4",
"desc": "Enable IP tunnel GRE 6in4 IDS option."
},
{
"name": "gre-6in6",
"desc": "Enable IP tunnel GRE 6... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D10. | [
"Attack Detection and Prevention Overview"
] |
gre (Routing Options) | gre <source-address> <destination-networks>; | [edit logical-systems logical-system-name routing-options dynamic-tunnels tunnel-name],
[edit routing-options dynamic-tunnels tunnel-name] | Define a dynamic generic routing encapsulation (GRE) tunnel for IPv4 to automatically establish label-
switched paths (LSPs) for any new provider edge (PE) router added to a full mesh of LSPs. | [
{
"name": "destination-networks",
"desc": "A list of one or more destination prefixes that are reachable through the GRE tunnel."
},
{
"name": "source-address",
"desc": "The source address used for the dynamic GRE tunnel."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
next-hop-based-tunnel option introduced in Junos OS Release 16.2. | [
"Configuring MPLS-Signaled LSPs to Use GRE Tunnels"
] |
gre | gre {
destination {
addressaddress;
}
key key; key;
source {
addressaddress;
}
{
routing-instance routing-instance;
}
tunnel-termination;
} | [edit interfaces fti number unit logical-unit-number tunnel encapsulation] | Configure GRE (Generic Routing Encapsulation) encapsulation type. | [] | interface | Statement introduced in Junos OS Evolved Release 20.2R1. | [] |
gre-in | gre-in {
mss value;
} | [edit security flow tcp-mss] | Enable and specify the TCP maximum segment size (TCP MSS) for Generic Routing Encapsulation (GRE)
packets that are coming out from an IPsec VPN tunnel. If the device receives a GRE-encapsulated TCP
packet with the SYN bit and TCP MSS option set and the TCP MSS option specified in the packet
exceeds the TCP MSS specifie... | [
{
"name": "mss value",
"desc": "TCP MSS for GRE packets. Value is optional."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
gre-out | gre-out {
mss value;
} | [edit security flow tcp-mss] | Enable and specify the TCP maximum segment size (TCP MSS) for Generic Routing Encapsulation (GRE)
packets that are going into an IPsec VPN tunnel. If the device receives a GRE-encapsulated TCP packet
with the SYN bit and TCP MSS option set and the TCP MSS option specified in the packet exceeds the
TCP MSS specified by ... | [
{
"name": "mss value",
"desc": "TCP MSS for GRE packets. Value is optional."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
gre-performance-acceleration (Security Flow) | gre-performance-acceleration; | [edit security flow] | Enables GRE performance acceleration. This helps to accelerate GRE traffic performance. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1 for SRX Series and NFX Series. | [] |
greater-than | greater-than value; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format integer],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format time] | Specify a value for the custom AVP attribute above which the incoming RADIUS request from the
subscriber must match.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected. | [
{
"name": "value",
"desc": "Value that the attribute must be greater than."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
gres-route-flush-delay (Subscriber Management) | gres-route-flush-delay; | [edit system services subscriber-management] | For a subscriber network configured with either nonstop active routing (NSR) or graceful restart,
configure the router to wait 180 seconds (3 minutes) before removing (flushing) static or dynamic access
routes and access-internal routes from the forwarding table after a graceful Routing Engine switchover
(GRES) has tak... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"High Availability for Subscriber Access Networks"
] |
group (Bridge Domains) | group ip-address {
source ip-address;
} | [edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name static],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id interface interface-
name static],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping inter... | Configure the IGMP multicast group address that receives data on an interface and (optionally) a source
address for certain packets. | [
{
"name": "ip-address",
"desc": "Group address."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring IGMP Snooping"
] |
group (Configuring Group Name) | group group-name {
(default-context-prefix | context-prefix context-prefiix){
security-model (any | usm | v1 | v2c) {
security-level (authentication | none | privacy) {
notify-view view-name;
read-view view-name;
write-view view-name;
}... | [edit snmp v3 vacm access] | Assign the security name to a group, and specify the SNMPv3 context applicable to the group. The
default-context-prefix statement, when included, adds all the contexts configured on the device to the
group, whereas the context-prefix context-prefix statement enables you to specify a context and to add
that particular c... | [
{
"name": "group-name",
"desc": "SNMPv3 group name created for the SNMPv3 group."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Group"
] |
group (Defining Access Privileges for an SNMPv3 Group) | group group-name; | [edit snmp v3 vacm security-to-group security-model (usm | v1 | v2c) security-name security-name] | Define access privileges granted to a group. | [
{
"name": "group-name",
"desc": "Identifies a collection of SNMP security names that belong to the same access policy SNMP."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Group"
] |
group (DHCP Local Server) | group group-name {
access-profile profile-name;
authentication {
password password-string;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name-string;
interface-description (device-interfa... | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server ...],
[edit logical-systems logical-system-name system services dhcp-local-server ...],
[edit routing-instances ... | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "group-name",
"desc": "Name of the group. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
interface-tag option introduced in Junos OS Release 23.2R1 | [
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Grouping Interfaces with Common DHCP Configurations",
"Specifying Authentication Support",
"Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces",
"DHCP Liveness Detection Using ARP and Neighbor Discovery Packe... |
group (DHCP Relay Agent) | group group-name {
access-profile profile-name;
active-server-group server-group-name;
authentication {
password password-string;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name-string;
... | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay ...],
[edit routing-instances routing-instance... | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "group-name",
"desc": "Name of a group of interfaces that have a common DHCP or DHCPv6 relay agent configuration. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
interface-tag option introduced in Junos OS Release 23.2R1 | [
"Extended DHCP Relay Agent Overview",
"Configuring DHCP Relay Agent",
"Configuring Group-Specific DHCP Relay Options",
"Grouping Interfaces with Common DHCP Configurations",
"Specifying Authentication Support",
"Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces",
"DHCP L... |
group (DHCP Security for MX Series) | group group-name {
interface interface-name {
static-ip ip-address {
mac mac-address;
}
}
overrides {
no-option82;
trusted;
untrusted;
}
} | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] | Specify the name of a group of access interfaces that you want to configure for DHCP security
attributes that are different from the attributes set for other interfaces in the VLAN or bridge domain. A
group must contain at least one interface.
The remaining statements are explained separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10 .
Support for the static-ipv6 and no-option37 statements introduced in Junos OS Release 13.2X51-D20 for
EX Series switches. | [
"Configuring Static DHCP IP Addresses for DHCP snooping (MX routers)",
"Enabling a Trusted DHCP Server (MX Series Routers)",
"Understanding DHCP Snooping (non-ELS)"
] |
group (DHCP Security) | group group-name {
interface interface-name {
static-ip ip-address {
mac mac-address;
}
static-ipv6 ip-address {
mac mac-address;
}
}
overrides {
no-dhcpv6-options;
no-option16;
no-option18;
no-option37;
no-opt... | [edit vlans vlan-name forwarding-options dhcp-security] | Specify the name of a group of access interfaces that you want to configure for DHCP security
attributes that are different from the attributes set for other interfaces in the VLAN. A group must
contain at least one interface.
The remaining statements are explained separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10 .
Support for the static-ipv6 and no-option37 statements introduced in Junos OS Release 13.2X51-D20 for
EX Series switches. | [
"Configuring Static DHCP IP Addresses for DHCP snooping (ELS)",
"Enabling a Trusted DHCP Server (ELS)",
"Understanding DHCP Snooping (non-ELS)"
] |
group (DHCP Spoofing Prevention) | group group-name {
interface interface-name;
} | [edit routing-instances routing-instance-name bridge-domains bridge-domain-name forwarding-options
dhcp-relay],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay] | Configure Dynamic Host Configuration Protocol (DHCP) snooping on the router. When acting as a
snooping agent, the MX Series router typically is located between the client and the DHCP relay agent.
It creates filters by “snooping” DHCP messages and binding DHCP-issued IP addresses with the MAC
address of the client. The... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4 (MX Series routers only). | [
"Preventing DHCP Spoofing on MX Series 5G Universal Routing Platforms"
] |
group (Distributed IGMP) | group multicast-group-address {
<distributed>;
source source-address <distributed>;
} | [edit protocols pim static] | Specify the multicast group address for the multicast group that is statically configured on an interface. | [
{
"name": "distributed",
"desc": "(Optional) Preprovision a specific multicast group address (G)."
},
{
"name": "multicast-group-address",
"desc": "Specific multicast group address being statically configured on an interface. The remaining statements are explained separately."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X50. | [
"Enabling Distributed IGMP",
"Junos OS Multicast Protocols User Guide",
"Junos OS Multicast Protocols User Guide"
] |
group (Dynamic IGMP Interface) | For group configuration with a source, use the following syntax:
group ip-address {
source ip-address;
}
For group configuration without a source, use the following syntax:
group group; | [edit dynamic-profiles profile-name protocols igmp interface interface-name static] | When configuring with a source address, configure the IGMP multicast group address that receives data
on an interface and a source address for certain packets. For configuration without a source address,
configure only the IGMP multicast group address that receives data on an interface. | [
{
"name": "ip-address",
"desc": "Group IP address."
},
{
"name": "group",
"desc": "Name of group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Enabling IGMP Static Group Membership"
] |
group (Dynamic MLD Interface) | group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
} | [edit dynamic-profiles profile-name protocols mld interface interface-name static] | The MLD multicast group address and (optionally) the source address for the multicast group being
dynamically configured on an interface. | [
{
"name": "multicast-group-address",
"desc": "Address of the group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD Static Group Membership"
] |
group (IGMP Snooping) | group ip-address; | [edit protocols igmp-snooping vlan (all | vlan-name) interface (all | interface-name) static] | Configure a static multicast group on an interface. | [
{
"name": "ip-address",
"desc": "IP address of the multicast group receiving data on an interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [] |
group (Origin Validation for BGP) | group group-name {
max-sessions number;
session address {
hold-time seconds;
local-address local-ip-address;
port port-number;
preference number;
record-lifetime seconds;
refresh-time seconds;
traceoptions {
file filename <files number> <size... | [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation],
[edit logical-systems logical-system-name routing-options validation],
[edit routing-instances instance-name routing-options validation],
[edit routing-options validation] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "group-name",
"desc": "Name of the validation group."
},
{
"name": "max-sessions",
"desc": ""
},
{
"name": "number",
"desc": "Configure the number of concurrent sessions for each group. If the number of sessions in a group exceeds the max-sessions value, the connections are... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
group (Protocols BGP) | group group-name {
advertise-bgp-static
advertise-inactive;
allow [ network/mask-length ];
authentication-key key;
cluster cluster-identifier;
damping;
description text-description;
enforce-first-as;
export [ policy-names ];
family {
(inet | inet6 | inet-vpn | inet6-vpn |... | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp],
[edit protocols bgp],
[edit protocols bgp family prefix-limit (inet | inet6)(any | flow | labeled-unicast | multicast |
unicast)],
[edit routing-instances routing-... | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "group-name",
"desc": "Name of the BGP group"
},
{
"name": "link-bandwith",
"desc": ""
},
{
"name": "auto-sense",
"desc": "Enable this option to automatically detect the bandwidth towards the peer and attach the link-bandwith value to the interface speed over which the BGP ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
link-bandwith auto-sense, and send-non-transitive-link-bandwidth options introduced in Junos OS Release
24.2R1. | [
"BGP User Guide"
] |
group (Protocols IGMP) | group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
} | [edit logical-systems logical-system-name protocols igmp interface interface-name static],
[edit protocols igmp interface interface-name static] | Specify the IGMP multicast group address and (optionally) the source address for the multicast group
being statically configured on an interface.
NOTE: You must specify a unique address for each group.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling IGMP Static Group Membership"
] |
group (Protocols MLD Snooping) | group multicast-group-address {
source ip-address;
} | [edit protocols mld-snooping vlan (all | vlan-name) interface (all | interface-name) static],
[edit routing-instances instance-name protocols mld-snooping vlan vlan-name interface interface-
name static] | Configure a static multicast group on an interface and (optionally) the source address for the multicast
group. | [
{
"name": "multicast-group-address",
"desc": "Valid IP multicast address for the multicast group."
},
{
"name": "source ip-address",
"desc": "Valid IP multicast address for the source of the multicast group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1.
Support at the [edit routing-instances instance-name protocols mld-snooping vlan vlan-name interface interface-
name static] hierarchy level introduced in Junos OS Release 13.3 for EX Series switches.
Support for the source statement introduced in Junos OS Release 13.3 for... | [
"Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)"
] |
group (Protocols MLD) | group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
} | [edit logical-systems logical-system-name protocols mld interface interface-name static],
[edit protocols mld interface interface-name static] | The MLD multicast group address and (optionally) the source address for the multicast group being
statically configured on an interface. | [
{
"name": "multicast-group-address",
"desc": "Address of the group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling MLD Static Group Membership"
] |
group (Protocols MSDP) | group group-name {
disable;
export [ policy-names ];
import [ policy-names ];
local-address address;
mode (mesh-group | standard);
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
}
peer add... | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
msdp],
[edit protocols msdp],
[edit routing-instances routing-instance-name protocols msdp] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "group-name",
"desc": "Name of the MSDP group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring MSDP in a Routing Instance"
] |
group (Protocols PIM) | group group-address {
source source-address {
rate threshold-rate;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
mdt threshold],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family inet | inet6mdt threshold],
[edit routing-instances routing-instance-name protocols pim mdt threshol... | Specify the explicit or prefix multicast group address to which the threshold limits apply. This is typically
a well-known address for a certain type of multicast traffic. | [
{
"name": "group-address",
"desc": "Explicit group address to limit."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. In Junos OS Release 17.3R1, the mdt hierarchy was
moved from provider-tunnel to the provider-tunnel family inet and provider-tunnel family inet6 hierarchies as
part of an upgrade to add IPv6 support for default MDT in Rosen 7, and data MDT for Rosen 6 and
Rosen 7. The p... | [
"Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode",
"Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode"
] |
group (Protocols RIP) | group group-name {
bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-in... | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit protocols rip],
[edit routing-instances routing-instance-name protocols rip] | Configure a set of RIP neighbors that share an export policy and metric. The export policy and metric
govern what routes to advertise to neighbors in a given group. Each group must contain at least one
neighbor. You should create a group for every export policy. | [
{
"name": "group-name",
"desc": "Name of a group, up to 16 characters long."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring RIP"
] |
group (Protocols RIPng) | group group-name {
export [ policy-names ];
metric-out metric;
neighbor neighbor-name {
import policy-name;
metric-in metric;
receive <none>;
route-timeout seconds;
send <none>;
update-interval seconds;
}
preference number;
route-timeout seconds;
... | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng],
[edit protocols ripng],
[edit routing-instances routing-instance-name protocols ripng] | Configure a set of RIPng neighbors that share an export policy and metric. The export policy and metric
govern what routes to advertise to neighbors in a given group.
Each group must contain at least one neighbor. You should create a group for each export policy that
you have. | [
{
"name": "group-name",
"desc": "Name of a group, up to 16 characters long."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances introduced in Junos OS Release 9.0. | [] |
group (Redundant Trunk Groups) | group name {
interface interface-name <primary>;
interface interface-name;
preempt-cutover-timer seconds;
} | For platforms with ELS:
[edit switch-options redundant-trunk-group]
For platforms without ELS:
[edit ethernet-switching-options redundant-trunk-group] | Create a redundant trunk group. | [
{
"name": "name",
"desc": "The name of the redundant trunk group."
}
] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Hierarchy level [edit switch-options] introduced in Junos OS Release 13.2X50-D10 (ELS). (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"Example: Configuring Redundant Trunk Links for Faster Recovery on EX Series Switches",
"Example: Configuring Redundant Trunk Links for Faster Recovery on Devices with ELS Support",
"Understanding Redundant Trunk Links (Legacy RTG Configuration)"
] |
group (Routing Instances) | group address {
source source-address {
inter-region-segmented {
fan-out fan-out value;
threshold rate-value;
}
ldp-p2mp;
pim-ssm {
group-range multicast-prefix;
}
rsvp-te {
label-switched-path-template {
... | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective],
[edit routing-instances routing-instance-name provider-tunnel selective] | Specify the IP address for the multicast group configured for point-to-multipoint label-switched paths
(LSPs) and PIM-SSM GRE selective provider tunnels. | [
{
"name": "address",
"desc": "Specify the IP address for the multicast group. This address must be a valid multicast group"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
The inter-region-segmented statement added in Junos OS Release 15.1. | [
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN",
"Configuring PIM-SSM GRE Selective Provider Tunnels"
] |
group (RPF Selection) | group group-address{
sourcesource-address{
next-hop next-hop-address;
}
wildcard-source {
next-hop next-hop-address;
}
} | [edit routing-instances routing-instance-name edit protocols pim rpf-selection] | Configure the PIM group address for which you configure RPF selection"group (RPF Selection)" on page
8214.
Default
By default, PIM RPF selection is not configured. | [
{
"name": "group-address",
"desc": "PIM group address for which you configure RPF selection."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.4. | [
"Example: Configuring PIM RPF Selection"
] |
group (Security Group VPN) | group name {
anti-replay-time-window milliseconds;
description description;
group-id number;
ike-gateway gateway-name;
ipsec-sa name {
match-policy policy-name {
destination ip-address/netmask;
destination-port number;
protocol number;
source i... | [edit security group-vpn server] | Configure group VPN on the group server. Group VPNv2 is supported on SRX300, SRX320, SRX340,
SRX345, SRX550HM, SRX1500, SRX4100, SRX4200, and SRX4600 devices and vSRX Virtual Firewall
instances. | [
{
"name": "name",
"desc": "Name of the group."
},
{
"name": "anti-replay-time-window milliseconds",
"desc": "Configure antireplay time in milliseconds. Specify a value from 1"
},
{
"name": "description description",
"desc": "Description of the group."
},
{
"name": "group-id n... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2
member-threshold option introduced in Junos OS Release 15.1X49-D30 for vSRX Virtual Firewall. | [
"Group VPNv2 Overview"
] |
group (Static Subscribers) | group group-name {
access-profile profile-name;
dynamic-profile profile-name {
aggregate-clients (merge | replace);
}
authentication {
password password-string;
username-include {
delimiter delimiter-character;
domain-name domain-name;
interfac... | [edit logical-systems logical-system-name system services static-subscribers],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers],
[edit routing-instances routing-instances-name system services static-subscribers],
[edit system services static-subscri... | Configure a static subscriber group with values that override the values configured at the [edit system
services static-subscribers] hierarchy level for subscribers outside the group. Includes the subscriber
access and dynamic profiles, the authentication parameters that trigger the Access-Request message to
AAA for st... | [
{
"name": "group-name",
"desc": "Name of a group that defines authentication parameters for static subscribers to override the"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Creating a Static Subscriber Group"
] |
group (System Services DHCP) | group group-name {
authentication {
password password;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
logical-system-name;
relay-agent-interface-id... | [edit system services dhcp-local-server dhcpv6] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "group-name",
"desc": "Name of the group."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Overview",
"DHCP Server",
"DHCP Server Configuration"
] |
group (Traffic Load Balancer) | group group-name {
control-interface control-interface-name;
health-check-interface-subunit health-check-interface-subunit;
network-monitoring-profile [profile-name1, <profile-name2>];
real-service-rejoin-options no-auto-rejoin;
real-services [server-list];
<routing-instance routing-instance>;
} | [edit services traffic-load-balance instance instance-name] | Configure a group of servers as a pool for next-hop session distribution. | [
{
"name": "group-name",
"desc": "Use the specified string identifier for a group of servers to which sessions are distributed using the server distribution table in conjunction with the session distribution API."
},
{
"name": "control-interface control-interface-name",
"desc": "Use the specified... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card.
Support added for control-interface option for Connected Security Distributed Services (CSDS) in Junos
OS Release 25.4R1. | [
"Traffic Load Balancer Overview",
"Configuring TLB"
] |
group (Uplink Failure Detection) | group group-name {
debounce-interval seconds;
link-to-monitor interface-name;
link-to-disable interface-name;
} | [edit protocols uplink-failure-detection] | Configure a group of uplink and downlink interfaces for uplink failure detection. You can also configure
the debounce interval, which is the amount of time, in seconds, that elapses before the downlink
interfaces are brought up after a state change of the uplink interfaces. | [
{
"name": "group-name",
"desc": "Name of the uplink-failure-detection group."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Overview of Uplink Failure Detection",
"Configuring Interfaces for Uplink Failure Detection",
"Example: Configuring Interfaces for Uplink Failure Detection"
] |
group | group group-name {
debounce-interval seconds;
link-to-monitor interface-name;
link-to-disable interface-name;
} | [edit protocols uplink-failure-detection] | Configure a group of uplink and downlink interfaces for uplink failure detection. | [
{
"name": "group-name",
"desc": "Name of the uplink failure detection group."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Overview of Uplink Failure Detection",
"Configuring Interfaces for Uplink Failure Detection",
"Example: Configuring Interfaces for Uplink Failure Detection"
] |
group-address (Routing Instances Tunnel Group) | group-address address; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family inet | inet6 pim-ssm],
[edit routing-instances routing-instance-name provider-tunnel family inet | inet6 pim-ssm] | Configure the PIM-ASM (Rosen 6) or PIM-SSM (Rosen 7) provider tunnel group address. Each MDT is
linked to a group address in the provider space. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
In Junos OS Release 17.3R1, the pim-ssm hierarchy was moved from provider-tunnel to the provider-tunnel
family inet and provider-tunnel family inet6 hierarchies as part of an upgrade to add IPv6 support for
default multicast distribution tree (MDT) in Rosen 7, and data MDT... | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
group-address (Routing Instances VPN) | group-address address; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel pim-asm],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel pim-asm family inet],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider... | Specify a group address on which to encapsulate multicast traffic from a virtual private network (VPN)
instance.
NOTE: IPv6 provider tunnels are not currently supported for draft-rosen MVPNs. They
are supported for MBGP MVPNs. | [
{
"name": "address",
"desc": "For IPv4, IP address whose high-order bits are 1110, giving an address range from 224.0.0.0"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Starting with Junos OS Release 11.4, to provide consistency with draft-rosen 7 and next-generation
BGP-based multicast VPNs, configure the provider tunnels for draft-rosen 6 anysource multicast VPNs
at the [edit routing-instances routing-instance-name provider-tunnel] h... | [
"Example: Configuring Any-Source Multicast for Draft-Rosen VPNs",
"Configuring Multicast Layer 3 VPNs",
"Multicast Protocols User Guide"
] |
group-count (Dynamic MLD Interface) | group-count number; | [edit dynamic-profiles profile-name protocols mld interface interface-name static group multicast-
group-address] | Configure the number of static groups to be created over the dynamic interface. | [
{
"name": "number",
"desc": "Number of static groups."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD Static Group Membership"
] |
group-count (Protocols IGMP) | group-count number; | [edit logical-systems logical-system-name protocols igmp interface interface-name static group
multicast-group-address],
[edit protocols igmp interface interface-name static group multicast-group-address] | Specify the number of static groups to be created. | [
{
"name": "number",
"desc": "Number of static groups."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Enabling IGMP Static Group Membership"
] |
group-count (Protocols MLD) | group-count number; | [edit logical-systems logical-system-name protocols mld interface interface-name static group
multicast-group-address],
[edit protocols mld interface interface-name static group multicast-group-address] | Configure the number of static groups to be created. | [
{
"name": "number",
"desc": "Number of static groups."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Enabling MLD Static Group Membership"
] |
group-increment (Dynamic MLD Interface) | group-increment increment; | [edit dynamic-profiles profile-name protocols mld interface interface-name static group multicast-
group-address source] | Configure the number of times the address should be incremented for each static group created on a
dynamic interface. The increment is specified in a format similar to an IPv6 address. | [
{
"name": "increment",
"desc": "Number of times the address should be incremented."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD Static Group Membership"
] |
group-increment (Protocols IGMP) | group-increment increment; | [edit logical-systems logical-system-name protocols igmp interface interface-name static group
multicast-group-address],
[edit protocols igmp interface interface-name static group multicast-group-address] | Configure the number of times the address should be incremented for each static group created. The
increment is specified in dotted decimal notation similar to an IPv4 address. | [
{
"name": "increment",
"desc": "Number of times the address should be incremented."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Enabling IGMP Static Group Membership"
] |
group-increment (Protocols MLD) | group-increment number; | [edit logical-systems logical-system-name protocols mld interface interface-name static group
multicast-group-address],
[edit protocols mld interface interface-name static group multicast-group-address] | Configure the number of times the address should be incremented for each static group created. The
increment is specified in a format similar to an IPv6 address. | [
{
"name": "increment",
"desc": "Number of times the address should be incremented."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Enabling MLD Static Group Membership"
] |
group-limit (Dynamic IGMP Interface) | group-limit limit; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Configure a limit for the number of multicast groups (or [S,G] channels in IGMPv3) allowed on a dynamic
logical interface. After this limit is reached, new reports will be ignored and all related flows are not
flooded on the logical interface.
Default
By default, there is no limit to the number of multicast groups that... | [
{
"name": "limit",
"desc": "group limit value for the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces"
] |
group-limit (Dynamic MLD Interface) | group-limit limit; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | Configure a limit for the number of multicast groups (or [S,G] channels in MLDv2) allowed on a dynamic
logical interface. After this limit is reached, new reports will be ignored and all related flows are not
flooded on the logical interface.
Default
By default, there is no limit to the number of multicast groups that ... | [
{
"name": "limit",
"desc": "group limit value for the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Dynamic MLD Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Configuring the Number of MLD Multicast Group Joins on Logical Interfaces"
] |
group-limit (IGMP and MLD Snooping) | group-limit limit; | [edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id interface interface-
name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping interface interface... | Configure a limit for the number of multicast groups (or [S,G] channels in IGMPv3) allowed on an
interface. After this limit is reached, new reports are ignored and all related flows are not flooded on the
interface.
Default
By default, there is no limit to the number of multicast groups joining an interface. | [
{
"name": "limit",
"desc": "a 32-bit number for the limit on the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring IGMP Snooping"
] |
group-limit (IGMP) | group-limit limit; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Configure a limit for the number of multicast groups (or [S,G] channels in IGMPv3) allowed on an
interface. After this limit is reached, new reports are ignored and all related flows are not flooded on the
interface.
To confirm the configured group limit on the interface, use the show igmp interface command.
Default
By... | [
{
"name": "limit",
"desc": "group limit value for the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces"
] |
group-limit (Protocols MLD) | group-limit limit; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Configure a limit for the number of multicast groups (or [S,G] channels in MLDv2) allowed on a logical
interface. After this limit is reached, new reports are ignored and all related flows are not flooded on the
interface.
Default
By default, there is no limit to the number of multicast groups that can join the interfa... | [
{
"name": "limit",
"desc": "group value limit for the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Configuring MLD"
] |
group-members | group-members [attack-or-attack-group-name]; | [edit security idp custom-attack-group custom-attack-group-name] | Specify the group members in a custom group. The members can be predefined attacks, predefined
attack groups, custom attacks, or custom dynamic groups.
Use custom groups for the following tasks:
•
To define a specific set of attacks to which you know your network is vulnerable.
•
To group your custom attack objects.
•
... | [
{
"name": "attack-or-attack-group-name",
"desc": "Name of the attack object or group attack object."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
group-policy (Dynamic IGMP Interface) | group-policy policy-name; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Compare the IGMPv2 or IGMPv3 group against the specified group policy, after receiving an IGMP
report, and perform the action configured in that policy (for example, reject the report). | [
{
"name": "policy-name",
"desc": "Name of the group policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Filtering Unwanted IGMP Reports at the IGMP Interface Level"
] |
group-policy (Dynamic MLD Interface) | group-policy policy-name; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | Compare the MLDv1 or MLDv2 group against the specified group policy, after receiving an MLD report,
and perform the action configured in that policy (for example, reject the report). | [
{
"name": "policy-name",
"desc": "Name of the group policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Dynamic MLD Configuration Overview",
"Filtering Unwanted MLD Reports at the MLD Interface Level"
] |
group-policy (Protocols IGMP AMT Interface) | group-policy [ policy-names ]; | [edit logical-systems logical-system-name protocols igmp amt relay defaults],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols igmp
amt relay defaults],
[edit protocols igmp amt relay defaults],
[edit routing-instances routing-instance-name protocols igmp amt relay defaults] | When this statement is enabled on the Automatic Multicast Tunneling (AMT) interfaces running IGMP
version 2 (IGMPv2) or version 3 (IGMPv3), after the router receives an IGMP report, the router
compares the group against the specified group policy and performs the action configured in that policy
(for example, rejects t... | [
{
"name": "policy-names",
"desc": "Name of the policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Default IGMP Parameters for AMT Interfaces"
] |
group-policy (Protocols IGMP) | group-policy [ policy-names ]; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | When this statement is enabled on a router running IGMP version 2 (IGMPv2) or version 3 (IGMPv3),
after the router receives an IGMP report, the router compares the group against the specified group
policy and performs the action configured in that policy (for example, rejects the report). | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Filtering Unwanted IGMP Reports at the IGMP Interface Level"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.