opic2_um

USER MANUAL
FOX61x
OPIC2, opic2_r15b
Optical Teleprotection, Packet Services,
TDM Services, 4 Ports
OPIC2 User Manual
Document ID 1KHW028635
Document edition FOX61x System Release: R1/R2/R3/R14/R15

Revision: P
Date: 2022-01-11
Copyright and confidentiality Copyright in this document vests in Hitachi Energy.

Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine
scannable form is not permitted, either in whole or in part. The contents of the
manual may not be disclosed by the recipient to any third party, without the prior
written agreement of Hitachi Energy.
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 Hitachi Energy.
Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Manufactured by/for a Hitachi Energy company.
Hitachi Energy Switzerland Ltd (hereinafter referred to as Hitachi Energy) has taken
reasonable care in compiling this document, however Hitachi Energy accepts no
liability whatsoever for any error or omission in the information contained herein and
gives no other warranty or undertaking as to its accuracy.
Hitachi Energy can accept no responsibility for damages, resulting from the use of
the network components or the associated operating software. In addition, we refer to
the conditions of use specified in the license contract.
Hitachi Energy 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 continuously 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 protect the product/software/firmware or the resulting
overall solution, the network, its system and all the interfaces against any kind of
security breaches, unauthorized access, interference, intrusion, leakage and/or theft
of data or information. Hitachi Energy and its affiliates are not liable for damages and/
or losses related to such security breaches, any unauthorized access, interference,
intrusion, leakage and/or theft of data or information.
Although Hitachi Energy 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 2022 Hitachi Energy. All rights reserved. 2

