CTR 8500-8300 3.0 ERPS Config July2015 260-668256-003

CTR 8300/8500 CONFIGURATION
ERPS
Version 3.0
260-668256-003
Copyright & Terms of Use
July 2015
This documentation incorporates features and functions provided with CTR 8540 and CTR 8300 for software
release 3.0
Copyright © 2015 by Aviat Networks, Inc.
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a
retrieval system, or translated into any language or computer language, in any form or by any means, elec-
tronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Aviat Net-
works Inc. To request permission, contact techpubs@aviatnet.com.
Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof and specifically dis-
claims any implied warranties or merchantability or fitness for any particular purpose. Further, Aviat Net-
works reserves the right to revise this publication and to make changes from time to time in the content
hereof without obligation of Aviat Networks to notify any person of such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons and/or damage to the
equipment:
1. Installation and Service Personnel: Installation and service must be carried out by authorized personnel who
have the technical training and experience necessary to be aware of any hazardous operations during install-
ation and service, and of measures to avoid any danger to themselves, to any other personnel, and to the equip-
ment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety sections of this guide.
Local safety regulations must be used if mandatory. Safety instructions in this guide should be used in addi-
tion to the local safety regulations. In the case of conflict between safety instructions stated in this guide and
those indicated in local regulations, mandatory local norms will prevail. Should local regulations not be man-
datory, then the safety norms in this guide will prevail.
4. Service Personnel Skill: Service personnel must have received adequate technical training on tele-
communications and in particular on the equipment this guide refers to.
Trademarks
All trademarks are the property of their respective owners.
End User License Agreement and Open Source
By using this product you agree to the terms of the CTR 8540 End User License Agreement; to view this, log
into a CTR 8540 or CTR 8300 using the CLI command window and enter the CLI command “show EULA”.
The CTR 8540 and CTR 8300 use free and open source software components, which can be viewed by using
the CLI command “show system acknowledgments”. This command also details the licenses associated with
each component and describes the methods available to acquire the open source software.
260-668256-003 JULY 2015 I

ERPS CONFIGURATION FOR CTR 8300 AND 8500
Aviat Networks Technical & Sales

Support
Technical Service and Support
For customer service and technical support, contact one of the regional Technical Help Desks listed below, or
for 24/7 (all day, every day of the year) there is the Global Technical Help Desk (GTHD). A call will be answered
by GTHD support staff who will resolve the issue, if possible, or quickly pass the call to the appropriate TAC
engineer for resolution. Contact information is available below or on the Aviat Networks web site.
Global Technical Help Desk
The GTHD number is: +1-210-526-6345, or toll free 1-800-227-8332 within USA
For 24/7 access you will need your Support Assurance PIN. Without a PIN you will still receive support, but the
support process will require an additional screening step. After-hours calls to Paris are routed to the GTHD,
with the existing number left in place during business hours.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help Desk
Aviat Networks Aviat Networks Aviat Networks
5200 Great America Parkway 4 Bell Drive Bldg 10, Units A&B
Santa Clara CA 95054 Hamilton International Technology Philexcel Industrial Park
U.S.A. Park M. Roxas Hi-way
Blantyre, Glasgow, Scotland Clark Freeport Zone
G72 0FB Philippines 2023
United Kingdom
Toll Free (Canada/USA): 800 227 Phone: Phone: +63 45 599 5192
8332 Hamilton: +44 (0) 1698 717 230 Fax: +63 45 599 5196
Phone: 210 561 7400 Paris: +33 (0) 1 77 31 00 33
Fax: 210 561 7399 Fax: +44 (0) 1698 717 204
Cus- Cus- CustomerCare.Asia@aviatnet.com
tomerCare.Americas@aviatnet.com tomerCare.EMEA@aviatnet.com
Sales and Sales Support

Contact one of the Aviat Networks headquarters, or find your regional sales office on the Aviat Networks web
site.
Corporate Headquarters, California, USA International Headquarters , Singapore
Aviat Networks, Inc. Aviat Networks(S) Pte. Ltd.
5200 Great America Parkway 17, Changi Business Park Central 1
Santa Clara CA 95054 Honeywell Building, #04-01
U.S.A. Singapore 486073
Phone: + 408 567 7000 Phone: +65 6496 0900
Fax: + 408 567 7001 Fax: + 65 6496 0999
Sales Inquiries: +1-321-674-4252
II AVIAT NETWORKS
Product Compliance Notes

CTR 8540, CTR 8312, and CTR 8311 have been tested for and meet EMC Directive 2004/108/EC. The equipment
was tested using screened cable; if any other type of cable is used, it may violate compliance.
CTR 8540, CTR 8312, and CTR 8311 are Class A products. In a domestic environment these products may
cause radio interference in which case the user may be required to take adequate measures. This equipment
is intended to be used exclusively in telecommunications centers.
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of IRU 6 0 0 i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 or ODU 3 0 0 h p on ANSI f r eq u en c y b an d s
i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 on th e l i c en s e- f r ee 5 . 8 GHz b an d i s n ot
s u p p or ted .
International Use of 5.8GHz

ODU 600 or IRU 600 with CTR 8540, CTR 8312, or CTR 8311 on the 5.8 GHz license-free band do not employ
DFS, and as such the equipment cannot be deployed within Europe or any country where DFS is a regulatory
requirement for protection of radars.
WEEE Directive
In accordance with the WEEE Directive (2002/96/EC), CTR 8540, CTR 8312, and CTR 8311 are marked with the
following symbol:
This symbol indicates that this equipment should be collected separately for the purposes of recovery and/or
recycling.
For information about collection and recycling of Aviat Networks equipment please contact your local Aviat
Networks sales office. If you purchased your product via a distributor please contact the distributor for inform-
ation regarding collection and recovery/recycling.
More information on the WEEE Directive is available at our website:
http://www.aviatnetworks.com/products/compliance/weee/.
(WEEE is the acronym for Waste Electrical and Electronic Equipment)
RoHS Directive
CTR 8540, CTR 8312, and CTR 8311 meet the requirements of ROHS directive 2011/65/EU.
260-668256-003 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

The reference to CTR in this declaration denotes intended use of the CTR 8540, CTR 8312, or CTR 8311, with
one or more of the following Aviat Networks ODUs: ODU 600, ODU 600sp, ODU 300hp.
IV AVIAT NETWORKS
The CTR 8540, CTR 8312, or CTR 8311 with an ODU 600, ODU 600sp, or ODU 300hp radio is classified under the
R&TTE Directive 99/5/EC as a class 2.8 radio (microwave fixed link) product.
Point-to-point radio relay equipment is intended to be used for:
- Interconnecting private and public networks.
- Interconnecting mobile base stations back to the PSTN point of presence (POP).
For details of where the equipment is intended to be used, see the country matrix below.
- AVIAT NETWORKS intends to market this equipment where a cross (X) is shown in the table below.
- The information contained in this table has been gathered from the relevant government authorities and
relates only to European countries participating in the R&TTE directive.
It s h ou l d b e n oted th at a l i c en s e to op er ate th i s eq u i p men t i s l i kel y to b e n ec es s ar y, an d
th e ap p r op r i ate r eg u l ator y ad mi n i s tr ati on s h ou l d b e c on tac ted .
260-668256-003 JULY 2015 V

VI AVIAT NETWORKS
Table of Contents
Copyright & Terms of Use i
Aviat Networks Technical & Sales Support ii
Product Compliance Notes iii
International Use of 5.8GHz iii
WEEE Directive iii
RoHS Directive iii
Declaration of Conformity, R&TTE Directive, 1999/5/EC iv
Table of Contents vii
CHAPTER 1. ERPS INTRODUCTION 1

Purpose and Scope 1
Acronyms 1
References 2
ERPS General Configurations 3
CLI Configurations 3
CHAPTER 2. ERPS PROTOCOL DESCRIPTION 5
CHAPTER 3. ERPS BRIDGE MODE CONFIGURATION 7

Configuring Bridge Mode during System Runtime 8
CLI Configurations 8
CHAPTER 4. ERPS CONFIGURATIONS 11

Starting/Shutting Down ERPS Module 12
CLI Configuration 12
Enabling/Disabling ERPS Module 13
Creating/Deleting Ethernet Ring Protection Group 14
Configuring Ring Specific Parameters 16
Configuring Ring Name 16
Configuring Ring Mandatory Parameters 17
260-668256-003 JULY 2015 VII

Configuring Ring Timers 29

Configuring Force/Manual Switch 34
Clearing Force/Manual Switch 36
Configuring Topology Change Propagation List 37
Configuring Recovery Method 38
Clearing the Ring Statistics Counters 39
Enabling/Disabling Debugging 43
Enabling/Disabling Trap Notification 45
Configuring Ring Port Presence 46
Configuring Distributing Ports 48
Configuring Minimizing Segmentation Objects 49
CHAPTER 5. ERPS CONFIGURATION GUIDELINES 51
CHAPTER 6. CONFIGURING ERPS VERSION 1 - EXAMPLES 53

