XTM Series

Ethernet Muxponder II
Installation Guide R32.0
Installation & Commissioning
Ethernet Muxponder-II:
GBE10-EMXP10/II, GBE22-EMXP10/II, EMXP40G/II, EMXP80G/II
Ethernet Muxponder-IIe:
EMXP48/IIe, EMXP62/IIe, EMXP120/IIe, EMXP220/IIe, EMXP240/IIe
Gigabit Ethernet NID:
NID-GE, NID-GEH
IC-INST-EMXPII

Rev A | 2018-12-06
Copyright

© Copyright 2018 Infinera Corporation. All rights reserved.

This Manual is the property of Infinera Corporation and is confidential. No part of this Manual may be reproduced for
any purposes or transmitted in any form to any third party without the express written consent of Infinera.

Infinera makes no warranties or representations, expressed or implied, of any kind relative to the information or any
portion thereof contained in this Manual or its adaptation or use, and assumes no responsibility or liability of any kind,
including, but not limited to, indirect, special, consequential or incidental damages, (1) for any errors or inaccuracies
contained in the information or (2) arising from the adaptation or use of the information or any portion thereof
including any application of software referenced or utilized in the Manual. The information in this Manual is subject to
change without notice.

Trademarks

Infinera, Infinera Intelligent Transport Networks, I-PIC, IQ NOS, FlexILS, DTN-X, DTN, ATN, FastSMP and logos that
contain Infinera are trademarks or registered trademarks of Infinera Corporation in the United States and other
countries. All other trademarks in this Manual are the property of their respective owners.

Infinera DTN-X, DTN, FlexILS, Cloud Xpress, XT and ATN Regulatory Compliance

FCC Class A

This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this
device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation. Modifying the equipment without Infinera's written authorization
may result in the equipment no longer complying with FCC requirements for Class A digital devices. In that event,
your right to use the equipment may be limited by FCC regulations, and you may be required to correct any
interference to radio or television communications at your own expense.

DOC Class A

This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus as set out in
the interference-causing equipment standard titled “Digital Apparatus," ICES-003 of the Department of
Communications.

Cet appareil numérique respecte les limites de bruits radioélectriques applicables aux appareils numériques de
Classe A prescrites dans la norme sur le matériel brouilleur: "Appareils Numériques," NMB-003 édictée par le
Ministère des Communications.

Class A ITE

This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic
environment, radio interference may occur, in which case, the user may be required to take corrective actions.

Warning

This is a class A product. In a domestic environment this product may cause radio interference in which case the user
may be required to take adequate measures.

FDA

This product complies with the DHHS Rules 21CFR 1040.10 and 1040.11, except for deviations pursuant to Laser
Notice No. 50,dated June 24, 2007.
Technical Assistance
Customer Support for Infinera products is available, 24 hours a day, 7 days a week (24x7).
For information or assistance with Infinera products, please contact the Infinera Technical
Assistance Center (TAC) using any of the methods listed below:
• Email: techsupport@infinera.com
• Telephone:
• Direct within United States: 1-408-572-5288
• Outside North America: +1-408-572-5288
• Toll-free within United States: +1-877-INF-5288 (+1-877-463-5288)
• Toll-free within Germany/France/Benelux/United Kingdom: 00-800-4634-6372
• Toll-free within Japan: 010-800-4634-6372
• Infinera corporate website: http://www.infinera.com
• Infinera Customer Web Portal: https://support.infinera.com
Please see the Infinera Customer Web Portal to view technical support policies and
procedures, to download software updates and product documentation, to view training
course information, or to create/update incident reports and RMA requests.

Documentation Feedback
Infinera strives to constantly improve the quality of its products and documentation. Please
submit comments or suggestions regarding Infinera Technical Product Documentation using
any of the following methods:
• Submit a service request using the Infinera Customer Web Portal
• Send email to: techpubs@infinera.com
• Send mail to the following address:
Attention: Infinera Technical Documentation and Technical Training
Infinera Corporation
140 Caspian Court
Sunnyvale, CA 94089
When submitting comments, please include the following information:
• Document name and document ID written on the document cover page
• Document release number and version written on the document cover page
• Page number(s) in the document on which there are comments
 CONTENTS

Contents
1 Introduction.........................................................................................................................1
1.1 Document Revision History.........................................................................................1
2 Abbreviations and Definitions ...............................................................................................2
3 Background ........................................................................................................................7
3.1 Traffic Definitions .......................................................................................................7
3.2 MPLS-TP .................................................................................................................7
3.2.1 Label Edge Router............................................................................................8
3.2.2 Label Switch Router..........................................................................................8
3.2.3 MPLS-TP and Layer 2 Switching Interwork and functional compatibility ................9
3.2.4 MPLS-TP Linear protection configuration ...........................................................9
3.2.5 Pseudowire Operations...................................................................................10
3.2.6 MPLS-TP Quality of Service ............................................................................ 11
4 Preconditions....................................................................................................................13
4.1 Safety .....................................................................................................................13
4.1.1 Laser product safety .......................................................................................13
4.1.2 ESD Safety ...................................................................................................13
4.2 Actions Before Installation ........................................................................................13
4.3 Verify pre-installed SW .............................................................................................14
4.4 CU-System..............................................................................................................15
4.5 TU Upgrade.............................................................................................................15
4.6 Recommended Tools and Equipment ........................................................................16
5 Installing the Traffic Unit.....................................................................................................17
5.1 Installing SFP/XFP...................................................................................................17
5.2 SFP/SFP+ extraction tool .........................................................................................18
5.3 Creating a Traffic Unit in the Node .............................................................................19
6 Configuration ....................................................................................................................20
6.1 Prerequisites ...........................................................................................................20
6.2 ENM GUI ................................................................................................................20
6.2.1 Subracks view................................................................................................22
6.2.2 Verbose mode................................................................................................23
6.2.3 Board settings ................................................................................................24
6.2.4 Network Element Parameters..........................................................................24
6.3 Enhanced GUI features ............................................................................................25
6.3.1 Accessing single entries..................................................................................25
6.3.2 Filtering overview tables..................................................................................25
6.3.3 Sorting overview tables ...................................................................................26
6.3.4 Multiset in overview tables...............................................................................27
6.3.5 Create and Delete entries in overview tables ....................................................28
6.4 Layer 1 Port Configuration ........................................................................................29
6.4.1 Setting Expected Frequency — Tunable XFP/SFP+ ..........................................29
6.4.2 Setting Physical Media....................................................................................29
6.4.3 Changing Signal Format .................................................................................30
6.4.4 Setting Near End Loopback.............................................................................31
6.4.5 Setting Far End Loopback ...............................................................................31
6.4.6 Configuring FEC Type ....................................................................................31
6.4.7 Configuring Signal Degrade Threshold.............................................................32
6.4.8 Configuring Optical Layer Mapping ..................................................................32
6.5 Layer 2 Port Configuration ........................................................................................34
6.5.1 Setting Auto Negotiation .................................................................................34
6.5.2 Setting Port Mode...........................................................................................35
6.5.3 Setting Native VLAN ID...................................................................................35
6.5.4 Setting Native Priority .....................................................................................35
6.5.5 Creating Link Aggregation Group (LAG) ...........................................................36
6.5.6 Configure LACP .............................................................................................39
6.5.7 Creating Shapers ...........................................................................................41
6.5.8 Creating Policers ............................................................................................41
6.5.9 Configure Port Mirroring..................................................................................42
6.5.10 Setting Port Trust..........................................................................................44

IC-INST-EMXPII Rev A | 2018-12-06 IV

Infinera Proprietary and Confidential
 CONTENTS

6.5.11 Enabling LLDP .............................................................................................45

6.5.12 Viewing LLDP information .............................................................................45
6.6 VLAN Configuration .................................................................................................47
6.6.1 Creating VLAN Maps ......................................................................................47
6.6.2 Creating VLAN Rules......................................................................................49
6.7 Multicast Configuration.............................................................................................52
6.7.1 Configuring a Multicast Enabled Interface.........................................................52
6.7.2 Configuring a Static Multicast member .............................................................53
6.7.3 Viewing Multicast Membership Tables ..............................................................54
6.7.4 Viewing Multicast Forwarding Tables................................................................56
6.8 Policies Configuration ..............................................................................................58
6.8.1 Creating Classifications ..................................................................................58
6.8.2 Creating Actions.............................................................................................60
6.8.3 Creating MEF Policer......................................................................................62
6.8.4 Configuring QoS Profiles.................................................................................64
6.8.5 WRED ...........................................................................................................65
6.9 Synchronous Ethernet Configuration .........................................................................65
6.9.1 Creating a synchronization domain ..................................................................65
6.9.2 Associating board with synchronization domain ................................................66
6.9.3 Enabling/Disabling Quality Level Selection .......................................................67
6.9.4 Configuring Synchronization Bus .....................................................................67
6.9.5 Configuring Sync source .................................................................................68
6.9.6 Setting Source Mode of Sync Source ...............................................................69
6.9.7 Setting Priority of Sync Source ........................................................................70
6.9.8 Setting Static Quality Level..............................................................................70
6.9.9 Clearing Wait to Restore Timer ........................................................................70
6.9.10 Setting Manual/Forced Switch .......................................................................71
6.9.11 Enabling/disabling PTP1588v2 TC .................................................................71
6.10 Configuring Ethernet OAM .....................................................................................72
6.10.1 Creating MEG ..............................................................................................72
6.10.2 Creating MEP...............................................................................................73
6.10.3 Creating LM Session.....................................................................................75
6.10.4 Creating DM Session ....................................................................................78
6.11 ERPv1 Configuration ..............................................................................................82
6.11.1 Creating an ERPv1 node ...............................................................................82
6.12 Configuring ERPv2 ................................................................................................84
6.12.1 Creating an ERPv2 node...............................................................................85
6.12.2 Creating a VLAN Protection Group.................................................................90
6.12.3 Viewing ERPv2 configuration.........................................................................93
6.13 Configuring Multi Chassis Redundancy....................................................................94
6.13.1 Creating an ICCP Redundancy Group............................................................94
6.13.2 Creating an MC-LAG ....................................................................................96
6.14 Configuring MPLS-TP ............................................................................................98
6.14.1 Configuration of MPLS Node .........................................................................99
6.14.2 Configuration of MPLS Interface .................................................................. 100
6.14.3 Configuration of Label Switched Path........................................................... 102
6.14.4 Configuration of MPLS Tunnel ..................................................................... 104
6.14.5 Creation of MPLS linear protection............................................................... 106
6.14.6 Configuration of MPLS linear protection ....................................................... 108
6.14.7 MPLS linear protection operator commands ................................................. 108
6.15 Configure Pseudowires ........................................................................................ 110
6.15.1 Creating an Edge Pseudowire ..................................................................... 110
6.15.2 Service Delimiting VLAN Tag Operations...................................................... 111
6.15.3 Creating a Multi-Segment Pseudowire ......................................................... 112
6.16 MPLS-TP OAM configuration ................................................................................ 114
6.16.1 Creating a BFD Template ............................................................................ 114
6.16.2 Creating a BFD Session.............................................................................. 115
6.16.3 Configuration of Tunnel ID or Destination tunnel ID ....................................... 117
6.16.4 Changing the configuration of Tunnel ID, Destination tunnel ID, and
Destination global ID ............................................................................... 117
6.16.5 Configuration of LSP ID............................................................................... 118

IC-INST-EMXPII Rev A | 2018-12-06 V

Infinera Proprietary and Confidential
 CONTENTS

6.16.6 Configuration MPLS-TP MEP ID for LSP LSR............................................... 119

6.16.7 Interoperability of BFD Session and MPLS-TP MEP ID.................................. 119
6.16.8 BFD warnings and alarms ........................................................................... 119
6.17 Viewing and removing MPLS-TP configuration ....................................................... 120
6.17.1 MPLS-TP Service Overview ........................................................................ 120
6.17.2 Viewing static MPLS-TP configuration in CLI ................................................ 122
6.17.3 Viewing MPLS-TP protection and OAM configuration in CLI........................... 122
6.17.4 Viewing PW configuration in CLI .................................................................. 122
6.17.5 Removing MPLS-TP configuration ............................................................... 123
6.18 Configuring Port Devices ...................................................................................... 124
6.18.1 Creating a NID ........................................................................................... 124
6.18.2 NID Port Configuration ................................................................................ 125
6.18.3 NID OAM Configuration .............................................................................. 127
6.18.4 Delete NID configuration ............................................................................. 135
6.18.5 Upgrading NID firmware.............................................................................. 136
6.18.6 Restart NID ................................................................................................ 139
6.18.7 Creating an iSFP port device ....................................................................... 140
6.18.8 Configure iSFP........................................................................................... 142
6.18.9 Configure iSFP IWF .................................................................................... 142
6.18.10 Reset PM counters ................................................................................... 144
6.19 Error Propagation................................................................................................. 146
6.19.1 Creating an Error Propagation Entry ............................................................ 146
6.20 Mgmt VLAN Configuration .................................................................................... 148
6.20.1 Creating management VLAN channel on client ports ..................................... 148
6.20.2 Enabling Management VLAN – Node Level .................................................. 148
6.20.3 Enabling Management VLAN – TU Level...................................................... 148
6.20.4 Enabling Management VLAN – Port Level .................................................... 149
6.20.5 Changing Management VLAN Settings – Port Level ...................................... 149
6.20.6 Configuring GbE port on EMXP40................................................................ 150
6.20.7 Configuring Private VLAN ........................................................................... 151
6.21 Configuring OpenFlow mode ................................................................................ 151
6.21.1 L1 port configuration ................................................................................... 151
6.21.2 L2 port configuration ................................................................................... 152
6.21.3 Configuring an OpenFlow logical switch ....................................................... 152
6.21.4 Creating an OpenFlow controller connection................................................. 153
6.22 Configuring NETCONF for use by Xceed ............................................................... 153
6.22.1 Setting NETCONF mode using GUI ............................................................. 154
6.22.2 Setting NETCONF mode using CLI .............................................................. 154
6.23 Configuring PPP over Ethernet ............................................................................. 155
6.23.1 Creating PPPoE using GUI.......................................................................... 155
6.23.2 Creating PPPoE using CLI .......................................................................... 156
6.23.3 Verifying PPP links and default gateway ....................................................... 157
6.24 Configuring Topology Entries ................................................................................ 158
6.24.1 Creating an Internal Entry............................................................................ 158
6.24.2 Creating a Peer Entry.................................................................................. 159
6.24.3 Creating a Client Entry ................................................................................ 160
7 Commissioning of EMXP/II............................................................................................... 161
7.1 Node Preparations and Acceptance Tests................................................................ 161
7.1.1 Verifying Corrrect SFP/XFP........................................................................... 161
7.1.2 Verifying Internal Fiber Connections............................................................... 161
7.1.3 Measuring Optical Power .............................................................................. 161
7.1.4 Connecting Nodes........................................................................................ 162
7.1.5 Preparing for Network Acceptance Test.......................................................... 163
7.1.6 Preparing Cabling for End to End Test............................................................ 163
7.1.7 Near End Loop Back..................................................................................... 163
7.2 Network Acceptance Tests ..................................................................................... 164
7.2.1 Connecting traffic analyzers for end to end test ............................................... 164
7.2.2 Verifying error free line traffic ......................................................................... 164
7.2.3 Verifying Management Channels ................................................................... 165
7.3 Preparing the System for Operation......................................................................... 165
7.3.1 Save, reboot, check alarms and upload.......................................................... 166

IC-INST-EMXPII Rev A | 2018-12-06 VI

Infinera Proprietary and Confidential
 INTRODUCTION

1 Introduction
This manual provides an overview of how to install, configure and commission the Ethernet
Muxponder/II and Ethernet Muxponder/IIe traffic units (EMXP/II and EMXP/IIe).

1.1 Document Revision History

Table 1 Document Revision History

Revision Date Description of changes

A 2018-12-06 First release R32.0

IC-INST-EMXPII Rev A | 2018-12-06 1 (167)

Infinera Proprietary and Confidential
 ABBREVIATIONS AND DEFINITIONS

2 Abbreviations and Definitions

Active Unit Active Unit: For example a PCU or VOA2P

ALS Automatic Laser Shutdown

ASM Any source multicast

BBE Background Block Error

BER Bit Error rate (PM Definition)

Board A board can be a traffic unit, active unit or a passive unit.

BFD Bidirectional Forwarding Detection

C-tag Customer VLAN Tag with a TPID of 0x8100

CBS Commited Burst Size

CC Continuity Check

CCM Continuity check message as defined in ITU-T Y.1731

CFI Canonical Format Indicator

Chassis Card cage with primary power, fan units, mounting brackets. Also referred
to as subrack.
CIF Customer Interface
CIR Commited Information Rate
CLI Command Line Interface
Some parts of a command require a value that is unique to the installation
being performed. These parts are italic, e.g. subrack. These will have to
be changed to reflect the installation.
Normally it is presupposed that after a command is entered the enter but-
ton is pressed to execute the command. Sometimes <enter> is used to
clarify for the user that the enter button has to be pressed to continue a
configuration.

CoS Class of Service

CU Control Unit, to be used in the TM-3000 or TM-301 chassis

CU-less A traffic unit that is installed in a TM-102 or TM-101 chassis

CU-less mode A traffic unit running in a TM-101 or TM-102. Also referred to as stand-
alone mode.
CU-less SW Required for a TU that is installed in a TM-102 or TM-101 chassis

CU-system A TM-3000 or TM-301 chassis configured with a CU.

CV Connectivity Verification

CWDM Coarse Wavelength Division Multiplexing

DCN Data Communications Network

IC-INST-EMXPII Rev A | 2018-12-06 2 (167)

Infinera Proprietary and Confidential
 ABBREVIATIONS AND DEFINITIONS

DEI Drop Eligibility Indicator

DM Delay Measurement also called ETH-DM, as defined in ITU-T Y.1731 and

IEEE 802.1ag

DWDM Dense Wavelength Division Multiplexing

EBS Excess Burst Size

EIR Excess Information Rate
ENM Embedded Node Manager

ERP Ethernet Ring Protection

ES Errored Second (PM definition)

ESMC Ethernet Synchronization Messaging Channel

ESD Electrostatic Discharge

Fallback An operation where a node has been upgraded to a new SW release and
is returned to a previous version of SW that the node was running.

FCAPS Fault, Configuration, Accounting, Performance and Security Management.

(ITU Term)

FE Fast Ethernet (100 Mb/s Ethernet)

FEC Forward Error Correction

FW Firmware
GbE Gigabit Ethernet (1000 Mb/s Ethernet)

GUI Graphical User Interface

HW Hardware
ID Identifier
iSFP Intelligent SFP

IGMP Internet Group Message Protocol

LAG Link Aggregation Group

LED Light Emitting Diode

LER Label Edge Router

LM Loss Measurement also known as ETH-LM, as defined in ITU-T Y.1731

and IEEE 802.1ag

LOS Loss of Signal

LSP Label Switched Path

LSR Label Switch Router
MAC Media Access Control
MEF Metro Ethernet Forum

IC-INST-EMXPII Rev A | 2018-12-06 3 (167)

Infinera Proprietary and Confidential
 ABBREVIATIONS AND DEFINITIONS

MEG Managed Entity Group

MEP Maintenance association End Point

MPLS Multiprotocol label switching

MPLS-TP Multiprotocol label switching Transport Profile

MPLS Tunnel A MPLS entity providing a logical association between two Label Edge
Routers. The tunnel is instantiated by one or several LSPs.

MIB Management Information Base

MXP Muxponder is a term for a combined aggregator and transponder

NE Network Element
NID Network Interface Device
NIF Network Interface
NMS Network Management System

NNI Network to Network Interface

OAM Operations administration and management

OSC Optical Supervisory Channel

OSPF Open Shortest Path First, a dynamic routing protocol

OSS Operation Support System

Passive Unit For example an optical filter.

PCP Priority Code Point

Plug-in unit For example, a power unit, fan, traffic unit, passive unit, SFP or XFP

PM Performance Monitoring or Performance Management (FCAPS)

PoP Point of Presence

PSC Protection State Coordination, coordinates protection switching between
two MPLS end points.

PW Pseudowire
QoS Quality of Service

RDI Remote Defect Indication

Revert An operation performed during an ongoing upgrade that entails reactiva-
tion of a previous version of SW

ROADM Reconfigurable optical add drop multiplexer

RPL Ring Protection Link, used in ERP

S-tag Service VLAN Tag with a TPID of 0x88a8

SES Severely Errored Second (PM definition)

IC-INST-EMXPII Rev A | 2018-12-06 4 (167)

Infinera Proprietary and Confidential
 ABBREVIATIONS AND DEFINITIONS

SFP Small form-factor pluggable transceiver.

SLA Service Level Agreement

SNMP Simple Network Management Protocol

SNTP Simple Network Time Protocol

SOAM Service OAM, focuses on service delivery, as defined in ITU-T Y.1731 and
IEEE 802.1ag

Spare part A replacement unit.

Spare part mode In this mode, the TU will automatically upgrade the SW and switch to TU
mode if installed in CU-system. If the TU is installed in a TM-101 or TM-
102 chassis the TU will switch to standalone mode. Once the TU has been
started spare part mode is disabled.

Standalone mode In this mode, a TU is running in a TM-101 or TM-102 chassis.

Subrack Card cage with primary power, fan units, mounting brackets etc. Also re-
ferred to as “chassis”.
SW Software
TCP Transmission Control Protocol
TDM Time Division Multiplexing

TNM Dynamic Network Administrator - Metro

TP Transponder

TPID Tag Protocol Identifier

Traffic Unit A general term for a unit that carries traffic.

TRX An electrical or optical SFP or an XFP module.

TU Traffic Unit
TU MODE In this mode, the TU is running in a TM-3000 or TM-301 chassis. The TU
is managed by a CU.

TU SW Is required for a TU installed in a TM-3000 or TM-301 chassis.

UAS Unavailable Second (PM definition)

UNI User Network Interface

UNIMUX User Network Service Multiplexed Interface

Upgrade An operation where a node is upgraded to an earlier or later version of SW

Up MEP A Maintenance End Point located on the client side of a traffic unit, send
packets through the switch core towards the network

CC ID used to identify a Maintenance End Point, refer to MEP

VLAN Virtual Local Area Network

WDM Wavelength Division Multiplexing

IC-INST-EMXPII Rev A | 2018-12-06 5 (167)

Infinera Proprietary and Confidential
 ABBREVIATIONS AND DEFINITIONS

WRED Weighted Random Early Detection also known as Weighted Random

Early Discard

XC MPLS Cross-connect
XFP 10 Gigabit Small Form Factor Pluggable Module

IC-INST-EMXPII Rev A | 2018-12-06 6 (167)

Infinera Proprietary and Confidential
 BACKGROUND

3 Background
This section provides a short background on concepts and definitions relating to Layer 2.

3.1 Traffic Definitions

This section establishes some basic traffic definitions used by the EMXP family from genera-
tion II and onwards. The EMXP Traffic Unit recognizes the TPIDs standardized in
IEEE802.1Q. These are TPID values of:
• 0x88a8, used for Service VLANs
• 0x8100, used for Customer VLANs
Priority tagged traffic i.e. a frame with a VLAN tag that has VLAN ID zero is not treated in any
special manner.
The EMXP marks frames with one of three different tag statuses. These are double tagged,
single tagged or untagged.
Double tagged frames are defined as having one outer and one inner tag. The inner tag has
TPID 0x8100 and the outer tag has a TPID corresponding to either 0x8100 or 0x88a8.
Single tagged frames have one outer tag with TPID that equal 0x8100 or 0x88a8 and do not
have any inner tag with TPID corresponding to 0x8100.
Untagged frames have no VLAN tags with TPIDs of either 0x8100 or 0x88a8.
In this manual a C-tag denotes a tag where the TPID is 0x8100 and S-tag denotes a tag with
TPID 0x88a8.
The outer VLAN tag is the one closest to the MAC source address. There has to exist several
VLAN tags in order for a frame to have an inner VLAN tag. If a frame only has a single VLAN
tag, that tag will be considered as an outer VLAN tag.

Fig. 1 Outer and inner VLAN tag definition

Multicast traffic is defined on two layers. Layer two multicast is defined by the MAC destination
address multicast bit, the least significant bit in the first octet, is set.
Multicast traffic can also be defined on layer three as IPv4 multicast, then the MAC destination
address is in the interval of 01:00:5E:00:00:00 to 01:00:5E:7F:FF:FF. The IP destination ad-
dress must also be in the address range of 224.0.0.0 to 239.255.255.255

3.2 MPLS-TP
The EMXP/II traffic units support MPLS-TP based virtual private wire services (VPWS) provid-
ing encapsulation and transparent transport of ethernet based services. The option to do serv-
ice delimiting operations is included in the pseudowire. A configuration model of MPLS-TP
providing a VPWS is shown in 2.

IC-INST-EMXPII Rev A | 2018-12-06 7 (167)

Infinera Proprietary and Confidential
 BACKGROUND

Fig. 2 An overview of MPLS-TP configuration

In 2 the color markings indicate configuration that needs to be coordinated between the
EMXP/II Traffic units in order for the MPLS based service to be able to correctly forward traffic.
The configuration do only need to be coordinated layer by layer in the model. For example:
There are no dependencies between how the parameters are selected in MPLS interfaces
and in LSPs. The arrows indicate the flow of traffic colored according to the labels they will
have on different segments.

3.2.1 Label Edge Router

The Label Edge Router (LER) functionality of the EMXP/II family provides an MPLS-TP serv-
ice edge. Basically it maps ethernet traffic based on a port, port and VLAN or based on a poli-
cy classification into a pseudowire, which encapsulates an MPLS-TP structure according to
RFC-4448 on the original ethernet frame.

3.2.2 Label Switch Router

The Label Switch Router (LSR) simply switch the incoming traffic that matches one of the
MPLS interfaces defined on the TU. A switch decision will be built upon the matching MPLS
cross connect which defines the next hop.

IC-INST-EMXPII Rev A | 2018-12-06 8 (167)

Infinera Proprietary and Confidential
 BACKGROUND