FOX61x | OPIC2
Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Precautions and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Symbols and Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Interfaces and Circuit Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Unit View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3 Functions and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1 Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Slots for the OPIC2 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3 SFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3.1 SFP Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3.2 SFP Module Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3.3 Optical Attenuators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.4 Interoperability and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.4.1 FOX61x System Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.4.2 FOX61x Teleprotection Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.4.3 FOX51x Teleprotection Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.4.4 Previous ESW Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5 Connections and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.1 Front Connectors of the OPIC2 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.2 Optical TPE Interface Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.5.3 Optical IRIG-B or PPS Output Cable V9PT. . . . . . . . . . . . . . . . . . . . . . . 23
4.5.4 Electrical IRIG-B or PPS Output Cable V9IR . . . . . . . . . . . . . . . . . . . . . . 23
4.5.5 Fixing the Cables to the Cable Tray . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.1 Packet Based Teleprotection Signal Transport . . . . . . . . . . . . . . . . . . . . . 25
5.1.2 TDM Based Teleprotection Signal Transport . . . . . . . . . . . . . . . . . . . . . . 25
5.1.3 Synchronization and IRIG-B or PPS Timing . . . . . . . . . . . . . . . . . . . . . . 26
5.1.4 Applications and Functions Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.1 Optical Teleprotection Equipment (TPE) Interface . . . . . . . . . . . . . . . . . . . 27
5.2.2 PBUS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2.3 IRIG-B or PPS Output Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.3 Applications with Packet Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3.1 Teleprotection Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3.2 P0_nc (nx64 kbit/s) Application via Core Unit . . . . . . . . . . . . . . . . . . . . . 34
5.3.3 P12 (2048 kbit/s) Application via Core Unit . . . . . . . . . . . . . . . . . . . . . . . 35
5.4 Applications with TDM Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.1 Teleprotection Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.5 Functions for Packet Based Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.5.1 Circuit Emulation Service (CES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.5.2 Trail Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.6 Functions for TDM Based Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.6.1 PMTS (Performance Monitoring Timeslot) . . . . . . . . . . . . . . . . . . . . . . . 49
5.6.2 PMTS Generated Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.6.3 Bidirectional Symmetrical Linear Trail Protection . . . . . . . . . . . . . . . . . . . . 50

FOX61x | OPIC2
5.6.4 Protection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.7 Synchronization Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.7.1 Unit Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.7.2 IRIG-B and PPS Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.8 IEEE C37.94 Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.8.1 Transmission Protocol / Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . 53
5.8.2 Communication Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.9 FOX6plus Frame Compatible Hitachi Energy Teleprotection Equipment Protocol . . . . . . . . 55
5.10 FO5 Protection Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.11 IRIG-B Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.11.1 Signal Identification Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.11.2 IRIG-B 002/006 Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.11.3 IRIG-B Leap Second Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.1.1 Core Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.1.2 OPIC2 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.1.3 FOXCST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.1.4 PETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.2 TPE Link Commissioning with Packet Transport . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.2.1 IEEE C37.94 Application with RED670 64 kbit/s LDCM Module . . . . . . . . . . . . 61
6.2.2 IEEE C37.94 Application with RED670 2 Mbit/s LDCM Module . . . . . . . . . . . . 65
6.2.3 Hitachi Energy TPE Application with REL551 and REL316*4 . . . . . . . . . . . . . 68
6.2.4 Differential Protection over E1 Interface . . . . . . . . . . . . . . . . . . . . . . . . 72
6.2.5 Differential Protection over E0 Interface . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2.6 Differential Protection over X.24-V.11 Interface 1984kbit/s. . . . . . . . . . . . . . . 78
6.2.7 Differential Protection over 2/4-wire Analog Interface . . . . . . . . . . . . . . . . . 81
6.2.8 Basic MPLS-TP Configuration for a Redundant OPIC2 Link . . . . . . . . . . . . . . 84
6.2.9 Basic EoS and MPLS-TP Configuration for a Redundant OPIC2 Link . . . . . . . . . 91
6.3 TPE Link Commissioning with TDM Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.3.1 IEEE C37.94 Application with Traffic Protection for RED670 Line Differential Protection Re-
lays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.3.2 IEEE C37.94 Application without Traffic Protection for NSD570 Teleprotection Equipment
and G1LOa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
6.3.3 Hitachi Energy TPE Application with Traffic Protection for REL551 and REL316*4 Line Dif-
ferential Protection Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.3.4 Hitachi Energy TPE Application without Traffic Protection for NSD570 Teleprotection
Equipment and G1LO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.3.5 Hitachi Energy TPE Application without Traffic Protection for NSD570 Teleprotection
Equipment and G1LOa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.4 Migration from OPIC1 to OPIC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
7 Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
7.1 Unit Optical Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
7.2 Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
7.2.1 CES Layer Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
7.2.2 TDM Layer Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
7.3 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
7.3.1 Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
7.3.2 Unit ESW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
8 User Interface Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
8.2 AP: /unit-x: OPIC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
8.2.1 AP: /unit-x, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

FOX61x | OPIC2
8.2.2 AP: /unit-x, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

8.2.3 AP: /unit-x, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
8.2.4 AP: /unit-x, Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
8.2.5 AP: /unit-x, Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.3 AP: /unit-x/port-y (y = 1 … 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.3.1 AP: /unit-x/port-y, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.3.2 AP: /unit-x/port-y, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
8.3.3 AP: /unit-x/port-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
8.3.4 AP: /unit-x/port-y, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . . 128
8.3.5 AP: /unit-x/port-y, Performance Management . . . . . . . . . . . . . . . . . . . . . 131
8.3.6 AP: /unit-x/port-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
8.4 AP: /unit-x/port-5: IRIG-B (IRIG-B opt.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.4.1 AP: /unit-x/port-5, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.4.2 AP: /unit-x/port-5, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.4.3 AP: /unit-x/port-5, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.4.4 AP: /unit-x/port-5, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . . 134
8.5 AP: /unit-x/port-6: IRIG-B (IRIG-B el.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
8.5.1 AP: /unit-x/port-6, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
8.5.2 AP: /unit-x/port-6, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
8.5.3 AP: /unit-x/port-6, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.5.4 AP: /unit-x/port-6, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.6 AP: /unit-x/tdmChannels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.6.1 AP: /unit-x/tdmChannels, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 135
8.6.2 AP: /unit-x/tdmChannels, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.7 AP: /unit-x/tdmChannels/chan-t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.7.1 AP: /unit-x/tdmChannels/chan-t, Overview . . . . . . . . . . . . . . . . . . . . . . . 136
8.7.2 AP: /unit-x/tdmChannels/chan-t, Main . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.7.3 AP: /unit-x/tdmChannels/chan-t, Configuration . . . . . . . . . . . . . . . . . . . . . 136
8.7.4 AP: /unit-x/tdmChannels/chan-t, Fault Management . . . . . . . . . . . . . . . . . . 139
8.7.5 AP: /unit-x/tdmChannels/chan-t, Status. . . . . . . . . . . . . . . . . . . . . . . . . 140
8.8 AP: /unit-x/circuitEmulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.8.1 AP: /unit-x/circuitEmulation, Overview . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.8.2 AP: /unit-x/circuitEmulation, Main. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.8.3 AP: /unit-x/circuitEmulation, Fault Management . . . . . . . . . . . . . . . . . . . . 143
8.9 AP: /unit-x/circuitEmulation/cesop-z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.9.1 AP: /unit-x/circuitEmulation/cesop-z, Overview . . . . . . . . . . . . . . . . . . . . . 143
8.9.2 AP: /unit-x/circuitEmulation/cesop-z, Main . . . . . . . . . . . . . . . . . . . . . . . 143
8.9.3 AP: /unit-x/circuitEmulation/cesop-z, Configuration. . . . . . . . . . . . . . . . . . . 144
8.9.4 AP: /unit-x/circuitEmulation/cesop-z, Fault Management . . . . . . . . . . . . . . . . 150
8.9.5 AP: /unit-x/circuitEmulation/cesop-z, Status . . . . . . . . . . . . . . . . . . . . . . 152
8.10 AP: /unit-x/circuitEmulation/cesop-z/chan-c . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
8.10.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Overview . . . . . . . . . . . . . . . . . 155
8.10.2 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Main . . . . . . . . . . . . . . . . . . . 156
8.10.3 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Configuration. . . . . . . . . . . . . . . 156
8.10.4 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Fault Management . . . . . . . . . . . . 157
8.10.5 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Performance Management. . . . . . . . 158
8.10.6 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status . . . . . . . . . . . . . . . . . . 159
8.11 AP: /unit-x/vlanInterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.11.1 AP: /unit-x/vlanInterfaces, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.11.2 AP: /unit-x/vlanInterfaces, Main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.12 AP: /unit-x/vlanInterfaces/vif-z_v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.12.1 AP: /unit-x/vlanInterfaces/vif-z_v, Overview . . . . . . . . . . . . . . . . . . . . . . 160
8.12.2 AP: /unit-x/vlanInterfaces/vif-z_v, Main . . . . . . . . . . . . . . . . . . . . . . . . . 161
8.12.3 AP: /unit-x/vlanInterfaces/vif-z_v, Configuration . . . . . . . . . . . . . . . . . . . . 161
8.12.4 AP: /unit-x/vlanInterfaces/vif-z_v, Fault Management . . . . . . . . . . . . . . . . . 162
8.12.5 AP: /unit-x/vlanInterfaces/vif-z_v, Performance Management . . . . . . . . . . . . . 162
8.12.6 AP: /unit-x/vlanInterfaces/vif-z_v, Status . . . . . . . . . . . . . . . . . . . . . . . . 163
9 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

FOX61x | OPIC2
9.1 Associated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

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 IEC 62368-1 (Safety of audio/video, information and communication 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 IEC 62368-1
Voltage Current
Local power supply ES2 < 72 VDC < 0.1 A
IRIG-B/PPS output ES1 5V < 0.2 A
Table 2: Optical interfaces

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

Table 2: Optical interfaces (continued)

OPIC2 interface Parameter Range Remark
IRIG-B output, 100 bit/s, or Laser class 1M safe for all conditions of use
PPS output (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 precau-
tions for failures or laser warnings are not necessary.
3. Optical transmitted power, modulation and wavelengths are typical values for SFP modules, however
these values 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 manufactur-
ers cable, results will vary due to differing NA values and specification methods.
1.4 Document History

Table 3: Document history
Document ID FOX61x Rev. Date Changes since previous version
Release
1KHW028635 R15B P January 2022 Updated for current system release. Added condition for
TSF alarm in 8.7.4 "AP: /unit-x/tdmChannels/chan-t,
Fault Management".
1KHW028635 R15A N August 2021 - Update SFP note in section 4.3.1.
1KHW028635 R15A M June 2021 - Support of new interface type FO5.
- NPHM alarm removed.
- Support of a new SFP type.
- New OOS alarm at the cesop-z access point.
- Update copyright statement.
1KHW028635 R14A K June 2020 - Support of the unit “Overview - DDM” management
function.
- The IRIG-B outputs can be configured to use the
PPS format.
- Description of the TTI handling corrected.
1KHW028635 R3B_SP01 I January 2020 - Support of TDM transport of teleprotection sig-
nals.
1KHW028635 R3B_SP01 H December 2019 - PTP grandmaster supervision added, see section
5.7.1 Unit Synchronization (on page 52).
- New byte slip performance counters on the tele-
protection ports.
1KHW028635 R3B G September 2019 - New Holdover Timeout configuration parameter.
- Support of the packet connectivity overview fea-
ture.

Table 3: Document history (continued)

Document ID FOX61x Rev. Date Changes since previous version
Release
1KHW028635 R3A_SP01 F April 2019 - Application example added with RED670 2 Mbit/s.
1KHW028635 R3A E February 2019 - Warning note about MPLS-TP LSP protection
removed.
1KHW028635 R3A D August 2018 Minor editorial changes
1KHW028635 R2D 3 March 2018 System test performed on FOX61x release R2D.
New company branding for user manual.
1KHW028635 R2C 2 March 2017 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 R2B 1 March 2016 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, provisioning,
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
Please note:
Only instructed or skilled persons as per IEC 62368-1 may install and maintain the
system.
1.6 Definition of Terms

For an explanation of terms used in this document please refer to [1KHW028514] Information
“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.

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 teleprotection
interfaces complying to IEEE C37.94 (IEC 62843) standard, or to the proprietary transmission
protocol (ABB TPE), or to the Siemens® protection interface FO5 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 and FO5 for differential protection application over 4
optical front ports.
• OPIC2 supports various legacy interfaces for differential protection applications. The legacy
interfaces are accessed over the FOX61x internal TDM bus (PBUS). This application is only
available with packet based WAN transport, see below.
• The WAN transport channels of the OPIC2 unit are packet based or TDM based. The trans-
port mode is configurable per teleprotection port:
− In the packet based mode the OPIC2 unit implements a circuit emulation over packet
(CESoP) function and communicates 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.
To enhance the systems availability the OPIC2 unit provides redundant transmission trail
configuration and provides hitless protection switchover in case of a failure.
FOX61x
teleprot ection Core GbE Packet
TPE Unit Network
GbE star
OPIC2
TDM
PBUS
teleprot ection
Service SAMO
STM-x (EoS) TDM
TPE legacy Network
Unit
FOX61x
teleprot ection Core GbE
TPE Unit
GbE star
OPIC2
TDM
PBUS
teleprot ection STM-x (EoS)

Service SAMO
TPE legacy Unit
Figure 1: OPIC2 used as access to teleprotection equipment (TPE), packet transport

− In the TDM based mode the OPIC2 unit communicates to a P12 transport unit, e.g. a
SAMOx unit, via the PBUS.
The teleprotection signals accessed by the OPIC2 unit are transported via a high speed
TDM network, e.g. the teleprotection signals are transported over SDH.
To enhance the systems availability the OPIC2 unit provides 1+1 end to end nx64 kbit/s
linear trail protection with symmetrical bi-directional switching.
FOX61x
PBUS
teleprot ection STM-x TDM
TPE OPIC2 SAMO
Network
FOX61x
PBUS
teleprot ection STM-x
TPE OPIC2 SAMO
Figure 2: OPIC2 used as access to teleprotection equipment (TPE), TDM transport
Please note:
When using a TPE port of the OPIC2 in the packet transport mode the TDM trans-
port mode is disabled:
→ No data from the TPE optical port can be transported to a P12 transport unit via
the PBUS
→ The TDM part can be preconfigured, including the required cross connection, to
allow a fast switch-over from the packet transport mode to the TDM transport
mode.
Please note:
When using a TPE port of the OPIC2 in the TDM transport mode the packet trans-
→ No data from the TPE optical port can be transported with a CESoP function.
→ No legacy data from the PBUS can be transported with a CESoP function.
→ The CESoP function can be preconfigured and activated to allow a fast switch-
over from the TDM transport mode to the packet transport mode.
The OPIC2 unit accesses the PBUS (FOX61x internal TDM bus) with
• P0_nc (1 … 12 x 64 kbit/s) signals, or
• P12 (2048 kbit/s) signals (not applicable for the TDM based transport mode).

2.2 Unit View
Figure 3: OPIC2 unit view
Figure 3 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 or PPS outputs.

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
- Performance Monitoring - ABB TPE
Front Connectors
4
- ARP handling (MAC discovery) - FO5
IRIG-B/PPS
5
Output
optical
Host processor Date and Time Processing
Backplane access
IRIG-B/PPS
6
Outputs
Subrack internal electrical
communication
Power
Figure 4: OPIC2 block diagram
Figure 4 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 inter-
faces can individually be configured as IEEE C37.94 interfaces or as ABB TPE interfaces or
as FO5 interfaces (port-1 and port-2 only). Each interface can be connected to a circuit emu-
lation circuit for packet transport, or to a P0_nc channel for TDM transport.
• 4 PBUS interfaces accessing the PBUS on the backplane for nx64 kbit/s or 2048 kbit/s leg-
acy applications, or for nx64 kbit/s TDM transport of TPE interface signals.
• IRIG-B or PPS output interfaces to synchronize user equipment in the substation.
• 4 Circuit Emulation Service (CES) instances for asynchronous network access of synchro-
nous user data.
• Redundant core unit interface for protection.
• Unit synchronization and supervision to provide accurate timestamps to CES and IRIG-B or
PPS, and to detect core unit failure conditions.

FOX61x | OPIC2 FUNCTIONS AND SPECIFICATIONS
3 Functions and Specifications

The OPIC2 unit provides the following functions and conforms to the corresponding standards
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)
2x optical teleprotection interfaces compatible to the Sie- r15a
mens® FO5 protection interface.
Circuit emulation service (CES) 4 proprietary circuit emulation units 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
- Legacy teleprotection signal modes nx64 kbit/s, n = 1 … 32 (terminated internal channel) r1b
2048 kbit/s (transparent internal channel) r1c
- TDM transport modes nx64 kbit/s, n = 1 … 13 (working and protecting) r1f
- Cross connections Flexible cross connections to any other FOX61x TDM unit on the
- P0_nc layer
- P12 layer r1b
r1c
Optical IRIG-B or PPS output One optical IRIG-B output: r1b
- Connector type: ST
- Wave length range: 792 … 865 nm
- Center wave length: 820 nm
Alternatively the IRIG-B output can be used as PPS output: r2a
- Optical specification: as IRIG-B
- Rising edge: start of a second
- Pulse width: 3 ms typical
- Accuracy: -50 ns … +50 ns relative to the PETS timing
Electrical IRIG-B or PPS 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
Alternatively the IRIG-B outputs can be used as PPS outputs: r2a
- Electrical specification: as IRIG-B
- Rising edge: the start of a second
- Pulse width: 3 ms typical
Maintenance functions
- Loops on the CES layer (applicable - Loop 2b: Remote loop, back-to-back r1b
for the packet transport mode) - Loop 2b: Local loop, back-to-back
- Loop 3b: Local loop, front-to-front

Table 5: Functions and specifications (continued)

Feature Rating or standard Release
- Loops on the port layer (applicable - Loop 2b: Remote loop, back-to-back r1f
for the TDM transport mode) - Loop 2b: Local loop, back-to-back
- Loop 3b: Local loop, front-to-front
- TDM delay threshold supervision - Configurable safety margin for TDM delay supervision r1c
- Individual per CESoP instance
Protection, packet transport mode
- Hitless protection Hitless protection for each CESoP instance r1b
- Switching time Hitless protection r1b
Protection, TDM transport mode
- Linear trail protection - 1+1 bi-directional symmetrical, revertive r1f
- 1+1 bi-directional symmetrical, non revertive
- Switching time < 25 ms r1f
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
Table 6: Mechanical and environmental features

Feature Rating or standard
Power consumption 1
- Power supply range VBAT -39.5 VDC … -72 VDC
- Maximum total power requirement 8.5 W
from battery, PTOT (VBAT = nominal
voltage)
Mechanical parameters
- Construction practice 19 inch
- Height of unit (1 HU = 44.45 mm) 6 HU
- Width of unit (1 TE = 5.08 mm) 4 TE (1 slot)
- Size of the PCB (H x D) 233 mm x 220 mm
- Weight 400 g
- RoHS Directive 2011/65/EU of the European Parliament and of the Council of 8
June 2011 on the Restriction of the use of certain hazardous substances
in electrical and electronic equipment
- WEEE Directive 2012/19/EU of the European Parliament and of the Council of
4 July 2012 on waste electrical and electronic equipment
Reliability
- Calculated MTTF at 35 °C 100 years
(MIL-HDBK-217F) (SFPs are not considered)
Emission refer to [1KHW002460] System Description “FOX61x”
Immunity refer to [1KHW002460] System Description “FOX61x”
Safety refer to [1KHW002460] System Description “FOX61x”
SFP modules:
according to the manufacturer’s data sheets (typically IEC 60825-1 Class
1 laser product)

Table 6: Mechanical and environmental features (continued)

Feature Rating or standard
Ambient conditions refer to [1KHW002460] System Description “FOX61x”
Error free operation up to 65°C ambient temperature is only guaranteed
with SFP modules specified for the industrial temperature range (up to
85°C).
Operation above 60°C requires optimization of the air flow around units
that are equipped with SFPs. Please refer to [1KHW029122] Application Note
“Extended Temperature Range Operation”.
1. The given power consumption figures are without SFP modules. The power consumption of an SFP module is around
1 W. Please refer to the SFP modules data sheet for the exact power consumption value.

FOX61x | OPIC2 INSTALLATION
4 Installation
4.1 Prerequisites
Before installing a 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 R2 and FOX615 Installation”, or
• refer to [1KHW002462] Installation Instruction “FOX612 Installation”, or
• refer to [1KHW029142] Installation Instruction “FOX611 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 R2 and FOX615: 1 … 10, 12, 14 … 21
• FOX612: 7 … 10, 12, 14
• FOX611: 9 … 10, 12
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 requirements 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 Agree-
ment (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)
− 1KHW022740P0001: IEEE C37.94 optical port (1310nm, single mode, up to 20 km)
− 1KHW001872R0001: ABB TPE optical port (1310 nm, single mode, up to 30 km)
• 2 Mbit/s … 128 kbit/s interface SFP module
− 1KHW003878R0001: IEEE C37.94 or FO5 optical port (850 nm, multi mode, up to 2 km)

The 1KHW003878R0001 SFP module is only operable at an ambient temperature
above 0° C.

Please note:
Only SFP modules recommended by Hitachi Energy can guarantee the specified
functionality of the OPIC2 unit.
→ In order to get the latest list of Hitachi Energy recommended SFP modules
please contact your local Hitachi Energy 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-stan-
dardized, methods to release this locking mechanism:
• with a bail (generally used on optical SFP modules), or
• 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 5: 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 con-
nected.
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 unlocking
actuator is on the left 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
with unlocking actuator
push
install remove
Tx Tx
Rx Rx
Figure 6: SFP module handling
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 transmitter,
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,
• IEEE C37.94 interfaces with 2 Mbit/s interface SFP modules 1KHW022740P0001.
• IEEE C37.94 or FO5 interfaces with 2 Mbit/s … 128 kbit/s interface SFP modules
1KHW003878R0001.
4.4 Interoperability and Compatibility
4.4.1 FOX61x System Releases

The OPIC2 unit using the TDM transport mode can be operated in all deployed FOX61x system
releases.
The OPIC2 unit using the packet transport mode can be operated in all deployed FOX61x sys-
tem releases except the R1 system releases.
4.4.2 FOX61x Teleprotection Units

Using the TDM transport mode with nx64 kbit/s (P0_nc) signals the OPIC2 IEEE C37.94 inter-
faces and ABB TPE interfaces can inter-operate with OPIC1.

The OPIC2 interfaces using the TDM transport mode do not support the transparent 2048 kbit/s
(P12) signals as does the OPIC1 unit. The OPIC2 and OPIC1 units cannot inter-operate in the
transparent TDM transport mode.
Using the packet transport mode the OPIC2 IEEE C37.94 interfaces and ABB TPE interfaces
cannot inter-operate with OPIC1.
4.4.3 FOX51x Teleprotection Units

Using the TDM transport mode the OPIC2 IEEE C37.94 interfaces and ABB TPE interfaces can
inter-operate with OPTIF.

The FOX51x service unit OPTIF uses the “SPACE” character to fill up a not com-
pletely defined PI (Path Identifier).
→ To be inter-operable with the OPTIF unit you have to fill up the transmitted and
expected TTI values in the OPIC2 unit with “SPACE” characters.
Using the packet transport mode the OPIC2 IEEE C37.94 interfaces and ABB TPE interfaces
cannot inter-operate with OPTIF.
4.4.4 Previous ESW Revisions

The OPIC2 unit with the ESW release opic2_r15b is compatible to the previous ESW release.
When upgrading to the ESW release opic2_r15b all configuration parameters are inherited from
an existing configuration. New parameters get their default values.
For the compatibility information with the FOX61x system releases please refer to
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 or PPS output and six galvanic isolated IRIG-B or PPS outputs
with common ground.

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 7: OPIC2 front panel and interface connectors
Table 7: OPIC2 port-6 front connector pins

IRIG-B or PPS signal Connector pin for
signal + signal -
IRIG-B1 or PPS1 A1 C1
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 termination
required.
Duplex ST connector Duplex LC connector
Figure 8: 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 standard con-
nectors (e.g. RED670), placed outside the communication cabinet.
The same cable type can be used for the direct connection of OPIC2 FO5 SFP
interfaces with a corresponding TPE.
Dual FC-PC connector Duplex LC connector
Figure 9: 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 connec-
tors on single mode fibers, placed inside or outside the same communication cabi-
net (e.g. REL316).
Duplex LC connector Duplex LC connector
Figure 10: 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
Please note:
These cable types are indicated for the direct connection of OPIC2 SFP interfaces
with a corresponding TPE also providing SFP interfaces, placed inside the same
communication cabinet or outside (e.g. NSD570 with G1LOa interface).

Please note:
The above cables can be ordered directly from Hitachi Energy.
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 or PPS Output Cable V9PT

The optical IRIG-B or PPS cable connects to the IRIG-B or PPS output port-5 of the OPIC2 unit.
CAUTION
LASER
1M
Figure 11: Class 1M laser
Please note:
As a Class 1M laser product, the IRIG-B or PPS output is considered non-hazard-
ous. Hazard increases if viewed with optical aids including magnifiers, binoculars,
or telescopes.
The optical IRIG-B or PPS cable requires a standard simplex ST connector and can be termi-
nated with a simplex LC, ST, FC/PC or E2000 connector on the other end, depending on the
termination required.
ST connector ST connector
Figure 12: 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 decimeters
(R0010 corresponds to a 1 meter cable).
4.5.4 Electrical IRIG-B or PPS Output Cable V9IR

The Electrical IRIG-B or PPS output cable V9IR interfaces six galvanically isolated Electrical
IRIG-B or PPS outputs to the OPIC2 unit. The cable is available in 3 m and 20 m length. The
cable is available 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 R2 or FOX615, or the cor-
responding device of the FOX612 or FOX611.
Figure 13 shows the cable/cable tray assembly of the FOX615 R2 and FOX615. For additional
information refer to [1KHW002461] Installation Instruction “FOX615 R2 and FOX615 Installa-
tion”.
When operating the OPIC2 unit in a FOX615 R2 or FOX615, the cables must be attached to the
cable tray as shown in Figure 13.

<x> mm
Figure 13: Side view of the cable tray and the cables in FOX615 R2 and FOX615
The open cable length <x> between the cable fixing point on the cable tray and the connector
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 fix-
ing 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 or FOX611 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 or FOX611 refer to [1KHW002462] Installation Instruction “FOX612 Installation” or
refer to [1KHW029142] Installation Instruction “FOX611 Installation”.

FOX61x | OPIC2 FUNCTIONAL DESCRIPTION
5 Functional Description
This section gives the detailed functional description of the OPIC2 unit as teleprotection applica-
tion unit in the FOX61x subrack.
5.1 Introduction
5.1.1 Packet Based Teleprotection Signal Transport

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 transmission protocol
(ABB TPE) on every unit. Two of the interfaces support in addition the FO5 protection interface
type.
OPIC2 has also an access of 4x2 Mbit/s towards the FOX61x internal cross connection back-
plane (PBUS) allowing for full 2 Mbit/s user access per circuit emulation service channel. On the
P0_nc layer the OPIC2 unit supports applications with 1x64 … 32x64 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 backplane 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 trans-
port 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 handling
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.
5.1.2 TDM Based Teleprotection Signal Transport

The PBUS access can alternatively be used for the transport of the teleprotection signals via the
TDM network. On the P0_nc layer the OPIC2 unit supports applications with 1x64 … 13x64 kbit/
s. The optical and electrical TDM user data are directly mapped to/from a TDM channel for
transport in a TDM network. The access to the TDM network can be done using any of the P12
transport units of the FOX61x, e.g. LEDE1, DATI1 or SAMOx.
The OPIC2 TDM transport mode offers an optional PM (Performance Monitoring) time slot
which can be added to the nx64 kbit/s data stream for monitoring end to end performance and
for bidirectional symmetrical 1+1 linear trail protection.

5.1.3 Synchronization and IRIG-B or PPS Timing

In OPIC2, configurable electrical and optical IRIG-B outputs complying to the B002/B006 fram-
ing are available on the front plate. Alternatively the IRIG-B outputs can be configured to use the
PPS format.
OPIC2 CESoP and IRIG-B/PPS output generation only work when the unit is Time-of-Day syn-
chronized to a grandmaster clock over PTP. The involved CESoP instances must use the same
grandmaster clock or two grandmaster clocks which are both synchronized to GPS. Accord-
ingly, OPIC2 has a built-in unit synchronization 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/PPS generation
• provide any synchronization failure to CESoP and IRIG-B/PPS generation in order to stop
the service
• provide any core unit failure to CESoP in order to switch between redundant core units
5.1.4 Applications and Functions Overview

The following diagram summarizes all the applications and functionalities to support these appli-
cations and their section/clause numbers:
IEEE C37.94 ABB TPE

section 5.3.1 section 5.3.1 nx64 kbit/s 2048 kbit/s IRIG-B/PPS
Applications section 5.4.1
section 5.4.1 section 5.3.2 section 5.3.3 section 5.7.2
Optical TPE PBUS IRIG-B/PPS

Interfaces Interface Interface Interface
section 5.2.1 section 5.2.2 section 5.2.3
TDM Circuit Emulation Unit Synchronization IRIG-B/PPS

Functions Transport Service and Supervision Generation
section 5.6 section 5.5.1 section 5.7.1 section 5.7.2
PMTS Protection Authentication Protection Performance ARP Handling

section 5.6.1 section 5.6.3 section 5.5.1.1 section 5.5.1.2 Monitoring (MAC Discovery)
section 5.5.1.3 section 5.5.1.4
WAN Core Unit

Redundancy Redundancy
section 5.5.1.2.1 section 5.5.1.2.2
Figure 14: Supported applications and functions of OPIC2
5.2 Interfaces
The OPIC2 unit provides the following user interfaces for the applications specified in Figure 14:
• Optical TPE interface
• PBUS interface

• IRIG-B or PPS output interface
5.2.1 Optical Teleprotection Equipment (TPE) Interface

The optical TPE interface of the OPIC2 unit 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 WAN transport instances to further transport/receive decoded
user data to/from the WAN. A WAN transport instance can be a circuit emulation service (CES)
or a TDM transport. The WAN transport mode can be configured for each port individually. See
Figure 15 for a visual representation of the optical TPE interface in OPIC2.
OPIC2
FOX61x
Protection IEEE C37.94

port-4 Et hernet
Relay ABB TPE
GbE star
Circuit Emulation WAN interface
Core Unit
Service
port-3
Relay ABB TPE

port-2 TDM
Relay ABB TPE/ FO5 P12
P0_nc WAN interface
Transport
terminated
PBUS
Protection IEEE C37.94 Unit
port-1
Relay ABB TPE/ FO5
AP: /unit-x/port-y
Figure 15: Optical user interface with packet based and TDM based transport
The 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 sec-
tion section 8.3.3 AP: /unit-x/port-y, Configuration (on page 126).
The optical TPE interface supports decoding/encoding of the following three types of optical pro-
tocols which can carry teleprotection data:
• IEEE C37.94 (see section 5.8 IEEE C37.94 Protocol (on page 53)).
• FOX6plus compatible ABB TPE (see section 5.9 FOX6plus Frame Compatible Hitachi
Energy Teleprotection Equipment Protocol (on page 55)).
• FO5 (see section 5.10 FO5 Protection Interface (on page 57)).
Please note:
The 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. The interfaces of
port-1 and port-2 can alternatively be configured to the FO5 type. Please check
section 8.3.3.1 AP: /unit-x/port-y, Configuration - Interface (on page 126) 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 setting depends on
the interface type.
As described in section 5.8 IEEE C37.94 Protocol (on page 53), the IEEE C37.94 standard
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 tele-
protection data with one additional remote alarm channel can be transported. The FO5 interface
type can be configured with 2 or 8 channels.

Please note:
ABB TPE interface can also transport remote alarm information in case it is
needed. It is automatically extracted from the ABB TPE frames and only inserted in
the data to be transported in the WAN if the configuration parameter “Number of
Protection Channels” is set to 2. Otherwise, when it is set to 1, only the teleprotec-
tion data will be transported without remote alarm information.
See section 8.3.3.1 AP: /unit-x/port-y, Configuration - Interface (on page 126) for a summary 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 or FO5). However, depending on the equip-
ment’s frame transmission alignment synchronization scheme, hazardous synchronization loops
can occur if the equipment tries to align its transmitted frame start position 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, Configuration - Interoperability (on page 127) to see
where to set/clear it in FOXCST.
Please note:
When “FSP Loop Prevention Enabled” is set, reliable operation is guaranteed with-
out any frame alignment synchronization loops, however, end-to-end transmission
delay accuracy can be degraded up to 125 µs in this case.
5.2.1.1 Synchronization
In the connection to a TPE, OPIC2 always acts as a clock master.
In receive direction, the user data rate is derived from the network element timing.
In transmit direction, OPIC2 expects that the incoming user signal at the TPE interface is syn-
chronous to the network element timing (PETS). This requires that the network element timing is
looped in the TPE.
If the incoming user signal is not synchronous to the network element timing, bit slips, byte slips
or frame slips will occur and the data transmission is therefore disturbed.
Transmit data signal

TPE OPIC2
loop
timing Receive data signal
Figure 16: TPE looped timing
5.2.1.2 Communication Failure Scenarios

The OPIC2 optical user interface has a fault management system which detects the communi-
cation failures on the optical communication with the attached teleprotection devices. Accord-
ingly, OPIC2 informs the user via FOXCST with the following alarms:
• Degraded Signal (DEG) - not for FO5
• 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) - not for FO5
• TPE Loss Of Frame Alignment (TLOFA) - only for ABB TPE
• TPE Loss Of Synchronization (TLOS) - not for FO5
• 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 128).
Please note:
Depending on the optical interface type (IEEE C37.94 or ABB TPE or FO5), avail-
able alarms can differ (e.g. DRM only for IEEE C37.94) and the trigger conditions
for the alarms can also be different. Please refer to section 8.3.4 AP: /unit-x/port-y,
Fault Management (on page 128) 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 failure conditions.
5.2.2 PBUS Interface

The PBUS interface of the OPIC2 unit can be used for the packet transport of legacy differential
protection applications. Alternatively the PBUS interface can be used for the TDM transport of
optical TPE interface data.
5.2.2.1 PBUS Usage with Packet Transport

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. The PBUS access is shared with the access of
optical TPE interface data using TDM transport.
OPIC2s 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 encapsulated and
transported by CES
• Acting locally as a TDM service start point for the TDM traffic that is decapsulated and trans-
ported 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 chan-1 cesop-4 vif-4_1
Relay
Protection E0 Codir G.703

LECO1 chan-1 cesop-3 vif-3_1 Ethernet
Relay
GbE Core WAN interf ace
access Unit
GbE star
Protection E1 G.703
LEDE1 chan-1 cesop-2 vif-2_1
Relay
PBUS
Protection V.11 - X.24
LEDS1 chan-1 cesop-1 vif-1_1
Relay
AP: /unit-x/circuitEmulation/cesop-z
AP: /unit-x/circuitEmulation/cesop-z/chan-c AP: /unit-x/vlanInterfaces/vif-z_v
Figure 17: PBUS interface with packet transport
Communication through the PBUS is channel based and the user has to create channels for
each application separately. Please check section 8.9.3.5 AP: /unit-x/circuitEmulation/cesop-z,
Configuration – Channels (on page 147) 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 have to be created. Please refer to
[1KHW002467] User Manual “TDM Services” to see how to create cross connec-
tions.
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 corre-
sponding 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 provides
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.2.2.2 PBUS Usage with TDM Transport

OPIC2 provides a PBUS access at P0_nc line rate in order to transport nx64 kbit/s (n = … 13)
optical TPE interface data through a TDM network.
OPIC2 has access to one physical PBUS line providing an overall bandwidth of 4x 2Mbit/s to
the user. The PBUS access is shared with the access of legacy user data using packet trans-
port.

OPIC2s PBUS interface acts as a bridge between the optical TPE port and a P12 transport unit,
e.g. LEDE1, SAMOx. The PBUS interface acts locally as a TDM service termination point for the
TDM traffic that is transported via a TDM network.
OPIC2 FOX61x

port-4 chan-4
Relay ABB TPE
PMTS
port-3 chan-3 TDM
Relay ABB TPE P12 WAN interf ace
PBUS
PMTS Transport
Protection IEEE C37.94 Unit
port-2 chan-2
Relay ABB TPE / FO5
PMTS
port-1 chan-1
Relay ABB TPE / FO5
PMTS
AP: /unit-x/port-y AP: /unit-x/tdmChannels/chan-t
Figure 18: PBUS interface with TDM transport
Communication through the PBUS is channel based. The OPIC2 management interface pro-
vides 4 predefined channels, see section 8.7 AP: /unit-x/tdmChannels/chan-t (on page 136).
Each channel supports up to 12 timeslots of user data plus 1 optional timeslot for performance
management data that can be received/sent from/to PBUS at P0_nc line rate. The number of
timeslots used is automatically set considering the number of configured protection channels
(see section 8.3.3.1 AP: /unit-x/port-y, Configuration - Interface (on page 126)), and if the perfor-
mance management timeslot is used (see section 8.7.3.2 AP: /unit-x/tdmChannels/chan-t, Con-
figuration – Transport (on page 137)).
Please note:
For a successful communication through the PBUS between service units and
OPIC2, cross connections between channels have to be created. Please refer to
[1KHW002467] User Manual “TDM Services” to see how to create cross connec-
tions.
For more information regarding the PBUS access, please refer to [1KHW002467] User Manual
“TDM Services”.
5.2.3 IRIG-B or PPS Output Interface

The IRIG-B subsystem in the OPIC2 unit provides OPIC2 front interfaces with 7 IRIG-B outputs:
• 1 optical output via a ST connector (port 5):
The transmitter of the OPIC2 unit supports multi-mode transmission at 820 nm.
• 6 electrical outputs via a 24-pin connector (port 6):
All the IRIG-B outputs are galvanically isolated from all other electrical circuits on the OPIC2
unit.
Alternatively the IRIG-B outputs can be configured to use the PPS format.

AP: /unit-x/port-6
FOX61x
IRIG-B 002/006 OPIC2
or PPS
Devices with electrical 6x elect rical
port-6
IRIG-B/PPS input IRIG-B/PPS Unit
IRIG-B 002/006 IRIG-B/PPS
or PPS output synchronization
generation
Device with optical IRIG- 1x optical (ST) interface and supervision
port-5
B/PPS input
AP: /unit-x/port-5
Figure 19: IRIG-B output interface
At both ports, the time format is configurable between IRIG-B002, IRIG-B006 and PPS. Please
refer to section 8.4 AP: /unit-x/port-5: IRIG-B (IRIG-B opt.) (on page 133) and section 8.5 AP: /
unit-x/port-6: IRIG-B (IRIG-B el.) (on page 134) to see how these interfaces can be configured
via FOXCST.
See section 5.7.2 IRIG-B and PPS Generation (on page 53) for functional details of the IRIG-B
or PPS generation.
The IRIG-B protocol is described in section 5.11 IRIG-B Protocol (on page 57).
5.3 Applications with Packet Transport

Please note:
When using a TPE port of the OPIC2 in the packet transport mode the TDM trans-
→ No data from the TPE optical port can be transported to a P12 transport unit via
the PBUS.
5.3.1 Teleprotection Application
5.3.1.1 Packet Transport via Core Unit

Teleprotection signals of a protection relay connected to a OPIC2 unit can be transported over a
packet network, e.g. a MPLS-TP network, via the core unit.
The interface mode of the OPIC2 teleprotection port has to be configured to “Packet”. The termi-
nation mode of the OPIC2 CESoP instance has to be configured to “Terminated Optical Port”.
The TDM signal of the protection relay is mapped/demapped to/from a circuit emulation service.
The circuit emulation service uses one VLAN (without WAN redundancy) or two VLANs (with
WAN redundancy) that are transported over the packet network, refer to section 5.5.1.2.1 Hit-
less WAN Redundancy (on page 41).
The VLAN(s) are connected to the FOX61x Switch on the core unit and transported over the
MPLS-TP network using a VPWS service.
Please check Figure 20 to see the use case of OPIC2 with teleprotection signal packet transport
over a packet network.

FOX61x
Protection IEEE C37.94 OPIC2 Core GbE

Relay ABB TPE / FO5 Unit
GbE star
MPLS-TP
Network
FOX61x
Protection IEEE C37.94 Core GbE

OPIC2
GbE star
Figure 20: OPIC2 use case for teleprotection signal packet transport via core unit
The OPIC2 can serve four circuit emulation services.
5.3.1.2 Packet Transport via SDH Service Unit (EoS)

TDM network, e.g. a SDH network, via the core unit and a SDH service unit.
The interface mode of the OPIC2 teleprotection port has to be configured to “Packet”. The termi-
nation mode of the OPIC2 CESoP instance has to be configured to “Terminated Optical Port”.

The operation of a OPIC2 CESoP instance requires the synchronization of the
FOX61x network element to a timing source providing phase information.
→ Because SDH is not able to correctly transmit PTP time information, a local time
source (e.g. GPS) or the packet network must be used for PTP transmission.
The TDM signal of the protection relay is mapped/demapped to/from a circuit emulation service.
The circuit emulation service uses one VLAN (without WAN redundancy) or two VLANs (with
WAN redundancy) that are transported over the packet network, refer to section 5.5.1.2.1 Hit-
less WAN Redundancy (on page 41).
The VLAN(s) are connected to the FOX61x Switch on the core unit. The VLAN(s) are forwarded
via the GbE star to the SDH service unit and transported over a SDH network using an EoS
channel.
Please check Figure 21 to see the use case of OPIC2 with teleprotection signal packet transport
over a TDM network.

FOX61x
Protection IEEE C37.94 OPIC2 Core

GbE star
SDH STM-x (EoS)
Service
Unit
FOX61x TDM
Network
OPIC2
Protection IEEE C37.94 Core
GbE star
SDH STM-x (EoS)
Service
Unit
Figure 21: OPIC2 use case for teleprotection signal packet transport via SDH service unit
The OPIC2 can serve four circuit emulation services.
5.3.2 P0_nc (nx64 kbit/s) Application via Core Unit

OPIC2 supports nx64 kbit/s applications via cross connections created on the PBUS between
OPIC2 and other TDM service units such as LECO1, LEDS1, LEDA1 and LEDE1.
The termination mode of the OPIC2 CESoP instance has to be configured to “Terminated Inter-
nal Port”. A channel has to be created on the OPIC2 CESoP instance for each service con-
nected via the PBUS.
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 possible
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 22 to see the use cases of OPIC2 with nx64 kbit/s legacy applications.

FOX61x
Protection 2/4 wire
Relay LEDA1
P0_nc
Relay LECO1
GbE
OPIC2 Core
Unit
GbE star
Protection E1 G.703
LEDE1
Relay
PBUS
LEDS1
Relay
MPLS-TP
Network
FOX61x
Protection 2/4 wire
LEDA1
Relay
P0_nc
LECO1
Relay
OPIC2 Core GbE
Unit
GbE star
Protection E1 G.703
LEDE1
Relay
PBUS

LEDS1
Relay
Figure 22: OPIC2 use cases for nx64 kbit/s applications
The OPIC2 can serve four circuit emulation services with up to 1 to 32 channels on each ser-
vice. A channel provides the nx64 kbit/s application using its P0_nc line rate.
Please note:
The packet transport can alternatively also be done via an SDH service unit using
the EoS protocol.
Please note:
For further information on the framing and timing in the PBUS please refer to
Please note:
For further information on the supported service units by OPIC2 for TDM communi-
cation, 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!
5.3.3 P12 (2048 kbit/s) Application via Core Unit

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.

The termination mode of the OPIC2 CESoP instance has to be configured to “Transparent Inter-
nal Port”. A channel has to be created on the OPIC2 CESoP instance for the service connected
via the PBUS.
In order to access the PBUS, following application are possible for teleprotection operation by
E1 relays:
• E1 channel with LEDE1 at P12 line rate (2 Mbit/s)
Please check Figure 23 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 star
PBUS
MPLS-TP
Network
FOX61x
P12
Protection E1 G.703
LEDE1 OPIC2 Core GbE
Relay Unit
GbE star
PBUS
Figure 23: OPIC2 use case for P12 application
The OPIC2 can serve four circuit emulation services with 1 channel on each service. A channel
provides the 2048 kbit/s application using its P12 line rate.
Please note:
The packet transport can alternatively also be done via an SDH service unit using
the EoS protocol.
Please note:
For further information on the framing and timing in the PBUS please refer to
Please note:
For further information on the supported service unit by OPIC2 for TDM communi-
cation, please refer to [1KHW002473] User Manual “LEDE1”.

LEDE1 and OPIC2 must be plugged into the same subrack!
5.4 Applications with TDM Transport

Please note:
When using a TPE port of the OPIC2 in the TDM transport mode the packet trans-
→ No data from the TPE optical port can be transported with a CESoP function.
→ No legacy data from the PBUS can be transported with a CESoP function.
5.4.1 Teleprotection Application

TDM network, e.g. a SDH network, via a SDH service unit.

The interface mode of the OPIC2 teleprotection port has to be configured to “TDM”. The chan-
nel used for this application is predefined at the AP: /unit-x/tdmChannels/chan-t.
The TDM signal of the protection relay with n time slots is mapped directly to a TDM channel
with n time slots, i.e. without any bit rate adaptation. This channel is cross connected to another
TDM channel on the P12 transport unit.
Please note:
If the TDM transport mode is used, the FOX61x network element does not have to
be synchronized to a timing source providing phase information.
Please check Figure 24 to see the use case of OPIC2 with teleprotection signal TDM transport
over a TDM network.
FOX61x
SDH
OPIC2
STM-x (P12)
Service
Relay ABB TPE / FO5
PBUS
Unit
TDM
Network
FOX61x
SDH
OPIC2
STM-x (P12)
Service
Relay
PBUS
ABB TPE / FO5

Unit
Figure 24: OPIC2 use case for teleprotection signal TDM transport via SDH service unit
The OPIC2 can serve four TDM channel services.

The parameter n can be in the range 1 to 12 for IEEE C37.94 interfaces, or 1 to 2 for ABB TPE
interfaces, or 2 or 8 for FO5 interfaces.
If required, the PM time slot is added to the nx64 kbit/s TDM connection point (not for FO5). The
P0_nc signal with n(+1)x64 kbit/s is mapped and demapped to and from the PBUS.
Please note:
The number of required timeslots in the TDM channel is automatically configured.
from TPE Data stream
interface 2048 kbit/ s
Data bits from data n time slots
FIFO stream mapped to n
2048 kbit/s timeslots
PBUS, backplane
transmit
PETS timing
2048 kHz
n time slots
to TPE Data stream working
n timeslots demapped
interface 2048 kbit/ s
to data bits of data protecting
2048 kbit/s stream
receive
PETS timing
2048 kHz
Figure 25: PBUS access with terminated nx64 kbit/s signals
The “n timeslots demapped to data bits of data stream” block performs also the signal connec-
tions for the 1+1 linear trail protection application. Refer also to section 5.6.3 Bidirectional Sym-
metrical Linear Trail Protection (on page 50).

from TPE working

interface
protecting
PBUS, backplane
signaling bits signaling bits
working protecting
defect monitoring monitoring

evaluation working protecting
to TPE working
interface
protecting
Figure 26: 1+1 linear trail protection connection
5.5 Functions for Packet Based Transport
5.5.1 Circuit Emulation Service (CES)

Circuit emulation service is a telecommunication technology which enables to transport synchro-
nous data over asynchronous networks (e.g. Ethernet). OPIC2 hosts up to four independent
CES units which are connected in a fixed manner to either the corresponding IEEE C37.94 front
port or the internal PBUS 2Mbit/s line.

The operation of a OPIC2 CESoP instance requires the synchronization of the
FOX61x network element to a timing source providing phase information.
→ Because SDH is not able to correctly transmit PTP time information, a local time
source (e.g. GPS) or the packet network must be used for PTP transmission.
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 datagrams into
Ethernet packets in the WAN direction and which decapsulates the Ethernet packets into user
datagrams towards the attached protection device. See Figure 27 for a visual representation.
OPIC2 FOX61x
2/4 wire 4
Protection Relay LEDA1 Circuit
Emulation
E0 Codir G.703
LECO1 PBUS 3 Service
Protection Relay
(internal)
E1 G.703 interface 2
Protection Relay LEDE1 cesop-4
GbE star
PBUS
Source switch
V.11 - X.24 1
LEDS1
Scheduler
Protection Relay cesop-3

Core GbE
IEEE C37.94 4 Unit
Protection Relay ABB TPE
port-4 cesop-2
IEEE C37.94 3
Protection Relay ABB TPE
port-3 Optical cesop-1
user
IEEE C37.94 2
Protection Relay port-2 interface
ABB TPE/ FO5
IEEE C37.94 1
Protection Relay ABB TPE/ FO5
port-1
source select (1 … 4)
Figure 27: Circuit Emulation Service
OPIC2’s CES implementation is based on an Hitachi Energy innovative solution which compen-
sates 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.7.1 Unit Synchronization
(on page 52) for more details on the OPIC2 unit synchronization)
OPIC2 includes four independent instances of CES each of which can be independent config-
ured as shown in section 8.8 AP: /unit-x/circuitEmulation (on page 142).
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.9.3.1 AP: /
unit-x/circuitEmulation/cesop-z, Configuration – General (on page 144).
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 proportional to the
number of TDM frames encapsulated in one Ethernet frame. OPIC2 offers four different configu-
ration options (1, 2, 4 and 8) corresponding to the number of TDM frames per Ethernet frame.
See section 8.9.3.3 AP: /unit-x/circuitEmulation/cesop-z, Configuration – CESoP (on page 146)
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.2.1 Optical Telepro-
tection Equipment (TPE) Interface (on page 27) and section 5.2.2 PBUS Interface (on page 29),
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 car-
ried by the created and cross connected PBUS channels.
Table 8 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 8: 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.656 … 4.864
IEEE C37.94 or
FO5 or
PBUS
FO5 8 1, 2, 4 or 8 0.125 … 1 8 … 64 1.040 … 4.736
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/Chan-
nels” and the same “Number of TDM frames per Ethernet packet”. Otherwise 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. Depending on
the lack of network resources and huge buffering delays in WAN, OPIC2 packets can experi-
ence 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 communicating 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.9.3.3 AP: /unit-x/cir-
cuitEmulation/cesop-z, Configuration – CESoP (on page 146).
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 following sub-
sections:
• Authentication
• Protection
• Performance monitoring
• MAC address discovery
• Trail Supervision
5.5.1.1 Authentication
For teleprotection applications, message integrity is very crucial in terms of cyber security. Mali-
cious 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 com-
municating 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 configurable.
As a minimum requirement, the user has to enter a key consisting of at least 6 characters which
have at least 1 capital letter, 1 symbol and 1 number. Please check section 8.9.3.1 AP: /unit-x/
circuitEmulation/cesop-z, Configuration – General (on page 144) to see how to configure the
authentication keys.
Please note:
In order to achieve the highest possible level of security, the user is recommended
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.5.1.2 Protection
Data reliability and availability are two of the main concerns of teleprotection applications.
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.5.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 communica-
tion even during a link failure in one of the MPLS-TP pseudo-wires.
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.12.3.1 AP: /unit-x/vlanInterfaces/
vif-z_v, Configuration – General (on page 161).
OPIC2
FOX61x
Circuit Emulation Service
vif-1_1
cesop-1 VLAN to MPLS mapping
GbE star
vif-1_2
VLAN PW
vif-2_1
cesop-2 vif-1_1 working 1
Scheduler
vif-2_2 vif-1_2 working 2

cesop-3 vif-3_2 vif-2_2 working 2
vif-3_1 working 1
vif-4_2 working 2
MPLS-TP Network
WAN protection
(Pat h 1 pseudo wires)
OPIC2
FOX61x
MPLS-TP Network
(Path 2 pseudo wires)
Circuit Emulation Service
vif-1_1
cesop-1 VLAN to MPLS mapping
GbE star
vif-1_2
VLAN PW
vif-2_1
cesop-2 vif-1_1 working 1
Scheduler

vif-3_1 working 1
vif-4_2 working 2
WAN protection
Figure 28: WAN redundancy

Please note:
In order to establish an end-to-end OPIC2 communication, at least one VLAN inter-
face 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 interfaces of
all CES instances (cesop-z) must be configured with different VLAN IDs.
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 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.5.1.2.2 Core Unit Redundancy

Being one of the unique features of the Hitachi Energy 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 pro-
vided 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 29 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 star
FOX61x
Core Unit East 1
(Standby)
OPIC2 1
1
MPLS-TP Network
2 Core Unit West 2
(Active)
GbE star
Figure 29: 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.5.1.3 Performance Monitoring

OPIC2’s performance monitoring is based on supervision of the WAN performance measured
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.
Performance counters are the basis of all performance monitoring in OPIC2. There are 8 count-
ers 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.9.5.3 AP: /unit-x/circuitEmulation/cesop-z, Status - CESoP (on page 153) and
section 8.9.5.4 AP: /unit-x/circuitEmulation/cesop-z, Status - Statistics (on page 154) 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 interface
within several different time durations. Available options are last 15 minutes, last 24
hours and last 7 days. Check section 8.12.6 AP: /unit-x/vlanInterfaces/vif-z_v, Sta-
tus (on page 163) 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 fol-
lowing alarms which are created by comparing the set/clear threshold values with the perfor-
mance 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 sec-
ond
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 recommended 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).
Please note:
All EPL alarms observed during OPIC2 lifetime are stored in the OPIC2 event
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 trans-
mission 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 trans-
mission 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 net-
work administrator when these alarms appear. Also note that during EPD, due to
safety reasons, AIS (ALL 1) is sent to the OPIC2 user interfaces 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
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 transmis-
sion delay threshold.
− See detailed behavior in combination with other delay and traffic effected alarms in Figure
30.
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 net-
work 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.
Check section 8.9.4 AP: /unit-x/circuitEmulation/cesop-z, Fault Management (on page 150) to
see where the EPL, PEPL, EPD and PEPD alarms are located in FOXCST view of OPIC2.
Check section 8.12.4 AP: /unit-x/vlanInterfaces/vif-z_v, Fault Management (on page 162) to see
where the DTE alarm is located in FOXCST view of OPIC2.
Figure 30 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 30: Performance monitoring alarms and warning levels
Figure 31 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” configuration.
Figure 31: Packet delay variation
Figure 32 shows the packet delay histogram. It helps to monitor real packet delays in the net-
work and omit wrong configurations of the OPIC2 “E2E transmission delay” configuration.