Configuring Single ERPS Ring 54
Basic Configuration 54
Configuring Monitoring Entities in ECFM 56
Configuring Ring in ERPS 58
Configuring ERPS Service Based Protection of Multiple Rings 61
Configuring Monitoring Entities in ECFM (Ring 1) 74
CHAPTER 7. CONFIGURING ERPS VERSION 2 - EXAMPLES 77

Configuring a Single ERPS Ring 78
Configuring Monitoring Entities in ECFM 80
Configuring Ring in ERPS 82
Configuring Multiple ERPS Rings 85
Configuring ECFM 92
Configuring ERPS 101
VIII AVIAT NETWORKS

Chapter 1. ERPS Introduction

Aviat Networks ERPS (Ethernet Ring Protection Switching) provides highly reliable and stable
protection mechanism in ring networks. It also provides mechanisms to avoid formation of
loops, which affects network performance and service availability.
This section describes the purpose and scope of this document, lists the definitions / acronyms,
conventions used in this document, and the general CLI configurations.
Purpose and Scope

This document describes the ERPS module configuration on a switch running Aviat Networks
AOS. It also describes the configuration detail through CLI (Command Line Interface) inter-
faces.
The reader is expected to have a basic knowledge of the ERPS protocol.
Acronyms
Table 1-1. Acronyms Used in this Document
Acronym Explanation
APS Automatic Protection Switching
CCM Continuity Check Message
CLI Command Line Interface
DNF Do Not Flush
ECFM Ethernet Connectivity Fault Management
ERPS Ethernet Ring Protection Switching
FDB Forwarding Database
GARP Generic Attribute Registration Protocol
GMRP GARP Multicast Registration Protocol
GVRP GARP VLAN Registration Protocol
LA Link Aggregation
MA Maintenance Association
MD Maintenance Domain
ME Maintenance Entity
MEG Maintenance Entity Group
MEP Maintenance End Point
MI Multiple Instance
MSTP Multiple Spanning Tree Protocol
NR No Request
260-668256-003 JULY 2015 1

CHAPTER 1. ERPS INTRODUCTION
P2P Point-to-Point
PVID Port VLAN ID
R-APS Ring Automatic Protection Switching
RB RPL Blocked
RPL Ring Protection Link
RSTP Rapid Spanning Tree Protocol
SF Signal Fail
SNMP Simple Network Management Protocol
TC Topology Change
VCM Virtual Context Manager
VID VLAN Identifier
VLAN Virtual Local Area Network
WTR Wait-to-Restore
References
l CLI User Manual
l Quick Start Guide
l ITU-T G.8032/Y.1344 (06/2008) Ethernet Protection Switching
l ITU-T G.8032/Y.1344 Amendment 1 (04/2009) Ethernet Protection Switching
Amendment 1
l VLAN Configuration User Manual
2 AVIAT NETWORKS
ERPS General Configurations

This section provides details on the various modes for the CLI configuration.
CLI Configurations
This table lists the access and exit methods to various general configuration modes.
Table 1-2. CLI Configurations
Command Mode Access Method Prompt Exit method
User EXEC This is the initial mode aos> The logout method is used.
to start a session.
Privileged EXEC Use the enable com- aos# Use the command disable to
mand to enter the Priv- return from the Privileged EXEC
ileged EXEC mode. mode to User EXEC mode, the dis-
able command is used.
Global Con- Enter Privileged EXEC aos(config)# Use the command exit to log
figuration mode and use the com- out of the Global Configuration
mand configure Mode, and the command end to
terminal to enter the log out of the Privileged EXEC
Global Configuration mode.
Mode.
Multiple Use the Global Con- aos(config-switch)# Use the command exit to log
Instance Con- figuration mode com- out of the Global Configuration
figuration mand switch to enter Mode, and the command end to
the Multiple Instance log out of the Privileged EXEC
Configuration mode. mode.
VLAN Con- Use the Multiple aos(config-switch- Use the command exit to log
figuration Instance Configuration vlan)# into Multiple Configuration Mode,
mode command VLAN and the command end to log into
<VLAN ID> to enter the the Privileged EXEC mode.
VLAN configuration
mode.
APS Ring Group Use the Multiple aos(config-switch- Use the command exit to log
Configuration Instance Configuration ring)# into Multiple Configuration Mode,
mode command aps and the command end to log into
ring group, <aps ring the Privileged EXEC mode.
group id> to enter the
APS Ring Group Con-
figuration mode.
260-668256-003 JULY 2015 3

Chapter 2. ERPS Protocol

Description
Aviat Networks ERPS provides highly reliable and stable protection mechanism in ring net-
works; and provides mechanism to avoid formation of loop, which would affect network oper-
formance and service availability.
In ring networks, each ring node is connected to the adjacent nodes participating in the same
ring, using two independent links. A ring link is bounded by two adjacent nodes and a port for
a ring link is called a ring port. Aviat Networks ERPS ensures that there is no loop formed in a
ring topology by blocking a port, that is, the RPL (Ring Protection Link) port participating in
the ring. It also unblocks the RPL port, whenever there is any failure in the ring network. The
designated node, RPL owner is responsible for blocking/unblocking the RPL.
The fundamentals of the ERPS architecture are:
1. The principle of loop avoidance.
2. The utilization of learning, forwarding, and address table mechanisms of Ethernet
technology.
Loop avoidance in the ring is achieved by ensuring that, at any time, the traffic flows on all the
rings except the RPL. Under normal conditions, the RPL link is blocked, that is, not used for
traffic. The RPL owner is responsible to block traffic over the RPL.
Under a ring failure condition, the RPL owner is responsible to unblock the RPL, allowing the
RPL to be used for traffic. The event of a ring failure results in protection switching of the
traffic. R-APS (Ring Automatic Protection Switching) protocol is used to coordinate the pro-
tection actions over the ring.
Aviat Networks ERPS supports both revertive and non-revertive mode of operations.
Aviat Networks ERPS stack is conformed to the ITU-T standard G.8032/Y.1344 (06/2008) and
its amendment G.8032/Y.1344 Amendment 1 (04/2009). It is a part of the AOS Metro package
solution.
260-668256-003 JULY 2015 5

Chapter 3. ERPS Bridge Mode

Configuration
Aviat Networks ERPS is a multiple instantiated module.
This section describes the procedure to configure the bridge mode in the system.
260-668256-003 JULY 2015 7

CHAPTER 3. ERPS BRIDGE MODE CONFIGURATION
Configuring Bridge Mode during System

Runtime
The bridge mode is also configured at runtime. The following conditions apply, when bridge
mode is changed during runtime:
1. Spanning tree should be in shutdown state.
2. GARP module should be in shutdown state. GVRP and GMRP protocols should be
in disabled state.
3. ECFM module should be in shutdown state.
After changing the bridge mode, the above modules (STP, GARP, ECFM) can be started.
CLI Configurations
Execute the following commands to configure the bridge mode during system runtime.
1. Enter the Global Configuration mode.
aos#configure terminal
2. Enter the context configuration mode.
#switch default
3. Shutdown spanning tree.
aos(config-switch)# shutdown spanning-tree
4. Disable the GVRP module.
aos(config-switch)# set gvrp disable
Disable the GMRP module.
aos(config-switch)# set gmrp disable
5. Shutdown the GARP module.
aos(config-switch)# shutdown garp
6. Shutdown the ECFM module.
aos(config-switch)# no ethernet cfm start
7. Change the bridge mode to provider-edge bridge.
aos(config-switch)# bridge-mode provider-edge
aos(config-switch)# end
aos(config)# end
8. View the current bridge mode of the switch.
aos# show vlan device info switch default
Switch default
Vlan device configurations
--------------------------
Vlan Status : Enabled
Vlan Oper status : Enabled
Gvrp status : Disabled
Gmrp status : Disabled
8 AVIAT NETWORKS
Gvrp Oper status : Disabled

Gmrp Oper status : Disabled
Mac-Vlan Status : Disabled
Protocol-Vlan Status : Enabled
Bridge Mode : Provider Edge
Bridge
Traffic Classes : Enabled
Vlan Operational Learning Mode : IVL
Version number : 1
Max Vlan id : 4094
Max supported vlans : 2048
Unicast mac learning limit : 150
260-668256-003 JULY 2015 9

Chapter 4. ERPS Configurations

This section describes the various ERPS configurations such as start/shutdown ERPS module,
enable/disable ERPS module, create/delete ERPS ring group, ERPS ring specific configurations
and other related configurations.
260-668256-003 JULY 2015 11

CHAPTER 4. ERPS CONFIGURATIONS
Starting/Shutting Down ERPS Module

This section lists the CLI configuration steps to start and shutdown the ERPS module.
When the ERPS is shutdown (without the switch string) the ERPS module is shutdown in the
context and all the ring configurations in the context are deleted. When the shutdown com-
mand is used with the optional switch string, the ERPS context information in the switch will
be deleted. When the ERPS is started, ERPS module is started in the context and the module
status is initialized to disable. ERPS module should be started to perform the ERPS con-
figurations.
CLI Configuration
1. Enter the Multiple Instance Configuration mode
aos# configure terminal
aos(config)# Switch default
aos(config-switch)#
2. Start the ERPS module.
aos(config-switch)# no shutdown aps ring
3. View the ERPS global configuration for the switch.
aos# show aps ring global info switch switch1
Switch default
ERPS Global Info
--------------------------------------------
Module Status : Disabled
System Control : Start
Trap Status : Disabled
4. Shutdown the ERPS module.
aos(config-switch)# shutdown aps ring
Switch default
%ERPS is ShutDown
6. Shutdown the ERPS module with optional switch string.
aos(config-switch)# shutdown aps ring switch
Switch default
%ERPS is ShutDown
12 AVIAT NETWORKS
Enabling/Disabling ERPS Module