3.2.3 MPLS-TP and Layer 2 Switching Interwork and functional

compatibility
MPLS-TP is designed to seamless integrate with existing L2 installations based on VLAN and
MAC address switching. In order to have a well defined behaviour of the switching fabric in the
EMXP/II a number of rules for switching are applied. This since the switching fabric should be
able to switch MPLS tagged frames in MPLS aware fashion or treat the frame as an ordinary
ethernet frame.
To be defined as an MPLS package the MPLS frame must have a backbone VLAN ID that
matches on of the defined MPLS interfaces, also the destination MAC address must match
the MPLS interface MAC address. All other traffic will be forwarded according to the normal
L2 switching rules according to VLAN maps and port trust.
If a received MPLS frame matches a MPLS interface but do not get any hit amongst the MPLS
cross connects it will be dropped.
If a received frame matches both the MPLS interface and a MPLS cross connect of a edge
LSP a lookup is made of the inner MPLS label against the available pseudowire labels. If no
such match can be found the frame will be dropped, else it will be stripped of the MPLS-TP en-
capsulation and forwarded to the port defined by the pseudowire.
It is possible to mix VLANs carrying MPLS-TP traffic with usual S-VLANs and C-VLANs seam-
less on the same physical interfaces.
Within the normal frame pipeline several functions are not supported when using the MPLS-
TP transport layer. It is not supported to make service mappings, port policing and MEF polic-
ing while mapping traffic into a pseudowire. Queue mappings and Shaping are however sup-
ported pipeline operations.

3.2.4 MPLS-TP Linear protection configuration

Fig. 3 An overview of MPLS-TP linear protection configuration

To configure MPLS-TP Linear Protection for a Label Edge Router (LER) a protection LSP is
associated to the tunnel. The protection domain is defined by the working path LSP and pro-
tection path LSP configured in the LERs.

IC-INST-EMXPII Rev A | 2018-12-06 9 (167)

Infinera Proprietary and Confidential
 BACKGROUND

The roles (working / protection) of the protection group paths are static and the traffic is trans-
ported using one path at a time. The protection group can be configured to operate in revertive
and non-revertive mote.
A protection switch can be triggered by a fault indication or an administrative command issued
by the operator. The traffic of all pseudowires associated to the protected tunnel are switched
to the working / protection LSP in case of a protection switch.
A fault indication is generated by a local loss of signal, an continuity check time out or failed
connectivity verification.
For continuity check and connectivity verification a Bidirectional Forwarding Detection (BFD)
session must be configured for the LSPs.

3.2.5 Pseudowire Operations

Once a MPLS-TP tunnel has been created it is straightforward to add services in form of pseu-
dowires to the tunnel. A pseudowire represents a point to point service which in its simplest
form, transparent mode and classified on a port, simply transports all packages received on a
specified port through the MPLS-TP tunnel to the other side where a corresponding pseudo-
wire delivers them to the desired port. From an operators perspective the two main advan-
tages are that it is easy to set up more pseudowires to an existing tunnel and, assuming the
MPLS-TP has a protection path, if something goes wrong the pseudowires will be rapidly
switched to the protection path with minimum disturbance to the customer traffic.
When creating a pseudowire the user chooses one pseudowire classification, which deter-
mines what packages will be sent through the pseudowire. The options are an entire port,
packages incoming on port with a specific VLAN tag, or a policy classification. This policy clas-
sification has to be set up before the pseudowire is created but gives the user a large number
of ways to select which packages should be sent trough the pseudowire. It is only possible to
have one pseudowire classifier per pseudowire.
When creating a pseudowire the user can choose a operation mode for the pseudowire. In
tagged or raw mode service delimiting (SD) operations are performed on the packages ac-
cording to Fig. 4 Pseudowire operation modes. in contrast to transparent mode where the
packages are transported without any extra SD tag operation. The user chooses what ether
type (C or S) should be considered as service delimiting and what the egress action should
be. It is important to notice that the egress action is on this pseudowire and not on the corre-
sponding pseudowire on the other end of the tunnel.
In tagged mode the ingress SD-operation is push, which will push the user defined SD tag if ,
and only if, the package has an outer VLAN tag that is of a different ether type then the se-
lected SD tag. Pop and swap will only be applied on a package where the outer VLAN tag is of
the same ether type as the chosen SD tag. The only exception is push on egress (option in
raw mode) which will push a extra SD tag on all packages.

IC-INST-EMXPII Rev A | 2018-12-06 10 (167)

Infinera Proprietary and Confidential
 BACKGROUND

Fig. 4 Pseudowire operation modes.

The pseudowire operation mode does not have to be the same on the corresponding pseudo-
wire on the other side of the tunnel and it is up to the user to make sure that the chosen combi-
nation meets the needs and does not result in package loss.
As an example imagine a tunnel going from site A to site B. Site B wants all packages to have
an outer VLAN tag of a specific ether type and VLAN ID and that site A wants no extra VLAN
tag on its packages. The solution would be to have transparent mode on the pseudowire on
site A and raw mode with the egress action push on the pseudowire on site B. The packages
going from site A into the pseudowire will be unchanged until they come to the pseudowire on
site B where an extra VLAN tag (SD-tag) will be pushed on the packages. In the reverse direc-
tion the packages will be have the SD-tag removed (pop) in the pseudowire on site B and the
transported to site A.

3.2.6 MPLS-TP Quality of Service

Infinera utilizes E-LSP as a base for MPLS-TP QoS. An MPLS tagged packet arriving at an
LSR will be queued with regard to the value of the Traffic class (previously EXP) field in the
LSP label header. The value of the LSP Traffic class field is in turn copied from the Traffic
class of the encapsulated Pseudowire label. As several Pseudowires can be transported with-
in the same LSP, the value of the LSP traffic class will vary depending on what PW is trans-
ported in the individual packets.
Pseudowires are configured with a static traffic class during creation at the ingress LER. The
PW Traffic class value is copied into the LSP Traffic Class field when encapsulated. The same
value is also copied into the PCP field of the backbone VLAN header carrying the MPLS pack-
ets. This allows for similar QoS treatment in both MPLS aware nodes as Layer 2 nodes found
in seamless integration scenarios described in section 3.2.3 MPLS-TP and Layer 2 Switching
Interwork and functional compatibility MPLS-TP and Layer 2 Switching Interwork and function-
al compability.

IC-INST-EMXPII Rev A | 2018-12-06 11 (167)

Infinera Proprietary and Confidential
 BACKGROUND

Infinera LSRs use strict queue mapping derived from the LSP Traffic Class when queuing re-
ceived MPLS packets.

IC-INST-EMXPII Rev A | 2018-12-06 12 (167)

Infinera Proprietary and Confidential
 PRECONDITIONS

4 Preconditions
This section lists the preconditions to consider before installation.

4.1 Safety

Only service personnel with proper knowledge should perform service/maintenance

when the system is in operation mode.

4.1.1 Laser product safety

Statement acc. to IEC/EN 60825-1

INVISIBLE LASER RADIATION. DO NOT VIEW DIRECTLY WITH OPTICAL INSTRU-
MENTS CLASS 1M LASER PRODUCT.
The laser radiation is invisible. Always use a power meter to verify the optical output power.

Statement acc. to IEC/EN 60825-1 (Information for the user)

VIEWING THE LASER OUTPUT WITH CERTAIN OPTICAL INSTRUMENTS MAY POSE AN
EYE HAZARD.
No optical power shall be present at the connector. Authorized personnel can verify the con-
nector surface (ferrule and core) with approved fiber optical microscopes.
Airborne dirt or damaged fiber can be a major source of loss.
The hazard level of the system is laser class 1M according to IEC/EN 60825-1 and IEC/EN
60825-2.

In order to fulfill the Laser Class 1M at system level, only Infinera products is to be used
within the system configurations (excluding OAR-450C and OA 26C, which may be of a
higher Laser Class, depending on configuration).

4.1.2 ESD Safety

Always use an approved ESD wrist strap during installation/maintenance of the system
or when handling ESD sensitive parts (plug-in units etc.). The ESD wrist strap shall be
connected to protective earth.
Use ESD protective bags when transporting the equipment.

4.2 Actions Before Installation

Before installation, configuration and commissioning of the TU it is recommended that the in-
formation required for the different phases is collected.

IC-INST-EMXPII Rev A | 2018-12-06 13 (167)

Infinera Proprietary and Confidential
 PRECONDITIONS

Infinera provides two acceptance report templates:

• Node Acceptance Report
• Network Acceptance Report
Within the Node Acceptance Report the following items can be collected and described:
• Inventory (show delivered inventory e.g. TU, transceivers and their specifications)
• Node Specific Verification (Node specific settings)
• Commissioning Report (shows expected wavelengths and power levels of ports)
• Patch Plan – Client (shows how fibers are connected to customer equipment)
• Patch Plan – Internal (shows how fibers are connected within a node)
• Patch Plan – Peer (shows how fibers are connected between nodes)
• Module Positioning Scheme (shows how HW is to be installed in the node)
Within the Network Acceptance Report the following test templates can be found:
• Traffic Tests
• Protection Tests
• Management Tests
• Alarm Tests
• Network Design
For installation, configuration and commissioning, the information that corresponds to the
node and network acceptance report is needed. This document assumes that this information
is available.
Furthermore, if in-band management channels are used, a DCN Network/node plan is
needed. The plan shall include IP-settings, PPP-links etc. for the nodes. For further informa-
tion refer to Designing DCN Networks Plans in the system manual.
Additionally, it is also necessary to have a transceiver plan (ITU Channels).

4.3 Verify pre-installed SW

The TU is delivered in spare part mode.
The first time a TU is plugged-in to a TM-3000 or TM-3000/II chassis the TU SW that is run-
ning in the node is loaded from the CU.
A label on the ESD bag states the SW version on the TU.
Verify that the TU has the correct SW by reading the label located on the sealed ESD bag.

It is recommended that the CU-system has the latest released SW version. If the CU-system
has an older release than the TU software it will not configure itself properly. Failure to comply
with this recommendation will result in the TU no longer being in spare part mode and the TU
will not be able to communicate with the CU. If this happens see the Spare Part and Mainte-
nance Guide in volume C of the system manual to configure the TU in spare part mode again.

An unsealed ESD bag indicates that the board may not contain the release written on the
label.

IC-INST-EMXPII Rev A | 2018-12-06 14 (167)

Infinera Proprietary and Confidential
 PRECONDITIONS

4.4 CU-System
When the TU is to be installed in a CU-system the requirements are:
• The CU must be of CU-SFP, CU-SFP/II or later.
• The CU must be installed and configured in the system before installing the TU.
• The CU-system must at least have the SW version corresponding to the release when the
Traffic Unit was released. See Table 2 Traffic Units and Software Release. If the TU is in-
serted to a CU system that has an older release than the TU SW it will not be able to com-
municate with the system and can not be configured. When the TU is inserted into a CU
system with a later release it will be upgraded to corresponding release.

The upgrade of the system might affect configuration or traffic on specific boards. For more in-
formation read the upgrade instructions for the relevant release.

EMXP/IIe requires CU-SFP/II or later.

4.5 TU Upgrade
2 lists which releases the Traffic Units were released for the first time. Refer to the Upgrade In-
struction for further information regarding upgrade.

Table 2 Traffic Units and Software Release

Traffic Unit Software Release

10xGbE/10GbE Ethernet Muxponder/II (GBE10–EXMP10/II) R15

22xGbE/10GbE Ethernet Muxponder/II (GBE22–EMXP10/II) R15

