close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Understanding Layer 2 Networking
- Layer 2 Networking
play_arrow Configuring MAC Addresses
- MAC Addresses
play_arrow Configuring MAC Learning
- MAC Learning
play_arrow Configuring MAC Accounting
- MAC Accounting
play_arrow Configuring MAC Notification
- MAC Notification
play_arrow Configuring MAC Table Aging
- MAC Table Aging
play_arrow Configuring Learning and Forwarding
- Layer 2 Forwarding Tables
play_arrow Configuring Bridging and VLANs
- Bridging and VLANs
play_arrow Configuring 802.1Q VLANs
- 802.1Q VLANs Overview
- 802.1Q VLAN IDs and Ethernet Interface Types
- Configuring Dynamic 802.1Q VLANs
- Enabling VLAN Tagging
- Configuring Tagged Interface with multiple tagged vlans and native vlan
- Sending Untagged Traffic Without VLAN ID to Remote End
- Configuring Tag Protocol IDs (TPIDs) on QFX Series Switches
- Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers
- Configuring an MPLS-Based VLAN CCC with Pop, Push, and Swap and Control Passthrough
- Binding VLAN IDs to Logical Interfaces
- Associating VLAN IDs to VLAN Demux Interfaces
- Configuring VLAN and Extended VLAN Encapsulation
- Configuring a Layer 2 VPN Routing Instance on a VLAN-Bundled Logical Interface
- Example: Configuring a Layer 2 VPN Routing Instance on a VLAN-Bundled Logical Interface
- Specifying the Interface Over Which VPN Traffic Travels to the CE Router
- Configuring Access Mode on a Logical Interface
- Configuring a Logical Interface for Trunk Mode
- Configuring the VLAN ID List for a Trunk Interface
- Configuring a Trunk Interface on a Bridge Network
- Configuring a VLAN-Bundled Logical Interface to Support a Layer 2 VPN Routing Instance
- Configuring a VLAN-Bundled Logical Interface to Support a Layer 2 VPN Routing Instance
- Configuring a Layer 2 Circuit on a VLAN-Bundled Logical Interface
- Example: Configuring a Layer 2 Circuit on a VLAN-Bundled Logical Interface
- Guidelines for Configuring VLAN ID List-Bundled Logical Interfaces That Connect CCCs
- Specifying the Interface to Handle Traffic for a CCC
- Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2 Circuit
play_arrow Configuring Static ARP Table Entries
- Static ARP Table Entries Overview
- Static ARP Entries on Ethernet Interfaces
- Configuring Static ARP Table Entries For Mapping IP Addresses to MAC Addresses
- Example: Configuring Static ARP Entries on Ethernet Interfaces
play_arrow Configuring Restricted and Unrestricted Proxy ARP
- Restricted and Unrestricted Proxy ARP Overview
- Configuring Restricted and Unrestricted Proxy ARP
play_arrow Configuring Gratuitous ARP
- Configuring Gratuitous ARP
play_arrow Adjusting the ARP Aging Timer
- Adjusting the ARP Aging Timer
play_arrow Configuring Tagged VLANs
- Configuring Tagged VLANs
play_arrow Stacking and Rewriting Gigabit Ethernet VLAN Tags
- Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview
- Stacking and Rewriting Gigabit Ethernet VLAN Tags
- Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames
- Configuring Tag Protocol IDs (TPIDs) on PTX Series Packet Transport Routers
- Configuring Stacked VLAN Tagging
- Configuring Dual VLAN Tags
- Configuring Inner and Outer TPIDs and VLAN IDs
- Stacking a VLAN Tag
- Stacking Two VLAN Tags
- Removing a VLAN Tag
- Removing the Outer and Inner VLAN Tags
- Removing the Outer VLAN Tag and Rewriting the Inner VLAN Tag
- Rewriting the VLAN Tag on Tagged Frames
- Rewriting a VLAN Tag on Untagged Frames
- Rewriting a VLAN Tag and Adding a New Tag
- Rewriting the Inner and Outer VLAN Tags
- Examples: Stacking and Rewriting Gigabit Ethernet IQ VLAN Tags
- Understanding Transparent Tag Operations and IEEE 802.1p Inheritance
- Understanding swap-by-poppush
- Configuring IEEE 802.1p Inheritance push and swap from the Transparent Tag
play_arrow Configuring Private VLANs
- Private VLANs
- Understanding Private VLANs
- Bridge Domains Setup in PVLANs on MX Series Routers
- Bridging Functions With PVLANs
- Flow of Frames on PVLAN Ports Overview
- Guidelines for Configuring PVLANs on MX Series Routers
- Configuring PVLANs on MX Series Routers in Enhanced LAN Mode
- Example: Configuring PVLANs with Secondary VLAN Trunk Ports and Promiscuous Access Ports on a QFX Series Switch
- IRB Interfaces in Private VLANs on MX Series Routers
- Guidelines for Configuring IRB Interfaces in PVLANs on MX Series Routers
- Forwarding of Packets Using IRB Interfaces in PVLANs
- Configuring IRB Interfaces in PVLAN Bridge Domains on MX Series Routers in Enhanced LAN Mode
- Example: Configuring an IRB Interface in a Private VLAN on a Single MX Series Router
play_arrow Configuring Layer 2 Bridging Interfaces
- Layer 2 Bridging Interfaces Overview
- Configuring Layer 2 Bridging Interfaces
- Example: Configuring the MAC Address of an IRB Interface
play_arrow Configuring Layer 2 Virtual Switch Instances
- Layer 2 Virtual Switch Instances
play_arrow Configuring Link Layer Discovery Protocol
- LLDP Overview
- Configuring LLDP
- Example: Configuring LLDP
- Configuring the Transmission of Maximum VLAN Name TLVs in LLDP
- LLDP Operational Mode Commands
- Tracing LLDP Operations
play_arrow Configuring Layer 2 Protocol Tunneling
- Layer 2 Protocol Tunneling (L2PT)
play_arrow Configuring Virtual Routing Instances
- Virtual Routing Instances
play_arrow Configuring Layer 3 Logical Interfaces
- Layer 3 Logical Interfaces
play_arrow Configuring Routed VLAN Interfaces
- Routed VLAN Interfaces
play_arrow Configuring Integrated Routing and Bridging
- Integrated Routing and Bridging
play_arrow Configuring VLANS and VPLS Routing Instances
- VLANs and VPLS Routing Instances
play_arrow Configuring Multiple VLAN Registration Protocol (MVRP)
- Multiple VLAN Registration Protocol
play_arrow Configuring Ethernet Ring Protection Switching
- Example: Configuring Ethernet Ring Protection Switching on EX Series Switches
- Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches Supporting ELS
play_arrow Configuring Q-in-Q Tunneling and VLAN Translation
- Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation
play_arrow Configuring Redundant Trunk Groups
- Redundant Trunk Groups
- Q-in-Q Support on Redundant Trunk Links Using LAGs with Link Protection
play_arrow Configuring Proxy ARP
- Proxy ARP
play_arrow Configuring Layer 2 Interfaces on Security Devices
- Layer 2 Interfaces on Security Devices
play_arrow Configuring Security Zones and Security Policies on Security Devices
- Security Zones and Security Policies on Security Devices
play_arrow Configuring Ethernet Port Switching Modes on Security Devices
- Ethernet Port Switching Modes on Security Devices
play_arrow Configuring Ethernet Port VLANs in Switching Mode on Security Devices
- Ethernet Port VLANs in Switching Mode on Security Devices
play_arrow Configuring Secure Wire on Security Devices
- Secure Wire on Security Devices
play_arrow Configuring Reflective Relay on Switches
- Reflective Relay on Switches
play_arrow Configuring Edge Virtual Bridging
- Edge Virtual Bridging
play_arrow Troubleshooting Ethernet Switching
- Troubleshooting Ethernet Switching
- Troubleshooting Ethernet Switching on EX Series Switches
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Virtual Routing Instances