This section lists the CLI configuration steps to enable and disable the ERPS module.
When the ERPS functionality is enabled, ERPS module is enabled in the context and the ERPS
protocol starts running on all the rings configured in the context. When the ERPS functionality
is disabled, ERPS module is disabled in the context and all the rings configured in the context
become non-operational, that is, the ERPS protocol does not run on the rings in the context.
ERPS module should be started and enabled to perform the ERPS configurations.
CLI Configuration
1. Enter the Multiple Instance Configuration mode as specified
aos(config-switch)#
2. Enable the ERPS module.
aos(config-switch)# aps ring enable
3. Disable the ELPS module.
aos(config-switch)# no aps ring enable
4. View the ERPS module enable status for the switch.
aos# show aps global info Switch default
Switch default
ERPS Global Info
------------------------------------------------
Module Status : Enabled
ERPS modul e shoul d be started i n thi s vi rtual swi tch, before executi ng the
above commands.
5. View the ERPS module disable status for the switch.
aos# show aps global info Switch default
Switch default
ERPS Global Info
-----------------------------------------------
260-668256-003 JULY 2015 13

Creating/Deleting Ethernet Ring

Protection Group
This section details the CLI configurations to create and delete a ring.
When a ring entry is created it will be in an inactive state. If the ring entry is already created,
this configuration enters into the ring group mode for that ring entry. All the ring specific con-
figurations are done in the ring group configuration mode. These configurations include activ-
ating the ring group, configuring the ring ports and R-APS VLAN ID for the ring and related
actions.
When a ring entry is deleted, it deletes an already created ring entry. If the ring entry is not
present, the following error message is displayed.
Ring Entry is not present.
CLI Configuration
This CLI is valid only in the Multiple Instance Configuration mode.
1. Enter the Multiple Instance Configuration mode as specified in step Enter the Mul-
tiple Instance Configuration mode of Section CLI Configuration. ERPS module
should be started (as specified in step Enter the Multiple Instance Configuration
mode of CLI Configuration) and enabled (as specified in step Enter the Multiple
Instance Configuration mode as specified of CLI Configuration) before cre-
ating/deleting the ring group.
2. Create a ring with ring ID 1. Administrator can give any numerical number for the
ring. But, the given number should be unique in a virtual context.
aos(config-switch)# aps ring group 1
After successful execution of this command, the
CLI enters the ring group configuration mode and
the AOS CLI prompt changes as follows:
aos(config-switch-ring)#
I f the ri ng group i s al ready created, then the same command i s used to go
to the ri ng confi gurati on mode.
3. View the configurations of ring group 1.
aos# show aps ring group 1 configuration Switch
default
Switch default
Ring Id 1 Configurations
----------------------------------------------
RingName : Ring1
R-APS Vlan Id : 0
Ring Port1 : None
Ring Port2 : None
Node Type : Non-RPL Owner
14 AVIAT NETWORKS
RPL Port : 0
Operating Mode : Revertive
Recovery Method : Auto
Switch Command : None
SwitchCommand Port : 0
Port blocking on VC recovery : Allowed
TC Propagation Status : Disable
TC Propagation Ring List : None
Protection Type : port-based
Ring Id 1 CFM Configurations

----------------------------------------------
MEG1 : 0
ME1 : 0
MEP1 : 0
MEG2 : 0
ME2 : 0
MEP2 : 0
aos#
4. Delete the ring group 1 from Switch default.
aos(config-switch)# no aps ring group 1
5. View the configurations of ring group 1, after deleting it from Switch default.
default
Switch default
No i nformati on i s di spl ayed here, as the ri ng group 1 i s del eted from
Swi tch defaul t.
260-668256-003 JULY 2015 15

Configuring Ring Specific Parameters

This section details the CLI configurations that are specific to a particular ring group.
The ring specific configurations include ring name, RAPS VLAN ID, ring ports, ring monitoring
entries, RPL port, operating mode, ring timers and related actions.
I f the ri ng i s al ready i n acti ve state, then the user has to de-acti vate that
ri ng fi rst, then onl y the ri ng speci fi c confi gurati ons can be done.
Ri ng group I D or Ri ng I D means the same and i denti fi es a Ethernet pro-
tecti on ri ng.
To execute the CLI configurations provided in this section, user has to enter the ring con-
figuration mode.
The CLI configuration steps to enter the ring configuration mode are listed below.
1. Enter the Multiple Instance Configuration mode as specified in step Enter the Mul-
tiple Instance Configuration mode of section CLI Configuration.
2. Enter the ring configuration mode for ring ID 1.
3. If the command is successful, then it returns the prompt as follows:
Configuring Ring Name

This section lists the CLI configuration steps to provide a user-friendly name to a ring. This is
an optional configuration. By default, the ring name is configured for a ring, that is, the ring
name is constructed by appending ring ID to the string ring. For example, ring name for a ring
with ID as 1 will be ring1.
CLI Configuration
The CLI configuration steps to set the ring name are listed below.
1. Configure the ring name cust-ring1 for the ring 1.
aos(config-switch)# aps group name cust-ring1
ring group 1
2. View the ring name configured for the ring 1.
default
Switch default
--------------------------------------------------
RingName : cust-ring1
R-APS Vlan Id : 0
Ring Port1 : None
Ring Port2 : None
16 AVIAT NETWORKS
RPL Port : 0
Switch Command Port : 0

---------------------------------------------
MEG1 : 0
ME1 : 0
MEP1 : 0
MEG2 : 0
ME2 : 0
MEP2 : 0
Configuring Ring Mandatory Parameters

This section lists the CLI configuration steps to configure the mandatory parameters of a ring
group. Without configuring these parameters, the ring group cannot be made active.
The following are the mandatory parameters to be configured for making a ring as active:
1. R-APS VLAN ID
2. Ring ports
3. Ring monitoring entries
4. RPL port: If not configured, will have zero (meaning non-RPL owner). Ring can be
made active, even if this parameter is not configured. In that case, this ring node
starts working as a Non RPL owner.
5. Operating mode: If not configured, the mode will be revertive. Ring can be made
active, even if this parameter is not configured. In that case, the ring starts working
in revertive mode.
Configuring R-APS VLAN ID, Ring Ports

This section lists the CLI configuration steps to define the ring ports and ring VLAN ID for a
ring. The ring ports and R-APS VLAN should be configured for activating the ring group.
Confi guri ng the R-APS VLAN i n ERPS modul e wi l l not create VLAN i n the
system. VLAN shoul d be expl i ci tl y created i n VLAN modul e.
CLI Configuration
The CLI configuration steps to configure the ring VLAN ID and ring ports are listed below.
260-668256-003 JULY 2015 17

1. Enter the ring configuration mode for ring 1.

2. Deactivate the ring 1, if it is already activated.
aos(config-switch)# no aps ring group 1
3. Configure ring port 1 as gigabit Ethernet 0/1 and ring port 2 as gigabit Ethernet
0/2 and R-APS VLAN as VLAN 2 for ring 1.
aos(config-switch-ring)# aps working
gigabitethernet 0/1 gigabitethernet 0/2 vlan 2
4. Activate the ring 1.
aos(config-switch-ring)# aps group active
5. View the ring 1 configurations.
default
Switch default
-----------------------------------------------
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2
RPL Port : 0
------------------------------------------
MEG1 : 1
ME1 : 1
MEP1 : 1
MEG2 : 2
ME2 : 1
MEP2 : 7
18 AVIAT NETWORKS
Configuring Ring Operation Mode

This section lists the CLI configuration steps to change the ring operation mode (revertive or
non-revertive). In revertive mode of operation, the traffic channel is restored to the working
transport entity, i.e., blocked on the RPL, after the condition(s) causing a switch has cleared. In
non-revertive operation, the traffic channel is allowed to use the RPL, if it is not failed, after a
switch condition has cleared.By default, ring is in revertive mode of operation.
To configure this option, user should enter ring configuration mode. If ring is already activated,
then de-activate it and then give the following command.
CLI Configuration
The CLI configuration steps to change the ring operation mode are listed below.
1. Enter the ring configuration mode for ring group 1.
2. Configure the ring operation mode as non-revertive.
aos(config-switch-ring)# no aps revert
3. If the ring is already activated, use:
aos(config-switch)# no aps group active
User can confi gure the recovery method al ong wi th the no aps revert com-
mand. Thi s i s an opti onal confi gurati on.
4. View the operation type configured for the ring group 1 in switch.
default
Switch default
--------------------------------------------------
-
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2
RPL Port : 0
Operating Mode : Non-Revertive
--------------------------------------------
MEG1 : 1
260-668256-003 JULY 2015 19