Figure 32: Packet delay histogram
Figure 33 shows the packet loss rate variation. In a properly configured network the packet loss
rate shall be 0% or very close to 0%.
Figure 33: Packet loss rate variation
Figure 34 shows the packet loss rate histogram. In a properly configured network the packet
loss rate shall be 0% or very close to 0%.

Figure 34: Packet loss rate histogram
5.5.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 pri-
mary 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 con-
nections. Received ARP requests are responded with ARP reply messages carrying also the
MAC address of the destination OPIC2 unit. Figure 35 shows how ARP message exchange
works between two end stations.
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 35: 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 destination IP
addresses. Check section 8.2.3.1 AP: /unit-x, Configuration – General (on
page 120) and section 8.9.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration –
General (on page 144) 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 configura-
tion, 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 starting with
three hexadecimal bytes of 00:02:a3 which represents Hitachi Energy products.
Check section 8.2.3.1 AP: /unit-x, Configuration – General (on page 120) to see
how to access the Source MAC address in FOXCST.
5.5.2 Trail Supervision

OPIC2 offers “Trail Supervision” as an additional safety mechanism against faulty user configu-
rations 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.9.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration – General (on page 144).
When enabled, up to 15 characters of “Transmitted Trail Trace Identifier (TTI)” which are config-
urable by the user are inserted in OPIC2 frames. The user can also configure up to 15 charac-
ters of “Expected TTI” field to accept only the OPIC2 frames carrying the expected TTI value.
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 “Transmitted
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.6 Functions for TDM Based Transport
5.6.1 PMTS (Performance Monitoring Timeslot)