date_range 20-Dec-24

arrow_backward

arrow_forward

Understanding Virtual Routing Instances on EX Series Switches

Virtual routing instances allow administrators to divide a Juniper Networks EX Series Ethernet Switch into multiple independent virtual routers, each with its own routing table. Splitting a device into many virtual routing instances isolates traffic traveling across the network without requiring multiple devices to segment the network.

You can use virtual routing instances to isolate customer traffic on your network and to bind customer-specific instances to customer-owned interfaces.

Virtual routing and forwarding (VRF) is often used in conjunction with Layer 3 subinterfaces, allowing traffic on a single physical interface to be differentiated and associated with multiple virtual routers. Each logical Layer 3 subinterface can belong to only one routing instance.

EX Series switches support IPv4 and IPv6 unicast and multicast VRF traffic. See Feature Explorer for details on VRF support by switch per Junos OS release.

Configuring Virtual Routing Instances on EX Series Switches

Use virtual routing and forwarding (VRF) to divide an EX Series switch into multiple virtual routing instances. VRF allows you to isolate traffic traversing the network without using multiple devices to segment your network. VRF is supported on all Layer 3 interfaces.

Before you begin, make sure to set up your VLANs. See Configuring VLANs for EX Series Switches, Configuring VLANs for EX Series Switches with ELS Support (CLI Procedure), or Configuring VLANs for EX Series Switches (J-Web Procedure).