ME1 : 1
MEP1 : 1
MEG2 : 2
ME2 : 1
MEP2 : 7
5. Configure the ring group operation mode as revertive.
aos(config-switch-ring)# aps revert
User can confi gure the WTR (Wai t-to-Restore) ti mer i nterval al ong wi th
the command aps revert. Thi s i s an opti onal confi gurati on. Refer secti on
Wait -t o-Rest ore Timer for more detai l on the WTR ti mer confi gurati on.
6. View the operation type configured for the ring group 1 in switch.
aos# show aps ring group 1 Switch default
Switch default
Ring Id 1
----------------------------------------------
Ring Name : Ring1
RAPS Vlan Id : 2
Recovery Method : Manual
ERPS Compatible Version : Version1
Ring State : Idle
Status : Active
Wait-to-restore timer : Not Running
Hold timer : Not Running
Guard timer : Not Running
This node is non-RPL Owner.

This node is non-RPL Neighbor.
Ring node is configured with virtual channel
Ring Port Link Status Command Port Status

--------------------------------------------------
-
Gi0/1 Not Failed None UnBlocked
20 AVIAT NETWORKS
Configuring RPL Port

This configuration is used to configure the RPL port for the ring group. In revertive mode of
operation, the traffic channel is restored to the working transport entity, i.e., blocked on the
RPL, after the condition(s) causing a switch has cleared.
CLI Configuration
The CLI configuration steps to configure the RPL port is listed below.
2. Configure the port gigabit Ethernet 0/2 as RPL port for the ring group 1 Switch
default.
aos(config-switch-ring)# aps protect
gigabitethernet 0/2
3. View the RPL port configuration.
default
Switch default
-------------------------------------------
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2
Node Type : RPL Owner
RPL Port : Gi0/2

-------------------------------------
MEG1 : 1
ME1 : 1
MEP1 : 1
MEG2 : 2
ME2 : 1
260-668256-003 JULY 2015 21

MEP2 : 7
Configuring ERPS compatible Version

This command configures the ERPS compatible version for the ring node.
Ring node compatible version can be configured to either Version 2 or Version 1 using this com-
mand.
then de-activate it:
#no aps ring group active
And then re-active the aps ring instance:
#aps group active
CLI Configuration
The CLI configuration steps to configure the ERPS compatible version as Version 2 is listed
below.
2. Configure the ring node compatible version for ring group 1 Switch default.
aos(config-switch-ring)# aps compatible version
v2
3. View the compatible version 2 configuration.
Switch default
Ring Id 1
-------------------------------------------
Ring Name : Ring1
RAPS Vlan Id : 2
Recovery Method : auto
Ring State : Idle
Status : Active
Wait-to-block timer : Not Running
22 AVIAT NETWORKS
This node is RPL Neighbour. RPL Neighbour is Gi0/2

Ring Port Link Status Command Port

Status
--------------------------------------------------
----
Gi0/1 Not Failed None
UnBlocked
blocked
Configuring RPL Neighbor port

This configuration is supported only when ERPS Compatible version is Version 2.
This configuration is used to configure the RPL neighbor port for the ring group. In revertive
mode of operation, the traffic channel is restored to the working transport entity, i.e., blocked
on the RPL, after the condition(s) causing a switch has cleared.
CLI Configuration
The CLI configuration steps to configure the RPL neighbor port is listed below.
2. Configure the port gigabit Ethernet 0/2 as RPL neighbor port for the ring group 1
Switch default.
aos(config-switch-ring)# aps neighbor
gigabitethernet 0/2
3. View the RPL neighbor port configuration.
Switch default
Ring Id 1
-------------------------------------------
Ring Name : Ring1
RAPS Vlan Id : 2
Ring State : Idle
Status : Active
260-668256-003 JULY 2015 23


This node is RPL Neighbour. RPL Neighbour is Gi0/2

Status
--------------------------------------------------
-
Gi0/2 Not Failed None blocked
Configuring Protection Type

This command configures the protection type for the ring node.
Ring node protection type can be configured to port based using this command.
CLI Configuration
The CLI configuration steps to configure the Protection type as service based in ring is listed
below.
2. View the protection type configuration.
aos# sh aps ring group 1 configuration Switch
default
Switch default
---------------------------------------
RingName : Ring1
R-APS Vlan Id : 0
Ring Port1 : None
Ring Port2 : None
Main Ring Id : 0
RPL Port : None
24 AVIAT NETWORKS
Switch Command Port : None

Port blocking on VC recovery : Not-Allowed
Protection Type : service-based
Group Manager : MSTP
Vlan Group Id : 0
Mac Id : 1

---------------------------------------
MEG1 : 0
ME1 : 0
MEP1 : 0
MEG2 : 0
ME2 : 0
MEP2 : 0
Configuring Vlan Group Manager

This command configures the vlan group manager to manage the grouping of vlans for the ring
node.
Vlan group Manager can be configured to either erps or mstp using this command.
CLI Configuration
The CLI configuration steps to configure the vlan group manger in ring are listed below.
1. Enter the global configuration mode after enabling ring
2. Configure the vlan group manager in switch.
aos(config-switch)# aps ring vlan-group-manager
erps
3. View the group manager configuration
default
Switch default
-------------------------------------------
RingName : Ring1
R-APS Vlan Id : 0
Ring Port1 : None
Ring Port2 : None
Main Ring Id : 0
260-668256-003 JULY 2015 25


RPL Port : None
SwitchCommand Port : None
Port blocking on VC recovery : Not-Allowed
Protection Type : service-based
Group Manager : ERPS
Vlan Group Id : 0
Mac Id : 1

----------------------------------------------
MEG1 : 0
ME1 : 0
MEP1 : 0
MEG2 : 0
ME2 : 0
MEP2 : 0
Configuring Monitoring Entities

This section lists the CLI configuration steps to associate the fault monitoring entities (Y1731
specific) with a ring group.
Confi guri ng the CF M moni tori ng i nformati on i n ERPS modul e does not
establ i sh the mai ntenance poi nts. Mai ntenance end poi nts shoul d be con-
fi gured i n CF M modul e expl i ci tl y.
To configure this option, user should enter ring configuration mode. If ring is already activated
CLI Configuration
The CLI configuration steps to associate the monitoring entities are listed below.
2. For ring port 1, configure MEG ID as 1, ME ID as 1 and MEP ID as 2 and for ring
port 2 configure MEG ID as 2, ME ID as 1 and MEP ID as 2.
aos(config-switch-ring)# aps working meg 1 me 1
mep 2 meg 2 me 1 mep 2
26 AVIAT NETWORKS
3. View the configured monitoring information for the protection entity for ring
group 1 in switch.
aos# show aps ring group 1 configurations Switch
default
Switch default
-------------------------------------------
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2

RPL Port : Gi0/2

----------------------------------------------
MEG1 : 1
ME1 : 1
MEP1 : 2
MEG2 : 2
ME2 : 1
MEP2 : 2
Activating/De-activating Ring
This section lists the CLI configuration steps to activate and deactivate a ring group.
To activate/deactivate a ring, user should enter the ring configuration mode.
CLI Configuration
The CLI configuration steps to activate/deactivate a ring are listed below.
260-668256-003 JULY 2015 27

2. Activate the APS ring group 1. Before activating, the mandatory configuration
(Ring ports, R-APS VLAN, CFM entries) for ring should be done.
3. View the ring 1 configurations in switch.
aos# show aps ring Switch default
Switch default
Ring Id 1
---------------------------------------------
Ring Name : Ring1
RAPS Vlan Id : 2
Ring State : Protection
Status : Active
Status
--------------------------------------------------
----
Gi0/1 Failed None
Blocked
Gi0/2 Failed None
Blocked
4. De- Activate the APS ring group 1.
aos(config-switch-ring)# no aps group active
aos# sh aps ring group 1 Switch default
Switch default
Ring Id 1
--------------------------------------------
Ring Name : Ring1
RAPS Vlan Id : 2
28 AVIAT NETWORKS

Ring State : Disabled
Status : inactive


Status
-------------------------------------------------
UnBlocked
Configuring Ring Timers

This section lists the CLI configuration steps for the various timer intervals related to a ring
group.
To configure the ring timers through CLI, user should enter the ring configuration mode. For
ring timer configurations, user does not have to de-activate the ring. The configured value of the
timer is applicable only from the next start/re-start of the timer.
Wait-to-Restore Timer
The WTR (Wait-to-Restore) timer will be running when RPL owner receives NR message in pro-
tection state.
This timer interval has a period from 0 to 86400000 milliseconds. The value of the timer can
be configured through CLI in the following units:
milliseconds
seconds
minutes
hours
CLI module converts the given value to milliseconds and calls the corresponding mib low level
routine to set the WTR timer.
The timer value is shown in milliseconds, even though it is configured in various units.
If the ring is configured with revertive mode of operation. Non-Revertive mode does not run
WTR.
260-668256-003 JULY 2015 29