An optional PM (Performance Monitoring) time slot can be added to the nx64 kbit/s data stream
for monitoring of the end to end performance. This PMTS heads the associated concatenated
time slot group. As a consequence they will then occupy n+1 time slots. This feature is available
for the TDM transport application and its utilization is mandatory for the use of the following
functions:
• Bidirectional symmetrical 1+1 linear trail protection (LTP)
• Trail Trace Identifier (TTI) transmission and supervision
• Remote defect indication (RDI) transmission
• Remote interface defect indication (RIDI)

• Remote loop (2b) control
Please note:
PMTS and related functionalities are not supported for FO5 interfaces.
For details about the PM time slot structure and its utilization for the implemented functions
please refer to [1KHW028611] Application Note “OPIC1 and OPIC2 TDM Features”.
5.6.2 PMTS Generated Defects

The supervision of the received PMTS can generate the following PMTS defects:
• PM AIS:
This defect is activated if there are not more than 3 binary “0” within each of two consecutive
PM frames.
• Loss of PM Multiframe:
There are three consecutive PM frames with errored multiframe alignment words.
• TTI Mismatch:
The received TTI does not correspond to the expected TTI.
Please note:
The PMTS defects “PM AIS” and “Loss of PM Multiframe” are used as criteria for
the trail switching decision, see section 5.6.3 Bidirectional Symmetrical Linear Trail
Protection (on page 50).
Please note:
The PMTS defect “TTI Mismatch” is used by the fault management to generate the
alarm “Trace Identifier Mismatch” (TIM), see section 8.7.4 AP: /unit-x/tdmChannels/
chan-t, Fault Management (on page 139).
5.6.3 Bidirectional Symmetrical Linear Trail Protection

The OPIC2 unit provides a proprietary bidirectional symmetrical 1+1 linear trail protection (LTP)
with switching times ≤ 25 ms.
Please note:
The FOX61x system feature “1+1 inherently monitored subnetwork connection pro-
tection (SNCP/I)” is not available and therefore not configurable with OPIC2.
The bidirectional symmetrical 1+1 linear trail protection (LTP) is available only with the use of
the PMTS, see section 5.6.1 PMTS (Performance Monitoring Timeslot) (on page 49). When
PMTS is available, PM AIS, PM RDI or Loss of PM Multiframe can be detected and used as
switching criteria.
1+1 protection provides the bidirectional symmetrical 1+1 protection. The operation type can be
configured to revertive or non-revertive.
The switching of the working and the protecting data channel is done in sink direction only. On
the source side a fixed bridge is used.

working working
TDM
protecting Network protecting
P12 P12 P12 P12

transport transport transport transport
P12 P12 P12 P12
P12 P12 P12
P0-nc P0-nc P0-nc

OPIC2
OPIC2
Data Data
Figure 36: 1+1 protection of the data channel in one direction
5.6.4 Protection Configuration

P0_nc protection switching takes place in the OPIC2 traffic signal processing and not in the
OPIC2 cross connect function.
The local PMTS supervision is used to detect signal failures of the received traffic on both the
working and the protecting trail but the PMTS is also used to transmit relevant information about
the local trail switching status to the remote end to ensure that the remote end trail switching
reacts in a way that at both ends the signal is received from the same trail.
Protection switching action can be initiated by three different request types but the switching
decision is taken considering the situation of the locally received signal on both working and
protecting trails as well as the locally available knowledge of the situation of the received signal
at the remote end: this knowledge is received with the PMTS Trail Protection Control bits.
• Traffic signal local request:
These traffic signal requests received independently on both the working and the protecting
trails define which trail is not available. This information is used locally for the trail switching
decision.
− PM AIS
This defect is activated if there are not more than 3 binary “0” within each of two consecu-
tive PM frames.
− Loss of PM Multiframe
This defect is activated if there are three consecutive PM frames with errored multiframe
alignment words.
• Traffic signal remote request:
The traffic signal local requests are used to determine the Trail Status information to transmit
remotely on the PMTS of the working trail and on the PMTS of the protecting trail. For details
about the Trail Status refer to [1KHW028611] Application Note “OPIC1 and OPIC2 TDM
Features”.
• External Requests:
− Forced switch to working

− Forced switch to protecting

The External Requests are used locally for the trail switching decision and transmitted
remotely on the PMTS using the Trail Protection Control bits. For details about the logic that
defines the External Command that is transmitted on the working trail PMTS and on the pro-
tecting trail PMTS refer to [1KHW028611] Application Note “OPIC1 and OPIC2 TDM Fea-
tures”.
The Trail Protection Control information received on both working and protecting trail is used
locally for the trail switching decision.
Please note:
A forced switch is executed even when there is a failure on the target signal.
The External Requests are maintenance functions, i.e. they are not stored in the unit’s data-
base.
It is possible to check the status of the protection switch (working, protecting circuit) via the CTP
status function.
5.7 Synchronization Functions
5.7.1 Unit Synchronization
Please note:
If the TDM transport mode is used, the FOX61x network element does not have to
be synchronized to a timing source providing phase information.
OPIC2 requires properly synchronized network elements in order to fulfill differential protection
requirements. For this purpose Hitachi Energy 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 infor-
mation (time of day) is distributed by PTP in boundary clock mode. Alternatively the PTP “Fre-
quency And Phase” mode can be used where the frequency and the phase information (time of
day) are distributed by PTP in boundary clock mode. For more information about network
design requirements and proper configuration of the network element, 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” or “Frequency
And Phase” mode, and get into so called phase-lock state before OPIC2 can start circuit emula-
tion operation and IRIG-B or PPS 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.
Proper synchronization requires that both connected OPIC2 CESoP instances are synchronized
to a common timing source. The OPIC2 can check
• if both CESoP instances use a PTP grandmaster clock with the same identifier, and/or
• if both CESoP instances use a PTP grandmaster clock which is synchronized to GPS.
If the configured synchronization criteria are not met a SCNM alarm is raised.
If proper synchronization of the network is not guaranteed, OPIC2 will stop the circuit emulation
operation and IRIG-B or PPS output signal generation, and send an AIS signal (all 1) towards
the TPE interface. The alarm activation (OOS and SCNM) and stopping of the circuit emulation
operation can be delayed by a configurable holdover time. See section 8.2.3.3 AP: /unit-x, Con-
figuration – Holdover (on page 121).
Major conditions to stop CESoP operation and IRIG-B or PPS output signal generation are:
• Core unit enters free run mode
• Core unit enters holdover mode and remains in holdover for longer than the configured hold-
over time

• Core unit protection switch-over (core unit redundancy)

• Core unit reboot
• Core unit remove
• Core unit software activation
• Core unit system release update
5.7.2 IRIG-B and PPS Generation

OPIC2 generates IRIG-B002/006 outputs or PPS for the user as long as the unit itself is syn-
chronized to a PTP grandmaster clock placed in the WAN with a high accuracy clock (sub-µs).
The IRIG-B and PPS generation works closely with the “Unit synchronization and supervision”
block which sends the synchronized BCDTOY, BCDYEAR, PPS and supervision information to
the IRIG-B and PPS generation block. When the synchronization is degraded, the IRIG-B and
PPS generation block is informed and IRIG-B or PPS outputs are set to “0” immediately. See
Figure 37 for a visual representation of the relationship between the two internal functional
blocks to generate IRIG-B or PPS.
FOX61x
IRIG-B 002/006 OPIC2

or PPS IRIG-B and PPS generation
Devices with electrical 6x elect rical
port-6
IRIG-B/PPS input IRIG-B/PPS IRIG-B/PPS encoder
IRIG-B 002/006
or PPS output
BCDDay
Device with optical IRIG- 1x optical (ST) interface 0
port-5 BCDYear
B/PPS input Output select PPS
Unit synchronization and

supervision
PPS from core unit
Figure 37: IRIG-B frame generation and PPS generation
Please note:
When synchronization is degraded or lost, the “Unit Synchronization and Supervi-
sion” block activates the OOS alarm to inform the user. As long as the OOS alarm
is active, IRIG-B and PPS output generation is stopped and IRIG-B or PPS output
lines are driven to “0” which will be indicated by the OSSO alarm.
5.8 IEEE C37.94 Protocol

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

The IEEE C37.94 frame structure is designed to allow the passage of information in packet for-
mat from the multiplexer to the teleprotection equipment and from the teleprotection to the multi-
plexer 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 structure 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 format
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 38.
Time
0 µs 125 µs 250 µs 375 µs 500 µs

256 bit frame
16 bits Header (sync)

a b c d e f g h 00 0 0 1 1 1 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 38: IEEE C37.94 frame structure
5.8.1.1 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: a b c d e f g h = 1 0 0 1 1 0 1 1
Pattern 2: a b c d e f g h = 1 1 y 1 1 1 1 1
• 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.8.1.2 Overhead Data

This 48-bit section includes bits for providing information between the multiplexer and telepro-
tection 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.8.1.3 Channel Data

This 192-bit section comprises 96 data bits, with each data bit followed by its complement.
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.
5.8.1.4 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.8.2 Communication Failure Scenarios
5.8.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 con-
secutive 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.8.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.8.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 signal
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 signal is
bad (LOS).
5.9 FOX6plus Frame Compatible Hitachi Energy

Teleprotection Equipment Protocol
This type of fiber-optic interface serves for interconnecting different Hitachi Energy teleprotec-
tion equipment (implementing the FOX6plus compatible optical transmission protocol) to a FOX-
61x network, in particular
• the Numerical Line Protection REL 316,
• the Line Differential Protection Terminals REL551/REL561, and
• the Teleprotection Equipment NSD570/NSD70D.

The frame structure is designed according to Hitachi Energy’ Safety Frame Concept imple-
mented 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 39.
SYNC BIT "1"

SYNC BIT "0"
SYNC BIT "1"
SYNC BIT "1"

SYNC BIT "1"
SYNC BIT "0"
SYNC BIT "0"
SYNC BIT "0"

REMOTE BIT
PARITY BIT
8 kHz Clock
CH 1
"0"
"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 bit s
Data bit s = "0"
Figure 39: Hitachi Energy proprietary SFC frame structure
5.9.1.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.9.1.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.9.1.3 Data Bits

The remaining of the safety frame is used for data transmission. Since OPIC2 does not support
interconnection of Hitachi Energy FOX6plus Multiplexer Equipment but only Hitachi Energy
Teleprotection Equipment, only 1 data channel is used:
• Bit 18: Data Channel 1
5.9.1.4 Not Used Bits

Since OPIC2 does not support interconnection of Hitachi Energy FOX6plus Multiplexer Equip-
ment but only Hitachi Energy Teleprotection Equipment, the following bits of the frame are not
used and shall be set to 0:
• Bit 8…13, 15, 16, 17, 19, 20, 22…28, 30 and 31 are set to 0.


The receiver will rise a LOS when the alarm is indicated by the SFP module (“LOS” according to
MSA INF-8074i).
The receiver will clear LOS when the SFP module clears the LOS alarm.

• The data bits over the higher order communications link are replaced with “All Ones”, which
is commonly referred to as Alarm Indication Signal or AIS.
• Change the “Remote Bit” in the transmitted optical output frames from “0” to “1”.
• The data bits in the transmitted optical output frames are replaced with “All Ones”.
5.10 FO5 Protection Interface

This type of fiber-optic interface serves for interconnecting teleprotection equipment using the
Siemens® FO5 protection interface to a FOX61x network.

The OPIC2 supports the clock synchronous mode with 2 or 8 channels. Each channel uses 8
kbit/s. Correspondingly the bit rate on the FO5 interface is 128 kbit/s or 512 kbit/s.

The receiver will rise a LOS when the alarm is indicated by the SFP module (“LOS” according to
MSA INF-8074i).
The receiver will clear LOS when the SFP module clears the LOS alarm.

• The data bits over the higher order communications link are replaced with “All Ones”, which
is commonly referred to as Alarm Indication Signal or AIS.
• Change the “Remote Bit” in the transmitted optical output frames from “0” to “1”.
Please note:
The “Remote Bit” is not applicable for the FO5 interface type.
• The data bits in the transmitted optical output frames are replaced with “All Ones”.
5.11 IRIG-B Protocol

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 Sep-
tember, 2004.

