Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation

Solutions

Featured solutions AI Campus and branch Data center WAN Security Service provider Cloud operator Industries
Campus and Branch

Welcome to the NOW Way to Wi-Fi

Take your networking performance to new heights with a modern, cloud-native, AI-Native architecture. Only Juniper can help you unleash the full potential of Wi-Fi 7 with our AI-Native platform for innovation.
Prepare for liftoff
Business intelligence analyst dashboard on virtual screen. Big data Graphs Charts.

AI Data Center Networking

Juniper’s AI data center solution is a quick way to deploy high performing AI training and inference networks that are the most flexible to design and easiest to manage with limited IT resources.
Find out more
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Zero trust security

Ops4AI Lab

Visit our lab in Sunnyvale, CA and see our AI data center solution for yourself. You can try out your own model’s functionality and performance, too.
Visit the lab
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Higher Education

Shaping Student Experiences: The NOW Way to Build Higher Education Networks

Join Juniper Networks CIO Sharon Mandell and a virtual summit of C-level IT leaders from prestigious institutions as they discuss ongoing efforts to support digital transformation.
Register to attend
Hand on tablet with healthcare overlay of graphics

Security in healthcare

In this IDC Spotlight report, discover how AI networking can automate and strengthen a healthcare ecosystem to defeat criminals and prevent loss. 
Gain insights into ecosystem security
Retail

The Future of In-Store Technologies

Join us for an enlightening webinar with Kevin McCartan, Senior IT Service Delivery Engineer at Musgrave; retail guru Jack Stratten of Insider Trends; and Christian Gilby, Director of Product Marketing at Juniper Networks, as they discuss the future of in-store technologies.
Reserve my spot

Products

Wireless access Wired access SD-WAN / SASE Routing and switching Security Mist AI™ Management software Network operating system Blueprint for AI-Native Acceleration Optics
  • Operations
ACX7020 router

Juniper ACX7020 Cloud Metro Access Router

Legacy networks simply cannot meet the demands of today’s rapidly evolving metro landscape. Unlock a new generation of highly scalable architectures and automated operations with the Juniper ACX7020. 
Learn more
EX4000 Ethernet Switch

Next-gen AI-Native EX4000 line of switches

Lack of AI innovation from your current networking vendor slowing you down? Embrace Juniper’s cloud-native, AI-Native access switches that support every level and layer, across nearly every deployment.
Discover how
The Q and AI text with an image of Bob Friday and Kedar Dhuru.

The Q&AI Podcast

Delivering practical solutions and enriching discussions, this podcast series is a vital resource for those seeking an in-depth exploration of AI's transformative potential.
Catch the latest episode

Services

Services
Services AI Care

Juniper AI Care Services Revolutionize Your Service Experience

Our industry-first AI-Native services couple AIOps with our deep expertise across the full network life cycle. You can move from reactive response to proactive insight and action.
Explore AI Care Services
Services AI Data Center

Juniper AI Data Center Deployment Services Optimize Your AI Model Runs

We use our expertise and validated designs to help design, deploy, validate and tune networks, including GPUs and storage, to get the most from your AI infrastructure operation.
Learn about AI Data Center Deployment Services

Partners

Partners

Support and Documentation

Support and Documentation

Learn

About Juniper Training Events The Feed Resources Technology learning topics Thought leadership and insights
Audience raising hands up while businessman is speaking in training at the office.

Juniper certification and training news

See the latest
Ringing of the bell

All global events

See the latest
AI-native-now

AI-Native NOW event series

Register now
Juniper's Christina Hendrix at the head of a conference table. With the text "The NOW Way to Network" overlayed, with "NOW" emphasizing the "O" in green color.

The NOW Way to Network

Watch the video series
AI Native Now

Executive insights

Dive deep with leading experts and thought leaders on all the topics that matter most to your business, from AI to network security to driving rapid, relevant transformation for your business.
Learn more
A keynote speaker giving a presentation at a conference. There are dozens of people sitting around them. The presentation is displayed via projector on all the walls in the room.

Leadership voices

Juniper Networks’ leaders operate on the front lines of creating the network of the future. Take a look around to see what’s on their minds.
Watch now
Bob Friday and Jessica Garrison speaking

Bob Friday Talks