CLI Configuration
The CLI configuration steps to set the WTR timer is listed below.
2. Configure the WTR time interval for the ring as 5 minutes.
aos(config-switch-ring)# aps revert wtr 5 minute
3. View the configured WTR timer value.
aos# show aps ring group 1 timers Switch default
Switch default
Ring Id 1 Timers
------------------------------------------------
Periodic Timer Interval : 5000 milli-
seconds
Hold-Off Timer Interval : 0 milli-seconds
Guard Timer Interval : 500 milli-
seconds
WTR Timer Interval : 300000 milli-
seconds
Vc Periodic Timer Interval : 5560 milli-
seconds
WTR ti mer confi gurati on i n aps revert command i s an opti onal parameter.
I t i s hel pful for the user to confi gure the i ntended val ue for WTR ti mer,
i nstead of the defaul t val ue 5 mi nutes, whi l e setti ng the ri ng operati onal
mode i tsel f. I n thi s case, user can use aps revert wai t-to-restore com-
mand. But, before usi ng thi s command, ri ng group shoul d bede-acti vated
fi rst.
Wait-to-Block Timer
The WTB (Wait-to-Block) timer will be started
1. when RPL owner receives RAPS (MS), RAPS (NR) in Manual Switch state
2. or
3. when RPL owner receives RAPS (NR) in Forced Switch state
4. or
5. when user gives “aps clear” command in RPL owner node when node state is
Forced Switch or Manual Switch.
This timer interval has a period from 0 to 86400000 milliseconds. The value of the timer can
be configured through CLI in the following units:
milliseconds
seconds
minutes
hours
30 AVIAT NETWORKS
routine to set the WTB timer.
CLI Configuration
The CLI configuration steps to set the WTB timer is listed below.
2. Configure the WTB time interval for the ring as 5 minutes.
aos(config-switch-ring)# aps wtb 5 minute
3. View the configured WTB timer value.
Switch default
Ring Id 1 Timers
-------------------------------------------------
seconds
seconds
seconds
WTB Timer Interval : 300000 milli-
seconds
Configuring Hold-off Timer

The hold-off timer is the interval for:
a server layer protection mechanism to fix a problem before switching at client layer,
or
an upstream protected domain to switch before a downstream domain.
This timer interval has a period from 0 to 3600000 milliseconds. The value of the timer can be
configured through CLI in the following units:
milliseconds
seconds
minutes
hours
routine to set the hold-ff timer value.
CLI Configuration
The CLI configuration steps to set the hold-off timer are listed below.
260-668256-003 JULY 2015 31


2. Set the hold-off timer interval as 10 milliseconds for ring group 1.
aos(config-ring)# aps timers hold-off 10
milliseconds
3. View the configured value of hold-off timer interval.
Switch default
Ring Id 1 Timers
-----------------------------------------------
seconds
seconds
seconds
seconds
Configuring Periodic Timer

The periodic timer is the time interval for sending Automatic Ring Protection Switching Pro-
tocol Data Units.
1. milliseconds
2. seconds
3. minutes
4. hours
routine to set the periodic timer value.
CLI Configuration
The CLI configuration steps to set the periodic timer are listed below.
2. Set the periodic timer interval to 3000 millisecond for ring group 1.
aos(config-switch-ring)# aps timers periodic
3000 milliseconds
32 AVIAT NETWORKS
3. View the configured value of periodic timer interval.
Switch default
Ring Id 1 Timers
----------------------------------------------
seconds
seconds
seconds
seconds
Configuring Guard Timer

The guard timer is the time interval to prevent reception of outdated R-APS messages.
1. milliseconds
2. seconds
3. minutes
4. hours
routine to set the guard timer value.
CLI Configuration
The CLI configuration steps to set the guard timer are listed below.
2. Set the guard timer interval as 20 milliseconds for ring group 1.
aos(config-switch-ring)# aps timers guard 20
milliseconds
3. View the configured guard timer interval value.
Switch default
Ring Id 1 Timers
-----------------------------------------------
260-668256-003 JULY 2015 33


seconds
Guard Timer Interval : 20 milli-seconds
seconds
seconds
Configuring Force/Manual Switch

This section lists the CLI configuration steps to configure the manual / force switch command
on a ring. To execute this configuration, user should enter the ring group mode. By default, this
switch command will be none.
Before this configuration, the switch port for that ring should be given.
In CLI, this switch port and switch command will be given in a single command.
CLI Configuration
The CLI configuration steps to set the manual / force switch is listed below.
1. Enter the ring group configuration mode for ring group 1.
2. Configure the ring switch command as manual for ring group 1.
aos(config-switch-ring)# aps manual
gigabitethernet 0/2
3. View the switch command configuration for ring group 1.
default
Switch default
----------------------------------------------
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2
RPL Port : Gi0/2
Switch Command : Manual
SwitchCommand Port : Gi0/2
34 AVIAT NETWORKS

----------------------------------------------
MEG1 : 1
ME1 : 1
MEP1 : 1
MEG2 : 2
ME2 : 1
MEP2 : 7
4. Configure the ring switch command as force for ring group 1.
aos(config-switch-ring)# aps force
gigabitethernet 0/2
default
Switch default
----------------------------------------------
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2
RPL Port : Gi0/2
Switch Command : Force
Switch Command Port : Gi0/2

-------------------------------------------
MEG1 : 1
ME1 : 1
MEP1 : 1
MEG2 : 2
ME2 : 1
MEP2 : 7
260-668256-003 JULY 2015 35

The no form of this command no aps manual or no

aps force is used to clear the switch command
configuration for the ring group 1.
Clearing Force/Manual Switch

This command is used to trigger clear operation, to remove the switch commands (Force
Switch/Manual Switch) or trigger reversion in revertive mode before the WTR or WTB timer
expires or trigger reversion in non-revertive mode when the ERPS compatible version number is
configured as 2.
To execute this configuration, user should enter the ring group mode.
CLI Configuration
The CLI configuration steps to clear the manual / force switch is listed below.
2. Clear the ring switch command for ring group 1.
aos(config-switch-ring)# aps clear
default
Switch default
---------------------------------------------
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2
RPL Port : Gi0/2

---------------------------------------
MEG1 : 1
ME1 : 1
36 AVIAT NETWORKS
MEP1 : 1
MEG2 : 2
ME2 : 1
MEP2 : 7
Configuring Topology Change Propagation List

This section lists the CLI configuration steps to configure the list of rings, where TC (Topology
Change) has to be propagated, whenever there is a FDB (Forwarding Database) flush condition
in the sub-ring. The rings that are to be configured as TC propagate ring IDs should be present
in the system.
CLI Configuration
The CLI configuration steps to set the TC propagation list is listed below.
1. Configure ring 1, 2, 3 and 4 in the system using the configuration steps mentioned
in the section CLI Configuration to Creating/Deleting Ethernet Ring Protection
Group.
3. Configure the ring IDs 2, 3 and 4 as TC propagate IDs for the ring group 1. This
command enables the propagate-TC status also.
aos(config-switch-ring)# aps propagate-tc status
enable ring-ids 2-4
4. View the TC propagate ring IDs for the ring group 1.
default
Switch default
----------------------------------------------
RingName : Ring1
R-APS Vlan Id : 1
Ring Port1 : Gi0/1
Ring Port2 : None
RPL Port : 0
TC Propagation Status : Enable
TC Propagation Ring List : 2,3,4
260-668256-003 JULY 2015 37


--------------------------------------------
MEG1 : 1
ME1 : 1
MEP1 : 4
MEG2 : 5
ME2 : 1
MEP2 : 6
Configuring Recovery Method

This section lists the CLI configuration steps to set the recovery method for a ring group.
In Manual-Recovery mode, there will be no action taken by the recovered node as compared to
Auto-Recovery mode. In this mode the recovered link will remain in blocked state and continue
to transmit R-APS (SF) messages, until administrator clears the failure condition.
This configuration will have impact only in non-revertive mode of operation. By default, the
recovery mode will be auto for a ring.
CLI Configuration
The CLI configuration steps to set the recovery method are listed below.
2. Configure the recovery method as manual for ring group 1.
aos(config-switch-ring)# no aps revert manual
3. View the recovery method for ring group 1.
default
Switch default
--------------------------------------------
RingName : Ring1
R-APS Vlan Id : 2
Ring Port1 : Gi0/1
Ring Port2 : Gi0/2
RPL Port : Gi0/2
Recovery Method : Manual
Switch Command : Force
38 AVIAT NETWORKS


----------------------------------------------
MEG1 : 1
ME1 : 1
MEP1 : 1
MEG2 : 2
ME2 : 1
MEP2 : 7
Clearing the Ring Statistics Counters

This section lists the CLI configuration steps to clear the counters statistics information for the
given ring or all the rings.
The cl ear aps ri ng stati sti cs command i s appl i cabl e for a parti cul ar ri ng
group. I n thi s command, the ri ng group I D i s opti onal parameter, thi s com-
mand wi l l del ete the stati sti cs counter of the gi ven ri ng i n the ri ng group
I D. I f the ri ng i s not gi ven, then i t del etes stati sti cs counters for al l the
ri ng i n the system.
To execute this configuration, user should enter the switch mode.
CLI Configuration
The CLI configuration steps to clear the counters statistics information is listed below.
1. Enter the switch mode Switch default
Execute clear aps ring statistics to clear the
statistics counter for ring group 1.
aos(config-switch)# clear aps ring statistics
ring group 1
2. View the ring statistics.
aos# show aps ring group 1 statistics Switch
default
Switch default
Ring Id 1 Statistics
---------------------------------------------
Port1 R-APS Pdu's Sent Count : 0
Port1 R-APS Pdu's Received Count : 0
Port1 R-APS Pdu's Discarded Count : 0
260-668256-003 JULY 2015 39

