[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring an Instance Type

You can configure eight routing instance types at the [edit routing-instances routing-instance-name instance-type] and [edit logical-systems logical-system-name routing-instances routing-instance-name instance-type] hierarchy levels:

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.
Layer2-control—Use this routing instance type for RSTP or MSTP in customer edge interfaces of a VPLS routing instance. This instance type cannot be used if the customer edge interface is multihomed to two provider edge interfaces. If the customer edge interface is multihomed to two provider edge interfaces, use the default BPDU tunneling. For more information about configure a layer2–control instance type, see the JUNOS MX-series Layer 2 Configuration Guide.
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—This routing instance is 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.
Virtual switch—(MX-series routers only) Use the virtual switch instance type to group one or more Layer 2 bridge domains. A bridge domain consists of a set of ports that share the same flooding or broadcast characteristics. Each virtual switch represents a Layer 2 network. You can optionally configure a virtual switch to support Integrating Routing and Bridging (IRB), which facilitates simultaneous Layer 2 bridging and Layer 3 IP routing on the same interface. You can also configure Layer 2 control protocols to provide loop resolution. Protocols supported include the Spanning Tree Protocol, the Rapid Spanning Tree Protocol, and the Multiple Spanning Tree Protocol. For more information about configuring a virtual switch instance type, see the JUNOS MX-series Layer 2 Configuration Guide.
VPLS—Use this routing instance type for point-to-multipoint LAN implementations between a set of sites in a VPN.
VRF—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:




routing-instances {



routing-instance-name {

interface interface-name;

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


}

You can include the statement at the following hierarchy levels:

[edit routing-instances routing-instance-name]
[edit logical-systems logical-system-name routing-instances routing-instance-name]

For more information about configuring Layer 2 VPNs, Layer 3 VPNs, and VPLS, see the JUNOS VPNs Configuration Guide.

For more information about configuring the types of routing instances, see the following sections:

[Contents] [Prev] [Next] [Index] [Report an Error]