To configure virtual routing instances:

Create a routing instance:
```
[edit routing-instances]user@switch# set routing-instance-name instance-type virtual-router 
```
Note:
EX Series switches only support the virtual-router instance type.

Bind each routing instance to the corresponding physical interfaces:

content_copy zoom_out_map
[edit routing-instances]user@switch# set routing-instance-name interface interface-name.logical-unit-number 

Create the logical interfaces that are bound to the routing instance.
- To create a logical interface with an IPv4 address:
  [edit interfaces]user@switch# set interface-name unit logical-unit-number family inet address ip-address
- To create a logical interface with an IPv6 address:
  [edit interfaces]user@switch# set interface-name unit logical-unit-number family inet6 address ipv6–address
Note:
Do not create a logical interface using the family ethernet-switching option in this step. Binding an interface using the family ethernet-switching option to a routing instance can cause the interface to shutdown.
Enable VLAN tagging on each physical interface that was bound to the routing instance:
```
 [edit interfaces]user@switch# set interface-name vlan-tagging   
```

Example: Using Virtual Routing Instances to Route Among VLANs on EX Series Switches

Virtual routing instances allow each EX Series switch to have multiple routing tables on a device. With virtual routing instances, you can segment your network to isolate traffic without setting up additional devices.

This example describes how to create virtual routing instances:

Requirements
Overview and Topology
Configuration
Verification

Requirements

This example uses the following hardware and software components:

One EX Series switch
Junos OS Release 9.2 or later for EX Series switches

Before you create the virtual routing instances, make sure you have:

Configured the necessary VLANs. See Configuring VLANs for EX Series Switches, Configuring VLANs for EX Series Switches with ELS Support (CLI Procedure), or Configuring VLANs for EX Series Switches (J-Web Procedure).

Overview and Topology

In a large office, you may need multiple VLANs to properly manage your traffic. This configuration example shows a simple topology wherein a LAN is segmented into two VLANs, each of which is associated with an interface and a virtual routing instance, on the EX Series switch. This example also shows how to use policy statements to import routes from one of the virtual routing instances to the other.

CLI Quick Configuration

To quickly create and configure virtual routing instances, copy the following commands and paste them into the switch terminal window:

content_copy zoom_out_map
[edit]
 set interfaces ge-0/0/3 vlan-tagging 
 set interfaces ge-0/0/3 unit 0 vlan-id 1030 family inet address 10.1.1.1/24 
 set interfaces ge-0/0/3 unit 1 vlan-id 1031 family inet address 10.1.1.1/24 