Port1 Blocked Count : 0

Port1 un-Blocked Count : 0
Port1 Failed Count : 0
Port1 recovered Count : 0
Port1 Version Discard Count : 0
Port1 R-APS NR Pdu's Rx Count : 0
Port1 R-APS NR Pdu's Tx Count : 0
Port1 R-APS NRRB Pdu's Rx Count : 0
Port1 R-APS NRRB Pdu's Tx Count : 0
Port1 R-APS SF Pdu's Rx Count : 0
Port1 R-APS SF Pdu's Tx Count : 0
Port1 R-APS Event Pdu's Rx Count : 0
Port1 R-APS Event Pdu's Tx Count : 0
Execute clear aps ring statistics to clear the
statistics counter for all the ring groups in
context 1.
aos(config-switch)# clear aps ring statistics
3. View the ring statistics.
aos# show aps ring statistics Switch default
Switch default
--------------------------------------------
40 AVIAT NETWORKS

-----------------------------------------------
260-668256-003 JULY 2015 41


{1.3.6.1.4.1.29601.2.40.3.4.1.20.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.21.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.22.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.23.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.24.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.25.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.26.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.27.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.28.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.29.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.30.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.31.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.32.1.2 Counter32 0}
{1.3.6.1.4.1.29601.2.40.3.4.1.33.1.2 Counter32 0}
42 AVIAT NETWORKS
Enabling/Disabling Debugging
This section lists the CLI configuration steps to enable or disable the debugging trace messages
for ERPS module. This configuration sets the trace level for debugging. When a particular trace
is enabled, the debugging message of the sub-modules for which trace is enabled is displayed.
CLI Configuration
The CLI configuration steps to enable or disable the debugging trace messages are listed below.
1. View the currently enabled debug trace level for ERPS module in virtual Switch
default.
aos# debug aps ring Switch default
Switch default
ERPS critical debugging is on
2. Enable packet dump trace for ERPS module.
aos# debug aps ring pkt-dump Switch default
Thi s enabl es the packet dump trace messages. Whenever an R-APS PDU i s
recei ved or transmi tted, the packet i nformati on wi l l be dumped i n the ter-
mi nal consol e.
3. View the configured debug trace level value.
aos# debug aps ring Switch default
Switch default
ERPS packet dump debugging is on
ERPS critical debugging is on
4. Similarly, the following trace levels can be enabled:
l all = All trace messages

l all-fail = All failure traces
l buff = Buffer allocation/release traces
l critical = Critical traces
l ctrl = Control Plane traces
l mgmt = Management traces
l pkt-dump = Packet dump traces
l resource = Traces related to all resources such as memory, data
structure
l start-shut = Start and shut down traces
l switch = Switch related configuration
5. All the above mentioned options can be given in a single command itself (except
the global trace option), as follows:
aos# debug aps ring critical init-shut mgmt
debug aps ring critical mgmt ctrl pkt-dump
resource all-fail buff switch default
260-668256-003 JULY 2015 43

6. Disable packet dump trace in virtual context 1.

aos# no debug aps ring pkt-dump Switch default
7. Disable packet dump and control plane trace together in virtual context 1.
aos# no debug aps ring ctrl pkt-dump Switch
default
44 AVIAT NETWORKS
Enabling/Disabling Trap Notification

This section lists the CLI configuration steps to enable/disable sending trap notification mes-
sages from the ERPS module. This notification can be enabled or disabled per virtual context
(only if APS ring is started on that context).
CLI Configuration
The CLI configuration steps to enable or disable sending trap notification messages is listed
below.
1. Enable the ring notification for the switch.
aos(config-switch)# aps ring notification enable
2. View the trap notification enable/disable status for the switch.
aos# show aps ring global info Switch default
Switch default
ERPS Global Info
-------------------------------------------
Module Status : Enabled
Trap Status : Enabled
The no form of this command disables the APS
notification for the switch.
aos(config-switch)# no aps ring notification
enable
3. View the trap notification enable/disable status for the switch.
aos# sh aps ring global info Switch default
Switch default
ERPS Global Info
--------------------------------------------
260-668256-003 JULY 2015 45

Configuring Ring Port Presence

This section lists the CLI configuration steps to configure the port presence in a ring.
To configure the port presence, enter the ring configuration mode.
CLI Configuration
The CLI configuration steps to configure the port presence are listed below.
2. Configure ring ports - port1 and port2 for the ring
aos(config-switch-ring)# aps working gi 0/1
gigabitethernet 0/2 vlan 2
3. Configure the port presence as local for port1 and remote for port2.
aos(config-switch-ring)# aps ring port1 local
port2 remote
aos# show aps ring Switch default
Switch default
Ring Id 1
------------------------------------------
Ring Name : Ring1
RAPS Vlan Id : 2
Ring State : Disabled
Status : inactive
Inter Connection Node : none
Multiple Failure : Disabled
Node ID, BPR bit Pair

=====================
Ring Port 1 - (00:00:00:00:00:00 , 0)
Ring Port 2 - (00:00:00:00:00:00 , 0)
46 AVIAT NETWORKS

Status
--------------------------------------------------
----
UnBlocked
UnBlocked
Line Card Information
-----------------------
Ring Port 1 :Local
Ring Port 2 :Remote
260-668256-003 JULY 2015 47

Configuring Distributing Ports

This section lists the CLI configuration steps to configure the distributing port required for Dis-
tributed ERPS .
To configure the port presence, enter the ring configuration mode.
CLI Configuration
The CLI configuration steps to configure the port presence are listed below.
2. Configure ring ports port1 and port2 for the ring
aos(config-switch-ring)# aps working gi 0/1
3. Configure the port presence as local for port1 and remote for port2.
aos(config-switch-ring)# aps ring port1 local
port2 remote
4. Configure the CFM configuration for ring ports.
5. Configure the distributing port for the ring.
aos(config-switch-ring)# aps distribute
gigabitethernet 0/10
48 AVIAT NETWORKS
Configuring Minimizing Segmentation

Objects
This section lists the CLI configuration steps to configure interconnection node of the subring
and multiple failure in interconnection node of the sub-ring to avoid segmentation in the main
ring. This configuration is applicable for Compatible version V2.
CLI Configuration
The CLI configuration steps to configure the interconnection node of the subring and multiple
failures in interconnection node of the sub-ring
1. Enter into the ring configuration mode for the sub-ring
2. Configure the inter-connection node as primary or secondary
aos(config-switch-ring)# aps interconnection-
node primary
3. Configure the multiple failure in interconnection-node as primary or secondary
aos(config-switch-ring)# aps multiple-failure
primary
260-668256-003 JULY 2015 49

Chapter 5. ERPS Configuration

Guidelines
Aviat Networks ERPS provides highly reliable and stable protection mechanism to protect a ring
network from the formation of loops. The following are the guidelines to be followed, for the
Aviat Networks ERPS to protect Ethernet rings:
1. In a ring, only one RPL port (hence, only one RPL owner) should be configured. If
multiple RPL ports are configured in the ring, then the ring will get segmented.
2. R-APS VLAN has to be explicitly created with proper member ports for switching
R-APS messages. It is recommended that R-APS VLAN is created first through the
VLAN configuration before making the ring entry active, in order to avoid any loss of
R-APS PDU Tx/Rx. It is not recommended to use the same R-APS VLAN ID for more
than one ring.
3. R-APS VLANs should be used only for ring R-APS message communication and
should not be used for data switching and management purposes.
4. A port that is member of link aggregator should not be configured as a ring port.
5. A ring port should not be configured as member of link aggregated port.
6. If data traffic is happening on a port and that needs to be configured as a ring
port, then the following steps should be followed to avoid loop in the network before
ERPS takes control:
Shutdown the port (admin down)
Disable spanning tree on that port
Configure the port as ring port, activate the ring
Enable the port (admin up)
7. To avoid loop in a ring, either ERPS has to be enabled or spanning tree to be
enabled. If both are disabled, then loop is possible in the ring. If both are enabled on
the same port, then the behavior is unknown.
8. Before making a ring entry active, the MEPs associated with the ring ports should
be created in the fault monitoring module (ECFM-Y.1731). Otherwise, ERPS will not
be able to register with the fault monitoring module for getting the link fault status
and for receiving R-APS PDUs.
9. Hold-off timer for a sub-ring should be greater than the hold-off timer for the ring
to which it is connected (shares a link).
10. When the ring is in Non-Revertive mode, all the ring nodes of the ring should be
configured in either auto recovery method or manual recovery method to observe
proper behavior of the ring.
260-668256-003 JULY 2015 51

Chapter 6. Configuring ERPS

Version 1 - Examples
This sectionprovides the sample configuration setup for provisioning Ethernet protection rings
for version 1 using Aviat Networks ERPS through CLI.
260-668256-003 JULY 2015 53