Join Bob as he ventures into all the knowns -- and -- unknowns -- of AI.
Catch the latest episode
Documentation
Menu
License Guide
Quick Starts
Validated Designs
Explore Pathfinder Apps
CLI Explorer
Feature Explorer
Hardware Compatibility Tool
Port Checker
Browse All
Collapse

Pathfinder Apps

All

By Software

By Hardware

Learn More
Pathfinder HomeCLI ExplorerCompliance AdvisorFeature ExplorerHardware Compatibility ToolJunos XML API ExplorerJunos YANG Data Model ExplorerPort CheckerPower CalculatorSNMP MIB ExplorerSystem Log Explorer
CLI ExplorerFeature ExplorerJunos XML API ExplorerJunos YANG Data Model ExplorerSNMP MIB ExplorerSystem Log Explorer
Compliance AdvisorFeature ExplorerHardware Compatibility ToolPort CheckerPower Calculator
Home Documentation Junos OS Ethernet Switching User Guide Configuring Ethernet Ring Protection Switching

Ethernet Switching User Guide

keyboard_arrow_up
close
keyboard_arrow_left
Ethernet Switching User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
ON THIS PAGE
keyboard_arrow_right

Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches Supporting ELS

date_range 20-Dec-24
arrow_backward
arrow_forward

You can configure Ethernet ring protection switching (ERPS) on connected EX Series or QFX Series switches to prevent fatal loops from disrupting a network. ERPS is similar to the Spanning Tree Protocol, but ERPS is more efficient because it is customized for ring topologies. You must connect and configure at least three switches to form a ring.

This example shows how to configure Ethernet ring protection switching on four switches with ELS support, connected to one another on a dedicated link in a ring topology. You can include different types of switches in an ERPS ring, including those with and without ELS support. If any of your EX Series switches runs software that does not support ELS, use these configuration directions: Example: Configuring Ethernet Ring Protection Switching on EX Series Switches. For ELS details, see Using the Enhanced Layer 2 Software CLI.

Requirements

This example uses the following hardware and software components:

  • Four connected EX Series switches or QFX Series switches that support the Enhanced Layer 2 Software (ELS) to function as nodes in the ring topology. You could use any of these QFX Series switches: QFX5100, QFX5200, and QFX10000. This configuration also applies to EX Series switches that support the Enhanced Layer 2 Software (ELS) configuration style that runs on EX4300, EX4600, EX2300, and EX3400 switches.

  • Junos OS Release 13.2X50-D10 or later for EX Series switches.

  • Junos OS Release 14.1X53-D10 or later for QFX5100 switches. Junos OS Release 15.1X53-D30 or later for QFX5200, and QFX10000 switches.

Before you begin, be sure you have:

  • Configured two trunk interfaces on each of the four switches. See Table 1 for a list of the interface names used in this example.

  • Configured a VLAN (with name erp-control-vlan-1 and ID 100) on all four switches and associated two network interfaces from each of the four switches with the VLAN. See Configuring VLANs for the QFX Series OR Configuring VLANs for EX Series Switches with ELS Support (CLI Procedure). See Table 1 for a list of the interface names used in this example.

  • Configured two more VLANs (one with name erp-data-1 and vlan ID 101 and a second vlan with the name erp-data-2 and vlan ID 102) on all four switches and associated both the east and west interfaces on each switch.

Overview and Topology

ERPS uses a dedicated physical link, including a control VLAN for trunk ports, between all of the switches to protect the active links. ERPS VLANs are all located on this link and are also blocked by default. When traffic between the switches is flowing with no problems, the active links take care of all traffic. Only if an error occurs on one of the data links would the ERPS control channel take over and start forwarding traffic.

Note:

Trunk ports on switches use a VLAN to create individual control channels for ERPS. When multiple ERPS instances are configured for a ring, there are multiple sets of ring protection links (RPLs) and RPL owners on the ERPS link, and a different channel is blocked for each instance. Nontrunk ports use the physical link as the control channel and protocol data units (PDUs) are untagged, with no VLAN information in the packet.

This example creates one protection ring (called a node ring) named erp1 on four switches connected in a ring by trunk ports as shown in Figure 1. Because the links are trunk ports, VLAN 100 is used for erp1 traffic. The east interface of each switch is connected with the west interface of an adjacent switch. Cobia is the RPL owner, with interface ge-0/0/0 configured as an RPL end interface. The interface ge-0/0/0 of Jas5-esc is configured as the RPL neighbor interface. In the idle state, the RPL end blocks the control VLAN and data channel VLAN for this particular ERP instance—the blocked port on Cobia is marked with a star in Figure 1.

