1KHW028635 FOX61x OPIC2 D

—
USER MANUAL
FOX61x
OPIC2, opic2_r1c
Optical Teleprotection, Packet Services,
4 Ports
OPIC2 User Manual
Document ID 1KHW028635
Document edition FOX61x System Release: R1 and R2 and R3

Revision: D
Date: 2018-12-13
Copyright and confidentiality Copyright in this document vests in ABB Switzerland Ltd (hereinafter referred to
as ABB).
Manuals and software are protected by copyright. All rights reserved. The copy-
ing, reproduction, translation, conversion into any electronic medium or
machine scannable form is not permitted, either in whole or in part. The con-
tents of the manual may not be disclosed by the recipient to any third party,
without the prior written agreement of ABB.
An exception is the preparation of a backup copy of the software for your own
use. For devices with embedded software, the end-user license agreement on
the enclosed CD applies.
This document may not be used for any purposes except those specifically
authorized by contract or otherwise in writing by ABB.
Disclaimer ABB has taken reasonable care in compiling this document, however ABB
accepts no liability whatsoever for any error or omission in the information con-
tained herein and gives no other warranty or undertaking as to its accuracy.
ABB can accept no responsibility for damages, resulting from the use of the net-
work components or the associated operating software. In addition, we refer to
the conditions of use specified in the license contract.
ABB reserves the right to amend this document at any time without prior notice.
The product/software/firmware or the resulting overall solution are designed
for data processing and data transmission and may therefore be connected to
communication networks. It is your sole responsibility to provide and continu-
ously ensure a secure connection between the product/software/firmware or
the resulting overall solution and your network or any other networks (as the
case may be). You shall establish and maintain any appropriate measures (such
as but not limited to the installation of firewalls, application of authentication
measures, encryption of data, installation of anti-virus programs, etc.) to pro-
tect the product/software/firmware or the resulting overall solution, the net-
work, its system and all the interfaces against any kind of security breaches,
unauthorized access, interference, intrusion, leakage and/or theft of data or
information. ABB and its affiliates are not liable for damages and/or losses
related to such security breaches, any unauthorized access, interference, intru-
sion, leakage and/or theft of data or information.
Although ABB provides functionality testing on the products including related
firmware and software that we release, you should institute your own testing
program for any product updates or other major system updates (to include but
not limited to firmware/software changes, configuration file changes, third
party software updates or patches, hardware exchanges, etc.) to ensure that
the security measures that you have implemented have not been compromised
and system functionality in your environment is as expected.
Copyright © 2018 ABB 2