CHAPTER 6. CONFIGURING ERPS VERSION 1 - EXAMPLES
Configuring Single ERPS Ring
Figure 6-1. Ring Topology 1

This section describes the procedure to configure a single Ethernet protection ring using CLI.
Basic Configuration
This section details the basic CLI configuration steps that should be followed before the ERPS
ring configurations.
Configuration through CLI

The basic CLI configuration steps are listed below.
Execute the following configurations in all the four switches, AOS1, AOS2, AOS3 and AOS4:
1. Create virtual context switch and set the bridge mode as provider edge bridge
aos(config-switch)# spanning-tree mode mst
aos(config-switch)# exit
2. Map interface P1 to switch1 and disable spanning tree in the port.
aos(config)# interface gigabitethernet 0/1
aos(config-if)# map Switch default
aos(config-if)# spanning-tree disable
aos(config-if)# exit
54 AVIAT NETWORKS

5. Enable interface P1.
aos(config-if)# no shutdown
8. Set the port type for interface P3.
aos(config-if)# bridge port-type
customerNetworkPort port-based
aos(config-if)# end
9. Create R-APS VLAN 2 and map interfaces P1, P2.
10. aos# configure terminal
aos(config-switch)# vlan 2
aos(config-switch-vlan)# ports gigabitethernet
0/1,0/2
11. aos(config-switch-vlan)# exit
12. aos(config-switch)# exit
13. Create VLAN 3 in switch with member ports P1 , P2 and P3, where P3 is
untagged member port.
0/1-3 untagged gigabitethernet 0/3
15. aos(config-switch-vlan)# exit
16. aos(config-switch)# exit
260-668256-003 JULY 2015 55

17. Set PVID (Port VLAN ID) for P3 as 3 in switch.

aos(config-if)# switchport pvid 3
19. aos(config-if)# exit
Configuring Monitoring Entities in ECFM

This section details the CLI configuration steps to enable the ECFM module and configure the
monitoring entities in ECFM.
AOS1 Configuration through CLI

The CLI configuration steps to configure the monitoring entities in ECFM are listed below.
20. Start the ECFM module and enable the ECFM module and Y1731 module in
switch.
aos(config-switch)# ethernet cfm start
aos(config-switch)# ethernet cfm enable
aos(config-switch)# ethernet cfm y1731 enable
21. Create MD (Maintenance Domain) with name CUS1 and level 6.
aos(config-switch)# ethernet cfm domain format
dns-like-name name CUS1 level 6
22. Create MA (Maintenance Association) with name CUSMA1 and VLAN 2.
aos(config-ether-ecfm)# service format char-
string name CUSMA1 vlan 2
23. Create MEP1 and MEP2 for VLAN 2 within this MD and MA.
aos(config-ether-ecfm)# mep crosscheck mpid 1
vlan 2
vlan 2
aos(config-ether-ecfm)# exit
24. Create MD with name CUS4 and level 6.
25. Create MA with name CUSMA1 and VLAN 2.
vlan 2
vlan 2
56 AVIAT NETWORKS
27. Set the CCM (Continuity Check Message) interval as one second and enable CC
on level 6 VLAN 2.
aos(config-switch)# ethernet cfm cc level 6 vlan
2 interval one-sec
aos(config-switch)# ethernet cfm cc enable level
6 vlan 2
28. Install MEP 1 for VLAN 2 on interface P1.
aos(config-if)# ethernet cfm mep level 6 mpid 1
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
aos(config-if)# end

switch.
vlan 2
vlan 2
260-668256-003 JULY 2015 57


vlan 2
vlan 2
8. Set the CCM (Continuity Check Message) interval as one second and enable CC on
level 6 VLAN 2.
2 interval one-sec
6 vlan 2
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
11. aos(config-if)# end

Execute the same steps in AOS 3 as mentioned in section AOS1 Configuration through CLI
AOS1 Configuration through CLI.

Configuring Ring in ERPS

This section details the sample CLI ring configurations in ERPS.

The CLI configuration steps to configure rings in ERPS is listed below.
1. Enable ERPS in switch.
58 AVIAT NETWORKS
aos(config)# switch 1
2. Create ring 1, map ring ports to the ring and create cfm entry for the ring.

The CLI configuration steps to configure ring in ERPS is listed below.
5. aos(config-switch-ring)# aps group active


To configure the RPL ports, execute the following CLI configurations in AOS 4:
1. Configure RPL port for ring 1.
260-668256-003 JULY 2015 59


gigabitethernet 0/2
aos(config-switch-ring)# aps revert 500
milliseconds
60 AVIAT NETWORKS
Configuring ERPS Service Based

Protection of Multiple Rings
Basic Configuration

Execute the following CLI configuration steps in AOS 1 to perform the basic configurations:
aos(config-switch)# bridge-mode provider-core
2. Disable gvrp and gmrp in switch
3. Map interface P1 to switch and disable spanning tree in the port.
aos(config-if)# map switch
260-668256-003 JULY 2015 61


aos(config-if)# end
0/1,0/3
aos(config-switch-vlan)# end
10. Create R-APS VLAN 3 in switch with member ports P1 , P2 and P3.
0/1-3
11. Create RAPS Vlan 4 in switch with member ports P1 and P3
0/1,0/3
12. Create RAPS Vlan 5 in switch with member port P1,P2 ad P3
0/1-3
0/1,0/3
62 AVIAT NETWORKS

0/1-3
15. .Create protected data VLAN 20 in switch.
0/1-3
16. Create protected data VLAN 40 in switch.
0/1-3
0/1-3

1. Create virtual context switch and set the bridge mode as provider core bridge
260-668256-003 JULY 2015 63


aos(config-if)# end
0/1,0/2
10. Create R-APS VLAN 3 in switch with member ports P1 , P2
0/1-2
0/1,0/2
64 AVIAT NETWORKS
Create RAPS Vlan 5 in switch with member port
P1,P2
0/1-2
0/1,0/2
13. Create RAPS Vlan 7 in switch with member port P1,P2
0/1-2
260-668256-003 JULY 2015 65


0/1,0/2
66 AVIAT NETWORKS

0/1-2
0/1,0/2
0/1-2
0/1,0/2
0/1-2
0/1,0/2
14. .Create protected data VLAN 40 in switch.
0/1,0/2
260-668256-003 JULY 2015 67


0/1,0/2

1. Create virtual context switch and set the bridge mode as provider core bridge.
68 AVIAT NETWORKS
aos(config-if)# end
0/1,0/3
0/1-3
0/1,0/3
0/1-3
0/1,0/3
260-668256-003 JULY 2015 69


0/1-3
0/1-3
0/1-3
0/1-3

70 AVIAT NETWORKS

0/1-2
0/1-2
0/1-2
0/1,0/2
260-668256-003 JULY 2015 71

0/1,0/2
0/1,0/2

72 AVIAT NETWORKS
aos(config-if)# end
0/1,0/2
0/1,0/2
0/1,0/2
14. aos(config-switch-vlan)# end
260-668256-003 JULY 2015 73


16. aos(config-switch-vlan)# end
Configuring Monitoring Entities in ECFM (Ring 1)

switch.
vlan 2
vlan 2
vlan 2
vlan 2
74 AVIAT NETWORKS
8. Set the CCM interval as one second and enable CC on level 6 VLAN 2.
2 interval one-sec
6 vlan 2
vlan 2 active
aos(config-if)# end
vlan 2 active
aos(config-if)# end
vlan 3
vlan 3
3 interval one-sec
vlan 3 active
aos(config-ether-mep)# end
6 vlan 3
260-668256-003 JULY 2015 75

15. Create MEP13 and MEP14 for VLAN 3.
aos(config-switch)# ethernet cfm default-domain
global level 7 mip-creation-criteria default
aos(config-switch)# ethernet cfm default-domain
vlan 3 level 7 mip-creation-criteria default
vlan 3
vlan 3
aos(config-switch)# ethernet cfm cc level 7
vlan 3 interval one-sec
aos#
aos(config-if)# ethernet cfm mep level 7 inward
mpid 14 vlan 3 active
7 vlan 3
76 AVIAT NETWORKS
Chapter 7. Configuring ERPS

Version 2 - Examples
This sectionprovides the sample configuration setup for provisioning Ethernet protection rings
for version 2 using Aviat Networks ERPS through CLI.
260-668256-003 JULY 2015 77

Configuring a Single ERPS Ring

This section describes the procedure to configure a single Ethernet protection ring for version 2
through CLI. Refer topology for these sample configurations.
Basic Configuration
Configuration through CLI

The basic CLI configuration steps are listed below.
Execute the following configurations in all the four switches, AOS1, AOS2, AOS3 and AOS4:
78 AVIAT NETWORKS
aos(config-if)# end
0/1,0/2
aos(config-switch-vlan)# exit
10. Create VLAN 3 in switch with member ports P1 , P2 and P3, where P3 is
untagged member port.
260-668256-003 JULY 2015 79


Configuring Monitoring Entities in ECFM


switch.
vlan 2
vlan 2
vlan 2
vlan 2
80 AVIAT NETWORKS
level 6 VLAN 2.
2 interval one-sec
6 vlan 2
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
aos(config-if)# end