IRIG-B is one of the 6 existing IRIG code formats which are defined by different pulse rates as
shown below:
Table 9: 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
IRIG-H 1 PPS 1 second
Note that the OPIC2 unit supports only the IRIG-B format.
5.11.1 Signal Identification Numbers

In addition to the letter used to designate one of the six IRIG code formats, signal identification
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 10: 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
5.11.2 IRIG-B 002/006 Framing

An IRIG-B frame is composed of pulse-width modulated signals as shown in Figure 40:
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 40: 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 expressions
(e.g. BCDTOY)
• “1” = 5 ms active high in 10 ms = shows a binary “One” for one bit of the coded expressions
(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 41: 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” sym-
bols 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.11.3 IRIG-B Leap Second Introduction

The basic time for mostly all of the world's local time zones is called Coordinated Universal
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.
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 published 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 output
frame:
Please note:
The standard way of OPIC2 IRIG-B output to count UTC time across a leap second
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

FOX61x | OPIC2 COMMISSIONING
6 Commissioning
This section describes the management of the basic system functions of the OPIC2 unit and the
commissioning of 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 R2/FOX615/FOX612/FOX611” for specific
characteristics of the FOX61x.
6.1 Prerequisites
Before starting the commissioning of any application on the OPIC2 unit, the following prerequi-
sites need to be fulfilled:
6.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.2 OPIC2 Unit

In a FOX615 R2 or FOX615, the OPIC2 unit is inserted into a subrack slot as listed in section
4.2 Slots for the OPIC2 Unit (on page 17).
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
6.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 operation of the
FOXCST, please refer to [1KHW002466] User Manual “FOXCST”.
6.1.4 PETS
The PETS on the FOX61x network element must be configured to an appropriate synchroniza-
tion clock source.
Ensure that both connected FOX61x network elements are properly configured in term of net-
work 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 TPE Link Commissioning with Packet Transport
6.2.1 IEEE C37.94 Application with RED670 64 kbit/s LDCM Module

To set up a communication link between two of Hitachi Energy 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

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)
Source IP: 192.168. 100.1 VLAN 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
VLAN ID = 10;
label = 2000
GbE star
port-1 port-2
forward out and reverse forward out and reverse
in label = 100 in label = 200
FOX61x (subrack-2)
OPIC2 (slot-8) port-1 port-2
GbE star
Source IP: 192.168. 100.2 forward out and reverse forward out and reverse
vif-1_1
VLAN ID = 10;
label = 2000
Protection port-1 cesop-1
Relay IEEE C37.94 Dest. IP: 192.168.100. 1 vif-1_2
VLAN 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.

2. Navigate to front port configuration dialog in Tree View:

- AP: /unit-8/port-1, Configuration - Interface.
- Interface Operating Mode = Packet,
- 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.



End of instruction
MPLS-TP configuration
OPIC2 is designed to work over MPLS-TP. Therefore, the configuration of all known network
elements, MPLS-TP tunnels and VPWS towards OPIC2 are needed.
Follow the basic MPLS-TP configuration in section 6.2.8 Basic MPLS-TP Configuration for a
Redundant OPIC2 Link (on page 84) 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 → LDCMxxx
→ 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 → LDCMxxx
→ 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
6.2.2 IEEE C37.94 Application with RED670 2 Mbit/s LDCM Module

• 2 SFP modules
1KHW001871R0005 (850nm, multi mode, up to 2 km)
• 2 fiber optic cables
FOX61x (subrack 1)
OPIC2 (slot-8) Core Unit

vif-1_2 (slot-11)
Source IP: 192.168. 100.1 VLAN ID = 11;
Relay IEEE C37.94 Dest. IP: 192.168.100. 2
vif-1_1
VLAN ID = 10;
label = 2000
GbE star
port-1 port-2
FOX61x (subrack-2)

GbE star
vif-1_1
VLAN ID = 10;
label = 2000
Relay IEEE C37.94 Dest. IP: 192.168.100. 1 vif-1_2
VLAN 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 IEEE C37.94 towards the RED670 with 1x64 kbit/s
protection channel and use the hitless WAN redundancy feature.




End of instruction
of MPLS-TP.
End of instruction
RED670:
→ CRMx”
• TerminalNo: 1
• RemoteTermNo: 2
• DiffSynch: ECHO
End of instruction

Commissioning
follows:
• Check Status
→ CRMx”
End of instruction
6.2.3 Hitachi Energy TPE Application with REL551 and REL316*4

Relays
• REL551 preconfigured with an Hitachi Energy Communication Module (DCM-FOM), or
• REL316*4
• 2 SFP modules
1KHW001872R0001 (1310 nm, single mode, up to 30 km)
• 2 optical attenuators
1KHW001997R0010 (10 dB FC/PC, 1310 nm, single mode
• 2 fiber-optic cables
V9KW/ 1KHW001323R00YY (for connection in the same cabinet), or
V9KZ/ 1KHW001326R00YY (for connection outside the cabinet)
of appropriate length.
On each OPIC2 an SFP has to be placed into the cage of the designated interface, an optical
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)
Source IP: 192.168. 100.1 VLAN ID = 11;
Protection inbound and outbound
TX
Relay port-1 cesop-1 label = 3000
REL551 ABB TPE Dest. IP: 192.168.100.2
RX
REL316*4 vif-1_1
VLAN ID = 10;
label = 2000
GbE star
port-1 port-2
FOX61x (subrack-2)
GbE star
optical attenuator vif-1_1
VLAN ID = 10;
Protection label = 2000
TX
Relay port-1 cesop-1
ABB TPE
REL551 RX
Dest. IP: 192.168.100.1 vif-1_2
REL316*4 VLAN 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 Hitachi Energy 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

- AP: /unit-8/port-1, Configuration - Interoperability.
- All One Tx Suppression Enabled = true


End of instruction
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)
− 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 configured to
“Slave”.
Please note:
The REL316*4 relay requires no configuration.

Commissioning
A successful commissioning of the communication link can be verified on any of the REL551 by
checking the round trip delay of the link and monitoring the communication status as follows:
Reset LCDMCounterDiscomfit → Yes”
• Check Status
“Enter menu → ServiceReport → Functions → Differential → DiffCom→ DiffCom”
− TransmDelay: [μs] (round trip transmission delay, available only on the terminal config-
ured as DiffCom “Slave”)
End of instruction
6.2.4 Differential Protection over E1 Interface

To set up a communication link between two line differential protection relays with E1 interface
• 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 subrack.
Each LEDE1 has to be connected over the dedicated copper cable with the differential protec-
tion device.
FOX61x (subrack 1)
LEDE1 Core Unit
(slot-9) Source IP: 192.168. 100.1 VLAN ID = 11;
Relay E1 Dest. IP: 192.168.100. 2
vif-1_1
VLAN ID = 10;
label = 2000 port-1 port-2
GbE star
PBUS
forward out and forward out and

reverse in reverse in
label = 100 label = 200
FOX61x (subrack-2)
LEDE1 OPIC2 (slot-8) port-1 port-2

GbE star
(slot-9) Source IP: 192.168. 100.2 forward out and forward out and
vif-1_1 label = 100 label = 200
VLAN ID = 10;
label = 2000
Relay E1 Dest. IP: 192.168.100. 1 vif-1_2
PBUS
VLAN 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 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.

- 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.
→ 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

of MPLS-TP.
End of instruction
6.2.5 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 following 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 subrack.
Each LECO1 has to be connected over the dedicated copper cable with the differential protec-
tion device.
FOX61x (subrack 1)
LECO1 Core Unit
Relay E0 codir Dest. IP: 192.168.100. 2
vif-1_1
VLAN ID = 10;
GbE star
PBUS

FOX61x (subrack-2)
LECO1 OPIC2 (slot-8) port-1 port-2
GbE star
VLAN ID = 10;
label = 2000
Relay E0 codir Dest. IP: 192.168.100. 1 vif-1_2
PBUS
VLAN ID = 11;
label = 3000
(slot-11)

- Usage = MPLS-TP.
- Usage = MPLS-TP.


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

- 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.



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

of MPLS-TP.
End of instruction
6.2.6 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 subrack.
Each LEDS1 has to be connected over the dedicated copper cable with the differential protec-
tion device.
FOX61x (subrack 1)
LEDS1 Core Unit
2/ 4 wire
Relay 64 kbit/s
Dest. IP: 192.168.100. 2
vif-1_1
VLAN ID = 10;
GbE star
PBUS

FOX61x (subrack-2)
LEDS1 OPIC2 (slot-8) port-1 port-2
GbE star
VLAN ID = 10;
label = 2000
2/ 4 wire
Relay 64 kbit/s
Dest. IP: 192.168.100. 1 vif-1_2
VLAN 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.




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

of MPLS-TP.
End of instruction
6.2.7 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 additional 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 subrack.
Each LEDA1 has to be connected over the dedicated copper cable with the differential protec-
tion device.
FOX61x (subrack 1)
LEDA1 Core Unit
2/ 4 wire
Relay 64 kbit/s
Dest. IP: 192.168.100. 2
vif-1_1
VLAN ID = 10;
GbE star
PBUS

FOX61x (subrack-2)
LEDA1 OPIC2 (slot-8) port-1 port-2
GbE star
VLAN ID = 10;
label = 2000
2/ 4 wire
Relay 64 kbit/s
Dest. IP: 192.168.100. 1 vif-1_2
PBUS
VLAN ID = 11;
label = 3000
(slot-11)

- Usage = MPLS-TP.


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




End of instruction
LEDA1 unit configuration

The LEDA1 has to be configured to support the 2/4-wire analog interface towards the differential
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

of MPLS-TP.
End of instruction
6.2.8 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.
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 con-
figuration.
→ 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:


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:

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.

3. Add two MPLS tunnels:

- MPLS-TP/Tunnels, Tunnels – Create a new tunnel.

4. Add two VPWS for the backplane communication with OPIC2:

- MPLS-TP/VPWS, VPWS – Create a new Ethernet Private Wire Service


Result: The MPLS-TP configuration is done.

End of instruction
6.2.9 Basic EoS and MPLS-TP Configuration for a Redundant OPIC2 Link
For linking the VLAN interfaces of the OPIC2 unit over SDH and MPLS-TP, an EoS link and a
Virtual Private Wire Service (VPWS) are required to build point-to-point connections for each
cesop-z separately. In this example, the configuration for the teleprotection signaling over two
diverse transmission links is shown.
In order to minimize the transport delay over the EoS link when using virtual concatenation, the
“Max. Differential Delay” parameter of the EoS group (available on SAMO2 and SAMO3) can be
set to “0”. This requires that all EoS group members are transported over the same path.

PTP is used for Time-of-Day synchronization. PTP packets should not be trans-
ported over EoS links.
→ In a diverse setup with EoS and MPLS-TP transport there will be a single point
of failure for the Time-of-Day synchronization.
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.

VLAN is NOT member

of the bridge VLANs
FOX61x (subrack 1)
OPIC2 (slot-8) VPWS
vif-2 AC VLAN = 11
Source IP: 192.168. 100.1 iport-8
VLAN ID = 11 Inbound label = 3000
Outbound label = 3000
cesop-1
Dest. IP: 192.168.100. 2 core
vif-1 SAMOx unit
VLAN ID = 10 (slot-18)
port-2
GbE star
eos-3 Tunnel
port-1 Forward out label = 200
VLAN is member of Reverse in label = 200
the bridge VLANs
FOX61x (subrack 2)
OPIC2 (slot-8) port-2
GbE star
eos-3
Source IP: 192.168. 100.2 Tunnel
port-1 Forward out label = 200
Reverse in label = 200
vif-1 SAMOx
VLAN ID = 10 core
(slot-18)
cesop-1 unit
Dest. IP: 192.168.100. 1
VPWS
vif-2 AC VLAN = 11
iport-8
VLAN ID = 11 Inbound label = 3000
Outbound label = 3000
Figure 42: Configuration setup for the EoS and MPLS-TP transport
EoS configuration
→ EoS configuration for FOX61x subrack 1 and subrack 2. Proceed as follows:

1. The SAMOx EoS port and the internal backplane port of the core unit that corresponds to the
slot the OPIC2 unit is plugged in (slot-8) have to be configured as CVP port type. Navigate to
port type configuration dialog in the FOXCST Tree View:
- unit-11, Main - Port Type,
- Usage for iport-8 = CVP,
- Usage for eos-3 = CVP.
2. Execute “Apply”.
3. The FOX61x Switch has to be configured so that the Ethernet packets of the cesop-1 are for-
warded between the OPIC2 unit and the SAMOx unit. Go to the FOXCST Switching tab and
select the AP: /Switching/Bridges/bridge-1, Ports.
- Select the core unit iport-8 (this is the slot where the OPIC2 is plugged),
- set the Mode = General,
- set the Acceptable Frame Type = Tagged.
- Under VLAN Configuration click the “+” button and add VLAN 10: VLANs = 10.
- Select eos-3 and make sure, eos-3 is in admin down state,
- set Mode = General,
- set the Acceptable Frame Type = Tagged.
- Under VLAN Configuration click the “+” button and add VLAN 10: VLANs = 10.
- Set eos-3 to admin up.
4. Add the VLAN to be used to the bridge VLANs. Go to the FOXCST Switching tab and select
the AP: /Switching/Bridges/bridge-1, VLANs.
- Click the “+” button and add VLAN 10: VLAN ID = 10.

Please note:
The VLAN ID 11 used for the MPLS-TP VPWS transport MUST NOT be added to
the bridge VLANs.
→ Refer to the VLAN based attachment circuit handling in [1KHW028618] User
Manual “MPLS-TP Services”.
Result: The EoS point-to-point connection for teleprotection signaling with cesop-1 is con-
figured: The connection between the two vif-1 is configured over eos-3 of the
SAMOx unit.
End of instruction
MPLS-TP Configuration
→ MPLS-TP configuration for FOX61x subrack 1. Proceed as follows:

1. The core unit Ethernet port-2 has to be configured as MPLS-TP port type. Note that the inter-
nal backplane port of the core unit that corresponds to the slot the OPIC2 unit is plugged in
(slot-8) has been configured as CVP port type before. Navigate to the port type configuration
dialog in the FOXCST Tree View:
- Usage for port-2 = MPLS-TP.
3. Navigate to the MPLS-TP configuration dialog in the FOXCST MPLS-TP view at the AP: /
MPLS-TP, Network Elements.
5. Navigate to the MPLS-TP tunnel configuration dialog in the FOXCST MPLS-TP view at the
AP: /MPLS-TP/Tunnels, Tunnels.
- Add the communication tunnel 1 on the core unit port-2 with the following settings:

6. Navigate to the MPLS-TP VPWS configuration dialog in the FOXCST MPLS-TP view at the
AP: /MPLS-TP/VPWS, VPWS.
- Add VPWS 1 on the core unit iport-8 for VLAN 11 with the following settings:

Result: The point-to-point connection for teleprotection signaling with cesop-1 is configured
in the subrack 1.
→ MPLS-TP configuration for FOX61x subrack 2. Proceed as follows:

1. The core unit Ethernet port-2 has to be configured as MPLS-TP port type. Note that the inter-
nal backplane port of the core unit that corresponds to the slot the OPIC2 unit is plugged in
(slot-8) has been configured as CVP port type before. Navigate to the port type configuration
dialog in the FOXCST Tree View:
- Usage for port-2 = MPLS-TP.
3. Navigate to the MPLS-TP configuration dialog in the FOXCST MPLS-TP view at the AP: /
MPLS-TP, Network Elements.
- Set the Global ID = 64512.
- Set the Node ID = 2.
4. Add known network elements in MPLS-TP. Click the “+” button in the Known Network Ele-
ments area.
- Add a node with following settings:

5. Navigate to the MPLS-TP tunnel configuration dialog in the FOXCST MPLS-TP view at the
AP: /MPLS-TP/Tunnels, Tunnels.
- Add the communication tunnel 1 on the core unit port-2 with the following settings:
6. Navigate to the MPLS-TP VPWS configuration dialog in the FOXCST MPLS-TP view at the
AP: /MPLS-TP/VPWS, VPWS.
- Add VPWS 1 on the core unit iport-8 for VLAN 11 with the following settings:

Result: The point-to-point connection for teleprotection signaling with cesop-1 is configured
in the subrack 2.
End of instruction
6.3 TPE Link Commissioning with TDM Transport
6.3.1 IEEE C37.94 Application with Traffic Protection for RED670 Line
Differential Protection Relays
• 2 SFP modules
1KHW001871R0005 (850 nm, multi mode, up to 2 km)

FOX61x (subrack 1)
optical attenuator
OPIC2 (slot-14) SAMO2 (slot-4)
Protection
TX
port-1 chan-1
128 kbit/s
Relay RX
IEEE C37.94
PMTS
P0_nc (n=2) P0_nc (n=2)
/pdh/vc12-1/ p12/chan-1 /pdh/vc12-2/p12/chan-1
FOX61x (subrack-2)
optical attenuator OPIC2 (slot-14)

P0_nc (n=2) P0_nc (n=2)
Protection
TX
port-1 chan-1
128 kbit/s
Relay RX
IEEE C37.94
PMTS SAMO2 (slot-4)
IEEE C37.94 Application configuration

