Samox Um

USER MANUAL
FOX61x
SAMO2, SAMO2-F, SAMO3, SAMO5,
SAMO5-F, samo2_r15b
STM-16, STM-4, STM-1, EoS, TDM Ser-
vices, (48 E1 Ports)
SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F User Manual
Document ID 1KHW028668
Document edition FOX61x System Release: R15B

Revision: A
Date: 2022-01-06
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 | SAMO2, SAMO3, SAMO5
Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1 Precautions and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Symbols and Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Interfaces and Circuit Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 Unit View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 Functions and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Summary of Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4 SFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5 Restrictions and Limitations of Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5.1 Implementation Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5.2 Implementation Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2 Slots for the SAMOx Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.3 SFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.1 SFP Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.2 SFP Module Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.4 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.4.1 FOX61x Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.4.2 Previous ESW Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.5 Connections and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.5.1 Front Connectors of the SAMOx Unit . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.5.2 Optical SDH Interface Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.5.3 Electrical SDH Interface Cable, DIN to Open End . . . . . . . . . . . . . . . . . . . 41
4.5.4 Electrical SDH Interface Cable, DIN to BNC . . . . . . . . . . . . . . . . . . . . . . 41
4.5.5 Ethernet Interface Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.5.6 Y-Adapter Type V9PK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.5.7 Fixing the Cables to the Cable Tray . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1.1 SDH Terminal Multiplexer Unprotected . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1.2 SDH Terminal Multiplexer with MSP Protection . . . . . . . . . . . . . . . . . . . . 48
5.1.3 SDH Terminal Multiplexer with MSP and Equipment Protection . . . . . . . . . . . . 49
5.1.4 Ethernet over an SDH Terminal Multiplexer . . . . . . . . . . . . . . . . . . . . . . 49
5.1.5 SDH Add/Drop Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.1.6 SDH Add/Drop Multiplexer with MSP Protection . . . . . . . . . . . . . . . . . . . . 53
5.1.7 SDH Add/Drop Multiplexer with Equipment Protection . . . . . . . . . . . . . . . . . 54
5.1.8 SDH Add/Drop Multiplexer with MSP and Equipment Protection. . . . . . . . . . . . 55
5.1.9 Ethernet over an SDH add/drop Multiplexer . . . . . . . . . . . . . . . . . . . . . . 56
5.1.10 MPLS-TP Transport with VPWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.1.11 MPLS-TP Transport with VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.2 SDH Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3 PDH Layers and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.3.1 E12 Layer (SAMO3 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.3.2 P12 Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.4 Ethernet Layers and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.4.1 Ethernet Front Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.4.2 Ethernet Internal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.4.3 Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.4.4 Ethernet over SDH (EoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.5 Embedded Communication Channel (ECC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.6 Synchronization and Timing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.7 Traffic Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.7.1 Multiplex Section Protection (MSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.7.2 Subnetwork Connection Protection SNCP/N . . . . . . . . . . . . . . . . . . . . . . 80
5.7.3 Subnetwork Connection Protection SNCP/I . . . . . . . . . . . . . . . . . . . . . . 84
5.7.4 P12 and P0-nc Subnetwork Connection Protection SNCP . . . . . . . . . . . . . . . 86
5.7.5 Ethernet Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.8 Equipment Protection (EQP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
5.8.1 Redundancy Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
5.8.2 EQP with SETS Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.8.3 EQP with Traffic Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.8.4 EQP Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.8.5 EQP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.8.6 EQP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.1 Cross Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.1.1 VC-4 Cross Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.1.2 VC-3 Cross Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.1.3 VC-12 Cross Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.1.4 P12 Cross Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.1.5 P0-nc Cross Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
6.1.6 Cross Connection Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.2 SNCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6.2.1 SNCP Timer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6.2.2 SNCP Degraded Signal Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 117
6.3 Automatic Laser Shutdown and Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
6.3.1 Automatic Laser Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
6.3.2 Automatic Laser Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.4 Commissioning Example of PDH and EoS Transport . . . . . . . . . . . . . . . . . . . . . . 119
6.4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.4.2 Configuration of the SDH Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . 120
7 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.1 Unit Optical Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.2 Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.2.1 VC Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.2.2 P12 and P0-nc Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
7.3 Detection of Signal Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
7.4 Trail Trace Identifier (TTI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7.5 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.5.1 Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.5.2 Unit ESW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.5.3 ESW Upgrade with EQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
8 User Interface Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.2 AP: / unit-x: SAMOx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
8.2.1 AP: / unit-x, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
8.2.2 AP: / unit-x, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8.2.3 AP: / unit-x, Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8.2.4 AP: / unit-x, Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
8.2.5 AP: / unit-x, Performance Management . . . . . . . . . . . . . . . . . . . . . . . . 168
8.2.6 AP: / unit-x, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
8.2.7 AP: / unit-x, QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
8.3 AP: / unit-x / port-y, y = 1 … 4 (SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

8.3.1 AP: / unit-x / port-y, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

8.3.2 AP: / unit-x / port-y, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
8.3.3 AP: / unit-x / port-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
8.3.4 AP: / unit-x / port-y, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . 180
8.3.5 AP: / unit-x / port-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
8.4 AP: / unit-x / port-y, y = 5 … 8 (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
8.4.4 AP: / unit-x / port-y, Performance Management . . . . . . . . . . . . . . . . . . . . 185
8.4.5 AP: / unit-x / port-y, Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
8.4.6 AP: / unit-x / port-y, QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
8.5 AP: / unit-x / port-y / mau, y = 5 … 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
8.5.1 AP: / unit-x / port-y / mau, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
8.6 AP: / unit-x / port-y, y = 101 … 148 (E12) (SAMO3 only) . . . . . . . . . . . . . . . . . . . . . 186
8.6.4 AP: / unit-x / port-y, Performance Management . . . . . . . . . . . . . . . . . . . . 187
8.6.5 AP: / unit-x / port-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
8.7 AP: / unit-x / port-y / vc12, y = 101 … 148 (SAMO3 only) . . . . . . . . . . . . . . . . . . . . 189
8.7.1 AP: / unit-x / port-y / vc12, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 189
8.7.2 AP: / unit-x / port-y / vc12, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
8.7.3 AP: / unit-x / port-y / vc12, Configuration . . . . . . . . . . . . . . . . . . . . . . . . 190
8.7.4 AP: / unit-x / port-y / vc12, Fault Management . . . . . . . . . . . . . . . . . . . . . 193
8.7.5 AP: / unit-x / port-y / vc12, Performance Management . . . . . . . . . . . . . . . . . 195
8.7.6 AP: / unit-x / port-y / vc12, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
8.8 AP: / unit-x / sdh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.8.1 AP: / unit-x / sdh, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.8.2 AP: / unit-x / sdh, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.9 AP: / unit-x / sdh / sdh-y, y = 1 … 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.9.1 AP: / unit-x / sdh / sdh-y, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.9.2 AP: / unit-x / sdh / sdh-y, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.9.3 AP: / unit-x / sdh / sdh-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 201
8.9.4 AP: / unit-x / sdh / sdh-y, Fault Management . . . . . . . . . . . . . . . . . . . . . . 206
8.9.5 AP: / unit-x / sdh / sdh-y, Performance Management. . . . . . . . . . . . . . . . . . 208
8.9.6 AP: / unit-x / sdh / sdh-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
8.10 AP: / unit-x / sdh / sdh-y / dccm and dccr, y = 1 … 8 . . . . . . . . . . . . . . . . . . . . . . . 213
8.10.1 AP: / unit-x / sdh / sdh-y / dccm and dccr, Overview . . . . . . . . . . . . . . . . . . 213
8.10.2 AP: / unit-x / sdh / sdh-y / dccm and dccr, Main . . . . . . . . . . . . . . . . . . . . 213
8.10.3 AP: / unit-x / sdh / sdh-y / dccm and dccr, Configuration . . . . . . . . . . . . . . . . 214
8.10.4 AP: / unit-x / sdh / sdh-y / dccm and dccr, Fault Management . . . . . . . . . . . . . 215
8.10.5 AP: / unit-x / sdh / sdh-y / dccm and dccr, Status. . . . . . . . . . . . . . . . . . . . 215
8.11 AP: / unit-x / sdh / sdh-y / j-z, y = 1 … 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
8.11.1 AP: / unit-x / sdh / sdh-y / j-z, Overview. . . . . . . . . . . . . . . . . . . . . . . . . 217
8.11.2 AP: / unit-x / sdh / sdh-y / j-z, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
8.11.3 AP: / unit-x / sdh / sdh-y / j-z, Configuration . . . . . . . . . . . . . . . . . . . . . . 218
8.11.4 AP: / unit-x / sdh / sdh-y / j-z, Fault Management. . . . . . . . . . . . . . . . . . . . 219
8.11.5 AP: / unit-x / sdh / sdh-y / j-z, Status . . . . . . . . . . . . . . . . . . . . . . . . . . 219
8.12 AP: / unit-x / vc4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
8.12.1 AP: / unit-x / vc4, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
8.12.2 AP: / unit-x / vc4, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
8.12.3 AP: / unit-x / vc4, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
8.13 AP: / unit-x / vc4 / vc4-b. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
8.13.1 AP: / unit-x / vc4 / vc4-b, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
8.13.2 AP: / unit-x / vc4 / vc4-b, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
8.13.3 AP: / unit-x / vc4 / vc4-b, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 223
8.13.4 AP: / unit-x / vc4 / vc4-b, Fault Management . . . . . . . . . . . . . . . . . . . . . . 225
8.13.5 AP: / unit-x / vc4 / vc4-b, Performance Management . . . . . . . . . . . . . . . . . . 227

8.13.6 AP: / unit-x / vc4 / vc4-b, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

8.14 AP: / unit-x / vc4 / vc4-b / klm-n00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
8.14.1 AP: / unit-x / vc4 / vc4-b / klm-n00, Overview. . . . . . . . . . . . . . . . . . . . . . 230
8.14.2 AP: / unit-x / vc4 / vc4-b / klm-n00, Main . . . . . . . . . . . . . . . . . . . . . . . . 231
8.14.3 AP: / unit-x / vc4 / vc4-b / klm-n00, Configuration . . . . . . . . . . . . . . . . . . . 231
8.14.4 AP: / unit-x / vc4 / vc4-b / klm-n00, Fault Management. . . . . . . . . . . . . . . . . 232
8.14.5 AP: / unit-x / vc4 / vc4-b / klm-n00, Status . . . . . . . . . . . . . . . . . . . . . . . 233
8.15 AP: / unit-x / vc4 / vc4-b / klm-npq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
8.15.1 AP: / unit-x / vc4 / vc4-b / klm-npq, Overview. . . . . . . . . . . . . . . . . . . . . . 234
8.15.2 AP: / unit-x / vc4 / vc4-b / klm-npq, Main . . . . . . . . . . . . . . . . . . . . . . . . 234
8.15.3 AP: / unit-x / vc4 / vc4-b / klm-npq, Configuration . . . . . . . . . . . . . . . . . . . 235
8.15.4 AP: / unit-x / vc4 / vc4-b / klm-npq, Fault Management. . . . . . . . . . . . . . . . . 236
8.15.5 AP: / unit-x / vc4 / vc4-b / klm-npq, Status . . . . . . . . . . . . . . . . . . . . . . . 237
8.16 AP: / unit-x / pdh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
8.16.1 AP: / unit-x / pdh, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
8.16.2 AP: / unit-x / pdh, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
8.17 AP: / unit-x / pdh / vc12-y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
8.17.1 AP: / unit-x / pdh / vc12-y, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 238
8.17.2 AP: / unit-x / pdh / vc12-y, Main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
8.17.3 AP: / unit-x / pdh / vc12-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . 239
8.17.4 AP: / unit-x / pdh / vc12-y, Fault Management . . . . . . . . . . . . . . . . . . . . . 242
8.17.5 AP: / unit-x / pdh / vc12-y, Performance Management . . . . . . . . . . . . . . . . . 244
8.17.6 AP: / unit-x / pdh / vc12-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
8.18 AP: / unit-x / pdh / vc12-y / p12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
8.18.1 AP: / unit-x / pdh / vc12-y / p12, Overview . . . . . . . . . . . . . . . . . . . . . . . 250
8.18.2 AP: / unit-x / pdh / vc12-y / p12, Main. . . . . . . . . . . . . . . . . . . . . . . . . . 250
8.18.3 AP: / unit-x / pdh / vc12-y / p12, Configuration . . . . . . . . . . . . . . . . . . . . . 250
8.18.4 AP: / unit-x / pdh / vc12-y / p12, Fault Management . . . . . . . . . . . . . . . . . . 255
8.18.5 AP: / unit-x / pdh / vc12-y / p12, Performance Management . . . . . . . . . . . . . . 256
8.18.6 AP: / unit-x / pdh / vc12-y / p12, Status . . . . . . . . . . . . . . . . . . . . . . . . . 257
8.19 AP: / unit-x / pdh / vc12-y / p12 / chan-z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
8.19.1 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Overview. . . . . . . . . . . . . . . . . . . 259
8.19.2 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Main . . . . . . . . . . . . . . . . . . . . . 259
8.19.3 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Configuration . . . . . . . . . . . . . . . . 260
8.19.4 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Fault Management. . . . . . . . . . . . . . 261
8.19.5 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Performance Management . . . . . . . . . 262
8.19.6 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Status . . . . . . . . . . . . . . . . . . . . 263
8.20 AP: / unit-x / eos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
8.20.1 AP: / unit-x / eos, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
8.20.2 AP: / unit-x / eos, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
8.20.3 AP: / unit-x / eos, QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
8.21 AP: / unit-x / eos / eos-y. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
8.21.1 AP: / unit-x / eos / eos-y, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
8.21.2 AP: / unit-x / eos / eos-y, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
8.21.3 AP: / unit-x / eos / eos-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 267
8.21.4 AP: / unit-x / eos / eos-y, Fault Management . . . . . . . . . . . . . . . . . . . . . . 271
8.21.5 AP: / unit-x / eos / eos-y, Performance Management. . . . . . . . . . . . . . . . . . 272
8.21.6 AP: / unit-x / eos / eos-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
8.21.7 AP: / unit-x / eos / eos-y, Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
8.21.8 AP: / unit-x / eos / eos-y, QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.22 AP: / unit-x / eos / eos-y / eos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.22.1 AP: / unit-x / eos / eos-y / eos, Overview . . . . . . . . . . . . . . . . . . . . . . . . 273
8.22.2 AP: / unit-x / eos / eos-y / eos, Main . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.22.3 AP: / unit-x / eos / eos-y / eos, Configuration . . . . . . . . . . . . . . . . . . . . . . 274
8.22.4 AP: / unit-x / eos / eos-y / eos, Fault Management . . . . . . . . . . . . . . . . . . . 276
8.22.5 AP: / unit-x / eos / eos-y / eos, Performance Management . . . . . . . . . . . . . . . 277
8.22.6 AP: / unit-x / eos / eos-y / eos, Status . . . . . . . . . . . . . . . . . . . . . . . . . 278
8.23 AP: / unit-x / eos / eos-y / eos / vcz-a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
8.23.1 AP: / unit-x / eos / eos-y / eos / vcz-a, Overview . . . . . . . . . . . . . . . . . . . . 279

8.23.2 AP: / unit-x / eos / eos-y / eos / vcz-a, Main . . . . . . . . . . . . . . . . . . . . . . 279

8.23.3 AP: / unit-x / eos / eos-y / eos / vcz-a, Configuration . . . . . . . . . . . . . . . . . . 280
8.23.4 AP: / unit-x / eos / eos-y / eos / vc4-a, Fault Management . . . . . . . . . . . . . . . 281
8.23.5 AP: / unit-x / eos / eos-y / eos / vc3-a, Fault Management . . . . . . . . . . . . . . . 282
8.23.6 AP: / unit-x / eos / eos-y / eos / vc12-a, Fault Management . . . . . . . . . . . . . . 284
8.23.7 AP: / unit-x / eos / eos-y / eos / vcz-a, Performance Management . . . . . . . . . . . 285
8.23.8 AP: / unit-x / eos / eos-y / eos / vcz-a, Status. . . . . . . . . . . . . . . . . . . . . . 286
8.24 AP: / unit-x / iports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8.24.1 AP: / unit-x / iports, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8.24.2 AP: / unit-x / iports, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8.25 AP: / unit-x / iports / iport-b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
8.25.1 AP: / unit-x / iports / iport-b, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
8.25.2 AP: / unit-x / iports / iport-b, Performance Management . . . . . . . . . . . . . . . . 292
8.25.3 AP: / unit-x / iports / iport-b, Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . 292
8.25.4 AP: / unit-x / iports / iport-b, QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
9 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
9.1 Associated FOX61x Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

FOX61x | SAMO2, SAMO3, SAMO5 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] Operating Instruction “Precautions and safety”.
1.2 Symbols and Notations

This User Manual uses the following symbols:
CAUTION Non-observance could result in minor or moderate injury.

Failing to comply with this may result in the injury of the user or in physical dam-
age.
→ Possible actions are given.
Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.
Please note:
Shows significant information.
1.3 Interfaces and Circuit Categories
Table 1: Electrical interfaces and circuit categories

SAMO2/SAMO3 interface Circuit category according Max. rating
to IEC 62368-1 Voltage Current
Local power supply ES2 < 72 VDC < 1.6 A
Electrical Gigabit or Fast Ethernet ES1 <3V < 10 mA
ITU-T G.703 electrical interfaces ES1 < 3.3 Vpeak < 10 mA
Electrical STM-1 ES1 < 1V < 10 mA

Table 2: Optical interfaces

SAMO2/SAMO3 interface Parameter Max. rat- Remarks
ing
Optical STM-1, STM-4 and STM-16 Laser class 11
(according to EN 60825-1)
Optical transmitted power 2 5 dBm
Transmitted wavelength 1310 nm, non-visible
1550 nm, radiation
1470 nm …
1610 nm
Time until automatic safety 0.85 s
power reduction operates
Time until automatic restart 110 s
takes place
1. 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.
2. 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.
1.4 Document History

Table 3: Document history
Document ID FOX61x Rev. Date Changes since previous version
release
1KHW028668 R15B A January 2022 Updated for current system release.
1KHW028668 R15A J June 2021 - In the FOXCST the QoS related parameters are
moved to the new “QoS” view.
- New feature Redundancy Support. See section
8.2.1.1 AP: / unit-x, Overview - Redundancy Support
(on page 146).
- “mau” access point removed from the internal
ports.
- Update copyright statement.
1KHW028668 R14A H June 2020 - Support in the system release R14.
1KHW028668 R3B_SP01 G January 2020 - New alarm “RDEG” for SNC-protected VC12 trails.
- Configurable WTR timers for SNC-protected VC12
trails.
- New status information for SNC-protected VC12
trails.
- POH signal label configurable to use “Equipped
non-specific”.
1KHW028668 R3B_SP01 F December 2019 - Update of references to the synchronization user
manual.
- Eos ports of a standby SAMOx unit can be directly
added to the FOX61x Switch in the FOXCST “Switch-
ing” view.
- AP tree reordered.
- Multiplex section configuration parameters reor-
dered, see section 8.9.3.2 AP: / unit-x / sdh / sdh-y,
Configuration - MS (on page 203).
1KHW028668 R3B E June 2019 - TTI complemented with “NUL” characters instead
of “SPACE” characters.
- Update of the Ethernet cables specification.
- Modified ECSL and SCSL alarm activation.

Table 3: Document history (continued)

Document ID FOX61x Rev. Date Changes since previous version
release
1KHW028668 R3A_SP01 D March 2019 - In the FOXCST the “QoS resource usage” GUI is
moved from the Status to the QoS management func-
tion.
- Switch transmit queue buffer configurable with a
CPS.
1KHW028668 R3A C November 2018 - Support of the CESM3 core unit.
- New Hitachi Energy branding.
- QoS configuration reworked.
- Virtual concatenation group differential delay:
minimum value 0 ms.
1KHW028668 R2D 2 February 2018 - Service unit SAMO5, SAMO5-F added.
- Note added about cross connection creation with
EQP.
1KHW028668 R2C 1 December 2016 - User Manuals SAMO2, SAMO2-F and SAMO3
merged.
- New document number.
- R-L2GP support for RSTP enabled ports.
- Port Type and Mirroring management functions
moved from “Overview” to “Main”.
- Performance Management added on Ethernet port
layer.
- QoS management functions added on unit, Ether-
net port and EoS port layers.
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

Table 4: Specific terms
Term Explanation
CESM1 Designates the core and control unit CESM1 or CESM1-F of FOX61x.
CESM2 Designates the core and control unit CESM2 or CESM2-F of FOX61x.
Core Unit Designates the core and control unit CESM1, CESM1-F, CESM2, CESM2-F or
CESM3 of 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.

Table 4: Specific terms (continued)

Term Explanation
SAMO2 Designates the one slot wide functional unit SAMO2 samo2_r15a, SDH transport
unit for TDM and Ethernet traffic of the FOX61x. It must be operated in an actively
cooled FOX61x subrack with a fan unit.
In this User Manual, the term SAMO2 is used to name the SAMO2 and SAMO2-F.
Where certain features or characteristics apply to the SAMO2-F only, the SAMO2-F
is named explicitly.
SAMO2-F Designates the two slot wide functional unit SAMO2 samo2_r15a, SDH transport unit
for TDM and Ethernet traffic of the FOX61x.
SAMO2-F is functionally identical to the SAMO2 unit, but can be operated in FOX61x
subracks with passive cooling, i.e. fanless operation.
SAMO3 Designates the two slot wide functional unit SAMO3 samo2_r15a, SDH transport unit
for TDM and Ethernet traffic of the FOX61x.
SAMO3 provides the same functions as the SAMO2 and supports in addition 48 E1
ports usable for TDM transport.
SAMO5 Designates the one slot wide functional unit SAMO5 samo2_r15a, SDH transport
unit for TDM and Ethernet traffic of the FOX61x. It must be operated in an actively
cooled FOX61x subrack with a fan unit.
In this user guide, the term SAMO5 is used to name the SAMO5 and SAMO5-F.
Where certain features or characteristics apply to the SAMO5-F only, the SAMO5-F
is named explicitly.
SAMO5-F Designates the two slot wide functional unit SAMO5-F samo2_r15a, SDH transport
unit for TDM and Ethernet traffic of the FOX61x.
SAMO5-F is functionally identical to the SAMO2 unit, but can be operated in FOX61x
subracks with passive cooling, i.e. fanless operation.
SAMOx In this User Manual, the term SAMOx is used to name the SAMO5, SAMO5-F,
SAMO2, SAMO2-F and SAMO3. Where certain features or characteristics apply to a
specific unit only, this unit is named explicitly.

FOX61x | SAMO2, SAMO3, SAMO5 INTRODUCTION
2 Introduction
2.1 General
This document describes the architecture and functions of the SAMO5, SAMO5-F, SAMO2,
SAMO2-F and SAMO3 units and shows, how the units are commissioned and operated as part
of the FOX61x.
The SAMO5 is a 1 slot wide functional unit of FOX61x that must be operated in actively cooled
subracks. The SAMO5-F is a 2 slot wide functional equivalent to the SAMO5 unit that can be
operated in passively cooled subracks.
subracks. The SAMO2-F is a 2 slot wide functional equivalent to the SAMO2 unit that can be
operated in passively cooled subracks.
subracks.
The SAMO5, SAMO5-F, SAMO2, SAMO2-F and SAMO3 units are SDH units, providing four
SDH front interfaces, four Ethernet front interfaces, PBUS access (FOX61x internal TDM bus)
and also connect to the Gb-Ethernet star (FOX61x internal Ethernet connection to the core unit).
The SAMO3 unit provides in addition 48 E12 front interfaces usable for TDM transport applica-
tions.
The SAMOx unit can be configured as an SDH access system with termination and add/drop
functionality from STM-16, STM-4 and STM-1 trunks. Typical applications are the termination of
STM-16, STM-4 or STM-1 traffic from an STM-16, STM-4 or STM-1 trunk in linear networks (ter-
minal multiplexer TM) and add/drop of VC-n traffic in linear or ring networks (add/drop multi-
plexer ADM).
The following SDH interfaces are supported:
• two interfaces STM-16 or STM-4:
− STM-16 optical (SAMO2 and SAMO3 only), or
− STM-4 optical,
• two interfaces STM-4 or STM-1:
− STM-4 optical or
− STM-1 electrical or optical,
The interfaces can be used as aggregate interfaces for the transmission of STM-16, STM-4 or
STM-1 traffic into the transport network, or as tributary interfaces for the access of subtended
network elements. The aggregate or tributary usage of an interface is independent of the
SAMOx configuration.
The interfaces are implemented on SAMOx with four SFP cages, allowing to plug in any com-
patible SFP module according to the network application.
The SAMOx unit implements also the synchronous equipment timing source (SETS) for the unit.

10 / 10 / 10 / 10 /
100 / 100 / 100 / 100 /
1000 1000 1000 1000 STM-4 / STM-4 / STM-16 / STM-16 /
BASE-T BASE-T BASE-T BASE-T STM-1 STM-1 STM-4 STM-4 E12
ETH ETH ETH ETH SDH SDH SDH SDH

E12
PHY PHY PHY PHY SFP SFP SFP SFP
4x 4x 16 x 16 x 48 x E12
AU-4 AU-4 AU-4 AU-4 SAMO3 only
AU-4 Cross Connect
48 x 945 x
TU-3 TU-12
TU-3 TU-12
Cross Connect Cross Connect
12 x 24 x 252 x 64 x 48 x
VC-4 VC-3 VC-12 VC-12 VC-12
EoS P-12 P-12
2 x 1GbE
8 x 100MbE
Ethernet Switch SAMOx
10Gb Ethernet 1Gb Ethernet PBUS
Figure 1: SAMOx overview
Please note:
The maximum SDH port speed of the SAMO5 is STM-4.
→ The STM-16/STM-4 ports shown in Figure 1 can only be operated with STM-4.
The SAMOx unit accesses Ethernet services via the units four electrical 10/100/1000BASE-T
front interfaces and the 10 Gb or 1 Gb-Ethernet star from the core unit(s). The 10 Gb and 1 Gb-
Ethernet stars connect the SAMOx unit to the working and protecting core units. The Ethernet
switch device on the SAMOx unit participates in the FOX61x Switch.
Please note:
The access to the 10Gb-Ethernet star is only available with the CESM3 core unit.
Ethernet over SDH (EoS) traffic can be transported in two modes:
• Unswitched mode:
The Ethernet traffic from an Ethernet front port is bypassing the Ethernet switch device and
is mapped to a EoS group. There is one dedicated EoS group per front port in the
unswitched mode.
Ethernet traffic from any other FOX61x Switch port can be transported over SDH. With the
four Ethernet front ports using the unswitched mode, 28 (4 for SAMO5) EoS groups remain
available for the FOX61x Switch ports. The total EoS transport capacity is limited to 2 Gbit/s.
• Switched mode:
A SAMOx Ethernet front port in the switched mode accesses the switch device and partici-
pates in the FOX61x Switch. Ethernet traffic from the Ethernet front ports and any other
FOX61x Switch port can be transported over SDH. There are 32 (8 for SAMO5) EoS groups
in maximum. The total EoS transport capacity is limited to 2 Gbit/s.

Please note:
Using the MPLS-TP Transport function with the VPWS service, the number of EoS
groups is limited:
→ Maximum 8 EoS groups in the unswitched mode.
→ Maximum 12 EoS groups in the switched mode.
FOX61x
STM-4/
FXO FXS
TDM
STM-16
LESU1 Network
West
E12 SAMO3 only

DTE
SAMOx
STM-4/
E12 STM-16
TDM
DTE LEDE1 Network
East
data
DTE LEDS1
Ethernet
DTE
Figure 2: SAMOx unit in an add/drop multiplexer application
The SAMO5, SAMO5-F, SAMO2 and SAMO2-F units access TDM services via PBUS. Up to 64
P12 tributary signals can directly be accessed.
The SAMO3 unit accesses TDM services directly via the 48 E12 front ports and via PBUS. In
addition to the 48 E12 front ports up to 64 P12 tributary signals can be accessed via the PBUS.

2.2 Unit View
Figure 3: SAMO5 / SAMO2 (left) and SAMO5-F / SAMO2-F (right) unit view
Figure 4: SAMO3 unit view
Figure 3 and Figure 4 show the SAMO5, SAMO5-F, SAMO2, SAMO2-F and SAMO3 unit hard-
ware. On the front plate are two LEDs for unit- and traffic failure indication.

CAUTION Non-observance could result in minor or moderate injury.

The front of the SAMO5-F and SAMO2-F can become hot.
→ Do not touch the front cover.

2.3 Block Diagram

Front
LEDs Front Connectors
10/100/1000 STM-4/STM-1 STM-4/STM-1 STM-16/STM-4 STM-16/STM-4 SAMOx

E12
BASE-T Ethernet (SFP) (SFP) (SFP) (SFP)
4x AU-4 4x AU-4 16x AU-4 16x AU-4 48x E12
SAMO3 only
2x 40x AU-4 4
Redundancy Switch
4
Only 40x AU-4 are active
at the same time
STM STM STM STM STM STM STM STM SETS

Term. Term. Term. Term. Term. Term. Term. Term. G.813
4x 4x 4x 4x 16x 16x 16x 16x
AU-4 AU-4 AU-4 AU-4 AU-4 AU-4 AU-4 AU-4
AU-4 Cross Connect
12x AU-4 31x AU-4
VC-4
VC-4 Termination
Termination
12x VC-4 1 48x TU-3 2 945x TU-12
1
EoS via VC-12, VC-3 TU-3 Cross TU-12 Cross
and VC-4 can be used
up to a maximum
Connect Connect
capacity of 12 VC-4.
24x TU-3 2
2
VC-3 VC-12
The TU-3 cross connect
is limited t o a maximum Termination Termination
capacity of 48x48 TU-3.
24x VC-3 1 252x 64x 48x
VC-12 VC-12 VC-12
VCAT / LCAS
P12
GFP
Termination
3
The ECC access capacit y
PBUS 48x P12
Board MAC / FIFO / is taken from the
P12 Termination capacity,
Controller Rate Control i.e. the maximum access
2x 1GbE capacity for ECC and P12
8x 100MbE Terminat ion is 64 x P12.
P12 ECC
Ethernet Switch
Termination Processing
2x 10GbE 2x 1GbE 3
64x P12 4x P12
(only 1 active) (only 1 active)
PBUS PBUS PBUS

Subrack internal 10Gb Ethernet 1Gb Ethernet
Power Access Access Access REDUN
communication Access Access
Backplane Connectors
Figure 5: SAMOx block diagram

Please note:
The maximum SDH port speed of the SAMO5 is STM-4.
→ The STM-16/STM-4 ports shown in Figure 5 can only be operated with STM-4.
Figure 5 shows the block diagram of the SAMOx unit. The main functions of the SAMOx unit
can be divided into the following nine parts:
• SDH terminal multiplexer or add/drop multiplexer with four SDH interfaces:
− 2 x STM-16/STM-4 (SAMO2 and SAMO3), or
− 2 x STM-4 (SAMO5), and
− 2 x STM-4/STM-1.
• SDH cross connect system for 123 x 123 AU-4.
• SDH cross connect system for 48 x 48 TU-3
• SDH cross connect system for 1309 x 1309 TU-12
• Termination to the PBUS of 64 x P12.
• Termination of 48 E12 front ports (SAMO3 only).
• Ethernet over SDH with a maximum capacity of 2 Gbit/s:
− up to 32 EoS groups (SAMO2 and SAMO3),
− up to 8 EoS groups (SAMO5).
• Redundancy switch
The redundancy switch is used for the 1:1 equipment protection application with two SAMOx
units. It connects the protecting SAMOx unit via the backplane with a capacity of 2 x 40 x
AU-4.
40 x AU-4 40 x AU-4
STM-x STM-x
SFP SFP
2 x 40 x AU-4
STM-x STM-x STM-x STM-x

port port port port
SAMOx SAMOx
working protecting
80 x AU-4
Figure 6: Redundancy switch, working unit is active
The redundancy switch makes the four SDH ports on the working unit and the four SDH
ports on the protecting unit available on the working unit, i.e. doubles the terminated SDH
traffic from 40 x AU-4 to 80 x AU-4.
• Ethernet switch
The Ethernet switch device on the SAMOx unit participates in the FOX61x Switch. FOX61x
Switch ports are all external Ethernet ports on units participating in the FOX61x Switch, the
SAMOx EoS ports and, depending of the switch mode, the SAMOx external Ethernet ports:

− Unswitched mode:
A SAMOx external Ethernet port is not part of the FOX61x Switch. The Ethernet traffic
from the Ethernet front ports is bypassing the Ethernet switch device and is mapped to a
dedicated EoS port with a point-to-point connection.
With the VLAN Bridge function all EoS ports can be used as customer VLAN ports (CVP).
With the MPLS-TP Transport function up to 8 EoS ports can be used as Pseudo Wire
Attachment Circuits (PWAC) in a VPWS or up to 28 EoS ports can be used as Customer
VLAN Ports (CVP) in a VPLS.
− Switched mode:
A SAMOx external Ethernet port is part of the FOX61x Switch.
With the VLAN Bridge function all external Ethernet ports and EoS ports can be used a
customer VLAN ports (CVP).
With the MPLS-TP Transport function the external Ethernet ports and up to 12 EoS ports
can be used as Pseudo Wire Attachment Circuits (PWAC) in a VPWS or up to 32 EoS
ports can be used as Customer VLAN Ports (CVP) in a VPLS.

FOX61x | SAMO2, SAMO3, SAMO5 FUNCTIONS AND SPECIFICATIONS
3 Functions and Specifications

The SAMOx unit uses the following feature licenses, provides the functions listed below and
conforms to the corresponding standards and recommendations (conformance to applicable
parts of the standards).
3.1 Feature Licenses

This unit is subject to one or several feature licenses. The following licenses are available for
this unit.
Table 5: Feature licenses relevant for this unit

License ID Short Description Description
STM16 Lic SAMOx STM16 Feature License for STM-16 operation, for SAMOx, right to use
per card.
E1-EQP Lic SAMO3 E1Prot Feature License for E1 port protection, for SAMO3, right to use
per subrack.
Please note:
Two SAMOx units operating as equipment protected pair and both using STM-16
ports need two feature licenses.
For more information on features licenses please refer to [1KHW028777] Release Note “FOX-
61x System Release R15B” and to [1KHW028776] Product Description “Feature Licenses for
FOX61x”.
3.2 Summary of Standards

Table 6: Standards
Feature Standard Release
SDH transport, ETSI - EN 300 147 (09/2001) r1a
Synchronous digital hierarchy multiplexing
structure
- EN 300 417-1-1 (10/2001)
Generic processes and performance
- EN 300 417-2-1 (10/2001)
SDH and PDH physical section layer functions
- EN 300 417-3-1 (10/2001)
STM-N regenerator and multiplex section layer
functions
- EN 300 417-4-1 (10/2001)
SDH path layer functions

Table 6: Standards (continued)

SDH transport, ITU-T - ITU-T G.707 (01/2007) r1a
Network node interface for the synchronous
digital hierarchy
- ITU-T G.783 (03/2006)
Characteristics of synchronous digital hierar-
chy (SDH) equipment functional blocks
- ITU-T G.803 (03/2000)
Architecture of transport networks based on
the synchronous digital hierarchy (SDH)
- ITU-T G.805 (03/2000)
Generic functional architecture of transport
networks
- ITU-T G.806 (01/2009)
Characteristics of transport equipment –
Description methodology and generic function-
ality
- ITU-T G.841 (10/98)
Types and characteristics of SDH network pro-
tection architectures
- ITU-T G.808.1 (02/2010)
Generic protection switching – Linear trail and
subnetwork protection
- ITU-T G.957 (03/2006)
Optical interfaces for equipments and systems
relating to the synchronous digital hierarchy
Optical interfaces SFF committee r1a
- INF-8074i Rev. 1.0 (05/2001)
SFP (Small Formfactor Pluggable) Transceiver
- SFF-8472 Rev. 9.5 (06/2004)
Diagnostic Monitoring Interface for Optical
Xcvrs
ITU-T
- G.694.2 (12/2003)
Spectral grids for WDM applications: CWDM
wavelength grid
IEC
- 60825-1 (08/2001)
Safety of laser products – Part 1: Equipment
classification, requirements and user’s guide


Synchronization and timing ETSI r1a
- EN 300 417-6-1 (05/99)
Synchronization layer functions
- EN 300 462-1-1 (05/1998)
Definitions and terminology for synchroniza-
tion networks
- EN 300 462-4-1 (05/1998)
Timing characteristics of slave clocks suitable
for synchronization supply to Synchronous Dig-
ital Hierarchy (SDH) and Plesiochronous Digital
Hierarchy (PDH) equipment
- EN 300 462-5-1 (05/1998)
Timing characteristics of slave clocks suitable
for operation in Synchronous Digital Hierarchy
(SDH) equipment
ITU-T
- ITU-T G.813 (03/2003)
Timing characteristics of synchronous digital
hierarchy (SDH) equipment slave clocks (SEC)
- ITU-T G.825 (03/2000)
The control of jitter and wander within digital
networks which are based on the synchronous
digital hierarchy (SDH)
PDH transport ETSI r1a
- EN 300 417-5-1 (10/2001)
PDH path layer functions
ITU-T
- ITU-T G.703 (11/2001)
Physical/electrical characteristics of hierarchi-
cal digital interfaces
- ITU-T G.704 (10/1998)
Synchronous frame structures used at 1544,
6312, 2048, 8488 and 44736 kbit/s hierarchy
levels
- ITU-T G.775 (10/98)
Loss of Signal (LOS), Alarm Indication Signal
(AIS) and Remote Defect Indication (RDI) defect
detection and clearance criteria for PDH signals
- ITU-T G.805 (03/2000)
Generic functional architecture of transport
networks
Access digital section for ISDN primary rate ETSI r1a
- ETS 300 233 (05/1994)
Integrated Services Digital Network (ISDN);
Access digital section for ISDN primary rate
Ethernet transport IEEE r1a
- IEEE 802.3-2008
CSMA/CD access method and physical specifi-
cations.
- IEEE 802.1D-2004
Media Access Control bridges.
Ethernet over SDH transport ITU-T r1a
- ITU-T G.7041(04/2011)
Generic Frame Procedure
- ITU-T G.7042 (03/2006)
Link Capacity Adjustment Scheme (LCAS) for
virtually concatenated signals.


Performance parameters and limits ITU-T r1a
- ITU-T G.826 (12/2002)
End-to-end error performance parameters and
objectives for international, constant bit-rate
digital paths and connections
- ITU-T M.2101.1 (04/97)
Performance limits for bringing into service
and maintenance of international SDH paths
and multiplex section
Ethernet management IETF r1a
- RFC 1213 (03/1991)
Management Information Base for Network
Management of TCP/IP-based internets: MIB-II
- RFC 2819 (05/2000)
Remote Network Monitoring Management
Information Base
Character set ITU-T r1a
- ITU-T T.50 (09/92)
International Reference Alphabet (IRA) - Infor-
mation technology - 7 bit coded character set
for information interchange
3.3 Specifications
The usage of specific VLAN IDs in the FOX61x Switch is prohibited when a
SAMOx unit is plugged in a FOX61x subrack.
→ Never use the VLAN IDs 4059 to 4062.

Table 7: Functions and specifications - SDH parameters

Feature Rating or standard Release
SDH ports r1a
Number of STM-16/STM-4 ports 2
STM-16: optical (SAMO2 and SAMO3 only)
STM-4: optical
Number of STM-4/STM-1 ports 2
STM-4: optical
STM-1: optical or electrical
Optical STM-16 interface SFP module with optical STM-16 interface
(SAMO2 and SAMO3 only) according to ITU-T G.957 with different transmis-
sion ranges
Optical STM-4 interface SFP module with optical STM-4 interface accord-
ing to ITU-T G.957 with different transmission
ranges
Optical STM-1 interface SFP module with optical STM-1 interface accord-
ing to ITU-T G.957 with different transmission
ranges
Optical connection Fibers according to ITU-T G.957
Connector duplex LC-type
SFP features - Manual laser activation / deactivation
- Automatic laser shutdown (ALS)
- Automatic laser restart (ALR)
Parameters of the optical interfaces (SFP mod- According to the manufacturer’s data sheets
ules)
Electrical STM-1 interface SFP module with electrical STM-1 interface
according to ITU-T G.703
Electrical connection Coaxial, 75 Ω
Connector DIN 1.0/2.3 (push-pull self latching/
coupling)
SDH traffic layers r1a
Number of VC-4 resources 80
AU-4 cross connect 123 x 123, unrestricted
TU-3 cross connect 48 x 48, unrestricted
TU-12 cross connect 1309 x 1309, unrestricted
Synchronization r1a
SETS on unit 1
Number of selectable SDH clock sources - 4, derived from working unit STM-16/STM-4/
STM-1 signals
- 4, derived from protecting unit STM-16/STM-4/
STM-1 signals
- 4, derived from SDH signals from other units
(shared with terminated PDH signals)
Number of selectable PDH clock sources 4, derived from terminated PDH signals (shared
with SDH signals from other units)
External synchronization input 2, derived from the external synchronization sig- r1a
nal on the working and protecting core unit
Local oscillator Reference clock with an accuracy of ± 4.6 ppm r1a
according to ITU-T G.813 (clause 5, option 1).
External synchronization output 1, external clock output on the working and pro- r1a
tecting core unit

Table 8: Functions and specifications - PDH parameters

PDH ports (SAMO3 only) r2a
Number of E12 ports 48
Electrical E12 interface according to ITU-T G.703
Interface impedance Configurable per unit:
- 120 Ω symmetrical
- 75 Ω asymmetrical
Connector 2 x DIN 41612
Maximum cable lengths
- 75 Ω with coaxial cables 390 m
- 120 Ω with balanced HF cables 180 m
P12 traffic signal handling - transparent
Jitter ITU-T G.823, table 5:
< 0.05 UIpp, 20 Hz … 100 kHz
Wander ITU-T G.823, §5.2.1
2048 kbit/s interface output wander limit
PBUS access
Number of P12 resources 64 r1d
P12 traffic signal handling, 64 P12 signals - terminated G.704 with CAS, with CRC4 r1d
- terminated G.704 with CAS, without CRC4
- terminated G.704 without CAS, with CRC4
- terminated G.704 without CAS, without CRC4
- V5 uplink, with CRC4
- V5 uplink, without CRC4
- transparent
- clock master
ECC layer via SDH RS DCC (D1 … D3 bytes, 192 kbit/s), r1a
and/or
via SDH MS DCC (D4 … D12 bytes, 576 kbit/s)
Table 9: Functions and specifications - Ethernet parameters

Ethernet ports r1a
- Number of Ethernet ports 4
electrical
- Interface type 10/100/1000BASE-T
- Interface mode Auto - MDI/MDI-X
- Electrical connection Connector RJ-45
Impedance 100 ± 15 Ω for the frequency band
from 1 to 100 MHz
Ethernet traffic layers r1a
- Ethernet modes - 10BASE-T half duplex
- 10BASE-T full duplex
- 100BASE-TX half duplex
- 100BASE-TX full duplex
- 1000BASE-T full duplex
- Autonegotiation
- Ethernet features - Flow control IEEE 802.3 r1a
- Link pass through r2a

Table 9: Functions and specifications - Ethernet parameters (continued)

- VLAN Bridging 1 - between the Ethernet front interfaces and the r1a
VC group, transport capacity limited to 100
Mbit/s per VC group (unswitched mode)
- between the Ethernet front interfaces and any
other FOX61x Switch port, including up to 32 VC
groups, transport capacity limited to 2 Gbit/s for all
VC groups (switched mode)
- MPLS-TP Transport with VPWS 2 - between the (switched) Ethernet front inter- r3a
faces (PWAC) and an MPLS-TP port on the core
unit.
- between the EoS groups 1 to 12 (PWAC) and an
MPLS-TP port on the core unit.
- MPLS-TP Transport with VPLS 2 - between the (switched) Ethernet front inter- r3b
faces (CVP) and an MPLS-TP port on the core
unit.
- between the EoS groups 1 to 32 (CVP) and an
MPLS-TP port on the core unit.
- Frame size up to 9’194 bytes r1a
EoS layer r1a
- Number of virtual concatenation groups - 4 switched or unswitched (point-to-point, EPL)
- 28 switched (SAMO2 and SAMO3 only)
- 4 switched (SAMO5)
- Framing procedure GFP according to ITU-T G.7041
- VC concatenation virtual concatenation according to ITU-T G.783
- VC capacity adjustment link capacity adjustment scheme according to
ITU-T G.7042
- Number of VC-4 resources up to 12 3
- Number of VC-3 resources up to 24
- Number of VC-12 resources up to 252
Ingress buffer, switched or unswitched guaranteed per Ethernet port or EoS group: r1e
- 10’240 bytes,
- 1 frame
Egress buffer, switched or unswitched guaranteed per Ethernet port or EoS group:
- 3’584 bytes per queue 4,
- 19 frames per queue.
limit per Ethernet port or EoS group:
- 3’584 bytes per queue, plus up to 128 kB from a
pool of 512 kB 4,
- 19 frames per queue, plus up to 128 frames
from a pool of 2048 frames.
1. The switch device will drop any incoming Ethernet packet with an incorrect length field.
2. An Ethernet front interface in the unswitched mode connects directly to the corresponding EoS group. This EoS group
is no longer available for the MPLS-TP Transport function.
3. This value is shared between all VC-4, VC-3 and VC-12 EoS group members.
4. Buffers are consumed by the frames in steps of 256 bytes, e.g. a frame with a size of 300 bytes occupies a buffer size
of 512 bytes.
Table 10: Functions and specifications - maintenance features

Error detection MS layer r1a
VC-4 layer
VC-3 layer
VC-12 layer

Table 10: Functions and specifications - maintenance features (continued)

Trail trace identifier (TTI) RS layer r1a
VC-4 layer
VC-4, VC-3 and VC-12 layer per VCG
VC-12 layer
Signal label VC-4 layer r1a
VC-3 layer
VC-12 layer
Remote defect indication VC-4 layer r1a
VC-3 layer
VC-12 layer
Loops (SAMO3 only) E12 front to front r2a
E12 back to back
Loops P12 front to front r1a
P0 front to front
Table 11: Functions and specifications - protection and alarming

Protection
- 1:1 equipment protection (EQP) Two SAMOx units, r1a
- PDH traffic to PBUS
- EoS traffic to Ethernet interfaces
- SETS
- EQP switching time < 50 ms with SAMO5 r3e
< 50 ms with SAMO2 HW revision ≥ R1F r2b
< 50 ms with SAMO3 HW revision ≥ R1D
< 600 ms with SAMO2 HW revision ≤ R1E r2b
< 600 ms with SAMO3 HW revision ≤ R1C
- Multiplex section protection (MSP) SDH ports on the same SAMOx unit (unidirectional r1a
and bidirectional)
SDH ports on two SAMOx units plugged in mating
subrack slots (unidirectional and bidirectional)
- SNCP/I up to 255 protected connections between any 2 r1a
not terminated VC-n, on the same SAMOx unit
- SNCP/I protection modes - 1+1 unidirectional, revertive
- 1+1 unidirectional, non-revertive
- SNCP/N up to 255 protected connections between any 2 r1a
terminated VC-n, on the same SAMOx unit
- SNCP/N protection modes - 1+1 unidirectional, revertive
- 1+1 unidirectional, non-revertive
- 1+1 bidirectional, revertive, for VC-12 termi-
nated to PBUS
- 1+1 bidirectional, non-revertive, for VC-12 termi-
nated to PBUS
- 1+1 bidirectional, non-revertive, for VC-12 termi-
nated to the E1 front ports (SAMO3 only)
- SNCP - between any 2 P12 or P0-nc signals from the r1a
PBUS
- between any 2 E12 front ports, on the same
SAMO3 unit (SAMO3 only)
- SNCP protection modes - 1+1 unidirectional, revertive
- 1+1 unidirectional, non revertive (for P0-1c only)

Table 11: Functions and specifications - protection and alarming (continued)

Alarm reporting ITU-T X.733 (1992) r1a
Information technology – open systems intercon-
nection – systems management: Alarm reporting
function
Table 12: Functions and specifications - performance monitoring

ITU-T G.826 MS layer r1a
VC-4 layer
VC-3 layer
VC-12 layer
E12 layer
P12 layer
Layer specific events PS layer: r1a
- Out of frame
MS layer:
- Protection switchover
VC-4 layer:
VC-3 layer:
VC-12 layer:
E12 layer:
- Line code violations
P12 layer:
- Positive slips
- Negative slips
MIB-2 statistics Ethernet layer: r1a
- In octets
- In unicast packets
- In discarded packets
- In errors
- In flow control packets
- Out octets
- Out packets
- Out flow control packets
GFP encapsulation GFP layer: r1a
- Transmitted GFP frames
- Received GFP frames
- Discarded GFP frames
- Errored GFP frames
Table 13: Functions and specifications - mechanical and environmental parameters

Feature Rating or standard
Power supply SAMO5, SAMO2 SAMO5-F, SAMO3
SAMO2-F
- Power supply range VBAT refer to [1KHW002460] System Description “FOX61x R15B”
- Maximum current consumption, IVBAT 0.8 A 0.8 A 1.1 A
VBAT = -48 V
- Maximum total power requirement from bat- 39 W 39 W 52 W
tery, PTOT The above rating includes the power consumption of four typi-
VBAT = nominal voltage cal S.4-1 SFPs (4 x 1 W). Depending on the actually plugged SFP
modules, the power consumption may be higher.

Table 13: Functions and specifications - mechanical and environmental parameters (continued)
Feature Rating or standard
Mechanical parameters SAMO5, SAMO2 SAMO5-F, SAMO3
SAMO2-F
- Construction practice 19 inch 19 inch 19 inch
- Height of unit (1 HU = 44.45 mm) 6 HU 6 HU 6 HU
- Width of unit (1 TE = 5.08 mm) 4 TE (1 slot) 8 TE (2 slots) 8 TE (2 slots)
- Size of the PCB (H x D) 233 mm x 220 mm 233 mm x 220 mm 233 mm x 220 mm
- Weight 510 g 1’700 g 970 g
- Unit cooling Active cooling man- Operation without Active cooling man-
datory fan unit (passive datory
ventilation).
Vertical mounting
of the unit is man-
datory.
- 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 equip-
ment
Reliability SAMO5, SAMO2 SAMO5-F, SAMO3
SAMO2-F
- Calculated MTTF at 35 °C (MIL-HDBK-217F) 47 years 30 years
- Calculated MTTF at 55 °C (MIL-HDBK-217F) 29 years
(assuming 20 °C higher temperature than with
the fan based unit)
Emission refer to [1KHW002460] System Description “FOX61x R15B”

Immunity refer to [1KHW002460] System Description “FOX61x R15B”
Safety refer to [1KHW002460] System Description “FOX61x R15B”
SFP modules:
according to the manufacturer’s data sheets (typically IEC
60825-1 Class 1 laser product)
Ambient conditions refer to [1KHW002460] System Description “FOX61x R15B”.
- Storage, Transport and Operation with active Error free operation up to 65°C ambient temperature is only
cooling guaranteed with SFP/SFP+ modules specified for the indus-
trial 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”
Ambient conditions not applicable -25°C … +55°C 1 not applicable
- Operation with passive cooling Error free opera-
tion up to 55°C
ambient tempera-
ture is only guaran-
teed with SFP/SFP+
modules specified
for the industrial
temperature range
(up to 85°C).
1. The SAMO2-F hardware revisions R1A and R1B support only a reduced maximum ambient temperature of 50°C in-
stead of 55°C.

3.4 SFP Modules

The SDH interfaces of the SAMOx unit are implemented with SFP cages where different SFP
pluggable modules can be inserted providing STM-16 (SAMO2 and SAMO3 only), STM-4 and/
or STM-1 front interfaces.
The SFP modules are standardized modules following the SFP – MSA (Multi-Source Agree-
ment) and are implemented according to INF-8074.
For more information please refer to section 4.3 SFP Modules (on page 32).
3.5 Restrictions and Limitations of Implementation
3.5.1 Implementation Restrictions

The table below shows the implementation restrictions that are specific for the SAMOx unit.
Table 14: Implementation restrictions

Keyword Description
Threshold for degraded defect In SAMOx the threshold for the degraded defect dDEG is configured
dDEG on the unit level per VC type, not individually per VC.
Wait to restore time, guard time In SAMOx the wait to restore time, guard time and hold off time for
and hold off time for SNCP SNCP are configured on the unit level per VC type, not individually per
VC.
Trail trace identifier TTI SAMOx supports the 16 byte TTI only.
The one byte TTI is not supported.
E1 and E2 bytes The E1 and E2 bytes of the RS and MS overhead provide a local
order wire channel for voice communication between regenera-
tors and multiplexers.
SAMOx provides no access to the E1 and E2 bytes.
F1 byte The F1 byte provides a channel for user purposes.
SAMOx provides no access to the F1 byte.
F2, F3 The F2 and F3 bytes of the VC-4 and VC-3 path overhead provide a
channel for user purposes.
SAMOx provides no access to the F2 and F3 bytes.
K3, K4 The automatic protection switching channel bytes K3 of the VC-4
and VC-3 path overhead and K4 of the VC-12 path overhead are
not supported by the SAMOx unit.
N1, N2 The tandem connection monitoring byte N1 of the VC-4 and VC-3
path overhead and N2 of the VC-12 path overhead are not sup-
ported by the SAMOx unit.
3.5.2 Implementation Limitations

For limitations that apply to the SAMOx implementation, please refer to [1KHW028777] Release
Note “FOX61x System Release R15B”.

FOX61x | SAMO2, SAMO3, SAMO5 INSTALLATION
4 Installation
4.1 Prerequisites
Before installing a SAMOx unit take care to follow the safety advice as listed in [1KHW002497]
Operating Instruction “Precautions and safety”.
Valid combinations of hardware (HW) and embedded software (ESW) versions are given in
[1KHW028777] Release Note “FOX61x System Release R15B”.
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”.

Disconnect fibers before removing or installing SFP modules. Otherwise, there is a
potential risk of damaging the optical interfaces and fibers.
4.2 Slots for the SAMOx Unit

The SAMO5 and SAMO2 units use one slot in the FOX61x subrack. The SAMO5-F, SAMO2-F
and SAMO3 units use two slots in the FOX61x subrack.
In a FOX61x, the SAMO5 or SAMO2 unit can be operated in any of the following slots.
• FOX615 R2 with CESM3 core unit: 2… 7, 16 … 20.
• FOX615 R2 with CESM1 or CESM2 core unit: 1 … 10, 12, 14 … 21.
• FOX615: 1 … 10, 12, 14 … 21.
• FOX612: 7 … 10, 12, 14.
• FOX611: 9 … 10, 12.
In a FOX61x, the SAMO5-F, SAMO2-F or SAMO3 unit can be operated in any of the following
slots. Only the left most slot is indicated:
• FOX615 R2 with CESM3 core unit: 2… 7, 16 … 20.
• FOX615 R2 with CESM1 or CESM2 core unit: 1 … 9, 12, 14 … 20.
• FOX615: 1 … 9, 12, 14 … 20.
• FOX612: 7 … 9, 12.
• FOX611: 9.
Slot 11 is reserved for the working core unit (optional: slot 13 reserved for redundant core unit in
the FOX615 R2, FOX615 and FOX612).
When using SAMOx equipment protection specific slot pairs in the FOX615 R2, FOX615 and
FOX612 subrack must be used:
FOX615 R2 and FOX615:
• Slot 4 and slot 6
FOX612:

FOX615 R2 and FOX615 FOX612 FOX611
Slot Slot Slot Slot Slot Slot Slot Slot

1 11 21 7 11 14 9 11
S S S S S S S
A A A A A A A
S S S M S M S S S S C S C S S S S M S M S M S M S C S C S M S C S
U U U O U O U U U U U U U U U U U O U O U O U O U U U U U O U U U
x x x x x x x
Figure 7: FOX61x subracks with SAMO5, SAMO2 and core unit (CU) equipment protection
using dedicated slot pairs
FOX615 R2 and FOX615 FOX612 FOX611

1 11 21 7 11 14 9 11
S S S S S S S
A A A A A A A
S S S M M S S S C C S S S M M M M C C M C
U U U O O U U U U U U U U O O O O U U O U
x x x x x x x
- - - - - - -
F F F F F F F

1 11 21 7 11 14 9 11
S S S S S S S
A A A A A A A
S S S S S S C S C S S S S C SC S C S
U U U M M U U U U U U U U U U M M M M U UU U M U U
O O O O O O O
3 3 3 3 3 3 3
Figure 8: FOX61x subracks with SAMO5-F, SAMO2-F, SAMO3 and core unit (CU) equip-
ment protection using dedicated slot pairs
4.3 SFP Modules
4.3.1 SFP Interface Types

SAMOx has four SFP cages where different SFP modules for the SDH interfaces can be
inserted. All recommended SFP modules are designed in conformance with the SFP Multi-
Source Agreement (SFF document INF-8074i) and are hot pluggable, i.e. they can be installed
and removed from an operational SAMOx unit.
The supported SFP modules can provide the following interfaces:
• Optical STM-16 interface SFP modules (SAMO2 and SAMO3 only)
− I-16.1 optical port (1310 nm, intra-office short haul)
− S-16.1 optical port (1310 nm, short haul)
− L-16.1 optical port (1310 nm, long haul)


• Optical STM-4 interface SFP modules
− X-4.2 optical port (1550 nm, enhanced long haul)
− Bidirectional optical port (1310/1550 nm, short haul)
• Optical STM-1 interface SFP modules
− X-1.2 optical port (1550 nm, enhanced long haul)
− Bidirectional optical port (1310/1550 nm, short haul)
− CWDM optical port (1470 … 1610 nm, long haul)
− CWDM optical port (1470 … 1610 nm, enhanced long haul)
• Electrical STM-1 interface SFP modules
− Electrical STM-1 interface according to ITU-T G.703
The selection of the transceiver and the media type will determine the maximum distance.
For details on connectors and pins for these interfaces please refer to INF-8074i.
Please note:
The SFP transceiver modules must be mounted by the customer.
Please note:
SFP modules must be fully MSA (Multi-Source Agreement) compliant [INF-8074].
Please note that only Hitachi Energy recommended SFP modules should be used
in order to guarantee inter-working with the SAMOx 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 SFP modules, 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
Tx/Rx Tx/Rx
(Bidi) (Bidi)
Figure 9: 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, 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 10: 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.4 Compatibility
4.4.1 FOX61x Units

SAMOx is compatible with any other FOX61x service unit with an ESW release of the current
FOX61x system release. Please refer to [1KHW028777] Release Note “FOX61x System
Release R15B”.
4.4.2 Previous ESW Revisions

The SAMOx unit with the ESW release samo2_r15a is compatible to the previous ESW release.
When upgrading to the ESW release samo2_r15a 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 SAMOx Unit

The SAMOx has four SDH interfaces on the unit front, designated from bottom up with port-1 to
port-4. The optical or electrical interface connectors are provided by the pluggable SFP mod-
ules.
The optical SDH interfaces are equipped with industry standard duplex LC connectors. The bidi-
rectional (bidi) SFP modules have a simplex LC connector.

The electrical SDH interfaces are equipped with industry standard DIN 1.0/2.3 (push-pull self
latching/coupling) connectors for coaxial cables.
The four Ethernet interfaces are designated from bottom up with port-5 to port-8.
The Ethernet interfaces are equipped with RJ-45 connectors. The interface layout is per default
according to the MDI-X layout, but implements automatic crossover functionality (MDI/MDI-X).
The 48 E12 interfaces of the SAMO3 unit are available on two 96 pin DIN connectors.
The pin and port assignment of the front panel connectors is shown in section 4.5.1.1 Ethernet
Connectors (on page 38) and section 4.5.1.2 E12 Connectors (SAMO3 only) (on page 39).

R1A R1A
39700xxx 39700xxx
pin 1
port-8
pin 8
10BASE-T 100BASE-TX 1000BASE-T

port-7 Pin
MDI MDI-X MDI MDI-X MDI MDI-X
1 TD+ RD+ Transmit + Receive + BI_DA+ BI_DB+
2 TD- RD- Transmit - Receive - BI_DA- BI_DB-
3 RD+ TD+ Receive + Transmit + BI_DB+ BI_DA+
port-6 4 BI_DC+ BI_DD+
5 BI_DC- BI_DD-
6 RD- TD- Receive - Transmit - BI_DB- BI_DA-
7 BI_DD+ BI_DC+
port-5 8 BI_DD- BI_DC-
port-4 optical optical bidi

Tx Tx/Rx
Rx
port-3
electrical
port-2 Tx
Rx
port-1
Figure 11: SAMO5, SAMO2 (left) and SAMO5-F, SAMO2-F (right) front panel and interface
connectors
The symbol indicates the risk of the hot SAMO5-F or SAMO2-F front cover.

R1A
39700xxx
Ethernet port connectors

front view
pin 1
port-8
pin 8
port-7
SFP based port connectors
optical optical bidi
Tx Tx/Rx
port-6 Rx
electrical
port-5 Tx
Rx
E12 port connectors

port-4 front view
a b c
32
port-3 31
30
29
28
27
port-2
26
25
port-1 7
6
5
4
3
2
1
Figure 12: SAMO3 front panel and interface connectors
4.5.1.1 Ethernet Connectors
Table 15: SAMOx Ethernet front connector pins

Pin 10BASE-T 100BASE-TX 1000BASE-T
1 TD+ RD+ Transmit+ Receive+ BI_DA+ BI_DB+

Table 15: SAMOx Ethernet front connector pins (continued)

Pin 10BASE-T 100BASE-TX 1000BASE-T
2 TD- RD- Transmit- Receive- BI_DA- BI_DB-
3 RD+ TD+ Receive+ Transmit+ BI_DB+ BI_DA+
4 BI_DC+ BI_DD+
5 BI_DC- BI_DD-
6 RD- TD- Receive- Transmit- BI_DB- BI_DA-
7 BI_DD+ BI_DC+
8 BI_DD- BI_DC-
Each Ethernet interface provides two LEDs indicating the link activity state and the link state:
Activity
Link
Figure 13: Ethernet link LEDs on the SAMOx unit
The activity LED has the following states:

− Yellow blinking: Traffic activity.
− Dark: No traffic.
The link LED has the following states:
− Green: 10/100/1000 Mbit/s link up.
− Dark: Link down.
4.5.1.2 E12 Connectors (SAMO3 only)

The E12 ports can be configured to
• 120 Ω symmetrical signal termination, or to
• 75 Ω asymmetrical signal termination.
The configuration is applied on the unit layer, i.e. is valid for all E12 front ports of the SAMO3
unit.
Table 16: Pins of the E12 ports

Pin label Description
a Signal “a” for symmetrical interfaces (120 Ω signal termination) and center lead
for asymmetrical interfaces (75 Ω signal termination).
b Signal “b” for symmetrical interfaces (120 Ω signal termination) and shield for
asymmetrical interfaces (75 Ω signal termination).
Please note:
The shield of the symmetrical and asymmetrical interface cable is not grounded on
the connector frame.
→ The cable shield must be grounded via the subrack earthing bar.
The lower connector on the SAMO3 front is for the E12 ports port-101 to port-124, the upper
connector on the SAMO3 front is for the E12 ports port-125 to port-148.

Table 17: SAMO3 E12 front connector pins

E12 port E12 port Connector pin for
(lower connec- (upper connec- output output input a input b
tor) tor) a b
port-101 port-125 1a 1c 2a 2c
port-105 port-129 9a 9c 10a 10c
port-106 port-130 11a 11c 12a 12c
port-107 port-131 13a 13c 14a 14c
port-108 port-132 15a 15c 16a 16c
port-109 port-133 17a 17c 18a 18c
port-110 port-134 19a 19c 20a 20c
port-111 port-135 21a 21c 22a 22c
port-112 port-136 23a 23c 24a 24c
port-113 port-137 25a 25c 26a 26c
port-114 port-138 27a 27c 28a 28c
port-115 port-139 29a 29c 30a 30c
port-116 port-140 31a 31c 32a 32c
port-117 port-141 1b 2b 3b 4b
port-118 port-142 5b 6b 7b 8b
port-119 port-143 9b 10b 11b 12b
port-120 port-144 13b 14b 15b 16b
port-121 port-145 17b 18b 19b 20b
port-122 port-146 21b 22b 23b 24b
port-123 port-147 25b 26b 27b 28b
port-124 port-148 29b 30b 31b 32b

E12 ports which are not connected at the remote end of the cable can cause cross
talk. Cross talk onto such an open-ended cable can cause spurious alarms.
→ Set the administrative state of these ports to “down”.
4.5.2 Optical SDH Interface Cables

The optical SDH interfaces (SFP modules) are equipped with industry standard duplex LC con-
nectors (bidi SFP modules: simplex LC connector). Connection to other types of connectors as
e.g. LC, SC or FC-PC is possible with converter cables (optical jumpers) or via an optical distri-
bution frame.
The SAMOx unit performs as specified with optical single mode fibers that conform to the ITU-T
G.652 recommendation (Characteristics of a single mode optical fiber and cable).

Duplex LC connector Duplex LC connector
Simplex LC connector Simplex LC connector
Figure 14: SAMOx duplex and simplex LC to LC cable
Duplex SC connector Duplex LC connector
Simplex SC connector Simplex LC connector
Figure 15: SAMOx duplex and simplex LC to SC adapter cable
Dual FC-PC connector Duplex LC connector
FC-PC connector Simplex LC connector
Figure 16: SAMOx duplex and simplex LC to FC-PC adapter cable
Please note:
The above cables can be ordered directly from Hitachi Energy.
For details on available optical cables, please refer to [1KHW002498] Product Guide “FOX61x
cables”.
4.5.3 Electrical SDH Interface Cable, DIN to Open End

The electrical SDH interfaces (SFP modules) are equipped with industry standard DIN 1.0/2.3
(push-pull self latching/coupling) connectors for 75 Ω coaxial cables.
This cable provides input and outputs to/ from the SAMOx unit with SFP modules for STM-1
G.703 / 75 Ω circuits. The other end of this cable is not terminated.
Please note:
The electrical interface requires two cables.
Please note:
The above cable can be ordered directly from Hitachi Energy.
For details on available coaxial cables, please refer to [1KHW002498] Product Guide “FOX61x
cables”.
4.5.4 Electrical SDH Interface Cable, DIN to BNC

The electrical SDH interfaces (SFP modules) are equipped with industry standard DIN 1.0/2.3
(push-pull self latching/coupling) connectors for 75 Ω coaxial cables.

This cable provides input and outputs to/ from the SAMOx unit with SFP modules for STM-1
G.703 / 75 Ω circuits. The other end of this cable is terminated with a male BNC connector.
Please note:
The electrical interface requires two cables.
Please note:
The above cable can be ordered directly from Hitachi Energy.
For details on available coaxial cables, please refer to [1KHW002498] Product Guide “FOX61x
cables”.
4.5.5 Ethernet Interface Cables

The Ethernet interfaces are equipped with RJ-45 connectors. The interface layout is per default
according to the MDI-X layout, but implements automatic crossover functionality (MDI/MDI-X),
i.e. it can adapt itself automatically to work with a host or a switch. The interface therefore works
with crossover and straight cables.
The following media types are supported:
Table 18: Ethernet media types

IEEE Standard Distance Media Type
10BASE-T 100m Category 5 SF/UTP or better
100BASE-TX 100m Category 5 SF/UTP or better
1000BASE-T 100m Category 6 SF/STP or better
Please note:
The latching clips of the connectors must be positioned to the left to insert the con-
nector correctly.
Please note:
The Ethernet cables can be ordered directly from Hitachi Energy.
For details on available Ethernet cables, please refer to [1KHW002498] Product Guide “FOX61x
cables”.
4.5.6 Y-Adapter Type V9PK

The Y-Adapter is used for the 48 x E12 connections on SAMO3.
The E1 port connecting cables from the SAMO3 Main and Standby will be connected to two Y-
Adapters. The Common cables from the Y-Adapters will be routed to the customer equipment,
e.g. Krone LSA-PLUS Connector (E12 120 Ω) with the V9PN cable, or to the E1 Patch panel
BNC (E12 75 Ω) with the V9PQ cable.

SAMO3 Main Common Standby SAMO3
Port 25 to 48
Port 25 to 48
V9PK
V9PR V9PR
V9PR or V9PQ
Main Common Standby

Port 1 to 24
Port 1 to 24
V9PK
V9PQ V9PQ
V9PR or V9PQ
Figure 17: SAMO3 connected to Y-adapters V9PK
Table 19: V9PK adapter and required cables

Material Ordering description Ordering number
Y-Adapter V9PK*Y-ADAPTER C96M DRM 1KHW003339R0001
Cable SAMO3 lower position (Port V9PQ*SAMO_LY 1KHW028396R0020 (2 m) 1
1 to 24) to the Y-Adapter CABLE VOICE/DATA 48CH OE 1KHW028396R0030 (3 m)
Cable SAMO3 upper position V9PR*SAMO_UY 1KHW028397R0020 (2 m) 1
(Port 25 to 48) to the Y-Adapter CABLE VOICE/DATA 48CH OE 1KHW028397R0030 (3 m)
Cable from the Y-Adapter to the V9PN*SAMO_L 1KHW028394R0030 (3 m)
customer equipment (E12 120 Ω) CABLE VOICE/DATA 48CH OE 1KHW028394R0050 (5 m)
1KHW028394R0100 (10 m)
1KHW028394R0200 (20 m)
Cable from the Y-Adapter to the V9PQ see above
E1 Patch Panel BNC (E12 75 Ω)
E1 Patch Panel BNC (E12 75 Ω) Will be available 2Q2018
1. as short as possible
Table 20: Y-Adapter technical data

Feature Rating
Width 93 mm
Length 188 mm
Depth 102 mm

Table 20: Y-Adapter technical data

Feature Rating
Weight 450 gram
Connector male type C according to DIN 41612
Number of pins 96
The Y-Adapter is halogen free, RoHS and REACh compliant.

Mounting location is on a DIN Rail according EN 50022 on the cabinet wall or in a 19" Rack
(e.g. R9AN). The position can be turned by 90 degrees by unscrewing (Torx T10) the DIN Rail
holder.
Mounting accessories: Locking latch for the C96 connector, cable tie and shield clamp.
Normal mounting position Normal mounting position 90 degree turned mounting position
front view back view back view
Figure 18: Mounting of the Y-adapter
4.5.7 Fixing the Cables to the Cable Tray

The optical or electrical cables must be attached to the cable tray of the FOX615 R2 and
FOX615 or the corresponding device of the FOX612.
The open cable shields (electrical cables only) must be in contact with the FOX61x grounding
bar.
The figure below shows the cable/cable tray assembly of the FOX615 R2 and FOX615. For
additional information refer to [1KHW002461] Installation Instruction “FOX615 R2 and FOX615
Installation”.
With the FOX612 the cable tray functionality is implemented differently and depends on the type
of installation (rack-, wall-mounted). For more information on fixing the cables with the FOX612
refer to [1KHW002462] Installation Instruction “FOX612 Installation”.
The 19-inch adapter of the FOX611 provides no cable tray. For more information on fixing the
cables with the FOX611 refer to [1KHW029142] Installation Instruction “FOX611 Installation”.

<x> mm
120 mm
120 mm
<x> mm
120 mm
Figure 19: Side view of the FOX615 R2 and FOX615 cable tray and cables
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.

FOX61x | SAMO2, SAMO3, SAMO5 FUNCTIONAL DESCRIPTION
5 Functional Description
This section gives the detailed functional description of the SAMOx unit as an SDH terminal
multiplexer and add/drop multiplexer in the FOX61x subrack.
5.1 Applications
The main applications with the SAMOx unit are
• SAMOx as SDH terminal multiplexer with SDH, PDH and Ethernet tributaries.
• SAMOx as SDH add/drop multiplexer with SDH, PDH and Ethernet tributaries.
This section presents some application examples implemented with the SAMOx unit.
Please note:
All examples show the application with the SAMO3 unit.
→ When using the SAMO2 unit instead no E12 front ports are available.
→ When using the SAMO5 unit instead no E12 front ports are available and the
maximum SDH port speed is STM-4.
5.1.1 SDH Terminal Multiplexer Unprotected
SDH
access
network
STM-16 /
Network side STM-4
FOX61x
SAMOx
GbE star PBUS
GbE star Core Unit PDH units
IP service
units
Ethernet 4x 2x 48 x E12
Ethernet STM-4 / E12 Data
STM-1 1x Voice
Tributary side STM-16 / DSL TDM
STM-4
FOX61x Switch
Figure 20: SDH terminal multiplexer, unprotected
An SDH terminal multiplexer with an unprotected STM-16 or STM-4 uplink can be implemented
with one SAMOx unit.
The SAMOx unit offers three SDH tributary ports, one STM-16 or STM-4 and two STM-4 or
STM-1.
The Ethernet traffic is connected to the SAMOx unit via cables connecting the front interfaces,
or via the GbE star as part of the FOX61x Switch. Refer also to section 5.1.4 Ethernet over an
SDH Terminal Multiplexer (on page 49).

5.1.2 SDH Terminal Multiplexer with MSP Protection
SDH
access
network
STM-16 / STM-16 /
Network side STM-4 STM-4
FOX61x
SAMOx
GbE star PBUS
GbE star Core Unit PDH units
IP service
units
Tributary side STM-1 Voice
DSL TDM
FOX61x Switch
Figure 21: SDH terminal multiplexer, MSP protected
An SDH terminal multiplexer with MSP protected STM-16 or STM-4 uplinks can be implemented
The SAMOx unit offers two STM-4 or STM-1 tributary ports. These ports can be handled
• as two independent tributary ports or
• as subtending ring ports or
• as one MSP protected STM-4 or STM-1 tributary.
SDH Terminal Multiplexer (on page 49).

5.1.3 SDH Terminal Multiplexer with MSP and Equipment Protection
SDH
access
network
STM-16 / STM-16 /
STM-4 STM-16 / STM-4
STM-4 /
Network side STM-1
FOX61x SAMOx working SAMOx protecting
GbE star highZ GbE star
GbE star Core Unit
PBUS
IP service
units PDH units
Ethernet 1x 4x 48 x E12 48 x 1x 4x
STM-16 / Ethernet E12 Data E12 STM-16 / Ethernet
STM-4 2x Voice STM-4 2x
Tributary side STM-4 / DSL TDM STM-4 /
STM-1 STM-1
FOX61x Switch
Figure 22: SDH terminal multiplexer, MSP protected
An SDH terminal multiplexer with MSP protected STM-16 or STM-4 uplinks can be implemented
with two SAMOx units, operating as equipment protection pair. Both SAMOx units have one
SDH port active towards the network side. The traffic processing, i.e. SDH termination, access
to the PBUS, access to the E12 front interfaces (SAMO3 only) and the access to the Ethernet
front interfaces takes place on the working SAMOx unit.
Please note:
MSP over two SAMOx units not operating as equipment protection pair is not sup-
ported.
The other SDH ports on both SAMOx units remain operational, i.e. two STM-16 or STM-4 ports
and four STM-4 or STM-1 ports. These ports can be handled
• as six independent tributary ports or
• as MSP protected STM-16 or STM-4 or STM-1 tributaries.
The E12 PDH traffic is connected to the working and protecting SAMOx units via cables con-
necting the front interfaces in parallel (SAMO3 only).
The Ethernet traffic is connected to the working and protecting SAMOx units via cables connect-
ing the front interfaces, or via the GbE star as part of the FOX61x Switch. Refer also to section
5.1.4 Ethernet over an SDH Terminal Multiplexer (on page 49).
5.1.4 Ethernet over an SDH Terminal Multiplexer
5.1.4.1 Ethernet over SDH, Unswitched Transport Mode

In the unswitched transport mode the Ethernet traffic from an Ethernet port on the SAMOx unit
is transported in SDH networks using the EoS (Ethernet over SDH) approach providing point to

point Ethernet connections. Ethernet traffic is transported in virtually concatenated VC-4, VC-3
or VC-12.
The Ethernet traffic from an Ethernet device is connected to the SAMOx unit via cables connect-
ing the Ethernet front interfaces using the unswitched mode.
SDH
access
network
STM-16 /
STM-4
FOX61x eos-1 SAMOx
port-5 port-6 port-7 por t-8

Core Unit
Figure 23: EoS without SAMOx EQP, unswitched mode
When using SAMOx equipment protection, the Ethernet traffic from an Ethernet device is con-
nected to both SAMOx units via cables. This requires two Ethernet ports on the Ethernet device.
Alternatively an Ethernet switch can be used to connect both SAMOx ports to one Ethernet front
port on the Ethernet device.
The Ethernet device Ethernet ports may have RSTP disabled since the EoS transport on a
standby SAMOx unit is not active.
SDH SDH
access access
network network
STM-16 / STM-16 / STM-16 / STM-16 /

STM-4 STM-4 STM-4 STM-4
active standby active standby
FOX61x FOX61x
e-1 SAMOx e-1 SAMOx e-1 SAMOx e-1 SAMOx
p-5 p-6 p-7 p-8 p-5 p-6 p-7 p-8 p-5 p-6 p-7 p-8 p-5 p-6 p-7 p-8
Core Unit Core Unit
p-x = Ethernet port-x

e-x = EoS group eos-x
Figure 24: EoS with SAMOx EQP, unswitched mode

5.1.4.2 Ethernet over SDH, Switched Transport Mode

The Ethernet over SDH, switched transport mode, makes use of the VLAN Bridge function of
the FOX61x.
In the switched transport mode there are no dedicated EoS ports reserved for the SAMOx front
ports. All EoS ports are used as external ports of the FOX61x Switch, i.e. the Ethernet switch
device on the SAMOx unit participates in the FOX61x Switch.
The Ethernet traffic from any FOX61x Ethernet port participating in the FOX61x Switch is con-
nected to the SAMOx unit via the GbE star.
When using core unit equipment protection, also the Ethernet switch device on the redundant
core unit is part of the FOX61x Switch. The core unit redundancy is handled by the network ele-
ment control processes. The EoS application requires no redundancy specific configuration.
SDH SDH
access access
network network
STM-16 / STM-16 /
STM-4 STM-4
FOX61x eos-9 SAMOx FOX61x eos-9 SAMOx
Ethernet Switch Ethernet Switch
star-1 por t-5 port-6 port-7 port-8 star-1 star-2 port-5 por t-6 port-7 port-8
GbE star GbE star GbE star

Core Core Core
Unit Unit Unit
FOX61x Switch
Figure 25: EoS, switched mode
When using SAMOx equipment protection, also the redundant SAMOx is part of the FOX61x
Switch, the Ethernet front ports on the active and on the standby SAMOx unit are active. The
EoS transport is only operational on the active SAMOx unit and disabled on the standby SAMOx
unit.
Please note:
The two EoS ports on the working and the protecting SAMOx units are both
attached to the FOX61x Switch. One EoS port is active, the other is standby, but
both EoS ports are available as bridge ports in the FOXCST “Switching” view.
→ The bridge port configuration (port mode, PVID, VLANs, …) must be configured
identically for both ports.
→ The SAMOx supports the automatic adjustment of the configuration on both
units of an EQP group. See section 8.2.1.1 AP: / unit-x, Overview - Redundancy
Support (on page 146).
Please note:
When connecting an Ethernet device via two FOX61x Switch ports as shown in
Figure 25 and Figure 26 on the right side, “meshed” VPLS pseudo wires must be
configured to avoid a packet loop or xSTP must be enabled to avoid a packet loop.

SDH SDH
access access
network network
STM-16 / STM-16 /
STM-16 / STM-16 / STM-4 STM-4
STM-4 STM-4
active standby act ive standby
FOX61x e-9 SAMOx e-9 SAMOx FOX61x e-9 SAMOx e-9 SAMOx
Ethernet Switch Ethernet Switch Ethernet Swit ch Ethernet Swit ch
s-1 p-5 p-6 p-7 p-8 s-1 p-5 p-6 p-7 p-8 s-1 s-2 p-5 p-6 p-7 p-8 s-1 s-2 p-5 p-6 p-7 p-8
GbE star GbE star GbE star GbE star GbE star GbE star
Core Core Core
Unit Unit Unit
FOX61x Switch
s-x = GbE star-x
Figure 26: EoS with SAMOx EQP, switched mode
5.1.5 SDH Add/Drop Multiplexer
SDH SDH
access access
network network
STM-16 / STM-16 /
STM-4 STM-4
Network side west east
FOX61x SAMOx
GbE star PBUS

Core
GbE star PDH units
Unit
IP service
units switched or
unswit ched
Tributary side STM-1 Voice
DSL TDM
FOX61x Switch
Figure 27: SDH add/drop multiplexer, unprotected
An SDH add/drop multiplexer with unprotected STM-16 or STM-4 uplinks can be implemented
The SAMOx unit offers two STM-4 or STM-1 tributary ports. These ports can be handled

• as two independent tributary ports or

• as one MSP protected STM-4 or STM-1 tributary.
This application offers subnetwork connection protection (SNCP) on the VC-4, VC-3 and VC-12
layers.
This application offers also subnetwork connection protection (SNCP) with bidirectional switch-
ing type for the VC-12 signals terminated to the PBUS.
SDH add/drop Multiplexer (on page 56).
5.1.6 SDH Add/Drop Multiplexer with MSP Protection
SDH SDH
access access
network network

west west east east
protecting working working protecting
Network side
FOX61x SAMOx
GbE star PBUS

Core
GbE star PDH units
Unit
IP service
units switched or
unswit ched
Ethernet 4x 48 x E12
Ethernet E12 Data
Tributary side Voice
DSL TDM
FOX61x Switch
Figure 28: SDH add/drop multiplexer, MSP protected
An SDH add/drop multiplexer with MSP protected STM-4 uplinks can be implemented with one
SAMOx unit. STM-16 and STM-1 interfaces cannot be supported in this scenario.
The SAMOx unit supports no SDH tributary ports.
This application offers subnetwork connection protection (SNCP) on the VC-4, VC-3 and VC-12
layers.
This application offers also subnetwork connection protection (SNCP) with bidirectional switch-
ing type for the VC-12 signals terminated to the PBUS.
SDH add/drop Multiplexer (on page 56).

5.1.7 SDH Add/Drop Multiplexer with Equipment Protection
SDH SDH
access access
network network
STM-16 / STM-16 /
STM-4 STM-16 / STM-4
west STM-4 / east
Network side STM-1
FOX61x SAMOx active SAMOx standby
GbE star highZ GbE star

Core
GbE star
Unit
PBUS
IP service
units PDH units
Tributary side STM-4 2x Voice STM-4 2x
STM-4 / DSL TDM STM-4 /
STM-1 STM-1
FOX61x Switch
Figure 29: SDH add/drop multiplexer, EQP protected
An SDH add/drop multiplexer with equipment protection (EQP) and unprotected STM-16 or
STM-4 uplinks can be implemented with two SAMOx units, operating as equipment protection
pair. Both SAMOx units have one SDH port active towards the network side. The traffic process-
ing, i.e. SDH termination, access to the PBUS, access to the E12 front interfaces (SAMO3 only)
and the access to the Ethernet front interfaces takes place on the working SAMOx unit.
The other SDH ports on both SAMOx units remain operational, i.e. two STM-16 or STM-4 ports
and four STM-4 or STM-1 ports. These ports can be handled
• as six independent tributary ports or
• as MSP protected STM-16 or STM-4 or STM-1 tributaries.
Please note:
ported.
The E12 PDH traffic is connected to the working and protecting SAMO3 units via cables con-
5.1.9 Ethernet over an SDH add/drop Multiplexer (on page 56).

5.1.8 SDH Add/Drop Multiplexer with MSP and Equipment Protection
SDH SDH
access access
network network
STM-16 / STM-16 / STM-16 / STM-16 /

west west east east
working protecting protecting working
Network side
FOX61x SAMOx active SAMOx standby
STM-16 /
GbE star STM-4 /
highZ GbE star
STM-1
Core
GbE star
Unit
PBUS
IP service
units PDH units
Tributary side STM-1 Voice STM-1
DSL TDM
FOX61x Switch
Figure 30: SDH add/drop multiplexer, EQP protected
An SDH add/drop multiplexer with equipment protection (EQP) and multiplex section protected
STM-16 or STM-4 uplinks can be implemented with two SAMOx units, operating as equipment
protection pair. Both SAMOx units have two SDH ports active towards the network side. The
traffic processing, i.e. SDH termination, access to the PBUS, access to the E12 front interfaces
(SAMO3 only) and the access to the Ethernet front interfaces takes place on the working
SAMOx unit.
The other SDH ports on both SAMOx units remain operational, i.e. four STM-4 or STM-1 ports.
These ports can be handled
• as four independent tributary ports or
• as MSP protected STM-4 or STM-1 tributaries.
Please note:
ported.
The E12 PDH traffic is connected to the working and protecting SAMO3 units via cables con-
5.1.9 Ethernet over an SDH add/drop Multiplexer (on page 56).

5.1.9 Ethernet over an SDH add/drop Multiplexer
5.1.9.1 Ethernet over SDH, Unswitched Transport Mode

In the unswitched transport mode the Ethernet ports on the SAMOx unit provide point to point
Ethernet connections.
The Ethernet traffic from any Ethernet device uses two EoS ports, one for the west and one for
the east direction. The Ethernet traffic is connected to the SAMOx unit via cables connecting the
Ethernet front interfaces using the unswitched mode.
The Ethernet device Ethernet ports must have RSTP enabled to avoid a packet loop.
SDH SDH SDH SDH

access access access access
network network network network
STM-16 / STM-16 /
STM-16 / STM-16 /
STM-4 STM-4
STM-4 STM-4
west east
west east
active active standby standby
west east west east
FOX61x eos-1 eos-2
SAMOx
FOX61x e-1 e-2 e-1 e-2
SAMOx SAMOx
Core port-5 por t-6 port-7 port-8
Unit p-5 p-6 p-7 p-8 p-5 p-6 p-7 p-8
Core Unit

Figure 31: EoS with and without SAMOx EQP, unswitched mode
5.1.9.2 Ethernet over SDH, Switched Transport Mode

In the switched transport mode there are no dedicated EoS ports reserved for the SAMOx front
ports. All EoS ports are used as external ports of the FOX61x Switch, i.e. the Ethernet switch
device on the SAMOx unit participates in the FOX61x Switch.
The EoS ports must have RSTP enabled to avoid a packet loop.
The Ethernet traffic from any FOX61x Ethernet port participating in the FOX61x Switch is con-
nected to the SAMOx unit via the GbE star.

SDH SDH SDH SDH

access access access access
network network network network
STM-16 / STM-16 / STM-16 / STM-16 /

west east west east
active active standby standby
west east west east
FOX61x FOX61x SAMOx

eos-9 eos-10
SAMOx e-9 e-10 e-9 e-10
SAMOx
Ethernet Swit ch Ethernet Swit ch Et hernet Switch
star-1 port-5 port-6 por t-7 por t-8 s-1 p-5 p-6 p-7 p-8 s-1 p-5 p-6 p-7 p-8
GbE star GbE star GbE star

Core Core
Unit Unit
FOX61x Switch
p-x = Et hernet port-x

s-x = GbE star-x
Figure 32: EoS with and without SAMOx EQP, switched mode
5.1.10 MPLS-TP Transport with VPWS
FOX61x
por t-5
Et hernet Switch
Core Unit
GbE star
por t-8
Pseudo
star-1
Wire MPLS-TP
MPLS
eos-1 Tunnel LSP Network
Port
SDH
access eos-12
SAMOx
network
Figure 33: MPLS-TP VPWS Transport function with SAMOx and core unit
With the MPLS-TP Transport function of the FOX61x the SAMOx Ethernet front ports and the
EoS ports can be used as PWAC ports of a Virtual Private Wire Service (VPWS).
In the switched mode of the Ethernet front ports the EoS ports eos-1 to eos-12 are available.
In the unswitched mode of the Ethernet front ports the EoS ports eos-5 to eos-12 are available.
EoS traffic can be SNC protected on the VC-4, VC-3 and VC-12 layers.
Please note:
A SAMOx Ethernet front port or EoS port used for the MPLS-TP VPWS Transport
function is no longer available for the VLAN Bridge function.
For detailed information about the MPLS-TP application with FOX61x please refer to
[1KHW028618] User Manual “MPLS-TP Services”.

5.1.11 MPLS-TP Transport with VPLS
FOX61x
por t-5
Core Unit
Ethernet Switch
GbE star
Et hernet Swit ch
por t-8 Pseudo
SVI MPLS
Tunnel
star-1 VPLS Wire MPLS-TP
LSP Network
eos-1 Port
SAMOx
SDH
access eos-32
network
Pseudo
MPLS
Tunnel
Wire MPLS-TP
LSP
Port Network
FOX61x Switch
Figure 34: MPLS-TP VPLS Transport function with SAMOx and core unit
With the MPLS-TP Transport function of the FOX61x the SAMOx Ethernet front ports and the
EoS ports can be used as CVP ports of a Virtual Private LAN Service (VPLS). The CVP ports of
the SAMOx unit and the SVI (Switch Virtual Interface) of the VPLS are attached to the FOX61x
Switch, using the VLAN Bridge application.
In the switched mode of the Ethernet front ports the EoS ports eos-1 to eos-32 are available.
In the unswitched mode of the Ethernet front ports the EoS ports eos-5 to eos-32 are available.
EoS traffic can be SNC protected on the VC-4, VC-3 and VC-12 layers.
For detailed information about the MPLS-TP application with FOX61x please refer to
[1KHW028618] User Manual “MPLS-TP Services”.
5.2 SDH Multiplexing

The multiplexing structure implemented in SAMOx and supported in FOX61x is a subset of the
complete multiplexing structure defined in ITU-T G.707.
SAMOx provides the multiplexing functions for VC-12, VC-3 and VC-4 as depicted in the figure
below.
Please note:
The SAMO5 supports no STM-16.
x1
STM-16 AUG-16
x4
x1
STM-4 AUG-4
x4 x1
x1
STM-1 AUG-1 AU-4 VC-4 C-4
x3
x1
Pointer processing TUG-3 TU-3 VC-3 C-3
Multiplexing x7 x3
Aligning TUG-2 TU-12 VC-12 C-12
Mapping
Figure 35: Multiplexing structure supported in SAMOx

SAMO5 supports STM-4 SAMOx

instead of STM-16
Redundancy Switch
AUG-16 AUG-16 AUG-16 AUG-16

x4 x4 x4 x4
AUG-4
AUG-4 AUG-4
AUG-4 AUG-4
AUG-4 AUG-4
AUG-4
AUG-4 AUG-4 AUG-4
AUG-4 AUG-4
AUG-4 AUG-4
AUG-4
x4 x4 x4 x4 x4 x4 x4 x4
AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1
AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1 AUG-1
AUG-1
AU-4 AU-4 AU-4 AU-4 AU-4 AU-4 AU-4 AU-4

x4 x4 x 16 x 16 x4 x4 x 16 x 16
AU-4 Cross Connect
x 12 x 31
VC-4 VC-4
x3
TUG-3
TUG-3 2x 40x AU-4
TUG-3
connection to the
x7
redundant
TUG-2
TUG-2
TUG-2
SAMOx unit
TUG-2
TUG-2
TUG-2
TUG-2
x3
TU-12
TU-12
TU-3 TU-12
x 48 x 945
TU-3 Cross Connect TU-12 Cross Connect
x 24 x 252 x 64 x 48
VC-3 VC-12 VC-12 VC-12
VCAT / GFP / MAC / ETH C-12 C-12

2x 1GbE
8x 100MbE
Ethernet Switch P-12 P-12
x4 x2 x2 x 64 x 48
(only 1 active) (only 1 active) SAMO3
10/100/1000
BASE-T only
Ethernet E12
10Gb Ethernet 1Gb Ethernet PBUS REDUN
Figure 36: SDH multiplexing with SAMOx
The functional blocks implemented in the SAMOx unit are shown in the Figure 36. The figure
shows also the numbers of available functional blocks, e.g. the number of TU-12 processing
blocks is
15 (VC-4) x 3 (TUG-3) x 7 (TUG-2) x 3 (TU-12) = 945.
The AU-4, TU-3 and TU-12 cross connects are non blocking, i.e. arbitrary cross connections
between all inputs and outputs are allowed.

Please note:
The VC-3 EoS application uses the TU-3 cross connect. Each EoS VC-3 requires
therefore two TU-3 resources in the cross connect, one for the connection towards
the front interface and one for the connection towards the EoS application.
→ This limits the VC-3 EoS capacity to 24 x VC-3.
→ The TU-3 cross connect capacity must be shared between the EoS application
and the cross connected VC-3 in an add/drop multiplexer application.
The two 40x AU-4 signals at the redundancy switch connect two SAMOx units, operating as
equipment protection pair.
The STM-16, STM-4 and STM-1 output signals are frequency locked to the SETS (Synchronous
Equipment Timing Source) timing.
5.3 PDH Layers and Functions
5.3.1 E12 Layer (SAMO3 only)

The E12 layer is used for the E12 front ports. It provides the following functions:
• Termination of the electrical 2048 kbit/s signal.
− Receive signal regeneration
− Clock and data recovery
− HDB3 coder and decoder
− Jitter attenuation in transmit direction
The SAMO3 unit offers maintenance loops at the E12 layer.
5.3.2 P12 Layer

The P12 layer of the SAMOx unit is used for the 48 E12 front ports and for the PBUS access of
up to 64 P12 signals. SAMOx supports the asynchronous mapping of the P12 to the VC-12.
The P12 mode controls the P12 signal structure, the mapping on the FOX61x internal TDM bus
(PBUS), the synchronization and the handling of the time slot 0 Sa-bits:
• Terminated (P12 mode: PCM30, PCM30C, PCM31, PCM31C, V5 Uplink, V5 Uplink NCI)
The time slot 0 of the P12 signal is analyzed in the receive direction (from the network inter-
face) and regenerated in the transmit direction.
Cross connection and protection switching (P0-nc SNCP) is established on the P0-nc (n x 64
kbit/s) traffic signal level.
For terminated signals the following functions are available:
− CAS (PCM30, PCM30C)
Support of channel associated signaling in time slot 16.
− CRC4 (PCM30C, PCM31C)
Generation and evaluation of the CRC4 code in time slot 0.
• Transparent P12 mode:
The P12 signal has an unknown structure.
Cross connection and protection switching is established on the P12 (2 Mbit/s) traffic signal
level.
Please note:
The transparent mode features clock transparent cross connections. That means
that the signal is in a plesiochronous phase relationship with the NE timing source.

• Clock master
Unlike the transparent mode, a clock master traffic signal is only cross connected transpar-
ently in terms of its structure. The P12 output signal is always resynchronized by the NE tim-
ing source. The input signal must be synchronous to the output signal in order to avoid bit
slips.
For details of the clock master mode, please refer to [1KHW002467] User Manual “TDM Ser-
vices”.
• V5.x applications (P12 mode: V5 Uplink, V5 Uplink NCI)
The V5.x applications will be available in a future release.
Please note:
The E12 front ports of the SAMO3 unit only support the “transparent” mode.
The spare bits Sa4 to Sa8 to be transmitted in the time slot 0 can be configured. In case one of
the spare bits is used for the synchronization (SSI or SSM), the Sa bit configuration of this spare
bit is ignored.
Please note:
The V5 application uses the Sa7 spare bit of time slot 0 for the link identification
control.
→ The configuration of the Sa7 spare bit is ignored.
Please note:
The Sa4 to Sa8 spare bit configuration is not applicable for the transparent trans-
port modes.
→ The configuration of the spare bits is ignored.
The SAMOx unit offers maintenance loops at the P12 and P0-nc layer.
5.4 Ethernet Layers and Functions
5.4.1 Ethernet Front Interfaces

SAMOx offers four electrical 10/100/1000BASE-T Ethernet interfaces.
5.4.1.1 LAN Mode

The LAN mode can be configured to a fixed link speed or to autonegotiation. Full duplex mode
is supported with 10, 100 and 1000BASE-T, half duplex mode is supported with 10 and
100BASE-T.
The Ethernet ports support auto-negotiation with parallel detection. Auto-negotiation provides
the automatic selection of the highest performance mode on a given link.

Be aware that when connecting Ethernet ports configured in manual mode (no
auto-negotiation) to Ethernet ports in auto-negotiation mode, the following situation
may occur:
The link will be up but the duplex settings may be inconsistent and this can result
on poor throughput performance on the link.
The previous note applies to any Ethernet device and is a consequence of the behavior of auto-
negotiation and parallel detection. When a port supporting auto-negotiation is connected to a
port not supporting auto-negotiation, the port supporting auto-negotiation will revert to parallel
detection. This can detect the link type (e.g. 10BASE-T or 100BASE-TX) but will assume half-
duplex operation (reference IEEE 802.3 clause 28.2.3.1 note 2). If the far side port is manually
configured in full-duplex mode then there is an inconsistent configuration and the side operating
in half-duplex may experience collisions while transmitting data.

5.4.1.2 IEEE 802.3 Flow Control

The Ethernet functional layer allows using IEEE 802.3x flow control.
Flow control is a mechanism which allows inhibiting transmission of data frames for a specified
period of time. This is normally used when the receive data buffer is almost full. This state is
indicated to the transmitter to stop the transmission of frames for the specified period of time.
In half-duplex mode SAMOx supports collision-based congestion control. This operates inde-
pendently of the setting of the 802.3 flow control configuration parameter in the FOXCST.
Please note:
The flow control feature is only available for the EoS ports in the EPL (unswitched)
mode.
5.4.1.3 Link Pass Through

SAMOx also provides the “link pass through” feature. This feature can bring the local link state
(up or down) to the remote Ethernet interface. If the local link state is down SAMOx will gener-
ate GFP client signal fail management frames going to the remote site. A failure in the SDH path
will interrupt the GFP connection.
If the GFP receiver on the remote site will receive GFP client signal fail management frames or
no GFP frames at all, it will set the Ethernet interface to the down state accordingly.
With this feature the Ethernet transport is transparent also for link states.
Please note:
The link pass through feature must be enabled on the Ethernet interfaces at both
sides of the SDH path to become operational.
Please note:
The link pass through feature is only available for the EoS ports in the EPL
(unswitched) mode.
5.4.2 Ethernet Internal Interfaces

SAMOx has a connection via the Gb Ethernet star in the FOX61x backplane to the active and to
the redundant core units. These connections are internal connections of the FOX61x Switch.
Please note:
Only the backplane connection to the active core unit is used.
→ The backplane connection to the standby core unit is not used.

2x STM-16 / STM-4
2x STM-4 / STM-1
SAMOx
eos-1 eos-2 eos-3 ... eos-32
EoS
32 groups
2x 1GbE
8x 100MbE
Ethernet Switch
por t-5 por t-6 por t-7 port-8 slot-11 slot-11-1 slot-13 slot-13-1
10GbE star 1GbE star 10GbE star 1GbE star
Core Core FOX61x

Unit Unit
4x
10/100/1000-BASE-T
Figure 37: Ethernet internal interfaces
Please note:
Figure 37 shows the switched port mode for the EoS ports.
→ Refer to section 5.4.3.2 Switched Port Mode (on page 66).
5.4.3 Ethernet Switch

The Ethernet switch device on the SAMOx unit participates in the FOX61x Switch. The Ethernet
front ports can be configured to bypass the VLAN bridge.
With the VLAN Bridge function the Ethernet front ports and the EoS ports support up to three
operation modes:
• Unswitched mode (see section 5.4.3.1):
In the unswitched mode the Ethernet traffic from an Ethernet front port is directly connected
to an EoS port. The Ethernet front port and the EoS port are not part of the FOX61x Switch.
• Switched mode (see section 5.4.3.2):
In the switched mode the Ethernet traffic from an Ethernet front port and from an EoS port
accesses the FOX61x Switch. The Ethernet front port and the EoS port are handled as any
other port of the FOX61x Switch.
• Expansion mode (see section 5.4.3.3) (SAMO2 and SAMO3 only):
An EoS port eos-9 to eos-12 in the expansion mode provides five additional EoS ports to be
used as FOX61x Switch ports. The feature set of an EoS expansion port is reduced com-
pared with a normal EoS switched port.
The availability of the different port modes for the Ethernet front ports and the EoS ports is as
follows:

Table 21: Available port modes

Port Mode
Unswitched Switched Expansion
port-5: Ethernet yes yes no
port-6: Ethernet
port-7: Ethernet
port-8: Ethernet
eos-1
eos-2
eos-3
eos-4
eos-5 no yes
eos-6 (SAMO2 and
SAMO3 only)
eos-7
eos-8
eos-9 yes yes yes
eos-10 (SAMO2 and
SAMO3 only)
eos-11 no
eos-12
eos-13 to eos-32 no no yes
(SAMO2 and
SAMO3 only)
Please note:
Without using expansion ports the number of usable EoS ports is limited to 12.
→ Refer to section 5.4.3.3 Expansion Port Mode (SAMO2 and SAMO3 only) (on
page 67).
Please note:
The switched, unswitched or expansion port mode is configurable individually per
Ethernet port and EoS port, respecting the port mode availability listed in Table 21.
5.4.3.1 Unswitched Port Mode

The unswitched mode connects an Ethernet front port directly to the corresponding EoS port,
bypassing the VLAN bridge. This corresponds to the EPL (Ethernet Private Line) application.
The following point-to-point connections are available:
Table 22: Unswitched port mode

Ports connected EoS Band- QoS Restrictions
Ethernet Eos width
port-5 eos-1 100 Mbit/s Flow control, Scheduling none
port-5 eos-9 1000 Mbit/s Flow control, Scheduling If eos-9 is used in the unswitched port
mode the following EoS ports are not
usable, i.e. are not available for user traf-
fic:
eos-11, eos-13 to eos-17, eos-23 to eos-27.

Table 22: Unswitched port mode (continued)

Ports connected EoS Band- QoS Restrictions
Ethernet Eos width
port-6 eos-10 1000 Mbit/s Flow control, Scheduling If eos-10 is used in the unswitched port
mode the following EoS ports are not
usable, i.e. are not available for user traf-
fic:
eos-12, eos-18 to eos-22, eos-28 to eos-
32.
Please note:
In the FOXCST “Tree View” tab the Ethernet front port and the corresponding EoS
port must be configured to the “CVP” port type.
→ Otherwise the ports do not appear in the FOXCST “Switching” tab.
Please note:
The EoS ports of a standby SAMOx unit can only be configured to the “CVP” port
type on the NE level.
→ Navigate to the AP: /ne, Main - Port Type.
Please note:
In the FOXCST “Switching” tab the Ethernet front port and the corresponding EoS
port must be configured to the “unswitched” port mode before the EPL mode can
be enabled for the ports.
→ When using the EoS port eos-9 in the “unswitched” port mode also the EoS port
eos-11 must be configured to the “unswitched” port mode before the EPL mode
can be enabled.
→ When using the EoS port eos-10 in the “unswitched” port mode also the EoS
port eos-12 must be configured to the “unswitched” port mode before the EPL
mode can be enabled.
All Ethernet ports and EoS ports not configured for the unswitched port mode operate in the
switched or expansion port mode, accessing the VLAN bridge. Refer to section 5.4.3.2 Switched
Port Mode (on page 66) and section 5.4.3.3 Expansion Port Mode (SAMO2 and SAMO3 only)
(on page 67).
EoS EoS EoS EoS EoS EoS EoS EoS EoS EoS EoS EoS
eos-1 eos-9 eos-11 eos-2 eos-10 eos-12 eos-3 eos-4 eos-5 eos-6 eos-7 eos-8
100 Mb 1 Gb shared 100 Mb 1 Gb shared 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb
Ethernet Switch
2x 2x
10 Gb 1 Gb
or or 10/100/1000 10Gb Ethernet 1Gb Ethernet

BASE-T Ethernet Access Access
Eth Eth Eth Eth Eth Eth Backplane Connectors

port-5 port-5 port-6 port-6 port-7 port-8
FOX61x Switch
Figure 38: EoS and Ethernet switching in unswitched mode

Please note:
In Figure 38 the not usable expansion EoS ports eos-13 to eos-32 are not shown.
Please note:
In Figure 38 the EoS ports eos-5 to eos-8 are not available for the SAMO5 unit.
5.4.3.2 Switched Port Mode

The switched mode connects an Ethernet front port or an EoS port directly to the FOX61x
Switch.
The port can be used as VLAN bridge port (in the VLAN Bridge application) or as PWAC port
(for the MPLS-TP VPWS Transport application.
Table 23: Switched port mode

Port Bandwidth QoS Restrictions
port-5 10/100/1000 standard FOX61x Switch port none
Mbit/s
Mbit/s
Mbit/s
Mbit/s
eos-1 100 Mbit/s standard FOX61x Switch port none
eos-5 100 Mbit/s standard FOX61x Switch port none (SAMO2 and SAMO3 only)
eos-9 1000 Mbit/s standard FOX61x Switch port Bandwidth shared with eos-11

100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 1 Gb shared 1 Gb shared
Ethernet Switch
2x 2x
10 Gb 1 Gb
10/100/1000 10Gb Ethernet 1Gb Ethernet

Eth Eth Eth Eth Backplane Connectors

port-5 port-6 port-7 port-8
FOX61x Switch
Figure 39: EoS and Ethernet switching in switched mode
Please note:
In Figure 39 the EoS ports eos-9 to eos-12 are all configured to the switched port
mode.
→ The expansion EoS ports eos-13 to eos-32 are not usable and are not shown.
Please note:
In Figure 39 the EoS ports eos-5 to eos-8 are not available for the SAMO5 unit.
5.4.3.3 Expansion Port Mode (SAMO2 and SAMO3 only)

When one of the EoS ports eos-9 to eos-12 is configured to the expansion port mode it is called
“master expansion port”. Each master expansion port makes five additional EoS ports usable as
VLAN bridge ports. The master expansion port and the five additional EoS ports belong to one
expansion group, designated X1 to X4.
Even though all EoS ports of an expansion group access the VLAN bridge, only the master
expansion port is visible in the FOXCST “Switching” tab. In the “Switching” tab this master
expansion port has to be configured
• to the “trunk” port mode, or
• to the “general” port mode with “tagged” acceptable frame types and “tagged” egress frames.
All used VLAN IDs must be added to the VLAN membership table.
• The QoS configuration of the master expansion port is applied to all EoS ports of the expan-
sion group.

When using an additional expansion port, the master expansion port of this expan-
sion group must have an EoS group configured and must be in the administrative
state “Up”.
→ Otherwise the expansion ports of this expansion group will not be operational.
The VLAN configuration of all expansion group members is done on the SAMOx unit at the AP: /
unit-x/eos/eos-y - Configuration - Port Mode:
• Expansion mode frame type:

− Tagged:
Ingress frames must be tagged.
Egress frames are sent out tagged.
The usable VLAN IDs must be configured in the VLAN table.
The Port VLAN ID is not used.
− Untagged.
Ingress frames must be untagged and are tagged with the Port VLAN ID inside the FOX-
61x Switch.
Egress frames are sent out untagged, or with the outer VLAN tag removed.
The Port VLAN ID must be configured in the VLAN table.
• Port VLAN ID:
Only used for the untagged frame type.
• VLAN table:
− List of VLAN IDs for tagged and untagged traffic

The VLAN table of an expansion port can contain multiple VLAN IDs, but a VLAN
ID cannot be member of more than one EoS port of the same expansion group.

Expansion ports do not support RSTP, MSTP or ERPS.
→ When activating RSTP, MSTP or ERPS on a master expansion port unpredict-
able behavior will occur.
SAMOx FOX61x Switch

FOXCST “Tree View” FOXCST “Switching” view
AP: /unit-x/eos/eos-y, Configuration – Port Mode: Bridge Ports Bridge VLANs
Expansion EoS port: The frame type Master expansion EoS port: Add all VLANs to be used by
- Frame type configuration of the - Port mode: Trunk any of the expansion ports of
- Port VLAN ID expansion EoS port - QoS parameters the expansion group
- VLAN table controls if the Ethernet - Storm Control parameters
frames on the EoS
transport channel are
tagged or untagged Master expansion EoS port:
Add all VLANs to be - Port mode: General
used by the expansion - Acceptable frame types: Tagged
port The QoS and storm
- VLAN Configuration control parameters of the
Add all VLANs of the expansion group, master expansion EoS
Egress Frametype: Tagged Frames port are applied to all
- QoS parameters ports of the expansion
- Storm Control parameters group
Figure 40: Configuration parameters of an expansion EoS port
Table 24: Expansion port mode

Master expan- Expansion Expansion Bandwidth QoS
sion port group ports
eos-9 X1 eos-9 1000 Mbit/s, shared standard VLAN bridge port con-
eos-13 between eos9, eos-13 to eos-17, figuration of eos-9 is applied to
and eos-11, eos-9 and eos-13 to eos-17
eos-14 and eos-23 to eos-27 if expan-
eos-15 sion mode is used for eos-11.
eos-16
eos-17

Table 24: Expansion port mode (continued)

Master expan- Expansion Expansion Bandwidth QoS
sion port group ports
eos-18 between eos10, eos-18 to eos- figuration of eos-10 is applied
22, and eos-12, to eos-10 and eos-18 to eos-22
eos-21
eos-22
eos-23 between eos11, eos-23 to eos- figuration of eos-11 is applied to
27, and eos-9, eos-11 and eos-23 to eos-27
eos-26
eos-27
eos-28 between eos12, eos-28 to eos- figuration of eos-12 is applied to
32, and eos-10, eos-12 and eos-28 to eos-32
eos-31
eos-32

Master expansion port Expansion group X2 Master expansion port Expansion group X4
Master expansion port Expansion group X1 Master expansion port Expansion group X3
EoS EoS EoS EoS EoS EoS EoS EoS

eos-1 eos-2 eos-3 eos-4 eos-5 eos-6 eos-7 eos-8
100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 100 Mb 1 Gb shared 1 Gb shared
Ethernet Switch
2x 2x
10 Gb 1 Gb
10/100/1000 10Gb Ethernet 1Gb Ethernet

Eth Eth Eth Eth Backplane Connectors

port-5 port-6 port-7 port-8
FOX61x Switch
Expansion group
Figure 41: EoS and Ethernet switching in expansion mode
5.4.4 Ethernet over SDH (EoS)

SAMOx enables the interconnection of dispersed LANs through SDH networks by creating point
to point connections with “Ethernet over SDH” (EoS). SAMOx supports up to 32 EoS ports. EoS
ports accessing the VLAN bridge are handled as external ports of the VLAN bridge. Refer also
to section 5.4.3 Ethernet Switch (on page 63).
EoS transport is possible using the generic framing procedure (GFP) and virtual concatenation
(VCAT). The link capacity adjustment scheme (LCAS) allows an EoS group to remain opera-
tional also when one of the links fails. LCAS also provides the capability to manually add or
delete links to or from an EoS group.
The following sections present the main functions, features and protocols used by EoS.
5.4.4.1 Generic Framing Procedure (GFP)

The SAMOx unit implements GFP according to ITU-T G.7041. This recommendation defines the
required procedures for transporting variable length frames over SDH transport paths.
GFP provides a unified way to encapsulate and transport client signals instead of application
specific mapping protocols.
G.7041 defines two GFP modes of operation:
• Frame mapped GFP
A single client frame is mapped into a single GFP frame.

• Transparent GFP
A number of client data characters are mapped into efficient block codes for transport within
a GFP frame.
GFP supports two types of frames:
• Client frames
Client frames transport client data (client data frame) or management information (client
management frame).
• Control frames
Control frames are used as idle frames, i.e. when no client data has to be transported.
The basic signal structure of a GFP client frame is shown in the figure below. GFP frames are
octet aligned and consist of a GFP core header and a GFP payload area, i.e. a payload header
and a payload information field.
A GFP control frame consists of a core header only.
GFP frame
Payload Length
16 bit
Indicator
Core
Header
Core Header
16 bit
Error Check
PTI PFI EXI 8 bit
Type
Ethernet MAC frame Payload UPI 8 bit
Preamble Header
Type Header
16 bit
Start of frame Error Check
Destination Address
Source Address
Length / Type
Payload
Information
MAC client data up to 1600 octets
Field
Pad
Frame Check Sequence
Inter-Packet Gap
PTI: payload type identifier = 000 (client data)
= 100 (client management)
PFI: payload FCS identifier = 0 (no GFP FCS)
EXI: extension header identifier = 0000 (null extension header)
UPI: user payload identifier = 0000 0001 (frame mapped Ethernet)
Figure 42: Frame mapped GFP
SAMOx implements the following payload header type fields for client data:
Table 25: Payload header type fields

Field Value Description
PTI 000 Client data
PFI 0 No GFP frame check sequence (FCS)
EXI 0000 Null header extension
UPI 0000 0001 Frame mapped Ethernet
The payload information field contains the framed PDU. The client PDU is always transferred
into the GFP payload information field as an octet aligned packet stream.

The GFP payload contains the Ethernet MAC frame excluding the Ethernet “preamble” and
“start of frame” bytes but including the Ethernet FCS.
SAMOx implements the following payload header type fields for client management:
Table 26: Payload header type fields

Field Value Description
PTI 100 Client management
PFI 0 No GFP frame check sequence (FCS)
EXI 0000 Null header extension
UPI 0000 0001 Loss of client signal
0000 0010 Loss of client character synchronization
Client management frames are used to propagate a client signal fail (CSF) indication to the far
end. In case of a Link Down, the SAMOx generates client management GFP frames once every
100 – 150 ms. The GFP CSF condition will be cleared after 3 s, if no GFP CSF frames are
received, or upon receiving a valid GFP client data frame.
The GFP frame stream is mapped into a container-n or virtually concatenated container-n-Xv (n
= 12, 3, 4) with its byte boundaries aligned with the byte boundaries of the container. The con-
tainer is then mapped into the VC-n, or VC-n-Xv respectively, together with the associated path
overhead.
The GFP frame boundaries are thus aligned with the VC-n byte boundaries. Since the con-
tainer-n capacity is not an integer multiple of the variable length GFP frame, a GFP frame may
cross a container-n frame boundary.
GFP frames arrive as a continuous byte stream with a capacity that is identical to the VC pay-
load, due to the insertion of GFP idle frames at the GFP adaptation stage.
5.4.4.2 Virtual Concatenation (VCAT)

SAMOx provides 32 EoS groups (virtual concatenation groups, VCG groups) that can be used
for the transport of Ethernet traffic over SDH.
Each EoS group consists of a number of virtual channels, the members of this group. All mem-
bers of a group must be of the same VC type. The following group member types are supported:
Table 27: EoS group members

Member type Max. number of mem- Max. number of mem-
bers per group bers per unit
VC-12 63 252
VC-3 24 24
VC-4 12 12
The maximum available EoS capacity depends on the usage of VC-12 EoS members:
• No VC-12 EoS members used:
The VC-4 and VC-3 EoS members share a total capacity of 12 VC-4 equivalents.
• VC-12 EoS members used:
The VC-4, VC-3 and VC-12 EoS members share a total capacity of 12 VC-4 equivalents:
− Up to 8 VC-4 equivalents for VC-4 and VC-3 members,
− Up to 4 VC-4 equivalents for VC-12 members.
Please note:
The 48 x 48 TU-3 cross connect capacity of SAMOx must be shared for EoS VC-3
group members and through connected VC-3.
→ (Number of EoS VC-3) + (Number of through connected VC-3) ≤ 24

The members of an EoS group are virtually concatenated. Virtual concatenation allows trans-
porting more efficiently low capacity payloads which are unable to fill complete VC-3 or VC-4
signals. This is achieved by the concatenation of smaller signal containers (e.g. VC-12) with a
common destination. The aggregation of signal containers (members) is called a virtual concat-
enation group (VCG).
A GFP frame is split over all members of the virtual concatenation group. Each member of a
VCG can take a different path through the network. The VCG will be reassembled at the desti-
nation point. The reassembly buffer supports with an adaptive buffer a differential delay of up to
64 ms between virtual concatenated VCs. The maximum differential delay is configurable in the
range 0 ms to 64 ms.
Please note:
In case virtual concatenation is not used the maximum differential delay should be
set to 0 ms.
→ This minimizes the delay via the EoS path.
The following figure shows how frames are split over different VC belonging to the same VCG.
The VC is labeled with the frame counter and a sequence indicator which makes it possible to
reassemble the frames at the remote end.
Sequence Frame count

indicator
0 5 4 3 2 5 4 3 2
0
1 4 3 2 5 4 3 2 1
2
2 4 3 2 5 4 3 2
Frame split over each 3
link according to the
sequence indicators 3 4 3 2 1 5 4 3 2
VCG member Reassembly buffers

cope with the
differential delay
Figure 43: Virtual concatenation
The sequence indicator and the frame count are transported in the VC path overhead of every
virtual container.
Table 28: VCG frame counter and sequence indicator

VC Frame count Sequence indicator Transport
VC-4 0 … 4095 0 … 255 H4 byte
VC-3
VC-12 0 … 31 0 … 63 K4[2] byte
With VC-12 virtual concatenation the usable capacity is a multiple of 2’176 kbit/s 1, up to a maxi-
mum of 63 x 2’176 = 137’088 kbit/s.
With VC-3 virtual concatenation the usable capacity is a multiple of 48’384 kbit/s 1, up to a maxi-
mum of 24 x 48’384 = 1’161’216 kbit/s.
With VC-4 virtual concatenation the usable capacity is a multiple of 149’760 kbit/s 1, up to a
maximum of 12 x 149’760 = 1’797’120 kbit/s.
1. EoS full bandwidth, i.e. “Single Class Traffic” parameter is set to true.


Per default the traffic capacity of a virtual concatenation group is reduced by 15%
in the shaper of the SAMOx Ethernet bridge circuit.
→ In order to get the full available bandwidth of the virtual concatenation group set
the “Single Class Traffic” parameter of the EoS group to true. Refer to section
8.21.3.2 AP: / unit-x / eos / eos-y, Configuration - PHY (on page 268).
Table 29: Ethernet to VCG traffic allocation examples, full bandwidth

Ethernet Container types Number of VCG capacity VCG utiliza-
bandwidth containers tion 1
10 Mbit/s C-12 (2’176 kbit/s) 5 10.880 Mbit/s 92%
C-3 (48’384 kbit/s) 1 48.384 Mbit/s 20%
C-3 (48’384 kbit/s) 3 145.152 Mbit/s 69%
C-4 (149’760 kbit/ 1 149.760 Mbit/s 67%
s)
1000 Mbit/s C-4 (149’760 kbit/ 7 1’048.320 95%
s) Mbit/s
1. Calculated for the Ethernet bandwidth
Table 30: Ethernet to VCG traffic allocation examples, reduced bandwidth

Ethernet Container types Number of VCG capacity VCG utiliza-
bandwidth containers tion 1
C-3 (41’126 kbit/s) 1 41.126 Mbit/s 24%
C-3 (41’126 kbit/s) 3 123.378 Mbit/s 81%
C-4 (127’296 kbit/ 1 127’296 Mbit/s 78%
s)
1000 Mbit/s C-4 (127’296 kbit/ 8 1’018.368 Mbit/ 98%
s) s
1. Calculated for the Ethernet bandwidth
Please note:
The VCG groups are attached to EoS ports of the VLAN bridge or to a SAMOx
Ethernet front port, limiting the available bandwidth per EoS port to 100 Mbit/s for
eos-1 to eos-8 and 1000 Mbit/s for eos-9 plus eos-11 and eos-10 plus eos-12.
→ Please refer to section 5.4.3 Ethernet Switch (on page 63).
5.4.4.3 Link Capacity Adjustment Scheme (LCAS)

The link capacity adjustment scheme (LCAS) protocol is an addition to the virtual concatenation
process which allows you to use a variable number of virtual concatenated containers. This
means that the number of members in the VCG can be changed on demand of the user. The
LCAS protocol provides a synchronization and a handshake mechanism between the concate-
nation source and sink functions to allow a change in the group size without transmission hits.
LCAS uses control packets that are transmitted over the links in advance of a configuration
change so that the receiver can switch hitless to a new configuration. The different states of a
link can be seen in the VC status section.
Another function of the LCAS protocol is to autonomously remove members that experience
transmission failures or degraded transmission performance. This feature can be used to imple-
ment resilience by routing link members over different network routes.

Note further that there is no need to have an identical number of members in the two directions
of a bi-directional link, however there should be at least one member active in both directions.
The operation of LCAS is unidirectional which means that in order to add or remove members of
a VCG the operation has to be done at both ends. These actions are independent from each
other, do not require to be synchronized and have to be performed by the management system
(FOXCST or FOXMAN-UN).
It is possible to enable or disable LCAS in FOXCST.
FOXCST/
FOXMAN-UN
add/remove VCG
link request
VCG member
LCAS control packets
VCG member
VCG source VCG member VCG sink
Figure 44: LCAS operation
5.5 Embedded Communication Channel (ECC)

The embedded communication channel (ECC) of FOX61x provides an integrated communica-
tion structure for the management communication. The element manager accesses the ECC
normally via a management interface of the core unit. The ECC is transported via aggregate sig-
nals connecting the NEs.
SAMOx provides the DCC in the regenerator section overhead (3 x 64 kbit/s) and the multiplex
section overhead (9 x 64 kbit/s) for the ECC transport. The ECC is transported either via the
RSOH DCC or the MSOH DCC or via both DCC channels.
The ECC is connected via the PBUS to the core unit which provides the routing function. When
using the RSOH DCC and MSOH DCC of eight SDH ports the required bandwidth is 8 x (3 + 9)
= 96 time slots, occupying 4 P12 signals on the PBUS.
Please note:
The access to the RS and/or MS DCC requires PBUS resources.
→ As soon as one of the RS or MS DCC is configured the vc12-61 to vc12-64
resources are no longer available.
The DCC status function provides information about the HDLC link status towards the SDH port
and towards the PBUS access.

SAMOx Core Unit

STM-n
DCC Management
3 x 64 kbit/s and/or interface
9 x 64 kbit/s
IP
OSPFv2
PPP
DCC HDLC
TDM CTP TDM CTP
PBUS
Figure 45: NE management over DCC operation
It is also possible to use a partially or completely filled P12 for the ECC transport. The P12 is
transported in a VC-12.
The core unit is used the same way as with the ECC over DCC transport.
SAMOx Core Unit

STM-n
Management
interface
VC-12
IP
OSPFv2
PPP
ECC VC-12/P12 HDLC
n x 64 kbit/s or
2048 kbit/s TDM CTP TDM CTP
PBUS
Figure 46: ECC over P12 operation
5.6 Synchronization and Timing Functions

For a description of the SAMOx and FOX61x synchronization and timing functions please refer
to [1KHW029105] User Manual “Synchronization”.
5.7 Traffic Protection
5.7.1 Multiplex Section Protection (MSP)

SAMOx supports multiplex section protection (MSP) on a single unit. MSP can be enabled on
the STM-16, STM-4 and/or STM-1 port pairs, i.e. MSP is supported between the logical SDH
ports
− sdh-1 and sdh-2, and
− sdh-3 and sdh-4.
In addition the SAMOx unit supports MSP on two units, operating as equipment protection pair.
MSP can be enabled on the STM-16, STM-4 and/or STM-1 port pairs. With MSP configured to
“intracard”, MSP is supported between the logical SDH ports


With MSP configured to “intercard”, MSP is supported between the logical SDH ports
The MSP mode “intracard” or “intercard” is individually configurable per logical SDH port.
working protecting working protecting

unit unit unit unit
SAMOx
SAMOx
SAMOx
SAMOx
SAMOx
SDH SDH SDH SDH SDH

logical logical logical logical logical
port port port port port
sdh-4 sdh-4 sdh-8 sdh-4 sdh-8
MSP intracard MSP intracard MSP intercard
Figure 47: MSP on a single unit (left) and on two units (right)
MSP protects against failures in the physical section (optical or electrical), the regenerator sec-
tion and the multiplex section. Using the “intercard” MSP mode, MSP protects also against
SAMOx equipment failures. MSP provides the following functions:
• 1+1 unidirectional protection mode according to ITU-T G.841, § 7.1.4.4.
The SAMOx unit selects the received signal from one of the two STM-16, STM-4 or STM-1
interfaces and switches to the other interface if this signal fails.
1+1 unidirectional protection switching uses no protocol.
• 1+1 bidirectional protection mode
A dedicated protocol, transported in the K1 and K2 bytes of the MS overhead, synchronizes
the local and remote STM-16, STM-4 or STM-1 interfaces of the multiplex section to select
the received signal from the same STM-16, STM-4 or STM-1 interface.
Bidirectional protection switching uses a fixed bridge (without extra traffic), compatible with
1:n bidirectional switching according to ITU-T G.841, § 7.1.4.5.1.
The operation type is non-revertive, i.e. the system does not switch back to the working channel
if the working channel becomes available again after a switch-over to the protecting channel.
If after a protection switchover the working channel is available again while the protecting chan-
nel fails, the system switches back to the working channel. However, the protection protocol of
the bidirectional protection is not switched to the working channel.
The working channel provides the active STM-16, STM-4 or STM-1 signal under normal operat-
ing conditions. The standards refer to the working channel as channel 1. The protecting channel
protects the working channel. The standards refer to the protecting channel as channel 0.

working working
SDH
access
protecting network protecting
K1, K2 AUG-4 AUG-4 K1, K2 AUG-4 AUG-4

x4 x4 x4 x4
AU-4 AU-4 AU-4 AU-4

x4 x4 x4 x4
SAMOx
SAMOx
4 x AU-4 4 x AU-4
AU-4 Cross Connect AU-4 Cross Connect
Figure 48: 1+1 MSP (only one direction of the MS trail is shown)
The figure above shows an example with STM-4.

Protection switching takes place in the higher order cross connect (AU-4 cross connect). 16
(STM-16 interface), 4 (STM-4 interface) or 1 (STM-1 interface) AU-4 signals are switched simul-
taneously.
Protection switching action can be driven by two different request types:
Traffic signal requests:
• Signal fail (SF)
The SF state is activated if the analysis of the STM-16, STM-4 or STM-1 traffic signal reports
a signal failure in the PS, MS or RS:
− Loss of optical or electrical signal,
− Loss of frame alignment,
− TTI mismatch,
− AIS.
• Signal degraded (SD)
The SD state is activated if the analysis of the STM-16, STM-4 or STM-1 traffic signal shows
a degraded traffic signal.
External command requests:
External commands are the switching requests applied by the user via the management system.
The list below shows the external commands for MSP in the descending order of priority. Please
note the restrictions on effectiveness for some of the commands:
• Clear
Clears all switching requests listed below.
• Lockout of protection (Protecting channel only).
This command blocks all switching requests to switch the active channel from the working to
the protecting channel.

• Forced switch
Switches the active channel to the port where the command has been applied to, unless an
equal or higher priority switch command is in effect.
Since a forced switch has higher priority than SF or SD on the working channel, this com-
mand will be carried out regardless of the condition of the working channel.
Note that an SF condition on the protecting channel has higher priority than a forced switch.
Therefore it is not possible to switch from the working channel to the protecting channel if
this channel has SF.
• Manual switch
Switches the active channel to the port where the command has been applied to, unless an
equal or higher priority switch command is in effect or an SF condition exists on this channel.
Since manual switch has lower priority than SF or SD on a working or protecting channel,
this command will be carried out only if the channel is not in SF or SD condition.
• Exercise
Effective for the bidirectional MSP mode and working channel only.
This command checks the responses of automatic protection switching (APS) bytes to a
switch request, unless the protecting channel is in use. The switch is not actually completed
for the traffic signal.
The remote request will display a “Reverse request”.
Each request (signal, external) has a fixed priority. These priorities allow the MSP to select the
request with the highest priority if there is more than one request pending. The table below lists
the requests with the corresponding priorities according to ITU-T G.841.
Table 31: Types of request (Table 7-1/G.841)

Bits Condition, state or external request Order 1
1234
1111 Lockout of protection 2 Highest
1110 Forced switch |
1101 Signal fail high priority |
1100 Signal fail low priority |
1011 Signal degrade high priority |
1010 Signal degrade low priority |
3 |
1001 Unused
1000 Manual switch |
3
0111 Unused |
0110 Wait to restore |
3
0101 Unused |
0100 Exercise |
3
0011 Unused |
0010 Reverse request |
0001 Do not revert |
0000 No request Lowest
1. An SF condition on the protection section is higher priority than any of the requests
that would cause a working channel to be selected from the protection section.
2. Only the null signal (0), i.e. the protecting channel, is allowed with a lockout of pro-
tection request.
3. Some network operators may use these codes for network specific purposes. The
receiver is capable of ignoring these codes.
In the bidirectional MSP mode it is possible to indicate locally the requests issued by the remote
interface. This information is transmitted via the K1/K2 bytes in the SOH.

Beside the signal requests and external requests there is a protocol failure which can actuate a
protection switching. FOP (failure of protocol) is available only for the bidirectional MSP mode.
The FOP switchover has a higher priority than all the other requests above.
Failure of protocol:
• Failure of protocol (FOP) driven switchover
If the protocol in the protecting channel fails, the system generates a FOP failure and
switches the traffic signal to the working channel.
For example, the FOP failure (alarm) is generated if a switch command issued from an inter-
face in bidirectional MSP mode receives no answer from the remote interface that operates
in unidirectional MSP mode.
Please note:
The protocol for the bidirectional protection mode is always running on the protect-
ing channel (channel 0).
Please note:
When using the DCC in the regenerator and/or multiplex section overhead for
ECC, please note that
→ MSP affects payload traffic only. The channels in the SOH are not protected
with the configuration of MSP.
→ Accordingly, the MSP maintenance functions do not affect the channels in the
SOH.
→ the ECC, transported in the DCC bytes, is taken from the unprotected side, i.e.
protection of the ECC is done in the management communication network. Note
that this doubles the required capacity on the PBUS.
5.7.2 Subnetwork Connection Protection SNCP/N

SAMOx supports non-intrusively monitored subnetwork connection protection (SNCP/N) for
trails terminated on the unit. SNCP/N protects against server failures, disconnected matrix con-
nections (via unequipped signal detection) and mis-connections (via TTI mismatch supervision).
The EoS application terminates the VC-4, VC-3 and VC-12.
The PBUS application (P12) terminates the VC-4 and VC-12.
SNCP/N is supported for VC-4, VC-3 and VC-12. SNCP/N can be enabled on any VC pairs.
Please note:
The number of SNCP protected VC-n connections is limited to 255.
SNCP/N provides the following functions:
• 1+1 unidirectional protection mode according to ITU-T G.841, § 8.
− The SAMOx unit selects the received signal from one of the two VCs and switches to the
other VC if this signal fails.
− 1+1 unidirectional protection switching uses no protocol.
− The operation type can be configured to non-revertive or revertive.
− The working channel provides the active VC under normal operating conditions. The pro-
tecting channel protects the working channel.
− There is no restriction about the selection of working and protecting VC.
In addition SAMOx supports SNCP/N with bidirectional switching type and revertive or non-
revertive operation type for the PBUS and E12 front port application, i.e. for VC-12 trails ter-
minated on the unit.
This type of protection provides the following functions:
• 1+1 bidirectional protection mode.

other VC if this signal fails. The selector state is signaled to the remote termination func-
tion which switches its selector accordingly.
− 1+1 bidirectional protection switching uses a proprietary protocol transported in the RFI
bit of the V5[4] byte.
− The operation type can be configured to revertive or non-revertive.
The protection parameters SNCP “wait to restore time”, “hold off time” and “guard time” are con-
figurable per VC type on the unit configuration layer. Please refer to section 8.2.3.1 AP: / unit-x,
Configuration - General - SNCP Times (on page 150).
When cross connections in SAMOx have been protected with SNCP it is possible to check and
control the status of the SNCP/N protection switch (working, protecting circuit) via the CTP sta-
tus function.
In case of revertive operation type the active trail status displays if the path selector is in the
WTR (wait to restore) state.
In case of bidirectional protection switching the general status dialog displays also the path
selector state from the remote end:
− Working: The remote path selector has selected the working path,
− Protecting: The remote path selector has selected the protecting path.
The APS Protocol Failure is activated when the received APS protocol state mismatches the
local path selector state.
For more information on the principles of protection please refer to [1KHW002467] User Manual
“TDM Services”.

5.7.2.1 SNCP/N for VC-4
working working
SDH
access

SAMOx
SAMOx
x4 x4 x4 x4
x4 x4 x4 x4
AU-4 AU-4 AU-4 AU-4

x 16 x 16 x 16 x 16
AU-4 MON MON

AU-4 Cross Connect
AU-4
AU-4 Cross Connect
Figure 49: VC-4 SNCP/N
VC-4 protection switching takes place in the higher order cross connect (AU-4 cross connect).
• Traffic signal requests:
− Signal fail (SF)
The SF state is activated if the analysis of the VC-4 traffic signal reports a signal failure:
- AU-4 AIS,
- AU-4 loss of pointer,
- VC-4 unequipped,
- TTI mismatch.
− Signal degraded (SD)
The SD state is activated if the analysis of the VC-4 traffic signal shows a degraded traffic
signal.
• External command requests
− Forced switch to working
− Forced switch to protecting
− Manual switch to working
− Manual switch to protecting
Note that a forced switch is executed even when there is a failure on the target signal. The com-
mand is a maintenance function, i.e. it is not stored in the unit’s database.
Note that a manual switch is executed only when there is no failure on the target signal. The
command is a maintenance function, i.e. it is not stored in the units database.

5.7.2.2 SNCP/N for VC-3 and VC-12
working working
SDH
access

SAMOx
SAMOx
VC-4 VC-4 VC-4 VC-4
TUG-3 TUG-3 TUG-3 TUG-3
TU-3 TU-3 TU-3 TU-3
TU-3 MON MON

TU-3 Cross Connect
TU-3
TU-3 Cross Connect
Figure 50: VC-3 SNCP/N
VC-3 and VC-12 protection switching takes place in the lower order cross connects (TU-3 cross
connect and TU-12 cross connect).
• Traffic signal requests:
The SF state is activated if the analysis of the VC-3 or VC-12 traffic signal reports a signal
failure:
- TU-3 or TU-12 AIS,
- TU-3 or TU-12 loss of pointer,
- VC-3 or VC-12 unequipped,
- TTI mismatch.
The SD state is activated if the analysis of the VC-3 or VC-12 traffic signal shows a
degraded traffic signal.

5.7.3 Subnetwork Connection Protection SNCP/I

SAMOx supports inherently monitored subnetwork connection protection (SNCP/I) for trails not
terminated on the unit. SNCP/I protects against server failures.
Through connected VC-4, VC-3 and VC-12 are not terminated.
SNCP/I is supported for VC-4, VC-3 and VC-12. SNCP/I can be enabled on any VC pairs.
Please note:
The number of SNCP protected VC-n connections is limited to 255.
SNCP/I provides the following functions:
• 1+1 unidirectional protection mode according to ITU-T G.841, § 8.
other VC if this signal fails.
− The operation type can be configured to non-revertive or revertive.
The protection parameters SNCP “wait to restore time”, “hold off time” and “guard time” are con-
figurable per VC type on the unit configuration layer. The same configuration as for SNCP/N
applies.
5.7.3.1 SNCP/I for VC-4
working working
SDH
access

SAMOx
SAMOx

x4 x4 x4 x4
x4 x4 x4 x4
AU-4 AU-4 AU-4 AU-4

x 16 x 16 x 16 x 16
AU-4 AU-4
Figure 51: VC-4 SNCP/I
VC-4 protection switching takes place in the higher order cross connect (AU-4 cross connect).


• Traffic signal request:
The SF state is activated if the analysis of the VC-4 traffic signal reports a signal failure:
- AU-4 AIS,
- AU-4 loss of pointer.
5.7.3.2 SNCP/I for VC-3 and VC-12
working working
SDH
access

SAMOx
SAMOx
VC-4 VC-4 VC-4 VC-4
TUG-3 TUG-3 TUG-3 TUG-3
TU-3 TU-3 TU-3 TU-3
TU-3 TU-3
TU-3 Cross Connect TU-3 Cross Connect
Figure 52: VC-3 SNCP/I example
VC-3 and VC-12 protection switching takes place in the lower order cross connects (TU-3 cross
connect and TU-12 cross connect).
The SF state is activated if the analysis of the VC-3 or VC-12 traffic signal reports a signal
failure:
- TU-3 or TU-12 AIS,
- TU-3 or TU-12 loss of pointer.


5.7.4 P12 and P0-nc Subnetwork Connection Protection SNCP

SAMOx supports inherently monitored subnetwork connection protection (SNCP/I) for P12 and
P0-nc signals.
The protection can be configured to protect P12 and P0-nc signals from the aggregate side (net-
work side) or from the tributary side (PBUS side).
5.7.4.1 Protection from Tributary Side

P12 and P0-nc signals connected to one or two tributary units, e.g. LEDE1, are terminated or
through connected transparently. The signal state of the working and protecting signal is
brought via the PBUS to the SAMOx unit where the protection switching takes place.
SNCP/I provides the following functions:
• 1+1 unidirectional protection mode according to ITU-T G.808.1, § 11.2.
− The SAMOx unit selects the received signal from one of the two P12 or P0-nc signals and
switches to the other P12 or P0-nc if this signal fails.
− The operation type is revertive or non-revertive (for P0-1c only).
− There is no restriction about the selection of working and protecting P12 or P0-nc.
In addition SAMOx supports bidirectional switching type for terminated P12 signals.
This type of protection provides the following functions:
• 1+1 bidirectional protection mode.
− The SAMOx unit selects the received signal from one of the two P12 signals and switches
to the other P12 signal if this signal fails. The failure state is signaled to the remote termi-
nation function with the RDI which switches its selector accordingly.
− 1+1 bidirectional protection switching uses RDI as protection switching criterion. Please
refer to [1KHW002467] User Manual “TDM Services” for further information.
− The operation type can be configured to revertive or non-revertive (non-revertive for P0-1
only).
− The working channel provides the active P12 signal under normal operating conditions.
The protecting channel protects the working channel.
− There is no restriction about the selection of working and protecting P12 signal.

SAMOx
VC-12
C-12
P-12
PBUS
P12 P12
E1 E1
LEDE1 LEDE1
Figure 53: P12 SNCP/I from the tributary side
P12 and P0-nc protection switching takes place in the P12/P0-nc cross connect function of the
PBUS access circuit.
The SF state is activated if the analysis of the P12 or P0-nc traffic signal reports a signal
failure:
- E12 loss of signal,
- P12 AIS,
- P12 loss of frame alignment (terminated P12 mode only),
- P12 loss of multiframe alignment (terminated P12 mode only),
- P12 TTI mismatch (terminated P12 mode only, future release),
- P12 bit error ratio > 10E-3 (terminated P12 mode only).
The SD state is activated if the analysis of the P12 traffic signal shows a degraded traffic
signal (terminated P12 mode only).
5.7.4.2 Protection from Network Side

P12 and P0-nc protection switching for signals from the network or aggregate side takes place
on a tributary unit, e.g. LEDE1. A P12 or P0-nc signal transported over the network is received

on one or two SAMOx units as a working and a protecting signal. The tributary unit performs the
selection according to the signal states of the two signals.
SAMO SAMO
VC-12 VC-12
C-12 C-12
P-12 P-12
PBUS
P12
E1
LEDE1
Figure 54: P12 SNCP/I from the network side with two SAMOx units
Please note:
The protection parameters wait-to-restore time, holdoff time and guard time are not
available for P12 and P0-nc SNCP.
5.7.5 Ethernet Protection

SAMOx provides no dedicated facilities for Ethernet protection. Ethernet protection shall be
done on an external Ethernet layer 2 device using an appropriate protocol (e.g. STP, RSTP).
Please note:
Ethernet protection using an Ethernet switch is only applicable if the SAMOx inter-
nal switch is disabled, i.e. in the unswitched bridging mode.
→ In the unswitched mode, i.e. the SAMOx Ethernet ports do not participate in the
VLAN bridge, the ports support all VLAN bridge port features as e.g. RSTP or
MSTP. Please refer to [1KHW028566] User Manual “Ethernet Services”.

SDH
access
network
SAMOx
SAMOx
SAMOx
SAMOx
VC-4 VC-4 VC-4 VC-4
EoS EoS EoS EoS
ETH ETH ETH ETH
forwarding blocking blocking forwarding
Ethernet switch Ethernet switch

xSTP enabled xSTP enabled
Figure 55: Ethernet protection using an Ethernet switch
Please note:
The two SAMOx units in Figure 55 are no equipment protected pair of units.
5.8 Equipment Protection (EQP)

Equipment protection of the SAMOx unit within FOX61x is only available if the working and the
protecting SAMOx units are plugged as pairs in dedicated subrack slots:
Table 32: FOX61x slot pairs for SAMOx EQP

Network element Working unit Protecting unit
FOX615 R2 and FOX615 slot-4 slot-6
FOX615 R2 and FOX615 slot-18 slot-20
FOX612 slot-7 slot-9
Please note:
The roles of working and protecting unit is fixed within a slot pair.
Please note:
The FOX611 provides no dedicated slot pair for SAMOx equipment protection.
After startup the working unit is the active unit and the protecting unit is the standby unit.
The two units in the equipment protection group must be of the same type, e.g. both units must
be a SAMO3 unit.

5.8.1 Redundancy Switch

The redundancy switch on the SAMOx unit is placed between the SDH SFPs and the STM-1/4/
16 termination circuits. It makes a connection between the SDH SFPs of the working and pro-
tecting units and the STM-1/4/16 termination circuits on the working and protecting unit via the
backplane of the FOX61x. There are in total four STM-16 and four STM-4 bidirectional connec-
tions.
Without EQP the connections between the working and the protecting SAMOx units are not
used.
Please note:
The Figure 56 and the Figure 57 show STM-16 and STM-4 SFP modules as an
example.
→ STM-16 SFP modules can be replaced with STM-4 SFP modules.
→ STM-4 SFP modules can be replaced with STM-1 SFP modules.
STM-16 STM-16 STM-4 STM-4 STM-16 STM-16 STM-4 STM-4

port-1 port-2 port-3 port-4 port-1 port-2 port-3 port-4
Redundancy
Redundancy
Switch
Switch
STM-16 STM-16 STM-16 STM-16 STM-4 STM-4 STM-4 STM-4 STM-16 STM-16 STM-16 STM-16 STM-4 STM-4 STM-4 STM-4
sdh-1 sdh-5 sdh-2 sdh-6 sdh-3 sdh-7 sdh-4 sdh-8 sdh-1 sdh-5 sdh-2 sdh-6 sdh-3 sdh-7 sdh-4 sdh-8
SAMOx working, active SAMOx protecting, standby
Figure 56: Redundancy switch connections, working unit is active


port-1 port-2 port-3 port-4 port-1 port-2 port-3 port-4
Redundancy
Redundancy
Switch
Switch
STM-16 STM-16 STM-16 STM-16 STM-4 STM-4 STM-4 STM-4 STM-16 STM-16 STM-16 STM-16 STM-4 STM-4 STM-4 STM-4
sdh-1 sdh-5 sdh-2 sdh-6 sdh-3 sdh-7 sdh-4 sdh-8 sdh-1 sdh-5 sdh-2 sdh-6 sdh-3 sdh-7 sdh-4 sdh-8
SAMOx working, standby SAMOx protecting, active
Figure 57: Redundancy switch connections, protecting unit is active
The redundancy switch on the working unit connects the physical SDH ports (SFPs) port-1 to
port-4 on the working unit to the logical SDH ports sdh-1 to sdh-4 on the working and protecting
unit.
The redundancy switch on the protecting unit connects the physical SDH ports (SFPs) port-1 to
port-4 on the protecting unit to the logical SDH ports sdh-5 to sdh-8 on the working and protect-
ing unit.
On the standby unit, working or protecting, the SFPs and the redundancy switch are active. The
Ethernet switch as part of the FOX61x Switch and the Ethernet front ports are also active. The
access circuits to the PBUS, the E12 ports, the EoS ports and the SDH circuits are disabled.
5.8.2 EQP with SETS Protection

On an equipment protected pair of SAMOx units the SETS function is equipment protected. This
means:
• Only the SETS on the active SAMOx unit provides the SDH timing signals.
• Only the working SAMOx unit is available as PDH clock source in the PETS configuration on
the NE level.
• Only the working SAMOx unit is available as SDH clock source in the ESO-2 configuration
on the NE level.
After a protection switch-over the SETS function on the protecting SAMOx unit will provide the
SDH timing signals, will be used as PDH clock source and will be used as source for ESO-2.
Please note:
During a protection switch-over the ESO-2 synchronization output on the core is
squelched for several seconds.
5.8.3 EQP with Traffic Protection

SAMOx equipment protection can be used together with traffic protection, i.e. path protection
(MSP) or subnetwork connection protection.

Traffic protection together with equipment protection protects also against failures in the network
and a failure of the SFP or redundancy switch.
5.8.3.1 PDH Traffic Protection

The PDH traffic accessing the PBUS or an E12 front port is protected as follows: During normal
operation, the VC-12 traffic from the west and east direction is terminated on the working unit
(active), using the redundancy switch. The TU-12 cross connect selects the working or the pro-
tecting VC-12 signal from the west or east direction. The selected signal accesses the E12 front
port or the PBUS. The E12 front port and the PBUS access on the protecting unit (standby) are
disabled.
In case of a failure of the working unit, the working unit becomes the standby unit and the pro-
tecting unit becomes the active unit. The VC-12 traffic from the west and east direction is termi-
nated on the protecting unit (active), using the redundancy switch. The TU-12 cross connect
selects the working or the protecting VC-12 signal from the west or east direction. The selected
signal accesses the E12 front port or the PBUS. The E12 front port and the PBUS access on
the working unit (standby) is disabled.
STM-16 STM-16
west east
STM-16 STM-16
SAMOx
SAMOx
SFP SFP
Redundancy Redundancy
Switch Switch
TU-12 TU-12 TU-12 TU-12
TU-12
Cross
Connect
MON MON MON MON
active VC-12 VC-12 VC-12 standby VC-12
SAMO3 SAMO3
C-12 C-12 C-12 C-12
only only
P-12 P12 P12 P-12

highZ
PBUS
E12 E12 E12 E12
Figure 58: Equipment protection for PDH traffic

5.8.3.2 Ethernet Traffic Protection over EPL Ports

The Ethernet traffic accessing the Ethernet front ports in the unswitched port handling mode is
protected as follows: During normal operation, the EoS VC-4, VC-3, and VC-12 traffic from the
west and east direction is terminated on the working unit (active), using the redundancy switch.
The terminated signal is forwarded to the Ethernet port. The Ethernet ports on the protecting
unit (standby) remain active, but the forwarding of packets is disabled.
tecting unit becomes the active unit. The EoS VC-4, VC-3, and VC-12 traffic from the west and
east direction is terminated on the protecting unit (active), using the redundancy switch. The ter-
minated signal is forwarded to the Ethernet port. The Ethernet ports on the working unit
(standby) remain active, but the forwarding of packets is disabled.
STM-16 STM-16
west east
STM-16 STM-16
SAMOx
SAMOx
SFP SFP
Switch Switch
STM-16 STM-16
AU-4
Cross
Connect
MON MON
VC-4 VC-4
VCAT stop VCAT

forwarding
GFP GFP
MAC MAC
active ETH standby ETH
Figure 59: Equipment protection for unswitched Ethernet traffic (VC-4 EoS)
Please note:
The Ethernet ports used on the working and the protecting SAMOx units must be
both set to the administrative state “up”.

Please note:
The EPL handling on the working and the protecting SAMOx units must be config-
ured identically.
Please note:
The EoS ports used for the EPL application on the working and the protecting
SAMOx units must be configured identically (port mode = unswitched) in the bridge
port configuration in the FOXCST “Switching” view.
Please note:
Both Ethernet front ports of the working and the protecting unit can be connected to
the same Ethernet switch.
→ xSTP is not required since the Ethernet front port on the standby unit is not in
the forwarding state.
Please note:
During a protection switching event the user traffic is interrupted for up to 50 ms.
Please note:
With the SAMO2 HW revision R1E and earlier and the SAMO3 HW revision R1C
and earlier, the protection switching event after removal of the working SAMO2 unit
interrupts the user traffic for up to 600 ms.
5.8.3.3 Ethernet Traffic Protection over Switched Ports

The Ethernet traffic accessing the Ethernet front ports in the switched port handling mode is pro-
tected as follows: During normal operation, the EoS VC-4, VC-3, and VC-12 traffic from the west
and east direction is terminated on the working unit (active), using the redundancy switch. The
terminated signal is forwarded to the FOX61x Switch and can be accessed at any Ethernet front
port which is attached to FOX61x Switch. The example in Figure 60 shows the external Ethernet
front port located on the working SAMOx unit. The Ethernet front ports on the standby unit are
not used.
tecting unit becomes the active unit. The EoS VC-4, VC-3, and VC-12 traffic from the west and
east direction is terminated on the protecting unit (active), using the redundancy switch. The ter-
minated signal is forwarded to the FOX61x Switch and can still be accessed at the Ethernet
front port on the working unit (standby). This scenario requires no external Ethernet switch, but
relies on an operational switch circuit and Ethernet port on the standby SAMOx unit.

STM-16 STM-16
west east
STM-16 STM-16
SAMOx
SAMOx
SFP SFP
Switch Switch
AU-4 AU-4
Cross Cross
Connect Connect
MON MON MON MON
VC-4 VC-4
VCAT / GFP / stop VCAT / GFP /

MAC / ETH forwarding MAC / ETH
FOX61x Switch
active ETH standby
Figure 60: Equipment protection for switched Ethernet traffic (VC-4 EoS)
If also the switch circuit and Ethernet port on the standby SAMOx unit shall be protected
another Ethernet front port which is attached to FOX61x Switch can be connected in parallel to
an external Ethernet device. This requires the activation of RSTP or MSTP on these ports.
Please note:
The two EoS ports on the working and the protecting SAMOx units are both
attached to the FOX61x Switch. One EoS port is active, the other is standby, but
both EoS ports are available as bridge ports in the FOXCST “Switching” view.
→ The bridge port configuration (port mode, PVID, VLANs, …) must be configured
identically for both ports.
Please note:
During a protection switching event the user traffic is interrupted for up to 50 ms.
Please note:
With the SAMO2 HW revision R1E and earlier and the SAMO3 HW revision R1C
and earlier, the protection switching event after removal of the working SAMO2 unit
interrupts the user traffic for up to 600 ms.

5.8.4 EQP Prerequisites

To enable equipment protection for the SAMOx unit some prerequisites must be met:
• The protecting SAMOx unit must be plugged in one of the dedicated protecting unit slots of
the FOX61x subrack.
• The protecting SAMOx unit must be in the unassigned state. Otherwise the unit will not be
selectable in the EQP configuration in AP: /unit-x, Configuration - EQP: Create Group…,
EQP Group Creation, Protecting Unit.
• The protecting unit must be hardware compatible with the working unit. Check the hardware
compatibility status after the EQP group configuration in the AP: /unit-x, Status - EQP: Units
Status, HW Compatible.
The following requirements must be fulfilled that the two units are stated as hardware com-
patible:
− Identical unit function. The unit function is composed of the 5 first characters of the unit
name, e.g. SAMOx. The unit name is available at the AP: /unit-x, Main - Equipment, Unit.
− Identical board identification, e.g. 383. The board identification is available at the AP: /
unit-x, Main - Inventory, Board ID.
− Identical hardware variant. The hardware variant is the truncation of the hardware key
divided by 256, e.g. 1/256 = 0. The hardware key is available at the AP: /unit-x, Main -
Inventory, Hardware Key.
• The protecting unit must be software compatible with the working unit. Check the software
compatibility status after the EQP group configuration in the AP: /unit-x, Status - EQP: Units
Status, SW Compatible.
The following requirements must be fulfilled that the two units are stated as software compat-
ible:
− Identical unit function. The unit function is composed of the 5 first characters of the soft-
ware name, e.g. samo2. The software name is available at the AP: /unit-x, Main - Equip-
ment, Software.
In order to guarantee the full compatibility of all features it is strongly recommended to use
the same software on the working and on the protecting unit.
The compatible software must be installed on the SAMOx unit before the EQP group cre-
ation.
• The unit configuration of an equipment protection group is mainly done on the active unit.
• The standby unit requires the configuration of the following items:
− Physical SDH front ports:
All SFP related parameters must be configured.
The ports must be in the administrative state “up”.
− Physical E12 front ports (SAMO3 only):
No parameters must be configured.
− Physical Ethernet front ports:
All PHY parameters must be configured.
The ports must be in the administrative state “up”.
− Bridge ports of the FOX61x Switch (VLAN Bridge function):
The EoS ports and, if used, the Ethernet front ports attached to the FOX61x Switch must
be configured in the “Tree View” and “Switching” view of the FOXCST.
Please note:
The EoS ports of a standby SAMOx unit can be added to the FOX61x Switch by
configuring them to the “CVP” port type on the NE level (navigate to the AP: /ne,
Main - Port Type) or by adding them directly in the FOXCST “Switching” view (navi-
gate to AP: /Switching/Bridges/bridge-1/Ports).

− PWAC ports of the FOX61x Switch (MPLS-TP VPWS Transport function):

The EoS ports and, if used, the Ethernet front ports attached to the FOX61x Switch must
be configured in the “Tree View” view of the FOXCST.
− SETS:
No SETS parameters must be configured. The SETS parameters of the working unit are
applied to the protecting unit after a switch-over. In the PETS and ESO configuration on
the NE only the working SAMOx unit is available as PDH clock source.
All other items on the standby unit are not configurable.

The configuration of an equipment protection group must be saved (FOXCST NE
menu or FOXCST tool bar: Save to NE).
→ Otherwise, in case of a protection switch event, the NE will load an outdated
configuration from the internal configuration database and the NE configuration
will be corrupted.
5.8.5 EQP Configuration

The working SAMOx unit of an EQP group is assigned and configured the same way as a stand
alone SAMOx unit.
The protecting SAMOx unit is running with the same ESW as the working unit and must be in
the unassigned state.
The 1:1 equipment protection group is configured on the working unit:
• AP: /unit-x, Configuration - EQP.
− Execute the command “Create EQP Group…”.
− Select the Protecting unit, e.g. /unit-6.
− Execute “OK”.
• Configure the protecting unit according to the list given in section EQP Prerequisites:
− Physical SDH ports.
− Physical E12 ports (SAMO3 only).
− Physical Ethernet ports.
− FOX61x Switch ports and VLANs.
− SETS.
• Configure all required TDM cross connections with the involved CTPs on the working unit
which must also be the active unit.
• Save the NE configuration.
Further on any changes on the SAMOx configuration, except ports and cross connections, must
be done on the active unit. To find out which unit is the active unit check the AP tree
or the unit status of the working or protecting SAMOx unit.

Please note:
The TDM cross connections on the SAMOx unit can only be created on the work-
ing unit. If the working unit is the standby unit, the CTPs of the standby working
unit are only visible in the “Create Cross Connection” dialog if the A-End or Z-End
“Unit” parameter is set to “All”.
Please note:
The TDM cross connections on the SAMOx unit always use the MO addresses of
the working unit.
5.8.6 EQP Status

The unit status of the working and protecting units shows the actual status of the units belonging
to the equipment protection group. The unit status offers also the commands for the EQP
manipulation:
• Manual switch-over
The currently standby unit is set as active unit and the currently active unit is set as standby
unit. This requires that the currently standby unit is in operational state, i.e.
− has no failure,
− is not isolated.
A manual switch is possible if it is indicated with the “Manual Switch-Over Allowed” parame-
ter.
Note that this command can only be activated on the working unit status dialog.
• Forced switch-over
The currently standby unit is set as active unit, independent of the operational state of the
currently standby unit.
Note that there is a risk that the user traffic will be permanently interrupted if the currently
standby unit is not operational.
The currently active unit is set as standby unit.
Note that this command can only be activated on the working unit status dialog.
• Isolate unit
To be able to perform a maintenance action, e.g. update of the embedded software, on an
active unit without activating a protection switchover, the working unit can be isolated. This
means that the protection switching state machine is frozen and no protection switch will be
done until the isolation of the unit is removed.
Note that the isolate unit command can only be applied to the working unit.
• Join unit
Remove the isolation of a previously isolated unit.
Note that the join unit command can only be applied to the working unit.
The table in the EQP status dialog displays the following items. Please refer also to section
8.2.6.5 AP: / unit-x, Status - EQP (on page 176):
• Unit
MO address of the unit belonging to the EQP group.
• EQP unit mode
The working unit is the unit where the protection group has been configured.
The protecting unit is the unit that has been set to the unassigned state before configuring
the protection group.

• Active
Active true means the unit is the active unit, i.e. it is the operational unit.
Active false means the unit is the standby unit, i.e. it is not the operational unit.
The active state can be changed with the “Manual Switch” and “Forced Switch” commands.
• Failure
Failure true means the unit is in a failure state.
Failure false means the unit is not in a failure state.
The failure state can not be changed manually.
• Substituted
Substituted true on the working unit means the unit has been substituted by the protecting
unit. A substituted unit is also in the “active false” state.
Substituted false on the working unit means the unit has not been substituted, i.e. it is the
active unit or it has been isolated.
The substituted state of the protecting unit is always false.
• Isolated
Isolated true means the unit has been isolated with the “Isolate Unit” command.
Isolated false means the unit is not isolated.
The isolation state can be changed with the “Isolate Unit” and “Join Unit” commands.
The isolated state of the protecting unit is always false.
• HW Compatible
HW compatible true means the working HW unit is compatible with the protecting HW unit.
HW compatible false means the working HW unit is not compatible with the protecting HW
unit. Equipment protection is not possible.
• SW Compatible
SW compatible true means the working unit embedded software (ESW) is compatible with
the protecting unit ESW.
SW compatible false means the working unit ESW is not compatible with the protecting unit
ESW. Equipment protection is not possible.
• DB Saved
DB saved true means the current configuration of the working and protecting unit has been
saved to the FOX61x internal database.
DB saved false means the current configuration of the working or protecting unit has not
been saved to the FOX61x internal database. A protection switching event will load an out-
dated configuration and traffic will be disturbed.

FOX61x | SAMO2, SAMO3, SAMO5 COMMISSIONING
6 Commissioning
This section describes the management of the basic system functions of the SAMOx unit and
the configuration of the PDH and EoS transport.
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 Cross Connections

The SAMOx unit implements three cross connect functions, an AU-4 cross connect, a TU-3
cross connect and a TU-12 cross connect. All signals that are cross connected through the
SAMOx unit must pass either the AU-4 cross connect or the AU-4 and TU-3 or TU-12 cross
connects.
Accordingly only traffic signal cross connections on the VC-4 layer can be configured in a single
step. Traffic signal cross connections on the VC-3 and VC-12 layers are configured in two steps,
cross connections on the P12 and P0-nc layers must be configured in three steps.
An exception is the DCC which can be cross connected in one step to a channel on the core
unit.
sdh/
sdh-x STM-1/4/16 STM-1/4/16 STM-1/4/16
j-x dccm dccr
1. step
eos/ vc4 vc4 vc4

eos-x/ VC4 VC4 VC4 VC4
eos vc4-x vc4-x vc4-x vc4-x
VC3 VC12 VC12

klm-x00 klm-xyz klm-xyz
2. step
eos/ eos/ port-x pdh

eos-x/ VC3 eos-x/ VC12 VC12 VC12
eos vc3-x eos vc12-x vc12 vc12-x
P12/P0-nc
chan-x
SAMOx
PBUS 3. step
TDM TDM management

service P12/P0-nc service P0-nc Network/ P0-nc
unit chan-x unit chan-x tdmInterfaces ppp-x
Figure 61: Cross connection overview
The Figure 62 shows all cross connections on the SAMOx unit. These cross connections are
described in detail in the following sections.

Please note:
In the figure below all items “Ethernet switch/port” stand for a SAMOx Ethernet
front port or for a VLAN bridge Ethernet port.
Please note:
In all figures and all tables of this section the numbering of the ports, SDH, PDH
and Ethernet signals uses the same characters on both sides of a connection.
Despite of this the numbering needs not to be identical, e.g. a VC-12 signal desig-
nated “vc4/vc4-1/klm-121” can be cross connected to another VC-12 signal desig-
nated “vc4/vc4-5/klm-372”.
sdh/
sdh-x STM-1/4/16 STM-1/4/16 STM-1/4/16
j-x dccm dccr
sdh/sdh-x/j-x ↔ sdh/sdh-x/dccm ↔ sdh/sdh-x/dccr ↔

sdh/sdh-y/j-y sdh/sdh-y/dccm sdh/sdh-y/dccr
sdh/sdh-x/j-x ↔
eos/eos-y/eos/vc4-y
sdh/sdh-x/j-x ↔
vc4/ vc4-y
sdh/sdh-x/j-x ↔
vc4/ vc4-y
SAMOx
eos/ vc4 vc4
eos-x/ VC4 VC4 VC4
sdh/sdh-x/dccr ↔ sdh/sdh-x/dccr ↔
eos vc4-y vc4-y vc4-y managementNetwork/
TDM service unit/chan-y
and/ or tdmI nterfaces/ ppp-x
sdh/sdh-x/dccm ↔ and/ or
VC3 VC12 sdh/sdh-x/dccm ↔
klm-x00 klm-xyz managementNetwork/
tdmI nterfaces/ ppp-x
Ethernet switch/port
vc4/ vc4-x/klm-x00 ↔ vc4/ vc4-x/klm-xyz ↔

vc4/vc4-x/klm-x00 ↔ vc4/ vc4-y/klm-y00 vc4/ vc4-y/klm-abc
eos/eos-y/eos/vc3-y
eos/
eos-x/ VC3
eos vc3-y vc4/vc4-x/klm-xyz ↔ vc4/vc4-x/klm-xyz ↔ vc4/ vc4-x/klm-xyz ↔
port-x/vc12 pdh/ vc12-y pdh/vc12-y
port-x pdh pdh

VC12 VC12 VC12
Ethernet switch/port vc12 vc12-y vc12-y
SAMO3 P12 P0_nc

vc4/vc4-x/klm-xyz ↔ only chan-x chan-x
eos/eos-y/eos/vc12-y
eos/
eos-x/ VC12 pdh/vc12-x/p12/chan-x ↔ pdh/vc12-x/p12/chan-x ↔
pdh/vc12-y/p12/chan-y pdh/vc12-y/p12/chan-y
eos vc12-y
pdh/vc12-x/p12/chan-x ↔ pdh/vc12-x/p12/chan-x ↔
TDM service unit/chan-y TDM service unit/chan-y
PBUS Access
Ethernet switch/port E12 port PBUS Access PBUS Access PBUS Access
TDM TDM TDM

service P12 service P0-nc service P0-nc
unit chan-y unit chan-y unit chan-y
management
Network/ P0-nc
tdmInterfaces ppp-x
Figure 62: Cross connection detail view

6.1.1 VC-4 Cross Connections

VC-4 cross connections can only be done on a single SAMOx unit. There is no way to access a
VC-4 signal on another SDH unit.
Please note:
Cross connections related to the physical SDH ports located on a protecting
SAMOx unit are handled as if these ports were located on the working SAMOx unit,
i.e. the logical SDH ports managed objects are available on the working SAMOx
unit.
VC-4 resources on the SAMOx unit are available as follows:
• STM-16, STM-4 or STM-1 port resources are available in the “/unit-x/sdh/sdh-x” access
points.
• VC-4 resources used for the lower layers (VC-3, VC-12, P12, P0-nc) must be created in the
“/unit-x/vc4” configuration.
• EoS resources (VCG members) must be created in the “/unit-x/eos/eos-x/eos” configuration.
On the VC-4 layer in SAMOx the following signal types are available:
• /unit-x/sdh/sdh-y/j-z, e.g. /unit-4/sdh/sdh-1/j-1:
y = 1 to 4 (physical SDH port number 1 to 4 on the working SAMOx unit)
y = 5 to 8 (physical SDH port number 1 to 4 on the protecting SAMOx unit)
z = 1 (AU-4 number of STM-1), or
z = 1 to 4 (AU-4 number of STM-4), or
z = 1 to 16 (AU-4 number of STM-16) (SAMO2 and SAMO3 only)
The maximum number of available AU-4 in SAMOx is 80, when using SAMOx equipment
protection with two STM-4 ports and two STM-16 ports on both units.
• /unit-x/vc4/vc4-y, e.g. /unit-4/vc4/vc4-1:
y = 1 to 31 (VC-4 number)
vc4-y are internal resources of the SAMOx unit. The maximum number of available VC-4
with a TUG-3 structure in SAMOx is 31.
The maximum number of available VC-3 in a terminated VC-4 is 48.
The maximum number of available VC-12 in a terminated VC-4 is 945.
There is no restriction for the TUG-3 structure, i.e. any mixture of VC-3 and VC-12 is configu-
rable.
• /unit-x/eos/eos-y/eos/vc4-z, e.g. /unit-4/eos/eos-1/eos/vc4-1:
y = 1 to 32 (EoS port number)
z = 1 to 12 (VCG member number)
The maximum number of available EoS VC-4 members on the SAMOx unit and in a virtual
concatenation group is 12.
Please note:
The EoS capacity of 12 VC-4 must be shared between the EoS VC-4 members
and the EoS VC-3 members.
Please note:
If also EoS VC-12 members are configured the EoS capacity for VC-4 and VC-3
members is reduced to 8 VC-4 equivalents:
→ Up to 8 VC-4 equivalents for VC-4 and VC-3 members,
→ Up to 4 VC-4 equivalents for VC-12 members.

.../sdh-1/ .../sdh-1/ .../sdh-2/ .../sdh-2/ .../sdh-3/ .../sdh-5/ .../sdh-5/ .../sdh-6/ .../sdh-6/ .../sdh-7/
(STM-16) (STM-16) (STM-16) (STM-16) (STM-4) (STM-16) (STM-16) (STM-16) (STM-16) (STM-4)
j-1 j-2 j-1 j-2 j-1 j-1 j-2 j-1 j-2 j-1
j-3 j-4 j-3 j-4 j-2 j-3 j-4 j-3 j-4 j-2
j-5 j-6 j-5 j-6 j-3 j-5 j-6 j-5 j-6 j-3
j-7 j-8 j-7 j-8 j-4 j-7 j-8 j-7 j-8 j-4
j-9 j-10 j-9 j-10 j-1 j-9 j-10 j-9 j-10 j-1
j-11 j-12 j-11 j-12 j-2 j-11 j-12 j-11 j-12 j-2
j-13 j-14 j-13 j-14 j-3 j-13 j-14 j-13 j-14 j-3
j-15 j-16 j-15 j-16 j-4 j-15 j-16 j-15 j-16 j-4
sdh/sdh-x/j-x ↔ sdh/sdh-x/j-x ↔
eos/eos-y/eos/vc4-y sdh/sdh-x/j-x ↔ vc4/ vc4-y
sdh/sdh-y/j-y
.../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/ vc4/ vc4/ vc4/ vc4/

vc4-1 vc4-2 vc4-3 vc4-4 vc4-1 vc4-2 vc4-3 vc4-4


vc4/ vc4/ vc4/ vc4/

vc4-13 vc4-14 vc4-15 vc4-16
vc4/ vc4/ vc4/ vc4/

vc4-17 vc4-18 vc4-19 vc4-20
vc4/ vc4/ vc4/ vc4/

vc4-21 vc4-22 vc4-23 vc4-24
vc4/ vc4/ vc4/ vc4/

vc4-25 vc4-26 vc4-27 vc4-28
vc4/ vc4/ vc4/

vc4-29 vc4-30 vc4-31
Figure 63: Cross connections in the VC-4 layer
Please note:
The logical SDH ports sdh-5 to sdh-8 are only available with equipment protection
of the SAMOx unit, i.e. using a working and a protecting SAMOx unit.
The following unidirectional and bidirectional cross connections are configurable:

Table 33: VC-4 layer cross connections

a-End z-End Cross connection
/sdh/sdh-x/j-x /sdh/sdh-y/j-y Connects a VC-4 signal from an SDH port to itself or to another VC-4 sig-
nal on an SDH port.
This cross connection is used for through connected VC-4 signals or can
be used for maintenance purposes. i.e. to loop a VC-4 back towards the
SDH port using a unidirectional cross connection.
There is no restriction in the number of through connected VC-4.
/sdh/sdh-x/j-x /vc4/vc4-y Connects a VC-4 signal from an SDH port to an internal VC-4.
This cross connection is used for terminating signals below the VC-4
layer, i.e. signals of the VC-3 or VC-12 layer.
The maximum number of terminated VC-4 is 31.
/vc4/vc4-x /sdh/sdh-y/j-y Connects a VC-4 signal from an internal VC-4 to an SDH port.
This cross connection is used for terminating signals below the VC-4
layer, i.e. signals of the VC-3 or VC-12 layer.
/sdh/sdh-x/j-x /eos/eos-y/eos/ Connects a VC-4 signal from an SDH port to an EoS VC-4 member.
vc4-y This cross connection is used for Ethernet transport over virtually con-
catenated or non concatenated VC-4.
The maximum number of terminated VC-4 is 12, including the number of
VC-4 used for the EoS VC-3 and 252 VC-12 members.
/eos/eos-x/eos/ /sdh/sdh-y/j-y Connects a VC-4 signal from an EoS VC-4 member to an SDH port.
vc4-x This cross connection is used for Ethernet transport over virtually con-
The maximum number of terminated VC-4 is 12, including the number of
VC-4 used for the EoS VC-3 and 252 VC-12 members.
In the VC-4 layer the following SNC protections can be configured:
Table 34: VC-4 layer protection cross connections

a-End working a-End protect- z-End Protection
ing
/sdh/sdh-x/j-x /sdh/sdh-y/j-y /sdh/sdh-z/j-z Protects an outgoing VC-4 signal by two incoming
VC-4 signals from one or two SDH ports.
This cross connection is used for protected VC-4
through traffic.
/sdh/sdh-x/j-x /sdh/sdh-y/j-y /vc4/vc4-z Protects an internal VC-4 by two incoming VC-4 sig-
nals from one or two SDH ports.
This cross connection is used for protected termi-
nating signals below the VC-4 layer, i.e. signals of
the VC-3 or VC-12 layer.
/sdh/sdh-x/j-x /sdh/sdh-y/j-y /eos/eos-z/eos/ Protects an EoS VC-4 member by two incoming VC-4
vc4-z signals from one or two SDH ports.
This cross connection is used for protected Ethernet
transport over virtually concatenated or non concat-
enated VC-4.

VC-3 cross connections on SAMOx are used for Ethernet access and for through connected
VC-3 traffic.
VC-3 cross connections can only be done on a single SAMOx unit. There is no way to access a
VC-3 signal on another SDH unit.
• VC-3 resources belonging to an internal VC-4 must be created in the “/unit-x/vc4/vc4-y” con-
figuration.

• EoS resources (VCG members) must be created in the “/unit-x/eos/eos-y/eos” configuration.

• /unit-x/vc4/vc4-y/klm-z00, e.g. /unit-4/vc4/vc4-1/klm-100:
z = 1 to 3 (TU-3 number)
vc4-y/klm-z00 are all VC-3 signals handled in the TU-3 cross connect of the SAMOx unit.
The maximum number of available VC-3 in SAMOx is 48.
Please note:
All VC-3 signals used for through connected VC-3 traffic or used for EoS transport
must pass the TU-3 cross connect of the SAMOx unit.
→ When using 24 VC-3 for EoS traffic no capacity is left for through connected
traffic.
The maximum number of available EoS VC-3 members on the SAMOx unit and in a virtual
concatenation group is 24.
vc4/vc4-1 vc4/vc4-2 vc4/vc4-31

klm-100 klm-100 klm-100

klm-200 klm-200 klm-200

klm-300 klm-300 klm-300
vc4/vc4-x/klm-x00 ↔
vc4/ vc4-x/klm-x00 ↔ eos/eos-y/eos/vc3-y
vc4/ vc4-y/klm-y00
.../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/

vc3-1 vc3-2 vc3-3 vc3-4

vc3-5 vc3-6 vc3-7 vc3-8

vc3-9 vc3-10 vc3-11 vc3-12

vc3-13 vc3-14 vc3-15 vc3-16

vc3-17 vc3-18 vc3-19 vc3-20

vc3-21 vc3-22 vc3-23 vc3-24

Please note:
The EoS capacity of 12 VC-4 must be shared between the EoS VC-4 members
and the EoS VC-3 members.
Please note:
If also EoS VC-12 members are configured the EoS capacity for VC-4 and VC-3
members is reduced to 8 VC-4 equivalents:
→ Up to 8 VC-4 equivalents for VC-4 and VC-3 members,
→ Up to 4 VC-4 equivalents for VC-12 members.

/vc4/vc4-x/klm-x00 /vc4/vc4-y/klm-y00 Connects a VC-3 to itself or to another VC-3 signal.
This cross connection is used for through connected VC-3 signals or
can be used for maintenance purposes. i.e. to loop a VC-3 back
towards the internal VC-4 using a unidirectional cross connection.
/vc4/vc4-x/klm-x00 /eos/eos-y/eos/ Connects a VC-3 signal from an internal VC-4 to an EoS VC-3 member.
vc3-y This cross connection is used for Ethernet transport over virtually
concatenated or non concatenated VC-3.
/eos/eos-x/eos/ /vc4/vc4-y/klm-y00 Connects a VC-3 signal from an EoS VC-3 member to an internal VC-4.
vc3-x This cross connection is used for Ethernet transport over virtually
concatenated or non concatenated VC-3.
In the VC-3 layer the following SNC protections can be configured:
Please note:
The working and the protecting path of an SNC protected connection must be
located on the same SAMOx unit or on an equipment protected pair of SAMOx
units.

a-End working a-End protecting z-End Protection
/vc4/vc4-x/klm-x00 /vc4/vc4-y/klm-y00 /vc4/vc4-z/klm-z00 Protects an outgoing VC-3 by two incoming VC-
3 signals from one or two internal VC-4.
This cross connection is used for protected
through connected VC-3 signals.
/vc4/vc4-x/klm-x00 /vc4/vc4-y/klm-y00 /eos/eos-z/eos/ Protects an EoS VC-3 member by two incoming
vc3-z VC-3 signals from one or two internal VC-4.
This cross connection is used for protected
Ethernet transport over virtually concatenated
or non concatenated VC-3.

VC-12 cross connections on SAMOx can be used for Ethernet access, for E12 ports, for PBUS
access and for through connected VC-12 traffic.
VC-12 cross connections can only be done on a single SAMOx unit. There is no way to connect
two VC-12 signals on different SDH units.
• VC-12 resources being part of an internal VC-4 must be created at the AP: /unit-x/vc4/vc4-y.
• VC-12 resources for the E12 front ports are available at the AP: /unit-x/port-y.

• EoS resources (VCG members) must be created at the AP: /unit-x/eos/eos-y/eos.

• VC-12 resources for the PBUS access are all available at the AP: /unit-x/pdh.
• /unit-a/vc4/vc4-b/klm-xyz, e.g. /unit-4/vc4/vc4-1/klm-121:
b = 1 to 31 (VC-4 number)
x = 1 to 3 (TUG-3 number)
y = 1 to 7 (TUG-2 number)
z = 1 to 3 (TU-12 number)
vc4-y/klm-xyz are all VC-12 signals terminated or through connected on the SAMOx unit.
The maximum number of available VC-12 in SAMOx is 945.
• /unit-x/port-y/vc12, e.g. /unit-4/port-101/vc12 (SAMO3 only):
y = 101 to 148 (E12 port number)
port-y/vc12 are the VC-12 signals whose contained P12 signals access the E12 front ports.
The number of available VC-12 members for the E12 front ports is fixed to 48.
The maximum number of available VC-12 members on the SAMOx unit is 252. The maxi-
mum number of available VC-12 members in a virtual concatenation group is 63.
• /unit-x/pdh/vc12-z, e.g. /unit-4/pdh/vc12-1:
z = 1 to 64 (VC-12 number)
pdh/vc12-z are the VC-12 signals whose contained P12 signals can access the PBUS. The
number of available VC-12 members in the pdh access point is fixed to 64.

vc4/vc4-1/ vc4/vc4-2/ vc4/vc4-30/ vc4/vc4-31/

klm-111 klm-111 klm-111 klm-111

klm-112 klm-112 klm-112 klm-112

klm-372 klm-372 klm-372 klm-372

klm-373 klm-373 klm-373 klm-373
vc4/vc4-x/klm-xyz ↔ vc4/ vc4-x/klm-xyz ↔ vc4/vc4-x/klm-xyz ↔

eos/eos-y/eos/vc12-y vc4/ vc4-x/klm-xyz ↔ pdh/ vc12-y port-x/vc12
vc4/ vc4-y/klm-abc
.../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/ pdh/ pdh/ pdh/

vc12-1 vc12-2 vc12-3 vc12-1 vc12-2 vc12-3
.../eos-y/eos/ .../eos-y/eos/ pdh/ pdh/

vc12-62 vc12-63 vc12-63 vc12-64
.../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/ port-101/ port-102/ port-103/

vc12-64 vc12-65 vc12-66 vc12 vc12 vc12
.../eos-y/eos/ .../eos-y/eos/ port-147/ port-148/

vc12-125 vc12-126 vc12 vc12
SAMO3
.../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/ only
vc12-127 vc12-128 vc12-129
.../eos-y/eos/ .../eos-y/eos/
vc12-188 vc12-189
.../eos-y/eos/ .../eos-y/eos/ .../eos-y/eos/

vc12-190 vc12-191 vc12-192
.../eos-y/eos/ .../eos-y/eos/
vc12-251 vc12-252


/vc4/vc4-x/klm- /vc4/vc4-a/klm- Connects a VC-12 to itself or to another VC-12 signal.
xyz abc This cross connection is used for through connected VC-12 signals or can
be used for maintenance purposes. i.e. to loop a VC-12 back towards the
internal VC-4 using a unidirectional cross connection.
/vc4/vc4-x/klm- /port-y/vc12 Connects a VC-12 signal from an internal VC-4 to a VC-12 accessing an
xyz E12 front port (SAMO3 only).
This cross connection is used for E12 front port access with unstruc-
tured P12 signals.
The maximum number of VC-12 with E12 port access is 48.
/port-y/vc12 /vc4/vc4-a/klm- Connects a VC-12 signal accessing an E12 front port to a VC-12 going to
abc an internal VC-4 (SAMO3 only).
This cross connection is used for E12 front port access with unstruc-
tured P12 signals.
The maximum number of VC-12 with E12 port access is 48.
/vc4/vc4-x/klm- /eos/eos-y/eos/ Connects a VC-12 signal from an internal VC-4 to an EoS VC-12 member.
xyz vc12-y This cross connection is used for Ethernet transport over virtually con-
The maximum number of terminated VC-12 is 252 per SAMO3 unit. The max-
imum number of terminated VC-12 is 63 per virtual concatenation group.
/eos/eos-x/eos/ /vc4/vc4-a/klm- Connects a VC-12 signal from an EoS VC-12 member to an internal VC-4.
vc12-x abc This cross connection is used for Ethernet transport over virtually con-
The maximum number of terminated VC-12 is 252 per SAMO3 unit. The max-
imum number of terminated VC-12 is 63 per virtual concatenation group.
/vc4/vc4-x/klm- /pdh/vc12-y Connects a VC-12 signal from an internal VC-4 to a VC-12 accessing the
xyz PBUS.
This cross connection is used for PBUS access with structured and
unstructured P12 signals.
The maximum number of VC-12 with PBUS access is 64.
/pdh/vc12-x /vc4/vc4-a/klm- Connects a VC-12 signal accessing the PBUS to a VC-12 going to an inter-
abc nal VC-4.
This cross connection is used for PBUS access with structured and
unstructured P12 signals.
The maximum number of VC-12 with PBUS access is 64.

It is possible to create a connection between a VC-12 EoS member and a PDH
VC-12 or E12 port VC-12.
→ Since the EoS mapping and the VC-12 with PDH mapping are not compatible
this cross connection makes no sense.
The following SNC protections can be configured in the VC-12 layer:
Please note:
The working and the protecting path of an SNC protected connection must be
located on the same SAMOx unit or on an equipment protected pair of SAMOx
units.

ing
/vc4/vc4-x/klm- /vc4/vc4-a/klm- /vc4/vc4-d/klm- Protects an outgoing VC-12 by two incoming VC-12
xyz abc def signals from one or two internal VC-4.
This cross connection is used for protected through
connected VC-12 signals.

Table 38: VC-12 layer protection cross connections (continued)

ing
/vc4/vc4-x/klm- /vc4/vc4-a/klm- /port-y/vc12 Protects a VC-12 signal with access to an E12 front
xyz abc port by two incoming VC-12 signals from one or two
internal VC-4 (SAMO3 only).
This cross connection is used for protected E12
front port access.
/vc4/vc4-x/klm- /vc4/vc4-a/klm- /eos/eos-z/eos/ Protects an EoS VC-12 member by two incoming VC-
xyz abc vc12-z 12 signals from one or two internal VC-4.
This cross connection is used for protected Ethernet
transport over virtually concatenated or non concat-
enated VC-12.
/vc4/vc4-x/klm- /vc4/vc4-a/klm- /pdh/vc12-z Protects a VC-12 signal with PBUS access by two
xyz abc incoming VC-12 signals from one or two internal VC-
4.
This cross connection is used for protected P12
PBUS access.
The switching type of this SNC protection can be
configured to be unidirectional or bidirectional.
6.1.4 P12 Cross Connections

P12 cross connections on SAMOx are used for PBUS access.
P12 resources on SAMOx are enabled by the P12 configuration of the PDH VC-12 signals to
one of the following P12 modes:
− Transparent,
− Clock master.
Please note:
The P12 resources of the E12 front ports on the SAMO3 unit require no cross con-
nection.
→ The E12 ports (/unit-x/port-y) have an inherent and invisible P12 cross connec-
tion to their VC-12 resource (/unit-x/port-y/vc12).
The following signal types are available on the P12 layer:
• /unit-x/pdh/vc12-y/p12/chan-z, e.g. unit-4/pdh/vc12-1/p12/chan-1:
z = 1 (channel index)
vc12-y/p12/chan-z are all unterminated P12 signals demapped from a VC-12 of the SAMOx
unit. The maximum number of available P12 channels in SAMOx is 64.
pdh/vc12-1/ pdh/vc12-2/ pdh/vc12-3/ pdh/vc12-63/ pdh/vc12-64/

p12/chan-x p12/chan-x p12/chan-x p12/chan-x p12/chan-x
pdh/vc12-x/p12/chan-x ↔
pdh/ vc12-x/p12/chan-x ↔ TDM service unit/chan-y
pdh/ vc12-y/p12/chan-y
PBUS Access
Figure 66: Cross connections in the P12 layer

Table 39: P12 layer cross connections

/pdh/vc12-x/p12/ <TDM service Cross connection between the SAMOx unit and another PBUS unit:
chan-x unit>/chan-y Connects an unterminated P12 signal from a VC-12 to the PBUS.
This cross connection is used for unterminated P12 signals using the
PBUS.
The maximum number of P12 signals accessing the PBUS is 64.
<TDM service /pdh/vc12-x/p12/ Cross connection between another PBUS unit and the SAMOx unit.
unit>/chan-y chan-x Connects an unterminated P12 signal from a VC-12 to the PBUS.
This cross connection is used for unterminated P12 signals using the
PBUS.
The maximum number of P12 signals accessing the PBUS is 64.
/pdh/vc12-x/p12/ /pdh/vc12-y/p12/ Cross connection on the same SAMOx unit:
chan-x chan-y Connects an unterminated P12 to itself or to another P12 signal.
This cross connection is mainly used for maintenance purposes. i.e. to
loop a P12 back towards the VC-12 using a unidirectional cross connec-
tion.
The following SNC protections can be configured in the P12 layer:
Table 40: P12 layer protection cross connections

ing
/pdh/vc12-x/p12/ /pdh/vc12-y/p12/ <TDM service Cross connection between the SAMOx unit and another
chan-x chan-y unit>/chan-z PBUS unit:
Protects a P12 signal on another PBUS unit by two
P12 signals from the same or different SAMOx units.
This cross connection is used for protected untermi-
nated P12 signals using the PBUS.
Please refer to Figure 54: "P12 SNCP/I from the net-
work side with two SAMOx units" (on page 88).
<TDM service <TDM service /pdh/vc12-z/p12/ Cross connection between the SAMOx unit and another
unit>/chan-x unit>/chan-y chan-z PBUS unit:
Protects a P12 signal on the SAMOx unit by two P12
signals coming from other PBUS units.
This cross connection is used for protected untermi-
Please refer to Figure 53: "P12 SNCP/I from the tribu-
tary side" (on page 87).
/pdh/vc12-x/p12/ /pdh/vc12-y/p12/ /pdh/vc12-z/p12/ Cross connection on the same or different SAMOx
chan-x chan-y chan-z units:
Protects an outgoing P12 signal by two incoming P12
signals.
connected P12 signals.
Note that this type of protection requires three
(P12) PBUS access resources.
For more information about the P12 connection termination points and the P12 cross connection
configuration refer to [1KHW002467] User Manual “TDM Services”.
6.1.5 P0-nc Cross Connections

P0-nc cross connections on SAMOx are used for PBUS access.
P0-nc resources on SAMOx are enabled by the P12 configuration of the PDH VC-12 signals to
one of the following P12 modes:
− PCM30,

− PCM30C,
− PCM31,
− PCM31C,
− V5 uplink,
− V5 uplink NCI.
Other P0-nc resources are the DCC of the RS (dccr) and MS (dccm) layer of the SDH ports.
The DCC must be enabled by the FOXCST configuration.
The following signal types are available on the P0-nc layer:
• /unit-x/pdh/vc12-y/p12/chan-z, e.g. unit-4/pdh/vc12-1/p12/chan-1:
z = 1 to 32 (channel index)
vc12-y/p12/chan-z are all single or concatenated timeslots of a terminated P12 signal,
mapped/demapped to/from a VC-12 of the SAMOx unit. Time slot 0 is not accessible, time
slot 16 is only accessible if CAS is disabled. The maximum number of available P0-nc chan-
nels in SAMOx is 64 x 31 = 1984.
• /unit-x/sdh/sdh-y/dccr, e.g. unit-4/sdh/sdh-1/dccr:
y = 1 to 8 (logical SDH port number)
dccr are all concatenated timeslots with n=3 (RS DCC).
• /unit-x/sdh/sdh-y/dccm, e.g. unit-4/sdh/sdh-1/dccm:
y = 1 to 8 (logical SDH port number)
dccm are all concatenated timeslots with n=9 (MS DCC).
pdh/vc12-1/ pdh/vc12-2/ pdh/vc12-64/ sdh/sdh-1/ sdh/sdh-2/ sdh/sdh-1/ sdh/sdh-2/

p12/chan-x p12/chan-x p12/chan-x dccr dccr dccm dccm

p12/chan-y p12/chan-y p12/chan-y dccr dccr dccm dccm
sdh/sdh-5/ sdh/sdh-6/ sdh/sdh-5/ sdh/sdh-6/

dccr dccr dccm dccm

p12/chan-z p12/chan-z p12/chan-z dccr dccr dccm dccm
pdh/vc12-x/p12/chan-x ↔ sdh/sdh-y/dccr ↔ sdhPort s/sdh-y/dccm ↔

pdh/vc12-y/p12/chan-y sdh/sdh-z/dccr sdh/sdh-z/dccm
sdh/sdh-y/dccr ↔ sdh/sdh-y/dccm ↔
TDM service unit/chan-y TDM service unit/chan-y
pdh/ vc-12-x/p12/chan-x ↔
PBUS Access PBUS Access
PBUS Access
sdh/sdh-y/dccr ↔ sdh/sdh-y/dccm ↔
management Network/ management Network/
tdmInterf aces/ppp-y tdmI nterf aces/ ppp-z
PBUS Access PBUS Access
Figure 67: Cross connections in the P0-nc layer
Please note:

Table 41: P0-nc layer cross connections

/pdh/vc12-x/p12/ <TDM service Cross connection between the SAMOx unit and another PBUS unit:
chan-x unit>/chan-y Connects a P0-nc channel from a VC-12 to the PBUS.
This cross connection is used for terminated P12 signals using the PBUS.
The maximum number of P0-nc signals accessing the PBUS is 1984.
<TDM service /pdh/vc12-x/p12/ Cross connection between another PBUS unit and the SAMOx unit:
unit>/chan-y chan-x Connects a P0-nc channel from a VC-12 to the PBUS.
This cross connection is used for terminated P12 signals using the PBUS.
The maximum number of P0-nc signals accessing the PBUS is 1984.
/pdh/vc12-x/p12/ /pdh/vc12-y/p12/ Cross connection on the same SAMOx unit:
chan-x chan-y Connects a P0-nc channel from a VC-12 to itself or to another P0-nc
channel.
This cross connection is mainly used for maintenance purposes. i.e. to
loop a P0-nc channel back towards the VC-12 using a unidirectional cross
connection.
/sdh/sdh-x/dccr /managementNet- Cross connection between the SAMOx unit and the FOX61x management
work/tdmInter- router:
faces/ppp-y Connects a RS DCC to a PPP signal of the FOX61x management router.
The maximum number of RS DCC accessing the PBUS is 8.
/sdh/sdh-x/dccr /sdh/sdh-y/dccr Cross connection on the same or another SAMOx unit:
Connects a P0-nc channel from a RS DCC to itself or to another RS DCC.
/sdh/sdh-x/dccr <TDM service Cross connection between the RS DCC and the same or another PBUS
unit>/chan-y unit:
Connects a P0-nc channel from a RS DCC to a P0-nc channel with 3 time
slots in a P12.
/sdh/sdh-x/dccm /managementNet- Cross connection between the SAMOx unit and the FOX61x management
work/tdmInter- router:
faces/ppp-y Connects a MS DCC to a PPP signal of the FOX61x management router.
The maximum number of MS DCC accessing the PBUS is 8.
/sdh/sdh-x/dccm /sdh/sdh-y/dccm Cross connection on the same or another SAMOx unit:
Connects a P0-nc channel from a MS DCC to itself or to another MS DCC.
/sdh/sdh-x/dccm <TDM service Cross connection between the MS DCC and the same or another PBUS
unit>/chan-y unit:
Connects a P0-nc channel from a MS DCC to a P0-nc channel with 9 time
slots in a P12.
The following SNC protections can be configured in the P0-nc layer:
Table 42: P0-nc layer protection cross connections

ing
/pdh/vc12-x/p12/ /pdh/vc12-y/p12/ <TDM service Cross connection between the SAMOx unit and another
chan-x chan-y unit>/chan-z PBUS unit:
Protects a P0-nc signal on another PBUS unit by two
P0-nc signals from the same or different SAMOx units.
<TDM service <TDM service /pdh/vc12-z/p12/ Cross connection between the SAMOx unit and other
unit>/chan-x unit>/chan-y chan-z PBUS units:
Protects a P0-nc signal on the SAMOx unit by two P0-
nc signals coming from other PBUS units.

Table 42: P0-nc layer protection cross connections (continued)

ing
/pdh/vc12-x/p12/ /pdh/vc12-y/p12/ /pdh/vc12-z/p12/ Cross connection on the same or different SAMOx
chan-x chan-y chan-z units:
Protects an outgoing P0-nc signal by two incoming
P0-nc signals.
connected P0-nc signals.
/sdh/sdh-x/dccr /sdh/sdh-y/dccr /managementNet- Cross connection between one or two SAMOx units and
work/tdmInter- the FOX61x management router:
faces/ppp-z Protects a PPP signal on the management router by two
RS DCC signals from the same or different SAMOx
units.
/sdh/sdh-x/dccr /sdh/sdh-y/dccr <TDM service Cross connection between one or two SAMOx units and
unit>/chan-y another PBUS unit.
RS DCC signals from the same or different SAMOx
units.
<TDM service <TDM service /sdh/sdh-z/dccr Cross connection between the SAMOx unit and other
unit>/chan-x unit>/chan-y PBUS units:
Protects a RS DCC on the SAMOx unit by two P0-nc
channels with 3 time slots coming from other PBUS
units.
/sdh/sdh-x/dccr /sdh/sdh-y/dccr /sdh/sdh-z/dccr Cross connection on the same or different SAMOx
units:
Protects an outgoing RS DCC by two incoming RS
DCC.
/sdh/sdh-x/dccm /sdh/sdh-y/dccm /managementNet- Cross connection between one or two SAMOx units and
work/tdmInter- the FOX61x management router:
faces/ppp-z Protects a PPP signal on the management router by two
MS DCC signals from the same or different SAMOx
units.
/sdh/sdh-x/dccm /sdh/sdh-x/dccm <TDM service Cross connection between one or two SAMOx units and
unit>/chan-y another PBUS unit.
MS DCC signals from the same or different SAMOx
units.
<TDM service <TDM service /sdh/sdh-z/dccm Cross connection between the SAMOx unit and other
unit>/chan-x unit>/chan-y PBUS units:
Protects a MS DCC on the SAMOx unit by two P0-nc
channels with 9 time slots coming from other PBUS
units.
/sdh/sdh-x/dccm /sdh/sdh-y/dccm /sdh/sdh-z/dccm Cross connection on the same or different SAMOx
units:
Protects an outgoing MS DCC by two incoming MS
DCC.
For more information about the P0-nc connection termination points and the P0-nc cross con-
nection configuration refer to [1KHW002467] User Manual “TDM Services”.
6.1.6 Cross Connection Examples

In the following the cross connection configuration steps are given for some application exam-
ples. Note that all connection termination points (CTP) are on the SAMOx unit except where
indicated otherwise (e.g. LEDE1).

Table 43: EoS with 4 VC-4

CTP a-End CTP z-End Layer
/unit-4/sdh/sdh-1/j-1 /unit-4/eos/eos-1/eos/vc4-1 VC4
/unit-4/sdh/sdh-1/j-2 /unit-4/eos/eos-1/eos/vc4-2

/unit-4/sdh/sdh-1/j-1 /unit-4/vc4/vc4-1 VC4
/unit-4/sdh/sdh-1/j-2 /unit-4/vc4/vc4-2
/unit-4/vc4/vc4-1/klm-100 /unit-4/eos/eos-1/eos/vc3-1 VC3
/unit-4/vc4/vc4-1/klm-200 /unit-4/eos/eos-1/eos/vc3-2

/unit-4/vc4/vc4-1/klm-111 /unit-4/eos/eos-1/eos/vc12-1 VC12
Table 46: Through connection with 3 VC-4

/unit-4/sdh/sdh-1/j-1 /unit-4/sdh/sdh-2/j-1 VC4
/unit-4/sdh/sdh-1/j-2 /unit-4/sdh/sdh-2/j-2
/unit-4/sdh/sdh-1/j-3 /unit-4/sdh/sdh-2/j-3
Table 47: Through connection with 3 VC-3

/unit-4/sdh/sdh-2/j-1 /unit-4/vc4/vc4-2
/unit-4/vc4/vc4-1/klm-100 /unit-4/vc4/vc4-2/klm-100 VC3
/unit-4/vc4/vc4-1/klm-200 /unit-4/vc4/vc4-2/klm-200
/unit-4/vc4/vc4-1/klm-300 /unit-4/vc4/vc4-2/klm-300
Table 48: E12 front port access with 2 VC-12

/unit-4/vc4/vc4-1/klm-111 /unit-4/port-101/vc12 VC12
/unit-4/vc4/vc4-1/klm-112 /unit-4/port-102/vc12
Table 49: PBUS access with 2 P12

/unit-4/vc4/vc4-1/klm-111 /unit-4/pdh/vc12-1 VC12
/unit-4/vc4/vc4-1/klm-112 /unit-4/pdh/vc12-2
/unit-4/pdh/vc12-1/p12/chan-1 LEDE1/port-1/chan-1 1 P12
/unit-4/pdh/vc12-2/p12/chan-1 LEDE1/port-2/chan-1 2
1. LEDE1 port-1 is configured to an unterminated P12 mode.

2. LEDE1 port-2 is configured to an unterminated P12 mode.
Table 50: PBUS access with 2 P0-nc

/unit-4/vc4/vc4-1/klm-111 /unit-4/pdh/vc12-1 VC12
/unit-4/pdh/vc12-1/p12/chan-1 1 LEDE1/port-1/chan-1 3 P0-nc
/unit-4/pdh/vc12-1/p12/chan-2 2 LEDE1/port-1/chan-2 3
1. chan-1 comprises n time slots.

2. chan-2 comprises m time slots.
3. LEDE1 port-1 is configured to a terminated P12 mode. chan-1 comprises n time slots. chan-2 comprises m time slots.
6.2 SNCP Configuration
6.2.1 SNCP Timer Configuration

In the revertive mode of SNC protection the path selector switches back to the working path as
soon as the configured “wait to restore” (WTR) timer elapses. The WTR timer is reset when the
working path is in a failure state and starts when the working path becomes fault free.
The “holdoff” time is the time interval to define how long the switching criteria have to be active
before the protection switching is activated.
The “guard time” is the time interval after an automatic protection switchover when no additional
switchover is allowed. During the guard time the path selector does not switch back to the work-
ing path even if the protecting path becomes faulty.
Working
channel
failed
OK
time
Protecting
channel
failed
OK
time
holdoff time guard time
Protection
switch
protecting
working
time
Figure 68: Holdoff and guard times
The SNCP “wait to restore”, “holdoff” and “guard time” timers are configured per VC type for the
whole unit.

Please note:
The SNCP “wait to restore”, “holdoff” and “guard time” timers are not supported for
the E12 front port protection switching.
6.2.2 SNCP Degraded Signal Configuration

The threshold level to set a degraded signal defect can be configured per VC type for the whole
SAMOx unit.
Please refer to section 7.3 Detection of Signal Defects (on page 136) for a description of the
degraded signal defect evaluation.
6.3 Automatic Laser Shutdown and Restart

ALS and ALR are implemented according to ITU-T G.664.
Please note:
The SAMOx supports the same parameters for SFP modules with optical and elec-
trical STM-1 interfaces. Accordingly the electrical STM-1 interface supports also
management functions that are normally only applicable for the optical interface,
such as laser shutdown and laser restart.
6.3.1 Automatic Laser Shutdown

Automatic laser shutdown (ALS) is a technique to automatically shutdown the output power of
laser transmitters to avoid exposure to hazardous levels.
With this option enabled, the laser transmitter automatically shuts down when the received opti-
cal signal is lost (LOS) for more than 500 ms. The shutdown is activated within 850 ms after the
“loss of light” at the receiver input.
As soon as a valid optical signal is received, the laser is restarted.

ALS enabled
Section in operation,
TX power on
yes Receive signal

from far end?
no
no LOS for more

than 500 ms?
yes
Automatic TX
power shutdown
Figure 69: Automatic laser shutdown (ALS)
6.3.2 Automatic Laser Restart

After an automatic laser shutdown, the laser can be restarted in several ways to get the section
operational again:
• Automatic laser restart
With the automatic laser restart enabled, the laser automatically restarts periodically for 2 ±
0.25 s at an interval of 110 s.
• Manual laser restart (maintenance function)
The manual laser restart activates the laser for 2 ± 0.25 s.
• Manual laser restart for test (maintenance function)
The manual laser restart for test activates the laser for 90 ± 10 s.

TX power off
Automatic restart Manual restart

Manual restart
for test
Delay
110 s
TX power on TX power on TX power on

for 2 ± 0.25 s for 2 ± 0.25 s for 90 ± 10 s
no Receive signal
from far end?
yes
Section in operation,
TX power on
Figure 70: Automatic laser restart (ALR)
6.4 Commissioning Example of PDH and EoS Transport
6.4.1 Prerequisites
Before starting the commissioning of an SDH multiplexer for PDH and EoS transport on the
SAMOx unit, the following prerequisites need to be fulfilled.
6.4.1.1 Core unit

In a FOX61x, a core unit needs to be in operation in slot 11 of the FOX61x subrack.
6.4.1.2 SAMOx unit

The SAMOx service unit is inserted into a slot of the FOX61x subrack. Available slots are listed
in section 4.2 Slots for the SAMOx Unit (on page 31).
A valid ESW is installed on the SAMOx unit. For the management of ESW, refer to
[1KHW002466] User Manual “FOXCST”. For details about compatible ESW versions, refer to
6.4.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”.
The amount and accessibility of operations depend on the user profile with which you are
logged in. For more information, please refer to [1KHW028522] User Manual “Management
Communication”.

6.4.2 Configuration of the SDH Multiplexer
SDH multiplexer configuration with SAMO3

This action list shows step by step how to configure the SDH multiplexer for PDH and EoS
transport. The multiplexer transports
- Ethernet traffic of Ethernet port 5 in a single VC-4, using the unswitched Ethernet transport
mode with EoS port 1,
- Ethernet traffic of Ethernet port 6 in two concatenated VC-3, using the switched Ethernet
transport mode with EoS port 2,
- The Ethernet port 6 and the EoS port 2 are access ports of the VLAN bridge, using the port
VLAN ID 1,
- two P12 signals from the SAMO3 E12 front ports 101 and 102.
- two P12 signals in transparent mode from the LEDE1 ports 1 and 2.
- The Ethernet traffic is transported via j-1 (AU4-1) and j-2 (AU4-2) of the SDH port 1,
- the PDH traffic from the E12 front ports is transported in unprotected mode via j-2 (AU4-2) of
the SDH port 1.
- the PDH traffic from the LEDE1 ports is transported in protected mode via j-2 (AU4-2) of the
SDH port 1 and via j-1 (AU4-1) of the SDH port 2.
For the configuration of the SDH multiplexer for PDH and EoS transport, the following steps
have to be performed. The main steps are:
• Configure the port type of the Ethernet and EoS ports
• Configure the Ethernet transport mode
• Configure the physical SDH ports
• Configure the logical SDH ports
• Configure the physical Ethernet ports
• Configure the EoS ports
• Configure the physical E12 ports
• Create and configure the VC-4 resources with TUG-3 structure
• Configure the VC-12 and P12 signals used for the PDH traffic
• Create the channels on the P12 signals
• Configure the E12 interface unit
• Create the cross connections to the EoS group members
• Create the cross connections to the SAMO3 E12 ports
• Create the cross connections to the LEDE1 E12 ports
• Configure the SETS
• Activate the SAMO3 SDH, Ethernet and E12 ports
• Activate the VC-4 and VC-12 resources
• Activate the LEDE1 E12 ports

port-1 port-2
SDH SDH
sdh-1 sdh-2
j-1 j-2 j-1
vc4 vc4
vc4-1 vc4-2

klm100 klm200 klm311 klm312 klm313 klm321 klm111 klm112
eos-1 eos-2 eos-2

vc4-1 vc3-1 vc3-2
pdh pdh port-101 port-102

eos-1 eos-2
vc12-1 vc12-2 vc12-1 vc12-1
FOX61x Switch
port-5 port-6 p12 p12 port-101 port-102 SAMO3

ETH ETH chan-1 chan-1 E12 E12
PBUS
LEDE1 port-1 port-2

chan-1 chan-1
port-1 port-2
E12 E12
Figure 71: SAMO3 configuration example
The following assumptions and identifiers are used:

- The SAMO3 unit is assumed to be plugged in slot 4 of the FOX615.
- The SAMO3 unit is assigned.
- Port 1 and port 2 of the SAMO3 unit are equipped with SFP modules supporting STM-4, e.g.
S-4.1.
- The E12 transport unit LEDE1 running with a proper ESW is plugged in slot 20 of the
FOX615. The port-1 and port-2 are used for the PDH traffic.
→ Configure the port type of the Ethernet and EoS ports. Proceed as follows:
1. Navigate to the unit port type configuration:
- FOXCST “Tree View” tab
- AP: /unit-4, Main - Port Type.
2. Configure the Ethernet and EoS ports:
- /unit-4/port-5, Usage = CVP.
- /unit-4/port-6, Usage = CVP.
- /unit-4/eos/eos-1, Usage = CVP.
- /unit-4/eos/eos-2, Usage = CVP.

3. Execute “Apply”.
Result: The port type is configured.
→ Configure the VLAN bridge ports. Proceed as follows:

1. Navigate to the unit VLAN bridge port configuration:
- FOXCST “Switching” tab
- AP: /Switching/Bridges/bridge-1, Ports.
2. Configure the unswitched Ethernet ports:
- /unit-4/port-5, Mode = Unswitched.
- /unit-4/eos/eos-1, Mode = Unswitched.
3. Configure the switched Ethernet ports:
- /unit-4/port-6, Mode = Access, PVID = 1.
- /unit-4/eos/eos-2, Mode = Access, PVID = 1.
Result: The VLAN bridge ports are configured.
→ Configure the Ethernet transport mode. Proceed as follows:

1. Navigate to the unit EPL configuration dialog:
- AP: /unit-4, Configuration - EPL.
2. Configure the EPL handling:
- port-5 = eos-1.
- port-6 = no EPL.
Result: The Ethernet transport mode is configured.
→ Configure the physical SDH port-1. Proceed as follows:

1. Navigate to the port-1 physical section configuration dialog:
- AP: /unit-4/port-1, Configuration - PS.
2. Set the SFP port mode:
- SFP Port Mode = STM-4.
3. Enable the automatic laser shutdown:
- Automatic Laser Shutdown = true.
4. Enable the automatic laser restart:
- Automatic Laser Restart = true.
Result: The physical SDH port 1 is fully configured.
→ Configure the physical SDH port-2. Proceed as follows:

1. Navigate to the port-2 physical section configuration dialog:
- AP: /unit-4/port-2, Configuration - PS.
2. Set the SFP port mode:
- SFP Port Mode = STM-4.
3. Enable the automatic laser shutdown:
- Automatic Laser Shutdown = true.
4. Enable the automatic laser restart:
- Automatic Laser Restart = true.
Result: The physical SDH port 2 is fully configured.

→ Configure the logical SDH port-1. Proceed as follows:

1. Navigate to the logical SDH port-1 regenerator section configuration dialog:
- AP: /unit-4/sdh/sdh-1, Configuration - RS.
2. Set the port mode:
- Port Mode = STM-4.
3. Disable the trail trace identifier supervision:
- TTI Supervision = false.
4. Navigate to the port-1 multiplex section configuration dialog:
- AP: /unit-4/sdh/sdh-1, Configuration - MS.
5. Enable the synchronization status message:
- SSM = true.
6. Select the excessive signal threshold:
- Excessive Defect Threshold = 10E-3.
7. Select the degraded signal threshold:
- Degraded Defect Threshold = 10E-6.
8. Keep the default setting of the input mapping table for the quality levels:
- The adapted QL equals the received QL.
9. Keep the default setting of the output mapping table for the quality levels:
- The adapted QL equals the transmitted QL.
10.Keep the default setting of the synchronization usability of all clock sources:
- sdh-1 = “Do Not Use”.
- All other ports = “Can Be Used”.
11.Navigate to the port-1 multiplex section protection configuration dialog:
- AP: /unit-4/sdh/sdh-1, Configuration - MSP.
12.Disable the multiplex section protection:
- Protection = None.
13.Navigate to the port-1 DCC configuration dialog:
- AP: /unit-4/sdh/sdh-1, Configuration - DCC.
14.Disable the DCC usage:
- DCC Type = None.
15.Execute “Apply”.
Result: The logical SDH port 1 is fully configured.
→ Configure the logical SDH port-2. Proceed as follows:

1. Navigate to the logical SDH port-2 regenerator section configuration dialog:
- AP: /unit-4/sdh/sdh-2, Configuration - RS.
2. Set the port mode:
- Port Mode = STM-4.
4. Navigate to the port-2 multiplex section configuration dialog:
- AP: /unit-4/sdh/sdh-2, Configuration - MS.
5. Enable the synchronization status message:
- SSM = true.
6. Select the excessive signal threshold:
- Excessive Defect Threshold = 10E-3.

7. Select the degraded signal threshold:

- Degraded Defect Threshold = 10E-6.
8. Keep the default setting of the input mapping table for the quality levels:
- The adapted QL equals the received QL.
9. Keep the default setting of the output mapping table for the quality levels:
- The adapted QL equals the transmitted QL.
10.Keep the default setting of the synchronization usability of all clock sources:
- sdh-2 = “Do Not Use”.
- All other ports = “Can Be Used”.
11.Navigate to the port-2 multiplex section protection configuration dialog:
- AP: /unit-4/sdh/sdh-2, Configuration - MSP.
12.Disable the multiplex section protection:
- Protection = None.
13.Navigate to the port-2 DCC configuration dialog:
- AP: /unit-4/sdh/sdh-2, Configuration - DCC.
14.Disable the DCC usage:
- DCC Type = None.
Result: The logical SDH port 2 is fully configured.
→ Configure the physical Ethernet port-5. Proceed as follows:

1. Navigate to the port-5 PHY configuration dialog:
- AP: /unit-4/port-5, Main - Physical.
2. Configure the Ethernet ports MTU size:
- MTU = 1578 Octets.
3. Configure the Ethernet interface speed and duplex mode:
- Admin = Auto.
4. Disable the Ethernet interface flow control:
- Admin = false.
Result: The physical Ethernet port 5 is fully configured.
→ Configure the physical Ethernet port-6. Proceed as follows:

1. Navigate to the port-6 PHY configuration dialog:
- AP: /unit-4/port-6, Main - Physical.
2. Configure the Ethernet ports MTU size:
- MTU = 1578 Octets.
3. Configure the Ethernet interface speed and duplex mode:
- Admin = Auto.
4. Disable the Ethernet interface flow control:
- Admin = false.
Result: The physical Ethernet port 6 is fully configured.
→ Configure the EoS port 1. Proceed as follows:

1. Navigate to the EoS port eos-1 configuration dialog:
- AP: /unit-4/eos/eos-1, Configuration - EoS.
- Execute “Create EoS Group…”.

2. Set the layer rate:

- Layer Rate = VC4.
3. Enable LCAS:
- LCAS = true.
4. Set the number of EoS group members:
- Number Of Members = 1.
5. Execute “OK”.
Result: The EoS port eos-1 is fully configured. The EoS group has one member vc4-1. It
transports the Ethernet traffic from the Ethernet port 5.
→ Configure the EoS port 2. Proceed as follows:

1. Navigate to the EoS port eos-2 configuration dialog:
- AP: /unit-4/eos/eos-2/eos, Configuration - EoS.
- Execute “Create EoS Group…”.
2. Set the layer rate:
- Layer Rate = VC3.
3. Enable LCAS:
- LCAS = true.
4. Set the number of EoS group members:
- Number Of Members = 2.
Result: The EoS port eos-2 is fully configured. The EoS group has two members vc3-1 and
vc3-2. It transports the (untagged) Ethernet traffic from the VLAN bridge with the
switch internal VLAN ID 1.
→ Create the VC-4 resource with TUG-3 structure for EoS and PDH traffic. Proceed as follows:
1. Navigate to the VC-4 configuration dialog:
- AP: /unit-4/vc4, Configuration - General.
- Execute the command “Create VC4”.
2. Configure the VC-4 index:
- Index = 0 (automatically select the next free index).
3. Select the structure of the three TUG-3:
- k-1 = VC3.
- k-2 = VC3.
- k-3 = VC12.
4. Select the number of repetitions:
- Repetitions = 1.
Result: The VC-4 called vc4-1 with the TUG-3 structure is created.
→ Create the VC-4 resource with TUG-3 structure for protected PDH traffic.
Proceed as follows:
1. Navigate to the VC-4 configuration dialog:
- AP: /unit-4/vc4, Configuration - General.
- Execute the command “Create VC4”.
2. Configure the VC-4 index:

3. Select the structure of the three TUG-3:

- k-1 = VC12.
- k-2 = VC3.
- k-3 = VC3.
4. Select the number of repetitions:
- Repetitions = 1.
Result: The VC-4 called vc4-2 with the TUG-3 structure is created.
→ Configure the VC-4 resources with TUG-3 structure. Proceed as follows:

1. Navigate to the VC-4-1 configuration dialog:
- AP: /unit-4/vc4/vc4-1, Configuration - General.
- AP: /unit-4/vc4/vc4-2, Configuration - General.
Result: The VC-4-1 and VC-4-2 are configured.
→ Configure the VC-12 resources for PDH traffic. Proceed as follows:

- AP: /unit-4/pdh/vc12-1, Configuration - General.
- AP: /unit-4/pdh/vc12-2, Configuration - General.
Result: The VC-12 resources are configured.
→ Configure the P12 resources. Proceed as follows:

1. Navigate to the P12 configuration dialog:
- AP: /unit-4/pdh/vc12-1/p12, Configuration - General.
2. Configure the P12 termination mode:
- Mode = Transparent.
- AP: /unit-4/pdh/vc12-2/p12, Configuration - General.
5. Configure the P12 termination mode:
- Mode = Transparent.
Result: The two P12 signals are configured.

→ Create the P12 channels. Proceed as follows:

- AP: /unit-4/pdh/vc12-1/p12, Configuration - Channels.
- Execute the command “Create Channel”.
2. Configure the P12 channel index:
- AP: /unit-4/pdh/vc12-2/p12, Configuration - Channels.
- Execute “Create Channel…”.
5. Configure the P12 channel index:
Result: The two channels chan-1 on the two P12 signals are created.
→ Configure the LEDE1 E12 interface unit. Proceed as follows:

1. On the E12 interface unit LEDE1, two ports (port-1 and port-2) have to be configured to the
“Transparent” termination mode. Please refer to [1KHW002473] User Manual “LEDE1” for
the detail configuration.
Result: The E12 interface unit is configured.
→ Create the cross connection to the EoS group member of eos-1. Proceed as follows:
1. Select the “Cross Connections” tab of the FOXCST “TDM Services” view.
- Click on the “Connection Wizard” button:
- The “Create TDM Connection” dialog opens.
2. Set the connection parameters:
- Layer Rate = VC4.
- Directionality = Bidirectional.
- Protected = No.
- Number = 1.
- Label 1 = <anyName>.
3. Execute “Next ->”.
4. Select the Z-End CTP:
- Select the SAMO3 unit, eos, eos-1, eos, vc4-1.
6. Select the A-End CTP:
- Select the SAMO3 unit, sdh, sdh-1, j-1.
7. Execute “Create”.
Result: The connection from the VC-4 EoS group to the SDH port-1 is created.
→ Create the cross connections to the EoS group members of eos-2. Proceed as follows:


- Layer Rate = VC4.
- Protected = No.
- Number = 1.
- Select the SAMO3 unit, vc4, vc4-1.
Result: The connection from the internal VC-4 with TUG-3 structure to the SDH port-1 is
created.
- Layer Rate = VC3.
- Protected = No.
- Number = 2.
10.Execute “Next ->”.
11.Select the Z-End CTPs:
13.Select the A-End CTPs:
- Select the SAMO3 unit, vc4, vc4-1, klm-100.
14.Execute “Create”.
Result: The two connections from the EoS group members vc3-1 and vc3-2 to the VC-3 of
the internal VC-4 with TUG-3 structure are created.
→ Create the cross connections to the unprotected VC-12 signals (SAMO3 E12 ports).
Proceed as follows:
- Layer Rate = VC12.
- Protected = No.
- Number = 2.

4. Select the Z-End CTPs:

- Select the SAMO3 unit, port-101, vc12.
- Select the SAMO3 unit, port-102, vc12.
6. Select the A-End CTPs:
Result: The two unprotected connections from the internal VC-4 vc4-1 to the two VC-12
are created.
→ Create the cross connections to the protected VC-12 signals (LEDE1 E12 ports).
Proceed as follows:
- Layer Rate = VC4.
- Protected = No.
- Number = 1.
- Select the SAMO3 unit, vc4, vc4-2.
Result: The connection from the second internal VC-4 with TUG-3 structure to the SDH
port-2 is created.
- Layer Rate = VC12.
- Protected = Yes.
- Number = 2.
11.Select the Z-End CTPs:
- Select the SAMO3 unit, pdh, vc12-1.
- Select the SAMO3 unit, pdh, vc12-2.
13.Select the A-End CTPs:

15.Select the A-End Protecting CTPs:

16.Execute “Create”.
Result: The two protected connections from the two internal VC-4 vc4-1 and vc4-2 to the
two VC-12 are created.
→ Create the cross connections to the E12 ports on the LEDE1 unit. Proceed as follows:
- Layer Rate = P12.
- Protected = No.
- Number = 2.
4. Select the Z-End CTPs:
- Select the SAMO3 unit, pdh, vc12-1, p12, chan-1.
- Select the SAMO3 unit, pdh, vc12-2, p12, chan-1.
6. Select the A-End CTPs:
- Select the LEDE1 unit, port-1, chan-1.
- Select the LEDE1 unit, port-2, chan-1.
Result: The connections from the two VC-12 to the LEDE1 E12 port-1 and port-2 are cre-
ated.
→ Configure the SETS. Proceed as follows:

1. Navigate to the configuration dialog:
- AP: /unit-4, Configuration - SETS.
2. In the SETS Clock Selection table select the “sdh-1” row.
3. Configure the clock source parameters:
- Priority = 1.
- QL = Received.
- Holdoff Time = 0.
- Wait-To-Restore Time = 0.
4. In the SETS Clock Selection table select the “sdh-2” row.
5. Configure the clock source parameters:
- Priority = 2.
- QL = Received.
- Holdoff Time = 0.
- Wait-To-Restore Time = 0.
6. Select the clock selection algorithm:
- Selection Algorithm = Priority.
Result: The SETS is fully configured.

→ Activate the SDH, Ethernet and E12 ports. Proceed as follows:

1. AP: /unit-4/port-1, Main - Admin And Oper Status:
- Set the administrative status of the physical SDH port-1 to up:
- State = Up.
- Set the administrative status of the physical SDH port-2 to up:
- State = Up.
5. AP: /unit-4/sdh/sdh-1, Main - Admin And Oper Status:
- Set the administrative status of the logical SDH port-1 to up:
- State = Up.
7. AP: /unit-4/sdh/sdh-2, Main - Admin And Oper Status:
- Set the administrative status of the logical SDH port-2 to up:
- State = Up.
9. AP: /unit-4/port-5, Main - General:
- Set the administrative status of the physical Ethernet port-5 to up:
- Admin Status = Up.
11.AP: /unit-4/port-6, Main - General:
- Set the administrative status of the physical Ethernet port-6 to up:
- Admin Status = Up.
13.AP: /unit-4/eos/eos-1, Main - Admin And Oper Status:
- Set the administrative status of the EoS port eos-1 to up:
- State = Up.
15.AP: /unit-4/eos/eos-2, Main - Admin And Oper Status:
- Set the administrative status of the EoS port eos-2 to up:
- State = Up.
17.AP: /unit-4/port-101, Main - Admin And Oper Status:
- Set the administrative status of the E12 port-101 to up:
- State = Up.
19.AP: /unit-4/port-102, Main - Admin And Oper Status:
- State = Up.
Result: All physical and logical SDH, Ethernet and E12 ports on the SAMO3 unit have
been activated.
→ Activate the VC-4 and VC-12 resources. Proceed as follows:

1. AP: /unit-4/vc4/vc4-1, Main - Admin And Oper Status:
- Make sure the administrative status of the vc4-1 is up:
- State = Up.

3. AP: /unit-4/vc4/vc4-2, Main - Admin And Oper Status:

- Make sure the administrative status of the vc4-2 is up:
- State = Up.
5. AP: /unit-4/pdh/vc12-1, Main - Admin And Oper Status:
- Set the administrative status of the vc12-1 to up:
- State = Up.
7. AP: /unit-4/pdh/vc12-2, Main - Admin And Oper Status:
- Set the administrative status of the vc12-2 to up:
- State = Up.
Result: All VC-4 and VC-12 resources on the SAMO3 unit have been activated.
→ Activate the E12 ports on the LEDE1 unit. Proceed as follows:

- State = Up.
- State = Up.
Result: All E12 ports on the LEDE1 unit have been activated.
End of instruction

FOX61x | SAMO2, SAMO3, SAMO5 OPERATION
7 Operation
This section describes the operation functions of the SAMOx unit.
Please note:
The operation functions described in this section assume a correctly configured
and operational SAMOx unit.
7.1 Unit Optical Indicators

LEDs on the front of the SAMOx unit are used to indicate to the operator the alarm status sum-
mary of the unit and of the network traffic signals.
XXXXx R1B XXXXx R1B

37900374 37900374
UNIT UNIT
TRAFFIC TRAFFIC
Figure 72: Fault indication LEDs on the SAMOx unit
Table 51: LED signaling on SAMOx

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 replace-
ment of unit HW or ESW.
Green / Red Booting or Unit has not been taken in service yet or the unit has not been
(blinking 1 Hz) waiting 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 ser-
vice.
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 VC Loops
There are no dedicated maintenance functions available for the application of VC-4, VC-3 or
VC-12 loops on SAMOx.

To apply a loop on a VC, a unidirectional cross connection must be configured on the desired
path itself.
Please note:
Only the unidirectional cross connections for the front to front loops are applicable.
Please note:
Loops activated with a unidirectional cross connection generate no “maintenance
function active” alarm as regular test loops would do.
SDH
access
network
STM-1/4/16
SAMOx
Front to Front
AU-4 or TU-3 loop
or TU-12
cross connect Back to Back
loop
Figure 73: Loops with unidirectional cross connections
Table 52: Loops with unidirectional cross connections

Loop Signal type Signal name
Front to front VC-4 /unit-x/sdh/sdh-y/j-z
Back to back VC-4 not applicable
Front to front VC-3 /unit-x/vc4/vc4-y/klm-x00 1
Front to front VC-12 /unit-x/vc4/vc4-y/klm-xyz 1
1. This loop requires the corresponding cross connections on the VC-4 layer.
7.2.2 P12 and P0-nc Loops
Please note:
Activated loops generate the “maintenance function active (MFA)” alarm.
Please note:
When applying a loop the operational state of the access point changes to “Test-
ing”.

Please note:
P12 and P0-nc loops are not treated as configuration parameters and are not
stored in the configuration. They are permanent until they are deactivated manually
or by a unit restart or by a power reset.
The following diagnostic loops can be individually set for each of the 48 E12 front ports in the /
unit-x/port-y Status - Maintenance dialog (SAMO3 only):
• E12 front to front loop:
Loops the received E12 signal back towards the E12 interface. The loop is transparent, i.e.
no AIS is transmitted in direction to the SDH interface.
• E12 back to back loop:
Loops the outgoing E12 signal back to the SDH interface. The loop is transparent, i.e. no AIS
is transmitted in the direction of the E12 interface.
Only one of the E12 loops loop can be active at the same time.
SAMO3
Back To Back
STM-1/4/16
Signal SDH
Processing access
E12 port network
(E12)
Front To Front
Figure 74: Loops on the E12 access point
The following diagnostic loops can be individually set for each of the 64 P12 signals in the /unit-
x/pdh/vc12-y/p12 Status - Maintenance dialog or for all P12 and P0-nc channels in the /unit-x/
pdh/vc12-y/p12/chan-z Status - Maintenance dialog:
• P12 front to front loop:
Loops the received P12 signal back towards the SDH interface. The loop is transparent, i.e.
no AIS is transmitted in direction to the PBUS.
Please note:
The P12 “back to back” loop will be available in a future release.
SAMOx
Front To Front
AIS
STM-1/4/16
SDH
Signal access
PBUS
Processing network
(P12)
Back To Back
Figure 75: Loops on the P12 access point
• Channel (P12 and P0-nc) front to front loop:

Loops the received P12 or P0-nc channel signal back towards the SDH interface. The loop is
transparent, i.e. no AIS is transmitted in direction to the PBUS.

Please note:
To be able to activate a diagnostic loop the channel CTP must be the source of a
configured connection.
SAMOx
Front To Front
STM-1/4/16
SDH
Signal access
PBUS
Processing network
(P12)
Figure 76: Loop on the channel access point
It is also possible to apply P12 and P0-nc loops with unidirectional cross connections.
Please note:
Only the unidirectional cross connections for the front to front loops are applicable.
Table 53: Loops with unidirectional cross connections

Loop Signal type Signal name
Front to front P12 /unit-a/pdh/vc12-x/p12/chan-y 1
Front to front P0-nc /unit-a/pdh/vc12-x/p12/chan-y 1
Back to back P0-nc not applicable
1. This loop requires the corresponding cross connections on the VC-4 and VC-12 lay-
ers.
7.3 Detection of Signal Defects

Bit or block errors in a signal are detectable by checking the signal's associated error detection
code (EDC). An example of the EDC is the SDH BIP-N (bit interleaved parity of level N).
The procedure to set and clear an excessive or degraded signal defect is as follows, assuming
a poisson error distribution. Refer to ITU-T G.806, clause 6.2.3.1.1:
• The signal defect is set if the equivalent bit error ratio (BER) exceeds a preset threshold.
• The signal defect is cleared if the equivalent BER is better than the preset threshold divided
by 10.
SAMOx offers the evaluation of the excessive and degraded signal defects on the following lay-
ers:
− MS16
− MS4
− MS1
− VC-4
− VC-3
− VC-12
The thresholds to set a signal defect are configurable in the FOXCST. The configuration is done
individually for the MS16, MS4 and MS1, and per unit for the VC-4, VC-3 and VC-12:

Table 54: Signal defect parameters

Layer EDC Blocks/s Excessive signal defect Degraded signal defect
Threshold range Threshold Threshold range Threshold
default default
MS16 BIP-1 3’072’000 10E-3 … 10E-5 10E-3 10E-5 … 10E-8 10E-6
MS4 BIP-1 768’000 10E-3 … 10E-5 10E-3 10E-5 … 10E-8 10E-6
MS1 BIP-1 192’000 10E-3 … 10E-5 10E-3 10E-5 … 10E-8 10E-6
VC-4 BIP-8 8’000 10E-3 … 10E-5 10E-3 10E-5 … 10E-8 10E-6
VC-3 BIP-8 8’000 10E-3 … 10E-5 10E-3 10E-5 … 10E-8 10E-6
VC-12 BIP-2 2’000 10E-3 … 10E-5 10E-3 10E-5 … 10E-8 10E-6
7.4 Trail Trace Identifier (TTI)

The trail trace identifier (TTI) is a means to identify each direction of a bidirectional path. A
wrong cross connection of the path within the network is detected and generates an alarm.
• At the transmit side, the configured “Transmitted TTI” string is inserted into the TTI byte.
• At the receive side, the received TTI is extracted from the TTI byte. The received TTI is then
compared with the configured “Expected TTI” for that signal.
• If the received TTI and the configured “Expected TTI” are not the same, the trace identifier
mismatch (TIM) alarm indicates a wrong connection somewhere in the network.
SDH
access
network
STM-1/4/16 STM-1/4/16
SAMOx
SAMOx
Transmitted TTI Received TTI
Compare Alarm
Expected TTI
Figure 77: TTI application
The TTI is implemented in accordance with ITU-T G.806. It uses the 16 bytes / 15 characters
format for all layers.
TTI on SAMOx is supported for the following layers:
− RS,
− VC-4 terminated,
− VC-12 terminated,
− EoS VC-4, one transmitted TTI per EoS group, display of the received TTI for every group
member,
− EoS VC-3, one transmitted TTI per EoS group, display of the received TTI for every group
member,

− EoS VC-12, one transmitted TTI per EoS group, display of the received TTI for every
group member,
− P12 (proprietary TTI, future release).
Please note:
In accordance to the ITU-T recommendation, the TTI always requires all the 15
characters. If a TTI is not completely defined, the SAMOx will supplement “NUL”
characters up to a total of 15 characters.
Please note:
The FOX51x service unit SYN4E uses the “NUL” character to fill up a not com-
pletely defined TTI.
→ It is inter-operable with the SAMOx unit with an ESW release samo2_r4c and
newer.

The SAMOx unit with an ESW release samo2_r4b and older uses the “SPACE”
character to fill up a not completely defined TTI.
→ To be inter-operable with the FOX51x service unit SYN4E you have to fill up the
transmitted and expected TTI values in the SYN4E unit with “SPACE” charac-
ters.
7.5 Maintenance
7.5.1 Inventory Data

It is possible to read inventory data from the SAMOx unit via the FOXCST with the following
access point:
AP: /unit-x, Main - Inventory.
7.5.2 Unit ESW Download

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

The assignment of new embedded software restarts the SAMOx unit.
Thus, the installation of new ESW on the unit affects all traffic functions of the
SAMOx unit.
7.5.3 ESW Upgrade with EQP

When upgrading the ESW on 1:1 equipment protected SAMOx units, care must be taken con-
cerning the traffic interruptions and which unit will finally be the active unit. At the end of the
upgrade procedure the working unit shall be the active unit.
The examples below assume that the working unit is plugged in slot 4 and the protecting unit is
plugged in slot 6 of the FOX615 subrack.
ESW upgrade procedure 1

The following procedure provides the upgrade process with one traffic interruption of up to four
minutes.

Please note:
A typical ESW upgrade will interrupt the traffic for a duration as indicated above.
→ The ESW upgrade procedure 2 provides two shorter interruptions.
→ ESW download and start. Proceed as follows:

1. Configure the new ESW file for the working SAMOx unit:
- FOXCST menu Tools - Software Download ….
- Click on the table row with ID “/unit-4”.
- In the “Software to install” column select the software to be downloaded.
- Tick the “Delete unused Software” box.
2. Configure the new ESW file for the protecting SAMOx:
3. Execute the “Download and Start …” command.
- The “Parameters for command Download and Start” dialog opens.
- Select the “Upgrade Units Only” algorithm.
- Click “OK”.
- The new ESW is downloaded and becomes active on the working and the protecting
units.
- Traffic will be interrupted for up to four minutes.
Result: The new ESW is active on the working and the protecting SAMOx units. The work-
ing SAMOx unit in slot 4 remains the active unit.
End of instruction
ESW upgrade procedure 2

An alternative procedure requires two shorter interruptions of up to 50 ms instead of one long
interruption. Please refer to the note above.
→ ESW download. Proceed as follows:

1. Configure the new ESW file for the working SAMOx unit:
3. Execute the “Download” command.
Result: The new ESW is downloaded to the working and protecting SAMOx units.
→ ESW upgrade on the protecting unit. Proceed as follows:

- In the “Software to install” column select the new software.

2. Execute the “Start …” command.

- In the “Parameters for command Start” select the algorithm “Upgrade Units Only”.
- Click “OK”.
- The protecting SAMOx unit starts with the configured ESW.
- This takes up to 4 minutes.
Result: The protecting SAMOx unit is now running with the correct ESW.
→ Manual switch to protecting unit. Proceed as follows:

1. Navigate to the EQP status dialog on the working unit:
- AP: /unit-4, Status - EQP
2. Perform a manual switch-over from the working to the protecting SAMOx unit:
- Execute the “Manual Switch-Over” command.
- Traffic will be switched to the protecting unit.
- Traffic will be interrupted for up to 50 ms.
Result: The protecting SAMOx unit is active.

The upgrade procedure 2 with sequential ESW upgrade must follow two different
approaches for the ESW upgrade process on the working unit, depending if the
databases of the running ESW and the new ESW are compatible or not.
→ If the new ESW is a hotfix or a customer specific ESW, e.g. ESW
samo2_r15a03 -> samo2_r15a03_03, the databases are compatible.
If the databases are compatible please proceed with → "ESW upgrade on the
working unit (compatible databases)".
→ In any other case, i.e. if the release number or the release alphabetic character
changes, please contact the Hitachi Energy technical support for information
about compatibility between ESW releases.
If the databases are compatible please proceed with → "ESW upgrade on the
working unit (compatible databases)".
If the databases are not compatible please proceed with → "ESW upgrade on
the working unit (non compatible databases)".
→ ESW upgrade on the working unit (compatible databases). Proceed as follows:

1. Configure the new ESW file for the working SAMOx:
- In the “Software to install” column select the new software.
2. Execute the “Start …” command.
- In the “Parameters for command Start” select the algorithm “Upgrade Units Only”.
- Click “OK”.
- The working SAMOx unit starts with the configured ESW.
Result: The working SAMOx unit is now running with the correct ESW. Proceed with →
"Manual switch to working unit".
→ ESW upgrade on the working unit (non compatible databases). Proceed as follows:
1. Navigate to the equipment handling dialog on the working SAMOx:
- AP: /unit-4, Main - Equipment
2. Start the unit in the bootloader application:
- Execute the “Stop In Boot” command.
3. Wait until the working unit has rebooted.
- This takes about 2 minutes.

4. Navigate to the software dialog on the working SAMOx:

- AP: /unit-4, Main - Software
5. Delete all softwares from the “Software On Unit” table except the new ESW.
6. Start the new ESW:
- In the “Configuration, Software” parameter select the new ESW.
- Execute the “Start Software” command.
7. Wait until the working unit has rebooted.
- If the databases of the previously running ESW and of the new ESW are not compatible
there will be a software mismatch (SWM) alarm.
8. Start the new ESW again:
- In the “Configuration, Software” parameter select the new ESW.
- Execute the “Start Software” command.
- The SWM alarm is cleared.
Result: The working SAMOx unit is now running with the correct ESW.
→ Manual switch to working unit. Proceed as follows:

1. Navigate to the EQP status dialog on the working unit:
- AP: /unit-4, Status - EQP
2. Perform a manual switch-over from the protecting to the working SAMOx unit:
- Execute the “Manual Switch-Over” command.
- Traffic will be switched to the working unit.
- Traffic will be interrupted for up to 50ms.
Result: The ESW upgrade is complete and the working SAMOx unit is active.
End of instruction

FOX61x | SAMO2, SAMO3, SAMO5 USER INTERFACE REFERENCE
8 User Interface Reference

This section gives a complete reference of the managed objects, properties, and commands of
the SAMOx service unit as far as these are not covered in the generic descriptions in
[1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
For a description on how to configure and bring into operation the SAMOx unit and its main
functions, please refer to section 6 Commissioning (on page 100).
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 SAMOx functional unit.
Figure 78 shows the access point (AP) tree for an active SAMOx unit with its managed objects.
Figure 79 shows the access point (AP) tree for a standby SAMOx unit with its managed objects.

<a p>
FOX-
0...20 <a p>

unit-x: SAMOx
4 <a p>
port-x: STM
4 <a p>
port-x: Ethernet
1 <a p>
mau
48 <a p> SAMO

port-x: E12 3 only
1 <a p>
vc12-1
1 <a p>
sdh
4 or 8 <a p>
sdh-x
0 ... 1 <a p> 0 ... 1 <a p> 1 … 16 <a p>

dccm dccr j-x
1 <a p>
vc4
0...31 <a p>

vc4-x
0...63 <a p> 0...3 <a p>

klm-xyz klm-x00
1 <a p>
pdh
64 <a p>
vc12-x
1 <a p>
p12
1 <a p>
eos 0...31 <a p>
chan-x
32 <a p> SAMO5 provides in maximum

eos-x 8 EoS groups
1 <a p>
eos
1 <a p>
iports
1 ... 63 <a p> 1 ... 24 <a p> 1 ... 12 <a p>
vc12-x vc3-y vc4-z
4 <a p>
iport-x: Ethernet
Figure 78: MOM (managed object model) of the SAMOx unit

<a p>
FOX-
0...20 <a p>

unit-x: SAMOx
4 <a p>
port-x: STM
4 <a p>
port-x: Etherne t
1 <a p>
mau
1 <a p>
ipor ts
4 <a p>
ipor t-x: Etherne t
Figure 79: MOM (managed object model) of the standby SAMOx unit
With these managed objects (MOs) the following functions are covered:
Table 55: Managed objects (MOs) for SAMOx

MO Description of the management functions
unit-x: SAMOx Rxx Restart of the unit, management of the unit ESW, label-
(samo2_r15a) ing, indication of the equipment status, display of
inventory data, presentation of logbooks.
General parameters for VC SNC protection and
degraded signal evaluation.
SETS and ESO-2 clock selection and priority configura-
tion. SETS and ESO-2 status display.
EQP group creation and deletion. EQP status display.
eos The eos MO contains per default 32 EoS ports.
eos-x Configure the EoS ports in the switched, unswitched or
expansion transport mode. Create and delete an EoS
group.
eos Configure the EoS group.
Add and delete EoS group members. Fault manage-
ment, performance management and status indication
of the EoS group.
vc12-x EoS group members.
vc3-y Fault and performance management.
vc4-z Status indication of the VC and the CTP.
pdh The pdh MO contains the VC-12/P12 resources access-
ing the PBUS.
vc12-x TTI and CTP configuration of the VC-12. Bidirectional
protection switching.
Fault and performance management.
Status indication of the VC and the CTP.
p12 P12 mode and channel configuration.
Maintenance functions for the P12 signal.
chan-x Display of the configured channel parameters.
port-x, x = 1 … 4 Configuration of the SDH ports physical section.
Fault management and status indication.

Table 55: Managed objects (MOs) for SAMOx (continued)

MO Description of the management functions
port-x, x = 5 … 8 Configuration of the Ethernet front ports speed and
duplex, flow control.
Fault management and statistics.
Port status display.
mau The mau is the access point for the physical media
attachment unit. It provides no fault management func-
tions.
sdh The sdh MO contains the 4 logical SDH ports of an
unprotected SAMOx unit or the 8 logical SDH ports of an
equipment protected SAMOx unit.
sdh-x Configuration of the SDH regenerator section, multi-
plex section and DCC usage.
MSP configuration and status indication.
dccm CTP configuration and status of the SDH MS DCC sig-
nals.
dccr CTP configuration and status of the SDH RS DCC sig-
nals.
j-x CTP configuration and status of the SDH ports VC-4
signals.
vc4 Create and delete a VC-4 with a TUG-3 structure.
vc4-x TUG-3 structure, TTI and CTP configuration of the VC-4.
klm-xyz VC-12 CTP configuration and status indication.
klm-x00 VC-3 CTP configuration and status indication.
port-x, x = 101 … 148 Configuration of the E12 front ports (SAMO3 only).
Fault management and statistics.
Port status display.
vc12 TTI and CTP configuration of the VC-12. Bidirectional
protection switching.
iports The iports MO contains the internal Ethernet port.
iport-x, x = 1 … 4 Management of the Ethernet internal port. The internal
Ethernet port connects the SAMOx unit via the 10 GbE and
the 1 GbE star with the core unit.
For each of the managed objects, properties and commands, the GUI “Tree Views” are given.
This reference section comprises the management functions:
• Overview,
• Main,
• Statistics,
• Configuration,
• Fault Management,
• Performance Management, and
• 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 are examples and show configurations or
data that may not correspond to the view you see when managing your FOX61x
equipment.
8.2 AP: / unit-x: SAMOx
8.2.1 AP: / unit-x, Overview

For a description of the
− “Overview - Alarms”,
− “Overview - Cross Connections”,
− “Overview - STM Allocation”,
− “Overview - VC4 TUG Allocation”,
− “Overview - Timeslot Allocation”,
− “Overview - Unused Channels”,
− “Overview - Statistics”,
− “Overview - Ethernet Speed”, and
− “Overview - DDM”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.
8.2.1.1 AP: / unit-x, Overview - Redundancy Support
Please note:
The Redundancy Support tab is only available in the FOXCST
• with an FOXCST release R14B or newer, and
• if two SAMOx units are plugged in the subrack, configured as equipment protec-
tion pair.
When operating two SAMOx units as equipment protected pair, some parameters on both
SAMOx units must be configured with the same parameter values. In this way the SAMOx units
behaves the same, independent which unit is the active unit.
Parameters to be aligned are the EPL and EoS configuration parameters related to the FOX61x
Switch access, as listed below:
• Unit:
− EPL, e.g. unswitched or switched mode
• Ethernet port-5 to port-8 and eos-1 to eos-12:
− Port Type, e.g. CVP
• Ethernet port-5 to port-8, Port Configuration:
− Admin State
• Ethernet port-5 to port-8 and eos-1 to eos-12, Bridge Configuration:
− Bridge Port Configuration, e.g. Mode, PVID
− Storm Control, e.g. Broadcast
− RSTP, e.g. STP Enabled, Priority, Automatic Cost, Manual Cost

− RSTP Auto Port, e.g. STP Auto Edge Port

− R-L2GP, e.g. Restricted TCN, Restricted Role
• Ethernet port-5 to port-8, QoS Configuration:
− Port QoS, e.g. any port related QoS parameter
− Port & VLAN QoS, e.g. any port VLAN related QoS parameter
Please note:
The SDH front ports on the working and protecting SAMOx units operate inde-
pendently. No alignment is required.
The FOXCST provides a redundancy support feature on the SAMOx unit which applies the
Ethernet port and EoS configuration of the working unit to the corresponding Ethernet port and
EoS configuration of the protecting unit.
Please note:
The alignment of parameter values only works in direction from the working
SAMOx unit to the protecting SAMOx unit.
→ Never modify an Ethernet port or EoS configuration parameter on the protecting
unit. With the next “align” command the parameter values are overwritten with
the values from the working unit.

Table 56: AP: / unit-x, Overview - Redundancy Support

Operation Name Parameter Name Range Descriptions / Details
Execute the “Align all” command.
Start the alignment process of Ethernet port and
EoS configuration parameters: The FOX61x Switch
related Ethernet port and EoS configuration parameters
of the working SAMOx unit are copied to the configura-
tion parameters of the protecting SAMOx unit.
Depending of the number and type of parameter
discrepancies the command must be activated sev-
eral times. Repeat the “Align all” command until all
parameter values are aligned.
The same command is available as context com-
mand in the table area. Clicking the right mouse but-
ton shows the “Align all” command:
To apply an alignment to a single item, e.g. a single

parameter, select the corresponding table row and
execute the “Align” command.
The alignment will be applied to the item in the
selected table row and all items in subordinate table
rows.
This command is only available as context command
in the table area. Clicking the right mouse button
shows the “Align” command:
Expand all table rows.

Alternatively you can click the icon in a table row
to expand a single row.
Collapse all table rows.
Alternatively you can click the icon in a table row
to collapse a single row.
Table with align- Function Unit Collection of unit related configuration parameters.
ment items
port-5 … port-8 Collection of Ethernet port related configuration
parameters.
eos-1 … eos-12 Collection of EoS related configuration parameters.
- EPL EPL configuration for the Ethernet front ports.
Accessible in the FOXCST Tree view at the AP: /unit-x,
Configuration - EPL.
- Port Type Port type parameter.
Accessible in the FOXCST Tree view at the AP: /unit-x,
Main - Port Type.
- Port Configura- Collection of port configuration parameters.
tion
- Administrative Administrative status configuration for the Ethernet
Status front ports.
Accessible in the FOXCST Tree view at the AP: /unit-x/
port-y, Main - General.
- Bridge Configu- Collection of bridge port configuration parameters.
ration
- Bridge Port Con- Bridge port configuration parameters:
figuration Mode, PVID, Acceptable Frametypes, Ingress Filter-
ing, VLAN Membership.
Accessible in the FOXCST Switching view at the AP: /
Switching/Bridges/bridge-1/Ports.

Table 56: AP: / unit-x, Overview - Redundancy Support (continued)

- Storm Control Bridge port storm control configuration parameters.
Switching/Bridges/bridge-1/Ports/Storm Control.
- RSTP Bridge port protocol configuration parameters:
STP Enabled, Priority, Automatic Cost, Manual Cost.
Switching/Protocols/Spanning Tree/bridge-1/Ports.
- RSTP Auto Port Bridge port protocol configuration parameter:
Auto Edgeport.
- R-L2GP Bridge port protocol configuration parameters:
R-L2GP Enabled, Restricted TCN, Restricted Role,
Pseudo Root Bridge MAC Address and Priority.
- QoS Configura- Collection of port QoS configuration parameters.
tion
- Port QoS Port QoS configuration parameters:
Rate Limiting Enabled and CIR, CBS, EIR, EBS;
Traffic Classification CoS Type and Priority.
Accessible in the FOXCST “QoS” view at the AP: /QoS/
Policing/UNI, Rate Limiting and at the AP: /QoS/Traffic
Classification/UNI, Traffic Classification.
- Port & VLAN QoS Collection of port and VLAN QoS configuration
parameters.
- VLAN: xxx VLAN based QoS configuration parameters:
Rate Limiting Enabled and CIR, CBS, EIR, EBS.
Traffic Classification CoS Overwrite and Overwrite
Priority.
Accessible in the FOXCST “QoS” view at the AP: /QoS/
Policing/UNI, Rate Limiting and at the AP: /QoS/Traffic
Classification/UNI, Traffic Classification.
The configuration is aligned, i.e. the Ethernet port
and EoS configuration parameters of the item in this
Configuration Aligned table row and of any item in subordinate table rows
are identical on the Ethernet port or EoS configura-
tion of the working and protecting SAMOx unit.
The configuration is not aligned, i.e. the Ethernet
port and EoS configuration parameters of the item
Configuration Not Aligned in this table row or of any item in subordinate table
rows are different on the Ethernet port or EoS con-
figuration of the working and protecting SAMOx unit.
The EPL mode is not used on the unit, or the Ether-
net or EoS port is not used in the FOX61x Switch, i.e.
Configuration the port type usage is neither “CVP” nor “PWAC”.
Details Required for EPL The Ethernet port is used in the EPL (unswitched)
mode.
A change of the The message is displayed if the port type configura-
Port Type might tion differs between the working and the protecting
require a further unit, e.g. “CVP” on the working unit and “None” on
alignment the protecting unit.
A single “align” command is often not sufficient to
align all parameter values. Repeat the “align” com-
mand until all parameter values are aligned.

Table 56: AP: / unit-x, Overview - Redundancy Support (continued)

The port types of The message is displayed if the EPL configuration
the physical ports differs between the working and the protecting unit,
and the EoS ports e.g. “eos-x” on the working unit and “no EPL” on the
have to be aligned protecting unit.
first A single “align” command is often not sufficient to
align all parameter values. Repeat the “align” com-
mand until all parameter values are aligned.
8.2.2 AP: / unit-x, Main

− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”,
− “Main - Software”,
− “Main - Port Type, and
− “Main - Mirroring”
FOX612/FOX611”.
8.2.3 AP: / unit-x, Configuration
8.2.3.1 AP: / unit-x, Configuration - General - SNCP Times

Table 57: AP: / unit-x, Configuration - General - SNCP Times

Operation Name Parameter Name Range Description / Details
SNCP VC4 Guard Time 0 … 60 s The holdoff and guard times are configured
Holdoff Time 0 … 20 s per VC type for the whole unit.
The guard time is the time interval after an
Wait-To-Restore 0 … 600 … 1800 s automatic protection switchover when no
Time additional switchover is allowed.
SNCP VC3 Guard Time 0 … 60 s The holdoff time is the time interval to define
how long the switching criteria have to be
Holdoff Time 0 … 20 s
active before the protection switchover is
Wait-To-Restore 0 … 600 … 1800 s activated.
Time For further information please refer to section 6.2
SNCP VC12 Guard Time 0 … 60 s SNCP Configuration (on page 116).
The revertive operation type of the SNC pro-
Holdoff Time 0 … 20 s
tected VC signal provides the configuration
Wait-To-Restore 0 … 600 … 1800 s of the wait to restore (WTR) timer.
Time The WTR timer is configured per VC type for
the whole unit.
Note that for the AP: /unit-x/pdh/vc12-y and
the AP: /unit-x/port-y/vc12 the WTR timer is
configurable individually.
A path selector which selects the protecting
path switches back to the working path as
soon as the configured WTR timer elapses.
The WTR timer is reset when the working
path is in a failure state and starts when the
working path becomes fault free.
8.2.3.2 AP: / unit-x, Configuration - General - Signal Quality
Table 58: AP: / unit-x, Configuration - General - Signal Quality

Excessive Defect Excessive Defect 10E-3 … 10E-5 The bit error ratio for the excessive signal
Threshold VC-4 defect are configured per VC type for the
Excessive Defect Excessive Defect 10E-3 … 10E-5 whole unit.
Threshold VC-3 Please refer to section 7.3 Detection of Signal
Defects (on page 136) for a description of the
Excessive Defect Excessive Defect 10E-3 … 10E-5 excessive signal defect evaluation.
Threshold VC-12 Please note that the error distribution for the
excessive signal is assumed to be poisson.

Table 58: AP: / unit-x, Configuration - General - Signal Quality (continued)

Degraded Defect Degraded Defect 10E-5 … 10E-6 … 10E-8 The bit error ratio for the degraded signal
Threshold VC-4 defect are configured per VC type for the
Degraded Defect Degraded Defect 10E-5 … 10E-6 … 10E-8 whole unit.
Threshold VC-3 Please refer to section 7.3 Detection of Signal
Degraded Defect Degraded Defect 10E-5 … 10E-6 … 10E-8 degraded signal defect evaluation.
Threshold VC-12 Please note that the error distribution for the
degraded signal is assumed to be poisson.
8.2.3.3 AP: / unit-x, Configuration - General - Impedance
Table 59: AP: / unit-x, Configuration - General - Impedance

Impedances E1 Port Impedance 75 Ohms Select the impedance of the 48 E12 front
120 Ohms ports.
Only applicable for the SAMO3 unit.
8.2.3.4 AP: / unit-x, Configuration - EPL
Please note:
An Ethernet or EoS port used in an Ethernet Private Line (EPL) must be configured
to the “CVP” port type.
→ Otherwise the port does not appear in the FOXCST “Switching” tab.
Please note:
The EoS ports of a standby SAMOx unit can only be configured to the “CVP” port
type on the NE level.
→ Navigate to the AP: /ne, Main - Port Type.
Please note:
An Ethernet or EoS port used in an Ethernet Private Line (EPL) must be configured
to the port mode “unswitched” in the FOXCST “Switching” tab before assigning it
to an EPL EoS port.
Please note:
Refer to section 5.4.3 Ethernet Switch (on page 63) for further information.

Table 60: AP: / unit-x, Configuration - EPL

Ethernet Port EPL port-5 no EPL The Ethernet port participates in the VLAN
Handling bridge.
eos-1 The Ethernet port and the EoS port eos-1
eos-9 (100 Mbit/s) or eos-9 (1 Gbit/s) are intercon-
nected with a point-to-point connection,
bypassing the VLAN bridge.
Configure the port-5, eos-1 or eos-9 (and eos-
11) ports to the “unswitched” port mode in
the FOXCST “Switching” tab before configuring
the EPL mode.
port-6 no EPL The Ethernet port participates in the VLAN
bridge.
eos-10 (100 Mbit/s) or eos-10 (1 Gbit/s) are intercon-
nected with a point-to-point connection,
bypassing the VLAN bridge.
Configure the port-6, eos-2 or eos-10 (and
eos-12) ports to the “unswitched” port mode
in the FOXCST “Switching” tab before configur-
ing the EPL mode.
bridge.
(100 Mbit/s) are interconnected with a point-
to-point connection, bypassing the VLAN
bridge.
Configure the port-7 and eos-3 ports to the
“unswitched” port mode in the FOXCST “Switch-
ing” tab before configuring the EPL mode.
bridge.
(100 Mbit/s) are interconnected with a point-
to-point connection, bypassing the VLAN
bridge.
Configure the port-8 and eos-4 ports to the
“unswitched” port mode in the FOXCST “Switch-
ing” tab before configuring the EPL mode.

The EoS ports eos-9 and eos-11, and if applicable the EoS ports eos-13 to eos-17
and/or eos-23 to eos-27, share one unit internal physical 1 Gb Ethernet link.
→ When using the EoS port eos-9 in an Ethernet Private Line, the EoS ports eos-
11, eos-13 to eos-17 and eos-23 to eos-27 are no longer available.
Please note:
When using the EoS port eos-9 in an Ethernet Private Line, also the EoS port eos-
11 must be configured to the port mode “unswitched” in the FOXCST “Switching”
tab before assigning the EoS port eos-9 to an EPL Ethernet port.

The EoS ports eos-10 and eos-12, and if applicable the EoS ports eos-18 to eos-
22 and/or eos-28 to eos-32, share one unit internal physical 1 Gb Ethernet link.
→ When using the EoS port eos-10 in an Ethernet Private Line, the EoS ports eos-
12, eos-18 to eos-22 and eos-28 to eos-32 are no longer available.

Please note:
When using the EoS port eos-10 in an Ethernet Private Line, also the EoS port
eos-12 must be configured to the port mode “unswitched” in the FOXCST “Switch-
ing” tab before assigning the EoS port eos-10 to an EPL Ethernet port.
8.2.3.5 AP: / unit-x, Configuration - SETS
Table 61: AP: / unit-x, Configuration - SETS

PDH Clock Sources PDH Clock Source 1 <MO address> The managed object address of the four PDH
PDH Clock Source 2 <MO address> clock sources.
These parameters are read-only.
PDH Clock Source 3 <MO address>

Table 61: AP: / unit-x, Configuration - SETS (continued)

SETS Clock Selec- Source sdh-1 Available timing sources for the SETS syn-
tion sdh-2 chronization.
Note that the sdh-5 to sdh-8 sources can only
sdh-3 be used if a protecting SAMOx unit is available.
sdh-4 These values are read-only.
For more information regarding quality level
sdh-5
handling please refer to [1KHW029105] User
sdh-6 Manual “Synchronization”.
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Internal
Priority 1 … 14 The priority of a timing source is used as a
selection criterion if the selection algorithm is
configured to “priority based” (see below).
1 is the highest priority, 14 is the lowest prior-
ity.
It is possible to assign the same priority to
more than one source.
Disabled A disabled timing source is not used for the
SETS synchronization.
The internal timing source cannot be dis-
abled.
QL 1 … 14 The quality level QL of a timing source is used
as a selection criterion if the selection algo-
rithm is configured to “QL based” (see
below).
1 is the highest QL, 14 is the lowest QL.
Assign a QL for timing sources that provide
no QL or if you want to fix the QL for a timing
source.
Note that the use of some of the QL values is
standardized.
The default QL of the PDH Clock Sources is
“14”.
The internal timing source has a default qual-
ity level of 11.
Manual “Synchronization”.
Received Use the QL as received with the timing
source. The QL is transported within the SSM
(synchronization status message).
The default QL of the sdh-x clock sources is
“Received”.
Timing sources not providing the SSM only
have an assigned quality level.

Table 61: AP: / unit-x, Configuration - SETS (continued)

Holdoff Time 0 … 60 s During the holdoff time the timing source
step 0.1 s selection process performs no switchover to
a lower priority or lower quality level timing
source.
The holdoff timer starts when the timing
source enters a failure state.
Wait-To-Restore Time 0 … 30 … 720 s During the wait to restore (WTR) time the
step 1 s timing source selection process performs no
switchover from a lower priority or lower
quality level timing source.
The WTR timer is reset when the timing
source is in a failure state and starts when the
timing source becomes fault free.
Selection Algo- Selection Algorithm Priority Select the timing sources according to the
rithm assigned priorities.
This selection algorithm disregards the qual-
ity levels (QL).
QL Select the timing sources according to the
received or assigned quality levels (QL).
The selection algorithm first considers the QL
and then the priority.
Please note:
If the SETS is locked to any of the PDH Clock Sources it will forward the QL 15 (do
not use) inside the FOX61x network element.
8.2.3.6 AP: / unit-x, Configuration - ESO-2

Table 62: AP: / unit-x, Configuration - ESO-2

PDH Clock Sources PDH Clock Source 1 <MO address> The managed object address of the four PDH
PDH Clock Source 2 <MO address> clock sources.
These parameters are read-only.
ESO-2 SETS- ESO-2 SETS-Locked The external synchronization output on the
Locked core unit is synchronized to the SETS func-
tion.
For more information regarding ESO-2 please
refer to [1KHW029105] User Manual “Synchroni-
zation”.
The external synchronization output on the
core unit is synchronized to the selected ESO-
2 clock source.
ESO-2 Clock Selec- Source sdh-1 Note that the ESO-2 Clock Selection parame-
tion sdh-2 ters are only available for the non SETS
locked mode, i.e. “ESO-2 SETS locked” = false.
sdh-3 Refer to the parameter above.
sdh-4 Available timing sources for the ESO-2 syn-
chronization.
sdh-5
sdh-7 The source parameter values are read-only.
sdh-8

Table 62: AP: / unit-x, Configuration - ESO-2 (continued)

Priority 1 … 14 The priority of a timing source is used as a
selection criterion if the selection algorithm is
configured to “priority based” (see below).
1 is the highest priority, 14 is the lowest prior-
ity.
It is possible to assign the same priority to
more than one source.
Disabled A disabled timing source is not used for the
SETS synchronization.
QL 1 … 14 The quality level QL of a timing source is used
as a selection criterion if the selection algo-
rithm is configured to “QL based” (see
below).
1 is the highest QL, 14 is the lowest QL.
Assign a QL for timing sources that provide
no QL or if you want to fix the QL for a timing
source.
Note that the use of some of the QL values is
standardized.
Received Use the QL as received with the timing
source. The QL is transported within the SSM
(synchronization status message).
Timing sources not providing the SSM only
have an assigned quality level
Holdoff Time 0 … 60 s During the holdoff time the timing source
step 0.1 s selection process performs no switchover to
a lower priority or lower quality level timing
source.
The holdoff timer starts when the timing
source enters a failure state.
Wait-To-Restore Time 0 … 30 … 720 s During the wait to restore (WTR) time the
timing source selection process performs no
switchover from a lower priority or lower
The WTR timer is reset when the timing
source is in a failure state and starts when the
timing source becomes fault free.
Selection Algo- Selection Algorithm Priority Select the timing sources in the non SETS
rithm locked mode according to the assigned prior-
ities.
This selection algorithm disregards the qual-
ity levels (QL).
QL Select the timing sources in the non SETS
locked mode according to the received or
assigned quality levels (QL).
The selection algorithm first considers the QL
and then the priority.

Table 62: AP: / unit-x, Configuration - ESO-2 (continued)

ESO-2 Squelched Source sdh-1 Note that the ESO-2 Squelched By Source
By Source sdh-2 parameters are only available for the SETS
locked mode, i.e. “ESO-2 SETS locked” = true.
sdh-3 Refer to the parameter above.
sdh-4 Available timing sources for the ESO-2 syn-
chronization.
sdh-5
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Internal
Squelched The ESO-2 output on the core unit is
squelched, i.e. disabled, if the corresponding
source is selected.
The ESO-2 output on the core unit is active,
i.e. enabled, if the corresponding source is
selected.
ESO-2 Squelched QL 1 … 15 Note that the ESO-2 Squelched By QL param-
By QL eters are available for the SETS locked and
the non SETS locked modes, i.e. “ESO-2 SETS
locked” = true or false.
Quality levels of the timing sources for the
ESO-2 synchronization.
These values are read-only.
Squelched The ESO-2 output on the core unit is
squelched for the selected QL.
The ESO-2 output on the core unit is active
for the selected QL.
8.2.3.7 AP: / unit-x, Configuration - EQP
“Create EQP Group” dialog “Delete EQP Group” dialog

Please note:
→ Please refer to Table 32: "FOX61x slot pairs for SAMOx EQP" (on page 89).
Table 63: AP: / unit-x, Configuration - EQP

Create EQP Group Open the dialog for the creation of an equip-
… ment protection (EQP) group.
EQP Group Cre- Group Type 1:1 Type of the EQP group.
ation Working Unit <MO address> MO address of the working unit, e.g. /unit-18.
In the FOXCST the working unit MO address is
read-only.
Protecting Unit <MO address> List of the MO addresses of all HW and SW
- compatible units which are not assigned, e.g.
/unit-20.
Default is no unit selected.
Delete EQP Group Delete an existing protection group.
Traffic on the protecting unit will be inter-
rupted and services will be re-established on
the working unit.
The protecting unit will become unassigned.
Please note:
The creation and deletion of an EQP group must be done on the working unit.
8.2.3.8 AP: / unit-x, Configuration - CPS

The transmit queue buffer sizes of all SAMOx switch ports can be configured. The configuration
is done with a CPS file.
Without the configuration of a customer specific CPS the default transmit queue buffer sizes as
specified in Table 66: "Transmit Queue default values" (on page 164) and Table 67: "Port Map-
ping default values" (on page 165) are applied.
A customer specific CPS can be ordered at the Hitachi Energy technical support:
Please contact your local Hitachi Energy representative for support contact information.
Table 64: AP: / unit-x, Configuration - CPS

Unit CPS Transmit Queue default Apply the default transmit queue values.
Buffer Refer to Table 66 and Table 67.
<File list> File list of the CPS versions available.
Preview Open the preview window of the selected CPS. This
allows you to check all CPS parameters.
“Preview” GUI dialog of a Transmit Queue Buffer CPS:


Table 65: AP: / unit-x, Configuration - CPS - Preview

Transmit Queue Global Resource Global sharing of resources for the queuing of pack-
General Share Enable ets.
The global shared buffer pool is configured with the
parameters “Global Pool Buffer Limit” and “Global
Pool Descriptor Limit”.
Global Resource 0 Port buffer and descriptor limits in the egress pro-
Share Policy files are ignored for the global shared pool alloca-
tion, i.e. one single port could occupy the whole
shared pool resources.
1 Port buffer and descriptor limits in the egress pro-
files are taken into account.
Global Pool Buffer 0 … 1024 … 6144 Buffer limit in the global shared buffer pool.
Limit The value has to be multiplied with a factor 256 to
get the effective buffer size in bytes.
The usage of the global shared buffer pool is con-
trolled by the parameter “Global Resource Share
Enable”.
Global Pool 0 … 1024 … 5902 Descriptor limit in the global shared buffer pool.
Descriptor Limit The number of descriptors limits the number of
frames that can be stored in the buffers.
The usage of the global shared descriptor pool is
controlled by the parameter “Global Resource Share
Enable”.
Global Buffer Limit 0 … 6144 Limits the total number of buffers in all egress
queues.
Note: If the buffer threshold is N and each descrip-
tor equals M buffers, then packets are dropped
when the buffer counter is N+M.
Note: It is recommended to use the max available
buffers, i.e. 6144.
Global Descriptor 5902 Limits the total number of descriptor in all egress
Limit queues.
Note: This value cannot be changed.
Global Multicast 0 … 16 … 31 Maximum number of descriptors that may be allo-
Descriptor Limit cated for a multicast packet.
Global Ingress Mir- 0 … 10 … 5902 Number of descriptors allocated for packets for-
roring Descriptor warded to the ingress analyzer port due to mirror-
Limit ing.
Global Egress Mir- 0 … 10 … 5902 Number of descriptors allocated for packets for-
roring Descriptor warded to the egress analyzer port due to mirroring.
Limit
Global Tail Drop When Tail Drop is disabled, packets are not dropped
Disable by the Tail Drop algorithm.
This configuration does not affect the “Global
Descriptor Limit”, i.e. Tail Drop drops packets that
exceed the “Global Descriptor Limit” regardless of
the state of this configuration.
Global Random Weighted Random Tail Drop (WRTD) provides
Tail Drop Enable Weighted Random Early Detection (WRED) like
behavior, i.e.:
- Random discard of packets before queue size
reaches the tail drop limit.
- The discard probability increases linearly with the
queue size.

Table 65: AP: / unit-x, Configuration - CPS - Preview (continued)

Global DP1 Allow DP1 packets to use the global shared buffer
Resource Share pool.
Enable
Transmit Queue Profile ID 0…7 Identifier of the transmit queue profile.
Profile Table Note: Profile 7 is used for switch internal purposes
and cannot be used for user ports.
Profile Name 0 … 40 characters Name of the transmit queue profile.
Port Buffer Limit 0 … 6144 The egress profiles defines the guaranteed resource
Port Descriptor 0 … 5902 configuration for a port and for each of the 16
Limit {queue, drop-precedence} pairs on the port. Follow-
ing configurable resource limits are kept per profile:
Q0Dp0BufLimit 0 … 6144 - Port Buffer Limit [bytes x 256]
Q0Dp1BufLimit 0 … 6144 - Port Descriptor Limit [frames]
- {queue, drop-precedence} Buffer Limit [bytes x
Q0Dp0DescLimit 0 … 5902
256]
Q0Dp1DescLimit 0 … 5902 - {queue, drop-precedence} Descriptor Limit
Q0ResShareEn [frames]
- {queue} Resource Sharing Enable
The buffer size values have to be multiplied with a
factor 256 to get the effective buffer size in bytes.
The number of descriptors limits the number of
frames that can be stored in a buffer.
Q1 … Q7 parame- Refer to the Q0 parameters
ters
Port Profile Map- Entry Validity Validity of the physical switch port entries.
ping Table
Port ID P_5 … P_8 Ethernet front ports.

I_BEC Internal port to the local processor.
E_11_13 Backplane 1 Gbit/s Ethernet port.
X_11, X_13 Backplane 10 Gbit/s Ethernet port.
I_EOS_1 … EoS Ethernet port, when no expansion EoS ports are
I_EOS_12 used.
I_EOS_LB_9 … EoS Ethernet port, when expansion EoS ports are
I_EOS_LB_12 used.
I_FLEX_1,I_FLEX_2
Port Usage Front Front ports.
Internal Unit internal port.
Backplane Backplane 1 Gbit/s or 10 Gbit/s Ethernet port.
Port Bandwidth 10M/100M/1000M Maximum Bandwidth of the switch port.
100M
1G
10G
Profile ID 0…7 Identifier of the transmit queue profile.
TQ0 Enable Enable/disable queuing of packets to Traffic Class 0
queue.
TQ1 Enable … Refer to “TQ0 Enable”.

TQ7 Enable

Please note:
All buffer size values given in the Table 66 have to be multiplied with a factor 256
to get the effective buffer sizes. E.g a Q0Dp0BufLimit of 6 gives a buffer size of 6 x
256 = 1536 bytes.
Table 66: Transmit Queue default values

Profile ID 0 1 2 3 4 5 6 7
Parameter
Port Buffer Limit 512 512 512 0 0 0 512 0
Port Descriptor Limit 128 128 128 0 0 0 128 0
Q0Dp0BufLimit 14 36 36 0 0 0 0 16
Q0Dp1BufLimit 0 0 0 0 0 0 0 0
Q0Dp0DescLimit 19 36 36 0 0 0 0 16
Q0Dp1DescLimit 0 0 0 0 0 0 0 0
Q0ResShareEn
Q1Dp0BufLimit 14 36 36 0 0 0 0 0
Q1Dp1BufLimit 0 0 0 0 0 0 0 0
Q1Dp0DescLimit 19 36 36 0 0 0 0 0
Q1ResShareEn
Q2Dp0BufLimit 14 36 36 0 0 0 0 0
Q2Dp1BufLimit 0 0 0 0 0 0 0 0
Q2Dp0DescLimit 19 36 36 0 0 0 0 0
Q2ResShareEn
Q3Dp0BufLimit 14 36 36 0 0 0 0 32
Q3Dp1BufLimit 0 0 0 0 0 0 0 0
Q3Dp0DescLimit 19 36 36 0 0 0 0 32
Q3ResShareEn
Q4Dp0BufLimit 14 36 36 0 0 0 0 0
Q4Dp1BufLimit 0 0 0 0 0 0 0 0
Q4Dp0DescLimit 19 36 36 0 0 0 0 0
Q4ResShareEn
Q5Dp0BufLimit 14 36 36 0 0 0 0 32
Q5Dp1BufLimit 0 0 0 0 0 0 0 0
Q5Dp0DescLimit 19 36 36 0 0 0 0 32
Q5ResShareEn
Q6Dp0BufLimit 14 36 36 0 0 0 0 32
Q6Dp1BufLimit 0 0 0 0 0 0 0 0
Q6Dp0DescLimit 19 36 36 0 0 0 0 32
Q6ResShareEn
Q7Dp0BufLimit 14 36 36 0 0 0 32 32
Q7Dp1BufLimit 0 0 0 0 0 0 0 0

Table 66: Transmit Queue default values (continued)

Profile ID 0 1 2 3 4 5 6 7
Parameter
Q7Dp0DescLimit 19 36 36 0 0 0 32 32
Q7ResShareEn
Table 67: Port Mapping default values

Port ID Port Usage Port Bandwidth Profile ID TQ0 … TQ7 Enable
P_5 … P_8 Front 10M/100M/1G 0
I_BEC Internal 1G 6
E_11_13 Backplane 1G 1
X_11, X_13 Backplane 10G 2
I_EOS_1 … I_EOS_8 Internal 100M 0
I_EOS_9 … I_EOS_12 Internal 1G 0
I_EOS_LB_9 … I_EOS_LB_12 Internal 1G 0
I_FLEX_1, I_FLEX_2 Internal 1G 0
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.
Please note:
Whenever a CSF alarm is raised please contact technical support.
Table 68: AP: / unit-x, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
CCE Configuration or Cus- Processing Major An invalid configuration has been
tomization Error Error Alarm accepted by the unit by mistake.
To get rid of the alarm redo the com-
plete configuration of the unit:
- Unassign the unit.
- Restart the unit.
- Assign the unit.
If the alarm persists please contact Hita-
chi Energy.
CSF Communication Sub- Communica- Major A potential failure is detected which is
system Failure tion Alarm local on the unit. The alarm is cleared
after 24 hours.
ECSL All Selected ESO Clock Communica- Minor All configured timing sources for the
Sources Lost tion Alarm ESO-2 clock output on the core unit
are lost, or the priority or QL is worse
than the internal clock source.
The clock output is squelched.
EQM Equipment Malfunc- Equipment Critical The SAMOx controller detects any
tion Alarm anomalies on the unit, e.g. a voltage is
missing, a chip does not respond, etc.

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

Affecting Severity
EQPHWI EQP Hardware Incom- Equipment Major The actual hardware is not compatible
patible With Configu- Alarm with the hardware of the protecting
ration unit.
This alarm is available on the working
unit of an EQP group only.
EQPNPR EQP Group Not Pro- Equipment Major The working or the protecting unit is
tected Alarm not available, i.e. not plugged in or has
an equipment failure.
EQPSWI EQP Software Incom- Equipment Major The running software (ESW) is not
patible With Configu- Alarm compatible with the software on the
ration protecting unit.
EQPUNA EQP Working Unit Not Equipment Major An automatic protection switch or a
Active Alarm “manual switch” or a “forced switch”
to the protecting unit has been done.
EQPUNV EQP Unit Not Avail- Equipment Major The standby unit is not available, i.e.
able Alarm not plugged in or has an equipment
failure.
and the protecting unit of an EQP
group.
EQPWUI EQP Working Unit Iso- Equipment Major The working unit has been isolated
lated Alarm with the “Isolate Unit” status com-
mand.
No protection is available in this state.
ESOSNP ESO Clock Source Not Communica- Warning The selected timing source for the
Primary tion Alarm ESO-2 clock output on the core unit is
not the one with the highest priority,
on condition that QL-mode is dis-
abled.
GSW General Software Equipment Major An ESW internal error has been
Alarm Alarm detected that might inhibit the ESW
from running correctly.
HWIC Hardware Incompati- Equipment Major The plugged HW is not compatible
ble With Configura- Alarm with the unit configuration HW stored
tion in the database. You may need to
change the HW or re-create the con-
figuration for the unit.
LOSESI Loss Of Signal On Communica- Warning Loss of timing source ESI-2.
External Synchroniza- tion Alarm
tion Input
LOSP1 Loss Of Signal On Communica- Warning Loss of timing source on PDH clock
PDH Clock Source 1 tion Alarm source 1.


Affecting Severity
LOSS1 Loss Of Signal On Communica- Warning Loss of timing source on SDH port-1,
SDH Clock Source 1 tion Alarm STM-16 or STM-4.
LOSS5 Loss Of Signal On Communica- Warning Loss of timing source on SDH port-1
SDH Clock Source 5 tion Alarm of the protecting SAMOx unit,
STM-16 or STM-4.
STM-16 or STM-4.
STM-4 or STM-1.
STM-4 or STM-1.
MFA Maintenance Func- Communica- Warning A maintenance function has been acti-
tion Active tion Alarm vated by the operator.
E.g. the synchronization condition has
been manually changed in the timing
sources status.
NSW No Application Soft- Equipment Major There is no application ESW installed
ware Alarm on the unit, or the application ESW has
not yet finished its boot process.
PRC PBUS Resource Con- Processing Major The PBUS access circuit of another
flict Error Alarm TDM unit in the subrack is defective.
Remove or unassign the other TDM
units in the subrack one by one until
the alarm is cleared. Replace the
defective unit.
SCSL All Selected Clock Communica- Minor Loss of all SDH Equipment Clock (SEC)
Sources Lost tion Alarm clock sources that have been config-
ured as selectable sources, or the pri-
ority or QL of all external clock sources
is worse than the internal clock
source.
SETSHO SETS Holdover Communica- Minor The SETS is in the holdover state, i.e.
tion Alarm all external synchronization sources
are lost or the selected source has a
frequency offset of more than ±15
ppm.
The SETS maintains operation within
specifications.
SETSOOL SETS Out Of Limits Communica- Minor The measured SETS frequency
tion Alarm exceeds the limit of ± 15 ppm.
SETSPLL SETS PLL Out Of Lock Communica- Minor Marks the start-up phase during
tion Alarm which the PLL is probably unlocked.


Affecting Severity
SETSSNP SETS Clock Source Communica- Warning The currently active SETS clock source
Not Primary tion Alarm is not the source with the highest pri-
ority, on condition that QL-mode is
disabled.
SSWNA Scheduled Software Equipment Minor The ESW that is scheduled for installa-
Not Available Alarm tion is not available on the unit. Make
sure that the ESW is downloaded to
the unit.
SWIC Software Incompati- Equipment Major The ESW running on the unit is not
ble With Configura- Alarm compatible with the unit configura-
tion tion stored in the database. You may
need to upgrade, or downgrade the
ESW, or re-create the configuration
with the currently running ESW.
SWIN Software Incompati- Equipment Major The running ESW is not compatible
ble With Network Ele- Alarm with the version required by the NE
ment type or version.
SWM Software Mismatch Equipment Minor The running ESW does not match the
Alarm assigned ESW.
UIC Unit Incompatible Equipment Major The inserted unit is not compatible
Alarm with the assigned unit.
UNAS Unit Not Assigned Equipment Warning The unit is not assigned and cannot be
Alarm configured. To assign the unit, exe-
cute the “Assign” command in the
“Main” function of the unit.
UNAV Unit Not Available Equipment Critical The unit that is configured is either
Alarm not plugged or not recognized due to
a failure.
Please note:
Automatic, manual and forced protection switching is available from the working to
the protecting unit and vice versa.
→ Please refer to section 5.8 Equipment Protection (EQP) (on page 89).
8.2.5 AP: / unit-x, 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 SAMOx unit:
• “Unfiltered Events” group, see section 8.2.5.1 AP: / unit-x, Performance Management - Unfil-
tered Events (on page 169).
The following counter intervals are available:
Table 69: PM counter interval availability

Counter interval Unfiltered
Events
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no

Table 69: PM counter interval availability (continued)

Counter interval Unfiltered
Events
Alarm 24h no
8.2.5.1 AP: / unit-x, Performance Management - Unfiltered Events
Table 70: PM group: Unfiltered Events

PM parameter Description
SETS Source Switch The timing source of the SETS function has
changed.
ESO Source Switch The timing source of the ESO-2 clock has
changed.
8.2.6 AP: / unit-x, Status
8.2.6.1 AP: / unit-x, Status - SETS - General
“Clear WTR” dialog:

Table 71: AP: / unit-x, Status - SETS - General

Source Status Source sdh-1 List of all enabled timing sources.
sdh-2
sdh-3
sdh-4
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Internal
Priority 1 … 14 Configured priority value of the timing
Disabled source.
QL 1 … 15 Adjusted or received quality level of the tim-

ing source, as it is used by the selection algo-
rithm in the SETS selectors A and B.
Status Not Supervised Disposability of the timing source.
Available
Holdoff
Failed
Wait To Restore
Clock Status Selection Algo- Priority Display of the configured selection algorithm
rithm QL for the timing sources:
- Priority Table based
- Quality Level based
Selected Clock <Timing Source> Display of the selected timing source.
Source
Clock Operation Free Running Display of the current operation mode of the
Mode Locked SETS system:
- Locked: Locked to a traffic signal.
Holdover - Free-running: SETS synchronized to the
internal oscillator.
- Holdover: SETS keeps the acquired fre-
quency from a traffic signal which has been
lost.
The acquired frequency is calculated during
1 minute as the average frequency.
The maximum allowed offset for the hold-
over frequency is ±10 ppm.
Clock Operation Clock Operation Auto Selection With the clock operation type it is possible to
Type Type Forced Free Run force the SETS to change its state for mainte-
nance purposes.
Forced Holdover These manual commands override the auto-
matic selection.
Forced states are not configuration data and
thus not stored in the MIB database.
A forced clock operation state activates the
maintenance function active (MFA) alarm.

Table 71: AP: / unit-x, Status - SETS - General (continued)

Clear WTR … Open the FOXCST dialog to select a timing
source.
Clear WTR Source List sdh-1 The WTR timer can be cleared to immediately
sdh-2 switch back from the lower priority or lower
sdh-3
sdh-4
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
8.2.6.2 AP: / unit-x, Status - SETS - Sources

Table 72: AP: / unit-x, Status - SETS - Sources

Lockout Command Source sdh-1 The lockout of a port prevents the selection
sdh-2 as a SETS timing source.
It is not possible to override the lockout of a
sdh-3 source with a forced or manual switch com-
sdh-4 mand.
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Lockout locked out
not locked out
Switch Command Forced Switch None Perform a forced switch to a specific timing
sdh-1 source for the SETS.
The switch command is only accepted if the
sdh-2 source is enabled, i.e. has a priority config-
sdh-3 ured.
If the source is not available, i.e. failed or in
sdh-4
WTR state, “Internal” is selected.
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Manual Switch None Perform a manual switch to a specific timing
sdh-1 source for the SETS.
The switch command is only accepted if no
sdh-2 forced switch is active and the source is avail-
sdh-3 able. The source is not available if
- disabled, or
sdh-4
- failed, or
sdh-5 - in WTR state.
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2

8.2.6.3 AP: / unit-x, Status - ESO-2 - General
“Clear WTR” dialog:
Table 73: AP: / unit-x, Status - ESO-2 - General

Source Status Source sdh-1 List of all enabled timing sources.
sdh-2
sdh-3
sdh-4
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Internal
Priority 1 … 14 Configured priority value of the timing
Disabled source.
QL 1 … 15 Adjusted or received quality level of the tim-

ing source, as it is used by the selection algo-
rithm in the SETS selectors A and B.
Status Not Supervised Disposability of the timing source.
Available
Holdoff
Failed
Wait To Restore

Table 73: AP: / unit-x, Status - ESO-2 - General (continued)

Clock Status Selection Algo- Priority Display of the configured selection algorithm
rithm QL for the timing sources:
- Priority Table based
- Quality Level based
Selected Clock <Timing Source> Display of the selected timing source.
Source
ESO-2 Signal Sta- Active Display of the current operation mode of the
tus Squelched ESO-2 clock output:
- Active: The ESO-2 clock signal is active
- Squelched: The ESO-2 clock signal is
squelched due to the selected timing source
or due to the QL of the selected timing
source.
Clear WTR… Open the FOXCST dialog to select a timing
source.
Clear WTR Source List sdh-1 The WTR timer can be cleared to immediately
sdh-2 switch back from the lower priority or lower
sdh-3
sdh-4
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2

8.2.6.4 AP: / unit-x, Status - ESO-2 - Sources
Table 74: AP: / unit-x, Status - ESO-2 - Sources

Lockout Command Source sdh-1 The lockout of a port prevents the selection
sdh-2 as an ESO-2 timing source.
It is not possible to override the lockout of a
sdh-3 source with a forced or manual switch com-
sdh-4 mand.
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Lockout locked out
not locked out

Table 74: AP: / unit-x, Status - ESO-2 - Sources (continued)

Switch Command Forced Switch None Perform a forced switch to a specific timing
sdh-1 source for the ESO-2 clock output.
The switch command is only accepted if the
sdh-2 source is enabled, i.e. has a priority config-
sdh-3 ured.
If the source is not available, i.e. failed or in
sdh-4
WTR state, “Internal” is selected.
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Manual Switch None Perform a manual switch to a specific timing
sdh-1 source for the ESO-2 clock output.
The switch command is only accepted if no
sdh-2 forced switch is active and the source is avail-
sdh-3 able. The source is not available if
- disabled, or
sdh-4
- failed, or
sdh-5 - in WTR state.
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
8.2.6.5 AP: / unit-x, Status - EQP
Please note:
→ Please refer to Table 32: "FOX61x slot pairs for SAMOx EQP" (on page 89).

Table 75: AP: / unit-x, Status - EQP

EQP Group Manual Switch- Indication that the standby unit, i.e. the work-
Over Allowed ing or the protecting unit is operational and
can take over the service.
Indication that the standby unit, i.e. the work-
ing or the protecting unit is not operational
due to a failure or to isolation. A manual pro-
tection switching is not possible.
EQP Group - Units Unit <MO address> MO address of the unit belonging to the EQP
Status group.
EQP Unit Mode Undefined Mode Mode of a unit in the EQP group.
Working Unit
Protecting Unit
Active The unit is active (operational).
The unit is standby (not operational).
Failure The unit has detected failure(s).
Substituted The working unit has been taken over by the

protecting unit.
Isolated The working unit has been isolated with the

“Isolate Unit” command.
HW Compatible The working unit is hardware compatible with

the protecting unit in the EQP group.
Please refer to section 5.8.4 EQP Prerequisites
(on page 96).
SW Compatible The working unit is embedded software com-
patible with the protecting unit in the EQP
group.
Please refer to section 5.8.4 EQP Prerequisites
(on page 96).
DB Saved The configuration of the unit has been saved.
Manual Switch- Manual switch (active to standby) of the unit

Over in the EQP group.
A switch-over is performed only when the
other unit is error free and is not isolated.
Refer to the “Manual Switch-Over Allowed”
property above.
Note: The traffic will be interrupted for up to
50 ms.
Forced Switch- Forced switch (active to standby) of the unit
Over in the EQP group.
A switch-over is performed independent of
the error state of the other unit.
Note: Traffic will be interrupted for up to
50 ms.
Note: Traffic will remain interrupted if the
active unit is not operational.
Isolate Unit Isolate the working unit from the EQP group.
An isolated working unit will not perform any
protection switch action. The protection
switching state of the unit is frozen.

Table 75: AP: / unit-x, Status - EQP (continued)

Join Unit Join the isolated working unit to the EQP
group, i.e. remove the isolation.
8.2.7 AP: / unit-x, QoS

− “QoS - Rate Limiting”
− “QoS - Counters”,
− “QoS - Traffic Classification”, and
− “QoS - Resource Usage”
management functions, please refer to [1KHW029124] User Manual “Quality of Service”.
Please note:
The QoS management function is only available if at least one Ethernet or EoS port
is configured to the CVP or PWAC port type.
8.3 AP: / unit-x / port-y, y = 1 … 4 (SDH)
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 - SFP

Table 76: AP: / unit-x / port-y, Main - SFP

Equipment Inven- Equipment State OK Equipment state of the plugged SFP module.
tory Unknown
Empty
Plugged
Mismatch
Failed
Module Type 0 … 16 characters In the SFP module type the following abbrevi-
ations are used:
- SDH: SDH module
- OC3: STM-1 module
- OC12: STM-4 module
- OC48: STM-16 module
- SM: Single mode fiber
- SR: Short reach
- IR: Intermediate reach
- LR: Long reach
- XR: Enhanced long reach
Note that with electrical modules this field is
normally not specified (SFP module “unrecog-
nized”). However, some manufacturers may
show proprietary information such as “OC3-
MMODE SR, OC-3 Multi-Mode Short Reach”
which is not directly applicable to electrical
interfaces.
Manufacturer 0 … 16 characters These description fields provide information
Serial Number about the vendor, part number, revision and
Manufacturing 0 … 10 characters production date.
Date
Manufacturer ID 0 … 16 characters
Manufacturer Part 0 … 16 characters
Number
8.3.2.3 AP: / unit-x / port-y, Main - Admin And Oper Status
Table 77: AP: / unit-x / port-y, Main - Admin And Oper Status
Administrative State Up Set the IETF administrative status of the
Status Down physical SDH port.
Unused ports (without fibers or electrical
cables connected to them) should be set to
the down state, so that they do not generate
alarms (i.e. loss of signal).

Table 77: AP: / unit-x / port-y, Main - Admin And Oper Status (continued)
Operational Status State Up Display of the IETF operational status of the
Down physical SDH port.
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.3.3 AP: / unit-x / port-y, Configuration
8.3.3.1 AP: / unit-x / port-y, Configuration - PS
Table 78: AP: / unit-x / port-y, Configuration - PS

SFP SFP Port Mode STM-1 The port-1 and port-2 support STM-16 and
STM-4 STM-4. Default is STM-4. On SAMO5 the port-1
and port-2 only support STM-4.
STM-16 The port-3 and port-4 support STM-4 and
STM-1. Default is STM-1.
Automatic Laser With automatic laser shutdown (ALS)
Shutdown enabled, the laser transmitter automatically
shuts down when the received optical signal
is lost.
For further information please refer to section 6.3
Automatic Laser Shutdown and Restart (on
page 117)
Automatic Laser After an automatic laser shutdown, the laser
Restart can be restarted automatically.
page 117)
8.3.4 AP: / unit-x / port-y, Fault Management


Table 79: AP: / unit-x / port-y, Fault Management

Affecting Severity
ALS Automatic Laser Shut- Communica- Major The laser is inactive for safety rea-
down tion Alarm sons.
ENA Equipment Not Avail- Equipment Major No SFP module is present.
able Alarm
HWIC Hardware Incompati- Equipment Major The plugged SFP module is not com-
ble With Configura- Alarm patible with the application.
tion
LOS Loss Of Signal Communica- Major Loss of the optical or electrical input
tion Alarm signal (STM-LOS).
MFA Maintenance Func- Communica- Warning This alarm appears if a manual change
tion Active tion Alarm in the status/maintenance function
has been done.
TRDEG 1 Transmitter Degraded Communica- Minor The SFP module reports that the opti-
tion Alarm cal output power has fallen below the
lower power threshold (SFP specific,
typically 2 dB below the normal mod-
ule operating range).
TRF 1 Transmitter Failure Equipment Major No optical output power.
Alarm
TRPE 1 Transmitter Power Communica- Minor The SFP module reports that the opti-
Exceeded tion Alarm cal output power has exceeded the
upper power threshold (SFP specific,
typically 2 dB above the normal mod-
ule operating range).
1. The support of this alarm is only possible for SFP modules with diagnostics function. SFP modules with electrical inter-
faces do not support this alarm (no diagnostics function available).
8.3.5 AP: / unit-x / port-y, Status
8.3.5.1 AP: / unit-x / port-y, Status - DDM

Table 80: AP: / unit-x / port-y, Status - DDM

DDM Status DDM Interface Supported If diagnostic is supported, some physical
Support Not Supported parameters are displayed.
Note that all Hitachi Energy recommended SFP
Unknown modules with optical interfaces support SFP
diagnostic.
Module Tempera- °C SFP module temperature, displayed in °C.
ture
Supply Voltage V SFP supply voltage, displayed in V.
TX Bias Current mA SFP bias current, displayed in mA.
TX Output Power dBm Optical power at the transmit interface, dis-
played in dBm.
RX Input Power dBm Optical power at the receive interface, dis-
played in dBm.
Please note:
SAMOx 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.
SFP modules with the electrical STM-1 interface do not support diagnostics.
8.3.5.2 AP: / unit-x / port-y, Status - PS - ALS
Table 81: AP: / unit-x / port-y, Status - PS - ALS

Normal Laser The laser restart can be delayed up to 110 s.
Restart The “normal laser restart” option can force
the start up procedure.
Normal restart will activate the laser trans-
mitter for t = 2 ± 0.25 s.
Test Laser Restart Test laser restart will activate the laser trans-
mitter for t = 90 ± 10 s.
page 117)
Please note:
SAMOx supports laser restart for SFP modules with optical and electrical inter-
faces.
→ The laser restart function is also applied to the electrical interface.
8.4 AP: / unit-x / port-y, y = 5 … 8 (Ethernet)


− “Overview - Alarms”, and

− “Overview - Packet Connectivity” (CVP port type related)
FOX612/FOX611”.
− “Overview - Packet Connectivity” (PWAC port type related)
management function, please refer to [1KHW028618] User Manual “MPLS-TP Services”.
Please note:
The Overview - Packet Connectivity management function is only available for
ports configured to the CVP or PWAC port type.
8.4.2.1 AP: / unit-x / port-y, Main – General

For a description of the “Labels” and “Alarm Status” parameters in the
FOX612/FOX611”.
Table 82: AP: / unit-x / port-y, Main – General

Interface Status Admin Status Up Select “Up” to bring the port into service
Down Select “Down” to take the port out of service.
Oper Status Up Shows the operational state is up. The state can only
be up if the administrative state is up and there are
currently no failures.
Down Shows the operational state is down.
Testing Shows the port is in a testing state.

8.4.2.2 AP: / unit-x / port-y, Main – Physical
Table 83: AP: / unit-x / port-y, Main – Physical

Interface Status MAC Address 00:00:00:00:00:00 … Shows the physical (MAC) address of this
ff:ff:ff:ff:ff:ff port.
This parameter is read-only.
Port Speed 10 Mbit/s Shows the port speed.
100 Mbit/s This parameter is read-only.
1000 Mbit/s
MTU 42 … 1’578 … 9’194 Maximum Transmission Unit, i.e. maximum IP
Octets, packet size.
step 2 Octets The MTU size is calculated including the IP
headers.
Speed And Duplex Admin Auto Autonegotiation
10BaseT HD 10 Mbit/s, half duplex
10BaseT FD 10 Mbit/s, full duplex
100BaseTX HD 100 Mbit/s, half duplex
100BaseTX FD 100 Mbit/s, full duplex
1000BaseT FD 1’000 Mbit/s, full duplex
Operational 10BaseT HD 10 Mbit/s, half duplex
10BaseT FD 10 Mbit/s, full duplex
100BaseTX HD 100 Mbit/s, half duplex
100BaseTX FD 100 Mbit/s, full duplex
1000BaseT FD 1’000 Mbit/s, full duplex
Flow Control Admin Port Ethernet flow control according to IEEE
802.3x.
Flow control is a mechanism which allows the
Operational receiving party of a connection to control the
rate of the sending party.
Please note:
For an overview on the specific characteristics of FOX61x Switch ports, please
refer to [1KHW002460] System Description “FOX61x R15B”.


Be aware when connecting Ethernet ports configured in manual mode on SAMOx
(no autonegotiation) to Ethernet ports in autonegotiation mode, the following situa-
tion may occur:
The link will be up but the duplex settings may be inconsistent and this can result in
poor throughput performance on the link.
8.4.2.3 AP: / unit-x / port-y, Main – Port Type

− “Main - Port Type
FOX612/FOX611”.
8.4.2.4 AP: / unit-x / port-y, Main – Mirroring

FOX612/FOX611”.


Affecting Severity
LOS Loss Of Signal Communica- Major Ethernet link not established.
tion Alarm
8.4.4 AP: / unit-x / port-y, Performance Management

− “Performance Management - General Counters”,
− “Performance Management - Ethernet Counters”, and
− “Performance Management - Egress Queue Counters”
FOX612/FOX611”.
8.4.5 AP: / unit-x / port-y, Statistics

− “Statistics - General”, and
− “Statistics - Ethernet”
FOX612/FOX611”.

8.4.6 AP: / unit-x / port-y, QoS

− “QoS - Traffic Classification”,
− “QoS - TC Scheduling”, and
− “QoS - Port Shaping”
Please note:
The QoS - Rate Limiting, QoS - Counters and QoS - Traffic Classification manage-
ment functions are only available for ports configured to the CVP or PWAC port
type.
8.5 AP: / unit-x / port-y / mau, y = 5 … 8
8.5.1 AP: / unit-x / port-y / mau, Main

FOX612/FOX611”.
8.6 AP: / unit-x / port-y, y = 101 … 148 (E12) (SAMO3 only)

− “Overview - Alarms”, and
− “Overview - Cross Connections”
FOX612/FOX611”.
8.6.2.1 AP: / unit-x / port-y, Main - General

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

Administrative State Up Set the IETF administrative status of the port.
Status Down
Down port.
Testing
Unknown
Dormant
Not Present
Lower Layer Down


Affecting Severity
AIS AIS Received Communica- Minor AIS detected on the incoming P12 sig-
tion Alarm nal.
BERE3 BER > 1E-3 Communica- Major Bit error ratio >10E-3 on the incoming
tion Alarm E12 signal calculated from bipolar vio-
lations (code errors).
BERE5 BER > 1E-5 Communica- Minor Bit error ratio >10E-5 on the incoming
tion Alarm E12 signal calculated from bipolar vio-
lations (code errors).
LOS Loss Of Signal Communica- Major Loss of incoming E12 signal.
tion Alarm
has been done. E.g. applying a loop.
8.6.4 AP: / unit-x / port-y, Performance Management

for the SAMO3 E12 ports:
• “G.826” group, see section 8.6.4.1 AP: / unit-x / port-y, Performance Management - G.826
(on page 188).
• “P12 Events” group, see section 8.6.4.2 AP: / unit-x / port-y, Performance Management -
P12 Events (on page 188).
The following counter intervals are available, depending of the counter group:


Counter interval G.826 P12 Events
User Counter yes yes
History 15min yes yes
History 24h yes yes
Alarm 15min yes no
Alarm 24h yes no
8.6.4.1 AP: / unit-x / port-y, Performance Management - G.826
Table 88: PM group: G.826

Near End ES Near end count of Errored Seconds.
A second with one or more errored blocks but
with less than 30% of the blocks errored and not
part of unavailable time (UAT).
Near End SES Near end count of Severely Errored Seconds.
A second with more than 30% of the blocks
errored or with a defect signal (e.g. LOS, loss of
signal) and not part of unavailable time (UAT).
Near End BBE Near end count of Background Block Errors.
An errored block (EB, block with one or more bit
errors) occurring as part of an errored second
(ES), but not as part of a severely errored second
(SES) or unavailable time (UAT).
Near End UAT Near end count of Unavailable Time.
Unavailable time starts with 10 consecutive SES
(included in UAT) and ends with 10 consecutive
ES or error free seconds (not included in UAT).
8.6.4.2 AP: / unit-x / port-y, Performance Management - P12 Events
Table 89: PM group: P12 Events

Line Code Violations Near end bipolar violations (HDB3 line code
errors).
8.6.5 AP: / unit-x / port-y, Status
8.6.5.1 AP: / unit-x / port-y, Status - Maintenance

Table 90: AP: / unit-x / port-y, Status - Maintenance

Maintenance Loops None No loop active.
Refer to section 7.2 Loops (on page 133)
Front To Front The incoming signal from the E12 port is
looped back towards the E12 port.
The loop is removed when the configuration
is restored or the port administrative state is
set to down.
Back To Back The outgoing signal towards the E12 port is
looped back towards the backplane.
set to down.
8.7 AP: / unit-x / port-y / vc12, y = 101 … 148 (SAMO3 only)
8.7.1 AP: / unit-x / port-y / vc12, Overview

− “Overview - Cross Connections”, and
− “Overview - CTP”
FOX612/FOX611”.
8.7.2 AP: / unit-x / port-y / vc12, Main
8.7.2.1 AP: / unit-x / port-y / vc12, Main - General

FOX612/FOX611”.
8.7.2.2 AP: / unit-x / port-y / vc12, Main - Admin And Oper Status
Table 91: AP: / unit-x / port-y / vc12, Main - Admin And Oper Status
Down port.
The operational status is up if a cross connec-
Testing tion to another VC-12 resource is configured.
Unknown
Dormant
Not Present
Lower Layer Down

8.7.3 AP: / unit-x / port-y / vc12, Configuration
8.7.3.1 AP: / unit-x / port-y / vc12, Configuration - General
Table 92: AP: / unit-x / port-y / vc12, Configuration - General

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.
Trail Trace Identifier (TTI) (on page 137)
Transmitted TTI 15 characters TTI transmitted in the VC-12 path overhead
(J2 byte).
The default string is TX_UNALLOCATED_.
In the disabled mode the transmit TTI string
is TX_UNALLOCATED_ or any other config-
ured TTI.
A TTI shorter than 15 characters is automati-
cally completed with NUL characters.
Note: All entered characters are underlined.
Expected TTI 15 characters TTI expected in the VC path overhead.
The default string is RX_UNALLOCATED_.
In the disabled mode the expected TTI string
is RX_UNALLOCATED_ or any other config-
ured TTI.

Table 92: AP: / unit-x / port-y / vc12, Configuration - General (continued)

Protection Directionality Unidirectional In the unidirectional mode the path selector is
controlled by the failure state of the working
and the protecting paths, and by the WTR
timer if the revertive operation type is config-
ured.
Bidirectional In the bidirectional mode the path selector is
in addition controlled by the remote selector
state. In the bidirectional switching mode the
local and the remote path selectors are syn-
chronized to select both the same path, i.e.
both select the working path or both select
the protecting path.
The automatic protection switching (APS)
protocol used to synchronize the two selec-
tors is transported in bit 4 of the V5 byte.
AIS On Switchover AIS on Switch-Over enabled:
At a switch-over event of the path selector
the signal sent towards the E12 port can be
replaced by an AIS signal for a duration of 4 s.
If there is a mismatch in the local and remote
path selector state the AIS insertion is not
released until the mismatch state terminates.
Switch Mode Auto For testing or debugging purposes the path
Force Working selector of the SNC protected VC-12 signal
can be forced to the working or the protect-
Force Protecting ing path. In case the VC-12 is configured to
the bidirectional switching type also the
remote selector will switch to the configured
path.
The forced configurations override the exter-
nal commands available in the CTP status dia-
log.
Note that no alarm is activated when the path
selector is forced to the working or protect-
ing path.
Select CTP WTR Select the WTR timer as configured below.
Time
Select the WTR timer as configured for the
whole unit.
See section 8.2.3.1 AP: / unit-x, Configuration -
General - SNCP Times (on page 150).
Wait-To-Restore 0 … 600 … 1800 s A path selector which selects the protecting
Time path switches back to the working path as
Equipment Com- Signal Label Default Accept and transmit the regular signal label
patibility “Asynchronous” as valid signal label.
Equipped Non-Specific Accept and transmit the signal label
“Equipped non-specific” as valid signal label.
This allows interoperability with old SDH
equipment.

8.7.3.2 AP: / unit-x / port-y / vc12, Configuration - CTP
Table 93: AP: / unit-x / port-y / vc12, Configuration - CTP

CTP Configuration Layer Rate VC12 The layer rate of this connection termination
point is fixed.
n 0 … 2 characters Number of timeslots in case of P0_nc. The
possible range is from 1 to 32.
The number of time slots of a VC-12 is not
applicable.
Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 signal in
case of P0_nc, e.g. 1 … 31.
The timeslot(s) property of a VC-12 is not
applicable.
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 VC-12.
Without a connection the parameter is empty
Directionality Bidirectional Directionality of the connection.
Unidirectional
Local Role z-End The VC-12 is the ending point of a connection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The VC-12 is the working starting point of a
protected or unprotected connection.
a-End Protecting The VC-12 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.

Table 93: AP: / unit-x / port-y / vc12, Configuration - CTP (continued)

z-End Configura- Revertive Protec- Enable revertive protection switching.
tion tion Switching The z-End will preferably select the working a-
End.
Switch-Over Log- Enable the logging of the protection switch-
ging over events.
8.7.4 AP: / unit-x / port-y / vc12, Fault Management

Table 94: AP: / unit-x / port-y / vc12, Fault Management

Affecting Severity
AIS AIS Received Communica- Minor Failure in the received optical or elec-
tion Alarm trical signal, in the RS or MS layer, or in
the VC-4 layer or in the P12 VC-12 layer
(TU-12-AIS).
APSFOP APS Failure Of Proto- Communica- Minor The remote path selector state
col tion Alarm received in the V5/4 bit mismatches
the local path selector state.
Note that there are transient states
where the remote path selector indi-
cation does not reflect the actual path
selector state, e.g. when after a bidi-
rectional interruption of the working
path only one direction is brought into
service again. In this case the APS Fail-
ure Of Protocol alarm is raised even
though both selectors still select the
protecting path.
DEG Degraded Signal Communica- Major The bit error ratio on the working
tion Alarm channel is above the configured
“Degraded Defect Threshold” for VC-
12.
EXC Excessive Bit Error Communica- Major The bit error ratio is above the config-
Rate tion Alarm ured “Excessive Defect Threshold” for
VC-12.
FDPF Far End Degraded Communica- Warning ES ≥ 648 or SES ≥ 33 or BBE ≥ 1620
Performance tion Alarm over a 24 hour interval at the far end.
The alarm status is reset after a 24
hour interval with ES = 0 and SES = 0.
The alarm can be cleared by resetting
the corresponding PM alarm counter.
FUPF Far End Unacceptable Communica- Warning ES ≥ 120 or SES ≥ 15 or BBE ≥ 300 over
Performance tion Alarm a 15 min. interval at the far end.
min. interval with ES ≤ 2 and SES = 0
and BBE ≤ 12.

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

Affecting Severity
LOP Loss Of Pointer Communica- Major Eight consecutive invalid TU-12
tion Alarm pointer values have been received (TU-
12-LOP).
tion Active tion Alarm in the status function has been done.
E.g. external switch request.
NDPF Near End Degraded Communica- Warning ES ≥ 648 or SES ≥ 33 or BBE ≥ 1620
Performance tion Alarm over a 24 hour interval at the near end.
NUPF Near End Unaccept- Communica- Warning ES ≥ 120 or SES ≥ 15 or BBE ≥ 300 over
able Performance tion Alarm a 15 min. interval at the near end.
and BBE ≤ 12.
PLM Payload Mismatch Communica- Major The received and accepted trail signal
tion Alarm label does not indicate the expected
“Asynchronous” in the VC-12 (VC-12-
PLM).
RDEG Redundant Trail Communica- Minor The bit error ratio on the protecting
Degraded Signal tion Alarm channel is above the configured
12.
For unprotected connections the
alarm is not applicable.
Note that this alarm is not monitored
by default.
RDI Remote Defect Indica- Communica- Minor The far end equipment has one or
tion tion Alarm more of the following defects:
VC-4-LOM, VC-4-PLM, TU-12-LOP, TU-
12-AIS, VC-12-UNEQ, VC-12-TIM.
RTSF Redundant Trail Sig- Communica- Minor For unprotected connections: Alarm
nal Failure tion Alarm not available.
For protected connections: Signal fail-
ure on the working or protecting
channel subnetwork connection.
Alarm activation criteria: Server signal
fail or VC-12 signal failure.
by default.
TIM Trace Identifier Mis- Communica- Major The received and accepted TTI does
match tion Alarm not match the expected VC-12 TTI.
TSF Trail Signal Failure Communica- Major For unprotected connections: Signal
tion Alarm failure on the working channel subnet-
work connection.
ure on the working and protecting
by default.

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

Affecting Severity
UNEQ Unequipped Communica- Major The received and accepted trail signal
tion Alarm label indicates “Unequipped” (VC-12-
UNEQ).
Please note:
The monitoring of the RDEG, TSF and RTSF alarms is disabled by default.
8.7.5 AP: / unit-x / port-y / vc12, Performance Management

The PM parameters are presented in different groups. The following counter groups are avail-
able for the SAMO3 VC-12 signals:
• “G.826” group, see section 8.7.5.1 AP: / unit-x / port-y / vc12, Performance Management -
G.826 (on page 195).
• “Unfiltered Events” group, see section 8.7.5.2 AP: / unit-x / port-y / vc12, Performance Man-
agement - Unfiltered Events (on page 195).

Counter interval G.826 Unfiltered Events
History 24h yes yes
Alarm 15min yes no
Alarm 24h yes no
8.7.5.1 AP: / unit-x / port-y / vc12, Performance Management - G.826
Table 96: PM group: G.826 VC-12

Near End ES VC near end errored second.
Near End SES VC near end severely errored second.
Near End BBE VC near end background block errors.
Near End UAT VC near end unavailable time.
Far End ES VC far end errored second.
Far End SES VC far end severely errored second.
Far End BBE VC far end background block errors.
Far End UAT VC far end unavailable time.
Path UAT VC path unavailable time.
8.7.5.2 AP: / unit-x / port-y / vc12, Performance Management - Unfiltered Events

Protection Switches SNC protection switchover event.

8.7.6 AP: / unit-x / port-y / vc12, Status
8.7.6.1 AP: / unit-x / port-y / vc12, Status - General
Table 98: AP: / unit-x / port-y / vc12, Status - General

TTI Status, Work- Received TTI 0 … 15 characters Display of the received TTI in the J2 byte in
ing Trail the VC-12 path overhead.
TTI State OK TTI supervision is enabled and the received
TTI equals the expected TTI.
Mismatch TTI supervision is enabled and the received
TTI is not equal to the expected TTI.
Not Checked TTI supervision is not enabled.
TTI Status, Pro- Received TTI 0 … 15 characters Display of the received TTI in the J2 byte in
tecting Trail the VC-12 path overhead.

Table 98: AP: / unit-x / port-y / vc12, Status - General (continued)

Server Signal Sta- Server Signal State OK Failure indication of the VC-12 server signal,
tus, Working Trail TU-AIS i.e. the TU-12 signal.
Signal fail means a SSF in the server signal.
TU-LOP
Signal Fail
Signal Label Asynchronous The VC-12 layers are able to transport a vari-
Unequipped ety of client signals applied to the layer via
different adaptation functions. The informa-
Unknown tion about the signal type is carried in the
<Any other signal label> (trail) signal label, transported in the V5 byte
of the VC-12 path overhead.
SAMO3 inserts the signal label “Asynchronous”
for all VC-12 signals with tributaries from an E12
port.
VC-12 signals without cross connection insert
the signal label “Unequipped”.
VC-12 signals with a server failure show an
“Unknown” signal label.
Signal Label State OK The received signal label equals the expected
signal label, i.e. “Asynchronous”.
Mismatch The received signal label is not equal to the
expected signal label.
Not Checked The VC-12 is not used for transport, i.e. no
cross connections have been configured.
RDI State The VC-12 path remote defect indication (RDI)
displays the received RDI state of the active
trail which is sent back from the far end ter-
mination function, if either TU-12 server sig-
nal failure or a trail signal failure is being
detected.
RDI is transported in the V5 byte of the VC-12
path overhead. It can be “true” or “false”.
Note that the VC signal status is not filtered.
E.g. a server signal AIS has as a consequence
also a signal label mismatch.
Note that these states are not visible in the
alarm list since the alarms are filtered.
tus, Protecting TU-AIS i.e. the TU-12 signal.
Trail Signal fail means a SSF in the server signal.
TU-LOP
Signal Fail
SAMO3 inserts the signal label “Asynchronous”
for all VC-12 signals with tributaries from an E12
port.

Table 98: AP: / unit-x / port-y / vc12, Status - General (continued)

detected.
Bidirectional Pro- Working Remote Working Display of the remote selector status, trans-
tection Switching Active Trail Protecting ported in the working trail.
Not available means that the bidirectional
Not Available protection switching is not enabled or the
trail is faulty.
Bit 4 of the V5 VC-12 path overhead is used
for the Hitachi Energy proprietary transport of the
automatic protection switching (APS) protocol.
The APS Protocol Failure alarm is activated
when the received APS protocol state on the
active trail mismatches the local path selector
state.
Protecting Remote Working Display of the remote selector status, trans-
Active Trail Protecting ported in the protecting trail.
trail is faulty.
8.7.6.2 AP: / unit-x / port-y / vc12, Status - CTP

Table 99: AP: / unit-x / port-y / vc12, Status - CTP

Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the VC-12 is
connected to, e.g. /unit-18/vc4/vc4-1/klm-
112.
Working Trail, Sta- OK No failure on the received signal at the
tus remote CTP.
SF Signal Fail status on the received signal at the
remote CTP.
SD CAS AIS status in the received signal at the
remote CTP, i.e. an all ‘1’ signal in time slot 16.
Not Available Signal Degraded status on the received signal
at the remote CTP.
Protecting Trail, <MO Address> The status of the received signal is not avail-
Remote CTP able at the remote CTP, e.g. when the local
CTPs role is a-end in a unidirectional connec-
tion.
Protecting Trail, OK No failure on the received signal at the
Status remote CTP.
remote CTP.
at the remote CTP.
Active Trail Working The status of the received signal is not avail-
able at the remote CTP, e.g. when the local
tion.
Protecting The trail from the a-End protecting remote
CTP has been selected.
Not Available There is no active trail.
Protecting/Wait-To- In case of revertive protection switching the
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
working trail.

8.8 AP: / unit-x / sdh
8.8.1 AP: / unit-x / sdh, Overview

− “Overview - STM Allocation”
FOX612/FOX611”.
8.8.2 AP: / unit-x / sdh, Main

FOX612/FOX611”.
8.9 AP: / unit-x / sdh / sdh-y, y = 1 … 8

The sdh-5 to sdh-8 access points are only available within an EQP group.
8.9.1 AP: / unit-x / sdh / sdh-y, Overview

− “Overview - STM Allocation”
FOX612/FOX611”.
8.9.2 AP: / unit-x / sdh / sdh-y, Main
8.9.2.1 AP: / unit-x / sdh / sdh-y, Main - General

FOX612/FOX611”.
8.9.2.2 AP: / unit-x / sdh / sdh-y, Main - Admin And Oper Status

Table 100: AP: / unit-x / sdh / sdh-y, Main - Admin And Oper Status
Administrative State Up Set the IETF administrative status of the SDH
Status Down logical port.

Down logical SDH port.
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.9.3 AP: / unit-x / sdh / sdh-y, Configuration
8.9.3.1 AP: / unit-x / sdh / sdh-y, Configuration - RS
Table 101: AP: / unit-x / sdh / sdh-y, Configuration - RS

Port Port Mode STM-1 SDH port-1, port-2, port-5 and port-6 can be
STM-4 configured to STM-16 or STM-4. The default
value is STM-4. On SAMO5 the port-1, port-2,
STM-16 port-5 and port-6 only support STM-4.
SDH port-3, port-4, port-7 and port-8 can be
configured to STM-4 or STM-1. The default
value is STM-1.
Please note that changing the port mode will
remove any existing cross connections of the
underlying VC-4 signals.
This configuration has to match the configu-
ration of the plugged SFP module.
Note that multirate SFP modules are available
that can be used for several SDH data rates. A
multirate SFP module will be set according to
the port type configuration.
Note that the optical or electrical type config-
uration is done automatically by the plugged
SFP module.
Note that when MSP is enabled the port mode
cannot be changed.

Table 101: AP: / unit-x / sdh / sdh-y, Configuration - RS (continued)

Transmitted TTI 15 characters TTI transmitted in the J0 byte of the RS over-
head.
ured TTI.
Expected TTI 15 characters TTI expected in the J0 byte of the RS over-
head.
ured TTI.

8.9.3.2 AP: / unit-x / sdh / sdh-y, Configuration - MS

Table 102: AP: / unit-x / sdh / sdh-y, Configuration - MS

Signal Quality Excessive Defect 10E-3 … 10E-5 The bit error ratio threshold for the excessive
Threshold signal defect is configurable.
In the MS layer the error detection code evalu-
ates the BIP-384 (STM-16), the BIP-96 (STM-4)
or BIP-24 (STM-1) as a BIP-1.
Please refer to section 7.3 Detection of Signal
excessive signal defect evaluation.
Degraded Defect 10E-5 … 10E-6 … 10E-8 The bit error ratio threshold for the degraded
Threshold signal defect is configurable.
In the MS layer the error detection code evalu-
ates the BIP-384 (STM-16), the BIP-96 (STM-4)
or BIP-24 (STM-1) as a BIP-1.
Please refer to section 7.3 Detection of Signal
degraded signal defect evaluation.
SSM Enable or disable the usage of the synchroni-
zation status message (SSM).
The SSM is carried in the S1 byte of the MS
overhead and contains signal quality informa-
tion (QL 1-15), used for the timing source
selection in the SETS.
For further information please refer to
[1KHW029105] User Manual “Synchronization”.
SDH Routing Table Source sdh-1 SETS timing source signal.
sdh-3
sdh-4
sdh-5
sdh-6
sdh-7
sdh-8
PDH Clock Source 1
PDH Clock Source 2
PDH Clock Source 3
PDH Clock Source 4
ESI-2
Internal
Synchronization Can Be Used A STM-16, STM-4 or STM-1 output signal
Usability Do Not Use transports the SETS timing. The signal trans-
mitted onwards can be tagged as “Do not
use” or “Can be used” in the SSM depending
on its own active timing source.
The default value for the own source is “Do
Not Use”.
“Synchronization” for a description of the quality
level handling.
Input Mapping Received QL 1 … 15 A received quality level in the range 1 to 15 can
Table Adapted QL 1 … 15 be adapted to any other QL which will then be
used in the SETS and ESO-2 selection process.
Note that a lower QL means a higher clock
quality.

Table 102: AP: / unit-x / sdh / sdh-y, Configuration - MS (continued)

Output Mapping Transmitted QL 1 … 15 A SETS internally used quality level in the
Table Adapted QL 1 … 15 range 1 to 15 can be adapted to any other QL
which will then be used in the SSM of the cor-
responding transmit signal.
Note that a lower QL means a higher clock
quality.
“Synchronization” for a description of the quality
level handling.
8.9.3.3 AP: / unit-x / sdh / sdh-y, Configuration - MSP
Table 103: AP: / unit-x / sdh / sdh-y, Configuration - MSP

MSP Protection None Enable or disable multiplex section protec-
IntraCard tion.
Note that the two SDH ports constituting an
InterCard MSP pair must be configured to the same
STM type (STM-16, STM-4 or STM-1).
For further information please refer to section
5.7.1 Multiplex Section Protection (MSP) (on
page 76)
Mode Unidirectional On a failure in one direction of a working mul-
tiplex section, only the failed direction is
switched to the protecting multiplex section.
The protocol in the K1 and K2 bytes is not
used.
Bidirectional On a failure in one direction of a working mul-
tiplex section, both directions are switched to
the protecting multiplex section using the
protocol in the K1 and K2 bytes of the pro-
tecting channel.
8.9.3.4 AP: / unit-x / sdh / sdh-y, Configuration - DCC

Table 104: AP: / unit-x / sdh / sdh-y, Configuration - DCC

DCC DCC Type None Disable the usage of the RSOH and MSOH
data communication channel (DCC).
Embedded Communication Channel (ECC) (on
page 75)
RSOH Use the DCC in the regenerator section over-
head:
Bytes D1 to D3, 192 kbit/s.
MSOH Use the DCC in the multiplex section over-
head:
Bytes D4 to D12, 576 kbit/s.
Both Use the DCC in the regenerator and multiplex
section overhead.
Please note:
→ If one of the vc12-61 to vc12-64 resources has already a channel configured, no
RS or MS DCC can be configured.
Please note:
In an MSP protected path the DCC is not protected.
→ The DCC configuration and cross connection must be done on the working and
on the protecting section. The selection of the active section must be handled
by the management communication network.
Please note:
A DCC cannot be used as a-End in a protected connection.
8.9.4 AP: / unit-x / sdh / sdh-y, Fault Management

Table 105: AP: / unit-x / sdh / sdh-y, Fault Management

Affecting Severity
AIS AIS Received Communica- Minor Multiplex Section AIS received due to a
tion Alarm failure in the received optical or elec-
trical signal or in the RS layer.
DEG Degraded Signal Communica- Major The bit error ratio is above the config-
tion Alarm ured “Degraded Defect Threshold” for
the logical SDH port.
the logical SDH port.

Table 105: AP: / unit-x / sdh / sdh-y, Fault Management (continued)

Affecting Severity
LOF Loss Of Frame Communica- Major Loss of frame of the optical or electri-
tion Alarm cal input signal (STM-LOF).
MSFDPF MS Far End Degraded Communica- Warning ES ≥ 1728 or SES ≥ 22 or BBE ≥ 62’200
Performance tion Alarm over a 24 hour interval at the far end
input signal.
MSFUPF MS Far End Unaccept- Communica- Warning ES ≥ 114 or SES ≥ 10 or BBE ≥ 27’000
able Performance tion Alarm over a 15 min. interval at the far end
input signal.
and BBE ≤ 1100.
MSNDPF MS Near End Communica- Warning ES ≥ 1728 or SES ≥ 22 or BBE ≥ 62’200
Degraded Perfor- tion Alarm over a 24 hour interval at the near end
mance input signal.
MSNUPF MS Near End Unac- Communica- Warning ES ≥ 114 or SES ≥ 10 or BBE ≥ 27’000
ceptable Performance tion Alarm over a 15 min. interval at the near end
input signal.
and BBE ≤ 1100.
MSPFOP MSP Failure Of Proto- Communica- Warning This alarm appears if the multiplex
col tion Alarm section protection protocol in the pro-
tecting channel fails, e.g. when the
remote side is not configured to bidi-
rectional mode.
MSPMFA MSP Maintenance Communica- Warning This alarm appears if a manual change
Function Active tion Alarm in the status/maintenance function
has been done. E.g. Manual switching
request.
RDI Remote Defect Indica- Communica- Minor Multiplex Section RDI received from
tion tion Alarm the far end equipment. RDI is acti-
vated by one or more of the following
defects:
STM-LOS, STM-LOF, RS-TIM, MS-AIS
match tion Alarm not match the expected RS TTI.
Please note:
The errored signal, degraded signal and performance alarm thresholds are the
same for MS16, MS4 and MS1.

8.9.5 AP: / unit-x / sdh / sdh-y, Performance Management

able for the SAMOx logical SDH ports:
• “Unfiltered Events” group, see section 8.9.5.1 AP: / unit-x / sdh / sdh-y, Performance Man-
agement - Unfiltered Events (on page 208),
• “G.826” group, see section 8.9.5.2 AP: / unit-x / sdh / sdh-y, Performance Management -
G.826 (on page 208).

History 24h yes yes
Alarm 15min yes no
Alarm 24h yes no
8.9.5.1 AP: / unit-x / sdh / sdh-y, Performance Management - Unfiltered Events

Out Of Frame Physical section out of frame event
Protection Switches Multiplex section protection switchover event
Please note:
The “Out Of Frame” counter will be available in a future release.
8.9.5.2 AP: / unit-x / sdh / sdh-y, Performance Management - G.826

Near End ES Multiplex section near end errored second.
Near End SES Multiplex section near end severely errored sec-
ond.
Near End BBE Multiplex section near end background block
errors.
Near End UAT Multiplex section near end unavailable time.
Far End ES Multiplex section far end errored second.
Far End SES Multiplex section far end severely errored sec-
ond.
Far End BBE Multiplex section far end background block
errors.
Far End UAT Multiplex section far end unavailable time.
Path UAT Multiplex section path unavailable time.

8.9.6 AP: / unit-x / sdh / sdh-y, Status
8.9.6.1 AP: / unit-x / sdh / sdh-y, Status - RS
Table 109: AP: / unit-x / sdh / sdh-y, Status - RS

TTI Status Received TTI 0 … 15 characters Display of the received TTI in the J0 byte of
the RS overhead.
8.9.6.2 AP: / unit-x / sdh / sdh-y, Status - MS
Table 110: AP: / unit-x / sdh / sdh-y, Status - MS

Clock Quality Received QL Unknown The synchronization method “None” has been
configured.
Do Not Use Received SSM value = 15.
1 … 14 Display of the received SSM value < 15.
Transmitted QL Unknown The SSM parameter has been disabled.
Do Not Use The “Do Not Use” quality level is transmitted
as SSM value = 15.
1 … 14 Display of the transmitted SSM value < 15.
8.9.6.3 AP: / unit-x / sdh / sdh-y, Status - MSP
“External Command” dialog:

Table 111: AP: / unit-x / sdh / sdh-y, Status - MSP

MSP Status MSP Group 0 … 30 characters Display of the SDH ports belonging to the
MSP group.
Please refer to section 5.7.1 Multiplex Section
Protection (MSP) (on page 76) for further infor-
mation.
Status Active Indication of the current port usage with
Standby respect to the STM-16, STM-4 or STM-1 traffic
signal:
- Active: The received SDH traffic is pro-
cessed.
- Standby: The received SDH traffic is not pro-
cessed.
The active port can be the working or the pro-
tecting channel.
Not Available MSP is not enabled.
SRQ SRQ are the signal requests. SRQ indicate the
result of the receive signal monitoring. The
states are:
No Request No request: No switching request (due to SF
or SD) is pending for the port.
SF High A switching request due to SF (signal fail) is
pending.
SD High A switching request due to SD (signal
degraded) is pending.
Not Available MSP is not enabled.

Table 111: AP: / unit-x / sdh / sdh-y, Status - MSP (continued)

External Com- External commands are the switching
mand requests applied by the user via the FOXCST.
The list below shows the external commands for
MSP in the descending order of priority. Please
note the restrictions on effectiveness for some of
the commands:
Clear Clears all switching requests listed below.
Lockout Of Protection Protecting channel only.
(Protecting Only) This command blocks all switching requests
to switch the active channel from the working
to the protecting channel.
Forced Switch Switches the active channel to the port where
the command has been applied to, unless an
equal or higher priority switch command is in
effect.
Since a forced switch has higher priority than
SF or SD on the working channel, this com-
mand will be carried out regardless of the
condition of the working channel.
Note that an SF condition on the protecting
channel has higher priority than a forced
switch. Therefore it is not possible to switch
from the working channel to the protecting
channel if this channel has SF.
Manual Switch Switches the active channel to the port where
the command has been applied to, unless an
equal or higher priority switch command is in
effect or an SF or SD condition exists on this
channel.
Since manual switch has lower priority than
SF or SD on a working or protecting channel,
this command will be carried out only if the
channel is not in SF or SD condition.
Exercise (Working Only) Effective for the bidirectional MSP mode and
working channel only.
This command checks the responses of auto-
matic protection switching (APS) bytes to a
switch request, unless the protecting chan-
nel is in use. The switch is not actually com-
pleted for the traffic signal.
The remote request will display a “Reverse
Request”.
None No external request is issued. The external
command status remains unchanged.

Table 111: AP: / unit-x / sdh / sdh-y, Status - MSP (continued)

Remote Request The remote request indication is for the bidi-
rectional MSP mode available only.
In the bidirectional mode it is possible to indi-
cate locally the requests issued by the remote
interface. This information is transmitted via
the K1/K2 bytes in the SOH.
Lockout Of Protection
Forced Switch
Signal Fail High Priority
Signal Fail Low Priority
Signal Degrade High Pri-
ority
Signal Degrade Low Pri-
ority
Manual Switch
Wait To Restore
Exercise
Reverse Request
Do Not Revert
No Request
None
External Com- Open the FOXCST dialog to apply an external
mand … command to a port of the MSP group.
External Com- Port port-x (Working Intrac- Select the port where the external command
mand ard) or will be applied to.
port-x (Working Inter-
card)
port-x (Protecting Intrac-
ard) or
port-x (Protecting Inter-
card)
External Com- None For the description refer to the External com-
mand Clear mand status above.
Forced Switch
Manual Switch
Exercise (Working Only)
Lockout Of Protection
(Protecting Only)
Please note:
The MSP status is available only on the working logical SDH ports.
Please note:
MSP with SAMOx provides non revertive protection switching, i.e. if after a protec-
tion switching to the protecting channel the working channel is operational again,
there is no automatic switching back to the working channel.
→ The switching back must be ordered by an external command (manual switch or
forced switch).

8.10 AP: / unit-x / sdh / sdh-y / dccm and dccr, y = 1 … 8

The following management functions are related to the access points dccm and dccr, but the
screenshots shown are only taken from the dccm access point.
The dccm is the access point for the multiplex section overhead (MSOH) DCC. The dccr is the
access point for the regenerator section overhead (RSOH) DCC.
8.10.1 AP: / unit-x / sdh / sdh-y / dccm and dccr, Overview

FOX612/FOX611”.
8.10.2 AP: / unit-x / sdh / sdh-y / dccm and dccr, Main
8.10.2.1 AP: / unit-x / sdh / sdh-y / dccm and dccr, Main - General
FOX612/FOX611”.
8.10.2.2 AP: / unit-x / sdh / sdh-y / dccm and dccr, Main - Admin And Oper Status
Table 112: AP: / unit-x / sdh / sdh-y / dccm and dccr, Main - Admin And Oper Status
Down DCC signal.
The operational state is up when the logical
Testing SDH port administrative state is up.
Unknown
Dormant
Not Present
Lower Layer Down

8.10.3 AP: / unit-x / sdh / sdh-y / dccm and dccr, Configuration
8.10.3.1 AP: / unit-x / sdh / sdh-y / dccm and dccr, Configuration - CTP
Table 113: AP: / unit-x / sdh / sdh-y / dccm and dccr, Configuration - CTP
CTP Configuration Layer Rate P0_nc The layer rate of the connection termination
point is P0_nc.
The number of time slots of a RSOH DCC is 3,
the number of time slots of a MSOH DCC is 9.
The timeslot(s) property of a DCC is not
applicable.
Connected to Remote CTP <MO address> Address string of a connections remote end.
Connection Index 0 … 65’535 Index of a connection assigned to the DCC.
Unidirectional
Local Role z-End The DCC is the ending point of a connection.
“TDM Services”
a-End Working The DCC is the working starting point of a
a-End Protecting The DCC is the protecting starting point of a
“TDM Services”
nection.

Table 113: AP: / unit-x / sdh / sdh-y / dccm and dccr, Configuration - CTP (continued)
End.
Non revertive protection switching will be
available in a future release.
CAS AIS Supervi- Use CAS AIS as protection switching criterion.
sion CAS AIS supervision is not applicable with a
DCC.
ging over events.
8.10.4 AP: / unit-x / sdh / sdh-y / dccm and dccr, Fault Management
Table 114: AP: / unit-x / sdh / sdh-y / dccm and dccr, Fault Management
Affecting Severity
8.10.5 AP: / unit-x / sdh / sdh-y / dccm and dccr, Status
8.10.5.1 AP: / unit-x / sdh / sdh-y / dccm and dccr, Status - CTP

Table 115: AP: / unit-x / sdh / sdh-y / dccm and dccr, Status - CTP
Remote CTP tion termination point) where the DCC signal
is connected to, e.g. /unit-10/port-3/chan-1.
tus remote CTP.
remote CTP.
at the remote CTP.
tion.
Status remote CTP.
remote CTP.
at the remote CTP.
tion.
protecting trail.
working trail.
8.11 AP: / unit-x / sdh / sdh-y / j-z, y = 1 … 8

z = 1 … 16 for STM-16 ports.
z = 1 … 4 for STM-4 ports.
z = 1 for STM-1 ports.

8.11.1 AP: / unit-x / sdh / sdh-y / j-z, Overview

FOX612/FOX611”.
8.11.2 AP: / unit-x / sdh / sdh-y / j-z, Main
8.11.2.1 AP: / unit-x / sdh / sdh-y / j-z, Main - General

FOX612/FOX611”.
8.11.2.2 AP: / unit-x / sdh / sdh-y / j-z, Main - Admin And Oper Status
Table 116: AP: / unit-x / sdh / sdh-y / j-z, Main - Admin And Oper Status
Down AU-4 signal.
The operational state is up when the port
Testing administrative state is up and a sink connec-
Unknown tion to another VC-4 resource is configured
and no major defect is active.
Dormant
Not Present
Lower Layer Down

8.11.3 AP: / unit-x / sdh / sdh-y / j-z, Configuration
8.11.3.1 AP: / unit-x / sdh / sdh-y / j-z, Configuration - CTP
Table 117: AP: / unit-x / sdh / sdh-y / j-z, Configuration - CTP

CTP Configuration Layer Rate VC4 The layer rate of the connection termination
point is VC-4.
applicable.
applicable.
Connection Index 0 … 65’535 Index of a connection assigned to the VC-4.
Unidirectional
“TDM Services”

Table 117: AP: / unit-x / sdh / sdh-y / j-z, Configuration - CTP (continued)
“TDM Services”
nection.
End.
ging over events.
8.11.4 AP: / unit-x / sdh / sdh-y / j-z, Fault Management

Table 118: AP: / unit-x / sdh / sdh-y / j-z, Fault Management

Affecting Severity
8.11.5 AP: / unit-x / sdh / sdh-y / j-z, Status
8.11.5.1 AP: / unit-x / sdh / sdh-y / j-z, Status - CTP

Table 119: AP: / unit-x / sdh / sdh-y / j-z, Status - CTP

Remote CTP tion termination point) where the VC-4 signal
is connected to, e.g. /unit-18/sdh/sdh-3/j-1.
tus remote CTP.
remote CTP.
at the remote CTP.
tion.
Status remote CTP.
remote CTP.
at the remote CTP.
tion.
protecting trail.
working trail.
8.12 AP: / unit-x / vc4
8.12.1 AP: / unit-x / vc4, Overview


− “Overview - VC4 Overview”, and
− “Overview - VC4 TUG Allocation”
FOX612/FOX611”.
8.12.2 AP: / unit-x / vc4, Main

FOX612/FOX611”.
8.12.3 AP: / unit-x / vc4, Configuration
8.12.3.1 AP: / unit-x / vc4, Configuration - General
“Create VC4” dialog: “Delete VC4” dialog:
Table 120: AP: / unit-x / vc4, Configuration - General

Create VC4 … Open the FOXCST dialog to create an addi-
tional VC-4 resource with a TUG-3 structure

Table 120: AP: / unit-x / vc4, Configuration - General (continued)

VC4 VC4 Index 0 … 31 Enter the index number of the new mem-
ber to be created.
0 is a reserved value used for the auto-
assignment of a VC-4 index: The auto-
assigned index is the highest existing
index number + 1.
In the FOXCST the default value is the
autoassigned index number.
TUG-3 Structure, VC3 Structure of the first TUG-3.
k-1 VC12
TUG-3 Structure, VC3 Structure of the second TUG-3.
k-2 VC12
TUG-3 Structure, VC3 Structure of the third TUG-3.
k-3 VC12
Repetitions 1 … 100 Number of VC-4 resources to be created.
Delete VC4 … Open the FOXCST dialog to delete a VC-4
resource.
VC4 VC4 All Select the VC-4 name to be deleted.
vc4-1 … vc4-31
8.13 AP: / unit-x / vc4 / vc4-b
8.13.1 AP: / unit-x / vc4 / vc4-b, Overview

− “Overview - CTP”, and
− “Overview - VC4 TUG Allocation”
FOX612/FOX611”.
8.13.2 AP: / unit-x / vc4 / vc4-b, Main
8.13.2.1 AP: / unit-x / vc4 / vc4-b, Main - General

FOX612/FOX611”.
8.13.2.2 AP: / unit-x / vc4 / vc4-b, Main - Admin And Oper Status

Administrative State Up Set the IETF administrative status of the VC-
Status Down 4.
Unused VC-4 (without cross connection)
should be set to the down state, so that they
do not generate alarms (i.e. unequipped).
Down VC-4.
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.13.3 AP: / unit-x / vc4 / vc4-b, Configuration
8.13.3.1 AP: / unit-x / vc4 / vc4-b, Configuration - General
Table 122: AP: / unit-x / vc4 / vc4-b, Configuration - General

Transmitted TTI 15 characters TTI transmitted in the VC-4 path overhead (J1
byte).
ured TTI.
Expected TTI 15 characters TTI expected in the VC-4 path overhead.
ured TTI.

Table 122: AP: / unit-x / vc4 / vc4-b, Configuration - General (continued)

patibility “TUG Structure” as valid signal label.
equipment.
8.13.3.2 AP: / unit-x / vc4 / vc4-b, Configuration - TUG-3 Structure
Table 123: AP: / unit-x / vc4 / vc4-b, Configuration - TUG-3 Structure

TUG-3 Structure k-1 VC3 Structure of the first TUG-3.
VC12
k-2 VC3 Structure of the second TUG-3.
VC12
k-3 VC3 Structure of the third TUG-3.
VC12
Please note:
Changing the structure of a TUG-3 will delete all existing managed objects (MO) of
this TUG-3 and create the MOs according to the new TUG-3 structure.
8.13.3.3 AP: / unit-x / vc4 / vc4-b, Configuration - CTP

Table 124: AP: / unit-x / vc4 / vc4-b, Configuration - CTP

point is fixed.
applicable.
applicable.
Unidirectional
“TDM Services”
“TDM Services”
nection.
End.
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.13.4 AP: / unit-x / vc4 / vc4-b, Fault Management


Table 125: AP: / unit-x / vc4 / vc4-b, Fault Management

Affecting Severity
tion Alarm trical signal, in the RS or MS layer (AU-
4-AIS).
tion Alarm ured “Errored Signal” threshold for the
VC-4.
Rate tion Alarm ured “Errored Signal” threshold for the
VC-4.
FDPF Far End Degraded Communica- Warning ES ≥ 2’592 or SES ≥ 33 or BBE ≥ 12’960
input signal.
Performance tion Alarm a 15 min. interval at the far end input
signal.
and BBE ≤ 50.
LOM Loss Of Multiframe Communica- Major Loss of the multi-frame alignment on
tion Alarm the incoming VC-4 signal (VC-4-LOM).
Applicable only with VC-12 tributary
signals.
LOP Loss Of Pointer Communica- Major Eight consecutive invalid AU-4 pointer
tion Alarm values have been received (AU-4-LOP)
NDPF Near End Degraded Communica- Warning ES ≥ 2’592 or SES ≥ 33 or BBE ≥ 12’960
Performance tion Alarm over a 24 hour interval at the near end
input signal.
able Performance tion Alarm a 15 min. interval at the near end input
signal.
and BBE ≤ 50.
“TUG Structure” in the VC-4 (VC-4-
PLM).

Table 125: AP: / unit-x / vc4 / vc4-b, Fault Management (continued)

Affecting Severity
AU-4-LOP, AU-4-AIS, VC-4-UNEQ, VC-
4-TIM.
ure on the working or protecting VC-4
subnetwork connection.
Alarm activation criteria: AU-4-LOP,
AU-4-AIS, VC-4-UNEQ or VC-4-TIM.
by default.
match tion Alarm not match the expected VC-4 TTI (VC-
4-TIM).
tion Alarm failure on the working VC-4 subnet-
work connection.
ure on the working and protecting VC-
4 subnetwork connection.
by default.
tion Alarm label is the unequipped indication (VC-
4-UNEQ).
Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.
8.13.5 AP: / unit-x / vc4 / vc4-b, Performance Management

for the SAMOx VC-4 resources:
• “G.826” group, see section 8.13.5.1 AP: / unit-x / vc4 / vc4-b, Performance Management -
G.826 (on page 228).

Counter interval G.826
User Counter yes
History 15min yes
History 24h yes
Alarm 15min yes
Alarm 24h yes

8.13.5.1 AP: / unit-x / vc4 / vc4-b, Performance Management - G.826

8.13.6 AP: / unit-x / vc4 / vc4-b, Status
8.13.6.1 AP: / unit-x / vc4 / vc4-b, Status - General
Table 128: AP: / unit-x / vc4 / vc4-b, Status - General

the VC-4 path overhead.
tus AU-AIS i.e. the AU-4 signal.
AU-LOP

Table 128: AP: / unit-x / vc4 / vc4-b, Status - General (continued)

Signal Label TUG Structure The VC-4 layer is able to transport a variety of
Unequipped client signals applied to the layer via different
adaptation functions. The information about
<Any other signal label> the signal type is carried in the (trail) signal
label, transported in the C2 byte of the VC-4
path overhead.
SAMOx inserts the signal label “TUG Structure”
for all VC-4 signals with tributaries from the TU-3
/ TU-12 cross connect, i.e. VC-3 and VC-12 sig-
nals from the PBUS or from the E12 ports or
from the Ethernet ports
signal label, i.e. “TUG-Structure”.
displays the received RDI state which is sent
back from the far end termination function, if
either an AU-4 server signal failure or a trail
signal failure is being detected.
RDI is transported in the G1 byte of the VC-4
E.g. a TTI mismatch in the RS layer inserts an
AIS as a consequent action. All subsequent
failures are also displayed: Signal label mis-
match.
8.13.6.2 AP: / unit-x / vc4 / vc4-b, Status - CTP

Table 129: AP: / unit-x / vc4 / vc4-b, Status - CTP

Remote CTP tion termination point) where the VC-4signal
is connected to, e.g. /unit-18/sdh/sdh-1/j-1.
tus remote CTP.
remote CTP.
at the remote CTP.
tion.
Status remote CTP.
remote CTP.
at the remote CTP.
tion.
protecting trail.
working trail.
8.14 AP: / unit-x / vc4 / vc4-b / klm-n00
8.14.1 AP: / unit-x / vc4 / vc4-b / klm-n00, Overview


FOX612/FOX611”.
8.14.2 AP: / unit-x / vc4 / vc4-b / klm-n00, Main
8.14.2.1 AP: / unit-x / vc4 / vc4-b / klm-n00, Main - General

FOX612/FOX611”.
8.14.2.2 AP: / unit-x / vc4 / vc4-b / klm-n00, Main - Admin And Oper Status
Table 130: AP: / unit-x / vc4 / vc4-b / klm-n00, Main - Admin And Oper Status
Down VC-3.
The operational state is up when the adminis-
Testing trative state of the VC-4 is up and a sink con-
Unknown nection to another VC-3 resource is
configured.
Dormant
Not Present
Lower Layer Down
8.14.3 AP: / unit-x / vc4 / vc4-b / klm-n00, Configuration
8.14.3.1 AP: / unit-x / vc4 / vc4-b / klm-n00, Configuration - CTP

Table 131: AP: / unit-x / vc4 / vc4-b / klm-n00, Configuration - CTP

point is fixed according to the TUG-3 struc-
ture configuration.
applicable.
applicable.
Unidirectional
“TDM Services”
“TDM Services”
nection.
End.
ging over events.
Please note:
8.14.4 AP: / unit-x / vc4 / vc4-b / klm-n00, Fault Management


Table 132: AP: / unit-x / vc4 / vc4-b / klm-n00, Fault Management

Affecting Severity
8.14.5 AP: / unit-x / vc4 / vc4-b / klm-n00, Status
8.14.5.1 AP: / unit-x / vc4 / vc4-b / klm-n00, Status - CTP
Table 133: AP: / unit-x / vc4 / vc4-b / klm-n00, Status - CTP

Remote CTP tion termination point) where the VC-3 is con-
nected to, e.g. /unit-20/vc4/vc4-1/klm-300.
tus remote CTP.
remote CTP.
at the remote CTP.
tion.
Status remote CTP.
remote CTP.
at the remote CTP.

Table 133: AP: / unit-x / vc4 / vc4-b / klm-n00, Status - CTP (continued)
tion.
protecting trail.
working trail.
8.15 AP: / unit-x / vc4 / vc4-b / klm-npq
8.15.1 AP: / unit-x / vc4 / vc4-b / klm-npq, Overview

FOX612/FOX611”.
8.15.2 AP: / unit-x / vc4 / vc4-b / klm-npq, Main
8.15.2.1 AP: / unit-x / vc4 / vc4-b / klm-npq, Main - General

FOX612/FOX611”.
8.15.2.2 AP: / unit-x / vc4 / vc4-b / klm-npq, Main - Admin And Oper Status

Table 134: AP: / unit-x / vc4 / vc4-b / klm-npq, Main - Admin And Oper Status
Down VC-12.
The operational state is up when the adminis-
Testing trative state of the VC-4 is up and a sink con-
Unknown nection to another VC-12 resource is
configured.
Dormant
Not Present
Lower Layer Down
8.15.3 AP: / unit-x / vc4 / vc4-b / klm-npq, Configuration
8.15.3.1 AP: / unit-x / vc4 / vc4-b / klm-npq, Configuration - CTP
Table 135: AP: / unit-x / vc4 / vc4-b / klm-npq, Configuration - CTP

point is fixed according to the TUG-3 struc-
ture configuration.
applicable.
applicable.
Unidirectional

Table 135: AP: / unit-x / vc4 / vc4-b / klm-npq, Configuration - CTP (continued)
“TDM Services”
“TDM Services”
nection.
End.
ging over events.
Please note:
8.15.4 AP: / unit-x / vc4 / vc4-b / klm-npq, Fault Management

Table 136: AP: / unit-x / vc4 / vc4-b / klm-npq, Fault Management

Affecting Severity

8.15.5 AP: / unit-x / vc4 / vc4-b / klm-npq, Status
8.15.5.1 AP: / unit-x / vc4 / vc4-b / klm-npq, Status - CTP
Table 137: AP: / unit-x / vc4 / vc4-b / klm-npq, Status - CTP

Remote CTP tion termination point) where the VC-12 sig-
nal is connected to, e.g. /unit-20/vc4/vc4-1/
klm-121.
tus remote CTP.
remote CTP.
at the remote CTP.
tion.
Status remote CTP.
remote CTP.
at the remote CTP.
tion.

Table 137: AP: / unit-x / vc4 / vc4-b / klm-npq, Status - CTP (continued)
protecting trail.
working trail.
8.16 AP: / unit-x / pdh
8.16.1 AP: / unit-x / pdh, Overview

− “Overview - Timeslot Allocation”, and
− “Overview - Unused Channels”
FOX612/FOX611”.
8.16.2 AP: / unit-x / pdh, Main

FOX612/FOX611”.
8.17 AP: / unit-x / pdh / vc12-y
8.17.1 AP: / unit-x / pdh / vc12-y, Overview

− “Overview - CTP”,
FOX612/FOX611”.

8.17.2 AP: / unit-x / pdh / vc12-y, Main
8.17.2.1 AP: / unit-x / pdh / vc12-y, Main - General

FOX612/FOX611”.
8.17.2.2 AP: / unit-x / pdh / vc12-y, Main - Admin And Oper Status
Table 138: AP: / unit-x / pdh / vc12-y, Main - Admin And Oper Status
Administrative State Up Set the IETF administrative status of the VC-
Status Down 12 signal.

Down VC-12 signal.
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.17.3 AP: / unit-x / pdh / vc12-y, Configuration
8.17.3.1 AP: / unit-x / pdh / vc12-y, Configuration - General

Table 139: AP: / unit-x / pdh / vc12-y, Configuration - General

Transmitted TTI 15 characters TTI transmitted in the VC-12 path overhead
(J2 byte).
ured TTI.
ured TTI.
Protection Directionality Unidirectional In the unidirectional mode the path selector is
and the protecting paths, and by the WTR
timer if the revertive operation type is config-
ured.
Bidirectional In the bidirectional mode the path selector is
in addition controlled by the remote selector
state. In the bidirectional switching mode the
local and the remote path selectors are syn-
chronized to select both the same path, i.e.
both select the working path or both select
the protecting path.
The automatic protection switching (APS)
protocol used to synchronize the two selec-
tors is transported in bit 4 of the V5 byte.
AIS On Switchover AIS on Switch-Over enabled:
At a switch-over event of the path selector
the signal sent towards the PBUS can be
replaced by an AIS signal for a duration of 4 s.
If there is a mismatch in the local and remote
path selector state the AIS insertion is not
released until the mismatch state terminates.
Switch Mode Auto For testing or debugging purposes the path
Force Working selector of the SNC protected VC-12 signal
can be forced to the working or the protect-
Force Protecting ing path. In case the VC-12 is configured to
the bidirectional switching type also the
remote selector will switch to the configured
path.
The forced configurations override the exter-
nal commands available in the CTP status dia-
log.
Note that no alarm is activated when the path
selector is forced to the working or protect-
ing path.

Table 139: AP: / unit-x / pdh / vc12-y, Configuration - General (continued)

Select CTP WTR Select the WTR timer as configured below.
Time Select the WTR timer as configured for the
whole unit.
See section 8.2.3.1 AP: / unit-x, Configuration -
General - SNCP Times (on page 150).
Wait-To-Restore 0 … 600 … 1800 s A path selector which selects the protecting
Time path switches back to the working path as
patibility “Asynchronous” as valid signal label.
equipment.
8.17.3.2 AP: / unit-x / pdh / vc12-y, Configuration - CTP
Table 140: AP: / unit-x / pdh / vc12-y, Configuration - CTP

point is fixed.
applicable.
applicable.
Connected To Remote CTP <MO Address> Address string of a connections remote end.
Connection Index 0 … 65‘535 Index of a connection assigned to the VC-12.

Table 140: AP: / unit-x / pdh / vc12-y, Configuration - CTP (continued)

Unidirectional
“TDM Services”
“TDM Services”
nection.
End.
ging over events.
8.17.4 AP: / unit-x / pdh / vc12-y, Fault Management

Table 141: AP: / unit-x / pdh / vc12-y, Fault Management

Affecting Severity
tion Alarm trical signal, in the RS or MS layer, or in
the VC-4 layer or in the P12 VC-12 layer
(TU-12-AIS).
APSFOP APS Failure Of Proto- Communica- Minor The remote path selector state
col tion Alarm received in the V5/4 bit mismatches
the local path selector state.
Note that there are transient states
where the remote path selector indi-
cation does not reflect the actual path
selector state, e.g. when after a bidi-
rectional interruption of the working
path only one direction is brought into
service again. In this case the APS Fail-
ure Of Protocol alarm is raised even
though both selectors still select the
protecting path.

Table 141: AP: / unit-x / pdh / vc12-y, Fault Management (continued)

Affecting Severity
DEG Degraded Signal Communica- Major The bit error ratio on the working
tion Alarm channel is above the configured
12.
VC-12.
and BBE ≤ 12.
LOP Loss Of Pointer Communica- Major Eight consecutive invalid TU-12
tion Alarm pointer values have been received (TU-
12-LOP).
and BBE ≤ 12.
“Asynchronous” in the VC-12 (VC-12-
PLM).
RDEG Redundant Trail Communica- Minor The bit error ratio on the protecting
Degraded Signal tion Alarm channel is above the configured
12.
For unprotected connections the
alarm is not applicable.
by default.
12-AIS, VC-12-UNEQ, VC-12-TIM.

Table 141: AP: / unit-x / pdh / vc12-y, Fault Management (continued)

Affecting Severity
by default.
match tion Alarm not match the expected VC-12 TTI.
work connection.
by default.
tion Alarm label indicates “Unequipped” (VC-12-
UNEQ).
Please note:
The monitoring of the RDEG, TSF and RTSF alarms is disabled by default.
8.17.5 AP: / unit-x / pdh / vc12-y, Performance Management

able for the SAMOx VC-12 signals:
• “G.826” group, see section 8.17.5.1 AP: / unit-x / pdh / vc12-y, Performance Management -
G.826 (on page 245).
• “Unfiltered Events” group, see section 8.17.5.2 AP: / unit-x / pdh / vc12-y, Performance Man-
agement - Unfiltered Events (on page 245).

History 24h yes yes
Alarm 15min yes no
Alarm 24h yes no

8.17.5.1 AP: / unit-x / pdh / vc12-y, Performance Management - G.826
Table 143: PM group: G.826 VC-12

8.17.5.2 AP: / unit-x / pdh / vc12-y, Performance Management - Unfiltered Events

Protection Switches SNC protection switchover event.

8.17.6 AP: / unit-x / pdh / vc12-y, Status
8.17.6.1 AP: / unit-x / pdh / vc12-y, Status - General
Table 145: AP: / unit-x / pdh / vc12-y, Status - General

TTI Status, Work- Received TTI 0 … 15 characters Display of the received TTI in the J2 byte in
ing Trail the VC-12 path overhead.
TTI Status, Pro- Received TTI 0 … 15 characters Display of the received TTI in the J2 byte in
tecting Trail the VC-12 path overhead.

Table 145: AP: / unit-x / pdh / vc12-y, Status - General (continued)

tus, Working Trail TU-AIS i.e. the TU-12 signal.
Signal fail means a SSF in the server signal.
TU-LOP
Signal Fail
SAMOx inserts the signal label “Asynchronous”
for all VC-12 signals with tributaries from the
PBUS.
detected.
tus, Protecting TU-AIS i.e. the TU-12 signal.
Trail Signal fail means a SSF in the server signal.
TU-LOP
Signal Fail
SAMOx inserts the signal label “Asynchronous”
for all VC-12 signals with tributaries from the
PBUS.

Table 145: AP: / unit-x / pdh / vc12-y, Status - General (continued)

detected.
Bidirectional Pro- Working Remote Working Display of the remote selector status, trans-
tection Switching Active Trail Protecting ported in the working trail.
trail is faulty.
The APS Protocol Failure alarm is activated
when the received APS protocol state on the
active trail mismatches the local path selector
state.
Protecting Remote Working Display of the remote selector status, trans-
Active Trail Protecting ported in the protecting trail.
trail is faulty.
8.17.6.2 AP: / unit-x / pdh / vc12-y, Status - CTP

Table 146: AP: / unit-x / pdh / vc12-y, Status - CTP

Remote CTP tion termination point) where the VC-12 is
connected to, e.g. /unit-18/vc4/vc4-1/klm-
112.
tus remote CTP.
remote CTP.
at the remote CTP.
tion.
Status remote CTP.
remote CTP.
at the remote CTP.
tion.
protecting trail.
working trail.

8.18 AP: / unit-x / pdh / vc12-y / p12
8.18.1 AP: / unit-x / pdh / vc12-y / p12, Overview

FOX612/FOX611”.
8.18.2 AP: / unit-x / pdh / vc12-y / p12, Main
8.18.2.1 AP: / unit-x / pdh / vc12-y / p12, Main - General

FOX612/FOX611”.
8.18.2.2 AP: / unit-x / pdh / vc12-y / p12, Main - Admin And Oper Status
Table 147: AP: / unit-x / pdh / vc12-y / p12, Main - Admin And Oper Status
Down P12 signal.
The operational status is set to up when the
Testing administrative status of the VC-12 is set to up
Unknown and no major defect is active.
Dormant
Not Present
Lower Layer Down
8.18.3 AP: / unit-x / pdh / vc12-y / p12, Configuration

Please note that the fields for some of the configuration parameters are context sensitive. Con-
figuration parameters that are not available due to a higher-ranking configuration parameter are
indicated as “NA” (not available) or “None”.
The steering parameters for the port configuration are
• Termination Mode
• Synchronization Method
The configuration strategy to be followed is from the uppermost tab (General) to the lowermost
tab (Channels), and on the tabs from the top parameter downwards.
After the parameter configuration of a higher-ranking parameter press the “Apply” button to
assign the applicable values to the lower-ranking parameters.

8.18.3.1 AP: / unit-x / pdh / vc12-y / p12, Configuration - General
Table 148: AP: / unit-x / pdh / vc12-y / p12, Configuration - General

Termination Mode Transparent Clock and data transparent.
2048 kbit/s signal with unknown structure.
Clock Master Transparent data, clock locked to PETS.
2048 kbit/s signal with unknown structure.
PCM30 Terminated with CAS, without CRC4.
ITU-T G.704 structured 2048 kbit/s signal.
PCM30C Terminated with CAS and CRC4.
PCM31 Terminated without CAS or CRC4.
PCM31C Terminated without CAS, with CRC4.
V5 Uplink Transport mode for V5 links.
The 5 Sa bits (timeslot 0, spare bits Sa4 …
Sa8) support V5.x applications.
This uplink uses CRC4.
V5 Uplink NCI Transport mode for V5 links.
The 5 Sa bits (timeslot 0, spare bits Sa4 …
Sa8) support V5.x applications.
This uplink does not offer CRC4.
Switching Bidirectional In the bidirectional mode the path selector is
and the protecting paths and by the remote
selector state. In the bidirectional switching
mode the local and the remote path selectors
are synchronized to select both the same
path, i.e. both select the working path or both
select the protecting path.
“TDM Services” for a description of the switching
criteria.
In the unidirectional mode the path selector is
and the protecting paths.
TS0 Spare Bits Sa4 … Sa8 0 Set the transmitted Sa bit value.
1 Refer to section 5.3.2 P12 Layer (on page 60).


Changing the P12 termination mode results in most cases in incompatible layer
rates or number of timeslots.
→ The channel with its CTP and the assigned connections are deleted automati-
cally and must be newly created.
→ Please refer to [1KHW002467] User Manual “TDM Services”, section 4.2.2.
8.18.3.2 AP: / unit-x / pdh / vc12-y / p12, Configuration - Synchronization
Table 149: AP: / unit-x / pdh / vc12-y / p12, Configuration - Synchronization

Synchronization Method None Do not use a synchronization method
SSM-Sa4 Use the selected Sa bit in time slot 0 for the
SSM-Sa5 transport of the synchronization status mes-
sage (SSM).
SSM-Sa6 These parameter values are only available
SSM-Sa7 with the termination modes “PCM30C” and
“PCM31C”.
SSM-Sa8
SSI-Sa5 Use the Sa5 bit in time slot 0 for the transport
of the synchronization status indication (SSI).
The SSI method is Hitachi Energy proprietary
and is compatible with the FOX51x.
This parameter value is only available with the
termination modes “PCM30”, “PCM30C”,
“PCM31” and “PCM31C”.
QL Transmission Source ESI-1 Synchronization sources are all the PDH clock
ESI-2 sources as they are configured in the FOXCST
“Synchronization” view at the AP: /Synchroniza-
<PDH Clock Source 1> tion/PETS, Configuration.
<PDH Clock Source 2>
Internal
Usage NA No synchronization method has been
selected.
CanBeUsed Transmit the QL value of the selected syn-
chronization source
DoNotUse Transmit the QL value 15, i.e. indicating that
the traffic signal cannot be used as a synchro-
nization source.

Please note:
For more information regarding quality level handling please refer to
[1KHW029105] User Manual “Synchronization”.
8.18.3.3 AP: / unit-x / pdh / vc12-y / p12, Configuration - Channels
“Create Channel” and “Create Multiple Channels” dialogs:
The “Create Advanced Channel” command displays the created channel:
“Delete Channel” dialog:
Table 150: AP: / unit-x / pdh / vc12-y / p12, Configuration - Channels

Create Channel … Open the FOXCST dialog to create one or more
channels. A channel is a connection termination
point (CTP) used as a starting or ending point of
a cross connection.
Create Channel Index 0 … 32 The channel index is used to identify the
channel.
0 is a reserved value used for the auto-assign-
ment of a channel index: The auto-assigned
index is the highest existing index number +
1.
In the FOXCST the default value is the autoas-
signed index number.

Table 150: AP: / unit-x / pdh / vc12-y / p12, Configuration - Channels (continued)
Layer Rate P12 Unstructured 2048 kbit/s.
Automatically selected when the termination
mode is configured to “Transparent” or
“Clock Master”.
P0_nc Structured n x 64 kbit/s.
Automatically selected when the termination
mode is configured to “PCM30”, “PCM30C”,
“PCM31”, “PCM31C”, “V5 Uplink” or V5 Uplink
NCI”.
n 1 … 32 Number of consecutive timeslots (valid for
P0_nc only). If the structured P12 signal, the
channel is belonging to, uses CAS the time-
slot 16 will be skipped automatically, e.g. a
channel with n = 19 and start timeslot 1 will
occupy timeslots 1 to 15 and 17 to 20 in a
PCM30 signal.
The default value is the maximum of available
timeslots.
Start Timeslot 0 … 31 First timeslot of the first channel in the struc-
tured P12 signal (valid for P0_nc only). The
minimum valid parameter value is 1.
Note that start timeslot 0 is only used for the
unstructured P12 mode.
Create Advanced Open the FOXCST dialog to create one chan-
Channel … nels with non-consecutive time slots in the struc-
tured P12 signal.
The termination mode must be configured to
“PCM30”, “PCM30C”, “PCM31” or “PCM31C”.
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”
If the structured P12 signal, the channel is
belonging to, uses CAS the timeslot 16 must
not be used, i.e. a range must be split so that
it does not include the timeslot 16, e.g. “1..15”,
“17..31”.
Create Multiple Open the FOXCST dialog to create one or more
Channels … channels.
The termination mode must be configured to
“PCM30”, “PCM30C”, “PCM31” or “PCM31C”.
Create Multiple Start Index 0 … 32 The start index is the channel index of the
Channels first channel.
1.

Table 150: AP: / unit-x / pdh / vc12-y / p12, Configuration - Channels (continued)
Number Of Chan- 1 … 32 Number of channels to be created.
nels 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. If the struc-
tured P12 signal, the channel is belonging to,
uses CAS the timeslot 16 will be skipped auto-
matically, e.g. a channel with n = 19 and start
timeslot 1 will occupy timeslots 1 to 15 and 17
to 20 in a PCM30 signal.
The default value is the maximum of available
timeslots.
The start timeslot of the first channel is the
lowest available timeslot number.
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-31 Delete a channel.
All connections assigned to the channel will
be deleted also.
8.18.4 AP: / unit-x / pdh / vc12-y / p12, Fault Management

Table 151: AP: / unit-x / pdh / vc12-y / p12, Fault Management

Affecting Severity
AIS AIS Received Communica- Minor AIS detected on the incoming P12 sig-
tion Alarm nal.
DEG Degraded Signal Communica- Major BER > 10-3 on the incoming P12 signal
tion Alarm from TS0 errors (CRC4 disabled), or
BER > 10-5 on the incoming P12 signal
calculated using CRC4 block errors
(CRC4 enabled).
FDPF Far End Degraded Communica- Warning ES ≥ 432 or SES ≥ 22 over a 24 hour
Performance tion Alarm interval at the far end.
FUPF Far End Unacceptable Communica- Warning ES ≥ 150 or SES ≥ 15 over a 15 min.
Performance tion Alarm interval at the far end.
min. interval with ES ≤ 3 and SES = 0.

Table 151: AP: / unit-x / pdh / vc12-y / p12, Fault Management (continued)
Affecting Severity
LOCM Loss Of CAS MF Communica- Major Loss of CAS multiframe alignment on
tion Alarm the incoming P12 signal.
LOF Loss Of Frame Communica- Major Loss of frame alignment on the
tion Alarm incoming P12 signal.
NCI Non CRC4 Interwork- Communica- Warning The CRC4 monitoring function is dis-
ing tion Alarm abled due to a disabled CRC4 func-
tion at the remote equipment.
NDPF Near End Degraded Communica- Warning ES ≥ 432 or SES ≥ 22 over a 24 hour
Performance tion Alarm interval at the near end.
NUPF Near End Unaccept- Communica- Warning ES ≥ 150 or SES ≥ 15 over a 15 min.
able Performance tion Alarm interval at the near end.
min. interval with ES ≤ 3 and SES = 0.
Hardware fault, AIS received, BER
> 10-3, loss of frame, loss of signal.
RLOCM Remote Loss Of CAS Communica- Minor Loss of CAS multiframe alignment on
MF tion Alarm the incoming P12 signal at the remote
equipment.
RNCI Remote Non CRC4 Communica- Minor “Non CRC4 interworking” alarm at the
Interworking tion Alarm remote equipment.
8.18.5 AP: / unit-x / pdh / vc12-y / p12, Performance Management

able for the SAMOx P12 signals:
• “G.826” group, see section 8.18.5.1 AP: / unit-x / pdh / vc12-y / p12, Performance Manage-
ment - G.826 (on page 257).
• “P12 Events” group, see section 8.18.5.2 AP: / unit-x / pdh / vc12-y / p12, Performance Man-
agement - P12 Events (on page 257).

Counter interval G.826 P12 Events
History 24h yes yes
Alarm 15min yes no
Alarm 24h yes no

8.18.5.1 AP: / unit-x / pdh / vc12-y / p12, Performance Management - G.826

Near End ES Near end count of Errored Seconds.
Near End SES Near end count of Severely Errored Seconds.
Near End BBE Near end count of Background Block Errors.
Near End UAT Near end count of Unavailable Time.
Far End ES Far end count of Errored Seconds.
Far End SES Far end count of Severely Errored Seconds.
Far End BBE Far end count of Background Block Errors.
Far End UAT Far end count of Unavailable Time.
Path UAT Path UAT is the UAT of the near end or the far
end.
8.18.5.2 AP: / unit-x / pdh / vc12-y / p12, Performance Management - P12 Events
Table 154: PM group: P12 Events

Positive Slips Near end positive frame slips.
The counter for positive frame slips is incre-
mented when the clock of the NE runs faster
than the clock provided via the ITU-T G.704
framed 2 Mbit/s traffic signal.
Negative Slips Near end negative frame slips.
The counter for negative frame slips is incre-
mented when the clock of the NE runs slower
than the clock provided via the ITU-T G.704
framed 2 Mbit/s traffic signal.
8.18.6 AP: / unit-x / pdh / vc12-y / p12, Status
8.18.6.1 AP: / unit-x / pdh / vc12-y / p12, Status - Maintenance
Table 155: AP: / unit-x / pdh / vc12-y / p12, Status - Maintenance

Maintenance Loops None No loop active.
Refer to section 7.2.2 P12 and P0-nc Loops (on
page 134)
Front To Front The incoming signal from the SDH port is
looped back towards the SDH port.
set to down.

Table 155: AP: / unit-x / pdh / vc12-y / p12, Status - Maintenance (continued)
MF State OK The CRC4 multiframe alignment state is read
only.
The CRC4 monitoring function is active.
Non CRC Interworking The CRC4 monitoring function is disabled due
to disabled CRC4 at the remote equipment.
If the CRC4 multiframe alignment is in the NCI
state no further automatic search is done. A
new search for CRC4 multiframe alignment
must be initiated manually with the “Force
CRC4 Multiframe Search” command (see
below).
None The port is configured without CRC4 monitor-
ing.
Force CRC4 Multi- Trigger a new attempt for the CRC4 multi-
frame Search frame alignment.
To check the result of the new attempt, you
have to press the “Refresh” button.
Please note:
During maintenance an NCI Alarm (non-CRC4 interworking) can appear. If this
alarm is active, and it is known that the other equipment now sends the CRC4 mul-
tiframe, the following procedure can clear the alarm:
→ Perform a “Force new search” in the CRC4 MFA status of the P12 layer, or
→ Disable CRC4 and re-enable the CRC4.
8.18.6.2 AP: / unit-x / pdh / vc12-y / p12, Status - General
Table 156: AP: / unit-x / pdh / vc12-y / p12, Status - General

TS0 Spare Bits Sa4 … Sa8 0 Display of the received Sa bit value.
1
X The Sa bit value is not available:
- The P12 termination mode is “Transparent”
or “Clock Master”
8.18.6.3 AP: / unit-x / pdh / vc12-y / p12, Status - QL

Table 157: AP: / unit-x / pdh / vc12-y / p12, Status - QL

Clock Quality Received QL Unknown The synchronization method “None” has been
configured.
Do Not Use Received SSM value = 15.
The received SSI value = 0 is interpreted as
“Do Not Use” and gets the QL = 15 assigned.
1 … 14 Display of the received SSM value < 15.
The received SSI value = 1 is interpreted as
“Can Be Used” and gets the QL = 13 assigned.
Transmitted QL Unknown The synchronization method “None” has been
configured.
Do Not Use The “Do Not Use” quality level is transmitted
as SSM value = 15, or as SSI value = 0.
1 … 14 Display of the transmitted SSM value < 15.
The transmitted SSI value = 1 is displayed as
QL = 13.
8.19 AP: / unit-x / pdh / vc12-y / p12 / chan-z
8.19.1 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Overview

FOX612/FOX611”.
8.19.2 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Main
8.19.2.1 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Main - General

FOX612/FOX611”.
8.19.2.2 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Main - Admin And Oper Status

Table 158: AP: / unit-x / pdh / vc12-y / p12 / chan-z, Main - Admin And Oper Status
Down channel.
The operational state is set to up when the
Testing channel has a sink connection configured and
Unknown no defect is active on the received signal from
the PBUS.
Dormant
Not Present
Lower Layer Down
8.19.3 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Configuration
8.19.3.1 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Configuration - CTP
Please note:
All layer rate, number of time slots and time slot allocation parameters are read
only.
→ To change a parameter the channel has to be deleted and newly created with
the modified parameters.
Table 159: AP: / unit-x / pdh / vc12-y / p12 / chan-z, 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).
Connection Index 0 … 65’535 Index of a connection assigned to the chan-
nel. Without a connection the parameter is
empty
Unidirectional

Table 159: AP: / unit-x / pdh / vc12-y / p12 / chan-z, Configuration - CTP (continued)
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
a-End Protecting The channel is the protecting starting point
of a protected connection.
“TDM Services”
nection.
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 CAS AIS supervision is only applicable with
P0-nc.
ging over events.
Please note:
8.19.4 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Fault Management

Table 160: AP: / unit-x / pdh / vc12-y / p12 / chan-z, Fault Management
Affecting Severity
has been done. E.g. manual switching
request.

Table 160: AP: / unit-x / pdh / vc12-y / p12 / chan-z, Fault Management (continued)
Affecting Severity
fail or CAS AIS.
by default.
work connection.
fail or CAS AIS.
by default.
Please note:
8.19.5 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Performance Management

for the SAMOx P12 channels:
• “Protection” group, see section 8.19.5.1 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Perfor-
mance Management - Protection (on page 262).

Counter interval Protection
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.19.5.1 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Performance Management - Protection
Table 162: PM group: Protection

Switch-Over Protection switchover event.

8.19.6 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Status
8.19.6.1 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Status - CTP
Table 163: AP: / unit-x / pdh / vc12-y / p12 / chan-z, Status - CTP
Remote CTP tion termination point) where the P12 or P0-
nc signal is connected to, e.g. /unit-21/port-
1/chan-1.
tus remote CTP.
remote CTP.
CAS AIS CAS AIS status in the received signal at the
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
tion.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P12 or P0-
nc signal is connected to, e.g. /unit-21/port-
2/chan-1.
Status remote CTP.
remote CTP.
CAS AIS CAS AIS status in the received signal at the
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
tion.

Table 163: AP: / unit-x / pdh / vc12-y / p12 / chan-z, Status - CTP (continued)
Active Trail Working The trail from the a-End working remote CTP
has been selected.
protecting trail.
working trail.
8.19.6.2 AP: / unit-x / pdh / vc12-y / p12 / chan-z, Status - Maintenance
Table 164: AP: / unit-x / pdh / vc12-y / p12 / chan-z, Status - Maintenance
Loop Status State None Deactivate any loop.
Front To Front Activate the Front-to-front loop.
For more information refer to section 7.2
Loops (on page 133).
Please note:
The channel CTP must have a cross connection configured, otherwise the loop
cannot be activated.
8.20 AP: / unit-x / eos
8.20.1 AP: / unit-x / eos, Overview

− “Overview - Statistics”
FOX612/FOX611”.

8.20.2 AP: / unit-x / eos, Main

− “Main - General”,
− “Main - Port Type”, and
FOX612/FOX611”.
8.20.3 AP: / unit-x / eos, QoS

− “QoS - Counters”, and
− “QoS - Traffic Classification”
Please note:
The QoS management functions are only available if at least one EoS port is con-
figured to the CVP or PWAC port type.
8.21 AP: / unit-x / eos / eos-y

SAMO5 supports up to 8 EoS groups.
SAMO2 and SAMO3 support up to 32 EoS groups.
8.21.1 AP: / unit-x / eos / eos-y, Overview

− “Overview - Packet Connectivity” (CVP port type related)
FOX612/FOX611”.
− “Overview - Packet Connectivity” (PWAC port type related)
management function, please refer to [1KHW028618] User Manual “MPLS-TP Services”.
Please note:
The Overview - Packet Connectivity management function is only available for
ports configured to the CVP or PWAC port type.
8.21.2 AP: / unit-x / eos / eos-y, Main
8.21.2.1 AP: / unit-x / eos / eos-y, Main - General

FOX612/FOX611”.
The “Interface Status” parameters in the

management function are only available for the EoS ports eos-1 to eos-12.
Table 165: AP: / unit-x / eos / eos-y, Main - General

Interface Status Admin Status Up Select “Up” to bring the port into service
Down Select “Down” to take the port out of service.
8.21.2.2 AP: / unit-x / eos / eos-y, Main - Physical

The “Main - Physical” management function is only available for the EoS ports eos-1 to eos-12.
Table 166: AP: / unit-x / eos / eos-y, Main - Physical

Interface Status MAC Address 00:00:00:00:00:00 … Shows the physical (MAC) address of this
1000 Mbit/s This parameter is read-only.
MTU 42 … 1’578 … 9’194 Maximum Transmission Unit, i.e. maximum IP

Octets, packet size.
step 2 Octets The MTU size is calculated including the IP
headers.

8.21.2.3 AP: / unit-x / eos / eos-y, Main - Admin And Oper Status
The “Main - Admin And Oper Status” management function is only available for the EoS ports
eos-13 to eos-32.
Table 167: AP: / unit-x / eos / eos-y, Main - Admin And Oper Status
Administrative State Up Set the IETF administrative status of the EoS
Status Down port.

Down EoS port.
Testing
Unknown
Dormant
Not Present
Lower Layer Down
8.21.2.4 AP: / unit-x / eos / eos-y, Main – Port Type

− “Main - Port Type
FOX612/FOX611”.
8.21.2.5 AP: / unit-x / eos / eos-y, Main – Mirroring

FOX612/FOX611”.
8.21.3 AP: / unit-x / eos / eos-y, Configuration
8.21.3.1 AP: / unit-x / eos / eos-y, Configuration - EoS
Please note:
An EoS port can be operated in switched, unswitched or expansion mode.
→ Please refer to section 5.4.3 Ethernet Switch (on page 63) for further informa-
tion.
“Create EoS Group …” dialog: “Delete EoS Group” dialog:

Table 168: AP: / unit-x / eos / eos-y, Configuration - EoS

Create EoS Group Open the FOXCST dialog to create an EoS
… group.
Only one EoS group can be created per EoS
port.
Delete EoS Group Delete the EoS group of this EoS port.
The confirmation is only required if a cross
connection has been created for a member of
this EoS group.
EoS Group Layer Rate VC4 VC type carrying the Ethernet payload.
VC3 Note that all members of a EoS group are of
the same VC type.
VC12
LCAS Enable or disable LCAS for the EoS group.
For further information refer to section 5.4.4.3
Link Capacity Adjustment Scheme (LCAS) (on
page 74).
When LCAS is not enabled it is not assured
that member 1 connects to member 1 on the
other side, member 2 to member 2, etc.
Number Of Mem- 0…1…n Number of VCs constituting the virtual con-
bers catenation group (VCG).
The total available tributary VC capacity per
SAMOx unit for VC-4 and VC-3 group members
only is 12 VC-4 equivalents.
The total available tributary VC capacity per
SAMOx unit for VC-4, VC-3 and VC-12 group
members is 12 VC-4 equivalents:
- Up to 8 VC-4 equivalents for VC-4 and VC-3
members,
- Up to 4 VC-4 equivalents for VC-12 mem-
bers.
The maximum number n of VC-4 is 12 per VCG
and 12 per unit.
The maximum number n of VC-3 is 24 per VCG
and 24 per unit.
The maximum number n of VC-12 is 63 per
VCG and 252 per unit.
Please refer to section 5.4.4 Ethernet over SDH
(EoS) (on page 70) for further information.
8.21.3.2 AP: / unit-x / eos / eos-y, Configuration - PHY

The “Configuration - PHY” management function is only available for the EoS ports eos-1 to
eos-12.

Table 169: AP: / unit-x / eos / eos-y, Configuration - PHY

Mode IEEE 802.3 Flow Enable or disable flow control.
Control For further information please refer to section
5.4.1.2 IEEE 802.3 Flow Control (on page 62).
Link Pass Through The link pass through feature can bring the
local link state (up or down) to the remote
Ethernet interface.
With this feature the Ethernet transport is
transparent also for link states.
For further information please refer to section
5.4.1.3 Link Pass Through (on page 62).
Single Class Traffic Use the whole bandwidth available in the EoS
group.
This is the preferred setting for the EPL
mode.
When using more than one traffic class there
is a risk that high and low priority packets are
dropped. It is therefore strongly recom-
mended to use only one single traffic class.
Use only 85% of the bandwidth available in
the EoS group.
When using more than one traffic class high
priority traffic will be forwarded preferred.
Please note:
The link pass through feature must be enabled on the Ethernet interfaces at both
sides of the SDH path to become operational.
Please note:
The link pass through feature is only available for the EoS ports in the EPL
(unswitched) mode.
Please note:
The flow control feature is only available for the EoS ports in the EPL (unswitched)
mode.

8.21.3.3 AP: / unit-x / eos / eos-y, Configuration - Port Mode
Add a VLAN to the VLAN table:
Table 170: AP: / unit-x / eos / eos-y, Configuration - Port Mode

EoS Expansion EoS Port Mode EPL Mode An EoS port in the EPL Mode accesses an
Port Handling Ethernet front port of the SAMOx unit, bypassing
the VLAN bridge. Please refer to section 5.4.3
Ethernet Switch (on page 63).
This mode is displayed and cannot be modi-
fied if an EoS port has been configured to the
EPL mode in the AP: /unit-x, Configuration -
EPL management function of the SAMOx unit.
Applicable for the EoS ports eos-1 to eos-4,
eos-9 and eos-10.
Switched Mode An EoS port in the Switched Mode accesses
This mode is displayed if an EoS port has not
been configured to the EPL mode in the AP: /
unit-x, Configuration - EPL management func-
tion of the SAMOx unit.
Applicable for the EoS ports eos-1 to eos-12.
Expansion Mode An EoS port in the Expansion Mode accesses
This mode is configurable on the EoS ports
eos-9 to eos-12.
This mode cannot be modified on the EoS
ports eos-13 to eos-32.
Applicable for the EoS ports eos-9 to eos-32.

Table 170: AP: / unit-x / eos / eos-y, Configuration - Port Mode (continued)
Expansion Mode Tagged The ingress frames must be tagged. Egress
Frame Type frames are sent out tagged.
This parameter is only applicable for the
expansion port mode.
Untagged The ingress frames must be untagged and
are tagged with the Port VLAN ID inside the
VLAN bridge
Egress frames are sent out untagged, or with
the outer VLAN tag removed.
expansion port mode.
PVID 1 … 4094 Port VLAN ID for untagged frames.
expansion port mode using the untagged
frame type.
vlanTable, vlanId 1 … 4094 List of all VLAN IDs that are transported over
the EoS port.
If the EoS port uses the untagged frame type
also the Port VLAN ID must be configured in
the VLAN table.
This list is only applicable for the expansion
port mode.
vlanTable, Add… Open the FOXCST dialog to add a new VLAN ID
to the VLAN table.
vlanTableEntry, 1 … 4094 Enter the VLAN ID
vlanId
vlanTable, Remove Remove the selected VLAN ID from the VLAN
table.

The VLAN table of an expansion port can contain multiple VLAN IDs, but a VLAN
ID cannot be member of more than one EoS port of the same expansion group.

Expansion ports do not support RSTP, MSTP or ERPS.

Expansion ports of the same expansion group have all the same QoS parameters,
as they are configured for the master expansion port.
8.21.4 AP: / unit-x / eos / eos-y, Fault Management


Table 171: AP: / unit-x / eos / eos-y, Fault Management

Affecting Severity
OPSDWN Operational State Communica- Major The EoS group is not operational.
Down tion Alarm This can be due to a loss of the total
capacity of the virtual concatenation
group.
8.21.5 AP: / unit-x / eos / eos-y, Performance Management

FOX612/FOX611”.
8.21.6 AP: / unit-x / eos / eos-y, Status
8.21.6.1 AP: / unit-x / eos / eos-y, Status - PHY

The “Status - PHY” management function is only available for the EoS ports eos-1 to eos-12.
Table 172: AP: / unit-x / eos / eos-y, Status - PHY

Status IEEE 802.3 Flow Flow control is enabled on this port.
Control Flow control is disabled on this port.
Operational State Not Available The link pass through feature is disabled on
Forced Down From this port.
Remote True The link pass through feature is enabled and
the Ethernet port is disabled due to a link
down state of the Ethernet port at the
remote end of the SDH path.
False The link pass through feature is enabled and
the Ethernet port is enabled.
8.21.7 AP: / unit-x / eos / eos-y, Statistics

FOX612/FOX611”.
The “Statistics - General” management function is only available for the EoS ports eos-1 to eos-
12.

8.21.8 AP: / unit-x / eos / eos-y, QoS

− “QoS - Traffic Classification”, and
− “QoS - TC Scheduling”
Please note:
The QoS management functions are only available for the EoS ports eos-1 to eos-
12.
Please note:
The QoS - Rate Limiting, QoS - Counters and QoS - Traffic Classification manage-
ment functions are only available for EoS ports configured to the CVP or PWAC
port type.
8.22 AP: / unit-x / eos / eos-y / eos
8.22.1 AP: / unit-x / eos / eos-y / eos, Overview

− “Overview - EoS Group Overview”
FOX612/FOX611”.
8.22.2 AP: / unit-x / eos / eos-y / eos, Main
8.22.2.1 AP: / unit-x / eos / eos-y / eos, Main - General

FOX612/FOX611”.
8.22.2.2 AP: / unit-x / eos / eos-y / eos, Main - Admin And Oper Status

Table 173: AP: / unit-x / eos / eos-y / eos, Main - Admin And Oper Status
Down eos group.
The operational state is up when the port
Testing administrative state is up and no GFPLOF or
Unknown VCGLOTC defect is active.
Dormant
Not Present
Lower Layer Down
8.22.3 AP: / unit-x / eos / eos-y / eos, Configuration
8.22.3.1 AP: / unit-x / eos / eos-y / eos, Configuration - General
“Create Member” dialog: “Delete Member” dialog:
Table 174: AP: / unit-x / eos / eos-y / eos, Configuration - General

LCAS Enable or disable LCAS for the EoS group.
For further information refer to section 5.4.4.3
Link Capacity Adjustment Scheme (LCAS) (on
page 74).
When LCAS is not enabled it is not assured
that member 1 connects to member 1 on the
other side, member 2 to member 2, etc.

Table 174: AP: / unit-x / eos / eos-y / eos, Configuration - General (continued)
Max. Differential 0 … 4 … 64 ms Set the expected maximum differential delay
Delay for the EoS group members.
The measured differential delay is available in
the EoS group status. See section 8.22.6.1 AP: /
unit-x / eos / eos-y / eos, Status - General (on
page 278).
Note that the differential delay causes also a
traffic delay of the same amount.
The configured Max. Differential Delay value 0
effectively allows the following differential
delays:
- 750 us for VC-12
- 130 us for VC-3 and VC-4
Create Member … Open the FOXCST dialog to create an additional
member to an existing EoS group.
EoS Member Member Index 0 … 63 Enter the index number of the new member
to be created.
ment of a EoS member index: The auto-
assigned index is the highest existing index
number + 1.
See also notes below.
Delete Member … Open the FOXCST dialog to delete a member
from an existing EoS group.
EoS Member Member vc12-1 … vc12-63, Select the EoS group member name to be
vc3-1 … vc3-24, deleted.
vc4-1 … vc4-12 See also notes below.
All
received TTI of all EoS group members and no
alarm is generated.
Transmitted TTI 15 characters TTI transmitted in the VC path overhead (J1
byte for VC-4 and VC-3, J2 byte for VC-12).
ured TTI.
Note that the same TTI is transmitted in every
member of an EoS group.
ured TTI.
Note that the same TTI is expected in every
member of an EoS group.

Table 174: AP: / unit-x / eos / eos-y / eos, Configuration - General (continued)
patibility “GFP” as valid signal label.
equipment.

In order to minimize the impact when adding members to an EoS group follow the
procedure below:
→ Add a single member to an EoS group.
→ Use the auto-assigned index number, this is the highest existing index number
+ 1.
→ Add the cross connection for the new EoS member to the transport Virtual Con-
tainer.
→ Add the next single member, and so on.

In order to minimize the impact when removing members from an EoS group follow
the procedure below:
→ Delete a single member from an EoS group.
→ Delete the member with the highest index number.
→ The cross connection of the deleted EoS member is automatically removed.
→ Delete the next single member, and so on.
8.22.4 AP: / unit-x / eos / eos-y / eos, Fault Management

Table 175: AP: / unit-x / eos / eos-y / eos, Fault Management

Affecting Severity
AIS VC AIS Received Communica- Minor Failure in the received optical or elec-
tion Alarm trical signal, in the RS or MS layer (AU-
4-AIS), or in the EoS VC-4 layer (TU-3-
AIS, TU-12-AIS) of one or more of the
VCG members.
GFPLOF GFP Loss Of Frame Communica- Major Multiple bit errors detected on the
tion Alarm GFP core header or GFP type header
by the HEC (header error check).
LOP VC Loss Of Pointer Communica- Major Eight consecutive invalid AU-4, TU-3
tion Alarm or TU-12 pointer values have been
received in one or more of the VCG
members.
A persistent mismatch between provi-
sioned and received AU or TU types
will also result in a LOP failure.

Table 175: AP: / unit-x / eos / eos-y / eos, Fault Management (continued)
Affecting Severity
PLM VC Payload Mismatch Communica- Major The received and accepted trail signal
“GFP” in the VC-4, VC-3 or VC-12 (VC-n-
PLM) in one or more of the VCG mem-
bers.
RDI VC Remote Defect Communica- Minor The far end equipment has one or
Indication tion Alarm more of the following defects in one
or more of the VCG members:
AU-4-LOP, AU-4-AIS, VC-4-UNEQ, VC-
4-TIM, (VC-4), or
VC-4-PLM, TU-3-LOP, TU-3-AIS, VC-3-
UNEQ, VC-3-TIM (VC-3), or
12-AIS, VC-12-UNEQ, VC-12-TIM (VC-
12).
TIM VC Trace Identifier Communica- Major The received and accepted TTI does
Mismatch tion Alarm not match the expected TTI (VC-n-
TIM) in one or more of the VCG mem-
bers.
UNEQ VC Unequipped Communica- Major The received and accepted trail signal
tion Alarm label indicates “Unequipped” (VC-n-
UNEQ) in one or more of the VCG
members.
VCATLOMF VCAT Loss Of Multi- Communica- Major Loss of the VCAT multiframe align-
frame tion Alarm ment in the H4 byte (VC-4, VC-3) or in
the K4 bit 2.
VCATSNM VCAT Sequence Num- Communica- Major The received VCAT sequence number
ber Mismatch tion Alarm does not match with the expected
one.
VCGLOA VCG Loss Of Align- Communica- Major The differential delay in the virtual
ment tion Alarm concatenation group exceeds the size
of the alignment buffer.
VCGLOPC VCG Loss Of Partial Communica- Minor One or more members of a group suf-
Capacity tion Alarm fer from payload mismatch, loss of
multiframe or a failure in the server
layer, but the group is still available.
LCAS mode only.
VCGLOTC VCG Loss Of Total Communica- Major The virtual concatenation group is not
Capacity tion Alarm available due to the fact that
- in non LCAS mode at least one mem-
ber of a group suffers from payload
mismatch, loss of multiframe or a
failure in the server layer, or
- in LCAS mode all members of a
group suffer from payload mis-
match, loss of multiframe or a failure
in the server layer
8.22.5 AP: / unit-x / eos / eos-y / eos, Performance Management

for the SAMOx EoS groups:

• “EoS GFP Encapsulation” group, see section 8.22.5.1 AP: / unit-x / eos / eos-y / eos, Perfor-
mance Management - EoS GFP Encapsulation (on page 278).

Counter interval EoS GFP Encapsula-
tion
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no
8.22.5.1 AP: / unit-x / eos / eos-y / eos, Performance Management - EoS GFP Encapsulation
Table 177: PM group: EoS GFP Encapsulation

Transmitted GFP Frames Number of egress GFP frames.
Received GFP Frames Number of ingress GFP frames.
Discarded GFP Frames Number of ingress discarded GFP frames.
Errored GFP Frames Number of ingress errored GFP frames.
8.22.6 AP: / unit-x / eos / eos-y / eos, Status
8.22.6.1 AP: / unit-x / eos / eos-y / eos, Status - General
Table 178: AP: / unit-x / eos / eos-y / eos, Status - General

General Total Members 0 … 63 Display of the total number of EoS group
members.
Up Members 0 … 63 Display of the number of operational EoS
group members.
Differential Delay 0 … 64’000 µs Display of the maximum transfer time differ-
ence between all members of the EoS group
(VCG) in microseconds. This value can be dif-
ferent from 0 when the transmission path is
not the same for all members of a group.
8.23 AP: / unit-x / eos / eos-y / eos / vcz-a

z = 4 (vc4), 3 (vc3) or 12 (vc12).

8.23.1 AP: / unit-x / eos / eos-y / eos / vcz-a, Overview

FOX612/FOX611”.
8.23.2 AP: / unit-x / eos / eos-y / eos / vcz-a, Main
8.23.2.1 AP: / unit-x / eos / eos-y / eos / vcz-a, Main - General

FOX612/FOX611”.
8.23.2.2 AP: / unit-x / eos / eos-y / eos / vcz-a, Main - Admin And Oper Status
Table 179: AP: / unit-x / eos / eos-y / eos / vcz-a, Main - Admin And Oper Status
Down EoS group member.
The operational state is up when the EoS port
Testing administrative state is up.
Unknown VC-4 members of an EoS group require in
addition a sink connection to another VC-4
Dormant
resource.
Not Present
Lower Layer Down

8.23.3 AP: / unit-x / eos / eos-y / eos / vcz-a, Configuration
8.23.3.1 AP: / unit-x / eos / eos-y / eos / vcz-a, Configuration - CTP
Table 180: AP: / unit-x / eos / eos-y / eos / vcz-a, Configuration - CTP
VC3 point is fixed according to the EoS group con-
figuration.
VC12
The number of time slots of a VC-4, VC-3 or
VC-12 is not applicable.
The timeslot(s) property of a VC-4, VC-3 or
VC-12 is not applicable.
Connection Index 0 … 65’535 Index of a connection assigned to the VC-4,
VC-3 or VC-12. Without a connection the
parameter is empty
Unidirectional
Local Role z-End The VC-4, VC-3 or VC-12 is the ending point of
a connection.
“TDM Services”
a-End Working The VC-4, VC-3 or VC-12 is the working start-
ing point of a protected or unprotected con-
nection.
a-End Protecting The VC-4, VC-3 or VC-12 is the protecting
starting point of a protected connection.

Table 180: AP: / unit-x / eos / eos-y / eos / vcz-a, Configuration - CTP (continued)
“TDM Services”
nection.
End.
ging over events.
Please note:
8.23.4 AP: / unit-x / eos / eos-y / eos / vc4-a, Fault Management

Table 181: AP: / unit-x / eos / eos-y / eos / vc4-a, Fault Management
Affecting Severity
VC-4.
VC-4.
FDPF Far End Degraded Communica- Warning ES ≥ 2592 or SES ≥ 33 or BBE ≥ 12’960
input signal.
signal.
and BBE ≤ 50.

Table 181: AP: / unit-x / eos / eos-y / eos / vc4-a, Fault Management (continued)
Affecting Severity
NDPF Near End Degraded Communica- Warning ES ≥ 2592 or SES ≥ 33 or BBE ≥ 12’960
input signal.
signal.
and BBE ≤ 50.
by default.
work connection.
by default.
Please note:


Affecting Severity
VC-3.
VC-3.
input signal.
signal.
and BBE ≤ 50.
input signal.
signal.
and BBE ≤ 50.
Alarm activation criteria: TU-3-LOP,
TU-3-AIS, VC-3-UNEQ or VC-3-TIM.
by default.

Affecting Severity
work connection.
by default.
Please note:

Affecting Severity
VC-12.
VC-12.
and BBE ≤ 12.

Affecting Severity
and BBE ≤ 12.
ure on the working or protecting VC-
by default.
work connection.
by default.
Please note:
8.23.7 AP: / unit-x / eos / eos-y / eos / vcz-a, Performance Management

able for the SAMOx EoS members:
• “G.826” group, see section 8.23.7.1 AP: / unit-x / eos / eos-y / eos / vcz-a, Performance
Management - G.826 (on page 286).
• “Unfiltered Events” group, see section 8.23.7.2 AP: / unit-x / eos / eos-y / eos / vcz-a, Perfor-
mance Management - Unfiltered Events (on page 286).

History 24h yes yes
Alarm 15min yes no
Alarm 24h yes no

8.23.7.1 AP: / unit-x / eos / eos-y / eos / vcz-a, Performance Management - G.826

8.23.7.2 AP: / unit-x / eos / eos-y / eos / vcz-a, Performance Management - Unfiltered Events

Protection Switches SNC protection switchover event
8.23.8 AP: / unit-x / eos / eos-y / eos / vcz-a, Status
8.23.8.1 AP: / unit-x / eos / eos-y / eos / vcz-a, Status - General
Table 187: AP: / unit-x / eos / eos-y / eos / vcz-a, Status - General
the VC-4 or VC-3 path overhead or the J2 byte
in the VC-12 path overhead.
The received TTI of every group member is
displayed.

Table 187: AP: / unit-x / eos / eos-y / eos / vcz-a, Status - General (continued)
Server Signal Sta- Server Signal State OK Failure indication of the VC-4, VC-3 or VC-12
tus AU-AIS server signal, i.e. the AU-4, TU-3 or TU-12 sig-
nal.
TU-AIS
AU-LOP
TU-LOP
Signal Label GFP The VC-4, VC-3 and VC-12 layers are able to
Unequipped transport a variety of client signals applied to
the layer via different adaptation functions.
<Any other signal label> The information about the signal type is car-
ried in the (trail) signal label, transported in
the C2 byte of the VC-4 or VC-3 path overhead
or the V5 byte of the VC-12 path overhead.
SAMOx inserts the signal label “GFP” for all VC
signals used for Ethernet transport.
signal label, i.e. “GFP”.
Not Checked The EoS VC is not cross connected.
RDI State The VC-4, VC-3 and VC-12 path remote defect
indication (RDI) displays the received RDI
state which is sent back from the far end ter-
mination function, if either an AU-4, TU-3 or
TU-12 server signal failure or a trail signal fail-
ure is being detected.
RDI is transported in the G1 byte of the VC-4
or VC-3 path overhead or the V5 byte of the
VC-12 path overhead. It can be “true” or
“false”.
E.g. a TTI mismatch in the RS layer inserts an
AIS as a consequent action. All subsequent
failures are also displayed: Signal label mis-
match.
8.23.8.2 AP: / unit-x / eos / eos-y / eos / vcz-a, Status - EoS

Table 188: AP: / unit-x / eos / eos-y / eos / vcz-a, Status - EoS
EoS Status Rx State Operational Display of the receiver state of each member
Failed (VC-4, VC-3 or VC-12) of an EoS group. The
state can be:
Idle - Operational, or
- Failed, due to a loss of the multiframe align-
ment or a VC signal failure, or
- Idle, the member is not part of the group or
about to be removed.
Tx State Operational When LCAS is enabled the transmitter state
of each member (VC-4, VC-3 or VC-12) of an
EoS group is displayed.
Operational indicates normal transmission.
Added This member is about to be added to the
group.
Idle This member is not part of the group or
about to be removed.
Do Not Use Do not use the payload since the receive side
reported a failure
Fixed Non-LCAS LCAS is disabled.
Sequence Number 0 … 63 The sequence number uniquely identifies
each received member within an EoS group.
None The EoS group member is not operational.
8.23.8.3 AP: / unit-x / eos / eos-y / eos / vcz-a, Status - CTP

Table 189: AP: / unit-x / eos / eos-y / eos / vcz-a, Status - CTP
Remote CTP tion termination point) where the VC-4, VC-3
or VC-12 is connected to, e.g. /unit-20/port-
1/j-1.
tus remote CTP.
remote CTP.
at the remote CTP.
tion.
Status remote CTP.
remote CTP.
at the remote CTP.
tion.
protecting trail.
working trail.

8.24 AP: / unit-x / iports
8.24.1 AP: / unit-x / iports, Overview

− “Overview - Statistics”
FOX612/FOX611”.
8.24.2 AP: / unit-x / iports, Main

FOX612/FOX611”.
8.25 AP: / unit-x / iports / iport-b

The internal ports connect the SAMOx unit via the backplane to the core unit(s). The port usage
is as follows:
Table 190: Internal port usage

Internal port Ethernet star CESM3 CESM1 or CESM2
iport-1 1 GbE to the active subrack internal manage- user traffic and subrack
core unit ment traffic internal management traffic
iport-2 1 GbE to the unit pro-
cessor
iport-3 10 GbE to unit-11 user traffic not usable
iport-4 10 GbE to unit-13
Please note:
Only the backplane connection to the active core unit is used.
→ The backplane connection to the standby core unit is not used.
Please note:
The internal port iport-1 corresponds to the backplane port connected to the active
core unit.
→ With the CESM3 core unit the port statistics of iport-1 show the transmit and
receive counter values of the management traffic.
→ With the CESM1 or CESM2 core unit the port statistics of iport-1 show the
transmit and receive counter values of the user traffic and management traffic.
Please note:
The internal port iport-2 corresponds to the unit internal switch port connected to
the unit processor.
→ The port statistics of iport-2 show the transmit and receive counter values of the
management traffic. The receive and transmit counter values are interchanged
with respect to the counter values of iport-1.

8.25.1 AP: / unit-x / iports / iport-b, Main
8.25.1.1 AP: / unit-x / iports / iport-b, Main – General

FOX612/FOX611”.
Table 191: AP: / unit-x / iports / iport-b, Main – General

Interface Status Admin Status Up Select “Up” to bring the internal port into service
Down The internal port cannot be set to the Down state.
Please note:
The administrative state of the internal ports iport-1 and iport-2 are always up.
8.25.1.2 AP: / unit-x / iports / iport-b, Main – Physical

Table 192: AP: / unit-x / iports / iport-b, Main – Physical

MAC Address 00:00:00:00:00:00 … Shows the physical (MAC) address of this
MTU 1’978 … 9’194 Octets, Maximum Transmission Unit, i.e. maximum IP
step 2 Octets packet size.
The MTU size is calculated including the IP
headers.
Please note:
The port speed of the internal ports iport-1 and iport-2 is cannot be modified. It is
fixed to 1’000 Mbit/s.
Please note:
The port speed of the internal ports iport-3 and iport-4 is managed via the AP: /
backplane, Main - Port Speed.
Please note:
For an overview on the specific characteristics of FOX61x Switch ports, please
refer to [1KHW002460] System Description “FOX61x R15B”.
8.25.2 AP: / unit-x / iports / iport-b, Performance Management

FOX612/FOX611”.
8.25.3 AP: / unit-x / iports / iport-b, Statistics

FOX612/FOX611”.
8.25.4 AP: / unit-x / iports / iport-b, QoS

− “QoS - TC Scheduling”, and
− “QoS - Port Shaping”

FOX61x | SAMO2, SAMO3, SAMO5 ANNEX
9 Annex
9.1 Associated FOX61x Documents

[1KHW028777] Release Note “FOX61x System Release R15B”
[1KHW002460] System Description “FOX61x R15B”
[1KHW002497] Operating 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”
[1KHW029105] User Manual “Synchronization”
[1KHW028566] User Manual “Ethernet Services”
[1KHW028618] User Manual “MPLS-TP Services”
[1KHW029124] User Manual “Quality of Service”
[1KHW002469] User Manual “CESM1, CESM1-F”
[1KHW028642] User Manual “CESM2, CESM2-F”
[1KHW028774] User Manual “CESM3”
[1KHW002473] User Manual “LEDE1”
[1KHW002498] Product Guide “FOX61x cables”
[1KHW028776] Product Description “Feature Licenses for FOX61x”
[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: [email protected]
www.hitachienergy.com/communication-networks
Document ID: 1KHW028668
Copyright 2022 Hitachi Energy. All rights reserved.

Specifications subject to change without notice.

Samox Um

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Samox Um

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Samox Um

Uploaded by

Copyright:

Available Formats

USER MANUAL

Document edition FOX61x System Release: R15B

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.4.2 Ethernet Internal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Copyright 2022 Hitachi Energy. All rights reserved. 4

8.3.1 AP: / unit-x / port-y, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Copyright 2022 Hitachi Energy. All rights reserved. 5

8.13.6 AP: / unit-x / vc4 / vc4-b, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Copyright 2022 Hitachi Energy. All rights reserved. 6

8.23.2 AP: / unit-x / eos / eos-y / eos / vcz-a, Main . . . . . . . . . . . . . . . . . . . . . . 279

Copyright 2022 Hitachi Energy. All rights reserved. 7

1.1 Precautions and Safety

1.2 Symbols and Notations

CAUTION Non-observance could result in minor or moderate injury.

Risk of operating trouble!

1.3 Interfaces and Circuit Categories

Table 1: Electrical interfaces and circuit categories

Copyright 2022 Hitachi Energy. All rights reserved. 8

Table 2: Optical interfaces

1.4 Document History

Copyright 2022 Hitachi Energy. All rights reserved. 9

Table 3: Document history (continued)

1.5 Target Audience

1.6 Definition of Terms

Copyright 2022 Hitachi Energy. All rights reserved. 10

Table 4: Specific terms (continued)

Copyright 2022 Hitachi Energy. All rights reserved. 11

Copyright 2022 Hitachi Energy. All rights reserved. 12

ETH ETH ETH ETH SDH SDH SDH SDH

10Gb Ethernet 1Gb Ethernet PBUS

Figure 1: SAMOx overview

Copyright 2022 Hitachi Energy. All rights reserved. 13

E12 SAMO3 only

Figure 2: SAMOx unit in an add/drop multiplexer application

Copyright 2022 Hitachi Energy. All rights reserved. 14

2.2 Unit View

Figure 4: SAMO3 unit view

Copyright 2022 Hitachi Energy. All rights reserved. 15

CAUTION Non-observance could result in minor or moderate injury.

Copyright 2022 Hitachi Energy. All rights reserved. 16

2.3 Block Diagram

10/100/1000 STM-4/STM-1 STM-4/STM-1 STM-16/STM-4 STM-16/STM-4 SAMOx

STM STM STM STM STM STM STM STM SETS

AU-4 Cross Connect

12x AU-4 31x AU-4

PBUS PBUS PBUS

Figure 5: SAMOx block diagram

Copyright 2022 Hitachi Energy. All rights reserved. 17

STM-x STM-x STM-x STM-x

Figure 6: Redundancy switch, working unit is active

Copyright 2022 Hitachi Energy. All rights reserved. 18

Copyright 2022 Hitachi Energy. All rights reserved. 19

3 Functions and Specifications

3.1 Feature Licenses