Figure 1: Ethernet Ring Protection Switching ExampleEthernet Ring Protection Switching Example

In this example, we configure the four switches with the interfaces indicated in both Figure 1 and Table 1.

Table 1: Components to Configure for This Example

Interfaces

Cobia

Jas5-esc

Jas6-esc

Hairtail

East

ge-0/0/0

ge-0/0/10

ge-0/0/30

ge-0/0/20

West

ge-0/0/20

ge-0/0/0

ge-0/0/20

ge-0/0/10

Third

ge-0/0/10

ge-0/0/20

ge-0/0/0

ge-0/0/0

Configuration

Configuring ERPS on Cobia, the RPL Owner Node

CLI Quick Configuration

To quickly configure Cobia, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

ERPS cannot be configured on an interface if any spanning-tree protocol is configured. (RSTP is configured by default.) Therefore, in this example, RSTP is disabled on each ring port before configuring ERPS. Spanning-tree protocols are disabled two different ways, depending on which version of the Junos OS you are running. Therefore, the first two statements in this example vary: Junos release 15.1 or later uses one command to turn off RSTP and Junos releases prior to 15.1 uses another command.

content_copy zoom_out_map
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/0 disable
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/20 disable
Junos OS release prior to 15.1: delete rstp interface ge-0/0/0
Junos OS release prior to 15.1: delete rstp interface ge-0/0/20
set protocols protection-group ethernet-ring erp1
set protocols protection-group ethernet-ring erp1 ring-protection-link-owner 
set protocols protection-group ethernet-ring erp1 data-channel 101 
set protocols protection-group ethernet-ring erp1 data-channel 102 
set protocols protection-group ethernet-ring erp1 control-vlan 100 
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/0.0 
set protocols protection-group ethernet-ring erp1 east-interface ring-protection-link-end 
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/20.0 
set protocols protection-group ethernet-ring erp1 west-interface control-channel vlan 100 
set protocols protection-group ethernet-ring erp1 east-interface control-channel vlan 100

Step-by-Step Procedure

To configure ERPS on Cobia:

  1. Disable any spanning-tree protocol currently configured on the ERPS interfaces. RSTP, VSTP, and MSTP are all available spanning-tree protocols. RSTP is enabled in the default configuration, so this example shows disabling RSTP. Spanning-tree protocols are disabled two different ways, depending on which version of the Junos OS you are running.

    If you are running Junos release 15.1 or later, disable any spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set rstp interface ge-0/0/0 disable
user@switch# set  rstp interface ge-0/0/20 disable

    If you are running a Junos release prior to 15.1, disable any spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# delete rstp interface ge-0/0/0
user@switch# delete rstp interface ge-0/0/20

  2. Create a node ring named erp1:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set protection-group ethernet-ring erp1

  3. Designate Cobia as the RPL owner node:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set ring-protection-link-owner

  4. Configure the VLANs 101 and 102 as data channels:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set data-channel 101
user@switch# set data-channel 102

  5. Configure the control vlan 100 for this ERPS instance on the trunk interface:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set control-vlan 100

  6. Configure the east interface of the node ring erp1 with control channel ge-0/0/0.0 and indicate that this particular ring protection link ends here:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set east-interface control-channel ge-0/0/0.0 
user@switch#  set east-interface ring-protection-link-end

  7. Configure the west interface of the node ring erp1 with control channel ge-0/0/20.0 :

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel ge-0/0/20.0

  8. Every ring instance on a trunk port has one control VLAN in which ERP packets traverse. The control VLAN also controls data VLANs, if any are configured. Assign 100 as the control VLAN on both interfaces:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel vlan 100 
user@switch#  set east-interface control-channel

Configuring ERPS on Jas5-esc

CLI Quick Configuration

To quickly configure Jas5-esc, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

ERPS cannot be configured on an interface if any spanning tree protocol is configured. (RSTP is configured by default.) Therefore, in this example, RSTP is disabled on each ring port before configuring ERPS. Spanning tree is disabled two different ways, depending on which version of the Junos OS you are running. Therefore, the first two statements will vary: Junos release 15.1 or later uses one command to turn off RSTP and Junos releases prior to 15.1 uses another command.

