routing-instances (Multiple Routing Entities)
Statement introduced before Junos OS Release 7.4.
remote-vtep-v6-list statement introduced in Junos OS Release 17.3 for MX Series routers with MPC and MIC interfaces.
Configure an additional routing entity for a router. You can create multiple instances of BGP, IS-IS, OSPF, OSPFv3, and RIP for a router. You can also create multiple routing instances for separating routing tables, routing policies, and interfaces for individual wholesale subscribers (retailers) in a Layer 3 wholesale network.
Each routing instance consist of the following:
A set of routing tables
A set of interfaces that belong to these routing tables
A set of routing option configurations
Each routing instance has a unique name and a corresponding IP unicast table. For example, if you configure a routing instance with the name my-instance, its corresponding IP unicast table is my-instance.inet.0. All routes for my-instance are installed into my-instance.inet.0.
Routes are installed into the default routing instance inet.0 by default, unless a routing instance is specified.
In Junos OS Release 9.0 and later, you can no longer specify a routing-instance name of primary, default, or bgp or include special characters within the name of a routing instance.
In Junos OS Release 9.6 and later, you can include a slash (/) in a routing-instance name only if a logical system is not configured. That is, you cannot include the slash character in a routing-instance name if a logical system other than the default is explicitly configured. Routing-instance names, further, are restricted from having the form __.*__ (beginning and ending with underscores). The colon : character cannot be used when multitopology routing (MTR) is enabled.
Routing instances are disabled for the router.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.