8x10GbE Ethernet Muxponder/II (EMXP80G/II R16

4x10GbE Ethernet Muxponder/II (EXMP40G/II) R18

22xGbE/4x10GbE Ethernet Muxponder-IIe (EMXP62/IIe) R21

12x10GbE Ethernet Muxponder-IIe (EMXP120/IIe) R21

8xGbE/4x10GbE Ethernet Muxponder-IIe (EMXP48/IIe) R22

12x10GbE/1x100GbE Ethernet Muxponder-IIe (EMXP220/IIe) R23

24x10GbE Ethernet Muxponder-IIe (EMXP240/IIe) R25

IC-INST-EMXPII Rev A | 2018-12-06 15 (167)

Infinera Proprietary and Confidential
 PRECONDITIONS

4.6 Recommended Tools and Equipment

The following tools are recommended when installing the traffic unit for the first time.
• Laptop including the ENM software, RS232 port (or USB-RS232 converter)
• ENM software available from Infinera TAC Online. Always double-check that the latest ver-
sion of a specific SW release is used.
• Infinera proprietary RS232 adapter (to be used between the computer and the eth cable
during installation).
• Infinera RJ45 to 2.5mm cable for CLI access at installation of CU-less systems.
• Fiber cleaning tool.
• Fiber optical microscope.
• Optical power meter.
• Torx T8, to fasten the boards into chassis.
• ESD wrist strap.
• Board extraction tool. Delivered with the chassis. This tool can only be used in a TM-3000/
II or TM-3000 chassis.
• Patch cords.

IC-INST-EMXPII Rev A | 2018-12-06 16 (167)

Infinera Proprietary and Confidential
 INSTALLING THE TRAFFIC UNIT

5 Installing the Traffic Unit

Use the following procedure to install a traffic unit into a TM chassis. For patch cord cabling re-
fer to the network and site plan valid for the installation.

1. Remove the cover plate and air-stopper in the chassis for the dedicated slot position.

2. Insert the TU according to the module positioning scheme.

3. Fasten the TU with the two screws at the front panel using Torx T8.

All units are hot-swappable, that is, the TU can be inserted/extracted without powering down
the system. Other units in operation will not be affected.

The TUs can be used in:

• Slot 2-17 in a TM-3000 chassis.
• Slot 3-5 in a TM-301 chassis.
• Slot 2 in a TM-102 chassis if the TU is single slot. EMXP40/II can only be used in a TM-102
chassis. EMXP48/IIe cannot be used in a TM-102 chassis

See separate Technical Descriptions and Dimensioning Guidelines for details and restrictions.

5.1 Installing SFP/XFP

The majority of the traffic units (plug-in boards) is intended to have an external SFP and/or
XFP installed. The SFP and XFP are hot-swappable.

Fig. 5 SFP/XFP Installation

Install SFP/XFP

1. The latch shall be locked in position 1.

2. Insert the SFP/XFP in the ports according to the plan.

3. Verify that TX LED is lit/blink (Note: if ALS is enabled on client side the LED will be off).

IC-INST-EMXPII Rev A | 2018-12-06 17 (167)

Infinera Proprietary and Confidential
 INSTALLING THE TRAFFIC UNIT

Remove SFP/XFP

1. The latch should be opened in position 2.

2. Pull the latch towards you.

5.2 SFP/SFP+ extraction tool

To address the limited room around some SFP/SFP+ positions in certain boards, an SFP/SFP
+ extraction tool is provided.

1. Unplug and remove the fibers from the SFP/SFP+ using the broader end of the tool

2. Unplug and pull out the SFP/SFP+ from its cage using the thinner end of the extraction
tool.

IC-INST-EMXPII Rev A | 2018-12-06 18 (167)

Infinera Proprietary and Confidential
 INSTALLING THE TRAFFIC UNIT

5.3 Creating a Traffic Unit in the Node

The first step when configuring the TU is to create an entity in the node. This can be done by
entering the command shown in CLI: Create a TU in Node or by using the ENM GUI. The
boardname subrack and slot values have to be changed to reflect the actual installation.

CLI: Create a TU in Node

• create ::eq::board::<boardname>:<subrack>:<slot>

GUI: Create a TU in Node

• Click the slot where the TU is installed in the Equipment frame to start the initial
configuration, see example below.

IC-INST-EMXPII Rev A | 2018-12-06 19 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6 Configuration
This section explains the steps needed to configure the basic functions in the TU. Remember
to save the configuration afterwards.

6.1 Prerequisites
The chassis and the CU is installed, the node is configured and OSPF is enabled if used.

6.2 ENM GUI

There are two options to manage a Network Element, via a graphical web-based user inter-
face (GUI) or via a Command Line Interface (CLI). See Command Line Interface Guide within
the Installation & Commissioning volume of the System Manual for more details on the CLI
option.
The GUI is launched using an Internet Browser and then entering the IP-address of the NE.
After login the initial view is the Subracks view. The appearance will differ depending on the
chassis and how it is configured. Fig. 6 Subracks – Main view shows the view presented when
logging in to a TM-3000 chassis.

Fig. 6 Subracks – Main view

There are three main areas from which the node can be managed.
The left area is a menu always available in the browser. Clicking the Subracks or the logotype
in the left top corner brings back the starting page where all the traffic units can be seen.

IC-INST-EMXPII Rev A | 2018-12-06 20 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

The top area is updated dynamically and shows the number of alarms and the highest severity
among them.
The main area is the equipment area. This area is changed according to selections made from
other areas.
Some items will change color to reflect alarm status, for example the fan and power areas.
When hovering over a plug-in unit, the CLI name will appear as a tool-tip. For more information
on items and menu links, see section 6.2.1 Subracks view.

IC-INST-EMXPII Rev A | 2018-12-06 21 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.2.1 Subracks view

This section gives an overview of the information areas as well as clickable areas in the main
window.

Fig. 7 Information and Configuration areas in Subracks view

The Chassis tab indicates the chassis type. If several chassis are connected into a single NE
entity, the included chassis will be found under separate tabs. A Control Unit (CU) is required
to connect multiple chassis into one NE. It is not possible to combine multiple TM-102II, TM-
102, TM-101 chassis in this way since a CU is not used in these type of configurations.
Board Missing is shown if a slot is not equipped with a unit type it has been configured for.
Unexpected is shown if a slot is equipped with another unit type than it has been configured
for.
Not Configured is shown for slot that is equipped with a unit but has not yet been configured.
It is possible to configure a slot before a unit is inserted. When the slot is configured the slot
will show Board Missing until the correct unit type is inserted.
Save changes color when there are unsaved changes in the configuration.
If there are unsaved changes a warning is presented upon logout from ENM where it is possi-
ble to save, leave unsaved or cancel the logout. All unsaved configurations will be lost if the
node is rebooted.
Non used interfaces on traffic units are indicated with a transparent mask.

IC-INST-EMXPII Rev A | 2018-12-06 22 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.2.2 Verbose mode

The ENM GUI can be set in two modes where different depth of information is presented.
Clicking Settings in the lower right corner enables changes to the browser view.
For normal operation of a NE, the browser shall be set in Verbose mode off. This presents
the most relevant information and settings, and provides a more compact display of the differ-
ent windows.

Fig. 8 Verbose mode

The default setting for Verbose mode is off. Select Settings and Verbose mode and click
OK to activate Verbose mode. Some configurations can only be done with the verbose mode
activated, this will vary from unit to unit.
It is recommended to deactivate verbose mode when necessary configurations have been
done.

IC-INST-EMXPII Rev A | 2018-12-06 23 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.2.3 Board settings

When clicking on the lower part of a configured board a number of menu tabs containing infor-
mation and configuration parameters are shown.

Fig. 9 Board view

The information is structured in two levels having a set of main menu tabs and sub-menu tabs.
Some views have a series of buttons at the bottom.

Fig. 10 ENM buttons

Apply Performed changes are activated (note that the change is not saved).

Clear Clear all unsaved changes on the page.

Multi Set Enables setting of multiple parameters.

View Table All related and relevant data is listed in a table format.
Help Help texts for the configuration parameters.

Create Opens a Create dialog for adding new configuration objects in the current
view.
Delete Deletes selected configuration objects.

Refresh Updates the page.

6.2.4 Network Element Parameters

When a node is to be commissioned for the first time, a number of configuration steps must be
taken on both NE and board level. To ease this process a Getting started guide presents a ser-
ies of steps where configuration data is entered.

IC-INST-EMXPII Rev A | 2018-12-06 24 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

The NE related configuration is activated via the menu item Getting started. Typical NE re-
lated data is:
• DNS and Node Name
• IP address
• Default Gateway
• Date and time (NTP)
• SNMP Traps
• Passwords
• Radius and Tacacs+ settings
• Backup and upload settings
The entered values are saved and activated when clicking Apply after the last step. The pa-
rameters can also be set using the menus and tabs under the Management network menu
item.
The configuration parameters related to the boards is set when creating a board.

6.3 Enhanced GUI features

From R24, a new enhanced overview user interface is introduced for certain boards. The main
features are described below.

6.3.1 Accessing single entries

Clicking a tab with more than one entry will open an overview table containing the most vital
data for all entries as well as any active alarms on each entry. To access a single entry, simply
click on the entry name. The entry data is presented in a separate frame.

Fig. 11 Access a single entry by clicking on the name of the entry.

6.3.2 Filtering overview tables

When a tab contain many entries, it can be useful to filter the entries to be shown in the
overview.

IC-INST-EMXPII Rev A | 2018-12-06 25 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

1. To start filtering, simply start typing in the filtering field.

2. Any entry that has not an attribute value matching the string entered in the filtering field
will now be removed from the overview.

3. To remove the filter, erase the text in the filtering field.

The entered string will be matched against all attributes in an entry, not only attributes shown
in the overview.

6.3.3 Sorting overview tables

When a tab contain many entries, it may be useful to adjust the sorting order to get a better
visibility.

1. Click the header of the table column that should serve as a key for the sorting.
The items in the table will be sorted alphanumerical based on the key. An arrow in the ta-
ble header indicates the sorting order.

2. Click the table column header one more time to reverse the sorting order.

IC-INST-EMXPII Rev A | 2018-12-06 26 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 12 Sorting in overview tables

6.3.4 Multiset in overview tables

It is possible to do a multiset of one or several attributes in multiple entries from the overview
table.

1. Select the entries to be edited by clicking the checkbox to the far left in the entry table row
or select all visible entries by clicking the checkbox to the far left in the table header.

2. Set the new desired value on all selected entries by editing the fields in the bottom table
row. Adjusted attributes will be highlighted with yellow.

3. Click Apply to change all selected items or Clear to cancel the changes.

Fig. 13 Multiset of an attirbute on selected entries

Multiset is only possible on visible entries. Entries that are not shown, due to filtering or paging
functions, will not be replaced even if the top checkbox is selected.

IC-INST-EMXPII Rev A | 2018-12-06 27 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.3.5 Create and Delete entries in overview tables

Dynamic entries can be created or deleted from the overview tables.

Create entries in overview in tables

1. Click Create in the bottom row and enter required data.

Delete entries in overview tables

1. Select the entries to be deleted by clicking the checkbox to the far left in the entry table
row or select all visible entries by clicking the checkbox to the far left in the table header.

2. Click Delete in the bottom row to delete the selected entries.

3. User confirmation may be needed before the delete operation is performed.

Fig. 14 Deletion / creation of selected entries

IC-INST-EMXPII Rev A | 2018-12-06 28 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.4 Layer 1 Port Configuration

This section includes instructions on how to configure the EMXP/II ports layer 1 properties
from both ENM and CLI.

Fig. 15 Port Tab L1 sub tab where layer 1 properties of the selected port are shown and configured

6.4.1 Setting Expected Frequency — Tunable XFP/SFP+

When a tunable XFP or SFP+ is inserted in a line port it will not start to transmit before a valid
frequency is set.

CLI: Set Expected Frequency

• set ::client::if::client:subrack:slot:txPort-rxPort::
expectedFrequency chXYZ

GUI: Set Expected Frequency

• Select Subracks->Actual Board->Port tab-> L1 tab. Click on a client port from the
Name list. Select a value from the Expected Frequency drop-down list.

6.4.2 Setting Physical Media

The physical media configuration needs to match the current transceiver in the designated
port. There are two different options, electrical and optical.

IC-INST-EMXPII Rev A | 2018-12-06 29 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Set Physical Media

• ::client::if::client:subrack:slot:txPort-rxPort::configureTrxMode

• Follow the instructions on screen.

GUI: Set Physical Media

• Select Subracks->Actual Board->Port tab-> L1 tab. Click on a client port from the
Name list. Click Change transciever mode

6.4.3 Changing Signal Format

The signal format can be changed between Fast Ethernet and Gigabit Ethernet on Gigabit
Ethernet ports where an optical transceiver is configured. 10/100/1000 BASE-T is available
when an electrical transceiver is configured. On EMXP/IIe Traffic Units 10G interfaces can be
configured with either the lan10GbE or the OTU2e signal format.

GUI: Changing Signal Format

1. Select Subracks->Actual Board->Port tab-> L1 tab. Click on a client port from the
Name list. Click Change signal format (and mode)

CLI: Changing Signal Format

1. ::client::if::client:subrack:slot:txPort-rxPort::configure

2. Follow the instructions on screen. Valid Signal formats for the EMXP/II are
fastEthernet, GbE and ethernet , additionally otu2e and lan10GbE is available
on 10G interfaces on the EMXP/IIe traffic units.

IC-INST-EMXPII Rev A | 2018-12-06 30 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.4.4 Setting Near End Loopback

Near end loopback can be enabled or disabled in order to loopback incoming frames at any
port that supports near end loopback.

GUI: Setting Near End Loopback

1. Select Subracks->Actual Board->Port tab->L1 tab. Click on a client port from the
Name list. Select a desired value from the Near end loopback drop-down list.

CLI: Setting Near End Loopback

1. set ::client::if::client:subrack:slot:txPort-rxPort::
nearEndLoopback <value>
valid configurations for nearEndLoopback are enabled and disabled.

Please note that the Near end loopback is not supported on 100G interfaces. It is however
possible to loop back the traffic using the Port Redirect action in the policy framework de-
scribed in 6.8.2 Creating Actions

6.4.5 Setting Far End Loopback

Far end loopback can be enabled or disabled in order to loopback frames that has traversed
the switch core and are about to be transmitted at any EMXP port.

GUI: Setting Far End Loopback

1. Select Subracks->Actual Board->Port tab->L1 tab. Click on a client port from the
Name list. Select a desired value from Far end loopback attribute drop-down list.

CLI: Setting Far End Loopback

1. set ::client::if::client:subrack:slot:txPort-rxPort::
farEndLoopback <value>
Valid configurations for farEndLoopback are enabled and disabled.

6.4.6 Configuring FEC Type

On the 10G interfaces of the EMXP/IIe traffic units FEC type can optionally be configured if
the signal format is configured to OTU2e. Valid FEC types for the EMXP/IIe TUs are
disabled, gFec, superFecI4 and superFecI7 each with different coding gain and added
latency.

GUI: Configuring FEC Type

1. Select Subracks->Actual Board->Port tab->L1 tab->. Click on a client port from the
Name list. Select a desired FEC type in the FEC Type drop-down list click apply
button on the lower part of the screen

IC-INST-EMXPII Rev A | 2018-12-06 31 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Changing Signal Format

1. set ::client::if::client:subrack:slot:txPort-rxPort::fecType
<desired FEC type>

Please note that the FEC attributes are hidden if the signal format is not configured to OTU2e.

Changing FEC type on one 10 G port will affect all other 10 G ports as well.

6.4.7 Configuring Signal Degrade Threshold

The 10G interfaces of the EMXP/IIe and PTIO10G traffic units can optionally utilize FEC to
provide coding gain. The post-FEC bit error rate is estimated using the estimated pre-FEC bit
error rate. The signal degrade threshold provides a threshold when the signal degrade alarm
should be raised because of high bit error rate. Valid signal degrade thresholds for the TUs
are rxBerLevel1, rxBerLevel2, rxBerLevel3 corresponding to bit error levels of 1E-12,
1E-13 and 1E-15.

GUI: Configuring Signal Degrade Threshold

1. Select Subracks->Actual Board->Port tab->L1 tab. Click on a client port from the
Name list. Select a desired signal degrade threshold in the Signal Degrade
Threshold drop-down list click apply button on the lower part of the screen

CLI: Configuring Signal Degrade Threshold

1. set ::client::if::client:subrack:slot:txPort-rxPort::
signalDegradeThreshold <desired signal degrade threshold>

Please note that the signal degrade threshold attribute is hidden if the signal format is not con-
figured to OTU2e.

6.4.8 Configuring Optical Layer Mapping

Depending on the number of optical lanes on the CFP/CFP2, the correct setting needs to be
set on the interface. A coherent CFP/CFP2 is using one optical carrier, while SR-10/LR-10
and LR-4 are using ten and four optical carriers respectively.
Optical Layer Mapping is only applicable for 100G interfaces.

GUI: Changing Optical Layer Mapping

• Select Port tab->L1 tab. Select the 100G client port from the Name list. Select a desired
Expected optical layer mapping from drop-down list and press Apply.

IC-INST-EMXPII Rev A | 2018-12-06 32 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 16 Configure expected optical layer mapping

CLI: Configuring Optical Layer Mapping

1. set ::client::if::client:subrack:slot:txPort-rxPort::
expectedOpticalLayerMapping <desired optical layer mapping>

The individual optical carriers of the CFP are monitored separately and presented per lane in
Lane tab under the same Port tab. E.g. Rx power level, Rx sensitivity, and transmitted wave-
length per lane.

Fig. 17 Showing attributes per lane in the Lane tab

Please note that the expected optical layer mapping and actual optical layer mapping attrib-
utes are hidden if the interface is not 100G.

The rx power level presented in the L1 tab for the 100 G port is taken from the lane with the
lowest rx power. Measuring rx power on the 100 G port with an optical power meter will show
the accumulated optical power value for all lanes.
The tx power level presented in the L1 tab for the 100 G port is taken from the lane with the
highest tx power. The tx power value is not presented per lane.

IC-INST-EMXPII Rev A | 2018-12-06 33 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.5 Layer 2 Port Configuration

This section includes instructions on how to configure the EMXP/II ports layer 2 properties
from both ENM and CLI.

Fig. 18 Port Tab L2 sub tab where layer 2 properties of the selected port are shown and configured

6.5.1 Setting Auto Negotiation

EMXP/II supports auto negotiation of port speed in 10/100/1000 Mbit/s BASE-T and FE/GBE
BASE-X. Only the full duplex alternatives of the port speeds are supported by the EMXP/II.
A new auto negotiation sequence can be initialized by the EMXP/II in ENM.

GUI: Set Auto Negotiation

• Select Subracks->Actual Board->Port tab->L2 tab. Click on the client port from the
Name list. Select a value from the Auto negotiation mode drop-down list and press
Apply.

CLI: Set Auto Negotiation

• set ::mes::port::port:subrack:slot:txPort-rxPort::
autoNegotiationMode
Valid settings for autoNegotiationMode are off or on.

IC-INST-EMXPII Rev A | 2018-12-06 34 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.5.2 Setting Port Mode

EMXP supports three predefined port modes, UNI, UNIMUX and NNI. See the Technical De-
scription for more information.

GUI: Setting Port Mode

1. Select Subracks->Actual Board->Port tab->L2 tab. Click on the client port from the
Name list. Select a mode from the Mode drop-down list and click Apply.

CLI: Setting Port Mode

1. set ::mes::port::port:subrack:slot:txPort-rxPort::mode portmode

2. Valid settings for portmode are nni, uni and uniMux.

6.5.3 Setting Native VLAN ID

The port requires a native VLAN ID which is set to 0 by default. The native VLAN ID can vary
over the full range of available VLAN IDs which are not used by other functions such as ERP.

GUI: Setting Native VLAN ID

1. Select Subracks->Actual Board->Port tab->L2 tab. Click on the client port in the
Name list.

2. Enter the Native VLAN id and click Apply

CLI: Setting Native VLAN ID

1. set ::mes::port::port:subrack:slot:txPort-rxPort::nativeVlanId
<VLANID>

6.5.4 Setting Native Priority

The port requires a native VLAN priority which is by default set to 0. The native VLAN priority
can be varied between 0-7.

GUI: Setting Native Priority

1. Select Subracks->Actual Board->Port tab->L2 tab.Name list.

2. Enter the Native VLAN Priority and click Apply

CLI: Setting Native Priority

1. set ::mes::port::port:subrack:slot:txPort-rxPort::
nativeVlanPriority <pcp>

IC-INST-EMXPII Rev A | 2018-12-06 35 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.5.5 Creating Link Aggregation Group (LAG)

The EMXPs support the use of LAGs as defined by IEEE802.1AX. The implementation is
based around having a LAG master port and a series of LAG slave ports, the slave ports will
inherit some basic properties from the LAG master port. Some properties have to be shared
amongst all the LAG members, for the LAG to work in a symmetric manner.
The software will make sure that the required properties spread from the LAG master port to
the LAG slave port. These properties will be grayed out on the LAG slaves and the only way to
configure them will be through changing the configuration of the LAG master port.
If the selected master port is used for a MEP or ERPv2, then that MEP or ERP will be migrated
to use the LAG. It is not allowed to include slave ports having MEPs or ERPv2.

GUI: Creating LAG

1. Select Subracks->Actual Board->Port tab->L2 tab. Click on the client port in the
Name list.

2. Click the Associate LAG button .

3. Select available slave ports to be added to the master port in Associate LAG pop-up
window. The number of slave ports has to be between 0 and 7. If no slave ports are
chosen, the LAG will comprise the master port only, i.e. an individual link. The lag has
to be given a unique identifier as well as a hash algorithm to use for load distribution
over the physical links. The hash algorithm makes sure that no frame reordering in a
session will occur while load balancing the links. Upon creation it is also possible to
enable and configure LACP (Link Aggregation Control Protocol). N+N protection can
be configured using the “LACP maximum number of active links” attribute.

IC-INST-EMXPII Rev A | 2018-12-06 36 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 19 Associate LAG dialogue window

Identifier A unique identifier for the LAG.

Hash Algorithm MAC: Enable MAC hashing.

IP: Enable IP hashing.
VLAN: Enable VLAN hashing.
MPLS: EMXP/II: Based on up to two MPLS labels. EMXP/IIe: Based on
up to three MPLS labels and IPv4 and IPv6 headers in IP-MPLS packets.
AUTOMATIC: The fields selected for hashing is depending on ethertype.
IPv4/IPv6 packets uses the IP src/dst addresses and TCP/UDP ports,

IC-INST-EMXPII Rev A | 2018-12-06 37 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

MPLS packets uses labels and the remaining ethertypes use VLAN ID
and src/dst MAC addresses (Default value).

LACP enable Off: (Default) Disable LACP (Link Aggregation Control Protocol) for the
LAG i.e. configure a static LAG.
Passive: Enable passive LACP for the LAG. LACP will only transmit
frames upon reception of LACP frames. This means that the remote sys-
tem should be configured as LACP active.
Active: Enable active LACP for the LAG. LACP will periodically transmit
frames regardless of how the remote system is configured.

System priority Set the priority of the LAG.

LACP period Slow: (Default) Configure LACP for slow transmission. The transmission
interval is 30 seconds with a long timeout of 90 seconds.
Fast: Configure LACP for fast transmission. The transmission interval is 1
second with short timeout of 3 seconds.
LACP maximum If the maximum number of active links equals to the number of ports con-
number of figured in the LAG, the load is distributed on all links in the LAG. If the
active links maximum number of active links is less than the number of ports config-
ured in the LAG, traffic is carried by the primary link(s) while the other(s) is
used as a standby link(s) in case of failure on the primary link. Port priority
is used to determine the active links.
LACP minimum If the number of links that can be activated is less than this value, all links
number of are deactivated (the traffic forwarding is disabled).
active links
LACP port Set the priorities of the member ports. A lower numerical value indicates a
priorities higher priority.

CLI: Creating LAG

1. ::mes::port::port:subrack:slot:txPort-rxPort::associateLag

2. Follow the instructions on screen and enter values for Identifier, hash algorithm and
slave. Valid hash algorithm options are mac, ip , vlan, mpls and automatic. Valid
slaves are the ports on the same TU having the same signal format as the master
port.

GUI: Configuring LAG

After creating a LAG, the current configuration can be viewed and modified under
Subracks->Actual Board->Port tab->L2 tab->LAG . Click on the LAG in the Name list.

Fig. 20 LAG configuration tab.

IC-INST-EMXPII Rev A | 2018-12-06 38 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

• The hash algorithm is a board level configuration. Changing hash algorithm on one LAG will affect all LAGs on
the board.

• ERPv1 and egress policies are not supported on LAGs.

• Ports with different port speed cannot be a part of the same LAG and no more than 8 ports can belong to a sin-
gle LAG.

• If Management VLAN function is enabled on master port of a lag, slave ports of the lag will inherit Management
VLAN function from the master port. However the Management Vlan function on slave ports will not take effect
on TU-system until CU-system is rebooted. More specific description of enabling Management VLAN function
is detailed in6.20 Mgmt VLAN Configuration.

6.5.6 Configure LACP

If a LAG is LACP enabled it is possible to see each port’s individual LACP state and
configuration.

GUI: Configuring LACP

Navigate to Equipment->Actual Board->Port tab->L2 tab->LACP list. Click on the LACP

object in the Name list. Actual Port.

Fig. 21 LACP port overview tab.

Name The management name of the LACP group (lacp:[subrack]:[slot]:[LAG

identifier]:[LACP port]).

LAG name A unique name of the LAG.

LAG ID The LAG ID is a unique identifier for each LAG. The LAG ID is constructed
from the following parameters for each of the communicating systems.
— The system identifier
— The operational key assigned to the ports in the LAG
— The port identifier, if the link is identified as an individual link
The general form of the LAG ID is [SKP, TLQ] where:
— S and T are system identifiers
— K and L are the operational keys assigned to a LAG by S and T,
respectively.
— P and Q are the port identifiers of the attached ports if the LAG com-
prises one individual link and zeroes if the LAG comprises one or more ag-
gregatable links.

Port priority Set the port priority. A lower numerical value indicates a higher priority.

IC-INST-EMXPII Rev A | 2018-12-06 39 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Selected Unselected: No aggregator is currently selected.

Selected: The selection logic has selected an appropriate aggregator.
Standby: Although the selection logic has selected an appropriate aggre-
gator, restrictions currently prevent the port from being enabled as part of
the aggregation (link protection mode).

LACP receive Current: A LACPDU has been received.

state
Expired: If no LACPDU is received before the Rx timer expires, the re-
ceive state is set to expired. The Rx timer is equal to the transmission in-
terval of the remote system in the LAG.
Defaulted: If no LACPDU is received while the port is in expired state, the
port is set to defaulted. The expired time interval is equal to the transmis-
sion interval of the remote system times 3, i.e. 3 seconds for fast periodic
and 90 seconds for slow periodic.

LACP transmit SlowPeriodic: Transmission interval is set to 30 seconds.

state
FastPeriodic: Transmission interval is set to 1 second.
LACP mux state Detached: The port is not included in the LAG.
Attached: The port is attached to the LAG.
Collecting/Distributing: The port is attached to the LAG and is forward-
ing traffic.

CLI: Configuring LACP

1. Navigate to ::mes::lag::lag:subrack:slot:unique_lag_name

2. Write set parameter value. Valid LACP parameters are lacpEnabled (off/active/
passive), lacpPeriod (slow/fast), lacpMaxNrOfActiveLinks (integer) and
lacpMinNrOfActiveLinks (integer).

3. It is now possible to configure the port priority by navigating to ::mes::lacp::

lacp:subrack:slot;unique_lag_name:txPort-rxPort and using the set
command.

Configuring n+n protection:

1. Create a LAG with up to 8 member ports and enable LACP .

2. Set LACP Maximum Number of Active Links to the amount that should carry traffic
under normal circumstances, the rest will be used as standby links.

3. Set the System priority. The port priorities of the system with higher priority will be used
when deciding which port will be forwarding traffic and which port will be standby.

4. Set the Port priority of the member ports. The port with the higher priority will forward
traffic and the other port will act as a hot standby.

IC-INST-EMXPII Rev A | 2018-12-06 40 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

A lower numerical value means a higher priority. As both ends of the LAG must agree on the
same links, the Port Priorities of the system with the highest System Aggregation Priority is
used. This priority first compares the System Priority values and then the System ID which is
the MAC address used by the LAG in LACPDUs.

6.5.7 Creating Shapers

A shaper must be configured with a minimal and maximal bit rate. A shaper will smooth out
bursts by utilization of the upper limit and prevent starvation by the lower limit bit rate.

GUI: Creating Shapers

1. Select Subracks->Actual Board->Port tab->L2 tab. Select a port in the Name list.

2. Click Associate Shaper Button in the lower part of the attribute list..

3. Add an Identifier and set the Minimum and Maximum rate together with the Queue.
The Minimum and Maximum rate is dependent on the port and port speed currently
configured. The Existing drop-down list will allow linking an already configured shaper
to the selected port. This does not mean that the ports will compete for the same band-
width, but rather each port having its own shaper which share properties with another
shaper If an existing shaper is selected no further configuration of the shaper can be
done. Queue denotes on which queue on the currently selected port the shaper will be
associated to.

CLI: Creating Shapers

1. ::mes::port::port:subrack:slot:txPort-rxPort::associateShaper

2. Follow the instructions on screen. Valid options for Shaper are new, or the name of an
already configured shaper. A valid Identifiers is a TU unique string. Valid minimum and
maximum rates depend on the port speed of the current port.

6.5.8 Creating Policers

Policers also called port policers are configured on a port level. The port policer should not be
mixed up with the MEF policer which is configured through the policy framework.

IC-INST-EMXPII Rev A | 2018-12-06 41 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating Policers

1. Select Subracks->Actual Board->Port tab->L2 tab. Click on a port in the Name list.

2. Click the Associate policer near the end of the attribute list.

3. Add an Identifier and set the Rate, Burst size and Type in the Associate policer
dialogue.
The desired rate is set with a resolution of 153 kb/s. The Existing drop-down list will
allow linking an already configured policer to the selected port. This does not mean
that the ports will compete for the same bandwidth, but rather each port having its own
policer which share properties with another shaper If an existing policer is selected no
further configuration of the policer can be done.
Typeindicates if the policer should police different combinations of broadcast frames,
multicast frames and/or unknown unicast frames. The option All will make the policer
police all frames including unicast.

CLI: Creating Policers

1. ::mes::port::port:subrack:slot:txPort-rxPort::associatePolicer

2. Follow the instructions on screen. Valid options for Policer are new, or the name of an
already configured policer. The rate should not be greater than the port speed.

Burst size should be larger than the MTU.

For policer types broadcastMulticast, broadcastUnknownunicast,

broadcastMulticastUnknownunicast and all, the rate will be used for each frame type inde-
pendently. For example, A policer on broadcastMulticast with the rate 20 Mb will allow 20 Mb
of broadcast traffic and 20 Mb of multicast traffic.

Unicast frames are considered unknown when the destination MAC address is not in the MAC
table.

6.5.9 Configure Port Mirroring

The mirror function allows overriding the VLAN Maps and Trust in the switch block. This func-
tion will copy the traffic on either ingress, egress or a combination of both on a mirrored port.
The copied frames will be egress frames on the mirror port.
This function is designed to be of use when troubleshooting an configuration without discon-
necting any live traffic.
Note that the mirrored traffic will be subjected to the mirror port egress port mode and its QoS
profile. So in order to make sure that the copied frames are the same on the mirrored port they
should have the same configuration.
Also note that only one mirror can be active at a single TU at any given time.

IC-INST-EMXPII Rev A | 2018-12-06 42 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Configure Mirroring

1. Select Subracks->Actual Board->Port tab->Mirror tab. Click on a mirror object in

the Name list.

2. Click a Configure destination. The port associated with selected mirror object
becomes the mirrored port.

3. In the Port drop-down menu choose to which port the mirrored port will be mirrored to.
Only one port can be selected as a mirror port. The Direction drop-down list selects
whether ingress traffic, egress traffic or if all traffic should be mirrored to the mirror port.
If an destination port is already set and it shall be changed the “Override old
destination port” tick-box needs to be ticked.

CLI: Configure Mirroring

1. ::mes::mirroring::mirror:subrack:slot:txPort-rxPort::
configureDestination

2. Follow the instructions on screen. Valid options for Direction are both, egress, and
ingress.

IC-INST-EMXPII Rev A | 2018-12-06 43 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.5.10 Setting Port Trust

In order for the switch block to forward a frame it has to be tagged and have a VLAN ID which
has a corresponding VLAN map. The VLAN map also states a valid TPID. Alongside with the
VLAN map there is also port trust. Port trust allows the creation of E-Tree and other flexible
layer two layouts in the EMXP switch core.
If a port trusts another port it can send its ingress traffic to this port if allowed by the VLAN
map. If a port distrusts another port it will still egress the traffic sent from this port.
For ease of use during the installation, an option for changing the default setting of port trust is
added in the GUI dialog. From a separate tab in the dialog, it is possible to set the port trust
defaults for all ports to either trust or untrust all other ports.

GUI: Configure Port Trust

1. Select Subracks->Actual Board->Port tab->L2 tab->Port drop-down list.

2. Click Configure Trusted Ports.

3. Enter trusted ports as a comma separated list of tx-ports, ex: ‘ 1,3,9–13’, or none, —,
all or lag-name. LAG slaves will be trusted only if its LAG master is trusted.

CLI: Configure Port Trust

1. ::mes::port::portsubrack:slot:txPort-rxPort::
configureTrustedPortmask

2. Enter trusted ports as a comma separated list of tx-ports, ex: ‘ 1,3,9–13’, or none, —,
all or lag-name. LAG slaves will be trusted only if its LAG master is trusted.

It is not possible to configure trust for slave ports of a LAG, the input will be ignored and they
will inherit the trust settings from the LAG master port.

IC-INST-EMXPII Rev A | 2018-12-06 44 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.5.11 Enabling LLDP

EMXP’s supports LLDP on all ports. See Technical Description for more information.

GUI: Enabling LLDP

1. Select Subracks->Actual Board->Port tab->LLDP tab. Select a port by clicking on it

in the Name list. Select mode txAndRx from the Admin Status drop-down list and
click Apply.

CLI: Enabling LLDP

1. set ::lldp::agentConfig::lldp:subrack:slot:txPort-rxPort::
adminStatus txAndRx

6.5.12 Viewing LLDP information

GUI: Viewing LLDP neighbor information

1. Select Subracks->Actual Board->Port tab->LLDP Neighbor tab. All detected LLDP

neighbors on enabled LLDP ports will be presented in an overview list with basic
LLDP data.

2. Click on an entry in the Name list to view a more comprehensive list of received LLDP
neighbor info.

Fig. 22 LLDP neighbor tab

GUI: Viewing Common LLDP agent data

1. Select Subracks->Actual Board->Port tab->LLDP tab.

2. Click on an entry in the Name list to view more information on a specfic port/agent, along
with LLDP statistics for that port/agent.

IC-INST-EMXPII Rev A | 2018-12-06 45 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 23 LLDP agent/port configuration and statistics

CLI: Viewing LLDP agent, statistics and neighbor data

1. ::lldp::agentConfig::

2. ::lldp::neighborSystem::

3. ::lldp::statistics::

IC-INST-EMXPII Rev A | 2018-12-06 46 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.6 VLAN Configuration

This section includes instructions on how to configure the EMXP/II VLAN operations and
VLAN maps

6.6.1 Creating VLAN Maps

VLAN maps defines which ports that are members of certain VLANS. The VLAN map also
contains information of the valid TPID of the VLAN map and if this VLAN should learn MAC
addresses.
MAC learning enables the EMXP to forward traffic according to a learned MAC table on this
certain VLAN instead of broadcasting on all VLAN ports.
For more information see Technical Description EMXP/II.

It is not possible to configure trust for slave ports of a LAG independently of the LAG master
port.

IC-INST-EMXPII Rev A | 2018-12-06 47 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Configure VLAN Maps

1. Select Subracks->Actual Board->VLAN tab->VLAN tab.

2. Click Create.

3. Enter VLAN ID for VLAN to be created and configured

4. Select the ports to be included in the Create VLAN dialogue. Some ports may be
unavailable since LAG slaves can only be in a VLAN map if the LAG master is
included.
In case a VLAN map is created for usage in an ERPv2 ring, the ring itself can be se-
lected. The checkboxes for the two ports used in the ERPv2 ring are then automati-
cally filled in.

5. Select if MAC addresses learning should be enabled on the VLAN in the Learning
drop-down list.

6. If Learning is set to on, the maximum number of MAC address entries for this VLAN
can be set in the MAC address limit field.

7. Select the ether type of the VLAN map. If the TPID of the outer VLAN tag does not
match the configured ether type in the VLAN map the frame will be dropped.

8. Select Trust ports if all member ports of the VLAN map automatically should be
configured to with mutual trust.

9. A description for the VLAN map can be added in the description field. (Optional)

IC-INST-EMXPII Rev A | 2018-12-06 48 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Configure VLAN Maps

The VLAN map is created from one of the member ports by the associateVlan com-
mand. The rest of the member ports are added with the configurePortMask command
on the vlanMap object.

1. ::mes::port::port:subrack:slot:txPort-rxPort::associateVlan

2. Follow the instructions on screen for the associateVlan command

3. ::mes:vlanMap::map:subrack:slot:VLANID::configurePortmask

4. Follow the instructions on screen for the configurePortMask command. Enter yes
for the ports to be added.

MAC address limit feature is only supported on EMXP/II and EMXP/IIe units

6.6.2 Creating VLAN Rules

VLAN rules can be defined on both ingress and egress and can do a variety of VLAN tag oper-
ations. In the ingress direction, the outer VLAN tag can be swapped or an additional VLAN tag
added. In the egress direction, the outer VLAN tag can be removed together with an option of
rewriting the inner VLAN tag or both inner and outer VLAN tags can be removed. If more free-
dom in the VLAN operations are needed, please see 6.8 Policies Configuration.

IC-INST-EMXPII Rev A | 2018-12-06 49 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating VLAN Rules

1. Select Subracks->Actual Board->VLAN tab->Rule tab.

2. Click Create near the bottom of the page.

3. Select the port the rule is to be applied to in the Create Rule dialogue. The outer
VLAN ID designates the VLAN ID of the outer VLAN tag of frames that will be
subjected to this rule.

4. Select the desired priority assigment for the Rule (Ingress or Egress VLAN
rewrite). Ingress rules support the operations Push and Swap, while egress rules
support PopSwap, Pop and PopPop.

5. Select the desired priority assigment for the Rule (Set or Copy). Copy will make this
VLAN rule copy the PCP from the frame while set will set a new statical PCP of the
frame.

Port Port or LAG that the VLAN rule shall be applied on.

Outer VLAN ID The VLAN ID that the VLAN rule shall be applied on. Double tagged pack-
ets can only have a VLAN rule applied on the outer VLAN tag.

Type Defined wther the VLAN rules is applied onto incoming or outgoing
packets.

Operation The type of VLAN operation that the VLAN rule shall perform.

New VLAN Id VLAN ID to swap to or push onto the the existing tag.

Priority Defines what to do with the priority value of the new VLAN tag when push-
assignment ing a new tag onto the packet. The priority value can either be copied from
the inner VLAN tag, or statically assigned a value between 0 and 7.

IC-INST-EMXPII Rev A | 2018-12-06 50 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

On EMXP/II the priority depends on the QoS egress color encoding logic when pushing a new
VLAN tag. Egress PCP or DEI encoding must be enabled for the PCP to be set. For example
to set egress PCP to 8P0D.
On EMXP/II there is a limitation in the egress VLAN rewrite function when doing “pop&swap”
namely:
When the inner VLAN ID is swapped to the new VLAN ID(and new priority is set) the DEI/CFI
bit will always be set to 0.

CLI: Creating VLAN Rules

1. ::mes::port::port:subrack:slot:txPort-rxPort::configureTagRule
or
::mes::lag::lag:subrack:slot:identifier::configureTagRule

2. Follow the instructions on screen.

IC-INST-EMXPII Rev A | 2018-12-06 51 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.7 Multicast Configuration

This section describes how to enable IGMP snooping, and how to configure static multicast
forwarding entries in ENM and CLI. More information about multicast forwarding can be found
in Technical Description EMXP/II.

6.7.1 Configuring a Multicast Enabled Interface

Multicast enabled interfaces allow IGMP snooping assisted multicast forwarding traffic
grooming.

GUI: Configure Multicast Interface

• Select Subracks->Actual Board->Multicast tab->If tab. Click on a port in the Name list.

• Configure the parameters described below.

Protocol Off (default): disables multicast forwarding rules on the interface and all in-
coming traffic is treated in the same way as unicast traffic.
IGMP: enables IGMP snooping on the interface and enables the multicast
forwarding rules on ingress traffic.

Router enable Enabled: Ingress IGMP queries will be accepted and IGMP membership
reports will be forwarded to the interface.
Disabled (default): Ingress IGMP queries will be dropped and IGMP mem-
bership reports will not be forwarded to the interface.

Fast Leave Enabled (default): The interface will consider IGMPv2 fast leave mes-
sages and drop the multicast subscription instantaneous.
Disabled: The interface will not consider IGMPv2 fast leave messages
and subscriptions has to age out before they are dropped.

Robustness Integer ranging from 1-7 (default 2) : The robustness parameter effectively
decides the age out period of an IGMP multicast subscription. The robust-
ness parameter indicate how susceptible the network is to packet loss.
IGMP snooping can maintain multicast forwarding even if robustness mi-
nus one IGMP join packets are lost.
The robustness factor scales the age out timer according to:
Age out = 10 s + Robustness x 120 s

Reserved Range Enabled (default): The interface will maintain transparency in the 224.0.0.
Flooding X address range.
Disabled: The interface will not be transparent in the 224.0.0.X address
range.

Maximum Integer ranging from 0-1000 (default 1000): Limit for the maximum number
number of of members allowed for a port. The limit prevents new dynamic members
members to be added (if over the set limit), existing members are not removed. Stat-
ically provisioned entries are included in the count, however it is always
possible to add new static entries as long as the system limit (1000) for
the board is not reached.

IC-INST-EMXPII Rev A | 2018-12-06 52 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Configure Multicast Interface

1. ::multicast::if::subrack:slot:

2. Set values for the following parameters: protocol, robustness, membersMax and
routerEnable See the list above for available values. For example: set protocol
igmp

6.7.2 Configuring a Static Multicast member

There are several ways to access the window that allows static configuration of multicast
members and therefore also static multicast provisioning in the ENM.

New static multicast members can only be configured on IGMP enabled interfaces.

GUI: Create Static Multicast Member

• Select Subracks->Actual Board->Multicast tab-> Membership Click Create.

or

• Select Subracks->Actual Board->Multicast tab->Membership tab->Click Create

static member

• Configure the parameters described below.

Fig. 24 Add Static Member

IC-INST-EMXPII Rev A | 2018-12-06 53 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Port The port parameter decides which port the multicast group should be for-
warded to. Selectable ports are IGMP enabled ports configured according
to Configuring a Multicast Enabled Interface.

Identifier A unique name for the static member.

VLAN ID Defines which VLAN the multicast traffic should be forwarded to the static
multicast member.
Type Denotes if the static multicast member is a Source Specific Multicast
(SSM) or an Any Source Multicast (ASM). If SSM is selected the source
address field must be configured accordingly.

Group address Defines the IP multicast address of the multicast traffic that should be for-
warded to the static multicast member. The group address parameter
range from 224.0.0.0 to 239.255.255.255

Source address Defines the IP address of the source to the specified multicast group that
should be forwarded to the static multicast member. The valid parameter
for source address is any valid unicast IP address.

CLI: Create Static Multicast Member

1. ::multicast::if::port::subrack:slot:txPort-rxPort::
associateStaticMember

2. Follow the instructions on screen and enter values for Identfier, VLAN ID, Source
address and Group address.

If the Source address parameter is defined as All, the membership entry will be an ASM, if a
specific source is defined the membership entry will be a SSM.

6.7.3 Viewing Multicast Membership Tables

The multicast membership tables and forwarding tables on the EMXP/II family can potentially
grow very large. To facilitate information gathering from the TU states there are several ways
to access and filter these tables.

GUI: Viewing Multicast Membership Table

1. Select Subracks->Actual Board->Multicast tab.

IC-INST-EMXPII Rev A | 2018-12-06 54 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 25 Multicast Membership Table

The multicast membership table shows a summary of the current multicast members. The
multicast membership table can be sorted throughout its columns by clicking on the different
data types for example clicking VLAN in the table header will sort the table by VLAN. Multicast
members are defined by the following fields.

Name A board unique identifier of the Multicast membership object. Dynamically

learnt members from IGMP snooping are named IGMP1, IGMP2 etc.
These names cannot be used as identifiers for static members.
Source If SSM is used the source is the source of the multicast stream that is sub-
scribed to, if the source is 0.0.0.0 any source is accepted and hence it is
ASM. Valid addresses are any unicast IP address and 0.0.0.0.

Group The IP multicast group address of the stream that is subscribed to. This
address can be any valid IP multicast address.

VLAN The VLAN ID of the multicast traffic that the member subscribes to.
Port The port that the multicast traffic should be forwarded to.

Up-time How long time that the multicast member has been in the membership ta-
ble and received multicast traffic.
Expiry-time How long until the current membership age out of the membership table,
statically provisioned members always have 0 s in expiry time.

Type Show whether the current member is a statically provisioned (user) entry
or if it is dynamically learnt through snooping (dynamic).

GUI: Viewing Filtered Multicast Membership Table

• Select Subracks->Actual Board->Multicast tab->I/F tab->Click Filtered membership

table.

The filtered version of the membership table provides more powerful functions to filter on the
different parameters.

IC-INST-EMXPII Rev A | 2018-12-06 55 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 26 Filtered multicast membership table

The filtered multicast membership table contains the same data as the membership table but
has filtering possibilities on port, type and VLAN ID.
It is also possible to sort the rows in the table in the table heading by clicking the desired prop-
erty to sort on, for example VLAN. Sorting can be in both ascending and descending order;
the order is changed by an additional click in the header of the table.

On systems that have large multicast membership tables, it is highly recommended to use the
filtered versions of the tables, since these offers significantly better performance even when
no filter is applied.

6.7.4 Viewing Multicast Forwarding Tables

The multicast forwarding tables on the EMXP/II family can potentially grow very large since
they have a potential 1 to 1 relation with the multicast membership table. To facilitate informa-
tion gathering from the TU states there are several ways to access and filter the multicast for-
warding table.

GUI: Viewing Multicast Forwarding Table

• Select Subracks->Actual Board->Multicast tab->Forwarding tab.

Fig. 27 Multicast Forwarding Table

IC-INST-EMXPII Rev A | 2018-12-06 56 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

The multicast forwarding table shows a summary of the current multicast forwarding state in
the TU which is derived from the multicast membership table. The multicast forwarding table
can be sorted throughout its columns, by clicking on the different data types.

Name A node unique identifier of the Multicast forwarding object.

Source If SSM is used the source is the source of the multicast stream that is sub-
scribed to, if the source is 0.0.0.0 any source is accepted and hence it is
ASM. Valid addresses are any unicast IP address and 0.0.0.0.

Group The IP multicast group address of the stream that is to be forwarded. This
address can be any valid IP multicast address.

VLAN The VLAN ID of the multicast traffic that is forwarded.

Fwd Indicates whether the forwarding entry has been used to forward multicast
traffic since the last time the table was refreshed.
Port The port(s) that the multicast traffic is forwarded to.

If two entries cover the same the same multicast traffic one SSM and one ASM only the SSM
entry will be used for forwarding when source address is the one specified by the SSM. Only
the ports defined in the port list of the SSM entry will then receive the multicast stream.

The filtered version of the multicast forwarding table provides more powerful functions to filter
on different parameters.

GUI: Viewing Filtered Forwarding Table

• Select Subracks->Actual Board->Multicast tab->I/F tab->Click Filtered forwarding

table

Fig. 28 Filtered multicast forwarding table

The filtered multicast forwarding table contains the same data as the multicast forwarding ta-
ble but has filtering possibilities namely on type, source address and group address.
It is also possible to sort the rows in the table in the table heading by clicking the desired prop-
erty to sort on, for example VLAN. Sorting can be in both ascending and descending order,
the order is changed by an additional click in the header of the table.

IC-INST-EMXPII Rev A | 2018-12-06 57 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

On systems that have large multicast membership tables, it is highly recommended to use the
filtered versions of the tables, since these offers significantly better performance even when
no filter is applied.

6.8 Policies Configuration

This section describes how to set up a policy from both ENM and CLI.

6.8.1 Creating Classifications

Classifications are used to define what kind of traffic an action is applicable to. A classification
with an associated action forms a policy. More information about Classifications can be found
in the Technical Description EMXP/II.

GUI: Creating Classifications

1. Select Subracks->Actual Board->Policy tab->Classification tab->Click Create

near the bottom.

2. Set values for Identifier, Precedence and Direction. Choose the attributes that
should be used in the classification and set the appropriate values for the chosen
attributes.

Fig. 29 Create classification dialogue for egress and ingress classifications

CLI: Creating Classifications

1. ::mes::misc::misc:subrack:slot::::associateClass

2. Follow the instructions on screen and set the values for the classification types below

IC-INST-EMXPII Rev A | 2018-12-06 58 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Identifier The identifier has to be unique on the TU.

Precedence If two classifications match a frame, the classification with the highest
precedence will be carried out.
Range: 0 to 511.

Direction An ingress classification classifies incoming frames, while an egress clas-

sification acts on switched and outgoing frames.

Port If configured as none in CLI, the classification will ignore the port.
Port ranges are dependent on the type of EMXP and the number of config-
ured LAGs.
Vlan Untagged Vlan Untagged classification classifies traffic without VLAN tag.
If configured as none in CLI, the classification will ignore the tag status.

Outer VLAN If configured as -1 in CLI, the classification will ignore the PCP.
PCP
Range: 0 to 7

Outer VLAN ID If configured as -1 in CLI, the classification will ignore VLAN IDs.
Range: 0 to 4094

Outer VLAN CFI If configured as -1 in CLI, the classification will ignore the VLAN CFI value.
Range: 0 to 1

Outer VLAN If configured as anytag in CLI, the classification will ignore the TPID value.
TPID
Inner VLAN PCP If configured as -1 in CLI, the classification will ignore the PCP.
Range: 0 to 7

Inner VLAN ID If configured as -1 in CLI, the classification will ignore VLAN IDs.
Range: 0 to 4094

Inner VLAN CFI If configured as -1 in CLI, the classification will ignore the VLAN CFI value.
Range: 0 to 1

DSCP If configured as -1 in CLI, the classification will ignore the DSCP value.
Range: 0 to 63

MAC Can be used as a MAC filter together with the MAC address mask.
Destination
Address If configured as none in CLI, the Destination MAC address will be ignored
by the classification.

MAC Address Can be used as a MAC filter together with MAC Destination address.
Mask
If configured as none in CLI, the MAC address mask will be ignored by the
classification.
Ethertype Any of the following Ethertypes can be included in the classification: IPv4
(0x0800), IPv6 (0x86dd), Slow Protocols (0x8809), MAC Security
(0x88e5), PTP (0x88f7) or OAM (0x8902).

IC-INST-EMXPII Rev A | 2018-12-06 59 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Source IP Can be used as a Source IPV4 address filter together with the Source IP
Address Mask.
It configured as none in CLI, the Source IP Address will be ignored by the
classification.
Source IP Mask Can be used as a Source IPV4 address filter together with the Source IP
Address.
It configured as none in CLI, the Source IP Mask will be ignored by the
classification.
Destination IP Can be used as a Destination IPV4 address filter together with the Desti-
Address nation IP Mask.
It configured as none in CLI, the Desitination IP Address will be ignored by
the classification.
Destination IP Can be used as a Destination IPV4 address filter together with the Desti-
Mask nation IP Address.
It configured as none in CLI, the Destination IP Mask will be ignored by
the classification.

6.8.2 Creating Actions

Actions are different forms and combinations of operations which when associated with a clas-
sification forms a policy.
A Classification has to already exist before configuring actions.

GUI: Creating Actions

1. Select Subracks->Actual Board->Policy tab->Action tab->Click the Create button

in the lower part of the page.

2. Choose an Identifier, choose a Classification that the action should be associated

with and choose what operations that should be performed in the action.

IC-INST-EMXPII Rev A | 2018-12-06 60 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 30 Create Action dialogue

CLI: Creating Actions

1. ::mes::class::class:subrack:slot:unique_class_identifier::
associateAction

2. Follow the instructions on screen and set the values for Identifier, Class, Type
and type related values.

The unique_class_identifier is the identifier of an already preconfigured classification.

The type is the type of action that should be associated with the classification.
General policy actions do not alter the frame but rather the EMXP handling of the frame.
Amongst the general actions drop can be configured but also queue assignments that over-
rides any PCP to queue mapping.
VLAN policy actions do alter the frame itself, by altering the VLAN tags.
For an egress classification, only VLAN operation actions are allowed.
It is possible to associate a MEF policer to a classification that will police the traffic matching
the classification.

IC-INST-EMXPII Rev A | 2018-12-06 61 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Identifier The identifier has to be unique on the TU

Classification The identifier of the classification that this action is associated to. From
the GUI, the classification is chosen by selecting it in a drop-down list.
From CLI, the class is automatically chosen when associating an action
from the classification object.

Drop Drop frames matching the classification. Only allowed for ingress
classifications.
Redirect Port Redirect traffic matching the classification to a specific port . Only allowed
for ingress classifications.

Green Queue Queue assignment for green frames matching the classification. Only al-
lowed for ingress classifications.

Yellow Queue Queue assignment for yellow frames matching the classification. Only al-
lowed for ingress classifications.

Green Pcp Set the PCP value for green frames matching the classification.

Yellow Pcp Set the PCP value for yellow frames matching the classification.

Swap Inner Set new Inner VLAN ID for frames matching the classification.
VLAN ID
Swap Outer Set new Outer VLAN ID for frames matching the classification.
VLAN ID
Push Inner Push a new VLAN tag in front of the Inner VLAN tag for frames matching
VLAN the classification. Only allowed for ingress classifications.

Push Outer Push a new VLAN tag in front of the Outer VLAN tag for frames matching
VLAN the classification. Only allowed for ingress classifications.

Pop Inner VLAN Remove the Inner VLAN tag for frames matching the classification. Only
allowed for ingress classifications.

Copy Outer Copy the Inner VLAN PCP value to the Outer VLAN tag for frames match-
VLAN PCP ing the classification. Only allowed for ingress classifications.

Police Apply a MEF policer on frames matching the classification. Only allowed
for ingress classifications. The MEF policer must first be created, see next
chapter.Creating MEF Policer.

Please note that on EMXP/III and EMXP440/III it’s not possible to set Action to “Redirect” to
another port based on a classification set-up by the Policy-Framework

6.8.3 Creating MEF Policer

MEF policers are used for color aware bit rate policing. A detailed overview over MEF policers
can be found in Technical Description EMXP/II.

IC-INST-EMXPII Rev A | 2018-12-06 62 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating MEF Policer

1. Select Subracks->Actual Board->Policy tab->MEF Policer tab->Click Create

button in the lower part of the page.

2. Configure and set values for Identifier, CIR, CBS, EIR, EBS and Mode.

Fig. 31 Create MEF Policer Dialogue

CLI: Creating MEF Policer

1. ::mes::misc::misc:subrack:slot:associateBwp

2. Follow the instructions on screen and set the values for Identifier, CIR, CBS, EIR,
EBS and Color mode. Identifier should be TU unique. Valid values of color mode
are colorAware or colorBlind.

IC-INST-EMXPII Rev A | 2018-12-06 63 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

The MEF policer needs to be associated with a classification see 6.8.2 Creating Actions.

If a MEF policer is shared amongst different classifications the rates will also be shared. CIR
and EIR can be independently set up to the theoretical speed of the interface.

6.8.4 Configuring QoS Profiles

Quality of Service is managed in QoS profiles for the EMXP/II. There are four independent
profiles that can be independently customized. A port of the EMXP/II TU is a member of one
of four QoS profiles. Members of a LAG are required to share the same profile.
In an EMXP/II QoS profile there are three vital parts, color encoding/decoding, PCP to queue
mapping, and scheduling.
More information on QoS can be found in Technical Description EMXP/II.

GUI: Setting QoS Profiles

• Select Subracks->Actual Board->QoS tab->Color tab.

Profile On the top of the tab the current profile is shown in the drop-list. By select-
ing another profile in the drop-list the selected profile loads and gets
dutiable.
Ports A list of the ports that are currently members of the shown profile.

Ingress color Color decoding is selected under color & queue mapping, represented by
decoding two drop-lists. The upper one represents PCP color decoding and the low-
er one can enable CFI/DEI color decoding. If it is desirable the EMXP/II
can be made colorblind by disabling both decoding schemes. If no color
decoding is enabled all frames are considered green.

Egress color The EMXP/II TUs has several different color encoding schemes, in the
encoding same manner as the ingress color decoding.

Queue When CFI/DEI decoding is enabled the CoS to queue mapping is configu-
rable since color is not encoded in the PCP values. The mapping is config-
ured by altering the queue drop-lists to the right of the PCP values.

Scheduler The scheduler can be configured in the scheduler section of this tab,
where strict priority, round-robin and weighted round robin are the sup-
ported alternatives.

CLI: Setting QoS Profiles

1. ::mes::cosProfile::profile:subrack:slot:profileNr::
configureScheduler

2. Follow the instructions on screen and enter values for scheduler type and weight.
Valid scheduler types are rr for round robin and wrr for weighted round robin and
strict for strict scheduling. The weights can only be set when using a WRR
scheduler.

IC-INST-EMXPII Rev A | 2018-12-06 64 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: egressDei encoding

• set ::mes::cosProfile::profile:slot:profileNr::egressDei <value>

Valid arguments for egressDei and ingressDei are enabled or disabled.

CLI: ingressPcp encoding from CLI

• set ::mes::cosProfile::profile:slot::profileNr::ingressPcp <value>

Valid arguments for ingressPcp and egressPcp are disabled or userDefined,

pcp6P2D, pcp7P1D, pcp8P0D and pcp5P3D.

It is highly recommended to use CFI/DEI encoding for decoding of color, so all PCP values
can be used to encode/decode priority.

For ease of use, it is recommended to use the GUI for configuring QoS.

6.8.5 WRED
WRED (a congestion avoidance algorithm) can be enabled on board level. When enabled
WRED will monitor packet queue sizes and randomly drop packets if a queue is growing close
to its maximum size. More information about WRED can be found in Technical Description
EMXP/II.

GUI: Enable/disable WRED function on board level

1. Select Subracks->Actual Board->Board name (overview) tab->Misc tab.

2. Set WRED to desired state and press Apply.

CLI: Enable/disable WRED function on board level

• set ::mes::misc::misc:subrack:slot::wred<enabled>/<disabled>

On EMXP/IIe family only traffic of type known unicast is handled by WRED. This implies that
the destination address needs to be existing in the L2 mac table. For example, when running
traffic through a VLAN then mac learning needs to be enabled to make the traffic known and
applicable for WRED governing.

6.9 Synchronous Ethernet Configuration

6.9.1 Creating a synchronization domain
To be able to run the automatic synchronization selection process with quality level selection
enabled, a synchronization domain has to be created. Perform the following steps to create a
synchronization domain:

IC-INST-EMXPII Rev A | 2018-12-06 65 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating a synchronization domain

1. Select Subracks->Actual Board->Sync tab->Domain tab->Click Create.

2. Enter the desired Domain number and choose QL selection setting. Select the
EMXP boards that should be part of the domain by adding them in the right side
window. If sync signal should be shared between the boards in the domain, choose a
Sync Bus to distribute the signal and a EMXP board as the Sync Bus Master to
distribute sync signals on the sync bus.

Creating a sync Domain

CLI: Creating a synchronization domain

• create ::sync::domain::sd:domain number

The domain number can be any number between 1 and 99. A total of 10 sync domains can be
created per subrack.

6.9.2 Associating board with synchronization domain

To associate a board with a synchronization domain, perform the following:

IC-INST-EMXPII Rev A | 2018-12-06 66 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Associating board with a synchronization domain

1. Select Subracks->Actual Board->Sync tab->Domain tab->Click Associate Boards.

2. Select Board from the Associate Board drop-down menu and click Apply.

CLI: Associating board with a synchronization domain

1. sync::domain::sd:domain number

2. associateBoard subrack:slot

ESMC quality level selection and signalling cannot be enabled when the TU is not associated
with a synchronization domain.

A single TU can only be a member of one synchronization domain at any given time.

6.9.3 Enabling/Disabling Quality Level Selection

To enable/disable quality level selection on all boards in the sync domain, perform the
following:

GUI: Enabling Quality Level Selection

1. Select Subracks->Actual Board->Sync tab->Domain tab.

2. Select enabled or disabled in the Quality level selection drop-down list and click
Apply.

CLI: Enabling/Disabling Quality Level Selection

• set sync::domain::sd:domain number ::qualityLevelSelection mode

Where mode is to be substituted with enabled or disabled

Enabling quality level selection will enable ESMC on all ports depending on the source mode.
Enabling ESMC quality level signalling can raise the invalid CE VLAN alarm on ports if not the
native VLAN is set to a VLAN that have a VLAN map.

6.9.4 Configuring Synchronization Bus

The backplane synchronization buses can be used to share sync signals between different
boards.
To configure a backplane synchronization bus, perform the following:

IC-INST-EMXPII Rev A | 2018-12-06 67 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Configuring the Sync Bus

1. Select Subracks->Actual Board->Sync tab->Bus tab.

2. Enter Domain and Master Slot, and click Apply.

CLI: Configuring the Sync Bus

1. sync::bus::sb:subrack:<busA/busB>::

2. set domain <value>

3. set masterSlot <value>

Subrack The subrack parameter informs in which subrack the current synchroniza-
tion bus belongs to.

Domain The domain the synchronization bus should be associated to, if no domain
are associated to the synchronization bus this parameter will have the val-
ue 0.
Master Slot The card slot of the traffic unit that should share it’s synchronization over
the bus.

Make sure that no synchronization loops are created when reconfiguring synchronization
buses.

If the ESMC quality level of the sync bus signal should be shared between boards in a syn-
chronization domain, the bus must also be part of the same domain.

6.9.5 Configuring Sync source

Some configuration is made for each individual synchronization source. A synchronization
source become nominated when it’s source mode is enabled and the status of the source is
normal. Configurable attributes for the synchronization source are:

IC-INST-EMXPII Rev A | 2018-12-06 68 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Source Mode Defines wether the sync source should be nominated to the sync selection
process and send and receive ESMC messages in quality level selection
mode. An enabled source can be nominated as the synchronization
source of a board, and send and receive ESMC messages. A lockedOut
source send and receives EMCS messags but cannot be nominated. A
disabled source neither sends or receives ESMC messages and cannot
be nominated.
Priority Defines the priority of the source among all nominated sync sources with
the same sync quality, or all nominated sync sources when quality level
selection is disabled.
Range: 1 to 16, 1 being the highest priority and 16 the lowest.

Static Quality Setting the Static Quality level to something other than 0 will override any
Level received ESMC quality level messages for that source and the source will
get the Static Quality level in the sync selection process. Only valid when
quality level selection is enabled.
Range: 0 to 15.

Table 3 Quality Level value interpretation

Quality Level Description

0 Quality unknown.

2 Traceable to PRC G.811

4 Traceable to Transit G.812 / SSH-A

8 Traceable to Local G.812 / SSH-B.

11 Derived from SETS / SEC

15 Do not use for synchronization

16 Quality Level not supported. Only internally generated.

17 Sync source failed. Only internally generated.

18 Sync source unconnected. Only internally generated.

6.9.6 Setting Source Mode of Sync Source

To set the source mode of a source, perform the following the steps:

GUI: Set Source Mode of Sync Source

1. Select Subracks->Actual Board->Sync tab->Source tab.

2. Set Source Mode, from the drop-down list and click Apply.

CLI: Setting Source Mode of Sync Source

1. set ::sync::source::ss:subrack:slot:txPort-rxPort::sourceMode
<source mode>

The source mode can be set to enabled ,disabled or lockedOut.

IC-INST-EMXPII Rev A | 2018-12-06 69 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.9.7 Setting Priority of Sync Source

To set the priority of a source, perform the following:

GUI: Setting Priority of Sync Source

1. Select Subracks->Actual Board->Sync tab->Source tab.

2. Select Source in the Name drop-down list. Enter a Priority value for the selected
source and click Apply.

CLI: Setting Priority of Sync Source

1. set ::sync::source::ss:subrack:slot:txPort-rxPort::prio
<priority>

6.9.8 Setting Static Quality Level

To set a static quality level of a sync source, perform the following:

GUI: Setting Static Quality Level

1. Select Subracks-> Actual Board-> Sync tab-> Source tab.

2. Select Source in the Name drop-down list. Enter a Static quality level value for the
selected source and click Apply.

CLI: Setting Static Quality Level

1. set ::sync::source::ss:subrack:slot:txPort-rxPort::
staticQuality <quality level>

Static quality level settings override dynamically learnt sync quality levels by the ESMC
protocol.

6.9.9 Clearing Wait to Restore Timer

It is possible to manually clear the wait to restore timer to make a source to be enabled for
sync source selection before the restore timer expires. This is done by the Clear WTR button
in the source tab in GUI or by the wtrClear command in CLI. The Clear WTR button in the
source tab in GUI and the wtrClear command in CLI are only available if source state is
waitToRestore.

GUI: Clearing Wait To Restore Timer

1. Select Subracks->Actual BoardSync tab->Source tab.

2. Click Clear WTR button and click Apply.

IC-INST-EMXPII Rev A | 2018-12-06 70 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Clearing Wait To Restore Timer

• sync::source::ss:subrack:slot:txPort-rxPort::wtrClear
txPort-rxPort may be substituted for bus-A, bus-B or osc for clearing the wtr timers for
the appropriate sync source.

6.9.10 Setting Manual/Forced Switch

Manual synchronization mode can be activated on a board using the manual/forced switch
command.
Manual switch allows switching to any sync source with same or better quality as the currently
selected sync source, whereas forced switch allows switching to any nominated sync source.
Manual and forced switches should be used with caution since they are one shot commands
and are not guaranteed to be enforced when TU states change.
Perform the following steps to manually switch sync source:

GUI: Setting Manual/Forced Switch

1. Select Subracks->Actual Board->Sync tab->Group tab.

2. Click Switch Source, select Switch Type and Source from the drop-down lists and
then Apply.

CLI: Manual/Forced Switch

1. sync::group::sg:subrack:slot::sourceSwitch

2. Follow the instructions on screen and enter values for switch type and source. Valid
switch types are manual or forced.

Forced sync source switches may not be persistent over TU sync state changes and are not
enforced after TU cold start or CU restart even if configuration is saved.

6.9.11 Enabling/disabling PTP1588v2 TC

Precision time protocol 1588v2 transparent clock can be enabled on board level.

GUI: Enable/disable Ptp 1588v2 TC on board level

1. Select Subracks->Actual Board->Board name (overview) tab->Misc tab.

2. Set Ptp 1588v2 transparent clock, to desired state and press Apply

CLI: Enable/disable Ptp 1588v2 TC on board level

• set ::mes::misc::misc:subrack:slot::enablePtp1588v2 <enabled>/

<disabled>

IC-INST-EMXPII Rev A | 2018-12-06 71 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.10 Configuring Ethernet OAM

Ethernet OAM can be configured in order to provide Connectivity Fault Management (CFM)
and Performance Montitoring (PM). The functions are using MEG/MEPs which support con-
tinuity check, loopback, loss measurement and delay measurement per Y.1731.

LM and DM configuration and functionality is available on EMXP/IIe Traffic Units.

Connectivity Fault Management is available for aggregated ports (LAGs) on EMXP/IIe Traffic
Units.

6.10.1 Creating MEG

Perform the following steps to create a MEG. For more information on Ethernet OAM, MEGs,
MEPs, LMs and DMs, refer to the Technical Description. To configure OAM for NIDs refer to
the NID OAM Configuration.

GUI: Creating MEG

1. Select Subracks->Actual Board->OAM tab->MEG tab

2. Click Create and configure the following parameters in the Associate MEG window.

Fig. 32 Associate MEG dialog

Identifier A TU unique Identifier for the MEG object.

Level The service level of the MEG.

IC-INST-EMXPII Rev A | 2018-12-06 72 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CCM interval On which interval the MEPs in the MEG should expect and send a OAM
CCM message.

Domain Domain as defined in 802.1ag.

Association Association formats defined in 802.1ag or ITU Y.1731.

Format

CLI: Creating MEG

• mes::misc::misc:subrack:slot::associateMeg

• Follow the instruction on screen and enter values for the following parameters:
Identifier, Level, CCM interval, Domain format, Association format, and
ICC.

6.10.2 Creating MEP

Perform the following steps to create a MEP

GUI: Creating MEP

1. Select Subracks->Actual Board->OAM tab->MEG tab and choose a MEG in the

Namelist

2. Click Associate MEP and configure the following parameters in the Associate MEP
dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 73 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 33 Associate MEP Dialogue

Interface The Interface parameter defines the ingress port or LAG for the expected
OAM CCM messages for a MEP defined as a remote MEP. If the MEP is
defined as a local MEP, the interface parameter defines the egress port/
LAG for the OAM CCM frames
Direction Defines location and transmission direction of the MEP. A Down MEP is lo-
cated on the network side of the unit switch core and send OAM frames to-
wards the egress/ingress interface. An Up MEP is located on the client
side of the unit switch core and sends OAM frames towards the network
through the switch core.

Primary VLAN Defines the encapsulating VLAN of the OAM CCM frames that are sent
ID and expected.

VLAN Priority Defines the encapsulating VLAN priority for sent OAM CCM frames.

Type Defines whether the MEP should be a remote MEP that expects and in-
spect OAM CCM messages or a local MEP that actively sends OAM CCM
messages.

Identifier Defines the MEP ID for the MEP

CCM Sequence If selected, a sequence number will be included in every CCM frame sent
number by the MEP. Only available for Up MEPs.

Loopback If selected, the MEP will respond to OAM loopback messages if they are
response at the right MEG level and addressed to the TU eth0 address if the TU is
configured in a CU-system, and eth1 for CU-less configurations.

IC-INST-EMXPII Rev A | 2018-12-06 74 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

LM Responder If selected, the MEP will respond to OAM Loss measurement messages
belonging to this MEP.

DM Responder If selected, the MEP will respond to OAM Delay measurement messages
belonging to this MEP.

LM Cos ID Specifies if the LM Responder should be Priority aware or Priority blind.

An ERPv2 or MEP that is configured for a port can later be migrated to work over a LAG, see
6.5.5 Creating Link Aggregation Group (LAG)

LM or DM is only supported on port interfaces, not LAGs.

LM Cos ID parameter (priorityBlind or priorityAware) needs to correspond to the use of Cos ID

in the LM Session defined at the other endpoint.

If an LM Session is configured for the remote mep, the LM Responder is automatically en-
abled on the local MEP.

CLI: Creating MEP

• mes::maid::meg:subrack:slot:megIdentifier::associateMep
where megIdentifier is the Identifier of the MEG.

• Follow the instructions on screen and enter values for the following parameters:
Direction, Interface, Primary VLAN ID, VLAN priority, Type, MEP identifier ,
Transmit loopback response? , DM loopback response? , LM loopback
response?,Cos ID for LM Responder?.

6.10.3 Creating LM Session

Perform the following steps to create an LM Session

Starting an LM session will automatically enable that 15 minute and 24 hour periodic LM Re-
ports are generated and sent to TNM.

In order for an LM session to run, an LM Responder also needs to be activated at MEP on the
remote node.

IC-INST-EMXPII Rev A | 2018-12-06 75 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating LM

1. Select Subracks->Actual Board->OAM tab->MEP tab and choose a remote MEP in

the Namelist.

2. Click Associate LM Measurement in the attribute list and configure the following
parameters in the Create LM Session dialogue.

Fig. 34 Create LM Dialogue, left: using MEP. right: specify MAC address.

LMM Interval Defines the interval of sending LMM messages to the remote LM respond-
er. Values can be 1, 10 seconds or 100 milliseconds (default 1 second).

Priority Defines which priority to do Loss Measurement for. The Prioirity is only rel-
evant for Priority Aware sessions (set in the Cos ID parameter). Priorities
can have values 0 to 7.
Cos ID Defines if an LM Session should do measurement for a specific priority
(priorityAware), or for all priorites combined (priorityBlind). Up to 8 priority
aware sessions can be defined. Restrictions: It is not possible to mix Prior-
ity Blind and Priority Aware sessions for a MEP. It is only possible to define
one Priority Blind session for a MEP. Note that the Cos ID parameter
needs to correspond to the use of Cos ID in the LM Responder defined in
the MEP at the other endpoint.

Type Type can be MEP or MAC address.

If MEP is chosen: The LM session will use the MAC address from the re-
mote MEP, i.e the LM will discover the MAC address in received Continuity
Check (CCM) messages of the remote MEP and use it to address the re-
mote LM responder.
If MAC address is chosen: Explicitly specify a MAC address of the remote
LM responder.

High Loss Defines the level for triggering counting of unavailable seconds.
Threshold
Unavailable Defines the threshold of unavailable seconds for triggering an alarm.
seconds alarm
threshold

IC-INST-EMXPII Rev A | 2018-12-06 76 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 35 LM Session tab after add

CLI: Creating LM

• ::mes::cfmMep:remotemep identifier::associateLM

• Follow the instructions on screen and enter values for the following parameters:
Message Interval, High Loss Threshold, Unavailable Alarm Threshold, Cos
ID, Use remote MEP id or MAC address?, Set a MAC Address in case MAC was
selected.

GUI: Showing LM Statistics.

1. Select Subracks->Actual Board->OAM tab->LM tab and choose an LM session

Name list.

2. Click Statistics button next to the Operational status to open the LM Counters
dialogue box.

IC-INST-EMXPII Rev A | 2018-12-06 77 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 36 LM Counters

CLI: Viewing LM statistics

• ::soamPm::lmStats::mep:MEG Identifier:subrack:slot:MEP identifier:

priority

6.10.4 Creating DM Session

Perform the following steps to create a DM Session.

IC-INST-EMXPII Rev A | 2018-12-06 78 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Starting a DM session will automatically enable that 15 minute and 24 hour periodic DM Re-
ports are generated and sent to TNM.

In order for a DM session to run, a DM Responder also needs to be activated at MEP on the
remote node.

GUI: Creating DM

1. Select Subracks->Actual Board->OAM tab->MEP tab and choose a remote MEP in

the Name/label> list.

2. Click the Associate DM Measurement button and configure the following parameters
in the Create DM Session dialogue.

Fig. 37 Create DM Dialogue, left: using MEP. right: specify MAC address.

DMM Interval Defines the interval of sending DMM messages to the remote DM res-
ponder. Values can be 100 milliseconds, 1 or 10 seconds. (default 100
milliseconds)

Priority Defines the priority for this DM session. values can be from 0 to 7. (There
can be up to 8 sessions with different priorities)

Type Type can be MEP or MAC address.

If MEP is chosen: The DM session will use the MAC address from the re-
mote MEP, i.e the DM session will discover the MAC address in received
Continuity Check (CCM) messages from the remote MEP and use it to ad-
dress the remote DM responder.
If MAC address is chosen: Explicitly specify a MAC address of the remote
DM responder.

IC-INST-EMXPII Rev A | 2018-12-06 79 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 38 DM Session tab after adding

CLI: Creating DM

• ::mes::cfmMep:remotemep identifier::associateDM

• Follow the instructions on screen and enter values for the following parameters:
Message Interval, Priority Value, Use remote mep Id, Destination MAC, in
case MAC was choosen in type.

GUI: Showing DM Statistics.

1. Select Subracks->Actual Board->OAM tab->DM tab and choose a DM session in

the Name list.

2. Click Statistics button next to the Operational status to open the DM Counters
dialogue box.

IC-INST-EMXPII Rev A | 2018-12-06 80 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 39 DM Counters

CLI: Viewing DM statistics

• ::soamPm::dmStats::mep:MEG Identifier:subrack:slot:MEP identifier:

priority

IC-INST-EMXPII Rev A | 2018-12-06 81 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.11 ERPv1 Configuration

6.11.1 Creating an ERPv1 node
Before creating an ERP make sure that the ring interfaces have the correct VLAN ID associ-
ated to the interfaces and that they trust each other.

GUI: Creating an ERP

1. Select Subracks->Actual Board-> Prot tab->ERP tab.

2. Click Create button from the bottom of the page and configure the following
parameters in the Create ERP dialogue.

Fig. 40 Create ERP dialogue

CLI: Creating an ERP

• ::mes::misc::misc:subrack:slot::associateErp

• Follow the instruction on screen and enter values for the following parameters: VLAN ID,
Description, MEG Level, Left interface, Right interface, Protection link
and Guard time.

VLAN ID The VLAN ID of the R-APS VLAN for the ERP ring.

Description A user defined description of the ERP ring.

MEG level The MEG level that should be used by the ERP R-APS messages.

Left interface The left ring port (no lag).

IC-INST-EMXPII Rev A | 2018-12-06 82 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Right interface The right ring port (no lag).

Protection link Defines if the node is a ring node which has no direct connection to the
protection link which corresponds to values none, or if it is the Ring Protec-
tion Link (RPL) owner. Only one RPL must be configured in a single ERP
ring. When the node is configured as a RPL owner the state of the Protec-
tion link parameter is left or right.

OAM detection can be configured for the individual ERP interfaces. This is done by creating a
MEG with MEPs on the same interface(s), with a lower MEG level than the R-APS VLAN of
the ERP. This should be done individually for each OAM detection enabled ERP ring interface
according to Creating MEG and Creating MEP.

ERP V1 over LAG is not supported. So the interface constitutes only to port object.

When configuring an ERP ring the RPL owner should be configured last. The ERP R-APS
VLAN should be unique and should not be extended outside the ERP ring, and should thus
not be used for traffic.

OAM detection MEGs should have a MEG level less than the one configured for the ERP R-
APS messages. This since ERP R-APS messages are OAM messages and can be terminated
by MEPs.

IC-INST-EMXPII Rev A | 2018-12-06 83 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.12 Configuring ERPv2

In ERPv2 services are protected, meaning only a set of VLANs on a port are blocked and not
the whole port as in ERPv1. Accordingly several rings may be put on top of each other. ERPv2
also implements the possibility to connect Sub-rings to a an already existing ring. Fig. 41
ERPv2 ring example illustrates the terminology used within ERPv2 configuration.

Fig. 41 ERPv2 ring example

To create a functional ERPv2 ring the VLAN maps, the VLAN Protection groups and the
ERPv2 ring itself have to be correctly configured in a specific order on each node. The proce-
dure below describe how this should be done.

Configuring an ERPv2 Ring Node

1. Create the VLAN Protection Group(s) for the traffic VLANs according to Creating a VLAN
Protection Group.

2. Create the R-APS VLAN map, with trust set on the ring ports. See Creating VLAN Maps.

3. Create the ERPv2 Ring node according to Creating an ERPv2 node. The VLAN
Protection Group for the R-APS VLAN is created automatically, if it does not already
exist.

4. Add the VLAN Protection Group(s) created in 1) to the ERPv2 ring according to Creating
a VLAN Protection Group. The VLANs in the VLAN Protection groups will be protected by
the ERPv2 ring when the VLAN Map is created on the ERPv2 ring ports.

