close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

inter-as (Routing Instances)

date_range 19-Nov-23

arrow_backward

arrow_forward

Syntax

inter-as{ 
    ingress-replication { 
        create-new-ucast-tunnel;
        label-switched-path-template {
            (default-template lsp-template-name);
        }
    }
    inter-region-segmented { 
        fan-out <leaf-AD routes>);
        threshold <kilobits>);
    }
    ldp-p2mp;
    rsvp-te {
        label-switched-path-template {
            (default-template lsp-template-name);
        }
    }
}

Hierarchy Level

content_copy zoom_out_map
[edit routing-instances routing-instance-name provider-tunnel]

Description

These statements add Junos support for segmented RSVP-TE provider tunnels with next-generation Layer 3 multicast VPNs (MVPN), that is, Inter-AS Option B. Inter-AS (autonomous-systems) support is required when an L3VPN spans multiple ASes, which can be under the same or different administrative authority (such as in an inter-provider scenario). Provider-tunnels (p-tunnels) segmentation occurs at the Autonomous System Border Routers (ASBR). The ASBRs are actively involved in BGP-MVPN signaling as well as data-plane setup.

In addition to creating the Intra-AS p-tunnel segment, these Inter-AS configurations are also used for ASBRs to originate the Inter-AS Auto Discovery (AD) route into Exterior Border Gateway Protocol (eBGP).

Options

ingress-replication	Select the ingress replication tunnel for further configuration. Choose `create-new-ucast-tunnel` to create a new unicast tunnel for ingress replication. Choose `label-switched-path` to create a point-to-point LSP unicast tunnel, and then choose `label-switched-path-template` to use the default template and parameters for dynamic point-to-point LSP.
inter-region-segmented	Select whether Inter-Region Segmented LSPs are triggered by `threshold rate`, or `fan-out`, or both. Supported tunnels are PIM-SSM and PIM-ASM; Inter-region-segmented cannot be set for PIM tunnels. Choose `fan-out` and then specify the number (from 1 to 10,000) of remote Leaf-AD routes to use as a trigger point for segmentation. Choose `threshold` and then specify a data threshold rate (from 0 to 1,000,000 kilobytes per second) to use to use as a trigger point for segmentation.
ldp-p2mp	Select to use LDP point-to-multipoint LSP for flooding; LDP P2MP must be configured in the master routing instance.
rsvp-te	Select to use RSVP-TE point-to-multipoint LSP for flooding. Choose `label-switched-path-template` to use the default template and parameters for dynamic point-to-point LSP.

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 Junos OS Release 19.1R1.

arrow_backward PREVIOUS inter-area-prefix-import

NEXT arrow_forward inter-domain

Junos CLI Reference

ON THIS PAGE

inter-as (Routing Instances)

Syntax

Hierarchy Level

Description

Options

Required Privilege Level

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Junos CLI Reference

ON THIS PAGE

inter-as (Routing Instances)

Syntax

Hierarchy Level

Description

Options

Required Privilege Level

Release Information

Related Documentation

Stay in touch