This action list shows step by step how to configure an IEEE C37.94 port to be used in connec-
tion with a RED670 with the optical Line Data Communication Module (LDCM) with end-to-end
traffic protection on nx64 kbit/s level.
The associated channels will use 2x64 kbit/s transmission (1x64 kbit/s user data preceded by
1x64 kbit/s PMTS) and will be connected to terminated P12 channels transmitted over SDH of a
SAMO2 unit.
The following assumptions and identifiers are used:
- The OPIC2 unit is assumed to be plugged in slot-14 of the FOX61x.
- The OPIC2 unit is assigned.
- The IEEE C37.94 port used has the identifier port-1.
- The SAMO2 unit is assumed to be plugged in slot 4 of the FOX61x.
- The SAMO2 unit is assigned and has a prepared configuration of an SDH link with a connec-
tion to the following configured PDH channels:
− /pdh/vc12-1/p12/chan-1: P0_nc (n=2),
− /pdh/vc12-2/p12/chan-1: P0_nc (n=2)
→ IEEE C37.94 port configuration. Proceed as follows:

- Interface Operating Mode = TDM,
3. Navigate to the port configuration dialog:
- AP: /unit-14/port-1, Configuration – Maintenance
4. Enable the loop activation possibility from the remote unit:
- Allow Activation of Loop 2b From Remote = true
→ Associated channel configuration. Proceed as follows:

1. Navigate to the channel configuration dialog:
- AP: /unit-14/tdmChannels/chan-1, Configuration – Transport

2. Enable the PMTS usage:

- PMTS = On,
- Alarm / Switching Criteria = AIS Only,
- TTI Supervision = On,
- Transmitted TTI = sr1-u14-p1 , (subrack 1 configuration)
- Expected TTI = sr2-u14-p1 , (subrack 1 configuration)
- Transmitted TTI = sr2-u14-p1 , (subrack 2 configuration)
- Expected TTI = sr1-u14-p1 . (subrack 2 configuration)
Please note:
Fill up the Transmitted TTI and Expected TTI values with “SPACE” characters up to
the full length of 15 characters.
→ This ensures interoperability if one of the OPIC2 units is replaced with the FOX-
51x service unit OPTIF.
Result: The IEEE C37.94 port and its associated channel are configured.
→ Create cross connections. Proceed as follows:

1. Configure the protected cross connection from chan-1 (Z-End) CTP on the OPIC2 unit to /
pdh/vc12-1/p12/chan-1: P0_nc (n=2) (A-End) CTP and /pdh/vc12-2/p12/chan-1: P0_nc (n=2)
(A-End Prot.) CTP on the SAMO2 unit.
2. Select the “Cross connections” view of the FOXCST:
- Click on the “Connection Wizard” button:
- The “Create TDM Connection” dialog opens.

3. Set the connection parameters:
- Layer Rate = P0_nc.
- Directionality = Bidirectional.
- Protected = Yes.
- Label 1 = <anyName>.
- Number = 1.
- P0_nc Multiple timeslots as one channel = true
4. Execute “Next ->”.
5. Select the Z-End CTP:
- Select the OPIC2 unit, tdmChannels/chan-1.
7. Select the A-End CTP:
- Select the SAMO2 unit, /pdh/vc12-1/p12/chan-1.
8. Execute “Next”.
9. Select the A-End Protecting CTP:
10.Execute “Create”.
Result: The bidirectional cross connection is configured.

→ Activation. Proceed as follows:

1. Set the administrative state of OPIC2 unit, port-1 to up: AP: /unit-14/port-1, Main - Admin
And Oper Status:
- Set Administrative Status to State = Up.
- The “Operational Status” changes to “Up”.
3. Set the administrative state of SAMO2 unit, /pdh/vc12-1 to up: AP: /unit-4/pdh/vc12-1, Main -
Admin And Oper Status:
Result: The IEEE C37.94 port on OPIC2 unit and the channels on SAMO2 used for the
communication link are activated.
End of instruction
RED670:
→ CRMx”
• TerminalNo: 1
• RemoteTermNo: 2
• DiffSynch: ECHO
End of instruction
Commissioning
follows:
• Check Status
→ CRMx”


End of instruction
Please note:
Typical “TransmDelay” value for a FOX61X back to back configuration link consist-
ing of OPIC2 – SAMO2 (STM-4) ↔ SAMO2 (STM-4) – OPIC2 with RED670 is
about 1.35 ms.
6.3.2 IEEE C37.94 Application without Traffic Protection for NSD570

Teleprotection Equipment and G1LOa
To set up a communication link between two of Hitachi Energy NSD570 Teleprotection Equip-
ment preconfigured with an optical interface G1LOa 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
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 interface
and one of the optical cables connected between the SFPs.
optical attenuator
FOX61x (subrack 1)
TX
Protection port-2 chan-2
Relay RX
IEEE C37.94 64 kbit /s
P0_nc (n=1)
/pdh/vc12-3/ p12/chan-1
FOX61x (subrack-2)
optical attenuator OPIC2 (slot-14)
P0_nc (n=1)
TX
Relay IEEE C37.94 64 kbit /s
RX SAMO2 (slot-4)
IEEE C37.94 port configuration

This action list shows step by step how to configure an IEEE C37.94 port to be used in connec-
tion with an NSD570 with optical interface G1LOa without traffic protection on nx64 kbit/s level.
The associated channel will use 1x64 kbit/s transmission and will be connected to a terminated
P12 channel transmitted over SDH of a SAMO2 unit.


- The IEEE C37.94 port created has the identifier port-2.
tion to the following configured PDH channel:
− /pdh/vc12-3/p12/chan-1: P0_nc (n=1)
→ IEEE C37.94 port configuration. Proceed as follows:


2. Disable the PMTS usage:
- PMTS = Off
- When PMTS is disabled, all other parameters of this dialog are ignored.
Result: The IEEE C37.94 port and its associated channel are configured.
→ Create cross connections . Proceed as follows:

1. Configure the cross connection from chan-2 (Z-End) CTP on the OPIC2 unit to /pdh/vc12-3/
p12/chan-1: P0_nc (n=2) (A-End) CTP on the SAMO2 unit.

- Layer Rate = P0_nc
- Directionality = Bidirectional
- Protected = No
- Label 1 = <anyName>
- Number = 1
- P0_nc Multiple timeslots as one channel = false
- Select the OPIC2 unit, tdmChannels/chan-2


- Select the SAMO2 unit, /pdh/vc12-3/p12/chan-1
8. Execute “Create”.

And Oper Status:
Result: The IEEE C37.94 port on OPIC2 unit and the channel on SAMO2 used for the
communication link are activated.
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”.
− Transmission time [ms] x.y (round trip transmission delay)
End of instruction
Please note:
Typical “Transmission time” value for a FOX61X back to back configuration link
consisting of OPIC2 – SAMO2 (STM-4) ↔ SAMO2 (STM-4) – OPIC2 with NSD570
with G1LOa is about 5.0 ms

6.3.3 Hitachi Energy TPE Application with Traffic Protection for REL551 and
REL316*4 Line Differential Protection Terminal
Relays
• REL551 preconfigured with a fiber optical communication module (DCM-FOM), or
• REL316*4
• 2 SFP modules
• 2 optical attenuators
1KHW001997R0010 (10 dB FC/PC, 1310 nm, single mode
On each OPIC2, an SFP has to be placed into the cage of the designated interface, an optical
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.
optical attenuator
FOX61x (subrack 1)
Protection
TX
port-3 chan-3
128 kbit/s
Relay RX
ABB TPE
PMTS
P0_nc (n=3) P0_nc (n=3)
FOX61x (subrack-2)
OPIC2 (slot-14)
optical attenuator
P0_nc (n=3) P0_nc (n=3)
Protection
TX
port-3 chan-3
ABB TPE 128 kbit/s
Relay RX PMTS SAMO2 (slot-4)
Hitachi Energy TPE port configuration

This action list shows step by step how to configure an Hitachi Energy TPE port to be used in
connection with a REL551 with a fiber optical communication module (DCM-FOM) or with a
REL316*4.
The associated channel will use 3x64 kbit/s transmission (128 kbit/s user data with RDI pre-
ceded by 1x64 kbit/s PMTS) and will be connected to terminated P12 channels transmitted over
SDH of a SAMO2 unit.
- The Hitachi Energy TPE port created has the identifier port-3.
tion to the following configured PDH channels:

− /pdh/vc12-4/p12/chan-1: P0_nc (n=3)

− /pdh/vc12-5/p12/chan-1: P0_nc (n=3)
→ Hitachi Energy TPE port configuration. Proceed as follows:

6. Navigate to the port alarm configuration dialog:
- AP: /unit-14/port-3, Fault management - Configuration
7. Disable the monitoring of the TLOFA alarm:
- Monitored = false

2. Enable the PMTS usage:
- PMTS = On,
- Alarm / Switching Criteria = AIS Only,
- TTI Supervision = Off.
Result: The Hitachi Energy TPE port and its associated channel are configured.

1. Configure the protected cross connection from chan-3 (Z-End) CTP on the OPIC2 unit to /
pdh/vc12-4/p12/chan-1: P0_nc (n=3) (A-End) CTP and /pdh/vc12-5/p12/chan-1: P0_nc (n=3)
(A-End Prot.) CTP on the SAMO2 unit.

- Layer Rate = P0_nc.
- Directionality = Bidirectional.
- Protected = Yes.
- Number = 1


8. Execute “Next”
9. Select the A-End Protecting CTP:
10.Execute “Create”.

And Oper Status:
Result: The Hitachi Energy TPE port on OPIC2 unit and the channel on SAMO2 used for
the communication link are activated.
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)
− 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 configured to
“Slave”.
Please note:
The REL316*4 relay requires no configuration.
Commissioning
A successful commissioning of the communication link can be verified on any of the REL551 by
checking the round trip delay of the link and monitoring the communication status as follows:
Reset LCDMCounterDiscomfit → Yes”
• Check Status
“Enter menu → ServiceReport → Functions → Differential → DiffCom→ DiffCom”
− TransmDelay: [μs] (round trip transmission delay, available only on the terminal config-
ured as DiffCom “Slave”)
End of instruction
Please note:
Typical “TransmDelay” value for a FOX61X back to back configuration link consist-
ing of OPIC2 – SAMO2 (STM-4) ↔ SAMO2 (STM-4) – OPIC2 with REL551 is
about 1.20 ms.
6.3.4 Hitachi Energy TPE Application without Traffic Protection for NSD570
Teleprotection Equipment and G1LO
ment preconfigured with an optical interface G1LO over a FOX61x network with two OPIC2
• 2 SFP modules 1KHW001872R0001
(1310 nm, single mode, up to 30 km)
the optical cables connected between the SFP and the G1LO.

optical attenuator
FOX61x (subrack 1)
TX
Relay RX
ABB TPE 128 kbit/s
P0_nc (n=2)
FOX61x (subrack-2)
OPIC2 (slot-14)
optical attenuator
P0_nc (n=2)
TX
Relay ABB TPE 128 kbit/s
RX SAMO2 (slot-4)

connection with an NSD570 with an optical interface G1LO without traffic protection on nx64
kbit/s level.
The associated channel will use 128 kbit/s transmission (user data with RDI) and will be con-
nected to a terminated P12 channel transmitted over SDH of a SAMO2 unit.
- The ABB TPE port created has the identifier port-4.
− /pdh/vc12-6/p12/chan-1: P0_nc (n=2)


- PMTS = Off.


p12/chan-1: P0_nc (n=2) (A-End) CTP on the SAMO2 unit.

- Protected = No
- Number = 1
- Select the OPIC2 unit, tdmChannels/chan-4.

And Oper Status:
End of instruction


Digital Interface:
− Interface Type: Optical OTERM/OPTIF
− Long Haul: off
End of instruction
Commissioning
A successful commissioning of the communication link can be verified on any of the NSD570 by
End of instruction
Please note:
Typical “Transmission time” value for a FOX61x back to back configuration link
and G1LO is about 5.1 ms.
6.3.5 Hitachi Energy TPE Application without Traffic Protection for NSD570
Teleprotection Equipment and G1LOa
ment preconfigured with an optical interface G1LOa over a FOX61x network with two OPIC2
• 4 SFP modules
V9KU/ 1KHW001321R00YY (for connection in the same cabinet), or
V9KX/ 1KHW001324R00YY (for connection outside the cabinet)
On each OPIC2 and G1LOa, an SFP has to be placed into the cage of the designated interface
and one of the optical cables connected between the SFPs.

FOX61x (subrack 1)
optical attenuator
TX
Relay RX
ABB TPE 128 kbit/s
P0_nc (n=2)
FOX61x (subrack-2)
OPIC2 (slot-14)
optical attenuator
P0_nc (n=2)
TX
Relay ABB TPE 128 kbit/s
RX SAMO2 (slot-4)

connection with an NSD570 with an optical interface G1LOa without traffic protection on nx64
kbit/s level.
The associated channel will use 128 kbit/s transmission (user data with RDI) and will be con-
nected to a terminated P12 channel transmitted over SDH of a SAMO2 unit.
- The ABB TPE port created has the identifier port-4.
− /pdh/vc12-6/p12/chan-1: P0_nc (n=2)


- PMTS = Off


p12/chan-1: P0_nc (n=2) CTP on the SAMO2 unit.

- Protected = No
- Number = 1

And Oper Status:
End of instruction
Digital Interface:

− Interface Type: Optical OTERM/OPTIF

− Automatic Laser Shutdown (ALS): off
End of instruction
Commissioning
A successful commissioning of the communication link can be verified on any of the NSD570 by
End of instruction
Please note:
Typical “Transmission time” value for a FOX61x back to back configuration link
and G1LOa is about 5.1 ms.
6.4 Migration from OPIC1 to OPIC2

Migration from an OPIC1 to an OPIC2 unit means to redo the complete configurations process
on the new OPIC2 unit.
For detailed instructions, depending on the transport mode (TDM or packet), please refer to sec-
tion 6.2 TPE Link Commissioning with Packet Transport (on page 61) or section 6.3 TPE Link
Commissioning with TDM Transport (on page 97).
Please note:
The transparent transmission mode of OPIC1 is not supported on OPIC2 units. In
the connection to a TPE, OPIC2 always acts as a clock master, see also section
5.2.1.1 Synchronization (on page 28).
→ As consequence the TPE needs to be configured as a slave.

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 configured
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 summary
of the unit and of the network traffic signals.
XXXXx R1A
XXXXXXXXXXX
UNIT TRAFFIC
Figure 43: Fault indication LEDs on the OPIC2 unit
Table 11: 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.

7.2 Loops
7.2.1 CES Layer Loops

For the CESoP instances, applicable for external and internal user ports, OPIC2 offers two dif-
ferent types of diagnostic loops for maintenance purposes.
The Back-to-Back-2b loop redirects the received data from the network back to the network.
The network connection between the local OPIC2 and the remote OPIC2 can be tested.
The Front-to-Front-3b loop 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 Back-to-Back-2b or Front-to-Front-3b can be active at the same time.
OPIC2
GbE star
TPE Back-To-Back
or Loop 2b Processing
Front-To-Front
PBUS T
Loop 3b
Figure 44: Back-to-Back-2b and Front-to-Front-3b loops
Please note:
An active loop 2b or 3b is traffic disturbing.
The Back-to-Back-2b loop 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 45: Back-to-Back-2b loop
The Back-to-Back-2b loop activation at location A requires that the loop command is transported
to the remote OPIC2 at location B.
The Back-to-Back-2b loop at location B can be activated at the AP: /unit-x/circuitEmulation/
cesop-z, Status - Maintenance
• from FOXCST at location A.
The activation must be enabled at location B by setting the “Allow Activation Of Loop 2b
From Remote” parameter to true.
• from FOXCST at location B.
The Front-to-Front-3b loop according to ITU-T X.150 is the so called local loop. The loop selec-
tor 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 46: Front-to-Front-3b loop
The Front-to-Front-3b loop at location A can be activated at the AP: /unit-x/circuitEmulation/

cesop-z, Status - Maintenance
When applying a loop the operational state of the port changes to “Testing” and the “Mainte-
nance Function Active” (MFA) alarm is activated.
7.2.2 TDM Layer Loops

For the TPE interfaces operated in the “TDM” interface mode the OPIC2 offers two different
types of diagnostic loops for maintenance purposes.
Back-To-Back-2b loop redirects the received data from the network back to the network. The
network connection between the local OPIC2 and the remote OPIC2 can be tested.
Front-To-Front-3b loop sends the user data transmitted by the TPE back to the TPE. The con-
nection between TPE and local OPIC2 can be tested.
Only one loop Back-To-Back-2b or Front-To-Front-3b can be active at the same time.
OPIC2
PBUS, backplane
R
Back-To-Back
TPE Loop 2b Processing
Front-To-Front
Loop 3b
T
Figure 47: Back-To-Back-2b and Front-To-Front-3b loops
Please note:
An active Back-To-Back-2b or Front-To-Front-3b loop is traffic disturbing.
The Back-To-Back-2b loop 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 TDM
TPE
Processing
A Network Back-To-Back B
Loop 2b
T
R
AIS
Figure 48: Back-To-Back-2b loop
The Back-To-Back-2b loop at location B can be activated at the AP: /unit-x/port-y, Status - Main-
tenance


The loop command is transported to location B in the performance monitoring (PM) time slot.
This is a proprietary feature.
The activation must be enabled at location B by setting the “Allow Activation Of Loop 2b
From Remote” parameter to true.
• from FOXCST at location B.
The Front-To-Front-3b loop according to ITU-T X.150 is the so called local loop. The loop selec-
tor is located close to the PBUS interface of OPIC2 and replaces the receive signal by the trans-
mit signal.
OPIC2 A, OPIC2 B,
local remote
T
R
TPE TDM
TPE
Processing
A Front-To-Front
Network B
Loop 3b
T
R
AIS
Figure 49: Front-To-Front-3b loop
The Front-To-Front-3b loop at location A can be activated at the AP: /unit-x/port-y, Status -
Maintenance
When applying a loop the operational state of the port changes to “Testing” and the “Mainte-
nance 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 following
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 down-
load procedure.

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.