5. Create the VLAN maps, with trust and MAC learning set, for the traffic VLANs according
to Creating VLAN Maps. Since the ERPv2 ring already is created, the ports may be
selected by filling in the check box for the ERPv2 ring.
The two nodes, on which the Sub-ring connects to the Major ring, are configured as ERPv2
Sub-interconnection nodes. The other nodes in the Sub-ring are configured as regular Ring
nodes according to procedure above.

IC-INST-EMXPII Rev A | 2018-12-06 84 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Configuring an ERPv2 Sub-interconnection Node

1. Create the VLAN Protection Group(s) for the traffic VLANs according to Creating a VLAN
Protection Group

2. Create the R-APS VLAN map, with trust set on the ports. The VLAN map must cover the
Sub-ring port and the two Major Ring ports to achieve correct functionality. See Creating
VLAN Maps.

3. Create the ERPv2 Sub-interconnection node according toCreating an ERPv2 node. The
VLAN Protection Group for the R-APS VLAN is created automatically, if it does not
already exist. The Major ring, to which the Sub-ring shall be connected, must be created
prior to this step.

4. Add the R-APS VLAN of the Sub-ring to the traffic VLAN of the Major Ring, by following
the steps described in step 1, 4 and 5 above. This will implement the Sub-ring virtual
channel.