content_copy zoom_out_map
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/10 disable
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/0 disable
Junos OS release prior to 15.1: delete rstp interface ge-0/0/10
Junos OS release prior to 15.1: delete rstp interface ge-0/0/0
set protocols protection-group ethernet-ring erp1 
set protocols protection-group ethernet-ring erp1 data-channel 101 
set protocols protection-group ethernet-ring erp1 data-channel 102 
set protocols protection-group ethernet-ring erp1 control-vlan 100
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/10.0
set protocols protection-group ethernet-ring erp1 east-interface control-channel vlan 100 ge-0/0/0.0
set protocols protection-group ethernet-ring erp1 west-interface control-channel ge-0/0/20.0 
set protocols protection-group ethernet-ring erp1 west-interface control-channel vlan 100 
set protocols protection-group ethernet-ring erp1 west-interface control-channel vlan 100

Step-by-Step Procedure

To configure ERPS on Jas5-esc:

  1. Disable any spanning-tree protocol currently configured on the ERPS interfaces. RSTP, VSTP, and MSTP are all available spanning-tree protocols. RSTP is enabled in the default configuration, so this example shows disabling RSTP. Spanning-tree protocols are disabled two different ways, depending on which version of the Junos OS you are running.

    If you are running Junos release 15.1 or later, disable any spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set rstp interface ge-0/0/10 disable
user@switch# set rstp interface ge-0/0/0 disable

    If you are running a Junos release prior to 15.1, disable any version of spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# delete rstp interface ge-0/0/10 
user@switch# delete rstp interface ge-0/0/0

  2. Create a node ring named erp1:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set protection-group ethernet-ring erp1

  3. Configure two data channels named erp-data-1 and erp-data-2 to define a set of VLAN IDs that belong to a ring instance.

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set data-channel vlan 101
user@switch# set data-channel vlan 102

  4. Configure a control VLAN with ID 100 for the node ring erp1:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set control-vlan 100

  5. Configure the east interface of the node ring erp1 with the control channel ge-0/0/10.0:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set east-interface control-channel ge-0/0/10.0

  6. Configure the west interface of the node ring erp1 with the control channel ge-0/0/0.0 vlan 100:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel ge-0/0/0.0

  7. Every ring instance on a trunk port has one control VLAN in which ERP packets traverse. The control VLAN also controls data VLANs, if any are configured. Assign vlan # 100 as the control VLAN:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel vlan 100
user@switch#  set east-interface control-channel vlan 100

Configuring ERPS on Hairtail

CLI Quick Configuration

To quickly configure Hairtail, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

ERPS cannot be configured on an interface if any spanning tree protocol is configured. (RSTP is configured by default.) Therefore, in this example, RSTP is disabled on each ring port before configuring ERPS. Spanning tree is disabled two different ways, depending on which version of the Junos OS you are running. Therefore, the first two statements will vary: Junos release 15.1 or later uses one command to turn off RSTP and Junos releases prior to 15.1 uses another command.

content_copy zoom_out_map
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/10 disable
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/20 disable
Junos OS release prior to 15.1: delete rstp interface ge-0/0/10
Junos OS release prior to 15.1: delete rstp interface ge-0/0/20
set protocols protection-group ethernet-ring erp1 
set protocols protection-group ethernet-ring erp1 data-channel 101 
set protocols protection-group ethernet-ring erp1 data-channel 102 
set protocols protection-group ethernet-ring erp1 control-vlan 100 
Set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/0.0 
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/20.0 
set protocols protection-group ethernet-ring erp1 west-interface control-channel vlan 100 
set protocols protection-group ethernet-ring erp1 east-interface control-channel vlan 100

Step-by-Step Procedure

To configure ERPS on Hairtail:

  1. Disable any spanning-tree protocol currently configured on the ERPS interfaces. RSTP, VSTP, and MSTP are all available spanning-tree protocols. RSTP is enabled in the default configuration, so this example shows disabling RSTP. Spanning-tree protocols are disabled two different ways, depending on which version of the Junos OS you are running.

    If you are running Junos release 15.1 or later, disable any spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set rstp interface ge-0/0/10 disable
user@switch# set rstp interface ge-0/0/20 disable

    If you are running a Junos release prior to 15.1, disable any spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# delete rstp interface ge-0/0/10 