set interfaces ge-0/0/1 unit 0 family inet address 10.11.1.1/24
set interfaces ge-0/0/2 unit 0 family inet address 10.12.1.1/24
set routing-instances r1 instance-type virtual-router
set routing-instances r1 interface ge-0/0/1.0
set routing-instances r1 interface ge-0/0/3.0
set routing-instances r1 routing-options instance-import import-from-r2
set routing-instances r2 instance-type virtual-router
set routing-instances r2 interface ge-0/0/2.0
set routing-instances r2 interface ge-0/0/3.1
set routing-instances r2 routing-options instance-import import-from-r1
set policy-options policy-statement import-from-r1 term 1 from instance r1 
set policy-options policy-statement import-from-r1 term 1 then accept
set policy-options policy-statement import-from-r2 term 1 from instance r2
set policy-options policy-statement import-from-r2 term 1 then accept 

Procedure

Step-by-Step Procedure
Results

Step-by-Step Procedure

To configure virtual routing instances:

Create a VLAN-tagged interface:

content_copy zoom_out_map
 [edit]user@switch# set interfaces ge-0/0/3 vlan-tagging 

Create one or more subinterfaces on the interfaces to be included in each routing instance:

content_copy zoom_out_map
 [edit]user@switch# set interfaces ge-0/0/3 unit 0 vlan-id 1030 family inet address 10.1.1.1/24 
user@switch# set interfaces ge-0/0/3 unit 1 vlan-id 1031 family inet address 10.1.1.1/24 
user@switch# set interfaces ge-0/0/1 unit 0 family inet address 10.11.1.1/24
user@switch# set interfaces ge-0/0/2 unit 0 family inet address 10.12.1.1/24

Create two virtual routing instances:

content_copy zoom_out_map
 [edit]user@switch# set routing-instances r1 instance-type virtual-router
user@switch# set routing-instances r2 instance-type virtual-router

Set the interfaces for the virtual routing instances:

content_copy zoom_out_map
[edit]user@switch# set routing-instances r1 interface ge-0/0/1.0
user@switch# set routing-instances r1 interface ge-0/0/3.0
user@switch# set routing-instances r2 interface ge-0/0/2.0
user@switch# set routing-instances r2 interface ge-0/0/3.1

Apply a policy to routes being imported into each of the virtual routing instances:

content_copy zoom_out_map
[edit]user@switch# set routing-instances r1 routing-options instance-import import-from-r2
user@switch# set routing-instances r2 routing-options instance-import import-from-r1

Create a policy that imports routes from routing instances r1 to r2 and another policy that imports routes from routing instances r2 to r1:

content_copy zoom_out_map
[edit]user@switch# set policy-options policy-statement import-from-r1 term 1 from instance r1
user@switch# set policy-options policy-statement import-from-r1 term 1 then accept
user@switch# set policy-options policy-statement import-from-r2 term 1 from instance r2
user@switch# set policy-options policy-statement import-from-r2 term 1 then accept

Results

Check the results of the configuration:

content_copy zoom_out_map
user@switch> show configuration 
interfaces {
            ge-0/0/1 {
                unit 0 {
                    family inet {
                        address 10.11.1.1/24;
                    }
                }
            }
            ge-0/0/2 {
                unit 0 {
                    family inet {
                        address 10.12.1.1/24;
                    }
                }
            }
            ge-1/0/3 {
                vlan-tagging;
                unit 0 {
                    vlan-id 1030;
                    family inet {
                        address 10.1.1.1/24;
                    }
                }
                unit 1 {
                    vlan-id 1031;
                    family inet {
                        address 10.1.1.1/24;
                    }
                }
            }
        }
        policy-options {
            policy-statement import-from-r1 {
                term 1 {
                    from instance r1;
                    then accept;
                }
            }
            policy-statement import-from-r2 {
                term 1 {
                    from instance r2;
                    then accept;
                }
            }
        }
        routing-instances {
            r1 {
                instance-type virtual-router;
                interface ge-0/0/1.0;
                interface ge-0/0/3.0;
                routing-options {
                    instance-import import-from-r2;
                }
            }
            r2 {
                instance-type virtual-router;
                interface ge-0/0/2.0;
                interface ge-0/0/3.1;
                routing-options {
                    instance-import import-from-r1;
                }
            }
        }
    }
}

