Configure an Instance Type

There are four types of routing instances that you configure at the [edit routing-instances routing-instance-name instance-type] hierarchy level:

• Forwarding—Use this routing instance type for filter-based forwarding applications. For this instance type, there is no one-to-one mapping between an interface and a routing instance. All interfaces belong to the default instance inet.0.
• Layer 2 VPN—Use this routing instance type for Layer 2 VPN implementations.
• Nonforwarding—Use this routing instance type when a separation of routing table information is required. There is no corresponding forwarding table. All routes are installed into the default forwarding table. IS-IS instances are strictly nonforwarding instance types.
• Virtual router—Similar to a VPN routing and forwarding instance type, but used for non-VPN-related applications. There are no VRF import, VRF export, VRF target, or route distinguisher requirements for this instance type.
• VPLS—Virtual private local-area network (LAN) service. Use this routing instance type for point-to-multipoint LAN implementations between a set of sites in a VPN.
• VRF—VPN routing and forwarding. Use this routing instance type for Layer 3 VPN implementations. For this instance type, there is a one-to-one mapping between an interface and a routing instance. Each VRF instance corresponds with a forwarding table. Routes on an interface go into the corresponding forwarding table.

To configure a routing instance type, include the instance-type statement at the [edit routing-instances] hierarchy level:

[edit]

routing-instances {

    routing-instance-name {

        interface interface-name ;

        instance-type (forwarding | l2vpn | no-forwarding | virtual-router | vpls | vrf);

    }

}

For more detailed information about configuring Layer 2 VPNs, Layer 3 VPNs, and VPLS, see JUNOS Internet Software Configuration Guide: VPNs.