5. Add the VLAN Protection Group(s) created in 1) to the ERPv2 Sub-ring and the ERPv2
Major Ring according to Creating a VLAN Protection Group. The VLANs in the VLAN
Protection groups will be protected by both the Sub-ring and the Major ring when the
VLAN Map is created on the Sub-ring and Major ring ports.

6. Create the VLAN maps, with trust and MAC learning set, for the traffic VLANs according
to Creating VLAN Maps. Since the Sub-ring and the Major ring already are created, the
ports may be selected by filling in the check boxes for the ERPv2 Sub-ring and the
ERPv2 ring.
Important Notes:

A VLAN ID can only be a member of one VLAN Protection Group.

All Sub-rings connected to a Major ring have to be deleted before the Major ring can be
deleted.
When an ERPv2 ring is deleted, the VLAN Protection Groups are automatically disassociated
from the ring.

6.12.1 Creating an ERPv2 node

There are two different types of nodes, “Ring”- and “Sub-Interconnection” node. If the node is
the node where the Sub-ring connects to the Major ring, a Sub-Interconnection node shall be
created. In all other cases the type Ring node shall be selected.

GUI: Creating an ERPv2 Ring node

1. Select Subracks->Actual Board->Prot tab->ERP tab.

2. Click Create button and configure the following parameters in the Create ERP
dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 85 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 42 Creating an ERPv2 Ring node

CLI: Creating an ERPv2 Ring node

• ::mes::misc::misc:subrack:slot::associateErpV2

• Follow the instructions on the screen and enter values for the following parameters: Ring
ID, VLAN ID, MEG Level, Description, Node type, Interface left, Interface
right, Protection Link, Protection mode and VLAN protection group
identifier for R-APS VLAN.

Ring ID The Ring ID (1–239) is the ID associated with the ERPv2 ring. The Ring
ID / VLAN ID combination composes an unique key for the ERPv2 ring.

VLAN ID The VLAN ID of the R-APS VLAN for the ERPv2 ring.

MEG level The MEG level that should be used by the ERPv2 R-APS messages.

Description A user defined description of the ERPv2 ring.

Node type ringNode: Selected in all cases except when an interconnection-point for
a Sub-ring is configured. (Selected in this section)
subInterconnection: Selected in case an interconnection-point for a
Sub-ring is configured.

Interface left The left ring port (or LAG).

Interface right The right ring port (or LAG).

Protection Link Defines the connection to the Ring Protection Link (RPL), where:
none: no direct connection to the RPL
left: the RPL is set on the left port — the node is RPL Owner
right: the RPL is set on the right port — the node is RPL Owner

IC-INST-EMXPII Rev A | 2018-12-06 86 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

leftNeighbour: the RPL is set on the left port — the node is RPL
Neighbour
rightNeighbour: the RPL is set on the right port — the node is RPL
Neighbour

Protection The Protection Mode specifies revertive or non-revertive mode. (Only eli-
mode gible if node is RPL Owner)

VLAN A user defined description of the VLAN Protection Group, in which the R-
protection APS VLAN resides.
group identifier
for R-APS VLAN

GUI: Creating an ERPv2 Sub-interconnection node

1. Select Subracks->Actual Board->Prot tab->ERP tab.

2. Click Create button and configure the following parameters in the Create ERP
dialogue.

Fig. 43 Creating a Sub-interconnection node

CLI: Creating an ERPv2 Sub-interconnection node

• ::mes::misc::misc:subrack:slot::associateErpV2

• Follow the instructions on the screen and enter values for the following parameters: Ring
ID, VLAN ID, MEG Level, Description, Node type, Interface left, Major Ring,
Protection Link, Protection mode and VLAN protection group identifier
for R-APS VLAN.

IC-INST-EMXPII Rev A | 2018-12-06 87 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Ring ID The Ring ID (1–239) is the ID associated with the ERPv2 Sub-ring. The
Ring ID / VLAN ID combination composes an unique key for the ERPv2
Sub-ring.

VLAN ID The VLAN ID of the R-APS VLAN for the ERPv2 Sub-ring.

MEG level The MEG level that should be used by the ERPv2 R-APS messages.

Description A user defined description of the ERPv2 Sub-ring.

Node type ringNode: Selected in all cases except when an interconnection-point for
a Sub-ring is configured.
subInterconnection: Selected in case an interconnection-point for a
Sub-ring is configured. (Selected in this section)

Interface left The left ring interface. (a Sub-ring has a left interface only)

Major Ring The Major Ring, to which the Sub-ring is connected.

Protection Link Defines the connection to the Ring Protection Link (RPL), where:
none: no direct connection to the RPL
left: the RPL is set on the left port — the node is RPL Owner
leftNeighbour: the RPL is set on the left port — the node is RPL
Neighbour

Protection The Protection Mode specifies revertive or non-revertive mode. (Only eli-
mode gible if node is RPL Owner)

VLAN A user defined description of the VLAN Protection Group, in which the R-
protection APS VLAN resides.
group identifier
for R-APS VLAN

When the ERPv2 node has been created, there are a few parameters that may be configured
in the GUI.

IC-INST-EMXPII Rev A | 2018-12-06 88 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 44 Parameters in the ERPv2 GUI

MEG level The MEG level for the R-APS messages may be updated after creation.
Will cause traffic hit.
Protection link The protection link may be updated after creation. Will cause traffic hit.

Protection Protection mode may be updated after creation. Will not cause traffic hit.
mode
Guard time The Guard Time can be set in the interval 10ms-2s with a resolution of
10ms. The default value is 500ms.
Wait to restore In case the node is RPL Owner, the Wait To Restore (WTR) timer can be
time set in the interval 1–12min with a resolution of 1min. The default value is
5min.
OAM detection OAM detection can be configured for the individual ERPv2 ports. This is
left done by creating a MEG with MEPs on the ERPv2 ring port(s). The MEG
should have a MEG level lower than the one configured for the ERPv2 R-
APS messages since the ERPv2 R-APS messages are OAM messages
and can be terminated by MEPs. The OAM configuration should be done
individually for each OAM detection enabled ERPv2 ring port according to
6.10 Configuring Ethernet OAM .

IC-INST-EMXPII Rev A | 2018-12-06 89 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Topology In case of a Sub-interconnection node, the Topology change propagation

change can be enabled. When enabled, a topology change in the Sub-ring, will
propagation propagate to the Major ring it is connected to. The ring ports in the major
ring will accordingly be flushed to enable learning of the new topology.
The default value is disabled.
OAM detection The VLAN ID in CCM:s used for OAM detection
VLAN ID

The ERPv2 Ring ID / R-APS VLAN ID combination should be unique and must not be used by
another ERPv2 ring.

The R-APS VLAN ID should not be used for traffic. The only exception is the virtual channel
for a Sub-ring, which requires the Sub-ring R-APS VLAN ID to be part of the traffic VLANs of
the Major Ring.

In case of a newly created Sub-interconnection, “Topology change propagation” is set to dis-

able by default. In many cases this causes slower convergence than necessary and in most
network configurations “Topology change propagation” could be changed to “enable” for better
overall network performance.

An ERPv2 that is configured for a port can later be migrated to work over a LAG, see 6.5.5
Creating Link Aggregation Group (LAG)

OAM detection MEGs should have a MEG level less than the one configured for the ERP R-
APS messages. This since ERP R-APS messages are OAM messages and can be terminated
by MEPs.

6.12.2 Creating a VLAN Protection Group

According to the ERPv2 standard certain VLANs/services are blocked on a port and not the
whole port as in ERPv1. To implement this with required blocking performance, VLAN Protec-
tion Groups have to be created. A VLAN Protection Group can contain one to many VLANs
and can be associated with several ERPv2 rings. When an ERPv2 ring blocks one of its ports,
it actually blocks all its associated VLAN Protection Groups on the specified port.

GUI: Creating a VLAN Protection Group

1. Select Subracks->Actual Board-> VLAN tab->VLAN Prot tab.

2. Click Create button and configure the following parameters in the Create VLAN
Protection dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 90 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 45 Create VLAN Protection Group

When creating the VLAN Protection Group in the GUI, both the group creation and the associ-
ation to an ERPv2 ring are managed in the dialogue above. However, the creation and associ-
ation need not be configured at the same time.
In CLI, the group has to be created in one CLI part and thereafter the association to/from the
ring is managed in another CLI part. See below.

CLI: Creating a VLAN Protection Group

1. ::mes::misc::misc:subrack:slot::associateVlanProt

2. Follow the instructions on the screen and enter values for the following parameters:
Identifier, Protected VLANs.

Identifier A user defined description of the VLAN Protection Group.

Protected A VLAN or set of VLANs that shall be added to the group. Could be a com-
VLANs ma separated list or as a range. A specific VLAN can only be a member of
one VLAN Protection Group. The TPID of the VLAN(s) can be either Q
(0x8100) or S (0x88a8) and VLANs with different TPIDs can coexist in the
same VLAN Protection Group.

CLI: Adding Protection of a VLAN Protection Group

1. mes::vlanProt::vlanProt:subrack:slot:Identifier::addRing

2. Follow the instructions on the screen and enter values for the following parameters:
Ring.

Ring The Erpv2 ring that shall protect the VLAN Protection Group.

IC-INST-EMXPII Rev A | 2018-12-06 91 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Removing Protection of a VLAN Protection Group

1. mes::vlanProt::vlanProt:subrack:slot:Identifier::removeRing

2. Follow the instructions on the screen and enter values for the following parameters:
Ring.

Ring The Erpv2 ring that shall stop protecting the VLAN Protection Group.

IC-INST-EMXPII Rev A | 2018-12-06 92 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.12.3 Viewing ERPv2 configuration

When a ERPv2 service has been created, an overview of the configured ERPv2 service can
be seen in the Show Protection dialog. Basic ERPv2 parameters will be shown, along with
assigned VLAN Protection groups, configured VLAN maps and Mgmt VLANs included in the
VLAN Protection Groups.

GUI: Viewing ERPv2 configuration

1. Select Subracks->Actual Board->Prot tab-> ERP tab-> Actual ERPv2 object

2. Click Show Protection button.

Fig. 46 ERPv2 configuration overview

When enabling Mgmt VLAN on the ERP ports with the Mgmt VLAN ID included in a VLAN pro-
tection group, the change will not take effect until the CU is rebooted. Thus, the Mgmt VLAN
ID will not be protected nor shown in the dialog until after the reboot.

IC-INST-EMXPII Rev A | 2018-12-06 93 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.13 Configuring Multi Chassis Redundancy

To configure Multi Chassis Redundancy, a number of objects need to be created and associ-
ated with each other. These are the LAG that should be protected, an up MEP which is used
as communication channel for the ICCP and mLACP protocol TLV:s (payload in OAM MCC
PDU:s), an ICCP Redundancy Group and lastly the MC-LAG itself. The figure below shows
some use cases.

Fig. 47 MC-LAG to a normal LAG to the left and MC-LAG to MC-LAG to the right.

Preparatory Steps:

1. Create a LAG according to Creating Link Aggregation Group (LAG) .

2. Create an up MEP according to Creating MEP.

LACP must be enabled on the LAG when used in Multi Chassis mode.

When the preparatory steps has been completed the ICCP Redundancy Group and MC-LAG
can be configured. See Creating an ICCP Redundancy Group and Creating an MC-LAG. In
the ENM, the user can create the ICCP Redundancy Group and the MC-LAG in the same
dialogue.

6.13.1 Creating an ICCP Redundancy Group

GUI: Creating an ICCP Redundancy Group

