inter-as (Routing Instances)
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
[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.
|
| inter-region-segmented | Select whether Inter-Region Segmented LSPs are triggered by
|
| 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.
|
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.