import (MPLS Traffic Engineering Database)
Syntax
import {
bgp-ls-identifier domain-identifier;
identifier identifier;
ipv6;
l3-unicast-topology {
bgp-link-state;
}
policy policy-name;
igp-topology{
bgp-link-state;
}
Hierarchy Level
[edit logical-systems logical-system-name protocols mpls traffic-engineering database], [edit protocols mpls traffic-engineering database]
Description
Configure the traffic engineering database import parameters.
Options
bgp-ls-identifier domain-identifier |
BGP-TE domain identifier. |
| identifier identifier |
BGP-TE identifier.
|
ipv6 |
Enable import of IPv6 addresses into the traffic engineering database (TED). |
l3-unicast-topology |
Download L3-Unicast topology into RIB. |
policy policy-name |
Name of the import policy. |
igp-topology |
Download IGP topology information into the traffic engineering database (TED). In Junos OS, the IGPs install topology information into a database called the traffic engineering database. The traffic engineering database contains the aggregated topology information. The IGP routes are installed by the traffic engineering database on behalf of the corresponding IGP into a user-visible routing table called lsdist.0, subject to route policies. |
bgp-link-state |
Export IGP topology information into BGP-Link State (BGP-LS) from the lsdist.0 routing table. The lsdist.0 routing table stores the network topology information from the traffic engineering database. The BGP-LS reads IGP entries from lsdist.0 and advertises the information to BGP peers. |
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 14.2.
ipv6 option introduced in Junos OS Release 20.4R1.