1. Select Subracks->Actual Board-> Prot tab->ICCP-RG tab.

2. Click Create button from the bottom of the page and configure the following
parameters in the Create Multi Chassis Redundancy dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 94 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 48 Create ICCP Redundancy Group dialogue

When an ICCP Redundancy Group has been created the states for the ICCP and application
connections can be verified. In this case no MC-LAG has been created yet so the connection
state for the application is nonExistent.

Fig. 49 ICCP Redundancy Group tab

CLI: Creating an ICCP Redundancy Group

• ::iccp::node::iccpNode:subrack:slot::createIccpRg

• Follow the instruction on screen and enter values for the following parameters: Group ID
and MEP.

Group ID The Group ID used by all of its members. Range: 1–8.

MEP The management name of the MEP used for communication.

The Group ID must match between the EMXP:s that protect the same LAG.

The MEP selected must be of type remote and direction up.

IC-INST-EMXPII Rev A | 2018-12-06 95 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.13.2 Creating an MC-LAG

Before proceeding with these steps make sure that the preparatory steps in Configuring Multi
Chassis Redundancy has been completed. There are two ways to create MC-LAG in the
ENM. One is from the Create MC-LAG dialogue. The other one is from the Create Multi Chas-
sis Redundancy dialog if the “Create MC-LAG” checkbox is invoked.

GUI: From the Create MC-LAG dialogue

1. Select Subracks->Actual Board-> Prot tab->MC-LAG tab.

2. Click Create button from the bottom of the page and configure the following
parameters in the Create MC-LAG dialogue.

GUI: From the Create Multi Chassis Redundancy dialogue

1. Select Subracks->Actual Board-> Prot tab->ICCP-RG tab.

2. Click Create button from the bottom of the page and configure the following
parameters in the Create Multi Chassis Redundancy dialogue.

3. Invoke the Create MC-LAG checkbox.

Fig. 50 Create Multi Chassis Redundancy dialogue to the left and Create MC-LAG dialogue to the right.

CLI: Creating an MC-LAG

• ::iccp::rg::iccpRg:<subrack>:<slot>:<ICCP redundancy group ID>::

createMcLag

• Follow the instruction on screen and enter values for the following parameters: NodeID,
Lag, Administrative system priority and Port priority.

IC-INST-EMXPII Rev A | 2018-12-06 96 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Node ID Used to ensure that the LACP port numbers are unique across all mem-
bers of a Redundancy Group. Range: 0–7.

LAG The management name of the controlled LAG.

Administrative The Administrative system priority is used in the initial negotiation with the
system priority other member in the Redundancy Group. It is necessary for all members
in a Redundancy Group to agree upon the System MAC Address and Sys-
tem priority values to be used ubiquitously. Range: 1–65534 (65535 is re-
served for internal use).

Port priority This priority is used on all ports in the LAG. Range: 1–65535.

When the MC-LAG has been created the LAG status, Operational system priority and Opera-
tional port priority can be viewed.

Fig. 51 MC-LAG tab.

LAG status The LACP selection logic compares the port aggregation priority of the lo-
cal and remote ports and determines which system is active.

Operational This is the priority that the members of the Redundancy Group have
system priority agreed to use in LACPDU:s. Range: 1–65535.

Operational port This priority is used as the Actor Priority in LACPDU:s. Range: 1–65535.
priority

When a LAG is in Multi Chassis mode, the LACP enabled setting, the individual port priorities
of the ports and the system priority of the LAG is no longer writable. These parameters are in-
stead owned by the MC-LAG.

Minimum number of active links is not supported on the LAG when operated in Multi Chassis
mode.

When an MC-LAG is deleted the Maximum number of active links and Minimum number of ac-
tive links are set to zero to avoid a traffic loop. If this LAG is to be operated in Multi Chassis
mode again, these parameters must be updated before the MC-LAG is created.

A change in the Administrative port priority on an MC-LAG will not be reflected in the Opera-
tional port priority if the change would lead to a LAG status change from standby to active. To
change the LAG status for the members in a Redundancy group, set the Administrative port
priority on the currently active MC-LAG to a higher numerical value than the standby MC-LAG.

IC-INST-EMXPII Rev A | 2018-12-06 97 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.14 Configuring MPLS-TP

The EMXP traffic units supports MPLS-TP which is configured under the MPLS and the PW
tabs in the ENM GUI. The EMXP TU can be configured to act in two different roles while par-
ticipating in an MPLS service, Label edge router (LER) or label switch router (LSR). The roles
are configured in An overview of MPLS-TP configuration the MPLS-TP service configuration.
MPLS-TP configuration objects can be configured in a variety of ways and orders to provide
full flexibility, yet it is advisable to follow the following procedures for efficiency and easy
troubleshooting.

Fig. 52 Steps required to set up LER functionality

Recommended procedure for configuration of a LER functionality

1. Configure the Global ID of the MPLS node. (optional)

2. Create a VLAN ID to carry the MPLS-TP encapsulated traffic, a backbone VLAN ID. This
VLAN ID must be set on all MPLS-IF ports connected to the LSP.

3. Configure the desired MPLS interface if it is not already configured.

4. In ENM GUI create an MPLS tunnel and create the edge LSP in the same dialogue and
associate it with the desired MPLS interface.

5. Associate LSP for protection services (optional).

Recommended procedure for configuration of a Virtual Private Wire Service (VPWS)

1. Create a desired pseudowire and associate it with the newly created tunnel.

Recommended procedure for configuration of a LSR functionality

1. Make sure the physical ports associated to the MPLS interfaces are trusted.

2. Configure the desired MPLS interfaces if they are not already configured.

3. In ENM GUI create an transit LSP associated with the desired MPLS interfaces.

It is highly recommended to use ENM GUI for configuration of MPLS functionality. Once the
basic configuration is in place (MPLS-IF) the DNA-M can also be used to create LSP, tunnel
and pseudowires.

A pseudowire created in ENM/CLI must have the same pseudowire ID in both ends in order
for the DNA-M to discover the service.

IC-INST-EMXPII Rev A | 2018-12-06 98 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.14.1 Configuration of MPLS Node

The MPLS node is constituted by a single EMXP traffic unit and contains configuration that is
shared by all configured MPLS objects on this unit.
The Global ID in the network should be set to the global unique number of the service pro-
vider, RFC-5003. Global ID configuration is local and only refers to current EMXP card and
needs to be configured for every card. The Node ID refers to the current EMXP card and can
in this instance considered to be the node. Ref: RFC6428

Fig. 53 MPLS-TP Node Page

GUI: Configuring a MPLS node

1. Select Subracks->Actual Board-> MPLS-TP tab->Node .

2. Configure desired parameters and click the Apply.

The parameters associated with the MPLS node are:

Linear Defines the mode for MPLS-TP protection services on the node, revertive
Protection Mode / non-revertive.
Wait to restore Defines the WTR timer value for all MPLS-TP protection services on the
timer (WTR) node.

Continuous Defines the cyclic coordination message interval for all MPLS-TP protec-
message tion services on the node.
interval
Global ID An unique operator identifier also called MPLS-TP Global Identifier.

Node ID Unique nodeID/routerID assigned with in the scope of the network of the
operator/service provider, defined by the Global ID.

IC-INST-EMXPII Rev A | 2018-12-06 99 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Configuring the MPLS Linear protection mode

• set ::mpls::node::node:subrack:slot::linearProtMode <revertive/

nonRevertive>

CLI: Configuring the MPLS Wait to restore timer

• set ::mpls::node::node:subrack:slot::wtrTimer <timer value>

CLI: Configuring the MPLS Continuos message interval

• set ::mpls::node::node:subrack:slot::contMessageInterval <timer

value>

CLI: Configuring the MPLS GlobalID

• set ::mpls::node::node:subrack:slot::globalId <globalId>

CLI: Configuring the MPLS Node Router ID

• set ::mpls::node::node:subrack:slot::nodeNumber <nodeRouterId>

It is recommended to use the node router ID and to use the MPLS-TP IDs on tunnels and
LSPs where applicable in any larger MPLS-TP installation.

Node ID and Global Id can not be changed without setting the existing BFD session in BFD
admin down state. All existing BFD session will be updated with the New Node ID and Global
ID. Even Destination Global ID and Destination Node ID will be updated if the value is not con-
figure, value 0, or has the same value as the current Node ID or Global ID.

6.14.2 Configuration of MPLS Interface

Before configuring an MPLS interface the backbone VLAN MAP must be configured on the
port. The backbone VLAN MAP carries the MPLS-TP encapsulated traffic between two peer
MPLS interfaces. The MPLS interface defines a subinterface on a port or LAG which actively
can detect and participate in MPLS-TP services. At least one MPLS interface is required on
every interface that will forward traffic in an MPLS aware manner. Several MPLS interfaces
can be associated with the same physical interface. An MPLS interface can be configured in
ENM GUI by executing the following procedure

GUI: Creating an MPLS interface

1. Select Subracks->Actual Board-> MPLS-TP tab->Interface tab.

2. Click Create and configure the following parameters in the Create I/F dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 100 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 54 The Create I/F Dialogue

The parameters associated with an MPLS Interface are:

Identifier A user defined unique identifier for referencing to the MPLS interface.

Admin Status Defines whether the MPLS interface should be up or down.

Port/LAG The physical port or LAGthat the logical MPLS interface is associated
with.
VLAN ID The VLAN ID that the interface will use for receiving and forwarding of
MPLS traffic. Note that this parameter have to be equal between two
MPLS interfaces over a link.
Next hop MAC The destination MAC address of all frames forwarded by this MPLS inter-
face. By default this is set to a known IANA MPLS-TP point-to-point multi-
cast MAC address (see dialogue figure) that will be accepted by any peer
MPLS interfaces (if supported). It can also be set to the interface MAC ad-
dress of the peer MPLS interface.

Interface MAC The interface MAC address is a logical MAC address used by the MPLS
interface. If the destination address of an incoming frame differs from the
interface MAC address or the known IANA MPLS-TP point-to-point multi-
cast MAC address, the frame will not be forwarded.

IC-INST-EMXPII Rev A | 2018-12-06 101 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Creating an MPLS interface

• ::mpls::node::node:subrack:slot::createIf

• Follow the instruction on screen and enter values for the following parameters:
Identifier, VLAN ID, adminStatus, Next hop MAC address, Interface MAC
address

Before creating an MPLS interface make sure that the backbone VLAN ID is configured on the
physical port or LAG and that its port mode is set to NNI.
The next hop and interface MAC addresses should be configured in a mirrored fashion be-
tween two peer MPLS interfaces.
The backbone VLAN ID should be the same for the two peer MPLS interfaces.
The backbone VLAN ID should strictly be used for MPLS traffic.

6.14.3 Configuration of Label Switched Path

The Label switched path (LSP ) defines two MPLS X-connects as a part of a bidirectional LSP.
The LSP can be of one of two different types, namely edge LSP used in LER configurations
and transit LSP used in LSR configurations. Please note that the needed underlying X-con-
nects used will be automatically created upon completion of the GUI dialogue. Refer to 2.

When configuring edge LSPs it can be faster to use the create Tunnel dialogues which allows
for direct creation of edge LSPs together with the tunnel in the same dialogue.

GUI: Creating an MPLS LSP

1. Select Subracks->Actual Board-> MPLS-TP tab->LSP tab.

2. Click Create and configure the following parameters in the Create LSP dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 102 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 55 The Create LSP dialogue for both transit and edge LSPs

CLI: Creating an MPLS Edge LSP

• ::mpls::node::node:subrack:slot::createLsp2

• Follow the instruction on screen and enter values for the following parameters:
Identifier, LSP Role? edge, MPLS Interface, MPLS outlabel, MPLS inlabel,
Internal tunnel ID, Add BFD session? Yes/No, BFD profile.

CLI: Creating an MPLS Transit LSP

• ::mpls::node::node:subrack:slot::createLsp2

• Follow the instruction on screen and enter values for the following parameters:
Identifier, LSP Role? transit, MPLS Interface, MPLS outlabel, MPLS
inlabel, MPLS Interface 2, MPLS outlabel 2, MPLS inlabel 2, Add MPLS-TP LSP
ID? yes/no, Source tunnel ID, Destination node ID, Destination tunnel ID .

The parameters when creating an LSP are:

Identifier A user defined unique identifier for referencing to the LSP.

Role Defines whether this LSP is an edge or transit node in an MPLS service.

Mpls Interface The MPLS interface to use for a LER when configured with the role edge.
If the role of the LSP is transit, this correlates to the forward outbound
and reverse inbound cross connect MPLS interface.
Mpls outlabel Outbound MPLS label to use in underlying MPLS cross connect. This cor-
relates to the forward cross connect outbound MPLS label.
Mpls inlabel Outbound MPLS label to use in underlying MPLS cross connect. This cor-
relates to the reverse cross connect inbound MPLS label.

IC-INST-EMXPII Rev A | 2018-12-06 103 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Tunnel Only defined for role edge The MPLS tunnel associated with this LSP.
(Optional)

Enable BFD Only defined for tunnel associated edge LSP Allows for automatic crea-
tion of a BFD session monitoring the LSP. (Optional)

BFD Template Only defined for tunnel associated edge LSP The template to use when
creating a BFD session. (Optional)

Mpls Interface 2 Only defined for role transit The MPLS interface to use for the reverse
outbound and forward inbound MPLS interface in the underlying MPLS
cross connect.
Mpls outlabel 2 Only defined for role transit Outbound MPLS label to use in underlying
MPLS cross connect. This correlates to the reverse cross connect out-
bound MPLS label.
Mpls inlabel 2 Only defined for role transit Outbound MPLS label to use in underlying
MPLS cross connect. This correlates to the forward cross connect in-
bound MPLS label.
Source node ID Only defined for role transit The MPLS-TP source node ID. (Optional)

Source node Only defined for role transit The MPLS-TP source node tunnel ID.
tunnel ID (Optional)

Destination Only defined for role transit The MPLS-TP destination node ID.
node ID (Optional)

Destination Only defined for role transit The MPLS-TP destination node tunnel ID.
node tunnel ID (Optional)

• Tabbing in CLI provides valid configuration suggestions.

• When selecting MPLS labels it is highly recommended to use different spaces for LSPs and Pseudowires.

6.14.4 Configuration of MPLS Tunnel

An MPLS tunnel is defined as a service between two LERs provided by one or several LSPs.
When creating a MPLS tunnel, it is possible to simultaneously create a working LSP for the
tunnel.

GUI: Creating an MPLS Tunnel

1. Select Subracks->Actual Board-> MPLS-TP tab->Tunnel tab.

2. Click Create and configure the following parameters in the Create Tunnel dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 104 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 56 The Create Tunnel Dialogue

The parameters associated with an MPLS Tunnel are:

Destination The MPLS-TP ID of the destination node for this tunnel. (Optional)
node ID
Source node The MPLS-TP ID of the tunnel in this node. (Optional)
tunnel ID
Destination The MPLS-TP ID of the tunnel at the destination node. (Optional)
node tunnel ID
Existing LSP Allows the direct association of an already configured LSP to the tunnel.
(Optional)

Create Edge Allows for automatic creation and association of an edge LSP upon the
LSP creation of the tunnel.
Identifier A user defined unique identifier for referencing to the edge LSP created to-
gether with the MPLS tunnel.

IC-INST-EMXPII Rev A | 2018-12-06 105 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Mpls Interface The MPLS interface to use by the edge LSP created together with the
MPLS tunnel.
Mpls outlabel Outbound MPLS label to use by the edge LSP created together with the
MPLS tunnel.
Mpls inlabel Inbound MPLS label to use by the edge LSP created together with the
MPLS tunnel.
Enable BFD Allows for automatic creation of a BFD session monitoring the created
LSP (Optional)

BFD template The BFD template to use for OAM.

Traffic Class Defines the value of the Traffic Class Field.

CLI: Creating an MPLS tunnel

• ::mpls::node::node:subrack:slot::createTunnel

• Follow the instruction on screen and enter values for the following parameters:
Identifier, Working LSP Id, Add standard MPLS-TP ID? yes/no, Source
Tunnel ID, Destination Node ID, Destination Tunnel ID.

6.14.5 Creation of MPLS linear protection

A MPLS linear protection service is created by adding a protection LSP in the tunnel.

GUI: Creating an MPLS linear protection object

1. Select Subracks->Actual Board-> MPLS-TP tab->Tunnel tab.

2. Click Associate button and configure the following parameters in the Associate LSP
dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 106 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 57 The AssociateLsp Dialog for creating MPLS linear protection

The parameters when creating protection LSP within the tunnel in the GUI are:

Existing LSP Allows the direct association of an already configured LSP to the tunnel.
(Optional)

Identifier A user defined unique identifier for referencing to the protection LSP.

Mpls Interface The MPLS interface to use for a LER when configured with the role edge.

Mpls outlabel Outbound MPLS label to use in underlying MPLS cross connect. This cor-
relates to the forward cross connect outbound MPLS label.
Mpls inlabel Outbound MPLS label to use in underlying MPLS cross connect. This cor-
relates to the reverse cross connect inbound MPLS label.
Enable BFD Allows for automatic creation of a BFD session monitoring the created
LSP (Optional)

BFD template The BFD template to use for OAM.

Traffic Class Defines the value of the Traffic Class Field.

IC-INST-EMXPII Rev A | 2018-12-06 107 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Creating an MPLS Linear Protection

• Create an edge LSP. Follow the instructions on the screen for the ::mpls::node::
node:subrack:slot::createLsp command.

• ::mpls::tunnel::tunnel:subrack:slot:tunnelID::associateLinearProt

• Follow the instructions on screen for the associateLinearProt command. Enter the
LSPID of the newly created edge LSP.

Tabbing in CLI provides valid configuration suggestions.

6.14.6 Configuration of MPLS linear protection

Most attributes are configured on a node level and affects all configured protection services,
but one timer attribute can be uniquely configured for every service.
Wait to restore timer is configured in node properties described in Configuration of MPLS
Node
Linear protection mode is configured in node properties described in Configuration of MPLS
Node
Continuous message interval is configured in node properties described in Configuration of
MPLS Node
Hold-off timer configuration:

GUI: Configure MPLS linear protection hold-off timer

1. Select Subracks->Actual Board-> MPLS-TP tab->MPLS prot tab.

2. Select protected tunnel and enter time in hold-off timer field and click Apply.

CLI: Configure MPLS linear protection hold-off timer

• set ::psr::mplsLinearProt::linProt:subrack:slot:tunnelID::
holdOffTimer <time>.

6.14.7 MPLS linear protection operator commands

A configured protection service can be manually controlled through a number of operator com-
mands directing the traffic onto one of the paths associated to the MPLS Tunnel.

Table 4 MPLS linear protection operator commands

Priority Command Description

1 = highest

1 noRequest No active operator command. Clears the previous active operator command

IC-INST-EMXPII Rev A | 2018-12-06 108 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Table 4 MPLS linear protection operator commands (cont’d.)

2 lockOut Lock out of protection is used prevent switching of data traffic to the protec-
tion path.

3 forced Forced switch is used to switch traffic from the working path to the protection
path.

The forced switch will be performed regardless of the state of the protection
path.

4 manual Manual switch is used to switch traffic from the working path to the protection
path.

The traffic will only be switched if no currently active fault condition.

• Operator commands with lower priority than the currently active operator command will not be performed.
• To clear an active operator command issue a noRequest command.

GUI: Set MPLS linear protection operator command

1. Select Subracks-> Actual Board-> MPLS-TP tab->MPLS prot tab.

2. Select protected tunnel and select operator command and click Apply.

CLI: Set MPLS linear protection operator command

• set ::psr::mplsLinearProt::linProt:subrack:slot:tunnelID::
opCommand <operator command>.

IC-INST-EMXPII Rev A | 2018-12-06 109 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.15 Configure Pseudowires

The pseudowire (PW) represents a Layer 2 virtual private wire service (VPWS) with the option
to do service delimiting (SD-tag) operations on the traffic carried on the PW. The traffic
mapped into a PW can be a physical interface, a specific VLAN on a physical interface or se-
lected by a ingress policy classification on the board attached to the PW. A VLAN map is not
required for mapping traffic into a pseudowire. There is an option to do SD delimiting opera-
tions on the traffic in the PW in accordance with RFC-4448. The PW can be a edge PW where
the traffic is on ingress MPLS-TP encapsulated and decapsulated on egress or it can be a
multi-segment PW which connects other pseudowires.
Pseudowire classification mappings may not overlap between pseudowires, also the incoming
pseudowire labels must be unique and allocated from another label space than the LSP
labels.

6.15.1 Creating an Edge Pseudowire

If the traffic shall be mapped into the PW by a policy classification then it needs to be created
before the PW. For the optional service delimiting tag see 6.15.2 Service Delimiting VLAN Tag
Operations. The default operation is transparent mode, meaning that the traffic will be fully en-
capsulated and transparently transported through the pseudowire.

GUI: Creating a Edge Pseudowire

1. Select Subracks->Actual Board->PW tab->Generic tab.

2. Click Create and select Edge in the drop down menu and configure the following
parameters in the Create pseudowire dialogue.

Fig. 58 create edge pseudowire

IC-INST-EMXPII Rev A | 2018-12-06 110 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

The parameters associated with a edge pseudowire are:

Pseudowire ID A user defined unique identifier for referencing to the pseudowire.

PW in label The incoming pseudowire MPLS label associated with this pseudowire.

PW out label The outgoing pseudowire MPLS label associated with this pseudowire.

Traffic class The traffic class of the PW, used for QoS mapping in the MPLS-TP
system.

Tunnel The Tunnel that the pseudowire is currently mapped into.

Flow Label Label added to the MPLS label stack to be used for load balancing.NOTE:
Generated based on the currently selected LAG-hash algorithm.

Pseudowire One of the following three methods is used to map traffic into the PW
Classification
Port All traffic on this port is mapped into the pseudowire.(Optional)

VLAN Specific VLAN that will be mapped into the pseudowire. (Optional)

Classification Policy classification used to map traffic into the pseudowire. (Optional)

Service Associate a service delimiting operation to the pseudowire, default is

delimiting VLAN transparent. See 6.15.2 Service Delimiting VLAN Tag Operations
Tag (Optional)

CLI: Creating a edge pseudowire

• ::mpls::node::node:subrack:slot::createPw

• Follow the instruction on screen and enter values for the following parameters:
Identifier, Outbound PW label, Inbound PW label, Tunnel ID,
Classification Type, Pseudowire operation mode.

• When selecting MPLS labels it is highly recommended to use different spaces for LSPs and Pseudowires.
• Tabbing in CLI provides valid configuration suggestions.
• For DNA-M to discover the created service the pseudowire ID must be the same on both ends.

6.15.2 Service Delimiting VLAN Tag Operations

The Service delimiting tag (SD-tag) implementation is divided into three modes according to
RFC-4448. In transparent mode (default) no additional action is taken either on ingress or
egress and the frames are transported through the MPLS-TP PW seamless. The operations
performed in tagged and raw mode are show in the table below.

Table 5 Service delimiting operations

Mode: Action on Ingress: Action on Egress:

Transparent No Action No Action

IC-INST-EMXPII Rev A | 2018-12-06 111 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Table 5 Service delimiting operations (cont’d.)

Tagged Push Pop

Swap
No Action

Raw Pop Push

No Action

• The egress action is performed on the same PW end as the ingress action.
• Push on egress (option for Raw mode) will allways push a SD-tag on the frames.

6.15.3 Creating a Multi-Segment Pseudowire

A multi segment pseudowire connects other multi segment pseudowires or edge
pseudowires.

GUI: Creating a Multi-SegmentPseudowire

1. Select Subracks->Actual Board->PW tab->Generic tab.

2. Click Create and select Multi-segment in the drop down menu and configure the
following parameters in the Create pseudowire dialogue.

Fig. 59 The create Multi-segment pseudowire

IC-INST-EMXPII Rev A | 2018-12-06 112 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

The parameters associated with a Multi-segment pseudowire are:

Pseudowire ID A user defined unique identifier for referencing to the pseudowire.

East in label The incoming pseudowire MPLS label associated with this pseudowire on
the east side.
East out label The outgoing pseudowire MPLS label associated with this pseudowire on
the east side.
East Tunnel The tunnel associated with this pseudowire to the east.

West in label The incoming pseudowire MPLS label associated with this pseudowire on
the west side.
West out label The outgoing pseudowire MPLS label associated with this pseudowire on
the west side.
West Tunnel The tunnel associated with this pseudowire to the west.

CLI: Creating a multi-segment pseudowire

• ::mpls::node::node:subrack:slot::createMsPw .

• Follow the instruction on screen and enter values for the following parameters:
Identifier, East Outbound PW label, East Inbound PW label, East Tunnel ID,
West Outbound PW label, West Inbound PW label, West Tunnel ID.

• When selecting MPLS labels it is highly recommended to use different spaces for LSPs and Pseudowires.
• Tabbing in CLI provides valid configuration suggestions.
• For DNA-M to discover the created service the pseudowire ID must be the same on the multi segment pseudo-
wire as on the edge pseudowires.

IC-INST-EMXPII Rev A | 2018-12-06 113 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.16 MPLS-TP OAM configuration

Infinera uses MPLS-TP OAM based on Bidirectional Forwarding Detection, BFD. A BFD ses-
sion can be connected to an LSP to provide supervision of the LSP.
BFD sessions send two types of messages, Continuity Check (CC) and Connection Verifica-
tion (CV) messages.
The CC messages verify the connection by sending messages with the interval set by the
used BFD template. The initial timing is 1000 ms and is negotiated down by the node and peer
BFD session according to RFC6428. The CV and CC messages share fate with the common
traffic.
The CV message verifies that the right peer BFD session is connected. Verification uses
MPLS-TP MEP IDs composed of Global ID, Node ID, Tunnel ID and LSP ID. The composed
value is shown in the BFD session, and the LSP. Both the MEP ID for the local session and
the peer node session need to be configured in order to verify the connectivity in both ends of
the LSP.
The LSP ID will by default be given the value 1 for working path LSPs and the value 2 for pro-
tection path LSPs. This value will automatically be reconfigured when the LSP connected to a
tunnel. The automatic reconfiguration will only take place if the LSP ID has the value; 0, 1, or
2. Otherwise the value will be left untouched.