FOX61x | OPIC2 CONTENTS
Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 Precautions and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Symbols and Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Interfaces and Circuit Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
1.5 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
1.6 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Unit View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 Functions and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1 Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Slots for the OPIC2 Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3 SFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.1 SFP Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.2 SFP Module Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.3 Optical Attenuators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4 Interoperability and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.1 FOX51x and FOX61x Teleprotection Units . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.2 Previous ESW Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5 Connections and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.1 Front Connectors of the OPIC2 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.2 Optical TPE Interface Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.5.3 Optical IRIG-B Output Cable V9PT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5.4 Electrical IRIG-B Output Cable V9IR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5.5 Fixing the Cables to the Cable Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.1 IEEE C37.94 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.2 Communication Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2.3 FOX6plus Frame Compatible ABB Teleprotection Equipment Application . . . . . . 24
5.2.4 Transmission Protocol / Frame Structure. . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2.5 P0_nc (nx64 kbit/s) Applications via the FOX61x TDM Bus (PBUS). . . . . . . . . . . 25
5.2.6 P12 (2048 kbit/s) Applications via the FOX61x TDM Bus (PBUS) . . . . . . . . . . . . 27
5.2.7 IRIG-B Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3.1 Optical Teleprotection Equipment (TPE) Interface . . . . . . . . . . . . . . . . . . . . 30
5.3.2 PBUS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3.3 IRIG-B Output Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4.1 Circuit Emulation Service (CES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4.2 Trail Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.4.3 Unit Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.4.4 IRIG-B Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1 Commissioning of Teleprotection Equipment Links . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.2 IEEE C37.94 Application with RED670 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.3 IEEE C37.94 Application with NSD570 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2018-12-13 3
6.4 ABB TPE Application with REL551 and REL316*4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.5 ABB TPE Application with NSD570 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.6 Differential Protection over E1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.7 Differential Protection over E0 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.8 Differential Protection over X.24-V.11 Interface 1984kbit/s . . . . . . . . . . . . . . . . . . . . . 66
6.9 Differential Protection over 2/4-wire Analog Interface . . . . . . . . . . . . . . . . . . . . . . . 69
6.10 Basic MPLS-TP Configuration for a Redundant OPIC2 Link . . . . . . . . . . . . . . . . . . . . . 72
7 Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.1 Unit Optical Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.2 Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.3 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.3.1 Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.3.2 Unit ESW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8 User Interface Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.2 AP: /unit-x: OPIC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.2.1 AP: /unit-x, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.2.2 AP: /unit-x, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.2.3 AP: /unit-x, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.2.4 AP: /unit-x, Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.2.5 AP: /unit-x, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.3 AP: /unit-x/port-y (y = 1 … 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.3.1 AP: /unit-x/port-y, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.3.2 AP: /unit-x/port-y, Main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.3.3 AP: /unit-x/port-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.3.4 AP: /unit-x/port-y, Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.3.5 AP: /unit-x/port-y, Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.4 AP: /unit-x/port-5: IRIG-B (IRIG-B opt.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.4.1 AP: /unit-x/port-5, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.4.2 AP: /unit-x/port-5, Main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.4.3 AP: /unit-x/port-5, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.4.4 AP: /unit-x/port-5, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.5 AP: /unit-x/port-6: IRIG-B (IRIG-B el.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.5.1 AP: /unit-x/port-6, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.5.2 AP: /unit-x/port-6, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.5.3 AP: /unit-x/port-6, Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.5.4 AP: /unit-x/port-6, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.6 AP: /unit-x/circuitEmulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.6.1 AP: /unit-x/circuitEmulation, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.6.2 AP: /unit-x/circuitEmulation, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.6.3 AP: /unit-x/circuitEmulation, Fault Management . . . . . . . . . . . . . . . . . . . . . 99
8.7 AP: /unit-x/circuitEmulation/cesop-z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.7.1 AP: /unit-x/circuitEmulation/cesop-z, Overview . . . . . . . . . . . . . . . . . . . . . 99
8.7.2 AP: /unit-x/circuitEmulation/cesop-z, Main . . . . . . . . . . . . . . . . . . . . . . . . 99
8.7.3 AP: /unit-x/circuitEmulation/cesop-z, Configuration . . . . . . . . . . . . . . . . . 100
8.7.4 AP: /unit-x/circuitEmulation/cesop-z, Fault Management . . . . . . . . . . . . . . 104
8.7.5 AP: /unit-x/circuitEmulation/cesop-z, Status . . . . . . . . . . . . . . . . . . . . . . 106
8.8 AP: /unit-x/circuitEmulation/cesop-z/chan-c . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.8.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Overview . . . . . . . . . . . . . . . 108
8.8.2 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Main . . . . . . . . . . . . . . . . . . 109
8.8.3 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Configuration . . . . . . . . . . . . 109
8.8.4 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Fault Management . . . . . . . . . 110
8.8.5 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Performance Management . . . . 111
8.8.6 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status . . . . . . . . . . . . . . . . . 112
8.9 AP: /unit-x/vlanInterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.9.1 AP: /unit-x/vlanInterfaces, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.9.2 AP: /unit-x/vlanInterfaces, Main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.10 AP: /unit-x/vlanInterfaces/vif-z_v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2018-12-13 4
8.10.1 AP: /unit-x/vlanInterfaces/vif-z_v, Overview . . . . . . . . . . . . . . . . . . . . . . . 113

8.10.2 AP: /unit-x/vlanInterfaces/vif-z_v, Main . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.10.3 AP: /unit-x/vlanInterfaces/vif-z_v, Configuration . . . . . . . . . . . . . . . . . . . . 114
8.10.4 AP: /unit-x/vlanInterfaces/vif-z_v, Fault Management . . . . . . . . . . . . . . . . . 114
8.10.5 AP: /unit-x/vlanInterfaces/vif-z_v, Performance Management . . . . . . . . . . . . 115
8.10.6 AP: /unit-x/vlanInterfaces/vif-z_v, Status. . . . . . . . . . . . . . . . . . . . . . . . . 115
9 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
9.1 Associated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
2018-12-13 5
FOX61x | OPIC2 PREFACE
1 Preface
1.1 Precautions and Safety

Before you handle any equipment you must comply with the safety advices.
Adherence to the safety instructions ensures compliance with the safety requirements as
defined in EN 60950 (Safety of Information Technology Equipment).
Please refer to the following document:
[1KHW002497] Operation Instruction “Precautions and Safety”.
1.2 Symbols and Notations

This User Manual uses the following symbols:
Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.
→ Possible actions are given.
Please note:
Shows significant information.
→ Possible actions are given.
1.3 Interfaces and Circuit Categories

Table 1: Electrical interfaces and circuit categories
OPIC2 interface Circuit category Max. rating
according to EN 60950-1
Voltage Current
Local power supply TNV2 < 72 VDC < 0.1 A
IRIG-B output SELV 5V < 0.2 A
Table 2: Optical interfaces

OPIC2 interface Parameter Range Remark
Optical 2 Mbit/s 1 Laser class 12
(according to EN 60825-1)
Optical transmitted power 3 - 7 dBm maximum value
Transmitted wavelength 850 nm multi-mode
1310 nm single-mode
2018-12-13 6
Table 2: Optical interfaces (continued)

OPIC2 interface Parameter Range Remark
IRIG-B output, 100 bit/s Laser class 1M safe for all conditions of use
(according to EN 60825-1) except when passed through
magnifying optics
Optical transmitted power 4 - 15.8 dBm 50/125 µm fiber, NA 5 = 0.2
-12.0 dBm 62.5/125 µm fiber, NA = 0.275
-8.5 dBm 100/140 µm fiber, NA = 0.3
-4.5 dBm 200 µm fiber, NA = 0.37
Transmitted wavelength 820 nm multi-mode,
non-visible radiation
Compatible fibers 50/125 µm,
62.5/125 µm,
100/140 µm,
200 µm PCS PCS = plastic-clad silica
1. The listed optical properties are related to the SFPs plugged in the OPIC2 unit.
2. As the laser protection class 1 is complied, dangerous radiation cannot be emitted. Thus, special precautions
for failures or laser warnings are not necessary.
3. Optical transmitted power, modulation and wavelengths are typical values for SFP modules, however these val-
ues may vary depending on SFP types and manufacturers.
Please refer to SFP manufacturers data sheets for more details.
4. Typical values at 25 °C with 60 mA forward current, 1 m of cable.
5. Fiber NA is measured at the end of 2 m of mode stripped fiber, using the far-field pattern. NA is defined as the
sine of the half angle, determined at 5% of the peak intensity point. When using other manufacturers cable, re-
sults will vary due to differing NA values and specification methods.
1.4 Document History

Table 3: Document history
Document ID Rev. Date FOX61x Changes since previous version
Release
1KHW028635 D August 2018 R3A Minor editorial changes
1KHW028635 3 March 2018 R2D System test performed on FOX61x release R2D.
New company branding for user manual.
1KHW028635 2 March 2017 R2C Add information about E1 transparent support.
Add additional legacy interface support description.
Add additional commissioning examples for various
interfaces.
Add delay threshold exceeded functionality descrip-
tion.
Add leap second behavior on IRIG-B output.
1KHW028635 1 March 2016 R2B First version of the document for the FOX61x
release.
1.5 Target Audience

This User Manual is targeted at persons who are entrusted with the installation, provi-
sioning, operation and administration of the system.
The persons targeted are
• the installation personnel, and/or
• the provisioning personnel, and/or
• the operation and administration personnel
2018-12-13 7
Please note:
Only trained and skilled personnel (maintenance staff as per EN 60950) may
install and maintain the system.
1.6 Definition of Terms

For an explanation of terms used in this document please refer to [1KHW028514] Informa-
tion “Terms and Abbreviations”.
Table 4: Specific terms

Term Explanation
CESM1 Designates the core and control unit CESM1 or CESM1-F of the FOX61x.
CESM2 Designates the core and control unit CESM2 or CESM2-F of the FOX61x.
Core Unit Designates the core and control unit CESM1, CESM1-F, CESM2, CESM2-F or
CESM3 of the FOX61x.
Where certain features or characteristics apply to a specific core unit only, the
CESM1, CESM1-F, CESM2, CESM2-F or CESM3 is named explicitly.
2018-12-13 8
FOX61x | OPIC2 INTRODUCTION
2 Introduction
2.1 General
This document describes the architecture and functions of the OPIC2 unit and shows how
this unit is commissioned and operated as part of the FOX61x.
The OPIC2 unit is a 1-slot wide service unit of FOX61x and provides 4 optical teleprotec-
tion interfaces complying to IEEE C37.94 (IEC 62843) standard or to the proprietary trans-
mission protocol (ABB TPE) for differential protection applications. In addition to the
optical front port, access to the PBUS is possible and provides differential protection
application on P0_nc (nx64 kbit/s) level or P12 level over an E1 interface.
• OPIC2 supports C37.94 and ABB TPE for differential protection application over 4 opti-
cal front ports.
• OPIC2 supports various legacy interfaces for differential protection applications. The
legacy interfaces are accessed over the FOX61x internal TDM bus (PBUS).
• The WAN transport channels of the OPIC2 unit are packet based. The OPIC2 unit com-
municates to the core unit over an internal 1GbE backplane interface.
The teleprotection signals accessed by the OPIC2 unit can be transported via a high speed
packet switched network, e.g. the teleprotection signals are transported over an MPLS-TP
network.
Alternatively the Ethernet frames can also be transported via an SDH network using the
EoS function, as long as each network element is synchronized to one common timing
source.
FOX61x FOX61x
teleprotecti on Core GbE Packet GbE Core teleprotection
TPE OPIC2
Unit Network Unit OPIC2 TPE
Figure 1: OPIC2 used as access to teleprotection equipment (TPE)
To enhance the systems availability the OPIC2 unit provides redundant transmission trail
configuration and provides hitless protection switchover in case of a failure.
2018-12-13 9
2.2 Unit View
Figure 2: OPIC2 unit view
Figure 2 shows the OPIC2 unit hardware. On the front plate are two LEDs for unit- and
traffic failure indication, 4 SFP cages, electrical and optical IRIG-B Outputs.
2018-12-13 10
2.3 Block Diagram
P0_nc terminated
PBUS Cross 4 x P12 (nx64 kbit/s)
Connect P12 transparent
(2048 kbit/s)
Double GbE Star
Circuit Emulation Service 1

- Hitless protection TPE interface 2
2 x GbE
GbE MUX - Authentication - IEC 37.94 3
Front Connectors
- Performance Monitoring - ABB TPE 4
- ARP handling (MAC discovery)
IRIG-B Output 5
optical
Host processor Date and Time Processing
Backplane access
IRIG-B Outputs 6
electrical
Subrack internal
communication
Power
Figure 3: OPIC2 block diagram
Figure 3 shows the block diagram of the OPIC2 unit. The main functions of the OPIC2 unit
can be divided into the following parts:
• 4 optical TPE interfaces consisting of SFP slots for plugging optical transceivers. The
interfaces can individually be configured as IEEE C37.94 interfaces or as ABB TPE inter-
faces.
• 4 PBUS interfaces accessing the PBUS on the backplane for nx64 kbit/s or 2048 kbit/s
legacy applications.
• IRIG-B output interfaces to synchronize user equipment in the substation
• Circuit Emulation Service (CES) for asynchronous network access of synchronous user
data
• Redundant core unit interface for protection
• Unit synchronization and supervision to provide accurate timestamps to CES and IRIG-
B, and to detect core unit failure conditions
2018-12-13 11
FOX61x | OPIC2 FUNCTIONS AND SPECIFICATIONS
3 Functions and Specifications

The OPIC2 unit provides the following functions and conforms to the corresponding stan-
dards and recommendations (conformance to applicable parts of the standards).
3.1 Feature Licenses

Part of the FOX61x functionality is subject to feature licenses. For more information on
feature licenses please refer to [1KHW028777] Release Note “FOX61x”.
3.2 Specification
The OPIC2 unit provides the following functions and supports the following standards:
Table 5: Functions and specifications

Feature Rating or standard Release
SFP interfaces 4x optical teleprotection interfaces compatible to IEEE C37.94 r1b
(IEC 62843) standard or to the proprietary FOX6plus compati-
ble optical transmission protocol (ABB TPE)
Circuit emulation service (CES) Proprietary procedure r1b
- Frame size: 1 to 32 time slots
- Payload size: 1 to 8 frames
- Jitter buffer depth: 20 ms
TDM bus access 4x 2 Mbit/s r1b
- Transport modes nx64 kbit/s, n = 1 … 32 r1b
2048 kbit/s, transparent r1c
- Cross connections Flexible cross connections for TDM signals on the P0_nc layer r1b
Flexible cross connections for TDM signals on the P12 layer r1c
Optical IRIG-B output One optical IRIG-B output: r1b
- Connector type: ST
- Wave length range: 792 … 865 nm
- Center wave length: 820 nm
Electrical IRIG-B outputs Six isolated electrical IRIG-B outputs with common ground: r1b
- Signal level high: 5 V
- Signal level low: high impedance
- Maximum current per output: 200 mA
- Maximum current summed over all outputs: 600 mA
Maintenance functions
- Loops on the CES layer - Loop 2b: Remote loop, back-to-back r1b
- Loop 3b: Local loop, front-to-front
- TDM delay threshold supervision - Configurable safety margin for TDM delay supervision r1c
- Individual per CESoP instance
Protection
- Hitless protection Hitless protection for each CESoP instance r1b
- Switching time Hitless protection r1b
Cyber security
- Authentication Traffic authentication with 256 bit AES r1b
Alarm reporting ITU-T X.733 (1992) r1b
Information technology – open systems interconnection – sys-
tems management: Alarm reporting function
Power consumption
- Power supply range VBAT -39.5 VDC … -72 VDC r1b
2018-12-13 12
FOX61x | OPIC2 FUNCTIONS AND SPECIFICATIONS
Table 5: Functions and specifications (continued)

Feature Rating or standard Release
- Maximum total power requirement 8.5 W r1b
from battery, PTOT (VBAT = nominal
voltage)
Mechanical parameters
- Construction practice 19 inch r1b
- Height of unit (1 HU = 44.45 mm) 6 HU r1b
- Width of unit (1 TE = 5.08 mm) 4 TE (1 slot) r1b
- Size of the PCB (H x D) 233 mm x 220 mm r1b
- Weight 400 g r1b
- RoHS Directive 2011/65/EC of the European Parliament and of the r1b
Council of 1.07.2011 on the Restriction of the use of certain
hazardous substances in electrical and electronic equipment
- WEEE Directive 2011/65/EC of the European Parliament and of the r1b
Council of 13.08.2012 on waste electrical and electronic equip-
ment
Reliability
- Calculated MTTF at 35 °C 100 years r1b
(MIL-HDBK-217F)
Emission refer to [1KHW002460] System Description “FOX61x” r1b
Immunity refer to [1KHW002460] System Description “FOX61x” r1b
Safety refer to [1KHW002460] System Description “FOX61x” r1b
Ambient conditions refer to [1KHW002460] System Description “FOX61x” r1b
2018-12-13 13
FOX61x | OPIC2 INSTALLATION
4 Installation
4.1 Prerequisites
Before installing, OPIC2 unit take care to follow the safety advice as listed in
[1KHW002497] Operation Instruction “Precautions and Safety”.
Valid combinations of hardware (HW) and embedded software (ESW) versions are given in
[1KHW028777] Release Note “FOX61x”.
For the installation of FOX61x HW
• refer to [1KHW002461] Installation Instruction “FOX615 Installation”, and
• refer to [1KHW002462] Installation Instruction “FOX612 Installation”.
4.2 Slots for the OPIC2 Unit

The OPIC2 unit uses one slot in the FOX61x subrack.
In a FOX61x, the OPIC2 unit can be operated in any of the following slots:
• FOX615: 1 … 10, 12, 14 … 21
• FOX612: 7 … 10, 12, 14
For more information regarding the PBUS access and the cross connections please refer
to [1KHW002467] User Manual “TDM Services”.
For more information regarding supported network topologies and network require-
ments please refer to [1KHW028636] Application Note “Design Guide for MPLS-TP based
Utility Networks”.
4.3 SFP Modules
4.3.1 SFP Interface Types

OPIC2 has four SFP cages where different SFP modules for the two applications can be
inserted.
All recommended SFP modules are designed in conformance with the SFP Multi-Source
Agreement (SFF document INF-8074i) and are hot pluggable, i.e. they can be installed and
removed from an operational OPIC2 unit.
The supported SFP modules can provide the following interfaces:
• 2 Mbit/s interface SFP modules
− 1KHW001871R0005: IEEE C37.94 optical port (850 nm, multi mode, up to 2 km)
− 1KHW001872R0001: ABB TPE optical port (1310 nm, single mode, up to 30 km)
Please note:
Only SFP modules recommended by ABB can guarantee the specified func-
tionality of the OPIC2 unit.
→ In order to get the latest list of ABB’s recommended SFP modules please
contact your local ABB representative.
4.3.2 SFP Module Mounting

A plugged SFP module is secured in the SFP cage by a locking mechanism. To remove the
SFP module from the SFP cage this locking must be released. There are different, non-
standardized, methods to release this locking mechanism:
• with a bail (generally used on optical SFP modules), or
2018-12-13 14
• with a unlocking actuator (generally used on electrical SFP modules).

No tool or equipment is required to install or remove an SFP module.
4.3.2.1 SFP Module with Bail Actuator

To insert an SFP module with bail actuator, the bail latch should be in the locked position.
The module is oriented so that the bail is on the right side of the SFP. The module is
pushed into the SFP cage carefully until a clicking sound indicates that the module is
locked.
SFP module SFP module
bail in locked position bail in open position
install remove
Tx Tx
Rx Rx
Figure 4: SFP module handling
After disconnection of the optical cable, SFP modules can be removed from the SFP cage
by using the metal bail latch located on the right side of the SFP module. Pull on the bail to
unlock and remove the SFP module.
Please note:
To protect optics, dust covers should always be installed when cables are not
connected.
Please note:
Unplugged SFP modules should be stored in an ESD safe environment.
4.3.2.2 SFP Module with Unlocking Actuator

To insert SFP modules with unlocking actuator, the module is oriented so that the unlock-
ing actuator is on the left side of the SFP. The module is pushed into the SFP cage care-
fully until a clicking sound indicates that the module is locked.
SFP module
with unlocking actuator
push
install remove
Tx Tx
Rx Rx
Figure 5: SFP module handling
2018-12-13 15
The SFP modules can be removed from the SFP cage by pushing the unlocking actuator
and then pulling on the module itself or the electrical cables to remove the SFP module.
Please note:
Unplugged SFP modules should be stored in an ESD safe environment.
4.3.3 Optical Attenuators

For very short fiber links, optical attenuators may need to be inserted on the SFP trans-
mitter, depending on the TPE receiver robustness.
The following optical attenuators are indicated:
• For IEEE C37.94 interfaces with 2 Mbit/s interface SFP modules 1KHW001871R0002:
− 1KHW001878R0010: 10dB LC/PC (850 nm, multi mode)
• For ABB TPE interfaces with 2 Mbit/s interface SFP modules 1KHW001872R0001:
− 1KHW001997R0010: 10dB LC/PC (1310 nm, single mode).
With the following SFP no optical attenuator is needed:
• IEEE C37.94 interfaces with 2 Mbit/s interface SFP modules 1KHW001871R0005.
4.4 Interoperability and Compatibility
4.4.1 FOX51x and FOX61x Teleprotection Units

OPIC2 IEEE C37.94 interfaces and ABB TPE interfaces cannot inter-operate with OPTIF
and/or OPIC1.
4.4.2 Previous ESW Revisions

Contact ABB for the newest OPIC2 unit ESW release compatible with the FOX61x system
release.
4.5 Connections and Cables
4.5.1 Front Connectors of the OPIC2 Unit

OPIC2 has four optical interfaces on the unit front, designated from bottom up with port-
1 to port-4. The optical interface connectors are provided by the pluggable SFP modules.
The optical interfaces are equipped with industry standard duplex LC connectors.
OPIC2 has one optical IRIG-B outputs and six galvanic isolated IRIG-B outputs with com-
mon ground.
2018-12-13 16
R1A
1KHWxxx
Connector port-6,
untiltet front view
Notch for the A B C D

cable latching
1
clip
2
3
port-6
4
6
port-5
optical
port-4 Tx
Rx
port-3
port-2
port-1
Figure 6: OPIC2 front panel and interface connectors
Table 6: OPIC2 port-6 front connector pins

IRIG-B signal Connector pin for
signal + signal -
IRIG-B1 A1 C1
IRIG-B2 A2 C2
IRIG-B3 A3 C3
IRIG-B4 A4 C4
IRIG-B5 A5 C5
IRIG-B6 A6 C6
2018-12-13 17
Please note:
Tx corresponds to the optical transmitter output on the receive path towards
the TPE.
Rx corresponds to the optical receiver input on the transmit path from the
TPE.
4.5.2 Optical TPE Interface Cables

The SFP modules provide the optical interfaces for the multi mode and/or single mode
optical fibers to be connected.
The OPIC2 optical cables require standard duplex LC connectors and can be terminated
with duplex LC, ST, FC/PC or E2000 connectors on the other end, depending on the termi-
nation required.
Duplex ST connector Duplex LC connector
Figure 7: Duplex LC to ST adapter cable
Reference numbers:
• outside the cabinet, multi mode: V9YE/1KHW001862R00YY
Please note:
This cable type is indicated for the direct connection of OPIC2 IEEE C37.94
SFP interfaces with a corresponding TPE complying with IEEE C37.94 stan-
dard connectors (e.g. RED670), placed outside the communication cabinet.
Dual FC-PC connector Duplex LC connector
Figure 8: Duplex LC to FC/PC adapter cable
Reference numbers:
• inside the cabinet, single mode: V9KW/1KHW001323R00YY
• outside the cabinet, single mode: V9KZ/1KHW001326R00YY
Please note:
These cable types are indicated for the direct connection of OPIC2 ABB TPE
SFP interfaces with a corresponding ABB TPE which generally provide FC/PC
connectors on single mode fibers, placed inside or outside the same commu-
nication cabinet (e.g. REL316).
Duplex LC connector Duplex LC connector
Figure 9: Duplex LC to LC cable
Reference numbers:
• inside the cabinet, multi mode: V9YG/1KHW001874R00YY
• inside the cabinet, single mode: V9KU/1KHW001321R00YY
• outside the cabinet, multi mode: V9YF/1KHW001873R00YY
• outside the cabinet, single mode: V9KX/1KHW001324R00YY
2018-12-13 18
Please note:
These cable types are indicated for the direct connection of OPIC2 SFP inter-
faces with a corresponding TPE also providing SFP interfaces, placed inside
the same communication cabinet or outside (e.g. NSD570 with G1LOa inter-
face).
Please note:
The above cables can be ordered directly from ABB.
Please note:
YY of the ordering number is a placeholder for the length of the cable in
meters (R0010 corresponds to a 10 meter cable).
4.5.3 Optical IRIG-B Output Cable V9PT

The optical IRIG-B cable connects to the IRIG-B output port-5 of the OPIC2 unit.
CAUTION
LASER
1M
Figure 10: Class 1M laser
Please note:
As a Class 1M laser product, the IRIG-B output is considered non-hazardous.
Hazard increases if viewed with optical aids including magnifiers, binoculars,
or telescopes.
The optical IRIG-B cable requires a standard simplex ST connector and can be terminated
with a simplex LC, ST, FC/PC or E2000 connector on the other end, depending on the ter-
mination required.
ST connector ST connector
Figure 11: Simplex ST to ST adapter cable
Reference numbers:
• outside the cabinet, multi mode: V9PT/1KHW028398R00YY
Please note:
YY of the ordering number is a placeholder for the length of the cable in deci-
meters (R0010 corresponds to a 1 meter cable).
4.5.4 Electrical IRIG-B Output Cable V9IR

The Electrical IRIG-B output cable V9IR interfaces six galvanically isolated Electrical IRIG-B
outputs to the OPIC2 unit. The cable is available in 3 m and 20 m length. The cable is avail-
able as not terminated which has to be terminated on a Krone or R&M Block.
4.5.5 Fixing the Cables to the Cable Tray

The optical cables must be attached to the cable tray of the FOX615 or the corresponding
device of the FOX612.
2018-12-13 19
Figure 12 shows the cable/cable tray assembly of the FOX615. For additional information
refer to [1KHW002461] Installation Instruction “FOX615 Installation”.
When operating the OPIC2 unit in a FOX615, the cables must be attached to the cable tray
as shown in Figure 12.
<x> mm
Figure 12: Side view of the cable tray and the cables in FOX615
The open cable length <x> between the cable fixing point on the cable tray and the con-
nector depends on the connected interface.
Please note:
The cable route on the cable tray should follow approximately the projection
of the unit slot on the cable tray.
Please note:
Do not exceed the specified bending radius or squeeze the optical fibers
when fixing the fibers to the cable tray.
Stressing the fibers in excess to the specified parameters or squeezing the
fibers can permanently degrade the performance of the optical fibers.
With the FOX612 the cable tray functionality is implemented differently and depends on
the type of installation (rack-, wall-mounted). For more information on fixing the cables
with the FOX612 refer to [1KHW002462] Installation Instruction “FOX612 Installation”.
2018-12-13 20
FOX61x | OPIC2 FUNCTIONAL DESCRIPTION
5 Functional Description
This section gives the detailed functional description of the OPIC2 unit as teleprotection
application unit in the FOX61x subrack.
5.1 Introduction
The OPIC2 unit supports up to 4 optical teleprotection interfaces complying to IEEE
C37.94 (IEC 62843) standard or to the proprietary FOX6plus compatible optical transmis-
sion protocol (ABB TPE) on every unit.
OPIC2 has also an access of 4x2 Mbit/s towards the FOX61x internal cross connection
backplane (PBUS) allowing for full 2 Mbit/s user access per circuit emulation service chan-
nel. On the P0_nc layer the OPIC2 unit supports applications with 1 … 32x 64 kbit/s. On
the P12 layer the OPIC2 unit supports applications with 2048 kbit/s.
OPIC2 is a teleprotection interface card which emulates the optical and electrical TDM
user data to Ethernet packets for transport in packet switched wide area network (WAN).
This operation is called circuit emulation service (CES) or circuit emulation service over
packet switched network (CESoP). Note that OPIC2 accesses the GbE star on the back-
plane to send/receive traffic with a line rate of 1 Gb/s.
CESoP is protected by authentication so no change in the frame content during message
transport in WAN is possible without the right authentication key.
The following protection features of CESoP help to enhance the systems availability:
• Hitless end to end WAN protection with constant and symmetrical end to end delay for
both data paths.
• Core unit redundancy to access WAN during core unit failure scenarios.
CESoP provides performance management to inform the user about following statistics,
graphs and alarms that are available per user port/VLAN interface:
• Number of transmitted, received, delayed and lost packets
• Minimum, average, maximum delay, delay variation of the received packets
• Packet delay variation and packet loss variation graphs
• Packet delay and packet loss histograms
• Excessive packet loss and excessive packet delay alarms
• Configured packet delay exceeded alarm for network health information
OPIC2 CESoP communication is based on unicast, which brings the requirement to resolve
the destination OPIC2 MAC address. OPIC2 addresses this problem by having an ARP han-
dling mechanism in each CESoP.
OPIC2 CESoP offers also “trail supervision” as an additional safety service by insertion and
assertion of unique trail identifiers in the OPIC2 frames per direction.
In OPIC2, configurable electrical and optical IRIG-B outputs complying to the B002/B006
framing are available on the front plate.
OPIC2 CESoP and IRIG-B output generation only work when the unit is Time-of-Day syn-
chronized to a grandmaster clock over PTP. Accordingly, OPIC2 has a built-in unit synchro-
nization and supervision logic which is responsible for:
• supervise synchronization and liveness signals received from core unit
• provide the synchronized Time-of-Day information to CESoP and IRIG-B generation
• provide any synchronization failure to CESoP and IRIG-B generation in order to stop the
service
• provide any core unit failure to CESoP in order to switch between redundant core units
The following diagram summarizes all the applications and functionalities to support
these applications and their section/clause numbers:
2018-12-13 21
IEEE C37.94 ABB TPE nx64 kbit/s 2048 kbit/s IRIG-B

Applications section 5.2.1 section 5.2.3 section 5.2.5 section 5.2.6 section 5.2.7
Optical TPE Interface PBUS Interface IRIG-B Interface

Interfaces section 5.3.1 section 5.3.2 section 5.3.3
Circuit Emulation Unit Synchronization

IRIG-B Generation
Functions Service and Supervision
section 5.4.1 section 5.4.3 section 5.4.4
Performance ARP Handling

Authentication Protection
Monitoring (MAC Discovery)
section 5.4.1.1 section 5.4.1.2 section 5.4.1.3 section 5.4.1.4
WAN Core Unit

Redundancy Redundancy
section 5.4.1.2.1 section 5.4.1.2.2
Figure 13: Supported applications and functions of OPIC2
5.2 Applications
5.2.1 IEEE C37.94 Application

This type of fiber optic interface serves for interconnecting different vendor’s teleprotec-
tion equipment, in particular line differential protection equipment complying with IEEE
C37.94 standard to a FOX61x network.
5.2.1.1 Transmission Protocol / Frame Structure

The IEEE C37.94 frame structure is designed to allow the passage of information in packet
format from the multiplexer to the teleprotection equipment and from the teleprotection
to the multiplexer equipment. The format was chosen so that:
• The frame is a valid International Telecommunications Union (ITU-T) recommendation
G.704 pattern from the standpoint of framing and data rate. However, the data struc-
ture is not a standard data format.
• The bit pattern would have approximately equal ones and zeros (for transmission
through AC coupled optical circuits).
• The frame would have an easily detected bit pattern for frame synchronization.
• The frame structure is identical in both directions. The frame is the same size and for-
mat regardless of the number of 64 kbit/s timeslots being utilized.
• The frame is 256 bits and is repeated at a frame rate of 8000 Hz.
The resultant bit rate is 2048 kbit/s.
The frame consists of three sections: the header, the overhead data, and the channel data
arranged as shown in Figure 14.
2018-12-13 22
Time
0 µs 125 µs 250 µs 375 µs 500 µs

256 bit frame
16 bits Header (sync)

a b c d e fg h0 0 0 0 1 11 1 48 bits Overhead
pp qq rr ss 10 10 10 10 10 … 10 192 bits Channel Data (payload)
D1D1 D2D2 D3D3 D4D4 … D96D96
Figure 14: IEEE C37.94 frame structure
5.2.1.2 Header
The 16-bit header is a unique bit pattern to allow the receiver to synchronize to the 256-bit
frame. The header is 16 bits with the following format.
abcdefgh00001111
The first eight bits a, b, c, d, e, f, g, h form one of two patterns that alternate with every
other frame. This is done to ensure compliance with ITU-T recommendation G.704.
The two patterns are:
Pattern 1: abcdefgh=10011011
Pattern 2: abcdefgh=11y11111
• y = Yellow Alarm bit
− = 0 for normal;
− = 1 if receiving bad signal (LOS declared)
The second eight bits are
00001111
in every frame.
The receiver shall acquire frame sync by pattern matching to
1100001111
5.2.1.3 Overhead Data

This 48-bit section includes bits for providing information between the multiplexer and
teleprotection equipment. Each data bit is followed by its complement (for 24 actual bits
of information).
The data currently assigned comprise:
• p q r s = number of used time slots (N = 1 to 12, p is the most significant bit)
− 0 0 0 1, for N = 1
− 0 0 1 0, for N = 2
− …
− 1 1 0 0, for N = 12
5.2.1.4 Channel Data

This 192-bit section comprises 96 data bits, with each data bit followed by its comple-
ment.
The first N times 8 data bits carry the N times 64 kbit/s data.
The remaining 96 – (N times 8) data bits are set to 1.
2018-12-13 23
5.2.1.5 Trail Frame Alignment

Note that the standard does not require multiplexer equipment to provide end-to-end
frame alignments; i.e., there is no requirement that a frame’s first data bit D1 at the
source site appears as a frame’s first data bit D1 at the destination site.
5.2.2 Communication Failure Scenarios
5.2.2.1 Loss of Signal (LOS)

It is important that a low-level signal (e.g., from a deteriorating optical fiber) does not
result in garbled data for more than a few milliseconds.
Therefore the receiver will rise a LOS within 1 ms after receiving two or more errors in
eight consecutive framing patterns or directly through the SFP module (“LOS” according
to MSA INF-8074i).
The receiver will clear LOS upon receiving eight consecutive correct framing patterns or
when the SFP module clears the LOS.
5.2.2.2 Signal Failure Actions

During LOS condition at its optical receive port:
• The data bits over the higher order communications link are replaced with “ALL 1,”
which is commonly referred to as Alarm Indication Signal or AIS.
• Change the “Yellow” bit in the transmitted optical output frames from “0” to “1”.
During the loss of the higher order communications link:
• The data bits in the transmitted optical output frames are replaced with “ALL 1”.
5.2.2.3 Trail “Yellow” Detection (Far End Alarm)

The receiver declares trail “Yellow”:
• When three consecutive received frames have the “Yellow” bit = 1 AND the received sig-
nal is OK (no LOS).
(however the received data timing may be free-running, at ±100 ppm)
The receiver clears trail “Yellow”:
• When three consecutive received frames have the “Yellow” bit = 0 OR the received sig-
nal is bad (LOS).
5.2.3 FOX6plus Frame Compatible ABB Teleprotection Equipment Application

This type of fiber-optic interface serves for interconnecting different ABB teleprotection
equipment (implementing the FOX6plus compatible optical transmission protocol) to a
FOX61x network, in particular
• the Numerical Line Protection REL 316,
• the Line Differential Protection Terminals REL551/REL561, and
• the Teleprotection Equipment NSD570/NSD70D.
5.2.4 Transmission Protocol / Frame Structure

The frame structure is designed according to ABB’ Safety Frame Concept implemented
for FOX6plus/FOX20. The relevant bits of this frame for communication with REL 316,
REL551/REL561 and NSD570/NSD70D are mentioned in the following paragraphs:
• The frame is 32 bits and is repeated at a frame rate of 64 kHz.
The resultant bit rate is 2’048 kbit/s.
The frame consists of synchronizing bits, signaling bits and data bits as shown in Figure
15.
2018-12-13 24
SYNC BIT "0"
SYNC BIT "0"
SYNC BIT "0"
SYNC BIT "0"

REMOTE BIT
SYNC BIT "1"
SYNC BIT "1"
SYNC BIT "1"

SYNC BIT "1"
8 kHz Clock
PARITY BIT
CH 2
CH 1
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
"0"
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Synchronizing bits
Signaling bits
Data bits
Data bits = "0"
Figure 15: ABB proprietary SFC frame structure
5.2.4.1 Synchronizing Bit

8 specific bit form a unique pattern to allow the receiver to synchronize to the 32-bit
frame. The pattern is composed as follows:
• Bit 1, 14, 21 and 29 are set to 0,
• Bit 2, 3, 4 and 5 are set to 1.
5.2.4.2 Signaling Bits

The following bits are used for signaling:
• Bit 6: 8 kHz Clock
For the transmission of a byte, the 8 kHz clock is mapped as follows:
8 kHz Clock 1 1 1 0 0 0 0 1
Data Bit (LSB first) 0 1 2 3 4 5 6 7
• Bit 7: Remote Bit

This bit is set by the sender, whenever it is in alarm condition and is interpreted as
“Remote Defect Indication” by the receiver, when set.
• Bit 32: Parity Bit
Even parity over the whole frame (Bit 1 … Bit 31) determines the value of this bit.
5.2.4.3 Data Bits

The remaining of the safety frame is used for data transmission. Since OPIC2 does not
support interconnection of ABBs FOX6plus Multiplexer Equipment but only ABBs Telepro-
tection Equipment, only 2 data channels are used:
• Bit 18: Data Channel 1
• Bit 17: Data Channel 2
5.2.4.4 Not Used Bits

Since OPIC2 does not support interconnection of ABBs FOX6plus Multiplexer Equipment
but only ABBs Teleprotection Equipment, the following bits of the frame are not used and
shall be set to 0:
• Bit 8…13, 15, 16, 19, 20, 22…28, 30 and 31 are set to 0.
5.2.5 P0_nc (nx64 kbit/s) Applications via the FOX61x TDM Bus (PBUS)
OPIC2 supports nx64 kbit/s applications via cross connections created on the internal
FOX61x bus between OPIC2 and other TDM service units such as LECO1, LEDS1, LEDA1 and
2018-12-13 25
LEDE1. OPIC2 provides this functionality mainly to support relays communicating with
legacy protocols such as Codirectional G.703, X.24-V.11 and 2/4-wire analog interfaces.
In order to access the PBUS, following application and service unit combinations are pos-
sible for teleprotection operation by such relays:
• Codirectional G.703 with LECO1 at P0_nc line rate (n = 1)
• X.24-V.11 with LEDS1 at P0_nc line rate (n = 1 … 31)
• 2/4-wire analog voice channel with LEDA1 at P0_nc line rate (n = 1)
• nx64kbit/s channel with LEDE1 at P0_nc line rate (n = 1 … 31)
Please check Figure 16 to see the use cases of OPIC2 with nx64 kbit/s legacy applications.
FOX61x
Protection 2/4 wire
LEDA1
Relay
P0_nc
Protection E0 Codir G.703
LECO1
Relay GbE
OPIC2 Core
Unit
GbE s tar
Protection E1 G.703
LEDE1
Relay
PBUS
Protection V.11 - X.24

LEDS1
Relay
MPLS-TP
Network
FOX61x
Protection 2/4 wire
LEDA1
Relay
P0_nc

LECO1
Relay
OPIC2 Core GbE
Unit
GbE s tar
Protection E1 G.703
LEDE1
Relay
PBUS

LEDS1
Relay
Figure 16: OPIC2 use cases for nx64 kbit/s applications
Through the PBUS, OPIC2 can serve four nx64 kbit/s applications using its P0_nc line rate.
Please note:
For further information on the framing and timing in the PBUS please refer to
[1KHW002467] User Manual “TDM Services”.
Please note:
For further information on the supported service units by OPIC2 for TDM
communication, please refer to:
LECO1: refer to [1KHW002481] User Manual “LECO1”
LEDS1: refer to [1KHW002478] User Manual “LEDS1”
LEDA1: refer to [1KHW002479] User Manual “LEDA1”
LEDE1: refer to [1KHW002473] User Manual “LEDE1”

LECO1, LEDS1, LEDA1, LEDE1 and OPIC2 must be plugged into the same sub-
rack!
2018-12-13 26
5.2.6 P12 (2048 kbit/s) Applications via the FOX61x TDM Bus (PBUS)
OPIC2 supports the P12 application via cross connections created on the PBUS between
OPIC2 and the E1 service unit LEDE1. OPIC2 provides this functionality mainly to support
relays communicating with legacy protocols such as an E1 interface.
In order to access the PBUS, following application are possible for teleprotection opera-
tion by E1 relays:
• E1 channel with LEDE1 at P12 line rate (2 Mbit/s)
Please check Figure 17 to see the use case of OPIC2 with a P12 legacy application.
FOX61x
P12
Protection E1 G.703
OPIC2 Core GbE
LEDE1
Relay Unit
GbE s tar
PBUS
MPLS-TP
Network
FOX61x P12
Protection E1 G.703
LEDE1 OPIC2
Core GbE
Relay Unit
GbE s tar
PBUS
Figure 17: OPIC2 use case for P12 application
Through the PBUS OPIC2 can serve four P12 applications using its P12 line rate.
Please note:
For further information on the framing and timing in the PBUS please refer to
[1KHW002467] User Manual “TDM Services”.
Please note:
For further information on the supported service unit by OPIC2 for TDM com-
munication, please refer to [1KHW002473] User Manual “LEDE1”.

LEDE1 and OPIC2 must be plugged into the same subrack!
5.2.7 IRIG-B Output

The IRIG time codes were originally developed by the Inter-Range Instrumentation Group
(IRIG) in order to provide a way to encode/decode time-of-year information.
The latest version is IRIG standard 200-04, “IRIG Serial Time Code Formats” updated in
September, 2004.
IRIG-B is one of the 6 existing IRIG code formats which are defined by different pulse rates
as shown below:
Table 7: IRIG Formats

Format Pulse Rate Index Count Interval
IRIG-A 1000 PPS (pulse per second) 1 ms
IRIG-B 100 PPS 10 ms
IRIG-D 1 PPM (pulse per minute) 1 minute
IRIG-E 10 PPS 100 ms
IRIG-G 10000 PPS 0.1 ms
2018-12-13 27
Table 7: IRIG Formats (continued)

Format Pulse Rate Index Count Interval
IRIG-H 1 PPS 1 second
Note that the OPIC2 unit supports only the IRIG-B format.
5.2.7.1 Signal Identification Numbers

In addition to the letter used to designate one of the six IRIG code formats, signal identifi-
cation numbers are used to further describe specific characteristics. Thus, the complete
IRIG time code designation consists of a letter and three digits, as shown below.
Format (A, B, C, D, E, F, G or H)
Modulation
Carrier Frequency / Resolution
Coded Expressions
B 0 0 6
Table 8: IRIG signal identification numbers (3 digits)

1st Digit Modulation
0 Unmodulated – DC Level Shift (DCLS), pulse-width coded
1 Amplitude modulated, sine wave carrier
2 Manchester modulated
2nd Digit Carrier frequency/resolution
0 No carrier (DCLS)
1 100 Hz / 10 ms resolution
2 1 kHz / 1 ms resolution
3rd Digit Coded expressions
0 BCDTOY, CF, SBS
1 BCDTOY, CF
2 BCDTOY
3 BCDTOY, SBS
4 BCDTOY, BCDYEAR, CF, SBS
5 BCDTOY, BCDYEAR, CF
6 BCDTOY, BCDYEAR
7 BCDTOY, BCDYEAR, SBS
where
• BCDTOY is Time-of-Year in BCD representation.
• BCDYEAR is the years offset since the year 2000 in BCD representation.
• CF are the control functions.
• SBS are the straight binary seconds which show the Time-of-Day.
Note that the OPIC2 unit supports only the following time codes:
• IRIG-B 002 which is unmodulated, has no carrier and provides BCDTOY
• IRIG-B 006 which is unmodulated, has no carrier and provides BCDTOY and BCDYEAR
2018-12-13 28
5.2.7.2 IRIG-B 002/006 Framing

An IRIG-B frame is composed of pulse-width modulated signals as shown in Figure 18:
Time Frame 1 second, Index Count 0.01 seconds
0 10 20 30 40 50
On time
Ref. marker Seconds Minutes Hours Days
1 2 4 8 10 20 40 1 2 4 8 10 20 40 1 2 4 8 10 20 1 2 4 8 10 20 40 80 100 200
P0 P1 P2 P3 P4 P5
50 60 70 80 90 0
Years Control Functions Time of Day, straight binary seconds (17 bits)
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 2 4 8 10 20 40 80 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
P5 P6 P7 P8 P9 P0
Figure 18: Sample IRIG-B frame
Depending on the pulse width of the signals, following symbols are encoded in an IRIG-B
frame:
• “0” = 2 ms active high in 10 ms = shows a binary “Zero” for one bit of the coded expres-
sions (e.g. BCDTOY)
• “1” = 5 ms active high in 10 ms = shows a binary “One” for one bit of the coded expres-
sions (e.g. BCDTOY)
• “P” = 8 ms active high in 10 ms = exists between every 10 symbol, a reference marker
for 100 ms
• “R” = 2 consecutive “P” symbols = Only exists once in a second, shows the start of a
second
10 ms 10 ms
2 ms "0" binary "zero"
5 ms "1" binary "one"
8 ms "P" Position identifier
8 ms 8 ms "R" Reference marker
Figure 19: IRIG-B frame symbols
IRIG-B 002 provides only the BCDTOY information which includes seconds, minutes, hours
and days. In the OPIC2 unit, other coded expressions BCDYEAR, CF and SBS are filled with
“0” symbols when IRIG-B output interface is configured with this time format.
IRIG-B 006 provides also the BCDYEAR information in addition to BCDTOY. In the OPIC2
unit, other coded expressions CF and SBS are similarly filled with “0” symbols when IRIG-B
output interface is configured with this time format.
5.2.7.3 IRIG-B Leap Second Introduction

The basic time for mostly all of the world's local time zones is called Coordinated Univer-
sal Time, UTC, which is derived from a bunch of atomic clocks which are distributed in
several countries all over the world.
The rotation of the earth is not very constant and varies a bit over time, while decreasing
the mean rotation speed slowly. This is the reason why so called leap seconds are inserted
into the UTC time scale, they adjust process of the UTC time to the real earth rotation.
Due to the fact that the IRIG-B output on OPIC2 distribute UTC time, leap seconds would
be introduced on a non-regular basis.
2018-12-13 29
Insertion of a leap second is always scheduled for UTC midnight at the end of the last day
of a month, preferably for the last day of June or December. In the past all leap seconds
have been inserted at one of these dates. Announcements whether a leap second is
scheduled or not are published by the IERS in their Bulletin C. The current Bulletin C is pub-
lished about 6 months before the next possible date for a leap second.
Following are the description how OPIC2 insert a positive leap second into the IRIG-B out-
put frame:
Please note:
The standard way of OPIC2 IRIG-B output to count UTC time across a leap sec-
ond is:
2016-12-31 23.59.57
2016-12-31 23.59.58
2016-12-31 23.59.59
2016-12-31 23.59.60 <-- leap second
2017-01-01 00.00.00
2017-01-01 00.00.01
2017-01-01 00.00.02
5.3 Interfaces
The OPIC2 unit provides the following user interfaces for the applications specified in Fig-
ure 13:
• Optical TPE interface
• PBUS interface
• IRIG-B output interface
5.3.1 Optical Teleprotection Equipment (TPE) Interface

Optical TPE interface of OPIC2 is mainly responsible for decoding/encoding of the user
data received/sent from/to the attached teleprotection equipment. At the same time, it
is internally communicating with CES instances to further transport/receive decoded user
data to/from WAN. See Figure 20 for a visual representation of the optical TPE interface in
OPIC2.
OPIC2
FOX61x
Protection IEEE C37 .94

port-4
Relay ABB TPE
GbE s tar

port-3 Ethernet
Relay ABB TPE Optical Circuit
Core WAN interface
user Emulation
Unit
Protection IEEE C37 .94 interface Service
port-2
Relay ABB TPE

port-1
Relay ABB TPE
Figure 20: Optical user interface
OPIC2 optical user interface includes 4 independent sub-instances each of which belongs
to a dedicated user port and each of which can be independently configured as shown in
section section 8.3.3 AP: /unit-x/port-y, Configuration (on page 91).
Optical TPE interface supports decoding/encoding of the following two types of optical
protocols which can carry teleprotection data:
2018-12-13 30
• IEEE C37.94 (see section 5.2.1 IEEE C37.94 Application (on page 22))
• FOX6plus compatible ABB TPE (see section 5.2.3 FOX6plus Frame Compatible ABB
Teleprotection Equipment Application (on page 24))
Please note:
Optical interface type is configurable and each optical user interface instance
can be configured either with IEEE C37.94 or ABB TPE at a time. Please check
section 8.3.3.1 AP: /unit-x/port-y, Configuration - Interface (on page 91) to see
how to configure the interface type.
In addition to the interface type, there is one more configuration parameter through
which the number of protection channels can be set. The range for this configuration set-
ting depends on the interface type.
As described in section 5.2.1 IEEE C37.94 Application (on page 22), the IEEE C37.94 stan-
dard defines a frame format which can encode up to 96 bits of data. By decoding and
encoding IEEE C37.94 frames, the OPIC2 optical TPE interface supports the transport of
up to 12 protection channels each of which carries 8 bit user data, sent by the attached
teleprotection equipment. On the other hand, when ABB TPE is selected as the interface
type, only one channel of teleprotection data with one additional remote alarm channel
can be transported.
Please note:
ABB TPE interface can also transport remote alarm information in case
needed. It is automatically extracted from the ABB TPE frames and only
inserted in the data to be transported in WAN if the configuration parameter
“Number of Protection Channels” is set to 2. Otherwise, when it is set to 1,
only the teleprotection data will be transported without remote alarm infor-
mation.
See section 8.3.3.1 AP: /unit-x/port-y, Configuration - Interface (on page 91) for a sum-
mary of supported data rates corresponding to the supported number of protection
channels.
OPIC2 supports teleprotection equipments which are sending teleprotection data using
one of the specified protocols (IEEE C37.94 or ABB TPE). However, depending on the
equipment’s frame transmission alignment synchronization scheme, hazardous synchro-
nization loops can occur if the equipment tries to align its transmitted frame start posi-
tion to the received frame alignment from OPIC2. In order to prevent any synchronization
loops due to such teleprotection equipment, OPIC2 offers an additional configuration
parameter “FSP Loop Prevention Enabled”. Check section 8.3.3.2 AP: /unit-x/port-y, Con-
figuration - Interoperability (on page 92) to see where to set/clear it in FOXCST.
Please note:
When “FSP Loop Prevention Enabled” is set, reliable operation is guaranteed
without any frame alignment synchronization loops, however, end-to-end
transmission delay accuracy can be degraded up to 125 µs in this case.
5.3.1.1 Communication Failure Scenarios

OPIC2 optical user interface has a fault management system which detects the communi-
cation failures on the optical communication with the attached teleprotection devices.
Accordingly, OPIC2 informs the user via FOXCST with the following alarms:
• Degraded Signal (DEG)
• Data Rate Mismatch (DRM) - only for IEEE C37.94
• SFP Module Not Available (ENA)
• Loss Of Frame (LOF)
• Loss Of Signal (LOS)
• Remote Defect Indication (RDI)
2018-12-13 31
• TPE Loss Of Frame Alignment (TLOFA) - only for ABB TPE

• TPE Loss Of Synchronization (TLOS)
• Transmitter Degraded (TRDEG)
• Transmitter Failure (TRF)
• Transmitter Power Exceeded (TRPE)
Please note:
For detailed description of the optical user interface alarms, please refer to
section 8.3.4 AP: /unit-x/port-y, Fault Management (on page 92).
Please note:
Depending on the optical interface type (IEEE C37.94 or ABB TPE), available
alarms can differ (e.g. DRM only for IEEE C37.94) and the trigger conditions
for the alarms can be also different. Please refer to section 8.3.4 AP: /unit-x/
port-y, Fault Management (on page 92) for detailed information.
Please note:
In case of an alarm condition, an alarm is reported and AIS (ALL 1) is inserted
in receive and transmit direction to signal the attached protection devices
with the interruption of the teleprotection data transmission and reception.
This is done to prevent malicious data transmission to the relays during fail-
ure conditions.
5.3.2 PBUS Interface

OPIC2 provides a PBUS access at P0_nc or P12 line rate in order to transport nx64 kbit/s
(n = 1 … 32) or 2048 kbit/s legacy user data through the packet switched network.
OPIC2 has access to one physical PBUS line providing an overall bandwidth of 4x 2Mbit/s
to the user when all available timeslots are used.
OPIC2’s PBUS interface acts as a bridge between PBUS and CES, which is responsible for:
• Acting locally as a TDM service termination point for the TDM traffic that is encapsu-
lated and transport by CES
• Acting locally as a TDM service start point for the TDM traffic that is decapsulated and
transport via the PBUS
• Getting and decoding the data from the corresponding PBUS lines according to the
channel configuration and providing it to CES
• Encoding the data received from CES and putting it into the corresponding PBUS lines
according to the configuration
• Provide authentication for PBUS data over packet switched networks.
OPIC2 FOX61x
Protection 2/4 wire
LEDA1
Relay

LECO1 Ethernet
Relay Circuit
Core WAN interface
Emulation
interface Unit
GbE s tar
Protection E1 G.703 Service

LEDE1
Relay
PBUS

LEDS1
Relay
Figure 21: PBUS interface
2018-12-13 32
Communication through the PBUS is channel based and the user has to create channels
for each application separately. Please check section 8.7.3.4 AP: /unit-x/circuitEmulation/
cesop-z, Configuration – Channels (on page 102) to see how to create channels and how
to configure them.
Please note:
For a successful communication through the PBUS between service units and
OPIC2, cross connections between channels shall be created. Please refer to
[1KHW002467] User Manual “TDM Services” to see how to create cross con-
nections.
There are 4 independent PBUS interface instances in OPIC2. Each interface supports up to
32 timeslots of data that can be received/sent from/to PBUS at P0_nc or P12 line rate. In
each PBUS interface instance, towards the WAN transport transmit direction, n time slots
in a framed 2 Mbit/s signal at the PBUS are mapped to nx64 kbit/s data which is sent to
the related CES instance. On the other hand, in the WAN transport receive direction,
nx64 kbit/s data received from the CES instance are remapped to n time slots in a framed
2 Mbit/s signal.
Please note:
Overall number of timeslots existing in all channels created within one CES
instance shall be reported to the CES instance in order to encapsulate the cor-
responding amount of data from the TDM frames in Ethernet packets. This
number is automatically calculated by the OPIC2 software and transferred to
the related CES instance, no user interaction is required as in optical TPE
interface.
Please note:
The TDM interface bus is also referred as “Internal Port” interface since it pro-
vides this user access through the internal backplane connection with other
service units.
For more information regarding the PBUS access, please refer to [1KHW002467] User
Manual “TDM Services”.
5.3.3 IRIG-B Output Interface

IRIG-B subsystem in the OPIC2 unit is meant to provide OPIC2 front interface with 7 IRIG-B
outputs:
• 1 optical output via ST connector (port 5):
The transmitter of the OPIC2 unit supports multi-mode transmission at 820 nm.
• 6 electrical outputs via 24-pin connector (port 6):
All the IRIG-B outputs are galvanically isolated from all other electrical circuits on the
OPIC2 unit.
FOX61x
OPIC2
Devices with electrical IRIG-B 002/006

port-6
IRIG-B input 6x electrical IRIG-B Unit
IRIG-B
output synchronization
generation
Device with optical IRIG-B 002/006 interface and supervision
port-5
IRIG-B input 1x optical (ST)
Figure 22: IRIG-B output interface
At both ports, time format is configurable between IRIG-B002 and IRIG-B006. Please refer
to section 8.4 AP: /unit-x/port-5: IRIG-B (IRIG-B opt.) (on page 96) and section 8.5 AP: /
2018-12-13 33
unit-x/port-6: IRIG-B (IRIG-B el.) (on page 97) to see how these interfaces can be config-
ured via FOXCST.
See section 5.4.4 IRIG-B Generation (on page 45) for functional details of IRIG-B genera-
tion.
5.4 Functions
5.4.1 Circuit Emulation Service (CES)

Circuit emulation service is a telecommunication technology which enables to transport
synchronous data over asynchronous networks (e.g. Ethernet).
As being the core functionality of OPIC2, CES acts as a bridge between the user interfaces
(optical front ports or internal PBUS) and Ethernet, which encapsulates the user data-
grams into Ethernet packets in the WAN direction and which decapsulates the Ethernet
packets into user datagrams towards the attached protection device. See Figure 23 for a
visual representation.
OPIC2 FOX61x
2/4 wire 4
Protection Relay LEDA1 Circuit
Emulation
E0 Codir G.703
LECO1
3 Service
Protection Relay
PBUS
E1 G.703 interface 2
Protection Relay LEDE1 cesop-4
GbE s tar
PBUS
Source switch
V.11 - X.24 1
Scheduler
Protection Relay LEDS1 cesop-3
Core GbE
IEEE C37 .94 4 Unit
Protection Relay port-4 cesop-2
ABB TPE
IEEE C37 .94 3
Protection Relay port-3 Optical cesop-1
ABB TPE
user
IEEE C37 .94 2
Protection Relay port-2 interface
ABB TPE
IEEE C37 .94 1
Protection Relay port-1
ABB TPE source select (1 … 4)
Figure 23: Circuit Emulation Service
OPIC2’s CES implementation is based on an ABB’s innovative solution which compensates

the delay variation in the asynchronous packet switched network and provide therefore
constant end-to-end transmission delay between two communicating OPIC2 CESoP units.
Accurate timestamps are required for reliable CES operation and these timestamps are
taken from the “Unit synchronization and supervision” block. (See section 5.4.3 Unit Syn-
chronization (on page 45) for more details on the OPIC2 unit synchronization)
OPIC2 includes four independent instances of CES each of which can be independent con-
figured as shown in section 8.6 AP: /unit-x/circuitEmulation (on page 98).
Each CES instance (cesop-z) can serve one user interface (optical or internal PBUS) at the
same time. Source selection is configurable and can be done as shown in section 8.7.3.1
AP: /unit-x/circuitEmulation/cesop-z, Configuration – General (on page 100).
Please note:
Source selection configuration can be changed only when the related CES
instance (cesop-z) admin state is down.
The OPIC2 CESoP application requires different bandwidths based on the encapsulation
of TDM frames into Ethernet packets. Due to the fixed OPIC2 Ethernet packet overhead
(74 bytes, excluding interframe gap and preamble), the required bandwidth is inversely
2018-12-13 34
proportional to the number of TDM frames encapsulated in one Ethernet frame. OPIC2
offers four different configuration options (1, 2, 4 and 8) corresponding to the number of
TDM frames per Ethernet frame. See section 8.7.3.3 AP: /unit-x/circuitEmulation/cesop-z,
Configuration – CESoP (on page 101) to see how to configure this setting via FOXCST.
The number of TDM timeslots to be transported also affects the bandwidth need of
OPIC2. CES supports the encapsulation of up to 32 timeslots out of one TDM frame, which
is the maximum number of timeslots that a TDM frame can have. As described in section
5.3.1 Optical Teleprotection Equipment (TPE) Interface (on page 30) and section 5.3.2
PBUS Interface (on page 32), the teleprotection interface can generate a TDM frame with
at most 12 timeslots user data, while the PBUS interface can generate up to 32 timeslots
depending on the number of timeslots carried by the created and cross connected PBUS
channels.
Table 9 shows the bandwidth need of different configuration combinations based on
“Number of TDM frames per Ethernet packet” and “Number of Timeslots in one TDM
frame”.
Table 9: Configurable CESoP payload sizes

Source inter- Channels or TDM Packetization Payload size CESoP bandwidth per
face time slots frames delay [ms] [Byte] VLAN interface [Mbit/s]
ABB TPE or 1 1, 2, 4 or 8 0.125 … 1 1…8 0.656 … 4.800
IEEE C37.94 or
PBUS
ABB TPE or 2 1, 2, 4 or 8 0.125 … 1 2 … 16 0.720 … 4.864
IEEE C37.94 or
PBUS
IEEE C37.94 or 3 … 12 1, 2, 4 or 8 0.125 … 1 3 … 96 0.784 … 5.504
PBUS
PBUS 13 … 32 1, 2, 4 or 8 0.125 … 1 13 … 256 1.424 … 6.784
Please note:
In order to establish a running communication between 2 CES instances, both
OPIC2 instances must be configured with the same “Number of Timeslots/
Channels” and the same “Number of TDM frames per Ethernet packet”. Other-
wise the Path Capacity Mismatch (PCM) alarm will be asserted by OPIC2 to
inform the user.
OPIC2 packets cross the WAN to reach their destination OPIC2 CESoP partners. Depend-
ing on the lack of network resources and huge buffering delays in WAN, OPIC2 packets can
experience increased delays. In order to be able to work under high load conditions, OPIC2
CES also offers configurable constant end-to-end transmission delay between two com-
municating OPIC2 CES instances. Available values are 1 ms, 2 ms, 4 ms, 6 ms, 8 ms, 10 ms,
12 ms, 14 ms, 16 ms, 18 ms and 20 ms which can be configured as shown in section 8.7.3.3
AP: /unit-x/circuitEmulation/cesop-z, Configuration – CESoP (on page 101).
Please note:
In order to have a reliable differential protection application between two
relays attached to two OPIC2 units, end-to-end transmission delay must be
configured to the same value in both OPIC2 units!
CES also offers the following sub functionalities that are described in detail in the follow-
ing subsections:
• Authentication
• Protection
• Performance monitoring
• MAC address discovery
• Trail Supervision
2018-12-13 35
5.4.1.1 Authentication
For teleprotection applications, message integrity is very crucial in terms of cyber secu-
rity. Malicious commands and/or fake sampled values can lead to trips in the protection
devices. OPIC2 offers authentication as the security feature to prevent such attacks.
In order to provide high level of security, OPIC2 implements the NIST approved CMAC-
AES256 algorithm which is running with 256-bit long symmetrical keys.
Please note:
Symmetrical keys bring the requirement to configure the same key on the two
communicating CES instances. The user has to enter exactly the same keys on
both sides for correct operation. Having different keys on two sides causes
the EAF (Excessive Authentication Failure) alarm.
In OPIC2, each CES instance (cesop-z) has one unique key which is separately configu-
rable. As a minimum requirement, the user has to enter a key consisting of at least 6 char-
acters which have at least 1 capital letter, 1 symbol and 1 number. Please check section
8.7.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration – General (on page 100) to see
how to configure the authentication keys.
Please note:
In order to achieve the highest possible level of security, the user is recom-
mended to enter all 32 characters in the key field.
Please note:
After first startup of OPIC2, the default authentication key will be active.
OPIC2 informs the user via DAKA alarm. It is highly recommended to set a
user-defined key after the first startup.
Please note:
OPIC2’s authentication mechanism is always active and cannot be disabled by
the user due to security reasons.
Please note:
Unless wrong configuration, any attacks on message integrity is detected by
OPIC2 immediately and reported to the user via the EAF alarm. In case of EAF,
please consult your network administrator.
Please note:
All EAF alarms observed during the OPIC2 lifetime are stored in the OPIC2
event recorder to give the user more insight about when and how many times
this alarm was raised.
5.4.1.2 Protection
Data reliability and availability are two of the main concerns of teleprotection applica-
tions. OPIC2 provides the following protection schemes to increase the reliability and
availability of the end-to-end user communication.
• Hitless WAN redundancy
• Core unit redundancy
5.4.1.2.1 Hitless WAN Redundancy

OPIC2 offers WAN redundancy via two VLAN interfaces per CES instance (cesop-z). VLAN
interfaces are mapped to two different and non-crossing MPLS-TP pseudo-wires in the
core unit for redundant communication in WAN. This scheme protects the end-to-end
user communication even during a link failure in one of the MPLS-TP pseudo-wires.
2018-12-13 36
OPIC2’s WAN redundancy is configurable by the user and can be disabled unless needed.
In OPIC2, 8 VLAN interfaces exist corresponding to 4 CES instances (cesop-1 … 4). Each
VLAN interface is independently configurable as shown in section 8.10.3.1 AP: /unit-x/
vlanInterfaces/vif-z_v, Configuration – General (on page 114).
OPIC2
FOX61x
Circuit Emulation Service
vif-1_1
cesop-4 VLAN to MPLS mapping
GbE s tar
vif-1_2
VLAN PW
vif-2_1
Scheduler
cesop-3 vif-2_2
vif-1_1 wor king 1
vif-1_2 wor king 2
vif-3_1 vif-2_1 wor king 1
cesop-2 vif-3_2 vif-2_2 wor king 2
vif-3_1 wor king 1
vif-4_2 wor king 2
MPLS-TP Network
WAN protection
(Path 1 pseudo wires)
OPIC2
FOX61x
MPLS-TP Network
(Path 2 ps eudo wires)
Circuit Emulation Service
vif-1_1
cesop-4 VLAN to MPLS mapping
GbE s tar
vif-1_2
VLAN PW
vif-2_1
Scheduler
cesop-3 vif-2_2
vif-1_1 wor king 1
vif-1_2 wor king 2
vif-3_1 wor king 1
vif-4_2 wor king 2
WAN protection
Figure 24: WAN redundancy
Please note:
In order to establish an end-to-end OPIC2 communication, at least one VLAN
interface must be enabled on both OPIC2 units.
Please note:
VLAN-MPLS mapping is done in the core unit based on the VLAN ID configured
in OPIC2. In order to make use of redundancy, vif-z_1 and vif-z_2 VLAN inter-
faces of all CES instances (cesop-z) must be configured with different VLAN
IDs.

Do not enable MPLS-TP LSP protection on the core unit. This may cause oper-
ational problems due to the reason that OPIC2 has a built-in hitless protection
mechanism.
Each VLAN interface (vif-z_v) in OPIC2 transports the traffic of the related CES instance
(cesop-z) to the core unit which then encapsulates the VLAN tagged OPIC2 frames in
MPLS frames and sends them to the remote station through the dedicated MPLS-TP
pseudo-wire. At the remote station, received messages by the core unit are decapsulated
2018-12-13 37
to VLAN frames which are forwarded to the matching VLAN interface of the destination
OPIC2.
Using redundant VLANs two messages with the same content, but different VLAN IDs are
received. Messages are identified with their sequence number. The first message received
with a new sequence number is forwarded. A message received with a sequence number
that has been received before is deleted.
For proper QoS configuration refer to [1KHW028636] Application Note “Design Guide for
MPLS-TP based Utility Networks”.
Please note:
In order to establish a running communication between two CES instances,
VLAN interfaces of both OPIC2 instances must be configured with the same
“VLAN ID”. OPIC2 units will inform the user with the VLAN Mismatch (VMM)
alarm whenever they receive a frame with a VLAN ID which is not existing in
their configuration. Note that the default VLAN priority for OPIC2 is 6.
5.4.1.2.2 Core Unit Redundancy

Being one of the unique features of the ABB’s FOX61x platform, redundant core units are
available in order to protect their running services during a core unit failure.
OPIC2 provides built-in core unit redundancy (switching) logic which cannot be disabled
by the user. The “Unit synchronization and supervision” block of OPIC2 continuously
checks the provided liveness signals from both core units and informs the core unit
redundancy logic to switch its traffic from the previously active core unit to the new
active core unit. See Figure 25 for a visual representation of the core unit redundancy
scheme with OPIC2. All CES traffic is sent to the active core unit.
FOX61x
Core Unit East 1
1 (Active)
2
OPIC2 2
MPLS-TP Network
Core Unit West 2
(Standby)
GbE s tar
FOX61x
Core Unit East 1
(Standby)
OPIC2 1
MPLS-TP Network
1
2 Core Unit West 2
(Active)
GbE s tar
Figure 25: OPIC2 and core unit redundancy
Please note:
OPIC2 services can be protected with this redundancy scheme only if a second
core unit is placed in the FOX61x subrack.
5.4.1.3 Performance Monitoring

OPIC2’s performance monitoring is based on supervision of the WAN performance mea-
sured through the statistics of packet delays and lost packets. There are mainly three
types of OPIC2 outputs which can be found in FOXCST view: Performance counters,
graphs and alarms.
2018-12-13 38
Performance counters are the basis of all performance monitoring in OPIC2. There are 8
counters for each VLAN interface, which are available to the user.
• Number of transmitted packets
• Number of received packets
• Number of delayed packets
• Number of lost packets
• Minimum delay
• Maximum delay
• Average delay
• Delay variation
Check section 8.7.5.3 AP: /unit-x/circuitEmulation/cesop-z, Status - CESoP (on page 107)
and section 8.7.5.4 AP: /unit-x/circuitEmulation/cesop-z, Status - Statistics (on page 108)
to see how to access performance counters on FOXCST view of OPIC2.
Performance graphs use performance counters to create a visual representation to the
user. Following graphs are available for each VLAN interface to the user:
• Packet Delay Variation
• Packet Loss Variation
• Packet Delay Histogram
• Packet Loss Histogram
Please note:
Performance graphs of OPIC2 can show the performance of each VLAN inter-
face within several different time durations. Available options are last 15 min-
utes, last 24 hours and last 7 days. Check section 8.10.6 AP: /unit-x/
vlanInterfaces/vif-z_v, Status (on page 115) to see a detailed description of
the graphs with the specified time ranges.
In addition to the performance counters and graphs, OPIC2 also informs the user with the
following alarms which are created by comparing the set/clear threshold values with the
performance counters:
• Excessive Packet Loss (EPL):
− Set locally if in the last second at least three expected OPIC2 packets are lost at all
active VLAN interfaces of the related CES instance or when they are not received
within the 20 ms time window by all the active VLAN interfaces of the related CES
instance after they have been sent by the remote OPIC2 unit in the last second.
− Cleared when no expected OPIC2 packets are lost in the last second.
• Protection path Excessive Packet Loss (PEPL):
− Can be set only when both VLAN interfaces belonging to one CES instance are
enabled.
− Set locally if in the last second at least three expected OPIC2 packets are lost at only
one of the active VLAN interfaces or when they are not received within the 20 ms
time window by only one of the active VLAN interfaces after they have been sent by
the remote OPIC2 unit in the last second.
− Cleared when no expected OPIC2 packets are lost at any VLAN interface in the last
second
Please note:
EPL and PEPL alarms show that OPIC2 packets are lost within the WAN due to
several reasons (e.g. buffer overflow, link failure, etc.). It is highly recom-
mended to inform the network administrator when these alarms appear. Also
note that during EPL, due to safety reasons, AIS (ALL 1) is sent to the OPIC2
user interfaces. AIS indicates WAN communication problems towards the end
device (e.g. a protection device).
2018-12-13 39
Please note:
All EPL alarms observed during OPIC2 lifetime are stored in the OPIC2 event
recorder to give the user more insight about when and how many times this
alarm was raised.
• Excessive Packet Delay (EPD)
− Set locally if in the last second at least three expected OPIC2 packets are received
after the configured “E2E transmission delay” but within the 20 ms time window by
all the active VLAN interfaces of the related CES instance after they have been sent
by the remote OPIC2 unit.
− Cleared when all expected OPIC2 packets are received within the configured “E2E
transmission delay” in the last second.
• Protection path Excessive Packet Delay (PEPD)
− Can be set only when both VLAN interfaces belonging to one CES instance are
enabled.
− Set locally if in the last second at least three expected OPIC2 packets are received
after the configured “E2E transmission delay” but within the 20 ms time window at
only one of the active VLAN interfaces after they have been sent by the remote
OPIC2 unit.
− Cleared when all expected OPIC2 packets are received within the configured “E2E
transmission delay” at both VLAN interfaces in the last second.
Please note:
EPD and PEPD alarms show that OPIC2 packets experience bigger delay in the
WAN than expected due to several reasons (e.g. increasing buffering delays
with increasing network resource utilization). It is highly recommended to
inform the network administrator when these alarms appear. Also note that
during EPD, due to safety reasons, AIS (ALL 1) is sent to the OPIC2 user inter-
faces instead of the expected packets. AIS indicates WAN communication
problems towards the end device (e.g. a protection device).
Please note:
All EPD alarms observed during OPIC2 lifetime are stored in the OPIC2 event
recorder to give the user more insight about when and how many times this
alarm was raised.
• Delay Threshold Exceeded (DTE):
− Can only be set if the end-to-end transmission delay supervision is enabled.
− Set locally if the received OPIC2 packets are delayed for more than the configured
end-to-end transmission delay threshold value, but smaller than the configured end-
to-end transmission delay.
− Cleared when the OPIC2 packet delay drop below the configured end-to-end trans-
mission delay threshold.
− See detailed behavior in combination with other delay and traffic effected alarms in
Figure 26.
Please note:
The end-to-end transmission Delay Threshold Exceeded (DTE) alarm shows
that OPIC2 packets experience bigger delay in the WAN than the configured
DTE threshold value due to several reasons (e.g. increasing buffering delays
with increasing network resource utilization). It is highly recommended to
inform the network administrator when this alarm appears.
Also, note that with an active DTE alarm the traffic is not interrupted.
The end-to-end Transmission Delay Threshold is per default disabled.
2018-12-13 40
Check section 8.7.4 AP: /unit-x/circuitEmulation/cesop-z, Fault Management (on

page 104) to see where the EPL, PEPL, EPD and PEPD alarms are located in FOXCST view
of OPIC2.
Check section 8.10.4 AP: /unit-x/vlanInterfaces/vif-z_v, Fault Management (on page 114)
to see where the DTE alarm is located in FOXCST view of OPIC2.
Figure 26 depicts the dependencies in performance monitoring alarms and warning levels
of OPIC2.
Transmission
Delay
EPL
(per CES)
OPIC2 jitter buffer depth
20 ms
18 ms
AIS on teleprotection
16 ms
interface EPD
(per CES)
14 ms
12 ms
End-to-end Transmission Delay

10 ms
DTE
8 ms
(per VIF)
End-to-end Transmission Delay Threshold
6 ms
4 ms
Valid teleprotection
data No Alarm
2 ms
EPL Excessive Packet Loss Time

EPD Excessive Packet Delay
DTE Transmission Delay Threshold Exceeded
Figure 26: Performance monitoring alarms and warning levels
Figure 27 shows the packet delay variation. It helps to monitor real packet delay variation
in the network and omit wrong configurations of the OPIC2 “E2E transmission delay” con-
figuration.
2018-12-13 41
Figure 27: Packet delay variation
Figure 28 shows the packet delay histogram. It helps to monitor real packet delays in the
network and omit wrong configurations of the OPIC2 “E2E transmission delay” configura-
tion.
Figure 28: Packet delay histogram
Figure 29 shows the packet loss rate variation. In a properly configured network the
packet loss rate shall be 0% or very close to 0%.
2018-12-13 42
Figure 29: Packet loss rate variation
Figure 30 shows the packet loss rate histogram. In a properly configured network the
packet loss rate shall be 0% or very close to 0%.
Figure 30: Packet loss rate histogram
5.4.1.4 ARP Handling (MAC Address Discovery)

OPIC2 frame transmission/reception by the CES instances is based on unicast Layer 2
Ethernet communication. This brings the requirement to learn the MAC address of the
remote OPIC2 unit before starting CES operation.
Destination MAC address learning is achieved by ARP frames exchange protocol which
carry the MAC addresses of the source and destination nodes to the communicating
OPIC2 CES instances. Every time when a CES instance (cesop-z) admin state is set to “UP”
and related primary VLAN interface is enabled, ARP request messages are broadcast in
the network which eventually reaches the destination with the help of underlying end-to-
end VLAN interface connections. Received ARP requests are responded with ARP reply
messages carrying also the MAC address of the destination OPIC2 unit. Figure 31 shows
how ARP message exchange works between two end stations.
2018-12-13 43
ARP Request
Destination MAC: FF:FF:FF:FF:FF:FF
Computer A Computer B
192.168.1.1 192.168.1.2
MAC: AAA MAC: BBB
ARP Reply
Source MAC: BBB
Destination MAC: AAA
Computer A Computer B
192.168.1.1 192.168.1.2
MAC: AAA MAC: BBB
Figure 31: Mac address discovery through ARP message exchange
Please note:
In order to have a successful ARP exchange and start CES communication,
OPIC2 unit has to be configured with the correct pair of source IP and destina-
tion IP addresses. Check section 8.2.3.1 AP: /unit-x, Configuration – General
(on page 86) and section 8.7.3.1 AP: /unit-x/circuitEmulation/cesop-z, Config-
uration – General (on page 100) to see how to configure Destination and
Source IP addresses of the OPIC2 units in FOXCST respectively.
Please note:
In case ARP exchange fails due to a missing partner station or wrong configu-
ration, Destination MAC Address Not Resolved (DMANR) alarm will be
asserted to inform the user. The alarm will be cleared as soon as the OPIC2
receives the ARP reply with the expected IP addresses.
Please note:
The source MAC address of OPIC2 units is not configurable, it is rather pro-
grammed during manufacturing with an available unique MAC address start-
ing with three hexadecimal bytes of 00:02:a3 which represents ABB products.
Check section 8.2.3.1 AP: /unit-x, Configuration – General (on page 86) to see
how to access the Source MAC address in FOXCST.
5.4.2 Trail Supervision

OPIC2 offers “Trail Supervision” as an additional safety mechanism against faulty user
configurations which might lead to wrong end-to-end CES channel connections, and so to
wrong relay connections.
OPIC2’s trail supervision is configurable by the user and can be enabled at any time as
shown in section 8.7.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration – General (on
page 100). When enabled, up to 15 characters of “Transmitted Trail Trace Identifier (TTI)”
which are configurable by the user are inserted in OPIC2 frames. The user can also config-
ure up to 15 characters of “Expected TTI” field to accept only the OPIC2 frames carrying
the expected TTI value.
2018-12-13 44
Please note:
In OPIC2 configuration, “Transmitted TTI” and “Expected TTI” of the same CES
instance do not have to be the same. Important is to have matching “Trans-
mitted TTI” and “Expected TTI” values between two communicating distinct
CES instances. When an OPIC2 frame is received with a TTI other than
“Expected TTI” or when an OPIC2 frame is received with no TTI when the TTI
supervision is enabled, then the user will be informed with the Trail Identifier
Mismatch (TIM) alarm.
5.4.3 Unit Synchronization

OPIC2 requires properly synchronized network elements in order to fulfill differential pro-
tection requirements. For this purpose ABB has developed a so called PTP pure hybrid
mode for the core unit. In this mode the frequency is distributed by SyncE and the phase
information (time of day) is distributed by PTP in boundary clock mode. For more infor-
mation about network design requirements and proper configuration of the network ele-
ment, please refer to [1KHW028636] Application Note “Design Guide for MPLS-TP based
Utility Networks”.
Each network element in the network has to be synchronized in pure hybrid mode and get
into so called phase-lock state before OPIC2 can start circuit emulation operation and
IRIG-B output signal generation. OPIC2 keeps the OOS alarm active until the phase-lock
state is reached.
Circuit emulation will not start the operation until the remote station also gets into the
phase-lock state. The corresponding CESoP instance keeps the EPL alarm active until this
condition is cleared.
If proper synchronization of the network is not guaranteed, OPIC2 will stop the circuit
emulation operation and IRIG-B output signal generation and activate the OOS alarm.
Major conditions to stop CESoP operation and IRIG-B output signal generation are:
• Core unit enters free run mode
• Core unit enters holdover mode and remains in holdover for longer than 60 seconds
• Core unit protection switch-over (core unit redundancy)
• Core unit reboot
• Core unit remove
• Core unit software activation
• Core unit system release update
5.4.4 IRIG-B Generation

OPIC2 generates IRIG-B002/006 outputs for the user as long as the unit itself is synchro-
nized to a PTP grandmaster clock placed in the WAN with a high accuracy clock (sub-µs).
The IRIG-B generation works closely with the “Unit synchronization and supervision” block
which sends the synchronized BCDTOY, BCDYEAR and supervision information to the IRIG-B
generation block. When the synchronization is degraded, the IRIG-B generation block is
informed and IRIG-B outputs are set to ‘0’ immediately. See Figure 32 for a visual repre-
sentation of the relationship between the two internal functional blocks to generate
IRIG-B.
2018-12-13 45
FOX61x
OPIC2
IRIG-B generation
Devices with electrical IRIG-B 002/006
port-6
IRIG-B input 6x electrical IRIG-B IRIG-B encoder
output
Device with optical IRIG-B 002/006 interface 0 BCDDay
port-5
IRIG-B input 1x optical (ST) Output select
BCDYear
Unit synchronization and

supervision
Figure 32: IRIG-B frame generation
Please note:
When synchronization is degraded or lost, the “Unit Synchronization and
Supervision” block activates the OOS alarm to inform the user. As long as the
OOS alarm is active, IRIG-B output generation is stopped and IRIG-B output
lines are driven to ‘0’ which will be indicated by OSSO alarm.
2018-12-13 46
FOX61x | OPIC2 COMMISSIONING
6 Commissioning
This section describes the management of the basic system functions of the OPIC2 unit:
• Commissioning example of the OPIC2 unit in typical teleprotection equipment links.
Please refer to [1KHW002466] User Manual “FOXCST” for details on the general GUI
aspects, and refer to [1KHW002464] User Manual “FOX615/FOX612” for specific character-
istics of the FOX61x.
6.1 Commissioning of Teleprotection Equipment Links

Typical examples for commissioning of TPE-links through an existing FOX61x network
with OPIC2 interfaces are introduced as possible reference.
6.1.1 Prerequisites
Before starting the commissioning of any application on the OPIC2 unit, the following pre-
requisites need to be fulfilled:
6.1.1.1 Core Unit

In a FOX61x a core unit needs to be in operation in slot 11 of the FOX61x subrack. A second
core unit in slot-13 is optional and would offer core unit hardware protection.
6.1.1.2 OPIC2 Unit

In a FOX615, the OPIC2 unit is inserted into a subrack slot as listed in section 4.2 Slots for
the OPIC2 Unit (on page 14).
A valid ESW is installed on the OPIC2 unit. For the management of ESW, refer to
[1KHW002466] User Manual “FOXCST”. For details about compatible ESW versions, refer
to [1KHW028777] Release Note “FOX61x”.
6.1.1.3 FOXCST
FOXCST needs to be installed on a PC, and a management connection from the FOXCST
to the FOX61x needs to be up and running. For details about the installation and opera-
tion of the FOXCST, please refer to [1KHW002466] User Manual “FOXCST”.
6.1.1.4 PETS
The PETS on the FOX61x network element must be configured to an appropriate synchro-
nization clock source.
Ensure that both connected FOX61x network elements are properly configured in term of
network synchronization and are phase locked to the same time source.
For the PETS configuration refer to [1KHW028636] Application Note “Design Guide for
MPLS-TP based Utility Networks”.
6.2 IEEE C37.94 Application with RED670

To set up a communication link between two of ABBs Line Differential Protection Relays
RED670 preconfigured with an IEEE C37.94 Line Data Communication Module (LDCM) over
a FOX61x network with two OPIC2 units, the following additional items are required:
• 2 SFP modules
1KHW001871R0005 (850nm, multi mode, up to 2 km)
• 2 fiber optic cables
V9YE/1KHW001862R00YY of appropriate length
2018-12-13 47
On each OPIC2, an SFP has to be placed into the cage of the designated interface and one
of the optical cables connected between the SFP and the LDCM.
FOX61x (subrack 1)
OPIC2 (slot-8) Core Unit

vif-1_2 (slot-11)
Sour ce IP: 192.168.100.1 VLA N ID = 11;
inbound and outbound
Protection port-1 cesop-1 label = 3000
Relay IEEE C37 .94 Dest. IP: 192.168.100.2
vif-1_1
VLA N ID = 10;
label = 2000
GbE star
port-1 port-2
forward out and forward out and
reverse in label = 100 reverse in label = 200
FOX61x (subrack-2)
OPIC2 (slot-8) port-1 port-2
GbE star
Sour ce IP: 192.168.100.2 forward out and forward out and
vif-1_1
VLA N ID = 10;
label = 2000
Protection port-1 cesop-1
Relay IEEE C37 .94 Dest. IP: 192.168.100.1 vif-1_2
VLA N ID = 11;
inbound and outbound Core Unit
label = 3000
(slot-11)
Core unit configuration

The external core unit ports have to be configured as MPLS-TP port type and the internal
iport which correspond to the OPIC2 unit (slot-8) as PWAC port type.
⇒ Configure the core unit ports (on both FOX61x subracks). Proceed as follows:
1. Navigate to port configuration dialog in Tree View:
- AP: /unit-11/port-1, Main - Port Type.
- Usage = MPLS-TP.
- Usage = MPLS-TP.
• AP: /unit-11/iports/iport-8, Main - Port Type.
- Usage = PWAC.
Result: The core unit port types are configured.
End of instruction
OPIC2 configuration:
The OPIC2 has to be configured to support IEEE C37.94 towards the RED670 with
1x64 kbit/s protection channel and use the hitless WAN redundancy feature.
⇒ Configuration of OPIC2 in FOX61x subrack 1. Proceed as follows:

1. Navigate to OPIC2 configuration dialog in Tree View:
- AP: /unit-8, Configuration - General.
- Set the Source IP Address = 192.168.100.1.
2018-12-13 48
2. Navigate to front port configuration dialog in Tree View:

- AP: /unit-8/port-1, Configuration - Interface.
- Select the Type = IEEE C37.94.
- Set the Number Of Protection Channels = 1.
- AP: /unit-8/port-1, Main - Admin And Oper Status.
- Set the Administrative State = Up.
3. Navigate to circuit emulation configuration dialog in Tree View:
- AP: /unit-8/circuitEmulation/cesop-1, Configuration - General.
- Select the Termination Mode = Terminated Optical Port.
- Set the Destination IP Address = 192.168.100.2.
- Set the Vlan Authentication Key =Abb$1234.
4. Navigate to vlanInterfaces configuration dialog in Tree View:
- AP: /unit-8/vlanInterfaces/vif-1_1, Configuration - Transport.
- Set the VLAN ID =10.
- Set the VLAN Priority =7.
- AP: /unit-8/vlanInterfaces/vif-1_1, Main - Admin And Oper Status.
- AP: /unit-8/circuitEmulation/cesop-1, Main - Admin And Oper Status.
Result: The OPIC2 unit in subrack 1 is configured.

2018-12-13 49

End of instruction
MPLS-TP configuration
OPIC2 is designed to work over MPLS-TP. Therefore, the configuration of all known net-
work elements, MPLS-TP tunnels and VPWS towards OPIC2 are needed.
Follow the basic MPLS-TP configuration in section 6.10 Basic MPLS-TP Configuration for a
Redundant OPIC2 Link (on page 72) to interconnect the two OPIC2 over the WAN with the
help of MPLS-TP.
End of instruction
RED670 Configuration
Relevant HMI configuration for the designated line data communication module LDCM on
both RED670:
“Menu → Settings → General Settings → Communication → LDCM Configuration → LDC-
Mxxx → CRMx”
• TerminalNo: 1
any number, must be the same as in RemoteTermNo of opposite RED670
• RemoteTermNo: 2
any number, must be the same as in TerminalNo of opposite RED670
• DiffSynch: ECHO
• CommSync: Slave (on both RED670!)
End of instruction
Commissioning
A successful commissioning of the communication link can be verified on any of the
RED670 by checking the round trip delay of the link and monitoring the communication
status. Proceed as follows:
• Reset Error Counters
“Menu → Reset → Reset Counters → LDCMCommunication → LDCMxxx → CRMx → Reset
LCDMCounters? → Yes”
• Check Status
“Menu → Test → Function status → Communication → Remote communication → LDC-
Mxxx → CRMx”
− TransmDelay: [μs] (round trip transmission delay)
− NoOfShInter: 0 (# of short interruptions: 20 – 50 ms)
− NoOfMedInter: 0 (# of med. interruptions: 50 – 150 ms)
− NoOfLongInter: 0 (# of long interruptions: > 150 ms)
− CommStatus: Ok (communication status ok)
− COMFAIL: 0 (no communication failure)
− CRCERROR: 0 (no CRC-Error in incoming message)
End of instruction
2018-12-13 50
6.3 IEEE C37.94 Application with NSD570

To set up a communication link between two of ABBs NSD570 Teleprotection Equipment
preconfigured with an optical interface G1LOa with C37.94 over a FOX61x network with
two OPIC2 units, the following additional items are required:
• 4 SFP modules
1KHW001871R0005 (850 nm, multi mode, up to 2 km), or
• 4 SFP modules
1KHW001872R0001 (1310 nm, single mode, up to 30 km)
• 2 fiber-optic cables
V9YG/ 1KHW001874R00YY (for connection in the same cabinet), or
V9YF/ 1KHW001873R00YY (for connection outside the cabinet)
of appropriate length.
On each OPIC2 and G1LOa, an SFP has to be placed into the cage of the designated inter-
face and one of the optical cables connected between the SFPs.
FOX61x (subrack 1)
OPIC2 (slot-8) Core Unit

vif-1_2 (slot-11)
NSD570 Sour ce IP: 192.168.100.1 VLA N ID = 11;
port-1 cesop-1 label = 3000
G1LOa IEEE C37 .94 Dest. IP: 192.168.100.2
IEEE C37 .94 vif-1_1
VLA N ID = 10;
label = 2000
GbE star
port-1 port-2
FOX61x (subrack-2)
OPIC2 (slot-8) port-1 port-2

GbE star

vif-1_1
VLA N ID = 10;
NSD570 inbound and outbound
label = 2000
port-1 cesop-1
G1LOa IEEE C37 .94 Dest. IP: 192.168.100.1 vif-1_2
IEEE C37 .94 VLA N ID = 11;
label = 3000
(slot-11)

- Usage = MPLS-TP.
- Usage = MPLS-TP.
2018-12-13 51

- Usage = PWAC.
End of instruction
The OPIC2 has to be configured to support IEEE C37.94 towards the NSD570 G1Loa inter-
face with 1x64 kbit/s protection channel and use the hitless WAN redundancy feature.


2018-12-13 52

End of instruction
help of MPLS-TP.
End of instruction
NSD570 Configuration
Relevant HMI570 configuration for both NSD570:
• “Configuration → Edit Configuration”.
• Digital Interface:
− Interface Type: Optical IEEE C37.94
− Automatic Laser Shutdown (ALS): off
End of instruction
Commissioning
A successful commissioning of the communication link can be verified on any NSD570 by
checking the alarms as follows:
• “Status / Alarm → Upload Alarm”.
− No pending alarms
− Only two LED shine at front of NSD570: Ok and Guard
Further, the transmission time can be verified on any NSD570 as follows:
• “Maintenance → Manual Loop Test”.
2018-12-13 53
− Transmission time [ms] x.y (round trip transmission delay)

End of instruction
6.4 ABB TPE Application with REL551 and REL316*4

To set up a communication link between two of ABBs Line Differential Protection Relays
• REL551 preconfigured with an ABB Communication Module (DCM-FOM), or
• REL316*4
over a FOX61x network with two OPIC2 units, the following additional items are required:
• 2 SFP modules
1KHW001872R0001 (1310 nm, single mode, up to 30 km)
• 2 optical attenuators
1KHW001997R0010 (10 dB FC/PC, 1310 nm, single mode
V9KW/ 1KHW001323R00YY (for connection in the same cabinet), or
V9KZ/ 1KHW001326R00YY (for connection outside the cabinet)
On each OPIC2 an SFP has to be placed into the cage of the designated interface, an opti-
cal attenuator inserted into the optical transmitter (Tx is above Rx, when SFP is plugged
into the cage) and one of the optical cables connected between the SFP and the DCM-
FOM.
FOX61x (subrack 1)
optical attenuator
Core Unit
OPIC2 (slot-8) vif-1_2 (slot-11)
Sour ce IP: 192.168.100.1 VLA N ID = 11;
Protection inbound and outbound
TX
Relay port-1 cesop-1 label = 3000
REL551 RX
ABB TPE Dest. IP: 192.168.100.2
REL316*4 vif-1_1
VLA N ID = 10;
label = 2000
GbE star
port-1 port-2
FOX61x (subrack-2)
port-1 port-2
GbE star
OPIC2 (slot-8)
optical attenuator vif-1_1
VLA N ID = 10;
Protection label = 2000
TX
Relay port-1 cesop-1
REL551 RX
ABB TPE Dest. IP: 192.168.100.1 vif-1_2
REL316*4 VLA N ID = 11;
label = 3000
(slot-11)

2018-12-13 54
- Usage = MPLS-TP.
- Usage = MPLS-TP.
- Usage = PWAC.
End of instruction
The OPIC2 has to be configured to support ABB TPE towards the REL551 or REL316*4 with
1x64 kbit/s protection channel and use the hitless WAN redundancy feature.

- Select the Type = ABB TPE.
- AP: /unit-8/port-1, Configuration - Interoperability.
- All One Tx Suppression Enabled = true
- AP: /unit-8/port-1, Fault Management - Configuration.
- Disable the monitoring of the TLOFA alarm, Monitored = false
2018-12-13 55

- AP: /unit-8/port-1, Configuration - Interoperability.
- All One Tx Suppression Enabled = true
End of instruction
help of MPLS-TP.
End of instruction
REL551 Configuration
Relevant HMI configuration for the designated fiber optical communication modules
DCM-FOM on both REL551:
• “Enter menu → Configuration → DiffFunctions”
− DiffSynch: Master/Slave (one terminal set to “Master”, the other to “Slave”)
• “Enter menu → Configuration → TerminalCom → RemTermCom”
− TerminalNo: 1 (any number, must be the same as in RemoteTermNo of opposite
REL551)
2018-12-13 56
− RemoteTermNo: 2 (any number, must be the same as in TerminalNo of opposite

REL551)
− OptoPower: Low
− CommSync: Master (on both REL551)
End of instruction
Please note:
The CommSync parameter definition in REL551 is inversed:
→ By setting the parameter to “Master”, the equipment is in reality config-
ured to “Slave”.
Please note:
The REL316*4 relay requires no configuration.
Commissioning
REL551 by checking the round trip delay of the link and monitoring the communication
status as follows:
• Reset Error Counters
“Menu → Reset → Reset Counters → LDCMCommunication → LDCMxxx → CRMx → Reset
LCDMCounterDiscomfit → Yes”
• Check Status
“Enter menu → ServiceReport → Functions → Differential → DiffCom→ DiffCom”
− TransmDelay: [μs] (round trip transmission delay, available only on the terminal con-
figured as DiffCom “Slave”)
− NoOfShInter: 0 (# of short interruptions: 20 – 50 ms)
− NoOfMedInter: 0 (# of med. interruptions: 50 – 150 ms)
− NoOfLongInter: 0 (# of long interruptions: > 150 ms)
− CommStatus: Ok (communication status ok)
End of instruction
6.5 ABB TPE Application with NSD570

To set up a communication link between two of ABBs NSD570 Teleprotection Equipment
preconfigured with an optical interface G1LOa with ABB TPE over a FOX61x network with
two OPIC2 units, the following additional items are required:
• 4 SFP modules 1KHW001871R0005
(850 nm, multi mode, up to 2 km), or
• 4 SFP modules 1KHW001872R0001
(1310 nm, single mode, up to 30 km)
V9YG / 1KHW001874R00YY (for connection in the same cabinet), or
V9YF / 1KHW001873R00YY (for connection outside the cabinet)
On each OPIC2 and G1LOa an SFP has to be placed into the cage of the designated inter-
face and one of the optical cables connected between the SFPs.
2018-12-13 57
FOX61x (subrack 1)
Core Unit
NSD570 Sour ce IP: 192.168.100.1 VLA N ID = 11;
port-1 cesop-1 label = 3000
G1LOa ABB TPE Dest. IP: 192.168.100.2
ABB TPE vif-1_1
VLA N ID = 10;
label = 2000
GbE star
port-1 port-2
FOX61x (subrack-2)
port-1 port-2
GbE star
OPIC2 (slot-8)
vif-1_1
VLA N ID = 10;
NSD570 inbound and outbound
label = 2000
port-1 cesop-1
G1LOa ABB TPE Dest. IP: 192.168.100.1 vif-1_2
ABB TPE VLA N ID = 11;
label = 3000
(slot-11)

- Usage = MPLS-TP.
- Usage = MPLS-TP.
- Usage = PWAC.
End of instruction
The OPIC2 has to be configured to support ABB TPE towards the NSD570 G1LOa interface
with 1x64 kbit/s protection channel and use the hitless WAN redundancy feature.

2018-12-13 58


2018-12-13 59

End of instruction
help of MPLS-TP.
End of instruction
NSD570 Configuration
Relevant HMI570 configuration for both NSD570:
• “Configuration → Edit Configuration”.
Digital Interface:
− Interface Type: Optical OTERM/OPTIF
− Automatic Laser Shutdown (ALS): off
End of instruction
Commissioning
NSD570 by checking the alarms as follows:
• “Status / Alarm → Upload Alarm”.
− No pending alarms
− Only two LED shine at front of NSD570: Ok and Guard
Further, the transmission time can be verified on any NSD570 as follows:
• “Maintenance → Manual Loop Test”.
− Transmission time [ms] x.y (round trip transmission delay)
End of instruction
6.6 Differential Protection over E1 Interface

To set up a communication link between two line differential protection relays with E1
interface over a FOX61x network with two OPIC2 units, the following additional items are
required:
• 2x LEDE1 units
• 2x LEDE1 cables according to the needed impedance.
For additional information refer to [1KHW002498] Product Guide “FOX61x Cables”.
On each side, an OPIC2 as well as a LEDE1 unit have to be inserted into the FOX61x sub-
rack. Each LEDE1 has to be connected over the dedicated copper cable with the differen-
tial protection device.
2018-12-13 60
FOX61x (subrack 1)
LEDE1 Core Unit
(slot-9) Sour ce IP: 192.168.100.1 VLA N ID = 11;
Relay E1 Dest. IP: 192.168.100.2
vif-1_1
VLA N ID = 10;
label = 2000 port-1 port-2
GbE star
PBUS
forward out forward out
and reverse in and reverse in
label = 100 label = 200
FOX61x (subrack-2)
LEDE1 port-1 port-2
GbE star
OPIC2 (slot-8)
(slot-9) Sour ce IP: 192.168.100.2 forward out forward out
vif-1_1 label = 100 label = 200
VLA N ID = 10;
label = 2000
Relay E1 Dest. IP: 192.168.100.1 vif-1_2
VLA N ID = 11;
PBUS

label = 3000
(slot-11)

- Usage = MPLS-TP.
- Usage = MPLS-TP.
- Usage = PWAC.
End of instruction
The OPIC2 has to be configured to support receiving/transmitting of P12 signals towards
the PBUS on the backplane, to access the E1 interface on the LEDE1 unit. Furthermore we
use the hitless WAN redundancy feature.

2018-12-13 61

- Select the Termination Mode = Transparent Internal Port.

- Select the Termination Mode = Transparent Internal Port.
End of instruction
LEDE1 unit configuration

The LEDE1 has to be configured to support E1 towards the differential protection device.
2018-12-13 62
⇒ Configuration of LEDE1 in FOX61x subrack 1 and subrack2. Proceed as follows:

1. Navigate to LEDE1 configuration dialog port-1 in Tree View:
- AP: /unit-9/port-1, Configuration - General.
- Set the Termination Mode = Transparent.
2. Navigate to the Cross Connections view in FOXCST:
- Select “Create a new Cross Connection”.
- Set the Layer Rate = P12.
- Select the A-End Working Unit = unit-9 (LEDE1).
- Select the /unit-9/port-1/P12-channel.
- Select the Z-End Working Unit = unit-8 (OPIC2).
- Select the /unit-8/circuitEmulation/cesop-1/P12-channel.
- Click “Create”
3. Navigate to LEDE1 configuration dialog port-1 in Tree View:
→ The LEDE1 units in subrack 1 and subrack 2 are configured. The cross connections
between the LEDE1 and the OPIC2 are created.
End of instruction
help of MPLS-TP.
End of instruction
6.7 Differential Protection over E0 Interface

To set up a communication link between two line differential protection relays with E0
(64 kbit/s) codirectional interface over a FOX61x network with two OPIC2 units, the fol-
lowing additional items are required:
• 2x LECO1 units
• 2x LECO1 cables according to the needed impedance.
On each side, an OPIC2 as well as a LECO1 unit have to be inserted into the FOX61x sub-
rack. Each LECO1 has to be connected over the dedicated copper cable with the differen-
2018-12-13 63
FOX61x (subrack 1)
LECO1 Core Unit
Relay E0 codir Dest. IP: 192.168.100.2
vif-1_1
VLA N ID = 10;
GbE star
PBUS
FOX61x (subrack-2)
LECO1 port-1 port-2
GbE star
OPIC2 (slot-8)
VLA N ID = 10;
label = 2000
Relay E0 codir Dest. IP: 192.168.100.1 vif-1_2
VLA N ID = 11;
PBUS

label = 3000
(slot-11)

- Usage = MPLS-TP.
- Usage = MPLS-TP.
- Usage = PWAC.
End of instruction
the PBUS on the backplane, to access the E0 interface on the LECO1 unit. Furthermore we
use the hitless WAN redundancy feature.

2018-12-13 64

- Select the Termination Mode = Terminated Internal Port.
- AP: /unit-8/circuitEmulation/cesop-1, Configuration - Channels.
- → Click “Create Channel …”.
- → Set the Index = 1.
- → Set n (number of 64 kbit/s timeslots for this channel) = 1.
- → Set the Start Timeslot =0.

2018-12-13 65

End of instruction
LECO1 unit configuration

The LECO1 has to be configured to support E0 towards the differential protection device.
⇒ Configuration of LECO1 in FOX61x subrack 1 and subrack2. Proceed as follows:

- Set the Layer Rate = P0_nc.
- Select the A-End Working Unit = unit-9 (LECO1).
- Select the /unit-9/port-1: E0.
- Select the /unit-8/circuitEmulation/cesop-1/chan-1: P0_nc (n=1) (TS 0).
2. Navigate to LECO1 configuration dialog port-1 in Tree View:
→ The LECO1 units in subrack 1 and subrack 2 are configured. The cross connections
between the LECO1 and the OPIC2 are created.
End of instruction
help of MPLS-TP.
End of instruction
6.8 Differential Protection over X.24-V.11 Interface

1984kbit/s
To set up a communication link between two line differential protection relays with X.24-
V.11 interface (1984 kbit/s) over a FOX61x network with two OPIC2 units, the following
additional items are required:
• 2x LEDS1 units
• 2x LEDS1 cables.
On each side, an OPIC2 as well as a LEDS1 unit have to be inserted into the FOX61x sub-
rack. Each LEDS1 has to be connected over the dedicated copper cable with the differen-
2018-12-13 66
FOX61x (subrack 1)
LEDS1 Core Unit
X.24-V.11
Relay 1984 kbit/s
Dest. IP: 192.168.100.2
vif-1_1
VLA N ID = 10;
GbE star
PBUS
FOX61x (subrack-2)
LEDS1 port-1 port-2
GbE star
OPIC2 (slot-8)
VLA N ID = 10;
label = 2000
X.24-V.11
Relay 1984 kbit/s
Dest. IP: 192.168.100.1 vif-1_2
VLA N ID = 11;
PBUS

label = 3000
(slot-11)

- Usage = MPLS-TP.
- Usage = MPLS-TP.
- Usage = PWAC.
End of instruction
The OPIC2 has to be configured to support 1984 kbit/s receiving/transmitting towards
the PBUS on the backplane, to access the 1984 kbit/s X24-V.11 interface on the LEDS1 unit.
Furthermore we use the hitless WAN redundancy feature.

2018-12-13 67


2018-12-13 68

End of instruction
LEDS1 unit configuration

The LEDS1 has to be configured to support X.24-V.11 with 1984kbit/s bandwidth towards
the differential protection device.
⇒ Configuration of LEDS1 in FOX61x subrack 1 and subrack2. Proceed as follows:

1. Navigate to LEDS1 configuration dialog port-1 in Tree View:
- Set the Interface Type = X.24-V.11.
- Select the Rate = 1984 kbit/s.
- Select the A-End Working Unit = unit-9 (LEDS1).
- Select the /unit-9/port-1: X.24/V.11 (1984 kbit/s).
- Select the /unit-8/circuitEmulation/cesop-1/chan-1: P0_nc (n=31) (TS 0..30).
3. Navigate to LEDS1 configuration dialog port-1 in Tree View:
→ The LEDS1 units in subrack 1 and subrack 2 are configured. The cross connections
between the LEDS1 and the OPIC2 are created.
End of instruction
help of MPLS-TP.
End of instruction
6.9 Differential Protection over 2/4-wire Analog Interface

To set up a communication link between two line differential protection relays with a 2/4-
wire analog interface over a FOX61x network with two OPIC2 units, the following addi-
tional items are required:
• 2x LEDA1 units
• 2x LEDA1 cables.
On each side an OPIC2 as well as a LEDA1 unit have to be inserted into the FOX61x sub-
rack. Each LEDA1 has to be connected over the dedicated copper cable with the differen-
2018-12-13 69
FOX61x (subrack 1)
LEDA1 Core Unit
2/4 wire
Relay 64 kbit/s
Dest. IP: 192.168.100.2
vif-1_1
VLA N ID = 10;
GbE star
PBUS
FOX61x (subrack-2)
LEDA1 port-1 port-2
GbE star
OPIC2 (slot-8)
VLA N ID = 10;
label = 2000
2/4 wire
Relay 64 kbit/s
Dest. IP: 192.168.100.1 vif-1_2
VLA N ID = 11;
PBUS

label = 3000
(slot-11)

- Usage = MPLS-TP.
- Usage = MPLS-TP.
- Usage = PWAC.
End of instruction
the PBUS on the backplane, to access the 2/4-wire analog interface on the LEDA1 unit.
Furthermore we use the hitless WAN redundancy feature.

2018-12-13 70


2018-12-13 71

End of instruction
LEDA1 unit configuration

The LEDA1 has to be configured to support the 2/4-wire analog interface towards the dif-
ferential protection device.
⇒ Configuration of LEDA1 in FOX61x subrack 1 and subrack2. Proceed as follows:

1. Navigate to LEDA1 configuration dialog in Tree View:
- Set the Voice Interface Type = 4-Wire (or 2-Wire if required).
- Select the A-End Working Unit = unit-9 (LEDA1).
- Select the /unit-9/port-1: E&M (4-Wire).
- Select the /unit-8/circuitEmulation/cesop-1/chan-1: P0_nc (n=1) (TS 0).
3. Navigate to LEDA1 configuration dialog port-1 in Tree View:
→ The LEDA1 units in subrack 1 and subrack 2 are configured. The cross connections
between the LEDA1 and the OPIC2 are created.
End of instruction
help of MPLS-TP.
End of instruction
6.10 Basic MPLS-TP Configuration for a Redundant OPIC2

Link
Please note:
The SFP plugged in port-1 and port-2 of the core unit have to be configured
according to the used type:
→ On port-1 and port-2 only 10GbE SFPs are supported.
→ On port-3 and port-4 of CESM2 only 1GbE SFPs are supported.
2018-12-13 72
MPLS-TP Configuration for FOX61x subrack 1

The following description creates a redundant VPWS over two separate fibers. All settings
are done manually on the individual network elements. There is no NMS needed to setup
the configuration.
⇒ MPLS configuration. Proceed as follows:

1. Navigate to the global MPLS-TP configuration dialog: MPLS-TP view in FOXCST.
- MPLS-TP, Network Elements.
- Set the Global ID “1234”.
- Set the Node ID “1”.
2. Add the known network elements in MPLS-TP:
- MPLS-TP, Network Elements – Add a Network Element.
- Add node with following settings:
3. Add two MPLS tunnels:

- MPLS-TP/Tunnels, Tunnels – Create a new tunnel
- Add tunnel 1 on the core unit port-1 with following settings:
2018-12-13 73
2018-12-13 74
4. Add two VPWS for the backplane communication with OPIC2:

- MPLS-TP/VPWS, VPWS – Create a new Ethernet Private Wire Service.
- Add VPWS 1 on the core unit iport-8 for VLAN 10 with following settings:
2018-12-13 75
Result: The MPLS-TP configuration is done.

End of instruction
MPLS-TP Configuration for FOX61x subrack 2
⇒ MPLS configuration. Proceed as follows:

1. Navigate to global MPLS-TP configuration dialog in MPLS-TP:
- MPLS-TP, Network Elements.
- Set the Global ID “1234”.
- Set the Node ID “2”.
2. Add the known network elements in MPLS-TP:
- MPLS-TP, Network Elements – Add a Network Element.
2018-12-13 76
3. Add two MPLS tunnels:

- MPLS-TP/Tunnels, Tunnels – Create a new tunnel.
2018-12-13 77
4. Add two VPWS for the backplane communication with OPIC2:

- MPLS-TP/VPWS, VPWS – Create a new Ethernet Private Wire Service
2018-12-13 78
2018-12-13 79
Result: The MPLS-TP configuration is done.

End of instruction
2018-12-13 80
FOX61x | OPIC2 OPERATION AND MAINTENANCE
7 Operation and Maintenance

This section gives an overview of operational and maintenance aspects of the OPIC2 unit.
You will find the following information:
• Description of the optical indicators found on the OPIC2 unit front.
• Diagnostic loop availability and handling.
• Generic maintenance functions of the unit.
Please note:
The operation functions described in this section assume a correctly config-
ured and operational OPIC2 unit
7.1 Unit Optical Indicators

LEDs on the front of the OPIC2 unit are used to indicate to the user the alarm status sum-
mary of the unit and of the network traffic signals.
XXXXx R1A
XXXXXXXXXXXX
UNIT TRAFFIC
Figure 33: Fault indication LEDs on the OPIC2 unit
Table 10: LED signaling on OPIC2

LED name Color State Meaning
UNIT Red Failure Unit is not in service.
The unit is not able to provide the requested function due
to
- equipment failure (total breakdown),
- mismatch of HW and SW.
Recovery from this error situation is done usually by
replacement of unit HW or ESW.
Green / Red Booting or Unit has not been taken in service yet or the unit has not
(blinking 1 Hz) Waiting been provisioned.
Recovery from this situation is done by taking this unit into
service with FOXCST.
Green Running Unit is up and running, it is ready to provide the required
service.
Off Failure System is not powered or outage of power supply on unit
or outage of LED.
TRAFFIC Red Failure One or more active failures on the unit, independent of the
severity.
More detailed information is provided by FOXCST.
Off Normal Normal (error free) operation.
2018-12-13 81
7.2 Loops
For the CESoP instances, applicable for external and internal user ports, OPIC2 offers two
different types of diagnostic loops for maintenance purposes.
The Back-to-Back Loop 2b redirects the received data from the network back to the net-
work. The network connection between the local OPIC2 and the remote OPIC2 can be
tested.
The Front-to-Front Loop 3b sends the user data transmitted by the TPE back to the TPE.
The connection between TPE and local OPIC2 can be tested.
Only one loop 2b or 3b can be active at the same time.
OPIC2
GbE star
TPE Back-To-Back
or Loop 2b Processing
Front-To-Front
Loop 3b
PBUS T
Figure 34: Back-to-Back loop 2b and Front-to-Front loop 3b
Please note:
An active loop 2b or 3b is traffic disturbing.
The Back-to-Back loop 2b according to ITU-T X.150 is the so called remote loop. The loop
selector is located close to the OPIC2 user interface and replaces the transmit signal by
the receive signal.
OPIC2 A OPIC2 B
local remote
T
R
TPE Packet TPE
Processing
A Network Back-To-Back B
Loop 2b
T
R
AIS
Figure 35: Back-to-Back loop 2b
The Back-to-Back loop 2b activation at location A requires that the loop command is
transported to the remote OPIC2 at location B.
The Back-to-Back loop 2b at location B can be activated
• from FOXCST at location A.
• from FOXCST at location B.
The Front-to-Front loop 3b according to ITU-T X.150 is the so called local loop. The loop
selector is located close to the CESoP interface of OPIC2 and replaces the receive signal
by the transmit signal.
OPIC2 A OPIC2 B
local remote
T
R
TPE Packet TPE
Processing
A Front-To-Front
Network B
Loop 3b
T
R
AIS
Figure 36: Front-to-Front Loop 3b
2018-12-13 82
The Front-to-Front loop 3b at location A can be activated

• from FOXCST at location A.
When applying a loop the operational state of the port changes to “Testing” and the
“Maintenance Function Active” (MFA) alarm is activated.
7.3 Maintenance
7.3.1 Inventory Data

It is possible to read inventory data from the OPIC2 unit via the FOXCST with the follow-
ing access point:
AP: /unit-x, Main - Inventory.
7.3.2 Unit ESW Download

It is possible to update the embedded software (ESW) of the OPIC2 unit via software
download.
Please refer to [1KHW002466] User Manual “FOXCST” for the description of the ESW
download.

The assignment of new embedded software restarts the OPIC2 unit.
Thus, the installation of new ESW on the unit affects all traffic functions of
the OPIC2 unit.
2018-12-13 83
FOX61x | OPIC2 USER INTERFACE REFERENCE
8 User Interface Reference

This section gives a complete reference of the managed objects, properties, and com-
mands of the OPIC2 functional unit of the FOX61x as far as these are not covered in the
generic descriptions in refer to [1KHW002464] User Manual “FOX615/FOX612”.
For a description on how to configure and bring into operation the OPIC2 unit and its
main functions, please refer to section 6 Commissioning (on page 47).
8.1 Introduction
Below, you will find a detailed description of all the configuration parameters and opera-
tions belonging to the managed objects model (MOM) for the OPIC2 service unit.
Figure 37 shows the access point (AP) tree for the OPIC2 unit with its managed objects.
<ap>
FOX61x
0 … 20 <ap>
unit-x: OPIC2
<ap>
4
port-y
Teleprotection
<ap>
1
port-5
IRIG-B opt.
<ap>
1
port-6
IRIG-B el.
1 <ap>
circuitEmulation
4 <ap>
cesop-z
0 … 32 <ap>
chan-c
1 <ap>
vlanInterfaces
8 <ap>
vif-z_v
Figure 37: MOM (managed object model) of the OPIC2 unit
With these managed objects (MOs) the following functions are covered:
2018-12-13 84
Table 11: Managed objects (MOs) for OPIC2

MO Description of the management functions
unit-x: OPIC2 Rxx Restart of the unit, management of the unit ESW, labeling, indication of
(opic2_r1c) the equipment status, display of inventory data, presentation of log-
books.
Configuration of the source IP Address.
port-y Management of the TPE ports. Configuration of the interface type, mode
and data rate parameters, status information.
port-5: IRIG-B optical Management of the optical IRIG-B port. Configuration of the IRIG-B sig-
nal format.
port-6: IRIG-B electrical Management of the electrical IRIG-B port. Configuration of the IRIG-B
signal format.
circuitEmulation This MO is a container for the cesop-z
cesop-z Management of the Circuit Emulation over Packet switched networks.
Configuration of the source assignment, TDM frames per Ethernet
frame, E2E transmission delay, diagnostic loop activation and status
information.
chan-c Channels are the connection termination points (CTP) for the P0_nc and
P12 traffic signal cross connections. For the configuration of cross con-
nections please refer to [1KHW002467] User Manual “TDM Services”.
vlanInterfaces This MO is a container for the vif-z_v
vif-z_v Management of VLAN interfaces.
Configuration of VLAN ID and priority. Status information and statistics.
For each of the managed objects, properties and commands, the FOXCST “Tree View” is
given.
This reference section comprises the management functions:
• “Overview”
• “Main”
• “Configuration”
• “Fault Management”
• “Performance Management”
• “Status”
Most of the APs only offer a part of the management functions listed above.
The order of appearance of the management function descriptions is in accordance with
the APs in the FOXCST AP tree and the availability of the management functions of each
AP.
In the tables of the sections below, the parameter default values for properties are under-
lined.
Please note:
For better legibility of numbers in this User Manual, inverted commas are
used when the number’s size exceeds three digits (e.g. 40’000). In parameter
entry fields of the FOXCST, these inverted commas must not be entered.
Instead, the numbers are entered without these inverted commas (e.g.
40000).
Please note:
Screenshots presented in this reference may show configurations or data
that may not correspond to the FOXCST you see when managing your FOX61x
equipment.
2018-12-13 85
8.2 AP: /unit-x: OPIC2
8.2.1 AP: /unit-x, Overview

For a description of the
− “Overview – Alarms”,
− “Overview – Cross Connections”,
− “Overview – Timeslot Allocation”, and
− “Overview – Unused Channels”
management functions, please refer to [1KHW002464] User Manual “FOX615/FOX612”.
8.2.2 AP: /unit-x, Main

− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”
8.2.3 AP: /unit-x, Configuration
8.2.3.1 AP: /unit-x, Configuration – General
Table 12: AP: /unit-x, Configuration – General

Operation Name Parameter Name Range Description / Details
Source Addresses Source IP Address <IPv4 address> Source IP address of the OPIC2 unit.
The default is 192.168.100.100.
Source MAC Address <MAC address> Source MAC address of the OPIC2 unit.
The MAC address cannot be changed.
8.2.3.2 AP: /unit-x, Configuration – Time Reference
2018-12-13 86
Table 13: AP: /unit-x, Configuration – Time Reference

NE high precision QL Frequency Thresh- 3 … 6 … 11 Set the threshold of the Quality Level (QL) of
(PTP) old the SyncE. It is recommended to set to the
default value 6.
If the QL of the timing in the network falls
below the configured level then the time
dependent service (IRIG-B output) will be
switched-off and OPIC2 will switch to another
synchronization source according to the con-
figured priorities in the table above.
This configuration applies for the use case
when PTP is an active time source.
Note: A lower QL value means a better quality.
For more information refer to [1KHW028636]

Application Note “Design Guide for MPLS-TP
based Utility Networks”
8.2.4 AP: /unit-x, Fault Management

For a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
The following table lists the fault causes of the current AP.
Table 14: AP: /unit-x, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
BPCF Backplane Clock Failure Equipment true Major Backplane Master clock failed or
Alarm cannot be detected by OPIC2.
OPIC2 operation switches off.
BPPF Backplane PPS Failure Equipment true Major Backplane PPS signal failed or
Alarm cannot be detected by OPIC2.
OPIC2 operation switches off.
EQM Equipment Malfunction Equipment false Critical The OPIC2 controller detects any
Alarm anomalies on the unit, e.g. a volt-
age is missing, a chip does not
respond, etc.
GSW General Software Alarm Equipment false Major An ESW internal error has been
Alarm detected that might inhibit the
ESW from running correctly.
HWIC Hardware Incompatible Equipment true Major The plugged HW is not compati-
With Configuration Alarm ble with the unit configuration
HW stored in the database. You
may need to change the HW or
re-create the configuration for
the unit.
MFA Maintenance Function Communication true Warning A maintenance function has
Active Alarm been activated by the operator.
NPHM No Pure Hybrid Mode Equipment true Warning The ABB Pure hybrid mode is not
Alarm selected on the core unit. Use
PTP Wizard to enable it.
2018-12-13 87
Table 14: AP: /unit-x, Fault Management (continued)

Affecting Severity
NSW No Application Software Equipment true Major There is no application ESW
Alarm installed on the unit, or the appli-
cation ESW has not yet finished
its boot process.
OOS Out Of Synchronization Equipment true Major Synchronization to PTP time
Alarm source failed.
PRC PBUS Resource Conflict Processing true Major The PBUS access circuit of
Error Alarm another TDM unit in the subrack
is defective. Remove or unassign
the other TDM units in the sub-
rack one by one until the alarm is
cleared. Replace the defective
unit.
PWRSVE Battery Power Saving Equipment true Critical Power saving is active on the
Alarm unit, i.e. it is kept in the “reset”
state during battery power
backup.
RAF Realignment Failed Equipment true Major OPIC2 cannot get Time of Day
Alarm information from the core unit.
SSWNA Scheduled Software Equipment false Minor The ESW that is scheduled for
Not Available Alarm installation is not available on
the unit. Make sure that the ESW
is downloaded to the unit.
SWIC Software Incompatible Equipment true Major The ESW running on the unit is
With Configuration Alarm not compatible with the unit
configuration stored in the data-
base. You may need to upgrade,
or downgrade the ESW, or recre-
ate the configuration with the
currently running ESW.
SWIN Software Incompatible Equipment true Major The running ESW is not compati-
With Network Element Alarm ble with the version required by
the NE type or version.
SWM Software Mismatch Equipment false Minor The running ESW does not match
Alarm the assigned ESW.
UIC Unit Incompatible Equipment true Major The inserted unit is not compati-
Alarm ble with the assigned unit.
UNAS Unit Not Assigned Equipment false Warning The unit is not assigned and can-
Alarm not be configured. To assign the
unit, execute the “Assign” com-
mand in the “Main” function of
the unit.
UNAV Unit Not Available Equipment true Critical The unit that is configured is
Alarm either not plugged or not recog-
nized due to a failure.
2018-12-13 88
8.2.5 AP: /unit-x, Status
8.2.5.1 AP: /unit-x, Status – Unit Event Recorder
select the “Number Of Events” to be displayed:
“Unit Event Recorder” dialog:
Table 15: AP: /unit-x, Status – Unit Event Recorder

Unit Event Recorder Number Of New 0 … 4’294’967’295 Shows the number of new unit events
Events occurred since the last Acknowledge of
events.
Acknowledge Reset the number of new events without
modifying the content of the unit event
recorder.
Clear Event Reset the number of new events and delete
the content of the unit event recorder.
Show Unit Event Open the GUI dialog to select the number of
Recorder … events to be displayed.
Show Unit Event Number Of Events All Display all available unit events.
Recorder 5 Display the number of latest unit events.
10
20
50
100
150
200
250
500
750
1000
1500
2000
2018-12-13 89
Table 15: AP: /unit-x, Status – Unit Event Recorder (continued)

Unit Event Recorder Index Index number of the event. The index number
Array is increased with every new event.
Time Stamp yyyy-mm-dd Time stamp of the event.
hh:mm:ss.mmm
Address <MO address> Managed object address where the event
occurred.
Id <alarm ID> Alarm identifier of the event.
Description Alarm description of the event.
State Active alarm state of the event.
Cleared alarm state of the event.
8.3 AP: /unit-x/port-y (y = 1 … 4)
8.3.1 AP: /unit-x/port-y, Overview

− “Overview – Alarms”
management function, please refer to [1KHW002464] User Manual “FOX615/FOX612”.
8.3.2 AP: /unit-x/port-y, Main
8.3.2.1 AP: /unit-x/port-y, Main - General

− “Main - General”
8.3.2.2 AP: /unit-x/port-y, Main - Admin And Oper Status
Table 16: AP: /unit-x/port-y, Main – Admin And Oper Status

Administrative Status State Up Set the IETF administrative status of the tele-
Down protection SFP port.
Operational Status State Up Display of the IETF operational status of the

Down teleprotection SFP port.
Testing
Unknown
Dormant
Not Present
Lower Layer Down
2018-12-13 90
8.3.2.3 AP: /unit-x/port-y, Main - SFP
Table 17: AP: /unit-x/port-y, Main – SFP

Equipment Inventory Equipment State Ok Equipment state of the plugged SFP module.
Unknown
Empty
Plugged
Mismatch
Failed
Module Type 0 … 16 characters In the SFP module type the following abbrevi-
ations are used:
- SM: Single mode fiber
- SR: Short reach
- IR: Intermediate reach
- LR: Long reach
- XR: Enhanced long reach
Manufacturer Serial 0 … 16 characters These description fields provide information
Number about the vendor, part number, production
Manufacturing Date 0 … 10 characters date and serial number.
Manufacturer ID 0 … 16 characters
Manufacturer Part 0 … 16 characters
Number
8.3.3 AP: /unit-x/port-y, Configuration
8.3.3.1 AP: /unit-x/port-y, Configuration - Interface
2018-12-13 91
Table 18: AP: /unit-x/port-y, Configuration - Interface

Interface Type IEEE C37.94 Selects the IEEE C37.94 (IEC 62843) standard
optical transmission protocol to be used for
port-y.
ABB TPE Selects the ABB proprietary FOX6plus com-
patible optical transmission protocol to be
used for port-y.
Number Of Protec- 1 For IEEE C37.94 (IEC 62843) interface type use
tion Channels 2 1 (64 kbit/s) to 12 (768 kbit/s) depending on
the data rate of the remote equipment con-
3 nected to port-y.
4 For ABB TPE interface type use 1:
- 1 (64 kbit/s): for transmission of Ch1 only;
5
- 2 (128 kbit/s): for transmission of Ch1 and
6 „Rem Alarm Ch“.
7
8
9
10
11
12
1. For ABB teleprotection equipment types NSD570 and NSD70D, and for ABB protection relay types REL316,
REL551 and REL561 use “1” (64 kbit/s).
8.3.3.2 AP: /unit-x/port-y, Configuration - Interoperability
Table 19: AP: /unit-x/port-y, Configuration - Interoperability

Frame Synchroniza- FSP Loop Prevention Used to prevent FSP loops on the OPIC2 port.
tion Pulse Enabled See section 5.3.1 Optical Teleprotection
Equipment (TPE) Interface (on page 30).
All One Transmission All One Tx Suppres- Used for interoperability with the ABB TPE
sion Enabled interface and the REL551 differential protec-
tion device from ABB.
Enable this function if this combination of
device and interface is used.
8.3.4 AP: /unit-x/port-y, Fault Management

2018-12-13 92
Table 20: AP: /unit-x/port-y, Fault Management

Affecting Severity
DEG Degraded Signal Communication true Minor Degraded signal (IEEE C37.94
Alarm and ABB TPE)
For IEEE C37.94 the alarm is
raised when at least one bit error
is detected in the channel data
(payload) over a monitoring
period of one second. It is
released when no bit error
occurred during the last second.
For ABB TPE the alarm is raised
when at least one parity bit error
is detected over a monitoring
period of one second. It is
released when no error occurred
during the last second.
DRM Data Rate Mismatch Communication true Minor Data rate mismatch (IEEE C37.94
Alarm only)
IEEE defines the data rate as
nx64 kbit/s where n = 1 … 12.
This information is exchanged
between OPIC2 and the con-
nected TPE within the overhead
data of the C37.94 frame. The
alarm is raised, when the
received value does not match
the configured value.
ENA Equipment Not Available Equipment true Major No SFP module is present.
Alarm
LOF Loss Of Frame Communication true Major Receiver detected errors in the
Alarm frame alignment of the input sig-
nal (IEEEC37.94 and ABB TPE).
Frame alignment is assumed to
have been lost and the alarm is
raised when three consecutive
incorrect frame alignment sig-
nals have been received. It is
recovered when at least three
consecutive correct frame align-
ment signals have been received.
2018-12-13 93
Table 20: AP: /unit-x/port-y, Fault Management (continued)

Affecting Severity
LOS Loss Of Signal Communication true Major Low or no received power level
Alarm (IEEEC37.94 and ABB TPE) or
receiver detects errors in the
input signal
Alarm activated by the SFP mod-
ule (“LOS” according to MSA INF-
8074i).
Additionally for IEEE C37.94 the
receiver activates LOS within
1 ms after receiving two or more
errors in eight consecutive fram-
ing patterns.
The alarm is cleared upon receiv-
ing eight consecutive correct
framing patterns.
Additionally for ABB TPE the
receiver activates LOS when the
Bit Error Ratio (BER) of the
MCMI-coded incoming data
reaches > 10-3.
RDI Remote Defect Indication Communication true Minor Remote defect indication bit in
Alarm input signal received (IEEEC37.94
“yellow bit” / ABB TPE “Rem
Alm”)
The communication from OPIC2
to connected TPE is disturbed
and the TPE signalizes this
defect by asserting the defect
indication bit.
TLOFA TPE Loss Of Frame Align- Communication true Major 8 kHz clock error (ABB TPE only)
ment Alarm For ABB TPE the alarm is raised
when 8 kHz clock in the frame is
not detected or has a wrong
duty cycle for at least 3 consecu-
tive periods (24 frames with 32
bit, 375 µs). It is released when 8
kHz clock in the frame is
detected correctly for at least 3
consecutive periods (24 frames
with 32 bit, 375 µs).
The monitoring of this alarm
must be deactivated when a
REL551 or REL316*4 relay is con-
nected to the port. With the
REL551 or REL316*4 relay an
active TLOFA alarm indicates no
disturbed communication.
TLOS TPE Loss Of Synchroniza- Communication true Minor TPE out of synchronization
tion Alarm (IEEEC37.94 and ABB TPE)
The alarm is raised when byte
slips are detected over a moni-
toring period of one second. It is
released when no byte slips
occurred during the last second.
2018-12-13 94
Table 20: AP: /unit-x/port-y, Fault Management (continued)

Affecting Severity
TRDEG 1 Transmitter Degraded Equipment false Minor The SFP module reports that the
Alarm optical output power has fallen
below the lower power thresh-
old (SFP specific, typically 2 dB
below the normal module oper-
ating range).
TRF2 1 Transmitter Failure Equipment true Major No optical output power.
Alarm
TRPE 1 Transmitter Power Equipment false Minor The SFP module reports that the
exceeded Alarm optical output power has
exceeded the upper power
threshold (SFP specific, typically
2 dB above the normal module
operating range).
1. The support of this alarm is only possible for SFP modules with diagnostics function.
Please note:
Monitoring of the TLOFA fault cause should be disabled for IEEE C37.94 inter-
faces.
Please note:
Monitoring of the TLOFA fault cause should be disabled for REL551 and
REL316*4 relays.
→ An active alarm with one of these relays does not indicate a disturbed com-
munication.
8.3.5 AP: /unit-x/port-y, Status
8.3.5.1 AP: /unit-x/port-y, Status - DDM
2018-12-13 95
Table 21: AP: /unit-x/port-y, Status - DDM

DDM Status DDM Interface Sup- Supported If diagnostic is supported, some physical
port Unknown parameters are displayed.
Module Temperature °C Temperature of the SFP module.
Supply Voltage V Supply voltage for the SFP.
TX Bias Current mA Bias current of the transmit interface.
TX Output Power dBm Optical power at the transmit interface.
RX Input Power dBm Optical power at the receive interface.
Please note:
OPIC2 supports diagnostics for SFP modules. Support of diagnostics is not
mandatory for SFP modules with optical interfaces. However ABB recom-
mends only optical SFP modules that support diagnostics.
8.4 AP: /unit-x/port-5: IRIG-B (IRIG-B opt.)
8.4.1 AP: /unit-x/port-5, Overview

− “Overview - Alarms”
8.4.2 AP: /unit-x/port-5, Main
8.4.2.1 AP: /unit-x/port-5, Main - General

8.4.2.2 AP: /unit-x/port-5, Main - Admin And Oper Status
Table 22: AP: /unit-x/port-5, Main – Admin And Oper Status

Administrative Status State Up Set the IRIG-B optical port administrative sta-
Down tus.
Operational Status State Up Display of the IRIG-B optical port operational

Down status.
2018-12-13 96
8.4.3 AP: /unit-x/port-5, Configuration
8.4.3.1 AP: /unit-x/port-5, Configuration - Output Circuit
Table 23: AP: /unit-x/port-5, Configuration - Output Circuit

IRIG-B Format IRIG Format IRIG-B002 Selection of the format of the IRIG-B optical
IRIG-B006 port.
8.4.4 AP: /unit-x/port-5, Fault Management

Table 24: AP: /unit-x/port-5, Fault Management

Affecting Severity
OSSO Output Signal Switched Equipment true Major IRIG-B output is switched off in
Off Alarm case OPIC2 is not synchronized
to a PTP time source.
8.5 AP: /unit-x/port-6: IRIG-B (IRIG-B el.)
8.5.1 AP: /unit-x/port-6, Overview

− “Overview - Alarms”
8.5.2 AP: /unit-x/port-6, Main

8.5.2.1 AP: /unit-x/port-6, Main - Admin And Oper Status
2018-12-13 97
Table 25: AP: /unit-x/port-6, Main – Admin And Oper Status

Administrative Status State Up Set the IRIG-B electrical port administrative
Down status.
Operational Status State Up Display of the IRIG-B electrical port opera-

Down tional status.
8.5.3 AP: /unit-x/port-6, Configuration
8.5.3.1 AP: /unit-x/port-6, Configuration - Output Circuit
Table 26: AP: /unit-x/port-6, Configuration - Output Circuit

Output Circuit IRIG Format IRIG-B002 Selection of the format of the IRIG-B electrical
IRIG-B006 port.
8.5.4 AP: /unit-x/port-6, Fault Management

Table 27: AP: /unit-x/port-6, Fault Management

Affecting Severity
OSSO Output Signal Switched Equipment true Major IRIG-B output is switched off in
Off Alarm case OPIC2 is not synchronized
to a PTP time source.
8.6 AP: /unit-x/circuitEmulation
8.6.1 AP: /unit-x/circuitEmulation, Overview

2018-12-13 98
8.6.2 AP: /unit-x/circuitEmulation, Main

8.6.3 AP: /unit-x/circuitEmulation, Fault Management

Table 28: AP: /unit-x/circuitEmulation, Fault Management

Affecting Severity
VMM VLAN Mismatch Communication false Minor The VLAN address of OPIC2 does
Alarm not correspond to the VLAN
address of the remote OPIC2.
8.7 AP: /unit-x/circuitEmulation/cesop-z
8.7.1 AP: /unit-x/circuitEmulation/cesop-z, Overview

8.7.2 AP: /unit-x/circuitEmulation/cesop-z, Main

8.7.2.1 AP: /unit-x/circuitEmulation/cesop-z, Main - Admin And Oper Status
2018-12-13 99
Table 29: AP: /unit-x/circuitEmulation/cesop-z, Main – Admin And Oper Status

Administrative Status State Up Set the circuit emulation service administra-
Down tive status.
Operational Status State Up Display of the circuit emulation service opera-

Down tional status.
8.7.3 AP: /unit-x/circuitEmulation/cesop-z, Configuration
8.7.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration – General
“VLAN Authentication Key” dialog:
Table 30: AP: /unit-x/circuitEmulation/cesop-z, Configuration – General

Termination Mode Terminated Opti- Use the optical TPE front port to access data
cal Port for the cesop-z.
Terminated Inter- Use the internal PBUS port to access data on
nal Port P0_nc level (n x 64 kbit/s, n = 1-32) for the
cesop-z.
Transparent Inter- Use the internal PBUS port to access data on
nal Port P12 level (2048 kbit/s) for the cesop-z.
IP Parameters Source IP Address <IPv4 address> The source IP address of the OPIC2 unit is
configured on the unit AP.
It is shown here for reference purposes.
Destination IP <IPv4 address> Destination IP address of the remote OPIC2
Address unit the cesop-z is connected to.
Default address: 192.168.100.101.
2018-12-13 100
Table 30: AP: /unit-x/circuitEmulation/cesop-z, Configuration – General (continued)

TTI TTI Supervision The trail trace identifier (TTI) supervision can
be enabled or disabled.
In the disabled mode no check is done on the
received TI and no alarm is generated.
Transmitted TTI <15 characters> The transmitted trail trace identifier (TTI).
A TTI shorter than 15 characters is automati-
cally completed with SPACE characters.
Expected TTI <15 characters> The expected trail trace identifier (TTI).
A TTI shorter than 15 characters is automati-
cally completed with SPACE characters.
Vlan Authentication Open the GUI dialog to specify a custom
Key … authentication key.
Authentication Key New Key 6 … 32 characters Specify a custom authentication key.
The key must contain at least one alphabetic
and one numeric character.
The key must contain at least one special
character:
!”#$%&’()*+,-/:;<=>?@[]^_‘{|}~
The default key is empty.
Confirm Key 6 … 32 characters Confirm the new key.
The default key is empty.
8.7.3.2 AP: /unit-x/circuitEmulation/cesop-z, Configuration – Maintenance
Table 31: AP: /unit-x/circuitEmulation/cesop-z, Configuration – Maintenance

Loop Allow Activation Of Enable the loop activation possibility from
Loop 2b From Remote the remote OPIC2 unit.
8.7.3.3 AP: /unit-x/circuitEmulation/cesop-z, Configuration – CESoP
2018-12-13 101
Table 32: AP: /unit-x/circuitEmulation/cesop-z, Configuration – CESoP

CESoP Configuration Number Of TDM 1 This parameter has impact on the packetiza-
Frames Per Ethernet 2 tion delay due to longer waiting times for the
Frame TDM frames and on the bandwidth due to the
4 fixed overhead size per packet.
8
E2E Transmission 1, 2 … 6 … 20 ms, OPIC2 will provide the configured end-to-end
Delay step 2 ms transmission delay towards the front inter-
faces and towards the PBUS.
It has to be understood as a constant OPIC2
transmission delay despite data is transmit-
ted over the WAN with non-constant switch-
ing delays.
E2E Transmission OFF The threshold provides warning to the cus-
Delay Threshold 1, 2 … 18 ms, tomer that the transmission delay through
step 2 ms the WAN exceeds the configured value.
This feature can be useful for network opera-
tion in order to be able to react to changing
network condition before the configured end-
to-end transmission delay is exceeded and
OPIC2 traffic is switched off.
The valid configuration range depends on the
configured “E2E Transmission Delay” parame-
ter.
Refer to 5.4.1.3 "Performance Monitoring" (on
page 38).
CESoP Payload Sizes Packetization Delay 0.125 … 1.0 ms Packetization delay depends from the “Num-
ber Of TDM Frames Per Ethernet Frame”
parameter.
Refer to Table 9: "Configurable CESoP pay-
load sizes" (on page 35).
Bandwidth 0.656 … 6.784 Bandwidth required to transmit OPIC2 traffic.
Mbps Refer to Table 9: "Configurable CESoP pay-
load sizes" (on page 35).
8.7.3.4 AP: /unit-x/circuitEmulation/cesop-z, Configuration – Channels
Please note:
The channel settings are only applicable if the Internal Port is chosen as
source in the Configuration – General Tab (see also section 8.7.3.1 AP: /unit-x/
circuitEmulation/cesop-z, Configuration – General (on page 100).
“Create Channel” and “Create Multiple Channels” dialogs:
2018-12-13 102
The “Create Advanced Channel” command displays the created channel:
“Delete Channel” dialog:
Table 33: AP: /unit-x/circuitEmulation/cesop-z, Configuration - Channels

Create Channel … Open the FOXCST dialogue to create a chan-
nels. A channel is a connection termination
point (CTP) used as a starting or ending point
of a cross connection.
Create Channel Index 0 … 32 The channel index is used to identify the
channel.
0 is a reserved value used for the auto-assign-
ment of a channel index: The auto-assigned
index is the highest existing index number +
1.
In the FOXCST the default value is the autoas-
signed index number.
Layer Rate P12 Unstructured 2048 kbit/s.
Automatically selected when the termination
mode is configured to “Transparent Internal
Port.
P0_nc Structured n x 64 kbit/s.
Automatically selected when the termination
mode is configured to “Terminated Internal
Port”.
n 1 … 32 Number of consecutive timeslots (valid for
P0_nc only).
The default value is the maximum of available
timeslots.
Start Timeslot 0 … 31 First timeslot of the channel in the structured
P12 signal (valid for P0_nc only).
2018-12-13 103
Table 33: AP: /unit-x/circuitEmulation/cesop-z, Configuration - Channels (continued)

Create Multiple Chan- Open the FOXCST dialogue to create one or
nels … more channels.
The termination mode must be configured to
“Terminated Internal Port”.
Create Multiple Chan- Start Index 0 … 32 The start index is the channel index of the
nels first channel.
1.
Number Of Channels 1 … 32 Number of channels to be created.
If the configured number of channels to be
created is higher than the available number of
unused time slots, the FOXCST creates no
channel, and displays a corresponding error
message.
n 1 … 32 Number of consecutive timeslots.
The default value is the maximum of available
timeslots.
The start timeslot of the first channel is the
lowest available timeslot number.
Create Advanced Open the FOXCST dialogue to create one
Channel … channel with non-consecutive timeslots in the
structured P12 signal.
The termination mode must be configured to
“Terminated Internal Port”.
Create Advanced Index 0 … 32 The channel index is used to identify the
Channel channel.
1.
Timeslot(s) <Timeslot range> Configure the time slots to be used. A range
of consecutive time slots is defined by
“..”, e.g. “5..9”.
Different ranges are separated by
“,”, e.g. “1, 4, 5..9, 31”.
Delete Channel … Open the FOXCST dialogue to delete one or
all channels.
Delete Channel Delete Channel All Delete all channels.
All connections assigned to the channels will
be deleted also.
chan-1 … chan-32 Delete a channel.
All connections assigned to the channel will
be deleted also.
8.7.4 AP: /unit-x/circuitEmulation/cesop-z, Fault Management

2018-12-13 104
The following table lists the Fault Causes of the current AP.
Table 34: AP: /unit-x/circuitEmulation/cesop-z, Fault Management

Affecting Severity
DAKA Default Authentication Communication false Warning Default authentication key is
Key Active Alarm used.
It is recommended to modify the
default key to a strong custom
authentication key.
DMANR Destination MAC Address Communication true Major The local station cannot resolve
Not Resolved Alarm the MAC address of the remote
station.
No ARP reply after 10 ARP
requests.
The ARP protocol is used for
MAC address resolution. Ensure
the correct IP address settings
of the local and the remote
OPIC2 unit and the WAN channel
conditions.
EAF Excessive Authentication Communication false Warning Ethernet packets are wrongly
Fail Alarm authenticated or replied.
EPD Excessive Packet Delay Communication true Major Ethernet packets from both
Alarm redundant paths are received
after the configured TDM delay
but within 20 ms.
Please reconsider the config-
ured cesop-z E2E TDM Delay.
EPL Excessive Packet Loss Communication true Major Ethernet packets from both
Alarm redundant paths are received
after the 20 ms TDM delay or are
not received at all.
GMIDM Grandmaster ID Mis- Communication true Minor The local Grandmaster ID is dif-
match Alarm ferent from the remote station
Grandmaster ID.
Active Alarm been activated by the operator
from the communication channel
status dialog.
PCM Path Capacity Mismatch Communication true Minor Discrepancy between the config-
Alarm ured and the received Circuit
Emulation payload size.
PEPD Protection Path Exces- Communication true Warning Ethernet packets from only one
sive Packet Delay Alarm redundant path are received
after the configured TDM delay
but within 20 ms.
PEPL Protection Path Exces- Communication true Minor Ethernet packets from only one
sive Packet Loss Alarm redundant path are received
after the 20 ms TDM delay or are
not received at all.
TDMDM TDM delay Mismatch Communication true Major The E2E Transmission Delay
Alarm parameter is not the same on
both sides of the cesop-z link.
TIM Trail Identifier Mismatch Communication true Major Discrepancy between the
Alarm expected and the received Trail
Identifier.
2018-12-13 105
8.7.5 AP: /unit-x/circuitEmulation/cesop-z, Status
8.7.5.1 AP: /unit-x/circuitEmulation/cesop-z, Status - General
Table 35: AP: /unit-x/circuitEmulation/cesop-z, Status - General

Remote Address IP Address <IPv4 address> IP address of the remote side the cesop-z has
to communicate to.
Resolved Display if the ARP request with the configured
remote IP address is resolved.
Communication can only be started if the
remote MAC address is known.
MAC Address <MAC address> Display of the physical (MAC) address of the
remote OPIC2.
TTI Status Received TTI 15 characters Display of the received trail trace identifier
(TTI).
TTI State Not Checked TTI Supervision is disabled.
OK The received TTI matches the expected TTI.
Mismatch The received TTI does not match the
expected TTI.
Remote TDM Delay E2E Transmission 0 … 20 ms E2E transmission delay from the remote side.
Delay If the delay does not match the locally config-
ured E2E Transmission Delay parameter, AIS
(ALL 1 signal) will be sent to the user interface
and an appropriate alarm is raised.
8.7.5.2 AP: /unit-x/circuitEmulation/cesop-z, Status - Maintenance
2018-12-13 106
Table 36: AP: /unit-x/circuitEmulation/cesop-z, Status - Maintenance

Loop Request Request None Deactivate any loop.
Back-To-Back-2b Activates the back-to-back loop.
For more information refer to section 7.2
Loops (on page 82).
Front-To-Front-3b Activates the front-to-front loop.
Loops (on page 82).
Back-To-Back-2b Activates the back-to-back loop on the
(on remote unit) remote unit. This only works if the remote
unit has the corresponding option enabled.
Loops (on page 82).
Loop Status State None No loop is activated.
Back-To-Back-2b The local back-to-back loop is activated with
(On Local Unit Set a local loop request.
Locally)
Back-To-Back-2b The local back-to-back loop is activated with
(On Local Unit Set a remote loop request.
Remotely)
Front-To-Front-3b The front-to-front loop is activated.
(On Local Unit)
Back-To-Back-2b The remote back-to-back loop is activated
(On Remote Unit with a remote loop request.
Set Remotely)
Back-To-Back-2b The remote back-to-back loop is activated
(On Remote Unit with a local loop request.
Set Locally)
8.7.5.3 AP: /unit-x/circuitEmulation/cesop-z, Status - CESoP
2018-12-13 107
Table 37: AP: /unit-x/circuitEmulation/cesop-z, Status - CESoP

Packet Delay Minimum Delay Vif-x_1 0 … 20 ms The minimum delay occurred on vif-x_y
Minimum Delay Vif-x_2 0 … 20 ms over an infinite measuring period.
Maximum Delay Vif-x_1 0 … 20 ms The maximum delay occurred on vif-x_y

Maximum Delay Vif-x_2 0 … 20 ms over an infinite measuring period.
Average Delay Vif-x_1 0 … 20 ms The average delay occurred on vif-x_y

Average Delay Vif-x_2 0 … 20 ms over an infinite measuring period.
Delay Variation Vif-x_1 0 … 20 ms The variation of the delay observed on vif-x_y

Delay Variation Vif-x_2 0 … 20 ms over an infinite measuring period.
8.7.5.4 AP: /unit-x/circuitEmulation/cesop-z, Status - Statistics
Table 38: AP: /unit-x/circuitEmulation/cesop-z, Status - Statistics

Statistics Transmitted Packets vif-x_1 0 … 264-1 Number of transmitted packets on vif-x_y
Transmitted Packets vif-x_2 0 … 264-1 since the last reset.
Received Packets vif-x_1 0 … 264-1 Number of received packets on vif-x_y since

Received Packets vif-x_2 0…2 64-1 the last reset.
Lost Packets vif-x_1 0 … 264-1 Number of lost packets on vif-x_y since the
Lost Packets vif-x_2 0 … 264-1 last reset.
Delayed Packets vif-x_1 0 … 264-1 Number of delayed packets on vif-x_y since

Delayed Packets vif-x_2 0…2 64-1 the last reset.
Running Time 0 … 264-1 s Time elapsed since the last reset.

Reset Statistics Reset all statistics counters and the running
time counter.
8.8 AP: /unit-x/circuitEmulation/cesop-z/chan-c
8.8.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Overview

2018-12-13 108
− “Overview – Cross Connections”, and
− “Overview – CTP”
8.8.2 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Main

8.8.2.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Main - Admin And Oper Status
Table 39: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Main – Admin And Oper Status

Operational Status State Up Display of the channel operational status.
Down The state is up if the administrative state of
the cesop-z is up.
8.8.3 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Configuration
8.8.3.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Configuration - CTP
Please note:
All parameters of layer rate, number of time slots and time slot allocation are
read only.
2018-12-13 109
Table 40: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Configuration - CTP

CTP Configuration Layer Rate P12 Unstructured 2048 kbit/s.
P0_nc Structured n x 64 kbit/s.
n 0 … 2 characters Number of channel timeslots (valid for P0_nc
only).
Timeslot(s) 0 … 64 characters Occupied timeslots in the structured P12 sig-
nal (valid for P0_nc only).
Connected to Remote CTP <MO address> Address string of a connections remote end.
CTPs Without a connection the parameter is empty
Connection Index 0 … 65’535 Index of a connection assigned to the chan-
nel. Without a connection the parameter is
empty
Directionality Bidirectional Directionality of the connection.
Unidirectional
Local Role z-End The channel is the ending point of a connec-
tion.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The channel is the working starting point of a
protected or unprotected connection.
a-End Protecting The channel is the protecting starting point
of a protected connection.
Remote Role z-End The CTP at the connections remote end is the
ending point of a connection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The CTP at the connections remote end is the
working starting point of a protected or
unprotected connection.
a-End Protecting The CTP at the connections remote end is the
protecting starting point of a protected con-
nection.
z-End Configura- Revertive Protec- Revertive protection switching is not applica-
tion tion Switching ble for the OPIC2 unit.
CAS AIS Supervi- Use CAS AIS as protection switching criterion.

sion This parameter is not applicable for OPIC2.
Switch-Over Log- Enable the logging of the protection switch-

ging over events.
Linear Trail Protec- Pilot Channel This parameter is not applicable for the
tion OPIC2 unit.
8.8.4 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Fault Management

− “Fault Management - Status”
2018-12-13 110
Table 41: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Fault Management

Affecting Severity
Active Alarm been activated by the operator.
RTSF Redundant Trail Signal Communication true Minor For unprotected connections:
Failure Alarm Alarm not available.
For protected connections: Sig-
nal failure on the working or pro-
tecting trail.
Alarm activation criteria: when
the frame synchronization has
been lost.
TSF Trail Signal Failure Communication true Major For unprotected connections:
Alarm Signal failure on the working
trail.
For protected connections: Sig-
nal failure on both working and
protecting trail.
Alarm activation criteria: when
the frame synchronization has
been lost.
Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.
8.8.5 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Performance Management

For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615/FOX612”.
The PM parameters are presented in different groups. The following counter group is
available for the OPIC2 channels:
• “Protection” group, see section 8.8.5.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c,
Performance Management - Protection (on page 111).
The following counter intervals are available:
Table 42: PM counter interval availability

Counter interval Protection
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.8.5.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Performance Management - Protection
Table 43: PM group: Protection

PM parameter Description
Switch-Over The protection switch-over count gives informa-
tion about the number and distribution of pro-
tection switching events.
2018-12-13 111
8.8.6 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status
8.8.6.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status – CTP
Table 44: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status – CTP

Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0_nc is
connected to, e.g. /unit-20/port-1/chan-1.
Working Trail, OK No failure on the received signal.
Status SF Signal Fail status on the received signal.
SD Signal Degraded status on the received sig-
nal.
Not Available The status of the received signal is not avail-
able, e.g. when the CTPs role is a-End in a uni-
directional connection.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0_nc is
connected to, e.g. /unit-20/port-1/chan-1.
Protecting Trail, OK No failure on the received signal.
Status SF Signal Fail status on the received signal.
SD Signal Degraded status on the received sig-
nal.
Not Available The status of the received signal is not avail-
able, e.g. when the CTPs role is a-End in a uni-
directional connection.
Active Trail Working The trail from the a-End working remote CTP
has been selected.
Protecting The trail from the a-End protecting remote
CTP has been selected.
Not Available There is no active trail.
Protecting/Wait- In case of revertive protection switching the
To-Restore selector is waiting to switch back to the
restored a-End working remote CTP.
2018-12-13 112
Table 44: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status – CTP (continued)

External Request Request Release Automatic trail selection.
Force Working Force the selector to use the trail from the a-
End working remote CTP.
Force Protecting Force the selector to use the trail from the a-
End protecting remote CTP.
Manual Working This function is not supported by OPIC2.
Manual Protecting This function is not supported by OPIC2.
8.9 AP: /unit-x/vlanInterfaces
8.9.1 AP: /unit-x/vlanInterfaces, Overview

8.9.2 AP: /unit-x/vlanInterfaces, Main

8.10 AP: /unit-x/vlanInterfaces/vif-z_v
8.10.1 AP: /unit-x/vlanInterfaces/vif-z_v, Overview

8.10.2 AP: /unit-x/vlanInterfaces/vif-z_v, Main

8.10.2.1 AP: /unit-x/vlanInterfaces/vif-z_v, Main - Admin And Oper Status
2018-12-13 113
Table 45: AP: /unit-x/vlanInterfaces/vif-z_v, Main – Admin And Oper Status

Administrative Status State Up Set the VLAN interface administrative status.
Down
Operational Status State Up Display of the VLAN interface operational sta-
Down tus.
8.10.3 AP: /unit-x/vlanInterfaces/vif-z_v, Configuration
8.10.3.1 AP: /unit-x/vlanInterfaces/vif-z_v, Configuration – General
Table 46: AP: /unit-x/vlanInterfaces/vif-z_v, Configuration – General

VLAN VLAN ID 1 … 4089 VLAN ID used by the communication channel.
Defaults:
- 11 for vif-1_1
- 12 for vif-1_2
- 21 for vif-2_1
- 22 for vif-2_2
- 31 for vif-3_1
- 32 for vif-3_2
- 41 for vif-4_1
- 42 for vif-4_2
VLAN Priority 0…6…7 VLAN priority used by the communication
channel.
It is recommended to change this parameter
to 7.
For more and actual configuration informa-
tion refer to [1KHW028636] Application Note
“Design Guide for MPLS-TP based Utility Net-
works”.
8.10.4 AP: /unit-x/vlanInterfaces/vif-z_v, Fault Management

The following table lists the Fault Causes of the current AP.
2018-12-13 114
Table 47: AP: /unit-x/vlanInterfaces/vif-z_v, Fault Management

Affecting Severity
DTE Delay Threshold Communication false Warning The configured E2E Transmis-
Exceeded Alarm sion Delay Threshold is
exceeded.
Refer to section 8.7.3.3 AP: /unit-
x/circuitEmulation/cesop-z,
Configuration – CESoP (on
page 101).
8.10.5 AP: /unit-x/vlanInterfaces/vif-z_v, Performance Management

For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615/FOX612”.
The PM parameters are presented in different groups. The following counter group is
available for the OPIC2 channels:
• “VIF” group, see section 8.10.5.1 AP: /unit-x/vlanInterfaces/vif-z_v, Performance Man-
agement - VIF (on page 115).
The following counter intervals are available:
Table 48: PM counter interval availability

Counter interval Protection
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.10.5.1 AP: /unit-x/vlanInterfaces/vif-z_v, Performance Management - VIF
Table 49: PM group: VIF

PM parameter Description
Packet Loss Counter for the lost packets.
Delay Exceedance Counter for packets with a delay higher than the
configured E2E Transmission Delay parameter.
8.10.6 AP: /unit-x/vlanInterfaces/vif-z_v, Status
8.10.6.1 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Statistics
2018-12-13 115
Table 50: AP: /unit-x/vlanInterfaces/vif-z_v, Status - Statistics

Reset Statistic Graphs Reset the graphs in the tabs
- Packet Delay Variation,
- Packet Delay Histogram,
- Packet Loss Variation,
- Packet Loss Histogram.
8.10.6.2 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Delay Variation
Table 51: AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Delay Variation

Packet Delay Variation Observation Interval 0 … 15 min Observation interval for the “History 15 min-
utes” tab.
The measurement interval is 1 minute.
0 … 24 h Observation interval for the “History 24
hours” tab.
The measurement interval is 15 minutes.
0 … 7 days Observation interval for the “History 7 days”
tab.
The measurement interval is 1 day.
Packet Delay ms Measured and calculated packet delay values:
- Minimum Packet Delay (red),
- Maximum Packet Delay (blue),
- Average Packet Delay (green).
- The raw data can be stored with a right
mouse click on the graph.
2018-12-13 116
8.10.6.3 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Delay Histogram
Table 52: AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Delay Histogram

Packet Delay Histo- Packet Delay ms Measured and calculated packet delay values.
gram Number Of Observa- % Packet delay distribution for
tion Intervals - Minimum Packet Delay (red),
- Maximum Packet Delay (blue),
- Average Packet Delay (green).
The observation period is selectable to
- 15 minutes (“History 15 minutes” tab),
- 24 hours (“History 24 hours” tab),
- 7 days (“History 7 days” tab).
The raw data can be stored with a right
2018-12-13 117
8.10.6.4 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Loss Variation
Table 53: AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Loss Variation

Packet Loss Rate Vari- Observation Interval 0 … 15 min Observation interval for the “History 15 min-
ation utes” tab.
The measurement interval is 1 minute.
0 … 24 h Observation interval for the “History 24
hours” tab.
The measurement interval is 15 minutes.
0 … 7 days Observation interval for the “History 7 days”
tab.
The measurement interval is 1 day.
Packet Loss Rate 0 … 100% Measured packet loss rate:
- Packet Loss Rate (red).
2018-12-13 118
8.10.6.5 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Loss Histogram
Table 54: AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Loss Histogram

Packet Loss Rate His- Packet Loss Rate % Measured packet loss rate.
togram Number Of Observa- % Packet loss rate distribution for the
tion Intervals - Packet Loss Rate (red).
The observation period is selectable to
- 15 minutes (“History 15 minutes” tab),
- 24 hours (“History 24 hours” tab),
- 7 days (“History 7 days” tab).
2018-12-13 119
FOX61x | OPIC2 ANNEX
9 Annex
9.1 Associated Documents

[1KHW028777] Release Note “FOX61x”
[1KHW002460] System Description “FOX61x”
[1KHW002497] Operation Instruction “Precautions and Safety”
[1KHW002461] Installation Instruction “FOX615 Installation”
[1KHW002462] Installation Instruction “FOX612 Installation”
[1KHW002464] User Manual “FOX615/FOX612”
[1KHW028522] User Manual “Management Communication”
[1KHW002466] User Manual “FOXCST”
[1KHW002467] User Manual “TDM Services”
[1KHW002469] User Manual “CESM1, CESM1-F”
[1KHW028642] User Manual “CESM2, CESM2-F”
[1KHW002473] User Manual “LEDE1”
[1KHW002478] User Manual “LEDS1”
[1KHW002479] User Manual “LEDA1”
[1KHW002481] User Manual “LECO1”
[1KHW028635] User Manual “OPIC2”
[1KHW002498] Product Guide “FOX61x Cables”
[1KHW028514] Information “Terms and Abbreviations”
[1KHW028636] Application Note “Design Guide for MPLS-TP based Utility Networks”
2018-12-13 120
—
ABB Switzerland Ltd
Power Grids
Bruggerstrasse 72
5400 Baden - Switzerland
Phone: +41 844 845 845

(Customer Contact Center)
E-Mail: communication.networks@ch.abb.com
www.abb.com/communicationnetworks
Document ID: 1KHW028635
Copyright © 2018 ABB. All rights reserved.

Specifications subject to change without notice.

1KHW028635 FOX61x OPIC2 D

Uploaded by

Copyright:

Available Formats

1KHW028635 FOX61x OPIC2 D

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1KHW028635 FOX61x OPIC2 D

Uploaded by

Copyright:

Available Formats

—

Document edition FOX61x System Release: R1 and R2 and R3

Copyright © 2018 ABB 2

6.4 ABB TPE Application with REL551 and REL316*4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

8.10.1 AP: /unit-x/vlanInterfaces/vif-z_v, Overview . . . . . . . . . . . . . . . . . . . . . . . 113

1.1 Precautions and Safety

1.2 Symbols and Notations

Risk of operating trouble!

1.3 Interfaces and Circuit Categories

Table 2: Optical interfaces

Table 2: Optical interfaces (continued)

1.4 Document History

1.5 Target Audience

1.6 Definition of Terms

Table 4: Specific terms

Figure 1: OPIC2 used as access to teleprotection equipment (TPE)

2.2 Unit View

Figure 2: OPIC2 unit view

2.3 Block Diagram

Circuit Emulation Service 1

Figure 3: OPIC2 block diagram

3 Functions and Specifications

3.1 Feature Licenses

Table 5: Functions and specifications

Table 5: Functions and specifications (continued)

4.2 Slots for the OPIC2 Unit

4.3 SFP Modules

4.3.1 SFP Interface Types

4.3.2 SFP Module Mounting

• with a unlocking actuator (generally used on electrical SFP modules).

4.3.2.1 SFP Module with Bail Actuator

Figure 4: SFP module handling

4.3.2.2 SFP Module with Unlocking Actuator

Figure 5: SFP module handling

4.3.3 Optical Attenuators

4.4 Interoperability and Compatibility

4.4.1 FOX51x and FOX61x Teleprotection Units

4.4.2 Previous ESW Revisions

4.5 Connections and Cables

4.5.1 Front Connectors of the OPIC2 Unit

Notch for the A B C D

Figure 6: OPIC2 front panel and interface connectors

Table 6: OPIC2 port-6 front connector pins

4.5.2 Optical TPE Interface Cables

Duplex ST connector Duplex LC connector

Figure 7: Duplex LC to ST adapter cable

Dual FC-PC connector Duplex LC connector

Figure 8: Duplex LC to FC/PC adapter cable

Duplex LC connector Duplex LC connector

Figure 9: Duplex LC to LC cable

4.5.3 Optical IRIG-B Output Cable V9PT

Figure 11: Simplex ST to ST adapter cable

4.5.4 Electrical IRIG-B Output Cable V9IR

4.5.5 Fixing the Cables to the Cable Tray

IEEE C37.94 ABB TPE nx64 kbit/s 2048 kbit/s IRIG-B

Optical TPE Interface PBUS Interface IRIG-B Interface

Circuit Emulation Unit Synchronization

Performance ARP Handling

WAN Core Unit