switch.
vlan 2
vlan 2
260-668256-003 JULY 2015 81


vlan 2
vlan 2
level 6 VLAN 2.
2 interval one-sec
6 vlan 2
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
aos(config-if)# end


Configuring Ring in ERPS

This section details the sample CLI ring configurations in ERPS.

82 AVIAT NETWORKS
aos(config-switch-ring)#aps protection-type
port-based
v2
aos(config-switch-ring)# aps neighbor
gigabitethernet 0/2

port-based
v2
260-668256-003 JULY 2015 83


Execute the same steps in AOS 3 as mentioned in section 6.2.3.3 AOS1 Configuration through
CLI.

Execute the same steps in AOS 4 as mentioned in section6.2.3.3 AOS1 Configuration through
CLI.
To configure the RPL ports, execute the following CLI configurations in AOS 4:
aos(config-switch-ring)#aps compatible version
v2
port-based
gigabitethernet 0/2
84 AVIAT NETWORKS
Configuring Multiple ERPS Rings

Ring 1 is comprised of ring nodes AOS1, AOS2, AOS3 and AOS4.
The sub-ring Ring 2 is comprised of ring nodes AOS1, AOS4, AOS5 and AOS6.
The inter-connecting link between AOS1 and AOS4 is owned by Ring1.
Basic Configuration
This section details the CLI configuration steps to be followed before the ERPS multiple ring
configurations. Refer topology Figure 6-2 for these sample configurations.

260-668256-003 JULY 2015 85

aos(config-if)# end
0/1,0/3
0/1-3
10. Create VLAN 4 in switch.
0/1-3
86 AVIAT NETWORKS

aos(config-if)# end
0/1,0/2
260-668256-003 JULY 2015 87


0/1,0/2
aos(config-if)# end
11. Create VLAN 4 in switch.
aos(config-if)# end

88 AVIAT NETWORKS

aos(config-if)# end
0/1,0/2
0/1,0/2
8. Create VLAN 4 in switch
0/1-2


1. Create virtual context switch and set the bridge mode as provider edge bridge.
260-668256-003 JULY 2015 89

aos(config-if)# end
0/1,0/2
0/1-2

90 AVIAT NETWORKS

aos(config-if)# end
0/1,0/2
aos(config-if)# end
260-668256-003 JULY 2015 91

aos(config-if)# end
Configuring ECFM
This section describes the procedure to configure ECFM.

Execute the following CLI configuration steps to configure ECFM:
switch.
vlan 2
vlan 2
92 AVIAT NETWORKS

vlan 2
vlan 2
2 interval one-sec
6 vlan 2
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
aos(config-if)# end
vlan 3
vlan 3
3 interval one-sec
vlan 3 active
260-668256-003 JULY 2015 93

6 vlan 3

To configure ECFM through CLI, execute the following steps in AOS 2:
switch.
vlan 2
vlan 2
vlan 2
vlan 2
2 interval one-sec
94 AVIAT NETWORKS

6 vlan 2
9. Install MEP2 for VLAN 2 on interface P1.
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
aos(config-if)# end

switch.
vlan 2
vlan 2
260-668256-003 JULY 2015 95


vlan 2
vlan 2
2 interval one-sec
6 vlan 2
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
aos(config-if)# end
6 vlan 2
aos(config-if)# end

switch.
96 AVIAT NETWORKS

vlan 2
vlan 2
vlan 2
vlan 2
2 interval one-sec
6 vlan 2
vlan 2 active
aos(config-if)# end
aos#
vlan 2 active
aos(config-if)# end
260-668256-003 JULY 2015 97


vlan 3
vlan 3
3 interval one-sec
vlan 3 active
6 vlan 3

switch.
vlan 3
vlan 3
98 AVIAT NETWORKS

vlan 3
vlan 3
3 interval one-sec
6 vlan 3
vlan 3 active
aos(config-if)# end
aos#
vlan 3 active
aos(config-if)# end
6 vlan 3
aos(config-if)# end

switch.
260-668256-003 JULY 2015 99


vlan 3
vlan 3
vlan 3
vlan 3
3 interval one-sec
6 vlan 3
vlan 3 active
aos(config-if)# end
aos#
vlan 3 active
aos(config-if)# end
100 AVIAT NETWORKS


6 vlan 3
aos(config-if)# end
Configuring ERPS
This section describes the procedure to configure ERPS.

To configure ERPS through CLI in AOS 1, execute the following steps:
v2
aos(config-switch-ring)# end
3. Configure RPL port for ringi 1.
gigabitethernet 0/1
aos(config-switch-ring)# aps revert wtr 600
milliseconds
4. Create sub-ring ring 2.
260-668256-003 JULY 2015 101


v2
5000 milliseconds hold-off 0 milliseconds guard
5000 milliseconds
5. Enable subring without virtual channel and Topology changes flag
aos(config-switch-ring)# aps subring-without-
virtualchannel enable
aos(config-switch-ring)#aps propagate-tc status
enable ring-ids 1
aos(config-switch-ring)#end

v2
aos(config-switch-ring)#aps neighbor
gigabitethernet 0/1
102 AVIAT NETWORKS


v2

v2
3. Create sub-ring ring 2.
260-668256-003 JULY 2015 103


v2
aos(config-switch-ring)#aps neighbor
gigabitethernet 0/2
5000 milliseconds hold-off 0 milliseconds guard
5000 milliseconds
4. Enable subring without virtual channel and Topology changes flag
aos(config-switch-ring)#aps propagate-tc status
enable ring-ids 1

v2
104 AVIAT NETWORKS


gigabitethernet 0/2
aos(config-switch-ring)# aps revert wtr 300
milliseconds
4. Enabling subring without virtual channel

v2
3. Enabe subring without virtual channel
260-668256-003 JULY 2015 105


Configuring Minimizing Segmentation Objects
To avoid the main ring segmentation from subring for multiple failures in Main Ring, configure
the following in both interconnected nodes.
In interconnected node Switch default:
1. Configure the below commands in interconnected node Switch default
node primary
3. Configure the multiple failures in interconnection-node as primary or secondary
primary
In interconnected node switch 4:
4. Configure the below commands in interconnected node switch 4
node primary
6. Configure the multiple failures in interconnection-node as primary or secondary
primary
106 AVIAT NETWORKS

260-668256-003
WWW.AVIATNETWORKS.COM

CTR 8500-8300 3.0 ERPS Config July2015 260-668256-003

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CTR 8500-8300 3.0 ERPS Config July2015 260-668256-003

Uploaded by

Copyright:

Available Formats

CTR 8300/8500 CONFIGURATION

260-668256-003 JULY 2015 I

Aviat Networks Technical & Sales

Sales and Sales Support

Product Compliance Notes

International Use of 5.8GHz

260-668256-003 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

260-668256-003 JULY 2015 V

CHAPTER 1. ERPS INTRODUCTION 1

CHAPTER 2. ERPS PROTOCOL DESCRIPTION 5

CHAPTER 3. ERPS BRIDGE MODE CONFIGURATION 7

CHAPTER 4. ERPS CONFIGURATIONS 11

260-668256-003 JULY 2015 VII

Configuring Ring Timers 29

CHAPTER 5. ERPS CONFIGURATION GUIDELINES 51

CHAPTER 6. CONFIGURING ERPS VERSION 1 - EXAMPLES 53

CHAPTER 7. CONFIGURING ERPS VERSION 2 - EXAMPLES 77

VIII AVIAT NETWORKS

Chapter 1. ERPS Introduction

Purpose and Scope

260-668256-003 JULY 2015 1

ERPS General Configurations

260-668256-003 JULY 2015 3

Chapter 2. ERPS Protocol

260-668256-003 JULY 2015 5

Chapter 3. ERPS Bridge Mode

260-668256-003 JULY 2015 7

Configuring Bridge Mode during System

Gvrp Oper status : Disabled

260-668256-003 JULY 2015 9

Chapter 4. ERPS Configurations

260-668256-003 JULY 2015 11

Starting/Shutting Down ERPS Module

Enabling/Disabling ERPS Module

260-668256-003 JULY 2015 13

Creating/Deleting Ethernet Ring

Ring Id 1 CFM Configurations

260-668256-003 JULY 2015 15

Configuring Ring Specific Parameters

Configuring Ring Name

Ring Id 1 CFM Configurations

Configuring Ring Mandatory Parameters

Configuring R-APS VLAN ID, Ring Ports

260-668256-003 JULY 2015 17

1. Enter the ring configuration mode for ring 1.

Configuring Ring Operation Mode

260-668256-003 JULY 2015 19

This node is non-RPL Owner.

Ring Port Link Status Command Port Status

Configuring RPL Port

Ring Id 1 CFM Configurations

260-668256-003 JULY 2015 21

Configuring ERPS compatible Version

This node is non-RPL Owner.

This node is RPL Neighbour. RPL Neighbour is Gi0/2

Ring Port Link Status Command Port

Configuring RPL Neighbor port

260-668256-003 JULY 2015 23

Guard timer : Not Running

Ring Port Link Status Command Port

Configuring Protection Type

Switch Command Port : None