The MPLS-TP MEP-ID does not have to be configured. The BFD session will display a warn-
ing if Node ID, Tunnel ID, or LSP ID is not configured and left with the default value 0. The
BFD sessions will start and run the connection verification anyway.

6.16.1 Creating a BFD Template

A BFD template can be create to be able to create BFD sessions with a specific timing re-
quired by the user. There is always a default BFD template to ease the creation of BFD
sessions.

GUI: Procedure for creating a BFD template

1. Select Subracks->Actual Board->OAM->BFD Template

2. Click Create button

3. Set configuration and click Apply

IC-INST-EMXPII Rev A | 2018-12-06 114 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 60 The Create BFD template dialog

CLI: Creating a BFD template

• mplsOam::bfdTemplate::bft:subrack:slot:default::createNewTemplate

• Follow the instruction on screen and enter values for the following parameters:
Identifier, Tx interval (ms), Rx interval

The detection multiplier is a 3 and can not be changed.

6.16.2 Creating a BFD Session

BFD sessions can be created and associated with already configured LSPs.
In “Create LSP” and “Create tunnel” GUI dialogs the BFD session can be created automati-
cally when creating a tunnel or an edge LSP.

Procedure for creating a BFD session

1. Select Subracks->Actual Board->MPLS-TP->LSP tab.

2. Click the Add button to add a BFD session to selected LSP.

3. Set configuration and click Apply.

IC-INST-EMXPII Rev A | 2018-12-06 115 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 61 The Create BFD Session dialogue

BFD template The BFD template contains timing configuration for the BFD session.
There is always a default template. A custom template could also be chos-
en. To create a custom BFD template refer to 6.16.1 Creating a BFD
Template

Traffic Class The entry signifies the Traffic Class used on the traffic generated by the
BFD session CV and CC messages

Admin status The administrative state of the BFD session can be set. This value can be
changed later. The default value is up.

CLI: Creating a BFD Session

• mpls::lsp::lsp:subrack:slot:lsp::createBFD

• Follow the instruction on screen and enter values for the following parameters: BFD
Profile, Set administrative status.

In order to create a BFD session the LSP must be connected to a tunnel. The reason for this
is because the MPLS-TP MEP ID is in part inherited from the tunnel.

IC-INST-EMXPII Rev A | 2018-12-06 116 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.16.3 Configuration of Tunnel ID or Destination tunnel ID

The MPLS-TP MEP ID can be configured during the creation of the tunnel object. See 6.14.4
Configuration of MPLS Tunnel.

6.16.4 Changing the configuration of Tunnel ID, Destination tunnel

ID, and Destination global ID
The following dialog is only visible in Verbose mode.

GUI: Reconfiguring an MPLS tunnel ID

1. Select Equipment->Actual Board->MPLS-TP->Tunnel tab

2. Select tunnel object.

3. Set Tunnel ID, Destination tunnel ID, or Destination global ID.

Fig. 62 Reconfiguration of Tunnel ID, Destination tunnel ID, and Destination global ID.

CLI: Procedure for setting destination global ID

• set ::mpls::tunnel::subrack:slot::name::dstGlobalId <expected

global ID>

IC-INST-EMXPII Rev A | 2018-12-06 117 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Procedure for setting destination node ID

• set ::mpls::tunnel::subrack:slot::name::destNodeId <expected node

ID>

CLI: Procedure for setting destination tunnel ID

• set ::mpls::tunnel::subrack:slot::name::destTunnelId <expected

tunnel ID>

6.16.5 Configuration of LSP ID

The LSP ID will by default be given the value 1 for working path LSPs and the value 2 for pro-
tection path LSPs. This value will automatically be reconfigured when the LSP is connected to
a tunnel. The automatic reconfiguration will only take place if the LSP ID has the value; 0, 1, or
2. Otherwise the value will be left untouched. The configuration of the LSPs MPLS-TP MEP ID
can be changed. But the web browser and CLI need to be set in verbose mode.

The configuration of the LSPs MPLS-TP MEP ID can be changed. But the web browser and
CLI need to be set in verbose mode.

Procedure for changing the configuration of LSP ID

1. Select Subracks->Actual Board->MPLS-TP->LSP tab

2. Select LSP object.

3. Set LSP ID.

IC-INST-EMXPII Rev A | 2018-12-06 118 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 63 LSP ID configuration

CLI : Procedure for changing the configuration of LSP ID

• set ::mpls::lsp::lsp::subrack:slot::name::lspId <set LSP ID>

6.16.6 Configuration MPLS-TP MEP ID for LSP LSR

A transit LSP will not require a MPLS-TP MEP ID configuration. For documentation purposes
it could be a good idea to set the MEP IDs. The Source node ID and Source tunnel ID could
be either end of the tunnel. Configuration values can only be set during the creation of the
LSP.

6.16.7 Interoperability of BFD Session and MPLS-TP MEP ID

For BFD session to interact with other networks the MPLS-TP MEP ID may need some con-
sideration. The Global ID in the network should be set to the global unique number of the serv-
ice provider, RFC-5003 Destination global ID should be set to the to the peer network Global
ID number. Node ID, Destination Tunnel ID and LSP ID may need to be change to match the
peer network BFD session settings.

6.16.8 BFD warnings and alarms

The following alarms are defined for BFD sessions.

IC-INST-EMXPII Rev A | 2018-12-06 119 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

MEP not MEP-ID for tunnel, node or LSP are set to zero, source or remote BFD
configured sessions. The CV messages will be transmitted but the connectivity verifi-
cation will have degraded function.

Local Invalid MEP-ID received by local session. MPLS-TP MEP-ID from CV

misconnectivity messages does not match local configuration. BFD session is connected
to wrong peer BFD session or MEP IDs are not configured correctly. The
BFD session will display expected and actual values.

Local timer Local BFD session has not received valid CC packages for an interval of
expired more than (Detection multiplier X negotiated RX interval).

Remote timer The local BFD session has received an indication that the peer BFD ses-
expired sion is in down state due to time-out of CC packages.

Remote The local BFD session has received an indication that the peer BFD ses-
misconnectivity sion is in down state due to an invalid received MPLS-TP MEP-ID.

6.17 Viewing and removing MPLS-TP configuration

6.17.1 MPLS-TP Service Overview
The MPLS-TP service overview is a flexible and convenient tool to display the whole MPLS-
TP setup from the interfaces to the pseudowires.

GUI: Displaying the MPLS-TP service overview

1. Select Subracks->Actual Board->PW tab->Overview tab ->MPLS-TP service

overview button.

2. The MPLS-TP service overview can also be accessed from the Generic, Mpls,
Ethernet and Multi-segment tabs. The object from which the MPLS service overview is
initiated will serve as a starting point for mapping the MPLS service instances.

IC-INST-EMXPII Rev A | 2018-12-06 120 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 64 The MPLS-TP service overview

The MPLS-TP service overview displays the MPLS-TP objects associated with a selected
pseudowire. The pseudowire is selected by a drop down list below the pseudowire object with
all pseudowires on the board. The pseudowire can also be by chosen by selecting a specific
tunnel in the drop down menu below the tunnel object and then selecting one of the pseudo-
wires in this tunnel from the down menu to the right of the tunnel menu.

Pseudowire Here some of the attributes are shown for the selected pseudowire.

Tunnel and The tunnel associated with the pseudowire and the protection object for
Protection the service.
LSP The LPS associated with the pseudowire, both the working path and the
protection path.

IC-INST-EMXPII Rev A | 2018-12-06 121 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

BFD The BFD associated with the LSP, both the working path and the protec-
tion path.

IF The IF associated with the LSP, both the working path and the protection
path.

6.17.2 Viewing static MPLS-TP configuration in CLI

A configured MPLS tunnel is represented by several related MPLS objects, as seen in Fig. 2
An overview of MPLS-TP configuration. The object can be found in the tunnel, lsp, xc and
iftables in CLI.

CLI: Viewing Static MPLS-TP configuration

1. ::mpls::tunnel::tunnel::subrack:slot:Id::

2. ::mpls::lsp:: lsp::subrack:slot:Id::

3. ::mpls::xconnect:: xc::subrack:slot:outlabel:inlabel

4. ::mpls::if:: mplsif::subrack:slot:Id::

6.17.3 Viewing MPLS-TP protection and OAM configuration in CLI

Adding lsp supervision and protection synchronisation for a MPLS tunnel adds some extra ob-
jects, as seen in Fig. 3 An overview of MPLS-TP linear protection configuration. The object
can be found in the linPrt, bfd and bft tables in CLI.

CLI: Viewing MPLS-TP protection configuration

1. ::psr::mplsLinearProt::linPrt::subrack:slot:tunnelId::

CLI: Viewing MPLS-TP OAM configuration

1. ::mplsOam::bfdSession::bfd::subrack:slot:lspId::

2. ::mplsOam::bfdTemplate::bft::subrack:slot:Id::

6.17.4 Viewing PW configuration in CLI

Pseudowire configuration is divided into 4 separate tables. An edge PW is represented in the
generic, mpls and ethernet tables. A multi-segment PW is represented in the generic and
Multi-segment.

IC-INST-EMXPII Rev A | 2018-12-06 122 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Viewing PW configuration

1. ::pw::generic::pw::subrack:slot:Id::

2. ::pw::mpls:: mpls::subrack:slot:Id::

3. ::pw::enet:: enet::subrack:slot:Id::

4. ::pw::mspw:: mspw::subrack:slot:Id::

6.17.5 Removing MPLS-TP configuration

As a general guideline for deletion of objects, any other objects referring to the current object
should be removed first. To remove an MPLS-TP configuration the pseudowires must be re-
moved first and then LSPs, Tunnels and finally the MPLS-TP IFs. It is however possible to re-
move an LSP that's is set as protection path and then, if desirable, to set up a new protection
LSP.

GUI: Removing MPLS-TP configuration

1. Select Subracks->Actual Board->PW tab->Generic Click Delete

2. Select Subracks->Actual Board->MPLS-TP tab->LSP Click Delete

3. Select Subracks->Actual Board->MPLS-TP tab->Tunnel Click Delete

4. Select Subracks->Actual Board->MPLS-TP tab->Interface Click Delete

CLI: Removing MPLS-TP configuration

1. ::pw::generic:: delete pw::subrack:slot:Id::

2. ::mpls::lsp:: delete lsp::subrack:slot:Id::

3. ::mpls::tunnel:: delete tunnel::subrack:slot:Id::

4. ::mpls::if:: delete if::subrack:slot:Id::

IC-INST-EMXPII Rev A | 2018-12-06 123 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.18 Configuring Port Devices

This section includes instructions on how to configure a Network Interface Device or iSFP
from both ENM and CLI.

6.18.1 Creating a NID

A NID is intended to be managed as a part of the EMXP/IIe traffic units. The preferred concept
is to view the NID as a “remote” port of the EMXP/IIe, that includes OAM functions.
A NID can be created on a 1G port of EMXP/IIe, which is a member of certain VLANs. The
VLAN is used when configuring and managing the EMXP-NID. For more information on
VLANS see VLAN Configuration.

The communication between a node and a NID is always VLAN tagged using ethertype
qTag0x8100. It is therefor recommended that the required VLAN map is configured with this
ethertype or it will result in uncessary “Rx invalid CE VLAN id” alarms.

GUI: Create NID

1. Select Subracks->Actual Board->PortDevice tab->NID General tab.

2. Click Create.

3. NID-GE will be auto-selected as Device type in the Create port device window.
iSFPs will also be shown in the Device type drop-down list.

4. Select the port the NID to be connected to by selecting the available port in the Port
drop-down list.

5. Select the VLAN ID for the NID by selecting the appropriate value in the VLAN ID
drop-down list.

CLI: Create NID

1. ::portDev::generic::portDevGeneric:subrack:slot::
createPortDevice.

2. Follow the instructions on screen.

IC-INST-EMXPII Rev A | 2018-12-06 124 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.18.2 NID Port Configuration

This section includes instructions on how to configure the NID ports from both ENM and CLI.

6.18.2.1 Configuring Link Passthrough

The NID units supports NIF to CIF link passthrough. With link passthrough enabled a LOS on
the NID:s NIF port will trigger a laser shutdown on its CIF port. This will propagate a LOS to-
wards the customer through the NID unit. If the CIF-b is active then the CIF link will still be ac-
tive but no communication can take place.

GUI: Configuring Link Passthrough

1. Select Subracks->Actual Board->PortDevice tab->NID General tab->Name list.

Select enabled/disabled from the Link passthrough drop-down list and click Apply.

CLI: Configuring Link Passthrough

• set ::portDev::equipment::nidGe name::linkpassthrough setting

Valid settings for linkpassthrough are enabled or disabled.

IC-INST-EMXPII Rev A | 2018-12-06 125 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.18.2.2 Setting Auto Negotiation

GUI: Set Auto Negotiation

• Select Subracks->Actual Board->PortDevice tab->NID L2 tab->Name list->Auto

negotiation mode drop-down list

CLI: Set Auto Negotiation

• set ::portDevIf::L2::nidGe name:port::autoNegationMode

Valid settings for autoNegotiationMode are off or on.

6.18.2.3 Configuring Client Signal Fail

The NID units supports ETH-CSF on the NIF. When CSF is enabled, a LOS on the active CIF
will trigger a ETH-CSF message being sent from the NID MEP, if it is configured. In addition,
when an ETH-CSF is detected on the MEP the NID will shut down the laser of the active CIF.
The function is meant to work either NID-NID, or NID-EMXP which in turn will require
Error Propagation
policies to be configured on the EMXP.

IC-INST-EMXPII Rev A | 2018-12-06 126 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Configuring CSF

1. Select Subracks->Actual Board->PortDevice tab->NID General tab->Name list.

Select enabled/disabled from the Client Signal Fail drop-down list and click Apply.

CLI: Configuring CSF

• set ::portDev::equipment::nidGe name::csf setting

Valid settings for Client signal Fail are enabled or disabled.

6.18.3 NID OAM Configuration

6.18.3.1 Creating MEG to be used on a NID
Perform the following steps to create a MEG. For more information on Ethernet OAM, MEGs
and MEPs, refer to the Technical Description EMXP/II.

GUI: Creating MEG

1. Select Subracks->Actual Board->PortDevice tab->NID MEG tab

2. Click Create and configure the following parameters in the Create MEG dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 127 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 65 Create NID MEG Dialogue

Identifier A unique Identifier for the MEG object.

Level The service level of the MEG.

CCM interval Defines which interval the MEPs in the MEG should expect and send peri-
odic OAM CCM messages.

Domain Domain as defined in 802.1ag.

Association Association formats defined in 802.1ag or ITU Y.1731.

Format

CLI: Creating MEG

1. ::portDev::generic::portDevGeneric:subrack:slot::createMeg

2. Follow the instruction on screen and enter values for the following parameters:
Identifier, Level, CCM interval, Domain format, Association format,
and ICC.

6.18.3.2 Creating MEP on a NID

Perform the following steps to create a MEP

GUI: Creating MEP

1. Select Subracks->Actual Board->PortDevice tab->NID MEG tab and choose a

MEG in the MEG drop-down list

2. Click Add button next to the No. of current nid-MEPs field and configure the
following parameters in the Create MEP dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 128 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 66 Create NID MEP Dialogue

MEP Type Defines the whether the MEP should be a remote MEP that expects and
inspect OAM CCM messages or a local MEP that actively sends OAM
CCM messages.

MEP Identifier Defines the MEP ID for the MEP

Port device Defines the Port Device to which the MEP will be added..

CLI: Creating MEP

• ::portDev::generic::portDevGeneric:subrack:slot::createMep

• Follow the instructions on screen and enter values for the following parameters: MEG, MEP
type, MEP identifier and Port Device.

Setting the administrative status to down on a local NID MEP will also disable a remote MEP
on that NID. Setting the administrative status to down on a remote NID MEP will only suppress
alarms but not affect the termination of OAM packets in the NID. This administrative status be-
havior differs from other MEPs on a EMXP.

6.18.3.3 Creating an LM Session on a NID

Perform the following steps to create an LM Session

Starting an LM session will automatically enable that 15 minute and 24 hour periodic LM Re-
ports are generated and sent to TNM.

GUI: Creating LM

1. Select Subracks->Actual Board->PortDevice tab->NID MEP tab and choose a

remote MEP in the MEP drop-down list

2. Click Add button next to the No. of current LM Sessions field and configure the
following parameters in the Create LM dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 129 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 67 Create LM Dialogue, left: using MEP. right: specify MAC address.

LMM Interval Defines the interval of sending LMM messages to the remote LM re-
sonder. values can be 1, 10 seconds or 100ms (1s default).

Type Type can be MEP or MAC address.

If MEP is chosen: The LM session will use the MAC address from the re-
mote MEP, i.e the LM will discover the MAC address in received Continuity
Check (CCM) messages of the remote MEP and use it to address the re-
mote LM responder.
If MAC address is chosen: Explicitly specify a MAC address of the remote
LM responder.

High Loss Defines the alarm level for triggering a High loss alarm.
Threshold
Unavailable Defines the number of seconds until triggering an Unavailable alarm.
seconds alarm
threshold

IC-INST-EMXPII Rev A | 2018-12-06 130 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 68 LM Session tab after add

GUI: Showing LM Statistics.

1. Select Subracks->Actual Board->PortDevice tab->NID LM tab and choose an LM

session Name drop-down list.

2. Click Statistics button next to the Session status LM Counters dialogue box.

IC-INST-EMXPII Rev A | 2018-12-06 131 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 69 LM Counters

CLI: Creating LM

• ::mes::cfmMep:remotemep identifier::associateLM

• Follow the instructions on screen and enter values for the following parameters:
Interval, MEP id or MAC address, Set a MAC Address in case MAC was choosen
in type.

CLI: Viewing LM statitics

• ::soamPm::lmStats::mepNid:MEG Identifier:subrack:slot:MEP
identifier

IC-INST-EMXPII Rev A | 2018-12-06 132 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.18.3.4 Creating a DM Session on a NID

Perform the following steps to create an DM Session.

Starting a DM session will automatically enable that 15 minute and 24 hour periodic DM Re-
ports are generated and sent to TNM.

GUI: Creating DM

1. Select Subracks->Actual Board->PortDevice tab->NID MEP tab and choose a

remote MEP in the MEP drop-down list

2. Click Add button next to the No. of current DM Sessions field and configure the
following parameters in the Create DM dialogue.

Fig. 70 Create DM Dialogue, left: using MEP. right: specify MAC address.

DMM Interval Defines the interval of sending DMM messages to the remote DM re-
sonder. values can be 100ms, 1, 10 seconds. (default 100ms)

Type Type can be MEP or MAC address.

If MEP is chosen: The DM session will use the MAC address from the re-
mote MEP, i.e the DM session will discover the MAC address in received
Continuity Check (CCM) messages from the remote MEP and use it to ad-
dress the remote DM responder.
If MAC address is chosen: Explicitly specify a MAC address of the remote
DM responder.

IC-INST-EMXPII Rev A | 2018-12-06 133 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 71 DM Session tab after adding

CLI: Creating DM

• ::mes::cfmMep:remotemep identifier::associateDM

• Follow the instructions on screen and enter values for the following parameters:
Interval, MEP or MAC address, MAC Address, in case MAC was choosen in type.

GUI: Showing DM Statistics.

1. Select Subracks->Actual Board->PortDevice tab->NID DM tab and choose a DM

session Name drop-down list

2. Click Statistics button next to the Session statusDM Counters dialogue box.

IC-INST-EMXPII Rev A | 2018-12-06 134 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 72 DM Counters

CLI: Viewing DM statitics

• ::soamPm::lmStats::mepNid:MEG Identifier:subrack:slot:MEP
identifier

6.18.4 Delete NID configuration

As a general guideline for deleting configuration objects, any other objects referring to the cur-
rent object should be removed first. To remove a NID configuration the MEP objects must be
removed first. Likewise, LM and DM objects must be removed before parent MEP objects.

IC-INST-EMXPII Rev A | 2018-12-06 135 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Removing NID configuration

1. Select Subracks->Actual Board-> PortDevice->NID General and select the untis to

delete by clicking the checkbox to the far left.

2. Click Delete button in the bottom row.

CLI: Removing NID configuration

1. ::portDev::equipment:: delete nidGe:subrack:slot:txPort-rxPort:

vlanId

2. Follow the instructions on screen.

6.18.5 Upgrading NID firmware

This section describes how to upgrade the firmware on a NID. The NID has two memory
banks, one which is active and one which is inactive. Installing a new firmware on the NID will
replace the firmware in the inactive slot. The new firmware is not activated until the activate
action is performed.

The activation step will result in a traffic affecting reboot of the NID.

6.18.5.1 Preparations
The firmware for the NID has to be placed on EMXP/IIe before it can be installed and activated
on the NID.

CLI: Placing the firmware on EMXP/IIe

1. In CLI, placing the firmware for the NID using command: swu install appl
subrack.slot path of the firmware package on the tftp server

IC-INST-EMXPII Rev A | 2018-12-06 136 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 73 Placing Firmware on EMXP/IIe

Refer to the Upgrade Instruction for further information regarding tftp server

6.18.5.2 Upgrading NID firmware

GUI: Upgrading NID firmware

1. Select Subracks->Actual Board->PortDevice tab->NID General tab

2. Click Upgrade button in the bottom row and input the following parameters in the
Upgrade firmware dialogue.

The upgrade procedure can take up to 10 minutes, a progress bar will show the progress.
Once the upgrade procure has started, do not shut down the progress dialogue.

IC-INST-EMXPII Rev A | 2018-12-06 137 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 74 Upgrade Firmware dialogue

Port device Defines the Port Device to be upgraded

Action Sets the action to be performed:

Install will upload the firmware file to the NID and install it in the inactive
memory bank.
Activate activates the firmware that is in the inactive memory bank.
Install and activate will sequentially first upload the new firmware to the
NID and then activate it.
File Specifies which firmware file to install on the NID.

IC-INST-EMXPII Rev A | 2018-12-06 138 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Upgrading NID firmware

Upgrading NID firmware using the CLI always requires the install and activate steps to be
performed individually.

1. ::portDev::fw::NID name::installFw

2. Follow the instructions on screen and enter values for the following parameters: File.
To get the paths to firmware files available on the system one can run the ::
portDev::fw::NID name::getAllFiles command.

3. The installation process takes some time and can be tracked under ::portDev::
fw::NID name::. Once it is done you can proceed with the activation.

4. ::portDev::fw::NID name::activateFw

5. Confirm that you want to activate the firmware that is currently in the inactive slot by
typing yes in the query. The activation step will cause the NID to cold start.

6.18.6 Restart NID

NID can be restarted separately from the EMXP/IIe. It usually takes several minutes for the re-
start process to be completed.

A cold restart affects traffic.

IC-INST-EMXPII Rev A | 2018-12-06 139 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Restart NID

1. Select Subracks-> Actual Board-> PortDevice-> NID General tab.

2. Click Restart button on the bottom row..

3. Select the NID to restart in the Port device drop-down list.

4. Select the type of restart in the Restart type drop-down list.

CLI: Restart NID

1. ::portDev::generic::portDevGeneric:subrack:slot::
restartPortDevice

2. Follow the instructions on the screen.

6.18.7 Creating an iSFP port device

The iSFP enables efficient and cost-effective transport of SONET/SDH signals on CWDM or
DWDM networks, without the need to sacrifice additional wavelength.

Note that it is important that a networking carrying Ethernet encapsulated SONET/SDH is

synced or there will be traffic outages.

IC-INST-EMXPII Rev A | 2018-12-06 140 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating iSFP

1. Select Subracks->Actual Board->PortDevice tab->iSFP General tab

2. Click Create

3. Choose Device type and Port

4. If a channelized iSFP is selected, some additional channel parameters need to be set.

Choose Administrative status, Base VLAN Id, Ether type and Vlan Priority

Fig. 75 Create iSFP dialogue

Device type The type of port device to be created and managed

Port The port in which the iSFP is inserted

Administrative The initial administrative status setting of all channels of this iSFP.
status
Base VLAN ID The first VLAN ID in a range that will be applied to the channels. The chos-
en value will be used as VLAN ID on channel 1 and the next VLAN ID in
the range will be used on channel 2 and so on.

Ether type Specifies the ether type to be used for the VLAN of each channel on this
iSFP.
VLAN priority Specifies the Vlan priority (PCP) of each channel on this iSFP.

CLI: Create port device

• ::portDev::generic::portDevGeneric:subrack:slot::createPortDevice

• Follow the instructions on screen and enter values for the following parameters:
DeviceType and Port. If choosing a channelized iSFP DeviceType then also enter the
following parameters: Administrative status, Base VLAN Id, Ether type and Vlan
Priority.

IC-INST-EMXPII Rev A | 2018-12-06 141 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.18.8 Configure iSFP

GUI: Enable/Disable destination MAC address check

• Select Subracks->Actual Board->PortDevice tab->iSFP General tab.

Fig. 76 iSFP General dialogue

Destination If enabled, for each received packet the destination MAC address is com-
MAC address pared with the device MAC address. In case the addresses are not equal,
check the packet is not processed.

CLI: Enable/Disable destination MAC address check

set ::portDev::equipment::iSFP:subrack:slot::
destinationMacAddressCheck <enable/disable>

6.18.9 Configure iSFP IWF

The Interworking Function (IWF) is the function that handles the encapsulation and decapsu-
lation between the optical TDM signal and the emulated ethernet stream. The number of inter-
working functions per iSFP varies based on the Device Type. A clear-channel iSFP will have
just one IWF object for the whole interface while a channelized iSFP will have one IWF object
for each channel.

GUI: iSFP General

• Select Subracks->Actual Board->PortDevice tab->iSFP IWF tab.

IC-INST-EMXPII Rev A | 2018-12-06 142 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 77 iSFP STM-1 IWF

Fig. 78 iSFP E1 IWF