FOX61x | OPIC2 USER INTERFACE REFERENCE
8 User Interface Reference

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

Table 12: 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_r15b) the equipment status, display of inventory data, presentation of log-
books.
Configuration of the source IP Address for the “Packet” transport mode.
port-y Management of the TPE ports. Configuration of the interface operating
mode, interface type, and data rate parameters. Status information.
port-5: IRIG-B optical Management of the optical IRIG-B port. Configuration of the IRIG-B or
PPS signal format.
port-6: IRIG-B electrical Management of the electrical IRIG-B port. Configuration of the IRIG-B or
PPS signal format.
tdmChannels This MO is a container for the chan-t.
chan-t Channels are the connection termination points (CTP) for the P0_nc and
P12 traffic signal cross connections for the TDM transport of TPE port
signals. For the configuration of cross connections please refer to
The chan-t MO is not used with the “Packet” transport mode.
circuitEmulation This MO is a container for the cesop-z
cesop-z Management of the Circuit Emulation over Packet switched networks for
the packet transport of TPE port signals. Configuration of the source
assignment, TDM frames per Ethernet frame, E2E transmission delay,
diagnostic loop activation and status information.
The cesop-z MO is not used with the “TDM” transport mode.
chan-c Channels are the connection termination points (CTP) for the P0_nc and
P12 traffic signal cross connections for the packet transport of internal
TDM signals. For the configuration of cross connections please refer to
The chan-c MO is not used with the “TDM” transport mode and with the
“Terminated Optical Port” termination mode.
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.
The vif-z_v MO is not used with the “TDM” transport mode.
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 underlined.
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.
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”,
− “Overview - Unused Channels”, and
− “Overview - DDM”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.
8.2.2 AP: /unit-x, Main

− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”
FOX612/FOX611”.
8.2.3 AP: /unit-x, Configuration
8.2.3.1 AP: /unit-x, Configuration – General
Table 13: 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
Table 14: 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 and/or PTP, depending on the PTP
mode. It is recommended to set the parame-
ter to the default value 6.
If the QL of the timing in the network element
falls below the configured level, then the OPIC2
circuit emulation service will be switched off and
the time dependent service (IRIG-B or PPS out-
put) will be switched off after the expiry of the
holdover timer, see section 8.2.3.3 AP: /unit-x,
Configuration – Holdover (on page 121).
With a QL value of 14 the OPIC2 timing depen-
dent services are switched off immediately. QL is
set to 14 if the core unit makes corrections on
the PPS signal or if the PETS is in free running
mode.
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” and refer to
[1KHW029111] Application Note “PTP Configu-
ration Guideline”.
8.2.3.3 AP: /unit-x, Configuration – Holdover
Table 15: AP: /unit-x, Configuration – Holdover

Holdover Holdover Timeout 0 … 180 … 300 Defines the time interval in seconds after a
loss of frequency lock until the OOS alarm is
activated, and the circuit emulation operation
and the time dependent service (IRIG-B or PPS
output) are stopped.
With a QL value of 14 the OPIC2 timing depen-
dent services are switched off immediately. QL is
set to 14 if the core unit makes corrections on
the PPS signal or if the PETS is in free running
mode.
If frequency lock is re-established during the

holdover time no alarm is activated and the
OPIC2 timing dependent services remains oper-
ational.

8.2.4 AP: /unit-x, Fault Management

For a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
FOX612/FOX611”.
The following table lists the fault causes of the current AP.
Table 16: 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.
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.
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.

Table 16: AP: /unit-x, Fault Management (continued)

Affecting Severity
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.
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 17: 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
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 R2/FOX615/
FOX612/FOX611”.

8.3.2 AP: /unit-x/port-y, Main
8.3.2.1 AP: /unit-x/port-y, Main - General

− “Main - General”
FOX612/FOX611”.
8.3.2.2 AP: /unit-x/port-y, Main - Admin And Oper Status
Table 18: 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
8.3.2.3 AP: /unit-x/port-y, Main - SFP
Table 19: AP: /unit-x/port-y, Main – SFP

Equipment Inventory Equipment State Ok Equipment state of the plugged SFP module.
Unknown
Empty
Plugged
Mismatch
Failed

Table 19: AP: /unit-x/port-y, Main – SFP (continued)

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
Table 20: AP: /unit-x/port-y, Configuration - Interface

Interface Operating Interface Mode Packet Circuit Emulation over Packet transport of
Mode TPE port signals.
When configuring the interface mode to
“Packet” the cross connection of the corre-
sponding TDM channel is not deleted.
The cross connection is only deleted if a chan-
nel is created for the corresponding CESoP
instance.
TDM TDM transport of TPE port signals.
When configuring the interface mode to
“TDM” the termination mode of the corre-
sponding CESoP instance is automatically set
to “Terminated Optical Port”. The channels
and cross connections of the corresponding
CESoP instance are deleted.
No new channels can be created for the corre-
sponding CESoP instance.

Table 20: AP: /unit-x/port-y, Configuration - Interface (continued)

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 Hitachi Energy proprietary FOX6plus
compatible optical transmission protocol to be
used for port-y.
FO5 Selects the Siemens® FO5 protection inter-
face type.
This type is only available for the port-1 and
port-2.
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 Hitachi Energy teleprotection equipment types NSD570 and NSD70D, and for Hitachi Energy protection relay types
REL316, REL551 and REL561 use “1” (64 kbit/s).
8.3.3.2 AP: /unit-x/port-y, Configuration - Interoperability

This management function is only applicable for the Circuit Emulation over Packet transport of
TPE port signals.
Table 21: 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.2.1 Optical Teleprotection Equip-
ment (TPE) Interface (on page 27).
This parameter cannot be enabled for the
FO5 protection interface type.
All One Transmission All One Tx Suppres- Used for interoperability with the ABB TPE inter-
sion Enabled face and the REL551 differential protection
device from Hitachi Energy.
Enable this function if this combination of
device and interface is used.

8.3.3.3 AP: /unit-x/port-y, Configuration - Maintenance

This management function is only applicable for the TDM transport of TPE port signals.
Please note:
This management function is not supported for the FO5 protection interface type.
Table 22: AP: /unit-x/port-y, Configuration - Maintenance

Loop Allow Activation of The loop 2b activation from remote requires
Loop 2b From Remote the usage of the PMTS.
See section 8.7.3.2 AP: /unit-x/tdmChannels/
chan-t, Configuration – Transport (on page 137).
8.3.4 AP: /unit-x/port-y, Fault Management

FOX612/FOX611”.
Table 23: 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 connected
TPE within the overhead data of
the C37.94 frame. The alarm is
raised, when the received value
does not match the configured
value.

Table 23: AP: /unit-x/port-y, Fault Management (continued)

Affecting Severity
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.
Receiver detects AIS for more
than 100 ms (FO5).
LOS Loss Of Signal Communication true Major Low or no received power level
Alarm (IEEEC37.94 and ABB TPE and
FO5) 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.
Active Alarm been activated by the operator
from the port status dialog.
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.

Table 23: AP: /unit-x/port-y, Fault Management (continued)

Affecting Severity
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.
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).
TRF 1 Laser Fault 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 communi-
cation.

8.3.5 AP: /unit-x/port-y, Performance Management

For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
The PM parameters are presented in different groups. The following counter group is available
for the OPIC2 ports:
• “Slip Counter Events” group, see section 8.3.5.1 AP: /unit-x/port-y, Performance Manage-
ment - Slip Counter Events (on page 131).
The following counter intervals are available:
Table 24: PM counter interval availability

Counter interval Slip Counter Events
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.3.5.1 AP: /unit-x/port-y, Performance Management - Slip Counter Events
Table 25: PM group: Slip Counter Events

PM parameter Description
Positive Slips Counts the number of positive byte slips related
to the network element timing.
Negative Slips Counts the number of negative byte slips related
to the network element timing.
8.3.6 AP: /unit-x/port-y, Status
8.3.6.1 AP: /unit-x/port-y, Status - DDM

Table 26: 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 man-
datory for SFP modules with optical interfaces. However Hitachi Energy recom-
mends only optical SFP modules that support diagnostics.
8.3.6.2 AP: /unit-x/port-y, Status - Maintenance

This management function is only applicable for the TDM transport of TPE port signals.
Table 27: AP: /unit-x/port-y, 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.2 TDM
Layer Loops (on page 116).
Front-To-Front-3b Activates the front-to-front loop.
Back-To-Back-2b Activates the Back-to-back loop on the
(on remote unit) remote unit.
The remote loop 2b activation requires the
usage of the PMTS. See section 8.7.3.2 AP: /
unit-x/tdmChannels/chan-t, Configuration –
Transport (on page 137).
Note: The loop 2b on the remote unit is not
available for the FO5 interface type.
Loop Status State None No loop is activated.
Back-To-Back-2b The back-to-back loop is activated.
Front-To-Front-3b The front-to-front loop is activated.
Back-To-Back-2b The back-to-back loop is activated on the
(on remote unit) remote unit.

Please note:
On an OPIC2 link only one loop can be activated at the same time.
8.4 AP: /unit-x/port-5: IRIG-B (IRIG-B opt.)
8.4.1 AP: /unit-x/port-5, Overview

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

FOX612/FOX611”.
8.4.2.2 AP: /unit-x/port-5, Main - Admin And Oper Status
Table 28: 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.
8.4.3 AP: /unit-x/port-5, Configuration
8.4.3.1 AP: /unit-x/port-5, Configuration - Output Circuit

Table 29: AP: /unit-x/port-5, Configuration - Output Circuit

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

FOX612/FOX611”.
Table 30: AP: /unit-x/port-5, Fault Management

Affecting Severity
OSSO Output Signal Switched Equipment true Major The IRIG-B/PPS output is
Off Alarm switched off in 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”
FOX612/FOX611”.
8.5.2 AP: /unit-x/port-6, Main

FOX612/FOX611”.
8.5.2.1 AP: /unit-x/port-6, Main - Admin And Oper Status

Table 31: 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 32: AP: /unit-x/port-6, Configuration - Output Circuit

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

FOX612/FOX611”.
Table 33: AP: /unit-x/port-6, Fault Management

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

− “Overview – Alarms”, and
− “Overview – Cross Connections”
FOX612/FOX611”.

8.6.2 AP: /unit-x/tdmChannels, Main

FOX612/FOX611”.
8.7 AP: /unit-x/tdmChannels/chan-t

Please note:
The channels at this access point are used if the TPE port is configured to the
“TDM” Interface Mode, see section 8.3.3.1 AP: /unit-x/port-y, Configuration - Inter-
face (on page 126).
8.7.1 AP: /unit-x/tdmChannels/chan-t, Overview

− “Overview – Alarms”, and
− “Overview – Cross Connections”
FOX612/FOX611”.
8.7.2 AP: /unit-x/tdmChannels/chan-t, Main

− “Main - General
FOX612/FOX611”.
8.7.3 AP: /unit-x/tdmChannels/chan-t, Configuration
8.7.3.1 AP: /unit-x/tdmChannels/chan-t, Configuration – Channel Assignment
Table 34: AP: /unit-x/tdmChannels/chan-t, Configuration – Channel Assignment

Channel Assignment Channel Is Mapped To port-1 Channel assignments are fixed:
port-2 chan-1 is assigned to port-1,
chan-2 is assigned to port-2,
port-3 chan-3 is assigned to port-3,
port-4 chan-4 is assigned to port-4.

8.7.3.2 AP: /unit-x/tdmChannels/chan-t, Configuration – Transport
Please note:
The performance monitoring time slot (PMTS) is not supported for the FO5 protec-
tion interface type.
→ The PMTS parameters are not applicable.
Table 35: AP: /unit-x/tdmChannels/chan-t, Configuration – Transport

PMTS PMTS On Enables PMTS (Performance Monitoring TS)
and allows to use of the following features:
- channel supervision;
- 1+1 trail protection;
- trace identifier supervision;
- remote status indication (RDI, RIDI);
- remote back-to-back loop enabling.
Off Disables PMTS
Alarm/Switching Cri- AIS Only Trail protection switching occurs only when
teria AIS is detected in the whole PMTS.
Loss Of PM Frame Trail protection switching occurs when PMTS
multiframe alignment has been lost or when
AIS is detected in the whole PMTS.
TTI Supervision On The trail trace identifier (TTI) supervision can
Off be enabled or disabled.
In the disabled mode no check is done on the
received TTI and no alarm is generated.
Transmitted TTI 15 characters TTI transmitted in the PMTS.
It is highly recommended to configure all 15
characters for the TTI.
The default transmitted TTI is empty.
Expected TTI 15 characters TTI expected in the PMTS.
It is highly recommended to configure all 15
characters for the TTI.
The default expected TTI is empty.

The FOX51x service unit OPTIF uses the “SPACE” character to fill up a not com-
pletely defined PI (Path Identifier).
→ To be inter-operable with the OPTIF unit you have to fill up the transmitted and
expected TTI values in the OPIC2 unit with “SPACE” characters.

8.7.3.3 AP: /unit-x/tdmChannels/chan-t, Configuration - CTP
Please note:
All parameters of layer rate, number of time slots and time slot allocation are read
only.
Table 36: AP: /unit-x/tdmChannels/chan-t, 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).
This parameter is not applicable for OPIC2.
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.

Table 36: AP: /unit-x/tdmChannels/chan-t, Configuration - CTP (continued)

Remote Role z-End The CTP at the connections remote end is the
ending point of a connection.
“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- Enable revertive protection switching.
tion tion Switching The z-End will preferably select the working a-
End.
Non-revertive protection switching is only
available for channels with the number of
timeslots n=1.
Non-revertive protection switching for n>1
will be available in a future release.
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.
Please note:
The z-End of a protected connection shows two entries in the “Connected to CTPs”
table, one for the working and one for the protecting path.
8.7.4 AP: /unit-x/tdmChannels/chan-t, Fault Management

− “Fault Management - Status”
FOX612/FOX611”.
Table 37: AP: /unit-x/tdmChannels/chan-t, Fault Management

Affecting Severity
RDI Remote Defect Indication Communication true Minor The far end equipment has one
Alarm or more of the following defects
in the corresponding channel:
TSF, RTSF, TIM.
Alarm not available for an FO5
channel.

Table 37: AP: /unit-x/tdmChannels/chan-t, Fault Management (continued)

Affecting Severity
RIDI Remote Interface Defect Communication true Minor The far end equipment has one
Indication Alarm or more of the following defects
at the interface assigned to the
corresponding channel: DEG,
DRM, ENA, LOF, LOS, RDI, TLOFA,
TLOS.
channel.
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.
channel.
TIM Trace Identifier Mismatch Communication true Critical For unprotected connections
Alarm and protected connections: The
received and accepted trace
identifier does not match the
expected trace identifier on the
working trail.
channel.
TSF Trail Signal Failure Communication true Critical For unprotected connections:
Alarm Signal failure on the working
trail.
nal failure on both working and
protecting trail.
been lost.
Alarm only available if PMTS is
enabled.
channel.
8.7.5 AP: /unit-x/tdmChannels/chan-t, Status
8.7.5.1 AP: /unit-x/tdmChannels/chan-t, Status – Transport
Please note:
The performance monitoring time slot (PMTS) is not supported for the FO5 protec-
tion interface type.
→ The PMTS parameters are not applicable.

Table 38: AP: /unit-x/tdmChannels/chan-t, Status – Transport

PMTS Remote End Not Applicable Status information is not available when
PMTS is disabled.
OK
RDI
Detailed Remote Sta- Not Applicable Status information is not available when
tus PMTS is disabled.
No Failure
PM AIS
Loss Of PM Multi-
frame
TTI Mismatch
TTI State Not Applicable Status information is not available when
PMTS is disabled or when TTI supervision is
disabled.
TTI Match TTI supervision is enabled and the received
TTI equals the expected TTI.
No TTI Match TTI supervision is enabled and the received
TTI is not equal to the expected TTI.
Received TTI 0 … 15 characters Display of the received TTI in the PMTS.
8.7.5.2 AP: /unit-x/tdmChannels/chan-t, Status – CTP

Table 39: AP: /unit-x/tdmChannels/chan-t, 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-
Protecting Trail, OK No failure on the received signal.
nal.
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.
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 Prefer the trail from the a-end working
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
protecting trail.
Manual Protecting Prefer the trail from the a-end protecting
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
working trail.
8.8 AP: /unit-x/circuitEmulation
8.8.1 AP: /unit-x/circuitEmulation, Overview

− “Overview – Alarms”,
− “Overview – Cross Connections”,
− “Overview – Timeslot Allocation”, and

− “Overview – Unused Channels”

FOX612/FOX611”.
8.8.2 AP: /unit-x/circuitEmulation, Main

FOX612/FOX611”.
8.8.3 AP: /unit-x/circuitEmulation, Fault Management

FOX612/FOX611”.
Table 40: 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.9 AP: /unit-x/circuitEmulation/cesop-z
8.9.1 AP: /unit-x/circuitEmulation/cesop-z, Overview

− “Overview – Cross Connections”,
− “Overview – Timeslot Allocation”, and
− “Overview – Unused Channels”
FOX612/FOX611”.
8.9.2 AP: /unit-x/circuitEmulation/cesop-z, Main

FOX612/FOX611”.

8.9.2.1 AP: /unit-x/circuitEmulation/cesop-z, Main - Admin And Oper Status
Table 41: 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.
Lower Layer Down
8.9.3 AP: /unit-x/circuitEmulation/cesop-z, Configuration
8.9.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration – General
“VLAN Authentication Key” dialog:

Table 42: 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.
The channel creation for the CESoP instance
is blocked.
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.
The Terminated Internal Port can only be
selected if the Interface Operating Mode of
the corresponding TPE port is set to “Packet”,
see section 8.3.3.1 AP: /unit-x/port-y, Configura-
tion - Interface (on page 126).
One or more P0_nc channels have to be cre-
ated for the CESoP instance. Refer to section
8.9.3.5 AP: /unit-x/circuitEmulation/cesop-z,
Configuration – Channels (on page 147).
Transparent Inter- Use the internal PBUS port to access data on
nal Port P12 level (2048 kbit/s) for the cesop-z.
The Transparent Internal Port can only be
selected if the Interface Operating Mode of
the corresponding TPE port is set to “Packet”,
see section 8.3.3.1 AP: /unit-x/port-y, Configura-
tion - Interface (on page 126).
One P12 channel has to be created for the
CESoP instance. Refer to section 8.9.3.5 AP: /
unit-x/circuitEmulation/cesop-z, Configuration –
Channels (on page 147).
IP Parameters Source IP Address <IPv4 address> The source IP address of the OPIC2 unit is con-
figured on the unit AP.
It is shown here for reference purposes.
Destination IP <IPv4 address> Destination IP address of the remote OPIC2 unit
Address the cesop-z is connected to.
Default address: 192.168.100.101.
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 TTI 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.9.3.2 AP: /unit-x/circuitEmulation/cesop-z, Configuration – Maintenance
Table 43: 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.9.3.3 AP: /unit-x/circuitEmulation/cesop-z, Configuration – CESoP
Table 44: 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 interfaces
and towards the PBUS.
It has to be understood as a constant OPIC2
transmission delay despite data is transmitted
over the WAN with non-constant switching
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.5.1.3 "Performance Monitoring" (on
page 43).

Table 44: AP: /unit-x/circuitEmulation/cesop-z, Configuration – CESoP (continued)

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 8: "Configurable CESoP payload
sizes" (on page 39).
Bandwidth 0.656 … 6.784 Bandwidth required to transmit OPIC2 traffic.
Mbps Refer to Table 8: "Configurable CESoP payload
sizes" (on page 39).
8.9.3.4 AP: /unit-x/circuitEmulation/cesop-z, Configuration – Sync Supervision
Table 45: AP: /unit-x/circuitEmulation/cesop-z, Configuration – Sync Supervision

Sync Supervision CESoP Enable Criteria GMs Locked By The PTP synchronization of the connected
GPS Or GM IDs CESoP instances is derived from grandmaster
Match clocks
- which are synchronized to GPS,
OR
- which have the same identifier.
GMs Locked By The PTP synchronization of the connected
GPS And GM IDs CESoP instances is derived from the same
Match grandmaster clock which is synchronized to
GPS.
GMs Locked By The PTP synchronization of the connected
GPS CESoP instances is derived from grandmaster
clocks which are synchronized to GPS.
GM IDs Match The PTP synchronization of the connected
CESoP instances is derived from the same
grandmaster clock.
None (Sync Super- The PTP synchronization source is not super-
vision Disabled) vised.
A PTP phase lock is required regardless of
which PTP timing source is used.
Please note:
In case the configured “CESoP Enable Criteria” are not met for a duration longer
than the configured holdover timeout (see section 8.2.3.3 AP: /unit-x, Configuration
– Holdover (on page 121)), the SCNM alarm is raised and the TPE output signal is
replaced by an AIS (all 1).
8.9.3.5 AP: /unit-x/circuitEmulation/cesop-z, Configuration – Channels
Please note:
The channel creation is only possible
• if the Internal Port is chosen as source for the CESoP instance (Termination
Mode = Terminated Internal Port or Transparent Internal Port, see section

8.9.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration – General (on

page 144), and
• if the PBUS access is not used by the TDM transport mode of the TPE port
(Interface Operating Mode = Packet, see section 8.3.3.1 AP: /unit-x/port-y, Con-
figuration - Interface (on page 126).
Please note:
When creating a channel for a CESoP instance an existing cross connection of the
corresponding TDM channel (AP: /unit-x/tdmChannels/chan-t) is deleted.
“Create Channel” and “Create Multiple Channels” dialogs:
The “Create Advanced Channel” command displays the created channel:
“Delete Channel” dialog:
Table 46: AP: /unit-x/circuitEmulation/cesop-z, Configuration - Channels

Create Channel … Open the FOXCST dialog to create a channels.
A channel is a connection termination point
(CTP) used as a starting or ending point of a
cross connection.

Table 46: AP: /unit-x/circuitEmulation/cesop-z, Configuration - Channels (continued)

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.
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).
Create Multiple Chan- Open the FOXCST dialog to create one or more
nels … 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 dialog to create one channel
Channel … with non-consecutive timeslots in the structured
P12 signal.
The termination mode must be configured to
“Terminated Internal Port”.

Table 46: AP: /unit-x/circuitEmulation/cesop-z, Configuration - Channels (continued)

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 dialog 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.9.4 AP: /unit-x/circuitEmulation/cesop-z, Fault Management

FOX612/FOX611”.
The following table lists the Fault Causes of the current AP.
Table 47: 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 condi-
tions.
EAF Excessive Authentication Communication false Warning Ethernet packets are wrongly
Fail Alarm authenticated or replied.

Table 47: AP: /unit-x/circuitEmulation/cesop-z, Fault Management (continued)

Affecting Severity
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.
GMNGL Grand Master Not GPS Communication false Minor The local or remote Grandmaster
Locked Alarm is not synchronized to GPS.
Active Alarm been activated by the operator
from the communication channel
status dialog.
OOS Out Of Synchronization Communication true Major Synchronization to PTP time
Alarm source failed.
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.
SCNM Sync Criteria Not Met Communication true Major The configured “CESoP Enable
Alarm Criteria” (see section 8.9.3.4 AP: /
unit-x/circuitEmulation/cesop-z,
Configuration – Sync Supervision
(on page 147)) are not met for a
duration longer than the config-
ured holdover timeout (see section
8.2.3.3 AP: /unit-x, Configuration –
Holdover (on page 121)).
The TPE output signal is
replaced by an AIS (all 1).
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.

8.9.5 AP: /unit-x/circuitEmulation/cesop-z, Status
8.9.5.1 AP: /unit-x/circuitEmulation/cesop-z, Status - General
Table 48: 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.9.5.2 AP: /unit-x/circuitEmulation/cesop-z, Status - Maintenance

Table 49: 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.1 CES
Front-To-Front-3b Activates the front-to-front loop.
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.
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.9.5.3 AP: /unit-x/circuitEmulation/cesop-z, Status - CESoP

Table 50: 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.9.5.4 AP: /unit-x/circuitEmulation/cesop-z, Status - Statistics
Table 51: AP: /unit-x/circuitEmulation/cesop-z, Status - Statistics

64
Statistics Transmitted Packets vif-x_1 0 … 2 -1 Number of transmitted packets on vif-x_y
Transmitted Packets vif-x_2 0… 264-1 since the last reset.
64
Received Packets vif-x_1 0 … 2 -1 Number of received packets on vif-x_y since
Received Packets vif-x_2 0… 264-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.
64
Delayed Packets vif-x_1 0 … 2 -1 Number of delayed packets on vif-x_y since
Delayed Packets vif-x_2 0… 264-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.9.5.5 AP: /unit-x/circuitEmulation/cesop-z, Status - Sync Supervision
Table 52: AP: /unit-x/circuitEmulation/cesop-z, Status - Sync Supervision

Sync Supervision, Location Local The PTP grandmaster clock parameters apply
GM Info Table for the local CESoP instance.
Remote The PTP grandmaster clock parameters apply
for the remote CESoP instance.
GM Identity <16 hex charac- PTP grandmaster identifier.
ters>
Locked By GPS The parameter is true if the PTP grandmaster
clock is synchronized to GPS.
Frequency Traceable The parameter is true if the PTP grandmaster

clock frequency is traceable to a primary ref-
erence.
Time Traceable The parameter is true if the PTP grandmaster
clock is traceable to a primary reference.
Sync Supervision Remaining Holdover Time Not In Holdover The “CESoP Enable Criteria” are met. The PTP
grandmaster clocks operate as intended.
0 … 300 Remaining holdover time in seconds until the
TPE output signal is replaced by an AIS.
The holdover time starts when the configured
“CESoP Enable Criteria” are not met.
8.10 AP: /unit-x/circuitEmulation/cesop-z/chan-c

Please note:
The channels at this access point are used if the TPE port is configured to the
“Packet” Interface Mode, see section 8.3.3.1 AP: /unit-x/port-y, Configuration -
Interface (on page 126), and if the CESoP instance is configured to the Termina-
tion Mode “Terminated Internal Port” or “Transparent Internal Port”, see section
8.9.3.1 AP: /unit-x/circuitEmulation/cesop-z, Configuration – General (on
page 144).
8.10.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Overview

− “Overview – Cross Connections”, and
− “Overview – CTP”


FOX612/FOX611”.
8.10.2 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Main

FOX612/FOX611”.
8.10.2.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Main - Admin And Oper Status
Table 53: 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.10.3 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Configuration
8.10.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.

Table 54: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Configuration - CTP

CTP Configuration Layer Rate P12 Unstructured 2048 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.
“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.
“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 OPIC2
tion unit.
8.10.4 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Fault Management

− “Fault Management - Status”
FOX612/FOX611”.

Table 55: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Fault Management

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

for the OPIC2 channels:
• “Protection” group, see section 8.10.5.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Perfor-
mance Management - Protection (on page 158).

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/circuitEmulation/cesop-z/chan-c, Performance Management - Protection
Table 57: PM group: Protection

Switch-Over The protection switch-over count gives informa-
tion about the number and distribution of pro-
tection switching events.

8.10.6 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status
8.10.6.1 AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status – CTP
Table 58: AP: /unit-x/circuitEmulation/cesop-z/chan-c, Status – CTP

Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Working Trail, OK No failure on the received signal.
nal.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Protecting Trail, OK No failure on the received signal.
nal.
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.

Table 58: 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.11 AP: /unit-x/vlanInterfaces
8.11.1 AP: /unit-x/vlanInterfaces, Overview

FOX612/FOX611”.
− “Overview – Packet Connectivity” (PWAC port type related)
management function, please refer to [1KHW028618] User Manual “MPLS-TP Services”.
8.11.2 AP: /unit-x/vlanInterfaces, Main

FOX612/FOX611”.
8.12 AP: /unit-x/vlanInterfaces/vif-z_v

Please note:
The VLAN interfaces vif-z_1 and vif-z_2 are assigned to the CESoP instance
cesop-z.
Please note:
The VLAN interface vif-z_1 and vif-z_2 are the two VLAN interfaces used for WAN
redundancy, see section 5.5.1.2.1 Hitless WAN Redundancy (on page 41).
→ WAN redundancy is enabled by setting both VLAN interfaces of a CESoP
instance to the administrative state “Up”.
8.12.1 AP: /unit-x/vlanInterfaces/vif-z_v, Overview

FOX612/FOX611”.
− “Overview – Packet Connectivity” (PWAC port type related)

management function, please refer to [1KHW028618] User Manual “MPLS-TP Services”.
8.12.2 AP: /unit-x/vlanInterfaces/vif-z_v, Main

FOX612/FOX611”.
8.12.2.1 AP: /unit-x/vlanInterfaces/vif-z_v, Main - Admin And Oper Status
Table 59: 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.12.3 AP: /unit-x/vlanInterfaces/vif-z_v, Configuration
8.12.3.1 AP: /unit-x/vlanInterfaces/vif-z_v, Configuration – General

Table 60: 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.12.4 AP: /unit-x/vlanInterfaces/vif-z_v, Fault Management

FOX612/FOX611”.
The following table lists the Fault Causes of the current AP.
Table 61: 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.9.3.3 AP: /unit-x/
circuitEmulation/cesop-z, Configu-
ration – CESoP (on page 146).
8.12.5 AP: /unit-x/vlanInterfaces/vif-z_v, Performance Management

for the OPIC2 channels:
• “VIF” group, see section 8.12.5.1 AP: /unit-x/vlanInterfaces/vif-z_v, Performance Manage-
ment - VIF (on page 163).

Counter interval VIF
User Counter yes
History 15min yes

Table 62: PM counter interval availability (continued)

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

Packet Loss Counter for the lost packets.
Delay Exceedance Counter for packets with a delay higher than the
configured E2E Transmission Delay parameter.
8.12.6 AP: /unit-x/vlanInterfaces/vif-z_v, Status
8.12.6.1 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Statistics
Table 64: 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.12.6.2 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Delay Variation
To view the parameters listed in a table click the icon left of “Table View”.
Table 65: 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.
Packet Delay Variation Observation Interval Observation interval number, starting with 0.
Array <measurement Measured and calculated packet delay values.
parameters>

8.12.6.3 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Delay Histogram
Table 66: 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
Packet Delay Histo- Packet Delay Packet delay value.
gram Array <measurement Measured and calculated number [%] of
parameters> packet delay values.

8.12.6.4 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Loss Variation
Table 67: 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).
Packet Loss Variation Observation Interval Observation interval number, starting with 0.
Array <measurement Measured and calculated packet loss rate val-
parameters> ues.

8.12.6.5 AP: /unit-x/vlanInterfaces/vif-z_v, Status - Packet Loss Histogram
Table 68: 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).
Packet Loss Histo- Packet Delay Packet delay value.
gram Array <measurement Measured and calculated number [%] of
parameters> packet delay values.

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 R2 and FOX615 Installation”
[1KHW002462] Installation Instruction “FOX612 Installation”
[1KHW029142] Installation Instruction “FOX611 Installation”
[1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”
[1KHW028522] User Manual “Management Communication”
[1KHW002466] User Manual “FOXCST”
[1KHW002467] User Manual “TDM Services”
[1KHW028618] User Manual “MPLS-TP Services”
[1KHW002469] User Manual “CESM1, CESM1-F”
[1KHW028642] User Manual “CESM2, CESM2-F”
[1KHW028774] User Manual “CESM3”
[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”
[1KHW028611] Application Note “OPIC1 and OPIC2 TDM Features”
[1KHW029111] Application Note “PTP Configuration Guideline”
[1KHW029122] Application Note “Extended Temperature Range Operation”

Hitachi Energy Switzerland Ltd
Bruggerstrasse 72
5400 Baden - Switzerland
Phone: please refer to https://www.hitachienergy.com/contact-us/Customer-Connect-Center

(Customer Connect Center)
Email: communication.networks@hitachienergy.com
www.hitachienergy.com/communication-networks
Document ID: 1KHW028635
Copyright 2022 Hitachi Energy. All rights reserved.

Specifications subject to change without notice.

opic2_um

Uploaded by

Document Information

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

opic2_um

Uploaded by

Copyright:

Available Formats

USER MANUAL

Document edition FOX61x System Release: R1/R2/R3/R14/R15

Copyright and confidentiality Copyright in this document vests in Hitachi Energy.

Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Copyright 2022 Hitachi Energy. All rights reserved. 2

Copyright 2022 Hitachi Energy. All rights reserved. 3

5.6.4 Protection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Copyright 2022 Hitachi Energy. All rights reserved. 4

8.2.2 AP: /unit-x, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Copyright 2022 Hitachi Energy. All rights reserved. 5

9.1 Associated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Copyright 2022 Hitachi Energy. All rights reserved. 6

1.1 Precautions and Safety

1.2 Symbols and Notations

Risk of operating trouble!

1.3 Interfaces and Circuit Categories

Table 2: Optical interfaces

Copyright 2022 Hitachi Energy. All rights reserved. 7

Table 2: Optical interfaces (continued)

1.4 Document History

Copyright 2022 Hitachi Energy. All rights reserved. 8

Table 3: Document history (continued)

1.5 Target Audience

1.6 Definition of Terms

Table 4: Specific terms

Copyright 2022 Hitachi Energy. All rights reserved. 9

teleprot ection STM-x (EoS)

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

Copyright 2022 Hitachi Energy. All rights reserved. 10

Figure 2: OPIC2 used as access to teleprotection equipment (TPE), TDM transport

Copyright 2022 Hitachi Energy. All rights reserved. 11

2.2 Unit View

Figure 3: OPIC2 unit view

Copyright 2022 Hitachi Energy. All rights reserved. 12

2.3 Block Diagram

Circuit Emulation Service 1

Figure 4: OPIC2 block diagram

Copyright 2022 Hitachi Energy. All rights reserved. 13

3 Functions and Specifications

3.1 Feature Licenses

Table 5: Functions and specifications

Copyright 2022 Hitachi Energy. All rights reserved. 14

Table 5: Functions and specifications (continued)

Table 6: Mechanical and environmental features

Copyright 2022 Hitachi Energy. All rights reserved. 15

Table 6: Mechanical and environmental features (continued)

Copyright 2022 Hitachi Energy. All rights reserved. 16

4.2 Slots for the OPIC2 Unit

4.3 SFP Modules

4.3.1 SFP Interface Types

Risk of operating trouble!

Copyright 2022 Hitachi Energy. All rights reserved. 17

4.3.2 SFP Module Mounting

4.3.2.1 SFP Module with Bail Actuator

Figure 5: SFP module handling

4.3.2.2 SFP Module with Unlocking Actuator

Copyright 2022 Hitachi Energy. All rights reserved. 18

Figure 6: SFP module handling

4.3.3 Optical Attenuators

4.4 Interoperability and Compatibility

4.4.1 FOX61x System Releases

4.4.2 FOX61x Teleprotection Units

Copyright 2022 Hitachi Energy. All rights reserved. 19

4.4.3 FOX51x Teleprotection Units