Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

group-range (Data MDTs)

date_range 19-Nov-23

Syntax

content_copy zoom_out_map
group-range multicast-prefix;

Hierarchy Level

content_copy zoom_out_map
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel family inet | inet6mdt],
[edit routing-instances routing-instance-name  provider-tunnel family inet | inet6mdt]

Description

Establish the group range to use for data MDTs created in this VRF instance. Only IPv4 address are valid for group range. This address range cannot overlap the default MDT addresses of any other VPNs on the router, nor can the group range specified under the inet and inet6 hierarchies overlap. If you configure overlapping group ranges, the configuration commit fails. Up to 8000 MDT group ranges are supported for IPv4 and IPv6.

Options

multicast-prefix—Multicast address range to identify data MDTs.

  • Range: Any valid, nonreserved multicast address range

  • Default: None (No data MDTs are created for this VRF instance.)

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

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 provider-tunnel mdt hierarchy is now hidden for backward compatibility with existing scripts.

footer-navigation