Destination The destination MAC address inserted into the transmitted packets of this
MAC address IWF.
VLAN ID Specifies the VLAN ID used to VLAN tag the transmitted packets of this
IWF.
Ether type Specifies the ether type used by this IWF.

VLAN priority Specifies the VLAN priority (PCP) used by this IWF.

RTP clock Specifes which side the plug will use as clock source. If set to ethernet the
source sync will be taken from the EMXP. If set to TDM then the iSFP will take the
sync from the optical SDH side.

Jitter buffer Function to re-center position of jitter buffer. Setting of this object triggers
recenter recentering of the jitter buffer to the default position.

The above are all the parameters available for different types of IWFs. Some parameters are
only available for IWF of channelized iSFPs and some are only available for clear-channel
iSFPs.

CLI: Set destination MAC address

set ::portDev::iwf::<IWF name>::destinationMacAddress <MAC address>

IC-INST-EMXPII Rev A | 2018-12-06 143 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Set VLAN ID

set ::portDev::iwf::<IWF name>::vlanId <VLAN ID>

CLI: Set Ether type

set ::portDev::iwf::<IWF name>::etherType <Ether type>

CLI: Set VLAN Priority

set ::portDev::iwf::<IWF name>::priority <VLAN priority>

CLI: Set RTP clock source

set ::portDev::iwf::<IWF name>::rtpClockSource <RTP clock source>

CLI: Recenter jitter buffer

set ::portDev::iwf::<IWF name>::jitterBufferRecenter recenter

Recentering the jitter buffer is a service-affecting operation.

6.18.10 Reset PM counters

GUI: iSFP General

• Select Subracks->Actual Board->PortDevice tab->iSFP PM IWF tab.

Fig. 79 iSFP PM IWF dialogue

Reset Setting of this object to 'reset' invokes a reset of the counters for this IWF
channel.

IC-INST-EMXPII Rev A | 2018-12-06 144 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

CLI: Reset PM counters

set ::portDev::iwfPm::iSFP:subrack:slot::reset reset

IC-INST-EMXPII Rev A | 2018-12-06 145 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.19 Error Propagation

Error Propagation provides means for information transfer between instances that otherwise
are independent of each other.

6.19.1 Creating an Error Propagation Entry

Perform the following steps to create an Error Propagation Entry. For more information on Er-
ror Propagation, refer to the Technical Description EMXP/II.

GUI: Creating Error Propagation

1. Select Subracks->Actual Board->Policy tab->Error Propagation tab

2. Click Create button and configure the following parameters in the Create Error
Propagation Object dialogue.

Fig. 80 Create Error Propagation Object Dialogue

Trigger type The Trigger type (MEP status, Port Status, MEP CSF or LAG State
Change) for the Error Propagation Object.
Trigger type MEP status will trigger on RDI and CCM timeout.
Trigger type Port Status will trigger on link down.
Trigger type MEP CSF will trigger on the CSF faults – LOS, FDI and RDI.
Trigger type LAG State Change will trigger when going to/from LAG failure
or when an associated MC-LAG changes status from active to standby or
the opposite.

Trigger MEP/ The remote MEP, Port or LAG to trigger upon.

Trigger port/
Trigger LAG

IC-INST-EMXPII Rev A | 2018-12-06 146 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Action type The action to perform when the trigger is activated (Laser Shutdown, Send
Csf, Flush MAC table, Flush All MAC Entries or Flush ERPv2).
If action type Send Csf is selected, the frame sent will be CSF-LOS.
If Mac Flush is selected, the VLAN of the triggering remote MEP is se-
lected as the VLAN to flush.
Action port/ The port, local MEP or ERPv2 ring to perform the action upon.
Action MEP/
Action ERP
Hold-off time Defines the Hold-off time (0–10000ms) from activated trigger to action.

Admin status Defines whether or not the Admin status for the error propagation object is
Up or Down. Default is Up.

CLI: Creating Error Propagation

• mes::misc::misc:subrack:slot::associateErrorProp

• Follow the instructions on screen and enter values for the following parameters:
Trigger type, Trigger MEP/Trigger port, Action type, Action port/Action
MEP, Hold-off time and Admin status.

IC-INST-EMXPII Rev A | 2018-12-06 147 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.20 Mgmt VLAN Configuration

This section describes how to configure Mgmt VLAN functionality in the TU

6.20.1 Creating management VLAN channel on client ports

There are some prerequisites to creating a management VLAN channel on a port. First, man-
agement VLAN has to be enabled on node level. Second, management VLAN has to be en-
abled on the TU. If a TU is used in standalone mode further steps have to be performed when
enabling management VLAN on the TU. Refer to Designing DCN Network plans in the system
manual for more information.

Note that only EMXP80/II does not support management VLAN functionality.

When changing Mgmt VLAN configurations , the CU must be restarted before the new settings
are applied. This CU restart is not service affecting for CU systems, reboot of CULESS sys-
tems are however service affecting.

6.20.2 Enabling Management VLAN – Node Level

Management VLAN on node level is disabled by default. Enabling and disabling is controlled
by the managementVlan parameter in the node.
Management VLAN is enabled by changing managementVlan parameter to bridge2dcn.

GUI: Enabling Management VLAN on Node Level

1. Select Subracks

2. Set Management VLAN to bridge2dcn.

CLI: Enabling Management VLAN on Node Level

• set ::eq::node::0::managementVlan bridge2dcn

When management VLAN is disabled, the VLAN support is disabled in the node, in the CU
switch and the TUs.

6.20.3 Enabling Management VLAN – TU Level

This setting enables or disables the management VLAN function on the TU. It will only take ef-
fect if management VLAN is enabled on node level.
Management VLAN on the TU is disabled by default.

IC-INST-EMXPII Rev A | 2018-12-06 148 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Enabling Management VLAN on TU Level

1. Select Actual Board->Misc tab.

2. Set Administrative state to up and click Apply.

CLI: Enabling Management VLAN on TU Level

• set ::mes::misc::misc:subrack:slot::adminStatus up

If the TU is used in standalone mode then an IP address and netmask must be set in “misc”
before setting it to adminstatus up. The IP address should be specified in the DCN Network/
node plan. The IP address should also be different from the node IP address

GUI: Setting misc IP address and netmask

1. Select Actual Board->Misc tab.

2. Click Change Mgmt VLAN IP address.

CLI: Setting misc IP address and netmask

• ::mes::misc::misc:subrack:slot::configureAddress

6.20.4 Enabling Management VLAN – Port Level

This setting enables or disables the management VLAN function on each individual client
port.
Management VLAN on the TU is disabled by default.

GUI: Enabling Management VLAN on TU Level

1. Select Actual Board->VLAN tab->Mgmt VLAN tab.

2. Select port and set Administrative status to up and click Apply.

CLI: Enabling Management VLAN on a port

• set ::mes::mgmtVlan::subrack:slot:portNr::adminStatus up

If the Mgmt VLAN is to be protected by an ERP instance, the ERP should be configured before
enabling Mgmt VLAN on the ERP ports.

6.20.5 Changing Management VLAN Settings – Port Level

The settings for a management VLAN port can be changed. The settings are:

IC-INST-EMXPII Rev A | 2018-12-06 149 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

mgmtVlanEther- The ether type of the management VLAN.

Type

mgmtVlanId The VLAN ID of the management VLAN.

mgmtVlanPriori- The PCP encoded to the management VLAN tags.

ty

GUI: Changing Management VLAN

1. Select ->Subracks->VLAN tab->Management VLAN.

2. Select the port in the Name drop-down list and configure the VLAN settings.

CLI: Changing Management VLAN

• ::mes::mgmtVlan::mgmtVlan:subrack:slot:portNr::configure

For more information refer to Designing DCN Network plans.

When Management VLAN is configured the MTU has to be at least 1522 bytes.

6.20.6 Configuring GbE port on EMXP40

On EMXP40, it is possible to configure how the additional GbE port should be used, it could ei-
ther be connected to the external SFP port on the front, or internally used for Management
VLAN .

GUI: Configuring GbE port usage

1. Select Subracks->Actual Board->Misc

2. Select 1 gbE port usage next and set the desired configuration.

3. Save the configuration.

4. Cold start the board.

CLI: Configuring GbE port usage

1. set ::mes::misc::misc:subrack:slot::sfpPortUsageNext <external/

mgmtVlan>

2. Save the configuration.

3. Cold start the board.

IC-INST-EMXPII Rev A | 2018-12-06 150 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.20.7 Configuring Private VLAN

It is possible to configure Private VLAN to either isolated or community. This setting is only
valid when management VLAN is enabled on the node.
The Management VLAN privacy default setting is community.

GUI: Configuring Private VLAN

• Select System -> Equipment->Mgmt VLAN privacy

CLI: Configuring Private VLAN

1. ::eq::node::0

2. set mgmtVlanPrivacy community

or set mgmtVlanPrivacy isolated

For true isolation the ports that are management VLAN enabled must not trust each other.

6.21 Configuring OpenFlow mode

From R28, EMXP/IIe TUs are possible to use in a SDN-enabled network by defining the board
as OpenFlow controlled at creation. This means that EMXP L2 dataplane functions are no lon-
ger controlled via ENM/DNA-M, but from an external SDN controller via the OpenFlow proto-
col. L1 provisioning is still managed via ENM/DNA-M.
OpenFlow is available in combination with CU-SFP/III or in a CU-less configuration with
EMXP48/IIe in the TM102/II. When an EMXP is created as OpenFlow controlled, no control
signalling, carrier Ethernet, MPLS-TP or SyncE features (including VLANS, ERPS, policing,
OAM, ESMC etc) are available to configure on the EMXP. Only board, inventory and L1/L2
port interface configuration can be done on the EMXP, everything else is expected to be
handled by an SDN controller.
The configuration flow for setting up the EMXP to be controlled via OpenFlow is described
below:

Fig. 81 Config flow for enabling OpenFlow control of an EMXP

6.21.1 L1 port configuration

L1 configuration options are the same as when running in normal mode, see section 6.4 Layer
1 Port Configuration.

IC-INST-EMXPII Rev A | 2018-12-06 151 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.21.2 L2 port configuration

L2 configuration options are a subset of available configuration when running in normal mode,
see section 6.5 Layer 2 Port Configuration.
LAG/LACP, LLDP, port modes, policing , shaping, Trust settings are not supported from ENM
in OpenFlow mode.

6.21.3 Configuring an OpenFlow logical switch

GUI: Creating Logical Switch

1. Select Subracks->Actual Board->OpenFlow tab->Switch tab..

2. Click Create and configure the following parameters in the Create Logical Switch
dialogue.

Fig. 82 Create Logical Switch dialogue

CLI: Creating Logical Switch

1. ::openflow::generic::generic:subrack:slot::createOfLs

2. Follow the instruction on screen and enter values for the following parameters:
Switch Identifer, Description, MAC address.

IC-INST-EMXPII Rev A | 2018-12-06 152 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.21.4 Creating an OpenFlow controller connection

GUI: Creating OpenFlow controller connection

1. Select Subracks->Actual Board->OpenFlow tab->Switch tab.

2. Open a Logical Switch entry, click on the Create controller connection button and
configure the following parameters in the Create controller connection dialogue.

Fig. 83 Create controller connection

CLI: Creating controller connection

1. ::openflow::logicalSwitch::ofls:switchId::associateCxn

2. Follow the instructions on screen and enter values for the following parameters:
Description, Controller IP address and Controller TCP port.

6.22 Configuring NETCONF for use by Xceed

It is possible to use NETCONF with Xceed for all EMXP generation II boards.

NETCONF mode SHOULD only be used with Xceed.

IC-INST-EMXPII Rev A | 2018-12-06 153 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.22.1 Setting NETCONF mode using GUI

GUI: Setting NETCONF mode

1. Select IP->General

2. Change the NETCONF mode to enabled/disabled.

3. Select to reboot the CU.

6.22.2 Setting NETCONF mode using CLI

CLI: Setting NETCONF mode

1. set ::ip::general::netconfMode enabled

2. Reboot the CU

IC-INST-EMXPII Rev A | 2018-12-06 154 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.23 Configuring PPP over Ethernet

This section describes how to configure PPPoE over EMXP

EMXP/II and EMXP/III units does not support PPPoE functionality.

A logical switch is a prerequisite for PPPoE in OpenFlow mode. See 6.21.3 Configuring an
OpenFlow logical switch.

Normal Mode Support:

• NNI: Both S-tag and C-tag works
• UNI-mux: Not supported
• UNI: Not supported
OpenFlow Mode Support:
• Default Mode: Both S-tag and C-tag works
• XCEED ‘NNI’ port: Only S-tag

It is mandatory to use same ether type on both sides of PPP links.

6.23.1 Creating PPPoE using GUI

There are two ways to create PPPoE from the ENM GUI, via the EMXP PPP tab or using DCN
configuration. The procedures are valid for Normal mode as well as the OpenFlow controlled
variant.

GUI: Creating PPPoE

1. Select Subrack->Actual Board->PPP tab

2. Click Create and configure the parameters in Create PPP Link.

Fig. 84 Creating PPPoE link

IC-INST-EMXPII Rev A | 2018-12-06 155 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Port Port where to create ppp link

VLAN ID Link specific Vlan Id

Ether type Select the ether type for Vlan

Create PPPoE from DCN tab:

1. Select Management Network->DCN->PPP tab

2. Click Create.

3. Select Subrack and Slot where the EMXP board is present and configure the
parameters in Create PPP Link.

Fig. 85 Create PPPoE Link Object Dialogue from DCN tab

Subrack Subrack number

Slot Slot number
Board Type Select the Board (EMXP)

Port Port where to create ppp link

VLAN ID Link specific VLAN Id

Ether type Select the ether type for Vlan

6.23.2 Creating PPPoE using CLI

CLI: Creating PPPoE Link

1. create ::dcn::ppp::ppp:port:<subrack>:<slot>:<txPort>:vlan:
<vlanId>:<etherType>
Example: create ::dcn::ppp::ppp:port:1:10:3:vlan:4093:qTag0x8100

IC-INST-EMXPII Rev A | 2018-12-06 156 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

Fig. 86 CLI Example – creating PPPoE Link

6.23.3 Verifying PPP links and default gateway

To verify IP connectivity, perform the following steps:

Check PPP and gateway in CLI

1. Navigate to
::ip::route::

2. Verify PPP- and gateway connectivity by checking the Operational status for those
interfaces.

Check PPP and gateway in GUI

1. Select Management network->IP->Route

2. Verify PPP- and gateway connectivity by checking the Operational status for those
interfaces.

IC-INST-EMXPII Rev A | 2018-12-06 157 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

6.24 Configuring Topology Entries

Topology entries are needed for the DNA-M to be able to route a service through the network.
The topology entries define the physical and logical topology of a Infinera network. There are
three types of topology entries defined that are used to describe how nodes, ports and client
systems are connected:
• Internal – describes how units are connected within a node. Start- and end-points are regis-
tered using the notation: subrack-slot-port
• Peer – describes connections between Infinera nodes. The start-point uses the notation:
subrack-slot-port and the end-point use the notation IP-address-subrack-slot-port
• Client – describes how a bi-directional client signal is connected to a Infinera node. The cli-
ent system is identified with an index and optionally either an arbitrary descriptive string or
IP-address and interface index. For both directions the network side uses the notation: sub-
rack-slot-port

Fig. 87 Topology Entries

If Dynamic Network Administrator - Metro (DNA-M) is available, it can be used to configure the
topology. For more information, refer to the DNA-M User Guide.

6.24.1 Creating an Internal Entry

Perform the following steps to create an internal entry.

CLI: Creating Internal Topology Entry

1. ::topo::internal

2. create int:<fromsubrack>:<slot>:<port>:<tosubrack>:<slot>:
<port>
Example: ::topo::internal
create ::int:2:5:1:1:5:1

IC-INST-EMXPII Rev A | 2018-12-06 158 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating Internal Topology Entry

• Select Topology->Internal tab. Click Create.

• Enter Subrack, Slot and Port for the internal topology and click Apply.

6.24.2 Creating a Peer Entry

The peer entry is created by specifying start point of the line fiber in the node and end-point in
another node. If a fiber-pair is used for a link, peers must be added for both directions.
Perform the following steps to create a peer entry.

CLI: Creating a Peer Topology Entry

1. ::topo::peer

2. create peer:<localsubrack>:<slot>:<port>:<remotesubrack>:<slot:
port>
Example: create peer:1:16:4:1:15:5

3. Enter a local label, remote label and remoteIp. ::topo::peer::peer:

<localsubrack>:<slot>:<port>:<remotesubrack>:<slot>:<port>
Example: create peer:1:16:4:1:15:5
set remoteLabel Husqvarna_tx
set localLabel Bankeryd_rx
set remoteIp 172.16.1.111
set descr Husqvarna Bankeryd Peer

A local label in a node must be the same as the remote label in the other end of a peer. Labels
must also be unique within a node.

IC-INST-EMXPII Rev A | 2018-12-06 159 (167)

Infinera Proprietary and Confidential
 CONFIGURATION

GUI: Creating a Peer Topology Entry

1. Select Topology->Peer tab. Click Create.

2. Enter Local: Subrack, Slot, Port, Label and Remote: IP and Label.

6.24.3 Creating a Client Entry

CLI: Creating a Client Topology Entry

1. ::topo::client

2. create client:<subrack>:<slot>:<inport>:<subrack>:<slot>:
<port>:<outport>:<channelId>
Example: create client:1:5:2:1:5:1:0

GUI: Creating a Client Topology Entry

1. Select Topology->Client tab. Click Create.

2. Enter Subrack, Slot and Port for Rx and Tx.

After the client has been created some more optional data can be configured, client descrip-
tion (In the GUI this can be done when creating the client), remote IP address and remote
Interface.

IC-INST-EMXPII Rev A | 2018-12-06 160 (167)

Infinera Proprietary and Confidential
 COMMISSIONING OF EMXP/II

7 Commissioning of EMXP/II
This section describes the commissioning of the TU. The following instructions requires that
the installation of the TU has been completed.
The commissioning steps can be divided into two steps:
1. Node Preparations and Acceptance Tests, see Node Preparations and Acceptance Tests
2. Network Acceptance Tests, see Network Acceptance Tests

Be careful when inspecting equipment and optical fibers that are connected to a node. A laser
beam could be harmful to the eyes.

7.1 Node Preparations and Acceptance Tests

7.1.1 Verifying Corrrect SFP/XFP
Inspect that the correct SFP/XFP have been installed in the correct ports according to the
XFP/SFP plan. Check the transceiver class of the client and line ports.

GUI: Checking transceiver class

1. Select Subracks->Actual TU->Port tab->L1 tab.

2. Select the port in the Name drop-down list and check the Transceiver class

CLI: Checking transceiver class

• show ::client::if::client:subrack:slotNr:txPort-rxPort::trxClass

7.1.2 Verifying Internal Fiber Connections

The internal fiber connections are either factory pre-installed or should be installed according
to fiber connection plans according to internal patch plan and commission report.

Verify that the internal fiber connections are correct according to an internal patch plan

Make sure to always clean the fiber before inserting the fiber into any equipment.

7.1.3 Measuring Optical Power

Optical power measurements of the node should be performed to ensure that the cabling and
attenuators has been installed correctly in the system and that incoming and outgoing signals
have the correct power. To confirm and collect data, a commission report can be created.

IC-INST-EMXPII Rev A | 2018-12-06 161 (167)

Infinera Proprietary and Confidential
 COMMISSIONING OF EMXP/II

Table 6 Commission Report Example

Testpoint (subrack:slot: Transponder/Muxponder/CU Nominal Power Measured Power

port) (dbm) (-1 dBm to +3 dBm from
nominal)

1:2:1 1:2:21 -3

1:1.2 1:2:22 -10

1:2:2 1:2:21 -12

1:2:4 1:2:4 -12

Table 6 Commission Report Example is to be used for non-amplified networks only, for infor-
mation regarding test specifications in amplified networks, see Installation and Commissioning
Amplified Links.

Measuring Optical Power

1. Connect the optical power meter to the port that is to be tested.

2. If the port is a client port set ALS to disabled. Select Equipment->TU->Line tab. Selec the
port from the Name drop-down list->set Laser Mode to on and click Apply.

3. Check the output power on the power meter and note the value in the commissioning
report.

4. Reset Laser Mode and ALS to the settings they had before the optical power
measurement.
Perform the optical power tests for all ports. The test values should be within the limit stated in
the commissioning report.

7.1.4 Connecting Nodes

Once the optical power measurements are completed the nodes should be connected to each
other according to peer patch plan and commission report.

IC-INST-EMXPII Rev A | 2018-12-06 162 (167)

Infinera Proprietary and Confidential
 COMMISSIONING OF EMXP/II

7.1.5 Preparing for Network Acceptance Test

A network plan will help and minimize the time it takes to commission the system. An example
plan can be illustrated as in Network plan example, a Ring Network with mostly hubbed con-
nections but also one meshed connection.

Fig. 88 Network plan example

From the “Network plan” the steps in the commissioning can be decided. The suggested
method is to commission each node and prepare looping of connections so that the final sys-
tem test can be done from one site (or as few as possible).
The following is an example of the steps needed to commission the system in Fig. 88 Network
plan example.
1. Commission Sat A according to 7.1 Node Preparations and Acceptance Tests. Prepare
looping of client signals and IP setup to be able to test connection C1 from the Hub node.
2. Commission Sat B according to 7.1 Node Preparations and Acceptance Tests. Prepare
looping of client signals and IP setup to be able to test connection C2 from the Hub node.
3. Commission Sat C according to 7.1 Node Preparations and Acceptance Tests. Prepare
looping of client signals and IP setup to be able to test connection C4 from the Hub node.
4. Commission Sat D according to 7.1 Node Preparations and Acceptance Tests. Prepare
looping of client signals and IP setup to be able to test connection C5 from the Hub node.
Test connection C3 according to 7.2 Network Acceptance Tests
5. Commission the Hub node according to 7.1 Node Preparations and Acceptance Tests. Test
connection C1, C2, C4 and C5 according to 7.2 Network Acceptance Tests.
6. Prepare the system for operation according to 7.3 Preparing the System for Operation.
7. Remove connected unnecessary Ethernet cables.
The system is now ready to accept client traffic.

7.1.6 Preparing Cabling for End to End Test

Looping of the client circuits can be made using the built-in loopback function for the board

7.1.7 Near End Loop Back

Perform the following steps to enable near end loop back:

IC-INST-EMXPII Rev A | 2018-12-06 163 (167)

Infinera Proprietary and Confidential
 COMMISSIONING OF EMXP/II

1. Select Subracks->Actual Board->Port tab->L1 tab.

2. Select the port from the Name xxxdrop-down list, set Near end loopback to enabled
and click Apply.

7.2 Network Acceptance Tests

The Network acceptance tests consists of link, protection and management connectivity tests.

7.2.1 Connecting traffic analyzers for end to end test

When the remote end of the connection is looped, the test equipment can be connected in the
node where the test is to be performed. Each channel is tested separately.

7.2.2 Verifying error free line traffic

When the line signals are connected you can verify that the line connection is bit-error free us-
ing a BER instrument and checking that the PM counters does not increase on the TU
Perform the following steps:

Check error free traffic in CLI

1. show ::performance::g826::<client/line>*:<subrack>:<slot>:<i/f>

2. Check that the values for client- and/or line ports do not increase between the
measurements

3. Perform a stability test of the unprotected channel.

Check error free traffic in GUI

1. Click Performance on the left menu, push Refresh a number of times to see if any of
the error counters are changing.

2. Check that the values for client- and/or line ports do not increase between the
measurements

3. Perform a stability test of the unprotected channel.

IC-INST-EMXPII Rev A | 2018-12-06 164 (167)

Infinera Proprietary and Confidential
 COMMISSIONING OF EMXP/II

7.2.3 Verifying Management Channels

To verify a management VLAN channel on a remote managed Infinera product use ping.

7.3 Preparing the System for Operation

When the commissioning is finished, the nodes are ready for operation. To take the nodes into
operation, perform the following steps:

1. Set Administrative Status for each TU to up. This is done in ENM GUI Board view for
each board

2. Disable near end loopback on looped clients.

3. Verify that the client power levels are according to the commissioning report.

4. Save, reboot all nodes one by one, check alarms and upload the configuration. See 7.3.1
Save, reboot, check alarms and upload

IC-INST-EMXPII Rev A | 2018-12-06 165 (167)

Infinera Proprietary and Confidential
 COMMISSIONING OF EMXP/II

7.3.1 Save, reboot, check alarms and upload

1. Save the configured data.

2. Optional step: Reboot all nodes one by one and verify that the correct configuration is
loaded.

Rebooting a node with EMXP units may result in a traffic hit, see Technical
Description for more information about Hitless Software Upgrade.

It may take up to 4 minutes for the GCC link on a FXP400GOTN or

MXP200GOTN unit to recover after reboot.

Reboot the node in the following way in ENM GUI: Click Software Control, select
Reboot from the multi-set drop-down list and click Apply.

3. Wait until the node is started again and login again.

Contact with other nodes during the reboot might be lost if using in-band
channels for data-communication. The connection will be restored after the
reboot.

4. Check that no configuration has been changed.

5. Check the alarm list in each node and verify that no unexpected alarms exist. Select
Alarms in top right corner in ENM GUI.

6. Save the configuration files so the node can quickly be restored. To be able to restore a
node from configuration files a tftp-server is needed on a remote system. See 7.3.1.1
Upload Configuration Files.

IC-INST-EMXPII Rev A | 2018-12-06 166 (167)

Infinera Proprietary and Confidential
 COMMISSIONING OF EMXP/II

7.3.1.1 Upload Configuration Files

1. Click Backup control->Remote Backup tab.

2. Enter a Server address to the tftp-server.

3. Enter a Server path where the files are to be saved to the tftp-server.

4. Enter the Hour when the backup package should be transferred. The hour is set to 23 by
default.

5. Select Upload and click Apply.

It is possible to upload the configuration files periodically.

IC-INST-EMXPII Rev A | 2018-12-06 167 (167)

Infinera Proprietary and Confidential