Verification

To confirm that the configuration is working properly, perform these tasks:

Verifying That the Routing Instances Were Created

Purpose
Action
Meaning

Purpose

Verify that the virtual routing instances were properly created on the switch.

Action

Use the show route instance command:

content_copy zoom_out_map
user@switch> show route instance
Instance             Type
         Primary RIB                                     Active/holddown/hidden
master               forwarding
         inet.0                                          6/0/0
         iso.0                                           1/0/0
         inet6.0                                         2/0/0

...

r1                   virtual-router
         r1.inet.0                                       7/0/0

r2                   virtual-router
         r2.inet.0                                       7/0/0

Meaning

Each routing instance created is displayed, along with its type, information about whether it is active or not, and its primary routing table.

Verifying That Virtual Routing Instances Are Working on EX Series Switches

Purpose
Action
Meaning

Purpose

After creating a virtual routing instance, make sure it is set up properly.

Action

Use the show route instance command to list all of the routing instances and their properties:

content_copy zoom_out_map
user@switch> show route instance
Instance             Type
         Primary RIB                                     Active/holddown/hidden
master               forwarding
         inet.0                                          3/0/0

__juniper_private1__ forwarding
         __juniper_private1__.inet.0                     1/0/3

__juniper_private2__ forwarding

instance1            forwarding

r1                   virtual-router
         r1.inet.0                                       1/0/0

r2                   virtual-router
         r2.inet.0                                       1/0/0

Use the show route forwarding-table command to view the forwarding table information for each routing instance:

content_copy zoom_out_map
user@switch> show route forwarding-table
Routing table: r1.inet
Internet:
Destination        Type RtRef Next hop           Type Index NhRef Netif
default            perm     0                    rjct   539     2
0.0.0.0/32         perm     0                    dscd   537     1
10.1.1.0/24       ifdn      0                    rslv   579     1 ge-0/0/3.0
10.1.1.0/32       iddn      0 10.1.1.0           recv   577     1 ge-0/0/3.0
10.1.1.1/32       user      0                    rjct   539     2
10.1.1.1/32       intf      0 10.1.1.1           locl   578     2
10.1.1.1/32       iddn      0 10.1.1.1           locl   578     2
10.1.1.255/32     iddn      0 10.1.1.255         bcst   576     1 ge-0/0/3.0
233.252.0.1/32       perm     0 233.252.0.1          mcst   534     1
255.255.255.255/32 perm     0                    bcst   535     1

Meaning

The output confirms that the virtual routing instances are created and the links are up and displays the routing table information.

arrow_backward PREVIOUS Layer 2 Protocol Tunneling (L2PT)

NEXT arrow_forward Layer 3 Logical Interfaces

Ethernet Switching User Guide

ON THIS PAGE

Virtual Routing Instances

Understanding Virtual Routing Instances on EX Series Switches

Configuring Virtual Routing Instances on EX Series Switches

Example: Using Virtual Routing Instances to Route Among VLANs on EX Series Switches

Requirements

Overview and Topology

Configuration

CLI Quick Configuration

Procedure

Step-by-Step Procedure

Results

Verification

Verifying That the Routing Instances Were Created

Purpose

Action

Meaning

Verifying That Virtual Routing Instances Are Working on EX Series Switches

Purpose

Action

Meaning

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Ethernet Switching User Guide

ON THIS PAGE

Virtual Routing Instances

Understanding Virtual Routing Instances on EX Series Switches

See Also

Configuring Virtual Routing Instances on EX Series Switches

Example: Using Virtual Routing Instances to Route Among VLANs on EX Series Switches

Requirements

Overview and Topology

Configuration

CLI Quick Configuration

Procedure

Step-by-Step Procedure

Results

Verification

Verifying That the Routing Instances Were Created

Purpose

Action

Meaning

Verifying That Virtual Routing Instances Are Working on EX Series Switches

Purpose

Action

Meaning

Stay in touch