user@switch# delete rstp interface ge-0/0/20

  2. Create a node ring named erp1:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set protection-group ethernet-ring erp1

  3. Configure the control vlan 100 for the node ring erp1:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set control-vlan 100

  4. Configure two data channels numbered 101 and 102 to define a set of VLAN IDs that belong to a ring instance:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set data-channel vlan 101
user@switch# set data-channel vlan 102

  5. Configure the east interface of the node ring erp1 with the control channel ge-0/0/20.0:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set east-interface control-channel ge-0/0/20.0

  6. Configure the west interface of the node ring erp1 with the control channel ge-0/0/10.0:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel ge-0/0/10.0

  7. Every ring instance on a trunk port has one control VLAN in which ERP packets traverse. The control VLAN also controls data VLANs, if any are configured. Assign 100 as the control VLAN:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel vlan 100
user@switch#  set east-interface control-channel vlan 100

Configuring ERPS on Jas6-esc

CLI Quick Configuration

To quickly configure Jas6-esc, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

ERPS cannot be configured on an interface if any spanning tree protocol is configured. (RSTP is configured by default.) Therefore, in this example, RSTP is disabled on each ring port before configuring ERPS. Spanning tree is disabled two different ways, depending on which version of the Junos OS you are running. Therefore, the first two statements will vary: Junos release 15.1 or later uses one command to turn off RSTP and Junos releases prior to 15.1 uses another command.

content_copy zoom_out_map
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/30 disable
Junos OS release 15.1 or later: set protocols rstp interface ge-0/0/20 disable
Junos OS release prior to 15.1: delete rstp interface ge-0/0/30
Junos OS release prior to 15.1: delete rstp interface ge-0/0/20
set protocols protection-group ethernet-ring erp1
set protocols protection-group ethernet-ring erp1 data-channel 101
set protocols protection-group ethernet-ring erp1 data-channel 102
set protocols protection-group ethernet-ring erp1 control-vlan 100
set protocols protection-group ethernet-ring erp1 east-interface control-channel ge-0/0/30.0
set protocols protection-group ethernet-ring erp1 west-interface control-channel ge-0/0/20.0 
set protocols protection-group ethernet-ring erp1 west-interface control-channel vlan 100
set protocols protection-group ethernet-ring erp1 east-interface control-channel vlan 100

Step-by-Step Procedure

To configure ERPS on Jas6-esc:

  1. Disable any spanning-tree protocol currently configured on the ERPS interfaces. RSTP, VSTP, and MSTP are all available spanning-tree protocols. RSTP is enabled in the default configuration, so this example shows disabling RSTP. Spanning-tree protocols are disabled two different ways, depending on which version of the Junos OS you are running.

    If you are running Junos release 15.1 or later, disable any spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set rstp interface ge-0/0/30 disable
user@switch# set rstp interface ge-0/0/20 disable

    If you are running a Junos release prior to 15.1, disable any spanning-tree protocol with these commands. To disable RSTP:

    content_copy zoom_out_map
    [edit protocols]
user@switch# delete rstp interface ge-0/0/30 
user@switch# delete rstp interface ge-0/0/20

  2. Create a node ring named erp1:

    content_copy zoom_out_map
    [edit protocols]
user@switch# set protection-group ethernet-ring erp1

  3. Configure the control vlan 100 for the node ring erp1:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set control-vlan 100

  4. Configure two data channels numbered 101 and 102 to define VLAN IDs that belong to a ring instance.

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch# set data-channel 101
user@switch# set data-channel 102

  5. Configure the east interface of the node ring erp1 with the control channel ge-0/0/30.0 :

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set east-interface control-channel ge-0/0/30.0

  6. Configure the west interface of the node ring erp1 with the control channel ge-0/0/20.0:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel ge-0/0/20.0

  7. Every ring instance on a trunk port has one control VLAN in which ERP packets traverse. The control VLAN also controls data VLANs, if any are configured. Assign vlan number 100 as the control VLAN:

    content_copy zoom_out_map
    [edit protocols protection-group ethernet-ring erp1]
user@switch#  set west-interface control-channel vlan 100
user@switch#  set east-interface control-channel vlan 100

Related Documentation

arrow_backward PREVIOUS Example: Configuring Ethernet Ring Protection Switching on EX Series Switches
NEXT arrow_forward Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation
footer-navigation

© 1999 - 2025 Juniper Networks, Inc. All rights reserved.

Scroll to top